June 2019 - Users - oVirt List Archives

Re: option to remove a specific VM greyed out
by Strahil 03 Jun '19

03 Jun '19

Maybe, there is a deletion protection? Just go to edit and uncheck it. Best Regards, Strahil NikolovOn Jun 3, 2019 17:46, Jayme <jaymef(a)gmail.com> wrote: > > Running latest stable 4.3. I have one particular VM that is shutdown but options for removal are greyed out in the admin gui. I tried starting it and shutting it down again but still the options are not-selectable. However, they are for other VMs. > > Any idea what is different about this VM that is preventing removal from the GUI? > >

1 0

option to remove a specific VM greyed out
by Jayme 03 Jun '19

03 Jun '19

Running latest stable 4.3. I have one particular VM that is shutdown but options for removal are greyed out in the admin gui. I tried starting it and shutting it down again but still the options are not-selectable. However, they are for other VMs. Any idea what is different about this VM that is preventing removal from the GUI?

2 2

Re: Gluster Deployment Failed - No Medium Found
by Strahil 03 Jun '19

03 Jun '19

Aanother option - you do not have blacklist section in multipath (requires rebuild of initramfs + reboot). Best Regards, Strahil NikolovOn Jun 3, 2019 14:49, Sachidananda URS <surs(a)redhat.com> wrote: > > Hi Stephen, > > > On Mon, Jun 3, 2019 at 3:57 PM <smcintosh(a)tradeprint.co.uk> wrote: >> >> Good Morning, >> >> I'm completely new to this and I'm testing setting up a Gluster environment with Ovirt. However, my deployment keeps fails and I don't understand what it means. Any assistance would be much appreciated. Please see error below... >> >> Error Message >> >> TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** >> failed: [ov1.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} > > > One of the reasons for this is, the device could be having an existing partition table information. > > Can you please run the command: > > wipefs -a /dev/sdb > > On all the nodes and try again? > > -sachi >

1 0

Westmere CPU Family
by Vrgotic, Marko 03 Jun '19

03 Jun '19

Dear oVirt, For a strange reason I am convinced I have read somewhere that with 4.3 oVirt, the CPU family Westmere will not be supported any longer. Still, I see it in dropdown list after upgradingfrom 4.2 to 4.3, also after installing fresh 4.3. I also see it in oVirt documentation. Can someone tell me if its actually supported and if its going to be “discontinued” in 4.4 maybe? Thank you. Marko Vrgotic ActiveVideo

2 1

Gluster Deployment Failed - No Medium Found
by smcintosh＠tradeprint.co.uk 03 Jun '19

03 Jun '19

Good Morning, I'm completely new to this and I'm testing setting up a Gluster environment with Ovirt. However, my deployment keeps fails and I don't understand what it means. Any assistance would be much appreciated. Please see error below... Error Message TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** failed: [ov1.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} failed: [ov3.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} failed: [ov2.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* to retry, use: --limit @/usr/share/cockpit/ovirt-dashboard/ansible/hc_wizard.retry PLAY RECAP ********************************************************************* ov1.test1.lan : ok=10 changed=0 unreachable=0 failed=1 ov2.test1.lan : ok=10 changed=0 unreachable=0 failed=1 ov3.test1.lan : ok=10 changed=0 unreachable=0 failed=1 Any assistance would be much appreciated. Regards Stephen

2 1

Nvme over fabric array support through OVirt MANAGED_BLOCK_STORAGE Domain
by amit1.kumar＠intel.com 03 Jun '19

03 Jun '19

for an NVMe over fabric storage array that supports Cinder backend plugin, is it possible to use MANAGED_BLOCK_STORAGE domain to configure Virtual disk? in this case, is it required to have a single Virtual disk accessible from all the VDSM hosts (within the cluster) to support VM migration? Thanks, Amit

3 4

Re: libvirt memory leak?
by Strahil 02 Jun '19

02 Jun '19

Hi Alex, As a sys admin - I would rexommend to thoroughly check the 'journalctl' if it is permanent. If not - check libvirt logs (/var/log/something/qemu/VM-name.log -> this is based on memory). Also, if you run out of memory - the OOM killer kicked in and it will be reporting details kn /var/log/messages. Best Regards, Strahil NikolovOn Jun 2, 2019 06:37, Alex McWhirter <alex(a)triadic.us> wrote: > > After moving from 4.2 -> 4.3 libvirtd seems to be leaking memory, it > recently crashed a host by eating 123GB of RAM. Seems to follow one > specific VM around, this is the only VM i have created since 4.3, the > others were all made in 4.2 them upgraded to 4.3 > > What logs would be applicable? > > Libvirt 4.5.0 > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SB75R63BMUEWC…

1 0

Re: Uploading disk images (oVirt 4.3.3.1)
by Strahil 02 Jun '19

02 Jun '19

If you can, edit your /etc/hosts (linux client browsing the web) to point 'engine.mydomain.otherstuff.com' to the IP of the engine. I'm using the same approach but from windows and it worka for me. I am not sure but a CNAME in DNS should also work, but someone more experienced should step in. Best Regards, Strahil NikolovOn May 31, 2019 23:55, adrianquintero(a)gmail.com wrote: > > Hi, > I have an issue while trying to upload disk images thru the Web UI. > "Connection to ovirt-imageio-proxy service has failed. Make sure the service is installed, configured, and ovirt-engine certificate is registered as a valid CA in the browser." > > My ovirt engine's fqdn is ovirt-engine.mydomain.com however due to network restrictions I had to set rules in order to reach our ovirt-engine > ovirt-engine.mydomain.com = 192.168.0.45 > > For example ovirt-engine.mydomain.otherstuff.com - 192.168.10.109:80, 192.168.10.109:443, 192.168.0.45:80 > So as you can see I need to hit the ovirt-engine using ovirt-engine.mydomain.otherstuff.com which I am able to by modifyting the 11-setup-sso.conf file and adding "SSO_ENGINE_URL="https://ovirt-engine.mydomain.otherstuff.com:443/ovirt-engine/" > > I am able to upload disk images when using http://ovirt-engine.mydomain.com but not able to http://ovirt-engine.mydomain.otherstuff.com > I know it might be related to the certificates but I need to be able to upload disk images using both URLs. > > any ideas? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/QSQKTZ6YCD7XB…

1 0

Re: possible to clear vm started under different name warning in gui?
by Strahil 02 Jun '19

02 Jun '19

KVM allows the config to be updated when the feature cannot be done live. The 'poweron' is the only time KVM reads the configuration files. In our case, vdsm completely destroys the VM (virsh undefine) during poweroff and creates the VM (virsh define) during poweron. When using 'reboot' the KVM process never stops - so from Virtualization perspective , the VM never stops and thus no reread of the config. Best Regards, Strahil NikolovOn May 31, 2019 16:58, Jayme <jaymef(a)gmail.com> wrote: > > Thanks, I feel silly for not figuring that out but it looks like a full shutdown/power-off resolved it. I was only doing reboots previously. > > On Fri, May 31, 2019 at 10:47 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Have you tried to power off and then power on the VM ? >> >> Best Regards, >> Strahil Nikolov >> >> В петък, 31 май 2019 г., 8:59:54 ч. Гринуич-4, Jayme <jaymef(a)gmail.com> написа: >> >> >> When a VM is renamed a warning in engine gui appears with an exclamation point stating "vm was started with a different name". Is there a way to clear this warning? The VM has been restarted a few times since but it doesn't go away. >> >> Thanks! >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FLA643IOFHYXZ…

1 0

libvirt memory leak?
by Alex McWhirter 02 Jun '19

02 Jun '19

After moving from 4.2 -> 4.3 libvirtd seems to be leaking memory, it recently crashed a host by eating 123GB of RAM. Seems to follow one specific VM around, this is the only VM i have created since 4.3, the others were all made in 4.2 them upgraded to 4.3 What logs would be applicable? Libvirt 4.5.0

1 0