date:20220204

> you have 16 developer self support subscriptions from RH, those are more than 
> enough to
> use with ovirt as a cluster/s.

I'd consider that an off-topic post.

And whilst we are off-topic, one of the main attractions of using TrueCentOS 
(the downstream Community ENterprise Operating System) even when my employer 
has a fat Redhat support contract that covers everything I do, is that I just 
didn't have to bother with license management at all.

It's a whole set of processes, activities and knowledge I could simply strike 
off the list and in the context of a lab environment with lots of machines and 
VMs getting created and deleted every day, that is a huge benefit.

Well RHEL not supporting OpenVZ containers was another reason never to bother 
with it and why we ran CentOS userlands even in PCI-DSS production.

I consider the benefit of zero license and subscription management still so 
significant, that I am rather investing into Alma, Rocky, Liberty, OracleLinux 
or VzLinux than dealing with RHEL.

And BetaCentOS aka SomethingStream just isn't an acceptable match for a 
hypervisor or a management engine "for the entire enterprise": Beta is for the 
VMs, if your work is low-level, but 99% of what we do is application level or 
in fact the science above it, where Beta just adds work and risks without any 
benefit.

Sorry for the rant, but posting stuff like that is asking for it.
___
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/BTWAULNR4KWV3LLFECBD4EA5LYUA4LVP/

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Fri, Feb 04, 2022 at 08:42:08AM +, Richard W.M. Jones wrote:
> On Thu, Feb 03, 2022 at 06:31:52PM +0200, Nir Soffer wrote:
> > This is expected on oVirt, our multipath configuration is intentionally 
> > grabbing
> > any device that multipath can work with, even if the device only has one 
> > path.
> > The motivation is to be able to configure a system when only one path is
> > available (maybe you have an hba/network/server issue), and once the other
> > paths are available the system will use them transparently.
> > 
> > To avoid this issue with local devices, you need to blacklist the device.
> > 
> > Add this file:
> > 
> > $ cat /etc/multipath/conf.d/local.conf
> > blacklist {
> > wwid "QEMU HARDDISK"
> > }
> 
> Thanks - for the mailing list record the syntax that worked for me is:
> 
> # cat /etc/multipath/conf.d/local.conf
> blacklist {
> wwid ".*QEMU_HARDDISK.*"
> }
> 
> > Configuring NFS on some other machine is easy.
> > 
> > I'm using another VM for this, so I can easily test negative flows like 
> > stopping
> > or restarting the NFS server while it is being used by vms or storage
> > operations.
> > I'm using 2G alpine vm for this, it works fine even with 1G memory.
> 
> I think I can get local storage working now (I had it working before).

Well finally it fails with:

2022-02-04 09:14:55,779Z ERROR 
[org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand] 
(default task-2) [25a32edf] Command 
'org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand' 
failed: EngineException: 
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
VDSGenericException: VDSErrorException: Failed to CreateStorageDomainVDS, error 
= Could not initialize cluster lock: (), code = 701 (Failed with error 
unexpected and code 16)

I think this feature (local storage) no longer works.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
___
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/OD43QV4C5HCQGDQVTA72QQBTTU7T6N45/

[ovirt-users] Re: Deploy ovirt-csi in the kubernetes cluster

2022-02-04 Thread moizr--- via Users

Hello, understand this is an old post but were you able to make this work on 
native kubernetes. 
___
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/SKTQAFVLPQ7D2TLIMDP7UFN7XB3ZXFGQ/

[ovirt-users] Re: Installing a windows vm from importing an OVA Template

2022-02-04 Thread moizr--- via Users

Hello, do you mean if there is a bug which is already discussed, is it possible 
to get that particular page. 
___
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/SOGX2RI75PG6T32OWV45Q2JAVMEFOSWL/

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Thu, Feb 03, 2022 at 06:31:52PM +0200, Nir Soffer wrote:
> This is expected on oVirt, our multipath configuration is intentionally 
> grabbing
> any device that multipath can work with, even if the device only has one path.
> The motivation is to be able to configure a system when only one path is
> available (maybe you have an hba/network/server issue), and once the other
> paths are available the system will use them transparently.
> 
> To avoid this issue with local devices, you need to blacklist the device.
> 
> Add this file:
> 
> $ cat /etc/multipath/conf.d/local.conf
> blacklist {
> wwid "QEMU HARDDISK"
> }

Thanks - for the mailing list record the syntax that worked for me is:

# cat /etc/multipath/conf.d/local.conf
blacklist {
wwid ".*QEMU_HARDDISK.*"
}

> Configuring NFS on some other machine is easy.
> 
> I'm using another VM for this, so I can easily test negative flows like 
> stopping
> or restarting the NFS server while it is being used by vms or storage
> operations.
> I'm using 2G alpine vm for this, it works fine even with 1G memory.

I think I can get local storage working now (I had it working before).

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
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/AU5UUXFNGPMBGETPZI3R445FFWESUGXK/

[ovirt-users] Re: Installing oVirt on RHEL vs CentOS Stream, Alma or Rocky Linux

> On Tue, Feb 1, 2022 at 7:55 PM Richard W.M. Jones  wrote:
> 
> Would you like to file a doc bug about this?
> 
> oVirt on RHEL is not such a common combination..
Well IBM seems bent on changing that (see the developer license post below)
> 
> In CI we only test on Centos Stream (8, hopefully soon also 9, we'll see),
> and RHV on RHEL.
Which is exactly why BetaStreamOS (upstream to RHEL) based oVirt is breaking 
the value proposition of TrueCentOS (downstream of RHEL) based oVirt as a 
solution "for the entire enterprise".

AFAIK there is no "developer license" of RHV so if you want to run a lab 
environment where the experimentation is done at app or science level (not OS), 
this new beta(OS)-on-beta(VM orchestration) stack just becomes too fragile to 
use, not that oVirt HCI has ever proven better than hardware level fault 
resilience to me, which I believe was its design goal.

> We'll be happy to get success/failure (with details) reports of attempts
> to install/setup both engine and hosts on other OSes.
> 
I have been working on just that, going through Alma, Rocky and Oracle (RHEL, 
Liberty and VzLinux might be added) using a nested VMs on VMware for two 
scenarios:
1. Installing oVirt on a new hardware node (a CentOS8 VM switched to each new 
EL8 brand)
2. Switching a pre-existing oVirt HCI node to a new EL8 brand

In all cases the virtual hosts wind up running a single node HCI gluster, to 
keep things reasonable simple.

All of these worked fine,with some tiny glitches, but that was before the 
gluster8 repos got archived. Currently I am awaiting that being fixed to 
continue testing and hopefully posting a somewhat bigger report here.

But there is another new issue that bothers me quite a bit: The oVirt 
management appliance:

I managed to still get one of the latest CentOS8 based appliances during my 
tests and that could evidently be switched to one of the other EL8 variants, 
once the repo issues are sorted out.

But newer versions of the appliance are built on the UpStreamBeta, which cannot 
(easily?) be switched to a downstream EL8, while the RHEL appliance most likely 
can't be used legally.

Using a Beta engine without the RHEL benefit of vulnerability management is a 
no-go in PCI-DSS or similar compliance heavy environments, so for oVirt to be a 
"solution for the entire enterprise" there needs to be an EL8 based engine, too.

But AFAIK there is not even a publicly available build script for the appliance 
so someone outside RH could build a matching bot. And forced downgrades of the 
engine to one of the EL8 variants might well break the engine...

> Next step is probably for someone to try and build an oVirt node image
> based on a different OS...
I would love trying (if I can find the time...), but I'm not sure where I could 
find build scripts...

One of the reasons I could never use these node images was that the 2.5Gbit USB 
Realtek driver is broken in EL7+EL8, which I used on my Atom based 3 node HCI. 
Building node images would allow adding drivers and putting in nested virt 
support...
> 
> 
> Perhaps I am missing something - is this oVirt-specific, or
> relevant?
> 
> Thanks and best regards,
___
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/ELW5CNTXJNAZ4IS3ONMBDSQ7LFGQNGZI/

[ovirt-users] Re: Installing a windows vm from importing an OVA Template

2022-02-04 Thread ravi k

Hello,
I work along with Moiz and here's what we tried. 

We created a blank VM, loaded Windows 2016 ISO and booted it up. When we select 
the OS as Windows 2016 x64 the ISO is loaded but the screen is stuck with the 
windows logo. The CPU spikes up to 99%.
However if we select the OS as 'Other OS' the installation proceeds. We 
compared the XML files in both cases and noticed that the below parameters are 
added when we select the OS as windows 2016. 










I guess this is expected because of the line "hypervEnabled = 
vmInfoBuildUtils.isHypervEnabled(vm.getVmOsId(), 
vm.getCompatibilityVersion());" in 
https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-4.3/backend/manager/modules/vdsbroker/src/main/java/org/ovirt/engine/core/vdsbroker/builder/vminfo/LibvirtVmXmlBuilder.java

However the question is why are the hyperv enlightenments causing a problem? 
The host details are as below:
Linux server01 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 23 11:18:01 PST 2021 
x86_64 x86_64 x86_64 GNU/Linux

 lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):96
On-line CPU(s) list:   0-95
Thread(s) per core:2
Core(s) per socket:24
Socket(s): 2
NUMA node(s):  2
Vendor ID: GenuineIntel
CPU family:6
Model: 85
Model name:Intel(R) Xeon(R) Platinum 8160 CPU @ 2.10GHz
Stepping:  4
CPU MHz:   2100.000
BogoMIPS:  4200.00
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  1024K
L3 cache:  33792K
NUMA node0 CPU(s): 0-23,48-71
NUMA node1 CPU(s): 24-47,72-95
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl 
vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic 
movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 
3dnowprefetch epb cat_l3 cdp_l3 invpcid_single intel_ppin intel_pt ssbd mba 
ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 
hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx 
smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 cqm_llc 
cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts hwp_epp pku 
ospke md_clear spec_ctrl intel_stibp flush_l1d

The CPU type in ovirt detects it as Intel Skylake-Server-noTSX-IBRS Family. We 
tried changing the cpu type for the VM to broadwell and other types to no 
effect. 

The ovirt version is 4.3.10.4-1.0.22.el7
___
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/5BKRP3PVXH7UW3Z736VURGDQGBWPH6WO/

[ovirt-users] Re: RHGS and RHV closing down: could you please put that on the home page?

2022-02-04 Thread Leo David

Maybe its a perfect time to add ( again ) Ceph into discution.

Leo


On Fri, Feb 4, 2022, 18:21 Thomas Hoberg  wrote:

> With Gluster gone, you could still use SAN and NFS storage, just like
> before they tried to compete with Nutanix and vSphere.
>
> Can you imagine IBM sponsoring oVirt, which doesn't make any money without
> RHV, which evidently isn't profitable enough?
>
> Most likely oVirt will lead RHV, in this case to the scrapyard, by months
> if not years.
> ___
> 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/T64IKY4DQUPQJXLRRBUCOOJ45FBRXM7Q/
>
___
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/GAWGUIQ7A36G6OPZDBCXNTCKAI3LJEXJ/

[ovirt-users] RHGS and RHV closing down: could you please put that on the home page?

I just read this message: https://bugzilla.redhat.com/show_bug.cgi?id=2016359

I am shocked but not surprised. And very, very sad.

But I believe this decision needs to be communicated more prominently, as 
people should not get aboard a project already axed.
___
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/RMWAAOUJXYPGWCEAHAESV6IHQWIF3CTI/

[ovirt-users] Re: RHGS and RHV closing down: could you please put that on the home page?

2022-02-04 Thread Derek Atkins

Hmm.
So if Gluster is being deprecated, what is it being replaced with?
Also, Nir did ask if this also applies to ovirt -- would be interesting to
see the response to that question.
-derek

On Fri, February 4, 2022 10:05 am, Thomas Hoberg wrote:
> I just read this message:
> https://bugzilla.redhat.com/show_bug.cgi?id=2016359
>
> I am shocked but not surprised. And very, very sad.
>
> But I believe this decision needs to be communicated more prominently, as
> people should not get aboard a project already axed.
> ___
> 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/RMWAAOUJXYPGWCEAHAESV6IHQWIF3CTI/
>


-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
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/4EQM34RRASBQITSHFONIGQJAMVEZVPXQ/

[ovirt-users] Re: RHGS and RHV closing down: could you please put that on the home page?

With Gluster gone, you could still use SAN and NFS storage, just like before 
they tried to compete with Nutanix and vSphere.

Can you imagine IBM sponsoring oVirt, which doesn't make any money without RHV, 
which evidently isn't profitable enough?

Most likely oVirt will lead RHV, in this case to the scrapyard, by months if 
not years.
___
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/T64IKY4DQUPQJXLRRBUCOOJ45FBRXM7Q/

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Fri, Feb 4, 2022 at 11:16 AM Richard W.M. Jones  wrote:
>
> On Fri, Feb 04, 2022 at 08:42:08AM +, Richard W.M. Jones wrote:
> > On Thu, Feb 03, 2022 at 06:31:52PM +0200, Nir Soffer wrote:
> > > This is expected on oVirt, our multipath configuration is intentionally 
> > > grabbing
> > > any device that multipath can work with, even if the device only has one 
> > > path.
> > > The motivation is to be able to configure a system when only one path is
> > > available (maybe you have an hba/network/server issue), and once the other
> > > paths are available the system will use them transparently.
> > >
> > > To avoid this issue with local devices, you need to blacklist the device.
> > >
> > > Add this file:
> > >
> > > $ cat /etc/multipath/conf.d/local.conf
> > > blacklist {
> > > wwid "QEMU HARDDISK"
> > > }
> >
> > Thanks - for the mailing list record the syntax that worked for me is:
> >
> > # cat /etc/multipath/conf.d/local.conf
> > blacklist {
> > wwid ".*QEMU_HARDDISK.*"
> > }
> >
> > > Configuring NFS on some other machine is easy.
> > >
> > > I'm using another VM for this, so I can easily test negative flows like 
> > > stopping
> > > or restarting the NFS server while it is being used by vms or storage
> > > operations.
> > > I'm using 2G alpine vm for this, it works fine even with 1G memory.
> >
> > I think I can get local storage working now (I had it working before).
>
> Well finally it fails with:
>
> 2022-02-04 09:14:55,779Z ERROR 
> [org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand] 
> (default task-2) [25a32edf] Command 
> 'org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand' 
> failed: EngineException: 
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
> VDSGenericException: VDSErrorException: Failed to CreateStorageDomainVDS, 
> error = Could not initialize cluster lock: (), code = 701 (Failed with error 
> unexpected and code 16)

The error "Could not initialize cluster lock" comes from vdsm. Usually
engine log is
not the best way to debug such failures. This is only the starting
point and you need to
go to the host and check vdsm and supervdsm logs in /var/log/vdsm/.
Since this error
comes from sanlock, we also may have useful info in /var/log/sanlock.log.

Can you share instructions on how to reproduce this issue?

> I think this feature (local storage) no longer works.

This is not local storage, local storage is a storage domain using a
local directory
on a host. This works only when creating a local data center,
basically each host
has its own data center.

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/SO6SUNKEIGGTJSOD4QQ7DSJ5667C45TZ/

[ovirt-users] Re: Ignore CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION ?

Actually the inability to mix CPU vendors is increasingly becoming an issue, 
and probably not just for me.

Of course this isn't an oVirt topic, not even a KVM-only topic, but reaches 
deep into the OS and even applications.

I guess Intel rather likes adding extensions and proprietary registers/flags as 
long as it plays in their favor, but with enough clouds and DCs going to EPYC 
that might flip on them one day.

And in terms of actual instruction support, there should be a rather larger 
intersection of true shared ISA between the two than the last true common 
ancestor (80486?) implies, which could be defined as abstract machine types by 
hypervisor vendors.

The other day I managed to trick a Ryzen 9 via a VMware configuration into 
appearing an Intel CPU well enough to run a Hackintosh that doesn't like AMD 
(CPUs), so it's a definite possibility.
___
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/32SDISBOT6NUQLB6VUCZIPLSMSYXAE6V/

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Fri, Feb 04, 2022 at 03:09:02PM +0200, Nir Soffer wrote:
> On Fri, Feb 4, 2022 at 11:16 AM Richard W.M. Jones  wrote:
> >
> > On Fri, Feb 04, 2022 at 08:42:08AM +, Richard W.M. Jones wrote:
> > > On Thu, Feb 03, 2022 at 06:31:52PM +0200, Nir Soffer wrote:
> > > > This is expected on oVirt, our multipath configuration is intentionally 
> > > > grabbing
> > > > any device that multipath can work with, even if the device only has 
> > > > one path.
> > > > The motivation is to be able to configure a system when only one path is
> > > > available (maybe you have an hba/network/server issue), and once the 
> > > > other
> > > > paths are available the system will use them transparently.
> > > >
> > > > To avoid this issue with local devices, you need to blacklist the 
> > > > device.
> > > >
> > > > Add this file:
> > > >
> > > > $ cat /etc/multipath/conf.d/local.conf
> > > > blacklist {
> > > > wwid "QEMU HARDDISK"
> > > > }
> > >
> > > Thanks - for the mailing list record the syntax that worked for me is:
> > >
> > > # cat /etc/multipath/conf.d/local.conf
> > > blacklist {
> > > wwid ".*QEMU_HARDDISK.*"
> > > }
> > >
> > > > Configuring NFS on some other machine is easy.
> > > >
> > > > I'm using another VM for this, so I can easily test negative flows like 
> > > > stopping
> > > > or restarting the NFS server while it is being used by vms or storage
> > > > operations.
> > > > I'm using 2G alpine vm for this, it works fine even with 1G memory.
> > >
> > > I think I can get local storage working now (I had it working before).
> >
> > Well finally it fails with:
> >
> > 2022-02-04 09:14:55,779Z ERROR 
> > [org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand] 
> > (default task-2) [25a32edf] Command 
> > 'org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand' 
> > failed: EngineException: 
> > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
> > VDSGenericException: VDSErrorException: Failed to CreateStorageDomainVDS, 
> > error = Could not initialize cluster lock: (), code = 701 (Failed with 
> > error unexpected and code 16)
> 
> The error "Could not initialize cluster lock" comes from vdsm. Usually
> engine log is
> not the best way to debug such failures. This is only the starting
> point and you need to
> go to the host and check vdsm and supervdsm logs in /var/log/vdsm/.

I can't really see anything relevant in supervdsm.log, it's all fairly
neutral debug messages.

> Since this error
> comes from sanlock, we also may have useful info in /var/log/sanlock.log.

Interesting:

2022-02-04 13:15:27 16723 [826]: open error -13 EACCES: no permission to open 
/rhev/data-center/mnt/_dev_sdb1/13a731d2-e1d2-4998-9b02-ac46899e3159/dom_md/ids
2022-02-04 13:15:27 16723 [826]: check that daemon user sanlock 179 group 
sanlock 179 has access to disk or file.

I think it's quite likely that the sanlock daemon does not have access
here, since (see below) I choown'd the root of the xfs filesystem to
36:36 (otherwise vdsm complains).

> Can you share instructions on how to reproduce this issue?

I have one engine and one node (both happen to be VMs, but I don't
believe that is relevant here).  It's running Version 4.4.10.6-1.el8.

I added a second disk to the node, and disabled multipath as
previously discussed.  The second disk is /dev/sdb1.  I formatted it
as xfs and chowned the root of the filesystem to 36:36.

In the admin portal, Storage -> Domains -> New domain

Storage type: Posix compliant fs

Name: ovirt-data

Path: /dev/sdb1

VFS type: xfs

Hit OK ->
Error while executing action AddPosixFsStorageDomain: Unexpected exception



> > I think this feature (local storage) no longer works.
> 
> This is not local storage, local storage is a storage domain using a
> local directory
> on a host. This works only when creating a local data center,
> basically each host
> has its own data center.
> 
> Nir

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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/CSKCHQVWWD7EW3A4HPA37RJTKACFATO6/

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Fri, Feb 4, 2022 at 3:18 PM Richard W.M. Jones  wrote:
>
> On Fri, Feb 04, 2022 at 03:09:02PM +0200, Nir Soffer wrote:
> > On Fri, Feb 4, 2022 at 11:16 AM Richard W.M. Jones  
> > wrote:
> > >
> > > On Fri, Feb 04, 2022 at 08:42:08AM +, Richard W.M. Jones wrote:
> > > > On Thu, Feb 03, 2022 at 06:31:52PM +0200, Nir Soffer wrote:
> > > > > This is expected on oVirt, our multipath configuration is 
> > > > > intentionally grabbing
> > > > > any device that multipath can work with, even if the device only has 
> > > > > one path.
> > > > > The motivation is to be able to configure a system when only one path 
> > > > > is
> > > > > available (maybe you have an hba/network/server issue), and once the 
> > > > > other
> > > > > paths are available the system will use them transparently.
> > > > >
> > > > > To avoid this issue with local devices, you need to blacklist the 
> > > > > device.
> > > > >
> > > > > Add this file:
> > > > >
> > > > > $ cat /etc/multipath/conf.d/local.conf
> > > > > blacklist {
> > > > > wwid "QEMU HARDDISK"
> > > > > }
> > > >
> > > > Thanks - for the mailing list record the syntax that worked for me is:
> > > >
> > > > # cat /etc/multipath/conf.d/local.conf
> > > > blacklist {
> > > > wwid ".*QEMU_HARDDISK.*"
> > > > }
> > > >
> > > > > Configuring NFS on some other machine is easy.
> > > > >
> > > > > I'm using another VM for this, so I can easily test negative flows 
> > > > > like stopping
> > > > > or restarting the NFS server while it is being used by vms or storage
> > > > > operations.
> > > > > I'm using 2G alpine vm for this, it works fine even with 1G memory.
> > > >
> > > > I think I can get local storage working now (I had it working before).
> > >
> > > Well finally it fails with:
> > >
> > > 2022-02-04 09:14:55,779Z ERROR 
> > > [org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand] 
> > > (default task-2) [25a32edf] Command 
> > > 'org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand' 
> > > failed: EngineException: 
> > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
> > > VDSGenericException: VDSErrorException: Failed to CreateStorageDomainVDS, 
> > > error = Could not initialize cluster lock: (), code = 701 (Failed with 
> > > error unexpected and code 16)
> >
> > The error "Could not initialize cluster lock" comes from vdsm. Usually
> > engine log is
> > not the best way to debug such failures. This is only the starting
> > point and you need to
> > go to the host and check vdsm and supervdsm logs in /var/log/vdsm/.
>
> I can't really see anything relevant in supervdsm.log, it's all fairly
> neutral debug messages.
>
> > Since this error
> > comes from sanlock, we also may have useful info in /var/log/sanlock.log.
>
> Interesting:
>
> 2022-02-04 13:15:27 16723 [826]: open error -13 EACCES: no permission to open 
> /rhev/data-center/mnt/_dev_sdb1/13a731d2-e1d2-4998-9b02-ac46899e3159/dom_md/ids
> 2022-02-04 13:15:27 16723 [826]: check that daemon user sanlock 179 group 
> sanlock 179 has access to disk or file.
>
> I think it's quite likely that the sanlock daemon does not have access
> here, since (see below) I choown'd the root of the xfs filesystem to
> 36:36 (otherwise vdsm complains).
>
> > Can you share instructions on how to reproduce this issue?
>
> I have one engine and one node (both happen to be VMs, but I don't
> believe that is relevant here).  It's running Version 4.4.10.6-1.el8.
>
> I added a second disk to the node, and disabled multipath as
> previously discussed.  The second disk is /dev/sdb1.  I formatted it
> as xfs and chowned the root of the filesystem to 36:36.

Looks right, forgetting to change ownership is a common mistake.

> In the admin portal, Storage -> Domains -> New domain
>
> Storage type: Posix compliant fs
>
> Name: ovirt-data
>
> Path: /dev/sdb1
>
> VFS type: xfs
>
> Hit OK ->
> Error while executing action AddPosixFsStorageDomain: Unexpected exception

I reproduce with vdsm-4.50.0.5-1.el8.x86_64. on RHEL 8.6 nightly.

Can you file a oVirt/vdsm bug for this?
___
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/TXPJHOTW4FN7FNLC3WHZP3H5DRKPGOWD/

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Fri, Feb 4, 2022 at 3:18 PM Richard W.M. Jones  wrote:
>
> On Fri, Feb 04, 2022 at 03:09:02PM +0200, Nir Soffer wrote:
> > On Fri, Feb 4, 2022 at 11:16 AM Richard W.M. Jones  
> > wrote:
> > >
> > > On Fri, Feb 04, 2022 at 08:42:08AM +, Richard W.M. Jones wrote:
> > > > On Thu, Feb 03, 2022 at 06:31:52PM +0200, Nir Soffer wrote:
> > > > > This is expected on oVirt, our multipath configuration is 
> > > > > intentionally grabbing
> > > > > any device that multipath can work with, even if the device only has 
> > > > > one path.
> > > > > The motivation is to be able to configure a system when only one path 
> > > > > is
> > > > > available (maybe you have an hba/network/server issue), and once the 
> > > > > other
> > > > > paths are available the system will use them transparently.
> > > > >
> > > > > To avoid this issue with local devices, you need to blacklist the 
> > > > > device.
> > > > >
> > > > > Add this file:
> > > > >
> > > > > $ cat /etc/multipath/conf.d/local.conf
> > > > > blacklist {
> > > > > wwid "QEMU HARDDISK"
> > > > > }
> > > >
> > > > Thanks - for the mailing list record the syntax that worked for me is:
> > > >
> > > > # cat /etc/multipath/conf.d/local.conf
> > > > blacklist {
> > > > wwid ".*QEMU_HARDDISK.*"
> > > > }
> > > >
> > > > > Configuring NFS on some other machine is easy.
> > > > >
> > > > > I'm using another VM for this, so I can easily test negative flows 
> > > > > like stopping
> > > > > or restarting the NFS server while it is being used by vms or storage
> > > > > operations.
> > > > > I'm using 2G alpine vm for this, it works fine even with 1G memory.
> > > >
> > > > I think I can get local storage working now (I had it working before).
> > >
> > > Well finally it fails with:
> > >
> > > 2022-02-04 09:14:55,779Z ERROR 
> > > [org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand] 
> > > (default task-2) [25a32edf] Command 
> > > 'org.ovirt.engine.core.bll.storage.domain.AddPosixFsStorageDomainCommand' 
> > > failed: EngineException: 
> > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
> > > VDSGenericException: VDSErrorException: Failed to CreateStorageDomainVDS, 
> > > error = Could not initialize cluster lock: (), code = 701 (Failed with 
> > > error unexpected and code 16)
> >
> > The error "Could not initialize cluster lock" comes from vdsm. Usually
> > engine log is
> > not the best way to debug such failures. This is only the starting
> > point and you need to
> > go to the host and check vdsm and supervdsm logs in /var/log/vdsm/.
>
> I can't really see anything relevant in supervdsm.log, it's all fairly
> neutral debug messages.
>
> > Since this error
> > comes from sanlock, we also may have useful info in /var/log/sanlock.log.
>
> Interesting:
>
> 2022-02-04 13:15:27 16723 [826]: open error -13 EACCES: no permission to open 
> /rhev/data-center/mnt/_dev_sdb1/13a731d2-e1d2-4998-9b02-ac46899e3159/dom_md/ids
> 2022-02-04 13:15:27 16723 [826]: check that daemon user sanlock 179 group 
> sanlock 179 has access to disk or file.

The issue is selinux:

NFS domain:

$ ls -lhZ 
/rhev/data-center/mnt/alpine\:_01/e9467633-ee31-4e15-b3f8-3812b374c764/dom_md/
total 2.3M
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s0 1.0M Feb  4 15:32 ids
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s0  16M Jan 20 23:53 inbox
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s0 2.0M Jan 20 23:54 leases
-rw-r--r--. 1 vdsm kvm system_u:object_r:nfs_t:s0  354 Jan 20 23:54 metadata
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s0  16M Jan 20 23:53 outbox
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s0 1.3M Jan 20 23:53 xleases

The posix domain mount (mounted manually):

$ ls -lhZ mnt/689c22c4-e264-4873-aa75-1aa4970d4366/dom_md/
total 252K
-rw-rw. 1 vdsm kvm system_u:object_r:unlabeled_t:s00 Feb  4 15:23 ids
-rw-rw. 1 vdsm kvm system_u:object_r:unlabeled_t:s0  16M Feb  4 15:23 inbox
-rw-rw. 1 vdsm kvm system_u:object_r:unlabeled_t:s00 Feb  4 15:23 leases
-rw-r--r--. 1 vdsm kvm system_u:object_r:unlabeled_t:s0  316 Feb  4
15:23 metadata
-rw-rw. 1 vdsm kvm system_u:object_r:unlabeled_t:s0  16M Feb  4 15:23 outbox
-rw-rw. 1 vdsm kvm system_u:object_r:unlabeled_t:s0 1.3M Feb  4
15:23 xleases

Can be fixed with:

$ sudo chcon -R -t nfs_t mnt

$ ls -lhZ mnt/689c22c4-e264-4873-aa75-1aa4970d4366/dom_md/
total 252K
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s00 Feb  4 15:23 ids
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s0  16M Feb  4 15:23 inbox
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s00 Feb  4 15:23 leases
-rw-r--r--. 1 vdsm kvm system_u:object_r:nfs_t:s0  316 Feb  4 15:23 metadata
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s0  16M Feb  4 15:23 outbox
-rw-rw. 1 vdsm kvm system_u:object_r:nfs_t:s0 1.3M Feb  4 15:23 xleases

After this change delete the storage domain directory:

$ rm -rf mnt/689c22c4-e264-4873-aa75-1aa4970d4366

Since vdsm will refuse to create a storage domain in a

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Fri, Feb 04, 2022 at 03:47:11PM +0200, Nir Soffer wrote:
> Can be fixed with:
> 
> $ sudo chcon -R -t nfs_t mnt

Yes that did work, thanks.

Is this still a bug?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
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/Q2E35J2MSA36DP3A5TJIKIMWJP4PM52D/

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Fri, Feb 4, 2022 at 3:49 PM Richard W.M. Jones  wrote:
>
> On Fri, Feb 04, 2022 at 03:47:11PM +0200, Nir Soffer wrote:
> > Can be fixed with:
> >
> > $ sudo chcon -R -t nfs_t mnt
>
> Yes that did work, thanks.
>
> Is this still a bug?

For NFS this works out of the box - I don't think you need to
relebal anything manually.

As a user I would expect that mounting posix file system will also work
out of the box. For example vdsm ca relabel the mount point when creating
a storage domain.

Also I'm not sure using nfs_t is the right label to use, we better discuss this
with selinux folks.

So I think this issue is worth a bug, in the worst case we will close
it, and the
bug will also document the workaround.

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/WUXD2DQ6DDCVOK2HNMEOHLJNRWXKWOE2/

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Fri, Feb 04, 2022 at 04:02:56PM +0200, Nir Soffer wrote:
> On Fri, Feb 4, 2022 at 3:49 PM Richard W.M. Jones  wrote:
> >
> > On Fri, Feb 04, 2022 at 03:47:11PM +0200, Nir Soffer wrote:
> > > Can be fixed with:
> > >
> > > $ sudo chcon -R -t nfs_t mnt
> >
> > Yes that did work, thanks.
> 
> Warning: that this configuration is a trap - if you add another host
> to this system,
> the system will try to mount the same device (/dev/sdb1) on the new
> host. Since the
> other host does not have the same disk, the mount will fail, and the
> other host will
> be deactivated, since it cannot access all storage.

Point taken!  This is only a test however.

Here's the bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2050721

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/5G7FB3DDW77WKVPLS2LL325RQHORG6WY/

[ovirt-users] Re: Erasure Coding Storage Support

It was this near endless range of possibilities via permutation of the parts
that originally attracted me to oVirt.

Being clearly a member of the original Lego generation I imagined how you could
simply add blocks of this and that to rebuild to something new fantastic...,
limitless gluster scaling and HCI, VDO dedup/compression, SSD caching, nested
virtualization, geo-replication, OVA support, it just had everything I might
want!

The truth is rather ugly from what I have gathered around here during almost
three years.

You don't mention it explicitly, but you evidently are talking about a HCI
setup, preferably installed, expanded and managed by the nice Cockpit/Engine
GUIs.

What I learned is that Gluster based HCI receives very little love from the
oVirt developers, even if it seems to you and me (Lego people?) the most
attractive option.

My impression is that they tend to work more with the original non-HCI approach
based on SAN or NFS storage, even if the engine may now by default be a VM,
when it was separate servers originally.

Gluster, VDO, Ansible, Java engine are all aquisitions, HCI more of a
management decision to counter Nutanix and I find that following the evolution
from Moshe Bar's Mosix to Qumranet and the Permabit, Ansible and Gluster
acquisitions as well as the competitor products helps understand why things are
as they are.

The current oVirt code base supports single node HCI, which delivers no
benefits beyond testing. It also supports 3 node HCI, which kind of works with
the Cockpit wizard (I have never succeeded with an installation where I didn't
have to do some fiddling).

Beyond that you already branch out into the jungle of not-tested,
not-supported, even if I remember reading that 6-nodes and 9-node HCI seem
possible. But quorums with 6 nodes don't seem natural and certainly nobody
would want to use replicas in a 9-node HCI setup, right?

I've seem actual "not supported" comments in the oVirt Ansible code that stops
any installation using dispersed volumes, so there is your immediate answer.
I've tricked it past that point editing Ansible scripts and actually got oVirt
running with dispersed (erasure coded) volumes on 5 nodes, but it felt too
wobbly for real use. Instead I've added the CPU/RAM parts of these 5 nodes to a
3 node HCI setup and then used the disks to create an erasure coded Gluster,
which then can be used by VMs via Gluster or NFS pretty much like a filer.

I can't recommend that unless you're willing to pay the price of being on your
own.

One major issue here is that you can't just create glusters and then merge them
as any system can only ever be a member of one gluster. And you have to destroy
volumes before moving to an other gluster: not sure how that rhymes with
bottleneck-free scalability.

And then there are various parts in oVirt, which look for quorums and find them
missing even when nodes aren't actually contributing bricks to a volume
(compute-only hosts or non-HCI volumes).

I guess it's safe to say that everybody here would like to see you trying and
feeding the changes required to make it work back into the project...

...but it's not "supported out of the box".

P.S. When I'm offered erasure coding, VDO dedup/compression and thin
allocation, I naturally tend to tick all boxes (originally I also chose SSD
cache, but quickly changed to SSD-only storage). It's only later when they
mention somewhere, that you aren't supposed to use them in combination, without
a full explanation or analysis to follow. Because even at today's SSD storage
pricing I need all the tricks in the book I stayed with them all, but Gluster
doesn't seem to be a speed devil, no matter what you put on top.

And to think that there used to be a UDMA/Infiniband option, that later
disappeared with little comment...

VMs in a 9-node HCI replica gluster could only ever get ~1Gbit/s throughput on
a 10Gbit/s network, so erasure coding should be the smart choice...
___
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/WQ3LKYCOSKVGYRCCSFW7FW72HHWKUWXB/

[ovirt-users] Re: Unclear how to add local (POSIX) storage

On Fri, Feb 4, 2022 at 3:49 PM Richard W.M. Jones  wrote:
>
> On Fri, Feb 04, 2022 at 03:47:11PM +0200, Nir Soffer wrote:
> > Can be fixed with:
> >
> > $ sudo chcon -R -t nfs_t mnt
>
> Yes that did work, thanks.

Warning: that this configuration is a trap - if you add another host
to this system,
the system will try to mount the same device (/dev/sdb1) on the new
host. Since the
other host does not have the same disk, the mount will fail, and the
other host will
be deactivated, since it cannot access all storage.

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/7BZBMO5TXNKLBXVGKAUHBGRJAS7VWUHS/

[ovirt-users] Re: Unclear how to add local (POSIX) storage