答复: [Xen-devel] Linux DomU halted very early after booted withVT-d device

[沈启龙 <shen.qilong@xxxxxxxxxxxx>]

I don't add "quiet" option in domU kernel parameter, and the Linux domU is
not completely booted. So I can't log in to dump kernel message.

Now I find some other information.
I have "iommu=1 loglvl=all guest_loglvl=all " in my dom0 kernel parameter?

When I boot centos DumU, I can get the following logger.

(XEN) [VT-D]iommu.c:1357:d32767 domain_context_unmap:PCIe: bdf = 2:0.1
(XEN) [VT-D]iommu.c:1245:d32767 domain_context_mapping:PCIe: bdf = 2:0.1
(XEN) [VT-D]iommu.c:1357:d0 domain_context_unmap:PCIe: bdf = 2:0.1
(XEN) [VT-D]iommu.c:1245:d0 domain_context_mapping:PCIe: bdf = 2:0.1
(XEN) [VT-D]io.c:251:d0 VT-d irq bind: m_irq = ff device = 3 intx = 0
(XEN) HVM2: HVM Loader
(XEN) HVM2: Detected Xen v3.4-091208
(XEN) HVM2: CPU speed is 1995 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 10 size 02000000: f2000004
(XEN) domctl.c:835:d0 memory_map:add: gfn=f2000 mfn=dc000 nr_mfns=2000
(XEN) domctl.c:845:d0 memory_map:remove: gfn=f200c mfn=dc00c nr_mfns=1
(XEN) HVM2: pci dev 04:0 bar 14 size 01000000: f4000008
(XEN) HVM2: pci dev 02:0 bar 14 size 00001000: f5000000
(XEN) HVM2: pci dev 04:0 bar 10 size 00000100: 0000c001
(XEN) HVM2: pci dev 01:1 bar 20 size 00000010: 0000c101
(XEN) HVM2: Multiprocessor initialisation:
(XEN) HVM2:  - CPU0 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8] ...
done.
(XEN) HVM2: Writing SMBIOS tables ...
(XEN) HVM2: Loading ROMBIOS ...
(XEN) HVM2: 10300 bytes of ROMBIOS high-memory extensions:
(XEN) HVM2:   Relocating to 0xfc000000-0xfc00283c ... 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-fc00609f
(XEN) HVM2: vm86 TSS at fc006400
(XEN) HVM2: BIOS map:
(XEN) HVM2:  c0000-c8fff: VGA BIOS
(XEN) HVM2:  eb000-eb14a: 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 (10000 MBytes)
(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) HVM2: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM2: int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) HVM2: *** int 15h function AX=00c0, BX=0000 not yet supported!
(XEN) HVM2: int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) HVM2: *** int 15h function AX=ec00, BX=0002 not yet supported!
(XEN) HVM2: KBD: unsupported int 16h function 03
(XEN) HVM2: int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) HVM2: int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) domctl.c:835:d0 memory_map:add: gfn=f200c mfn=dc00c nr_mfns=1
(XEN) domctl.c:845:d0 memory_map:remove: gfn=f2000 mfn=dc000 nr_mfns=2000
(XEN) domctl.c:835:d0 memory_map:add: gfn=fe000 mfn=dc000 nr_mfns=2000
(XEN) domctl.c:845:d0 memory_map:remove: gfn=fe00c mfn=dc00c nr_mfns=1
(XEN) domctl.c:835:d0 memory_map:add: gfn=fe00c mfn=dc00c nr_mfns=1
(XEN) domctl.c:845:d0 memory_map:remove: gfn=fe000 mfn=dc000 nr_mfns=2000
(XEN) domctl.c:835:d0 memory_map:add: gfn=f2000 mfn=dc000 nr_mfns=2000
(XEN) domctl.c:845:d0 memory_map:remove: gfn=f200c mfn=dc00c nr_mfns=1
(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

And I use command xm debug-key V (dump iommu info)

(XEN) iommu 0: nr_pt_levels = 4.
(XEN)   Queued Invalidation: supported and enabled.
(XEN)   Interrupt Remapping: not supported.

I think Interrupt Remapping is enable by default, does that mean that the
system don't support vtd completely.

-----邮件原件-----
发件人: Jiang, Yunhong [mailto:yunhong.jiang@xxxxxxxxx] 
发送时间: 2009年12月15日 9:58
收件人: 沈启龙; 'Konrad Rzeszutek Wilk'
抄送: xen-devel@xxxxxxxxxxxxxxxxxxx
主题: RE: [Xen-devel] Linux DomU halted very early after booted withVT-d
device

You have "quiet" in you kernel parameter?

--jyh

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 沈启龙
>Sent: Monday, December 14, 2009 9:46 AM
>To: 'Konrad Rzeszutek Wilk'
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: 答复: [Xen-devel] Linux DomU halted very early after booted
withVT-d
>device
>
>For example
>DomU system is CentOS.
>There is nearly no any out from kernel.
>After grub configure info, the only output info is a logger as following.
>Memory for crash kernel (0x0 to 0x0) notwithin permissible range.
>Then the system halted.
>
>If I don't use vtd option, the following information is "PCI: PIIX3:
>Enabling Passive Release on 0000:00:01:0"
>
>-----邮件原件-----
>发件人: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] 代表 Konrad Rzeszutek Wilk
>发送时间: 2009年12月11日 23:10
>收件人: 沈启龙
>抄送: xen-devel@xxxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
>主题: Re: [Xen-devel] Linux DomU halted very early after booted withVT-d
>device
>
>On Fri, Dec 11, 2009 at 05:11:55PM +0800, 沈启龙 wrote:
>> My windows2k3 server domU can run normally. I can sign into the system
and
>> find the vt-d
>>
>> device, the device is not driverd, but the system can recognize it.
>>
>> However other linux domU can't start normally, it halt very early after
>> booted.
>
>Can you give me the kernel output of the domU?
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel


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