Hi Larry,
For a free trial, you can click here or email me on mmakhija@vmware.com and I can connect you to correct team
Thanks
Munish
Hi Larry,
For a free trial, you can click here or email me on mmakhija@vmware.com and I can connect you to correct team
Thanks
Munish
L.
The vast vm has VM tools install and I am looking at vmxnet3 adapter.
I have windows vm and Linux vm on my cluster and I would like to run a ps so I can come up with a list of only Linux and what type of adapter they have
Thanks L.
I have a Usage Meter instance that insists that one of our vCenter servers is unlicensed for vRealize Operations Manager and doesn't have the extension installed, and is alerting every hour. Of course, it isn't licensed for it and doesn't have the extension installed, because it doesn't have vRealize Operations Manager installed in the first place. I don't know what it is detecting, but it's essentially complaining about nothing. Know any way to get it to shut up about it? It keeps generating false alarm tickets every hour since 3PM.
Reloaded windows ( 10 pro) in laptop & tried to open exisitng virtual machine "The system cant file the specified file " error is there.
Path & file name are correct.
Did you try by using the Server parameter?
You could do for example
Try something like this
where{$_.ExtensionData.GuestFamily-ne'windowsGuest'}|
Select Name,
@{N='OS';E={$_.ExtensionData.Guest.GuestFullName}},
@{N='vNICType';E={(Get-NetworkAdapter-VM $_).Type -join'|'}}
If you don't want to rely on the VMware Tools and you are sure that all your VMs were configured with the correct GuestId, you could do
where{$_.GuestId-notmatch'windows'}|
Select Name,
@{N='OS';E={$_.GuestId}},
@{N='vNICType';E={(Get-NetworkAdapter-VM $_).Type -join'|'}}
jburen - You sir, are a genius!
I first went down the route of trying another TFTP server. This actually was a good exercise to do. I was using the QNAP for both TFTP and DHCP, and that was due to the convenience of the solution but my intention was to always move those onto a Raspberry Pi eventually and have the QNAP be dedicated to just iSCSI storage needs. I just moved that project ahead of schedule, and now have the TFTP and DHCP services running off of the RPi with no problems.
Except I still could not load a different installer based upon the MAC address of the ESXi host. I was about to call it quits for the day, and logged onto here to post an update that it was still not working with a completely different TFTP server. Then I saw your post and gave it a shot. Adding the "01-" prefix is exactly what was missing. I edited the directory names, and now everything works as expected.
This is stated in the VMware documentation that I used:
"Create a subdirectory of /tftpboot named after the MAC address of the target host machine (01-mac_address_of_target_ESXi_host), for example, 01-23-45-67-89-0a-bc."
I just completely missed this step. I am going to suggest to the VMware staff that a change be made to the documentation though. I'd like to see the instruction changed to the following:
"Create a subdirectory of /tftpboot named "01-" followed by the MAC address of the target host machine (01-mac_address_of_target_ESXi_host), for example, 01-23-45-67-89-0a-bc"
Hopefully that will prevent others from making the same mistake that I did. Serves me right for working on the home lab well past a reasonable hour! I'm glad I turned to others for a second set of fresh eyes to take a look at the problem. Now I'm back on track for fully automating my home lab being built from scratch whenever I need to.
Thanks André, let suppose I have a windows or linux file system how can I zero out the un-used space I am only can't imagine the steps involved so if you can spot some steps would be a great help from you
ESXI 6.7
In the process of turning off the virtual machine, an automatic rename occurred.
Renamed dev-main from dev-main to /vmfs/volumes/5bebf3ee-eed02d31-1f4e-ac1f6b336d6a/dev-main/dev-main.vmx in ha-datacenter
Type
Time
Friday, 17, May., 11:26:46
Virtual machine
dev-main
I spent lot more time but still no luck. I now started using fp-eth1 as well on the edge vm (nsxtedge02) with Tier-0 router and mapped it to a different VLAN than the transport VLAN. I'm sharing some info below from my own debugging - hopefully that will expose something for someone to help me.
nsxtedge02(tier0_sr)> get interfaces Logical Router UUID VRF LR-ID Name Type e5421544-631e-41f5-bd47-1105da236e4f 2 3 DR--bs-tier0 DISTRIBUTED_ROUTER_TIER0 Interfaces Interface : b035990b-de81-58b2-86fc-1ec2fcdec173 Ifuid : 277 Mode : blackhole Interface : b8fac27f-1adb-4adb-abef-c2d7a48785f4 Ifuid : 278 Name : bp-dr-port Mode : lif IP/Mask : 169.254.0.1/28;fe80::50:56ff:fe56:4452/64 MAC : 02:50:56:56:44:52 VNI : 71683 LS port : 9a0a8564-4ae8-4b3a-a0f1-44319390c79e Urpf-mode : PORT_CHECK Admin : up Op_state : up MTU : 1500 Interface : db4c0c0a-b342-49d8-905c-6b09db7ee9c8 Ifuid : 279 Name : -bs-tier0-bstier1gw-t0_lr Internal name : downlink-279 Mode : lif IP/Mask : 100.64.240.0/31;fc21:3e51:80e3:b000::1/64;fe80::50:56ff:fe56:4452/64 MAC : 02:50:56:56:44:52 VNI : 71682 LS port : c2c3a0e6-594d-48fa-b302-70a1732587ac Urpf-mode : PORT_CHECK Admin : up Op_state : up MTU : 1500 Interface : fe3788d9-3597-575a-b8ef-845882c6e2e0 Ifuid : 276 Mode : cpu Logical Router UUID VRF LR-ID Name Type d8942a8a-b52d-4f9d-a170-d1ed79f51457 1 5 SR--bs-tier0 SERVICE_ROUTER_TIER0 Interfaces Interface : 4feca6e7-da2e-59b8-9717-b0b99b32df6c Ifuid : 269 Mode : cpu Interface : 3a5c3f9e-8f07-4aec-96d0-87a79f9792b3 Ifuid : 275 Mode : loopback IP/Mask : 127.0.0.1/8;10.4.14.11/32;::1/128 Interface : 9d000121-d24b-5c3e-8324-cfe6356dfc12 Ifuid : 270 Mode : blackhole Interface : 200603e9-5ded-49fd-9485-4a07b9531049 Ifuid : 273 Name : bp-sr0-port Mode : lif IP/Mask : 169.254.0.2/28;fe80::50:56ff:fe56:5300/64 MAC : 02:50:56:56:53:00 VNI : 71683 LS port : 312ce065-db04-4d35-8da9-a448fe281825 Urpf-mode : NONE Admin : up Op_state : up MTU : 1500 Interface : b6f466c5-4a85-4c06-9a57-22f1366f5643 Ifuid : 272 Name : uplink-ns-exit Internal name : uplink-272 Mode : lif IP/Mask : 10.4.14.10/24 MAC : 00:50:56:a5:7d:85 LS port : 9ff79c75-69e8-45c0-b561-11a39dbbcb76 Urpf-mode : STRICT_MODE Admin : up Op_state : up MTU : 1600 nsxtedge02(tier0_sr)> ping 8.8.8.8 repeat 3 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=52 time=2.320 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=2.599 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=2.139 ms --- 8.8.8.8 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 2.139/2.353/2.599/0.189 ms nsxtedge02(tier0_sr)> exit nsxtedge02> vrf 2 nsxtedge02(vrf)> ping 8.8.8.8 repeat 3 PING 8.8.8.8 (8.8.8.8): 56 data bytes --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss nsxtedge02(vrf)> get forwarding Logical Router UUID VRF LR-ID Name Type e5421544-631e-41f5-bd47-1105da236e4f 2 3 DR--bs-tier0 DISTRIBUTED_ROUTER_TIER0 IPv4 Forwarding Table IP Prefix Gateway IP Type UUID Gateway MAC 0.0.0.0/0 10.4.14.1 route b6f466c5-4a85-4c06-9a57-22f1366f5643 64:00:6a:d6:4b:a1 10.4.14.0/24 route b6f466c5-4a85-4c06-9a57-22f1366f5643 10.4.14.10/32 route 4feca6e7-da2e-59b8-9717-b0b99b32df6c 10.4.14.11/32 route 3a5c3f9e-8f07-4aec-96d0-87a79f9792b3 100.64.240.0/32 route fe3788d9-3597-575a-b8ef-845882c6e2e0 100.64.240.0/31 route db4c0c0a-b342-49d8-905c-6b09db7ee9c8 127.0.0.1/32 route 3a5c3f9e-8f07-4aec-96d0-87a79f9792b3 169.254.0.0/28 route 200603e9-5ded-49fd-9485-4a07b9531049 169.254.0.1/32 route fe3788d9-3597-575a-b8ef-845882c6e2e0 169.254.0.2/32 route 4feca6e7-da2e-59b8-9717-b0b99b32df6c 192.168.2.0/24 100.64.240.1 route db4c0c0a-b342-49d8-905c-6b09db7ee9c8 192.168.3.0/24 100.64.240.1 route db4c0c0a-b342-49d8-905c-6b09db7ee9c8 IPv6 Forwarding Table IP Prefix Gateway IP Type UUID Gateway MAC ::1/128 route 3a5c3f9e-8f07-4aec-96d0-87a79f9792b3 fc21:3e51:80e3:b000::/64 route db4c0c0a-b342-49d8-905c-6b09db7ee9c8 fc21:3e51:80e3:b000::1/128 route fe3788d9-3597-575a-b8ef-845882c6e2e0 fe80::/64 route 200603e9-5ded-49fd-9485-4a07b9531049 nsxtedge02(vrf)> ping 100.64.240.1 repeat 3 PING 100.64.240.1 (100.64.240.1): 56 data bytes 36 bytes from 100.64.240.1: Destination Host Unreachable Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 0000 0 0000 40 01 d226 100.64.240.0 100.64.240.1 --- 100.64.240.1 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss nsxtedge02(vrf)> get neighbor Logical Router UUID : e5421544-631e-41f5-bd47-1105da236e4f VRF : 2 LR-ID : 3 Name : DR--bs-tier0 Type : DISTRIBUTED_ROUTER_TIER0 Neighbor Interface : b8fac27f-1adb-4adb-abef-c2d7a48785f4 IP : fe80::50:56ff:fe56:5300 MAC : 02:50:56:56:53:00 State : perm Interface : b8fac27f-1adb-4adb-abef-c2d7a48785f4 IP : 169.254.0.2 MAC : 02:50:56:56:53:00 State : perm Logical Router UUID : d8942a8a-b52d-4f9d-a170-d1ed79f51457 VRF : 1 LR-ID : 5 Name : SR--bs-tier0 Type : SERVICE_ROUTER_TIER0 Neighbor Interface : b6f466c5-4a85-4c06-9a57-22f1366f5643 IP : 10.4.14.1 MAC : 64:00:6a:d6:4b:a1 State : reach Timeout : 804 nsxtedge02(vrf)> ping 10.4.14.1 repeat 2 PING 10.4.14.1 (10.4.14.1): 56 data bytes --- 10.4.14.1 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss
Hello.
I just downloaded Red Hat Enterprise Linux 8 64-bit ISO and installed in a VMware Workstation (15.1.0) VM. VM has the default settings, host screen resolution: 3840x2160 (latest Intel drvs). RH is updated, open-vm-tools installed. For some reason I can't set 3840x2160 (native host) resolution in RH. On top of that, RH does not remember screen settings. Host is W10Pro 1809.
Hi, I am currently using ESXi 6.7 U2 (free) to run a Windows 10 guest OS. I am able to add a PCI device to my VM and enable the passthrough. This works as fine. Also, if I disable the PCI passthrough and enable the "expose hardware assisted virtualization" flag in the CPU settings for the VM, this also works fine.
However, when I try to enable both the PCI passthrough and the hardware assisted virtualization flag, I get the following error.
"PCI passthrough devices cannot be added when Nested Hardware-Assisted Virtualization is enabled."
This seems odd to me because I am not sure how those two are related. Doesn't the passthrough use VT-D and the hardware assisted virtualization use VT-X?
Is it possible to enable these at the same time?
Thanks!
but it works
At first: Which version of Usage Meter are you using?
And can you please check the extensionList in the MOB: https://YOUR-VCENTER/mob/?moid=ExtensionManager
At the top section (Properties -> extensionList), is there one of the followin extensions displayed?
- com.vmware.vrops
- com.vmware.vcops
- com.vmware.vrops.install
Did you have vROps installed in the past?
I encountered this question as well~
I'm wondering did you find the solution?~
I found that the mac-address of the VMs are displayed differently,
and is also confirmed from ipconfig in the VM.
However, somehow the IPs are assigned as the same.
But the IPs are assigned as different if I create a new VM from scratch instead of cloning a VM.
Did you enable the VT-d from the bios? I had a similar issue and realized that it was because VT-d was disabled accidentially. After going into my bios and enabling it, everything worked fine.
Me es imposible poder cargar un solo archivo a un hdd desde la pagina web de ESXi 6.7 ni desde un programa que me baje que se llama win spc, empieza la descarga en unos 190mps y acaba dando un pico de cero y ya no hay quien lo levante nada mas que actualizando la pagina. El equipo donde esta montado el ESXi es un AMD Ryzen 5 con 16gm de ram y una placa base msi, ambos aptos para tecnologia de virtualizacion. ya no se que mas probar para que la red funcione adecuadamente. os paso un grafico.... muchas gracias.
We only have basic support.
Don't know if htis includes to open a case ...
This did it for me to...
*Edit:Post #27