Displaying 6 results from an estimated 6 matches for "virstoragefilebackendfilereadhead".
Did you mean:
virstoragefilebackendfilereadheader
2015 Apr 29
1
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
...ah. Your debug symbols aren't enough to give a full stack trace - what
> I was really looking for was those things marked as ??.
>
> However, your debug output shows several things leading up tothe
> qemuProcessStop that might have been the reason for it being called:
>
> 1) virStorageFileBackendFileReadHeader() complains that there is no
> medium in /dev/sr0 (i.e. no disk in the CD drive) (this was actually in
> your much more abbreviated log in an earlier message, but for some
> reason I skipped over it :-/)
>
> 2) libvirt sends the following command to qemu:
>
>
> {"...
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.
.../lib64/libc.so.6
> (gdb)
Bah. Your debug symbols aren't enough to give a full stack trace - what
I was really looking for was those things marked as ??.
However, your debug output shows several things leading up tothe
qemuProcessStop that might have been the reason for it being called:
1) virStorageFileBackendFileReadHeader() complains that there is no
medium in /dev/sr0 (i.e. no disk in the CD drive) (this was actually in
your much more abbreviated log in an earlier message, but for some
reason I skipped over it :-/)
2) libvirt sends the following command to qemu:
{"execute":"block-commit",...
2015 Apr 21
2
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
...be true.
> If not, then something is wrong.
>
Here are the logs from the vm:
2015-04-20 23:50:20.387+0000: shutting down
qemu: terminating on signal 15 from pid 25298
And part of the logs from libvirt when I started it. Does this help at all?
2015-04-20 23:50:20.387+0000: 25373: error :
virStorageFileBackendFileReadHeader:1443 : Failed to open file
'/dev/sr0': No medium found
2015-04-20 23:50:20.387+0000: 25373: debug :
virStorageFileReadHeader:2714 : read of storage header 0x7fb8cc0d75f0:
ret=-1
2015-04-20 23:50:20.387+0000: 25373: debug :
virStorageFileBackendFileDeinit:1369 : deinitializing...
2015 Apr 21
0
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
...g.
>>
> Here are the logs from the vm:
>
> 2015-04-20 23:50:20.387+0000: shutting down
> qemu: terminating on signal 15 from pid 25298
>
> And part of the logs from libvirt when I started it. Does this help at all?
>
> 2015-04-20 23:50:20.387+0000: 25373: error :
> virStorageFileBackendFileReadHeader:1443 : Failed to open file
> '/dev/sr0': No medium found
> 2015-04-20 23:50:20.387+0000: 25373: debug :
> virStorageFileReadHeader:2714 : read of storage header 0x7fb8cc0d75f0:
> ret=-1
> 2015-04-20 23:50:20.387+0000: 25373: debug :
> virStorageFileBackendFil...
2015 Apr 21
2
QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
List,
I was under the impression that I could restart libvirtd without it
destroying my VMs, but am not finding that to be true. When I killall
libvirtd then my VM's keep running, but then when I start libvirtd it
calls qemuDomainObjEndJob:1542 : Stopping job: modify (async=none
vm=0x7fb8cc0d8510 name=test) and my domain gets whacked.
Any way to disable this behavior?
Also, while I'm