VNC display support for QEMU
PATCH 1/1 VNC display support for QEMU
Hi,
The attach patch adds VNC display support for QEMU. It does not use libvncserver but was rather written from scratch. libvncserver is a really neat project and I've used it in a number of other projects but I think QEMU really requires a custom implementation.
First, to enable vnc support, you use the -vnc option like:
qemu -vnc 1
Where 1 is the first display (port 5901). This syntax may change in the near future to support binding to a particular interface. It's very useful to use an absolute mouse with VNC as the relative support is quite poor. It may be useful to adapt the libvncserver patch's calibration code here but I've not attempted to do that yet.
This patch is still experimental. I've tested it with RealVNC and TightVNC under a variety of depths but I won't be suprised if there are still problems. I only implement Raw, CopyRect, and Hextile encodings too. Any sort of palette color mode or pixel format that QEMU doesn't support will not work either.
One thing you may notice is that RealVNC has some issues with being disconnected. This is because it likes to switch from 8bit to 32bit depths automatically at startup. Unfortunately, there is a race condition in the VNC protocol and since this implementation is asynchronous, we seem to be much more prone to exposing this.
A short near-term TODO list is:
1) More testing
2) Support switching between monitor/serial
3) Support a better encoding (like TightEncoding or ZRLE)
4) Support a vnc password (and perhaps stuff like TLS)
Any feedback is greatly appreciated (especially with how it works with clients I've not tested).
Regards,
Anthony Liguori
hw/cirrus_vga.c +79 -4
@@ -644,15 +644,90 @@ (s->cirrus_blt_srcaddr & ~7)); } -static int cirrus_bitblt_videotovideo_copy (CirrusVGAState * s) +static void cirrus_do_copy (CirrusVGAState *s,int dst,int src,int w,int h) { +int sx, sy; +int dx, dy; +int width, height; +int depth; +int notify =0 ; + + depth = s->get_bpp ((VGAState *)s) /8 ; + s->get_resolution ((VGAState *)s, &width, &height); + +/* extra x, y */ + sx = (src % (width * depth)) / depth; + sy = (src / (width * depth)); + dx = (dst % (width *depth)) / depth; + dy = (dst / (width * depth)); + +/* normalize width */ + w /= depth; + +/* if we're doing a backward copy, we have to adjust +our x/y to be the upper left corner (instead of the lower +right corner) */ +if (s->cirrus_blt_dstpitch <0 ) { + sx -= (s->cirrus_blt_width / depth) -1 ; + dx -= (s->cirrus_blt_width / depth) -1 ; + sy -= s->cirrus_blt_height -1 ; + dy -= s->cirrus_blt_height -1 ; + } + +/* are we in the visible portion of memory? */ +if (sx >=0 && sy >=0 && dx >=0 && dy >=0 && + (sx + w) <= width && (sy + h) <= height && + (dx + w) <= width && (dy + h) <= height) { + notify =1 ; + } + +/* make to sure only copy if it's a plain copy ROP */ +if (*s->cirrus_rop != cirrus_bitblt_rop_fwd_src && + *s->cirrus_rop != cirrus_bitblt_rop_bkwd_src) + notify =0 ; + +/* we have to flush all pending changes so that the copy +is generated at the appropriate moment in time */ +if (notify) +vga_hw_update (); + (*s->cirrus_rop) (s, s->vram_ptr + s->cirrus_blt_dstaddr, s->vram_ptr + s->cirrus_blt_srcaddr, s->cirrus_blt_dstpitch, s->cirrus_blt_srcpitch, s->cirrus_blt_width, s->cirrus_blt_height); -cirrus_invalidate_region (s, s->cirrus_blt_dstaddr, - s->cirrus_blt_dstpitch, s->cirrus_blt_width, - s->cirrus_blt_height); + +if (notify) + s->ds->dpy_copy (s->ds, + sx, sy, dx, dy, + s->cirrus_blt_width / depth, + s->cirrus_blt_height); + +/* we don't have to notify the display that this portion has +changed since dpy_copy implies this */ + +if (!notify) +cirrus_invalidate_region (s, s->cirrus_blt_dstaddr, + s->cirrus_blt_dstpitch, s->cirrus_blt_width, + s->cirrus_blt_height); +} + +static int cirrus_bitblt_videotovideo_copy (CirrusVGAState * s) +{ +if (s->ds->dpy_copy) { +cirrus_do_copy (s, s->cirrus_blt_dstaddr - s->start_addr, + s->cirrus_blt_srcaddr - s->start_addr, + s->cirrus_blt_width, s->cirrus_blt_height); + }else { + (*s->cirrus_rop) (s, s->vram_ptr + s->cirrus_blt_dstaddr, + s->vram_ptr + s->cirrus_blt_srcaddr, + s->cirrus_blt_dstpitch, s->cirrus_blt_srcpitch, + s->cirrus_blt_width, s->cirrus_blt_height); + +cirrus_invalidate_region (s, s->cirrus_blt_dstaddr, + s->cirrus_blt_dstpitch, s->cirrus_blt_width, + s->cirrus_blt_height); + } +return 1 ; }
Makefile.target +4 -0
@@ -357,6 +357,7 @@ ifdef CONFIG_SDL VL_OBJS+=sdl.o endif +VL_OBJS+=vnc.o ifdef CONFIG_COCOA VL_OBJS+=cocoa.o COCOA_LIBS=-F/System/Library/Frameworks -framework Cocoa -framework IOKit
@@ -409,6 +410,9 @@ sdl.o: sdl.c keymaps.c sdl_keysym.h $(CC) $(CFLAGS) $(DEFINES) $(SDL_CFLAGS) -c -o $@ $< +vnc.o: vnc.c keymaps.c sdl_keysym.h vnchextile.h + $(CC) $(CFLAGS) $(DEFINES) -c -o $@ $< + sdlaudio.o: sdlaudio.c $(CC) $(CFLAGS) $(DEFINES) $(SDL_CFLAGS) -c -o $@ $<
qemu-doc.texi +7 -0
@@ -185,6 +185,13 @@ the console. Therefore, you can still use QEMU to debug a Linux kernel with a serial console. +@item -vnc d + +Normally, QEMU uses SDL to display the VGA output. With this option, +you can have QEMU listen on VNC display d and redirect the VGA display +over the VNC session. It is very useful to enable the usb tablet device +when using this option. + @item -k language Use keyboard layout @var{language} (for example @code{fr} for
vl.c +13 -0
@@ -149,6 +149,7 @@USBDevice *vm_usb_hub;static VLANState *first_vlan;int smp_cpus =1 ; +int vnc_display =-1 ;#if defined(TARGET_SPARC )#define MAX_CPUS 16#elif defined(TARGET_I386 )
@@ -4638,6 +4639,7 @@ " (default is CL-GD5446 PCI VGA)\n"#endif "-loadvm file start right away with a saved state (loadvm in monitor)\n" +"-vnc display start a VNC server on display\n" "\n" "During emulation, the following keys are useful:\n" "ctrl-alt-f toggle full screen\n"
@@ -4721,6 +4723,7 @@ QEMU_OPTION_usb, QEMU_OPTION_usbdevice, QEMU_OPTION_smp, + QEMU_OPTION_vnc, }; typedef struct QEMUOption {
@@ -4788,6 +4791,7 @@ { "win2k-hack", 0, QEMU_OPTION_win2k_hack }, { "usbdevice", HAS_ARG, QEMU_OPTION_usbdevice }, { "smp", HAS_ARG, QEMU_OPTION_smp }, + { "vnc", HAS_ARG, QEMU_OPTION_vnc },/* temporary options */ { "usb", 0, QEMU_OPTION_usb },
@@ -5386,6 +5390,13 @@exit (1 ); }break ; +case QEMU_OPTION_vnc: + vnc_display =atoi (optarg); +if (vnc_display <0 ) { +fprintf (stderr,"Invalid VNC display\n" ); +exit (1 ); + } +break ; } } }
@@ -5551,6 +5562,8 @@/* terminal init */ if (nographic) {dumb_display_init (ds); + }if (vnc_display !=-1 ) { +vnc_display_init (ds, vnc_display); }else {#if defined(CONFIG_SDL )sdl_display_init (ds, full_screen);
vl.h +13 -0
@@ -82,6 +82,13 @@#define tostring (s) #s#endif +#ifndef MIN +#define MIN (a, b) (((a) < (b)) ? (a) : (b)) +#endif +#ifndef MAX +#define MAX (a, b) (((a) > (b)) ? (a) : (b)) +#endif +/* vl.c */ uint64_t muldiv64 (uint64_t a,uint32_t b,uint32_t c);
@@ -672,9 +679,12 @@int depth;int width;int height; +void *opaque; +void (*dpy_update)(struct DisplayState *s,int x,int y,int w,int h);void (*dpy_resize)(struct DisplayState *s,int w,int h);void (*dpy_refresh)(struct DisplayState *s); +void (*dpy_copy)(struct DisplayState *s,int src_x,int src_y,int dst_x,int dst_y,int w,int h); };static inline void dpy_update (DisplayState *s,int x,int y,int w,int h)
@@ -703,6 +713,9 @@/* cocoa.m */ void cocoa_display_init (DisplayState *ds,int full_screen); +/* vnc.c */ +void vnc_display_init (DisplayState *ds,int display); +/* ide.c */ #define MAX_DISKS 4
vnc.c +894 -0
894 lines not on this page · raw message
vnchextile.h +189 -0
189 lines not on this page · raw message
vnc_keysym.h +275 -0
275 lines not on this page · raw message
Hi,
Quoted 5 lines · Anthony Liguori
One thing you may notice is that RealVNC has some issues with being disconnected. This is because it likes to switch from 8bit to 32bit depths automatically at startup. Unfortunately, there is a race condition in the VNC protocol and since this implementation is asynchronous, we seem to be much more prone to exposing this.
This, along with other problems, has been solved with LibVNCServer. But of course, you are welcome to solve them again.
Ciao,
Dscho
Hi Johannes,
Quoted 5 lines · Johannes Schindelin
Hi,
On Sat, 29 Apr 2006, Anthony Liguori wrote:
Quoted 9 lines
Quoted 6 lines
One thing you may notice is that RealVNC has some issues with being disconnected. This is because it likes to switch from 8bit to 32bit depths automatically at startup. Unfortunately, there is a race condition in the VNC protocol and since this implementation is asynchronous, we seem to be much more prone to exposing this.
This, along with other problems, has been solved with LibVNCServer. But of course, you are welcome to solve them again.
I should mention, the majority of the "smarts" of this patch are QEMU specific optimizations. The first one maintains a separate copy of the client's framebuffer to use to reduce the size of the updates generated by the VGA code. The second one hooks the Cirrus 2d video-to-video copy to generate VNC CopyRect updates.
The actual VNC side of the code is pretty trivial.
I would have been more inclined to use LibVNCServer if it wasn't based on threading. I really wanted an asynchronous implementation of a VNC server that didn't depend on threads.
Regards,
Anthony Liguori
Quoted 10 lines
Ciao,
Dscho_______________________________________________
Qemu-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Hi,
Quoted 3 lines · Anthony Liguori
I would have been more inclined to use LibVNCServer if it wasn't based on threading. I really wanted an asynchronous implementation of a VNC server that didn't depend on threads.
AFAICT it does not. In vnc_refresh(), there is a call to rfbProcessEvents, which says to select() the socket(s) for 0 microseconds. Same thread.
Now, there is a facility in LibVNCServer to take advantage of pthreads, and in some applications it is actually better to run a background thread to handle all the VNC stuff. But it is not used in QEmu.
Ciao,
Dscho
Quoted 10 lines · Johannes Schindelin
Hi,
Quoted 2 lines · Anthony Liguori
I would have been more inclined to use LibVNCServer if it wasn't based on threading. I really wanted an asynchronous implementation of a VNC server that didn't depend on threads.
AFAICT it does not. In
vnc_refresh(), there is a call to rfbProcessEvents, which says toselect()the socket(s) for 0 microseconds. Same thread.
There is a fundamental design in the LibVNCServer code (which I believe was inherited from the various RealVNC derivatives) that all IO is done through some derivation of rfbReadExact. rfbReadExact is semantically synchronous (it uses select to enforce that).
You could, perhaps, not begin an iteration of the server message process loop until the socket becomes readable but that only gives you a semi-asynchronous interface. As soon as you get 1 byte of message data, you are now handling things synchronously until that message is complete.
Since QEMU is single threaded, this means everything blocks (including progress of the guest). This theoretical problem is why I implemented a true asynchronous VNC implementation. You'll notice that I use a state machine to handle the message dispatch (which is practical for the server side of the VNC protocol at least). My VNC will never (assuming it's working correctly :-)) block guest progress because of outstanding IO.
There is a practical problem too with a semi-asynchronous approach. It's entirely possible to get serious congestion in odd places during a message transmission (or even a loss that requires timeout). This means you could end up blocking the guest for a prolonged period of time (and if the guest is doing serious work--like hosting some sort of network service--this is catastrophic).
So, in a multithreaded application or a single-threaded application that doesn't have to worry about these things, LibVNCServer is a great solution. I just don't think it's the right solution for QEMU for the reasons outlined above.
Regards,
Anthony Liguori
Quoted 12 lines
Now, there is a facility in LibVNCServer to take advantage of pthreads, and in some applications it is actually better to run a background thread to handle all the VNC stuff. But it is not used in QEmu.
Ciao,
Dscho_______________________________________________
Qemu-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/qemu-devel
just a quick note: your patch breaks the mingw32 build on winXP. Christian
for d in i386-softmmu; do \
make -C $d all || exit 1 ; \
done
make[1]: Entering directory `/home/root/qemu/i386-softmmu'
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I.. -I/home/root/qemu/target-i386 -I/home/root/qemu -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/root/qemu/fpu -DHAS_AUDIO -I/home/root/qemu/slirp -c -o vnc.o /home/root/qemu/vnc.c c:/qemu/mingw/home/root/qemu/vnc.c:3:24: sys/socket.h: No such file or directory c:/qemu/mingw/home/root/qemu/vnc.c:4:24: netinet/in.h: No such file or directory c:/qemu/mingw/home/root/qemu/vnc.c:5:25: netinet/tcp.h: No such file or directory
c:/qemu/mingw/home/root/qemu/vnc.c: In function `vnc_client_write':
c:/qemu/mingw/home/root/qemu/vnc.c:414: error: `ssize_t' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:414: error: (Each undeclared identifier is reported only once c:/qemu/mingw/home/root/qemu/vnc.c:414: error: for each function it appears in.) c:/qemu/mingw/home/root/qemu/vnc.c:414: error: syntax error before "ret" c:/qemu/mingw/home/root/qemu/vnc.c:417: error: `ret' undeclared (first use in this function)
c:/qemu/mingw/home/root/qemu/vnc.c: In function `vnc_client_read':
c:/qemu/mingw/home/root/qemu/vnc.c:439: error: ssize_t' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:439: error: syntax error before "ret" c:/qemu/mingw/home/root/qemu/vnc.c:443: error: ret' undeclared (first use in this function)
c:/qemu/mingw/home/root/qemu/vnc.c: In function `vnc_listen_read':
c:/qemu/mingw/home/root/qemu/vnc.c:810: error: storage size of `addr' isn't known
c:/qemu/mingw/home/root/qemu/vnc.c:811: error: `socklen_t' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:811: error: syntax error before "addrlen" c:/qemu/mingw/home/root/qemu/vnc.c:813: warning: implicit declaration of function `accept'
c:/qemu/mingw/home/root/qemu/vnc.c:813: error: addrlen' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:815: warning: implicit declaration of function fcntl'
c:/qemu/mingw/home/root/qemu/vnc.c:815: error: F_SETFL' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:815: error: O_NONBLOCK' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:810: warning: unused variable addr' c:/qemu/mingw/home/root/qemu/vnc.c: In function vnc_display_init':
c:/qemu/mingw/home/root/qemu/vnc.c:830: error: storage size of `addr' isn't known
c:/qemu/mingw/home/root/qemu/vnc.c:853: warning: implicit declaration of function `socket'
c:/qemu/mingw/home/root/qemu/vnc.c:853: error: PF_INET' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:853: error: SOCK_STREAM' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:859: error: AF_INET' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:860: warning: implicit declaration of function htons'
c:/qemu/mingw/home/root/qemu/vnc.c:864: warning: implicit declaration of function `setsockopt'
c:/qemu/mingw/home/root/qemu/vnc.c:864: error: SOL_SOCKET' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:864: error: SO_REUSEADDR' undeclared (first use in this function) c:/qemu/mingw/home/root/qemu/vnc.c:871: warning: implicit declaration of function `bind'
c:/qemu/mingw/home/root/qemu/vnc.c:876: warning: implicit declaration of function `listen'
c:/qemu/mingw/home/root/qemu/vnc.c:830: warning: unused variable `addr' make[1]: *** [vnc.o] Error 1
make[1]: Leaving directory `/home/root/qemu/i386-softmmu'
make: *** [all] Error 1
neat! it is working on windows 3.0 guest (no acceleration) on a winXP host. Fabrice fixed it live while I was trying it (he's fast!).
old mouse sync problem is still here, as you mentionned no calibration is done. You mention "absolute mouse". how to do it ?
Quoted 2 lines · Christian MICHON
just a quick note: your patch breaks the mingw32 build on winXP. Christian
Quoted 2 lines · Christian MICHON
neat! it is working on windows 3.0 guest (no acceleration) on a winXP host. Fabrice fixed it live while I was trying it (he's fast!).
Yeah, sorry about that. Fortunately, Fabrice rocks :-)
Quoted 2 lines
old mouse sync problem is still here, as you mentionned no calibration is done. You mention "absolute mouse". how to do it ?
You would need at least a win98 guest. You then have to add '-usb -usbdevice tablet' to the qemu command line.
Regards,
Anthony Liguori
Quoted 3 lines · Christian MICHON
Quoted 2 lines
just a quick note: your patch breaks the mingw32 build on winXP. Christian
PATCH 1/1 Enhanced Documentation
In reply to Johannes SchindelinHere are three patches which enhance and fix the existing QEMU documentation.
1. Makefile: added rules to build qemu-doc and qemu-tech in info and dvi format. I did not add a dependency which calls these rules automatically, so run make qemu-doc.info qemu-tech.info qemu-doc.dvi qemu-tech.dvi to build the new targets.
2. qemu-doc.texi, qemu-tech.texi:
* fixed for generation of info files
* fixed long lines for generation of dvi / ps / pdf files
* fixed html title
* added menus for html and info
* added table of contents for html and dvi
* added index (still empty) for html, info and dvi
* fixed minor spelling bug (reasonnable)
All documentation formats should build now without error messages (my test on Debian Linux passed).
Regards
Stefan Weil
Index: qemu-doc.texi
===================================================================
RCS file: /sources/qemu/qemu/qemu-doc.texi,v
retrieving revision 1.85
qemu-doc.texi +154 -36
@@ -1,16 +1,46 @@ \input texinfo @c -*- texinfo -*- +@c %**start of header +@setfilename qemu-doc.info +@settitle QEMU CPU Emulator User Documentation +@exampleindent 0 +@paragraphindent 0 +@c %**end of header @iftex -@settitle QEMU CPU Emulator User Documentation @titlepage @sp 7 -@center @titlefont{QEMU CPU Emulator User Documentation} +@center @titlefont{QEMU CPU Emulator} +@sp 1 +@center @titlefont{User Documentation} @sp 3 @end titlepage @end iftex +@ifnottex +@node Top +@top + +@menu +* Introduction:: +* Installation:: +* QEMU PC System emulator:: +* QEMU System emulator for non PC targets:: +* QEMU Linux User space emulator:: +* compilation:: Compilation from the sources +* Index:: +@end menu +@end ifnottex + +@contents + +@node Introduction @chapter Introduction +@menu +* intro_features:: Features +@end menu + +@node intro_features @section Features QEMU is a FAST! processor emulator using dynamic translation to
@@ -52,27 +82,53 @@ For user emulation, x86, PowerPC, ARM, MIPS, and Sparc32/64 CPUs are supported. +@node Installation @chapter Installation If you want to compile QEMU yourself, see @ref{compilation}. +@menu +* install_linux:: Linux +* install_windows:: Windows +* install_mac:: Macintosh +@end menu + +@node install_linux @section Linux If a precompiled package is available for your distribution - you just have to install it. Otherwise, see @ref{compilation}. +@node install_windows @section Windows Download the experimental binary installer at -@url{http://www.free.oszoo.org/download.html}. +@url{http://www.free.oszoo.org/@/download.html}. +@node install_mac @section Mac OS X Download the experimental binary installer at -@url{http://www.free.oszoo.org/download.html}. +@url{http://www.free.oszoo.org/@/download.html}. +@node QEMU PC System emulator @chapter QEMU PC System emulator +@menu +* pcsys_introduction:: Introduction +* pcsys_quickstart:: Quick Start +* sec_invocation:: Invocation +* pcsys_keys:: Keys +* pcsys_monitor:: QEMU Monitor +* disk_images:: Disk Images +* pcsys_network:: Network emulation +* direct_linux_boot:: Direct Linux Boot +* pcsys_usb:: USB emulation +* gdb_usage:: GDB usage +* pcsys_os_specific:: Target OS specific information +@end menu + +@node pcsys_introduction @section Introduction @c man begin DESCRIPTION
@@ -118,6 +174,7 @@ @c man end +@node pcsys_quickstart @section Quick Start Download and uncompress the linux image (@file{linux.img}) and type:
@@ -147,14 +204,14 @@ @item -fda file @item -fdb file -Use @var{file} as floppy disk 0/1 image (@xref{disk_images}). You can +Use @var{file} as floppy disk 0/1 image (@pxref{disk_images}). You can use the host floppy by using @file{/dev/fd0} as filename. @item -hda file @item -hdb file @item -hdc file @item -hdd file -Use @var{file} as hard disk 0, 1, 2 or 3 image (@xref{disk_images}). +Use @var{file} as hard disk 0, 1, 2 or 3 image (@pxref{disk_images}). @item -cdrom file Use @var{file} as CD-ROM image (you cannot use @option{-hdc} and and
@@ -168,7 +225,7 @@ @item -snapshot Write to temporary files instead of disk image files. In this case, the raw disk image you use is not written back. You can however force -the write back by pressing @key{C-a s} (@xref{disk_images}). +the write back by pressing @key{C-a s} (@pxref{disk_images}). @item -m megs Set virtual RAM size to @var{megs} megabytes. Default is 128 MB.
@@ -297,9 +354,12 @@ Example: @example # launch a first QEMU instance -qemu linux.img -net nic,macaddr=52:54:00:12:34:56 -net socket,listen=:1234 -# connect the VLAN 0 of this instance to the VLAN 0 of the first instance -qemu linux.img -net nic,macaddr=52:54:00:12:34:57 -net socket,connect=127.0.0.1:1234 +qemu linux.img -net nic,macaddr=52:54:00:12:34:56 \ + -net socket,listen=:1234 +# connect the VLAN 0 of this instance to the VLAN 0 +# of the first instance +qemu linux.img -net nic,macaddr=52:54:00:12:34:57 \ + -net socket,connect=127.0.0.1:1234 @end example @item -net socket[,vlan=n][,fd=h][,mcast=maddr:port]
@@ -321,17 +381,22 @@ Example: @example # launch one QEMU instance -qemu linux.img -net nic,macaddr=52:54:00:12:34:56 -net socket,mcast=230.0.0.1:1234 +qemu linux.img -net nic,macaddr=52:54:00:12:34:56 \ + -net socket,mcast=230.0.0.1:1234 # launch another QEMU instance on same "bus" -qemu linux.img -net nic,macaddr=52:54:00:12:34:57 -net socket,mcast=230.0.0.1:1234 +qemu linux.img -net nic,macaddr=52:54:00:12:34:57 \ + -net socket,mcast=230.0.0.1:1234 # launch yet another QEMU instance on same "bus" -qemu linux.img -net nic,macaddr=52:54:00:12:34:58 -net socket,mcast=230.0.0.1:1234 +qemu linux.img -net nic,macaddr=52:54:00:12:34:58 \ + -net socket,mcast=230.0.0.1:1234 @end example Example (User Mode Linux compat.): @example -# launch QEMU instance (note mcast address selected is UML's default) -qemu linux.img -net nic,macaddr=52:54:00:12:34:56 -net socket,mcast=239.192.168.1:1102 +# launch QEMU instance (note mcast address selected +# is UML's default) +qemu linux.img -net nic,macaddr=52:54:00:12:34:56 \ + -net socket,mcast=239.192.168.1:1102 # launch UML /path/to/linux ubd0=/path/to/root_fs eth0=mcast @end example
@@ -464,7 +529,7 @@ non graphical mode. @item -s -Wait gdb connection to port 1234 (@xref{gdb_usage}). +Wait gdb connection to port 1234 (@pxref{gdb_usage}). @item -p port Change gdb connection port. @item -S
@@ -487,6 +552,7 @@ @c man end +@node pcsys_keys @section Keys @c man begin OPTIONS
@@ -535,9 +601,6 @@ @ignore -@setfilename qemu -@settitle QEMU System Emulator - @c man begin SEEALSO The HTML documentation of QEMU for more precise information and Linux user mode emulator invocation.
@@ -549,8 +612,7 @@ @end ignore -@end ignore - +@node pcsys_monitor @section QEMU Monitor The QEMU monitor is used to give complex commands to the QEMU
@@ -676,7 +738,7 @@ @item Dump 80 16 bit values at the start of the video memory. -@example +@smallexample (qemu) xp/80hx 0xb8000 0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42 0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41
@@ -688,7 +750,7 @@ 0x000b8070: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x000b8080: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x000b8090: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 -@end example +@end smallexample @end itemize @item p or print/fmt expr
@@ -739,6 +801,14 @@ growable disk images (their size increase as non empty sectors are written), compressed and encrypted disk images. +@menu +* disk_images_quickstart:: Quick start for disk image creation +* disk_images_snapshot_mode:: Snapshot mode +* qemu_img_invocation:: qemu-img Invocation +* disk_images_fat_images:: Virtual FAT disk images +@end menu + +@node disk_images_quickstart @subsection Quick start for disk image creation You can create a disk image with the command:
@@ -749,8 +819,9 @@ size in kilobytes. You can add an @code{M} suffix to give the size in megabytes and a @code{G} suffix for gigabytes. -@xref{qemu_img_invocation} for more information. +See @ref{qemu_img_invocation} for more information. +@node disk_images_snapshot_mode @subsection Snapshot mode If you use the option @option{-snapshot}, all disk images are
@@ -764,6 +835,7 @@ @include qemu-img.texi +@node disk_images_fat_images @subsection Virtual FAT disk images QEMU can automatically create a virtual FAT disk image from a
@@ -798,6 +870,7 @@ @item write to the FAT directory on the host system while accessing it with the guest system. @end itemize +@node pcsys_network @section Network emulation QEMU can simulate several networks cards (NE2000 boards on the PC
@@ -901,10 +974,10 @@ @item Launch @code{qemu.sh}. You should have the following output: -@example +@smallexample > ./qemu.sh Connected to host network interface: tun0 -Linux version 2.4.21 (bellard@@voyager.localdomain) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #5 Tue Nov 11 18:18:53 CET 2003 +Linux version 2.4.21 (bellard@@voyager.localdomain) (gcc version 3.2.2 20030222 @/(Red Hat @/Linux 3.2.2-5)) #5 Tue Nov 11 18:18:53 CET 2003 BIOS-provided physical RAM map: BIOS-e801: 0000000000000000 - 000000000009f000 (usable) BIOS-e801: 0000000000100000 - 0000000002000000 (usable)
@@ -913,7 +986,7 @@ zone(0): 4096 pages. zone(1): 4096 pages. zone(2): 0 pages. -Kernel command line: root=/dev/hda sb=0x220,5,1,5 ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe console=ttyS0 +Kernel command line: root=/dev/hda sb=0x220,5,1,5 ide2=noprobe ide3=noprobe ide4=noprobe @/ide5=noprobe console=ttyS0 ide_setup: ide2=noprobe ide_setup: ide3=noprobe ide_setup: ide4=noprobe
@@ -922,7 +995,7 @@ Detected 2399.621 MHz processor. Console: colour EGA 80x25 Calibrating delay loop... 4744.80 BogoMIPS -Memory: 28872k/32768k available (1210k kernel code, 3508k reserved, 266k data, 64k init, 0k highmem) +Memory: 28872k/32768k available (1210k kernel code, 3508k reserved, 266k data, 64k init, @/0k highmem) Dentry cache hash table entries: 4096 (order: 3, 32768 bytes) Inode cache hash table entries: 2048 (order: 2, 16384 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes)
@@ -964,14 +1037,14 @@ VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 64k freed -Linux version 2.4.21 (bellard@@voyager.localdomain) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #5 Tue Nov 11 18:18:53 CET 2003 +Linux version 2.4.21 (bellard@@voyager.localdomain) (gcc version 3.2.2 20030222 @/(Red Hat @/Linux 3.2.2-5)) #5 Tue Nov 11 18:18:53 CET 2003 QEMU Linux test distribution (based on Redhat 9) Type 'exit' to halt the system sh-2.05b# -@end example +@end smallexample @item Then you can play with the kernel inside the virtual serial console. You
@@ -1021,6 +1094,7 @@ @end enumerate +@node pcsys_usb @section USB emulation QEMU emulates a PCI UHCI USB controller and a 8 port USB hub connected
@@ -1104,7 +1178,8 @@ In order to use gdb, launch qemu with the '-s' option. It will wait for a gdb connection: @example -> qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda" +> qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img \ + -append "root=/dev/hda" Connected to host network interface: tun0 Waiting gdb connection on port 1234 @end example
@@ -1136,6 +1211,7 @@ @code{x/10i $cs*16+*eip} to dump the code at the PC position. @end enumerate +@node pcsys_os_specific @section Target OS specific information @subsection Linux
@@ -1222,12 +1298,22 @@ from @url{http://www.vmware.com/software/dosidle210.zip} to solve this problem. +@node QEMU System emulator for non PC targets @chapter QEMU System emulator for non PC targets QEMU is a generic emulator and it emulates many non PC machines. Most of the options are similar to the PC emulator. The differences are mentionned in the following sections. +@menu +* QEMU PowerPC System emulator:: +* Sparc32 System emulator invocation:: +* Sparc64 System emulator invocation:: +* MIPS System emulator invocation:: +* ARM System emulator invocation:: +@end menu + +@node QEMU PowerPC System emulator @section QEMU PowerPC System emulator Use the executable @file{qemu-system-ppc} to simulate a complete PREP
@@ -1292,6 +1378,7 @@ More information is available at @url{http://perso.magic.fr/l_indien/qemu-ppc/}. +@node Sparc32 System emulator invocation @section Sparc32 System emulator invocation Use the executable @file{qemu-system-sparc} to simulate a JavaStation
@@ -1320,7 +1407,7 @@ The number of peripherals is fixed in the architecture. QEMU uses the Proll, a PROM replacement available at -@url{http://people.redhat.com/zaitcev/linux/}. The required +@url{http://people.redhat.com/@/zaitcev/linux/}. The required QEMU-specific patches are included with the sources. A sample Linux 2.6 series kernel and ram disk image are available on
@@ -1341,6 +1428,7 @@ @c man end +@node Sparc64 System emulator invocation @section Sparc64 System emulator invocation Use the executable @file{qemu-system-sparc64} to simulate a Sun4u machine.
@@ -1359,6 +1447,7 @@ PC-compatible serial ports @end itemize +@node MIPS System emulator invocation @section MIPS System emulator invocation Use the executable @file{qemu-system-mips} to simulate a MIPS machine.
@@ -1376,6 +1465,7 @@ More information is available in the QEMU mailing-list archive. +@node ARM System emulator invocation @section ARM System emulator invocation Use the executable @file{qemu-system-arm} to simulate a ARM
@@ -1394,8 +1484,16 @@ A Linux 2.6 test image is available on the QEMU web site. More information is available in the QEMU mailing-list archive. +@node QEMU Linux User space emulator @chapter QEMU Linux User space emulator +@menu +* Quick Start:: +* Wine launch:: +* Command line options:: +@end menu + +@node Quick Start @section Quick Start In order to launch a Linux process, QEMU needs the process executable
@@ -1439,11 +1537,13 @@ @item The x86 version of QEMU is also included. You can try weird things such as: @example -qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 /usr/local/qemu-i386/bin/ls-i386 +qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 \ + /usr/local/qemu-i386/bin/ls-i386 @end example @end itemize +@node Wine launch @section Wine launch @itemize
@@ -1460,17 +1560,19 @@ (@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page). @item Configure Wine on your account. Look at the provided script -@file{/usr/local/qemu-i386/bin/wine-conf.sh}. Your previous +@file{/usr/local/qemu-i386/@/bin/wine-conf.sh}. Your previous @code{$@{HOME@}/.wine} directory is saved to @code{$@{HOME@}/.wine.org}. @item Then you can try the example @file{putty.exe}: @example -qemu-i386 /usr/local/qemu-i386/wine/bin/wine /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe +qemu-i386 /usr/local/qemu-i386/wine/bin/wine \ + /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe @end example @end itemize +@node Command line options @section Command line options @example
@@ -1498,6 +1600,14 @@ @node compilation @chapter Compilation from the sources +@menu +* Linux/Unix:: +* Windows:: +* Cross compilation for Windows with Linux:: +* Mac OS X:: +@end menu + +@node Linux/Unix @section Linux/Unix @subsection Compilation
@@ -1555,6 +1665,7 @@ variables. You must use gcc 3.x on PowerPC. @end example +@node Windows @section Windows @itemize
@@ -1564,7 +1675,7 @@ @item Download the MinGW development library of SDL 1.2.x -(@file{SDL-devel-1.2.x-mingw32.tar.gz}) from +(@file{SDL-devel-1.2.x-@/mingw32.tar.gz}) from @url{http://www.libsdl.org}. Unpack it in a temporary place, and unpack the archive @file{i386-mingw32msvc.tar.gz} in the MinGW tool directory. Edit the @file{sdl-config} script so that it gives the
@@ -1584,6 +1695,7 @@ @end itemize +@node Cross compilation for Windows with Linux @section Cross compilation for Windows with Linux @itemize
@@ -1615,9 +1727,15 @@ Note: Currently, Wine does not seem able to launch QEMU for Win32. +@node Mac OS X @section Mac OS X The Mac OS X patches are not fully merged in QEMU, so you should look at the QEMU mailing list archive to have all the necessary information. +@node Index +@chapter Index +@printindex cp + +@bye
Index: qemu-tech.texi
===================================================================
RCS file: /sources/qemu/qemu/qemu-tech.texi,v
retrieving revision 1.8
qemu-tech.texi +82 -4
245 lines not on this page · raw message
Index: Makefile
===================================================================
RCS file: /sources/qemu/qemu/Makefile,v
retrieving revision 1.97
Makefile +6 -0
@@ -85,6 +85,12 @@ %.html: %.texi texi2html -monolithic -number $< +%.info: %.texi + makeinfo $< -o $@ + +%.dvi: %.texi + texi2dvi $< + qemu.1: qemu-doc.texi $(SRC_PATH)/texi2pod.pl $< qemu.pod pod2man --section=1 --center=" " --release=" " qemu.pod > $@
Quoted 4 lines · Johannes Schindelin
Hi,
On Sat, 29 Apr 2006, Anthony Liguori wrote:
Quoted 8 lines
Quoted 5 lines
One thing you may notice is that RealVNC has some issues with being disconnected. This is because it likes to switch from 8bit to 32bit depths automatically at startup. Unfortunately, there is a race condition in the VNC protocol and since this implementation is asynchronous, we seem to be much more prone to exposing this.
This, along with other problems, has been solved with LibVNCServer. But of course, you are welcome to solve them again.
I have noticed that interactive performance with the current libvncserver based patches is quite bad compared to doing the same thing on SDL. Maybe re-implementing vnc will uncover why it is slow.
Quoted 21 lines
Where 1 is the first display (port 5901). This syntax may change in the near future to support binding to a particular interface. It's very useful to use an absolute mouse with VNC as the relative support is quite poor. It may be useful to adapt the libvncserver patch's calibration code here but I've not attempted to do that yet.
This patch is still experimental. I've tested it with RealVNC and TightVNC under a variety of depths but I won't be suprised if there are still problems. I only implement Raw, CopyRect, and Hextile encodings too. Any sort of palette color mode or pixel format that QEMU doesn't support will not work either.
One thing you may notice is that RealVNC has some issues with being disconnected. This is because it likes to switch from 8bit to 32bit depths automatically at startup. Unfortunately, there is a race condition in the VNC protocol and since this implementation is asynchronous, we seem to be much more prone to exposing this.
A short near-term TODO list is:
Quoted 7 lines
1) More testing
2) Support switching between monitor/serial
3) Support a better encoding (like TightEncoding or ZRLE)
4) Support a vnc password (and perhaps stuff like TLS)Any feedback is greatly appreciated (especially with how it works with clients I've not tested).
realvnc on debian-ppc (xvncviewer-3.3.7) has endian issues (the colors are wrong). However, mouse tracking and dragging windows actually *works*. (This is with the version currently in cvs)
Quoted 4 lines · Anthony Liguori
Hi,
The attach patch adds VNC display support for QEMU. It does not use libvncserver but was rather written from scratch. libvncserver is a really neat project and I've used it in a number of other projects but I think QEMU really requires a custom implementation.
Nice job.. Improves VNC interactivity nicely..
I use xtightvncviewer with the -bgr option to cut down network bandwidth quite a bit. This generates funky colours with the current patch but works with the old implementation.
I'll take a look when I get the chance..
Also I can't access the monitor (which I can with the other vnc patch) ... again, when I get a chance.
I need to look at the protocol and see if there is a way to instruct the client to change its size on the fly also.. at the moment booting win2k I have three different client sizes and need to close/reopen the client for each change.
Nice work. The optimisations to the qemu portion speed up the display refreshes significantly.
Brad
Signature · 3 lines
"Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams
Quoted 1 line · Brad Campbell
Also I can't access the monitor (which I can with the other vnc patch) ... again, when I get a chance.
Oh how I wish I'd read the todo carefully.. <thumps head on desk>
Signature · 3 lines
"Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams
Hi,
Quoted 4 lines · Brad Campbell
I need to look at the protocol and see if there is a way to instruct the client to change its size on the fly also.. at the moment booting win2k I have three different client sizes and need to close/reopen the client for each change.
rfbEncodingNewFBSize. You can find example code in the current CVS of LibVNCServer.
Hth,
Dscho