Hi all, I'm working on Chromium OS development. We have a pretty elaborate chroot inside of which we carry out all development. We use KVM to launch Chromium OS builds inside a VM for testing. Turns out that for some reason, when QEMU is launched from inside the chroot, KVM itself seems not to be used. The VM is extremely slow.
Is this known/expected? QEMU is installed inside the chroot, the KVM modules are loaded, the /dev/kvm device is present and accesible. Any ideas on how to debug this? Thanks, Jorge -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
