Re: xennet0 not connected

[Jean-Yves Migeon <jeanyves.migeon%free.fr@localhost>]

On Thu, 23 Sep 2010 11:59:10 +0200, Pierre-Philipp Braun
<pbraun%wda-fr.org@localhost> wrote:
> On Wed, 22 Sep 2010 10:42:36 +0200, Jean-Yves Migeon
> <jeanyves.migeon%free.fr@localhost> wrote:
>> Yup; the xentools that come with are likely 4.0 too, and I don't know
> the
>> rules for the vif creation within the dom0.
> 
> they look pretty much like the xen3 tools (on linux), bridge becomes
> 'eth0' unless specified otherwise and the physical NIC becomes peth0. 
the
> vif behaviour is probably the same too.
> 
> I tryed with {network,vif}-route instead of bridge and I got the same
> problem, netbsd domU doesn't ping the dom0, while rhel 2.6.18 domU does.

Any activity for vif in dom0 or xennet0 in domU?

dom0 => $ cat /proc/interrupts # probably
domU => $ vmstat -i # and look for the event line attached to xennet0

-- 
Jean-Yves Migeon
jeanyves.migeon%free.fr@localhost