The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,226 other subscribers

Archive for April 17th, 2020

When using a e1000 virtual network adapter under VMware, use the “Intel PRO/1000 MT Server (82545EM)” under Virtual Box

Posted by jpluimers on 2020/04/17

Every now and then I need to run existing VMware based disk under a different virtualisation environment.

In my case, the target was VirtualBox, and the source used a e1000 virtual network adapter.

You find the required settings to migrate to VirtualBox by running this inside the directory of your VMware virtual machine:

grep ethernet *vmx

It gives output like this:

ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.networkName = "VM Network on LAN"
ethernet0.addressType = "generated"
ethernet0.generatedAddress = "00:0c:29:cc:cc:cc"
ethernet0.pciSlotNumber = "32"
ethernet0.generatedAddressOffset = "0"

This is in fact an “Intel 82545EM Gigabit Ethernet NIC” adapter, which VirtualBox calls “Intel PRO/1000 MT Server (82545EM)”.

Another compatible pair is the VMware vlance or “AMD 79C970 PCnet32- LANCE NIC” which VirtualBox calls “AMD PCNet PCI II (Am79C970A)”

First note:

Often the virtual operating system still recognises it as a different adapter. Sometimes you can prevent this by also copying the MAC address (as VirtualBox by default uses a MAC address like 080027CCCCCC.

If it is still wrong, then read [WayBack] PredictableNetworkInterfaceNames: the various ways of assigning network interface names in virtualisation environments tend to mismatch. To fix this, I had to rename /etc/sysconfig/ifcfg-ens32 to the nee interface name I found via if -a.

Second note:

VMware supports two special virtual networks that are accessible from the host: vmnet1 (host-only) and vmnet8(NAT) : both are accessible from the host as VMware installs special network adapters:

  • vmnet1 is the host-only network where the host can talk to the VMs and vice versa, but the hosts cannot talk to the outside world
  • vmnet8 is the NAT network where the host can talk to the VMs and vice versa, but the hosts can talk to the outside world

Some background info at:

Read the rest of this entry »

Posted in Power User, VirtualBox, Virtualization, VMware | Leave a Comment »

.ZIP URLs (or, Why You Should Block Domains on a TLD That Doesn’t Have Any) | Blue Coat

Posted by jpluimers on 2020/04/17

Reminder to self:

Some 5 years after the .zip top-level domain got live, I wonder if there are any domains in it.

Currently, it screws up non-quoted searches in browsers like Chrome, so I wonder if  this still holds: .ZIP URLs (or, Why You Should Block Domains on a TLD That Doesn’t Have Any) | Blue Coat

When writing this, there was one domain ( and two registrars.


Posted in Chrome, Google, Power User | Leave a Comment »

%d bloggers like this: