Re: [Xen-devel] [Xen EFI] Impossible to limit the dom0 memory
Hi Jan, hi Juergen, This needs to be investigated from the kernel side (which I'm afraid I simply don't have the time to help with). If someone can lead me, I can give some of my time to help. I can also provide an access to a server where the problem occurs. Let me know what I can do. I also have to admit that your way of stripping all relevant (technical) context from the earlier conversation made it necessary to dig out the old thread to understand at all what this is about. Sorry, for everyone else interested by the problem, the thread is here : https://lists.xenproject.org/archives/html/xen-devel/2018-01/threads.html#02010 Thanks for your reply, Guillaume Le 03/12/2018 à 09:25, Jan Beulich a écrit : On 30.11.18 at 16:12, wrote: I'm trying again this week to install Xen on a OVH server (https://www.ovh.com/fr/serveurs_dedies/infra/1801eg02.xml). It is still impossible to boot Xen with the option "dom0_mem=1G,max:1G" (boot : EFI->xen). I'm sorry to say so, but nothing has changed from the prior situation: This needs to be investigated from the kernel side (which I'm afraid I simply don't have the time to help with). I also have to admit that your way of stripping all relevant (technical) context from the earlier conversation made it necessary to dig out the old thread to understand at all what this is about. Jan ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Xen EFI] Impossible to limit the dom0 memory
Hi Jan, hi Juergen, I'm trying again this week to install Xen on a OVH server (https://www.ovh.com/fr/serveurs_dedies/infra/1801eg02.xml). It is still impossible to boot Xen with the option "dom0_mem=1G,max:1G" (boot : EFI->xen). I have tried with Debian 9 stable/stretch : - grub2 (2.02~beta3-5+deb9u1) : https://packages.debian.org/stretch/grub2 - xen-system-amd64 (4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10) : https://packages.debian.org/stretch/xen-system-amd64 - linux-image-amd64 (4.9+80+deb9u6) (4.9+80+deb9u6) https://packages.debian.org/stretch/linux-image-amd64 I have tried with Debian 10 testing/buster : - grub2 (2.02+dfsg1-8) : https://packages.debian.org/buster/grub2 - xen-system-amd64 (4.11.1~pre.20180911.5acdd26fdc+dfsg-5) : https://packages.debian.org/buster/xen-system-amd64 - linux-image-amd64 (4.18+99) : https://packages.debian.org/buster/linux-image-amd64 # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 158 model name : Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz stepping: 9 microcode : 0x8e Microcode version seems to be up to date : https://www.intel.com/content/dam/www/public/us/en/documents/sa00115-microcode-update-guidance.pdf Here is my WORKING xen.cfg file : ``` [global] default=xen [xen] options=smt=on kernel=$VMLINUZ_NAME root=/dev/md3 ro rootdelay=10 noquiet nosplash ramdisk=$INITRD_NAME ``` Here is my FAILING xen.cfg file (with dom0_mem=1G,max:1G) : ``` [global] default=xen [xen] options=smt=on dom0_mem=1G,max:1G kernel=vmlinuz root=/dev/md3 ro rootdelay=10 noquiet nosplash ramdisk=initrd.img ``` For information, if helpful : - Booting Linux with EFI->grub->Linux works fine. - Booting Xen with EFI->grub->Xen fails too (In January I only had 1/8 core available, now I cannot boot but I will discuss this problem in another thread). Do you have more information on the dom0_mem argument problem ? Best regards, Guillaume Le 25/01/2018 à 17:07, msd+xen-de...@msd.im a écrit : I have installed `linux-image-amd64-dbg` and `binutils`. I can now execute `addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 `. I have generated a file "commands.txt" with all the addresses after "Guest stack trace from rsp=82003cb0:" in my log file "dom0_crash_with_dom0_memory.txt". I attached the result : "result.txt". We can see inside this file "xen/mmu_pv.c:1548" and "drivers/firmware/efi/efi.c:558", so I hope it will be helpful. Is that ok for you ? Can I do something more ? Regards, Guillaume ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Xen EFI] Impossible to limit the dom0 memory
I have installed `linux-image-amd64-dbg` and `binutils`. I can now execute `addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 `. I have generated a file "commands.txt" with all the addresses after "Guest stack trace from rsp=82003cb0:" in my log file "dom0_crash_with_dom0_memory.txt". I attached the result : "result.txt". We can see inside this file "xen/mmu_pv.c:1548" and "drivers/firmware/efi/efi.c:558", so I hope it will be helpful. Is that ok for you ? Can I do something more ? Regards, Guillaume addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0010 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 303030363838 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0003 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 8240723c addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0001e030 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 00010086 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 82003cf0 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 e02b addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 8241c3ef addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 86bb5000 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0001 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 824355f9 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0af0 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 1000 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 8163 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 05be82003d38 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 86bb5af0 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0010 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0018 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 000c addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 885f2e18 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 000c addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 8243582e addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 ff2001f8 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 82003de0 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 8245400f addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 824355f9 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 824c6fc0 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 45963d3ad719b2cb addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 6f65670ed0dabca3 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 05fe addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0018 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 82003df8 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 ff2000d8 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 824c6fc0 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0018 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 824540e3 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 824540e3 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 ff200260 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 024ac1e0 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 82003f18 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 8241fa00 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 204b444582003f18 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 20534f4942204949 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 30303231533a4449 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 302e4236382e5053 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 3230302e31302e33 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 3032373239302e36 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 393237303731 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0100 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 8100 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 8240a82a addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 810d12fd addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 0010 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 82003f18 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 82003ed0 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 02633000 addr2line -pfi -e vmlinux-4.14.0-0.bpo.3-amd64 000
Re: [Xen-devel] [Xen EFI] Impossible to limit the dom0 memory
Guillaume, can you try to get symbol+offset for the values on the stack looking like kernel code addresses (e.g. everything starting with "82")? For sure. Just, can you explain me how I can do this, please ? Guillaume ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Xen EFI] Impossible to limit the dom0 memory
# About the kernel crash Did you read the above? I just wanted to say that I have solved the kernel panic crash that I had before, when you explained "Xen doesn't crash at all. It's the Dom0 kernel which panics". Just for information the crash happens if I put the "console=com1" to the kernel command line. ``` kernel=vmlinuz root=/dev/md2 ro rootdelay=10 noquiet nosplash earlyprintk=xen console=com1 ``` And this, I understand, is not linked to Xen. # About the Xen Dom0 crash This tells us (together with the page fault error code) that the Dom0 kernel tried to provide memory as kernel stack which can't be written. This may be a Dom0 kernel stack overflow, but there may also be other reasons. At this point I can't exclude there being some root cause in Xen, but the issue needs to be investigated from the Dom0 kernel side. I have tested with the version 4.9 and 4.14 of the kernel from Debian and the crash occurs when there is the option "dom0_mem=1G,max:1G". https://packages.debian.org/stretch/linux-image-amd64 https://packages.debian.org/stretch-backports/linux-image-amd64 Do you want that I test something else ? Regards, Guillaume ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Xen EFI] Impossible to limit the dom0 memory
(With the attached file) Xen doesn't crash at all. With this file, it works, Xen boots : ``` [global] default=xen [xen] options=loglvl=all com1=115200,8n1 console=com1,vga kernel=vmlinuz root=/dev/md2 ro rootdelay=10 noquiet nosplash earlyprintk=xen ramdisk=initrd.img ``` With this file, I have just added "dom0_mem=1G,max:1G", Xen crashes : ``` [global] default=xen [xen] options=loglvl=all com1=115200,8n1 console=com1,vga dom0_mem=1G,max:1G kernel=vmlinuz root=/dev/md2 ro rootdelay=10 noquiet nosplash earlyprintk=xen ramdisk=initrd.img ``` I attached the boot logs "dom0_crash_with_dom0_memory.txt". The last line is "(XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds." Do you need something else helpful ? Regards, Guillaume Le 24/01/2018 à 08:43, Jan Beulich a écrit : On 23.01.18 at 18:43, wrote: Yet you'll need to provide the kernel messages I attached a console log "xen-console-log.txt". Here, Xen crash even without the "dom0_mem=1G,max:1G" option : Xen doesn't crash at all. It's the Dom0 kernel which panics, but the log doesn't tell me why it does (other than _something_ having tried to exit the init process). This doesn't look Xen related at all with the provided information. Jan Xen 4.8.3-pre (c/s ) EFI loader Using configuration file 'xen.cfg' vmlinuz: 0x82578000-0x82a16710 initrd.img: 0x80ef3000-0x82577165 0x:0x02:0x00.0x0: ROM: 0x11000 bytes at 0x85312018 0x:0x03:0x00.0x0: ROM: 0x11000 bytes at 0x85300018 (XEN) Xen version 4.8.3-pre (Debian 4.8.2+xsa245-0+deb9u1) (ijack...@chiark.greenend.org.uk) (gcc (Debian 6.3.0-18) 6.3.0 20170516) debug=n Sat Nov 25 11:30:34 UTC 2017 (XEN) Bootloader: EFI (XEN) Command line: loglvl=all com1=115200,8n1 console=com1,vga dom0_mem=1G,max:1G (XEN) Video information: (XEN) VGA is graphics mode 800x600, 32 bpp (XEN) Disc information: (XEN) Found 0 MBR signatures (XEN) Found 2 EDD information structures (XEN) EFI RAM map: (XEN) - 00058000 (usable) (XEN) 00058000 - 00059000 (reserved) (XEN) 00059000 - 0009e000 (usable) (XEN) 0009e000 - 0009f000 (reserved) (XEN) 0009f000 - 000a (usable)
Re: [Xen-devel] [Xen EFI] Impossible to limit the dom0 memory
Xen doesn't crash at all. With this file, it works, Xen boots : ``` [global] default=xen [xen] options=loglvl=all com1=115200,8n1 console=com1,vga kernel=vmlinuz root=/dev/md2 ro rootdelay=10 noquiet nosplash earlyprintk=xen ramdisk=initrd.img ``` With this file, I have just added "dom0_mem=1G,max:1G", Xen crashes : ``` [global] default=xen [xen] options=loglvl=all com1=115200,8n1 console=com1,vga dom0_mem=1G,max:1G kernel=vmlinuz root=/dev/md2 ro rootdelay=10 noquiet nosplash earlyprintk=xen ramdisk=initrd.img ``` I attached the boot logs "dom0_crash_with_dom0_memory.txt". The last line is "(XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds." Do you need something else helpful ? ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Xen EFI] Impossible to limit the dom0 memory
Yet you'll need to provide the kernel messages I attached a console log "xen-console-log.txt". Here, Xen crash even without the "dom0_mem=1G,max:1G" option : ``` # cat /boot/efi/EFI/xen/xen.cfg [global] default=xen [xen] options=loglvl=all com1=115200,8n1 console=com1,vga kernel=vmlinuz root=/dev/md2 ro rootdelay=10 noquiet nosplash earlyprintk=xen console=com1 ramdisk=initrd.img ``` Do you need something else helpful ? Regards, Guillaume [0.00] node 0: [mem 0x1000-0x00057fff] [0.00] node 0: [mem 0x00059000-0x0009dfff] [0.00] node 0: [mem 0x0009f000-0x0009] [0.00] node 0: [mem 0x0010-0x881c5fff] [0.00] node 0: [mem 0x88211000-0x88282fff] [0.00] node 0: [mem 0x89fff000-0x89ff] [0.00] node 0: [mem 0x0001-0x000861ff] [0.00] Initmem setup node 0 [mem 0x1000-0x000861ff] [0.00] p2m virtual area at c900, size is 4000 [0.00] Remapped 491049 page(s) [0.00] ACPI: PM-Timer IO Port: 0x1808 [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [0.00] IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-119 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] Using ACPI (MADT) for SMP configuration information [0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.00] smpboot: Allowing 8 CPUs, 0 hotplug CPUs [0.00] PM: Registered nosave memory: [mem 0x-0x0fff] [0.00] PM: Registered nosave memory: [mem 0x00058000-0x00058fff] [0.00] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff] [0.00] PM: Registered nosave memory: [mem 0x000a-0x000f] [0.00] PM: Registered nosave memory: [mem 0x881c6000-0x881c6fff] [0.00] PM: Registered nosave memory: [mem 0x881c7000-0x88210fff] [0.00] PM: Registered nosave memory: [mem 0x88283000-0x89ec1fff] [0.00] PM: Registered nosave memory: [mem 0x89ec2000-0x89f99fff] [0.00] PM: Registered nosave memory: [mem 0x89f9a000-0x89ffefff] [0.00] PM: Registered nosave memory: [mem 0x8a00-0x8bff] [0.00] PM: Registered nosave memory: [mem 0x8c00-0x8fff] [0.00] PM: Registered nosave memory: [mem 0x9000-0x95ff] [0.00] PM: Registered nosave memory: [mem 0x9600-0x97ff] [0.00] PM: Registered nosave memory: [mem 0x9800-0x9dff] [0.00] PM: Registered nosave memory: [mem 0x9e00-0xe00f9fff] [0.00] PM: Registered nosave memory: [mem 0xe00fa000-0xe00fafff] [0.00] PM: Registered nosave memory: [mem 0xe00fb000-0xe00fcfff] [0.00] PM: Registered nosave memory: [mem 0xe00fd000-0xe00fdfff] [0.00] PM: Registered nosave memory: [mem 0xe00fe000-0xfdff] [0.00] PM: Registered nosave memory: [mem 0xfe00-0xfe010fff] [0.00] PM: Registered nosave memory: [mem 0xfe011000-0xfebf] [0.00] PM: Registered nosave memory: [mem 0xfec0-0xfec00fff] [0.00] PM: Registered nosave memory: [mem 0xfec01000-0xfed8] [0.00] PM: Registered nosave memory: [mem 0xfed9-0xfed90fff] [0.00] PM: Registered nosave memory: [mem 0xfed91000-0xfedf] [0.00] PM: Registered nosave memory: [mem 0xfee0-0xfeef] [0.00] PM: Registered nosave memory: [mem 0xfef0-0x] [0.00] e820: [mem 0x9e00-0xe00f9fff] available for PCI devices [0.00] Booting paravirtualized kernel on Xserve-AD) [0.00] clocksource: refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 7645519600211568 ns [0.00] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1 [0.00] percpu: Embedded 35 pages/cpu @88083ec0 s105304 r8192 d29864 u262144 [0.00] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes) [0.00] Built 1 zonelists in Node order, mobility grouping on. Total pages: 8169272 [0.00] Policy zone: Normal [0.00] Kernel command line: root=/dev/md2 ro rootdelay=10 noquiet nosplash earlyprintk=xen console=com1 [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] software IO TLB [mem 0x83ac0-0x83ec0] (64MB) mapped at
[Xen-devel] [Xen EFI] Impossible to limit the dom0 memory
Hi, I have configured Xen to boot directly from EFI (with `efibootmgr`). As explained on the Xen_EFI wiki page, I have added a line "options=" into my file "/boot/efi/EFI/xen/xen.cfg" : ``` # cat /boot/efi/EFI/xen/xen.cfg : [global] default=xen [xen] options=dom0_mem=1G,max:1G kernel=vmlinuz root=/dev/md2 ro rootdelay=10 noquiet nosplash ramdisk=initrd.img ``` With the line `options=dom0_mem=1G,max:1G` the server reboot infinitely. Without the line `options=dom0_mem=1G,max:1G`, the server boot correctly, but obviously, the dom0 memory is in ballooning mode. I have attached a screen shot of the boot lines with the last lines I can see before the reboot. Unfortunately, I have nothing in kern.log. 1. Do you know what happens ? 2. Do you need some logs ? Regards, Guillaume Links : - https://wiki.xen.org/wiki/Xen_Project_Best_Practices#Xen_dom0_dedicated_memory_and_preventing_dom0_memory_ballooning - https://xenbits.xen.org/docs/4.8-testing/misc/xen-command-line.html - https://wiki.xen.org/wiki/Xen_EFI ``` # cat /proc/cpuinfo model name : Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz microcode : 0x5e flags : fpu de tsc msr pae mce cx8 apic sep mca cmov pat clflush acpi mmx fxsr sse sse2 ht syscall nx lm constant_tsc arch_perfmon rep_good nopl nonstop_tsc eagerfpu pni pclmulqdq monitor est ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch epb fsgsbase bmi1 hle avx2 bmi2 erms rtm rdseed adx clflushopt xsaveopt xsavec xgetbv1 dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp # xl info release: 4.9.0-5-amd64 version: #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) xen_version: 4.8.3-pre # cat /etc/debian_version 9.3 ``` ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] I only see one CPU core on Xen when booted via grub
... your report is very likely duplicating earlier ones where the ACPI root point cannot be found without it being properly propagated through by grub from EFI to Xen. Iirc the only way around that is to chainload xen.efi, if the grub used doesn't support the extensions needed to boot Xen via the multiboot2 protocol (support for which was added during the 4.9 development cycle). Thanks. So if I want to boot Xen through grub, I need Xen >= 4.9 and which version of grub ? Guillaume ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
[Xen-devel] I only see one CPU core on Xen when booted via grub
Hi, I only see 1 CPU core on Xen 4.9 when booted via grub instead of 8. It's may be related to : - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820807 - https://xenproject.atlassian.net/browse/XEN-42 It is the first server on which I have this problem. I can confirm that : - if I boot Debian througt grub, I see the 8 cores - if I boot Xen through grub, I only see _one_ core - if I boot Xen directly through EFI (using `efibootmgr`), I see the 8 cores 1. Do you know what happens ? 2. Do you need some logs ? Regards, Guillaume # cat /proc/cpuinfo model name : Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz microcode : 0x5e flags : fpu de tsc msr pae mce cx8 apic sep mca cmov pat clflush acpi mmx fxsr sse sse2 ht syscall nx lm constant_tsc arch_perfmon rep_good nopl nonstop_tsc eagerfpu pni pclmulqdq monitor est ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch epb fsgsbase bmi1 hle avx2 bmi2 erms rtm rdseed adx clflushopt xsaveopt xsavec xgetbv1 dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp # xl info release: 4.9.0-5-amd64 version: #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) xen_version: 4.8.3-pre # cat /etc/debian_version 9.3 ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
