I respond to this public-dev thread here Le Sun, 03 Jun 2007 08:58:19 -0400, Dale Blount <[EMAIL PROTECTED]> a écrit :
> On Sun, 2007-06-03 at 22:28 +1000, James Rayner wrote: > > On Sun, Jun 03, 2007 at 12:47:41PM +0200, Alexander Baldeck wrote: > > > Hey all, > > > > > > some of you may have noticed that we have a couple of feature > > > requests on flyspray [1] [2] regarding a new KVM and > > > paravirtualization. I've been messing with KVM on Linuxtag. So > > > far it works well but there's a few issues with it: > > > > > > 1) makes no sense to port to non-x86_64 > > > - i686 has kqemu - the kqemu on x86_64 is pretty much useless > > > btw > > > - I have never heard of a 32bit CPU that actually supports > > > this > > > - correct me if I'm wrong > > > > what about a capable 64bit processor running a 32 bit distro? Like > > the core 2 duos, pentium D 9x0..? > > Count me in here... This is what I was planning on doing on my core 2 > duo server when I get around to it. I got a Core2Duo, and I'm using Arch32 and kvm (and kqemu). > > > > > 2) it comes with a modified version of Qemu that only provides > > > qemu-system-$CARCH and thus conflicts with qemu itself > > > - merge with qemu package? > > > - strip qemu-system-$CARCH off of qemu package? > > > > could also rename the binary, otherwise, if you're using kvm, then > > you probably wont mind if you dont have stock qemu, so a conflicts > > should be fine? > > > > I'd say it'd be fine to conflict. You probably won't use both on the > same system. I do use both on the same system, I do have kvm and kqemu loaded at the same time, used at the same time, and they work well together. The reason to use the both, I wasn't able to install windows with Kvm, but it worked fine with kqemu. > > > > > 3) KVM modules in our kernel26 are very outdated and should be > > > removed in favor of the ones provided by the KVM source tarball > > > > or would it be better to patch the kernel with the new one? Why patch and patch again ? There are kvm modules in the kernel,use it. If someone want more uptodate kvm, he can patch it's kernel. Keep the patch number as low as possible is a good idea. > > > > > 4) split KVM into kvm-qemu & kvm-modules? > > It's a better solution than the number 3. > > definitely split the modules off if they must be seperated from the > > kernel. > > Agreed. > > > Dale > Best regards. -- slubman (aka Nicolas Doualot) jabber ID: [EMAIL PROTECTED] site: http://www.slubman.info/ _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
