[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] XEN 4.3.0 Complete Crash on Kernel vmlinuz-3.2.0-4-amd64


no patch at all is needed since XEN is fully included in the kernel. My
kernel config file works for 3.10.5. you can open that file with 3.10.8,
make menuconfig will then update the kernel config to the newer version

what I do is going through the new kernel config file, since new features
have often "DEBUG" enabled. And I don't want DEBUG information in my
productive kernel (ex: WIF, LAN, ...).

If you want DEBUG information you have to, those you want, turn on.

My procedure is:

aptitude install fakeroot build-essential kernel-package fakeroot
cd /usr/src
tar -Jxvf [KERNEL_SOURCE].xz
make menuconfig
CONCURRENCY_LEVEL=$(getconf _NPROCESSORS_ONLN) fakeroot make-kpkg --initrd
kernel_image kernel_headers modules_image
cd ..
dpkg -I [KERNEL].deb

aptitude install build-essential bcc bin86 libcurl3 bzip"
"drbd8-module-source drbd8-utils build-essential bcc bin86 libcurl3 bzip2
pciutils-dev gettext libpci-dev mercurial make gcc libc6-dev libncurses5-dev
patch libvncserver-dev libsdl-dev
aptitude install iasl bison flex libyajl-dev gcc-multilib libaio-dev
libncurses-dev python-dev uuid uuid-dev libglib2.0-dev libyajl-dev
libpci-dev libaio-dev iproute xz-utils bridge-utils python module-init-tools
zlib1g-dev libbz2-dev liblzo2-dev
aptitude install libpixman-1-dev e2fslibs-dev ocaml ocaml-nox ocaml-findlib
lzma lzma-dev liblzma-dev markdown libcurl4-openssl-dev transfig tgif gawk
git-core texinfo texlive-fonts-recommended
aptitude install texlive-latex-recommended python-twisted
texlive-fonts-extra texlive-latex-base

wget [XEN_SOURCE].tar.gz
tar xvfz [XEN_SOURCE].tar.gz
./configure --enable-githttp --libdir=/usr/lib;
make -j $CONCURRENCY_LEVEL dist; 
make install
make install-tools PYTHON_PREFIX_ARG=--install-layout=deb

# I don't need al thos kernels variation, only 4-3-0 :-)
rm -f /boot/xen.gz;
rm -f /boot/xen-4.gz;
rm -f /boot/xen-4.3.gz;
cp /boot/xen-syms-4.3.0 /etc/xen/xen-syms-4.3.0;
rm -f /boot/xen-syms-4.3.0;

update-rc.d xencommons defaults;
update-rc.d xendomains defaults;
update-rc.d xen-watchdog defaults;

# in /etc/default change/add
GRUB_CMDLINE_LINUX="panic=30 noswap nosplash - rootdelay=7"

# in /etc/xen/xl.conf change/add

# in /etc/sysctl.conf comment out all except
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0

that's it from my side

-----Original Message-----
From: Maik Brauer [mailto:maik.brauer@xxxxxxxxxxxxxxx] 
Sent: Mittwoch, 21. August 2013 09:47
To: Walter Robert Ditzler
Subject: Re: [Xen-users] XEN 4.3.0 Complete Crash on Kernel

Hi Walter,

question. Do I need to patch the original kernels (3.10.8 or 3.10.5) in any
way with files for xen?
Or is it just the .config file to compile with the original kernels and all
is good?

Can you please more elaborate on things needs to be done. Thanks a lot.


On 20.08.2013, at 20:18, Maik Brauer <maik.brauer@xxxxxxxxxxxxxxx> wrote:

> Hi Walter,
> no I have just used the kernel which is shipped by the Debian Wheezy
> I will install now the serial Console as well.
> Will give it a try with the current stable 3.10.8 Kernel.
> Will try your config file and compile the 3.10.5 as well to test.
> Thanks a lot for the answer.
> Cheers,
> Maik
> On Aug 20, 2013, at 4:47 PM, Walter Robert Ditzler <ditwal001@xxxxxxxxxxx>
>> Hi Maik,
>> Did you compile your kernel by your-self? I had to move up to a more 
>> recent kernel too. Now my XEN 4.3, Debian Wheezy runs since one month 
>> in production perfectly with attached 3-10-5 kernel config file / kernel.
>> Serial Console always helps ;-)
>> Thanks Walter.
>> -----Original Message-----
>> From: xen-users-bounces@xxxxxxxxxxxxx 
>> [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Wei Liu
>> Sent: Dienstag, 20. August 2013 15:42
>> To: Maik Brauer
>> Cc: xen-users@xxxxxxxxxxxxx; wei.liu2@xxxxxxxxxx
>> Subject: Re: [Xen-users] XEN 4.3.0 Complete Crash on Kernel
>> vmlinuz-3.2.0-4-amd64
>> On Tue, Aug 20, 2013 at 03:19:28PM +0200, Maik Brauer wrote:
>>> Hello,
>>> I have installed the new version XEN 4.3.0 from the Source packages 
>>> from
>> the xen homepage with Debian 7.1 Dom0.
>>> After some time (approx. 6 days) the whole machine crashes, with all 
>>> the
>> Domains (DomU) running on it.
>>> -rw-r--r--  1 root root 2.8M Jun  9 20:35 vmlinuz-3.2.0-4-amd64
>>> -rw-r--r--  1 root root 127K Jun  9 20:47 config-3.2.0-4-amd64
>>> -rw-r--r--  1 root root 2.1M Jun  9 20:47 System.map-3.2.0-4-amd64
>>> drwx------  2 root root  16K Jul 27 23:19 lost+found
>>> -rw-r--r--  1 root root  12M Jul 27 23:19 initrd.img-3.2.0-4-amd64
>>> -rw-r--r--  1 root root  16M Jul 28 00:07 xen-syms-4.3.0
>>> -rw-r--r--  1 root root 814K Jul 28 00:07 xen-4.3.0.gz
>>> Just a hardware reset will bring up the machine again. The logs are 
>>> not
>> showing that much information, which could lead to the issue.
>>> What can I do here in order to find the root cause. This XEN machine 
>>> is
>> not usable, due the fact that it can crash suddenly.
>>> Find attached a screenshot from the console.
>>> Thanks a lot for any helpful answer in advance.
>> The stack trace in your photo is just a portion of the whole thing. 
>> The most interesting bit would be the upper part of the stacktrace 
>> which includes various infomation.
>> If you have a serial console it would be handy. Please refer to 
>> http://wiki.xen.org/wiki/Xen_Serial_Console
>> on how to configure serial console.
>> Wei.
>>> Cheers,
>>> Maik
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxx
>>> http://lists.xen.org/xen-users
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-users
>> <config->
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.