Hello Bryan, I did make my templates using this same method, but I went back and added the rootDiskController setting to the Template after it was already made and tried making new Instances from that Template. I will certainly go through the Template steps again and see if there is a step I missed. Thank you.
Jordan -----Original Message----- From: Bryan Lima <[email protected]> Sent: Thursday, July 25, 2024 1:29 PM To: [email protected] Subject: Re: Root Disk Controller Global Setting EXTERNAL Hello, Jordan Can you confirm that the instances create from the Windows template have the `rootDiskController` set to `virtio` after the reboot? If they do, the problem seems to be related to the operating system or the steps used to create the template. How did you create this Windows template? When creating a Windows template, we usually follow these steps: 1. Create a VM using a Windows ISO. 2. Install all the required drivers and packages that we need. 3. Create the template from the volume snapshot of this VM. 4. Configure the template settings (e.g. setting `nicAdapter` and `rootDiskController` to `virtio`). 5. Create instances from this template. You should only need to install the VirtIO drivers to the first VM instance, when preparing it for the template creation. Best regards, Bryan On 24/07/2024 14:17, Jordan Wolfson wrote: > Hello Bryan, > > I wanted to check in and see if you or anyone else had any insight or update > on this issue. Thanks. > > Jordan > > -----Original Message----- > From: Jordan Wolfson > Sent: Tuesday, July 23, 2024 1:01 PM > To: [email protected] > Subject: RE: Root Disk Controller Global Setting > > Hello Bryan, > > Thank you for the information. I have set my templates to use specific > controllers for my testing and have generated Instances from the templates, > but the Instance OS does not seem to inherit the controller settings that is > set on the Template. > > These Windows Instances all end up with the QEMU HARDDISKs and the Standard > SATA AHCI Controller in each case. This is after the VirtIO drivers have been > installed. > > How is using the VirtIO ISO different than the Executable? I mount the VirtIO > ISO in Windows and then run the "virtio-win-guest-tools" option from inside > the ISO. Is there a different way that I should be installing the VirtIO > drivers on these Instances? > > Thank you for the help, > > Jordan > > -----Original Message----- > From: Bryan Lima <[email protected]> > Sent: Tuesday, July 23, 2024 12:47 PM > To: [email protected] > Subject: Re: Root Disk Controller Global Setting > > EXTERNAL > > Hello, Jordan > > About the root/data disk controller global configuration, you can set this on > a per-template basis, i.e. you can set the root and data disk controller in > the template settings and all VMs create from it will use the same settings. > Therefore, if you create a Windows VM template in CloudStack with the > settings `rootDiskController` set to `virtio`, all VMs created from this > template will inherit the `virtio` disk controller setting — this is valid > for all settings in the template. Note that updating the settings of a > template will not change any running VMs created from it. > > As for the disk controller inside the Windows OS, we had some bad experience > when installing the VirtIO drivers using the executable; using the ISO image > worked best for the majority of our cases. > > Best regards, > Bryan > > On 23/07/2024 11:40, Jordan Wolfson wrote: >> Hello, >> >> My Windows Instances are set to "Windows PV" and they are assigned the >> "virtio" controller for Root and Data disks in Settings. >> >> However, inside the Windows Instance, I only see QEMU HARDDISKs and a >> Standard SATA AHCI Controller instead of any kind of VirtIO device. I am >> able to add new Volumes that initially appear inside the OS as VirtIO SCSI >> Disks but then change to QEMU HARDDISKs after a reboot. >> >> I have attempted to manually add the VirtIO drivers to these QEMU disks and >> to the Standard SATA AHCI Controller with no success. I attempted to add the >> drivers during installation but the disks always change to QEMU HARDDISK >> after a reboot. I added a new Volume to the Instance to see if the VirtIO >> drivers would be added with a new Volume without success. >> >> I ran CrystalDiskMark benchmark tests on different Instances with the >> different root and data disk controllers (ide, scsi, virtio, and osdefault) >> and the benchmark tests all came back roughly the same. >> >> Basically, I am not seeing that my specific CloudStack/KVM setup is honoring >> the Root and Data disk Settings for these Windows Instances and want to >> figure out what I can do to fix this issue please. >> >> Thank you for the help, >> >> Jordan >> >> -----Original Message----- >> From: Wei ZHOU <[email protected]> >> Sent: Tuesday, July 23, 2024 10:09 AM >> To: [email protected] >> Subject: Re: Root Disk Controller Global Setting >> >> EXTERNAL >> >> for vms on kvm, the disk controller (virtio/ide/virtio-scsi) is determined >> by os type. It can be overwritten by vm settings. Users can change os type >> for each vm as another option. >> >> If you have Windows vm with virtio driver installed, you can change the the >> OS type to "Windows PV". >> >> IMO, It is not needed to have global settings for kvm vms, which will bring >> more trouble than benefits. If the value in global settings is not supported >> by the vm(e.g. driver is not installed), vm won't boot up. >> >> >> >> -Wei >> >> On Tuesday, July 23, 2024, Jordan Wolfson >> <[email protected]> >> wrote: >> >>> Hello, >>> >>> Thank you, but I am asking about a Global Setting that can be >>> enabled or disabled. I am aware that I can add specific root/data >>> controllers for Instances but those settings are not being honored >>> inside the Windows OS even with VirtIO drivers installed. I am >>> inquiring about a Global Setting that can be toggled for KVM Instances. >>> Thank you. >>> >>> Jordan >>> >>> -----Original Message----- >>> From: Wei ZHOU <[email protected]> >>> Sent: Tuesday, July 23, 2024 9:35 AM >>> To: [email protected] >>> Cc: [email protected] >>> Subject: Re: Root Disk Controller Global Setting >>> >>> EXTERNAL >>> >>> Hi, >>> >>> You can add vm settings for the root/data disk controller. >>> >>> >>> -Wei >>> >>> >>> On Tue, Jul 23, 2024 at 3:29 PM Jordan Wolfson >>> <[email protected]> wrote: >>>> Good Morning, >>>> >>>> I am troubleshooting some Root and Data disk controller settings in >>>> our >>> KVM/CloudStack deployment and I have noticed that there is a global >>> setting for "Vmware root disk controller' for Instances but no such >>> setting to assign a default KVM Root or Data disk controller to >>> Instances. Is there a setting that I am missing or something else >>> that I need to enable? Thank you. >>>> [photo]<http://www.ussignal.com/> >>>> >>>> Jordan Wolfson >>>> Professional Services Engineer, US Signal >>>> >>>> 616.233.5032<tel:616.233.5032> | >>>> http://www.ussignal.com<https://www.ussignal.com> | >>>> [email protected]<mailto:[email protected]> >>>> >>>> 201 Ionia Ave SW, Grand Rapids, MI >>>> 49503<https://urldefense.com/v3/__https://maps.google.com/?q=201*20 >>>> I >>>> on >>>> ia*20Ave*20SW,*20Grand*20Rapids,*20MI*2049503__;JSUlJSUlJQ!!P9cq_d3 >>>> G >>>> yw >>>> !ljwFgSMEXIP0piGRApbxF-py-ulecCAFzVeTqyqX1MatYgmY4NPI5AXsLK-1vBgDjR >>>> B >>>> a- >>>> sv5WMZqZHj_tNbKjw$ > >>>> >>>> [linkedin]<https://urldefense.com/v3/__https://www.linkedin.com/com >>>> p >>>> an >>>> y/us-signal/__;!!P9cq_d3Gyw!ljwFgSMEXIP0piGRApbxF-py-ulecCAFzVeTqyq >>>> X 1M atYgmY4NPI5AXsLK-1vBgDjRBa-sv5WMZqZHirG7qkbA$ > >>>> >>>> [facebook]<https://urldefense.com/v3/__https://www.facebook.com/uss >>>> i >>>> gn >>>> alcom/__;!!P9cq_d3Gyw!ljwFgSMEXIP0piGRApbxF-py-ulecCAFzVeTqyqX1MatY >>>> g mY 4NPI5AXsLK-1vBgDjRBa-sv5WMZqZHg42ATsaQ$ > >>>> >>>> [youtube]<https://urldefense.com/v3/__https://www.youtube.com/chann >>>> e >>>> l/ >>>> UCaFBGFfXmHziWGTFqjGzaWw__;!!P9cq_d3Gyw!ljwFgSMEXIP0piGRApbxF-py-ul >>>> e cC AFzVeTqyqX1MatYgmY4NPI5AXsLK-1vBgDjRBa-sv5WMZqZHgI-WzhSg$ > >>>> >>>> IMPORTANT: The contents of this email are confidential. Information >>>> is >>> intended for the named recipient(s) only. If you have received this >>> email by mistake, please notify the sender immediately and do not >>> disclose the contents to anyone or make copies thereof.
