Since May 5, 2024 Broadcom shut down the self-purchase licensure portal for VMware customers. Click on 'Login' in upper-right here: https://www.vmware.com/ takes you to this 'site-maintenance' dead end.
Hours of digging and I must ask "How does one renew a VMware Workstation Pro license now that Broadcom owns it?"
I have called Broadcom support and even they don't know.
I have a VMware: 10.10.10.1, a linux in VMware (Guest): 10.10.10.128 and a honeypot on Guest: 10.10.10.15, and my Windows (Host): 192.168.1.11. I can send FTP requests directly from my Host to honeypot and the connection is established. Now I want to send FTP requests to Guest and these forward to my honeypot. I put these rules in iptables on Guest:
iptables -t nat -A PREROUTING -p tcp --dport 21 -j DNAT --to-destination 10.10.10.15:21
iptables -t nat -A POSTROUTING -p tcp -s 10.10.10.15 --sport 21 -j SNAT --to-source 10.10.10.128
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
But I cannot get the desired result. What can I do?
Note: When the honeypot is running, I can ping it from the Host, but I cannot ping it from the Guest and the result is:
Destination Host Unreachable
Where is my wrong?
EHLO everyone! My first post on the StackOverflow network :)
We're running some ESXi 5.0/vCenter infrastructure to host mainly Debian 6/amd64 guest systems with ext3 partitions and open-vm-tools compiled from source per debian bug 471784.
Got an issue that is seen being raised all around the internet, but without a conclusive answer given anywhere.
When trying to shrink a thin-provisioned disk in independent-persistent mode, with no snapshots, parents, clones whatsoever, I consistently get the following error:
root@linux64:~# vmware-toolbox-cmd disk list
Shrink disk is disabled for this virtual machine.
Shrinking is disabled for linked clones, parents of linked clones,
pre-allocated disks, snapshots, or due to other factors.
See the User's manual for more information.
(By the way, what are the "other factors", and which of the ton of white papers and technical manuals is the User's manual?:)
I know that I can stuff the partitions with zeros (in fact, I do use shred -fuzn0 when deleting large files) then shut down the guest in question and use various methods like vmkfstools, cloning or vMotioning disks around in thin-provision mode, etc, but all of them either incur the downtime penalty for the guest being shirnked, or result in an unwarranted moving of data between datastores and/or hosts.
And the answer is: No shrinking under ESX/ESXi (as of version 5).
The documentation reads:
IMPORTANT Shrinking disks is not allowed under the following circumstances:
The virtual machine is hosted on an ESX/ESXi server. ESX/ESXi Server can shrink the size of a virtual disk only when a virtual machine is exported. The space occupied by the virtual disk on the ESX/ESXi server, however, does not change.
The virtual machine has a Mac guest operating system.
You preallocated all the disk space to the virtual disk when you created it.
The virtual machine contains a snapshot.
The virtual machine is a linked clone or the parent of a linked clone.
The virtual disk is an independent disk in nonpersistent mode.
The file system is a journaling file system, such as an ext4, xfs, or jfs file system.
No wonder there is an option to shrink in VMWare Workstation but not in vSphere client connected to an ESXi or vCenter instance.
When I use VMware workstation I can set the VM with multiple cores. I am actually using it on a machine with dual core and 4 logical cores. So would I really improve the VMS performance by using more cores on the VM?
Is there any way to copy a physical hard drive to a virtual drive for use in Vmware Workstation?