Follow up Question Was: Re: Virtal Machine preferences?

[Derek Broughton]

Fred Roller wrote:


> As Peter mentioned, if the software does not need networking then don't
> give it - kill the network card.  If you need the machines to be
> networked then try local network or assigning the windows machine it's
> own network with a static IP then set up second connection on the host:
> 
>     sudo ifconfig eth0:1 192.168.51.100
> 
> This leaves your original eth0 intact but gives the host and guest
> network connection.  Vbox allows for this with "Internal Network".  The
> guest cannot navigate out to the internet.

Actually, you presumably meant the "Host-only adapter", not "Internal 
Network", as "Internal Network" works only between VMs, not including 
traffic to the host. This is the hard way, now.  Vbox provides DHCP on the 
host-only network, by default assigning addresses in the 192.168.56.* 
subnet.  For a linux client, I then install avahi-utils and I can access it 
from the VM host as HOSTNAME.local (I thought I had to actually put an 
"avahi-publish" stanza in /etc/network/interfaces, but it seems that was 
redundant).  Windows should do this by default, and I think the zeroconf-
published name will be HOSTNAME.WORKGROUP, but I'm not sure about the value 
of "WORKGROUP".

> 
> Also, as mentioned, once you have everything updated and all the
> software installed, if at that point you are not going to change
> anything then I recommend two things.  Get a snapshot so you can recover
> in <5 sec /and/ copy your .vdi file:
> 
>    vboxmanage clonehd <filename> <outputfile>

Again, it's simplified in VirtualBox 3.0 - use "Export appliance" from the 
VirtualBox control panel's "File" menu.

-- 
derek