We can't run kvm-ok directly, because the package that provides kvm-ok may be being installed at that time. Note that there's another bug where we're trying to get kvm-ok into the base system files and out of qemu-kvm, Bug #429443.
However, kvm-ok's real meat is a very simple grep of /proc/cpuinfo. That's certainly something that we can do.
I disagree with the concept of a "dialog box", or anything interactive that would hamper unattended installations.
But I can throw a warning message echo'd in the nc postinst, such that the message is at least logged *somewhere*.
Etienne-
Hmm, this is a bit easier said than done.
We can't run kvm-ok directly, because the package that provides kvm-ok may be being installed at that time. Note that there's another bug where we're trying to get kvm-ok into the base system files and out of qemu-kvm, Bug #429443.
However, kvm-ok's real meat is a very simple grep of /proc/cpuinfo. That's certainly something that we can do.
I disagree with the concept of a "dialog box", or anything interactive that would hamper unattended installations.
But I can throw a warning message echo'd in the nc postinst, such that the message is at least logged *somewhere*.
:-Dustin