good progress on pci vga passthrough in xen-3.4-rc1

good progress on pci vga passthrough in xen-3.4-rc1

[Tim Moore]

[-- Attachment #1.1: Type: text/plain, Size: 2002 bytes --]

Platform : Nehalem, official Intel x58 with Core i7 920 (dx58so)
Main (Console): Nvidia 9500 GT PCI Express
Secondary: Nvidia 8800 GTS PCI Express

Yes, I binned the ASUS P6T due to bad VT-d support in the BIOS.

With the latest BIOS from Intel, the dx58so has enable/disable for VT-d, ICH FLR and Interrupt Mapping! Helped a lot with getting this working ...

Dom0: 2.6.18-xen0 (built from xen-3.4-rc1)
DomU: 2.6.26-1-xen-amd64 (deb lenny shipped)

SUCCESS! - Linux DomU with the official drivers from Nvidia (180.44) .. boot DomU into console, patch and install Nvidia driver, then started X using defaults. gdm chooser appeared on Secondary screen!!

So far, i`m using VNC or Synergy to control the DomU (from Dom0 also running X/gdm) and it is good and stable.

ISSUES:
This is only possible after a clean restart of the physical machine. Dom0 kernel seems to have problems with the IRQ. BUG trap: "irq has gone away" after attempting to start DomU a second time, Dom0 kernel displays: Disabling IRQ#. (the IRQ IS being shared on Dom0 with a usb controller, but im assuming this is already patched from reading xen history)

Also confirmed that this is NOT possible under a HVM or running Windows in a DomU, this could be due to the IRQ corruption but i`m not really sure, in both cases the PCI device is visible but the driver will not load :(

As these vga cards dont support FLR, would the FLR code when attempting d3r or sbr cause the interrupt corruption ?

Some steer and some assistance would help here, i`m trying to get this working for HVM too !?

BTW: I`m eagerly awaiting Jeremy Fitzhardinge to bring pciback.ko to the modern kernels ! Support for this chipset in 2.6.18 is not very good and i would like to try pvops and PCI passthrough. (although, got a hang with x2apic and IRQ mapping enabled)

I`m willing to help move the development of xen forwards with any testing or assistance you guys need!

Thanks,
Tim
http://www.linkedin.com/in/tmoore




[-- Attachment #1.2: Type: text/html, Size: 5231 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: good progress on pci vga passthrough in xen-3.4-rc1

[Bryan York]

[-- Attachment #1.1: Type: text/plain, Size: 2687 bytes --]

Working on something similar. Have you contacted Peter J. van der Maas
regarding this? He has the Q35 intel board, but was able to fully pass
through an nvidia card to a Windows HVM DomU. You can see his latest message
on Thu, Apr 9, 2009 at 5:54 PM in the xen-users list. He may have some more
technical details regarding this, but he seems hesitant to provide more
details to these lists.

-Bryan

On Sun, Apr 12, 2009 at 4:03 PM, Tim Moore <timothy.moore@expidas.net>wrote:

>  Platform : Nehalem, official Intel x58 with Core i7 920 (dx58so)
>  Main (Console): Nvidia 9500 GT PCI Express
> Secondary: Nvidia 8800 GTS PCI Express
>
>  Yes, I binned the ASUS P6T due to bad VT-d support in the BIOS.
>
>  With the latest BIOS from Intel, the dx58so has enable/disable for VT-d,
> ICH FLR and Interrupt Mapping! Helped a lot with getting this working ...
>
> Dom0: 2.6.18-xen0 (built from xen-3.4-rc1)
> DomU: 2.6.26-1-xen-amd64 (deb lenny shipped)
>
> SUCCESS! - Linux DomU with the official drivers from Nvidia (180.44) ..
> boot DomU into console, patch and install Nvidia driver, then started X
> using defaults. gdm chooser appeared on Secondary screen!!
>
> So far, i`m using VNC or Synergy to control the DomU (from Dom0 also
> running X/gdm) and it is good and stable.
>
> ISSUES:
> This is only possible after a clean restart of the physical machine. Dom0
> kernel seems to have problems with the IRQ. BUG trap: "irq has gone away"
> after attempting to start DomU a second time, Dom0 kernel displays:
> Disabling IRQ#. (the IRQ IS being shared on Dom0 with a usb controller, but
> im assuming this is already patched from reading xen history)
>
> Also confirmed that this is NOT possible under a HVM or running Windows in
> a DomU, this could be due to the IRQ corruption but i`m not really sure, in
> both cases the PCI device is visible but the driver will not load :(
>
> As these vga cards dont support FLR, would the FLR code when attempting d3r
> or sbr cause the interrupt corruption ?
>
> Some steer and some assistance would help here, i`m trying to get this
> working for HVM too !?
>
> BTW: I`m eagerly awaiting Jeremy Fitzhardinge to bring pciback.ko to the
> modern kernels ! Support for this chipset in 2.6.18 is not very good and i
> would like to try pvops and PCI passthrough. (although, got a hang with
> x2apic and IRQ mapping enabled)
>
> I`m willing to help move the development of xen forwards with any testing
> or assistance you guys need!
>
> Thanks,
> Tim
> http://www.linkedin.com/in/tmoore
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>

[-- Attachment #1.2: Type: text/html, Size: 5932 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

RE: good progress on pci vga passthrough in xen-3.4-rc1

[Tim Moore]

[-- Attachment #1.1: Type: text/plain, Size: 3488 bytes --]

Hi Bryan

I think my email to Peter along with emails from probably yourself and other people in the community is what prompted his reply to xen-users.

There seems to be a general reluctance to move this forwards within the Xen developers, I think this may be due to the current status of some of the commercial vendors that are working on the "next big thing" for Virtualisation. Neocleus and XCI seem to be the products that will bring this to market.. it seems that the open source community may be being left out at this stage!?

Tim

________________________________
From: Bryan York [mailto:bryan.york@gmail.com]
Sent: 15 April 2009 04:37
To: Tim Moore
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1

Working on something similar. Have you contacted Peter J. van der Maas regarding this? He has the Q35 intel board, but was able to fully pass through an nvidia card to a Windows HVM DomU. You can see his latest message on Thu, Apr 9, 2009 at 5:54 PM in the xen-users list. He may have some more technical details regarding this, but he seems hesitant to provide more details to these lists.

-Bryan
On Sun, Apr 12, 2009 at 4:03 PM, Tim Moore <timothy.moore@expidas.net<mailto:timothy.moore@expidas.net>> wrote:
Platform : Nehalem, official Intel x58 with Core i7 920 (dx58so)
Main (Console): Nvidia 9500 GT PCI Express
Secondary: Nvidia 8800 GTS PCI Express

Yes, I binned the ASUS P6T due to bad VT-d support in the BIOS.

With the latest BIOS from Intel, the dx58so has enable/disable for VT-d, ICH FLR and Interrupt Mapping! Helped a lot with getting this working ...

Dom0: 2.6.18-xen0 (built from xen-3.4-rc1)
DomU: 2.6.26-1-xen-amd64 (deb lenny shipped)

SUCCESS! - Linux DomU with the official drivers from Nvidia (180.44) .. boot DomU into console, patch and install Nvidia driver, then started X using defaults. gdm chooser appeared on Secondary screen!!

So far, i`m using VNC or Synergy to control the DomU (from Dom0 also running X/gdm) and it is good and stable.

ISSUES:
This is only possible after a clean restart of the physical machine. Dom0 kernel seems to have problems with the IRQ. BUG trap: "irq has gone away" after attempting to start DomU a second time, Dom0 kernel displays: Disabling IRQ#. (the IRQ IS being shared on Dom0 with a usb controller, but im assuming this is already patched from reading xen history)

Also confirmed that this is NOT possible under a HVM or running Windows in a DomU, this could be due to the IRQ corruption but i`m not really sure, in both cases the PCI device is visible but the driver will not load :(

As these vga cards dont support FLR, would the FLR code when attempting d3r or sbr cause the interrupt corruption ?

Some steer and some assistance would help here, i`m trying to get this working for HVM too !?

BTW: I`m eagerly awaiting Jeremy Fitzhardinge to bring pciback.ko to the modern kernels ! Support for this chipset in 2.6.18 is not very good and i would like to try pvops and PCI passthrough. (although, got a hang with x2apic and IRQ mapping enabled)

I`m willing to help move the development of xen forwards with any testing or assistance you guys need!

Thanks,
Tim
http://www.linkedin.com/in/tmoore




_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
http://lists.xensource.com/xen-devel


[-- Attachment #1.2: Type: text/html, Size: 13642 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: good progress on pci vga passthrough in xen-3.4-rc1

[Stefano Stabellini]

Tim Moore wrote:

> Hi Bryan
> 
>  
> 
> I think my email to Peter along with emails from probably yourself and
> other people in the community is what prompted his reply to xen-users.
> 
>  
> 
> There seems to be a general reluctance to move this forwards within the
> Xen developers, I think this may be due to the current status of some of
> the commercial vendors that are working on the “next big thing” for
> Virtualisation. Neocleus and XCI seem to be the products that will bring
> this to market.. it seems that the open source community may be being
> left out at this stage!?
> 

Come on, XCI sources are fully open source and available on the web!

The plain truth is that graphic card passtrough doesn't always work at
the moment, most of the problems come from the rexecution of the vga
bios (or the lack of thereof).
You can read the workaround we have in place in XCI in
tools/libxc/xc_hvm_build.c:setup_vga_pt, but even that one doesn't work
all the times.

RE: good progress on pci vga passthrough in xen-3.4-rc1

[Tim Moore]

[-- Attachment #1: Type: text/plain, Size: 1704 bytes --]

Hi Stefano,

Thanks for your reply. This is the first time that I have been provided with some pointers where to look.. like I said in previous emails, I can work on this but I didn't write Xen or any of these workarounds!

I also posted the [attached] question about XCI - no one answers :(

Can you help answer?

Thank you again,
Tim

I`m assumingalos, that Citrix Project "Independence" is simply a name for XCI?

-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com] 
Sent: 15 April 2009 10:10
To: Tim Moore
Cc: 'Bryan York'; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1

Tim Moore wrote:

> Hi Bryan
> 
>  
> 
> I think my email to Peter along with emails from probably yourself and
> other people in the community is what prompted his reply to xen-users.
> 
>  
> 
> There seems to be a general reluctance to move this forwards within the
> Xen developers, I think this may be due to the current status of some of
> the commercial vendors that are working on the "next big thing" for
> Virtualisation. Neocleus and XCI seem to be the products that will bring
> this to market.. it seems that the open source community may be being
> left out at this stage!?
> 

Come on, XCI sources are fully open source and available on the web!

The plain truth is that graphic card passtrough doesn't always work at
the moment, most of the problems come from the rexecution of the vga
bios (or the lack of thereof).
You can read the workaround we have in place in XCI in
tools/libxc/xc_hvm_build.c:setup_vga_pt, but even that one doesn't work
all the times.



[-- Attachment #2: Type: message/rfc822, Size: 6901 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 657 bytes --]

Hi J/Ross, Hope you can help ...



Reading the Xen Client Initiative meeting minutes from May 20 2008, it mentions that:



*       Multiple graphics cards are working with recent patches (3 Main vendors)



Do we know which 3x Graphics card vendors are working?



I have built the XCI source from xenbits and whilst using it seems that the VGA card  support is still quite specific ...



Also:

*       Need a list of requests for Bios and Drivers to assist in virtualization of graphics cards



Well, I can start : nVidia 8/9 as a lot of people on the list are trying to set this up with Xen-unstable.



Thanks - Tim


[-- Attachment #2.1.2: Type: text/html, Size: 5045 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: good progress on pci vga passthrough in xen-3.4-rc1

[Keir Fraser]

On 15/04/2009 10:20, "Tim Moore" <timothy.moore@expidas.net> wrote:

> Thanks for your reply. This is the first time that I have been provided with
> some pointers where to look.. like I said in previous emails, I can work on
> this but I didn't write Xen or any of these workarounds!
> 
> I also posted the [attached] question about XCI - no one answers :(

Are there more than three main gfx vendors? ;-)

The passthru has been got working on at least one example of each of ATI,
nVidia and Intel integrated gfx. That doesn't necessarily mean it will work
for your chip, with your BIOS. Getting it working can on some systems be
quite a pain in the arse, even if a developer has local access to the
system.

 -- Keir

Re: good progress on pci vga passthrough in xen-3.4-rc1

[Stefano Stabellini]

Tim Moore wrote:

> Thread-Topic:
> [XCI] Question?
> Thread-Index:
> Acm88go+caOvZEXVSRCK6Iw2iEIE+A==
> Message-ID:
> <14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1F@heavy-vm03.heavy.org.uk>
> Accept-Language:
> en-US
> X-MS-Exchange-Organization-SCL:
> -1
> Content-Type:
> multipart/alternative;
> boundary="_000_14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1Fheavyvm03he_"
> MIME-Version:
> 1.0
> 
> 
> Hi J/Ross, Hope you can help …
> 
>  
> 
> Reading the Xen Client Initiative meeting minutes from May 20 2008, it
> mentions that:
> 
>  
> 
>     * Multiple graphics cards are working with recent patches (3 Main
>       vendors) 
> 
>  
> 
> Do we know which 3x Graphics card vendors are working?
> 
>  
> 
> I have built the XCI source from xenbits and whilst using it seems that
> the VGA card  support is still quite specific …
> 


The VGA support in XCI at the moment is Intel specific.

However videocard passthrough should work OK with most graphic cards if
you passthrought the videocard to the guest as a secondary card (you do
not disable the emulated cirrus vga). The problem with this approach is
that you are not able to see anything on the screen until the guest
enables the secondary card so you may need to configure the guest using
vnc fron another machine, at least the first time.
On the other hand if you disable the emulated vga so the pt graphic card
happers as a primary in the guest, you should be able to see output on
the screen since the beginning of the guest boot sequence, but then you
are going to have more vga bios problems.

RE: good progress on pci vga passthrough in xen-3.4-rc1

[Tim Moore]

Kier,

I have an nvidia nv4 (8800 GTS) and 9500 GT and they do not work under XCI (as primary or secondary cards) and the same problem under xen-rc1. I have also tried ATI cards to no avail.

Will it be possible to get a list of bios + vendors /drivers that have been tested / compatible? I will even offer to maintain the Wiki with such information!!

Cheers,
Tim


-----Original Message-----
From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] 
Sent: 15 April 2009 10:26
To: Tim Moore; Stefano Stabellini
Cc: xen-devel@lists.xensource.com; 'Bryan York'
Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1

On 15/04/2009 10:20, "Tim Moore" <timothy.moore@expidas.net> wrote:

> Thanks for your reply. This is the first time that I have been provided with
> some pointers where to look.. like I said in previous emails, I can work on
> this but I didn't write Xen or any of these workarounds!
> 
> I also posted the [attached] question about XCI - no one answers :(

Are there more than three main gfx vendors? ;-)

The passthru has been got working on at least one example of each of ATI,
nVidia and Intel integrated gfx. That doesn't necessarily mean it will work
for your chip, with your BIOS. Getting it working can on some systems be
quite a pain in the arse, even if a developer has local access to the
system.

 -- Keir

RE: good progress on pci vga passthrough in xen-3.4-rc1

[Tim Moore]

Thanks Stefano,

I have tried all your suggestions with both XCI and Xen-rc1 already to no avail. It works for pv DomU but not HVM.

Disable/enable Cirrus - no effect, tried -std-vga -vga none and all host of combinations. When trying primary, the DomU seems to fail and qemu just quits I think due to no video.

Can I get some dmesg / logs that will help to analyse further?

As I just mentioned to Kier, I'm more than willing to help the community out with this one ;) I have been writing code for Win32 for years, i`m just a bit new to the Xen scene and developing towards the hw.

Cheers,
Tim

-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com] 
Sent: 15 April 2009 10:34
To: Tim Moore
Cc: 'Bryan York'; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1

Tim Moore wrote: 
> Thread-Topic:
> [XCI] Question?
> Thread-Index:
> Acm88go+caOvZEXVSRCK6Iw2iEIE+A==
> Message-ID:
> <14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1F@heavy-vm03.heavy.org.uk>
> Accept-Language:
> en-US
> X-MS-Exchange-Organization-SCL:
> -1
> Content-Type:
> multipart/alternative;
> boundary="_000_14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1Fheavyvm03he_"
> MIME-Version:
> 1.0
> 
> 
> Hi J/Ross, Hope you can help ...
> 
>  
> 
> Reading the Xen Client Initiative meeting minutes from May 20 2008, it
> mentions that:
> 
>  
> 
>     * Multiple graphics cards are working with recent patches (3 Main
>       vendors) 
> 
>  
> 
> Do we know which 3x Graphics card vendors are working?
> 
>  
> 
> I have built the XCI source from xenbits and whilst using it seems that
> the VGA card  support is still quite specific ...
> 


The VGA support in XCI at the moment is Intel specific.

However videocard passthrough should work OK with most graphic cards if
you passthrought the videocard to the guest as a secondary card (you do
not disable the emulated cirrus vga). The problem with this approach is
that you are not able to see anything on the screen until the guest
enables the secondary card so you may need to configure the guest using
vnc fron another machine, at least the first time.
On the other hand if you disable the emulated vga so the pt graphic card
happers as a primary in the guest, you should be able to see output on
the screen since the beginning of the guest boot sequence, but then you
are going to have more vga bios problems.

Re: good progress on pci vga passthrough in xen-3.4-rc1

[Jean Guyader]

Hi Tim,

Here is the current status for the different vendors.

Nvidia graphic cards don't work as primaries, there are some issue
with the bios rexecution.
Nvidia cards should work as a seconday display adapter side by side
with the cirrus.

So far ATI doesn't support vt-d.

Intel graphic card only works as a primary.

Jean

2009/4/15 Tim Moore <timothy.moore@expidas.net>:
> Kier,
>
> I have an nvidia nv4 (8800 GTS) and 9500 GT and they do not work under XCI (as primary or secondary cards) and the same problem under xen-rc1. I have also tried ATI cards to no avail.
>
> Will it be possible to get a list of bios + vendors /drivers that have been tested / compatible? I will even offer to maintain the Wiki with such information!!
>
> Cheers,
> Tim
>
>
> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> Sent: 15 April 2009 10:26
> To: Tim Moore; Stefano Stabellini
> Cc: xen-devel@lists.xensource.com; 'Bryan York'
> Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1
>
> On 15/04/2009 10:20, "Tim Moore" <timothy.moore@expidas.net> wrote:
>
>> Thanks for your reply. This is the first time that I have been provided with
>> some pointers where to look.. like I said in previous emails, I can work on
>> this but I didn't write Xen or any of these workarounds!
>>
>> I also posted the [attached] question about XCI - no one answers :(
>
> Are there more than three main gfx vendors? ;-)
>
> The passthru has been got working on at least one example of each of ATI,
> nVidia and Intel integrated gfx. That doesn't necessarily mean it will work
> for your chip, with your BIOS. Getting it working can on some systems be
> quite a pain in the arse, even if a developer has local access to the
> system.
>
>  -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

Re: good progress on pci vga passthrough in xen-3.4-rc1

[Stefano Stabellini]

Tim Moore wrote:

> Thanks Stefano,
> 
> I have tried all your suggestions with both XCI and Xen-rc1 already to no avail. It works for pv DomU but not HVM.
> 
> Disable/enable Cirrus - no effect, tried -std-vga -vga none and all host of combinations. When trying primary, the DomU seems to fail and qemu just quits I think due to no video.
> 
> Can I get some dmesg / logs that will help to analyse further?
> 
> As I just mentioned to Kier, I'm more than willing to help the community out with this one ;) I have been writing code for Win32 for years, i`m just a bit new to the Xen scene and developing towards the hw.
> 


In this case you are interested in the qemu and xen logs.
For qemu, just open /var/log/xen/qemu-dm-guestname.log; for xen
compile the hypervisor with debug = y (in Config.mk) and keep an eye on
the serial.

RE: [XCI] result of pci vga passthrough

[Tim Moore]

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

Hi Stefano,

Please find attached, logs from XCI and a quick jpg of the WinXP host.

I will compile Xen for XCI with debug if necessary?

Cheers,
Tim

-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com] 
Sent: 15 April 2009 10:50
To: Tim Moore
Cc: 'Bryan York'; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1

Tim Moore wrote:

> Thanks Stefano,
> 
> I have tried all your suggestions with both XCI and Xen-rc1 already to no avail. It works for pv DomU but not HVM.
> 
> Disable/enable Cirrus - no effect, tried -std-vga -vga none and all host of combinations. When trying primary, the DomU seems to fail and qemu just quits I think due to no video.
> 
> Can I get some dmesg / logs that will help to analyse further?
> 
> As I just mentioned to Kier, I'm more than willing to help the community out with this one ;) I have been writing code for Win32 for years, i`m just a bit new to the Xen scene and developing towards the hw.
> 


In this case you are interested in the qemu and xen logs.
For qemu, just open /var/log/xen/qemu-dm-guestname.log; for xen
compile the hypervisor with debug = y (in Config.mk) and keep an eye on
the serial.

[-- Attachment #2: qemu.1 --]
[-- Type: application/octet-stream, Size: 55321 bytes --]

Using domid: 1
Arguments: -d 1 -m 2047 -boot cd -serial pty -vcpus 1 -vncunused -k en-us -net nic,vlan=0,macaddr=00:16:3e:15:60:9a,model=rtl8139 -net tap,vlan=0,bridge=,ifname=tap1.0
domid: 1
qemu: the number of cpus is 1
config qemu network with xen bridge for  tap1.0
Incorrect number of arguments for command
Usage: brctl addif <bridge> <device>	add interface to bridge
Watching /local/domain/0/device-model/1/logdirty/next-active
Watching /local/domain/0/device-model/1/command
screenshot watch node /local/domain/1/screenshot
xs_read(): vncpasswd get error. /vm/00000000-0000-0000-0000-000000000002/vncpasswd.
char device redirected to /dev/pts/0
direct_pci_str: 0000:03:00.00-
qemu_map_cache_init nr_buckets = 4000 size 196608
shared page at pfn 7fefe
buffered io page at pfn 7fefc
Time offset set 0
register_real_device: Assigning real physical device 03:00.0 ...
pt_register_regions: IO region registered (size=0x01000000 base_addr=0xb2000000)
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe0000000)
pt_register_regions: IO region registered (size=0x02000000 base_addr=0xb0000000)
pt_register_regions: IO region registered (size=0x00000080 base_addr=0x00001000)
register_real_device: Real device vendor_id=0x10de class=0x300
register_real_device: Real physical device 03:00.0 registered successfuly!
Register xen platform.
Done register platform.
xs_read(/local/domain/0/device-model/1/xen_extended_power_mgmt): read error
xs_read(/local/domain/0/device-model/1/oem_features): read error
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_read(/local/domain/1/screenshot): read error
pt_pci_read_config: [00:02.0]: address=000a val=0x00000300 len=2
pt_pci_read_config: [00:02.0]: address=0000 val=0x000010de len=2
pt_pci_read_config: [00:02.0]: address=0002 val=0x00000600 len=2
pt_pci_read_config: [00:02.0]: address=0010 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=0010 val=0xffffffff len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xff000000 len=4
pt_pci_write_config: [00:02.0]: address=0010 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0x0000000c len=4
pt_pci_write_config: [00:02.0]: address=0014 val=0xffffffff len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xf000000c len=4
pt_pci_write_config: [00:02.0]: address=0014 val=0x0000000c len=4
pt_pci_read_config: [00:02.0]: address=001c val=0x00000004 len=4
pt_pci_write_config: [00:02.0]: address=001c val=0xffffffff len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xfe000004 len=4
pt_pci_write_config: [00:02.0]: address=001c val=0x00000004 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x00000001 len=4
pt_pci_write_config: [00:02.0]: address=0024 val=0xffffffff len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0xffffff81 len=4
pt_pci_write_config: [00:02.0]: address=0024 val=0x00000001 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xfffe0000 len=4
pt_pci_write_config: [00:02.0]: address=0030 val=0xffffffff len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xfffe0001 len=4
pt_pci_write_config: [00:02.0]: address=0030 val=0xfffe0000 len=4
pt_pci_write_config: Guest attempt to set address to unused Base Address Register. [00:02.0][Offset:30h][Length:4]
pt_pci_read_config: [00:02.0]: address=003d val=0x00000001 len=1
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
pt_pci_read_config: [00:02.0]: address=0014 val=0x0000000c len=4
pt_pci_write_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00000000 len=2
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000002 len=2
pt_iomem_map: e_phys=c0000000 maddr=e0000000 type=8 len=268435456 index=1 first_map=1
pt_pci_read_config: [00:02.0]: address=001c val=0x00000004 len=4
pt_pci_write_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00000002 len=2
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000002 len=2
pt_iomem_map: e_phys=d0000000 maddr=b0000000 type=0 len=33554432 index=3 first_map=1
pt_pci_read_config: [00:02.0]: address=0010 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00000002 len=2
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000002 len=2
pt_iomem_map: e_phys=d4000000 maddr=b2000000 type=0 len=16777216 index=0 first_map=1
pt_pci_read_config: [00:02.0]: address=0030 val=0xfffe0000 len=4
pt_pci_write_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_write_config: Guest attempt to set address to unused Base Address Register. [00:02.0][Offset:30h][Length:4]
pt_pci_read_config: [00:02.0]: address=0004 val=0x00000002 len=2
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000002 len=2
pt_pci_read_config: [00:02.0]: address=0024 val=0x00000001 len=4
pt_pci_write_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00000002 len=2
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000003 len=2
pt_ioport_map: e_phys=c200 pio_base=1000 len=128 index=5 first_map=1
pt_pci_read_config: [00:02.0]: address=0000 val=0x000010de len=2
pt_pci_read_config: [00:02.0]: address=0002 val=0x00000600 len=2
pt_pci_read_config: [00:02.0]: address=000a val=0x00000300 len=2
pt_pci_read_config: [00:02.0]: address=0000 val=0x000010de len=2
pt_pci_read_config: [00:02.0]: address=0002 val=0x00000600 len=2
stolen video RAM at 7f6f8000
mapping video RAM from 7f6f8000
mapping vram to d2000000 - d2800000
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
XenPCI --> DriverEntry
XenPCI --> XenPci_FixLoadOrder
XenPCI     Current Order:
XenPCI       System Reserved
XenPCI       Dummy Group
XenPCI       WdfLoadGroup
XenPCI       Boot Bus Extender
XenPCI       System Bus Extender
XenPCI       SCSI miniport
XenPCI       Port
XenPCI       Primary Disk
XenPCI       SCSI Class
XenPCI       SCSI CDROM Class
XenPCI       FSFilter Infrastructure
XenPCI       FSFilter System
XenPCI       FSFilter Bottom
XenPCI       FSFilter Copy Protection
XenPCI       FSFilter Security Enhancer
XenPCI       FSFilter Open File
XenPCI       FSFilter Physical Quota Management
XenPCI       FSFilter Encryption
XenPCI       FSFilter Compression
XenPCI       FSFilter HSM
XenPCI       FSFilter Cluster File System
XenPCI       FSFilter System Recovery
XenPCI       FSFilter Quota Management
XenPCI       FSFilter Content Screener
XenPCI       FSFilter Continuous Backup
XenPCI       FSFilter Replication
XenPCI       FSFilter Anti-Virus
XenPCI       FSFilter Undelete
XenPCI       FSFilter Activity Monitor
XenPCI       FSFilter Top
XenPCI       Filter
XenPCI       Boot File System
XenPCI       Base
XenPCI       Pointer Port
XenPCI       Keyboard Port
XenPCI       Pointer Class
XenPCI       Keyboard Class
XenPCI       Video Init
XenPCI       Video
XenPCI       Video Save
XenPCI       File System
XenPCI       Event Log
XenPCI       Streams Drivers
XenPCI       NDIS Wrapper
XenPCI       COM Infrastructure
XenPCI       UIGroup
XenPCI       LocalValidation
XenPCI       PlugPlay
XenPCI       PNP_TDI
XenPCI       NDIS
XenPCI       TDI
XenPCI       NetBIOSGroup
XenPCI       ShellSvcGroup
XenPCI       SchedulerGroup
XenPCI       SpoolerGroup
XenPCI       AudioGroup
XenPCI       SmartCardGroup
XenPCI       NetworkProvider
XenPCI       RemoteValidation
XenPCI       NetDDEGroup
XenPCI       Parallel arbitrator
XenPCI       Extended Base
XenPCI       PCI Configuration
XenPCI       MS Transactions
XenPCI     dummy_group_index = 1
XenPCI     wdf_load_group_index = 2
XenPCI     boot_bus_extender_index = 3
XenPCI     SystemStartOptions = NOEXECUTE=OPTIN  FASTDETECT
XenPCI     Version = 0
region type 1 at [c100,c200).
region type 0 at [d6021000,d6021100).
XenPCI     Disabled qemu devices
XenPCI     PV Devices Active
XenPCI <-- DriverEntry
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x000010de len=2
pt_pci_read_config: [00:02.0]: address=0002 val=0x00000600 len=2
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0060 val=0x00006801 len=2
pt_pci_read_config: [00:02.0]: address=0062 val=0x00000003 len=2
pt_pci_read_config: [00:02.0]: address=0064 val=0x00000008 len=4
pt_pci_read_config: [00:02.0]: address=0060 val=0x00006801 len=2
pt_pci_read_config: [00:02.0]: address=0062 val=0x00000003 len=2
pt_pci_read_config: [00:02.0]: address=0064 val=0x00000008 len=4
pt_pci_write_config: [00:02.0]: address=0064 val=0x00000008 len=2
pt_pci_read_config: [00:02.0]: address=0064 val=0x00000008 len=2
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_write_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000000 len=4
pt_iomem_map: e_phys=ffffffff maddr=b2000000 type=0 len=16777216 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=e0000000 type=8 len=268435456 index=1 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=b0000000 type=0 len=33554432 index=3 first_map=0
pt_ioport_map: e_phys=ffff pio_base=1000 len=128 index=5 first_map=0
pt_pci_write_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_write_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=0010 val=0xffffffff len=4
pt_pci_write_config: [00:02.0]: address=0014 val=0xffffffff len=4
pt_pci_write_config: [00:02.0]: address=0018 val=0xffffffff len=4
pt_pci_write_config: [00:02.0]: address=001c val=0xffffffff len=4
pt_pci_write_config: [00:02.0]: address=0020 val=0xffffffff len=4
pt_pci_write_config: [00:02.0]: address=0024 val=0xffffffff len=4
pt_pci_write_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_write_config: [00:02.0]: address=0030 val=0xfffff800 len=4
pt_pci_write_config: Guest attempt to set address to unused Base Address Register. [00:02.0][Offset:30h][Length:4]
pt_pci_write_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_write_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100000 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xff000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xf000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0xffffffff len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xfe000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0xffffffff len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0xffffff81 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xfffe0000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_write_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_write_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_write_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_write_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_write_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_write_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_write_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_write_config: Guest attempt to set address to unused Base Address Register. [00:02.0][Offset:30h][Length:4]
pt_pci_write_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_write_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000003 len=2
pt_iomem_map: e_phys=d4000000 maddr=b2000000 type=0 len=16777216 index=0 first_map=0
pt_iomem_map: e_phys=c0000000 maddr=e0000000 type=8 len=268435456 index=1 first_map=0
pt_iomem_map: e_phys=d0000000 maddr=b0000000 type=0 len=33554432 index=3 first_map=0
pt_ioport_map: e_phys=c200 pio_base=1000 len=128 index=5 first_map=0
pt_pci_read_config: [00:02.0]: address=0060 val=0x00006801 len=2
pt_pci_read_config: [00:02.0]: address=0062 val=0x00000003 len=2
pt_pci_read_config: [00:02.0]: address=0064 val=0x00000008 len=4
pt_pci_write_config: [00:02.0]: address=0064 val=0x00000008 len=2
pt_pci_read_config: [00:02.0]: address=0064 val=0x00000008 len=2
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00000003 len=2
XenPCI --> XenPci_EvtDeviceAdd
XenPCI <-- XenPci_EvtDeviceAdd
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
XenPCI --> XenPci_EvtDevicePrepareHardware
XenPCI     IoPort Address(c000) Length: 256
XenPCI     Private Data: 0x01 0x00 0x00
XenPCI     Memory mapped CSR:(d5000000:0) Length:(16777216)
XenPCI     Memory flags = 0004
XenPCI     Private Data: 0x01 0x01 0x00
XenPCI     irq_number = 00b
XenPCI     irq_vector = 03b
XenPCI     irq_level = 010
XenPCI     irq_mode = LevelSensitive
XenPCI     ShareDisposition = CmResourceShareShared
XenPCI <-- XenPci_EvtDevicePrepareHardware
XenPCI --> XenPci_EvtDeviceD0Entry
XenPCI     WdfPowerDeviceD3Final
XenPCI --> XenPci_Init
XenPCI     base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000002
XenPCI     Hypercall area at 89C4C000
XenPCI     pfn =             9E4C
XenPCI     shared_info_area_unmapped.QuadPart = d5000000
XenPCI     gpfn = d5000
XenPCI     hypervisor memory op (XENMAPSPACE_shared_info) ret = 0
XenPCI <-- XenPci_Init
XenPCI --> GntTbl_Init
XenPCI     grant_frames = 32
XenPCI     grant_entries = 16384
XenPCI <-- GntTbl_Init
XenPCI --> EvtChn_Init
XenPCI --> hvm_set_parameter
XenPCI HYPERVISOR_hvm_op retval = 0
XenPCI <-- hvm_set_parameter
XenPCI     hvm_set_parameter(HVM_PARAM_CALLBACK_IRQ, 11) = 0
XenPCI --> EvtChn_AllocIpi
XenPCI <-- EvtChn_AllocIpi
XenPCI --> EvtChn_BindDpc
XenPCI <-- EvtChn_BindDpc
XenPCI     pdo_event_channel = 4
XenPCI <-- EvtChn_Init
XenPCI <-- XenPci_EvtDeviceD0Entry
XenPCI --> EvtChn_EvtInterruptEnable
XenPCI <-- EvtChn_EvtInterruptEnable
XenPCI --> XenPci_EvtDeviceD0EntryPostInterruptsEnabled
XenPCI --> XenBus_Init
XenPCI --> hvm_get_parameter
XenPCI HYPERVISOR_hvm_op retval = 0
XenPCI <-- hvm_get_parameter
XenPCI --> hvm_get_parameter
XenPCI HYPERVISOR_hvm_op retval = 0
XenPCI <-- hvm_get_parameter
XenPCI --> EvtChn_BindDpc
XenPCI <-- EvtChn_BindDpc
XenPCI <-- XenBus_Init
XenPCI --> XenPci_SysrqHandler
XenPCI     SysRq Value = (null)
XenPCI <-- XenPci_SysrqHandler
XenPCI --> XenPci_ShutdownHandler
Error reading shutdown path - ENOENT
XenPCI <-- XenPci_ShutdownHandler
XenPCI <-- XenPci_EvtDeviceD0EntryPostInterruptsEnabled
XenPCI --> XenPci_EvtChildListScanForChildren
XenPCI <-- XenPci_EvtChildListScanForChildren
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI     device = 'vbd', index = '768', path = 'device/vbd/768'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI     device = 'vif', index = '0', path = 'device/vif/0'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI     device = 'pci', index = '0', path = 'device/pci/0'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenHide --> DriverEntry
XenHide <-- DriverEntry
XenHide --> XenHide_AddDevice
XenHide     ZwOpenDirectoryObject = c0000034
XenHide <-- XenHide_AddDevice (filter not required for Intel(R) 82371SB PCI Bus Master IDE Controller)
XenVbd --> DriverEntry
XenVbd     IRQL = 0
XenVbd     DriverObject = 89C38550, RegistryPath = 80093A00
XenVbd <-- DriverEntry
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for Xen Block Device Driver)
XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
XenPCI     device/vbd/768
XenPCI     CmResourceTypeMemory (0)
XenPCI     Start = d5000000, Length = 0
XenPCI     pfn[0] = 0000a9c0
XenPCI     New Start = 000000000a9c0000, Length = 4096
XenPCI     CmResourceTypeMemory (1)
XenPCI     Start = d5000001, Length = 0
XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
XenPCI --> XenPciPdo_EvtDevicePrepareHardware
XenPCI <-- XenPciPdo_EvtDevicePrepareHardware
XenPCI --> XenPciPdo_EvtDeviceD0Entry
XenPCI     WdfPowerDeviceD3Final
XenPCI --> XenConfig_InitConfigPage
XenPCI     fdo_driver_object = 89C38550
XenPCI     fdo_driver_extension = 89BB3008
XenPCI <-- XenConfig_InitConfigPage
XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
XenPCI     testing path = device/vbd/768/device-type
XenPCI     testing disk vs disk
XenPCI     condition = 0
XenPCI     Backend State Changed to InitWait (/local/domain/0/backend/vbd/1/768/state)
XenPCI --> EvtChn_BindIrq
XenPCI <-- EvtChn_BindIrq
XenPCI     Backend State Changed to Connected (/local/domain/0/backend/vbd/1/768/state)
XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
XenPCI <-- XenPciPdo_EvtDeviceD0Entry
XenVbd --> XenVbd_HwScsiFindAdapter
XenVbd     IRQL = 0
XenVbd     xvdd = 89BB0004
XenVbd     BusInterruptLevel = 11
XenVbd     BusInterruptVector = 00b
XenVbd     NumberOfAccessRanges = 1
XenVbd     RangeStart = 0a9c0000, RangeLength = 00001000
XenVbd     XEN_INIT_TYPE_VECTORS
XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 89C3BA5C
XenVbd     XEN_INIT_TYPE_RING - ring-ref = 89BB2000
XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 5
XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
XenVbd     device-type = Disk
XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
XenVbd     mode = w
XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 79691776
XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
XenVbd     Dma64BitAddresses not supported
XenVbd <-- XenVbd_HwScsiFindAdapter
XenPCI --> XenPci_BIS_GetDmaAdapter
XenPCI     IRQL = 0
XenPCI     Device Description = BA4C70C0:
XenPCI      Version  = 0
XenPCI      Master = 1
XenPCI      ScatterGather = 1
XenPCI      DemandMode = 0
XenPCI      AutoInitialize = 0
XenPCI      Dma32BitAddresses = 1
XenPCI      IgnoreCount = 0
XenPCI      Dma64BitAddresses = 0
XenPCI      BusNumber = 0
XenPCI      DmaChannel = -1
XenPCI      InterfaceType = 15
XenPCI      DmaWidth = 0
XenPCI      DmaSpeed = 0
XenPCI      MaximumLength = 45056
XenPCI      DmaPort = -1
XenPCI     About to call IoGetAttachedDeviceReference
XenPCI     Before start of loop - curr = 89C37030
XenPCI     End of loop
XenPCI <-- XenPci_BIS_GetDmaAdapter
XenVbd --> XenVbd_HwScsiInitialize
XenVbd     IRQL = 16
XenVbd     dump_mode = 0
XenVbd <-- XenVbd_HwScsiInitialize
XenVbd --> XenVbd_HwScsiAdapterControl
XenVbd     IRQL = 0
XenVbd     ScsiQuerySupportedControlTypes (Max = 5)
XenVbd <-- XenVbd_HwScsiAdapterControl
XenVbd --- HwScsiStartIo (Still figuring out ring)
XenVbd     ring_detect_state = 0, operation = ff, id = 0, status = 0
XenVbd     ring_detect_state = 1, operation = ff, id = 0, status = 0
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for Primary IDE Channel)
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for Secondary IDE Channel)
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
XenVbd     SRB_FUNCTION_IO_CONTROL
XenVbd     SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 28, allocation_length = 192
XenVbd     EXECUTE_SCSI Command = 1A returned error 00
XenVbd     SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192
XenVbd     SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 12
XenPCI --> XenPci_EvtDeviceUsageNotification
XenPCI     notification_type = Paging, flag = 1
XenPCI <-- XenPci_EvtDeviceUsageNotification
XenPCI --> XenPciPdo_EvtDeviceUsageNotification
XenPCI     path = device/vbd/768
XenPCI     notification_type = Paging, flag = 1
XenPCI <-- XenPciPdo_EvtDeviceUsageNotification
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for WAN Miniport (L2TP))
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for WAN Miniport (IP))
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for WAN Miniport (PPPOE))
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for WAN Miniport (PPTP))
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for Packet Scheduler Miniport)
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for Packet Scheduler Miniport)
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for Packet Scheduler Miniport)
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for Packet Scheduler Miniport)
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for Direct Parallel)
XenNet --> DriverEntry
XenNet     DriverObject = 89A89A30, RegistryPath = 89983000
XenNet     NdisGetVersion = 50001
XenNet     ndis_wrapper_handle = 00000000
XenNet     ndis_wrapper_handle = 89A896B8
XenNet     NdisMInitializeWrapper succeeded
XenNet     MajorNdisVersion = 5,  MinorNdisVersion = 1
XenNet     about to call NdisMRegisterMiniport
XenNet     called NdisMRegisterMiniport
XenNet <-- DriverEntry
XenHide --> XenHide_AddDevice
XenHide <-- XenHide_AddDevice (filter not required for Xen Net Device Driver)
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100003 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_write_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000000 len=4
pt_iomem_map: e_phys=ffffffff maddr=b2000000 type=0 len=16777216 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=e0000000 type=8 len=268435456 index=1 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=b0000000 type=0 len=33554432 index=3 first_map=0
pt_ioport_map: e_phys=ffff pio_base=1000 len=128 index=5 first_map=0
pt_pci_write_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_write_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_write_config: [00:02.0]: address=0014 val=0xc0000000 len=4
pt_pci_write_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=001c val=0xd0000000 len=4
pt_pci_write_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=0024 val=0x0000c200 len=4
pt_pci_write_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_write_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_write_config: Guest attempt to set address to unused Base Address Register. [00:02.0][Offset:30h][Length:4]
pt_pci_write_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_write_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_write_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_write_config: [00:02.0]: address=0004 val=0x00000007 len=2
pt_iomem_map: e_phys=d4000000 maddr=b2000000 type=0 len=16777216 index=0 first_map=0
pt_iomem_map: e_phys=c0000000 maddr=e0000000 type=8 len=268435456 index=1 first_map=0
pt_iomem_map: e_phys=d0000000 maddr=b0000000 type=0 len=33554432 index=3 first_map=0
pt_ioport_map: e_phys=c200 pio_base=1000 len=128 index=5 first_map=0
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0000 val=0x060010de len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00100007 len=4
pt_pci_read_config: [00:02.0]: address=0008 val=0x030000a2 len=4
pt_pci_read_config: [00:02.0]: address=000c val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0010 val=0xd4000000 len=4
pt_pci_read_config: [00:02.0]: address=0014 val=0xc000000c len=4
pt_pci_read_config: [00:02.0]: address=0018 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=001c val=0xd0000004 len=4
pt_pci_read_config: [00:02.0]: address=0020 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=0024 val=0x0000c201 len=4
pt_pci_read_config: [00:02.0]: address=0028 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=002c val=0x071919f1 len=4
pt_pci_read_config: [00:02.0]: address=0030 val=0xd6000000 len=4
pt_pci_read_config: [00:02.0]: address=0034 val=0x00000060 len=4
pt_pci_read_config: [00:02.0]: address=0038 val=0x00000000 len=4
pt_pci_read_config: [00:02.0]: address=003c val=0x0000010b len=4
pt_pci_read_config: [00:02.0]: address=0004 val=0x00000007 len=2
XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
XenPCI     device/vif/0
XenPCI     CmResourceTypeMemory (0)
XenPCI     Start = d5000000, Length = 0
XenPCI     pfn[0] = 0000aa00
XenPCI     New Start = 000000000aa00000, Length = 4096
XenPCI     CmResourceTypeMemory (1)
XenPCI     Start = d5000001, Length = 0
XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
XenPCI --> XenPciPdo_EvtDevicePrepareHardware
XenPCI <-- XenPciPdo_EvtDevicePrepareHardware
XenPCI --> XenPciPdo_EvtDeviceD0Entry
XenPCI     WdfPowerDeviceD3Final
XenPCI --> XenConfig_InitConfigPage
XenPCI     fdo_driver_object = 89A89A30
XenPCI     fdo_driver_extension = 00000000
XenPCI     fdo_driver_object = 89C50928
XenPCI     fdo_driver_extension = 00000000
XenPCI <-- XenConfig_InitConfigPage
XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
XenPCI <-- XenPciPdo_EvtDeviceD0Entry
XenNet --> XenNet_Init
XenNet     IRQL = 0
XenNet     NdisReadPciSlotInformation = 0
XenNet     nrl_length = 40
XenNet     irq_vector = 00b, irq_level = 00b, irq_mode = NdisInterruptLevelSensitive
XenNet     XEN_INIT_TYPE_13
XenNet     XEN_INIT_TYPE_VECTORS
XenNet     XEN_INIT_TYPE_DEVICE_STATE - 89BB7C44
XenNet     XEN_INIT_TYPE_ACTIVE
ScatterGather = 1
LargeSendOffload = 61440
ChecksumOffload = 1
ChecksumOffloadRxCheck = 1
MTU = 1500
RxInterruptModeration = 0
Could not read NetworkAddress value (c0000001)
XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
XenPCI     Backend State Changed to InitWait (/local/domain/0/backend/vif/1/0/state)
XenPCI --> EvtChn_Bind
XenPCI <-- EvtChn_Bind
XenPCI     Backend State Changed to Connected (/local/domain/0/backend/vif/1/0/state)
XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
XenNet --> XenNet_ConnectBackend
XenNet     XEN_INIT_TYPE_13
XenNet     XEN_INIT_TYPE_VECTORS
XenNet     XEN_INIT_TYPE_DEVICE_STATE - 89BB7C44
XenNet     XEN_INIT_TYPE_RING - tx-ring-ref = 8995A000
XenNet     XEN_INIT_TYPE_RING - rx-ring-ref = 89959000
XenNet     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 6
XenNet     XEN_INIT_TYPE_12
XenNet <-- XenNet_ConnectBackend
XenPCI --> XenPci_BIS_GetDmaAdapter
XenPCI     IRQL = 0
XenPCI     Device Description = BA50362C:
XenPCI      Version  = 2
XenPCI      Master = 1
XenPCI      ScatterGather = 1
XenPCI      DemandMode = 0
XenPCI      AutoInitialize = 0
XenPCI      Dma32BitAddresses = 0
XenPCI      IgnoreCount = 0
XenPCI      Dma64BitAddresses = 1
XenPCI      BusNumber = 0
XenPCI      DmaChannel = 0
XenPCI      InterfaceType = 0
XenPCI      DmaWidth = 0
XenPCI      DmaSpeed = 0
XenPCI      MaximumLength = 122880
XenPCI      DmaPort = 0
XenPCI     About to call IoGetAttachedDeviceReference
XenPCI     Before start of loop - curr = 89983030
XenPCI     End of loop
XenPCI <-- XenPci_BIS_GetDmaAdapter
XenPCI --> XenPci_DOP_CalculateScatterGatherList
XenPCI     Mdl = 00000000
XenPCI     CurrentVa = 00000000
XenPCI     Length = 69632
XenPCI     ScatterGatherListSize = 300, NumberOfMapRegisters = 17
XenPCI <-- XenPci_DOP_CalculateScatterGatherList
XenNet --> XenNet_RxInit
XenNet <-- XenNet_RxInit
XenNet <-- XenNet_Init
Get Unknown OID 0x10202
Get Unknown OID 0xfd010100
XenNet XenNet_PnPEventNotify called (line 671)
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
Get Unknown OID 0x10202
Get Unknown OID 0xfd010100
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
pt_pci_write_config: [00:02.0]: address=003c val=0x0000000b len=1
Get Unknown OID 0x10201
Get Unknown OID 0xfc010210
Get OID_TCP_TASK_OFFLOAD
XenNet     (BUFFER_TOO_SHORT 100 > 28)
Get OID_TCP_TASK_OFFLOAD
config_csum enabled
nto = 89A516DC
nto->Size = 24
nto->TaskBufferLength = 16
config_gso enabled
nto = 89A51700
nto->Size = 24
nto->TaskBufferLength = 16
&(nttls->IpOptions) = 89A51721
Set OID_TCP_TASK_OFFLOAD
TcpIpChecksumNdisTask
  V4Transmit.IpOptionsSupported  = 0
  V4Transmit.TcpOptionsSupported = 1
  V4Transmit.TcpChecksum         = 1
  V4Transmit.UdpChecksum         = 0
  V4Transmit.IpChecksum          = 0
  V4Receive.IpOptionsSupported   = 0
  V4Receive.TcpOptionsSupported  = 0
  V4Receive.TcpChecksum          = 1
  V4Receive.UdpChecksum          = 0
  V4Receive.IpChecksum           = 0
  V6Transmit.IpOptionsSupported  = 0
  V6Transmit.TcpOptionsSupported = 0
  V6Transmit.TcpChecksum         = 0
  V6Transmit.UdpChecksum         = 0
  V6Receive.IpOptionsSupported   = 0
  V6Receive.TcpOptionsSupported  = 0
  V6Receive.TcpChecksum          = 0
  V6Receive.UdpChecksum          = 0
TcpLargeSendNdisTask
  MaxOffLoadSize                 = 61440
  MinSegmentCount                = 4
  TcpOptions                     = 0
  IpOptions                      = 0
Get Unknown OID 0xfd010100
Set Unknown OID 0x10119
Set OID_GEN_CURRENT_LOOKAHEAD 128
Set OID_GEN_CURRENT_PACKET_FILTER
  NDIS_PACKET_TYPE_DIRECTED
  NDIS_PACKET_TYPE_MULTICAST
  NDIS_PACKET_TYPE_BROADCAST
XenNet     (BUFFER_TOO_SHORT 140 > 0)
Get Unknown OID 0x10117
XenNet     (BUFFER_TOO_SHORT 140 > 0)
XenPCI --> XenPci_EvtDeviceUsageNotification
XenPCI     notification_type = Paging, flag = 1
XenPCI <-- XenPci_EvtDeviceUsageNotification
XenPCI --> XenPciPdo_EvtDeviceUsageNotification
XenPCI     path = device/vbd/768
XenPCI     notification_type = Paging, flag = 1
XenPCI <-- XenPciPdo_EvtDeviceUsageNotification
XenPCI --> XenPci_EvtDeviceUsageNotification
XenPCI     notification_type = Dump, flag = 1
XenPCI <-- XenPci_EvtDeviceUsageNotification
XenPCI --> XenPciPdo_EvtDeviceUsageNotification
XenPCI     path = device/vbd/768
XenPCI     notification_type = Dump, flag = 1
XenPCI <-- XenPciPdo_EvtDeviceUsageNotification
XenNet     (BUFFER_TOO_SHORT 140 > 0)
XenNet     (BUFFER_TOO_SHORT 140 > 0)
Set Unknown OID 0x10118
Set Unknown OID 0xfd010103
Set Unknown OID 0xfd010103
     Set OID_802_3_MULTICAST_LIST
       Length = 6
       Entries = 1
XenPCI --> XenPci_EvtDeviceFileCreate
XenPCI <-- XenPci_EvtDeviceFileCreate
XenPCI --> XenPci_EvtIoWrite
XenPCI     35 bytes of write buffer remaining
XenPCI     completing request with length 35
XenPCI <-- XenPci_EvtIoWrite
XenPCI --> XenPci_EvtIoRead
XenPCI     found pending read
XenPCI <-- XenPci_ProcessReadRequest
XenPCI <-- XenPci_EvtIoRead
XenPCI --> XenPci_EvtIoRead
XenPCI     no data to read
XenPCI <-- XenPci_EvtIoRead
XenPCI --> XenPci_IoWatch
XenPCI     found pending read - MinorFunction = 0, length = 1024
XenPCI <-- XenPci_ProcessReadRequest
XenPCI <-- XenPci_IoWatch
XenPCI --> XenPci_EvtIoWrite
XenPCI     33 bytes of write buffer remaining
XenPCI --> XenBus_Raw
XenPCI <-- XenBus_Raw
XenPCI     completing request with length 33
XenPCI <-- XenPci_EvtIoWrite
XenPCI --> XenPci_EvtIoRead
XenPCI     found pending read
XenPCI <-- XenPci_ProcessReadRequest
XenPCI <-- XenPci_EvtIoRead
XenPCI --> XenPci_EvtIoRead
XenPCI     no data to read
XenPCI <-- XenPci_EvtIoRead
Set Unknown OID 0xfd010103
Get Unknown OID 0xd010108
     Set OID_802_3_MULTICAST_LIST
       Length = 12
       Entries = 2
Get Unknown OID 0xd010108
Get Unknown OID 0xd010108

[-- Attachment #3: xci-dmesg.log --]
[-- Type: application/octet-stream, Size: 6517 bytes --]

(XEN) Bad console= option 'tty0'
 __  __            _____ _  _                      _        _     _      
 \ \/ /___ _ __   |___ /| || |     _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \    |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | |  ___) |__   _|__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_) |_|     \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                         
(XEN) Xen version 3.4-unstable (root@[unknown]) (gcc version 4.2.4) Sun Apr  5 22:17:25 UTC 2009
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: console=tty0 dom0_mem=128M iommu=required iommu_inclusive_mapping=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000008f000 (usable)
(XEN)  000000000008f000 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000aca5c000 (usable)
(XEN)  00000000aca5c000 - 00000000acd61000 (ACPI NVS)
(XEN)  00000000acd61000 - 00000000af6bd000 (usable)
(XEN)  00000000af6bd000 - 00000000af6bf000 (reserved)
(XEN)  00000000af6bf000 - 00000000af715000 (usable)
(XEN)  00000000af715000 - 00000000af7bf000 (ACPI NVS)
(XEN)  00000000af7bf000 - 00000000af7e7000 (usable)
(XEN)  00000000af7e7000 - 00000000af7ff000 (ACPI data)
(XEN)  00000000af7ff000 - 00000000af800000 (usable)
(XEN)  00000000af800000 - 00000000b0000000 (reserved)
(XEN)  00000000f8000000 - 00000000fd000000 (reserved)
(XEN)  00000000ffe00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 00000001d0000000 (usable)
(XEN) System RAM: 6131MB (6278936kB)
(XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL )
(XEN) ACPI: XSDT AF7FE120, 006C (r1 INTEL  DX58SO        DB0       1000013)
(XEN) ACPI: FACP AF7FD000, 00F4 (r3 INTEL  DX58SO        DB0 MSFT  100000D)
(XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126]
(XEN) ACPI: DSDT AF7F8000, 45D9 (r2 INTEL  DX58SO        DB0 MSFT  100000D)
(XEN) ACPI: FACS AF728000, 0040
(XEN) ACPI: APIC AF7F7000, 0138 (r2 INTEL  DX58SO        DB0 MSFT  100000D)
(XEN) ACPI: WDDT AF7F6000, 0040 (r1 INTEL  DX58SO        DB0 MSFT  100000D)
(XEN) ACPI: MCFG AF7F5000, 003C (r1 INTEL  DX58SO        DB0 MSFT  100000D)
(XEN) ACPI: ASF! AF7F4000, 00AC (r32 INTEL  DX58SO        DB0 MSFT  100000D)
(XEN) ACPI: SSDT AF7EA000, 70AC (r1 INTEL  SSDT  PM      DB0 MSFT  100000D)
(XEN) ACPI: DMAR AF7E7000, 0140 (r1 INTEL  DX58SO        DB0 MSFT  100000D)
(XEN) ACPI: WDTT AF7F2000, 020C (r2 INTEL  DX58SO        DB0 MSFT  100000D)
(XEN) ACPI: ASPT AF7F3000, 0034 (r4 INTEL  PerfTune      DB0 MSFT  100000D)
(XEN) Xen heap: 14MB (14532kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:10 APIC version 21
(XEN) Processor #2 7:10 APIC version 21
(XEN) Processor #4 7:10 APIC version 21
(XEN) Processor #6 7:10 APIC version 21
(XEN) Processor #1 7:10 APIC version 21
(XEN) Processor #3 7:10 APIC version 21
(XEN) Processor #5 7:10 APIC version 21
(XEN) Processor #7 7:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Intel VT-d has been enabled
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2666.799 MHz processor.
(XEN) VMX: EPT is available.
(XEN) VMX: VPID is available.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) CPU0: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz stepping 04
(XEN) Booting processor 1/2 eip 8c000
(XEN) CPU1: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz stepping 04
(XEN) Booting processor 2/4 eip 8c000
(XEN) CPU2: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz stepping 04
(XEN) Booting processor 3/6 eip 8c000
(XEN) CPU3: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz stepping 04
(XEN) Booting processor 4/1 eip 8c000
(XEN) CPU4: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz stepping 04
(XEN) Booting processor 5/3 eip 8c000
(XEN) CPU5: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz stepping 04
(XEN) Booting processor 6/5 eip 8c000
(XEN) CPU6: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz stepping 04
(XEN) Booting processor 7/7 eip 8c000
(XEN) CPU7: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz stepping 04
(XEN) Total of 8 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 8 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Brought up 8 CPUs
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) [VT-D]iommu.c:1291:d32767 domain_context_mapping:invalid
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc056e000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   00000001c8000000->00000001c9000000 (28672 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: 00000000c0100000->00000000c056e000
(XEN)  Init. ramdisk: 00000000c056e000->00000000c07fea00
(XEN)  Phys-Mach map: 00000000c07ff000->00000000c081f000
(XEN)  Start info:    00000000c081f000->00000000c081f4a4
(XEN)  Page tables:   00000000c0820000->00000000c082c000
(XEN)  Boot stack:    00000000c082c000->00000000c082d000
(XEN)  TOTAL:         00000000c0000000->00000000c0c00000
(XEN)  ENTRY ADDRESS: 00000000c0100000
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Scrubbing Free RAM: ...........................................................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 108kB init memory.


[-- Attachment #4: XCI-HVM.JPG --]
[-- Type: image/jpeg, Size: 48324 bytes --]

[-- Attachment #5: xenvm-debug-00000000-0000-0000-0000-000000000002 --]
[-- Type: application/octet-stream, Size: 5409 bytes --]

[20090415 05:13:17.323|info|xenvm] stale socket left by previous xenvm. removing
[20090415 05:13:17.323|info|vmact] sending notification ping
[20090415 05:13:17.324|debug|xenops] Regenerating the xenstored tree under: [/local/domain/1]
[20090415 05:13:17.326|debug|xenops] Created domain with id: 1
[20090415 05:13:17.326|info|vmact] sending notification vm:state:created
[20090415 05:13:17.331|debug|xenops] build_pre domid=1; mem=2105140 KiB; shadow=18432 KiB (18 MiB)
[20090415 05:13:17.332|debug|xenguesthelper] connect: args = [ -mode hvm_build -domid 1 -store_port 2 -image /usr/lib/xen/boot/hvmloader -memsize 2047 -vcpus 1 -pae true -apic false -acpi false -nx false -smbios_pt false -acpi_pt false -viridian false -fork true ]
[20090415 05:13:17.379|debug|xenguesthelper] VIRTUAL MEMORY ARRANGEMENT:\n  Loader:        
[20090415 05:13:17.379|debug|xenguesthelper] 0000000000100000->00000000001515d0\n  TOTAL:         
[20090415 05:13:17.379|debug|xenguesthelper] 0000000000000000->000000007ff00000\n  ENTRY ADDRESS: 
[20090415 05:13:17.379|debug|xenguesthelper] 0000000000100000\n
[20090415 05:13:17.499|debug|xenops] Read [524029]
[20090415 05:13:17.500|debug|xenops] Device.Vbd.add (virtpath=hda | physpath=/dev/xenclient/storage | phystype=phys)
[20090415 05:13:17.500|debug|xenops] adding device  B0[/local/domain/0/backend/vbd/1/768]  F1[/local/domain/1/device/vbd/768]  H[/xapi/1/hotplug/vbd/768]
[20090415 05:13:17.504|debug|hotplug] Hotplug.wait_for_plug: frontend (domid=1 | kind=vbd | devid=768); backend (domid=0 | kind=vbd | devid=768)
[20090415 05:13:17.504|debug|xenops] watch: watching xenstore paths: [ /xapi/1/hotplug/vbd/768/hotplug ] with timeout 1200.000000 seconds
[20090415 05:13:17.504|debug|xenops] watch: fired on /xapi/1/hotplug/vbd/768/hotplug
[20090415 05:13:17.516|debug|xenops] watch: fired on /xapi/1/hotplug/vbd/768/hotplug
[20090415 05:13:17.516|debug|xenops] watch: value has appeared: /xapi/1/hotplug/vbd/768/hotplug = online
[20090415 05:13:17.516|debug|xenops] watch: Successfully finished watching xenstore after 0.012476 seconds
[20090415 05:13:17.516|debug|hotplug] Synchronised ok with hotplug script: frontend (domid=1 | kind=vbd | devid=768); backend (domid=0 | kind=vbd | devid=768)
[20090415 05:13:17.516|debug|xenops] Device.Vif.add domid=1 devid=0 mac=00:16:3e:15:60:9a rate=none
[20090415 05:13:17.516|debug|xenops] adding device  B0[/local/domain/0/backend/vif/1/0]  F1[/local/domain/1/device/vif/0]  H[/xapi/1/hotplug/vif/0]
[20090415 05:13:17.518|debug|hotplug] Hotplug.wait_for_plug: frontend (domid=1 | kind=vif | devid=0); backend (domid=0 | kind=vif | devid=0)
[20090415 05:13:17.518|debug|xenops] watch: watching xenstore paths: [ /xapi/1/hotplug/vif/0/hotplug ] with timeout 1200.000000 seconds
[20090415 05:13:17.518|debug|xenops] watch: fired on /xapi/1/hotplug/vif/0/hotplug
[20090415 05:13:17.535|debug|xenops] watch: fired on /xapi/1/hotplug/vif/0/hotplug
[20090415 05:13:17.535|debug|xenops] watch: value has appeared: /xapi/1/hotplug/vif/0/hotplug = online
[20090415 05:13:17.535|debug|xenops] watch: Successfully finished watching xenstore after 0.017563 seconds
[20090415 05:13:17.536|debug|hotplug] Synchronised ok with hotplug script: frontend (domid=1 | kind=vif | devid=0); backend (domid=0 | kind=vif | devid=0)
[20090415 05:13:17.536|debug|netman] Adding vif1.0 to bridge xenbr0
[20090415 05:13:17.541|debug|xenops] pci add mem bar b2000000-b2ffffff
[20090415 05:13:17.541|debug|xenops] pci add mem bar e0000000-efffffff
[20090415 05:13:17.541|debug|xenops] pci add mem bar b0000000-b1ffffff
[20090415 05:13:17.541|debug|xenops] pci add io bar 1000-107f
[20090415 05:13:17.541|debug|xenops] adding device  B0[/local/domain/0/backend/pci/1/0]  F1[/local/domain/1/device/pci/0]  H[/xapi/1/hotplug/pci/0]
[20090415 05:13:17.544|debug|xenops] qemu-dm: executing commandline: /opt/xensource/libexec/closeandexec -- /opt/xensource/libexec/qemu-dm-wrapper 1 /tmp/qemu.1 -d 1 -m 2047 -boot cd -serial pty -vcpus 1 -vncunused -k en-us -net nic,vlan=0,macaddr=00:16:3e:15:60:9a,model=rtl8139 -net tap,vlan=0,bridge=,ifname=tap1.0
[20090415 05:13:17.545|debug|xenops] qemu-dm: should be running in the background (stdout and stderr redirected to /tmp/qemu.1)
[20090415 05:13:17.546|debug|xenops] watch: watching xenstore paths: [ /local/domain/1/device-misc/dm-ready ] with timeout 15.000000 seconds
[20090415 05:13:17.546|debug|xenops] watch: fired on /local/domain/1/device-misc/dm-ready
[20090415 05:13:17.636|debug|xenops] watch: fired on /local/domain/1/device-misc/dm-ready
[20090415 05:13:17.636|debug|xenops] watch: value has appeared: /local/domain/1/device-misc/dm-ready = 1
[20090415 05:13:17.637|debug|xenops] watch: Successfully finished watching xenstore after 0.091099 seconds
[20090415 05:13:17.637|debug|xenops] qemu-dm: pid = 1458
[20090415 05:13:17.637|debug|xenops] watch: watching xenstore paths: [ /local/domain/1/console/vnc-port ] with timeout 1200.000000 seconds
[20090415 05:13:17.637|debug|xenops] watch: fired on /local/domain/1/console/vnc-port
[20090415 05:13:17.637|debug|xenops] watch: value has appeared: /local/domain/1/console/vnc-port = 5900
[20090415 05:13:17.637|debug|xenops] watch: Successfully finished watching xenstore after 0.000320 seconds
[20090415 05:13:17.637|debug|xenops] qemu-dm: wrote vnc port 5900 into the store
[20090415 05:13:17.637|info|vmact] sending notification vm:state:running

[-- Attachment #6: Type: text/plain, Size: 138 bytes --]

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

Re: RE: [XCI] result of pci vga passthrough

[Jun Koi]

On Wed, Apr 15, 2009 at 7:28 PM, Tim Moore <timothy.moore@expidas.net> wrote:
> Hi Stefano,
>
> Please find attached, logs from XCI and a quick jpg of the WinXP host.
>
> I will compile Xen for XCI with debug if necessary?

Could you explain why you use XCI for this kind of thing (video
passthrough)? Because it provides better support?

Thanks,
Jun




> -----Original Message-----
> From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com]
> Sent: 15 April 2009 10:50
> To: Tim Moore
> Cc: 'Bryan York'; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1
>
> Tim Moore wrote:
>
>> Thanks Stefano,
>>
>> I have tried all your suggestions with both XCI and Xen-rc1 already to no avail. It works for pv DomU but not HVM.
>>
>> Disable/enable Cirrus - no effect, tried -std-vga -vga none and all host of combinations. When trying primary, the DomU seems to fail and qemu just quits I think due to no video.
>>
>> Can I get some dmesg / logs that will help to analyse further?
>>
>> As I just mentioned to Kier, I'm more than willing to help the community out with this one ;) I have been writing code for Win32 for years, i`m just a bit new to the Xen scene and developing towards the hw.
>>
>
>
> In this case you are interested in the qemu and xen logs.
> For qemu, just open /var/log/xen/qemu-dm-guestname.log; for xen
> compile the hypervisor with debug = y (in Config.mk) and keep an eye on
> the serial.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>

RE: RE: [XCI] result of pci vga passthrough

[Tim Moore]

XCI is supposed to provide more rounded support as it seems that most development of vendor workarounds are in XCI.

Not official answer, maybe Xen developers can give a better steer?

-----Original Message-----
From: Jun Koi [mailto:junkoi2004@gmail.com] 
Sent: 15 April 2009 11:32
To: Tim Moore
Cc: Stefano Stabellini; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] RE: [XCI] result of pci vga passthrough

On Wed, Apr 15, 2009 at 7:28 PM, Tim Moore <timothy.moore@expidas.net> wrote:
> Hi Stefano,
>
> Please find attached, logs from XCI and a quick jpg of the WinXP host.
>
> I will compile Xen for XCI with debug if necessary?

Could you explain why you use XCI for this kind of thing (video
passthrough)? Because it provides better support?

Thanks,
Jun




> -----Original Message-----
> From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com]
> Sent: 15 April 2009 10:50
> To: Tim Moore
> Cc: 'Bryan York'; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1
>
> Tim Moore wrote:
>
>> Thanks Stefano,
>>
>> I have tried all your suggestions with both XCI and Xen-rc1 already to no avail. It works for pv DomU but not HVM.
>>
>> Disable/enable Cirrus - no effect, tried -std-vga -vga none and all host of combinations. When trying primary, the DomU seems to fail and qemu just quits I think due to no video.
>>
>> Can I get some dmesg / logs that will help to analyse further?
>>
>> As I just mentioned to Kier, I'm more than willing to help the community out with this one ;) I have been writing code for Win32 for years, i`m just a bit new to the Xen scene and developing towards the hw.
>>
>
>
> In this case you are interested in the qemu and xen logs.
> For qemu, just open /var/log/xen/qemu-dm-guestname.log; for xen
> compile the hypervisor with debug = y (in Config.mk) and keep an eye on
> the serial.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>

Re: RE: [XCI] result of pci vga passthrough

[Jean Guyader]

Hi,

XCI support pass through as a primary display adpater, the patch are
not into xen unstable.
For nvidia graphic card as a seconday it shouldn't make any different
because nvidia only works as secondary.

Jean

2009/4/15 Tim Moore <timothy.moore@expidas.net>:
> XCI is supposed to provide more rounded support as it seems that most development of vendor workarounds are in XCI.
>
> Not official answer, maybe Xen developers can give a better steer?
>
> -----Original Message-----
> From: Jun Koi [mailto:junkoi2004@gmail.com]
> Sent: 15 April 2009 11:32
> To: Tim Moore
> Cc: Stefano Stabellini; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] RE: [XCI] result of pci vga passthrough
>
> On Wed, Apr 15, 2009 at 7:28 PM, Tim Moore <timothy.moore@expidas.net> wrote:
>> Hi Stefano,
>>
>> Please find attached, logs from XCI and a quick jpg of the WinXP host.
>>
>> I will compile Xen for XCI with debug if necessary?
>
> Could you explain why you use XCI for this kind of thing (video
> passthrough)? Because it provides better support?
>
> Thanks,
> Jun
>
>
>
>
>> -----Original Message-----
>> From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com]
>> Sent: 15 April 2009 10:50
>> To: Tim Moore
>> Cc: 'Bryan York'; xen-devel@lists.xensource.com
>> Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1
>>
>> Tim Moore wrote:
>>
>>> Thanks Stefano,
>>>
>>> I have tried all your suggestions with both XCI and Xen-rc1 already to no avail. It works for pv DomU but not HVM.
>>>
>>> Disable/enable Cirrus - no effect, tried -std-vga -vga none and all host of combinations. When trying primary, the DomU seems to fail and qemu just quits I think due to no video.
>>>
>>> Can I get some dmesg / logs that will help to analyse further?
>>>
>>> As I just mentioned to Kier, I'm more than willing to help the community out with this one ;) I have been writing code for Win32 for years, i`m just a bit new to the Xen scene and developing towards the hw.
>>>
>>
>>
>> In this case you are interested in the qemu and xen logs.
>> For qemu, just open /var/log/xen/qemu-dm-guestname.log; for xen
>> compile the hypervisor with debug = y (in Config.mk) and keep an eye on
>> the serial.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>



-- 
Jean Guyader

Re: RE: [XCI] result of pci vga passthrough

[Jun Koi]

On Wed, Apr 15, 2009 at 7:44 PM, Jean Guyader <jean.guyader@gmail.com> wrote:
> Hi,
>
> XCI support pass through as a primary display adpater, the patch are
> not into xen unstable.

Does that mean we use only 1 video card (primary), and use it for
DomU? Then Dom0 has no video card?


Thanks,
Jun

> 2009/4/15 Tim Moore <timothy.moore@expidas.net>:
>> XCI is supposed to provide more rounded support as it seems that most development of vendor workarounds are in XCI.
>>
>> Not official answer, maybe Xen developers can give a better steer?
>>
>> -----Original Message-----
>> From: Jun Koi [mailto:junkoi2004@gmail.com]
>> Sent: 15 April 2009 11:32
>> To: Tim Moore
>> Cc: Stefano Stabellini; xen-devel@lists.xensource.com
>> Subject: Re: [Xen-devel] RE: [XCI] result of pci vga passthrough
>>
>> On Wed, Apr 15, 2009 at 7:28 PM, Tim Moore <timothy.moore@expidas.net> wrote:
>>> Hi Stefano,
>>>
>>> Please find attached, logs from XCI and a quick jpg of the WinXP host.
>>>
>>> I will compile Xen for XCI with debug if necessary?
>>
>> Could you explain why you use XCI for this kind of thing (video
>> passthrough)? Because it provides better support?
>>
>> Thanks,
>> Jun
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com]
>>> Sent: 15 April 2009 10:50
>>> To: Tim Moore
>>> Cc: 'Bryan York'; xen-devel@lists.xensource.com
>>> Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1
>>>
>>> Tim Moore wrote:
>>>
>>>> Thanks Stefano,
>>>>
>>>> I have tried all your suggestions with both XCI and Xen-rc1 already to no avail. It works for pv DomU but not HVM.
>>>>
>>>> Disable/enable Cirrus - no effect, tried -std-vga -vga none and all host of combinations. When trying primary, the DomU seems to fail and qemu just quits I think due to no video.
>>>>
>>>> Can I get some dmesg / logs that will help to analyse further?
>>>>
>>>> As I just mentioned to Kier, I'm more than willing to help the community out with this one ;) I have been writing code for Win32 for years, i`m just a bit new to the Xen scene and developing towards the hw.
>>>>
>>>
>>>
>>> In this case you are interested in the qemu and xen logs.
>>> For qemu, just open /var/log/xen/qemu-dm-guestname.log; for xen
>>> compile the hypervisor with debug = y (in Config.mk) and keep an eye on
>>> the serial.
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
>
> --
> Jean Guyader
>

Re: RE: [XCI] result of pci vga passthrough

[Jean Guyader]

2009/4/15 Jun Koi <junkoi2004@gmail.com>:
> On Wed, Apr 15, 2009 at 7:44 PM, Jean Guyader <jean.guyader@gmail.com> wrote:
>> Hi,
>>
>> XCI support pass through as a primary display adpater, the patch are
>> not into xen unstable.
>
> Does that mean we use only 1 video card (primary), and use it for
> DomU? Then Dom0 has no video card?
>
>

I mean pass through as a primary in the guest, for doing so we have to:
  - Rexecute the bios
  - Map the legacy iomem
  - Map the legacy ioport

dom0 could have a graphic card be it's not required.

Thanks,
Jean

Re: RE: [XCI] result of pci vga passthrough

[Jun Koi]

On Wed, Apr 15, 2009 at 7:58 PM, Jean Guyader <jean.guyader@gmail.com> wrote:
> 2009/4/15 Jun Koi <junkoi2004@gmail.com>:
>> On Wed, Apr 15, 2009 at 7:44 PM, Jean Guyader <jean.guyader@gmail.com> wrote:
>>> Hi,
>>>
>>> XCI support pass through as a primary display adpater, the patch are
>>> not into xen unstable.
>>
>> Does that mean we use only 1 video card (primary), and use it for
>> DomU? Then Dom0 has no video card?
>>
>>
>
> I mean pass through as a primary in the guest, for doing so we have to:
>  - Rexecute the bios
>  - Map the legacy iomem
>  - Map the legacy ioport
>
> dom0 could have a graphic card be it's not required.

So we can have 2 cards, and pass one to DomU, and DomU sees that as
primary video card?

I searched around, but dont see where to download XCI??

Thanks,
Jun

Re: RE: [XCI] result of pci vga passthrough

[Jean Guyader]

2009/4/15 Jun Koi <junkoi2004@gmail.com>:
> On Wed, Apr 15, 2009 at 7:58 PM, Jean Guyader <jean.guyader@gmail.com> wrote:
>> 2009/4/15 Jun Koi <junkoi2004@gmail.com>:
>>> On Wed, Apr 15, 2009 at 7:44 PM, Jean Guyader <jean.guyader@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> XCI support pass through as a primary display adpater, the patch are
>>>> not into xen unstable.
>>>
>>> Does that mean we use only 1 video card (primary), and use it for
>>> DomU? Then Dom0 has no video card?
>>>
>>>
>>
>> I mean pass through as a primary in the guest, for doing so we have to:
>>  - Rexecute the bios
>>  - Map the legacy iomem
>>  - Map the legacy ioport
>>
>> dom0 could have a graphic card be it's not required.
>
> So we can have 2 cards, and pass one to DomU, and DomU sees that as
> primary video card?
>
> I searched around, but dont see where to download XCI??
>

Yes, that the tricks to make it works with intel graphic card, but I
thing it won't change anything for nvidia or ati card.

http://xenbits.xen.org/xenclient/

clone build.git and then there is a readme inside.
Don't hesitate if you have any further questions.

Thanks,
Jean

Re: [XCI] result of pci vga passthrough

[Stefano Stabellini]

Tim Moore wrote:

> Hi Stefano,
> 
> Please find attached, logs from XCI and a quick jpg of the WinXP host.
> 
> I will compile Xen for XCI with debug if necessary?
> 



You have some stuff in the qemu logs I am not familiar with.
Where do all the:

XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE

and

XenNet --> XenNet_ConnectBackend

come from?

RE: [XCI] result of pci vga passthrough

[Tim Moore]

[-- Attachment #1: Type: text/plain, Size: 2008 bytes --]

Stefano / Jean,

I am looking through these logs and nothing seems to be wrong ! no error mapping i/o or mem for Xen or Qemu, for all intents and purpose this should work? I feel like i`m cracking up!

Additional info attached.

What IS strange is that the card is detected as PCIe V1.0 not V2.0 which it is. When using pv DomU this does show as a PCIe v2.0 card ... but not under HVM.

Cheers,
Tim
________________________________________
From: xen-devel-bounces@lists.xensource.com [xen-devel-bounces@lists.xensource.com] On Behalf Of Tim Moore [timothy.moore@expidas.net]
Sent: 15 April 2009 11:28
To: 'Stefano Stabellini'
Cc: xen-devel@lists.xensource.com
Subject: [Xen-devel] RE: [XCI] result of pci vga passthrough

Hi Stefano,

Please find attached, logs from XCI and a quick jpg of the WinXP host.

I will compile Xen for XCI with debug if necessary?

Cheers,
Tim

-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com]
Sent: 15 April 2009 10:50
To: Tim Moore
Cc: 'Bryan York'; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1

Tim Moore wrote:

> Thanks Stefano,
>
> I have tried all your suggestions with both XCI and Xen-rc1 already to no avail. It works for pv DomU but not HVM.
>
> Disable/enable Cirrus - no effect, tried -std-vga -vga none and all host of combinations. When trying primary, the DomU seems to fail and qemu just quits I think due to no video.
>
> Can I get some dmesg / logs that will help to analyse further?
>
> As I just mentioned to Kier, I'm more than willing to help the community out with this one ;) I have been writing code for Win32 for years, i`m just a bit new to the Xen scene and developing towards the hw.
>


In this case you are interested in the qemu and xen logs.
For qemu, just open /var/log/xen/qemu-dm-guestname.log; for xen
compile the hypervisor with debug = y (in Config.mk) and keep an eye on
the serial.

[-- Attachment #2: pci32 output from XCI DomU.txt --]
[-- Type: text/plain, Size: 1636 bytes --]

 Bus 0 (PCI Express), Device Number 2, Device Function 0
 Vendor 10DEh Nvidia Corp
 Device 0600h Unknown
 Command 0007h (I/O Access, Memory Access, BusMaster)
 Status 0010h (Has Capabilities List, Fast Timing)
 Revision A2h, Header Type 00h, Bus Latency Timer 00h
 Self test 00h (Self test not supported)
 PCI Class Display, type VGA
 Subsystem ID 071919F1h Unknown
 Subsystem Vendor 19F1h Unknown
 Address 0 is a Memory Address (anywhere in 0-4Gb) : D4000000h
 Address 1 is a Memory Address (anywhere in 64-bit space, Prefetchable) : C00000
00h
 Address 3 is a Memory Address (anywhere in 64-bit space) : D0000000h
 Address 5 is an I/O Port : 0000C200h
 System IRQ 11, INT# A
 Expansion ROM of 128Kb decoded by this card (Currently disabled)
 New Capabilities List Present:
   Power Management Capability, Version 1.2
     Does not support low power State D1 or D2
     Does not support PME# signalling
     Current Power State : D0 (Device operational, no power saving)
   Message Signalled Interrupt Capability
     MSI is disabled
     MSI function can generate 64-bit addresses
   PCI Express Capability, Version 1
     Device/Port Type :
       PCI Express Endpoint Device
     Device Capabilities :
     Device Control :
       Unsupported Request Severity is Fatal
     Device Status :
       Correctable Error Detected
     Link Capabilities :
       Maximum Link Speed : 2.5Gb/s
       Maximum Link Width : x16
       Link Port Number   : 0
     Link Control :
       Asynchronous Clocking in Use
     Link Status :
       Current Link Speed : 2.5Gb/s
       Current Link Width : x16

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: good progress on pci vga passthrough in xen-3.4-rc1

[wei zhou]

[-- Attachment #1.1: Type: text/plain, Size: 2390 bytes --]

2009/4/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>

> Tim Moore wrote:
>
> > Thread-Topic:
> > [XCI] Question?
> > Thread-Index:
> > Acm88go+caOvZEXVSRCK6Iw2iEIE+A==
> > Message-ID:
> > <14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1F@heavy-vm03.heavy.org.uk>
> > Accept-Language:
> > en-US
> > X-MS-Exchange-Organization-SCL:
> > -1
> > Content-Type:
> > multipart/alternative;
> > boundary="_000_14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1Fheavyvm03he_"
> > MIME-Version:
> > 1.0
> >
> >
> > Hi J/Ross, Hope you can help …
> >
> >
> >
> > Reading the Xen Client Initiative meeting minutes from May 20 2008, it
> > mentions that:
> >
> >
> >
> >     * Multiple graphics cards are working with recent patches (3 Main
> >       vendors)
> >
> >
> >
> > Do we know which 3x Graphics card vendors are working?
> >
> >
> >
> > I have built the XCI source from xenbits and whilst using it seems that
> > the VGA card  support is still quite specific …
> >
>
>
> The VGA support in XCI at the moment is Intel specific.
>
> However videocard passthrough should work OK with most graphic cards if
> you passthrought the videocard to the guest as a secondary card (you do
> not disable the emulated cirrus vga). The problem with this approach is
> that you are not able to see anything on the screen until the guest
> enables the secondary card so you may need to configure the guest using
> vnc fron another machine, at least the first time.
> On the other hand if you disable the emulated vga so the pt graphic card
> happers as a primary in the guest, you should be able to see output on
> the screen since the beginning of the guest boot sequence, but then you
> are going to have more vga bios problems.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>


I have tried pass through a PCI ATI graphic card to DomainU.
I recognized that the ATI would be the second card.
I boot the DomainU with console and modified the xorg.conf file for the
X-window rendered by the ATI card.
But the DomainU still displaied on the same screen.

I want to know how to make the DomainU displaied on the second screen?
How to disable the emulated graphic card.


-- 
Best regards ！
joe
E-mail: weizhou.sir@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 3300 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

RE: [XCI] result of pci vga passthrough

[Tim Moore]

I think this is coming from the GplPv drivers, we have 0.10.50 installed at the moment ... is there a specific version that you have tested with XCI. I don't think this matters for PCI passthrough ?!
Also used older versions of GplPv too and also tried without ...

Thanks,
Tim
-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com] 
Sent: 15 April 2009 12:08
To: Tim Moore
Cc: xen-devel@lists.xensource.com
Subject: Re: [XCI] result of pci vga passthrough

Tim Moore wrote:

> Hi Stefano,
> 
> Please find attached, logs from XCI and a quick jpg of the WinXP host.
> 
> I will compile Xen for XCI with debug if necessary?
> 



You have some stuff in the qemu logs I am not familiar with.
Where do all the:

XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE

and

XenNet --> XenNet_ConnectBackend

come from?

RE: good progress on pci vga passthrough in xen-3.4-rc1

[Tim Moore]

[-- Attachment #1.1: Type: text/plain, Size: 3261 bytes --]

Hello Wei,

Please try with your Nvidia card, ATI not working with VT-d.

You WILL have to compile from source, to fix bad RMRR error. This will make VT-d work.

Then hope your BIOS isn’t too broken and try again.

Tim

And Everytime i use the PCIE card render for Domain0, the VT-D can't be Enable Because of the RMMR incorrect.

See:
http://www.nabble.com/Re:-Re:-VT-D-RMRR-is-incorrect-p22022061.html

Use this work around and (/* the whole “if” section */) and compile Xen.

________________________________
From: wei zhou [mailto:weizhou.sir@gmail.com]
Sent: 15 April 2009 12:28
To: Stefano Stabellini
Cc: Tim Moore; xen-devel@lists.xensource.com; Bryan York
Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1


2009/4/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com<mailto:stefano.stabellini@eu.citrix.com>>
Tim Moore wrote:

> Thread-Topic:
> [XCI] Question?
> Thread-Index:
> Acm88go+caOvZEXVSRCK6Iw2iEIE+A==
> Message-ID:
> <14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1F@heavy-vm03.heavy.org.uk<mailto:14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1F@heavy-vm03.heavy.org.uk>>
> Accept-Language:
> en-US
> X-MS-Exchange-Organization-SCL:
> -1
> Content-Type:
> multipart/alternative;
> boundary="_000_14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1Fheavyvm03he_"
> MIME-Version:
> 1.0
>
>
> Hi J/Ross, Hope you can help …
>
>
>
> Reading the Xen Client Initiative meeting minutes from May 20 2008, it
> mentions that:
>
>
>
>     * Multiple graphics cards are working with recent patches (3 Main
>       vendors)
>
>
>
> Do we know which 3x Graphics card vendors are working?
>
>
>
> I have built the XCI source from xenbits and whilst using it seems that
> the VGA card  support is still quite specific …
>


The VGA support in XCI at the moment is Intel specific.

However videocard passthrough should work OK with most graphic cards if
you passthrought the videocard to the guest as a secondary card (you do
not disable the emulated cirrus vga). The problem with this approach is
that you are not able to see anything on the screen until the guest
enables the secondary card so you may need to configure the guest using
vnc fron another machine, at least the first time.
On the other hand if you disable the emulated vga so the pt graphic card
happers as a primary in the guest, you should be able to see output on
the screen since the beginning of the guest boot sequence, but then you
are going to have more vga bios problems.



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
http://lists.xensource.com/xen-devel


I have tried pass through a PCI ATI graphic card to DomainU.
I recognized that the ATI would be the second card.
I boot the DomainU with console and modified the xorg.conf file for the X-window rendered by the ATI card.
But the DomainU still displaied on the same screen.

I want to know how to make the DomainU displaied on the second screen?
How to disable the emulated graphic card.


--
Best regards ！
joe
E-mail: weizhou.sir@gmail.com<mailto:weizhou.sir@gmail.com>

[-- Attachment #1.2: Type: text/html, Size: 11002 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: good progress on pci vga passthrough in xen-3.4-rc1

[wei zhou]

[-- Attachment #1.1: Type: text/plain, Size: 3640 bytes --]

Thanks so much for your reply.
Because of the RMRR incorrect , i aborted the NVIDIA card.
I will use the ATI card as the primary the NVIDIA card asigned to GuestOS.
Hope some good news !





2009/4/15 Tim Moore <timothy.moore@expidas.net>

>  Hello Wei,
>
>
>
> Please try with your Nvidia card, ATI not working with VT-d.
>
>
>
> You WILL have to compile from source, to fix bad RMRR error. This will make
> VT-d work.
>
>
>
> Then hope your BIOS isn’t too broken and try again.
>
>
>
> Tim
>
>
>
> And Everytime i use the PCIE card render for Domain0, the VT-D can't be
> Enable Because of the RMMR incorrect.
>
>
>
> See:
>
> http://www.nabble.com/Re:-Re:-VT-D-RMRR-is-incorrect-p22022061.html
>
>
>
> Use this work around and (/* the whole “if” section */) and compile Xen.
>
>
>  ------------------------------
>
> *From:* wei zhou [mailto:weizhou.sir@gmail.com]
> *Sent:* 15 April 2009 12:28
> *To:* Stefano Stabellini
> *Cc:* Tim Moore; xen-devel@lists.xensource.com; Bryan York
> *Subject:* Re: [Xen-devel] good progress on pci vga passthrough in
> xen-3.4-rc1
>
>
>
>
>
> 2009/4/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> Tim Moore wrote:
>
> > Thread-Topic:
> > [XCI] Question?
> > Thread-Index:
> > Acm88go+caOvZEXVSRCK6Iw2iEIE+A==
> > Message-ID:
> > <14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1F@heavy-vm03.heavy.org.uk>
> > Accept-Language:
> > en-US
> > X-MS-Exchange-Organization-SCL:
> > -1
> > Content-Type:
> > multipart/alternative;
> > boundary="_000_14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1Fheavyvm03he_"
> > MIME-Version:
> > 1.0
> >
> >
> > Hi J/Ross, Hope you can help …
> >
> >
> >
> > Reading the Xen Client Initiative meeting minutes from May 20 2008, it
> > mentions that:
> >
> >
> >
> >     * Multiple graphics cards are working with recent patches (3 Main
> >       vendors)
> >
> >
> >
> > Do we know which 3x Graphics card vendors are working?
> >
> >
> >
> > I have built the XCI source from xenbits and whilst using it seems that
> > the VGA card  support is still quite specific …
> >
>
>
> The VGA support in XCI at the moment is Intel specific.
>
> However videocard passthrough should work OK with most graphic cards if
> you passthrought the videocard to the guest as a secondary card (you do
> not disable the emulated cirrus vga). The problem with this approach is
> that you are not able to see anything on the screen until the guest
> enables the secondary card so you may need to configure the guest using
> vnc fron another machine, at least the first time.
> On the other hand if you disable the emulated vga so the pt graphic card
> happers as a primary in the guest, you should be able to see output on
> the screen since the beginning of the guest boot sequence, but then you
> are going to have more vga bios problems.
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
> I have tried pass through a PCI ATI graphic card to DomainU.
> I recognized that the ATI would be the second card.
> I boot the DomainU with console and modified the xorg.conf file for the
> X-window rendered by the ATI card.
> But the DomainU still displaied on the same screen.
>
> I want to know how to make the DomainU displaied on the second screen?
> How to disable the emulated graphic card.
>
>
> --
> Best regards ！
> joe
> E-mail: weizhou.sir@gmail.com
>



-- 
Best regards ！
William zhou
E-mail: weizhou.sir@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 9631 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

RE: good progress on pci vga passthrough in xen-3.4-rc1

[Ian Pratt]

> Nvidia graphic cards don't work as primaries, there are some issue
> with the bios rexecution.
> Nvidia cards should work as a seconday display adapter side by side
> with the cirrus.
> 
> So far ATI doesn't support vt-d.

We've had a HD3450 mobile ATI card working as secondary in a vista VM with std drivers -- it just required a secondary bus reset. There was a bug at one point where various bridge flags weren't preserved across a reset.

Ian 

 
> Intel graphic card only works as a primary.
> 
> Jean
> 
> 2009/4/15 Tim Moore <timothy.moore@expidas.net>:
> > Kier,
> >
> > I have an nvidia nv4 (8800 GTS) and 9500 GT and they do not work
> under XCI (as primary or secondary cards) and the same problem under
> xen-rc1. I have also tried ATI cards to no avail.
> >
> > Will it be possible to get a list of bios + vendors /drivers that
> have been tested / compatible? I will even offer to maintain the Wiki
> with such information!!
> >
> > Cheers,
> > Tim
> >
> >
> > -----Original Message-----
> > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> > Sent: 15 April 2009 10:26
> > To: Tim Moore; Stefano Stabellini
> > Cc: xen-devel@lists.xensource.com; 'Bryan York'
> > Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-
> 3.4-rc1
> >
> > On 15/04/2009 10:20, "Tim Moore" <timothy.moore@expidas.net> wrote:
> >
> >> Thanks for your reply. This is the first time that I have been
> provided with
> >> some pointers where to look.. like I said in previous emails, I can
> work on
> >> this but I didn't write Xen or any of these workarounds!
> >>
> >> I also posted the [attached] question about XCI - no one answers :(
> >
> > Are there more than three main gfx vendors? ;-)
> >
> > The passthru has been got working on at least one example of each of
> ATI,
> > nVidia and Intel integrated gfx. That doesn't necessarily mean it
> will work
> > for your chip, with your BIOS. Getting it working can on some systems
> be
> > quite a pain in the arse, even if a developer has local access to the
> > system.
> >
> >  -- Keir
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: good progress on pci vga passthrough in xen-3.4-rc1

[wei zhou]

[-- Attachment #1.1: Type: text/plain, Size: 4045 bytes --]

Hi Tim:

  I have modified the source code and recompiled. Everything seems good .
Without RMRR incorrect and VT-D enable.

   Domain0 works with VT-D.

   DomainU asigned the PCIE NVIDIA card

   installed the nvidia-177-83 drivers for DomainU .

   But I am still face the tough question mentioned before that DomainU
cann't be   displaied on the second screen.

    Booted the DomainU with console --> configured the driver for card -->
startx

     DomainU staied on the same screen then went into  black screen but
still alived.

Any hint was appreciated.

Thanks so much



2009/4/15 Tim Moore <timothy.moore@expidas.net>

>  Hello Wei,
>
>
>
> Please try with your Nvidia card, ATI not working with VT-d.
>
>
>
> You WILL have to compile from source, to fix bad RMRR error. This will make
> VT-d work.
>
>
>
> Then hope your BIOS isn’t too broken and try again.
>
>
>
> Tim
>
>
>
> And Everytime i use the PCIE card render for Domain0, the VT-D can't be
> Enable Because of the RMMR incorrect.
>
>
>
> See:
>
> http://www.nabble.com/Re:-Re:-VT-D-RMRR-is-incorrect-p22022061.html
>
>
>
> Use this work around and (/* the whole “if” section */) and compile Xen.
>
>
>  ------------------------------
>
> *From:* wei zhou [mailto:weizhou.sir@gmail.com]
> *Sent:* 15 April 2009 12:28
> *To:* Stefano Stabellini
> *Cc:* Tim Moore; xen-devel@lists.xensource.com; Bryan York
> *Subject:* Re: [Xen-devel] good progress on pci vga passthrough in
> xen-3.4-rc1
>
>
>
>
>
> 2009/4/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> Tim Moore wrote:
>
> > Thread-Topic:
> > [XCI] Question?
> > Thread-Index:
> > Acm88go+caOvZEXVSRCK6Iw2iEIE+A==
> > Message-ID:
> > <14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1F@heavy-vm03.heavy.org.uk>
> > Accept-Language:
> > en-US
> > X-MS-Exchange-Organization-SCL:
> > -1
> > Content-Type:
> > multipart/alternative;
> > boundary="_000_14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F1Fheavyvm03he_"
> > MIME-Version:
> > 1.0
> >
> >
> > Hi J/Ross, Hope you can help …
> >
> >
> >
> > Reading the Xen Client Initiative meeting minutes from May 20 2008, it
> > mentions that:
> >
> >
> >
> >     * Multiple graphics cards are working with recent patches (3 Main
> >       vendors)
> >
> >
> >
> > Do we know which 3x Graphics card vendors are working?
> >
> >
> >
> > I have built the XCI source from xenbits and whilst using it seems that
> > the VGA card  support is still quite specific …
> >
>
>
> The VGA support in XCI at the moment is Intel specific.
>
> However videocard passthrough should work OK with most graphic cards if
> you passthrought the videocard to the guest as a secondary card (you do
> not disable the emulated cirrus vga). The problem with this approach is
> that you are not able to see anything on the screen until the guest
> enables the secondary card so you may need to configure the guest using
> vnc fron another machine, at least the first time.
> On the other hand if you disable the emulated vga so the pt graphic card
> happers as a primary in the guest, you should be able to see output on
> the screen since the beginning of the guest boot sequence, but then you
> are going to have more vga bios problems.
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
> I have tried pass through a PCI ATI graphic card to DomainU.
> I recognized that the ATI would be the second card.
> I boot the DomainU with console and modified the xorg.conf file for the
> X-window rendered by the ATI card.
> But the DomainU still displaied on the same screen.
>
> I want to know how to make the DomainU displaied on the second screen?
> How to disable the emulated graphic card.
>
>
> --
> Best regards ！
> joe
> E-mail: weizhou.sir@gmail.com
>



-- 
Best regards ！
William zhou
E-mail: weizhou.sir@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 10208 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: good progress on pci vga passthrough in xen-3.4-rc1

[wei zhou]

[-- Attachment #1.1: Type: text/plain, Size: 923 bytes --]

 Hi Tim :
      I am still working about VT-D Graphic pass through experiment. Even
with your guys' useful helps, I still cann't make the DomainU displaied on
the second screen connected with the graphic card passed through.
      You said you used the "DomU: 2.6.26-1-xen-amd64 (deb lenny shipped)" as
DomainU. you also said that " Also confirmed that this is NOT possible under
a HVM or running Windows in a DomU, ".

      That means the DomainU should be Para-Virtualization in your
experiment of VT-D graphic pass through .
      How do i get the 2.6.26-1-xen-amd64 (deb lenny shipped) DomainU for
testing?

Thanks

Wei

2009/4/15 Tim Moore <timothy.moore@expidas.net>

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


-- 
Best regards ！
wei zhou
E-mail: weizhou.sir@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 2247 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

RE: good progress on pci vga passthrough in xen-3.4-rc1

[Tim Moore]

[-- Attachment #1.1: Type: text/plain, Size: 1529 bytes --]

Hi Wei,

Yes, DomU should be PV.

Any Xen-enabled kernel will be OK for DomU.

Do you have pciback=”” kernel cmdline for Dom0.

What does lspci -vvv show for the DomU ?

Please also include your X server log file for DomU and your Dom0 Kernel output.

Ta

Tim

________________________________
From: wei zhou [mailto:weizhou.sir@gmail.com]
Sent: 21 April 2009 09:29
To: Tim Moore
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] good progress on pci vga passthrough in xen-3.4-rc1

 Hi Tim :
      I am still working about VT-D Graphic pass through experiment. Even with your guys' useful helps, I still cann't make the DomainU displaied on the second screen connected with the graphic card passed through.
      You said you used the "DomU: 2.6.26-1-xen-amd64 (deb lenny shipped)" as DomainU. you also said that " Also confirmed that this is NOT possible under a HVM or running Windows in a DomU, ".

      That means the DomainU should be Para-Virtualization in your experiment of VT-D graphic pass through .
      How do i get the 2.6.26-1-xen-amd64 (deb lenny shipped) DomainU for testing?

Thanks

Wei
2009/4/15 Tim Moore <timothy.moore@expidas.net<mailto:timothy.moore@expidas.net>>


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
http://lists.xensource.com/xen-devel



--
Best regards ！
wei zhou
E-mail: weizhou.sir@gmail.com<mailto:weizhou.sir@gmail.com>

[-- Attachment #1.2: Type: text/html, Size: 8886 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: good progress on pci vga passthrough in xen-3.4-rc1

[wei zhou]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset=GB2312, Size: 2707 bytes --]

Hi Tim :
    I didn't pay attention to the PV DomainU. I always use the HVM or
Windows OS as the DomainU in my experiments. You remaid me  the PV GuestOS
may make that work easily.
But i still have some questions :
    The PV DomU supported the VT-D / IO virtualization ?
     Did i add the command line "pci = ['xx:xx.x']" in config file of PV
DomU ?

For you questions :

Do you have pciback=¡±¡± kernel cmdline for Dom0.


yes , I added  " pciback.hide = (xx:xx.x) " cmdline in " module
................"

I also added the "iommu = 1 vtd = 1" in " kernel ....................... "


What does lspci ¨Cvvv show for the DomU ?



using the lspci -vvv cmd, i could find the NVIDIA card passed through in
DomU HVM.

But i can't use that for rendering X-window .


Please also include your X server log file for DomU and your Dom0 Kernel
output.
Presently , My system doesn't work . I will attach those files next time.

Thanks so much .

wei



2009/4/22 Tim Moore <timothy.moore@expidas.net>

>  Hi Wei,
>
>
>
> Yes, DomU should be PV.
>
>
>
> Any Xen-enabled kernel will be OK for DomU.
>
>
>
> Do you have pciback=¡±¡± kernel cmdline for Dom0.
>
>
>
> What does lspci ¨Cvvv show for the DomU ?
>
>
>
> Please also include your X server log file for DomU and your Dom0 Kernel
> output.
>
>
>
> Ta
>
>
>
> Tim
>
>
>  ------------------------------
>
> *From:* wei zhou [mailto:weizhou.sir@gmail.com]
> *Sent:* 21 April 2009 09:29
> *To:* Tim Moore
> *Cc:* xen-devel@lists.xensource.com
> *Subject:* Re: [Xen-devel] good progress on pci vga passthrough in
> xen-3.4-rc1
>
>
>
>  Hi Tim :
>
>       I am still working about VT-D Graphic pass through experiment. Even
> with your guys' useful helps, I still cann't make the DomainU displaied on
> the second screen connected with the graphic card passed through.
>       You said you used the "DomU: 2.6.26-1-xen-amd64 (deb lenny shipped)"
> as DomainU. you also said that " Also confirmed that this is NOT possible
> under a HVM or running Windows in a DomU, ".
>
>       That means the DomainU should be Para-Virtualization in your
> experiment of VT-D graphic pass through .
>       How do i get the 2.6.26-1-xen-amd64 (deb lenny shipped) DomainU for
> testing?
>
> Thanks
>
> Wei
>
> 2009/4/15 Tim Moore <timothy.moore@expidas.net>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
>
> --
> Best regards £¡
> wei zhou
> E-mail: weizhou.sir@gmail.com
>



-- 
Best regards £¡
William zhou
E-mail: weizhou.sir@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 10023 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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