Since you''re using a 2.4 kernel, udev won''t work. If you use
a 2.6 kernel
(your dom0 kernel would do fine) you may have more luck.
Alternatively, if you really want to use 2.4, use the MAKEDEV program to
create a full set of device nodes in your image file''s /dev. Then you
shouldn''t even need an initrd to boot it.
Cheers,
Mark
On Saturday 30 April 2005 00:54, Chetan Jog wrote:> Hello All,
>
> Using FC3
> Booted in Xen...with the initrd in grub.conf to tide over the udev issue of
> Fedora Core 3
> I have created a domain with follwing parameters in my domain config file:
>
> kernel = "/boot/vmlinuz-2.4.29-xenU"
> memory = 64
> name = "enjoy1"
> nics=1
> disk = [ ''file:/root/fedora.img,hda3,w'' ]
>
> As you can see I am using freshly a created fedora.img.
>
> now it hangs at the same point (where others had pointed out it hangs when
> there was no
> initrd in the grub.conf when the system itself is booting up in Xen.)
>
> for me it hangs after i try to start the domain with
> $ xm create -c enjoy1
> .......
> .......
> .
> .
> Freeing unused kernel memory: 60k freed
> Warning: unable to open an initial console.
>
> $ xm list shows the domain enjoy1 up with the "b" flag
>
> I am not sure if it makes sense but I also tried putting
> Initrd = "/root/initrd-fc3.img"
> in the domain config ....unfortunately it makes no difference.
>
> Would appreciate if someone give me some ideas or pointers.
>
> thanks !
> C. Jog
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users