| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] [PATCH][RFC] do ifdown netdev before shutting down vif0 |
| From: | "Kirk Allan" <kallan@xxxxxxxxxx> |
| Date: | 2006年10月12日 13:37:37 -0600 |
| Delivery-date: | 2006年10月12日 12:38:22 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
I've been trying to track down an occasional system hang when doing
/etc/xen/scripts/network-bridge stop. Would it be reasonable to do the fdown
${netdev} and then set ${vif0} down to provide ifdown with a behavior that is
as close as possible to a real network card?
Signed- off- by: Kirk Allan <kallan@xxxxxxxxxx>
Attachment:
network-bridge.diff
Description: Binary data
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] intel g965 + wine questions , Julian Davison |
|---|---|
| Next by Date: | [Xen-devel] [PATCH] an obvious fix to PIC IO intercept , Li, Xin B |
| Previous by Thread: | [Xen-devel] Apache in Xen guest , Apparao, Padmashree K |
| Next by Thread: | RE: [Xen-devel] [PATCH][RFC] do ifdown netdev before shutting down vif0 , Ian Pratt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |