Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Problem with Ubuntu 16.04 PV clients



On Fri, 24 Jun 2016 09:22:09 +0200
Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:

> On Thu, Jun 23, 2016 at 05:04:15PM -0600, Greg Oster wrote:
> > On Thu, 23 Jun 2016 12:09:12 -0600
> > Greg Oster <oster%netbsd.org@localhost> wrote:
> >   
> > > On Thu, 23 Jun 2016 16:16:30 +1200
> > > Mark Davies <mark%ecs.vuw.ac.nz@localhost> wrote:
> > >   
> > > > On Tue, 21 Jun 2016 14:07:09 Greg Oster wrote:    
> > > > > > I was seeing the same issue... but I've only debugged it to
> > > > > > the point
> > > > > > 
> > > > > > where if change my 'disk' line to:
> > > > > >  disk = [ ]
> > > > > > 
> > > > > > then it gets past that error..... (not to anything useful,
> > > > > > of course, because it can't find the installation CD or the
> > > > > > disks...)      
> > > > > 
> > > > > I forgot to mention:
> > > > > 
> > > > > This is on NetBSD-6.1.4/amd64 with Xen4.1 dom0.      
> > > > 
> > > > Yes, if I change the disk line to "disk = [ ]" it gets into
> > > > running the ubuntu install script but not usefully as you say
> > > > as there is no disk. This is NetBSD 7.0_STABLE/amd64 with
> > > > either Xen4.2 dom0 or 4.5 dom0
> > > > 
> > > > So how can we debug this further?    
> > > 
> > > I pulled down a kernel from here:
> > > 
> > >  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc4-yakkety/
> > > 
> > > and while it doesn't crash, it also doesn't see the CDROM (image)
> > > or the disk :(  'dmesg' shows the errors:
> > > 
> > > [    1.230336] xenbus_probe_frontend: Device with no driver:
> > > device/vbd/768
> > > [    1.230343] xenbus_probe_frontend: Device with no driver:
> > > device/vbd/5632
> > > [    1.230350] xenbus_probe_frontend: Device with no driver:
> > > device/vif/0
> > > 
> > > which makes me wonder if the initrg.gz I'm using (from the 16.04
> > > iso image) is still missing something...  
> > 
> > I've also tried the kernel and initrd.gz from here, with no further
> > luck:
> > 
> > http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/netboot/xen/  
> 
> with this, the domU crashes just after
> "No PS/2 controller found. Probing ports directly"
> (XEN) Domain 271 (vcpu#0) crashed on cpu#7:
> (XEN) ----[ Xen-4.5.2  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    7
> (XEN) RIP:    e033:[<ffffffff8106c037>]
> (XEN) RFLAGS: 0000000000010207   EM: 1   CONTEXT: pv guest (d271v0)
> (XEN) rax: ffffffff81829db8   rbx: ffffffff8106c037   rcx:
> ffffffff8126396f (XEN) rdx: ffffffff8106c037   rsi:
> ffffffff8182a5e8   rdi: ffffffff81829590 (XEN) rbp:
> ffff88003e1aa038   rsp: ffff88003e1aa038   r8:  0000000000030001
> (XEN) r9:  00000000000000d1   r10: ffffea00001c5500   r11:
> 00000000000000d1 (XEN) r12: ffff88003e2f8000   r13:
> 0000000000000000   r14: 000000000000000b (XEN) r15:
> ffffffff81829db8   cr0: 000000008005003b   cr4: 00000000000026f4
> (XEN) cr3: 000000016bafb000   cr2: ffffffff81829db8 (XEN) ds: 0000
> es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033 (XEN) Guest
> stack trace from rsp=ffff88003e1aa038: [...]
> 
> I've also seen:
> [    0.585176] xen_netfront: Initialising Xen virtual ethernet driver
> [    0.587485] BUG: unable to handle kernel NULL pointer dereference
> at 0000000000000008 [    0.587517] IP: [<ffffffff813ef6e7>]
> rb_insert_color+0x17/0x190 [    0.587541] PGD 0
> [    0.587552] Oops: 0000 [#1] SMP
> [    0.587566] Modules linked in:
> [    0.587582] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
> 4.4.0-21-generic #37-Ubuntu [    0.587598] task: ffff88003e2f8000 ti:
> ffff88003e3àQÿÿsk.ti: fJÿÿe300000 [    0.587612] RIP:
> e030:[<ffffffff813ef6e7>]  [<ffffffff813ef6e7>]
> rb_insert_color+0x17/0x190 [    0.587631] RSP: e02@Rÿÿ003e303dLÿÿGS:
> 00010246 [    0.587640] RAX: 0000000000000000 RBX: 0000000000000000
> RCX: 0000000000000006 [    0.587651] RDX: ffff8800071d Rÿÿ:
> ffff88Nÿÿ00 RDI: ffff880007165540 [    0.587662] RBP:
> ffff88003e303d10 R08: 000000000001a260 R09: ffffffff813eadcc
> [    0.587673] R10: Sÿÿ00f6b800Pÿÿ0000000000000b R12:
> ffff880007165528 [    0.587684] R13: ffff8800071c2bb8 R14:
> ffff8800071c2bb8 R15: 0000000000000000 [    0.5`SÿÿS:
> 0000Rÿÿ0000(0000) GS:ffff88003f900000(0000) knlGS:0000000000000000
> [    0.587718] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> [ÀSÿÿ7728] CRTÿÿ00000000008 CR3: 0000000001e0a000 CR4:
> 0000000000002660
> 
> do you get something else ?

With the stock 16.04 vmlinuz and initrd.gz I get:

(XEN) domain_crash_sync called from entry.S
(XEN) Domain 36 (vcpu#0) crashed on cpu#2:
(XEN) ----[ Xen-4.1.6.1  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    2
(XEN) RIP:    e033:[<ffffffff8106b7a0>]
(XEN) RFLAGS: 0000000000010297   EM: 1   CONTEXT: pv guest
(XEN) rax: 0000000081825057   rbx: 0000000000000001   rcx:
ffffffff81825057 
(XEN) rdx: ffff880002b80200   rsi: 0000000000000010
rdi: ffff88003e35a008 
(XEN) rbp: ffff88003e38bbc0   rsp:
ffff88003e35a000   r8:  ffffffff81ccc484 
(XEN) r9:  ffffffff81ccc473
r10: 00000000ffffffff   r11: ffffffff81ccc462 
(XEN) r12: ffffea00000ae000   r13: 0000000000000008   r14:
ffff880002b80000 
(XEN) r15: 0000000000000001   cr0: 000000008005003b
cr4: 00000000000026f4 
(XEN) cr3: 00000000c799a000   cr2:
ffffffff8106b7a0 
(XEN) ds: 0000 es: 0000   fs: 0000   gs: 0000   ss:
e02b   cs: e033 
(XEN) Guest stack trace from rsp=ffff88003e35a000:
(XEN)    ffffffff81826678 0000000000000001 ffff880002b80000
0000000000000008 
(XEN)    ffffea00000ae000 ffff88003e38bbc0 0000000000000001
ffffffff81ccc462 
(XEN)    00000000ffffffff ffffffff81ccc473 ffffffff81ccc484
0000000081825057 
(XEN)    ffffffff81825057 ffff880002b80200 0000000000000010
ffff88003e35a0b8 
(XEN)    ffffffffffffffff ffffffff8106b7a0 000000010000e030
0000000000010097 
(XEN)    ffff88003e35a0b0 000000000000e02b ffffffff81826678
0000000000000001 
(XEN)    ffff880002b80000 0000000000000008 ffffea00000ae000
ffff88003e38bbc0 
(XEN)    0000000000000001 ffffffff81ccc462 00000000ffffffff
ffffffff81ccc473 
(XEN)    ffffffff81ccc484 0000000081825057 ffffffff81825057
ffff880002b80200 
(XEN)    0000000000000010 ffff88003e35a168 ffffffffffffffff
ffffffff8106b7a0 
(XEN)    000000010000e030 0000000000010097 ffff88003e35a160
000000000000e02b 
(XEN)    ffffffff81826678 0000000000000001 ffff880002b80000
0000000000000008 
(XEN)    ffffea00000ae000 ffff88003e38bbc0 0000000000000001
ffffffff81ccc462 
(XEN)    00000000ffffffff ffffffff81ccc473 ffffffff81ccc484
0000000081825057 
(XEN)    ffffffff81825057 ffff880002b80200 0000000000000010
ffff88003e35a218 
(XEN)    ffffffffffffffff ffffffff8106b7a0 000000010000e030
0000000000010097 
(XEN)    ffff88003e35a210 000000000000e02b ffffffff81826678
0000000000000001 
(XEN)    ffff880002b80000 0000000000000008 ffffea00000ae000
ffff88003e38bbc0 
(XEN)    0000000000000001 ffffffff81ccc462 00000000ffffffff
ffffffff81ccc473 
(XEN)    ffffffff81ccc484 0000000081825057 ffffffff81825057
ffff880002b80200

and that's when it crashes right after printing:
...
[    0.288995] uhci_hcd: USB Universal Host Controller Interface driver
[    0.289066] i8042: PNP: No PS/2 controller found. Probing ports
directly. 
[    1.302255] i8042: No controller found
[    1.302305] clocksource: tsc: mask: 0xffffffffffffffff max_cycles:
0x22982fdf183, max_idle_ns: 440795240423 ns


Later...

Greg Oster


Home | Main Index | Thread Index | Old Index