I am currently having problems persuading 3.0.4 (binary dist) to boot a
virtual machine from a virtual floppy when running in HVM mode. Although I
can boot a real computer from a real drive with my floppy image, with Xen
it merely hangs after saying:
HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
If I give it a completely blank floppy image, it does the same (I''d
expect a "not bootable" complaint), and if I point it at a floppy
image which does not exist, it produces no window at all, and is shown
in state ''------'' by "xm list", as, indeed, are the
other two.
What am I doing wrong? My minimalist configuration file reads:
kernel = "/usr/lib/xen/boot/hvmloader"
builder = ''hvm''
device_model = ''/usr/lib64/xen/bin/qemu-dm''
memory = 256
name = "floppy"
fda="/scratch/VM/FDSTD.144"
sdl=1
boot=''a''
and "xm info | grep xen"
release : 2.6.16.33-xen
xen_major : 3
xen_minor : 0
xen_extra : .4-1
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p
hvm-3.0-x86_64
xen_pagesize : 4096
xen_changeset : Mon Jan 08 14:09:25 2007 +0000 13130:4d34be661f31
xend_config_format : 3
The thing boots from hard disk images fine, happily running a 32 bit
version of Suse 9.3, and FDSTD.144 is a FreeDOS bootable disk. The
machine itself is running SLES 10.0 on a Core2, with the 2.6.16.33-xen
kernel.
With thanks for any advice,
Michael
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
