The guest's log without vt-d device assignment as following:
Linux version 2.6.18-128.el5 (mockbuild@xxxxxxxxxxxxxxxxxxxx) (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=/dev/VolGroup00/LogVol00 rhgb console=ttyS0, 115200,
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=/dev/VolGroup00/LogVol00 rhgb console=ttyS0,
115200, 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.53 BogoMIPS
(lpj=1997268)
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 6250187
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.064 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=routeirq". If it helps, post a
report
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = 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
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1261395690.009:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
alg: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key 75ED35FE9471DC0E
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Limiting direct PCI/PCI transfers.
PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
Activating ISA DMA hang workarounds.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
l8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX3: IDE controller at PCI slot 0000:00:01.1
PIIX3: chipset revision 0
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xc100-0xc107, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xc108-0xc10f, BIOS settings: hdc:pio, hdd:pio
hda: QEMU HARDDISK, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 512KiB
hda: 20480000 sectors (10485 MB) w/256KiB Cache, CHS=16383/255/63, (U)DMA
hda: cache flushes supported
hda: hda1 hda2
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S3 S4 S5)
Freeing unused kernel memory: 200k freed
Write protecting the kernel read-only data: 482k
Red Hat nash version 5.1.19.6 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
input: AT Translated Set 2 keyboard as /class/input/input0
input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
Creating block device nodes.
Loading ehci-hcd.ko module
Loading ohci-hcd.ko module
Loading uhci-hcd.ko module
USB Universal Host Controller Interface driver v3.0
Loading jbd.ko module
Loading ext3.ko module
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Loading libata.ko module
Loading ata_piix.ko module
Loading dm-mod.ko module
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-devel@xxxxxxxxxx
Loading dm-log.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Loading dm-mem-cache.ko module
Loading dm-region_hash.ko module
Loading dm-message.ko module
Loading dm-raid45.ko module
device-mapper: dm-raid45: initialized v0.2429
Waiting for driver initialization.
Scanning and configuring dmraid supported devices
Scanning logical volumes
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
2 logical volume(s) in volume group "VolGroup00" now active
Trying to resume from /dev/VolGroup00/LogVol01
No suspend signature on swap, not resuming.
Creating root device.
Mounting root filesystem.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
type=1404 audit(1261395715.680:2): enforcing=1 old_enforcing=0
auid=4294967295 ses=4294967295
type=1403 audit(1261395715.973:3): policy loaded auid=4294967295
ses=4294967295
INIT: version 2.86 booting
Welcome to CentOS release 5.3 (Final)
Press 'I' to enter interactive startup.
Setting clock (utc): Mon Dec 21 06:41:59 EST 2009 [ OK ]
Starting udev: [ OK ]
Loading default keymap (us): [ OK ]
Setting hostname localhost.localdomain: [ OK ]
Setting up Logical Volume Management: 2 logical volume(s) in volume group
"VolGroup00" now active
[ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VolGroup00/LogVol00
/dev/VolGroup00/LogVol00: clean, 100174/1893120 files, 766467/1892352 blocks
[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/hda1
/boot: clean, 34/26104 files, 15723/104388 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
INIT: Entering runlevel: 5
Entering non-interactive startup
Applying Intel CPU microcode update: [ OK ]
Starting monitoring for VG VolGroup00: 2 logical volume(s) in volume group
"VolGroup00" monitored
[ OK ]
Starting background readahead: [ OK ]
Checking for hardware changes [ OK ]
Starting mcstransd: [ OK ]
Bringing up loopback interface: [ OK ]
Starting auditd: [ OK ]
Starting restorecond: [ OK ]
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
Starting irqbalance: [ OK ]
Starting portmap: [ OK ]
Starting NFS statd: [ OK ]
Starting RPC idmapd: [ OK ]
Starting system message bus: [ OK ]
[ OK ] Bluetooth services:[ OK ]
Mounting other filesystems: [ OK ]
Starting PC/SC smart card daemon (pcscd): [ OK ]
Starting hidd: [ OK ]
Starting autofs: Loading autofs4: [ OK ]
Starting automount: [ OK ]
[ OK ]
Starting acpi daemon: [ OK ]
Starting hpiod: [ OK ]
Starting hpssd: [ OK ]
Starting sshd: [ OK ]
Starting cups: [ OK ]
Starting sendmail: [ OK ]
Starting sm-client: [ OK ]
Starting console mouse services: [ OK ]
Starting crond: [ OK ]
Starting xfs: [ OK ]
Starting anacron: [ OK ]
Starting atd: [ OK ]
Starting background readahead: [ OK ]
Starting yum-updatesd: [ OK ]
Starting Avahi daemon... [ OK ]
Starting HAL daemon: [ OK ]
Starting smartd: [ OK ]
CentOS release 5.3 (Final)
Kernel 2.6.18-128.el5 on an x86_64
localhost.localdomain login: mtrr: type mismatch for f0000000,100000 old:
uncachable new: write-combining
mtrr: type mismatch for f0000000,400000 old: uncachable new: write-combining
The assigned device is a net card, its BDF is 02:00.01.
If I only put the card into pciback driver, I run the command xm
pci-list-assignable-devices, nothing showed out.
But if I also put the card with BDF 02:00:00 into the pciback driver, then I
run the command xm pci-list-assignable-devices, I can find what I want,
there are info of two cards.
-----邮件原件-----
发件人: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] 代表 Zhang, Xiantao
发送时间: 2009年12月21日 10:58
收件人: 沈启龙; Han, Weidong; Jiang, Yunhong; 'Konrad Rzeszutek Wilk'
抄送: xen-devel@xxxxxxxxxxxxxxxxxxx
主题: RE: [Xen-devel] Linux DomU halted very early afterbootedwithVT-ddevice
Could you paste the guest's log without vt-d devcie assignment ?
In you mail, you said: "And I use the command xm
pci-list-assignable-devices, nothing show."
So when to run the command ? Before creating the vm or after ?
Xiantao
沈启龙 wrote:
> I had created a vm without device assignment with VT-d, and it could
> run normally.
>
> Regards,
> shenqilong
>
> -----邮件原件-----
> 发件人: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] 代表 Han, Weidong
> 发送时间: 2009年12月21日 10:25
> 收件人: 沈启龙; Zhang, Xiantao; Jiang, Yunhong; 'Konrad Rzeszutek Wilk'
> 抄送: xen-devel@xxxxxxxxxxxxxxxxxxx
> 主题: RE: [Xen-devel] Linux DomU halted very early after
> bootedwithVT-ddevice
>
> Did you try to create the guest without device assignment with VT-d?
>
> Regards,
> Weidong
>
> -----Original Message-----
> From: 沈启龙 [mailto:shen.qilong@xxxxxxxxxxxx]
> Sent: Monday, December 21, 2009 9:21 AM
> To: Zhang, Xiantao; Han, Weidong; Jiang, Yunhong; 'Konrad Rzeszutek
> Wilk' Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: 答复: [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@xxxxxxxxxxxxxxxxxxxx) (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=/dev/VolGroup00/LogVol00 rhgb console=ttyS0,
> 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=/dev/VolGroup00/LogVol00 rhgb
> console=ttyS0, 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=1997409) 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=routeirq". If it helps, post
> a report
> NetLabel: Initializing
> NetLabel: domain hash size = 128
> NetLabel: protocols = 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=routeirq 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
>
> -----邮件原件-----
> 发件人: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] 代表 Zhang, Xiantao
> 发送时间: 2009年12月18日 23:56
> 收件人: Han, Weidong; 沈启龙; Jiang, Yunhong; 'Konrad Rzeszutek Wilk'
> 抄送: xen-devel@xxxxxxxxxxxxxxxxxxx
> 主题: RE: [Xen-devel] Linux DomU halted very early after booted
> withVT-ddevice
>
> Another mothod is to add "console=ttyS0, 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.
> Xiantao
>
>
> Han, Weidong wrote:
>> Can you create CentOS guest without device assignment? If so, you can
>> log in and remove "quiet" in grub.
>>
>> Regards,
>> Weidong
>>
>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 沈启龙 Sent:
>> Tuesday, December 15, 2009 3:36 PM
>> To: Jiang, Yunhong; 'Konrad Rzeszutek Wilk'
>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: 答复: [Xen-devel] Linux DomU halted very early after booted
>> withVT-d device
>>
>> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home