> Dec 20 09:38:58 vt-dp3 xenstored: [ID 702911 daemon.error] TDB error on read: > Corrupt database
Aha! (I've had a couple of xenstory registry corruptions in the past, too) > And I tried to remove /var/lib/xenstored/tdb and > reboot the machine. After that, I even can not read > device-misc/vif/default-nic. > [vt-dp3@/]/usr/lib/xen/bin/xenstore-read device-misc/vif/default-nic > /usr/lib/xen/bin/xenstore-read: couldn't read path device-misc/vif/default-nic Ok, that's the expected behaviour. A fresh / empty xenstore registry was created on the next start of the xenstore daemon. > But after I create a Guest, I can read it and the > default value is e1000g2 now. > [vt-dp3@/]/usr/lib/xen/bin/xenstore-read > device-misc/vif/default-nic > e1000g2 Yep, the default nic was determined when starting the first guest domain, and the default nic was stored to the xenstore registry. This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list [email protected]
