When using virtual frame buffer directive in the domU config file: vfb= [ ''type=xxx,....] vbd gets started but vbkd device cannot start, so is this the race condition that was discussed a while ago (patched in april I think) ? Error: Device 0 (vkbd) could not be connected. Hotplug scripts not working This problem was in 3.1-testing and 3.-unstable and now appears to be in 3.1(downloaded today). Any ideas much appreciated. Jon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
When using virtual frame buffer directive in the domU config file: vfb= [ ''type=xxx,....] vbd gets started but vbkd device cannot start, so is this the race condition that was discussed a while ago (patched in april I think) ? Error: Device 0 (vkbd) could not be connected. Hotplug scripts not working This problem was in 3.1-testing and 3.-unstable and now appears to be in 3.1 (downloaded today). Any ideas much appreciated. Jon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
When using virtual frame buffer directive in the domU config file: vfb= [ ''type=xxx,....] vbd gets started but vbkd device cannot start, so is this the race condition that was discussed a while ago (patched in april I think) ? Error: Device 0 (vkbd) could not be connected. Hotplug scripts not working This problem was in 3.1-testing and 3.-unstable and now appears to be in 3.1 (downloaded today). Any ideas much appreciated. Jon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Maybe Matching Threads
- Error: Device 0 (vkbd) is already connected.
- Hanging boot of solaris 11 install image as HVM
- Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
- Ubuntu DomU does not finish booting up.
- Xen 4.0 - prerequisites for succesfull live migration?