You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
RootDiskController setting not Honored throughout Instance lifecycle #9460
When creating a Windows Instance configured with "rootDiskController=virtio" in Settings and using UEFI Secure Boot in the OS, existing and added Disks, initially configured with virtio scsi controllers, will lose these controller settings and revert to basic sata controllers after a stop and start. This behavior does not occur on Windows Instance using BIOS boot.
STEPS TO REPRODUCE
Create Windows 2019 Instance that is assigned the setting "rootDiskController=virtio" and uses UEFI Secure Boot. Install all necessary VirtIO drivers. Reboot the Instance. Log in and Open Device Manager in Windows. Hot-add new Volume to Windows Instance through CloudStack and observe in the OS that the newly added disk will be the correct "Red Hat VirtIO SCSI Disk Device" and the Storage Controller will be the correct "Red Hat VirtIO SCSI Controller." Stop the Instance. Start the Instance. Log in and open Device Manager in OS. Observe that both disks are now "QEMU HARDDISK" and the Storage Controller has been removed.
EXPECTED RESULTS
Expected results are that the Disk Controller and Volume settings would persist for the entirety of the Instance Lifecycle. The Disk Controller would remain in the following state as seen in this virsh file snippit. This excerpt is from before the Instance was stopped:
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source file='/mnt/7fe777bd-cd27-3b37-bf4c-dc94fcbe6d33/0b4b8825-1465-4221-b42d-8827688baac3' index='4'/>
<backingStore/>
<target dev='vdb' bus='virtio'/>
<serial>0b4b882514654221b42d</serial>
<alias name='virtio-disk1'/>
<address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
</disk>
ACTUAL RESULTS
After Shutdown and Startup, the Disk Controller and Volume settings are changed to the following state in the OS and in the virsh file:
<disk type="file" device="disk">
<driver name="qemu" type="qcow2" cache="none"/>
<source file="/mnt/7fe777bd-cd27-3b37-bf4c-dc94fcbe6d33/0b4b8825-1465-4221-b42d-8827688baac3" index="2"/>
<backingStore/>
<target dev="sdb" bus="sata"/>
<serial>0b4b882514654221b42d</serial>
<alias name="sata0-0-1"/>
<address type="drive" controller="0" bus="0" target="0" unit="1"/>
@shwstppr Wouldn't the SATA device be the Optical Drive? What is "it" in your message? Which Volume? The Boot Volume or another one? I ask because we are still seeing this issue occur. Thanks.
@tyradyne I'm not completely sure now as it has been a few weeks since I tested but I think I was referring to the ROOT volume disk controller. Can retest and confirm in the next few days.
The PR I mentioned is not merged yet so I don't think we have any resolution for the behaviour as of now
@shwstppr Hello, have you bee able to retest and confirm whether you were looking at the ROOT disk or the SATA Optical Drive in terms of RootDiskController settings? Would you please share the testing screenshots? Thank you.
Hey @tyradyne , I reported this issue #12041 that refers to DiskController in the VMWare context. DO you think they both could be related and potentially solved by the same code changes?
Activity
boring-cyborg commentedon Jul 26, 2024
Thanks for opening your first issue here! Be sure to follow the issue template!
andrijapanicsb commentedon Jul 28, 2024
Sounds like a nice bug
Cc @weizhouapache @rohityadavcloud @sureshanaparti
kvm: fix disk controller for secure boot vm
12 remaining items
tyradyne commentedon Oct 29, 2025
@shwstppr Wouldn't the SATA device be the Optical Drive? What is "it" in your message? Which Volume? The Boot Volume or another one? I ask because we are still seeing this issue occur. Thanks.
shwstppr commentedon Oct 29, 2025
@tyradyne I'm not completely sure now as it has been a few weeks since I tested but I think I was referring to the ROOT volume disk controller. Can retest and confirm in the next few days.
The PR I mentioned is not merged yet so I don't think we have any resolution for the behaviour as of now
tyradyne commentedon Nov 17, 2025
@shwstppr Hello, have you bee able to retest and confirm whether you were looking at the ROOT disk or the SATA Optical Drive in terms of RootDiskController settings? Would you please share the testing screenshots? Thank you.
daviftorres commentedon Nov 17, 2025
Hey @tyradyne , I reported this issue #12041 that refers to DiskController in the VMWare context. DO you think they both could be related and potentially solved by the same code changes?
shwstppr commentedon Nov 27, 2025
@tyradyne sorry I got busy with other things. I'll try to get back to you on your query by tomorrow
shwstppr commentedon Nov 29, 2025
@tyradyne here is my test, deployed a Windows UEFI VM with rootDiskController set to virtio and having an additional DATA disk,
VM definition showed SATA for device bus,
VM definition remained same after VM stop-start
kvm: allow skip forcing disk controller
kvm: allow skip forcing disk controller
DaanHoogland commentedon Jan 9, 2026
fixed in #11750