Yes, I tried that as well. Tried: "Other PV 32 bit" "Other PV 64 bit" "Other VirtIO PV" "Windows PV"
The other pv 64 and 32 bit are trying to load a CentOS template for some reason. The Windows PV boots bit the PV drivers are still not there. I am going to try a couple of other things. -----Original Message----- From: Ruben Bosch <[email protected]> Sent: Monday, October 23, 2023 5:10 PM To: [email protected] Subject: Re: PV Drivers on VMs created through CS Hi, Did you check this document? https://docs.cloudstack.apache.org/en/latest/adminguide/templates.html You need to prepare your VM and specify the OS type as "Other PV (xx-bit)" Met vriendelijke groet / Kind regards, Ruben Bosch CLDIN > On 23 Oct 2023, at 23:05, <[email protected]> <[email protected]> wrote: > > Hello all, > > > > A few weeks back I sent a message about how my VMs created in CS do > not honor the installed PV drivers. To recap, I use XCP-NG for my > hypervisors, and I use a lab install to create templates that I then > upload into the CS console. This lab XCP-NG cluster is the same > version and patch level as the production CS hosts. On these > templates, I add the Windows PV drivers so the VM runs with the best > driver support. You can see the proper drivers when you go into the > device manager, and you get the message in XOA that the agent is > installed. So as an example, you see the NIC as an XCP-NG Virt NIC, the XCP-NG storage bus, etc. > > > > I then sysprep this image and shutdown and then export the VHD and > import into CS. But here is where it gets weird. After uploading this > VHD into CS and then creating a VM from that template, the PV drivers > are not used. It reverts to the Realtek NIC, the storage driver is > gone, and XOA does not show it has an agent. So its like the drivers > are not even installed. To make sure its not my hardware, if I import > the same VHD manually into one of the CS hosts directly and create a > fully default VM with that template, all the drivers are still present. > > > > So my question is, is CS creating the VM in such a way that it is not > allowing the driver use? Are there any settings I can look at to find > out why this is happening? I do check the slider bar that says > "Original XS Version is 6.1+". Should I not do this? > > > > Thank you guys for any help. >
