setting routing rules for guests?
by yam yam
Hello everyone!
I'm wondering there is any feature like applying routing rules for VM to reach the external network (and vice versa).
and I guess it's different according to using external provider(OVN).
if not, how to users usually assign floating IP to VM??
Thanks
Sincerely,
4 years, 4 months
Re: Clone a VM in the User Portal
by Arik Hadas
On Tue, Nov 10, 2020 at 10:10 PM tferic(a)swissonline.ch <
tferic(a)swissonline.ch> wrote:
> Cloning VM's is a core feature of virtualization.
>
> I remember having cloned VM's back in the 90's with the free VMware
> version 0.9.
>
> My main use case ever since is cloning fully configured production servers
> into a testservers, for isolated testing.
>
> Why would a hypervisor not offer cloning, when it is possible and useful?
>
> regards, Toni
>
(Added users(a)ovirt.org back)
Sure, it can be handy in some cases - that's why we've implemented it in
oVirt and enhance it in 4.4.3 (for running VMs).
But I wouldn't expect it to be commonly used via the user portal, that's
why I am interested in the use-case.
>
> On 10.11.20 16:22, Arik Hadas wrote:
>
>
>
> On Tue, Nov 10, 2020 at 4:37 PM Nicolás <nicolas(a)devels.es> wrote:
>
>> Hi Arik,
>>
>> El 10/11/20 a las 13:21, Arik Hadas escribió:
>>
>>
>>
>> On Tue, Nov 10, 2020 at 3:08 PM Nicolás <nicolas(a)devels.es> wrote:
>>
>>> Hi Sharon,
>>>
>>> Thanks for the reply! I've opened [1], so hopefully someone will be able
>>> to implement it.
>>>
>>> Regards,
>>>
>>> Nico
>>>
>>> [1]: https://github.com/oVirt/ovirt-site/issues/2389
>>>
>>> El 10/11/20 a las 11:38, Sharon Gratch escribió:
>>>
>>> Hi,
>>>
>>> This feature of cloning a VM was indeed part of the old User Portal and
>>> you are right that it's not supported by the newer VM Portal (since oVirt
>>> 4.3).
>>> It seemed that this wasn't required by VM Portal users (no user
>>> complained up till now) and that's why we omitted it and it's not part of
>>> our current roadmap to implement it as well.
>>>
>>> Nevertheless, there is no real reason not to include that ability as
>>> part of VM Portal, so you are most welcome to open an issue on
>>> https://github.com/oVirt/ovirt-web-ui/issues
>>> <https://github.com/oVirt/ovirt-site/issues>
>>> and you can push a fix yourself if you have time (or someone else from
>>> the community) :-)
>>>
>>> Thanks!
>>> Sharon
>>>
>>> On Fri, Nov 6, 2020 at 11:06 AM Nicolás <nicolas(a)devels.es> wrote:
>>>
>>>> Hi,
>>>>
>>>> We're using oVirt 4.3.8, having an organization that intensively uses
>>>> the User Portal. After upgrading from 4.2, we've noticed that cloning a
>>>> VM from within the User Portal is not possible anymore. In our case,
>>>> this feature was heavily used by hundreds of students deploying their
>>>> VMs.
>>>>
>>>
>> Out of curiosity, why cloning a VM and not provisioning the VMs from
>> template(s)?
>>
>>
>>
>> Most of our students are IT-related, and their professors want to teach
>> them the procedure to deploy a VM from scratch. Some other courses surely
>> deploy their VMs from a template as they are not that IT oriented and they
>> just want to have a working VM instead of building it from scratch. We have
>> a lot of casuistry, but in our case about 400~500 students would very
>> welcome having back the clone option.
>>
>
> Thanks Nicolás.
> I'd say that even for the IT-related students it may make more sense to
> provision VMs from templates instead of cloning VMs -
> so you want them to deploy VMs from scratch, which means starting with a
> VM that is based on the blank template, add disk(s) and other devices,
> install and configure the guest and such; and then the students would use
> clone-VM to duplicate the VM they just prepared, right?
> Why would you want them to clone the VM rather than creating a template
> out of this VM and provision further VMs from that template with
> thin-provisioned disks?
>
>
>>
>> Regards,
>>
>> Nico
>>
>>
>>>> Is this feature in the roadmap yet? If not, do you consider it useful
>>>> to
>>>> open a RFE?
>>>>
>>>> Thank you.
>>>>
>>>> Regards,
>>>>
>>>> Nico
>>>> _______________________________________________
>>>> Users mailing list -- users(a)ovirt.org
>>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HFMFJRV3AC3...
>>>>
>>>
>>> _______________________________________________
>>> Users mailing list -- users(a)ovirt.org
>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RUEW52WZUD2...
>>>
>>
>>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/QXPS6FCRT66...
>
>
4 years, 4 months
[ANN] oVirt 4.4.3 is now generally available
by Sandro Bonazzola
oVirt 4.4.3 is now generally available
The oVirt project is excited to announce the general availability of oVirt
4.4.3 , as of November 10th, 2020.
This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics, as compared to oVirt 4.3.
Important notes before you install / upgrade
Please note that oVirt 4.4 only supports clusters and data centers with
compatibility version 4.2 and above. If clusters or data centers are
running with an older compatibility version, you need to upgrade them to at
least 4.2 (4.3 is recommended).
Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
are no longer supported.
For example, the megaraid_sas driver is removed. If you use Enterprise
Linux 8 hosts you can try to provide the necessary drivers for the
deprecated hardware using the DUD method (See the users’ mailing list
thread on this at
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXE...
)
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>.
What’s new in oVirt 4.4.3 Release?
This update is the third in a series of stabilization updates to the 4.4
series.
This release is available now on x86_64 architecture for:
-
Red Hat Enterprise Linux 8.2 / 8.3
-
CentOS Linux (or similar) 8.2
-
CentOS Stream (tech preview)
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
-
Red Hat Enterprise Linux 8.2 / 8.3
-
CentOS Linux (or similar) 8.2
-
CentOS Stream (tech preview)
Please note that this release introduces cluster compatibility level 4.5
which is supported only with Red Hat Enterprise Linux 8.3 or equivalent.
oVirt Node and Appliance have been updated, including:
-
oVirt 4.4.3: https://www.ovirt.org/release/4.4.3/
-
Ansible 2.9.15:
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v...
-
Glusterfs 7.8: https://docs.gluster.org/en/latest/release-notes/7.8/
See the release notes [1] for installation instructions and a list of new
features and bugs fixed.
Notes:
-
oVirt Appliance is already available for CentOS Linux 8
-
oVirt Node NG will be available soon for CentOS Linux 8
Additional resources:
-
Read more about the oVirt 4.4.3 release highlights:
https://www.ovirt.org/release/4.4.3/
-
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] https://www.ovirt.org/release/4.4.3/
<https://www.ovirt.org/release/4.4.3/>
[2] https://resources.ovirt.org/pub/ovirt-4.4/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
4 years, 4 months
VM's gone to unknown state
by hjadavalluva＠ukaachen.de
Hello,
I have an issue with ovirt 4.3 console. The exact issue is, except hosted engine, all other VM's gone to unknown state. I wonder what's the problem is? And how bring back the VM's to normal state. I can see that nothing is enable (for instance, acktivate option, maintaiance option, etc). Can anyone guide me please in this?
Thanks in advance!
Best Regards,
Hariharan
4 years, 4 months
Re: LiveStorageMigration fail
by Christoph Köhler
yes, the output is:
-[ RECORD 1 ]---------+-------------------------------------
image_guid | 77af2f70-f3e3-4e69-a062-b0dd9970e9e3
creation_date | 2019-05-23 10:08:39+02
size | 348966092800
it_guid | 00000000-0000-0000-0000-000000000000
parentid | 00000000-0000-0000-0000-000000000000
imagestatus | 1
lastmodified | 2020-11-09 15:39:56.22+01
vm_snapshot_id | edade1d1-05ce-46a4-9929-984e5ad3e025
volume_type | 2
volume_format | 4
image_group_id | 02240cf3-65b6-487c-b5af-c266a1dd18f8
_create_date | 2018-01-11 17:31:50.075047+01
_update_date | 2020-11-09 15:41:01.008245+01
active | t
volume_classification | 1
qcow_compat | 2
On 09.11.20 17:23, Benny Zlotnik wrote:
> Can you share the output of:
> $ psql -U engine -d engine -c "\x on" -c "SELECT * FROM images where
> image_group_id = '02240cf3-65b6-487c-b5af-c266a1dd18f8';"
>
> On Mon, Nov 9, 2020 at 5:18 PM Christoph Köhler
> <koehler(a)luis.uni-hannover.de <mailto:koehler@luis.uni-hannover.de>> wrote:
>
> yes sure, here they are:
>
> On 09.11.20 15:30, Benny Zlotnik wrote:
> > Can you send me the full logs with the failure (vdsm+engine)?
> >
> > On Mon, Nov 9, 2020 at 4:26 PM Christoph Köhler
> > <koehler(a)luis.uni-hannover.de
> <mailto:koehler@luis.uni-hannover.de>
> <mailto:koehler@luis.uni-hannover.de
> <mailto:koehler@luis.uni-hannover.de>>> wrote:
> >
> > engine runs with 4.3.10.4-1
> > and yes, the message is persistently the same, so I cannot
> migrate this
> > disk.
> >
> >
> >
> > On 09.11.20 15:10, Benny Zlotnik wrote:
> > > Which version are you using?
> > > Did this happen more than once for the same disk?
> > > A similar bug was fixed in 4.3.10.1[1]
> > > There is another bug with a similar symptom which occurs very
> > rarely and
> > > we were unable to reproduce it
> > >
> > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1758048
> > >
> > > On Mon, Nov 9, 2020 at 3:57 PM Christoph Köhler
> > > <koehler(a)luis.uni-hannover.de
> <mailto:koehler@luis.uni-hannover.de>
> > <mailto:koehler@luis.uni-hannover.de
> <mailto:koehler@luis.uni-hannover.de>>
> > <mailto:koehler@luis.uni-hannover.de
> <mailto:koehler@luis.uni-hannover.de>
> > <mailto:koehler@luis.uni-hannover.de
> <mailto:koehler@luis.uni-hannover.de>>>> wrote:
> > >
> > > Hello experts,
> > >
> > > perhaps someone has an idea about that error. It appears
> when
> > in try to
> > > migrate a disk to another storage, and this live.
> Generally it
> > works
> > > good but - this is the log snippet:
> > >
> > > HSMGetAllTasksStatusesVDS failed: Error during
> destination image
> > > manipulation:
> u"image=02240cf3-65b6-487c-b5af-c266a1dd18f8, dest
> > > domain=3c4fbbfe-6796-4007-87ab-d7f205b7fae3: msg=Invalid
> > parameter:
> > > 'capacity=134217728000'"
> > >
> > > Surely the is enough space on the target domain for this
> operation
> > > (~4TB).
> > >
> > > Any ideas..?
> > >
> > > Greetings from
> > > Chris
> > > _______________________________________________
> > > Users mailing list -- users(a)ovirt.org
> <mailto:users@ovirt.org> <mailto:users@ovirt.org
> <mailto:users@ovirt.org>>
> > <mailto:users@ovirt.org <mailto:users@ovirt.org>
> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>
> > > To unsubscribe send an email to users-leave(a)ovirt.org
> <mailto:users-leave@ovirt.org>
> > <mailto:users-leave@ovirt.org <mailto:users-leave@ovirt.org>>
> > > <mailto:users-leave@ovirt.org
> <mailto:users-leave@ovirt.org> <mailto:users-leave@ovirt.org
> <mailto:users-leave@ovirt.org>>>
> > > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > > oVirt Code of Conduct:
> > > https://www.ovirt.org/community/about/community-guidelines/
> > > List Archives:
> > >
> >
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/6KT5HQXEFB477O7GW5KP4BJJUR5YBL6Q/
> > >
> >
>
4 years, 4 months
The Master data domain can't be activated
by Miguel Angel Costas
Hi all!!
I had a terrible problem with my blade and I lost the 2 nodes. I have installed a new server as a node ( ovirt-node-iso-3.6-0.999.201608311021.el7.centos.iso) but for any reason the data domain don't start. It the same node version.
The ovirt manager is 3.6.7
If I create a new datacenter I can attach a lv from the same lun with the problem..
Someone could help me.. I have been working to solve the problem fron the saturday..
Thanks!
4 years, 4 months
Cannot access ovirt engine
by suporte＠logicworks.pt
Hi,
I was installing a VM and than I notice that cannot access the CD, after this could not access the engine anymore.
The ovirt-engine service is running.
But I have this error in the engine log:
2020-11-09 13:49:16,356Z ERROR [org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataServlet.CacheUpdate.Inventory] (EE-ManagedThreadFactory-default-Thread-5) [] Could not update the Inventory Cache: Error while running SQL query: org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataException: Error while running SQL query
ovirt-engine-dwh.log
2020-11-09 13:57:21|Yd4P7G|GUQ4i7|NlyWRj|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|Default|5|tWarn|tWarn_1|Can not sample data, oVirt Engine is not updating the statistics. Please check your oVirt Engine status.|9704
ovirt-engine-4.3.4.3-1.el7.noarch
ovirt-engine-dwh-setup-4.3.8-1.el7.noarch
Any idea?
Thanks
--
Jose Ferradeira
http://www.logicworks.pt
4 years, 4 months
Change compatibility level for data center/cluster, what exactly we are changing?
by Patrick Chiang
Hi all,
From the procedure I learned at the last phase of upgrade, we should
change compatibility level for data center/cluster, respectively.
But may I know what exactly the settings we are changing - a config in a
database or in a file? Actually my question is, are these changes can lead
to any service downtime for "guest VM" or "Storage domain", "hypervisors"?
Because lately my RHV 4.2 suffered a few network disconnections and that
causes hosts to be fenced forcefully.
I hope I can collect more info here to prepare for 4.2->4.3 upgrade.
Thanks,
Patrick Chiang
4 years, 4 months
LiveStorageMigration fail
by Christoph Köhler
Hello experts,
perhaps someone has an idea about that error. It appears when in try to
migrate a disk to another storage, and this live. Generally it works
good but - this is the log snippet:
HSMGetAllTasksStatusesVDS failed: Error during destination image
manipulation: u"image=02240cf3-65b6-487c-b5af-c266a1dd18f8, dest
domain=3c4fbbfe-6796-4007-87ab-d7f205b7fae3: msg=Invalid parameter:
'capacity=134217728000'"
Surely the is enough space on the target domain for this operation (~4TB).
Any ideas..?
Greetings from
Chris
4 years, 4 months
ovirt guest agent ubuntu 16.04.6 LTS
by suporte＠logicworks.pt
What is the best way to install ovirt guest on Ubuntu 16.04.6?
What I did:
# apt-get install ovirt-guest-agent
I changed value in /etc/ovirt-guest-agent.conf to look like:
[virtio]
# device = /dev/virtio-ports/com.redhat.rhevm.vdsm
device = /dev/virtio-ports/ovirt-guest-agent.0
# systemctl start ovirt-guest-agent
Error on the log:
OSError: [Errno 13] Permission denied: '/dev/virtio-ports/ovirt-guest-agent.0
Than I set the owner and group
# chown ovirtagent:ovirtagent /dev/virtio-ports/ovirt-guest-agent.0
Than I was able to start the agent
# systemctl status ovirt-guest-agent
● ovirt-guest-agent.service - oVirt Guest Agent
Loaded: loaded (/lib/systemd/system/ovirt-guest-agent.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2020-10-31 19:50:03 WET; 9min ago
Process: 6531 ExecStartPre=/bin/chown ovirtagent:ovirtagent /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS)
Process: 6527 ExecStartPre=/bin/touch /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS)
Process: 6524 ExecStartPre=/sbin/modprobe virtio_console (code=exited, status=0/SUCCESS)
Main PID: 6537 (python)
Tasks: 3
Memory: 68.7M
CPU: 5.462s
CGroup: /system.slice/ovirt-guest-agent.service
└─6537 /usr/bin/python /usr/share/ovirt-guest-agent/ovirt-guest-agent.py
Oct 31 19:52:05 alfa.acloud.pt python[6537]: [100B blob data]
Oct 31 19:54:06 alfa.acloud.pt python[6537]: [90B blob data]
Oct 31 19:54:06 alfa.acloud.pt python[6537]: [155B blob data]
Oct 31 19:54:06 alfa.acloud.pt python[6537]: [100B blob data]
Oct 31 19:56:06 alfa.acloud.pt python[6537]: [90B blob data]
Oct 31 19:56:07 alfa.acloud.pt python[6537]: [155B blob data]
Oct 31 19:56:07 alfa.acloud.pt python[6537]: [100B blob data]
Oct 31 19:58:07 alfa.acloud.pt python[6537]: [90B blob data]
Oct 31 19:58:08 alfa.acloud.pt python[6537]: [155B blob data]
Oct 31 19:58:08 alfa.acloud.pt python[6537]: [100B blob data]
Everytime I restart the VM I need to set the owner and group
# chown ovirtagent:ovirtagent /dev/virtio-ports/ovirt-guest-agent.0
--
Jose Ferradeira
http://www.logicworks.pt
4 years, 4 months
