Re: [Xen-devel] Xen-4.10 Domain-0 crashes at bootup
Hi All. As suggested by Michael. I compiled the kernel as per https://lkml.org/lkml/2018/2/23/59, containing the patch https://lists.xenproject.org/archives/html/xen-devel/2018-02/msg00045.html. Upon installing this fresh kernel, the machine booted fine with Xen enabled (just needed an additional "sudo apt-get install libyajl-dev" and another reboot to get the proper listing of "Domain-0". So, at least from my side, this thread can be marked solved/closed. Thanks and Regards, Ajay On Wed, Apr 4, 2018 at 8:45 PM, Juergen Gross wrote: > On 04/04/18 17:00, M A Young wrote: >> On Wed, 4 Apr 2018, Ajay Garg wrote: >> >>> Thanks Michael for the reply. >>> >>> I want to give this patch a try, as the symptoms look identical. >>> However, I see no xen-head.S when I clone the repo from >>> git://xenbits.xen.org/xen.git >>> >>> What am I missing? >> >> The patch is for the xen code in the kernel. It was accepted in the kernel >> upstream (in 4.15.5 and probably backported to other maintained kernels) >> so you probably just need a kernel less than a month old, but as has >> already been said, the kernel may not be the problem. > > And the symptoms are completely different (well, at least for me). > > Ajay's crash is due to an illegal instruction, so probably a BUG(). > > The patch above fixes an early page fault in the kernel. > > > Juergen -- Regards, Ajay ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Xen-4.10 Domain-0 crashes at bootup
On 04/04/18 17:00, M A Young wrote: > On Wed, 4 Apr 2018, Ajay Garg wrote: > >> Thanks Michael for the reply. >> >> I want to give this patch a try, as the symptoms look identical. >> However, I see no xen-head.S when I clone the repo from >> git://xenbits.xen.org/xen.git >> >> What am I missing? > > The patch is for the xen code in the kernel. It was accepted in the kernel > upstream (in 4.15.5 and probably backported to other maintained kernels) > so you probably just need a kernel less than a month old, but as has > already been said, the kernel may not be the problem. And the symptoms are completely different (well, at least for me). Ajay's crash is due to an illegal instruction, so probably a BUG(). The patch above fixes an early page fault in the kernel. Juergen ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Xen-4.10 Domain-0 crashes at bootup
On Wed, 4 Apr 2018, Ajay Garg wrote: > Thanks Michael for the reply. > > I want to give this patch a try, as the symptoms look identical. > However, I see no xen-head.S when I clone the repo from > git://xenbits.xen.org/xen.git > > What am I missing? The patch is for the xen code in the kernel. It was accepted in the kernel upstream (in 4.15.5 and probably backported to other maintained kernels) so you probably just need a kernel less than a month old, but as has already been said, the kernel may not be the problem. Michael Young ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Xen-4.10 Domain-0 crashes at bootup
Thanks Michael for the reply. I want to give this patch a try, as the symptoms look identical. However, I see no xen-head.S when I clone the repo from git://xenbits.xen.org/xen.git What am I missing? Thanks and Regards, Ajay > > It is a kernel problem under some compile conditions. See for example > https://lists.xenproject.org/archives/html/xen-devel/2018-02/msg00010.html > and the patch at > https://lists.xenproject.org/archives/html/xen-devel/2018-02/msg00045.html > > Michael Young ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Xen-4.10 Domain-0 crashes at bootup
On Wed, Apr 4, 2018 at 6:25 AM, Juergen Gross wrote: > On 04/04/18 12:07, M A Young wrote: >> On Wed, 4 Apr 2018, Ajay Garg wrote: >> >>> Since I failed to get a single reply on my original issue as per >>> https://lists.xenproject.org/archives/html/minios-devel/2018-04/msg4.html, >>> so I had no option but to try on a newer xen version. >>> >>> So, I created a new virtualbox-guest, and followed the steps as per >>> https://blog.werk21.de/en/2018/02/08/build-xen-hypervisor-410-and-xen-tools-ubuntu-1604-pvh >>> >>> Now, when start the guest with Xen-hypervisor enabled, it does not come up. >>> I took serial-logs at bootup time, they are as follows : >>> >>> # >>> Xen 4.10.1-pre >>> (XEN) Xen version 4.10.1-pre (ajay@) (gcc (Ubuntu >>> 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609) debug=n Wed Apr 4 12:54:58 >>> IST 2018 >>> (XEN) Latest ChangeSet: Tue Mar 20 14:23:14 2018 +0100 git:0f92968 >>> (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.17 >>> (XEN) Command line: placeholder console=com1 com1=115200,8n1 >>> loglvl=all guest_loglvl=all >>> (XEN) Xen image load base address: 0 >>> (XEN) Video information: >>> (XEN) VGA is text mode 80x25, font 8x16 >>> (XEN) Disc information: >>> (XEN) Found 1 MBR signatures >>> (XEN) Found 1 EDD information structures >>> (XEN) Xen-e820 RAM map: >>> (XEN) - 0009fc00 (usable) >>> (XEN) 0009fc00 - 000a (reserved) >>> (XEN) 000f - 0010 (reserved) >>> (XEN) 0010 - bfff (usable) >>> (XEN) bfff - c000 (ACPI data) >>> (XEN) fec0 - fec01000 (reserved) >>> (XEN) fee0 - fee01000 (reserved) >>> (XEN) fffc - 0001 (reserved) >>> (XEN) New Xen image base address: 0xbf80 >>> (XEN) System RAM: 3071MB (3145276kB) >>> (XEN) ACPI: RSDP 000E, 0024 (r2 VBOX ) >>> (XEN) ACPI: XSDT BFFF0030, 003C (r1 VBOX VBOXXSDT1 ASL61) >>> (XEN) ACPI: FACP BFFF00F0, 00F4 (r4 VBOX VBOXFACP1 ASL61) >>> (XEN) ACPI: DSDT BFFF0470, 21FF (r2 VBOX VBOXBIOS2 INTL 20160108) >>> (XEN) ACPI: FACS BFFF0200, 0040 >>> (XEN) ACPI: APIC BFFF0240, 0054 (r2 VBOX VBOXAPIC1 ASL61) >>> (XEN) ACPI: SSDT BFFF02A0, 01CC (r1 VBOX VBOXCPUT2 INTL 20160108) >>> (XEN) No NUMA configuration found >>> (XEN) Faking a node at -bfff >>> (XEN) Domain heap initialised >>> (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 142 (0x8e), Stepping 9 >>> (raw 000806e9) >>> (XEN) found SMP MP-table at 0009fff0 >>> (XEN) DMI 2.5 present. >>> (XEN) Using APIC driver default >>> (XEN) ACPI: PM-Timer IO Port: 0x4008 (32 bits) >>> (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:4004,1:0], pm1x_evt[1:4000,1:0] >>> (XEN) ACPI: wakeup_vec[bfff020c], vec_size[20] >>> (XEN) ACPI: Local APIC address 0xfee0 >>> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) >>> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) >>> (XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23 >>> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) >>> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) >>> (XEN) ACPI: IRQ0 used by override. >>> (XEN) ACPI: IRQ2 used by override. >>> (XEN) ACPI: IRQ9 used by override. >>> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >>> (XEN) ERST table was not found >>> (XEN) Using ACPI (MADT) for SMP configuration information >>> (XEN) SMP: Allowing 1 CPUs (0 hotplug CPUs) >>> (XEN) IRQ limits: 24 GSI, 184 MSI/MSI-X >>> (XEN) Not enabling x2APIC: depends on iommu_supports_eim. >>> (XEN) xstate: size: 0x440 and states: 0x7 >>> (XEN) CPU0: No MCE banks present. Machine check support disabled >>> (XEN) Speculative mitigation facilities: >>> (XEN) Compiled-in support: INDIRECT_THUNK >>> (XEN) BTI mitigations: Thunk RETPOLINE, Others: RSB_NATIVE RSB_VMEXIT >>> (XEN) Using scheduler: SMP Credit Scheduler (credit) >>> (XEN) Platform timer is 3.579MHz ACPI PM Timer >>> (XEN) Detected 2712.035 MHz processor. >>> (XEN) Initing memory sharing. >>> (XEN) alt table 82d080421798 -> 82d080423244 >>> (XEN) I/O virtualisation disabled >>> (XEN) nr_sockets: 1 >>> (XEN) ENABLING IO-APIC IRQs >>> (XEN) -> Using new ACK method >>> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 >>> (XEN) Allocated console ring of 16 KiB. >>> (XEN) Brought up 1 CPUs >>> (XEN) build-id: 0734050809e0cb9f52e65322a0d3911d082e348b >>> (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'. >>> (XEN) ACPI sleep modes: S3 >>> (XEN) VPMU: disabled >>> (XEN) xenoprof: Initialization failed. Intel processor family 6 model >>> 142 is not supported >>> (XEN) Dom0 has maximum 208 PIRQs >>> (XEN) NX (Execute Disable) protection active >>> (XEN) *** LOADING DOMAIN 0 *** >>> (XEN) Xen kernel: 64-bit, lsb, compat32 >>> (XEN) Dom0 ke
Re: [Xen-devel] Xen-4.10 Domain-0 crashes at bootup
On 04/04/18 12:07, M A Young wrote: > On Wed, 4 Apr 2018, Ajay Garg wrote: > >> Since I failed to get a single reply on my original issue as per >> https://lists.xenproject.org/archives/html/minios-devel/2018-04/msg4.html, >> so I had no option but to try on a newer xen version. >> >> So, I created a new virtualbox-guest, and followed the steps as per >> https://blog.werk21.de/en/2018/02/08/build-xen-hypervisor-410-and-xen-tools-ubuntu-1604-pvh >> >> Now, when start the guest with Xen-hypervisor enabled, it does not come up. >> I took serial-logs at bootup time, they are as follows : >> >> # >> Xen 4.10.1-pre >> (XEN) Xen version 4.10.1-pre (ajay@) (gcc (Ubuntu >> 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609) debug=n Wed Apr 4 12:54:58 >> IST 2018 >> (XEN) Latest ChangeSet: Tue Mar 20 14:23:14 2018 +0100 git:0f92968 >> (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.17 >> (XEN) Command line: placeholder console=com1 com1=115200,8n1 >> loglvl=all guest_loglvl=all >> (XEN) Xen image load base address: 0 >> (XEN) Video information: >> (XEN) VGA is text mode 80x25, font 8x16 >> (XEN) Disc information: >> (XEN) Found 1 MBR signatures >> (XEN) Found 1 EDD information structures >> (XEN) Xen-e820 RAM map: >> (XEN) - 0009fc00 (usable) >> (XEN) 0009fc00 - 000a (reserved) >> (XEN) 000f - 0010 (reserved) >> (XEN) 0010 - bfff (usable) >> (XEN) bfff - c000 (ACPI data) >> (XEN) fec0 - fec01000 (reserved) >> (XEN) fee0 - fee01000 (reserved) >> (XEN) fffc - 0001 (reserved) >> (XEN) New Xen image base address: 0xbf80 >> (XEN) System RAM: 3071MB (3145276kB) >> (XEN) ACPI: RSDP 000E, 0024 (r2 VBOX ) >> (XEN) ACPI: XSDT BFFF0030, 003C (r1 VBOX VBOXXSDT1 ASL61) >> (XEN) ACPI: FACP BFFF00F0, 00F4 (r4 VBOX VBOXFACP1 ASL61) >> (XEN) ACPI: DSDT BFFF0470, 21FF (r2 VBOX VBOXBIOS2 INTL 20160108) >> (XEN) ACPI: FACS BFFF0200, 0040 >> (XEN) ACPI: APIC BFFF0240, 0054 (r2 VBOX VBOXAPIC1 ASL61) >> (XEN) ACPI: SSDT BFFF02A0, 01CC (r1 VBOX VBOXCPUT2 INTL 20160108) >> (XEN) No NUMA configuration found >> (XEN) Faking a node at -bfff >> (XEN) Domain heap initialised >> (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 142 (0x8e), Stepping 9 >> (raw 000806e9) >> (XEN) found SMP MP-table at 0009fff0 >> (XEN) DMI 2.5 present. >> (XEN) Using APIC driver default >> (XEN) ACPI: PM-Timer IO Port: 0x4008 (32 bits) >> (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:4004,1:0], pm1x_evt[1:4000,1:0] >> (XEN) ACPI: wakeup_vec[bfff020c], vec_size[20] >> (XEN) ACPI: Local APIC address 0xfee0 >> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) >> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) >> (XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23 >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) >> (XEN) ACPI: IRQ0 used by override. >> (XEN) ACPI: IRQ2 used by override. >> (XEN) ACPI: IRQ9 used by override. >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >> (XEN) ERST table was not found >> (XEN) Using ACPI (MADT) for SMP configuration information >> (XEN) SMP: Allowing 1 CPUs (0 hotplug CPUs) >> (XEN) IRQ limits: 24 GSI, 184 MSI/MSI-X >> (XEN) Not enabling x2APIC: depends on iommu_supports_eim. >> (XEN) xstate: size: 0x440 and states: 0x7 >> (XEN) CPU0: No MCE banks present. Machine check support disabled >> (XEN) Speculative mitigation facilities: >> (XEN) Compiled-in support: INDIRECT_THUNK >> (XEN) BTI mitigations: Thunk RETPOLINE, Others: RSB_NATIVE RSB_VMEXIT >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >> (XEN) Platform timer is 3.579MHz ACPI PM Timer >> (XEN) Detected 2712.035 MHz processor. >> (XEN) Initing memory sharing. >> (XEN) alt table 82d080421798 -> 82d080423244 >> (XEN) I/O virtualisation disabled >> (XEN) nr_sockets: 1 >> (XEN) ENABLING IO-APIC IRQs >> (XEN) -> Using new ACK method >> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 >> (XEN) Allocated console ring of 16 KiB. >> (XEN) Brought up 1 CPUs >> (XEN) build-id: 0734050809e0cb9f52e65322a0d3911d082e348b >> (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'. >> (XEN) ACPI sleep modes: S3 >> (XEN) VPMU: disabled >> (XEN) xenoprof: Initialization failed. Intel processor family 6 model >> 142 is not supported >> (XEN) Dom0 has maximum 208 PIRQs >> (XEN) NX (Execute Disable) protection active >> (XEN) *** LOADING DOMAIN 0 *** >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2957000 >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> (XEN) Dom0 alloc.: b400->b800 (71
Re: [Xen-devel] Xen-4.10 Domain-0 crashes at bootup
On Wed, 4 Apr 2018, Ajay Garg wrote: > Since I failed to get a single reply on my original issue as per > https://lists.xenproject.org/archives/html/minios-devel/2018-04/msg4.html, > so I had no option but to try on a newer xen version. > > So, I created a new virtualbox-guest, and followed the steps as per > https://blog.werk21.de/en/2018/02/08/build-xen-hypervisor-410-and-xen-tools-ubuntu-1604-pvh > > Now, when start the guest with Xen-hypervisor enabled, it does not come up. > I took serial-logs at bootup time, they are as follows : > > # > Xen 4.10.1-pre > (XEN) Xen version 4.10.1-pre (ajay@) (gcc (Ubuntu > 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609) debug=n Wed Apr 4 12:54:58 > IST 2018 > (XEN) Latest ChangeSet: Tue Mar 20 14:23:14 2018 +0100 git:0f92968 > (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.17 > (XEN) Command line: placeholder console=com1 com1=115200,8n1 > loglvl=all guest_loglvl=all > (XEN) Xen image load base address: 0 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) Disc information: > (XEN) Found 1 MBR signatures > (XEN) Found 1 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) - 0009fc00 (usable) > (XEN) 0009fc00 - 000a (reserved) > (XEN) 000f - 0010 (reserved) > (XEN) 0010 - bfff (usable) > (XEN) bfff - c000 (ACPI data) > (XEN) fec0 - fec01000 (reserved) > (XEN) fee0 - fee01000 (reserved) > (XEN) fffc - 0001 (reserved) > (XEN) New Xen image base address: 0xbf80 > (XEN) System RAM: 3071MB (3145276kB) > (XEN) ACPI: RSDP 000E, 0024 (r2 VBOX ) > (XEN) ACPI: XSDT BFFF0030, 003C (r1 VBOX VBOXXSDT1 ASL61) > (XEN) ACPI: FACP BFFF00F0, 00F4 (r4 VBOX VBOXFACP1 ASL61) > (XEN) ACPI: DSDT BFFF0470, 21FF (r2 VBOX VBOXBIOS2 INTL 20160108) > (XEN) ACPI: FACS BFFF0200, 0040 > (XEN) ACPI: APIC BFFF0240, 0054 (r2 VBOX VBOXAPIC1 ASL61) > (XEN) ACPI: SSDT BFFF02A0, 01CC (r1 VBOX VBOXCPUT2 INTL 20160108) > (XEN) No NUMA configuration found > (XEN) Faking a node at -bfff > (XEN) Domain heap initialised > (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 142 (0x8e), Stepping 9 > (raw 000806e9) > (XEN) found SMP MP-table at 0009fff0 > (XEN) DMI 2.5 present. > (XEN) Using APIC driver default > (XEN) ACPI: PM-Timer IO Port: 0x4008 (32 bits) > (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:4004,1:0], pm1x_evt[1:4000,1:0] > (XEN) ACPI: wakeup_vec[bfff020c], vec_size[20] > (XEN) ACPI: Local APIC address 0xfee0 > (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > (XEN) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) ACPI: IRQ9 used by override. > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) ERST table was not found > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) SMP: Allowing 1 CPUs (0 hotplug CPUs) > (XEN) IRQ limits: 24 GSI, 184 MSI/MSI-X > (XEN) Not enabling x2APIC: depends on iommu_supports_eim. > (XEN) xstate: size: 0x440 and states: 0x7 > (XEN) CPU0: No MCE banks present. Machine check support disabled > (XEN) Speculative mitigation facilities: > (XEN) Compiled-in support: INDIRECT_THUNK > (XEN) BTI mitigations: Thunk RETPOLINE, Others: RSB_NATIVE RSB_VMEXIT > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Platform timer is 3.579MHz ACPI PM Timer > (XEN) Detected 2712.035 MHz processor. > (XEN) Initing memory sharing. > (XEN) alt table 82d080421798 -> 82d080423244 > (XEN) I/O virtualisation disabled > (XEN) nr_sockets: 1 > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 > (XEN) Allocated console ring of 16 KiB. > (XEN) Brought up 1 CPUs > (XEN) build-id: 0734050809e0cb9f52e65322a0d3911d082e348b > (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'. > (XEN) ACPI sleep modes: S3 > (XEN) VPMU: disabled > (XEN) xenoprof: Initialization failed. Intel processor family 6 model > 142 is not supported > (XEN) Dom0 has maximum 208 PIRQs > (XEN) NX (Execute Disable) protection active > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2957000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: b400->b800 (715309 pages > to be allocated) > (XEN) Init. ramdisk: bc915000->bf7ffed9 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Lo
[Xen-devel] Xen-4.10 Domain-0 crashes at bootup
Since I failed to get a single reply on my original issue as per https://lists.xenproject.org/archives/html/minios-devel/2018-04/msg4.html, so I had no option but to try on a newer xen version. So, I created a new virtualbox-guest, and followed the steps as per https://blog.werk21.de/en/2018/02/08/build-xen-hypervisor-410-and-xen-tools-ubuntu-1604-pvh Now, when start the guest with Xen-hypervisor enabled, it does not come up. I took serial-logs at bootup time, they are as follows : # Xen 4.10.1-pre (XEN) Xen version 4.10.1-pre (ajay@) (gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609) debug=n Wed Apr 4 12:54:58 IST 2018 (XEN) Latest ChangeSet: Tue Mar 20 14:23:14 2018 +0100 git:0f92968 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.17 (XEN) Command line: placeholder console=com1 com1=115200,8n1 loglvl=all guest_loglvl=all (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009fc00 (usable) (XEN) 0009fc00 - 000a (reserved) (XEN) 000f - 0010 (reserved) (XEN) 0010 - bfff (usable) (XEN) bfff - c000 (ACPI data) (XEN) fec0 - fec01000 (reserved) (XEN) fee0 - fee01000 (reserved) (XEN) fffc - 0001 (reserved) (XEN) New Xen image base address: 0xbf80 (XEN) System RAM: 3071MB (3145276kB) (XEN) ACPI: RSDP 000E, 0024 (r2 VBOX ) (XEN) ACPI: XSDT BFFF0030, 003C (r1 VBOX VBOXXSDT1 ASL61) (XEN) ACPI: FACP BFFF00F0, 00F4 (r4 VBOX VBOXFACP1 ASL61) (XEN) ACPI: DSDT BFFF0470, 21FF (r2 VBOX VBOXBIOS2 INTL 20160108) (XEN) ACPI: FACS BFFF0200, 0040 (XEN) ACPI: APIC BFFF0240, 0054 (r2 VBOX VBOXAPIC1 ASL61) (XEN) ACPI: SSDT BFFF02A0, 01CC (r1 VBOX VBOXCPUT2 INTL 20160108) (XEN) No NUMA configuration found (XEN) Faking a node at -bfff (XEN) Domain heap initialised (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 142 (0x8e), Stepping 9 (raw 000806e9) (XEN) found SMP MP-table at 0009fff0 (XEN) DMI 2.5 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x4008 (32 bits) (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:4004,1:0], pm1x_evt[1:4000,1:0] (XEN) ACPI: wakeup_vec[bfff020c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee0 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ERST table was not found (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 1 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 24 GSI, 184 MSI/MSI-X (XEN) Not enabling x2APIC: depends on iommu_supports_eim. (XEN) xstate: size: 0x440 and states: 0x7 (XEN) CPU0: No MCE banks present. Machine check support disabled (XEN) Speculative mitigation facilities: (XEN) Compiled-in support: INDIRECT_THUNK (XEN) BTI mitigations: Thunk RETPOLINE, Others: RSB_NATIVE RSB_VMEXIT (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 3.579MHz ACPI PM Timer (XEN) Detected 2712.035 MHz processor. (XEN) Initing memory sharing. (XEN) alt table 82d080421798 -> 82d080423244 (XEN) I/O virtualisation disabled (XEN) nr_sockets: 1 (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) Allocated console ring of 16 KiB. (XEN) Brought up 1 CPUs (XEN) build-id: 0734050809e0cb9f52e65322a0d3911d082e348b (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'. (XEN) ACPI sleep modes: S3 (XEN) VPMU: disabled (XEN) xenoprof: Initialization failed. Intel processor family 6 model 142 is not supported (XEN) Dom0 has maximum 208 PIRQs (XEN) NX (Execute Disable) protection active (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2957000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: b400->b800 (715309 pages to be allocated) (XEN) Init. ramdisk: bc915000->bf7ffed9 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 8100->82957000 (XEN) Init. ramdisk: -> (XEN) Phys-Mach map: 0080->0080005ac8c0 (XEN) Start info:82957000->829574b4 (XEN) Xenstore ring: 000
