Hi!
I've tried qemu yesterday by a Windows XP (no SP-s)
installation and found that the security problem does
not appear when using kqemu, but appears without it.
System: Debian Sarge
Qemu: 7.0
(http://packages.debian.org/unstable/misc/qemu)
built from source and diff found on cited page
k
On Wed, 2005-08-31 at 17:40 +0200, Antonio Vargas wrote:
> On 8/30/05, Antonio Vargas <[EMAIL PROTECTED]> wrote:
> > Having a look at the sources, I've noticed that extra ppc registers
> > are only used when doing usermode-inly emulation and not when doing
> > fullsystem-mode. Can anyone tell me wh
On 8/30/05, Antonio Vargas <[EMAIL PROTECTED]> wrote:
> Having a look at the sources, I've noticed that extra ppc registers
> are only used when doing usermode-inly emulation and not when doing
> fullsystem-mode. Can anyone tell me where should I look for problems
> when disabling that restriction?
Hello Sven...
> rdtsc gives you the cpu's clock count, which, if CPU frequency
> changes, or your code is run on different processors (multiprocessor
> machine), cannot be assumed to be related to real time anymore.
> Resolutionwise, the real time clock may be inferior, of course, as
> Jim mention
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi - I'm writing a front-end for QEmu, and one problem I had was activating
full-screen mode. Sending ctrl-alt-f to the QEmu window via XSendEvent seems
to send it to the guest operating system - this may be because I've
reparented the window inside
