UPDATE
These notes have been succeeded by QEMU vde Notes Revisited
To restart setup like you had before, use these commands:
You'll also have to get vde_switch, br0 (aptitude install bridge-utils) kqemu going again. Follow notes below.
vde:
vde_switch is the command to use to setup the virtual switch. It will get plugged into the tap0 interface.
dnsmasq:
you probably only want this running on the tap0 interface
qemu:
use vdeqemu wrapper instead.
kqemu:
mknod /dev/kqemu c 250 0
chmod 666 /dev/kqemu
Not so surprisingly, qemu works pretty darn well even over wan links (768k) with nomachine's freenx. I have my setup configured like this:
This setup works better than the qemu vnc, as that server doesn't have much when it comes to compression (no tightVNC).
AWESOME! I got it to work with vde. There were a few gotchas:
sudo chmod -R a+rwx /tmp/vde.ctl
I built as small a debian installation as I could. It is based on Debian etch, uses a 300MB raw hard drive (for rough compatibility with Parallels), and no swap. The base install uses about 250MB of memory so there isn't much room left over for other stuff, but if you need more room you can always use an nfs export or something.
As the slackware docs put it, this is a "serious networking powerhouse".
Now I'm trying to figure out how bridging works. I just took my little dectop down by creating a bridge, then adding the only ethernet interface to it. Must be a problem with the USB ethernet stick (or I brought the network interface down accidentally).
After a cold hard reboot, I added the bridging configuration to /etc/network/interfaces and rebooted again. I first forgot to add "auto br0" so I added that and here's what it finally looks like:
auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_maxwait 2 #kvm has to have this set to 0.0.0.0 to work... not sure why #not sure if promisc is necessary up /sbin/ifconfig eth0 inet 0.0.0.0 #set to something random, br0 initialization will undo this iface eth0 inet static address 172.16.5.0 netmask 255.255.255.0
Amazingly, it works! Now this machine is the little dectop running debian, so I'm a little wary about running QEMU / KQEMU on it, but what the heck - I did just increase the RAM to 256MB, and the hard drive to 80GB! A 300MB QEMU file shouldn't be too much to handle.
Phenomenal! Even the dectop can do virtualization. :-) And oh so cool. Bridging brings the virtual machines into the real world lan, no need to have another lan behind another NAT layer. This is really really cool. I used some debian qemu directions on how to setup the bridge to connect with qemu. I'm running vde_switch, but I'm not sure if I need to be. Here's the command I eventually used after modifying /etc/qemu-ifup:
qemu -m 96 -vnc :1 -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup deb4vde.raw
Weird Clock Bug? TSC appears to be running slowly. Marking it as unstable
Time: pit clocksource has been installed. Related Links
http://geekpit.blogspot.com/2006/03/using-qemu-and-kqemu-under-debian-or.html
http://compsoc.dur.ac.uk/~djw/qemu.html
http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:vde
http://base91.sourceforge.net/qemu/
http://lists.gnu.org/archive/html/qemu-devel/2004-09/msg00150.html