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.
Created attachment 1268910[details]
libvirtd.log on source and target host, qemu log on target host
Description of problem:
Libvirtd can not report clear error when migration start but failed with some reason.
Version-Release number of selected component (if applicable):
libvirt-3.2.0-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Prepare guest xml with unix guest agent, and specify the socket path :
<channel type='unix'>
<source mode='bind' path='/test/agent'/>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<address type='virtio-serial' controller='0' bus='0' port='2'/>
</channel>
2.# mkdir /test
3. Change the owner and selinux context of the directory:
# chown qemu:qemu /test
# chcon system_u:object_r:qemu_var_run_t:s0 /test/
4. Define&start guest:
# virsh define rhel7.3-min.xml
# virsh start rhel7.3-min
5.Do migration:
# virsh migrate rhel7.3-min qemu+ssh://10.66.4.148/system --live --verbose --migrateuri tcp://10.66.4.148
root.4.148's password:
error: invalid argument: monitor must not be NULL
Actual results:
Migration failed with unclear error.
Expected results:
Migration failed with error:
error: internal error: process exited while connecting to monitor: 2017-04-05T05:43:26.542618Z qemu-kvm: -chardev socket,id=charchannel1,path=/test/agent,server,nowait: Failed to bind socket to /test/agent: No such file or directory
Additional info:
1.Check the libvirtd.log on source host, could see the migration has started;
2.The issue can also reproduced with other scenario, such as the source file not found on the target host;
3.It works well with libvirt-3.1.0-2.el7.x86_64
(In reply to Jiri Denemark from comment #2)
> The most important log file "libvirtd.log-target" is empty...
Sorry, I uploaded the libivrtd.log on target host again.
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/RHEA-2017:1846
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/RHEA-2017:1846
Created attachment 1268910 [details] libvirtd.log on source and target host, qemu log on target host Description of problem: Libvirtd can not report clear error when migration start but failed with some reason. Version-Release number of selected component (if applicable): libvirt-3.2.0-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Prepare guest xml with unix guest agent, and specify the socket path : <channel type='unix'> <source mode='bind' path='/test/agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> 2.# mkdir /test 3. Change the owner and selinux context of the directory: # chown qemu:qemu /test # chcon system_u:object_r:qemu_var_run_t:s0 /test/ 4. Define&start guest: # virsh define rhel7.3-min.xml # virsh start rhel7.3-min 5.Do migration: # virsh migrate rhel7.3-min qemu+ssh://10.66.4.148/system --live --verbose --migrateuri tcp://10.66.4.148 root.4.148's password: error: invalid argument: monitor must not be NULL Actual results: Migration failed with unclear error. Expected results: Migration failed with error: error: internal error: process exited while connecting to monitor: 2017-04-05T05:43:26.542618Z qemu-kvm: -chardev socket,id=charchannel1,path=/test/agent,server,nowait: Failed to bind socket to /test/agent: No such file or directory Additional info: 1.Check the libvirtd.log on source host, could see the migration has started; 2.The issue can also reproduced with other scenario, such as the source file not found on the target host; 3.It works well with libvirt-3.1.0-2.el7.x86_64