windows 10 1909 and 1903 build issue

[vijaykumay]

Hi Team,
I'm trying to build windows 10 1909 build using cloudbase tool, the image creation happens successfully, after uploading the image to openstack and when i try to create a VM from the image i get the below error.

"windows setup experienced an unexpected error to install windows restart the installation"

can someone help me

Regards
vijay

[ader1990]

Hello,

This error can be debugged by checking the logs from C:\Windows\Panther.

When you get this error, press Shift+F10 to open a CMD window and navigate to the folder using:
"cd C:\Windows\Panther". PowerShell can be also started from the cmd, while notepad.exe can be used to open the log files.

Can you share the following log files, if possible (print screens with any relevant errors in those logs would be fine too)?
C:\Windows\Panther\setupact.log
C:\Windows\Panther\setuperr.log
C:\Windows\Panther\UnattendGC\setupact.log
C:\Windows\Panther\UnattendGC\setuperr.log

It would be great if you can give more details on what Cloudbase-Init version you used, if you syspreped the system using the installer's Unattend.xml (the workflow you followed when you created the image).

Thank you,
Adrian

[vijaykumay]

Hi Adrian,

we are using Cloudbase-Init 1.1 and using unattend.xml file for doing sysprep

following is the screen shot of C:\Windows\Panther\setupact.log, but is there any way i can share you the logs from the vnc console.

[ader1990]

Hi Adrian,

we are using Cloudbase-Init 1.1 and using unattend.xml file for doing sysprep

following is the screen shot of C:\Windows\Panther\setupact.log, but is there any way i can share you the logs from the vnc console.

can you please share the last lines, preferably of the error log files first? the first lines are usually with no error logs :)

[vijaykumay]

Hi Adrain,

[vijaykumay]

Hi A

drain,
last few line of setupacct.log file

[ader1990]

In this case, the relevant error message might be "0xc0000005 Access violation".
Can you detail on what is the hypervisor type and the vm specs (ram to be more specific)?

Windows machines require a compatible hypervisor (like qemu with kvm acceleration) and a decent amount of RAM (minimum 2GB for 64-bit Window 10): https://support.microsoft.com/en-us/help/4028142/windows-10-system-requirements .

[vijaykumay]

Hi Adrain.

we are using openstack ocata with KVM as an hypervisor .
windows VM has 4GB RAM 4 cores and 40GB HDD

[ader1990]

At this moment, I can suggest you to try to bump the RAM to 6 or 8GB to see if the error is reproduceable.

Also make sure that all the latest Windows updates have been applied, that there are no more pending updates and a reboot has been performed each time an update has been applied (even if the updates did not request a reboot). Then it is safe to install Cloudbase-Init and sysprep.

This is a great tool to create reliably and reproducibly Windows images:
https://github.com/cloudbase/windows-openstack-imaging-tools/

[vijaykumay]

Hi Adrain,

i use the same tool to create the images , i have been using this from past 2 years and its an excellent tool for creating windows images, this is the first time i'm getting this error for windows 10 1909 build
https://github.com/cloudbase/windows-openstack-imaging-tools/

i will try to create a new VM with 8GB RAM.

[vijaykumay]

Hi Adrain,

we tried creating new windows VM with 8GB RAM still the same issue

[ader1990]

Can you share the Windows ISO full name that you used?

I would like to see if the problem can be reproduced on another environment, to exclude the possibility of Windows (updates/kvm compatibility/virtual hardware) to be actually broken.

Thanks.

[vijaykumay]

Hi Adrain,

we are using the below ISO

Microsoft_Windows_Enterprise_10_1903_64BIT.ISO

[vijaykumay]

Hi Adrain,

i have seen the issue with both the windows 10 build 1909 and 1903.

Regards,
vijay

[ader1990]

Thank you for the information. One more thing: what virtio version did you use? To exclude that moving part too.

[vijaykumay]

Hi Adrain,

I have tried both 0.1.1 and 0.1.173

[vijaykumay]

Hi Adrain,
did you get a chance to replicate the issue.

Regards,
vijay

[ader1990]

Hello,

I tested the Windows 10 1909 with Virtio drivers 0.1.171 on an Ubuntu 18.04 baremetal machine with KVM, using host-passthrough, and it booted successfully (although it took a while to first boot). Qemu-kvm version was 2.11.

In this case, the problem seems to not reside in cloudbase-init or the imaging tools.

This is most likely a hypervisor issue or an incompatibility between your hypervisor version and Windows 10. You can try to debug this further looking at the KVM logs or trying to use another cpu model.

[vijaykumay]

Hi Adrain,

thanks a lot for testing.

we are running openstack ocata and ubunut 16.04 version.

regards,
vijay

[vijaykumay]

Hi Adrian,

can you please help me with image you build, i can try it in our openstack cloud for testing

Regards,
vijay

[ader1990]

I cannot upload publicly / send you the image directly, as there are licensing / legal issues on that matter. I can suggest you get in touch with the Cloudbase team for further professional help.

[vijaykumay]

Hi Adrian,

I understand, let me check with cloudbase team.

Regards,
vijay