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
That's good.
Then someone should create drivers for the OSes that doesn't include
USB tablet support and will be great.
El 05/05/2006, a las 12:33, Oliver Gerlich escribió:
Natalia Portillo wrote:
That requires a driver in guest side that communicates with qemu.
VMWare and VirtualPC does
Host: winXP pro
Guest: Redhat 7.2
when kqemu (user mode) is active, sleep 1 segfaults each time.
With kqemu disabled, no problem
--
Christian
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
On Fri, 5 May 2006, Sven K?hler wrote:
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
lo list. I forgot to update the bLength field in the hub
descriptor. The attached patch does this.
--- b/qemu/hw/usb-hub.c 2006-04-30 16:53:59.0 -0500
+++ a/qemu/hw/usb-hub.c 2006-05-05 08:47:52.0 -0500
@@ -152,7 +152,7 @@
static const uint8_t qemu_hub_hub_descriptor[] =
{
Ben Taylor wrote:
I'm seeing quite a few bugs on Qemu 0.8.1 with the vnc feature
1) Sparc based system comes up in distored colors (foreground of a Damn Small
linux
iso comes up in yellow, instead of white)
This is a know problem. qemu doesn't give any indication that the guest
is
on windows 3.0 (my usual testcase) ?
I'll try at least on rh72...
On 5/5/06, Anthony Liguori [EMAIL PROTECTED] wrote:
As someone has already mentioned, you want to use -usb -usbdevice tablet.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
well, at least inside rh72, I can see a usb device:
Vendor=0627 ProdID=0001
Product=QEMU USB Tablet
all I need now is:
1) which module to modprobe
2) which /dev/input/event... is used
3) modify XF86config accordingly
and then theoretically it should work...
anyone can help me please on rh72 +
qemu's ACPI PCI device doesn't seem to be _that_ normal/known. At least
a recent Knoppix lists it as Bridge: Intel Corp.: Inknown device 7013.
Wrong device id, should be 0x7113.
Hmmm, i looked it up, and i think i know why the author preferred 7013
instead of 7113.
7113 is 82371AB/EB/MB
Christian MICHON wrote:
well, at least inside rh72, I can see a usb device:
Vendor=0627 ProdID=0001
Product=QEMU USB Tablet
all I need now is:
1) which module to modprobe
2) which /dev/input/event... is used
3) modify XF86config accordingly
and then theoretically it should work...
anyone can
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
Ah ha! DMA mode work
Sven Köhler [EMAIL PROTECTED] wrote:
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
So using 7113 would mean, that the PIIX4 stuff gets mixed with PIIX3
stuff. I don't know, how odd that might seem to some OS.
It's irrelevant to any OS that i know of.
;-)
Beside that, a PIIX3-ACPI-device doesn't seem to exist in the
pciid-database.
Huh?
# cat
CVSROOT:/sources/qemu
Module name:qemu
Branch:
Changes by: Fabrice Bellard [EMAIL PROTECTED] 06/05/05 20:03:46
Modified files:
hw : acpi.c
Log message:
typo
CVSWeb URLs:
CVSROOT:/sources/qemu
Module name:qemu
Branch:
Changes by: Fabrice Bellard [EMAIL PROTECTED] 06/05/05 20:05:35
Modified files:
hw : usb-hub.c
Log message:
patch in bLength for hub descriptor (Lonnie Mendez)
CVSWeb URLs:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don Kitchen schrieb:
Next, it seems the *one* thing QEMU lacks that you-know-who does correctly
is networking, specifically bridged mode. I know about creating a tap device
and sticking it into a bridge (really hasn't worked for me, but that's the
Hi there,
On 05/05/06, Sven Köhler [EMAIL PROTECTED] wrote:
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:
17 matches
Mail list logo
