Could you try this as a workaround: In dom0:
sudo xenstore-write /local/domain/0/vm hello I think this might be the same problem as reported by John Weber on xen-api -- Dave Scott On May 23, 2012, at 7:11 PM, "George Shuklin" <[email protected]> wrote: > Some more data: > > Done clean reinstall (now with i386 in dom0), got exactly same error. > > After some digging around got this (new uuids, same problem): > > Key logs entries: > [20120523T17:50:08.602Z|debug|lab-xh3|249 UNIX > /var/lib/xcp/xapi|VM.start R:1c6c2941c565|xenops] Device.Vbd.add > (device_number=Xen(0, 0) | > params=/dev/sm/backend/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/741cb833-b2c3-4bf7-b724-1295e984f097 > > | phystype=vhd) > [20120523T17:50:08.602Z|debug|lab-xh3|249 UNIX > /var/lib/xcp/xapi|VM.start R:1c6c2941c565|xenops] adding device > B0[/local/domain/0/backend/vbd/4/51712] > F4[/local/domain/4/device/vbd/51712] H[/xapi/4/hotplug/vbd/51712] > [20120523T17:50:08.603Z|debug|lab-xh3|249 UNIX > /var/lib/xcp/xapi|VM.start R:1c6c2941c565|backtrace] Raised at > device.ml:65.10-42 -> xst.ml:52.18-23 -> xst.ml:55.9-12 -> > device.ml:497.1-60 -> vbdops.ml:102.37-229 -> > storage_access.ml:516.14-317 -> xapi_xenops_errors.ml:79.4-8 > [20120523T17:50:08.603Z|debug|lab-xh3|249 UNIX > /var/lib/xcp/xapi|VM.start R:1c6c2941c565|xapi] Converting xenops > exception (INTERNAL_ERROR: [ Device_common.Device_backend_vanished(_) ]) > into nice API internal error > > > I've checked - when I plug vbd to dom0 it works fine, but I can't do it > with other domains. > > _______________________________________________ > Xen-api mailing list > [email protected] > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
