From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?gb2312?B?yfLG9MH6?= Subject: =?gb2312?B?tPC4tDogW1hlbi1kZXZlbF0gTGludXggRG9tVSBoYWx0ZWQgdmVyeQ==?= =?gb2312?B?IGVhcmx5IGFmdGVyIGJvb3RlZHdpdGhWVC1kZGV2aWNl?= Date: Mon, 21 Dec 2009 10:54:18 +0800 Message-ID: <000b01ca81e8$e37d0ea0$2705a8c0@freecloud> References: <000001ca7a41$fc802580$2705a8c0@freecloud><20091211151008.GC19662@phenom.dumpdata.com><001801ca7c5f$33f4d0a0$2705a8c0@freecloud><001701ca7d59$34a154b0$2705a8c0@freecloud><60E426D47DE8EA47AA104E65008A100D05AE7ED663@shzsmsx501.ccr.corp.intel.com><000001ca81db$eab7b790$2705a8c0@freecloud> <60E426D47DE8EA47AA104E65008A100D05CD54608E@shzsmsx501.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <60E426D47DE8EA47AA104E65008A100D05CD54608E@shzsmsx501.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "'Han, Weidong'" , "'Zhang, Xiantao'" , "'Jiang, Yunhong'" , 'Konrad Rzeszutek Wilk' Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I had created a vm without device assignment with VT-d, and it could run normally. Regards, shenqilong -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] =B4=FA=B1=ED Han, Weidong =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA12=D4=C221=C8=D5 10:25 =CA=D5=BC=FE=C8=CB: =C9=F2=C6=F4=C1=FA; Zhang, Xiantao; Jiang, Yunhong; = 'Konrad Rzeszutek Wilk' =B3=AD=CB=CD: xen-devel@lists.xensource.com =D6=F7=CC=E2: RE: [Xen-devel] Linux DomU halted very early after bootedwithVT-ddevice Did you try to create the guest without device assignment with VT-d?=20 Regards, Weidong -----Original Message----- From: =C9=F2=C6=F4=C1=FA [mailto:shen.qilong@21vianet.com]=20 Sent: Monday, December 21, 2009 9:21 AM To: Zhang, Xiantao; Han, Weidong; Jiang, Yunhong; 'Konrad Rzeszutek = Wilk' Cc: xen-devel@lists.xensource.com Subject: =B4=F0=B8=B4: [Xen-devel] Linux DomU halted very early after = booted withVT-ddevice Thank you for you method, I get the domU's dump message as following: Linux version 2.6.18-128.el5 (mockbuild@builder10.centos.org) (gcc = version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Jan 21 10:41:14 EST 2009 Command line: ro root=3D/dev/VolGroup00/LogVol00 rhgb console=3DttyS0, = 11520, 8n1 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000040000000 (usable) BIOS-e820: 00000000fc000000 - 0000000100000000 (reserved) DMI 2.4 = present. No NUMA configuration found Faking a node at 0000000000000000-0000000040000000 Bootmem setup node 0 0000000000000000-0000000040000000 Memory for crash kernel (0x0 to 0x0) notwithin permissible range disabling kdump ACPI: PM-Timer IO Port: 0x1f48 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 7:10 = APIC version 20 ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level) ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level) ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level) Setting = APIC routing to physical flat Using ACPI (MADT) for SMP configuration = information Nosave address range: 000000000009f000 - 00000000000a0000 Nosave address range: 00000000000a0000 - 00000000000e0000 Nosave address range: 00000000000e0000 - 0000000000100000 Allocating PCI resources starting at 50000000 (gap: 40000000:bc000000) SMP: Allowing 1 CPUs, 0 hotplug CPUs Built 1 zonelists. Total pages: 257201 Kernel command line: ro root=3D/dev/VolGroup00/LogVol00 rhgb = console=3DttyS0, 11520, 8n1 Initializing CPU#0 PID hash table entries: 4096 (order: 12, = 32768 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Checking aperture... Memory: 1023668k/1048576k available (2494k kernel code, 24520k reserved, 1263k data, 200k init) Calibrating delay using timer specific routine.. 3994.81 BogoMIPS (lpj=3D1997409) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: = 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 256K CPU: L3 cache: 4096K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 SMP alternatives: switching to UP code Freeing SMP alternatives: 32k freed ACPI: Core revision 20060707 activating NMI Watchdog ... done. Using local APIC timer interrupts. result 6250115 Detected 6.250 MHz APIC timer. Brought up 1 CPUs testing NMI watchdog ... <4>WARNING: CPU#0: NMI appears to be stuck = (0->0)! time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer. time.c: Detected 1995.040 MHz processor. checking if image is initramfs... it is Freeing initrd memory: 3229k freed NET: Registered protocol family 16 No dock devices found. ACPI: bus type pci registered PCI: Using configuration type 1 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI quirk: region 1f40-1f7f claimed by PIIX4 ACPI ACPI: PCI Interrupt Link [LNKA] (IRQs *5 10 11) ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11) ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs *5 10 11) Linux Plug and Play = Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 12 devices usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=3Drouteirq". If it helps, post = a report NetLabel: Initializing NetLabel: domain hash size =3D 128 NetLabel: protocols =3D UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default PCI-GART: No AMD northbridge found. pnp: 00:02: ioport range 0x10c0-0x10e1 has been reserved pnp: 00:02: ioport range 0xb044-0xb047 has been reserved PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0 NET: Registered protocol family 2 The the vm hang!! And I used the option pci=3Drouteirq as kernel parameter, but the output = is the same. And I use the command xm pci-list-assignable-devices, nothing show. cat /sys/bus/pci/driver/pciback/slots, I can find the pci device what I needed. But if I use cat /sys/bus/pci/driver/pciback/permissive, nothing is = showed out. Best Regards shenqilong -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] =B4=FA=B1=ED Zhang, = Xiantao =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA12=D4=C218=C8=D5 23:56 =CA=D5=BC=FE=C8=CB: Han, Weidong; =C9=F2=C6=F4=C1=FA; Jiang, Yunhong; = 'Konrad Rzeszutek Wilk' =B3=AD=CB=CD: xen-devel@lists.xensource.com =D6=F7=CC=E2: RE: [Xen-devel] Linux DomU halted very early after booted withVT-ddevice Another mothod is to add "console=3DttyS0, 115200, 8n1" to guest's = kernel cmdline in domU's grub and use "xm con $hvm-dom-id" in dom0's terminal = at the same time. Then guest's kernel output should redirect to the dom0's terminal. And once you see the kernel output, maybe you can paste it = here, and it should help to identify this issue.=20 Xiantao Han, Weidong wrote: > Can you create CentOS guest without device assignment? If so, you can > log in and remove "quiet" in grub.=20 >=20 > Regards, > Weidong >=20 > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of = =C9=F2=C6=F4=C1=FA Sent: > Tuesday, December 15, 2009 3:36 PM=20 > To: Jiang, Yunhong; 'Konrad Rzeszutek Wilk' > Cc: xen-devel@lists.xensource.com > Subject: =B4=F0=B8=B4: [Xen-devel] Linux DomU halted very early after = booted > withVT-d device=20 >=20 > I don't add "quiet" option in domU kernel parameter, and the Linux > domU is=20 > not completely booted. So I can't log in to dump kernel message. >=20 > Now I find some other information. > I have "iommu=3D1 loglvl=3Dall guest_loglvl=3Dall " in my dom0 kernel > parameter?=20 >=20 > When I boot centos DumU, I can get the following logger. >=20 > (XEN) [VT-D]iommu.c:1357:d32767 domain_context_unmap:PCIe: bdf =3D = 2:0.1 > (XEN) [VT-D]iommu.c:1245:d32767 domain_context_mapping:PCIe: bdf =3D > 2:0.1 (XEN) [VT-D]iommu.c:1357:d0 domain_context_unmap:PCIe: bdf =3D > 2:0.1 (XEN) [VT-D]iommu.c:1245:d0 domain_context_mapping:PCIe: bdf =3D > 2:0.1 (XEN) [VT-D]io.c:251:d0 VT-d irq bind: m_irq =3D ff device =3D 3 > intx =3D 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=3Df2000 mfn=3Ddc000 = nr_mfns=3D2000 > (XEN) domctl.c:845:d0 memory_map:remove: gfn=3Df200c mfn=3Ddc00c = nr_mfns=3D1 > (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] ...=20 > 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=3D16383/16/63 translation=3Dlba = LCHS=3D1024/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=3D81 > (XEN) HVM2: int13_harddisk: function 08, unmapped device for ELDL=3D81 > (XEN) HVM2: *** int 15h function AX=3D00c0, BX=3D0000 not yet = supported! > (XEN) HVM2: int13_harddisk: function 15, unmapped device for ELDL=3D81 > (XEN) HVM2: *** int 15h function AX=3Dec00, BX=3D0002 not yet = supported! > (XEN) HVM2: KBD: unsupported int 16h function 03 > (XEN) HVM2: int13_harddisk: function 15, unmapped device for ELDL=3D81 > (XEN) HVM2: int13_harddisk: function 02, unmapped device for ELDL=3D81 > (XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=3D81 > (XEN) domctl.c:835:d0 memory_map:add: gfn=3Df200c mfn=3Ddc00c = nr_mfns=3D1 > (XEN) domctl.c:845:d0 memory_map:remove: gfn=3Df2000 mfn=3Ddc000 > nr_mfns=3D2000 (XEN) domctl.c:835:d0 memory_map:add: gfn=3Dfe000 > mfn=3Ddc000 nr_mfns=3D2000 (XEN) domctl.c:845:d0 memory_map:remove: > gfn=3Dfe00c mfn=3Ddc00c nr_mfns=3D1 (XEN) domctl.c:835:d0 = memory_map:add: > gfn=3Dfe00c mfn=3Ddc00c nr_mfns=3D1 (XEN) domctl.c:845:d0 > memory_map:remove: gfn=3Dfe000 mfn=3Ddc000 nr_mfns=3D2000 (XEN) > domctl.c:835:d0 memory_map:add: gfn=3Df2000 mfn=3Ddc000 nr_mfns=3D2000 > (XEN) domctl.c:845:d0 memory_map:remove: gfn=3Df200c mfn=3Ddc00c > nr_mfns=3D1 (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 >=20 > And I use command xm debug-key V (dump iommu info) >=20 > (XEN) iommu 0: nr_pt_levels =3D 4. > (XEN) Queued Invalidation: supported and enabled. > (XEN) Interrupt Remapping: not supported. >=20 > I think Interrupt Remapping is enable by default, does that mean that > the=20 > system don't support vtd completely. >=20 > -----=D3=CA=BC=FE=D4=AD=BC=FE----- > =B7=A2=BC=FE=C8=CB: Jiang, Yunhong [mailto:yunhong.jiang@intel.com] > =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA12=D4=C215=C8=D5 9:58 > =CA=D5=BC=FE=C8=CB: =C9=F2=C6=F4=C1=FA; 'Konrad Rzeszutek Wilk' > =B3=AD=CB=CD: xen-devel@lists.xensource.com > =D6=F7=CC=E2: RE: [Xen-devel] Linux DomU halted very early after = booted withVT-d > device >=20 > You have "quiet" in you kernel parameter? >=20 > --jyh >=20 >> -----Original Message----- >> From: xen-devel-bounces@lists.xensource.com >> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of = =C9=F2=C6=F4=C1=FA >> Sent: Monday, December 14, 2009 9:46 AM >> To: 'Konrad Rzeszutek Wilk' >> Cc: xen-devel@lists.xensource.com >> Subject: =B4=F0=B8=B4: [Xen-devel] Linux DomU halted very early after = booted >> withVT-d device=20 >>=20 >> 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.=20 >> Then the system halted. >>=20 >> If I don't use vtd option, the following information is "PCI: PIIX3: >> Enabling Passive Release on 0000:00:01:0" >>=20 >> -----=D3=CA=BC=FE=D4=AD=BC=FE----- >> =B7=A2=BC=FE=C8=CB: xen-devel-bounces@lists.xensource.com >> [mailto:xen-devel-bounces@lists.xensource.com] =B4=FA=B1=ED Konrad = Rzeszutek >> Wilk =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA12=D4=C211=C8=D5 23:10 = =CA=D5=BC=FE=C8=CB: =C9=F2=C6=F4=C1=FA >> =B3=AD=CB=CD: xen-devel@lists.xensource.com; = xen-users@lists.xensource.com >> =D6=F7=CC=E2: Re: [Xen-devel] Linux DomU halted very early after = booted >> withVT-d device=20 >>=20 >> On Fri, Dec 11, 2009 at 05:11:55PM +0800, =C9=F2=C6=F4=C1=FA wrote: >>> My windows2k3 server domU can run normally. I can sign into the >>> system and find the vt-d=20 >>>=20 >>> device, the device is not driverd, but the system can recognize it. >>>=20 >>> However other linux domU can't start normally, it halt very early >>> after booted. >>=20 >> Can you give me the kernel output of the domU? >>=20 >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >>=20 >>=20 >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel