Re: [Qemu-devel] QEMU 0.8.1
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 whenever you reach the limits of the SDL window ? On 5/5/06, Anthony Liguori [EMAIL PROTECTED] wrote: 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 -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
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 this but requires a driver in the guest side, so in unsupported systems you still have to click to grab. Just as a side note, the USB tablet support makes this quite easy at least on Win2k - it already has the required driver, so for me it was enough to add -usbdevice tablet to the command line to have the mouse cursor automatically grabbed/ungrabbed (it seems that the behaviour of Ctrl+Alt changed a bit, but one gets used to it). Thanks to Brad and Anthony for making that possible :D Regards, Oliver El 05/05/2006, a las 8:57, Christian MICHON escribió: 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 whenever you reach the limits of the SDL window ? On 5/5/06, Anthony Liguori [EMAIL PROTECTED] wrote: 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 -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] sleep segfaults on qemu-0.8.1/kqemu-1.3.0pre6
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
Re: [Qemu-devel] Re: Unknown PCI Bridge
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 PCI device? I'm especially interested in this question: is qemu's current ACPI PCI device so normal, that it would be recognized and properly used by a newly installed Win2k? 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. -- mailto:[EMAIL PROTECTED]Index: hw/acpi.c === RCS file: /cvsroot/qemu/qemu/hw/acpi.c,v retrieving revision 1.1 diff -u -r1.1 acpi.c --- hw/acpi.c 3 May 2006 22:02:44 - 1.1 +++ hw/acpi.c 5 May 2006 12:25:49 - @@ -234,7 +234,7 @@ pci_conf[0x00] = 0x86; pci_conf[0x01] = 0x80; pci_conf[0x02] = 0x13; -pci_conf[0x03] = 0x70; +pci_conf[0x03] = 0x71; pci_conf[0x08] = 0x00; // revision number pci_conf[0x09] = 0x00; pci_conf[0x0a] = 0x80; // other bridge device ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] [usb] patch in bLength for hub descriptor
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[] =
{
- 0x09, /* u8 bLength; */
+ 0x00, /* u8 bLength; patched in later */
0x29, /* u8 bDescriptorType; Hub-descriptor */
0x00, /* u8 bNbrPorts; (patched later) */
0x0a, /* u16 wHubCharacteristics; */
@@ -417,6 +417,7 @@
}
ret = sizeof(qemu_hub_hub_descriptor) + var_hub_size;
+data[0] = ret;
break;
}
default:
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] Re: QEMU 0.8.1 and vnc
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 storing pixels in big endian mode. A proper fix is on my TODO list. 2) When it bounces from the initial syslinux text to the grahpical screen, it leaves the text in the top left corner not cleared. (to the boot: at the bottom) Yeah, I've noticed something similar myself. It's on the TODO list (see vnc.c). 3) screen autoresize is not working. 2 examples with DSL. a) initial screen is 80x25, but qemu comes up in 80x24 and stays there and I can't see boot: prompt at the bottom. b) when it goes into graphical mode, it's not resizing so I'm missing some portion of the screen TightVNC doesn't support the desktop resize encoding. Try RealVNC. Regards, Anthony Liguori Host is solaris 9/sparc and solaris 11/x86, viewer is tightvnc V 1.2.8 on solaris 11/x86. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
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 http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
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 + usb tablet ? Thanks On 5/5/06, Anthony Liguori [EMAIL PROTECTED] wrote: Oh, I doubt that Windows 3.0 has USB support. I also doubt that VMware wrote a driver for it :-) You probably won't have much like with RH7.2 either. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] Re: Unknown PCI Bridge
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 PIIX4 ACPI, but all the other qemu-hardware is only PIIX3 - afaik. 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. Beside that, a PIIX3-ACPI-device doesn't seem to exist in the pciid-database. signature.asc Description: OpenPGP digital signature ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
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 help me please on rh72 + usb tablet ? I don't know of an X driver for such an old kernel that would work. Sorry. Regards, Anthony Liguori Thanks On 5/5/06, Anthony Liguori [EMAIL PROTECTED] wrote: Oh, I doubt that Windows 3.0 has USB support. I also doubt that VMware wrote a driver for it :-) You probably won't have much like with RH7.2 either. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] Re: DMA with Knoppix and qemu (cvs-version)
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 for harrdisks, but not for cdroms. Strange - why? signature.asc Description: OpenPGP digital signature ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Re: DMA with Knoppix and qemu (cvs-version)
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 failed: Operation not permitted Ah ha! DMA mode work for harrdisks, but not for cdroms. Strange - why? cause the mode bits set for HD DMA weren't set for CDROM. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] Re: Unknown PCI Bridge
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 /usr/share/misc/pci.ids|grep -i PIIX3 7000 82371SB PIIX3 ISA [Natoma/Triton II] 7010 82371SB PIIX3 IDE [Natoma/Triton II] 7020 82371SB PIIX3 USB [Natoma/Triton II] # cat /usr/share/misc/pci.ids|grep -i PIIX4 7110 82371AB/EB/MB PIIX4 ISA 7111 82371AB/EB/MB PIIX4 IDE 7112 82371AB/EB/MB PIIX4 USB 7113 82371AB/EB/MB PIIX4 ACPI See? No PIIX3 ACPI device. That's all i tried to say. signature.asc Description: OpenPGP digital signature ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] qemu/hw acpi.c
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: http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/hw/acpi.c.diff?tr1=1.1tr2=1.2r1=textr2=text ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] qemu/hw usb-hub.c
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: http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/hw/usb-hub.c.diff?tr1=1.3tr2=1.4r1=textr2=text ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] bug reports and suggestions
-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 subject for a different day.) I realize that it's a complicated issue requiring kernel modules, etc, and exponentially more complicated with cross platform, but I wonder if anyone has considered trying to tie into the vmware-player's kernel modules and use them? There has to be some sort of de-facto API for interaction between the modules and the player. Too rife with IP problems? Someone wrote a kernel module some months ago which exposes some special kernel function via /proc ... IIUC this was intended to allow easier networking... Does anyone know more about it (or did anyone understand my confusing description ;) ? Another interesting thing concerning networking: I use a little script to set up a bridge between eth0 and tap0; but I have give the new bridge interface (eg. br0) an IP address and such stuff, because eth0 doesn't work. This is with Linux 2.6, but I read that with Linux 2.4 it was not necessary to configure br0, as eth0 would still be accessible. Does anyone know why this changed? I think it would be much easier if an interface used in a bridge was still usable. Thanks, Oliver -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEW9vwTFOM6DcNJ6cRApc8AJ9qYCEBHJqu/TsWilH5ztnx+PF8wACffVTp 2AbeG8IcGxMz3lO1BUeZ3gY= =a4mn -END PGP SIGNATURE- ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] DMA with Knoppix and qemu (cvs-version)
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: HDIO_SET_DMA failed: Operation not permitted Just a note: setting DMA through hdparm doesn't work on Linux since tens of versions ago, it's been depreceted and you have to trust the on-boot autodetection (and it works fine -- unless you didn't compile the right driver in). It's the same on real machines. Are there some issues with qemu's DMA support and Linux? (qemu does have DMA support, doesn't it?) Greetings Sven ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel Regards, Andrzej -- balrog 2oo6 Dear Outlook users: Please remove me from your address books http://www.newsforge.com/article.pl?sid=03/08/21/143258 ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
