- Users - oVirt List Archives

Self Hosted Engine disk increase
by Paulo Silva 07 Oct '21

07 Oct '21

Hi, Is there any official procedure to increase the disk size of a self-hosted engine? Regards

2 4

Re: qemu-guest-agent not reporting IP address on boot?
by Tomáš Golembiovský 07 Oct '21

07 Oct '21

On Mon, Oct 04, 2021 at 01:03:10PM +0000, Schreuders, Cliffe wrote: > Thank you. It does look like that bug could be related. Is the problem just with the IP addresses? Do you see other guest information or are those missing too? Tomas > > I had an earlier version of the VM template which continued to work correctly, and an updated version (via apt-get dist-upgrade) that did not report IP addresses correctly. > > I suspected that it might be related to the new ovirt/qemu user agent, so I hold/pinned "ovirt-guest-agent" on the older template before re-running the software updates. > > This worked to create an updated Kali VM that reports it's IP address (albeit more-or-less stuck with whatever dependencies the last ovirt-guest-agent has) so it seems this is indeed an issue with qemu-guest-agent vs ovirt-guest-agent. > > Cheers, > Cliffe. > ________________________________ > From: Arik Hadas <ahadas(a)redhat.com> > Sent: 03 October 2021 12:04 > To: Schreuders, Cliffe <C.Schreuders(a)leedsbeckett.ac.uk> > Cc: users <users(a)ovirt.org>; Tomas Golembiovsky <tgolembi(a)redhat.com> > Subject: Re: [ovirt-users] qemu-guest-agent not reporting IP address on boot? > > > Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. > > > On Fri, Oct 1, 2021 at 5:51 PM <c.schreuders(a)leedsbeckett.ac.uk<mailto:c.schreuders@leedsbeckett.ac.uk>> wrote: > Hi folks, > > Kali Linux repos (based on Debian) no longer ship ovirt-guest-agent, and instead package qemu-guest-agent. However, since this upgrade VMs based on Kali no longer report their IP address to oVirt (and therefore timeout during provisioning). If I interact with the VM console, the VM does have an IP address, and the agent is running, yet oVirt reports N/A IP address. I've tried restarting the agent, but that does not help. If I load the console and use the VM it seems to increase the chances the IP address will eventually makes it's way to oVirt, although I can't seem to reproduce an update, or get it to provide the IP address on boot so that provisioning works reliably. > > Any suggestions would be really appreciated. > > Might be the same as/related to https://bugzilla.redhat.com/show_bug.cgi?id=1981946<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.…> which is still being investigated > > > Thank you. > > Cheers, > Cliffe. > _______________________________________________ > Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> > To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> > Privacy Statement: https://www.ovirt.org/privacy-policy.html<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FFINLLXPBRKYH…<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…> > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email -- Tomáš Golembiovský <tgolembi(a)redhat.com>

2 2

adding new node to host engine is getting failed - engine version latest 4.4.8
by dhanaraj.ramesh＠yahoo.com 06 Oct '21

06 Oct '21

Hi Team when I try to add a new node to the cluster, the installation getting failed with below error Host beclovkvma04.bec.lab installation failed. Task Run PKI enroll request for vdsm and QEMU failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20211006191147-beclovkvma04.bec.lab-e9351609-1bf4-4a8e-adcc-af459f8b25a0.log. log shows as below oR4K1dI9NIaH1jSEtBnIC0Qycxz1i9", "/knKXJLDKeuRsY2holB/BYbMECe4dpseRO+SJPnoqLbK0S6lEf/F6rIcowcg4KbS", "TYjL8g8P6/mM", "-----END CERTIFICATE REQUEST-----" ], "stderr_lines" : [ "Generating a RSA private key", "...............+++++", "........................................+++++", "writing new private key to '/tmp/ansible.wjc0hdouvdsm'", "-----" ], "failed" : false, "item" : { "changed" : true, "path" : "/tmp/ansible.wjc0hdouvdsm", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "vdsm", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "vdsm", "pending_file" : "keys/vdsmkey.pending.pem", "req_dir" : "requests" }, "ansible_loop_var" : "item" }, "ansible_loop_var" : "item" } }, { "diff" : [ ], "dest" : "/etc/pki/ovirt-engine/requests-qemu/beclovkvma04.bec.lab.req", "src" : "/var/lib/ovirt-engine/.ansible/tmp/ansible-tmp-1633527734.1252306-38395-243978746272048/source", "md5sum" : "76137d8fb7063ee3ecce0a1637e991e9", "checksum" : "37c73f4ac229f1837a9b5f4a84162426547de18e", "changed" : true, "cmd" : [ "/usr/share/ovirt-engine/bin/pki-enroll-request.sh", "--name=beclovkvma04.bec.lab", "--subject=/O=bec.lab /CN=beclovkvma04.bec.lab", "--san=DNS:beclovkvma04.bec.lab", "--days=398", "--timeout=30", "--ca-file=ca", "--cert-dir=certs" , "--req-dir=requests" ], "stdout" : "", "stderr" : "Using configuration from openssl.conf\nunable to load number from serial.txt\nerror while loading serial number\n139654062544704:error: 0D066096:asn1 encoding routines:a2i_ASN1_INTEGER:short line:crypto/asn1/f_int.c:140:\nCannot sign certificate", "rc" : 1, "start" : "2021-10-06 19:12:14.648053", "end" : "2021-10-06 19:12:14.673708", "delta" : "0:00:00.025655", "changed" : true, "failed" : true, "invocation" : { "module_args" : { "_raw_params" : "\"/usr/share/ovirt-engine/bin/pki-enroll-request.sh\"\n\"--name=beclovkvma04.bec.lab\"\n\"--subject=/O=bec.bsn lab.broadcom.net/CN=beclovkvma04.bec.lab\"\n\"--san=DNS:beclovkvma04.bec.bsnlab.broadcom.net\"\n\"--days=398\"\n\"--timeout=30\"\n\"--ca-file =ca\"\n\"--cert-dir=certs\"\n\"--req-dir=requests\"\n", "warn" : true, "_uses_shell" : false, "stdin_add_newline" : true, "strip_empty_ends" : true, "argv" : null, "chdir" : null, "executable" : null, "creates" : null, "removes" : null, "stdin" : null } },

1 0

adding new node to host engine is getting failed - engine version latest 4.4.8
by dhanaraj.ramesh＠yahoo.com 06 Oct '21

06 Oct '21

Hi Team when I try to add a new node to the cluster, the installation getting failed with below error Host beclovkvma04.bec.lab installation failed. Task Run PKI enroll request for vdsm and QEMU failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20211006191147-beclovkvma04.bec.lab-e9351609-1bf4-4a8e-adcc-af459f8b25a0.log. log shows as below oR4K1dI9NIaH1jSEtBnIC0Qycxz1i9", "/knKXJLDKeuRsY2holB/BYbMECe4dpseRO+SJPnoqLbK0S6lEf/F6rIcowcg4KbS", "TYjL8g8P6/mM", "-----END CERTIFICATE REQUEST-----" ], "stderr_lines" : [ "Generating a RSA private key", "...............+++++", "........................................+++++", "writing new private key to '/tmp/ansible.wjc0hdouvdsm'", "-----" ], "failed" : false, "item" : { "changed" : true, "path" : "/tmp/ansible.wjc0hdouvdsm", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "vdsm", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "vdsm", "pending_file" : "keys/vdsmkey.pending.pem", "req_dir" : "requests" }, "ansible_loop_var" : "item" }, "ansible_loop_var" : "item" } }, { "diff" : [ ], "dest" : "/etc/pki/ovirt-engine/requests-qemu/beclovkvma04.bec.lab.req", "src" : "/var/lib/ovirt-engine/.ansible/tmp/ansible-tmp-1633527734.1252306-38395-243978746272048/source", "md5sum" : "76137d8fb7063ee3ecce0a1637e991e9", "checksum" : "37c73f4ac229f1837a9b5f4a84162426547de18e", "changed" : true, "cmd" : [ "/usr/share/ovirt-engine/bin/pki-enroll-request.sh", "--name=beclovkvma04.bec.lab", "--subject=/O=bec.lab /CN=beclovkvma04.bec.lab", "--san=DNS:beclovkvma04.bec.lab", "--days=398", "--timeout=30", "--ca-file=ca", "--cert-dir=certs" , "--req-dir=requests" ], "stdout" : "", "stderr" : "Using configuration from openssl.conf\nunable to load number from serial.txt\nerror while loading serial number\n139654062544704:error: 0D066096:asn1 encoding routines:a2i_ASN1_INTEGER:short line:crypto/asn1/f_int.c:140:\nCannot sign certificate", "rc" : 1, "start" : "2021-10-06 19:12:14.648053", "end" : "2021-10-06 19:12:14.673708", "delta" : "0:00:00.025655", "changed" : true, "failed" : true, "invocation" : { "module_args" : { "_raw_params" : "\"/usr/share/ovirt-engine/bin/pki-enroll-request.sh\"\n\"--name=beclovkvma04.bec.lab\"\n\"--subject=/O=bec.bsn lab.broadcom.net/CN=beclovkvma04.bec.lab\"\n\"--san=DNS:beclovkvma04.bec.bsnlab.broadcom.net\"\n\"--days=398\"\n\"--timeout=30\"\n\"--ca-file =ca\"\n\"--cert-dir=certs\"\n\"--req-dir=requests\"\n", "warn" : true, "_uses_shell" : false, "stdin_add_newline" : true, "strip_empty_ends" : true, "argv" : null, "chdir" : null, "executable" : null, "creates" : null, "removes" : null, "stdin" : null } },

1 0

Import ISCSI target as data domain, cannot see old data
by joyzhao93＠gmail.com 06 Oct '21

06 Oct '21

Hi Team, Hope you are doing well. I had a standalone Ovirt Engine with 2 hosts, one 2TB ISCSI data domain (dell equallogic). Today the Ovirt Engine machine crashed so we have to bring up a new one, setup is good and when I try to import ISCSI data domain I can see volumes/Luns, but after import, Ovirt shows the volume is empty - 2TB free (so all old data on the ISCSI volume is not presenting). However when I login to the ISCSI target machine, it shows the old data (around 400GB) is in use. Seems like the new Ovirt Engine cannot detect the old ISCSI data domain disk content. Thank you, Sincerely, SYZhao

2 1

Deploying ovirt+gluster hyperconverged with standalone engine
by J W 06 Oct '21

06 Oct '21

I'm looking for the proper steps to deploy ovirt+gluster hyperconverged with standalone engine as the scenario doesn't seem to be covered here: https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_H… I have attempted to: 1) Deploy standalone engine 2) deploy 3 nodes and ran gluster deployment, stopping before the engine deploy 3) Added hosts to standalone engine I then attempt to add the gluster volumes to the standalone engine by specifying host1:/volume as glusterfs but the volume does not successfully add. Is there another perferred method for this type of deployment?

1 0

importing an ovirt vm via the API for "Virtual Appliance OVA"
by divan＠santanas.co.za 05 Oct '21

05 Oct '21

Hi oVirt Team, Reading the API docs http://ovirt.github.io/ovirt-engine-api-model/4.3/#services/external_vm_imp… http://ovirt.github.io/ovirt-engine-api-model/4.3/#types/external_vm_provid… and ovirt_vm module https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_mo… I see support for - kvm - vmware - XEN In the oVirt web GUI (4.3) there is under compute -> VM -> import -> source options for: - kvm - vmware - XEN - Virtual Appliance OVA I'm trying to import an OVA that sits on the file system on the oVirt node. Via the GUI selecting Virtual Appliance OVA does the job. Is the API missing this functionality or am I missing something? -- Divan Santana

4 4

COarse-grained LOck-stepping for oVirt
by Harry O 05 Oct '21

05 Oct '21

Hi, Will COLO be implemented in oVirt? Is it possible to do it myself? I see qemu-kvm and lots of other qemu installed on my oVirt nodes. It's in Qemu upstream (v4.0) https://wiki.qemu.org/Features/COLO

2 3

Re: About the vm memory limit
by Tommy Sway 04 Oct '21

04 Oct '21

transparent huge pages are not used on vm and physical host. But, can I enable hugepage memory on virtual machines but not on a physical machine? For database running on vm, and it needs to config hugepage. From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Saturday, September 25, 2021 5:32 PM To: Tommy Sway <sz_cuitao(a)163.com> Subject: Re: [ovirt-users] About the vm memory limit It depends on the numa configuration of the host. If you have 256G per CPU, it's best to stay into that range. Also, consider disabling transparent huge pages on the host & VM. Since 4.4 Regular Huge Pages (do not confuse them with THP) can be used on the Hypervisors, while on 4.3 there were some issues but I can't provode any details. Best Regards, Strahil Nikolov On Fri, Sep 24, 2021 at 6:40, Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > wrote: I would like to ask if there is any limit on the memory size of virtual machines, or performance curve or something like that? As long as there is memory on the physical machine, the more virtual machines the better? In our usage scenario, there are many virtual machines with databases, and their memory varies greatly. For some virtual machines, 4G memory is enough, while for some virtual machines, 64GB memory is needed. I want to know what is the best use of memory for a virtual machine, since the virtual machine is just a QEMU emulation process on a physical machine, and I worry that it is not using as much memory as a physical machine. Understand this so that we can develop guidelines for optimal memory usage scenarios for virtual machines. Thank you! _______________________________________________ Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Y6XDOIMKCP4JE…

4 26

Re: Can't join new mon - lossy channel, failing
by Konstantin Shalygin 04 Oct '21

04 Oct '21

Hi, > On 4 Oct 2021, at 16:37, Vladimir Bashkirtsev <vladimir(a)bashkirtsev.com> wrote: > > And just for clarity: you do not attempt to join mixed 32/64 bit cluster? There's a known bug in src/msg/async/frames_v2.h causing frame size mismatch on mixed clusters leading to the same error messages. All hardware is x86_64 k

1 0