Hi Bernhard,

On Friday 24 April 2009 14:56:15 Bernhard Held wrote:
> > does not boot, BIOS complains "Boot failed: could not read the boot
> > disk":
> >
> > -drive file=/dev/VolGroup00/testpart,if=virtio,index=0 \
>
> Please try with:
> -drive file=/dev/VolGroup00/testpart,if=virtio,index=0,boot=on \

That's it! With boot=on it works.

Thanks for pointing this out.

Was this change intentional? I didn't see it mentioned in the changelog and 
could not even find the "boot"-parameter in the qemu-kvm manpage.

I usually start kvm via libvirt and libvirt doesn't know anything about 
boot=on, at least not in 0.6.2. I did not have time to try 0.6.3 as it was 
released just yet.

Is there some way in a running qemu to find out if a virtio blockdevice is 
activated this way? When running "info block" I always get this result if the 
device has boot=on or not:

virtio0: type=hd removable=0 file=/dev/VolGroup00/testpart ro=0 
drv=host_device encrypted=0

Kind regards,

Gerd

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to