-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to build Windows Image due to error : Qemu stdout: !!!! X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - 00000000 !!!! #267
Comments
Eventually it got failed with below errors: ImageBase=000000007FA67000, EntryPoint=000000007FAA7503) !!!! 2024/09/11 06:57:42 machine readable: error-count []string{"1"} ==> Some builds didn't complete successfully and had errors: ==> Builds finished but no artifacts were created. |
@jurekh , @alexsander-souza : Could you please look into it as this is a blocker for us to use MAAS in production. |
this relates to this already closed issue: #252 |
is also reproducible with other iso e.g. windows server 2022.
|
@erickellerek1 : Correct I tried with 2019 and 2022 and the same issue is replicable. Although #252 is closed but the issue is still there. |
I cannot reproduce this in my env: Windows Server 2022 downloaded from https://go.microsoft.com/fwlink/p/?LinkID=2195280&clcid=0x409&culture=en-us&country=US
This might not be an issue related to the packer template, but to the combination of the HW platform and qemu that you're using. Can you try another environment to help isolate the cause? Update: added |
Will try and check but below are details of my setup:
|
If anyone is looking for a workaround, it's been reported that performing the build on Ubuntu 24.04 doesn't run into the exception. |
Image Building worked fine, but while provisioning the OS from same, it failed with below errors: Running command ['sh', '-cf', 'wget "$1" --progress=dot:mega -O - |smtar -C "$2" --xattrs --xattrs-include=* -Sxpf - --numeric-owner', '--', 'http://192.168.103.11:5248/images/6cae7a18f76457c2e29d611017514cbf4f801df4c0b1f1db7bf7d35a4da59db1/custom/amd64/generic/cloudlyte-win2k19/uploaded/root.tgz', '/tmp/tmplkx33zym/target'] with allowed return codes [0] (capture=False)
tar: Skipping to next header Cannot write to ‘-’ (Broken pipe).
Stderr: '' |
I am having all the issues mentioned above. the latest commit also resulted in failure. I am building a ubuntu 24 VM now to try this. Thanks for suggestion. I will update here if successful to back you up. |
Hello Guys. Just an update, after wasting a week on the problem, and a day working on ubuntu 24, I can confirm the above solution mentioned by the user works. If you are getting frustrated as me on ubuntu22 please try ubuntu 24 for successful builds. Thank You |
@nics90 I got the image working by making new image . I had to make changes in pkr.hcl file. Can't find the another thread in which we were having conversation for the problem tar: This does not look like a tar archive |
I have posted the script in a different issue. please read it. |
Hello Everyone! Please note that Windows images are not tar.gz. They are DD images and need to be imported accordingly in MAAS. Please see the README file for an example also this:
|
This issue is stale because it has been open for 30 days with no activity. |
Hi, I'm trying to create a Windows Server 2019 image but I'm getting the below error:
The text was updated successfully, but these errors were encountered: