[Openstack-operators] VirtIO and IDE disk

Pouliot.net peter at pouliot.net
Fri Aug 12 21:01:50 UTC 2016


Sounds like you should just use this:

https://cloudbase.it/coriolis/

P


> On Aug 12, 2016, at 3:29 AM, Emilio Moreno Fernandez <emilio.moreno at adam.es> wrote:
> 
> Hi Edmund,
>  
> Thank you for your explanations.
>  
> But I need to know how to inject drivers to a Windows Server 2012 that has installed in other platform without VirtIO, like Vmware ESX. I have a lot of migrations of clients to our Openstack Platform with Windows Server 2012 R2 system.
>  
> Install like legacy hardware it does not work correctly, and install dirvers manually either. This process it works with any version of Windows, boot like hda, install drivers, shutoff and boot like vda. In 2012 CRASH!
>  
> Thanks
>  
> De: Edmund Rhudy (BLOOMBERG/ 120 PARK) [mailto:erhudy at bloomberg.net] 
> Enviado el: miércoles, 10 de agosto de 2016 15:41
> Para: Emilio Moreno Fernandez
> CC: openstack-operators at lists.openstack.org
> Asunto: Re: [Openstack-operators] VirtIO and IDE disk
>  
> (Sorry, this got sent prematurely.)
> 
> Hi Emilio,
> 
> I had to solve getting Windows 2012 running in KVM recently and was able to do so with this nova boot command:
> 
> nova boot \
> --image [[WINDOWS 2012 INSTALL MEDIA]] \
> --block-device source=blank,dest=volume,size=40,shutdown=preserve,device=vda \
> --block-device source=image,dest=volume,size=1,shutdown=remove,id=[[ ID OF VIRTIO DRIVER DISC ]],type=cdrom \
> --flavor m1.medium \
> INSTANCE_NAME_GOES_HERE
> 
> This ran the Windows 2012 installer, attaching the virtio driver disc (https://fedoraproject.org/wiki/Windows_Virtio_Drivers) as another CD and a 40GB install destination at vda. After the install was done and the instance was sysprepped and configured appropriately, I shut it down, snapshotted it, and made an image from that. If you can do the Windows installation inside OpenStack instead of importing a VMDK from elsewhere, this should let you produce an instance that works correctly with QEMU/KVM virtio for storage and networking.
>  
> From: emilio.moreno at adam.es
> Subject: Re: [Openstack-operators] VirtIO and IDE disk
> Hi Peter,
>  
> Drivers are correct for Windows 2012 R2, if I install one server with 2012 ISO disk and VirtIO ISO to volume. All it’s ok!
> But...if I receive one vmdk image, I convert it to raw and launch it with ide bus on hda...but i want lauch it with virtio bus.
>  
> Boot the instance...install virtio driver for Windows 2012 R2 of last ISO from fedora like “legacy hardware” and shutoff...at the next boot...BSOD of Windows 2012.
>  
> This process it’s ok with Windows 2008 R2, Windows XP, Windows 2003, Windows 7 and Windows 8.
>  
>  
> One solution is launch volume in my PC with KVM local install, I can launch instance with two volumes, first IDE hda volume with system and second volume like vdc VirtIO. When I boot system, I can install drivers for second VirtIO volume and then I can launch system volume like VirtIO VDA without problems. I think that Windows install driver correctly with virtio volume attached.
>  
>  
> Finally, I want to launch one instance in Openstack JUNO, with two volumes, one IDE HDA and second VirtIO like vdc for example. I can’t launch instance like this, this is my last option because manually install of drivers on Windows 2012 installed and migrated fail.
>  
> Thanks
>  
> _________________________________________________________________________
>  
> Emilio Moreno Fernández
> Departamento de Sistemas
>  
> c/ Artesans, 7 - Parc Tecnològic del Vallès
> 08290 Cerdanyola del Vallès - Barcelona
>  
> Tel.  902 902 685
> E-mail. emilio.moreno at adam.es
> www.adam.es
>  
> <image001.png> LinkedIn  |   <image002.png> @Adam_TIC 
>  
>  
> <image003.png> 
>  
> De: Pouliot.net [mailto:peter at pouliot.net] 
> Enviado el: lunes, 08 de agosto de 2016 19:05
> Para: Emilio Moreno Fernandez
> CC: openstack-operators at lists.openstack.org
> Asunto: Re: [Openstack-operators] VirtIO and IDE disk
>  
> Sounds like you need to use the correct paravirtualization drivers for the hypervisor you are using.   I highly suggest you create the Windows vm on that hypervisor with certified paravirtualization drivers from the vendor of the Linux distribution you are using. 
>  
> If you have more questions, email me here: Openstack at microsoft.com and I'll setup a call.
>  
> P
> 
> On Aug 8, 2016, at 9:30 AM, Emilio Moreno Fernandez <emilio.moreno at adam.es> wrote:
> 
> Hi all,
>  
> We have very problems to launch Windows Server 2012 without viostor driver.
> I can launch with “hda” and install drivers but before we have BSOD on Windows.
>  
> It’s possible launch instance with one volume on hda and other volume with vdc for example to install drivers without legacy software?
>  
> How I can to resolve this with glance image of Windows imported from ESX Server. (VirtIO drivers are in C:\ )
>  
> Thanks
>  
> _________________________________________________________________________
>  
> Emilio Moreno Fernández
> Departamento de Sistemas
>  
> c/ Artesans, 7 - Parc Tecnològic del Vallès
> 08290 Cerdanyola del Vallès - Barcelona
>  
> Tel.  902 902 685
> E-mail.emilio.moreno at adam.es
> www.adam.es
>  
> <image001.png> LinkedIn  |   <image002.png> @Adam_TIC 
>  
>  
> <image003.png> 
>  
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>  
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160812/43459900/attachment.html>


More information about the OpenStack-operators mailing list