RE: Reboot on *DOM0* while/after installing GPLPV drivers

[John Hayward <john.hayward%wheaton.edu@localhost>]

Thanks for your continued work on this.
See below for the vif and bridge results of an ifconfig -a (extracted the 
bridge and particular interface).
Let me know if there is more info you could use.
johnh...
________________________________________
From: Manuel Bouyer [bouyer%antioche.eu.org@localhost]
Sent: Monday, October 21, 2013 12:25 PM
To: John Hayward
Cc: Mike C.; Takahiro HAYASHI; Adiel; port-xen%NetBSD.org@localhost
Subject: Re: Reboot on *DOM0* while/after installing GPLPV drivers

On Mon, Oct 21, 2013 at 04:37:45PM +0000, John Hayward wrote:
> I think this patch fixed the disk driver failure to prevent crash of dom0 but 
> did not address the underlying problem of the driver to properly register.  I 
> have not had time to verify this.

the PV drivers works fine with XP/2003. I don't have anything newer to test
with ...

> starting win7 on NetBSD-5.1.2 dom0 of:
> ====
> xenstore-read: couldn't read path /local/domain/0/backend/vif/22/0/vifname

This may, or may not be a problem.

> ====
> This occures both before and after I install the pci and network drivers.
> Before install of network drivers windows reports a realtek ethernet device
> After install of network drivers windows reports Xen Net Device Driver
> It does have the correct mac address.
> The interface does not get an IP via dhcp - if manually configured it still 
> cannot ping the default router for the network it should be on.

What does ifconfig and brconfig show for the virtual interface on
the dom0 side ?
====
bridge0: flags=41<UP,RUNNING> mtu 1500

xvif8.0: flags=8963<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,SIMPLEX,MULTICAST> 
mtu 1500
        capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
        enabled=0
        address: aa:00:00:51:02:15
        inet6 fe80::a800:ff:fe51:215%xvif8.0 prefixlen 64 scopeid 0xb
===
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--