Debian eth0, eth1, eth2, in Virtualbox or VMware Virtual machines when copying

jacob — Fri, 13 Nov 2009 19:44:17 +0000

Debian uses udev. Udev handles mapping MAC’s to the appropriate /dev/eth(X) file. If you copy a Virtual machine, Udev will remember the MAC address of the old NIC. When you copy the machine, the virtual host usually generates a new MAC address for the VM.
Udev will assign the new Device to eth1, eth2, and so on. If you want to change your NIC assignments make Udev forget the old MAC.
In Debian 5 (lenny) it is in this file:

/etc/udev/rules.d/70-persistent-net.rules

In Debian 4 (etch) it is in this file:

/etc/udev/rules.d/z25_persistent-net.rules

To apply changes in Lenny: “udevadm trigger” or “udevtrigger” (in Etch)

Vmware – Unable to change virtual machine power state: Internal error.

jacob — Fri, 14 Aug 2009 13:43:23 +0000

Ran into this while running Vmware Workstation under Ubuntu Jaunty. I got an error while shutting down the machine through an NX session.

This is a result of a zombie ‘vmware-vmx’ process running. All you need to do is kill the process. This command sends ‘signal 9′ to the process. When sent to a program, SIGKILL causes it to terminate immediately. In contrast to SIGTERM and SIGINT, this signal cannot be caught or ignored. For more information: more sigkill info.

killall -s9 vmware-vmx

After that, I was able to start up the virtual machine without issue.

SurlyJake » VM

Debian eth0, eth1, eth2, in Virtualbox or VMware Virtual machines when copying

Vmware – Unable to change virtual machine power state: Internal error.