Bug 11939 - libvirt not working anymore (Core125)
Summary: libvirt not working anymore (Core125)
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: x86_64 All
: - Unknown - Crash
Assignee: Michael Tremer
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-26 17:46 UTC by geh kah
Modified: 2019-01-10 19:35 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description geh kah 2018-11-26 17:46:53 UTC
following error occures on new libvirt installation with core 125, and core 124 isnt working too, if libvirt/qemu-packages has been freshly installed:


2018-11-26 17:37:41.084+0000: 2748: error : virJSONJanssonOnceInit:66 : this function is not supported by the connection driver: libjansson.so.4 JSON library not available: libjansson.so.4: cannot open shared object file: No such file or directory
/var/log/libvirt/libvirtd.log (END)


following appears during boot:

Starting virtlogd Daemon...                                            [  OK  ]
Load required kernel modules for Libvirt                               [  OK  ]
Starting Libvirt Daemon...                                             [ FAIL ]


but no other logs can be found.
Comment 1 Michael Tremer 2018-11-27 10:04:14 UTC
Did you try to install the jansson package? Does the daemon start then?
Comment 2 geh kah 2018-11-27 14:06:22 UTC
(In reply to Michael Tremer from comment #1)
> Did you try to install the jansson package? Does the daemon start then?

Dear Michael

Indeed I didnt know to install this package. Now I did. libvirtd is running :)

But I got problems to setup a VM. I got access to the pool and am able to deploy a disk. But when I want to finish the wizard, it tells me:

internal error: process exited while connecting to monitor: date qemu-system-x86_64 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny:seccomp support is disabled

Also I changed /var/ipfire/ethernet/settings to GREEN_MODE=bridge but the Host-devices are marked as "macvtap" in Virtual Machine Manager --> I dont think this is right because I got the same issue on Core124 with libvirtd 4.0 --> when I change ZONE_Mode=bridge, I cannot set the device to "greenphys0 (bridge 'green0') as I did in advance on earlier kernels?

I'm sorry for my lost in libvirtd
Comment 3 geh kah 2018-11-27 15:09:34 UTC
(In reply to Michael Tremer from comment #1)
> Did you try to install the jansson package? Does the daemon start then?

I'm so sorry, I did a typo in the config file of the ethernet settings. now network is corrected, but I got the same error message while trying to add a new VM with virt manager
Comment 4 geh kah 2018-11-27 15:19:51 UTC
solved!!!

I added this to qemu.conf

cat /etc/libvirt/qemu.conf
seccomp_sandbox = 0

after that, i restarted with /etc/init.d/libvirtd restart --> successfully deployed a VM and got network. will test now
Comment 5 Michael Tremer 2018-11-28 13:34:16 UTC
(In reply to geh kah from comment #4)
> solved!!!
> 
> I added this to qemu.conf
> 
> cat /etc/libvirt/qemu.conf
> seccomp_sandbox = 0
> 
> after that, i restarted with /etc/init.d/libvirtd restart --> successfully
> deployed a VM and got network. will test now

Thanks for reporting back. Because this is a separate issue, I created a new ticket #11941.

This is fixed now in https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=612424542710ab75cbfb4187d98295a7cbaec719
Comment 6 Daniel Weismüller 2018-11-28 13:49:43 UTC
I confirm the bug and I solved like described above. 
First installed the jansson paket via pakfire and then added

seccomp_sandbox = 0

to /etc/libvirt/qemu.conf

-
Daniel
Comment 7 geh kah 2018-11-28 18:50:40 UTC
(In reply to Daniel Weismüller from comment #6)
> I confirm the bug and I solved like described above. 
> First installed the jansson paket via pakfire and then added
> 
> seccomp_sandbox = 0
> 
> to /etc/libvirt/qemu.conf
> 
> -
> Daniel

I forgot to confirm: yes, this way works since 24hours without a problem. I just dont know how bad it is on security?
Comment 8 Michael Tremer 2019-01-08 15:57:55 UTC
A new version is shipped.
Comment 9 geh kah 2019-01-10 19:35:10 UTC
Thank you Michael

As you already know, the fix is working, I confirm.

Thank you very much for all your efforts, very much appreciated.