Public bug reported: It appears as though libvirt is generating improper command-line arguments to kvm when overlays are being used. When starting a VM associated with an overlay via virsh, the VM complains that it cannot find the boot drive. Starting it manually, however, works:
Here is what I was able to do in order to boot the VM using an overlay: kvm -hda /VMs/Windows7DomainTest.ovl -m 512 -vnc 127.0.0.1:0 But here is what libvirt did: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name Windows7DomainTest -uuid a2556b35 -fe8d-303b-6cbe-fc795c647387 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/Windows7DomainTest.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=localtime -boot c -drive file=/VMs/Windows7DomainTest.ovl,if=none,id=drive- ide0-0-0,boot=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -device rtl8139,vlan=0,id=net0,mac=52:54:00:88:6b:a6,bus=pci.0,addr=0x3 -net tap,fd=35,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa- serial,chardev=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -k en-us -vga std -device virtio-balloon- pci,id=balloon0,bus=pci.0,addr=0x4 I was reading a few of the man pages and noticed that using the -boot option may be an older way of doing it so I suspect that may be the problem. However, I don't know how to make libvirt use the -hdX syntax instead. This is on Ubuntu 10.10 using libvirt 0.8.3. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/695697 Title: libvirt not working properly with overlays -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs