Open Stack

Kris;

I also use Windows extensively for OpenStack instances.  I have never been able to boot a Windows image with --property hw_firmware_type=uefi.  It hasn't been important enough, to this point, to troubleshoot.  Windows Server 2012 boots fine without UEFI though.  We use Victoria on CentOS 8, and Ubuntu 20.10.

It would be a good idea to install virtio drivers into the image, and use some other parameter for hw_disk_bus.  I believe ide makes qemu software emulate and IDE interface. What you choose here will partly depend on where / how you store your images and volumes.

Thank you,

Dominic L. Hilsbos, MBA
Vice President – Information Technology
Perform Air International Inc.
DHilsbos at PerformAir.com  
www.PerformAir.com


From: KK CHN [mailto:kkchn.in at gmail.com] 
Sent: Thursday, August 19, 2021 5:10 AM
To: openstack-discuss at lists.openstack.org
Subject: Re: Windows2012 VM image importing and Instance Launch Failure


On Thu, Aug 19, 2021 at 12:30 PM Eugen Block <eblock at nde.ag> wrote:
Hi,

to launch windows VMs in openstack you need virtio drivers [2], see  
[1] for an example.

Is this  virtiio drivers applicable to launch   new  Windows  virtual machines y from downloaded ISOs only ?   Or  as in my case   I am exporting  from hyperV . The file I got   is vhdx file and I converted it to qcow2 format.  Is the virtio drivers  hack required for exported(from other hypervisors) Windows images also ? to import it to openstack.

if so     The step mentioned  here        https://docs.openstack.org/image-guide/windows-image.html

1. 
a. $ qemu-img create -f qcow2 ws2012.qcow2 15G
Is this step needed for  other hypervisor exported  WindowsVM image which converted by me already in qcow2 format ?   what the relevance of 15G in my case of  qcow2 format  WIndows Single disk images  which is 17G in qcow2 format ?  


2.   Step 2  In  mycase 
what need to be  edited  here so that it successfully can be imported to OpenStack and running . 

# virt-install --connect qemu:///system \
  --name ws2012 --ram 2048 --vcpus 2 \
  --network network=default,model=virtio \
  --disk path=ws2012.qcow2,format=qcow2,device=disk,bus=virtio \
  --cdrom /path/to/en_windows_server_2012_x64_dvd.iso \
  --disk path=/path/to/virtio-win-0.1-XX.iso,device=cdrom \
  --vnc --os-type windows --os-variant win2k12 \
  --os-distro windows --os-version 2012

  

That file size ( 17 GB  in qcow2 format, in bare KVM when I imported successfully  its booted and disk space  around 500 GB ) .  





 
I haven't done that in quite some time, but I remember after following  
that guide I was able to launch a windows VM.

Regards,
Eugen


[1] https://docs.openstack.org/image-guide/windows-image.html
[2]  
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso

Zitat von KK CHN <kkchn.in at gmail.com>:

> Error : failed to perform requested operation on instance "WindowsVM "the
> instance has error status. Please try again later [Error exceeded maximum
> number of retries. Exhausted all hosts available for retrying build
> failures for instance e3d5c095-7d26-4b1e-89d1-d1a6e20a45041
>
> I am trying to import a WIndows2012 Single disk VM, to OpenStack Ussuri,
> with glance and Qemu KVM.
>
> In bare machine KVM I am able to import and boot this Windows VM which
> exported from rhevm hypervisor as  vhdx image.
> what I have done is
>
> 1. converted this windows  image from vhdx to qcow2
> 2.  root at MeghCtrol1:/home/cloud/CMOBB_APP#cirt-install --name WINDOWS
> --ram=1048 --vcups=1 --cpu host --hvm --dick
> path=BackUP2_CMAPP_disk_1_Windows_qcow2_imagefile,device=disk,
> format=qcow2,bus=virtio --graphics vnc --boot uefi
>
> This uploaded the qcow2 image of WindowsVM to  KVM  hypervisor and its
> working.
>
> But when I do importing to openstack   unable to launch  instance from the
> image .
>
> These are the steps I performed..
>
> 1. openstack image create "WindowsVM" --file CMAPP_disk_1.qcow2
> --disk-format qcow2 --container-format bare --public
>
> 4.openstack image set --property hw_firmware_type=uefi --property
> os_secure_boot=required WindowsVM
>
> 5.openstack image set --property hw_firmware_type=uefi --property
> hw_disk_bus=ide WindowsVM
>
> 6.openstack image show WindowsVM
>
> 7. root at dmzcloud:/home/cloud# openstack image show WindowsVM|grep
> "properties"
> | properties       | hw_disk_bus='ide', hw_firmware_type='uefi',
> os_hash_algo='sha512',
> os_hash_value='753ee596980409e1e72d6d020c8219c56a6ada8b43f634fb575c594a245725a398e45982c0a1ad72b3fc3451cde62cceb9ff22be044863b31ecdd7893b049349',
> os_hidden='False', os_secure_boot='required',
> owner_specified.openstack.md5='',
> owner_specified.openstack.object='images/WindowsVM',
> owner_specified.openstack.sha256='' |
> root at dmzcloud:/home/cloud#
>
>
> Then  I logged into horizon dashboard,  from the images  selected the
> imported image and try to launch the instance.  With  a Flavour of 550 GB
> disk, 4 vcpus and 8GB Ram ..
>
> The instance spawning ran for 30 minutes and throws the error which I
> pasted first in the right top corner of horizon dashboard.
>
> How to solve this error and boot the Windows machine successfully ..
>
>
> """
> Error : failed to perform requested operation on instance "WindowsVM "the
> instance has error status. Please try again later [Error exceeded maximum
> number of retries. Exhausted all hosts available for retrying build
> failures for instance e3d5c095-7d26-4b1e-89d1-d1a6e20a45041
>
>
> """
>
> Any help highly appreciated.
>
> Kris