Windows Server 2022 support

asked 2021-10-14 14:22:38 +0300

flowloic
1 ●1 ●2 ●1

Hi,

I'm trying to create an image for Windows Server 2022 using virtIO drivers and cloudbase init on Virtuozzo. I am able to create a VM and an image, but when I deploy a VM with it, it takes about 15 minutes for the VM to be ready. Same procedure with Windows Server 2019 deploys the VM in about 2 minutes.

The logs showed it was hanging for about 9 minutes while trying to change the ethernet adapters name: 2021-10-14 12:58:42.066 3544 INFO cloudbaseinit.plugins.common.networkconfig [-] Renaming network adapter "Ethernet" to "tap3b249609-32"

I know Windows Server 2022 is not yet supported, but do you have an estimate when that's going to change? Or is there a workaround?

BR, Loïc

edit retag flag offensive close merge delete

Comments

I am seeing this same behavior with the March 2023 version of Windows Server 2022 except I have a cmd box that just sits there forever (it never starts up). When I close the cmd prompt I get: Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified

sarhaynes ( 2023-04-12 00:08:24 +0300 )edit

The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Deployment].

sarhaynes ( 2023-04-12 00:09:32 +0300 )edit

Hello, can you please share the ISO name, your environment (hypervisor/OS versions/KVM/Libvirt versions/virtio driver versions) and the eventual errors that you are getting? I am interested in the logs present in C:\Windows\Panther folder. If you press SHIFT+F10, you ll get a CMD to navigate around

avladu ( 2023-04-12 09:10:44 +0300 )edit

add a comment

2 answers

Sort by » oldest newest most voted

answered 2023-04-17 18:17:31 +0300

sarhaynes
1

I have figured out to resolve the problems I was having: In the cloudbase-init-unattend.conf I had to remove the NetworkConfigPlugin, LocalScriptsPlugin, and NTPClientPlugin. Once I did this both issues I was having went away (long delay and constant reboot).

I also had to set allow_reboot to false in cloudbase-init.conf file (it was already false in cloudbase-init-unattend.conf).

edit flag offensive delete link

add a comment

answered 2021-10-15 00:22:17 +0300

avladu

613 ●1 ●3 ●5

Hello,

I have checked cloudbase-init run on Windows Server 2022 and everything looks fine. I could not reproduce any error related to networking or any other issue for that matter.

Windows Server 2022 is an incremental version, so there should not be any Windows API surface backward compatibility issues.

Can you please share any relevant information that can help debug the issue? if possible, can you share the following: Cloudbase-init logs, virtio driver version that you used, network metadata that had to be applied.

Thank you,
Adrian Vladu

edit flag offensive delete link

Comments

Hi Adrian, Thanks for your quick relpy! Well, yeah everything works fine otherwise, it's just the hang while deploying, very weird. I tried it with different virtio drivers (0.1.196 and 0.1.208), same behavior. How can I share the logs with you? The space here is rather limited. BR,

flowloic ( 2021-10-15 17:47:39 +0300 )edit

Pastebin works, if possible.

avladu ( 2021-10-18 13:37:35 +0300 )edit

Sure! https://pastebin.com/xXGXrAAL thx for the help!

flowloic ( 2021-10-18 14:04:03 +0300 )edit

Let me know if there's any other information you might need! The pastebin site has expired here is a new one: https://pastebin.com/qXZhzKvb BR

flowloic ( 2021-10-21 18:17:35 +0300 )edit

I tried a few things when creating the image but I always have the same issue. Any ideas what might be the cause? Were you able to check the logs?

flowloic ( 2021-11-04 11:02:52 +0300 )edit

see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Windows Server 2022 support

Comments

2 answers

Comments

Your Answer

Question Tools

Stats

Windows Server 2022 support edit

Comments

2 answers

Comments

Your Answer

Question Tools

Stats

Windows Server 2022 support