Xen And Spice Problem

Home » General » Xen And Spice Problem
General 13 Comments

Hi

it is possible to use xen and spice already? If yes is there any howto or doc how?

If I turn on spice in cfg of a hvm domU, I get this error:

Parsing config from /etc/xen/marax.cfg libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: base group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: freq group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: time_ref_count group enabled xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0xbad04
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x1bad04
xc: detail: VIRTUAL MEMORY ARRANGEMENT:
xc: detail: Loader: 0000000000100000->00000000001bad04
xc: detail: Modules: 0000000000000000->0000000000000000
xc: detail: TOTAL: 0000000000000000->000000007f000000
xc: detail: ENTRY: 0000000000100610
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail: 4KB PAGES: 0x0000000000000200
xc: detail: 2MB PAGES: 0x00000000000003f7
xc: detail: 1GB PAGES: 0x0000000000000000
xc: detail: elf_load_binary: phdr 0 at 0x7fab7190a000 -> 0x7fab719bb151
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000
libxl: error: libxl_dm.c:1849:device_model_spawn_outcome: domain 29
device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1340:domcreate_devmodel_started: device model did not start: -3
libxl: error: libxl_dm.c:1959:kill_device_model: Device Model already exited libxl: error: libxl.c:1580:libxl__destroy_domid: non-existant domain 29
libxl: error: libxl.c:1538:domain_destroy_callback: unable to destroy guest with domid 29
libxl: error: libxl.c:1465:domain_destroy_cb: destruction of domain 29
failed

(xen-4.6rc3-4.el7.x86_64)

13 thoughts on - Xen And Spice Problem

  • Am 2015-10-01 12:24, schrieb Fabio Fantoni:
    thats the config of domU:

    builder = ‘hvm’
    memory = 2048
    vcpus=8
    boot=”c”
    name = “marax”
    disk = [ ‘phy:/dev/vg_lilith/lv_marax_c,hda,w’ ]
    vif = [
    ‘bridge=xenbr5,mac:16:3e:05:01:10,script=vif-bridge’ ]
    on_poweroff = ‘destroy’
    on_reboot = ‘restart’
    on_crash = ‘restart’
    vnc=0
    vga = ‘stdvga’
    spice = 1
    spicehost = ‘0.0.0.0’
    spiceport = 6000
    spicedisable_ticketing=1
    spicevdagent=1
    spice_clipboard_sharing=1
    localtime=1
    keymap=’de’
    viridian = 1

    where/how I can see the qemu log?

  • Am 2015-10-01 12:33, schrieb Fabio Fantoni:
    oh ok:

    qemu-system-i386: -spice port`00,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on: There is no option group ‘spice’
    spice is not supported by this qemu build. qemu-system-i386: -spice port`00,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on:
    There is no option group ‘spice’
    spice is not supported by this qemu build. qemu-system-i386: -spice port`00,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on: There is no option group ‘spice’
    spice is not supported by this qemu build. qemu: terminating on signal 1 from pid 25375
    qemu-system-i386: -spice port`00,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on:
    There is no option group ‘spice’
    spice is not supported by this qemu build. qemu-system-i386: -spice port`00,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on:
    There is no option group ‘spice’
    spice is not supported by this qemu build. qemu-system-i386: -spice port`00,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on:
    There is no option group ‘spice’
    spice is not supported by this qemu build. qemu-system-i386: -spice port`00,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on:
    There is no option group ‘spice’
    spice is not supported by this qemu build. qemu-system-i386: -spice port`00,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on:
    There is no option group ‘spice’
    spice is not supported by this qemu build. qemu-system-i386: -spice port`00,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on:
    There is no option group ‘spice’
    spice is not supported by this qemu build.

    seems to be not build in into the pkgs…

    I use this one: qemu-img-1.5.3-86.el7_1.6.x86_64
    Is there one which have spice support build in?

  • No, the qemu version will be one that is custom build for the xen package.

    Fabio, is there a toplevel config option to enable spice when building through the Xen build system?

    Please manually CC me if you can, as I’m not getting your mails to CentOS-devel…

    -George

  • Am 2015-10-01 13:30, schrieb George Dunlap:

    there is an qemu 2.0 ver in EPEL (qemu-2.0.0-1.el7.5 RPM for x86_64)
    there is the spice support build in…

  • hmm cant install it:

    Transaction check error:
    file /usr/share/locale/de_DE/LC_MESSAGES/qemu.mo from install of qemu-common-2:2.0.0-1.el7.5.x86_64 conflicts with file from package xen-runtime-4.6rc3-4.el7.x86_64
    file /usr/share/locale/fr_FR/LC_MESSAGES/qemu.mo from install of qemu-common-2:2.0.0-1.el7.5.x86_64 conflicts with file from package xen-runtime-4.6rc3-4.el7.x86_64
    file /usr/share/locale/hu/LC_MESSAGES/qemu.mo from install of qemu-common-2:2.0.0-1.el7.5.x86_64 conflicts with file from package xen-runtime-4.6rc3-4.el7.x86_64
    file /usr/share/locale/it/LC_MESSAGES/qemu.mo from install of qemu-common-2:2.0.0-1.el7.5.x86_64 conflicts with file from package xen-runtime-4.6rc3-4.el7.x86_64
    file /usr/share/locale/tr/LC_MESSAGES/qemu.mo from install of qemu-common-2:2.0.0-1.el7.5.x86_64 conflicts with file from package xen-runtime-4.6rc3-4.el7.x86_64

    is there anywhere an xen qemu with enabled spice support for CentOS7?

  • http://107.185.144.55/xen/cent7/dom0/RPMS/stable-4.6/mock/
    above is a build of upstream xen with this `configure` including spice support:./configure –enable-systemd –prefix=/usr –enable-xsmpolicy –enable-ocamltools \
      –libdir=%{_libdir} –enable-efi \
      –with-extra-qemuu-configure-args=”–enable-spice –enable-usb-redir”
    there is no associated libvirt buildIncluded are patches up to the HEAD of staging-4.6, so its basically rc5.

  • Am 2015-10-04 17:50, schrieb Mark Pryor:

    why is the spice support not in the ‘offical’ xen CentOS7 repo built in?

  • Historically, because it wasn’t available. Now, simply because it’s off by default and before now nobody had asked for it to be enabled.

    The Virt SIG is a community effort — adding a configure option and rebuilding is no problem, but the Virt SIG will need help testing /
    working out bugs in this feature if it’s going to be available going forward.

    If you’re up for helping test it / work out any bugs, I can rebuild it with the above arguments today.

    -George

  • Am 2015-10-05 12:39, schrieb George Dunlap:

    oh sure, if should find any bugs I would report it here….

  • OK, I’ve done a build of 4.6rc4 with spice enabled. You can install it with –enablerepo=virt-xen-46-candidate; I haven’t done any testing on it at all (all our test boxes are being moved today).

    Let me know how it works for you.

    -George

  • Hi

    till now it are the rpm’s with spice support working without problems
    (spice works to :) )

    there is one issue what I have found, after install does grub2-mkconfig make this entry:

    multiboot /boot/xen-4.6.0-rc-2.el7.gz placeholder…

    but I think it should be:

    multiboot /boot/xen.gz placeholder …

    with the first one it doesnt boot here, grub cant find it allthough its there in fs…