On August 9, 2012 at 10:59 AM Gerd Hoffmann wrote:
> > Hi Gerd,
> >
> > sorry for the delays, I tested the latest pulled patch queue and it's
> > now fine on my Intel board, too. The dongle gets detected again without
> > assertions. Thanks for your work.
> >
> > Still remaining are the multiple
On August 9, 2012 at 10:59 AM Gerd Hoffmann wrote:
> > Hi Gerd,
> >
> > sorry for the delays, I tested the latest pulled patch queue and it's
> > now fine on my Intel board, too. The dongle gets detected again without
> > assertions. Thanks for your work.
> >
> > Still remaining are the multiple
Hi all,
I assume that I found a possible source of the bad usbtablet update rate.
I did some git bisectioning but I didn't get a usable result due to too
many merges (or maybe my little knowledge to git), so I proceeded with some
manual bisectioning by manually selecting commits and tested the
Jan Kiszka wrote:
On 2012-01-24 18:24, Erik Rull wrote:
Hi all,
I assume that I found a possible source of the bad usbtablet update rate.
I did some git bisectioning but I didn't get a usable result due to too
many merges (or maybe my little knowledge to git), so I proceeded with some
m
Hi all,
from the qemu-kvm master I did some bisectioning because I cannot compile it.
My error is:
In file included from /home/erik/qemu-kvm/hw/pci.c:36:
/qmp-commands.h:3: error: expected identifier or '(' before '{' token
/qmp-commands.h:10: error: expected identifier or '(' before ',' token
/
Hi Jan,
This little change fixes my problem with the usb-tablet update rate.
Can you please verify if this has some side effects?
If not, can you post a real patch?
I don't know how to handle the whole patching and committing stuff exactly.
Thanks.
Erik
--
diff --git a/ui/sdl.c b/ui/sdl.c
i
Gleb Natapov wrote:
On Wed, Jan 25, 2012 at 12:22:51PM +0100, erik.r...@rdsoftware.de wrote:
Hi all,
from the qemu-kvm master I did some bisectioning because I cannot compile it.
I got the same error because of some stale .h file. Removing it resolved
the problem, but I do not remember what w
Jan Kiszka wrote:
On 2012-01-25 12:48, erik.r...@rdsoftware.de wrote:
Hi Jan,
You should CC me then... :)
I will do that for upcoming emails.
This little change fixes my problem with the usb-tablet update rate.
Can you please verify if this has some side effects?
Surely as it disables
Hi Jan,
here the results of the sdl printfs.
First of all the modified code:
#include
#define NO_DEBUG_PATHS 3
int paths[NO_DEBUG_PATHS] = {0,0,0};
int last_sec = 0;
struct timeval tv;
static
Andreas Färber wrote:
Am 26.01.2012 11:32, schrieb Jan Kiszka:
On 2012-01-26 11:00, Andreas Färber wrote:
Am 26.01.2012 07:38, schrieb Gleb Natapov:
On Wed, Jan 25, 2012 at 10:07:14PM +0100, Erik Rull wrote:
Is it possible that you provide this patch? Or was it already
applied somewhere
Hi all,
when having a USB device connected to a windows XP guest that is booting
(or rebooting) the guest will never finish booting. It hangs before the
screen gets resized and the well known Windows is starting dialog appears.
If there is no usb device given to the guest, everything is fine, if
Jan Kiszka wrote:
On 2012-01-27 23:52, Jan Kiszka wrote:
On 2012-01-26 14:10, Erik Rull wrote:
I assume from these results that the gui_grab is never set to 1 when having
entered the window in windowed mode with the cursor.
Maybe that's why the sdl_grab_start() is called so often.
It
Jan Kiszka wrote:
On 2012-01-28 13:39, Erik Rull wrote:
Jan Kiszka wrote:
On 2012-01-27 23:52, Jan Kiszka wrote:
On 2012-01-26 14:10, Erik Rull wrote:
I assume from these results that the gui_grab is never set to 1 when
having
entered the window in windowed mode with the cursor.
Maybe
On January 28, 2012 at 3:52 PM Jan Kiszka wrote:
> On 2012-01-28 14:01, Erik Rull wrote:
> > Jan Kiszka wrote:
> >> On 2012-01-28 13:39, Erik Rull wrote:
> >>> Jan Kiszka wrote:
> >>&
On January 30, 2012 at 12:52 PM Jan Kiszka wrote:
> On 2012-01-30 12:34, Erik Rull wrote:
> > Hi Jan,
> >
> > I'm sorry, but this does not solve my issue. I applied the patch and
> > crosschecked that the resulting file looks fine.
> >
> > The fi
On January 30, 2012 at 2:48 PM Jan Kiszka wrote:
> On 2012-01-30 14:17, Erik Rull wrote:
> >
> >
> >
> > On January 30, 2012 at 12:52 PM Jan Kiszka
wrote:
> >
> >> On 2012-01-30 12:34, Erik Rull wrote:
> >>> Hi Jan,
> >>>
>
On January 30, 2012 at 3:48 PM Jan Kiszka wrote:
> On 2012-01-30 15:17, Erik Rull wrote:
> >
> >
> >
> > On January 30, 2012 at 2:48 PM Jan Kiszka
wrote:
> >
> >> On 2012-01-30 14:17, Erik Rull wrote:
> >>>
> >>>
sdl_grab_end was once introduced to work around a Windows-only
issue (0294ffb9c8), limit it to that platform.
CC: Erik Rull
Signed-off-by: Jan Kiszka
---
ui/sdl.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/ui/sdl.c b/ui/sdl.c
index 73e5839..6f8091c 100644
--- a/ui/sdl.c
Hi all,
first of all I'm a bit confused:
What is the difference between qemu with command line option --enable-kvm
and qemu-kvm?
It seems to be a difference in code so far, from the performance point of
view it seems to be the same...
Now my issue that lead me to a git bisect on qemu-kvm:
The f
On February 1, 2012 at 2:40 PM Avi Kivity wrote:
> On 02/01/2012 02:52 PM, Erik Rull wrote:
> > Hi all,
> >
> > first of all I'm a bit confused:
> >
> > What is the difference between qemu with command line option
--enable-kvm
> > and qemu-kvm?
&g
On February 1, 2012 at 3:42 PM Jan Kiszka wrote:
> On 2012-02-01 15:02, Erik Rull wrote:
> >
> > On February 1, 2012 at 2:40 PM Avi Kivity wrote:
> >
> >> On 02/01/2012 02:52 PM, Erik Rull wrote:
> >>> Hi all,
> >>>
> >>> f
Please use qemu-1.0 + ehci. The UHCI layer seems to cause this problem
when handling some USB 2.0 devices. I had similar problems but with EHCI
+ qemu-1.0 it was fixed. See docs/usb2.txt for USB 2.0 support.
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
Public bug reported:
affected qemus: qemu-1.0, qemu-kvm-1.0, qemu and qemu-kvm master branches
(older versions not tested)
affected guests: linux, windows
test hardware: standard usb key (or any other piece of USB hardware) that works
perfectly when plugged in after guest bootup
Several Sequenc
On February 1, 2012 at 5:01 PM Jan Kiszka wrote:
> On 2012-02-01 16:43, Erik Rull wrote:
> > On February 1, 2012 at 3:42 PM Jan Kiszka
wrote:
> >
> >> On 2012-02-01 15:02, Erik Rull wrote:
> >>>
> >>> On February 1, 2012 at 2:40 PM Avi Kivity
Jan Kiszka wrote:
On 2012-02-01 13:52, Erik Rull wrote:
Hi all,
first of all I'm a bit confused:
What is the difference between qemu with command line option --enable-kvm
and qemu-kvm?
It seems to be a difference in code so far, from the performance point of
view it seems to be the
On February 1, 2012 at 11:05 PM Erik Rull wrote:
> Jan Kiszka wrote:
> > On 2012-02-01 13:52, Erik Rull wrote:
> >> Hi all,
> >>
> >> first of all I'm a bit confused:
> >>
> >> What is the difference between qemu with command line o
On February 2, 2012 at 2:21 PM Jan Kiszka wrote:
> On 2012-02-02 14:18, Erik Rull wrote:
> >
> > On February 1, 2012 at 11:05 PM Erik Rull
wrote:
> >
> >> Jan Kiszka wrote:
> >>> On 2012-02-01 13:52, Erik Rull wrote:
> >>>>
update:
it works with the following parameter set:
-usb -device usb-host
but then only USB 1.1 is available (very slow)
it does not work with:
-readconfig ich9-ehci-uhci.cfg -device usb-host,bus=ehci.0
but there I have USB 2.0 and USB 1.1 devices routed perfectly with a good speed
to the guest at
update:
Seems to affect only USB 2.0 devices and if USB 2.0 (EHCI) is enabled.
If there is only -usb -device usb-host added, it works for both USB 2.0 and USB
1.1 but extremely slow due to the missing USB 2.0 layer
If the command line is given as reported above, it works for USB 1.1 devices,
to
Hi all,
is there a .inf file that makes a Windows XP guest no longer complaining
about the missing drivers for the qemu host option -vga std?
I tried several manual Windows .inf file copies / merges, but either the
exclamation mark in the Device Manager persisted or it falls back to
640x480
On February 6, 2012 at 9:29 AM Stefan Hajnoczi wrote:
> On Thu, Jan 19, 2012 at 08:06:30PM +0100, Erik Rull wrote:
> > test-coroutine.c:92: warning: implicit declaration of function
> > 'g_assert_cmpint'
> ...
> > erik@debian:~/qemu-test/qemu-kvm$
>
>
Anthony Liguori wrote:
Please respond to this note with an '+1', or an Ack, to vote for this icon.
+1
Anthony Liguori wrote:
Please respond to this note with an '+1', or an Ack, to vote for this icon.
+1
Jan Kiszka wrote:
Hi Gerd,
I'm getting
qemu/hw/usb/core.c:410: usb_packet_complete: Assertion
`((&ep->queue)->tqh_first) == p' failed.
with a passed-through USB headset (UHCI controller). This was with
current QEMU git head. Known issues? Anything I can do to debug it?
Jan
Hi all,
I get
Hi all,
is there a way to deny passing certain devices to the guest? I want to deny
two devices to get assigned to the guest, all others on all ports are
allowed, ony two each with a defined pid/vid should not get routed.
Providing a positive list would exceed the max. command line parameter
l
Hans de Goede wrote:
Hi,
On 06/25/2012 06:17 PM, Erik Rull wrote:
Hi all,
is there a way to deny passing certain devices to the guest? I want to
deny two devices to get assigned to the guest, all others on all ports
are allowed, ony two each with a defined pid/vid should not get routed
Jan Kiszka wrote:
On 2012-06-23 11:29, Erik Rull wrote:
Jan Kiszka wrote:
Hi Gerd,
I'm getting
qemu/hw/usb/core.c:410: usb_packet_complete: Assertion
`((&ep->queue)->tqh_first) == p' failed.
with a passed-through USB headset (UHCI controller). This was with
current
Gerd Hoffmann wrote:
Add support for (re-)initializing endpoints which belong to a specific
interface only. Use this in usb-host when changing altsetting for an
interface, so other interfaces are not disturbed.
Hi Gerd,
I tested it on my AMD test system where the issue didn't appear with the
Erik Rull wrote:
Gerd Hoffmann wrote:
Add support for (re-)initializing endpoints which belong to a specific
interface only. Use this in usb-host when changing altsetting for an
interface, so other interfaces are not disturbed.
Hi Gerd,
I tested it on my AMD test system where the issue
Hi all,
which is the graphics emulation with the lowest CPU usage for 2D-only GUIs?
(e.g. Win XP without Direct3D usage)? I just need to drive a virtual
graphics display with 1024x768 (@16bit colors). At the moment I use the
cirrus graphics card emulation. Is there something more efficient?
T
Hi Gerd, hi Hans,
is my assumption correct that if I check out and compile this version from
GIT master that the usb-tablet device is automatically routed to ehci
without changing anything else in the qemu call arguments? (And the
performance enhancement takes place automatically)
If not - wh
Hi,
thanks for your quick reply.
Dunrong Huang wrote:
On Wed, Dec 26, 2012 at 8:04 PM, Erik Rull wrote:
Hi all,
which is the graphics emulation with the lowest CPU usage for 2D-only GUIs?
(e.g. Win XP without Direct3D usage)? I just need to drive a virtual
graphics display with 1024x768
Hi all,
with the current git master and the git submodule pixman, I get the
following errors when trying to "make":
erik@debian:~/qemu-test/qemu-now/qemu$ make
GEN x86_64-softmmu/config-devices.mak
GEN config-all-devices.mak
GEN config-host.h
(cd /home/erik/qemu-test/qemu-now/qemu/
Libtool was missing, works now :-)
Erik Rull wrote:
Hi all,
with the current git master and the git submodule pixman, I get the
following errors when trying to "make":
erik@debian:~/qemu-test/qemu-now/qemu$ make
GEN x86_64-softmmu/config-devices.mak
GEN config-all-devices.
Hi Hans,
Hans de Goede wrote:
Hi,
On 12/26/2012 01:07 PM, Erik Rull wrote:
Hi Gerd, hi Hans,
is my assumption correct that if I check out and compile this version
from GIT master that the usb-tablet device is automatically routed to
ehci without changing anything else in the qemu call
Hi all,
is it meanwhile possible to get the same screen output on a screen and on
VNC? I would like to offer a "direct" terminal (with a real screen and
keyboard) for user interaction and a VNC remote terminal e.g. for service
access.
Is it possible to configure it so that the guest sees onl
Hi all,
when using the released qemu-1.6.0.tar.bz2, I get the following error message:
[...]
ar: creating libfdt/libfdt.a
a - libfdt/fdt.o
a - libfdt/fdt_ro.o
a - libfdt/fdt_wip.o
a - libfdt/fdt_sw.o
a - libfdt/fdt_rw.o
a - libfdt/fdt_strerror.o
GEN qemu-options.def
GEN qmp-commands.h
Tra
Luiz Capitulino wrote:
On Fri, 16 Aug 2013 14:21:50 +0100
Peter Maydell wrote:
On 16 August 2013 08:59, Erik Rull wrote:
Hi all,
when using the released qemu-1.6.0.tar.bz2, I get the following error message:
File "/home/erik/qemu-1.6.0/scripts/qapi.py", line 164
Hi Markus,
I would like to try it - see the python-traceback thread - when qemu
compiles, I will definitively try it with the 1.6.0.
Best regards,
Erik
Markus Armbruster wrote:
Erik Rull writes:
Hi all,
I'm struggling with the QEMU VNC on qemu-kvm-1.2.0 a bit, the following two
t
> On August 19, 2013 at 6:15 PM Erik Rull wrote:
>
>
> Luiz Capitulino wrote:
> > On Fri, 16 Aug 2013 14:21:50 +0100
> > Peter Maydell wrote:
> >
> >> On 16 August 2013 08:59, Erik Rull wrote:
> >>> Hi all,
> >>>
> >>
Markus Armbruster wrote:
Erik Rull writes:
Hi all,
I'm struggling with the QEMU VNC on qemu-kvm-1.2.0 a bit, the following two
things are not working properly:
Have you tried to reproduce on a current version?
Hello Markus,
yes, I was able to reproduce this with the released qemu-
Markus Armbruster wrote:
Erik Rull writes:
Markus Armbruster wrote:
Erik Rull writes:
Hi all,
I'm struggling with the QEMU VNC on qemu-kvm-1.2.0 a bit, the following two
things are not working properly:
Have you tried to reproduce on a current version?
Hello Markus,
yes, I was
> On August 23, 2013 at 7:42 AM Markus Armbruster wrote:
>
>
> Anthony Liguori writes:
>
> > On Aug 22, 2013 4:55 PM, "Erik Rull" wrote:
> >>
> >> Markus Armbruster wrote:
> >>>
> >>> Erik Rull writes:
> >>>
&
Hi all,
is it possible to get back to the "legacy" BIOS instead of the (u)efi based
BIOS? I have problems booting the guest on a SSD HDD, there it reboots
infinitely, when running the guest on a rotating HDD, it works. On qemu 1.2.0
both disks work properly. I didn't find a way to select the BIOS
Stefan Hajnoczi wrote:
On Mon, Aug 26, 2013 at 11:52:26AM +0200, Erik Rull wrote:
is it possible to get back to the "legacy" BIOS instead of the (u)efi based
BIOS? I have problems booting the guest on a SSD HDD, there it reboots
infinitely, when running the guest on a rotating HDD, it
> On August 27, 2013 at 11:37 PM Anthony Liguori wrote:
>
>
> On Aug 27, 2013 4:32 PM, "Paolo Bonzini" wrote:
> >
> > Il 27/08/2013 22:26, Erik Rull ha scritto:
> > > Hi Stefan,
> > >
> > > which BIOS is selected by default?
>
> On August 28, 2013 at 9:50 AM Stefan Hajnoczi wrote:
>
>
> On Tue, Aug 27, 2013 at 11:31:28PM +0200, Paolo Bonzini wrote:
> > Il 27/08/2013 22:26, Erik Rull ha scritto:
> > > It's more a guess, there must be a
> > > change between 1.2.0 and 1.6
Benoît Canet wrote:
Can you whip up a patch to avoid that? Or to honor bps_max if it is
specified (making avg/10 simply the default)?
Pushed in the same branch (it honor bps_max if specified).
Best regards
Benoît
Hi all,
thanks for your help. I cloned the git and compiled it - but I'm no
Benoît Canet wrote:
thanks for your help. I cloned the git and compiled it - but I'm not
completely sure how to enable the throttling finally - there were
several mails regarding averages and max values... And the "unit" of
the values would be interesting.
Hi Erik,
The main settings are bps, b
> On August 28, 2013 at 9:22 PM Erik Rull wrote:
>
>
> Benoît Canet wrote:
> >> thanks for your help. I cloned the git and compiled it - but I'm not
> >> completely sure how to enable the throttling finally - there were
> >> several mails regarding
> On August 29, 2013 at 11:25 AM Benoît Canet wrote:
>
>
> > My commandline section is (I played with bps between 0.5 and 2.0 MB/sec and
> > iops
> > with 1000 and 500):
> > -drive file=/dev/sda2,cache=none,bps=548576,bps_max=1,iops_max=1000
> > Within qemu it looks like that:
> > QEMU 1.6.50 mo
> On August 29, 2013 at 4:55 PM Paolo Bonzini wrote:
>
>
> Il 29/08/2013 16:51, Erik Rull ha scritto:
> >
> >
> >> On August 29, 2013 at 11:25 AM Benoît Canet
> >> wrote:
> >>
> >>
> >>> My commandline section is (I played
Hi all,
I'm struggling with the QEMU VNC on qemu-kvm-1.2.0 a bit, the following two
things are not working properly:
1) Shift key pressed and hold for several seconds causes multiple shift key
press + release events => I would expect getting one press, one or more hold and
one release event (mino
Public bug reported:
When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla kernel
3.4.67 or 3.10.12 to run a Windows 8.0 guest, the guest freezes at Windows 8
boot without any error.
When I dump the CPU registers via "info registers", nothing changes, that means
the system rea
** Description changed:
- When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla
kernel
- 3.4.67 or 3.10.12 to run a Windows 8.0 guest, the guest freezes at Windows 8
boot without any error.
- When I dump the CPU registers via "info registers", nothing changes, that
means
- t
** Description changed:
When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla
kernel 3.4.67 or 3.10.12 to run a Windows 8.0 guest, the guest freezes at
Windows 8 boot without any error.
When I dump the CPU registers via "info registers", nothing changes, that
means the s
Here the register dump of the stalled Win8
QEMU 2.1.0 monitor - type 'help' for more information
(qemu) info registers
EAX=3e2009e3 EBX=3e2009e3 ECX=8000 EDX=8000
ESI=3e2009e3 EDI=8220c108 EBP=81f9b33c ESP=81f9b2f0
EIP=80c98d83 EFL=00010282 [--S] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0023 00
I found a new trace - using the ipipe patch that I have, there seems to be an
issue in the 3.4 kernels, but as it looks also in the 3.10 kernels.
http://www.xenomai.org/pipermail/xenomai/2013-March/027865.html
Is there an update on that already existing? It was not completely clear
if this issue
attached the trace.dat (tar-gzipped) as recommended. Hope this helps finding
the issue. The file should capture the following:
- windows 8 with screen that shows that the last boot attempts failed
- issued system_reset on qemu commandline
- startup of windows 8 that stalls
** Attachment added: "
sorry for the corrupt file, this one should be fine now.
** Attachment added: "trace.tgz"
https://bugs.launchpad.net/qemu/+bug/1366836/+attachment/4201455/+files/trace.tgz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
Confirmed - the current kvm.git without any ipipe patch also causes the
issue. Trace File attached.
** Attachment added: "trace.tgz"
https://bugs.launchpad.net/qemu/+bug/1366836/+attachment/4202192/+files/trace.tgz
--
You received this bug notification because you are a member of qemu-
devel
Hi all,
I post this to both QEMU and libusb because I'm not sure where the error could
be located.
I have an application using libusb which is running for months without any
issues on the host system.
When I start QEMU - which uses libusb, too - the errors begin. I route some USB
ports to my QEM
Hi all,
I did already several tests and I'm not completely sure what's going wrong, but
here my scenario:
When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla kernel
3.4.67 to run a Windows 8.0 guest, the guest freezes at boot without any error.
When I dump the CPU registers
Hi all,
how can I use a USB 1.1 device on the USB 2.0 bus? Currently the EHCI
implementation complains that the device is mismatches the USB version.
I want to offer one root port for both USB 2.0 and USB 1.1 devices using
usb-host,... Routings to the guest.
Maybe only some parameters need
> On 12/31/11 13:11, Erik Rull wrote:
> > Hi all,
> >
> > how can I use a USB 1.1 device on the USB 2.0 bus? Currently the EHCI
> > implementation complains that the device is mismatches the USB version.
>
> -readconfig docs/ich9-ehci-uhci.cfg
>
> cheers,
&
erik.r...@rdsoftware.de wrote:
On 12/31/11 13:11, Erik Rull wrote:
Hi all,
how can I use a USB 1.1 device on the USB 2.0 bus? Currently the EHCI
implementation complains that the device is mismatches the USB version.
-readconfig docs/ich9-ehci-uhci.cfg
cheers,
Gerd
Thanks for the hint
Erik Rull wrote:
Anthony Liguori wrote:
On 12/19/2011 03:33 PM, Erik Rull wrote:
Hi all,
coming from qemu 0.14 the usbdevice tablet update rate gets really bad in
qemu-1.0 with the same guest.
What's the specific guest?
Regards,
Anthony Liguori
It's a Windows XP guest. It w
Erik Rull wrote:
Erik Rull wrote:
Anthony Liguori wrote:
On 12/19/2011 03:33 PM, Erik Rull wrote:
Hi all,
coming from qemu 0.14 the usbdevice tablet update rate gets really bad in
qemu-1.0 with the same guest.
What's the specific guest?
Regards,
Anthony Liguori
It's a Window
Erik Rull wrote:
Erik Rull wrote:
Anthony Liguori wrote:
On 12/19/2011 03:33 PM, Erik Rull wrote:
Hi all,
coming from qemu 0.14 the usbdevice tablet update rate gets really bad in
qemu-1.0 with the same guest.
What's the specific guest?
Regards,
Anthony Liguori
It's a Window
Erik Rull wrote:
Erik Rull wrote:
Erik Rull wrote:
Anthony Liguori wrote:
On 12/19/2011 03:33 PM, Erik Rull wrote:
Hi all,
coming from qemu 0.14 the usbdevice tablet update rate gets really bad in
qemu-1.0 with the same guest.
What's the specific guest?
Regards,
Anthony Liguori
Hi all,
I just got a copy of the current qemu-kvm but there is a build failure in
test-coroutine.c:
erik@debian:~/qemu-test/qemu-kvm$ make
[...]
CCtest-coroutine.o
test-coroutine.c: In function 'test_nesting':
test-coroutine.c:92: warning: implicit declaration of function
'g_assert_cmpi
Andreas Färber wrote:
Am 19.01.2012 17:40, schrieb Erik Rull:
Erik Rull wrote:
Erik Rull wrote:
Erik Rull wrote:
Anthony Liguori wrote:
On 12/19/2011 03:33 PM, Erik Rull wrote:
Hi all,
coming from qemu 0.14 the usbdevice tablet update rate gets really
bad in
qemu-1.0 with the same guest
Hi all,
when buildung target x86_64-softmmu the final link fails:
LINK x86_64-softmmu/qemu-system-x86_64
../libhw64/9pfs/virtio-9p-proxy.o: In function `proxy_opendir':
/home/erik/qemu-test/qemu/hw/9pfs/virtio-9p-proxy.c:659: undefined
reference to `fdopendir'
collect2: ld returned 1 exit s
Hi Andreas,
Andreas Färber wrote:
Hi Erik,
Am 19.01.2012 20:15, schrieb Erik Rull:
Andreas Färber wrote:
Am 19.01.2012 17:40, schrieb Erik Rull:
[...] there seems to be a
difference between the captured cursor for the native X-Windows window
and the VNC window that occured somewhere between
Hi all,
I'm really sorry, but the bisectioning does not work for the versions that
I want to test.
I get a bunch of errors when bisectioning.
e.g. continuosly:
erik@debian:~/qemu-test/qemu-kvm$ make
CCx86_64-softmmu/monitor.o
In file included from /home/erik/qemu-test/qemu-kvm/qmp-commands
On March 21, 2012 at 6:36 PM Gerd Hoffmann wrote:
> Not only QHs can form rings, but TDs too. With the new
> queuing/pipelining support we are following TD chains and
> can actually walk in circles. An assert() prevents us from
> entering an endless loop then.
>
> Fix is easy: Just stop queui
Gerd Hoffmann wrote:
Hi,
When enabling the -device usb-host option support for adding
automatically USB devices from the host to the guest, only one device
gets detected.
Yes. -device usb-host creates a *single* virtual usb device instance.
When a matching device on the host is found the vi
David Ahern wrote:
Come on Gerd. That was not an attempt to get it included. Someone asked
for a patch and I took the existing tree, merged with latest and through
out the patch. The v1/v2 is not in Jan's tree. That's a hack I have
locally to have mixed devices. What is shows is that is not a big
Hi Gerd,
could you provide a single patch file for the new USB files against the
released qemu 0.14.0 or 0.14.1? I tried to create that file by assembling
the patch emails but no real success.
Feedback on the patch is guaranteed :-)
Thanks a lot!
Best regards,
Erik
Hi all,
in usb-linux.c my qemu crashes in
static int usb_host_open(USBHostDevice *dev, int bus_num, int addr, char
*port, const char *prod_name, int speed)
because port is NULL.
The line that causes the problem is:
strcpy(dev->port, port);
All Ports are displayed in the qemu monitor info as
Hi all,
is there a documentation available for the new USB EHCI and Port selection
feature?
I have read some patches that contained these updates, but I don't know how
to tell my USB device to be exposed as EHCI device to the guest.
My info usbhost shows 5x UHCI and 1x EHCI host after adding
Hi Gerd,
thanks a lot.
I just had a look on usb-linux.c where the "port" could be identified.
for those that must use /proc/bus/usb it would be possible to allow the
following:
read in the "Port=" and check if it is on bus level 1, then you can
identify at least your real root hardware port - hu
Hi Gerd,
thanks a lot.
I just had a look on usb-linux.c where the "port" could be identified.
for those that must use /proc/bus/usb it would be possible to allow the
following:
read in the "Port=" and check if it is on bus level 1, then you can
identify at least your real root hardware port - h
Hi Fabian,
Fabian Holler wrote:
Hello Erik,
I just want to route all keypresses to the guest without interfering with
the native QEMU key layout. Is that possible?
Yes, if you start kvm without the "-k" option and use a linux VNC client that
supports RFB extended key events (eg gtk-vnc, tige
Hi Fabian,
Fabian Holler wrote:
Howdy Erik,
On Tue, May 29, 2012 at 09:22:02PM +0200, Erik Rull wrote:
Fabian Holler wrote:
I just want to route all keypresses to the guest without interfering with
the native QEMU key layout. Is that possible?
Yes, if you start kvm without the "-k&qu
Hi all,
when assigning USB host devices to a guest using the hostport option, there
seem to be different formats, when calling info usbhost:
- On my vanilla kernel linux there is a hostport format e.g. "1.5" or "1.2"
- On my Debian 6.0 full blown linux there is a hostport format "2" or "4",
t
Hans de Goede wrote:
Hi,
On 06/08/2012 06:33 PM, Erik Rull wrote:
Hi all,
when assigning USB host devices to a guest using the hostport option,
there seem to be different formats, when calling info usbhost:
- On my vanilla kernel linux there is a hostport format e.g. "1.5" or &qu
Hans de Goede wrote:
Hi,
On 06/08/2012 10:56 PM, Erik Rull wrote:
Hans de Goede wrote:
Hi,
On 06/08/2012 06:33 PM, Erik Rull wrote:
Hi all,
when assigning USB host devices to a guest using the hostport option,
there seem to be different formats, when calling info usbhost:
- On my vanilla
Hi,
please try to use the .cfg file from the docs/ directory, using this file,
the USB printer speed is really good on my systems. Well it is still an
emulation so you'll never get native speed, but it is far better than the
USB 1.x emulation we had in 0.1x versions.
Best thing to test the app
Hi,
Reeted wrote:
On 04/03/12 15:33, Erik Rull wrote:
Hi,
please try to use the .cfg file from the docs/ directory,
The ich9-ehci-uhci.cfg ? Yes it's the same thing I am using.
If you look at the section I have replicated that file
exactly.
I had access rights problem using the .cfg
1 - 100 of 216 matches
Mail list logo
