* [RFC][QEMU] ATI graphics VBIOS passthru support
@ 2010-10-07 16:56 Huang2, Wei
2010-10-07 23:57 ` Kay, Allen M
0 siblings, 1 reply; 32+ messages in thread
From: Huang2, Wei @ 2010-10-07 16:56 UTC (permalink / raw)
To: Ian Jackson; +Cc: Xen-devel, Kay, Allen M
[-- Attachment #1.1: Type: text/plain, Size: 467 bytes --]
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 2524 bytes --]
[-- Attachment #2: ati_vbios_passthru_patch_v1.txt --]
[-- Type: text/plain, Size: 15074 bytes --]
diff --git a/hw/pass-through.c b/hw/pass-through.c
index 014144e..d27aeea 100644
--- a/hw/pass-through.c
+++ b/hw/pass-through.c
@@ -1379,9 +1379,17 @@ static void pt_ioport_map(PCIDevice *d, int i,
if (e_phys != -1)
{
/* Create new mapping */
- ret = xc_domain_ioport_mapping(xc_handle, domid, e_phys,
- assigned_device->bases[i].access.pio_base, e_size,
- DPCI_ADD_MAPPING);
+ if ( vga_skip_ioport_map(d) )
+ {
+ assigned_device->bases[i].e_physbase = -1;
+ }
+ else
+ {
+ ret = xc_domain_ioport_mapping(xc_handle, domid, e_phys,
+ assigned_device->bases[i].access.pio_base, e_size,
+ DPCI_ADD_MAPPING);
+ }
+
if ( ret != 0 )
{
PT_LOG("Error: create new mapping failed!\n");
diff --git a/hw/pass-through.h b/hw/pass-through.h
index e59eb52..19652c4 100644
--- a/hw/pass-through.h
+++ b/hw/pass-through.h
@@ -411,6 +411,11 @@ int pt_pci_host_write(int bus, int dev, int fn, u32 addr, u32 val, int len);
void intel_pch_init(PCIBus *bus);
int register_vga_regions(struct pt_dev *real_device);
int unregister_vga_regions(struct pt_dev *real_device);
+int vga_skip_ioport_map(PCIDevice *d);
+int igd_register_vga_regions(struct pt_dev *real_device);
+int igd_unregister_vga_regions(struct pt_dev *real_device);
+int ati_register_vga_regions(struct pt_dev *real_device);
+int ati_unregister_vga_regions(struct pt_dev *real_device);
int setup_vga_pt(struct pt_dev *real_device);
PCIBus *intel_pci_bridge_init(PCIBus *bus, int devfn, uint16_t vid,
uint16_t did, const char *name, uint16_t revision);
diff --git a/hw/pci.h b/hw/pci.h
index e4cc79a..4aa0373 100644
--- a/hw/pci.h
+++ b/hw/pci.h
@@ -54,6 +54,8 @@ extern target_phys_addr_t pci_mem_base;
#define PCI_VENDOR_ID_CIRRUS 0x1013
+#define PCI_VENDOR_ID_ATI 0x1002
+
#define PCI_VENDOR_ID_IBM 0x1014
#define PCI_DEVICE_ID_IBM_OPENPIC2 0xffff
diff --git a/hw/pt-graphics.c b/hw/pt-graphics.c
index 5dfcca2..b8f5a3a 100644
--- a/hw/pt-graphics.c
+++ b/hw/pt-graphics.c
@@ -8,11 +8,213 @@
#include <unistd.h>
#include <sys/ioctl.h>
+#include <sys/io.h>
#include <assert.h>
extern int gfx_passthru;
extern int igd_passthru;
+/*********************************/
+/* Code for ATI GFX Passthru */
+/*********************************/
+/* ATI VBIOS Working Mechanism
+ *
+ * Generally there are three memory resources (two MMIO and one PIO)
+ * associated with modern ATI gfx. VBIOS uses special tricks to figure out
+ * BARs, instead of using regular PCI config space read.
+ *
+ * (1) VBIOS relies on I/O port 0x3C3 to retrieve PIO BAR
+ * (2) VBIOS maintains a shadow copy of PCI configure space. It retries the
+ * MMIO BARs from this shadow copy via sending I/O requests to first two
+ * registers of PIO (MMINDEX and MMDATA). The workflow is like this:
+ * MMINDEX (register 0) is written with an index value, specifying the
+ * register VBIOS wanting to access. Then the shadowed data can be
+ * read/written from MMDATA (register 1). For two MMIO BARs, the index
+ * values are 0x4010 and 0x4014 respectively.
+ *
+ */
+
+#define ATI_BAR1_INDEX 0 //MMIO BAR1
+#define ATI_BAR2_INDEX 1 //MMIO BAR2
+#define ATI_BAR5_INDEX 4 //PIO BAR == BAR5
+
+#define ATI_BAR1_MMINDEX 0x4010 //data written to MMINDEX for MMIO BAR1
+#define ATI_BAR2_MMINDEX 0x4014 //data written to MMINDEX FOR MMIO BAR2
+
+struct ati_gfx_info {
+ int initialized; /* initialized already? */
+
+ /* PIO */
+ uint32_t host_pio_base; /* host base addr of PIO */
+ uint32_t guest_pio_base; /* guest base addr of PIO */
+ uint32_t pio_size; /* PIO size */
+
+ /* MMIO */
+ uint32_t guest_mmio_base1; /* guest base addr of MMIO 1 */
+ uint32_t guest_mmio_base2; /* guest base addr of MMIO 2 */
+
+ /* PIO MMINDEX access recording */
+ uint32_t pre_mmindex_data; /* previous data written to MMINDEX */
+};
+
+static struct ati_gfx_info gfx_info;
+
+/* Convert guest PIO port to host PIO port */
+static uint16_t gport_to_hport(uint16_t gport)
+{
+ return (gport - gfx_info.guest_pio_base) + gfx_info.host_pio_base;
+}
+
+/* Read host PIO port */
+static uint32_t ati_hw_in(uint16_t hport)
+{
+ unsigned val;
+
+ ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 1);
+ asm volatile ("in %1,%0":"=a"(val):"Nd"(hport));
+ ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 0);
+
+ return val;
+}
+
+/* Write data to host PIO */
+static void ati_hw_out(uint16_t hport, uint32_t data)
+{
+ ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 1);
+ asm volatile ("out %1, %0"::"Nd"(hport),"a"(data));
+ ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 0);
+}
+
+static uint32_t ati_io_regs_read(void *opaque, uint32_t addr)
+{
+ uint32_t val;
+
+ val = ati_hw_in(gport_to_hport(addr));
+
+ /* tweak the value if VBIOS is reading MMIO BAR1 and BAR2 */
+ if ( addr == (gfx_info.guest_pio_base + 4) )
+ {
+ switch ( gfx_info.pre_mmindex_data )
+ {
+ case ATI_BAR1_MMINDEX:
+ val = gfx_info.guest_mmio_base1 | (val & 0x0000000f);
+ break;
+ case ATI_BAR2_MMINDEX:
+ val = gfx_info.guest_mmio_base2 | (val & 0x0000000f);
+ break;
+ default:
+ break;
+ }
+ }
+
+ return val;
+}
+
+static void ati_io_regs_write(void *opaque, uint32_t addr, uint32_t val)
+{
+ ati_hw_out(gport_to_hport(addr), val);
+
+ /* book keeping */
+ if ( addr == gfx_info.guest_pio_base )
+ gfx_info.pre_mmindex_data = val;
+}
+
+static void ati_gfx_init(struct pt_dev *assigned)
+{
+ PCIDevice *dev = (PCIDevice *)&assigned->dev;
+
+ register_ioport_read(dev->io_regions[ATI_BAR5_INDEX].addr,
+ dev->io_regions[ATI_BAR5_INDEX].size, 4, ati_io_regs_read, assigned);
+
+ register_ioport_write(dev->io_regions[ATI_BAR5_INDEX].addr,
+ dev->io_regions[ATI_BAR5_INDEX].size, 4, ati_io_regs_write, assigned);
+
+ /* initialize IO registers */
+ gfx_info.guest_pio_base = dev->io_regions[ATI_BAR5_INDEX].addr;
+ gfx_info.pio_size = dev->io_regions[ATI_BAR5_INDEX].size;
+ gfx_info.host_pio_base = assigned->bases[ATI_BAR5_INDEX].access.pio_base;
+
+ gfx_info.guest_mmio_base1 = dev->io_regions[ATI_BAR1_INDEX].addr;
+ gfx_info.guest_mmio_base2 = dev->io_regions[ATI_BAR2_INDEX].addr;
+ gfx_info.initialized = 1;
+
+ PT_LOG("guest_pio_bar = 0x%x, host_pio_bar = 0x%x, pio_size=0x%x "
+ "guest_mmio_bar1=0x%x, guest_mmio_bar2=0x%x\n",
+ gfx_info.guest_pio_base, gfx_info.host_pio_base, gfx_info.pio_size,
+ gfx_info.guest_mmio_base1, gfx_info.guest_mmio_base2);
+}
+
+static uint32_t ati_legacy_io_read(void *opaque, uint32_t addr)
+{
+ struct pt_dev *assigned_device = opaque;
+ PCIDevice *dev = (PCIDevice *)&assigned_device->dev;
+ uint32_t val = 0xFF;
+
+ switch( addr )
+ {
+ case 0x3c3:
+ val = dev->io_regions[ATI_BAR5_INDEX].addr >> 8;
+ /* Intercept GFX IO registers. This supposes to happen in
+ * ati_register_vga_regions(). But we cannot get guest phys IO BAR
+ * over there. */
+ if ( !gfx_info.initialized )
+ ati_gfx_init(assigned_device);
+ break;
+ default:
+ PT_LOG("ERROR: port 0x%x I/O read not handled\n", addr);
+ break;
+ }
+
+ return val;
+}
+
+static void ati_legacy_io_write(void *opaque, uint32_t addr, uint32_t val)
+{
+ PT_LOG("ERROR: port 0x%x I/O write not handled\n", addr);
+}
+
+int ati_register_vga_regions(struct pt_dev *real_device)
+{
+ PCIDevice *dev = (PCIDevice *)&real_device->dev;
+ int ret = 0;
+
+ /* We need to intercept VBIOS accesses to port 0x3C3, which returns
+ * device port I/O BAR. For the rest of legacy I/O ports, we allow direct
+ * accesses.
+ */
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
+ 0x3C0, 0x3, DPCI_ADD_MAPPING);
+
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C4,
+ 0x3C4, 0x1C, DPCI_ADD_MAPPING);
+
+ register_ioport_read(0x3c3, 1, 1, ati_legacy_io_read, real_device);
+ register_ioport_write(0x3c3, 1, 1, ati_legacy_io_write, real_device);
+
+ /* initialized on the first port 0x3C3 access in ati_gfx_init */
+ gfx_info.initialized = 0;
+
+ return ret;
+}
+
+int ati_unregister_vga_regions(struct pt_dev *real_device)
+{
+ int ret = 0;
+
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
+ 0x3C0, 0x3, DPCI_REMOVE_MAPPING);
+
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C4,
+ 0x3C4, 0x1C, DPCI_REMOVE_MAPPING);
+
+ gfx_info.initialized = 0;
+
+ return ret;
+}
+
+/*********************************/
+/* Code for Intel IGD Passthru */
+/*********************************/
static int pch_map_irq(PCIDevice *pci_dev, int irq_num)
{
PT_LOG("pch_map_irq called\n");
@@ -88,6 +290,77 @@ uint32_t igd_pci_read(PCIDevice *pci_dev, int config_addr, int len)
return val;
}
+int igd_register_vga_regions(struct pt_dev *real_device)
+{
+ u32 vendor_id, igd_opregion;
+ int ret = 0;
+
+ /* legacy I/O ports 0x3C0 -- 0x3E0 */
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
+ 0x3C0, 0x20, DPCI_ADD_MAPPING);
+
+ /* 1:1 map ASL Storage register value */
+ vendor_id = pt_pci_host_read(0, 2, 0, 0, 2);
+ igd_opregion = pt_pci_host_read(0, 2, 0, 0xfc, 4);
+ if ( (vendor_id == 0x8086) && igd_opregion )
+ {
+ ret |= xc_domain_memory_mapping(xc_handle, domid,
+ igd_opregion >> XC_PAGE_SHIFT,
+ igd_opregion >> XC_PAGE_SHIFT,
+ 2,
+ DPCI_ADD_MAPPING);
+ PT_LOG("register_vga: igd_opregion = %x\n", igd_opregion);
+ }
+
+ return ret;
+}
+
+int igd_unregister_vga_regions(struct pt_dev *real_device)
+{
+ u32 vendor_id, igd_opregion;
+ int ret = 0;
+
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
+ 0x3C0, 0x20, DPCI_REMOVE_MAPPING);
+
+ vendor_id = pt_pci_host_read(0, 2, 0, 0, 2);
+ igd_opregion = pt_pci_host_read(0, 2, 0, 0xfc, 4);
+ if ( (vendor_id == 0x8086) && igd_opregion )
+ {
+ ret |= xc_domain_memory_mapping(xc_handle, domid,
+ igd_opregion >> XC_PAGE_SHIFT,
+ igd_opregion >> XC_PAGE_SHIFT,
+ 2,
+ DPCI_REMOVE_MAPPING);
+ }
+
+ return ret;
+}
+/*********************************/
+/* Generic Code for GFX Passthru */
+/*********************************/
+/* This function decides whether I/O port map should be skipped */
+int vga_skip_ioport_map(PCIDevice *d)
+{
+ struct pt_dev *dev = (struct pt_dev *)d;
+ int skip = 0;
+
+ if ( !gfx_passthru || dev->pci_dev->device_class != 0x0300 )
+ return 0;
+
+ switch( dev->pci_dev->vendor_id )
+ {
+ case PCI_VENDOR_ID_ATI:
+ case PCI_VENDOR_ID_AMD:
+ skip = 1;
+ break;
+ default:
+ skip = 0;
+ break;
+ }
+
+ return skip;
+}
/*
* register VGA resources for the domain with assigned gfx
*/
@@ -99,29 +372,31 @@ int register_vga_regions(struct pt_dev *real_device)
if ( !gfx_passthru || real_device->pci_dev->device_class != 0x0300 )
return ret;
+ /* legacy I/O ports 0x3B0 - 0x3BC */
ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3B0,
0x3B0, 0xC, DPCI_ADD_MAPPING);
-
- ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
- 0x3C0, 0x20, DPCI_ADD_MAPPING);
-
+
+ /* legacy video MMIO range 0xA0000 - 0xBFFFF */
ret |= xc_domain_memory_mapping(xc_handle, domid,
0xa0000 >> XC_PAGE_SHIFT,
0xa0000 >> XC_PAGE_SHIFT,
0x20,
DPCI_ADD_MAPPING);
- /* 1:1 map ASL Storage register value */
- vendor_id = pt_pci_host_read(0, 2, 0, 0, 2);
- igd_opregion = pt_pci_host_read(0, 2, 0, 0xfc, 4);
- if ( (vendor_id == 0x8086) && igd_opregion )
+ /* Other VGA regions are vendor specific */
+ switch( real_device->pci_dev->vendor_id )
{
- ret |= xc_domain_memory_mapping(xc_handle, domid,
- igd_opregion >> XC_PAGE_SHIFT,
- igd_opregion >> XC_PAGE_SHIFT,
- 2,
- DPCI_ADD_MAPPING);
- PT_LOG("register_vga: igd_opregion = %x\n", igd_opregion);
+ case PCI_VENDOR_ID_INTEL:
+ ret = igd_register_vga_regions(real_device);
+ break;
+ case PCI_VENDOR_ID_ATI:
+ case PCI_VENDOR_ID_AMD:
+ ret = ati_register_vga_regions(real_device);
+ break;
+ default:
+ PT_LOG("gfx card wasn't supported by Xen passthru!\n");
+ ret = 1;
+ break;
}
if ( ret != 0 )
@@ -135,33 +410,36 @@ int register_vga_regions(struct pt_dev *real_device)
*/
int unregister_vga_regions(struct pt_dev *real_device)
{
- u32 vendor_id, igd_opregion;
int ret = 0;
if ( !gfx_passthru || real_device->pci_dev->device_class != 0x0300 )
return ret;
+ /* legacy I/O ports 0x3B0 - 0x3BC */
ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3B0,
0x3B0, 0xC, DPCI_REMOVE_MAPPING);
- ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
- 0x3C0, 0x20, DPCI_REMOVE_MAPPING);
-
+ /* legacy video MMIO range 0xA0000 - 0xBFFFF */
ret |= xc_domain_memory_mapping(xc_handle, domid,
0xa0000 >> XC_PAGE_SHIFT,
0xa0000 >> XC_PAGE_SHIFT,
20,
DPCI_REMOVE_MAPPING);
- vendor_id = pt_pci_host_read(0, 2, 0, 0, 2);
- igd_opregion = pt_pci_host_read(0, 2, 0, 0xfc, 4);
- if ( (vendor_id == 0x8086) && igd_opregion )
+ /* Other VGA regions are vendor specific */
+ switch( real_device->pci_dev->vendor_id )
{
- ret |= xc_domain_memory_mapping(xc_handle, domid,
- igd_opregion >> XC_PAGE_SHIFT,
- igd_opregion >> XC_PAGE_SHIFT,
- 2,
- DPCI_REMOVE_MAPPING);
+ case PCI_VENDOR_ID_INTEL:
+ ret = igd_unregister_vga_regions(real_device);
+ break;
+ case PCI_VENDOR_ID_ATI:
+ case PCI_VENDOR_ID_AMD:
+ ret = ati_unregister_vga_regions(real_device);
+ break;
+ default:
+ PT_LOG("gfx card wasn't supported by Xen passthru!\n");
+ ret = 1;
+ break;
}
if ( ret != 0 )
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply related [flat|nested] 32+ messages in thread
* RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-07 16:56 [RFC][QEMU] ATI graphics VBIOS passthru support Huang2, Wei
@ 2010-10-07 23:57 ` Kay, Allen M
2010-10-08 4:05 ` Huang2, Wei
0 siblings, 1 reply; 32+ messages in thread
From: Kay, Allen M @ 2010-10-07 23:57 UTC (permalink / raw)
To: Huang2, Wei, Ian Jackson; +Cc: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1024 bytes --]
Hi Wei,
This patch did not cause any problems with Intel IGD passthrough for me. However, the monitor remained blank if I pass through ATI Firepro V3750 either as the primary display device or the secondary device (gfx_passthru=1/0). Passing it through as the secondary device used to work.
Have you tested the patch with this graphics card?
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:57 AM
To: Ian Jackson
Cc: Xen-devel; Kay, Allen M
Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 4129 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-07 23:57 ` Kay, Allen M
@ 2010-10-08 4:05 ` Huang2, Wei
2010-10-08 7:20 ` Kay, Allen M
0 siblings, 1 reply; 32+ messages in thread
From: Huang2, Wei @ 2010-10-08 4:05 UTC (permalink / raw)
To: Kay, Allen M, Ian Jackson; +Cc: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 2085 bytes --]
Hi Allen,
Thanks for testing it out. We have tested this patch with Radeon 4850, 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750 at hand. It is very possible this patch isn't compatible with V3750. We will try to get hold of one for debugging. For graphics which work with this path, users should be able to get rid of emulated gfx (such as Cirrus). I have successfully installed a Windows guest VM using this patch.
I also want to point out that there is still an issue. Users will see a black screen after installing Catalyst driver. Even though the screen appears to be black, the driver is actually functioning correctly (3DMark can be run with external monitor). Our driver team is currently debugging it and they believe this is easy to fix.
What is your opinion on this patch (and the solution) in general?
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Thursday, October 07, 2010 6:58 PM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
This patch did not cause any problems with Intel IGD passthrough for me. However, the monitor remained blank if I pass through ATI Firepro V3750 either as the primary display device or the secondary device (gfx_passthru=1/0). Passing it through as the secondary device used to work.
Have you tested the patch with this graphics card?
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:57 AM
To: Ian Jackson
Cc: Xen-devel; Kay, Allen M
Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 6590 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-08 4:05 ` Huang2, Wei
@ 2010-10-08 7:20 ` Kay, Allen M
2010-10-08 11:09 ` Stefano Stabellini
2010-10-08 13:57 ` Huang2, Wei
0 siblings, 2 replies; 32+ messages in thread
From: Kay, Allen M @ 2010-10-08 7:20 UTC (permalink / raw)
To: Huang2, Wei, Ian Jackson; +Cc: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 2602 bytes --]
Hi Wei,
Is Catalyst driver the one on AMD website? I think that's what I have in my win7 guest and it matches the symptom you are describing. "lspci" reports my ATI card is a V5700 - although it says v3750 on the box. Where can I get a working driver?
The patch looks reasonable to me in general.
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:06 PM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Thanks for testing it out. We have tested this patch with Radeon 4850, 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750 at hand. It is very possible this patch isn't compatible with V3750. We will try to get hold of one for debugging. For graphics which work with this path, users should be able to get rid of emulated gfx (such as Cirrus). I have successfully installed a Windows guest VM using this patch.
I also want to point out that there is still an issue. Users will see a black screen after installing Catalyst driver. Even though the screen appears to be black, the driver is actually functioning correctly (3DMark can be run with external monitor). Our driver team is currently debugging it and they believe this is easy to fix.
What is your opinion on this patch (and the solution) in general?
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Thursday, October 07, 2010 6:58 PM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
This patch did not cause any problems with Intel IGD passthrough for me. However, the monitor remained blank if I pass through ATI Firepro V3750 either as the primary display device or the secondary device (gfx_passthru=1/0). Passing it through as the secondary device used to work.
Have you tested the patch with this graphics card?
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:57 AM
To: Ian Jackson
Cc: Xen-devel; Kay, Allen M
Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 8097 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-08 7:20 ` Kay, Allen M
@ 2010-10-08 11:09 ` Stefano Stabellini
2010-10-08 15:32 ` Huang2, Wei
2010-10-08 13:57 ` Huang2, Wei
1 sibling, 1 reply; 32+ messages in thread
From: Stefano Stabellini @ 2010-10-08 11:09 UTC (permalink / raw)
To: Kay, Allen M; +Cc: Huang2, Wei, Ian Jackson, Xen-devel
On Fri, 8 Oct 2010, Kay, Allen M wrote:
>
> Hi Wei,
>
> ??
>
> Is Catalyst driver the one on AMD website??? I think that???s what I have in my win7 guest and it matches the symptom you are
> describing.?? ???lspci??? reports my ATI card is a V5700 ??? although it says v3750 on the box.?? Where can I get a working
> driver?
>
> ??
>
> The patch looks reasonable to me in general.
>
Agreed. It is a pity that we need to add:
if ( vga_skip_ioport_map(d) )
in pass-through.c but I cannot see better way of doing it.
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-08 7:20 ` Kay, Allen M
2010-10-08 11:09 ` Stefano Stabellini
@ 2010-10-08 13:57 ` Huang2, Wei
2010-10-08 14:41 ` djmagee
1 sibling, 1 reply; 32+ messages in thread
From: Huang2, Wei @ 2010-10-08 13:57 UTC (permalink / raw)
To: Kay, Allen M, Ian Jackson; +Cc: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 3114 bytes --]
Hi Allen,
Yes, Catalyst driver is the one from public website. The driver still has a minor issue with this VBIOS patch. The purpose of submitting VBIOS patch is to get community feedbacks. After we figure out the root cause of black screen, I will formally submit a patch for inclusion.
Thanks,
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Friday, October 08, 2010 2:21 AM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
Is Catalyst driver the one on AMD website? I think that's what I have in my win7 guest and it matches the symptom you are describing. "lspci" reports my ATI card is a V5700 - although it says v3750 on the box. Where can I get a working driver?
The patch looks reasonable to me in general.
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:06 PM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Thanks for testing it out. We have tested this patch with Radeon 4850, 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750 at hand. It is very possible this patch isn't compatible with V3750. We will try to get hold of one for debugging. For graphics which work with this path, users should be able to get rid of emulated gfx (such as Cirrus). I have successfully installed a Windows guest VM using this patch.
I also want to point out that there is still an issue. Users will see a black screen after installing Catalyst driver. Even though the screen appears to be black, the driver is actually functioning correctly (3DMark can be run with external monitor). Our driver team is currently debugging it and they believe this is easy to fix.
What is your opinion on this patch (and the solution) in general?
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Thursday, October 07, 2010 6:58 PM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
This patch did not cause any problems with Intel IGD passthrough for me. However, the monitor remained blank if I pass through ATI Firepro V3750 either as the primary display device or the secondary device (gfx_passthru=1/0). Passing it through as the secondary device used to work.
Have you tested the patch with this graphics card?
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:57 AM
To: Ian Jackson
Cc: Xen-devel; Kay, Allen M
Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 9768 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-08 13:57 ` Huang2, Wei
@ 2010-10-08 14:41 ` djmagee
2010-10-08 14:50 ` Pasi Kärkkäinen
2010-10-08 15:41 ` Huang2, Wei
0 siblings, 2 replies; 32+ messages in thread
From: djmagee @ 2010-10-08 14:41 UTC (permalink / raw)
To: Huang2, Wei, Kay, Allen M, Ian Jackson; +Cc: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 4206 bytes --]
Wei,
I've tested with a Radeon 4770 and it the VBIOS works
without a problem, through many guest (re)boots, so it seems pretty
solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
and Windows 7 (without accelerated drivers). The open radeon linux
driver works fine.
The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
in device driver), windows 7 (STOP 0x00000116, driver fails to properly
reset?), and linux (total system freeze). This seems to be different
than the 'Blank Screen' problem you report, as the driver is clearly not
functioning properly.
Doug Magee
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
Sent: Friday, October 08, 2010 9:57 AM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Yes, Catalyst driver is the one from public website. The driver still
has a minor issue with this VBIOS patch. The purpose of submitting
VBIOS patch is to get community feedbacks. After we figure out the root
cause of black screen, I will formally submit a patch for inclusion.
Thanks,
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Friday, October 08, 2010 2:21 AM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
Is Catalyst driver the one on AMD website? I think that's what I have
in my win7 guest and it matches the symptom you are describing. "lspci"
reports my ATI card is a V5700 - although it says v3750 on the box.
Where can I get a working driver?
The patch looks reasonable to me in general.
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:06 PM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Thanks for testing it out. We have tested this patch with Radeon 4850,
4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750
at hand. It is very possible this patch isn't compatible with V3750. We
will try to get hold of one for debugging. For graphics which work with
this path, users should be able to get rid of emulated gfx (such as
Cirrus). I have successfully installed a Windows guest VM using this
patch.
I also want to point out that there is still an issue. Users will see a
black screen after installing Catalyst driver. Even though the screen
appears to be black, the driver is actually functioning correctly
(3DMark can be run with external monitor). Our driver team is currently
debugging it and they believe this is easy to fix.
What is your opinion on this patch (and the solution) in general?
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Thursday, October 07, 2010 6:58 PM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
This patch did not cause any problems with Intel IGD passthrough for me.
However, the monitor remained blank if I pass through ATI Firepro V3750
either as the primary display device or the secondary device
(gfx_passthru=1/0). Passing it through as the secondary device used to
work.
Have you tested the patch with this graphics card?
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:57 AM
To: Ian Jackson
Cc: Xen-devel; Kay, Allen M
Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch
enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
Windows boot logo) can now show in passthru screen. We have tested with
various Windows and Linux guest VMs. Please help review it. We are also
looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 14274 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-08 14:41 ` djmagee
@ 2010-10-08 14:50 ` Pasi Kärkkäinen
2010-10-08 15:41 ` Huang2, Wei
1 sibling, 0 replies; 32+ messages in thread
From: Pasi Kärkkäinen @ 2010-10-08 14:50 UTC (permalink / raw)
To: djmagee; +Cc: Ian Jackson, Huang2, Wei, Kay, Allen M, Xen-devel
On Fri, Oct 08, 2010 at 10:41:06AM -0400, djmagee@mageenet.net wrote:
> Wei,
>
> I've tested with a Radeon 4770 and it the VBIOS works
> without a problem, through many guest (re)boots, so it seems pretty
> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> and Windows 7 (without accelerated drivers). The open radeon linux driver
> works fine.
>
>
I added this (and other) tested adapters to:
http://wiki.xensource.com/xenwiki/XenVGAPassthroughTestedAdapters
-- Pasi
>
> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in
> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> reset?), and linux (total system freeze). This seems to be different than
> the `Blank Screen' problem you report, as the driver is clearly not
> functioning properly.
>
>
>
> Doug Magee
>
>
>
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> Sent: Friday, October 08, 2010 9:57 AM
> To: Kay, Allen M; Ian Jackson
> Cc: Xen-devel
> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Allen,
>
>
>
> Yes, Catalyst driver is the one from public website. The driver still has
> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> patch is to get community feedbacks. After we figure out the root cause of
> black screen, I will formally submit a patch for inclusion.
>
>
>
> Thanks,
>
> -Wei
>
>
>
> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> Sent: Friday, October 08, 2010 2:21 AM
> To: Huang2, Wei; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Wei,
>
>
>
> Is Catalyst driver the one on AMD website? I think that's what I have in
> my win7 guest and it matches the symptom you are describing. "lspci"
> reports my ATI card is a V5700 - although it says v3750 on the box. Where
> can I get a working driver?
>
>
>
> The patch looks reasonable to me in general.
>
>
>
> Allen
>
>
>
> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> Sent: Thursday, October 07, 2010 9:06 PM
> To: Kay, Allen M; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Allen,
>
>
>
> Thanks for testing it out. We have tested this patch with Radeon 4850,
> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750
> at hand. It is very possible this patch isn't compatible with V3750. We
> will try to get hold of one for debugging. For graphics which work with
> this path, users should be able to get rid of emulated gfx (such as
> Cirrus). I have successfully installed a Windows guest VM using this
> patch.
>
>
>
> I also want to point out that there is still an issue. Users will see a
> black screen after installing Catalyst driver. Even though the screen
> appears to be black, the driver is actually functioning correctly (3DMark
> can be run with external monitor). Our driver team is currently debugging
> it and they believe this is easy to fix.
>
>
>
> What is your opinion on this patch (and the solution) in general?
>
>
>
> -Wei
>
>
>
> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> Sent: Thursday, October 07, 2010 6:58 PM
> To: Huang2, Wei; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Wei,
>
>
>
> This patch did not cause any problems with Intel IGD passthrough for me.
> However, the monitor remained blank if I pass through ATI Firepro V3750
> either as the primary display device or the secondary device
> (gfx_passthru=1/0). Passing it through as the secondary device used to
> work.
>
>
>
> Have you tested the patch with this graphics card?
>
>
>
> Allen
>
>
>
> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> Sent: Thursday, October 07, 2010 9:57 AM
> To: Ian Jackson
> Cc: Xen-devel; Kay, Allen M
> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Ian,
>
>
>
> There have been a lot of interest on gfx passthru recently. This patch
> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> Windows boot logo) can now show in passthru screen. We have tested with
> various Windows and Linux guest VMs. Please help review it. We are also
> looking forward to comments and suggestions from Xen community users.
>
>
>
> Signed-off-by: Wei Huang <wei.huang2@amd.com>
>
> Signed-off-by: Wei Wang <wei.wang2@amd.com>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-08 11:09 ` Stefano Stabellini
@ 2010-10-08 15:32 ` Huang2, Wei
0 siblings, 0 replies; 32+ messages in thread
From: Huang2, Wei @ 2010-10-08 15:32 UTC (permalink / raw)
To: Stefano Stabellini, Kay, Allen M; +Cc: Xen-devel, Ian Jackson
Hi Stefano,
I don't like this approach myself. So far this is the only way to intercept port IO accesses.
Thanks,
-Wei
-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com]
Sent: Friday, October 08, 2010 6:10 AM
To: Kay, Allen M
Cc: Huang2, Wei; Ian Jackson; Xen-devel
Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
On Fri, 8 Oct 2010, Kay, Allen M wrote:
>
> Hi Wei,
>
> ??
>
> Is Catalyst driver the one on AMD website??? I think that???s what I have in my win7 guest and it matches the symptom you are
> describing.?? ???lspci??? reports my ATI card is a V5700 ??? although it says v3750 on the box.?? Where can I get a working
> driver?
>
> ??
>
> The patch looks reasonable to me in general.
>
Agreed. It is a pity that we need to add:
if ( vga_skip_ioport_map(d) )
in pass-through.c but I cannot see better way of doing it.
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-08 14:41 ` djmagee
2010-10-08 14:50 ` Pasi Kärkkäinen
@ 2010-10-08 15:41 ` Huang2, Wei
2010-10-08 15:52 ` djmagee
1 sibling, 1 reply; 32+ messages in thread
From: Huang2, Wei @ 2010-10-08 15:41 UTC (permalink / raw)
To: djmagee@mageenet.net, Kay, Allen M, Ian Jackson; +Cc: Wang2, Wei, Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 4594 bytes --]
Hi Doug,
Regarding Catalyst driver, we never saw guest crashing. Was it a fresh Catalyst installation or an existing guest image? We felt this VBIOS patch might not provide all necessary resources to driver, which got upset. Currently we are debugging it with our driver team and will let you know the update.
Thanks,
-Wei
From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
Sent: Friday, October 08, 2010 9:41 AM
To: Huang2, Wei; Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Wei,
I've tested with a Radeon 4770 and it the VBIOS works without a problem, through many guest (re)boots, so it seems pretty solid. I tested a linux guest (fairly standard Fedora 12), Windows XP, and Windows 7 (without accelerated drivers). The open radeon linux driver works fine.
The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in device driver), windows 7 (STOP 0x00000116, driver fails to properly reset?), and linux (total system freeze). This seems to be different than the 'Blank Screen' problem you report, as the driver is clearly not functioning properly.
Doug Magee
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
Sent: Friday, October 08, 2010 9:57 AM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Yes, Catalyst driver is the one from public website. The driver still has a minor issue with this VBIOS patch. The purpose of submitting VBIOS patch is to get community feedbacks. After we figure out the root cause of black screen, I will formally submit a patch for inclusion.
Thanks,
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Friday, October 08, 2010 2:21 AM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
Is Catalyst driver the one on AMD website? I think that's what I have in my win7 guest and it matches the symptom you are describing. "lspci" reports my ATI card is a V5700 - although it says v3750 on the box. Where can I get a working driver?
The patch looks reasonable to me in general.
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:06 PM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Thanks for testing it out. We have tested this patch with Radeon 4850, 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750 at hand. It is very possible this patch isn't compatible with V3750. We will try to get hold of one for debugging. For graphics which work with this path, users should be able to get rid of emulated gfx (such as Cirrus). I have successfully installed a Windows guest VM using this patch.
I also want to point out that there is still an issue. Users will see a black screen after installing Catalyst driver. Even though the screen appears to be black, the driver is actually functioning correctly (3DMark can be run with external monitor). Our driver team is currently debugging it and they believe this is easy to fix.
What is your opinion on this patch (and the solution) in general?
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Thursday, October 07, 2010 6:58 PM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
This patch did not cause any problems with Intel IGD passthrough for me. However, the monitor remained blank if I pass through ATI Firepro V3750 either as the primary display device or the secondary device (gfx_passthru=1/0). Passing it through as the secondary device used to work.
Have you tested the patch with this graphics card?
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:57 AM
To: Ian Jackson
Cc: Xen-devel; Kay, Allen M
Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 16074 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-08 15:41 ` Huang2, Wei
@ 2010-10-08 15:52 ` djmagee
2010-10-13 20:47 ` Huang2, Wei
0 siblings, 1 reply; 32+ messages in thread
From: djmagee @ 2010-10-08 15:52 UTC (permalink / raw)
To: Huang2, Wei, Kay, Allen M, Ian Jackson; +Cc: Wang2, Wei, Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 5637 bytes --]
Wei,
These were guests that had never seen the catalyst
driver before. I booted each three with the graphics device and usb
devices assigned, they worked fine using the basic VGA driver, then
installed fresh Catalyst 10.9, rebooted, and each one crashed.
Let me know if there's any other info I can provide that
will help you debug. The motherboard is a DQ45CB, running xen-unstable
c/s 22155 using 'dom0_mem=768M iommu=1' on the grub line, and using
pvops Dom0 from stable-2.6.32.x commit 179eca50.
Doug Magee
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Friday, October 08, 2010 11:41 AM
To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
Cc: Xen-devel; Wang2, Wei
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
support
Hi Doug,
Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
Catalyst installation or an existing guest image? We felt this VBIOS
patch might not provide all necessary resources to driver, which got
upset. Currently we are debugging it with our driver team and will let
you know the update.
Thanks,
-Wei
From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
Sent: Friday, October 08, 2010 9:41 AM
To: Huang2, Wei; Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
support
Wei,
I've tested with a Radeon 4770 and it the VBIOS works
without a problem, through many guest (re)boots, so it seems pretty
solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
and Windows 7 (without accelerated drivers). The open radeon linux
driver works fine.
The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
in device driver), windows 7 (STOP 0x00000116, driver fails to properly
reset?), and linux (total system freeze). This seems to be different
than the 'Blank Screen' problem you report, as the driver is clearly not
functioning properly.
Doug Magee
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
Sent: Friday, October 08, 2010 9:57 AM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Yes, Catalyst driver is the one from public website. The driver still
has a minor issue with this VBIOS patch. The purpose of submitting
VBIOS patch is to get community feedbacks. After we figure out the root
cause of black screen, I will formally submit a patch for inclusion.
Thanks,
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Friday, October 08, 2010 2:21 AM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
Is Catalyst driver the one on AMD website? I think that's what I have
in my win7 guest and it matches the symptom you are describing. "lspci"
reports my ATI card is a V5700 - although it says v3750 on the box.
Where can I get a working driver?
The patch looks reasonable to me in general.
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:06 PM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Thanks for testing it out. We have tested this patch with Radeon 4850,
4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750
at hand. It is very possible this patch isn't compatible with V3750. We
will try to get hold of one for debugging. For graphics which work with
this path, users should be able to get rid of emulated gfx (such as
Cirrus). I have successfully installed a Windows guest VM using this
patch.
I also want to point out that there is still an issue. Users will see a
black screen after installing Catalyst driver. Even though the screen
appears to be black, the driver is actually functioning correctly
(3DMark can be run with external monitor). Our driver team is currently
debugging it and they believe this is easy to fix.
What is your opinion on this patch (and the solution) in general?
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Thursday, October 07, 2010 6:58 PM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
This patch did not cause any problems with Intel IGD passthrough for me.
However, the monitor remained blank if I pass through ATI Firepro V3750
either as the primary display device or the secondary device
(gfx_passthru=1/0). Passing it through as the secondary device used to
work.
Have you tested the patch with this graphics card?
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:57 AM
To: Ian Jackson
Cc: Xen-devel; Kay, Allen M
Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch
enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
Windows boot logo) can now show in passthru screen. We have tested with
various Windows and Linux guest VMs. Please help review it. We are also
looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 17856 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-08 15:52 ` djmagee
@ 2010-10-13 20:47 ` Huang2, Wei
2010-10-13 21:37 ` Huang2, Wei
0 siblings, 1 reply; 32+ messages in thread
From: Huang2, Wei @ 2010-10-13 20:47 UTC (permalink / raw)
To: djmagee@mageenet.net, Kay, Allen M, Ian Jackson; +Cc: Wang2, Wei, Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 5942 bytes --]
Hi Allen and Doug,
Could you fix the following line in save_pci_conf_space() of tools/python/xen/util/pci.py?
"for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
This solves my black screen issue. Please let me know the results.
Thanks,
-Wei
From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
Sent: Friday, October 08, 2010 10:53 AM
To: Huang2, Wei; Kay, Allen M; Ian Jackson
Cc: Xen-devel; Wang2, Wei
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Wei,
These were guests that had never seen the catalyst driver before. I booted each three with the graphics device and usb devices assigned, they worked fine using the basic VGA driver, then installed fresh Catalyst 10.9, rebooted, and each one crashed.
Let me know if there's any other info I can provide that will help you debug. The motherboard is a DQ45CB, running xen-unstable c/s 22155 using 'dom0_mem=768M iommu=1' on the grub line, and using pvops Dom0 from stable-2.6.32.x commit 179eca50.
Doug Magee
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Friday, October 08, 2010 11:41 AM
To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
Cc: Xen-devel; Wang2, Wei
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Doug,
Regarding Catalyst driver, we never saw guest crashing. Was it a fresh Catalyst installation or an existing guest image? We felt this VBIOS patch might not provide all necessary resources to driver, which got upset. Currently we are debugging it with our driver team and will let you know the update.
Thanks,
-Wei
From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
Sent: Friday, October 08, 2010 9:41 AM
To: Huang2, Wei; Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Wei,
I've tested with a Radeon 4770 and it the VBIOS works without a problem, through many guest (re)boots, so it seems pretty solid. I tested a linux guest (fairly standard Fedora 12), Windows XP, and Windows 7 (without accelerated drivers). The open radeon linux driver works fine.
The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in device driver), windows 7 (STOP 0x00000116, driver fails to properly reset?), and linux (total system freeze). This seems to be different than the 'Blank Screen' problem you report, as the driver is clearly not functioning properly.
Doug Magee
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
Sent: Friday, October 08, 2010 9:57 AM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Yes, Catalyst driver is the one from public website. The driver still has a minor issue with this VBIOS patch. The purpose of submitting VBIOS patch is to get community feedbacks. After we figure out the root cause of black screen, I will formally submit a patch for inclusion.
Thanks,
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Friday, October 08, 2010 2:21 AM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
Is Catalyst driver the one on AMD website? I think that's what I have in my win7 guest and it matches the symptom you are describing. "lspci" reports my ATI card is a V5700 - although it says v3750 on the box. Where can I get a working driver?
The patch looks reasonable to me in general.
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:06 PM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Thanks for testing it out. We have tested this patch with Radeon 4850, 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750 at hand. It is very possible this patch isn't compatible with V3750. We will try to get hold of one for debugging. For graphics which work with this path, users should be able to get rid of emulated gfx (such as Cirrus). I have successfully installed a Windows guest VM using this patch.
I also want to point out that there is still an issue. Users will see a black screen after installing Catalyst driver. Even though the screen appears to be black, the driver is actually functioning correctly (3DMark can be run with external monitor). Our driver team is currently debugging it and they believe this is easy to fix.
What is your opinion on this patch (and the solution) in general?
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Thursday, October 07, 2010 6:58 PM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
This patch did not cause any problems with Intel IGD passthrough for me. However, the monitor remained blank if I pass through ATI Firepro V3750 either as the primary display device or the secondary device (gfx_passthru=1/0). Passing it through as the secondary device used to work.
Have you tested the patch with this graphics card?
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:57 AM
To: Ian Jackson
Cc: Xen-devel; Kay, Allen M
Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 20127 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-13 20:47 ` Huang2, Wei
@ 2010-10-13 21:37 ` Huang2, Wei
2010-12-07 10:00 ` Pasi Kärkkäinen
0 siblings, 1 reply; 32+ messages in thread
From: Huang2, Wei @ 2010-10-13 21:37 UTC (permalink / raw)
To: Huang2, Wei, djmagee@mageenet.net, Kay, Allen M, Ian Jackson
Cc: Wang2, Wei, Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 6361 bytes --]
Sorry, hold on a second. This fix seems corrupt my pci config space after several runs.
-Wei
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
Sent: Wednesday, October 13, 2010 3:47 PM
To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
Cc: Wang2, Wei; Xen-devel
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen and Doug,
Could you fix the following line in save_pci_conf_space() of tools/python/xen/util/pci.py?
"for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
This solves my black screen issue. Please let me know the results.
Thanks,
-Wei
From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
Sent: Friday, October 08, 2010 10:53 AM
To: Huang2, Wei; Kay, Allen M; Ian Jackson
Cc: Xen-devel; Wang2, Wei
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Wei,
These were guests that had never seen the catalyst driver before. I booted each three with the graphics device and usb devices assigned, they worked fine using the basic VGA driver, then installed fresh Catalyst 10.9, rebooted, and each one crashed.
Let me know if there's any other info I can provide that will help you debug. The motherboard is a DQ45CB, running xen-unstable c/s 22155 using 'dom0_mem=768M iommu=1' on the grub line, and using pvops Dom0 from stable-2.6.32.x commit 179eca50.
Doug Magee
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Friday, October 08, 2010 11:41 AM
To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
Cc: Xen-devel; Wang2, Wei
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Doug,
Regarding Catalyst driver, we never saw guest crashing. Was it a fresh Catalyst installation or an existing guest image? We felt this VBIOS patch might not provide all necessary resources to driver, which got upset. Currently we are debugging it with our driver team and will let you know the update.
Thanks,
-Wei
From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
Sent: Friday, October 08, 2010 9:41 AM
To: Huang2, Wei; Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Wei,
I've tested with a Radeon 4770 and it the VBIOS works without a problem, through many guest (re)boots, so it seems pretty solid. I tested a linux guest (fairly standard Fedora 12), Windows XP, and Windows 7 (without accelerated drivers). The open radeon linux driver works fine.
The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in device driver), windows 7 (STOP 0x00000116, driver fails to properly reset?), and linux (total system freeze). This seems to be different than the 'Blank Screen' problem you report, as the driver is clearly not functioning properly.
Doug Magee
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
Sent: Friday, October 08, 2010 9:57 AM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Yes, Catalyst driver is the one from public website. The driver still has a minor issue with this VBIOS patch. The purpose of submitting VBIOS patch is to get community feedbacks. After we figure out the root cause of black screen, I will formally submit a patch for inclusion.
Thanks,
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Friday, October 08, 2010 2:21 AM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
Is Catalyst driver the one on AMD website? I think that's what I have in my win7 guest and it matches the symptom you are describing. "lspci" reports my ATI card is a V5700 - although it says v3750 on the box. Where can I get a working driver?
The patch looks reasonable to me in general.
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:06 PM
To: Kay, Allen M; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Allen,
Thanks for testing it out. We have tested this patch with Radeon 4850, 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750 at hand. It is very possible this patch isn't compatible with V3750. We will try to get hold of one for debugging. For graphics which work with this path, users should be able to get rid of emulated gfx (such as Cirrus). I have successfully installed a Windows guest VM using this patch.
I also want to point out that there is still an issue. Users will see a black screen after installing Catalyst driver. Even though the screen appears to be black, the driver is actually functioning correctly (3DMark can be run with external monitor). Our driver team is currently debugging it and they believe this is easy to fix.
What is your opinion on this patch (and the solution) in general?
-Wei
From: Kay, Allen M [mailto:allen.m.kay@intel.com]
Sent: Thursday, October 07, 2010 6:58 PM
To: Huang2, Wei; Ian Jackson
Cc: Xen-devel
Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Wei,
This patch did not cause any problems with Intel IGD passthrough for me. However, the monitor remained blank if I pass through ATI Firepro V3750 either as the primary display device or the secondary device (gfx_passthru=1/0). Passing it through as the secondary device used to work.
Have you tested the patch with this graphics card?
Allen
From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
Sent: Thursday, October 07, 2010 9:57 AM
To: Ian Jackson
Cc: Xen-devel; Kay, Allen M
Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
Hi Ian,
There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Wei Wang <wei.wang2@amd.com>
[-- Attachment #1.2: Type: text/html, Size: 21347 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-10-13 21:37 ` Huang2, Wei
@ 2010-12-07 10:00 ` Pasi Kärkkäinen
2010-12-07 10:14 ` Jean Guyader
` (2 more replies)
0 siblings, 3 replies; 32+ messages in thread
From: Pasi Kärkkäinen @ 2010-12-07 10:00 UTC (permalink / raw)
To: Huang2, Wei
Cc: Wang2, Wei, Kay, Allen M, Xen-devel, djmagee@mageenet.net,
Ian Jackson
On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> Sorry, hold on a second. This fix seems corrupt my pci config space after
> several runs.
>
Hello,
Any updates to these patches? Many users have been asking about amd/ati vga passthru stuff..
-- Pasi
>
>
> -Wei
>
>
>
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> Sent: Wednesday, October 13, 2010 3:47 PM
> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> Cc: Wang2, Wei; Xen-devel
> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> support
>
>
>
> Hi Allen and Doug,
>
>
>
> Could you fix the following line in save_pci_conf_space() of
> tools/python/xen/util/pci.py?
>
>
>
> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>
>
>
> This solves my black screen issue. Please let me know the results.
>
>
>
>
>
> Thanks,
>
> -Wei
>
>
>
> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> Sent: Friday, October 08, 2010 10:53 AM
> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> Cc: Xen-devel; Wang2, Wei
> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> support
>
>
>
> Wei,
>
> These were guests that had never seen the catalyst driver
> before. I booted each three with the graphics device and usb devices
> assigned, they worked fine using the basic VGA driver, then installed
> fresh Catalyst 10.9, rebooted, and each one crashed.
>
>
>
> Let me know if there's any other info I can provide that
> will help you debug. The motherboard is a DQ45CB, running xen-unstable
> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using pvops
> Dom0 from stable-2.6.32.x commit 179eca50.
>
>
>
> Doug Magee
>
>
>
> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> Sent: Friday, October 08, 2010 11:41 AM
> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> Cc: Xen-devel; Wang2, Wei
> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> support
>
>
>
> Hi Doug,
>
>
>
> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> Catalyst installation or an existing guest image? We felt this VBIOS patch
> might not provide all necessary resources to driver, which got upset.
> Currently we are debugging it with our driver team and will let you know
> the update.
>
>
>
> Thanks,
>
> -Wei
>
>
>
> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> Sent: Friday, October 08, 2010 9:41 AM
> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> support
>
>
>
> Wei,
>
> I've tested with a Radeon 4770 and it the VBIOS works
> without a problem, through many guest (re)boots, so it seems pretty
> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> and Windows 7 (without accelerated drivers). The open radeon linux driver
> works fine.
>
>
>
> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in
> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> reset?), and linux (total system freeze). This seems to be different than
> the `Blank Screen' problem you report, as the driver is clearly not
> functioning properly.
>
>
>
> Doug Magee
>
>
>
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> Sent: Friday, October 08, 2010 9:57 AM
> To: Kay, Allen M; Ian Jackson
> Cc: Xen-devel
> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Allen,
>
>
>
> Yes, Catalyst driver is the one from public website. The driver still has
> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> patch is to get community feedbacks. After we figure out the root cause of
> black screen, I will formally submit a patch for inclusion.
>
>
>
> Thanks,
>
> -Wei
>
>
>
> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> Sent: Friday, October 08, 2010 2:21 AM
> To: Huang2, Wei; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Wei,
>
>
>
> Is Catalyst driver the one on AMD website? I think that's what I have in
> my win7 guest and it matches the symptom you are describing. "lspci"
> reports my ATI card is a V5700 - although it says v3750 on the box. Where
> can I get a working driver?
>
>
>
> The patch looks reasonable to me in general.
>
>
>
> Allen
>
>
>
> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> Sent: Thursday, October 07, 2010 9:06 PM
> To: Kay, Allen M; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Allen,
>
>
>
> Thanks for testing it out. We have tested this patch with Radeon 4850,
> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750
> at hand. It is very possible this patch isn't compatible with V3750. We
> will try to get hold of one for debugging. For graphics which work with
> this path, users should be able to get rid of emulated gfx (such as
> Cirrus). I have successfully installed a Windows guest VM using this
> patch.
>
>
>
> I also want to point out that there is still an issue. Users will see a
> black screen after installing Catalyst driver. Even though the screen
> appears to be black, the driver is actually functioning correctly (3DMark
> can be run with external monitor). Our driver team is currently debugging
> it and they believe this is easy to fix.
>
>
>
> What is your opinion on this patch (and the solution) in general?
>
>
>
> -Wei
>
>
>
> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> Sent: Thursday, October 07, 2010 6:58 PM
> To: Huang2, Wei; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Wei,
>
>
>
> This patch did not cause any problems with Intel IGD passthrough for me.
> However, the monitor remained blank if I pass through ATI Firepro V3750
> either as the primary display device or the secondary device
> (gfx_passthru=1/0). Passing it through as the secondary device used to
> work.
>
>
>
> Have you tested the patch with this graphics card?
>
>
>
> Allen
>
>
>
> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> Sent: Thursday, October 07, 2010 9:57 AM
> To: Ian Jackson
> Cc: Xen-devel; Kay, Allen M
> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Ian,
>
>
>
> There have been a lot of interest on gfx passthru recently. This patch
> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> Windows boot logo) can now show in passthru screen. We have tested with
> various Windows and Linux guest VMs. Please help review it. We are also
> looking forward to comments and suggestions from Xen community users.
>
>
>
> Signed-off-by: Wei Huang <wei.huang2@amd.com>
>
> Signed-off-by: Wei Wang <wei.wang2@amd.com>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-07 10:00 ` Pasi Kärkkäinen
@ 2010-12-07 10:14 ` Jean Guyader
2010-12-08 5:31 ` Huang2, Wei
2010-12-10 23:40 ` Wei Huang
2 siblings, 0 replies; 32+ messages in thread
From: Jean Guyader @ 2010-12-07 10:14 UTC (permalink / raw)
To: Pasi Kärkkäinen
Cc: Xen-devel, Ian Jackson, Huang2, Wei, Kay, Allen M, Wang2, Wei,
djmagee@mageenet.net
Hi,
ATI gpu passthru should already works as a secondary display adapter (along
with the cirrus/stdvga in the guest).
This patch is to use an ATI gpu passthru without any other display
adapter in the guest.
Jean
On 7 December 2010 11:00, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
>> Sorry, hold on a second. This fix seems corrupt my pci config space after
>> several runs.
>>
>
> Hello,
>
> Any updates to these patches? Many users have been asking about amd/ati vga passthru stuff..
>
> -- Pasi
>
>>
>>
>> -Wei
>>
>>
>>
>> From: xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>> Sent: Wednesday, October 13, 2010 3:47 PM
>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>> Cc: Wang2, Wei; Xen-devel
>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>> support
>>
>>
>>
>> Hi Allen and Doug,
>>
>>
>>
>> Could you fix the following line in save_pci_conf_space() of
>> tools/python/xen/util/pci.py?
>>
>>
>>
>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>>
>>
>>
>> This solves my black screen issue. Please let me know the results.
>>
>>
>>
>>
>>
>> Thanks,
>>
>> -Wei
>>
>>
>>
>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>> Sent: Friday, October 08, 2010 10:53 AM
>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>> Cc: Xen-devel; Wang2, Wei
>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>> support
>>
>>
>>
>> Wei,
>>
>> These were guests that had never seen the catalyst driver
>> before. I booted each three with the graphics device and usb devices
>> assigned, they worked fine using the basic VGA driver, then installed
>> fresh Catalyst 10.9, rebooted, and each one crashed.
>>
>>
>>
>> Let me know if there's any other info I can provide that
>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using pvops
>> Dom0 from stable-2.6.32.x commit 179eca50.
>>
>>
>>
>> Doug Magee
>>
>>
>>
>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>> Sent: Friday, October 08, 2010 11:41 AM
>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>> Cc: Xen-devel; Wang2, Wei
>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>> support
>>
>>
>>
>> Hi Doug,
>>
>>
>>
>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
>> Catalyst installation or an existing guest image? We felt this VBIOS patch
>> might not provide all necessary resources to driver, which got upset.
>> Currently we are debugging it with our driver team and will let you know
>> the update.
>>
>>
>>
>> Thanks,
>>
>> -Wei
>>
>>
>>
>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>> Sent: Friday, October 08, 2010 9:41 AM
>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>> Cc: Xen-devel
>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>> support
>>
>>
>>
>> Wei,
>>
>> I've tested with a Radeon 4770 and it the VBIOS works
>> without a problem, through many guest (re)boots, so it seems pretty
>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
>> and Windows 7 (without accelerated drivers). The open radeon linux driver
>> works fine.
>>
>>
>>
>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in
>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
>> reset?), and linux (total system freeze). This seems to be different than
>> the `Blank Screen' problem you report, as the driver is clearly not
>> functioning properly.
>>
>>
>>
>> Doug Magee
>>
>>
>>
>> From: xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>> Sent: Friday, October 08, 2010 9:57 AM
>> To: Kay, Allen M; Ian Jackson
>> Cc: Xen-devel
>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Allen,
>>
>>
>>
>> Yes, Catalyst driver is the one from public website. The driver still has
>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
>> patch is to get community feedbacks. After we figure out the root cause of
>> black screen, I will formally submit a patch for inclusion.
>>
>>
>>
>> Thanks,
>>
>> -Wei
>>
>>
>>
>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>> Sent: Friday, October 08, 2010 2:21 AM
>> To: Huang2, Wei; Ian Jackson
>> Cc: Xen-devel
>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Wei,
>>
>>
>>
>> Is Catalyst driver the one on AMD website? I think that's what I have in
>> my win7 guest and it matches the symptom you are describing. "lspci"
>> reports my ATI card is a V5700 - although it says v3750 on the box. Where
>> can I get a working driver?
>>
>>
>>
>> The patch looks reasonable to me in general.
>>
>>
>>
>> Allen
>>
>>
>>
>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>> Sent: Thursday, October 07, 2010 9:06 PM
>> To: Kay, Allen M; Ian Jackson
>> Cc: Xen-devel
>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Allen,
>>
>>
>>
>> Thanks for testing it out. We have tested this patch with Radeon 4850,
>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750
>> at hand. It is very possible this patch isn't compatible with V3750. We
>> will try to get hold of one for debugging. For graphics which work with
>> this path, users should be able to get rid of emulated gfx (such as
>> Cirrus). I have successfully installed a Windows guest VM using this
>> patch.
>>
>>
>>
>> I also want to point out that there is still an issue. Users will see a
>> black screen after installing Catalyst driver. Even though the screen
>> appears to be black, the driver is actually functioning correctly (3DMark
>> can be run with external monitor). Our driver team is currently debugging
>> it and they believe this is easy to fix.
>>
>>
>>
>> What is your opinion on this patch (and the solution) in general?
>>
>>
>>
>> -Wei
>>
>>
>>
>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>> Sent: Thursday, October 07, 2010 6:58 PM
>> To: Huang2, Wei; Ian Jackson
>> Cc: Xen-devel
>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Wei,
>>
>>
>>
>> This patch did not cause any problems with Intel IGD passthrough for me.
>> However, the monitor remained blank if I pass through ATI Firepro V3750
>> either as the primary display device or the secondary device
>> (gfx_passthru=1/0). Passing it through as the secondary device used to
>> work.
>>
>>
>>
>> Have you tested the patch with this graphics card?
>>
>>
>>
>> Allen
>>
>>
>>
>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>> Sent: Thursday, October 07, 2010 9:57 AM
>> To: Ian Jackson
>> Cc: Xen-devel; Kay, Allen M
>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Ian,
>>
>>
>>
>> There have been a lot of interest on gfx passthru recently. This patch
>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
>> Windows boot logo) can now show in passthru screen. We have tested with
>> various Windows and Linux guest VMs. Please help review it. We are also
>> looking forward to comments and suggestions from Xen community users.
>>
>>
>>
>> Signed-off-by: Wei Huang <wei.huang2@amd.com>
>>
>> Signed-off-by: Wei Wang <wei.wang2@amd.com>
>>
>>
>>
>>
>
>> _______________________________________________
>> 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
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-07 10:00 ` Pasi Kärkkäinen
2010-12-07 10:14 ` Jean Guyader
@ 2010-12-08 5:31 ` Huang2, Wei
2010-12-08 8:44 ` Pasi Kärkkäinen
2010-12-10 23:40 ` Wei Huang
2 siblings, 1 reply; 32+ messages in thread
From: Huang2, Wei @ 2010-12-08 5:31 UTC (permalink / raw)
To: Pasi Kärkkäinen
Cc: Wang2, Wei, Kay, Allen M, Xen-devel, djmagee@mageenet.net,
Ian Jackson
Hi Pasi,
I have another patch which detects PIO and MMIO BARs on-the-fly. This should address some issues seen by the community (because BAR index varies among gfx generations). I will clean it up and submit it for testing in the next few days.
-Wei
________________________________________
From: Pasi Kärkkäinen [pasik@iki.fi]
Sent: Tuesday, December 07, 2010 4:00 AM
To: Huang2, Wei
Cc: djmagee@mageenet.net; Kay, Allen M; Ian Jackson; Wang2, Wei; Xen-devel
Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> Sorry, hold on a second. This fix seems corrupt my pci config space after
> several runs.
>
Hello,
Any updates to these patches? Many users have been asking about amd/ati vga passthru stuff..
-- Pasi
>
>
> -Wei
>
>
>
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> Sent: Wednesday, October 13, 2010 3:47 PM
> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> Cc: Wang2, Wei; Xen-devel
> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> support
>
>
>
> Hi Allen and Doug,
>
>
>
> Could you fix the following line in save_pci_conf_space() of
> tools/python/xen/util/pci.py?
>
>
>
> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>
>
>
> This solves my black screen issue. Please let me know the results.
>
>
>
>
>
> Thanks,
>
> -Wei
>
>
>
> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> Sent: Friday, October 08, 2010 10:53 AM
> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> Cc: Xen-devel; Wang2, Wei
> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> support
>
>
>
> Wei,
>
> These were guests that had never seen the catalyst driver
> before. I booted each three with the graphics device and usb devices
> assigned, they worked fine using the basic VGA driver, then installed
> fresh Catalyst 10.9, rebooted, and each one crashed.
>
>
>
> Let me know if there's any other info I can provide that
> will help you debug. The motherboard is a DQ45CB, running xen-unstable
> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using pvops
> Dom0 from stable-2.6.32.x commit 179eca50.
>
>
>
> Doug Magee
>
>
>
> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> Sent: Friday, October 08, 2010 11:41 AM
> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> Cc: Xen-devel; Wang2, Wei
> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> support
>
>
>
> Hi Doug,
>
>
>
> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> Catalyst installation or an existing guest image? We felt this VBIOS patch
> might not provide all necessary resources to driver, which got upset.
> Currently we are debugging it with our driver team and will let you know
> the update.
>
>
>
> Thanks,
>
> -Wei
>
>
>
> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> Sent: Friday, October 08, 2010 9:41 AM
> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> support
>
>
>
> Wei,
>
> I've tested with a Radeon 4770 and it the VBIOS works
> without a problem, through many guest (re)boots, so it seems pretty
> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> and Windows 7 (without accelerated drivers). The open radeon linux driver
> works fine.
>
>
>
> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in
> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> reset?), and linux (total system freeze). This seems to be different than
> the `Blank Screen' problem you report, as the driver is clearly not
> functioning properly.
>
>
>
> Doug Magee
>
>
>
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> Sent: Friday, October 08, 2010 9:57 AM
> To: Kay, Allen M; Ian Jackson
> Cc: Xen-devel
> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Allen,
>
>
>
> Yes, Catalyst driver is the one from public website. The driver still has
> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> patch is to get community feedbacks. After we figure out the root cause of
> black screen, I will formally submit a patch for inclusion.
>
>
>
> Thanks,
>
> -Wei
>
>
>
> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> Sent: Friday, October 08, 2010 2:21 AM
> To: Huang2, Wei; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Wei,
>
>
>
> Is Catalyst driver the one on AMD website? I think that's what I have in
> my win7 guest and it matches the symptom you are describing. "lspci"
> reports my ATI card is a V5700 - although it says v3750 on the box. Where
> can I get a working driver?
>
>
>
> The patch looks reasonable to me in general.
>
>
>
> Allen
>
>
>
> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> Sent: Thursday, October 07, 2010 9:06 PM
> To: Kay, Allen M; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Allen,
>
>
>
> Thanks for testing it out. We have tested this patch with Radeon 4850,
> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750
> at hand. It is very possible this patch isn't compatible with V3750. We
> will try to get hold of one for debugging. For graphics which work with
> this path, users should be able to get rid of emulated gfx (such as
> Cirrus). I have successfully installed a Windows guest VM using this
> patch.
>
>
>
> I also want to point out that there is still an issue. Users will see a
> black screen after installing Catalyst driver. Even though the screen
> appears to be black, the driver is actually functioning correctly (3DMark
> can be run with external monitor). Our driver team is currently debugging
> it and they believe this is easy to fix.
>
>
>
> What is your opinion on this patch (and the solution) in general?
>
>
>
> -Wei
>
>
>
> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> Sent: Thursday, October 07, 2010 6:58 PM
> To: Huang2, Wei; Ian Jackson
> Cc: Xen-devel
> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Wei,
>
>
>
> This patch did not cause any problems with Intel IGD passthrough for me.
> However, the monitor remained blank if I pass through ATI Firepro V3750
> either as the primary display device or the secondary device
> (gfx_passthru=1/0). Passing it through as the secondary device used to
> work.
>
>
>
> Have you tested the patch with this graphics card?
>
>
>
> Allen
>
>
>
> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> Sent: Thursday, October 07, 2010 9:57 AM
> To: Ian Jackson
> Cc: Xen-devel; Kay, Allen M
> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>
>
>
> Hi Ian,
>
>
>
> There have been a lot of interest on gfx passthru recently. This patch
> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> Windows boot logo) can now show in passthru screen. We have tested with
> various Windows and Linux guest VMs. Please help review it. We are also
> looking forward to comments and suggestions from Xen community users.
>
>
>
> Signed-off-by: Wei Huang <wei.huang2@amd.com>
>
> Signed-off-by: Wei Wang <wei.wang2@amd.com>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-08 5:31 ` Huang2, Wei
@ 2010-12-08 8:44 ` Pasi Kärkkäinen
0 siblings, 0 replies; 32+ messages in thread
From: Pasi Kärkkäinen @ 2010-12-08 8:44 UTC (permalink / raw)
To: Huang2, Wei
Cc: Wang2, Wei, Kay, Allen M, Xen-devel, djmagee@mageenet.net,
Ian Jackson
On Tue, Dec 07, 2010 at 11:31:12PM -0600, Huang2, Wei wrote:
> Hi Pasi,
>
> I have another patch which detects PIO and MMIO BARs on-the-fly. This should address some issues seen by the community (because BAR index varies among gfx generations). I will clean it up and submit it for testing in the next few days.
>
That's great!
-- Pasi
> -Wei
> ________________________________________
> From: Pasi Kärkkäinen [pasik@iki.fi]
> Sent: Tuesday, December 07, 2010 4:00 AM
> To: Huang2, Wei
> Cc: djmagee@mageenet.net; Kay, Allen M; Ian Jackson; Wang2, Wei; Xen-devel
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> > Sorry, hold on a second. This fix seems corrupt my pci config space after
> > several runs.
> >
>
> Hello,
>
> Any updates to these patches? Many users have been asking about amd/ati vga passthru stuff..
>
> -- Pasi
>
> >
> >
> > -Wei
> >
> >
> >
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > Sent: Wednesday, October 13, 2010 3:47 PM
> > To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > Cc: Wang2, Wei; Xen-devel
> > Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > support
> >
> >
> >
> > Hi Allen and Doug,
> >
> >
> >
> > Could you fix the following line in save_pci_conf_space() of
> > tools/python/xen/util/pci.py?
> >
> >
> >
> > "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
> >
> >
> >
> > This solves my black screen issue. Please let me know the results.
> >
> >
> >
> >
> >
> > Thanks,
> >
> > -Wei
> >
> >
> >
> > From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > Sent: Friday, October 08, 2010 10:53 AM
> > To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > Cc: Xen-devel; Wang2, Wei
> > Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > support
> >
> >
> >
> > Wei,
> >
> > These were guests that had never seen the catalyst driver
> > before. I booted each three with the graphics device and usb devices
> > assigned, they worked fine using the basic VGA driver, then installed
> > fresh Catalyst 10.9, rebooted, and each one crashed.
> >
> >
> >
> > Let me know if there's any other info I can provide that
> > will help you debug. The motherboard is a DQ45CB, running xen-unstable
> > c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using pvops
> > Dom0 from stable-2.6.32.x commit 179eca50.
> >
> >
> >
> > Doug Magee
> >
> >
> >
> > From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > Sent: Friday, October 08, 2010 11:41 AM
> > To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > Cc: Xen-devel; Wang2, Wei
> > Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > support
> >
> >
> >
> > Hi Doug,
> >
> >
> >
> > Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> > Catalyst installation or an existing guest image? We felt this VBIOS patch
> > might not provide all necessary resources to driver, which got upset.
> > Currently we are debugging it with our driver team and will let you know
> > the update.
> >
> >
> >
> > Thanks,
> >
> > -Wei
> >
> >
> >
> > From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > Sent: Friday, October 08, 2010 9:41 AM
> > To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > Cc: Xen-devel
> > Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > support
> >
> >
> >
> > Wei,
> >
> > I've tested with a Radeon 4770 and it the VBIOS works
> > without a problem, through many guest (re)boots, so it seems pretty
> > solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> > and Windows 7 (without accelerated drivers). The open radeon linux driver
> > works fine.
> >
> >
> >
> > The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in
> > device driver), windows 7 (STOP 0x00000116, driver fails to properly
> > reset?), and linux (total system freeze). This seems to be different than
> > the `Blank Screen' problem you report, as the driver is clearly not
> > functioning properly.
> >
> >
> >
> > Doug Magee
> >
> >
> >
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > Sent: Friday, October 08, 2010 9:57 AM
> > To: Kay, Allen M; Ian Jackson
> > Cc: Xen-devel
> > Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >
> >
> >
> > Hi Allen,
> >
> >
> >
> > Yes, Catalyst driver is the one from public website. The driver still has
> > a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> > patch is to get community feedbacks. After we figure out the root cause of
> > black screen, I will formally submit a patch for inclusion.
> >
> >
> >
> > Thanks,
> >
> > -Wei
> >
> >
> >
> > From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > Sent: Friday, October 08, 2010 2:21 AM
> > To: Huang2, Wei; Ian Jackson
> > Cc: Xen-devel
> > Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >
> >
> >
> > Hi Wei,
> >
> >
> >
> > Is Catalyst driver the one on AMD website? I think that's what I have in
> > my win7 guest and it matches the symptom you are describing. "lspci"
> > reports my ATI card is a V5700 - although it says v3750 on the box. Where
> > can I get a working driver?
> >
> >
> >
> > The patch looks reasonable to me in general.
> >
> >
> >
> > Allen
> >
> >
> >
> > From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > Sent: Thursday, October 07, 2010 9:06 PM
> > To: Kay, Allen M; Ian Jackson
> > Cc: Xen-devel
> > Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >
> >
> >
> > Hi Allen,
> >
> >
> >
> > Thanks for testing it out. We have tested this patch with Radeon 4850,
> > 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750
> > at hand. It is very possible this patch isn't compatible with V3750. We
> > will try to get hold of one for debugging. For graphics which work with
> > this path, users should be able to get rid of emulated gfx (such as
> > Cirrus). I have successfully installed a Windows guest VM using this
> > patch.
> >
> >
> >
> > I also want to point out that there is still an issue. Users will see a
> > black screen after installing Catalyst driver. Even though the screen
> > appears to be black, the driver is actually functioning correctly (3DMark
> > can be run with external monitor). Our driver team is currently debugging
> > it and they believe this is easy to fix.
> >
> >
> >
> > What is your opinion on this patch (and the solution) in general?
> >
> >
> >
> > -Wei
> >
> >
> >
> > From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > Sent: Thursday, October 07, 2010 6:58 PM
> > To: Huang2, Wei; Ian Jackson
> > Cc: Xen-devel
> > Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >
> >
> >
> > Hi Wei,
> >
> >
> >
> > This patch did not cause any problems with Intel IGD passthrough for me.
> > However, the monitor remained blank if I pass through ATI Firepro V3750
> > either as the primary display device or the secondary device
> > (gfx_passthru=1/0). Passing it through as the secondary device used to
> > work.
> >
> >
> >
> > Have you tested the patch with this graphics card?
> >
> >
> >
> > Allen
> >
> >
> >
> > From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > Sent: Thursday, October 07, 2010 9:57 AM
> > To: Ian Jackson
> > Cc: Xen-devel; Kay, Allen M
> > Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
> >
> >
> >
> > Hi Ian,
> >
> >
> >
> > There have been a lot of interest on gfx passthru recently. This patch
> > enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> > Windows boot logo) can now show in passthru screen. We have tested with
> > various Windows and Linux guest VMs. Please help review it. We are also
> > looking forward to comments and suggestions from Xen community users.
> >
> >
> >
> > Signed-off-by: Wei Huang <wei.huang2@amd.com>
> >
> > Signed-off-by: Wei Wang <wei.wang2@amd.com>
> >
> >
> >
> >
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-07 10:00 ` Pasi Kärkkäinen
2010-12-07 10:14 ` Jean Guyader
2010-12-08 5:31 ` Huang2, Wei
@ 2010-12-10 23:40 ` Wei Huang
2010-12-11 14:06 ` Sander Eikelenboom
2 siblings, 1 reply; 32+ messages in thread
From: Wei Huang @ 2010-12-10 23:40 UTC (permalink / raw)
To: Pasi Kärkkäinen
Cc: Wang2, Wei, Kay, Allen M, Xen-devel, djmagee@mageenet.net,
Ian Jackson
[-- Attachment #1: Type: text/plain, Size: 8442 bytes --]
Hi,
The attached patch supports dynamic detection of BARs (both MMIO and
PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
passthru. Please let me know whether it works better for you.
Thanks,
-Wei
On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
>> Sorry, hold on a second. This fix seems corrupt my pci config space after
>> several runs.
>>
> Hello,
>
> Any updates to these patches? Many users have been asking about amd/ati vga passthru stuff..
>
> -- Pasi
>
>>
>> -Wei
>>
>>
>>
>> From: xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>> Sent: Wednesday, October 13, 2010 3:47 PM
>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>> Cc: Wang2, Wei; Xen-devel
>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>> support
>>
>>
>>
>> Hi Allen and Doug,
>>
>>
>>
>> Could you fix the following line in save_pci_conf_space() of
>> tools/python/xen/util/pci.py?
>>
>>
>>
>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>>
>>
>>
>> This solves my black screen issue. Please let me know the results.
>>
>>
>>
>>
>>
>> Thanks,
>>
>> -Wei
>>
>>
>>
>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>> Sent: Friday, October 08, 2010 10:53 AM
>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>> Cc: Xen-devel; Wang2, Wei
>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>> support
>>
>>
>>
>> Wei,
>>
>> These were guests that had never seen the catalyst driver
>> before. I booted each three with the graphics device and usb devices
>> assigned, they worked fine using the basic VGA driver, then installed
>> fresh Catalyst 10.9, rebooted, and each one crashed.
>>
>>
>>
>> Let me know if there's any other info I can provide that
>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using pvops
>> Dom0 from stable-2.6.32.x commit 179eca50.
>>
>>
>>
>> Doug Magee
>>
>>
>>
>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>> Sent: Friday, October 08, 2010 11:41 AM
>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>> Cc: Xen-devel; Wang2, Wei
>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>> support
>>
>>
>>
>> Hi Doug,
>>
>>
>>
>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
>> Catalyst installation or an existing guest image? We felt this VBIOS patch
>> might not provide all necessary resources to driver, which got upset.
>> Currently we are debugging it with our driver team and will let you know
>> the update.
>>
>>
>>
>> Thanks,
>>
>> -Wei
>>
>>
>>
>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>> Sent: Friday, October 08, 2010 9:41 AM
>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>> Cc: Xen-devel
>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>> support
>>
>>
>>
>> Wei,
>>
>> I've tested with a Radeon 4770 and it the VBIOS works
>> without a problem, through many guest (re)boots, so it seems pretty
>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
>> and Windows 7 (without accelerated drivers). The open radeon linux driver
>> works fine.
>>
>>
>>
>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in
>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
>> reset?), and linux (total system freeze). This seems to be different than
>> the `Blank Screen' problem you report, as the driver is clearly not
>> functioning properly.
>>
>>
>>
>> Doug Magee
>>
>>
>>
>> From: xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>> Sent: Friday, October 08, 2010 9:57 AM
>> To: Kay, Allen M; Ian Jackson
>> Cc: Xen-devel
>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Allen,
>>
>>
>>
>> Yes, Catalyst driver is the one from public website. The driver still has
>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
>> patch is to get community feedbacks. After we figure out the root cause of
>> black screen, I will formally submit a patch for inclusion.
>>
>>
>>
>> Thanks,
>>
>> -Wei
>>
>>
>>
>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>> Sent: Friday, October 08, 2010 2:21 AM
>> To: Huang2, Wei; Ian Jackson
>> Cc: Xen-devel
>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Wei,
>>
>>
>>
>> Is Catalyst driver the one on AMD website? I think that's what I have in
>> my win7 guest and it matches the symptom you are describing. "lspci"
>> reports my ATI card is a V5700 - although it says v3750 on the box. Where
>> can I get a working driver?
>>
>>
>>
>> The patch looks reasonable to me in general.
>>
>>
>>
>> Allen
>>
>>
>>
>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>> Sent: Thursday, October 07, 2010 9:06 PM
>> To: Kay, Allen M; Ian Jackson
>> Cc: Xen-devel
>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Allen,
>>
>>
>>
>> Thanks for testing it out. We have tested this patch with Radeon 4850,
>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750
>> at hand. It is very possible this patch isn't compatible with V3750. We
>> will try to get hold of one for debugging. For graphics which work with
>> this path, users should be able to get rid of emulated gfx (such as
>> Cirrus). I have successfully installed a Windows guest VM using this
>> patch.
>>
>>
>>
>> I also want to point out that there is still an issue. Users will see a
>> black screen after installing Catalyst driver. Even though the screen
>> appears to be black, the driver is actually functioning correctly (3DMark
>> can be run with external monitor). Our driver team is currently debugging
>> it and they believe this is easy to fix.
>>
>>
>>
>> What is your opinion on this patch (and the solution) in general?
>>
>>
>>
>> -Wei
>>
>>
>>
>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>> Sent: Thursday, October 07, 2010 6:58 PM
>> To: Huang2, Wei; Ian Jackson
>> Cc: Xen-devel
>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Wei,
>>
>>
>>
>> This patch did not cause any problems with Intel IGD passthrough for me.
>> However, the monitor remained blank if I pass through ATI Firepro V3750
>> either as the primary display device or the secondary device
>> (gfx_passthru=1/0). Passing it through as the secondary device used to
>> work.
>>
>>
>>
>> Have you tested the patch with this graphics card?
>>
>>
>>
>> Allen
>>
>>
>>
>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>> Sent: Thursday, October 07, 2010 9:57 AM
>> To: Ian Jackson
>> Cc: Xen-devel; Kay, Allen M
>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>>
>>
>>
>> Hi Ian,
>>
>>
>>
>> There have been a lot of interest on gfx passthru recently. This patch
>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
>> Windows boot logo) can now show in passthru screen. We have tested with
>> various Windows and Linux guest VMs. Please help review it. We are also
>> looking forward to comments and suggestions from Xen community users.
>>
>>
>>
>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
>>
>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
>>
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
[-- Attachment #2: ati_vbios_patch_with_bar_detection.txt --]
[-- Type: text/plain, Size: 16513 bytes --]
diff --git a/hw/pass-through.c b/hw/pass-through.c
index 9c5620d..71d4792 100644
--- a/hw/pass-through.c
+++ b/hw/pass-through.c
@@ -1379,9 +1379,17 @@ static void pt_ioport_map(PCIDevice *d, int i,
if (e_phys != -1)
{
/* Create new mapping */
- ret = xc_domain_ioport_mapping(xc_handle, domid, e_phys,
- assigned_device->bases[i].access.pio_base, e_size,
- DPCI_ADD_MAPPING);
+ if ( vga_skip_ioport_map(d) )
+ {
+ assigned_device->bases[i].e_physbase = -1;
+ }
+ else
+ {
+ ret = xc_domain_ioport_mapping(xc_handle, domid, e_phys,
+ assigned_device->bases[i].access.pio_base, e_size,
+ DPCI_ADD_MAPPING);
+ }
+
if ( ret != 0 )
{
PT_LOG("Error: create new mapping failed!\n");
diff --git a/hw/pass-through.h b/hw/pass-through.h
index dd218f7..4ef84c4 100644
--- a/hw/pass-through.h
+++ b/hw/pass-through.h
@@ -411,6 +411,11 @@ int pt_pci_host_write(int bus, int dev, int fn, u32 addr, u32 val, int len);
void intel_pch_init(PCIBus *bus);
int register_vga_regions(struct pt_dev *real_device);
int unregister_vga_regions(struct pt_dev *real_device);
+int vga_skip_ioport_map(PCIDevice *d);
+int igd_register_vga_regions(struct pt_dev *real_device);
+int igd_unregister_vga_regions(struct pt_dev *real_device);
+int ati_register_vga_regions(struct pt_dev *real_device);
+int ati_unregister_vga_regions(struct pt_dev *real_device);
int setup_vga_pt(struct pt_dev *real_device);
PCIBus *intel_pci_bridge_init(PCIBus *bus, int devfn, uint16_t vid,
uint16_t did, const char *name, uint16_t revision);
diff --git a/hw/pci.h b/hw/pci.h
index e4cc79a..4aa0373 100644
--- a/hw/pci.h
+++ b/hw/pci.h
@@ -54,6 +54,8 @@ extern target_phys_addr_t pci_mem_base;
#define PCI_VENDOR_ID_CIRRUS 0x1013
+#define PCI_VENDOR_ID_ATI 0x1002
+
#define PCI_VENDOR_ID_IBM 0x1014
#define PCI_DEVICE_ID_IBM_OPENPIC2 0xffff
diff --git a/hw/pt-graphics.c b/hw/pt-graphics.c
index e3fdf8e..8379a9d 100644
--- a/hw/pt-graphics.c
+++ b/hw/pt-graphics.c
@@ -8,11 +8,248 @@
#include <unistd.h>
#include <sys/ioctl.h>
+#include <sys/io.h>
#include <assert.h>
extern int gfx_passthru;
extern int igd_passthru;
+/*********************************/
+/* Code for ATI GFX Passthru */
+/*********************************/
+/* ATI VBIOS Working Mechanism
+ *
+ * Generally there are three memory resources (two MMIO and one PIO)
+ * associated with modern ATI gfx. VBIOS uses special tricks to figure out
+ * BARs, instead of using regular PCI config space read.
+ *
+ * (1) VBIOS relies on I/O port 0x3C3 to retrieve PIO BAR
+ * (2) VBIOS maintains a shadow copy of PCI configure space. It retries the
+ * MMIO BARs from this shadow copy via sending I/O requests to first two
+ * registers of PIO (MMINDEX and MMDATA). The workflow is like this:
+ * MMINDEX (register 0) is written with an index value, specifying the
+ * register VBIOS wanting to access. Then the shadowed data can be
+ * read/written from MMDATA (register 1). For two MMIO BARs, the index
+ * values are 0x4010 + 4 * bar_index. For instance the index value for
+ * BAR 2 is 0x4018 (0x4010 + 4*2).
+ *
+ */
+
+#define ATI_BAR_MMINDEX_BASE 0x4010 //data written to MMINDEX for MMIO BAR1
+
+struct ati_gfx_info {
+ int initialized; /* initialized already? */
+
+ /* PIO */
+ uint32_t host_pio_base; /* host base addr of PIO */
+ uint32_t guest_pio_base; /* guest base addr of PIO */
+ uint32_t pio_bar_index; /* PIO BAR index can vary */
+ uint32_t pio_size; /* PIO size */
+
+ /* MMIO */
+ uint32_t guest_mmio_base1; /* guest base addr of MMIO 1 */
+ uint32_t mmio_bar1_index; /* guest MMIO BAR1 index */
+ uint32_t guest_mmio_base2; /* guest base addr of MMIO 2 */
+ uint32_t mmio_bar2_index; /* guest MMIO BAR2 index */
+
+ /* PIO MMINDEX access recording */
+ uint32_t pre_mmindex_data; /* previous data written to MMINDEX */
+};
+
+static struct ati_gfx_info gfx_info;
+
+/* Convert guest PIO port to host PIO port */
+static uint16_t gport_to_hport(uint16_t gport)
+{
+ return (gport - gfx_info.guest_pio_base) + gfx_info.host_pio_base;
+}
+
+/* Read host PIO port */
+static uint32_t ati_hw_in(uint16_t hport)
+{
+ unsigned val;
+
+ ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 1);
+ asm volatile ("in %1,%0":"=a"(val):"Nd"(hport));
+ ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 0);
+
+ return val;
+}
+
+/* Write data to host PIO */
+static void ati_hw_out(uint16_t hport, uint32_t data)
+{
+ ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 1);
+ asm volatile ("out %1, %0"::"Nd"(hport),"a"(data));
+ ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 0);
+}
+
+static uint32_t ati_io_regs_read(void *opaque, uint32_t addr)
+{
+ uint32_t val, index;
+
+ val = ati_hw_in(gport_to_hport(addr));
+
+ /* tweak the value if VBIOS is reading MMIO BAR1 and BAR2 */
+ if ( addr == (gfx_info.guest_pio_base + 4) )
+ {
+ index = (gfx_info.pre_mmindex_data - ATI_BAR_MMINDEX_BASE) / 4;
+
+ if ( index == gfx_info.mmio_bar1_index )
+ val = gfx_info.guest_mmio_base1 | (val & 0x0000000f);
+ else if ( index == gfx_info.mmio_bar2_index )
+ val = gfx_info.guest_mmio_base2 | (val & 0x0000000f);
+ }
+
+ return val;
+}
+
+static void ati_io_regs_write(void *opaque, uint32_t addr, uint32_t val)
+{
+ ati_hw_out(gport_to_hport(addr), val);
+
+ /* book keeping */
+ if ( addr == gfx_info.guest_pio_base )
+ gfx_info.pre_mmindex_data = val;
+}
+
+#define PCI_NUM_BARS 6
+static void ati_gfx_init(struct pt_dev *assigned)
+{
+ PCIDevice *dev = (PCIDevice *)&assigned->dev;
+ int i, mmio_bar1_index, mmio_bar2_index, pio_index;
+ PCIIORegion *r;
+
+ pio_index = mmio_bar1_index = mmio_bar2_index = -1;
+
+ /* PCI configure space only contains 6 BARs. Don't use PCI_NUM_REGIONS. */
+ for ( i = 0; i < PCI_NUM_BARS; i++ )
+ {
+ r = &dev->io_regions[i];
+
+ if ( r->size && (r->addr > 0) &&
+ (r->type == PCI_ADDRESS_SPACE_MEM ||
+ r->type == PCI_ADDRESS_SPACE_MEM_PREFETCH) )
+ {
+ if ( mmio_bar1_index < 0 )
+ mmio_bar1_index = i;
+ else
+ mmio_bar2_index = i;
+ }
+
+ if ( r->size && (r->addr > 0) && (r->type == PCI_ADDRESS_SPACE_IO) )
+ {
+ pio_index = i;
+
+ }
+ }
+
+ if ( pio_index < 0 || mmio_bar1_index < 0 || mmio_bar2_index < 0 )
+ {
+ PT_LOG("Error: can't find correct gfx memory resource BARs\n");
+ return;
+ }
+
+ register_ioport_read(dev->io_regions[pio_index].addr,
+ dev->io_regions[pio_index].size, 4, ati_io_regs_read, assigned);
+
+ register_ioport_write(dev->io_regions[pio_index].addr,
+ dev->io_regions[pio_index].size, 4, ati_io_regs_write, assigned);
+
+ /* initialize PIO fields */
+ gfx_info.guest_pio_base = dev->io_regions[pio_index].addr;
+ gfx_info.pio_size = dev->io_regions[pio_index].size;
+ gfx_info.pio_bar_index = pio_index;
+ gfx_info.host_pio_base = assigned->bases[pio_index].access.pio_base;
+
+ /* initialize MMIO fields */
+ gfx_info.guest_mmio_base1 = dev->io_regions[mmio_bar1_index].addr;
+ gfx_info.mmio_bar1_index = mmio_bar1_index;
+ gfx_info.guest_mmio_base2 = dev->io_regions[mmio_bar2_index].addr;
+ gfx_info.mmio_bar2_index = mmio_bar2_index;
+
+ gfx_info.initialized = 1;
+
+ PT_LOG("ATI GFX Guest Info:\n"
+ " pio_index=0x%08x, guest_pio_bar=0x%08x\n"
+ " mmio_bar1_index=0x%08x, guest_mmio_bar1=0x%08x\n"
+ " mmio_bar2_index=0x%08x, guest_mmio_bar2=0x%08x\n",
+ gfx_info.pio_bar_index, gfx_info.guest_pio_base,
+ gfx_info.mmio_bar1_index, gfx_info.guest_mmio_base1,
+ gfx_info.mmio_bar2_index, gfx_info.guest_mmio_base2);
+}
+
+static uint32_t ati_legacy_io_read(void *opaque, uint32_t addr)
+{
+ struct pt_dev *assigned_device = opaque;
+ PCIDevice *dev = (PCIDevice *)&assigned_device->dev;
+ uint32_t val = 0xFF;
+
+ switch( addr )
+ {
+ case 0x3c3:
+ val = dev->io_regions[gfx_info.pio_bar_index].addr >> 8;
+ /* Intercept GFX IO registers. This supposes to happen in
+ * ati_register_vga_regions(). But we cannot get guest phys IO BAR
+ * over there. */
+ if ( !gfx_info.initialized )
+ ati_gfx_init(assigned_device);
+ break;
+ default:
+ PT_LOG("ERROR: port 0x%x I/O read not handled\n", addr);
+ break;
+ }
+
+ return val;
+}
+
+static void ati_legacy_io_write(void *opaque, uint32_t addr, uint32_t val)
+{
+ PT_LOG("ERROR: port 0x%x I/O write not handled\n", addr);
+}
+
+int ati_register_vga_regions(struct pt_dev *real_device)
+{
+ PCIDevice *dev = (PCIDevice *)&real_device->dev;
+ int ret = 0;
+
+ /* We need to intercept VBIOS accesses to port 0x3C3, which returns
+ * device port I/O BAR. For the rest of legacy I/O ports, we allow direct
+ * accesses.
+ */
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
+ 0x3C0, 0x3, DPCI_ADD_MAPPING);
+
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C4,
+ 0x3C4, 0x1C, DPCI_ADD_MAPPING);
+
+ register_ioport_read(0x3c3, 1, 1, ati_legacy_io_read, real_device);
+ register_ioport_write(0x3c3, 1, 1, ati_legacy_io_write, real_device);
+
+ /* initialized on the first port 0x3C3 access in ati_gfx_init */
+ gfx_info.initialized = 0;
+
+ return ret;
+}
+
+int ati_unregister_vga_regions(struct pt_dev *real_device)
+{
+ int ret = 0;
+
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
+ 0x3C0, 0x3, DPCI_REMOVE_MAPPING);
+
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C4,
+ 0x3C4, 0x1C, DPCI_REMOVE_MAPPING);
+
+ gfx_info.initialized = 0;
+
+ return ret;
+}
+
+/*********************************/
+/* Code for Intel IGD Passthru */
+/*********************************/
static int pch_map_irq(PCIDevice *pci_dev, int irq_num)
{
PT_LOG("pch_map_irq called\n");
@@ -88,6 +325,77 @@ uint32_t igd_pci_read(PCIDevice *pci_dev, uint32_t config_addr, int len)
return val;
}
+int igd_register_vga_regions(struct pt_dev *real_device)
+{
+ u32 vendor_id, igd_opregion;
+ int ret = 0;
+
+ /* legacy I/O ports 0x3C0 -- 0x3E0 */
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
+ 0x3C0, 0x20, DPCI_ADD_MAPPING);
+
+ /* 1:1 map ASL Storage register value */
+ vendor_id = pt_pci_host_read(0, 2, 0, 0, 2);
+ igd_opregion = pt_pci_host_read(0, 2, 0, 0xfc, 4);
+ if ( (vendor_id == 0x8086) && igd_opregion )
+ {
+ ret |= xc_domain_memory_mapping(xc_handle, domid,
+ igd_opregion >> XC_PAGE_SHIFT,
+ igd_opregion >> XC_PAGE_SHIFT,
+ 2,
+ DPCI_ADD_MAPPING);
+ PT_LOG("register_vga: igd_opregion = %x\n", igd_opregion);
+ }
+
+ return ret;
+}
+
+int igd_unregister_vga_regions(struct pt_dev *real_device)
+{
+ u32 vendor_id, igd_opregion;
+ int ret = 0;
+
+ ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
+ 0x3C0, 0x20, DPCI_REMOVE_MAPPING);
+
+ vendor_id = pt_pci_host_read(0, 2, 0, 0, 2);
+ igd_opregion = pt_pci_host_read(0, 2, 0, 0xfc, 4);
+ if ( (vendor_id == 0x8086) && igd_opregion )
+ {
+ ret |= xc_domain_memory_mapping(xc_handle, domid,
+ igd_opregion >> XC_PAGE_SHIFT,
+ igd_opregion >> XC_PAGE_SHIFT,
+ 2,
+ DPCI_REMOVE_MAPPING);
+ }
+
+ return ret;
+}
+/*********************************/
+/* Generic Code for GFX Passthru */
+/*********************************/
+/* This function decides whether I/O port map should be skipped */
+int vga_skip_ioport_map(PCIDevice *d)
+{
+ struct pt_dev *dev = (struct pt_dev *)d;
+ int skip = 0;
+
+ if ( !gfx_passthru || dev->pci_dev->device_class != 0x0300 )
+ return 0;
+
+ switch( dev->pci_dev->vendor_id )
+ {
+ case PCI_VENDOR_ID_ATI:
+ case PCI_VENDOR_ID_AMD:
+ skip = 1;
+ break;
+ default:
+ skip = 0;
+ break;
+ }
+
+ return skip;
+}
/*
* register VGA resources for the domain with assigned gfx
*/
@@ -99,29 +407,31 @@ int register_vga_regions(struct pt_dev *real_device)
if ( !gfx_passthru || real_device->pci_dev->device_class != 0x0300 )
return ret;
+ /* legacy I/O ports 0x3B0 - 0x3BC */
ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3B0,
0x3B0, 0xC, DPCI_ADD_MAPPING);
-
- ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
- 0x3C0, 0x20, DPCI_ADD_MAPPING);
-
+
+ /* legacy video MMIO range 0xA0000 - 0xBFFFF */
ret |= xc_domain_memory_mapping(xc_handle, domid,
0xa0000 >> XC_PAGE_SHIFT,
0xa0000 >> XC_PAGE_SHIFT,
0x20,
DPCI_ADD_MAPPING);
- /* 1:1 map ASL Storage register value */
- vendor_id = pt_pci_host_read(0, 2, 0, 0, 2);
- igd_opregion = pt_pci_host_read(0, 2, 0, 0xfc, 4);
- if ( (vendor_id == 0x8086) && igd_opregion )
+ /* Other VGA regions are vendor specific */
+ switch( real_device->pci_dev->vendor_id )
{
- ret |= xc_domain_memory_mapping(xc_handle, domid,
- igd_opregion >> XC_PAGE_SHIFT,
- igd_opregion >> XC_PAGE_SHIFT,
- 2,
- DPCI_ADD_MAPPING);
- PT_LOG("register_vga: igd_opregion = %x\n", igd_opregion);
+ case PCI_VENDOR_ID_INTEL:
+ ret = igd_register_vga_regions(real_device);
+ break;
+ case PCI_VENDOR_ID_ATI:
+ case PCI_VENDOR_ID_AMD:
+ ret = ati_register_vga_regions(real_device);
+ break;
+ default:
+ PT_LOG("gfx card wasn't supported by Xen passthru!\n");
+ ret = 1;
+ break;
}
if ( ret != 0 )
@@ -135,33 +445,36 @@ int register_vga_regions(struct pt_dev *real_device)
*/
int unregister_vga_regions(struct pt_dev *real_device)
{
- u32 vendor_id, igd_opregion;
int ret = 0;
if ( !gfx_passthru || real_device->pci_dev->device_class != 0x0300 )
return ret;
+ /* legacy I/O ports 0x3B0 - 0x3BC */
ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3B0,
0x3B0, 0xC, DPCI_REMOVE_MAPPING);
- ret |= xc_domain_ioport_mapping(xc_handle, domid, 0x3C0,
- 0x3C0, 0x20, DPCI_REMOVE_MAPPING);
-
+ /* legacy video MMIO range 0xA0000 - 0xBFFFF */
ret |= xc_domain_memory_mapping(xc_handle, domid,
0xa0000 >> XC_PAGE_SHIFT,
0xa0000 >> XC_PAGE_SHIFT,
20,
DPCI_REMOVE_MAPPING);
- vendor_id = pt_pci_host_read(0, 2, 0, 0, 2);
- igd_opregion = pt_pci_host_read(0, 2, 0, 0xfc, 4);
- if ( (vendor_id == 0x8086) && igd_opregion )
+ /* Other VGA regions are vendor specific */
+ switch( real_device->pci_dev->vendor_id )
{
- ret |= xc_domain_memory_mapping(xc_handle, domid,
- igd_opregion >> XC_PAGE_SHIFT,
- igd_opregion >> XC_PAGE_SHIFT,
- 2,
- DPCI_REMOVE_MAPPING);
+ case PCI_VENDOR_ID_INTEL:
+ ret = igd_unregister_vga_regions(real_device);
+ break;
+ case PCI_VENDOR_ID_ATI:
+ case PCI_VENDOR_ID_AMD:
+ ret = ati_unregister_vga_regions(real_device);
+ break;
+ default:
+ PT_LOG("gfx card wasn't supported by Xen passthru!\n");
+ ret = 1;
+ break;
}
if ( ret != 0 )
@@ -231,12 +544,12 @@ int setup_vga_pt(struct pt_dev *real_device)
if ( !gfx_passthru || real_device->pci_dev->device_class != 0x0300 )
return rc;
- /* Allocated 64K for the vga bios */
- if ( !(bios = malloc(64 * 1024)) )
+ /* Allocated 128K for the vga bios */
+ if ( !(bios = malloc(128 * 1024)) )
return -1;
bios_size = get_vgabios(bios);
- if ( bios_size == 0 || bios_size > 64 * 1024)
+ if ( bios_size == 0 || bios_size > 128 * 1024)
{
PT_LOG("vga bios size (0x%x) is invalid!\n", bios_size);
rc = -1;
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply related [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-10 23:40 ` Wei Huang
@ 2010-12-11 14:06 ` Sander Eikelenboom
2010-12-11 15:38 ` Keir Fraser
0 siblings, 1 reply; 32+ messages in thread
From: Sander Eikelenboom @ 2010-12-11 14:06 UTC (permalink / raw)
To: Wei Huang
Cc: Xen-devel, Ian Jackson, Kay, Allen M, Wang2, Wei,
djmagee@mageenet.net
Do i need any previous patches for this to work ?
After applying it to xen-unstable, compiling xen results in:
make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
[ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
[ -e include/mini-os ] || ln -sf . include/mini-os
[ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
make --directory=arch/x86 OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 || exit 1;
make[3]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
ld -r -nostdlib -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib -m elf_x86_64 /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64 -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
objcopy -w -G xenos_* -G _start /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
ld -nostdlib -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib -m elf_x86_64 -T arch/x86/minios-x86_64.lds /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In function `ati_hw_out':
/usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined reference to `ioperm'
/usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined reference to `ioperm'
/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In function `ati_hw_in':
/usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined reference to `ioperm'
/usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined reference to `ioperm'
make[2]: *** [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
make[1]: *** [ioemu-stubdom] Error 2
make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
make: *** [install-stubdom] Error 2
Don't know why the include of sys/io.h doesn't seem to work
--
Sander
Saturday, December 11, 2010, 12:40:19 AM, you wrote:
> Hi,
> The attached patch supports dynamic detection of BARs (both MMIO and
> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
> passthru. Please let me know whether it works better for you.
> Thanks,
> -Wei
> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
>>> Sorry, hold on a second. This fix seems corrupt my pci config space after
>>> several runs.
>>>
>> Hello,
>>
>> Any updates to these patches? Many users have been asking about amd/ati vga passthru stuff..
>>
>> -- Pasi
>>
>>>
>>> -Wei
>>>
>>>
>>>
>>> From: xen-devel-bounces@lists.xensource.com
>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>> Sent: Wednesday, October 13, 2010 3:47 PM
>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>> Cc: Wang2, Wei; Xen-devel
>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>> support
>>>
>>>
>>>
>>> Hi Allen and Doug,
>>>
>>>
>>>
>>> Could you fix the following line in save_pci_conf_space() of
>>> tools/python/xen/util/pci.py?
>>>
>>>
>>>
>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>>>
>>>
>>>
>>> This solves my black screen issue. Please let me know the results.
>>>
>>>
>>>
>>>
>>>
>>> Thanks,
>>>
>>> -Wei
>>>
>>>
>>>
>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>> Sent: Friday, October 08, 2010 10:53 AM
>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>> Cc: Xen-devel; Wang2, Wei
>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>> support
>>>
>>>
>>>
>>> Wei,
>>>
>>> These were guests that had never seen the catalyst driver
>>> before. I booted each three with the graphics device and usb devices
>>> assigned, they worked fine using the basic VGA driver, then installed
>>> fresh Catalyst 10.9, rebooted, and each one crashed.
>>>
>>>
>>>
>>> Let me know if there's any other info I can provide that
>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using pvops
>>> Dom0 from stable-2.6.32.x commit 179eca50.
>>>
>>>
>>>
>>> Doug Magee
>>>
>>>
>>>
>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>> Sent: Friday, October 08, 2010 11:41 AM
>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>> Cc: Xen-devel; Wang2, Wei
>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>> support
>>>
>>>
>>>
>>> Hi Doug,
>>>
>>>
>>>
>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
>>> Catalyst installation or an existing guest image? We felt this VBIOS patch
>>> might not provide all necessary resources to driver, which got upset.
>>> Currently we are debugging it with our driver team and will let you know
>>> the update.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> -Wei
>>>
>>>
>>>
>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>> Sent: Friday, October 08, 2010 9:41 AM
>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>> Cc: Xen-devel
>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>> support
>>>
>>>
>>>
>>> Wei,
>>>
>>> I've tested with a Radeon 4770 and it the VBIOS works
>>> without a problem, through many guest (re)boots, so it seems pretty
>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
>>> and Windows 7 (without accelerated drivers). The open radeon linux driver
>>> works fine.
>>>
>>>
>>>
>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck in
>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
>>> reset?), and linux (total system freeze). This seems to be different than
>>> the `Blank Screen' problem you report, as the driver is clearly not
>>> functioning properly.
>>>
>>>
>>>
>>> Doug Magee
>>>
>>>
>>>
>>> From: xen-devel-bounces@lists.xensource.com
>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>> Sent: Friday, October 08, 2010 9:57 AM
>>> To: Kay, Allen M; Ian Jackson
>>> Cc: Xen-devel
>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>
>>>
>>>
>>> Hi Allen,
>>>
>>>
>>>
>>> Yes, Catalyst driver is the one from public website. The driver still has
>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
>>> patch is to get community feedbacks. After we figure out the root cause of
>>> black screen, I will formally submit a patch for inclusion.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> -Wei
>>>
>>>
>>>
>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>> Sent: Friday, October 08, 2010 2:21 AM
>>> To: Huang2, Wei; Ian Jackson
>>> Cc: Xen-devel
>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>
>>>
>>>
>>> Hi Wei,
>>>
>>>
>>>
>>> Is Catalyst driver the one on AMD website? I think that's what I have in
>>> my win7 guest and it matches the symptom you are describing. "lspci"
>>> reports my ATI card is a V5700 - although it says v3750 on the box. Where
>>> can I get a working driver?
>>>
>>>
>>>
>>> The patch looks reasonable to me in general.
>>>
>>>
>>>
>>> Allen
>>>
>>>
>>>
>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>> Sent: Thursday, October 07, 2010 9:06 PM
>>> To: Kay, Allen M; Ian Jackson
>>> Cc: Xen-devel
>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>
>>>
>>>
>>> Hi Allen,
>>>
>>>
>>>
>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have V3750
>>> at hand. It is very possible this patch isn't compatible with V3750. We
>>> will try to get hold of one for debugging. For graphics which work with
>>> this path, users should be able to get rid of emulated gfx (such as
>>> Cirrus). I have successfully installed a Windows guest VM using this
>>> patch.
>>>
>>>
>>>
>>> I also want to point out that there is still an issue. Users will see a
>>> black screen after installing Catalyst driver. Even though the screen
>>> appears to be black, the driver is actually functioning correctly (3DMark
>>> can be run with external monitor). Our driver team is currently debugging
>>> it and they believe this is easy to fix.
>>>
>>>
>>>
>>> What is your opinion on this patch (and the solution) in general?
>>>
>>>
>>>
>>> -Wei
>>>
>>>
>>>
>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>> Sent: Thursday, October 07, 2010 6:58 PM
>>> To: Huang2, Wei; Ian Jackson
>>> Cc: Xen-devel
>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>
>>>
>>>
>>> Hi Wei,
>>>
>>>
>>>
>>> This patch did not cause any problems with Intel IGD passthrough for me.
>>> However, the monitor remained blank if I pass through ATI Firepro V3750
>>> either as the primary display device or the secondary device
>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
>>> work.
>>>
>>>
>>>
>>> Have you tested the patch with this graphics card?
>>>
>>>
>>>
>>> Allen
>>>
>>>
>>>
>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>> Sent: Thursday, October 07, 2010 9:57 AM
>>> To: Ian Jackson
>>> Cc: Xen-devel; Kay, Allen M
>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>
>>>
>>>
>>> Hi Ian,
>>>
>>>
>>>
>>> There have been a lot of interest on gfx passthru recently. This patch
>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
>>> Windows boot logo) can now show in passthru screen. We have tested with
>>> various Windows and Linux guest VMs. Please help review it. We are also
>>> looking forward to comments and suggestions from Xen community users.
>>>
>>>
>>>
>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
>>>
>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>
--
Best regards,
Sander mailto:linux@eikelenboom.it
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-11 14:06 ` Sander Eikelenboom
@ 2010-12-11 15:38 ` Keir Fraser
2010-12-12 6:19 ` Huang2, Wei
0 siblings, 1 reply; 32+ messages in thread
From: Keir Fraser @ 2010-12-11 15:38 UTC (permalink / raw)
To: Sander Eikelenboom, Wei Huang
Cc: Wang2, Wei, Kay, Allen M, djmagee@mageenet.net, Xen-devel,
Ian Jackson
The patch would need some work to make it suitable for check in and get it
working for stubdom. At the very least the ioperm() calls would need
removing completely, or stubbing out for the stubdom build.
-- Keir
On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
> Do i need any previous patches for this to work ?
>
> After applying it to xen-unstable, compiling xen results in:
>
> make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
> [ -e include/mini-os ] || ln -sf . include/mini-os
> [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
> make --directory=arch/x86
> OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
> exit 1;
> make[3]: Entering directory
> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory
> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> ld -r -nostdlib
> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> -m elf_x86_64
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
> .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
> -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
> -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> objcopy -w -G xenos_* -G _start
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> ld -nostdlib
> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> -m elf_x86_64 -T arch/x86/minios-x86_64.lds
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> function `ati_hw_out':
> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
> reference to `ioperm'
> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
> reference to `ioperm'
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> function `ati_hw_in':
> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
> reference to `ioperm'
> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
> reference to `ioperm'
> make[2]: ***
> [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
> make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> make[1]: *** [ioemu-stubdom] Error 2
> make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
> make: *** [install-stubdom] Error 2
>
> Don't know why the include of sys/io.h doesn't seem to work
> --
>
> Sander
>
> Saturday, December 11, 2010, 12:40:19 AM, you wrote:
>
>> Hi,
>
>> The attached patch supports dynamic detection of BARs (both MMIO and
>> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
>> passthru. Please let me know whether it works better for you.
>
>> Thanks,
>> -Wei
>
>> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
>>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
>>>> Sorry, hold on a second. This fix seems corrupt my pci config space
>>>> after
>>>> several runs.
>>>>
>>> Hello,
>>>
>>> Any updates to these patches? Many users have been asking about amd/ati vga
>>> passthru stuff..
>>>
>>> -- Pasi
>>>
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: xen-devel-bounces@lists.xensource.com
>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>> Sent: Wednesday, October 13, 2010 3:47 PM
>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>> Cc: Wang2, Wei; Xen-devel
>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Hi Allen and Doug,
>>>>
>>>>
>>>>
>>>> Could you fix the following line in save_pci_conf_space() of
>>>> tools/python/xen/util/pci.py?
>>>>
>>>>
>>>>
>>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>>>>
>>>>
>>>>
>>>> This solves my black screen issue. Please let me know the results.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>> Sent: Friday, October 08, 2010 10:53 AM
>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel; Wang2, Wei
>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Wei,
>>>>
>>>> These were guests that had never seen the catalyst
>>>> driver
>>>> before. I booted each three with the graphics device and usb devices
>>>> assigned, they worked fine using the basic VGA driver, then installed
>>>> fresh Catalyst 10.9, rebooted, and each one crashed.
>>>>
>>>>
>>>>
>>>> Let me know if there's any other info I can provide
>>>> that
>>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
>>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
>>>> pvops
>>>> Dom0 from stable-2.6.32.x commit 179eca50.
>>>>
>>>>
>>>>
>>>> Doug Magee
>>>>
>>>>
>>>>
>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>> Sent: Friday, October 08, 2010 11:41 AM
>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel; Wang2, Wei
>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Hi Doug,
>>>>
>>>>
>>>>
>>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
>>>> Catalyst installation or an existing guest image? We felt this VBIOS
>>>> patch
>>>> might not provide all necessary resources to driver, which got upset.
>>>> Currently we are debugging it with our driver team and will let you
>>>> know
>>>> the update.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>> Sent: Friday, October 08, 2010 9:41 AM
>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Wei,
>>>>
>>>> I've tested with a Radeon 4770 and it the VBIOS works
>>>> without a problem, through many guest (re)boots, so it seems pretty
>>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
>>>> and Windows 7 (without accelerated drivers). The open radeon linux
>>>> driver
>>>> works fine.
>>>>
>>>>
>>>>
>>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
>>>> in
>>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
>>>> reset?), and linux (total system freeze). This seems to be different
>>>> than
>>>> the `Blank Screen' problem you report, as the driver is clearly not
>>>> functioning properly.
>>>>
>>>>
>>>>
>>>> Doug Magee
>>>>
>>>>
>>>>
>>>> From: xen-devel-bounces@lists.xensource.com
>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>> Sent: Friday, October 08, 2010 9:57 AM
>>>> To: Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Hi Allen,
>>>>
>>>>
>>>>
>>>> Yes, Catalyst driver is the one from public website. The driver still
>>>> has
>>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
>>>> patch is to get community feedbacks. After we figure out the root cause
>>>> of
>>>> black screen, I will formally submit a patch for inclusion.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>> Sent: Friday, October 08, 2010 2:21 AM
>>>> To: Huang2, Wei; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>
>>>>
>>>>
>>>> Hi Wei,
>>>>
>>>>
>>>>
>>>> Is Catalyst driver the one on AMD website? I think that's what I have
>>>> in
>>>> my win7 guest and it matches the symptom you are describing. "lspci"
>>>> reports my ATI card is a V5700 - although it says v3750 on the box.
>>>> Where
>>>> can I get a working driver?
>>>>
>>>>
>>>>
>>>> The patch looks reasonable to me in general.
>>>>
>>>>
>>>>
>>>> Allen
>>>>
>>>>
>>>>
>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>> Sent: Thursday, October 07, 2010 9:06 PM
>>>> To: Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>
>>>>
>>>>
>>>> Hi Allen,
>>>>
>>>>
>>>>
>>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
>>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
>>>> V3750
>>>> at hand. It is very possible this patch isn't compatible with V3750. We
>>>> will try to get hold of one for debugging. For graphics which work with
>>>> this path, users should be able to get rid of emulated gfx (such as
>>>> Cirrus). I have successfully installed a Windows guest VM using this
>>>> patch.
>>>>
>>>>
>>>>
>>>> I also want to point out that there is still an issue. Users will see a
>>>> black screen after installing Catalyst driver. Even though the screen
>>>> appears to be black, the driver is actually functioning correctly
>>>> (3DMark
>>>> can be run with external monitor). Our driver team is currently
>>>> debugging
>>>> it and they believe this is easy to fix.
>>>>
>>>>
>>>>
>>>> What is your opinion on this patch (and the solution) in general?
>>>>
>>>>
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>> Sent: Thursday, October 07, 2010 6:58 PM
>>>> To: Huang2, Wei; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>
>>>>
>>>>
>>>> Hi Wei,
>>>>
>>>>
>>>>
>>>> This patch did not cause any problems with Intel IGD passthrough for
>>>> me.
>>>> However, the monitor remained blank if I pass through ATI Firepro V3750
>>>> either as the primary display device or the secondary device
>>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
>>>> work.
>>>>
>>>>
>>>>
>>>> Have you tested the patch with this graphics card?
>>>>
>>>>
>>>>
>>>> Allen
>>>>
>>>>
>>>>
>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>> Sent: Thursday, October 07, 2010 9:57 AM
>>>> To: Ian Jackson
>>>> Cc: Xen-devel; Kay, Allen M
>>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>
>>>>
>>>>
>>>> Hi Ian,
>>>>
>>>>
>>>>
>>>> There have been a lot of interest on gfx passthru recently. This patch
>>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
>>>> Windows boot logo) can now show in passthru screen. We have tested with
>>>> various Windows and Linux guest VMs. Please help review it. We are also
>>>> looking forward to comments and suggestions from Xen community users.
>>>>
>>>>
>>>>
>>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
>>>>
>>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>>
>
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-11 15:38 ` Keir Fraser
@ 2010-12-12 6:19 ` Huang2, Wei
2010-12-12 19:10 ` Sander Eikelenboom
` (2 more replies)
0 siblings, 3 replies; 32+ messages in thread
From: Huang2, Wei @ 2010-12-12 6:19 UTC (permalink / raw)
To: Keir Fraser, Sander Eikelenboom
Cc: Wang2, Wei, Kay, Allen M, djmagee@mageenet.net, Xen-devel,
Ian Jackson
This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
Thanks,
-Wei
________________________________________
From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
Sent: Saturday, December 11, 2010 9:38 AM
To: Sander Eikelenboom; Huang2, Wei
Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
The patch would need some work to make it suitable for check in and get it
working for stubdom. At the very least the ioperm() calls would need
removing completely, or stubbing out for the stubdom build.
-- Keir
On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
> Do i need any previous patches for this to work ?
>
> After applying it to xen-unstable, compiling xen results in:
>
> make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
> [ -e include/mini-os ] || ln -sf . include/mini-os
> [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
> make --directory=arch/x86
> OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
> exit 1;
> make[3]: Entering directory
> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory
> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> ld -r -nostdlib
> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> -m elf_x86_64
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
> .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
> -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
> -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> objcopy -w -G xenos_* -G _start
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> ld -nostdlib
> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> -m elf_x86_64 -T arch/x86/minios-x86_64.lds
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> function `ati_hw_out':
> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
> reference to `ioperm'
> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
> reference to `ioperm'
> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> function `ati_hw_in':
> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
> reference to `ioperm'
> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
> reference to `ioperm'
> make[2]: ***
> [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
> make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> make[1]: *** [ioemu-stubdom] Error 2
> make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
> make: *** [install-stubdom] Error 2
>
> Don't know why the include of sys/io.h doesn't seem to work
> --
>
> Sander
>
> Saturday, December 11, 2010, 12:40:19 AM, you wrote:
>
>> Hi,
>
>> The attached patch supports dynamic detection of BARs (both MMIO and
>> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
>> passthru. Please let me know whether it works better for you.
>
>> Thanks,
>> -Wei
>
>> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
>>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
>>>> Sorry, hold on a second. This fix seems corrupt my pci config space
>>>> after
>>>> several runs.
>>>>
>>> Hello,
>>>
>>> Any updates to these patches? Many users have been asking about amd/ati vga
>>> passthru stuff..
>>>
>>> -- Pasi
>>>
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: xen-devel-bounces@lists.xensource.com
>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>> Sent: Wednesday, October 13, 2010 3:47 PM
>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>> Cc: Wang2, Wei; Xen-devel
>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Hi Allen and Doug,
>>>>
>>>>
>>>>
>>>> Could you fix the following line in save_pci_conf_space() of
>>>> tools/python/xen/util/pci.py?
>>>>
>>>>
>>>>
>>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>>>>
>>>>
>>>>
>>>> This solves my black screen issue. Please let me know the results.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>> Sent: Friday, October 08, 2010 10:53 AM
>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel; Wang2, Wei
>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Wei,
>>>>
>>>> These were guests that had never seen the catalyst
>>>> driver
>>>> before. I booted each three with the graphics device and usb devices
>>>> assigned, they worked fine using the basic VGA driver, then installed
>>>> fresh Catalyst 10.9, rebooted, and each one crashed.
>>>>
>>>>
>>>>
>>>> Let me know if there's any other info I can provide
>>>> that
>>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
>>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
>>>> pvops
>>>> Dom0 from stable-2.6.32.x commit 179eca50.
>>>>
>>>>
>>>>
>>>> Doug Magee
>>>>
>>>>
>>>>
>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>> Sent: Friday, October 08, 2010 11:41 AM
>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel; Wang2, Wei
>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Hi Doug,
>>>>
>>>>
>>>>
>>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
>>>> Catalyst installation or an existing guest image? We felt this VBIOS
>>>> patch
>>>> might not provide all necessary resources to driver, which got upset.
>>>> Currently we are debugging it with our driver team and will let you
>>>> know
>>>> the update.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>> Sent: Friday, October 08, 2010 9:41 AM
>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Wei,
>>>>
>>>> I've tested with a Radeon 4770 and it the VBIOS works
>>>> without a problem, through many guest (re)boots, so it seems pretty
>>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
>>>> and Windows 7 (without accelerated drivers). The open radeon linux
>>>> driver
>>>> works fine.
>>>>
>>>>
>>>>
>>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
>>>> in
>>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
>>>> reset?), and linux (total system freeze). This seems to be different
>>>> than
>>>> the `Blank Screen' problem you report, as the driver is clearly not
>>>> functioning properly.
>>>>
>>>>
>>>>
>>>> Doug Magee
>>>>
>>>>
>>>>
>>>> From: xen-devel-bounces@lists.xensource.com
>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>> Sent: Friday, October 08, 2010 9:57 AM
>>>> To: Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>> support
>>>>
>>>>
>>>>
>>>> Hi Allen,
>>>>
>>>>
>>>>
>>>> Yes, Catalyst driver is the one from public website. The driver still
>>>> has
>>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
>>>> patch is to get community feedbacks. After we figure out the root cause
>>>> of
>>>> black screen, I will formally submit a patch for inclusion.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>> Sent: Friday, October 08, 2010 2:21 AM
>>>> To: Huang2, Wei; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>
>>>>
>>>>
>>>> Hi Wei,
>>>>
>>>>
>>>>
>>>> Is Catalyst driver the one on AMD website? I think that's what I have
>>>> in
>>>> my win7 guest and it matches the symptom you are describing. "lspci"
>>>> reports my ATI card is a V5700 - although it says v3750 on the box.
>>>> Where
>>>> can I get a working driver?
>>>>
>>>>
>>>>
>>>> The patch looks reasonable to me in general.
>>>>
>>>>
>>>>
>>>> Allen
>>>>
>>>>
>>>>
>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>> Sent: Thursday, October 07, 2010 9:06 PM
>>>> To: Kay, Allen M; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>
>>>>
>>>>
>>>> Hi Allen,
>>>>
>>>>
>>>>
>>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
>>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
>>>> V3750
>>>> at hand. It is very possible this patch isn't compatible with V3750. We
>>>> will try to get hold of one for debugging. For graphics which work with
>>>> this path, users should be able to get rid of emulated gfx (such as
>>>> Cirrus). I have successfully installed a Windows guest VM using this
>>>> patch.
>>>>
>>>>
>>>>
>>>> I also want to point out that there is still an issue. Users will see a
>>>> black screen after installing Catalyst driver. Even though the screen
>>>> appears to be black, the driver is actually functioning correctly
>>>> (3DMark
>>>> can be run with external monitor). Our driver team is currently
>>>> debugging
>>>> it and they believe this is easy to fix.
>>>>
>>>>
>>>>
>>>> What is your opinion on this patch (and the solution) in general?
>>>>
>>>>
>>>>
>>>> -Wei
>>>>
>>>>
>>>>
>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>> Sent: Thursday, October 07, 2010 6:58 PM
>>>> To: Huang2, Wei; Ian Jackson
>>>> Cc: Xen-devel
>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>
>>>>
>>>>
>>>> Hi Wei,
>>>>
>>>>
>>>>
>>>> This patch did not cause any problems with Intel IGD passthrough for
>>>> me.
>>>> However, the monitor remained blank if I pass through ATI Firepro V3750
>>>> either as the primary display device or the secondary device
>>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
>>>> work.
>>>>
>>>>
>>>>
>>>> Have you tested the patch with this graphics card?
>>>>
>>>>
>>>>
>>>> Allen
>>>>
>>>>
>>>>
>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>> Sent: Thursday, October 07, 2010 9:57 AM
>>>> To: Ian Jackson
>>>> Cc: Xen-devel; Kay, Allen M
>>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>
>>>>
>>>>
>>>> Hi Ian,
>>>>
>>>>
>>>>
>>>> There have been a lot of interest on gfx passthru recently. This patch
>>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
>>>> Windows boot logo) can now show in passthru screen. We have tested with
>>>> various Windows and Linux guest VMs. Please help review it. We are also
>>>> looking forward to comments and suggestions from Xen community users.
>>>>
>>>>
>>>>
>>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
>>>>
>>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>>
>
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-12 6:19 ` Huang2, Wei
@ 2010-12-12 19:10 ` Sander Eikelenboom
2010-12-13 20:17 ` Sander Eikelenboom
2011-01-06 17:23 ` Pasi Kärkkäinen
2 siblings, 0 replies; 32+ messages in thread
From: Sander Eikelenboom @ 2010-12-12 19:10 UTC (permalink / raw)
To: Huang2, Wei, Stefano Stabellini, Konrad Rzeszutek Wilk; +Cc: Xen-devel
[-- Attachment #1: Type: text/plain, Size: 15989 bytes --]
Hi Wei/Stefano,
I have tried this patch, but i don't succeed in passing a ATI HD 3450 to a windows HVM.
I have applied the patch to the latest xen-unstable, and rebuild with make "tools && make install-tools"
AMD iommu is enabled, passthrough of devices to PV-domains works ok.
Attached (created when te domU has been running for sometime):
- xm info
- xm dmesg
- dmesg
- lspci -k
- lspci -vvvknn (verbose)
- winhvm.cfg (domU config file, has a install of winxp and the latest catalyst drivers)
- qemu-dm-winhvm.log
- xend.log
- output of debug keys (Q,i,M)
Dom0 is latest from Jeremy's xen/next2.6.32.x branch.
The domain does run, and i can connect to a previously installed vnc (resulting in 4 color vga display), the driver doesn't recognize the ati hd 3450.
--
Sander
Sunday, December 12, 2010, 7:19:08 AM, you wrote:
> This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
> Thanks,
> -Wei
> ________________________________________
> From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> Sent: Saturday, December 11, 2010 9:38 AM
> To: Sander Eikelenboom; Huang2, Wei
> Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> The patch would need some work to make it suitable for check in and get it
> working for stubdom. At the very least the ioperm() calls would need
> removing completely, or stubbing out for the stubdom build.
> -- Keir
> On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
>> Do i need any previous patches for this to work ?
>>
>> After applying it to xen-unstable, compiling xen results in:
>>
>> make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
>> [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
>> [ -e include/mini-os ] || ln -sf . include/mini-os
>> [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
>> make --directory=arch/x86
>> OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
>> exit 1;
>> make[3]: Entering directory
>> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory
>> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
>> ld -r -nostdlib
>> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
>> -m elf_x86_64
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
>> .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
>> -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
>> -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>> objcopy -w -G xenos_* -G _start
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>> ld -nostdlib
>> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
>> -m elf_x86_64 -T arch/x86/minios-x86_64.lds
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
>> function `ati_hw_out':
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
>> reference to `ioperm'
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
>> reference to `ioperm'
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
>> function `ati_hw_in':
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
>> reference to `ioperm'
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
>> reference to `ioperm'
>> make[2]: ***
>> [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
>> make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
>> make[1]: *** [ioemu-stubdom] Error 2
>> make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
>> make: *** [install-stubdom] Error 2
>>
>> Don't know why the include of sys/io.h doesn't seem to work
>> --
>>
>> Sander
>>
>> Saturday, December 11, 2010, 12:40:19 AM, you wrote:
>>
>>> Hi,
>>
>>> The attached patch supports dynamic detection of BARs (both MMIO and
>>> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
>>> passthru. Please let me know whether it works better for you.
>>
>>> Thanks,
>>> -Wei
>>
>>> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
>>>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
>>>>> Sorry, hold on a second. This fix seems corrupt my pci config space
>>>>> after
>>>>> several runs.
>>>>>
>>>> Hello,
>>>>
>>>> Any updates to these patches? Many users have been asking about amd/ati vga
>>>> passthru stuff..
>>>>
>>>> -- Pasi
>>>>
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: xen-devel-bounces@lists.xensource.com
>>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>>> Sent: Wednesday, October 13, 2010 3:47 PM
>>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>>> Cc: Wang2, Wei; Xen-devel
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Hi Allen and Doug,
>>>>>
>>>>>
>>>>>
>>>>> Could you fix the following line in save_pci_conf_space() of
>>>>> tools/python/xen/util/pci.py?
>>>>>
>>>>>
>>>>>
>>>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>>>>>
>>>>>
>>>>>
>>>>> This solves my black screen issue. Please let me know the results.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>>> Sent: Friday, October 08, 2010 10:53 AM
>>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel; Wang2, Wei
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Wei,
>>>>>
>>>>> These were guests that had never seen the catalyst
>>>>> driver
>>>>> before. I booted each three with the graphics device and usb devices
>>>>> assigned, they worked fine using the basic VGA driver, then installed
>>>>> fresh Catalyst 10.9, rebooted, and each one crashed.
>>>>>
>>>>>
>>>>>
>>>>> Let me know if there's any other info I can provide
>>>>> that
>>>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
>>>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
>>>>> pvops
>>>>> Dom0 from stable-2.6.32.x commit 179eca50.
>>>>>
>>>>>
>>>>>
>>>>> Doug Magee
>>>>>
>>>>>
>>>>>
>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>> Sent: Friday, October 08, 2010 11:41 AM
>>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel; Wang2, Wei
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Hi Doug,
>>>>>
>>>>>
>>>>>
>>>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
>>>>> Catalyst installation or an existing guest image? We felt this VBIOS
>>>>> patch
>>>>> might not provide all necessary resources to driver, which got upset.
>>>>> Currently we are debugging it with our driver team and will let you
>>>>> know
>>>>> the update.
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>>> Sent: Friday, October 08, 2010 9:41 AM
>>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Wei,
>>>>>
>>>>> I've tested with a Radeon 4770 and it the VBIOS works
>>>>> without a problem, through many guest (re)boots, so it seems pretty
>>>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
>>>>> and Windows 7 (without accelerated drivers). The open radeon linux
>>>>> driver
>>>>> works fine.
>>>>>
>>>>>
>>>>>
>>>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
>>>>> in
>>>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
>>>>> reset?), and linux (total system freeze). This seems to be different
>>>>> than
>>>>> the `Blank Screen' problem you report, as the driver is clearly not
>>>>> functioning properly.
>>>>>
>>>>>
>>>>>
>>>>> Doug Magee
>>>>>
>>>>>
>>>>>
>>>>> From: xen-devel-bounces@lists.xensource.com
>>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>>> Sent: Friday, October 08, 2010 9:57 AM
>>>>> To: Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Hi Allen,
>>>>>
>>>>>
>>>>>
>>>>> Yes, Catalyst driver is the one from public website. The driver still
>>>>> has
>>>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
>>>>> patch is to get community feedbacks. After we figure out the root cause
>>>>> of
>>>>> black screen, I will formally submit a patch for inclusion.
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>>> Sent: Friday, October 08, 2010 2:21 AM
>>>>> To: Huang2, Wei; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Wei,
>>>>>
>>>>>
>>>>>
>>>>> Is Catalyst driver the one on AMD website? I think that's what I have
>>>>> in
>>>>> my win7 guest and it matches the symptom you are describing. "lspci"
>>>>> reports my ATI card is a V5700 - although it says v3750 on the box.
>>>>> Where
>>>>> can I get a working driver?
>>>>>
>>>>>
>>>>>
>>>>> The patch looks reasonable to me in general.
>>>>>
>>>>>
>>>>>
>>>>> Allen
>>>>>
>>>>>
>>>>>
>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>> Sent: Thursday, October 07, 2010 9:06 PM
>>>>> To: Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Allen,
>>>>>
>>>>>
>>>>>
>>>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
>>>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
>>>>> V3750
>>>>> at hand. It is very possible this patch isn't compatible with V3750. We
>>>>> will try to get hold of one for debugging. For graphics which work with
>>>>> this path, users should be able to get rid of emulated gfx (such as
>>>>> Cirrus). I have successfully installed a Windows guest VM using this
>>>>> patch.
>>>>>
>>>>>
>>>>>
>>>>> I also want to point out that there is still an issue. Users will see a
>>>>> black screen after installing Catalyst driver. Even though the screen
>>>>> appears to be black, the driver is actually functioning correctly
>>>>> (3DMark
>>>>> can be run with external monitor). Our driver team is currently
>>>>> debugging
>>>>> it and they believe this is easy to fix.
>>>>>
>>>>>
>>>>>
>>>>> What is your opinion on this patch (and the solution) in general?
>>>>>
>>>>>
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>>> Sent: Thursday, October 07, 2010 6:58 PM
>>>>> To: Huang2, Wei; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Wei,
>>>>>
>>>>>
>>>>>
>>>>> This patch did not cause any problems with Intel IGD passthrough for
>>>>> me.
>>>>> However, the monitor remained blank if I pass through ATI Firepro V3750
>>>>> either as the primary display device or the secondary device
>>>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
>>>>> work.
>>>>>
>>>>>
>>>>>
>>>>> Have you tested the patch with this graphics card?
>>>>>
>>>>>
>>>>>
>>>>> Allen
>>>>>
>>>>>
>>>>>
>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>> Sent: Thursday, October 07, 2010 9:57 AM
>>>>> To: Ian Jackson
>>>>> Cc: Xen-devel; Kay, Allen M
>>>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Ian,
>>>>>
>>>>>
>>>>>
>>>>> There have been a lot of interest on gfx passthru recently. This patch
>>>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
>>>>> Windows boot logo) can now show in passthru screen. We have tested with
>>>>> various Windows and Linux guest VMs. Please help review it. We are also
>>>>> looking forward to comments and suggestions from Xen community users.
>>>>>
>>>>>
>>>>>
>>>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
>>>>>
>>>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> http://lists.xensource.com/xen-devel
>>>>
>>
>>
>>
--
Best regards,
Sander mailto:linux@eikelenboom.it
[-- Attachment #2: debug-keys.txt --]
[-- Type: text/plain, Size: 20327 bytes --]
(XEN) [2010-12-12 18:38:31] ==== PCI devices ====
(XEN) [2010-12-12 18:38:31] 0b:00.0 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 0a:00.7 - dom 13 - MSIs < >
(XEN) [2010-12-12 18:38:31] 0a:00.6 - dom 13 - MSIs < >
(XEN) [2010-12-12 18:38:31] 0a:00.5 - dom 13 - MSIs < >
(XEN) [2010-12-12 18:38:31] 0a:00.4 - dom 13 - MSIs < >
(XEN) [2010-12-12 18:38:31] 0a:00.3 - dom 13 - MSIs < >
(XEN) [2010-12-12 18:38:31] 0a:00.2 - dom 13 - MSIs < >
(XEN) [2010-12-12 18:38:31] 0a:00.1 - dom 13 - MSIs < >
(XEN) [2010-12-12 18:38:31] 0a:00.0 - dom 13 - MSIs < >
(XEN) [2010-12-12 18:38:31] 09:00.0 - dom 0 - MSIs < 66 >
(XEN) [2010-12-12 18:38:31] 08:00.0 - dom 0 - MSIs < 67 >
(XEN) [2010-12-12 18:38:31] 07:01.2 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 07:01.1 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 07:01.0 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 06:00.0 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 05:00.1 - dom 14 - MSIs < >
(XEN) [2010-12-12 18:38:31] 05:00.0 - dom 14 - MSIs < >
(XEN) [2010-12-12 18:38:31] 04:00.7 - dom 9 - MSIs < >
(XEN) [2010-12-12 18:38:31] 04:00.6 - dom 9 - MSIs < >
(XEN) [2010-12-12 18:38:31] 04:00.5 - dom 9 - MSIs < >
(XEN) [2010-12-12 18:38:31] 04:00.4 - dom 9 - MSIs < >
(XEN) [2010-12-12 18:38:31] 04:00.3 - dom 9 - MSIs < >
(XEN) [2010-12-12 18:38:31] 04:00.2 - dom 9 - MSIs < >
(XEN) [2010-12-12 18:38:31] 04:00.1 - dom 9 - MSIs < >
(XEN) [2010-12-12 18:38:31] 04:00.0 - dom 9 - MSIs < >
(XEN) [2010-12-12 18:38:31] 03:06.0 - dom 11 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:18.4 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:18.3 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:18.2 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:18.1 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:18.0 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:16.2 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:16.0 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:15.0 - dom 0 - MSIs < 64 >
(XEN) [2010-12-12 18:38:31] 00:14.5 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:14.4 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:14.3 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:14.0 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:13.2 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:13.0 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:12.2 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:12.0 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:11.0 - dom 0 - MSIs < 65 >
(XEN) [2010-12-12 18:38:31] 00:0d.0 - dom 0 - MSIs < 63 >
(XEN) [2010-12-12 18:38:31] 00:0b.0 - dom 0 - MSIs < 62 >
(XEN) [2010-12-12 18:38:31] 00:0a.0 - dom 0 - MSIs < 61 >
(XEN) [2010-12-12 18:38:31] 00:06.0 - dom 0 - MSIs < 60 >
(XEN) [2010-12-12 18:38:31] 00:05.0 - dom 0 - MSIs < 59 >
(XEN) [2010-12-12 18:38:31] 00:03.0 - dom 0 - MSIs < 58 >
(XEN) [2010-12-12 18:38:31] 00:02.0 - dom 0 - MSIs < 57 >
(XEN) [2010-12-12 18:38:31] 00:00.2 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:31] 00:00.0 - dom 0 - MSIs < >
(XEN) [2010-12-12 18:38:34] Guest interrupt information:
(XEN) [2010-12-12 18:38:34] IRQ: 0 affinity:00000000,00000000,00000000,00000001 vec:f0 type=IO-APIC-edge status=00000000 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 1 affinity:00000000,00000000,00000000,00000001 vec:30 type=IO-APIC-edge status=00000054 in-flight=0 domain-list=0: 1(----),
(XEN) [2010-12-12 18:38:34] IRQ: 2 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:e2 type=XT-PIC status=00000000 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 3 affinity:00000000,00000000,00000000,00000001 vec:38 type=IO-APIC-edge status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 4 affinity:00000000,00000000,00000000,00000001 vec:f1 type=IO-APIC-edge status=00000000 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 5 affinity:00000000,00000000,00000000,00000001 vec:40 type=IO-APIC-edge status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 6 affinity:00000000,00000000,00000000,00000001 vec:48 type=IO-APIC-edge status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 7 affinity:00000000,00000000,00000000,00000001 vec:50 type=IO-APIC-edge status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 8 affinity:00000000,00000000,00000000,00000001 vec:58 type=IO-APIC-edge status=00000050 in-flight=0 domain-list=0: 8(----),
(XEN) [2010-12-12 18:38:34] IRQ: 9 affinity:00000000,00000000,00000000,00000001 vec:60 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 9(----),
(XEN) [2010-12-12 18:38:34] IRQ: 10 affinity:00000000,00000000,00000000,00000001 vec:68 type=IO-APIC-edge status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 11 affinity:00000000,00000000,00000000,00000001 vec:70 type=IO-APIC-edge status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 12 affinity:00000000,00000000,00000000,00000001 vec:78 type=IO-APIC-edge status=00000050 in-flight=0 domain-list=0: 12(----),
(XEN) [2010-12-12 18:38:34] IRQ: 13 affinity:00000000,00000000,00000000,0000003f vec:88 type=IO-APIC-edge status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 14 affinity:00000000,00000000,00000000,00000001 vec:90 type=IO-APIC-edge status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 15 affinity:00000000,00000000,00000000,00000001 vec:98 type=IO-APIC-edge status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 16 affinity:00000000,00000000,00000000,0000003f vec:b8 type=IO-APIC-level status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 17 affinity:00000000,00000000,00000000,00000001 vec:c9 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 17(----),
(XEN) [2010-12-12 18:38:34] IRQ: 18 affinity:00000000,00000000,00000000,00000001 vec:d1 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 18(----),
(XEN) [2010-12-12 18:38:34] IRQ: 19 affinity:00000000,00000000,00000000,0000003f vec:99 type=IO-APIC-level status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 22 affinity:00000000,00000000,00000000,00000010 vec:41 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 22(----),11: 22(----),
(XEN) [2010-12-12 18:38:34] IRQ: 28 affinity:00000000,00000000,00000000,00000002 vec:91 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 28(----),13: 28(----),
(XEN) [2010-12-12 18:38:34] IRQ: 29 affinity:00000000,00000000,00000000,00000002 vec:89 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 29(----),13: 29(----),
(XEN) [2010-12-12 18:38:34] IRQ: 30 affinity:00000000,00000000,00000000,00000004 vec:81 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 30(----),13: 30(----),
(XEN) [2010-12-12 18:38:34] IRQ: 31 affinity:00000000,00000000,00000000,00000008 vec:79 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 31(----),13: 31(----),
(XEN) [2010-12-12 18:38:34] IRQ: 32 affinity:00000000,00000000,00000000,00000004 vec:71 type=IO-APIC-level status=00000010 in-flight=0 domain-list=14: 16(----),
(XEN) [2010-12-12 18:38:34] IRQ: 33 affinity:00000000,00000000,00000000,00000004 vec:69 type=IO-APIC-level status=00000010 in-flight=0 domain-list=14: 17(----),
(XEN) [2010-12-12 18:38:34] IRQ: 40 affinity:00000000,00000000,00000000,00000010 vec:61 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 40(----),9: 40(----),
(XEN) [2010-12-12 18:38:34] IRQ: 41 affinity:00000000,00000000,00000000,00000010 vec:59 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 41(----),9: 41(----),
(XEN) [2010-12-12 18:38:34] IRQ: 42 affinity:00000000,00000000,00000000,00000010 vec:51 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 42(----),9: 42(----),
(XEN) [2010-12-12 18:38:34] IRQ: 43 affinity:00000000,00000000,00000000,00000010 vec:49 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 43(----),9: 43(----),
(XEN) [2010-12-12 18:38:34] IRQ: 44 affinity:00000000,00000000,00000000,00000001 vec:d9 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 44(----),
(XEN) [2010-12-12 18:38:34] IRQ: 45 affinity:00000000,00000000,00000000,00000001 vec:22 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 45(----),
(XEN) [2010-12-12 18:38:34] IRQ: 46 affinity:00000000,00000000,00000000,00000001 vec:a9 type=IO-APIC-level status=00000050 in-flight=0 domain-list=0: 46(----),
(XEN) [2010-12-12 18:38:34] IRQ: 51 affinity:00000000,00000000,00000000,0000003f vec:b9 type=IO-APIC-level status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 52 affinity:00000000,00000000,00000000,0000003f vec:a0 type=IO-APIC-level status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 53 affinity:00000000,00000000,00000000,0000003f vec:a8 type=IO-APIC-level status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 54 affinity:00000000,00000000,00000000,0000003f vec:b0 type=IO-APIC-level status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 56 affinity:00000000,00000000,00000000,00000001 vec:28 type=AMD_IOV_MSI status=00000000 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 57 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:c0 type=PCI-MSI status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 58 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:c8 type=PCI-MSI status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 59 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:d0 type=PCI-MSI status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 60 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:d8 type=PCI-MSI status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 61 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:21 type=PCI-MSI status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 62 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:29 type=PCI-MSI status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:31 type=PCI-MSI status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:39 type=PCI-MSI status=00000002 mapped, unbound
(XEN) [2010-12-12 18:38:34] IRQ: 65 affinity:00000000,00000000,00000000,00000008 vec:a1 type=PCI-MSI status=00000054 in-flight=0 domain-list=0:303(----),
(XEN) [2010-12-12 18:38:34] IRQ: 66 affinity:00000000,00000000,00000000,00000008 vec:b1 type=PCI-MSI status=00000050 in-flight=0 domain-list=0:302(----),
(XEN) [2010-12-12 18:38:34] IRQ: 67 affinity:00000000,00000000,00000000,00000004 vec:c1 type=PCI-MSI status=00000050 in-flight=0 domain-list=0:301(----),
(XEN) [2010-12-12 18:38:34] IO-APIC interrupt information:
(XEN) [2010-12-12 18:38:34] IRQ 0 Vec240:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 2: vector=240, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 1 Vec 48:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 1: vector=48, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 3 Vec 56:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 3: vector=56, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 4 Vec241:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 4: vector=241, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 5 Vec 64:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 5: vector=64, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 6 Vec 72:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 6: vector=72, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 7 Vec 80:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 7: vector=80, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 8 Vec 88:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 8: vector=88, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 9 Vec 96:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 9: vector=96, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 10 Vec104:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 10: vector=104, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 11 Vec112:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 11: vector=112, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 12 Vec120:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 12: vector=120, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 13 Vec136:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 13: vector=136, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=1, dest_id:63
(XEN) [2010-12-12 18:38:34] IRQ 14 Vec144:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 14: vector=144, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 15 Vec152:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 15: vector=152, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=0, irr=0, trigger=edge, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 16 Vec184:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 16: vector=184, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=1, dest_id:63
(XEN) [2010-12-12 18:38:34] IRQ 17 Vec201:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 17: vector=201, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 18 Vec209:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 18: vector=209, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 19 Vec153:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 19: vector=153, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=1, dest_id:63
(XEN) [2010-12-12 18:38:34] IRQ 22 Vec 65:
(XEN) [2010-12-12 18:38:34] Apic 0x00, Pin 22: vector=65, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:16
(XEN) [2010-12-12 18:38:34] IRQ 28 Vec145:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 4: vector=145, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:2
(XEN) [2010-12-12 18:38:34] IRQ 29 Vec137:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 5: vector=137, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:2
(XEN) [2010-12-12 18:38:34] IRQ 30 Vec129:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 6: vector=129, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:4
(XEN) [2010-12-12 18:38:34] IRQ 31 Vec121:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 7: vector=121, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:8
(XEN) [2010-12-12 18:38:34] IRQ 32 Vec113:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 8: vector=113, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:4
(XEN) [2010-12-12 18:38:34] IRQ 33 Vec105:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 9: vector=105, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:4
(XEN) [2010-12-12 18:38:34] IRQ 40 Vec 97:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 16: vector=97, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:16
(XEN) [2010-12-12 18:38:34] IRQ 41 Vec 89:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 17: vector=89, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:16
(XEN) [2010-12-12 18:38:34] IRQ 42 Vec 81:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 18: vector=81, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:16
(XEN) [2010-12-12 18:38:34] IRQ 43 Vec 73:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 19: vector=73, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:16
(XEN) [2010-12-12 18:38:34] IRQ 44 Vec217:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 20: vector=217, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 45 Vec 34:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 21: vector=34, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 46 Vec169:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 22: vector=169, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=0, dest_id:1
(XEN) [2010-12-12 18:38:34] IRQ 51 Vec185:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 27: vector=185, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=1, dest_id:63
(XEN) [2010-12-12 18:38:34] IRQ 52 Vec160:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 28: vector=160, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=1, dest_id:63
(XEN) [2010-12-12 18:38:34] IRQ 53 Vec168:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 29: vector=168, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=1, dest_id:63
(XEN) [2010-12-12 18:38:34] IRQ 54 Vec176:
(XEN) [2010-12-12 18:38:34] Apic 0x01, Pin 30: vector=176, delivery_mode=1, dest_mode=logical, delivery_status=0, polarity=1, irr=0, trigger=level, mask=1, dest_id:63
(XEN) [2010-12-12 18:38:40] PCI-MSI interrupt information:
(XEN) [2010-12-12 18:38:40] MSI 57 vec=c0 lowest edge assert log lowest dest=0000003f mask=0/1/-1
(XEN) [2010-12-12 18:38:40] MSI 58 vec=c8 lowest edge assert log lowest dest=0000003f mask=0/1/-1
(XEN) [2010-12-12 18:38:40] MSI 59 vec=d0 lowest edge assert log lowest dest=0000003f mask=0/1/-1
(XEN) [2010-12-12 18:38:40] MSI 60 vec=d8 lowest edge assert log lowest dest=0000003f mask=0/1/-1
(XEN) [2010-12-12 18:38:40] MSI 61 vec=21 lowest edge assert log lowest dest=0000003f mask=0/1/-1
(XEN) [2010-12-12 18:38:40] MSI 62 vec=29 lowest edge assert log lowest dest=0000003f mask=0/1/-1
(XEN) [2010-12-12 18:38:40] MSI 63 vec=31 lowest edge assert log lowest dest=0000003f mask=0/1/-1
(XEN) [2010-12-12 18:38:40] MSI 64 vec=39 lowest edge assert log lowest dest=0000003f mask=0/1/-1
(XEN) [2010-12-12 18:38:40] MSI 65 vec=a1 lowest edge assert log lowest dest=00000001 mask=0/0/-1
(XEN) [2010-12-12 18:38:40] MSI 66 vec=b1 lowest edge assert log lowest dest=00000002 mask=0/0/-1
(XEN) [2010-12-12 18:38:40] MSI 67 vec=c1 lowest edge assert log lowest dest=00000020 mask=0/0/-1
[-- Attachment #3: dmesg.txt --]
[-- Type: text/plain, Size: 188396 bytes --]
[ 0.000000] Linux version 2.6.32.26-xen-next-2.6.32.x-20101210 (root@serveerstertje) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #20 SMP Fri Dec 10 18:24:34 CET 2010
[ 0.000000] Command line: root=/dev/mapper/serveerstertje-root ro nomodeset vga=794 video=vesafb earlyprintk=xen max_loop=255 loop_max_part=63 iommu=soft xen-pciback.hide=(03:06.0)(04:00.0)(04:00.1)(04:00.2)(04:00.3)(04:00.4)(04:00.5)(04:00.6)(04:00.7)(0a:00.0)(0a:00.1)(0a:00.2)(0a:00.3)(0a:00.4)(0a:00.5)(0a:00.6)(0a:00.7)(05:00.0)(05:00.1)
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] released 0 pages of unused memory
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 000000000009b000 (usable)
[ 0.000000] Xen: 000000000009b000 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000030000000 (usable)
[ 0.000000] Xen: 00000000aff90000 - 00000000aff9e000 (ACPI data)
[ 0.000000] Xen: 00000000aff9e000 - 00000000affe0000 (ACPI NVS)
[ 0.000000] Xen: 00000000affe0000 - 00000000b0000000 (reserved)
[ 0.000000] Xen: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] Xen: 00000000fec20000 - 00000000fec21000 (reserved)
[ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] Xen: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] Xen: 0000000100000000 - 00000002b0000000 (usable)
[ 0.000000] bootconsole [xenboot0] enabled
[ 0.000000] DMI present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0x2b0000 max_arch_pfn = 0x400000000
[ 0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106
[ 0.000000] last_pfn = 0x30000 max_arch_pfn = 0x400000000
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009b000 (usable)
[ 0.000000] modified: 000000000009b000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 0000000030000000 (usable)
[ 0.000000] modified: 00000000aff90000 - 00000000aff9e000 (ACPI data)
[ 0.000000] modified: 00000000aff9e000 - 00000000affe0000 (ACPI NVS)
[ 0.000000] modified: 00000000affe0000 - 00000000b0000000 (reserved)
[ 0.000000] modified: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] modified: 00000000fec20000 - 00000000fec21000 (reserved)
[ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] modified: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] modified: 0000000100000000 - 00000002b0000000 (usable)
[ 0.000000] initial memory mapped : 0 - 033ff000
[ 0.000000] init_memory_mapping: 0000000000000000-0000000030000000
[ 0.000000] 0000000000 - 0030000000 page 4k
[ 0.000000] kernel direct mapping tables up to 30000000 @ 100000-282000
[ 0.000000] init_memory_mapping: 0000000100000000-00000002b0000000
[ 0.000000] 0100000000 - 02b0000000 page 4k
[ 0.000000] kernel direct mapping tables up to 2b0000000 @ 289f000-3e2b000
[ 0.000000] RAMDISK: 01e3a000 - 02704c00
[ 0.000000] ACPI: RSDP 00000000000fb100 00014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 00000000aff90000 00048 (v01 MSI OEMSLIC 20100913 MSFT 00000097)
[ 0.000000] ACPI: FACP 00000000aff90200 00084 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: DSDT 00000000aff905e0 09427 (v01 A7640 A7640100 00000100 INTL 20051117)
[ 0.000000] ACPI: FACS 00000000aff9e000 00040
[ 0.000000] ACPI: APIC 00000000aff90390 00088 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: MCFG 00000000aff90420 0003C (v01 7640MS OEMMCFG 20100913 MSFT 00000097)
[ 0.000000] ACPI: SLIC 00000000aff90460 00176 (v01 MSI OEMSLIC 20100913 MSFT 00000097)
[ 0.000000] ACPI: OEMB 00000000aff9e040 00072 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: SRAT 00000000aff9a5e0 00108 (v03 AMD FAM_F_10 00000002 AMD 00000001)
[ 0.000000] ACPI: HPET 00000000aff9a6f0 00038 (v01 7640MS OEMHPET 20100913 MSFT 00000097)
[ 0.000000] ACPI: IVRS 00000000aff9a730 00100 (v01 AMD RD890S 00202031 AMD 00000000)
[ 0.000000] ACPI: SSDT 00000000aff9a830 00DA4 (v01 A M I POWERNOW 00000001 AMD 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] (10 early reservations) ==> bootmem [0000000000 - 02b0000000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [0002886000 - 000289f000] XEN PAGETABLES ==> [0002886000 - 000289f000]
[ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
[ 0.000000] #3 [0001000000 - 0001d0fb08] TEXT DATA BSS ==> [0001000000 - 0001d0fb08]
[ 0.000000] #4 [0001e3a000 - 0002704c00] RAMDISK ==> [0001e3a000 - 0002704c00]
[ 0.000000] #5 [0002705000 - 0002886000] XEN START INFO ==> [0002705000 - 0002886000]
[ 0.000000] #6 [0100000000 - 02b0000000] XEN EXTRA ==> [0100000000 - 02b0000000]
[ 0.000000] #7 [0001d10000 - 0001d1c10b] BRK ==> [0001d10000 - 0001d1c10b]
[ 0.000000] #8 [0000100000 - 0000266000] PGTABLE ==> [0000100000 - 0000266000]
[ 0.000000] #9 [000289f000 - 0003626000] PGTABLE ==> [000289f000 - 0003626000]
[ 0.000000] found SMP MP-table at [ffff8800000ff780] ff780
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x002b0000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[3] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009b
[ 0.000000] 0: 0x00000100 -> 0x00030000
[ 0.000000] 0: 0x00100000 -> 0x002b0000
[ 0.000000] On node 0 totalpages: 1965963
[ 0.000000] DMA zone: 56 pages used for memmap
[ 0.000000] DMA zone: 361 pages reserved
[ 0.000000] DMA zone: 3562 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 14280 pages used for memmap
[ 0.000000] DMA32 zone: 178232 pages, LIFO batch:31
[ 0.000000] Normal zone: 24192 pages used for memmap
[ 0.000000] Normal zone: 1745280 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
[ 0.000000] ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 6, version 0, address 0xfec00000, GSI 0-0
[ 0.000000] ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
[ 0.000000] IOAPIC[1]: apic_id 7, version 0, address 0xfec20000, GSI 24-24
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8300 base: 0xfed00000
[ 0.000000] SMP: Allowing 6 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 280
[ 0.000000] Allocating PCI resources starting at 30000000 (gap: 30000000:7ff90000)
[ 0.000000] Booting paravirtualized kernel on Xen
[ 0.000000] Xen version: 4.1-unstable (preserve-AD) (dom0)
[ 0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:6 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff880028038000 s83288 r8192 d23208 u114688
[ 0.000000] pcpu-alloc: s83288 r8192 d23208 u114688 alloc=28*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1927074
[ 0.000000] Kernel command line: root=/dev/mapper/serveerstertje-root ro nomodeset vga=794 video=vesafb earlyprintk=xen max_loop=255 loop_max_part=63 iommu=soft xen-pciback.hide=(03:06.0)(04:00.0)(04:00.1)(04:00.2)(04:00.3)(04:00.4)(04:00.5)(04:00.6)(04:00.7)(0a:00.0)(0a:00.1)(0a:00.2)(0a:00.3)(0a:00.4)(0a:00.5)(0a:00.6)(0a:00.7)(05:00.0)(05:00.1)
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.000000] Initializing CPU#0
[ 0.000000] DMA: Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000
[ 0.000000] DMA: software IO TLB at phys 0x20000000 - 0x24000000
[ 0.000000] xen_swiotlb_fixup: buf=ffff880020000000 size=67108864
[ 0.000000] xen_swiotlb_fixup: buf=ffff880024060000 size=32768
[ 0.000000] Memory: 559244k/11272192k available (7657k kernel code, 3408340k absent, 7303940k reserved, 4087k data, 860k init)
[ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:4352 nr_irqs:1792
[ 0.000000] xen: --> irq=0
[ 0.000000] xen: --> irq=1
[ 0.000000] xen: --> irq=2
[ 0.000000] xen: --> irq=3
[ 0.000000] xen: --> irq=4
[ 0.000000] xen: --> irq=5
[ 0.000000] xen: --> irq=6
[ 0.000000] xen: --> irq=7
[ 0.000000] xen: --> irq=8
[ 0.000000] xen: --> irq=9
[ 0.000000] xen: --> irq=10
[ 0.000000] xen: --> irq=11
[ 0.000000] xen: --> irq=12
[ 0.000000] xen: --> irq=13
[ 0.000000] xen: --> irq=14
[ 0.000000] xen: --> irq=15
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.000000] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=3
[ 0.000000] xen: registering gsi 9 triggering 0 polarity 1
[ 0.000000] xen_allocate_pirq: returning irq 9 for gsi 9
[ 0.000000] xen: --> irq=9
[ 0.000000] xen: acpi sci 9
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled, bootconsole disabled
[ 0.000000] Xen: using vcpuop timer interface
[ 0.000000] installing Xen timer for CPU 0
[ 0.000000] alloc irq_desc for 1791 on node 0
[ 0.000000] alloc kstat_irqs on node 0
[ 0.000000] Detected 759607.949 MHz processor.
[ 0.000999] Calibrating delay loop (skipped), value calculated using timer frequency.. 6400.44 BogoMIPS (lpj=3200222)
[ 0.001016] Security Framework initialized
[ 0.001022] SELinux: Initializing.
[ 0.001030] SELinux: Starting in permissive mode
[ 0.001038] Mount-cache hash table entries: 256
[ 0.001220] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[ 0.001225] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.001230] tseg: 0000000000
[ 0.001238] CPU: Physical Processor ID: 0
[ 0.001241] CPU: Processor Core ID: 0
[ 0.001246] mce: CPU supports 6 MCE banks
[ 0.001271] SMP alternatives: switching to UP code
[ 0.003392] ACPI: Core revision 20090903
[ 0.016011] ftrace: converting mcount calls to 0f 1f 44 00 00
[ 0.016017] ftrace: allocating 27261 entries in 107 pages
[ 0.017058] alloc irq_desc for 1790 on node 0
[ 0.017061] alloc kstat_irqs on node 0
[ 0.017071] cpu 0 spinlock event irq 1790
[ 0.017077] alloc irq_desc for 1789 on node 0
[ 0.017079] alloc kstat_irqs on node 0
[ 0.017084] alloc irq_desc for 1788 on node 0
[ 0.017086] alloc kstat_irqs on node 0
[ 0.017091] alloc irq_desc for 1787 on node 0
[ 0.017094] alloc kstat_irqs on node 0
[ 0.017099] alloc irq_desc for 1786 on node 0
[ 0.017102] alloc kstat_irqs on node 0
[ 0.017374] installing Xen timer for CPU 1
[ 0.017378] alloc irq_desc for 1785 on node 0
[ 0.017380] alloc kstat_irqs on node 0
[ 0.017387] alloc irq_desc for 1784 on node 0
[ 0.017390] alloc kstat_irqs on node 0
[ 0.017395] cpu 1 spinlock event irq 1784
[ 0.017421] SMP alternatives: switching to SMP code
[ 0.018997] alloc irq_desc for 1783 on node 0
[ 0.018997] alloc kstat_irqs on node 0
[ 0.019003] alloc irq_desc for 1782 on node 0
[ 0.019006] alloc kstat_irqs on node 0
[ 0.019011] alloc irq_desc for 1781 on node 0
[ 0.019014] alloc kstat_irqs on node 0
[ 0.019020] alloc irq_desc for 1780 on node 0
[ 0.019022] alloc kstat_irqs on node 0
[ 0.000999] Initializing CPU#1
[ 0.000999] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[ 0.000999] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.000999] CPU: Physical Processor ID: 0
[ 0.000999] CPU: Processor Core ID: 1
[ 0.019211] installing Xen timer for CPU 2
[ 0.019221] alloc irq_desc for 1779 on node 0
[ 0.019223] alloc kstat_irqs on node 0
[ 0.019230] alloc irq_desc for 1778 on node 0
[ 0.019232] alloc kstat_irqs on node 0
[ 0.019238] cpu 2 spinlock event irq 1778
[ 0.019260] alloc irq_desc for 1777 on node 0
[ 0.019263] alloc kstat_irqs on node 0
[ 0.019269] alloc irq_desc for 1776 on node 0
[ 0.019271] alloc kstat_irqs on node 0
[ 0.019277] alloc irq_desc for 1775 on node 0
[ 0.019279] alloc kstat_irqs on node 0
[ 0.019285] alloc irq_desc for 1774 on node 0
[ 0.019288] alloc kstat_irqs on node 0
[ 0.000999] Initializing CPU#2
[ 0.000999] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[ 0.000999] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.000999] CPU: Physical Processor ID: 0
[ 0.000999] CPU: Processor Core ID: 2
[ 0.019475] installing Xen timer for CPU 3
[ 0.019484] alloc irq_desc for 1773 on node 0
[ 0.019487] alloc kstat_irqs on node 0
[ 0.019493] alloc irq_desc for 1772 on node 0
[ 0.019496] alloc kstat_irqs on node 0
[ 0.019501] cpu 3 spinlock event irq 1772
[ 0.019521] alloc irq_desc for 1771 on node 0
[ 0.019524] alloc kstat_irqs on node 0
[ 0.019530] alloc irq_desc for 1770 on node 0
[ 0.019532] alloc kstat_irqs on node 0
[ 0.019538] alloc irq_desc for 1769 on node 0
[ 0.019541] alloc kstat_irqs on node 0
[ 0.019547] alloc irq_desc for 1768 on node 0
[ 0.019550] alloc kstat_irqs on node 0
[ 0.000999] Initializing CPU#3
[ 0.000999] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[ 0.000999] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.000999] CPU: Physical Processor ID: 0
[ 0.000999] CPU: Processor Core ID: 3
[ 0.019718] installing Xen timer for CPU 4
[ 0.019727] alloc irq_desc for 1767 on node 0
[ 0.019729] alloc kstat_irqs on node 0
[ 0.019736] alloc irq_desc for 1766 on node 0
[ 0.019738] alloc kstat_irqs on node 0
[ 0.019744] cpu 4 spinlock event irq 1766
[ 0.019763] alloc irq_desc for 1765 on node 0
[ 0.019765] alloc kstat_irqs on node 0
[ 0.019772] alloc irq_desc for 1764 on node 0
[ 0.019774] alloc kstat_irqs on node 0
[ 0.019780] alloc irq_desc for 1763 on node 0
[ 0.019782] alloc kstat_irqs on node 0
[ 0.019788] alloc irq_desc for 1762 on node 0
[ 0.019791] alloc kstat_irqs on node 0
[ 0.000999] Initializing CPU#4
[ 0.000999] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[ 0.000999] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.000999] CPU: Physical Processor ID: 0
[ 0.000999] CPU: Processor Core ID: 4
[ 0.019959] installing Xen timer for CPU 5
[ 0.019968] alloc irq_desc for 1761 on node 0
[ 0.019970] alloc kstat_irqs on node 0
[ 0.019977] alloc irq_desc for 1760 on node 0
[ 0.019979] alloc kstat_irqs on node 0
[ 0.019985] cpu 5 spinlock event irq 1760
[ 0.019996] alloc irq_desc for 1759 on node 0
[ 0.019996] alloc kstat_irqs on node 0
[ 0.019996] alloc irq_desc for 1758 on node 0
[ 0.019996] alloc kstat_irqs on node 0
[ 0.019996] alloc irq_desc for 1757 on node 0
[ 0.019996] alloc kstat_irqs on node 0
[ 0.019996] alloc irq_desc for 1756 on node 0
[ 0.019996] alloc kstat_irqs on node 0
[ 0.000999] Initializing CPU#5
[ 0.000999] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[ 0.000999] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.000999] CPU: Physical Processor ID: 0
[ 0.000999] CPU: Processor Core ID: 5
[ 0.020072] Brought up 6 CPUs
[ 0.020090] CPU0 attaching sched-domain:
[ 0.020098] domain 0: span 0-5 level CPU
[ 0.020105] groups: 0 1 2 3 4 5
[ 0.020123] CPU1 attaching sched-domain:
[ 0.020125] domain 0: span 0-5 level CPU
[ 0.020130] groups: 1 2 3 4 5 0
[ 0.020151] CPU2 attaching sched-domain:
[ 0.020154] domain 0: span 0-5 level CPU
[ 0.020159] groups: 2 3 4 5 0 1
[ 0.020176] CPU3 attaching sched-domain:
[ 0.020179] domain 0: span 0-5 level CPU
[ 0.020183] groups: 3 4 5 0 1 2
[ 0.020199] CPU4 attaching sched-domain:
[ 0.020202] domain 0: span 0-5 level CPU
[ 0.020206] groups: 4 5 0 1 2 3
[ 0.020222] CPU5 attaching sched-domain:
[ 0.020225] domain 0: span 0-5 level CPU
[ 0.020229] groups: 5 0 1 2 3 4
[ 0.021310] Grant table initialized
[ 0.021310] regulator: core version 0.5
[ 0.021310] NET: Registered protocol family 16
[ 0.022031] alloc irq_desc for 1755 on node 0
[ 0.022031] alloc kstat_irqs on node 0
[ 0.022054] node 0 link 0: io port [1000, ffffff]
[ 0.022054] TOM: 00000000b0000000 aka 2816M
[ 0.022054] Fam 10h mmconf [e0000000, efffffff]
[ 0.022054] node 0 link 0: mmio [e0000000, efffffff] ==> none
[ 0.022054] node 0 link 0: mmio [f0000000, ffffffff]
[ 0.022054] node 0 link 0: mmio [a0000, bffff]
[ 0.022054] node 0 link 0: mmio [b0000000, dfffffff]
[ 0.022054] TOM2: 0000000250000000 aka 9472M
[ 0.022059] bus: [00,07] on node 0 link 0
[ 0.022062] bus: 00 index 0 io port: [0, ffff]
[ 0.022065] bus: 00 index 1 mmio: [f0000000, ffffffff]
[ 0.022068] bus: 00 index 2 mmio: [a0000, bffff]
[ 0.022071] bus: 00 index 3 mmio: [b0000000, dfffffff]
[ 0.022074] bus: 00 index 4 mmio: [250000000, fcffffffff]
[ 0.023503] ACPI: bus type pci registered
[ 0.023527] sync cpu 0 get result 1 max_id 5
[ 0.023527] sync cpu 1 get result 1 max_id 5
[ 0.023527] sync cpu 2 get result 1 max_id 5
[ 0.023527] sync cpu 3 get result 1 max_id 5
[ 0.024002] sync cpu 4 get result 1 max_id 5
[ 0.024019] sync cpu 5 get result 1 max_id 5
[ 0.024019] alloc irq_desc for 1754 on node 0
[ 0.024019] alloc kstat_irqs on node 0
[ 0.024078] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
[ 0.024078] PCI: Not using MMCONFIG.
[ 0.024078] PCI: Using configuration type 1 for base access
[ 0.024078] PCI: Using configuration type 1 for extended access
[ 0.042044] bio: create slab <bio-0> at 0
[ 0.045063] ERROR: Unable to locate IOAPIC for GSI 9
[ 0.045116] ACPI: EC: Look up EC in DSDT
[ 0.047043] ACPI Error (dswload-0659): [PCI0] Namespace lookup failure, AE_NOT_FOUND
[ 0.047053] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20090903/psloop-230)
[ 0.047063] ACPI Error (psparse-0537): Method parse/execution failed [\] (Node ffffffff81cf1c00), AE_NOT_FOUND
[ 0.047193] ACPI: Executed 3 blocks of module-level executable AML code
[ 0.060921] ACPI: Interpreter enabled
[ 0.060928] ACPI: (supports S0 S5)
[ 0.060948] ACPI: Using IOAPIC for interrupt routing
[ 0.060990] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
[ 0.062852] PCI: MCFG area at e0000000 reserved in ACPI motherboard resources
[ 0.122099] PCI: Using MMCONFIG at e0000000 - efffffff
[ 0.144099] ACPI Warning: Incorrect checksum in table [OEMB] - B2, should be B1 (20090903/tbutils-314)
[ 0.144528] ACPI: No dock devices found.
[ 0.144728] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.145017] PCI: Scanning bus 0000:00
[ 0.145021] pci 0000:00:00.0: found [1002:5a11] class 000600 header type 00
[ 0.145029] pci 0000:00:00.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145090] pci 0000:00:00.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145197] pci 0000:00:00.2: found [1002:5a23] class 000806 header type 00
[ 0.145224] pci 0000:00:00.2: calling quirk_no_ata_d3+0x0/0x22
[ 0.145280] pci 0000:00:00.2: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145352] pci 0000:00:02.0: found [1002:5a16] class 000604 header type 01
[ 0.145363] pci 0000:00:02.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145398] pci 0000:00:02.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145432] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
[ 0.145440] pci 0000:00:02.0: PME# disabled
[ 0.145474] pci 0000:00:03.0: found [1002:5a17] class 000604 header type 01
[ 0.145484] pci 0000:00:03.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145516] pci 0000:00:03.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145549] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 0.145555] pci 0000:00:03.0: PME# disabled
[ 0.145597] pci 0000:00:05.0: found [1002:5a19] class 000604 header type 01
[ 0.145608] pci 0000:00:05.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145640] pci 0000:00:05.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145672] pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
[ 0.145678] pci 0000:00:05.0: PME# disabled
[ 0.145713] pci 0000:00:06.0: found [1002:5a1a] class 000604 header type 01
[ 0.145724] pci 0000:00:06.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145756] pci 0000:00:06.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145788] pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
[ 0.145795] pci 0000:00:06.0: PME# disabled
[ 0.145836] pci 0000:00:0a.0: found [1002:5a1d] class 000604 header type 01
[ 0.145847] pci 0000:00:0a.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145879] pci 0000:00:0a.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145911] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
[ 0.145922] pci 0000:00:0a.0: PME# disabled
[ 0.145957] pci 0000:00:0b.0: found [1002:5a1f] class 000604 header type 01
[ 0.145967] pci 0000:00:0b.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:0b.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:0b.0: PME# supported from D0 D3hot D3cold
[ 0.145977] pci 0000:00:0b.0: PME# disabled
[ 0.145977] pci 0000:00:0d.0: found [1002:5a1e] class 000604 header type 01
[ 0.145977] pci 0000:00:0d.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:0d.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:0d.0: PME# supported from D0 D3hot D3cold
[ 0.145977] pci 0000:00:0d.0: PME# disabled
[ 0.145977] pci 0000:00:11.0: found [1002:4391] class 000106 header type 00
[ 0.145977] pci 0000:00:11.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:11.0: reg 10 io port: [0x7000-0x7007]
[ 0.145977] pci 0000:00:11.0: reg 14 io port: [0x6000-0x6003]
[ 0.145977] pci 0000:00:11.0: reg 18 io port: [0x5000-0x5007]
[ 0.145977] pci 0000:00:11.0: reg 1c io port: [0x3000-0x3003]
[ 0.145977] pci 0000:00:11.0: reg 20 io port: [0x2000-0x200f]
[ 0.145977] pci 0000:00:11.0: reg 24 32bit mmio: [0xf98ff000-0xf98ff3ff]
[ 0.145977] pci 0000:00:11.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:12.0: found [1002:4397] class 000c03 header type 00
[ 0.145977] pci 0000:00:12.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:12.0: reg 10 32bit mmio: [0xf98fb000-0xf98fbfff]
[ 0.145977] pci 0000:00:12.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:12.2: found [1002:4396] class 000c03 header type 00
[ 0.145977] pci 0000:00:12.2: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:12.2: reg 10 32bit mmio: [0xf98ff400-0xf98ff4ff]
[ 0.145977] pci 0000:00:12.2: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:12.2: supports D1 D2
[ 0.145977] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
[ 0.145977] pci 0000:00:12.2: PME# disabled
[ 0.145977] pci 0000:00:13.0: found [1002:4397] class 000c03 header type 00
[ 0.145977] pci 0000:00:13.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:13.0: reg 10 32bit mmio: [0xf98fc000-0xf98fcfff]
[ 0.145977] pci 0000:00:13.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:13.2: found [1002:4396] class 000c03 header type 00
[ 0.145977] pci 0000:00:13.2: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:13.2: reg 10 32bit mmio: [0xf98ff800-0xf98ff8ff]
[ 0.145977] pci 0000:00:13.2: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:13.2: supports D1 D2
[ 0.145977] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
[ 0.145977] pci 0000:00:13.2: PME# disabled
[ 0.145977] pci 0000:00:14.0: found [1002:4385] class 000c05 header type 00
[ 0.145977] pci 0000:00:14.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:14.0: calling sb600_disable_hpet_bar+0x0/0x60
[ 0.145977] pci 0000:00:14.0: calling force_disable_hpet_msi+0x0/0x20
[ 0.145977] pci 0000:00:14.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:14.3: found [1002:439d] class 000601 header type 00
[ 0.145977] pci 0000:00:14.3: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:14.3: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:14.4: found [1002:4384] class 000604 header type 01
[ 0.145977] pci 0000:00:14.4: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:14.4: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:14.5: found [1002:4399] class 000c03 header type 00
[ 0.145977] pci 0000:00:14.5: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:14.5: reg 10 32bit mmio: [0xf98fd000-0xf98fdfff]
[ 0.145977] pci 0000:00:14.5: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:15.0: found [1002:43a0] class 000604 header type 01
[ 0.145977] pci 0000:00:15.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:15.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145977] pci 0000:00:15.0: supports D1 D2
[ 0.145977] pci 0000:00:16.0: found [1002:4397] class 000c03 header type 00
[ 0.145977] pci 0000:00:16.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.145977] pci 0000:00:16.0: reg 10 32bit mmio: [0xf98fe000-0xf98fefff]
[ 0.145977] pci 0000:00:16.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.145999] pci 0000:00:16.2: found [1002:4396] class 000c03 header type 00
[ 0.146025] pci 0000:00:16.2: calling quirk_no_ata_d3+0x0/0x22
[ 0.146039] pci 0000:00:16.2: reg 10 32bit mmio: [0xf98ffc00-0xf98ffcff]
[ 0.146091] pci 0000:00:16.2: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146123] pci 0000:00:16.2: supports D1 D2
[ 0.146126] pci 0000:00:16.2: PME# supported from D0 D1 D2 D3hot
[ 0.146134] pci 0000:00:16.2: PME# disabled
[ 0.146196] pci 0000:00:18.0: found [1022:1200] class 000600 header type 00
[ 0.146238] pci 0000:00:18.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146267] pci 0000:00:18.1: found [1022:1201] class 000600 header type 00
[ 0.146308] pci 0000:00:18.1: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146323] pci 0000:00:18.2: found [1022:1202] class 000600 header type 00
[ 0.146364] pci 0000:00:18.2: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146383] pci 0000:00:18.3: found [1022:1203] class 000600 header type 00
[ 0.146424] pci 0000:00:18.3: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146453] pci 0000:00:18.4: found [1022:1204] class 000600 header type 00
[ 0.146494] pci 0000:00:18.4: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146520] PCI: Fixups for bus 0000:00
[ 0.146525] pci 0000:00:02.0: scanning behind bridge, config 0b0b00, pass 0
[ 0.146531] PCI: Scanning bus 0000:0b
[ 0.146555] pci 0000:0b:00.0: found [10de:06e4] class 000300 header type 00
[ 0.146581] pci 0000:0b:00.0: reg 10 32bit mmio: [0xfd000000-0xfdffffff]
[ 0.146598] pci 0000:0b:00.0: reg 14 64bit mmio pref: [0xd0000000-0xdfffffff]
[ 0.146615] pci 0000:0b:00.0: reg 1c 64bit mmio: [0xfa000000-0xfbffffff]
[ 0.146625] pci 0000:0b:00.0: reg 24 io port: [0xe800-0xe87f]
[ 0.146635] pci 0000:0b:00.0: reg 30 32bit mmio pref: [0xfe9e0000-0xfe9fffff]
[ 0.146642] pci 0000:0b:00.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146752] PCI: Fixups for bus 0000:0b
[ 0.146761] pci 0000:00:02.0: bridge io port: [0xe000-0xefff]
[ 0.146767] pci 0000:00:02.0: bridge 32bit mmio: [0xfa000000-0xfe9fffff]
[ 0.146775] pci 0000:00:02.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
[ 0.146778] PCI: Bus scan for 0000:0b returning with max=0b
[ 0.146784] pci 0000:00:03.0: scanning behind bridge, config 0a0a00, pass 0
[ 0.146791] PCI: Scanning bus 0000:0a
[ 0.146820] pci 0000:0a:00.0: found [9710:9990] class 000c03 header type 00
[ 0.146855] pci 0000:0a:00.0: reg 10 32bit mmio: [0xf9ff8000-0xf9ff8fff]
[ 0.146919] pci 0000:0a:00.0: calling quirk_netmos+0x0/0xe5
[ 0.146922] pci 0000:0a:00.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146974] pci 0000:0a:00.0: supports D1 D2
[ 0.146977] pci 0000:0a:00.0: PME# supported from D0 D1 D2 D3hot
[ 0.146977] pci 0000:0a:00.0: PME# disabled
[ 0.146977] pci 0000:0a:00.1: found [9710:9990] class 000c03 header type 00
[ 0.146977] pci 0000:0a:00.1: reg 10 32bit mmio: [0xf9ff9000-0xf9ff9fff]
[ 0.146977] pci 0000:0a:00.1: calling quirk_netmos+0x0/0xe5
[ 0.146977] pci 0000:0a:00.1: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146977] pci 0000:0a:00.1: supports D1 D2
[ 0.146977] pci 0000:0a:00.1: PME# supported from D0 D1 D2 D3hot
[ 0.146977] pci 0000:0a:00.1: PME# disabled
[ 0.146977] pci 0000:0a:00.2: found [9710:9990] class 000c03 header type 00
[ 0.146977] pci 0000:0a:00.2: reg 10 32bit mmio: [0xf9ffa000-0xf9ffafff]
[ 0.146977] pci 0000:0a:00.2: calling quirk_netmos+0x0/0xe5
[ 0.146977] pci 0000:0a:00.2: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146977] pci 0000:0a:00.2: supports D1 D2
[ 0.146977] pci 0000:0a:00.2: PME# supported from D0 D1 D2 D3hot
[ 0.146977] pci 0000:0a:00.2: PME# disabled
[ 0.146977] pci 0000:0a:00.3: found [9710:9990] class 000c03 header type 00
[ 0.146977] pci 0000:0a:00.3: reg 10 32bit mmio: [0xf9ffb000-0xf9ffbfff]
[ 0.146977] pci 0000:0a:00.3: calling quirk_netmos+0x0/0xe5
[ 0.146977] pci 0000:0a:00.3: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146977] pci 0000:0a:00.3: supports D1 D2
[ 0.146977] pci 0000:0a:00.3: PME# supported from D0 D1 D2 D3hot
[ 0.146977] pci 0000:0a:00.3: PME# disabled
[ 0.146977] pci 0000:0a:00.4: found [9710:9990] class 000c03 header type 00
[ 0.146977] pci 0000:0a:00.4: reg 10 32bit mmio: [0xf9ffc000-0xf9ffcfff]
[ 0.146977] pci 0000:0a:00.4: calling quirk_netmos+0x0/0xe5
[ 0.146977] pci 0000:0a:00.4: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146977] pci 0000:0a:00.4: supports D1 D2
[ 0.146977] pci 0000:0a:00.4: PME# supported from D0 D1 D2 D3hot
[ 0.146977] pci 0000:0a:00.4: PME# disabled
[ 0.146977] pci 0000:0a:00.5: found [9710:9990] class 000c03 header type 00
[ 0.146977] pci 0000:0a:00.5: reg 10 32bit mmio: [0xf9ffd000-0xf9ffdfff]
[ 0.146977] pci 0000:0a:00.5: calling quirk_netmos+0x0/0xe5
[ 0.146977] pci 0000:0a:00.5: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146977] pci 0000:0a:00.5: supports D1 D2
[ 0.146977] pci 0000:0a:00.5: PME# supported from D0 D1 D2 D3hot
[ 0.146977] pci 0000:0a:00.5: PME# disabled
[ 0.146977] pci 0000:0a:00.6: found [9710:9990] class 000c03 header type 00
[ 0.146977] pci 0000:0a:00.6: reg 10 32bit mmio: [0xf9ffe000-0xf9ffefff]
[ 0.146977] pci 0000:0a:00.6: calling quirk_netmos+0x0/0xe5
[ 0.146977] pci 0000:0a:00.6: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146977] pci 0000:0a:00.6: supports D1 D2
[ 0.146977] pci 0000:0a:00.6: PME# supported from D0 D1 D2 D3hot
[ 0.146977] pci 0000:0a:00.6: PME# disabled
[ 0.146977] pci 0000:0a:00.7: found [9710:9990] class 000c03 header type 00
[ 0.146977] pci 0000:0a:00.7: reg 10 32bit mmio: [0xf9fff000-0xf9ffffff]
[ 0.146977] pci 0000:0a:00.7: calling quirk_netmos+0x0/0xe5
[ 0.146977] pci 0000:0a:00.7: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146977] pci 0000:0a:00.7: supports D1 D2
[ 0.146977] pci 0000:0a:00.7: PME# supported from D0 D1 D2 D3hot
[ 0.146977] pci 0000:0a:00.7: PME# disabled
[ 0.146977] PCI: Fixups for bus 0000:0a
[ 0.146977] pci 0000:00:03.0: bridge 32bit mmio: [0xf9f00000-0xf9ffffff]
[ 0.146977] PCI: Bus scan for 0000:0a returning with max=0a
[ 0.146977] pci 0000:00:05.0: scanning behind bridge, config 090900, pass 0
[ 0.146977] PCI: Scanning bus 0000:09
[ 0.146977] pci 0000:09:00.0: found [10ec:8168] class 000200 header type 00
[ 0.146977] pci 0000:09:00.0: reg 10 io port: [0xd800-0xd8ff]
[ 0.146977] pci 0000:09:00.0: reg 18 64bit mmio pref: [0xcffff000-0xcfffffff]
[ 0.146977] pci 0000:09:00.0: reg 20 64bit mmio pref: [0xcfff8000-0xcfffbfff]
[ 0.146977] pci 0000:09:00.0: reg 30 32bit mmio pref: [0xf9ee0000-0xf9efffff]
[ 0.146977] pci 0000:09:00.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.146977] pci 0000:09:00.0: supports D1 D2
[ 0.146977] pci 0000:09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.146977] pci 0000:09:00.0: PME# disabled
[ 0.146977] PCI: Fixups for bus 0000:09
[ 0.146977] pci 0000:00:05.0: bridge io port: [0xd000-0xdfff]
[ 0.146977] pci 0000:00:05.0: bridge 32bit mmio: [0xf9e00000-0xf9efffff]
[ 0.146977] pci 0000:00:05.0: bridge 64bit mmio pref: [0xcff00000-0xcfffffff]
[ 0.146977] PCI: Bus scan for 0000:09 returning with max=09
[ 0.146977] pci 0000:00:06.0: scanning behind bridge, config 080800, pass 0
[ 0.146977] PCI: Scanning bus 0000:08
[ 0.147004] pci 0000:08:00.0: found [10ec:8168] class 000200 header type 00
[ 0.147035] pci 0000:08:00.0: reg 10 io port: [0xc800-0xc8ff]
[ 0.147089] pci 0000:08:00.0: reg 18 64bit mmio pref: [0xcfeff000-0xcfefffff]
[ 0.147108] pci 0000:08:00.0: reg 20 64bit mmio pref: [0xcfef8000-0xcfefbfff]
[ 0.147119] pci 0000:08:00.0: reg 30 32bit mmio pref: [0xf9de0000-0xf9dfffff]
[ 0.147127] pci 0000:08:00.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147176] pci 0000:08:00.0: supports D1 D2
[ 0.147179] pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.147187] pci 0000:08:00.0: PME# disabled
[ 0.147275] PCI: Fixups for bus 0000:08
[ 0.147284] pci 0000:00:06.0: bridge io port: [0xc000-0xcfff]
[ 0.147291] pci 0000:00:06.0: bridge 32bit mmio: [0xf9d00000-0xf9dfffff]
[ 0.147299] pci 0000:00:06.0: bridge 64bit mmio pref: [0xcfe00000-0xcfefffff]
[ 0.147302] PCI: Bus scan for 0000:08 returning with max=08
[ 0.147308] pci 0000:00:0a.0: scanning behind bridge, config 070600, pass 0
[ 0.147315] PCI: Scanning bus 0000:06
[ 0.147348] pci 0000:06:00.0: found [104c:8231] class 000604 header type 01
[ 0.147425] pci 0000:06:00.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147480] pci 0000:06:00.0: supports D1 D2
[ 0.147564] PCI: Fixups for bus 0000:06
[ 0.147576] pci 0000:00:0a.0: bridge 32bit mmio: [0xf9c00000-0xf9cfffff]
[ 0.147589] pci 0000:06:00.0: scanning behind bridge, config 070706, pass 0
[ 0.147597] PCI: Scanning bus 0000:07
[ 0.147622] pci 0000:07:01.0: found [1033:0035] class 000c03 header type 00
[ 0.147660] pci 0000:07:01.0: reg 10 32bit mmio: [0xf9cfd000-0xf9cfdfff]
[ 0.147729] pci 0000:07:01.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147762] pci 0000:07:01.0: supports D1 D2
[ 0.147765] pci 0000:07:01.0: PME# supported from D0 D1 D2 D3hot
[ 0.147774] pci 0000:07:01.0: PME# disabled
[ 0.147807] pci 0000:07:01.1: found [1033:0035] class 000c03 header type 00
[ 0.147853] pci 0000:07:01.1: reg 10 32bit mmio: [0xf9cfe000-0xf9cfefff]
[ 0.147922] pci 0000:07:01.1: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147955] pci 0000:07:01.1: supports D1 D2
[ 0.147958] pci 0000:07:01.1: PME# supported from D0 D1 D2 D3hot
[ 0.147967] pci 0000:07:01.1: PME# disabled
[ 0.147977] pci 0000:07:01.2: found [1033:00e0] class 000c03 header type 00
[ 0.147977] pci 0000:07:01.2: reg 10 32bit mmio: [0xf9cffc00-0xf9cffcff]
[ 0.147977] pci 0000:07:01.2: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:07:01.2: supports D1 D2
[ 0.147977] pci 0000:07:01.2: PME# supported from D0 D1 D2 D3hot
[ 0.147977] pci 0000:07:01.2: PME# disabled
[ 0.147977] PCI: Fixups for bus 0000:07
[ 0.147977] pci 0000:06:00.0: bridge 32bit mmio: [0xf9c00000-0xf9cfffff]
[ 0.147977] PCI: Bus scan for 0000:07 returning with max=07
[ 0.147977] pci 0000:06:00.0: scanning behind bridge, config 070706, pass 1
[ 0.147977] PCI: Bus scan for 0000:06 returning with max=07
[ 0.147977] pci 0000:00:0b.0: scanning behind bridge, config 050500, pass 0
[ 0.147977] PCI: Scanning bus 0000:05
[ 0.147977] pci 0000:05:00.0: found [1002:95c5] class 000300 header type 00
[ 0.147977] pci 0000:05:00.0: calling quirk_no_ata_d3+0x0/0x22
[ 0.147977] pci 0000:05:00.0: reg 10 64bit mmio pref: [0xb0000000-0xbfffffff]
[ 0.147977] pci 0000:05:00.0: reg 18 64bit mmio: [0xf9be0000-0xf9beffff]
[ 0.147977] pci 0000:05:00.0: reg 20 io port: [0xb000-0xb0ff]
[ 0.147977] pci 0000:05:00.0: reg 30 32bit mmio pref: [0xf9bc0000-0xf9bdffff]
[ 0.147977] pci 0000:05:00.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:05:00.0: supports D1 D2
[ 0.147977] pci 0000:05:00.1: found [1002:aa28] class 000403 header type 00
[ 0.147977] pci 0000:05:00.1: calling quirk_no_ata_d3+0x0/0x22
[ 0.147977] pci 0000:05:00.1: reg 10 64bit mmio: [0xf9bfc000-0xf9bfffff]
[ 0.147977] pci 0000:05:00.1: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:05:00.1: supports D1 D2
[ 0.147977] PCI: Fixups for bus 0000:05
[ 0.147977] pci 0000:00:0b.0: bridge io port: [0xb000-0xbfff]
[ 0.147977] pci 0000:00:0b.0: bridge 32bit mmio: [0xf9b00000-0xf9bfffff]
[ 0.147977] pci 0000:00:0b.0: bridge 64bit mmio pref: [0xb0000000-0xbfffffff]
[ 0.147977] PCI: Bus scan for 0000:05 returning with max=05
[ 0.147977] pci 0000:00:0d.0: scanning behind bridge, config 040400, pass 0
[ 0.147977] PCI: Scanning bus 0000:04
[ 0.147977] pci 0000:04:00.0: found [9710:9990] class 000c03 header type 00
[ 0.147977] pci 0000:04:00.0: reg 10 32bit mmio: [0xf9af8000-0xf9af8fff]
[ 0.147977] pci 0000:04:00.0: calling quirk_netmos+0x0/0xe5
[ 0.147977] pci 0000:04:00.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:04:00.0: supports D1 D2
[ 0.147977] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot
[ 0.147977] pci 0000:04:00.0: PME# disabled
[ 0.147977] pci 0000:04:00.1: found [9710:9990] class 000c03 header type 00
[ 0.147977] pci 0000:04:00.1: reg 10 32bit mmio: [0xf9af9000-0xf9af9fff]
[ 0.147977] pci 0000:04:00.1: calling quirk_netmos+0x0/0xe5
[ 0.147977] pci 0000:04:00.1: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:04:00.1: supports D1 D2
[ 0.147977] pci 0000:04:00.1: PME# supported from D0 D1 D2 D3hot
[ 0.147977] pci 0000:04:00.1: PME# disabled
[ 0.147977] pci 0000:04:00.2: found [9710:9990] class 000c03 header type 00
[ 0.147977] pci 0000:04:00.2: reg 10 32bit mmio: [0xf9afa000-0xf9afafff]
[ 0.147977] pci 0000:04:00.2: calling quirk_netmos+0x0/0xe5
[ 0.147977] pci 0000:04:00.2: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:04:00.2: supports D1 D2
[ 0.147977] pci 0000:04:00.2: PME# supported from D0 D1 D2 D3hot
[ 0.147977] pci 0000:04:00.2: PME# disabled
[ 0.147977] pci 0000:04:00.3: found [9710:9990] class 000c03 header type 00
[ 0.147977] pci 0000:04:00.3: reg 10 32bit mmio: [0xf9afb000-0xf9afbfff]
[ 0.147977] pci 0000:04:00.3: calling quirk_netmos+0x0/0xe5
[ 0.147977] pci 0000:04:00.3: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:04:00.3: supports D1 D2
[ 0.147977] pci 0000:04:00.3: PME# supported from D0 D1 D2 D3hot
[ 0.147977] pci 0000:04:00.3: PME# disabled
[ 0.147977] pci 0000:04:00.4: found [9710:9990] class 000c03 header type 00
[ 0.147977] pci 0000:04:00.4: reg 10 32bit mmio: [0xf9afc000-0xf9afcfff]
[ 0.147977] pci 0000:04:00.4: calling quirk_netmos+0x0/0xe5
[ 0.147977] pci 0000:04:00.4: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:04:00.4: supports D1 D2
[ 0.147977] pci 0000:04:00.4: PME# supported from D0 D1 D2 D3hot
[ 0.147977] pci 0000:04:00.4: PME# disabled
[ 0.147977] pci 0000:04:00.5: found [9710:9990] class 000c03 header type 00
[ 0.147977] pci 0000:04:00.5: reg 10 32bit mmio: [0xf9afd000-0xf9afdfff]
[ 0.147977] pci 0000:04:00.5: calling quirk_netmos+0x0/0xe5
[ 0.147977] pci 0000:04:00.5: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:04:00.5: supports D1 D2
[ 0.147977] pci 0000:04:00.5: PME# supported from D0 D1 D2 D3hot
[ 0.147977] pci 0000:04:00.5: PME# disabled
[ 0.147977] pci 0000:04:00.6: found [9710:9990] class 000c03 header type 00
[ 0.147977] pci 0000:04:00.6: reg 10 32bit mmio: [0xf9afe000-0xf9afefff]
[ 0.147977] pci 0000:04:00.6: calling quirk_netmos+0x0/0xe5
[ 0.147977] pci 0000:04:00.6: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:04:00.6: supports D1 D2
[ 0.147977] pci 0000:04:00.6: PME# supported from D0 D1 D2 D3hot
[ 0.147977] pci 0000:04:00.6: PME# disabled
[ 0.147977] pci 0000:04:00.7: found [9710:9990] class 000c03 header type 00
[ 0.147977] pci 0000:04:00.7: reg 10 32bit mmio: [0xf9aff000-0xf9afffff]
[ 0.147977] pci 0000:04:00.7: calling quirk_netmos+0x0/0xe5
[ 0.147977] pci 0000:04:00.7: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:04:00.7: supports D1 D2
[ 0.147977] pci 0000:04:00.7: PME# supported from D0 D1 D2 D3hot
[ 0.147977] pci 0000:04:00.7: PME# disabled
[ 0.147977] PCI: Fixups for bus 0000:04
[ 0.147977] pci 0000:00:0d.0: bridge 32bit mmio: [0xf9a00000-0xf9afffff]
[ 0.147977] PCI: Bus scan for 0000:04 returning with max=04
[ 0.147977] pci 0000:00:14.4: scanning behind bridge, config 030300, pass 0
[ 0.147977] PCI: Scanning bus 0000:03
[ 0.147977] pci 0000:03:06.0: found [13f6:0111] class 000401 header type 00
[ 0.147977] pci 0000:03:06.0: reg 10 io port: [0xa800-0xa8ff]
[ 0.147977] pci 0000:03:06.0: calling quirk_resource_alignment+0x0/0x1bd
[ 0.147977] pci 0000:03:06.0: supports D1 D2
[ 0.147977] PCI: Fixups for bus 0000:03
[ 0.147977] pci 0000:00:14.4: transparent bridge
[ 0.147977] pci 0000:00:14.4: bridge io port: [0xa000-0xafff]
[ 0.147977] PCI: Bus scan for 0000:03 returning with max=03
[ 0.147977] pci 0000:00:15.0: scanning behind bridge, config 020200, pass 0
[ 0.147977] PCI: Scanning bus 0000:02
[ 0.147977] PCI: Fixups for bus 0000:02
[ 0.147977] PCI: Bus scan for 0000:02 returning with max=02
[ 0.147977] pci 0000:00:02.0: scanning behind bridge, config 0b0b00, pass 1
[ 0.147977] pci 0000:00:03.0: scanning behind bridge, config 0a0a00, pass 1
[ 0.147977] pci 0000:00:05.0: scanning behind bridge, config 090900, pass 1
[ 0.147977] pci 0000:00:06.0: scanning behind bridge, config 080800, pass 1
[ 0.147977] pci 0000:00:0a.0: scanning behind bridge, config 070600, pass 1
[ 0.147977] pci 0000:00:0b.0: scanning behind bridge, config 050500, pass 1
[ 0.147977] pci 0000:00:0d.0: scanning behind bridge, config 040400, pass 1
[ 0.147977] pci 0000:00:14.4: scanning behind bridge, config 030300, pass 1
[ 0.147977] pci 0000:00:15.0: scanning behind bridge, config 020200, pass 1
[ 0.147977] PCI: Bus scan for 0000:00 returning with max=0b
[ 0.147977] pci_bus 0000:00: on NUMA node 0
[ 0.147977] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.148196] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PC02._PRT]
[ 0.148268] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PC03._PRT]
[ 0.148372] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PC05._PRT]
[ 0.148442] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PC06._PRT]
[ 0.148526] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PC0A._PRT]
[ 0.148596] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PC0B._PRT]
[ 0.148673] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PC0D._PRT]
[ 0.148765] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0PC._PRT]
[ 0.148899] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PE20._PRT]
[ 0.177104] ACPI: PCI Interrupt Link [LNKA] (IRQs 4 7 *10 11 14 15)
[ 0.177308] ACPI: PCI Interrupt Link [LNKB] (IRQs 4 7 10 *11 14 15)
[ 0.177522] ACPI: PCI Interrupt Link [LNKC] (IRQs 4 7 *10 11 14 15)
[ 0.178003] ACPI: PCI Interrupt Link [LNKD] (IRQs 4 7 *10 11 14 15)
[ 0.178214] ACPI: PCI Interrupt Link [LNKE] (IRQs 4 *7 10 11 14 15)
[ 0.178351] ACPI: PCI Interrupt Link [LNKF] (IRQs 4 7 10 *11 14 15)
[ 0.178488] ACPI: PCI Interrupt Link [LNKG] (IRQs 4 7 *10 11 14 15)
[ 0.178629] ACPI: PCI Interrupt Link [LNKH] (IRQs 4 7 *10 11 14 15)
[ 0.179003] xen_balloon: Initialising balloon driver with page order 0.
[ 0.179093] last_pfn = 0x2b0000 max_arch_pfn = 0x400000000
[ 0.202059] vgaarb: device added: PCI:0000:0b:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.202080] vgaarb: device added: PCI:0000:05:00.0,decodes=io+mem,owns=none,locks=none
[ 0.202104] vgaarb: loaded
[ 0.202997] SCSI subsystem initialized
[ 0.203021] libata version 3.00 loaded.
[ 0.204002] usbcore: registered new interface driver usbfs
[ 0.204011] usbcore: registered new interface driver hub
[ 0.204011] usbcore: registered new device driver usb
[ 0.204031] PCI: Using ACPI for IRQ routing
[ 0.205385] NetLabel: Initializing
[ 0.205385] NetLabel: domain hash size = 128
[ 0.205385] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.205385] NetLabel: unlabeled traffic allowed by default
[ 0.206375] Switching to clocksource xen
[ 0.221922] pnp: PnP ACPI init
[ 0.221943] ACPI: bus type pnp registered
[ 0.223852] xen: registering gsi 8 triggering 1 polarity 0
[ 0.223857] xen_allocate_pirq: returning irq 8 for gsi 8
[ 0.223862] xen: --> irq=8
[ 0.224462] xen: registering gsi 13 triggering 1 polarity 0
[ 0.224466] xen_allocate_pirq: returning irq 13 for gsi 13
[ 0.224471] xen: --> irq=13
[ 0.225313] xen: registering gsi 4 triggering 1 polarity 0
[ 0.225317] xen_allocate_pirq: returning irq 4 for gsi 4
[ 0.225321] xen: --> irq=4
[ 0.225325] Already setup the GSI :4
[ 0.229430] pnp: PnP ACPI: found 14 devices
[ 0.229436] ACPI: ACPI bus type pnp unregistered
[ 0.229461] system 00:01: iomem range 0xfec20000-0xfec200ff could not be reserved
[ 0.229483] system 00:02: iomem range 0xf6000000-0xf6003fff has been reserved
[ 0.229496] system 00:08: ioport range 0x600-0x6df has been reserved
[ 0.229501] system 00:08: ioport range 0xae0-0xaef has been reserved
[ 0.229513] system 00:0a: iomem range 0xfec00000-0xfec00fff could not be reserved
[ 0.229519] system 00:0a: iomem range 0xfee00000-0xfee00fff has been reserved
[ 0.229530] system 00:0b: ioport range 0x4d0-0x4d1 has been reserved
[ 0.229535] system 00:0b: ioport range 0x40b-0x40b has been reserved
[ 0.229540] system 00:0b: ioport range 0x4d6-0x4d6 has been reserved
[ 0.229545] system 00:0b: ioport range 0xc00-0xc01 has been reserved
[ 0.229550] system 00:0b: ioport range 0xc14-0xc14 has been reserved
[ 0.229555] system 00:0b: ioport range 0xc50-0xc51 has been reserved
[ 0.229560] system 00:0b: ioport range 0xc52-0xc52 has been reserved
[ 0.229565] system 00:0b: ioport range 0xc6c-0xc6c has been reserved
[ 0.229569] system 00:0b: ioport range 0xc6f-0xc6f has been reserved
[ 0.229574] system 00:0b: ioport range 0xcd0-0xcd1 has been reserved
[ 0.229579] system 00:0b: ioport range 0xcd2-0xcd3 has been reserved
[ 0.229584] system 00:0b: ioport range 0xcd4-0xcd5 has been reserved
[ 0.229589] system 00:0b: ioport range 0xcd6-0xcd7 has been reserved
[ 0.229594] system 00:0b: ioport range 0xcd8-0xcdf has been reserved
[ 0.229607] system 00:0b: ioport range 0x800-0x89f has been reserved
[ 0.229612] system 00:0b: ioport range 0xb00-0xb1f has been reserved
[ 0.229617] system 00:0b: ioport range 0xb20-0xb3f has been reserved
[ 0.229622] system 00:0b: ioport range 0x900-0x90f has been reserved
[ 0.229627] system 00:0b: ioport range 0x910-0x91f has been reserved
[ 0.229632] system 00:0b: ioport range 0xfe00-0xfefe has been reserved
[ 0.229637] system 00:0b: iomem range 0xffb80000-0xffbfffff has been reserved
[ 0.229643] system 00:0b: iomem range 0xfec10000-0xfec1001f has been reserved
[ 0.229648] system 00:0b: iomem range 0xfed80000-0xfed80fff has been reserved
[ 0.229659] system 00:0c: iomem range 0xe0000000-0xefffffff has been reserved
[ 0.229670] system 00:0d: iomem range 0x0-0x9ffff could not be reserved
[ 0.229676] system 00:0d: iomem range 0xc0000-0xcffff could not be reserved
[ 0.229681] system 00:0d: iomem range 0xe0000-0xfffff could not be reserved
[ 0.229686] system 00:0d: iomem range 0x100000-0xafffffff could not be reserved
[ 0.229692] system 00:0d: iomem range 0xfec00000-0xffffffff could not be reserved
[ 0.229979] pciback: wants to seize 0000:03:06.0
[ 0.229984] pciback: wants to seize 0000:04:00.0
[ 0.229988] pciback: wants to seize 0000:04:00.1
[ 0.229992] pciback: wants to seize 0000:04:00.2
[ 0.229995] pciback: wants to seize 0000:04:00.3
[ 0.229999] pciback: wants to seize 0000:04:00.4
[ 0.230002] pciback: wants to seize 0000:04:00.5
[ 0.230006] pciback: wants to seize 0000:04:00.6
[ 0.230009] pciback: wants to seize 0000:04:00.7
[ 0.230013] pciback: wants to seize 0000:0a:00.0
[ 0.230017] pciback: wants to seize 0000:0a:00.1
[ 0.230020] pciback: wants to seize 0000:0a:00.2
[ 0.230024] pciback: wants to seize 0000:0a:00.3
[ 0.230027] pciback: wants to seize 0000:0a:00.4
[ 0.230031] pciback: wants to seize 0000:0a:00.5
[ 0.230035] pciback: wants to seize 0000:0a:00.6
[ 0.230039] pciback: wants to seize 0000:0a:00.7
[ 0.230042] pciback: wants to seize 0000:05:00.0
[ 0.230046] pciback: wants to seize 0000:05:00.1
[ 0.230078] pciback 0000:00:00.0: probing...
[ 0.230098] pciback 0000:00:00.2: probing...
[ 0.230112] pciback 0000:00:02.0: probing...
[ 0.230125] pciback 0000:00:03.0: probing...
[ 0.230139] pciback 0000:00:05.0: probing...
[ 0.230156] pciback 0000:00:06.0: probing...
[ 0.230169] pciback 0000:00:0a.0: probing...
[ 0.230182] pciback 0000:00:0b.0: probing...
[ 0.230195] pciback 0000:00:0d.0: probing...
[ 0.230211] pciback 0000:00:11.0: probing...
[ 0.230225] pciback 0000:00:12.0: probing...
[ 0.230237] pciback 0000:00:12.2: probing...
[ 0.230251] pciback 0000:00:13.0: probing...
[ 0.230267] pciback 0000:00:13.2: probing...
[ 0.230286] pciback 0000:00:14.0: probing...
[ 0.230301] pciback 0000:00:14.3: probing...
[ 0.230313] pciback 0000:00:14.4: probing...
[ 0.230326] pciback 0000:00:14.5: probing...
[ 0.230340] pciback 0000:00:15.0: probing...
[ 0.230361] pciback 0000:00:16.0: probing...
[ 0.230379] pciback 0000:00:16.2: probing...
[ 0.230397] pciback 0000:00:18.0: probing...
[ 0.230419] pciback 0000:00:18.1: probing...
[ 0.230439] pciback 0000:00:18.2: probing...
[ 0.230460] pciback 0000:00:18.3: probing...
[ 0.230486] pciback 0000:00:18.4: probing...
[ 0.230501] pciback 0000:0b:00.0: probing...
[ 0.230514] pciback 0000:0a:00.0: probing...
[ 0.230517] pciback 0000:0a:00.0: seizing device
[ 0.230522] pciback 0000:0a:00.0: pcistub_device_alloc
[ 0.230527] pciback 0000:0a:00.0: deferring initialization
[ 0.230541] pciback 0000:0a:00.1: probing...
[ 0.230544] pciback 0000:0a:00.1: seizing device
[ 0.230548] pciback 0000:0a:00.1: pcistub_device_alloc
[ 0.230552] pciback 0000:0a:00.1: deferring initialization
[ 0.230561] pciback 0000:0a:00.2: probing...
[ 0.230564] pciback 0000:0a:00.2: seizing device
[ 0.230568] pciback 0000:0a:00.2: pcistub_device_alloc
[ 0.230572] pciback 0000:0a:00.2: deferring initialization
[ 0.230581] pciback 0000:0a:00.3: probing...
[ 0.230585] pciback 0000:0a:00.3: seizing device
[ 0.230588] pciback 0000:0a:00.3: pcistub_device_alloc
[ 0.230592] pciback 0000:0a:00.3: deferring initialization
[ 0.230601] pciback 0000:0a:00.4: probing...
[ 0.230604] pciback 0000:0a:00.4: seizing device
[ 0.230608] pciback 0000:0a:00.4: pcistub_device_alloc
[ 0.230612] pciback 0000:0a:00.4: deferring initialization
[ 0.230622] pciback 0000:0a:00.5: probing...
[ 0.230625] pciback 0000:0a:00.5: seizing device
[ 0.230629] pciback 0000:0a:00.5: pcistub_device_alloc
[ 0.230632] pciback 0000:0a:00.5: deferring initialization
[ 0.230641] pciback 0000:0a:00.6: probing...
[ 0.230645] pciback 0000:0a:00.6: seizing device
[ 0.230649] pciback 0000:0a:00.6: pcistub_device_alloc
[ 0.230652] pciback 0000:0a:00.6: deferring initialization
[ 0.230662] pciback 0000:0a:00.7: probing...
[ 0.230666] pciback 0000:0a:00.7: seizing device
[ 0.230670] pciback 0000:0a:00.7: pcistub_device_alloc
[ 0.230674] pciback 0000:0a:00.7: deferring initialization
[ 0.230686] pciback 0000:09:00.0: probing...
[ 0.230699] pciback 0000:08:00.0: probing...
[ 0.230712] pciback 0000:06:00.0: probing...
[ 0.230725] pciback 0000:07:01.0: probing...
[ 0.230738] pciback 0000:07:01.1: probing...
[ 0.230750] pciback 0000:07:01.2: probing...
[ 0.230763] pciback 0000:05:00.0: probing...
[ 0.230766] pciback 0000:05:00.0: seizing device
[ 0.230770] pciback 0000:05:00.0: pcistub_device_alloc
[ 0.230773] pciback 0000:05:00.0: deferring initialization
[ 0.230783] pciback 0000:05:00.1: probing...
[ 0.230786] pciback 0000:05:00.1: seizing device
[ 0.230790] pciback 0000:05:00.1: pcistub_device_alloc
[ 0.230793] pciback 0000:05:00.1: deferring initialization
[ 0.230804] pciback 0000:04:00.0: probing...
[ 0.230807] pciback 0000:04:00.0: seizing device
[ 0.230811] pciback 0000:04:00.0: pcistub_device_alloc
[ 0.230814] pciback 0000:04:00.0: deferring initialization
[ 0.230824] pciback 0000:04:00.1: probing...
[ 0.230827] pciback 0000:04:00.1: seizing device
[ 0.230831] pciback 0000:04:00.1: pcistub_device_alloc
[ 0.230860] pciback 0000:04:00.1: deferring initialization
[ 0.230869] pciback 0000:04:00.2: probing...
[ 0.230872] pciback 0000:04:00.2: seizing device
[ 0.230876] pciback 0000:04:00.2: pcistub_device_alloc
[ 0.230878] pciback 0000:04:00.2: deferring initialization
[ 0.230887] pciback 0000:04:00.3: probing...
[ 0.230890] pciback 0000:04:00.3: seizing device
[ 0.230894] pciback 0000:04:00.3: pcistub_device_alloc
[ 0.230897] pciback 0000:04:00.3: deferring initialization
[ 0.230907] pciback 0000:04:00.4: probing...
[ 0.230910] pciback 0000:04:00.4: seizing device
[ 0.230914] pciback 0000:04:00.4: pcistub_device_alloc
[ 0.230917] pciback 0000:04:00.4: deferring initialization
[ 0.230926] pciback 0000:04:00.5: probing...
[ 0.230929] pciback 0000:04:00.5: seizing device
[ 0.230932] pciback 0000:04:00.5: pcistub_device_alloc
[ 0.230935] pciback 0000:04:00.5: deferring initialization
[ 0.230944] pciback 0000:04:00.6: probing...
[ 0.230947] pciback 0000:04:00.6: seizing device
[ 0.230950] pciback 0000:04:00.6: pcistub_device_alloc
[ 0.230953] pciback 0000:04:00.6: deferring initialization
[ 0.230962] pciback 0000:04:00.7: probing...
[ 0.230965] pciback 0000:04:00.7: seizing device
[ 0.230968] pciback 0000:04:00.7: pcistub_device_alloc
[ 0.230971] pciback 0000:04:00.7: deferring initialization
[ 0.230981] pciback 0000:03:06.0: probing...
[ 0.230983] pciback 0000:03:06.0: seizing device
[ 0.230987] pciback 0000:03:06.0: pcistub_device_alloc
[ 0.230990] pciback 0000:03:06.0: deferring initialization
[ 0.234748] PM-Timer failed consistency check (0x0xffffff) - aborting.
[ 0.234916] pci 0000:00:02.0: PCI bridge, secondary bus 0000:0b
[ 0.234922] pci 0000:00:02.0: IO window: 0xe000-0xefff
[ 0.234930] pci 0000:00:02.0: MEM window: 0xfa000000-0xfe9fffff
[ 0.234937] pci 0000:00:02.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
[ 0.234947] pci 0000:00:03.0: PCI bridge, secondary bus 0000:0a
[ 0.234951] pci 0000:00:03.0: IO window: disabled
[ 0.234958] pci 0000:00:03.0: MEM window: 0xf9f00000-0xf9ffffff
[ 0.234965] pci 0000:00:03.0: PREFETCH window: disabled
[ 0.234974] pci 0000:00:05.0: PCI bridge, secondary bus 0000:09
[ 0.234979] pci 0000:00:05.0: IO window: 0xd000-0xdfff
[ 0.234987] pci 0000:00:05.0: MEM window: 0xf9e00000-0xf9efffff
[ 0.234993] pci 0000:00:05.0: PREFETCH window: 0x000000cff00000-0x000000cfffffff
[ 0.235003] pci 0000:00:06.0: PCI bridge, secondary bus 0000:08
[ 0.235008] pci 0000:00:06.0: IO window: 0xc000-0xcfff
[ 0.235016] pci 0000:00:06.0: MEM window: 0xf9d00000-0xf9dfffff
[ 0.235022] pci 0000:00:06.0: PREFETCH window: 0x000000cfe00000-0x000000cfefffff
[ 0.235032] pci 0000:06:00.0: PCI bridge, secondary bus 0000:07
[ 0.235036] pci 0000:06:00.0: IO window: disabled
[ 0.235046] pci 0000:06:00.0: MEM window: 0xf9c00000-0xf9cfffff
[ 0.235054] pci 0000:06:00.0: PREFETCH window: disabled
[ 0.235066] pci 0000:00:0a.0: PCI bridge, secondary bus 0000:06
[ 0.235070] pci 0000:00:0a.0: IO window: disabled
[ 0.235080] pci 0000:00:0a.0: MEM window: 0xf9c00000-0xf9cfffff
[ 0.235088] pci 0000:00:0a.0: PREFETCH window: disabled
[ 0.235097] pci 0000:00:0b.0: PCI bridge, secondary bus 0000:05
[ 0.235102] pci 0000:00:0b.0: IO window: 0xb000-0xbfff
[ 0.235110] pci 0000:00:0b.0: MEM window: 0xf9b00000-0xf9bfffff
[ 0.235116] pci 0000:00:0b.0: PREFETCH window: 0x000000b0000000-0x000000bfffffff
[ 0.235126] pci 0000:00:0d.0: PCI bridge, secondary bus 0000:04
[ 0.235130] pci 0000:00:0d.0: IO window: disabled
[ 0.235137] pci 0000:00:0d.0: MEM window: 0xf9a00000-0xf9afffff
[ 0.235144] pci 0000:00:0d.0: PREFETCH window: disabled
[ 0.235153] pci 0000:00:14.4: PCI bridge, secondary bus 0000:03
[ 0.235161] pci 0000:00:14.4: IO window: 0xa000-0xafff
[ 0.235170] pci 0000:00:14.4: MEM window: disabled
[ 0.235177] pci 0000:00:14.4: PREFETCH window: disabled
[ 0.235187] pci 0000:00:15.0: PCI bridge, secondary bus 0000:02
[ 0.235191] pci 0000:00:15.0: IO window: disabled
[ 0.235199] pci 0000:00:15.0: MEM window: disabled
[ 0.235206] pci 0000:00:15.0: PREFETCH window: disabled
[ 0.235232] xen: registering gsi 52 triggering 0 polarity 1
[ 0.235247] alloc irq_desc for 52 on node 0
[ 0.235251] alloc kstat_irqs on node 0
[ 0.235258] xen: --> irq=52
[ 0.235279] pci 0000:00:02.0: PCI INT A -> GSI 52 (level, low) -> IRQ 52
[ 0.235288] pci 0000:00:02.0: setting latency timer to 64
[ 0.235300] xen: registering gsi 52 triggering 0 polarity 1
[ 0.235304] xen_allocate_pirq: returning irq 52 for gsi 52
[ 0.235307] xen: --> irq=52
[ 0.235310] Already setup the GSI :52
[ 0.235314] pci 0000:00:03.0: PCI INT A -> GSI 52 (level, low) -> IRQ 52
[ 0.235320] pci 0000:00:03.0: setting latency timer to 64
[ 0.235332] xen: registering gsi 52 triggering 0 polarity 1
[ 0.235335] xen_allocate_pirq: returning irq 52 for gsi 52
[ 0.235338] xen: --> irq=52
[ 0.235341] Already setup the GSI :52
[ 0.235345] pci 0000:00:05.0: PCI INT A -> GSI 52 (level, low) -> IRQ 52
[ 0.235351] pci 0000:00:05.0: setting latency timer to 64
[ 0.235363] xen: registering gsi 53 triggering 0 polarity 1
[ 0.235368] alloc irq_desc for 53 on node 0
[ 0.235371] alloc kstat_irqs on node 0
[ 0.235375] xen: --> irq=53
[ 0.235389] pci 0000:00:06.0: PCI INT A -> GSI 53 (level, low) -> IRQ 53
[ 0.235397] pci 0000:00:06.0: setting latency timer to 64
[ 0.235409] xen: registering gsi 54 triggering 0 polarity 1
[ 0.235414] alloc irq_desc for 54 on node 0
[ 0.235417] alloc kstat_irqs on node 0
[ 0.235421] xen: --> irq=54
[ 0.235435] pci 0000:00:0a.0: PCI INT A -> GSI 54 (level, low) -> IRQ 54
[ 0.235443] pci 0000:00:0a.0: setting latency timer to 64
[ 0.235461] pci 0000:06:00.0: setting latency timer to 64
[ 0.235469] xen: registering gsi 54 triggering 0 polarity 1
[ 0.235469] xen_allocate_pirq: returning irq 54 for gsi 54
[ 0.235469] xen: --> irq=54
[ 0.235489] Already setup the GSI :54
[ 0.235492] pci 0000:00:0b.0: PCI INT A -> GSI 54 (level, low) -> IRQ 54
[ 0.235499] pci 0000:00:0b.0: setting latency timer to 64
[ 0.235511] xen: registering gsi 54 triggering 0 polarity 1
[ 0.235514] xen_allocate_pirq: returning irq 54 for gsi 54
[ 0.235517] xen: --> irq=54
[ 0.235520] Already setup the GSI :54
[ 0.235524] pci 0000:00:0d.0: PCI INT A -> GSI 54 (level, low) -> IRQ 54
[ 0.235530] pci 0000:00:0d.0: setting latency timer to 64
[ 0.235553] xen: registering gsi 16 triggering 0 polarity 1
[ 0.235558] alloc irq_desc for 16 on node 0
[ 0.235561] alloc kstat_irqs on node 0
[ 0.235565] xen: --> irq=16
[ 0.235580] pci 0000:00:15.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.235588] pci 0000:00:15.0: setting latency timer to 64
[ 0.235594] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 0.235597] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff]
[ 0.235600] pci_bus 0000:0b: resource 0 io: [0xe000-0xefff]
[ 0.235603] pci_bus 0000:0b: resource 1 mem: [0xfa000000-0xfe9fffff]
[ 0.235606] pci_bus 0000:0b: resource 2 pref mem [0xd0000000-0xdfffffff]
[ 0.235609] pci_bus 0000:0a: resource 1 mem: [0xf9f00000-0xf9ffffff]
[ 0.235612] pci_bus 0000:09: resource 0 io: [0xd000-0xdfff]
[ 0.235615] pci_bus 0000:09: resource 1 mem: [0xf9e00000-0xf9efffff]
[ 0.235618] pci_bus 0000:09: resource 2 pref mem [0xcff00000-0xcfffffff]
[ 0.235621] pci_bus 0000:08: resource 0 io: [0xc000-0xcfff]
[ 0.235624] pci_bus 0000:08: resource 1 mem: [0xf9d00000-0xf9dfffff]
[ 0.235627] pci_bus 0000:08: resource 2 pref mem [0xcfe00000-0xcfefffff]
[ 0.235630] pci_bus 0000:06: resource 1 mem: [0xf9c00000-0xf9cfffff]
[ 0.235633] pci_bus 0000:07: resource 1 mem: [0xf9c00000-0xf9cfffff]
[ 0.235636] pci_bus 0000:05: resource 0 io: [0xb000-0xbfff]
[ 0.235638] pci_bus 0000:05: resource 1 mem: [0xf9b00000-0xf9bfffff]
[ 0.235641] pci_bus 0000:05: resource 2 pref mem [0xb0000000-0xbfffffff]
[ 0.235644] pci_bus 0000:04: resource 1 mem: [0xf9a00000-0xf9afffff]
[ 0.235647] pci_bus 0000:03: resource 0 io: [0xa000-0xafff]
[ 0.235650] pci_bus 0000:03: resource 3 io: [0x00-0xffff]
[ 0.235653] pci_bus 0000:03: resource 4 mem: [0x000000-0xffffffffffffffff]
[ 0.235674] NET: Registered protocol family 2
[ 0.235718] IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.236300] TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
[ 0.237309] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.237572] TCP: Hash tables configured (established 262144 bind 65536)
[ 0.237577] TCP reno registered
[ 0.237674] NET: Registered protocol family 1
[ 0.238180] RPC: Registered udp transport module.
[ 0.238185] RPC: Registered tcp transport module.
[ 0.238189] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.238203] pci 0000:00:00.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238209] pci 0000:00:00.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238214] pci 0000:00:00.0: calling pci_fixup_video+0x0/0xd1
[ 0.238219] pci 0000:00:00.2: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238223] pci 0000:00:00.2: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238228] pci 0000:00:00.2: calling pci_fixup_video+0x0/0xd1
[ 0.238235] pci 0000:00:02.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238239] pci 0000:00:02.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238243] pci 0000:00:02.0: calling pci_fixup_video+0x0/0xd1
[ 0.238252] pci 0000:00:03.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238256] pci 0000:00:03.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238262] pci 0000:00:03.0: calling pci_fixup_video+0x0/0xd1
[ 0.238267] pci 0000:00:05.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238271] pci 0000:00:05.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238275] pci 0000:00:05.0: calling pci_fixup_video+0x0/0xd1
[ 0.238280] pci 0000:00:06.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238283] pci 0000:00:06.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238287] pci 0000:00:06.0: calling pci_fixup_video+0x0/0xd1
[ 0.238292] pci 0000:00:0a.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238296] pci 0000:00:0a.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238299] pci 0000:00:0a.0: calling pci_fixup_video+0x0/0xd1
[ 0.238305] pci 0000:00:0b.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238308] pci 0000:00:0b.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238312] pci 0000:00:0b.0: calling pci_fixup_video+0x0/0xd1
[ 0.238317] pci 0000:00:0d.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238320] pci 0000:00:0d.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238324] pci 0000:00:0d.0: calling pci_fixup_video+0x0/0xd1
[ 0.238329] pci 0000:00:11.0: calling quirk_msi_intx_disable_ati_bug+0x0/0x4c
[ 0.238339] pci 0000:00:11.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238343] pci 0000:00:11.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.238346] pci 0000:00:11.0: calling pci_fixup_video+0x0/0xd1
[ 0.238352] pci 0000:00:12.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.238355] pci 0000:00:12.0: calling quirk_usb_early_handoff+0x0/0x699
[ 0.997137] pci 0000:00:12.0: calling pci_fixup_video+0x0/0xd1
[ 0.997150] pci 0000:00:12.2: calling quirk_cardbus_legacy+0x0/0x30
[ 0.997154] pci 0000:00:12.2: calling quirk_usb_early_handoff+0x0/0x699
[ 0.997195] pci 0000:00:12.2: calling pci_fixup_video+0x0/0xd1
[ 0.997201] pci 0000:00:13.0: calling quirk_cardbus_legacy+0x0/0x30
[ 0.997204] pci 0000:00:13.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.018162] pci 0000:00:13.0: calling pci_fixup_video+0x0/0xd1
[ 1.018171] pci 0000:00:13.2: calling quirk_cardbus_legacy+0x0/0x30
[ 1.018175] pci 0000:00:13.2: calling quirk_usb_early_handoff+0x0/0x699
[ 1.018208] pci 0000:00:13.2: calling pci_fixup_video+0x0/0xd1
[ 1.018214] pci 0000:00:14.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.018217] pci 0000:00:14.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.018221] pci 0000:00:14.0: calling pci_fixup_video+0x0/0xd1
[ 1.018226] pci 0000:00:14.3: calling quirk_cardbus_legacy+0x0/0x30
[ 1.018230] pci 0000:00:14.3: calling quirk_usb_early_handoff+0x0/0x699
[ 1.018234] pci 0000:00:14.3: calling pci_fixup_video+0x0/0xd1
[ 1.018239] pci 0000:00:14.4: calling quirk_cardbus_legacy+0x0/0x30
[ 1.018243] pci 0000:00:14.4: calling quirk_usb_early_handoff+0x0/0x699
[ 1.018247] pci 0000:00:14.4: calling pci_fixup_video+0x0/0xd1
[ 1.018252] pci 0000:00:14.5: calling quirk_cardbus_legacy+0x0/0x30
[ 1.018256] pci 0000:00:14.5: calling quirk_usb_early_handoff+0x0/0x699
[ 1.039142] pci 0000:00:14.5: calling pci_fixup_video+0x0/0xd1
[ 1.039151] pci 0000:00:15.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.039155] pci 0000:00:15.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.039158] pci 0000:00:15.0: calling pci_fixup_video+0x0/0xd1
[ 1.039163] pci 0000:00:16.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.039167] pci 0000:00:16.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060110] pci 0000:00:16.0: calling pci_fixup_video+0x0/0xd1
[ 1.060119] pci 0000:00:16.2: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060123] pci 0000:00:16.2: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060154] pci 0000:00:16.2: calling pci_fixup_video+0x0/0xd1
[ 1.060160] pci 0000:00:18.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060164] pci 0000:00:18.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060168] pci 0000:00:18.0: calling pci_fixup_video+0x0/0xd1
[ 1.060177] pci 0000:00:18.1: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060181] pci 0000:00:18.1: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060185] pci 0000:00:18.1: calling pci_fixup_video+0x0/0xd1
[ 1.060190] pci 0000:00:18.2: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060194] pci 0000:00:18.2: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060197] pci 0000:00:18.2: calling pci_fixup_video+0x0/0xd1
[ 1.060202] pci 0000:00:18.3: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060206] pci 0000:00:18.3: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060210] pci 0000:00:18.3: calling pci_fixup_video+0x0/0xd1
[ 1.060215] pci 0000:00:18.4: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060219] pci 0000:00:18.4: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060223] pci 0000:00:18.4: calling pci_fixup_video+0x0/0xd1
[ 1.060228] pci 0000:0b:00.0: calling nv_msi_ht_cap_quirk_leaf+0x0/0x12
[ 1.060249] pci 0000:0b:00.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060252] pci 0000:0b:00.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060256] pci 0000:0b:00.0: calling pci_fixup_video+0x0/0xd1
[ 1.060263] pci 0000:0b:00.0: Boot video device
[ 1.060268] pciback 0000:0a:00.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060272] pciback 0000:0a:00.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060292] pciback 0000:0a:00.0: calling pci_fixup_video+0x0/0xd1
[ 1.060298] pciback 0000:0a:00.1: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060302] pciback 0000:0a:00.1: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060324] pciback 0000:0a:00.1: calling pci_fixup_video+0x0/0xd1
[ 1.060333] pciback 0000:0a:00.2: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060343] pciback 0000:0a:00.2: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060362] pciback 0000:0a:00.2: calling pci_fixup_video+0x0/0xd1
[ 1.060367] pciback 0000:0a:00.3: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060370] pciback 0000:0a:00.3: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060391] pciback 0000:0a:00.3: calling pci_fixup_video+0x0/0xd1
[ 1.060396] pciback 0000:0a:00.4: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060400] pciback 0000:0a:00.4: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060418] pciback 0000:0a:00.4: calling pci_fixup_video+0x0/0xd1
[ 1.060423] pciback 0000:0a:00.5: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060426] pciback 0000:0a:00.5: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060447] pciback 0000:0a:00.5: calling pci_fixup_video+0x0/0xd1
[ 1.060453] pciback 0000:0a:00.6: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060456] pciback 0000:0a:00.6: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060485] pciback 0000:0a:00.6: calling pci_fixup_video+0x0/0xd1
[ 1.060492] pciback 0000:0a:00.7: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060497] pciback 0000:0a:00.7: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060521] pciback 0000:0a:00.7: calling pci_fixup_video+0x0/0xd1
[ 1.060526] pci 0000:09:00.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060530] pci 0000:09:00.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060533] pci 0000:09:00.0: calling pci_fixup_video+0x0/0xd1
[ 1.060538] pci 0000:08:00.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060541] pci 0000:08:00.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060544] pci 0000:08:00.0: calling pci_fixup_video+0x0/0xd1
[ 1.060549] pci 0000:06:00.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060552] pci 0000:06:00.0: calling quirk_xio2000a+0x0/0xa3
[ 1.060555] pci 0000:06:00.0: TI XIO2000a quirk detected; secondary bus fast back-to-back transfers disabled
[ 1.060570] pci 0000:06:00.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060573] pci 0000:06:00.0: calling pci_fixup_video+0x0/0xd1
[ 1.060578] pci 0000:07:01.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060581] pci 0000:07:01.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060599] pci 0000:07:01.0: calling pci_fixup_video+0x0/0xd1
[ 1.060604] pci 0000:07:01.1: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060608] pci 0000:07:01.1: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060626] pci 0000:07:01.1: calling pci_fixup_video+0x0/0xd1
[ 1.060631] pci 0000:07:01.2: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060634] pci 0000:07:01.2: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060660] pci 0000:07:01.2: calling pci_fixup_video+0x0/0xd1
[ 1.060669] pciback 0000:05:00.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060673] pciback 0000:05:00.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060676] pciback 0000:05:00.0: calling pci_fixup_video+0x0/0xd1
[ 1.060683] pciback 0000:05:00.1: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060686] pciback 0000:05:00.1: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060690] pciback 0000:05:00.1: calling pci_fixup_video+0x0/0xd1
[ 1.060694] pciback 0000:04:00.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060698] pciback 0000:04:00.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060715] pciback 0000:04:00.0: calling pci_fixup_video+0x0/0xd1
[ 1.060721] pciback 0000:04:00.1: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060724] pciback 0000:04:00.1: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060744] pciback 0000:04:00.1: calling pci_fixup_video+0x0/0xd1
[ 1.060755] pciback 0000:04:00.2: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060758] pciback 0000:04:00.2: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060778] pciback 0000:04:00.2: calling pci_fixup_video+0x0/0xd1
[ 1.060783] pciback 0000:04:00.3: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060786] pciback 0000:04:00.3: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060910] pciback 0000:04:00.3: calling pci_fixup_video+0x0/0xd1
[ 1.060915] pciback 0000:04:00.4: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060918] pciback 0000:04:00.4: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060936] pciback 0000:04:00.4: calling pci_fixup_video+0x0/0xd1
[ 1.060942] pciback 0000:04:00.5: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060945] pciback 0000:04:00.5: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060966] pciback 0000:04:00.5: calling pci_fixup_video+0x0/0xd1
[ 1.060971] pciback 0000:04:00.6: calling quirk_cardbus_legacy+0x0/0x30
[ 1.060974] pciback 0000:04:00.6: calling quirk_usb_early_handoff+0x0/0x699
[ 1.060992] pciback 0000:04:00.6: calling pci_fixup_video+0x0/0xd1
[ 1.060998] pciback 0000:04:00.7: calling quirk_cardbus_legacy+0x0/0x30
[ 1.061001] pciback 0000:04:00.7: calling quirk_usb_early_handoff+0x0/0x699
[ 1.061021] pciback 0000:04:00.7: calling pci_fixup_video+0x0/0xd1
[ 1.061027] pciback 0000:03:06.0: calling quirk_cardbus_legacy+0x0/0x30
[ 1.061030] pciback 0000:03:06.0: calling quirk_usb_early_handoff+0x0/0x699
[ 1.061033] pciback 0000:03:06.0: calling pci_fixup_video+0x0/0xd1
[ 1.061110] Trying to unpack rootfs image as initramfs...
[ 1.069603] Freeing initrd memory: 9003k freed
[ 1.072157] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 1.072165] DMA: Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000
[ 1.072170] DMA: software IO TLB at phys 0x20000000 - 0x24000000
[ 1.072319] kvm: no hardware support
[ 1.072328] has_svm: svm not available
[ 1.072331] kvm: no hardware support
[ 1.077179] Scanning for low memory corruption every 60 seconds
[ 1.077626] audit: initializing netlink socket (disabled)
[ 1.077644] type=2000 audit(1292177416.827:1): initialized
[ 1.078224] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 1.084587] VFS: Disk quotas dquot_6.5.2
[ 1.084756] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 1.088483] Btrfs loaded
[ 1.088495] msgmni has been set to 1111
[ 1.088648] SELinux: Registering netfilter hooks
[ 1.090152] alg: No test for stdrng (krng)
[ 1.090431] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 1.090439] io scheduler noop registered
[ 1.090443] io scheduler anticipatory registered
[ 1.090447] io scheduler deadline registered
[ 1.090576] io scheduler cfq registered (default)
[ 1.091063] alloc irq_desc for 1753 on node 0
[ 1.091066] alloc kstat_irqs on node 0
[ 1.091107] pcieport 0000:00:02.0: setting latency timer to 64
[ 1.091456] alloc irq_desc for 1752 on node 0
[ 1.091459] alloc kstat_irqs on node 0
[ 1.091495] pcieport 0000:00:03.0: setting latency timer to 64
[ 1.091980] alloc irq_desc for 1751 on node 0
[ 1.091983] alloc kstat_irqs on node 0
[ 1.092013] pcieport 0000:00:05.0: setting latency timer to 64
[ 1.092284] alloc irq_desc for 1750 on node 0
[ 1.092287] alloc kstat_irqs on node 0
[ 1.092312] pcieport 0000:00:06.0: setting latency timer to 64
[ 1.092610] alloc irq_desc for 1749 on node 0
[ 1.092613] alloc kstat_irqs on node 0
[ 1.092636] pcieport 0000:00:0a.0: setting latency timer to 64
[ 1.093047] alloc irq_desc for 1748 on node 0
[ 1.093051] alloc kstat_irqs on node 0
[ 1.093083] pcieport 0000:00:0b.0: setting latency timer to 64
[ 1.093405] alloc irq_desc for 1747 on node 0
[ 1.093408] alloc kstat_irqs on node 0
[ 1.093433] pcieport 0000:00:0d.0: setting latency timer to 64
[ 1.093874] alloc irq_desc for 1746 on node 0
[ 1.093877] alloc kstat_irqs on node 0
[ 1.093914] pcieport 0000:00:15.0: setting latency timer to 64
[ 1.094401] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 1.094660] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 1.097666] vesafb: framebuffer at 0xfb000000, mapped to 0xffffc90010100000, using 10240k, total 14336k
[ 1.097671] vesafb: mode is 1280x1024x32, linelength=5120, pages=0
[ 1.097675] vesafb: scrolling: redraw
[ 1.097679] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 1.119590] Console: switching to colour frame buffer device 160x64
[ 1.140469] fb0: VESA VGA frame buffer device
[ 1.141431] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[ 1.141649] ACPI: Power Button [PWRB]
[ 1.141927] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 1.142113] ACPI: Power Button [PWRF]
[ 1.143424] ACPI: CPU-1 (power states: C1[C1] C2[C2])
[ 1.143714] ACPI: CPU-1 (power states: C1[C1] C2[C2])
[ 1.143990] ACPI: CPU-1 (power states: C1[C1] C2[C2])
[ 1.144285] ACPI: CPU-1 (power states: C1[C1] C2[C2])
[ 1.144548] ACPI: CPU-1 (power states: C1[C1] C2[C2])
[ 1.144871] ACPI: CPU-1 (power states: C1[C1] C2[C2])
[ 1.148257] Event-channel device installed.
[ 1.148583] pciback: pcistub_init_devices_late
[ 1.148590] pciback 0000:03:06.0: initializing...
[ 1.148596] pciback 0000:03:06.0: initializing config
[ 1.148599] pciback 0000:03:06.0: initializing virtual configuration space
[ 1.148604] pciback 0000:03:06.0: added config field at offset 0x00
[ 1.148609] pciback 0000:03:06.0: added config field at offset 0x02
[ 1.148612] pciback 0000:03:06.0: added config field at offset 0x04
[ 1.148616] pciback 0000:03:06.0: added config field at offset 0x3c
[ 1.148621] pciback 0000:03:06.0: added config field at offset 0x3d
[ 1.148624] pciback 0000:03:06.0: added config field at offset 0x0c
[ 1.148628] pciback 0000:03:06.0: added config field at offset 0x0d
[ 1.148633] pciback 0000:03:06.0: added config field at offset 0x0f
[ 1.148638] pciback 0000:03:06.0: added config field at offset 0x10
[ 1.148643] pciback 0000:03:06.0: added config field at offset 0x14
[ 1.148648] pciback 0000:03:06.0: added config field at offset 0x18
[ 1.148653] pciback 0000:03:06.0: added config field at offset 0x1c
[ 1.148659] pciback 0000:03:06.0: added config field at offset 0x20
[ 1.148665] pciback 0000:03:06.0: added config field at offset 0x24
[ 1.148671] pciback 0000:03:06.0: added config field at offset 0x30
[ 1.148696] pciback 0000:03:06.0: Found capability 0x1 at 0xc0
[ 1.148699] pciback 0000:03:06.0: added config field at offset 0xc0
[ 1.148702] pciback 0000:03:06.0: added config field at offset 0xc2
[ 1.148708] pciback 0000:03:06.0: added config field at offset 0xc4
[ 1.148711] pciback 0000:03:06.0: added config field at offset 0xc6
[ 1.148714] pciback 0000:03:06.0: added config field at offset 0xc7
[ 1.148718] pciback 0000:03:06.0: enabling device
[ 1.148738] xen: registering gsi 22 triggering 0 polarity 1
[ 1.148748] alloc irq_desc for 22 on node 0
[ 1.148751] alloc kstat_irqs on node 0
[ 1.148756] xen: --> irq=22
[ 1.148784] pciback 0000:03:06.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 1.148955] pciback 0000:03:06.0: reset device
[ 1.148968] pciback 0000:03:06.0: PCI INT A disabled
[ 1.149103] pciback 0000:04:00.7: initializing...
[ 1.149108] pciback 0000:04:00.7: initializing config
[ 1.149113] pciback 0000:04:00.7: initializing virtual configuration space
[ 1.149117] pciback 0000:04:00.7: added config field at offset 0x00
[ 1.149120] pciback 0000:04:00.7: added config field at offset 0x02
[ 1.149123] pciback 0000:04:00.7: added config field at offset 0x04
[ 1.149129] pciback 0000:04:00.7: added config field at offset 0x3c
[ 1.149133] pciback 0000:04:00.7: added config field at offset 0x3d
[ 1.149136] pciback 0000:04:00.7: added config field at offset 0x0c
[ 1.149139] pciback 0000:04:00.7: added config field at offset 0x0d
[ 1.149142] pciback 0000:04:00.7: added config field at offset 0x0f
[ 1.149146] pciback 0000:04:00.7: added config field at offset 0x10
[ 1.149150] pciback 0000:04:00.7: added config field at offset 0x14
[ 1.149153] pciback 0000:04:00.7: added config field at offset 0x18
[ 1.149156] pciback 0000:04:00.7: added config field at offset 0x1c
[ 1.149160] pciback 0000:04:00.7: added config field at offset 0x20
[ 1.149164] pciback 0000:04:00.7: added config field at offset 0x24
[ 1.149169] pciback 0000:04:00.7: added config field at offset 0x30
[ 1.149208] pciback 0000:04:00.7: Found capability 0x1 at 0x78
[ 1.149211] pciback 0000:04:00.7: added config field at offset 0x78
[ 1.149214] pciback 0000:04:00.7: added config field at offset 0x7a
[ 1.149220] pciback 0000:04:00.7: added config field at offset 0x7c
[ 1.149226] pciback 0000:04:00.7: added config field at offset 0x7e
[ 1.149232] pciback 0000:04:00.7: added config field at offset 0x7f
[ 1.149237] pciback 0000:04:00.7: enabling device
[ 1.149254] xen: registering gsi 43 triggering 0 polarity 1
[ 1.149260] alloc irq_desc for 43 on node 0
[ 1.149263] alloc kstat_irqs on node 0
[ 1.149268] xen: --> irq=43
[ 1.149285] pciback 0000:04:00.7: PCI INT D -> GSI 43 (level, low) -> IRQ 43
[ 1.149458] pciback 0000:04:00.7: reset device
[ 1.149467] pciback 0000:04:00.7: PCI INT D disabled
[ 1.149569] pciback 0000:04:00.6: initializing...
[ 1.149569] pciback 0000:04:00.6: initializing config
[ 1.149569] pciback 0000:04:00.6: initializing virtual configuration space
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x00
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x02
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x04
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x3c
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x3d
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x0c
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x0d
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x0f
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x10
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x14
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x18
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x1c
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x20
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x24
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x30
[ 1.149569] pciback 0000:04:00.6: Found capability 0x1 at 0x78
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x78
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x7a
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x7c
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x7e
[ 1.149569] pciback 0000:04:00.6: added config field at offset 0x7f
[ 1.149569] pciback 0000:04:00.6: enabling device
[ 1.149569] xen: registering gsi 43 triggering 0 polarity 1
[ 1.149569] xen_allocate_pirq: returning irq 43 for gsi 43
[ 1.149569] xen: --> irq=43
[ 1.149846] Already setup the GSI :43
[ 1.149935] pciback 0000:04:00.6: PCI INT D -> GSI 43 (level, low) -> IRQ 43
[ 1.150105] pciback 0000:04:00.6: reset device
[ 1.150115] pciback 0000:04:00.6: PCI INT D disabled
[ 1.150244] pciback 0000:04:00.5: initializing...
[ 1.150247] pciback 0000:04:00.5: initializing config
[ 1.150250] pciback 0000:04:00.5: initializing virtual configuration space
[ 1.150253] pciback 0000:04:00.5: added config field at offset 0x00
[ 1.150257] pciback 0000:04:00.5: added config field at offset 0x02
[ 1.150262] pciback 0000:04:00.5: added config field at offset 0x04
[ 1.150269] pciback 0000:04:00.5: added config field at offset 0x3c
[ 1.150273] pciback 0000:04:00.5: added config field at offset 0x3d
[ 1.150277] pciback 0000:04:00.5: added config field at offset 0x0c
[ 1.150283] pciback 0000:04:00.5: added config field at offset 0x0d
[ 1.150287] pciback 0000:04:00.5: added config field at offset 0x0f
[ 1.150291] pciback 0000:04:00.5: added config field at offset 0x10
[ 1.150296] pciback 0000:04:00.5: added config field at offset 0x14
[ 1.150308] pciback 0000:04:00.5: added config field at offset 0x18
[ 1.150314] pciback 0000:04:00.5: added config field at offset 0x1c
[ 1.150317] pciback 0000:04:00.5: added config field at offset 0x20
[ 1.150320] pciback 0000:04:00.5: added config field at offset 0x24
[ 1.150324] pciback 0000:04:00.5: added config field at offset 0x30
[ 1.150366] pciback 0000:04:00.5: Found capability 0x1 at 0x78
[ 1.150372] pciback 0000:04:00.5: added config field at offset 0x78
[ 1.150375] pciback 0000:04:00.5: added config field at offset 0x7a
[ 1.150381] pciback 0000:04:00.5: added config field at offset 0x7c
[ 1.150384] pciback 0000:04:00.5: added config field at offset 0x7e
[ 1.150388] pciback 0000:04:00.5: added config field at offset 0x7f
[ 1.150391] pciback 0000:04:00.5: enabling device
[ 1.150404] xen: registering gsi 42 triggering 0 polarity 1
[ 1.150411] alloc irq_desc for 42 on node 0
[ 1.150413] alloc kstat_irqs on node 0
[ 1.150418] xen: --> irq=42
[ 1.150435] pciback 0000:04:00.5: PCI INT C -> GSI 42 (level, low) -> IRQ 42
[ 1.150606] pciback 0000:04:00.5: reset device
[ 1.150614] pciback 0000:04:00.5: PCI INT C disabled
[ 1.150741] pciback 0000:04:00.4: initializing...
[ 1.150744] pciback 0000:04:00.4: initializing config
[ 1.150747] pciback 0000:04:00.4: initializing virtual configuration space
[ 1.150750] pciback 0000:04:00.4: added config field at offset 0x00
[ 1.150753] pciback 0000:04:00.4: added config field at offset 0x02
[ 1.150755] pciback 0000:04:00.4: added config field at offset 0x04
[ 1.150758] pciback 0000:04:00.4: added config field at offset 0x3c
[ 1.150760] pciback 0000:04:00.4: added config field at offset 0x3d
[ 1.150763] pciback 0000:04:00.4: added config field at offset 0x0c
[ 1.150766] pciback 0000:04:00.4: added config field at offset 0x0d
[ 1.150769] pciback 0000:04:00.4: added config field at offset 0x0f
[ 1.150772] pciback 0000:04:00.4: added config field at offset 0x10
[ 1.150774] pciback 0000:04:00.4: added config field at offset 0x14
[ 1.150777] pciback 0000:04:00.4: added config field at offset 0x18
[ 1.150779] pciback 0000:04:00.4: added config field at offset 0x1c
[ 1.150782] pciback 0000:04:00.4: added config field at offset 0x20
[ 1.150785] pciback 0000:04:00.4: added config field at offset 0x24
[ 1.150787] pciback 0000:04:00.4: added config field at offset 0x30
[ 1.150818] pciback 0000:04:00.4: Found capability 0x1 at 0x78
[ 1.150821] pciback 0000:04:00.4: added config field at offset 0x78
[ 1.150824] pciback 0000:04:00.4: added config field at offset 0x7a
[ 1.150829] pciback 0000:04:00.4: added config field at offset 0x7c
[ 1.150831] pciback 0000:04:00.4: added config field at offset 0x7e
[ 1.150834] pciback 0000:04:00.4: added config field at offset 0x7f
[ 1.150836] pciback 0000:04:00.4: enabling device
[ 1.150841] xen: registering gsi 42 triggering 0 polarity 1
[ 1.150841] xen_allocate_pirq: returning irq 42 for gsi 42
[ 1.150841] xen: --> irq=42
[ 1.150992] Already setup the GSI :42
[ 1.151081] pciback 0000:04:00.4: PCI INT C -> GSI 42 (level, low) -> IRQ 42
[ 1.151251] pciback 0000:04:00.4: reset device
[ 1.151259] pciback 0000:04:00.4: PCI INT C disabled
[ 1.151387] pciback 0000:04:00.3: initializing...
[ 1.151390] pciback 0000:04:00.3: initializing config
[ 1.151393] pciback 0000:04:00.3: initializing virtual configuration space
[ 1.151396] pciback 0000:04:00.3: added config field at offset 0x00
[ 1.151399] pciback 0000:04:00.3: added config field at offset 0x02
[ 1.151403] pciback 0000:04:00.3: added config field at offset 0x04
[ 1.151406] pciback 0000:04:00.3: added config field at offset 0x3c
[ 1.151409] pciback 0000:04:00.3: added config field at offset 0x3d
[ 1.151412] pciback 0000:04:00.3: added config field at offset 0x0c
[ 1.151415] pciback 0000:04:00.3: added config field at offset 0x0d
[ 1.151418] pciback 0000:04:00.3: added config field at offset 0x0f
[ 1.151421] pciback 0000:04:00.3: added config field at offset 0x10
[ 1.151425] pciback 0000:04:00.3: added config field at offset 0x14
[ 1.151428] pciback 0000:04:00.3: added config field at offset 0x18
[ 1.151432] pciback 0000:04:00.3: added config field at offset 0x1c
[ 1.151435] pciback 0000:04:00.3: added config field at offset 0x20
[ 1.151438] pciback 0000:04:00.3: added config field at offset 0x24
[ 1.151442] pciback 0000:04:00.3: added config field at offset 0x30
[ 1.151477] pciback 0000:04:00.3: Found capability 0x1 at 0x78
[ 1.151481] pciback 0000:04:00.3: added config field at offset 0x78
[ 1.151484] pciback 0000:04:00.3: added config field at offset 0x7a
[ 1.151489] pciback 0000:04:00.3: added config field at offset 0x7c
[ 1.151492] pciback 0000:04:00.3: added config field at offset 0x7e
[ 1.151495] pciback 0000:04:00.3: added config field at offset 0x7f
[ 1.151500] pciback 0000:04:00.3: enabling device
[ 1.151513] xen: registering gsi 41 triggering 0 polarity 1
[ 1.151518] alloc irq_desc for 41 on node 0
[ 1.151521] alloc kstat_irqs on node 0
[ 1.151530] xen: --> irq=41
[ 1.151545] pciback 0000:04:00.3: PCI INT B -> GSI 41 (level, low) -> IRQ 41
[ 1.151732] pciback 0000:04:00.3: reset device
[ 1.151741] pciback 0000:04:00.3: PCI INT B disabled
[ 1.151863] pciback 0000:04:00.2: initializing...
[ 1.151866] pciback 0000:04:00.2: initializing config
[ 1.151869] pciback 0000:04:00.2: initializing virtual configuration space
[ 1.151872] pciback 0000:04:00.2: added config field at offset 0x00
[ 1.151875] pciback 0000:04:00.2: added config field at offset 0x02
[ 1.151878] pciback 0000:04:00.2: added config field at offset 0x04
[ 1.151881] pciback 0000:04:00.2: added config field at offset 0x3c
[ 1.151883] pciback 0000:04:00.2: added config field at offset 0x3d
[ 1.151886] pciback 0000:04:00.2: added config field at offset 0x0c
[ 1.151889] pciback 0000:04:00.2: added config field at offset 0x0d
[ 1.151892] pciback 0000:04:00.2: added config field at offset 0x0f
[ 1.151895] pciback 0000:04:00.2: added config field at offset 0x10
[ 1.151898] pciback 0000:04:00.2: added config field at offset 0x14
[ 1.151901] pciback 0000:04:00.2: added config field at offset 0x18
[ 1.151904] pciback 0000:04:00.2: added config field at offset 0x1c
[ 1.151907] pciback 0000:04:00.2: added config field at offset 0x20
[ 1.151910] pciback 0000:04:00.2: added config field at offset 0x24
[ 1.151913] pciback 0000:04:00.2: added config field at offset 0x30
[ 1.151945] pciback 0000:04:00.2: Found capability 0x1 at 0x78
[ 1.151948] pciback 0000:04:00.2: added config field at offset 0x78
[ 1.151951] pciback 0000:04:00.2: added config field at offset 0x7a
[ 1.151956] pciback 0000:04:00.2: added config field at offset 0x7c
[ 1.151959] pciback 0000:04:00.2: added config field at offset 0x7e
[ 1.151962] pciback 0000:04:00.2: added config field at offset 0x7f
[ 1.151965] pciback 0000:04:00.2: enabling device
[ 1.151977] xen: registering gsi 41 triggering 0 polarity 1
[ 1.151980] xen_allocate_pirq: returning irq 41 for gsi 41
[ 1.152113] xen: --> irq=41
[ 1.152116] Already setup the GSI :41
[ 1.152205] pciback 0000:04:00.2: PCI INT B -> GSI 41 (level, low) -> IRQ 41
[ 1.152380] pciback 0000:04:00.2: reset device
[ 1.152389] pciback 0000:04:00.2: PCI INT B disabled
[ 1.152511] pciback 0000:04:00.1: initializing...
[ 1.152514] pciback 0000:04:00.1: initializing config
[ 1.152517] pciback 0000:04:00.1: initializing virtual configuration space
[ 1.152520] pciback 0000:04:00.1: added config field at offset 0x00
[ 1.152523] pciback 0000:04:00.1: added config field at offset 0x02
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x04
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x3c
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x3d
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x0c
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x0d
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x0f
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x10
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x14
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x18
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x1c
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x20
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x24
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x30
[ 1.152526] pciback 0000:04:00.1: Found capability 0x1 at 0x78
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x78
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x7a
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x7c
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x7e
[ 1.152526] pciback 0000:04:00.1: added config field at offset 0x7f
[ 1.152526] pciback 0000:04:00.1: enabling device
[ 1.152526] xen: registering gsi 40 triggering 0 polarity 1
[ 1.152526] alloc irq_desc for 40 on node 0
[ 1.152526] alloc kstat_irqs on node 0
[ 1.152648] xen: --> irq=40
[ 1.152664] pciback 0000:04:00.1: PCI INT A -> GSI 40 (level, low) -> IRQ 40
[ 1.152840] pciback 0000:04:00.1: reset device
[ 1.152848] pciback 0000:04:00.1: PCI INT A disabled
[ 1.153644] pciback 0000:04:00.0: initializing...
[ 1.153644] pciback 0000:04:00.0: initializing config
[ 1.153644] pciback 0000:04:00.0: initializing virtual configuration space
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x00
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x02
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x04
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x3c
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x3d
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x0c
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x0d
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x0f
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x10
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x14
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x18
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x1c
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x20
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x24
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x30
[ 1.153644] pciback 0000:04:00.0: Found capability 0x1 at 0x78
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x78
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x7a
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x7c
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x7e
[ 1.153644] pciback 0000:04:00.0: added config field at offset 0x7f
[ 1.153644] pciback 0000:04:00.0: enabling device
[ 1.153644] xen: registering gsi 40 triggering 0 polarity 1
[ 1.153644] xen_allocate_pirq: returning irq 40 for gsi 40
[ 1.153644] xen: --> irq=40
[ 1.159460] Already setup the GSI :40
[ 1.160455] pciback 0000:04:00.0: PCI INT A -> GSI 40 (level, low) -> IRQ 40
[ 1.160455] pciback 0000:04:00.0: reset device
[ 1.160455] pciback 0000:04:00.0: PCI INT A disabled
[ 1.160455] pciback 0000:05:00.1: initializing...
[ 1.160455] pciback 0000:05:00.1: initializing config
[ 1.160455] pciback 0000:05:00.1: initializing virtual configuration space
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x00
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x02
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x04
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x3c
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x3d
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x0c
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x0d
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x0f
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x10
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x14
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x18
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x1c
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x20
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x24
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x30
[ 1.160455] pciback 0000:05:00.1: Found capability 0x1 at 0x50
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x50
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x52
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x54
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x56
[ 1.160455] pciback 0000:05:00.1: added config field at offset 0x57
[ 1.160455] pciback 0000:05:00.1: enabling device
[ 1.160455] xen: registering gsi 33 triggering 0 polarity 1
[ 1.160455] alloc irq_desc for 33 on node 0
[ 1.160455] alloc kstat_irqs on node 0
[ 1.169979] xen: --> irq=33
[ 1.170001] pciback 0000:05:00.1: PCI INT B -> GSI 33 (level, low) -> IRQ 33
[ 1.170975] pciback 0000:05:00.1: reset device
[ 1.170975] pciback 0000:05:00.1: PCI INT B disabled
[ 1.170975] pciback 0000:05:00.0: initializing...
[ 1.170975] pciback 0000:05:00.0: initializing config
[ 1.170975] pciback 0000:05:00.0: initializing virtual configuration space
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x00
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x02
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x04
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x3c
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x3d
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x0c
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x0d
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x0f
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x10
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x14
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x18
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x1c
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x20
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x24
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x30
[ 1.170975] pciback 0000:05:00.0: Found capability 0x1 at 0x50
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x50
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x52
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x54
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x56
[ 1.170975] pciback 0000:05:00.0: added config field at offset 0x57
[ 1.170975] pciback 0000:05:00.0: enabling device
[ 1.170975] pciback 0000:05:00.0: enabling device (0000 -> 0003)
[ 1.170975] xen: registering gsi 32 triggering 0 polarity 1
[ 1.170975] alloc irq_desc for 32 on node 0
[ 1.170975] alloc kstat_irqs on node 0
[ 1.181219] xen: --> irq=32
[ 1.181247] pciback 0000:05:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[ 1.182215] pciback 0000:05:00.0: reset device
[ 1.182215] pciback 0000:05:00.0: PCI INT A disabled
[ 1.182215] pciback 0000:0a:00.7: initializing...
[ 1.182215] pciback 0000:0a:00.7: initializing config
[ 1.182215] pciback 0000:0a:00.7: initializing virtual configuration space
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x00
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x02
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x04
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x3c
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x3d
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x0c
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x0d
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x0f
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x10
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x14
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x18
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x1c
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x20
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x24
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x30
[ 1.182215] pciback 0000:0a:00.7: Found capability 0x1 at 0x78
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x78
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x7a
[ 1.182215] pciback 0000:0a:00.7: added config field at offset 0x7c
[ 1.189107] pciback 0000:0a:00.7: added config field at offset 0x7e
[ 1.189110] pciback 0000:0a:00.7: added config field at offset 0x7f
[ 1.189114] pciback 0000:0a:00.7: enabling device
[ 1.189127] xen: registering gsi 31 triggering 0 polarity 1
[ 1.189132] alloc irq_desc for 31 on node 0
[ 1.189135] alloc kstat_irqs on node 0
[ 1.189139] xen: --> irq=31
[ 1.189157] pciback 0000:0a:00.7: PCI INT D -> GSI 31 (level, low) -> IRQ 31
[ 1.190100] pciback 0000:0a:00.7: reset device
[ 1.190100] pciback 0000:0a:00.7: PCI INT D disabled
[ 1.190100] pciback 0000:0a:00.6: initializing...
[ 1.190100] pciback 0000:0a:00.6: initializing config
[ 1.190100] pciback 0000:0a:00.6: initializing virtual configuration space
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x00
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x02
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x04
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x3c
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x3d
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x0c
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x0d
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x0f
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x10
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x14
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x18
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x1c
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x20
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x24
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x30
[ 1.190100] pciback 0000:0a:00.6: Found capability 0x1 at 0x78
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x78
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x7a
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x7c
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x7e
[ 1.190100] pciback 0000:0a:00.6: added config field at offset 0x7f
[ 1.190100] pciback 0000:0a:00.6: enabling device
[ 1.190100] xen: registering gsi 31 triggering 0 polarity 1
[ 1.190100] xen_allocate_pirq: returning irq 31 for gsi 31
[ 1.190100] xen: --> irq=31
[ 1.201432] Already setup the GSI :31
[ 1.202428] pciback 0000:0a:00.6: PCI INT D -> GSI 31 (level, low) -> IRQ 31
[ 1.202428] pciback 0000:0a:00.6: reset device
[ 1.202428] pciback 0000:0a:00.6: PCI INT D disabled
[ 1.202428] pciback 0000:0a:00.5: initializing...
[ 1.202428] pciback 0000:0a:00.5: initializing config
[ 1.202428] pciback 0000:0a:00.5: initializing virtual configuration space
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x00
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x02
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x04
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x3c
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x3d
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x0c
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x0d
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x0f
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x10
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x14
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x18
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x1c
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x20
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x24
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x30
[ 1.202428] pciback 0000:0a:00.5: Found capability 0x1 at 0x78
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x78
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x7a
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x7c
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x7e
[ 1.202428] pciback 0000:0a:00.5: added config field at offset 0x7f
[ 1.202428] pciback 0000:0a:00.5: enabling device
[ 1.202428] xen: registering gsi 30 triggering 0 polarity 1
[ 1.202428] alloc irq_desc for 30 on node 0
[ 1.202428] alloc kstat_irqs on node 0
[ 1.214430] xen: --> irq=30
[ 1.214445] pciback 0000:0a:00.5: PCI INT C -> GSI 30 (level, low) -> IRQ 30
[ 1.215425] pciback 0000:0a:00.5: reset device
[ 1.215425] pciback 0000:0a:00.5: PCI INT C disabled
[ 1.215425] pciback 0000:0a:00.4: initializing...
[ 1.215425] pciback 0000:0a:00.4: initializing config
[ 1.215425] pciback 0000:0a:00.4: initializing virtual configuration space
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x00
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x02
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x04
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x3c
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x3d
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x0c
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x0d
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x0f
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x10
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x14
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x18
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x1c
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x20
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x24
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x30
[ 1.215425] pciback 0000:0a:00.4: Found capability 0x1 at 0x78
[ 1.215425] pciback 0000:0a:00.4: added config field at offset 0x78
[ 1.223543] pciback 0000:0a:00.4: added config field at offset 0x7a
[ 1.223549] pciback 0000:0a:00.4: added config field at offset 0x7c
[ 1.223553] pciback 0000:0a:00.4: added config field at offset 0x7e
[ 1.223556] pciback 0000:0a:00.4: added config field at offset 0x7f
[ 1.223559] pciback 0000:0a:00.4: enabling device
[ 1.223573] xen: registering gsi 30 triggering 0 polarity 1
[ 1.223576] xen_allocate_pirq: returning irq 30 for gsi 30
[ 1.224537] xen: --> irq=30
[ 1.228197] Already setup the GSI :30
[ 1.229193] pciback 0000:0a:00.4: PCI INT C -> GSI 30 (level, low) -> IRQ 30
[ 1.229193] pciback 0000:0a:00.4: reset device
[ 1.229193] pciback 0000:0a:00.4: PCI INT C disabled
[ 1.229193] pciback 0000:0a:00.3: initializing...
[ 1.229193] pciback 0000:0a:00.3: initializing config
[ 1.229193] pciback 0000:0a:00.3: initializing virtual configuration space
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x00
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x02
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x04
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x3c
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x3d
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x0c
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x0d
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x0f
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x10
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x14
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x18
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x1c
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x20
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x24
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x30
[ 1.229193] pciback 0000:0a:00.3: Found capability 0x1 at 0x78
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x78
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x7a
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x7c
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x7e
[ 1.229193] pciback 0000:0a:00.3: added config field at offset 0x7f
[ 1.229193] pciback 0000:0a:00.3: enabling device
[ 1.229193] xen: registering gsi 29 triggering 0 polarity 1
[ 1.229193] alloc irq_desc for 29 on node 0
[ 1.229193] alloc kstat_irqs on node 0
[ 1.242654] xen: --> irq=29
[ 1.242670] pciback 0000:0a:00.3: PCI INT B -> GSI 29 (level, low) -> IRQ 29
[ 1.243650] pciback 0000:0a:00.3: reset device
[ 1.243650] pciback 0000:0a:00.3: PCI INT B disabled
[ 1.243650] pciback 0000:0a:00.2: initializing...
[ 1.243650] pciback 0000:0a:00.2: initializing config
[ 1.243650] pciback 0000:0a:00.2: initializing virtual configuration space
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x00
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x02
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x04
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x3c
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x3d
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x0c
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x0d
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x0f
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x10
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x14
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x18
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x1c
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x20
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x24
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x30
[ 1.243650] pciback 0000:0a:00.2: Found capability 0x1 at 0x78
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x78
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x7a
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x7c
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x7e
[ 1.243650] pciback 0000:0a:00.2: added config field at offset 0x7f
[ 1.243650] pciback 0000:0a:00.2: enabling device
[ 1.243650] xen: registering gsi 29 triggering 0 polarity 1
[ 1.243650] xen_allocate_pirq: returning irq 29 for gsi 29
[ 1.243650] xen: --> irq=29
[ 1.257686] Already setup the GSI :29
[ 1.258681] pciback 0000:0a:00.2: PCI INT B -> GSI 29 (level, low) -> IRQ 29
[ 1.258681] pciback 0000:0a:00.2: reset device
[ 1.258681] pciback 0000:0a:00.2: PCI INT B disabled
[ 1.258681] pciback 0000:0a:00.1: initializing...
[ 1.258681] pciback 0000:0a:00.1: initializing config
[ 1.258681] pciback 0000:0a:00.1: initializing virtual configuration space
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x00
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x02
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x04
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x3c
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x3d
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x0c
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x0d
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x0f
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x10
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x14
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x18
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x1c
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x20
[ 1.258681] pciback 0000:0a:00.1: added config field at offset 0x24
[ 1.272319] pciback 0000:0a:00.1: added config field at offset 0x30
[ 1.272358] pciback 0000:0a:00.1: Found capability 0x1 at 0x78
[ 1.272363] pciback 0000:0a:00.1: added config field at offset 0x78
[ 1.272367] pciback 0000:0a:00.1: added config field at offset 0x7a
[ 1.272373] pciback 0000:0a:00.1: added config field at offset 0x7c
[ 1.272376] pciback 0000:0a:00.1: added config field at offset 0x7e
[ 1.272379] pciback 0000:0a:00.1: added config field at offset 0x7f
[ 1.272382] pciback 0000:0a:00.1: enabling device
[ 1.272396] xen: registering gsi 28 triggering 0 polarity 1
[ 1.272402] alloc irq_desc for 28 on node 0
[ 1.272405] alloc kstat_irqs on node 0
[ 1.272409] xen: --> irq=28
[ 1.272425] pciback 0000:0a:00.1: PCI INT A -> GSI 28 (level, low) -> IRQ 28
[ 1.273312] pciback 0000:0a:00.1: reset device
[ 1.273312] pciback 0000:0a:00.1: PCI INT A disabled
[ 1.273312] pciback 0000:0a:00.0: initializing...
[ 1.273312] pciback 0000:0a:00.0: initializing config
[ 1.273312] pciback 0000:0a:00.0: initializing virtual configuration space
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x00
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x02
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x04
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x3c
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x3d
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x0c
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x0d
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x0f
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x10
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x14
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x18
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x1c
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x20
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x24
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x30
[ 1.273312] pciback 0000:0a:00.0: Found capability 0x1 at 0x78
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x78
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x7a
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x7c
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x7e
[ 1.273312] pciback 0000:0a:00.0: added config field at offset 0x7f
[ 1.273312] pciback 0000:0a:00.0: enabling device
[ 1.273312] xen: registering gsi 28 triggering 0 polarity 1
[ 1.273312] xen_allocate_pirq: returning irq 28 for gsi 28
[ 1.273312] xen: --> irq=28
[ 1.286486] Already setup the GSI :28
[ 1.287481] pciback 0000:0a:00.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
[ 1.287481] pciback 0000:0a:00.0: reset device
[ 1.287481] pciback 0000:0a:00.0: PCI INT A disabled
[ 1.304136] blktap_device_init: blktap device major 253
[ 1.305122] blktap_ring_init: blktap ring major: 251
[ 1.320120] registering netback
[ 1.331860] alloc irq_desc for 1745 on node 0
[ 1.331863] alloc kstat_irqs on node 0
[ 1.332696] Non-volatile memory driver v1.3
[ 1.333687] Linux agpgart interface v0.103
[ 1.343089] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.352654] brd: module loaded
[ 1.429624] loop: module loaded
[ 1.435009] input: Macintosh mouse button emulation as /devices/virtual/input/input2
[ 1.440826] ahci 0000:00:11.0: version 3.0
[ 1.440844] xen: registering gsi 19 triggering 0 polarity 1
[ 1.440854] alloc irq_desc for 19 on node 0
[ 1.440857] alloc kstat_irqs on node 0
[ 1.440862] xen: --> irq=19
[ 1.440890] ahci 0000:00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 1.441766] alloc irq_desc for 1744 on node 0
[ 1.441766] alloc kstat_irqs on node 0
[ 1.446357] ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
[ 1.447202] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
[ 1.457885] scsi0 : ahci
[ 1.463538] scsi1 : ahci
[ 1.469043] scsi2 : ahci
[ 1.474503] scsi3 : ahci
[ 1.479941] scsi4 : ahci
[ 1.485208] scsi5 : ahci
[ 1.490349] ata1: SATA max UDMA/133 abar m1024@0xf98ff000 port 0xf98ff100 irq 1744
[ 1.491312] ata2: SATA max UDMA/133 abar m1024@0xf98ff000 port 0xf98ff180 irq 1744
[ 1.500143] ata3: SATA max UDMA/133 abar m1024@0xf98ff000 port 0xf98ff200 irq 1744
[ 1.500143] ata4: SATA max UDMA/133 abar m1024@0xf98ff000 port 0xf98ff280 irq 1744
[ 1.500143] ata5: SATA max UDMA/133 abar m1024@0xf98ff000 port 0xf98ff300 irq 1744
[ 1.500143] ata6: SATA max UDMA/133 abar m1024@0xf98ff000 port 0xf98ff380 irq 1744
[ 1.501556] Intel(R) PRO/1000 Network Driver - version 7.3.21-k5-NAPI
[ 1.501558] Copyright (c) 1999-2006 Intel Corporation.
[ 1.501670] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[ 1.501709] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 1.501828] Intel(R) Gigabit Ethernet Network Driver - version 1.3.16-k2
[ 1.501830] Copyright (c) 2007-2009 Intel Corporation.
[ 1.501923] Intel(R) Virtual Function Network Driver - version 1.0.0-k0
[ 1.501925] Copyright (c) 2009 Intel Corporation.
[ 1.502210] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 1.502212] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.502600] sky2 driver version 1.25
[ 1.502909] tun: Universal TUN/TAP device driver, 1.6
[ 1.502911] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 1.503018] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.503038] xen: registering gsi 46 triggering 0 polarity 1
[ 1.503046] alloc irq_desc for 46 on node 0
[ 1.503048] alloc kstat_irqs on node 0
[ 1.503052] xen: --> irq=46
[ 1.503112] r8169 0000:09:00.0: PCI INT A -> GSI 46 (level, low) -> IRQ 46
[ 1.503121] r8169 0000:09:00.0: enabling Mem-Wr-Inval
[ 1.503184] r8169 0000:09:00.0: setting latency timer to 64
[ 1.503270] alloc irq_desc for 1743 on node 0
[ 1.503273] alloc kstat_irqs on node 0
[ 1.503515] eth0: RTL8168d/8111d at 0xffffc90000070000, 40:61:86:f4:67:d9, XID 081000c0 IRQ 1743
[ 1.554829] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.554846] xen: registering gsi 51 triggering 0 polarity 1
[ 1.554850] alloc irq_desc for 51 on node 0
[ 1.554852] alloc kstat_irqs on node 0
[ 1.554855] xen: --> irq=51
[ 1.554917] r8169 0000:08:00.0: PCI INT A -> GSI 51 (level, low) -> IRQ 51
[ 1.554925] r8169 0000:08:00.0: enabling Mem-Wr-Inval
[ 1.554963] r8169 0000:08:00.0: setting latency timer to 64
[ 1.555028] alloc irq_desc for 1742 on node 0
[ 1.555030] alloc kstat_irqs on node 0
[ 1.555278] eth1: RTL8168d/8111d at 0xffffc90000074000, 40:61:86:f4:67:d8, XID 081000c0 IRQ 1742
[ 1.614971] console [netcon0] enabled
[ 1.615955] netconsole: network logging started
[ 1.626268] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.631856] xen: registering gsi 17 triggering 0 polarity 1
[ 1.631863] alloc irq_desc for 17 on node 0
[ 1.631866] alloc kstat_irqs on node 0
[ 1.631870] xen: --> irq=17
[ 1.631922] ehci_hcd 0000:00:12.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 1.632834] ehci_hcd 0000:00:12.2: enabling bus mastering
[ 1.632834] ehci_hcd 0000:00:12.2: EHCI Host Controller
[ 1.643528] ehci_hcd 0000:00:12.2: new USB bus registered, assigned bus number 1
[ 1.644511] ehci_hcd 0000:00:12.2: debug port 1
[ 1.644511] ehci_hcd 0000:00:12.2: enabling Mem-Wr-Inval
[ 1.644511] ehci_hcd 0000:00:12.2: irq 17, io mem 0xf98ff400
[ 1.666216] ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00
[ 1.671809] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.672779] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.672779] usb usb1: Product: EHCI Host Controller
[ 1.672779] usb usb1: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ehci_hcd
[ 1.672779] usb usb1: SerialNumber: 0000:00:12.2
[ 1.700419] usb usb1: configuration #1 chosen from 1 choice
[ 1.706244] hub 1-0:1.0: USB hub found
[ 1.711925] hub 1-0:1.0: 5 ports detected
[ 1.717613] xen: registering gsi 17 triggering 0 polarity 1
[ 1.717617] xen_allocate_pirq: returning irq 17 for gsi 17
[ 1.718507] xen: --> irq=17
[ 1.723294] Already setup the GSI :17
[ 1.724289] ehci_hcd 0000:00:13.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 1.724289] ehci_hcd 0000:00:13.2: enabling bus mastering
[ 1.724289] ehci_hcd 0000:00:13.2: EHCI Host Controller
[ 1.740462] ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 2
[ 1.746275] ehci_hcd 0000:00:13.2: debug port 1
[ 1.747244] ehci_hcd 0000:00:13.2: enabling Mem-Wr-Inval
[ 1.747244] ehci_hcd 0000:00:13.2: irq 17, io mem 0xf98ff800
[ 1.763226] ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00
[ 1.768765] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.769737] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.769737] usb usb2: Product: EHCI Host Controller
[ 1.769737] usb usb2: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ehci_hcd
[ 1.769737] usb usb2: SerialNumber: 0000:00:13.2
[ 1.796636] usb usb2: configuration #1 chosen from 1 choice
[ 1.802538] hub 2-0:1.0: USB hub found
[ 1.805158] ata4: SATA link down (SStatus 0 SControl 300)
[ 1.805198] ata6: SATA link down (SStatus 0 SControl 300)
[ 1.805208] ata5: SATA link down (SStatus 0 SControl 300)
[ 1.805235] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.805440] ata3: SATA link down (SStatus 0 SControl 300)
[ 1.837352] hub 2-0:1.0: 5 ports detected
[ 1.843298] xen: registering gsi 17 triggering 0 polarity 1
[ 1.843306] xen_allocate_pirq: returning irq 17 for gsi 17
[ 1.844205] xen: --> irq=17
[ 1.849239] Already setup the GSI :17
[ 1.850235] ehci_hcd 0000:00:16.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 1.850235] ehci_hcd 0000:00:16.2: enabling bus mastering
[ 1.850235] ehci_hcd 0000:00:16.2: EHCI Host Controller
[ 1.867053] ehci_hcd 0000:00:16.2: new USB bus registered, assigned bus number 3
[ 1.868036] ehci_hcd 0000:00:16.2: debug port 1
[ 1.868036] ehci_hcd 0000:00:16.2: enabling Mem-Wr-Inval
[ 1.868036] ehci_hcd 0000:00:16.2: irq 17, io mem 0xf98ffc00
[ 1.890204] ehci_hcd 0000:00:16.2: USB 2.0 started, EHCI 1.00
[ 1.895920] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.900149] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.900149] usb usb3: Product: EHCI Host Controller
[ 1.900149] usb usb3: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ehci_hcd
[ 1.900149] usb usb3: SerialNumber: 0000:00:16.2
[ 1.901836] usb usb3: configuration #1 chosen from 1 choice
[ 1.901922] hub 3-0:1.0: USB hub found
[ 1.901959] hub 3-0:1.0: 4 ports detected
[ 1.902075] xen: registering gsi 46 triggering 0 polarity 1
[ 1.902077] xen_allocate_pirq: returning irq 46 for gsi 46
[ 1.902078] xen: --> irq=46
[ 1.902087] Already setup the GSI :46
[ 1.902090] ehci_hcd 0000:07:01.2: PCI INT C -> GSI 46 (level, low) -> IRQ 46
[ 1.902111] ehci_hcd 0000:07:01.2: EHCI Host Controller
[ 1.902343] ehci_hcd 0000:07:01.2: new USB bus registered, assigned bus number 4
[ 1.923173] ehci_hcd 0000:07:01.2: irq 46, io mem 0xf9cffc00
[ 1.929127] ehci_hcd 0000:07:01.2: USB 2.0 started, EHCI 1.00
[ 1.929162] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.929165] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.929167] usb usb4: Product: EHCI Host Controller
[ 1.929169] usb usb4: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ehci_hcd
[ 1.929170] usb usb4: SerialNumber: 0000:07:01.2
[ 1.929293] usb usb4: configuration #1 chosen from 1 choice
[ 1.929411] hub 4-0:1.0: USB hub found
[ 1.929438] hub 4-0:1.0: 5 ports detected
[ 1.929825] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.929856] xen: registering gsi 18 triggering 0 polarity 1
[ 1.929862] alloc irq_desc for 18 on node 0
[ 1.929864] alloc kstat_irqs on node 0
[ 1.929868] xen: --> irq=18
[ 1.929936] ohci_hcd 0000:00:12.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 1.929959] ohci_hcd 0000:00:12.0: OHCI Host Controller
[ 1.930084] ohci_hcd 0000:00:12.0: new USB bus registered, assigned bus number 5
[ 1.930150] ohci_hcd 0000:00:12.0: irq 18, io mem 0xf98fb000
[ 1.958361] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.959779] ata1.00: ATA-8: Hitachi HDS722020ALA330, JKAOA20N, max UDMA/133
[ 1.959782] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 1.961337] ata1.00: configured for UDMA/133
[ 1.972415] scsi 0:0:0:0: Direct-Access ATA Hitachi HDS72202 JKAO PQ: 0 ANSI: 5
[ 1.973098] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 1.973186] sd 0:0:0:0: [sda] Write Protect is off
[ 1.973189] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.973230] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1.973521] sda:
[ 1.974165] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.986227] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.986232] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.986234] usb usb5: Product: OHCI Host Controller
[ 1.986236] usb usb5: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ohci_hcd
[ 1.986238] usb usb5: SerialNumber: 0000:00:12.0
[ 1.986318] sda1 sda2
[ 1.986470] usb usb5: configuration #1 chosen from 1 choice
[ 2.146086] hub 5-0:1.0: USB hub found
[ 2.146693] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.157783] hub 5-0:1.0: 5 ports detected
[ 2.163816] xen: registering gsi 18 triggering 0 polarity 1
[ 2.163819] xen_allocate_pirq: returning irq 18 for gsi 18
[ 2.164732] xen: --> irq=18
[ 2.169844] Already setup the GSI :18
[ 2.170840] ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 2.170840] ohci_hcd 0000:00:13.0: OHCI Host Controller
[ 2.188387] ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 6
[ 2.189367] ohci_hcd 0000:00:13.0: irq 18, io mem 0xf98fc000
[ 2.255361] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.256059] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.256059] usb usb6: Product: OHCI Host Controller
[ 2.256059] usb usb6: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ohci_hcd
[ 2.256059] usb usb6: SerialNumber: 0000:00:13.0
[ 2.291939] usb usb6: configuration #1 chosen from 1 choice
[ 2.298448] hub 6-0:1.0: USB hub found
[ 2.304675] hub 6-0:1.0: 5 ports detected
[ 2.310816] xen: registering gsi 18 triggering 0 polarity 1
[ 2.310819] xen_allocate_pirq: returning irq 18 for gsi 18
[ 2.311730] xen: --> irq=18
[ 2.316857] Already setup the GSI :18
[ 2.317852] ohci_hcd 0000:00:14.5: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 2.317852] ohci_hcd 0000:00:14.5: OHCI Host Controller
[ 2.335422] ohci_hcd 0000:00:14.5: new USB bus registered, assigned bus number 7
[ 2.336407] ohci_hcd 0000:00:14.5: irq 18, io mem 0xf98fd000
[ 2.402367] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.403059] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.403059] usb usb7: Product: OHCI Host Controller
[ 2.403059] usb usb7: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ohci_hcd
[ 2.403059] usb usb7: SerialNumber: 0000:00:14.5
[ 2.437582] usb usb7: configuration #1 chosen from 1 choice
[ 2.444053] hub 7-0:1.0: USB hub found
[ 2.446200] usb 4-5: new high speed USB device using ehci_hcd and address 4
[ 2.456677] hub 7-0:1.0: 2 ports detected
[ 2.463048] xen: registering gsi 18 triggering 0 polarity 1
[ 2.463051] xen_allocate_pirq: returning irq 18 for gsi 18
[ 2.463917] xen: --> irq=18
[ 2.469240] Already setup the GSI :18
[ 2.470236] ohci_hcd 0000:00:16.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 2.470236] ohci_hcd 0000:00:16.0: OHCI Host Controller
[ 2.488208] ohci_hcd 0000:00:16.0: new USB bus registered, assigned bus number 8
[ 2.489193] ohci_hcd 0000:00:16.0: irq 18, io mem 0xf98fe000
[ 2.555361] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.556059] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.556059] usb usb8: Product: OHCI Host Controller
[ 2.556059] usb usb8: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ohci_hcd
[ 2.556059] usb usb8: SerialNumber: 0000:00:16.0
[ 2.592885] usb usb8: configuration #1 chosen from 1 choice
[ 2.599471] hub 8-0:1.0: USB hub found
[ 2.605768] hub 8-0:1.0: 4 ports detected
[ 2.612081] xen: registering gsi 44 triggering 0 polarity 1
[ 2.612087] alloc irq_desc for 44 on node 0
[ 2.612090] alloc kstat_irqs on node 0
[ 2.612094] xen: --> irq=44
[ 2.612148] ohci_hcd 0000:07:01.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44
[ 2.613058] ohci_hcd 0000:07:01.0: OHCI Host Controller
[ 2.625074] ohci_hcd 0000:07:01.0: new USB bus registered, assigned bus number 9
[ 2.631370] ohci_hcd 0000:07:01.0: irq 44, io mem 0xf9cfd000
[ 2.639469] usb 4-5: New USB device found, idVendor=17e9, idProduct=019b
[ 2.640428] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.640428] usb 4-5: Product: USB to DVI Adapter
[ 2.640428] usb 4-5: Manufacturer: DisplayLink
[ 2.640428] usb 4-5: SerialNumber: 019B-001912
[ 2.669792] usb 4-5: configuration #1 chosen from 1 choice
[ 2.717262] usb usb9: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.718215] usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.718215] usb usb9: Product: OHCI Host Controller
[ 2.718215] usb usb9: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ohci_hcd
[ 2.718215] usb usb9: SerialNumber: 0000:07:01.0
[ 2.747428] usb usb9: configuration #1 chosen from 1 choice
[ 2.753610] hub 9-0:1.0: USB hub found
[ 2.759617] hub 9-0:1.0: 3 ports detected
[ 2.765620] xen: registering gsi 45 triggering 0 polarity 1
[ 2.765627] alloc irq_desc for 45 on node 0
[ 2.765630] alloc kstat_irqs on node 0
[ 2.765634] xen: --> irq=45
[ 2.765668] ohci_hcd 0000:07:01.1: PCI INT B -> GSI 45 (level, low) -> IRQ 45
[ 2.766518] ohci_hcd 0000:07:01.1: OHCI Host Controller
[ 2.777818] ohci_hcd 0000:07:01.1: new USB bus registered, assigned bus number 10
[ 2.778808] ohci_hcd 0000:07:01.1: irq 45, io mem 0xf9cfe000
[ 2.870230] usb usb10: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.871126] usb usb10: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.871126] usb usb10: Product: OHCI Host Controller
[ 2.871126] usb usb10: Manufacturer: Linux 2.6.32.26-xen-next-2.6.32.x-20101210 ohci_hcd
[ 2.871126] usb usb10: SerialNumber: 0000:07:01.1
[ 2.900404] usb usb10: configuration #1 chosen from 1 choice
[ 2.906569] hub 10-0:1.0: USB hub found
[ 2.912604] hub 10-0:1.0: 2 ports detected
[ 2.918763] uhci_hcd: USB Universal Host Controller Interface driver
[ 2.925334] usbcore: registered new interface driver usblp
[ 2.926325] Initializing USB Mass Storage driver...
[ 2.937481] usbcore: registered new interface driver usb-storage
[ 2.938470] USB Mass Storage support registered.
[ 2.949717] usbcore: registered new interface driver libusual
[ 2.956164] PNP: No PS/2 controller found. Probing ports directly.
[ 2.962852] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 2.963700] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 2.975311] mice: PS/2 mouse device common for all mice
[ 2.982263] rtc_cmos 00:04: RTC can wake from S4
[ 2.988566] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
[ 2.994622] rtc0: alarms up to one month, y3k, 114 bytes nvram
[ 3.002643] applesmc: supported laptop not found!
[ 3.003635] applesmc: driver init failed (ret=-19)!
[ 3.014845] f71805f: Unsupported Fintek device, skipping
[ 3.020862] f71882fg: Unsupported Fintek device
[ 3.027233] hdaps: supported laptop not found!
[ 3.028222] hdaps: driver init failed (ret=-19)!
[ 3.039701] lis3lv02d driver loaded.
[ 3.046657] pc87360: PC8736x not detected, module not inserted.
[ 3.053400] wdt: Xen WatchDog Timer Driver v0.01
[ 3.059483] wdt: initialized (timeout=60s, nowayout=0)
[ 3.066078] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[ 3.072415] device-mapper: multipath: version 1.1.0 loaded
[ 3.073404] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 3.084865] cpuidle: using governor ladder
[ 3.085845] cpuidle: using governor menu
[ 3.099065] usbcore: registered new interface driver hiddev
[ 3.105049] usbcore: registered new interface driver usbhid
[ 3.106043] usbhid: v2.6:USB HID core driver
[ 3.116510] Netfilter messages via NETLINK v0.30.
[ 3.122277] nf_conntrack version 0.5.0 (6144 buckets, 24576 max)
[ 3.128281] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
[ 3.129264] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
[ 3.129264] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 3.145805] ctnetlink v0.93: registering with nfnetlink.
[ 3.151886] xt_time: kernel timezone is -0000
[ 3.157838] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 3.163803] TCP cubic registered
[ 3.164777] Initializing XFRM netlink socket
[ 3.175836] NET: Registered protocol family 10
[ 3.181996] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 3.187769] IPv6 over IPv4 tunneling driver
[ 3.193709] NET: Registered protocol family 17
[ 3.199529] Bridge firewalling registered
[ 3.200503] Ebtables v2.0 registered
[ 3.211076] ebt_ulog: out of memory trying to call netlink_kernel_create
[ 3.213511] usb 9-2: new full speed USB device using ohci_hcd and address 2
[ 3.223154] powernow-k8: Found 1 AMD Phenom(tm) II X6 1090T Processor processors (6 cpu cores) (version 2.20.00)
[ 3.224059] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found.
[ 3.224059] [Firmware Bug]: powernow-k8: Try again with latest BIOS.
[ 3.243776] Freeing unused kernel memory: 860k freed
[ 3.368260] usb 9-2: New USB device found, idVendor=067b, idProduct=2303
[ 3.368274] usb 9-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.368285] usb 9-2: Product: USB-Serial Controller
[ 3.368293] usb 9-2: Manufacturer: Prolific Technology Inc.
[ 3.368915] usb 9-2: configuration #1 chosen from 1 choice
[ 3.589107] usb 10-2: new full speed USB device using ohci_hcd and address 2
[ 3.744205] usb 10-2: New USB device found, idVendor=1130, idProduct=f211
[ 3.750474] usb 10-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 3.750474] usb 10-2: Product: USB AUDIO
[ 3.750819] usb 10-2: configuration #1 chosen from 1 choice
[ 3.759470] input: USB AUDIO as /devices/pci0000:00/0000:00:0a.0/0000:06:00.0/0000:07:01.1/usb10/10-2/10-2:1.3/input/input3
[ 3.759627] generic-usb 0003:1130:F211.0001: input,hidraw0: USB HID v1.10 Device [USB AUDIO ] on usb-0000:07:01.1-2/input3
[ 3.766318] input: USB AUDIO as /devices/pci0000:00/0000:00:0a.0/0000:06:00.0/0000:07:01.1/usb10/10-2/10-2:1.4/input/input4
[ 3.766463] generic-usb 0003:1130:F211.0002: input,hidraw1: USB HID v1.10 Device [USB AUDIO ] on usb-0000:07:01.1-2/input4
[ 5.377985] kjournald starting. Commit interval 5 seconds
[ 5.378017] EXT3-fs: mounted filesystem with journal data mode.
[ 6.899156] udevd version 125 started
[ 7.755953] ata1.00: configured for UDMA/133
[ 7.756928] ata1: EH complete
[ 9.948749] ata1.00: configured for UDMA/133
[ 9.949722] ata1: EH complete
[ 11.277601] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
[ 11.298170] EXT3 FS on dm-0, internal journal
[ 13.741283] Adding 2097144k swap on /dev/mapper/serveerstertje-swap. Priority:-1 extents:1 across:2097144k
[ 14.869753] r8169: eth1: link up
[ 14.870753] r8169: eth1: link up
[ 15.033001] r8169: eth0: link up
[ 15.034014] r8169: eth0: link up
[ 37.088007] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=15526 PROTO=2
[ 39.905827] kjournald starting. Commit interval 5 seconds
[ 39.905888] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
[ 39.915957] EXT3 FS on sda1, internal journal
[ 39.915985] EXT3-fs: mounted filesystem with writeback data mode.
[ 40.431257] kjournald starting. Commit interval 5 seconds
[ 40.439387] EXT3 FS on dm-2, internal journal
[ 40.439422] EXT3-fs: mounted filesystem with writeback data mode.
[ 40.957951] kjournald starting. Commit interval 5 seconds
[ 40.972167] EXT3 FS on dm-3, internal journal
[ 40.973080] EXT3-fs: mounted filesystem with writeback data mode.
[ 41.443538] kjournald starting. Commit interval 5 seconds
[ 41.454204] EXT3 FS on dm-4, internal journal
[ 41.454230] EXT3-fs: mounted filesystem with writeback data mode.
[ 41.833599] EXT4-fs (dm-5): mounted filesystem with ordered data mode
[ 162.127579] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=15925 PROTO=2
[ 164.840362] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.102 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=57034 PROTO=TCP SPT=80 DPT=54409 WINDOW=115 RES=0x00 ACK FIN URGP=0
[ 165.223719] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.142 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=27768 PROTO=TCP SPT=80 DPT=54419 WINDOW=109 RES=0x00 ACK FIN URGP=0
[ 165.262333] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.102 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=57035 PROTO=TCP SPT=80 DPT=54409 WINDOW=115 RES=0x00 ACK FIN URGP=0
[ 165.294697] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.148 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=1489 PROTO=TCP SPT=80 DPT=54420 WINDOW=107 RES=0x00 ACK FIN URGP=0
[ 165.645240] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.142 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=27769 PROTO=TCP SPT=80 DPT=54419 WINDOW=109 RES=0x00 ACK FIN URGP=0
[ 165.714715] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.148 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=1490 PROTO=TCP SPT=80 DPT=54420 WINDOW=107 RES=0x00 ACK FIN URGP=0
[ 166.106984] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.102 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=57036 PROTO=TCP SPT=80 DPT=54409 WINDOW=115 RES=0x00 ACK FIN URGP=0
[ 166.489661] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.142 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=27770 PROTO=TCP SPT=80 DPT=54419 WINDOW=109 RES=0x00 ACK FIN URGP=0
[ 166.556492] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.148 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=1491 PROTO=TCP SPT=80 DPT=54420 WINDOW=107 RES=0x00 ACK FIN URGP=0
[ 167.795969] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.102 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=57037 PROTO=TCP SPT=80 DPT=54409 WINDOW=115 RES=0x00 ACK FIN URGP=0
[ 171.173373] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.102 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=57038 PROTO=TCP SPT=80 DPT=54409 WINDOW=115 RES=0x00 ACK FIN URGP=0
[ 177.928787] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.102 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=57039 PROTO=TCP SPT=80 DPT=54409 WINDOW=115 RES=0x00 ACK FIN URGP=0
[ 187.933869] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.102 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=57030 PROTO=TCP SPT=80 DPT=54409 WINDOW=115 RES=0x00 ACK FIN URGP=0
[ 197.938953] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.102 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=57030 PROTO=TCP SPT=80 DPT=54409 WINDOW=115 RES=0x00 ACK FIN URGP=0
[ 198.321557] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.142 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=50636 PROTO=TCP SPT=80 DPT=54419 WINDOW=109 RES=0x00 ACK FIN URGP=0
[ 207.943748] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.102 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=57030 PROTO=TCP SPT=80 DPT=54409 WINDOW=115 RES=0x00 ACK FIN URGP=0
[ 208.326638] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=74.125.79.142 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=50636 PROTO=TCP SPT=80 DPT=54419 WINDOW=109 RES=0x00 ACK FIN URGP=0
[ 228.138365] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=91.211.73.73 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=38831 DF PROTO=TCP SPT=80 DPT=54428 WINDOW=8190 RES=0x00 ACK FIN URGP=0
[ 228.146298] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=91.211.73.73 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=41903 DF PROTO=TCP SPT=80 DPT=54423 WINDOW=8190 RES=0x00 ACK FIN URGP=0
[ 228.146298] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=91.211.73.73 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=39855 DF PROTO=TCP SPT=80 DPT=54426 WINDOW=8190 RES=0x00 ACK FIN URGP=0
[ 231.159835] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=91.211.73.73 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=52701 DF PROTO=TCP SPT=80 DPT=54424 WINDOW=8190 RES=0x00 ACK FIN URGP=0
[ 243.186410] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=91.211.73.74 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=30330 DF PROTO=TCP SPT=80 DPT=54425 WINDOW=8190 RES=0x00 ACK FIN URGP=0
[ 243.223509] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=91.211.73.73 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=30074 DF PROTO=TCP SPT=80 DPT=54427 WINDOW=8190 RES=0x00 ACK FIN URGP=0
[ 256.951716] kjournald starting. Commit interval 5 seconds
[ 256.962800] EXT3 FS on dm-6, internal journal
[ 256.962827] EXT3-fs: mounted filesystem with writeback data mode.
[ 257.490321] kjournald starting. Commit interval 5 seconds
[ 257.496341] EXT3 FS on dm-9, internal journal
[ 257.496368] EXT3-fs: mounted filesystem with writeback data mode.
[ 257.994376] kjournald starting. Commit interval 5 seconds
[ 258.006865] EXT3 FS on dm-7, internal journal
[ 258.006892] EXT3-fs: mounted filesystem with writeback data mode.
[ 261.217352] alloc irq_desc for 1741 on node 0
[ 261.217357] alloc kstat_irqs on node 0
[ 261.217461] alloc irq_desc for 1740 on node 0
[ 261.217467] alloc kstat_irqs on node 0
[ 261.217957] XENBUS: Unable to read cpu state
[ 261.235595] XENBUS: Unable to read cpu state
[ 261.235763] XENBUS: Unable to read cpu state
[ 261.235909] XENBUS: Unable to read cpu state
[ 261.236051] XENBUS: Unable to read cpu state
[ 261.236226] XENBUS: Unable to read cpu state
[ 269.445740] alloc irq_desc for 1739 on node 0
[ 269.445746] alloc kstat_irqs on node 0
[ 269.998998] alloc irq_desc for 1738 on node 0
[ 269.999005] alloc kstat_irqs on node 0
[ 270.366363] device vif1.0 entered promiscuous mode
[ 270.386285] xen_bridge: port 1(vif1.0) entering learning state
[ 270.864967] xen_bridge: port 1(vif1.0) entering disabled state
[ 270.887609] xen_bridge: port 1(vif1.0) entering learning state
[ 272.461359] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[ 272.475643] alloc irq_desc for 1737 on node 0
[ 272.475647] alloc kstat_irqs on node 0
[ 272.508201] blkback: ring-ref 2046, event-channel 5, protocol 1 (x86_64-abi)
[ 272.522017] alloc irq_desc for 1736 on node 0
[ 272.522020] alloc kstat_irqs on node 0
[ 278.724433] frontend_changed: backend/vbd/1/2049: prepare for reconnect
[ 278.785921] frontend_changed: backend/vbd/1/2050: prepare for reconnect
[ 279.150315] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 279.205842] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 279.282006] alloc irq_desc for 1735 on node 0
[ 279.282012] alloc kstat_irqs on node 0
[ 285.901261] xen_bridge: port 1(vif1.0) entering forwarding state
[ 287.197902] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=16330 PROTO=2
[ 293.947087] alloc irq_desc for 1734 on node 0
[ 293.947092] alloc kstat_irqs on node 0
[ 294.797559] device vif2.0 entered promiscuous mode
[ 294.815295] xen_bridge: port 2(vif2.0) entering learning state
[ 294.848387] alloc irq_desc for 1733 on node 0
[ 294.848393] alloc kstat_irqs on node 0
[ 294.977546] xen_bridge: port 2(vif2.0) entering disabled state
[ 294.996657] xen_bridge: port 2(vif2.0) entering learning state
[ 297.531793] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[ 297.543696] alloc irq_desc for 1732 on node 0
[ 297.543700] alloc kstat_irqs on node 0
[ 297.582958] blkback: ring-ref 2046, event-channel 5, protocol 1 (x86_64-abi)
[ 297.594443] alloc irq_desc for 1731 on node 0
[ 297.594446] alloc kstat_irqs on node 0
[ 303.659709] frontend_changed: backend/vbd/2/2049: prepare for reconnect
[ 303.808914] frontend_changed: backend/vbd/2/2050: prepare for reconnect
[ 304.182818] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 304.245761] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 304.330347] alloc irq_desc for 1730 on node 0
[ 304.330354] alloc kstat_irqs on node 0
[ 310.008095] xen_bridge: port 2(vif2.0) entering forwarding state
[ 318.833637] alloc irq_desc for 1729 on node 0
[ 318.833642] alloc kstat_irqs on node 0
[ 319.873340] device vif3.0 entered promiscuous mode
[ 319.887591] xen_bridge: port 3(vif3.0) entering learning state
[ 320.022579] alloc irq_desc for 1728 on node 0
[ 320.022585] alloc kstat_irqs on node 0
[ 320.049511] xen_bridge: port 3(vif3.0) entering disabled state
[ 320.169254] xen_bridge: port 3(vif3.0) entering learning state
[ 321.690560] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[ 321.699759] alloc irq_desc for 1727 on node 0
[ 321.699767] alloc kstat_irqs on node 0
[ 322.013993] blkback: ring-ref 2046, event-channel 5, protocol 1 (x86_64-abi)
[ 322.022754] alloc irq_desc for 1726 on node 0
[ 322.022759] alloc kstat_irqs on node 0
[ 327.914321] frontend_changed: backend/vbd/3/2049: prepare for reconnect
[ 327.995616] frontend_changed: backend/vbd/3/2050: prepare for reconnect
[ 328.291415] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 328.355551] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 328.431582] alloc irq_desc for 1725 on node 0
[ 328.431586] alloc kstat_irqs on node 0
[ 335.178249] xen_bridge: port 3(vif3.0) entering forwarding state
[ 343.602825] alloc irq_desc for 1724 on node 0
[ 343.602830] alloc kstat_irqs on node 0
[ 344.735771] device vif4.0 entered promiscuous mode
[ 344.747846] xen_bridge: port 4(vif4.0) entering learning state
[ 344.785400] alloc irq_desc for 1723 on node 0
[ 344.785405] alloc kstat_irqs on node 0
[ 345.064568] xen_bridge: port 4(vif4.0) entering disabled state
[ 345.080247] xen_bridge: port 4(vif4.0) entering learning state
[ 346.691340] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[ 346.698582] alloc irq_desc for 1722 on node 0
[ 346.698585] alloc kstat_irqs on node 0
[ 346.740993] blkback: ring-ref 2046, event-channel 5, protocol 1 (x86_64-abi)
[ 346.748122] alloc irq_desc for 1721 on node 0
[ 346.748127] alloc kstat_irqs on node 0
[ 352.819113] frontend_changed: backend/vbd/4/51713: prepare for reconnect
[ 352.901416] frontend_changed: backend/vbd/4/51714: prepare for reconnect
[ 353.261941] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 353.310050] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 353.424590] alloc irq_desc for 1720 on node 0
[ 353.424595] alloc kstat_irqs on node 0
[ 360.080121] xen_bridge: port 4(vif4.0) entering forwarding state
[ 368.958288] alloc irq_desc for 1719 on node 0
[ 368.958296] alloc kstat_irqs on node 0
[ 370.186184] device vif5.0 entered promiscuous mode
[ 370.196601] xen_bridge: port 5(vif5.0) entering learning state
[ 370.539810] xen_bridge: port 5(vif5.0) entering disabled state
[ 370.553883] xen_bridge: port 5(vif5.0) entering learning state
[ 370.560262] alloc irq_desc for 1718 on node 0
[ 370.560268] alloc kstat_irqs on node 0
[ 377.290881] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[ 377.297234] alloc irq_desc for 1717 on node 0
[ 377.297239] alloc kstat_irqs on node 0
[ 377.622036] blkback: ring-ref 2046, event-channel 5, protocol 1 (x86_64-abi)
[ 377.628039] alloc irq_desc for 1716 on node 0
[ 377.628044] alloc kstat_irqs on node 0
[ 383.701293] frontend_changed: backend/vbd/5/2049: prepare for reconnect
[ 383.784482] frontend_changed: backend/vbd/5/2050: prepare for reconnect
[ 384.079855] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 384.114335] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 384.256910] alloc irq_desc for 1715 on node 0
[ 384.256917] alloc kstat_irqs on node 0
[ 385.560264] xen_bridge: port 5(vif5.0) entering forwarding state
[ 400.302699] alloc irq_desc for 1714 on node 0
[ 400.302704] alloc kstat_irqs on node 0
[ 401.528434] device vif6.0 entered promiscuous mode
[ 401.538242] xen_bridge: port 6(vif6.0) entering learning state
[ 401.687900] xen_bridge: port 6(vif6.0) entering disabled state
[ 401.693553] alloc irq_desc for 1713 on node 0
[ 401.693561] alloc kstat_irqs on node 0
[ 401.701941] xen_bridge: port 6(vif6.0) entering learning state
[ 403.675298] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[ 403.681396] alloc irq_desc for 1712 on node 0
[ 403.681400] alloc kstat_irqs on node 0
[ 403.734365] blkback: ring-ref 2046, event-channel 5, protocol 1 (x86_64-abi)
[ 403.740424] alloc irq_desc for 1711 on node 0
[ 403.740427] alloc kstat_irqs on node 0
[ 409.921232] frontend_changed: backend/vbd/6/51713: prepare for reconnect
[ 409.975355] frontend_changed: backend/vbd/6/51714: prepare for reconnect
[ 410.271517] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 410.319088] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 410.482753] alloc irq_desc for 1710 on node 0
[ 410.482757] alloc kstat_irqs on node 0
[ 411.086053] FW: BLOCKED low udp input: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=88.159.76.91 DST=88.159.76.249 LEN=69 TOS=0x00 PREC=0x00 TTL=122 ID=20848 PROTO=UDP SPT=1122 DPT=161 LEN=49
[ 412.264241] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=16695 PROTO=2
[ 413.329279] FW: BLOCKED low udp input: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=88.159.76.91 DST=88.159.76.249 LEN=69 TOS=0x00 PREC=0x00 TTL=122 ID=20870 PROTO=UDP SPT=1122 DPT=161 LEN=49
[ 416.707669] xen_bridge: port 6(vif6.0) entering forwarding state
[ 427.540310] alloc irq_desc for 1709 on node 0
[ 427.540315] alloc kstat_irqs on node 0
[ 428.644487] device vif7.0 entered promiscuous mode
[ 428.656533] xen_bridge: port 7(vif7.0) entering learning state
[ 428.727353] alloc irq_desc for 1708 on node 0
[ 428.727364] alloc kstat_irqs on node 0
[ 429.172472] xen_bridge: port 7(vif7.0) entering disabled state
[ 429.189743] xen_bridge: port 7(vif7.0) entering learning state
[ 430.737775] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[ 430.744766] alloc irq_desc for 1707 on node 0
[ 430.744769] alloc kstat_irqs on node 0
[ 430.793233] blkback: ring-ref 2046, event-channel 5, protocol 1 (x86_64-abi)
[ 430.800214] alloc irq_desc for 1706 on node 0
[ 430.800218] alloc kstat_irqs on node 0
[ 436.792215] frontend_changed: backend/vbd/7/2049: prepare for reconnect
[ 436.848062] frontend_changed: backend/vbd/7/2050: prepare for reconnect
[ 437.149556] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 437.206453] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 437.289976] alloc irq_desc for 1705 on node 0
[ 437.289983] alloc kstat_irqs on node 0
[ 444.196330] xen_bridge: port 7(vif7.0) entering forwarding state
[ 454.471197] alloc irq_desc for 1704 on node 0
[ 454.471202] alloc kstat_irqs on node 0
[ 455.948155] device vif8.0 entered promiscuous mode
[ 455.959190] xen_bridge: port 8(vif8.0) entering learning state
[ 456.132460] xen_bridge: port 8(vif8.0) entering disabled state
[ 456.146102] xen_bridge: port 8(vif8.0) entering learning state
[ 456.194840] alloc irq_desc for 1703 on node 0
[ 456.194846] alloc kstat_irqs on node 0
[ 458.028505] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 458.035539] alloc irq_desc for 1702 on node 0
[ 458.035544] alloc kstat_irqs on node 0
[ 458.286687] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 458.293606] alloc irq_desc for 1701 on node 0
[ 458.293609] alloc kstat_irqs on node 0
[ 458.395094] alloc irq_desc for 1700 on node 0
[ 458.395098] alloc kstat_irqs on node 0
[ 471.152210] xen_bridge: port 8(vif8.0) entering forwarding state
[ 485.294474] alloc irq_desc for 1699 on node 0
[ 485.294479] alloc kstat_irqs on node 0
[ 486.730956] device vif9.0 entered promiscuous mode
[ 486.742614] xen_bridge: port 9(vif9.0) entering learning state
[ 486.906464] xen_bridge: port 9(vif9.0) entering disabled state
[ 486.921713] xen_bridge: port 9(vif9.0) entering learning state
[ 487.719807] pciback pci-9-0: allocated pdev @ 0xffff88002592e180
[ 487.829167] pciback pci-9-0: getting be setup
[ 487.832496] pciback pci-9-0: exporting dom 0 bus 4 slot 0 func 0
[ 487.842113] pciback 0000:04:00.0: registering for 9
[ 487.848536] pciback pci-9-0: exporting dom 0 bus 4 slot 0 func 1
[ 487.860361] pciback 0000:04:00.1: registering for 9
[ 487.869779] pciback pci-9-0: exporting dom 0 bus 4 slot 0 func 2
[ 487.875800] pciback 0000:04:00.2: registering for 9
[ 487.890954] pciback pci-9-0: exporting dom 0 bus 4 slot 0 func 3
[ 487.897071] pciback 0000:04:00.3: registering for 9
[ 487.917685] pciback pci-9-0: exporting dom 0 bus 4 slot 0 func 4
[ 487.923710] pciback 0000:04:00.4: registering for 9
[ 487.938695] pciback pci-9-0: exporting dom 0 bus 4 slot 0 func 5
[ 487.941930] pciback 0000:04:00.5: registering for 9
[ 487.951310] pciback pci-9-0: exporting dom 0 bus 4 slot 0 func 6
[ 487.957359] pciback 0000:04:00.6: registering for 9
[ 487.968209] pciback pci-9-0: exporting dom 0 bus 4 slot 0 func 7
[ 487.974374] pciback 0000:04:00.7: registering for 9
[ 487.986497] pciback pci-9-0: Publishing pci roots
[ 487.986668] pciback pci-9-0: writing root 0 at 0000:04
[ 488.008203] pciback pci-9-0: Publishing pci roots
[ 488.008557] pciback pci-9-0: Publishing pci roots
[ 488.008902] pciback pci-9-0: Publishing pci roots
[ 488.009407] pciback pci-9-0: Publishing pci roots
[ 488.015636] pciback pci-9-0: Publishing pci roots
[ 488.018953] pciback pci-9-0: Publishing pci roots
[ 488.025080] pciback pci-9-0: Publishing pci roots
[ 488.246307] pciback pci-9-0: fe state changed 1
[ 488.262351] alloc irq_desc for 1698 on node 0
[ 488.262357] alloc kstat_irqs on node 0
[ 492.287935] pciback pci-9-0: fe state changed 3
[ 492.288250] pciback pci-9-0: Reading frontend config
[ 492.288673] pciback pci-9-0: Attaching to frontend resources - gnt_ref=8 evtchn=9
[ 492.288772] alloc irq_desc for 1697 on node 0
[ 492.288779] alloc kstat_irqs on node 0
[ 492.288822] pciback pci-9-0: Attached!
[ 492.288826] pciback pci-9-0: Connecting...
[ 492.298254] pciback pci-9-0: Connected? 0
[ 492.368408] blkback: ring-ref 9, event-channel 10, protocol 1 (x86_64-abi)
[ 492.375451] alloc irq_desc for 1696 on node 0
[ 492.375456] alloc kstat_irqs on node 0
[ 492.657927] blkback: ring-ref 10, event-channel 11, protocol 1 (x86_64-abi)
[ 492.667266] alloc irq_desc for 1695 on node 0
[ 492.667298] alloc kstat_irqs on node 0
[ 492.728413] blkback: ring-ref 11, event-channel 12, protocol 1 (x86_64-abi)
[ 492.735345] alloc irq_desc for 1694 on node 0
[ 492.735351] alloc kstat_irqs on node 0
[ 492.736278] pciback 0000:04:00.1: enabling device (0000 -> 0002)
[ 492.739502] xen: registering gsi 40 triggering 0 polarity 1
[ 492.739502] xen_allocate_pirq: returning irq 40 for gsi 40
[ 492.749498] xen: --> irq=40
[ 492.750097] Already setup the GSI :40
[ 492.754000] pciback 0000:04:00.1: PCI INT A -> GSI 40 (level, low) -> IRQ 40
[ 492.754000] pciback 0000:04:00.1: pciback[0000:04:00.1]: #40 on disable-> enable
[ 492.757171] pciback 0000:04:00.1: pciback[0000:04:00.1]: #40 on enabled
[ 492.757465] pciback 0000:04:00.1: enabling bus mastering
[ 492.757481] pciback 0000:04:00.1: setting latency timer to 64
[ 492.779049] pciback 0000:04:00.1: enabling Mem-Wr-Inval
[ 492.785683] pciback 0000:04:00.3: enabling device (0000 -> 0002)
[ 492.786484] xen: registering gsi 41 triggering 0 polarity 1
[ 492.786484] xen_allocate_pirq: returning irq 41 for gsi 41
[ 492.786484] xen: --> irq=41
[ 492.799793] Already setup the GSI :41
[ 492.800731] pciback 0000:04:00.3: PCI INT B -> GSI 41 (level, low) -> IRQ 41
[ 492.800731] pciback 0000:04:00.3: pciback[0000:04:00.3]: #41 on disable-> enable
[ 492.806985] pciback 0000:04:00.3: pciback[0000:04:00.3]: #41 on enabled
[ 492.807294] pciback 0000:04:00.3: enabling bus mastering
[ 492.807306] pciback 0000:04:00.3: setting latency timer to 64
[ 492.827857] pciback pci-9-0: fe state changed 4
[ 492.828911] pciback 0000:04:00.3: enabling Mem-Wr-Inval
[ 492.835582] pciback 0000:04:00.5: enabling device (0000 -> 0002)
[ 492.836015] xen: registering gsi 42 triggering 0 polarity 1
[ 492.836015] xen_allocate_pirq: returning irq 42 for gsi 42
[ 492.836015] xen: --> irq=42
[ 492.849965] Already setup the GSI :42
[ 492.850922] pciback 0000:04:00.5: PCI INT C -> GSI 42 (level, low) -> IRQ 42
[ 492.850922] pciback 0000:04:00.5: pciback[0000:04:00.5]: #42 on disable-> enable
[ 492.857263] pciback 0000:04:00.5: pciback[0000:04:00.5]: #42 on enabled
[ 492.857388] pciback 0000:04:00.5: enabling bus mastering
[ 492.857398] pciback 0000:04:00.5: setting latency timer to 64
[ 492.877942] pciback 0000:04:00.5: enabling Mem-Wr-Inval
[ 492.884341] pciback 0000:04:00.7: enabling device (0000 -> 0002)
[ 492.885054] xen: registering gsi 43 triggering 0 polarity 1
[ 492.885054] xen_allocate_pirq: returning irq 43 for gsi 43
[ 492.885054] xen: --> irq=43
[ 492.898853] Already setup the GSI :43
[ 492.900938] pciback 0000:04:00.7: PCI INT D -> GSI 43 (level, low) -> IRQ 43
[ 492.900938] pciback 0000:04:00.7: pciback[0000:04:00.7]: #43 on disable-> enable
[ 492.906123] pciback 0000:04:00.7: pciback[0000:04:00.7]: #43 on enabled
[ 492.906265] pciback 0000:04:00.7: enabling bus mastering
[ 492.906277] pciback 0000:04:00.7: setting latency timer to 64
[ 492.926632] alloc irq_desc for 1693 on node 0
[ 492.926637] alloc kstat_irqs on node 0
[ 492.926954] pciback 0000:04:00.7: enabling Mem-Wr-Inval
[ 492.933494] pciback 0000:04:00.0: enabling device (0000 -> 0002)
[ 492.934056] xen: registering gsi 40 triggering 0 polarity 1
[ 492.934056] xen_allocate_pirq: returning irq 40 for gsi 40
[ 492.934056] xen: --> irq=40
[ 492.948009] Already setup the GSI :40
[ 492.948930] pciback 0000:04:00.0: PCI INT A -> GSI 40 (level, low) -> IRQ 40
[ 492.948930] pciback 0000:04:00.0: pciback[0000:04:00.0]: #40 on disable-> enable
[ 492.955262] pciback 0000:04:00.0: pciback[0000:04:00.0]: #40 on enabled
[ 492.957959] pciback 0000:04:00.0: enabling bus mastering
[ 492.957968] pciback 0000:04:00.0: setting latency timer to 64
[ 493.015279] pciback 0000:04:00.2: enabling device (0000 -> 0002)
[ 493.016203] xen: registering gsi 41 triggering 0 polarity 1
[ 493.016203] xen_allocate_pirq: returning irq 41 for gsi 41
[ 493.016203] xen: --> irq=41
[ 493.034253] Already setup the GSI :41
[ 493.035167] pciback 0000:04:00.2: PCI INT B -> GSI 41 (level, low) -> IRQ 41
[ 493.035167] pciback 0000:04:00.2: pciback[0000:04:00.2]: #41 on disable-> enable
[ 493.035167] pciback 0000:04:00.2: pciback[0000:04:00.2]: #41 on enabled
[ 493.041950] pciback 0000:04:00.2: enabling bus mastering
[ 493.041958] pciback 0000:04:00.2: setting latency timer to 64
[ 493.099217] pciback 0000:04:00.4: enabling device (0000 -> 0002)
[ 493.100068] xen: registering gsi 42 triggering 0 polarity 1
[ 493.100068] xen_allocate_pirq: returning irq 42 for gsi 42
[ 493.100068] xen: --> irq=42
[ 493.118796] Already setup the GSI :42
[ 493.125233] pciback 0000:04:00.4: PCI INT C -> GSI 42 (level, low) -> IRQ 42
[ 493.125233] pciback 0000:04:00.4: pciback[0000:04:00.4]: #42 on disable-> enable
[ 493.126284] pciback 0000:04:00.4: pciback[0000:04:00.4]: #42 on enabled
[ 493.134049] pciback 0000:04:00.4: enabling bus mastering
[ 493.134058] pciback 0000:04:00.4: setting latency timer to 64
[ 493.191037] pciback 0000:04:00.6: enabling device (0000 -> 0002)
[ 493.191961] xen: registering gsi 43 triggering 0 polarity 1
[ 493.191961] xen_allocate_pirq: returning irq 43 for gsi 43
[ 493.191961] xen: --> irq=43
[ 493.212487] Already setup the GSI :43
[ 493.220366] pciback 0000:04:00.6: PCI INT D -> GSI 43 (level, low) -> IRQ 43
[ 493.220366] pciback 0000:04:00.6: pciback[0000:04:00.6]: #43 on disable-> enable
[ 493.220953] pciback 0000:04:00.6: pciback[0000:04:00.6]: #43 on enabled
[ 493.221197] pciback 0000:04:00.6: enabling bus mastering
[ 493.221207] pciback 0000:04:00.6: setting latency timer to 64
[ 501.928238] xen_bridge: port 9(vif9.0) entering forwarding state
[ 519.074662] alloc irq_desc for 1692 on node 0
[ 519.074667] alloc kstat_irqs on node 0
[ 520.337643] device vif10.0 entered promiscuous mode
[ 520.349066] xen_bridge: port 10(vif10.0) entering learning state
[ 520.619708] alloc irq_desc for 1691 on node 0
[ 520.619713] alloc kstat_irqs on node 0
[ 520.625794] xen_bridge: port 10(vif10.0) entering disabled state
[ 520.640969] xen_bridge: port 10(vif10.0) entering learning state
[ 522.629613] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[ 522.635997] alloc irq_desc for 1690 on node 0
[ 522.636003] alloc kstat_irqs on node 0
[ 522.682722] blkback: ring-ref 2046, event-channel 5, protocol 1 (x86_64-abi)
[ 522.689033] alloc irq_desc for 1689 on node 0
[ 522.689040] alloc kstat_irqs on node 0
[ 528.841678] frontend_changed: backend/vbd/10/2049: prepare for reconnect
[ 528.899199] frontend_changed: backend/vbd/10/2050: prepare for reconnect
[ 529.210654] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 529.268767] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 529.345468] alloc irq_desc for 1688 on node 0
[ 529.345473] alloc kstat_irqs on node 0
[ 535.645179] xen_bridge: port 10(vif10.0) entering forwarding state
[ 537.334248] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=17056 PROTO=2
[ 561.218216] FW: BLOCKED low tcp input: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=88.159.79.43 DST=88.159.76.249 LEN=52 TOS=0x00 PREC=0x00 TTL=120 ID=30897 DF PROTO=TCP SPT=58743 DPT=81 WINDOW=8192 RES=0x00 SYN URGP=0
[ 564.122742] FW: BLOCKED low tcp input: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=88.159.79.43 DST=88.159.76.249 LEN=52 TOS=0x00 PREC=0x00 TTL=120 ID=30964 DF PROTO=TCP SPT=58738 DPT=515 WINDOW=8192 RES=0x00 SYN URGP=0
[ 564.142819] FW: BLOCKED low tcp input: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=88.159.79.43 DST=88.159.76.249 LEN=52 TOS=0x00 PREC=0x00 TTL=120 ID=30965 DF PROTO=TCP SPT=58743 DPT=81 WINDOW=8192 RES=0x00 SYN URGP=0
[ 588.265811] alloc irq_desc for 1687 on node 0
[ 588.265816] alloc kstat_irqs on node 0
[ 590.182501] pciback pci-11-0: allocated pdev @ 0xffff88001adc6580
[ 590.552528] pciback pci-11-0: getting be setup
[ 590.552733] pciback pci-11-0: exporting dom 0 bus 3 slot 6 func 0
[ 590.556514] pciback 0000:03:06.0: registering for 11
[ 590.563091] pciback pci-11-0: Publishing pci roots
[ 590.563286] pciback pci-11-0: writing root 0 at 0000:03
[ 590.677775] pciback pci-11-0: fe state changed 1
[ 590.849059] alloc irq_desc for 1686 on node 0
[ 590.849066] alloc kstat_irqs on node 0
[ 592.815494] device vif11.0 entered promiscuous mode
[ 592.829605] xen_bridge: port 11(vif11.0) entering learning state
[ 597.951102] xen_bridge: port 11(vif11.0) entering disabled state
[ 597.968614] xen_bridge: port 11(vif11.0) entering learning state
[ 608.423919] pciback pci-11-0: fe state changed 3
[ 608.424246] pciback pci-11-0: Reading frontend config
[ 608.424786] pciback pci-11-0: Attaching to frontend resources - gnt_ref=8 evtchn=9
[ 608.424893] alloc irq_desc for 1685 on node 0
[ 608.424899] alloc kstat_irqs on node 0
[ 608.424944] pciback pci-11-0: Attached!
[ 608.424947] pciback pci-11-0: Connecting...
[ 608.438691] pciback pci-11-0: Connected? 0
[ 608.465658] blkback: ring-ref 9, event-channel 10, protocol 1 (x86_64-abi)
[ 608.473837] alloc irq_desc for 1684 on node 0
[ 608.473841] alloc kstat_irqs on node 0
[ 608.578316] blkback: ring-ref 10, event-channel 11, protocol 1 (x86_64-abi)
[ 608.586534] alloc irq_desc for 1683 on node 0
[ 608.586539] alloc kstat_irqs on node 0
[ 612.977267] xen_bridge: port 11(vif11.0) entering forwarding state
[ 613.948185] pciback pci-11-0: fe state changed 4
[ 614.025532] alloc irq_desc for 1682 on node 0
[ 614.025536] alloc kstat_irqs on node 0
[ 623.724776] pciback 0000:03:06.0: enabling device (0000 -> 0001)
[ 623.725647] xen: registering gsi 22 triggering 0 polarity 1
[ 623.725647] xen_allocate_pirq: returning irq 22 for gsi 22
[ 623.725647] xen: --> irq=22
[ 623.741191] Already setup the GSI :22
[ 623.749107] pciback 0000:03:06.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 623.749107] pciback 0000:03:06.0: pciback[0000:03:06.0]: #22 on disable-> enable
[ 623.749549] pciback 0000:03:06.0: pciback[0000:03:06.0]: #22 on enabled
[ 623.749845] pciback 0000:03:06.0: enabling bus mastering
[ 636.820166] alloc irq_desc for 1681 on node 0
[ 636.820171] alloc kstat_irqs on node 0
[ 637.210698] block tda: sector-size: 512 capacity: 1048576
[ 637.577729] block tdb: sector-size: 512 capacity: 8388608
[ 638.923860] device vif12.0 entered promiscuous mode
[ 638.937658] xen_bridge: port 12(vif12.0) entering learning state
[ 639.199961] xen_bridge: port 12(vif12.0) entering disabled state
[ 639.216241] xen_bridge: port 12(vif12.0) entering learning state
[ 640.607100] alloc irq_desc for 1680 on node 0
[ 640.607106] alloc kstat_irqs on node 0
[ 642.280779] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[ 642.289473] alloc irq_desc for 1679 on node 0
[ 642.289480] alloc kstat_irqs on node 0
[ 642.338595] blkback: ring-ref 2046, event-channel 5, protocol 1 (x86_64-abi)
[ 642.347269] alloc irq_desc for 1678 on node 0
[ 642.347273] alloc kstat_irqs on node 0
[ 649.228717] frontend_changed: backend/vbd/12/2049: prepare for reconnect
[ 649.296783] frontend_changed: backend/vbd/12/2050: prepare for reconnect
[ 649.721170] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 649.767100] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 649.884166] alloc irq_desc for 1677 on node 0
[ 649.884171] alloc kstat_irqs on node 0
[ 654.224125] xen_bridge: port 12(vif12.0) entering forwarding state
[ 662.401373] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=17423 PROTO=2
[ 677.534599] alloc irq_desc for 1676 on node 0
[ 677.534619] alloc kstat_irqs on node 0
[ 678.569269] device vif13.0 entered promiscuous mode
[ 678.582173] xen_bridge: port 13(vif13.0) entering learning state
[ 678.741177] xen_bridge: port 13(vif13.0) entering disabled state
[ 678.757207] xen_bridge: port 13(vif13.0) entering learning state
[ 679.730168] pciback pci-13-0: allocated pdev @ 0xffff88001f377900
[ 679.759894] pciback pci-13-0: getting be setup
[ 679.760686] pciback pci-13-0: exporting dom 0 bus a slot 0 func 0
[ 679.764843] pciback 0000:0a:00.0: registering for 13
[ 679.775295] pciback pci-13-0: exporting dom 0 bus a slot 0 func 1
[ 679.785027] pciback 0000:0a:00.1: registering for 13
[ 679.798335] pciback pci-13-0: exporting dom 0 bus a slot 0 func 2
[ 679.808135] pciback 0000:0a:00.2: registering for 13
[ 679.830072] pciback pci-13-0: exporting dom 0 bus a slot 0 func 3
[ 679.836886] pciback 0000:0a:00.3: registering for 13
[ 679.852885] pciback pci-13-0: exporting dom 0 bus a slot 0 func 4
[ 679.862655] pciback 0000:0a:00.4: registering for 13
[ 679.877258] pciback pci-13-0: exporting dom 0 bus a slot 0 func 5
[ 679.887326] pciback 0000:0a:00.5: registering for 13
[ 679.894547] pciback pci-13-0: exporting dom 0 bus a slot 0 func 6
[ 679.904209] pciback 0000:0a:00.6: registering for 13
[ 679.917685] pciback pci-13-0: exporting dom 0 bus a slot 0 func 7
[ 679.930382] pciback 0000:0a:00.7: registering for 13
[ 679.946250] pciback pci-13-0: Publishing pci roots
[ 679.946417] pciback pci-13-0: writing root 0 at 0000:0a
[ 679.971933] pciback pci-13-0: Publishing pci roots
[ 679.978491] pciback pci-13-0: Publishing pci roots
[ 679.982143] pciback pci-13-0: Publishing pci roots
[ 679.988758] pciback pci-13-0: Publishing pci roots
[ 679.992214] pciback pci-13-0: Publishing pci roots
[ 679.995873] pciback pci-13-0: Publishing pci roots
[ 679.998019] pciback pci-13-0: Publishing pci roots
[ 680.234068] pciback pci-13-0: fe state changed 1
[ 680.322648] alloc irq_desc for 1675 on node 0
[ 680.322654] alloc kstat_irqs on node 0
[ 684.362369] pciback pci-13-0: fe state changed 3
[ 684.362899] pciback pci-13-0: Reading frontend config
[ 684.363240] pciback pci-13-0: Attaching to frontend resources - gnt_ref=8 evtchn=21
[ 684.363326] alloc irq_desc for 1674 on node 0
[ 684.363330] alloc kstat_irqs on node 0
[ 684.363372] pciback pci-13-0: Attached!
[ 684.363374] pciback pci-13-0: Connecting...
[ 684.372936] pciback pci-13-0: Connected? 0
[ 684.396406] pciback pci-13-0: fe state changed 4
[ 684.586783] blkback: ring-ref 9, event-channel 22, protocol 1 (x86_64-abi)
[ 684.595365] alloc irq_desc for 1673 on node 0
[ 684.595370] alloc kstat_irqs on node 0
[ 684.731438] pciback 0000:0a:00.1: enabling device (0000 -> 0002)
[ 684.736902] xen: registering gsi 28 triggering 0 polarity 1
[ 684.736902] xen_allocate_pirq: returning irq 28 for gsi 28
[ 684.736902] xen: --> irq=28
[ 684.748530] Already setup the GSI :28
[ 684.756489] pciback 0000:0a:00.1: PCI INT A -> GSI 28 (level, low) -> IRQ 28
[ 684.756489] pciback 0000:0a:00.1: pciback[0000:0a:00.1]: #28 on disable-> enable
[ 684.757104] pciback 0000:0a:00.1: pciback[0000:0a:00.1]: #28 on enabled
[ 684.757459] pciback 0000:0a:00.1: enabling bus mastering
[ 684.757472] pciback 0000:0a:00.1: setting latency timer to 64
[ 684.778415] blkback: ring-ref 10, event-channel 23, protocol 1 (x86_64-abi)
[ 684.787013] pciback 0000:0a:00.1: enabling Mem-Wr-Inval
[ 684.787021] alloc irq_desc for 1672 on node 0
[ 684.787025] alloc kstat_irqs on node 0
[ 684.790902] pciback 0000:0a:00.3: enabling device (0000 -> 0002)
[ 684.791057] xen: registering gsi 29 triggering 0 polarity 1
[ 684.791057] xen_allocate_pirq: returning irq 29 for gsi 29
[ 684.791057] xen: --> irq=29
[ 684.808146] Already setup the GSI :29
[ 684.809053] pciback 0000:0a:00.3: PCI INT B -> GSI 29 (level, low) -> IRQ 29
[ 684.809053] pciback 0000:0a:00.3: pciback[0000:0a:00.3]: #29 on disable-> enable
[ 684.816947] pciback 0000:0a:00.3: pciback[0000:0a:00.3]: #29 on enabled
[ 684.817133] pciback 0000:0a:00.3: enabling bus mastering
[ 684.817142] pciback 0000:0a:00.3: setting latency timer to 64
[ 684.842247] pciback 0000:0a:00.3: enabling Mem-Wr-Inval
[ 684.848986] pciback 0000:0a:00.5: enabling device (0000 -> 0002)
[ 684.849953] xen: registering gsi 30 triggering 0 polarity 1
[ 684.849953] xen_allocate_pirq: returning irq 30 for gsi 30
[ 684.849953] xen: --> irq=30
[ 684.866154] Already setup the GSI :30
[ 684.871282] pciback 0000:0a:00.5: PCI INT C -> GSI 30 (level, low) -> IRQ 30
[ 684.871282] pciback 0000:0a:00.5: pciback[0000:0a:00.5]: #30 on disable-> enable
[ 684.874760] pciback 0000:0a:00.5: pciback[0000:0a:00.5]: #30 on enabled
[ 684.880179] pciback 0000:0a:00.5: enabling bus mastering
[ 684.880189] pciback 0000:0a:00.5: setting latency timer to 64
[ 684.906260] pciback 0000:0a:00.5: enabling Mem-Wr-Inval
[ 684.912862] pciback 0000:0a:00.7: enabling device (0000 -> 0002)
[ 684.913054] xen: registering gsi 31 triggering 0 polarity 1
[ 684.913054] xen_allocate_pirq: returning irq 31 for gsi 31
[ 684.913054] xen: --> irq=31
[ 684.930019] Already setup the GSI :31
[ 684.932592] pciback 0000:0a:00.7: PCI INT D -> GSI 31 (level, low) -> IRQ 31
[ 684.932592] pciback 0000:0a:00.7: pciback[0000:0a:00.7]: #31 on disable-> enable
[ 684.938754] pciback 0000:0a:00.7: pciback[0000:0a:00.7]: #31 on enabled
[ 684.939177] pciback 0000:0a:00.7: enabling bus mastering
[ 684.939187] pciback 0000:0a:00.7: setting latency timer to 64
[ 684.970240] pciback 0000:0a:00.7: enabling Mem-Wr-Inval
[ 684.976959] pciback 0000:0a:00.0: enabling device (0000 -> 0002)
[ 684.977055] xen: registering gsi 28 triggering 0 polarity 1
[ 684.977055] xen_allocate_pirq: returning irq 28 for gsi 28
[ 684.977055] xen: --> irq=28
[ 684.994480] Already setup the GSI :28
[ 684.999327] pciback 0000:0a:00.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
[ 684.999327] pciback 0000:0a:00.0: pciback[0000:0a:00.0]: #28 on disable-> enable
[ 685.003338] pciback 0000:0a:00.0: pciback[0000:0a:00.0]: #28 on enabled
[ 685.003632] pciback 0000:0a:00.0: enabling bus mastering
[ 685.003642] pciback 0000:0a:00.0: setting latency timer to 64
[ 685.063975] pciback 0000:0a:00.2: enabling device (0000 -> 0002)
[ 685.064953] xen: registering gsi 29 triggering 0 polarity 1
[ 685.064953] xen_allocate_pirq: returning irq 29 for gsi 29
[ 685.064953] xen: --> irq=29
[ 685.081560] Already setup the GSI :29
[ 685.088239] pciback 0000:0a:00.2: PCI INT B -> GSI 29 (level, low) -> IRQ 29
[ 685.088239] pciback 0000:0a:00.2: pciback[0000:0a:00.2]: #29 on disable-> enable
[ 685.098959] pciback 0000:0a:00.2: pciback[0000:0a:00.2]: #29 on enabled
[ 685.099062] pciback 0000:0a:00.2: enabling bus mastering
[ 685.099071] pciback 0000:0a:00.2: setting latency timer to 64
[ 685.102496] alloc irq_desc for 1671 on node 0
[ 685.102501] alloc kstat_irqs on node 0
[ 685.160606] pciback 0000:0a:00.4: enabling device (0000 -> 0002)
[ 685.168504] xen: registering gsi 30 triggering 0 polarity 1
[ 685.168504] xen_allocate_pirq: returning irq 30 for gsi 30
[ 685.168504] xen: --> irq=30
[ 685.169042] Already setup the GSI :30
[ 685.169048] pciback 0000:0a:00.4: PCI INT C -> GSI 30 (level, low) -> IRQ 30
[ 685.169067] pciback 0000:0a:00.4: pciback[0000:0a:00.4]: #30 on disable-> enable
[ 685.169099] pciback 0000:0a:00.4: pciback[0000:0a:00.4]: #30 on enabled
[ 685.169725] pciback 0000:0a:00.4: enabling bus mastering
[ 685.169742] pciback 0000:0a:00.4: setting latency timer to 64
[ 685.236047] pciback 0000:0a:00.6: enabling device (0000 -> 0002)
[ 685.236682] xen: registering gsi 31 triggering 0 polarity 1
[ 685.236682] xen_allocate_pirq: returning irq 31 for gsi 31
[ 685.236682] xen: --> irq=31
[ 685.254399] Already setup the GSI :31
[ 685.255323] pciback 0000:0a:00.6: PCI INT D -> GSI 31 (level, low) -> IRQ 31
[ 685.255323] pciback 0000:0a:00.6: pciback[0000:0a:00.6]: #31 on disable-> enable
[ 685.261485] pciback 0000:0a:00.6: pciback[0000:0a:00.6]: #31 on enabled
[ 685.261784] pciback 0000:0a:00.6: enabling bus mastering
[ 685.261792] pciback 0000:0a:00.6: setting latency timer to 64
[ 693.765163] xen_bridge: port 13(vif13.0) entering forwarding state
[ 730.337125] FW: INVALID IP PACKET: IN=eth0 OUT= MAC=40:61:86:f4:67:d9:00:08:ae:10:46:60:08:00 SRC=70.42.241.111 DST=88.159.76.249 LEN=40 TOS=0x00 PREC=0x00 TTL=44 ID=0 DF PROTO=TCP SPT=80 DPT=54378 WINDOW=1751 RES=0x00 RST URGP=0
[ 787.469022] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=17796 PROTO=2
[ 912.538171] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=18175 PROTO=2
[ 983.892836] FW: New not syn:IN=eth0 OUT=eth0 SRC=217.149.217.48 DST=88.159.73.189 LEN=52 TOS=0x00 PREC=0x00 TTL=117 ID=13153 DF PROTO=TCP SPT=51051 DPT=13568 WINDOW=4344 RES=0x00 ACK URGP=0
[ 1037.608236] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=18572 PROTO=2
[ 1152.691883] alloc irq_desc for 1670 on node 0
[ 1152.691889] alloc kstat_irqs on node 0
[ 1153.352863] device vif14.0 entered promiscuous mode
[ 1153.366881] xen_bridge: port 14(vif14.0) entering learning state
[ 1153.510046] xen_bridge: port 14(vif14.0) entering disabled state
[ 1153.528037] xen_bridge: port 14(vif14.0) entering learning state
[ 1157.040438] device tap14.0 entered promiscuous mode
[ 1157.049765] xen_bridge: port 15(tap14.0) entering learning state
[ 1157.069887] alloc irq_desc for 1669 on node 0
[ 1157.069893] alloc kstat_irqs on node 0
[ 1157.765422] pciback 0000:05:00.1: enabling permissive mode configuration space accesses!
[ 1157.766138] pciback 0000:05:00.1: permissive mode is potentially unsafe!
[ 1157.853691] pciback 0000:05:00.0: enabling permissive mode configuration space accesses!
[ 1157.854138] pciback 0000:05:00.0: permissive mode is potentially unsafe!
[ 1158.068109] pciback pci-14-0: allocated pdev @ 0xffff88001f19c100
[ 1158.086538] pciback pci-14-0: getting be setup
[ 1158.094161] pciback pci-14-0: exporting dom 0 bus 5 slot 0 func 1
[ 1158.098133] pciback 0000:05:00.1: registering for 14
[ 1158.109842] pciback pci-14-0: exporting dom 0 bus 5 slot 0 func 0
[ 1158.113578] pciback 0000:05:00.0: registering for 14
[ 1158.118842] pciback pci-14-0: Publishing pci roots
[ 1158.119006] pciback pci-14-0: writing root 0 at 0000:05
[ 1158.137216] pciback pci-14-0: Publishing pci roots
[ 1158.303880] pciback pci-14-0: fe state changed 1
[ 1162.637555] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=18966 PROTO=2
[ 1168.536087] xen_bridge: port 14(vif14.0) entering forwarding state
[ 1172.058093] xen_bridge: port 15(tap14.0) entering forwarding state
[ 1287.696506] FW: BLOCKED IGMP: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:08:ae:04:2e:43:08:00 SRC=88.159.81.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=19354 PROTO=2
[-- Attachment #4: lspci.txt --]
[-- Type: text/plain, Size: 5288 bytes --]
00:00.0 Host bridge: ATI Technologies Inc RD890 Northbridge only single slot PCI-e GFX Hydra part (rev 02)
00:00.2 Generic system peripheral [0806]: ATI Technologies Inc Device 5a23
00:02.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port B)
Kernel driver in use: pcieport
00:03.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port C)
Kernel driver in use: pcieport
00:05.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port E)
Kernel driver in use: pcieport
00:06.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port F)
Kernel driver in use: pcieport
00:0a.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (external gfx1 port A)
Kernel driver in use: pcieport
00:0b.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (NB-SB link)
Kernel driver in use: pcieport
00:0d.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (external gfx1 port B)
Kernel driver in use: pcieport
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] (rev 40)
Kernel driver in use: ahci
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
Kernel driver in use: ohci_hcd
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
Kernel driver in use: ehci_hcd
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
Kernel driver in use: ohci_hcd
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
Kernel driver in use: ehci_hcd
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 41)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller (rev 40)
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
Kernel driver in use: ohci_hcd
00:15.0 PCI bridge: ATI Technologies Inc Device 43a0
Kernel driver in use: pcieport
00:16.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
Kernel driver in use: ohci_hcd
00:16.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
Kernel driver in use: ehci_hcd
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control
03:06.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
Kernel driver in use: pciback
04:00.0 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
04:00.1 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
04:00.2 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
04:00.3 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
04:00.4 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
04:00.5 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
04:00.6 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
04:00.7 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
05:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3450
Kernel driver in use: pciback
05:00.1 Audio device: ATI Technologies Inc RV620 Audio device [Radeon HD 34xx Series]
Kernel driver in use: pciback
06:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge (rev 03)
07:01.0 USB Controller: NEC Corporation USB (rev 43)
Kernel driver in use: ohci_hcd
07:01.1 USB Controller: NEC Corporation USB (rev 43)
Kernel driver in use: ohci_hcd
07:01.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
Kernel driver in use: ehci_hcd
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Kernel driver in use: r8169
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Kernel driver in use: r8169
0a:00.0 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
0a:00.1 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
0a:00.2 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
0a:00.3 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
0a:00.4 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
0a:00.5 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
0a:00.6 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
0a:00.7 USB Controller: NetMos Technology Device 9990
Kernel driver in use: pciback
0b:00.0 VGA compatible controller: nVidia Corporation GeForce 8400 GS (rev a1)
[-- Attachment #5: lspci-verbose.txt --]
[-- Type: text/plain, Size: 72539 bytes --]
00:00.0 Host bridge [0600]: ATI Technologies Inc RD890 Northbridge only single slot PCI-e GFX Hydra part [1002:5a11] (rev 02)
Subsystem: ATI Technologies Inc RD890 Northbridge only single slot PCI-e GFX Hydra part [1002:5a11]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Capabilities: [f0] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [c4] HyperTransport: Slave or Primary Interface
Command: BaseUnitID=0 UnitCnt=20 MastHost- DefDir- DUL-
Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
Link Config 0: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit DwFcInEn- LWO=16bit DwFcOutEn-
Link Control 1: CFlE- CST- CFE- <LkFail+ Init- EOC+ TXO+ <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
Link Config 1: MLWI=8bit DwFcIn- MLWO=8bit DwFcOut- LWI=8bit DwFcInEn- LWO=8bit DwFcOutEn-
Revision ID: 3.00
Link Frequency 0: [b]
Link Error 0: <Prot- <Ovfl- <EOC- CTLTm-
Link Frequency Capability 0: 200MHz+ 300MHz- 400MHz+ 500MHz- 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz+ 1.4GHz- 1.6GHz- Vend-
Feature Capability: IsocFC+ LDTSTOP+ CRCTM- ECTLT- 64bA+ UIDRD-
Link Frequency 1: 200MHz
Link Error 1: <Prot- <Ovfl- <EOC- CTLTm-
Link Frequency Capability 1: 200MHz- 300MHz- 400MHz- 500MHz- 600MHz- 800MHz- 1.0GHz- 1.2GHz- 1.4GHz- 1.6GHz- Vend-
Error Handling: PFlE- OFlE- PFE- OFE- EOCFE- RFE- CRCFE- SERRFE- CF- RE- PNFE- ONFE- EOCNFE- RNFE- CRCNFE- SERRNFE-
Prefetchable memory behind bridge Upper: 00-00
Bus Number: 00
Capabilities: [40] HyperTransport: Retry Mode
Capabilities: [54] HyperTransport: UnitID Clumping
Capabilities: [9c] HyperTransport: #1a
Capabilities: [70] Message Signalled Interrupts: Mask- 64bit- Queue=0/2 Enable-
Address: 00000000 Data: 0000
00:00.2 Generic system peripheral [0806]: ATI Technologies Inc Device [1002:5a23]
Subsystem: ATI Technologies Inc Device [1002:5a23]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 10
Capabilities: [40] Secure device <?>
Capabilities: [54] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0100c Data: 4128
Capabilities: [64] HyperTransport: MSI Mapping Enable+ Fixed+
00:02.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port B) [1002:5a16] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fa000000-fe9fffff
Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x8, ASPM L0s L1, Latency L0 <1us, L1 <8us
ClockPM- Suprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x8, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise-
Slot # 1, PowerLimit 25.000000; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Address: fee3f00c Data: 41c0
Capabilities: [b0] Subsystem: ATI Technologies Inc Device [1002:5a11]
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Vendor Specific Information <?>
Capabilities: [190] Access Controls <?>
Kernel driver in use: pcieport
00:03.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port C) [1002:5a17] (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: f9f00000-f9ffffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x8, ASPM L0s L1, Latency L0 <1us, L1 <8us
ClockPM- Suprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise-
Slot # 3, PowerLimit 11.000000; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Address: fee3f00c Data: 41c8
Capabilities: [b0] Subsystem: ATI Technologies Inc Device [1002:5a11]
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Vendor Specific Information <?>
Capabilities: [190] Access Controls <?>
Kernel driver in use: pcieport
00:05.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port E) [1002:5a19] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: f9e00000-f9efffff
Prefetchable memory behind bridge: 00000000cff00000-00000000cfffffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 <1us, L1 <8us
ClockPM- Suprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise-
Slot # 5, PowerLimit 75.000000; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Address: fee3f00c Data: 41d0
Capabilities: [b0] Subsystem: ATI Technologies Inc Device [1002:5a11]
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Vendor Specific Information <?>
Capabilities: [190] Access Controls <?>
Kernel driver in use: pcieport
00:06.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port F) [1002:5a1a] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: f9d00000-f9dfffff
Prefetchable memory behind bridge: 00000000cfe00000-00000000cfefffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #2, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 <1us, L1 <8us
ClockPM- Suprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise-
Slot # 6, PowerLimit 75.000000; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Address: fee3f00c Data: 41d8
Capabilities: [b0] Subsystem: ATI Technologies Inc Device [1002:5a11]
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Vendor Specific Information <?>
Capabilities: [190] Access Controls <?>
Kernel driver in use: pcieport
00:0a.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (external gfx1 port A) [1002:5a1d] (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=06, subordinate=07, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: f9c00000-f9cfffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #5, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <1us, L1 <8us
ClockPM- Suprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise-
Slot # 2, PowerLimit 75.000000; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Address: fee3f00c Data: 4121
Capabilities: [b0] Subsystem: ATI Technologies Inc Device [1002:5a11]
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Vendor Specific Information <?>
Capabilities: [190] Access Controls <?>
Kernel driver in use: pcieport
00:0b.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (NB-SB link) [1002:5a1f] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: f9b00000-f9bfffff
Prefetchable memory behind bridge: 00000000b0000000-00000000bfffffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency L0 <1us, L1 <8us
ClockPM- Suprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise-
Slot # 5, PowerLimit 75.000000; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Address: fee3f00c Data: 4129
Capabilities: [b0] Subsystem: ATI Technologies Inc Device [1002:5a11]
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Vendor Specific Information <?>
Capabilities: [190] Access Controls <?>
Kernel driver in use: pcieport
00:0d.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (external gfx1 port B) [1002:5a1e] (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: f9a00000-f9afffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x4, ASPM L0s L1, Latency L0 <1us, L1 <8us
ClockPM- Suprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise-
Slot # 4, PowerLimit 75.000000; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Address: fee3f00c Data: 4131
Capabilities: [b0] Subsystem: ATI Technologies Inc Device [1002:5a11]
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Vendor Specific Information <?>
Capabilities: [190] Access Controls <?>
Kernel driver in use: pcieport
00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] (rev 40) (prog-if 01 [AHCI 1.0])
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 1744
Region 0: I/O ports at 7000 [size=8]
Region 1: I/O ports at 6000 [size=4]
Region 2: I/O ports at 5000 [size=8]
Region 3: I/O ports at 3000 [size=4]
Region 4: I/O ports at 2000 [size=16]
Region 5: Memory at f98ff000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable+
Address: 00000000fee0200c Data: 41a1
Capabilities: [70] SATA HBA <?>
Capabilities: [a4] PCIe advanced features <?>
Kernel driver in use: ahci
00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI])
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at f98fb000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd
00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 17
Region 0: Memory at f98ff400 (32-bit, non-prefetchable) [size=256]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+
Capabilities: [e4] Debug port: BAR=1 offset=00e0
Kernel driver in use: ehci_hcd
00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI])
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at f98fc000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd
00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 17
Region 0: Memory at f98ff800 (32-bit, non-prefetchable) [size=256]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+
Capabilities: [e4] Debug port: BAR=1 offset=00e0
Kernel driver in use: ehci_hcd
00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 41)
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] (rev 40)
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] (rev 40) (prog-if 00 [Normal decode])
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64
Bus: primary=00, secondary=03, subordinate=03, sec-latency=64
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: fff00000-000fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
00:14.5 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller [1002:4399] (prog-if 10 [OHCI])
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 18
Region 0: Memory at f98fd000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd
00:15.0 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a0] (prog-if 00 [Normal decode])
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #247, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <64ns, L1 <1us
ClockPM- Suprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed unknown, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise-
Slot # 20, PowerLimit 75.000000; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee3f00c Data: 4139
Capabilities: [b0] Subsystem: ATI Technologies Inc Device [1002:0000]
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Vendor Specific Information <?>
Kernel driver in use: pcieport
00:16.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI])
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at f98fe000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd
00:16.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 17
Region 0: Memory at f98ffc00 (32-bit, non-prefetchable) [size=256]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+
Capabilities: [e4] Debug port: BAR=1 offset=00e0
Kernel driver in use: ehci_hcd
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration [1022:1200]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Capabilities: [80] HyperTransport: Host or Secondary Interface
Command: WarmRst+ DblEnd- DevNum=0 ChainSide- HostHide+ Slave- <EOCErr- DUL-
Link Control: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn- LSEn+ ExtCTL- 64b-
Link Config: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit DwFcInEn- LWO=16bit DwFcOutEn-
Revision ID: 3.00
Link Frequency: [b]
Link Error: <Prot- <Ovfl- <EOC- CTLTm-
Link Frequency Capability: 200MHz+ 300MHz- 400MHz+ 500MHz- 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz+ 1.4GHz- 1.6GHz- Vend-
Feature Capability: IsocFC+ LDTSTOP+ CRCTM- ECTLT- 64bA+ UIDRD- ExtRS- UCnfE-
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map [1022:1201]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller [1022:1202]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control [1022:1203]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Capabilities: [f0] Secure device <?>
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control [1022:1204]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
03:06.0 Multimedia audio controller [0401]: C-Media Electronics Inc CM8738 [13f6:0111] (rev 10)
Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device [13f6:0111]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (500ns min, 6000ns max)
Interrupt: pin A routed to IRQ 22
Region 0: I/O ports at a800 [size=256]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: pciback
04:00.0 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 10 [OHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 40
Region 0: Memory at f9af8000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Virtual Channel <?>
Kernel driver in use: pciback
04:00.1 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 20 [EHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 40
Region 0: Memory at f9af9000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
04:00.2 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 10 [OHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 41
Region 0: Memory at f9afa000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
04:00.3 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 20 [EHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 41
Region 0: Memory at f9afb000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
04:00.4 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 10 [OHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 42
Region 0: Memory at f9afc000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
04:00.5 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 20 [EHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 42
Region 0: Memory at f9afd000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
04:00.6 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 10 [OHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin D routed to IRQ 43
Region 0: Memory at f9afe000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
04:00.7 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 20 [EHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin D routed to IRQ 43
Region 0: Memory at f9aff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
05:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3450 [1002:95c5] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:01d4]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 32
Region 0: Memory at b0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at f9be0000 (64-bit, non-prefetchable) [size=64K]
Region 4: I/O ports at b000 [size=256]
Expansion ROM at f9bc0000 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [100] Vendor Specific Information <?>
Kernel driver in use: pciback
05:00.1 Audio device [0403]: ATI Technologies Inc RV620 Audio device [Radeon HD 34xx Series] [1002:aa28]
Subsystem: ASUSTeK Computer Inc. Device [1043:aa28]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 33
Region 0: Memory at f9bfc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [100] Vendor Specific Information <?>
Kernel driver in use: pciback
06:00.0 PCI bridge [0604]: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge [104c:8231] (rev 03) (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=06, secondary=07, subordinate=07, sec-latency=64
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: f9c00000-f9cfffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/4 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [80] Subsystem: Gammagraphx, Inc. Device [0000:0000]
Capabilities: [90] Express (v1) PCI/PCI-X Bridge, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ BrConfRtry-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <1us, L1 <16us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting <?>
07:01.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) (prog-if 10 [OHCI])
Subsystem: NEC Corporation Hama USB 2.0 CardBus [1033:0035]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (250ns min, 10500ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 44
Region 0: Memory at f9cfd000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ohci_hcd
07:01.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) (prog-if 10 [OHCI])
Subsystem: NEC Corporation Hama USB 2.0 CardBus [1033:0035]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (250ns min, 10500ns max), Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 45
Region 0: Memory at f9cfe000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ohci_hcd
07:01.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04) (prog-if 20 [EHCI])
Subsystem: Device [1838:1074]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (4000ns min, 8500ns max), Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 46
Region 0: Memory at f9cffc00 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ehci_hcd
08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 03)
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 1742
Region 0: I/O ports at c800 [size=256]
Region 2: Memory at cfeff000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at cfef8000 (64-bit, prefetchable) [size=16K]
Expansion ROM at f9de0000 [disabled] [size=128K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0200c Data: 41c1
Capabilities: [70] Express (v2) Endpoint, MSI 01
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [ac] MSI-X: Enable- Mask- TabSize=4
Vector table: BAR=4 offset=00000000
PBA: BAR=4 offset=00000800
Capabilities: [cc] Vital Product Data <?>
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Capabilities: [160] Device Serial Number 00-e0-4c-68-00-00-00-03
Kernel driver in use: r8169
09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 03)
Subsystem: Micro-Star International Co., Ltd. Device [1462:7640]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 1743
Region 0: I/O ports at d800 [size=256]
Region 2: Memory at cffff000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at cfff8000 (64-bit, prefetchable) [size=16K]
Expansion ROM at f9ee0000 [disabled] [size=128K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0100c Data: 41b1
Capabilities: [70] Express (v2) Endpoint, MSI 01
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [ac] MSI-X: Enable- Mask- TabSize=4
Vector table: BAR=4 offset=00000000
PBA: BAR=4 offset=00000800
Capabilities: [cc] Vital Product Data <?>
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Capabilities: [160] Device Serial Number 00-e0-4c-68-00-00-00-04
Kernel driver in use: r8169
0a:00.0 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 10 [OHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 28
Region 0: Memory at f9ff8000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Virtual Channel <?>
Kernel driver in use: pciback
0a:00.1 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 20 [EHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 28
Region 0: Memory at f9ff9000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
0a:00.2 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 10 [OHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 29
Region 0: Memory at f9ffa000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
0a:00.3 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 20 [EHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 29
Region 0: Memory at f9ffb000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
0a:00.4 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 10 [OHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 30
Region 0: Memory at f9ffc000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
0a:00.5 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 20 [EHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 30
Region 0: Memory at f9ffd000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
0a:00.6 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 10 [OHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin D routed to IRQ 31
Region 0: Memory at f9ffe000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
0a:00.7 USB Controller [0c03]: NetMos Technology Device [9710:9990] (prog-if 20 [EHCI])
Subsystem: Device [a000:4000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin D routed to IRQ 31
Region 0: Memory at f9fff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0 <64ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: pciback
0b:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400 GS [10de:06e4] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:8266]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 10
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
Region 5: I/O ports at e800 [size=128]
Expansion ROM at fe9e0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <4us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <512ns, L1 <1us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Virtual Channel <?>
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information <?>
[-- Attachment #6: proc-interrupts.txt --]
[-- Type: text/plain, Size: 15581 bytes --]
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
1: 2 0 0 0 0 0 xen-pirq-ioapic-edge i8042
8: 0 0 0 0 0 0 xen-pirq-ioapic-edge rtc0
9: 0 0 0 0 0 0 xen-pirq-ioapic-edge acpi
12: 4 0 0 0 0 0 xen-pirq-ioapic-edge i8042
17: 1 0 0 0 0 0 xen-pirq-ioapic-level ehci_hcd:usb1, ehci_hcd:usb2, ehci_hcd:usb3
18: 4 0 0 0 0 0 xen-pirq-ioapic-level ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7, ohci_hcd:usb8
22: 0 0 0 0 0 0 xen-pirq-ioapic-level pciback[0000:03:06.0]
28: 0 0 0 0 0 0 xen-pirq-ioapic-level pciback[0000:0a:00.1], pciback[0000:0a:00.0]
29: 0 0 0 0 0 0 xen-pirq-ioapic-level pciback[0000:0a:00.3], pciback[0000:0a:00.2]
30: 0 0 0 0 0 0 xen-pirq-ioapic-level pciback[0000:0a:00.5], pciback[0000:0a:00.4]
31: 1627 0 0 0 0 0 xen-pirq-ioapic-level pciback[0000:0a:00.7], pciback[0000:0a:00.6]
40: 316173 0 0 0 0 0 xen-pirq-ioapic-level pciback[0000:04:00.1], pciback[0000:04:00.0]
41: 11087 0 0 0 0 0 xen-pirq-ioapic-level pciback[0000:04:00.3], pciback[0000:04:00.2]
42: 0 0 0 0 0 0 xen-pirq-ioapic-level pciback[0000:04:00.5], pciback[0000:04:00.4]
43: 32047 0 0 0 0 0 xen-pirq-ioapic-level pciback[0000:04:00.7], pciback[0000:04:00.6]
44: 20 0 0 0 0 0 xen-pirq-ioapic-level ohci_hcd:usb9
45: 388985 0 0 0 0 0 xen-pirq-ioapic-level ohci_hcd:usb10
46: 23 0 0 0 0 0 xen-pirq-ioapic-level ehci_hcd:usb4
1669: 788240 0 0 0 0 0 xen-dyn-event evtchn:qemu-dm
1670: 8 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1671: 40 0 0 0 0 0 xen-dyn-event vif13.0
1672: 1774 0 0 0 0 0 xen-dyn-event blkif-backend
1673: 24 0 0 0 0 0 xen-dyn-event blkif-backend
1674: 1229 0 0 0 0 0 xen-dyn-event pciback
1675: 1611 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1676: 492 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1677: 114 0 0 0 0 0 xen-dyn-event vif12.0
1678: 1043 0 0 0 0 0 xen-dyn-event blkif-backend
1679: 18 0 0 0 0 0 xen-dyn-event blkif-backend
1680: 1272 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1681: 464 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1682: 105 0 0 0 0 0 xen-dyn-event vif11.0
1683: 1288 0 0 0 0 0 xen-dyn-event blkif-backend
1684: 21 0 0 0 0 0 xen-dyn-event blkif-backend
1685: 378 0 0 0 0 0 xen-dyn-event pciback
1686: 692 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1687: 493 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1688: 80 0 0 0 0 0 xen-dyn-event vif10.0
1689: 1168 0 0 0 0 0 xen-dyn-event blkif-backend
1690: 19 0 0 0 0 0 xen-dyn-event blkif-backend
1691: 1233 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1692: 507 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1693: 16 0 0 0 0 0 xen-dyn-event vif9.0
1694: 545 0 0 0 0 0 xen-dyn-event blkif-backend
1695: 2466 0 0 0 0 0 xen-dyn-event blkif-backend
1696: 41 0 0 0 0 0 xen-dyn-event blkif-backend
1697: 1229 0 0 0 0 0 xen-dyn-event pciback
1698: 6195 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1699: 561 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1700: 102284 0 0 0 0 0 xen-dyn-event vif8.0
1701: 3355 0 0 0 0 0 xen-dyn-event blkif-backend
1702: 25 0 0 0 0 0 xen-dyn-event blkif-backend
1703: 330 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1704: 370 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1705: 97 0 0 0 0 0 xen-dyn-event vif7.0
1706: 1002 0 0 0 0 0 xen-dyn-event blkif-backend
1707: 19 0 0 0 0 0 xen-dyn-event blkif-backend
1708: 1196 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1709: 483 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1710: 90 0 0 0 0 0 xen-dyn-event vif6.0
1711: 933 0 0 0 0 0 xen-dyn-event blkif-backend
1712: 19 0 0 0 0 0 xen-dyn-event blkif-backend
1713: 303605 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1714: 475 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1715: 89 0 0 0 0 0 xen-dyn-event vif5.0
1716: 1013 0 0 0 0 0 xen-dyn-event blkif-backend
1717: 19 0 0 0 0 0 xen-dyn-event blkif-backend
1718: 1178 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1719: 515 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1720: 110 0 0 0 0 0 xen-dyn-event vif4.0
1721: 1353 0 0 0 0 0 xen-dyn-event blkif-backend
1722: 23 0 0 0 0 0 xen-dyn-event blkif-backend
1723: 485697 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1724: 534 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1725: 798 0 0 0 0 0 xen-dyn-event vif3.0
1726: 1436 0 0 0 0 0 xen-dyn-event blkif-backend
1727: 19 0 0 0 0 0 xen-dyn-event blkif-backend
1728: 1221 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1729: 470 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1730: 32 0 0 0 0 0 xen-dyn-event vif2.0
1731: 896 0 0 0 0 0 xen-dyn-event blkif-backend
1732: 19 0 0 0 0 0 xen-dyn-event blkif-backend
1733: 1222 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1734: 552 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1735: 49824 0 0 0 0 0 xen-dyn-event vif1.0
1736: 21876 0 0 0 0 0 xen-dyn-event blkif-backend
1737: 19 0 0 0 0 0 xen-dyn-event blkif-backend
1738: 1207 0 0 0 0 0 xen-dyn-event evtchn:xenconsoled
1739: 574 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1740: 0 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1741: 24189 0 0 0 0 0 xen-dyn-event evtchn:xenstored
1742: 105434 0 0 0 0 0 xen-pirq-msi eth1
1743: 96181 0 0 0 0 0 xen-pirq-msi eth0
1744: 160807 0 0 0 0 0 xen-pirq-msi ahci
1754: 0 0 0 0 0 0 xen-percpu-virq pcpu
1755: 19802 0 0 0 0 0 xen-dyn-event xenbus
1756: 0 0 0 0 0 20796 xen-percpu-ipi callfuncsingle5
1757: 0 0 0 0 0 1 xen-percpu-virq debug5
1758: 0 0 0 0 0 2039 xen-percpu-ipi callfunc5
1759: 0 0 0 0 0 349384 xen-percpu-ipi resched5
1760: 0 0 0 0 0 4507 xen-percpu-ipi spinlock5
1761: 0 0 0 0 0 194053 xen-percpu-virq timer5
1762: 0 0 0 0 21654 0 xen-percpu-ipi callfuncsingle4
1763: 0 0 0 0 1 0 xen-percpu-virq debug4
1764: 0 0 0 0 848 0 xen-percpu-ipi callfunc4
1765: 0 0 0 0 359448 0 xen-percpu-ipi resched4
1766: 0 0 0 0 5251 0 xen-percpu-ipi spinlock4
1767: 0 0 0 0 196034 0 xen-percpu-virq timer4
1768: 0 0 0 19491 0 0 xen-percpu-ipi callfuncsingle3
1769: 0 0 0 1 0 0 xen-percpu-virq debug3
1770: 0 0 0 910 0 0 xen-percpu-ipi callfunc3
1771: 0 0 0 344749 0 0 xen-percpu-ipi resched3
1772: 0 0 0 5897 0 0 xen-percpu-ipi spinlock3
1773: 0 0 0 176171 0 0 xen-percpu-virq timer3
1774: 0 0 21564 0 0 0 xen-percpu-ipi callfuncsingle2
1775: 0 0 1 0 0 0 xen-percpu-virq debug2
1776: 0 0 1966 0 0 0 xen-percpu-ipi callfunc2
1777: 0 0 358938 0 0 0 xen-percpu-ipi resched2
1778: 0 0 6170 0 0 0 xen-percpu-ipi spinlock2
1779: 0 0 292240 0 0 0 xen-percpu-virq timer2
1780: 0 37167 0 0 0 0 xen-percpu-ipi callfuncsingle1
1781: 0 1 0 0 0 0 xen-percpu-virq debug1
1782: 0 833 0 0 0 0 xen-percpu-ipi callfunc1
1783: 0 373321 0 0 0 0 xen-percpu-ipi resched1
1784: 0 7151 0 0 0 0 xen-percpu-ipi spinlock1
1785: 0 425274 0 0 0 0 xen-percpu-virq timer1
1786: 1705 0 0 0 0 0 xen-percpu-ipi callfuncsingle0
1787: 1 0 0 0 0 0 xen-percpu-virq debug0
1788: 893 0 0 0 0 0 xen-percpu-ipi callfunc0
1789: 210449 0 0 0 0 0 xen-percpu-ipi resched0
1790: 7444 0 0 0 0 0 xen-percpu-ipi spinlock0
1791: 740630 0 0 0 0 0 xen-percpu-virq timer0
NMI: 0 0 0 0 0 0 Non-maskable interrupts
LOC: 0 0 0 0 0 0 Local timer interrupts
SPU: 0 0 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 0 0 Performance monitoring interrupts
PND: 0 0 0 0 0 0 Performance pending work
RES: 210449 373321 358938 344749 359448 349384 Rescheduling interrupts
CAL: 2598 38000 23530 20401 22502 22835 Function call interrupts
TLB: 0 0 0 0 0 0 TLB shootdowns
TRM: 0 0 0 0 0 0 Thermal event interrupts
MCE: 0 0 0 0 0 0 Machine check exceptions
MCP: 11 11 11 11 11 11 Machine check polls
ERR: 0
MIS: 0
[-- Attachment #7: qemu-dm-winhvm.log --]
[-- Type: application/octet-stream, Size: 4622 bytes --]
domid: 14
config qemu network with xen bridge for tap14.0 xen_bridge
Using file /mnt/xen_images/domains/expirimental/winhvm/disk.img in read-write mode
Watching /local/domain/0/device-model/14/logdirty/cmd
Watching /local/domain/0/device-model/14/command
Watching /local/domain/14/cpu
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 1eac8e6a-d214-5b20-b62a-a88d6f01b3d9
Time offset set 0
pcilib: Cannot open /sys/bus/pci/devices/0000:00:1f.0/config
pcilib: Cannot open /sys/bus/pci/devices/0000:00:1f.0/config
pcilib: Cannot open /sys/bus/pci/devices/0000:00:1f.0/config
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/14/xen_extended_power_mgmt): read error
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
vcpu-set: watch node error.
xs_read(/local/domain/14/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/14/log-throttling'
medium change watch on `/local/domain/14/log-throttling' - unknown device, ignored
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 05:00.0 ...
register_real_device: Disable MSI translation via per device option
register_real_device: Disable power management
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x5:0x0.0x0
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xb000000c)
pt_register_regions: IO region registered (size=0x00010000 base_addr=0xf9be0004)
pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000b001)
pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xf9bc0000)
pci_intx: intx=1
register_real_device: Real physical device 05:00.0 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 05:00.1 ...
register_real_device: Disable MSI translation via per device option
register_real_device: Disable power management
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x5:0x0.0x1
pt_register_regions: IO region registered (size=0x00004000 base_addr=0xf9bfc004)
pci_intx: intx=2
register_real_device: Real physical device 05:00.1 registered successfuly!
IRQ type = INTx
char device redirected to /dev/pts/14
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
pt_iomem_map: e_phys=e0000000 maddr=b0000000 type=8 len=268435456 index=0 first_map=1
pt_iomem_map: e_phys=f1020000 maddr=f9be0000 type=0 len=65536 index=2 first_map=1
pt_iomem_map: e_phys=f1030000 maddr=f9bfc000 type=0 len=16384 index=0 first_map=1
pt_ioport_map: e_phys=c200 pio_base=b000 len=256 index=4 first_map=1
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
pt_iomem_map: e_phys=ffffffff maddr=b0000000 type=8 len=268435456 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=f9be0000 type=0 len=65536 index=2 first_map=0
pt_iomem_map: e_phys=e0000000 maddr=b0000000 type=8 len=268435456 index=0 first_map=0
pt_iomem_map: e_phys=f1020000 maddr=f9be0000 type=0 len=65536 index=2 first_map=0
pt_ioport_map: e_phys=c200 pio_base=b000 len=256 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=f9bfc000 type=0 len=16384 index=0 first_map=0
pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.1][Offset:30h][Length:4]
pt_iomem_map: e_phys=f1030000 maddr=f9bfc000 type=0 len=16384 index=0 first_map=0
[-- Attachment #8: winhvm.cfg --]
[-- Type: application/octet-stream, Size: 14274 bytes --]
# -*- mode: python; -*-
#============================================================================
# Python configuration setup for 'xm create'.
# This script sets the parameters used when a domain is created using 'xm create'.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#============================================================================
import os, re
arch_libdir = 'lib'
arch = os.uname()[4]
if os.uname()[0] == 'Linux' and re.search('64', arch):
arch_libdir = 'lib64'
#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/usr/lib/xen/boot/hvmloader"
# The domain build function. HVM domain uses 'hvm'.
builder='hvm'
# Initial memory allocation (in megabytes) for the new domain.
#
# WARNING: Creating a domain with insufficient memory may cause out of
# memory errors. The domain needs enough memory to boot kernel
# and modules. Allocating less than 32MBs is not recommended.
memory = 512
# Shadow pagetable memory for the domain, in MB.
# If not explicictly set, xend will pick an appropriate value.
# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
# shadow_memory = 8
# A name for your domain. All domains must have different names.
name = "winhvm"
# 128-bit UUID for the domain. The default behavior is to generate a new UUID
# on each call to 'xm create'.
#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"
#-----------------------------------------------------------------------------
# The number of cpus guest platform has, default=1
#vcpus=1
# Enable/disable HVM guest PAE, default=1 (enabled)
#pae=1
# Enable/disable HVM guest ACPI, default=1 (enabled)
#acpi=1
# Enable/disable HVM APIC mode, default=1 (enabled)
# Note that this option is ignored if vcpus > 1
#apic=1
# Enable/disable extended power management support within HVM guest, i.e., beyond
# S3, S4, S5 within guest like exposing battery meter.
# 0 (default option, extended power management support disabled)
# 1 (pass-through mode; uses pass-through as needed; efficient but limited in scope)
# 2 (non pass-through mode; extended scope, likely to work on all applicable environment
# but comparitively less efficient than pass-through mode)
# xen_extended_power_mgmt=0
# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # all vcpus run on cpus 0,2,3,5
#cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci' ]
# type=ioemu specify the NIC is an ioemu device not netfront
vif = [ 'type=ioemu, bridge=xen_bridge' ]
#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
#disk = [ 'phy:hda1,hda1,r' ]
disk = [ 'file:/mnt/xen_images/domains/expirimental/winhvm/disk.img,hda,w' ]
#----------------------------------------------------------------------------
# Configure the behaviour when a domain exits. There are three 'reasons'
# for a domain to stop: poweroff, reboot, and crash. For each of these you
# may specify:
#
# "destroy", meaning that the domain is cleaned up as normal;
# "restart", meaning that a new domain is started in place of the old
# one;
# "preserve", meaning that no clean-up is done until the domain is
# manually destroyed (using xm destroy, for example); or
# "rename-restart", meaning that the old domain is not cleaned up, but is
# renamed and a new domain started in its place.
#
# In the event a domain stops due to a crash, you have the additional options:
#
# "coredump-destroy", meaning dump the crashed domain's core and then destroy;
# "coredump-restart', meaning dump the crashed domain's core and the restart.
#
# The default is
#
# on_poweroff = 'destroy'
# on_reboot = 'restart'
# on_crash = 'restart'
#
# For backwards compatibility we also support the deprecated option restart
#
# restart = 'onreboot' means on_poweroff = 'destroy'
# on_reboot = 'restart'
# on_crash = 'destroy'
#
# restart = 'always' means on_poweroff = 'restart'
# on_reboot = 'restart'
# on_crash = 'restart'
#
# restart = 'never' means on_poweroff = 'destroy'
# on_reboot = 'destroy'
# on_crash = 'destroy'
#on_poweroff = 'destroy'
#on_reboot = 'restart'
#on_crash = 'restart'
#============================================================================
# Device Model to be used
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
#boot="cda"
boot="c"
#-----------------------------------------------------------------------------
# write to temporary files instead of disk image files
#snapshot=1
#----------------------------------------------------------------------------
# enable SDL library for graphics, default = 0
sdl=0
#----------------------------------------------------------------------------
# enable OpenGL for texture rendering inside the SDL window, default = 1
# valid only if sdl is enabled.
opengl=0
#----------------------------------------------------------------------------
# enable VNC library for graphics, default = 1
vnc=0
#----------------------------------------------------------------------------
# address that should be listened on for the VNC server if vnc is set.
# default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp
vnclisten="172.16.1.1"
#----------------------------------------------------------------------------
# set VNC display number, default = domid
vncdisplay=1
#----------------------------------------------------------------------------
# try to find an unused port for the VNC server, default = 1
vncunused=1
#----------------------------------------------------------------------------
# set password for domain's VNC console
# default is depents on vncpasswd in xend-config.sxp
vncpasswd=''
#----------------------------------------------------------------------------
# no graphics, use serial port
#nographic=0
#----------------------------------------------------------------------------
# enable stdvga, default = 0 (use cirrus logic device model)
stdvga=1
#-----------------------------------------------------------------------------
# serial port re-direct to pty deivce, /dev/pts/n
# then xm console or minicom can connect
#serial='pty'
#-----------------------------------------------------------------------------
# Qemu Monitor, default is disable
# Use ctrl-alt-2 to connect
#monitor=1
#-----------------------------------------------------------------------------
# enable sound card support, [sb16|es1370|all|..,..], default none
#soundhw='sb16'
#-----------------------------------------------------------------------------
# set the real time clock to local time [default=0 i.e. set to utc]
#localtime=1
#-----------------------------------------------------------------------------
# set the real time clock offset in seconds [default=0 i.e. same as dom0]
#rtc_timeoffset=3600
#-----------------------------------------------------------------------------
# start in full screen
#full-screen=1
#-----------------------------------------------------------------------------
# Enable USB support (specific devices specified at runtime through the
# monitor window)
#usb=1
# Enable USB mouse support (only enable one of the following, `mouse' for
# PS/2 protocol relative mouse, `tablet' for
# absolute mouse)
#usbdevice='mouse'
usbdevice='tablet'
#-----------------------------------------------------------------------------
# Set keyboard layout, default is en-us keyboard.
#keymap='ja'
#-----------------------------------------------------------------------------
# Enable/disable xen platform PCI device, default=1 (enabled)
#xen_platform_pci=1
#-----------------------------------------------------------------------------
# Configure guest CPUID responses:
#
#cpuid=[ '1:ecx=xxxxxxxxxxx00xxxxxxxxxxxxxxxxxxx,
# eax=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' ]
# - Unset the SSE4 features (CPUID.1[ECX][20-19])
# - Default behaviour for all other bits in ECX And EAX registers.
#
# Each successive character represent a lesser-significant bit:
# '1' -> force the corresponding bit to 1
# '0' -> force to 0
# 'x' -> Get a safe value (pass through and mask with the default policy)
# 'k' -> pass through the host bit value
# 's' -> as 'k' but preserve across save/restore and migration
#
# Expose to the guest multi-core cpu instead of multiple processors
# Example for intel, expose a 8-core processor :
#cpuid=['1:edx=xxx1xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
# ebx=xxxxxxxx00010000xxxxxxxxxxxxxxxx',
# '4,0:eax=001111xxxxxxxxxxxxxxxxxxxxxxxxxx']
# - CPUID.1[EDX][HT] : Enable HT
# - CPUID.1[EBX] : Number of vcpus * 2
# - CPUID.4,0[EAX] : Number of vcpus * 2 - 1
#vcpus=8
#
# Example for amd, expose a 5-core processor :
# cpuid = ['1:ebx=xxxxxxxx00001010xxxxxxxxxxxxxxxx,
# edx=xxx1xxxxxxxxxxxxxxxxxxxxxxxxxxxx',
# '0x80000001:ecx=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx1x',
# '0x80000008:ecx=xxxxxxxxxxxxxxxxxxxxxxxxxx001001']
# - CPUID.1[EBX] : Threads per Core * Cores per Socket (2 * #vcpus)
# - CPUID.1[EDX][HT] : Enable HT
# - CPUID.0x80000001[CmpLegacy] : Use legacy method
# - CPUID.0x80000008[ECX] : #vcpus * 2 - 1
#vcpus=5
#
# Downgrade the cpuid to make a better compatibility for migration :
# Look like a generic 686 :
# cpuid = [ '0:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0',
# '1:eax=0x06b1,
# ecx=xxxxxxxxxxx0000xx00xxx0000000xx0,
# edx=xxx00000xxxxxxx0xxxxxxxxx0xxxxxx',
# '4:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0',
# '0x80000000:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0']
# with the highest leaf
# - CPUID.0[EAX] : Set the highest leaf
# - CPUID.1[EAX] : 686
# - CPUID.1[ECX] : Mask some features
# - CPUID.1[EDX] : Mask some features
# - CPUID.4 : Reply like the highest leaf, in our case CPUID.3
# - CPUID.0x80000000 : No extension we are on a Pentium III, reply like the
# highest leaf (CPUID.3).
#
# Configure host CPUID consistency checks, which must be satisfied for this
# VM to be allowed to run on this host's processor type:
#cpuid_check=[ '1:ecx=xxxxxxxxxxxxxxxxxxxxxxxxxx1xxxxx' ]
# - Host must have VMX feature flag set
#
# The format is similar to the above for 'cpuid':
# '1' -> the bit must be '1'
# '0' -> the bit must be '0'
# 'x' -> we don't care (do not check)
# 's' -> the bit must be the same as on the host that started this VM
#-----------------------------------------------------------------------------
# Configure passthrough PCI{,-X,e} devices:
#
# pci=[ '[SSSS:]BB:DD.F[,option1[,option2[...]]]', ... ]
#
# [SSSS]:BB:DD.F "bus segment:bus:device.function"(1) of the device to
# be assigned, bus segment is optional. All fields are
# in hexadecimal and no field should be longer than that
# as shown in the pattern. Successful assignment may need
# certain hardware support and additional configurations
# (e.g. VT-d, see docs/misc/vtd.txt for more details).
#
# (1) bus segment is sometimes also referred to as the PCI "domain",
# not to be confused with Xen domain.
#
#
# optionN per-device options in "key=val" format. Current
# available options are:
# - msitranslate=0|1
# per-device overriden of pci_msitranslate, see below
# - power_mgmt=0|1
# per-device overriden of pci_power_mgmt, see below
#
gfx_passthru=1
pci=['05:00.*']
# MSI-INTx translation for MSI capable devices:
#
# If it's set, Xen will enable MSI for the device that supports it even
# if the guest don't use MSI. In the case, an IO-APIC type interrupt will
# be injected to the guest every time a corresponding MSI message is
# received.
# If the guest enables MSI or MSI-X, the translation is automatically
# turned off.
#
pci_msitranslate=0
# PCI Power Management:
#
# If it's set, the guest OS will be able to program D0-D3hot states of the
# PCI device for the purpose of low power consumption.
#
#pci_power_mgmt=0
#-----------------------------------------------------------------------------
# Configure PVSCSI devices:
#
#vscsi=[ 'PDEV, VDEV' ]
#
# PDEV gives physical SCSI device to be attached to specified guest
# domain by one of the following identifier format.
# - XX:XX:XX:XX (4-tuples with decimal notation which shows
# "host:channel:target:lun")
# - /dev/sdxx or sdx
# - /dev/stxx or stx
# - /dev/sgxx or sgx
# - result of 'scsi_id -gu -s'.
# ex. # scsi_id -gu -s /block/sdb
# 36000b5d0006a0000006a0257004c0000
#
# VDEV gives virtual SCSI device by 4-tuples (XX:XX:XX:XX) as
# which the specified guest domain recognize.
#
#vscsi = [ '/dev/sdx, 0:0:0:0' ]
[-- Attachment #9: xend.log --]
[-- Type: application/octet-stream, Size: 16533 bytes --]
[2010-12-12 19:29:25 7983] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'winhvm'], ['memory', 512], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', 1], ['oos', 1], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['videoram', 4], ['acpi', 1], ['apic', 1], ['boot', 'c'], ['cpuid', []], ['cpuid_check', []], ['device_model', '/usr/lib64/xen/bin/qemu-dm'], ['fda', ''], ['fdb', ''], ['gfx_passthru', 1], ['guest_os_type', 'default'], ['hap', 1], ['hpet', 0], ['isa', 0], ['keymap', ''], ['localtime', 0], ['nographic', 0], ['opengl', 0], ['oos', 1], ['pae', 1], ['pci', [['0x0000', '0x05', '0x00', '0x1', '0x101', [], '05:00.*'], ['0x0000', '0x05', '0x00', '0x0', '0x100', [], '05:00.*']]], ['pci_msitranslate', 0], ['pci_power_mgmt', 0], ['rtc_timeoffset', 0], ['sdl', 0], ['soundhw', ''], ['stdvga', 1], ['timer_mode', 1], ['usb', 0], ['usbdevice', 'tablet'], ['vcpus', 1], ['vnc', 0], ['vncdisplay', 1], ['vnclisten', '172.16.1.1'], ['vncunused', 1], ['viridian', 0], ['vpt_align', 1], ['xauthority', '/root/.Xauthority'], ['xen_platform_pci', 1], ['memory_sharing', 0], ['vncpasswd', 'XXXXXXXX'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'file:/mnt/xen_images/domains/expirimental/winhvm/disk.img'], ['dev', 'hda'], ['mode', 'w']]], ['device', ['pci', ['dev', ['slot', '0x00'], ['domain', '0x0000'], ['key', '05:00.*'], ['bus', '0x05'], ['vdevfn', '0x101'], ['func', '0x1']], ['dev', ['slot', '0x00'], ['domain', '0x0000'], ['key', '05:00.*'], ['bus', '0x05'], ['vdevfn', '0x100'], ['func', '0x0']]]], ['device', ['vif', ['bridge', 'xen_bridge'], ['type', 'ioemu']]]])
[2010-12-12 19:29:25 7983] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain
[2010-12-12 19:29:25 7983] DEBUG (balloon:187) Balloon: 3552480 KiB free; need 16384; done.
[2010-12-12 19:29:27 7983] DEBUG (XendDomain:476) Adding Domain: 14
[2010-12-12 19:29:27 7983] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 14 256
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: boot, val: c
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: fda, val: None
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: fdb, val: None
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: soundhw, val: None
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: localtime, val: 0
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: serial, val: None
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: std-vga, val: 1
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: isa, val: 0
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: acpi, val: 1
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: usb, val: 0
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: usbdevice, val: tablet
[2010-12-12 19:29:27 7983] DEBUG (image:891) args: gfx_passthru, val: 1
[2010-12-12 19:29:27 7983] INFO (image:822) Need to create platform device.[domid:14]
[2010-12-12 19:29:27 7983] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x20000000, memory_static_min=0x0.
[2010-12-12 19:29:27 7983] INFO (image:182) buildDomain os=hvm dom=14 vcpus=1
[2010-12-12 19:29:27 7983] DEBUG (image:949) domid = 14
[2010-12-12 19:29:27 7983] DEBUG (image:950) image = /usr/lib/xen/boot/hvmloader
[2010-12-12 19:29:27 7983] DEBUG (image:951) store_evtchn = 2
[2010-12-12 19:29:27 7983] DEBUG (image:952) memsize = 512
[2010-12-12 19:29:27 7983] DEBUG (image:953) target = 512
[2010-12-12 19:29:27 7983] DEBUG (image:954) vcpus = 1
[2010-12-12 19:29:27 7983] DEBUG (image:955) vcpu_avail = 1
[2010-12-12 19:29:27 7983] DEBUG (image:956) acpi = 1
[2010-12-12 19:29:27 7983] DEBUG (image:957) apic = 1
[2010-12-12 19:29:27 7983] INFO (XendDomainInfo:2357) createDevice: vbd : {'uuid': '14cd5a6b-4d69-8743-6377-02f1c666009b', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname': 'file:/mnt/xen_images/domains/expirimental/winhvm/disk.img', 'mode': 'w'}
[2010-12-12 19:29:27 7983] DEBUG (DevController:95) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/14/768'} to /local/domain/14/device/vbd/768.
[2010-12-12 19:29:27 7983] DEBUG (DevController:97) DevController: writing {'domain': 'winhvm', 'frontend': '/local/domain/14/device/vbd/768', 'uuid': '14cd5a6b-4d69-8743-6377-02f1c666009b', 'bootable': '1', 'dev': 'hda', 'state': '1', 'params': '/mnt/xen_images/domains/expirimental/winhvm/disk.img', 'mode': 'w', 'online': '1', 'frontend-id': '14', 'type': 'file'} to /local/domain/0/backend/vbd/14/768.
[2010-12-12 19:29:27 7983] INFO (XendDomainInfo:2357) createDevice: vif : {'bridge': 'xen_bridge', 'mac': '00:16:3e:15:46:77', 'type': 'ioemu', 'uuid': '5117cd83-38e3-68d1-0423-2dcab9dae57a'}
[2010-12-12 19:29:27 7983] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/14/0'} to /local/domain/14/device/vif/0.
[2010-12-12 19:29:27 7983] DEBUG (DevController:97) DevController: writing {'bridge': 'xen_bridge', 'domain': 'winhvm', 'handle': '0', 'uuid': '5117cd83-38e3-68d1-0423-2dcab9dae57a', 'script': '/etc/xen/scripts/vif-bridge', 'mac': '00:16:3e:15:46:77', 'frontend-id': '14', 'state': '1', 'online': '1', 'frontend': '/local/domain/14/device/vif/0', 'type': 'ioemu'} to /local/domain/0/backend/vif/14/0.
[2010-12-12 19:29:28 7983] INFO (XendDomainInfo:2357) createDevice: pci : {'devs': [{'slot': '0x00', 'domain': '0x0000', 'key': '05:00.*', 'bus': '0x05', 'vdevfn': '0x101', 'func': '0x1', 'uuid': '9324997b-ba66-c4a9-2701-2699ca06e96a'}, {'slot': '0x00', 'domain': '0x0000', 'key': '05:00.*', 'bus': '0x05', 'vdevfn': '0x100', 'func': '0x0', 'uuid': 'fbc09890-070f-5420-e70f-3d0d565bd865'}], 'uuid': 'c46f96d9-719f-9c82-a335-dcbe814139cc'}
[2010-12-12 19:29:31 7983] INFO (image:418) spawning device models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '-d', '14', '-domain-name', 'winhvm', '-videoram', '4', '-nographic', '-vcpus', '1', '-vcpu_avail', '0x1', '-boot', 'c', '-std-vga', '-acpi', '-usbdevice', 'tablet', '-gfx_passthru', '1', '-net', 'nic,vlan=1,macaddr=00:16:3e:15:46:77,model=rtl8139', '-net', 'tap,vlan=1,ifname=tap14.0,bridge=xen_bridge', '-M', 'xenfv']
[2010-12-12 19:29:31 7983] INFO (image:467) device model pid: 17739
[2010-12-12 19:29:31 7983] INFO (image:590) waiting for sentinel_fifo
[2010-12-12 19:29:31 7983] DEBUG (XendDomainInfo:893) XendDomainInfo.pci_device_configure: ['pci', ['dev', ['slot', '0x00'], ['domain', '0x0000'], ['key', '05:00.*'], ['bus', '0x05'], ['vdevfn', '0x100'], ['func', '0x0'], ['uuid', 'fbc09890-070f-5420-e70f-3d0d565bd865']], ['state', 'Initialising'], ['sub_state', 'Booting']]
[2010-12-12 19:29:32 7983] DEBUG (XendDomainInfo:779) XendDomainInfo.hvm_pci_device_insert: {'devs': [{'slot': '0x00', 'domain': '0x0000', 'key': '05:00.*', 'bus': '0x05', 'vdevfn': '0x100', 'func': '0x0', 'uuid': 'fbc09890-070f-5420-e70f-3d0d565bd865'}], 'states': ['Initialising']}
[2010-12-12 19:29:32 7983] DEBUG (XendDomainInfo:790) XendDomainInfo.hvm_pci_device_insert_dev: {'slot': '0x00', 'domain': '0x0000', 'key': '05:00.*', 'bus': '0x05', 'vdevfn': '0x100', 'func': '0x0', 'uuid': 'fbc09890-070f-5420-e70f-3d0d565bd865'}
[2010-12-12 19:29:32 7983] DEBUG (XendDomainInfo:811) XendDomainInfo.hvm_pci_device_insert_dev: 0000:05:00.0@100,msitranslate=0,power_mgmt=0
[2010-12-12 19:29:32 7983] DEBUG (XendDomainInfo:815) pci: assign device 0000:05:00.0@100,msitranslate=0,power_mgmt=0
[2010-12-12 19:29:32 7983] DEBUG (image:508) signalDeviceModel: orig_state is None, retrying
[2010-12-12 19:29:32 7983] INFO (image:538) signalDeviceModel:restore dm state to running
[2010-12-12 19:29:32 7983] INFO (pciquirk:92) NO quirks found for PCI device [1002:aa28:1043:aa28]
[2010-12-12 19:29:32 7983] DEBUG (pciquirk:132) Permissive mode enabled for PCI device [1002:aa28:1043:aa28]
[2010-12-12 19:29:32 7983] DEBUG (pciquirk:141) Unconstrained device: 0000:05:00.1
[2010-12-12 19:29:32 7983] DEBUG (pciif:334) pci: enabling iomem 0xf9bfc000/0x4000 pfn 0xf9bfc/0x4
[2010-12-12 19:29:32 7983] DEBUG (pciif:351) pci: enabling irq 33
[2010-12-12 19:29:32 7983] INFO (pciquirk:92) NO quirks found for PCI device [1002:95c5:1043:01d4]
[2010-12-12 19:29:32 7983] DEBUG (pciquirk:132) Permissive mode enabled for PCI device [1002:95c5:1043:01d4]
[2010-12-12 19:29:32 7983] DEBUG (pciquirk:141) Unconstrained device: 0000:05:00.0
[2010-12-12 19:29:32 7983] DEBUG (pciif:320) pci: enabling ioport 0xb000/0x100
[2010-12-12 19:29:32 7983] DEBUG (pciif:334) pci: enabling iomem 0xb0000000/0x10000000 pfn 0xb0000/0x10000
[2010-12-12 19:29:32 7983] DEBUG (pciif:334) pci: enabling iomem 0xf9be0000/0x10000 pfn 0xf9be0/0x10
[2010-12-12 19:29:32 7983] DEBUG (pciif:334) pci: enabling iomem 0xf9bc0000/0x20000 pfn 0xf9bc0/0x20
[2010-12-12 19:29:32 7983] DEBUG (pciif:351) pci: enabling irq 32
[2010-12-12 19:29:32 7983] DEBUG (pciif:456) pci: register aer watch /local/domain/0/backend/pci/14/0/aerState
[2010-12-12 19:29:32 7983] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/pci/14/0'} to /local/domain/14/device/pci/0.
[2010-12-12 19:29:32 7983] DEBUG (DevController:97) DevController: writing {'key-1': '05:00.*', 'key-0': '05:00.*', 'vdevfn-0': '101', 'vdevfn-1': '100', 'frontend-id': '14', 'dev-1': '0000:05:00.0', 'dev-0': '0000:05:00.1', 'domain': 'winhvm', 'opts-0': 'msitranslate=0,power_mgmt=0', 'state': '1', 'online': '1', 'frontend': '/local/domain/14/device/pci/0', 'num_devs': '2', 'uuid-0': '9324997b-ba66-c4a9-2701-2699ca06e96a', 'uuid-1': 'fbc09890-070f-5420-e70f-3d0d565bd865', 'opts-1': 'msitranslate=0,power_mgmt=0', 'uuid': 'c46f96d9-719f-9c82-a335-dcbe814139cc'} to /local/domain/0/backend/pci/14/0.
[2010-12-12 19:29:33 7983] DEBUG (pciif:169) Reconfiguring PCI device 0000:05:00.0.
[2010-12-12 19:29:33 7983] INFO (pciquirk:92) NO quirks found for PCI device [1002:95c5:1043:01d4]
[2010-12-12 19:29:33 7983] DEBUG (pciquirk:132) Permissive mode enabled for PCI device [1002:95c5:1043:01d4]
[2010-12-12 19:29:33 7983] DEBUG (pciquirk:141) Unconstrained device: 0000:05:00.0
[2010-12-12 19:29:33 7983] DEBUG (pciif:320) pci: enabling ioport 0xb000/0x100
[2010-12-12 19:29:33 7983] DEBUG (pciif:334) pci: enabling iomem 0xb0000000/0x10000000 pfn 0xb0000/0x10000
[2010-12-12 19:29:33 7983] DEBUG (pciif:334) pci: enabling iomem 0xf9be0000/0x10000 pfn 0xf9be0/0x10
[2010-12-12 19:29:33 7983] DEBUG (pciif:334) pci: enabling iomem 0xf9bc0000/0x20000 pfn 0xf9bc0/0x20
[2010-12-12 19:29:33 7983] DEBUG (pciif:351) pci: enabling irq 32
[2010-12-12 19:29:34 7983] DEBUG (XendDomainInfo:893) XendDomainInfo.pci_device_configure: ['pci', ['dev', ['slot', '0x00'], ['domain', '0x0000'], ['key', '05:00.*'], ['bus', '0x05'], ['vdevfn', '0x29'], ['func', '0x1'], ['uuid', '9324997b-ba66-c4a9-2701-2699ca06e96a']], ['state', 'Initialising'], ['sub_state', 'Booting']]
[2010-12-12 19:29:34 7983] DEBUG (XendDomainInfo:779) XendDomainInfo.hvm_pci_device_insert: {'devs': [{'slot': '0x00', 'domain': '0x0000', 'key': '05:00.*', 'bus': '0x05', 'vdevfn': '0x29', 'func': '0x1', 'uuid': '9324997b-ba66-c4a9-2701-2699ca06e96a'}], 'states': ['Initialising']}
[2010-12-12 19:29:34 7983] DEBUG (XendDomainInfo:790) XendDomainInfo.hvm_pci_device_insert_dev: {'slot': '0x00', 'domain': '0x0000', 'key': '05:00.*', 'bus': '0x05', 'vdevfn': '0x29', 'func': '0x1', 'uuid': '9324997b-ba66-c4a9-2701-2699ca06e96a'}
[2010-12-12 19:29:34 7983] DEBUG (XendDomainInfo:811) XendDomainInfo.hvm_pci_device_insert_dev: 0000:05:00.1@29,msitranslate=0,power_mgmt=0
[2010-12-12 19:29:34 7983] DEBUG (XendDomainInfo:815) pci: assign device 0000:05:00.1@29,msitranslate=0,power_mgmt=0
[2010-12-12 19:29:34 7983] INFO (image:538) signalDeviceModel:restore dm state to running
[2010-12-12 19:29:34 7983] DEBUG (pciif:169) Reconfiguring PCI device 0000:05:00.1.
[2010-12-12 19:29:34 7983] INFO (pciquirk:92) NO quirks found for PCI device [1002:aa28:1043:aa28]
[2010-12-12 19:29:34 7983] DEBUG (pciquirk:132) Permissive mode enabled for PCI device [1002:aa28:1043:aa28]
[2010-12-12 19:29:35 7983] DEBUG (pciquirk:141) Unconstrained device: 0000:05:00.1
[2010-12-12 19:29:35 7983] DEBUG (pciif:334) pci: enabling iomem 0xf9bfc000/0x4000 pfn 0xf9bfc/0x4
[2010-12-12 19:29:35 7983] DEBUG (pciif:351) pci: enabling irq 33
[2010-12-12 19:29:35 7983] DEBUG (XendDomainInfo:3421) Storing VM details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', 'shadow_memory': '5', 'uuid': '1eac8e6a-d214-5b20-b62a-a88d6f01b3d9', 'on_reboot': 'restart', 'start_time': '1292178575.78', 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'bootloader': '', 'image': "(hvm (kernel '') (superpages 0) (tsc_mode 0) (videoram 4) (hpet 0) (boot c) (vnclisten 172.16.1.1) (loader /usr/lib/xen/boot/hvmloader) (vpt_align 1) (xen_platform_pci 1) (opengl 0) (vncunused 1) (rtc_timeoffset 0) (pci ((0x0000 0x05 0x00 0x1 0x101 ()) (0x0000 0x05 0x00 0x0 0x100 ()))) (pae 1) (stdvga 1) (hap 1) (viridian 0) (acpi 1) (localtime 0) (timer_mode 1) (vnc 0) (nographic 0) (guest_os_type default) (vncdisplay 1) (pci_msitranslate 0) (oos 1) (apic 1) (sdl 0) (nomigrate 0) (usbdevice tablet) (device_model /usr/lib64/xen/bin/qemu-dm) (gfx_passthru 1) (pci_power_mgmt 0) (usb 0) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)))", 'name': 'winhvm'}
[2010-12-12 19:29:35 7983] DEBUG (XendDomainInfo:1794) Storing domain details: {'console/port': '3', 'description': '', 'console/limit': '1048576', 'store/port': '2', 'vm': '/vm/1eac8e6a-d214-5b20-b62a-a88d6f01b3d9', 'domid': '14', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'memory/target': '524288', 'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref': '1044476', 'console/type': 'ioemu', 'name': 'winhvm'}
[2010-12-12 19:29:37 7983] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/14/0'} to /local/domain/14/device/console/0.
[2010-12-12 19:29:37 7983] DEBUG (DevController:97) DevController: writing {'domain': 'winhvm', 'frontend': '/local/domain/14/device/console/0', 'uuid': '961f18a9-9ddc-1685-e439-070854116406', 'frontend-id': '14', 'state': '1', 'location': '3', 'online': '1', 'protocol': 'vt100'} to /local/domain/0/backend/console/14/0.
[2010-12-12 19:29:37 7983] DEBUG (pciif:460) XendDomainInfo.handleAerStateWatch
[2010-12-12 19:29:37 7983] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShutdownWatch
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices vif2.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices vif.
[2010-12-12 19:29:37 7983] DEBUG (DevController:144) Waiting for 0.
[2010-12-12 19:29:37 7983] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vif/14/0/hotplug-status.
[2010-12-12 19:29:37 7983] DEBUG (DevController:642) hotplugStatusCallback 1.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices vscsi.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices vbd.
[2010-12-12 19:29:37 7983] DEBUG (DevController:144) Waiting for 768.
[2010-12-12 19:29:37 7983] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/14/768/hotplug-status.
[2010-12-12 19:29:37 7983] DEBUG (DevController:642) hotplugStatusCallback 1.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices ioports.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices irq.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices vkbd.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices vfb.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices console.
[2010-12-12 19:29:37 7983] DEBUG (DevController:144) Waiting for 0.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices pci.
[2010-12-12 19:29:37 7983] DEBUG (DevController:144) Waiting for 0.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices tap2.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices tap.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices vusb.
[2010-12-12 19:29:37 7983] DEBUG (DevController:139) Waiting for devices vtpm.
[2010-12-12 19:29:37 7983] INFO (XendDomain:1225) Domain winhvm (14) unpaused.
[-- Attachment #10: xm-dmesg.txt --]
[-- Type: text/plain, Size: 49801 bytes --]
Node 0 PXM 0 100000000-250000000
(XEN) NUMA: Allocated memnodemap from 24df8d000 - 24df90000
(XEN) NUMA: Using 8 for the hash shift.
(XEN) Domain heap initialised
(XEN) vesafb: framebuffer at 0xfb000000, mapped to 0xffff82c000000000, using 6144k, total 14336k
(XEN) vesafb: mode is 1280x1024x32, linelength=5120, font 8x16
(XEN) vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
(XEN) found SMP MP-table at 000ff780
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x808
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
(XEN) ACPI: wakeup_vec[aff9e00c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
(XEN) Processor #4 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
(XEN) Processor #5 0:10 APIC version 16
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) ACPI: HPET id: 0x8300 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
(XEN) PCI: Not using MMCONFIG.
(XEN) Table is not found!
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) mapped APIC to ffff82c3ffffe000 (fee00000)
(XEN) mapped IOAPIC to ffff82c3ffffd000 (fec00000)
(XEN) mapped IOAPIC to ffff82c3ffffc000 (fec20000)
(XEN) IRQ limits: 56 GSI, 1112 MSI/MSI-X
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3200.222 MHz processor.
(XEN) Initing memory sharing.
(XEN) AMD Fam10h machine check reporting enabled
(XEN) AMD-Vi: Found MSI capability block
(XEN) AMD-Vi: ACPI Table:
(XEN) AMD-Vi: Signature IVRS
(XEN) AMD-Vi: Length 0x100
(XEN) AMD-Vi: Revision 0x1
(XEN) AMD-Vi: CheckSum 0x66
(XEN) AMD-Vi: OEM_Id AMD
(XEN) AMD-Vi: OEM_Table_Id RD890S
(XEN) AMD-Vi: OEM_Revision 0x202031
(XEN) AMD-Vi: Creator_Id AMD
(XEN) AMD-Vi: Creator_Revision 0x0
(XEN) AMD-Vi: IVRS Block:
(XEN) AMD-Vi: Type 0x10
(XEN) AMD-Vi: Flags 0x3e
(XEN) AMD-Vi: Length 0xd0
(XEN) AMD-Vi: Dev_Id 0x2
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0x0
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Dev_Id Range: 0x0 -> 0x2
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x10
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xb00
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x18
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0xa00
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Dev_Id Range: 0xa00 -> 0xa07
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x28
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x900
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x30
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x800
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x50
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x600
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x0
(XEN) AMD-Vi: Dev_Id 0x0
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x43
(XEN) AMD-Vi: Dev_Id 0x708
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Dev_Id Range: 0x708 -> 0x7ff
(XEN) AMD-Vi: Dev_Id Alias: 0x700
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x58
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0x500
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Dev_Id Range: 0x500 -> 0x501
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x68
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0x400
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Dev_Id Range: 0x400 -> 0x407
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x88
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0x90
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Dev_Id Range: 0x90 -> 0x92
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0x98
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Dev_Id Range: 0x98 -> 0x9a
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa0
(XEN) AMD-Vi: Flags 0xd7
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa3
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa4
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x0
(XEN) AMD-Vi: Dev_Id 0x0
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x43
(XEN) AMD-Vi: Dev_Id 0x300
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Dev_Id Range: 0x300 -> 0x3ff
(XEN) AMD-Vi: Dev_Id Alias: 0xa4
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa5
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa8
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0xa9
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x2
(XEN) AMD-Vi: Dev_Id 0x100
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x3
(XEN) AMD-Vi: Dev_Id 0xb0
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Dev_Id Range: 0xb0 -> 0xb2
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x0
(XEN) AMD-Vi: Dev_Id 0x0
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x48
(XEN) AMD-Vi: Dev_Id 0x0
(XEN) AMD-Vi: Flags 0xd7
(XEN) AMD-Vi: IVHD Device Entry:
(XEN) AMD-Vi: Type 0x48
(XEN) AMD-Vi: Dev_Id 0x0
(XEN) AMD-Vi: Flags 0x0
(XEN) AMD-Vi: Add device table entry at DTE:0x0, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x1, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x2, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x10, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x18, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x28, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x30, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x50, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x58, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x68, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x88, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x90, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x91, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x92, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x98, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x99, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x9a, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa0, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa3, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa4, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa5, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa8, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa9, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xb0, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xb1, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xb2, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x100, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x400, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x401, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x402, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x403, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x404, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x405, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x406, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x407, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x500, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x501, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x600, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x700, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x800, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0x900, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa00, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa01, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa02, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa03, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa04, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa05, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa06, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xa07, intremap_table:24df4e000
(XEN) AMD-Vi: Add device table entry at DTE:0xb00, intremap_table:24df4e000
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Getting VERSION: 80050010
(XEN) Getting VERSION: 80050010
(XEN) Getting ID: 0
(XEN) Getting LVT0: 700
(XEN) Getting LVT1: 400
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 0x00000004 after: 0x00000000
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) init IO_APIC IRQs
(XEN) IO-APIC (apicid-pin) 6-0, 6-16, 6-17, 6-18, 6-19, 6-20, 6-21, 6-22, 6-23, 7-0, 7-1, 7-2, 7-3, 7-4, 7-5, 7-6, 7-7, 7-8, 7-9, 7-10, 7-11, 7-12, 7-13, 7-14, 7-15, 7-16, 7-17, 7-18, 7-19, 7-20, 7-21, 7-22, 7-23, 7-24, 7-25, 7-26, 7-27, 7-28, 7-29, 7-30, 7-31 not connected.
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #6 registers: 24.
(XEN) number of IO-APIC #7 registers: 32.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #6......
(XEN) .... register #00: 06000000
(XEN) ....... : physical APIC id: 06
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00178021
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0021
(XEN) .... register #02: 06000000
(XEN) ....... : arbitration: 06
(XEN) .... register #03: 07000000
(XEN) ....... : Boot DT : 0
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 001 01 0 0 0 0 0 1 1 30
(XEN) 02 001 01 0 0 0 0 0 1 1 F0
(XEN) 03 001 01 0 0 0 0 0 1 1 38
(XEN) 04 001 01 0 0 0 0 0 1 1 F1
(XEN) 05 001 01 0 0 0 0 0 1 1 40
(XEN) 06 001 01 0 0 0 0 0 1 1 48
(XEN) 07 001 01 0 0 0 0 0 1 1 50
(XEN) 08 001 01 0 0 0 0 0 1 1 58
(XEN) 09 001 01 1 1 0 1 0 1 1 60
(XEN) 0a 001 01 0 0 0 0 0 1 1 68
(XEN) 0b 001 01 0 0 0 0 0 1 1 70
(XEN) 0c 001 01 0 0 0 0 0 1 1 78
(XEN) 0d 001 01 0 0 0 0 0 1 1 88
(XEN) 0e 001 01 0 0 0 0 0 1 1 90
(XEN) 0f 001 01 0 0 0 0 0 1 1 98
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 000 00 1 0 0 0 0 0 0 00
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 000 00 1 0 0 0 0 0 0 00
(XEN) 14 000 00 1 0 0 0 0 0 0 00
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 000 00 1 0 0 0 0 0 0 00
(XEN) IO APIC #7......
(XEN) .... register #00: 07000000
(XEN) ....... : physical APIC id: 07
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 001F8021
(XEN) ....... : max redirection entries: 001F
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0021
(XEN) .... register #02: 00000000
(XEN) ....... : arbitration: 00
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 000 00 1 0 0 0 0 0 0 00
(XEN) 02 000 00 1 0 0 0 0 0 0 00
(XEN) 03 000 00 1 0 0 0 0 0 0 00
(XEN) 04 000 00 1 0 0 0 0 0 0 00
(XEN) 05 000 00 1 0 0 0 0 0 0 00
(XEN) 06 000 00 1 0 0 0 0 0 0 00
(XEN) 07 000 00 1 0 0 0 0 0 0 00
(XEN) 08 000 00 1 0 0 0 0 0 0 00
(XEN) 09 000 00 1 0 0 0 0 0 0 00
(XEN) 0a 000 00 1 0 0 0 0 0 0 00
(XEN) 0b 000 00 1 0 0 0 0 0 0 00
(XEN) 0c 000 00 1 0 0 0 0 0 0 00
(XEN) 0d 000 00 1 0 0 0 0 0 0 00
(XEN) 0e 000 00 1 0 0 0 0 0 0 00
(XEN) 0f 000 00 1 0 0 0 0 0 0 00
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 000 00 1 0 0 0 0 0 0 00
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 000 00 1 0 0 0 0 0 0 00
(XEN) 14 000 00 1 0 0 0 0 0 0 00
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 000 00 1 0 0 0 0 0 0 00
(XEN) 18 000 00 1 0 0 0 0 0 0 00
(XEN) 19 000 00 1 0 0 0 0 0 0 00
(XEN) 1a 000 00 1 0 0 0 0 0 0 00
(XEN) 1b 000 00 1 0 0 0 0 0 0 00
(XEN) 1c 000 00 1 0 0 0 0 0 0 00
(XEN) 1d 000 00 1 0 0 0 0 0 0 00
(XEN) 1e 000 00 1 0 0 0 0 0 0 00
(XEN) 1f 000 00 1 0 0 0 0 0 0 00
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ48 -> 0:1
(XEN) IRQ56 -> 0:3
(XEN) IRQ241 -> 0:4
(XEN) IRQ64 -> 0:5
(XEN) IRQ72 -> 0:6
(XEN) IRQ80 -> 0:7
(XEN) IRQ88 -> 0:8
(XEN) IRQ96 -> 0:9
(XEN) IRQ104 -> 0:10
(XEN) IRQ112 -> 0:11
(XEN) IRQ120 -> 0:12
(XEN) IRQ136 -> 0:13
(XEN) IRQ144 -> 0:14
(XEN) IRQ152 -> 0:15
(XEN) .................................... done.
(XEN) Using local APIC timer interrupts.
(XEN) calibrating APIC timer ...
(XEN) ..... CPU clock speed is 3200.2202 MHz.
(XEN) ..... host bus clock speed is 200.0136 MHz.
(XEN) ..... bus_scale = 0x0000CCD7
(XEN) [2010-12-12 18:10:11] Platform timer is 14.318MHz HPET
(XEN) [2010-12-12 18:10:11] Allocated console ring of 64 KiB.
(XEN) [2010-12-12 18:10:11] HVM: ASIDs enabled.
(XEN) [2010-12-12 18:10:11] HVM: SVM enabled
(XEN) [2010-12-12 18:10:11] HVM: Hardware Assisted Paging detected.
(XEN) [2010-12-12 18:10:10] masked ExtINT on CPU#1
(XEN) [2010-12-12 18:10:10] masked ExtINT on CPU#2
(XEN) [2010-12-12 18:10:10] masked ExtINT on CPU#3
(XEN) [2010-12-12 18:10:10] masked ExtINT on CPU#4
(XEN) [2010-12-12 18:10:10] masked ExtINT on CPU#5
(XEN) [2010-12-12 18:10:12] Brought up 6 CPUs
(XEN) [2010-12-12 18:10:12] tmem: initialized comp=0 dedup=0 tze=0 global-lock=0
(XEN) [2010-12-12 18:10:12] HPET\047s MSI mode hasn\047t been supported when Interrupt Remapping is enabled.
(XEN) [2010-12-12 18:10:12] ACPI sleep modes: S3
(XEN) [2010-12-12 18:10:12] MCA: Use hw thresholding to adjust polling frequency
(XEN) [2010-12-12 18:10:12] mcheck_poll: Machine check polling timer started.
(XEN) [2010-12-12 18:10:12] Xenoprofile: Failed to setup IBS LVT offset, IBSCTL = 0xffffffff
(XEN) [2010-12-12 18:10:12] *** LOADING DOMAIN 0 ***
(XEN) [2010-12-12 18:10:12] elf_parse_binary: phdr: paddr=0x1000000 memsz=0xa79000
(XEN) [2010-12-12 18:10:12] elf_parse_binary: phdr: paddr=0x1a79000 memsz=0xff058
(XEN) [2010-12-12 18:10:12] elf_parse_binary: phdr: paddr=0x1b79000 memsz=0x8c8
(XEN) [2010-12-12 18:10:12] elf_parse_binary: phdr: paddr=0x1b7a000 memsz=0x14558
(XEN) [2010-12-12 18:10:12] elf_parse_binary: phdr: paddr=0x1b8f000 memsz=0x2ab000
(XEN) [2010-12-12 18:10:12] elf_parse_binary: memory: 0x1000000 -> 0x1e3a000
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: GUEST_OS = "linux"
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: ENTRY = 0xffffffff81b8f200
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81009000
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: PAE_MODE = "yes"
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: LOADER = "generic"
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) [2010-12-12 18:10:12] elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) [2010-12-12 18:10:12] elf_xen_addr_calc_check: addresses:
(XEN) [2010-12-12 18:10:12] virt_base = 0xffffffff80000000
(XEN) [2010-12-12 18:10:12] elf_paddr_offset = 0x0
(XEN) [2010-12-12 18:10:12] virt_offset = 0xffffffff80000000
(XEN) [2010-12-12 18:10:12] virt_kstart = 0xffffffff81000000
(XEN) [2010-12-12 18:10:12] virt_kend = 0xffffffff81e3a000
(XEN) [2010-12-12 18:10:12] virt_entry = 0xffffffff81b8f200
(XEN) [2010-12-12 18:10:12] p2m_base = 0xffffffffffffffff
(XEN) [2010-12-12 18:10:12] Xen kernel: 64-bit, lsb, compat32
(XEN) [2010-12-12 18:10:12] Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1e3a000
(XEN) [2010-12-12 18:10:12] PHYSICAL MEMORY ARRANGEMENT:
(XEN) [2010-12-12 18:10:12] Dom0 alloc.: 0000000244000000->0000000248000000 (177973 pages to be allocated)
(XEN) [2010-12-12 18:10:12] Init. ramdisk: 000000024f735000->000000024ffffc00
(XEN) [2010-12-12 18:10:12] VIRTUAL MEMORY ARRANGEMENT:
(XEN) [2010-12-12 18:10:12] Loaded kernel: ffffffff81000000->ffffffff81e3a000
(XEN) [2010-12-12 18:10:12] Init. ramdisk: ffffffff81e3a000->ffffffff82704c00
(XEN) [2010-12-12 18:10:12] Phys-Mach map: ffffffff82705000->ffffffff82885000
(XEN) [2010-12-12 18:10:12] Start info: ffffffff82885000->ffffffff828854b4
(XEN) [2010-12-12 18:10:12] Page tables: ffffffff82886000->ffffffff8289f000
(XEN) [2010-12-12 18:10:12] Boot stack: ffffffff8289f000->ffffffff828a0000
(XEN) [2010-12-12 18:10:12] TOTAL: ffffffff80000000->ffffffff82c00000
(XEN) [2010-12-12 18:10:12] ENTRY ADDRESS: ffffffff81b8f200
(XEN) [2010-12-12 18:10:12] Dom0 has maximum 6 VCPUs
(XEN) [2010-12-12 18:10:12] elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81a79000
(XEN) [2010-12-12 18:10:12] elf_load_binary: phdr 1 at 0xffffffff81a79000 -> 0xffffffff81b78058
(XEN) [2010-12-12 18:10:12] elf_load_binary: phdr 2 at 0xffffffff81b79000 -> 0xffffffff81b798c8
(XEN) [2010-12-12 18:10:12] elf_load_binary: phdr 3 at 0xffffffff81b7a000 -> 0xffffffff81b8e558
(XEN) [2010-12-12 18:10:12] elf_load_binary: phdr 4 at 0xffffffff81b8f000 -> 0xffffffff81c5f000
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x0, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x2, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x10, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x18, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x28, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x30, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x50, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x58, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x68, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x88, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x90, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x92, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x98, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0x9a, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0xa0, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0xa3, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0xa4, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0xa5, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:12] AMD-Vi: Setup I/O page table at DTE:0xa8, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xb0, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xb2, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Fail to find iommu for device00:18.0
(XEN) [2010-12-12 18:10:13] AMD-Vi: Fail to find iommu for device00:18.1
(XEN) [2010-12-12 18:10:13] AMD-Vi: Fail to find iommu for device00:18.2
(XEN) [2010-12-12 18:10:13] AMD-Vi: Fail to find iommu for device00:18.3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Fail to find iommu for device00:18.4
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x400, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x401, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x402, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x403, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x404, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x405, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x406, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x407, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x500, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x501, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x600, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x700, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x800, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0x900, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xa00, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xa01, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xa02, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xa03, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xa04, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xa05, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xa06, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xa07, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] AMD-Vi: Setup I/O page table at DTE:0xb00, root_table:248154000,domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:10:13] Scrubbing Free RAM: .........................................................................done.
(XEN) [2010-12-12 18:10:15] trace.c:90:d32767 calc_tinfo_first_offset: NR_CPUs 128, offset_in_bytes 258, t_info_first_offset 65
(XEN) [2010-12-12 18:10:15] Xen trace buffers: disabled
(XEN) [2010-12-12 18:10:15] Std. Loglevel: All
(XEN) [2010-12-12 18:10:15] Guest Loglevel: All
(XEN) [2010-12-12 18:10:15] Xen is relinquishing VGA console.
(XEN) [2010-12-12 18:10:15] *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch input to Xen)
(XEN) [2010-12-12 18:10:15] Freed 212kB init memory.
(XEN) [2010-12-12 18:10:15] IOAPIC[0]: Set PCI routing entry (6-9 -> 0x60 -> IRQ 9 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:15] traps.c:2357:d0 Domain attempted WRMSR 00000000c0010004 from 0x0000ff723ff31f5e to 0x0000000000000000.
(XEN) [2010-12-12 18:10:15] traps.c:2357:d0 Domain attempted WRMSR 00000000c0010000 from 0x00000204cc0a59df to 0x0000000000430076.
(XEN) [2010-12-12 18:10:16] PCI add device 00:00.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:00.2
(XEN) [2010-12-12 18:10:16] PCI add device 00:02.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:03.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:05.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:06.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:0a.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:0b.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:0d.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:11.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:12.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:12.2
(XEN) [2010-12-12 18:10:16] PCI add device 00:13.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:13.2
(XEN) [2010-12-12 18:10:16] PCI add device 00:14.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:14.3
(XEN) [2010-12-12 18:10:16] PCI add device 00:14.4
(XEN) [2010-12-12 18:10:16] PCI add device 00:14.5
(XEN) [2010-12-12 18:10:16] PCI add device 00:15.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:16.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:16.2
(XEN) [2010-12-12 18:10:16] PCI add device 00:18.0
(XEN) [2010-12-12 18:10:16] PCI add device 00:18.1
(XEN) [2010-12-12 18:10:16] PCI add device 00:18.2
(XEN) [2010-12-12 18:10:16] PCI add device 00:18.3
(XEN) [2010-12-12 18:10:16] PCI add device 00:18.4
(XEN) [2010-12-12 18:10:16] PCI add device 0b:00.0
(XEN) [2010-12-12 18:10:16] PCI add device 0a:00.0
(XEN) [2010-12-12 18:10:16] PCI add device 0a:00.1
(XEN) [2010-12-12 18:10:16] PCI add device 0a:00.2
(XEN) [2010-12-12 18:10:16] PCI add device 0a:00.3
(XEN) [2010-12-12 18:10:16] PCI add device 0a:00.4
(XEN) [2010-12-12 18:10:16] PCI add device 0a:00.5
(XEN) [2010-12-12 18:10:16] PCI add device 0a:00.6
(XEN) [2010-12-12 18:10:16] PCI add device 0a:00.7
(XEN) [2010-12-12 18:10:16] PCI add device 09:00.0
(XEN) [2010-12-12 18:10:16] PCI add device 08:00.0
(XEN) [2010-12-12 18:10:16] PCI add device 06:00.0
(XEN) [2010-12-12 18:10:16] PCI add device 07:01.0
(XEN) [2010-12-12 18:10:16] PCI add device 07:01.1
(XEN) [2010-12-12 18:10:16] PCI add device 07:01.2
(XEN) [2010-12-12 18:10:16] PCI add device 05:00.0
(XEN) [2010-12-12 18:10:16] PCI add device 05:00.1
(XEN) [2010-12-12 18:10:16] PCI add device 04:00.0
(XEN) [2010-12-12 18:10:16] PCI add device 04:00.1
(XEN) [2010-12-12 18:10:16] PCI add device 04:00.2
(XEN) [2010-12-12 18:10:16] PCI add device 04:00.3
(XEN) [2010-12-12 18:10:16] PCI add device 04:00.4
(XEN) [2010-12-12 18:10:16] PCI add device 04:00.5
(XEN) [2010-12-12 18:10:16] PCI add device 04:00.6
(XEN) [2010-12-12 18:10:16] PCI add device 04:00.7
(XEN) [2010-12-12 18:10:16] PCI add device 03:06.0
(XEN) [2010-12-12 18:10:16] IOAPIC[0]: Set PCI routing entry (6-8 -> 0x58 -> IRQ 8 Mode:0 Active:0)
(XEN) [2010-12-12 18:10:16] IOAPIC[0]: Set PCI routing entry (6-13 -> 0x88 -> IRQ 13 Mode:0 Active:0)
(XEN) [2010-12-12 18:10:16] IOAPIC[1]: Set PCI routing entry (7-28 -> 0xa0 -> IRQ 52 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:16] IOAPIC[1]: Set PCI routing entry (7-29 -> 0xa8 -> IRQ 53 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:16] IOAPIC[1]: Set PCI routing entry (7-30 -> 0xb0 -> IRQ 54 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:16] IOAPIC[0]: Set PCI routing entry (6-16 -> 0xb8 -> IRQ 16 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[0]: Set PCI routing entry (6-22 -> 0x41 -> IRQ 22 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-19 -> 0x49 -> IRQ 43 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-18 -> 0x51 -> IRQ 42 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-17 -> 0x59 -> IRQ 41 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-16 -> 0x61 -> IRQ 40 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-9 -> 0x69 -> IRQ 33 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-8 -> 0x71 -> IRQ 32 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-7 -> 0x79 -> IRQ 31 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-6 -> 0x81 -> IRQ 30 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-5 -> 0x89 -> IRQ 29 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-4 -> 0x91 -> IRQ 28 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[0]: Set PCI routing entry (6-19 -> 0x99 -> IRQ 19 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-22 -> 0xa9 -> IRQ 46 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[1]: Set PCI routing entry (7-27 -> 0xb9 -> IRQ 51 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[0]: Set PCI routing entry (6-17 -> 0xc9 -> IRQ 17 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:17] IOAPIC[0]: Set PCI routing entry (6-18 -> 0xd1 -> IRQ 18 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:18] IOAPIC[1]: Set PCI routing entry (7-20 -> 0xd9 -> IRQ 44 Mode:1 Active:1)
(XEN) [2010-12-12 18:10:18] IOAPIC[1]: Set PCI routing entry (7-21 -> 0x22 -> IRQ 45 Mode:1 Active:1)
(XEN) [2010-12-12 18:14:44] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:14:44] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:14:45] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:14:45] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:15:09] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:15:09] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:15:09] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:15:09] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:15:34] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:15:34] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:15:34] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:15:34] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:15:59] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:15:59] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:15:59] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:15:59] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:16:24] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:16:24] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:16:24] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:16:24] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:16:55] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:16:55] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:16:55] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:16:55] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:17:23] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:17:23] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:17:23] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:17:23] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:17:49] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:17:49] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:17:49] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:17:49] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:18:17] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:18:17] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:18:20] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:18:20] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:18:22] AMD-Vi: Disable DTE:0x400, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: Setup I/O page table at DTE:0x400, root_table:16bd03000,domain_id:9, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: reassign 4:0.0 domain 0 -> domain 9
(XEN) [2010-12-12 18:18:22] AMD-Vi: Disable DTE:0x401, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: Setup I/O page table at DTE:0x401, root_table:16bd03000,domain_id:9, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: reassign 4:0.1 domain 0 -> domain 9
(XEN) [2010-12-12 18:18:22] AMD-Vi: Disable DTE:0x402, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: Setup I/O page table at DTE:0x402, root_table:16bd03000,domain_id:9, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: reassign 4:0.2 domain 0 -> domain 9
(XEN) [2010-12-12 18:18:22] AMD-Vi: Disable DTE:0x403, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: Setup I/O page table at DTE:0x403, root_table:16bd03000,domain_id:9, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: reassign 4:0.3 domain 0 -> domain 9
(XEN) [2010-12-12 18:18:22] AMD-Vi: Disable DTE:0x404, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: Setup I/O page table at DTE:0x404, root_table:16bd03000,domain_id:9, paging_mode:3
(XEN) [2010-12-12 18:18:22] AMD-Vi: reassign 4:0.4 domain 0 -> domain 9
(XEN) [2010-12-12 18:18:23] AMD-Vi: Disable DTE:0x405, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:18:23] AMD-Vi: Setup I/O page table at DTE:0x405, root_table:16bd03000,domain_id:9, paging_mode:3
(XEN) [2010-12-12 18:18:23] AMD-Vi: reassign 4:0.5 domain 0 -> domain 9
(XEN) [2010-12-12 18:18:23] AMD-Vi: Disable DTE:0x406, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:18:23] AMD-Vi: Setup I/O page table at DTE:0x406, root_table:16bd03000,domain_id:9, paging_mode:3
(XEN) [2010-12-12 18:18:23] AMD-Vi: reassign 4:0.6 domain 0 -> domain 9
(XEN) [2010-12-12 18:18:23] AMD-Vi: Disable DTE:0x407, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:18:23] AMD-Vi: Setup I/O page table at DTE:0x407, root_table:16bd03000,domain_id:9, paging_mode:3
(XEN) [2010-12-12 18:18:23] AMD-Vi: reassign 4:0.7 domain 0 -> domain 9
(XEN) [2010-12-12 18:18:27] traps.c:2357:d9 Domain attempted WRMSR 00000000c0010004 from 0x0000efb8299e7950 to 0x000000000000abcd.
(XEN) [2010-12-12 18:18:54] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:18:54] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:18:54] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:18:54] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:19:59] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:19:59] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:20:02] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:20:02] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:20:05] AMD-Vi: Disable DTE:0xa4, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:20:05] AMD-Vi: Setup I/O page table at DTE:0xa4, root_table:1bf763000,domain_id:11, paging_mode:3
(XEN) [2010-12-12 18:20:05] AMD-Vi: reassign 3:6.0 domain 0 -> domain 11
(XEN) [2010-12-12 18:20:23] traps.c:2357:d11 Domain attempted WRMSR 00000000c0010004 from 0x0000efb8299e7950 to 0x000000000000abcd.
(XEN) [2010-12-12 18:20:52] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:20:52] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:20:52] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:20:52] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:21:27] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:21:27] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:21:32] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:21:32] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:21:34] AMD-Vi: Disable DTE:0xa00, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: Setup I/O page table at DTE:0xa00, root_table:1a37c4000,domain_id:13, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: reassign a:0.0 domain 0 -> domain 13
(XEN) [2010-12-12 18:21:34] AMD-Vi: Disable DTE:0xa01, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: Setup I/O page table at DTE:0xa01, root_table:1a37c4000,domain_id:13, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: reassign a:0.1 domain 0 -> domain 13
(XEN) [2010-12-12 18:21:34] AMD-Vi: Disable DTE:0xa02, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: Setup I/O page table at DTE:0xa02, root_table:1a37c4000,domain_id:13, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: reassign a:0.2 domain 0 -> domain 13
(XEN) [2010-12-12 18:21:34] AMD-Vi: Disable DTE:0xa03, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: Setup I/O page table at DTE:0xa03, root_table:1a37c4000,domain_id:13, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: reassign a:0.3 domain 0 -> domain 13
(XEN) [2010-12-12 18:21:34] AMD-Vi: Disable DTE:0xa04, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: Setup I/O page table at DTE:0xa04, root_table:1a37c4000,domain_id:13, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: reassign a:0.4 domain 0 -> domain 13
(XEN) [2010-12-12 18:21:34] AMD-Vi: Disable DTE:0xa05, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: Setup I/O page table at DTE:0xa05, root_table:1a37c4000,domain_id:13, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: reassign a:0.5 domain 0 -> domain 13
(XEN) [2010-12-12 18:21:34] AMD-Vi: Disable DTE:0xa06, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: Setup I/O page table at DTE:0xa06, root_table:1a37c4000,domain_id:13, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: reassign a:0.6 domain 0 -> domain 13
(XEN) [2010-12-12 18:21:34] AMD-Vi: Disable DTE:0xa07, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: Setup I/O page table at DTE:0xa07, root_table:1a37c4000,domain_id:13, paging_mode:3
(XEN) [2010-12-12 18:21:34] AMD-Vi: reassign a:0.7 domain 0 -> domain 13
(XEN) [2010-12-12 18:21:39] traps.c:2357:d13 Domain attempted WRMSR 00000000c0010004 from 0x000024b3aa2f339f to 0x000000000000abcd.
(XEN) [2010-12-12 18:29:25] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:29:25] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:29:27] tmem: all pools frozen for all domains
(XEN) [2010-12-12 18:29:27] tmem: all pools thawed for all domains
(XEN) [2010-12-12 18:29:32] AMD-Vi: Disable DTE:0x500, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:29:32] AMD-Vi: Setup I/O page table at DTE:0x500, root_table:1f5284000,domain_id:14, paging_mode:4
(XEN) [2010-12-12 18:29:32] AMD-Vi: reassign 5:0.0 domain 0 -> domain 14
(XEN) [2010-12-12 18:29:32] domctl.c:1038:d0 ioport_map:add f_gport=3b0 f_mport=3b0 np=c
(XEN) [2010-12-12 18:29:32] domctl.c:982:d0 memory_map:add: gfn=a0 mfn=a0 nr_mfns=20
(XEN) [2010-12-12 18:29:32] domctl.c:1038:d0 ioport_map:add f_gport=3c0 f_mport=3c0 np=3
(XEN) [2010-12-12 18:29:32] domctl.c:1038:d0 ioport_map:add f_gport=3c4 f_mport=3c4 np=1c
(XEN) [2010-12-12 18:29:34] AMD-Vi: Disable DTE:0x501, domain_id:0, paging_mode:3
(XEN) [2010-12-12 18:29:34] AMD-Vi: Setup I/O page table at DTE:0x501, root_table:1f5284000,domain_id:14, paging_mode:4
(XEN) [2010-12-12 18:29:34] AMD-Vi: reassign 5:0.1 domain 0 -> domain 14
(XEN) [2010-12-12 18:29:38] HVM14: HVM Loader
(XEN) [2010-12-12 18:29:38] HVM14: Detected Xen v4.1-unstable
(XEN) [2010-12-12 18:29:38] HVM14: CPU speed is 3200 MHz
(XEN) [2010-12-12 18:29:38] HVM14: Xenbus rings @0xfeffc000, event channel 2
(XEN) [2010-12-12 18:29:38] irq.c:258: Dom14 PCI link 0 changed 0 -> 5
(XEN) [2010-12-12 18:29:38] HVM14: PCI-ISA link 0 routed to IRQ5
(XEN) [2010-12-12 18:29:38] irq.c:258: Dom14 PCI link 1 changed 0 -> 10
(XEN) [2010-12-12 18:29:38] HVM14: PCI-ISA link 1 routed to IRQ10
(XEN) [2010-12-12 18:29:38] irq.c:258: Dom14 PCI link 2 changed 0 -> 11
(XEN) [2010-12-12 18:29:38] HVM14: PCI-ISA link 2 routed to IRQ11
(XEN) [2010-12-12 18:29:38] irq.c:258: Dom14 PCI link 3 changed 0 -> 5
(XEN) [2010-12-12 18:29:38] HVM14: PCI-ISA link 3 routed to IRQ5
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 01:2 INTD->IRQ5
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 01:3 INTA->IRQ10
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 03:0 INTA->IRQ5
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 04:0 INTA->IRQ5
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 05:0 INTA->IRQ10
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 05:1 INTB->IRQ11
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 05:0 bar 10 size 10000000: e000000c
(XEN) [2010-12-12 18:29:38] domctl.c:982:d0 memory_map:add: gfn=e0000 mfn=b0000 nr_mfns=10000
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 03:0 bar 14 size 01000000: f0000008
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 05:0 bar 30 size 00020000: f1000000
(XEN) [2010-12-12 18:29:38] domctl.c:982:d0 memory_map:add: gfn=f1020 mfn=f9be0 nr_mfns=10
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 05:0 bar 18 size 00010000: f1020004
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 05:1 bar 10 size 00004000: f1030004
(XEN) [2010-12-12 18:29:38] domctl.c:982:d0 memory_map:add: gfn=f1030 mfn=f9bfc nr_mfns=4
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 04:0 bar 14 size 00000100: f1034000
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 05:0 bar 20 size 00000100: 0000c201
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 01:2 bar 20 size 00000020: 0000c301
(XEN) [2010-12-12 18:29:38] HVM14: pci dev 01:1 bar 20 size 00000010: 0000c321
(XEN) [2010-12-12 18:29:38] HVM14: Multiprocessor initialisation:
(XEN) [2010-12-12 18:29:38] HVM14: - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [3/8] ... done.
(XEN) [2010-12-12 18:29:38] HVM14: Testing HVM environment:
(XEN) [2010-12-12 18:29:38] HVM14: - REP INSB across page boundaries ... passed
(XEN) [2010-12-12 18:29:38] HVM14: - GS base MSRs and SWAPGS ... passed
(XEN) [2010-12-12 18:29:38] HVM14: Passed 2 of 2 tests
(XEN) [2010-12-12 18:29:38] HVM14: Writing SMBIOS tables ...
(XEN) [2010-12-12 18:29:38] HVM14: Loading ROMBIOS ...
(XEN) [2010-12-12 18:29:38] HVM14: 9788 bytes of ROMBIOS high-memory extensions:
(XEN) [2010-12-12 18:29:38] HVM14: Relocating to 0xfc000000-0xfc00263c ... done
(XEN) [2010-12-12 18:29:38] HVM14: Creating MP tables ...
(XEN) [2010-12-12 18:29:38] HVM14: Loading VGABIOS of passthroughed gfx ...
(XEN) [2010-12-12 18:29:38] HVM14: Loading PCI Option ROM ...
(XEN) [2010-12-12 18:29:38] HVM14: - Manufacturer: http://etherboot.org
(XEN) [2010-12-12 18:29:38] HVM14: - Product name: gPXE
(XEN) [2010-12-12 18:29:38] HVM14: Loading ACPI ...
(XEN) [2010-12-12 18:29:38] HVM14: - Lo data: 000ea020-000ea04f
(XEN) [2010-12-12 18:29:38] HVM14: - Hi data: fc002800-fc01291f
(XEN) [2010-12-12 18:29:38] HVM14: vm86 TSS at fc012c00
(XEN) [2010-12-12 18:29:38] HVM14: BIOS map:
(XEN) [2010-12-12 18:29:38] HVM14: c0000-ce7ff: VGA BIOS
(XEN) [2010-12-12 18:29:38] HVM14: ce800-dc7ff: Etherboot ROM
(XEN) [2010-12-12 18:29:38] HVM14: eb000-eb156: SMBIOS tables
(XEN) [2010-12-12 18:29:38] HVM14: f0000-fffff: Main BIOS
(XEN) [2010-12-12 18:29:38] HVM14: E820 table:
(XEN) [2010-12-12 18:29:38] HVM14: [00]: 00000000:00000000 - 00000000:0009e000: RAM
(XEN) [2010-12-12 18:29:38] HVM14: [01]: 00000000:0009e000 - 00000000:0009fc00: RESERVED
(XEN) [2010-12-12 18:29:38] HVM14: [02]: 00000000:0009fc00 - 00000000:000a0000: RESERVED
(XEN) [2010-12-12 18:29:38] HVM14: HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) [2010-12-12 18:29:38] HVM14: [03]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) [2010-12-12 18:29:38] HVM14: [04]: 00000000:00100000 - 00000000:20000000: RAM
(XEN) [2010-12-12 18:29:38] HVM14: HOLE: 00000000:20000000 - 00000000:fc000000
(XEN) [2010-12-12 18:29:38] HVM14: [05]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) [2010-12-12 18:29:38] HVM14: Invoking ROMBIOS ...
(XEN) [2010-12-12 18:29:38] HVM14: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) [2010-12-12 18:29:38] HVM14: Bochs BIOS - build: 06/23/99
(XEN) [2010-12-12 18:29:38] HVM14: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) [2010-12-12 18:29:38] HVM14: Options: apmbios pcibios eltorito PMM
(XEN) [2010-12-12 18:29:38] HVM14:
(XEN) [2010-12-12 18:29:38] HVM14: ata0-0: PCHS=8322/16/63 translation=lba LCHS=522/255/63
(XEN) [2010-12-12 18:29:38] HVM14: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (4096 MBytes)
(XEN) [2010-12-12 18:29:44] HVM14: IDE time out
(XEN) [2010-12-12 18:29:44] HVM14:
(XEN) [2010-12-12 18:29:44] HVM14:
(XEN) [2010-12-12 18:29:44] HVM14:
(XEN) [2010-12-12 18:29:44] HVM14: Press F12 for boot menu.
(XEN) [2010-12-12 18:29:44] HVM14:
(XEN) [2010-12-12 18:29:44] HVM14: Booting from Hard Disk...
(XEN) [2010-12-12 18:29:44] HVM14: Booting from 0000:7c00
(XEN) [2010-12-12 18:29:44] HVM14: int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) [2010-12-12 18:29:44] HVM14: *** int 15h function AX=e980, BX=007e not yet supported!
(XEN) [2010-12-12 18:29:54] irq.c:258: Dom14 PCI link 0 changed 5 -> 0
(XEN) [2010-12-12 18:29:54] irq.c:258: Dom14 PCI link 1 changed 10 -> 0
(XEN) [2010-12-12 18:29:54] irq.c:258: Dom14 PCI link 2 changed 11 -> 0
(XEN) [2010-12-12 18:29:54] irq.c:258: Dom14 PCI link 3 changed 5 -> 0
(XEN) [2010-12-12 18:29:55] domctl.c:992:d0 memory_map:remove: gfn=e0000 mfn=b0000 nr_mfns=10000
(XEN) [2010-12-12 18:29:55] domctl.c:992:d0 memory_map:remove: gfn=f1020 mfn=f9be0 nr_mfns=10
(XEN) [2010-12-12 18:29:55] domctl.c:982:d0 memory_map:add: gfn=e0000 mfn=b0000 nr_mfns=10000
(XEN) [2010-12-12 18:29:55] domctl.c:982:d0 memory_map:add: gfn=f1020 mfn=f9be0 nr_mfns=10
(XEN) [2010-12-12 18:29:55] domctl.c:992:d0 memory_map:remove: gfn=f1030 mfn=f9bfc nr_mfns=4
(XEN) [2010-12-12 18:29:55] domctl.c:982:d0 memory_map:add: gfn=f1030 mfn=f9bfc nr_mfns=4
[-- Attachment #11: xm-info.txt --]
[-- Type: text/plain, Size: 1482 bytes --]
host : serveerstertje
release : 2.6.32.26-xen-next-2.6.32.x-20101210
version : #20 SMP Fri Dec 10 18:24:34 CET 2010
machine : x86_64
nr_cpus : 6
nr_nodes : 1
cores_per_socket : 6
threads_per_core : 1
cpu_mhz : 3200
hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000
virt_caps : hvm hvm_directio
total_memory : 8191
free_memory : 2950
free_cpus : 0
xen_major : 4
xen_minor : 1
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Wed Dec 08 10:46:31 2010 +0000 22468:89116f28083f
xen_commandline : dom0_mem=768M loglvl=all loglvl_guest=all console_timestamps vga=gfx-1280x1024x32 cpuidle cpufreq=xen noreboot debug lapic=debug apic_verbosity=debug apic=debug acpi_enforce_resources=lax iommu=on,amd-iommu-debug amd_iommu=on amd-iommu-debug com1=115200,8n1 console=vga,com1
cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1)
cc_compile_by : root
cc_compile_domain : dyndns.org
cc_compile_date : Sun Dec 12 17:49:14 CET 2010
xend_config_format : 4
[-- Attachment #12: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-12 6:19 ` Huang2, Wei
2010-12-12 19:10 ` Sander Eikelenboom
@ 2010-12-13 20:17 ` Sander Eikelenboom
2010-12-13 20:33 ` Huang2, Wei
2011-01-06 17:23 ` Pasi Kärkkäinen
2 siblings, 1 reply; 32+ messages in thread
From: Sander Eikelenboom @ 2010-12-13 20:17 UTC (permalink / raw)
To: Huang2, Wei
Cc: Xen-devel, Keir Fraser, Kay, Allen M, Ian Jackson, Wang2, Wei,
djmagee@mageenet.net
Hello Wei,
It just occured to me, this is probably only working when trying to passthrough the primary graphics card ?
I'm trying to passthrough a secondary card, so the primary(boot) card still has the xen/dom0 console.
It could end up giving problems by loading the wrong/no bios in the hvmloader ?
Should passing though a secondary graphics card also be possible with this patch ?
--
Sander
Sunday, December 12, 2010, 7:19:08 AM, you wrote:
> This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
> Thanks,
> -Wei
> ________________________________________
> From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> Sent: Saturday, December 11, 2010 9:38 AM
> To: Sander Eikelenboom; Huang2, Wei
> Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> The patch would need some work to make it suitable for check in and get it
> working for stubdom. At the very least the ioperm() calls would need
> removing completely, or stubbing out for the stubdom build.
> -- Keir
> On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
>> Do i need any previous patches for this to work ?
>>
>> After applying it to xen-unstable, compiling xen results in:
>>
>> make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
>> [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
>> [ -e include/mini-os ] || ln -sf . include/mini-os
>> [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
>> make --directory=arch/x86
>> OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
>> exit 1;
>> make[3]: Entering directory
>> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory
>> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
>> ld -r -nostdlib
>> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
>> -m elf_x86_64
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
>> .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
>> -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
>> -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>> objcopy -w -G xenos_* -G _start
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>> ld -nostdlib
>> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
>> -m elf_x86_64 -T arch/x86/minios-x86_64.lds
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
>> function `ati_hw_out':
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
>> reference to `ioperm'
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
>> reference to `ioperm'
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
>> function `ati_hw_in':
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
>> reference to `ioperm'
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
>> reference to `ioperm'
>> make[2]: ***
>> [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
>> make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
>> make[1]: *** [ioemu-stubdom] Error 2
>> make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
>> make: *** [install-stubdom] Error 2
>>
>> Don't know why the include of sys/io.h doesn't seem to work
>> --
>>
>> Sander
>>
>> Saturday, December 11, 2010, 12:40:19 AM, you wrote:
>>
>>> Hi,
>>
>>> The attached patch supports dynamic detection of BARs (both MMIO and
>>> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
>>> passthru. Please let me know whether it works better for you.
>>
>>> Thanks,
>>> -Wei
>>
>>> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
>>>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
>>>>> Sorry, hold on a second. This fix seems corrupt my pci config space
>>>>> after
>>>>> several runs.
>>>>>
>>>> Hello,
>>>>
>>>> Any updates to these patches? Many users have been asking about amd/ati vga
>>>> passthru stuff..
>>>>
>>>> -- Pasi
>>>>
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: xen-devel-bounces@lists.xensource.com
>>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>>> Sent: Wednesday, October 13, 2010 3:47 PM
>>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>>> Cc: Wang2, Wei; Xen-devel
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Hi Allen and Doug,
>>>>>
>>>>>
>>>>>
>>>>> Could you fix the following line in save_pci_conf_space() of
>>>>> tools/python/xen/util/pci.py?
>>>>>
>>>>>
>>>>>
>>>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>>>>>
>>>>>
>>>>>
>>>>> This solves my black screen issue. Please let me know the results.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>>> Sent: Friday, October 08, 2010 10:53 AM
>>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel; Wang2, Wei
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Wei,
>>>>>
>>>>> These were guests that had never seen the catalyst
>>>>> driver
>>>>> before. I booted each three with the graphics device and usb devices
>>>>> assigned, they worked fine using the basic VGA driver, then installed
>>>>> fresh Catalyst 10.9, rebooted, and each one crashed.
>>>>>
>>>>>
>>>>>
>>>>> Let me know if there's any other info I can provide
>>>>> that
>>>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
>>>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
>>>>> pvops
>>>>> Dom0 from stable-2.6.32.x commit 179eca50.
>>>>>
>>>>>
>>>>>
>>>>> Doug Magee
>>>>>
>>>>>
>>>>>
>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>> Sent: Friday, October 08, 2010 11:41 AM
>>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel; Wang2, Wei
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Hi Doug,
>>>>>
>>>>>
>>>>>
>>>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
>>>>> Catalyst installation or an existing guest image? We felt this VBIOS
>>>>> patch
>>>>> might not provide all necessary resources to driver, which got upset.
>>>>> Currently we are debugging it with our driver team and will let you
>>>>> know
>>>>> the update.
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>>> Sent: Friday, October 08, 2010 9:41 AM
>>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Wei,
>>>>>
>>>>> I've tested with a Radeon 4770 and it the VBIOS works
>>>>> without a problem, through many guest (re)boots, so it seems pretty
>>>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
>>>>> and Windows 7 (without accelerated drivers). The open radeon linux
>>>>> driver
>>>>> works fine.
>>>>>
>>>>>
>>>>>
>>>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
>>>>> in
>>>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
>>>>> reset?), and linux (total system freeze). This seems to be different
>>>>> than
>>>>> the `Blank Screen' problem you report, as the driver is clearly not
>>>>> functioning properly.
>>>>>
>>>>>
>>>>>
>>>>> Doug Magee
>>>>>
>>>>>
>>>>>
>>>>> From: xen-devel-bounces@lists.xensource.com
>>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>>> Sent: Friday, October 08, 2010 9:57 AM
>>>>> To: Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Hi Allen,
>>>>>
>>>>>
>>>>>
>>>>> Yes, Catalyst driver is the one from public website. The driver still
>>>>> has
>>>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
>>>>> patch is to get community feedbacks. After we figure out the root cause
>>>>> of
>>>>> black screen, I will formally submit a patch for inclusion.
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>>> Sent: Friday, October 08, 2010 2:21 AM
>>>>> To: Huang2, Wei; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Wei,
>>>>>
>>>>>
>>>>>
>>>>> Is Catalyst driver the one on AMD website? I think that's what I have
>>>>> in
>>>>> my win7 guest and it matches the symptom you are describing. "lspci"
>>>>> reports my ATI card is a V5700 - although it says v3750 on the box.
>>>>> Where
>>>>> can I get a working driver?
>>>>>
>>>>>
>>>>>
>>>>> The patch looks reasonable to me in general.
>>>>>
>>>>>
>>>>>
>>>>> Allen
>>>>>
>>>>>
>>>>>
>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>> Sent: Thursday, October 07, 2010 9:06 PM
>>>>> To: Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Allen,
>>>>>
>>>>>
>>>>>
>>>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
>>>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
>>>>> V3750
>>>>> at hand. It is very possible this patch isn't compatible with V3750. We
>>>>> will try to get hold of one for debugging. For graphics which work with
>>>>> this path, users should be able to get rid of emulated gfx (such as
>>>>> Cirrus). I have successfully installed a Windows guest VM using this
>>>>> patch.
>>>>>
>>>>>
>>>>>
>>>>> I also want to point out that there is still an issue. Users will see a
>>>>> black screen after installing Catalyst driver. Even though the screen
>>>>> appears to be black, the driver is actually functioning correctly
>>>>> (3DMark
>>>>> can be run with external monitor). Our driver team is currently
>>>>> debugging
>>>>> it and they believe this is easy to fix.
>>>>>
>>>>>
>>>>>
>>>>> What is your opinion on this patch (and the solution) in general?
>>>>>
>>>>>
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>>> Sent: Thursday, October 07, 2010 6:58 PM
>>>>> To: Huang2, Wei; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Wei,
>>>>>
>>>>>
>>>>>
>>>>> This patch did not cause any problems with Intel IGD passthrough for
>>>>> me.
>>>>> However, the monitor remained blank if I pass through ATI Firepro V3750
>>>>> either as the primary display device or the secondary device
>>>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
>>>>> work.
>>>>>
>>>>>
>>>>>
>>>>> Have you tested the patch with this graphics card?
>>>>>
>>>>>
>>>>>
>>>>> Allen
>>>>>
>>>>>
>>>>>
>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>> Sent: Thursday, October 07, 2010 9:57 AM
>>>>> To: Ian Jackson
>>>>> Cc: Xen-devel; Kay, Allen M
>>>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Ian,
>>>>>
>>>>>
>>>>>
>>>>> There have been a lot of interest on gfx passthru recently. This patch
>>>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
>>>>> Windows boot logo) can now show in passthru screen. We have tested with
>>>>> various Windows and Linux guest VMs. Please help review it. We are also
>>>>> looking forward to comments and suggestions from Xen community users.
>>>>>
>>>>>
>>>>>
>>>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
>>>>>
>>>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> http://lists.xensource.com/xen-devel
>>>>
>>
>>
>>
--
Best regards,
Sander mailto:linux@eikelenboom.it
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-13 20:17 ` Sander Eikelenboom
@ 2010-12-13 20:33 ` Huang2, Wei
2010-12-13 20:47 ` Sander Eikelenboom
2010-12-16 18:29 ` Pasi Kärkkäinen
0 siblings, 2 replies; 32+ messages in thread
From: Huang2, Wei @ 2010-12-13 20:33 UTC (permalink / raw)
To: Sander Eikelenboom
Cc: Ian, Keir Fraser, Kay, Allen M, Jackson, Wang2, Wei, Xen-devel,
djmagee@mageenet.net
Hi Sander,
I answer your questions (including the one from last email) below:
1. Your gfx is a bit old. Some of the tricks (such as MMINDEX values 0x4010) aren't quite consistent across different generations of ATI gfx. I need to look at the log myself. I will locate an HD3000 card to debug.
2. The goal of this patch is to passthru the primary gfx as THE ONLY GFX inside guest VM (namely: my patch + set gfx_passthru=1 in guest config file). Since you are passthru the on-board secondary gfx, I am not sure qemu-dm is copying the correct VBIOS from address 0xc0000. One solution is to force VBIOS been read from a file, which can be downloaded from http://www.techpowerup.com/vgabios/.
3. Note that current Xen support passthru ATI gfx as a secondary gfx, even without my patch. So if you don't care about primary/secondary, you probably don't need this patch. Have you tried: existing Xen + passthru ATI without gfx_passthru=1? As for as I have seen, it worked for many ATI gfx.
Thanks,
-Wei
-----Original Message-----
From: Sander Eikelenboom [mailto:linux@eikelenboom.it]
Sent: Monday, December 13, 2010 2:18 PM
To: Huang2, Wei
Cc: Keir Fraser; Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
Hello Wei,
It just occured to me, this is probably only working when trying to passthrough the primary graphics card ?
I'm trying to passthrough a secondary card, so the primary(boot) card still has the xen/dom0 console.
It could end up giving problems by loading the wrong/no bios in the hvmloader ?
Should passing though a secondary graphics card also be possible with this patch ?
--
Sander
Sunday, December 12, 2010, 7:19:08 AM, you wrote:
> This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
> Thanks,
> -Wei
> ________________________________________
> From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> Sent: Saturday, December 11, 2010 9:38 AM
> To: Sander Eikelenboom; Huang2, Wei
> Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> The patch would need some work to make it suitable for check in and get it
> working for stubdom. At the very least the ioperm() calls would need
> removing completely, or stubbing out for the stubdom build.
> -- Keir
> On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
>> Do i need any previous patches for this to work ?
>>
>> After applying it to xen-unstable, compiling xen results in:
>>
>> make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
>> [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
>> [ -e include/mini-os ] || ln -sf . include/mini-os
>> [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
>> make --directory=arch/x86
>> OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
>> exit 1;
>> make[3]: Entering directory
>> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory
>> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
>> ld -r -nostdlib
>> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
>> -m elf_x86_64
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
>> .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
>> -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
>> -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>> objcopy -w -G xenos_* -G _start
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>> ld -nostdlib
>> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
>> -m elf_x86_64 -T arch/x86/minios-x86_64.lds
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
>> function `ati_hw_out':
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
>> reference to `ioperm'
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
>> reference to `ioperm'
>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
>> function `ati_hw_in':
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
>> reference to `ioperm'
>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
>> reference to `ioperm'
>> make[2]: ***
>> [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
>> make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
>> make[1]: *** [ioemu-stubdom] Error 2
>> make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
>> make: *** [install-stubdom] Error 2
>>
>> Don't know why the include of sys/io.h doesn't seem to work
>> --
>>
>> Sander
>>
>> Saturday, December 11, 2010, 12:40:19 AM, you wrote:
>>
>>> Hi,
>>
>>> The attached patch supports dynamic detection of BARs (both MMIO and
>>> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
>>> passthru. Please let me know whether it works better for you.
>>
>>> Thanks,
>>> -Wei
>>
>>> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
>>>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
>>>>> Sorry, hold on a second. This fix seems corrupt my pci config space
>>>>> after
>>>>> several runs.
>>>>>
>>>> Hello,
>>>>
>>>> Any updates to these patches? Many users have been asking about amd/ati vga
>>>> passthru stuff..
>>>>
>>>> -- Pasi
>>>>
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: xen-devel-bounces@lists.xensource.com
>>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>>> Sent: Wednesday, October 13, 2010 3:47 PM
>>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>>> Cc: Wang2, Wei; Xen-devel
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Hi Allen and Doug,
>>>>>
>>>>>
>>>>>
>>>>> Could you fix the following line in save_pci_conf_space() of
>>>>> tools/python/xen/util/pci.py?
>>>>>
>>>>>
>>>>>
>>>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>>>>>
>>>>>
>>>>>
>>>>> This solves my black screen issue. Please let me know the results.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>>> Sent: Friday, October 08, 2010 10:53 AM
>>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel; Wang2, Wei
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Wei,
>>>>>
>>>>> These were guests that had never seen the catalyst
>>>>> driver
>>>>> before. I booted each three with the graphics device and usb devices
>>>>> assigned, they worked fine using the basic VGA driver, then installed
>>>>> fresh Catalyst 10.9, rebooted, and each one crashed.
>>>>>
>>>>>
>>>>>
>>>>> Let me know if there's any other info I can provide
>>>>> that
>>>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
>>>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
>>>>> pvops
>>>>> Dom0 from stable-2.6.32.x commit 179eca50.
>>>>>
>>>>>
>>>>>
>>>>> Doug Magee
>>>>>
>>>>>
>>>>>
>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>> Sent: Friday, October 08, 2010 11:41 AM
>>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel; Wang2, Wei
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Hi Doug,
>>>>>
>>>>>
>>>>>
>>>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
>>>>> Catalyst installation or an existing guest image? We felt this VBIOS
>>>>> patch
>>>>> might not provide all necessary resources to driver, which got upset.
>>>>> Currently we are debugging it with our driver team and will let you
>>>>> know
>>>>> the update.
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>>> Sent: Friday, October 08, 2010 9:41 AM
>>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Wei,
>>>>>
>>>>> I've tested with a Radeon 4770 and it the VBIOS works
>>>>> without a problem, through many guest (re)boots, so it seems pretty
>>>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
>>>>> and Windows 7 (without accelerated drivers). The open radeon linux
>>>>> driver
>>>>> works fine.
>>>>>
>>>>>
>>>>>
>>>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
>>>>> in
>>>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
>>>>> reset?), and linux (total system freeze). This seems to be different
>>>>> than
>>>>> the `Blank Screen' problem you report, as the driver is clearly not
>>>>> functioning properly.
>>>>>
>>>>>
>>>>>
>>>>> Doug Magee
>>>>>
>>>>>
>>>>>
>>>>> From: xen-devel-bounces@lists.xensource.com
>>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>>> Sent: Friday, October 08, 2010 9:57 AM
>>>>> To: Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>> support
>>>>>
>>>>>
>>>>>
>>>>> Hi Allen,
>>>>>
>>>>>
>>>>>
>>>>> Yes, Catalyst driver is the one from public website. The driver still
>>>>> has
>>>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
>>>>> patch is to get community feedbacks. After we figure out the root cause
>>>>> of
>>>>> black screen, I will formally submit a patch for inclusion.
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>>> Sent: Friday, October 08, 2010 2:21 AM
>>>>> To: Huang2, Wei; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Wei,
>>>>>
>>>>>
>>>>>
>>>>> Is Catalyst driver the one on AMD website? I think that's what I have
>>>>> in
>>>>> my win7 guest and it matches the symptom you are describing. "lspci"
>>>>> reports my ATI card is a V5700 - although it says v3750 on the box.
>>>>> Where
>>>>> can I get a working driver?
>>>>>
>>>>>
>>>>>
>>>>> The patch looks reasonable to me in general.
>>>>>
>>>>>
>>>>>
>>>>> Allen
>>>>>
>>>>>
>>>>>
>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>> Sent: Thursday, October 07, 2010 9:06 PM
>>>>> To: Kay, Allen M; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Allen,
>>>>>
>>>>>
>>>>>
>>>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
>>>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
>>>>> V3750
>>>>> at hand. It is very possible this patch isn't compatible with V3750. We
>>>>> will try to get hold of one for debugging. For graphics which work with
>>>>> this path, users should be able to get rid of emulated gfx (such as
>>>>> Cirrus). I have successfully installed a Windows guest VM using this
>>>>> patch.
>>>>>
>>>>>
>>>>>
>>>>> I also want to point out that there is still an issue. Users will see a
>>>>> black screen after installing Catalyst driver. Even though the screen
>>>>> appears to be black, the driver is actually functioning correctly
>>>>> (3DMark
>>>>> can be run with external monitor). Our driver team is currently
>>>>> debugging
>>>>> it and they believe this is easy to fix.
>>>>>
>>>>>
>>>>>
>>>>> What is your opinion on this patch (and the solution) in general?
>>>>>
>>>>>
>>>>>
>>>>> -Wei
>>>>>
>>>>>
>>>>>
>>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>>> Sent: Thursday, October 07, 2010 6:58 PM
>>>>> To: Huang2, Wei; Ian Jackson
>>>>> Cc: Xen-devel
>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Wei,
>>>>>
>>>>>
>>>>>
>>>>> This patch did not cause any problems with Intel IGD passthrough for
>>>>> me.
>>>>> However, the monitor remained blank if I pass through ATI Firepro V3750
>>>>> either as the primary display device or the secondary device
>>>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
>>>>> work.
>>>>>
>>>>>
>>>>>
>>>>> Have you tested the patch with this graphics card?
>>>>>
>>>>>
>>>>>
>>>>> Allen
>>>>>
>>>>>
>>>>>
>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>> Sent: Thursday, October 07, 2010 9:57 AM
>>>>> To: Ian Jackson
>>>>> Cc: Xen-devel; Kay, Allen M
>>>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>
>>>>>
>>>>>
>>>>> Hi Ian,
>>>>>
>>>>>
>>>>>
>>>>> There have been a lot of interest on gfx passthru recently. This patch
>>>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
>>>>> Windows boot logo) can now show in passthru screen. We have tested with
>>>>> various Windows and Linux guest VMs. Please help review it. We are also
>>>>> looking forward to comments and suggestions from Xen community users.
>>>>>
>>>>>
>>>>>
>>>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
>>>>>
>>>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> http://lists.xensource.com/xen-devel
>>>>
>>
>>
>>
--
Best regards,
Sander mailto:linux@eikelenboom.it
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-13 20:33 ` Huang2, Wei
@ 2010-12-13 20:47 ` Sander Eikelenboom
2010-12-16 18:29 ` Pasi Kärkkäinen
1 sibling, 0 replies; 32+ messages in thread
From: Sander Eikelenboom @ 2010-12-13 20:47 UTC (permalink / raw)
To: Huang2, Wei
Cc: Xen-devel, Keir Fraser, Kay, Allen M, Ian Jackson, Wang2, Wei,
djmagee@mageenet.net
Thx for your answers !
I forgot about the primary/secondary difference.
From what i have seen so far it's probably not possible to automatically copy the bios of secondary card to use as bios in a hvm ?
I will try to load it from file, thx for the pointer.
(i'm using a nvidia card as primary/boot, and intent to keep it as xen/dom0 console, and have a secondary ati which i want to passthrough to a hvm as primary)
--
Sander
Monday, December 13, 2010, 9:33:02 PM, you wrote:
> Hi Sander,
> I answer your questions (including the one from last email) below:
> 1. Your gfx is a bit old. Some of the tricks (such as MMINDEX values 0x4010) aren't quite consistent across different generations of ATI gfx. I need to look at the log myself. I will locate an HD3000 card to debug.
> 2. The goal of this patch is to passthru the primary gfx as THE ONLY GFX inside guest VM (namely: my patch + set gfx_passthru=1 in guest config file). Since you are passthru the on-board secondary gfx, I am not sure qemu-dm is copying the correct VBIOS from address 0xc0000. One solution is to force VBIOS been read from a file, which can be downloaded from http://www.techpowerup.com/vgabios/.
> 3. Note that current Xen support passthru ATI gfx as a secondary gfx, even without my patch. So if you don't care about primary/secondary, you probably don't need this patch. Have you tried: existing Xen + passthru ATI without gfx_passthru=1? As for as I have seen, it worked for many ATI gfx.
> Thanks,
> -Wei
> -----Original Message-----
> From: Sander Eikelenboom [mailto:linux@eikelenboom.it]
> Sent: Monday, December 13, 2010 2:18 PM
> To: Huang2, Wei
> Cc: Keir Fraser; Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> Hello Wei,
> It just occured to me, this is probably only working when trying to passthrough the primary graphics card ?
> I'm trying to passthrough a secondary card, so the primary(boot) card still has the xen/dom0 console.
> It could end up giving problems by loading the wrong/no bios in the hvmloader ?
> Should passing though a secondary graphics card also be possible with this patch ?
> --
> Sander
> Sunday, December 12, 2010, 7:19:08 AM, you wrote:
>> This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
>> Thanks,
>> -Wei
>> ________________________________________
>> From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
>> Sent: Saturday, December 11, 2010 9:38 AM
>> To: Sander Eikelenboom; Huang2, Wei
>> Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
>> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>> The patch would need some work to make it suitable for check in and get it
>> working for stubdom. At the very least the ioperm() calls would need
>> removing completely, or stubbing out for the stubdom build.
>> -- Keir
>> On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
>>> Do i need any previous patches for this to work ?
>>>
>>> After applying it to xen-unstable, compiling xen results in:
>>>
>>> make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
>>> [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
>>> [ -e include/mini-os ] || ln -sf . include/mini-os
>>> [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
>>> make --directory=arch/x86
>>> OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
>>> exit 1;
>>> make[3]: Entering directory
>>> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
>>> make[3]: Nothing to be done for `all'.
>>> make[3]: Leaving directory
>>> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
>>> ld -r -nostdlib
>>> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
>>> -m elf_x86_64
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
>>> .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
>>> -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
>>> -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>>> objcopy -w -G xenos_* -G _start
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
>>> ld -nostdlib
>>> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
>>> -m elf_x86_64 -T arch/x86/minios-x86_64.lds
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
>>> function `ati_hw_out':
>>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
>>> reference to `ioperm'
>>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
>>> reference to `ioperm'
>>> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
>>> function `ati_hw_in':
>>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
>>> reference to `ioperm'
>>> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
>>> reference to `ioperm'
>>> make[2]: ***
>>> [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
>>> make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
>>> make[1]: *** [ioemu-stubdom] Error 2
>>> make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
>>> make: *** [install-stubdom] Error 2
>>>
>>> Don't know why the include of sys/io.h doesn't seem to work
>>> --
>>>
>>> Sander
>>>
>>> Saturday, December 11, 2010, 12:40:19 AM, you wrote:
>>>
>>>> Hi,
>>>
>>>> The attached patch supports dynamic detection of BARs (both MMIO and
>>>> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
>>>> passthru. Please let me know whether it works better for you.
>>>
>>>> Thanks,
>>>> -Wei
>>>
>>>> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
>>>>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
>>>>>> Sorry, hold on a second. This fix seems corrupt my pci config space
>>>>>> after
>>>>>> several runs.
>>>>>>
>>>>> Hello,
>>>>>
>>>>> Any updates to these patches? Many users have been asking about amd/ati vga
>>>>> passthru stuff..
>>>>>
>>>>> -- Pasi
>>>>>
>>>>>>
>>>>>> -Wei
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: xen-devel-bounces@lists.xensource.com
>>>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>>>> Sent: Wednesday, October 13, 2010 3:47 PM
>>>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>>>> Cc: Wang2, Wei; Xen-devel
>>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>>> support
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Allen and Doug,
>>>>>>
>>>>>>
>>>>>>
>>>>>> Could you fix the following line in save_pci_conf_space() of
>>>>>> tools/python/xen/util/pci.py?
>>>>>>
>>>>>>
>>>>>>
>>>>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
>>>>>>
>>>>>>
>>>>>>
>>>>>> This solves my black screen issue. Please let me know the results.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> -Wei
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>>>> Sent: Friday, October 08, 2010 10:53 AM
>>>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>>>> Cc: Xen-devel; Wang2, Wei
>>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>>> support
>>>>>>
>>>>>>
>>>>>>
>>>>>> Wei,
>>>>>>
>>>>>> These were guests that had never seen the catalyst
>>>>>> driver
>>>>>> before. I booted each three with the graphics device and usb devices
>>>>>> assigned, they worked fine using the basic VGA driver, then installed
>>>>>> fresh Catalyst 10.9, rebooted, and each one crashed.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Let me know if there's any other info I can provide
>>>>>> that
>>>>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
>>>>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
>>>>>> pvops
>>>>>> Dom0 from stable-2.6.32.x commit 179eca50.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Doug Magee
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>>> Sent: Friday, October 08, 2010 11:41 AM
>>>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
>>>>>> Cc: Xen-devel; Wang2, Wei
>>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>>> support
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Doug,
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
>>>>>> Catalyst installation or an existing guest image? We felt this VBIOS
>>>>>> patch
>>>>>> might not provide all necessary resources to driver, which got upset.
>>>>>> Currently we are debugging it with our driver team and will let you
>>>>>> know
>>>>>> the update.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> -Wei
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
>>>>>> Sent: Friday, October 08, 2010 9:41 AM
>>>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
>>>>>> Cc: Xen-devel
>>>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>>> support
>>>>>>
>>>>>>
>>>>>>
>>>>>> Wei,
>>>>>>
>>>>>> I've tested with a Radeon 4770 and it the VBIOS works
>>>>>> without a problem, through many guest (re)boots, so it seems pretty
>>>>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
>>>>>> and Windows 7 (without accelerated drivers). The open radeon linux
>>>>>> driver
>>>>>> works fine.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
>>>>>> in
>>>>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
>>>>>> reset?), and linux (total system freeze). This seems to be different
>>>>>> than
>>>>>> the `Blank Screen' problem you report, as the driver is clearly not
>>>>>> functioning properly.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Doug Magee
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: xen-devel-bounces@lists.xensource.com
>>>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
>>>>>> Sent: Friday, October 08, 2010 9:57 AM
>>>>>> To: Kay, Allen M; Ian Jackson
>>>>>> Cc: Xen-devel
>>>>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
>>>>>> support
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Allen,
>>>>>>
>>>>>>
>>>>>>
>>>>>> Yes, Catalyst driver is the one from public website. The driver still
>>>>>> has
>>>>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
>>>>>> patch is to get community feedbacks. After we figure out the root cause
>>>>>> of
>>>>>> black screen, I will formally submit a patch for inclusion.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> -Wei
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>>>> Sent: Friday, October 08, 2010 2:21 AM
>>>>>> To: Huang2, Wei; Ian Jackson
>>>>>> Cc: Xen-devel
>>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Wei,
>>>>>>
>>>>>>
>>>>>>
>>>>>> Is Catalyst driver the one on AMD website? I think that's what I have
>>>>>> in
>>>>>> my win7 guest and it matches the symptom you are describing. "lspci"
>>>>>> reports my ATI card is a V5700 - although it says v3750 on the box.
>>>>>> Where
>>>>>> can I get a working driver?
>>>>>>
>>>>>>
>>>>>>
>>>>>> The patch looks reasonable to me in general.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Allen
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>>> Sent: Thursday, October 07, 2010 9:06 PM
>>>>>> To: Kay, Allen M; Ian Jackson
>>>>>> Cc: Xen-devel
>>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Allen,
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
>>>>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
>>>>>> V3750
>>>>>> at hand. It is very possible this patch isn't compatible with V3750. We
>>>>>> will try to get hold of one for debugging. For graphics which work with
>>>>>> this path, users should be able to get rid of emulated gfx (such as
>>>>>> Cirrus). I have successfully installed a Windows guest VM using this
>>>>>> patch.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I also want to point out that there is still an issue. Users will see a
>>>>>> black screen after installing Catalyst driver. Even though the screen
>>>>>> appears to be black, the driver is actually functioning correctly
>>>>>> (3DMark
>>>>>> can be run with external monitor). Our driver team is currently
>>>>>> debugging
>>>>>> it and they believe this is easy to fix.
>>>>>>
>>>>>>
>>>>>>
>>>>>> What is your opinion on this patch (and the solution) in general?
>>>>>>
>>>>>>
>>>>>>
>>>>>> -Wei
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
>>>>>> Sent: Thursday, October 07, 2010 6:58 PM
>>>>>> To: Huang2, Wei; Ian Jackson
>>>>>> Cc: Xen-devel
>>>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Wei,
>>>>>>
>>>>>>
>>>>>>
>>>>>> This patch did not cause any problems with Intel IGD passthrough for
>>>>>> me.
>>>>>> However, the monitor remained blank if I pass through ATI Firepro V3750
>>>>>> either as the primary display device or the secondary device
>>>>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
>>>>>> work.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Have you tested the patch with this graphics card?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Allen
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
>>>>>> Sent: Thursday, October 07, 2010 9:57 AM
>>>>>> To: Ian Jackson
>>>>>> Cc: Xen-devel; Kay, Allen M
>>>>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Ian,
>>>>>>
>>>>>>
>>>>>>
>>>>>> There have been a lot of interest on gfx passthru recently. This patch
>>>>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
>>>>>> Windows boot logo) can now show in passthru screen. We have tested with
>>>>>> various Windows and Linux guest VMs. Please help review it. We are also
>>>>>> looking forward to comments and suggestions from Xen community users.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
>>>>>>
>>>>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing list
>>>>>> Xen-devel@lists.xensource.com
>>>>>> http://lists.xensource.com/xen-devel
>>>>>
>>>
>>>
>>>
> --
> Best regards,
> Sander mailto:linux@eikelenboom.it
--
Best regards,
Sander mailto:linux@eikelenboom.it
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-13 20:33 ` Huang2, Wei
2010-12-13 20:47 ` Sander Eikelenboom
@ 2010-12-16 18:29 ` Pasi Kärkkäinen
2010-12-17 7:03 ` Wei Huang
1 sibling, 1 reply; 32+ messages in thread
From: Pasi Kärkkäinen @ 2010-12-16 18:29 UTC (permalink / raw)
To: Huang2, Wei
Cc: Xen-devel, Keir Fraser, Jackson, Kay, Allen M, Wang2, Wei,
Sander Eikelenboom, djmagee@mageenet.net, Ian
On Mon, Dec 13, 2010 at 02:33:02PM -0600, Huang2, Wei wrote:
> Hi Sander,
>
> I answer your questions (including the one from last email) below:
>
> 1. Your gfx is a bit old. Some of the tricks (such as MMINDEX values 0x4010) aren't quite consistent across different generations of ATI gfx. I need to look at the log myself. I will locate an HD3000 card to debug.
> 2. The goal of this patch is to passthru the primary gfx as THE ONLY GFX inside guest VM (namely: my patch + set gfx_passthru=1 in guest config file). Since you are passthru the on-board secondary gfx, I am not sure qemu-dm is copying the correct VBIOS from address 0xc0000. One solution is to force VBIOS been read from a file, which can be downloaded from http://www.techpowerup.com/vgabios/.
>
Do you happen to have a patch that allows specifying the file to load the vga bios
from in the xen /etc/xen/<guest> cfgfile ?
That'd be helpful for the time being..
-- Pasi
> 3. Note that current Xen support passthru ATI gfx as a secondary gfx, even without my patch. So if you don't care about primary/secondary, you probably don't need this patch. Have you tried: existing Xen + passthru ATI without gfx_passthru=1? As for as I have seen, it worked for many ATI gfx.
>
> Thanks,
> -Wei
>
> -----Original Message-----
> From: Sander Eikelenboom [mailto:linux@eikelenboom.it]
> Sent: Monday, December 13, 2010 2:18 PM
> To: Huang2, Wei
> Cc: Keir Fraser; Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
> Hello Wei,
>
> It just occured to me, this is probably only working when trying to passthrough the primary graphics card ?
> I'm trying to passthrough a secondary card, so the primary(boot) card still has the xen/dom0 console.
>
> It could end up giving problems by loading the wrong/no bios in the hvmloader ?
>
> Should passing though a secondary graphics card also be possible with this patch ?
>
> --
> Sander
>
> Sunday, December 12, 2010, 7:19:08 AM, you wrote:
>
> > This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
>
> > Thanks,
> > -Wei
> > ________________________________________
> > From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> > Sent: Saturday, December 11, 2010 9:38 AM
> > To: Sander Eikelenboom; Huang2, Wei
> > Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> > Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
> > The patch would need some work to make it suitable for check in and get it
> > working for stubdom. At the very least the ioperm() calls would need
> > removing completely, or stubbing out for the stubdom build.
>
> > -- Keir
>
> > On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
>
> >> Do i need any previous patches for this to work ?
> >>
> >> After applying it to xen-unstable, compiling xen results in:
> >>
> >> make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> >> [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
> >> [ -e include/mini-os ] || ln -sf . include/mini-os
> >> [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
> >> make --directory=arch/x86
> >> OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
> >> exit 1;
> >> make[3]: Entering directory
> >> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> >> make[3]: Nothing to be done for `all'.
> >> make[3]: Leaving directory
> >> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> >> ld -r -nostdlib
> >> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> >> -m elf_x86_64
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
> >> .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
> >> -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
> >> -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> >> objcopy -w -G xenos_* -G _start
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> >> ld -nostdlib
> >> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> >> -m elf_x86_64 -T arch/x86/minios-x86_64.lds
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> >> function `ati_hw_out':
> >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
> >> reference to `ioperm'
> >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
> >> reference to `ioperm'
> >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> >> function `ati_hw_in':
> >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
> >> reference to `ioperm'
> >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
> >> reference to `ioperm'
> >> make[2]: ***
> >> [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
> >> make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> >> make[1]: *** [ioemu-stubdom] Error 2
> >> make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
> >> make: *** [install-stubdom] Error 2
> >>
> >> Don't know why the include of sys/io.h doesn't seem to work
> >> --
> >>
> >> Sander
> >>
> >> Saturday, December 11, 2010, 12:40:19 AM, you wrote:
> >>
> >>> Hi,
> >>
> >>> The attached patch supports dynamic detection of BARs (both MMIO and
> >>> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
> >>> passthru. Please let me know whether it works better for you.
> >>
> >>> Thanks,
> >>> -Wei
> >>
> >>> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
> >>>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> >>>>> Sorry, hold on a second. This fix seems corrupt my pci config space
> >>>>> after
> >>>>> several runs.
> >>>>>
> >>>> Hello,
> >>>>
> >>>> Any updates to these patches? Many users have been asking about amd/ati vga
> >>>> passthru stuff..
> >>>>
> >>>> -- Pasi
> >>>>
> >>>>>
> >>>>> -Wei
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: xen-devel-bounces@lists.xensource.com
> >>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> >>>>> Sent: Wednesday, October 13, 2010 3:47 PM
> >>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> >>>>> Cc: Wang2, Wei; Xen-devel
> >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>>> support
> >>>>>
> >>>>>
> >>>>>
> >>>>> Hi Allen and Doug,
> >>>>>
> >>>>>
> >>>>>
> >>>>> Could you fix the following line in save_pci_conf_space() of
> >>>>> tools/python/xen/util/pci.py?
> >>>>>
> >>>>>
> >>>>>
> >>>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
> >>>>>
> >>>>>
> >>>>>
> >>>>> This solves my black screen issue. Please let me know the results.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> -Wei
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> >>>>> Sent: Friday, October 08, 2010 10:53 AM
> >>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> >>>>> Cc: Xen-devel; Wang2, Wei
> >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>>> support
> >>>>>
> >>>>>
> >>>>>
> >>>>> Wei,
> >>>>>
> >>>>> These were guests that had never seen the catalyst
> >>>>> driver
> >>>>> before. I booted each three with the graphics device and usb devices
> >>>>> assigned, they worked fine using the basic VGA driver, then installed
> >>>>> fresh Catalyst 10.9, rebooted, and each one crashed.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Let me know if there's any other info I can provide
> >>>>> that
> >>>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
> >>>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
> >>>>> pvops
> >>>>> Dom0 from stable-2.6.32.x commit 179eca50.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Doug Magee
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> >>>>> Sent: Friday, October 08, 2010 11:41 AM
> >>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> >>>>> Cc: Xen-devel; Wang2, Wei
> >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>>> support
> >>>>>
> >>>>>
> >>>>>
> >>>>> Hi Doug,
> >>>>>
> >>>>>
> >>>>>
> >>>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> >>>>> Catalyst installation or an existing guest image? We felt this VBIOS
> >>>>> patch
> >>>>> might not provide all necessary resources to driver, which got upset.
> >>>>> Currently we are debugging it with our driver team and will let you
> >>>>> know
> >>>>> the update.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> -Wei
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> >>>>> Sent: Friday, October 08, 2010 9:41 AM
> >>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> >>>>> Cc: Xen-devel
> >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>>> support
> >>>>>
> >>>>>
> >>>>>
> >>>>> Wei,
> >>>>>
> >>>>> I've tested with a Radeon 4770 and it the VBIOS works
> >>>>> without a problem, through many guest (re)boots, so it seems pretty
> >>>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> >>>>> and Windows 7 (without accelerated drivers). The open radeon linux
> >>>>> driver
> >>>>> works fine.
> >>>>>
> >>>>>
> >>>>>
> >>>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
> >>>>> in
> >>>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> >>>>> reset?), and linux (total system freeze). This seems to be different
> >>>>> than
> >>>>> the `Blank Screen' problem you report, as the driver is clearly not
> >>>>> functioning properly.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Doug Magee
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: xen-devel-bounces@lists.xensource.com
> >>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> >>>>> Sent: Friday, October 08, 2010 9:57 AM
> >>>>> To: Kay, Allen M; Ian Jackson
> >>>>> Cc: Xen-devel
> >>>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>>> support
> >>>>>
> >>>>>
> >>>>>
> >>>>> Hi Allen,
> >>>>>
> >>>>>
> >>>>>
> >>>>> Yes, Catalyst driver is the one from public website. The driver still
> >>>>> has
> >>>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> >>>>> patch is to get community feedbacks. After we figure out the root cause
> >>>>> of
> >>>>> black screen, I will formally submit a patch for inclusion.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> -Wei
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> >>>>> Sent: Friday, October 08, 2010 2:21 AM
> >>>>> To: Huang2, Wei; Ian Jackson
> >>>>> Cc: Xen-devel
> >>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>>
> >>>>>
> >>>>>
> >>>>> Hi Wei,
> >>>>>
> >>>>>
> >>>>>
> >>>>> Is Catalyst driver the one on AMD website? I think that's what I have
> >>>>> in
> >>>>> my win7 guest and it matches the symptom you are describing. "lspci"
> >>>>> reports my ATI card is a V5700 - although it says v3750 on the box.
> >>>>> Where
> >>>>> can I get a working driver?
> >>>>>
> >>>>>
> >>>>>
> >>>>> The patch looks reasonable to me in general.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Allen
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> >>>>> Sent: Thursday, October 07, 2010 9:06 PM
> >>>>> To: Kay, Allen M; Ian Jackson
> >>>>> Cc: Xen-devel
> >>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>>
> >>>>>
> >>>>>
> >>>>> Hi Allen,
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
> >>>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
> >>>>> V3750
> >>>>> at hand. It is very possible this patch isn't compatible with V3750. We
> >>>>> will try to get hold of one for debugging. For graphics which work with
> >>>>> this path, users should be able to get rid of emulated gfx (such as
> >>>>> Cirrus). I have successfully installed a Windows guest VM using this
> >>>>> patch.
> >>>>>
> >>>>>
> >>>>>
> >>>>> I also want to point out that there is still an issue. Users will see a
> >>>>> black screen after installing Catalyst driver. Even though the screen
> >>>>> appears to be black, the driver is actually functioning correctly
> >>>>> (3DMark
> >>>>> can be run with external monitor). Our driver team is currently
> >>>>> debugging
> >>>>> it and they believe this is easy to fix.
> >>>>>
> >>>>>
> >>>>>
> >>>>> What is your opinion on this patch (and the solution) in general?
> >>>>>
> >>>>>
> >>>>>
> >>>>> -Wei
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> >>>>> Sent: Thursday, October 07, 2010 6:58 PM
> >>>>> To: Huang2, Wei; Ian Jackson
> >>>>> Cc: Xen-devel
> >>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>>
> >>>>>
> >>>>>
> >>>>> Hi Wei,
> >>>>>
> >>>>>
> >>>>>
> >>>>> This patch did not cause any problems with Intel IGD passthrough for
> >>>>> me.
> >>>>> However, the monitor remained blank if I pass through ATI Firepro V3750
> >>>>> either as the primary display device or the secondary device
> >>>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
> >>>>> work.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Have you tested the patch with this graphics card?
> >>>>>
> >>>>>
> >>>>>
> >>>>> Allen
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> >>>>> Sent: Thursday, October 07, 2010 9:57 AM
> >>>>> To: Ian Jackson
> >>>>> Cc: Xen-devel; Kay, Allen M
> >>>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>>
> >>>>>
> >>>>>
> >>>>> Hi Ian,
> >>>>>
> >>>>>
> >>>>>
> >>>>> There have been a lot of interest on gfx passthru recently. This patch
> >>>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> >>>>> Windows boot logo) can now show in passthru screen. We have tested with
> >>>>> various Windows and Linux guest VMs. Please help review it. We are also
> >>>>> looking forward to comments and suggestions from Xen community users.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
> >>>>>
> >>>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Xen-devel mailing list
> >>>>> Xen-devel@lists.xensource.com
> >>>>> http://lists.xensource.com/xen-devel
> >>>>
> >>
> >>
> >>
>
>
>
>
>
>
>
> --
> Best regards,
> Sander mailto:linux@eikelenboom.it
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-16 18:29 ` Pasi Kärkkäinen
@ 2010-12-17 7:03 ` Wei Huang
2010-12-17 7:13 ` Pasi Kärkkäinen
0 siblings, 1 reply; 32+ messages in thread
From: Wei Huang @ 2010-12-17 7:03 UTC (permalink / raw)
To: Pasi Kärkkäinen
Cc: Xen-devel, Keir Fraser, Jackson, Kay, Allen M, Wang2, Wei,
Sander Eikelenboom, djmagee@mageenet.net, Ian@ikuisesti.iki.fi
Hi Pasi,
Users can do it in setup_vga_pt() in pt-graphics.c with something like:
+ int fd;
+ fd = open("/tmp/downloaded_vbios.bin", O_RDONLY);
+ bios_size = read(fd, bios, bios_size);
+ close(fd);
Then we can pass bios_size and bios to cpu_physical_memory_rw()
function.
-Wei
On Thu, 2010-12-16 at 12:29 -0600, Pasi Kärkkäinen wrote:
> On Mon, Dec 13, 2010 at 02:33:02PM -0600, Huang2, Wei wrote:
> > Hi Sander,
> >
> > I answer your questions (including the one from last email) below:
> >
> > 1. Your gfx is a bit old. Some of the tricks (such as MMINDEX values 0x4010) aren't quite consistent across different generations of ATI gfx. I need to look at the log myself. I will locate an HD3000 card to debug.
> > 2. The goal of this patch is to passthru the primary gfx as THE ONLY GFX inside guest VM (namely: my patch + set gfx_passthru=1 in guest config file). Since you are passthru the on-board secondary gfx, I am not sure qemu-dm is copying the correct VBIOS from address 0xc0000. One solution is to force VBIOS been read from a file, which can be downloaded from http://www.techpowerup.com/vgabios/.
> >
>
> Do you happen to have a patch that allows specifying the file to load the vga bios
> from in the xen /etc/xen/<guest> cfgfile ?
>
> That'd be helpful for the time being..
>
> -- Pasi
>
> > 3. Note that current Xen support passthru ATI gfx as a secondary gfx, even without my patch. So if you don't care about primary/secondary, you probably don't need this patch. Have you tried: existing Xen + passthru ATI without gfx_passthru=1? As for as I have seen, it worked for many ATI gfx.
> >
> > Thanks,
> > -Wei
> >
> > -----Original Message-----
> > From: Sander Eikelenboom [mailto:linux@eikelenboom.it]
> > Sent: Monday, December 13, 2010 2:18 PM
> > To: Huang2, Wei
> > Cc: Keir Fraser; Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> > Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >
> > Hello Wei,
> >
> > It just occured to me, this is probably only working when trying to passthrough the primary graphics card ?
> > I'm trying to passthrough a secondary card, so the primary(boot) card still has the xen/dom0 console.
> >
> > It could end up giving problems by loading the wrong/no bios in the hvmloader ?
> >
> > Should passing though a secondary graphics card also be possible with this patch ?
> >
> > --
> > Sander
> >
> > Sunday, December 12, 2010, 7:19:08 AM, you wrote:
> >
> > > This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
> >
> > > Thanks,
> > > -Wei
> > > ________________________________________
> > > From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> > > Sent: Saturday, December 11, 2010 9:38 AM
> > > To: Sander Eikelenboom; Huang2, Wei
> > > Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> > > Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >
> > > The patch would need some work to make it suitable for check in and get it
> > > working for stubdom. At the very least the ioperm() calls would need
> > > removing completely, or stubbing out for the stubdom build.
> >
> > > -- Keir
> >
> > > On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
> >
> > >> Do i need any previous patches for this to work ?
> > >>
> > >> After applying it to xen-unstable, compiling xen results in:
> > >>
> > >> make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > >> [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
> > >> [ -e include/mini-os ] || ln -sf . include/mini-os
> > >> [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
> > >> make --directory=arch/x86
> > >> OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
> > >> exit 1;
> > >> make[3]: Entering directory
> > >> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > >> make[3]: Nothing to be done for `all'.
> > >> make[3]: Leaving directory
> > >> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > >> ld -r -nostdlib
> > >> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > >> -m elf_x86_64
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
> > >> .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
> > >> -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
> > >> -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > >> objcopy -w -G xenos_* -G _start
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > >> ld -nostdlib
> > >> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > >> -m elf_x86_64 -T arch/x86/minios-x86_64.lds
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > >> function `ati_hw_out':
> > >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
> > >> reference to `ioperm'
> > >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
> > >> reference to `ioperm'
> > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > >> function `ati_hw_in':
> > >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
> > >> reference to `ioperm'
> > >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
> > >> reference to `ioperm'
> > >> make[2]: ***
> > >> [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
> > >> make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > >> make[1]: *** [ioemu-stubdom] Error 2
> > >> make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
> > >> make: *** [install-stubdom] Error 2
> > >>
> > >> Don't know why the include of sys/io.h doesn't seem to work
> > >> --
> > >>
> > >> Sander
> > >>
> > >> Saturday, December 11, 2010, 12:40:19 AM, you wrote:
> > >>
> > >>> Hi,
> > >>
> > >>> The attached patch supports dynamic detection of BARs (both MMIO and
> > >>> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
> > >>> passthru. Please let me know whether it works better for you.
> > >>
> > >>> Thanks,
> > >>> -Wei
> > >>
> > >>> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
> > >>>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> > >>>>> Sorry, hold on a second. This fix seems corrupt my pci config space
> > >>>>> after
> > >>>>> several runs.
> > >>>>>
> > >>>> Hello,
> > >>>>
> > >>>> Any updates to these patches? Many users have been asking about amd/ati vga
> > >>>> passthru stuff..
> > >>>>
> > >>>> -- Pasi
> > >>>>
> > >>>>>
> > >>>>> -Wei
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: xen-devel-bounces@lists.xensource.com
> > >>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > >>>>> Sent: Wednesday, October 13, 2010 3:47 PM
> > >>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > >>>>> Cc: Wang2, Wei; Xen-devel
> > >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>>> support
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Hi Allen and Doug,
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Could you fix the following line in save_pci_conf_space() of
> > >>>>> tools/python/xen/util/pci.py?
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> This solves my black screen issue. Please let me know the results.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Thanks,
> > >>>>>
> > >>>>> -Wei
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > >>>>> Sent: Friday, October 08, 2010 10:53 AM
> > >>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > >>>>> Cc: Xen-devel; Wang2, Wei
> > >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>>> support
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Wei,
> > >>>>>
> > >>>>> These were guests that had never seen the catalyst
> > >>>>> driver
> > >>>>> before. I booted each three with the graphics device and usb devices
> > >>>>> assigned, they worked fine using the basic VGA driver, then installed
> > >>>>> fresh Catalyst 10.9, rebooted, and each one crashed.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Let me know if there's any other info I can provide
> > >>>>> that
> > >>>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
> > >>>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
> > >>>>> pvops
> > >>>>> Dom0 from stable-2.6.32.x commit 179eca50.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Doug Magee
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > >>>>> Sent: Friday, October 08, 2010 11:41 AM
> > >>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > >>>>> Cc: Xen-devel; Wang2, Wei
> > >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>>> support
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Hi Doug,
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> > >>>>> Catalyst installation or an existing guest image? We felt this VBIOS
> > >>>>> patch
> > >>>>> might not provide all necessary resources to driver, which got upset.
> > >>>>> Currently we are debugging it with our driver team and will let you
> > >>>>> know
> > >>>>> the update.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Thanks,
> > >>>>>
> > >>>>> -Wei
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > >>>>> Sent: Friday, October 08, 2010 9:41 AM
> > >>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > >>>>> Cc: Xen-devel
> > >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>>> support
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Wei,
> > >>>>>
> > >>>>> I've tested with a Radeon 4770 and it the VBIOS works
> > >>>>> without a problem, through many guest (re)boots, so it seems pretty
> > >>>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> > >>>>> and Windows 7 (without accelerated drivers). The open radeon linux
> > >>>>> driver
> > >>>>> works fine.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
> > >>>>> in
> > >>>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> > >>>>> reset?), and linux (total system freeze). This seems to be different
> > >>>>> than
> > >>>>> the `Blank Screen' problem you report, as the driver is clearly not
> > >>>>> functioning properly.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Doug Magee
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: xen-devel-bounces@lists.xensource.com
> > >>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > >>>>> Sent: Friday, October 08, 2010 9:57 AM
> > >>>>> To: Kay, Allen M; Ian Jackson
> > >>>>> Cc: Xen-devel
> > >>>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>>> support
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Hi Allen,
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Yes, Catalyst driver is the one from public website. The driver still
> > >>>>> has
> > >>>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> > >>>>> patch is to get community feedbacks. After we figure out the root cause
> > >>>>> of
> > >>>>> black screen, I will formally submit a patch for inclusion.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Thanks,
> > >>>>>
> > >>>>> -Wei
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > >>>>> Sent: Friday, October 08, 2010 2:21 AM
> > >>>>> To: Huang2, Wei; Ian Jackson
> > >>>>> Cc: Xen-devel
> > >>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Hi Wei,
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Is Catalyst driver the one on AMD website? I think that's what I have
> > >>>>> in
> > >>>>> my win7 guest and it matches the symptom you are describing. "lspci"
> > >>>>> reports my ATI card is a V5700 - although it says v3750 on the box.
> > >>>>> Where
> > >>>>> can I get a working driver?
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> The patch looks reasonable to me in general.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Allen
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > >>>>> Sent: Thursday, October 07, 2010 9:06 PM
> > >>>>> To: Kay, Allen M; Ian Jackson
> > >>>>> Cc: Xen-devel
> > >>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Hi Allen,
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
> > >>>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
> > >>>>> V3750
> > >>>>> at hand. It is very possible this patch isn't compatible with V3750. We
> > >>>>> will try to get hold of one for debugging. For graphics which work with
> > >>>>> this path, users should be able to get rid of emulated gfx (such as
> > >>>>> Cirrus). I have successfully installed a Windows guest VM using this
> > >>>>> patch.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> I also want to point out that there is still an issue. Users will see a
> > >>>>> black screen after installing Catalyst driver. Even though the screen
> > >>>>> appears to be black, the driver is actually functioning correctly
> > >>>>> (3DMark
> > >>>>> can be run with external monitor). Our driver team is currently
> > >>>>> debugging
> > >>>>> it and they believe this is easy to fix.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> What is your opinion on this patch (and the solution) in general?
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> -Wei
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > >>>>> Sent: Thursday, October 07, 2010 6:58 PM
> > >>>>> To: Huang2, Wei; Ian Jackson
> > >>>>> Cc: Xen-devel
> > >>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Hi Wei,
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> This patch did not cause any problems with Intel IGD passthrough for
> > >>>>> me.
> > >>>>> However, the monitor remained blank if I pass through ATI Firepro V3750
> > >>>>> either as the primary display device or the secondary device
> > >>>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
> > >>>>> work.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Have you tested the patch with this graphics card?
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Allen
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > >>>>> Sent: Thursday, October 07, 2010 9:57 AM
> > >>>>> To: Ian Jackson
> > >>>>> Cc: Xen-devel; Kay, Allen M
> > >>>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Hi Ian,
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> There have been a lot of interest on gfx passthru recently. This patch
> > >>>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> > >>>>> Windows boot logo) can now show in passthru screen. We have tested with
> > >>>>> various Windows and Linux guest VMs. Please help review it. We are also
> > >>>>> looking forward to comments and suggestions from Xen community users.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
> > >>>>>
> > >>>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> Xen-devel mailing list
> > >>>>> Xen-devel@lists.xensource.com
> > >>>>> http://lists.xensource.com/xen-devel
> > >>>>
> > >>
> > >>
> > >>
> >
> >
> >
> >
> >
> >
> >
> > --
> > Best regards,
> > Sander mailto:linux@eikelenboom.it
> >
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-17 7:03 ` Wei Huang
@ 2010-12-17 7:13 ` Pasi Kärkkäinen
0 siblings, 0 replies; 32+ messages in thread
From: Pasi Kärkkäinen @ 2010-12-17 7:13 UTC (permalink / raw)
To: Wei Huang
Cc: Xen-devel, Keir Fraser, Jackson, Kay, Allen M, Wang2, Wei,
Sander Eikelenboom, djmagee@mageenet.net, Ian@ikuisesti.iki.fi
On Fri, Dec 17, 2010 at 01:03:14AM -0600, Wei Huang wrote:
> Hi Pasi,
>
> Users can do it in setup_vga_pt() in pt-graphics.c with something like:
>
> + int fd;
> + fd = open("/tmp/downloaded_vbios.bin", O_RDONLY);
> + bios_size = read(fd, bios, bios_size);
> + close(fd);
>
> Then we can pass bios_size and bios to cpu_physical_memory_rw()
> function.
>
Yep, I know, but I was thinking of making it easier for users
to experiment with VGA passthru.. not having to modify the sources
and re-compile.
Thanks anyway :)
-- Pasi
>
> On Thu, 2010-12-16 at 12:29 -0600, Pasi Kärkkäinen wrote:
> > On Mon, Dec 13, 2010 at 02:33:02PM -0600, Huang2, Wei wrote:
> > > Hi Sander,
> > >
> > > I answer your questions (including the one from last email) below:
> > >
> > > 1. Your gfx is a bit old. Some of the tricks (such as MMINDEX values 0x4010) aren't quite consistent across different generations of ATI gfx. I need to look at the log myself. I will locate an HD3000 card to debug.
> > > 2. The goal of this patch is to passthru the primary gfx as THE ONLY GFX inside guest VM (namely: my patch + set gfx_passthru=1 in guest config file). Since you are passthru the on-board secondary gfx, I am not sure qemu-dm is copying the correct VBIOS from address 0xc0000. One solution is to force VBIOS been read from a file, which can be downloaded from http://www.techpowerup.com/vgabios/.
> > >
> >
> > Do you happen to have a patch that allows specifying the file to load the vga bios
> > from in the xen /etc/xen/<guest> cfgfile ?
> >
> > That'd be helpful for the time being..
> >
> > -- Pasi
> >
> > > 3. Note that current Xen support passthru ATI gfx as a secondary gfx, even without my patch. So if you don't care about primary/secondary, you probably don't need this patch. Have you tried: existing Xen + passthru ATI without gfx_passthru=1? As for as I have seen, it worked for many ATI gfx.
> > >
> > > Thanks,
> > > -Wei
> > >
> > > -----Original Message-----
> > > From: Sander Eikelenboom [mailto:linux@eikelenboom.it]
> > > Sent: Monday, December 13, 2010 2:18 PM
> > > To: Huang2, Wei
> > > Cc: Keir Fraser; Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> > > Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >
> > > Hello Wei,
> > >
> > > It just occured to me, this is probably only working when trying to passthrough the primary graphics card ?
> > > I'm trying to passthrough a secondary card, so the primary(boot) card still has the xen/dom0 console.
> > >
> > > It could end up giving problems by loading the wrong/no bios in the hvmloader ?
> > >
> > > Should passing though a secondary graphics card also be possible with this patch ?
> > >
> > > --
> > > Sander
> > >
> > > Sunday, December 12, 2010, 7:19:08 AM, you wrote:
> > >
> > > > This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
> > >
> > > > Thanks,
> > > > -Wei
> > > > ________________________________________
> > > > From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> > > > Sent: Saturday, December 11, 2010 9:38 AM
> > > > To: Sander Eikelenboom; Huang2, Wei
> > > > Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> > > > Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >
> > > > The patch would need some work to make it suitable for check in and get it
> > > > working for stubdom. At the very least the ioperm() calls would need
> > > > removing completely, or stubbing out for the stubdom build.
> > >
> > > > -- Keir
> > >
> > > > On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
> > >
> > > >> Do i need any previous patches for this to work ?
> > > >>
> > > >> After applying it to xen-unstable, compiling xen results in:
> > > >>
> > > >> make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > > >> [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
> > > >> [ -e include/mini-os ] || ln -sf . include/mini-os
> > > >> [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
> > > >> make --directory=arch/x86
> > > >> OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
> > > >> exit 1;
> > > >> make[3]: Entering directory
> > > >> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > > >> make[3]: Nothing to be done for `all'.
> > > >> make[3]: Leaving directory
> > > >> `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > > >> ld -r -nostdlib
> > > >> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > > >> -m elf_x86_64
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
> > > >> .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
> > > >> -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
> > > >> -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > > >> objcopy -w -G xenos_* -G _start
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > > >> ld -nostdlib
> > > >> -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > > >> -m elf_x86_64 -T arch/x86/minios-x86_64.lds
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > > >> function `ati_hw_out':
> > > >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
> > > >> reference to `ioperm'
> > > >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
> > > >> reference to `ioperm'
> > > >> /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > > >> function `ati_hw_in':
> > > >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
> > > >> reference to `ioperm'
> > > >> /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
> > > >> reference to `ioperm'
> > > >> make[2]: ***
> > > >> [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
> > > >> make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > > >> make[1]: *** [ioemu-stubdom] Error 2
> > > >> make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
> > > >> make: *** [install-stubdom] Error 2
> > > >>
> > > >> Don't know why the include of sys/io.h doesn't seem to work
> > > >> --
> > > >>
> > > >> Sander
> > > >>
> > > >> Saturday, December 11, 2010, 12:40:19 AM, you wrote:
> > > >>
> > > >>> Hi,
> > > >>
> > > >>> The attached patch supports dynamic detection of BARs (both MMIO and
> > > >>> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
> > > >>> passthru. Please let me know whether it works better for you.
> > > >>
> > > >>> Thanks,
> > > >>> -Wei
> > > >>
> > > >>> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
> > > >>>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> > > >>>>> Sorry, hold on a second. This fix seems corrupt my pci config space
> > > >>>>> after
> > > >>>>> several runs.
> > > >>>>>
> > > >>>> Hello,
> > > >>>>
> > > >>>> Any updates to these patches? Many users have been asking about amd/ati vga
> > > >>>> passthru stuff..
> > > >>>>
> > > >>>> -- Pasi
> > > >>>>
> > > >>>>>
> > > >>>>> -Wei
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> From: xen-devel-bounces@lists.xensource.com
> > > >>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > > >>>>> Sent: Wednesday, October 13, 2010 3:47 PM
> > > >>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > > >>>>> Cc: Wang2, Wei; Xen-devel
> > > >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > > >>>>> support
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Hi Allen and Doug,
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Could you fix the following line in save_pci_conf_space() of
> > > >>>>> tools/python/xen/util/pci.py?
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> This solves my black screen issue. Please let me know the results.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Thanks,
> > > >>>>>
> > > >>>>> -Wei
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > > >>>>> Sent: Friday, October 08, 2010 10:53 AM
> > > >>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > > >>>>> Cc: Xen-devel; Wang2, Wei
> > > >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > > >>>>> support
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Wei,
> > > >>>>>
> > > >>>>> These were guests that had never seen the catalyst
> > > >>>>> driver
> > > >>>>> before. I booted each three with the graphics device and usb devices
> > > >>>>> assigned, they worked fine using the basic VGA driver, then installed
> > > >>>>> fresh Catalyst 10.9, rebooted, and each one crashed.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Let me know if there's any other info I can provide
> > > >>>>> that
> > > >>>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
> > > >>>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
> > > >>>>> pvops
> > > >>>>> Dom0 from stable-2.6.32.x commit 179eca50.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Doug Magee
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > > >>>>> Sent: Friday, October 08, 2010 11:41 AM
> > > >>>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > > >>>>> Cc: Xen-devel; Wang2, Wei
> > > >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > > >>>>> support
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Hi Doug,
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> > > >>>>> Catalyst installation or an existing guest image? We felt this VBIOS
> > > >>>>> patch
> > > >>>>> might not provide all necessary resources to driver, which got upset.
> > > >>>>> Currently we are debugging it with our driver team and will let you
> > > >>>>> know
> > > >>>>> the update.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Thanks,
> > > >>>>>
> > > >>>>> -Wei
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > > >>>>> Sent: Friday, October 08, 2010 9:41 AM
> > > >>>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > > >>>>> Cc: Xen-devel
> > > >>>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > > >>>>> support
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Wei,
> > > >>>>>
> > > >>>>> I've tested with a Radeon 4770 and it the VBIOS works
> > > >>>>> without a problem, through many guest (re)boots, so it seems pretty
> > > >>>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> > > >>>>> and Windows 7 (without accelerated drivers). The open radeon linux
> > > >>>>> driver
> > > >>>>> works fine.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
> > > >>>>> in
> > > >>>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> > > >>>>> reset?), and linux (total system freeze). This seems to be different
> > > >>>>> than
> > > >>>>> the `Blank Screen' problem you report, as the driver is clearly not
> > > >>>>> functioning properly.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Doug Magee
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> From: xen-devel-bounces@lists.xensource.com
> > > >>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > > >>>>> Sent: Friday, October 08, 2010 9:57 AM
> > > >>>>> To: Kay, Allen M; Ian Jackson
> > > >>>>> Cc: Xen-devel
> > > >>>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > > >>>>> support
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Hi Allen,
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Yes, Catalyst driver is the one from public website. The driver still
> > > >>>>> has
> > > >>>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> > > >>>>> patch is to get community feedbacks. After we figure out the root cause
> > > >>>>> of
> > > >>>>> black screen, I will formally submit a patch for inclusion.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Thanks,
> > > >>>>>
> > > >>>>> -Wei
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > > >>>>> Sent: Friday, October 08, 2010 2:21 AM
> > > >>>>> To: Huang2, Wei; Ian Jackson
> > > >>>>> Cc: Xen-devel
> > > >>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Hi Wei,
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Is Catalyst driver the one on AMD website? I think that's what I have
> > > >>>>> in
> > > >>>>> my win7 guest and it matches the symptom you are describing. "lspci"
> > > >>>>> reports my ATI card is a V5700 - although it says v3750 on the box.
> > > >>>>> Where
> > > >>>>> can I get a working driver?
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> The patch looks reasonable to me in general.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Allen
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > > >>>>> Sent: Thursday, October 07, 2010 9:06 PM
> > > >>>>> To: Kay, Allen M; Ian Jackson
> > > >>>>> Cc: Xen-devel
> > > >>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Hi Allen,
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
> > > >>>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
> > > >>>>> V3750
> > > >>>>> at hand. It is very possible this patch isn't compatible with V3750. We
> > > >>>>> will try to get hold of one for debugging. For graphics which work with
> > > >>>>> this path, users should be able to get rid of emulated gfx (such as
> > > >>>>> Cirrus). I have successfully installed a Windows guest VM using this
> > > >>>>> patch.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> I also want to point out that there is still an issue. Users will see a
> > > >>>>> black screen after installing Catalyst driver. Even though the screen
> > > >>>>> appears to be black, the driver is actually functioning correctly
> > > >>>>> (3DMark
> > > >>>>> can be run with external monitor). Our driver team is currently
> > > >>>>> debugging
> > > >>>>> it and they believe this is easy to fix.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> What is your opinion on this patch (and the solution) in general?
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> -Wei
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > > >>>>> Sent: Thursday, October 07, 2010 6:58 PM
> > > >>>>> To: Huang2, Wei; Ian Jackson
> > > >>>>> Cc: Xen-devel
> > > >>>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Hi Wei,
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> This patch did not cause any problems with Intel IGD passthrough for
> > > >>>>> me.
> > > >>>>> However, the monitor remained blank if I pass through ATI Firepro V3750
> > > >>>>> either as the primary display device or the secondary device
> > > >>>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
> > > >>>>> work.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Have you tested the patch with this graphics card?
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Allen
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > > >>>>> Sent: Thursday, October 07, 2010 9:57 AM
> > > >>>>> To: Ian Jackson
> > > >>>>> Cc: Xen-devel; Kay, Allen M
> > > >>>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Hi Ian,
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> There have been a lot of interest on gfx passthru recently. This patch
> > > >>>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> > > >>>>> Windows boot logo) can now show in passthru screen. We have tested with
> > > >>>>> various Windows and Linux guest VMs. Please help review it. We are also
> > > >>>>> looking forward to comments and suggestions from Xen community users.
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
> > > >>>>>
> > > >>>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> _______________________________________________
> > > >>>>> Xen-devel mailing list
> > > >>>>> Xen-devel@lists.xensource.com
> > > >>>>> http://lists.xensource.com/xen-devel
> > > >>>>
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Sander mailto:linux@eikelenboom.it
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> >
>
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2010-12-12 6:19 ` Huang2, Wei
2010-12-12 19:10 ` Sander Eikelenboom
2010-12-13 20:17 ` Sander Eikelenboom
@ 2011-01-06 17:23 ` Pasi Kärkkäinen
2011-01-06 19:56 ` Huang2, Wei
2 siblings, 1 reply; 32+ messages in thread
From: Pasi Kärkkäinen @ 2011-01-06 17:23 UTC (permalink / raw)
To: Huang2, Wei
Cc: Xen-devel, Keir Fraser, Ian Jackson, Kay, Allen M, Wang2, Wei,
Sander Eikelenboom, djmagee@mageenet.net
On Sun, Dec 12, 2010 at 12:19:08AM -0600, Huang2, Wei wrote:
> This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
>
Any plans for the "final version" ?
-- Pasi
> Thanks,
> -Wei
> ________________________________________
> From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> Sent: Saturday, December 11, 2010 9:38 AM
> To: Sander Eikelenboom; Huang2, Wei
> Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
> The patch would need some work to make it suitable for check in and get it
> working for stubdom. At the very least the ioperm() calls would need
> removing completely, or stubbing out for the stubdom build.
>
> -- Keir
>
> On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
>
> > Do i need any previous patches for this to work ?
> >
> > After applying it to xen-unstable, compiling xen results in:
> >
> > make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
> > [ -e include/mini-os ] || ln -sf . include/mini-os
> > [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
> > make --directory=arch/x86
> > OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
> > exit 1;
> > make[3]: Entering directory
> > `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > make[3]: Nothing to be done for `all'.
> > make[3]: Leaving directory
> > `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > ld -r -nostdlib
> > -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > -m elf_x86_64
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
> > .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
> > -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
> > -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > objcopy -w -G xenos_* -G _start
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > ld -nostdlib
> > -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > -m elf_x86_64 -T arch/x86/minios-x86_64.lds
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > function `ati_hw_out':
> > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
> > reference to `ioperm'
> > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
> > reference to `ioperm'
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > function `ati_hw_in':
> > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
> > reference to `ioperm'
> > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
> > reference to `ioperm'
> > make[2]: ***
> > [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
> > make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > make[1]: *** [ioemu-stubdom] Error 2
> > make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
> > make: *** [install-stubdom] Error 2
> >
> > Don't know why the include of sys/io.h doesn't seem to work
> > --
> >
> > Sander
> >
> > Saturday, December 11, 2010, 12:40:19 AM, you wrote:
> >
> >> Hi,
> >
> >> The attached patch supports dynamic detection of BARs (both MMIO and
> >> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
> >> passthru. Please let me know whether it works better for you.
> >
> >> Thanks,
> >> -Wei
> >
> >> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
> >>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> >>>> Sorry, hold on a second. This fix seems corrupt my pci config space
> >>>> after
> >>>> several runs.
> >>>>
> >>> Hello,
> >>>
> >>> Any updates to these patches? Many users have been asking about amd/ati vga
> >>> passthru stuff..
> >>>
> >>> -- Pasi
> >>>
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: xen-devel-bounces@lists.xensource.com
> >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> >>>> Sent: Wednesday, October 13, 2010 3:47 PM
> >>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> >>>> Cc: Wang2, Wei; Xen-devel
> >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Hi Allen and Doug,
> >>>>
> >>>>
> >>>>
> >>>> Could you fix the following line in save_pci_conf_space() of
> >>>> tools/python/xen/util/pci.py?
> >>>>
> >>>>
> >>>>
> >>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
> >>>>
> >>>>
> >>>>
> >>>> This solves my black screen issue. Please let me know the results.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> >>>> Sent: Friday, October 08, 2010 10:53 AM
> >>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel; Wang2, Wei
> >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Wei,
> >>>>
> >>>> These were guests that had never seen the catalyst
> >>>> driver
> >>>> before. I booted each three with the graphics device and usb devices
> >>>> assigned, they worked fine using the basic VGA driver, then installed
> >>>> fresh Catalyst 10.9, rebooted, and each one crashed.
> >>>>
> >>>>
> >>>>
> >>>> Let me know if there's any other info I can provide
> >>>> that
> >>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
> >>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
> >>>> pvops
> >>>> Dom0 from stable-2.6.32.x commit 179eca50.
> >>>>
> >>>>
> >>>>
> >>>> Doug Magee
> >>>>
> >>>>
> >>>>
> >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> >>>> Sent: Friday, October 08, 2010 11:41 AM
> >>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel; Wang2, Wei
> >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Hi Doug,
> >>>>
> >>>>
> >>>>
> >>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> >>>> Catalyst installation or an existing guest image? We felt this VBIOS
> >>>> patch
> >>>> might not provide all necessary resources to driver, which got upset.
> >>>> Currently we are debugging it with our driver team and will let you
> >>>> know
> >>>> the update.
> >>>>
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> >>>> Sent: Friday, October 08, 2010 9:41 AM
> >>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Wei,
> >>>>
> >>>> I've tested with a Radeon 4770 and it the VBIOS works
> >>>> without a problem, through many guest (re)boots, so it seems pretty
> >>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> >>>> and Windows 7 (without accelerated drivers). The open radeon linux
> >>>> driver
> >>>> works fine.
> >>>>
> >>>>
> >>>>
> >>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
> >>>> in
> >>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> >>>> reset?), and linux (total system freeze). This seems to be different
> >>>> than
> >>>> the `Blank Screen' problem you report, as the driver is clearly not
> >>>> functioning properly.
> >>>>
> >>>>
> >>>>
> >>>> Doug Magee
> >>>>
> >>>>
> >>>>
> >>>> From: xen-devel-bounces@lists.xensource.com
> >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> >>>> Sent: Friday, October 08, 2010 9:57 AM
> >>>> To: Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Hi Allen,
> >>>>
> >>>>
> >>>>
> >>>> Yes, Catalyst driver is the one from public website. The driver still
> >>>> has
> >>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> >>>> patch is to get community feedbacks. After we figure out the root cause
> >>>> of
> >>>> black screen, I will formally submit a patch for inclusion.
> >>>>
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> >>>> Sent: Friday, October 08, 2010 2:21 AM
> >>>> To: Huang2, Wei; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>
> >>>>
> >>>>
> >>>> Hi Wei,
> >>>>
> >>>>
> >>>>
> >>>> Is Catalyst driver the one on AMD website? I think that's what I have
> >>>> in
> >>>> my win7 guest and it matches the symptom you are describing. "lspci"
> >>>> reports my ATI card is a V5700 - although it says v3750 on the box.
> >>>> Where
> >>>> can I get a working driver?
> >>>>
> >>>>
> >>>>
> >>>> The patch looks reasonable to me in general.
> >>>>
> >>>>
> >>>>
> >>>> Allen
> >>>>
> >>>>
> >>>>
> >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> >>>> Sent: Thursday, October 07, 2010 9:06 PM
> >>>> To: Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>
> >>>>
> >>>>
> >>>> Hi Allen,
> >>>>
> >>>>
> >>>>
> >>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
> >>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
> >>>> V3750
> >>>> at hand. It is very possible this patch isn't compatible with V3750. We
> >>>> will try to get hold of one for debugging. For graphics which work with
> >>>> this path, users should be able to get rid of emulated gfx (such as
> >>>> Cirrus). I have successfully installed a Windows guest VM using this
> >>>> patch.
> >>>>
> >>>>
> >>>>
> >>>> I also want to point out that there is still an issue. Users will see a
> >>>> black screen after installing Catalyst driver. Even though the screen
> >>>> appears to be black, the driver is actually functioning correctly
> >>>> (3DMark
> >>>> can be run with external monitor). Our driver team is currently
> >>>> debugging
> >>>> it and they believe this is easy to fix.
> >>>>
> >>>>
> >>>>
> >>>> What is your opinion on this patch (and the solution) in general?
> >>>>
> >>>>
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> >>>> Sent: Thursday, October 07, 2010 6:58 PM
> >>>> To: Huang2, Wei; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>
> >>>>
> >>>>
> >>>> Hi Wei,
> >>>>
> >>>>
> >>>>
> >>>> This patch did not cause any problems with Intel IGD passthrough for
> >>>> me.
> >>>> However, the monitor remained blank if I pass through ATI Firepro V3750
> >>>> either as the primary display device or the secondary device
> >>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
> >>>> work.
> >>>>
> >>>>
> >>>>
> >>>> Have you tested the patch with this graphics card?
> >>>>
> >>>>
> >>>>
> >>>> Allen
> >>>>
> >>>>
> >>>>
> >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> >>>> Sent: Thursday, October 07, 2010 9:57 AM
> >>>> To: Ian Jackson
> >>>> Cc: Xen-devel; Kay, Allen M
> >>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>
> >>>>
> >>>>
> >>>> Hi Ian,
> >>>>
> >>>>
> >>>>
> >>>> There have been a lot of interest on gfx passthru recently. This patch
> >>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> >>>> Windows boot logo) can now show in passthru screen. We have tested with
> >>>> various Windows and Linux guest VMs. Please help review it. We are also
> >>>> looking forward to comments and suggestions from Xen community users.
> >>>>
> >>>>
> >>>>
> >>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
> >>>>
> >>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2011-01-06 17:23 ` Pasi Kärkkäinen
@ 2011-01-06 19:56 ` Huang2, Wei
2011-01-06 20:05 ` Pasi Kärkkäinen
0 siblings, 1 reply; 32+ messages in thread
From: Huang2, Wei @ 2011-01-06 19:56 UTC (permalink / raw)
To: Pasi Kärkkäinen
Cc: Xen-devel, Keir Fraser, Ian Jackson, Kay, Allen M, Wang2, Wei,
Sander Eikelenboom, djmagee@mageenet.net
Hi Pasi,
No it isn't ready yet. I found some problem with new 6000M GPU. The algorithm doesn't work for this VBIOS. It needs more work before a formal submission.
-Wei
-----Original Message-----
From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
Sent: Thursday, January 06, 2011 11:24 AM
To: Huang2, Wei
Cc: Keir Fraser; Sander Eikelenboom; Wang2, Wei; Kay, Allen M; djmagee@mageenet.net; Xen-devel; Ian Jackson
Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
On Sun, Dec 12, 2010 at 12:19:08AM -0600, Huang2, Wei wrote:
> This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
>
Any plans for the "final version" ?
-- Pasi
> Thanks,
> -Wei
> ________________________________________
> From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> Sent: Saturday, December 11, 2010 9:38 AM
> To: Sander Eikelenboom; Huang2, Wei
> Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
> The patch would need some work to make it suitable for check in and get it
> working for stubdom. At the very least the ioperm() calls would need
> removing completely, or stubbing out for the stubdom build.
>
> -- Keir
>
> On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
>
> > Do i need any previous patches for this to work ?
> >
> > After applying it to xen-unstable, compiling xen results in:
> >
> > make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
> > [ -e include/mini-os ] || ln -sf . include/mini-os
> > [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
> > make --directory=arch/x86
> > OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
> > exit 1;
> > make[3]: Entering directory
> > `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > make[3]: Nothing to be done for `all'.
> > make[3]: Leaving directory
> > `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > ld -r -nostdlib
> > -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > -m elf_x86_64
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
> > .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
> > -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
> > -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > objcopy -w -G xenos_* -G _start
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > ld -nostdlib
> > -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > -m elf_x86_64 -T arch/x86/minios-x86_64.lds
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > function `ati_hw_out':
> > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
> > reference to `ioperm'
> > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
> > reference to `ioperm'
> > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > function `ati_hw_in':
> > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
> > reference to `ioperm'
> > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
> > reference to `ioperm'
> > make[2]: ***
> > [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
> > make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > make[1]: *** [ioemu-stubdom] Error 2
> > make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
> > make: *** [install-stubdom] Error 2
> >
> > Don't know why the include of sys/io.h doesn't seem to work
> > --
> >
> > Sander
> >
> > Saturday, December 11, 2010, 12:40:19 AM, you wrote:
> >
> >> Hi,
> >
> >> The attached patch supports dynamic detection of BARs (both MMIO and
> >> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
> >> passthru. Please let me know whether it works better for you.
> >
> >> Thanks,
> >> -Wei
> >
> >> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
> >>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> >>>> Sorry, hold on a second. This fix seems corrupt my pci config space
> >>>> after
> >>>> several runs.
> >>>>
> >>> Hello,
> >>>
> >>> Any updates to these patches? Many users have been asking about amd/ati vga
> >>> passthru stuff..
> >>>
> >>> -- Pasi
> >>>
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: xen-devel-bounces@lists.xensource.com
> >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> >>>> Sent: Wednesday, October 13, 2010 3:47 PM
> >>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> >>>> Cc: Wang2, Wei; Xen-devel
> >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Hi Allen and Doug,
> >>>>
> >>>>
> >>>>
> >>>> Could you fix the following line in save_pci_conf_space() of
> >>>> tools/python/xen/util/pci.py?
> >>>>
> >>>>
> >>>>
> >>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
> >>>>
> >>>>
> >>>>
> >>>> This solves my black screen issue. Please let me know the results.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> >>>> Sent: Friday, October 08, 2010 10:53 AM
> >>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel; Wang2, Wei
> >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Wei,
> >>>>
> >>>> These were guests that had never seen the catalyst
> >>>> driver
> >>>> before. I booted each three with the graphics device and usb devices
> >>>> assigned, they worked fine using the basic VGA driver, then installed
> >>>> fresh Catalyst 10.9, rebooted, and each one crashed.
> >>>>
> >>>>
> >>>>
> >>>> Let me know if there's any other info I can provide
> >>>> that
> >>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
> >>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
> >>>> pvops
> >>>> Dom0 from stable-2.6.32.x commit 179eca50.
> >>>>
> >>>>
> >>>>
> >>>> Doug Magee
> >>>>
> >>>>
> >>>>
> >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> >>>> Sent: Friday, October 08, 2010 11:41 AM
> >>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel; Wang2, Wei
> >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Hi Doug,
> >>>>
> >>>>
> >>>>
> >>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> >>>> Catalyst installation or an existing guest image? We felt this VBIOS
> >>>> patch
> >>>> might not provide all necessary resources to driver, which got upset.
> >>>> Currently we are debugging it with our driver team and will let you
> >>>> know
> >>>> the update.
> >>>>
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> >>>> Sent: Friday, October 08, 2010 9:41 AM
> >>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Wei,
> >>>>
> >>>> I've tested with a Radeon 4770 and it the VBIOS works
> >>>> without a problem, through many guest (re)boots, so it seems pretty
> >>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> >>>> and Windows 7 (without accelerated drivers). The open radeon linux
> >>>> driver
> >>>> works fine.
> >>>>
> >>>>
> >>>>
> >>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
> >>>> in
> >>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> >>>> reset?), and linux (total system freeze). This seems to be different
> >>>> than
> >>>> the `Blank Screen' problem you report, as the driver is clearly not
> >>>> functioning properly.
> >>>>
> >>>>
> >>>>
> >>>> Doug Magee
> >>>>
> >>>>
> >>>>
> >>>> From: xen-devel-bounces@lists.xensource.com
> >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> >>>> Sent: Friday, October 08, 2010 9:57 AM
> >>>> To: Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> >>>> support
> >>>>
> >>>>
> >>>>
> >>>> Hi Allen,
> >>>>
> >>>>
> >>>>
> >>>> Yes, Catalyst driver is the one from public website. The driver still
> >>>> has
> >>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> >>>> patch is to get community feedbacks. After we figure out the root cause
> >>>> of
> >>>> black screen, I will formally submit a patch for inclusion.
> >>>>
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> >>>> Sent: Friday, October 08, 2010 2:21 AM
> >>>> To: Huang2, Wei; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>
> >>>>
> >>>>
> >>>> Hi Wei,
> >>>>
> >>>>
> >>>>
> >>>> Is Catalyst driver the one on AMD website? I think that's what I have
> >>>> in
> >>>> my win7 guest and it matches the symptom you are describing. "lspci"
> >>>> reports my ATI card is a V5700 - although it says v3750 on the box.
> >>>> Where
> >>>> can I get a working driver?
> >>>>
> >>>>
> >>>>
> >>>> The patch looks reasonable to me in general.
> >>>>
> >>>>
> >>>>
> >>>> Allen
> >>>>
> >>>>
> >>>>
> >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> >>>> Sent: Thursday, October 07, 2010 9:06 PM
> >>>> To: Kay, Allen M; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>
> >>>>
> >>>>
> >>>> Hi Allen,
> >>>>
> >>>>
> >>>>
> >>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
> >>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
> >>>> V3750
> >>>> at hand. It is very possible this patch isn't compatible with V3750. We
> >>>> will try to get hold of one for debugging. For graphics which work with
> >>>> this path, users should be able to get rid of emulated gfx (such as
> >>>> Cirrus). I have successfully installed a Windows guest VM using this
> >>>> patch.
> >>>>
> >>>>
> >>>>
> >>>> I also want to point out that there is still an issue. Users will see a
> >>>> black screen after installing Catalyst driver. Even though the screen
> >>>> appears to be black, the driver is actually functioning correctly
> >>>> (3DMark
> >>>> can be run with external monitor). Our driver team is currently
> >>>> debugging
> >>>> it and they believe this is easy to fix.
> >>>>
> >>>>
> >>>>
> >>>> What is your opinion on this patch (and the solution) in general?
> >>>>
> >>>>
> >>>>
> >>>> -Wei
> >>>>
> >>>>
> >>>>
> >>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> >>>> Sent: Thursday, October 07, 2010 6:58 PM
> >>>> To: Huang2, Wei; Ian Jackson
> >>>> Cc: Xen-devel
> >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>
> >>>>
> >>>>
> >>>> Hi Wei,
> >>>>
> >>>>
> >>>>
> >>>> This patch did not cause any problems with Intel IGD passthrough for
> >>>> me.
> >>>> However, the monitor remained blank if I pass through ATI Firepro V3750
> >>>> either as the primary display device or the secondary device
> >>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
> >>>> work.
> >>>>
> >>>>
> >>>>
> >>>> Have you tested the patch with this graphics card?
> >>>>
> >>>>
> >>>>
> >>>> Allen
> >>>>
> >>>>
> >>>>
> >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> >>>> Sent: Thursday, October 07, 2010 9:57 AM
> >>>> To: Ian Jackson
> >>>> Cc: Xen-devel; Kay, Allen M
> >>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
> >>>>
> >>>>
> >>>>
> >>>> Hi Ian,
> >>>>
> >>>>
> >>>>
> >>>> There have been a lot of interest on gfx passthru recently. This patch
> >>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> >>>> Windows boot logo) can now show in passthru screen. We have tested with
> >>>> various Windows and Linux guest VMs. Please help review it. We are also
> >>>> looking forward to comments and suggestions from Xen community users.
> >>>>
> >>>>
> >>>>
> >>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
> >>>>
> >>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2011-01-06 19:56 ` Huang2, Wei
@ 2011-01-06 20:05 ` Pasi Kärkkäinen
2011-01-07 16:08 ` Huang2, Wei
0 siblings, 1 reply; 32+ messages in thread
From: Pasi Kärkkäinen @ 2011-01-06 20:05 UTC (permalink / raw)
To: Huang2, Wei
Cc: Xen-devel, Keir Fraser, Ian Jackson, Kay, Allen M, Wang2, Wei,
Sander Eikelenboom, djmagee@mageenet.net
On Thu, Jan 06, 2011 at 01:56:47PM -0600, Huang2, Wei wrote:
> Hi Pasi,
>
> No it isn't ready yet. I found some problem with new 6000M GPU. The algorithm doesn't work for this VBIOS. It needs more work before a formal submission.
>
Ok.
Too bad, Xen 4.1 is getting ready for -rc1 now..
would have been good to have the AMD/ATI passthrough stuff in 4.1.
(at least for some adapters).
-- Pasi
> -Wei
> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> Sent: Thursday, January 06, 2011 11:24 AM
> To: Huang2, Wei
> Cc: Keir Fraser; Sander Eikelenboom; Wang2, Wei; Kay, Allen M; djmagee@mageenet.net; Xen-devel; Ian Jackson
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
> On Sun, Dec 12, 2010 at 12:19:08AM -0600, Huang2, Wei wrote:
> > This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
> >
>
> Any plans for the "final version" ?
>
> -- Pasi
>
> > Thanks,
> > -Wei
> > ________________________________________
> > From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> > Sent: Saturday, December 11, 2010 9:38 AM
> > To: Sander Eikelenboom; Huang2, Wei
> > Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> > Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >
> > The patch would need some work to make it suitable for check in and get it
> > working for stubdom. At the very least the ioperm() calls would need
> > removing completely, or stubbing out for the stubdom build.
> >
> > -- Keir
> >
> > On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
> >
> > > Do i need any previous patches for this to work ?
> > >
> > > After applying it to xen-unstable, compiling xen results in:
> > >
> > > make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > > [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
> > > [ -e include/mini-os ] || ln -sf . include/mini-os
> > > [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
> > > make --directory=arch/x86
> > > OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
> > > exit 1;
> > > make[3]: Entering directory
> > > `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > > make[3]: Nothing to be done for `all'.
> > > make[3]: Leaving directory
> > > `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > > ld -r -nostdlib
> > > -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > > -m elf_x86_64
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
> > > .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
> > > -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
> > > -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > > objcopy -w -G xenos_* -G _start
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > > ld -nostdlib
> > > -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > > -m elf_x86_64 -T arch/x86/minios-x86_64.lds
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > > function `ati_hw_out':
> > > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
> > > reference to `ioperm'
> > > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
> > > reference to `ioperm'
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > > function `ati_hw_in':
> > > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
> > > reference to `ioperm'
> > > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
> > > reference to `ioperm'
> > > make[2]: ***
> > > [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
> > > make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > > make[1]: *** [ioemu-stubdom] Error 2
> > > make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
> > > make: *** [install-stubdom] Error 2
> > >
> > > Don't know why the include of sys/io.h doesn't seem to work
> > > --
> > >
> > > Sander
> > >
> > > Saturday, December 11, 2010, 12:40:19 AM, you wrote:
> > >
> > >> Hi,
> > >
> > >> The attached patch supports dynamic detection of BARs (both MMIO and
> > >> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
> > >> passthru. Please let me know whether it works better for you.
> > >
> > >> Thanks,
> > >> -Wei
> > >
> > >> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
> > >>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> > >>>> Sorry, hold on a second. This fix seems corrupt my pci config space
> > >>>> after
> > >>>> several runs.
> > >>>>
> > >>> Hello,
> > >>>
> > >>> Any updates to these patches? Many users have been asking about amd/ati vga
> > >>> passthru stuff..
> > >>>
> > >>> -- Pasi
> > >>>
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: xen-devel-bounces@lists.xensource.com
> > >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > >>>> Sent: Wednesday, October 13, 2010 3:47 PM
> > >>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > >>>> Cc: Wang2, Wei; Xen-devel
> > >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Allen and Doug,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Could you fix the following line in save_pci_conf_space() of
> > >>>> tools/python/xen/util/pci.py?
> > >>>>
> > >>>>
> > >>>>
> > >>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
> > >>>>
> > >>>>
> > >>>>
> > >>>> This solves my black screen issue. Please let me know the results.
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > >>>> Sent: Friday, October 08, 2010 10:53 AM
> > >>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel; Wang2, Wei
> > >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Wei,
> > >>>>
> > >>>> These were guests that had never seen the catalyst
> > >>>> driver
> > >>>> before. I booted each three with the graphics device and usb devices
> > >>>> assigned, they worked fine using the basic VGA driver, then installed
> > >>>> fresh Catalyst 10.9, rebooted, and each one crashed.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Let me know if there's any other info I can provide
> > >>>> that
> > >>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
> > >>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
> > >>>> pvops
> > >>>> Dom0 from stable-2.6.32.x commit 179eca50.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Doug Magee
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > >>>> Sent: Friday, October 08, 2010 11:41 AM
> > >>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel; Wang2, Wei
> > >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Doug,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> > >>>> Catalyst installation or an existing guest image? We felt this VBIOS
> > >>>> patch
> > >>>> might not provide all necessary resources to driver, which got upset.
> > >>>> Currently we are debugging it with our driver team and will let you
> > >>>> know
> > >>>> the update.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > >>>> Sent: Friday, October 08, 2010 9:41 AM
> > >>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Wei,
> > >>>>
> > >>>> I've tested with a Radeon 4770 and it the VBIOS works
> > >>>> without a problem, through many guest (re)boots, so it seems pretty
> > >>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> > >>>> and Windows 7 (without accelerated drivers). The open radeon linux
> > >>>> driver
> > >>>> works fine.
> > >>>>
> > >>>>
> > >>>>
> > >>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
> > >>>> in
> > >>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> > >>>> reset?), and linux (total system freeze). This seems to be different
> > >>>> than
> > >>>> the `Blank Screen' problem you report, as the driver is clearly not
> > >>>> functioning properly.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Doug Magee
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: xen-devel-bounces@lists.xensource.com
> > >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > >>>> Sent: Friday, October 08, 2010 9:57 AM
> > >>>> To: Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Allen,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Yes, Catalyst driver is the one from public website. The driver still
> > >>>> has
> > >>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> > >>>> patch is to get community feedbacks. After we figure out the root cause
> > >>>> of
> > >>>> black screen, I will formally submit a patch for inclusion.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > >>>> Sent: Friday, October 08, 2010 2:21 AM
> > >>>> To: Huang2, Wei; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Wei,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Is Catalyst driver the one on AMD website? I think that's what I have
> > >>>> in
> > >>>> my win7 guest and it matches the symptom you are describing. "lspci"
> > >>>> reports my ATI card is a V5700 - although it says v3750 on the box.
> > >>>> Where
> > >>>> can I get a working driver?
> > >>>>
> > >>>>
> > >>>>
> > >>>> The patch looks reasonable to me in general.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Allen
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > >>>> Sent: Thursday, October 07, 2010 9:06 PM
> > >>>> To: Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Allen,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
> > >>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
> > >>>> V3750
> > >>>> at hand. It is very possible this patch isn't compatible with V3750. We
> > >>>> will try to get hold of one for debugging. For graphics which work with
> > >>>> this path, users should be able to get rid of emulated gfx (such as
> > >>>> Cirrus). I have successfully installed a Windows guest VM using this
> > >>>> patch.
> > >>>>
> > >>>>
> > >>>>
> > >>>> I also want to point out that there is still an issue. Users will see a
> > >>>> black screen after installing Catalyst driver. Even though the screen
> > >>>> appears to be black, the driver is actually functioning correctly
> > >>>> (3DMark
> > >>>> can be run with external monitor). Our driver team is currently
> > >>>> debugging
> > >>>> it and they believe this is easy to fix.
> > >>>>
> > >>>>
> > >>>>
> > >>>> What is your opinion on this patch (and the solution) in general?
> > >>>>
> > >>>>
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > >>>> Sent: Thursday, October 07, 2010 6:58 PM
> > >>>> To: Huang2, Wei; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Wei,
> > >>>>
> > >>>>
> > >>>>
> > >>>> This patch did not cause any problems with Intel IGD passthrough for
> > >>>> me.
> > >>>> However, the monitor remained blank if I pass through ATI Firepro V3750
> > >>>> either as the primary display device or the secondary device
> > >>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
> > >>>> work.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Have you tested the patch with this graphics card?
> > >>>>
> > >>>>
> > >>>>
> > >>>> Allen
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > >>>> Sent: Thursday, October 07, 2010 9:57 AM
> > >>>> To: Ian Jackson
> > >>>> Cc: Xen-devel; Kay, Allen M
> > >>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Ian,
> > >>>>
> > >>>>
> > >>>>
> > >>>> There have been a lot of interest on gfx passthru recently. This patch
> > >>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> > >>>> Windows boot logo) can now show in passthru screen. We have tested with
> > >>>> various Windows and Linux guest VMs. Please help review it. We are also
> > >>>> looking forward to comments and suggestions from Xen community users.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
> > >>>>
> > >>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> 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
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
2011-01-06 20:05 ` Pasi Kärkkäinen
@ 2011-01-07 16:08 ` Huang2, Wei
0 siblings, 0 replies; 32+ messages in thread
From: Huang2, Wei @ 2011-01-07 16:08 UTC (permalink / raw)
To: Pasi Kärkkäinen
Cc: Xen-devel, Keir Fraser, Ian Jackson, Kay, Allen M, Wang2, Wei,
Sander Eikelenboom, djmagee@mageenet.net
I understand that. It is an exciting hobby for many users (including me). But be honest, current Xen gfx passthru isn't mature enough for any production usage, especially users can't switch between guest VMs on the same gfx/LCD. XenClient's approach is better.
Thanks,
-Wei
-----Original Message-----
From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
Sent: Thursday, January 06, 2011 2:06 PM
To: Huang2, Wei
Cc: Keir Fraser; Sander Eikelenboom; Wang2, Wei; Kay, Allen M; djmagee@mageenet.net; Xen-devel; Ian Jackson
Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
On Thu, Jan 06, 2011 at 01:56:47PM -0600, Huang2, Wei wrote:
> Hi Pasi,
>
> No it isn't ready yet. I found some problem with new 6000M GPU. The algorithm doesn't work for this VBIOS. It needs more work before a formal submission.
>
Ok.
Too bad, Xen 4.1 is getting ready for -rc1 now..
would have been good to have the AMD/ATI passthrough stuff in 4.1.
(at least for some adapters).
-- Pasi
> -Wei
> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> Sent: Thursday, January 06, 2011 11:24 AM
> To: Huang2, Wei
> Cc: Keir Fraser; Sander Eikelenboom; Wang2, Wei; Kay, Allen M; djmagee@mageenet.net; Xen-devel; Ian Jackson
> Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
>
> On Sun, Dec 12, 2010 at 12:19:08AM -0600, Huang2, Wei wrote:
> > This patch isn't meant to be final version. The stubdom issue was known to me. Users can just compile qemu-dm and copy it to overwrite existing Xen installation for a quick testing.
> >
>
> Any plans for the "final version" ?
>
> -- Pasi
>
> > Thanks,
> > -Wei
> > ________________________________________
> > From: Keir Fraser [keir.xen@gmail.com] On Behalf Of Keir Fraser [keir@xen.org]
> > Sent: Saturday, December 11, 2010 9:38 AM
> > To: Sander Eikelenboom; Huang2, Wei
> > Cc: Xen-devel; Ian Jackson; Kay, Allen M; Wang2, Wei; djmagee@mageenet.net
> > Subject: Re: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> >
> > The patch would need some work to make it suitable for check in and get it
> > working for stubdom. At the very least the ioperm() calls would need
> > removing completely, or stubbing out for the stubdom build.
> >
> > -- Keir
> >
> > On 11/12/2010 14:06, "Sander Eikelenboom" <linux@eikelenboom.it> wrote:
> >
> > > Do i need any previous patches for this to work ?
> > >
> > > After applying it to xen-unstable, compiling xen results in:
> > >
> > > make[2]: Entering directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > > [ -e include/xen ] || ln -sf ../../../xen/include/public include/xen
> > > [ -e include/mini-os ] || ln -sf . include/mini-os
> > > [ -e include/x86/mini-os ] || ln -sf . include/x86/mini-os
> > > make --directory=arch/x86
> > > OBJ_DIR=/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 ||
> > > exit 1;
> > > make[3]: Entering directory
> > > `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > > make[3]: Nothing to be done for `all'.
> > > make[3]: Leaving directory
> > > `/usr/src/new/xen-unstable.hg/extras/mini-os/arch/x86'
> > > ld -r -nostdlib
> > > -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > > -m elf_x86_64
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86/x86_64.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os_app.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/blkfront.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/events.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fbfront.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/fs-front.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gntmap.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/gnttab.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/hypervisor.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/kernel.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lock.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/main.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mm.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/netfront.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/pcifront.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/sched.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/ctype.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/math.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/printf.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/stack_chk_fail.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/string.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/sys.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xmalloc.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lib/xs.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/xenbus/xenbus.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/console.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/console/xencons_ring
> > > .o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/lwip.a
> > > -L/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/arch/x86 -lx86_64
> > > -lc -o /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > > objcopy -w -G xenos_* -G _start
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o
> > > ld -nostdlib
> > > -L/usr/src/new/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
> > > -m elf_x86_64 -T arch/x86/minios-x86_64.lds
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o -o
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > > function `ati_hw_out':
> > > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:82: undefined
> > > reference to `ioperm'
> > > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:84: undefined
> > > reference to `ioperm'
> > > /usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os.o: In
> > > function `ati_hw_in':
> > > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:72: undefined
> > > reference to `ioperm'
> > > /usr/src/new/xen-unstable.hg/stubdom/ioemu/hw/pt-graphics.c:74: undefined
> > > reference to `ioperm'
> > > make[2]: ***
> > > [/usr/src/new/xen-unstable.hg/stubdom/mini-os-x86_64-ioemu/mini-os] Error 1
> > > make[2]: Leaving directory `/usr/src/new/xen-unstable.hg/extras/mini-os'
> > > make[1]: *** [ioemu-stubdom] Error 2
> > > make[1]: Leaving directory `/usr/src/new/xen-unstable.hg/stubdom'
> > > make: *** [install-stubdom] Error 2
> > >
> > > Don't know why the include of sys/io.h doesn't seem to work
> > > --
> > >
> > > Sander
> > >
> > > Saturday, December 11, 2010, 12:40:19 AM, you wrote:
> > >
> > >> Hi,
> > >
> > >> The attached patch supports dynamic detection of BARs (both MMIO and
> > >> PIO). Hopefully it can alleviate some of the issues you saw with ATI gfx
> > >> passthru. Please let me know whether it works better for you.
> > >
> > >> Thanks,
> > >> -Wei
> > >
> > >> On 12/07/2010 04:00 AM, Pasi Kärkkäinen wrote:
> > >>> On Wed, Oct 13, 2010 at 04:37:10PM -0500, Huang2, Wei wrote:
> > >>>> Sorry, hold on a second. This fix seems corrupt my pci config space
> > >>>> after
> > >>>> several runs.
> > >>>>
> > >>> Hello,
> > >>>
> > >>> Any updates to these patches? Many users have been asking about amd/ati vga
> > >>> passthru stuff..
> > >>>
> > >>> -- Pasi
> > >>>
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: xen-devel-bounces@lists.xensource.com
> > >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > >>>> Sent: Wednesday, October 13, 2010 3:47 PM
> > >>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > >>>> Cc: Wang2, Wei; Xen-devel
> > >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Allen and Doug,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Could you fix the following line in save_pci_conf_space() of
> > >>>> tools/python/xen/util/pci.py?
> > >>>>
> > >>>>
> > >>>>
> > >>>> "for i in range(0, 256, 4):" to "for i in range(0, 512, 4):"
> > >>>>
> > >>>>
> > >>>>
> > >>>> This solves my black screen issue. Please let me know the results.
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > >>>> Sent: Friday, October 08, 2010 10:53 AM
> > >>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel; Wang2, Wei
> > >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Wei,
> > >>>>
> > >>>> These were guests that had never seen the catalyst
> > >>>> driver
> > >>>> before. I booted each three with the graphics device and usb devices
> > >>>> assigned, they worked fine using the basic VGA driver, then installed
> > >>>> fresh Catalyst 10.9, rebooted, and each one crashed.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Let me know if there's any other info I can provide
> > >>>> that
> > >>>> will help you debug. The motherboard is a DQ45CB, running xen-unstable
> > >>>> c/s 22155 using `dom0_mem=768M iommu=1' on the grub line, and using
> > >>>> pvops
> > >>>> Dom0 from stable-2.6.32.x commit 179eca50.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Doug Magee
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > >>>> Sent: Friday, October 08, 2010 11:41 AM
> > >>>> To: djmagee@mageenet.net; Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel; Wang2, Wei
> > >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Doug,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Regarding Catalyst driver, we never saw guest crashing. Was it a fresh
> > >>>> Catalyst installation or an existing guest image? We felt this VBIOS
> > >>>> patch
> > >>>> might not provide all necessary resources to driver, which got upset.
> > >>>> Currently we are debugging it with our driver team and will let you
> > >>>> know
> > >>>> the update.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: djmagee@mageenet.net [mailto:djmagee@mageenet.net]
> > >>>> Sent: Friday, October 08, 2010 9:41 AM
> > >>>> To: Huang2, Wei; Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: RE: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Wei,
> > >>>>
> > >>>> I've tested with a Radeon 4770 and it the VBIOS works
> > >>>> without a problem, through many guest (re)boots, so it seems pretty
> > >>>> solid. I tested a linux guest (fairly standard Fedora 12), Windows XP,
> > >>>> and Windows 7 (without accelerated drivers). The open radeon linux
> > >>>> driver
> > >>>> works fine.
> > >>>>
> > >>>>
> > >>>>
> > >>>> The Catalyst driver fails in Windows XP (STOP 0x000000EA, thread stuck
> > >>>> in
> > >>>> device driver), windows 7 (STOP 0x00000116, driver fails to properly
> > >>>> reset?), and linux (total system freeze). This seems to be different
> > >>>> than
> > >>>> the `Blank Screen' problem you report, as the driver is clearly not
> > >>>> functioning properly.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Doug Magee
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: xen-devel-bounces@lists.xensource.com
> > >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Huang2, Wei
> > >>>> Sent: Friday, October 08, 2010 9:57 AM
> > >>>> To: Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: [Xen-devel] RE: [RFC][QEMU] ATI graphics VBIOS passthru
> > >>>> support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Allen,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Yes, Catalyst driver is the one from public website. The driver still
> > >>>> has
> > >>>> a minor issue with this VBIOS patch. The purpose of submitting VBIOS
> > >>>> patch is to get community feedbacks. After we figure out the root cause
> > >>>> of
> > >>>> black screen, I will formally submit a patch for inclusion.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > >>>> Sent: Friday, October 08, 2010 2:21 AM
> > >>>> To: Huang2, Wei; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Wei,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Is Catalyst driver the one on AMD website? I think that's what I have
> > >>>> in
> > >>>> my win7 guest and it matches the symptom you are describing. "lspci"
> > >>>> reports my ATI card is a V5700 - although it says v3750 on the box.
> > >>>> Where
> > >>>> can I get a working driver?
> > >>>>
> > >>>>
> > >>>>
> > >>>> The patch looks reasonable to me in general.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Allen
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > >>>> Sent: Thursday, October 07, 2010 9:06 PM
> > >>>> To: Kay, Allen M; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Allen,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Thanks for testing it out. We have tested this patch with Radeon 4850,
> > >>>> 4870, FirePro V5700 and FirePro M5800. Unfortunately we don't have
> > >>>> V3750
> > >>>> at hand. It is very possible this patch isn't compatible with V3750. We
> > >>>> will try to get hold of one for debugging. For graphics which work with
> > >>>> this path, users should be able to get rid of emulated gfx (such as
> > >>>> Cirrus). I have successfully installed a Windows guest VM using this
> > >>>> patch.
> > >>>>
> > >>>>
> > >>>>
> > >>>> I also want to point out that there is still an issue. Users will see a
> > >>>> black screen after installing Catalyst driver. Even though the screen
> > >>>> appears to be black, the driver is actually functioning correctly
> > >>>> (3DMark
> > >>>> can be run with external monitor). Our driver team is currently
> > >>>> debugging
> > >>>> it and they believe this is easy to fix.
> > >>>>
> > >>>>
> > >>>>
> > >>>> What is your opinion on this patch (and the solution) in general?
> > >>>>
> > >>>>
> > >>>>
> > >>>> -Wei
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Kay, Allen M [mailto:allen.m.kay@intel.com]
> > >>>> Sent: Thursday, October 07, 2010 6:58 PM
> > >>>> To: Huang2, Wei; Ian Jackson
> > >>>> Cc: Xen-devel
> > >>>> Subject: RE: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Wei,
> > >>>>
> > >>>>
> > >>>>
> > >>>> This patch did not cause any problems with Intel IGD passthrough for
> > >>>> me.
> > >>>> However, the monitor remained blank if I pass through ATI Firepro V3750
> > >>>> either as the primary display device or the secondary device
> > >>>> (gfx_passthru=1/0). Passing it through as the secondary device used to
> > >>>> work.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Have you tested the patch with this graphics card?
> > >>>>
> > >>>>
> > >>>>
> > >>>> Allen
> > >>>>
> > >>>>
> > >>>>
> > >>>> From: Huang2, Wei [mailto:Wei.Huang2@amd.com]
> > >>>> Sent: Thursday, October 07, 2010 9:57 AM
> > >>>> To: Ian Jackson
> > >>>> Cc: Xen-devel; Kay, Allen M
> > >>>> Subject: [RFC][QEMU] ATI graphics VBIOS passthru support
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Ian,
> > >>>>
> > >>>>
> > >>>>
> > >>>> There have been a lot of interest on gfx passthru recently. This patch
> > >>>> enables ATI VBIOS in passthru mode. The guest VM system BIOS (including
> > >>>> Windows boot logo) can now show in passthru screen. We have tested with
> > >>>> various Windows and Linux guest VMs. Please help review it. We are also
> > >>>> looking forward to comments and suggestions from Xen community users.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
> > >>>>
> > >>>> Signed-off-by: Wei Wang<wei.wang2@amd.com>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> 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
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
end of thread, other threads:[~2011-01-07 16:08 UTC | newest]
Thread overview: 32+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-07 16:56 [RFC][QEMU] ATI graphics VBIOS passthru support Huang2, Wei
2010-10-07 23:57 ` Kay, Allen M
2010-10-08 4:05 ` Huang2, Wei
2010-10-08 7:20 ` Kay, Allen M
2010-10-08 11:09 ` Stefano Stabellini
2010-10-08 15:32 ` Huang2, Wei
2010-10-08 13:57 ` Huang2, Wei
2010-10-08 14:41 ` djmagee
2010-10-08 14:50 ` Pasi Kärkkäinen
2010-10-08 15:41 ` Huang2, Wei
2010-10-08 15:52 ` djmagee
2010-10-13 20:47 ` Huang2, Wei
2010-10-13 21:37 ` Huang2, Wei
2010-12-07 10:00 ` Pasi Kärkkäinen
2010-12-07 10:14 ` Jean Guyader
2010-12-08 5:31 ` Huang2, Wei
2010-12-08 8:44 ` Pasi Kärkkäinen
2010-12-10 23:40 ` Wei Huang
2010-12-11 14:06 ` Sander Eikelenboom
2010-12-11 15:38 ` Keir Fraser
2010-12-12 6:19 ` Huang2, Wei
2010-12-12 19:10 ` Sander Eikelenboom
2010-12-13 20:17 ` Sander Eikelenboom
2010-12-13 20:33 ` Huang2, Wei
2010-12-13 20:47 ` Sander Eikelenboom
2010-12-16 18:29 ` Pasi Kärkkäinen
2010-12-17 7:03 ` Wei Huang
2010-12-17 7:13 ` Pasi Kärkkäinen
2011-01-06 17:23 ` Pasi Kärkkäinen
2011-01-06 19:56 ` Huang2, Wei
2011-01-06 20:05 ` Pasi Kärkkäinen
2011-01-07 16:08 ` Huang2, Wei
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.