On 2011-09-02 17:41, Liang Guo wrote: > On Fri, Sep 2, 2011 at 10:42 PM, Jan Kiszka <jan.kiszka@xxxxxxxxxxx> wrote: >> On 2011-09-02 15:59, Liang Guo wrote: >>> Hi, >>> >>> When I run kvm with following option: >>> >>> -net nic -net vde,sock=/var/run/vde2/vde3.ctl >>> >>> the guest OS's network work as expected, I can ping/ssh from/to host OS, >>> but when I run kvm with: >>> >>> -net nic -net user -net nic -net vde,sock=/var/run/vde2/vde3.ctl >> >> That's probably the classic mistake: You create one virtual LAN inside >> QEMU this way. Attached to this LAN are all four peers (two NICs, slirp >> and VDE). > Thank you pointing this out, I thought '-net nic' and '-net user|tap|vd' was > connected with their sequence. > >> >> What you likely want are two backend/frontend pairs: >> -net nic,netdev=net1 -net user,id=net1 \ >> -net nic,netdev=net2 -net vde,sock=/var/run/vde2/vde3.ctl,id=net2 >> >> Jan > I can reach my object with > > -netdev user,id=eth0 -device virtio-net-pci,netdev=eth0 \ > -netdev vde,sock=/var/run/vde2/vde3.ctl,id=eth1 -device > virtio-net-pci,netdev=eth1 > > or > > -net nic,vlan=1 -net user,vlan=1 \ > -net nic,vlan=2 -net vde,sock=/var/run/vde2/vde3.ctl,vlan=2 Err, yeah, I also confused the syntax. :) Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
