Ian Campbell <[email protected]> writes:
> FWIW xenstore-ls (perhaps with -f mostly prints the same thing...
Thanks, I found this only later :-)
> I think you have a more fundamental issue which is that the backends are
> not reacting at all to the creation of new backends.
>
> You do have them loaded right? What does "ls /sys/bus/xen*/drivers"
> show?
# ls /sys/bus/xen*/drivers
/sys/bus/xen-backend/drivers:
pciback vbd vif
/sys/bus/xen/drivers:
pcifront
# tree /sys/bus/xen*/drivers
/sys/bus/xen-backend/drivers
|-- pciback
| |-- bind
| |-- module -> ../../../../module/xen_pciback
| |-- uevent
| `-- unbind
|-- vbd
| |-- bind
| |-- module -> ../../../../module/xen_blkback
| |-- uevent
| `-- unbind
`-- vif
|-- bind
|-- module -> ../../../../module/xen_netback
|-- uevent
`-- unbind
/sys/bus/xen/drivers
`-- pcifront
|-- bind
|-- module -> ../../../../module/xen_pcifront
|-- uevent
`-- unbind
8 directories, 12 files
> You haven't by any chance restarted xenstored since you booted this dom0
> have you? xenstored doesn't restart very gracefully and in particular
> one thing which gets lost is the backend's watches which trigger them to
> see a new device entry. If this is the case then I'm afraid the only
> option is to reboot the entire system :-(
That I might have indeed done during all the debugging.
-Timo
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
