From: Phil Carinhas <pac@fortuitous.com>
To: "Mark A. Williamson" <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, pac@fortuitous.com
Subject: Re: Bridge not coming up
Date: Thu, 11 Nov 2004 16:52:30 -0600 [thread overview]
Message-ID: <20041111225230.GA28690@mail.fortuitous.com> (raw)
In-Reply-To: <200411112136.30263.mark.williamson@cl.cam.ac.uk>
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 |
`--------------------------------------------------------'
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-11 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 20:28 Bridge not coming up Phil Carinhas
2004-11-11 21:36 ` Mark A. Williamson
2004-11-11 22:52 ` Phil Carinhas [this message]
2004-11-12 1:51 ` Phil Carinhas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041111225230.GA28690@mail.fortuitous.com \
--to=pac@fortuitous.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.