http://bugzilla.novell.com/show_bug.cgi?id=620224 http://bugzilla.novell.com/show_bug.cgi?id=620224#c7 mail ignored <0.bugs.only.0@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|0.bugs.only.0@gmail.com | --- Comment #7 from mail ignored <0.bugs.only.0@gmail.com> 2010-07-13 07:40:14 PDT --- (In reply to comment #6)
It seems like this is because pciback.ko is not loaded at the time the system goes down. Assuming the driver is present while you run the domains,
it is, xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1010 1 r----- 175.1 fw 1 1024 4 -b---- 13.2 nas 2 1024 4 -b---- 6.9 lsmod | grep -i pciback pciback 55565 0 xenbus_be 3706 5 usbbk,netbk,blkbk,blktap,pciback
are you later removing it manually for some reason?
no, neither manually, nor intentionally. checking after 'destroy', prior to shutdown, xm destroy 1 xm destroy 2 grep -i pciback pciback 55565 0 xenbus_be 3706 5 usbbk,netbk,blkbk,blktap,pciback it's still there.
If not, we'll have to find what it is that triggers its removal. Are you keeping the devices you passed through bound to pciback after the guests terminate?
I'm doing nothing manually to either keep, or dispose of, the bindings.
A xenstore listing of the tree under /local/domain/0/backend/pci/ would also likely be helpful to see (obtained right before shutting down Dom0).
xenstore-list /local/domain/0 vm device control error memory guest hvmpv data cpu description console domid name xm create fw.cfg xm create nas.cfg xenstore-list /local/domain/0 (... as above ...) backend device-model xenstore-list /local/domain/0/backend/pci 1 2 xm destroy 1 xm destroy 2 xenstore-list /local/domain/0/backend/pci xenstore-list: could not list path /local/domain/0/backend/pci xenstore-list /local/domain/0 (... as above ...) device-model I'll get to work on providing the other data requested above. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.