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
>>> 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
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
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".
>>> On 25.01.18 at 12:16, wrote:
> On 25/01/18 11:40, Jan Beulich wrote:
>> 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,
>
> Really?
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
# 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
On 25/01/18 11:40, Jan Beulich wrote:
On 25.01.18 at 11:25, wrote:
>>> Xen doesn't crash at all.
>
> Did you read the above? it is being confirmed by ...
>
>> With this file, it works, Xen boots :
>>
>> ```
>> [global]
>> default=xen
>>
>> [xen]
>> options=loglvl=all
(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,
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
>>> 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
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
>>> On 23.01.18 at 12:18, wrote:
> 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
>
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
14 matches
Mail list logo