Port-xen archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Reboot on *DOM0* while/after installing GPLPV drivers
On Mon, Oct 21, 2013 at 07:17:09PM +0100, Mike C. wrote:
> On 10/21/13 18:25, Manuel Bouyer wrote:
> > 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 ?
> >
>
> Mine shows:
> xvif29i0: flags=8923<UP,BROADCAST,NOTRAILERS,PROMISC,SIMPLEX,MULTICAST>
> mtu 1500
> capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
> enabled=0
> address: 00:16:3e:4f:5c:6e
> inet6 fe80::216:3eff:fe4f:5c6e%xvif29i0 prefixlen 64 scopeid 0x25
>
> Seems ok
>
> And brconfig -a
> # brconfig -a
>
> bridge0: flags=41<UP,RUNNING>
> Configuration:
> priority 32768 hellotime 2 fwddelay 15 maxage 20
> ipfilter disabled flags 0x0
> Interfaces:
> xvif29i0 flags=3<LEARNING,DISCOVER>
> port 37 priority 128
> tap0 flags=3<LEARNING,DISCOVER>
> port 36 priority 128
> xvif1i0 flags=3<LEARNING,DISCOVER>
> port 6 priority 128
> re1 flags=3<LEARNING,DISCOVER>
> port 2 priority 128
> Address cache (max cache: 100, timeout: 1200):
> dc:71:44:3e:b2:c9 re1 1120 flags=0<>
> 60:a4:4c:28:13:c0 re1 1117 flags=0<>
> f4:ce:46:ee:1b:f0 re1 589 flags=0<>
> 24:db:ac:8c:bf:7b re1 585 flags=0<>
> 00:16:3e:52:3e:cf xvif1i0 217 flags=0<>
> 24:db:ac:8c:c4:df re1 86 flags=0<>
> 00:16:3e:4e:5c:6e tap0 18446744073709551576 flags=0<>
> ac:81:12:35:79:73 re1 18446744073709551539 flags=0<>
> e0:06:e6:aa:bf:5b re1 18446744073709551534 flags=0<>
>
>
> xvifli0 is a FreeBSD DomU which is working fine!
it looks like xvif29i0 isn't receivng anying.
does netstat -iIxvifli0 show anything ?
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index