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 <addr>`.
I have generated a file "commands.txt" with all the addresses after
"Guest stack trace from rsp=ffffffff82003cb0:" 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
