[libvirt][qemu] Ho to get a 'boot=on' parameter to appear on kvm command line
Hi, all. Can someone tell me how to get boot=on parameter to appear on my kvm cmdline? I define domain with the following xml <domain type="kvm"> <name>kvm-1</name> <memory>524288</memory> <vcpu>1</vcpu> <os> <type arch="x86_64" machine="pc">hvm</type> <boot dev="hd"/> </os> <devices> <emulator>/usr/bin/kvm</emulator> <graphics type="vnc" port="-1"/> <disk device="disk" type="file"> <source file="test.img"/> <target dev="sda"/> </disk> <interface type="bridge"> <source bridge="breth0"/> </interface> </devices> </domain> and get /usr/bin/kvm -S -M pc -m 512 -smp 1 -name kvm-1 -uuid b462e575-4044-146c-193a-9a70523b4258 -monitor pty -no-acpi -boot c -drive file=test.img,if=scsi,index=0 -net nic,macaddr=52:54:00:09:9b:19,vlan=0 -net tap,fd=15,vlan=0 -serial none -parallel none -usb But I want to get -drive file=test.img,if=scsi,index=0,boot=on instead.
On Wed, Jun 10, 2009 at 01:07:34PM +0400, Anton Protopopov wrote:
Hi, all.
Can someone tell me how to get boot=on parameter to appear on my kvm cmdline?
What version of KVM have you got ? There was one recent release which broke the 'boot=on' parameter.
I define domain with the following xml
<domain type="kvm"> <name>kvm-1</name> <memory>524288</memory> <vcpu>1</vcpu> <os> <type arch="x86_64" machine="pc">hvm</type> <boot dev="hd"/> </os> <devices> <emulator>/usr/bin/kvm</emulator> <graphics type="vnc" port="-1"/> <disk device="disk" type="file"> <source file="test.img"/> <target dev="sda"/> </disk> <interface type="bridge"> <source bridge="breth0"/> </interface> </devices> </domain>
and get
/usr/bin/kvm -S -M pc -m 512 -smp 1 -name kvm-1 -uuid b462e575-4044-146c-193a-9a70523b4258 -monitor pty -no-acpi -boot c -drive file=test.img,if=scsi,index=0 -net nic,macaddr=52:54:00:09:9b:19,vlan=0 -net tap,fd=15,vlan=0 -serial none -parallel none -usb
But I want to get -drive file=test.img,if=scsi,index=0,boot=on instead.
Your XML looks fine - the <boot dev='hd'/> tag should have resulted in the boot=on parameter being used on the first disk. Thus I suspect you have the broken KVM release. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
What version of KVM have you got ? There was one recent release which broke the 'boot=on' parameter.
I have kvm-85.
Your XML looks fine - the <boot dev='hd'/> tag should have resulted in the boot=on parameter being used on the first disk. Thus I suspect you have the broken KVM release.
So, should we add 'boot=on' to qemu-options.hx in our kvm package?
On Wed, Jun 10, 2009 at 02:58:11PM +0400, Anton Protopopov wrote:
What version of KVM have you got ? There was one recent release which broke the 'boot=on' parameter.
I have kvm-85.
Your XML looks fine - the <boot dev='hd'/> tag should have resulted in the boot=on parameter being used on the first disk. Thus I suspect you have the broken KVM release.
So, should we add 'boot=on' to qemu-options.hx in our kvm package?
Yeah, I believe so - check kvm-86 for the patch they applied Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
On Wed, 2009-06-10 at 14:58 +0400, Anton Protopopov wrote:
What version of KVM have you got ? There was one recent release which broke the 'boot=on' parameter. I have kvm-85.
Your XML looks fine - the <boot dev='hd'/> tag should have resulted in the boot=on parameter being used on the first disk. Thus I suspect you have the broken KVM release.
So, should we add 'boot=on' to qemu-options.hx in our kvm package?
One thing to bear in mind is that the kvm-XX releases are development snapshots, not stable releases. There's a good chance things like this will be broken in any given kvm-XX release. qemu-kvm-0.10.5 is the latest stable release. Cheers, Mark.
2009/6/10 Mark McLoughlin <markmc@redhat.com>
On Wed, 2009-06-10 at 14:58 +0400, Anton Protopopov wrote:
What version of KVM have you got ? There was one recent release which broke the 'boot=on' parameter. I have kvm-85.
Your XML looks fine - the <boot dev='hd'/> tag should have resulted in the boot=on parameter being used on the first disk. Thus I suspect you have the broken KVM release.
So, should we add 'boot=on' to qemu-options.hx in our kvm package?
One thing to bear in mind is that the kvm-XX releases are development snapshots, not stable releases. There's a good chance things like this will be broken in any given kvm-XX release.
qemu-kvm-0.10.5 is the latest stable release.
Thanks. I think we will cherry-pick only d7580e4d... for now and will not merge kvm-86 :)
Cheers, Mark.
participants (4)
-
Anton Protopopov -
Daniel Berrange -
Daniel P. Berrange
-
Mark McLoughlin