cvargashbs
Contributor
Contributor

Linked Clones with Disconnected Network Card

I have an interesting issue. I am deploying a new View environmnet with View 4.5 and after I create a new pool and try to deploy the linked clones, the they are created and the Network card setting is not selected to connect on power on or set as connected. I have to manually go to each linked clone and click the option to set connect on power on for the network card.

Setup

2 x ESXi server 4.1 (HP DL360G7)

Distributed Switch (Intel Cards) 4 Uplinks dedicated for View Desktops

View 4.5

OS: Windows XP SP3 with all the patches.

After I manually check the Connect to the Network Option everything works ok , but I have to deploy 300 VM's and I don't want to do this 300 times.

Thanks

9 Replies
kgsivan
VMware Employee
VMware Employee

Please verify the following.

Go the the parent VM and revert to the snapshot which is used for linked clone.

Edit Vm settings and check whether the network configuration enabled "Connected" and "Connect when Powering on"

Please confirm if it is enabled for the parent VM snapshot state

0 Kudos
idle-jam
Immortal
Immortal

sivaprasad is right. also without network the quickprep in the linked mode will not work as well. therefore it is essential to get it up and running and the only possible reason is that the connect when powering on is not enabled.

0 Kudos
arjanhs
Enthusiast
Enthusiast

What type of port binding are you using on you distributed switches, have similar issues and for me only the static binding is working.

0 Kudos
EAIabach
Contributor
Contributor

Has anyone found any answers on this?  I am seeing this issue as well.  My template / parent VM is set to connect to the network at power on.  The issue is sporadic, but I have VMs being cloned that do not have their vnic's connected.

I am using API call to deploy the VMs.

0 Kudos
bwilsor
Contributor
Contributor

I ran into a similar situation a while back.  the difference being that the VMs network would disconnect when it was being migrated to a different host.  The resolution was to increase the number of ports on the vSwitch that each host connected to.  The problem, if I remeber correctly, was that the vSwitch on the host ran out of available ports that the VMs could use.

0 Kudos
klauzser
Contributor
Contributor

similar case... if you will run a hundred VM's, it would be time consuming if you will do the whole step hundred times.. Smiley Sadhttps://imagicon.info/cat/5-59/vmware-cool.gif

0 Kudos
MarkWalters
Contributor
Contributor

I too am having this issue.

  • ESXi 5
  • vCenter 5 ODF Application from the VMWare website
  • Using the vSphere 5 SDK
  • C# .NET project to access the API

I'm using a simple VMClone_Task to create the linked clone. The original snapshot has the network adapter enabled, but the linked clone does not have the adapter enabled at power on - even if I explicitly specify for the adapter to be enabled at startup using the config below:

VirtualMachineCloneSpec cloneSpec = new VirtualMachineCloneSpec
{
    location = new VirtualMachineRelocateSpec { diskMoveType = "createNewChildDiskBacking" },
    powerOn = false,
    template = false,
    snapshot = snapshotRef,
    customization = new CustomizationSpec
    {
        globalIPSettings = new CustomizationGlobalIPSettings(),
        identity = new CustomizationSysprep
        {
            guiUnattended = new CustomizationGuiUnattended
            {
                password = new CustomizationPassword
                {
                    plainText = true,
                    value = [REDACTED],
                },
                autoLogon = false,
                autoLogonCount = 0,
                timeZone = 255
            },
            userData = new CustomizationUserData
            {
                computerName = new CustomizationFixedName { name = cloneName },
                fullName = [REDACTED],
                orgName = [REDACTED],
                productId = ""
            },

            identification = new CustomizationIdentification
            {
                domainAdmin = "Administrator",
                domainAdminPassword = new CustomizationPassword
                {
                    plainText = true,
                    value = [REDACTED]
                },
                joinDomain = [REDACTED]

            }
        },
        options = new CustomizationWinOptions
        {
            changeSID = true,
            deleteAccounts = false
        },
        nicSettingMap = new CustomizationAdapterMapping[]
        {
            new CustomizationAdapterMapping
            {
                adapter = new CustomizationIPSettings
                {
                    ip = new CustomizationDhcpIpGenerator()
                }
            }
        }
    },
    config = new VirtualMachineConfigSpec
    {
        numCPUsSpecified = true,
        numCPUs = 4,
        numCoresPerSocketSpecified = true,
        numCoresPerSocket = 4,
        memoryMBSpecified = true,
        memoryMB = 2048,
        deviceChange = new VirtualDeviceConfigSpec[]
        {
            new VirtualDeviceConfigSpec
            {
                operationSpecified = true,
                operation = VirtualDeviceConfigSpecOperation.edit,
                device = new VirtualE1000
                {
                    key = 4000,
                    connectable = new VirtualDeviceConnectInfo
                    {
                        startConnected = true
                    }
                }
            }
        }
    }
};

Any ideas?

Cheers,

Mark.

0 Kudos
gunnarb
Expert
Expert

THis may be dumb (I'm coming in late to this thread) but this just sounds like a standard issue that comes up when you run out of ports on your vSwitch.  Unfortunatly vSphere doesn't do a good job of letting you see that VCD does (hint to VMware!).  Have you tried the simple solution of just increasing your vSwitch ports?

Gunnar Berger http://www.gunnarberger.com http://www.endusercomputing.com
0 Kudos
andrey09
Contributor
Contributor

In my case problem was placed in gold image. Composer feel strong dislike to XP  that was deployed from template. Clean install helped me.