[ovirt-users] Re: ovirt4.4 vm with windows 2008r2 bsod19

[grig . 4n]

minidump file info: 

062421-17171-01.dmp 24.06.2021 10:33:29 BAD_POOL_HEADER 0x0019  
`0021   f8a0`0f9b4000   `a300   
006f006f`0052005c   ntoskrnl.exentoskrnl.exe+93ba0  NT Kernel & 
System  Microsoft® Windows® Operating SystemMicrosoft Corporation   
6.1.7601.24384 (win7sp1_ldr_escrow.190220-1800) x64 ntoskrnl.exe+93ba0  
C:\Windows\Minidump\062421-17171-01.dmp 8   
15  7601269 464 24.06.2021 10:35:16 

062421-28500-01.dmp 24.06.2021 10:27:18 PAGE_FAULT_IN_NONPAGED_AREA 
0x0050  `3d21   `0001   
f880`013e2f58   `0005   ntoskrnl.exe
ntoskrnl.exe+93ba0  NT Kernel & System  Microsoft® Windows® Operating 
SystemMicrosoft Corporation   6.1.7601.24384 
(win7sp1_ldr_escrow.190220-1800) x64 ntoskrnl.exe+93ba0 
 C:\Windows\Minidump\062421-28500-01.dmp 8   15  7601   
 269 464 24.06.2021 10:32:32 

061721-17531-01.dmp 17.06.2021 11:22:30 PAGE_FAULT_IN_NONPAGED_AREA 
0x0050  fd09`40515b88   `   
f800`01b9f60c   `0007   win32k.sys  
win32k.sys+283d84   Многопользовательский драйвер Win32 Операционная 
система Microsoft® Windows®Microsoft Corporation   6.1.7600.16385 
(win7_rtm.090713-1255)   x64 ntoskrnl.exe+93ba0 
 C:\Windows\Minidump\061721-17531-01.dmp 8   15  7601269 
464 17.06.2021 11:25:40 

chkdsk, sfc - whith out errors 
installed all drivers, in manualy from iso virtio-1.9.14.
___
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/DSVDT4RV3OQTVVF2LHWGMYEWES336HEM/

[ovirt-users] Re: oVirt 4.4.5 - Windows Server 2003 VM Reboot problems

[Liran Rotenberg]

On Thu, Jun 24, 2021 at 12:42 AM  wrote:

> Hi All,
>
> I've had to migrate a Windows Server 2003 R2 VM from VMWare to oVirt which
> I have successfully managed to get running.
>
> The problem I have is if I try to reboot from the OS I receive the
> following message after the VM shuts down but doesn't reboot:
>
> "Exit message: Lost connection with qemu process."
>
> Also any attempt to either shutdown or reboot from oVirt Manager has no
> effect.
>
> I realize that this OS is not supported in the current oVirt version, but
> is there something I am missing to get it working 'unsupported' please?
>
Reboot interacts with the guest OS, for that you need to have guest-agent
installed. In the older version you had windows guest tools ISO to install
it (WGT).

>
> Regards
>
> Simon...
> ___
> 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/BLMLUG5FZIM2TTUJA64IM5H6ORD6QEYN/
>
___
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/DB42SMTCGCVCNAFPRFEQYAOTFPF3QMSM/

[ovirt-users] Re: Disk (brick) failure on my stack

[Strahil Nikolov via Users]

 Are you using HW raid ? The stripe size and the ammount of physical disks is 
very important for the storage alignment.
Also do you use VDO ?
LVM allignment:
pvcreate --dataalignment alignment_value disk
For example if you use 12 disks in raid6 with 128KiB stripe unit size, 
alignment_value will be '1280k' ( 10 disks without the parity multiplied by 
128KiB).
vgcreate --physicalextentsize extentsize VOLGROUP physical_volume
With the same example, extentsize should be again '1280k'.
If you will be relying on gluster snapshots, you should create thinpool with 
1-2 MiB chunk size:
lvcreate --thinpool VOLGROUP/thin_pool --size 800g --chunksize 1280k 
--poolmetadatasize 16G --zero n
This example is again for raid6 with 12 disks and 128KiB stripe size. Note that 
the poolmetadata cannot be changed and it's always smart to set it to the max 
(16G)
For the LV ontop the thinpool you won't need any alignment:
lvcreate --thin --name LV_name --virtualsize LV_size VOLGROUP/thin_pool

FS alignment:Creating your XFS will need alignment again and also inode size of 
512.

mkfs.xfs -f -i size=512 -n size=8192 -d su=128k,sw=10 /dev/vg/thinlv
Note: su= HW stripe size, sw= data disks in the raid

I would mount that Filesystem with the following options(SELINUX enabled):
context=system_u:object_r:glusterd_brick_t:s0,noatime,inode64
If you disabled SELINUX , then you won't need the 'context=' option.

Once you have your brick restored you can remove the old and readd the new one:
gluster volume remove-brick  replica 2  
force
Note: ensure that you are removing the brick that has really failed. Full payh 
to brick can be taken from gluster volume info. The previous command will turn 
the volume into 'replica 2' which is sensitive to splitbrain. Don't do any 
maintenance till you add and heal the 3rd brick.

Next readd the fixed brick:
gluster volume add-brick  replica 3 

You can force a full heal:
gluster volume heal  full


About the disk alignment, you can read: 
https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.1/html/administration_guide/brick_configuration
I know that there is an ansible role that can do that for you, but I have never 
used it directly.
If you use VDO, I can try to find what I'm using (which might not be the best).

Best Regards,Strahil Nikolov
 
  On Wed, Jun 23, 2021 at 1:58, Dominique 
Deschênes 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/RRC5X7DBCDKKSLAOEDAR5V2N7ULFZ2WD/
  
___
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/3UVS5SDL4V2DLYVS3DDWCDPSHLGYIQNX/

[ovirt-users] Re: [ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing

[Sketch]

On Wed, 23 Jun 2021, Nir Soffer wrote:


On Wed, Jun 23, 2021 at 12:22 PM Sketch  wrote:


Installation fails on a CentOS Linux 8.4 host using yum update.

  Problem 1: cannot install the best update candidate for package 
vdsm-4.40.60.7-1.el8.x86_64
   - nothing provides python3-sanlock >= 3.8.3-3 needed by 
vdsm-4.40.70.4-1.el8.x86_64
   - nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64



This version was not released yet for Centos. You need to wait until
this package
is released on Centos if you want to upgrade ovirt to 4.4.7.

If you want to use the latest oVirt version as soon as it is released,
you need to use
Centos Stream.


I suspected that might have been the case, but figured I'd mention it 
since we're on RC4 now and the release notes say it's available for RHEL 
8.4 a well as Stream.  I checked the RHEL package browser and it doesn't 
have sanlock >= 3.8.3-3 yet either.  Is the oVirt 4.4.7 GA release waiting 
on this update to be pushed?

___
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/ZOQOBR6MDDUNNFUQ4WRCH6GGHQDUQFD6/

[ovirt-users] oVirt 4.4.5 - Windows Server 2003 VM Reboot problems

[simon]

Hi All,

I've had to migrate a Windows Server 2003 R2 VM from VMWare to oVirt which I 
have successfully managed to get running.

The problem I have is if I try to reboot from the OS I receive the following 
message after the VM shuts down but doesn't reboot:

"Exit message: Lost connection with qemu process."

Also any attempt to either shutdown or reboot from oVirt Manager has no effect.

I realize that this OS is not supported in the current oVirt version, but is 
there something I am missing to get it working 'unsupported' please?

Regards

Simon...
___
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/BLMLUG5FZIM2TTUJA64IM5H6ORD6QEYN/

[ovirt-users] Re: Mount Export Domain only temporary

[Strahil Nikolov via Users]

You can mount the NFS outside oVirt and backup to it 
Also, you can use pacemaker (if the NFS is a linux server) to ensure that 
failover is immediate and with NFS v3 the recovery of the clients should be 
fast enough to avoid troubles.

Best Regards,Strahil Nikolov
 
 
  On Wed, Jun 23, 2021 at 11:51, jb wrote:   Hello 
community,

We use a NFS export domain for full backups. Sometimes I have to restart 
the NFS file server, but when I just restart that server, without doing 
anything in oVirt (I guess normally I should put the domain in 
maintenance mode), it can happen that hosts and VMs a crashing.

I had one time even the issue, that after a crash one XFS file system on 
one host got damage and I had to fix that.

My though was now, because I make only one time a week a VM full backup, 
I only mount the export domain in this time.

Is there an easy way to do this, with the API? Or would you have a other 
hint, how to solve this issue?


Have a good day!

Jonathan

___
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/QAFV3KKXAMYOESEPGPWMCSNUTA5LH2JV/
  
___
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/27K75M23NPSSSODRRJ7LJCT3VDRLRIWI/

[ovirt-users] Re: Is there a slack channel for oVirt project?

[Jesse Hu]

Hi Sandor, Thanks very much for the details!
___
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/MOV3A4YGDMOCNMCV236R5RPYNKJTVYPD/

[ovirt-users] Re: [ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing

[Nir Soffer]

On Wed, Jun 23, 2021 at 12:22 PM Sketch  wrote:
>
> Installation fails on a CentOS Linux 8.4 host using yum update.
>
> I had previously installed ceph and python3-os-brick from the
> centos-oepnstrack-train and ceph-nautilus repos, but I removed the
> packages and the repos and ran dnf distro-sync, and used yum list
> installed just to be sure everything was in a clean state with no extra
> packages installed from nonstandard repos.
>
> Here's the output from yum update:
>
> Last metadata expiration check: 2:31:18 ago on Tue 22 Jun 2021 11:26:39 PM 
> PDT.
> Error:
>   Problem 1: cannot install the best update candidate for package 
> vdsm-4.40.60.7-1.el8.x86_64
>- nothing provides python3-sanlock >= 3.8.3-3 needed by 
> vdsm-4.40.70.4-1.el8.x86_64
>- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64

This version was not released yet for Centos. You need to wait until
this package
is released on Centos if you want to upgrade ovirt to 4.4.7.

If you want to use the latest oVirt version as soon as it is released,
you need to use
Centos Stream.

Nir

>   Problem 2: package vdsm-hook-fcoe-4.40.70.4-1.el8.noarch requires vdsm = 
> 4.40.70.4-1.el8, but none of the providers can be installed
>- cannot install the best update candidate for package 
> vdsm-hook-fcoe-4.40.60.7-1.el8.noarch
>- nothing provides python3-sanlock >= 3.8.3-3 needed by 
> vdsm-4.40.70.4-1.el8.x86_64
>- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
>   Problem 3: package vdsm-hook-ethtool-options-4.40.70.4-1.el8.noarch 
> requires vdsm = 4.40.70.4-1.el8, but none of the providers can be installed
>- cannot install the best update candidate for package 
> vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch
>- nothing provides python3-sanlock >= 3.8.3-3 needed by 
> vdsm-4.40.70.4-1.el8.x86_64
>- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
>   Problem 4: cannot install the best update candidate for package 
> vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
>- package vdsm-hook-vmfex-dev-4.40.70.4-1.el8.noarch requires vdsm = 
> 4.40.70.4-1.el8, but none of the providers can be installed
>- nothing provides python3-sanlock >= 3.8.3-3 needed by 
> vdsm-4.40.70.4-1.el8.x86_64
>- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
>   Problem 5: package ovirt-provider-ovn-driver-1.2.33-1.el8.noarch requires 
> vdsm, but none of the providers can be installed
>- package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-http = 
> 4.40.60.7-1.el8, but none of the providers can be installed
>- package vdsm-4.40.70.1-1.el8.x86_64 requires vdsm-http = 
> 4.40.70.1-1.el8, but none of the providers can be installed
>- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-http = 
> 4.40.70.2-1.el8, but none of the providers can be installed
>- package vdsm-4.40.17-1.el8.x86_64 requires vdsm-http = 4.40.17-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.18-1.el8.x86_64 requires vdsm-http = 4.40.18-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.19-1.el8.x86_64 requires vdsm-http = 4.40.19-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.20-1.el8.x86_64 requires vdsm-http = 4.40.20-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.21-1.el8.x86_64 requires vdsm-http = 4.40.21-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.22-1.el8.x86_64 requires vdsm-http = 4.40.22-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-http = 
> 4.40.26.3-1.el8, but none of the providers can be installed
>- package vdsm-4.40.30-1.el8.x86_64 requires vdsm-http = 4.40.30-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.31-1.el8.x86_64 requires vdsm-http = 4.40.31-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.32-1.el8.x86_64 requires vdsm-http = 4.40.32-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.33-1.el8.x86_64 requires vdsm-http = 4.40.33-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.34-1.el8.x86_64 requires vdsm-http = 4.40.34-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.35-1.el8.x86_64 requires vdsm-http = 4.40.35-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-http = 
> 4.40.35.1-1.el8, but none of the providers can be installed
>- package vdsm-4.40.36-1.el8.x86_64 requires vdsm-http = 4.40.36-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.37-1.el8.x86_64 requires vdsm-http = 4.40.37-1.el8, 
> but none of the providers can be installed
>- package vdsm-4.40.38-1.el8.x86_64 requires vdsm-http = 4.40.38-1.el8, 
> but none of the providers can be installed
>- package vd

[ovirt-users] Re: Is there a slack channel for oVirt project?

[Sandro Bonazzola]

Il giorno mer 23 giu 2021 alle ore 06:41 Jesse Hu  ha
scritto:

> Hi folks, Is there a slack channel for oVirt project? and is the #ovirt
> channel on irc.oftc.net server still active? I'd like to learn how oVirt
> project can be used for building IaaS platform, and whether oVirt community
> is active to provide support for questions. Thanks a lot.
>

Hi and welcome to oVirt!
The #ovirt channel on irc.oftc.net server is still active. The oVirt
community is pretty active and supportive so you're welcome to ask
questions :-)
I would recommend exploring the ovirt website and the documentation as a
first step.

About slack, there was an attempt to use it https://ovirt.slack.com/ but it
never got used consistently and has been abandoned since 2017 so I wouldn't
expect any reply by asking there.

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D 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/G5W6I6EYTRUS5VHB7R5C5O344OLGA53L/

[ovirt-users] Re: [ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing

[Sketch]

Installation fails on a CentOS Linux 8.4 host using yum update.

I had previously installed ceph and python3-os-brick from the 
centos-oepnstrack-train and ceph-nautilus repos, but I removed the 
packages and the repos and ran dnf distro-sync, and used yum list 
installed just to be sure everything was in a clean state with no extra 
packages installed from nonstandard repos.


Here's the output from yum update:

Last metadata expiration check: 2:31:18 ago on Tue 22 Jun 2021 11:26:39 PM PDT.
Error:
 Problem 1: cannot install the best update candidate for package 
vdsm-4.40.60.7-1.el8.x86_64
  - nothing provides python3-sanlock >= 3.8.3-3 needed by 
vdsm-4.40.70.4-1.el8.x86_64
  - nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
 Problem 2: package vdsm-hook-fcoe-4.40.70.4-1.el8.noarch requires vdsm = 
4.40.70.4-1.el8, but none of the providers can be installed
  - cannot install the best update candidate for package 
vdsm-hook-fcoe-4.40.60.7-1.el8.noarch
  - nothing provides python3-sanlock >= 3.8.3-3 needed by 
vdsm-4.40.70.4-1.el8.x86_64
  - nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
 Problem 3: package vdsm-hook-ethtool-options-4.40.70.4-1.el8.noarch requires 
vdsm = 4.40.70.4-1.el8, but none of the providers can be installed
  - cannot install the best update candidate for package 
vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch
  - nothing provides python3-sanlock >= 3.8.3-3 needed by 
vdsm-4.40.70.4-1.el8.x86_64
  - nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
 Problem 4: cannot install the best update candidate for package 
vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
  - package vdsm-hook-vmfex-dev-4.40.70.4-1.el8.noarch requires vdsm = 
4.40.70.4-1.el8, but none of the providers can be installed
  - nothing provides python3-sanlock >= 3.8.3-3 needed by 
vdsm-4.40.70.4-1.el8.x86_64
  - nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
 Problem 5: package ovirt-provider-ovn-driver-1.2.33-1.el8.noarch requires 
vdsm, but none of the providers can be installed
  - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-http = 4.40.60.7-1.el8, 
but none of the providers can be installed
  - package vdsm-4.40.70.1-1.el8.x86_64 requires vdsm-http = 4.40.70.1-1.el8, 
but none of the providers can be installed
  - package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-http = 4.40.70.2-1.el8, 
but none of the providers can be installed
  - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-http = 4.40.17-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-http = 4.40.18-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-http = 4.40.19-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-http = 4.40.20-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-http = 4.40.21-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-http = 4.40.22-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-http = 4.40.26.3-1.el8, 
but none of the providers can be installed
  - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-http = 4.40.30-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-http = 4.40.31-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-http = 4.40.32-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-http = 4.40.33-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-http = 4.40.34-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-http = 4.40.35-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-http = 4.40.35.1-1.el8, 
but none of the providers can be installed
  - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-http = 4.40.36-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-http = 4.40.37-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-http = 4.40.38-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-http = 4.40.39-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-http = 4.40.40-1.el8, but 
none of the providers can be installed
  - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-http = 4.40.50.8-1.el8, 
but none of the providers can be installed
  - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-http = 4.40.50.9-1.el8, 
but none of the providers can be installed
  - package vdsm-4.40.60.6-1.e

[ovirt-users] Mount Export Domain only temporary

[jb]

Hello community,

We use a NFS export domain for full backups. Sometimes I have to restart 
the NFS file server, but when I just restart that server, without doing 
anything in oVirt (I guess normally I should put the domain in 
maintenance mode), it can happen that hosts and VMs a crashing.


I had one time even the issue, that after a crash one XFS file system on 
one host got damage and I had to fix that.


My though was now, because I make only one time a week a VM full backup, 
I only mount the export domain in this time.


Is there an easy way to do this, with the API? Or would you have a other 
hint, how to solve this issue?



Have a good day!

Jonathan

___
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/QAFV3KKXAMYOESEPGPWMCSNUTA5LH2JV/

[ovirt-users] Re: Problems moving vm & templates between oVirt 4.3 & 4.4

[Arik Hadas]

On Wed, Jun 23, 2021 at 8:27 AM Guillaume Pavese <
guillaume.pav...@interactiv-group.com> wrote:

> I opened : https://bugzilla.redhat.com/show_bug.cgi?id=1975076
>

Thanks for filing it.
If you wish to transfer VMs from oVirt 4.4 to oVirt 4.3, you have to make
sure that the cluster you use in oVirt 4.4 is set with compatibility level
which is supported in oVirt 4.3 (that is, compatibility level 4.2 or 4.3),
as forward-compatibility is not supported.


>
>
>
> Guillaume Pavese
> Ingénieur Système et Réseau
> Interactiv-Group
>
>
> On Tue, Jun 22, 2021 at 12:26 PM Strahil Nikolov 
> wrote:
>
>> Error during ValidateFailure.: java.lang.IllegalArgumentExcepti
>> on: VM64BitMaxMemorySizeInMB has no value for version: 4.6
>>
>>
>> This one is quite interesting... Most probably is a bug.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> On Tue, Jun 22, 2021 at 0:59, Guillaume Pavese
>>  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/XXFQFMUD76O53PSA3XZHSXTMHHPBOEE3/
>>
>>
> Ce message et toutes les pièces jointes (ci-après le “message”) sont
> établis à l’intention exclusive de ses destinataires et sont confidentiels.
> Si vous recevez ce message par erreur, merci de le détruire et d’en avertir
> immédiatement l’expéditeur. Toute utilisation de ce message non conforme a
> sa destination, toute diffusion ou toute publication, totale ou partielle,
> est interdite, sauf autorisation expresse. L’internet ne permettant pas
> d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales)
> décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse
> ou il aurait été modifié. IT, ES, UK.
> 
> ___
> 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/2UNL6ASMOTFMT5NIIIR2GGC25KMPIT3J/
>
___
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/DRL7EK3XS2ZZGMS3UDTLHLBWASIFRBK3/