kernel: qvm86: unsupported module, tainting kernel.
kernel: qvm86: Module loaded
kernel: qvm86: Created device 10.62
When I start qemu, it runs without qvm86 acceleration.
I have no idea, why it isn't running with qvm86 on this machine. (Doing the
same procedure on a debian system,
Hi!
I tried to install qvm86 under SuSE Linux Enterprise Server 9 running on a
Dual Pentium III with Kernel 2.6.5-7.139-smp.
After compiling the module:
modprobe qvm86
chmod 666 /dev/qvm86
In /var/log/messages I get the following output:
kernel: qvm86: unsupported module, tainting kernel.
Hi,
With current qemu CVS + current qvm86 CVS, after appliing qvm86 patch, I get
this build warning:
[...]
Building modules, stage 2.
MODPOST
*** Warning: cleanup_module [/tmp/qemu/qemu/qvm86/qvm86.ko] undefined!
*** Warning: init_module [/tmp/qemu/qemu/qvm86/qvm86.ko] undefined!
Hi,
I recently spent some effort working out what Separate Kernel Address
Space (SKAS) did for user-mode-linux (UML). The results of this keen be
seen here:
http://news.gmane.org/group/gmane.linux.uml.devel/last=/force_load=t
on the thread Using SKAS, any examples?
the conclusion to this is
Paul Brook wrote:
For user-mode emulation the largest chunk of address space is the translated
code buffer. This needs to be able to directly address the guest memory
space, so sharing a VM with the host qemu process isn't really a problem. We
just map the host qemu out of the way somewhere.
On Monday 09 May 2005 10:09, Ian Rogers wrote:
Hi,
I recently spent some effort working out what Separate Kernel Address
Space (SKAS) did for user-mode-linux (UML). The results of this keen be
seen here:
http://news.gmane.org/group/gmane.linux.uml.devel/last=/force_load=t
on the thread
