I have create a template for Windows Server 2019 and created a VM using that template. During the creation of the VM it ask for the driver installation . It is only showing the diver of windows 10, 8, 7 . I have downloaded the Windows virtio image from the opennebula appstore . How can I Create …

I was able to get Windows server 2019 to work, were you able to run this step from the docs? My ONE system is down right now while I’m doing some upgrades, I can check what was on the virtio driver CD when it’s back up. Are you able to tell if the NIC virtio drivers are loaded? Windows Download th…

@christaylor . I am able to create a VM for Windows Server 2019 . But the NIC is different , and the IP are also different from my KVM node NIC i.e It is giving me the default NIC of Realteak. So, how can we change the NIC and keep same as of the NIC of the node? What should we use for “Default ha…

If I understand you correctly, It looks like you have in your template is correct, where you say NIC_DEFAULT=[ MODEL="virtio" ] That’s what you want- the virtualized NIC (not the same as on your bare metal KVM server). As for the VM IP, it will pull a free address from the range in the vnet ass…

@christaylor So, why the NIC is assigning the different IP . I can see there is one context.sh file generated in of the Context Drive. There is the information for the interface i.e public, private IP. But the NIC is showing different IP. The Created VM template has the correct IP . NIC = [ AR_I…

@christaylor I have created a new template using the new one-context provided by you. Still it is showing different IP.

Hmm, something is strange with the configuration. An IP of 169.254.222.56 is a local address a host gets when it can’t get talk to a DHCP server, or something like that. Maybe you could check the output of the contextualization script on your Windows VM? I think it saves it in c:\one-context or som…

@christaylor There is output file of contextualization script in one of the directory. This file has got all the correct information regarding public IP , gateway and netmask. But this file is not being implement inside the VM and NIC is assigning 169.254.222.56 IP. Yes, I have tried with the sing…

I’m not sure why it’s not working for you- I’d say, just keep working with it. That IP you’re getting is like a failed DHCP request or something - I’m not sure. On one of my templates, after the VM boots I see this part in .onecontext\opennebula-context.log: Configuring Network Settings: Red Hat V…

Hi, @christaylor it is working now . I have change the context ios by lates one. Releases · OpenNebula/addon-context-windows · GitHub But I have to run win virtio exec file manually after login into the VM. After that only the NIC is visible. And it was assigning 169.254.xx.xx range IP. After that …

No, if the virtio NIC drivers are installed in the image and the contextualization script runs you shouldn’t have to do anything every time the VM boots- the virtio NIC should get set up for connectivity and assigned an IP. When you created the image the first time and booted Windows, were you able…

NIC is assigning different IP in Window server 2019 VM

Product Support

dont32 (Dont32) June 8, 2022, 8:12am 19

@nibatandukar I have same issue. Have you fixed?
IPV4 from gateway and ethernet is different

Topic		Replies	Views
How to create Windows VM? Product Support	53	28989	April 17, 2021
Gateway of different range is not working in KVM node Product Support	28	967	October 20, 2021
Windows contextualization problem Product Support	25	5958	September 26, 2017
Installing Windows Server 2016 on OpenNebula 5.6.1 (nested virtualization) Installation & Configuration	5	4097	November 21, 2018
Opennebula Windows VM VirtIo Scsi Installation Error Product Support	7	810	October 12, 2023

NIC is assigning different IP in Window server 2019 VM

Related topics