All this time, I still haven''t managed to make a single Xen domain boot, other than domain0. I am just completely dumbfounded at the moment. I am starting the domain with the command line: xm create -c name=i1 kernel=/tmp/vmlinuz memory=64 disk=phy:/dev/hda6,hda1,w root=/dev/hda1 restart=never And all I ever get as a result is: Xen virtual console successfully installed as tty Event-channel device installed. xen_blk: Initialising virtual block device driver xen_net: Initialising virtual ethernet driver. ... VFS: Cannot open root device "hda1" or unknown-block(3,1) Please append a correct "root=" boot option My xmdefconfig is empty. I first thought it to be just a devfs problem, since I used to use devfs=mount on the command line, but upon closer inspection, it never had anything to do with it. With 2.6, hda is looked up in sysfs, and Xen should support that. My Xen things come from the 2.0.4-3 Debian packages and both dom0 and domU kernels are 2.6.10 debian kernels compiled by me. -- Naked ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> It has been my experience (as short as it is with Xen) that having devfs > built into the kernel image that is booting a domU, irregardless of > whether or not you pass devfs=nomount or not, will result in this error > message. Try compiling your domU kernel without devfs at all and see > what happens.Correct - don''t build devfs into your kernel at all if you want it to boot in a domU. Cheers, Mark> > B. > > On Tue, 2005-02-08 at 17:36, Nuutti Kotivuori wrote: > > All this time, I still haven''t managed to make a single Xen domain > > boot, other than domain0. I am just completely dumbfounded at the > > moment. > > > > I am starting the domain with the command line: > > > > xm create -c name=i1 kernel=/tmp/vmlinuz memory=64 > > disk=phy:/dev/hda6,hda1,w root=/dev/hda1 restart=never > > > > And all I ever get as a result is: > > > > Xen virtual console successfully installed as tty > > Event-channel device installed. > > xen_blk: Initialising virtual block device driver > > xen_net: Initialising virtual ethernet driver. > > ... > > VFS: Cannot open root device "hda1" or unknown-block(3,1) > > Please append a correct "root=" boot option > > > > My xmdefconfig is empty. I first thought it to be just a devfs > > problem, since I used to use devfs=mount on the command line, but upon > > closer inspection, it never had anything to do with it. With 2.6, hda > > is looked up in sysfs, and Xen should support that. > > > > My Xen things come from the 2.0.4-3 Debian packages and both dom0 and > > domU kernels are 2.6.10 debian kernels compiled by me. > > > > -- Naked > > > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/xen-devel > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
It has been my experience (as short as it is with Xen) that having devfs built into the kernel image that is booting a domU, irregardless of whether or not you pass devfs=nomount or not, will result in this error message. Try compiling your domU kernel without devfs at all and see what happens. B. On Tue, 2005-02-08 at 17:36, Nuutti Kotivuori wrote:> All this time, I still haven''t managed to make a single Xen domain > boot, other than domain0. I am just completely dumbfounded at the > moment. > > I am starting the domain with the command line: > > xm create -c name=i1 kernel=/tmp/vmlinuz memory=64 disk=phy:/dev/hda6,hda1,w root=/dev/hda1 restart=never > > And all I ever get as a result is: > > Xen virtual console successfully installed as tty > Event-channel device installed. > xen_blk: Initialising virtual block device driver > xen_net: Initialising virtual ethernet driver. > ... > VFS: Cannot open root device "hda1" or unknown-block(3,1) > Please append a correct "root=" boot option > > My xmdefconfig is empty. I first thought it to be just a devfs > problem, since I used to use devfs=mount on the command line, but upon > closer inspection, it never had anything to do with it. With 2.6, hda > is looked up in sysfs, and Xen should support that. > > My Xen things come from the 2.0.4-3 Debian packages and both dom0 and > domU kernels are 2.6.10 debian kernels compiled by me. > > -- Naked > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Tuesday 08 February 2005 03:56 pm, B.G. Bruce wrote:> It has been my experience (as short as it is with Xen) that having devfs > built into the kernel image that is booting a domU, irregardless of > whether or not you pass devfs=nomount or not, will result in this error > message. Try compiling your domU kernel without devfs at all and see > what happens.I am running with devfs compiled into the kernel without any problems.> B. > > On Tue, 2005-02-08 at 17:36, Nuutti Kotivuori wrote: > > All this time, I still haven''t managed to make a single Xen domain > > boot, other than domain0. I am just completely dumbfounded at the > > moment. > > > > I am starting the domain with the command line: > > > > xm create -c name=i1 kernel=/tmp/vmlinuz memory=64 > > disk=phy:/dev/hda6,hda1,w root=/dev/hda1 restart=neverShould the above be "/dev/hda1" instead of just "hda1"? -- Jon Mason jdmason@us.ibm.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> I am running with devfs compiled into the kernel without any problems.In your domU kernel? We''ve had more than one report of this not working at all IIRC, although it''s fine in dom0.> > > xm create -c name=i1 kernel=/tmp/vmlinuz memory=64 > > > disk=phy:/dev/hda6,hda1,w root=/dev/hda1 restart=never > > Should the above be "/dev/hda1" instead of just "hda1"?I think the tools sort that out automatically. Cheers, Mark ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Tuesday 08 February 2005 04:04 pm, Mark Williamson wrote:> > I am running with devfs compiled into the kernel without any problems. > > In your domU kernel? We''ve had more than one report of this not working at > all IIRC, although it''s fine in dom0.Oops..I only have it enabled in dom0, not domU. Sorry. -- Jon Mason jdmason@us.ibm.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
B. G. Bruce wrote:> It has been my experience (as short as it is with Xen) that having > devfs built into the kernel image that is booting a domU, > irregardless of whether or not you pass devfs=nomount or not, will > result in this error message. Try compiling your domU kernel > without devfs at all and see what happens.Ah, thanks! I remembered that advice back when talking about this whole mess earlier, but managed to forget it in the meantime. The kernel boots nicely now. -- Naked ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Mark Williamson wrote:>> I am running with devfs compiled into the kernel without any >> problems. > > In your domU kernel? We''ve had more than one report of this not > working at all IIRC, although it''s fine in dom0.Chalk one up for domU not booting with devfs ;-) (And yes, I have devfs in dom0 kernel.) -- Naked ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel