14 messages in com.xensource.lists.xen-develRe: [Xen-devel] BUG? domu network in...
FromSent OnAttachments
Michal OstrowskiAug 30, 2005 5:23 pm 
Keir FraserAug 31, 2005 1:00 am 
Ted KaczmarekAug 31, 2005 4:44 am 
Ian PrattAug 31, 2005 5:01 am 
Michal OstrowskiAug 31, 2005 5:42 am 
Ted KaczmarekAug 31, 2005 6:11 am 
Christian LimpachAug 31, 2005 6:53 am 
Hien NguyenAug 31, 2005 7:59 am 
Ted KaczmarekAug 31, 2005 8:09 am 
Michal OstrowskiAug 31, 2005 8:23 am 
Nivedita SinghviAug 31, 2005 9:03 am 
Hien NguyenAug 31, 2005 9:56 am 
Hien NguyenAug 31, 2005 3:07 pm 
Michal OstrowskiSep 1, 2005 7:26 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [Xen-devel] BUG? domu network interface configurationActions...
From:Ted Kaczmarek (ted@optonline.net)
Date:Aug 31, 2005 4:44:46 am
List:com.xensource.lists.xen-devel

On Wed, 2005-08-31 at 09:00 +0100, Keir Fraser wrote:

On 31 Aug 2005, at 01:24, Michal Ostrowski wrote:

- vif-route has never been called, so the domain's networking doesn't come up, even though the domain runs.

- this same configuration was working prior to an update this afternoon (previous snapshot was from last Thursday).

The changes to xenbus mean that we call vif up/down via hotplug, and our hotplug script is hardcoded to call the bridge script. Probably it ought to pull stuff out of xenstore to work out what to do, but that's not implemented right now.

One fix would be for you to just hack the hotplug script. Another, slightly better, way would be to grep around in xend's config script to find out what script should be run, and call that. We might even take that as an interim patch.

-- Keir

Any idea when this would be implemented?

Regards, Ted

_______________________________________________ Xen-devel mailing list Xen-@lists.xensource.com http://lists.xensource.com/xen-devel