On 04.11.2015 23:04, Paolo Bonzini wrote:
On 04/11/2015 22:33, Gerhard Wiesinger wrote:
What is the problem you are seeing? KVM can emulate task switches; the
intercept is set here because of a processor erratum that can mess them
up even though, in theory, AMD supports task switching from
On 04.11.2015 22:27, Paolo Bonzini wrote:
On 04/11/2015 20:33, Gerhard Wiesinger wrote:
Signed-off-by: Gerhard Wiesinger
---
arch/x86/kvm/svm.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 2f9ed1f..e0b00fc 100644
--- a/arch/x86
Signed-off-by: Gerhard Wiesinger
---
arch/x86/kvm/svm.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 2f9ed1f..e0b00fc 100644
--- a/arch/x86/kvm/svm.c
+++ b/arch/x86/kvm/svm.c
@@ -198,6 +198,10 @@ static bool npt_enabled;
static int
Negative also here:
Don't see anything on screen on startup...
From log, latest qemu-kvm git version:
Running option rom at c180:3d4e
Running option rom at c180:3da2
Running option rom at c180:3df6
Running option rom at c580:0003
qemu-system-x86_64: /root/download/qemu/git/qemu-kvm/exec.c:2641:
On 15.04.2012 11:44, Avi Kivity wrote:
On 04/12/2012 09:32 PM, Gerhard Wiesinger wrote:
Hello,
I'm having problems with recents kernels and qemu-kvm with a DOS VM:
TD286
System: Bad selector: 0007
System: Bad selector: 0D87
System: Bad selector: 001F
System: Bad selector: 0007
GP at 0020
On Mon, 16 Apr 2012, Avi Kivity wrote:
On 04/16/2012 01:30 PM, Roedel, Joerg wrote:
On Mon, Apr 16, 2012 at 12:25:37PM +0200, Jan Kiszka wrote:
On 2012-04-15 11:44, Avi Kivity wrote:
Jan, Joerg, was an AMD erratum published for the bug?
It wasn't an erratum but a documented feature limitati
On 15.04.2012 11:44, Avi Kivity wrote:
On 04/12/2012 09:32 PM, Gerhard Wiesinger wrote:
Hello,
I'm having problems with recents kernels and qemu-kvm with a DOS VM:
TD286
System: Bad selector: 0007
System: Bad selector: 0D87
System: Bad selector: 001F
System: Bad selector: 0007
GP at 0020
Hello,
I'm having problems with recents kernels and qemu-kvm with a DOS VM:
TD286
System: Bad selector: 0007
System: Bad selector: 0D87
System: Bad selector: 001F
System: Bad selector: 0007
GP at 0020 21D4 EC 0DC4
Error 269 loading D:\BP\BIN\TD286.EXE into extended memory
Another 286 DOS Extende
Hello,
Current QEMU-KVM VGA implementation have the following problem with legacy
OS (e.g. DOS with INT10h calls): Performance is low on accessing A000:0
page and doing bank switching at the 64k page.
Would a kernel mode VGA solve these problems?
How complicated is it?
Is it possible to have o
On Thu, 26 Jan 2012, Avi Kivity wrote:
On 01/25/2012 10:15 PM, Gerhard Wiesinger wrote:
On Sun, 15 Jan 2012, Avi Kivity wrote:
On 01/15/2012 04:40 PM, Gerhard Wiesinger wrote:
On Sun, 15 Jan 2012, Jan Kiszka wrote:
On 2012-01-15 15:17, Avi Kivity wrote:
Otherwise, the dirty log
On Sun, 15 Jan 2012, Avi Kivity wrote:
On 01/15/2012 04:40 PM, Gerhard Wiesinger wrote:
On Sun, 15 Jan 2012, Jan Kiszka wrote:
On 2012-01-15 15:17, Avi Kivity wrote:
Otherwise, the dirty log information is lost in the kernel forever.
Fixes opensuse-12.1 boot screen, which changes the vga
On Sun, 15 Jan 2012, Jan Kiszka wrote:
On 2012-01-15 15:17, Avi Kivity wrote:
Otherwise, the dirty log information is lost in the kernel forever.
Fixes opensuse-12.1 boot screen, which changes the vga windows rapidly.
Confirmed, problems solved here.
Problem from: http://permalink.gmane.or
On Tue, 19 Jul 2011, Hannes Reinecke wrote:
This patch adds an emulation for the LSI Megaraid SAS 8708EM2 HBA.
It is based off the 'block' tree from Kevin Wolf, as he pulled
in the preliminary patches.
I've tested it to work with Linux, Windows Vista, and Windows7.
Why hasn't this patch already
Hello Avi,
Thnx, fixed: OK, maybe some credits :-)
Acked-by: Gerhard Wiesinger
This pattern is still present at (maybe some further problems!!!) and I
guess it has to be fixed, too:
grep -ir 'ops, s, "' .
./hw/rtl8139.c:memory_region_init_io(&s->bar_io, &rt
On Thu, 11 Aug 2011, Avi Kivity wrote:
Or maybe it's just -O2 screwing up debug information. Please change
./configure to set -O1 and redo.
Please print *r.memory as well.
./configure --target-list=x86_64-softmmu,i386-softmmu --enable-debug
Rest below.
Ciao,
Gerhard
--
http://www.wiesinger
On Thu, 11 Aug 2011, Avi Kivity wrote:
This should be faster today with really new kernels (the problem is not in
qemu) but I'm not sure if it's fast enough.
What's a "really new" kernel? In which version were performance
optimizations done? (Currently I'm using 2.6.34.7, hadn't time yet to
u
On Thu, 11 Aug 2011, Avi Kivity wrote:
On 08/11/2011 12:01 PM, Gerhard Wiesinger wrote:
Hello Avi,
#0 0x003a060328f5 in raise () from /lib64/libc.so.6
#1 0x003a060340d5 in abort () from /lib64/libc.so.6
#2 0x003a0602b8b5 in __assert_fail () from /lib64/libc.so.6
#3
Hello Avi,
#0 0x003a060328f5 in raise () from /lib64/libc.so.6
#1 0x003a060340d5 in abort () from /lib64/libc.so.6
#2 0x003a0602b8b5 in __assert_fail () from /lib64/libc.so.6
#3 0x00435339 in memory_region_del_subregion (mr=,
subregion=)at
/root/download/qemu/git/qem
Hello Avi,
Thank for the fast fix. Unfortunatly it still doesn't work (but LSI BIOS
is initialized correctly).
I'm getting at boot time:
qemu-system-x86_64: /qemu-kvm-test/memory.c:1168:
memory_region_del_subregion: Assertion `subregion->parent == mr' failed.
Thnx.
Ciao,
Gerhard
--
http:/
Hello Avi,
qemu/qemu-kvm doesn't boot any more with LSI option rom (-option-rom
8xx_64.rom). Guess it comes from changes of the memory API. Also latest
git version from seabios.
Sorry, no further details currently available.
Ciao,
Gerhard
--
http://www.wiesinger.com/
On Mon, 8 Aug 2011, A
ard Wiesinger wrote:
On Mon, 10 May 2010, Avi Kivity wrote:
On 05/09/2010 10:35 PM, Gerhard Wiesinger wrote:
For 256 color more the first priority is to find out why direct mapping is
not used. I'd suggest tracing the code that makes this decision (in
hw/*vga.c) and seeing if it's
On Mon, 10 May 2010, Avi Kivity wrote:
On 05/09/2010 10:35 PM, Gerhard Wiesinger wrote:
For 256 color more the first priority is to find out why direct mapping is
not used. I'd suggest tracing the code that makes this decision (in
hw/*vga.c) and seeing if it's right or not.
On Thu, 22 Apr 2010, Avi Kivity wrote:
On 04/22/2010 09:04 AM, Gerhard Wiesinger wrote:
On Wed, 21 Apr 2010, Avi Kivity wrote:
On 04/21/2010 09:50 PM, Gerhard Wiesinger wrote:
I don't think changing VGA window is a problem because there are
500.000-1Mio changes/s possible.
1MB/s, 50
On Wed, 28 Apr 2010, Avi Kivity wrote:
On 04/28/2010 07:37 AM, Gerhard Wiesinger wrote:
Hello,
I saw that KVM git repository is not updated from QEMU repository very
often. Is it possible to integrate QEMU git tree into KVM git regularly as
qemu git tree is very dynamic. E.g. last commit
Hello,
I saw that KVM git repository is not updated from QEMU repository very
often. Is it possible to integrate QEMU git tree into KVM git regularly as
qemu git tree is very dynamic. E.g. last commit was more than 2 weeks ago.
I think it is necessary to integrate early and often as a lot of b
On Wed, 21 Apr 2010, Jamie Lokier wrote:
Gerhard Wiesinger wrote:
Hmmm. I'm very new to QEMU and KVM but at least accessing the virtual HW
of QEMU even from KVM must be possible (e.g. memory and port accesses are
done on nearly every virtual device) and therefore I'm ending in C c
On Wed, 21 Apr 2010, Avi Kivity wrote:
On 04/21/2010 09:50 PM, Gerhard Wiesinger wrote:
I don't think changing VGA window is a problem because there are
500.000-1Mio changes/s possible.
1MB/s, 500k-1M changes/s Coincidence? Is it taking a page fault
or trap on every write?
To cl
On Wed, 21 Apr 2010, Avi Kivity wrote:
On 04/21/2010 09:39 PM, Jamie Lokier wrote:
Avi Kivity wrote:
Writes to vga in 16-color mode don't change set a memory location to a
value, instead they change multiple memory locations.
While code is just writing to the VGA memory, not reading(*) and
On Wed, 21 Apr 2010, Avi Kivity wrote:
On 04/21/2010 09:14 PM, Gerhard Wiesinger wrote:
Can you explain which code files/functions of KVM is involved in handling
VGA memory window and page switching through the port write to the VGA
window register (or is that part handled through QEMU), so
On Wed, 21 Apr 2010, Jamie Lokier wrote:
Gerhard Wiesinger wrote:
Would it be possible to handle these writes through QEMU directly
(without
KVM), because performance is there very well (looking at the code there
is some pointer arithmetic and some memory write done)?
I've noticed extr
On Wed, 21 Apr 2010, Jamie Lokier wrote:
Gerhard Wiesinger wrote:
I'm using VESA mode 0x101 (640x480 256 colors), but performance is
there very low (~1MB/s). Test is also WITHOUT any vga window change, so
there isn't any page switching overhead involved in this test case.
Any
On Wed, 21 Apr 2010, Avi Kivity wrote:
On 04/21/2010 01:08 PM, Jamie Lokier wrote:
Avi Kivity wrote:
On 04/19/2010 10:14 PM, Gerhard Wiesinger wrote:
Hello,
Finally I got QEMU-KVM to work but video performance under DOS is very
low (QEMU 0.12.3 stable and QEMU GIT master branch is fast
On Wed, 21 Apr 2010, Avi Kivity wrote:
On 04/19/2010 10:14 PM, Gerhard Wiesinger wrote:
Hello,
Finally I got QEMU-KVM to work but video performance under DOS is very low
(QEMU 0.12.3 stable and QEMU GIT master branch is fast, QEMU KVM is slow)
I'm measuring 2 performance critical
QEMU 0.12.3 and QEMU GIT
==
INT10PER performance information V1.0, (c) 2010 by Gerhard Wiesinger
VESA set window: seconds=2, operations=100, ops/s=50.0
VESA set window (nc): seconds=2, operations=100, ops/s=50.0
VESA get w
34 matches
Mail list logo
