* booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-15 23:18 ` Pry Mar
0 siblings, 0 replies; 18+ messages in thread
From: Pry Mar @ 2019-04-15 23:18 UTC (permalink / raw)
To: xen-devel
Hello,
https://paste.debian.net/1077718/
I get a kernel panic as shown in the paste above no matter how I
launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
pvgrub2 (i386-xen_pvh support).
The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
packages (self built).
~$ sudo dpkg -l | grep -P 'xen|qemu' | grep '^ii'
ii libxen-4.12:amd64 4.12.0-1+ub18u04.1 amd64
Public libs for Xen
ii libxenstore3.0:amd64 4.12.0-1+ub18u04.1 amd64
Xenstore communications library for Xen
ii libxentoolcore1:amd64 4.12.0-1+ub18u04.1 amd64
helper for qemu & libxenstore
ii qemuu 3.1.0-1+ub18u04.1 amd64
qemu-system-i386 (3.1.0/xen-4.12) with 9pfs support
ii xen-hypervisor-4.12-amd64 4.12.0-1+ub18u04.1
amd64 Xen Hypervisor on AMD64
ii xen-utils-4.12 4.12.0-1+ub18u04.1
amd64 XEN administrative tools
ii xen-utils-common 4.12.0-1+ub18u04.1
all Xen administrative tools - common files
ii xen-virbr0 0.1-2
all Setup a virbr0 bridge and dnsmasq on a
ii xenstore-utils 4.12.0-1+ub18u04.1
amd64 Xenstore command line utilities for Xen
The same xl config and grub config works in xen-4.11.1. I've searched
for any new options in xl.cfg that could influence this, but nothing
catches my eye.
I get the same dmesg in other boot methods, but the i386-xen_pvh style
yields more info at the end. The (fire-missle) grub script is provided
Hans van Kranenburg .
Before the initrd unpacks I see many errors (line 201 of paste):
fuse init modprobe trap invalid opcode ip:7f797dc7bb95
But later the xen_netfront and xen_blkfront drivers load fine and then
trouble starts.
PryMar56,
##xen-packaging on Freenode IRC
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* [Xen-devel] booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-15 23:18 ` Pry Mar
0 siblings, 0 replies; 18+ messages in thread
From: Pry Mar @ 2019-04-15 23:18 UTC (permalink / raw)
To: xen-devel
Hello,
https://paste.debian.net/1077718/
I get a kernel panic as shown in the paste above no matter how I
launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
pvgrub2 (i386-xen_pvh support).
The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
packages (self built).
~$ sudo dpkg -l | grep -P 'xen|qemu' | grep '^ii'
ii libxen-4.12:amd64 4.12.0-1+ub18u04.1 amd64
Public libs for Xen
ii libxenstore3.0:amd64 4.12.0-1+ub18u04.1 amd64
Xenstore communications library for Xen
ii libxentoolcore1:amd64 4.12.0-1+ub18u04.1 amd64
helper for qemu & libxenstore
ii qemuu 3.1.0-1+ub18u04.1 amd64
qemu-system-i386 (3.1.0/xen-4.12) with 9pfs support
ii xen-hypervisor-4.12-amd64 4.12.0-1+ub18u04.1
amd64 Xen Hypervisor on AMD64
ii xen-utils-4.12 4.12.0-1+ub18u04.1
amd64 XEN administrative tools
ii xen-utils-common 4.12.0-1+ub18u04.1
all Xen administrative tools - common files
ii xen-virbr0 0.1-2
all Setup a virbr0 bridge and dnsmasq on a
ii xenstore-utils 4.12.0-1+ub18u04.1
amd64 Xenstore command line utilities for Xen
The same xl config and grub config works in xen-4.11.1. I've searched
for any new options in xl.cfg that could influence this, but nothing
catches my eye.
I get the same dmesg in other boot methods, but the i386-xen_pvh style
yields more info at the end. The (fire-missle) grub script is provided
Hans van Kranenburg .
Before the initrd unpacks I see many errors (line 201 of paste):
fuse init modprobe trap invalid opcode ip:7f797dc7bb95
But later the xen_netfront and xen_blkfront drivers load fine and then
trouble starts.
PryMar56,
##xen-packaging on Freenode IRC
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 8:10 ` M A Young
0 siblings, 0 replies; 18+ messages in thread
From: M A Young @ 2019-04-16 8:10 UTC (permalink / raw)
To: Pry Mar; +Cc: xen-devel
On Mon, 15 Apr 2019, Pry Mar wrote:
> Hello,
>
> https://paste.debian.net/1077718/
>
> I get a kernel panic as shown in the paste above no matter how I
> launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
> pvgrub2 (i386-xen_pvh support).
>
> The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
> packages (self built).
> ~$ sudo dpkg -l | grep -P 'xen|qemu' | grep '^ii'
> ii libxen-4.12:amd64 4.12.0-1+ub18u04.1 amd64
> Public libs for Xen
> ii libxenstore3.0:amd64 4.12.0-1+ub18u04.1 amd64
> Xenstore communications library for Xen
> ii libxentoolcore1:amd64 4.12.0-1+ub18u04.1 amd64
> helper for qemu & libxenstore
> ii qemuu 3.1.0-1+ub18u04.1 amd64
> qemu-system-i386 (3.1.0/xen-4.12) with 9pfs support
> ii xen-hypervisor-4.12-amd64 4.12.0-1+ub18u04.1
> amd64 Xen Hypervisor on AMD64
> ii xen-utils-4.12 4.12.0-1+ub18u04.1
> amd64 XEN administrative tools
> ii xen-utils-common 4.12.0-1+ub18u04.1
> all Xen administrative tools - common files
> ii xen-virbr0 0.1-2
> all Setup a virbr0 bridge and dnsmasq on a
> ii xenstore-utils 4.12.0-1+ub18u04.1
> amd64 Xenstore command line utilities for Xen
>
> The same xl config and grub config works in xen-4.11.1. I've searched
> for any new options in xl.cfg that could influence this, but nothing
> catches my eye.
>
> I get the same dmesg in other boot methods, but the i386-xen_pvh style
> yields more info at the end. The (fire-missle) grub script is provided
> Hans van Kranenburg .
>
> Before the initrd unpacks I see many errors (line 201 of paste):
> fuse init modprobe trap invalid opcode ip:7f797dc7bb95
>
> But later the xen_netfront and xen_blkfront drivers load fine and then
> trouble starts.
>
> PryMar56,
> ##xen-packaging on Freenode IRC
I have seen a similar crash on Fedora on a F30 guest that works with PV
but crashes with HVM on 4.12 but not on 4.11.1. I am seeing similar
behaviour on a Windows 10 HVM guest, though that is harder to diagnose.
Michael Young
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 8:10 ` M A Young
0 siblings, 0 replies; 18+ messages in thread
From: M A Young @ 2019-04-16 8:10 UTC (permalink / raw)
To: Pry Mar; +Cc: xen-devel
On Mon, 15 Apr 2019, Pry Mar wrote:
> Hello,
>
> https://paste.debian.net/1077718/
>
> I get a kernel panic as shown in the paste above no matter how I
> launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
> pvgrub2 (i386-xen_pvh support).
>
> The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
> packages (self built).
> ~$ sudo dpkg -l | grep -P 'xen|qemu' | grep '^ii'
> ii libxen-4.12:amd64 4.12.0-1+ub18u04.1 amd64
> Public libs for Xen
> ii libxenstore3.0:amd64 4.12.0-1+ub18u04.1 amd64
> Xenstore communications library for Xen
> ii libxentoolcore1:amd64 4.12.0-1+ub18u04.1 amd64
> helper for qemu & libxenstore
> ii qemuu 3.1.0-1+ub18u04.1 amd64
> qemu-system-i386 (3.1.0/xen-4.12) with 9pfs support
> ii xen-hypervisor-4.12-amd64 4.12.0-1+ub18u04.1
> amd64 Xen Hypervisor on AMD64
> ii xen-utils-4.12 4.12.0-1+ub18u04.1
> amd64 XEN administrative tools
> ii xen-utils-common 4.12.0-1+ub18u04.1
> all Xen administrative tools - common files
> ii xen-virbr0 0.1-2
> all Setup a virbr0 bridge and dnsmasq on a
> ii xenstore-utils 4.12.0-1+ub18u04.1
> amd64 Xenstore command line utilities for Xen
>
> The same xl config and grub config works in xen-4.11.1. I've searched
> for any new options in xl.cfg that could influence this, but nothing
> catches my eye.
>
> I get the same dmesg in other boot methods, but the i386-xen_pvh style
> yields more info at the end. The (fire-missle) grub script is provided
> Hans van Kranenburg .
>
> Before the initrd unpacks I see many errors (line 201 of paste):
> fuse init modprobe trap invalid opcode ip:7f797dc7bb95
>
> But later the xen_netfront and xen_blkfront drivers load fine and then
> trouble starts.
>
> PryMar56,
> ##xen-packaging on Freenode IRC
I have seen a similar crash on Fedora on a F30 guest that works with PV
but crashes with HVM on 4.12 but not on 4.11.1. I am seeing similar
behaviour on a Windows 10 HVM guest, though that is harder to diagnose.
Michael Young
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 9:10 ` Roger Pau Monné
0 siblings, 0 replies; 18+ messages in thread
From: Roger Pau Monné @ 2019-04-16 9:10 UTC (permalink / raw)
To: Pry Mar; +Cc: xen-devel
On Mon, Apr 15, 2019 at 04:18:57PM -0700, Pry Mar wrote:
> Hello,
>
> https://paste.debian.net/1077718/
>
> I get a kernel panic as shown in the paste above no matter how I
> launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
> pvgrub2 (i386-xen_pvh support).
>
> The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
> packages (self built).
> ~$ sudo dpkg -l | grep -P 'xen|qemu' | grep '^ii'
> ii libxen-4.12:amd64 4.12.0-1+ub18u04.1 amd64
> Public libs for Xen
> ii libxenstore3.0:amd64 4.12.0-1+ub18u04.1 amd64
> Xenstore communications library for Xen
> ii libxentoolcore1:amd64 4.12.0-1+ub18u04.1 amd64
> helper for qemu & libxenstore
> ii qemuu 3.1.0-1+ub18u04.1 amd64
> qemu-system-i386 (3.1.0/xen-4.12) with 9pfs support
> ii xen-hypervisor-4.12-amd64 4.12.0-1+ub18u04.1
> amd64 Xen Hypervisor on AMD64
> ii xen-utils-4.12 4.12.0-1+ub18u04.1
> amd64 XEN administrative tools
> ii xen-utils-common 4.12.0-1+ub18u04.1
> all Xen administrative tools - common files
> ii xen-virbr0 0.1-2
> all Setup a virbr0 bridge and dnsmasq on a
> ii xenstore-utils 4.12.0-1+ub18u04.1
> amd64 Xenstore command line utilities for Xen
>
> The same xl config and grub config works in xen-4.11.1. I've searched
> for any new options in xl.cfg that could influence this, but nothing
> catches my eye.
Do same kernel and initrd work fine when booted as PV or HVM?
Thanks, Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 9:10 ` Roger Pau Monné
0 siblings, 0 replies; 18+ messages in thread
From: Roger Pau Monné @ 2019-04-16 9:10 UTC (permalink / raw)
To: Pry Mar; +Cc: xen-devel
On Mon, Apr 15, 2019 at 04:18:57PM -0700, Pry Mar wrote:
> Hello,
>
> https://paste.debian.net/1077718/
>
> I get a kernel panic as shown in the paste above no matter how I
> launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
> pvgrub2 (i386-xen_pvh support).
>
> The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
> packages (self built).
> ~$ sudo dpkg -l | grep -P 'xen|qemu' | grep '^ii'
> ii libxen-4.12:amd64 4.12.0-1+ub18u04.1 amd64
> Public libs for Xen
> ii libxenstore3.0:amd64 4.12.0-1+ub18u04.1 amd64
> Xenstore communications library for Xen
> ii libxentoolcore1:amd64 4.12.0-1+ub18u04.1 amd64
> helper for qemu & libxenstore
> ii qemuu 3.1.0-1+ub18u04.1 amd64
> qemu-system-i386 (3.1.0/xen-4.12) with 9pfs support
> ii xen-hypervisor-4.12-amd64 4.12.0-1+ub18u04.1
> amd64 Xen Hypervisor on AMD64
> ii xen-utils-4.12 4.12.0-1+ub18u04.1
> amd64 XEN administrative tools
> ii xen-utils-common 4.12.0-1+ub18u04.1
> all Xen administrative tools - common files
> ii xen-virbr0 0.1-2
> all Setup a virbr0 bridge and dnsmasq on a
> ii xenstore-utils 4.12.0-1+ub18u04.1
> amd64 Xenstore command line utilities for Xen
>
> The same xl config and grub config works in xen-4.11.1. I've searched
> for any new options in xl.cfg that could influence this, but nothing
> catches my eye.
Do same kernel and initrd work fine when booted as PV or HVM?
Thanks, Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 13:23 ` Andrew Cooper
0 siblings, 0 replies; 18+ messages in thread
From: Andrew Cooper @ 2019-04-16 13:23 UTC (permalink / raw)
To: Pry Mar, xen-devel; +Cc: M A Young
[-- Attachment #1.1: Type: text/plain, Size: 1962 bytes --]
On 16/04/2019 00:18, Pry Mar wrote:
> Hello,
>
> https://paste.debian.net/1077718/
>
> I get a kernel panic as shown in the paste above no matter how I
> launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
> pvgrub2 (i386-xen_pvh support).
>From the log:
> traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95 sp:7ffe3099cdb8 error:0 in ld-2.29.so[7f797dc61000+21000]
Can you disassemble ld-2.29.so and find out what that instruction is?
It is almost certainly a related factor.
> [ 1.127818] Run /init as init process
> [ 1.130195] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
> [ 1.130230] CPU: 0 PID: 1 Comm: init Not tainted 5.0.0-8-generic #9-Ubuntu
> [ 1.130243] Call Trace:
> [ 1.130284] dump_stack+0x63/0x8a
> [ 1.130296] panic+0x101/0x2a7
> [ 1.130306] do_exit.cold.24+0x26/0x75
> [ 1.130315] do_group_exit+0x43/0xb0
> [ 1.130325] get_signal+0x139/0x6d0
> [ 1.130336] do_signal+0x34/0x710
> [ 1.130345] ? do_trap+0xda/0xe0
> [ 1.130375] exit_to_usermode_loop+0x8e/0x100
> [ 1.130387] prepare_exit_to_usermode+0x5a/0x80
> [ 1.130399] ? invalid_op+0xa/0x20
> [ 1.130408] retint_user+0x8/0x8
> [ 1.130418] RIP: 0033:0x7feef6fe4b95
> [ 1.130433] Code: Bad RIP value.
> [ 1.130441] RSP: 002b:00007ffdda330e78 EFLAGS: 00010246
> [ 1.130452] RAX: 000000000000000c RBX: 0000000000000001 RCX: 000000000000000b
> [ 1.130466] RDX: 0000000000000042 RSI: 00007feef6fecd75 RDI: 0000000000000000
> [ 1.130479] RBP: 000055c1b07f7040 R08: 0000000000000019 R09: 0000000000000001
> [ 1.130493] R10: 0000000000000000 R11: 000000000000004d R12: 000000000000000b
> [ 1.130507] R13: 00007feef6fcb810 R14: 0000000000000000 R15: 00007ffdda331119
> [ 1.130733] Kernel Offset: 0x2400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
This looks to be related to the #UD from above, but rather more fatal.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2563 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 13:23 ` Andrew Cooper
0 siblings, 0 replies; 18+ messages in thread
From: Andrew Cooper @ 2019-04-16 13:23 UTC (permalink / raw)
To: Pry Mar, xen-devel; +Cc: M A Young
[-- Attachment #1.1: Type: text/plain, Size: 1961 bytes --]
On 16/04/2019 00:18, Pry Mar wrote:
> Hello,
>
> https://paste.debian.net/1077718/
>
> I get a kernel panic as shown in the paste above no matter how I
> launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
> pvgrub2 (i386-xen_pvh support).
From the log:
> traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95 sp:7ffe3099cdb8 error:0 in ld-2.29.so[7f797dc61000+21000]
Can you disassemble ld-2.29.so and find out what that instruction is?
It is almost certainly a related factor.
> [ 1.127818] Run /init as init process
> [ 1.130195] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
> [ 1.130230] CPU: 0 PID: 1 Comm: init Not tainted 5.0.0-8-generic #9-Ubuntu
> [ 1.130243] Call Trace:
> [ 1.130284] dump_stack+0x63/0x8a
> [ 1.130296] panic+0x101/0x2a7
> [ 1.130306] do_exit.cold.24+0x26/0x75
> [ 1.130315] do_group_exit+0x43/0xb0
> [ 1.130325] get_signal+0x139/0x6d0
> [ 1.130336] do_signal+0x34/0x710
> [ 1.130345] ? do_trap+0xda/0xe0
> [ 1.130375] exit_to_usermode_loop+0x8e/0x100
> [ 1.130387] prepare_exit_to_usermode+0x5a/0x80
> [ 1.130399] ? invalid_op+0xa/0x20
> [ 1.130408] retint_user+0x8/0x8
> [ 1.130418] RIP: 0033:0x7feef6fe4b95
> [ 1.130433] Code: Bad RIP value.
> [ 1.130441] RSP: 002b:00007ffdda330e78 EFLAGS: 00010246
> [ 1.130452] RAX: 000000000000000c RBX: 0000000000000001 RCX: 000000000000000b
> [ 1.130466] RDX: 0000000000000042 RSI: 00007feef6fecd75 RDI: 0000000000000000
> [ 1.130479] RBP: 000055c1b07f7040 R08: 0000000000000019 R09: 0000000000000001
> [ 1.130493] R10: 0000000000000000 R11: 000000000000004d R12: 000000000000000b
> [ 1.130507] R13: 00007feef6fcb810 R14: 0000000000000000 R15: 00007ffdda331119
> [ 1.130733] Kernel Offset: 0x2400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
This looks to be related to the #UD from above, but rather more fatal.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2563 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 18:27 ` Pry Mar
0 siblings, 0 replies; 18+ messages in thread
From: Pry Mar @ 2019-04-16 18:27 UTC (permalink / raw)
To: Roger Pau Monné; +Cc: xen-devel
On 4/16/19, Roger Pau Monné <roger.pau@citrix.com> wrote:
> On Mon, Apr 15, 2019 at 04:18:57PM -0700, Pry Mar wrote:
>> Hello,
>>
>> https://paste.debian.net/1077718/
>>
>> I get a kernel panic as shown in the paste above no matter how I
>> launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
>> pvgrub2 (i386-xen_pvh support).
>>
>> The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
>> packages (self built).
>> ~$ sudo dpkg -l | grep -P 'xen|qemu' | grep '^ii'
>> ii libxen-4.12:amd64 4.12.0-1+ub18u04.1 amd64
>> Public libs for Xen
>> ii libxenstore3.0:amd64 4.12.0-1+ub18u04.1 amd64
>> Xenstore communications library for Xen
>> ii libxentoolcore1:amd64 4.12.0-1+ub18u04.1 amd64
>> helper for qemu & libxenstore
>> ii qemuu 3.1.0-1+ub18u04.1 amd64
>> qemu-system-i386 (3.1.0/xen-4.12) with 9pfs support
>> ii xen-hypervisor-4.12-amd64 4.12.0-1+ub18u04.1
>> amd64 Xen Hypervisor on AMD64
>> ii xen-utils-4.12 4.12.0-1+ub18u04.1
>> amd64 XEN administrative tools
>> ii xen-utils-common 4.12.0-1+ub18u04.1
>> all Xen administrative tools - common files
>> ii xen-virbr0 0.1-2
>> all Setup a virbr0 bridge and dnsmasq on a
>> ii xenstore-utils 4.12.0-1+ub18u04.1
>> amd64 Xenstore command line utilities for Xen
>>
>> The same xl config and grub config works in xen-4.11.1. I've searched
>> for any new options in xl.cfg that could influence this, but nothing
>> catches my eye.
>
> Do same kernel and initrd work fine when booted as PV or HVM?
>
> Thanks, Roger.
>
yes, I tried PV, but not HVM. None of the ld*.so errors appear
traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95
sp:7ffe3099cdb8 error:0 in ld-2.29.so[7f797dc61000+21000]
the log is similar as booting pvh in 4.11.1 for pv.
hth,
PryMar56
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 18:27 ` Pry Mar
0 siblings, 0 replies; 18+ messages in thread
From: Pry Mar @ 2019-04-16 18:27 UTC (permalink / raw)
To: Roger Pau Monné; +Cc: xen-devel
On 4/16/19, Roger Pau Monné <roger.pau@citrix.com> wrote:
> On Mon, Apr 15, 2019 at 04:18:57PM -0700, Pry Mar wrote:
>> Hello,
>>
>> https://paste.debian.net/1077718/
>>
>> I get a kernel panic as shown in the paste above no matter how I
>> launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
>> pvgrub2 (i386-xen_pvh support).
>>
>> The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
>> packages (self built).
>> ~$ sudo dpkg -l | grep -P 'xen|qemu' | grep '^ii'
>> ii libxen-4.12:amd64 4.12.0-1+ub18u04.1 amd64
>> Public libs for Xen
>> ii libxenstore3.0:amd64 4.12.0-1+ub18u04.1 amd64
>> Xenstore communications library for Xen
>> ii libxentoolcore1:amd64 4.12.0-1+ub18u04.1 amd64
>> helper for qemu & libxenstore
>> ii qemuu 3.1.0-1+ub18u04.1 amd64
>> qemu-system-i386 (3.1.0/xen-4.12) with 9pfs support
>> ii xen-hypervisor-4.12-amd64 4.12.0-1+ub18u04.1
>> amd64 Xen Hypervisor on AMD64
>> ii xen-utils-4.12 4.12.0-1+ub18u04.1
>> amd64 XEN administrative tools
>> ii xen-utils-common 4.12.0-1+ub18u04.1
>> all Xen administrative tools - common files
>> ii xen-virbr0 0.1-2
>> all Setup a virbr0 bridge and dnsmasq on a
>> ii xenstore-utils 4.12.0-1+ub18u04.1
>> amd64 Xenstore command line utilities for Xen
>>
>> The same xl config and grub config works in xen-4.11.1. I've searched
>> for any new options in xl.cfg that could influence this, but nothing
>> catches my eye.
>
> Do same kernel and initrd work fine when booted as PV or HVM?
>
> Thanks, Roger.
>
yes, I tried PV, but not HVM. None of the ld*.so errors appear
traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95
sp:7ffe3099cdb8 error:0 in ld-2.29.so[7f797dc61000+21000]
the log is similar as booting pvh in 4.11.1 for pv.
hth,
PryMar56
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 22:17 ` M A Young
0 siblings, 0 replies; 18+ messages in thread
From: M A Young @ 2019-04-16 22:17 UTC (permalink / raw)
To: Andrew Cooper; +Cc: xen-devel, Pry Mar
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1589 bytes --]
On Tue, 16 Apr 2019, Andrew Cooper wrote:
> From the log:
>
> traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95 sp:7ffe3099cdb8 erro
> r:0 in ld-2.29.so[7f797dc61000+21000]
>
>
> Can you disassemble ld-2.29.so and find out what that instruction is? It is
> almost certainly a related factor.
I get lines like
[ 1.384356] traps: modprobe[36] trap invalid opcode ip:7f57448af179
sp:7fff8fc3a938 error:0 in ld-2.29.so[7f5744895000+20000]
I am guessing the right place to look in ld-2.29.so is
0x7f57448af179-0x7f57448950000-20000 = 86873 in which case I get
(gdb) x/10i 86873
0x15359 <_dl_close_worker+3593>: mov (%rsi,%rcx,8),%r8
0x1535d <_dl_close_worker+3597>: testb $0x20,0x31d(%r8)
0x15365 <_dl_close_worker+3605>: jne 0x15375
<_dl_close_worker+3621>
0x15367 <_dl_close_worker+3607>: cmp %ecx,%edx
0x15369 <_dl_close_worker+3609>: je 0x15372
<_dl_close_worker+3618>
0x1536b <_dl_close_worker+3611>: mov %edx,%r9d
0x1536e <_dl_close_worker+3614>: mov %r8,(%rsi,%r9,8)
0x15372 <_dl_close_worker+3618>: add $0x1,%edx
0x15375 <_dl_close_worker+3621>: add $0x1,%rcx
0x15379 <_dl_close_worker+3625>: cmp %ecx,%eax
Some more lines like this are
[ 1.571479] traps: modprobe[41] trap invalid opcode ip:7f3e3628d179
sp:7ffc86abbe08 error:0 in ld-2.29.so[7f3e36273000+20000]
[ 1.630562] traps: modprobe[43] trap invalid opcode ip:7f227b39a179
sp:7ffdfd943198 error:0 in ld-2.29.so[7f227b380000+20000]
which all seem to get to the same place. Is this useful or am I looking in
the wrong place?
Michael Young
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-04-16 22:17 ` M A Young
0 siblings, 0 replies; 18+ messages in thread
From: M A Young @ 2019-04-16 22:17 UTC (permalink / raw)
To: Andrew Cooper; +Cc: xen-devel, Pry Mar
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1589 bytes --]
On Tue, 16 Apr 2019, Andrew Cooper wrote:
> From the log:
>
> traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95 sp:7ffe3099cdb8 erro
> r:0 in ld-2.29.so[7f797dc61000+21000]
>
>
> Can you disassemble ld-2.29.so and find out what that instruction is? It is
> almost certainly a related factor.
I get lines like
[ 1.384356] traps: modprobe[36] trap invalid opcode ip:7f57448af179
sp:7fff8fc3a938 error:0 in ld-2.29.so[7f5744895000+20000]
I am guessing the right place to look in ld-2.29.so is
0x7f57448af179-0x7f57448950000-20000 = 86873 in which case I get
(gdb) x/10i 86873
0x15359 <_dl_close_worker+3593>: mov (%rsi,%rcx,8),%r8
0x1535d <_dl_close_worker+3597>: testb $0x20,0x31d(%r8)
0x15365 <_dl_close_worker+3605>: jne 0x15375
<_dl_close_worker+3621>
0x15367 <_dl_close_worker+3607>: cmp %ecx,%edx
0x15369 <_dl_close_worker+3609>: je 0x15372
<_dl_close_worker+3618>
0x1536b <_dl_close_worker+3611>: mov %edx,%r9d
0x1536e <_dl_close_worker+3614>: mov %r8,(%rsi,%r9,8)
0x15372 <_dl_close_worker+3618>: add $0x1,%edx
0x15375 <_dl_close_worker+3621>: add $0x1,%rcx
0x15379 <_dl_close_worker+3625>: cmp %ecx,%eax
Some more lines like this are
[ 1.571479] traps: modprobe[41] trap invalid opcode ip:7f3e3628d179
sp:7ffc86abbe08 error:0 in ld-2.29.so[7f3e36273000+20000]
[ 1.630562] traps: modprobe[43] trap invalid opcode ip:7f227b39a179
sp:7ffdfd943198 error:0 in ld-2.29.so[7f227b380000+20000]
which all seem to get to the same place. Is this useful or am I looking in
the wrong place?
Michael Young
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-05-31 19:18 ` YOUNG, MICHAEL A.
0 siblings, 0 replies; 18+ messages in thread
From: YOUNG, MICHAEL A. @ 2019-05-31 19:18 UTC (permalink / raw)
To: Andrew Cooper; +Cc: xen-devel, Pry Mar
On Tue, 16 Apr 2019, M A Young wrote:
> On Tue, 16 Apr 2019, Andrew Cooper wrote:
>
>> From the log:
>>
>> traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95 sp:7ffe3099cdb8 erro
>> r:0 in ld-2.29.so[7f797dc61000+21000]
>>
>>
>> Can you disassemble ld-2.29.so and find out what that instruction is? It is
>> almost certainly a related factor.
>
> I get lines like
> [ 1.384356] traps: modprobe[36] trap invalid opcode ip:7f57448af179
> sp:7fff8fc3a938 error:0 in ld-2.29.so[7f5744895000+20000]
>
> I am guessing the right place to look in ld-2.29.so is
> 0x7f57448af179-0x7f57448950000-20000 = 86873 in which case I get
> (gdb) x/10i 86873
> 0x15359 <_dl_close_worker+3593>: mov (%rsi,%rcx,8),%r8
> 0x1535d <_dl_close_worker+3597>: testb $0x20,0x31d(%r8)
> 0x15365 <_dl_close_worker+3605>: jne 0x15375
> <_dl_close_worker+3621>
> 0x15367 <_dl_close_worker+3607>: cmp %ecx,%edx
> 0x15369 <_dl_close_worker+3609>: je 0x15372
> <_dl_close_worker+3618>
> 0x1536b <_dl_close_worker+3611>: mov %edx,%r9d
> 0x1536e <_dl_close_worker+3614>: mov %r8,(%rsi,%r9,8)
> 0x15372 <_dl_close_worker+3618>: add $0x1,%edx
> 0x15375 <_dl_close_worker+3621>: add $0x1,%rcx
> 0x15379 <_dl_close_worker+3625>: cmp %ecx,%eax
>
> Some more lines like this are
> [ 1.571479] traps: modprobe[41] trap invalid opcode ip:7f3e3628d179
> sp:7ffc86abbe08 error:0 in ld-2.29.so[7f3e36273000+20000]
> [ 1.630562] traps: modprobe[43] trap invalid opcode ip:7f227b39a179
> sp:7ffdfd943198 error:0 in ld-2.29.so[7f227b380000+20000]
> which all seem to get to the same place. Is this useful or am I looking in
> the wrong place?
I did a bisect on this issue, and it identified the first bad commit as
fd32dcfe4c9a539f8e5d26ff4c5ca50ee54556b2
x86/vmx: Don't leak EFER.NXE into guest context
Michael Young
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-05-31 19:18 ` YOUNG, MICHAEL A.
0 siblings, 0 replies; 18+ messages in thread
From: YOUNG, MICHAEL A. @ 2019-05-31 19:18 UTC (permalink / raw)
To: Andrew Cooper; +Cc: xen-devel, Pry Mar
On Tue, 16 Apr 2019, M A Young wrote:
> On Tue, 16 Apr 2019, Andrew Cooper wrote:
>
>> From the log:
>>
>> traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95 sp:7ffe3099cdb8 erro
>> r:0 in ld-2.29.so[7f797dc61000+21000]
>>
>>
>> Can you disassemble ld-2.29.so and find out what that instruction is? It is
>> almost certainly a related factor.
>
> I get lines like
> [ 1.384356] traps: modprobe[36] trap invalid opcode ip:7f57448af179
> sp:7fff8fc3a938 error:0 in ld-2.29.so[7f5744895000+20000]
>
> I am guessing the right place to look in ld-2.29.so is
> 0x7f57448af179-0x7f57448950000-20000 = 86873 in which case I get
> (gdb) x/10i 86873
> 0x15359 <_dl_close_worker+3593>: mov (%rsi,%rcx,8),%r8
> 0x1535d <_dl_close_worker+3597>: testb $0x20,0x31d(%r8)
> 0x15365 <_dl_close_worker+3605>: jne 0x15375
> <_dl_close_worker+3621>
> 0x15367 <_dl_close_worker+3607>: cmp %ecx,%edx
> 0x15369 <_dl_close_worker+3609>: je 0x15372
> <_dl_close_worker+3618>
> 0x1536b <_dl_close_worker+3611>: mov %edx,%r9d
> 0x1536e <_dl_close_worker+3614>: mov %r8,(%rsi,%r9,8)
> 0x15372 <_dl_close_worker+3618>: add $0x1,%edx
> 0x15375 <_dl_close_worker+3621>: add $0x1,%rcx
> 0x15379 <_dl_close_worker+3625>: cmp %ecx,%eax
>
> Some more lines like this are
> [ 1.571479] traps: modprobe[41] trap invalid opcode ip:7f3e3628d179
> sp:7ffc86abbe08 error:0 in ld-2.29.so[7f3e36273000+20000]
> [ 1.630562] traps: modprobe[43] trap invalid opcode ip:7f227b39a179
> sp:7ffdfd943198 error:0 in ld-2.29.so[7f227b380000+20000]
> which all seem to get to the same place. Is this useful or am I looking in
> the wrong place?
I did a bisect on this issue, and it identified the first bad commit as
fd32dcfe4c9a539f8e5d26ff4c5ca50ee54556b2
x86/vmx: Don't leak EFER.NXE into guest context
Michael Young
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-05-31 22:16 ` Andrew Cooper
0 siblings, 0 replies; 18+ messages in thread
From: Andrew Cooper @ 2019-05-31 22:16 UTC (permalink / raw)
To: YOUNG, MICHAEL A.; +Cc: xen-devel, Pry Mar
On 31/05/2019 12:18, YOUNG, MICHAEL A. wrote:
> On Tue, 16 Apr 2019, M A Young wrote:
>
>> On Tue, 16 Apr 2019, Andrew Cooper wrote:
>>
>>> From the log:
>>>
>>> traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95 sp:7ffe3099cdb8 erro
>>> r:0 in ld-2.29.so[7f797dc61000+21000]
>>>
>>>
>>> Can you disassemble ld-2.29.so and find out what that instruction is? It is
>>> almost certainly a related factor.
>> I get lines like
>> [ 1.384356] traps: modprobe[36] trap invalid opcode ip:7f57448af179
>> sp:7fff8fc3a938 error:0 in ld-2.29.so[7f5744895000+20000]
>>
>> I am guessing the right place to look in ld-2.29.so is
>> 0x7f57448af179-0x7f57448950000-20000 = 86873 in which case I get
>> (gdb) x/10i 86873
>> 0x15359 <_dl_close_worker+3593>: mov (%rsi,%rcx,8),%r8
>> 0x1535d <_dl_close_worker+3597>: testb $0x20,0x31d(%r8)
>> 0x15365 <_dl_close_worker+3605>: jne 0x15375
>> <_dl_close_worker+3621>
>> 0x15367 <_dl_close_worker+3607>: cmp %ecx,%edx
>> 0x15369 <_dl_close_worker+3609>: je 0x15372
>> <_dl_close_worker+3618>
>> 0x1536b <_dl_close_worker+3611>: mov %edx,%r9d
>> 0x1536e <_dl_close_worker+3614>: mov %r8,(%rsi,%r9,8)
>> 0x15372 <_dl_close_worker+3618>: add $0x1,%edx
>> 0x15375 <_dl_close_worker+3621>: add $0x1,%rcx
>> 0x15379 <_dl_close_worker+3625>: cmp %ecx,%eax
>>
>> Some more lines like this are
>> [ 1.571479] traps: modprobe[41] trap invalid opcode ip:7f3e3628d179
>> sp:7ffc86abbe08 error:0 in ld-2.29.so[7f3e36273000+20000]
>> [ 1.630562] traps: modprobe[43] trap invalid opcode ip:7f227b39a179
>> sp:7ffdfd943198 error:0 in ld-2.29.so[7f227b380000+20000]
>> which all seem to get to the same place. Is this useful or am I looking in
>> the wrong place?
> I did a bisect on this issue, and it identified the first bad commit as
> fd32dcfe4c9a539f8e5d26ff4c5ca50ee54556b2
> x86/vmx: Don't leak EFER.NXE into guest context
Aah - this will be a harpertown core.
You need e28c0ee3356f52f589bbae54e89aaed25c1f599d from staging, which
has been backported to staging-4.12
(8457c15b981ba04c0709e6f25af3b76beb34cafa) two weeks ago.
This but accidentally resulted in the SYSCALL instruction being disabled
behind the back of the guest, which broke all userspace system calls.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-05-31 22:16 ` Andrew Cooper
0 siblings, 0 replies; 18+ messages in thread
From: Andrew Cooper @ 2019-05-31 22:16 UTC (permalink / raw)
To: YOUNG, MICHAEL A.; +Cc: xen-devel, Pry Mar
On 31/05/2019 12:18, YOUNG, MICHAEL A. wrote:
> On Tue, 16 Apr 2019, M A Young wrote:
>
>> On Tue, 16 Apr 2019, Andrew Cooper wrote:
>>
>>> From the log:
>>>
>>> traps: modprobe[48] trap invalid opcode ip:7f797dc7bb95 sp:7ffe3099cdb8 erro
>>> r:0 in ld-2.29.so[7f797dc61000+21000]
>>>
>>>
>>> Can you disassemble ld-2.29.so and find out what that instruction is? It is
>>> almost certainly a related factor.
>> I get lines like
>> [ 1.384356] traps: modprobe[36] trap invalid opcode ip:7f57448af179
>> sp:7fff8fc3a938 error:0 in ld-2.29.so[7f5744895000+20000]
>>
>> I am guessing the right place to look in ld-2.29.so is
>> 0x7f57448af179-0x7f57448950000-20000 = 86873 in which case I get
>> (gdb) x/10i 86873
>> 0x15359 <_dl_close_worker+3593>: mov (%rsi,%rcx,8),%r8
>> 0x1535d <_dl_close_worker+3597>: testb $0x20,0x31d(%r8)
>> 0x15365 <_dl_close_worker+3605>: jne 0x15375
>> <_dl_close_worker+3621>
>> 0x15367 <_dl_close_worker+3607>: cmp %ecx,%edx
>> 0x15369 <_dl_close_worker+3609>: je 0x15372
>> <_dl_close_worker+3618>
>> 0x1536b <_dl_close_worker+3611>: mov %edx,%r9d
>> 0x1536e <_dl_close_worker+3614>: mov %r8,(%rsi,%r9,8)
>> 0x15372 <_dl_close_worker+3618>: add $0x1,%edx
>> 0x15375 <_dl_close_worker+3621>: add $0x1,%rcx
>> 0x15379 <_dl_close_worker+3625>: cmp %ecx,%eax
>>
>> Some more lines like this are
>> [ 1.571479] traps: modprobe[41] trap invalid opcode ip:7f3e3628d179
>> sp:7ffc86abbe08 error:0 in ld-2.29.so[7f3e36273000+20000]
>> [ 1.630562] traps: modprobe[43] trap invalid opcode ip:7f227b39a179
>> sp:7ffdfd943198 error:0 in ld-2.29.so[7f227b380000+20000]
>> which all seem to get to the same place. Is this useful or am I looking in
>> the wrong place?
> I did a bisect on this issue, and it identified the first bad commit as
> fd32dcfe4c9a539f8e5d26ff4c5ca50ee54556b2
> x86/vmx: Don't leak EFER.NXE into guest context
Aah - this will be a harpertown core.
You need e28c0ee3356f52f589bbae54e89aaed25c1f599d from staging, which
has been backported to staging-4.12
(8457c15b981ba04c0709e6f25af3b76beb34cafa) two weeks ago.
This but accidentally resulted in the SYSCALL instruction being disabled
behind the back of the guest, which broke all userspace system calls.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-06-01 12:03 ` YOUNG, MICHAEL A.
0 siblings, 0 replies; 18+ messages in thread
From: YOUNG, MICHAEL A. @ 2019-06-01 12:03 UTC (permalink / raw)
To: Andrew Cooper; +Cc: xen-devel, Pry Mar
On Fri, 31 May 2019, Andrew Cooper wrote:
>> I did a bisect on this issue, and it identified the first bad commit as
>> fd32dcfe4c9a539f8e5d26ff4c5ca50ee54556b2
>> x86/vmx: Don't leak EFER.NXE into guest context
>
> Aah - this will be a harpertown core.
>
> You need e28c0ee3356f52f589bbae54e89aaed25c1f599d from staging, which
> has been backported to staging-4.12
> (8457c15b981ba04c0709e6f25af3b76beb34cafa) two weeks ago.
>
> This but accidentally resulted in the SYSCALL instruction being disabled
> behind the back of the guest, which broke all userspace system calls.
Thanks, that patch fixes the DomU boot problem I was seeing.
Michael Young
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] booting domU guest as pvh works in xen-4.11.1 but fails in 4.12
@ 2019-06-01 12:03 ` YOUNG, MICHAEL A.
0 siblings, 0 replies; 18+ messages in thread
From: YOUNG, MICHAEL A. @ 2019-06-01 12:03 UTC (permalink / raw)
To: Andrew Cooper; +Cc: xen-devel, Pry Mar
On Fri, 31 May 2019, Andrew Cooper wrote:
>> I did a bisect on this issue, and it identified the first bad commit as
>> fd32dcfe4c9a539f8e5d26ff4c5ca50ee54556b2
>> x86/vmx: Don't leak EFER.NXE into guest context
>
> Aah - this will be a harpertown core.
>
> You need e28c0ee3356f52f589bbae54e89aaed25c1f599d from staging, which
> has been backported to staging-4.12
> (8457c15b981ba04c0709e6f25af3b76beb34cafa) two weeks ago.
>
> This but accidentally resulted in the SYSCALL instruction being disabled
> behind the back of the guest, which broke all userspace system calls.
Thanks, that patch fixes the DomU boot problem I was seeing.
Michael Young
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2019-06-01 12:04 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-15 23:18 booting domU guest as pvh works in xen-4.11.1 but fails in 4.12 Pry Mar
2019-04-15 23:18 ` [Xen-devel] " Pry Mar
2019-04-16 8:10 ` M A Young
2019-04-16 8:10 ` [Xen-devel] " M A Young
2019-04-16 9:10 ` Roger Pau Monné
2019-04-16 9:10 ` [Xen-devel] " Roger Pau Monné
2019-04-16 18:27 ` Pry Mar
2019-04-16 18:27 ` [Xen-devel] " Pry Mar
2019-04-16 13:23 ` Andrew Cooper
2019-04-16 13:23 ` [Xen-devel] " Andrew Cooper
2019-04-16 22:17 ` M A Young
2019-04-16 22:17 ` [Xen-devel] " M A Young
2019-05-31 19:18 ` YOUNG, MICHAEL A.
2019-05-31 19:18 ` [Xen-devel] " YOUNG, MICHAEL A.
2019-05-31 22:16 ` Andrew Cooper
2019-05-31 22:16 ` [Xen-devel] " Andrew Cooper
2019-06-01 12:03 ` YOUNG, MICHAEL A.
2019-06-01 12:03 ` [Xen-devel] " YOUNG, MICHAEL A.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.