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?

From: "Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; To: "Martin Kletzander" <mkletzan(a)redhat.com&gt; Cc: libvir-list(a)redhat.com, "vdsm-devel" <vdsm-devel(a)fedorahosted.org&gt;, "users" <users(a)ovirt.org&gt; 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.