Hi Frederick,
it depends a bit on wether you run a PVM or a HVM, but in latter case I
got very good results with booting from the mini.iso:
http://<repo>/debian/dists/etch/main/installer-i386/current/images/netboot/mini.iso
my domain.cfg:
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
device_model = ''/usr/lib/xen/bin/qemu-dm''
memory = 512
name = "vm1"
vcpus=1
pae=0
acpi=0
apic=0
cpus = ""
vif = [ ''type=ioemu, mac=aa:00:bb:cc:00:d4,
bridge=192.168.1.2'' ]
disk = [ ''file:/var/lib/xen/vm1-hda.img,ioemu:hda,w'',
''file:/var/lib/xen/debian-4.0r1-installer-gtk-netboot-mini.iso,hdc:cdrom,r''
]
on_poweroff = ''destroy''
on_reboot = ''destroy''
on_crash = ''destroy''
boot=''d''
sdl=0
vnc=1
vncviewer=0
stdvga=0
serial=''pty''
ne2000=0
usb=1
usbdevice=''tablet''
Sincerely,
Jan.
On Jan 13, 2008 9:57 AM, Frederick N. Brier <fbrier@multideck.com> wrote:
> I am trying to create a DomU Debian guest VM. I tried a Debian-Etch
> DomU from jailtime.org. Lots of my own issues, discovering other people
> having the same exact problems, but no solutions. So I installed
> debootstrap and xen-tools and tried that. Again like many other people
> I ran into the "VFS: Cannot open root device "hda1" or
> unknown-block(0,0)" issue. I have not figured out why the cfg file is
> not being generated in /etc/xen, but I have gotten it to generate images
> using the file image and LVM (creating the Logical Volumes). I just
> hand coded the cfg file. After they were generated, I mounted both
> images and noticed that neither had hda1 or hda2 device files in /dev.
> That would seem to be a problem. Please help! A link to tutorial or
> answer would be fabulous. The only thing I have not tried yet is using
> pygrub and bundling the kernel and .img files with the guest and not
> using the fc8xen kernel and images in the Dom0''s boot folder.
Thank you
> for any help.
>
> Fred
>
> --
> Fedora-xen mailing list
> Fedora-xen@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>