Re: [Xen-devel] Bridge not coming up

[Phil C. <pa...@fo...>]

On Thu, Nov 11, 2004 at 09:36:29PM +0000, Mark A. Williamson wrote:
> Have you checked the files /var/log/{xend,xend-debug}.log?  Do they contain 
> evidence of any interesting explosions?  If so, please post it back to us.
> 
> Does anyone else with RHEL see this?
 
 Here is the tail end of a boot sequence where this happend..
Simply doing a 'xend restart' seems to fix the problem.


----------------- xend-debug.log ----------------
VirqClient.virqReceived> 4
vif-bridge down vif=vif43.0 domain=home mac=aa:00:00:29:e1:6b bridge=xen-br0
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: c0100000->c0337e80
 Init. ramdisk: c0338000->c0338000
 Phys-Mach map: c0338000->c0358000
 Page tables:   c0358000->c035a000
 Start info:    c035a000->c035b000
 Boot stack:    c035b000->c035c000
 TOTAL:         c0000000->c0400000
 ENTRY ADDRESS: c0100000
vif-bridge up vif=vif44.0 domain=vserv2 mac=aa:00:00:66:d3:54 bridge=xen-br0
recv_fe_driver_status> {'status': 1}

recv_fe_driver_status>

recv_fe_interface_connect {'tx_shmem_frame': 499742, 'rx_shmem_frame': 499741, 'handle': 0}
VirqClient.virqReceived> 4
vif-bridge down vif=vif44.0 domain=vserv2 mac=aa:00:00:66:d3:54 bridge=xen-br0
----------------- xend-debug.log ----------------
 

-Phil Carinhas
--
 .--------------------------------------------------------.
 | Dr. Philip A. Carinhas       | pac(at)fortuitous.com   |
 | Fortuitous Technologies Inc. | http://fortuitous.com   |
 | Linux Networking & Security  | Tel : 1-512-351-7783    |
 `--------------------------------------------------------'