DomainU Fails to boot with "Error: Device 0 (vif) could not be connected. Could not find bridge, and none was specified"
来源:互联网 发布:清华大学网络公开课 编辑:程序博客网 时间:2024/05/16 14:53
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: 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: Once the file is loaded into a suitable editor, simply comment out the following line: so that it appears as follows: 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: Having made these changes save the Xend configuration file and then restart the xend daemon: 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."Error: Device 0 (vif) could not be connected. Could not find bridge, and none was specified".
/etc/xen/xend-config.sxp
(network-script network-dummy)
#(network-script network-dummy)
#(network-script network-dummy)(network-script network-bridge)
sudo /init.d/xend restart
- DomainU Fails to boot with "Error: Device 0 (vif) could not be connected. Could not find bridge, and none was specified"
- Brew AppLoader "Error - Either could not detect any device with the specified"
- GetModuleFileName False failed with error 126 (The specified module could not be found)
- A server with the specified hostname could not be found.
- Error: Application server fails to start with the following error WSNAT_CAT:1008: ERROR: Could not establish listening address o
- Error:JAVA_HOME is not set and could not be found
- progisp下载错误-error:could not find USBASP device
- The specified module could not be found
- The specified module could not be found
- OAF Could not find the specified responsibility.
- Cornerstone--could not find the specified file
- Error:Could not find wechat-sdk-android-with-mta.jar
- [Nagios] Error: Template 'timman' specified in contact definition could not be not found (c
- could not write to the device
- Failed to connect to the specified server. Server library could not be loaded
- ERROR The requested URL could not be retrieved The following error was encountered
- eclipse error: * could not be resolved
- Eclipse error: *** could not be resolved
- 修改grub启动项
- Microsoft eMbedded Visual C++ has discovered no CE platform SDK installed on the desktop please install at least one CE platform
- 使用 VMProtect 出现 未闭合标识的解决方法
- [opendoc]swift实战_纲要
- Silverlight, RIA Services, Data Annotation与本地化资源文件共享
- DomainU Fails to boot with "Error: Device 0 (vif) could not be connected. Could not find bridge, and none was specified"
- C#的Socket实现UDP协议通信
- 欲成事者之法
- Android_UI_中常用的两种ProgressDialog
- [原创]Weird C++ (before 0x) (updating)
- java 命令行输入 及密码读入
- 等差等比数列求和公式,排列组合公式, 二项式求根公式
- Ubuntu 11.04 x64 下安装Python
- 技术还是商业重要