Multiple NICs on hosted engine, oVirt 4.3
by Jiří Sléžka
Hello,
I would like to add second NIC to hosted engine vm (I need access to
isolated network with host's power management). I found this solution...
https://lists.ovirt.org/pipermail/users/2014-November/062610.html
...which seems to work in oVirt 3.5 but in oVirt 4.3 there is no file
like /etc/ovirt-hosted-engine/vm.conf anymore.
In the file /etc/ovirt-hosted-engine/hosted-engine.conf is a line
...
conf=/var/run/ovirt-hosted-engine-ha/vm.conf
...
which points to this config but this is a running config...
Is there a way to add a second NIC to hosted engin vm?
Cheers,
Jiri
5 years, 1 month
VM and cgroup
by yam yam
Hello,
I'm wondering why the cgroup for the VM is generated, because I thought VM and cgroup are not related.
does qemu/KVM use (memory) cgroup to handle memory resources or something else?
5 years, 1 month
manual migration
by eevans＠digitaldatatechs.com
FYI: My issue with the inability to migrate is solved. The issue was the ovirt-engine-ui-extensions-1.0.10-1.el7.noarch updated to 1.0.13 and it killed the ability to migrate.
In order to downgrade I had to download the rpm, ovirt-engine-ui-extensions-1.0.10-1.el7.noarch.rpm and run a yum downgrade command “yum downgrade ovirt-engine-ui-extensions-1.0.10-1.el7.noarch.rpm”. It would not downgrade any other way.
Once it downgraded, migration ability was back.
Thanks all for the help and support.
Eric Evans
Digital Data Services LLC.
304.660.9080
From: Jayme <jaymef(a)gmail.com>
Sent: Tuesday, February 25, 2020 9:29 AM
To: users <users(a)ovirt.org>
Subject: [ovirt-users] oVirt ansible backup improvements
If anyone has been following along, I had previously shared a blog post and GitHub repo regarding my unofficial solution for backing up oVirt VMs using Ansible.
Martin Necas reached out to me and we collaborated on some great improvements. Namely, it is now possible to run the playbook from any host without requiring direct access to storage (which I was previously using for export status verification). There were several other improvements and cleanups made as well.
The changes have been merged in and the READMME updated, you can find the project here: https://github.com/silverorange/ovirt_ansible_backup
Big thanks to Martin for helping out. Very much appreciated!
- Jayme
5 years, 1 month
Artwork: 4.4 GA banners
by Sandro Bonazzola
Hi,
in preparation of oVirt 4.4 GA it would be nice to have some graphics we
can use for launching oVirt 4.4 GA on social media and oVirt website.
If you don't have coding skills but you have marketing or design skills
this is a good opportunity to contribute back to the project.
Looking forward to your designs!
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>*
<https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>*
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
5 years, 1 month
NFS permissions error on ISODomain file with correct permissions
by Shareef Jalloq
Hi,
I asked this question in another thread but it seems to have been lost in
the noise so I'm reposting with a more descriptive subject.
I'm trying to start a Windows VM and use the virtio-win VFD floppy to get
the drivers but the VM startup fails due to a permissions issue detailed
below. The permissions look fine to me so why can't the VFD be read?
Shareef.
I found a permissions issue in the engine.log:
2020-03-25 21:28:41,662Z ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ForkJoinPool-1-worker-14) [] EVENT_ID: VM_DOWN_ERROR(119), VM win-2019 is
down with error. Exit message: internal error: qemu unexpectedly closed the
monitor: 2020-03-25T21:28:40.324426Z qemu-kvm: -drive
file=/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/11111111-1111-1111-1111-111111111111/virtio-win_servers_amd64.vfd,format=raw,if=none,id=drive-ua-0b9c28b5-f75c-4575-ad85-b5b836f67d61,readonly=on:
Could not open '/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/11111111-1111-1111-1111-111111111111/virtio-win_servers_amd64.vfd':
Permission denied.
But when I look at that path on the node in question, every folder and the
final file have the correct vdsm:kvm permissions:
[root@ovirt-node-01 ~]# ll /rhev/data-center/mnt/nas-01.phoelex.com:
_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/11111111-1111-1111-1111-111111111111/virtio-win_servers_amd64.vfd
-rwxrwxrwx. 1 vdsm kvm 2949120 Mar 25 21:24
/rhev/data-center/mnt/nas-01.phoelex.com:
_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/11111111-1111-1111-1111-111111111111/virtio-win_servers_amd64.vfd
The files were uploaded to the ISO domain using:
engine-iso-uploader --iso-domain=iso_storage upload virtio-win.iso
virtio-win_servers_amd64.vfd
5 years, 1 month
Re: Windows VirtIO drivers
by Shareef Jalloq
I can't seem to do anything. If I hit the Windows key and start typing, I
get a black popup with no options. Win+R doesn't do anything aside from
spit out a GSpice critical error in the terminal I'm running remote-viewer
from.
You spend a week trying to launch a VM and when you do, you can't do nowt.
:-)
On Thu, Apr 2, 2020 at 5:24 PM Robert Webb <rwebb(a)ropeguru.com> wrote:
> I have yet to figure that one out. All of the VM's I built I had to go old
> school with the tab key and arrow keys...
>
> Very annoying..
>
> ________________________________________
> From: Shareef Jalloq <shareef(a)jalloq.co.uk>
> Sent: Thursday, April 2, 2020 12:21 PM
> To: eevans(a)digitaldatatechs.com
> Cc: Robert Webb; users(a)ovirt.org
> Subject: Re: [ovirt-users] Re: Windows VirtIO drivers
>
> Any idea what I need to do to get a working mouse in a Windows VM? I can
> click on the SPICE viewer but the mouse pointer is fixed to the left hand
> border.
>
> On Thu, Apr 2, 2020 at 4:38 PM Shareef Jalloq <shareef(a)jalloq.co.uk
> <mailto:shareef@jalloq.co.uk>> wrote:
> Sorry, I missed all these replies. Thanks for the help.
>
> I just noticed something funny in the Windows installer. When you get to
> the point where it can't find any installation media, if you Load Driver, a
> popup appears with a Browse and OK/Cancel options. I assumed that I should
> be browsing to the floppy here but if you do that, you get an error that no
> signed drivers can be found. Instead, you just have to hit OK when the
> popup appears and that somehow finds the drivers.
>
> I'm assuming that I will need to install the network driver once the
> installation has finished?
>
> On Wed, Mar 25, 2020 at 8:37 PM <eevans(a)digitaldatatechs.com<mailto:
> eevans(a)digitaldatatechs.com>> wrote:
> Ok. Personally, I like having an ISO repository, but I like the fact that's
> it will be optional.
> Thanks.
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -----Original Message-----
> From: Robert Webb <rwebb(a)ropeguru.com<mailto:rwebb@ropeguru.com>>
> Sent: Wednesday, March 25, 2020 4:26 PM
> To: eevans(a)digitaldatatechs.com<mailto:eevans@digitaldatatechs.com>;
> 'Shareef Jalloq' <shareef(a)jalloq.co.uk<mailto:shareef@jalloq.co.uk>>;
> users(a)ovirt.org<mailto:users@ovirt.org>
> Subject: Re: [ovirt-users] Re: Windows VirtIO drivers
>
> It does work that way.
>
> I found that out as I was testing oVirt and had not created a separate ISO
> Domain. I believe it was Strahil who pointed me in the right direction.
>
> So if one does not have an ISO Domain, it is no longer required. Along with
> the fact that ISO Domains are or in the process of being deprecated.
>
> ________________________________________
> From: eevans(a)digitaldatatechs.com<mailto:eevans@digitaldatatechs.com> <
> eevans(a)digitaldatatechs.com<mailto:eevans@digitaldatatechs.com>>
> Sent: Wednesday, March 25, 2020 3:13 PM
> To: Robert Webb; 'Shareef Jalloq'; users(a)ovirt.org<mailto:users@ovirt.org>
> Subject: RE: [ovirt-users] Re: Windows VirtIO drivers
>
> That may be true, but in the ISO domain, when you open virt viewer you can
> change the cd very easily...maybe it works that way as well..
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -----Original Message-----
> From: Robert Webb <rwebb(a)ropeguru.com<mailto:rwebb@ropeguru.com>>
> Sent: Wednesday, March 25, 2020 2:35 PM
> To: eevans(a)digitaldatatechs.com<mailto:eevans@digitaldatatechs.com>;
> 'Shareef Jalloq' <shareef(a)jalloq.co.uk<mailto:shareef@jalloq.co.uk>>;
> users(a)ovirt.org<mailto:users@ovirt.org>
> Subject: [ovirt-users] Re: Windows VirtIO drivers
>
> Don't think you have to use the ISO Domain any longer.
>
> You can upload to a Data Domain and when you highlight the VM in the
> management GUI, select the three dots in the top left for extra options and
> there is a change cd option. That option will allow for attaching an ISO
> from a Data Domain.
>
> That is what I recall when I was using oVirt a month or so ago.
>
> ________________________________________
> From: eevans(a)digitaldatatechs.com<mailto:eevans@digitaldatatechs.com> <
> eevans(a)digitaldatatechs.com<mailto:eevans@digitaldatatechs.com>>
> Sent: Wednesday, March 25, 2020 2:28 PM
> To: 'Shareef Jalloq'; users(a)ovirt.org<mailto:users@ovirt.org>
> Subject: [ovirt-users] Re: Windows VirtIO drivers
>
> You have to copy the iso and vfd files to the ISO domain to make them
> available to the vm's that need drivers.
>
> engine-iso-uploader options list
> # engine-iso-uploader options upload file file file Documentation is found
> here: https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
> [cid:image001.jpg@01D602B1.9FEA2EC0]
>
> From: Shareef Jalloq <shareef(a)jalloq.co.uk<mailto:shareef@jalloq.co.uk>>
> Sent: Wednesday, March 25, 2020 1:51 PM
> To: users(a)ovirt.org<mailto:users@ovirt.org>
> Subject: [ovirt-users] Windows VirtIO drivers
>
> Hi,
>
> it seems the online documentation regarding the windows installation steps
> is well out of date. Where is there any current documentation on where to
> get the VirtIO drivers for a Windows installation?
>
> From a bit of Googling, it seems that I need to 'yum install virtio-win' on
> the engine VM and then copy the relevant .iso/.vfd to the ISO domain. Is
> that correct?
>
> Where is the documentation maintained and how do I open a bug on it?
>
> Thanks, Shareef.
>
>
>
>
>
5 years, 1 month
New Issue - Ovirt Status shows '?' or Down for all elements
by Mark Steele
Yesterday we had a storage crash that caused our hosted engine to stop and
not auto-restart. We manually restarted it and this morning, all elements
are showing a status of either question mark '?' or a red down chevron.
We are running version oVirt Engine Version: 3.5.0.1-1.el6.
We are chasing it down and see this in the log:
2020-04-01 10:15:53,060 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(DefaultQuartzScheduler_Worker-23) Failed to refresh VDS , vds =
e98f8f1d-dd1d-47c4-b039-d6eaaf578317 : hv-06, VDS Network Error,
continuing
Any insight into what might be causing this or the fix would be appreciated.
***
*Mark Steele*
5 years, 1 month
Re: Windows VirtIO drivers
by eevans＠digitaldatatechs.com
Ok. Personally, I like having an ISO repository, but I like the fact that's
it will be optional.
Thanks.
Eric Evans
Digital Data Services LLC.
304.660.9080
-----Original Message-----
From: Robert Webb <rwebb(a)ropeguru.com>
Sent: Wednesday, March 25, 2020 4:26 PM
To: eevans(a)digitaldatatechs.com; 'Shareef Jalloq' <shareef(a)jalloq.co.uk>;
users(a)ovirt.org
Subject: Re: [ovirt-users] Re: Windows VirtIO drivers
It does work that way.
I found that out as I was testing oVirt and had not created a separate ISO
Domain. I believe it was Strahil who pointed me in the right direction.
So if one does not have an ISO Domain, it is no longer required. Along with
the fact that ISO Domains are or in the process of being deprecated.
________________________________________
From: eevans(a)digitaldatatechs.com <eevans(a)digitaldatatechs.com>
Sent: Wednesday, March 25, 2020 3:13 PM
To: Robert Webb; 'Shareef Jalloq'; users(a)ovirt.org
Subject: RE: [ovirt-users] Re: Windows VirtIO drivers
That may be true, but in the ISO domain, when you open virt viewer you can
change the cd very easily...maybe it works that way as well..
Eric Evans
Digital Data Services LLC.
304.660.9080
-----Original Message-----
From: Robert Webb <rwebb(a)ropeguru.com>
Sent: Wednesday, March 25, 2020 2:35 PM
To: eevans(a)digitaldatatechs.com; 'Shareef Jalloq' <shareef(a)jalloq.co.uk>;
users(a)ovirt.org
Subject: [ovirt-users] Re: Windows VirtIO drivers
Don't think you have to use the ISO Domain any longer.
You can upload to a Data Domain and when you highlight the VM in the
management GUI, select the three dots in the top left for extra options and
there is a change cd option. That option will allow for attaching an ISO
from a Data Domain.
That is what I recall when I was using oVirt a month or so ago.
________________________________________
From: eevans(a)digitaldatatechs.com <eevans(a)digitaldatatechs.com>
Sent: Wednesday, March 25, 2020 2:28 PM
To: 'Shareef Jalloq'; users(a)ovirt.org
Subject: [ovirt-users] Re: Windows VirtIO drivers
You have to copy the iso and vfd files to the ISO domain to make them
available to the vm's that need drivers.
engine-iso-uploader options list
# engine-iso-uploader options upload file file file Documentation is found
here: https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html
Eric Evans
Digital Data Services LLC.
304.660.9080
[cid:image001.jpg@01D602B1.9FEA2EC0]
From: Shareef Jalloq <shareef(a)jalloq.co.uk>
Sent: Wednesday, March 25, 2020 1:51 PM
To: users(a)ovirt.org
Subject: [ovirt-users] Windows VirtIO drivers
Hi,
it seems the online documentation regarding the windows installation steps
is well out of date. Where is there any current documentation on where to
get the VirtIO drivers for a Windows installation?
From a bit of Googling, it seems that I need to 'yum install virtio-win' on
the engine VM and then copy the relevant .iso/.vfd to the ISO domain. Is
that correct?
Where is the documentation maintained and how do I open a bug on it?
Thanks, Shareef.
5 years, 1 month
Hosted Engine stalled and unable to restart
by Mark Steele
Hello,
We are on an older version (3.x - cannot be specific as I cannot get my
ovirt hosted engine up).
We experienced a storage failure earlier this evening - the hosted engine
was originally installed with this storage domain although we have moved
all VM's and disks off of it.
The storage was restored and all the VM's are now running, but the ovirt
engine is not pinging and is unreachable.
I have attempted to locate it on my HV's using 'virsh list --all' but only
one of those is taking my credentials - all the others fail to authenticate.
Is there a way to locate what the credentials are on each HV since the
default is not working? Additionally, is there any other way to locate the
hosted engine and restart it directly from a HV?
Thank you for your time and consideration.
***
*Mark Steele*
5 years, 1 month
