* Windows 8 VGA Passthrough
@ 2013-10-26 20:58 John Wargo
2013-10-27 9:30 ` Gordan Bobic
0 siblings, 1 reply; 20+ messages in thread
From: John Wargo @ 2013-10-26 20:58 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Geniuses,
I've been trying to get VGA pass-through working on Windows 8, however
I've been running into a few issues.
Currently I can get Windows 8 running flawlessly without VGA
pass-through, however I'm planning on using it for gaming, so this wont
work.
When I start windows 8, I am able to get past the install portion of the
DVD, however it hangs on "Getting devices ready.. (n%)".
Hardware Information :
AMD Fx6300
ASUS M5a99x evo r2.0
16GB RAM
6670 Radeon HD - Dom0
7850 Radeon HD - Win8
Attached is a zip with the following debugging files:
dmesg-boot : xl dmesg right after boot
dmesg-win : xl dmesg after windows 8 fails
grub : My grub configuration file
win8.cfg : My Windows 8 configuration file
xen-info : The result of xl info
If I've left out anything, don't hesitate to ask.
Thanks for your time,
-John
[-- Attachment #2: debug.zip --]
[-- Type: application/zip, Size: 6993 bytes --]
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-26 20:58 Windows 8 VGA Passthrough John Wargo
@ 2013-10-27 9:30 ` Gordan Bobic
2013-10-27 14:27 ` John Wargo
[not found] ` <526D1FBA.10708@gmail.com>
0 siblings, 2 replies; 20+ messages in thread
From: Gordan Bobic @ 2013-10-27 9:30 UTC (permalink / raw)
To: John Wargo, xen-devel@lists.xen.org
On 10/26/2013 09:58 PM, John Wargo wrote:
> Geniuses,
>
> I've been trying to get VGA pass-through working on Windows 8, however
> I've been running into a few issues.
> Currently I can get Windows 8 running flawlessly without VGA
> pass-through, however I'm planning on using it for gaming, so this wont
> work.
>
> When I start windows 8, I am able to get past the install portion of the
> DVD, however it hangs on "Getting devices ready.. (n%)".
>
> Hardware Information :
> AMD Fx6300
> ASUS M5a99x evo r2.0
> 16GB RAM
> 6670 Radeon HD - Dom0
> 7850 Radeon HD - Win8
I have recently (recently as in over the past 48 hours) re-tried to get
ATI VGA passthrough working, and the results are... interesting.
HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
ever seems to work (slowdown + white lines when dragging windows after a
domU reboot). I am using XP64 domU so I can't eject the GPU (it says it
is being used). But shutting down the domU, doing echo 1 > reset for the
GPU from dom0 (I don't know how this is implemented and whether it does
anything) and then starting it up again sometimes recovers it. GPU-Z
runs and reports the GPU correctly.
HD4850 dom0 + HD7970 domU results in the entire host locking up as soon
as the driver is loaded in domU. My solution is to swap the dom0 GPU for
an 8800GT, and the problem now doesn't occur. If I had to guess, BIOS on
the HD7970 does something bizzare, finds the HD4850 on the bus, tries to
do something to it, and ends up crashing the host. This could also be
exacerbated by the fact that I have to run with relaxed checking and no
PCI ACS due to NF200 bridges on my motherboard. Even so, however, GPU-Z
crashes the domU and it's GPU _hard_ (but not the host, thankfully). It
crashes it so hard, that the only cure is to reboot the host. Reseting
the GPU via /sys/ doesn't seem to do anything to help.
Are you using gfx_passthru=1 in your config? The way most people have
this kind of thing working is with gfx_passthru=0, i.e. secondary
passthru. Don't assign the PCI device in the config when installing.
Once the domU install is complete, shut it down, and add the GPU you
want to pass through. Then fire up domU in VNC, install the driver, and
with a bit of luck it will come up with output on the external monitor.
Also make sure that radeon or radeonfb kernel drivers DO NOT load before
the device is assigned to xen-pciback. The exact way to ensure this will
depend on what distro and dom0 kernel you are using.
Gordan
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 9:30 ` Gordan Bobic
@ 2013-10-27 14:27 ` John Wargo
2013-10-27 16:21 ` John Wargo
2013-10-27 19:31 ` Gordan Bobic
[not found] ` <526D1FBA.10708@gmail.com>
1 sibling, 2 replies; 20+ messages in thread
From: John Wargo @ 2013-10-27 14:27 UTC (permalink / raw)
To: Gordan Bobic, xen-devel@lists.xen.org
On 10/27/2013 04:30 AM, Gordan Bobic wrote:
> On 10/26/2013 09:58 PM, John Wargo wrote:
>> Geniuses,
>>
>> I've been trying to get VGA pass-through working on Windows 8, however
>> I've been running into a few issues.
>> Currently I can get Windows 8 running flawlessly without VGA
>> pass-through, however I'm planning on using it for gaming, so this wont
>> work.
>>
>> When I start windows 8, I am able to get past the install portion of the
>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>
>> Hardware Information :
>> AMD Fx6300
>> ASUS M5a99x evo r2.0
>> 16GB RAM
>> 6670 Radeon HD - Dom0
>> 7850 Radeon HD - Win8
>
> I have recently (recently as in over the past 48 hours) re-tried to
> get ATI VGA passthrough working, and the results are... interesting.
>
> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
> ever seems to work (slowdown + white lines when dragging windows after
> a domU reboot). I am using XP64 domU so I can't eject the GPU (it says
> it is being used). But shutting down the domU, doing echo 1 > reset
> for the GPU from dom0 (I don't know how this is implemented and
> whether it does anything) and then starting it up again sometimes
> recovers it. GPU-Z runs and reports the GPU correctly.
>
> HD4850 dom0 + HD7970 domU results in the entire host locking up as
> soon as the driver is loaded in domU. My solution is to swap the dom0
> GPU for an 8800GT, and the problem now doesn't occur. If I had to
> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on
> the bus, tries to do something to it, and ends up crashing the host.
> This could also be exacerbated by the fact that I have to run with
> relaxed checking and no PCI ACS due to NF200 bridges on my
> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
> _hard_ (but not the host, thankfully). It crashes it so hard, that the
> only cure is to reboot the host. Reseting the GPU via /sys/ doesn't
> seem to do anything to help.
>
> Are you using gfx_passthru=1 in your config? The way most people have
> this kind of thing working is with gfx_passthru=0, i.e. secondary
> passthru. Don't assign the PCI device in the config when installing.
> Once the domU install is complete, shut it down, and add the GPU you
> want to pass through. Then fire up domU in VNC, install the driver,
> and with a bit of luck it will come up with output on the external
> monitor.
>
> Also make sure that radeon or radeonfb kernel drivers DO NOT load
> before the device is assigned to xen-pciback. The exact way to ensure
> this will depend on what distro and dom0 kernel you are using.
>
> Gordan
Status update:
The catalyst drivers appear to be working perfectly fine, device manager
shows no errors, and everything works great, except that when I plug my
monitor into the second card, I get "No Signal" on the monitor, then it
shuts off.
I though that secondary passthrough meant that it would pass the virtual
adapter in as primary, but I could use my GPU that I passed through, so
where am I wrong, and how do I do that?
-John
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 14:27 ` John Wargo
@ 2013-10-27 16:21 ` John Wargo
2013-10-27 17:21 ` John Wargo
2013-10-27 19:35 ` Gordan Bobic
2013-10-27 19:31 ` Gordan Bobic
1 sibling, 2 replies; 20+ messages in thread
From: John Wargo @ 2013-10-27 16:21 UTC (permalink / raw)
To: Gordan Bobic, xen-devel@lists.xen.org
[-- Attachment #1: Type: text/plain, Size: 3447 bytes --]
On 10/27/2013 09:27 AM, John Wargo wrote:
> On 10/27/2013 04:30 AM, Gordan Bobic wrote:
>> On 10/26/2013 09:58 PM, John Wargo wrote:
>>> Geniuses,
>>>
>>> I've been trying to get VGA pass-through working on Windows 8, however
>>> I've been running into a few issues.
>>> Currently I can get Windows 8 running flawlessly without VGA
>>> pass-through, however I'm planning on using it for gaming, so this wont
>>> work.
>>>
>>> When I start windows 8, I am able to get past the install portion of
>>> the
>>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>>
>>> Hardware Information :
>>> AMD Fx6300
>>> ASUS M5a99x evo r2.0
>>> 16GB RAM
>>> 6670 Radeon HD - Dom0
>>> 7850 Radeon HD - Win8
>>
>> I have recently (recently as in over the past 48 hours) re-tried to
>> get ATI VGA passthrough working, and the results are... interesting.
>>
>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
>> ever seems to work (slowdown + white lines when dragging windows
>> after a domU reboot). I am using XP64 domU so I can't eject the GPU
>> (it says it is being used). But shutting down the domU, doing echo 1
>> > reset for the GPU from dom0 (I don't know how this is implemented
>> and whether it does anything) and then starting it up again sometimes
>> recovers it. GPU-Z runs and reports the GPU correctly.
>>
>> HD4850 dom0 + HD7970 domU results in the entire host locking up as
>> soon as the driver is loaded in domU. My solution is to swap the dom0
>> GPU for an 8800GT, and the problem now doesn't occur. If I had to
>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on
>> the bus, tries to do something to it, and ends up crashing the host.
>> This could also be exacerbated by the fact that I have to run with
>> relaxed checking and no PCI ACS due to NF200 bridges on my
>> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
>> _hard_ (but not the host, thankfully). It crashes it so hard, that
>> the only cure is to reboot the host. Reseting the GPU via /sys/
>> doesn't seem to do anything to help.
>>
>> Are you using gfx_passthru=1 in your config? The way most people have
>> this kind of thing working is with gfx_passthru=0, i.e. secondary
>> passthru. Don't assign the PCI device in the config when installing.
>> Once the domU install is complete, shut it down, and add the GPU you
>> want to pass through. Then fire up domU in VNC, install the driver,
>> and with a bit of luck it will come up with output on the external
>> monitor.
>>
>> Also make sure that radeon or radeonfb kernel drivers DO NOT load
>> before the device is assigned to xen-pciback. The exact way to ensure
>> this will depend on what distro and dom0 kernel you are using.
>>
>> Gordan
> Status update:
>
> The catalyst drivers appear to be working perfectly fine, device
> manager shows no errors, and everything works great, except that when
> I plug my monitor into the second card, I get "No Signal" on the
> monitor, then it shuts off.
>
> I though that secondary passthrough meant that it would pass the
> virtual adapter in as primary, but I could use my GPU that I passed
> through, so where am I wrong, and how do I do that?
>
> -John
I've been doing some research into my VGA passthrough, so I've gone
through the various debugging steps, and the only thing that I've found
out of place is with "xl dmesg" (attached).
Where do I go from here?
-John
[-- Attachment #2: debug.txt --]
[-- Type: text/plain, Size: 65536 bytes --]
main = 1, device id = 0x200, fault address = 0xf47fef3c00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3c40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3c80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3cc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xffffffffc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xffffffff80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffe00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xffffffff00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffe80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffdc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffec0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffe40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xffffffff40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf40f577480, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3d80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3e40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3e00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3dc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3d00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3d40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3f00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3ec0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3e80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3f40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3f80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef3fc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4000, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4780, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef42c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4280, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4340, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4080, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4040, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4300, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef43c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4700, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef40c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4380, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4640, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4140, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4180, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4400, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4680, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4500, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4240, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef41c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef44c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4580, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4540, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4200, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef45c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4600, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef46c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4440, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4100, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4480, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4740, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef47c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4840, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4800, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4880, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4940, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef48c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4980, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4900, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4ac0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef49c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4a40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4a00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4a80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4b00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4b40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4b80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4bc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4c00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4c40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4c80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4d00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4cc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4d80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4d40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4dc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4e00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4e40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4e80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4ec0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4f40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4f00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5000, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4f80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef4fc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff000, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5080, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5040, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff300, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff240, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff580, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff640, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff0c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff2c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff5c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff080, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff180, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff340, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff400, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff440, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff480, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff100, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff500, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff4c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff600, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff140, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff040, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff540, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff680, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff380, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff700, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff3c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff200, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff6c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff280, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff1c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff7c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff780, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff740, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff800, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff840, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff880, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff900, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff8c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff940, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff980, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffa00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff9c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffa40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffa80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffb00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffac0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffb40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffb80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffc00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffbc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffc40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffc80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffd00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffcc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffd40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffd80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffe00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffdc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffe40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffe80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xffffffff00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffec0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xffffffff80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xffffffff40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xffffffffc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff000, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff040, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff080, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff0c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff100, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff140, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff180, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff1c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff200, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff240, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff280, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff2c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff300, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff340, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff380, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff3c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff400, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff440, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff480, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff4c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff500, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff540, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff580, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff5c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff600, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff640, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff680, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff6c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff700, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff740, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff780, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff7c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff800, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff840, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff880, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff8c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff900, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff940, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff980, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffff9c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef50c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffa00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffa40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffa80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffac0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffb00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffb40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffb80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffbc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffc00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffc40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffc80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffcc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffd00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffd40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffd80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffdc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffe00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffe40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5380, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef53c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5100, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5200, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5140, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5280, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5180, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef52c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef51c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5340, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5240, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xf47fef5300, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 1, device id = 0x200, fault address = 0xfffffffe80, flags = 0
(XEN) AMD-Vi: Disable: device id = 0x200, domain = 1, paging mode = 4
(XEN) AMD-Vi: Setup I/O page table: device id = 0x200, type = 0x1, root table = 0x440a99000, domain = 0, paging mode = 3
(XEN) AMD-Vi: Re-assign 0000:02:00.0 from dom1 to dom0
(XEN) AMD-Vi: Disable: device id = 0x201, domain = 1, paging mode = 4
(XEN) AMD-Vi: Setup I/O page table: device id = 0x201, type = 0x1, root table = 0x440a99000, domain = 0, paging mode = 3
(XEN) AMD-Vi: Re-assign 0000:02:00.1 from dom1 to dom0
(XEN) AMD-Vi: Share p2m table with iommu: p2m table = 0x419872
(XEN) memory.c:132:d0 Could not allocate order=18 extent: id=2 memflags=0 (0 of 1)
(XEN) io.c:280: d2: bind: m_gsi=87 g_gsi=32 device=4 intx=0
(XEN) AMD-Vi: Disable: device id = 0x200, domain = 0, paging mode = 3
(XEN) AMD-Vi: Setup I/O page table: device id = 0x200, type = 0x1, root table = 0x419872000, domain = 2, paging mode = 4
(XEN) AMD-Vi: Re-assign 0000:02:00.0 from dom0 to dom2
(XEN) io.c:280: d2: bind: m_gsi=86 g_gsi=37 device=5 intx=1
(XEN) AMD-Vi: Disable: device id = 0x201, domain = 0, paging mode = 3
(XEN) AMD-Vi: Setup I/O page table: device id = 0x201, type = 0x1, root table = 0x419872000, domain = 2, paging mode = 4
(XEN) AMD-Vi: Re-assign 0000:02:00.1 from dom0 to dom2
(d2) HVM Loader
(d2) Detected Xen v4.4-unstable
(d2) Xenbus rings @0xfeffc000, event channel 6
(d2) System requested ROMBIOS
(d2) CPU speed is 4616 MHz
(d2) Relocating guest memory for lowmem MMIO space enabled
(XEN) irq.c:270: Dom2 PCI link 0 changed 0 -> 5
(d2) PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom2 PCI link 1 changed 0 -> 10
(d2) PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom2 PCI link 2 changed 0 -> 11
(d2) PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom2 PCI link 3 changed 0 -> 5
(d2) PCI-ISA link 3 routed to IRQ5
(d2) pci dev 01:2 INTD->IRQ5
(d2) pci dev 01:3 INTA->IRQ10
(d2) pci dev 03:0 INTA->IRQ5
(d2) pci dev 04:0 INTA->IRQ5
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 2, device id = 0x200, fault address = 0xf40f577180, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 2, device id = 0x200, fault address = 0xfffffff000, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 2, device id = 0x200, fault address = 0xfffffff080, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 2, device id = 0x200, fault address = 0xfffffff040, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 2, device id = 0x200, fault address = 0xfffffff0c0, flags = 0
(d2) pci dev 05:0 INTB->IRQ11
(d2) Relocating 0xffff pages from 0e0001000 to 20f800000 for lowmem MMIO hole
(d2) Relocating 0x1 pages from 0e0000000 to 21f7ff000 for lowmem MMIO hole
(d2) RAM in high memory; setting high_mem resource base to 21f800000
(d2) pci dev 04:0 bar 10 size 010000000: 0e000000c
(XEN) memory_map:add: dom2 gfn=e0000 mfn=b0000 nr=10000
(d2) pci dev 02:0 bar 10 size 002000000: 0f0000008
(d2) pci dev 03:0 bar 14 size 001000000: 0f2000008
(XEN) memory_map:add: dom2 gfn=f3000 mfn=fe900 nr=40
(d2) pci dev 04:0 bar 18 size 000040000: 0f3000004
(d2) pci dev 04:0 bar 30 size 000020000: 0f3040000
(d2) pci dev 05:0 bar 10 size 000004000: 0f3060004
(XEN) memory_map:add: dom2 gfn=f3060 mfn=fe960 nr=4
(d2) pci dev 02:0 bar 14 size 000001000: 0f3064000
(d2) pci dev 03:0 bar 10 size 000000100: 00000c001
(d2) pci dev 04:0 bar 20 size 000000100: 00000c101
(XEN) ioport_map:add: dom2 gport=c100 mport=d000 nr=100
(d2) pci dev 01:2 bar 20 size 000000020: 00000c201
(d2) pci dev 01:1 bar 20 size 000000010: 00000c221
(d2) Multiprocessor initialisation:
(d2) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [3/8] ... done.
(d2) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [3/8] ... done.
(d2) - CPU2 ... 48-bit phys ... fixed MTRRs ... var MTRRs [3/8] ... done.
(d2) - CPU3 ... 48-bit phys ... fixed MTRRs ... var MTRRs [3/8] ... done.
(d2) Testing HVM environment:
(d2) - REP INSB across page boundaries ... passed
(d2) - GS base MSRs and SWAPGS ... passed
(d2) Passed 2 of 2 tests
(d2) Writing SMBIOS tables ...
(d2) Loading ROMBIOS ...
(d2) 12124 bytes of ROMBIOS high-memory extensions:
(d2) Relocating to 0xfc001000-0xfc003f5c ... done
(d2) Creating MP tables ...
(d2) Loading Cirrus VGABIOS ...
(d2) Option ROMs:
(d2) c0000-c8fff: VGA BIOS
(d2) Loading ACPI ...
(d2) vm86 TSS at fc010080
(d2) BIOS map:
(d2) f0000-fffff: Main BIOS
(d2) E820 table:
(d2) [00]: 00000000:00000000 - 00000000:0009e000: RAM
(d2) [01]: 00000000:0009e000 - 00000000:000a0000: RESERVED
(d2) HOLE: 00000000:000a0000 - 00000000:000e0000
(d2) [02]: 00000000:000e0000 - 00000000:00100000: RESERVED
(d2) [03]: 00000000:00100000 - 00000000:e0000000: RAM
(d2) HOLE: 00000000:e0000000 - 00000000:fc000000
(d2) [04]: 00000000:fc000000 - 00000001:00000000: RESERVED
(d2) [05]: 00000001:00000000 - 00000002:1f800000: RAM
(d2) Invoking ROMBIOS ...
(XEN) stdvga.c:147:d2 entering stdvga and caching modes
(d2) VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $
(d2) Bochs BIOS - build: 06/23/99
(d2) $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(d2) Options: apmbios pcibios eltorito PMM
(d2)
(d2) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk ( 390 GBytes)
(d2) ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
(d2)
(d2)
(d2)
(d2) Press F12 for boot menu.
(d2)
(d2) Booting from CD-Rom...
(d2) 3415MB medium detected
(XEN) stdvga.c:151:d2 leaving stdvga
(XEN) irq.c:270: Dom2 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom2 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom2 PCI link 3 changed 5 -> 0
(XEN) irq.c:270: Dom2 PCI link 1 changed 10 -> 0
(XEN) memory_map:remove: dom2 gfn=e0000 mfn=b0000 nr=10000
(XEN) memory_map:remove: dom2 gfn=f3000 mfn=fe900 nr=40
(XEN) ioport_map:remove: dom2 gport=c100 mport=d000 nr=100
(XEN) memory_map:add: dom2 gfn=e0000 mfn=b0000 nr=10000
(XEN) memory_map:add: dom2 gfn=f3000 mfn=fe900 nr=40
(XEN) ioport_map:add: dom2 gport=c100 mport=d000 nr=100
(XEN) memory_map:remove: dom2 gfn=f3060 mfn=fe960 nr=4
(XEN) memory_map:add: dom2 gfn=f3060 mfn=fe960 nr=4
(XEN) memory_map:remove: dom2 gfn=f3060 mfn=fe960 nr=4
(XEN) memory_map:add: dom2 gfn=f3060 mfn=fe960 nr=4
(XEN) memory_map:remove: dom2 gfn=f3060 mfn=fe960 nr=4
(XEN) AMD-Vi: Disable: device id = 0x200, domain = 2, paging mode = 4
(XEN) AMD-Vi: Setup I/O page table: device id = 0x200, type = 0x1, root table = 0x440a99000, domain = 0, paging mode = 3
(XEN) AMD-Vi: Re-assign 0000:02:00.0 from dom2 to dom0
(XEN) AMD-Vi: Disable: device id = 0x201, domain = 2, paging mode = 4
(XEN) AMD-Vi: Setup I/O page table: device id = 0x201, type = 0x1, root table = 0x440a99000, domain = 0, paging mode = 3
(XEN) AMD-Vi: Re-assign 0000:02:00.1 from dom2 to dom0
(XEN) AMD-Vi: Share p2m table with iommu: p2m table = 0x419809
(XEN) memory.c:132:d0 Could not allocate order=18 extent: id=3 memflags=0 (0 of 1)
(XEN) io.c:280: d3: bind: m_gsi=87 g_gsi=32 device=4 intx=0
(XEN) AMD-Vi: Disable: device id = 0x200, domain = 0, paging mode = 3
(XEN) AMD-Vi: Setup I/O page table: device id = 0x200, type = 0x1, root table = 0x419809000, domain = 3, paging mode = 4
(XEN) AMD-Vi: Re-assign 0000:02:00.0 from dom0 to dom3
(XEN) io.c:280: d3: bind: m_gsi=86 g_gsi=37 device=5 intx=1
(XEN) AMD-Vi: Disable: device id = 0x201, domain = 0, paging mode = 3
(XEN) AMD-Vi: Setup I/O page table: device id = 0x201, type = 0x1, root table = 0x419809000, domain = 3, paging mode = 4
(XEN) AMD-Vi: Re-assign 0000:02:00.1 from dom0 to dom3
(d3) HVM Loader
(d3) Detected Xen v4.4-unstable
(d3) Xenbus rings @0xfeffc000, event channel 6
(d3) System requested ROMBIOS
(d3) CPU speed is 4616 MHz
(d3) Relocating guest memory for lowmem MMIO space enabled
(XEN) irq.c:270: Dom3 PCI link 0 changed 0 -> 5
(d3) PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom3 PCI link 1 changed 0 -> 10
(d3) PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom3 PCI link 2 changed 0 -> 11
(d3) PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom3 PCI link 3 changed 0 -> 5
(d3) PCI-ISA link 3 routed to IRQ5
(d3) pci dev 01:2 INTD->IRQ5
(d3) pci dev 01:3 INTA->IRQ10
(d3) pci dev 03:0 INTA->IRQ5
(d3) pci dev 04:0 INTA->IRQ5
(d3) pci dev 05:0 INTB->IRQ11
(d3) Relocating 0xffff pages from 0e0001000 to 20f800000 for lowmem MMIO hole
(d3) Relocating 0x1 pages from 0e0000000 to 21f7ff000 for lowmem MMIO hole
(d3) RAM in high memory; setting high_mem resource base to 21f800000
(d3) pci dev 04:0 bar 10 size 010000000: 0e000000c
(XEN) memory_map:add: dom3 gfn=e0000 mfn=b0000 nr=10000
(d3) pci dev 02:0 bar 10 size 002000000: 0f0000008
(d3) pci dev 03:0 bar 14 size 001000000: 0f2000008
(XEN) memory_map:add: dom3 gfn=f3000 mfn=fe900 nr=40
(d3) pci dev 04:0 bar 18 size 000040000: 0f3000004
(d3) pci dev 04:0 bar 30 size 000020000: 0f3040000
(d3) pci dev 05:0 bar 10 size 000004000: 0f3060004
(XEN) memory_map:add: dom3 gfn=f3060 mfn=fe960 nr=4
(d3) pci dev 02:0 bar 14 size 000001000: 0f3064000
(d3) pci dev 03:0 bar 10 size 000000100: 00000c001
(d3) pci dev 04:0 bar 20 size 000000100: 00000c101
(XEN) ioport_map:add: dom3 gport=c100 mport=d000 nr=100
(d3) pci dev 01:2 bar 20 size 000000020: 00000c201
(d3) pci dev 01:1 bar 20 size 000000010: 00000c221
(d3) Multiprocessor initialisation:
(d3) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [3/8] ... done.
(d3) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [3/8] ... done.
(d3) - CPU2 ... 48-bit phys ... fixed MTRRs ... var MTRRs [3/8] ... done.
(d3) - CPU3 ... 48-bit phys ... fixed MTRRs ... var MTRRs [3/8] ... done.
(d3) Testing HVM environment:
(d3) - REP INSB across page boundaries ... passed
(d3) - GS base MSRs and SWAPGS ... passed
(d3) Passed 2 of 2 tests
(d3) Writing SMBIOS tables ...
(d3) Loading ROMBIOS ...
(d3) 12124 bytes of ROMBIOS high-memory extensions:
(d3) Relocating to 0xfc001000-0xfc003f5c ... done
(d3) Creating MP tables ...
(d3) Loading Cirrus VGABIOS ...
(d3) Option ROMs:
(d3) c0000-c8fff: VGA BIOS
(d3) Loading ACPI ...
(d3) vm86 TSS at fc010080
(d3) BIOS map:
(d3) f0000-fffff: Main BIOS
(d3) E820 table:
(d3) [00]: 00000000:00000000 - 00000000:0009e000: RAM
(d3) [01]: 00000000:0009e000 - 00000000:000a0000: RESERVED
(d3) HOLE: 00000000:000a0000 - 00000000:000e0000
(d3) [02]: 00000000:000e0000 - 00000000:00100000: RESERVED
(d3) [03]: 00000000:00100000 - 00000000:e0000000: RAM
(d3) HOLE: 00000000:e0000000 - 00000000:fc000000
(d3) [04]: 00000000:fc000000 - 00000001:00000000: RESERVED
(d3) [05]: 00000001:00000000 - 00000002:1f800000: RAM
(d3) Invoking ROMBIOS ...
(XEN) stdvga.c:147:d3 entering stdvga and caching modes
(d3) VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $
(d3) Bochs BIOS - build: 06/23/99
(d3) $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(d3) Options: apmbios pcibios eltorito PMM
(d3)
(d3) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk ( 390 GBytes)
(d3) ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
(d3)
(d3)
(d3)
(d3) Press F12 for boot menu.
(d3)
(d3) Booting from CD-Rom...
(d3) 3415MB medium detected
(XEN) stdvga.c:151:d3 leaving stdvga
(XEN) irq.c:270: Dom3 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom3 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom3 PCI link 3 changed 5 -> 0
(XEN) irq.c:270: Dom3 PCI link 0 changed 5 -> 0
(XEN) memory_map:remove: dom3 gfn=e0000 mfn=b0000 nr=10000
(XEN) memory_map:remove: dom3 gfn=f3000 mfn=fe900 nr=40
(XEN) ioport_map:remove: dom3 gport=c100 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=e0000 mfn=b0000 nr=10000
(XEN) memory_map:add: dom3 gfn=f3000 mfn=fe900 nr=40
(XEN) ioport_map:add: dom3 gport=c100 mport=d000 nr=100
(XEN) memory_map:remove: dom3 gfn=f3060 mfn=fe960 nr=4
(XEN) memory_map:add: dom3 gfn=f3060 mfn=fe960 nr=4
(XEN) memory_map:remove: dom3 gfn=f3060 mfn=fe960 nr=4
(XEN) memory_map:add: dom3 gfn=f3060 mfn=fe960 nr=4
(XEN) memory_map:remove: dom3 gfn=e0000 mfn=b0000 nr=10000
(XEN) memory_map:remove: dom3 gfn=f3000 mfn=fe900 nr=40
(XEN) ioport_map:remove: dom3 gport=c100 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=e0000 mfn=b0000 nr=10000
(XEN) memory_map:add: dom3 gfn=f3000 mfn=fe900 nr=40
(XEN) ioport_map:add: dom3 gport=c100 mport=d000 nr=100
(XEN) io.c:305: d3: unbind: m_gsi=87 g_gsi=32 device=4 intx=0
(XEN) io.c:363: d3 unmap: m_irq=87 device=4 intx=0
(XEN) io.c:280: d3: bind: m_gsi=28 g_gsi=16 device=0 intx=0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf40f577440, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff000, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff580, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff4c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff3c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff080, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff600, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff100, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff180, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff500, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff1c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff140, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff240, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff200, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff400, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff280, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff540, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff440, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff2c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff640, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff480, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff680, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff5c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff300, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff040, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff340, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff0c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff380, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff6c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef30c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff780, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff740, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff7c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff700, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef30d0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3100, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3140, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3180, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef31a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef31b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef30e0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef30d0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef31b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff800, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef33b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3200, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef31c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3280, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3240, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef32b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef32a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef32c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef32b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3340, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3300, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef33a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3380, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef33c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef33b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff840, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffb00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff8c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffb80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff900, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffa00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff940, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffa40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff9c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff880, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffac0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffa80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffb40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff980, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffbc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3440, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3400, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3480, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef34a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef34b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef34c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef34b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3500, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3580, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3540, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef35a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef35b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef35b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef35c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffc40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffc00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffc80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffcc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffd40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffd00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffd80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffdc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef36c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef36b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3740, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3700, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3640, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3600, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3680, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef36a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef36b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef37a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3780, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef37b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef37b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef37c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3800, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3840, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef38a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3880, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef38b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffe00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffe40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffe80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffec0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xffffffff00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xffffffff40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef38b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef38c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3900, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3980, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3940, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef39a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef39b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef39b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3a00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef39c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3a80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3a40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3aa0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3ab0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3ab0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3ac0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3b00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3b40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3ba0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3b80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3bb0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3bb0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff000, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xffffffff80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff040, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xffffffffc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff080, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff0c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3bc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3c00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3c80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3ca0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3c40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3cb0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3cb0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3cc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3d00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3d40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3da0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3d80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3db0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3dc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3db0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff300, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff340, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff380, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff100, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff1c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff180, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff240, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff200, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff140, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff2c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff280, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3e00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3e40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3e80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3eb0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3eb0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3ea0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3ec0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3f00, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3f40, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3fa0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3f80, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff480, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff400, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff3c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff440, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff4c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff5c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff500, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff540, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff580, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff600, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff640, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff680, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff6c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4000, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3fb0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3fb0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef3fc0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff7c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff740, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff700, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff780, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff840, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff800, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff8c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff880, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef41b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4180, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4200, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef41c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4140, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4100, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef40c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4080, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4040, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef40b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef41a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4240, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef40a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef41b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef40b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff940, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff900, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff980, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4280, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef42b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef42a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef42c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef42b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4300, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4340, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef43a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4380, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef43b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef43b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffa00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffff9c0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffa80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffac0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffa40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef44a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef45a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef44b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4400, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4500, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4480, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4440, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef44b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4580, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef44c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef43c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4540, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef45b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef45b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef45c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4600, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4640, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4680, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef46a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef46b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef46b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffb00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffc40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffb40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffb80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffc00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffbc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffc80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffcc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef46c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4700, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4740, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef47b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef47b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef47a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4780, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef47c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4840, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4800, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef48a0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef4880, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef48b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef48b0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xf47fef48c0, flags = 0x20
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffdc0, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffd80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffe40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffe00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffd40, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffe80, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffd00, flags = 0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 3, device id = 0x200, fault address = 0xfffffffec0, flags = 0
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 16:21 ` John Wargo
@ 2013-10-27 17:21 ` John Wargo
2013-10-28 17:07 ` Konrad Rzeszutek Wilk
2013-10-28 19:30 ` Zytaruk, Kelly
2013-10-27 19:35 ` Gordan Bobic
1 sibling, 2 replies; 20+ messages in thread
From: John Wargo @ 2013-10-27 17:21 UTC (permalink / raw)
To: Gordan Bobic, xen-devel@lists.xen.org
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
I've made quite a bit of changes since my last email, and so far here's
what I've got:
AMD FX6300
ASUS M5A99X evo r2.0
ASUS Radeon 6670 (Dom0)
XFX Radeon 7850 (Win8)
Right now I've got AMD Catalyst (latest stable) installed in windows 8,
and device manager shows my Radeon 7850 reporting no issues.
I'm currently passing it through as secondary (gfx_passthrough=0),
however I cannot plug my monitor into it.
After taking debugging steps, I've come up with the attached debugging info:
info - xl info
dmesg - xl dmesg
grub - a copy of '/etc/default/grub'
win8.cfg - the configuration I'm using to launch windows 8
Fedora bug reporting tool caught a kernel bug at
'drivers/gpu/drm/ttm/ttm_bo.c:210', I have compiled xen from source, and
I'm using it as a kernel (or really part of it).
Is there some sort of AMD Radeon patch I need to use (I saw one on the
wiki, but it appeared to be several years old), or is it a needed
configuration?
Thanks for your time,
-John
[-- Attachment #2: debug.zip --]
[-- Type: application/zip, Size: 162 bytes --]
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
[not found] ` <526D1FBA.10708@gmail.com>
@ 2013-10-27 19:28 ` Gordan Bobic
0 siblings, 0 replies; 20+ messages in thread
From: Gordan Bobic @ 2013-10-27 19:28 UTC (permalink / raw)
To: John Wargo, xen-devel@lists.xen.org
On 10/27/2013 02:14 PM, John Wargo wrote:
> On 10/27/2013 04:30 AM, Gordan Bobic wrote:
>> On 10/26/2013 09:58 PM, John Wargo wrote:
>>> Geniuses,
>>>
>>> I've been trying to get VGA pass-through working on Windows 8, however
>>> I've been running into a few issues.
>>> Currently I can get Windows 8 running flawlessly without VGA
>>> pass-through, however I'm planning on using it for gaming, so this wont
>>> work.
>>>
>>> When I start windows 8, I am able to get past the install portion of the
>>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>>
>>> Hardware Information :
>>> AMD Fx6300
>>> ASUS M5a99x evo r2.0
>>> 16GB RAM
>>> 6670 Radeon HD - Dom0
>>> 7850 Radeon HD - Win8
>>
>> I have recently (recently as in over the past 48 hours) re-tried to
>> get ATI VGA passthrough working, and the results are... interesting.
>>
>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
>> ever seems to work (slowdown + white lines when dragging windows after
>> a domU reboot). I am using XP64 domU so I can't eject the GPU (it says
>> it is being used). But shutting down the domU, doing echo 1 > reset
>> for the GPU from dom0 (I don't know how this is implemented and
>> whether it does anything) and then starting it up again sometimes
>> recovers it. GPU-Z runs and reports the GPU correctly.
>>
>> HD4850 dom0 + HD7970 domU results in the entire host locking up as
>> soon as the driver is loaded in domU. My solution is to swap the dom0
>> GPU for an 8800GT, and the problem now doesn't occur. If I had to
>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on
>> the bus, tries to do something to it, and ends up crashing the host.
>> This could also be exacerbated by the fact that I have to run with
>> relaxed checking and no PCI ACS due to NF200 bridges on my
>> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
>> _hard_ (but not the host, thankfully). It crashes it so hard, that the
>> only cure is to reboot the host. Reseting the GPU via /sys/ doesn't
>> seem to do anything to help.
>>
>> Are you using gfx_passthru=1 in your config? The way most people have
>> this kind of thing working is with gfx_passthru=0, i.e. secondary
>> passthru. Don't assign the PCI device in the config when installing.
>> Once the domU install is complete, shut it down, and add the GPU you
>> want to pass through. Then fire up domU in VNC, install the driver,
>> and with a bit of luck it will come up with output on the external
>> monitor.
>>
>> Also make sure that radeon or radeonfb kernel drivers DO NOT load
>> before the device is assigned to xen-pciback. The exact way to ensure
>> this will depend on what distro and dom0 kernel you are using.
>>
>> Gordan
>
> After messing with a few of the options, and a bit of trickery, It
> appears that I've got it passed-through, however when viewing it in the
> device manager I get Error Code 43 : Not enough system resources. I'm
> currently working on installing the latest stable drivers from AMD on
> hopes that it will fix it, however I don't see it making a ton of
> difference.
>
> Is there some sort of patch I need to apply, or something I'm missing?
Are you using traditional or upstream qemu?
Gordan
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 14:27 ` John Wargo
2013-10-27 16:21 ` John Wargo
@ 2013-10-27 19:31 ` Gordan Bobic
1 sibling, 0 replies; 20+ messages in thread
From: Gordan Bobic @ 2013-10-27 19:31 UTC (permalink / raw)
To: John Wargo; +Cc: xen-devel@lists.xen.org
On 10/27/2013 02:27 PM, John Wargo wrote:
> On 10/27/2013 04:30 AM, Gordan Bobic wrote:
>> On 10/26/2013 09:58 PM, John Wargo wrote:
>>> Geniuses,
>>>
>>> I've been trying to get VGA pass-through working on Windows 8, however
>>> I've been running into a few issues.
>>> Currently I can get Windows 8 running flawlessly without VGA
>>> pass-through, however I'm planning on using it for gaming, so this wont
>>> work.
>>>
>>> When I start windows 8, I am able to get past the install portion of the
>>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>>
>>> Hardware Information :
>>> AMD Fx6300
>>> ASUS M5a99x evo r2.0
>>> 16GB RAM
>>> 6670 Radeon HD - Dom0
>>> 7850 Radeon HD - Win8
>>
>> I have recently (recently as in over the past 48 hours) re-tried to
>> get ATI VGA passthrough working, and the results are... interesting.
>>
>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
>> ever seems to work (slowdown + white lines when dragging windows after
>> a domU reboot). I am using XP64 domU so I can't eject the GPU (it says
>> it is being used). But shutting down the domU, doing echo 1 > reset
>> for the GPU from dom0 (I don't know how this is implemented and
>> whether it does anything) and then starting it up again sometimes
>> recovers it. GPU-Z runs and reports the GPU correctly.
>>
>> HD4850 dom0 + HD7970 domU results in the entire host locking up as
>> soon as the driver is loaded in domU. My solution is to swap the dom0
>> GPU for an 8800GT, and the problem now doesn't occur. If I had to
>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on
>> the bus, tries to do something to it, and ends up crashing the host.
>> This could also be exacerbated by the fact that I have to run with
>> relaxed checking and no PCI ACS due to NF200 bridges on my
>> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
>> _hard_ (but not the host, thankfully). It crashes it so hard, that the
>> only cure is to reboot the host. Reseting the GPU via /sys/ doesn't
>> seem to do anything to help.
>>
>> Are you using gfx_passthru=1 in your config? The way most people have
>> this kind of thing working is with gfx_passthru=0, i.e. secondary
>> passthru. Don't assign the PCI device in the config when installing.
>> Once the domU install is complete, shut it down, and add the GPU you
>> want to pass through. Then fire up domU in VNC, install the driver,
>> and with a bit of luck it will come up with output on the external
>> monitor.
>>
>> Also make sure that radeon or radeonfb kernel drivers DO NOT load
>> before the device is assigned to xen-pciback. The exact way to ensure
>> this will depend on what distro and dom0 kernel you are using.
>>
>> Gordan
> Status update:
>
> The catalyst drivers appear to be working perfectly fine, device manager
> shows no errors, and everything works great, except that when I plug my
> monitor into the second card, I get "No Signal" on the monitor, then it
> shuts off.
>
> I though that secondary passthrough meant that it would pass the virtual
> adapter in as primary, but I could use my GPU that I passed through, so
> where am I wrong, and how do I do that?
Your understanding is correct - real VGA card will be passed as
secondary, and the driver, when it loads, should start it up, and this
normally takes over from the primary.
Two things come to mind:
1) I find that sometimes I have to disable the primary emulated VGA adapter.
2) Make sure your desktop settings are correctly set up to use the real
VGA card as the primary desktop.
Gordan
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 16:21 ` John Wargo
2013-10-27 17:21 ` John Wargo
@ 2013-10-27 19:35 ` Gordan Bobic
2013-10-27 19:45 ` John Wargo
` (2 more replies)
1 sibling, 3 replies; 20+ messages in thread
From: Gordan Bobic @ 2013-10-27 19:35 UTC (permalink / raw)
To: John Wargo, xen-devel@lists.xen.org
On 10/27/2013 04:21 PM, John Wargo wrote:
> On 10/27/2013 09:27 AM, John Wargo wrote:
>> On 10/27/2013 04:30 AM, Gordan Bobic wrote:
>>> On 10/26/2013 09:58 PM, John Wargo wrote:
>>>> Geniuses,
>>>>
>>>> I've been trying to get VGA pass-through working on Windows 8, however
>>>> I've been running into a few issues.
>>>> Currently I can get Windows 8 running flawlessly without VGA
>>>> pass-through, however I'm planning on using it for gaming, so this wont
>>>> work.
>>>>
>>>> When I start windows 8, I am able to get past the install portion of
>>>> the
>>>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>>>
>>>> Hardware Information :
>>>> AMD Fx6300
>>>> ASUS M5a99x evo r2.0
>>>> 16GB RAM
>>>> 6670 Radeon HD - Dom0
>>>> 7850 Radeon HD - Win8
>>>
>>> I have recently (recently as in over the past 48 hours) re-tried to
>>> get ATI VGA passthrough working, and the results are... interesting.
>>>
>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
>>> ever seems to work (slowdown + white lines when dragging windows
>>> after a domU reboot). I am using XP64 domU so I can't eject the GPU
>>> (it says it is being used). But shutting down the domU, doing echo 1
>>> > reset for the GPU from dom0 (I don't know how this is implemented
>>> and whether it does anything) and then starting it up again sometimes
>>> recovers it. GPU-Z runs and reports the GPU correctly.
>>>
>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as
>>> soon as the driver is loaded in domU. My solution is to swap the dom0
>>> GPU for an 8800GT, and the problem now doesn't occur. If I had to
>>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on
>>> the bus, tries to do something to it, and ends up crashing the host.
>>> This could also be exacerbated by the fact that I have to run with
>>> relaxed checking and no PCI ACS due to NF200 bridges on my
>>> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
>>> _hard_ (but not the host, thankfully). It crashes it so hard, that
>>> the only cure is to reboot the host. Reseting the GPU via /sys/
>>> doesn't seem to do anything to help.
>>>
>>> Are you using gfx_passthru=1 in your config? The way most people have
>>> this kind of thing working is with gfx_passthru=0, i.e. secondary
>>> passthru. Don't assign the PCI device in the config when installing.
>>> Once the domU install is complete, shut it down, and add the GPU you
>>> want to pass through. Then fire up domU in VNC, install the driver,
>>> and with a bit of luck it will come up with output on the external
>>> monitor.
>>>
>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load
>>> before the device is assigned to xen-pciback. The exact way to ensure
>>> this will depend on what distro and dom0 kernel you are using.
>>>
>>> Gordan
>> Status update:
>>
>> The catalyst drivers appear to be working perfectly fine, device
>> manager shows no errors, and everything works great, except that when
>> I plug my monitor into the second card, I get "No Signal" on the
>> monitor, then it shuts off.
>>
>> I though that secondary passthrough meant that it would pass the
>> virtual adapter in as primary, but I could use my GPU that I passed
>> through, so where am I wrong, and how do I do that?
>>
>> -John
> I've been doing some research into my VGA passthrough, so I've gone
> through the various debugging steps, and the only thing that I've found
> out of place is with "xl dmesg" (attached).
>
> Where do I go from here?
Sounds like your IOMMU may be buggy. You may need to set permissive=1 on
your xen-pciback module.
I cannot remember if xl uses the same configuration, but for xm you
could try putting this in your /etc/xen/xend-config.sxp:
(pci-passthrough-strict-check no)
(pci-dev-assign-strict-check no)
Gordan
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 19:35 ` Gordan Bobic
@ 2013-10-27 19:45 ` John Wargo
2013-10-27 20:05 ` John Wargo
2013-10-27 21:01 ` John Wargo
2 siblings, 0 replies; 20+ messages in thread
From: John Wargo @ 2013-10-27 19:45 UTC (permalink / raw)
To: Gordan Bobic, xen-devel@lists.xen.org
On 10/27/2013 02:35 PM, Gordan Bobic wrote:
> On 10/27/2013 04:21 PM, John Wargo wrote:
>> On 10/27/2013 09:27 AM, John Wargo wrote:
>>> On 10/27/2013 04:30 AM, Gordan Bobic wrote:
>>>> On 10/26/2013 09:58 PM, John Wargo wrote:
>>>>> Geniuses,
>>>>>
>>>>> I've been trying to get VGA pass-through working on Windows 8,
>>>>> however
>>>>> I've been running into a few issues.
>>>>> Currently I can get Windows 8 running flawlessly without VGA
>>>>> pass-through, however I'm planning on using it for gaming, so this
>>>>> wont
>>>>> work.
>>>>>
>>>>> When I start windows 8, I am able to get past the install portion of
>>>>> the
>>>>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>>>>
>>>>> Hardware Information :
>>>>> AMD Fx6300
>>>>> ASUS M5a99x evo r2.0
>>>>> 16GB RAM
>>>>> 6670 Radeon HD - Dom0
>>>>> 7850 Radeon HD - Win8
>>>>
>>>> I have recently (recently as in over the past 48 hours) re-tried to
>>>> get ATI VGA passthrough working, and the results are... interesting.
>>>>
>>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
>>>> ever seems to work (slowdown + white lines when dragging windows
>>>> after a domU reboot). I am using XP64 domU so I can't eject the GPU
>>>> (it says it is being used). But shutting down the domU, doing echo 1
>>>> > reset for the GPU from dom0 (I don't know how this is implemented
>>>> and whether it does anything) and then starting it up again sometimes
>>>> recovers it. GPU-Z runs and reports the GPU correctly.
>>>>
>>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as
>>>> soon as the driver is loaded in domU. My solution is to swap the dom0
>>>> GPU for an 8800GT, and the problem now doesn't occur. If I had to
>>>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on
>>>> the bus, tries to do something to it, and ends up crashing the host.
>>>> This could also be exacerbated by the fact that I have to run with
>>>> relaxed checking and no PCI ACS due to NF200 bridges on my
>>>> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
>>>> _hard_ (but not the host, thankfully). It crashes it so hard, that
>>>> the only cure is to reboot the host. Reseting the GPU via /sys/
>>>> doesn't seem to do anything to help.
>>>>
>>>> Are you using gfx_passthru=1 in your config? The way most people have
>>>> this kind of thing working is with gfx_passthru=0, i.e. secondary
>>>> passthru. Don't assign the PCI device in the config when installing.
>>>> Once the domU install is complete, shut it down, and add the GPU you
>>>> want to pass through. Then fire up domU in VNC, install the driver,
>>>> and with a bit of luck it will come up with output on the external
>>>> monitor.
>>>>
>>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load
>>>> before the device is assigned to xen-pciback. The exact way to ensure
>>>> this will depend on what distro and dom0 kernel you are using.
>>>>
>>>> Gordan
>>> Status update:
>>>
>>> The catalyst drivers appear to be working perfectly fine, device
>>> manager shows no errors, and everything works great, except that when
>>> I plug my monitor into the second card, I get "No Signal" on the
>>> monitor, then it shuts off.
>>>
>>> I though that secondary passthrough meant that it would pass the
>>> virtual adapter in as primary, but I could use my GPU that I passed
>>> through, so where am I wrong, and how do I do that?
>>>
>>> -John
>> I've been doing some research into my VGA passthrough, so I've gone
>> through the various debugging steps, and the only thing that I've found
>> out of place is with "xl dmesg" (attached).
>>
>> Where do I go from here?
>
> Sounds like your IOMMU may be buggy. You may need to set permissive=1
> on your xen-pciback module.
>
> I cannot remember if xl uses the same configuration, but for xm you
> could try putting this in your /etc/xen/xend-config.sxp:
> (pci-passthrough-strict-check no)
> (pci-dev-assign-strict-check no)
>
> Gordan
>
Gordan,
I have fough IOMMU in the past, so this sounds very likely, I'll try it.
For future reference, I'm fairly certain that in xl you specify
permissive in the cfg file:
pci = [x:x.x, permissive=1...]
-John
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 19:35 ` Gordan Bobic
2013-10-27 19:45 ` John Wargo
@ 2013-10-27 20:05 ` John Wargo
2013-10-27 21:01 ` John Wargo
2 siblings, 0 replies; 20+ messages in thread
From: John Wargo @ 2013-10-27 20:05 UTC (permalink / raw)
To: Gordan Bobic, xen-devel@lists.xen.org
On 10/27/2013 02:35 PM, Gordan Bobic wrote:
> On 10/27/2013 04:21 PM, John Wargo wrote:
>> On 10/27/2013 09:27 AM, John Wargo wrote:
>>> On 10/27/2013 04:30 AM, Gordan Bobic wrote:
>>>> On 10/26/2013 09:58 PM, John Wargo wrote:
>>>>> Geniuses,
>>>>>
>>>>> I've been trying to get VGA pass-through working on Windows 8,
>>>>> however
>>>>> I've been running into a few issues.
>>>>> Currently I can get Windows 8 running flawlessly without VGA
>>>>> pass-through, however I'm planning on using it for gaming, so this
>>>>> wont
>>>>> work.
>>>>>
>>>>> When I start windows 8, I am able to get past the install portion of
>>>>> the
>>>>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>>>>
>>>>> Hardware Information :
>>>>> AMD Fx6300
>>>>> ASUS M5a99x evo r2.0
>>>>> 16GB RAM
>>>>> 6670 Radeon HD - Dom0
>>>>> 7850 Radeon HD - Win8
>>>>
>>>> I have recently (recently as in over the past 48 hours) re-tried to
>>>> get ATI VGA passthrough working, and the results are... interesting.
>>>>
>>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
>>>> ever seems to work (slowdown + white lines when dragging windows
>>>> after a domU reboot). I am using XP64 domU so I can't eject the GPU
>>>> (it says it is being used). But shutting down the domU, doing echo 1
>>>> > reset for the GPU from dom0 (I don't know how this is implemented
>>>> and whether it does anything) and then starting it up again sometimes
>>>> recovers it. GPU-Z runs and reports the GPU correctly.
>>>>
>>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as
>>>> soon as the driver is loaded in domU. My solution is to swap the dom0
>>>> GPU for an 8800GT, and the problem now doesn't occur. If I had to
>>>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on
>>>> the bus, tries to do something to it, and ends up crashing the host.
>>>> This could also be exacerbated by the fact that I have to run with
>>>> relaxed checking and no PCI ACS due to NF200 bridges on my
>>>> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
>>>> _hard_ (but not the host, thankfully). It crashes it so hard, that
>>>> the only cure is to reboot the host. Reseting the GPU via /sys/
>>>> doesn't seem to do anything to help.
>>>>
>>>> Are you using gfx_passthru=1 in your config? The way most people have
>>>> this kind of thing working is with gfx_passthru=0, i.e. secondary
>>>> passthru. Don't assign the PCI device in the config when installing.
>>>> Once the domU install is complete, shut it down, and add the GPU you
>>>> want to pass through. Then fire up domU in VNC, install the driver,
>>>> and with a bit of luck it will come up with output on the external
>>>> monitor.
>>>>
>>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load
>>>> before the device is assigned to xen-pciback. The exact way to ensure
>>>> this will depend on what distro and dom0 kernel you are using.
>>>>
>>>> Gordan
>>> Status update:
>>>
>>> The catalyst drivers appear to be working perfectly fine, device
>>> manager shows no errors, and everything works great, except that when
>>> I plug my monitor into the second card, I get "No Signal" on the
>>> monitor, then it shuts off.
>>>
>>> I though that secondary passthrough meant that it would pass the
>>> virtual adapter in as primary, but I could use my GPU that I passed
>>> through, so where am I wrong, and how do I do that?
>>>
>>> -John
>> I've been doing some research into my VGA passthrough, so I've gone
>> through the various debugging steps, and the only thing that I've found
>> out of place is with "xl dmesg" (attached).
>>
>> Where do I go from here?
>
> Sounds like your IOMMU may be buggy. You may need to set permissive=1
> on your xen-pciback module.
>
> I cannot remember if xl uses the same configuration, but for xm you
> could try putting this in your /etc/xen/xend-config.sxp:
> (pci-passthrough-strict-check no)
> (pci-dev-assign-strict-check no)
>
> Gordan
>
Gordan,
According to the xenbits page on xl.cfg, it appears the permissive will
only work with PV guests, not HVM..
-John
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 19:35 ` Gordan Bobic
2013-10-27 19:45 ` John Wargo
2013-10-27 20:05 ` John Wargo
@ 2013-10-27 21:01 ` John Wargo
2013-10-27 22:51 ` Gordan Bobic
2 siblings, 1 reply; 20+ messages in thread
From: John Wargo @ 2013-10-27 21:01 UTC (permalink / raw)
To: Gordan Bobic, xen-devel@lists.xen.org
On 10/27/2013 02:35 PM, Gordan Bobic wrote:
> On 10/27/2013 04:21 PM, John Wargo wrote:
>> On 10/27/2013 09:27 AM, John Wargo wrote:
>>> On 10/27/2013 04:30 AM, Gordan Bobic wrote:
>>>> On 10/26/2013 09:58 PM, John Wargo wrote:
>>>>> Geniuses,
>>>>>
>>>>> I've been trying to get VGA pass-through working on Windows 8,
>>>>> however
>>>>> I've been running into a few issues.
>>>>> Currently I can get Windows 8 running flawlessly without VGA
>>>>> pass-through, however I'm planning on using it for gaming, so this
>>>>> wont
>>>>> work.
>>>>>
>>>>> When I start windows 8, I am able to get past the install portion of
>>>>> the
>>>>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>>>>
>>>>> Hardware Information :
>>>>> AMD Fx6300
>>>>> ASUS M5a99x evo r2.0
>>>>> 16GB RAM
>>>>> 6670 Radeon HD - Dom0
>>>>> 7850 Radeon HD - Win8
>>>>
>>>> I have recently (recently as in over the past 48 hours) re-tried to
>>>> get ATI VGA passthrough working, and the results are... interesting.
>>>>
>>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
>>>> ever seems to work (slowdown + white lines when dragging windows
>>>> after a domU reboot). I am using XP64 domU so I can't eject the GPU
>>>> (it says it is being used). But shutting down the domU, doing echo 1
>>>> > reset for the GPU from dom0 (I don't know how this is implemented
>>>> and whether it does anything) and then starting it up again sometimes
>>>> recovers it. GPU-Z runs and reports the GPU correctly.
>>>>
>>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as
>>>> soon as the driver is loaded in domU. My solution is to swap the dom0
>>>> GPU for an 8800GT, and the problem now doesn't occur. If I had to
>>>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on
>>>> the bus, tries to do something to it, and ends up crashing the host.
>>>> This could also be exacerbated by the fact that I have to run with
>>>> relaxed checking and no PCI ACS due to NF200 bridges on my
>>>> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
>>>> _hard_ (but not the host, thankfully). It crashes it so hard, that
>>>> the only cure is to reboot the host. Reseting the GPU via /sys/
>>>> doesn't seem to do anything to help.
>>>>
>>>> Are you using gfx_passthru=1 in your config? The way most people have
>>>> this kind of thing working is with gfx_passthru=0, i.e. secondary
>>>> passthru. Don't assign the PCI device in the config when installing.
>>>> Once the domU install is complete, shut it down, and add the GPU you
>>>> want to pass through. Then fire up domU in VNC, install the driver,
>>>> and with a bit of luck it will come up with output on the external
>>>> monitor.
>>>>
>>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load
>>>> before the device is assigned to xen-pciback. The exact way to ensure
>>>> this will depend on what distro and dom0 kernel you are using.
>>>>
>>>> Gordan
>>> Status update:
>>>
>>> The catalyst drivers appear to be working perfectly fine, device
>>> manager shows no errors, and everything works great, except that when
>>> I plug my monitor into the second card, I get "No Signal" on the
>>> monitor, then it shuts off.
>>>
>>> I though that secondary passthrough meant that it would pass the
>>> virtual adapter in as primary, but I could use my GPU that I passed
>>> through, so where am I wrong, and how do I do that?
>>>
>>> -John
>> I've been doing some research into my VGA passthrough, so I've gone
>> through the various debugging steps, and the only thing that I've found
>> out of place is with "xl dmesg" (attached).
>>
>> Where do I go from here?
>
> Sounds like your IOMMU may be buggy. You may need to set permissive=1
> on your xen-pciback module.
>
> I cannot remember if xl uses the same configuration, but for xm you
> could try putting this in your /etc/xen/xend-config.sxp:
> (pci-passthrough-strict-check no)
> (pci-dev-assign-strict-check no)
>
> Gordan
>
Gordan,
After a bit of research, I was able to activate permissive mode on xen,
but I've got nothing, I'm still getting page faults.
The page faults occur when the loading screen goes black (I'd assume
when it's trying to pass to the GPU)
I've also tried setting (pci_msitranslate=0, along with changing
qemu=qemu-xen, but it doesn't help
-John
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 21:01 ` John Wargo
@ 2013-10-27 22:51 ` Gordan Bobic
2013-10-28 11:06 ` John Wargo
0 siblings, 1 reply; 20+ messages in thread
From: Gordan Bobic @ 2013-10-27 22:51 UTC (permalink / raw)
To: John Wargo; +Cc: xen-devel@lists.xen.org
On 10/27/2013 09:01 PM, John Wargo wrote:
> On 10/27/2013 02:35 PM, Gordan Bobic wrote:
>> On 10/27/2013 04:21 PM, John Wargo wrote:
>>> On 10/27/2013 09:27 AM, John Wargo wrote:
>>>> On 10/27/2013 04:30 AM, Gordan Bobic wrote:
>>>>> On 10/26/2013 09:58 PM, John Wargo wrote:
>>>>>> Geniuses,
>>>>>>
>>>>>> I've been trying to get VGA pass-through working on Windows 8,
>>>>>> however
>>>>>> I've been running into a few issues.
>>>>>> Currently I can get Windows 8 running flawlessly without VGA
>>>>>> pass-through, however I'm planning on using it for gaming, so this
>>>>>> wont
>>>>>> work.
>>>>>>
>>>>>> When I start windows 8, I am able to get past the install portion of
>>>>>> the
>>>>>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>>>>>
>>>>>> Hardware Information :
>>>>>> AMD Fx6300
>>>>>> ASUS M5a99x evo r2.0
>>>>>> 16GB RAM
>>>>>> 6670 Radeon HD - Dom0
>>>>>> 7850 Radeon HD - Win8
>>>>>
>>>>> I have recently (recently as in over the past 48 hours) re-tried to
>>>>> get ATI VGA passthrough working, and the results are... interesting.
>>>>>
>>>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough
>>>>> ever seems to work (slowdown + white lines when dragging windows
>>>>> after a domU reboot). I am using XP64 domU so I can't eject the GPU
>>>>> (it says it is being used). But shutting down the domU, doing echo 1
>>>>> > reset for the GPU from dom0 (I don't know how this is implemented
>>>>> and whether it does anything) and then starting it up again sometimes
>>>>> recovers it. GPU-Z runs and reports the GPU correctly.
>>>>>
>>>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as
>>>>> soon as the driver is loaded in domU. My solution is to swap the dom0
>>>>> GPU for an 8800GT, and the problem now doesn't occur. If I had to
>>>>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on
>>>>> the bus, tries to do something to it, and ends up crashing the host.
>>>>> This could also be exacerbated by the fact that I have to run with
>>>>> relaxed checking and no PCI ACS due to NF200 bridges on my
>>>>> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
>>>>> _hard_ (but not the host, thankfully). It crashes it so hard, that
>>>>> the only cure is to reboot the host. Reseting the GPU via /sys/
>>>>> doesn't seem to do anything to help.
>>>>>
>>>>> Are you using gfx_passthru=1 in your config? The way most people have
>>>>> this kind of thing working is with gfx_passthru=0, i.e. secondary
>>>>> passthru. Don't assign the PCI device in the config when installing.
>>>>> Once the domU install is complete, shut it down, and add the GPU you
>>>>> want to pass through. Then fire up domU in VNC, install the driver,
>>>>> and with a bit of luck it will come up with output on the external
>>>>> monitor.
>>>>>
>>>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load
>>>>> before the device is assigned to xen-pciback. The exact way to ensure
>>>>> this will depend on what distro and dom0 kernel you are using.
>>>>>
>>>>> Gordan
>>>> Status update:
>>>>
>>>> The catalyst drivers appear to be working perfectly fine, device
>>>> manager shows no errors, and everything works great, except that when
>>>> I plug my monitor into the second card, I get "No Signal" on the
>>>> monitor, then it shuts off.
>>>>
>>>> I though that secondary passthrough meant that it would pass the
>>>> virtual adapter in as primary, but I could use my GPU that I passed
>>>> through, so where am I wrong, and how do I do that?
>>>>
>>>> -John
>>> I've been doing some research into my VGA passthrough, so I've gone
>>> through the various debugging steps, and the only thing that I've found
>>> out of place is with "xl dmesg" (attached).
>>>
>>> Where do I go from here?
>>
>> Sounds like your IOMMU may be buggy. You may need to set permissive=1
>> on your xen-pciback module.
>>
>> I cannot remember if xl uses the same configuration, but for xm you
>> could try putting this in your /etc/xen/xend-config.sxp:
>> (pci-passthrough-strict-check no)
>> (pci-dev-assign-strict-check no)
>>
>> Gordan
>>
> Gordan,
>
> After a bit of research, I was able to activate permissive mode on xen,
> but I've got nothing, I'm still getting page faults.
>
> The page faults occur when the loading screen goes black (I'd assume
> when it's trying to pass to the GPU)
>
> I've also tried setting (pci_msitranslate=0, along with changing
> qemu=qemu-xen, but it doesn't help
The correct incantation you seek is to put this in the config:
device_model_version="qemu-xen-traditional"
Gordan
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 22:51 ` Gordan Bobic
@ 2013-10-28 11:06 ` John Wargo
0 siblings, 0 replies; 20+ messages in thread
From: John Wargo @ 2013-10-28 11:06 UTC (permalink / raw)
To: Gordan Bobic; +Cc: xen-devel@lists.xen.org
On 10/27/2013 05:51 PM, Gordan Bobic wrote:
> On 10/27/2013 09:01 PM, John Wargo wrote:
>> On 10/27/2013 02:35 PM, Gordan Bobic wrote:
>>> On 10/27/2013 04:21 PM, John Wargo wrote:
>>>> On 10/27/2013 09:27 AM, John Wargo wrote:
>>>>> On 10/27/2013 04:30 AM, Gordan Bobic wrote:
>>>>>> On 10/26/2013 09:58 PM, John Wargo wrote:
>>>>>>> Geniuses,
>>>>>>>
>>>>>>> I've been trying to get VGA pass-through working on Windows 8,
>>>>>>> however
>>>>>>> I've been running into a few issues.
>>>>>>> Currently I can get Windows 8 running flawlessly without VGA
>>>>>>> pass-through, however I'm planning on using it for gaming, so this
>>>>>>> wont
>>>>>>> work.
>>>>>>>
>>>>>>> When I start windows 8, I am able to get past the install
>>>>>>> portion of
>>>>>>> the
>>>>>>> DVD, however it hangs on "Getting devices ready.. (n%)".
>>>>>>>
>>>>>>> Hardware Information :
>>>>>>> AMD Fx6300
>>>>>>> ASUS M5a99x evo r2.0
>>>>>>> 16GB RAM
>>>>>>> 6670 Radeon HD - Dom0
>>>>>>> 7850 Radeon HD - Win8
>>>>>>
>>>>>> I have recently (recently as in over the past 48 hours) re-tried to
>>>>>> get ATI VGA passthrough working, and the results are... interesting.
>>>>>>
>>>>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI
>>>>>> passthrough
>>>>>> ever seems to work (slowdown + white lines when dragging windows
>>>>>> after a domU reboot). I am using XP64 domU so I can't eject the GPU
>>>>>> (it says it is being used). But shutting down the domU, doing echo 1
>>>>>> > reset for the GPU from dom0 (I don't know how this is implemented
>>>>>> and whether it does anything) and then starting it up again
>>>>>> sometimes
>>>>>> recovers it. GPU-Z runs and reports the GPU correctly.
>>>>>>
>>>>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as
>>>>>> soon as the driver is loaded in domU. My solution is to swap the
>>>>>> dom0
>>>>>> GPU for an 8800GT, and the problem now doesn't occur. If I had to
>>>>>> guess, BIOS on the HD7970 does something bizzare, finds the
>>>>>> HD4850 on
>>>>>> the bus, tries to do something to it, and ends up crashing the host.
>>>>>> This could also be exacerbated by the fact that I have to run with
>>>>>> relaxed checking and no PCI ACS due to NF200 bridges on my
>>>>>> motherboard. Even so, however, GPU-Z crashes the domU and it's GPU
>>>>>> _hard_ (but not the host, thankfully). It crashes it so hard, that
>>>>>> the only cure is to reboot the host. Reseting the GPU via /sys/
>>>>>> doesn't seem to do anything to help.
>>>>>>
>>>>>> Are you using gfx_passthru=1 in your config? The way most people
>>>>>> have
>>>>>> this kind of thing working is with gfx_passthru=0, i.e. secondary
>>>>>> passthru. Don't assign the PCI device in the config when installing.
>>>>>> Once the domU install is complete, shut it down, and add the GPU you
>>>>>> want to pass through. Then fire up domU in VNC, install the driver,
>>>>>> and with a bit of luck it will come up with output on the external
>>>>>> monitor.
>>>>>>
>>>>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load
>>>>>> before the device is assigned to xen-pciback. The exact way to
>>>>>> ensure
>>>>>> this will depend on what distro and dom0 kernel you are using.
>>>>>>
>>>>>> Gordan
>>>>> Status update:
>>>>>
>>>>> The catalyst drivers appear to be working perfectly fine, device
>>>>> manager shows no errors, and everything works great, except that when
>>>>> I plug my monitor into the second card, I get "No Signal" on the
>>>>> monitor, then it shuts off.
>>>>>
>>>>> I though that secondary passthrough meant that it would pass the
>>>>> virtual adapter in as primary, but I could use my GPU that I passed
>>>>> through, so where am I wrong, and how do I do that?
>>>>>
>>>>> -John
>>>> I've been doing some research into my VGA passthrough, so I've gone
>>>> through the various debugging steps, and the only thing that I've
>>>> found
>>>> out of place is with "xl dmesg" (attached).
>>>>
>>>> Where do I go from here?
>>>
>>> Sounds like your IOMMU may be buggy. You may need to set permissive=1
>>> on your xen-pciback module.
>>>
>>> I cannot remember if xl uses the same configuration, but for xm you
>>> could try putting this in your /etc/xen/xend-config.sxp:
>>> (pci-passthrough-strict-check no)
>>> (pci-dev-assign-strict-check no)
>>>
>>> Gordan
>>>
>> Gordan,
>>
>> After a bit of research, I was able to activate permissive mode on xen,
>> but I've got nothing, I'm still getting page faults.
>>
>> The page faults occur when the loading screen goes black (I'd assume
>> when it's trying to pass to the GPU)
>>
>> I've also tried setting (pci_msitranslate=0, along with changing
>> qemu=qemu-xen, but it doesn't help
>
> The correct incantation you seek is to put this in the config:
> device_model_version="qemu-xen-traditional"
>
> Gordan
Gordan,
Sorry for the confusion, I think that's what I meant by changing
"qemu=qemu-xen", and I've been running off of "qemu-xen-traditional" up
until I changed it.
I'm giving it another shot right now just in case though.
-John
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 17:21 ` John Wargo
@ 2013-10-28 17:07 ` Konrad Rzeszutek Wilk
2013-10-28 21:32 ` John Wargo
2013-10-28 19:30 ` Zytaruk, Kelly
1 sibling, 1 reply; 20+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-10-28 17:07 UTC (permalink / raw)
To: John Wargo; +Cc: Gordan Bobic, xen-devel@lists.xen.org
On Sun, Oct 27, 2013 at 12:21:14PM -0500, John Wargo wrote:
> I've made quite a bit of changes since my last email, and so far
> here's what I've got:
>
> AMD FX6300
> ASUS M5A99X evo r2.0
> ASUS Radeon 6670 (Dom0)
> XFX Radeon 7850 (Win8)
>
> Right now I've got AMD Catalyst (latest stable) installed in windows
> 8, and device manager shows my Radeon 7850 reporting no issues.
>
> I'm currently passing it through as secondary (gfx_passthrough=0),
> however I cannot plug my monitor into it.
>
> After taking debugging steps, I've come up with the attached debugging info:
> info - xl info
> dmesg - xl dmesg
> grub - a copy of '/etc/default/grub'
> win8.cfg - the configuration I'm using to launch windows 8
>
> Fedora bug reporting tool caught a kernel bug at
> 'drivers/gpu/drm/ttm/ttm_bo.c:210', I have compiled xen from source,
> and I'm using it as a kernel (or really part of it).
OK, what was the rest of it? And what version of the kernel?
You also seem to have a debug.zip attached - but it has nothing it it?
>
> Is there some sort of AMD Radeon patch I need to use (I saw one on
> the wiki, but it appeared to be several years old), or is it a
> needed configuration?
>
> Thanks for your time,
> -John
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-27 17:21 ` John Wargo
2013-10-28 17:07 ` Konrad Rzeszutek Wilk
@ 2013-10-28 19:30 ` Zytaruk, Kelly
2013-10-28 20:31 ` John Wargo
1 sibling, 1 reply; 20+ messages in thread
From: Zytaruk, Kelly @ 2013-10-28 19:30 UTC (permalink / raw)
To: John Wargo, Gordan Bobic, xen-devel@lists.xen.org
On Sunday, October 27, 2013 1:21 PM, John Wargo wrote:
>I've made quite a bit of changes since my last email, and so far here's what I've got:
>
>AMD FX6300
>ASUS M5A99X evo r2.0
>ASUS Radeon 6670 (Dom0)
>XFX Radeon 7850 (Win8)
>
>...
>
>Is there some sort of AMD Radeon patch I need to use (I saw one on the wiki, but it appeared to be several years old), or is it a needed configuration?
>
>Thanks for your time,
>-John
Hi John,
I am using XEN4.2 with QEMU-traditional and I have identified a couple of issues in regards to passing through a video adapter as the primary (VGA enabled) adapter.
The patch that you referenced attempts to get around one of the issues but it is not complete and doesn't cover all of the cases. If you apply the patch it will definitely help but not guaranteed to fix all of your problems.
The second issue is related to the fact that you are using two different graphics adapters. I am assuming that the Radeon 6670 is the primary (boot/VGA) adapter and that the 7850 is the secondary.
>From reading your thread I assume that you want to pass the 7850 through to the DomU as the primary. I have been able to do this successfully with a few fixes. The problem is in the way QEMU/hvmloader handle the VBios code. When you boot with the 6670 as the primary the VBios code for the graphics adapter is copied to memory at address 0xc0000. When QEMU passes the 7850 through to the DomU it copies VBios from 0xc0000 in Dom0 memory space into 0xc0000 in DomU memory space. DomU is effectively executing the VBios for the wrong video card. The correct fix is to have the hvmloader read a fresh copy of VBios from the 7850 and copy it into the DomU address space at 0xc0000.
Sometimes you can get away with executing the wrong VBios, sometimes you get stung.
Hope the explanation helps,
Kelly
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-28 19:30 ` Zytaruk, Kelly
@ 2013-10-28 20:31 ` John Wargo
2013-10-28 20:46 ` Gordan Bobic
0 siblings, 1 reply; 20+ messages in thread
From: John Wargo @ 2013-10-28 20:31 UTC (permalink / raw)
To: Zytaruk, Kelly; +Cc: Gordan Bobic, xen-devel@lists.xen.org
[-- Attachment #1.1: Type: text/plain, Size: 2265 bytes --]
This sounds about right, what then is the fix though? How do i get qemu/hvm
load the right vbios? On a side note, I assume that i need to install the
mentioned patch, if so, whats the best way to apply it? (It seems dated,
and i get errors when i try to patch with it)
Sorry for asking such basic questions,
-John
On Monday, October 28, 2013, Zytaruk, Kelly <Kelly.Zytaruk@amd.com> wrote:
> On Sunday, October 27, 2013 1:21 PM, John Wargo wrote:
>>I've made quite a bit of changes since my last email, and so far here's
what I've got:
>>
>>AMD FX6300
>>ASUS M5A99X evo r2.0
>>ASUS Radeon 6670 (Dom0)
>>XFX Radeon 7850 (Win8)
>>
>>...
>>
>>Is there some sort of AMD Radeon patch I need to use (I saw one on the
wiki, but it appeared to be several years old), or is it a needed
configuration?
>>
>>Thanks for your time,
>>-John
>
> Hi John,
>
> I am using XEN4.2 with QEMU-traditional and I have identified a couple of
issues in regards to passing through a video adapter as the primary (VGA
enabled) adapter.
>
> The patch that you referenced attempts to get around one of the issues
but it is not complete and doesn't cover all of the cases. If you apply
the patch it will definitely help but not guaranteed to fix all of your
problems.
>
> The second issue is related to the fact that you are using two different
graphics adapters. I am assuming that the Radeon 6670 is the primary
(boot/VGA) adapter and that the 7850 is the secondary.
>
> From reading your thread I assume that you want to pass the 7850 through
to the DomU as the primary. I have been able to do this successfully with
a few fixes. The problem is in the way QEMU/hvmloader handle the VBios
code. When you boot with the 6670 as the primary the VBios code for the
graphics adapter is copied to memory at address 0xc0000. When QEMU passes
the 7850 through to the DomU it copies VBios from 0xc0000 in Dom0 memory
space into 0xc0000 in DomU memory space. DomU is effectively executing the
VBios for the wrong video card. The correct fix is to have the hvmloader
read a fresh copy of VBios from the 7850 and copy it into the DomU address
space at 0xc0000.
>
> Sometimes you can get away with executing the wrong VBios, sometimes you
get stung.
>
> Hope the explanation helps,
> Kelly
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2593 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-28 20:31 ` John Wargo
@ 2013-10-28 20:46 ` Gordan Bobic
2013-10-28 21:29 ` John Wargo
0 siblings, 1 reply; 20+ messages in thread
From: Gordan Bobic @ 2013-10-28 20:46 UTC (permalink / raw)
To: John Wargo; +Cc: Zytaruk, Kelly, xen-devel@lists.xen.org
I'd focus more on why exactly do you think you need primary passthrough.
Is your requirement for seeing the SeaBIOS POST and the Windows loading
animation strong enough to bother with the amount of extra pain that it
is going to require?
On 10/28/2013 08:31 PM, John Wargo wrote:
> This sounds about right, what then is the fix though? How do i get
> qemu/hvm load the right vbios? On a side note, I assume that i need to
> install the mentioned patch, if so, whats the best way to apply it? (It
> seems dated, and i get errors when i try to patch with it)
>
> Sorry for asking such basic questions,
> -John
>
> On Monday, October 28, 2013, Zytaruk, Kelly <Kelly.Zytaruk@amd.com
> <mailto:Kelly.Zytaruk@amd.com>> wrote:
> > On Sunday, October 27, 2013 1:21 PM, John Wargo wrote:
> >>I've made quite a bit of changes since my last email, and so far
> here's what I've got:
> >>
> >>AMD FX6300
> >>ASUS M5A99X evo r2.0
> >>ASUS Radeon 6670 (Dom0)
> >>XFX Radeon 7850 (Win8)
> >>
> >>...
> >>
> >>Is there some sort of AMD Radeon patch I need to use (I saw one on
> the wiki, but it appeared to be several years old), or is it a needed
> configuration?
> >>
> >>Thanks for your time,
> >>-John
> >
> > Hi John,
> >
> > I am using XEN4.2 with QEMU-traditional and I have identified a
> couple of issues in regards to passing through a video adapter as the
> primary (VGA enabled) adapter.
> >
> > The patch that you referenced attempts to get around one of the
> issues but it is not complete and doesn't cover all of the cases. If
> you apply the patch it will definitely help but not guaranteed to fix
> all of your problems.
> >
> > The second issue is related to the fact that you are using two
> different graphics adapters. I am assuming that the Radeon 6670 is the
> primary (boot/VGA) adapter and that the 7850 is the secondary.
> >
> > From reading your thread I assume that you want to pass the 7850
> through to the DomU as the primary. I have been able to do this
> successfully with a few fixes. The problem is in the way
> QEMU/hvmloader handle the VBios code. When you boot with the 6670 as
> the primary the VBios code for the graphics adapter is copied to memory
> at address 0xc0000. When QEMU passes the 7850 through to the DomU it
> copies VBios from 0xc0000 in Dom0 memory space into 0xc0000 in DomU
> memory space. DomU is effectively executing the VBios for the wrong
> video card. The correct fix is to have the hvmloader read a fresh copy
> of VBios from the 7850 and copy it into the DomU address space at 0xc0000.
> >
> > Sometimes you can get away with executing the wrong VBios, sometimes
> you get stung.
> >
> > Hope the explanation helps,
> > Kelly
> >
> >
> >
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-28 20:46 ` Gordan Bobic
@ 2013-10-28 21:29 ` John Wargo
0 siblings, 0 replies; 20+ messages in thread
From: John Wargo @ 2013-10-28 21:29 UTC (permalink / raw)
To: Gordan Bobic; +Cc: Zytaruk, Kelly, xen-devel@lists.xen.org
[-- Attachment #1.1: Type: text/plain, Size: 2949 bytes --]
I dont want primary passthrough, im currently just trying for secondary..
On Monday, October 28, 2013, Gordan Bobic <gordan@bobich.net> wrote:
> I'd focus more on why exactly do you think you need primary passthrough.
Is your requirement for seeing the SeaBIOS POST and the Windows loading
animation strong enough to bother with the amount of extra pain that it is
going to require?
>
> On 10/28/2013 08:31 PM, John Wargo wrote:
>>
>> This sounds about right, what then is the fix though? How do i get
>> qemu/hvm load the right vbios? On a side note, I assume that i need to
>> install the mentioned patch, if so, whats the best way to apply it? (It
>> seems dated, and i get errors when i try to patch with it)
>>
>> Sorry for asking such basic questions,
>> -John
>>
>> On Monday, October 28, 2013, Zytaruk, Kelly <Kelly.Zytaruk@amd.com
>> <mailto:Kelly.Zytaruk@amd.com>> wrote:
>> > On Sunday, October 27, 2013 1:21 PM, John Wargo wrote:
>> >>I've made quite a bit of changes since my last email, and so far
>> here's what I've got:
>> >>
>> >>AMD FX6300
>> >>ASUS M5A99X evo r2.0
>> >>ASUS Radeon 6670 (Dom0)
>> >>XFX Radeon 7850 (Win8)
>> >>
>> >>...
>> >>
>> >>Is there some sort of AMD Radeon patch I need to use (I saw one on
>> the wiki, but it appeared to be several years old), or is it a needed
>> configuration?
>> >>
>> >>Thanks for your time,
>> >>-John
>> >
>> > Hi John,
>> >
>> > I am using XEN4.2 with QEMU-traditional and I have identified a
>> couple of issues in regards to passing through a video adapter as the
>> primary (VGA enabled) adapter.
>> >
>> > The patch that you referenced attempts to get around one of the
>> issues but it is not complete and doesn't cover all of the cases. If
>> you apply the patch it will definitely help but not guaranteed to fix
>> all of your problems.
>> >
>> > The second issue is related to the fact that you are using two
>> different graphics adapters. I am assuming that the Radeon 6670 is the
>> primary (boot/VGA) adapter and that the 7850 is the secondary.
>> >
>> > From reading your thread I assume that you want to pass the 7850
>> through to the DomU as the primary. I have been able to do this
>> successfully with a few fixes. The problem is in the way
>> QEMU/hvmloader handle the VBios code. When you boot with the 6670 as
>> the primary the VBios code for the graphics adapter is copied to memory
>> at address 0xc0000. When QEMU passes the 7850 through to the DomU it
>> copies VBios from 0xc0000 in Dom0 memory space into 0xc0000 in DomU
>> memory space. DomU is effectively executing the VBios for the wrong
>> video card. The correct fix is to have the hvmloader read a fresh copy
>> of VBios from the 7850 and copy it into the DomU address space at
0xc0000.
>> >
>> > Sometimes you can get away with executing the wrong VBios, sometimes
>> you get stung.
>> >
>> > Hope the explanation helps,
>> > Kelly
>> >
>> >
>> >
>
>
[-- Attachment #1.2: Type: text/html, Size: 3879 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-28 17:07 ` Konrad Rzeszutek Wilk
@ 2013-10-28 21:32 ` John Wargo
2013-10-29 13:09 ` Zytaruk, Kelly
0 siblings, 1 reply; 20+ messages in thread
From: John Wargo @ 2013-10-28 21:32 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: Gordan Bobic, xen-devel@lists.xen.org
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset=UTF-8, Size: 1595 bytes --]
Sorry for the delay, when i get home ill get ï¿¿both to you.
On Monday, October 28, 2013, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
wrote:
> On Sun, Oct 27, 2013 at 12:21:14PM -0500, John Wargo wrote:
>> I've made quite a bit of changes since my last email, and so far
>> here's what I've got:
>>
>> AMD FX6300
>> ASUS M5A99X evo r2.0
>> ASUS Radeon 6670 (Dom0)
>> XFX Radeon 7850 (Win8)
>>
>> Right now I've got AMD Catalyst (latest stable) installed in windows
>> 8, and device manager shows my Radeon 7850 reporting no issues.
>>
>> I'm currently passing it through as secondary (gfx_passthrough=0),
>> however I cannot plug my monitor into it.
>>
>> After taking debugging steps, I've come up with the attached debugging
info:
>> info - xl info
>> dmesg - xl dmesg
>> grub - a copy of '/etc/default/grub'
>> win8.cfg - the configuration I'm using to launch windows 8
>>
>> Fedora bug reporting tool caught a kernel bug at
>> 'drivers/gpu/drm/ttm/ttm_bo.c:210', I have compiled xen from source,
>> and I'm using it as a kernel (or really part of it).
>
> OK, what was the rest of it? And what version of the kernel?
>
> You also seem to have a debug.zip attached - but it has nothing it it?
>>
>> Is there some sort of AMD Radeon patch I need to use (I saw one on
>> the wiki, but it appeared to be several years old), or is it a
>> needed configuration?
>>
>> Thanks for your time,
>> -John
>
>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 2118 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Windows 8 VGA Passthrough
2013-10-28 21:32 ` John Wargo
@ 2013-10-29 13:09 ` Zytaruk, Kelly
0 siblings, 0 replies; 20+ messages in thread
From: Zytaruk, Kelly @ 2013-10-29 13:09 UTC (permalink / raw)
To: John Wargo, Konrad Rzeszutek Wilk; +Cc: Gordan Bobic, xen-devel@lists.xen.org
[-- Attachment #1.1: Type: text/plain, Size: 2381 bytes --]
On Mon, 28 Oct 2013 16:29:49 -0500 John Wargo wrote;
>I dont want primary passthrough, im currently just trying for secondary..
>
>On Monday, October 28, 2013, Gordan Bobic <gordan@xxxxxxxxxx<mailto:gordan@xxxxxxxxxx>> wrote:
>> I'd focus more on why exactly do you think you need primary passthrough. Is your requirement
>>for seeing the SeaBIOS POST and the Windows loading animation strong enough to bother with
>>the amount of extra pain that it is going to require?
And on Sunday, October 27, 2013 10:28 AM John Wargo also wrote;
> I though that secondary passthrough meant that it would pass the virtual adapter in as primary,
>but I could use my GPU that I passed through, so where am I wrong, and how do I do that?
John,
I’m not totally clear what you are trying to accomplish. Let me start with some groundwork and you can
help me from there.
You have 2 adapters; Radeon HD 6670 and Radeon HD 7850
Correct me if I am wrong but it sounds like you have booted on the 6670.
This make the 6670 the primary (VGA boot adapter) and the 7850 is the secondary adapter.
6670 = primary
7850 = secondary
There are 4 possible adapter configurations for DomU;
- Pass through primary as primary (6670 is primary in DomU)
- Pass through primary as secondary (6670 is secondary in DomU, Cirrus emulated is primary)
- Pass through secondary as primary (7850 is primary in DomU)
- Pass through secondary as secondary (7850 is secondary in DomU, Cirrus emulated is primary)
You said you wanted Dom0 = 6670 and DomU = 7850.
Looking at the list above, there are two possible configurations for the 7850 in DomU; 7850 as primary or
7850 as secondary.
If you set “gfx_passthru=1” in your .cfg file for DomU you will pass the 7850 through as a primary. This means
that the DomU will use the 7850 as a boot VGA adapter. Your desktop will be accelerated using the 7850.
If you set “gfx_passthru=0” in your .cfg file for DomU you will pass the 7850 through as a secondary. This means
that the DomU will use the Cirrus emulated VGA VBios as the boot device. Your desktop will use the emulated
adapter and the 7850 will be a secondary (extended) adapter.
So, the question is; what are you trying to accomplish?
Thanks,
Kelly
[-- Attachment #1.2: Type: text/html, Size: 9282 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2013-10-29 13:09 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-26 20:58 Windows 8 VGA Passthrough John Wargo
2013-10-27 9:30 ` Gordan Bobic
2013-10-27 14:27 ` John Wargo
2013-10-27 16:21 ` John Wargo
2013-10-27 17:21 ` John Wargo
2013-10-28 17:07 ` Konrad Rzeszutek Wilk
2013-10-28 21:32 ` John Wargo
2013-10-29 13:09 ` Zytaruk, Kelly
2013-10-28 19:30 ` Zytaruk, Kelly
2013-10-28 20:31 ` John Wargo
2013-10-28 20:46 ` Gordan Bobic
2013-10-28 21:29 ` John Wargo
2013-10-27 19:35 ` Gordan Bobic
2013-10-27 19:45 ` John Wargo
2013-10-27 20:05 ` John Wargo
2013-10-27 21:01 ` John Wargo
2013-10-27 22:51 ` Gordan Bobic
2013-10-28 11:06 ` John Wargo
2013-10-27 19:31 ` Gordan Bobic
[not found] ` <526D1FBA.10708@gmail.com>
2013-10-27 19:28 ` Gordan Bobic
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).