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....
]]>I can auto setup the /dev etc - pretty sure you can do it with udev but I was thinking i needed to...
]]>I assume this is possible ?
Is that the direction you were looking in .... ?
my 2c
]]>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?
]]>qemu updated to -4, built against gcc4
Give it a few mins to gensync tho, it's only going up now
Answers to 1 and 2 anyone?
]]>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!)
HTH
]]>The Situation
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.
The Solution:
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).
Remaining Issues
· 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