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

[Xen-users] tracebacks?


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
  • Date: Wed, 9 Aug 2006 23:20:29 +0200
  • Delivery-date: Wed, 09 Aug 2006 14:21:12 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=L+X+jKXrFHxU6rXl7iXluUKDHlBLHCM2L+hae8Xjgbob4MSvMBqaH9xlQGdCosuBIoxuZssBOxTfVQCVKil1VmdIJgQnLXlK+iomQ6Vz+pddpubj0GK7xPZETx5dKv/2xmPAWDtU3GRxIy9oh3E84WE4wbJu26HJAcr9tn5ibDo=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

How do I enable tracebacks for Xen commands?

I get this:
# xm create /etc/xen/blah
Using config file "/etc/xen/blah".
Error: Device 0 (vif) could not be connected. Backend device not found.

Obviously, I need some more information to fix this.
Seeing as the error message sucks, I'll have to look it up in the source.

How do I enable tracebacks, so I can see which file and line of source
code produce this message?

_______________________________________________
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®.