WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup

from [Konrad Rzeszutek Wilk] [Permanent Link][Original]
To: Łukasz Oleś <lukaszoles@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 22 Mar 2010 15:50:10 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 22 Mar 2010 13:23:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <cb0d70421003211530l1a2b3a3fp1206ff3f3aa40fc0@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <cb0d70421003161641x3f413623x11c82083e1c30ce9@xxxxxxxxxxxxxx> <cb0d70421003171120q1dcbbd28pa0fd3af4139d5b8f@xxxxxxxxxxxxxx> <20100317201446.GA7785@xxxxxxxxxxxxxxxxxxx> <cb0d70421003171448s4e45c007ta343a261d274473d@xxxxxxxxxxxxxx> <20100318141909.GA14445@xxxxxxxxxxxxxxxxxxx> <cb0d70421003211530l1a2b3a3fp1206ff3f3aa40fc0@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05) 
On Sun, Mar 21, 2010 at 11:30:57PM +0100, Łukasz Oleś wrote:
> Hi,
> 
> During earlier testst I used on dom0 xen/stable and on domU 2.6.32.9
> from debian testing.
> 
> Then I switched to xen/next on dom0 and domU. And now I have new problem :)

What is the version of Xen tools you have? Did you build them from
xen-unstable?

> 
> Here is the full log from the boot: http://pastebin.com/e8hUeQUs
> I'm still getting:
> (XEN) mm.c:859:d0 Error getting mfn 40100 (pfn 5555555555555555) from
> L1 entry 8000000040100473 for l1e_owner=0, pg_owner=32753
> 
> Now there are two ways:
> 
> FIRST:
> as you sugested I tried pass-through another device (usb controller)
> 
> I added it to pci-stub:
> root@debian:~# echo "8086 3a67" > /sys/bus/pci/drivers/pci-stub/new_id
> root@debian:~# echo
> "0000:00:1a.0">/sys/bus/pci/devices/0000:00:1a.0/driver/unbind
> root@debian:~# echo "0000:00:1a.0">/sys/bus/pci/drivers/pci-stub/bind
> root@debian:~# echo "8086 3a68" > /sys/bus/pci/drivers/pci-stub/new_id
> root@debian:~# echo
> "0000:00:1a.1">/sys/bus/pci/devices/0000:00:1a.1/driver/unbind
> root@debian:~# echo "0000:00:1a.1">/sys/bus/pci/drivers/pci-stub/bind

Where did you get the documentation for those steps? I would suggest you use
the 'pciback' instead of 'pci-stub' module for this just to see if that
makes the 'pciback' later error go away.
> 
> on console i got:
> 
> [  253.516238] uhci_hcd 0000:00:1a.0: remove, state 4
> [  253.518622] usb usb3: USB disconnect, address 1
> [  253.521197] uhci_hcd 0000:00:1a.0: USB bus 3 deregistered
> [  253.523799] uhci_hcd 0000:00:1a.0: PCI INT A disabled
> [  269.544219] pci-stub 0000:00:1a.0: claimed by stub
> [  319.424304] uhci_hcd 0000:00:1a.1: remove, state 4
> [  319.427776] usb usb4: USB disconnect, address 1
> [  319.430305] uhci_hcd 0000:00:1a.1: USB bus 4 deregistered
> [  319.433006] uhci_hcd 0000:00:1a.1: PCI INT B disabled
> [  339.692207] pci-stub 0000:00:1a.1: claimed by stub
> 
> 
> Then I launched guest and it worked, guest could see usb controller. I
> disabled guest, enabled it again, disabled it again and enabled it
> again and got call trace:
> 
> 
> (XEN) HVM1: HVM Loader
> (XEN) HVM1: Detected Xen v4.0.0-rc6
> (XEN) HVM1: CPU speed is 2800 MHz
> (XEN) irq.c:243: Dom1 PCI link 0 changed 0 -> 5
> (XEN) HVM1: PCI-ISA link 0 routed to IRQ5
> (XEN) irq.c:243: Dom1 PCI link 1 changed 0 -> 10
> (XEN) HVM1: PCI-ISA link 1 routed to IRQ10
> (XEN) irq.c:243: Dom1 PCI link 2 changed 0 -> 11
> (XEN) HVM1: PCI-ISA link 2 routed to IRQ11
> (XEN) irq.c:243: Dom1 PCI link 3 changed 0 -> 5
> (XEN) HVM1: PCI-ISA link 3 routed to IRQ5
> (XEN) HVM1: pci dev 01:3 INTA->IRQ10
> (XEN) HVM1: pci dev 03:0 INTA->IRQ5
> (XEN) HVM1: pci dev 04:0 INTA->IRQ5
> (XEN) HVM1: pci dev 02:0 bar 10 size 02000000: f0000008
> (XEN) HVM1: pci dev 03:0 bar 14 size 01000000: f2000008
> (XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f3000000
> (XEN) HVM1: pci dev 03:0 bar 10 size 00000100: 0000c001
> (XEN) domctl.c:1047:d0 ioport_map:add f_gport=c100 f_mport=e0c0 np=20
> (XEN) HVM1: pci dev 04:0 bar 20 size 00000020: 0000c101
> (XEN) HVM1: pci dev 01:1 bar 20 size 00000010: 0000c121
> (XEN) HVM1: Multiprocessor initialisation:
> (XEN) HVM1:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs
> [2/8] ... done.
> (XEN) HVM1: Writing SMBIOS tables ...
> (XEN) HVM1: Loading ROMBIOS ...
> (XEN) HVM1: 10556 bytes of ROMBIOS high-memory extensions:
> (XEN) HVM1:   Relocating to 0xfc000000-0xfc00293c ... done
> (XEN) HVM1: Creating MP tables ...
> (XEN) HVM1: Loading Cirrus VGABIOS ...
> (XEN) HVM1: Loading ACPI ...
> (XEN) HVM1:  - Lo data: 000ea020-000ea04f
> (XEN) HVM1:  - Hi data: fc002c00-fc012d1f
> (XEN) HVM1: vm86 TSS at fc013000
> (XEN) HVM1: BIOS map:
> (XEN) HVM1:  c0000-c8fff: VGA BIOS
> (XEN) HVM1:  eb000-eb148: SMBIOS tables
> (XEN) HVM1:  f0000-fffff: Main BIOS
> (XEN) HVM1: Invoking ROMBIOS ...
> (XEN) HVM1: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
> (XEN) stdvga.c:147:d1 entering stdvga and caching modes
> (XEN) HVM1: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert
> Exp $
> (XEN) HVM1: Bochs BIOS - build: 06/23/99
> (XEN) HVM1: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
> (XEN) HVM1: Options: apmbios pcibios eltorito PMM
> (XEN) HVM1:
> (XEN) HVM1: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
> (XEN) HVM1: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (20480 MBytes)
> (XEN) HVM1: IDE time out
> (XEN) HVM1: ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
> (XEN) HVM1: IDE time out
> (XEN) HVM1:
> (XEN) HVM1:
> (XEN) HVM1:
> (XEN) HVM1: Press F12 for boot menu.
> (XEN) HVM1:
> (XEN) HVM1: Booting from Hard Disk...
> (XEN) HVM1: Booting from 0000:7c00
> (XEN) stdvga.c:151:d1 leaving stdvga
> (XEN) stdvga.c:147:d1 entering stdvga and caching modes
> (XEN) vlapic.c:702:d1 Local APIC Write to read-only register 0x30
> (XEN) vlapic.c:702:d1 Local APIC Write to read-only register 0x20
> (XEN) vlapic.c:702:d1 Local APIC Write to read-only register 0x20
> (XEN) domctl.c:1071:d0 ioport_map:remove f_gport=c100 f_mport=e0c0
> np=20
> (XEN) domctl.c:1047:d0 ioport_map:add f_gport=c100 f_mport=e0c0 np=20
> (XEN) irq.c:243: Dom1 PCI link 0 changed 5 -> 0
> (XEN) irq.c:243: Dom1 PCI link 1 changed 10 -> 0
> (XEN) irq.c:243: Dom1 PCI link 2 changed 11 -> 0
> (XEN) irq.c:243: Dom1 PCI link 3 changed 5 -> 0
> [  679.719530] pciback pci-2-0: 22 Couldn't locate PCI device
> (0000:00:1a.0)! perhaps already in-use?


Uhh. So you assigned the device to 'pci-stub', and somehow 'pciback' gets
involved. That is not good. PCI back is to be used _only_ with
PV guests - you on the other hand are running an HVM guest.

Per the earlier statement, I would recommend you use the 'pciback'
instead of 'pci-stub' or just not compile pciback in and see what
happens. Keep in mind: PCI back module is only needed when you want to do PV PCI
passthrough, which is not what you are doing.



> (XEN) HVM2: HVM Loader
> (XEN) HVM2: Detected Xen v4.0.0-rc6
> (XEN) HVM2: CPU speed is 2800 MHz
> (XEN) irq.c:243: Dom2 PCI link 0 changed 0 -> 5
> (XEN) HVM2: PCI-ISA link 0 routed to IRQ5
> (XEN) irq.c:243: Dom2 PCI link 1 changed 0 -> 10
> (XEN) HVM2: PCI-ISA link 1 routed to IRQ10
> (XEN) irq.c:243: Dom2 PCI link 2 changed 0 -> 11
> (XEN) HVM2: PCI-ISA link 2 routed to IRQ11
> (XEN) irq.c:243: Dom2 PCI link 3 changed 0 -> 5
> (XEN) HVM2: PCI-ISA link 3 routed to IRQ5
> (XEN) HVM2: pci dev 01:3 INTA->IRQ10
> (XEN) HVM2: pci dev 03:0 INTA->IRQ5
> (XEN) HVM2: pci dev 04:0 INTA->IRQ5
> (XEN) HVM2: pci dev 02:0 bar 10 size 02000000: f0000008
> (XEN) HVM2: pci dev 03:0 bar 14 size 01000000: f2000008
> (XEN) HVM2: pci dev 02:0 bar 14 size 00001000: f3000000
> (XEN) HVM2: pci dev 03:0 bar 10 size 00000100: 0000c001
> (XEN) domctl.c:1047:d0 ioport_map:add f_gport=c100 f_mport=e0c0 np=20
> (XEN) HVM2: pci dev 04:0 bar 20 size 00000020: 0000c101
> (XEN) HVM2: pci dev 01:1 bar 20 size 00000010: 0000c121
> (XEN) HVM2: Multiprocessor initialisation:
> (XEN) HVM2:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs
> [2/8] ... done.
> (XEN) HVM2: Writing SMBIOS tables ...
> (XEN) HVM2: Loading ROMBIOS ...
> (XEN) HVM2: 10556 bytes of ROMBIOS high-memory extensions:
> (XEN) HVM2:   Relocating to 0xfc000000-0xfc00293c ... done
> (XEN) HVM2: Creating MP tables ...
> (XEN) HVM2: Loading Cirrus VGABIOS ...
> (XEN) HVM2: Loading ACPI ...
> (XEN) HVM2:  - Lo data: 000ea020-000ea04f
> (XEN) HVM2:  - Hi data: fc002c00-fc012d1f
> (XEN) HVM2: vm86 TSS at fc013000
> (XEN) HVM2: BIOS map:
> (XEN) HVM2:  c0000-c8fff: VGA BIOS
> (XEN) HVM2:  eb000-eb148: SMBIOS tables
> (XEN) HVM2:  f0000-fffff: Main BIOS
> (XEN) HVM2: Invoking ROMBIOS ...
> (XEN) HVM2: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
> (XEN) stdvga.c:147:d2 entering stdvga and caching modes
> (XEN) HVM2: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert
> Exp $
> (XEN) HVM2: Bochs BIOS - build: 06/23/99
> (XEN) HVM2: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
> (XEN) HVM2: Options: apmbios pcibios eltorito PMM
> (XEN) HVM2:
> (XEN) HVM2: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
> (XEN) HVM2: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (20480 MBytes)
> (XEN) HVM2: IDE time out
> (XEN) HVM2: ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
> (XEN) HVM2: IDE time out
> (XEN) HVM2:
> (XEN) HVM2:
> (XEN) HVM2:
> (XEN) HVM2: Press F12 for boot menu.
> (XEN) HVM2:
> (XEN) HVM2: Booting from Hard Disk...
> (XEN) HVM2: Booting from 0000:7c00
> (XEN) stdvga.c:151:d2 leaving stdvga
> (XEN) stdvga.c:147:d2 entering stdvga and caching modes
> (XEN) vlapic.c:702:d2 Local APIC Write to read-only register 0x30
> (XEN) vlapic.c:702:d2 Local APIC Write to read-only register 0x20
> (XEN) vlapic.c:702:d2 Local APIC Write to read-only register 0x20
> (XEN) domctl.c:1071:d0 ioport_map:remove f_gport=c100 f_mport=e0c0
> np=20
> (XEN) domctl.c:1047:d0 ioport_map:add f_gport=c100 f_mport=e0c0 np=20
> (XEN) irq.c:243: Dom2 PCI link 0 changed 5 -> 0
> (XEN) irq.c:243: Dom2 PCI link 1 changed 10 -> 0
> (XEN) irq.c:243: Dom2 PCI link 2 changed 11 -> 0
> (XEN) irq.c:243: Dom2 PCI link 3 changed 5 -> 0
> [  733.248052] pciback pci-3-0: 22 Couldn't locate PCI device
> (0000:00:1a.0)! perhaps already in-use?

Can you paste your 'xenstore-ls /local/domain/0' output when this
happening?

> [  733.253535] BUG: spinlock wrong CPU on CPU#1, xenwatch/16
> [  733.256210]  lock: ffff880006792208, .magic: dead4ead, .owner:
> xenwatch/16, .owner_cpu: 0
> [  733.257409] Pid: 16, comm: xenwatch Not tainted 2.6.32-amd64 #1
> [  733.257409] Call Trace:
> [  733.257409]  [<ffffffff81191b29>] ? _raw_spin_unlock+0x6e/0x82
> [  733.257409]  [<ffffffff811ef98f>] ?
> pciback_setup_backend+0x244/0x27e

> [  733.257409]  [<ffffffff8100ecef>] ?
> xen_restore_fl_direct_end+0x0/0x1
> [  733.257409]  [<ffffffff811ead2d>] ? xenbus_gather+0xda/0x125
> [  733.257409]  [<ffffffff812f8fcb>] ?
> _spin_unlock_irqrestore+0x34/0x36
> [  733.257409]  [<ffffffff811efec3>] ?
> pciback_xenbus_probe+0x122/0x147
> [  733.257409]  [<ffffffff811eb773>] ? xenbus_dev_probe+0x8b/0x125
> [  733.257409]  [<ffffffff81221905>] ? driver_probe_device+0x9f/0x126
> [  733.257409]  [<ffffffff812219fb>] ? __device_attach+0x0/0x39
> [  733.257409]  [<ffffffff81220d27>] ? bus_for_each_drv+0x47/0x7b
> [  733.257409]  [<ffffffff81221ab8>] ? device_attach+0x5e/0x7e
> [  733.257409]  [<ffffffff81220b99>] ? bus_probe_device+0x22/0x3c
> [  733.257409]  [<ffffffff8121f8c7>] ? device_add+0x372/0x519
> [  733.257409]  [<ffffffff8121ec3b>] ? dev_set_name+0x3f/0x44
> [  733.257409]  [<ffffffff811eba89>] ? xenbus_probe_node+0x136/0x1dd
> [  733.317104]  [<ffffffff811ebc8a>] ? xenbus_dev_changed+0x15a/0x18c
> [  733.317104]  [<ffffffff811ea0f3>] ? xenwatch_thread+0x11f/0x15c
> [  733.317104]  [<ffffffff8105ea7c>] ?
> autoremove_wake_function+0x0/0x2a
> [  733.317104]  [<ffffffff811e9fd4>] ? xenwatch_thread+0x0/0x15c
> [  733.317104]  [<ffffffff8105e7cf>] ? kthread+0x75/0x7d
> [  733.317104]  [<ffffffff81012baa>] ? child_rip+0xa/0x20
> [  733.317104]  [<ffffffff81011d61>] ? int_ret_from_sys_call+0x7/0x1b
> [  733.317104]  [<ffffffff8101251d>] ? retint_restore_args+0x5/0x6
> [  733.317104]  [<ffffffff81012ba0>] ? child_rip+0x0/0x20
> (XEN) HVM3: HVM Loader
> (XEN) HVM3: Detected Xen v4.0.0-rc6
> (XEN) HVM3: CPU speed is 2800 MHz
> (XEN) irq.c:243: Dom3 PCI link 0 changed 0 -> 5
> (XEN) HVM3: PCI-ISA link 0 routed to IRQ5
> (XEN) irq.c:243: Dom3 PCI link 1 changed 0 -> 10
> (XEN) HVM3: PCI-ISA link 1 routed to IRQ10
> (XEN) irq.c:243: Dom3 PCI link 2 changed 0 -> 11
> (XEN) HVM3: PCI-ISA link 2 routed to IRQ11
> (XEN) irq.c:243: Dom3 PCI link 3 changed 0 -> 5
> (XEN) HVM3: PCI-ISA link 3 routed to IRQ5
> (XEN) HVM3: pci dev 01:3 INTA->IRQ10
> (XEN) HVM3: pci dev 03:0 INTA->IRQ5
> (XEN) HVM3: pci dev 04:0 INTA->IRQ5
> (XEN) HVM3: pci dev 02:0 bar 10 size 02000000: f0000008
> (XEN) HVM3: pci dev 03:0 bar 14 size 01000000: f2000008
> (XEN) HVM3: pci dev 02:0 bar 14 size 00001000: f3000000
> (XEN) HVM3: pci dev 03:0 bar 10 size 00000100: 0000c001
> (XEN) domctl.c:1047:d0 ioport_map:add f_gport=c100 f_mport=e0c0 np=20
> (XEN) HVM3: pci dev 04:0 bar 20 size 00000020: 0000c101
> (XEN) HVM3: pci dev 01:1 bar 20 size 00000010: 0000c121
> (XEN) HVM3: Multiprocessor initialisation:
> (XEN) HVM3:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs
> [2/8] ... done.
> (XEN) HVM3: Writing SMBIOS tables ...
> (XEN) HVM3: Loading ROMBIOS ...
> (XEN) HVM3: 10556 bytes of ROMBIOS high-memory extensions:
> (XEN) HVM3:   Relocating to 0xfc000000-0xfc00293c ... done
> (XEN) HVM3: Creating MP tables ...
> (XEN) HVM3: Loading Cirrus VGABIOS ...
> (XEN) HVM3: Loading ACPI ...
> (XEN) HVM3:  - Lo data: 000ea020-000ea04f
> (XEN) HVM3:  - Hi data: fc002c00-fc012d1f
> (XEN) HVM3: vm86 TSS at fc013000
> (XEN) HVM3: BIOS map:
> (XEN) HVM3:  c0000-c8fff: VGA BIOS
> (XEN) HVM3:  eb000-eb148: SMBIOS tables
> (XEN) HVM3:  f0000-fffff: Main BIOS
> (XEN) HVM3: Invoking ROMBIOS ...
> (XEN) HVM3: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
> (XEN) stdvga.c:147:d3 entering stdvga and caching modes
> (XEN) HVM3: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $
> (XEN) HVM3: Bochs BIOS - build: 06/23/99
> (XEN) HVM3: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
> (XEN) HVM3: Options: apmbios pcibios eltorito PMM
> (XEN) HVM3:
> (XEN) HVM3: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
> (XEN) HVM3: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (20480 MBytes)
> (XEN) HVM3: IDE time out
> (XEN) HVM3: ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
> (XEN) HVM3: IDE time out
> (XEN) HVM3:
> (XEN) HVM3:
> (XEN) HVM3:
> (XEN) HVM3: Press F12 for boot menu.
> (XEN) HVM3:
> (XEN) HVM3: Booting from Hard Disk...
> (XEN) HVM3: Booting from 0000:7c00
> (XEN) stdvga.c:151:d3 leaving stdvga
> (XEN) stdvga.c:147:d3 entering stdvga and caching modes
> (XEN) vlapic.c:702:d3 Local APIC Write to read-only register 0x30
> (XEN) vlapic.c:702:d3 Local APIC Write to read-only register 0x20
> (XEN) vlapic.c:702:d3 Local APIC Write to read-only register 0x20
> (XEN) domctl.c:1071:d0 ioport_map:remove f_gport=c100 f_mport=e0c0 np=20
> (XEN) domctl.c:1047:d0 ioport_map:add f_gport=c100 f_mport=e0c0 np=20
> (XEN) irq.c:243: Dom3 PCI link 0 changed 5 -> 0
> (XEN) irq.c:243: Dom3 PCI link 1 changed 10 -> 0
> (XEN) irq.c:243: Dom3 PCI link 2 changed 11 -> 0
> (XEN) irq.c:243: Dom3 PCI link 3 changed 5 -> 0
> 
> 
> SECOND:
> 
>  I used FC card to pass-through(it uses ql2axxx module).
> 
> And I got:
> [  188.166084] pciback pci-1-0: 22 Couldn't locate PCI device
> (0000:01:00.0)! perhaps already in-use?
> (XEN) HVM1: HVM Loader
> (XEN) HVM1: Detected Xen v4.0.0-rc6
> (XEN) HVM1: CPU speed is 2800 MHz
> (XEN) irq.c:243: Dom1 PCI link 0 changed 0 -> 5
> (XEN) HVM1: PCI-ISA link 0 routed to IRQ5
> (XEN) irq.c:243: Dom1 PCI link 1 changed 0 -> 10
> (XEN) HVM1: PCI-ISA link 1 routed to IRQ10
> (XEN) irq.c:243: Dom1 PCI link 2 changed 0 -> 11
> (XEN) HVM1: PCI-ISA link 2 routed to IRQ11
> (XEN) irq.c:243: Dom1 PCI link 3 changed 0 -> 5
> (XEN) HVM1: PCI-ISA link 3 routed to IRQ5
> (XEN) HVM1: pci dev 01:3 INTA->IRQ10
> (XEN) HVM1: pci dev 03:0 INTA->IRQ5
> (XEN) HVM1: pci dev 04:0 INTA->IRQ5
> (XEN) HVM1: pci dev 02:0 bar 10 size 02000000: f0000008
> (XEN) HVM1: pci dev 03:0 bar 14 size 01000000: f2000008
> (XEN) HVM1: pci dev 04:0 bar 30 size 00020000: f3000000
> (XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f3020000
> (XEN) domctl.c:991:d0 memory_map:add: gfn=f3021 mfn=fe921 nr_mfns=1
> (XEN) HVM1: pci dev 04:0 bar 14 size 00001000: f3021000
> (XEN) HVM1: pci dev 03:0 bar 10 size 00000100: 0000c001
> (XEN) domctl.c:1047:d0 ioport_map:add f_gport=c100 f_mport=d000 np=100
> (XEN) HVM1: pci dev 04:0 bar 10 size 00000100: 0000c101
> (XEN) HVM1: pci dev 01:1 bar 20 size 00000010: 0000c201
> (XEN) HVM1: Multiprocessor initialisation:
> (XEN) HVM1:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs
> [2/8] ... done.
> (XEN) HVM1: Writing SMBIOS tables ...
> (XEN) HVM1: Loading ROMBIOS ...
> (XEN) HVM1: 10556 bytes of ROMBIOS high-memory extensions:
> (XEN) HVM1:   Relocating to 0xfc000000-0xfc00293c ... done
> (XEN) HVM1: Creating MP tables ...
> (XEN) HVM1: Loading Cirrus VGABIOS ...


> (XEN) domctl.c:991:d0 memory_map:add: gfn=f3000 mfn=40000 nr_mfns=20
> (XEN) mm.c:859:d1 Error getting mfn 40000 (pfn 5555555555555555) from
> L1 entry 0000000040000037 for l1e_owner=1, pg_owner=1
> (XEN) mm.c:859:d1 Error getting mfn 40001 (pfn 5555555555555555) from
> L1 entry 0000000040001037 for l1e_owner=1, pg_owner=1
> (XEN) mm.c:859:d1 Error getting mfn 40002 (pfn 5555555555555555) from
> L1 entry 0000000040002037 for l1e_owner=1, pg_owner=1
> (XEN) mm.c:859:d1 Error getting mfn 40003 (pfn 5555555555555555) from
> L1 entry 0000000040003037 for l1e_owner=1, pg_owner=1
> (XEN) mm.c:859:d1 Error getting mfn 40004 (pfn 5555555555555555) from
> L1 entry 0000000040004037 for l1e_owner=1, pg_owner=1
> ...
> 
> 
> And guest never starts.  Perhaps this is related to the firmware which
> is used by qla2xxx?

So you see this _only_ when you pass in QLA2XXX card, right? When you
don't pass in a PCI card, you don't see this, correct?


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-devel] Re: [pvops xen/next ][iommu] attenpt to passthrough PCI-e usb controllor to PV domU: (XEN) traps.c:2309:d1 Domain attempted WRMSR 000000000000008b from 00000a07:00000000 to 00000000:00000000., Konrad Rzeszutek Wilk
Next by Date:  Re: [Xen-devel] Re: [Xen-users] pvops dom0 kernel: crash in print_all_ICs(), Pasi Kärkkäinen
Previous by Thread:  Re: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Łukasz Oleś
Next by Thread:  RE: [Xen-devel] Re: [vt-d][xen4-rc6] Hangs on startup, Nadolski, Ed
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy