Following discussion in this thread I have now addressed the qemu "situation". Here is a basic rundown from the other thread:
OK - let me clarify the situation pkg wise:
qemu - in [community]: built without support of the kernel module kqemu
kqemu - in UNSUPPORTED: builds both qemu and kqemu but according to stonecrest this kernel module won't work
kqemu26 - removed from UNSUPPORTED: was supposed to install kernel module for qemu pkg but qemu pkg does have support for it.
kqemu cannot be distibuted as a binary. I will rebuild qemu in [community] using the kqemu PKGBUILD (should I use the patches?) but will not install the kernel module (last 4 lines). This will makedepends=('gcc<=3.4.3')
I will then remove kqemu from UNSUPPORTED and create a new pkg called kqemu that will be == with the old kqemu26 PKGBUILD.
kqemu will depend=('qemu') and will build against the running kernel - this will not be distributed as a binary.
What you need to know
If you currently have qemu, kqemu or kqemu26 installed I strongly suggest you remove them and begin from scratch as it was not possible to rely on conflicts and replaces commands in the PKGBUILDS. Simply install qemu from [community]
pacman -S qemu
Then download the kqemu tarball and use makepkg to create the kernel module for you running kernel. It does build against gcc4!
I have tested the new qemu pkg on my home system. I installed it, booted into kernel A and built the kqemu module - ran qemu and confirmed kqemu was enabled. I then removed kqemu, booted kernel B and built kqemu again. I then installed and tested in the same way and it worked perfectly. I did not need to use modprobe -f as I had previously.
So, there is no longer a PKGBUILD in the AUR that installs qemu and kqemu all in one. According to some this PKGBUILD did not work anyway (see thread linked above).
· I am not certain the PKGBUILDs are the greatest - I had to pretty much guess how they worked without spending even more time fixing it - if you have suggestions to tidy them up they are warmly welcomed.
· qemu needs to be moved from community/system to community/emulators, as I understand it this cannot be done by a regular TU remotely and must actually be moved in the cvsroot to maintain the file history.
· The qemu PKGBUILD does uses patches that apparently allow you to build it against gcc4 - can someone confirm this?
I hope this solution is to everyones satisfaction
well I got it working here
gcc4 ... qemu (kqemu + patches)
had to use a small script to create module etc.... (add it rc.local)
Qemu works better with kqemu but not that much faster (less cpu usage!)
Confirming that kqemu compiles fine using gcc4!
Why is it that kqemu cannot be distributed as a binary? If it has to do with kernel versioning, it should probably be built against the stock kernel, as least.
It's licensing, mate
As I feared... stupid crap
Aren't they using headers and things from the kernel though? Shouldn't that force it to be GPL'd as well?
pkgbuild needs to build install kqemu & set up /dev (rc.local or a daemon?)
I assume this is possible ?
Is that the direction you were looking in .... ?
np thinking aloud again .... :oops:
more install-kqemu #!/bin/sh modprobe kqemu mknod /dev/kqemu c 250 0 chmod 666 /dev/kqemu
I jut stuck it in a small script ... /me bloody lazy git lol....
/todo add lines above to rc.local
/me looks for code