Jorge Lucángeli Obes wrote:
[...]
Laurent, do you want the patches for the functionality that's working
right now? We can divide the (not very big amount of) work that's
left. It consists basically on teaching qemu how to look for command
line options, if none are present on the current
On 7/30/07, Avi Kivity [EMAIL PROTECTED] wrote:
Jorge Lucángeli Obes wrote:
Hi Avi, hi all,
I believe that Laurent (copied) is also interested in this area.
Copied him.
I've started some (very minor) groundwork for this task. My idea was
to add an extra annotation field in qcow2
The old_exception field is initialized on startup with 0.
Therefore the very first fault (e.g. #GP) could be converted
to a double fault on an application processor. The attached
patch initialize old_exception on every CPU reset with -1.
Bernhard Kauer
Index: target-i386/helper2.c
The PIC initilization should respect the fourth byte init
bit in single mode.
Bernhard Kauer
Index: hw/i8259.c
===
RCS file: /sources/qemu/qemu/hw/i8259.c,v
retrieving revision 1.22
diff -u -r1.22 i8259.c
--- hw/i8259.c 7
The current VNC server implementation does not have support for the
authentication of incoming client connections. The following series
of patches provide support for a number of alternatives, all compliant
with the VNC protocol spec. The simplest mechanism (and the weakest)
is the traditional VNC
This patch splits the vnc_display_init function into two parts,
the resulting vnc_display_init function merely initializes a
little state. The new vnc_display_open function is responsible
for starting the server. This refactoring is in preparation for
the next patch.
diff -r cdd882fa7018 vl.c
---
This patch extends the QEMU monitor 'change' command so that it can
be used to change the configuration of the VNC server. On the command
line the user can use -vnc none, and then issue the 'change vnc :1'
command later from the monitor. This is utilized in the next patch
to let the monitor fetch
This patch introduces support for VNC protocols upto 3.8 and with
it, support for password based authentication. VNC's password based
authentication is not entirely secure, but it is a standard and the
RFB spec requires that all clients support it. The password can be
provided by using the monitor
This patch introduces minimal support for the VeNCrypt protocol
extension. This layers use of TLS (aka SSL) into the VNC data stream,
providing session encryption. This patch is the bare minimum protocol
support. It is enabled by using the 'tls' option flag eg -vnc :1,tls'
This is not secure on
This patch adds support for using x509 certificates on the server
end. The server needs a CA certificate, and its own certificate and
private key. A CA revocation list is optional. This this patch the
file names are hardcoded. The next-but-one patch will make them
configurable.
The use of x509
This patch adds support for requesting and validating client certificates.
In effect the client certificates are being used as the authentication
mechansim, making VNC passwords unccessary, though using a combination of
both is also possible.
The verification of client certificates is enabled
This final code patch adds 4 new command line arguments to QEMU to allow the
certificate files to be specified. The '-x509cacert', '-x509cert' and '-x509key'
parameters are mandatory if the 'x509' or 'x509verify' flags are used when
setting up the VNC server. If the certificates are not provided,
This patch updates the user documentation to detail the new syntax
options for VNC server configuration. It moves all the display
related options into a combined logical section for clarity. It
documents the different deployment secenarios possible with the
new VNC server capabilities and their
Today, a change of the target list for a QEMU build (caused by
calling configure a second time) creates new files config-host.h
and */config.h. So make is forced to re-compile a lot of files
which depend on any of these two files - even when they did not
change anything but their time stamp.
A
On Tue, Jul 31, 2007 at 02:37:04AM +0200, Juergen Lock wrote:
On Mon, Jul 30, 2007 at 12:30:23AM +0200, Juergen Lock wrote:
On Sun, Jul 29, 2007 at 03:46:37AM +0200, andrzej zaborowski wrote:
Hi,
Hi,
On 29/07/07, Juergen Lock [EMAIL PROTECTED] wrote:
Anyway, boot now fails
Some parts for a working mips host are still missing
in QEMU CVS HEAD.
Here is a new patch which makes mips host work for
system emulation.
I tested it with i386-softmmu/qemu, mips-softmmu/qemu-system-mips
and mipsel-softmmu/qemu-system-mipsel running on
an emulated malta (big and little endian,
On 31/07/07, Juergen Lock [EMAIL PROTECTED] wrote:
On Tue, Jul 31, 2007 at 02:37:04AM +0200, Juergen Lock wrote:
On Mon, Jul 30, 2007 at 12:30:23AM +0200, Juergen Lock wrote:
On Sun, Jul 29, 2007 at 03:46:37AM +0200, andrzej zaborowski wrote:
Hi,
Hi,
On 29/07/07, Juergen Lock
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/07/31 23:07:32
Modified files:
. : configure
Log message:
A variant of move-if-change, by Stefan Weil.
CVSWeb URLs:
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/07/31 23:09:18
Modified files:
target-i386: helper2.c
Log message:
Initialize old_exception, by Bernhard Kauer.
CVSWeb URLs:
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/07/31 23:12:09
Modified files:
hw : i8259.c
Log message:
Fix i8259 initialization, by Bernhard Kauer.
CVSWeb URLs:
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/07/31 23:26:00
Modified files:
hw : cirrus_vga.c cirrus_vga_rop.h
Log message:
Cirrus transparent BITBLT (w/o color expand), by Hitoshi Osada.
CVSWeb URLs:
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/07/31 23:28:54
Modified files:
. : Changelog Makefile Makefile.target block.c vl.h
Added files:
. : block-parallels.c
Log message:
Parallels disk image
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/07/31 23:32:11
Modified files:
hw : acpi.c
Log message:
Implement ACPI specs 3.0, 4.7.2.5, by Michael Hanselmann.
CVSWeb URLs:
On Tue, Jul 31, 2007 at 11:31:58PM +0200, andrzej zaborowski wrote:
On 31/07/07, Juergen Lock [EMAIL PROTECTED] wrote:
On Tue, Jul 31, 2007 at 02:37:04AM +0200, Juergen Lock wrote:
On Mon, Jul 30, 2007 at 12:30:23AM +0200, Juergen Lock wrote:
On Sun, Jul 29, 2007 at 03:46:37AM +0200,
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/07/31 23:46:55
Modified files:
. : dyngen-exec.h exec-all.h
Log message:
Fiddly dyngen bits for s390 host support, by Ulrich Hecht.
CVSWeb URLs:
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/07/31 23:44:21
Modified files:
. : Makefile.target dis-asm.h disas.c
Added files:
. : s390-dis.c
Log message:
s390 disassembler support, by Ulrich
Ulrich Hecht wrote:
On Monday 30 July 2007 13:49, Ulrich Hecht wrote:
S/390 host support has been broken for a long time (since 0.4.2 or
something like that). I finally got around to fix it, adding
disassembly support on the way.
And here's an even better patch that also fixes non-i386
Michael Hanselmann wrote:
On Fri, Jul 27, 2007 at 09:22:08AM -0700, n schembr wrote:
Is system_powerdown a better way to stop the host? Is
system_powerdown a soft operation like the atx powersupply? It did
not work with a smoothwall guest.
It would, but is not implemented for x86.
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/08/01 00:09:31
Modified files:
. : configure
Log message:
Also match s390x.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/configure?cvsroot=qemur1=1.151r2=1.152
void op_cfc1 (void)
{
+#ifdef __s390__
+if(!T1)
+T0 = (int32_t)env-fcr0;
I guess this breaks when you _breathe_ at the compiler. Inventing
switch-table support in dyngen would be preferable (if possible...).
Actually, I'm surprised this doesn't break on other hosts.
Daniel P. Berrange wrote:
This patch extends the QEMU monitor 'change' command so that it can
be used to change the configuration of the VNC server. On the command
line the user can use -vnc none, and then issue the 'change vnc :1'
command later from the monitor. This is utilized in the next
Daniel P. Berrange wrote:
This patch introduces support for VNC protocols upto 3.8 and with
it, support for password based authentication. VNC's password based
authentication is not entirely secure, but it is a standard and the
RFB spec requires that all clients support it. The password can be
Daniel P. Berrange wrote:
This patch introduces minimal support for the VeNCrypt protocol
extension. This layers use of TLS (aka SSL) into the VNC data stream,
providing session encryption. This patch is the bare minimum protocol
support. It is enabled by using the 'tls' option flag eg -vnc
I have a pretty ugly patch against qemu 0.8 which allows the location of data
used with the -snapshot feature to be somewhere other than /var/tmp. I have a
use-case where I am creating many gigabytes of changes to disk in snapshot mode.
When 0.9 came out, I looked, but it seemed less than
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Andrzej Zaborowski balrog 07/08/01 02:31:55
Modified files:
target-arm : helper.c translate.c
Log message:
Special-case iWMMXt register transfer insns, which are in ARM LDC2/STC2
class.
CVSWeb URLs:
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Andrzej Zaborowski balrog 07/08/01 02:41:33
Modified files:
hw : spitz.c
Log message:
Move Spitz microdrive from first to second PCMCIA slot where it belongs.
CVSWeb URLs:
36 matches
Mail list logo
