> 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:
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
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
|