Hi Peter...
On Tue, Aug 3, 2010 at 15:13, Peter Niessen <p.nies...@fz-juelich.de> wrote:
> Dear List,
>
> I'm trying to set up a testbed for batch systems using qemu-kvm. So far,
> I've created two machines, a master ("torque") and an execution host
> ("mom") for use with torque. I'm using the following command lines to
> start up the virtual machines:
>
> qemu-kvm -smp 2 -m 768 -hda ./torque.qcow2 -net
> nic,vlan=1,macaddr=52:54:00:12:34:56 -net
> nic,vlan=2,macaddr=52:54:00:12:34:57 -net user,vlan=2 -net
> socket,vlan=1,listen=localhost:1234 -redir tcp:26022::22 -nographic
> -daemonize
>
> qemu-kvm -smp 2 -m 768 -hda ./mom.qcow2 -net
> nic,vlan=1,macaddr=52:54:00:12:34:58 -net
> socket,vlan=1,connect=localhost:1234 -nographic -daemonize
>
> which I took from http://www.h7.dion.ne.jp/~qemu-win/HowToNetwork-en.html.
Sorry, I took out most of your messages.
IIRC, I once met the same situation too. And it gets worse when using
non TCP transmission (e.g UDP, multicast etc).
So, uhm, perhaps better to use tun/tap and hook them together, maybe
by simply put them all in same network id but separated from host
network device...
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
