Let's try if the virtual provision would work

[psss]

No description provided.

[psss]

Seems to be working fine for f35 and f36. I see the following error on f34 and rawhide:

libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: 2022-05-25T14:53:24.448314Z qemu-system-x86_64: -device {"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x2","drive":"libvirt-2-format","id":"virtio-disk0","bootindex":1,"write-cache":"on"}: PCI: slot 2 function 0 not available for virtio-blk-pci, in use by virtio-net-pci,id=(null)
Instance startup failed, retrying in 5 seconds...
libvirt: QEMU Driver error : internal error: qemu unexpectedly closed the monitor: 2022-05-25T14:53:30.238067Z qemu-system-x86_64: -device {"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x2","drive":"libvirt-2-format","id":"virtio-disk0","bootindex":1,"write-cache":"on"}: PCI: slot 2 function 0 not available for virtio-blk-pci, in use by virtio-net-pci,id=(null)

@frantisekz, any idea what might be wrong / different for these two? @lukaszachy, @thrix, fyi.

[psss]

/packit test

[psss]

/packit test

[psss]

Fresh run failed with the following error:

Failed to boot testcloud instance (internal error: process exited while connecting to monitor: 2022-11-22T14:02:32.922607Z qemu-system-x86_64: -device {"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x2","drive":"libvirt-2-format","id":"virtio-disk0","bootindex":1,"write-cache":"on"}: PCI: slot 2 function 0 not available for virtio-blk-pci, in use by virtio-net-pci,id=(null)).

@frantisekz any idea what might be the problem?

[psss]

@lukaszachy, @happz, @thrix, once the fresh testcloud is released we could enable at least some tests which are using the virtual provision and catch possible problems related only to that method earlier.