Windows 10 VM - IP address

Hi,

I have created a VM with Windows 10 pro.

The network is not getting the Public IP from opennebula.

Any ideas ?

HYPERVISOR = "kvm"
Template
AUTOMATIC_DS_REQUIREMENTS = "“CLUSTERS/ID” @> 0"
AUTOMATIC_REQUIREMENTS = "(CLUSTER_ID = 0) & !(PUBLIC_CLOUD = YES)"
CONTEXT = [
DISK_ID = “1”,
ETH0_CONTEXT_FORCE_IPV4 = “”,
ETH0_DNS = “8.8.8.8”,
ETH0_GATEWAY = “81.xxx.xxx.xxx”,
ETH0_GATEWAY6 = “”,
ETH0_IP = “81.xxx.xxx.xxx”,
ETH0_IP6 = “”,
ETH0_IP6_ULA = “”,
ETH0_MAC = “02:00:51:c4:9d:3b”,
ETH0_MASK = “255.255.255.224”,
ETH0_MTU = “”,
ETH0_NETWORK = “”,
ETH0_SEARCH_DOMAIN = “”,
ETH0_VLAN_ID = “11”,
ETH0_VROUTER_IP = “”,
ETH0_VROUTER_IP6 = “”,
ETH0_VROUTER_MANAGEMENT = “”,
NETWORK = “YES”,
TARGET = “hdb” ]
CPU = "2"
DISK = [
CLONE = “NO”,
CLONE_TARGET = “SYSTEM”,
CLUSTER_ID = “0”,
DATASTORE = “nfs_images”,
DATASTORE_ID = “122”,
DEV_PREFIX = “hd”,
DISK_ID = “0”,
DISK_SNAPSHOT_TOTAL_SIZE = “0”,
DISK_TYPE = “FILE”,
DRIVER = “qcow2”,
IMAGE = “Win10_OS”,
IMAGE_ID = “25”,
IMAGE_STATE = “8”,
IMAGE_UNAME = “oneadmin”,
LN_TARGET = “NONE”,
ORDER = “1”,
PERSISTENT = “YES”,
READONLY = “no”,
SAVE = “YES”,
SIZE = “32768”,
SOURCE = “/var/lib/one//datastores/122/267e1b1989c550b90907502d4030130e”,
TARGET = “hda”,
TM_MAD = “shared”,
TYPE = “FILE” ]
FEATURES = [
ACPI = “yes”,
APIC = “yes”,
LOCALTIME = “yes” ]
GRAPHICS = [
LISTEN = “0.0.0.0”,
PORT = “5986”,
TYPE = “VNC” ]
MEMORY = "4096"
NIC = [
AR_ID = “0”,
BRIDGE = “br0”,
CLUSTER_ID = “0”,
DNS = “8.8.8.8”,
GATEWAY = “81.xxx.xxx.xxx”,
IP = “81.xxx.xxx.xxx”,
MAC = “02:00:51:c4:9d:3b”,
NETWORK = “Public Network”,
NETWORK_ID = “9”,
NETWORK_MASK = “255.255.255.224”,
NIC_ID = “0”,
SECURITY_GROUPS = “0”,
TARGET = “one-86-0”,
VLAN_ID = “11”,
VN_MAD = “dummy” ]
OS = [
ARCH = “x86_64”,
BOOT = “disk0” ]
RAW = [
DATA = “DATA=“core2duo”,
TYPE=“kvm””,
TYPE = “kvm” ]
SECURITY_GROUP_RULE = [
PROTOCOL = “ALL”,
RULE_TYPE = “OUTBOUND”,
SECURITY_GROUP_ID = “0”,
SECURITY_GROUP_NAME = “default” ]
SECURITY_GROUP_RULE = [
PROTOCOL = “ALL”,
RULE_TYPE = “INBOUND”,
SECURITY_GROUP_ID = “0”,
SECURITY_GROUP_NAME = “default” ]
TEMPLATE_ID = "14"
VCPU = "2"
VMID = “86”

Hi! Try use PS script without startup.vbs script. In Windows Serevr 2012 R2 with last updates startup.vbs not work. I use only context.ps1.

P.S. Sorry for my English.

I have the same problem… I try running the ps script only but it did not work. It look like the windows context did not support windows 10, can some one give a answer regarding this issue.

TQ In Advance.

Hi

Firstly, you’ll need to include context.ps1 in your template (FILES parameter in CONTEXT section), unless you have context.ps1 included in the image somewhere.

What happens if you run context.ps1 manually?

(i.e. d:\context.ps1 from an administrative powershell prompt). What are the error messages?

If this works, then the issue is likely to be calling context.ps1 at startup. I normally configure a login command in unattend.xml for this, but there are multiple ways of doing this.

Hi

Thank for replay… I already setup files parameter inside the CONTEXT section.
FYI, the ip is change if i run the context.ps1. The problem is it notwork while bootup.
Can you share how you configure the login command in unattend.xml

Sure.

The XML looks like this -

<settings pass="oobeSystem">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
        <FirstLogonCommands>
            <SynchronousCommand wcm:action="add">
                <CommandLine>powershell.exe -executionpolicy unrestricted -c &quot;&amp; { $p=((gwmi win32_volume | ? { $_.label -eq &apos;CONTEXT&apos; }).name + &apos;context.ps1&apos;);if (test-path $p) { &amp; $p } }&quot;</CommandLine>
                <Order>1</Order>
                <Description>Contextualize VM before continuing</Description>
            </SynchronousCommand>
        </FirstLogonCommands>
    </component>
</settings>

However, it’s probably much easier to simply install the new context msi package which will do all of this for you.

Here: https://opennebula.org/new-contextualization-packages-2/

Cheers