From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Knorr Subject: Re: unstable network trouble Date: Mon, 31 Oct 2005 11:58:10 +0100 Message-ID: <4365F8C2.4040809@suse.de> References: <4360DCDE.6000207@suse.de> <20051027151234.GX13783@leeni.uk.xensource.com> <4360F5AA.20207@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4360F5AA.20207@suse.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: xen-devel List-Id: xen-devel@lists.xenproject.org > Hmm, no, seems to be a missing hotplug event. Sticked some printk's into the net backend, looks like a xenbus issue: domU boot with broken network: netback_probe: add backend watch netback_probe: add frontend watch netback_probe: done frontend_changed: called frontend_changed: called frontend_changed: called frontend_changed: called domU boot with working network: netback_probe: add backend watch netback_probe: add frontend watch netback_probe: done backend_changed: called backend_changed: hotplug online netback_hotplug: called frontend_changed: called frontend_changed: called device vif2.0 entered promiscuous mode xenbr0: port 3(vif2.0) entering learning state xenbr0: topology change detected, propagating xenbr0: port 3(vif2.0) entering forwarding state frontend_changed: called frontend_changed: called frontend_changed: called Note that backend_changed is never called in the first case. cheers, Gerd