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.
Bug 1113668 - libvirt failed to start a domain with unix+guestfwd channel
Summary: libvirt failed to start a domain with unix+guestfwd channel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Martin Kletzander
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1112066
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-26 15:07 UTC by Martin Kletzander
Modified: 2015-03-05 07:40 UTC (History)
5 users (show)

Fixed In Version: libvirt-1.2.7-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1112066
Environment:
Last Closed: 2015-03-05 07:40:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0323 0 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2015-03-05 12:10:54 UTC

Description Martin Kletzander 2014-06-26 15:07:39 UTC 
+++ This bug was initially created as a clone of Bug #1112066 +++

Description of problem:
libvirt failed to start a domain with unix+guestfwd channel

Version-Release number of selected component (if applicable):
libvirt-0.10.2-38.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.428.el6.x86_64
kernel-2.6.32-468.el6.x86_64

How reproducible:
100%

Steps to Reproduce:

[root@rhel6 ~]# virsh dumpxml r7 | grep channel -A5
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/foo'/>
      <target type='guestfwd' address='127.0.0.1' port='2445'/>
    </channel>
...
[root@rhel6 ~]# virsh start r7
error: Failed to start domain r7
error: internal error process exited while connecting to monitor: 2014-06-19T09:02:41.371927Z qemu-kvm: -netdev user,guestfwd=tcp:127.0.0.1:2445,chardev=charchannel0,id=user-channel0: Invalid parameter 'chardev'

Actual results:
As shown above step.

Expected results:
Domain should be started successfully.

--- Additional comment from Martin Kletzander on 2014-06-26 10:57:46 EDT ---

Fixed upstream with v1.2.6-rc1-12-g39931f5:

commit 39931f5ee8314137dba453bad9742310fc275f5b
Author: Martin Kletzander <mkletzan>
Date:   Thu Jun 26 16:09:46 2014 +0200

    qemu: fix guestfwd chardev option back how it was
Comment 3 Hu Jianwei 2014-11-13 03:28:45 UTC 
The bug has been fixed.

[root@ibm-x3850x5-06 ~]# rpm -q libvirt kernel
libvirt-1.2.8-6.el7.x86_64
kernel-3.10.0-187.el7.x86_64

[root@ibm-x3850x5-06 ~]# virsh dumpxml r7 | grep "/channel" -B3
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/foo'/>
      <target type='guestfwd' address='10.0.2.9' port='2445'/>
    </channel>
[root@ibm-x3850x5-06 ~]# virsh start r7
Domain r7 started

[root@ibm-x3850x5-06 ~]# ps aux | grep qemu-kvm
qemu     14241 99.6  0.1 1717284 33644 ?       Sl   11:22   0:02 /usr/libexec/qemu-kvm -name r7 -S -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid a70da21c-ffe1-4dca-b348-62e44035a6b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/r7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device ahci,id=ahci0,bus=pci.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/var/lib/libvirt/images/r7.img,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fds=23:24,id=hostnet0,vhost=on,vhostfds=25:26 -device virtio-net-pci,mq=on,vectors=6,netdev=hostnet0,id=net0,mac=52:54:00:e5:fa:de,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/foo,server,nowait -netdev user,guestfwd=tcp:10.0.2.9:2445-chardev:charchannel0,id=user-channel0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
root     14251  0.0  0.0 112640   964 pts/2    S+   11:22   0:00 grep --color=auto qemu-kvm
[root@ibm-x3850x5-06 ~]#
Comment 4 Hu Jianwei 2014-11-28 05:36:41 UTC 
According to comment 3, move to Verified.
Comment 6 errata-xmlrpc 2015-03-05 07:40:29 UTC 
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/RHSA-2015-0323.html
Note You need to log in before you can comment on or make changes to this bug.