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, [email protected] a écrit :
I have installed `linux-image-amd
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 a
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 Deb
... 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
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
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=
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_me
(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,
# 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 ke
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 l
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
11 matches
Mail list logo
