I haven''t been able to boot a domU using the current xen-unstable on x86 for over 2 weeks. I''m building xen and the kernels from source using the default configs. My last try was changeset 7145. dom0 boots but when I try to boot domU I don''t see any error messages but can''t connect to the console. xentop says that domU is up and using 100% CPU. Is this just part of the development cycle or is anybody else able to use the current xen-unstable? Thanks, Jeff _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 30 Sep 2005, Jeffrey Buell wrote:> I haven''t been able to boot a domU using the current xen-unstable on x86 for > over 2 weeks. I''m building xen and the kernels from source using the default > configs. My last try was changeset 7145. dom0 boots but when I try to boot > domU I don''t see any error messages but can''t connect to the console. xentop > says that domU is up and using 100% CPU. Is this just part of the > development cycle or is anybody else able to use the current xen-unstable?I tried a couple of days ago but couldn''t get a domU to run, there was a pause during the boot while trying to initialize the xen block device driver, which timed out, and then of course it couldn''t open it''s root device. There is already a buzilla call open about that. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=176 key points to me were: xen_blk: Initialising virtual block device driver xen_blk: Timeout connecting to device! <snip> VFS: Cannot open root device "hda1" or unknown-block(2,0) Please append a correct "root=" boot option that bug was closed 2005-08-25, but re-opened 10 days ago. Seems to be tagged as ''critical''. 2.0-testing runs fine on my box, which is just a pretty standard dual xeon supermicro machine... 6013pt :-) (4 gig of memory though, that might be a tich unusual.) I _really_ _really_ want to be able to run SMP guests, so I''ve been holding of on staging this box. If the developers want access, that can be arranged. -Tom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
A lot of people have been having problems lately, however, I'm happily running a 4-way guest on a build from last Sunday. If you're using loopback you need an absolute path to the file, and you need to have udev or at least hotplug scripts installed in order for the backend to be brought up. -Kip On 9/30/05, Tom Brown <tbrown@baremetal.com> wrote:> > On Fri, 30 Sep 2005, Jeffrey Buell wrote: > > > I haven't been able to boot a domU using the current xen-unstable on x86 > for > > over 2 weeks. I'm building xen and the kernels from source using the > default > > configs. My last try was changeset 7145. dom0 boots but when I try to > boot > > domU I don't see any error messages but can't connect to the console. > xentop > > says that domU is up and using 100% CPU. Is this just part of the > > development cycle or is anybody else able to use the current > xen-unstable? > > I tried a couple of days ago but couldn't get a domU to run, there was a > pause during the boot while trying to initialize the xen block device > driver, which timed out, and then of course it couldn't open it's root > device. There is already a buzilla call open about that. > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=176 > > key points to me were: > > xen_blk: Initialising virtual block device driver > xen_blk: Timeout connecting to device! > <snip> > VFS: Cannot open root device "hda1" or unknown-block(2,0) > Please append a correct "root=" boot option > > that bug was closed 2005-08-25, but re-opened 10 days ago. Seems > to be tagged as 'critical'. 2.0-testing runs fine on my box, > which is just a pretty standard dual xeon supermicro machine... > 6013pt :-) (4 gig of memory though, that might be a tich > unusual.) > > I _really_ _really_ want to be able to run SMP guests, so I've > been holding of on staging this box. If the developers want > access, that can be arranged. > > -Tom > > > > _______________________________________________ > 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
On Fri, 30 Sep 2005, Kip Macy wrote:> A lot of people have been having problems lately, however, I''m happily > running a 4-way guest on a build from last Sunday. If you''re using > loopback you need an absolute path to the file, and you need to have > udev or at least hotplug scripts installed in order for the backend to > be brought up.Nope... just a simple raw partition... I had trouble with LVM a long time ago and haven''t gone back to anything fancy... although I should for some of our stuff. kernel = "/boot/vmlinuz-2.6-xenU" memory = 256 name = "centos" disk = [ ''phy:/dev/sdd3,hda1,w'' ] root = "/dev/hda1" extra = "ro single " The box is a dual 2.8Ghz xeon, 4 gig of RAM, 4 SATA drives. I did complile my own kernel... The same config file runs fine under 2.0-testing ... (I just booted it and then had to stop to figure out why it was working -- duh, not running 2.0-unstable anymore)... (I haven''t looked at it since the 28th.) -Tom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ted Kaczmarek
2005-Oct-01 16:11 UTC
Re: [Xen-users] booting domU with current xen-unstable?
On Sat, 2005-10-01 at 01:23 -0700, Tom Brown wrote:> On Fri, 30 Sep 2005, Kip Macy wrote: > > > A lot of people have been having problems lately, however, I''m happily > > running a 4-way guest on a build from last Sunday. If you''re using > > loopback you need an absolute path to the file, and you need to have > > udev or at least hotplug scripts installed in order for the backend to > > be brought up. > > Nope... just a simple raw partition... I had trouble with LVM a long time > ago and haven''t gone back to anything fancy... although I should for some > of our stuff. > > kernel = "/boot/vmlinuz-2.6-xenU" > memory = 256 > name = "centos" > disk = [ ''phy:/dev/sdd3,hda1,w'' ] > root = "/dev/hda1" > extra = "ro single " > > The box is a dual 2.8Ghz xeon, 4 gig of RAM, 4 SATA drives. I did > complile my own kernel... The same config file runs fine under > 2.0-testing ... (I just booted it and then had to stop to figure > out why it was working -- duh, not running 2.0-unstable anymore)... > (I haven''t looked at it since the 28th.) > > -Tom > >If you want to use LVM make sure the kernel supports it, very easy to miss that setting. Also it appears you need to have scsi support in your domU as well, and whatever filesystem /dev/sdd3 make sure that domU has support for that as well. Make sure your domU''s fstab jive''s with the config. You can try ##xen on irc and put some stuff up at pastebin to get help as well. For kicks what happens if you use a loop image instead of a partition? Regards, Ted _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > > If you want to use LVM make sure the kernel supports it, very easy to > miss that setting. Also it appears you need to have scsi support in yourOh, my trouble wasn''t in configuring it, my trouble was probably LVM in dom0 running out of memory and taking the whole machine down... very annoying to say the least. The lack of concrete details on _how much_ memory dom0 required was a tad frustrating.> domU as well,I don''t believe that is true, as that would imply that your domU kernel has to change depending on whether you call the device hda1 or sdd3 ... AFAIK, the domU gets "virtual block device" support, and the parameters passed to the kernel are just labels used to find the right virtual block device(s).> and whatever filesystem /dev/sdd3 make sure that domU hasyes, obviously the domU needs to be able to understand the filesystem on the block device, but AFAIK, the problem was the timeout with the block device.> support for that as well. Make sure your domU''s fstab jive''s with the > config. You can try ##xen on irc and put some stuff up at pastebin to > get help as well. > > For kicks what happens if you use a loop image instead of a partition?dunno. The fact that the xen 2 and xen 3 kernels overwrite each other when running the install scripts makes it a tich uncomfortable to switch back and forth between versions. I''ll try to find time to check it. ---------------------------------------------------------------------- tbrown@BareMetal.com | How often I found where I should be going http://BareMetal.com/ | only by setting out for somewhere else. web hosting since ''95 | -- R. Buckminster Fuller _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users