Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com
Answertopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

Red Hat Enterprise Linux 9 Essentials Book now available.

Purchase a copy of Red Hat Enterprise Linux 9 (RHEL 9) Essentials

Red Hat Enterprise Linux 9 Essentials Print and eBook (PDF) editions contain 34 chapters and 298 pages

Preview Book

28.10. Wrong bridge configured on the guest causing hot plug script timeouts

If you have moved configuration files between different hosts you may to make sure your guest configuration files have been updated to reflect any change in your network topology, such as Xen bridge numbering.
If you try to start a guest which has an incorrect or non-existent virtual network bridge configured you will see the following error after starting the guest
# xm create r5b2-mySQL01
Using config file "r5b2-mySQL01".
Going to boot Red Hat Enterprise Linux Server (2.6.18-1.2747.el5xen)
kernel: /vmlinuz-2.6.18-1.2747.el5xen
initrd: /initrd-2.6.18-1.2747.el5xen.img
Error: Device 0 (vif) could not be connected. Hotplug scripts not working
In /var/log/xen/xen-hotplug.log you will see the following error being logged
bridge xenbr1 does not exist!
and in /var/log/xen/xend.log you will see the following messages (or similar messages) being logged
[2006-12-14 15:07:08 xend 3874] DEBUG (DevController:143) Waiting for devices vif.
[2006-12-14 15:07:08 xend 3874] DEBUG (DevController:149) Waiting for 0.
[2006-12-14 15:07:08 xend 3874] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2006-12-14 15:07:08 xend 3874] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2006-12-14 15:08:48 xend.XendDomainInfo 3874] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=2
[2006-12-14 15:08:48 xend.XendDomainInfo 3874] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(2)
[2006-12-14 15:08:48 xend 3874] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2006-12-14 15:08:48 xend 3874] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2006-12-14 15:08:48 xend 3874] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2006-12-14 15:08:48 xend 3874] DEBUG (DevController:464)
hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
To resolve this issue edit your guest's configuration file and modify the vif entry to reflect your local configuration. For example if your local configuration is using xenbr0 as its default bridge you should modify your vif entry in your configuration file from
vif = [ 'mac=00:16:3e:49:1d:11, bridge=xenbr1', ]
to
vif = [ 'mac=00:16:3e:49:1d:11, bridge=xenbr0', ]

 
 
  Published under the terms of the GNU General Public License Design by Interspire