[ovirt-users] Re: Big problem on Ovirt 4.4

[Strahil Nikolov via Users]

Even if you start with brand new engine you can still import the storage 
domains and the VMs inside it.Drawback -> you might have to delete any VM 
snapshots prior the import.
Best Regards,Strahil Nikolov
 
 
  On Fri, Mar 25, 2022 at 13:40, Michal Skrivanek 
wrote:   ___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/KW6NQOM2JOBFXKK236H3K5UUR7ZFF24S/
  
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/KKAG3VUWFBVWBOTVDUA643TZH7IO55W4/

[ovirt-users] Re: change mount point for hosted_storage

[tpike]

I have resolved this issue. I'll document what I did here in case someone else 
finds this through Google or something. I basically found this note on this 
form (I believe) which outlined the steps:
The following procedure should provide the solution:

1. set the storage domain to maintenance (via webadmin UI, for example)
2. copy/sync the contents of the storage domain including the metadata, to 
ensure that data in both locations (the old and the new mount points) is the 
same.
3. run modification query on ovirt engine database (please replace the values 
'yournewmountpoint' and 'therelevantconnectionid' with the correct ones:
UPDATE storage_server_connections 
SET connection='yournewmountpoint' 
WHERE id='therelevantconnectionid';
4. There is a bug related to storage domain caching in VDSM (host) , so it 
needs to be workarounded by restarting vdsm (service name is 'vdsmd')
5. activate storage domain (via webadmin UI, for example).

So, since this was the storage domain that had the hosted_storage on it, I had 
to do more steps for safety:

 - stop all VMs
 - shutdown all hosts except for the one running hosted-engine
 - enter global maintenance
 - log into the hosted-engine VM
 - systemctl stop ovirt-engine
 - use psql as above to edit the connection information for the storage domain 
I was interested in
 - reboot the host running the hosted-engine
 - exit global maintenance
 - reboot all the other hosts and bring them back into the cluster
 - restart all VMs

It certainly is possible that this global shutdown wasn't totally necessary, 
but this cluster isn't in production yet and I thought this was the safest 
course of action.

Tod Pike
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SCSEX62AU3QOE7KS5DHXNM72B4H5MWBS/

[ovirt-users] Re: Correct way to search VM by mac

[Gianluca Cecchi]

On Fri, Mar 25, 2022 at 3:54 PM  wrote:

> Hi,
>
> We have a Python-SDK script to find MAC dupes in our infrastructure.
>
> Thanks for it, Nicolas.
But does it work if you have separate engines and in a scenario like mine?
Even if you have a mac pool, you could import a VM and have it retain its
original mac, that could be out of the mac pools normally admitted in that
environment.
It seems that your script has the variable below to adapt:
# Replace this with your active MAC address pools, WITHOUT the last octet
MACPOOLS = ['00:11:22:33:44', '00:55:66:77:88']

I will dig into your script, anyway.
In the meantime, querying the engine db I used something like this to find
the last two characters when the first ones are of type aa:bb:cc:dd:ee (or
in general to match what I need):

select substring(mac_addr from 16 for 2) as value from vm_interface where
mac_addr like 'aa:bb:cc:dd:ee%' order by value;

and then if I find anything in common in env1 and env2 (such as ff for last
two characters) and want to see which VMs are involved I can use

select vm_name from vm_interface,vm_static where
vm_interface.vm_guid=vm_static.vm_guid and mac_addr='aa:bb:cc:dd:ee:ff'

Gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ON4RQJQF6GKXHCNPI6NIDEXIIZTRAYGI/

[ovirt-users] Re: No bootable device

[Angus Clarke]

Hi Nicolas

You could try "fixing" the VM OS boot process by booting into rescue mode from 
the VM Linux distribution's installation CD - you'd need to read up on 
re-writing the boot software (probably grub.)

and/or you could look at exporting the disk back to VirtuaBox and trying to 
boot it there.

Regards
Angus


From: nico...@devels.es 
Sent: 25 March 2022 12:49
To: users@ovirt.org 
Subject: [ovirt-users] Re: No bootable device

Hi _isi_,

I already tried with all chipset/firmwares available. Still I get the
same result, it cannot boot with that disk. Not sure what the problem
actually is, as I said, I'm pretty sure the disk is bootable under
VirtualBox.

Thanks.

El 2022-03-23 14:50, uli.i...@elkb.de escribió:
> Hi,
>
> I guess you should check Chipset / Firmware Type Setting of VM. If it
> is UEFI or BIOS boot.
>
> _isi_
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: 
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.htmldata=04%7C01%7C%7C16e221618e6340794e2908da0e55fa6f%7C84df9e7fe9f640afb435%7C1%7C0%7C637838059693468774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=zG5W8dcEJHBhSzHX%2Fi%2BK6lJxsmXlMXL0UVduH1Tr6NM%3Dreserved=0
> oVirt Code of Conduct:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2Fdata=04%7C01%7C%7C16e221618e6340794e2908da0e55fa6f%7C84df9e7fe9f640afb435%7C1%7C0%7C637838059693468774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=N9VGdnap%2BX3g1s44z0Da%2BwT9m5aIuTF3gXUGeMryG8U%3Dreserved=0
> List Archives:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2FFUMIPVESOS4LVHQ24R4IAAE3S6L7NH5Z%2Fdata=04%7C01%7C%7C16e221618e6340794e2908da0e55fa6f%7C84df9e7fe9f640afb435%7C1%7C0%7C637838059693468774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=WMQBNXzckHM9fxbebdFV9C413s5EjsYQutj%2BvjaJHnY%3Dreserved=0
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.htmldata=04%7C01%7C%7C16e221618e6340794e2908da0e55fa6f%7C84df9e7fe9f640afb435%7C1%7C0%7C637838059693468774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=zG5W8dcEJHBhSzHX%2Fi%2BK6lJxsmXlMXL0UVduH1Tr6NM%3Dreserved=0
oVirt Code of Conduct: 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2Fdata=04%7C01%7C%7C16e221618e6340794e2908da0e55fa6f%7C84df9e7fe9f640afb435%7C1%7C0%7C637838059693468774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=N9VGdnap%2BX3g1s44z0Da%2BwT9m5aIuTF3gXUGeMryG8U%3Dreserved=0
List Archives: 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2FKGJWLIC7S3LTRPHN2VNGVVFL5REBCQFX%2Fdata=04%7C01%7C%7C16e221618e6340794e2908da0e55fa6f%7C84df9e7fe9f640afb435%7C1%7C0%7C637838059693468774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=JVP9c9MGdET8BZd4UZPvy7pgbvOeROkBl092O7o0WzE%3Dreserved=0
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/A5LAYOCWPHWAXUGA6CLCMFZOCELFN4MZ/

[ovirt-users] Re: Correct way to search VM by mac

[nicolas]

Hi,

We have a Python-SDK script to find MAC dupes in our infrastructure.

I'm attaching the script, you just need to set the URI, USERNAME, 
PASSWORD, CERTPATH and MACPOOLS variables.


Hope this helps.

Regards,

Nicolás

El 2022-03-25 14:35, Gianluca Cecchi escribió:

Sorry, incomplete message sent...

today I had a problem about conflicting MAC between two different VMs.
The source of the problem was a VM created on env1 managed by engine1
and then transferred some weeks ago to env2 managed by engine2.
The two envs share some networks and during migration I didn't change
the mac of the vnic after completing it.
So the mac was left free from env1 and used in env2.

The default mac pools are different ones between env1 and env2.
So today in env1 I created a new vm on the same vlan as the previous
one and oVirt assigned the previous one mac, now freed on it,
originating big problems...
I found an article (https://access.redhat.com/solutions/695383) to
search in the engine web admin by mac, but it was for version 3.2 and
it seems it doesn't work in 4.4.10.
In VMs page I search filling the query with

mac = my_mac
or

Vms: mac = my_mac

but it keeps thinking with 3 squares blinking in the page. I have not
so many VMs to justify time elapsing... (less then 50)

Can I search for mac? How?

Thanks,

Gianluca

On Fri, Mar 25, 2022 at 3:27 PM Gianluca Cecchi
 wrote:


Hello,
today I had a problem about conflicting MAC.
The source of problem was a VM transferred from an engine
environment

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2UN4APDMFAJEWXKAIEKREIFERH2WHAS4/
#!/usr/bin/env python

import os.path
from sys import exit

from ovirtsdk4 import Connection, types

URI = 'https://your-fqdn/ovirt-engine/api'
USERNAME = 'admin@internal'
PASSWORD = 'your-pass'
CERTPATH = '/etc/ssl/certs/your-cert-path.cert'

# Don't touch
MACOCTETS = ['00', '01', '02', '03', '04', '05', '06', '07', '08', '09', '0a', '0b', '0c', '0d', '0e', '0f',
 '10', '11', '12', '13', '14', '15', '16', '17', '18', '19', '1a', '1b', '1c', '1d', '1e', '1f',
 '20', '21', '22', '23', '24', '25', '26', '27', '28', '29', '2a', '2b', '2c', '2d', '2e', '2f',
 '30', '31', '32', '33', '34', '35', '36', '37', '38', '39', '3a', '3b', '3c', '3d', '3e', '3f',
 '40', '41', '42', '43', '44', '45', '46', '47', '48', '49', '4a', '4b', '4c', '4d', '4e', '4f',
 '50', '51', '52', '53', '54', '55', '56', '57', '58', '59', '5a', '5b', '5c', '5d', '5e', '5f',
 '60', '61', '62', '63', '64', '65', '66', '67', '68', '69', '6a', '6b', '6c', '6d', '6e', '6f',
 '70', '71', '72', '73', '74', '75', '76', '77', '78', '79', '7a', '7b', '7c', '7d', '7e', '7f',
 '80', '81', '82', '83', '84', '85', '86', '87', '88', '89', '8a', '8b', '8c', '8d', '8e', '8f',
 '90', '91', '92', '93', '94', '95', '96', '97', '98', '99', '9a', '9b', '9c', '9d', '9e', '9f',
 'a0', 'a1', 'a2', 'a3', 'a4', 'a5', 'a6', 'a7', 'a8', 'a9', 'aa', 'ab', 'ac', 'ad', 'ae', 'af',
 'b0', 'b1', 'b2', 'b3', 'b4', 'b5', 'b6', 'b7', 'b8', 'b9', 'ba', 'bb', 'bc', 'bd', 'be', 'bf',
 'c0', 'c1', 'c2', 'c3', 'c4', 'c5', 'c6', 'c7', 'c8', 'c9', 'ca', 'cb', 'cc', 'cd', 'ce', 'cf',
 'd0', 'd1', 'd2', 'd3', 'd4', 'd5', 'd6', 'd7', 'd8', 'd9', 'da', 'db', 'dc', 'dd', 'de', 'df',
 'e0', 'e1', 'e2', 'e3', 'e4', 'e5', 'e6', 'e7', 'e8', 'e9', 'ea', 'eb', 'ec', 'ed', 'ee', 'ef',
 'f0', 'f1', 'f2', 'f3', 'f4', 'f5', 'f6', 'f7', 'f8', 'f9', 'fa', 'fb', 'fc', 'fd', 'fe', 'ff']


# Replace this with your active MAC address pools, WITHOUT the last octet
MACPOOLS = ['00:11:22:33:44', '00:55:66:77:88']

conn = Connection(
   url=URI,
   username=USERNAME,
   password=PASSWORD,
   ca_file=CERTPATH
)

if not conn.test(raise_exception=False):
print("ERROR: Can't connect (credentials?)")
exit(1)

vms_macs = {}

sys_serv = conn.system_service()
vms_serv = sys_serv.vms_service()

macs = []
for vm in vms_serv.list():
nics = conn.follow_link(vm.nics)
for nic in nics:
if nic.mac.address in vms_macs:
vms_macs[nic.mac.address].append(vm.name)
else:
vms_macs[nic.mac.address] = [vm.name]
macs.append(nic.mac.address)

def find_unused_mac():
global MACOCTETS, MACPOOLS, macs

for pool in MACPOOLS:
for octet in MACOCTETS:
mac = "%s:%s" % (pool, octet)
if mac not in macs:
macs.append(mac)
return mac
return None

have_dupes = False
for mac, vms in vms_macs.items():
if len(vms) > 1:
have_dupes = True
print("Dupe 

[ovirt-users] Re: Correct way to search VM by mac

[Gianluca Cecchi]

Sorry, incomplete message sent...
today I had a problem about conflicting MAC between two different VMs.
The source of the problem was a VM created on env1 managed by engine1 and
then transferred some weeks ago to env2 managed by engine2.
The two envs share some networks and during migration I didn't change the
mac of the vnic after completing it.
So the mac was left free from env1 and used in env2.
The default mac pools are different ones between env1 and env2.
So today in env1 I created a new vm on the same vlan as the previous one
and oVirt assigned the previous one mac, now freed on it, originating big
problems...
I found an article (https://access.redhat.com/solutions/695383) to search
in the engine web admin by mac, but it was for version 3.2 and it seems it
doesn't work in 4.4.10.
In VMs page I search filling the query with

mac = my_mac
or

Vms: mac = my_mac

but it keeps thinking with 3 squares blinking in the page. I have not
so many VMs to justify time elapsing... (less then 50)

Can I search for mac? How?

Thanks,

Gianluca



On Fri, Mar 25, 2022 at 3:27 PM Gianluca Cecchi 
wrote:

> Hello,
> today I had a problem about conflicting MAC.
> The source of problem was a VM transferred from an engine environment
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2UN4APDMFAJEWXKAIEKREIFERH2WHAS4/

[ovirt-users] Correct way to search VM by mac

[Gianluca Cecchi]

Hello,
today I had a problem about conflicting MAC.
The source of problem was a VM transferred from an engine environment
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2KRK4V62C5MDPVX4TXMJNO4J6AYPZHY5/

[ovirt-users] Re: Unable to start VMs after upgrade from 4.4.9 to 4.4.10

[Christoph Timm]

Hello again,

I'm quite sure that this is a bug

Using up to date CentOS Stream 8 with vdsm-4.40.100.2-1.el8 and oVirt 
4.4.10.
The VM is getting into unresponsive state during the power down if port 
mirror is activated in the vNIC profile of the VM.
The supervdsm.log on the host is showing the following error during 
power off.


This was working in < 4.4.10. So I would say that this is a bug. Where 
should I report this?


MainProcess|libvirt/events::DEBUG::2022-03-25 
08:44:39,670::supervdsm_server::95::SuperVdsm.ServerCallback::(wrapper) 
call unsetPortMirroring with ('probe_traffic', 'vnet2') {}
MainProcess|libvirt/events::DEBUG::2022-03-25 
08:44:39,670::cmdutils::130::root::(exec_cmd) /sbin/tc filter show dev 
probe_traffic parent : (cwd None)
MainProcess|libvirt/events::DEBUG::2022-03-25 
08:44:39,678::cmdutils::138::root::(exec_cmd) SUCCESS:  = b'';  = 0
MainProcess|libvirt/events::ERROR::2022-03-25 
08:44:39,678::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper) 
Error in unsetPortMirroring

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", 
line 97, in wrapper

    res = func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 104, in unsetPortMirroring

    acts = _delTarget(network, QDISC_INGRESS, target)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 50, in _delTarget

    fs = list(filters(network, parent))
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 174, in filters

    for filt in _filters(dev, parent=parent, out=out):
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 199, in _iterate

    yield module.parse(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 99, in parse

    data[data['kind']] = _filter_cls_parser(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 119, in _parse_u32

    _parser.consume(tokens, '???')
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/_parser.py", 
line 36, in consume

    raise TCParseError('Found %s, expected %s' % (found, expected))
vdsm.network.tc._parser.TCParseError: Found not_in_hw, expected ('???',)


Best regards
Christoph


Am 25.03.22 um 07:42 schrieb Christoph Timm:

Good morning,

please note that I got a bit further with my investigation.

It might be a bug in the VDSM as I see the following while powering 
down the problematic VM:


MainProcess|libvirt/events::ERROR::2022-03-24 
20:43:48,740::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper) 
Error in unsetPortMirroring

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", 
line 97, in wrapper

    res = func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 104, in unsetPortMirroring

    acts = _delTarget(network, QDISC_INGRESS, target)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 50, in _delTarget

    fs = list(filters(network, parent))
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 174, in filters

    for filt in _filters(dev, parent=parent, out=out):
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 199, in _iterate

    yield module.parse(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 99, in parse

    data[data['kind']] = _filter_cls_parser(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 119, in _parse_u32

    _parser.consume(tokens, '???')
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/_parser.py", 
line 36, in consume

    raise TCParseError('Found %s, expected %s' % (found, expected))
vdsm.network.tc._parser.TCParseError: Found not_in_hw, expected ('???',)

I already manage to find out that this is related to the specific vNIC 
configuration which is using the port mirror flag.


My plan is remove and add the port mirror from the vNIC as the first 
step. After that I will recreate the vNIC.


Any recommendations?

Best regards
Christoph

Am 24.03.22 um 12:31 schrieb Christoph Timm:

Hi List,

I receive the following error while starting some of our VMs after 
the upgrade to 4.4.10.


VM v4-probe is down with error. Exit message: internal error: process 
exited while connecting to monitor: 2022-03-24T11:27:23.098838Z 
qemu-kvm: -blockdev 
{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":"libvirt-3-format"}: 
Failed to get "write" lock
Is another process using the image 
[/rhev/data-center/mnt/lxskinner:_exports_skinner__2tb__1/28da0c79-b6f1-4740-bd24-e7bafcb62c75/images/90b28e7e-98a3-4f80-a136-c5a52c4a3e05/c1450651-b1e5-47fd-906b-8ebd62ace8a4]?.


The example disk is located on a NFS share.

Any idea how to tell oVirt that there is no other process 

[ovirt-users] Re: No bootable device

[nicolas]

Hi _isi_,

I already tried with all chipset/firmwares available. Still I get the 
same result, it cannot boot with that disk. Not sure what the problem 
actually is, as I said, I'm pretty sure the disk is bootable under 
VirtualBox.


Thanks.

El 2022-03-23 14:50, uli.i...@elkb.de escribió:

Hi,

I guess you should check Chipset / Firmware Type Setting of VM. If it
is UEFI or BIOS boot.

_isi_
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/FUMIPVESOS4LVHQ24R4IAAE3S6L7NH5Z/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/KGJWLIC7S3LTRPHN2VNGVVFL5REBCQFX/

[ovirt-users] Re: No bootable device

[nicolas]

Hi Abe,

Yes, it was set as bootable. I tried your approach, however I get the 
same results; converted the disk with qemu-img from vmdk to qcow2, tried 
any disk driver (SATA, VirtIO, VirtIO-SCSI) and also tried all 
chipset/firmwares available. Still I get the same result, it cannot boot 
with that disk.


Thanks.

El 2022-03-24 18:33, Abe E escribió:
Is it set as bootable? I have seen some QCOWs not be read correctly by 
ovirt.

In that case I would take an OVA file and convert it manually to QCOW
using the CLI, sometimes the QCOW works only with IDE from what I have
seen.

My way is somewhat long but usually works for me:
Upload to Disk page in GUI and attach to a premade VM -- If it fails 
use CLI:

CLI:
tar -xvf .ova
it will extract to .vmdk files
OR if you have a VMDK already

qemu-img convert -disk001.vmdk .qcow2 -O qcow2

Once completed, you should verify that the file is successfully a QEMU
QCOW2 Image.
file .qcow2

You can then download over winscp and upload to the GUI Disks page and
attach to a VM -- Sometimes if you have errors on boot you need to
choose a different CPU or set HDD to IDE or virtIO-Sata.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/GZ526EVNG5Q4TU75BS6ICNBIF3JL2VWR/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ABRBPC3OIRJ2WFER62F7VJKU2DZ75O26/

[ovirt-users] Re: Big problem on Ovirt 4.4

[Michal Skrivanek]

> On 24. 3. 2022, at 18:38, Nenhum de Nos via Users  wrote:
> 
> Hi,
> 
> I run a small test node and engine of ovirt since 4.3. Its in my home, but I 
> kind messed up and now I can't use or reinstall it without loosing all my 
> vm's data (at least this is the point my knowledge of ovirt is).
> 
> I got the issue where I could not update yum since CentOS 8 mirrors would not 
> answer. And I tried some solution I found in the list archives, and got 
> really bad here.

Hi,
well, CentOS 8 doesn't exist anymore, you would have to switch to 8-stream

> 
> I had a power outage last Saturday and my node got to nonresponsive. No 
> matter what I did, never left this state. Kept complaining about the CPU 
> Type, I run it on Ryzen 3400G (used to run on Intel i5, also desktop CPU, and 
> never had an issue, when I changed to Ryzen, every outage from power here is 
> a problem), and the node wouldn't come back. So I tried to upgrade my cluster 
> to 4.4 level (was 4.3) and it didn't help. So I tried to get back to 4.3 and 
> a message said just empty clusters could do that. I then removed my ryzen 
> node from it and it got back to 4.3.
> But now I could not install the node. I tried changing its name, no good. 
> Failed on how to get packages from GLuster8 repo.
> That is where my story got sad. I tried to update my repo using the steps in 
> the last post from 
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D3FEXQ5KOLN3SST3MPGIHSCEF52IBTKY/
>  
> .
>  Bad idea, and another one was I didn't do a backup of the engine.
> 
> Now my engine won't start, the backup won't run:
> 
> engine-backup --mode=backup --file=/root/backup_deuruim 
> --log=/root/backup_deuruim.log
> Start of engine-backup with mode 'backup'
> scope: all
> archive file: /root/backup_deuruim
> log file: /root/backup_deuruim.log
> Backing up:
> Notifying engine
> Notifying engine
> FATAL: Failed notifying engine
> 
> pg_dump: error: Dumping the contents of table "audit_log" failed: 
> PQgetResult() failed.
> pg_dump: error: Error message from server: ERROR:  MultiXactId 1076887572 has 
> not been created yet -- apparent wraparound
> pg_dump: error: The command was: COPY public.audit_log (audit_log_id, 
> user_id, user_name, vm_id, vm_name, vm_template_id, vm_template_name, vds_id, 
> vds_name, log_time, log_type_name, log_type, severity, message, processed, 
> storage_pool_id, storage_pool_name, storage_domain_id, storage_domain_name, 
> cluster_id, cluster_name, correlation_id, job_id, quota_id, quota_name, 
> gluster_volume_id, gluster_volume_name, origin, custom_event_id, 
> event_flood_in_sec, custom_data, deleted, call_stack, brick_id, brick_path, 
> custom_id) TO stdout;
> 2022-03-24 13:16:10 3461: FATAL: Database engine backup failed
> 
> the Admin portal won't work, and I get a message on the login screen from 
> engine saying I have a web console at port 9090. I don't get it.

I don't get it either, it all sounds too confusing.

> 
> As my last resort I am here, trying at least to know a way I could backup it 
> and install the engine elsewhere. All vm data is fine, but as the names are 
> cryptographic, import them would have me guessing things, right?
> 
> The number of VM's is low, 6 or 7, so if there is a way to do it manually, I 
> would try. Installing it again would be my nightmare here.

with just a few VMs it's indeed best to just reinstall from scratch and 
importing the storage domain back. You would only be missing the other non-VM 
configuration in oVirt that you have to do again, but the VMs should have the 
right name and all after import. Assuming you still have the storage domain 
somewhere safe.

Thanks,
michal
> 
> thanks,
> 
> matheus
> 
> ps: if needed, I can provide more info.
> 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/PVFGIOV6KKG3BPAJMRFNXG2W6QYYFDK4/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/KW6NQOM2JOBFXKK236H3K5UUR7ZFF24S/

[ovirt-users] Re: dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.

[Martin Perina]

Hi,

oVirt 4.4 requires ansible 2.9, it cannot work with any newer version of
ansible because of deep changes in ansible between ansible 2.9 and 2.10.

We are preparing upgrade to ansible-core-2.12 in oVirt 4.5, the process is
tracked by https://bugzilla.redhat.com/show_bug.cgi?id=2065052

So if you need to perform package updates manually before oVirt 4.5 is
released, then please use:

dnf update -x ansible -x ansible-core

Regards,
Martin


On Fri, Mar 25, 2022 at 7:47 AM Christoph Timm  wrote:

> Good morning,
>
> please note that I have performed some tests and I'm quite sure that
> oVirt is not compatible with ansible-core-2.12.
> I run into issues with hosts installation and the check for updates
> results into a Null pointer exception.
>
> So I have reverted back to ansible-2.9 which is also provided from the
> oVirt repositories.
> Guess the OS (CentOS Stream 8) is providing already a newer version
> which is not working for oVirt.
>
> Best regards
> Christoph
>
> Am 24.03.22 um 03:43 schrieb Sketch:
> > Just for the record, I fixed this with:
> >
> > # rpm -e ansible --nodeps
> > # dnf install ansible
> >
> > Now dnf update works as expected without errors or removing any packages.
> >
> > I haven't encounted this issue on my hosts because they are running
> > Rocky, not Stream.
> >
> > On Thu, 24 Mar 2022, Sketch wrote:
> >
> >> Just a warning, adding --allowerasing on my engine causes
> >> ovirt-engine and a bunch of other ovirt-* packages to be removed.  So
> >> make sure you check the yum output carefully before running the command.
> >>
> >> On Wed, 23 Mar 2022, Jillian Morgan wrote:
> >>
> >>>  I had to add --allowerasing to my dnf update command to get it to go
> >>>  through
> >>>  (which it did, cleanly removing the old ansible package and
> >>> replacing it
> >>>  with ansible-core). I suspect that the new ansible-core package
> doesn't
> >>>  properly obsolete the older ansible package. Trying to Upgrade
> >>> hosts from
> >>>  the Admin portal would fail because of this requirement.
> >>>
> >>>  As a side note, my systems hadn't been updated since before the
> mirrors
> >>>  for
> >>>  Centos 8 packages went away, so all updates failed due to failure
> >>>  downloading mirrorlists. I had to do this first, to get the updated
> >>> repo
> >>>  files pointing to Centos 8 Stream packages:
> >>>
> >>>  dnf update --disablerepo ovirt-4.4-* ovirt-realease44
> >>>
> >>>  --
> >>>  Jillian Morgan (she/her) ️‍⚧️
> >>>  Systems & Networking Specialist
> >>>  Primordial Software Group & I.T. Consultancy
> >>>  https://www.primordial.ca
> >>>
> >>>
> >>>  On Wed, Mar 23, 2022 at 3:53 PM Christoph Timm 
> wrote:
> >>>Hi List,
> >>>
> >>>I see the same issue on my CentOS Stream 8 hosts and engine.
> >>>I'm running 4.4.10.
> >>>My systems are all migrated from CentOS 8 to CentOS Stream 8.
> >>>Might this be caused by that?
> >>>
> >>>Best regards
> >>>Christoph
> >>>
> >>>
> >>>Am 20.02.22 um 19:58 schrieb Gilboa Davara:
> >>>I managed to upgrade a couple of 8-streams based clusters
> >>>w/ --nobest, and thus far, I've yet to experience any
> >>>issues (knocks wood feaviously).
> >>>
> >>>  - Gilboa
> >>>
> >>>  On Sat, Feb 19, 2022 at 3:21 PM Daniel McCoshen
> >>>   wrote:
> >>>Hey all,
> >>>I'm running ovirt 4.4 in production
> >>>(4.4.5-11-1.el8), and I'm attempting to update the
> >>>OS on my hosts. The hosts are all centos 8 stream,
> >>>and dnf update is failing on all of them with the
> >>>following output:
> >>>
> >>>[root@ovirthost ~]# dnf update
> >>>Last metadata expiration check: 1:36:32 ago on Thu
> >>>17 Feb 2022 12:01:25 PM CST.
> >>>Error:
> >>> Problem: package
> >>>cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires
> >>>ansible, but none of the providers can be installed
> >>>  - package ansible-2.9.27-2.el8.noarch conflicts
> >>>with ansible-core > 2.11.0 provided by
> >>>ansible-core-2.12.2-2.el8.x86_64
> >>>  - package ansible-core-2.12.2-2.el8.x86_64
> >>>obsoletes ansible < 2.10.0 provided by
> >>>ansible-2.9.27-2.el8.noarch
> >>>  - package ansible-core-2.12.2-2.el8.x86_64
> >>>obsoletes ansible < 2.10.0 provided by
> >>>ansible-2.9.27-1.el8.noarch
> >>>  - package ansible-core-2.12.2-2.el8.x86_64
> >>>obsoletes ansible < 2.10.0 provided by
> >>>ansible-2.9.17-1.el8.noarch
> >>>  - package ansible-core-2.12.2-2.el8.x86_64
> >>>obsoletes ansible < 2.10.0 provided by
> >>>ansible-2.9.18-2.el8.noarch
> >>>  - package ansible-core-2.12.2-2.el8.x86_64
> >>>obsoletes ansible < 2.10.0 provided by
> >>>ansible-2.9.20-2.el8.noarch
> >>>  - package ansible-core-2.12.2-2.el8.x86_64
> >>>obsoletes ansible < 2.10.0 provided by
> >>>

[ovirt-users] Re: Zanata user request

[Temuri Doghonadze]

Hello,
Got it, thank you.
All's ok, I'm in. Only thing I might also ask, is if you got any access to
person who is maintaining virt-manager, could you ask them to fix
translation? (at https://translate.fedoraproject.org/).

Thanks for provided help, will try my best.
BR, Temuri

On Tue, Mar 22, 2022 at 11:49 AM Sharon Gratch  wrote:

>
> Hi Temuri,
>
> I activated your account on Zanata (you already had one) and added you to
> the Georgian translation group.
> I'll send you the account details in a separate mail.
>
> Thanks for willing to help with translations!
> Sharon
>
> On Mon, Mar 21, 2022 at 3:32 PM Sandro Bonazzola 
> wrote:
>
>> +Sharon Gratch  +Scott Dickerson
>>  +Michal Skrivanek  can you
>> help here?
>>
>> Il giorno lun 21 mar 2022 alle ore 11:23 Temuri Doghonadze <
>> temuri.doghona...@gmail.com> ha scritto:
>>
>>> Hello,
>>> My name is Temuri and I'd like to ask for account for Zanata to help
>>> with translation of ovirt to Georgian.
>>>
>>> I've done translation of zoiper, FreeCAD, part of gitlab, protonmail,
>>> parts of gnome and KDE, etc etc etc.
>>> In case of questions feel free to ask.
>>> BR, Temuri
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@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/RYKJ2ZFIOYA66XY3PRPXHF5Y5ZDSTKVG/
>>>
>>
>>
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> 
>>
>> *Red Hat respects your work life balance. Therefore there is no need to
>> answer this email out of your office hours.*
>>
>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/N55BSEXLNV26HEWKJTQSUCYN4PPA3P6W/

[ovirt-users] Re: Zanata user request

[Temuri Doghonadze]

Hello again,
Translation of 2 modules you gave access me to is completed.
But I've noticed 2 additional modules I didn't have access to.
Could you please tell me if they're not neccessary?
Also, virt-manager translation is still unavailable.

On Tue, Mar 22, 2022 at 1:02 PM Temuri Doghonadze <
temuri.doghona...@gmail.com> wrote:

> Hello,
> Got it, thank you.
> All's ok, I'm in. Only thing I might also ask, is if you got any access to
> person who is maintaining virt-manager, could you ask them to fix
> translation? (at https://translate.fedoraproject.org/).
>
> Thanks for provided help, will try my best.
> BR, Temuri
>
> On Tue, Mar 22, 2022 at 11:49 AM Sharon Gratch  wrote:
>
>>
>> Hi Temuri,
>>
>> I activated your account on Zanata (you already had one) and added you
>> to the Georgian translation group.
>> I'll send you the account details in a separate mail.
>>
>> Thanks for willing to help with translations!
>> Sharon
>>
>> On Mon, Mar 21, 2022 at 3:32 PM Sandro Bonazzola 
>> wrote:
>>
>>> +Sharon Gratch  +Scott Dickerson
>>>  +Michal Skrivanek  can you
>>> help here?
>>>
>>> Il giorno lun 21 mar 2022 alle ore 11:23 Temuri Doghonadze <
>>> temuri.doghona...@gmail.com> ha scritto:
>>>
 Hello,
 My name is Temuri and I'd like to ask for account for Zanata to help
 with translation of ovirt to Georgian.

 I've done translation of zoiper, FreeCAD, part of gitlab, protonmail,
 parts of gnome and KDE, etc etc etc.
 In case of questions feel free to ask.
 BR, Temuri
 ___
 Users mailing list -- users@ovirt.org
 To unsubscribe send an email to users-le...@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/RYKJ2ZFIOYA66XY3PRPXHF5Y5ZDSTKVG/

>>>
>>>
>>> --
>>>
>>> Sandro Bonazzola
>>>
>>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>>
>>> Red Hat EMEA 
>>>
>>> sbona...@redhat.com
>>> 
>>>
>>> *Red Hat respects your work life balance. Therefore there is no need to
>>> answer this email out of your office hours.*
>>>
>>>
>>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DLP6WWYIZ64MLAGCBQNYF4QO6RZ5RVIV/

[ovirt-users] Re: No bootable device

[uli . iske]

Hi,

I guess you should check Chipset / Firmware Type Setting of VM. If it is UEFI 
or BIOS boot.

_isi_
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/FUMIPVESOS4LVHQ24R4IAAE3S6L7NH5Z/

[ovirt-users] Commvault Backup fails to attach disk snapshots

[martin . kaufmann]

Hello all,

since we updated our Commvault to the version "service pack 26 hotfix 16", 
random VM backups are failing to attach disk snapshots to the backup proxy VM.
We are running oVirt Version 4.4.10.6-1.el8 and the hypervisor is oVirt Node 
4.4.9.

These are the logs from the managerVM:

##
2022-03-24 11:13:59,390+01 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default 
task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Disk hot-plug: 
  

  
  

  
  
  
  
  e3c292e0-dfd2-4cd5-a27f-f87308a18e64

  
  http://ovirt.org/vm/1.0;>

  
98d981da-d010-11ea-9e4d-00163e1be424

8b524896-902c-445f-a33a-65335cb75eff
transient

e3c292e0-dfd2-4cd5-a27f-f87308a18e64

6da85fb1-ff4b-4665-ade3-0f32f83250bc
  

  


2022-03-24 11:13:59,898+01 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default 
task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Failed in 'HotPlugDiskVDS' 
method
2022-03-24 11:13:59,898+01 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default 
task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command 
'org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand' return value 
'StatusOnlyReturn [status=Status [code=45, message=Requested operation is not 
valid: Domain already contains a disk with that address]]'
2022-03-24 11:13:59,898+01 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default 
task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] HostName = hypervisor1.domain
2022-03-24 11:13:59,898+01 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default 
task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command 
'HotPlugDiskVDSCommand(HostName = hypervisor1.domain, 
HotPlugDiskVDSParameters:{hostId='c2fd81cd-8fc8-410e-8333-a0a36b87ab2b', 
vmId='890c105d-333b-435e-8d8b-0b889f4f9c14', 
diskId='e3c292e0-dfd2-4cd5-a27f-f87308a18e64'})' execution failed: 
VDSGenericException: VDSErrorException: Failed to HotPlugDiskVDS, error = 
Requested operation is not valid: Domain already contains a disk with that 
address, code = 45
2022-03-24 11:13:59,898+01 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (default 
task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] FINISH, 
HotPlugDiskVDSCommand, return: , log id: 536a4414
2022-03-24 11:13:59,898+01 ERROR 
[org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] (default 
task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command 
'org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand' failed: 
EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
VDSGenericException: VDSErrorException: Failed to HotPlugDiskVDS, error = 
Requested operation is not valid: Domain already contains a disk with that 
address, code = 45 (Failed with error FailedToPlugDisk and code 45)
2022-03-24 11:13:59,899+01 INFO  [org.ovirt.engine.core.bll.CommandCompensator] 
(default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command 
[id=87712152-4660-40ca-b292-397796c735d5]: Compensating NEW_ENTITY_ID of 
org.ovirt.engine.core.common.businessentities.storage.DiskVmElement; snapshot: 
VmDeviceId:{deviceId='e3c292e0-dfd2-4cd5-a27f-f87308a18e64', 
vmId='890c105d-333b-435e-8d8b-0b889f4f9c14'}.
2022-03-24 11:13:59,900+01 INFO  [org.ovirt.engine.core.bll.CommandCompensator] 
(default task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Command 
[id=87712152-4660-40ca-b292-397796c735d5]: Compensating NEW_ENTITY_ID of 
org.ovirt.engine.core.common.businessentities.VmDevice; snapshot: 
VmDeviceId:{deviceId='e3c292e0-dfd2-4cd5-a27f-f87308a18e64', 
vmId='890c105d-333b-435e-8d8b-0b889f4f9c14'}.
2022-03-24 11:13:59,910+01 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default 
task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] EVENT_ID: 
USER_FAILED_ATTACH_DISK_TO_VM(2,017), Failed to attach Disk VM1_Disk1 to VM 
backupproxyVM (User: backupagent@internal-authz).
2022-03-24 11:13:59,910+01 INFO  
[org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] (default 
task-1578) [0aeb5794-5c2e-44c6-8fc5-34ec0e81d16b] Lock freed to object 
'EngineLock:{exclusiveLocks='[e3c292e0-dfd2-4cd5-a27f-f87308a18e64=DISK]', 
sharedLocks=''}'
2022-03-24 11:13:59,910+01 ERROR 
[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default 
task-1578) [] Operation Failed: [Failed to hot-plug disk]
###

Here are the logs from the hypervisor:

##
2022-03-24 11:13:59,712+0100 INFO  (jsonrpc/4) [virt.vm] 
(vmId='890c105d-333b-435e-8d8b-0b889f4f9c14') Hotplug disk xml: 






e3c292e0-dfd2-4cd5-a27f-f87308a18e64



 (vm:3851)
2022-03-24 11:13:59,721+0100 ERROR (jsonrpc/4) [virt.vm] 
(vmId='890c105d-333b-435e-8d8b-0b889f4f9c14') Hotplug failed (vm:3859)
Traceback (most recent call last):
  File 

[ovirt-users] Big problem on Ovirt 4.4

[Nenhum de Nos via Users]

Hi,
I run a small test node and engine of ovirt since 4.3. Its in my home, but I 
kind messed up and now I can't use or reinstall it without loosing all my vm's 
data (at least this is the point my knowledge of ovirt is).
I got the issue where I could not update yum since CentOS 8 mirrors would not 
answer. And I tried some solution I found in the list archives, and got really 
bad here.
I had a power outage last Saturday and my node got to nonresponsive. No matter 
what I did, never left this state. Kept complaining about the CPU Type, I run 
it on Ryzen 3400G (used to run on Intel i5, also desktop CPU, and never had an 
issue, when I changed to Ryzen, every outage from power here is a problem), and 
the node wouldn't come back. So I tried to upgrade my cluster to 4.4 level (was 
4.3) and it didn't help. So I tried to get back to 4.3 and a message said just 
empty clusters could do that. I then removed my ryzen node from it and it got 
back to 4.3.But now I could not install the node. I tried changing its name, no 
good. Failed on how to get packages from GLuster8 repo.That is where my story 
got sad. I tried to update my repo using the steps in the last post from 
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D3FEXQ5KOLN3SST3MPGIHSCEF52IBTKY/.
 Bad idea, and another one was I didn't do a backup of the engine.
Now my engine won't start, the backup won't run:
engine-backup --mode=backup --file=/root/backup_deuruim 
--log=/root/backup_deuruim.logStart of engine-backup with mode 'backup'scope: 
allarchive file: /root/backup_deuruimlog file: /root/backup_deuruim.logBacking 
up:Notifying engineNotifying engineFATAL: Failed notifying engine
pg_dump: error: Dumping the contents of table "audit_log" failed: PQgetResult() 
failed.pg_dump: error: Error message from server: ERROR:  MultiXactId 
1076887572 has not been created yet -- apparent wraparoundpg_dump: error: The 
command was: COPY public.audit_log (audit_log_id, user_id, user_name, vm_id, 
vm_name, vm_template_id, vm_template_name, vds_id, vds_name, log_time, 
log_type_name, log_type, severity, message, processed, storage_pool_id, 
storage_pool_name, storage_domain_id, storage_domain_name, cluster_id, 
cluster_name, correlation_id, job_id, quota_id, quota_name, gluster_volume_id, 
gluster_volume_name, origin, custom_event_id, event_flood_in_sec, custom_data, 
deleted, call_stack, brick_id, brick_path, custom_id) TO stdout;2022-03-24 
13:16:10 3461: FATAL: Database engine backup failed
the Admin portal won't work, and I get a message on the login screen from 
engine saying I have a web console at port 9090. I don't get it.
As my last resort I am here, trying at least to know a way I could backup it 
and install the engine elsewhere. All vm data is fine, but as the names are 
cryptographic, import them would have me guessing things, right?
The number of VM's is low, 6 or 7, so if there is a way to do it manually, I 
would try. Installing it again would be my nightmare here.
thanks,
matheus
ps: if needed, I can provide more info.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/PVFGIOV6KKG3BPAJMRFNXG2W6QYYFDK4/

[ovirt-users] Re: dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.

[Christoph Timm]

Good morning,

please note that I have performed some tests and I'm quite sure that 
oVirt is not compatible with ansible-core-2.12.
I run into issues with hosts installation and the check for updates 
results into a Null pointer exception.


So I have reverted back to ansible-2.9 which is also provided from the 
oVirt repositories.
Guess the OS (CentOS Stream 8) is providing already a newer version 
which is not working for oVirt.


Best regards
Christoph

Am 24.03.22 um 03:43 schrieb Sketch:

Just for the record, I fixed this with:

# rpm -e ansible --nodeps
# dnf install ansible

Now dnf update works as expected without errors or removing any packages.

I haven't encounted this issue on my hosts because they are running 
Rocky, not Stream.


On Thu, 24 Mar 2022, Sketch wrote:

Just a warning, adding --allowerasing on my engine causes 
ovirt-engine and a bunch of other ovirt-* packages to be removed.  So 
make sure you check the yum output carefully before running the command.


On Wed, 23 Mar 2022, Jillian Morgan wrote:


 I had to add --allowerasing to my dnf update command to get it to go
 through
 (which it did, cleanly removing the old ansible package and 
replacing it
 with ansible-core). I suspect that the new ansible-core package 
doesn't
 properly obsolete the older ansible package. Trying to Upgrade 
hosts from

 the Admin portal would fail because of this requirement.

 As a side note, my systems hadn't been updated since before the 
mirrors

 for
 Centos 8 packages went away, so all updates failed due to failure
 downloading mirrorlists. I had to do this first, to get the updated 
repo

 files pointing to Centos 8 Stream packages:

 dnf update --disablerepo ovirt-4.4-* ovirt-realease44

 --
 Jillian Morgan (she/her) ️‍⚧️
 Systems & Networking Specialist
 Primordial Software Group & I.T. Consultancy
 https://www.primordial.ca


 On Wed, Mar 23, 2022 at 3:53 PM Christoph Timm  
wrote:

   Hi List,

   I see the same issue on my CentOS Stream 8 hosts and engine.
   I'm running 4.4.10.
   My systems are all migrated from CentOS 8 to CentOS Stream 8.
   Might this be caused by that?

   Best regards
   Christoph


   Am 20.02.22 um 19:58 schrieb Gilboa Davara:
   I managed to upgrade a couple of 8-streams based clusters
   w/ --nobest, and thus far, I've yet to experience any
   issues (knocks wood feaviously).

 - Gilboa

 On Sat, Feb 19, 2022 at 3:21 PM Daniel McCoshen
  wrote:
   Hey all,
   I'm running ovirt 4.4 in production
   (4.4.5-11-1.el8), and I'm attempting to update the
   OS on my hosts. The hosts are all centos 8 stream,
   and dnf update is failing on all of them with the
   following output:

   [root@ovirthost ~]# dnf update
   Last metadata expiration check: 1:36:32 ago on Thu
   17 Feb 2022 12:01:25 PM CST.
   Error:
    Problem: package
   cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires
   ansible, but none of the providers can be installed
     - package ansible-2.9.27-2.el8.noarch conflicts
   with ansible-core > 2.11.0 provided by
   ansible-core-2.12.2-2.el8.x86_64
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.27-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.27-1.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.17-1.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.18-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.20-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.21-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.23-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.24-2.el8.noarch
     - cannot install the best update candidate for
   package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
     - cannot install the best update candidate for
   package ansible-2.9.27-2.el8.noarch
     - package ansible-2.9.20-1.el8.noarch is filtered
   out by exclude filtering
     - package ansible-2.9.16-1.el8.noarch is filtered
   out by exclude filtering
     - package ansible-2.9.19-1.el8.noarch is filtered
   out by exclude filtering
     - package ansible-2.9.23-1.el8.noarch is filtered
   out by exclude filtering
   (try to add '--allowerasing' to command line to
   replace conflicting packages or '--skip-broken' to
   skip uninstallable packages or '--nobest' to use not
   only 

[ovirt-users] Re: dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.

[Christoph Timm]

Good morning,

please note that I have performed some tests and I'm quite sure that 
oVirt is not compatible with ansible-core-2.12.
I run into issues with hosts installation and the check for updates 
results into a Null pointer exception.


So I have reverted back to ansible-2.9 which is also provided from the 
oVirt repositories.
Guess the OS (CentOS Stream 8) is providing already a newer version 
which is not working for oVirt.


Best regards
Christoph

Am 24.03.22 um 03:43 schrieb Sketch:

Just for the record, I fixed this with:

# rpm -e ansible --nodeps
# dnf install ansible

Now dnf update works as expected without errors or removing any packages.

I haven't encounted this issue on my hosts because they are running 
Rocky, not Stream.


On Thu, 24 Mar 2022, Sketch wrote:

Just a warning, adding --allowerasing on my engine causes 
ovirt-engine and a bunch of other ovirt-* packages to be removed.  So 
make sure you check the yum output carefully before running the command.


On Wed, 23 Mar 2022, Jillian Morgan wrote:


 I had to add --allowerasing to my dnf update command to get it to go
 through
 (which it did, cleanly removing the old ansible package and 
replacing it

 with ansible-core). I suspect that the new ansible-core package doesn't
 properly obsolete the older ansible package. Trying to Upgrade 
hosts from

 the Admin portal would fail because of this requirement.

 As a side note, my systems hadn't been updated since before the mirrors
 for
 Centos 8 packages went away, so all updates failed due to failure
 downloading mirrorlists. I had to do this first, to get the updated 
repo

 files pointing to Centos 8 Stream packages:

 dnf update --disablerepo ovirt-4.4-* ovirt-realease44

 --
 Jillian Morgan (she/her) ️‍⚧️
 Systems & Networking Specialist
 Primordial Software Group & I.T. Consultancy
 https://www.primordial.ca


 On Wed, Mar 23, 2022 at 3:53 PM Christoph Timm  wrote:
   Hi List,

   I see the same issue on my CentOS Stream 8 hosts and engine.
   I'm running 4.4.10.
   My systems are all migrated from CentOS 8 to CentOS Stream 8.
   Might this be caused by that?

   Best regards
   Christoph


   Am 20.02.22 um 19:58 schrieb Gilboa Davara:
   I managed to upgrade a couple of 8-streams based clusters
   w/ --nobest, and thus far, I've yet to experience any
   issues (knocks wood feaviously).

 - Gilboa

 On Sat, Feb 19, 2022 at 3:21 PM Daniel McCoshen
  wrote:
   Hey all,
   I'm running ovirt 4.4 in production
   (4.4.5-11-1.el8), and I'm attempting to update the
   OS on my hosts. The hosts are all centos 8 stream,
   and dnf update is failing on all of them with the
   following output:

   [root@ovirthost ~]# dnf update
   Last metadata expiration check: 1:36:32 ago on Thu
   17 Feb 2022 12:01:25 PM CST.
   Error:
    Problem: package
   cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires
   ansible, but none of the providers can be installed
     - package ansible-2.9.27-2.el8.noarch conflicts
   with ansible-core > 2.11.0 provided by
   ansible-core-2.12.2-2.el8.x86_64
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.27-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.27-1.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.17-1.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.18-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.20-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.21-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.23-2.el8.noarch
     - package ansible-core-2.12.2-2.el8.x86_64
   obsoletes ansible < 2.10.0 provided by
   ansible-2.9.24-2.el8.noarch
     - cannot install the best update candidate for
   package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
     - cannot install the best update candidate for
   package ansible-2.9.27-2.el8.noarch
     - package ansible-2.9.20-1.el8.noarch is filtered
   out by exclude filtering
     - package ansible-2.9.16-1.el8.noarch is filtered
   out by exclude filtering
     - package ansible-2.9.19-1.el8.noarch is filtered
   out by exclude filtering
     - package ansible-2.9.23-1.el8.noarch is filtered
   out by exclude filtering
   (try to add '--allowerasing' to command line to
   replace conflicting packages or '--skip-broken' to
   skip uninstallable packages or '--nobest' to use not
   only best 

[ovirt-users] Re: Unable to start VMs after upgrade from 4.4.9 to 4.4.10

[Christoph Timm]

Good morning,

please note that I got a bit further with my investigation.

It might be a bug in the VDSM as I see the following while powering down 
the problematic VM:


MainProcess|libvirt/events::ERROR::2022-03-24 
20:43:48,740::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper) 
Error in unsetPortMirroring

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", 
line 97, in wrapper

    res = func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 104, in unsetPortMirroring

    acts = _delTarget(network, QDISC_INGRESS, target)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 50, in _delTarget

    fs = list(filters(network, parent))
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 174, in filters

    for filt in _filters(dev, parent=parent, out=out):
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 199, in _iterate

    yield module.parse(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 99, in parse

    data[data['kind']] = _filter_cls_parser(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 119, in _parse_u32

    _parser.consume(tokens, '???')
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/_parser.py", 
line 36, in consume

    raise TCParseError('Found %s, expected %s' % (found, expected))
vdsm.network.tc._parser.TCParseError: Found not_in_hw, expected ('???',)

I already manage to find out that this is related to the specific vNIC 
configuration which is using the port mirror flag.


My plan is remove and add the port mirror from the vNIC as the first 
step. After that I will recreate the vNIC.


Any recommendations?

Best regards
Christoph

Am 24.03.22 um 12:31 schrieb Christoph Timm:

Hi List,

I receive the following error while starting some of our VMs after the 
upgrade to 4.4.10.


VM v4-probe is down with error. Exit message: internal error: process 
exited while connecting to monitor: 2022-03-24T11:27:23.098838Z 
qemu-kvm: -blockdev 
{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":"libvirt-3-format"}: 
Failed to get "write" lock
Is another process using the image 
[/rhev/data-center/mnt/lxskinner:_exports_skinner__2tb__1/28da0c79-b6f1-4740-bd24-e7bafcb62c75/images/90b28e7e-98a3-4f80-a136-c5a52c4a3e05/c1450651-b1e5-47fd-906b-8ebd62ace8a4]?.


The example disk is located on a NFS share.

Any idea how to tell oVirt that there is no other process using this 
disk?


Best regards and thx
Christoph
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SIDIS42UA5DUTS3GF5W7XBQFCNVMN3YG/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3DD4UJSQXJENYYYP762Q5Z3TTHE7GKBH/