it works. Side effect: after the first ungrab, I can't see the host
pointer over the SDL windows.
Yet, it's nothing as compared to the invisible wall.
I know nothing about most qemu internals, but would it be
possible to make it like vmw*re, ie the mouse is automagically
grabbed/ungrabbed wheneve
On Thu, 04 May 2006 20:17:04 +0200, Fabrice Bellard wrote:
> Chris Bagwell wrote:
>> Hi all,
>>
>> I upgraded to current CVS (0.8.1 plus a couple of patches like acpi).
>> Last time I upgraded was about 1 week ago.
>>
>> When I ran this version with a win98 guest, windows detected a new
>> devic
Thomas Han wrote:
Hi,
For what it's worth. I have also seen this "invisible wall" problem
with my mouse for a few weeks off the CVS build too.
Can you try out the following patch. *grumbles about SDL's brokenness*
Regards,
Anthony Liguori
Since 0.8.1 came out yesterday, Instead of using
Sent: Thursday, May 04, 2006 5:45 AM Fabrice Bellard wrote:
> Hi,
>
> QEMU version 0.8.1 is available at http://bellard.org/qemu/download.html.
>
qemu-system-sparc.exe doesn't work. A patch is below.
Regards,
Kazu
--- qemu-0.8.1.orig/loader.c Thu May 4 05:32:58 2006
+++ qemu-0.8.1/loader.c T
I have a few images from qemu-0.8.0 version::
debian-3.r1 boots
freebsd-6.0 complains about caclcru:...
openbsd-3.8 does not boot
plan 9does not boot
minix-3.0 does not boot
all of the boot and work without -kernel-kqemu option
(qemu -hda ./image-file -m 128 -localtime
Hi,
i just booted a recent knoppix-cd (4.0.2) and i'm trying to enable DMA,
but it won't work!
I started qemu with that command:
qemu -m 256 -cdrom knoppix.iso -boot d
But inside knoppix, a "hdparm -d1 /dev/hdc" won't work:
HDIO_SET_DMA failed: Operation not permitted
Are there some issues
> Yes, ACPI adds a new PCI device so it is normal. I am interested by any
> regression found using the current CVS with ACPI...
I think, this answer is fairly useless for the OP.
So perhaps the OP wanted to ask: how do i tell my Win2k to properly use
the new PCI device?
I'm especially interested
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
after switching from kqemu-1.3.0pre5 to kqemu-1.3.0pre6, Win98 guest
stops during boot with "Windows protection fault". Qemu is started with
qemu -hda win98/win98-new.img -boot c
(I used the same command line successfully with old kqemu).
Any i
Syatme is Debian derivative, kernel version 2.6.15.1.
compiled k1qemu with gcc-4.0, compiles and insmods fine
compiled qemu with gcc-3.4, compiles, installs and runs
fine without -kernel-kqemu option
kernel panic with -kernel-kqemu option (guest slax,
host linux).
Is this a known issue?
-ishwar
Chris Bagwell wrote:
Hi all,
I upgraded to current CVS (0.8.1 plus a couple of patches like acpi).
Last time I upgraded was about 1 week ago.
When I ran this version with a win98 guest, windows detected a new
device called "PCI Bridge". It was unable to find a driver for this on
the win98
Hi,For what it's worth. I have also seen this "invisible wall" problem with my mouse for a few weeks off the CVS build too.Since 0.8.1 came out yesterday, Instead of using CVS build, I'm now running Qemu
0.8.1 + kqemu-1.3.0pre6. My host OS is FC5 and I'm running XP inside it.Thanks,ThomasOn 5/4/
yes, but this is a painful way to recalibrate. Apparently, there's a
confusion inside absolute coord and relative coord between
guest and host.
Turning off acceleration is not helping at all. Unfortunately
On 5/4/06, Chris Bagwell <[EMAIL PROTECTED]> wrote:
I've seen this for a few weeks in CVS
Hi all,
I upgraded to current CVS (0.8.1 plus a couple of patches like acpi).
Last time I upgraded was about 1 week ago.
When I ran this version with a win98 guest, windows detected a new
device called "PCI Bridge". It was unable to find a driver for this on
the win98 CD and placed it as n
Christian MICHON wrote:
seen on winXP host (kqemu independent): sometimes the pointer
inside the guest hits like an invisible wall and cannot go any further.
This happens on a win2003 bartpe based guest and on a RedHat 7.2
livecd (superrescue 2.1.2).
I've seen this for a few weeks in CVS as well
I can reproduce on a linux host. I've seen this for a few weeks in CVS.
On 5/4/06, Christian MICHON <[EMAIL PROTECTED]> wrote:
qemu 0.8.0 does not show this invisible barrier issue.
if this is worth anything, I use SDL 1.2.9.
If someone can reproduce the issue also on linux hosts,
there could
qemu 0.8.0 does not show this invisible barrier issue.
if this is worth anything, I use SDL 1.2.9.
If someone can reproduce the issue also on linux hosts,
there could be a lead.
On 5/4/06, Christian MICHON <[EMAIL PROTECTED]> wrote:
I removed manually vnc_display_init, and this is not the culpr
I removed manually vnc_display_init, and this is not the culprit...
I'll check anyway versus qemu-0.8.0...
On 5/4/06, Christian MICHON <[EMAIL PROTECTED]> wrote:
I would say this could be a grab/ungrab issue induced recently
(vnc patch?). To check it, how do I remove the vnc patch alltogether ?
seen on winXP host (kqemu independent): sometimes the pointer
inside the guest hits like an invisible wall and cannot go any further.
This happens on a win2003 bartpe based guest and on a RedHat 7.2
livecd (superrescue 2.1.2).
how to see it:
- boot the guest without having the physical pointer gr
Hi,
I just compiled Qemu 0.8.1 for windows and started it with kquemu 1.3.0pre6 and
tapped networking under Win2k. Within the last 4 hours I got about 4
bluescreens of the machine.
It only happens when accessing files on the qemu gentoo system via a samba
share from the windows host. Is there an
Hi!
> QEMU version 0.8.1 is available at
> http://bellard.org/qemu/download.html.
Great! Thanks for the hard work of Qemu community!
BTW, any decision about the async I/O patch? Will you merge it or does
it need more tests?
regards,
Mulyadi
___
Qe
20 matches
Mail list logo
