[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-27 Thread Mark R
Replying to my own post here, I've verified that it's currently not possible to do a greenfield deploy of oVirt 4.4.0 w/ hosted engine on EPYC CPUs due to the system setting a requirement of 'virt-ssbd' for the final HE definition after the move to shared storage. The local HE runs perfectly

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-28 Thread Mark R
Oof, I butchered his last name, but the quote I found was this: "Details: Tom Lendacky from AMD writes[4] -- "The idea behind 'virt-ssbd' was to provide an architectural method for a guest to do SSBD when 'amd-ssbd' isn't present. The 'amd-ssbd' feature will use SPEC_CTRL which

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-28 Thread Mark R
I should have also mentioned that I found an existing report for the issue I'm having on RedHat's Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1783180 Mark ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-28 Thread Mark R
Hi Lucia, >>> the cluster is set to use the secure variant of the CPU type but your host does not support all the necessary flags. For my deployments the system is auto-detecting and using the 'Secure AMD EPYC' CPU type. Note that the HostedEngineLocal VM does run with 'amd-ssbd' and works

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-29 Thread Mark R
Thank you Lucia, that's good news to hear. Is this something that might be fixed up in the 4.4.1 release whenever it comes along, and/or something simple to patch to get a clean deploy using 4.4.0? I have the servers and time to experiment with for now. If I can somehow edit that '4:Secure

[ovirt-users] Issues deploying 4.4 with HE on new EPYC hosts

2020-05-26 Thread Mark R
Hello all, I have some EPYC servers that are not yet in production, so I wanted to go ahead and move them off of 4.3 (which was working) to 4.4. I flattened and reinstalled the hosts with CentOS 8.1 Minimal and installed all updates. Some very simple networking, just a bond and two iSCSI

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-26 Thread Mark R
Thank you for the suggestion, Ryan it looks like AVIC is disabled by default though (/sys/module/kvm_amd/parameters/avic is 0). ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:

[ovirt-users] Re: New oVirt Install - Host Engine Deployment Fails

2020-09-18 Thread Mark R
Just to chime in here, trying a fresh hosted engine deploy today on AMD EPYC servers, the exact same error kills the deploy. So it's not you or your CPUs/servers, there's a bug in the Ansible routine that was introduced with 4.4.2 that makes hosted engine deployment impossible. I was able to

[ovirt-users] iSCSI multipath with separate subnets... still not possible in 4.4.x?

2020-07-13 Thread Mark R
I'm looking through quite a few bug reports and mailing list threads, but want to make sure I'm not missing some recent development. It appears that doing iSCSI with two separate, non-routed subnets is still not possible with 4.4.x. I have the dead-standard iSCSI setup with two separate

[ovirt-users] Re: status of oVirt 4.4.x and CentOS 8.2

2020-06-30 Thread Mark R
Hello Ales, The nmstate and NetworkManager versions are as follows, installed from repos that are added while installing oVirt/HE: Name : nmstate Version : 0.2.10 Release : 1.el8 Architecture : noarch Size : 32 k Repository : @System From repo:

[ovirt-users] Re: status of oVirt 4.4.x and CentOS 8.2

2020-06-19 Thread Mark R
The error with a bit more info from the events page, after adding network to an interface fails: VDSM rack4slot11.domain.com command HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': 'Unexpected failure of libnm when running the mainloop: run execution'} Sorry, should have

[ovirt-users] Re: status of oVirt 4.4.x and CentOS 8.2

2020-06-19 Thread Mark R
Hi Michal, Might the openvswitch issues you mention be tied to the issue I'm having standing up a new 4.4 installation on 8.2, namely that you can create a network in the UI, but when you go to apply/attach it to a host (using the drag-and-drop wizard to try to add a new network onto the same

[ovirt-users] Re: status of oVirt 4.4.x and CentOS 8.2

2020-06-23 Thread Mark R
Hi Dominik, My apologies for the delay, have been pushed to other projects this week. I just verified that our CentOS 8.2 and oVirt 4.4.0 installs are fully up to date, and tried to apply a network configuration adding a tagged VLAN to the same bridge as ovirtmgmt. Here are the logs: ```

[ovirt-users] Re: status of oVirt 4.4.x and CentOS 8.2

2020-06-23 Thread Mark R
Follow up, as well as the logged error from supervdsm.log, I see this in dmesg so it appears that it very briefly does create DMZ0 and the bond0.22 interface, but rolls everything back. ``` [ 2205.551920] IPv6: ADDRCONF(NETDEV_UP): DMZ0: link is not ready [ 2205.558366] IPv6:

[ovirt-users] Re: 4.4.x - VLAN-based logical network can't attach to bonds?

2020-07-24 Thread Mark R
> Can you please create a bug > for oVirt with > reproduction steps? > Created https://bugzilla.redhat.com/show_bug.cgi?id=1860479 ___ Users mailing list -- users@ovirt.org To unsubscribe send

[ovirt-users] Re: 4.4.x - VLAN-based logical network can't attach to bonds?

2020-07-24 Thread Mark R
Hi Dominik, > Can you please create a bug > for oVirt with > reproduction steps? Yes, I'll do so. Rebuilding the host fresh now so I have a clean slate as I go through the steps for the report. I did try NM 1.26 from the COPR repo you

[ovirt-users] Re: 4.4.x - VLAN-based logical network can't attach to bonds?

2020-07-23 Thread Mark R
Hello Ales, > can you please share supervdsm.log from the relevant host? Absolutely! Here is the log from the point of opening the "Setup Host Networks" UI, as I just drag the "LegacyDMZ" network over onto the same bond that's running ovirtmgmt and click "OK".

[ovirt-users] 4.4.x - VLAN-based logical network can't attach to bonds?

2020-07-22 Thread Mark R
Hello all, New 4.4.1 hosted-engine install. Pre-deploy, the host already had bond0 and its iSCSI interfaces configured. The deploy correctly sets up the ovirtmgmt interface using the bond, and when everything finishes up it's working as expected. However, I then need to create a VLAN-based

[ovirt-users] Re: iSCSI multipath with separate subnets... still not possible in 4.4.x?

2020-07-22 Thread Mark R
> I don't use them as multipathing generally works without OVirt bonds in > my setup, I configured multipathd directly to use round robin e.g. Thanks, Uwe. Am I understanding correctly that you're just letting your nodes attach to the iSCSI storage on their own by leaving "node.startup =

[ovirt-users] Re: 4.4.x - VLAN-based logical network can't attach to bonds?

2020-07-30 Thread Mark R
Following up, as noted in the bug report ( https://bugzilla.redhat.com/show_bug.cgi?id=1860479 ) this doesn't appear to be oVirt / VDSM having issues. You can replicate the same inability to attach a bond to a bridge by simply booting the 8.2.2004 installation media and trying a few manual