Displaying 3 results from an estimated 3 matches for "devicenotfound".
2015 Apr 29
1
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
...;
> {"execute":"block-commit","arguments":{"device":"bogus"},"id":"libvirt-4"}
>
> and gets back this error:
>
> {"id": "libvirt-4",
> "error": {"class": "DeviceNotFound", "desc": "Device 'bogus' not found"}}
>
> Since (1) actually generates a libvirt error log, that is what I would
> look into first.
>
Thanks Laine,
Confirmed, if I:
virsh attach-disk test '' hdc --type cdrom
Then I can kick libvirtd all I...
2015 Apr 28
2
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
On 04/22/2015 08:19 AM, Laine Stump wrote:
> If you're compiling yourself, then you should be all set to run under
> gdb. libvirt-debuginfo is just a separate subpackage that contains all
> the symbol and line number info from the build so that backtraces in
> gdb make sense. Try attaching gdb to the libvirtd process and do
> something like "thread apply all bt" - if
2015 Apr 29
0
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
...the following command to qemu:
{"execute":"block-commit","arguments":{"device":"bogus"},"id":"libvirt-4"}
and gets back this error:
{"id": "libvirt-4",
"error": {"class": "DeviceNotFound", "desc": "Device 'bogus' not found"}}
Since (1) actually generates a libvirt error log, that is what I would
look into first.