Hi Sydney, Thanks for all the info. I'd like to have the initscript work sensibly in this scenario at some point (not for Jessie though, it's too late now) so I think we may as well keep this bug around to track that since it already contains a bunch of useful information.
Thanks, Ian. On Tue, 2014-12-30 at 00:39 +0100, Sydney Meyer wrote: > Hello Ian, > > i´ve tried to install "xen-linux-system-amd64" on a VMware host again and > everything went fine. The Installation completes and i can boot into Xen und > boot up the Dom0. > > So, you were right. It seems to be a problem with the initscript, but as far > as i can tell, only when running xen under xen. > > To me, this specific issue is resolved, since the meta-package seems to > install just fine, apart when running under Xen, which would be another, > separate issue I think. > > But then again, since Nested Virtualization is experimental on almost every > platform, this is no problem to me or to my usecase. > > Anyhow, if you still would like to take a deeper look, i'm happy to help out > whereever i can, otherwise, you can mark this bug as resolved. > > Cheers, > S. > > > On 30 Dec 2014, at 00:20, Sydney Meyer <syd.me...@gmail.com> wrote: > > > >> > >> On 23 Dec 2014, at 12:59, Ian Campbell <i...@debian.org> wrote: > >> > >> Control: reassign -1 xen-utils-common 4.4.1-6 > >> Control: retitle -1 /etc/init.d/xen fails when run in a guest, causing > >> postinst to fail. > >> > >> Seems like this issue is in the Xen packages not in the xen-linux-system > >> metapackage, so reassigning. > >> > >> On Mon, 2014-12-22 at 23:01 +0100, Sydney Meyer wrote: > >>>> On 22 Dec 2014, at 17:25, Ian Campbell <i...@debian.org> wrote: > >>>> > >>>> On Sat, 2014-12-20 at 20:46 +0100, Sydney Meyer wrote: > >>>>> Hello Ian, > >>>>> > >>>>> "systemctl status xen.service" gives: > >>>> > >>>> Thanks. Sadly these logs weren't as informative a I had hoped they would > >>>> be :-/ (In case it's not clear: this is not your fault) > >>>> > >>>>> root@jessie:/home/sydney# systemctl status xen.service > >>>>> ● xen.service - LSB: Xen daemons > >>>>> Loaded: loaded (/etc/init.d/xen) > >>>>> Active: failed (Result: exit-code) since Sat 2014-12-20 20:42:30 CET; > >>>>> 11s ago > >>>>> Process: 4796 ExecStart=/etc/init.d/xen start (code=exited, status=255) > >>>>> > >>>>> Dec 20 20:42:30 jessie xen[4796]: Starting Xen daemons: xenfs (warning). > >>>>> Dec 20 20:42:30 jessie systemd[1]: xen.service: control process exited, > >>>>> code=exited status=255 > >>>>> Dec 20 20:42:30 jessie systemd[1]: Failed to start LSB: Xen daemons. > >>>>> Dec 20 20:42:30 jessie systemd[1]: Unit xen.service entered failed > >>>>> state. > >>>> > >>>> This basically says "it failed", which isn't terribly helpful! > >>>> > >>>> I think it is complaining because it couldn't mount xenfs, but it > >>>> doesn't say why. > >>>> > >>>> If you run "/etc/init.d/xen start" from the root command line does it > >>>> say something more informative/useful? > >>> > >>> No, it fails and refers to systemctl/journalctl: > >> > >> OK. > >>> > >>> root@jessie:/home/sydney# /etc/init.d/xen start > >>> [....] Starting xen (via systemctl): xen.serviceJob for xen.service > >>> failed. See 'systemctl status xen.service' and 'journalctl -xn' for > >>> details. > >>> failed! > >>>> > >>>> Could you also try running /usr/lib/xen-common/bin/xen-dir > >>>> and /usr/lib/xen-common/bin/xen-toolstack by hand (also as root). > >>> > >>> root@jessie:/home/sydney# /usr/lib/xen-common/bin/xen-dir > >>> /usr/lib/xen-4.4 > >>> > >>> root@jessie:/home/sydney# /usr/lib/xen-common/bin/xen-toolstack > >>> /usr/lib/xen-4.4/bin/xl > >> > >> Thanks, so it thinks it is running under Xen (which given what you say > >> below makes sense). > >> > >> What (if anything) does "mount -t xenfs xenfs /proc/xen" report? > >> Does /proc/xen exist? > > > > root@xen:/home/sydney# mount -t xenfs xenfs /proc/xen > > mount: xenfs is already mounted or /proc/xen busy > > xenfs is already mounted on /proc/xen > >> > >>> Yes, this particular output is from a Xen DomU with vmx enabled. The > >>> Dom0 is running Xen 4.4.1 compiled from source on a Debian Linux > >>> 3.16.2 Kernel. > >> > >> Thanks, this would have been good to know up front. I suppose you are > >> wanting to do some sort of nested virtualisation? > > > > actually no, this was just for testing purposes, I never expected the > > Hypervisor to do any real work. > > > >> You are likely the > >> first to try this with the Debian packaging, and nested virt generally > >> is considered tech preview upstream, so I'd expect there to be some > >> wrinkles in doing this. > >> > >> By "with vmx enabled" I guess you mean with nestedhvm=1 in the guest > >> cfg? Are you running this in a PV or HVM guest (I think HVM)? Can you > >> post the dmesg from the kernel please, along with the guest cfg file. > > > > root@intel:/home/sydney# cat xencfg/xen.cfg > > name='xen' > > builder="hvm" > > vnc=1 > > vncdisplay=84 > > vncpasswd="test" > > keymap="de" > > vcpus = 1 > > memory = "2048" > > hap=1 > > nestedhvm=1 > > disk = [ > > 'phy:/dev/vgssd/xen,xvda,w', > > ] > > vif = [ > > 'mac=00:16:3E:8B:84:CC,bridge=br0.6', > > ] > > > > > > > > root@xen:/home/sydney# journalctl -k --boot > > -- Logs begin at Mon 2014-12-29 23:55:59 CET, end at Mon 2014-12-29 > > 23:58:24 CET. -- > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys cpuset > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys cpu > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys cpuacct > > Dec 29 23:55:59 xen kernel: Linux version 3.16.0-4-amd64 > > (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-16) ) #1 > > SMP Debian 3.16.7-ckt2-1 (2014-12-08) > > Dec 29 23:55:59 xen kernel: Command line: > > BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/xen--vg-root ro quiet > > Dec 29 23:55:59 xen kernel: e820: BIOS-provided physical RAM map: > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x0000000000000000-0x000000000009fbff] usable > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x000000000009fc00-0x000000000009ffff] reserved > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x00000000000f0000-0x00000000000fffff] reserved > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x0000000000100000-0x000000007f7fefff] usable > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x000000007f7ff000-0x000000007f7fffff] reserved > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x00000000fc000000-0x00000000ffffffff] reserved > > Dec 29 23:55:59 xen kernel: NX (Execute Disable) protection: active > > Dec 29 23:55:59 xen kernel: SMBIOS 2.4 present. > > Dec 29 23:55:59 xen kernel: DMI: Xen HVM domU, BIOS 4.4.1 09/03/2014 > > Dec 29 23:55:59 xen kernel: Hypervisor detected: Xen HVM > > Dec 29 23:55:59 xen kernel: Xen version 4.4. > > Dec 29 23:55:59 xen kernel: Xen Platform PCI: I/O protocol version 1 > > Dec 29 23:55:59 xen kernel: Netfront and the Xen platform PCI driver have > > been compiled for this kernel: unplug emulated NICs. > > Dec 29 23:55:59 xen kernel: Blkfront and the Xen platform PCI driver have > > been compiled for this kernel: unplug emulated disks. > > You might have to change the root device > > from /dev/hd[a-d] to /dev/xvd[a-d] > > in your root= kernel command line option > > Dec 29 23:55:59 xen kernel: HVMOP_pagetable_dying not supported > > Dec 29 23:55:59 xen kernel: e820: update [mem 0x00000000-0x00000fff] usable > > ==> reserved > > Dec 29 23:55:59 xen kernel: e820: remove [mem 0x000a0000-0x000fffff] usable > > Dec 29 23:55:59 xen kernel: AGP: No AGP bridge found > > Dec 29 23:55:59 xen kernel: e820: last_pfn = 0x7f7ff max_arch_pfn = > > 0x400000000 > > Dec 29 23:55:59 xen kernel: MTRR default type: write-back > > Dec 29 23:55:59 xen kernel: MTRR fixed ranges enabled: > > Dec 29 23:55:59 xen kernel: 00000-9FFFF write-back > > Dec 29 23:55:59 xen kernel: A0000-BFFFF write-combining > > Dec 29 23:55:59 xen kernel: C0000-FFFFF write-back > > Dec 29 23:55:59 xen kernel: MTRR variable ranges enabled: > > Dec 29 23:55:59 xen kernel: 0 base 00F0000000 mask 7FF8000000 uncachable > > Dec 29 23:55:59 xen kernel: 1 base 00F8000000 mask 7FFC000000 uncachable > > Dec 29 23:55:59 xen kernel: 2 disabled > > Dec 29 23:55:59 xen kernel: 3 disabled > > root@xen:/home/sydney# journalctl -k --boot | cat dmesg.txt > > cat: dmesg.txt: No such file or directory > > root@xen:/home/sydney# journalctl -k --boot | cat > dmesg.txt > > root@xen:/home/sydney# cat dmesg.txt > > -- Logs begin at Mon 2014-12-29 23:55:59 CET, end at Mon 2014-12-29 > > 23:58:24 CET. -- > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys cpuset > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys cpu > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys cpuacct > > Dec 29 23:55:59 xen kernel: Linux version 3.16.0-4-amd64 > > (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-16) ) #1 > > SMP Debian 3.16.7-ckt2-1 (2014-12-08) > > Dec 29 23:55:59 xen kernel: Command line: > > BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/xen--vg-root ro quiet > > Dec 29 23:55:59 xen kernel: e820: BIOS-provided physical RAM map: > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x0000000000000000-0x000000000009fbff] usable > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x000000000009fc00-0x000000000009ffff] reserved > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x00000000000f0000-0x00000000000fffff] reserved > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x0000000000100000-0x000000007f7fefff] usable > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x000000007f7ff000-0x000000007f7fffff] reserved > > Dec 29 23:55:59 xen kernel: BIOS-e820: [mem > > 0x00000000fc000000-0x00000000ffffffff] reserved > > Dec 29 23:55:59 xen kernel: NX (Execute Disable) protection: active > > Dec 29 23:55:59 xen kernel: SMBIOS 2.4 present. > > Dec 29 23:55:59 xen kernel: DMI: Xen HVM domU, BIOS 4.4.1 09/03/2014 > > Dec 29 23:55:59 xen kernel: Hypervisor detected: Xen HVM > > Dec 29 23:55:59 xen kernel: Xen version 4.4. > > Dec 29 23:55:59 xen kernel: Xen Platform PCI: I/O protocol version 1 > > Dec 29 23:55:59 xen kernel: Netfront and the Xen platform PCI driver have > > been compiled for this kernel: unplug emulated NICs. > > Dec 29 23:55:59 xen kernel: Blkfront and the Xen platform PCI driver have > > been compiled for this kernel: unplug emulated disks. > > You might have to change the root device > > from /dev/hd[a-d] to /dev/xvd[a-d] > > in your root= kernel command line option > > Dec 29 23:55:59 xen kernel: HVMOP_pagetable_dying not supported > > Dec 29 23:55:59 xen kernel: e820: update [mem 0x00000000-0x00000fff] usable > > ==> reserved > > Dec 29 23:55:59 xen kernel: e820: remove [mem 0x000a0000-0x000fffff] usable > > Dec 29 23:55:59 xen kernel: AGP: No AGP bridge found > > Dec 29 23:55:59 xen kernel: e820: last_pfn = 0x7f7ff max_arch_pfn = > > 0x400000000 > > Dec 29 23:55:59 xen kernel: MTRR default type: write-back > > Dec 29 23:55:59 xen kernel: MTRR fixed ranges enabled: > > Dec 29 23:55:59 xen kernel: 00000-9FFFF write-back > > Dec 29 23:55:59 xen kernel: A0000-BFFFF write-combining > > Dec 29 23:55:59 xen kernel: C0000-FFFFF write-back > > Dec 29 23:55:59 xen kernel: MTRR variable ranges enabled: > > Dec 29 23:55:59 xen kernel: 0 base 00F0000000 mask 7FF8000000 uncachable > > Dec 29 23:55:59 xen kernel: 1 base 00F8000000 mask 7FFC000000 uncachable > > Dec 29 23:55:59 xen kernel: 2 disabled > > Dec 29 23:55:59 xen kernel: 3 disabled > > Dec 29 23:55:59 xen kernel: 4 disabled > > Dec 29 23:55:59 xen kernel: 5 disabled > > Dec 29 23:55:59 xen kernel: 6 disabled > > Dec 29 23:55:59 xen kernel: 7 disabled > > Dec 29 23:55:59 xen kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, > > new 0x7010600070106 > > Dec 29 23:55:59 xen kernel: found SMP MP-table at [mem > > 0x000f1760-0x000f176f] mapped at [ffff8800000f1760] > > Dec 29 23:55:59 xen kernel: Base memory trampoline at [ffff880000099000] > > 99000 size 24576 > > Dec 29 23:55:59 xen kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] > > Dec 29 23:55:59 xen kernel: [mem 0x00000000-0x000fffff] page 4k > > Dec 29 23:55:59 xen kernel: BRK [0x01af3000, 0x01af3fff] PGTABLE > > Dec 29 23:55:59 xen kernel: BRK [0x01af4000, 0x01af4fff] PGTABLE > > Dec 29 23:55:59 xen kernel: BRK [0x01af5000, 0x01af5fff] PGTABLE > > Dec 29 23:55:59 xen kernel: init_memory_mapping: [mem 0x7f400000-0x7f5fffff] > > Dec 29 23:55:59 xen kernel: [mem 0x7f400000-0x7f5fffff] page 2M > > Dec 29 23:55:59 xen kernel: BRK [0x01af6000, 0x01af6fff] PGTABLE > > Dec 29 23:55:59 xen kernel: init_memory_mapping: [mem 0x7c000000-0x7f3fffff] > > Dec 29 23:55:59 xen kernel: [mem 0x7c000000-0x7f3fffff] page 2M > > Dec 29 23:55:59 xen kernel: init_memory_mapping: [mem 0x00100000-0x7bffffff] > > Dec 29 23:55:59 xen kernel: [mem 0x00100000-0x001fffff] page 4k > > Dec 29 23:55:59 xen kernel: [mem 0x00200000-0x7bffffff] page 2M > > Dec 29 23:55:59 xen kernel: init_memory_mapping: [mem 0x7f600000-0x7f7fefff] > > Dec 29 23:55:59 xen kernel: [mem 0x7f600000-0x7f7fefff] page 4k > > Dec 29 23:55:59 xen kernel: BRK [0x01af7000, 0x01af7fff] PGTABLE > > Dec 29 23:55:59 xen kernel: RAMDISK: [mem 0x362f8000-0x37173fff] > > Dec 29 23:55:59 xen kernel: ACPI: Early table checksum verification disabled > > Dec 29 23:55:59 xen kernel: ACPI: RSDP 0x00000000000F16B0 000024 (v02 Xen > > ) > > Dec 29 23:55:59 xen kernel: ACPI: XSDT 0x00000000FC009F70 000054 (v01 Xen > > HVM 00000000 HVML 00000000) > > Dec 29 23:55:59 xen kernel: ACPI: FACP 0x00000000FC0098A0 0000F4 (v04 Xen > > HVM 00000000 HVML 00000000) > > Dec 29 23:55:59 xen kernel: ACPI: DSDT 0x00000000FC001250 0085CD (v02 Xen > > HVM 00000000 INTL 20100528) > > Dec 29 23:55:59 xen kernel: ACPI: FACS 0x00000000FC001210 000040 > > Dec 29 23:55:59 xen kernel: ACPI: APIC 0x00000000FC0099A0 000460 (v02 Xen > > HVM 00000000 HVML 00000000) > > Dec 29 23:55:59 xen kernel: ACPI: HPET 0x00000000FC009E80 000038 (v01 Xen > > HVM 00000000 HVML 00000000) > > Dec 29 23:55:59 xen kernel: ACPI: WAET 0x00000000FC009EC0 000028 (v01 Xen > > HVM 00000000 HVML 00000000) > > Dec 29 23:55:59 xen kernel: ACPI: SSDT 0x00000000FC009EF0 000031 (v02 Xen > > HVM 00000000 INTL 20100528) > > Dec 29 23:55:59 xen kernel: ACPI: SSDT 0x00000000FC009F30 000031 (v02 Xen > > HVM 00000000 INTL 20100528) > > Dec 29 23:55:59 xen kernel: ACPI: Local APIC address 0xfee00000 > > Dec 29 23:55:59 xen kernel: No NUMA configuration found > > Dec 29 23:55:59 xen kernel: Faking a node at [mem > > 0x0000000000000000-0x000000007f7fefff] > > Dec 29 23:55:59 xen kernel: Initmem setup node 0 [mem 0x00000000-0x7f7fefff] > > Dec 29 23:55:59 xen kernel: NODE_DATA [mem 0x7f7fa000-0x7f7fefff] > > Dec 29 23:55:59 xen kernel: [ffffea0000000000-ffffea0001bfffff] PMD -> > > [ffff88007ce00000-ffff88007e9fffff] on node 0 > > Dec 29 23:55:59 xen kernel: Zone ranges: > > Dec 29 23:55:59 xen kernel: DMA [mem 0x00001000-0x00ffffff] > > Dec 29 23:55:59 xen kernel: DMA32 [mem 0x01000000-0xffffffff] > > Dec 29 23:55:59 xen kernel: Normal empty > > Dec 29 23:55:59 xen kernel: Movable zone start for each node > > Dec 29 23:55:59 xen kernel: Early memory node ranges > > Dec 29 23:55:59 xen kernel: node 0: [mem 0x00001000-0x0009efff] > > Dec 29 23:55:59 xen kernel: node 0: [mem 0x00100000-0x7f7fefff] > > Dec 29 23:55:59 xen kernel: On node 0 totalpages: 522141 > > Dec 29 23:55:59 xen kernel: DMA zone: 56 pages used for memmap > > Dec 29 23:55:59 xen kernel: DMA zone: 21 pages reserved > > Dec 29 23:55:59 xen kernel: DMA zone: 3998 pages, LIFO batch:0 > > Dec 29 23:55:59 xen kernel: DMA32 zone: 7084 pages used for memmap > > Dec 29 23:55:59 xen kernel: DMA32 zone: 518143 pages, LIFO batch:31 > > Dec 29 23:55:59 xen kernel: ACPI: PM-Timer IO Port: 0xb008 > > Dec 29 23:55:59 xen kernel: ACPI: Local APIC address 0xfee00000 > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] > > enabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x08] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x0a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x0c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x0e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x09] lapic_id[0x12] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x14] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x16] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x18] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x1a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x1c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x1e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x11] lapic_id[0x22] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x12] lapic_id[0x24] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x13] lapic_id[0x26] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x14] lapic_id[0x28] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x15] lapic_id[0x2a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x16] lapic_id[0x2c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x17] lapic_id[0x2e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x18] lapic_id[0x30] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x19] lapic_id[0x32] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x34] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x36] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x38] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x20] lapic_id[0x40] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x21] lapic_id[0x42] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x22] lapic_id[0x44] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x23] lapic_id[0x46] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x24] lapic_id[0x48] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x25] lapic_id[0x4a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x26] lapic_id[0x4c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x27] lapic_id[0x4e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x28] lapic_id[0x50] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x29] lapic_id[0x52] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x2a] lapic_id[0x54] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x2b] lapic_id[0x56] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x2c] lapic_id[0x58] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x2d] lapic_id[0x5a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x2e] lapic_id[0x5c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x2f] lapic_id[0x5e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x30] lapic_id[0x60] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x31] lapic_id[0x62] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x32] lapic_id[0x64] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x33] lapic_id[0x66] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x34] lapic_id[0x68] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x35] lapic_id[0x6a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x36] lapic_id[0x6c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x37] lapic_id[0x6e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x38] lapic_id[0x70] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x39] lapic_id[0x72] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x3a] lapic_id[0x74] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x3b] lapic_id[0x76] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x3c] lapic_id[0x78] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x3d] lapic_id[0x7a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x3e] lapic_id[0x7c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x3f] lapic_id[0x7e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x40] lapic_id[0x80] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x41] lapic_id[0x82] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x42] lapic_id[0x84] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x43] lapic_id[0x86] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x44] lapic_id[0x88] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x45] lapic_id[0x8a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x46] lapic_id[0x8c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x47] lapic_id[0x8e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x48] lapic_id[0x90] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x49] lapic_id[0x92] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x4a] lapic_id[0x94] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x4b] lapic_id[0x96] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x4c] lapic_id[0x98] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x4d] lapic_id[0x9a] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x4e] lapic_id[0x9c] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x4f] lapic_id[0x9e] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x50] lapic_id[0xa0] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x51] lapic_id[0xa2] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x52] lapic_id[0xa4] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x53] lapic_id[0xa6] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x54] lapic_id[0xa8] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x55] lapic_id[0xaa] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x56] lapic_id[0xac] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x57] lapic_id[0xae] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x58] lapic_id[0xb0] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x59] lapic_id[0xb2] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x5a] lapic_id[0xb4] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x5b] lapic_id[0xb6] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x5c] lapic_id[0xb8] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x5d] lapic_id[0xba] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x5e] lapic_id[0xbc] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x5f] lapic_id[0xbe] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x60] lapic_id[0xc0] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x61] lapic_id[0xc2] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x62] lapic_id[0xc4] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x63] lapic_id[0xc6] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x64] lapic_id[0xc8] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x65] lapic_id[0xca] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x66] lapic_id[0xcc] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x67] lapic_id[0xce] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x68] lapic_id[0xd0] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x69] lapic_id[0xd2] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x6a] lapic_id[0xd4] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x6b] lapic_id[0xd6] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x6c] lapic_id[0xd8] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x6d] lapic_id[0xda] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x6e] lapic_id[0xdc] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x6f] lapic_id[0xde] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x70] lapic_id[0xe0] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x71] lapic_id[0xe2] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x72] lapic_id[0xe4] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x73] lapic_id[0xe6] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x74] lapic_id[0xe8] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x75] lapic_id[0xea] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x76] lapic_id[0xec] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x77] lapic_id[0xee] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x78] lapic_id[0xf0] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x79] lapic_id[0xf2] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x7a] lapic_id[0xf4] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x7b] lapic_id[0xf6] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x7c] lapic_id[0xf8] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x7d] lapic_id[0xfa] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x7e] lapic_id[0xfc] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: LAPIC (acpi_id[0x7f] lapic_id[0xfe] > > disabled) > > Dec 29 23:55:59 xen kernel: ACPI: IOAPIC (id[0x01] address[0xfec00000] > > gsi_base[0]) > > Dec 29 23:55:59 xen kernel: IOAPIC[0]: apic_id 1, version 17, address > > 0xfec00000, GSI 0-47 > > Dec 29 23:55:59 xen kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 > > dfl dfl) > > Dec 29 23:55:59 xen kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 > > low level) > > Dec 29 23:55:59 xen kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq > > 10 low level) > > Dec 29 23:55:59 xen kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq > > 11 low level) > > Dec 29 23:55:59 xen kernel: ACPI: IRQ0 used by override. > > Dec 29 23:55:59 xen kernel: ACPI: IRQ2 used by override. > > Dec 29 23:55:59 xen kernel: ACPI: IRQ5 used by override. > > Dec 29 23:55:59 xen kernel: ACPI: IRQ9 used by override. > > Dec 29 23:55:59 xen kernel: ACPI: IRQ10 used by override. > > Dec 29 23:55:59 xen kernel: ACPI: IRQ11 used by override. > > Dec 29 23:55:59 xen kernel: Using ACPI (MADT) for SMP configuration > > information > > Dec 29 23:55:59 xen kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000 > > Dec 29 23:55:59 xen kernel: smpboot: Allowing 128 CPUs, 127 hotplug CPUs > > Dec 29 23:55:59 xen kernel: nr_irqs_gsi: 64 > > Dec 29 23:55:59 xen kernel: PM: Registered nosave memory: [mem > > 0x0009f000-0x0009ffff] > > Dec 29 23:55:59 xen kernel: PM: Registered nosave memory: [mem > > 0x000a0000-0x000effff] > > Dec 29 23:55:59 xen kernel: PM: Registered nosave memory: [mem > > 0x000f0000-0x000fffff] > > Dec 29 23:55:59 xen kernel: e820: [mem 0x7f800000-0xfbffffff] available for > > PCI devices > > Dec 29 23:55:59 xen kernel: Booting paravirtualized kernel on Xen HVM > > Dec 29 23:55:59 xen kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 > > nr_cpu_ids:128 nr_node_ids:1 > > Dec 29 23:55:59 xen kernel: PERCPU: Embedded 27 pages/cpu @ffff88007be00000 > > s81792 r8192 d20608 u131072 > > Dec 29 23:55:59 xen kernel: pcpu-alloc: s81792 r8192 d20608 u131072 > > alloc=1*2097152 > > Dec 29 23:55:59 xen kernel: pcpu-alloc: [0] 000 001 002 003 004 005 006 007 > > 008 009 010 011 012 013 014 015 > > Dec 29 23:55:59 xen kernel: pcpu-alloc: [0] 016 017 018 019 020 021 022 023 > > 024 025 026 027 028 029 030 031 > > Dec 29 23:55:59 xen kernel: pcpu-alloc: [0] 032 033 034 035 036 037 038 039 > > 040 041 042 043 044 045 046 047 > > Dec 29 23:55:59 xen kernel: pcpu-alloc: [0] 048 049 050 051 052 053 054 055 > > 056 057 058 059 060 061 062 063 > > Dec 29 23:55:59 xen kernel: pcpu-alloc: [0] 064 065 066 067 068 069 070 071 > > 072 073 074 075 076 077 078 079 > > Dec 29 23:55:59 xen kernel: pcpu-alloc: [0] 080 081 082 083 084 085 086 087 > > 088 089 090 091 092 093 094 095 > > Dec 29 23:55:59 xen kernel: pcpu-alloc: [0] 096 097 098 099 100 101 102 103 > > 104 105 106 107 108 109 110 111 > > Dec 29 23:55:59 xen kernel: pcpu-alloc: [0] 112 113 114 115 116 117 118 119 > > 120 121 122 123 124 125 126 127 > > Dec 29 23:55:59 xen kernel: Built 1 zonelists in Node order, mobility > > grouping on. Total pages: 514980 > > Dec 29 23:55:59 xen kernel: Policy zone: DMA32 > > Dec 29 23:55:59 xen kernel: Kernel command line: > > BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/xen--vg-root ro quiet > > Dec 29 23:55:59 xen kernel: PID hash table entries: 4096 (order: 3, 32768 > > bytes) > > Dec 29 23:55:59 xen kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 > > Dec 29 23:55:59 xen kernel: AGP: Checking aperture... > > Dec 29 23:55:59 xen kernel: AGP: No AGP bridge found > > Dec 29 23:55:59 xen kernel: Calgary: detecting Calgary via BIOS EBDA area > > Dec 29 23:55:59 xen kernel: Calgary: Unable to locate Rio Grande table in > > EBDA - bailing! > > Dec 29 23:55:59 xen kernel: Memory: 2019640K/2088564K available (5192K > > kernel code, 942K rwdata, 1828K rodata, 1200K init, 840K bss, 68924K > > reserved) > > Dec 29 23:55:59 xen kernel: Hierarchical RCU implementation. > > Dec 29 23:55:59 xen kernel: RCU dyntick-idle grace-period > > acceleration is enabled. > > Dec 29 23:55:59 xen kernel: RCU restricting CPUs from NR_CPUS=512 > > to nr_cpu_ids=128. > > Dec 29 23:55:59 xen kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, > > nr_cpu_ids=128 > > Dec 29 23:55:59 xen kernel: NR_IRQS:33024 nr_irqs:2112 16 > > Dec 29 23:55:59 xen kernel: xen:events: Using FIFO-based ABI > > Dec 29 23:55:59 xen kernel: xen:events: Xen HVM callback vector for event > > delivery is enabled > > Dec 29 23:55:59 xen kernel: Console: colour VGA+ 80x25 > > Dec 29 23:55:59 xen kernel: console [tty0] enabled > > Dec 29 23:55:59 xen kernel: hpet clockevent registered > > Dec 29 23:55:59 xen kernel: tsc: Detected 2900.062 MHz processor > > Dec 29 23:55:59 xen kernel: Calibrating delay loop (skipped), value > > calculated using timer frequency.. 5800.12 BogoMIPS (lpj=11600248) > > Dec 29 23:55:59 xen kernel: pid_max: default: 131072 minimum: 1024 > > Dec 29 23:55:59 xen kernel: ACPI: Core revision 20140424 > > Dec 29 23:55:59 xen kernel: ACPI: All ACPI Tables successfully acquired > > Dec 29 23:55:59 xen kernel: Security Framework initialized > > Dec 29 23:55:59 xen kernel: AppArmor: AppArmor disabled by boot time > > parameter > > Dec 29 23:55:59 xen kernel: Yama: disabled by default; enable with sysctl > > kernel.yama.* > > Dec 29 23:55:59 xen kernel: Dentry cache hash table entries: 262144 (order: > > 9, 2097152 bytes) > > Dec 29 23:55:59 xen kernel: Inode-cache hash table entries: 131072 (order: > > 8, 1048576 bytes) > > Dec 29 23:55:59 xen kernel: Mount-cache hash table entries: 4096 (order: 3, > > 32768 bytes) > > Dec 29 23:55:59 xen kernel: Mountpoint-cache hash table entries: 4096 > > (order: 3, 32768 bytes) > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys memory > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys devices > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys freezer > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys net_cls > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys blkio > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys perf_event > > Dec 29 23:55:59 xen kernel: Initializing cgroup subsys net_prio > > Dec 29 23:55:59 xen kernel: CPU: Physical Processor ID: 0 > > Dec 29 23:55:59 xen kernel: CPU: Processor Core ID: 0 > > Dec 29 23:55:59 xen kernel: mce: CPU supports 2 MCE banks > > Dec 29 23:55:59 xen kernel: Last level iTLB entries: 4KB 1024, 2MB 1024, > > 4MB 1024 > > Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB > > 1024, 1GB 4 > > tlb_flushall_shift: 6 > > Dec 29 23:55:59 xen kernel: ftrace: allocating 21561 entries in 85 pages > > Dec 29 23:55:59 xen kernel: Switched APIC routing to physical flat. > > Dec 29 23:55:59 xen kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 > > pin2=0 > > Dec 29 23:55:59 xen kernel: smpboot: CPU0: Intel(R) Core(TM) i3-4130T CPU @ > > 2.90GHz (fam: 06, model: 3c, stepping: 03) > > Dec 29 23:55:59 xen kernel: Xen: using vcpuop timer interface > > Dec 29 23:55:59 xen kernel: installing Xen timer for CPU 0 > > Dec 29 23:55:59 xen kernel: Performance Events: unsupported p6 CPU model 60 > > no PMU driver, software events only. > > Dec 29 23:55:59 xen kernel: x86: Booted up 1 node, 1 CPUs > > Dec 29 23:55:59 xen kernel: smpboot: Total of 1 processors activated > > (5800.12 BogoMIPS) > > Dec 29 23:55:59 xen kernel: devtmpfs: initialized > > Dec 29 23:55:59 xen kernel: pinctrl core: initialized pinctrl subsystem > > Dec 29 23:55:59 xen kernel: NET: Registered protocol family 16 > > Dec 29 23:55:59 xen kernel: NMI watchdog: disabled (cpu0): hardware events > > not enabled > > Dec 29 23:55:59 xen kernel: xenbus: xs_reset_watches failed: -38 > > Dec 29 23:55:59 xen kernel: cpuidle: using governor ladder > > Dec 29 23:55:59 xen kernel: cpuidle: using governor menu > > Dec 29 23:55:59 xen kernel: ACPI: bus type PCI registered > > Dec 29 23:55:59 xen kernel: acpiphp: ACPI Hot Plug PCI Controller Driver > > version: 0.5 > > Dec 29 23:55:59 xen kernel: PCI: Using configuration type 1 for base access > > Dec 29 23:55:59 xen kernel: ACPI: Added _OSI(Module Device) > > Dec 29 23:55:59 xen kernel: ACPI: Added _OSI(Processor Device) > > Dec 29 23:55:59 xen kernel: ACPI: Added _OSI(3.0 _SCP Extensions) > > Dec 29 23:55:59 xen kernel: ACPI: Added _OSI(Processor Aggregator Device) > > Dec 29 23:55:59 xen kernel: ACPI: Interpreter enabled > > Dec 29 23:55:59 xen kernel: ACPI Exception: AE_NOT_FOUND, While evaluating > > Sleep State [\_S1_] (20140424/hwxface-580) > > Dec 29 23:55:59 xen kernel: ACPI Exception: AE_NOT_FOUND, While evaluating > > Sleep State [\_S2_] (20140424/hwxface-580) > > Dec 29 23:55:59 xen kernel: ACPI: (supports S0 S3 S4 S5) > > Dec 29 23:55:59 xen kernel: ACPI: Using IOAPIC for interrupt routing > > Dec 29 23:55:59 xen kernel: PCI: Using host bridge windows from ACPI; if > > necessary, use "pci=nocrs" and report a bug > > Dec 29 23:55:59 xen kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus > > 00-ff]) > > Dec 29 23:55:59 xen kernel: acpi PNP0A03:00: _OSC: OS supports [ASPM > > ClockPM Segments MSI] > > Dec 29 23:55:59 xen kernel: acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); > > disabling ASPM > > Dec 29 23:55:59 xen kernel: acpi PNP0A03:00: fail to add MMCONFIG > > information, can't access extended PCI configuration space under this > > bridge. > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [3] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [4] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [5] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [6] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [7] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [8] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [9] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [10] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [11] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [12] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [13] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [14] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [15] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [16] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [17] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [18] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [19] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [20] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [21] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [22] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [23] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [24] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [25] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [26] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [27] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [28] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [29] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [30] registered > > Dec 29 23:55:59 xen kernel: acpiphp: Slot [31] registered > > Dec 29 23:55:59 xen kernel: PCI host bridge to bus 0000:00 > > Dec 29 23:55:59 xen kernel: pci_bus 0000:00: root bus resource [bus 00-ff] > > Dec 29 23:55:59 xen kernel: pci_bus 0000:00: root bus resource [io > > 0x0000-0x0cf7] > > Dec 29 23:55:59 xen kernel: pci_bus 0000:00: root bus resource [io > > 0x0d00-0xffff] > > Dec 29 23:55:59 xen kernel: pci_bus 0000:00: root bus resource [mem > > 0x000a0000-0x000bffff] > > Dec 29 23:55:59 xen kernel: pci_bus 0000:00: root bus resource [mem > > 0xf0000000-0xfbffffff] > > Dec 29 23:55:59 xen kernel: pci 0000:00:00.0: [8086:1237] type 00 class > > 0x060000 > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.0: [8086:7000] type 00 class > > 0x060100 > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.1: [8086:7010] type 00 class > > 0x010180 > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.1: reg 0x20: [io 0xc200-0xc20f] > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.1: legacy IDE quirk: reg 0x10: > > [io 0x01f0-0x01f7] > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.1: legacy IDE quirk: reg 0x14: > > [io 0x03f6] > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.1: legacy IDE quirk: reg 0x18: > > [io 0x0170-0x0177] > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: > > [io 0x0376] > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.3: [8086:7113] type 00 class > > 0x068000 > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.3: quirk: [io 0xb000-0xb03f] > > claimed by PIIX4 ACPI > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.3: quirk: [io 0xb100-0xb10f] > > claimed by PIIX4 SMB > > Dec 29 23:55:59 xen kernel: pci 0000:00:02.0: [5853:0001] type 00 class > > 0xff8000 > > Dec 29 23:55:59 xen kernel: pci 0000:00:02.0: reg 0x10: [io 0xc000-0xc0ff] > > Dec 29 23:55:59 xen kernel: pci 0000:00:02.0: reg 0x14: [mem > > 0xf2000000-0xf2ffffff pref] > > Dec 29 23:55:59 xen kernel: pci 0000:00:03.0: [1013:00b8] type 00 class > > 0x030000 > > Dec 29 23:55:59 xen kernel: pci 0000:00:03.0: reg 0x10: [mem > > 0xf0000000-0xf1ffffff pref] > > Dec 29 23:55:59 xen kernel: pci 0000:00:03.0: reg 0x14: [mem > > 0xf3050000-0xf3050fff] > > Dec 29 23:55:59 xen kernel: pci 0000:00:03.0: reg 0x30: [mem > > 0xf3040000-0xf304ffff pref] > > Dec 29 23:55:59 xen kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs *5 10 11) > > Dec 29 23:55:59 xen kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11) > > Dec 29 23:55:59 xen kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11) > > Dec 29 23:55:59 xen kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *5 10 11) > > Dec 29 23:55:59 xen kernel: ACPI: Enabled 2 GPEs in block 00 to 0F > > Dec 29 23:55:59 xen kernel: xen:balloon: Initialising balloon driver > > Dec 29 23:55:59 xen kernel: xen_balloon: Initialising balloon driver > > Dec 29 23:55:59 xen kernel: init_memory_mapping: [mem 0x80000000-0x87ffffff] > > Dec 29 23:55:59 xen kernel: [mem 0x80000000-0x87ffffff] page 2M > > Dec 29 23:55:59 xen kernel: vgaarb: setting as boot device: PCI:0000:00:03.0 > > Dec 29 23:55:59 xen kernel: vgaarb: device added: > > PCI:0000:00:03.0,decodes=io+mem,owns=io+mem,locks=none > > Dec 29 23:55:59 xen kernel: vgaarb: loaded > > Dec 29 23:55:59 xen kernel: vgaarb: bridge control possible 0000:00:03.0 > > Dec 29 23:55:59 xen kernel: PCI: Using ACPI for IRQ routing > > Dec 29 23:55:59 xen kernel: PCI: pci_cache_line_size set to 64 bytes > > Dec 29 23:55:59 xen kernel: e820: reserve RAM buffer [mem > > 0x0009fc00-0x0009ffff] > > Dec 29 23:55:59 xen kernel: e820: reserve RAM buffer [mem > > 0x7f7ff000-0x7fffffff] > > Dec 29 23:55:59 xen kernel: HPET: 3 timers in total, 0 timers will be used > > for per-cpu timer > > Dec 29 23:55:59 xen kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 > > Dec 29 23:55:59 xen kernel: hpet0: 3 comparators, 64-bit 62.500000 MHz > > counter > > Dec 29 23:55:59 xen kernel: Switched to clocksource xen > > Dec 29 23:55:59 xen kernel: pnp: PnP ACPI init > > Dec 29 23:55:59 xen kernel: ACPI: bus type PNP registered > > Dec 29 23:55:59 xen kernel: system 00:00: [mem 0x00000000-0x0009ffff] could > > not be reserved > > Dec 29 23:55:59 xen kernel: system 00:00: Plug and Play ACPI device, IDs > > PNP0c02 (active) > > Dec 29 23:55:59 xen kernel: system 00:01: [io 0x08a0-0x08a3] has been > > reserved > > Dec 29 23:55:59 xen kernel: system 00:01: [io 0x0cc0-0x0ccf] has been > > reserved > > Dec 29 23:55:59 xen kernel: system 00:01: [io 0x04d0-0x04d1] has been > > reserved > > Dec 29 23:55:59 xen kernel: system 00:01: Plug and Play ACPI device, IDs > > PNP0c02 (active) > > Dec 29 23:55:59 xen kernel: xen: --> pirq=16 -> irq=8 (gsi=8) > > Dec 29 23:55:59 xen kernel: pnp 00:02: Plug and Play ACPI device, IDs > > PNP0b00 (active) > > Dec 29 23:55:59 xen kernel: xen: --> pirq=17 -> irq=12 (gsi=12) > > Dec 29 23:55:59 xen kernel: pnp 00:03: Plug and Play ACPI device, IDs > > PNP0f13 (active) > > Dec 29 23:55:59 xen kernel: xen: --> pirq=18 -> irq=1 (gsi=1) > > Dec 29 23:55:59 xen kernel: pnp 00:04: Plug and Play ACPI device, IDs > > PNP0303 PNP030b (active) > > Dec 29 23:55:59 xen kernel: xen: --> pirq=19 -> irq=6 (gsi=6) > > Dec 29 23:55:59 xen kernel: pnp 00:05: [dma 2] > > Dec 29 23:55:59 xen kernel: pnp 00:05: Plug and Play ACPI device, IDs > > PNP0700 (active) > > Dec 29 23:55:59 xen kernel: system 00:06: [io 0xae00-0xae0f] has been > > reserved > > Dec 29 23:55:59 xen kernel: system 00:06: [io 0xb044-0xb047] has been > > reserved > > Dec 29 23:55:59 xen kernel: system 00:06: Plug and Play ACPI device, IDs > > PNP0c02 (active) > > Dec 29 23:55:59 xen kernel: pnp: PnP ACPI: found 7 devices > > Dec 29 23:55:59 xen kernel: ACPI: bus type PNP unregistered > > Dec 29 23:55:59 xen kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7] > > Dec 29 23:55:59 xen kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff] > > Dec 29 23:55:59 xen kernel: pci_bus 0000:00: resource 6 [mem > > 0x000a0000-0x000bffff] > > Dec 29 23:55:59 xen kernel: pci_bus 0000:00: resource 7 [mem > > 0xf0000000-0xfbffffff] > > Dec 29 23:55:59 xen kernel: NET: Registered protocol family 2 > > Dec 29 23:55:59 xen kernel: TCP established hash table entries: 16384 > > (order: 5, 131072 bytes) > > Dec 29 23:55:59 xen kernel: TCP bind hash table entries: 16384 (order: 6, > > 262144 bytes) > > Dec 29 23:55:59 xen kernel: TCP: Hash tables configured (established 16384 > > bind 16384) > > Dec 29 23:55:59 xen kernel: TCP: reno registered > > Dec 29 23:55:59 xen kernel: UDP hash table entries: 1024 (order: 3, 32768 > > bytes) > > Dec 29 23:55:59 xen kernel: UDP-Lite hash table entries: 1024 (order: 3, > > 32768 bytes) > > Dec 29 23:55:59 xen kernel: NET: Registered protocol family 1 > > Dec 29 23:55:59 xen kernel: pci 0000:00:00.0: Limiting direct PCI/PCI > > transfers > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.0: PIIX3: Enabling Passive > > Release > > Dec 29 23:55:59 xen kernel: pci 0000:00:01.0: Activating ISA DMA hang > > workarounds > > Dec 29 23:55:59 xen kernel: pci 0000:00:03.0: Video device with shadowed ROM > > Dec 29 23:55:59 xen kernel: PCI: CLS 0 bytes, default 64 > > Dec 29 23:55:59 xen kernel: Unpacking initramfs... > > Dec 29 23:55:59 xen kernel: Freeing initrd memory: 14832K (ffff8800362f8000 > > - ffff880037174000) > > Dec 29 23:55:59 xen kernel: RAPL PMU detected, hw unit 2^-14 Joules, API > > unit is 2^-32 Joules, 4 fixed counters 655360 ms ovfl timer > > Dec 29 23:55:59 xen kernel: microcode: CPU0 sig=0x306c3, pf=0x2, > > revision=0x12 > > Dec 29 23:55:59 xen kernel: microcode: Microcode Update Driver: v2.00 > > <tig...@aivazian.fsnet.co.uk>, Peter Oruba > > Dec 29 23:55:59 xen kernel: futex hash table entries: 32768 (order: 9, > > 2097152 bytes) > > Dec 29 23:55:59 xen kernel: audit: initializing netlink subsys (disabled) > > Dec 29 23:55:59 xen kernel: audit: type=2000 audit(1419893758.380:1): > > initialized > > Dec 29 23:55:59 xen kernel: HugeTLB registered 2 MB page size, > > pre-allocated 0 pages > > Dec 29 23:55:59 xen kernel: zbud: loaded > > Dec 29 23:55:59 xen kernel: VFS: Disk quotas dquot_6.5.2 > > Dec 29 23:55:59 xen kernel: Dquot-cache hash table entries: 512 (order 0, > > 4096 bytes) > > Dec 29 23:55:59 xen kernel: msgmni has been set to 3973 > > Dec 29 23:55:59 xen kernel: alg: No test for stdrng (krng) > > Dec 29 23:55:59 xen kernel: Block layer SCSI generic (bsg) driver version > > 0.4 loaded (major 252) > > Dec 29 23:55:59 xen kernel: io scheduler noop registered > > Dec 29 23:55:59 xen kernel: io scheduler deadline registered > > Dec 29 23:55:59 xen kernel: io scheduler cfq registered (default) > > Dec 29 23:55:59 xen kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > > Dec 29 23:55:59 xen kernel: pciehp: PCI Express Hot Plug Controller Driver > > version: 0.4 > > Dec 29 23:55:59 xen kernel: intel_idle: does not run on family 6 model 60 > > Dec 29 23:55:59 xen kernel: GHES: HEST is not enabled! > > Dec 29 23:55:59 xen kernel: xen: --> pirq=20 -> irq=24 (gsi=24) > > Dec 29 23:55:59 xen kernel: xen:grant_table: Grant tables using version 1 > > layout > > Dec 29 23:55:59 xen kernel: Grant table initialized > > Dec 29 23:55:59 xen kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing > > enabled > > Dec 29 23:55:59 xen kernel: Linux agpgart interface v0.103 > > Dec 29 23:55:59 xen kernel: i8042: PNP: PS/2 Controller > > [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 > > Dec 29 23:55:59 xen kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 > > Dec 29 23:55:59 xen kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 > > Dec 29 23:55:59 xen kernel: mousedev: PS/2 mouse device common for all mice > > Dec 29 23:55:59 xen kernel: input: AT Translated Set 2 keyboard as > > /devices/platform/i8042/serio0/input/input0 > > Dec 29 23:55:59 xen kernel: input: Xen Virtual Keyboard as > > /devices/virtual/input/input2 > > Dec 29 23:55:59 xen kernel: input: Xen Virtual Pointer as > > /devices/virtual/input/input3 > > Dec 29 23:55:59 xen kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos > > as rtc0 > > Dec 29 23:55:59 xen kernel: rtc_cmos 00:02: alarms up to one day, 114 bytes > > nvram, hpet irqs > > Dec 29 23:55:59 xen kernel: ledtrig-cpu: registered to indicate activity on > > CPUs > > Dec 29 23:55:59 xen kernel: ioremap error for 0xfc001000-0xfc002000, > > requested 0x10, got 0x0 > > Dec 29 23:55:59 xen kernel: AMD IOMMUv2 driver by Joerg Roedel > > <joerg.roe...@amd.com> > > Dec 29 23:55:59 xen kernel: AMD IOMMUv2 functionality not available on this > > system > > Dec 29 23:55:59 xen kernel: TCP: cubic registered > > Dec 29 23:55:59 xen kernel: NET: Registered protocol family 10 > > Dec 29 23:55:59 xen kernel: mip6: Mobile IPv6 > > Dec 29 23:55:59 xen kernel: NET: Registered protocol family 17 > > Dec 29 23:55:59 xen kernel: mpls_gso: MPLS GSO support > > Dec 29 23:55:59 xen kernel: registered taskstats version 1 > > Dec 29 23:55:59 xen kernel: xenbus_probe_frontend: Device with no driver: > > device/vbd/51712 > > Dec 29 23:55:59 xen kernel: xenbus_probe_frontend: Device with no driver: > > device/vif/0 > > Dec 29 23:55:59 xen kernel: rtc_cmos 00:02: setting system clock to > > 2014-12-29 22:55:58 UTC (1419893758) > > Dec 29 23:55:59 xen kernel: PM: Hibernation image not present or could not > > be loaded. > > Dec 29 23:55:59 xen kernel: Freeing unused kernel memory: 1200K > > (ffffffff818ed000 - ffffffff81a19000) > > Dec 29 23:55:59 xen kernel: Write protecting the kernel read-only data: > > 8192k > > Dec 29 23:55:59 xen kernel: Freeing unused kernel memory: 940K > > (ffff880001515000 - ffff880001600000) > > Dec 29 23:55:59 xen kernel: Freeing unused kernel memory: 220K > > (ffff8800017c9000 - ffff880001800000) > > Dec 29 23:55:59 xen systemd-udevd[55]: starting version 215 > > Dec 29 23:55:59 xen kernel: random: systemd-udevd urandom read with 5 bits > > of entropy available > > Dec 29 23:55:59 xen kernel: SCSI subsystem initialized > > Dec 29 23:55:59 xen kernel: libata version 3.00 loaded. > > Dec 29 23:55:59 xen kernel: ata_piix 0000:00:01.1: version 2.13 > > Dec 29 23:55:59 xen kernel: scsi0 : ata_piix > > Dec 29 23:55:59 xen kernel: scsi1 : ata_piix > > Dec 29 23:55:59 xen kernel: ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma > > 0xc200 irq 14 > > Dec 29 23:55:59 xen kernel: ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma > > 0xc208 irq 15 > > Dec 29 23:55:59 xen kernel: xen_netfront: Initialising Xen virtual ethernet > > driver > > Dec 29 23:55:59 xen kernel: FDC 0 is a S82078B > > Dec 29 23:55:59 xen kernel: blkfront: xvda: flush diskcache: enabled; > > persistent grants: enabled; indirect descriptors: enabled; > > Dec 29 23:55:59 xen kernel: xvda: xvda1 xvda2 < xvda5 > > > Dec 29 23:55:59 xen kernel: device-mapper: uevent: version 1.0.3 > > Dec 29 23:55:59 xen kernel: device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) > > initialised: dm-de...@redhat.com > > Dec 29 23:55:59 xen kernel: PM: Starting manual resume from disk > > Dec 29 23:55:59 xen kernel: PM: Hibernation image partition 254:1 present > > Dec 29 23:55:59 xen kernel: PM: Looking for hibernation image. > > Dec 29 23:55:59 xen kernel: PM: Image not found (code -22) > > Dec 29 23:55:59 xen kernel: PM: Hibernation image not present or could not > > be loaded. > > Dec 29 23:55:59 xen kernel: EXT4-fs (dm-0): mounted filesystem with ordered > > data mode. Opts: (null) > > Dec 29 23:55:59 xen systemd[1]: Cannot add dependency job for unit > > display-manager.service, ignoring: Unit display-manager.service failed to > > load: No such file or directory. > > Dec 29 23:55:59 xen systemd-udevd[153]: starting version 215 > > Dec 29 23:55:59 xen kernel: input: Power Button as > > /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 > > Dec 29 23:55:59 xen kernel: ACPI: Power Button [PWRF] > > Dec 29 23:55:59 xen kernel: input: Sleep Button as > > /devices/LNXSYSTM:00/LNXSLPBN:00/input/input5 > > Dec 29 23:55:59 xen kernel: ACPI: Sleep Button [SLPF] > > Dec 29 23:55:59 xen kernel: piix4_smbus 0000:00:01.3: SMBus Host Controller > > not enabled! > > Dec 29 23:55:59 xen kernel: [drm] Initialized drm 1.1.0 20060810 > > Dec 29 23:55:59 xen kernel: input: PC Speaker as > > /devices/platform/pcspkr/input/input6 > > Dec 29 23:55:59 xen kernel: AVX2 version of gcm_enc/dec engaged. > > Dec 29 23:55:59 xen kernel: ppdev: user-space parallel port driver > > Dec 29 23:55:59 xen kernel: alg: No test for __gcm-aes-aesni > > (__driver-gcm-aes-aesni) > > Dec 29 23:55:59 xen kernel: alg: No test for crc32 (crc32-pclmul) > > Dec 29 23:55:59 xen kernel: Adding 471036k swap on > > /dev/mapper/xen--vg-swap_1. Priority:-1 extents:1 across:471036k SSFS > > Dec 29 23:55:59 xen kernel: EXT4-fs (dm-0): re-mounted. Opts: > > errors=remount-ro > > Dec 29 23:55:59 xen kernel: tsc: Refined TSC clocksource calibration: > > 2899.997 MHz > > Dec 29 23:56:00 xen kernel: input: ImExPS/2 Generic Explorer Mouse as > > /devices/platform/i8042/serio1/input/input7 > > Dec 29 23:56:02 xen kernel: EXT4-fs (xvda1): mounting ext2 file system > > using the ext4 subsystem > > Dec 29 23:56:02 xen kernel: EXT4-fs (xvda1): mounted filesystem without > > journal. Opts: (null) > > Dec 29 23:56:08 xen kernel: random: nonblocking pool is initialized > > Dec 29 23:58:21 xen kernel: SGI XFS with ACLs, security attributes, > > realtime, large block/inode numbers, no debug enabled > > Dec 29 23:58:21 xen kernel: JFS: nTxBlock = 8192, nTxLock = 65536 > > Dec 29 23:58:21 xen kernel: ntfs: driver 2.1.30 [Flags: R/W MODULE]. > > Dec 29 23:58:21 xen kernel: QNX4 filesystem 0.2.3 registered. > > Dec 29 23:58:21 xen kernel: raid6: sse2x1 9012 MB/s > > Dec 29 23:58:21 xen kernel: raid6: sse2x2 11538 MB/s > > Dec 29 23:58:21 xen kernel: raid6: sse2x4 13416 MB/s > > Dec 29 23:58:21 xen kernel: raid6: avx2x1 17961 MB/s > > Dec 29 23:58:21 xen kernel: raid6: avx2x2 20596 MB/s > > Dec 29 23:58:21 xen kernel: raid6: avx2x4 23839 MB/s > > Dec 29 23:58:21 xen kernel: raid6: using algorithm avx2x4 (23839 MB/s) > > Dec 29 23:58:21 xen kernel: raid6: using avx2x2 recovery algorithm > > Dec 29 23:58:22 xen kernel: xor: automatically using best checksumming > > function: > > Dec 29 23:58:22 xen kernel: avx : 28823.000 MB/sec > > Dec 29 23:58:22 xen kernel: Btrfs loaded > > Dec 29 23:58:22 xen kernel: fuse init (API version 7.23) > > Dec 29 23:58:22 xen kernel: EXT4-fs (xvda2): unable to read superblock > > Dec 29 23:58:22 xen kernel: EXT4-fs (xvda2): unable to read superblock > > Dec 29 23:58:22 xen kernel: EXT4-fs (xvda2): unable to read superblock > > Dec 29 23:58:22 xen kernel: XFS (xvda2): Invalid superblock magic number > > Dec 29 23:58:22 xen kernel: FAT-fs (xvda2): utf8 is not a recommended IO > > charset for FAT filesystems, filesystem will be case sensitive! > > Dec 29 23:58:22 xen kernel: FAT-fs (xvda2): bogus number of reserved sectors > > Dec 29 23:58:22 xen kernel: FAT-fs (xvda2): Can't find a valid FAT > > filesystem > > Dec 29 23:58:22 xen kernel: FAT-fs (xvda2): utf8 is not a recommended IO > > charset for FAT filesystems, filesystem will be case sensitive! > > Dec 29 23:58:22 xen kernel: FAT-fs (xvda2): bogus number of reserved sectors > > Dec 29 23:58:22 xen kernel: FAT-fs (xvda2): Can't find a valid FAT > > filesystem > > Dec 29 23:58:22 xen kernel: ntfs: (device xvda2): read_ntfs_boot_sector(): > > Primary boot sector is invalid. > > Dec 29 23:58:22 xen kernel: ntfs: (device xvda2): read_ntfs_boot_sector(): > > Mount option errors=recover not used. Aborting without trying to recover. > > Dec 29 23:58:22 xen kernel: ntfs: (device xvda2): ntfs_fill_super(): Not an > > NTFS volume. > > Dec 29 23:58:22 xen kernel: MINIX-fs: unable to read superblock > > Dec 29 23:58:22 xen kernel: attempt to access beyond end of device > > Dec 29 23:58:22 xen kernel: xvda2: rw=16, want=3, limit=2 > > Dec 29 23:58:22 xen kernel: hfsplus: unable to find HFS+ superblock > > Dec 29 23:58:22 xen kernel: qnx4: no qnx4 filesystem (no root dir). > > Dec 29 23:58:22 xen kernel: You didn't specify the type of your ufs > > filesystem > > > > mount -t ufs -o > > ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... > > > >>>> WARNING<<< Wrong ufstype may corrupt your filesystem, default is > >>>> ufstype=old > > Dec 29 23:58:22 xen kernel: hfs: can't find a HFS filesystem on dev xvda2 > > Dec 29 23:58:24 xen kernel: xen:xen_evtchn: Event-channel device installed > >> > >> I don't have much experience with nested virt but AIUI there are some > >> caveats with running Xen on Xen, in particular it seems that the L1 > >> hypervisor (see [0] for the terminology) can either be a xenbus client > >> of the L0 hypervisor or provide xenbus services to its own L2 guests, > >> but not both at the same time. I think that people generally disable PV > >> drivers on the L1 domain (e.g. with xen_platform_pci=1 in its config) so > >> that it is free to provide xenbus services to its own guests. It might > >> be that this isn't relevant to the issue you report here, but it might > >> have some bearing (and it worth trying to disable it). > >> > >> [0] http://wiki.xenproject.org/wiki/Xen_nested > >> > >>> I have also tested this on a VMware Fusion 7 Guest (HW Version 11). > >> > >> And it fails in the same way? If so then that's interesting because I > >> wouldn't expect the kernel to discover that it was running on Xen under > >> those circumstances. I wonder if the initscript is confused because it > >> is running on any hypervisor at all not specifically Xen > >> > >> Does /sys/hypervisor/type exist in all cases and what does it contain? > > > > root@xen:/home/sydney# cat /sys/hypervisor/type > > xen > > > > Actually, I haven't tried installing in VMware since last time it failed. I > > will give it a go again and report back on this one. > >> > >>>> Assuming you are running this on the dom0/host, have you booted into the > >>>> hypervisor at this point or are you running bare-metal/native? (I > >>>> suspect the latter). > >>> > >>> The VM was running "native", i.e. the VM itself didn't boot into > >>> hypervisor mode. > >> > >> My hypothesis is that because it is running as a guest on Xen something > >> is getting confused and thinking it is actually booting as a host on > >> Xen, but the vmware thing doesn't quite fit. > >> > >> Ian. > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
