[Qemu-devel] QEMU 0.8.1

[Fabrice Bellard]

Hi,

QEMU version 0.8.1 is available at http://bellard.org/qemu/download.html.

version 0.8.1:

  - USB tablet support (Brad Campbell, Anthony Liguori)
  - win32 host serial support (Kazu)
  - PC speaker support (Joachim Henke)
  - IDE LBA48 support (Jens Axboe)
  - SSE3 support
  - Solaris port (Ben Taylor)
  - Preliminary SH4 target (Samuel Tardieu)
  - VNC server (Anthony Liguori)
  - slirp fixes (Ed Swierk et al.)
  - USB fixes
  - ARM Versatile Platform Baseboard emulation (Paul Brook)

Fabrice.


___
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]

mingw32 build breaks on "ssize_t" which should be "long"
instead on win32 (see previous post on vnc.c).

beyond this little detail, compiled version works fine on
win32 (I'll do more testing tomorrow).

do we need kqemu-1.3.0pre6.tar.gz for this version
or a newer kqemu ?

On 5/3/06, Fabrice Bellard <[EMAIL PROTECTED]> wrote:

Hi,

QEMU version 0.8.1 is available at http://bellard.org/qemu/download.html.

version 0.8.1:

   - USB tablet support (Brad Campbell, Anthony Liguori)
   - win32 host serial support (Kazu)
   - PC speaker support (Joachim Henke)
   - IDE LBA48 support (Jens Axboe)
   - SSE3 support
   - Solaris port (Ben Taylor)
   - Preliminary SH4 target (Samuel Tardieu)
   - VNC server (Anthony Liguori)
   - slirp fixes (Ed Swierk et al.)
   - USB fixes
   - ARM Versatile Platform Baseboard emulation (Paul Brook)

Fabrice.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel




--
Christian


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[Mulyadi Santosa]

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


___
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]

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 grabbed
- the guest pointer is centered (position A)
- move the physical/host pointer halfway between guest pointer
and the bottom of the windows of the guest (position B)
- click inside the guest (grabs the physical pointer: we're in
position A)
- move the pointer vertically slowly down, the pointer cannot go
any lower than position B

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 ?

Christian

On 5/3/06, Fabrice Bellard <[EMAIL PROTECTED]> wrote:

Hi,

QEMU version 0.8.1 is available at http://bellard.org/qemu/download.html.




___
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]

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 ?



___
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]

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 culprit...
I'll check anyway versus qemu-0.8.0...


--
Christian


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[WaxDragon]

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 be a lead.

On 5/4/06, Christian MICHON <[EMAIL PROTECTED]> wrote:
> I removed manually vnc_display_init, and this is not the culprit...
> I'll check anyway versus qemu-0.8.0...
>
--
Christian


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel




--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows.  ReactOS is not just
software, it's people.
   kjk_hyperion


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[Chris Bagwell]

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 on win98 guest.  There 
seems to be a work around.   If you roll your mouse around a lot and far 
distances, it seems to recalibrate itself or something and the invisible 
wall goes away.


During the emails on the usb tablet development, I saw a few comments 
about having mouse acceleration turned on in windows could cause mouse 
confusion.  I haven't bothered trying to turn that off but that may also 
fix it.


Chris


___
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]

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 as well on win98 guest.  There
seems to be a work around.   If you roll your mouse around a lot and far
distances, it seems to recalibrate itself or something and the invisible
wall goes away.

During the emails on the usb tablet development, I saw a few comments
about having mouse acceleration turned on in windows could cause mouse
confusion.  I haven't bothered trying to turn that off but that may also
fix it.

Chris


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel




--
Christian


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[Thomas Han]

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/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 be a lead.On 5/4/06, Christian MICHON <[EMAIL PROTECTED]
> wrote:> I removed manually vnc_display_init, and this is not the culprit...> I'll check anyway versus qemu-0.8.0...>--Christian___
Qemu-devel mailing listQemu-devel@nongnu.orghttp://lists.nongnu.org/mailman/listinfo/qemu-devel

___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[Kazu]

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 Thu May  4 17:35:10 2006
@@ -200,7 +200,7 @@
 int fd, data_order, must_swab, ret;
 uint8_t e_ident[EI_NIDENT];
 
-fd = open(filename, O_RDONLY);
+fd = open(filename, O_RDONLY | O_BINARY);
 if (fd < 0) {
 perror(filename);
 return -1;



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[Anthony Liguori]

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 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,
Thomas

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 be a lead.

On 5/4/06, Christian MICHON <[EMAIL PROTECTED]
> wrote:
> I removed manually vnc_display_init, and this is not the culprit...
> I'll check anyway versus qemu-0.8.0...
>
--
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
  


diff -r 39a6dd1136c6 sdl.c
--- a/sdl.c Thu May 04 04:13:13 2006 +
+++ b/sdl.c Thu May 04 21:30:11 2006 -0500
@@ -280,13 +280,18 @@ static void sdl_update_caption(void)
 
 static void sdl_hide_cursor(void)
 {
-SDL_SetCursor(sdl_cursor_hidden);
+if (kbd_mouse_is_absolute()) {
+   SDL_ShowCursor(1);
+   SDL_SetCursor(sdl_cursor_hidden);
+} else {
+   SDL_ShowCursor(0);
+}
 }
 
 static void sdl_show_cursor(void)
 {
 if (!kbd_mouse_is_absolute()) {
-   SDL_SetCursor(sdl_cursor_normal);
+   SDL_ShowCursor(1);
 }
 }
 
___
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]

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

[Natalia Portillo]

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.


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

Re: [Qemu-devel] QEMU 0.8.1

[Oliver Gerlich]

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

Re: [Qemu-devel] QEMU 0.8.1

[Natalia Portillo]

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

Re: [Qemu-devel] QEMU 0.8.1

[Anthony Liguori]

Christian MICHON wrote:

it works. Side effect: after the first ungrab, I can't see the host
pointer over the SDL windows.


Ok.  I'll take a look at that.  Should be easy enough to fix.



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 ?


As someone has already mentioned, you want to use -usb -usbdevice tablet.

Regards,

Anthony Liguori


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

Re: [Qemu-devel] QEMU 0.8.1

[Christian MICHON]

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

[Anthony Liguori]

Christian MICHON wrote:

on windows 3.0 (my usual testcase) ?
I'll try at least on rh72...


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.


Regards,

Anthony Liguori


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




___
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]

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

Re: [Qemu-devel] QEMU 0.8.1

[Anthony Liguori]

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

Re: [Qemu-devel] QEMU 0.8.1

[Jim C. Brown]

On Fri, May 05, 2006 at 10:43:06AM +0200, Natalia Portillo wrote:
> That requires a driver in guest side that communicates with qemu.

No it doesn't. It'd only work in absolute mode of course... but it'd be easy
to implement.

Personally I'd dislike such a feature anyways.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[Jim C. Brown]

On Fri, May 05, 2006 at 10:57:01AM -0500, Anthony Liguori wrote:
> 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
> 

I don't remember which kernel rh72 ships with.

However, you just need to modprobe evdev.o and use /dev/input/eventN (for me
the actual name of the event device varies, but there should only be a single
event device there).

The evtouch driver (tested with XFree86 4.2.1) should have no  issues with such 
a setup.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.


___
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]

thanks for the tips.
unfortunately, rh72 means xfree86 4.1.0 (event with updates)
xfree86 4.2 means at least rh73

I read somewhere that evtouch driver is actually for kernel 2.6
and at least xorg (not xfree 4.x). I tried to fiddle with the usb
tablet in rh72, but no luck yet.

One question: which driver is actually used for win98 guest ?

On 5/8/06, Jim C. Brown <[EMAIL PROTECTED]> wrote:

On Fri, May 05, 2006 at 10:57:01AM -0500, Anthony Liguori wrote:
> 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
>

I don't remember which kernel rh72 ships with.

However, you just need to modprobe evdev.o and use /dev/input/eventN (for me
the actual name of the event device varies, but there should only be a single
event device there).

The evtouch driver (tested with XFree86 4.2.1) should have no  issues with such 
a setup.

--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel




--
Christian


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[Brad Campbell]

Christian MICHON wrote:

thanks for the tips.
unfortunately, rh72 means xfree86 4.1.0 (event with updates)
xfree86 4.2 means at least rh73

I read somewhere that evtouch driver is actually for kernel 2.6
and at least xorg (not xfree 4.x). I tried to fiddle with the usb
tablet in rh72, but no luck yet.

One question: which driver is actually used for win98 guest ?


Windows built in hid driver.. works with absolute input messages out of the box.


--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[Jim C. Brown]

On Mon, May 08, 2006 at 10:12:15PM +0200, Christian MICHON wrote:
> thanks for the tips.
> unfortunately, rh72 means xfree86 4.1.0 (event with updates)
> xfree86 4.2 means at least rh73
> 

Can't hurt to try.

The driver I have was compiled against Xorg 6.8.2 but it works with
Xfree86 4.2.1

The official drivers are compiled against Xorg 6.8 but work with XFree86 4.0
(iirc), so there is a good chance the evtouch driver will work if u try it.

> I read somewhere that evtouch driver is actually for kernel 2.6
> and at least xorg (not xfree 4.x). I tried to fiddle with the usb
> tablet in rh72, but no luck yet.

evtouch definitely works with 4.x

The site claims that evtouch only works with 2.6 kernels though (rather, that
it has only been tested on 2.6 kernels). Looking at the source code of
evdev.c I don't see any obvious differences that would stop it from
functioning with the /dev/input/eventX interface of 2.4 though. I guess what we
really need is someone who can test. :)

> 
> One question: which driver is actually used for win98 guest ?
> 
> On 5/8/06, Jim C. Brown <[EMAIL PROTECTED]> wrote:
> >On Fri, May 05, 2006 at 10:57:01AM -0500, Anthony Liguori wrote:
> >> 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
> >>
> >
> >I don't remember which kernel rh72 ships with.
> >
> >However, you just need to modprobe evdev.o and use /dev/input/eventN (for 
> >me
> >the actual name of the event device varies, but there should only be a 
> >single
> >event device there).
> >
> >The evtouch driver (tested with XFree86 4.2.1) should have no  issues with 
> >such a setup.
> >
> >--
> >Infinite complexity begets infinite beauty.
> >Infinite precision begets infinite perfection.
> >
> >
> >___
> >Qemu-devel mailing list
> >Qemu-devel@nongnu.org
> >http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >
> 
> 
> --
> Christian
> 
> 
> ___
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1

[Thomas Han]

Hi Anthony,Sorry for the late reply.  I did try out the patch with my local build and I haven't see that  "invisible wall" mouse problem for a few days now.Thanks very much,Thomas
On 5/4/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> 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,> Thomas>> On 5/4/06, *Christian MICHON* < [EMAIL PROTECTED]> 
[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 be a lead.>> On 5/4/06, Christian MICHON <[EMAIL PROTECTED]> 
[EMAIL PROTECTED]>> wrote:> > I removed manually vnc_display_init, and this is not the culprit...> > I'll check anyway versus qemu-0.8.0...> >> --
> Christian>>> ___> Qemu-devel mailing list> Qemu-devel@nongnu.org 
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>diff -r 39a6dd1136c6 sdl.c--- a/sdl.c Thu May 04 04:13:13 2006 ++++ b/sdl.c Thu May 04 21:30:11 2006 -0500@@ -280,13 +280,18 @@ static void sdl_update_caption(void)
 static void sdl_hide_cursor(void) {-SDL_SetCursor(sdl_cursor_hidden);+if (kbd_mouse_is_absolute()) {+   SDL_ShowCursor(1);+   SDL_SetCursor(sdl_cursor_hidden);+} else {
+   SDL_ShowCursor(0);+} } static void sdl_show_cursor(void) { if (!kbd_mouse_is_absolute()) {-   SDL_SetCursor(sdl_cursor_normal);+   SDL_ShowCursor(1); }
 }___Qemu-devel mailing listQemu-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] Qemu 0.8.1 crash!!

[Luis Ramirez]

Hi,

I'm running the qemu 0.8.1 directly compiled from the sources with the
kqemu accelarator 1.3.0pre8 version.

I start it with the next command:

$sudo qemu -hda /home/luis/qemu/w2k_office_filezilla.img -hdb
/dev/hda1 -hdc /home/luis/qemu/w2k_data.img -net nic,vlan=0 -net
tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup -m 256M -localtime

I'm running a windows2000 inside with several partitions. hdc is an
encrypted partition (qcow format). When I access to the partition
administrative tool of W2000 qemu crash with the next output prints.

EAX=00010110 EBX=00c822e0 ECX=01010101 EDX=f3d9f84c
ESI=00c822e0 EDI=00c85028 EBP=0006f5d0 ESP=0006f5a8
EIP=77e149a7 EFL=00010246 [---Z-P-] CPL=3 II=0 A20=1 HLT=0
ES =0023   00cff300
CS =001b   00cffb00
SS =0023   00cff300
DS =0023   00cff300
FS =003b 7ffde000 0fff 7f40f3fd
GS =   
LDT=   8000
TR =0028 80652000 20ab 80008965
GDT= 80036000 03ff
IDT= 80036400 07ff
CR0=e001003b CR2=a00e1cfa CR3=09eec000 CR4=0690
Unsupported return value: 0x

If you need more details please lend me know. I'm not subscribed to
mailing list because I'm not a developer.

Good luck!

--
Luis Ramírez González.
--
< NO A LAS PATENTES DE SOFTWARE EN LA UE >
< STOP EU SOFTWARE PATENTS >
http://www.nosoftwarepatents.com/es/m/intro/index.html
http://swpat.ffii.org/index.es.html
LARG
--


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

[Qemu-devel] QEMU 0.8.1 crashes system

[vdr]

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 anything I can do for tracing that ? The 
trap is not reproducable.
Bye
Helmut





___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1 crashes system

[Helmut Auer]

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 anything I can do for tracing that ? The 
trap is not reproducable.

>
The problem should be reproducable by opening several explorer windows and 
changing to the mounted root drive of the qemu target.
When I do not use the windows explorer and only work on commandline no crash 
occurs.

--
Helmut Auer, [EMAIL PROTECTED]


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1 - Invisible wall

[Dan Sandberg]

Thomas Han wrote:


Hi Anthony,

Sorry for the late reply.  I did try out the patch with my local build 
and I

haven't see that  "invisible wall" mouse problem for a few days now.

Thanks very much,
Thomas

On 5/4/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

> 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,
> Thomas
>
> 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 be a lead.
>
> On 5/4/06, Christian MICHON <[EMAIL PROTECTED]
> > wrote:
> > I removed manually vnc_display_init, and this is not the
culprit...
> > I'll check anyway versus qemu-0.8.0...
> >
> --
> 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
>



diff -r 39a6dd1136c6 sdl.c
--- a/sdl.c Thu May 04 04:13:13 2006 +
+++ b/sdl.c Thu May 04 21:30:11 2006 -0500
@@ -280,13 +280,18 @@ static void sdl_update_caption(void)

static void sdl_hide_cursor(void)
{
-SDL_SetCursor(sdl_cursor_hidden);
+if (kbd_mouse_is_absolute()) {
+   SDL_ShowCursor(1);
+   SDL_SetCursor(sdl_cursor_hidden);
+} else {
+   SDL_ShowCursor(0);
+}
}

static void sdl_show_cursor(void)
{
 if (!kbd_mouse_is_absolute()) {
-   SDL_SetCursor(sdl_cursor_normal);
+   SDL_ShowCursor(1);
 }
}



___
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
 

On my installation (v0.8.1 with WindowsXP host) the "invisible wall" can 
be avoided or reproduced at will and I guess this indicates what´s wrong.


After leaving MouseGrab with Ctrl-Alt there will be an invisible wall if 
I reenter by clicking with the host's mouse pointer far away from where 
the quest-OS-pointer is. On the other hand if I reenter by carefully 
clicking exactly at the guest-OS-pointer they will be in sync and 
everything seems to be OK.
I haven´t been looking at the source-code, but my suggestion is that in 
the Click-event-handler where Mousegrab is entered the guest-OS pointer 
coordinates should be passed rather than the host's coordinates 
(simulating a click at the exakt right position).

Regards
Dan Sandberg






___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

[Qemu-devel] qemu-0.8.1 and Solaris-10

[Ishwar Rattan]

I was able to compile the qemu-cvs code with Taylor's
patches applied. I did not see a qemu executable? Is it
the same as qemu/aprc-softmmu/qemu-system-sparc? When
I try to  use it it keeps complaining that it can't
load::

/usr/local/share/qemu/proll.elf: No such file or directory
qemu: could not load prom '/usr/local/share/qemu/proll.bin'

I know I have not installed it in /usr/local as I do not
have the privileges but should this file be somewhere
in the qemu/* (where it was compiled)?

-ishwar



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

[Qemu-devel] qemu 0.8.1 && sparc-user && x86_64

[VMiklos]

hi

qemu 0.8.1 (0.8.0, too) fails to compile on x86_64 if sparc-user is
enabled:

gcc-3.3 -Wall -O2 -g -fno-strict-aliasing -I. -I..
-I/var/tmp/fst/src/qemu-0.8.1/target-sparc -I/var/tmp/fst/src/qemu-0.8.1
-I/var/tmp/fst/src/qemu-0.8.1/linux-user
-I/var/tmp/fst/src/qemu-0.8.1/linux-user/sparc -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/var/tmp/fst/src/qemu-0.8.1/fpu -I/var/tmp/fst/src/qemu-0.8.1/slirp -c
-o translate-op.o /var/tmp/fst/src/qemu-0.8.1/translate-op.c
In file included from /var/tmp/fst/src/qemu-0.8.1/translate-op.c:36:
op.h: In function `dyngen_code':
op.h:3759: error: syntax error before '.' token
op.h:3761: error: syntax error before '.' token
make[1]: *** [translate-op.o] Error 1
make[1]: Leaving directory `/var/tmp/fst/src/qemu-0.8.1/sparc-user'
make: *** [all] Error 1

is this a known issue?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

[Qemu-devel] Qemu-0.8.1 and Belneix-0.4.3?

[Ishwar Rattan]

Any one has had success with this combination?

Also, anyone running any x86 version of Solaris
under qemu? I would like a copy of the disk-image
if possible.

-ishwar



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

RE: [Qemu-devel] QEMU 0.8.1 and vnc

[Dugger, Donald D]

We've seen multiple issues with tightVNC, mainly because I don't believe
that tightvnc does resize requests at all.  Can you try a realvnc client
and see if you see the same issues?

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
[EMAIL PROTECTED]
Ph: (303)443-3786 

>-Original Message-
>From: [EMAIL PROTECTED] 
>[mailto:[EMAIL PROTECTED]
>] On Behalf Of Ben Taylor
>Sent: Friday, May 05, 2006 6:24 AM
>To: qemu-devel@nongnu.org
>Subject: [Qemu-devel] QEMU 0.8.1 and vnc
>
>
>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)
>
>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)
>
>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
>
>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 and Solaris-10

[Ben Taylor]

 Ishwar Rattan <[EMAIL PROTECTED]> wrote: 
> I was able to compile the qemu-cvs code with Taylor's
> patches applied. I did not see a qemu executable? Is it
> the same as qemu/aprc-softmmu/qemu-system-sparc? When
> I try to  use it it keeps complaining that it can't
> load::
> 
> /usr/local/share/qemu/proll.elf: No such file or directory
> qemu: could not load prom '/usr/local/share/qemu/proll.bin'
> 
> I know I have not installed it in /usr/local as I do not
> have the privileges but should this file be somewhere
> in the qemu/* (where it was compiled)?

Why don't you try installing it in your home directory, ie

./configure --prefix=/home/myhome/mqemu .

Qemu expects things to be installed, even if your debugging things,
otherwise you have use a bunch of flags to tell qemu where to find
the components.

Ben


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

[Qemu-devel] QEMU 0.8.1 VNC: Segfault on closing

[Michael McConnell]

When I try to use QEMU's VNC server, every time I close the connection it
segfaults.  So far I've been unable to trace the cause of this (gdb appears
to be next to useless at tracing the execution), but it is totally
repeatable.

Running with kqemu 1.3.0pre7 in -kernel-kqemu with Windows XP as the guest 
operating system, the host is an Athlon XP2000+ running kernel 2.6.14, and 
glibc 2.1.3. QEMU was compiled with gcc 3.4.3.

(I tried upgrading glibc, had to restore the machine from a backup.)

Any pointers would be much appreciated...

-- Michael "Soruk" McConnell
   Eridani Star System

   MailStripper - http://www.MailStripper.eu/ - SMTP spam filter
   Mail Me Anywhere - http://www.MailMeAnywhere.com/ - Mobile email



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] Qemu-0.8.1 and Belneix-0.4.3?

[Ben Taylor]

 Ishwar Rattan <[EMAIL PROTECTED]> wrote: 
> Any one has had success with this combination?

Haven't tried it yet.
> 
> Also, anyone running any x86 version of Solaris
> under qemu? I would like a copy of the disk-image
> if possible.

Depending on the version of Solaris x86 you want to run,
the best way to get Solaris running is to apply the acpi
patch that was posted to the list (and run the iasl against
it to create the hex file) and grab a dvd image (or burn
the dvd if short of the 2.5G that the dvd images requires)
and install Solaris.

Hints for installing Solaris under qemu:

1) At a minimum, you will need at least a 4-5GB qemu image file
to load all of Solaris on.  Even the developer subset is probably
around 3GB.  a bare minimum install is a 3-400MB, but is barely
usable unless you like a bare system with no X.

2) solaris 8/9/10 FCS - at least 256 MB of memory, 384 is better.  
solaris 10 U1 or better, or Solaris Express (11) really needs
384 at a bare minimum or 512 to do the graphical install. I prefer
the text install, just to keep the overhead down.

You can configure the xorg driver to do 1152x864 (IIRC) at the
maximum resolution. Default should be around 1024x768. You
can also do this very easily post reboot if you've done a text
install.  (Though build 38 or 39 of Solaris Express does  a really
job of picking the right resolution for displaying)

3) If loading S10U1 or Solaris express (11),  you'll need to edit the
initial grub boot menu, and add ",atapi-cd-dma-enabled=0" after
the "-B "

While I haven't installed 8, 9 or 10FCS recently, you may or may not
have to go into the DCS (Device configuration setup), and modify
the parameter acpi-user-options=0x2.  This will be F4 at the boot
   device selection menu.  I haven't tested this these older releases with
the acpi patch, so you might not have to do this.

4) Download the DU Install Time Update (ITU) floppy from 
tools.de/solaris/itu.  There is one for Solaris 9/10, and one
for Solaris Express (Nevada).  This driver disk has a modified
version of Murayama's ni driver (ne2000) that works with qemu.
   For Solaris 9 and 10/FCS, you will hit F4 in the DCS menu to install
   the ITU.  For Solaris Express and Solaris 10 U1 or later, you will
   have to do it once the machine is booted (IIRC, select #5).  The
   ACPI patch is important here because Sun's grub boot code doesn't
   correctly enumerate an ISA floppy.  The ACPI patch allows Solaris
   to recognize the floppy, and therefore you can do an Install time 
   update.

HTH,

Ben


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

[Qemu-devel] qemu-0.8.1-cvs patch for Solaris/sparc

[Ben Taylor]

Enclosed is a set of patches that allows qemu-0.8.1-cvs to be compiled on 
Solaris 10
Sparc systems and run x86 software (tested DamnSmallLinux and Win98SE).  I will 
be following up with a second patch which corrects the bgr colors that 
Solaris/Sparc 
natviely displays, but am keeping it separate due to the amount of discussion 
that has 
gone on previously to correctly handling the rgb vs bgr color map issue.

I have to attribute Fabrice in the patch to slirp/if.c and slirp/slirp.c for 
adding some code
that fixed an unalignment error on Solaris/Sparc without the need for a 
"asm("ta 6"); 
directive to allow unaligned access.  However, that patch wasn't put into CVS 
yet, so
I am including it for those who want to get going now.

Ben

diff -ruN qemu-presol-sparc/Makefile qemu/Makefile
--- qemu-presol-sparc/Makefile	2006-04-30 19:54:18.0 -0400
+++ qemu/Makefile	2006-05-10 12:22:47.141367000 -0400
@@ -4,6 +4,9 @@
 ifdef CONFIG_DARWIN
 CFLAGS+= -mdynamic-no-pic
 endif
+ifeq ($(ARCH),sparc)
+CFLAGS+=-mcpu=ultrasparc
+endif
 LDFLAGS=-g
 LIBS=
 DEFINES+=-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
diff -ruN qemu-presol-sparc/Makefile.target qemu/Makefile.target
--- qemu-presol-sparc/Makefile.target	2006-05-03 18:02:44.0 -0400
+++ qemu/Makefile.target	2006-05-10 12:22:55.952904000 -0400
@@ -102,6 +102,11 @@
 endif
 
 ifeq ($(ARCH),sparc)
+ifeq ($(CONFIG_SOLARIS),yes)
+CFLAGS+=-mcpu=ultrasparc -m32 -ffixed-g2 -ffixed-g3
+LDFLAGS+=-m32
+OP_CFLAGS=$(CFLAGS) -fno-delayed-branch -fno-omit-frame-pointer -ffixed-i0
+else
 CFLAGS+=-m32 -ffixed-g1 -ffixed-g2 -ffixed-g3 -ffixed-g6
 LDFLAGS+=-m32
 OP_CFLAGS=$(CFLAGS) -fno-delayed-branch -ffixed-i0
@@ -109,6 +114,7 @@
 # -static is used to avoid g1/g3 usage by the dynamic linker
 LDFLAGS+=-Wl,-T,$(SRC_PATH)/sparc.ld -static
 endif
+endif
 
 ifeq ($(ARCH),sparc64)
 CFLAGS+=-m64 -ffixed-g1 -ffixed-g2 -ffixed-g3 -ffixed-g6
diff -ruN qemu-presol-sparc/cpu-exec.c qemu/cpu-exec.c
--- qemu-presol-sparc/cpu-exec.c	2006-04-27 17:05:14.0 -0400
+++ qemu/cpu-exec.c	2006-05-10 12:23:23.286414000 -0400
@@ -253,7 +253,7 @@
 uint32_t *saved_regwptr;
 #endif
 #endif
-#ifdef __sparc__
+#if defined(__sparc__) && !defined(HOST_SOLARIS)
 int saved_i7, tmp_T0;
 #endif
 int ret, interrupt_request;
@@ -323,7 +323,7 @@
 #if defined(reg_T2)
 saved_T2 = T2;
 #endif
-#ifdef __sparc__
+#if defined(__sparc__) && !defined(HOST_SOLARIS)
 /* we also save i7 because longjmp may not restore it */
 asm volatile ("mov %%i7, %0" : "=r" (saved_i7));
 #endif
@@ -447,7 +447,7 @@
 
 T0 = 0; /* force lookup of first TB */
 for(;;) {
-#ifdef __sparc__
+#if defined(__sparc__) && !defined(HOST_SOLARIS)
 /* g1 can be modified by some libc? functions */ 
 tmp_T0 = T0;
 #endif	
@@ -467,7 +467,7 @@
 do_interrupt(intno, 0, 0, 0, 1);
 /* ensure that no TB jump will be modified as
the program flow was changed */
-#ifdef __sparc__
+#if defined(__sparc__) && !defined(HOST_SOLARIS)
 tmp_T0 = 0;
 #else
 T0 = 0;
@@ -486,7 +486,7 @@
 			env->error_code = 0;
 do_interrupt(env);
 env->interrupt_request &= ~CPU_INTERRUPT_HARD;
-#ifdef __sparc__
+#if defined(__sparc__) && !defined(HOST_SOLARIS)
 tmp_T0 = 0;
 #else
 T0 = 0;
@@ -497,7 +497,7 @@
 env->error_code = 0;
 do_interrupt(env);
 env->interrupt_request &= ~CPU_INTERRUPT_TIMER;
-#ifdef __sparc__
+#if defined(__sparc__) && !defined(HOST_SOLARIS)
 tmp_T0 = 0;
 #else
 T0 = 0;
@@ -516,7 +516,7 @@
 env->error_code = 0;
 do_interrupt(env);
 env->interrupt_request &= ~CPU_INTERRUPT_HARD;
-#ifdef __sparc__
+#if defined(__sparc__) && !defined(HOST_SOLARIS)
 tmp_T0 = 0;
 #else
 T0 = 0;
@@ -534,7 +534,7 @@
 			env->interrupt_request &= ~CPU_INTERRUPT_HARD;
 			do_interrupt(env->interrupt_index);
 			env->interrupt_index = 0;
-#ifdef __sparc__
+#if defined(__sparc__) && !defined(HOST_SOLARIS)
 tmp_T0 = 0;
 #else
 T0 = 0;
@@ -565,7 +565,7 @@
 env->interrupt_request &= ~CPU_INTERRUPT_EXITTB;
 /* ensure that no TB jump will be modified as
the program flow was changed */
-#ifdef __sparc__
+#if defined(__sparc__) && !defined(HOST_SOLARIS)
 tmp_T0 = 0;
 #else
 T0 = 0;
@@ -633,7 +633,7 @@
 lookup_symbol(tb->pc));
 }
 #endif
-#ifdef __sparc__
+#if defined(__s

Re: [Qemu-devel] QEMU 0.8.1 VNC: Segfault on closing

[Anthony Liguori]

Michael McConnell wrote:

When I try to use QEMU's VNC server, every time I close the connection it
segfaults.  So far I've been unable to trace the cause of this (gdb appears
to be next to useless at tracing the execution), but it is totally
repeatable.
  


Can you provide more information?  What VNC client are you using?  What 
host architecture are you on?  What is the guest OS/target?


Can you provide a stack trace that leads to the seg fault?

Regards,

Anthony Liguori

Running with kqemu 1.3.0pre7 in -kernel-kqemu with Windows XP as the guest 
operating system, the host is an Athlon XP2000+ running kernel 2.6.14, and 
glibc 2.1.3. QEMU was compiled with gcc 3.4.3.


(I tried upgrading glibc, had to restore the machine from a backup.)

Any pointers would be much appreciated...

-- Michael "Soruk" McConnell
   Eridani Star System

   MailStripper - http://www.MailStripper.eu/ - SMTP spam filter
   Mail Me Anywhere - http://www.MailMeAnywhere.com/ - Mobile email



___
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

Re: [Qemu-devel] QEMU 0.8.1 VNC: Segfault on closing

[Michael McConnell]

On Sun, 21 May 2006, Anthony Liguori wrote:

> Michael McConnell wrote:
> > When I try to use QEMU's VNC server, every time I close the connection it
> > segfaults.  So far I've been unable to trace the cause of this (gdb appears
> > to be next to useless at tracing the execution), but it is totally
> > repeatable.
> >   
> 
> Can you provide more information?  What VNC client are you using? 

TightVNC 1.2.9 - and the fault can also be triggered by just telnetting to 
the VNC port and closing the connection.

> What 
> host architecture are you on?  What is the guest OS/target?

I already gave that - REinserting immediately below.
(It was in the second paragraph, which you inserted your reply above.)
For those not familiar with AMD, the Athlon
XP2000+ is an ix86 32-bit CPU.

> > Running with kqemu 1.3.0pre7 in -kernel-kqemu with Windows XP as the guest 
> > operating system, the host is an Athlon XP2000+ running kernel 2.6.14, and 
> > glibc 2.1.3. QEMU was compiled with gcc 3.4.3.

> Can you provide a stack trace that leads to the seg fault?

GDB seems unable to - this is how it started off when analysing the core 
dump:
[EMAIL PROTECTED] QEMU]# gdb /usr/local/bin/qemu-i386 core
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...

Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.

Core was generated by `qemu-i386 -m 128 -sync -kernel-kqemu -boot c -net 
nic,macaddr=fe:fd:00:00:00:01'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libm.so.6...done.
Reading symbols from /usr/lib/libz.so.1...done.
Reading symbols from /usr/local/lib/libSDL-1.2.so.0...done.
Reading symbols from /lib/libpthread.so.0...done.
Reading symbols from /lib/libutil.so.1...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/libdl.so.2...done.
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0  0x804ff4a in ?? ()
(gdb) bt
#0  0x804ff4a in ?? ()
(gdb) quit
[EMAIL PROTECTED] QEMU]# gdb ls

I have no idea what this "dwarf error" is.

-- Michael "Soruk" McConnell
   Eridani Star System

   MailStripper - http://www.MailStripper.eu/ - SMTP spam filter
   Mail Me Anywhere - http://www.MailMeAnywhere.com/ - Mobile email



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.8.1 VNC: Segfault on closing

[Anthony Liguori]

Michael McConnell wrote:

On Sun, 21 May 2006, Anthony Liguori wrote:

  

Michael McConnell wrote:


When I try to use QEMU's VNC server, every time I close the connection it
segfaults.  So far I've been unable to trace the cause of this (gdb appears
to be next to useless at tracing the execution), but it is totally
repeatable.
  
  
Can you provide more information?  What VNC client are you using? 



TightVNC 1.2.9 - and the fault can also be triggered by just telnetting to 
the VNC port and closing the connection.
  


Curious, I've not seen this myself and your configuration does not seem 
out of the ordinary.


Can you try with CVS and 0.8.1?  Also, make sure that you're doing a 
full build if you've built this from CVS as the dependences in the 
Makefile aren't good.


Regards,

Anthony Liguori

  
What 
host architecture are you on?  What is the guest OS/target?



I already gave that - REinserting immediately below.
(It was in the second paragraph, which you inserted your reply above.)
For those not familiar with AMD, the Athlon
XP2000+ is an ix86 32-bit CPU.

  
Running with kqemu 1.3.0pre7 in -kernel-kqemu with Windows XP as the guest 
operating system, the host is an Athlon XP2000+ running kernel 2.6.14, and 
glibc 2.1.3. QEMU was compiled with gcc 3.4.3.
  


  

Can you provide a stack trace that leads to the seg fault?



GDB seems unable to - this is how it started off when analysing the core 
dump:

[EMAIL PROTECTED] QEMU]# gdb /usr/local/bin/qemu-i386 core
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...

Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.

Core was generated by `qemu-i386 -m 128 -sync -kernel-kqemu -boot c -net 
nic,macaddr=fe:fd:00:00:00:01'.

Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libm.so.6...done.
Reading symbols from /usr/lib/libz.so.1...done.
Reading symbols from /usr/local/lib/libSDL-1.2.so.0...done.
Reading symbols from /lib/libpthread.so.0...done.
Reading symbols from /lib/libutil.so.1...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/libdl.so.2...done.
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0  0x804ff4a in ?? ()
(gdb) bt
#0  0x804ff4a in ?? ()
(gdb) quit
[EMAIL PROTECTED] QEMU]# gdb ls

I have no idea what this "dwarf error" is.

-- Michael "Soruk" McConnell
   Eridani Star System

   MailStripper - http://www.MailStripper.eu/ - SMTP spam filter
   Mail Me Anywhere - http://www.MailMeAnywhere.com/ - Mobile email



___
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

Re: [Qemu-devel] QEMU 0.8.1 VNC: Segfault on closing

[Michael McConnell]

On Sun, 21 May 2006, Anthony Liguori wrote:

> Michael McConnell wrote:
> > On Sun, 21 May 2006, Anthony Liguori wrote:
> >
> >   
> >> Michael McConnell wrote:
> >> 
> >>> When I try to use QEMU's VNC server, every time I close the connection it
> >>> segfaults.  So far I've been unable to trace the cause of this (gdb 
> >>> appears
> >>> to be next to useless at tracing the execution), but it is totally
> >>> repeatable.
> >>>   
> >> Can you provide more information?  What VNC client are you using? 
> >
> > TightVNC 1.2.9 - and the fault can also be triggered by just telnetting to 
> > the VNC port and closing the connection.
> 
> Curious, I've not seen this myself and your configuration does not seem 
> out of the ordinary.
> 
> Can you try with CVS and 0.8.1?  Also, make sure that you're doing a 
> full build if you've built this from CVS as the dependences in the 
> Makefile aren't good.

Not having quite figured out how to get CVS to work as I so rarely have to
use it (nor could I find a link on qemu.org) I tried with the
qemu-snapshot-2006-05-21_23.tar.bz2 snapshot from qemu.dad-answers.com.  And
ran into exactly the same problem.  gdb is equally useless on this build too.

-- Michael "Soruk" McConnell
   Eridani Star System

   MailStripper - http://www.MailStripper.eu/ - SMTP spam filter
   Mail Me Anywhere - http://www.MailMeAnywhere.com/ - Mobile email



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] qemu-0.8.1-cvs patch for Solaris/sparc

[Ishwar Rattan]

On Wed, 10 May 2006, Ben Taylor wrote:

>
> Enclosed is a set of patches that allows qemu-0.8.1-cvs to be compiled on 
> Solaris 10
> Sparc systems and run x86 software (tested DamnSmallLinux and Win98SE).  I 
> will

Is thre a support for Sun-Blade-100 based system? I tried to compile
the 0.8.1 version, and it quit with message that the processor is
unknown.

-ishwar



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

[Qemu-devel] qemu-0.8.1 compile errors on x86_64 suse linux 10.1

[Doctor Bill]

At first I thought the problem was that I was using gcc-4, so I installed gcc-3.4.6, but I still get the same errors:gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I.. -I/tmp/qemu-0.8.1/target-i386 -I/tmp/qemu-0.8.1
 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/tmp/qemu-0.8.1/fpu -DHAS_AUDIO -I/tmp/qemu-0.8.1/slirp -c -o usb-linux.o /tmp/qemu-0.8.1/usb-linux.cIn file included from /tmp/qemu-0.8.1/usb-linux.c:29:
/usr/include/linux/usbdevice_fs.h:49: error: variable or field `__user' declared void/usr/include/linux/usbdevice_fs.h:49: error: syntax error before '*' token/usr/include/linux/usbdevice_fs.h:56: error: variable or field `__user' declared void
/usr/include/linux/usbdevice_fs.h:56: error: syntax error before '*' token/usr/include/linux/usbdevice_fs.h:66: error: variable or field `__user' declared void/usr/include/linux/usbdevice_fs.h:66: error: syntax error before '*' token
/usr/include/linux/usbdevice_fs.h:100: error: variable or field `__user' declared void/usr/include/linux/usbdevice_fs.h:100: error: syntax error before '*' token/usr/include/linux/usbdevice_fs.h:109: error: syntax error before '}' token
/usr/include/linux/usbdevice_fs.h:116: error: variable or field `__user' declared void/usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*' token/tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_control':
/tmp/qemu-0.8.1/usb-linux.c:91: error: invalid application of `sizeof' to incomplete type `usbdevfs_ctrltransfer'/tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_data':/tmp/qemu-0.8.1/usb-linux.c:110: error: storage size of 'bt' isn't known
/tmp/qemu-0.8.1/usb-linux.c:121: error: invalid application of `sizeof' to incomplete type `usbdevfs_bulktransfer'/tmp/qemu-0.8.1/usb-linux.c:110: warning: unused variable `bt'/tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_device_open':
/tmp/qemu-0.8.1/usb-linux.c:185: error: storage size of 'ctrl' isn't known/tmp/qemu-0.8.1/usb-linux.c:188: error: invalid application of `sizeof' to incomplete type `usbdevfs_ioctl'/tmp/qemu-0.8.1/usb-linux.c:185: warning: unused variable `ctrl'
make[1]: *** [usb-linux.o] Error 1make[1]: Leaving directory `/tmp/x/i386-softmmu'make: *** [all] Error 1[EMAIL PROTECTED]:/tmp/x> makefor d in i386-user arm-user armeb-user sparc-user ppc-user mips-user mipsel-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu mipsel-softmmu arm-softmmu; do \
make -C $d all || exit 1 ; \    donemake[1]: Entering directory `/tmp/x/i386-user'make[1]: Nothing to be done for `all'.make[1]: Leaving directory `/tmp/x/i386-user'make[1]: Entering directory `/tmp/x/arm-user'
make[1]: Nothing to be done for `all'.make[1]: Leaving directory `/tmp/x/arm-user'make[1]: Entering directory `/tmp/x/armeb-user'make[1]: Nothing to be done for `all'.make[1]: Leaving directory `/tmp/x/armeb-user'
make[1]: Entering directory `/tmp/x/sparc-user'make[1]: Nothing to be done for `all'.make[1]: Leaving directory `/tmp/x/sparc-user'make[1]: Entering directory `/tmp/x/ppc-user'make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/tmp/x/ppc-user'make[1]: Entering directory `/tmp/x/mips-user'make[1]: Nothing to be done for `all'.make[1]: Leaving directory `/tmp/x/mips-user'make[1]: Entering directory `/tmp/x/mipsel-user'
make[1]: Nothing to be done for `all'.make[1]: Leaving directory `/tmp/x/mipsel-user'make[1]: Entering directory `/tmp/x/i386-softmmu'gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I.. -I/tmp/qemu-0.8.1/target-i386 -I/tmp/qemu-
0.8.1 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/tmp/qemu-0.8.1/fpu -DHAS_AUDIO -I/tmp/qemu-0.8.1/slirp -c -o usb-linux.o /tmp/qemu-0.8.1/usb-linux.cIn file included from /tmp/qemu-0.8.1/usb-linux.c:29:
/usr/include/linux/usbdevice_fs.h:49: error: variable or field `__user' declared void/usr/include/linux/usbdevice_fs.h:49: error: syntax error before '*' token/usr/include/linux/usbdevice_fs.h:56: error: variable or field `__user' declared void
/usr/include/linux/usbdevice_fs.h:56: error: syntax error before '*' token/usr/include/linux/usbdevice_fs.h:66: error: variable or field `__user' declared void/usr/include/linux/usbdevice_fs.h:66: error: syntax error before '*' token
/usr/include/linux/usbdevice_fs.h:100: error: variable or field `__user' declared void/usr/include/linux/usbdevice_fs.h:100: error: syntax error before '*' token/usr/include/linux/usbdevice_fs.h:109: error: syntax error before '}' token
/usr/include/linux/usbdevice_fs.h:116: error: variable or field `__user' declared void/usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*' token/tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_control':
/tmp/qemu-0.8.1/usb-linux.c:91: error: invalid application of `sizeof' to incomplete type `usbdevfs_ctrltransfer'/tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_data':/tmp/qemu-0.8.1/usb-linux.c:110: error: storage size of 'bt' isn't known
/tmp/qemu-0.8.1/usb-linux.c:121: error: invalid application o

Re: [Qemu-devel] qemu-0.8.1 compile errors on x86_64 suse linux 10.1

[Jim C. Brown]

The issue is with your linux kernel headers.

On Sat, Jul 08, 2006 at 11:07:57AM -0400, Doctor Bill wrote:
> At first I thought the problem was that I was using gcc-4, so I installed
> gcc-3.4.6, but I still get the same errors:
> 
> gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I..
> -I/tmp/qemu-0.8.1/target-i386
> -I/tmp/qemu-0.8.1 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> -I/tmp/qemu-0.8.1/fpu -DHAS_AUDIO -I/tmp/qemu-0.8.1/slirp -c -o
> usb-linux.o/tmp/qemu-
> 0.8.1/usb-linux.c
> In file included from /tmp/qemu-0.8.1/usb-linux.c:29:
> /usr/include/linux/usbdevice_fs.h:49: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:49: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:56: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:56: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:66: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:66: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:100: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:100: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:109: error: syntax error before '}' token
> /usr/include/linux/usbdevice_fs.h:116: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*' token
> /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_control':
> /tmp/qemu-0.8.1/usb-linux.c:91: error: invalid application of `sizeof' to
> incomplete type `usbdevfs_ctrltransfer'
> /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_data':
> /tmp/qemu-0.8.1/usb-linux.c:110: error: storage size of 'bt' isn't known
> /tmp/qemu-0.8.1/usb-linux.c:121: error: invalid application of `sizeof' to
> incomplete type `usbdevfs_bulktransfer'
> /tmp/qemu-0.8.1/usb-linux.c:110: warning: unused variable `bt'
> /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_device_open':
> /tmp/qemu-0.8.1/usb-linux.c:185: error: storage size of 'ctrl' isn't known
> /tmp/qemu-0.8.1/usb-linux.c:188: error: invalid application of `sizeof' to
> incomplete type `usbdevfs_ioctl'
> /tmp/qemu-0.8.1/usb-linux.c:185: warning: unused variable `ctrl'
> make[1]: *** [usb-linux.o] Error 1
> make[1]: Leaving directory `/tmp/x/i386-softmmu'
> make: *** [all] Error 1
> [EMAIL PROTECTED]:/tmp/x> make
> for d in i386-user arm-user armeb-user sparc-user ppc-user mips-user
> mipsel-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu
> mips-softmmu mipsel-softmmu arm-softmmu; do \
> make -C $d all || exit 1 ; \
>done
> make[1]: Entering directory `/tmp/x/i386-user'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/tmp/x/i386-user'
> make[1]: Entering directory `/tmp/x/arm-user'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/tmp/x/arm-user'
> make[1]: Entering directory `/tmp/x/armeb-user'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/tmp/x/armeb-user'
> make[1]: Entering directory `/tmp/x/sparc-user'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/tmp/x/sparc-user'
> make[1]: Entering directory `/tmp/x/ppc-user'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/tmp/x/ppc-user'
> make[1]: Entering directory `/tmp/x/mips-user'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/tmp/x/mips-user'
> make[1]: Entering directory `/tmp/x/mipsel-user'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/tmp/x/mipsel-user'
> make[1]: Entering directory `/tmp/x/i386-softmmu'
> gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I..
> -I/tmp/qemu-0.8.1/target-i386
> -I/tmp/qemu-0.8.1 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> -I/tmp/qemu-0.8.1/fpu -DHAS_AUDIO -I/tmp/qemu-0.8.1/slirp -c -o
> usb-linux.o/tmp/qemu-
> 0.8.1/usb-linux.c
> In file included from /tmp/qemu-0.8.1/usb-linux.c:29:
> /usr/include/linux/usbdevice_fs.h:49: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:49: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:56: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:56: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:66: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:66: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:100: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:100: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:109: error: syntax error before '}' token
> /usr/include/linux/usbdevice_fs.h:116: error: variable or field `__user'
> declared void
> /usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*' token
> /tmp/qemu-0.8.1/usb-linux.c: In funct

Re: [Qemu-devel] qemu-0.8.1 compile errors on x86_64 suse linux 10.1

[Bill C. Riemers]

Good guess, SuSE makes many modifications to the standard kernel.  However, the kernel source is not the problem.  I downloaded fresh kernel source from www.kernel.org, and I still have the exact same error.  Here are the relevant details:
QEMU version: qemu-0.8.1Linux Kernel: 2.6.16.13Operating System: SuSE 10.1gcc version: 3.4.6CPU: Amd Athlon(tm) Processor 3200+Bill
On 7/8/06, Jim C. Brown <[EMAIL PROTECTED]> wrote:
The issue is with your linux kernel headers.On Sat, Jul 08, 2006 at 11:07:57AM -0400, Doctor Bill wrote:> At first I thought the problem was that I was using gcc-4, so I installed> gcc-3.4.6, but I still get the same errors:
>> gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I..> -I/tmp/qemu-0.8.1/target-i386> -I/tmp/qemu-0.8.1 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE> -I/tmp/qemu-0.8.1/fpu -DHAS_AUDIO -I/tmp/qemu-
0.8.1/slirp -c -o> usb-linux.o/tmp/qemu-> 0.8.1/usb-linux.c> In file included from /tmp/qemu-0.8.1/usb-linux.c:29:> /usr/include/linux/usbdevice_fs.h:49: error: variable or field `__user'> declared void
> /usr/include/linux/usbdevice_fs.h:49: error: syntax error before '*' token> /usr/include/linux/usbdevice_fs.h:56: error: variable or field `__user'> declared void> /usr/include/linux/usbdevice_fs.h:56: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:66: error: variable or field `__user'> declared void> /usr/include/linux/usbdevice_fs.h:66: error: syntax error before '*' token> /usr/include/linux/usbdevice_fs.h:100: error: variable or field `__user'
> declared void> /usr/include/linux/usbdevice_fs.h:100: error: syntax error before '*' token> /usr/include/linux/usbdevice_fs.h:109: error: syntax error before '}' token> /usr/include/linux/usbdevice_fs.h:116: error: variable or field `__user'
> declared void> /usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*' token> /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_control':> /tmp/qemu-0.8.1/usb-linux.c:91: error: invalid application of `sizeof' to
> incomplete type `usbdevfs_ctrltransfer'> /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_data':> /tmp/qemu-0.8.1/usb-linux.c:110: error: storage size of 'bt' isn't known> /tmp/qemu-
0.8.1/usb-linux.c:121: error: invalid application of `sizeof' to> incomplete type `usbdevfs_bulktransfer'> /tmp/qemu-0.8.1/usb-linux.c:110: warning: unused variable `bt'> /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_device_open':
> /tmp/qemu-0.8.1/usb-linux.c:185: error: storage size of 'ctrl' isn't known> /tmp/qemu-0.8.1/usb-linux.c:188: error: invalid application of `sizeof' to> incomplete type `usbdevfs_ioctl'> /tmp/qemu-
0.8.1/usb-linux.c:185: warning: unused variable `ctrl'> make[1]: *** [usb-linux.o] Error 1> make[1]: Leaving directory `/tmp/x/i386-softmmu'> make: *** [all] Error 1> [EMAIL PROTECTED]:/tmp/x> make
> for d in i386-user arm-user armeb-user sparc-user ppc-user mips-user> mipsel-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu> mips-softmmu mipsel-softmmu arm-softmmu; do \> make -C $d all || exit 1 ; \
>done> make[1]: Entering directory `/tmp/x/i386-user'> make[1]: Nothing to be done for `all'.> make[1]: Leaving directory `/tmp/x/i386-user'> make[1]: Entering directory `/tmp/x/arm-user'
> make[1]: Nothing to be done for `all'.> make[1]: Leaving directory `/tmp/x/arm-user'> make[1]: Entering directory `/tmp/x/armeb-user'> make[1]: Nothing to be done for `all'.> make[1]: Leaving directory `/tmp/x/armeb-user'
> make[1]: Entering directory `/tmp/x/sparc-user'> make[1]: Nothing to be done for `all'.> make[1]: Leaving directory `/tmp/x/sparc-user'> make[1]: Entering directory `/tmp/x/ppc-user'> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/tmp/x/ppc-user'> make[1]: Entering directory `/tmp/x/mips-user'> make[1]: Nothing to be done for `all'.> make[1]: Leaving directory `/tmp/x/mips-user'> make[1]: Entering directory `/tmp/x/mipsel-user'
> make[1]: Nothing to be done for `all'.> make[1]: Leaving directory `/tmp/x/mipsel-user'> make[1]: Entering directory `/tmp/x/i386-softmmu'> gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I..
> -I/tmp/qemu-0.8.1/target-i386> -I/tmp/qemu-0.8.1 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE> -I/tmp/qemu-0.8.1/fpu -DHAS_AUDIO -I/tmp/qemu-0.8.1/slirp -c -o> usb-linux.o/tmp/qemu-
> 0.8.1/usb-linux.c> In file included from /tmp/qemu-0.8.1/usb-linux.c:29:> /usr/include/linux/usbdevice_fs.h:49: error: variable or field `__user'> declared void> /usr/include/linux/usbdevice_fs.h:49: error: syntax error before '*' token
> /usr/include/linux/usbdevice_fs.h:56: error: variable or field `__user'> declared void> /usr/include/linux/usbdevice_fs.h:56: error: syntax error before '*' token> /usr/include/linux/usbdevice_fs.h:66: error: variable or field `__user'
> declared void> /usr/include/linux/usbdevice_fs.h:66: error: syntax error before '*' token> /usr/include/linux/usbdevice_fs.h:100: error: variable or field `__user'> declared void> /usr/includ

Re: [Qemu-devel] qemu-0.8.1 compile errors on x86_64 suse linux 10.1

[Damien Mascord]

Bill C. Riemers wrote:
> Good guess, SuSE makes many modifications to the standard kernel.  However,
> the kernel source is not the problem.  I downloaded fresh kernel source
> from
> www.kernel.org, and I still have the exact same error.  Here are the
> relevant details:
> 
> QEMU version: qemu-0.8.1
> Linux Kernel: 2.6.16.13
> Operating System: SuSE 10.1
> gcc version: 3.4.6
> CPU: Amd Athlon(tm) Processor 3200+
> 
> Bill

Hi Bill,

NOTE: Jim, if I am totally misrepresenting your comment, my apologies :)

I think Jim is pointing to the linux kernel headers, and not necessarily the 
kernel source.

The linux kernel headers that are used to build your local glibc, and hence 
even if you use the virgin kernel source and load that
particular kernel, you will have to rebuild your glibc against those kernel 
sources.

You will probably have to symlink the relevant directories so that when you 
build your glibc, it will pick up the virgin headers
instead of the SuSE modified ones.

Once you have a clean system, running on a virgin kernel, running on a glibc 
compiled against the kernel headers of that virgin
kernel, and then attempt to compile qemu with gcc 3.x, you will likely not run 
into any problems.

If you still have problems, perhaps you need to recompile said gcc with the 
virgin headers too.

Hope to help,

Damien


> On 7/8/06, Jim C. Brown <[EMAIL PROTECTED]> wrote:
>>
>> The issue is with your linux kernel headers.
>>
>> On Sat, Jul 08, 2006 at 11:07:57AM -0400, Doctor Bill wrote:
>> > At first I thought the problem was that I was using gcc-4, so I
>> installed
>> > gcc-3.4.6, but I still get the same errors:
>> >
>> > gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I..
>> > -I/tmp/qemu-0.8.1/target-i386
>> > -I/tmp/qemu-0.8.1 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
>> -D_LARGEFILE_SOURCE
>> > -I/tmp/qemu-0.8.1/fpu -DHAS_AUDIO -I/tmp/qemu-0.8.1/slirp -c -o
>> > usb-linux.o/tmp/qemu-
>> > 0.8.1/usb-linux.c
>> > In file included from /tmp/qemu-0.8.1/usb-linux.c:29:
>> > /usr/include/linux/usbdevice_fs.h:49: error: variable or field `__user'
>> > declared void
>> > /usr/include/linux/usbdevice_fs.h:49: error: syntax error before '*'
>> token
>> > /usr/include/linux/usbdevice_fs.h:56: error: variable or field `__user'
>> > declared void
>> > /usr/include/linux/usbdevice_fs.h:56: error: syntax error before '*'
>> token
>> > /usr/include/linux/usbdevice_fs.h:66: error: variable or field `__user'
>> > declared void
>> > /usr/include/linux/usbdevice_fs.h:66: error: syntax error before '*'
>> token
>> > /usr/include/linux/usbdevice_fs.h:100: error: variable or field
>> `__user'
>> > declared void
>> > /usr/include/linux/usbdevice_fs.h:100: error: syntax error before '*'
>> token
>> > /usr/include/linux/usbdevice_fs.h:109: error: syntax error before '}'
>> token
>> > /usr/include/linux/usbdevice_fs.h:116: error: variable or field
>> `__user'
>> > declared void
>> > /usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*'
>> token
>> > /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_control':
>> > /tmp/qemu-0.8.1/usb-linux.c:91: error: invalid application of `sizeof'
>> to
>> > incomplete type `usbdevfs_ctrltransfer'
>> > /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_data':
>> > /tmp/qemu-0.8.1/usb-linux.c:110: error: storage size of 'bt' isn't
>> known
>> > /tmp/qemu-0.8.1/usb-linux.c:121: error: invalid application of `sizeof'
>> to
>> > incomplete type `usbdevfs_bulktransfer'
>> > /tmp/qemu-0.8.1/usb-linux.c:110: warning: unused variable `bt'
>> > /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_device_open':
>> > /tmp/qemu-0.8.1/usb-linux.c:185: error: storage size of 'ctrl' isn't
>> known
>> > /tmp/qemu-0.8.1/usb-linux.c:188: error: invalid application of `sizeof'
>> to
>> > incomplete type `usbdevfs_ioctl'
>> > /tmp/qemu-0.8.1/usb-linux.c:185: warning: unused variable `ctrl'
>> > make[1]: *** [usb-linux.o] Error 1
>> > make[1]: Leaving directory `/tmp/x/i386-softmmu'
>> > make: *** [all] Error 1
>> > [EMAIL PROTECTED]:/tmp/x> make
>> > for d in i386-user arm-user armeb-user sparc-user ppc-user mips-user
>> > mipsel-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu
>> > mips-softmmu mipsel-softmmu arm-softmmu; do \
>> > make -C $d all || exit 1 ; \
>> >done
>> > make[1]: Entering directory `/tmp/x/i386-user'
>> > make[1]: Nothing to be done for `all'.
>> > make[1]: Leaving directory `/tmp/x/i386-user'
>> > make[1]: Entering directory `/tmp/x/arm-user'
>> > make[1]: Nothing to be done for `all'.
>> > make[1]: Leaving directory `/tmp/x/arm-user'
>> > make[1]: Entering directory `/tmp/x/armeb-user'
>> > make[1]: Nothing to be done for `all'.
>> > make[1]: Leaving directory `/tmp/x/armeb-user'
>> > make[1]: Entering directory `/tmp/x/sparc-user'
>> > make[1]: Nothing to be done for `all'.
>> > make[1]: Leaving directory `/tmp/x/sparc-user'
>> > make[1]: Entering directory `/tmp/x/ppc-user'
>> > make[1]: Nothing to be done for `all'.
>> > make[1]: Leaving dire

Re: [Qemu-devel] qemu-0.8.1 compile errors on x86_64 suse linux 10.1

[Bill C. Riemers]

The following message was forwarded to me:-Hello all,there's a problem compiling usb-linux.c on SuSE 10.1 with the standardkernel headers (kernel 
2.6.16.13-4-default from uname -r).I'm using gcc 3.4.6 and the problem is an include file is missing in usb-linux.cThe missing h-file is . That inclusion needs to bewritten before the inclusion of 
Adding this include file the compiler is happy and all is ok.regards,Fausto---This solution works.  So it looks like the problem is simply a missing header include in 
qemu-0.8.1 version.   It has nothing to do with recompiling glibc, or downloading different kernel source, or any other such non-sense.BillOn 7/17/06, 
Damien Mascord <[EMAIL PROTECTED]> wrote:
Bill C. Riemers wrote:> Good guess, SuSE makes many modifications to the standard kernel.  However,> the kernel source is not the problem.  I downloaded fresh kernel source> from> 
www.kernel.org, and I still have the exact same error.  Here are the> relevant details:>> QEMU version: qemu-0.8.1> Linux Kernel: 2.6.16.13> Operating System: SuSE 
10.1> gcc version: 3.4.6> CPU: Amd Athlon(tm) Processor 3200+>> BillHi Bill,NOTE: Jim, if I am totally misrepresenting your comment, my apologies :)I think Jim is pointing to the linux kernel headers, and not necessarily the kernel source.
The linux kernel headers that are used to build your local glibc, and hence even if you use the virgin kernel source and load thatparticular kernel, you will have to rebuild your glibc against those kernel sources.
You will probably have to symlink the relevant directories so that when you build your glibc, it will pick up the virgin headersinstead of the SuSE modified ones.Once you have a clean system, running on a virgin kernel, running on a glibc compiled against the kernel headers of that virgin
kernel, and then attempt to compile qemu with gcc 3.x, you will likely not run into any problems.If you still have problems, perhaps you need to recompile said gcc with the virgin headers too.Hope to help,
Damien> On 7/8/06, Jim C. Brown <[EMAIL PROTECTED]> wrote: The issue is with your linux kernel headers. On Sat, Jul 08, 2006 at 11:07:57AM -0400, Doctor Bill wrote:
>> > At first I thought the problem was that I was using gcc-4, so I>> installed>> > gcc-3.4.6, but I still get the same errors:>> >>> > gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I..
>> > -I/tmp/qemu-0.8.1/target-i386>> > -I/tmp/qemu-0.8.1 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64>> -D_LARGEFILE_SOURCE>> > -I/tmp/qemu-0.8.1/fpu -DHAS_AUDIO -I/tmp/qemu-0.8.1/slirp -c -o
>> > usb-linux.o/tmp/qemu->> > 0.8.1/usb-linux.c>> > In file included from /tmp/qemu-0.8.1/usb-linux.c:29:>> > /usr/include/linux/usbdevice_fs.h:49: error: variable or field `__user'
>> > declared void>> > /usr/include/linux/usbdevice_fs.h:49: error: syntax error before '*'>> token>> > /usr/include/linux/usbdevice_fs.h:56: error: variable or field `__user'
>> > declared void>> > /usr/include/linux/usbdevice_fs.h:56: error: syntax error before '*'>> token>> > /usr/include/linux/usbdevice_fs.h:66: error: variable or field `__user'
>> > declared void>> > /usr/include/linux/usbdevice_fs.h:66: error: syntax error before '*'>> token>> > /usr/include/linux/usbdevice_fs.h:100: error: variable or field>> `__user'
>> > declared void>> > /usr/include/linux/usbdevice_fs.h:100: error: syntax error before '*'>> token>> > /usr/include/linux/usbdevice_fs.h:109: error: syntax error before '}'
>> token>> > /usr/include/linux/usbdevice_fs.h:116: error: variable or field>> `__user'>> > declared void>> > /usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*'
>> token>> > /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_control':>> > /tmp/qemu-0.8.1/usb-linux.c:91: error: invalid application of `sizeof'>> to>> > incomplete type `usbdevfs_ctrltransfer'
>> > /tmp/qemu-0.8.1/usb-linux.c: In function `usb_host_handle_data':>> > /tmp/qemu-0.8.1/usb-linux.c:110: error: storage size of 'bt' isn't>> known>> > /tmp/qemu-0.8.1/usb-
linux.c:121: error: invalid application of `sizeof'>> to>> > incomplete type `usbdevfs_bulktransfer'>> > /tmp/qemu-0.8.1/usb-linux.c:110: warning: unused variable `bt'>> > /tmp/qemu-
0.8.1/usb-linux.c: In function `usb_host_device_open':>> > /tmp/qemu-0.8.1/usb-linux.c:185: error: storage size of 'ctrl' isn't>> known>> > /tmp/qemu-0.8.1/usb-linux.c:188: error: invalid application of `sizeof'
>> to>> > incomplete type `usbdevfs_ioctl'>> > /tmp/qemu-0.8.1/usb-linux.c:185: warning: unused variable `ctrl'>> > make[1]: *** [usb-linux.o] Error 1>> > make[1]: Leaving directory `/tmp/x/i386-softmmu'
>> > make: *** [all] Error 1>> > [EMAIL PROTECTED]:/tmp/x> make>> > for d in i386-user arm-user armeb-user sparc-user ppc-user mips-user>> > mipsel-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu
>> > mips-softmmu mipsel-softmmu arm-softmmu; do \>> > make -C $d all || exit 1 ; \>> >done>> > make[1]: Enterin

Re: [Qemu-devel] qemu-0.8.1 compile errors on x86_64 suse linux 10.1

[Damien Mascord]

Bill C. Riemers wrote:
> The following message was forwarded to me:
>
> -
> Hello all,
>
> there's a problem compiling usb-linux.c on SuSE 10.1 with the standard
> kernel headers (kernel 2.6.16.13-4-default from uname -r).
>
> I'm using gcc 3.4.6 and the problem is an include file is missing in
> usb-linux.c
>
> The missing h-file is . That inclusion needs to be
> written before the inclusion of 
>
> Adding this include file the compiler is happy and all is ok.
>
> regards,
> Fausto
> ---
>
> This solution works.  So it looks like the problem is simply a missing
> header include in qemu-0.8.1 version.   It has nothing to do with
> recompiling glibc, or downloading different kernel source, or any
> other such non-sense.
>
> Bill
Hi Bill,

Luckily it was as simple as that, my apologies for blowing it out of
proportion here.

Cheers,

Damien


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel