Re: [Xen-users] Problems with xen and linux 2.26.32 kernels
On Wed, Jun 16, 2010 at 9:29 PM, Fajar A. Nugraha <fajar@xxxxxxxxx>
You didn't mention which distro/version you use.
On Thu, Jun 17, 2010 at 1:51 AM, Jia Rao <rickenrao@xxxxxxxxx
> Hi all,
> I used to use xen 3.4.2 and linux 2.6.18-xen kernels for both dom0 and domU,
> without any problems.
Any particular reason wanting to use 2.6.32? IMHO, the most "stable"
> Recently, I need to try io bandwidth control like dm-ioband in the new
> kernel 2.6.32 (dm-ioband has patches for this kernel). It gave me a lot of
> problems if I want to upgrade the dom0 to 2.6.32. The following is what I
> tried and the errors.
kernel-xen version out there is still currently RHEL's 2.6.18 kernel
(although it's missing some of newer Xen features)
I want to try dm-ioband whose latest version has patches only for 2.6.32
You might want to try Xen 4.0. 3.4.3 might not have all the support
> Xen: 3.4.3 (I need to stick with 3.4.x. 3.4.3 is the one that can run pvops)
needed to run 2.6.32 kernel:
Did you actually have it built in? Missing usb modules are usually OK,
> First approach:
> I tried to download pvops from the git repository xen/stable-2.6.32.x. The
> compilation was OK, but the initrd has a lot missing dependencies. I tried
> to use --builtin to claim those missing modules in kernel.
missing disk drivers are not.
It's best to start with known good kernel config (in my case it was
> However, with the
> generated initrd, dom0 can not boot. I got the error: unable to locate
> IOAPIC for GSIx and mount: could not find filesystem: /dev/root.
> I enabled : CONFIG_SYSFS_DEPRECATED=y, CONFIG_SYSFS_DEPRECATED_V2=y and
> tried to use root=/dev/sdax or root=LABEL=/. No luck.
RHEL5's kernel-xen config), the add/adjust whatever's necessary in
newer kernel (including selecting pv_ops dom0 support). I use this
config on 184.108.40.206 pv_ops, on top of RHEL5, which works fine:
>Any particular reason to switch domU to 2.6.32 as well?
> Second approach:
> Then I switched to the forward ported 220.127.116.11 kernel generated from the
> gentoo xen kernel patches.
> Still xen 3.4.3. After compilation, dom0 booted successfully. However I
> previous domU which has 2.6.18-xen kernels can not boot.
I am wondering if it is the problem of centos (RHEL5) with the new
kernel. I can boot all my domUs on a machine: Xen 3.4 + 2.6.18 dom0.
When I boot the same domU under the new forward ported 2.6.32 kernel, the VM timed out and prompt:
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Probably it is the RHEL5 udev scripts that is not compatible with the new kernel.
BTW. domU still has 2.6.18 kernel, only dom0 changed.
It depends on kernel config and distro.
> It has the same
> error: mount: could not find filesystem: /dev/root
> Do I need to create a initrd for the domU? I didnt need one when dom0 is
> 2.6.18-xen kernel.
I prefer to use pygrub/pvgrub for domU kernels. That ensures domU is
somewhat independent of whatever kernel dom0 is running. In your case,
the easiest way would be to use 2.6.18-xen kernel for domU, while
using 2.6.32.x for dom0.
Xen-users mailing list