Hi Steve I don't know about the hot-add nic issue - but with the volumes on windows guests you need to set the SAN policy to OnlineAll in diskpart - then additional volumes will always be available (we bake this into our windows templates) Ref: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/san
BR Gary Gary Dixon Quadris Cloud Manager 0161 537 4980 +44 7989717661 [email protected] www.quadris.com Innovation House, 12-13 Bredbury Business Park Bredbury Park Way, Bredbury, Stockport, SK6 2SN -----Original Message----- From: S.Fuller <[email protected]> Sent: Wednesday, January 24, 2024 3:04 AM To: [email protected] Subject: Hot Added NICs - PCI slot changes on instance reboot 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]
