[ovirt-users] Re: [SOLVED] Re: Re: How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment?
Hi Derek, Many thanks for your email, it has helped me a lot for troubleshooting my certificates issues on my homelab. I don't know if you solved the san issue, but I have made it work using --san=DNS:host.na.me I found this somewhere although I can't remember where (probably in between my hundreds tabs). Thanks again, Kind regards. Timothe 'NokiDev' Van Deputte ___ 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/V3HX7Q2TAORTLZZGNCJBKA3CDQTSL5KK/
[ovirt-users] Re: Unable to start VMs after upgrade from 4.4.9 to 4.4.10
Hi Ales,
thank you so much for the feedback and for the possible workaround.
For the moment I have tweaked the bridge to perform the port mirror.
Best regards
Christoph
Am 28.03.22 um 07:08 schrieb Ales Musil:
Hi,
this is already fixed in oVirt 4.5 [0]. Possible workaround might be
to downgrade the iproute-tc package below version 5.15.0-3.
Regards,
Ales
[0]
https://github.com/oVirt/vdsm/commit/503a98139d65daed856d97a8c6d7f875bcbe42df
On Fri, Mar 25, 2022 at 1:15 PM Christoph Timm wrote:
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
[ovirt-users] Re: Unable to start VMs after upgrade from 4.4.9 to 4.4.10
Hi,
this is already fixed in oVirt 4.5 [0]. Possible workaround might be to
downgrade the iproute-tc package below version 5.15.0-3.
Regards,
Ales
[0]
https://github.com/oVirt/vdsm/commit/503a98139d65daed856d97a8c6d7f875bcbe42df
On Fri, Mar 25, 2022 at 1:15 PM Christoph Timm wrote:
> 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
>
[ovirt-users] Re: No bootable device
On Sun, Mar 27, 2022 at 9:09 PM Richard W.M. Jones wrote: > > > On Sun, Mar 27, 2022 at 01:18:43PM +0300, Arik Hadas wrote: > > That information message is incorrect, both OVAs that are created by > > oVirt/RHV and OVAs that are created by VMware are supported It could > > work for OVAs that are VMware-compatible though > > "VMware-compatible" is doing a bit of work there. Virt-v2v only > supports (and more importantly _tests_) OVAs produced by VMware. > Anything claiming to be "VMware-compatible" might or might not work. > > I'm on holiday at the moment but I can have a look at the OVA itself > when I get back if someone posts a link. The v2v log was from this image: https://github.com/brimstone/metasploitable3/releases/download/0.1.4/Metasploitable3-0.1.4.ova ___ 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/YUHELHX37V3TZZCKOXXHK4J5V3EHC33A/
[ovirt-users] Re: No bootable device
On Sun, Mar 27, 2022 at 01:18:43PM +0300, Arik Hadas wrote: > That information message is incorrect, both OVAs that are created by > oVirt/RHV and OVAs that are created by VMware are supported It could > work for OVAs that are VMware-compatible though "VMware-compatible" is doing a bit of work there. Virt-v2v only supports (and more importantly _tests_) OVAs produced by VMware. Anything claiming to be "VMware-compatible" might or might not work. I'm on holiday at the moment but I can have a look at the OVA itself when I get back if someone posts a link. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v ___ 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/6ECSCDJ7FHXVO37K5E7KVP252XZCXHJA/
[ovirt-users] Re: Big problem on Ovirt 4.4
You can reinstall your node - it will be assigned ryzen-based model for the cluster.Once you import the storage domains, all VMs should be visible. Then you can edit each VM, verify NIC, MAC address and change the CPU type of the VM to the one that is available in the Cluster (respectfully the host). Best Regards,Strahil Nikolov On Sat, Mar 26, 2022 at 19:02, Nenhum_de_Nos wrote: On Sat, 26 Mar 2022 06:37:39 + (UTC) Strahil Nikolov via Users wrote: > Can you summarize the situation, as it's hard to get an idea of the > situation? On the Hypervisor: rpm -qa | grep ovirt | sortvirsh -c > qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf > domcapabilities From the Engine UI:Cluster version and CPU type From > the HostedEngine VM:rpm -qa | grep ovirt | sort Best Regards, > Nikolov Hi Strahil, I know it was not the best explanation of the issue, I was kind stressed as my VM's were offline for almost a week. Now things are quite again. I think this problem I went through is not quite common to ovirt users as by what I could see here, people use server hardware, unlike me. After the power outage I could not get my node back active on the cluster (there is just one node here). And no matter how many times I tried, the logs kept saying the CPU was not compatible. I am answering here as I could not find this on my search through google and mail lists, forums (just could not see the redhat forum, I don't have account there). My problem was that my machine got some kind of bios reset, at least it disabled Virtualization Capabilities. And as I had not turned it off, I never would suspect it was this. In a desperate move, I installed ESXi on the machine and begun migrating my VM's. When the first was able to run, he hypervisor told me mu CPU was not VM capable. So then it hit me. I got back on the ovirt engine I had installed from scratch, and it was fine installing the node on cluster version 4.3 and the AMD EPYC IBPB SSBD. Then I just had to follow your hint to import the Storage Domain (another issue here, I tried to add it and then canceled, so it got stuck and couldn't import it until I wen to psql and delete the line by hand). The error message was always "Host ryzen-node moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all". And I never would guess that above from this :( When I tried to remove the node and add again, as it was CentOS8 based and I could not install packages, it all went downhill to a state where I tried to update packages from command line and the Engine GUI would not work anymore. Now the storm is behind me and I now have both node and engine up to date. I will now seek information on how to keep them updated so I don't have to be on that road again. Thanks for all support! I guess those rpm commands are no longer needed, right? If so, I can send afterwards. One last question, is it safe to update the cluster version to 4.6 using Ryzen 3400G? thanks, matheus > On Fri, Mar 25, 2022 at 20:31, Nenhum_de_Nos > wrote: On Fri, 25 Mar 2022 18:01:01 + (UTC) Strahil Nikolov via > Users wrote: > > > 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 > > Hi Strahil, thanks for the info. > > My main issue now is the ovirt node. Its no easy for me to get an > intel based one and my ryzen based I cannot add to any cluster. I > tried creating clusters from 4.2 to 4.6, and its the same error over > and over again. Not compatible :( > > I don't get it, before last satyrday it was, and worked fine. I > reinstalled all, I need those VM's ASAP, most my things are offline > for a week now. It's house stuff, yes, not big company production > VM's, no, but I need them to have all my stuff here. > > thanks to all that helped. > > matheus > ___ 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/2FB6TCFUETAE6XZRCCCSC4EYH2I2BQCZ/
[ovirt-users] Re: No bootable device
On Sun, Mar 27, 2022 at 12:24 PM Nir Soffer wrote:
> On Wed, Mar 23, 2022 at 3:09 PM wrote:
> > We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit
> > v.3, FWIW)
>
> Is it Metasploitable3-0.1.4.ova from the github releases page?
> https://github.com/brimstone/metasploitable3/releases
>
> If not, can you share the image? It will help if we can reproduce this
> problem
> locally with the same image you are using.
>
> > using the GUI (Storage -> Disks -> Upload -> Start). The
> > image is in qcow2 format.
>
> Did you convert the vmdk file from the ova to qcow2?
>
> > No options on the right side were checked. The
> > upload went smoothly, so we now tried to attach the disk to a VM.
> >
> > To do that, we opened the VM -> Disks -> Attach and selected the disk.
> > As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so
> > the "bootable" checkbox was selected.
> >
> > The VM was later powered on, but when accessing the console the message
> > "No bootable device." appears. We're pretty sure this is a bootable
> > image, because it was tested on other virtualization infrastructure and
> > it boots well. We also tried to upload the image in RAW format but the
> > result is the same.
> >
> > What are we missing here? Is anything else needed to do so the disk is
> > bootable?
>
> It sounds like you converted an image from another virtualization
> system (virtualbox)
> to qcow2 format, which may not be good enough to use the virtual machine.
>
> oVirt supports importing OVA, but based on the UI, it supports only OVA
> created
> by oVirt.
>
That information message is incorrect, both OVAs that are created by
oVirt/RHV and OVAs that are created by VMware are supported
It could work for OVAs that are VMware-compatible though
Posted https://github.com/oVirt/ovirt-engine/pull/191 to emphasis that
>
> You can try virt-v2v - this is an example command, you need
> to fill in the {} parts:
>
> virt-v2v \
> -i ova {path-to-ova-file} \
> -o rhv-upload \
> -oc https://{engine-address}/ovirt-engine/api \
> -op {engine-password-file} \
> -on {vm-name} \
> -os {storrage-domain-name} \
> -of qcow2 \
> -oo rhv-cafile={engine-ca-file} \
> -oo rhv-cluster={cluster-name}
>
> I tried to import the Metasploitable3-0.1.4.ova, and virt-v2 fails
> with this error:
>
> virt-v2v: error: inspection could not detect the source guest (or
> physical machine).
>
> attached virt-v2v log.
>
> Nir
>
___
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/XLRNVGUB43YPAYOBSGA6BZZD6ULUMC5H/
[ovirt-users] Re: No bootable device
On Wed, Mar 23, 2022 at 3:09 PM wrote:
> We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit
> v.3, FWIW)
Is it Metasploitable3-0.1.4.ova from the github releases page?
https://github.com/brimstone/metasploitable3/releases
If not, can you share the image? It will help if we can reproduce this problem
locally with the same image you are using.
> using the GUI (Storage -> Disks -> Upload -> Start). The
> image is in qcow2 format.
Did you convert the vmdk file from the ova to qcow2?
> No options on the right side were checked. The
> upload went smoothly, so we now tried to attach the disk to a VM.
>
> To do that, we opened the VM -> Disks -> Attach and selected the disk.
> As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so
> the "bootable" checkbox was selected.
>
> The VM was later powered on, but when accessing the console the message
> "No bootable device." appears. We're pretty sure this is a bootable
> image, because it was tested on other virtualization infrastructure and
> it boots well. We also tried to upload the image in RAW format but the
> result is the same.
>
> What are we missing here? Is anything else needed to do so the disk is
> bootable?
It sounds like you converted an image from another virtualization
system (virtualbox)
to qcow2 format, which may not be good enough to use the virtual machine.
oVirt supports importing OVA, but based on the UI, it supports only OVA created
by oVirt.
You can try virt-v2v - this is an example command, you need
to fill in the {} parts:
virt-v2v \
-i ova {path-to-ova-file} \
-o rhv-upload \
-oc https://{engine-address}/ovirt-engine/api \
-op {engine-password-file} \
-on {vm-name} \
-os {storrage-domain-name} \
-of qcow2 \
-oo rhv-cafile={engine-ca-file} \
-oo rhv-cluster={cluster-name}
I tried to import the Metasploitable3-0.1.4.ova, and virt-v2 fails
with this error:
virt-v2v: error: inspection could not detect the source guest (or
physical machine).
attached virt-v2v log.
Nir
v2v.log.xz
Description: application/xz
___
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/SSTTTGN2NMV4FMLZYUBSQWV2KLKROIZE/
