|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup
Hi,
2010/3/22 Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>:
> What is the version of Xen tools you have? Did you build them from
> xen-unstable?
Yes, there are from xen-unstable
>> "0000:00:1a.1">/sys/bus/pci/devices/0000:00:1a.1/driver/unbind
>> root@debian:~# echo "0000:00:1a.1">/sys/bus/pci/drivers/pci-stub/bind
>
> Where did you get the documentation for those steps? I would suggest you use
> the 'pciback' instead of 'pci-stub' module for this just to see if that
> makes the 'pciback' later error go away.
Well, I missread http://wiki.xensource.com/xenwiki/VTdHowTo I
switched to pciback(I used
http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module)
and this error no longer occurs.
> Uhh. So you assigned the device to 'pci-stub', and somehow 'pciback' gets
> involved. That is not good. PCI back is to be used _only_ with
> PV guests - you on the other hand are running an HVM guest.
>
> Per the earlier statement, I would recommend you use the 'pciback'
> instead of 'pci-stub' or just not compile pciback in and see what
> happens. Keep in mind: PCI back module is only needed when you want to do PV
> PCI
> passthrough, which is not what you are doing.
>
Wiki says something else (http://wiki.xensource.com/xenwiki/VTdHowTo)
So pciback or pci-stub for HVM?
from wiki: "If using pv-ops dom0, also can use pci-stub to hide
devices for assignment"
>> [ 733.248052] pciback pci-3-0: 22 Couldn't locate PCI device
>> (0000:00:1a.0)! perhaps already in-use?
>
> Can you paste your 'xenstore-ls /local/domain/0' output when this
> happening?
When using pci-stub:
xenstore-ls /local/domain/0
vm = "/vm/00000000-0000-0000-0000-000000000000"
device = ""
control = ""
platform-feature-multiprocessor-suspend = "1"
error = ""
backend = ""
pci = ""
1 = ""
0 = ""
error = "22 Couldn't locate PCI device (0000:01:01.0)! perhaps
already in-use?"
memory = ""
target = "1017632"
guest = ""
hvmpv = ""
data = ""
cpu = ""
1 = ""
availability = "online"
0 = ""
availability = "online"
description = ""
console = ""
limit = "1048576"
type = "xenconsoled"
domid = "0"
name = "Domain-0"
device-model = ""
1 = ""
disable_pf = "0"
state = "running"
parameter = "0x20"
backend = ""
vfb = ""
1 = ""
0 = ""
vncunused = "1"
domain = "ExampleHVMDomain"
vnc = "1"
uuid = "e4f967e1-9ab9-6170-9392-711b7eee638d"
vnclisten = "0.0.0.0"
frontend = "/local/domain/1/device/vfb/0"
state = "1"
online = "1"
frontend-id = "1"
location = "0.0.0.0:5900"
vbd = ""
1 = ""
768 = ""
domain = "ExampleHVMDomain"
frontend = "/local/domain/1/device/vbd/768"
uuid = "f51680ce-7057-ed25-3a4f-aacd78e5f2b5"
bootable = "1"
dev = "hda"
state = "2"
params = "/media/debian.img"
mode = "w"
online = "1"
frontend-id = "1"
type = "file"
node = "/dev/loop1"
physical-device = "7:1"
hotplug-status = "connected"
5632 = ""
domain = "ExampleHVMDomain"
frontend = "/local/domain/1/device/vbd/5632"
uuid = "44367e07-409f-d676-9047-d84b1f2189e2"
bootable = "0"
dev = "hdc"
state = "2"
params = "/media/debian.iso"
mode = "r"
online = "1"
frontend-id = "1"
type = "file"
node = "/dev/loop2"
physical-device = "7:2"
hotplug-status = "connected"
pci = ""
1 = ""
0 = ""
domain = "ExampleHVMDomain"
key-0 = "01:01.0"
vdevfn-0 = "20"
uuid = "01ad7a64-bf43-b782-b4ad-bbcb9060c36a"
dev-0 = "0000:01:01.0"
frontend = "/local/domain/1/device/pci/0"
state = "7"
online = "1"
frontend-id = "1"
opts-0 = "msitranslate=1,power_mgmt=0"
uuid-0 = "9db6e99f-31c4-8a7a-96c4-dd88e130abbe"
num_devs = "1"
state-0 = "1"
console = ""
1 = ""
0 = ""
domain = "ExampleHVMDomain"
protocol = "vt100"
uuid = "ae8d643f-cd4d-2256-2f55-c79736f96311"
frontend = "/local/domain/1/device/console/0"
state = "1"
location = "3"
online = "1"
frontend-id = "1"
>> (XEN) mm.c:859:d1 Error getting mfn 40004 (pfn 5555555555555555) from
>> L1 entry 0000000040004037 for l1e_owner=1, pg_owner=1
>> ...
>> And guest never starts. Perhaps this is related to the firmware which
>> is used by qla2xxx?
>
> So you see this _only_ when you pass in QLA2XXX card, right? When you
> don't pass in a PCI card, you don't see this, correct?
Exactly. This happens with both pciback and pci-stub.
Regards,
Łukasz Oleś
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, (continued)
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Łukasz Oleś
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Łukasz Oleś
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Konrad Rzeszutek Wilk
- RE: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Nadolski, Ed
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Konrad Rzeszutek Wilk
- RE: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Nadolski, Ed
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Sander Eikelenboom
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup,
Łukasz Oleś <=
- Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Konrad Rzeszutek Wilk
|
|
|
|
|