Here is the kvm command line that can boot successfully from the second
device:
usr/bin/kvm -M pc -m 128 -smp 1 -monitor pty -boot c -drive
file=/home/mathiaz/vm/tests_isos/jaunty-server-
amd64-raid1/vm//root2.qcow2,if=virtio,index=0,boot=on -drive
file=/home/mathiaz/vm/isos/9.04-20090414/jaunty-server-
amd64.iso,if=ide,media=cdrom,index=2 -net
nic,macaddr=52:54:00:a2:34:e9,vlan=0,model=virtio -net
tap,fd=10,script=,vlan=0 -usb -vnc 0.0.0.0:0
And its associated libvirt file:
<domain type='kvm'>
<name>jaunty-server-amd64-raid1</name>
<uuid>1c3d9419-3c1d-493b-9ce7-c4a3cf6d1409</uuid>
<memory>131072</memory>
<vcpu>1</vcpu>
<features>
<acpi/>
</features>
<os>
<type>hvm</type>
<boot dev='hd' />
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>reboot</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<!-- <disk type='file' device='disk'><source
file='/home/mathiaz/vm/tests_isos/jaunty-server-amd64-raid1/vm//root1.qcow2'/><target
dev='hda' bus='virtio'/></disk> -->
<disk type='file' device='disk'><source
file='/home/mathiaz/vm/tests_isos/jaunty-server-amd64-raid1/vm//root2.qcow2'/><target
dev='hda' bus='virtio'/></disk>
<disk type='file' device='cdrom'><source
file='/home/mathiaz/vm/isos/9.04-20090414/jaunty-server-amd64.iso'/><target
dev='hdc'/><readonly/></disk>
<interface type='network'>
<mac address='52:54:00:a2:34:e9'/>
<source network='default' />
<model type='virtio'/>
</interface>
<graphics type='vnc' listen='0.0.0.0'/>
</devices>
</domain>
The only difference with between the two libvirt file is the dev
attribute in the device target defintion.
--
unable to boot from the second disk of a RAID1 array - error 21
https://bugs.launchpad.net/bugs/360832
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
