Re: xen-4.5 and -current/amd64

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Fri, Jun 19, 2015 at 05:46:39PM -0700, Harry Waddell wrote:
> I assume you have xencommons=YES in your /etc/rc.conf, etc... 

I didn't do "etc..." though - xenconsoled and xenstored are running.
Anything else necessary?

> Here are some things you may want to try:
> 
> 1. vnconfig vnd3 /scratch/disk.img
>    and set 
> 
> 	disk = ['phy:/dev/vnd3d,xvda,w']
> 
>    to rule ount any problems with xen getting vnode devices for your file: based disks.

Tried:

vnd0: /scratch (/dev/raid6a) inode 7
disk = ['phy:/dev/vnd0d,xvda,w']
# disklabel -rt vnd0
vnd|Automatically generated label:\
        :dt=vnd:se#512:ns#32:nt#64:sc#2048:nc#1024:\
        :pa#2097152:oa#0:ta=4.2BSD:ba#0:fa#0:\
        :pd#2097152:od#0:

> 2. examine the logs in /var/logs/xen for clues. Also see "xl dmesg". 

/var/log/xen is empty(!) - the only logs are from the /dev/rraid6a attempts...
.. and nothing extra in dmesg. The end of dmesg before domU creation
attempts is:

(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=000109f0
(XEN) ioapic_guest_write: old_entry=00010000 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=2, irq=0
(XEN) ioapic_guest_write: new_entry=000109f0
(XEN) ioapic_guest_write: old_entry=000009f0 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1916: dom0: pirq 0 or irq 3 already mapped
(XEN) irq.c:1916: dom0: pirq 0 or irq 4 already mapped
(XEN) irq.c:1916: dom0: pirq 0 or irq 5 already mapped
(XEN) irq.c:1916: dom0: pirq 0 or irq 6 already mapped
(XEN) irq.c:1916: dom0: pirq 0 or irq 7 already mapped
(XEN) irq.c:1916: dom0: pirq 0 or irq 8 already mapped
(XEN) irq.c:1916: dom0: pirq 0 or irq 9 already mapped
(XEN) irq.c:1916: dom0: pirq 0 or irq 10 already mapped
(XEN) irq.c:1916: dom0: pirq 0 or irq 11 already mapped
(XEN) irq.c:1916: dom0: pirq 0 or irq 12 already mapped

> 3. Use "xl -vvvv create domname" to create the domU to get more debugging info

I don't see any more errors in there than the

libxl: error: libxl_create.c:1153:domcreate_launch_dm: unable to add disk devices

Some highlights:

libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk vdev=xvda, using backend phy

xc: detail: elf_xen_parse: __xen_guest: "GUEST_OS=NetBSD,GUEST_VER=4.99,XEN_VER=xen-3.0,LOADER=generic,VIRT_BASE=0xffffffff80000000,ELF_PADDR_OFFSET=0xffffffff80000000,VIRT_ENTRY=0xffffffff80100000,HYPERCALL_PAGE=0x00000101,BSD_SYMTAB=yes"

4.99?

and just before the error:

local/domain/0/backend/vbd/7/51712/state token=3/0: event epath=/local/domain/0/backend/vbd/7/51712/state
libxl: debug: libxl_event.c:830:devstate_watch_callback: backend /local/domain/0/backend/vbd/7/51712/state wanted state 2 ok
libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch w=0x7f7ff7b34378 wpath=/local/domain/0/backend/vbd/7/51712/state token=3/0: deregister slotnum=3
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x7f7ff7b34378: deregister unregistered
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x7f7ff7b34400: deregister unregistered
libxl: error: libxl_create.c:1153:domcreate_launch_dm: unable to add disk devices

As a quick test

name = "leucite"
kernel = "netbsd-INSTALL_XEN3_DOMU.gz"
vcpus = 2
memory = 1024

does work, adding the disk line makes it break.

I don't know that there are any more permutations of disk line left?

Cheers,

Patrick