Bug 2035497 - internal error: qemu unexpectedly closed the monitor: 2021-12-24T09:35:01.024566Z qemu-kvm: -device {"driver":"virtio-scsi-pci","id":"scsi0","bus":"pci.0","addr":"0x2"}: PCI: slot 2 function 0 not available for virtio-scsi-pci, in use by virtio-net-pci [c
Summary: internal error: qemu unexpectedly closed the monitor: 2021-12-24T09:35:01.024...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libguestfs
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-24 09:41 UTC by Richard W.M. Jones
Modified: 2022-01-09 01:10 UTC (History)
1 user (show)

Fixed In Version: libguestfs-1.46.2-1.fc34 libguestfs-1.46.2-1.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-09 00:54:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2021-12-24 09:41:14 UTC
This bug was initially created as a copy of Bug #2034160

Description of problem:
v2v conversion is failed with PCI: slot 2 function 0 not available for virtio-scsi-pci, in use by virtio-net-pci [code=1 int1=-1]

A simple reproducer is

$ guestfish --network run
libguestfs: error: could not create appliance through libvirt.

Try running qemu directly without libvirt using this environment variable:
export LIBGUESTFS_BACKEND=direct

Original error from libvirt: internal error: qemu unexpectedly closed the monitor: 2021-12-24T09:40:44.648231Z qemu-kvm: -device {"driver":"virtio-scsi-pci","id":"scsi0","bus":"pci.0","addr":"0x2"}: PCI: slot 2 function 0 not available for virtio-scsi-pci, in use by virtio-net-pci [code=1 int1=-1]

Version-Release number of selected component (if applicable):

libvirt-libs-7.10.0-1.fc36.x86_64
qemu-6.2.0-1.fc36.x86_64
libguestfs-1.46.0-2.fc36.x86_64

How reproducible:
100%

Comment 2 Fedora Update System 2021-12-24 11:30:09 UTC
FEDORA-2021-fd774f1eaf has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-fd774f1eaf

Comment 3 Fedora Update System 2021-12-24 11:30:11 UTC
FEDORA-2021-fb500603c0 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-fb500603c0

Comment 4 Fedora Update System 2021-12-25 01:59:44 UTC
FEDORA-2021-fb500603c0 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-fb500603c0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-fb500603c0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-12-25 02:11:39 UTC
FEDORA-2021-fd774f1eaf has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-fd774f1eaf`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-fd774f1eaf

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-01-09 00:54:09 UTC
FEDORA-2021-fb500603c0 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2022-01-09 01:10:03 UTC
FEDORA-2021-fd774f1eaf has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.