Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When upgrading libvirt to the latest release we had a spate of Ubuntu guests
that were terminated by the new libvirt process. It turns out that these guests had previously received a reboot event from libvirt.
Version-Release number of selected component (if applicable):
libvirt version: 0.10.2, package: 46.el6_6.2
How reproducible:
Steps to Reproduce:
1. Create a transient Ubuntu VM along the lines of attached XML
2. virsh reboot <vm name>
3. Once the server has restarted: /sbin/service libvirtd condrestart
Actual results:
The rebooted server is terminated with signal 15 by the new libvirt daemon. All others remain untouched.
Expected results:
No running servers should be affected by a libvirt restart.
Additional info:
libvirt log contains:
2014-12-01 14:47:18.610+0000: 23716: info : libvirt version: 0.10.2, package: 46.el6_6.2 (Scientific Linux, 2014-11-18-14:07:51, sl6.fnal.gov)
2014-12-01 14:47:18.610+0000: 23716: error : qemuMonitorIO:615 : internal error End of file from monitor
qemu log for server contains:
qemu: terminating on signal 15 from pid 23716
2014-12-01 14:47:18.611+0000: shutting down
2014-12-01 14:51:53.612+0000: starting up
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name srv-5f2yv,process=qemu:srv-5f2yv -S -M rhel6.5.0 -cpu Westmere,+rdtscp,+pdpe1gb,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -enable-kvm -m 512 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 80297423-74ca-61c6-6e43-654ca26a347f -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/srv-5f2yv.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/servers/srv-5f2yv-vol,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,ioeventfd=on,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=67,id=hostnet0,vhost=on,vhostfd=68 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:24:19:f1:c0:62,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:59051,password -k en-gb -vga cirrus -device i6300esb,id=watchdog0,bus=pci.0,addr=0x6 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
char device redirected to /dev/pts/34
I could reproduce this bug with libvirt-46.el6_6.2, the reproduce steps as following
1.Create a guest with the guest's xml
#virsh create rhel6
2.Reboot the guest while the guest start completly
#virsh reboot rhel6
3.Restart the libvirtd with the following command while the guest restart(better run the command after the guest finsh shutdown and in the process of re-start)
#/sbin/service libvirtd condrestart
4.Re-check the guest, found the guest desapear
# virsh list
Id Name State
----------------------------------------------------
#
#ps aux|grep qemu
#cat /var/log/libvirt/qemu/rhel6.log
--
qemu: terminating on signal 15 from pid 5028
2015-02-06 06:13:47.476+0000: shutting down
#cat /var/lib/libvirt/libvirtd.log
2015-02-06 06:13:47.476+0000: 5028: info : libvirt version: 0.10.2, package: 46.el6_6.2 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-11-07-08:34:58, x86-029.build.eng.bos.redhat.com)
2015-02-06 06:13:47.476+0000: 5028: error : qemuMonitorIO:615 : internal error End of file from monitor
Verify the bug with libvirt-0.10.2-48.el6, the guest didn't disapper after step 3 in the reproduce steps
#virsh create rhel6
# virsh reboot rhel6
Domain rhel6 is being rebooted
# /sbin/service libvirtd condrestart
Stopping libvirtd daemon: [ OK ]
Starting libvirtd daemon: [ OK ]
# virsh list
Id Name State
----------------------------------------------------
1 rhel6 running
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-1252.html