From: "B.G. Bruce" <bgb@nt-nv.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: RE: More driver domain issues - rebooting backend hangs
Date: Tue, 08 Feb 2005 08:53:40 -0400 [thread overview]
Message-ID: <1107867220.9884.11.camel@master.vms.security> (raw)
In-Reply-To: <1107863884.9884.5.camel@master.vms.security>
Well, that idea was wrong. I've got my front end now using a
vif-be-bridge script that is basically the vif-bridge script with the
brctl/ifconfig/iptables commands removed. I get nothing reported in
xend-debug now, but the backends still hang on a poweroff or reboot.
B.
On Tue, 2005-02-08 at 07:58, B.G. Bruce wrote:
> With the latest pull for testing, I now get more info in xend-debug.log
> that may help to diagnose as well. This is what is reported as I
> shutdown the driver domains AFTER the front end domain has properly
> terminated.
>
> {}
> {}
> {}
> {}
> VirqClient.virqReceived> 4
> vif-bridge down vif=vif5.0 domain=be01-vsw mac=aa:00:04:fa:00:02
> bridge=mgmt
> VirqClient.virqReceived> 4
> vif-bridge down vif=vif7.0 domain=be03-3c59x mac=aa:00:04:fa:00:04
> bridge=mgmt
> VirqClient.virqReceived> 4
> vif-bridge down vif=vif8.0 domain=fwmgmt mac=aa:00:02:fa:00:05
> bridge=e1000
> bridge e1000 doesn't exist!
> vif-bridge down vif=vif8.1 domain=fwmgmt mac=aa:00:03:fa:00:05
> bridge=3c59x
> bridge 3c59x doesn't exist!
> CtrlMsgRcvr>writeRequest> no channel!
> <xen.xend.server.netif.NetifBackendController instance at 0xb7671e2c>
> vif-bridge down vif=vif8.2 domain=fwmgmt mac=aa:00:01:fa:00:05
> bridge=vsw
> bridge vsw doesn't exist!
> CtrlMsgRcvr>writeRequest> no channel!
> <xen.xend.server.netif.NetifBackendController instance at 0xb7671f6c>
> vif-bridge down vif=vif8.3 domain=fwmgmt mac=aa:00:04:fa:00:05
> bridge=mgmt
> VirqClient.virqReceived> 4
> vif-bridge down vif=vif6.0 domain=be02-e1000 mac=aa:00:04:fa:00:03
> bridge=mgmt
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-08 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 1:51 More driver domain issues - rebooting backend hangs Ian Pratt
2005-02-07 13:48 ` B.G. Bruce
2005-02-07 22:16 ` B.G. Bruce
2005-02-08 11:58 ` B.G. Bruce
2005-02-08 12:53 ` B.G. Bruce [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-08 22:45 Ian Pratt
2005-02-09 0:47 ` B.G. Bruce
2005-02-04 15:37 B.G. Bruce
2005-02-06 11:23 ` B.G. Bruce
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=1107867220.9884.11.camel@master.vms.security \
--to=bgb@nt-nv.com \
--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.