[ovirt-users] Re: ovirt virtulization manager login error failed: Connection refused (Connection refused)
mark this problem solved. i did it by setting selinux to disable ___ 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/HE36ZZ4WZIXLQWAJNPKMLS4YVQMBEVFR/
[ovirt-users] Unknown CPU model Broadwell-IBRS-SSBD
Hi, I've just installed hosted-engine. It proceeds to near the end of the Ansible script, then pauses at: "TASK [Check engine VM health]" then eventually errors: "Engine VM is not running, please check vdsm logs. The VDSM logs have error: "libvirtError: internal error: Unknown CPU model Broadwell-IBRS-SSBD" Also, in the oVirt Node webui, the HostedEngine VM is created, but not started. If I press Run, the following error is shown: VM START action failed error: Failed to start domain HostedEngine error: internal error: Unknown CPU model Broadwell-IBRS-SSBD I notice a Trello card was created to add similar Skylake & EPYC CPUs, but not Broadwell: https://trello.com/c/5nGTgQ9P/89-new-ibrs-and-ssbd-cpu-types# Does the Broadwell-IBRS-SSBD CPU need to be added to this supported types list? Many 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/KONKNDI3SXU4R4HEYU5VFG7JKDJOAUIR/
[ovirt-users] Re: Slow vm transfer speed from vmware esxi 5
On Sat, 18 Aug 2018 at 18:45 Bernhard Dick wrote: > Hi, > > currently I'm trying to move VMs from our vsphere 5 environment to > oVirt. While the io performance on oVirt and on the esxi platform is > quite well (about 100MByte/sec on a 1GBit storage link) the transfer > speed using the integrated v2v-feature is very slow (only 10MByte/sec). > That would result in transfer time of >24h for some machines. > Do you have any ideas how I can improve the transfer speed? > > Regards > Bernhard Dick > Hi Bernhard, With the latest version of the ovirt-imageio and the v2v we are performing quite nicely, and without specifying number I can tell you that weakest link is the read rate from the vmware data store. In our lab I can say that we roughly peek ~40 MiB/sec reading a single vm and the rest of our components(after the read from vmds) have no problem dealing with that - i.e buffering -> converting -> writing to imageio -> writing to storage So, in short, examine the read-rate from vm datastore, let us know, and please specify the versions you are using. ___ > 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/KQZPRX4M7V74FSYIY5LRUPC46CCJ2DCR/ > ___ 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/WYKFJPEIPGVUT7Q6TMRVLYRAFQVWBQTI/
[ovirt-users] ovirt-node-ng-image-update 4.2.4 to 4.2.5.1 fails
yum update ends with: warning: %post(ovirt-node-ng-image-update-4.2.5.1-1.el7.noarch) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package ovirt-node-ng-image-update-4.2.5.1-1.el7.noarch It creates the layers: ovirt-node-ng-4.2.5.1-0.20180731.0 onn Vri---tz-k 6.00g pool00 ovirt-node-ng-4.2.5.1-0.20180731.0+1 onn Vwi-a-tz-- 6.00g pool00 ovirt-node-ng-4.2.5.1-0.20180731.0 But no grub2 boot entry. nodectl info: layers: ovirt-node-ng-4.2.4-0.20180626.0: ovirt-node-ng-4.2.4-0.20180626.0+1 ovirt-node-ng-4.2.5.1-0.20180731.0: ovirt-node-ng-4.2.5.1-0.20180731.0+1 ovirt-node-ng-4.2.2-0.20180405.0: ovirt-node-ng-4.2.2-0.20180405.0+1 bootloader: default: ovirt-node-ng-4.2.4-0.20180626.0+1 entries: ovirt-node-ng-4.2.2-0.20180405.0+1: index: 1 title: ovirt-node-ng-4.2.2-0.20180405.0+1 kernel: /boot/ovirt-node-ng-4.2.2-0.20180405.0+1/vmlinuz-3.10.0-693.21.1.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=onn/ovirt-node-ng-4.2.2-0.20180405.0+1 img.bootid=ovirt-node-ng-4.2.2-0.20180405.0+1" initrd: /boot/ovirt-node-ng-4.2.2-0.20180405.0+1/initramfs-3.10.0-693.21.1.el7.x86_64.img root: /dev/onn/ovirt-node-ng-4.2.2-0.20180405.0+1 ovirt-node-ng-4.2.4-0.20180626.0+1: index: 0 title: ovirt-node-ng-4.2.4-0.20180626.0+1 kernel: /boot/ovirt-node-ng-4.2.4-0.20180626.0+1/vmlinuz-3.10.0-862.3.3.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=onn/ovirt-node-ng-4.2.4-0.20180626.0+1 img.bootid=ovirt-node-ng-4.2.4-0.20180626.0+1" initrd: /boot/ovirt-node-ng-4.2.4-0.20180626.0+1/initramfs-3.10.0-862.3.3.el7.x86_64.img root: /dev/onn/ovirt-node-ng-4.2.4-0.20180626.0+1 current_layer: ovirt-node-ng-4.2.4-0.20180626.0+1 Just posting for others that might have the same issue. ___ 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/VOTNR3NH3EAEW6YDINIILFVGQB2BX544/
