I am running Cloudstack 4.11 and have encountered an issue with hot added NICs on Windows guests. I add the NIC to a running guest, configure it, and it works as expected. After the guest reboots, the NIC is assigned to a different PCI slot, and then needs to be reconfigured. This has caused issues when those hot-added network interfaces are used for ISCSI traffic.
I can see the slot reassignment in both Windows and in the XML when I do a virsh dumpxml on the guest. I've also seen this behavior when hot adding volumes. That sometimes results in the volumes being in an offline state when the guest restarts. We can bring them online manually, and all of the data is there. I assume someone else has encountered this. If so, have you worked around it somehow? For now, we're going to add interfaces and volumes only when the guest is powered off, but that does make things a bit more work. Thanks. -- Steve Fuller [email protected]
