RSS 
Well, with Qemu 0.8.0 out for a while I decided to finally get my networked starcraft working with it. There were several changes but it's not too bad.
The first simple easy change to take note of is that the '-enable-audio' flag no longer works. They have added support for several sound cards of which you have to pick one. If you want to maintain the Soundblaster you previously had working you should now use '-soundhw sb16'. However if this is a fresh install you may find that one of the other drivers '-soundhw adlib' or '-soundhw es1370' work better for you or you could use the '-soundhw all' option and have QEmu emulate them all and let Windows pick what it likes best.
Now, go see Starcraft in QEmu on Linux, the original, and get set up.
Once you're set up for Qemu 0.7.2 there are some networking changes that I will outline here.
- QEmu now uses a tap device instead of a tun device so go through bridge.sh and cleanup.sh and change all references to 'tun0' to 'tap0'.
- The QEmu command line options for network configuration are now more powerful so you can delete '/etc/qemu-ifup' since it is no longer required. Instead, when you are starting QEmu for Starcraft on the network use '-net nic,vlan=0 -net tap,vlan=0,ifname=tap0'.
And that's it. Now you are good to play networked starcraft in QEmu 0.8.0 on Linux.
June 11th, 2006 at 9:53 am
QEMU is amazing to me. I haven’t even bothered to install VMware on my Ubuntu desktop.
June 16th, 2006 at 7:17 am
I’ve seen that you have also configured network manager, isn’t it causing problems with your bridged network?
June 21st, 2006 at 10:50 am
Yes infact it does. But for that I just shut it off and do a more manually network config. You could presumably just launch dhcpcd iface, but in my case I just fall back to the more reliable Gentoo network controllers like /etc/init.d/net.eth0. Also, I’ve found that this works a lot more stably on wired networks. I’m not sure I’ve ever gotten it working on a wireless network.