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

[Xen-devel] xen 4.6.0 on jessie dom0 unable to start domUs and questions about systemd and build deps

To: xen-devel@xxxxxxxxxxxxx
From: Fabio Fantoni <fabio.fantoni@xxxxxxx>
Date: Sat, 10 Oct 2015 15:08:54 +0200
Cc: Wei Liu <wei.liu2@xxxxxxxxxx>, mcgrof@xxxxxxxx, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, Ian Campbell <ian.campbell@xxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Sat, 10 Oct 2015 13:08:58 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

Hi, I built xen 4.6.0 from source on jessie 64 bit system.
I cleaned some deps from too many of previous systems, built
successufull xen and upstream qemu with these dependencies:
aptitude install build-essential git-core patch python-dev uuid-dev
gettext libncurses5-dev libyajl-dev libaio-dev pkg-config libglib2.0-dev
libssl-dev libpixman-1-dev bridge-utils wget bcc iasl bin86 texinfo
libc6-dev-i386 e2fslibs-dev gcc-multilib gcc liblzma-dev zlib1g-dev
libc6-dev libsystemd-daemon-dev
# Installed seabios package from unstable
# Additional qemu deps
aptitude install libcurl4-openssl-dev libncurses5-dev libjpeg-dev
# additional spice and usbredir deps (latest spice rebuild from unstable
instead)
aptitude install libspice-protocol-dev libspice-server-dev
libusbredirparser-dev libusb-1.0-0-dev

I have dubt about some deps not installed because not blocked by
configure but that I remember was used in past, for example:
bison flex binutils graphviz gawk iproute
these or other deps are required even if configure don't check/stop and
built successfull?

I did these changes in Config.mk:
debug ?= y
PYTHON_PREFIX_ARG ?=

configure options used:
./configure --prefix=/usr --disable-blktap1 --disable-qemu-traditional
--disable-rombios --with-system-seabios=/usr/share/seabios/bios-256k.bin
--with-extra-qemuu-configure-args="--enable-spice --enable-usb-redir"
--disable-blktap2 -enable-systemd

there was an error in generated config/Tools.mk I solved manually
(replacing @debug@ with y), already reported here:
http://lists.xen.org/archives/html/xen-devel/2015-10/msg01184.html

I enabled xen services with systemd:
systemctl enable xencommons
systemctl enable xendomains
I missed or did wrong something?

And used this grub entry:

menuentry 'Jessie con Linux 3.16.0-4-amd64 e XEN 4.6 - RAID' --class
debian --class gnu-linux --class gnu --class os {
        set root='(lvm/RAID-ROOT)'
        echo    'Caricamento Hypervisor Xen 4.6...'
        multiboot       /boot/xen.gz placeholder dom0_mem=2G,max:2G
        echo    'Caricamento Linux 3.16.0-4-amd64...'
        module  /boot/vmlinuz-3.16.0-4-amd64 placeholder
root=/dev/mapper/RAID-ROOT ro quiet
        echo    'Caricamento ramdisk iniziale...'
        module  --nounzip /boot/initrd.img-3.16.0-4-amd64
}

I tried to remove swiotlb=65762 from kernel parameters used for year as
workaround that I not remember good, should be still neded?


DomU fails to start:

xl -vvv create /etc/xen/W10.cfg
Parsing config from /etc/xen/W10.cfg
libxl: debug: libxl_create.c:1557:do_domain_create: ao 0x1825260:
create: how=(nil) callback=(nil) poller=0x18252f0
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk
vdev=hda, using backend phy
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
vdev=hdb spec.backend=unknown
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk
vdev=hdb, using backend phy
libxl: debug: libxl_create.c:945:initiate_domain_create: running
bootloader
libxl: debug: libxl_bootloader.c:324:libxl__bootloader_run: not a PV
domain, skipping bootloader
libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
w=0x1826d28: deregister unregistered
libxl: detail: libxl_dom.c:239:hvm_set_viridian_features: base group
enabled
libxl: detail: libxl_dom.c:239:hvm_set_viridian_features: freq group
enabled
libxl: detail: libxl_dom.c:239:hvm_set_viridian_features:
time_ref_count group enabled
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x5bbc4
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x15bbc4
xc: detail: VIRTUAL MEMORY ARRANGEMENT:
xc: detail:   Loader:   0000000000100000->000000000015bbc4
xc: detail:   Modules:  0000000000000000->0000000000000000
xc: detail:   TOTAL:    0000000000000000->00000000f8000000
xc: detail:   ENTRY:    0000000000100630
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail:   4KB PAGES: 0x0000000000000200
xc: detail:   2MB PAGES: 0x00000000000003bf
xc: detail:   1GB PAGES: 0x0000000000000002
xc: detail: elf_load_binary: phdr 0 at 0x7f0f7a73e000 -> 0x7f0f7a790151
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x108000
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
vdev=hda spec.backend=phy
libxl: debug: libxl_event.c:639:libxl__ev_xswatch_register: watch
w=0x1828820 wpath=/local/domain/0/backend/vbd/1/768/state token=3/0:
register slotnum=3
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
vdev=hdb spec.backend=phy
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
vdev=hdb spec.backend=phy
libxl: debug: libxl_event.c:639:libxl__ev_xswatch_register: watch
w=0x1829a30 wpath=/local/domain/0/backend/vbd/1/832/state token=2/1:
register slotnum=2
libxl: debug: libxl_create.c:1580:do_domain_create: ao 0x1825260:
inprogress: poller=0x18252f0, flags=i
libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0x1828820
wpath=/local/domain/0/backend/vbd/1/768/state token=3/0: event
epath=/local/domain/0/backend/vbd/1/768/state
libxl: debug: libxl_event.c:880:devstate_callback: backend
/local/domain/0/backend/vbd/1/768/state wanted state 2 ok
libxl: debug: libxl_event.c:677:libxl__ev_xswatch_deregister: watch
w=0x1828820 wpath=/local/domain/0/backend/vbd/1/768/state token=3/0:
deregister slotnum=3
libxl: debug: libxl_device.c:937:device_backend_callback: calling
device_backend_cleanup
libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
w=0x1828820: deregister unregistered
libxl: error: libxl.c:1972:libxl__get_domid: failed to get own domid
(domid)
libxl: error: libxl_device.c:987:device_hotplug: Failed to get domid
libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
w=0x1828920: deregister unregistered
libxl: debug: libxl_event.c:545:watchfd_callback: watch
epath=/local/domain/0/backend/vbd/1/768/state token=3/0: empty slot
libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0x1829a30
wpath=/local/domain/0/backend/vbd/1/832/state token=2/1: event
epath=/local/domain/0/backend/vbd/1/832/state
libxl: debug: libxl_event.c:884:devstate_callback: backend
/local/domain/0/backend/vbd/1/832/state wanted state 2 still waiting
state 1
libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0x1829a30
wpath=/local/domain/0/backend/vbd/1/832/state token=2/1: event
epath=/local/domain/0/backend/vbd/1/832/state
libxl: debug: libxl_event.c:880:devstate_callback: backend
/local/domain/0/backend/vbd/1/832/state wanted state 2 ok
libxl: debug: libxl_event.c:677:libxl__ev_xswatch_deregister: watch
w=0x1829a30 wpath=/local/domain/0/backend/vbd/1/832/state token=2/1:
deregister slotnum=2
libxl: debug: libxl_device.c:937:device_backend_callback: calling
device_backend_cleanup
libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
w=0x1829a30: deregister unregistered
libxl: error: libxl.c:1972:libxl__get_domid: failed to get own domid
(domid)
libxl: error: libxl_device.c:987:device_hotplug: Failed to get domid
libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
w=0x1829b30: deregister unregistered
libxl: error: libxl_create.c:1174:domcreate_launch_dm: unable to add
disk devices
libxl: error: libxl_dm.c:1956:kill_device_model: unable to find device
model pid in /local/domain/1/image/device-model-pid
libxl: error: libxl.c:1628:libxl__destroy_domid:
libxl__destroy_device_model failed for 1
libxl: error: libxl.c:1972:libxl__get_domid: failed to get own domid
(domid)
libxl: error: libxl_device.c:795:libxl__initiate_device_remove: unable
to get my domid
libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
w=0x182baa0: deregister unregistered
libxl: error: libxl.c:1972:libxl__get_domid: failed to get own domid
(domid)
libxl: error: libxl.c:1972:libxl__get_domid: failed to get own domid
(domid)
libxl: error: libxl_device.c:795:libxl__initiate_device_remove: unable
to get my domid
libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
w=0x182bd90: deregister unregistered
libxl: error: libxl.c:1972:libxl__get_domid: failed to get own domid
(domid)
libxl: error: libxl.c:1665:devices_destroy_cb: libxl__devices_destroy
failed for 1
libxl: debug: libxl.c:1719:devices_destroy_cb: forked pid 1009 for
destroy of domain 1
libxl: debug: libxl_event.c:1874:libxl__ao_complete: ao 0x1825260:
complete, rc=-3
libxl: debug: libxl_event.c:1843:libxl__ao__destroy: ao 0x1825260: destroy
libxl: debug: libxl.c:1458:libxl_domain_destroy: ao 0x18290e0: create:
how=(nil) callback=(nil) poller=0x18252f0
libxl: error: libxl.c:1591:libxl__destroy_domid: non-existant domain 1
libxl: error: libxl.c:1549:domain_destroy_callback: unable to destroy
guest with domid 1
libxl: error: libxl.c:1476:domain_destroy_cb: destruction of domain 1
failed
libxl: debug: libxl_event.c:1874:libxl__ao_complete: ao 0x18290e0:
complete, rc=-21
libxl: debug: libxl.c:1467:libxl_domain_destroy: ao 0x18290e0:
inprogress: poller=0x18252f0, flags=ic
libxl: debug: libxl_event.c:1843:libxl__ao__destroy: ao 0x18290e0: destroy
xc: debug: hypercall buffer: total allocations:977 total releases:977
xc: debug: hypercall buffer: current allocations:0 maximum allocations:3
xc: debug: hypercall buffer: cache current size:3
xc: debug: hypercall buffer: cache hits:967 misses:3 toobig:7

In attachment domU xl cfg.

Xen service seems started:

systemctl status xencommons
â xencommons.service - LSB: Start/stop xenstored and xenconsoled
   Loaded: loaded (/etc/init.d/xencommons)
   Active: active (running) since sab 2015-10-10 14:23:40 CEST; 29min ago
  Process: 761 ExecStart=/etc/init.d/xencommons start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/xencommons.service
           ââ859 /usr/sbin/xenconsoled --pid-file=/var/run/xenconsoled.pid
           ââ917 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 0
-xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor
/dev/null -serial /dev/null -parallel /dev/null ...

ott 10 14:23:36 univirt xencommons[761]: Starting xenconsoled...
ott 10 14:23:36 univirt xencommons[761]: Starting QEMU as disk backend
for dom0
systemctl status xendomains
â xendomains.service - Xendomains - start and stop guests on boot and
shutdown
   Loaded: loaded (/usr/lib/systemd/system/xendomains.service; enabled)
   Active: active (exited) since sab 2015-10-10 14:23:37 CEST; 30min ago
  Process: 851 ExecStart=/usr/lib/xen/bin/xendomains start
(code=exited, status=0/SUCCESS)
  Process: 849 ExecStartPre=/bin/grep -q control_d
/proc/xen/capabilities (code=exited, status=0/SUCCESS)
 Main PID: 851 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/xendomains.service


But there are strange things:

xl list
Name                                        ID   Mem VCPUs State   Time(s)
(null)                                       0  2048     8 r-----
15.3

and:

xenstore-ls
tool = ""
 xenstored = ""
local = ""
 domain = ""
  0 = ""
   device-model = ""
    0 = ""
     state = "running"
   backend = ""
    vbd = ""
     1 = ""
      768 = ""
       frontend = "/local/domain/1/device/vbd/768"
       params = "/mnt/vm/disks/W10.disk1.xm"
       script = "/etc/xen/scripts/block"
       frontend-id = "1"
       online = "1"
       removable = "0"
       bootable = "1"
       state = "6"
       dev = "hda"
       type = "phy"
       mode = "w"
       device-type = "disk"
       discard-enable = "1"
      832 = ""
       frontend = "/local/domain/1/device/vbd/832"
       params = "/mnt/vm/iso/Windows10pro64bit.iso"
       script = "/etc/xen/scripts/block"
       frontend-id = "1"
       online = "1"
       removable = "1"
       bootable = "1"
       state = "6"
       dev = "hdb"
       type = "phy"
       mode = "r"
       device-type = "cdrom"
       discard-enable = "0"
vm = ""
libxl = ""

data about a domU not started correctly...

I not understand what is exactly is wrong.

Checking xen services I found a xendriverdomain service added recently
but not in systemd:
http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=2909ad4c96ba5527b35ac87c089116cd0320a5e7
is this needed but missed in systemd support?


Thanks for any reply and sorry for my bad english.

Attachment: W10.cfg
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] xen 4.6.0 on jessie dom0 unable to start domUs and questions about systemd and build deps
  - From: Wei Liu

Prev by Date: [Xen-devel] [linux-linus test] 62744: regressions - FAIL
Next by Date: [Xen-devel] [linux-mingo-tip-master test] 62755: regressions - trouble: blocked/broken/fail/pass
Previous by thread: [Xen-devel] [linux-linus test] 62744: regressions - FAIL
Next by thread: Re: [Xen-devel] xen 4.6.0 on jessie dom0 unable to start domUs and questions about systemd and build deps
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.