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. 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. Xen: 3.4.3 (I need to stick with 3.4.x. 3.4.3 is the one that can run pvops) *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. 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. *Second approach:* Then I switched to the forward ported 2.6.32.13 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. 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. * *BTW. I dont see a PARAVIRT_GUEST config option in the forward ported 2.6.32 kernel*. *Any ideas? Thanks in advance!* * _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-Jun-17 01:29 UTC
Re: [Xen-users] Problems with xen and linux 2.26.32 kernels
On Thu, Jun 17, 2010 at 1:51 AM, Jia Rao <rickenrao@gmail.com> wrote:> 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.You didn''t mention which distro/version you use.> > 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.Any particular reason wanting to use 2.6.32? IMHO, the most "stable" kernel-xen version out there is still currently RHEL''s 2.6.18 kernel (although it''s missing some of newer Xen features)> > > Xen: 3.4.3 (I need to stick with 3.4.x. 3.4.3 is the one that can run pvops)You might want to try Xen 4.0. 3.4.3 might not have all the support needed to run 2.6.32 kernel: http://lists.xensource.com/archives/html/xen-users/2010-05/msg00879.html> > 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.Did you actually have it built in? Missing usb modules are usually OK, missing disk drivers are not.> 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.It''s best to start with known good kernel config (in my case it was 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 2.6.32.13 pv_ops, on top of RHEL5, which works fine: http://pastebin.com/5L44xXQj> > Second approach: > Then I switched to the forward ported 2.6.32.13 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.Any particular reason to switch domU to 2.6.32 as well?> 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.It depends on kernel config and distro. 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. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Jun 16, 2010 at 9:29 PM, Fajar A. Nugraha <fajar@fajar.net> wrote:> On Thu, Jun 17, 2010 at 1:51 AM, Jia Rao <rickenrao@gmail.com> wrote: > > 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. > > You didn''t mention which distro/version you use. > > > > > 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. > > Any particular reason wanting to use 2.6.32? IMHO, the most "stable" > 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> > > > > > > Xen: 3.4.3 (I need to stick with 3.4.x. 3.4.3 is the one that can run > pvops) > > You might want to try Xen 4.0. 3.4.3 might not have all the support > needed to run 2.6.32 kernel: > http://lists.xensource.com/archives/html/xen-users/2010-05/msg00879.html > > > > > 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. > > Did you actually have it built in? Missing usb modules are usually OK, > missing disk drivers are not.> > 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. > > It''s best to start with known good kernel config (in my case it was > 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 2.6.32.13 pv_ops, on top of RHEL5, which works fine: > http://pastebin.com/5L44xXQj > > > > > Second approach: > > Then I switched to the forward ported 2.6.32.13 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. > > Any particular reason to switch domU to 2.6.32 as well? >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 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. > > It depends on kernel config and distro. > > 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. > > -- > Fajar >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-Jun-17 02:09 UTC
Re: [Xen-users] Problems with xen and linux 2.26.32 kernels
On Thu, Jun 17, 2010 at 8:54 AM, Jia Rao <rickenrao@gmail.com> wrote:> I am wondering if it is the problem of centos (RHEL5) with the new kernel.Probably. Although it worked fine on my setup.> 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.If youse RHEL/Centos5, you might want to try my kernel config. I use it with Xen 4.0 from gitco, and it''s tested to work with both PV and HVM guest (with GPLPV). -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
You mean the config you just mentioned? I found it is for 2.6.32.13, but the stable-2.6.32.x has 2.6.32.15 kernel. Can I also use the config ? On Wed, Jun 16, 2010 at 10:09 PM, Fajar A. Nugraha <fajar@fajar.net> wrote:> On Thu, Jun 17, 2010 at 8:54 AM, Jia Rao <rickenrao@gmail.com> wrote: > > I am wondering if it is the problem of centos (RHEL5) with the new > kernel. > > Probably. Although it worked fine on my setup. > > > 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. > > If youse RHEL/Centos5, you might want to try my kernel config. I use > it with Xen 4.0 from gitco, and it''s tested to work with both PV and > HVM guest (with GPLPV). > > -- > Fajar >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-Jun-17 02:18 UTC
Re: [Xen-users] Problems with xen and linux 2.26.32 kernels
On Thu, Jun 17, 2010 at 9:15 AM, Jia Rao <rickenrao@gmail.com> wrote:> You mean the config you just mentioned? I found it is for 2.6.32.13, but the > stable-2.6.32.x has 2.6.32.15 kernel. Can I also use the config ?I haven''t tested it, but it should work since the version is close enough. Put it as .config on 2.6.32.15 directory, and run "make menuconfig". It should fill out missing new values automatically, plus give you the chance to review the current config. Exit and save the config, and you should be ready. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Finally the 2.6.32 pvops dom0 booted with xen 4.0. However the xend can not start. I believe that is something related to the *evtchn*. I compile the CONFIG_XEN_DEV_EVTCHN=y in kernel, so i donot need to load it. When the dom0 booted, I can see there is a entry for evtchn in /dev/xen along with gntdev. But when xend starts, the evtchn in /dev/xen disappeared. and xend is not properly started. The error log in /var/log/xen/xend.log is the following: [2010-06-18 10:51:35 4685] INFO (SrvDaemon:332) Xend Daemon started [2010-06-18 10:51:35 4685] INFO (SrvDaemon:336) Xend changeset: unavailable. [2010-06-18 10:51:35 4685] ERROR (SrvDaemon:349) Exception starting xend ((111, ''Connection refused'')) I am using a centos 5, which has an old udev. I tried to modified the udev rules in /etc/udev/rules.d/xen-backend.rules and changed evtchn to xen-evtchn. No luck. Any ideas? Thanks. On Wed, Jun 16, 2010 at 10:18 PM, Fajar A. Nugraha <fajar@fajar.net> wrote:> On Thu, Jun 17, 2010 at 9:15 AM, Jia Rao <rickenrao@gmail.com> wrote: > > You mean the config you just mentioned? I found it is for 2.6.32.13, but > the > > stable-2.6.32.x has 2.6.32.15 kernel. Can I also use the config ? > > I haven''t tested it, but it should work since the version is close > enough. Put it as .config on 2.6.32.15 directory, and run "make > menuconfig". It should fill out missing new values automatically, plus > give you the chance to review the current config. Exit and save the > config, and you should be ready. > > -- > Fajar >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users