Hi s10,
I know, but we never hit the deadlock they had fixed by the revert in Artful
AFAIK.
We followed the revert in the code for Bionic, but not yet intended to SRU the
revert to Artful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Upstream reverted this fix:
https://github.com/libvirt/libvirt/commit/72adaf2f10509c3682f2c65ffad4176e00e5a2fb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582990
Title:
internal error: End of
One has to be clear - any case where qemu stops executing in an unexpected way
make libvirt go "huh ?" and this is that message.
Please be careful that having the same "message" does not imply the same error
other than "qemu went away" which can be for various reasons.
There was some activity
I met the same bug.
Aug 10 08:01:41 controller libvirtd[12421]: internal error: End of file from
monitor
Aug 10 08:23:12 controller libvirtd[12421]: internal error: End of file from
monitor
Aug 10 08:24:06 controller libvirtd[12421]: internal error: End of file from
monitor
Aug 10 08:25:54
Great; then it feels like it's ready for upstream review.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582990
Title:
internal error: End of file from monitor
To manage notifications
On Wed, Mar 8, 2017 at 2:01 AM, Seth Arnold <1582...@bugs.launchpad.net>
wrote:
> Is the bool getting the
> correct initial value due to a 'memset 0' when the struct is
> initialized? Or does this also need an explicit initializer?
>
Hi,
as always in libvirt things are a bit more abstracted.
Christian, many thanks for tracking this down. Is the bool getting the
correct initial value due to a 'memset 0' when the struct is
initialized? Or does this also need an explicit initializer?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582990
Title:
internal error: End of file from monitor
To manage notifications about this bug go to:
Do you think it makes sense suggesting that upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582990
Title:
internal error: End of file from monitor
To manage notifications about this bug
Reproducable with current upstream (3.2 in development)
Note that on newer versions with full virtlogd there also is a similar message
from that:
virtlogd[19517]: End of file while reading data: Input/output error
There is some side effect that makes this slightly less straight forward.
If the
The following patch (so far RFC level) would avoid the error for all
qemu shutdown modes supported (acpi and agent).
I checked that:
- no error message on acpi shutdown
- no error message on agent shutdown
- still reports the error when the guest is killed from "other sources" (we
want that).
-
On ther per guest qemu log one always can see:
2017-03-07 08:59:35.748+: shutting down
Then libvirt throws
Mär 07 09:59:35 lap libvirtd[3023]: internal error: End of file from monitor
It seems even on a clean shutdown I see before a kill signal like:
qemu-system-x86_64: terminating on signal
Not an excuse at all, but a statement of overall status - I checked a
few other distros (Redhat, IBMKVM, Suse) as far as I could see they all
have the same
I'm analyzing the case at the moment (will post on that later) and I
think I have found a place where once could tweak, but it seems to be
Hmm, this seems to be a non Fatal error.
After explicitly looking for it I see this up to (including) zesty.
Slight change in the Text: "End of file from qemu monitor"
Which is as before +qemu
This seems to be part of a normal non-error guest shutdown phase:
dnsmasq-dhcp[5221]:
This was still happening as of mid-february 2017:
Feb 24 20:34:45 hunt libvirtd[3871]: internal error: End of file from
monitor
$ dpkg -l libvirt-bin qemu-kvm | cat
...
ii libvirt-bin1.3.1-1ubuntu10.8 amd64programs for the libvirt
library
ii qemu-kvm
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582990
Title:
internal error: End of file from monitor
To manage notifications
See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785011
Debian Bug report logs - #785011 libvirtd: log error message after successfully
terminating machine
** Bug watch added: Debian Bug tracker #785011
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785011
--
You received this bug
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582990
Title:
internal error: End of file from monitor
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582990
Title:
19 matches
Mail list logo
