Description of problem: When taking baby steps on getting a xen client going, the error message 'Error: Device 769 (vbd) could not be connected. Hotplug scripts not working.' appears: [root@buran xen]# xm create -c myxen vmid=1 Using config file "myxen". Error: Device 769 (vbd) could not be connected. Hotplug scripts not working. 'myxen' is the stock xmexample1 script - only thing changed is the name of the kernel image. And since my disks are sda and sdb, the default disk drive didn't exist. Suggest a 'specify an existing disk, dummy' error message.
*** Bug 211681 has been marked as a duplicate of this bug. ***
On current RHEL-5, you get the following message if you try to start a guest with a disk that doesn't exist: [root@dhcp83-137 xen]# xm create rhel5test Using config file "./rhel5test". No handlers could be found for logger "xend" Error: Disk isn't accessible Usage: xm create <ConfigFile> [options] [vars] Is that sufficient, or do you want more error logging? Chris Lalancette
That's sufficient, I think...
OK, excellent. I'm pretty sure this has been in there for quite a while at this point, so I'm going to close it out as CURRENTRELEASE. If you find differently, or run into similar problems, feel free to reopen. Chris Lalancette