[Users] Host local_host running without virtualization hardware acceleration
Hi, I had to reinstall ovirt yesterday and now it seems that it doesn't work anymore. I'm running nightly on Fedora 18. kernel-3.11.4-101.fc18.x86_64 sanlock-2.8-1.fc18.x86_64 libvirt-1.1.4-1.fc18.x86_64 qemu-1.5.1-1.fc18.x86_64 vdsm-4.13.0-93.gitea8c8f0.fc18.x86_64 ovirt-engine-3.4.0-0.2.master.20131104192919.git3b65870.fc18.noarch engine-setup with all-in-one detects hardware virtualization and allow me to configure the system. (it fails detecting engine health status due probably to recent changes in its URL, I'm already looking into it) Once added localhost to the engine, it has been moved to non operational mode saying I don't have virtualization hardware acceleration anymore. I've found that: # modinfo kvm filename: /lib/modules/3.11.4-101.fc18.x86_64/kernel/arch/x86/kvm/kvm.ko license: GPL author: Qumranet depends: intree: Y vermagic: 3.11.4-101.fc18.x86_64 SMP mod_unload parm: min_timer_period_us:uint parm: ignore_msrs:bool parm: tsc_tolerance_ppm:uint parm: allow_unsafe_assigned_interrupts:Enable device assignment on platforms without interrupt remapping support. (bool) # /usr/bin/qemu-kvm Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory looking at strace: open("/dev/kvm", O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory) Any clue on what may be happened? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 05/11/2013 09:08, Sandro Bonazzola ha scritto:
Hi, I had to reinstall ovirt yesterday and now it seems that it doesn't work anymore. I'm running nightly on Fedora 18. kernel-3.11.4-101.fc18.x86_64 sanlock-2.8-1.fc18.x86_64 libvirt-1.1.4-1.fc18.x86_64 qemu-1.5.1-1.fc18.x86_64 vdsm-4.13.0-93.gitea8c8f0.fc18.x86_64 ovirt-engine-3.4.0-0.2.master.20131104192919.git3b65870.fc18.noarch
engine-setup with all-in-one detects hardware virtualization and allow me to configure the system. (it fails detecting engine health status due probably to recent changes in its URL, I'm already looking into it)
Once added localhost to the engine, it has been moved to non operational mode saying I don't have virtualization hardware acceleration anymore.
I've found that:
# modinfo kvm filename: /lib/modules/3.11.4-101.fc18.x86_64/kernel/arch/x86/kvm/kvm.ko license: GPL author: Qumranet depends: intree: Y vermagic: 3.11.4-101.fc18.x86_64 SMP mod_unload parm: min_timer_period_us:uint parm: ignore_msrs:bool parm: tsc_tolerance_ppm:uint parm: allow_unsafe_assigned_interrupts:Enable device assignment on platforms without interrupt remapping support. (bool)
# /usr/bin/qemu-kvm Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory
looking at strace: open("/dev/kvm", O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory)
Any clue on what may be happened?
I've found kvm_intel module not loaded. I've created a new conf file for loading it automatically at boot so I've solved on my system. However, what has been changed for not having it loaded automatically as it was done before? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
--H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 05, 2013 at 09:08:33AM +0100, Sandro Bonazzola wrote:
Hi, I had to reinstall ovirt yesterday and now it seems that it doesn't work = anymore. I'm running nightly on Fedora 18. kernel-3.11.4-101.fc18.x86_64 sanlock-2.8-1.fc18.x86_64 libvirt-1.1.4-1.fc18.x86_64 qemu-1.5.1-1.fc18.x86_64 vdsm-4.13.0-93.gitea8c8f0.fc18.x86_64 ovirt-engine-3.4.0-0.2.master.20131104192919.git3b65870.fc18.noarch =20 engine-setup with all-in-one detects hardware virtualization and allow me= to configure the system. (it fails detecting engine health status due probably to recent changes i= n its URL, I'm already looking into it) =20 Once added localhost to the engine, it has been moved to non operational = mode saying I don't have virtualization hardware acceleration anymore. =20 I've found that: =20 # modinfo kvm filename: /lib/modules/3.11.4-101.fc18.x86_64/kernel/arch/x86/kvm/k= vm.ko license: GPL author: Qumranet depends: intree: Y vermagic: 3.11.4-101.fc18.x86_64 SMP mod_unload parm: min_timer_period_us:uint parm: ignore_msrs:bool parm: tsc_tolerance_ppm:uint parm: allow_unsafe_assigned_interrupts:Enable device assignment= on platforms without interrupt remapping support. (bool) =20
This is good, but AFAIK this module is not what provides /dev/kvm. Depending on the processor you're using, try checking 'kvm_intel' or 'kvm_amd'. Also make sure both are loaded.
# /usr/bin/qemu-kvm Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory =20 looking at strace: open("/dev/kvm", O_RDWR|O_CLOEXEC) =3D -1 ENOENT (No such file or di= rectory) =20
What does ls -lZ /dev/kvm tell you?
Any clue on what may be happened? =20
No idea, but I'm basing everything on the fact that it worked before the re-install, am I right? Martin --H+4ONPRPur6+Ovig Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJSeL86AAoJEAgfwp8kF4bdXvQQAIuIrJfMF9fw9WTz9+Adfoli 0/VfH+VcWNsVR21C1rTn+1QfDngu6JsrmCrB8DDrsUFwmRbPB2XzH/uYX2NJ5Lue G8TBqG94+lpLi22PKrMj8Zlueg3UHsfLOpv8RON0t9dzofwWIGk5yBxQgm0ac+rV Gpu7LzxX11RketJtGnY1zCFH5wbWGbskSl0A4RQyzSBR3Y+uyFhAHVnw8p10tRmE 2SJyNVcNs7tViudQn+mpAINrwTSz7k/QrhM1F8u26/ubE11tODXp1B9WUs5cOx+9 a7WADp9WzpWca1ebjyy3/QS0SkTMx3SNpjwjQ2DP6UIb/c+/qXHiUVQlmGeMupIG BoiGaI+EpWyioUNtGuVFmoA7VS1iVUk75pEIL23niQozOKTw9v7x1Hiu83YNYvWo V7aWrp57xE5td40CEuJX0wy0EvHL7bjSo3VK0k1H+r6IBsgNys3+VJHHDldJDRyR 3o92QJmizH6u+ScHW7EvJ/CdXD/WsMZaTR05u70xNQUwAy/PhNbdcRCCUnjLpw0n Ux5Fx/7gxCu75qlgy6c0f0DanZOYOPFSHIEnK3ew09dop84ZGXAazplOc8Wzuzxp dgzXVRRbfJLSMhQhgQDAyEWyF6oldU8IZkSlAqC44j6dewmV/tXOxopa37A/5gyl qSk4tKHy2WAmcVa+tovE =jrqH -----END PGP SIGNATURE----- --H+4ONPRPur6+Ovig--
Il 05/11/2013 10:49, Martin Kletzander ha scritto:
On Tue, Nov 05, 2013 at 09:08:33AM +0100, Sandro Bonazzola wrote:
Hi, I had to reinstall ovirt yesterday and now it seems that it doesn't work anymore. I'm running nightly on Fedora 18. kernel-3.11.4-101.fc18.x86_64 sanlock-2.8-1.fc18.x86_64 libvirt-1.1.4-1.fc18.x86_64 qemu-1.5.1-1.fc18.x86_64 vdsm-4.13.0-93.gitea8c8f0.fc18.x86_64 ovirt-engine-3.4.0-0.2.master.20131104192919.git3b65870.fc18.noarch
engine-setup with all-in-one detects hardware virtualization and allow me to configure the system. (it fails detecting engine health status due probably to recent changes in its URL, I'm already looking into it)
Once added localhost to the engine, it has been moved to non operational mode saying I don't have virtualization hardware acceleration anymore.
I've found that:
# modinfo kvm filename: /lib/modules/3.11.4-101.fc18.x86_64/kernel/arch/x86/kvm/kvm.ko license: GPL author: Qumranet depends: intree: Y vermagic: 3.11.4-101.fc18.x86_64 SMP mod_unload parm: min_timer_period_us:uint parm: ignore_msrs:bool parm: tsc_tolerance_ppm:uint parm: allow_unsafe_assigned_interrupts:Enable device assignment on platforms without interrupt remapping support. (bool)
This is good, but AFAIK this module is not what provides /dev/kvm. Depending on the processor you're using, try checking 'kvm_intel' or 'kvm_amd'. Also make sure both are loaded.
I've found that, missing kvm_intel.
# /usr/bin/qemu-kvm Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory
looking at strace: open("/dev/kvm", O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory)
What does ls -lZ /dev/kvm tell you?
it doesn't existed, now it's working again after modprobe kvm_intel
Any clue on what may be happened?
No idea, but I'm basing everything on the fact that it worked before the re-install, am I right?
right. something was loading that module automatically before reinstall and now I needed to create a conf file for having it loaded.
Martin
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Martin Kletzander" <mkletzan@redhat.com> Cc: libvir-list@redhat.com, "vdsm-devel" <vdsm-devel@fedorahosted.org>, "users" <users@ovirt.org> Sent: Tuesday, November 5, 2013 11:56:24 AM Subject: Re: [Users] [libvirt] Host local_host running without virtualization hardware acceleration
Il 05/11/2013 10:49, Martin Kletzander ha scritto:
On Tue, Nov 05, 2013 at 09:08:33AM +0100, Sandro Bonazzola wrote:
Hi, I had to reinstall ovirt yesterday and now it seems that it doesn't work anymore. I'm running nightly on Fedora 18. kernel-3.11.4-101.fc18.x86_64 sanlock-2.8-1.fc18.x86_64 libvirt-1.1.4-1.fc18.x86_64 qemu-1.5.1-1.fc18.x86_64 vdsm-4.13.0-93.gitea8c8f0.fc18.x86_64 ovirt-engine-3.4.0-0.2.master.20131104192919.git3b65870.fc18.noarch
engine-setup with all-in-one detects hardware virtualization and allow me to configure the system. (it fails detecting engine health status due probably to recent changes in its URL, I'm already looking into it)
Once added localhost to the engine, it has been moved to non operational mode saying I don't have virtualization hardware acceleration anymore.
I've found that:
# modinfo kvm filename: /lib/modules/3.11.4-101.fc18.x86_64/kernel/arch/x86/kvm/kvm.ko license: GPL author: Qumranet depends: intree: Y vermagic: 3.11.4-101.fc18.x86_64 SMP mod_unload parm: min_timer_period_us:uint parm: ignore_msrs:bool parm: tsc_tolerance_ppm:uint parm: allow_unsafe_assigned_interrupts:Enable device assignment on platforms without interrupt remapping support. (bool)
This is good, but AFAIK this module is not what provides /dev/kvm. Depending on the processor you're using, try checking 'kvm_intel' or 'kvm_amd'. Also make sure both are loaded.
I've found that, missing kvm_intel.
# /usr/bin/qemu-kvm Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory
looking at strace: open("/dev/kvm", O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory)
What does ls -lZ /dev/kvm tell you?
it doesn't existed, now it's working again after modprobe kvm_intel
Any clue on what may be happened?
No idea, but I'm basing everything on the fact that it worked before the re-install, am I right?
right. something was loading that module automatically before reinstall and now I needed to create a conf file for having it loaded.
Perhaps it was libvirtd, and in your new setup it's not started automatically on boot? -- Didi
On Tue, Nov 05, 2013 at 09:08:33AM +0100, Sandro Bonazzola wrote:
Hi, I had to reinstall ovirt yesterday and now it seems that it doesn't work anymore. I'm running nightly on Fedora 18. kernel-3.11.4-101.fc18.x86_64 sanlock-2.8-1.fc18.x86_64 libvirt-1.1.4-1.fc18.x86_64 qemu-1.5.1-1.fc18.x86_64 vdsm-4.13.0-93.gitea8c8f0.fc18.x86_64 ovirt-engine-3.4.0-0.2.master.20131104192919.git3b65870.fc18.noarch
engine-setup with all-in-one detects hardware virtualization and allow me to configure the system. (it fails detecting engine health status due probably to recent changes in its URL, I'm already looking into it)
Once added localhost to the engine, it has been moved to non operational mode saying I don't have virtualization hardware acceleration anymore.
I've found that:
# modinfo kvm filename: /lib/modules/3.11.4-101.fc18.x86_64/kernel/arch/x86/kvm/kvm.ko license: GPL author: Qumranet depends: intree: Y vermagic: 3.11.4-101.fc18.x86_64 SMP mod_unload parm: min_timer_period_us:uint parm: ignore_msrs:bool parm: tsc_tolerance_ppm:uint parm: allow_unsafe_assigned_interrupts:Enable device assignment on platforms without interrupt remapping support. (bool)
# /usr/bin/qemu-kvm Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory
looking at strace: open("/dev/kvm", O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory)
Any clue on what may be happened?
What's your `lsmod | grep kvm` ? If empty, does `modprobe kvm_intel` trigger tail-telling lines on /var/log/message? Dan.
participants (4)
-
Dan Kenigsberg -
Martin Kletzander -
Sandro Bonazzola -
Yedidyah Bar David