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

RE: [Xen-devel] VM creation failure using passthrough with latestunstable


  • To: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ross Philipson" <Ross.Philipson@xxxxxxxxxx>
  • Date: Wed, 23 Jul 2008 08:15:41 -0400
  • Cc:
  • Delivery-date: Wed, 23 Jul 2008 05:16:13 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcjsI/xMqu8AwcH2QVyJcB9YA6Jk1gARDjvwABVO4wA=
  • Thread-topic: [Xen-devel] VM creation failure using passthrough with latestunstable

Thanks, that was certainly the problem. The error messages are misleading as is the xend log trace. The bdf value returned is -1 which is why the trace output shows incorrect PCI information. The attached patch e.g. might not be the prettiest output but it would be correct.

 

From: Cui, Dexuan [mailto:dexuan.cui@xxxxxxxxx]
Sent: Tuesday, July 22, 2008 10:10 PM
To: Ross Philipson; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] VM creation failure using passthrough with latestunstable

 

>   File "//usr/lib/python/xen/xend/XendDomainInfo.py", line 2094, in _constructDomain
>     raise VmError("Fail to assign device(%x:%x.%x): maybe VT-d is "
>  VmError: Fail to assign device(ff:1f.7): maybe VT-d is not enabled, or the device is not exist, or it has already been assigned to other domain

 

According to the log (actually bdf = -1 here), I believe it's due to the recent changeset:

 

7 days ago: iommu: disable by default. 'iommu' on cmdline to enable.
changeset 18057: b5bfe3515f65
http://xenbits.xensource.com/xen-unstable.hg?rev/b5bfe3515f65

 

Now you need to specify "iommu=1" in the Xen grub entry to assign iommu devices.

 

I think the error message "Error: (‘<domain GUID>’, ‘VM_metrics’)" is confusing... We'd better improve it.

 
Thanks,
-- Dexuan

 


From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ross Philipson
Sent: 2008
723 1:54
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] VM creation failure using passthrough with latestunstable

I have pulled a recent (today’s) clone of staging/xen-unstable.hg and I get a failure when trying to create a domain with xend/xm. The failure I get is:

 

Error: (‘<domain GUID>’, ‘VM_metrics’)

 

I have traced the problem down to where the  pci = [ ’02:00.0’ ] parameter (which is the value in my case) from my configuration file is being tested in xc.c:pyxc_test_assign_device(). This function fails and causes the calling code in xm/create.py:make_domain() to fail. The attached log shows the output where this fails – the wrong values for the bus/dev/func are clearly being traced out.

 

Something changed in the last 2 – 3 weeks to cause this. I do not see this issue with a July 2 pull of unstable. I will keep digging but I hoped something would ring a bell.

 

Thanks

Ross

 

Ross Philipson

Senior Software Engineer

Citrix Systems, Inc

14 Crosby Drive

Bedford, MA 01730

781-301-7949

ross.philipson@xxxxxxxxxx

 

Attachment: xend-iommu-error-logging.patch
Description: xend-iommu-error-logging.patch

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

 


Rackspace

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