> > I think the default nic is cached in the "xenstore" registry
>
> > Check with "/usr/lib/xen/bin/xenstore-read device-misc/vif/default-nic".
>
> > You probably have to remove that property from xenstore,
> > so that a new default nic is determined from svcprops or
> > dladm (and written to xenstore).
>
> > "/usr/lib/xen/bin/xenstore-rm device-misc/vif/default-nic"
> > should remove the old default nic key/value.
>
> Thanks for your info. But the command does not work
> on my system.
> [vt-dp3@/]/usr/lib/xen/bin/xenstore-read device-misc/vif/default-nic
> e1000g0
> [vt-dp3@/]/usr/lib/xen/bin/xenstore-rm device-misc/vif/default-nic
> /usr/lib/xen/bin/xenstore-rm: could not remove path
> device-misc/vif/default-nic
That xenstore-rm failure might explain why the wrong interface
is persistent across reboots. The snv77 smf(5) startup method for
xend (/lib/svc/method/xend) tries to run exactly the same command
to force selecting a new default nic when the first domain starts:
/lib/svc/method/xend:
27 default_nic_path=device-misc/vif/default-nic
....
40 #
41 # Ensure that booting the first domain will determine
42 # the default NIC correctly.
43 #
44 /usr/lib/xen/bin/xenstore-rm $default_nic_path 2>/dev/null
45
46 /usr/lib/xend start
During a reboot, did you notice any error messages on the
console or in /var/adm/messages about a corrupted xenstore
database?
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
[email protected]
