mirror of
https://github.com/retspen/webvirtcloud.git
synced 2026-04-25 07:25:53 +03:00
[GH-ISSUE #230] Error: unknown procedure: 342 #155
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/webvirtcloud#155
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zaghost on GitHub (Mar 27, 2019).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/230
I got en error when visit http:///computes/2/create/ or some other pages
There is the following line in the console log:
libvirt: XML-RPC error : unknown procedure: 342
@catborise commented on GitHub (Mar 27, 2019):
"http:///computes/2/create/" is this the adress? there should be hostname or ip
it is related libvirt and/or network/port problem. you should check libvirt config.
how you check...
you connect and manage other host hypervisor. if you could not that. you must solve that problem before webvirtcloud use
@zaghost commented on GitHub (Mar 28, 2019):
@catborise Thank you for your reply
I'm sorry, I wanted to say
"http://<host>/computes/2/create/", but github don't display the"<host>"part.In
http://<hostname>/instances/, the VMs are listed under libvirt host, so I think the connection to libvirt host is OK.But I click "Add Instance" button, it turns to
http://<host>/computes/2/create/where display an error message@catborise commented on GitHub (Mar 28, 2019):
what is host operating system?
what is libvirt version?
what is qemu version?
login to virt host:
run;
qemu-img --version
virsh --version
@zaghost commented on GitHub (Mar 28, 2019):
the versions are a bit old
kvm03:~ # uname -a
Linux kvm03 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) x86_64 x86_64 x86_64 GNU/Linux
kvm03:~ # cat /etc/SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2
kvm03:~ # virsh -v
0.9.6
kvm03:~ # qemu-img --version
qemu-img version 0.15.0, Copyright (c) 2004-2008 Fabrice Bellard
usage: qemu-img command [command options]
QEMU disk image utility
@catborise commented on GitHub (Mar 28, 2019):
It is too old for qemu and libvirt. You should update these packages.
Latest stable releases for libvirt is 5.0 and qemu is 2.12
You should update them to use webvirtcloud without problem
@sckghost commented on GitHub (Apr 9, 2019):
I also encountered the same problem. In the latest version of webvirtcloud, Error: unknown procedure: 342 appeared when clicking on an instance of the web interface. Here is the information of the server system.
[root@webvirt2-200-74 script]# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
[root@webvirt2-200-74 script]# virsh -v
4.5.0
@catborise commented on GitHub (Apr 9, 2019):
hi @sckghost could you please send me the output out this command "virsh version"
@sckghost commented on GitHub (Apr 9, 2019):
(venv) [root@webvirt2-200-74 ~]# virsh version
Compiled against library: libvirt 4.5.0
Using library: libvirt 4.5.0
Using API: QEMU 4.5.0
Running hypervisor: QEMU 1.5.3
@sckghost commented on GitHub (Apr 9, 2019):
centos7.x Must I use libvirt version 5.0 or above?
@catborise commented on GitHub (Apr 9, 2019):
@sckghost no, you should upgrade the qemu.
i am using also centos 7 and i upgrade the qemu package to "2.12"
you could add "qemu-kvm-ev" repo to upgrade the qemu-kvm package.
i think this solve your problem.
qemu 2.12 stable version. it contains many features.
@sckghost commented on GitHub (Apr 9, 2019):
Okay, it's still 342 error after installation. What's next?
Yum install centos-release-qemu-ev
Yum update qemu-kvm
(venv) [root@webvirt2-200-74 ~]# virsh version
Compiled against library: libvirt 4.5.0
Use library: libvirt 4.5.0
Using API: QEMU 4.5.0
Running hypervisor: QEMU 2.12.0
@catborise commented on GitHub (Apr 9, 2019):
@sckghost could you create a new instance to see the error still exist
(ps: to activate new version of qemu you should stop and start the instance.)
@sckghost commented on GitHub (Apr 9, 2019):
(venv) [root@webvirt2 webvirtcloud]# cat conf/requirements.txt
Django==1.11.17
websockify==0.8.0
gunicorn==19.9.0
lxml==4.2.5
libvirt-python==4.10.0
pytz
Does the libvirt-python version need to be changed to 5.0, or the libvirt version of the system needs to be upgraded to 5.0?
@sckghost commented on GitHub (Apr 9, 2019):
I tried, but I still couldn't. Restart webvirtcloud and nginx. Errors still exist.
@catborise commented on GitHub (Apr 9, 2019):
no, i also did not upgrade libvirt-python. i am using 4.10.
i suspect jquery.js, i did upgrade it lately. it could cause something like that. but i need more information.
could you check with chrome(right click and inspect) if there is an anomaly
@sckghost commented on GitHub (Apr 9, 2019):
@catborise commented on GitHub (Apr 9, 2019):
there is an error as you see right
could you click to see.
@sckghost commented on GitHub (Apr 9, 2019):
@catborise commented on GitHub (Apr 9, 2019):
@sckghost i check it again it is not related with qemu or libvirt.
i will install centos 7.6 to try it again. i could not simulate it. i am also using but there is not error like that.
please give me some time to install new env
@sckghost commented on GitHub (Apr 9, 2019):
ok
@catborise commented on GitHub (Apr 9, 2019):
@sckghost i install a minimal host.
cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
run the script to prepare host:
yum install epel-release wget
wget -O - https://clck.ru/9V9fH | sudo sh
disable firewall:
systemctl stop firewalld
add an sasl2 user:
saslpasswd2 -a libvirt admin
build an os image:
virt-builder centos-7.6 --output /var/lib/libvirt/images/test.qcow2 --format qcow2
add host to webvirtcloud with tcp connection.
create an instance from custom
start it.
and there is not any error
virsh version
Compiled against library: libvirt 4.5.0
Using library: libvirt 4.5.0
Using API: QEMU 4.5.0
Running hypervisor: QEMU 1.5.3
what could it be? i do not understand