nielse's Posts

Support for vSAN is coming in Patch 4 for v7. Patch release should be next week.
Is the date on these files the same as the moment when the backup/snapshot was made? I think these are just some leftover files which you can only resolve by doing "consolidate virtual machine... See more...
Is the date on these files the same as the moment when the backup/snapshot was made? I think these are just some leftover files which you can only resolve by doing "consolidate virtual machine"...
You could automate it using PowerCLI, if the users are known in a domain you can export & import those. It will become harder when they are OS specific users.
Did you check the "connect on power on" box?
Can you do the following things and provide screenshots: dmesg | grep eth cat /etc/sysconfig/network-scripts/ifcfg-eth0 cat /etc/sysconfig/network-scripts/ifcfg-eth1 cat /etc/sysconfig/netw... See more...
Can you do the following things and provide screenshots: dmesg | grep eth cat /etc/sysconfig/network-scripts/ifcfg-eth0 cat /etc/sysconfig/network-scripts/ifcfg-eth1 cat /etc/sysconfig/network-scripts/ifcfg-eth2 Make sure that the MAC addresses in these configs matches the network cards you can see under "edit settings" (maybe provide screenshots of those as well).
As you can see eth0 is renamed into rename2 and then eth2 You should compare the lines in the udev file with the MAC addresses in "edit settings" on the VM. Make sure they are correct: NIC1 =... See more...
As you can see eth0 is renamed into rename2 and then eth2 You should compare the lines in the udev file with the MAC addresses in "edit settings" on the VM. Make sure they are correct: NIC1 = eth0 NIC2 = eth1 etc As mentioned you can clear the 70-net... file and it should fill up again after a reboot.
How much memory did you assign for the video card under VM settings?
Did you configure syslog or scratchconfig? How are you running ESXi? Is this from a direct disk or using an USB disk.
There has probably been a MAC change and you now have 2 network cards in the OS (atleast that's what it will think). Can you check the following things and give screenshots: dmesg | grep eth ... See more...
There has probably been a MAC change and you now have 2 network cards in the OS (atleast that's what it will think). Can you check the following things and give screenshots: dmesg | grep eth Also could you check the content of /etc/udev/rules.d/70-persistent-net.rules There is a big chance there are 2 devices in this file, remove both entries and reboot the server. This might already resolve the issue.
When you suspend a virtual machine, a file with a .vmss extension is created. This file contains the entire state of the virtual machine. When you resume the virtual machine, its state is resto... See more...
When you suspend a virtual machine, a file with a .vmss extension is created. This file contains the entire state of the virtual machine. When you resume the virtual machine, its state is restored from the .vmss file.
Did the job fail/ended with a warning or error?
Are you running PowerCLI in 32bit?
Can you change the following line: $vm=New-VM -Name $_.Name -Template $_.Template -Host $_.Host `         -Datastore $_.Datastore -Confirm:$false -RunAsync | Set-OSCustomizationSpec -OSCustom... See more...
Can you change the following line: $vm=New-VM -Name $_.Name -Template $_.Template -Host $_.Host `         -Datastore $_.Datastore -Confirm:$false -RunAsync | Set-OSCustomizationSpec -OSCustomizationSpec $_.Customization into: $vm=New-VM -Name $_.Name -Template $_.Template -Host $_.Host `         -Datastore $_.Datastore -Confirm:$false -RunAsync | Set-VM -OSCustomizationSpec $_.Customization
Can you try the following (not tested, based on old script i have) $vms = Import-CSV C:\Users\sg0217865\Desktop\NewVMs.csv foreach ($vm in $vms){     $Template = Get-Template $vm.template ... See more...
Can you try the following (not tested, based on old script i have) $vms = Import-CSV C:\Users\sg0217865\Desktop\NewVMs.csv foreach ($vm in $vms){     $Template = Get-Template $vm.template     $VMHost = Get-VMHost $vm.host     $Datastore = Get-Datastore $vm.datastore     Get-OSCustomizationSpec LinuxTemplateforPCLI | Get-OSCustomizationNicMapping | Set-OSCustomizationNicMapping -IpMode UseStaticIp -IpAddress $_.IP Address -SubnetMask $_.Subnet -DefaultGateway $_.Gateway | Out-Null     New-VM -Name $vm.name -Template $Template -Datastore $Datastore -VMHost $VMHost -DiskStorageFormat Thin | Set-VM -OSCustomizationSpec $OSCustomization -Confirm:$false }
Did you close the old connection to the vCenter and ran the script again? The customization should work without a problem
How is the switch configured? You are probably using a switch with a port in trunk mode configgured. If you configure a VLAN make sure the port is in access mode. (This is from a Cisco swich POV)... See more...
How is the switch configured? You are probably using a switch with a port in trunk mode configgured. If you configure a VLAN make sure the port is in access mode. (This is from a Cisco swich POV).
This is not about the default root directory but pure about the shell layout. You receive a minimal shell (/bin/sh) which gives ~ #. A shell like /bin/bash will give [root@hostone ~]# by default.... See more...
This is not about the default root directory but pure about the shell layout. You receive a minimal shell (/bin/sh) which gives ~ #. A shell like /bin/bash will give [root@hostone ~]# by default. Since /bin/bash isn't available on ESXi (as this is a minimal shell system) you can't use it. You can however create a profile file which will be read on logging in: vi /.profile Insert the following line: PS1='\u@\h:\$ ' If you now log in to your server you will receive: root@hostone:#
You can only use vi on an ESXi host.