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:
Can NOT convert an existing guest to the native qemu-argv configuration format
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. List the existing vms
# virsh list --all
Id Name State
----------------------------------------------------
1 avocado-vt-vm1 running
2. Conver avocado-vt-vm1 to native qemu-argv configuration format
# virsh domxml-to-native qemu-argv --domain avocado-vt-vm1
error: Unable to bind to UNIX socket path '/var/lib/libvirt/qemu/domain--1-avocado-vt-vm1/monitor.sock': No such file or directory
Expected results:
Conversion should be successful.
Additional info:
When I tried this virsh cmd on libvirt-4.4.0-2.el7.x86_64
# virsh domxml-to-native qemu-argv --domain avocado-vt-vm1
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name guest=avocado-vt-vm1,debug-threads=on -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain--1-avocado-vt-vm1/master-key.aes .....
The conversion succeed.
We need this fix from upstream
commit 7ac08cc929dc512e8682fbfcc5d33518058f20e4
Author: Daniel P. Berrangé <berrange>
Date: Thu Jun 28 12:49:12 2018 +0100
qemu: don't use chardev FD passing with standalone args
When using domxml-to-native, we must generate CLI args that can be used
in a standalone scenario. This means no FD passing can be used. To
achieve this we must clear the QEMU_CAPS_CHARDEV_FD_PASS capability bit.
Reviewed-by: John Ferlan <jferlan>
Signed-off-by: Daniel P. Berrangé <berrange>
Verify this bug with:
libvirt-4.5.0-3.el7.x86_64
Steps to verify:
1. List the existing vms
# virsh list --all
Id Name State
----------------------------------------------------
22 win16 running
2. Conver avocado-vt-vm1 to native qemu-argv configuration format
# virsh domxml-to-native qemu-argv --domain win16
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name guest=win16,debug-threads=on -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain--1-win16/master-key.aes -machine pc-i440fx-rhel7.6.0,.....
# ps aux |grep qemu
qemu 25896 112 0.8 2717260 132536 ? Sl 18:35 0:12 /usr/libexec/qemu-kvm -name guest=win16
....
-chardev socket,id=charmonitor,fd=29,server,nowait -mon chardev=charmonitor,id=monitor
....
As the guest can be started successfully, and did not change the other functions of the guest.
Mark the bug as verified.
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://access.redhat.com/errata/RHSA-2018:3113