All of lore.kernel.org
 help / color / mirror / Atom feed
* dom0 not seeing all of the assigned memory
@ 2012-02-22 22:19 Henrik Olsson
  2012-02-22 22:40 ` Henrik Olsson
  2012-02-23 18:55 ` David Vrabel
  0 siblings, 2 replies; 19+ messages in thread
From: Henrik Olsson @ 2012-02-22 22:19 UTC (permalink / raw)
  To: xen-devel

[-- Attachment #1: Type: text/plain, Size: 309 bytes --]

Hi, i'm having some trouble with assigning memory to my dom0.

I've added "dom0_mem=8192M" to the xen command line yet "free -m"
reports only 5686MB total.

Running Xen 4.1.2 with kernel 3.2.0-1-amd64, debian testing.

Attached are the outputs of dmesg, xm dmesg, xm info and xm list.

Regards,
Henrik Olsson

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

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.2.0-1-amd64 (Debian 3.2.4-1) (waldi@debian.org) (gcc version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Sun Feb 5 15:17:15 UTC 2012
[    0.000000] Command line: placeholder root=/dev/mapper/muaddib-root ro rdblacklist=radeon radeon.modset=0 mem=8192M
[    0.000000] Freeing  9d-100 pfn range: 99 pages freed
[    0.000000] 1-1 mapping on 9d->100
[    0.000000] Freeing  20000-20200 pfn range: 512 pages freed
[    0.000000] 1-1 mapping on 20000->20200
[    0.000000] Freeing  40000-40200 pfn range: 512 pages freed
[    0.000000] 1-1 mapping on 40000->40200
[    0.000000] Freeing  6ed6d-6edf2 pfn range: 133 pages freed
[    0.000000] 1-1 mapping on 6ed6d->6edf2
[    0.000000] Freeing  6edf3-6ee7b pfn range: 136 pages freed
[    0.000000] 1-1 mapping on 6edf3->6ee7b
[    0.000000] Freeing  6f000-100000 pfn range: 593920 pages freed
[    0.000000] 1-1 mapping on 6f000->100000
[    0.000000] Released 595312 pages of unused memory
[    0.000000] Set 595312 page(s) to 1-1 mapping
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 000000000009d000 (usable)
[    0.000000]  Xen: 000000000009d800 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 0000000020000000 (usable)
[    0.000000]  Xen: 0000000020000000 - 0000000020200000 (reserved)
[    0.000000]  Xen: 0000000020200000 - 0000000040000000 (usable)
[    0.000000]  Xen: 0000000040000000 - 0000000040200000 (reserved)
[    0.000000]  Xen: 0000000040200000 - 000000006ed6d000 (usable)
[    0.000000]  Xen: 000000006ed6d000 - 000000006edbc000 (ACPI NVS)
[    0.000000]  Xen: 000000006edbc000 - 000000006edc5000 (ACPI data)
[    0.000000]  Xen: 000000006edc5000 - 000000006edf2000 (reserved)
[    0.000000]  Xen: 000000006edf2000 - 000000006edf3000 (usable)
[    0.000000]  Xen: 000000006edf3000 - 000000006ee03000 (reserved)
[    0.000000]  Xen: 000000006ee03000 - 000000006ee10000 (ACPI NVS)
[    0.000000]  Xen: 000000006ee10000 - 000000006ee38000 (reserved)
[    0.000000]  Xen: 000000006ee38000 - 000000006ee7b000 (ACPI NVS)
[    0.000000]  Xen: 000000006ee7b000 - 000000006f000000 (usable)
[    0.000000]  Xen: 000000006f800000 - 000000007fa00000 (reserved)
[    0.000000]  Xen: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  Xen: 00000000fed1c000 - 00000000fed40000 (reserved)
[    0.000000]  Xen: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  Xen: 00000000ff000000 - 0000000100000000 (reserved)
[    0.000000]  Xen: 0000000100000000 - 000000047fe00000 (usable)
[    0.000000] e820 remove range: 0000000200000000 - ffffffffffffffff (usable)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] user-defined physical RAM map:
[    0.000000]  user: 0000000000000000 - 000000000009d000 (usable)
[    0.000000]  user: 000000000009d800 - 0000000000100000 (reserved)
[    0.000000]  user: 0000000000100000 - 0000000020000000 (usable)
[    0.000000]  user: 0000000020000000 - 0000000020200000 (reserved)
[    0.000000]  user: 0000000020200000 - 0000000040000000 (usable)
[    0.000000]  user: 0000000040000000 - 0000000040200000 (reserved)
[    0.000000]  user: 0000000040200000 - 000000006ed6d000 (usable)
[    0.000000]  user: 000000006ed6d000 - 000000006edbc000 (ACPI NVS)
[    0.000000]  user: 000000006edbc000 - 000000006edc5000 (ACPI data)
[    0.000000]  user: 000000006edc5000 - 000000006edf2000 (reserved)
[    0.000000]  user: 000000006edf2000 - 000000006edf3000 (usable)
[    0.000000]  user: 000000006edf3000 - 000000006ee03000 (reserved)
[    0.000000]  user: 000000006ee03000 - 000000006ee10000 (ACPI NVS)
[    0.000000]  user: 000000006ee10000 - 000000006ee38000 (reserved)
[    0.000000]  user: 000000006ee38000 - 000000006ee7b000 (ACPI NVS)
[    0.000000]  user: 000000006ee7b000 - 000000006f000000 (usable)
[    0.000000]  user: 000000006f800000 - 000000007fa00000 (reserved)
[    0.000000]  user: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  user: 00000000fed1c000 - 00000000fed40000 (reserved)
[    0.000000]  user: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  user: 00000000ff000000 - 0000000100000000 (reserved)
[    0.000000]  user: 0000000100000000 - 0000000200000000 (usable)
[    0.000000] DMI 2.7 present.
[    0.000000] DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z68 Extreme4 Gen3, BIOS P1.00 07/08/2011
[    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[    0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[    0.000000] No AGP bridge found
[    0.000000] last_pfn = 0x200000 max_arch_pfn = 0x400000000
[    0.000000] x2apic enabled by BIOS, switching to x2apic ops
[    0.000000] last_pfn = 0x6f000 max_arch_pfn = 0x400000000
[    0.000000] found SMP MP-table at [ffff8800000fd230] fd230
[    0.000000] initial memory mapped : 0 - 03a2c000
[    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 20480
[    0.000000] init_memory_mapping: 0000000000000000-000000006f000000
[    0.000000]  0000000000 - 006f000000 page 4k
[    0.000000] kernel direct mapping tables up to 6f000000 @ c85000-1000000
[    0.000000] xen: setting RW the range fd4000 - 1000000
[    0.000000] init_memory_mapping: 0000000100000000-0000000200000000
[    0.000000]  0100000000 - 0200000000 page 4k
[    0.000000] kernel direct mapping tables up to 200000000 @ 6dd64000-6ed6d000
[    0.000000] xen: setting RW the range 6e568000 - 6ed6d000
[    0.000000] RAMDISK: 0193a000 - 03a2c000
[    0.000000] ACPI: RSDP 00000000000f0450 00024 (v02 ALASKA)
[    0.000000] ACPI: XSDT 000000006edbc070 0005C (v01 ALASKA    A M I 01072009 AMI  00010013)
[    0.000000] ACPI: FACP 000000006edc4158 000F4 (v04 ALASKA    A M I 01072009 AMI  00010013)
[    0.000000] ACPI: DSDT 000000006edbc158 07FFB (v02 ALASKA    A M I 00000000 INTL 20051117)
[    0.000000] ACPI: FACS 000000006ee07f80 00040
[    0.000000] ACPI: APIC 000000006edc4250 00092 (v03 ALASKA    A M I 01072009 AMI  00010013)
[    0.000000] ACPI: SSDT 000000006edc42e8 001D6 (v01 AMICPU     PROC 00000001 MSFT 03000001)
[    0.000000] ACPI: MCFG 000000006edc44c0 0003C (v01 ALASKA    A M I 01072009 MSFT 00000097)
[    0.000000] ACPI: AAFT 000000006edc4500 000D3 (v01 ALASKA OEMAAFT  01072009 MSFT 00000097)
[    0.000000] ACPI: HPET 000000006edc45d8 00038 (v01 ALASKA    A M I 01072009 AMI. 00000004)
[    0.000000] ACPI: XMAR 000000006edc4610 000E8 (v01 ALASKA    A M I 00000001 INTL 00000001)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] Setting APIC routing to cluster x2apic.
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at 0000000000000000-0000000200000000
[    0.000000] Initmem setup node 0 0000000000000000-0000000200000000
[    0.000000]   NODE_DATA [00000001ffffb000 - 00000001ffffffff]
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   DMA32    0x00001000 -> 0x00100000
[    0.000000]   Normal   0x00100000 -> 0x00200000
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[7] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x0000009d
[    0.000000]     0: 0x00000100 -> 0x00020000
[    0.000000]     0: 0x00020200 -> 0x00040000
[    0.000000]     0: 0x00040200 -> 0x0006ed6d
[    0.000000]     0: 0x0006edf2 -> 0x0006edf3
[    0.000000]     0: 0x0006ee7b -> 0x0006f000
[    0.000000]     0: 0x00100000 -> 0x00200000
[    0.000000] On node 0 totalpages: 1501824
[    0.000000]   DMA zone: 56 pages used for memmap
[    0.000000]   DMA zone: 852 pages reserved
[    0.000000]   DMA zone: 3073 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 14280 pages used for memmap
[    0.000000]   DMA32 zone: 434987 pages, LIFO batch:31
[    0.000000]   Normal zone: 14336 pages used for memmap
[    0.000000]   Normal zone: 1034240 pages, LIFO batch:31
[    0.000000] ACPI: PM-Timer IO Port: 0x408
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 0, version 255, address 0xfec00000, GSI 0-255
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[    0.000000] SMP: Allowing 8 CPUs, 0 hotplug CPUs
[    0.000000] nr_irqs_gsi: 272
[    0.000000] PM: Registered nosave memory: 000000000009d000 - 000000000009e000
[    0.000000] PM: Registered nosave memory: 000000000009e000 - 0000000000100000
[    0.000000] PM: Registered nosave memory: 0000000020000000 - 0000000020200000
[    0.000000] PM: Registered nosave memory: 0000000040000000 - 0000000040200000
[    0.000000] PM: Registered nosave memory: 000000006ed6d000 - 000000006edbc000
[    0.000000] PM: Registered nosave memory: 000000006edbc000 - 000000006edc5000
[    0.000000] PM: Registered nosave memory: 000000006edc5000 - 000000006edf2000
[    0.000000] PM: Registered nosave memory: 000000006edf3000 - 000000006ee03000
[    0.000000] PM: Registered nosave memory: 000000006ee03000 - 000000006ee10000
[    0.000000] PM: Registered nosave memory: 000000006ee10000 - 000000006ee38000
[    0.000000] PM: Registered nosave memory: 000000006ee38000 - 000000006ee7b000
[    0.000000] PM: Registered nosave memory: 000000006f000000 - 000000006f800000
[    0.000000] PM: Registered nosave memory: 000000006f800000 - 000000007fa00000
[    0.000000] PM: Registered nosave memory: 000000007fa00000 - 00000000fec00000
[    0.000000] PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000
[    0.000000] PM: Registered nosave memory: 00000000fec01000 - 00000000fed1c000
[    0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed40000
[    0.000000] PM: Registered nosave memory: 00000000fed40000 - 00000000fee00000
[    0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000
[    0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ff000000
[    0.000000] PM: Registered nosave memory: 00000000ff000000 - 0000000100000000
[    0.000000] Allocating PCI resources starting at 7fa00000 (gap: 7fa00000:7f200000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 4.1.2 (preserve-AD)
[    0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
[    0.000000] PERCPU: Embedded 28 pages/cpu @ffff8801ffeca000 s82304 r8192 d24192 u114688
[    0.000000] pcpu-alloc: s82304 r8192 d24192 u114688 alloc=28*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 
[    4.040278] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 1472300
[    4.040279] Policy zone: Normal
[    4.040281] Kernel command line: placeholder root=/dev/mapper/muaddib-root ro rdblacklist=radeon radeon.modset=0 mem=8192M
[    4.040331] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    4.057191] Placing 64MB software IO TLB between ffff8801f5a00000 - ffff8801f9a00000
[    4.057193] software IO TLB at phys 0x1f5a00000 - 0x1f9a00000
[    4.073111] Memory: 5787228k/8388608k available (3368k kernel code, 2381312k absent, 220068k reserved, 3361k data, 568k init)
[    4.073175] Hierarchical RCU implementation.
[    4.073176] 	RCU dyntick-idle grace-period acceleration is enabled.
[    4.073183] NR_IRQS:33024 nr_irqs:2048 16
[    4.073234] xen: sci override: global_irq=9 trigger=0 polarity=0
[    4.073237] xen: registering gsi 9 triggering 0 polarity 0
[    4.073243] xen: --> pirq=9 -> irq=9 (gsi=9)
[    4.073262] xen: acpi sci 9
[    4.073264] xen: --> pirq=1 -> irq=1 (gsi=1)
[    4.073267] xen: --> pirq=2 -> irq=2 (gsi=2)
[    4.073269] xen: --> pirq=3 -> irq=3 (gsi=3)
[    4.073271] xen: --> pirq=4 -> irq=4 (gsi=4)
[    4.073274] xen: --> pirq=5 -> irq=5 (gsi=5)
[    4.073276] xen: --> pirq=6 -> irq=6 (gsi=6)
[    4.073278] xen: --> pirq=7 -> irq=7 (gsi=7)
[    4.073281] xen: --> pirq=8 -> irq=8 (gsi=8)
[    4.073282] xen_map_pirq_gsi: returning irq 9 for gsi 9
[    4.073284] xen: --> pirq=9 -> irq=9 (gsi=9)
[    4.073286] xen: --> pirq=10 -> irq=10 (gsi=10)
[    4.073288] xen: --> pirq=11 -> irq=11 (gsi=11)
[    4.073291] xen: --> pirq=12 -> irq=12 (gsi=12)
[    4.073293] xen: --> pirq=13 -> irq=13 (gsi=13)
[    4.073295] xen: --> pirq=14 -> irq=14 (gsi=14)
[    4.073298] xen: --> pirq=15 -> irq=15 (gsi=15)
[    4.075061] Console: colour VGA+ 80x25
[    4.079807] console [tty0] enabled
[    4.079858] Xen: using vcpuop timer interface
[    4.079861] installing Xen timer for CPU 0
[    4.079904] Detected 3392.376 MHz processor.
[    4.079938] Calibrating delay loop (skipped), value calculated using timer frequency.. 6784.75 BogoMIPS (lpj=13569504)
[    4.080001] pid_max: default: 32768 minimum: 301
[    4.080065] Security Framework initialized
[    4.080096] AppArmor: AppArmor disabled by boot time parameter
[    4.081740] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    4.083739] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    4.084379] Mount-cache hash table entries: 256
[    4.084505] Initializing cgroup subsys cpuacct
[    4.084537] Initializing cgroup subsys memory
[    4.084577] Initializing cgroup subsys devices
[    4.084607] Initializing cgroup subsys freezer
[    4.084638] Initializing cgroup subsys net_cls
[    4.084669] Initializing cgroup subsys blkio
[    4.084749] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    4.084749] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[    4.084817] CPU: Physical Processor ID: 0
[    4.084846] CPU: Processor Core ID: 0
[    4.085304] ACPI: Core revision 20110623
[    4.095208] Performance Events: unsupported p6 CPU model 42 no PMU driver, software events only.
[    4.095371] NMI watchdog disabled (cpu0): hardware events not enabled
[    4.095489] installing Xen timer for CPU 1
[    4.095626] NMI watchdog disabled (cpu1): hardware events not enabled
[    4.095678] Brought up 2 CPUs
[    4.095897] devtmpfs: initialized
[    4.098078] PM: Registering ACPI NVS region at 6ed6d000 (323584 bytes)
[    4.098128] PM: Registering ACPI NVS region at 6ee03000 (53248 bytes)
[    4.099460] PM: Registering ACPI NVS region at 6ee38000 (274432 bytes)
[    4.099578] Grant table initialized
[    4.099660] print_constraints: dummy: 
[    4.099740] NET: Registered protocol family 16
[    4.099926] ACPI: bus type pci registered
[    4.100018] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    4.100067] PCI: not using MMCONFIG
[    4.100097] PCI: Using configuration type 1 for base access
[    4.100749] bio: create slab <bio-0> at 0
[    4.100887] ACPI: Added _OSI(Module Device)
[    4.100919] ACPI: Added _OSI(Processor Device)
[    4.100950] ACPI: Added _OSI(3.0 _SCP Extensions)
[    4.100981] ACPI: Added _OSI(Processor Aggregator Device)
[    4.102708] ACPI: EC: Look up EC in DSDT
[    4.104547] ACPI: Executed 1 blocks of module-level executable AML code
[    4.111819] ACPI: SSDT 000000006ee0f898 006F4 (v01    AMI      IST 00000001 MSFT 03000001)
[    4.112518] ACPI: Dynamic OEM Table Load:
[    4.112572] ACPI: SSDT           (null) 006F4 (v01    AMI      IST 00000001 MSFT 03000001)
[    4.112708] ACPI: SSDT 000000006ee06d98 000E4 (v01    AMI      CST 00000001 MSFT 03000001)
[    4.113231] ACPI: Dynamic OEM Table Load:
[    4.113285] ACPI: SSDT           (null) 000E4 (v01    AMI      CST 00000001 MSFT 03000001)
[    4.113832] ACPI: Interpreter enabled
[    4.113863] ACPI: (supports S0 S1 S3 S4 S5)
[    4.113975] ACPI: Using IOAPIC for interrupt routing
[    4.114034] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    4.114187] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[    4.166851] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[    4.174065] ACPI: No dock devices found.
[    4.174096] HEST: Table not found.
[    4.174126] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    4.174604] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    4.175063] pci_root PNP0A08:00: host bridge window [io  0x0000-0x03af]
[    4.175098] pci_root PNP0A08:00: host bridge window [io  0x03e0-0x0cf7]
[    4.175132] pci_root PNP0A08:00: host bridge window [io  0x03b0-0x03df]
[    4.175166] pci_root PNP0A08:00: host bridge window [io  0x0d00-0xffff]
[    4.175200] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
[    4.175245] pci_root PNP0A08:00: host bridge window [mem 0x000c0000-0x000dffff]
[    4.175291] pci_root PNP0A08:00: host bridge window [mem 0x7fa00000-0xffffffff]
[    4.175351] pci 0000:00:00.0: [8086:0100] type 0 class 0x000600
[    4.175429] pci 0000:00:01.0: [8086:0101] type 1 class 0x000604
[    4.175506] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[    4.175509] pci 0000:00:01.0: PME# disabled
[    4.175548] pci 0000:00:02.0: [8086:0102] type 0 class 0x000300
[    4.175571] pci 0000:00:02.0: reg 10: [mem 0xfb400000-0xfb7fffff 64bit]
[    4.175583] pci 0000:00:02.0: reg 18: [mem 0xb0000000-0xbfffffff 64bit pref]
[    4.175592] pci 0000:00:02.0: reg 20: [io  0xf000-0xf03f]
[    4.175713] pci 0000:00:16.0: [8086:1c3a] type 0 class 0x000780
[    4.175757] pci 0000:00:16.0: reg 10: [mem 0xfbf04000-0xfbf0400f 64bit]
[    4.175908] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[    4.175913] pci 0000:00:16.0: PME# disabled
[    4.175976] pci 0000:00:1a.0: [8086:1c2d] type 0 class 0x000c03
[    4.176015] pci 0000:00:1a.0: reg 10: [mem 0xfbf03000-0xfbf033ff]
[    4.176197] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[    4.176203] pci 0000:00:1a.0: PME# disabled
[    4.176244] pci 0000:00:1c.0: [8086:1c10] type 1 class 0x000604
[    4.176409] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    4.176415] pci 0000:00:1c.0: PME# disabled
[    4.176466] pci 0000:00:1c.4: [8086:1c18] type 1 class 0x000604
[    4.176632] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[    4.176638] pci 0000:00:1c.4: PME# disabled
[    4.176685] pci 0000:00:1c.5: [8086:1c1a] type 1 class 0x000604
[    4.176849] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[    4.176855] pci 0000:00:1c.5: PME# disabled
[    4.176900] pci 0000:00:1c.6: [8086:1c1c] type 1 class 0x000604
[    4.177064] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
[    4.177070] pci 0000:00:1c.6: PME# disabled
[    4.177116] pci 0000:00:1c.7: [8086:1c1e] type 1 class 0x000604
[    4.177282] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
[    4.177288] pci 0000:00:1c.7: PME# disabled
[    4.177340] pci 0000:00:1d.0: [8086:1c26] type 0 class 0x000c03
[    4.177380] pci 0000:00:1d.0: reg 10: [mem 0xfbf02000-0xfbf023ff]
[    4.177561] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[    4.177568] pci 0000:00:1d.0: PME# disabled
[    4.177608] pci 0000:00:1f.0: [8086:1c44] type 0 class 0x000601
[    4.177840] pci 0000:00:1f.2: [8086:1c02] type 0 class 0x000106
[    4.177881] pci 0000:00:1f.2: reg 10: [io  0xf0b0-0xf0b7]
[    4.177897] pci 0000:00:1f.2: reg 14: [io  0xf0a0-0xf0a3]
[    4.177912] pci 0000:00:1f.2: reg 18: [io  0xf090-0xf097]
[    4.177928] pci 0000:00:1f.2: reg 1c: [io  0xf080-0xf083]
[    4.177943] pci 0000:00:1f.2: reg 20: [io  0xf060-0xf07f]
[    4.177959] pci 0000:00:1f.2: reg 24: [mem 0xfbf01000-0xfbf017ff]
[    4.178062] pci 0000:00:1f.2: PME# supported from D3hot
[    4.178067] pci 0000:00:1f.2: PME# disabled
[    4.178099] pci 0000:00:1f.3: [8086:1c22] type 0 class 0x000c05
[    4.178130] pci 0000:00:1f.3: reg 10: [mem 0xfbf00000-0xfbf000ff 64bit]
[    4.178175] pci 0000:00:1f.3: reg 20: [io  0xf040-0xf05f]
[    4.178292] pci 0000:01:00.0: [1002:6719] type 0 class 0x000300
[    4.178314] pci 0000:01:00.0: reg 10: [mem 0xc0000000-0xcfffffff 64bit pref]
[    4.178331] pci 0000:01:00.0: reg 18: [mem 0xfbe20000-0xfbe3ffff 64bit]
[    4.178343] pci 0000:01:00.0: reg 20: [io  0xe000-0xe0ff]
[    4.178365] pci 0000:01:00.0: reg 30: [mem 0xfbe00000-0xfbe1ffff pref]
[    4.178421] pci 0000:01:00.0: supports D1 D2
[    4.178455] pci 0000:01:00.1: [1002:aa80] type 0 class 0x000403
[    4.178476] pci 0000:01:00.1: reg 10: [mem 0xfbe40000-0xfbe43fff 64bit]
[    4.178583] pci 0000:01:00.1: supports D1 D2
[    4.185391] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[    4.185445] pci 0000:00:01.0:   bridge window [io  0xe000-0xefff]
[    4.185449] pci 0000:00:01.0:   bridge window [mem 0xfbe00000-0xfbefffff]
[    4.185455] pci 0000:00:01.0:   bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
[    4.185581] pci 0000:02:00.0: [10b5:8112] type 1 class 0x000604
[    4.185831] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'
[    4.185897] pci 0000:00:1c.0: PCI bridge to [bus 02-03]
[    4.185933] pci 0000:00:1c.0:   bridge window [io  0xd000-0xdfff]
[    4.186093] pci 0000:03:04.0: [13f6:8788] type 0 class 0x000401
[    4.186144] pci 0000:03:04.0: reg 10: [io  0xd000-0xd0ff]
[    4.186389] pci 0000:03:04.0: supports D1 D2
[    4.186506] pci 0000:02:00.0: PCI bridge to [bus 03-03]
[    4.186545] pci 0000:02:00.0:   bridge window [io  0xd000-0xdfff]
[    4.186700] pci 0000:04:00.0: [1b4b:9120] type 0 class 0x000106
[    4.186728] pci 0000:04:00.0: reg 10: [io  0xc040-0xc047]
[    4.186748] pci 0000:04:00.0: reg 14: [io  0xc030-0xc033]
[    4.186768] pci 0000:04:00.0: reg 18: [io  0xc020-0xc027]
[    4.186789] pci 0000:04:00.0: reg 1c: [io  0xc010-0xc013]
[    4.186809] pci 0000:04:00.0: reg 20: [io  0xc000-0xc00f]
[    4.186830] pci 0000:04:00.0: reg 24: [mem 0xfbd10000-0xfbd107ff]
[    4.186851] pci 0000:04:00.0: reg 30: [mem 0xfbd00000-0xfbd0ffff pref]
[    4.186950] pci 0000:04:00.0: PME# supported from D3hot
[    4.186957] pci 0000:04:00.0: PME# disabled
[    4.187024] pci 0000:00:1c.4: PCI bridge to [bus 04-04]
[    4.187060] pci 0000:00:1c.4:   bridge window [io  0xc000-0xcfff]
[    4.187066] pci 0000:00:1c.4:   bridge window [mem 0xfbd00000-0xfbdfffff]
[    4.187198] pci 0000:05:00.0: [1b6f:7023] type 0 class 0x000c03
[    4.187240] pci 0000:05:00.0: reg 10: [mem 0xfbc00000-0xfbc07fff 64bit]
[    4.187447] pci 0000:05:00.0: supports D1 D2
[    4.187449] pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    4.187456] pci 0000:05:00.0: PME# disabled
[    4.187535] pci 0000:00:1c.5: PCI bridge to [bus 05-05]
[    4.187576] pci 0000:00:1c.5:   bridge window [mem 0xfbc00000-0xfbcfffff]
[    4.187709] pci 0000:06:00.0: [1b6f:7023] type 0 class 0x000c03
[    4.187750] pci 0000:06:00.0: reg 10: [mem 0xfbb00000-0xfbb07fff 64bit]
[    4.187956] pci 0000:06:00.0: supports D1 D2
[    4.187958] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    4.187965] pci 0000:06:00.0: PME# disabled
[    4.188044] pci 0000:00:1c.6: PCI bridge to [bus 06-06]
[    4.188084] pci 0000:00:1c.6:   bridge window [mem 0xfbb00000-0xfbbfffff]
[    4.188215] pci 0000:07:00.0: [10b5:8608] type 1 class 0x000604
[    4.188243] pci 0000:07:00.0: reg 10: [mem 0xfba00000-0xfba1ffff]
[    4.188422] pci 0000:07:00.0: PME# supported from D0 D3hot D3cold
[    4.188429] pci 0000:07:00.0: PME# disabled
[    4.188529] pci 0000:00:1c.7: PCI bridge to [bus 07-10]
[    4.188565] pci 0000:00:1c.7:   bridge window [io  0xb000-0xbfff]
[    4.188570] pci 0000:00:1c.7:   bridge window [mem 0xfb800000-0xfbafffff]
[    4.188581] pci 0000:00:1c.7:   bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[    4.188738] pci 0000:08:01.0: [10b5:8608] type 1 class 0x000604
[    4.188950] pci 0000:08:01.0: PME# supported from D0 D3hot D3cold
[    4.188957] pci 0000:08:01.0: PME# disabled
[    4.189054] pci 0000:08:04.0: [10b5:8608] type 1 class 0x000604
[    4.189264] pci 0000:08:04.0: PME# supported from D0 D3hot D3cold
[    4.189271] pci 0000:08:04.0: PME# disabled
[    4.189363] pci 0000:08:05.0: [10b5:8608] type 1 class 0x000604
[    4.189574] pci 0000:08:05.0: PME# supported from D0 D3hot D3cold
[    4.189581] pci 0000:08:05.0: PME# disabled
[    4.189678] pci 0000:08:06.0: [10b5:8608] type 1 class 0x000604
[    4.189887] pci 0000:08:06.0: PME# supported from D0 D3hot D3cold
[    4.189895] pci 0000:08:06.0: PME# disabled
[    4.189994] pci 0000:08:07.0: [10b5:8608] type 1 class 0x000604
[    4.190203] pci 0000:08:07.0: PME# supported from D0 D3hot D3cold
[    4.190210] pci 0000:08:07.0: PME# disabled
[    4.190311] pci 0000:08:08.0: [10b5:8608] type 1 class 0x000604
[    4.190520] pci 0000:08:08.0: PME# supported from D0 D3hot D3cold
[    4.190527] pci 0000:08:08.0: PME# disabled
[    4.190632] pci 0000:08:09.0: [10b5:8608] type 1 class 0x000604
[    4.190841] pci 0000:08:09.0: PME# supported from D0 D3hot D3cold
[    4.190849] pci 0000:08:09.0: PME# disabled
[    4.190982] pci 0000:07:00.0: PCI bridge to [bus 08-10]
[    4.191025] pci 0000:07:00.0:   bridge window [io  0xb000-0xbfff]
[    4.191032] pci 0000:07:00.0:   bridge window [mem 0xfb800000-0xfb9fffff]
[    4.191045] pci 0000:07:00.0:   bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[    4.191167] pci 0000:08:01.0: PCI bridge to [bus 09-09]
[    4.191393] pci 0000:0a:00.0: [1b21:1080] type 1 class 0x000604
[    4.191659] pci 0000:0a:00.0: supports D1 D2
[    4.191660] pci 0000:0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    4.191669] pci 0000:0a:00.0: PME# disabled
[    4.191760] pci 0000:08:04.0: PCI bridge to [bus 0a-0b]
[    4.192093] pci 0000:0a:00.0: PCI bridge to [bus 0b-0b]
[    4.192341] pci 0000:0c:00.0: [1106:3403] type 0 class 0x000c00
[    4.192389] pci 0000:0c:00.0: reg 10: [mem 0xfb900000-0xfb9007ff 64bit]
[    4.192414] pci 0000:0c:00.0: reg 18: [io  0xb000-0xb0ff]
[    4.192630] pci 0000:0c:00.0: supports D2
[    4.192632] pci 0000:0c:00.0: PME# supported from D2 D3hot D3cold
[    4.192640] pci 0000:0c:00.0: PME# disabled
[    4.192734] pci 0000:08:05.0: PCI bridge to [bus 0c-0c]
[    4.192776] pci 0000:08:05.0:   bridge window [io  0xb000-0xbfff]
[    4.192783] pci 0000:08:05.0:   bridge window [mem 0xfb900000-0xfb9fffff]
[    4.192970] pci 0000:0d:00.0: [14e4:16b1] type 0 class 0x000200
[    4.193020] pci 0000:0d:00.0: reg 10: [mem 0xd0010000-0xd001ffff 64bit pref]
[    4.193060] pci 0000:0d:00.0: reg 18: [mem 0xd0000000-0xd000ffff 64bit pref]
[    4.193135] pci 0000:0d:00.0: reg 30: [mem 0xfb800000-0xfb8007ff pref]
[    4.193281] pci 0000:0d:00.0: PME# supported from D0 D3hot D3cold
[    4.193289] pci 0000:0d:00.0: PME# disabled
[    4.193410] pci 0000:08:06.0: PCI bridge to [bus 0d-0d]
[    4.193458] pci 0000:08:06.0:   bridge window [mem 0xfb800000-0xfb8fffff]
[    4.193471] pci 0000:08:06.0:   bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[    4.193595] pci 0000:08:07.0: PCI bridge to [bus 0e-0e]
[    4.193776] pci 0000:08:08.0: PCI bridge to [bus 0f-0f]
[    4.193962] pci 0000:08:09.0: PCI bridge to [bus 10-10]
[    4.194169] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    4.194352] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
[    4.194404] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
[    4.194447] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX5._PRT]
[    4.194490] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT]
[    4.194533] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7._PRT]
[    4.194579] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR21._PRT]
[    4.194769] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR21.BR31._PRT]
[    4.194818] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR21.BR34._PRT]
[    4.194868] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR21.BR34.BR22._PRT]
[    4.194940] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR21.BR35._PRT]
[    4.194988] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR21.BR36._PRT]
[    4.195036] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR21.BR37._PRT]
[    4.195084] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR21.BR38._PRT]
[    4.195132] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR21.BR39._PRT]
[    4.195175] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[    4.195369]  pci0000:00: Requesting ACPI _OSC control (0x1d)
[    4.195794]  pci0000:00: ACPI _OSC control (0x1c) granted
[    4.202690] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[    4.202926] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[    4.203158] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
[    4.203376] ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
[    4.203595] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
[    4.203848] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
[    4.204102] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
[    4.204355] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 10 11 12 14 15)
[    4.204564] xen/balloon: Initialising balloon driver.
[    4.204611] xen-balloon: Initialising balloon driver.
[    4.204706] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[    4.204762] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
[    4.204815] vgaarb: loaded
[    4.204842] vgaarb: bridge control possible 0000:01:00.0
[    4.204873] vgaarb: no bridge control possible 0000:00:02.0
[    4.204935] PCI: Using ACPI for IRQ routing
[    4.219490] PCI: pci_cache_line_size set to 64 bytes
[    4.219674] reserve RAM buffer: 000000000009d000 - 000000000009ffff 
[    4.219676] reserve RAM buffer: 000000006ed6d000 - 000000006fffffff 
[    4.219680] reserve RAM buffer: 000000006edf3000 - 000000006fffffff 
[    4.219683] reserve RAM buffer: 000000006f000000 - 000000006fffffff 
[    4.219784] Switching to clocksource xen
[    4.221344] pnp: PnP ACPI init
[    4.221382] ACPI: bus type pnp registered
[    4.221629] pnp 00:00: [bus 00-ff]
[    4.221631] pnp 00:00: [io  0x0cf8-0x0cff]
[    4.221633] pnp 00:00: [io  0x0000-0x03af window]
[    4.221635] pnp 00:00: [io  0x03e0-0x0cf7 window]
[    4.221636] pnp 00:00: [io  0x03b0-0x03df window]
[    4.221638] pnp 00:00: [io  0x0d00-0xffff window]
[    4.221640] pnp 00:00: [mem 0x000a0000-0x000bffff window]
[    4.221641] pnp 00:00: [mem 0x000c0000-0x000dffff window]
[    4.221643] pnp 00:00: [mem 0x7fa00000-0xffffffff window]
[    4.221645] pnp 00:00: [mem 0x00000000 window]
[    4.221687] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
[    4.221786] pnp 00:01: [mem 0xfed10000-0xfed19fff]
[    4.221787] pnp 00:01: [mem 0xe0000000-0xefffffff]
[    4.221789] pnp 00:01: [mem 0xfed90000-0xfed93fff]
[    4.221791] pnp 00:01: [mem 0xfed20000-0xfed3ffff]
[    4.221792] pnp 00:01: [mem 0xfee00000-0xfee0ffff]
[    4.221833] system 00:01: [mem 0xfed10000-0xfed19fff] has been reserved
[    4.221868] system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
[    4.221902] system 00:01: [mem 0xfed90000-0xfed93fff] has been reserved
[    4.221937] system 00:01: [mem 0xfed20000-0xfed3ffff] has been reserved
[    4.221971] system 00:01: [mem 0xfee00000-0xfee0ffff] could not be reserved
[    4.222006] system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
[    4.222090] pnp 00:02: [io  0x0000-0xffffffffffffffff disabled]
[    4.222092] pnp 00:02: [io  0x0290-0x029f]
[    4.222093] pnp 00:02: [io  0x0000-0xffffffffffffffff disabled]
[    4.222131] system 00:02: [io  0x0290-0x029f] has been reserved
[    4.222165] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
[    4.222645] pnp 00:03: [dma 4]
[    4.222647] pnp 00:03: [io  0x0000-0x000f]
[    4.222649] pnp 00:03: [io  0x0081-0x0083]
[    4.222651] pnp 00:03: [io  0x0087]
[    4.222653] pnp 00:03: [io  0x0089-0x008b]
[    4.222654] pnp 00:03: [io  0x008f]
[    4.222655] pnp 00:03: [io  0x00c0-0x00df]
[    4.222677] pnp 00:03: Plug and Play ACPI device, IDs PNP0200 (active)
[    4.222688] pnp 00:04: [io  0x0070-0x0071]
[    4.222690] xen: registering gsi 8 triggering 1 polarity 0
[    4.222693] xen_map_pirq_gsi: returning irq 8 for gsi 8
[    4.222725] xen: --> pirq=8 -> irq=8 (gsi=8)
[    4.222743] pnp 00:04: [irq 8]
[    4.222764] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
[    4.222773] pnp 00:05: [io  0x0061]
[    4.222793] pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
[    4.222819] pnp 00:06: [io  0x0010-0x001f]
[    4.222821] pnp 00:06: [io  0x0022-0x003f]
[    4.222822] pnp 00:06: [io  0x0044-0x005f]
[    4.222824] pnp 00:06: [io  0x0062-0x0063]
[    4.222825] pnp 00:06: [io  0x0065-0x006f]
[    4.222827] pnp 00:06: [io  0x0072-0x007f]
[    4.222828] pnp 00:06: [io  0x0080]
[    4.222830] pnp 00:06: [io  0x0084-0x0086]
[    4.222831] pnp 00:06: [io  0x0088]
[    4.222833] pnp 00:06: [io  0x008c-0x008e]
[    4.222834] pnp 00:06: [io  0x0090-0x009f]
[    4.222835] pnp 00:06: [io  0x00a2-0x00bf]
[    4.222837] pnp 00:06: [io  0x00e0-0x00ef]
[    4.222838] pnp 00:06: [io  0x04d0-0x04d1]
[    4.222881] system 00:06: [io  0x04d0-0x04d1] has been reserved
[    4.222915] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[    4.222923] pnp 00:07: [io  0x00f0-0x00ff]
[    4.222925] xen: registering gsi 13 triggering 1 polarity 0
[    4.222927] xen_map_pirq_gsi: returning irq 13 for gsi 13
[    4.222959] xen: --> pirq=13 -> irq=13 (gsi=13)
[    4.222976] pnp 00:07: [irq 13]
[    4.222999] pnp 00:07: Plug and Play ACPI device, IDs PNP0c04 (active)
[    4.223396] pnp 00:08: [io  0x03f8-0x03ff]
[    4.223398] xen: registering gsi 4 triggering 1 polarity 0
[    4.223400] xen_map_pirq_gsi: returning irq 4 for gsi 4
[    4.223432] xen: --> pirq=4 -> irq=4 (gsi=4)
[    4.223448] pnp 00:08: [irq 4]
[    4.223450] pnp 00:08: [dma 0 disabled]
[    4.223500] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
[    4.223815] pnp 00:09: [io  0x0400-0x0453]
[    4.223817] pnp 00:09: [io  0x0458-0x047f]
[    4.223818] pnp 00:09: [io  0x1180-0x119f]
[    4.223820] pnp 00:09: [io  0x0500-0x057f]
[    4.223822] pnp 00:09: [mem 0xfed1c000-0xfed1ffff]
[    4.223823] pnp 00:09: [mem 0xfec00000-0xfecfffff]
[    4.223825] pnp 00:09: [mem 0xfed08000-0xfed08fff]
[    4.223826] pnp 00:09: [mem 0xff000000-0xffffffff]
[    4.223871] system 00:09: [io  0x0400-0x0453] has been reserved
[    4.223905] system 00:09: [io  0x0458-0x047f] has been reserved
[    4.223938] system 00:09: [io  0x1180-0x119f] has been reserved
[    4.223971] system 00:09: [io  0x0500-0x057f] has been reserved
[    4.224005] system 00:09: [mem 0xfed1c000-0xfed1ffff] has been reserved
[    4.224039] system 00:09: [mem 0xfec00000-0xfecfffff] could not be reserved
[    4.224074] system 00:09: [mem 0xfed08000-0xfed08fff] has been reserved
[    4.224108] system 00:09: [mem 0xff000000-0xffffffff] has been reserved
[    4.224142] system 00:09: Plug and Play ACPI device, IDs PNP0c01 (active)
[    4.224202] pnp 00:0a: [io  0x0454-0x0457]
[    4.224243] system 00:0a: [io  0x0454-0x0457] has been reserved
[    4.224277] system 00:0a: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    4.224438] pnp 00:0b: [mem 0xfed00000-0xfed003ff]
[    4.224474] pnp 00:0b: Plug and Play ACPI device, IDs PNP0103 (active)
[    4.224685] pnp: PnP ACPI: found 12 devices
[    4.224715] ACPI: ACPI bus type pnp unregistered
[    4.230268] PM-Timer failed consistency check  (0x0xffffff) - aborting.
[    4.230318] PCI: max bus depth: 4 pci_try_num: 5
[    4.230559] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[    4.230592] pci 0000:00:01.0:   bridge window [io  0xe000-0xefff]
[    4.230628] pci 0000:00:01.0:   bridge window [mem 0xfbe00000-0xfbefffff]
[    4.230664] pci 0000:00:01.0:   bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
[    4.230715] pci 0000:02:00.0: PCI bridge to [bus 03-03]
[    4.230750] pci 0000:02:00.0:   bridge window [io  0xd000-0xdfff]
[    4.230815] pci 0000:00:1c.0: PCI bridge to [bus 02-03]
[    4.230849] pci 0000:00:1c.0:   bridge window [io  0xd000-0xdfff]
[    4.230902] pci 0000:00:1c.4: PCI bridge to [bus 04-04]
[    4.230935] pci 0000:00:1c.4:   bridge window [io  0xc000-0xcfff]
[    4.230975] pci 0000:00:1c.4:   bridge window [mem 0xfbd00000-0xfbdfffff]
[    4.231021] pci 0000:00:1c.5: PCI bridge to [bus 05-05]
[    4.231060] pci 0000:00:1c.5:   bridge window [mem 0xfbc00000-0xfbcfffff]
[    4.231107] pci 0000:00:1c.6: PCI bridge to [bus 06-06]
[    4.231144] pci 0000:00:1c.6:   bridge window [mem 0xfbb00000-0xfbbfffff]
[    4.231192] pci 0000:08:01.0: PCI bridge to [bus 09-09]
[    4.231248] pci 0000:0a:00.0: PCI bridge to [bus 0b-0b]
[    4.231312] pci 0000:08:04.0: PCI bridge to [bus 0a-0b]
[    4.231368] pci 0000:08:05.0: PCI bridge to [bus 0c-0c]
[    4.231402] pci 0000:08:05.0:   bridge window [io  0xb000-0xbfff]
[    4.231444] pci 0000:08:05.0:   bridge window [mem 0xfb900000-0xfb9fffff]
[    4.231494] pci 0000:08:06.0: PCI bridge to [bus 0d-0d]
[    4.231534] pci 0000:08:06.0:   bridge window [mem 0xfb800000-0xfb8fffff]
[    4.231573] pci 0000:08:06.0:   bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[    4.231630] pci 0000:08:07.0: PCI bridge to [bus 0e-0e]
[    4.231687] pci 0000:08:08.0: PCI bridge to [bus 0f-0f]
[    4.231744] pci 0000:08:09.0: PCI bridge to [bus 10-10]
[    4.231800] pci 0000:07:00.0: PCI bridge to [bus 08-10]
[    4.231834] pci 0000:07:00.0:   bridge window [io  0xb000-0xbfff]
[    4.231876] pci 0000:07:00.0:   bridge window [mem 0xfb800000-0xfb9fffff]
[    4.231915] pci 0000:07:00.0:   bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[    4.231972] pci 0000:00:1c.7: PCI bridge to [bus 07-10]
[    4.232005] pci 0000:00:1c.7:   bridge window [io  0xb000-0xbfff]
[    4.232044] pci 0000:00:1c.7:   bridge window [mem 0xfb800000-0xfbafffff]
[    4.232083] pci 0000:00:1c.7:   bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[    4.232142] xen: registering gsi 16 triggering 0 polarity 1
[    4.232152] xen: --> pirq=16 -> irq=16 (gsi=16)
[    4.232167] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.232204] pci 0000:00:01.0: setting latency timer to 64
[    4.232212] xen: registering gsi 17 triggering 0 polarity 1
[    4.232216] xen: --> pirq=17 -> irq=17 (gsi=17)
[    4.232231] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    4.232269] pci 0000:00:1c.0: setting latency timer to 64
[    4.232277] xen: registering gsi 16 triggering 0 polarity 1
[    4.232278] xen_map_pirq_gsi: returning irq 16 for gsi 16
[    4.232310] xen: --> pirq=16 -> irq=16 (gsi=16)
[    4.232311] Already setup the GSI :16
[    4.232340] pci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.232382] pci 0000:02:00.0: setting latency timer to 64
[    4.232392] xen: registering gsi 17 triggering 0 polarity 1
[    4.232394] xen_map_pirq_gsi: returning irq 17 for gsi 17
[    4.232425] xen: --> pirq=17 -> irq=17 (gsi=17)
[    4.232426] Already setup the GSI :17
[    4.232455] pci 0000:00:1c.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    4.232493] pci 0000:00:1c.4: setting latency timer to 64
[    4.232502] xen: registering gsi 16 triggering 0 polarity 1
[    4.232503] xen_map_pirq_gsi: returning irq 16 for gsi 16
[    4.232535] xen: --> pirq=16 -> irq=16 (gsi=16)
[    4.232536] Already setup the GSI :16
[    4.232565] pci 0000:00:1c.5: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[    4.232603] pci 0000:00:1c.5: setting latency timer to 64
[    4.232612] xen: registering gsi 18 triggering 0 polarity 1
[    4.232616] xen: --> pirq=18 -> irq=18 (gsi=18)
[    4.232631] pci 0000:00:1c.6: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    4.232669] pci 0000:00:1c.6: setting latency timer to 64
[    4.232678] xen: registering gsi 19 triggering 0 polarity 1
[    4.232681] xen: --> pirq=19 -> irq=19 (gsi=19)
[    4.232696] pci 0000:00:1c.7: PCI INT D -> GSI 19 (level, low) -> IRQ 19
[    4.232733] pci 0000:00:1c.7: setting latency timer to 64
[    4.232743] xen: registering gsi 19 triggering 0 polarity 1
[    4.232745] xen_map_pirq_gsi: returning irq 19 for gsi 19
[    4.232777] xen: --> pirq=19 -> irq=19 (gsi=19)
[    4.232778] Already setup the GSI :19
[    4.232807] pci 0000:07:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    4.232847] pci 0000:07:00.0: setting latency timer to 64
[    4.232857] xen: registering gsi 16 triggering 0 polarity 1
[    4.232859] xen_map_pirq_gsi: returning irq 16 for gsi 16
[    4.232890] xen: --> pirq=16 -> irq=16 (gsi=16)
[    4.232891] Already setup the GSI :16
[    4.232921] pci 0000:08:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.232960] pci 0000:08:01.0: setting latency timer to 64
[    4.232971] xen: registering gsi 19 triggering 0 polarity 1
[    4.232972] xen_map_pirq_gsi: returning irq 19 for gsi 19
[    4.233004] xen: --> pirq=19 -> irq=19 (gsi=19)
[    4.233005] Already setup the GSI :19
[    4.233034] pci 0000:08:04.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    4.233074] pci 0000:08:04.0: setting latency timer to 64
[    4.233086] xen: registering gsi 19 triggering 0 polarity 1
[    4.233087] xen_map_pirq_gsi: returning irq 19 for gsi 19
[    4.233119] xen: --> pirq=19 -> irq=19 (gsi=19)
[    4.233120] Already setup the GSI :19
[    4.233150] pci 0000:0a:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    4.233190] pci 0000:0a:00.0: setting latency timer to 64
[    4.233202] xen: registering gsi 16 triggering 0 polarity 1
[    4.233203] xen_map_pirq_gsi: returning irq 16 for gsi 16
[    4.233235] xen: --> pirq=16 -> irq=16 (gsi=16)
[    4.233236] Already setup the GSI :16
[    4.234560] pci 0000:08:05.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.234599] pci 0000:08:05.0: setting latency timer to 64
[    4.234610] xen: registering gsi 17 triggering 0 polarity 1
[    4.234611] xen_map_pirq_gsi: returning irq 17 for gsi 17
[    4.234643] xen: --> pirq=17 -> irq=17 (gsi=17)
[    4.234644] Already setup the GSI :17
[    4.234673] pci 0000:08:06.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    4.234713] pci 0000:08:06.0: setting latency timer to 64
[    4.234723] xen: registering gsi 18 triggering 0 polarity 1
[    4.234725] xen_map_pirq_gsi: returning irq 18 for gsi 18
[    4.234756] xen: --> pirq=18 -> irq=18 (gsi=18)
[    4.234758] Already setup the GSI :18
[    4.234787] pci 0000:08:07.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    4.234826] pci 0000:08:07.0: setting latency timer to 64
[    4.234837] xen: registering gsi 19 triggering 0 polarity 1
[    4.234838] xen_map_pirq_gsi: returning irq 19 for gsi 19
[    4.234870] xen: --> pirq=19 -> irq=19 (gsi=19)
[    4.234871] Already setup the GSI :19
[    4.234900] pci 0000:08:08.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    4.234939] pci 0000:08:08.0: setting latency timer to 64
[    4.234950] xen: registering gsi 16 triggering 0 polarity 1
[    4.234952] xen_map_pirq_gsi: returning irq 16 for gsi 16
[    4.234983] xen: --> pirq=16 -> irq=16 (gsi=16)
[    4.234985] Already setup the GSI :16
[    4.235013] pci 0000:08:09.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.235053] pci 0000:08:09.0: setting latency timer to 64
[    4.235057] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
[    4.235059] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
[    4.235060] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
[    4.235062] pci_bus 0000:00: resource 7 [io  0x0d00-0xffff]
[    4.235063] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
[    4.235065] pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff]
[    4.235067] pci_bus 0000:00: resource 10 [mem 0x7fa00000-0xffffffff]
[    4.235068] pci_bus 0000:01: resource 0 [io  0xe000-0xefff]
[    4.235070] pci_bus 0000:01: resource 1 [mem 0xfbe00000-0xfbefffff]
[    4.235071] pci_bus 0000:01: resource 2 [mem 0xc0000000-0xcfffffff 64bit pref]
[    4.235073] pci_bus 0000:02: resource 0 [io  0xd000-0xdfff]
[    4.235075] pci_bus 0000:03: resource 0 [io  0xd000-0xdfff]
[    4.235076] pci_bus 0000:04: resource 0 [io  0xc000-0xcfff]
[    4.235078] pci_bus 0000:04: resource 1 [mem 0xfbd00000-0xfbdfffff]
[    4.235079] pci_bus 0000:05: resource 1 [mem 0xfbc00000-0xfbcfffff]
[    4.235081] pci_bus 0000:06: resource 1 [mem 0xfbb00000-0xfbbfffff]
[    4.235082] pci_bus 0000:07: resource 0 [io  0xb000-0xbfff]
[    4.235084] pci_bus 0000:07: resource 1 [mem 0xfb800000-0xfbafffff]
[    4.235085] pci_bus 0000:07: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
[    4.235087] pci_bus 0000:08: resource 0 [io  0xb000-0xbfff]
[    4.235088] pci_bus 0000:08: resource 1 [mem 0xfb800000-0xfb9fffff]
[    4.235090] pci_bus 0000:08: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
[    4.235092] pci_bus 0000:0c: resource 0 [io  0xb000-0xbfff]
[    4.235093] pci_bus 0000:0c: resource 1 [mem 0xfb900000-0xfb9fffff]
[    4.235095] pci_bus 0000:0d: resource 1 [mem 0xfb800000-0xfb8fffff]
[    4.235097] pci_bus 0000:0d: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
[    4.235149] NET: Registered protocol family 2
[    4.235626] IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    4.237523] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
[    4.238833] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    4.239008] TCP: Hash tables configured (established 524288 bind 65536)
[    4.239042] TCP reno registered
[    4.239098] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[    4.239174] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[    4.239318] NET: Registered protocol family 1
[    4.239368] pci 0000:00:02.0: Boot video device
[    4.463995] PCI: CLS 64 bytes, default 64
[    4.464034] Unpacking initramfs...
[    4.489942] Freeing initrd memory: 33736k freed
[    4.495428] audit: initializing netlink socket (disabled)
[    4.495473] type=2000 audit(1329948441.475:1): initialized
[    4.511215] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    4.511481] VFS: Disk quotas dquot_6.5.2
[    4.511544] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    4.511659] msgmni has been set to 11369
[    4.511859] alg: No test for stdrng (krng)
[    4.511919] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    4.511968] io scheduler noop registered
[    4.511998] io scheduler deadline registered
[    4.512042] io scheduler cfq registered (default)
[    4.512178] pcieport 0000:00:01.0: setting latency timer to 64
[    4.512335] pcieport 0000:00:1c.0: setting latency timer to 64
[    4.512552] pcieport 0000:00:1c.4: setting latency timer to 64
[    4.512769] pcieport 0000:00:1c.5: setting latency timer to 64
[    4.512986] pcieport 0000:00:1c.6: setting latency timer to 64
[    4.513202] pcieport 0000:00:1c.7: setting latency timer to 64
[    4.513437] pcieport 0000:07:00.0: setting latency timer to 64
[    4.513747] pcieport 0000:08:01.0: setting latency timer to 64
[    4.514058] pcieport 0000:08:04.0: setting latency timer to 64
[    4.514371] pcieport 0000:08:05.0: setting latency timer to 64
[    4.514681] pcieport 0000:08:06.0: setting latency timer to 64
[    4.514992] pcieport 0000:08:07.0: setting latency timer to 64
[    4.515303] pcieport 0000:08:08.0: setting latency timer to 64
[    4.515614] pcieport 0000:08:09.0: setting latency timer to 64
[    4.515958] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
[    4.515994] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    4.516028] pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
[    4.516063] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
[    4.516098] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[    4.516132] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
[    4.516166] pci 0000:03:04.0: Signaling PME through PCIe PME interrupt
[    4.516204] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
[    4.516239] pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
[    4.516274] pci 0000:04:00.0: Signaling PME through PCIe PME interrupt
[    4.516312] pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
[    4.516347] pcieport 0000:00:1c.5: Signaling PME through PCIe PME interrupt
[    4.516381] pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
[    4.516419] pcie_pme 0000:00:1c.5:pcie01: service driver pcie_pme loaded
[    4.516453] pcieport 0000:00:1c.6: Signaling PME through PCIe PME interrupt
[    4.516488] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
[    4.516526] pcie_pme 0000:00:1c.6:pcie01: service driver pcie_pme loaded
[    4.516561] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
[    4.516595] pcieport 0000:07:00.0: Signaling PME through PCIe PME interrupt
[    4.516629] pcieport 0000:08:01.0: Signaling PME through PCIe PME interrupt
[    4.516663] pcieport 0000:08:04.0: Signaling PME through PCIe PME interrupt
[    4.516697] pci 0000:0a:00.0: Signaling PME through PCIe PME interrupt
[    4.516731] pcieport 0000:08:05.0: Signaling PME through PCIe PME interrupt
[    4.516765] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
[    4.516798] pcieport 0000:08:06.0: Signaling PME through PCIe PME interrupt
[    4.516832] pci 0000:0d:00.0: Signaling PME through PCIe PME interrupt
[    4.516865] pcieport 0000:08:07.0: Signaling PME through PCIe PME interrupt
[    4.516899] pcieport 0000:08:08.0: Signaling PME through PCIe PME interrupt
[    4.516933] pcieport 0000:08:09.0: Signaling PME through PCIe PME interrupt
[    4.516972] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
[    4.517069] ERST: Table is not found!
[    4.517098] GHES: HEST is not enabled!
[    4.517497] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    4.538252] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    4.588744] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    4.604106] hpet_acpi_add: no address or irqs in _CRS
[    4.604146] Linux agpgart interface v0.103
[    4.604249] agpgart-intel 0000:00:00.0: Intel Sandybridge Chipset
[    4.604418] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[    4.605461] agpgart-intel 0000:00:00.0: detected 262144K stolen memory
[    4.605638] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xb0000000
[    4.605771] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    4.608698] serio: i8042 KBD port at 0x60,0x64 irq 1
[    4.608735] serio: i8042 AUX port at 0x60,0x64 irq 12
[    4.608910] mousedev: PS/2 mouse device common for all mice
[    4.608991] rtc_cmos 00:04: RTC can wake from S4
[    4.609186] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
[    4.609278] rtc0: alarms up to one month, y3k, 114 bytes nvram
[    4.609431] TCP cubic registered
[    4.609502] NET: Registered protocol family 10
[    4.609809] Mobile IPv6
[    4.609837] NET: Registered protocol family 17
[    4.609869] Registering the dns_resolver key type
[    4.610037] PM: Hibernation image not present or could not be loaded.
[    4.610048] registered taskstats version 1
[    4.611048] rtc_cmos 00:04: setting system clock to 2012-02-22 22:07:20 UTC (1329948440)
[    4.611152] Initializing network drop monitor service
[    4.611383] Freeing unused kernel memory: 568k freed
[    4.611469] Write protecting the kernel read-only data: 6144k
[    4.613428] Freeing unused kernel memory: 712k freed
[    4.613711] Freeing unused kernel memory: 684k freed
[    4.633455] udevd[50]: starting version 175
[    4.667069] usbcore: registered new interface driver usbfs
[    4.667134] usbcore: registered new interface driver hub
[    4.677044] SCSI subsystem initialized
[    4.679549] usbcore: registered new device driver usb
[    4.680286] xen: registering gsi 17 triggering 0 polarity 1
[    4.680292] xen_map_pirq_gsi: returning irq 17 for gsi 17
[    4.680331] xen: --> pirq=17 -> irq=17 (gsi=17)
[    4.680333] Already setup the GSI :17
[    4.680370] xhci_hcd 0000:05:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    4.680441] xhci_hcd 0000:05:00.0: setting latency timer to 64
[    4.680447] xhci_hcd 0000:05:00.0: xHCI Host Controller
[    4.680503] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 1
[    4.680770] xhci_hcd 0000:05:00.0: irq 17, io mem 0xfbc00000
[    4.680860] xhci_hcd 0000:05:00.0: Failed to enable MSI-X
[    4.681149] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    4.681189] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.681241] usb usb1: Product: xHCI Host Controller
[    4.681277] usb usb1: Manufacturer: Linux 3.2.0-1-amd64 xhci_hcd
[    4.681315] usb usb1: SerialNumber: 0000:05:00.0
[    4.685473] xHCI xhci_add_endpoint called for root hub
[    4.685476] xHCI xhci_check_bandwidth called for root hub
[    4.685510] hub 1-0:1.0: USB hub found
[    4.685555] hub 1-0:1.0: 2 ports detected
[    4.685688] xhci_hcd 0000:05:00.0: xHCI Host Controller
[    4.685733] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 2
[    4.685831] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    4.685874] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.685926] usb usb2: Product: xHCI Host Controller
[    4.685963] usb usb2: Manufacturer: Linux 3.2.0-1-amd64 xhci_hcd
[    4.686001] usb usb2: SerialNumber: 0000:05:00.0
[    4.688319] xHCI xhci_add_endpoint called for root hub
[    4.688322] xHCI xhci_check_bandwidth called for root hub
[    4.688356] hub 2-0:1.0: USB hub found
[    4.688399] hub 2-0:1.0: 2 ports detected
[    4.700516] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.700583] xen: registering gsi 16 triggering 0 polarity 1
[    4.700589] xen_map_pirq_gsi: returning irq 16 for gsi 16
[    4.700628] xen: --> pirq=16 -> irq=16 (gsi=16)
[    4.700631] Already setup the GSI :16
[    4.700667] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.700728] ehci_hcd 0000:00:1a.0: setting latency timer to 64
[    4.700734] ehci_hcd 0000:00:1a.0: EHCI Host Controller
[    4.700780] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[    4.700882] ehci_hcd 0000:00:1a.0: debug port 2
[    4.704823] ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported
[    4.705255] ehci_hcd 0000:00:1a.0: irq 16, io mem 0xfbf03000
[    4.707953] xen: registering gsi 18 triggering 0 polarity 1
[    4.707957] xen_map_pirq_gsi: returning irq 18 for gsi 18
[    4.708026] xen: --> pirq=18 -> irq=18 (gsi=18)
[    4.708028] Already setup the GSI :18
[    4.708097] xhci_hcd 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    4.708203] xhci_hcd 0000:06:00.0: setting latency timer to 64
[    4.708209] xhci_hcd 0000:06:00.0: xHCI Host Controller
[    4.708281] xhci_hcd 0000:06:00.0: new USB bus registered, assigned bus number 4
[    4.708609] xhci_hcd 0000:06:00.0: irq 18, io mem 0xfbb00000
[    4.708740] xhci_hcd 0000:06:00.0: Failed to enable MSI-X
[    4.709088] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[    4.709162] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.709221] usb usb4: Product: xHCI Host Controller
[    4.709258] usb usb4: Manufacturer: Linux 3.2.0-1-amd64 xhci_hcd
[    4.709295] usb usb4: SerialNumber: 0000:06:00.0
[    4.709416] xHCI xhci_add_endpoint called for root hub
[    4.709419] xHCI xhci_check_bandwidth called for root hub
[    4.709453] hub 4-0:1.0: USB hub found
[    4.709496] hub 4-0:1.0: 2 ports detected
[    4.709608] xhci_hcd 0000:06:00.0: xHCI Host Controller
[    4.709651] xhci_hcd 0000:06:00.0: new USB bus registered, assigned bus number 5
[    4.709728] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
[    4.709768] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.709819] usb usb5: Product: xHCI Host Controller
[    4.709855] usb usb5: Manufacturer: Linux 3.2.0-1-amd64 xhci_hcd
[    4.709893] usb usb5: SerialNumber: 0000:06:00.0
[    4.710032] libata version 3.00 loaded.
[    4.710137] xHCI xhci_add_endpoint called for root hub
[    4.710140] xHCI xhci_check_bandwidth called for root hub
[    4.710171] hub 5-0:1.0: USB hub found
[    4.710214] hub 5-0:1.0: 2 ports detected
[    4.727906] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[    4.727977] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    4.728022] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.728077] usb usb3: Product: EHCI Host Controller
[    4.728115] usb usb3: Manufacturer: Linux 3.2.0-1-amd64 ehci_hcd
[    4.728154] usb usb3: SerialNumber: 0000:00:1a.0
[    4.728335] hub 3-0:1.0: USB hub found
[    4.728374] hub 3-0:1.0: 2 ports detected
[    4.728504] ahci 0000:00:1f.2: version 3.0
[    4.728519] xen: registering gsi 19 triggering 0 polarity 1
[    4.728527] xen_map_pirq_gsi: returning irq 19 for gsi 19
[    4.728573] xen: --> pirq=19 -> irq=19 (gsi=19)
[    4.728576] Already setup the GSI :19
[    4.728613] ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    4.741581] tg3.c:v3.121 (November 2, 2011)
[    4.741632] xen: registering gsi 17 triggering 0 polarity 1
[    4.741636] xen_map_pirq_gsi: returning irq 17 for gsi 17
[    4.741674] xen: --> pirq=17 -> irq=17 (gsi=17)
[    4.741676] Already setup the GSI :17
[    4.741711] tg3 0000:0d:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    4.741762] tg3 0000:0d:00.0: setting latency timer to 64
[    4.743920] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
[    4.745278] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst 
[    4.745338] ahci 0000:00:1f.2: setting latency timer to 64
[    4.749960] xen: registering gsi 16 triggering 0 polarity 1
[    4.749965] xen_map_pirq_gsi: returning irq 16 for gsi 16
[    4.750003] xen: --> pirq=16 -> irq=16 (gsi=16)
[    4.750005] Already setup the GSI :16
[    4.750041] firewire_ohci 0000:0c:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.750102] firewire_ohci 0000:0c:00.0: setting latency timer to 64
[    4.769292] tg3 0000:0d:00.0: eth0: Tigon3 [partno(BCM57781) rev 57785100] (PCI Express) MAC address 00:25:22:f6:b9:2e
[    4.769364] tg3 0000:0d:00.0: eth0: attached PHY is 57765 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[    4.769421] tg3 0000:0d:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[    4.769479] tg3 0000:0d:00.0: eth0: dma_rwctrl[00000001] dma_mask[64-bit]
[    4.784554] scsi0 : ahci
[    4.784684] scsi1 : ahci
[    4.784788] scsi2 : ahci
[    4.784892] scsi3 : ahci
[    4.785011] scsi4 : ahci
[    4.785117] scsi5 : ahci
[    4.785341] ata1: SATA max UDMA/133 abar m2048@0xfbf01000 port 0xfbf01100 irq 300
[    4.785390] ata2: SATA max UDMA/133 abar m2048@0xfbf01000 port 0xfbf01180 irq 300
[    4.785437] ata3: SATA max UDMA/133 abar m2048@0xfbf01000 port 0xfbf01200 irq 300
[    4.785485] ata4: SATA max UDMA/133 abar m2048@0xfbf01000 port 0xfbf01280 irq 300
[    4.785533] ata5: SATA max UDMA/133 abar m2048@0xfbf01000 port 0xfbf01300 irq 300
[    4.785580] ata6: SATA max UDMA/133 abar m2048@0xfbf01000 port 0xfbf01380 irq 300
[    4.785655] xen: registering gsi 16 triggering 0 polarity 1
[    4.785659] xen_map_pirq_gsi: returning irq 16 for gsi 16
[    4.785700] xen: --> pirq=16 -> irq=16 (gsi=16)
[    4.785702] Already setup the GSI :16
[    4.785740] ahci 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.785992] ahci 0000:04:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[    4.786040] ahci 0000:04:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs 
[    4.786093] ahci 0000:04:00.0: setting latency timer to 64
[    4.786383] xen: registering gsi 23 triggering 0 polarity 1
[    4.786392] xen: --> pirq=23 -> irq=23 (gsi=23)
[    4.786406] scsi6 : ahci
[    4.786412] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[    4.786436] ehci_hcd 0000:00:1d.0: setting latency timer to 64
[    4.786441] ehci_hcd 0000:00:1d.0: EHCI Host Controller
[    4.786453] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
[    4.786512] ehci_hcd 0000:00:1d.0: debug port 2
[    4.786834] scsi7 : ahci
[    4.786943] ata7: SATA max UDMA/133 abar m2048@0xfbd10000 port 0xfbd10100 irq 301
[    4.787040] ata8: SATA max UDMA/133 abar m2048@0xfbd10000 port 0xfbd10180 irq 301
[    4.790391] ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported
[    4.790431] ehci_hcd 0000:00:1d.0: irq 23, io mem 0xfbf02000
[    4.803892] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[    4.803966] usb usb6: New USB device found, idVendor=1d6b, idProduct=0002
[    4.804001] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.804046] usb usb6: Product: EHCI Host Controller
[    4.804077] usb usb6: Manufacturer: Linux 3.2.0-1-amd64 ehci_hcd
[    4.804110] usb usb6: SerialNumber: 0000:00:1d.0
[    4.804244] hub 6-0:1.0: USB hub found
[    4.804281] hub 6-0:1.0: 2 ports detected
[    4.811961] firewire_ohci: Added fw-ohci device 0000:0c:00.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x11
[    4.995942] usb 1-2: new high-speed USB device number 2 using xhci_hcd
[    5.013196] usb 1-2: New USB device found, idVendor=0409, idProduct=005a
[    5.013254] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    5.013480] hub 1-2:1.0: USB hub found
[    5.013682] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep
[    5.013816] hub 1-2:1.0: 4 ports detected
[    5.103904] ata3: SATA link down (SStatus 0 SControl 300)
[    5.103992] ata6: SATA link down (SStatus 0 SControl 300)
[    5.104006] ata7: SATA link down (SStatus 0 SControl 330)
[    5.104055] ata8: SATA link down (SStatus 0 SControl 330)
[    5.104170] ata1: SATA link down (SStatus 0 SControl 300)
[    5.104230] ata5: SATA link down (SStatus 0 SControl 300)
[    5.111910] ata4: SATA link down (SStatus 0 SControl 300)
[    5.111994] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    5.112304] ata2.00: ATA-8: INTEL SSDSC2MH120A2, PPG4, max UDMA/133
[    5.112355] ata2.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    5.112703] ata2.00: configured for UDMA/133
[    5.112854] scsi 1:0:0:0: Direct-Access     ATA      INTEL SSDSC2MH12 PPG4 PQ: 0 ANSI: 5
[    5.116782] sd 1:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
[    5.116959] sd 1:0:0:0: [sda] Write Protect is off
[    5.116991] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    5.117026] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.119070]  sda: sda1 sda2 sda3
[    5.119480] sd 1:0:0:0: [sda] Attached SCSI disk
[    5.123887] usb 3-1: new high-speed USB device number 2 using ehci_hcd
[    5.256235] usb 3-1: New USB device found, idVendor=8087, idProduct=0024
[    5.256294] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    5.256535] hub 3-1:1.0: USB hub found
[    5.256736] hub 3-1:1.0: 6 ports detected
[    5.312243] firewire_core: created device fw0: GUID 008f13005d650f00, S400
[    5.367904] usb 6-1: new high-speed USB device number 2 using ehci_hcd
[    5.385866] device-mapper: uevent: version 1.0.3
[    5.385976] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
[    5.500225] usb 6-1: New USB device found, idVendor=8087, idProduct=0024
[    5.500230] usb 6-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    5.500512] hub 6-1:1.0: USB hub found
[    5.500595] hub 6-1:1.0: 8 ports detected
[    5.571977] usb 3-1.4: new high-speed USB device number 3 using ehci_hcd
[    5.664723] usb 3-1.4: New USB device found, idVendor=0781, idProduct=5567
[    5.664727] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    5.664731] usb 3-1.4: Product: Cruzer Blade
[    5.664734] usb 3-1.4: Manufacturer: SanDisk
[    5.664736] usb 3-1.4: SerialNumber: 200515358218B5A33CBE
[    5.667062] usbcore: registered new interface driver uas
[    5.667771] Initializing USB Mass Storage driver...
[    5.667888] scsi8 : usb-storage 3-1.4:1.0
[    5.667984] usbcore: registered new interface driver usb-storage
[    5.667987] USB Mass Storage support registered.
[    5.771967] usb 6-1.1: new low-speed USB device number 3 using ehci_hcd
[    5.882115] usb 6-1.1: New USB device found, idVendor=04d9, idProduct=2221
[    5.882119] usb 6-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[    5.882123] usb 6-1.1: Product: USB Keyboard
[    5.895533] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.1/6-1.1:1.0/input/input0
[    5.895604] generic-usb 0003:04D9:2221.0001: input,hidraw0: USB HID v1.10 Keyboard [USB Keyboard] on usb-0000:00:1d.0-1.1/input0
[    5.918636] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.1/6-1.1:1.1/input/input1
[    5.918708] generic-usb 0003:04D9:2221.0002: input,hidraw1: USB HID v1.10 Device [USB Keyboard] on usb-0000:00:1d.0-1.1/input1
[    5.918724] usbcore: registered new interface driver usbhid
[    5.918726] usbhid: USB HID core driver
[    5.951991] usb 6-1.2: new full-speed USB device number 4 using ehci_hcd
[    6.046357] usb 6-1.2: New USB device found, idVendor=1532, idProduct=0015
[    6.046362] usb 6-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.046366] usb 6-1.2: Product: Razer Naga
[    6.046368] usb 6-1.2: Manufacturer: Razer
[    6.092630] input: Razer Razer Naga as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.2/6-1.2:1.0/input/input2
[    6.092754] generic-usb 0003:1532:0015.0003: input,hidraw2: USB HID v1.11 Mouse [Razer Razer Naga] on usb-0000:00:1d.0-1.2/input0
[    6.093815] input: Razer Razer Naga as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.2/6-1.2:1.1/input/input3
[    6.093934] generic-usb 0003:1532:0015.0004: input,hidraw3: USB HID v1.11 Keyboard [Razer Razer Naga] on usb-0000:00:1d.0-1.2/input1
[    6.668637] scsi 8:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.00 PQ: 0 ANSI: 2
[    6.669976] sd 8:0:0:0: [sdb] 31250432 512-byte logical blocks: (16.0 GB/14.9 GiB)
[    6.670723] sd 8:0:0:0: [sdb] Write Protect is off
[    6.670726] sd 8:0:0:0: [sdb] Mode Sense: 03 00 00 00
[    6.671739] sd 8:0:0:0: [sdb] No Caching mode page present
[    6.671744] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[    6.674607] sd 8:0:0:0: [sdb] No Caching mode page present
[    6.674611] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[    6.675373]  sdb: sdb1
[    6.678219] sd 8:0:0:0: [sdb] No Caching mode page present
[    6.678222] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[    6.678225] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[   11.696918] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
[   11.700976] alg: No test for __cbc-aes-aesni (cryptd(__driver-cbc-aes-aesni))
[   12.281553] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
[   12.519103] udevd[383]: starting version 175
[   12.613820] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4
[   12.613887] ACPI: Power Button [PWRB]
[   12.613971] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
[   12.614025] ACPI: Power Button [PWRF]
[   12.642090] wmi: Mapper loaded
[   12.690035] [drm] Initialized drm 1.1.0 20060810
[   12.704079] xen: registering gsi 16 triggering 0 polarity 1
[   12.704085] xen_map_pirq_gsi: returning irq 16 for gsi 16
[   12.704124] xen: --> pirq=16 -> irq=16 (gsi=16)
[   12.704126] Already setup the GSI :16
[   12.704162] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   12.704206] i915 0000:00:02.0: setting latency timer to 64
[   12.708839] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   12.787608] iTCO_vendor_support: vendor-support=0
[   12.789901] input: PC Speaker as /devices/platform/pcspkr/input/input6
[   12.790584] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[   12.790709] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
[   12.790826] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   12.840046] xen: registering gsi 17 triggering 0 polarity 1
[   12.840052] xen_map_pirq_gsi: returning irq 17 for gsi 17
[   12.840094] xen: --> pirq=17 -> irq=17 (gsi=17)
[   12.840096] Already setup the GSI :17
[   12.840133] snd_hda_intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[   12.840341] snd_hda_intel 0000:01:00.1: setting latency timer to 64
[   12.859279] [drm] MTRR allocation failed.  Graphics performance may suffer.
[   12.860494] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   12.860534] [drm] Driver supports precise vblank timestamp query.
[   12.860655] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   12.860711] vgaarb: transferring owner from PCI:0000:00:02.0 to PCI:0000:01:00.0
[   12.862947] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0
[   12.863090] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input7
[   13.612276] fbcon: inteldrmfb (fb0) is primary device
[   13.963639] Console: switching to colour frame buffer device 240x67
[   13.968804] fb0: inteldrmfb frame buffer device
[   13.968805] drm: registered panic notifier
[   13.968862] No ACPI video bus found
[   13.968947] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[   13.969118] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   13.969148] xen: registering gsi 18 triggering 0 polarity 1
[   13.969153] xen_map_pirq_gsi: returning irq 18 for gsi 18
[   13.969155] xen: --> pirq=18 -> irq=18 (gsi=18)
[   13.969158] Already setup the GSI :18
[   13.969162] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[   13.989840] xen: registering gsi 16 triggering 0 polarity 1
[   13.989845] xen_map_pirq_gsi: returning irq 16 for gsi 16
[   13.989884] xen: --> pirq=16 -> irq=16 (gsi=16)
[   13.989886] Already setup the GSI :16
[   13.989913] snd_virtuoso 0000:03:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   15.402645] EXT4-fs (dm-1): re-mounted. Opts: (null)
[   15.427729] EXT4-fs (dm-1): re-mounted. Opts: user_xattr,errors=remount-ro
[   15.545909] loop: module loaded
[   15.897001] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[   16.013167] Bridge firewalling registered
[   16.018223] device eth0 entered promiscuous mode
[   16.175369] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.179561] ADDRCONF(NETDEV_UP): br0: link is not ready
[   19.521036] tg3 0000:0d:00.0: eth0: Link is up at 1000 Mbps, full duplex
[   19.522594] tg3 0000:0d:00.0: eth0: Flow control is on for TX and on for RX
[   19.524132] tg3 0000:0d:00.0: eth0: EEE is disabled
[   19.526044] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   19.527574] br0: topology change detected, propagating
[   19.529089] br0: port 1(eth0) entering forwarding state
[   19.530602] br0: port 1(eth0) entering forwarding state
[   19.532428] ADDRCONF(NETDEV_CHANGE): br0: link becomes ready
[   22.386565] RPC: Registered named UNIX socket transport module.
[   22.388019] RPC: Registered udp transport module.
[   22.389468] RPC: Registered tcp transport module.
[   22.390908] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   22.398140] FS-Cache: Loaded
[   22.407133] FS-Cache: Netfs 'nfs' registered for caching
[   22.414252] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   23.390335] fuse init (API version 7.17)
[   24.114152] Bluetooth: Core ver 2.16
[   24.114172] NET: Registered protocol family 31
[   24.114173] Bluetooth: HCI device and connection manager initialized
[   24.114175] Bluetooth: HCI socket layer initialized
[   24.114176] Bluetooth: L2CAP socket layer initialized
[   24.114434] Bluetooth: SCO socket layer initialized
[   24.120979] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   24.120981] Bluetooth: BNEP filters: protocol multicast
[   24.560458] Bluetooth: RFCOMM TTY layer initialized
[   24.560463] Bluetooth: RFCOMM socket layer initialized
[   24.560464] Bluetooth: RFCOMM ver 1.11
[   26.160701] Event-channel device installed.
[   26.197393] XENBUS: Unable to read cpu state
[   26.197535] XENBUS: Unable to read cpu state
[   26.907888] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder 1
[   49.674327] FAT-fs (sdb1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[   80.418891] WARNING! power/level is deprecated; use power/control instead
[   80.496088] usb 3-1.4: USB disconnect, device number 3

[-- Attachment #3: xm_dmesg.txt --]
[-- Type: text/plain, Size: 5339 bytes --]

(XEN) Xen version 4.1.2 (Debian 4.1.2-2) (waldi@debian.org) (gcc version 4.6.2 (Debian 4.6.2-6) ) Sat Dec 10 19:58:21 UTC 2011
(XEN) Bootloader: GRUB 1.99-14
(XEN) Command line: placeholder dom0_max_vcpus=2 dom0_vcpus_pin dom0_mem=8192M
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009d800 (usable)
(XEN)  000000000009d800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000020000000 (usable)
(XEN)  0000000020000000 - 0000000020200000 (reserved)
(XEN)  0000000020200000 - 0000000040000000 (usable)
(XEN)  0000000040000000 - 0000000040200000 (reserved)
(XEN)  0000000040200000 - 000000006ed6d000 (usable)
(XEN)  000000006ed6d000 - 000000006edbc000 (ACPI NVS)
(XEN)  000000006edbc000 - 000000006edc5000 (ACPI data)
(XEN)  000000006edc5000 - 000000006edf2000 (reserved)
(XEN)  000000006edf2000 - 000000006edf3000 (usable)
(XEN)  000000006edf3000 - 000000006ee03000 (reserved)
(XEN)  000000006ee03000 - 000000006ee10000 (ACPI NVS)
(XEN)  000000006ee10000 - 000000006ee38000 (reserved)
(XEN)  000000006ee38000 - 000000006ee7b000 (ACPI NVS)
(XEN)  000000006ee7b000 - 000000006f000000 (usable)
(XEN)  000000006f800000 - 000000007fa00000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed40000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000047fe00000 (usable)
(XEN) ACPI: RSDP 000F0450, 0024 (r2 ALASKA)
(XEN) ACPI: XSDT 6EDBC070, 005C (r1 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: FACP 6EDC4158, 00F4 (r4 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: DSDT 6EDBC158, 7FFB (r2 ALASKA    A M I        0 INTL 20051117)
(XEN) ACPI: FACS 6EE07F80, 0040
(XEN) ACPI: APIC 6EDC4250, 0092 (r3 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: SSDT 6EDC42E8, 01D6 (r1 AMICPU     PROC        1 MSFT  3000001)
(XEN) ACPI: MCFG 6EDC44C0, 003C (r1 ALASKA    A M I  1072009 MSFT       97)
(XEN) ACPI: AAFT 6EDC4500, 00D3 (r1 ALASKA OEMAAFT   1072009 MSFT       97)
(XEN) ACPI: HPET 6EDC45D8, 0038 (r1 ALASKA    A M I  1072009 AMI.        4)
(XEN) ACPI: DMAR 6EDC4610, 00E8 (r1 ALASKA    A M I        1 INTL        1)
(XEN) System RAM: 16104MB (16491072kB)
(XEN) Domain heap initialised
(XEN) ACPI: 32/64X FACS address mismatch in FADT - 6ee07f80/0000000000000000, using 32
(XEN) Processor #0 6:10 APIC version 21
(XEN) Processor #2 6:10 APIC version 21
(XEN) Processor #4 6:10 APIC version 21
(XEN) Processor #6 6:10 APIC version 21
(XEN) Processor #1 6:10 APIC version 21
(XEN) Processor #3 6:10 APIC version 21
(XEN) Processor #5 6:10 APIC version 21
(XEN) Processor #7 6:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Table is not found!
(XEN) Switched to APIC driver x2apic_cluster.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3392.376 MHz processor.
(XEN) Initing memory sharing.
(XEN) Intel VT-d Snoop Control not 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 Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using old ACK method
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(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) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Brought up 8 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x193a000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000046c000000->0000000470000000 (2072334 pages to be allocated)
(XEN)  Init. ramdisk: 000000047dd0e000->000000047fdffe00
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff8193a000
(XEN)  Init. ramdisk: ffffffff8193a000->ffffffff83a2be00
(XEN)  Phys-Mach map: ffffffff83a2c000->ffffffff84a2c000
(XEN)  Start info:    ffffffff84a2c000->ffffffff84a2c4b4
(XEN)  Page tables:   ffffffff84a2d000->ffffffff84a56000
(XEN)  Boot stack:    ffffffff84a56000->ffffffff84a57000
(XEN)  TOTAL:         ffffffff80000000->ffffffff84c00000
(XEN)  ENTRY ADDRESS: ffffffff816a9200
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: .............................................................................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 216kB init memory.
(XEN) physdev.c:155: dom0: wrong map_pirq type 3

[-- Attachment #4: xm_info.txt --]
[-- Type: text/plain, Size: 1162 bytes --]

host                   : muaddib
release                : 3.2.0-1-amd64
version                : #1 SMP Sun Feb 5 15:17:15 UTC 2012
machine                : x86_64
nr_cpus                : 8
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 3392
hw_caps                : bfebfbff:28100800:00000000:00003f40:13bae3ff:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 16104
free_memory            : 10022
free_cpus              : 0
xen_major              : 4
xen_minor              : 1
xen_extra              : .2
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : placeholder dom0_max_vcpus=2 dom0_vcpus_pin dom0_mem=8192M
cc_compiler            : gcc version 4.6.2 (Debian 4.6.2-6) 
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Sat Dec 10 19:58:21 UTC 2011
xend_config_format     : 4

[-- Attachment #5: xm_list.txt --]
[-- Type: text/plain, Size: 159 bytes --]

Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  5866     2     r-----    117.0

[-- Attachment #6: 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] 19+ messages in thread

* Re: dom0 not seeing all of the assigned memory
  2012-02-22 22:19 dom0 not seeing all of the assigned memory Henrik Olsson
@ 2012-02-22 22:40 ` Henrik Olsson
  2012-02-23 18:55 ` David Vrabel
  1 sibling, 0 replies; 19+ messages in thread
From: Henrik Olsson @ 2012-02-22 22:40 UTC (permalink / raw)
  To: xen-devel

On Wed, Feb 22, 2012 at 23:19, Henrik Olsson <henrik@fixme.se> wrote:
> Hi, i'm having some trouble with assigning memory to my dom0.
>
> I've added "dom0_mem=8192M" to the xen command line yet "free -m"
> reports only 5686MB total.
>
> Running Xen 4.1.2 with kernel 3.2.0-1-amd64, debian testing.
>
> Attached are the outputs of dmesg, xm dmesg, xm info and xm list.
>
> Regards,
> Henrik Olsson

Forgot to mention, issuing xm mem-set changes what xm list says but not free.
root@muaddib:~# xm mem-set Domain-0 8192M
root@muaddib:~# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  8192     2     r-----    598.1
root@muaddib:~# free -m
             total       used       free     shared    buffers     cached
Mem:          5686       2133       3552          0         54        884

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

* Re: dom0 not seeing all of the assigned memory
  2012-02-22 22:19 dom0 not seeing all of the assigned memory Henrik Olsson
  2012-02-22 22:40 ` Henrik Olsson
@ 2012-02-23 18:55 ` David Vrabel
  2012-02-27 17:34   ` Henrik Olsson
  1 sibling, 1 reply; 19+ messages in thread
From: David Vrabel @ 2012-02-23 18:55 UTC (permalink / raw)
  To: Henrik Olsson; +Cc: xen-devel

On 22/02/12 22:19, Henrik Olsson wrote:
> Hi, i'm having some trouble with assigning memory to my dom0.
> 
> I've added "dom0_mem=8192M" to the xen command line yet "free -m"
> reports only 5686MB total.

[    0.000000] Freeing  6f000-100000 pfn range: 593920 pages freed
[    0.000000] 1-1 mapping on 6f000->100000
[    0.000000] Released 595312 pages of unused memory

This accounts for most of your "missing" memory.  To get it back you
need to adjust the balloon driver's target to the amount of memory you want.

David

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

* Re: dom0 not seeing all of the assigned memory
  2012-02-23 18:55 ` David Vrabel
@ 2012-02-27 17:34   ` Henrik Olsson
  2012-02-27 19:04     ` Roderick Colenbrander
  0 siblings, 1 reply; 19+ messages in thread
From: Henrik Olsson @ 2012-02-27 17:34 UTC (permalink / raw)
  To: David Vrabel; +Cc: xen-devel

On Thu, Feb 23, 2012 at 19:55, David Vrabel <dvrabel@cantab.net> wrote:
> On 22/02/12 22:19, Henrik Olsson wrote:
>> Hi, i'm having some trouble with assigning memory to my dom0.
>>
>> I've added "dom0_mem=8192M" to the xen command line yet "free -m"
>> reports only 5686MB total.
>
> [    0.000000] Freeing  6f000-100000 pfn range: 593920 pages freed
> [    0.000000] 1-1 mapping on 6f000->100000
> [    0.000000] Released 595312 pages of unused memory
>
> This accounts for most of your "missing" memory.  To get it back you
> need to adjust the balloon driver's target to the amount of memory you want.
>
> David

Hi, i'm not sure i understand..

I've configured /etc/xen/xend-config.sxp with:
(dom0-min-mem 8192)
(enable-dom0-ballooning no)

Shouldn't this disable ballooning? Or do i need to pass some parameter
somewhere?

Regards,
Henrik

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

* Re: dom0 not seeing all of the assigned memory
  2012-02-27 17:34   ` Henrik Olsson
@ 2012-02-27 19:04     ` Roderick Colenbrander
  2012-03-11 22:20       ` Sven Köhler
  0 siblings, 1 reply; 19+ messages in thread
From: Roderick Colenbrander @ 2012-02-27 19:04 UTC (permalink / raw)
  To: Henrik Olsson; +Cc: David Vrabel, xen-devel

On Mon, Feb 27, 2012 at 5:34 PM, Henrik Olsson <henrik@fixme.se> wrote:
> On Thu, Feb 23, 2012 at 19:55, David Vrabel <dvrabel@cantab.net> wrote:
>> On 22/02/12 22:19, Henrik Olsson wrote:
>>> Hi, i'm having some trouble with assigning memory to my dom0.
>>>
>>> I've added "dom0_mem=8192M" to the xen command line yet "free -m"
>>> reports only 5686MB total.
>>
>> [    0.000000] Freeing  6f000-100000 pfn range: 593920 pages freed
>> [    0.000000] 1-1 mapping on 6f000->100000
>> [    0.000000] Released 595312 pages of unused memory
>>
>> This accounts for most of your "missing" memory.  To get it back you
>> need to adjust the balloon driver's target to the amount of memory you want.
>>
>> David
>
> Hi, i'm not sure i understand..
>
> I've configured /etc/xen/xend-config.sxp with:
> (dom0-min-mem 8192)
> (enable-dom0-ballooning no)
>
> Shouldn't this disable ballooning? Or do i need to pass some parameter
> somewhere?
>
> Regards,
> Henrik
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Make sure you have added the following patch to your Xen if you are
using a recent >=3.1 kernel. Unfortunately it isn't in Xen 4.1.x, but
I guess it should be added to there:
http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/c56dd5eb0fa2

See if it helps.

Roderick

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

* Re: dom0 not seeing all of the assigned memory
  2012-02-27 19:04     ` Roderick Colenbrander
@ 2012-03-11 22:20       ` Sven Köhler
  2012-03-15 18:33         ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 19+ messages in thread
From: Sven Köhler @ 2012-03-11 22:20 UTC (permalink / raw)
  To: xen-devel

Am 27.02.2012 20:04, schrieb Roderick Colenbrander:
> On Mon, Feb 27, 2012 at 5:34 PM, Henrik Olsson <henrik@fixme.se> wrote:
>> On Thu, Feb 23, 2012 at 19:55, David Vrabel <dvrabel@cantab.net> wrote:
>>> On 22/02/12 22:19, Henrik Olsson wrote:
>>>> Hi, i'm having some trouble with assigning memory to my dom0.
>>>>
>>>> I've added "dom0_mem=8192M" to the xen command line yet "free -m"
>>>> reports only 5686MB total.
>>>
>>> [    0.000000] Freeing  6f000-100000 pfn range: 593920 pages freed
>>> [    0.000000] 1-1 mapping on 6f000->100000
>>> [    0.000000] Released 595312 pages of unused memory
>>>
>>> This accounts for most of your "missing" memory.  To get it back you
>>> need to adjust the balloon driver's target to the amount of memory you want.
>>>
>>> David
>>
>> Hi, i'm not sure i understand..
>>
>> I've configured /etc/xen/xend-config.sxp with:
>> (dom0-min-mem 8192)
>> (enable-dom0-ballooning no)
>>
>> Shouldn't this disable ballooning? Or do i need to pass some parameter
>> somewhere?

I have the same problem. I believe this also happens even if the
ballooning driver is disabled in dom0 kernel.

>> Regards,
>> Henrik
> 
> Make sure you have added the following patch to your Xen if you are
> using a recent >=3.1 kernel. Unfortunately it isn't in Xen 4.1.x, but
> I guess it should be added to there:
> http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/c56dd5eb0fa2
> 
> See if it helps.

I recompiled the hypervisor (this was a patch for the hypervisor,
right?) and dom0 only has around 413MB inspite of dom0_mem=512M
hypervisor parameter.

free shows 413MB straight after booting into dom0 (no xend, xenstored or
anything xen related stuff has started yet).


Regards,
  Sven

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-11 22:20       ` Sven Köhler
@ 2012-03-15 18:33         ` Konrad Rzeszutek Wilk
  2012-03-15 18:54           ` David Vrabel
  0 siblings, 1 reply; 19+ messages in thread
From: Konrad Rzeszutek Wilk @ 2012-03-15 18:33 UTC (permalink / raw)
  To: Sven Köhler, david.vrabel; +Cc: xen-devel

On Sun, Mar 11, 2012 at 11:20:02PM +0100, Sven Köhler wrote:
> Am 27.02.2012 20:04, schrieb Roderick Colenbrander:
> > On Mon, Feb 27, 2012 at 5:34 PM, Henrik Olsson <henrik@fixme.se> wrote:
> >> On Thu, Feb 23, 2012 at 19:55, David Vrabel <dvrabel@cantab.net> wrote:
> >>> On 22/02/12 22:19, Henrik Olsson wrote:
> >>>> Hi, i'm having some trouble with assigning memory to my dom0.
> >>>>
> >>>> I've added "dom0_mem=8192M" to the xen command line yet "free -m"
> >>>> reports only 5686MB total.
> >>>
> >>> [    0.000000] Freeing  6f000-100000 pfn range: 593920 pages freed
> >>> [    0.000000] 1-1 mapping on 6f000->100000
> >>> [    0.000000] Released 595312 pages of unused memory
> >>>
> >>> This accounts for most of your "missing" memory.  To get it back you
> >>> need to adjust the balloon driver's target to the amount of memory you want.
> >>>
> >>> David
> >>
> >> Hi, i'm not sure i understand..
> >>
> >> I've configured /etc/xen/xend-config.sxp with:
> >> (dom0-min-mem 8192)
> >> (enable-dom0-ballooning no)
> >>
> >> Shouldn't this disable ballooning? Or do i need to pass some parameter
> >> somewhere?
> 
> I have the same problem. I believe this also happens even if the
> ballooning driver is disabled in dom0 kernel.
> 
> >> Regards,
> >> Henrik
> > 
> > Make sure you have added the following patch to your Xen if you are
> > using a recent >=3.1 kernel. Unfortunately it isn't in Xen 4.1.x, but
> > I guess it should be added to there:
> > http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/c56dd5eb0fa2
> > 
> > See if it helps.
> 
> I recompiled the hypervisor (this was a patch for the hypervisor,
> right?) and dom0 only has around 413MB inspite of dom0_mem=512M
> hypervisor parameter.
> 
> free shows 413MB straight after booting into dom0 (no xend, xenstored or
> anything xen related stuff has started yet).

<sigh> So it sounds like that the kernel should balloon up the released
amount of memory. David, did we discuss this at some point and agreed that
was the proper way?

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-15 18:33         ` Konrad Rzeszutek Wilk
@ 2012-03-15 18:54           ` David Vrabel
  2012-03-15 20:07             ` Sven Köhler
  0 siblings, 1 reply; 19+ messages in thread
From: David Vrabel @ 2012-03-15 18:54 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel, Sven Köhler

On 15/03/12 18:33, Konrad Rzeszutek Wilk wrote:
> On Sun, Mar 11, 2012 at 11:20:02PM +0100, Sven Köhler wrote:
>> Am 27.02.2012 20:04, schrieb Roderick Colenbrander:
>>> On Mon, Feb 27, 2012 at 5:34 PM, Henrik Olsson <henrik@fixme.se> wrote:
>>>> On Thu, Feb 23, 2012 at 19:55, David Vrabel <dvrabel@cantab.net> wrote:
>>>>> On 22/02/12 22:19, Henrik Olsson wrote:
>>>>>> Hi, i'm having some trouble with assigning memory to my dom0.
>>>>>>
>>>>>> I've added "dom0_mem=8192M" to the xen command line yet "free -m"
>>>>>> reports only 5686MB total.
>>>>>
>>>>> [    0.000000] Freeing  6f000-100000 pfn range: 593920 pages freed
>>>>> [    0.000000] 1-1 mapping on 6f000->100000
>>>>> [    0.000000] Released 595312 pages of unused memory
>>>>>
>>>>> This accounts for most of your "missing" memory.  To get it back you
>>>>> need to adjust the balloon driver's target to the amount of memory you want.
>>>>>
>>>>> David
>>>>
>>>> Hi, i'm not sure i understand..
>>>>
>>>> I've configured /etc/xen/xend-config.sxp with:
>>>> (dom0-min-mem 8192)
>>>> (enable-dom0-ballooning no)
>>>>
>>>> Shouldn't this disable ballooning? Or do i need to pass some parameter
>>>> somewhere?
>>
>> I have the same problem. I believe this also happens even if the
>> ballooning driver is disabled in dom0 kernel.

Well, yes.  The balloon driver needs to be enabled and a new target set
to get back the memory released during boot.

>>> Make sure you have added the following patch to your Xen if you are
>>> using a recent >=3.1 kernel. Unfortunately it isn't in Xen 4.1.x, but
>>> I guess it should be added to there:
>>> http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/c56dd5eb0fa2
>>>
>>> See if it helps.
>>
>> I recompiled the hypervisor (this was a patch for the hypervisor,
>> right?) and dom0 only has around 413MB inspite of dom0_mem=512M
>> hypervisor parameter.

You need dom0_mem=max:512M

>> free shows 413MB straight after booting into dom0 (no xend, xenstored or
>> anything xen related stuff has started yet).

This case isn't because of the released memory (since 512M is well below
the MMIO holes that cause lots of released memory) but because page
tables are reserved to the amount of physical ram in the system.

> <sigh> So it sounds like that the kernel should balloon up the released
> amount of memory. David, did we discuss this at some point and agreed that
> was the proper way?

I don't remember discussing it but it's an interesting idea.  Let me
think about it.  It will need to work without the balloon driver (since
it might not exist).

David

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-15 18:54           ` David Vrabel
@ 2012-03-15 20:07             ` Sven Köhler
  2012-03-15 20:13               ` Ian Campbell
  2012-03-19 11:09               ` David Vrabel
  0 siblings, 2 replies; 19+ messages in thread
From: Sven Köhler @ 2012-03-15 20:07 UTC (permalink / raw)
  To: David Vrabel; +Cc: xen-devel, Konrad Rzeszutek Wilk

Am 15.03.2012 19:54, schrieb David Vrabel:
> On 15/03/12 18:33, Konrad Rzeszutek Wilk wrote:
>> On Sun, Mar 11, 2012 at 11:20:02PM +0100, Sven Köhler wrote:
>>>
>>> I have the same problem. I believe this also happens even if the
>>> ballooning driver is disabled in dom0 kernel.
> 
> Well, yes.  The balloon driver needs to be enabled and a new target set
> to get back the memory released during boot.

The dom0 releases pages and passes them back to the hypervisor?
But why does it do so in the first place?

>>>> Make sure you have added the following patch to your Xen if you are
>>>> using a recent >=3.1 kernel. Unfortunately it isn't in Xen 4.1.x, but
>>>> I guess it should be added to there:
>>>> http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/c56dd5eb0fa2
>>>>
>>>> See if it helps.
>>>
>>> I recompiled the hypervisor (this was a patch for the hypervisor,
>>> right?) and dom0 only has around 413MB inspite of dom0_mem=512M
>>> hypervisor parameter.
> 
> You need dom0_mem=max:512M

I can't find documentation on what that does. But if I had to make an
educated guess, I would assume that dom0_mem=max:512M sets an upper
bound on the memory that dom0 may consume. It sounds like, the
hypervisor may take memory away from dom0, so that dom0 drops below the
specified 512MB.

Here's what I want to do (and what I though that dom0_mem=512M would
actually do): I want dom0 to have _exactly_ 512MB of RAM. Neither less
nor more than that.

So what does dom0_mem=512M do? Does it set a lower bound?
Recommendation for dom0_mem=512M are all over the internet (even
wiki.xen.org) and it is often explained as statically assinging memory
to dom0 (which IMHO implies that 512M is both the upper and lower bound).

>>> free shows 413MB straight after booting into dom0 (no xend, xenstored or
>>> anything xen related stuff has started yet).
> 
> This case isn't because of the released memory (since 512M is well below
> the MMIO holes that cause lots of released memory) but because page
> tables are reserved to the amount of physical ram in the system.

OK, I understand. What I don't understand is why the kernel thinks why
it needs page tables for more than 512M.

>> <sigh> So it sounds like that the kernel should balloon up the released
>> amount of memory. David, did we discuss this at some point and agreed that
>> was the proper way?
> 
> I don't remember discussing it but it's an interesting idea.  Let me
> think about it.  It will need to work without the balloon driver (since
> it might not exist).

I'm not sure what you are discussing. Can you explain a little more?

I remember the good old times, kernel 2.6.18 and 2.6.38 with xen
patches, where free shows a total of 524620 kilobytes and xl list shows
512 megabytes, with dom0_mem=512M.
With 3.3, free shows a toal of 413920 and xl list shows 511 megabytes
for dom0.

Do you realize, that the numbers are very different? 524620 is very
close to 512 * 1024 while 413920 is very very different from 511 * 1024.


Regards,
  Sven

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-15 20:07             ` Sven Köhler
@ 2012-03-15 20:13               ` Ian Campbell
  2012-03-15 20:29                 ` Sven Köhler
  2012-03-19 11:09               ` David Vrabel
  1 sibling, 1 reply; 19+ messages in thread
From: Ian Campbell @ 2012-03-15 20:13 UTC (permalink / raw)
  To: Sven Köhler; +Cc: xen-devel, David Vrabel, Konrad Rzeszutek Wilk

On Thu, 2012-03-15 at 20:07 +0000, Sven Köhler wrote:
> Am 15.03.2012 19:54, schrieb David Vrabel:

> > You need dom0_mem=max:512M
> 
> I can't find documentation on what that does.

This option is documented in the source tree, and the in tree
documentation is published at:
http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html

Ian.

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-15 20:13               ` Ian Campbell
@ 2012-03-15 20:29                 ` Sven Köhler
  2012-03-15 21:55                   ` Ian Campbell
  0 siblings, 1 reply; 19+ messages in thread
From: Sven Köhler @ 2012-03-15 20:29 UTC (permalink / raw)
  To: Ian Campbell; +Cc: xen-devel, David Vrabel, Konrad Rzeszutek Wilk

Am 15.03.2012 21:13, schrieb Ian Campbell:
> On Thu, 2012-03-15 at 20:07 +0000, Sven Köhler wrote:
>> Am 15.03.2012 19:54, schrieb David Vrabel:
> 
>>> You need dom0_mem=max:512M
>>
>> I can't find documentation on what that does.
> 
> This option is documented in the source tree, and the in tree
> documentation is published at:
> http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html

Thanks for the link. That is very useful! Is there any path that leads
from http://www.xen.org/support/documentation.html to the page above in
case I forget the URL?

However: according to that documentation dom0_mem=512M implies
dom0_mem=max:512M. Or am I wrong?

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-15 20:29                 ` Sven Köhler
@ 2012-03-15 21:55                   ` Ian Campbell
  2012-03-15 22:09                     ` Sven Köhler
  0 siblings, 1 reply; 19+ messages in thread
From: Ian Campbell @ 2012-03-15 21:55 UTC (permalink / raw)
  To: Sven Köhler; +Cc: xen-devel, David Vrabel, Konrad Rzeszutek Wilk

On Thu, 2012-03-15 at 20:29 +0000, Sven Köhler wrote:
> Am 15.03.2012 21:13, schrieb Ian Campbell:
> > On Thu, 2012-03-15 at 20:07 +0000, Sven Köhler wrote:
> >> Am 15.03.2012 19:54, schrieb David Vrabel:
> > 
> >>> You need dom0_mem=max:512M
> >>
> >> I can't find documentation on what that does.
> > 
> > This option is documented in the source tree, and the in tree
> > documentation is published at:
> > http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html
> 
> Thanks for the link. That is very useful! Is there any path that leads
> from http://www.xen.org/support/documentation.html to the page above in
> case I forget the URL?

Click "Generated Xen 4.x Documentation" then "complete set of generated
documents here".

> However: according to that documentation dom0_mem=512M implies
> dom0_mem=max:512M. Or am I wrong?

Not if the machine only has 256M of RAM?

Ian.

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-15 21:55                   ` Ian Campbell
@ 2012-03-15 22:09                     ` Sven Köhler
  0 siblings, 0 replies; 19+ messages in thread
From: Sven Köhler @ 2012-03-15 22:09 UTC (permalink / raw)
  To: Ian Campbell; +Cc: xen-devel, David Vrabel, Konrad Rzeszutek Wilk

Am 15.03.2012 22:55, schrieb Ian Campbell:
> On Thu, 2012-03-15 at 20:29 +0000, Sven Köhler wrote:
>> However: according to that documentation dom0_mem=512M implies
>> dom0_mem=max:512M. Or am I wrong?
> 
> Not if the machine only has 256M of RAM?

My interpretation is that dom0_mem=512M  also implies dom0_mem=min:512M.
Not sure how the hypervisor deals with that, if the machine only has
256M of RAM.

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-15 20:07             ` Sven Köhler
  2012-03-15 20:13               ` Ian Campbell
@ 2012-03-19 11:09               ` David Vrabel
  2012-03-19 12:25                 ` Sven Köhler
  1 sibling, 1 reply; 19+ messages in thread
From: David Vrabel @ 2012-03-19 11:09 UTC (permalink / raw)
  To: Sven Köhler; +Cc: xen-devel, Konrad Rzeszutek Wilk

On 15/03/12 20:07, Sven Köhler wrote:
> Am 15.03.2012 19:54, schrieb David Vrabel:
>> On 15/03/12 18:33, Konrad Rzeszutek Wilk wrote:
>>> On Sun, Mar 11, 2012 at 11:20:02PM +0100, Sven Köhler wrote:
>>>>
>>>> I have the same problem. I believe this also happens even if the
>>>> ballooning driver is disabled in dom0 kernel.
>>
>> Well, yes.  The balloon driver needs to be enabled and a new target set
>> to get back the memory released during boot.
> 
> The dom0 releases pages and passes them back to the hypervisor?
> But why does it do so in the first place?

Because the pages are not accessible. They overlap with BIOS or device
memory.

Later kernels are better at releasing more pages than earlier ones and
so it may appear that the domain ends up with less pages but it really
has the same number of usable pages.

>>>>> Make sure you have added the following patch to your Xen if you are
>>>>> using a recent >=3.1 kernel. Unfortunately it isn't in Xen 4.1.x, but
>>>>> I guess it should be added to there:
>>>>> http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/c56dd5eb0fa2
>>>>>
>>>>> See if it helps.
>>>>
>>>> I recompiled the hypervisor (this was a patch for the hypervisor,
>>>> right?) and dom0 only has around 413MB inspite of dom0_mem=512M
>>>> hypervisor parameter.
>>
>> You need dom0_mem=max:512M
> 
> I can't find documentation on what that does. But if I had to make an
> educated guess, I would assume that dom0_mem=max:512M sets an upper
> bound on the memory that dom0 may consume. It sounds like, the
> hypervisor may take memory away from dom0, so that dom0 drops below the
> specified 512MB.

The documentation isn't great. dom0_mem sets two memory related limits:
a) the initial number of pages; and b) the maximum possible number of
pages (maximum reservation).

Without the 'max:' option, the maximum reservation is unlimited.

Since 3.0.5, Linux has used the minimum of the maximum reservation and
the total amount of physical RAM to size its page tables etc.

David

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-19 11:09               ` David Vrabel
@ 2012-03-19 12:25                 ` Sven Köhler
  2012-03-19 12:30                   ` Fantu
  0 siblings, 1 reply; 19+ messages in thread
From: Sven Köhler @ 2012-03-19 12:25 UTC (permalink / raw)
  To: David Vrabel; +Cc: xen-devel, Konrad Rzeszutek Wilk


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

Am 19.03.2012 12:09, schrieb David Vrabel:
> On 15/03/12 20:07, Sven Köhler wrote:
>> Am 15.03.2012 19:54, schrieb David Vrabel:
>>> On 15/03/12 18:33, Konrad Rzeszutek Wilk wrote:
>>>> On Sun, Mar 11, 2012 at 11:20:02PM +0100, Sven Köhler wrote:
>>>>>
>>>>> I have the same problem. I believe this also happens even if the
>>>>> ballooning driver is disabled in dom0 kernel.
>>>
>>> Well, yes.  The balloon driver needs to be enabled and a new target set
>>> to get back the memory released during boot.
>>
>> The dom0 releases pages and passes them back to the hypervisor?
>> But why does it do so in the first place?
> 
> Because the pages are not accessible. They overlap with BIOS or device
> memory.
> 
> Later kernels are better at releasing more pages than earlier ones and
> so it may appear that the domain ends up with less pages but it really
> has the same number of usable pages.

This all makes sense. But I don't have the feeling, this is a proper
explanation of what I'm seeing.

"xl list" shows that dom0 is still at 511M. If the pages were really
released back to the hypervisor, then "xl list" should show an amount of
memory somewhere near the the value that "free" shows. But this isn't
the case. Was it wrong when I said that the pages are passed back to the
hypervisor?

>>>>>> Make sure you have added the following patch to your Xen if you are
>>>>>> using a recent >=3.1 kernel. Unfortunately it isn't in Xen 4.1.x, but
>>>>>> I guess it should be added to there:
>>>>>> http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/c56dd5eb0fa2
>>>>>>
>>>>>> See if it helps.
>>>>>
>>>>> I recompiled the hypervisor (this was a patch for the hypervisor,
>>>>> right?) and dom0 only has around 413MB inspite of dom0_mem=512M
>>>>> hypervisor parameter.
>>>
>>> You need dom0_mem=max:512M
>>
>> I can't find documentation on what that does. But if I had to make an
>> educated guess, I would assume that dom0_mem=max:512M sets an upper
>> bound on the memory that dom0 may consume. It sounds like, the
>> hypervisor may take memory away from dom0, so that dom0 drops below the
>> specified 512MB.
> 
> The documentation isn't great. dom0_mem sets two memory related limits:
> a) the initial number of pages; and b) the maximum possible number of
> pages (maximum reservation).

As far as I can see, there are three variables here:
- the initial amount of pages that dom0 gets
- the minimal amount of pages that dom0 should have
- the maximal amount of pages that dom0 can have

Please please fix the documentation!

Rumors about what dom0_mem=X does are spreading. And most pages I found
said that it would statically assign memory to dom0. What you're saying
sounds like dom0 is still allowed to grow if one does only use
dom0_mem=X but not dom0_mem=max:X - which is more dynamic than static.

> Without the 'max:' option, the maximum reservation is unlimited.
> 
> Since 3.0.5, Linux has used the minimum of the maximum reservation and
> the total amount of physical RAM to size its page tables etc.

I tried dom0_mem=max:512M as far as I remember. And it didn't improve
the situation (kernel 3.2.10). Also, when dom0 is booting without xen,
the amount of memory shown by free was not nearly as far away from the
amount of physical ram as when dom0 is booting with xen and dom0_mem=...

Something still smells fishy to me!

Anyway: I hope some of the developers have reproduced the problem and
are about to fix it.


Regards,
  Sven


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

[-- Attachment #2: 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] 19+ messages in thread

* Re: dom0 not seeing all of the assigned memory
  2012-03-19 12:25                 ` Sven Köhler
@ 2012-03-19 12:30                   ` Fantu
  2012-04-17  4:33                     ` Brian Szymanski
  0 siblings, 1 reply; 19+ messages in thread
From: Fantu @ 2012-03-19 12:30 UTC (permalink / raw)
  To: xen-devel

Also with Wheezy, upstream kernel (amd64 debian package) and xen-unstable
there is the same problem.

--
View this message in context: http://xen.1045712.n5.nabble.com/dom0-not-seeing-all-of-the-assigned-memory-tp5506459p5576960.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

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

* Re: dom0 not seeing all of the assigned memory
  2012-03-19 12:30                   ` Fantu
@ 2012-04-17  4:33                     ` Brian Szymanski
  2012-04-17  4:46                       ` Brian Szymanski
  0 siblings, 1 reply; 19+ messages in thread
From: Brian Szymanski @ 2012-04-17  4:33 UTC (permalink / raw)
  To: xen-devel

I'm having this problem in a vanillla debian squeeze install, too:

ski@xen:~$ dpkg -l | grep -e linux-image -e hypervisor | grep xen
ii  linux-image-2.6.32-5-xen-amd64          2.6.32-41squeeze2           
Linux 2.6.32 for 64-bit PCs, Xen dom0 support
ii  linux-image-xen-amd64                   2.6.32+29                   
Linux for 64-bit PCs (meta-package), Xen dom0 support
ii  xen-hypervisor-4.0-amd64                4.0.1-4                      The
Xen Hypervisor on AMD64

ski@xen:~$ free -m
             total       used       free     shared    buffers     cached
Mem:          4373       2478       1895          0         16         79
-/+ buffers/cache:       2382       1991
Swap:         3814          0       3814

ski@xen:~$ sudo xm info
host                   : xen.allafrica.com
release                : 2.6.32-5-xen-amd64
version                : #1 SMP Thu Mar 22 21:14:26 UTC 2012
machine                : x86_64
nr_cpus                : 8
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2493
hw_caps                :
bfebfbff:20100800:00000000:00000940:000ce3bd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 32762
free_memory            : 29280
node_to_cpu            : node0:0-7
node_to_memory         : node0:29280
node_to_dma32_mem      : node0:1974
max_node_id            : 0
xen_major              : 4
xen_minor              : 0
xen_extra              : .1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : placeholder com1=57600,8n1,0x2f8,3 console=com1,vga
loglvl=all guest_loglvl=all dom0_mem=max:6144M
cc_compiler            : gcc version 4.4.5 (Debian 4.4.5-8) 
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Thu Jun  9 18:38:03 UTC 2011
xend_config_format     : 4

Cheers.


--
View this message in context: http://xen.1045712.n5.nabble.com/dom0-not-seeing-all-of-the-assigned-memory-tp5506459p5645610.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

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

* Re: dom0 not seeing all of the assigned memory
  2012-04-17  4:33                     ` Brian Szymanski
@ 2012-04-17  4:46                       ` Brian Szymanski
  2012-04-17 21:30                         ` Dan Magenheimer
  0 siblings, 1 reply; 19+ messages in thread
From: Brian Szymanski @ 2012-04-17  4:46 UTC (permalink / raw)
  To: xen-devel

Also, if I xm mem-set Domain-0 6144, xm list is updated to the new value, but
xm top continues to show the old (even after restarting it).




--
View this message in context: http://xen.1045712.n5.nabble.com/dom0-not-seeing-all-of-the-assigned-memory-tp5506459p5645620.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

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

* Re: dom0 not seeing all of the assigned memory
  2012-04-17  4:46                       ` Brian Szymanski
@ 2012-04-17 21:30                         ` Dan Magenheimer
  0 siblings, 0 replies; 19+ messages in thread
From: Dan Magenheimer @ 2012-04-17 21:30 UTC (permalink / raw)
  To: Brian Szymanski, xen-devel

> From: Brian Szymanski [mailto:skibrianski@gmail.com]
> Subject: Re: [Xen-devel] dom0 not seeing all of the assigned memory
> 
> Also, if I xm mem-set Domain-0 6144, xm list is updated to the new value, but
> xm top continues to show the old (even after restarting it).

This is a very old annoying bug in xm.  It is especially
noticeable when a tmem-savvy guest (with selfballooning)
is enabled.  With xm now deprecated, it may never get fixed.

I'm told it is fixed with "xl".  If not, please report it.

Thanks,
Dan

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

end of thread, other threads:[~2012-04-17 21:30 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-02-22 22:19 dom0 not seeing all of the assigned memory Henrik Olsson
2012-02-22 22:40 ` Henrik Olsson
2012-02-23 18:55 ` David Vrabel
2012-02-27 17:34   ` Henrik Olsson
2012-02-27 19:04     ` Roderick Colenbrander
2012-03-11 22:20       ` Sven Köhler
2012-03-15 18:33         ` Konrad Rzeszutek Wilk
2012-03-15 18:54           ` David Vrabel
2012-03-15 20:07             ` Sven Köhler
2012-03-15 20:13               ` Ian Campbell
2012-03-15 20:29                 ` Sven Köhler
2012-03-15 21:55                   ` Ian Campbell
2012-03-15 22:09                     ` Sven Köhler
2012-03-19 11:09               ` David Vrabel
2012-03-19 12:25                 ` Sven Köhler
2012-03-19 12:30                   ` Fantu
2012-04-17  4:33                     ` Brian Szymanski
2012-04-17  4:46                       ` Brian Szymanski
2012-04-17 21:30                         ` Dan Magenheimer

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.