Re: [External]: Re: Need to transfer a VM from oVirt to vSphere
by Gianluca Cecchi
On Fri, Jun 24, 2022 at 4:38 PM David M. Hornsby <dmhornsby(a)mueller1875.com>
wrote:
> I have done this before quite a few times. What I did was:
>
>
> 1. Export the qcow2 or raw file and convert it: qemu-img convert -f
> qcow2 -O vmdk
> 2. Import the vmdk into vsphere storage and convert it to thin with
> vmkfstools
> 3. Then create the vm definition.
> 4. There will be some minor driver and ethernet type stuff to fix.
>
> This process has worked everytime. You probably could use a tool like virt
> v2v or veeam to accomplish this as well.
>
> David
>
>
Thanks David, I didn't see your e-mail while I was writing my answer.
I confirm I went a similar way (but passing anyway from OVA and then
extracting the disk...)
Gianluca
1 year, 10 months
Need to transfer a VM from oVirt to vSphere
by Gianluca Cecchi
Hello,
I need to transfer a VM from oVirt 4.4 to vSphere.
I see that the "Export as OVA" in the GUI exports in a format compatible
with oVirt but not vSphere.
Any hint?
Any way to easily convert the oVirt generated OVA to a vSPhere compatible
one?
Thanks,
Gianluca
1 year, 10 months
HCI Upgrade 4.4 to 4.5 Gluster 10
by simon＠justconnect.ie
Hi All,
When Upgrading ovirt 4.4 to 4.5 when using GlusterFS, should Gluster be upgraded manually before the nodes are upgraded?
Simon...
1 year, 10 months
Unable to ugprade cluster level to 4.7 for the hosted engine (only)
by lists＠pequod.io
Hello,
i upgraded my engine and nodes to 4.5 a few days ago and now planning to upgrade the cluster level compatibility from 4.6 to 4.7. First i tried doing this from the cluster settings, but it fails because hosted-engine settings are locked. So i tried it by hand but again got the locked error, i found i cant change any values on the hosted engine. Changing compatiblity level on all other VMs worked fine and there are on 4.7 now.
I read about the timezone issue in 4.4.8, so i checked the timezone of my hosted engine it is filled with "Standard: (GMTZ) Greenwhich Standard Time". To be sure, i just did a "/usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "update vm_static SET time_zone='Etc/GMT' where vm_name='HostedEngine';"" and it changed the timezone, but settings are still locked and i am unable to change the compatibility level.
Any idea how to solve this?
1 year, 10 months
oVirt Node 4.5.1
by Lev Veyde
On June 23rd 2022 the oVirt project released an update of oVirt Node
(4.5.1) delivering several security fixes, bug fixes and enhancements.
The update is already available on resources.ovirt.org and should land on
oVirt mirrors within 24 hours.
With oVirt 4.5.1 oVirt Node based on CentOS Stream 9 is also available as a
tech preview.
Known issues:
-
On oVirt Node based on CentOS Stream 9 with UEFI secure boot, vdsm fails
to decode DMI data due to Bug 2081648
<https://bugzilla.redhat.com/show_bug.cgi?id=2081648> – python-dmidecode
module fails to decode DMI data
Updates on el8 based oVirt Node:
Security fixes:
-
Important - Bug 2082616
<https://bugzilla.redhat.com/show_bug.cgi?id=2082616> - CVE-2022-24903 -
rsyslog: Heap-based overflow in TCP syslog server
-
Important - Bug 2072376
<https://bugzilla.redhat.com/show_bug.cgi?id=2072376> - CVE-2018-25032 -
zlib: A flaw in zlib-1.2.11 when compressing (not decompressing!) certain
inputs.
-
Important - Bug 2065568
<https://bugzilla.redhat.com/show_bug.cgi?id=2065568> - CVE-2022-27666 -
kernel: buffer overflow in IPsec ESP transformation code
Other updates:
-
CentOS Stream 8 latest updates
-
Full list of changes compared to oVirt Node 4.5.0.3:
oVirt Node 4.5.0.3
oVirt Node 4.5.1
NetworkManager 1.39.3-1.el8
1.39.5-1.el8
NetworkManager-config-server 1.39.3-1.el8
1.39.5-1.el8
NetworkManager-libnm 1.39.3-1.el8
1.39.5-1.el8
NetworkManager-ovs 1.39.3-1.el8
1.39.5-1.el8
NetworkManager-team 1.39.3-1.el8
1.39.5-1.el8
NetworkManager-tui 1.39.3-1.el8
1.39.5-1.el8
binutils 2.30-114.el8
2.30-116.el8
centos-release-ovirt45 8.7-1.el8s
8.7-2.el8s
cockpit 264.1-1.el8
270-1.el8
cockpit-bridge 264.1-1.el8
270-1.el8
cockpit-storaged 264.1-1.el8
269-1.el8
cockpit-system 264.1-1.el8
270-1.el8
cockpit-ws 264.1-1.el8
270-1.el8
cronie 1.5.2-6.el8
1.5.2-7.el8
cronie-anacron 1.5.2-6.el8
1.5.2-7.el8
cups-libs
2.2.6-45.el8
device-mapper-multipath 0.8.4-23.el8
0.8.4-25.el8
device-mapper-multipath-libs 0.8.4-23.el8
0.8.4-25.el8
dnf 4.7.0-9.el8
4.7.0-10.el8
dnf-data 4.7.0-9.el8
4.7.0-10.el8
dracut 049-201.git20220131.el8
049-202.git20220511.el8
dracut-config-generic 049-201.git20220131.el8
049-202.git20220511.el8
dracut-live 049-201.git20220131.el8
049-202.git20220511.el8
dracut-network 049-201.git20220131.el8
049-202.git20220511.el8
dracut-squash 049-201.git20220131.el8
049-202.git20220511.el8
e2fsprogs 1.45.6-4.el8
1.45.6-5.el8
e2fsprogs-libs 1.45.6-4.el8
1.45.6-5.el8
elfutils-default-yama-scope 0.186-1.el8
0.187-4.el8
elfutils-libelf 0.186-1.el8
0.187-4.el8
elfutils-libs 0.186-1.el8
0.187-4.el8
fence-agents-all 4.2.1-94.el8
4.2.1-97.el8
fence-agents-amt-ws 4.2.1-94.el8
4.2.1-97.el8
fence-agents-apc 4.2.1-94.el8
4.2.1-97.el8
fence-agents-apc-snmp 4.2.1-94.el8
4.2.1-97.el8
fence-agents-bladecenter 4.2.1-94.el8
4.2.1-97.el8
fence-agents-brocade 4.2.1-94.el8
4.2.1-97.el8
fence-agents-cisco-mds 4.2.1-94.el8
4.2.1-97.el8
fence-agents-cisco-ucs 4.2.1-94.el8
4.2.1-97.el8
fence-agents-common 4.2.1-94.el8
4.2.1-97.el8
fence-agents-compute 4.2.1-94.el8
4.2.1-97.el8
fence-agents-drac5 4.2.1-94.el8
4.2.1-97.el8
fence-agents-eaton-snmp 4.2.1-94.el8
4.2.1-97.el8
fence-agents-emerson 4.2.1-94.el8
4.2.1-97.el8
fence-agents-eps 4.2.1-94.el8
4.2.1-97.el8
fence-agents-heuristics-ping 4.2.1-94.el8
4.2.1-97.el8
fence-agents-hpblade 4.2.1-94.el8
4.2.1-97.el8
fence-agents-ibmblade 4.2.1-94.el8
4.2.1-97.el8
fence-agents-ifmib 4.2.1-94.el8
4.2.1-97.el8
fence-agents-ilo-moonshot 4.2.1-94.el8
4.2.1-97.el8
fence-agents-ilo-mp 4.2.1-94.el8
4.2.1-97.el8
fence-agents-ilo-ssh 4.2.1-94.el8
4.2.1-97.el8
fence-agents-ilo2 4.2.1-94.el8
4.2.1-97.el8
fence-agents-intelmodular 4.2.1-94.el8
4.2.1-97.el8
fence-agents-ipdu 4.2.1-94.el8
4.2.1-97.el8
fence-agents-ipmilan 4.2.1-94.el8
4.2.1-97.el8
fence-agents-kdump 4.2.1-94.el8
4.2.1-97.el8
fence-agents-mpath 4.2.1-94.el8
4.2.1-97.el8
fence-agents-redfish 4.2.1-94.el8
4.2.1-97.el8
fence-agents-rhevm 4.2.1-94.el8
4.2.1-97.el8
fence-agents-rsa 4.2.1-94.el8
4.2.1-97.el8
fence-agents-rsb 4.2.1-94.el8
4.2.1-97.el8
fence-agents-sbd 4.2.1-94.el8
4.2.1-97.el8
fence-agents-scsi 4.2.1-94.el8
4.2.1-97.el8
fence-agents-vmware-rest 4.2.1-94.el8
4.2.1-97.el8
fence-agents-vmware-soap 4.2.1-94.el8
4.2.1-97.el8
fence-agents-wti 4.2.1-94.el8
4.2.1-97.el8
glibc 2.28-200.el8
2.28-203.el8
glibc-common 2.28-200.el8
2.28-203.el8
glibc-langpack-en 2.28-200.el8
2.28-203.el8
kernel 4.18.0-383.el8
4.18.0-394.el8
kernel-core 4.18.0-383.el8
4.18.0-394.el8
kernel-modules 4.18.0-383.el8
4.18.0-394.el8
kernel-tools 4.18.0-383.el8
4.18.0-394.el8
kernel-tools-libs 4.18.0-383.el8
4.18.0-394.el8
kexec-tools 2.0.24-1.el8
2.0.24-2.el8
kpartx 0.8.4-23.el8
0.8.4-25.el8
libbasicobjects 0.1.1-39.el8
0.1.1-40.el8
libcap 2.48-2.el8
2.48-4.el8
libcollection 0.7.0-39.el8
0.7.0-40.el8
libcom_err 1.45.6-4.el8
1.45.6-5.el8
libdhash 0.5.0-39.el8
0.5.0-40.el8
libini_config 1.3.1-39.el8
1.3.1-40.el8
libldb 2.4.1-1.el8
2.5.0-1.el8
libpath_utils 0.2.1-39.el8
0.2.1-40.el8
libref_array 0.1.5-39.el8
0.1.5-40.el8
libss 1.45.6-4.el8
1.45.6-5.el8
libtdb 1.4.4-1.el8
1.4.6-1.el8
libtevent 0.11.0-0.el8
0.12.0-0.el8
libwbclient 4.15.5-8.el8
4.16.1-0.el8
mesa-dri-drivers 21.3.4-1.el8
21.3.4-1.0.1.el8
mesa-filesystem 21.3.4-1.el8
21.3.4-1.0.1.el8
mesa-libEGL 21.3.4-1.el8
21.3.4-1.0.1.el8
mesa-libGL 21.3.4-1.el8
21.3.4-1.0.1.el8
mesa-libgbm 21.3.4-1.el8
21.3.4-1.0.1.el8
mesa-libglapi 21.3.4-1.el8
21.3.4-1.0.1.el8
nmap-ncat 7.70-6.el8
7.70-7.el8
openvswitch-selinux-extra-policy 1.0-28.el8
1.0-29.el8s
osinfo-db 20211216-1.el8
20220516-1.el8
ovirt-ansible-collection 2.0.3-1.el8
2.1.0-1.el8
ovirt-hosted-engine-setup 2.6.3-1.el8
2.6.4-1.el8
ovirt-imageio-client 2.4.3-1.el8
2.4.5-1.el8
ovirt-imageio-common 2.4.3-1.el8
2.4.5-1.el8
ovirt-imageio-daemon 2.4.3-1.el8
2.4.5-1.el8
ovirt-node-ng-image-update-placeholder 4.5.0.3-1.el8
4.5.1-1.el8
ovirt-release-host-node 4.5.0.3-1.el8
4.5.1-1.el8
pacemaker-cluster-libs 2.1.2-4.el8
2.1.3-1.el8
pacemaker-libs 2.1.2-4.el8
2.1.3-1.el8
pacemaker-schemas 2.1.2-4.el8
2.1.3-1.el8
pam 1.3.1-16.el8
1.3.1-20.el8
python3-dnf 4.7.0-9.el8
4.7.0-10.el8
python3-perf 4.18.0-383.el8
4.18.0-394.el8
python38-ovirt-imageio-client 2.4.3-1.el8
2.4.5-1.el8
python38-ovirt-imageio-common 2.4.3-1.el8
2.4.5-1.el8
rpcbind 1.2.5-8.el8
1.2.5-9.el8
rsyslog 8.2102.0-9.el8
8.2102.0-10.el8
rsyslog-elasticsearch 8.2102.0-9.el8
8.2102.0-10.el8
rsyslog-mmjsonparse 8.2102.0-9.el8
8.2102.0-10.el8
rsyslog-mmnormalize 8.2102.0-9.el8
8.2102.0-10.el8
rsyslog-openssl 8.2102.0-9.el8
8.2102.0-10.el8
samba-client-libs 4.15.5-8.el8
4.16.1-0.el8
samba-common 4.15.5-8.el8
4.16.1-0.el8
samba-common-libs 4.15.5-8.el8
4.16.1-0.el8
scap-security-guide 0.1.60-7.el8
0.1.60-9.el8
selinux-policy 3.14.3-98.el8
3.14.3-99.el8
selinux-policy-targeted 3.14.3-98.el8
3.14.3-99.el8
sos 4.2-15.el8
4.3-1.el8
vdsm 4.50.0.13-1.el8
4.50.1.4-1.el8
vdsm-api 4.50.0.13-1.el8
4.50.1.4-1.el8
vdsm-client 4.50.0.13-1.el8
4.50.1.4-1.el8
vdsm-common 4.50.0.13-1.el8
4.50.1.4-1.el8
vdsm-gluster 4.50.0.13-1.el8
4.50.1.4-1.el8
vdsm-http 4.50.0.13-1.el8
4.50.1.4-1.el8
vdsm-jsonrpc 4.50.0.13-1.el8
4.50.1.4-1.el8
vdsm-network 4.50.0.13-1.el8
4.50.1.4-1.el8
vdsm-python 4.50.0.13-1.el8
4.50.1.4-1.el8
vdsm-yajsonrpc 4.50.0.13-1.el8
4.50.1.4-1.el8
yum 4.7.0-9.el8
4.7.0-10.el8
zlib 1.2.11-17.el8
1.2.11-19.el8
Additional resources:
-
Read more about the oVirt 4.5.1 release highlights:
https://www.ovirt.org/release/4.5.1/
-
Get more oVirt project updates on Twitter: https://twitter.com/ovirt
-
Check out the latest project news on the oVirt blog:
https://blogs.ovirt.org/
Thanks in advance,
--
Lev Veyde
Senior Software Engineer, RHCE | RHCVA | MCITP
Red Hat Israel
<https://www.redhat.com>
lev(a)redhat.com | lveyde(a)redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
1 year, 10 months
import vm disk image on ISCSI Data Domain
by sultanu＠inbox.ru
Hello, all
Maybe somebody have experiance.
I have cluster 3 hosts + ISCSI storage as Data Domain. How can i upload vm image from my old ovirt (baremetal with local storage) to my new cluster from CLI, NOT from WEB UI?
Dowload on my local computer and post from WEB UI it take long period of time.
Thak you for your time.
1 year, 10 months
Lost space in /var/log
by Andrei Verovski
Hi !
I have strange situation with low disk space on /var/log/, yet I can't
figure out what have consumed so much space.
Look at the du output.
Thanks in advance for any suggestion(s).
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-var 15G 1.3G 13G 9% /var
/dev/mapper/centos-var_log 7.8G 7.1G 293M 97% /var/log
/dev/mapper/centos-var_log_audit 2.0G 41M 1.8G 3% /var/log/audit
#
# du -ah /var/log | sort -n -r | head -n 20
664K /var/log/vdsm
660K /var/log/vdsm/vdsm.log
624K /var/log/gdm
580K /var/log/anaconda/storage.log
480K /var/log/anaconda/packaging.log
380K /var/log/gdm/:0.log.4
316K /var/log/anaconda/syslog
276K /var/log/tuned
252K /var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806
220K /var/log/Xorg.0.log
168K /var/log/gdm/:0.log
156K /var/log/yum.log-20191117
156K /var/log/secure-20180726
132K /var/log/libvirt/qemu/NextCloud-Collabora-Active.log
128K /var/log/anaconda/anaconda.log
120K /var/log/hp-snmp-agents
116K /var/log/hp-snmp-agents/cma.log
112K /var/log/vinchin
104K /var/log/vinchin/kvm_backup_service
104K /var/log/tuned/tuned.log.2
#
# find . -printf '%s %p\n'| sort -nr | head -10
16311686 ./rhsm/rhsm.log
4070423 ./cron-20180726
3667146 ./anaconda/journal.log
3409071 ./secure
3066660 ./rhsm/rhsm.log-20180726
2912670 ./audit/audit.log
1418007 ./sanlock.log
1189580 ./vdsm/vdsm.log
592718 ./anaconda/storage.log
487567 ./anaconda/packaging.log
1 year, 10 months
Re: Lost space in /var/log
by Michael Thomas
This can also happen with a misconfigured logrotate config. If a
process is writing to a large log file, and logrotate comes along and
removes it, then the process still has an open filehandle to the large
file even though you can't see it. The space won't get removed until
the process closes the filehandle (eg rebooting).
The following command should give you a list of these ghost files that
are still open but have been removed from the directory tree:
lsof | grep '(deleted)'
Stackexchange has some additional useful tips:
https://unix.stackexchange.com/questions/68523/find-and-remove-large-file...
--Mike
On 6/22/22 15:49, Matthew.Stier(a)fujitsu.com wrote:
> Deleted some files to "clean up" /var/log, but the space was not recovered?
>
> Space for deleted files are only recovered when all references to that space are removed. This includes the directory reference, and any open file-handles to the file.
>
> The is a popular trick for a self-deleting scratch file. Create a file, open file-handle to it, and then remove the file. The open file-handle can then be written to, and read from, as long as you like, but when the file-handle is closed, explicitly or implicitly, the space is automatically recovered.
>
>
> -----Original Message-----
> From: Andrei Verovski <andreil1(a)starlett.lv>
> Sent: Wednesday, June 22, 2022 3:27 PM
> To: users(a)ovirt.org
> Subject: [ovirt-users] Lost space in /var/log
>
> Hi !
>
> I have strange situation with low disk space on /var/log/, yet I can't figure out what have consumed so much space.
> Look at the du output.
>
> Thanks in advance for any suggestion(s).
>
>
> # df -h
>
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/centos-var 15G 1.3G 13G 9% /var
> /dev/mapper/centos-var_log 7.8G 7.1G 293M 97% /var/log
> /dev/mapper/centos-var_log_audit 2.0G 41M 1.8G 3% /var/log/audit
>
> #
> # du -ah /var/log | sort -n -r | head -n 20
>
> 664K /var/log/vdsm
> 660K /var/log/vdsm/vdsm.log
> 624K /var/log/gdm
> 580K /var/log/anaconda/storage.log
> 480K /var/log/anaconda/packaging.log
> 380K /var/log/gdm/:0.log.4
> 316K /var/log/anaconda/syslog
> 276K /var/log/tuned
> 252K /var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806
> 220K /var/log/Xorg.0.log
> 168K /var/log/gdm/:0.log
> 156K /var/log/yum.log-20191117
> 156K /var/log/secure-20180726
> 132K /var/log/libvirt/qemu/NextCloud-Collabora-Active.log
> 128K /var/log/anaconda/anaconda.log
> 120K /var/log/hp-snmp-agents
> 116K /var/log/hp-snmp-agents/cma.log
> 112K /var/log/vinchin
> 104K /var/log/vinchin/kvm_backup_service
> 104K /var/log/tuned/tuned.log.2
>
> #
> # find . -printf '%s %p\n'| sort -nr | head -10
>
> 16311686 ./rhsm/rhsm.log
> 4070423 ./cron-20180726
> 3667146 ./anaconda/journal.log
> 3409071 ./secure
> 3066660 ./rhsm/rhsm.log-20180726
> 2912670 ./audit/audit.log
> 1418007 ./sanlock.log
> 1189580 ./vdsm/vdsm.log
> 592718 ./anaconda/storage.log
> 487567 ./anaconda/packaging.log
> _______________________________________________
> 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/N566CST3DAX...
> _______________________________________________
> 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/JCAQU32UZSE...
1 year, 10 months
Q: Error ID 119 - ioctl(KVM_CREATE_VM) failed: Cannot allocate memory
by Andrei Verovski
Hi !
Does this error message means node runs out of RAM?
Quite strange since there are about 20 GB of free RAN, and VM requires
only 8.
I noticed this happen till Vinchin was in a process of removing snapshot
from another VM.
Thanks.
VM Jumis_VM-Active is down with error. Exit message: internal error:
process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed:
12 Cannot allocate memory
2022-06-22T19:50:46.501704Z qemu-kvm: failed to initialize KVM: Cannot
allocate memory.
1 year, 10 months
Move Master Storage Domain
by john＠penrod.net
Running oVirt 4.3.10.
Three storage domains. #1 is the current master. No disks/data remain on it. All virtual machines have been moved.
I plan to put it in maintenance mode and let it force an election. I don't care which of the remaining two become master.
Will this impact virtual machines that are currently running? If possible, I need to keep them running.
Thoughts?
1 year, 10 months
