Creating Windows 7 Image - Setup Error on first boot
I created a windows 7 image. I configured it to use virtio disk and network adapter using the 1-74 drivers. Updated to SP1. I also installed cloud init for windows. Tested it locally ok. I uploaded to my org's OpenStack cloud.
Created the disk like so
- qemu-img create -f qcow2 -o preallocation=metadata myfile.qcow2 20G
Created images through Virtual Machine Manager and also tried through terminal like this:
- sudo qemu-system-x86_64 -enable-kvm -m 4096 -cdrom [my.iso] -drive file=myfile.qcow2,if=virtio -drive file=virtio-win-0.1-74.iso,index=3,media=cdrom -net nic,model=virtio -net user -nographic -vnc :9 -usbdevice tablet
Upload to Glance
- glance image-create --name myname --container-format bare --disk-format qcow2 --is-public True --file myfile.qcow2 --progress
When I tried to create an instance I got the following error visible from the console:
Windows Setup could not configure Windows to run on this computer's hardware.
I acknowledged the error, the vm rebooted and now it's constantly showing the following error while trying to boot the OS:
Windows could not complete the installation. To install Windows on this computer, restart the installation.
I tried creating a brand new image with no windows updates or SP, no cloudbase-init: virtio drivers + basic sysprep only, and I'm still getting the error!
Reading from http://support.microsoft.com/kb/2466753 (this KB) I retrieved the log files, which look like this:
setuperr.log
- Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:WindowsSystem32scecli.dll,SceSysPrep', returned error code 1208[gle=0x000003e5]
- Error [0x060435] IBS Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x4b8
- Error [0x0603f1] IBS Module_Term_ImageTransfer: Failed to disable the image selection UI; status 0x80070005[gle=0x00000005]
- Error [0x0601b8] IBS Module_Term_DiskSpace:Failed to set the disk config UI flag.[gle=0x00000005]
setupact.log
Find the full log file here: https://ebay.box.com/s/rcurb79xesbuervlbtat (https://ebay.box.com/s/rcurb79xesbuer...)
I won't list the whole file here, but there was entry like the one described in the KB article. The closest entry was this:
- 2014-04-10 08:36:13, Info SYSPRP SPPNP: The function driver iaStorV is not in use.
Workaround
As a temporary workaround I can do the following to the broken instance to get it to work. However, I need a permanent solution so that the error doesn't come up in the first place.
- On error screen press SHIFT-F10 to bring up command prompt.
- Run CD C:\windows\system32\oobe\msoobe
Please help, I've been trying to get this to work for 2 weeks now!
