Results 1 to 3 of 3

Thread: 13.1 xen still broken?

  1. #1

    Post 13.1 xen still broken?

    Had a problem with a 12.1 machine a while back, so I have been trying to upgrade it to fix. The new Virtualization Repository is setup and the system has been updated.


    * VMM refuses to start, throwing the error:

    Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

    Now, that's REALLY weird, as there IS no libvirt-sock in that location:

    # ll /var/run/libvirt/
    total 0
    drwxr-xr-x 2 root root 40 Jan 17 14:30 libxl/
    drwx------ 2 root root 60 Jan 17 14:31 network/

    [libxl is empty]


    * The Xen kernel appears to be running:

    # ps ax | grep xen
    65 ? S 0:00 [xenwatch]
    66 ? S 0:00 [xenbus]
    729 ? Ss 0:00 avahi-daemon: running [xen.local]
    792 ? S< 0:00 [xen_pciback_wor]
    986 ? S 0:00 /usr/sbin/xenstored --pid-file /var/run/xenstored.pid
    1159 ? SLl 0:00 /usr/sbin/xenconsoled --pid-file=/var/run/xenconsoled.pid
    1245 ? Sl 0:00 /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 -pidfile /var/run/qemu-dom0.pid


    * libvirtd does not respond to any service commands:

    # service libvirtd status
    libvirtd.service - Virtualization daemon
    Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
    Active: inactive (dead) since Fri 2014-01-17 14:45:29 CST; 3s ago
    Process: 4354 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS)
    Main PID: 4354 (code=exited, status=0/SUCCESS)

    Jan 17 14:45:28 xen systemd[1]: Started Virtualization daemon.
    Jan 17 14:45:29 xen libvirtd[4354]: libvirt version: 1.1.2

    Even though it appears to start, it does not.


    * The only entries in libxl-driver.log are cache misses:

    xc: debug: hypercall buffer: total allocations:18 total releases:18
    xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
    xc: debug: hypercall buffer: cache current size:4
    xc: debug: hypercall buffer: cache hits:13 misses:4 toobig:1

    I would like to get this box running, .. any suggestions would be appreciated.

    Thanks!

    Lee

  2. #2

    Default Re: 13.1 xen still broken?

    Just used Yast to install Virtual Machine Manager on a virgin 13.1 installation, .. service livbvirtd status shows it is running, but virt-manager does not show a connection available! Is there any hope of getting Virtualization running on 13.1?? What's going on?? Thanks! Lee

  3. #3
    Join Date
    Aug 2008
    Location
    Belgium
    Posts
    275

    Default Re: 13.1 xen still broken?

    Hello,

    I'm on OpenSuse 13.1 (migrated from 12.3) with the XEN kernel from tumbleweed.
    Libvirtd and VM are running correctly:
    Code:
    ps -ef | grep vir
    root      2442     1  0 janv.16 ?      00:00:04 /usr/sbin/libvirtd --listen
    root     15273     1  2 20:44 ?        00:00:05 python /usr/share/virt-manager/virt-manager.py
    Do you have started qemu?

    As far as i remember I had to create a qemu user so that qemu starts correctly
    Code:
    id qemu
    uid=488(qemu) gid=124(qemu) groupes=1(bin),120(libvirt),124(qemu)
    Code:
    ps -ef | grep qemu
    root      1221     1  0 janv.16 ?      00:00:19 /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 -pidfile /var/run/qemu-dom0.pid
    root     15338     1  1 20:45 ?        00:00:04 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 1 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-1,server,nowait -mon chardev=libxl-cmd,mode=control -xen-attach -name Samba -vnc 127.0.0.1:0 -k fr-be -M xenpv -m 1025

    I start the VM via Yast.==> virtual manager ==> connect ==> open VM ==> connect to VM

    Regards
    Philippe
    Tumbleweed (x86_64) Kernel 5.14 with KDE plasma

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •