- Users - oVirt List Archives

Status of Snaphots and LVCache for VDO volumes in oVirt 4.3.x
by Guillaume Pavese 18 Feb '19

18 Feb '19

Hi, Currently choosing VDO at volume setup forces creation of a thick LV due to a RHEL bug, cf : https://bugzilla.redhat.com/show_bug.cgi?id=1634551 https://bugzilla.redhat.com/show_bug.cgi?id=1600156 The latter was closed while pointing to the following workaround : https://access.redhat.com/solutions/3562021 It is also said there that full fix will be available in RHEL-8 Thin LV are necessary to enable volume snapshots and LVCache, and are currently not possible on VDO volumes Does the above comments in BZs mean that it will still not be possible to configure Thin LV for VDO volumes with ovirt-4.3.x/Centos-7.X either? We have been postponing rolling out oVirt-4.2 in production because of these two major cons. Please advise if you think RHEL-8 will be necessary in order to have VDO volumes on par with normal volumes (snapshots and LVCache). In that case we will deploy production asap without VDO. Should we instead force the creation of VDO volmume on ThinLV by tweaking the gdeploy configuration and applying the mentionned workaround? Thanks Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

1 0

Status of Snaphots and LVCache for VDO volume in oVirt 4.3
by Guillaume Pavese 18 Feb '19

18 Feb '19

Hi, Currently choosing VDO at volume setup forces creation of a thick LV due to a RHEL bug, cf : https://bugzilla.redhat.com/show_bug.cgi?id=1634551 https://bugzilla.redhat.com/show_bug.cgi?id=1600156 The latter was closed while pointing to the following workaround : https://access.redhat.com/solutions/3562021 It is also said there that full fix will be available in RHEL-8 Thin LV are necessary to enable volume snapshots and LVCache, and are currently not possible on VDO volumes Does the above comments in BZs mean that it will still not be possible to configure Thin LV for VDO volumes with ovirt-4.3.x/Centos-7.X either? We have been postponing rolling out oVirt-4.2 in production because of these two major cons. Please advise if you think RHEL-8 will be necessary in order to have VDO volumes on par with normal volumes (snapshots and LVCache). In that case we will deploy production asap without VDO. Should we instead force the creation of VDO volmume on ThinLV by tweaking the gdeploy configuration and applying the mentionned workaround? Thanks Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

1 0

Re: Creating a static route
by Lev Veyde 18 Feb '19

18 Feb '19

Hi Doug, Sure, np. >> 1. - yes it is the priority setting of the specific rule. Basically you put in the file the post "ip rule add" part of the command e.g. for "ip rule add to 172.22.20.31 priority 32764" you need to put a line of "to 172.22.20.31 priority 32764" >> 2. - yes, the same priority can be used for all of them. E.g. if you want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to add: to 172.22.20.31 priority 32764 to 172.22.34.56 priority 32764 to 172.22.67.89 priority 32764 into the rule-<interface name> file e.g. rule-ovirtmgmt or rule-eno3. Please note that you will also need to add the static route for each one of these as well w/ "ip route add ... " command e.g. "ip route add 172.22.20.31 via 172.21.12.61". You can also use the route-<interface name> putting just the route info part, similar to the "ip rule" e.g. for equivalent of "ip route add 172.22.20.31 via 172.21.12.61" you need put in the file a line with the content "172.22.20.31 via 172.21.12.61". For routes it's important to use specifically the route-ovirtmgmt file since the script automatically adds the device to the route command i.e. you can put the following lines into your route-ovirtmgmt file: 172.22.20.31 via 172.21.12.61 172.22.34.56 via 172.21.12.61 172.22.67.89 via 172.21.12.68 (In case the first 2 of the mentioned IPs should be routed through the 172.21.12.61 gateway, and the last one should be routed through the 172.21.12.68 gateway). For the reference you can take a look at the /etc/sysconfig/network-scripts/ifup-routes script. It does the actual processing of both "route" and "rule" files for all network interfaces on a system. Please feel free to contact if you have further questions. Thanks in advance, On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield <Doug.L.Maxfield(a)emcins.com> wrote: > Lev, > > Thanks for the response. I was just getting ready to contact you about > this. I do have 2 follow-up questions, if you don’t mind. > > > > 1. When we were talking about creating the route that would be enabled > again after a reboot, you said to modify “the > /etc/sysconfig/network-scripts/rule-<interface name> e.g. rule-ovirtmgmt or > rule-eno3 (just put in the file "to 172.22.20.31 priority 32764”. Is > priority 32764 for the ip rule command? > 2. If I have multiple IPs that I would need to create a static route, > would the priority be 32764 for all of them? > > > > Once again, thank you for all of your help with this!! > > > > [image: Count On EMC] <http://www.emcins.com/> > > *Doug Maxfield *| Senior Operating Systems Analyst > > *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265 > Tel: 515.345.4507 | Fax: 866.331.1522 > Doug.L.Maxfield(a)EMCIns.com | www.emcins.com > > > > > > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* Thursday, February 14, 2019 3:19 AM > *To:* Doug Maxfield <Doug.L.Maxfield(a)EMCIns.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Creating a static route > > > > Hi Doug, > > Sorry that it took a bit of time to get back to you. > Managed to catch today somebody from the oVirt/RHV network team to discuss > the issue. > > It seems that we don't currently support custom static routes on the > hosts, so the workaround that I suggested is the way to do it. > > Thanks in advance, > > > > On Tue, Feb 12, 2019 at 11:12 PM Doug Maxfield <Doug.L.Maxfield(a)emcins.com> > wrote: > > Will do. Thanks again for all your help!! Looking forward to a > confirmation of the fix or a different solution. Either way, I know I have > a working fix. > > > > [image: Count On EMC] <http://www.emcins.com/> > > *Doug Maxfield *| Senior Operating Systems Analyst > > *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265 > Tel: 515.345.4507 | Fax: 866.331.1522 > Doug.L.Maxfield(a)EMCIns.com | www.emcins.com > > > > > > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* Tuesday, February 12, 2019 3:09 PM > *To:* Doug Maxfield <Doug.L.Maxfield(a)EMCIns.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Creating a static route > > > > Hi Doug, > > Just a small note - the commands in the rc.local should be placed *before* > the very last line (the touch ... command). > > Thanks in advance, > > > > On Tue, Feb 12, 2019 at 10:56 PM Lev Veyde <lveyde(a)redhat.com> wrote: > > Hi Doug, > > Thanks, you're welcome! > > It's generally possible to add persistent rules by either using the legacy > /etc/rc.d/rc.local boot script (chmod +x /etc/rc.d/rc.local and put the > relevant commands at the end of the file, that way you can actually run any > commands) or by using the /etc/sysconfig/network-scripts/rule-<interface > name> e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to > 172.22.20.31 priority 32764" - without quotes), however of course this > needs to be tested to verify that it works. > > I forwarded the issue to the network team and hopefully they will update > soon. > > > > Thanks in advance, > > > > On Tue, Feb 12, 2019 at 10:17 PM Doug Maxfield <Doug.L.Maxfield(a)emcins.com> > wrote: > > Lev, > > You have no idea how helpful you have been!!!!!! I’ve been having this > issue for over 2 months and starting to cause major problems. > > > > Please let me know if you find a better solution. I’m going to wait to > hear back from you before implementing. > > > > If we go with this workaround, is there a way to add the ip rule so it’s > persistent? I know how to make the ip route add persistent. > > > > [image: Count On EMC] <http://www.emcins.com/> > > *Doug Maxfield *| Senior Operating Systems Analyst > > *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265 > Tel: 515.345.4507 | Fax: 866.331.1522 > Doug.L.Maxfield(a)EMCIns.com | www.emcins.com > > > > > > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* Tuesday, February 12, 2019 2:14 PM > *To:* Doug Maxfield <Doug.L.Maxfield(a)EMCIns.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Creating a static route > > > > Hi Doug, > > Yes, it looks like it did. > > I'll try to catch somebody from my local oVirt/RHV networking team to take > a look at this issue, maybe there is a better solution for that issue than > my workaround. > > > > But meanwhile you can use this workaround (ip route add + ip rule add), > just please be aware that these should be run after each host reboot, since > these commands are not persistent. > > > > Thanks in advance, > > > > On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield <Doug.L.Maxfield(a)emcins.com> > wrote: > > Lev, > > Here’s the results. It appears to fix the issue!! > > > > From non-working system: > > > > -bash-4.2# ip rule add to 172.22.20.31 priority 32764 > > > > -bash-4.2# traceroute 172.22.20.31 > > traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets > > 1 CenteraAmesAN1.emcins.com (172.21.12.61) 0.487 ms 1.082 ms 1.313 ms > > 2 192.168.90.9 (192.168.90.9) 1.507 ms 2.090 ms 2.294 ms > > 3 pdputopcomm01.emcins.com (172.22.20.31) 1.403 ms 1.401 ms 1.348 ms > > > > [image: Count On EMC] <http://www.emcins.com/> > > *Doug Maxfield *| Senior Operating Systems Analyst > > *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265 > Tel: 515.345.4507 | Fax: 866.331.1522 > Doug.L.Maxfield(a)EMCIns.com | www.emcins.com > > > > > > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* Tuesday, February 12, 2019 2:01 PM > *To:* Doug Maxfield <Doug.L.Maxfield(a)EMCIns.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Creating a static route > > > > Hi Doug, > > OK, I think that I have a guess of what may have happened here... > > Can you please run the following command on the (non-working) host: > > ip rule add to 172.22.20.31 priority 32764 > > > > This needs to be run in addition to the ip route add ... command. > > > > And then please run the traceroute command and let me know if that fixed > the issue. > > > > Thanks in advance, > > > > On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield <Doug.L.Maxfield(a)emcins.com> > wrote: > > Lev, > > Here you go. > > > > From non-working system > > > > -bash-4.2# ip rule > > 0: from all lookup local > > 32764: from all to 172.21.0.0/16 iif ovirtmgmt lookup 2887058719 > > 32765: from 172.21.0.0/16 lookup 2887058719 > > 32766: from all lookup main > > 32767: from all lookup default > > > > > > From working system > > > > [root@paputopcomm04 ~]# ip rule > > 0: from all lookup local > > 32766: from all lookup main > > 32767: from all lookup default > > > > [image: Count On EMC] <http://www.emcins.com/> > > *Doug Maxfield *| Senior Operating Systems Analyst > > *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265 > Tel: 515.345.4507 | Fax: 866.331.1522 > Doug.L.Maxfield(a)EMCIns.com | www.emcins.com > > > > > > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* Tuesday, February 12, 2019 12:35 PM > *To:* Doug Maxfield <Doug.L.Maxfield(a)EMCIns.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Creating a static route > > > > Hi Doug, > > That shouldn't really matter, since ovirtmgmt is just a bridged interface, > and unless I'm missing something it shouldn't really affect routing. > > Can you please also provide the output of "ip rule" from both working and > non-working hosts ? > > > > Thanks in advance, > > > > On Tue, Feb 12, 2019 at 8:01 PM Doug Maxfield <Doug.L.Maxfield(a)emcins.com> > wrote: > > Lev, > > Here’s the ip route from the server that worked and didn’t work > > > > IP Route from server that worked > > > > [root@paputopcomm04 ~]# ip route > > default via 172.21.0.250 dev eno3 > > 169.254.0.0/16 dev eno3 scope link metric 1002 > > 169.254.0.0/16 dev eno4 scope link metric 1005 > > 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.18 > > 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34 > > *172.22.20.31 via 172.21.12.61 dev eno3* > > 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34 > > > > > > > > IP Route from server that didn't work > > > > -bash-4.2# ip route > > default via 172.21.0.250 dev ovirtmgmt > > 169.254.0.0/16 dev eno4 scope link metric 1004 > > 169.254.0.0/16 dev ovirtmgmt scope link metric 1021 > > 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.15 > > 172.21.0.0/16 dev ovirtmgmt proto kernel scope link src 172.21.5.31 > > *172.22.20.31 via 172.21.12.61 dev ovirtmgmt* > > 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.31 > > > > We have had our network team look and they don’t know. As I said, the was > setup by Commvault. It’s almost like the ovirtmgmt interface will not > allow a route add due to the way it’s configured? They, Commvault, are > trying different things within their software to get this working, but it’s > causing us more problems. I figured I would take a shot and see if > someone, who works with the oVirt software, would have any ideas. > > > > > > [image: Count On EMC] <http://www.emcins.com/> > > *Doug Maxfield *| Senior Operating Systems Analyst > > *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265 > Tel: 515.345.4507 | Fax: 866.331.1522 > Doug.L.Maxfield(a)EMCIns.com | www.emcins.com > > > > > > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* Tuesday, February 12, 2019 11:51 AM > *To:* Doug Maxfield <Doug.L.Maxfield(a)EMCIns.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Creating a static route > > > > Hi Doug, > > This is indeed quite weird... > > It looks like the OS for some reason disregards the static route that you > have added. > > BTW, have you verified that it's indeed was added by running "ip route" > following the "ip route add ..." command ? > > Maybe somebody from the network team has an idea of what may be the cause > of this issue... > > > > Thanks in advance, > > > > On Tue, Feb 12, 2019 at 7:36 PM Doug Maxfield <Doug.L.Maxfield(a)emcins.com> > wrote: > > Lev, > > I’m showing you the same outputs (ip a, ip route, traceroute, ip route > add, and traceroute) from another server in this group that doesn’t use the > ovirtmgmt for it’s default interface. > > > > [root@paputopcomm04 ~]# ip a > > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > inet 127.0.0.1/8 scope host lo > > valid_lft forever preferred_lft forever > > inet6 ::1/128 scope host > > valid_lft forever preferred_lft forever > > 2: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen > 1000 > > link/ether 90:1b:0e:db:bc:c0 brd ff:ff:ff:ff:ff:ff > > inet 172.21.5.34/16 brd 172.21.255.255 scope global eno3 > > valid_lft forever preferred_lft forever > > inet6 fe80::921b:eff:fedb:bcc0/64 scope link > > valid_lft forever preferred_lft forever > > 3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen > 1000 > > link/ether 90:1b:0e:e8:da:03 brd ff:ff:ff:ff:ff:ff > > inet 172.26.5.34/16 brd 172.26.255.255 scope global eno1 > > valid_lft forever preferred_lft forever > > inet6 fe80::921b:eff:fee8:da03/64 scope link > > valid_lft forever preferred_lft forever > > 4: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN > qlen 1000 > > link/ether 90:1b:0e:e8:da:04 brd ff:ff:ff:ff:ff:ff > > 5: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen > 1000 > > link/ether 90:1b:0e:db:bc:c1 brd ff:ff:ff:ff:ff:ff > > inet 172.17.53.18/16 brd 172.17.255.255 scope global eno4 > > valid_lft forever preferred_lft forever > > inet6 fe80::921b:eff:fedb:bcc1/64 scope link > > valid_lft forever preferred_lft forever > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# ip route > > default via 172.21.0.250 dev eno3 > > 169.254.0.0/16 dev eno3 scope link metric 1002 > > 169.254.0.0/16 dev eno4 scope link metric 1005 > > 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.18 > > 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34 > > 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34 > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# traceroute 172.22.20.31 > > traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets > > 1 ames-acc1-agg-1.emcins.com (172.21.0.246) 1.081 ms 1.816 ms 1.832 ms > > 2 192.168.200.30 (192.168.200.30) 0.639 ms 192.168.200.14 > (192.168.200.14) 1.063 ms 1.577 ms > > 3 192.168.200.101 (192.168.200.101) 3.110 ms ames-sw-wanrtr.emcins.com > (192.168.200.97) 3.191 ms 3.277 ms > > 4 192.168.100.26 (192.168.100.26) 4.146 ms 4.273 ms 4.394 ms > > 5 192.168.100.98 (192.168.100.98) 1.893 ms 2.364 ms 2.397 ms > > 6 192.168.100.50 (192.168.100.50) 5.707 ms 192.168.100.33 > (192.168.100.33) 5.134 ms 192.168.100.50 (192.168.100.50) 4.105 ms > > 7 pdputopcomm01.emcins.com (172.22.20.31) 1.359 ms 1.374 ms 1.351 ms > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# ip route add 172.22.20.31 via 172.21.12.61 > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# > > [root@paputopcomm04 ~]# traceroute 172.22.20.31 > > traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets > > 1 CenteraAmesAN1.emcins.com (172.21.12.61) 6.184 ms 6.475 ms 6.686 ms > > 2 192.168.90.9 (192.168.90.9) 1.770 ms 1.979 ms 2.189 ms > > 3 pdputopcomm01.emcins.com (172.22.20.31) 1.405 ms * 1.354 ms > > > > [image: Count On EMC] <http://www.emcins.com/> > > *Doug Maxfield *| Senior Operating Systems Analyst > > *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265 > Tel: 515.345.4507 | Fax: 866.331.1522 > Doug.L.Maxfield(a)EMCIns.com | www.emcins.com > > > > > > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* Tuesday, February 12, 2019 11:07 AM > *To:* Doug Maxfield <Doug.L.Maxfield(a)EMCIns.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Creating a static route > > > > Hi Doug, > > In most cases it should not be required, especially as my guess (again it > would be easier if you could post the output of the "ip a" and "ip route") > is that the eno1 is part of the ovirtmgmt bridge. > > What is the output of the "traceroute 172.22.20.31" that you get on the > host after you have added the static route? > > Thanks in advance, > > > > > > On Tue, Feb 12, 2019 at 6:58 PM Doug Maxfield <Doug.L.Maxfield(a)emcins.com> > wrote: > > Lev, > > One other question, since there are multiple enabled interfaces (ovirtmgmt > and eno1), do I need to specify an interface for the route add. > > > > [image: Count On EMC] <http://www.emcins.com/> > > *Doug Maxfield *| Senior Operating Systems Analyst > > *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265 > Tel: 515.345.4507 | Fax: 866.331.1522 > Doug.L.Maxfield(a)EMCIns.com | www.emcins.com > > > > > > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* Tuesday, February 12, 2019 10:50 AM > *To:* Doug Maxfield <Doug.L.Maxfield(a)EMCIns.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Creating a static route > > > > Hi Doug, > > What do you mean by "static route is refused"? > > What is the error message(s) you see? > > > > Can you please try to add the route with the following command: > > ip route add 172.22.20.31 via 172.21.12.61 > > > > If that doesn't work, then please provide more details, i.e. what is the > exact error message(s) you see, the version of your OS and oVirt, output of > "ip a" and "ip route" on your host(s), so that it will be easier to help > you. > > > > Thanks in advance, > > > > On Tue, Feb 12, 2019 at 6:43 PM Doug Maxfield <Doug.L.Maxfield(a)emcins.com> > wrote: > > Lev, > > Thanks for your response. > > > > If I attempt to manually add the route using route add: > > > > route add -net 172.22.20.31 netmask 255.255.255.255 gw 172.21.12.61 dev > ovirtmgmt > > > > This static route is refused and all traffic is routed over the default > gateway. > > > > But if I use a server that doesn’t use the ovirtmgmt interface and set the > same static route, the required data is routed correctly over that static > route. > > > > [image: Count On EMC] <http://www.emcins.com/> > > *Doug Maxfield *| Senior Operating Systems Analyst > > *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265 > Tel: 515.345.4507 | Fax: 866.331.1522 > Doug.L.Maxfield(a)EMCIns.com | www.emcins.com > > > > > > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* Tuesday, February 12, 2019 10:34 AM > *To:* Doug Maxfield <Doug.L.Maxfield(a)EMCIns.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Creating a static route > > > > Hi Doug, > > What is the exact problem you are having while attempting to add a static > route on the hosts? > > > > Thanks in advance, > > > > On Tue, Feb 12, 2019 at 5:23 PM <doug.l.maxfield(a)emcins.com> wrote: > > Good Morning, > New to oVirt. We are using this with a backup solution from Commvault. > The issue that we are having is that we need to setup a static route for > specific data between 2 remote sites. The ovirtmgmt is configured with the > correct IP and gateway for the server. We need to route data over a > different gateway so that we don't "max out" the default network connection > between the 2 sites. Example below > > Ovirtmgmt IP - 172.21.5.31 > Gateway IP - 172.21.0.250 > > We need any traffic with a destination of 172.22.20.31(Remote site) to > route over this gateway, 172.21.12.61 > > There are multiple servers in this configuration. Servers that are not > using the ovirtmgmt interface for their default, we are able to route the > data. The only problem is with attempting to setup a different static > route on the ovirtmgmt interfaces. > > Thanks in advance for any help!!! > > Doug > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/WGXSLHAP3X5OT… > > > > -- > > > > *Lev Veyde* > > 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> > > > NOTICE: This message (including any attachments) is intended for a > specific individual and may contain information that is either confidential > or legally protected. If you believe that it has been sent to you in > error, please reply to the sender that you have received the message in > error, then delete it. If you are not the intended recipient, you are > hereby notified that any retention, dissemination, distribution, or copying > of this communication is strictly prohibited. Thank you. EMC071856 > > > > -- > > > > *Lev Veyde* > > 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> > > > > -- > > > > *Lev Veyde* > > 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> > > > > -- > > > > *Lev Veyde* > > 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> > > > > -- > > > > *Lev Veyde* > > 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> > > > > -- > > > > *Lev Veyde* > > 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> > > > > -- > > > > *Lev Veyde* > > 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> > > > > -- > > > > *Lev Veyde* > > 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> > > > > -- > > > > *Lev Veyde* > > 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> > > > > -- > > > > *Lev Veyde* > > 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> > -- Lev Veyde 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>

2 2

Re: After import storage many of my vm's disks not appear
by Eyal Edri 18 Feb '19

18 Feb '19

On Mon, Feb 18, 2019 at 5:41 PM Kalil de A. Carvalho <kalilac(a)gmail.com> wrote: > Hello all. > It is been a while that I used the oVirt and on the same time, the company > where I started to work, has a big problem with the engine, we lose it. We > did not have any backup. > To try recovery the enverioment I installed a knew oVirt, this time Hosted > Engine, and import the Storage. I could import and start some vm's but the > most part not appear for me, dosen't show on "Disk Import", "VM Import" and > any place. > I know that is there, because show me that size. > May I see, like list, this disks? I can't do this throught oVirt web. > Is there any way to bring dist disks back? > I already search this tasks but with no luck. > > oVirt ver: 4.2.8.2-1.el7 > > Any one can help, please? > Best regards. > > -- > Atenciosamente, > Kalil de A. Carvalho > > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/64GREELIVLICG… > -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

After import storage many of my vm's disks not appear
by Kalil de A. Carvalho 18 Feb '19

18 Feb '19

Hello all. It is been a while that I used the oVirt and on the same time, the company where I started to work, has a big problem with the engine, we lose it. We did not have any backup. To try recovery the enverioment I installed a knew oVirt, this time Hosted Engine, and import the Storage. I could import and start some vm's but the most part not appear for me, dosen't show on "Disk Import", "VM Import" and any place. I know that is there, because show me that size. May I see, like list, this disks? I can't do this throught oVirt web. Is there any way to bring dist disks back? I already search this tasks but with no luck. oVirt ver: 4.2.8.2-1.el7 Any one can help, please? Best regards. -- Atenciosamente, Kalil de A. Carvalho

1 0

SURVEY: your NFS configuration (Bug 1666795 - SHE doesn't start after power-off, 4.1 to 4.3 upgrade - VolumeDoesNotExist: Volume does not exist )
by Nir Soffer 18 Feb '19

18 Feb '19

Looking at https://bugzilla.redhat.com/1666795 It seems that a change in vdsm/libvirt exposed NFS configuration issue, that may was needed in the past and probably not needed now. If you use NFS, I would like to see your /etc/exports (after sanitizing it if needed). For extra bonus, output of "exportfs -v" would be useful. In particular, I want to know if you use root_squash, all_squash, or no_root_squash. Thanks, Nir

6 5

How to set hot plugged memory online_movable
by zodaoko＠gmail.com 18 Feb '19

18 Feb '19

Hi, I'd like to try the memory hot unplug, refer to: https://www.ovirt.org/documentation/vmm-guide/chap-Editing_Virtual_Machines…: "All blocks of the hot-plugged memory must be set to **online_movable** in the virtual machine’s device management rules. In virtual machines running up-to-date versions of Enterprise Linux or CoreOS, this rule is set by default." I created a VM running CentOS7.6: # more /etc/redhat-release CentOS Linux release 7.6.1810 (Core) # more /usr/lib/udev/rules.d/40-redhat.rules ... # Memory hotadd request SUBSYSTEM!="memory", ACTION!="add", GOTO="memory_hotplug_end" PROGRAM="/bin/uname -p", RESULT=="s390*", GOTO="memory_hotplug_end" ENV{.state}="online" PROGRAM="/bin/systemd-detect-virt", RESULT=="none", ENV{.state}="online_movable" ATTR{state}=="offline", ATTR{state}="$env{.state}" LABEL="memory_hotplug_end" It looks like the online_movable will be set only when systemd-detect-virt returns none, i.e. hot plugging memory for a bare-metal machine, so how to make the hot plugged memory "online_movable" in the virtual machines? Thank you. Regards, -Zhen

2 1

changes in oVirt 4.3 and vGPU?
by Hetz Ben Hamo 18 Feb '19

18 Feb '19

Hi, I just installed a Tesla T4 card, installed the nvidia's RPM, I see the mdev_type stuff etc. Following their instructions, I'm trying to set a Windows 10 VM to use the vGPU (the VM works without any vGPU), I get this error in the event... VM Win-10-test is down with error. Exit message: internal error: qemu unexpectedly closed the monitor: 2019-02-08T14:01:11.287955Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NUMA mappings is obsoleted and will be removed in future 2019-02-08T14:01:11.313878Z qemu-kvm: -device vfio-pci,id=hostdev0,sysfsdev=/sys/bus/mdev/devices/486b48a3-01c7-4a67-9727-279813bae0e8,display=off,bus=pci.0,addr=0x8: vfio error: 486b48a3-01c7-4a67-9727-279813bae0e8: error getting device from group 0: Input/output error Verify all devices in group 0 are bound to vfio-<bus> or pci-stub and not already in use. Could someone explain to me what am I missing and what to do? I don't see any docs about it. Thanks

4 4

Migration of VMs across two Ovirt setups
by ddc.comp＠gmail.com 18 Feb '19

18 Feb '19

Hi, I have two ovirt setups having multiple hosts and cluster and around 100+ vms in one and around 32 in one setup. I want to dismantle one setup and before before doing so all vms are need to be migrated to one setup I tried with import vms from another setup using Libvert -- https://ovirt.org/develop/release-management/features/virt/KvmToOvirt.html but no luck connection not getting established. What if I simply remove one host from one setup having local storage(all vms are located on local storage) and simply add it to another setup? and then migrate VMs from local to shared storage and then dismantle host ! Regards Dipak Chaudhari

2 1

AMD EPYC 4.3 upgrade 'CPU type is not supported in this cluster compatibility version or is not supported at all'
by Ryan Bullock 18 Feb '19

18 Feb '19

We just updated our engine to 4.3, but when I tried to update one of our AMD EPYC hosts it could not activate with the error: Host vmc2h2 moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all. Relevant (I think) parts from the the engine log: (EE-ManagedThreadFactory-engineScheduled-Thread-82) [ee51a70] Could not find server cpu for server 'vmc2h2' (745a14c6-9d31-48a4-9566-914647d83f53), flags: 'fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,pdpe1gb,rdtscp,lm,constant_tsc,art,rep_good,nopl,nonstop_tsc,extd_apicid,amd_dcm,aperfmperf,eagerfpu,pni,pclmulqdq,monitor,ssse3,fma,cx16,sse4_1,sse4_2,movbe,popcnt,aes,xsave,avx,f16c,rdrand,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,skinit,wdt,tce,topoext,perfctr_core,perfctr_nb,bpext,perfctr_l2,cpb,hw_pstate,sme,retpoline_amd,ssbd,ibpb,vmmcall,fsgsbase,bmi1,avx2,smep,bmi2,rdseed,adx,smap,clflushopt,sha_ni,xsaveopt,xsavec,xgetbv1,clzero,irperf,xsaveerptr,arat,npt,lbrv,svm_lock,nrip_save,tsc_scale,vmcb_clean,flushbyasid,decodeassists,pausefilter,pfthreshold,avic,v_vmsave_vmload,vgif,overflow_recov,succor,smca' 2019-02-06 17:23:58,527-08 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-82) [7f6d4f0d] START, SetVdsStatusVDSCommand(HostName = vmc2h2, SetVdsStatusVDSCommandParameters:{hostId='745a14c6-9d31-48a4-9566-914647d83f53', status='NonOperational', nonOperationalReason='CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER' From virsh -r capabilities: <cpu> <arch>x86_64</arch> <model>EPYC-IBPB</model> <vendor>AMD</vendor> <microcode version='134222375'/> <topology sockets='1' cores='32' threads='2'/> <feature name='ht'/> <feature name='osxsave'/> <feature name='xsaves'/> <feature name='cmp_legacy'/> <feature name='extapic'/> <feature name='skinit'/> <feature name='wdt'/> <feature name='tce'/> <feature name='topoext'/> <feature name='perfctr_core'/> <feature name='perfctr_nb'/> <feature name='invtsc'/> <pages unit='KiB' size='4'/> <pages unit='KiB' size='2048'/> <pages unit='KiB' size='1048576'/> </cpu> I also tried creating a new 4.3 cluster, set to the AMD EPYC IPBDB SSBD and moving the host into it, but it failed to move it into that cluster with a similar error about an unsupported CPU (for some reason it also made me clear the additional kernel options as well, we use 1gb hugepages). I have not yet tried removing the host entirely and adding it as part of creating the new cluster. We have been/are using a database change to update the 4.2 cluster level to include EPYC support with the following entries (can post the whole query if needed): 7:AMD EPYC:svm,nx,model_EPYC:EPYC:x86_64; 8:AMD EPYC IBPB:svm,nx,ibpb,model_EPYC:EPYC-IBPB:x86_64 We have been running 4.2 with this for awhile. We did apply the same changes after the 4.3 update, but only for the 4.2 cluster level. We only used the AMD EPYC IBPB model. Reverting the host back to 4.2 allows it to activate and run normally. Anyone have any ideas as to why it can't seem to find the cpu type? Thanks, Ryan Bullock

5 16