View source for Ubuntu DomainU Fails to boot with "Error: Device 0 (vif) could not be connected. Could not find bridge, and none was specified".

After installing the xen-server packages on an Ubuntu system and creating a Xen domainU system the guest fails to boot with the following output:

<pre>
"Error: Device 0 (vif) could not be connected. Could not find bridge, and none was specified".
</pre>

This problem relates to the networking configuration of the Xen domain0 on the host system. By default, the Ubuntu implementation of Xen is installed with networking support disabled. If the domainU configuration file contains a ''vif'' directive, therefore, domain0 will be unable to find a network bridge for the domainU guest.

In order to rectify this problem, simply edit Xend configuration file. The default location for this file is:

<pre>
/etc/xen/xend-config.sxp
</pre>

Once the file is loaded into a suitable editor, simply comment out the following line:

<pre>
(network-script network-dummy
</pre>

so that it appears as follows:

<pre>
#(network-script network-dummy
</pre>

Once this line has been commented out, add a new line beneath it enabling the network bridge so that that the two lines appear as follows:

<pre>
#(network-script network-dummy)
(network-script network-bridge)
</pre>

Having made these changes save the Xend configuration file and then restart the ''xend'' daemon:

<pre>
sudo /init.d/xend restart
</pre>

If restarting the Xen daemon fails to resolve the problem it may be necessary to reboot the host system for the change to take effect.

[[Category:Virtualization Problem Solutions]]