Forums

Resolved
0 votes
Hello,

i got a HPE Microserver gen10, the cpu is virtualization capable but after i had installed kimchi inside the webserver the virtualization tab is not showing up, what could i try to correct the issue?


cat /proc/cpuinfo | grep svm
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm perfctr_core perfctr_nb bpext ptsc cpb hw_pstate retpoline_amd ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic vgif overflow_recov
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm perfctr_core perfctr_nb bpext ptsc cpb hw_pstate retpoline_amd ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic vgif overflow_recov


Thanks
Friday, December 27 2019, 11:27 PM
Share this post:

Accepted Answer

Sunday, December 29 2019, 10:28 AM - #Permalink
Resolved
0 votes
You should have a file, /etc/dnsmasq.d/bind.conf. If you do, please restart dnsmasq. It should get rid of the DHCP issue. If you don't have this file I've struggled to find which app provides it which is weird (it is configured on-the-fly by ClearOS). If you don't have it, create a file in /etc/dnsmasq.d, and add a line "bind-interfaces" then restart dnsmasq and libvirtd.

The rest I don't really know about. I haven't really played with Kimchi, but your errors are coming straight out of libvirtd.

On the ex-ClearVM server, the external interface is a bridge interface, br0, and the true interface is a child of it. You can set this up through the webconfig if you download the beta app-network ot you will have to do it manually. There is a howto. This allows you to bind a VM to the br0 interface as well. The Microserver on which I have kimchi is a bit different insomuch as yesterday I managed to put the VM on a macvlan interface bound directly to the external interface. I am not brilliant at this at all so hardly know what I'm doing. With a macvlan interface the host cannot contact the guest but in my case. both are on my LAN so I don't mind.
The reply is currently minimized Show
Responses (15)
  • Accepted Answer

    Saturday, December 28 2019, 09:07 AM - #Permalink
    Resolved
    0 votes
    At a guess you are using the released version. There is a better beta version in contribs-testing:
    yum update *kimchi* --enablerepo=clearos-contribs-testing
    This provides better functionality. Unfortunately the developer stopped developing the app and, in theory, was going to restart much earlier this year but I've never seen anything. I can't remember the problems this version had but it was better.

    Nearly all my VM management is done through the "virsh" command line. It is possible to load a graphical desktop on some machines and this will give you the Gnome Virtual Machine Manager, but I could never get the graphical desktop working on a Microserver.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 28 2019, 06:14 PM - #Permalink
    Resolved
    0 votes
    I've had another little look at Kimchi. It looks like GitLab is active but there has been no formal release for a couple of years.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 28 2019, 09:05 PM - #Permalink
    Resolved
    0 votes
    Hello Nick,

    thanks for your feedback, i tried also the beta version what you suggested, i see the same interface Kimchi

    I also posted my issue on the github now, any idea where should i see any errors if there are? (Logs?)

    Regarding "virsh" it is the command line to setup a new vm wihtout gui? There is any solution to connect to the vm lets say as vnc at the installation process? Could you provide me a good how-to for virsh.

    I know i ask a lot and because of this thanks for your dedication!

    Ervin
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 28 2019, 09:16 PM - #Permalink
    Resolved
    0 votes
    What do you get from:
    rpm -qa | grep kimchi
    I get:
    [root@microserver ~]# rpm -qa | grep kimchi
    kimchi-2.5.0-0.v7.noarch
    app-kimchi-1.1.8-1.v7.noarch
    app-kimchi-core-1.1.8-1.v7.noarch
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 28 2019, 09:38 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    What do you get from:
    rpm -qa | grep kimchi
    I get:
    [root@microserver ~]# rpm -qa | grep kimchi
    kimchi-2.5.0-0.v7.noarch
    app-kimchi-1.1.8-1.v7.noarch
    app-kimchi-core-1.1.8-1.v7.noarch



    i get the same

    rpm -qa | grep kimchi
    app-kimchi-core-1.1.8-1.v7.noarch
    app-kimchi-1.1.8-1.v7.noarch
    kimchi-2.5.0-0.v7.noarch
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 28 2019, 10:07 PM - #Permalink
    Resolved
    0 votes
    Mine looks very different. I've no idea if something needs restarting after an update.

    At the command line the following works for me:
    virt-install      --name=ClearOS7-test-master \
    --memory=1536 \
    --cpu=host \
    --vcpus=1 \
    --os-variant=rhel7 \
    --disk /mnt/d1/private_images/custom/ClearOS7-test-master.qcow2,size=64,bus=virtio \
    --disk /mnt/d1/private_images/cache/ClearOS-DVD-x86_64-7.6.0.261741.iso,device=cdrom,bus=ide \
    --network bridge=br0 \
    --graphics vnc,listen=0.0.0.0,password='mypassword' \
    --input tablet \
    --check path_in_use=off
    This is on an ex-ClearVM set up so some of the background set up was already done (NIC's) and the host has multiple NICs. The "--input tablet" is important if you want the mouse to track correctly in VNC.

    There is a one-liner here to find the VNC port number. For VNC, the only Windows VNC client which worked correctly was TigerVNC. None of the other ones mapped all the keys correctly. I think the main problem was the / or \.
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 28 2019, 10:11 PM - #Permalink
    Resolved
    0 votes
    I had stopped Kimchi using the clearos gui and i am not able to start anymore :) Tried also to reinstall but got the same result after.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 28 2019, 10:21 PM - #Permalink
    Resolved
    0 votes
    My machine has a mixed heritage. I know I installed libvirt at one time using this. Can you check the libvirtd service and, perhaps start it if it is not running.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 28 2019, 10:37 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    My machine has a mixed heritage. I know I installed libvirt at one time using this. Can you check the libvirtd service and, perhaps start it if it is not running.


    i used also this guide before and already setup like in how-to you mentioned, should i install also the graphical environment?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 28 2019, 11:14 PM - #Permalink
    Resolved
    0 votes
    the service is running should i concern about the errors below?

    sudo service libvirtd status
    Redirecting to /bin/systemctl status libvirtd.service
    ● libvirtd.service - Virtualization daemon
    Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
    Active: active (running) since Sat 2019-12-28 23:50:34 EET; 1h 21min ago
    Docs: man:libvirtd(8)
    https://libvirt.org
    Main PID: 1659 (libvirtd)
    CGroup: /system.slice/libvirtd.service
    └─1659 /usr/sbin/libvirtd

    Dec 28 23:50:38 server.darzu.com dnsmasq[2888]: failed to bind DHCP server socket: Address already in use
    Dec 28 23:50:38 server.darzu.com libvirtd[1659]: 2019-12-28 21:50:38.658+0000: 1861: info : libvirt version: 4.5.0, package: 23.el7_7.3 (CentOS BuildSystem <http://bugs.centos...centos.org)
    Dec 28 23:50:38 server.darzu.com libvirtd[1659]: 2019-12-28 21:50:38.658+0000: 1861: info : hostname: server.darzu.com
    Dec 28 23:50:38 server.darzu.com libvirtd[1659]: 2019-12-28 21:50:38.658+0000: 1861: error : virCommandWait:2709 : internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/s...t status 2:
    Dec 28 23:50:38 server.darzu.com libvirtd[1659]: dnsmasq: failed to bind DHCP server socket: Address already in use
    Dec 28 23:50:41 server.darzu.com libvirtd[1659]: 2019-12-28 21:50:41.188+0000: 1702: error : virCommandWait:2709 : internal error: Child process (/usr/sbin/showmount --no-head... registered
    Dec 28 23:50:44 server.darzu.com libvirtd[1659]: 2019-12-28 21:50:44.266+0000: 1702: error : virStorageBackendFileSystemNetFindPoolSources:191 : operation failed: no storage p...'127.0.0.1'
    Dec 28 23:50:44 server.darzu.com libvirtd[1659]: 2019-12-28 21:50:44.831+0000: 1703: error : qemuDomainDefValidateMemoryHotplug:9654 : unsupported configuration: memory hotplu...QEMU binary
    Dec 28 23:50:49 server.darzu.com libvirtd[1659]: 2019-12-28 21:50:49.763+0000: 1701: error : virCommandWait:2709 : internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/s...t status 2:
    Dec 28 23:50:49 server.darzu.com libvirtd[1659]: dnsmasq: failed to bind DHCP server socket: Address already in use
    Hint: Some lines were ellipsized, use -l to show in full.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, December 30 2019, 11:52 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    You should have a file, /etc/dnsmasq.d/bind.conf. If you do, please restart dnsmasq. It should get rid of the DHCP issue. If you don't have this file I've struggled to find which app provides it which is weird (it is configured on-the-fly by ClearOS). If you don't have it, create a file in /etc/dnsmasq.d, and add a line "bind-interfaces" then restart dnsmasq and libvirtd.

    The rest I don't really know about. I haven't really played with Kimchi, but your errors are coming straight out of libvirtd.

    On the ex-ClearVM server, the external interface is a bridge interface, br0, and the true interface is a child of it. You can set this up through the webconfig if you download the beta app-network ot you will have to do it manually. There is a howto. This allows you to bind a VM to the br0 interface as well. The Microserver on which I have kimchi is a bit different insomuch as yesterday I managed to put the VM on a macvlan interface bound directly to the external interface. I am not brilliant at this at all so hardly know what I'm doing. With a macvlan interface the host cannot contact the guest but in my case. both are on my LAN so I don't mind.


    Hello,

    i was able to resolve the issue, now the virtualization tab show up.

    Exactly i amn not able to tell what was the issue, but these are the steps what resolved my issue.

    I had created the bind.conf as you mentioned but the issue was still there, not even kimchi was starting.
    Meanwhile on the github i received some indications and after i installed python3 see the link here.
    After that still the admin console was disabled and i was not able to start it, so i was thinking to reinstall it and after reinstalling the admin console was available again.
    After logging in i was able to see the virtualization tab, i am already installing some guests on it.

    Thanks for your support

    Ervin
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, January 05 2020, 02:23 AM - #Permalink
    Resolved
    0 votes
    Kimchi has released 3.0: https://github.com/kimchi-project/kimchi/releases/tag/3.0.0

    But I doubt ClearOS repos will automatically pick it up.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, January 05 2020, 10:02 AM - #Permalink
    Resolved
    0 votes
    Hi Marc, since the thread started and I understand virtualisation a bit better, I've dusted off my copy and I like it. It (2.5) did have a obvious issue where an imported iso did not get the permissions it needed to run, and the set up process is slightly more involved that I'd realised, setting up a storage pool and template before you create a guest but it works OK and I like it.

    I was thinking about contacting you and releasing the current version as it has been in our testing repos for over 2 years now. The versions there are:
    app-kimchi-1.1.8-1.v7.noarch
    app-kimchi-core-1.1.8-1.v7.noarch
    kimchi-2.5.0-0.v7.noarch
    wok-2.5.0-1.v7.noarch.rpm

    The released version is useless:
    app-kimchi-1.1.7-1.v7.noarch
    app-kimchi-core-1.1.7-1.v7.noarch
    kimchi-2.3.1-0.v7.noarch
    wok-2.3.1-0.v7.noarch.rpm

    For the moment, do you want me to release the version in updates testing?

    Going forward, we don't have kimchi or app-kimchi in our repos so I suspect they were supplied by you (WikiSuite) and injected in by Peter. What are you proposing as a way forward? We have blank projects in GitLab where I guess we could do something, but I don't know how to convert your sources into something which can be built into one of our rpm's. Are you able to provide the rpm?

    Does wok also need updating? On your github I see wok is now at 3.0.0. We do not even have a dummy wok project in Gitlab.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, January 31 2020, 09:01 AM - #Permalink
    Resolved
    0 votes
    Hello Frank, I can see you've been trying to post really hard! As a new poster your first two posts get moderated and don't appear immediately.

    I have Kimchi/Wok 2.5 working here. The problem you probably have is libvirt is not starting because it can't bind to port 53 because dnsmasq is already bound to it. Try doing a "systemctl start libvirtd" and look for errors. If so, you have to stop dnsmasq from binding to all ports. The easiest way to do this is to upgrade app-dns to the version I pushed into updates testing yesterday:
    yum update app-dns --enablerepo=clearos-updates-testing
    The sole purpose of the update was to make dnsmasq only bind to normal interfaces, and I dusted off the update just because kimchi/wok had come to the fore again.

    After installing, try:
    systemctl start libvirtd
    Libvirt should start and your virtualisation tab should appear.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, January 31 2020, 01:24 AM - #Permalink
    Resolved
    0 votes
    Hello Nick and Marc,

    The previously released version of Kimchi 1.1.7-1.v7 was testing clean and fulfilled our use case. We need to provide our customers with an easy way (i.e., GUI) to authenticate+start+stop+console into KVM virtual machines running multiple copies of our application hosted on each ClearOS based server we add to our managed service.

    The upgrade to 1.1.8-1.v7 broke (see attached screen capture) the Wikisuite install/config for ClearOS 7.x (I tried it on ClearOS 7.4, 7.6, & 7.7 instances). You can't start Kimchi or open the admin console from the GUI now. In other words, the Kimchi 1.1.8 stack doesn't work with ClearOS 7.x. Were you aware of this problem?

    Can you switch the Kimchi stack back to 1.1.7 in the EPEL test repro deployed via Wikisuite's config (yum install app-kimchi) until a stable/working version of the Kimchi (1.18 and/or 3) is released?

    I'm happy to test and provide feedback.

    This is a time sensitive work stoppage problem for us. Any help is greatly appreciated.

    Thank you,

    Frank

    Works with ClearOS 7.x:

    app-kimchi-1.1.7-1.v7.noarch
    app-kimchi-core-1.1.7-1.v7.noarch
    kimchi-2.3.1-0.v7.noarch
    wok-2.3.1-0.v7.noarch.rpm

    Doesn't work with ClearOS 7.x:

    app-kimchi-1.1.8-1.v7.noarch
    app-kimchi-core-1.1.8-1.v7.noarch
    kimchi-2.5.0-0.v7.noarch
    wok-2.5.0-1.v7.noarch.rpm
    The reply is currently minimized Show
Your Reply