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

Re: [Xen-users] Debian 9 and device model stub domains


The xen-4.8 packages in Stretch are an `Nmu build` done by Ian Jackson, a Xen Developer. He stepped up to do that build at a difficult time when the Official Xen Maintainer was not planning to move to xen-4.8.

Since its release, Stretch has updated some important C-libs, like libc6, but the Xen packages have not kept up. They are dated May 2017, since before the Stretch release.

Today I did a monolithic build of xen-4.8, patched to HEAD, that includes all the stubdoms and the pvgrub2 binaries. They are in usr-lib-xen-boot/ here

grab the stubdom/pvgrub2 objects you need and copy them to

Its almost certain that the distro Xen packages need to be rebuilt to keep up with changes in C-libs and qemu-system-x86.
If you are interested in a debian-delta to rebuild the Xen Nmu build found in the distro repo, I've done it here

##xen-packaging on Freenode

On Thursday, August 10, 2017 9:05 PM, Brian Hoy <brian.hoy@xxxxxxxxxxx> wrote:

Hi folks,

I've rebuilt a hypervisor system on Debian 9 and used the Debian Xen
packages, however my Windows VM that uses device model stub domains will
not start:

$ xl create /etc/xen/wlgpc105
Parsing config from wlgpc105
xc: error: panic: xc_dom_core.c:208: failed to open file
'/usr/lib/xen-4.8/boot/ioemu-stubdom.gz': No such file or directory:
Internal error
libxl: error: libxl_dom.c:709:libxl__build_pv: xc_dom_kernel_file
failed: No such file or directory
libxl: error: libxl_dm.c:1932:stubdom_pvqemu_cb: error connecting nics
devices: No such file or directory
libxl: error: libxl_create.c:1504:domcreate_devmodel_started: device
model did not start: -3
libxl: error: libxl.c:1575:libxl__destroy_domid: non-existant domain 30
libxl: error: libxl.c:1534:domain_destroy_callback: unable to destroy
guest with domid 30
libxl: error: libxl.c:1463:domain_destroy_cb: destruction of domain 30

Previously when I was running on Debian 8 with a hypervisor that I
compiled myself, the ioemu-stubdom.gz file did exist. My preference
would be to use the Debian Xen packages rather than manually compiling Xen.

Does Xen 4.8.1 on Debian 9 support device model stub domains?

If so, then presumably I'm missing a package or two with components to
run stub domains, but I can figure out what that is. I have these installed:

$ dpkg -l | grep -e xen -e qemu
ii  grub-xen-bin 2.02~beta3-5                  amd64        GRand
Unified Bootloader, version 2 (Xen binaries)
ii  grub-xen-host 2.02~beta3-5                  amd64        GRand
Unified Bootloader, version 2 (Xen host version)
ii  ipxe-qemu 1.0.0+git-20161027.b991c67-1  all          PXE boot
firmware - ROM images for qemu
ii  libxen-4.8:amd64 4.8.1-1+deb9u1                amd64        Public
libs for Xen
ii  libxenstore3.0:amd64 4.8.1-1+deb9u1                amd64       
Xenstore communications library for Xen
ii  qemu-system-common 1:2.8+dfsg-6+deb9u2            amd64        QEMU
full system emulation binaries (common files)
ii  qemu-system-x86 1:2.8+dfsg-6+deb9u2            amd64        QEMU
full system emulation binaries (x86)
ii  qemu-utils 1:2.8+dfsg-6+deb9u2            amd64        QEMU utilities
ii  xen-hypervisor-4.8-amd64 4.8.1-1+deb9u1                amd64       
Xen Hypervisor on AMD64
ii  xen-linux-system-amd64 4.9+80+deb9u1                  amd64       
Xen system with Linux for 64-bit PCs (dummy package)
ii  xen-system-amd64 4.8.1-1+deb9u1                amd64        Xen
System on AMD64 (meta-package)
ii  xen-tools 4.7-1                          all          Tools to
manage Xen virtual servers
ii  xen-utils-4.8 4.8.1-1+deb9u1                amd64        XEN
administrative tools
ii  xen-utils-common 4.8.1-1+deb9u1                all          Xen
administrative tools - common files
ii  xenstore-utils 4.8.1-1+deb9u1                amd64        Xenstore
command line utilities for Xen

Any ideas? Many thanks.


Xen-users mailing list

Xen-users mailing list



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