Displaying 2 results from an estimated 2 matches for "wasvirt1".
2015 Apr 21
2
QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
...dify (async=none
vm=0x7fb8cc0d8510 name=test) and my domain gets whacked.
Any way to disable this behavior?
Also, while I'm at it, due to issues with snapshotting, I ended up with
two domains where libvirt insists the disk source is incorrect which
causes many things to break like this:
root@wasvirt1:/etc/libvirt# virsh domblklist wasdev
Target Source
------------------------------------------------
vda /glustervol1/vm/wasdev/wasdev.reboot
hdc /dev/sr0
Yet:
root@wasvirt1:/etc/libvirt# lsof | grep wasdev
2235 /usr/bin/qemu-system-x86_64 /var/log/libvirt/qemu/wasdev.log...
2015 Apr 21
0
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
...disable this behavior?
Whatever the bug is causing this to happen, fix it :-)
>
> Also, while I'm at it, due to issues with snapshotting, I ended up with
> two domains where libvirt insists the disk source is incorrect which
> causes many things to break like this:
>
> root@wasvirt1:/etc/libvirt# virsh domblklist wasdev
> Target Source
> ------------------------------------------------
> vda /glustervol1/vm/wasdev/wasdev.reboot
> hdc /dev/sr0
>
> Yet:
>
> root@wasvirt1:/etc/libvirt# lsof | grep wasdev
> 2235 /usr/bin/qemu-system-...