git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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 <awitwicki@xxxxxxxxxxxxx> 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
>
>     <disk type='file' device='disk'>
>       <driver name='qemu' type='raw' cache='none'/>
>       <source file='/home/user/blank.img'/>
>       <backingStore/>
>       <target dev='vdc' bus='virtio'/>
>       <readonly/>
>       <alias name='virtio-disk1'/>
>       </disk>
>
> Attach this disk to the running VM
>
> Virsh
> attach-device <VM internal name> /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 <andrija.panic@xxxxxxxxx>
> Sent: 21 September 2018 16:50
> To: users <users@xxxxxxxxxxxxxxxxxxxxx>
> 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 <sweller@xxxxxxx.invalid> 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 <awitwicki@xxxxxxxxxxxxx>
> > Sent: Friday, September 21, 2018 5:28 AM
> > To: users@xxxxxxxxxxxxxxxxxxxxx
> > 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 <andrija.panic@xxxxxxxxx>
> > Sent: 21 September 2018 11:25
> > To: users <users@xxxxxxxxxxxxxxxxxxxxx>
> > 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 <awitwicki@xxxxxxxxxxxxx>
> 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 <andrija.panic@xxxxxxxxx>
> > > Sent: 20 September 2018 11:18
> > > To: users <users@xxxxxxxxxxxxxxxxxxxxx>
> > > 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&&stopped
> > > 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
> > > <awitwicki@xxxxxxxxxxxxx>
> > > 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 <kudryavtsev_ia@xxxxxxxxx>
> > > > Sent: 20 September 2018 10:20
> > > > To: users <users@xxxxxxxxxxxxxxxxxxxxx>
> > > > 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
> > > ><<http://>www.rakeshv.com@xxxxxxxxx
> > > >:
> > > >
> > > > > I think you can change the controller type in XML file of the VM
> > > > > but not sure if that works or not.
> > > > >
> > > > > virsh dumpxml <vm name>
> > > > > virsh edit <vm name|domain>
> > > > > change the controller type, save and start the vm again
> > > > >
> > > > > On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki
> > > > > <awitwicki@xxxxxxxxxxxxx>
> > > > > 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ć
> > > 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
> > >
> > >
> > 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
> >
> >
> 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
>
>