Re: Changing the NIC and disk controller type permanently
To set it on the template, simply edit the template once it's created: cmk update template id=xx details[0].rootDiskController=pvscsi details[0].keyboard=uk details[0].nicAdapter=Vmxnet3 I have not tried to create a template with the "details" - feel free to use the same command structure as in the above example - per the API docs, it should work. Best, Andrija On Fri, 17 May 2019 at 13:48, Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > Thanks, the manual change in ESX is basically what we did when changing > the details in CS didn't have the desired effect. > > > Can you clarify how to correctly set the root disk controller for a > template? With the rootDiskController detail, as we tried to do it for VMs? > > > Since we'll be relying more on cloudmonkey from now on, what would be the > corresponding command line to this? > > > $ cmk create template details= ? > > > I have a vague recollection that cloudmonkey had an issue with nested data > structures specified as arguments. > > Is this still the case? > > > From: Andrija Panic > Sent: 17 May 2019 11:45:40 > To: users > Subject: Re: Changing the NIC and disk controller type permanently > > Gregor, > > I already shared the solution for existing VMs - for any new VMs to be > deployed from some template, please change the template details and specify > the rootController type as you need it - this will make sure all new VMs > deployed from that template will inherit the specific root controller > type... > > Let me know if that works for you. > > Andrija > > > On Fri, 17 May 2019 at 15:07, Riepl, Gregor (SWISS TXT) < > gregor.ri...@swisstxt.ch> wrote: > > > Hi Andrija, > > > > > > Thanks for the update, I kind of feared that this still wasn't possible > in > > a clean way. > > > > > > As evidenced by the results, setting the details via the commands I > posted > > *did* have a certain effect, it just didn't work correctly for the root > > disk controller. > > > > > > I know that changing the controller can make Windows unbootable, but for > > us, it was the opposite: Having the controller set to the default > lsilogic > > (not SAS) would result in unbootable Windows VMs, because the LSI Logic > > Parallel SCSI drivers were removed in Windows Server 2012. Without > > injecting them into the Template, new VMs deployed with this controller > > won't boot. Since we had a hard time preparing such a template, our > > solution was to modify the controller instead. > > > > > > That's why I'm asking how to change this permantenly, so we won't have > the > > issue with Windows VMs any more. > > > > > > The same applies to the NIC. The Windows E1000 driver is unreliable with > > VMware's emulation, so we'd like to switch to VMXNET3 for all Windows > VMs. > > Setting the nicAdapter detail worked as expected, at least. > > > > > > Any suggestions? > > > > > > Regards, > > > > Gregor > > > > > > From: Andrija Panic > > Sent: 17 May 2019 08:30:22 > > To: users > > Subject: Re: Changing the NIC and disk controller type permanently > > > > Hi Gregor, > > > > the code around managing VM details for existing VMs (CONTROLLER > > specifically) could be a bit better - but in short - there is NO way to > > change existing controller type from the current ones (for VMware > > specifically) using CloudStack (btw you "can" make the change in the GUI, > > while VM is stopped - there is a "Settings" tab there.) > > > > You "can" change these details on the VM level (existing VMs) via > API/GUI, > > this changes the records in the "user_vm_details" table - but simply > these > > new values are NOT read/applied during starting an existing VM - > actually, > > even when you change that in GUI (or DB) and start a VM - these values > will > > be reverted back. > > > > I just did more tests - and the way to change it would be to stop VM, go > to > > vCenter, change (all 4 controllers) to " LSI Logic SAS" (or any other > you > > want) - then go back to CloudStack and edit VM details (Settings tab, > while > > VM is stopped) to "lsisas1068" - simply to sync ACS to reality (to > > vCenter). > > > > Make sure to do proper testing, since changing root controller driver in > > Windows can sometimes cause it to fail boot. > > > > Best, > > Andrija > >
Re: Changing the NIC and disk controller type permanently
Thanks, the manual change in ESX is basically what we did when changing the details in CS didn't have the desired effect. Can you clarify how to correctly set the root disk controller for a template? With the rootDiskController detail, as we tried to do it for VMs? Since we'll be relying more on cloudmonkey from now on, what would be the corresponding command line to this? $ cmk create template details= ? I have a vague recollection that cloudmonkey had an issue with nested data structures specified as arguments. Is this still the case? From: Andrija Panic Sent: 17 May 2019 11:45:40 To: users Subject: Re: Changing the NIC and disk controller type permanently Gregor, I already shared the solution for existing VMs - for any new VMs to be deployed from some template, please change the template details and specify the rootController type as you need it - this will make sure all new VMs deployed from that template will inherit the specific root controller type... Let me know if that works for you. Andrija On Fri, 17 May 2019 at 15:07, Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > Hi Andrija, > > > Thanks for the update, I kind of feared that this still wasn't possible in > a clean way. > > > As evidenced by the results, setting the details via the commands I posted > *did* have a certain effect, it just didn't work correctly for the root > disk controller. > > > I know that changing the controller can make Windows unbootable, but for > us, it was the opposite: Having the controller set to the default lsilogic > (not SAS) would result in unbootable Windows VMs, because the LSI Logic > Parallel SCSI drivers were removed in Windows Server 2012. Without > injecting them into the Template, new VMs deployed with this controller > won't boot. Since we had a hard time preparing such a template, our > solution was to modify the controller instead. > > > That's why I'm asking how to change this permantenly, so we won't have the > issue with Windows VMs any more. > > > The same applies to the NIC. The Windows E1000 driver is unreliable with > VMware's emulation, so we'd like to switch to VMXNET3 for all Windows VMs. > Setting the nicAdapter detail worked as expected, at least. > > > Any suggestions? > > > Regards, > > Gregor > > ________ > From: Andrija Panic > Sent: 17 May 2019 08:30:22 > To: users > Subject: Re: Changing the NIC and disk controller type permanently > > Hi Gregor, > > the code around managing VM details for existing VMs (CONTROLLER > specifically) could be a bit better - but in short - there is NO way to > change existing controller type from the current ones (for VMware > specifically) using CloudStack (btw you "can" make the change in the GUI, > while VM is stopped - there is a "Settings" tab there.) > > You "can" change these details on the VM level (existing VMs) via API/GUI, > this changes the records in the "user_vm_details" table - but simply these > new values are NOT read/applied during starting an existing VM - actually, > even when you change that in GUI (or DB) and start a VM - these values will > be reverted back. > > I just did more tests - and the way to change it would be to stop VM, go to > vCenter, change (all 4 controllers) to " LSI Logic SAS" (or any other you > want) - then go back to CloudStack and edit VM details (Settings tab, while > VM is stopped) to "lsisas1068" - simply to sync ACS to reality (to > vCenter). > > Make sure to do proper testing, since changing root controller driver in > Windows can sometimes cause it to fail boot. > > Best, > Andrija > > > > On Thu, 16 May 2019 at 21:44, Riepl, Gregor (SWISS TXT) < > gregor.ri...@swisstxt.ch> wrote: > > > > > > $ cloudstack addResourceDetail "details[0].key=rootDiskController" > > > "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id" > > > > Note: lsisas1068 comes from > > > > > https://github.com/apache/cloudstack/blob/4.11.2.0/vmware-base/src/com/cloud/hypervisor/vmware/mo/ScsiDiskControllerType.java > > > > We had set this to lsilogicsas previously (on CS 4.5), which causes the > > following exception on start on CS 4.11.2.0: > > > > com.cloud.utils.exception.CloudRuntimeException: Invalid root disk > > controller detected : none > > at > > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResou > > rce.java:1690) > > at > > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vmwa > > reResource.java:496) > > at > > com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgen > > tAttache.java:315) > > at > > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Mana > > gedContextRunnable.java:49) > > > > ... > > > > > -- > > Andrija Panić > -- Andrija Panić
Re: Changing the NIC and disk controller type permanently
Gregor, I already shared the solution for existing VMs - for any new VMs to be deployed from some template, please change the template details and specify the rootController type as you need it - this will make sure all new VMs deployed from that template will inherit the specific root controller type... Let me know if that works for you. Andrija On Fri, 17 May 2019 at 15:07, Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > Hi Andrija, > > > Thanks for the update, I kind of feared that this still wasn't possible in > a clean way. > > > As evidenced by the results, setting the details via the commands I posted > *did* have a certain effect, it just didn't work correctly for the root > disk controller. > > > I know that changing the controller can make Windows unbootable, but for > us, it was the opposite: Having the controller set to the default lsilogic > (not SAS) would result in unbootable Windows VMs, because the LSI Logic > Parallel SCSI drivers were removed in Windows Server 2012. Without > injecting them into the Template, new VMs deployed with this controller > won't boot. Since we had a hard time preparing such a template, our > solution was to modify the controller instead. > > > That's why I'm asking how to change this permantenly, so we won't have the > issue with Windows VMs any more. > > > The same applies to the NIC. The Windows E1000 driver is unreliable with > VMware's emulation, so we'd like to switch to VMXNET3 for all Windows VMs. > Setting the nicAdapter detail worked as expected, at least. > > > Any suggestions? > > > Regards, > > Gregor > > ________ > From: Andrija Panic > Sent: 17 May 2019 08:30:22 > To: users > Subject: Re: Changing the NIC and disk controller type permanently > > Hi Gregor, > > the code around managing VM details for existing VMs (CONTROLLER > specifically) could be a bit better - but in short - there is NO way to > change existing controller type from the current ones (for VMware > specifically) using CloudStack (btw you "can" make the change in the GUI, > while VM is stopped - there is a "Settings" tab there.) > > You "can" change these details on the VM level (existing VMs) via API/GUI, > this changes the records in the "user_vm_details" table - but simply these > new values are NOT read/applied during starting an existing VM - actually, > even when you change that in GUI (or DB) and start a VM - these values will > be reverted back. > > I just did more tests - and the way to change it would be to stop VM, go to > vCenter, change (all 4 controllers) to " LSI Logic SAS" (or any other you > want) - then go back to CloudStack and edit VM details (Settings tab, while > VM is stopped) to "lsisas1068" - simply to sync ACS to reality (to > vCenter). > > Make sure to do proper testing, since changing root controller driver in > Windows can sometimes cause it to fail boot. > > Best, > Andrija > > > > On Thu, 16 May 2019 at 21:44, Riepl, Gregor (SWISS TXT) < > gregor.ri...@swisstxt.ch> wrote: > > > > > > $ cloudstack addResourceDetail "details[0].key=rootDiskController" > > > "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id" > > > > Note: lsisas1068 comes from > > > > > https://github.com/apache/cloudstack/blob/4.11.2.0/vmware-base/src/com/cloud/hypervisor/vmware/mo/ScsiDiskControllerType.java > > > > We had set this to lsilogicsas previously (on CS 4.5), which causes the > > following exception on start on CS 4.11.2.0: > > > > com.cloud.utils.exception.CloudRuntimeException: Invalid root disk > > controller detected : none > > at > > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResou > > rce.java:1690) > > at > > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vmwa > > reResource.java:496) > > at > > com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgen > > tAttache.java:315) > > at > > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Mana > > gedContextRunnable.java:49) > > > > ... > > > > > -- > > Andrija Panić > -- Andrija Panić
Re: Changing the NIC and disk controller type permanently
Hi Andrija, Thanks for the update, I kind of feared that this still wasn't possible in a clean way. As evidenced by the results, setting the details via the commands I posted *did* have a certain effect, it just didn't work correctly for the root disk controller. I know that changing the controller can make Windows unbootable, but for us, it was the opposite: Having the controller set to the default lsilogic (not SAS) would result in unbootable Windows VMs, because the LSI Logic Parallel SCSI drivers were removed in Windows Server 2012. Without injecting them into the Template, new VMs deployed with this controller won't boot. Since we had a hard time preparing such a template, our solution was to modify the controller instead. That's why I'm asking how to change this permantenly, so we won't have the issue with Windows VMs any more. The same applies to the NIC. The Windows E1000 driver is unreliable with VMware's emulation, so we'd like to switch to VMXNET3 for all Windows VMs. Setting the nicAdapter detail worked as expected, at least. Any suggestions? Regards, Gregor From: Andrija Panic Sent: 17 May 2019 08:30:22 To: users Subject: Re: Changing the NIC and disk controller type permanently Hi Gregor, the code around managing VM details for existing VMs (CONTROLLER specifically) could be a bit better - but in short - there is NO way to change existing controller type from the current ones (for VMware specifically) using CloudStack (btw you "can" make the change in the GUI, while VM is stopped - there is a "Settings" tab there.) You "can" change these details on the VM level (existing VMs) via API/GUI, this changes the records in the "user_vm_details" table - but simply these new values are NOT read/applied during starting an existing VM - actually, even when you change that in GUI (or DB) and start a VM - these values will be reverted back. I just did more tests - and the way to change it would be to stop VM, go to vCenter, change (all 4 controllers) to " LSI Logic SAS" (or any other you want) - then go back to CloudStack and edit VM details (Settings tab, while VM is stopped) to "lsisas1068" - simply to sync ACS to reality (to vCenter). Make sure to do proper testing, since changing root controller driver in Windows can sometimes cause it to fail boot. Best, Andrija On Thu, 16 May 2019 at 21:44, Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > > > $ cloudstack addResourceDetail "details[0].key=rootDiskController" > > "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id" > > Note: lsisas1068 comes from > > https://github.com/apache/cloudstack/blob/4.11.2.0/vmware-base/src/com/cloud/hypervisor/vmware/mo/ScsiDiskControllerType.java > > We had set this to lsilogicsas previously (on CS 4.5), which causes the > following exception on start on CS 4.11.2.0: > > com.cloud.utils.exception.CloudRuntimeException: Invalid root disk > controller detected : none > at > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResou > rce.java:1690) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vmwa > reResource.java:496) > at > com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgen > tAttache.java:315) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Mana > gedContextRunnable.java:49) > > ... > -- Andrija Panić
Re: Changing the NIC and disk controller type permanently
Hi Gregor, the code around managing VM details for existing VMs (CONTROLLER specifically) could be a bit better - but in short - there is NO way to change existing controller type from the current ones (for VMware specifically) using CloudStack (btw you "can" make the change in the GUI, while VM is stopped - there is a "Settings" tab there.) You "can" change these details on the VM level (existing VMs) via API/GUI, this changes the records in the "user_vm_details" table - but simply these new values are NOT read/applied during starting an existing VM - actually, even when you change that in GUI (or DB) and start a VM - these values will be reverted back. I just did more tests - and the way to change it would be to stop VM, go to vCenter, change (all 4 controllers) to " LSI Logic SAS" (or any other you want) - then go back to CloudStack and edit VM details (Settings tab, while VM is stopped) to "lsisas1068" - simply to sync ACS to reality (to vCenter). Make sure to do proper testing, since changing root controller driver in Windows can sometimes cause it to fail boot. Best, Andrija On Thu, 16 May 2019 at 21:44, Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > > > $ cloudstack addResourceDetail "details[0].key=rootDiskController" > > "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id" > > Note: lsisas1068 comes from > > https://github.com/apache/cloudstack/blob/4.11.2.0/vmware-base/src/com/cloud/hypervisor/vmware/mo/ScsiDiskControllerType.java > > We had set this to lsilogicsas previously (on CS 4.5), which causes the > following exception on start on CS 4.11.2.0: > > com.cloud.utils.exception.CloudRuntimeException: Invalid root disk > controller detected : none > at > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResou > rce.java:1690) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vmwa > reResource.java:496) > at > com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgen > tAttache.java:315) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Mana > gedContextRunnable.java:49) > > ... > -- Andrija Panić
Re: Changing the NIC and disk controller type permanently
> $ cloudstack addResourceDetail "details[0].key=rootDiskController" > "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id" Note: lsisas1068 comes from https://github.com/apache/cloudstack/blob/4.11.2.0/vmware-base/src/com/cloud/hypervisor/vmware/mo/ScsiDiskControllerType.java We had set this to lsilogicsas previously (on CS 4.5), which causes the following exception on start on CS 4.11.2.0: com.cloud.utils.exception.CloudRuntimeException: Invalid root disk controller detected : none at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResou rce.java:1690) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vmwa reResource.java:496) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgen tAttache.java:315) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Mana gedContextRunnable.java:49) ...
Changing the NIC and disk controller type permanently
Hi, This is an old topic, [1] but it looks like behaviour changed in newer CloudStack versions. What is the recommended procedure to change the NIC and disk controller types of an existing VM (in stopped state)? We used $ cloudstack addResourceDetail "details[0].key=rootDiskController" "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id" and cloudstack addResourceDetail "details[0].key=nicAdapter" "details[0].value=Vmxnet3" "resourcetype=UserVm" "resourceid=$id" ( cloudstack = https://github.com/exoscale/cs ) This seemed to be effective for the network adapter, but not for the disk controller. The VM was booted with the lsiscsi (LSI Logic Parallel SCSI driver). Any help would be much appreciated, as these settings are necessary for booting Windows Server 201X on VMware ESX. Note: we're running ESX 5.5. Thanks! [1] http://mail-archives.apache.org/mod_mbox/cloudstack-users/201409.mbox/%3c54213b18.7020...@gmail.com%3e
RE: Disk controller type
Andrija, It seems to be an issue with windows, it won't correctly add the driver for virtio until a device exists. I tried may times right clicking on the inf files, and selecting install then rebooting, in safe mode etc, with different BCDedit values, all failed to boot windows. But hot-adding a virtio disk (and controller) and then installing the drivers worked repeatedly. The old tricks of the XP days changing from IDE to SATA controllers no longer seem to work ;) Thanks Adam -Original Message- From: Andrija Panic Sent: 26 September 2018 13:50 To: users Subject: Re: Disk controller type ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Hi Adam, Glad you solved the problem! But I need to say this work sounds "crazy" in a sense that this is not (per my knowledge) how it should be done "properly". Im wondering if this is something in 4.11 that makes you make such workaround... Anyway, glad you worked it out. Cheers On Wed, Sep 26, 2018, 04:39 Adam Witwicki wrote: > Ok Guys, I have cracked it - this is for 4.11 but should work on most > versions > > To change the controller type of an existing windows 2012 and 2016 > server from IDE ATA to virtio do the following > > > On the Host > > Create an empty disk > dd if=/dev/zero of=/home/user/blank.img bs=1M count=4096 > > Create a device xml file for a virtio disk /home/user/virtodisk.xml > with the following contains > > > > > > > > > > > Attach this disk to the running VM > > Virsh > attach-device /home/user/virtodisk.xml exit > > insert the Virtio Driver iso and install drivers on VM > > Shutdown VM using cloudstack control (stop instance) > > Add the following to the “user_vm_detail” table in the database, where > XXX is the 3 digits in the internal VM name i-83-XXX-VM > > INSERT INTO `user_vm_details` (`vm_id`, `name`, `value`, `display`) > VALUES (xxx, 'rootDiskController', 'virtio', 1); > > Start the VM and all is good > > > Thanks for everyone's help and suggestions > > Adam > > > -Original Message- > From: Andrija Panic > Sent: 21 September 2018 16:50 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. > Treat hyperlinks and attachments in this email with caution. ** > > Or in other words, again based on ACS 4.8, simply use Windows PV as > the OS type, but make sure that you have a clean driver install > process in your head - if install windows from zero - that is simple, > just detach win.iso,attach virtidrivers ISO file and load scsi > drivers... later install network Virtio etc :) > > But if converting existing IDE version of Windows, make some tests > with /detecthal to avoid long downtime :) > > On Fri, Sep 21, 2018, 16:14 Simon Weller wrote: > > > Your two options are virtio blk or virtio-scsi. If your imported VM > > doesn't have the correct controller specified, you're going to have > > to modify it before enabling virtio in libvirt. > > > > Check out this guide: > > https://access.redhat.com/articles/2470791#installing-the-kvm-window > > s- > > virtio-drivers-5 > > > > > > > > > > From: Adam Witwicki > > Sent: Friday, September 21, 2018 5:28 AM > > To: users@cloudstack.apache.org > > Subject: RE: Disk controller type > > > > Win 2016 doesn’t use Virtio by default, but we need too as disk > > performance is rubbish if we don’t > > > > > > > > > > -Original Message- > > From: Andrija Panic > > Sent: 21 September 2018 11:25 > > To: users > > Subject: Re: Disk controller type > > > > ** This mail originated from OUTSIDE the Oakford corporate network. > > Treat hyperlinks and attachments in this email with caution. ** > > > > Hrm... Im mot aware of Windows 2016 OS type, that is probably in > > newer version of ACS, so far, up to Windows 2012 OS type, it was all IDE... > > > > Can you do silly check with either 'ps aux | grep VMNAME' or with > > 'virsh dumpxml VMNAME' so we see what controller type is used. > > > > I have hard time believing that Win 2016 OS type would use Virtio by > > default, since afaik no Virtio drivers are builtin inaide Windows by > > default (in contrast to Hype-V drivers being available in stock > > Linux kernel for some tome now :) ) > > > > > > On Fri, Sep 21, 2018, 10:31 Adam Witwicki > wrote: > > > > > Andrija, > > > >
Re: Disk controller type
Hi Adam, Glad you solved the problem! But I need to say this work sounds "crazy" in a sense that this is not (per my knowledge) how it should be done "properly". Im wondering if this is something in 4.11 that makes you make such workaround... Anyway, glad you worked it out. Cheers On Wed, Sep 26, 2018, 04:39 Adam Witwicki wrote: > Ok Guys, I have cracked it - this is for 4.11 but should work on most > versions > > To change the controller type of an existing windows 2012 and 2016 server > from IDE ATA to virtio do the following > > > On the Host > > Create an empty disk > dd if=/dev/zero of=/home/user/blank.img bs=1M count=4096 > > Create a device xml file for a virtio disk > /home/user/virtodisk.xml with the following contains > > > > > > > > > > > Attach this disk to the running VM > > Virsh > attach-device /home/user/virtodisk.xml > exit > > insert the Virtio Driver iso and install drivers on VM > > Shutdown VM using cloudstack control (stop instance) > > Add the following to the “user_vm_detail” table in the database, where XXX > is the 3 digits in the internal VM name i-83-XXX-VM > > INSERT INTO `user_vm_details` (`vm_id`, `name`, `value`, `display`) VALUES > (xxx, 'rootDiskController', 'virtio', 1); > > Start the VM and all is good > > > Thanks for everyone's help and suggestions > > Adam > > > -Original Message- > From: Andrija Panic > Sent: 21 September 2018 16:50 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. Treat > hyperlinks and attachments in this email with caution. ** > > Or in other words, again based on ACS 4.8, simply use Windows PV as the OS > type, but make sure that you have a clean driver install process in your > head - if install windows from zero - that is simple, just detach > win.iso,attach virtidrivers ISO file and load scsi drivers... later install > network Virtio etc :) > > But if converting existing IDE version of Windows, make some tests with > /detecthal to avoid long downtime :) > > On Fri, Sep 21, 2018, 16:14 Simon Weller wrote: > > > Your two options are virtio blk or virtio-scsi. If your imported VM > > doesn't have the correct controller specified, you're going to have to > > modify it before enabling virtio in libvirt. > > > > Check out this guide: > > https://access.redhat.com/articles/2470791#installing-the-kvm-windows- > > virtio-drivers-5 > > > > > > > > > > From: Adam Witwicki > > Sent: Friday, September 21, 2018 5:28 AM > > To: users@cloudstack.apache.org > > Subject: RE: Disk controller type > > > > Win 2016 doesn’t use Virtio by default, but we need too as disk > > performance is rubbish if we don’t > > > > > > > > > > -Original Message- > > From: Andrija Panic > > Sent: 21 September 2018 11:25 > > To: users > > Subject: Re: Disk controller type > > > > ** This mail originated from OUTSIDE the Oakford corporate network. > > Treat hyperlinks and attachments in this email with caution. ** > > > > Hrm... Im mot aware of Windows 2016 OS type, that is probably in newer > > version of ACS, so far, up to Windows 2012 OS type, it was all IDE... > > > > Can you do silly check with either 'ps aux | grep VMNAME' or with > > 'virsh dumpxml VMNAME' so we see what controller type is used. > > > > I have hard time believing that Win 2016 OS type would use Virtio by > > default, since afaik no Virtio drivers are builtin inaide Windows by > > default (in contrast to Hype-V drivers being available in stock Linux > > kernel for some tome now :) ) > > > > > > On Fri, Sep 21, 2018, 10:31 Adam Witwicki > wrote: > > > > > Andrija, > > > > > > I have something weird, I have a template which uses the OS type of > > > Windows Server 2016 (64-bit), this was imported into Cloudstack and > > > this template uses a VirtIO controller I have another template that > > > was created from a disk also with OS type of Windows Server 2016 > > > (64-bit) but has an ID controller. > > > > > > I am trying to work out why this happened and now I can make the > > > disk template always select the VirtIO controller. > > > Setting the instance to windows PV causes BSOD on boot, well before > > > hal can be redetected > > > > > > > > > Thanks > > > > > > Adam > >
RE: Disk controller type
Ok Guys, I have cracked it - this is for 4.11 but should work on most versions To change the controller type of an existing windows 2012 and 2016 server from IDE ATA to virtio do the following On the Host Create an empty disk dd if=/dev/zero of=/home/user/blank.img bs=1M count=4096 Create a device xml file for a virtio disk /home/user/virtodisk.xml with the following contains Attach this disk to the running VM Virsh attach-device /home/user/virtodisk.xml exit insert the Virtio Driver iso and install drivers on VM Shutdown VM using cloudstack control (stop instance) Add the following to the “user_vm_detail” table in the database, where XXX is the 3 digits in the internal VM name i-83-XXX-VM INSERT INTO `user_vm_details` (`vm_id`, `name`, `value`, `display`) VALUES (xxx, 'rootDiskController', 'virtio', 1); Start the VM and all is good Thanks for everyone's help and suggestions Adam -Original Message- From: Andrija Panic Sent: 21 September 2018 16:50 To: users Subject: Re: Disk controller type ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Or in other words, again based on ACS 4.8, simply use Windows PV as the OS type, but make sure that you have a clean driver install process in your head - if install windows from zero - that is simple, just detach win.iso,attach virtidrivers ISO file and load scsi drivers... later install network Virtio etc :) But if converting existing IDE version of Windows, make some tests with /detecthal to avoid long downtime :) On Fri, Sep 21, 2018, 16:14 Simon Weller wrote: > Your two options are virtio blk or virtio-scsi. If your imported VM > doesn't have the correct controller specified, you're going to have to > modify it before enabling virtio in libvirt. > > Check out this guide: > https://access.redhat.com/articles/2470791#installing-the-kvm-windows- > virtio-drivers-5 > > > > > From: Adam Witwicki > Sent: Friday, September 21, 2018 5:28 AM > To: users@cloudstack.apache.org > Subject: RE: Disk controller type > > Win 2016 doesn’t use Virtio by default, but we need too as disk > performance is rubbish if we don’t > > > > > -Original Message- > From: Andrija Panic > Sent: 21 September 2018 11:25 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. > Treat hyperlinks and attachments in this email with caution. ** > > Hrm... Im mot aware of Windows 2016 OS type, that is probably in newer > version of ACS, so far, up to Windows 2012 OS type, it was all IDE... > > Can you do silly check with either 'ps aux | grep VMNAME' or with > 'virsh dumpxml VMNAME' so we see what controller type is used. > > I have hard time believing that Win 2016 OS type would use Virtio by > default, since afaik no Virtio drivers are builtin inaide Windows by > default (in contrast to Hype-V drivers being available in stock Linux > kernel for some tome now :) ) > > > On Fri, Sep 21, 2018, 10:31 Adam Witwicki wrote: > > > Andrija, > > > > I have something weird, I have a template which uses the OS type of > > Windows Server 2016 (64-bit), this was imported into Cloudstack and > > this template uses a VirtIO controller I have another template that > > was created from a disk also with OS type of Windows Server 2016 > > (64-bit) but has an ID controller. > > > > I am trying to work out why this happened and now I can make the > > disk template always select the VirtIO controller. > > Setting the instance to windows PV causes BSOD on boot, well before > > hal can be redetected > > > > > > Thanks > > > > Adam > > > > -Original Message- > > From: Andrija Panic > > Sent: 20 September 2018 11:18 > > To: users > > Subject: Re: Disk controller type > > > > ** This mail originated from OUTSIDE the Oakford corporate network. > > Treat hyperlinks and attachments in this email with caution. ** > > > > Sooo... here is my experience: > > > > if using correct VirtIO OS TYPE (set on template/VM) - i.e. ubuntu > > 14.04, Centos 6.x or 7.x, Windows PV, other PV (but NOT centos 6.0 > > or > > 7.0 - these "dot zero" versions are NOT virtio at least in ACS 4.8), > > then when VM is STARTED FROM ACS (power on VM) - all drives should > > be > attached as VirtIO. > > > > BUT if you do same as above, then additionally create and HOTPLUG > > new drives/volumes to KVM - it will be IDE - some strange default > > behavior during hotplug action just stop VM/
Re: Disk controller type
Or in other words, again based on ACS 4.8, simply use Windows PV as the OS type, but make sure that you have a clean driver install process in your head - if install windows from zero - that is simple, just detach win.iso,attach virtidrivers ISO file and load scsi drivers... later install network Virtio etc :) But if converting existing IDE version of Windows, make some tests with /detecthal to avoid long downtime :) On Fri, Sep 21, 2018, 16:14 Simon Weller wrote: > Your two options are virtio blk or virtio-scsi. If your imported VM > doesn't have the correct controller specified, you're going to have to > modify it before enabling virtio in libvirt. > > Check out this guide: > https://access.redhat.com/articles/2470791#installing-the-kvm-windows-virtio-drivers-5 > > > > > From: Adam Witwicki > Sent: Friday, September 21, 2018 5:28 AM > To: users@cloudstack.apache.org > Subject: RE: Disk controller type > > Win 2016 doesn’t use Virtio by default, but we need too as disk > performance is rubbish if we don’t > > > > > -Original Message- > From: Andrija Panic > Sent: 21 September 2018 11:25 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. Treat > hyperlinks and attachments in this email with caution. ** > > Hrm... Im mot aware of Windows 2016 OS type, that is probably in newer > version of ACS, so far, up to Windows 2012 OS type, it was all IDE... > > Can you do silly check with either 'ps aux | grep VMNAME' or with 'virsh > dumpxml VMNAME' so we see what controller type is used. > > I have hard time believing that Win 2016 OS type would use Virtio by > default, since afaik no Virtio drivers are builtin inaide Windows by > default (in contrast to Hype-V drivers being available in stock Linux > kernel for some tome now :) ) > > > On Fri, Sep 21, 2018, 10:31 Adam Witwicki wrote: > > > Andrija, > > > > I have something weird, I have a template which uses the OS type of > > Windows Server 2016 (64-bit), this was imported into Cloudstack and > > this template uses a VirtIO controller I have another template that > > was created from a disk also with OS type of Windows Server 2016 > > (64-bit) but has an ID controller. > > > > I am trying to work out why this happened and now I can make the disk > > template always select the VirtIO controller. > > Setting the instance to windows PV causes BSOD on boot, well before > > hal can be redetected > > > > > > Thanks > > > > Adam > > > > -Original Message- > > From: Andrija Panic > > Sent: 20 September 2018 11:18 > > To: users > > Subject: Re: Disk controller type > > > > ** This mail originated from OUTSIDE the Oakford corporate network. > > Treat hyperlinks and attachments in this email with caution. ** > > > > Sooo... here is my experience: > > > > if using correct VirtIO OS TYPE (set on template/VM) - i.e. ubuntu > > 14.04, Centos 6.x or 7.x, Windows PV, other PV (but NOT centos 6.0 or > > 7.0 - these "dot zero" versions are NOT virtio at least in ACS 4.8), > > then when VM is STARTED FROM ACS (power on VM) - all drives should be > attached as VirtIO. > > > > BUT if you do same as above, then additionally create and HOTPLUG new > > drives/volumes to KVM - it will be IDE - some strange default behavior > > during hotplug action just stop VM/start and it will become VirtIO > > again... > > > > In order to "troubleshoot" these instances - you need to be careful to > > which OS TYPE was the instance set to (this is inherited from > > TEMPLATE, if you used some template - but it CAN be changed on an > > deployed& > > instance) > > > > In case you plan to i.e. move your Windows instances from IDE to > > VirtIO - be aware that it might fail miserably, and OS will fail to > > boot - but there is a fix with *"* bcdedit /set detecthal boolean > > (where boolean is one of 1, on, yes or true) " after which Windows > > will detect HAL again and boot just fine. > > > > Let me know if more help needed > > > > Cheers > > > > On Thu, 20 Sep 2018 at 11:22, Adam Witwicki > > wrote: > > > > > > > > > > > It looks like I can just add > > > > > > rootDiskController virtio > > > > > > To the templates settings tab? > > > > > > Can anyone confirm? > > > > > > Thanks > > > > > > Adam > > > > > > -Original Message-
Re: Disk controller type
Your two options are virtio blk or virtio-scsi. If your imported VM doesn't have the correct controller specified, you're going to have to modify it before enabling virtio in libvirt. Check out this guide: https://access.redhat.com/articles/2470791#installing-the-kvm-windows-virtio-drivers-5 From: Adam Witwicki Sent: Friday, September 21, 2018 5:28 AM To: users@cloudstack.apache.org Subject: RE: Disk controller type Win 2016 doesn’t use Virtio by default, but we need too as disk performance is rubbish if we don’t -Original Message- From: Andrija Panic Sent: 21 September 2018 11:25 To: users Subject: Re: Disk controller type ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Hrm... Im mot aware of Windows 2016 OS type, that is probably in newer version of ACS, so far, up to Windows 2012 OS type, it was all IDE... Can you do silly check with either 'ps aux | grep VMNAME' or with 'virsh dumpxml VMNAME' so we see what controller type is used. I have hard time believing that Win 2016 OS type would use Virtio by default, since afaik no Virtio drivers are builtin inaide Windows by default (in contrast to Hype-V drivers being available in stock Linux kernel for some tome now :) ) On Fri, Sep 21, 2018, 10:31 Adam Witwicki wrote: > Andrija, > > I have something weird, I have a template which uses the OS type of > Windows Server 2016 (64-bit), this was imported into Cloudstack and > this template uses a VirtIO controller I have another template that > was created from a disk also with OS type of Windows Server 2016 > (64-bit) but has an ID controller. > > I am trying to work out why this happened and now I can make the disk > template always select the VirtIO controller. > Setting the instance to windows PV causes BSOD on boot, well before > hal can be redetected > > > Thanks > > Adam > > -Original Message- > From: Andrija Panic > Sent: 20 September 2018 11:18 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. > Treat hyperlinks and attachments in this email with caution. ** > > Sooo... here is my experience: > > if using correct VirtIO OS TYPE (set on template/VM) - i.e. ubuntu > 14.04, Centos 6.x or 7.x, Windows PV, other PV (but NOT centos 6.0 or > 7.0 - these "dot zero" versions are NOT virtio at least in ACS 4.8), > then when VM is STARTED FROM ACS (power on VM) - all drives should be > attached as VirtIO. > > BUT if you do same as above, then additionally create and HOTPLUG new > drives/volumes to KVM - it will be IDE - some strange default behavior > during hotplug action just stop VM/start and it will become VirtIO > again... > > In order to "troubleshoot" these instances - you need to be careful to > which OS TYPE was the instance set to (this is inherited from > TEMPLATE, if you used some template - but it CAN be changed on an > deployed& > instance) > > In case you plan to i.e. move your Windows instances from IDE to > VirtIO - be aware that it might fail miserably, and OS will fail to > boot - but there is a fix with *"* bcdedit /set detecthal boolean > (where boolean is one of 1, on, yes or true) " after which Windows > will detect HAL again and boot just fine. > > Let me know if more help needed > > Cheers > > On Thu, 20 Sep 2018 at 11:22, Adam Witwicki > wrote: > > > > > > > It looks like I can just add > > > > rootDiskController virtio > > > > To the templates settings tab? > > > > Can anyone confirm? > > > > Thanks > > > > Adam > > > > -Original Message- > > From: Ivan Kudryavtsev > > Sent: 20 September 2018 10:20 > > To: users > > Subject: Re: Disk controller type > > > > ** This mail originated from OUTSIDE the Oakford corporate network. > > Treat hyperlinks and attachments in this email with caution. ** > > > > Rakesh, It doesn't work like that for CS as it uses stateless XML > configs. > > > > чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh > ><www.rakeshv@gmail.com > >: > > > > > I think you can change the controller type in XML file of the VM > > > but not sure if that works or not. > > > > > > virsh dumpxml > > > virsh edit > > > change the controller type, save and start the vm again > > > > > > On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki > > > > > > wrote: > > > > > > > Hello, > > > > > > > > I have a number of of ins
RE: Disk controller type
Win 2016 doesn’t use Virtio by default, but we need too as disk performance is rubbish if we don’t -Original Message- From: Andrija Panic Sent: 21 September 2018 11:25 To: users Subject: Re: Disk controller type ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Hrm... Im mot aware of Windows 2016 OS type, that is probably in newer version of ACS, so far, up to Windows 2012 OS type, it was all IDE... Can you do silly check with either 'ps aux | grep VMNAME' or with 'virsh dumpxml VMNAME' so we see what controller type is used. I have hard time believing that Win 2016 OS type would use Virtio by default, since afaik no Virtio drivers are builtin inaide Windows by default (in contrast to Hype-V drivers being available in stock Linux kernel for some tome now :) ) On Fri, Sep 21, 2018, 10:31 Adam Witwicki wrote: > Andrija, > > I have something weird, I have a template which uses the OS type of > Windows Server 2016 (64-bit), this was imported into Cloudstack and > this template uses a VirtIO controller I have another template that > was created from a disk also with OS type of Windows Server 2016 > (64-bit) but has an ID controller. > > I am trying to work out why this happened and now I can make the disk > template always select the VirtIO controller. > Setting the instance to windows PV causes BSOD on boot, well before > hal can be redetected > > > Thanks > > Adam > > -Original Message- > From: Andrija Panic > Sent: 20 September 2018 11:18 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. > Treat hyperlinks and attachments in this email with caution. ** > > Sooo... here is my experience: > > if using correct VirtIO OS TYPE (set on template/VM) - i.e. ubuntu > 14.04, Centos 6.x or 7.x, Windows PV, other PV (but NOT centos 6.0 or > 7.0 - these "dot zero" versions are NOT virtio at least in ACS 4.8), > then when VM is STARTED FROM ACS (power on VM) - all drives should be > attached as VirtIO. > > BUT if you do same as above, then additionally create and HOTPLUG new > drives/volumes to KVM - it will be IDE - some strange default behavior > during hotplug action just stop VM/start and it will become VirtIO > again... > > In order to "troubleshoot" these instances - you need to be careful to > which OS TYPE was the instance set to (this is inherited from > TEMPLATE, if you used some template - but it CAN be changed on an > deployed& > instance) > > In case you plan to i.e. move your Windows instances from IDE to > VirtIO - be aware that it might fail miserably, and OS will fail to > boot - but there is a fix with *"* bcdedit /set detecthal boolean > (where boolean is one of 1, on, yes or true) " after which Windows > will detect HAL again and boot just fine. > > Let me know if more help needed > > Cheers > > On Thu, 20 Sep 2018 at 11:22, Adam Witwicki > wrote: > > > > > > > It looks like I can just add > > > > rootDiskController virtio > > > > To the templates settings tab? > > > > Can anyone confirm? > > > > Thanks > > > > Adam > > > > -Original Message- > > From: Ivan Kudryavtsev > > Sent: 20 September 2018 10:20 > > To: users > > Subject: Re: Disk controller type > > > > ** This mail originated from OUTSIDE the Oakford corporate network. > > Treat hyperlinks and attachments in this email with caution. ** > > > > Rakesh, It doesn't work like that for CS as it uses stateless XML > configs. > > > > чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh > > >: > > > > > I think you can change the controller type in XML file of the VM > > > but not sure if that works or not. > > > > > > virsh dumpxml > > > virsh edit > > > change the controller type, save and start the vm again > > > > > > On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki > > > > > > wrote: > > > > > > > Hello, > > > > > > > > I have a number of of instances using the wrong controller type > > > > (ATA) > > > does > > > > anyone know where this is set in the database so I can start > > > > them with > > > the > > > > VirtIO scsi controller? > > > > > > > > Thanks > > > > > > > > Adam > > > > > > > > > > > > > > > > > > > > Disclaimer Notice: > > > > This email
Re: Disk controller type
Hrm... Im mot aware of Windows 2016 OS type, that is probably in newer version of ACS, so far, up to Windows 2012 OS type, it was all IDE... Can you do silly check with either 'ps aux | grep VMNAME' or with 'virsh dumpxml VMNAME' so we see what controller type is used. I have hard time believing that Win 2016 OS type would use Virtio by default, since afaik no Virtio drivers are builtin inaide Windows by default (in contrast to Hype-V drivers being available in stock Linux kernel for some tome now :) ) On Fri, Sep 21, 2018, 10:31 Adam Witwicki wrote: > Andrija, > > I have something weird, I have a template which uses the OS type of > Windows Server 2016 (64-bit), this was imported into Cloudstack and this > template uses a VirtIO controller > I have another template that was created from a disk also with OS type of > Windows Server 2016 (64-bit) but has an ID controller. > > I am trying to work out why this happened and now I can make the disk > template always select the VirtIO controller. > Setting the instance to windows PV causes BSOD on boot, well before hal > can be redetected > > > Thanks > > Adam > > -Original Message- > From: Andrija Panic > Sent: 20 September 2018 11:18 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. Treat > hyperlinks and attachments in this email with caution. ** > > Sooo... here is my experience: > > if using correct VirtIO OS TYPE (set on template/VM) - i.e. ubuntu 14.04, > Centos 6.x or 7.x, Windows PV, other PV (but NOT centos 6.0 or 7.0 - these > "dot zero" versions are NOT virtio at least in ACS 4.8), then when VM is > STARTED FROM ACS (power on VM) - all drives should be attached as VirtIO. > > BUT if you do same as above, then additionally create and HOTPLUG new > drives/volumes to KVM - it will be IDE - some strange default behavior > during hotplug action just stop VM/start and it will become VirtIO > again... > > In order to "troubleshoot" these instances - you need to be careful to > which OS TYPE was the instance set to (this is inherited from TEMPLATE, if > you used some template - but it CAN be changed on an deployed& > instance) > > In case you plan to i.e. move your Windows instances from IDE to VirtIO - > be aware that it might fail miserably, and OS will fail to boot - but there > is a fix with *"* bcdedit /set detecthal boolean (where boolean is one of > 1, on, yes or true) " after which Windows will detect HAL again and boot > just fine. > > Let me know if more help needed > > Cheers > > On Thu, 20 Sep 2018 at 11:22, Adam Witwicki > wrote: > > > > > > > It looks like I can just add > > > > rootDiskController virtio > > > > To the templates settings tab? > > > > Can anyone confirm? > > > > Thanks > > > > Adam > > > > -Original Message- > > From: Ivan Kudryavtsev > > Sent: 20 September 2018 10:20 > > To: users > > Subject: Re: Disk controller type > > > > ** This mail originated from OUTSIDE the Oakford corporate network. > > Treat hyperlinks and attachments in this email with caution. ** > > > > Rakesh, It doesn't work like that for CS as it uses stateless XML > configs. > > > > чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh >: > > > > > I think you can change the controller type in XML file of the VM but > > > not sure if that works or not. > > > > > > virsh dumpxml > > > virsh edit > > > change the controller type, save and start the vm again > > > > > > On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki > > > > > > wrote: > > > > > > > Hello, > > > > > > > > I have a number of of instances using the wrong controller type > > > > (ATA) > > > does > > > > anyone know where this is set in the database so I can start them > > > > with > > > the > > > > VirtIO scsi controller? > > > > > > > > Thanks > > > > > > > > Adam > > > > > > > > > > > > > > > > > > > > Disclaimer Notice: > > > > This email has been sent by Oakford Technology Limited, while we > > > > have checked this e-mail and any attachments for viruses, we can > > > > not guarantee that they are virus-free. You must therefore take > > > > full responsibility for virus checking. > > > > This message and any attachments are confidential and should only > > > >
RE: Disk controller type
That didn’t format correctly Set this is the user_vm_details table Idvm_id name valuedisplay 3625 201rootDiskController virtio 1 -Original Message- From: Adam Witwicki Sent: 21 September 2018 10:59 To: users@cloudstack.apache.org Subject: RE: Disk controller type ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Ok, I have found were to force the controller type for a VM Set this is the user_vm_details table idvm_idnamevaluedisplay 3625201rootDiskControllervirtio1 My issue now is slipstreaming the windows ISO and the operating system bcdedit /set detecthal Boolean 1 isnt working for me Thanks Adam -Original Message- From: Adam Witwicki Sent: 21 September 2018 09:31 To: users@cloudstack.apache.org Subject: RE: Disk controller type ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Andrija, I have something weird, I have a template which uses the OS type of Windows Server 2016 (64-bit), this was imported into Cloudstack and this template uses a VirtIO controller I have another template that was created from a disk also with OS type of Windows Server 2016 (64-bit) but has an ID controller. I am trying to work out why this happened and now I can make the disk template always select the VirtIO controller. Setting the instance to windows PV causes BSOD on boot, well before hal can be redetected Thanks Adam -Original Message- From: Andrija Panic Sent: 20 September 2018 11:18 To: users Subject: Re: Disk controller type ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Sooo... here is my experience: if using correct VirtIO OS TYPE (set on template/VM) - i.e. ubuntu 14.04, Centos 6.x or 7.x, Windows PV, other PV (but NOT centos 6.0 or 7.0 - these "dot zero" versions are NOT virtio at least in ACS 4.8), then when VM is STARTED FROM ACS (power on VM) - all drives should be attached as VirtIO. BUT if you do same as above, then additionally create and HOTPLUG new drives/volumes to KVM - it will be IDE - some strange default behavior during hotplug action just stop VM/start and it will become VirtIO again... In order to "troubleshoot" these instances - you need to be careful to which OS TYPE was the instance set to (this is inherited from TEMPLATE, if you used some template - but it CAN be changed on an deployed& instance) In case you plan to i.e. move your Windows instances from IDE to VirtIO - be aware that it might fail miserably, and OS will fail to boot - but there is a fix with *"* bcdedit /set detecthal boolean (where boolean is one of 1, on, yes or true) " after which Windows will detect HAL again and boot just fine. Let me know if more help needed Cheers On Thu, 20 Sep 2018 at 11:22, Adam Witwicki wrote: > > > It looks like I can just add > > rootDiskController virtio > > To the templates settings tab? > > Can anyone confirm? > > Thanks > > Adam > > -Original Message- > From: Ivan Kudryavtsev > Sent: 20 September 2018 10:20 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. > Treat hyperlinks and attachments in this email with caution. ** > > Rakesh, It doesn't work like that for CS as it uses stateless XML configs. > > чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh : > > > I think you can change the controller type in XML file of the VM but > > not sure if that works or not. > > > > virsh dumpxml > > virsh edit > > change the controller type, save and start the vm again > > > > On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki > > > > wrote: > > > > > Hello, > > > > > > I have a number of of instances using the wrong controller type > > > (ATA) > > does > > > anyone know where this is set in the database so I can start them > > > with > > the > > > VirtIO scsi controller? > > > > > > Thanks > > > > > > Adam > > > > > > > > > > > > > > > Disclaimer Notice: > > > This email has been sent by Oakford Technology Limited, while we > > > have checked this e-mail and any attachments for viruses, we can > > > not guarantee that they are virus-free. You must therefore take > > > full responsibility for virus checking. > > > This message and any attachments are confidential and should only > > > be read by those to whom they are addressed. If you are not the > > > intended
RE: Disk controller type
Andrija, I have something weird, I have a template which uses the OS type of Windows Server 2016 (64-bit), this was imported into Cloudstack and this template uses a VirtIO controller I have another template that was created from a disk also with OS type of Windows Server 2016 (64-bit) but has an ID controller. I am trying to work out why this happened and now I can make the disk template always select the VirtIO controller. Setting the instance to windows PV causes BSOD on boot, well before hal can be redetected Thanks Adam -Original Message- From: Andrija Panic Sent: 20 September 2018 11:18 To: users Subject: Re: Disk controller type ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Sooo... here is my experience: if using correct VirtIO OS TYPE (set on template/VM) - i.e. ubuntu 14.04, Centos 6.x or 7.x, Windows PV, other PV (but NOT centos 6.0 or 7.0 - these "dot zero" versions are NOT virtio at least in ACS 4.8), then when VM is STARTED FROM ACS (power on VM) - all drives should be attached as VirtIO. BUT if you do same as above, then additionally create and HOTPLUG new drives/volumes to KVM - it will be IDE - some strange default behavior during hotplug action just stop VM/start and it will become VirtIO again... In order to "troubleshoot" these instances - you need to be careful to which OS TYPE was the instance set to (this is inherited from TEMPLATE, if you used some template - but it CAN be changed on an deployed& instance) In case you plan to i.e. move your Windows instances from IDE to VirtIO - be aware that it might fail miserably, and OS will fail to boot - but there is a fix with *"* bcdedit /set detecthal boolean (where boolean is one of 1, on, yes or true) " after which Windows will detect HAL again and boot just fine. Let me know if more help needed Cheers On Thu, 20 Sep 2018 at 11:22, Adam Witwicki wrote: > > > It looks like I can just add > > rootDiskController virtio > > To the templates settings tab? > > Can anyone confirm? > > Thanks > > Adam > > -Original Message- > From: Ivan Kudryavtsev > Sent: 20 September 2018 10:20 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. > Treat hyperlinks and attachments in this email with caution. ** > > Rakesh, It doesn't work like that for CS as it uses stateless XML configs. > > чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh : > > > I think you can change the controller type in XML file of the VM but > > not sure if that works or not. > > > > virsh dumpxml > > virsh edit > > change the controller type, save and start the vm again > > > > On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki > > > > wrote: > > > > > Hello, > > > > > > I have a number of of instances using the wrong controller type > > > (ATA) > > does > > > anyone know where this is set in the database so I can start them > > > with > > the > > > VirtIO scsi controller? > > > > > > Thanks > > > > > > Adam > > > > > > > > > > > > > > > Disclaimer Notice: > > > This email has been sent by Oakford Technology Limited, while we > > > have checked this e-mail and any attachments for viruses, we can > > > not guarantee that they are virus-free. You must therefore take > > > full responsibility for virus checking. > > > This message and any attachments are confidential and should only > > > be read by those to whom they are addressed. If you are not the > > > intended > > recipient, > > > please contact us, delete the message from your computer and > > > destroy any copies. Any distribution or copying without our prior > > > permission is prohibited. > > > Internet communications are not always secure and therefore > > > Oakford Technology Limited does not accept legal responsibility > > > for this > message. > > > The recipient is responsible for verifying its authenticity before > > > acting on the contents. Any views or opinions presented are solely > > > those of the author and do not necessarily represent those of > > > Oakford Technology > > Limited. > > > Registered address: Oakford Technology Limited, 10 Prince Maurice > > > Court, Devizes, Wiltshire. SN10 2RT. > > > Registered in England and Wales No. 5971519 > > > > > > > > > > -- > > Thanks and regards > > Rakesh venkatesh > > > Disclaimer Notic
Re: Disk controller type
Sooo... here is my experience: if using correct VirtIO OS TYPE (set on template/VM) - i.e. ubuntu 14.04, Centos 6.x or 7.x, Windows PV, other PV (but NOT centos 6.0 or 7.0 - these "dot zero" versions are NOT virtio at least in ACS 4.8), then when VM is STARTED FROM ACS (power on VM) - all drives should be attached as VirtIO. BUT if you do same as above, then additionally create and HOTPLUG new drives/volumes to KVM - it will be IDE - some strange default behavior during hotplug action just stop VM/start and it will become VirtIO again... In order to "troubleshoot" these instances - you need to be careful to which OS TYPE was the instance set to (this is inherited from TEMPLATE, if you used some template - but it CAN be changed on an deployed& instance) In case you plan to i.e. move your Windows instances from IDE to VirtIO - be aware that it might fail miserably, and OS will fail to boot - but there is a fix with *"* bcdedit /set detecthal boolean (where boolean is one of 1, on, yes or true) " after which Windows will detect HAL again and boot just fine. Let me know if more help needed Cheers On Thu, 20 Sep 2018 at 11:22, Adam Witwicki wrote: > > > It looks like I can just add > > rootDiskController virtio > > To the templates settings tab? > > Can anyone confirm? > > Thanks > > Adam > > -Original Message- > From: Ivan Kudryavtsev > Sent: 20 September 2018 10:20 > To: users > Subject: Re: Disk controller type > > ** This mail originated from OUTSIDE the Oakford corporate network. Treat > hyperlinks and attachments in this email with caution. ** > > Rakesh, It doesn't work like that for CS as it uses stateless XML configs. > > чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh : > > > I think you can change the controller type in XML file of the VM but > > not sure if that works or not. > > > > virsh dumpxml > > virsh edit > > change the controller type, save and start the vm again > > > > On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki > > > > wrote: > > > > > Hello, > > > > > > I have a number of of instances using the wrong controller type > > > (ATA) > > does > > > anyone know where this is set in the database so I can start them > > > with > > the > > > VirtIO scsi controller? > > > > > > Thanks > > > > > > Adam > > > > > > > > > > > > > > > Disclaimer Notice: > > > This email has been sent by Oakford Technology Limited, while we > > > have checked this e-mail and any attachments for viruses, we can not > > > guarantee that they are virus-free. You must therefore take full > > > responsibility for virus checking. > > > This message and any attachments are confidential and should only be > > > read by those to whom they are addressed. If you are not the > > > intended > > recipient, > > > please contact us, delete the message from your computer and destroy > > > any copies. Any distribution or copying without our prior permission > > > is prohibited. > > > Internet communications are not always secure and therefore Oakford > > > Technology Limited does not accept legal responsibility for this > message. > > > The recipient is responsible for verifying its authenticity before > > > acting on the contents. Any views or opinions presented are solely > > > those of the author and do not necessarily represent those of > > > Oakford Technology > > Limited. > > > Registered address: Oakford Technology Limited, 10 Prince Maurice > > > Court, Devizes, Wiltshire. SN10 2RT. > > > Registered in England and Wales No. 5971519 > > > > > > > > > > -- > > Thanks and regards > > Rakesh venkatesh > > > Disclaimer Notice: > This email has been sent by Oakford Technology Limited, while we have > checked this e-mail and any attachments for viruses, we can not guarantee > that they are virus-free. You must therefore take full responsibility for > virus checking. > This message and any attachments are confidential and should only be read > by those to whom they are addressed. If you are not the intended recipient, > please contact us, delete the message from your computer and destroy any > copies. Any distribution or copying without our prior permission is > prohibited. > Internet communications are not always secure and therefore Oakford > Technology Limited does not accept legal responsibility for this message. > The recipient is responsible for verifying its authenticity before acting > on the contents. Any views or opinions presented are solely those of the > author and do not necessarily represent those of Oakford Technology Limited. > Registered address: Oakford Technology Limited, 10 Prince Maurice Court, > Devizes, Wiltshire. SN10 2RT. > Registered in England and Wales No. 5971519 > > -- Andrija Panić
RE: Disk controller type
It looks like I can just add rootDiskController virtio To the templates settings tab? Can anyone confirm? Thanks Adam -Original Message- From: Ivan Kudryavtsev Sent: 20 September 2018 10:20 To: users Subject: Re: Disk controller type ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Rakesh, It doesn't work like that for CS as it uses stateless XML configs. чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh : > I think you can change the controller type in XML file of the VM but > not sure if that works or not. > > virsh dumpxml > virsh edit > change the controller type, save and start the vm again > > On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki > > wrote: > > > Hello, > > > > I have a number of of instances using the wrong controller type > > (ATA) > does > > anyone know where this is set in the database so I can start them > > with > the > > VirtIO scsi controller? > > > > Thanks > > > > Adam > > > > > > > > > > Disclaimer Notice: > > This email has been sent by Oakford Technology Limited, while we > > have checked this e-mail and any attachments for viruses, we can not > > guarantee that they are virus-free. You must therefore take full > > responsibility for virus checking. > > This message and any attachments are confidential and should only be > > read by those to whom they are addressed. If you are not the > > intended > recipient, > > please contact us, delete the message from your computer and destroy > > any copies. Any distribution or copying without our prior permission > > is prohibited. > > Internet communications are not always secure and therefore Oakford > > Technology Limited does not accept legal responsibility for this message. > > The recipient is responsible for verifying its authenticity before > > acting on the contents. Any views or opinions presented are solely > > those of the author and do not necessarily represent those of > > Oakford Technology > Limited. > > Registered address: Oakford Technology Limited, 10 Prince Maurice > > Court, Devizes, Wiltshire. SN10 2RT. > > Registered in England and Wales No. 5971519 > > > > > > -- > Thanks and regards > Rakesh venkatesh > Disclaimer Notice: This email has been sent by Oakford Technology Limited, while we have checked this e-mail and any attachments for viruses, we can not guarantee that they are virus-free. You must therefore take full responsibility for virus checking. This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Oakford Technology Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Oakford Technology Limited. Registered address: Oakford Technology Limited, 10 Prince Maurice Court, Devizes, Wiltshire. SN10 2RT. Registered in England and Wales No. 5971519
Re: Disk controller type
Controler depends on setyings, specified in template or os family used. So Windows guests don't receive virtio for network and storagr, thus they can be deployed without additional drivers. чт, 20 сент. 2018 г., 16:19 Ivan Kudryavtsev : > Rakesh, It doesn't work like that for CS as it uses stateless XML configs. > > чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh : > >> I think you can change the controller type in XML file of the VM but not >> sure if that works or not. >> >> virsh dumpxml >> virsh edit >> change the controller type, save and start the vm again >> >> On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki >> wrote: >> >> > Hello, >> > >> > I have a number of of instances using the wrong controller type (ATA) >> does >> > anyone know where this is set in the database so I can start them with >> the >> > VirtIO scsi controller? >> > >> > Thanks >> > >> > Adam >> > >> > >> > >> > >> > Disclaimer Notice: >> > This email has been sent by Oakford Technology Limited, while we have >> > checked this e-mail and any attachments for viruses, we can not >> guarantee >> > that they are virus-free. You must therefore take full responsibility >> for >> > virus checking. >> > This message and any attachments are confidential and should only be >> read >> > by those to whom they are addressed. If you are not the intended >> recipient, >> > please contact us, delete the message from your computer and destroy any >> > copies. Any distribution or copying without our prior permission is >> > prohibited. >> > Internet communications are not always secure and therefore Oakford >> > Technology Limited does not accept legal responsibility for this >> message. >> > The recipient is responsible for verifying its authenticity before >> acting >> > on the contents. Any views or opinions presented are solely those of the >> > author and do not necessarily represent those of Oakford Technology >> Limited. >> > Registered address: Oakford Technology Limited, 10 Prince Maurice Court, >> > Devizes, Wiltshire. SN10 2RT. >> > Registered in England and Wales No. 5971519 >> > >> > >> >> -- >> Thanks and regards >> Rakesh venkatesh >> >
Re: Disk controller type
Rakesh, It doesn't work like that for CS as it uses stateless XML configs. чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh : > I think you can change the controller type in XML file of the VM but not > sure if that works or not. > > virsh dumpxml > virsh edit > change the controller type, save and start the vm again > > On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki > wrote: > > > Hello, > > > > I have a number of of instances using the wrong controller type (ATA) > does > > anyone know where this is set in the database so I can start them with > the > > VirtIO scsi controller? > > > > Thanks > > > > Adam > > > > > > > > > > Disclaimer Notice: > > This email has been sent by Oakford Technology Limited, while we have > > checked this e-mail and any attachments for viruses, we can not guarantee > > that they are virus-free. You must therefore take full responsibility for > > virus checking. > > This message and any attachments are confidential and should only be read > > by those to whom they are addressed. If you are not the intended > recipient, > > please contact us, delete the message from your computer and destroy any > > copies. Any distribution or copying without our prior permission is > > prohibited. > > Internet communications are not always secure and therefore Oakford > > Technology Limited does not accept legal responsibility for this message. > > The recipient is responsible for verifying its authenticity before acting > > on the contents. Any views or opinions presented are solely those of the > > author and do not necessarily represent those of Oakford Technology > Limited. > > Registered address: Oakford Technology Limited, 10 Prince Maurice Court, > > Devizes, Wiltshire. SN10 2RT. > > Registered in England and Wales No. 5971519 > > > > > > -- > Thanks and regards > Rakesh venkatesh >
Re: Disk controller type
I think you can change the controller type in XML file of the VM but not sure if that works or not. virsh dumpxml virsh edit change the controller type, save and start the vm again On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki wrote: > Hello, > > I have a number of of instances using the wrong controller type (ATA) does > anyone know where this is set in the database so I can start them with the > VirtIO scsi controller? > > Thanks > > Adam > > > > > Disclaimer Notice: > This email has been sent by Oakford Technology Limited, while we have > checked this e-mail and any attachments for viruses, we can not guarantee > that they are virus-free. You must therefore take full responsibility for > virus checking. > This message and any attachments are confidential and should only be read > by those to whom they are addressed. If you are not the intended recipient, > please contact us, delete the message from your computer and destroy any > copies. Any distribution or copying without our prior permission is > prohibited. > Internet communications are not always secure and therefore Oakford > Technology Limited does not accept legal responsibility for this message. > The recipient is responsible for verifying its authenticity before acting > on the contents. Any views or opinions presented are solely those of the > author and do not necessarily represent those of Oakford Technology Limited. > Registered address: Oakford Technology Limited, 10 Prince Maurice Court, > Devizes, Wiltshire. SN10 2RT. > Registered in England and Wales No. 5971519 > > -- Thanks and regards Rakesh venkatesh
Disk controller type
Hello, I have a number of of instances using the wrong controller type (ATA) does anyone know where this is set in the database so I can start them with the VirtIO scsi controller? Thanks Adam Disclaimer Notice: This email has been sent by Oakford Technology Limited, while we have checked this e-mail and any attachments for viruses, we can not guarantee that they are virus-free. You must therefore take full responsibility for virus checking. This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Oakford Technology Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Oakford Technology Limited. Registered address: Oakford Technology Limited, 10 Prince Maurice Court, Devizes, Wiltshire. SN10 2RT. Registered in England and Wales No. 5971519
