vmfh's Posts

Unfortunately, they set new/random values, so I cannot set one myself.
I emended the subject of my post. The OS is 10.14.6, the volume HFS+. In addition to the link I mentioned, I also found https://superuser.com/questions/344706/how-does-one-change-the-uuid-of-a-volu... See more...
I emended the subject of my post. The OS is 10.14.6, the volume HFS+. In addition to the link I mentioned, I also found https://superuser.com/questions/344706/how-does-one-change-the-uuid-of-a-volume-on-mac-os-x-to-a-specified-value, but it's too convoluted.
How can I set the volume uuid? By that I mean the value that System Information shows under Hardware > Storage > [disk] > Volume UUID. Only close reference to this that I found, is https://kb.vmware... See more...
How can I set the volume uuid? By that I mean the value that System Information shows under Hardware > Storage > [disk] > Volume UUID. Only close reference to this that I found, is https://kb.vmware.com/s/article/1021189.
I add two screen shots of the VMs to help visualize the problem and attach a diff of both vmx files. Although only both GE0/0 are connected to vnet0 in the vmx files and the other interfaces a... See more...
I add two screen shots of the VMs to help visualize the problem and attach a diff of both vmx files. Although only both GE0/0 are connected to vnet0 in the vmx files and the other interfaces are not — ethernet 0 through 3 are connected on boot to vnet0.
Mikero​, vnet0 doesn't show in the host (like vnet1, vnet8, custom vnets appear in ifconfig), and interfaces in the guest that are not connected to vnet0 are unexpectedly able to pass traffic, as... See more...
Mikero​, vnet0 doesn't show in the host (like vnet1, vnet8, custom vnets appear in ifconfig), and interfaces in the guest that are not connected to vnet0 are unexpectedly able to pass traffic, as per the description above.
Can anyone please try to reproduce this? I don't even have a vnet0 in Workstation's or Fusion's host (see output above) where I could make a trace on.
wila​ continuum​ Finally I could test again. $ grep --color "ethernet.*present\|vnet" ASAv.vmwarevm/ASAv941.vmx ASAv\ 2.vmwarevm/ASAv941.vmx ASAv.vmwarevm/ASAv941.vmx:ethernet0.present = ... See more...
wila​ continuum​ Finally I could test again. $ grep --color "ethernet.*present\|vnet" ASAv.vmwarevm/ASAv941.vmx ASAv\ 2.vmwarevm/ASAv941.vmx ASAv.vmwarevm/ASAv941.vmx:ethernet0.present = "TRUE" ASAv.vmwarevm/ASAv941.vmx:ethernet1.present = "TRUE" ASAv.vmwarevm/ASAv941.vmx:ethernet2.present = "TRUE" ASAv.vmwarevm/ASAv941.vmx:ethernet0.vnet = "VMnet0" ASAv.vmwarevm/ASAv941.vmx:ethernet3.present = "TRUE" ASAv.vmwarevm/ASAv941.vmx:ethernet4.present = "FALSE" ASAv.vmwarevm/ASAv941.vmx:ethernet5.present = "FALSE" ASAv.vmwarevm/ASAv941.vmx:ethernet6.present = "FALSE" ASAv.vmwarevm/ASAv941.vmx:ethernet7.present = "FALSE" ASAv 2.vmwarevm/ASAv941.vmx:ethernet0.present = "TRUE" ASAv 2.vmwarevm/ASAv941.vmx:ethernet1.present = "TRUE" ASAv 2.vmwarevm/ASAv941.vmx:ethernet2.present = "TRUE" ASAv 2.vmwarevm/ASAv941.vmx:ethernet0.vnet = "VMnet0" ASAv 2.vmwarevm/ASAv941.vmx:ethernet3.present = "TRUE" ASAv 2.vmwarevm/ASAv941.vmx:ethernet4.present = "FALSE" ASAv 2.vmwarevm/ASAv941.vmx:ethernet5.present = "FALSE" ASAv 2.vmwarevm/ASAv941.vmx:ethernet6.present = "FALSE" ASAv 2.vmwarevm/ASAv941.vmx:ethernet7.present = "FALSE" Although 8 interfaces are configurable and 4 are actually present (3 ethernet, 1 management), only 1 is connected to vnet0 — which doesn't show in the host ifconfig output —, but I can send traffic between any ethernet interface, if configured properly (eth0,1,2 corresponds to ge0/0,0/1,0/2 respectively). For example, if I configure ge0/0 which should be eth0 with ip 200.0.0.1/24 on one device and ge0/0 which should be eth0 with ip 200.0.0.254/24 on the other device, traffic passes between them (icmp). But, if I configure ge0/1 which should be eth1 with ip 200.0.0.1/24 on one device and ge0/2 which should be eth2 with ip 200.0.0.254/24 on the other device, traffic passes between them (icmp) too. Last I wouldn't expect, since eth1 on first device and eth2 on the second one are not connected to vnet0.
Can anyone help? I don't think this behaviour is expected nor documented.
Both devices have 3 interfaces each. As long as they are configured on the same subnet — random interface, random IP on each device, traffic passes between them. Here're the parsed vmx and networ... See more...
Both devices have 3 interfaces each. As long as they are configured on the same subnet — random interface, random IP on each device, traffic passes between them. Here're the parsed vmx and networking files. I don't have a VMnet0 on the host. There must be something I'm missing or something that the hypervisor is doing automatically. $ grep "ethernet" ASAv.vmwarevm/ASAv941.vmx ethernet0.present = "TRUE" ethernet0.addressType = "generated" ethernet0.connectionType = "custom" ethernet0.virtualDev = "e1000" ethernet0.startConnected = "FALSE" ethernet1.present = "TRUE" ethernet1.addressType = "generated" ethernet1.connectionType = "custom" ethernet1.virtualDev = "e1000" ethernet1.startConnected = "FALSE" ethernet2.present = "TRUE" ethernet2.addressType = "generated" ethernet2.connectionType = "custom" ethernet2.virtualDev = "e1000" ethernet2.startConnected = "FALSE" ethernet0.pciSlotNumber = "32" ethernet1.pciSlotNumber = "33" ethernet2.pciSlotNumber = "34" ethernet0.generatedAddressOffset = "0" ethernet1.generatedAddressOffset = "10" ethernet2.generatedAddressOffset = "20" ethernet0.vnet = "VMnet0" ethernet3.present = "TRUE" ethernet3.virtualDev = "e1000" ethernet3.startConnected = "FALSE" ethernet3.wakeOnPcktRcv = "FALSE" ethernet3.addressType = "generated" ethernet3.pciSlotNumber = "36" ethernet3.generatedAddressOffset = "30" ethernet4.present = "FALSE" ethernet5.present = "FALSE" ethernet6.present = "FALSE" ethernet7.present = "FALSE" $ $ grep "ethernet" ASAv\ 2.vmwarevm/ASAv941.vmx ethernet0.present = "TRUE" ethernet0.addressType = "generated" ethernet0.connectionType = "custom" ethernet0.virtualDev = "e1000" ethernet0.startConnected = "FALSE" ethernet1.present = "TRUE" ethernet1.addressType = "generated" ethernet1.connectionType = "custom" ethernet1.virtualDev = "e1000" ethernet1.startConnected = "FALSE" ethernet2.present = "TRUE" ethernet2.addressType = "generated" ethernet2.connectionType = "custom" ethernet2.virtualDev = "e1000" ethernet2.startConnected = "FALSE" ethernet0.pciSlotNumber = "32" ethernet1.pciSlotNumber = "33" ethernet2.pciSlotNumber = "34" ethernet0.generatedAddressOffset = "0" ethernet1.generatedAddressOffset = "10" ethernet2.generatedAddressOffset = "20" ethernet0.vnet = "VMnet0" ethernet3.present = "TRUE" ethernet3.virtualDev = "e1000" ethernet3.startConnected = "FALSE" ethernet3.wakeOnPcktRcv = "FALSE" ethernet3.addressType = "generated" ethernet3.pciSlotNumber = "36" ethernet3.generatedAddressOffset = "30" ethernet4.present = "FALSE" ethernet5.present = "FALSE" ethernet6.present = "FALSE" ethernet7.present = "FALSE" $ $ sed -En "s/.*(VNET_[0-9]*).*/\1/p" /Library/Preferences/VMware\ Fusion/networking | uniq | sort VNET_1 VNET_10 VNET_8 VNET_9 VNET_91 VNET_92 VNET_93
Can anyone help?
It seems that, in order to pass traffic between guest VMs, it is not necessary to connect them to a vnet, be it default or custom. I use VMware Fusion 7.1.3 as host and two virtual firewalls C... See more...
It seems that, in order to pass traffic between guest VMs, it is not necessary to connect them to a vnet, be it default or custom. I use VMware Fusion 7.1.3 as host and two virtual firewalls Cisco ASAv. When I configure their interfaces in the same subnet I can pass traffic between them (plain ICMP, haven't tried other types). Until now, I thought I would have to connect the firewall interfaces to a vnet in the vmx file (s. #582773) — but it doesn't seem to be case. It is as if the host would handle the traffic like VirtualBox's private networks, but without even configuring it. I couldn't find documentation to this regard though.
Note to self: VMware vSphere “I moved it” or “I copied it” – What’s the difference?
wila​, although I solved my problem, I still would like to know how and where VMs are registered by Workstation. This might explain why a copy/move dialogue didn't show in the first place.
This is what I found: 1. If I set ethernet0.generatedAddress = "" and leave the rest of ethernet0.* entries unedited, the VM doesn't ask if it's being copied or moved and still attaches to eth... See more...
This is what I found: 1. If I set ethernet0.generatedAddress = "" and leave the rest of ethernet0.* entries unedited, the VM doesn't ask if it's being copied or moved and still attaches to eth1, so I need to rename and edit the interface config file. For lack of a better guess, I'd think this is how Workstation indexes the interfaces. 2. Another macOS VM I opened there does check for copy/move on first run, which leads me to think there's some method for registering the VMs that could be reset, but that I don't know of. And I already enabled all hints. 3. Re http proxy, adding a custom vnet on Virtual Network Editor for a http server needs probably adding that network to the PAC file, which I by the way cannot edit. I can telnet to the server and do a GET /, but the browser will use the system settings and return a 407. If you know of a feasible workaround, I'd appreciate any idea.
I'll check and report back. Just to be sure, you import VMs in Workstation by opening the vmx file, right? Should I start another topic here for the problem with the custom vnet being proxied ... See more...
I'll check and report back. Just to be sure, you import VMs in Workstation by opening the vmx file, right? Should I start another topic here for the problem with the custom vnet being proxied for http (GPO)?
Is there any way to force it to ask?
eth1 appeared as the only ethernet interface running ifconfig -a before I changed the MAC address. When I get a chance, I'll try to open the vmx file without a key for hardware address. If ... See more...
eth1 appeared as the only ethernet interface running ifconfig -a before I changed the MAC address. When I get a chance, I'll try to open the vmx file without a key for hardware address. If you open a VM from a different hypervisor in Workstation, does it ask you if it's been copied or moved?
^ Well, I don't know why CentOS 6 has eth0 on Fusion 7 and eth1 on Workstation 12. It doesn't seem to be distro dependent. And I didn't modify all the ethernet0.* keys I had in the original vm... See more...
^ Well, I don't know why CentOS 6 has eth0 on Fusion 7 and eth1 on Workstation 12. It doesn't seem to be distro dependent. And I didn't modify all the ethernet0.* keys I had in the original vmx file from Fusion 7, but only the MAC address. If you open a VM from a different hypervisor in Workstation 12, does it ask you if it's been copied or moved? And, yes, it works now. I still have a problem with the custom vnet being proxied for http (GPO) and I cannot modify the PAC file. I still have to check --proxy-bypass-list on Chromium. But I don't know if such a problem could be posted here.
wila​, I realised a couple of things: 1. Workstation 12 doesn't prompt to check if a VM was copied or moved. 2. The attached ethernet interface was eth1, so I had to rename /etc/sysconfig/net... See more...
wila​, I realised a couple of things: 1. Workstation 12 doesn't prompt to check if a VM was copied or moved. 2. The attached ethernet interface was eth1, so I had to rename /etc/sysconfig/network-scripts/ifcfg-eth0 in CentOS 6. 3. The MAC address on ifcfg-eth1 and vmx file need to be corrected with the VM's ethernet hardware. All this should have been automatically checked and adjusted (interactively if necessary) by Workstation.
As soon as I have access to it, I'll check that and report back. Let's hope it's only PEBKAC. Thanks so far.