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.
The virtio-vsock guest drivers do not support multiple instances. I'm not aware of a use case where a guest needs to use multiple virtio-vsock devices at the same time.
*** This bug has been marked as a duplicate of bug 1455015 ***
Description of problem: hotplug qmp command: { "execute": "device_add", "arguments": { "driver": "vhost-vsock-pci","id":"vhost-vsock-pci3","guest-cid":6}} guest dmesg error log: .... [47.273648] vmw_vsock_virtio_transport: probe of virtio3 failed with error -16 Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.Boot 7.4 guest /usr/libexec/qemu-kvm -name guest=r7,debug-threads=on -enable-kvm -M pc -cpu SandyBridge -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -boot strict=on -rtc base=localtime,clock=host,driftfix=slew \ -drive file=rhel74.qcow2,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial=QEMU-DISK1 -device virtio-scsi-pci,id=scsi0,bus=pci.0,ioeventfd=off -device scsi-hd,bus=scsi0.0,drive=drive-system-disk,id=system-disk,channel=0,scsi-id=0,lun=0,ver=mike,serial=ababab,bootindex=1 \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x4 -vnc :2 -monitor stdio -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=net0,mac=12:54:00:5c:88:61 \ -device vhost-vsock-pci,id=vhost-vsock-pci0,guest-cid=3 \ -qmp tcp:0:4444,server,nowait \ 2.hotplug virtio-vsock device { "execute": "device_add", "arguments": { "driver": "vhost-vsock-pci","id":"vhost-vsock-pci3","guest-cid":6}} 3. Actual results: [ 47.237208] pci 0000:00:06.0: [1af4:1012] type 00 class 0x078000 [ 47.237334] pci 0000:00:06.0: reg 0x10: [io 0x0000-0x001f] [ 47.237375] pci 0000:00:06.0: reg 0x14: [mem 0x00000000-0x00000fff] [ 47.237524] pci 0000:00:06.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit pref] [ 47.238360] pci 0000:00:06.0: BAR 4: assigned [mem 0xc0000000-0xc0003fff 64bit pref] [ 47.238418] pci 0000:00:06.0: BAR 1: assigned [mem 0xc0004000-0xc0004fff] [ 47.238439] pci 0000:00:06.0: BAR 0: assigned [io 0x1000-0x101f] [ 47.238586] virtio-pci 0000:00:06.0: enabling device (0000 -> 0003) [ 47.273648] vmw_vsock_virtio_transport: probe of virtio3 failed with error -16 Expected results: no error Additional info: