search for: tapm

...ooks for two conditions: 1) the type of the vif is ioemu 2) the mailbox file (left by qemu-ifup) is present (in which case it's assumed to contain a VIF interface name) if both conditions are present, then from that point on vif-route ignores the vifN.0 interface and sets up tapM instead. Net result: on this system, ioemu-HVM guests now have working networking (another guest, which uses netfront-HVM [a SLES 11 VM], also works, but taking advantage of the faster VIF scheme) Thanks in advance, -- Cyrille -------------- next part -------------- A non-text attachment was...

...What xen/qemu-dm did is to build two network interfaces: * vifN.0 was used to send packets from the host to the guest routing was enabled towards this interface. No virtual hardware drivers took care of this network link, so all packets ended up dropped. * tapM was used by the guest to deliver packets from its virtual eth0. All packets were classified "martians" by the host and rejected. The reason why this happened is that the scripts/qemu-dm script *assumes* only bridging is ever used, and the scripts/vif-routing *assumes* on...