Ardalan K
2005-Jul-10 19:21 UTC
[Xen-users] problem in booting additional domains: "Error: Adding extent to vbd failed: error 8"
Hi, After I run "xm create dom1conf -c" I get the following error: Using config file "/etc/xen/dom1conf". Error: Adding extent to vbd failed: device (vbd (uname phy:xen/dom1root) (dev sda1) (mode w)), error 8 I am running Suse 9.0 and dom1root is the logical volume I created for domain 1. My config file is as follows: kernel = "/boot/vmlinuz-2.6.11-xenU" memory = 64 name = "dom1" disk = [ ''phy:xen/dom1root,hda1,w'' ] root = "/dev/hda1 ro" extra = "4" Any idea what the problem might be? Thanks in advance __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Marcus Brown
2005-Jul-11 02:16 UTC
Re: [Xen-users] problem in booting additional domains: "Error: Adding extent to vbd failed: error 8"
Hi, I believe you need to specify the full name of the device node, like disk = [ ''phy:/dev/xen/dom1root,hda1,w'' ] (I assume ''xen'' is your volume group name) Marcus. Ardalan K wrote:>Hi, > >After I run "xm create dom1conf -c" I get the >following error: >Using config file "/etc/xen/dom1conf". >Error: Adding extent to vbd failed: device (vbd (uname >phy:xen/dom1root) (dev sda1) (mode w)), error 8 > >I am running Suse 9.0 and dom1root is the logical >volume I created for domain 1. > >My config file is as follows: >kernel = "/boot/vmlinuz-2.6.11-xenU" >memory = 64 >name = "dom1" >disk = [ ''phy:xen/dom1root,hda1,w'' ] >root = "/dev/hda1 ro" >extra = "4" > >Any idea what the problem might be? >Thanks in advance > > >__________________________________________________ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around >http://mail.yahoo.com > >_______________________________________________ >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
Ardalan K
2005-Jul-11 20:10 UTC
Re: [Xen-users] problem in booting additional domains: "Error: Adding extent to vbd failed: error 8"
Thanks Marcus, I had tried what you said and that had given me the same error. By the way, the documentation section of xen (section 5.3) also does n''t put /dev. I think my problem with LVM originates from the fact that domain0 does n''t have LVM modules. It gives me the following error "LVM driver/module not loaded?". I don''t have this problem when I boot with the plain Linux option from Grub and that''s how I set up these logical volumes. I tried to configure linux-2.6.11-xen0 (assuming this is the domain0 kernel) to have all the LVM and sound modules that my Suse 9.0 has but after I boot with xen, domain0 still does n''t recognize LVM and my sound card. Please tell me if I am configuring the wrong kernel or if I am doing something wrong. Should I include these modules as part of kernel(not as modules)? Do I have the right initrd? Finally, I gave up on LVM and tried exporting physical devices (my hda7 partition) as VBD AND THAT WORKED! :D I appreciate if anyone can tell me how I can get LVM/sound working. Regards, Ardalan --- Marcus Brown <marcusbrutus@internode.on.net> wrote:> Hi, > > I believe you need to specify the full name of the > device node, like > > disk = [ ''phy:/dev/xen/dom1root,hda1,w'' ] > > (I assume ''xen'' is your volume group name) > > Marcus. > > Ardalan K wrote: > > >Hi, > > > >After I run "xm create dom1conf -c" I get the > >following error: > >Using config file "/etc/xen/dom1conf". > >Error: Adding extent to vbd failed: device (vbd > (uname > >phy:xen/dom1root) (dev hda1) (mode w)), error 8 > > > >I am running Suse 9.0 and dom1root is the logical > >volume I created for domain 1. > > > >My config file is as follows: > >kernel = "/boot/vmlinuz-2.6.11-xenU" > >memory = 64 > >name = "dom1" > >disk = [ ''phy:xen/dom1root,hda1,w'' ] > >root = "/dev/hda1 ro" > >extra = "4" > > > >Any idea what the problem might be? > >Thanks in advance > > > > > >__________________________________________________ > >Do You Yahoo!? > >Tired of spam? Yahoo! Mail has the best spam > protection around > >http://mail.yahoo.com > > > >_______________________________________________ > >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 >____________________________________________________ Sell on Yahoo! Auctions no fees. Bid on great items. http://auctions.yahoo.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Marcus Brown
2005-Jul-11 23:34 UTC
Re: [Xen-users] problem in booting additional domains: "Error: Adding extent to vbd failed: error 8"
Hi, Sounds like you''ve answered your own question! :) No LVM support in your kernel? Check to see if the device mapper is enabled in your .config. Here''s a snippet from mine: # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=y # CONFIG_MD_LINEAR is not set CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y # CONFIG_MD_RAID10 is not set CONFIG_MD_RAID5=y # CONFIG_MD_RAID6 is not set # CONFIG_MD_MULTIPATH is not set # CONFIG_MD_FAULTY is not set CONFIG_BLK_DEV_DM=y # CONFIG_DM_CRYPT is not set CONFIG_DM_SNAPSHOT=y CONFIG_DM_MIRROR=y # CONFIG_DM_ZERO is not set It seems that you''ve compiled these as modules, and if your root is on LVM (and no initrd) then the kernel has no way of loading the modules. The simplest way is to just compile all the modules you need directly into the kernel. Regarding sound, I''ve enabled my kernel for sound but haven''t got around to testing it yet. The modules load, however, and an lspci in dom0 shows the card. Marcus Ardalan K wrote:>Thanks Marcus, >I had tried what you said and that had given me the >same error. By the way, the documentation section of >xen (section 5.3) also does n''t put /dev. I think my >problem with LVM originates from the fact that domain0 >does n''t have LVM modules. It gives me the following >error "LVM driver/module not loaded?". I don''t have >this problem when I boot with the plain Linux option >from Grub and that''s how I set up these logical >volumes. I tried to configure linux-2.6.11-xen0 >(assuming this is the domain0 kernel) to have all the >LVM and sound modules that my Suse 9.0 has but after I >boot with xen, domain0 still does n''t recognize LVM >and my sound card. Please tell me if I am configuring >the wrong kernel or if I am doing something wrong. >Should I include these modules as part of kernel(not >as modules)? Do I have the right initrd? Finally, I >gave up on LVM and tried exporting physical devices >(my hda7 partition) as VBD AND THAT WORKED! :D > >I appreciate if anyone can tell me how I can get >LVM/sound working. > >Regards, >Ardalan > >--- Marcus Brown <marcusbrutus@internode.on.net> >wrote: > > > >>Hi, >> >>I believe you need to specify the full name of the >>device node, like >> >>disk = [ ''phy:/dev/xen/dom1root,hda1,w'' ] >> >>(I assume ''xen'' is your volume group name) >> >>Marcus. >> >>Ardalan K wrote: >> >> >> >>>Hi, >>> >>>After I run "xm create dom1conf -c" I get the >>>following error: >>>Using config file "/etc/xen/dom1conf". >>>Error: Adding extent to vbd failed: device (vbd >>> >>> >>(uname >> >> >>>phy:xen/dom1root) (dev hda1) (mode w)), error 8 >>> >>>I am running Suse 9.0 and dom1root is the logical >>>volume I created for domain 1. >>> >>>My config file is as follows: >>>kernel = "/boot/vmlinuz-2.6.11-xenU" >>>memory = 64 >>>name = "dom1" >>>disk = [ ''phy:xen/dom1root,hda1,w'' ] >>>root = "/dev/hda1 ro" >>>extra = "4" >>> >>>Any idea what the problem might be? >>>Thanks in advance >>> >>> >>>__________________________________________________ >>>Do You Yahoo!? >>>Tired of spam? Yahoo! Mail has the best spam >>> >>> >>protection around >> >> >>>http://mail.yahoo.com >>> >>>_______________________________________________ >>>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 >> >> >> > > > > >____________________________________________________ >Sell on Yahoo! Auctions – no fees. Bid on great items. >http://auctions.yahoo.com/ > >_______________________________________________ >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
Hi Marcus, I am amazed how you have LVM support. Because linux-2.6.11-xen0''s configuration does n''t have any module for LVM. None of the modules in xen0''s config (all those you named in your earlier email) has anything to do with LVM. I think LVM module is called lvm-mod. Could you or anyone verify for me that you have this module in your xen0 kernel? I guess this is the kernel I should look into for LVM support. Thanks --- Marcus Brown <marcusbrutus@internode.on.net> wrote:> Hi, > > Sounds like you''ve answered your own question! :) > No LVM support in your kernel? > Check to see if the device mapper is enabled in your > .config. > Here''s a snippet from mine: > # > # Multi-device support (RAID and LVM) > # > CONFIG_MD=y > CONFIG_BLK_DEV_MD=y > # CONFIG_MD_LINEAR is not set > CONFIG_MD_RAID0=y > CONFIG_MD_RAID1=y > # CONFIG_MD_RAID10 is not set > CONFIG_MD_RAID5=y > # CONFIG_MD_RAID6 is not set > # CONFIG_MD_MULTIPATH is not set > # CONFIG_MD_FAULTY is not set > CONFIG_BLK_DEV_DM=y > # CONFIG_DM_CRYPT is not set > CONFIG_DM_SNAPSHOT=y > CONFIG_DM_MIRROR=y > # CONFIG_DM_ZERO is not set > > It seems that you''ve compiled these as modules, and > if your root > is on LVM (and no initrd) then the kernel has no way > of loading the modules. > The simplest way is to just compile all the modules > you need directly into > the kernel. > > Regarding sound, I''ve enabled my kernel for sound > but haven''t got around to > testing it yet. The modules load, however, and an > lspci in dom0 shows > the card. > > Marcus > > > Ardalan K wrote: > > >Thanks Marcus, > >I had tried what you said and that had given me the > >same error. By the way, the documentation section > of > >xen (section 5.3) also does n''t put /dev. I think > my > >problem with LVM originates from the fact that > domain0 > >does n''t have LVM modules. It gives me the > following > >error "LVM driver/module not loaded?". I don''t have > >this problem when I boot with the plain Linux > option > >from Grub and that''s how I set up these logical > >volumes. I tried to configure linux-2.6.11-xen0 > >(assuming this is the domain0 kernel) to have all > the > >LVM and sound modules that my Suse 9.0 has but > after I > >boot with xen, domain0 still does n''t recognize LVM > >and my sound card. Please tell me if I am > configuring > >the wrong kernel or if I am doing something wrong. > >Should I include these modules as part of > kernel(not > >as modules)? Do I have the right initrd? Finally, I > >gave up on LVM and tried exporting physical devices > >(my hda7 partition) as VBD AND THAT WORKED! :D > > > >I appreciate if anyone can tell me how I can get > >LVM/sound working. > > > >Regards, > >Ardalan > > > >--- Marcus Brown <marcusbrutus@internode.on.net> > >wrote: > > > > > > > >>Hi, > >> > >>I believe you need to specify the full name of the > >>device node, like > >> > >>disk = [ ''phy:/dev/xen/dom1root,hda1,w'' ] > >> > >>(I assume ''xen'' is your volume group name) > >> > >>Marcus. > >> > >>Ardalan K wrote: > >> > >> > >> > >>>Hi, > >>> > >>>After I run "xm create dom1conf -c" I get the > >>>following error: > >>>Using config file "/etc/xen/dom1conf". > >>>Error: Adding extent to vbd failed: device (vbd > >>> > >>> > >>(uname > >> > >> > >>>phy:xen/dom1root) (dev hda1) (mode w)), error 8 > >>> > >>>I am running Suse 9.0 and dom1root is the logical > >>>volume I created for domain 1. > >>> > >>>My config file is as follows: > >>>kernel = "/boot/vmlinuz-2.6.11-xenU" > >>>memory = 64 > >>>name = "dom1" > >>>disk = [ ''phy:xen/dom1root,hda1,w'' ] > >>>root = "/dev/hda1 ro" > >>>extra = "4" > >>> > >>>Any idea what the problem might be? > >>>Thanks in advance > >>> > >>> > >>>__________________________________________________ > >>>Do You Yahoo!? > >>>Tired of spam? Yahoo! Mail has the best spam > >>> > >>> > >>protection around > >> > >> > >>>http://mail.yahoo.com > >>> > >>>_______________________________________________ > >>>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 > >> > >> > >> > > > > > > > > > >____________________________________________________ > >Sell on Yahoo! Auctions no fees. Bid on great > items. > >http://auctions.yahoo.com/ > > > >_______________________________________________ > >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 >__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday 14 July 2005 04:23, Ardalan K wrote:> Hi Marcus, > > I am amazed how you have LVM support. Because > linux-2.6.11-xen0''s configuration does n''t have any > module for LVM.Whats problematic about LVM? just enable it, compile a new xen0 kernel, done.> None of the modules in xen0''s config > (all those you named in your earlier email) has > anything to do with LVM.with 2.6 kernels, LVM is implemented atop the device mapper kernel modules. So you need the device mapper (DM) kernel modules, and the LVM2 userspace utilities.> I think LVM module is called > lvm-mod. Could you or anyone verify for me that you > have this module in your xen0 kernel? I guess this is > the kernel I should look into for LVM support.Yes, usually you put LVM into dom0 kernel, and then are free to export lvm LVs as virtual harddisks to the domU guests. /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users