Hi and thanks for your replies,
I cleaned up everything and started from scratch.
I using nested-kvm for my test with host-passthrough to expose vmx to the
VM hypervisor, my physical CPU is a Core i5 6500
This time I had another problem, the VM engine won't start because of this
error in vdsm.log
On 03/24/2018 01:40 PM, Andy Michielsen wrote:
> Hello,
>
> I also have done a installation on my host running KVM and I ‘m pretty
> sure my vm’s can only use the 192.168.122.0/24 range if you install
> them with NAT networking when creating them. So that might explain why
> you see that address ap
Hello,
I also have done a installation on my host running KVM and I ‘m pretty sure my
vm’s can only use the 192.168.122.0/24 range if you install them with NAT
networking when creating them. So that might explain why you see that address
appear in your log and also explain why the engine system
Hi,
I am testing oVirt 4.2, I am using nested KVM for that.
I am using two hypervisors Centos 7 updated and the hosted-Engine
deployment using the ovirt appliance.
For storage I am using iscsi and NFS4
Versions I am using :
ovirt-engine-appliance-4.2-20180214.1.el7.centos.noarch
ovirt-hosted-engi
4 matches
Mail list logo