ws to store all wide char as well as the WACS values.
> > >
> > > Signed-off-by: Samuel Thibault
> > > Cc: Eddie Kohler
> >
> > So the difference to the patch from Eddie is that charset
> > is configurable instead of being hard-coded to CP437?
>
> Yes.
>
> Samuel
>
switches QEMU to use wide-character
functions, using the VGA character Unicode equivalents from
Wikipedia. It works for me, and I'm hoping something like it would be
acceptable for QEMU.
Thanks for any comments,
Eddie Kohler
***
All VGA console characters have Unicode equivalents, and most
m
Hi
-vnc HOST:PORT,reverse connections are currently broken, because
vnc_refresh_server_surface is called before the guest is actually
available. The following patch fixes reverse connections.
Eddie
>From 32fe1bc61ee9f2f1a8220642a48acb05b5be7322 Mon Sep 17 00:00:00 2001
From: Eddie Kohler
D
Hi,
I would like to make QEMU snapshots work with read-only image files of
some kind (QCOW2 or whatever else). In other words, I would like to use
-loadvm with a read-only hard disk image.
Several years ago I sent in a patch that allowed the use of -loadvm with
read-only QCOW2 files:
http
OK, thanks. I understand how you're relying on the current behavior.
I'd rather not change all of QEMU and GDB in one step, but I'd like to
address this. QEMU documentation implies, and new users expect, that
debugging uses virtual addresses, not the segmentation-specific "linear
addresses"
Thanks for the response. I agree the patch is a workaround, but it is a
useful workaround, and I'd still argue for including it.
The patch doesn't *require* that CS.base == DS.base. Breakpoints
correctly and exclusively use CS.base. However, any memory examination
uses DS.base, and you're r
posted
several years ago.)
Thanks,
Eddie Kohler
>From 6784824c7576514456a989192e07e63352bdb4ae Mon Sep 17 00:00:00 2001
From: Eddie Kohler
Date: Fri, 24 Sep 2010 16:42:27 -0700
Subject: [PATCH] i386 debugging stubs: Consider segment bases
- Access dumpable memory relative to the current d
is is a reasonable assumption. Making the code work for
different code and data offsets would be more invasive.
Please accept this patch (this is a resend.)
Eddie Kohler
Index: target-i386/helper2.c
===
RCS file: /sources/qemu
andrzej zaborowski wrote:
On 03/02/2008, Eddie Kohler <[EMAIL PROTECTED]> wrote:
The following patch, against cvs, supports read-only snapshots on read-only
qcow2 image files. Snapshots can be loaded, but not saved. This is really
useful in my context, which is operating systems proje
Warner Losh wrote:
From: Andreas Färber <[EMAIL PROTECTED]>
Subject: Re: [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x
Date: Tue, 5 Feb 2008 13:58:28 +0100
Am 05.02.2008 um 12:30 schrieb Ian Jackson:
I don't believe that 10.0.2.0/24 was chosen randomly :-). It would be
better for qemu's
the boot process,
allowing them to run their code right away.
Please let me know if anything needs changing.
Eddie Kohler
Index: block-qcow2.c
===
RCS file: /sources/qemu/qemu/block-qcow2.c,v
retrieving revision 1.10
diff -u -u
Well, attached is a patch with ",reverse" syntax, anyway; hopefully one of
these syntaxes is OK!
Eddie
Anthony Liguori wrote:
Daniel P. Berrange wrote:
On Wed, Jan 16, 2008 at 07:09:03AM -0800, Eddie Kohler wrote:
Daniel P. Berrange wrote:
We already have the abili
Anthony Liguori wrote:
This doesn't feel like an option to me, though; rather a different
means of connecting. Among other things, in "-vnc :0", the QEMU VNC
server opens port 5900. But the client's listening port for reverse
connections defaults to 5500. "-vnc :-400,rev" is clearly insane,
Daniel P. Berrange wrote:
We already have the ability to pass multiple flags / options to the VNC
driver as a post-fix to the host:port pair, so I'm not a fan of introducing
a new option as a prefix. If using existing options syntax, it could look
like:
-vnc :5500,rev
-vnc read.cs.ucla.edu:5
Hi all,
This patch against current CVS adds VNC reverse connections, where the server
connects actively to a waiting client, as in "-vnc rev:5500" or "-vnc
rev:read.cs.ucla.edu:5500". This is quite useful if the user expects to run
QEMU many times in succession (for example, is debugging a to
translation.
I'm not sure this is the right way to do it (in fact, I'm sure that the memory
examination patch is the WRONG way to do it) and would appreciate pointers or
advice.
Thanks,
Eddie Kohler
diff -ru qemu-0.9.1/target-i386/helper2.c qemu-0.9.1-p/target-i386/helper2.c
---
16 matches
Mail list logo
