tyradyne opened a new issue, #9460:
URL: https://github.com/apache/cloudstack/issues/9460
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Instances
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19.1.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advanced Networking
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
KVM
##### SUMMARY
<!-- Explain the problem/feature briefly -->
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
<!--
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
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.
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
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
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
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"/>
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
