similar to: Newer Dom0 Xen kernel

We have a (supposedly) quite standard setup: 2 Dom0 with drbd-on-lvm and a bunch of DomU, on Quad Xeon Dell servers. We tried with both sid-based and etch-based (+ 3.1 xen hypervisor and drbd 8 from backports.org ) Dom0, and quite consistently have "kernel: invalid opcode: 0000 [1] SMP" errors which freezes Dom0 (during lasts tests a simple start-and-stop loop of 10 DomU can trigger

Dear List, I have problems using Xen dom0 Kernel including the IMA Kernel Module (Linux Integrity Measurement - http://linux-ima.sourceforge.net/) The IMA supports only kernel > 2.6.32 and I dont know how to find and build a Xen dom0 kernel in version greater or equal than 2.6.32. There is just kernel 2.6.18-xen in the Mercurial repository which is normally used during the standard

Dear List, I have problems using Xen dom0 Kernel including the IMA Kernel Module (Linux Integrity Measurement - http://linux-ima.sourceforge.net/) The IMA supports only kernel > 2.6.32 and I dont know how to find and build a Xen dom0 kernel in version greater or equal than 2.6.32. There is just kernel 2.6.18-xen in the Mercurial repository which is normally used during the standard

Processing commands for control at bugs.debian.org: > reassign 603727 linux-2.6 Bug #603727 [xen-hypervisor-4.0-amd64] xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver) Bug reassigned from package 'xen-hypervisor-4.0-amd64' to 'linux-2.6'. No longer marked as found in versions xen/4.0.1-1.

Hi, After the discussions of the last week about the topic of dom0 support, and being fairly sure there is no working solution in any distribution, I've been shown a working dom0 with Ubuntu, with 2.6.24-20. I actually did not believe this would work, and stated I'd not believe it until seeing it - and I saw it some minutes later, Ubuntu 7.10 booting dom0 with 2.6.24-20. No idea what

On Debian Squeeze (2.6.32-5) running Xen 4.0, I have created 2 Ubuntu Lucid Lynx (Ubuntu 10.04) vms. The vms, in a stress test, pass a large file between them via nfs file sharing. A previous entry in this forum helped to establish that some ethernet cards improve VM IO performance. However, our box installed with better intel nics is still rebooting under heavy VM IO loads. The kernel call

I use xen 4.0(dom0 is suse11.sp1,2.6.32 x86_64) on Dell R710 with PERC H700 RAID adapter. --Intel(R) Xeon(R) CPU E5620 @ 2.40GHz --8 CPU cores. --Memory 64G --RAID5 4.5T When I dedicated (pin) a CPU core only for dom0 use. (I specify "dom0_max_vcpus=1 dom0_vcpus_pin" options for Xen) I got dom0 kernel panic error(pin-1-5.30.bmp) When I pin 2 core to dom0, the dom0 system can boot up,

As far as I work out the version of the Dom0 linux kernel has to be 2.6.18. This is causing me a lot of problem, because the driver support in 2.6.18 is slowly falling behind, and I finding that more modern hardware isn''t supported by the 2.6.18 drivers. Is it possible to use a more recent version of the kernel for Dom0, or am I stuck with 2.6.18? Is there another way I can use more

Hello. Which kernel could be used for dom0 together with just-uploaded xen hypervisor 3.2 ? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20080123/64b16f1f/attachment.pgp

I have an IBM System x 3250 that successfully boots using the standard kernel (2.6.18-8.1.10.el5) but fails to boot with the xen kernel. The kernel appears to fail when it attempts to initialize the driver for the onboard SAS controller (LSI Logic / Symbios Logic SAS1064E PCI-Express Fusion-MPT SAS). Can anyone provide any advice? Here's the relevant info. Please let me know if any other

Hi Folks, Can anybody advise me which if any 3D (GLX) graphics card works well in 3D mode under a Xen dom0 kernel? My current hardware [Nvidia GEForce 7300LE] requires an Nvidia-supplied driver for GLX that appears to be incompatible with a xen-compatible linux kernel (at least 2.6.18-xen built from the xen-3.1.0 source tarball). My requirements are: - Must be 3D/GLX compatible so I can run

Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier.

Hello, More information and a patch for the bug. -- Pasi ----- Forwarded message from George Dunlap <George.Dunlap at eu.citrix.com> ----- From: George Dunlap <George.Dunlap at eu.citrix.com> To: Jan Beulich <JBeulich at novell.com> Cc: Sander Eikelenboom <linux at eikelenboom.it>, Jeremy Fitzhardinge <jeremy at goop.org>, Yunhong Jiang <yunhong.jiang at

Hi, I have an issue with my XEN servers, in that when I do a yum upgrade, it upgrades the kernels, and then updates the grub.conf file to boot with the normal Linux kernel, and not the XEN kernel - and I tend to forget to update the grub.conf, until I reboot and see XEN isn't running. So, is it safe to remove the normal kernel & kernel-development, and only run the XEN kernel? This is

Hello, The email (thread) below from xen-devel mailinglist indicates the changesets that should fix the bug that causes the lenny 2.6.26 xen kernel to crash on newer xen hypervisors. The workaround for this bug has been to use pci=nomsi on the dom0 kernel cmdline, but it would be better to apply the actual fix to the xen kernel in lenny. More information on xen-devel (archives). -- Pasi

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Hi, I set the severity to important as it seems that current xen tools does not allow to load amd64 Debian kernel in DomU. I also put the debian-kernel ML in CC as I'm not sure the problem comes from xen tools or the kernel itself. Here is my configuration: Hypervisor: xen-hypervisor-3.2-1-amd64 3.2.1-2

Hello, maybe I''m stupid but I find no way to have the kernel in Dom0 instead of DomU for Centos 5. Here is what I did: Regular Centos 5 Dom0 install, then creating a LVM group (vms) and install DomU with virt-install works perfectly: virt-install --p --location=http://mirrors.kernel.org/centos/5/os/i386 --file=/dev/vms/centos5_data --name=centos5 --ram=512 --nographics I get a

Hi, I recently compiled a Xen-4.0.1 and pv-ops Dom0 2.6.32.27 kernel from JF''s tree.Where my hypervisor could not boot and unfortunately the system is rebooting so frequently that I am not able to note down the error messages on a paper and pencil.So now I am planning to go for a non pv-ops Dom0.I am not clear as what should be the approach? I have been Googling it every now and then and

Processing commands for control@bugs.debian.org: > severity 384638 important Bug#384638: Dom0 dows not boot with kernel package linux-image-2.6.16-2-xen-686 version 2.6.16-18 Severity set to `important' from `critical' > reassign 384638 xen-3.0 Bug#384638: Dom0 dows not boot with kernel package linux-image-2.6.16-2-xen-686 version 2.6.16-18 Bug reassigned from package

On Sun, 2014-06-15 at 13:35 +0200, lee wrote: > Ian Campbell <ijc at hellion.org.uk> writes: > > > On Sun, 2014-06-15 at 11:03 +0200, lee wrote: > >> Hi, > >> > >> how could I get better debugging output from the dom0 kernel? > > > > Either configure a serial console [0] or add "noreboot" to your > > *hypervisor* command