xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* pv-grub guest booting fail with recent qemu-xen
@ 2016-03-02  7:16 Hao, Xudong
  2016-03-25 18:57 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 15+ messages in thread
From: Hao, Xudong @ 2016-03-02  7:16 UTC (permalink / raw)
  To: xen-devel; +Cc: stefano.stabellini


[-- Attachment #1.1: Type: text/plain, Size: 225 bytes --]

Hi,
For Xen upstream master branch with commit 1949868d, After updating qemu-xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will fail.
Attach the guest config file and Xen log.


Best Regards,
Xudong


[-- Attachment #1.2: Type: text/html, Size: 2694 bytes --]

[-- Attachment #2: xl_dmesg.txt --]
[-- Type: text/plain, Size: 48968 bytes --]

(XEN) Bad console= option '115200'
(XEN) Bad console= option '8n1'
 Xen 4.7-unstable
(XEN) Xen version 4.7-unstable (build@) (gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)) debug=y Fri Jan 29 09:38:36 EST 2016
(XEN) Latest ChangeSet: Sun Jan 24 19:45:51 2016 -0500 git:9937763-dirty
(XEN) Console output is synchronous.
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: dom0_mem=4096M loglvl=all guest_loglvl=all unrestricted_guest=1 msi=1 console=com1,115200,8n1 sync_console hap_1gb=1 conring_size=128M iommu=on,intpost psr=cmt psr=cat psr=cdp cpufreq=performance vpid=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007748f000 (usable)
(XEN)  000000007748f000 - 0000000077510000 (reserved)
(XEN)  0000000077510000 - 0000000078ca1000 (usable)
(XEN)  0000000078ca1000 - 000000007ac51000 (reserved)
(XEN)  000000007ac51000 - 000000007b681000 (ACPI NVS)
(XEN)  000000007b681000 - 000000007b7d3000 (ACPI data)
(XEN)  000000007b7d3000 - 000000007b800000 (usable)
(XEN)  000000007b800000 - 0000000090000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff800000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000880000000 (usable)
(XEN) ACPI: RSDP 000F0540, 0024 (r2 INTEL )
(XEN) ACPI: XSDT 7B7D10E8, 00AC (r1 INTEL  INTEL ID        0 INTL  1000013)
(XEN) ACPI: FACP 7B7D0000, 00F4 (r4 INTEL  INTEL ID        0 INTL 20091013)
(XEN) ACPI: DSDT 7B792000, 338C1 (r2 INTEL  INTEL ID        3 INTL 20091013)
(XEN) ACPI: FACS 7B67D000, 0040
(XEN) ACPI: UEFI 7B675000, 0042 (r1 INTEL  EDK2            2 INTL  1000013)
(XEN) ACPI: HPET 7B7CF000, 0038 (r1 INTEL  INTEL ID        1 INTL 20091013)
(XEN) ACPI: APIC 7B7CE000, 0AFC (r2 INTEL  INTEL ID        0 INTL 20091013)
(XEN) ACPI: MCFG 7B7CD000, 003C (r1 INTEL  INTEL ID        1 INTL 20091013)
(XEN) ACPI: MIGT 7B7CC000, 0040 (r1 INTEL  INTEL ID        0 INTL 20091013)
(XEN) ACPI: MSCT 7B7CB000, 0090 (r1 INTEL  INTEL ID        1 INTL 20091013)
(XEN) ACPI: SLIT 7B7CA000, 006C (r1 INTEL  INTEL ID        1 INTL 20091013)
(XEN) ACPI: SRAT 7B7C8000, 1130 (r3 INTEL  INTEL ID        1 INTL 20091013)
(XEN) ACPI: SVOS 7B7C7000, 0032 (r1 INTEL  INTEL ID        0 INTL 20091013)
(XEN) ACPI: WDDT 7B7C6000, 0040 (r1 INTEL  INTEL ID        0 INTL 20091013)
(XEN) ACPI: SSDT 7B6A8000, E96B0 (r2  INTEL SSDT  PM     4000 INTL 20130328)
(XEN) ACPI: SSDT 7B6A5000, 264A (r2  INTEL SpsNm           2 INTL 20130328)
(XEN) ACPI: SSDT 7B6A4000, 0064 (r2  INTEL SpsNvs          2 INTL 20130328)
(XEN) ACPI: PRAD 7B6A3000, 0102 (r2  INTEL SpsPrAgg        2 INTL 20130328)
(XEN) ACPI: SPCR 7B6A2000, 0050 (r1                        0             0)
(XEN) ACPI: DMAR 7B6A1000, 00A0 (r1 INTEL  INTEL ID        1 INTL 20091013)
(XEN) System RAM: 32651MB (33435564kB)
(XEN) SRAT: PXM 0 -> APIC 00 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 02 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 04 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 06 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 08 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 0a -> Node 0
(XEN) SRAT: PXM 0 -> APIC 10 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 12 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 14 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 16 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 18 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 20 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 22 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 24 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 26 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 28 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 2a -> Node 0
(XEN) SRAT: PXM 0 -> APIC 30 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 32 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 34 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 36 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 38 -> Node 0
(XEN) SRAT: PXM 1 -> APIC 40 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 42 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 44 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 46 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 48 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 4a -> Node 1
(XEN) SRAT: PXM 1 -> APIC 50 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 52 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 54 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 56 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 58 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 60 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 62 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 64 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 66 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 68 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 6a -> Node 1
(XEN) SRAT: PXM 1 -> APIC 70 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 72 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 74 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 76 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 78 -> Node 1
(XEN) SRAT: PXM 0 -> APIC 01 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 03 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 05 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 07 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 09 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 0b -> Node 0
(XEN) SRAT: PXM 0 -> APIC 11 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 13 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 15 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 17 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 19 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 21 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 23 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 25 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 27 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 29 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 2b -> Node 0
(XEN) SRAT: PXM 0 -> APIC 31 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 33 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 35 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 37 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 39 -> Node 0
(XEN) SRAT: PXM 1 -> APIC 41 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 43 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 45 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 47 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 49 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 4b -> Node 1
(XEN) SRAT: PXM 1 -> APIC 51 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 53 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 55 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 57 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 59 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 61 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 63 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 65 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 67 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 69 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 6b -> Node 1
(XEN) SRAT: PXM 1 -> APIC 71 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 73 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 75 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 77 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 79 -> Node 1
(XEN) SRAT: Node 0 PXM 0 0-480000000
(XEN) SRAT: Node 1 PXM 1 480000000-880000000
(XEN) NUMA: Using 19 for the hash shift.
(XEN) Domain heap initialised DMA width 32 bits
(XEN) Allocated console ring of 131072 KiB.
(XEN) found SMP MP-table at 000fd710
(XEN) DMI 2.7 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:404,1:0], pm1x_evt[1:400,1:0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT - 7b67d000/0000000000000000, using 32
(XEN) ACPI:             wakeup_vec[7b67d00c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x14] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x16] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x20] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x22] lapic_id[0x22] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x24] lapic_id[0x24] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x26] lapic_id[0x26] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x28] lapic_id[0x28] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x2a] lapic_id[0x2a] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x30] lapic_id[0x30] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x32] lapic_id[0x32] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x34] lapic_id[0x34] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x36] lapic_id[0x36] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x38] lapic_id[0x38] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x40] lapic_id[0x40] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x42] lapic_id[0x42] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x44] lapic_id[0x44] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x46] lapic_id[0x46] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x48] lapic_id[0x48] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x4a] lapic_id[0x4a] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x50] lapic_id[0x50] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x52] lapic_id[0x52] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x54] lapic_id[0x54] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x56] lapic_id[0x56] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x58] lapic_id[0x58] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x60] lapic_id[0x60] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x62] lapic_id[0x62] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x64] lapic_id[0x64] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x66] lapic_id[0x66] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x68] lapic_id[0x68] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x6a] lapic_id[0x6a] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x70] lapic_id[0x70] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x72] lapic_id[0x72] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x74] lapic_id[0x74] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x76] lapic_id[0x76] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x78] lapic_id[0x78] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x15] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x17] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x21] lapic_id[0x21] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x23] lapic_id[0x23] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x25] lapic_id[0x25] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x27] lapic_id[0x27] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x29] lapic_id[0x29] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x2b] lapic_id[0x2b] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x31] lapic_id[0x31] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x33] lapic_id[0x33] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x35] lapic_id[0x35] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x37] lapic_id[0x37] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x39] lapic_id[0x39] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x41] lapic_id[0x41] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x43] lapic_id[0x43] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x45] lapic_id[0x45] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x47] lapic_id[0x47] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x49] lapic_id[0x49] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x4b] lapic_id[0x4b] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x51] lapic_id[0x51] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x53] lapic_id[0x53] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x55] lapic_id[0x55] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x57] lapic_id[0x57] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x59] lapic_id[0x59] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x61] lapic_id[0x61] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x63] lapic_id[0x63] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x65] lapic_id[0x65] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x67] lapic_id[0x67] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x69] lapic_id[0x69] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x6b] lapic_id[0x6b] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x71] lapic_id[0x71] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x73] lapic_id[0x73] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x75] lapic_id[0x75] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x77] lapic_id[0x77] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x79] lapic_id[0x79] enabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC (acpi_id[0xff] lapic_id[0xff] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x08] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x09] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0e] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x10] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x11] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x12] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x13] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x14] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x15] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x16] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x17] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x18] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x19] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1e] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x20] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x21] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x22] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x23] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x24] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x25] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x26] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x27] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x28] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x29] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x2a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x2b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x2c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x2d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x2e] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x2f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x30] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x31] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x32] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x33] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x34] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x35] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x36] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x37] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x38] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x39] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x3a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x3b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x3c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x3d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x3e] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x3f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x40] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x41] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x42] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x43] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x44] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x45] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x46] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x47] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x48] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x49] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x4a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x4b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x4c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x4d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x4e] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x4f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x50] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x51] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x52] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x53] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x54] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x55] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x56] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x57] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x58] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x59] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x5a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x5b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x5c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x5d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x5e] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x5f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x60] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x61] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x62] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x63] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x64] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x65] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x66] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x67] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x68] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x69] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x6a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x6b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x6c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x6d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x6e] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x6f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x70] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x71] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x72] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x73] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x74] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x75] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x76] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x77] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x78] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x79] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x7a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x7b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x7c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x7c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x7d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x7e] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x7f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x80] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x81] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x82] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x83] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x84] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x85] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x86] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x87] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x88] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x89] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x8a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x8b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x8c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x8d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x8f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x90] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x91] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x92] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x93] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x94] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x95] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x96] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x97] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x98] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x99] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x9a] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x9b] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x9c] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x9d] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x9e] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x9f] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa0] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa1] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa2] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa3] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa4] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa5] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa6] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa7] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa8] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xa9] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xaa] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xab] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xac] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xad] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xae] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xaf] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb0] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb1] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb2] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb3] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb4] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb5] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb6] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb7] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb8] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xb9] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xba] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xbb] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xbc] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xbd] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xbe] high level lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0xbf] high level lint[0x1])
(XEN) Overriding APIC driver with bigsmp
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
(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 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Phys.  Using 3 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) ERST table was not found
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 192 CPUs (104 hotplug CPUs)
(XEN) IRQ limits: 72 GSI, 16840 MSI/MSI-X
(XEN) Switched to APIC driver x2apic_cluster.
(XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7
(XEN) mce_intel.c:735: MCA Capability: BCAST 1 SER 1 CMCI 1 firstbank 0 extended MCE MSR 0
(XEN) CMCI: threshold 0x2 too large for CPU0 bank 17, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU0 bank 18, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU0 bank 19, using 0x1
(XEN) Intel machine check reporting enabled
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2194.994 MHz processor.
(XEN) Initing memory sharing.
(XEN) alt table ffff82d0802f1398 -> ffff82d0802f25f8
(XEN) PCI: MCFG configuration 0: base 80000000 segment 0000 buses 00 - ff
(XEN) PCI: MCFG area at 80000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Posted Interrupt not enabled.
(XEN) Intel VT-d Shared EPT tables enabled.
(XEN) alloc_pdev: unknown type: 0000:7f:0e.2
(XEN) alloc_pdev: unknown type: 0000:7f:0e.3
(XEN) alloc_pdev: unknown type: 0000:7f:0e.4
(XEN) alloc_pdev: unknown type: 0000:7f:0e.5
(XEN) alloc_pdev: unknown type: 0000:ff:0e.2
(XEN) alloc_pdev: unknown type: 0000:ff:0e.3
(XEN) alloc_pdev: unknown type: 0000:ff:0e.4
(XEN) alloc_pdev: unknown type: 0000:ff:0e.5
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) nr_sockets: 6
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) TSC deadline timer enabled
(XEN) Platform timer is 14.318MHz HPET
(XEN) Defaulting to alternative key handling; send 'A' to switch to normal mode.
(XEN) Cache Monitoring Technology enabled
(XEN) CAT: enabled on socket 0, cos_max:7, cbm_len:20, CDP:on
(XEN) mwait-idle: MWAIT substates: 0x2120
(XEN) mwait-idle: v0.4 model 0x4f
(XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN)  - Unrestricted Guest
(XEN)  - APIC Register Virtualization
(XEN)  - Virtual Interrupt Delivery
(XEN)  - Posted Interrupt Processing
(XEN)  - VMCS shadowing
(XEN)  - VM Functions
(XEN)  - Virtualisation Exceptions
(XEN)  - Page Modification Logging
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) CMCI: threshold 0x2 too large for CPU44 bank 17, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU44 bank 18, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU44 bank 19, using 0x1
(XEN) CAT: enabled on socket 1, cos_max:7, cbm_len:20, CDP:on
(XEN) Brought up 88 CPUs
(XEN) ACPI sleep modes: S3
(XEN) VPMU: disabled
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) Dom0 has maximum 1416 PIRQs
(XEN) NX (Execute Disable) protection active
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0xa5f000
(XEN) elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xde000
(XEN) elf_parse_binary: phdr: paddr=0x1cde000 memsz=0x16698
(XEN) elf_parse_binary: phdr: paddr=0x1cf5000 memsz=0x21c000
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x1f11000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: INIT_P2M = 0x8000000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff81cf51f0
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb|writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel"
(XEN) elf_xen_parse_note: SUPPORTED_FEATURES = 0x90d
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: MOD_START_PFN = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xffffffff80000000
(XEN)     elf_paddr_offset = 0x0
(XEN)     virt_offset      = 0xffffffff80000000
(XEN)     virt_kstart      = 0xffffffff81000000
(XEN)     virt_kend        = 0xffffffff81f11000
(XEN)     virt_entry       = 0xffffffff81cf51f0
(XEN)     p2m_base         = 0x8000000000
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1f11000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000043a000000->000000043c000000 (1026062 pages to be allocated)
(XEN)  Init. ramdisk: 000000087c80e000->000000087ffffa00
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff81f11000
(XEN)  Init. ramdisk: 0000000000000000->0000000000000000
(XEN)  Phys-Mach map: 0000008000000000->0000008000800000
(XEN)  Start info:    ffffffff81f11000->ffffffff81f114b4
(XEN)  Page tables:   ffffffff81f12000->ffffffff81f25000
(XEN)  Boot stack:    ffffffff81f25000->ffffffff81f26000
(XEN)  TOTAL:         ffffffff80000000->ffffffff82000000
(XEN)  ENTRY ADDRESS: ffffffff81cf51f0
(XEN) Dom0 has maximum 88 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81a5f000
(XEN) elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81cde000
(XEN) elf_load_binary: phdr 2 at 0xffffffff81cde000 -> 0xffffffff81cf4698
(XEN) elf_load_binary: phdr 3 at 0xffffffff81cf5000 -> 0xffffffff81e07000
(XEN) [VT-D]iommu.c:1489: d0:unknown(0): 0000:7f:0e.2
(XEN) setup 0000:7f:0e.2 for d0 failed (-22)
(XEN) [VT-D]iommu.c:1489: d0:unknown(0): 0000:7f:0e.3
(XEN) setup 0000:7f:0e.3 for d0 failed (-22)
(XEN) [VT-D]iommu.c:1489: d0:unknown(0): 0000:7f:0e.4
(XEN) setup 0000:7f:0e.4 for d0 failed (-22)
(XEN) [VT-D]iommu.c:1489: d0:unknown(0): 0000:7f:0e.5
(XEN) setup 0000:7f:0e.5 for d0 failed (-22)
(XEN) [VT-D]iommu.c:1489: d0:unknown(0): 0000:ff:0e.2
(XEN) setup 0000:ff:0e.2 for d0 failed (-22)
(XEN) [VT-D]iommu.c:1489: d0:unknown(0): 0000:ff:0e.3
(XEN) setup 0000:ff:0e.3 for d0 failed (-22)
(XEN) [VT-D]iommu.c:1489: d0:unknown(0): 0000:ff:0e.4
(XEN) setup 0000:ff:0e.4 for d0 failed (-22)
(XEN) [VT-D]iommu.c:1489: d0:unknown(0): 0000:ff:0e.5
(XEN) setup 0000:ff:0e.5 for d0 failed (-22)
(XEN) Scrubbing Free RAM on 2 nodes using 44 CPUs
(XEN) .......done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1... 
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 308kB init memory.
(XEN) traps.c:2684:d0v0 Domain attempted WRMSR 00000000000001c9 from 0x0000000000000000 to 0x0000000000000003.
(XEN) traps.c:2684:d0v0 Domain attempted WRMSR 00000000000001a6 from 0x0000000000000000 to 0x0000000000000011.
(XEN) traps.c:2684:d0v0 Domain attempted WRMSR 00000000000001a7 from 0x0000000000000000 to 0x0000000000000011.
(XEN) traps.c:2684:d0v0 Domain attempted WRMSR 00000000000003f6 from 0x000000000000ffff to 0x000000000000ffee.
(XEN) d0: Forcing write emulation on MFNs 80000-8ffff
(XEN) PCI add device 0000:ff:08.0
(XEN) PCI add device 0000:ff:08.2
(XEN) PCI add device 0000:ff:08.3
(XEN) PCI add device 0000:ff:09.0
(XEN) PCI add device 0000:ff:09.2
(XEN) PCI add device 0000:ff:09.3
(XEN) PCI add device 0000:ff:0b.0
(XEN) PCI add device 0000:ff:0b.1
(XEN) PCI add device 0000:ff:0b.2
(XEN) PCI add device 0000:ff:0b.3
(XEN) PCI add device 0000:ff:0c.0
(XEN) PCI add device 0000:ff:0c.1
(XEN) PCI add device 0000:ff:0c.2
(XEN) PCI add device 0000:ff:0c.3
(XEN) PCI add device 0000:ff:0c.4
(XEN) PCI add device 0000:ff:0c.5
(XEN) PCI add device 0000:ff:0c.6
(XEN) PCI add device 0000:ff:0c.7
(XEN) PCI add device 0000:ff:0d.0
(XEN) PCI add device 0000:ff:0d.1
(XEN) PCI add device 0000:ff:0d.2
(XEN) PCI add device 0000:ff:0d.3
(XEN) PCI add device 0000:ff:0d.4
(XEN) PCI add device 0000:ff:0d.5
(XEN) PCI add device 0000:ff:0d.6
(XEN) PCI add device 0000:ff:0d.7
(XEN) PCI add device 0000:ff:0e.0
(XEN) PCI add device 0000:ff:0e.1
(XEN) PCI add device 0000:ff:0e.2
(XEN) PCI add device 0000:ff:0e.3
(XEN) PCI add device 0000:ff:0e.4
(XEN) PCI add device 0000:ff:0e.5
(XEN) PCI add device 0000:ff:0f.0
(XEN) PCI add device 0000:ff:0f.1
(XEN) PCI add device 0000:ff:0f.2
(XEN) PCI add device 0000:ff:0f.3
(XEN) PCI add device 0000:ff:0f.4
(XEN) PCI add device 0000:ff:0f.5
(XEN) PCI add device 0000:ff:0f.6
(XEN) PCI add device 0000:ff:10.0
(XEN) PCI add device 0000:ff:10.1
(XEN) PCI add device 0000:ff:10.5
(XEN) PCI add device 0000:ff:10.6
(XEN) PCI add device 0000:ff:10.7
(XEN) PCI add device 0000:ff:12.0
(XEN) PCI add device 0000:ff:12.1
(XEN) PCI add device 0000:ff:12.4
(XEN) PCI add device 0000:ff:12.5
(XEN) PCI add device 0000:ff:13.0
(XEN) PCI add device 0000:ff:13.1
(XEN) PCI add device 0000:ff:13.2
(XEN) PCI add device 0000:ff:13.3
(XEN) PCI add device 0000:ff:13.6
(XEN) PCI add device 0000:ff:13.7
(XEN) PCI add device 0000:ff:14.0
(XEN) PCI add device 0000:ff:14.1
(XEN) PCI add device 0000:ff:14.2
(XEN) PCI add device 0000:ff:14.3
(XEN) PCI add device 0000:ff:14.4
(XEN) PCI add device 0000:ff:14.5
(XEN) PCI add device 0000:ff:14.6
(XEN) PCI add device 0000:ff:14.7
(XEN) PCI add device 0000:ff:16.0
(XEN) PCI add device 0000:ff:16.1
(XEN) PCI add device 0000:ff:16.2
(XEN) PCI add device 0000:ff:16.3
(XEN) PCI add device 0000:ff:16.6
(XEN) PCI add device 0000:ff:16.7
(XEN) PCI add device 0000:ff:17.0
(XEN) PCI add device 0000:ff:17.1
(XEN) PCI add device 0000:ff:17.2
(XEN) PCI add device 0000:ff:17.3
(XEN) PCI add device 0000:ff:17.4
(XEN) PCI add device 0000:ff:17.5
(XEN) PCI add device 0000:ff:17.6
(XEN) PCI add device 0000:ff:17.7
(XEN) PCI add device 0000:ff:1e.0
(XEN) PCI add device 0000:ff:1e.1
(XEN) PCI add device 0000:ff:1e.2
(XEN) PCI add device 0000:ff:1e.3
(XEN) PCI add device 0000:ff:1e.4
(XEN) PCI add device 0000:ff:1f.0
(XEN) PCI add device 0000:ff:1f.2
(XEN) PCI add device 0000:7f:08.0
(XEN) PCI add device 0000:7f:08.2
(XEN) PCI add device 0000:7f:08.3
(XEN) PCI add device 0000:7f:09.0
(XEN) PCI add device 0000:7f:09.2
(XEN) PCI add device 0000:7f:09.3
(XEN) PCI add device 0000:7f:0b.0
(XEN) PCI add device 0000:7f:0b.1
(XEN) PCI add device 0000:7f:0b.2
(XEN) PCI add device 0000:7f:0b.3
(XEN) PCI add device 0000:7f:0c.0
(XEN) PCI add device 0000:7f:0c.1
(XEN) PCI add device 0000:7f:0c.2
(XEN) PCI add device 0000:7f:0c.3
(XEN) PCI add device 0000:7f:0c.4
(XEN) PCI add device 0000:7f:0c.5
(XEN) PCI add device 0000:7f:0c.6
(XEN) PCI add device 0000:7f:0c.7
(XEN) PCI add device 0000:7f:0d.0
(XEN) PCI add device 0000:7f:0d.1
(XEN) PCI add device 0000:7f:0d.2
(XEN) PCI add device 0000:7f:0d.3
(XEN) PCI add device 0000:7f:0d.4
(XEN) PCI add device 0000:7f:0d.5
(XEN) PCI add device 0000:7f:0d.6
(XEN) PCI add device 0000:7f:0d.7
(XEN) PCI add device 0000:7f:0e.0
(XEN) PCI add device 0000:7f:0e.1
(XEN) PCI add device 0000:7f:0e.2
(XEN) PCI add device 0000:7f:0e.3
(XEN) PCI add device 0000:7f:0e.4
(XEN) PCI add device 0000:7f:0e.5
(XEN) PCI add device 0000:7f:0f.0
(XEN) PCI add device 0000:7f:0f.1
(XEN) PCI add device 0000:7f:0f.2
(XEN) PCI add device 0000:7f:0f.3
(XEN) PCI add device 0000:7f:0f.4
(XEN) PCI add device 0000:7f:0f.5
(XEN) PCI add device 0000:7f:0f.6
(XEN) PCI add device 0000:7f:10.0
(XEN) PCI add device 0000:7f:10.1
(XEN) PCI add device 0000:7f:10.5
(XEN) PCI add device 0000:7f:10.6
(XEN) PCI add device 0000:7f:10.7
(XEN) PCI add device 0000:7f:12.0
(XEN) PCI add device 0000:7f:12.1
(XEN) PCI add device 0000:7f:12.4
(XEN) PCI add device 0000:7f:12.5
(XEN) PCI add device 0000:7f:13.0
(XEN) PCI add device 0000:7f:13.1
(XEN) PCI add device 0000:7f:13.2
(XEN) PCI add device 0000:7f:13.3
(XEN) PCI add device 0000:7f:13.6
(XEN) PCI add device 0000:7f:13.7
(XEN) PCI add device 0000:7f:14.0
(XEN) PCI add device 0000:7f:14.1
(XEN) PCI add device 0000:7f:14.2
(XEN) PCI add device 0000:7f:14.3
(XEN) PCI add device 0000:7f:14.4
(XEN) PCI add device 0000:7f:14.5
(XEN) PCI add device 0000:7f:14.6
(XEN) PCI add device 0000:7f:14.7
(XEN) PCI add device 0000:7f:16.0
(XEN) PCI add device 0000:7f:16.1
(XEN) PCI add device 0000:7f:16.2
(XEN) PCI add device 0000:7f:16.3
(XEN) PCI add device 0000:7f:16.6
(XEN) PCI add device 0000:7f:16.7
(XEN) PCI add device 0000:7f:17.0
(XEN) PCI add device 0000:7f:17.1
(XEN) PCI add device 0000:7f:17.2
(XEN) PCI add device 0000:7f:17.3
(XEN) PCI add device 0000:7f:17.4
(XEN) PCI add device 0000:7f:17.5
(XEN) PCI add device 0000:7f:17.6
(XEN) PCI add device 0000:7f:17.7
(XEN) PCI add device 0000:7f:1e.0
(XEN) PCI add device 0000:7f:1e.1
(XEN) PCI add device 0000:7f:1e.2
(XEN) PCI add device 0000:7f:1e.3
(XEN) PCI add device 0000:7f:1e.4
(XEN) PCI add device 0000:7f:1f.0
(XEN) PCI add device 0000:7f:1f.2
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:01.0
(XEN) PCI add device 0000:00:02.0
(XEN) PCI add device 0000:00:02.2
(XEN) PCI add device 0000:00:03.0
(XEN) PCI add device 0000:00:05.0
(XEN) PCI add device 0000:00:05.1
(XEN) PCI add device 0000:00:05.2
(XEN) PCI add device 0000:00:05.4
(XEN) PCI add device 0000:00:11.0
(XEN) PCI add device 0000:00:14.0
(XEN) PCI add device 0000:00:16.0
(XEN) PCI add device 0000:00:16.1
(XEN) PCI add device 0000:00:1a.0
(XEN) PCI add device 0000:00:1c.0
(XEN) PCI add device 0000:00:1c.3
(XEN) PCI add device 0000:00:1d.0
(XEN) PCI add device 0000:00:1f.0
(XEN) PCI add device 0000:00:1f.2
(XEN) PCI add device 0000:00:1f.3
(XEN) PCI add device 0000:03:00.0
(XEN) PCI add device 0000:03:00.1
(XEN) PCI add device 0000:05:00.0
(XEN) PCI add device 0000:05:00.1
(XEN) PCI add device 0000:08:00.0
(XEN) PCI add device 0000:80:01.0
(XEN) PCI add device 0000:80:05.0
(XEN) PCI add device 0000:80:05.1
(XEN) PCI add device 0000:80:05.2
(XEN) PCI add device 0000:80:05.4
(XEN) PCI add device 0000:81:00.0
(XEN) PCI add device 0000:81:00.1
(XEN) d0: Forcing read-only access to MFN fed00
(XEN) PCI add virtual function 0000:05:10.0
(XEN) PCI add virtual function 0000:05:10.2
(XEN) PCI add virtual function 0000:05:10.4
(XEN) PCI add virtual function 0000:05:10.6
(XEN) PCI add virtual function 0000:05:11.0
(d1) Bootstrapping...
(d1) Xen Minimal OS!
(d1)   start_info: 0xbb3000(VA)
(d1)     nr_pages: 0x40000
(d1)   shared_inf: 0x78c8c000(MA)
(d1)      pt_base: 0xbb6000(VA)
(d1) nr_pt_frames: 0xb
(d1)     mfn_list: 0x9b3000(VA)
(d1)    mod_start: 0x0(VA)
(d1)      mod_len: 0
(d1)        flags: 0x0
(d1)     cmd_line: (hd0,0)/boot/grub/grub.conf
(d1)        stack: 0x972860-0x992860
(d1) MM: Init
(d1)       _text: 0x0(VA)
(d1)      _etext: 0x83e34(VA)
(d1)    _erodata: 0x9f000(VA)
(d1)      _edata: 0xa4da0(VA)
(d1) stack start: 0x972860(VA)
(d1)        _end: 0x9b2e60(VA)
(d1)   start_pfn: bc4
(d1)     max_pfn: 40000
(d1) Mapping memory range 0xbc4000 - 0x40000000
(d1) setting 0x0-0x9f000 readonly
(d1) skipped 1000
(d1) MM: Initialise page allocator for dbc000(dbc000)-40000000(40000000)
(d1) MM: done
(d1) Demand map pfns at 40001000-0x2040001000.
(d1) Heap resides at 2040002000-4040002000.
(d1) Initialising timer interface
(d1) Initialising console ... done.
(d1) gnttab_table mapped at 0x40001000.
(d1) Initialising scheduler
(d1) Thread "Idle": pointer: 0x0x2040002050, stack: 0x0xfd0000
(d1) Thread "xenstore": pointer: 0x0x2040002800, stack: 0x0xfe0000
(d1) xenbus initialised on irq 1 mfn 0x424fb4
(d1) Thread "shutdown": pointer: 0x0x2040002fb0, stack: 0x0xff0000
(d1) main.c: dummy main: start_info=0x992960
(d1) Thread "main": pointer: 0x0x2040003760, stack: 0x0x1000000
(d1) vbd 768 is hd0
(d1) ******************* BLKFRONT for device/vbd/768 **********
(d1) 
(d1) 
(d1) backend at /local/domain/0/backend/qdisk/1/768
(d1) Failed to read /local/domain/0/backend/qdisk/1/768/feature-barrier.
(d1) 16777216 sectors of 512 bytes
(d1) **************************
(d1) Thread "kbdfront": pointer: 0x0x20400045a0, stack: 0x0x1010000
(d1) ******************* FBFRONT for device/vfb/0 **********
(d1) 
(d1) 
(d1) ******************* KBDFRONT for device/vkbd/0 **********
(d1) 
(d1) 
(d1) backend at /local/domain/0/backend/vkbd/1/0
(d1) /local/domain/0/backend/vkbd/1/0 connected
(d1) ************************** KBDFRONT
(d1) Thread "kbdfront" exited.
(d1) backend at /local/domain/0/backend/vfb/1/0
(d1) /local/domain/0/backend/vfb/1/0 connected
(d1) ************************** FBFRONT
(XEN) *********** VMCS Areas **************
(XEN) **************************************
(XEN) *********** VMCS Areas **************
(XEN) **************************************

[-- Attachment #3: config.pvgrub --]
[-- Type: application/octet-stream, Size: 1416 bytes --]

# =====================================================================
# Example PV Linux guest configuration
# =====================================================================
#
# This is a fairly minimal example of what is required for a
# Paravirtualised Linux guest. For a more complete guide see xl.cfg(5)

# Guest name
name = "uCPL_MEM_31_1456205543"

# 128-bit UUID for the domain as a hexadecimal number.
# Use "uuidgen" to generate one if required.
# The default behavior is to generate a new UUID each time the guest is started.
#uuid = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"

# pv-grub here
kernel="/boot/pv-grub-x86_64.gz"
extra= "(hd0,0)/boot/grub/grub.conf" 
# pv-grub end

# Initial memory allocation (MB)
memory = 1024

# Maximum memory (MB)
# If this is greater than `memory' then the slack will start ballooned
# (this assumes guest kernel support for ballooning)
#maxmem = 512

# Number of VCPUS
vcpus = 2

# Network devices
# A list of 'vifspec' entries as described in
# docs/misc/xl-network-configuration.markdown
vif = [ '' ]

# Disk Devices
# A list of `diskspec' entries as described in
# docs/misc/xl-disk-configuration.txt
disk= [ '//share/xvs/var/img.xenUCPL_MEM_31,qcow2,hda,rw' ] 
device_model_override = '/usr/local/lib/xen/bin/qemu-system-i386'
device_model_version = 'qemu-xen'
vfb = [ 'vnc=1,vncpass=' ]

vfb = [ 'vnc=1,vncpass=' ]
stdvga=1
hap=1
acpi=1
gfx_passthru=0
hpet=1

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-03-02  7:16 pv-grub guest booting fail with recent qemu-xen Hao, Xudong
@ 2016-03-25 18:57 ` Konrad Rzeszutek Wilk
  2016-03-28  2:03   ` Hao, Xudong
  0 siblings, 1 reply; 15+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-03-25 18:57 UTC (permalink / raw)
  To: Hao, Xudong; +Cc: stefano.stabellini, xen-devel

On Wed, Mar 02, 2016 at 07:16:40AM +0000, Hao, Xudong wrote:
> Hi,
> For Xen upstream master branch with commit 1949868d, After updating qemu-xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will fail.
> Attach the guest config file and Xen log.

Is this still an issue? I saw an MiniOS patch go by..
> 
> 
> Best Regards,
> Xudong
> 

> (XEN) Bad console= option '115200'
> (XEN) Bad console= option '8n1'

Also your options are incorrect.

>  Xen 4.7-unstable
> (XEN) Xen version 4.7-unstable (build@) (gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)) debug=y Fri Jan 29 09:38:36 EST 2016
> (XEN) Latest ChangeSet: Sun Jan 24 19:45:51 2016 -0500 git:9937763-dirty
> (XEN) Console output is synchronous.
> (XEN) Bootloader: GNU GRUB 0.97
> (XEN) Command line: dom0_mem=4096M loglvl=all guest_loglvl=all unrestricted_guest=1 msi=1 console=com1,115200,8n1 sync_console hap_1gb=1 conring_size=128M iommu=on,intpost psr=cmt psr=cat psr=cdp cpufreq=performance vpid=1

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-03-25 18:57 ` Konrad Rzeszutek Wilk
@ 2016-03-28  2:03   ` Hao, Xudong
  2016-03-28 13:21     ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 15+ messages in thread
From: Hao, Xudong @ 2016-03-28  2:03 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel, stefano.stabellini

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Konrad
> Rzeszutek Wilk
> Sent: Saturday, March 26, 2016 2:58 AM
> To: Hao, Xudong <xudong.hao@intel.com>
> Cc: stefano.stabellini@eu.citrix.com; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> 
> On Wed, Mar 02, 2016 at 07:16:40AM +0000, Hao, Xudong wrote:
> > Hi,
> > For Xen upstream master branch with commit 1949868d, After updating qemu-
> xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will fail.
> > Attach the guest config file and Xen log.
> 
> Is this still an issue? I saw an MiniOS patch go by..

Which patch of miniOS? 

This issue still exist on Xen commit a6f2cdb6. I didn't see update in Confit.mk, the minios revision is still: 
MINIOS_UPSTREAM_REVISION ?= 89268f00b0b0215057cb74edd94e866536a02489

> >
> >
> > Best Regards,
> > Xudong
> >
> 
> > (XEN) Bad console= option '115200'
> > (XEN) Bad console= option '8n1'
> 
> Also your options are incorrect.

It's serial console, what's the error?

Thanks,
-Xudong

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-03-28  2:03   ` Hao, Xudong
@ 2016-03-28 13:21     ` Konrad Rzeszutek Wilk
  2016-03-29  1:44       ` Hao, Xudong
  2016-03-29 16:58       ` Wei Liu
  0 siblings, 2 replies; 15+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-03-28 13:21 UTC (permalink / raw)
  To: Hao, Xudong, wei.liu2, samuel.thibault; +Cc: xen-devel, stefano.stabellini

On Mon, Mar 28, 2016 at 02:03:35AM +0000, Hao, Xudong wrote:
> > -----Original Message-----
> > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Konrad
> > Rzeszutek Wilk
> > Sent: Saturday, March 26, 2016 2:58 AM
> > To: Hao, Xudong <xudong.hao@intel.com>
> > Cc: stefano.stabellini@eu.citrix.com; xen-devel@lists.xen.org
> > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> > 
> > On Wed, Mar 02, 2016 at 07:16:40AM +0000, Hao, Xudong wrote:
> > > Hi,
> > > For Xen upstream master branch with commit 1949868d, After updating qemu-
> > xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will fail.

.. It was not clear to me - but did you do a git bisection?

> > > Attach the guest config file and Xen log.
> > 
> > Is this still an issue? I saw an MiniOS patch go by..
> 
> Which patch of miniOS? 
> 
> This issue still exist on Xen commit a6f2cdb6. I didn't see update in Confit.mk, the minios revision is still: 
> MINIOS_UPSTREAM_REVISION ?= 89268f00b0b0215057cb74edd94e866536a02489

Cc-ing Wei.
> 
> > >
> > >
> > > Best Regards,
> > > Xudong
> > >
> > 
> > > (XEN) Bad console= option '115200'
> > > (XEN) Bad console= option '8n1'
> > 
> > Also your options are incorrect.
> 
> It's serial console, what's the error?

'Bad console= option' - as you can see above.
> 
> Thanks,
> -Xudong
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-03-28 13:21     ` Konrad Rzeszutek Wilk
@ 2016-03-29  1:44       ` Hao, Xudong
  2016-03-29 16:58       ` Wei Liu
  1 sibling, 0 replies; 15+ messages in thread
From: Hao, Xudong @ 2016-03-29  1:44 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk, wei.liu2, samuel.thibault
  Cc: stefano.stabellini, xen-devel

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Konrad
> Rzeszutek Wilk
> Sent: Monday, March 28, 2016 9:21 PM
> To: Hao, Xudong <xudong.hao@intel.com>; wei.liu2@citrix.com;
> samuel.thibault@ens-lyon.org
> Cc: xen-devel@lists.xen.org; stefano.stabellini@eu.citrix.com
> Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> 
> On Mon, Mar 28, 2016 at 02:03:35AM +0000, Hao, Xudong wrote:
> > > -----Original Message-----
> > > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf
> > > Of Konrad Rzeszutek Wilk
> > > Sent: Saturday, March 26, 2016 2:58 AM
> > > To: Hao, Xudong <xudong.hao@intel.com>
> > > Cc: stefano.stabellini@eu.citrix.com; xen-devel@lists.xen.org
> > > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent
> > > qemu-xen
> > >
> > > On Wed, Mar 02, 2016 at 07:16:40AM +0000, Hao, Xudong wrote:
> > > > Hi,
> > > > For Xen upstream master branch with commit 1949868d, After
> > > > updating qemu-
> > > xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will fail.
> 
> .. It was not clear to me - but did you do a git bisection?

Not yet. Let me have a chance to build a environment, since the issue is there for a long time.

Thanks,
-Xudong


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-03-28 13:21     ` Konrad Rzeszutek Wilk
  2016-03-29  1:44       ` Hao, Xudong
@ 2016-03-29 16:58       ` Wei Liu
  2016-03-30  2:05         ` Hao, Xudong
  1 sibling, 1 reply; 15+ messages in thread
From: Wei Liu @ 2016-03-29 16:58 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk
  Cc: wei.liu2, xen-devel, stefano.stabellini, Hao, Xudong, samuel.thibault

On Mon, Mar 28, 2016 at 09:21:14AM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Mar 28, 2016 at 02:03:35AM +0000, Hao, Xudong wrote:
> > > -----Original Message-----
> > > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Konrad
> > > Rzeszutek Wilk
> > > Sent: Saturday, March 26, 2016 2:58 AM
> > > To: Hao, Xudong <xudong.hao@intel.com>
> > > Cc: stefano.stabellini@eu.citrix.com; xen-devel@lists.xen.org
> > > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> > > 
> > > On Wed, Mar 02, 2016 at 07:16:40AM +0000, Hao, Xudong wrote:
> > > > Hi,
> > > > For Xen upstream master branch with commit 1949868d, After updating qemu-
> > > xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will fail.
> 

pv-grub should be using qemu-traditional, not qemu-xen

The log message you posted in your original post doesn't seem to reveal
much.  Can you have a look at relevant QEMU logs under /var/log/xen?


> .. It was not clear to me - but did you do a git bisection?
> 
> > > > Attach the guest config file and Xen log.
> > > 
> > > Is this still an issue? I saw an MiniOS patch go by..
> > 
> > Which patch of miniOS? 
> > 
> > This issue still exist on Xen commit a6f2cdb6. I didn't see update in Confit.mk, the minios revision is still: 
> > MINIOS_UPSTREAM_REVISION ?= 89268f00b0b0215057cb74edd94e866536a02489
> 

That's the latest patch in mini-os tree. What else do you expect?

Wei.

> Cc-ing Wei.
> > 
> > > >
> > > >
> > > > Best Regards,
> > > > Xudong
> > > >
> > > 
> > > > (XEN) Bad console= option '115200'
> > > > (XEN) Bad console= option '8n1'
> > > 
> > > Also your options are incorrect.
> > 
> > It's serial console, what's the error?
> 
> 'Bad console= option' - as you can see above.
> > 
> > Thanks,
> > -Xudong
> > 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-03-29 16:58       ` Wei Liu
@ 2016-03-30  2:05         ` Hao, Xudong
  2016-04-01 15:54           ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 15+ messages in thread
From: Hao, Xudong @ 2016-03-30  2:05 UTC (permalink / raw)
  To: Wei Liu, Konrad Rzeszutek Wilk
  Cc: samuel.thibault, xen-devel, stefano.stabellini

> -----Original Message-----
> From: Wei Liu [mailto:wei.liu2@citrix.com]
> Sent: Wednesday, March 30, 2016 12:58 AM
> To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: Hao, Xudong <xudong.hao@intel.com>; wei.liu2@citrix.com;
> samuel.thibault@ens-lyon.org; stefano.stabellini@eu.citrix.com; xen-
> devel@lists.xen.org
> Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> 
> On Mon, Mar 28, 2016 at 09:21:14AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Mon, Mar 28, 2016 at 02:03:35AM +0000, Hao, Xudong wrote:
> > > > -----Original Message-----
> > > > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf
> > > > Of Konrad Rzeszutek Wilk
> > > > Sent: Saturday, March 26, 2016 2:58 AM
> > > > To: Hao, Xudong <xudong.hao@intel.com>
> > > > Cc: stefano.stabellini@eu.citrix.com; xen-devel@lists.xen.org
> > > > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent
> > > > qemu-xen
> > > >
> > > > On Wed, Mar 02, 2016 at 07:16:40AM +0000, Hao, Xudong wrote:
> > > > > Hi,
> > > > > For Xen upstream master branch with commit 1949868d, After
> > > > > updating qemu-
> > > > xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will fail.
> >
> 
> pv-grub should be using qemu-traditional, not qemu-xen
> 

Never hear this limitation.

> The log message you posted in your original post doesn't seem to reveal much.
> Can you have a look at relevant QEMU logs under /var/log/xen?

There is not valuable qemu log, only one line: "qemu: terminating on signal 1 from pid 36642".

Bisect and the bad commit of qemu-xen is:

commit 2ce1d30ef2858dfed72a281872579e5a26b090dd
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date:   Wed Jan 6 16:32:22 2016 +0000

    xenfb.c: avoid expensive loops when prod <= out_cons

    If the frontend sets out_cons to a value higher than out_prod, it will
    cause xenfb_handle_events to loop about 2^32 times. Avoid that by using
    better checks at the beginning of the function.

    upstream-commit-id: ac0487e1d2ae811cd4d035741a109a4ecfb013f1

    Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
    Reported-by: Ling Liu <liuling-it@360.cn>

diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c
index 4e2a27a..8eb3046 100644
--- a/hw/display/xenfb.c
+++ b/hw/display/xenfb.c
@@ -789,8 +789,9 @@ static void xenfb_handle_events(struct XenFB *xenfb)

     prod = page->out_prod;
     out_cons = page->out_cons;
-    if (prod == out_cons)
-       return;
+    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
+        return;
+    }
     xen_rmb();         /* ensure we see ring contents up to prod */
     for (cons = out_cons; cons != prod; cons++) {
        union xenfb_out_event *event = &XENFB_OUT_RING_REF(page, cons);


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-03-30  2:05         ` Hao, Xudong
@ 2016-04-01 15:54           ` Konrad Rzeszutek Wilk
  2016-04-05  1:26             ` Hao, Xudong
  0 siblings, 1 reply; 15+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-04-01 15:54 UTC (permalink / raw)
  To: Hao, Xudong; +Cc: samuel.thibault, xen-devel, Wei Liu, stefano.stabellini

On Wed, Mar 30, 2016 at 02:05:28AM +0000, Hao, Xudong wrote:
> > -----Original Message-----
> > From: Wei Liu [mailto:wei.liu2@citrix.com]
> > Sent: Wednesday, March 30, 2016 12:58 AM
> > To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > Cc: Hao, Xudong <xudong.hao@intel.com>; wei.liu2@citrix.com;
> > samuel.thibault@ens-lyon.org; stefano.stabellini@eu.citrix.com; xen-
> > devel@lists.xen.org
> > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> > 
> > On Mon, Mar 28, 2016 at 09:21:14AM -0400, Konrad Rzeszutek Wilk wrote:
> > > On Mon, Mar 28, 2016 at 02:03:35AM +0000, Hao, Xudong wrote:
> > > > > -----Original Message-----
> > > > > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf
> > > > > Of Konrad Rzeszutek Wilk
> > > > > Sent: Saturday, March 26, 2016 2:58 AM
> > > > > To: Hao, Xudong <xudong.hao@intel.com>
> > > > > Cc: stefano.stabellini@eu.citrix.com; xen-devel@lists.xen.org
> > > > > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent
> > > > > qemu-xen
> > > > >
> > > > > On Wed, Mar 02, 2016 at 07:16:40AM +0000, Hao, Xudong wrote:
> > > > > > Hi,
> > > > > > For Xen upstream master branch with commit 1949868d, After
> > > > > > updating qemu-
> > > > > xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will fail.
> > >
> > 
> > pv-grub should be using qemu-traditional, not qemu-xen
> > 
> 
> Never hear this limitation.
> 
> > The log message you posted in your original post doesn't seem to reveal much.
> > Can you have a look at relevant QEMU logs under /var/log/xen?
> 
> There is not valuable qemu log, only one line: "qemu: terminating on signal 1 from pid 36642".
> 
> Bisect and the bad commit of qemu-xen is:

If you use PV-grub without the framebuffer does it boot?


> 
> commit 2ce1d30ef2858dfed72a281872579e5a26b090dd
> Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Date:   Wed Jan 6 16:32:22 2016 +0000
> 
>     xenfb.c: avoid expensive loops when prod <= out_cons
> 
>     If the frontend sets out_cons to a value higher than out_prod, it will
>     cause xenfb_handle_events to loop about 2^32 times. Avoid that by using
>     better checks at the beginning of the function.
> 
>     upstream-commit-id: ac0487e1d2ae811cd4d035741a109a4ecfb013f1
> 
>     Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>     Reported-by: Ling Liu <liuling-it@360.cn>
> 
> diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c
> index 4e2a27a..8eb3046 100644
> --- a/hw/display/xenfb.c
> +++ b/hw/display/xenfb.c
> @@ -789,8 +789,9 @@ static void xenfb_handle_events(struct XenFB *xenfb)
> 
>      prod = page->out_prod;
>      out_cons = page->out_cons;
> -    if (prod == out_cons)
> -       return;
> +    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
> +        return;
> +    }
>      xen_rmb();         /* ensure we see ring contents up to prod */
>      for (cons = out_cons; cons != prod; cons++) {
>         union xenfb_out_event *event = &XENFB_OUT_RING_REF(page, cons);
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-04-01 15:54           ` Konrad Rzeszutek Wilk
@ 2016-04-05  1:26             ` Hao, Xudong
  2016-04-05 15:41               ` Wei Liu
  0 siblings, 1 reply; 15+ messages in thread
From: Hao, Xudong @ 2016-04-05  1:26 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk
  Cc: samuel.thibault, stefano.stabellini, Wei Liu, xen-devel

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Konrad
> Rzeszutek Wilk
> Sent: Friday, April 1, 2016 11:55 PM
> To: Hao, Xudong <xudong.hao@intel.com>
> Cc: samuel.thibault@ens-lyon.org; xen-devel@lists.xen.org; Wei Liu
> <wei.liu2@citrix.com>; stefano.stabellini@eu.citrix.com
> Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> 
> On Wed, Mar 30, 2016 at 02:05:28AM +0000, Hao, Xudong wrote:
> > > -----Original Message-----
> > > From: Wei Liu [mailto:wei.liu2@citrix.com]
> > > Sent: Wednesday, March 30, 2016 12:58 AM
> > > To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > > Cc: Hao, Xudong <xudong.hao@intel.com>; wei.liu2@citrix.com;
> > > samuel.thibault@ens-lyon.org; stefano.stabellini@eu.citrix.com; xen-
> > > devel@lists.xen.org
> > > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent
> > > qemu-xen
> > >
> > > On Mon, Mar 28, 2016 at 09:21:14AM -0400, Konrad Rzeszutek Wilk wrote:
> > > > On Mon, Mar 28, 2016 at 02:03:35AM +0000, Hao, Xudong wrote:
> > > > > > -----Original Message-----
> > > > > > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On
> > > > > > Behalf Of Konrad Rzeszutek Wilk
> > > > > > Sent: Saturday, March 26, 2016 2:58 AM
> > > > > > To: Hao, Xudong <xudong.hao@intel.com>
> > > > > > Cc: stefano.stabellini@eu.citrix.com; xen-devel@lists.xen.org
> > > > > > Subject: Re: [Xen-devel] pv-grub guest booting fail with
> > > > > > recent qemu-xen
> > > > > >
> > > > > > On Wed, Mar 02, 2016 at 07:16:40AM +0000, Hao, Xudong wrote:
> > > > > > > Hi,
> > > > > > > For Xen upstream master branch with commit 1949868d, After
> > > > > > > updating qemu-
> > > > > > xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will
> fail.
> > > >
> > >
> > > pv-grub should be using qemu-traditional, not qemu-xen
> > >
> >
> > Never hear this limitation.
> >
> > > The log message you posted in your original post doesn't seem to reveal
> much.
> > > Can you have a look at relevant QEMU logs under /var/log/xen?
> >
> > There is not valuable qemu log, only one line: "qemu: terminating on signal 1
> from pid 36642".
> >
> > Bisect and the bad commit of qemu-xen is:
> 
> If you use PV-grub without the framebuffer does it boot?

How to disable framebuffer when VM booting.
Reverted this patch, PV-grub guest boot successfully.

> 
> 
> >
> > commit 2ce1d30ef2858dfed72a281872579e5a26b090dd
> > Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > Date:   Wed Jan 6 16:32:22 2016 +0000
> >
> >     xenfb.c: avoid expensive loops when prod <= out_cons
> >
> >     If the frontend sets out_cons to a value higher than out_prod, it will
> >     cause xenfb_handle_events to loop about 2^32 times. Avoid that by using
> >     better checks at the beginning of the function.
> >
> >     upstream-commit-id: ac0487e1d2ae811cd4d035741a109a4ecfb013f1
> >
> >     Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> >     Reported-by: Ling Liu <liuling-it@360.cn>
> >
> > diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c index
> > 4e2a27a..8eb3046 100644
> > --- a/hw/display/xenfb.c
> > +++ b/hw/display/xenfb.c
> > @@ -789,8 +789,9 @@ static void xenfb_handle_events(struct XenFB
> > *xenfb)
> >
> >      prod = page->out_prod;
> >      out_cons = page->out_cons;
> > -    if (prod == out_cons)
> > -       return;
> > +    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
> > +        return;
> > +    }
> >      xen_rmb();         /* ensure we see ring contents up to prod */
> >      for (cons = out_cons; cons != prod; cons++) {
> >         union xenfb_out_event *event = &XENFB_OUT_RING_REF(page,
> > cons);
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-04-05  1:26             ` Hao, Xudong
@ 2016-04-05 15:41               ` Wei Liu
  2016-04-10 20:14                 ` Samuel Thibault
  0 siblings, 1 reply; 15+ messages in thread
From: Wei Liu @ 2016-04-05 15:41 UTC (permalink / raw)
  To: Hao, Xudong
  Cc: Wei Liu, stefano.stabellini, xen-devel, Anthony PERARD, samuel.thibault

On Tue, Apr 05, 2016 at 01:26:47AM +0000, Hao, Xudong wrote:
> > -----Original Message-----
> > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Konrad
> > Rzeszutek Wilk
> > Sent: Friday, April 1, 2016 11:55 PM
> > To: Hao, Xudong <xudong.hao@intel.com>
> > Cc: samuel.thibault@ens-lyon.org; xen-devel@lists.xen.org; Wei Liu
> > <wei.liu2@citrix.com>; stefano.stabellini@eu.citrix.com
> > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> > 
> > On Wed, Mar 30, 2016 at 02:05:28AM +0000, Hao, Xudong wrote:
> > > > -----Original Message-----
> > > > From: Wei Liu [mailto:wei.liu2@citrix.com]
> > > > Sent: Wednesday, March 30, 2016 12:58 AM
> > > > To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > > > Cc: Hao, Xudong <xudong.hao@intel.com>; wei.liu2@citrix.com;
> > > > samuel.thibault@ens-lyon.org; stefano.stabellini@eu.citrix.com; xen-
> > > > devel@lists.xen.org
> > > > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent
> > > > qemu-xen
> > > >
> > > > On Mon, Mar 28, 2016 at 09:21:14AM -0400, Konrad Rzeszutek Wilk wrote:
> > > > > On Mon, Mar 28, 2016 at 02:03:35AM +0000, Hao, Xudong wrote:
> > > > > > > -----Original Message-----
> > > > > > > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On
> > > > > > > Behalf Of Konrad Rzeszutek Wilk
> > > > > > > Sent: Saturday, March 26, 2016 2:58 AM
> > > > > > > To: Hao, Xudong <xudong.hao@intel.com>
> > > > > > > Cc: stefano.stabellini@eu.citrix.com; xen-devel@lists.xen.org
> > > > > > > Subject: Re: [Xen-devel] pv-grub guest booting fail with
> > > > > > > recent qemu-xen
> > > > > > >
> > > > > > > On Wed, Mar 02, 2016 at 07:16:40AM +0000, Hao, Xudong wrote:
> > > > > > > > Hi,
> > > > > > > > For Xen upstream master branch with commit 1949868d, After
> > > > > > > > updating qemu-
> > > > > > > xen version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will
> > fail.
> > > > >
> > > >
> > > > pv-grub should be using qemu-traditional, not qemu-xen
> > > >
> > >
> > > Never hear this limitation.
> > >
> > > > The log message you posted in your original post doesn't seem to reveal
> > much.
> > > > Can you have a look at relevant QEMU logs under /var/log/xen?
> > >
> > > There is not valuable qemu log, only one line: "qemu: terminating on signal 1
> > from pid 36642".
> > >
> > > Bisect and the bad commit of qemu-xen is:
> > 
> > If you use PV-grub without the framebuffer does it boot?
> 
> How to disable framebuffer when VM booting.
> Reverted this patch, PV-grub guest boot successfully.
> 

It could be the frontend that's buggy. I think mini-os's fbfront might
aggressively overwrites prod without checking if there is space
available.

We should probably fix mini-os. On the other hand, can this check in
QEMU be improved a bit so that it accommodate buggy frontend? Anthony?

Wei.


> > 
> > 
> > >
> > > commit 2ce1d30ef2858dfed72a281872579e5a26b090dd
> > > Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > > Date:   Wed Jan 6 16:32:22 2016 +0000
> > >
> > >     xenfb.c: avoid expensive loops when prod <= out_cons
> > >
> > >     If the frontend sets out_cons to a value higher than out_prod, it will
> > >     cause xenfb_handle_events to loop about 2^32 times. Avoid that by using
> > >     better checks at the beginning of the function.
> > >
> > >     upstream-commit-id: ac0487e1d2ae811cd4d035741a109a4ecfb013f1
> > >
> > >     Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > >     Reported-by: Ling Liu <liuling-it@360.cn>
> > >
> > > diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c index
> > > 4e2a27a..8eb3046 100644
> > > --- a/hw/display/xenfb.c
> > > +++ b/hw/display/xenfb.c
> > > @@ -789,8 +789,9 @@ static void xenfb_handle_events(struct XenFB
> > > *xenfb)
> > >
> > >      prod = page->out_prod;
> > >      out_cons = page->out_cons;
> > > -    if (prod == out_cons)
> > > -       return;
> > > +    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
> > > +        return;
> > > +    }
> > >      xen_rmb();         /* ensure we see ring contents up to prod */
> > >      for (cons = out_cons; cons != prod; cons++) {
> > >         union xenfb_out_event *event = &XENFB_OUT_RING_REF(page,
> > > cons);
> > >
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-04-05 15:41               ` Wei Liu
@ 2016-04-10 20:14                 ` Samuel Thibault
  2016-04-11 10:54                   ` Wei Liu
  0 siblings, 1 reply; 15+ messages in thread
From: Samuel Thibault @ 2016-04-10 20:14 UTC (permalink / raw)
  To: Wei Liu; +Cc: Anthony PERARD, xen-devel, Hao, Xudong, stefano.stabellini

Hello,

> > > > +    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
> > > > +        return;
> > > > +    }

This test seems overzealous to me: AIUI, the producer can produce
XENFB_OUT_RING_LEN events, and thus prod - out_cons is exactly
XENFB_OUT_RING_LEN, i.e. there is no room left at all.

The frontend part is:

   while (page->out_prod - page->out_cons == XENFB_OUT_RING_LEN)
        schedule();

I.e. it waits while the buffer is exactly full.

So it seems to me the bug is at the backend side.

Samuel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-04-10 20:14                 ` Samuel Thibault
@ 2016-04-11 10:54                   ` Wei Liu
  2016-04-11 11:52                     ` Wei Liu
  2016-04-12  1:56                     ` Hao, Xudong
  0 siblings, 2 replies; 15+ messages in thread
From: Wei Liu @ 2016-04-11 10:54 UTC (permalink / raw)
  To: Samuel Thibault, Wei Liu, Hao, Xudong, Konrad Rzeszutek Wilk,
	xen-devel, stefano.stabellini, Anthony PERARD

On Sun, Apr 10, 2016 at 10:14:46PM +0200, Samuel Thibault wrote:
> Hello,
> 
> > > > > +    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
> > > > > +        return;
> > > > > +    }
> 
> This test seems overzealous to me: AIUI, the producer can produce
> XENFB_OUT_RING_LEN events, and thus prod - out_cons is exactly
> XENFB_OUT_RING_LEN, i.e. there is no room left at all.
> 
> The frontend part is:
> 
>    while (page->out_prod - page->out_cons == XENFB_OUT_RING_LEN)
>         schedule();
> 
> I.e. it waits while the buffer is exactly full.
> 
> So it seems to me the bug is at the backend side.
> 

OK, thanks for checking!

Hudong, can you try the following diff?

diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c
index 8eb3046..284b345 100644
--- a/hw/display/xenfb.c
+++ b/hw/display/xenfb.c
@@ -789,7 +789,7 @@ static void xenfb_handle_events(struct XenFB *xenfb)

     prod = page->out_prod;
     out_cons = page->out_cons;
-    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
+    if (prod - out_cons > XENFB_OUT_RING_LEN) {
         return;
     }
     xen_rmb();         /* ensure we see ring contents up to prod */

> Samuel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-04-11 10:54                   ` Wei Liu
@ 2016-04-11 11:52                     ` Wei Liu
  2016-04-12  1:56                     ` Hao, Xudong
  1 sibling, 0 replies; 15+ messages in thread
From: Wei Liu @ 2016-04-11 11:52 UTC (permalink / raw)
  To: Samuel Thibault, Wei Liu, Hao, Xudong, Konrad Rzeszutek Wilk,
	xen-devel, stefano.stabellini, Anthony PERARD

On Mon, Apr 11, 2016 at 11:54:06AM +0100, Wei Liu wrote:
> On Sun, Apr 10, 2016 at 10:14:46PM +0200, Samuel Thibault wrote:
> > Hello,
> > 
> > > > > > +    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
> > > > > > +        return;
> > > > > > +    }
> > 
> > This test seems overzealous to me: AIUI, the producer can produce
> > XENFB_OUT_RING_LEN events, and thus prod - out_cons is exactly
> > XENFB_OUT_RING_LEN, i.e. there is no room left at all.
> > 
> > The frontend part is:
> > 
> >    while (page->out_prod - page->out_cons == XENFB_OUT_RING_LEN)
> >         schedule();
> > 
> > I.e. it waits while the buffer is exactly full.
> > 
> > So it seems to me the bug is at the backend side.
> > 
> 
> OK, thanks for checking!
> 
> Hudong, can you try the following diff?
  ^ Xudong

Sorry for the typo...

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-04-11 10:54                   ` Wei Liu
  2016-04-11 11:52                     ` Wei Liu
@ 2016-04-12  1:56                     ` Hao, Xudong
  2016-04-12  8:28                       ` Wei Liu
  1 sibling, 1 reply; 15+ messages in thread
From: Hao, Xudong @ 2016-04-12  1:56 UTC (permalink / raw)
  To: Wei Liu, Samuel Thibault, Konrad Rzeszutek Wilk, xen-devel,
	stefano.stabellini, Anthony PERARD

> -----Original Message-----
> From: Wei Liu [mailto:wei.liu2@citrix.com]
> Sent: Monday, April 11, 2016 6:54 PM
> To: Samuel Thibault <samuel.thibault@ens-lyon.org>; Wei Liu
> <wei.liu2@citrix.com>; Hao, Xudong <xudong.hao@intel.com>; Konrad
> Rzeszutek Wilk <konrad.wilk@oracle.com>; xen-devel@lists.xen.org;
> stefano.stabellini@eu.citrix.com; Anthony PERARD <anthony.perard@citrix.com>
> Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> 
> On Sun, Apr 10, 2016 at 10:14:46PM +0200, Samuel Thibault wrote:
> > Hello,
> >
> > > > > > +    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
> > > > > > +        return;
> > > > > > +    }
> >
> > This test seems overzealous to me: AIUI, the producer can produce
> > XENFB_OUT_RING_LEN events, and thus prod - out_cons is exactly
> > XENFB_OUT_RING_LEN, i.e. there is no room left at all.
> >
> > The frontend part is:
> >
> >    while (page->out_prod - page->out_cons == XENFB_OUT_RING_LEN)
> >         schedule();
> >
> > I.e. it waits while the buffer is exactly full.
> >
> > So it seems to me the bug is at the backend side.
> >
> 
> OK, thanks for checking!
> 
> Hudong, can you try the following diff?

Yes, This patch works with testing. 

Thanks,
-Xudong

> 
> diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c index 8eb3046..284b345
> 100644
> --- a/hw/display/xenfb.c
> +++ b/hw/display/xenfb.c
> @@ -789,7 +789,7 @@ static void xenfb_handle_events(struct XenFB *xenfb)
> 
>      prod = page->out_prod;
>      out_cons = page->out_cons;
> -    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
> +    if (prod - out_cons > XENFB_OUT_RING_LEN) {
>          return;
>      }
>      xen_rmb();         /* ensure we see ring contents up to prod */
> 
> > Samuel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: pv-grub guest booting fail with recent qemu-xen
  2016-04-12  1:56                     ` Hao, Xudong
@ 2016-04-12  8:28                       ` Wei Liu
  0 siblings, 0 replies; 15+ messages in thread
From: Wei Liu @ 2016-04-12  8:28 UTC (permalink / raw)
  To: Hao, Xudong
  Cc: Wei Liu, stefano.stabellini, xen-devel, Anthony PERARD, Samuel Thibault

On Tue, Apr 12, 2016 at 01:56:50AM +0000, Hao, Xudong wrote:
> > -----Original Message-----
> > From: Wei Liu [mailto:wei.liu2@citrix.com]
> > Sent: Monday, April 11, 2016 6:54 PM
> > To: Samuel Thibault <samuel.thibault@ens-lyon.org>; Wei Liu
> > <wei.liu2@citrix.com>; Hao, Xudong <xudong.hao@intel.com>; Konrad
> > Rzeszutek Wilk <konrad.wilk@oracle.com>; xen-devel@lists.xen.org;
> > stefano.stabellini@eu.citrix.com; Anthony PERARD <anthony.perard@citrix.com>
> > Subject: Re: [Xen-devel] pv-grub guest booting fail with recent qemu-xen
> > 
> > On Sun, Apr 10, 2016 at 10:14:46PM +0200, Samuel Thibault wrote:
> > > Hello,
> > >
> > > > > > > +    if (prod - out_cons >= XENFB_OUT_RING_LEN) {
> > > > > > > +        return;
> > > > > > > +    }
> > >
> > > This test seems overzealous to me: AIUI, the producer can produce
> > > XENFB_OUT_RING_LEN events, and thus prod - out_cons is exactly
> > > XENFB_OUT_RING_LEN, i.e. there is no room left at all.
> > >
> > > The frontend part is:
> > >
> > >    while (page->out_prod - page->out_cons == XENFB_OUT_RING_LEN)
> > >         schedule();
> > >
> > > I.e. it waits while the buffer is exactly full.
> > >
> > > So it seems to me the bug is at the backend side.
> > >
> > 
> > OK, thanks for checking!
> > 
> > Hudong, can you try the following diff?
> 
> Yes, This patch works with testing. 
> 

Thanks for testing!

I will submit this patch properly.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2016-04-12  8:28 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-02  7:16 pv-grub guest booting fail with recent qemu-xen Hao, Xudong
2016-03-25 18:57 ` Konrad Rzeszutek Wilk
2016-03-28  2:03   ` Hao, Xudong
2016-03-28 13:21     ` Konrad Rzeszutek Wilk
2016-03-29  1:44       ` Hao, Xudong
2016-03-29 16:58       ` Wei Liu
2016-03-30  2:05         ` Hao, Xudong
2016-04-01 15:54           ` Konrad Rzeszutek Wilk
2016-04-05  1:26             ` Hao, Xudong
2016-04-05 15:41               ` Wei Liu
2016-04-10 20:14                 ` Samuel Thibault
2016-04-11 10:54                   ` Wei Liu
2016-04-11 11:52                     ` Wei Liu
2016-04-12  1:56                     ` Hao, Xudong
2016-04-12  8:28                       ` Wei Liu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).