jesse
2011-May-13 19:48 UTC
[Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, hangs, reboots
I upgraded a test system from Xen 3.3 to Xen 4.1.0. I''ve compiled a kernel from the xen/stable-2.6.32.x branch from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. While I can get virtual machines from Xen 3.3 to run with some configuration changes I''ve been unable to keep the host system stable for more than a few hours when running domU''s. This could be hardware related as this is hardly server grade hardware. This is an AMD Athlon X2 on a consumer motherboard (ASUS I think). I have run memtest for many hours to see if this was related to bad memory but all memory has tested fine. After a few hours of running domU''s the system will either reboot, hard lock (completely unresponsive), crash (completely unresponsive plus stack trace displayed), or soft lock (magic sysrq still working). I''ve tried running domU''s using both xl and xm but both were unstable. Here is the xen options for the kernel configuration: CONFIG_XEN=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=y CONFIG_MICROCODE_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y # CONFIG_XEN_PCI_PASSTHROUGH is not set CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_KBDDEV_FRONTEND=m CONFIG_HVC_XEN=y CONFIG_XEN_WDT=m CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=y CONFIG_XEN_BLKBACK_PAGEMAP=y CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_MCE=y CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_GNTDEV=y CONFIG_XEN_S3=y CONFIG_ACPI_PROCESSOR_XEN=y CONFIG_XEN_PLATFORM_PCI=m I''ve attached a couple of screenshots of stack traces when those have been present. Are there known problems with stability in Xen 4.1? Is this possibly a hardware issue that for some reason was not a problem under Xen 3.3? Have I inadvertently enabled an unstable kernel module? Any advice on how to move forward and resolve this issue. I''d like to upgrade my Xen 3.x servers but only once I can be certain there is a stable platform for migrate too. Any advice would be appreciated. Thank you. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
agent 8131
2011-May-16 22:54 UTC
[Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, hangs, reboots
I upgraded a test system from Xen 3.3 to Xen 4.1.0. I''ve compiled a kernel from the xen/stable-2.6.32.x branch from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. While I can get virtual machines from Xen 3.3 to run with some configuration changes I''ve been unable to keep the host system stable for more than a few hours when running domU''s. This could be hardware related as this is hardly server grade hardware. This is an AMD Athlon X2 on a consumer motherboard (ASUS I think). I have run memtest for many hours to see if this was related to bad memory but all memory has tested fine. After a few hours of running domU''s the system will either reboot, hard lock (completely unresponsive), crash (completely unresponsive plus stack trace displayed), or soft lock (magic sysrq still working). I''ve tried running domU''s using both xl and xm but both were unstable. Here is the xen options for the kernel configuration: CONFIG_XEN=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=y CONFIG_MICROCODE_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y # CONFIG_XEN_PCI_PASSTHROUGH is not set CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_KBDDEV_FRONTEND=m CONFIG_HVC_XEN=y CONFIG_XEN_WDT=m CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=y CONFIG_XEN_BLKBACK_PAGEMAP=y CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_MCE=y CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_GNTDEV=y CONFIG_XEN_S3=y CONFIG_ACPI_PROCESSOR_XEN=y CONFIG_XEN_PLATFORM_PCI=m I''ve attached a couple of screenshots of stack traces when those have been present. Are there known problems with stability in Xen 4.1? Is this possibly a hardware issue that for some reason was not a problem under Xen 3.3? Have I inadvertently enabled an unstable kernel module? Any advice on how to move forward and resolve this issue. I''d like to upgrade my Xen 3.x servers but only once I can be certain there is a stable platform for migrate too. Any advice would be appreciated. Thank you. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
agent 8131
2011-May-17 10:49 UTC
[Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, hangs, reboots
I upgraded a test system from Xen 3.3 to Xen 4.1.0. I''ve compiled a kernel from the xen/stable-2.6.32.x branch from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. While I can get virtual machines from Xen 3.3 to run with some configuration changes I''ve been unable to keep the host system stable for more than a few hours when running domU''s. This could be hardware related as this is hardly server grade hardware. This is an AMD Athlon X2 on a consumer motherboard (ASUS I think). I have run memtest for many hours to see if this was related to bad memory but all memory has tested fine. After a few hours of running domU''s the system will either reboot, hard lock (completely unresponsive), crash (completely unresponsive plus stack trace displayed), or soft lock (magic sysrq still working). I''ve tried running domU''s using both xl and xm but both were unstable. Here is the xen options for the kernel configuration: CONFIG_XEN=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=y CONFIG_MICROCODE_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y # CONFIG_XEN_PCI_PASSTHROUGH is not set CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_KBDDEV_FRONTEND=m CONFIG_HVC_XEN=y CONFIG_XEN_WDT=m CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=y CONFIG_XEN_BLKBACK_PAGEMAP=y CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_MCE=y CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_GNTDEV=y CONFIG_XEN_S3=y CONFIG_ACPI_PROCESSOR_XEN=y CONFIG_XEN_PLATFORM_PCI=m I''ve attached a couple of screenshots of stack traces when those have been present. Are there known problems with stability in Xen 4.1? Is this possibly a hardware issue that for some reason was not a problem under Xen 3.3? Have I inadvertently enabled an unstable kernel module? Any advice on how to move forward and resolve this issue. I''d like to upgrade my Xen 3.x servers but only once I can be certain there is a stable platform for migrate too. Any advice would be appreciated. Thank you. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Tobin
2011-May-18 08:22 UTC
RE: [Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, hangs, reboots
What is your grub config set to? Ian -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of agent 8131 Sent: 16 May 2011 23:55 To: xen-users@lists.xensource.com Subject: [Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, hangs,reboots I upgraded a test system from Xen 3.3 to Xen 4.1.0. I''ve compiled a kernel from the xen/stable-2.6.32.x branch from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. While I can get virtual machines from Xen 3.3 to run with some configuration changes I''ve been unable to keep the host system stable for more than a few hours when running domU''s. This could be hardware related as this is hardly server grade hardware. This is an AMD Athlon X2 on a consumer motherboard (ASUS I think). I have run memtest for many hours to see if this was related to bad memory but all memory has tested fine. After a few hours of running domU''s the system will either reboot, hard lock (completely unresponsive), crash (completely unresponsive plus stack trace displayed), or soft lock (magic sysrq still working). I''ve tried running domU''s using both xl and xm but both were unstable. Here is the xen options for the kernel configuration: CONFIG_XEN=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=y CONFIG_MICROCODE_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y # CONFIG_XEN_PCI_PASSTHROUGH is not set CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_KBDDEV_FRONTEND=m CONFIG_HVC_XEN=y CONFIG_XEN_WDT=m CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=y CONFIG_XEN_BLKBACK_PAGEMAP=y CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_MCE=y CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_GNTDEV=y CONFIG_XEN_S3=y CONFIG_ACPI_PROCESSOR_XEN=y CONFIG_XEN_PLATFORM_PCI=m I''ve attached a couple of screenshots of stack traces when those have been present. Are there known problems with stability in Xen 4.1? Is this possibly a hardware issue that for some reason was not a problem under Xen 3.3? Have I inadvertently enabled an unstable kernel module? Any advice on how to move forward and resolve this issue. I''d like to upgrade my Xen 3.x servers but only once I can be certain there is a stable platform for migrate too. Any advice would be appreciated. Thank you. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
agent 8131
2011-May-19 06:52 UTC
Re: [Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, hangs, reboots
On 05/18/2011 01:22 AM, Ian Tobin wrote:> What is your grub config set to? > > Iantitle Xen 4.1.0 / Ubuntu 10.04.2 LTS, kernel 2.6.32.39 root (hd0,0) kernel /boot/xen-4.1.0.gz dom0_mem=768M module /boot/vmlinuz-2.6.32.39 root=/dev/md0 ro console=tty0 module /boot/initrd.img-2.6.32.39> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of agent 8131 > Sent: 16 May 2011 23:55 > To: xen-users@lists.xensource.com > Subject: [Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, > hangs,reboots > > I upgraded a test system from Xen 3.3 to Xen 4.1.0. I''ve compiled a > kernel from the xen/stable-2.6.32.x branch from > git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. While I > can get virtual machines from Xen 3.3 to run with some configuration > changes I''ve been unable to keep the host system stable for more than a > few hours when running domU''s. This could be hardware related as this > is hardly server grade hardware. This is an AMD Athlon X2 on a consumer > motherboard (ASUS I think). I have run memtest for many hours to see if > this was related to bad memory but all memory has tested fine. After a > few hours of running domU''s the system will either reboot, hard lock > (completely unresponsive), crash (completely unresponsive plus stack > trace displayed), or soft lock (magic sysrq still working). > > I''ve tried running domU''s using both xl and xm but both were unstable. > Here is the xen options for the kernel configuration: > > CONFIG_XEN=y > CONFIG_XEN_PVHVM=y > CONFIG_XEN_MAX_DOMAIN_MEMORY=128 > CONFIG_XEN_SAVE_RESTORE=y > # CONFIG_XEN_DEBUG_FS is not set > CONFIG_SWIOTLB_XEN=y > CONFIG_MICROCODE_XEN=y > CONFIG_XEN_DOM0=y > CONFIG_XEN_PRIVILEGED_GUEST=y > CONFIG_XEN_DOM0_PCI=y > # CONFIG_XEN_PCI_PASSTHROUGH is not set > CONFIG_PCI_XEN=y > CONFIG_XEN_PCIDEV_FRONTEND=m > CONFIG_XEN_BLKDEV_FRONTEND=m > CONFIG_NETXEN_NIC=m > CONFIG_XEN_NETDEV_FRONTEND=m > CONFIG_XEN_KBDDEV_FRONTEND=m > CONFIG_HVC_XEN=y > CONFIG_XEN_WDT=m > CONFIG_XEN_FBDEV_FRONTEND=m > CONFIG_XEN_BALLOON=y > CONFIG_XEN_SCRUB_PAGES=y > CONFIG_XEN_DEV_EVTCHN=y > CONFIG_XEN_BACKEND=y > CONFIG_XEN_NETDEV_BACKEND=y > CONFIG_XEN_BLKDEV_BACKEND=y > CONFIG_XEN_BLKDEV_TAP=y > CONFIG_XEN_BLKBACK_PAGEMAP=y > CONFIG_XEN_PCIDEV_BACKEND=y > CONFIG_XEN_PCIDEV_BACKEND_VPCI=y > # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # > CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # > CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # > CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=m > CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_MCE=y > CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_GNTDEV=y CONFIG_XEN_S3=y > CONFIG_ACPI_PROCESSOR_XEN=y CONFIG_XEN_PLATFORM_PCI=m > > I''ve attached a couple of screenshots of stack traces when those have > been present. Are there known problems with stability in Xen 4.1? Is > this possibly a hardware issue that for some reason was not a problem > under Xen 3.3? Have I inadvertently enabled an unstable kernel module? > Any advice on how to move forward and resolve this issue. I''d like to > upgrade my Xen 3.x servers but only once I can be certain there is a > stable platform for migrate too. > > Any advice would be appreciated. Thank you. > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
agent 8131
2011-May-21 22:00 UTC
Re: [Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, hangs, reboots
Still happening. the last 2 times the Xen 4.1 system has hard locked after running for 4-6 hours. My plan is to try Xen 4.0.1 instead. It would be nice if someone would support Xen 4.1. On 05/18/2011 11:52 PM, agent 8131 wrote:> On 05/18/2011 01:22 AM, Ian Tobin wrote: >> What is your grub config set to? >> >> Ian > title Xen 4.1.0 / Ubuntu 10.04.2 LTS, kernel 2.6.32.39 > root (hd0,0) > kernel /boot/xen-4.1.0.gz dom0_mem=768M > module /boot/vmlinuz-2.6.32.39 root=/dev/md0 ro console=tty0 > module /boot/initrd.img-2.6.32.39 > > >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of agent 8131 >> Sent: 16 May 2011 23:55 >> To: xen-users@lists.xensource.com >> Subject: [Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, >> hangs,reboots >> >> I upgraded a test system from Xen 3.3 to Xen 4.1.0. I''ve compiled a >> kernel from the xen/stable-2.6.32.x branch from >> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. While I >> can get virtual machines from Xen 3.3 to run with some configuration >> changes I''ve been unable to keep the host system stable for more than a >> few hours when running domU''s. This could be hardware related as this >> is hardly server grade hardware. This is an AMD Athlon X2 on a consumer >> motherboard (ASUS I think). I have run memtest for many hours to see if >> this was related to bad memory but all memory has tested fine. After a >> few hours of running domU''s the system will either reboot, hard lock >> (completely unresponsive), crash (completely unresponsive plus stack >> trace displayed), or soft lock (magic sysrq still working). >> >> I''ve tried running domU''s using both xl and xm but both were unstable. >> Here is the xen options for the kernel configuration: >> >> CONFIG_XEN=y >> CONFIG_XEN_PVHVM=y >> CONFIG_XEN_MAX_DOMAIN_MEMORY=128 >> CONFIG_XEN_SAVE_RESTORE=y >> # CONFIG_XEN_DEBUG_FS is not set >> CONFIG_SWIOTLB_XEN=y >> CONFIG_MICROCODE_XEN=y >> CONFIG_XEN_DOM0=y >> CONFIG_XEN_PRIVILEGED_GUEST=y >> CONFIG_XEN_DOM0_PCI=y >> # CONFIG_XEN_PCI_PASSTHROUGH is not set >> CONFIG_PCI_XEN=y >> CONFIG_XEN_PCIDEV_FRONTEND=m >> CONFIG_XEN_BLKDEV_FRONTEND=m >> CONFIG_NETXEN_NIC=m >> CONFIG_XEN_NETDEV_FRONTEND=m >> CONFIG_XEN_KBDDEV_FRONTEND=m >> CONFIG_HVC_XEN=y >> CONFIG_XEN_WDT=m >> CONFIG_XEN_FBDEV_FRONTEND=m >> CONFIG_XEN_BALLOON=y >> CONFIG_XEN_SCRUB_PAGES=y >> CONFIG_XEN_DEV_EVTCHN=y >> CONFIG_XEN_BACKEND=y >> CONFIG_XEN_NETDEV_BACKEND=y >> CONFIG_XEN_BLKDEV_BACKEND=y >> CONFIG_XEN_BLKDEV_TAP=y >> CONFIG_XEN_BLKBACK_PAGEMAP=y >> CONFIG_XEN_PCIDEV_BACKEND=y >> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y >> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # >> CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # >> CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # >> CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=m >> CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_MCE=y >> CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_GNTDEV=y CONFIG_XEN_S3=y >> CONFIG_ACPI_PROCESSOR_XEN=y CONFIG_XEN_PLATFORM_PCI=m >> >> I''ve attached a couple of screenshots of stack traces when those have >> been present. Are there known problems with stability in Xen 4.1? Is >> this possibly a hardware issue that for some reason was not a problem >> under Xen 3.3? Have I inadvertently enabled an unstable kernel module? >> Any advice on how to move forward and resolve this issue. I''d like to >> upgrade my Xen 3.x servers but only once I can be certain there is a >> stable platform for migrate too. >> >> Any advice would be appreciated. Thank you. >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2011-May-23 20:16 UTC
Re: [Xen-users] Xen 4.1.0 + stable-2.6.32.x kernel = crashes, hangs, reboots
On Fri, May 13, 2011 at 12:48:30PM -0700, jesse wrote:> I upgraded a test system from Xen 3.3 to Xen 4.1.0. I''ve compiled a > kernel from the xen/stable-2.6.32.x branch from > git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. While I > can get virtual machines from Xen 3.3 to run with some configuration > changes I''ve been unable to keep the host system stable for more than a > few hours when running domU''s. This could be hardware related as this > is hardly server grade hardware. This is an AMD Athlon X2 on a consumer > motherboard (ASUS I think). I have run memtest for many hours to see if > this was related to bad memory but all memory has tested fine. After a > few hours of running domU''s the system will either reboot, hard lock > (completely unresponsive), crash (completely unresponsive plus stack > trace displayed), or soft lock (magic sysrq still working). > > I''ve tried running domU''s using both xl and xm but both were unstable. > Here is the xen options for the kernel configuration: ><snip> Hello, Can you post your full .config ? Did you try my "reference" .config ? (available on XenParavirtOps wiki page).> > I''ve attached a couple of screenshots of stack traces when those have > been present. Are there known problems with stability in Xen 4.1? Is > this possibly a hardware issue that for some reason was not a problem > under Xen 3.3? Have I inadvertently enabled an unstable kernel module? > Any advice on how to move forward and resolve this issue. I''d like to > upgrade my Xen 3.x servers but only once I can be certain there is a > stable platform for migrate too. > > Any advice would be appreciated. Thank you.I haven''t seen this crash earlier.. you should set up a serial console and capture the full xen+dom0 console output, including the crash/oops, so it can be debugged.. http://wiki.xen.org/xenwiki/XenSerialConsole -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users