[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Re: Can't start domU after upgrade to xen3.3.0


  • To: "Andy Burns" <xen.lists@xxxxxxxxxxx>
  • From: "Todd Deshane" <deshantm@xxxxxxxxx>
  • Date: Mon, 1 Sep 2008 11:46:11 -0400
  • Cc: Xen Users <Xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 01 Sep 2008 08:46:45 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=YHJ+VZRYm/gB0NlaXgZmasacCj0sHbGzb/4IhFN7SEgdDF823MtGQ5QiE7iQ6SbJad mY00bcXWOdhbVEbrs4tZ250u6masl4GDyMu3Icbf1nP3F+xX0aVFZjGXLOUCg8/5vUl3 3xRp7WIzEJQon09RTBcHHD00jRaMgeMA3MkQc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Mon, Sep 1, 2008 at 7:07 AM, Andy Burns <xen.lists@xxxxxxxxxxx> wrote:
> 2008/8/31 Andy Burns <xen.lists@xxxxxxxxxxx>:
>
>> xm start mydomU complains
>> "Error: Device 0 (vif) could not be connected. Hotplug scripts not working."
>
> I thought this might be due to my "(network-script
> network-bridge-wrapper)" script which sets up eth1 and well as eth0,
> so took it out but made no difference, xen-hotplug.log still empty,
> any clues how to trace what's going on?
>

You can add +x to the shell scripts (the network scripts), which should produce
output to the system logger (i.e syslog)

Also, sometimes xenstore-* commands can help.

Cheers,
Todd


-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.