- Users - oVirt List Archives

Re: Hosted Engine I/O scheduler
by Strahil 21 Mar '19

21 Mar '19

Hi Darrel, Still, based on my experience we shouldn't queue our I/O in the VM, just to do the same in the Host. I'm still considering if I should keep deadline in my hosts or to switch to 'cfq'. After all, I'm using Hyper-converged oVirt and this needs testing. What I/O scheduler are you using on the host? Best Regards, Strahil NikolovOn Mar 18, 2019 19:15, Darrell Budic <budic(a)onholyground.com> wrote: > > Checked this on mine, see the same thing. Switching the engine to noop definitely feels more responsive. > > I checked on some VMs as well, it looks like virtio drives (vda, vdb….) get mq-deadline by default, but virtscsi gets noop. I used to think the tuned profile for virtual-guest would set noop, but apparently not… > > -Darrell > >> On Mar 18, 2019, at 1:58 AM, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Hi All, >> >> I have changed my I/O scheduler to none and here are the results so far: >> >> Before (mq-deadline): >> Adding a disk to VM (initial creation) START: 2019-03-17 16:34:46.709 >> Adding a disk to VM (initial creation) COMPLETED: 2019-03-17 16:45:17.996 >> >> After (none): >> Adding a disk to VM (initial creation) START: 2019-03-18 08:52:02.xxx >> Adding a disk to VM (initial creation) COMPLETED: 2019-03-18 08:52:20.xxx >> >> Of course the results are inconclusive, as I have tested only once - but I feel the engine more responsive. >> >> Best Regards, >> Strahil Nikolov >> >> В неделя, 17 март 2019 г., 18:30:23 ч. Гринуич+2, Strahil <hunter86_bg(a)yahoo.com> написа: >> >> >> Dear All, >> >> I have just noticed that my Hosted Engine has a strange I/O scheduler: >> >> Last login: Sun Mar 17 18:14:26 2019 from 192.168.1.43 >> [root@engine ~]# cat /sys/block/vda/queue/scheduler >> [mq-deadline] kyber none >> [root@engine ~]# >> >> Based on my experience anything than noop/none is useless and performance degrading for a VM. >> >> Is there any reason that we have this scheduler ? >> It is quite pointless to process (and delay) the I/O in the VM and then process (and again delay) on Host Level . >> >> If there is no reason to keep the deadline, I will open a bug about it. >> >> Best Regards, >> Strahil Nikolov >> >> Dear All, >> >> I have just noticed that my Hosted Engine has a strange I/O scheduler: >> >> Last login: Sun Mar 17 18:14:26 2019 from 192.168.1.43 >> [root@engine ~]# cat /sys/block/vda/queue/scheduler >> [mq-deadline] kyber none >> [root@engine ~]# >> >> Based on my experience anything than noop/none is useless and performance degrading for a VM. >> >>

4 5

Backup Ovirt VMs with Python not working
by daniel94.oeller＠gmail.com 20 Mar '19

20 Mar '19

Hello, I have set up Ovirt Backup how it is explained in this link: http://blog.infratic.com/create-ovirtrhevs-vm-backup/ I also have changed the settings on the default.conf. When I started the backup it works until it begins to create the qcow2 file It writes: qemu-img: Could not open '/home/DC01/2019-03-20-20/DC01_Disk1.qcow2': Failed to get shared "write" lock Is another process using the image? Have anyone ideas and can help me? Thanks

2 1

Re: Save Virtual Machine in NFS partition
by Strahil 20 Mar '19

20 Mar '19

Hi , Without the engine - this will be hard.The engine knows the configuration and the disks of each VM so the Hypervisor can start it. In your case I would focus on the engine as this could be (or not) the easier approach. Otherwise you need to run qemu-img against each image (just an uuid, no meta or lease ) , find your image and copy it to a standalone KVM. Once you have the disk, you should try to recall what was the host CPU type (should be the same on the whole cluster) and create a new VM using a COPY of your image . If KVM manages to start and the machine boots - you are done. As you can see , fixing the engine might be easier - especially with the help of the community. Best Regards, Strahil NikolovOn Mar 20, 2019 18:01, siovelrm(a)gmail.com wrote: > > Hi, I had problems with my ovirt-engine and it does not raise. I have some virtual machines in an NFS domain that is located in one of the nodes and I want to get one of the virtual machines. The problem is that what appears is a series of identifiers (ID) and I don't know what the virtual machine is, because by name I can not find it. There are some .meta files where I can see the Description of some Virtual Machines. Please I need help > _______________________________________________ > 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/NXNAZBOSGTIRC…

1 0

Save Virtual Machine in NFS partition
by siovelrm＠gmail.com 20 Mar '19

20 Mar '19

Hi, I had problems with my ovirt-engine and it does not raise. I have some virtual machines in an NFS domain that is located in one of the nodes and I want to get one of the virtual machines. The problem is that what appears is a series of identifiers (ID) and I don't know what the virtual machine is, because by name I can not find it. There are some .meta files where I can see the Description of some Virtual Machines. Please I need help

1 0

4.2.7 Importing qcow2 linux as disk
by Arnaud DEBEC 20 Mar '19

20 Mar '19

Hi, I want to import a Centos 7 qcow2 VM on oVirt 4.2.7. 0. the Centos 7 VM was previously running under libvirt / kvm hypervisor. 1. on Ovirt 4.2.7, I imported the VM qcow2 via Storage > Disks > Upload > Start > etc. 2. I created a VM and attached the disk and specifying the disk is bootable 3. When the machine boots, I get "Warning: /dev/disk/by-uuid/XXXXXXXXXX does not exist" Before going in deeper detail in the investigation, I would like to make sure if the previous steps make sens for importing a VM under qcow2 format. Most of documentation I found to import libvirt /KVM are done by using the Compute > VM > import > KVM (via Libvirt) which is not what I am looking for. Thank you.

1 0

Fwd: Re: Change cluster cpu type with hosted engine
by Fabrice SOLER 20 Mar '19

20 Mar '19

Hi, As you can read on the screenshot below, my servers have got Nehalem CPU type, so the hosted engine detect the correct CPU type. You can read on this link https://www.intel.com/content/www/us/en/support/articles/000006105/processo… that Windows 10 x64 does not support Nehalem CPU type. Bill is cutting the fonctionnality for the old CPU, I will be able to comment but i will not. But I need to use Windows 10 x64 with this servers for my students !!! I am in a dead-end. Sincerely, Fabrice SOLER -------- Message transféré -------- Sujet : Re: [ovirt-users] Change cluster cpu type with hosted engine Date : Tue, 12 Mar 2019 15:49:14 -0400 De : Fabrice SOLER <fabrice.soler(a)ac-guadeloupe.fr> Pour : Simone Tiraboschi <stirabos(a)redhat.com> Le 12/03/2019 à 11:21, Simone Tiraboschi a écrit : > > > On Tue, Mar 12, 2019 at 1:03 PM Fabrice SOLER > <fabrice.soler(a)ac-guadeloupe.fr > <mailto:fabrice.soler@ac-guadeloupe.fr>> wrote: > > Hello, > > I need to create a windows 10 virtual machine but I have an error : > > I have a fresh ovirt installation (version 4.2.8) with an hosted > engine. At the hosted engine installation there was no question > about the cluster cpu type, it should be great if in the future > version it could be. > > > It's by design: we simply let the engine choose the best CPU according > to the characteristics of the first host. > Can you please detail which CPU are you using on the first host and > how the engine detected it adding the first host to the first cluster? Hello, The first host is a DELL R610 (an old server). At the installation, the cluster was created with an CPU Architecture x86_64 and CPU type Intel Nehalem Family. > > To change an host to another cluster this host need to be in > maintenance mode, and the hosted engine will be power off. > > I have created another Cluster with an SandyBridge Family CPU > type, but to move the hosted engine to this new cluster the hosted > should be power off. > > Is there someone who can help ? > > Sincerely, > > -- > _______________________________________________ > 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/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/KFH3ZLPA7KZSS… > --

1 0

[ANN] oVirt 4.3.2 is now generally available
by Sandro Bonazzola 20 Mar '19

20 Mar '19

The oVirt Project is pleased to announce the general availability of oVirt 4.3.2, as of March 19th, 2019. This update is the second in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] oVirt Node has been updated including: - oVirt 4.3.2: http://www.ovirt.org/release/4.3.2/ - Latest CentOS updates (no relevant errata available up to now on https://lists.centos.org/pipermail/centos-announce ) Additional Resources: * Read more about the oVirt 4.3.2 release highlights: http://www.ovirt.org/release/4.3.2/ * 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.3.2/ [2] http://resources.ovirt.org/pub/ovirt-4.3/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 3

Re: Can't connect "https://FQDN/ovirt-engine" after reinstall ovirt-engine
by Александр Егоров 20 Mar '19

20 Mar '19

How do I repair the ovirt-engine? engine.log in attachment

2 1

Re: vender_id syntax UserDefinedVMProperties
by Strahil 20 Mar '19

20 Mar '19

Can't you make the script check if it windows or Linux and skip if it's Linux? Best Regards, Strahil NikolovOn Mar 19, 2019 23:02, Darin Schmidt <darinschmidt(a)gmail.com> wrote: > > You also need to have this code hooked in: > cd /usr/libexec/vdsm/hooks/before_vm_start/ > vi 99_mask_kvm > > #!/usr/bin/python2 > > import hooking > domxml = hooking.read_domxml() > > hyperv = domxml.getElementsByTagName('hyperv')[0] > smm = domxml.createElement('vendor_id') > smm.setAttribute('state', 'on') > smm.setAttribute('value', '1234567890ab') > hyperv.appendChild(smm) > > features = domxml.getElementsByTagName('features')[0] > kvm = domxml.createElement('kvm') > hidden = domxml.createElement('hidden') > hidden.setAttribute('state', 'on') > kvm.appendChild(hidden) > features.appendChild(kvm) > > hooking.write_domxml(domxml) > > > only problem now is that I cant boot a linux VM with the vendor_is portion there...... > > On Mon, Mar 18, 2019 at 3:30 PM Darin Schmidt <darinschmidt(a)gmail.com> wrote: >> >> Seems that the system has to be running with bios Q35 UEFI. Standard bios does not work. System is operational now. >> >> On Mon, Mar 18, 2019, 6:30 AM Darin Schmidt <darinschmidt(a)gmail.com> wrote: >>> >>> Still no luck getting the gtx 1080 to enable inside the VM. I see the code is being generated in the xml with the hook. But I still get error code 43. Someone mentioned doing it with eufi bios and that worked for them. So when I get back from work today, perhaps ill give that a try. >>> >>> On Mon, Mar 18, 2019, 6:10 AM Darin Schmidt <darinschmidt(a)gmail.com> wrote: >>>> >>>> I have gotten the system to see the card, its in device manager. The problem seems to be that I cannot use it in the VM because from what I have been finding out is that it gets and error code 43. Nvidia drivers disable the card if it detects that its being used in a VM. I have found some code to use to hook it into the xml before_vm_starts. >>>> >>>> 99_mask_kvm >>>> #!/usr/bin/python2 >>>> >>>> import hooking >>>> domxml = hooking.read_domxml() >>>> >>>> hyperv = domxml.getElementsByTagName('hyperv')[0] >>>> smm = domxml.createElement('vendor_id') >>>> smm.setAttribute('state', 'on') >>>> smm.setAttribute('value', '1234567890ab') >>>> hyperv.appendChild(smm) >>>> >>>> features = domxml.getElementsByTagName('features')[0] >>>> kvm = domxml.createElement('kvm') >>>> hidden = domxml.createElement('hidden') >>>> hidden.setAttribute('state', 'on') >>>> kvm.appendChild(hidden) >>>> features.appendChild(kvm) >>>> >>>> hooking.write_domxml(domxml) >>>> >>>> >>>> I am currently reinstalling the drivers to see if this helps. >>>> >>>> kvm off and vender_id is now in the xml code that get generated when the VM is started. Im going off of examples Im finding online. Perhaps I just need to add the 10de to it instead of some generic # others are using. >>>> >>>> On Mon, Mar 18, 2019 at 6:02 AM Nisim Simsolo <nsimsolo(a)redhat.com> wrote: >>>>> >>>>> Hi >>>>> >>>>> Vendor ID of Nvidia is usually 10de. >>>>> You can locate 'vendor ID:

2 1

Daily reboots of Hosted Engine?
by Juhani Rautiainen 20 Mar '19

20 Mar '19

Hi! Hosted engine reboots itself almost daily. Is this by design? If not, where should I be searching for the clues why it shuts down? Someone is giving reboot order to HE because /var/log/messages in contains this: Mar 19 12:05:00 ovirtmgr qemu-ga: info: guest-shutdown called, mode: powerdown Mar 19 12:05:00 ovirtmgr systemd: Started Delayed Shutdown Service. And I'm still running v4.3.0 because upgrade to that was bit painful and haven't dared to new round. Thanks, -Juhani

3 9