Xen - can't create domain because 'vdb could not be connected'

I'm attempting to start up a Xen VM, nonetheless I'm obtaining the adhering to mistake:

Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working.

what does this suggest?

The dom0 is CentOS and also the visitor OS is Debian Lenny. The network user interfaces I'm making use of are:

vif = [ 'mac=00:16:3e:3e:53:5f, bridge=xenbr0', 'mac=00:16:3e:18:16:e5, bridge=xenbr1' ]

The origin filesystem of the visitor OS is readied to place over NFS from the dom0, this is benefiting various other visitor OSs on the very same host. The swap (and also /var) is placed from a neighborhood LVM sensible quantity

UPDATE My mistake. I had not created the config appropriately, and also had not set up the filesystems appropriately. I had the ability to consider /var/log/xen/xen-hotplug.log to see that it was accessing the incorrect tool.

1
2022-06-07 14:33:30
Source Share
Answers: 2

My mistake. I had not created the config appropriately, and also had not set up the filesystems appropriately. I had the ability to consider/ var/log/xen/ xen - hotplug.log to see that it was accessing the incorrect tool.

0
2022-06-08 16:29:20
Source

Short variation:

Check that you have /etc/udev/rules.d/xen-backend.rules. The documents might or might not be prefixed by a number.

Otherwise, examine whether you have /etc/udev/xen-backend.rules and also create a symlink from that to /etc/udev/rules.d/xen-backend.rules.

Lengthy variation:

I've seen this with a Gentoo 3.3 dom0, not CentOS. Yet I believe the solution will certainly coincide or comparable.

The Xen construct manuscripts call a command udevinfo -V to establish the variation of udev mounted on the equipment. The udevinfo energy was decreased a while earlier in favour of udevadm. In even more current launches of udev the old energy has actually been gotten rid of completely.

The construct manuscripts make use of the variation of udev gotten as defined to establish what installments actions require to be taken on. If it can not find/match the udev variation after that it will not mounted the called for udev regulation. By not having udevinfo existing, this is what is taking place.

Currently it is possibly considered that you do not intend to downgrade udev. To make sure that leaves 2 remedies.

You can either examine whether your plan representative has actually dealt with the concern. As an example it is dealt with in Xen 4.4 on Gentoo based on this bug.

Conversely, you can function around it momentarily, by misleading it that udevinfo is still existing and also acting in the manner in which it anticipates. We can do this by scripting/proxying to the new udevadm command:

# echo -e '#!/bin/bash\n/sbin/udevadm info $1' > /usr/bin/udevinfo
# chmod +x /usr/bin/udevinfo
*** Install Xen ***
# rm /usr/bin/udevinfo

This will certainly get it functioning once more. Yet you will certainly still require to deal with the concern in the future.

2
2022-06-07 14:56:01
Source