Failed to deploy ovirt engine with "hosted-engine --deploy"
by Bong Shau Fui
Hi:
I'm new to ovirt. I followed the guide at the page https://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hoste..., started to run "hosted-engine --deploy". It got stuck at the stage TASK [Get local VM IP] for about 5 minutes, and failed. Did a search but came out with nothing. From the log files these 2 lines are shown:
2018-07-25 19:59:11,269+0800 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 {u'_ansible_parsed': True, u'stderr_lines': [], u'cmd': u"virsh -r net-dhcp-leases default | grep -i 00:16:3e:5e:43:32 | awk '{ print $5 }' | cut -f1 -d'/'", u'end': u'2018-07-25 19:59:11.081420', u'_ansible_no_log': False, u'stdout': u'', u'changed': True, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'_raw_params': u"virsh -r net-dhcp-leases default | grep -i 00:16:3e:5e:43:32 | awk '{ print $5 }' | cut -f1 -d'/'", u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin': None}}, u'start': u'2018-07-25 19:59:10.949464', u'attempts': 50, u'stderr': u'', u'rc': 0, u'delta': u'0:00:00.131956', u'stdout_lines': []}
2018-07-25 19:59:11,370+0800 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:98 fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "virsh -r net-dhcp-leases default | grep -i 00:16:3e:5e:43:32 | awk '{ print $5 }' | cut -f1 -d'/'", "delta": "0:00:00.131956", "end": "2018-07-25 19:59:11.081420", "rc": 0, "start": "2018-07-25 19:59:10.949464", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
Can someone please enlighten me on what has happened? Many thanks in advance.
regards,
Bong SF
5 years, 9 months
Re: Windows 10 - Ovirt 4.3 - EPYC
by Dominik Holler
On Fri, 1 Feb 2019 17:37:30 -0500
Darin Schmidt <darinschmidt(a)gmail.com> wrote:
> [root@ovirt ~]# rpm -qa kernel
> kernel-3.10.0-957.1.3.el7.x86_64
> kernel-3.10.0-862.el7.x86_64
> [root@ovirt ~]# uname -a
> Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018
https://bugzilla.redhat.com/1638835 looks like there is at least
kernel 3.10.0-957.3.1.el7.x86_64 required.
Can you please check if upgrading to kernel solves the issue for you?
I expectect at least kernel 3.10.0-957.5.1 to be availible.
> x86_64 x86_64 x86_64 GNU/Linux
> [root@ovirt ~]# rpm -qa qemu-kvm-ev
> qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
> [root@ovirt ~]# rpm -qa libvirt
> libvirt-4.5.0-10.el7_6.3.x86_64
> here is the vdsm
>
contains:
Hyper-V SynIC is not supported by kernel
> On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler <dholler(a)redhat.com>
> wrote:
>
> > On Fri, 1 Feb 2019 11:48:51 -0500
> > Darin Schmidt <darinschmidt(a)gmail.com> wrote:
> >
> > > I have successfully setup a centos vm, its up and running. Now I
> > > need to setup a windows 10 VM and I cant seem to get anything to
> > > work.
> > >
> > > Ive tried setting the OS type to other or Windows 10 64bit. With
> > > Windows 64bit, it fails to startup at all.... When I select
> > > OtherOS it will allow me to start to run the Windows ISO, but
> > > then fails after a few seconds as well. Is there something I'm
> > > not correctly configuring?
> >
> > Would you please share vdsm.log, and the output of
> > rpm -qa kernel
> > uname -a
> > rpm -qa qemu-kvm-ev
> > rpm -qa libvirt
> > from of the host, and the relevant part of engine.log?
> >
5 years, 9 months
Infiniband Usage / Support
by Andrey Rusakov
Hi,
I got a config with IB Storage (IPoIB).
I would like to extend IB usage to OVN network, but trying to do this i find some problems ...
Problem #1 (IPoIB Storage Network)
I configure IPoIB Before adding to oVirt cluster (I did it using Cockpit)
Create [Bond], assign IP, change MTU.
At this moment of time everything is fine...
But - I am not able to assign IP/MTU using oVirt Cluster.
And I can't perform any changes using Cockpit as IB interfaces are "Unmanaged Interfaces".
Problem #1.1
It will be great to avoid users adding IPoIB networks using brctl, as it will not work...
Problem #2
What is correct way to move OVN to IPoIB network?
5 years, 9 months
Please don't remove instance type
by Baptiste Agasse
Hi all,
We are happy oVirt users for some years now (we started with 3.6, now on 4.2) and we manage most of our virtualization stacks with it. To provision and manage our machines, we use the foreman (for bare metal and virtual machines) on top of it. I made some little contributions to the foreman and other underlying stuff to have a deeper integration with oVirt, like to be able to select instance type directly from foreman interface/api and we rely on it. We use instance types to standardize our vms by defining system resources (memory, cpu and cpu topology) console type, boot options. On top of that we plan to use templates to apply OS (CentOS 7 and CentOS 6 actually). Having resources definitions separated from OS installation help us to keep instance types and templates lists small and don't bother users about some technical underlying stuff. As we are interested in automating oVirt maintenance tasks and configuration with ansible, I asked at FOSDEM oVirt booth if there is any ansible module to manage instance types in Ovirt as I didn't find it in ovirt ansible infra repo. The person to whom I asked the question said that you are planning to remove instance types from ovirt, and this make me sad :(. So here I am to ask why do you plan to remove instance types from oVirt. As far as I know, it's fairly common to have "instance types" / "flavors" / "sizes" on one side and then templates (bare OS, preinstalled appliances...) on other side and pick one of each to make an instance. If this first part is missing in future version of ovirt, it will be a pain point for us. So, my question is, do you really plan to remove instances type definitely ?
Cheers.
--
Baptiste
5 years, 9 months
Quota Actual Consumption
by Andrey Rusakov
Hi,
Is it possible to configure oVirt to work Quota with actual vCPU Consumption.
Currently i got 1 VM with 2 vCPU and 8Gb.
In VM stats -
0% of CPU in use
0% of RAM in Use
(it is fresh Linux instalaltion)
In Quota consumption i can see
40% of CPU (vCPU quota = 5)
27% of RAM (Memory quota 30Gb)
Is it possible to adjust Quata management to work with Actual workload, instead of VM Configuration?
P.S. Seems like it is working for Storage, as i can see 0% Consumption in Quota (1Gb of thick disk with 20Gb Max and 200Gb in Quota)
5 years, 9 months
Cannot start VM: Bad volume specification
by Alan G
Hi,
I performed the following: -
1. Shutdown VM.
2. Take a snapshot
3. Create a clone from snapshot.
4. Start the clone. Clone starts fine.
5. Attempt to delete snapshot from original VM, fails.
6. Attempt to start original VM, fails with "Bad volume specification".
This was logged in VDSM during the snapshot deletion attempt.
2019-02-26 13:27:10,907+0000 ERROR (tasks/3) [storage.TaskManager.Task] (Task='67577e64-f29d-4c47-a38f-e54b905cae03') Unexpected error (task:872)
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 879, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/task.py", line 333, in run
return self.cmd(*self.argslist, **self.argsdict)
File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper
return method(self, *args, **kwargs)
File "/usr/share/vdsm/storage/sp.py", line 1892, in finalizeMerge
merge.finalize(subchainInfo)
File "/usr/share/vdsm/storage/merge.py", line 271, in finalize
optimal_size = subchain.base_vol.optimal_size()
File "/usr/share/vdsm/storage/blockVolume.py", line 440, in optimal_size
check = qemuimg.check(self.getVolumePath(), qemuimg.FORMAT.QCOW2)
File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 157, in check
out = _run_cmd(cmd)
File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 426, in _run_cmd
raise QImgError(cmd, rc, out, err)
QImgError: cmd=['/usr/bin/qemu-img', 'check', '--output', 'json', '-f', 'qcow2', '/rhev/data-center/mnt/blockSD/024109d5-ea84-47ed-87e5-1c8681fdd177/images/f7dea7bd-04
6c-4923-b5a5-d0c1201607fc/ac540314-989d-42c2-9e7e-3907eedbe27f'], ecode=3, stdout={
"image-end-offset": 52210892800,
"total-clusters": 1638400,
"check-errors": 0,
"leaks": 323,
"leaks-fixed": 0,
"allocated-clusters": 795890,
"filename": "/rhev/data-center/mnt/blockSD/024109d5-ea84-47ed-87e5-1c8681fdd177/images/f7dea7bd-046c-4923-b5a5-d0c1201607fc/ac540314-989d-42c2-9e7e-3907eedbe27f",
"format": "qcow2",
"fragmented-clusters": 692941
}
, stderr=Leaked cluster 81919 refcount=1 reference=0
Leaked cluster 81920 refcount=1 reference=0
Leaked cluster 81921 refcount=1 reference=0
etc..
Is there any way to fix these leaked clusters?
Running oVirt 4.1.9 with FC block storage.
Thanks,
Alan
5 years, 9 months
Cannot assign Network to Mellanox Interface
by cbop.mail＠gmail.com
Hello,
I want to use my Infiniband Network for Storage Access, so I created a new network and tried to assign it to a host. When I do this, I get a success message but it's actually not assigned to my Infiniband NIC.
I'm running the latest CentOS with the latest Mellanox OFED drivers and multiple Subnet Managers are running on the network. The NIC is a Mellanox ConnectX-2 VPI, set to Infiniband mode.
I didnt't knew which logs to send, so when you need to look into a log, just tell me which one you need.
I hope you can help me out.
Roman Meusch
5 years, 9 months
Re: Cannot Increase Hosted Engine VM Memory
by Douglas Duckworth
Ok sounds good.
I will upgrade then hope this goes away.
On Thu, Jan 31, 2019, 12:09 PM Simone Tiraboschi <stirabos(a)redhat.com<mailto:stirabos@redhat.com> wrote:
On Thu, Jan 31, 2019 at 4:20 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Hi Simone
Thanks again for your help!
Do you have some ideas on what I can try to resolve this issue?
Honestly I'm not able to reproduce this issue.
I can only suggest to try upgrading to 4.2.8 if still not there, and if still not working open a bug on bugzilla attaching engine.log.
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
On Fri, Jan 25, 2019 at 3:15 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Yes, I do. Gold crown indeed.
It's the "HostedEngine" as seen attached!
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
On Wed, Jan 23, 2019 at 12:02 PM Simone Tiraboschi <stirabos(a)redhat.com<mailto:stirabos@redhat.com>> wrote:
On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Hi Simone
Can I get help with this issue? Still cannot increase memory for Hosted Engine.
From the logs it seams that the engine is trying to hotplug memory to the engine VM which is something it should not happen.
The engine should simply update engine VM configuration in the OVF_STORE and require a reboot of the engine VM.
Quick question, in the VM panel do you see a gold crown symbol on the Engine VM?
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Sure, they're attached. In "first attempt" the error seems to be:
2019-01-17 07:49:24,795-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [680f82b3-7612-4d91-afdc-43937aa298a2] EVENT_ID: FAILED_HOT_SET_MEMORY_NOT_DIVIDABLE(2,048), Failed to hot plug memory to VM HostedEngine. Amount of added memory (4000MiB) is not dividable by 256MiB.
Followed by:
2019-01-17 07:49:24,814-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (default task-29) [26f5f3ed] Validation of action 'UpdateRngDevice' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING
2019-01-17 07:49:24,815-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-29) [26f5f3ed] Updating RNG device of VM HostedEngine (adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. New RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}.
In "second attempt" I used values that are dividable by 256 MiB so that's no longer present. Though same error:
2019-01-17 07:56:59,795-05 INFO [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f] START, SetAmountOfMemoryVDSCommand(HostName = ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu>, Params:{hostId='cdd5ffda-95c7-4ffa-ae40-be66f1d15c30', vmId='adf14389-1563-4b1a-9af6-4b40370a825b', memoryDevice='VmDevice:{id='VmDeviceId:{deviceId='7f7d97cc-c273-4033-af53-bc9033ea3abe', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='memory', type='MEMORY', specParams='[node=0, size=2048]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}', minAllocatedMem='6144'}), log id: 50873daa
2019-01-17 07:56:59,855-05 INFO [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f] FINISH, SetAmountOfMemoryVDSCommand, log id: 50873daa
2019-01-17 07:56:59,862-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-22) [7059a48f] EVENT_ID: HOT_SET_MEMORY(2,039), Hotset memory: changed the amount of memory on VM HostedEngine from 4096 to 4096
2019-01-17 07:56:59,881-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (default task-22) [28fd4c82] Validation of action 'UpdateRngDevice' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING
2019-01-17 07:56:59,882-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-22) [28fd4c82] Updating RNG device of VM HostedEngine (adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. New RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}.
This message repeats throughout engine.log:
2019-01-17 07:55:43,270-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-89) [] EVENT_ID: VM_MEMORY_UNDER_GUARANTEED_VALUE(148), VM HostedEngine on host ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu> was guaranteed 8192 MB but currently has 4224 MB
As you can see attached the host has plenty of memory.
Thank you Simone!
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
On Thu, Jan 17, 2019 at 5:09 AM Simone Tiraboschi <stirabos(a)redhat.com<mailto:stirabos@redhat.com>> wrote:
On Wed, Jan 16, 2019 at 8:22 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Sorry for accidental send.
Anyway I try to increase physical memory however it won't go above 4096MB. The hypervisor has 64GB.
Do I need to modify this value with Hosted Engine offline?
No, it's not required.
Can you please attach your engine.log for the relevant time frame?
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
On Wed, Jan 16, 2019 at 1:58 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Hello
I am trying to increase Hosted Engine physical memory above 4GB
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
_______________________________________________
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/site/privacy-policy/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_site_p...>
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_commun...>
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WGSXQVVPJJ2...<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_arch...>
5 years, 9 months
