- Users - oVirt List Archives

global ha maintenance status via rest api
by Markus Schaufler 24 Jun '21

24 Jun '21

Hello, I'd like to check the status of "global ha maintenance" via rest api. Can't find any hint on this in the api docs - only for enable/disable... any ideas? thanks!

1 0

[ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing
by Lev Veyde 24 Jun '21

24 Jun '21

oVirt 4.4.7 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.7 Fourth Release Candidate for testing, as of June 18th, 2021. This update is the seventh in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.7 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.7 (redeploy in case of already being on 4.4.7). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.7 release highlights: http://www.ovirt.org/release/4.4.7/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.7/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

3 4

ovirt4.4 vm with windows 2008r2 bsod19
by grig.4n＠gmail.com 24 Jun '21

24 Jun '21

after migrate from ovirt4.1 to ovirt4.4 virtual mashines with windows 2008r2 bsod 0x00000019.

1 1

oVirt 4.4.5 - Windows Server 2003 VM Reboot problems
by simon＠justconnect.ie 24 Jun '21

24 Jun '21

Hi All, I've had to migrate a Windows Server 2003 R2 VM from VMWare to oVirt which I have successfully managed to get running. The problem I have is if I try to reboot from the OS I receive the following message after the VM shuts down but doesn't reboot: "Exit message: Lost connection with qemu process." Also any attempt to either shutdown or reboot from oVirt Manager has no effect. I realize that this OS is not supported in the current oVirt version, but is there something I am missing to get it working 'unsupported' please? Regards Simon...

2 1

Disk (brick) failure on my stack
by Dominique D 24 Jun '21

24 Jun '21

yesterday I had a disk failure on my stack of 3 Ovirt 4.4.1 node on each server I have 3 Bricks (engine, data, vmstore) brick data 4X600Gig raid0. /dev/gluster_vg_sdb/gluster_lv_data mount /gluster_bricks/data brick engine 2X1TB raid1 /dev/gluster_vg_sdc/gluster_lv_engine mount /gluster_bricks/engine brick vmstore 2X1TB raid1 /dev/gluster_vg_sdc/gluster_lv_vmstore mount /gluster_bricks/vmstore Everything was configured by the gui (hyperconverge and hosted-engine) It is the raid0 of the 2nd server who broke. all VMs were automatically moved to the other two servers, I haven't lost any data. the host2 is now in maintenance mode. I am going to buy 4 new SSD disks to replace the 4 disks of the defective raid0. When I'm going to erase the faulty raid0 and create the new raid with the new disks on the raid controler, how do I add in ovirt so that they resynchronize with the other bricks data? Status of volume: data Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 172.16.70.91:/gluster_bricks/data/dat a 49153 0 Y 79168 Brick 172.16.70.92:/gluster_bricks/data/dat a N/A N/A N N/A Brick 172.16.70.93:/gluster_bricks/data/dat a 49152 0 Y 3095 Self-heal Daemon on localhost N/A N/A Y 2528 Self-heal Daemon on 172.16.70.91 N/A N/A Y 225523 Self-heal Daemon on 172.16.70.93 N/A N/A Y 3121

5 5

Is there a slack channel for oVirt project?
by Jesse Hu 23 Jun '21

23 Jun '21

Hi folks, Is there a slack channel for oVirt project? and is the #ovirt channel on irc.oftc.net server still active? I'd like to learn how oVirt project can be used for building IaaS platform, and whether oVirt community is active to provide support for questions. Thanks a lot.

2 2

Problems moving vm & templates between oVirt 4.3 & 4.4
by Guillaume Pavese 23 Jun '21

23 Jun '21

On ovirt 4.4.6, I created a VM and made a template from it. I would like to copy them to oVirt 4.3.7 & 4.3.10 DCs - I saw that Export Domain is deprecated. I tried exporting the VM & template to an Export Domain anyway but, after attaching the Export DOmain on my ovirt 4.3.7 DC, both VM and Template imports failed. The Template import failed immediately without any errors visible in the UI, The VM import failed with the message "General command validation failure." - I tried to do it through a Data Domains as recommended, but: If created on oVirt 4.4.6, I get a Format V5 DataDomain that my oVirt 4.3.7 refuses to import. If created first on the oVirt 4.3 DC, I get a Format V4 Domain. But then importing it on the oVirt 4.4 DC, I get the message: "Approving this operation will upgrade the Storage Domain format from 'V4' to 'V5'. Note that you will not be able to attach it back to an older Data Center." In "Administration > Providers" everything seems supported, from XEN / KVM and even VMware (we have used all three with some success). However oVirt is the obvious missing option... I still have to try "Export as OVA", is that the only supported way? Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group -- Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. <https://interactiv-group.com/disclaimer.html>

3 6

Is there a way to find the creation date of a Virtual Machines from Ovirt Manager
by k.gunasekhar＠non.keysight.com 22 Jun '21

22 Jun '21

Is there a way to find the creation date of a Virtual Machines from Ovirt Manager command line or psql

7 9

Import Ge0-Replicated Storage Domain fails
by simon＠justconnect.ie 22 Jun '21

22 Jun '21

Hi All, I have 2 independent Hyperconverged Sites/Data Centers. Site A has a GlusterFS Replica 3 + Arbiter Volume that is Storage Domain data2 This Volume is Geo-Replicated to a Replica 3 + Arbiter Volume at Site B called data2_bdt I have simulated a DR event and now want to import the Ge0-Replicated volume data2_bdt as a Storage Domain on Site B. Once imported I need to import the VMs on this volume to run in Site B. The Geo-Replication now works perfectly (thanks Strahil) but I haven't been able to import the Storage Domain. Please can someone point me in the right direction or documentation on how this can be achieved. Kind Regards Shimme...

6 9

importing vm's from storage pool from 4.1.6.2-1 in to 4.4.6 fails due to lingering snapshot configuration in source
by Charles Kozler 22 Jun '21

22 Jun '21

I know the subject is a bit wordy but let me try to explain I have a 4.1 installation that I am migrating to 4.4. I placed the storage domain into maintenance and then rsync'ed it to the storage I am using for 4.4. In 4.4 I import the domain and it comes in fine, however, when trying to import some VM's it fails because it says it cannot find a disk. The disk ID's I cannot find anywhere in 4.1 or 4.4 so I opened OVF_STORE after upgrading the pool in 4.4 and look at the ovf file for some of the VM's that are failing to import I see this in the ovf configuration file - <Section xsi:type="ovf:SnapshotsSection_Type"> <Snapshot ovf:id="e300fa3b-eee4-4b96-9103-45115081db57"> <Type>ACTIVE</Type> <Description>Active VM</Description> <CreationDate>2019/12/19 16:47:48</CreationDate> <Memory>07d3447c-c640-4163-9cf1-74ce126d702a,59b5cfdf-015b-0333-004b-000000000397,8c48ea33-dc34-403a-90d2-a3e78776404c,1757809b-9685-4315-a92e-3ea82dc6d8a8,94a2c2b3-e02e-4b05-80eb-6f4b7a9701e7,248a9fd1-61f0-4c5a-b6ab-4630d433c6fa</Memory> </Snapshot> </Section> </Content> </ovf:Envelope> These are the disk ID's I can see failing to import in engine.log I am aware that importing a VM cannot support snapshots and have found multiple mailing list posts around this, however, I do not have any snapshots visible in 4.1 UI. I also tried modifying OVF_STORE by untar'ing it and editing the ovf files directly, however, this does not work as it ends up overwritten by ovirt with the previous configuration Any ideas? As noted, I cannot see any snapshots listed in 4.1 source pool so I therefore cannot remove this stale configuration from the source and upon importing in to 4.4 it fails because it cannot find the disks I tried import partial and that still fails which to me seems like a bug because the idea of the import partial is to still register the VM even if it cant find disks I also tried scanning domain for disks and update OVF's in the UI and it does not help anything -- *Notice to Recipient*: https://www.fixflyer.com/disclaimer <https://www.fixflyer.com/disclaimer>

2 1