I am trying to get Micro Cloud Foundry working under Windows 7 64 bit with VMware workstation 7.1.4. For some reason, the VM starts with no eth0 only lo, therefore I never get a network connection. Ideas?
Do you have any other VMs running at the same time that may be using the same virtual adapter? Have you also checked the network settings on the VM to make sure a physical interface is selected on which to bridge the virtual adapter with.
As an alternate to deleting VM and starting from scratch again, and loose all your work, you could also rename the folder that contains the VM image. When relaunching VM from renamed folder, VMWare will ask whether you "copied" or "moved" this VM. Select the "I moved" option and then VMware will recreate the ethernet adapter configuration for you and you are good to go from then on
Related
I recently migrated a VM from vSphere vmware to Google Cloud Compute Instance.
I used CloudEndure, and everything worked fine, the VM is identical. But there is one problem. The upload is super slow, under 1mbps (0.65mbps), while the download is just super fast 300-900 mbps.
I tried twice migration changed vNic, changed zone region, everything but no luck. The funny thing is I put a temporary VM provided by GCP to connect rdp in the same subnet, and that temp-VM works fine.
Did you have this experience ?
Appreciate your suggestions, thanks in advance.
To change your MTU setting in Windows Server 2003 or 2008 use the following steps:
Open regedit as an administrator account on the server in question.
Navigate to HKLM\System\CurrentControlSet\services\Tcpip\Parameters\Interfaces[Choose the interface in question] (Do this by checking the correct IP address is in the settings under this key for the adapter you are configuring)
Once you are in the correct key for your interface, right-click and select new DWORD value (32 bit).
Call it MTU
Give this a decimal value equal to the setting 1460 (measured in bytes).
Win7 PC running Rails in an Ubuntu VM via VMWare Player. I'm working on a site and would like to show it to a friend who's outside my network.
I found this blog post, which got me very close: http://blog.fardad.com/2012/06/vmware-player-and-custom-nat-port-map.html
OK, so I have the VM that is using NAT. As I understand it, that means that the VM will appear to have the same IP address as the parent machine to outside traffic.
I went into NAT settings and added port forwarding:
Host Port: 8200 Type: UDP Virtual IP Address: 192.168.198.184:3000
OK so my understanding is that I should now be able to go to 192.168.1.1xx:8200 (the IP of my 'real' PC) and access the webserver running in the VM. But when I go to that address, I don't get anything. I can ping 192.168.198.184 (the VM) from the PC.
What I want to be able to do is go into my router and set up a port that will eventually forward into the VM.
It seems like I'm missing something very small but I don't know what that is. Help, please.
If anyone is curious how to get the Virtual Network Editor:
go to the vmware-directory and run in elevated cmd.exe-box
rundll32.exe vmnetui.dll VMNetUI_ShowStandalone
http://communities.vmware.com/message/2155960#2155960
Find the vmnetnat.conf file, usually located in
C:\ProgramData\VMware\vmnetnat.conf
or
C:\Users\Application Data\VMware\vmnetnat.conf
Edit vmnetnat, add similar line in the [incomingtcp] section
8200=192.168.198.184:3000
Restart VMware NAT Service.
Try using Bridged network option in vmware player instead of NAT. It replicates your physical network.
You can use an http proxy to do that, by doing that you don't need to expose your entire private network, check out this blog post for more information how to access docker containers from external devices
What is the best way to have a virtual operating system have a static IP address in VMWware. I would like to keep the IP address static since it is a virtual server.
You can configure VMware DHCP server [which runs on host OS] to assign a fix IP address to a VM each time.
According to vmware docs, configuration is stored at the following locations:
Windows XP
C:\Documents and Settings\All Users\Application Data\VMware\vmnetdhcp.conf
Windows Vista or Windows 7
C:\ProgramData\VMware\vmnetdhcp.conf
Linux (host-only)
/etc/vmware/vmnet1/dhcp/dhcp.conf
Linux (NAT)
/etc/vmware/vmnet8/dhcp/dhcp.conf
VMWare Fusion for Mac (host-only)
/Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
VMWare Fusion for Mac (NAT)
/Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
Static IP and DNS name by MAC example:
host ubuntu {
hardware ethernet 00:0c:29:c0:2c:58;
fixed-address 192.168.118.3;
}
For more details on this please see this blog post.
Assuming you're not using NAT-based VMWare networking, the answer isn't any different for a virtual (guest) server than for a real one. You can:
Assign a static IP via whatever mechanism the guest operating system supports.
Configure the guest operating system to get its IP address from a DHCP server, and configure the DHCP server to return a static IP address for the VMWare instance's MAC address.
If you want the VM slice / VM machine (guest) to have a static IP, assign it to the VM slice. Then on the VM Server select "Bridged" for the network adapter settings. This tells VMWare to use what ever IP settings you have established on the guest.
This works on my machine
Follow these simple steps. Takes just 5 minutes.
1. Note the MAC of the VM
2. On the host machine open C:\ProgramData\VMware\vmnetdhcp.conf
a. Or C:\Documents and Settings\All Users\Application Data\VMware\vmnetdhcp.conf
b. These 2 files are auto synced or mirrored.
c. Open the editor in Administrator mode. Eg notepad++. Otherwise you will get access denied message
3. Add a new entry at bottom of the configuration file, right before the "# End" marker. MyGuestVM is any unique name. Example below
host sunilW2008Server {
hardware ethernet 00-0C-29-05-2B-A0;
fixed-address 192.168.63.222;
}
3. Shutdown the VM and close the Workstation
4. Re-start the VMWare DHCP and NAT services for changes to take effect (From services.msc)
Notes:
the below folders are at sync automatically.. change at one place and the same will be reflected on the other folder
C:\ProgramData\VMware
C:\Documents and Settings\All Users\Application Data\VMware
A simple workaround, configure the vmware dhcp server to use longer leases.
In the vmware config folder (on windows 7 -- C:\ProgramData\vmware) edit the file
vmnetdhcp.conf and change the values of default-lease-time and max-lease-time to
something bigger say 4 months (4mo*30days*24hours*60min*60sec = 10368000).
Then restart the vmware dhcp server. Then release and renew the lease on the guest.
Now your guest IP is static for next four months.
If you prefer to leave the VM host configuration as default, it is also possible to configure the guest machine to request a fixed address for dhcp. This will work even for the NAT network. In the case of Ubuntu and dhclient, this is achieved by the following block in dhclient.conf:
interface "eth0" {
send dhcp-requested-address 192.168.1.222;
}
Source: https://serverfault.com/a/381137
I've been using VMWare for a while and am very happy with it, but I would like to compare it with VirtualBox. Apparently the disk images are compatible, and I have successfully booted my Fedora based VM created by VMWare in VirtualBox... but the network is completely unavailable. How do you port a virtual machine from VMWare to VirtualBox and keep all the capabilities intact?
have you tried going into the options in virtual box and changing the network adapter to the VB one? VB is a bit different in it's virtual adapters, you might have to create a new one attached to the nic and then specify that one as the primary nic.
Are you sure that network is completly unavailable? VirtualBox is known to have a problem with ICMP support so you won't be able to ping any host from the guest OS. I ran into the same problem yesterday and the network was actually working.
If the network is unavailable, you may want to check your VirtualBox configuration and make sure you have a network card configured. If you do, then the next stop would be the OS running in the virtual machine. An unfortunate fact of some operating systems is that they don't always appreciate hardware changes. If the OS is not auto-detecting the change to the network card, you may need to reconfigure it to support the new card.
Another possibility is that you were using a fixed IP address. VirtualBox uses a couple of schemes for networking that are a bit different than VMWare. You may need to change the IP inside the VM to match the expected subnet.
Outside the VM, you need to use either a bridged networking device or configure ports virtual ports through the NAT system if you want to gain access to your Virtual Machine.
Two RAID volumes, VMware kernel/console running on a RAID1, vmdks live on a RAID5. Entering a login at the console just results in SCSI errors, no password prompt. Praise be, the VMs are actually still running. We're thinking, though, that upon reboot the kernel may not start again and the VMs will be down.
We have database and disk backups of the VMs, but not backups of the vmdks themselves.
What are my options?
Our current best idea is
Use VMware Converter to create live vmdks from the running VMs, as if it was a P2V migration.
Reboot host server and run RAID diagnostics, figure out what in the "h" happened
Attempt to start ESX again, possibly after rebuilding its RAID volume
Possibly have to re-install ESX on its volume and re-attach VMs
If that doesn't work, attach the "live" vmdks created in step 1 to a different VM host.
It was the backplane. Both drives of the RAID1 and one drive of the RAID5 were inaccessible. Incredibly, the VMware hypervisor continued to run for three days from memory with no access to its host disk, keeping the VMs it managed alive.
At step 3 above we diagnosed the hardware problem and replaced the RAID controller, cables, and backplane. After restart, we re-initialized the RAID by instructing the controller to query the drives for their configurations. Both were degraded and both were repaired successfully.
At step 4, it was not necessary to reinstall ESX; although, at bootup, it did not want to register the VMs. We had to dig up some buried management stuff to instruct the kernel to resignature the VMs. (Search VM docs for "resignature.")
I believe that our fallback plan would have worked, the VMware Converter images of the VMs that were running "orphaned" were tested and ran fine with no data loss. I highly recommend performing a VMware Converter imaging of any VM that gets into this state, after shutting down as many services as possible and getting the VM into as read-only a state as possible. Loading a vmdk either elsewhere or on the original host as a repair is usually going to be WAY faster than rebuilding a server from the ground up with backups.