[ovirt-users] Wrong CPU performance report

[Hetz Ben Hamo]

Hi,

I'm running oVirt 4.2.7.1. I installed Windows 10 pro as a guest, along
with QXL and all the drivers, as well as QEMU guest agent.

While Windows reports a CPU usage of something like 2-4% when idle, oVirt
reports 24-27% CPU usage.

Bug? should I report it?

Thanks
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/OJMAVROXJOSJ2B33BZ5XFJ2QGHONM65Z/

[ovirt-users] Ovirt 4.3 RC missing glusterfs-gnfs

[Strahil]

Hi guys,I think you know that, but 'glusterfs-gnfs' package has no package for gluster v5 and blocks the upgrade.I have noticed that 'glusterfs-gnfs' depends on vdsm-gluster , so the whole thing is causing a mess.Best Regards,Strahil Nikolov___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IKBSM4LW3KVLY4RKMMFAMR64GZ43JIW3/

[ovirt-users] Re: Ovirt 4.3 RC missing glusterfs-gnfs

[Greg Sheremeta]

Please open a bug.
https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt

Best wishes,
Greg

On Sun, Feb 3, 2019 at 6:35 PM Strahil  wrote:

> Hi guys,
>
> I think you know that, but 'glusterfs-gnfs' package has no package for
> gluster v5 and blocks the upgrade.
> I have noticed that 'glusterfs-gnfs' depends on vdsm-gluster , so the
> whole thing is causing a mess.
>
> Best Regards,
> Strahil Nikolov
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/IKBSM4LW3KVLY4RKMMFAMR64GZ43JIW3/
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6PFB73XWDEHDI5KXW4HLTUZ3NK5YNSHZ/

[ovirt-users] Re: routing/firewalling problems (was: oVirt can't communicate with vSphere)

[Yedidyah Bar David]

On Sat, Feb 2, 2019 at 7:34 PM Benjamin Selinger  wrote:
>
> No. As I said, ICMP is routed through correctly without any issue. The 
> routing is correct, and the machine at 1.13 is definitely forwarding requests 
> correctly. I've tested from another machine on my LAN, same setup except not 
> running Centos/ovirt and it's got no problem with communication.
> Telnet from 1.195 never leaves the node,

As in, does not reach the gateway/vpn? Did you sniff traffic on the
node and the gateway to verify?

Please check/share iptables/firewalld config on the node, if you
suspect that it's blocking outgoing traffic (but I do not think
ovirt-node ever does this by default).

IMO it should not be hard to make iptables on the node log all blocks,
but I didn't try this recently (or at all, with firewalld).

> and never hits 1.13. I can successfully hit the 10.0.0.0/8 network from any 
> other machine on my network.
>
> I reinstalled the cluster (for various reasons) yesterday, using the 
> ovirt-node installer, and same issue. I dunno if I'm just derping out, but I 
> can't see where it's being blocked.

I'd suggest to sniff traffic in all relevant places and try to
identify the box that does not forward correctly. Then we can start
diagnosing why it does not.

Best regards,
-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7E6GAPO3D7Z275O2MYT3NU4D7KVPWYZV/

[ovirt-users] Re: rebooting an ovirt cluster

[feral]

So why is this the default behavior of the ovirt Node distro?

On Sun, Feb 3, 2019 at 5:16 PM Strahil  wrote:

>
> 2. Reboot all nodes. I was testing for power outage response. All nodes
> come up, but glusterd is not running (seems to have failed for some
> reason). I can manually restart glusterd on all nodes and it comes up and
> starts communicating normally. However, the engine does not come online. So
> I figure out where it last lived, and try to start it manually through the
> web interface. This fails because vdsm-ovirtmgmt is not up. I figured out
> the correct way to start up the engine would be through the cli via
> hosted-engine --vm-start. This does work, but it takes a very long time,
> and it usually starts up on any node other than the one I told it to start
> on.
>
> If you use fstab - prepare for pain... Systemd mounts are more effective.
> Here is a sample:
>
> [root@ovirt1 ~]# systemctl cat gluster_bricks-engine.mount
> # /etc/systemd/system/gluster_bricks-engine.mount
> [Unit]
> Description=Mount glusterfs brick - ENGINE
> Requires = vdo.service
> After = vdo.service
> Before = glusterd.service
> Conflicts = umount.target
>
> [Mount]
> What=/dev/mapper/gluster_vg_md0-gluster_lv_engine
> Where=/gluster_bricks/engine
> Type=xfs
> Options=inode64,noatime,nodiratime
>
> [Install]
> WantedBy=glusterd.service
>
> [root@ovirt1 ~]# systemctl cat glusterd.service
> # /etc/systemd/system/glusterd.service
> [Unit]
> Description=GlusterFS, a clustered file-system server
> Requires=rpcbind.service gluster_bricks-engine.mount
> gluster_bricks-data.mount
> After=network.target rpcbind.service gluster_bricks-engine.mount
> Before=network-online.target
>
> [Service]
> Type=forking
> PIDFile=/var/run/glusterd.pid
> LimitNOFILE=65536
> Environment="LOG_LEVEL=INFO"
> EnvironmentFile=-/etc/sysconfig/glusterd
> ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid  --log-level
> $LOG_LEVELKillMode=process
> SuccessExitStatus=15
>
> [Install]
> WantedBy=multi-user.target
>
> # /etc/systemd/system/glusterd.service.d/99-cpu.conf
> [Service]
> CPUAccounting=yes
> Slice=glusterfs.slice
>
>
> Note : Some of the 'After=' and 'Requires='  entries were removed during
> copy-pasting.
>
> So I guess two (or three) questions. What is the expected operation after
> a full cluster reboot (ie: in the event of a power failure)? Why doesn't
> the engine start automatically, and what might be causing glusterd to fail,
> when it can be restarted manually and works fine?
>
>
>
> Expected -everything to be up and running.
> Root cause , the system's fstab generator starts after cluster tries to
> start the bricks - and of course fails.
> Then everything on the chain fails.
>
> Just use systemd's mount entries ( I have added automount also)  and you
> won't have such issues.
>
> Best Regards,
> Strahil Nikolov
>


-- 
_
Fact:
1. Ninjas are mammals.
2. Ninjas fight ALL the time.
3. The purpose of the ninja is to flip out and kill people.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ZHCHWBBC2MB2UZYWIZH7UF2IQZOUKA7Q/

[ovirt-users] Re: Ovirt 4.3 RC missing glusterfs-gnfs

[Strahil]

I'd love to, but the person who has created the submenus definitely didn't expect new users to file a bug.I have checked at least 3 submenus and I still cannot catch the logic.Can someone tell me what submenu should be picked for glusterfs-gnfs ?Best Regards,Strahil NikolovOn Feb 4, 2019 02:15, Greg Sheremeta  wrote:Please open a bug.https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirtBest wishes,GregOn Sun, Feb 3, 2019 at 6:35 PM Strahil  wrote:Hi guys,I think you know that, but 'glusterfs-gnfs' package has no package for gluster v5 and blocks the upgrade.I have noticed that 'glusterfs-gnfs' depends on vdsm-gluster , so the whole thing is causing a mess.Best Regards,Strahil Nikolov___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/IKBSM4LW3KVLY4RKMMFAMR64GZ43JIW3/
-- GREG SHEREMETASENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UXRed Hat NAgshereme@redhat.com    IRC: gshereme
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/CWUINENYZEOLLDHTGEYKKBGUOH6N4G4Y/

[ovirt-users] Re: rebooting an ovirt cluster

[Strahil]

That's a good question... Yet, I'm new in oVirt - so I can't say for sure. I can even be wrong.Best Regards,Strahil NikolovOn Feb 4, 2019 03:45, feral  wrote:So why is this the default behavior of the ovirt Node distro?On Sun, Feb 3, 2019 at 5:16 PM Strahil  wrote:2. Reboot all nodes. I was testing for power outage response. All nodes come up, but glusterd is not running (seems to have failed for some reason). I can manually restart glusterd on all nodes and it comes up and starts communicating normally. However, the engine does not come online. So I figure out where it last lived, and try to start it manually through the web interface. This fails because vdsm-ovirtmgmt is not up. I figured out the correct way to start up the engine would be through the cli via hosted-engine --vm-start. This does work, but it takes a very long time, and it usually starts up on any node other than the one I told it to start on.If you use fstab - prepare for pain... Systemd mounts are more effective.Here is a sample:[root@ovirt1 ~]# systemctl cat gluster_bricks-engine.mount# /etc/systemd/system/gluster_bricks-engine.mount[Unit]Description=Mount glusterfs brick - ENGINERequires = vdo.serviceAfter = vdo.serviceBefore = glusterd.serviceConflicts = umount.target[Mount]What=/dev/mapper/gluster_vg_md0-gluster_lv_engineWhere=/gluster_bricks/engineType=xfsOptions=inode64,noatime,nodiratime[Install]WantedBy=glusterd.service[root@ovirt1 ~]# systemctl cat glusterd.service# /etc/systemd/system/glusterd.service[Unit]Description=GlusterFS, a clustered file-system serverRequires=rpcbind.service gluster_bricks-engine.mount gluster_bricks-data.mountAfter=network.target rpcbind.service gluster_bricks-engine.mount Before=network-online.target[Service]Type=forkingPIDFile=/var/run/glusterd.pidLimitNOFILE=65536Environment="LOG_LEVEL=INFO"EnvironmentFile=-/etc/sysconfig/glusterdExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid  --log-level $LOG_LEVELKillMode=processSuccessExitStatus=15[Install]WantedBy=multi-user.target# /etc/systemd/system/glusterd.service.d/99-cpu.conf[Service]CPUAccounting=yesSlice=glusterfs.sliceNote : Some of the 'After=' and 'Requires='  entries were removed during copy-pasting.So I guess two (or three) questions. What is the expected operation after a full cluster reboot (ie: in the event of a power failure)? Why doesn't the engine start automatically, and what might be causing glusterd to fail, when it can be restarted manually and works fine?Expected -everything to be up and running.Root cause , the system's fstab generator starts after cluster tries to start the bricks - and of course fails.Then everything on the chain fails.Just use systemd's mount entries ( I have added automount also)  and you won't have such issues.Best Regards,Strahil Nikolov-- _Fact:1. Ninjas are mammals.2. Ninjas fight ALL the time.3. The purpose of the ninja is to flip out and kill people.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/N5ON5URNMFMAVSMFROTKTPBCKGNDN5ON/

[ovirt-users] Re: rebooting an ovirt cluster

[Strahil]

2. Reboot all nodes. I was testing for power outage response. All nodes come up, but glusterd is not running (seems to have failed for some reason). I can manually restart glusterd on all nodes and it comes up and starts communicating normally. However, the engine does not come online. So I figure out where it last lived, and try to start it manually through the web interface. This fails because vdsm-ovirtmgmt is not up. I figured out the correct way to start up the engine would be through the cli via hosted-engine --vm-start. This does work, but it takes a very long time, and it usually starts up on any node other than the one I told it to start on.If you use fstab - prepare for pain... Systemd mounts are more effective.Here is a sample:[root@ovirt1 ~]# systemctl cat gluster_bricks-engine.mount# /etc/systemd/system/gluster_bricks-engine.mount[Unit]Description=Mount glusterfs brick - ENGINERequires = vdo.serviceAfter = vdo.serviceBefore = glusterd.serviceConflicts = umount.target[Mount]What=/dev/mapper/gluster_vg_md0-gluster_lv_engineWhere=/gluster_bricks/engineType=xfsOptions=inode64,noatime,nodiratime[Install]WantedBy=glusterd.service[root@ovirt1 ~]# systemctl cat glusterd.service# /etc/systemd/system/glusterd.service[Unit]Description=GlusterFS, a clustered file-system serverRequires=rpcbind.service gluster_bricks-engine.mount gluster_bricks-data.mountAfter=network.target rpcbind.service gluster_bricks-engine.mount Before=network-online.target[Service]Type=forkingPIDFile=/var/run/glusterd.pidLimitNOFILE=65536Environment="LOG_LEVEL=INFO"EnvironmentFile=-/etc/sysconfig/glusterdExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid  --log-level $LOG_LEVELKillMode=processSuccessExitStatus=15[Install]WantedBy=multi-user.target# /etc/systemd/system/glusterd.service.d/99-cpu.conf[Service]CPUAccounting=yesSlice=glusterfs.sliceNote : Some of the 'After=' and 'Requires='  entries were removed during copy-pasting.So I guess two (or three) questions. What is the expected operation after a full cluster reboot (ie: in the event of a power failure)? Why doesn't the engine start automatically, and what might be causing glusterd to fail, when it can be restarted manually and works fine?Expected -everything to be up and running.Root cause , the system's fstab generator starts after cluster tries to start the bricks - and of course fails.Then everything on the chain fails.Just use systemd's mount entries ( I have added automount also)  and you won't have such issues.Best Regards,Strahil Nikolov___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/W7YCIYIZVQGXJPGMVMYCTRJUVT7YZOSE/

[ovirt-users] Re: Wrong CPU performance report

[Liran Rotenberg]

Hi,
If your windows guest is with update 1803 or above you might hit this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1644693

Regards,
Liran.

On Sun, Feb 3, 2019 at 11:28 PM Hetz Ben Hamo  wrote:

> Hi,
>
> I'm running oVirt 4.2.7.1. I installed Windows 10 pro as a guest, along
> with QXL and all the drivers, as well as QEMU guest agent.
>
> While Windows reports a CPU usage of something like 2-4% when idle, oVirt
> reports 24-27% CPU usage.
>
> Bug? should I report it?
>
> Thanks
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/OJMAVROXJOSJ2B33BZ5XFJ2QGHONM65Z/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/MK5QWLJTGPQPLMSFLYR52UQXSVZU5BBR/