Please close it, it's solved with this patch commit to kvm / kernel:
Was found and fixed with great support of Paolo Bonzini
From: Paolo Bonzini
Date: Thu, 12 Feb 2015 17:04:47 +0100
Subject: KVM: emulate: fix CMPXCHG8B on 32-bit hosts
--
You received this bug notification because you are a
Meanwhile it works.
Thomas Huth wrote:
> Triaging old bug tickets ... Can you still reproduce this problem with
> the latest version of QEMU and the latest version of libusb? If so,
> could you please also provide the command line options that you used to
> start QEMU?
>
> ** Changed in: qemu
>
Hi all,I started with QEMU emulator version 2.1.2 backport on ubuntu 14.04 (I also tried the QEMU 2.0.0 that is provided natively with this version) and I can't get the USB device redirection working properly.No idea what actually goes wrong. I have the 32 bit version running properly without any
Hi all,
I got a Windows 8.1 guest running on ubuntu 14.04 / qemu-kvm 2.0.0 including
spice support.
I can connect the spice client to the guest and the copy / paste of text from /
to the client works (virtio serial port is running and the agent is running on
Windows.
But what I cannot get
Hi Gerd,
any ideas if there was an update or patch on this point? I tried to check
the commits since April but didn't find something that may fit...
Best regards,
Erik
Gerd Hoffmann wrote:
> On Mo, 2015-04-27 at 12:53 +0200, Erik Rull wrote:
>> Hi Gerd,
>>
>> well - it
Hi all,
which SDL(2) / XWindows Performance is the best at which graphics card type
(e.g. Cirrus or Std VGA) on the guest?
Is there a table with some reference benchmarks?
Thanks a lot.
Best regards,
Erik
Hi Gerd,
thanks a lot!
After some browsing through search result lists, it looks similar to the
issue that was reported here:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1323758
I will try the input_* tracepoints if this does not fix it.
I need some feedback from my colleague to check if
Hello,
is there a way to query the current cursor position of the QEMU tablet or
QEMU Mouse? Or is there a way to see that the mouse was moved e.g. since
the last query?
I currently have some trouble with the mouse - it just freezes in the guest
after an undefined period (might work before the
Hi all,
is there a comparison chart of the different disk formats supported by
QEMU? Especially throughput, latencies and robustness against unexpected
power loss on the host would be interesting.
Thanks a lot.
Best regards,
Erik
at 2:12 PM Erik Rull erik.r...@rdsoftware.de wrote:
Hi Gerd,
it seems to be a bug sitting in front of the computer :-)
I just recompiled the new SDL and didn't recompile QEMU against the new SDL
- I recognized later that there are version dependent pieces of code in QEMU.
I will proceed
an
update when the results are available.
Best regards,
Erik
Gerd Hoffmann wrote:
On Mi, 2015-04-22 at 18:20 +0200, Erik Rull wrote:
Hi all,
I'm struggling a bit with the numlock state when using SDL.
On SDL 1.2.13 I have the problem that the numlock state is inverted for QEMU
Hi all,
I'm struggling a bit with the numlock state when using SDL.
On SDL 1.2.13 I have the problem that the numlock state is inverted for QEMU -
but it is switchable.
On SDL 1.2.14 and 1.2.15 I can't enable the number input in any state of the
numlock key.
With VNC everything is fine.
I read
Which version is used? Try the latest QEMU or at least QEMU 2.0.
The behavior sounds like a pretty old QEMU version.
Additionally, enable the EHCI controller (see example in the docs subdirectory).
It it working on a native Windows XP?
--
You received this bug notification because you are a
Please check that the devices get added to the EHCI bus and not to the UHCI.
As far as I know the -usb* commands are deprecated. The functions behind the
-device usb* and -usb* should behave the same.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
sorry, my fault --disable-libpng fixed it in the configure option
** Changed in: qemu
Status: New = Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1446179
Title:
QEMU 2.2.1 fails to
Public bug reported:
QEMU 2.2.1 does not compile properly when having set --disable-vnc-png
due to the missing libpng support on the compile system. The worked
great in QEMU 2.1.0 but 2.2.1 seems to have a missing dependency
propagation to pixman which now requires libpng anyway. There seems to
Hi Eric,
On April 8, 2015 at 6:16 PM Eric Blake ebl...@redhat.com wrote:
On 04/08/2015 10:10 AM, Erik Rull wrote:
My suggestion is to create a script that sends the QMP command
query-status an then parse the result. The syntax and output is:
- { execute: query-status
Hello Paulo,
On April 7, 2015 at 3:42 PM Paulo Ricardo Paz Vital
paulo.vi...@profitbricks.com wrote:
On Tue, 2015-04-07 at 15:31 +0200, Erik Rull wrote:
Hi all,
I need a pretty simple way to get the current state of the VM running in
QEMU -
I only need the VM state (e.g. running
Hi all,
I need a pretty simple way to get the current state of the VM running in QEMU -
I only need the VM state (e.g. running, paused,...). Since my environment does
not have any perl, python or other high level scripting capabilities, a simple
way e.g. via a shell script would be nice. QEMU is
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-
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.
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
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
** 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
-
** 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
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,
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
Hi all,
I would like to provide 3GB of RAM to my guest - I use kvm and don't see a real
reason why this should not work. Currently, qemu-1.7.0 with kvm is in use.
Any hints or solutions are welcome.
Thanks.
Best regards,
Erik
, Erik Rull wrote:
Hi all,
I would like to provide 3GB of RAM to my guest - I use kvm and don't see a
real
reason why this should not work. Currently, qemu-1.7.0 with kvm is in use.
No way. Userspace has 3G address space on 32bit machines, and you can't
assign all of that to the guest
Hi all,
I try to replace the display content of a paused VM (to show the operator that
it is actually paused and not usable), but it causes only a short flicker on the
display instead of staying permanent.
By routing an HMP based command to console.c I want to replace the display
contents. I
Hi all,
I would like to have the guest drifting to a new set clock on the host.
My problem is the following:
- Host System (Linux) starts up, hwclock and kernel time are synced, guest
starts up with -rtc clock=host,driftfix=slew (which I assume should fix any
drift issue on ACPI compatible
Laszlo Ersek wrote:
On 03/27/14 09:41, Erik Rull wrote:
Hi all,
I would like to have the guest drifting to a new set clock on the host.
My problem is the following:
- Host System (Linux) starts up, hwclock and kernel time are synced,
guest starts up with -rtc clock=host,driftfix=slew (which
Hi all,
I would like to provide a possiblity to show the operator that his vm is
currently not alive, but paused / stopped. Currently, I see this only when
accessing the qemu monitor console. Is there a possibility to expose this
information to the guest display so that the operator does not
Hi all,
I'm using QEMU with ACPI enabled and the no-shutdown-option which does
not close the QEMU process after the shutdown is completed.
I would like to show to the user on the guest display that the guest system
is actually shut off - currently I just see the stalled shutting down
screen
Anthony Liguori wrote:
Hi,
On behalf of the QEMU Team, I'd like to announce the availability of the
third release candidate for the QEMU 1.7 release. This release is meant
for testing purposes and should not be used in a production environment.
Erik Rull wrote:
Hi all,
I have the following qemu commandline on an i3 or i5 CPU (both behave the same),
Windows XP (Standard PC installation) runs fine, Windows 7 and Windows 8 reboot
in an infinite loop either shortly before the logo is displayed (Windows 7) or
after the boot logo
Hi all,
I don't have libusbx installed on my system but the source package is available
and compiled for development.
This may also help other users to enable the libusbx support without having it
actually installed on the compile machine.
It's a first attempt, feel free to optimize it. I would
On November 27, 2013 at 11:14 AM Paolo Bonzini pbonz...@redhat.com wrote:
Il 27/11/2013 11:09, Erik Rull ha scritto:
I don't have libusbx installed on my system but the source package is
available
and compiled for development.
This may also help other users to enable the libusbx
On November 27, 2013 at 11:38 AM Paolo Bonzini pbonz...@redhat.com wrote:
Il 27/11/2013 11:24, Erik Rull ha scritto:
no I have no libusbx installed. I just downloaded the tar.bz2, unpacked it,
configure'd it and called make.
I think your patch wouldn't be enough to actually run QEMU
Hi all,
is there a Windows driver for the QEMU USB Hub that gets created automagically
when exposing more than 5 USB host ports to QEMU?
I didn't find something that fits my needs. The device is listed with an
exclamation mark in Windows 8.
Thanks.
Best regards,
Erik
On November 27, 2013 at 11:38 AM Paolo Bonzini pbonz...@redhat.com wrote:
Il 27/11/2013 11:24, Erik Rull ha scritto:
no I have no libusbx installed. I just downloaded the tar.bz2, unpacked it,
configure'd it and called make.
I think your patch wouldn't be enough to actually run QEMU
Hi all,
I have the following qemu commandline on an i3 or i5 CPU (both behave the same),
Windows XP (Standard PC installation) runs fine, Windows 7 and Windows 8 reboot
in an infinite loop either shortly before the logo is displayed (Windows 7) or
after the boot logo is displayed (Windows 8).
On
Hi all,
when using the latest GIT master qemu fails with the following error:
qemu-system-x86_64: -device usb-host,bus=ehci.0: Parameter 'driver' expects
device type
I haven't changed anything in the call parameters since 1.2.0 and the
documentation that is provided in the GIT repository doesn't
run there.
I'm really interested getting qemu running again, but I'm running from
trouble to trouble now for more than 4 weeks - python, ACPI, USB,...
Thanks.
Best regards,
Erik
Gerd Hoffmann wrote:
On Di, 2013-11-26 at 15:52 +0100, Erik Rull wrote:
Hi all,
when using the latest GIT
Erik Rull wrote:
Hi Gerd,
I only have libusb (0.1 and 1.0) installed. Is there a chance to get an
error message a bit earlier - or a warning that the usb-host support was
disabled? configure doesn't print out a libusb - disabled message when not
passing the libusb-parameter.
I tried now
Michael S. Tsirkin wrote:
On Fri, Nov 22, 2013 at 09:19:49PM +0100, Erik Rull wrote:
Paolo Bonzini wrote:
Il 22/11/2013 12:16, Erik Rull ha scritto:
It's getting more and more complex to build qemu, is there a reason why everyone
needs to build the acpi stuff by himself?
It is only
Michael S. Tsirkin wrote:
g_array_get_element_size was only added in glib 2.14,
there's no way to find element size in with an older glib.
Fortunately we only use a single table (linker) where element size 1.
Switch element size to 1 everywhere, then we can just look at len field
to get table
Richard Henderson wrote:
On 11/26/2013 07:01 AM, Michael S. Tsirkin wrote:
Can you confirm this works?
I can confirm that with this follow-on I can once again build on RHEL 5.3.
r~
Sorry, a bit late, but yes, it compiles on my Debian 4.0. My test target is
down at the moment, I try to
On November 22, 2013 at 11:56 AM Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Nov 21, 2013 at 09:44:29PM +0100, Erik Rull wrote:
Hu Tao wrote:
On Thu, Nov 21, 2013 at 09:06:43AM +0100, Erik Rull wrote:
Hi all,
when doing a git clone on the latest master, it fails compiling
Paolo Bonzini wrote:
Il 22/11/2013 12:16, Erik Rull ha scritto:
It's getting more and more complex to build qemu, is there a reason why everyone
needs to build the acpi stuff by himself?
It is only attempted if iasl is installed but as you said below, your
version is too old. Please run make
Hi all,
when doing a git clone on the latest master, it fails compiling:
CC x86_64-softmmu/memory_mapping.o
CC x86_64-softmmu/dump.o
CC x86_64-softmmu/xen-stub.o
CC x86_64-softmmu/hw/i386/multiboot.o
CC x86_64-softmmu/hw/i386/smbios.o
CC x86_64-softmmu/hw/i386/pc.o
Marcel Apfelbaum wrote:
Added 2 tests:
1. Basic check of FACS table (missed on prev submission)
2. Compare DSDT and SSDT tables against expected values
Test 2:
- runs only if iasl is installed on the host machine.
- the test plan:
1. Dumps the ACPI tables as AML on the disk.
2.
Marcel Apfelbaum wrote:
On Thu, 2013-11-21 at 22:20 +0100, Erik Rull wrote:
Marcel Apfelbaum wrote:
Added 2 tests:
1. Basic check of FACS table (missed on prev submission)
2. Compare DSDT and SSDT tables against expected values
Test 2:
- runs only if iasl is installed on the host
Hu Tao wrote:
On Thu, Nov 21, 2013 at 09:06:43AM +0100, Erik Rull wrote:
Hi all,
when doing a git clone on the latest master, it fails compiling:
CCx86_64-softmmu/memory_mapping.o
CCx86_64-softmmu/dump.o
CCx86_64-softmmu/xen-stub.o
CCx86_64-softmmu/hw/i386
Hi all,
the current git master of qemu fails on configure: (I did a fresh clone to
prevent any side effects)
erik@debian:~/tmp/qemu-test/qemu$ ./configure --prefix=
--target-list=x86_64-softmmu --disable-vnc-png --disable-vnc-jpeg
--disable-vnc-tls --disable-vnc-sasl --audio-drv-list=
On November 15, 2013 at 1:14 PM Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Nov 15, 2013 at 11:16:17AM +0100, Erik Rull wrote:
Hi all,
the current git master of qemu fails on configure: (I did a fresh clone to
prevent any side effects)
erik@debian:~/tmp/qemu-test/qemu
Erik Rull wrote:
Hi all,
when starting qemu (with or without kvm active) I get the following error
code after having a few minutes a blue windows logo on a black background:
Your PC needs to restart.
Please hold down the power button.
Error Code: 0x005C
Parameters:
0x0110
0xFFD09BC8
Hi all,
when starting qemu (with or without kvm active) I get the following error
code after having a few minutes a blue windows logo on a black background:
Your PC needs to restart.
Please hold down the power button.
Error Code: 0x005C
Parameters:
0x0110
0xFFD09BC8
0x0019
Hi all,
when testing my first Windows 7 guest, I noticed, that the IRQ load /
kernel time within the guest is quite high when having network access. I
use the virtio drivers - the same version as in the Windows XP guests.
There the kernel load is nearly only 50% of the Win7 load. Why? The
Paolo Bonzini wrote:
Il 14/09/2013 11:24, Erik Rull ha scritto:
Hi all,
I tried a guest OS that is ACPI capable with enabled ACPI in qemu (+kvm)
and qemu quits when the guest OS was shut down (and the guest PC
should be powered off). Well, from the guest point of view, this
behavior seems
Hi all,
I tried a guest OS that is ACPI capable with enabled ACPI in qemu (+kvm)
and qemu quits when the guest OS was shut down (and the guest PC should
be powered off). Well, from the guest point of view, this behavior seems to
be okay, but I would like to keep qemu running to have e.g. a
On August 28, 2013 at 9:22 PM Erik Rull erik.r...@rdsoftware.de 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 averages and max values
On August 29, 2013 at 11:25 AM Benoît Canet benoit.ca...@irqsave.net 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
On August 29, 2013 at 4:55 PM Paolo Bonzini pbonz...@redhat.com wrote:
Il 29/08/2013 16:51, Erik Rull ha scritto:
On August 29, 2013 at 11:25 AM Benoît Canet benoit.ca...@irqsave.net
wrote:
My commandline section is (I played with bps between 0.5 and 2.0 MB/sec
and
iops
On August 27, 2013 at 11:37 PM Anthony Liguori anth...@codemonkey.ws wrote:
On Aug 27, 2013 4:32 PM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 27/08/2013 22:26, Erik Rull ha scritto:
Hi Stefan,
which BIOS is selected by default?
QEMU only ships with SeaBIOS.
It's more
On August 28, 2013 at 9:50 AM Stefan Hajnoczi stefa...@gmail.com 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.0 that prevents a simple Windows XP from
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
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,
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 works
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
On August 23, 2013 at 7:42 AM Markus Armbruster arm...@redhat.com wrote:
Anthony Liguori anth...@codemonkey.ws writes:
On Aug 22, 2013 4:55 PM, Erik Rull erik.r...@rdsoftware.de wrote:
Markus Armbruster wrote:
Erik Rull erik.r...@rdsoftware.de writes:
Markus Armbruster wrote
Markus Armbruster wrote:
Erik Rull erik.r...@rdsoftware.de writes:
Markus Armbruster wrote:
Erik Rull erik.r...@rdsoftware.de 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
Markus Armbruster wrote:
Erik Rull erik.r...@rdsoftware.de 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
On August 19, 2013 at 6:15 PM Erik Rull erik.r...@rdsoftware.de wrote:
Luiz Capitulino wrote:
On Fri, 16 Aug 2013 14:21:50 +0100
Peter Maydell peter.mayd...@linaro.org wrote:
On 16 August 2013 08:59, Erik Rull erik.r...@rdsoftware.de wrote:
Hi all,
when using the released qemu
Luiz Capitulino wrote:
On Fri, 16 Aug 2013 14:21:50 +0100
Peter Maydell peter.mayd...@linaro.org wrote:
On 16 August 2013 08:59, Erik Rull erik.r...@rdsoftware.de 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
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 erik.r...@rdsoftware.de writes:
Hi all,
I'm struggling with the QEMU VNC on qemu-kvm-1.2.0 a bit
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
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
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 only
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,
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
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.mak
GEN
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?
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 -
Hi,
thanks for your quick reply.
Dunrong Huang wrote:
On Wed, Dec 26, 2012 at 8:04 PM, Erik Rull erik.r...@rdsoftware.de 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
On August 9, 2012 at 10:59 AM Gerd Hoffmann kra...@redhat.com 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
On August 9, 2012 at 10:59 AM Gerd Hoffmann kra...@redhat.com 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
Hi all,
how can I close an open telnet session to my qemu monitor? I didn't find
any possiblity beside killing my telnet client on my remote connected system.
Is there a nicer way of doing that? quit is definitively the wrong
command :-)
Thanks.
Best regards,
Erik
Paolo Bonzini wrote:
Il 16/07/2012 08:47, Erik Rull ha scritto:
how can I disable a switch to the parallel0 console when accidentially
pressing Ctrl + Alt + 2?
I don't need such a feature and it confuses some users of the running guest
system (some language layouts have the @ placed on the 2
Hi all,
how can I disable a switch to the parallel0 console when accidentially
pressing Ctrl + Alt + 2?
I don't need such a feature and it confuses some users of the running guest
system (some language layouts have the @ placed on the 2 where you need to
access either with AltGr or Ctrl + Alt).
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
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
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 QEMU git head. Known issues
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
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:
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
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 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,
that
1 - 100 of 214 matches
Mail list logo
