- Users - oVirt List Archives

Creating snapshot of a subset of disks
by Gianluca Cecchi 21 Jun '18

21 Jun '18

Hello, I'm trying to see how to create a snapshot of a VM, but only of a subset of its disks (actually it will be only the bootable one) Taking the examples at https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples I can accomodate something like this # Get the reference to the service that manages the virtual machines: vms_service = system_service.vms_service() # Find the virtual machine and put into data_vm vm = vms_service.list( search='name=%s' % MY_VM_NAME, all_content=True, )[0] logging.info( 'Found virtual machine \'%s\', the id is \'%s\'.', vm.name, vm.id, ) # Find the services that manage the data_vm virtual machine: vm_service = vms_service.vm_service(vm.id) # Send the request to create the snapshot. Note that this will return # before the snapshot is completely created, so we will later need to # wait till the snapshot is completely created. snaps_service = vm_service.snapshots_service() snap = snaps_service.add( snapshot=types.Snapshot( description=snap_description, persist_memorystate=False, ), ) This makes a snapshot of all the dsks of the vm. I can previously filter in my case the bootable disk with something like this: # Locate the service that manages the disk attachments of the virtual # machine: disk_attachments_service = vm_service.disk_attachments_service() # Retrieve the list of disks attachments, and print the disk details. disk_attachments = disk_attachments_service.list() for disk_attachment in disk_attachments: disk = connection.follow_link(disk_attachment.disk) print("name: %s" % disk.name) print("id: %s" % disk.id) print("status: %s" % disk.status) print("bootable: %s" % disk_attachment.bootable) print("provisioned_size: %s" % disk.provisioned_size) So in case of an example VM with two disks I get this print out name: padnpro_bootdisk id: c122978a-70d7-48aa-97c5-2f17d4603b1e status: ok bootable: True provisioned_size: 59055800320 name: padnpro_imp_Disk1 id: 5454b137-fb2c-46a7-b345-e6d115802582 status: ok bootable: False provisioned_size: 10737418240 But I haven't found then the syntax to use to specify a disk list in the block where I create the sapshot of the VM snap = snaps_service.add( snapshot=types.Snapshot( description=snap_description, persist_memorystate=False, disxk x x x ? ? ? ), ) Any help in this direction? Tahnsk, Gianluca

2 4

oVirt 4.2 and I/O threads configuration
by Gianluca Cecchi 21 Jun '18

21 Jun '18

Hello, in oVirt 4.1 I could enable I/O threads for a VM and then there was a field where I could define how many I/O threads (aka virtual scsi controllers from vm point of view). In 4.2 now I see only the option to enable them but not to specify the number. Next to the setting there is a symbol and a mouseover says "the field is not attached to any instance type" See this screenshot for the Edit VM -> Resource Allocation content: https://drive.google.com/file/d/1JzCiUBnWxS9fiY64_p5TJMY0uO5ZZUID/view?usp=… Any hints for setting the number? Thanks in advance, Gianluca

2 4

Re: [spice-list] Fwd: Fwd: VM hanging at boot - [drm] Initialized qxl
by Christophe Fergeau 20 Jun '18

20 Jun '18

On Wed, Jun 20, 2018 at 12:38:00PM +0300, Yaniv Kaul wrote: > On Wed, Jun 20, 2018 at 12:26 PM, Christophe Fergeau <cfergeau(a)redhat.com> > wrote: > > > > ---------- Forwarded message ---------- > > > > From: Leo David <leoalex(a)gmail.com> > > > > Date: Wed, Jun 13, 2018 at 8:24 PM > > > > Subject: VM hanging at boot - [drm] Initialized qxl > > > > To: users(a)ovirt.org > > > > > > > > > > > > Hello everyone, > > > > I have some Centos7 vms created from template ( CentOS 7 Generic Cloud > > > > Image v1802 for x86_64 ) > > > > I have alocated planty of resources to them, but they all have this > > issue > > > > when starting, they hang with the following message in console about > > 5-7 > > > > minutes. > > > > > > > > [drm] Initialized qxl 0.1.0 20120117 for 0000:00:02:0 on mirror 0 > > > > > > > > After a while, vm eventually boots up... > > > > Running self-hosted ovirt-node 4.2 > > > > Does anyone know what could be the issue for this behavior ? > > > > Thank you ! > > > > There were recently some hangs at startup due to a kernel bug in the qxl > > driver related to atomic modesetting, no idea if centos could be > > impacted by this or not. Does the issue go away when using another > > graphics device than QXL? > > > > Can you please respond on the oVirt users mailing list? I added it to cc: Christophe

2 1

upgrade 4.1 to 4.2
by Staniforth, Paul 20 Jun '18

20 Jun '18

Hello, I am trying to test the upgrade of our system from oVirt 4.1 to oVirt 4.2. I'm trying to restore a backup onto a test system but cannot install version 4.1 as the repos are not available. yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm yum install ovirt-engine gives http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8/repodata/repom…: [Errno 14] HTTP Error 404 - Not Found and yum --disablerepo=ovirt-4.1-centos-gluster38 install ovirt-engine gives http://mirror.centos.org/centos/7/virt/x86_64/ovirt-4.1/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found are there any alternate repos to try? Thanks, Paul S. To view the terms under which this email is distributed, please go to:- http://disclaimer.leedsbeckett.ac.uk/disclaimer/disclaimer.html

3 5

[ANN] oVirt 4.2.4 Fifth Release Candidate is now available
by Lev Veyde 20 Jun '18

20 Jun '18

The oVirt Project is pleased to announce the availability of the oVirt 4.2.4 Fifth Release Candidate, as of June 20th, 2018. This update is a release candidate of the fourth in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node is available [2] Additional Resources: * Read more about the oVirt 4.2.4 release highlights: http://www.ovirt.org/release/4.2.4/ * 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.2.4/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- Lev Veyde 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>

1 0

ovirt upgrade 4.1 -> 4.2: host bricks down
by Alex K 20 Jun '18

20 Jun '18

Hi all, I have a ovirt 2 node cluster for testing with self hosted engine on top gluster. The cluster was running on 4.1. After the upgrade to 4.2, which generally went smoothly, I am seeing that the bricks of one of the hosts (v1) are detected as down, while the gluster is ok when checked with command lines and all volumes mounted. Below is the error that the engine logs: 2018-06-17 00:21:26,309+03 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (DefaultQuartzScheduler2) [98d7e79] Error while refreshing brick statuses for volume 'vms' of cluster 'test': null 2018-06-17 00:21:26,318+03 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] (DefaultQuartzScheduler2) [98d7e79] Command 'GetGlusterLocalLogicalVolumeListVDSCommand(HostName = v0.test-group.com, VdsIdVDSCommandParametersBase:{hostId='d5a96118-ca49-411f-86cb-280c7f9c421f'})' execution failed: null 2018-06-17 00:21:26,323+03 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] (DefaultQuartzScheduler2) [98d7e79] Command 'GetGlusterLocalLogicalVolumeListVDSCommand(HostName = v1.test-group.com, VdsIdVDSCommandParametersBase:{hostId='12dfea4a-8142-484e-b912-0cbd5f281aba'})' execution failed: null 2018-06-17 00:21:27,015+03 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (DefaultQuartzScheduler9) [426e7c3d] Failed to acquire lock and wait lock 'EngineLock:{exclusiveLocks='[00000002-0002-0002-0002-00000000017a=GLUSTER]', sharedLocks=''}' 2018-06-17 00:21:27,926+03 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (DefaultQuartzScheduler2) [98d7e79] Error while refreshing brick statuses for volume 'engine' of cluster 'test': null Apart from this everything else is operating normally and VMs are running on both hosts. Any idea to isolate this issue? Thanx, Alex

7 9

cloud-init reverting static network settings to DHCP on shutdown and restart
by geoff.carr＠beazley.com 20 Jun '18

20 Jun '18

Setting static network settings in the "Initial Run" section works fine when deploying a VM from template. When using "Run" to start the VM, customization works as expected. On a reboot the network settings are maintained however if the VM is shutdown and restarted the settings are reverted to DHCP. When editing the VM the cloud-init settings are still set and a visible in the "Initial Run" section. cloud-init (0.7.9-24.el7.centos) - Previously 0.7.9-20.el7.centos but upgraded to see if it would fix the issue. oVirt engine (4.2.4.1-1.el7) Guest OS (CentOS Linux release 7.4.1708) There is another thread that reports exactly the same issue and behavior here: - https://lists.ovirt.org/pipermail/users/2018-March/087860.html Grateful for any thoughts or assistance. Regards Geoff

4 4

Hardering oVirt Engine
by Punaatua PK 19 Jun '18

19 Jun '18

Hello, we are subject to PCI-DSS. I have some questions. We currently have setup oVirt in our environnement. We created 2 Datacenter. - one with a cluster with hosted engine on gluster (Hyperconverged env) which represents the "LAN" part - one with a cluster with gluster storage wich is the DMZ In PCI-DSS we have to secure communication (use HTTPs as much as possible). I did saw that ovirt-ha-agent (on hosted-engine capable host) check the status of the engine by sending GET request on the hosted-engine on port 80 (the same check that hosted-engine --vm-status did in fact). Since ovirt 4.2.2, with the introduction of gluster eventing, a new flow (HTTP post resquest) is needed from gluster nodes to the engine. (In my case, it's a flow from the DMZ to the LAN part in HTTP (non secure) Here is my question. Is it possible to "hardering" this part of the engine ? Another question out of PCI scope. Events like warning and error in the dashboard are clean each days. I tried to find which process did that (look into /etc/cron.daily, root crontab, etc) on the engine without succes. Is there any maintenance task that is run periodicaly ? Could we have the list of all the engine's task ? (regulary check the status of host, vm, storage) also the frequency ? I would appreciate the help. (Great great product ovirt !) Thank you for your jobs ! We did manage KVM hypervisor as standalone machine without all the power that libvirt provides. No need to spend lot of money into licencing product (VSphere and co)

2 3

Re: Ovirt + Gluster : How do I gain access to the file systems of the VMs
by Hanson Turner 19 Jun '18

19 Jun '18

Hi Guys, I've an answer... Here's how I did it... First, I needed kpartx ... so #apt-get install kpartx Then setup a loopback device for the raw hdd image #losetup /dev/loop4 [IMAGE FILE] #kpartx -a /dev/loop4 This allowed me to mount the various partitions included in the VM. There you can modify the configs, make backups etc. Thanks, Hanson On 06/19/2018 09:31 AM, Hanson Turner wrote: > > Hi Sahina, > > Thanks for your reply, I can copy the files off without issue. Using > either a remote mount gluster, or just use the node and scp the files > to where I want them. > > I was asking how to/do I mount the VM's disk in a way to be able to > pull/modify files that are on the HDD of the VM. > > Thanks, > > Hason > > > On 06/19/2018 05:02 AM, Sahina Bose wrote: >> >> >> On Mon, Jun 18, 2018 at 5:12 PM, Hanson Turner >> <hanson(a)andrewswireless.net <mailto:hanson@andrewswireless.net>> wrote: >> >> Hi Guys, >> >> My engine has corrupted, and while waiting for help, I'd like to >> see if I can pull some data off the VM's to re purpose back onto >> dedicated hardware. >> >> Our setup is/was a gluster based storage system for VM's. The >> gluster data storage I'm assuming is okay, I think the hosted >> engine is hosed, and needs restored, but that's another thread. >> >> I can copy the raw disk file off of the gluster data domain. >> What's the best way to mount it short of importing it into >> another gluster domain? >> >> With vmware, we can grab the disk file and move it from server to >> server without issue. You can mount and explore contents with >> workstation. >> >> >> If you want to copy the image file. you can mount the gluster volume >> and copy it. >> using mount -t glusterfs <gluster-server>:/<volumename> <path-to-mount> >> >> >> What do we have available to us for ovirt? >> >> Thanks, >> >> _______________________________________________ >> 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://www.ovirt.org/site/privacy-policy/> >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> <https://www.ovirt.org/community/about/community-guidelines/> >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2AF5K2JERYH63… >> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/2AF5K2JERYH63…> >> >> >

2 1

General failure
by nicolas＠devels.es 19 Jun '18

19 Jun '18

Hi, We're running oVirt 4.1.9 (we cannot upgrade at this time) and we're having a major problem in our infrastructure. On friday, a snapshots were automatically created on more than 200 VMs and as this was just a test task, all of them were deleted at the same time, which seems to have corrupted several VMs. When trying to delete a snapshot on some of the VMs, a "General error" is thrown with a NullPointerException in the engine log (attached). But the worst part is that when some of these machines is powered off and then powered on, the VMs are corrupt... VM myvm is down with error. Exit message: Bad volume specification {u'index': 0, u'domainID': u'110ea376-d789-40a1-b9f6-6b40c31afe01', 'reqsize': '0', u'format': u'cow', u'bootOrder': u'1', u'address': {u'function': u'0x0', u'bus': u'0x00', u'domain': u'0x0000', u'type': u'pci', u'slot': u'0x06'}, u'volumeID': u'1fd0f9aa-6505-45d2-a17e-859bd5dd4290', 'apparentsize': '23622320128', u'imageID': u'65519220-68e1-462a-99b3-f0763c78eae2', u'discard': False, u'specParams': {}, u'readonly': u'false', u'iface': u'virtio', u'optional': u'false', u'deviceId': u'65519220-68e1-462a-99b3-f0763c78eae2', 'truesize': '23622320128', u'poolID': u'75bf8f48-970f-42bc-8596-f8ab6efb2b63', u'device': u'disk', u'shared': u'false', u'propagateErrors': u'off', u'type': u'disk'}. We're really frustrated by now and don't know how to procceed... We have a DB backup (with engine-backup) from thursday which would have a "sane" DB definition without all the snapshots, as they were all created on friday. Would it be safe to restore this backup? Any help is really appreciated... Thanks.

4 15