[Qemu-devel] invisible wall patch

2006-06-13 Thread Julian Seward

Could somebody please commit, or at least consider committing, 
Anthony Liguori's invisible wall patch, shown at 
http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00112.html ?

Without it, QEMU is essentially unusable on my SuSE 10 host; with it,
the mouse stuff works perfectly.  A couple of other people on that
thread had similar experiences with it.

J


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] invisible wall patch

2006-06-13 Thread Michael McConnell

Julian Seward wrote:
Could somebody please commit, or at least consider committing, 
Anthony Liguori's invisible wall patch, shown at 
http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00112.html ?


Without it, QEMU is essentially unusable on my SuSE 10 host; with it,
the mouse stuff works perfectly.  A couple of other people on that
thread had similar experiences with it.


I'll add my voice to this - with WinXP and Win2000 guests, without this 
patch they were virtually unusable.  They work fine with it.


--
-- Michael Soruk McConnell
   Eridani Star System

   MailStripper - http://www.MailStripper.eu/
   Mail Me Anywhere - http://www.mailmeanywhere.com/


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] Problem in compiling kqemu-1.3 .0pre7: kqemu-linux.c:52: error: expe cted ‘)’ before string constant

2006-06-13 Thread נדב ויניק
Title: Problem in compiling kqemu-1.3.0pre7: kqemu-linux.c:52: error: expected ‘)’ before string constant






Hello

I have problem to compile kqemu-1.3.0pre7:

kqemu-linux.c:52: error: expected ‘)’ before string constant

Thanks for your help
Nadav





___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] qemu sdl.c

2006-06-13 Thread Fabrice Bellard
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard bellard   06/06/13 12:03:53

Modified files:
.  : sdl.c 

Log message:
avoid stopping QEMU when switching desktops with Ctrl-Alt-x

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/sdl.c?cvsroot=qemur1=1.28r2=1.29

Patches:
Index: sdl.c
===
RCS file: /sources/qemu/qemu/sdl.c,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- sdl.c   13 Jun 2006 10:49:12 -  1.28
+++ sdl.c   13 Jun 2006 12:03:53 -  1.29
@@ -447,10 +447,18 @@
 gui_key_modifier_pressed = 0;
 if (gui_keysym == 0) {
 /* exit/enter grab if pressing Ctrl-Alt */
-if (!gui_grab)
+if (!gui_grab) {
+/* if the application is not active,
+   do not try to enter grab state. It
+   prevents
+   'SDL_WM_GrabInput(SDL_GRAB_ON)'
+   from blocking all the application
+   (SDL bug). */
+if (SDL_GetAppState()  SDL_APPACTIVE)
 sdl_grab_start();
-else
+} else {
 sdl_grab_end();
+}
 /* SDL does not send back all the
modifiers key, so we must correct it */
 reset_keys();


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] Mouse gets stuck w/ qemu-0.8.1 running Windows2000/XP

2006-06-13 Thread Agustin Barto

I'm running WindowsXP (the problem is also present with Windows2000)
on qemu-0.8.1 over an FC5 host, and sometimes the mouse gets stuck at
some point (kinda like hitting a screen edge) and I have to wiggle
the mouse a bit to pass over this limit.

I didn't have this problem with qemu-0.7.x and prior versions.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] Mouse gets stuck w/ qemu-0.8.1 running Windows2000/XP

2006-06-13 Thread Johannes Schindelin
Hi,

On Tue, 13 Jun 2006, Agustin Barto wrote:

 I'm running WindowsXP (the problem is also present with Windows2000)
 on qemu-0.8.1 over an FC5 host, and sometimes the mouse gets stuck at
 some point (kinda like hitting a screen edge) and I have to wiggle
 the mouse a bit to pass over this limit.
 
 I didn't have this problem with qemu-0.7.x and prior versions.

Funny. It seems that there have been quite a few messages on this list, 
which address exactly your problem. The latest such message was even only 
a few minutes ago.

Ciao,
Dscho



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] invisible wall patch

2006-06-13 Thread Anthony Liguori

Eric Hameleers wrote:

Julian Seward wrote:
  
Also, VNC

functionality is still basically where it was when it was added to
QEMU - which is barely above useable status.


What functionality are you referring to?

Regards,

Anthony Liguori


 I liked the functionality
offered by the libvncserver patch better but can no longer apply that.
Is someone going to take up adding the missing pieces to VNC
functionality? The suggested patch in
http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00142.html
might help here, too.

Eric

  




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] Support Questions

2006-06-13 Thread Joe Lee
I came across a product called Iemulator and think it based on QEMU. If 
so, I wanted to know how possible is it to re-brand qemu to something 
similar to Iemulator.


Also, I am quite new to QEMU and virtualization in general and wanted to 
know the difference between QEMU and product like OpenVZ. Based on my 
reading on them I think they are quite different. I suppose QEMU is more 
like VMware aimed at end users and OpenVZ would be more for Enterprise 
servers.


Joe



Natalia Portillo wrote:

Well,

Fabrice Bellard is main developer, and KQEMU whole developer.
Paul Brook maintains ARM system, and QVM86 whole developer.
Jocelyn Mayer (away) maintains PPC system.
Blue Swirl maintains Sparc system.
A couple of collaborators do development taks.
I maintain the OS compatibility list and do extensive operating system 
compatibility testing.


Just, for what you want that information?

El 12/06/2006, a las 20:32, Joe Lee escribió:

Wanted to know about individuals that provides support and custom 
development for QEUM.




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel







___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] MIPS emulation?

2006-06-13 Thread Alessandro Corradi
On Sat, Jan 14, 2006 at 07:34:36PM +0100, Tomasz Chmielewski wrote: (A) You have to build a qemu-specific kernel to use the MIPS QEMU.  And how to build qemu-specific MIPS kernel?
  Is it just a kernel built for MIPS, or perhaps some qemu-specific  patches have to be applied?You have to select QEMU as your machine type when you configure the
kernel.  Use the linux-mips.org CVS, of course.. (B) I have no idea if that method works with MIPS qemu; I only tested -kernel.
  Hmm?  I didn't quite understand what you mean.I've never used -cdrom or -boot.-- Daniel Jacobowitz
CodeSourceryHi,I downloaded mips/linux kernel from git and I configure it for qemu. But when I make it gets this error:/bin/sh: line 1: mips-linux-gcc: command not foundWhat's wrong?
ThanksAle
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] Support Questions

2006-06-13 Thread Johannes Schindelin
Hi,

On Tue, 13 Jun 2006, Joe Lee wrote:

 I came across a product called Iemulator and think it based on QEMU. If 
 so, I wanted to know how possible is it to re-brand qemu to something 
 similar to Iemulator.

It is based on QEmu. See http://www.iemulator.com/iemulator_faq.php, Is 
iEmulator based on the BOCHS emulator?. It is perfectly legal. The core 
of QEmu is licensed under the LGPL, and accordingly, (at least 
some) sources of iEmulator are freely downloadable.

 Also, I am quite new to QEMU and virtualization in general and wanted to 
 know the difference between QEMU and product like OpenVZ.

OpenVZ is a virtualiser, i.e. it uses the hardware -- including the CPU -- 
of the host, and relies on the OS to handle the sharing parts. Therefore, 
you can not run unmodified kernels (or Windows for that matter) using 
OpenVZ.

QEmu is a system emulator, i.e. the hardware componentes are emulated. As 
for the CPU, QEmu uses a technique called translation or Just-In-Time 
compilation in order to execute the code. If the host CPU is of the same 
type as the emulated CPU, you can use KQEmu or QVEmu to kind-of virtualise 
the CPU instead.

 I suppose QEMU is more like VMware aimed at end users and OpenVZ would 
 be more for Enterprise servers.

Correct. The principal application for QEmu is to run a different OS in 
a window on your desktop. The principal application for OpenVZ or Zen is 
to run many virtual computers (servers) on one host.

Hth,
Dscho



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] MIPS emulation?

2006-06-13 Thread Thiemo Seufer
Alessandro Corradi wrote:
[snip]
 Hi,
 I downloaded mips/linux kernel from git and I configure it for qemu.
 But when I make it gets this error:
 
 
 /bin/sh: line 1: mips-linux-gcc: command not found
 
 What's wrong?

You are either compiling natively on a mips system and have CONFIG_CROSS
enabled, or you have no cross-compiler, or the cross-compiler has a
different name than the default.


Thiemo


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] qemu vnc.c

2006-06-13 Thread Fabrice Bellard
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard bellard   06/06/13 16:35:24

Modified files:
.  : vnc.c 

Log message:
support for higher resolutions

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/vnc.c?cvsroot=qemur1=1.6r2=1.7

Patches:
Index: vnc.c
===
RCS file: /sources/qemu/qemu/vnc.c,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- vnc.c   14 May 2006 18:11:49 -  1.6
+++ vnc.c   13 Jun 2006 16:35:24 -  1.7
@@ -50,6 +50,10 @@
 uint32_t *last_fg,
 int *has_bg, int *has_fg);
 
+#define VNC_MAX_WIDTH 2048
+#define VNC_MAX_HEIGHT 2048
+#define VNC_DIRTY_WORDS (VNC_MAX_WIDTH / (16 * 32))
+
 struct VncState
 {
 QEMUTimer *timer;
@@ -59,7 +63,7 @@
 int need_update;
 int width;
 int height;
-uint64_t dirty_row[768];
+uint32_t dirty_row[VNC_MAX_HEIGHT][VNC_DIRTY_WORDS];
 char *old_data;
 int depth; /* internal VNC frame buffer byte per pixel */
 int has_resize;
@@ -95,6 +99,47 @@
 static void vnc_update_client(void *opaque);
 static void vnc_client_read(void *opaque);
 
+static inline void vnc_set_bit(uint32_t *d, int k)
+{
+d[k  5] |= 1  (k  0x1f);
+}
+
+static inline void vnc_clear_bit(uint32_t *d, int k)
+{
+d[k  5] = ~(1  (k  0x1f));
+}
+
+static inline void vnc_set_bits(uint32_t *d, int n, int nb_words)
+{
+int j;
+
+j = 0;
+while (n = 32) {
+d[j++] = -1;
+n -= 32;
+}
+if (n  0) 
+d[j++] = (1  n) - 1;
+while (j  nb_words)
+d[j++] = 0;
+}
+
+static inline int vnc_get_bit(const uint32_t *d, int k)
+{
+return (d[k  5]  (k  0x1f))  1;
+}
+
+static inline int vnc_and_bits(const uint32_t *d1, const uint32_t *d2, 
+   int nb_words)
+{
+int i;
+for(i = 0; i  nb_words; i++) {
+if ((d1[i]  d2[i]) != 0)
+return 1;
+}
+return 0;
+}
+
 static void vnc_dpy_update(DisplayState *ds, int x, int y, int w, int h)
 {
 VncState *vs = ds-opaque;
@@ -104,7 +149,7 @@
 
 for (; y  h; y++)
for (i = 0; i  w; i += 16)
-   vs-dirty_row[y] |= (1ULL  ((x + i) / 16));
+   vnc_set_bit(vs-dirty_row[y], (x + i) / 16);
 }
 
 static void vnc_framebuffer_update(VncState *vs, int x, int y, int w, int h,
@@ -316,10 +361,10 @@
 
 for (h = 1; h  (vs-height - y); h++) {
int tmp_x;
-   if (!(vs-dirty_row[y + h]  (1ULL  last_x)))
+   if (!vnc_get_bit(vs-dirty_row[y + h], last_x))
break;
for (tmp_x = last_x; tmp_x  x; tmp_x++)
-   vs-dirty_row[y + h] = ~(1ULL  tmp_x);
+   vnc_clear_bit(vs-dirty_row[y + h], tmp_x);
 }
 
 return h;
@@ -333,15 +378,12 @@
int y;
char *row;
char *old_row;
-   uint64_t width_mask;
+   uint32_t width_mask[VNC_DIRTY_WORDS];
int n_rectangles;
int saved_offset;
int has_dirty = 0;
 
-   width_mask = (1ULL  (vs-width / 16)) - 1;
-
-   if (vs-width == 1024)
-   width_mask = ~(0ULL);
+vnc_set_bits(width_mask, (vs-width / 16), VNC_DIRTY_WORDS);
 
/* Walk through the dirty map and eliminate tiles that
   really aren't dirty */
@@ -349,7 +391,7 @@
old_row = vs-old_data;
 
for (y = 0; y  vs-height; y++) {
-   if (vs-dirty_row[y]  width_mask) {
+   if (vnc_and_bits(vs-dirty_row[y], width_mask, VNC_DIRTY_WORDS)) {
int x;
char *ptr, *old_ptr;
 
@@ -358,7 +400,7 @@
 
for (x = 0; x  vs-ds-width; x += 16) {
if (memcmp(old_ptr, ptr, 16 * vs-depth) == 0) {
-   vs-dirty_row[y] = ~(1ULL  (x / 16));
+   vnc_clear_bit(vs-dirty_row[y], (x / 16));
} else {
has_dirty = 1;
memcpy(old_ptr, ptr, 16 * vs-depth);
@@ -389,11 +431,11 @@
int x;
int last_x = -1;
for (x = 0; x  vs-width / 16; x++) {
-   if (vs-dirty_row[y]  (1ULL  x)) {
+   if (vnc_get_bit(vs-dirty_row[y], x)) {
if (last_x == -1) {
last_x = x;
}
-   vs-dirty_row[y] = ~(1ULL  x);
+   vnc_clear_bit(vs-dirty_row[y], x);
} else {
if (last_x != -1) {
int h = find_dirty_height(vs, y, last_x, x);
@@ -688,10 +730,8 @@
char *old_row = vs-old_data + y_position * vs-ds-linesize;
 
for (i = 0; i  h; i++) {
-   vs-dirty_row[y_position + i] = (1ULL  (vs-ds-width / 16)) - 1;
-   if (vs-ds-width == 1024) {
- vs-dirty_row[y_position + i] = ~(0ULL);
-   }
+vnc_set_bits(vs-dirty_row[y_position + i], 
+ 

[Qemu-devel] qemu/hw vga.c vga_int.h

2006-06-13 Thread Fabrice Bellard
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard bellard   06/06/13 16:37:40

Modified files:
hw : vga.c vga_int.h 

Log message:
support for Bochs VBE GETCAPS call so that -std-vga works again with 
new VGA BIOSes - added support for modes up to 1600x1200x32 in -std-vga case

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/vga.c?cvsroot=qemur1=1.43r2=1.44
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/vga_int.h?cvsroot=qemur1=1.6r2=1.7

Patches:
Index: vga.c
===
RCS file: /sources/qemu/qemu/hw/vga.c,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -b -r1.43 -r1.44
--- vga.c   10 May 2006 22:17:36 -  1.43
+++ vga.c   13 Jun 2006 16:37:40 -  1.44
@@ -378,10 +378,29 @@
 VGAState *s = opaque;
 uint32_t val;
 
-if (s-vbe_index = VBE_DISPI_INDEX_NB)
+if (s-vbe_index = VBE_DISPI_INDEX_NB) {
+if (s-vbe_regs[VBE_DISPI_INDEX_ENABLE]  VBE_DISPI_GETCAPS) {
+switch(s-vbe_index) {
+/* XXX: do not hardcode ? */
+case VBE_DISPI_INDEX_XRES:
+val = VBE_DISPI_MAX_XRES;
+break;
+case VBE_DISPI_INDEX_YRES:
+val = VBE_DISPI_MAX_YRES;
+break;
+case VBE_DISPI_INDEX_BPP:
+val = VBE_DISPI_MAX_BPP;
+break;
+default:
 val = s-vbe_regs[s-vbe_index];
-else
+break;
+}
+} else {
+val = s-vbe_regs[s-vbe_index]; 
+}
+} else {
 val = 0;
+}
 #ifdef DEBUG_BOCHS_VBE
 printf(VBE: read index=0x%x val=0x%x\n, s-vbe_index, val);
 #endif
@@ -434,7 +453,8 @@
 s-bank_offset = (val  16);
 break;
 case VBE_DISPI_INDEX_ENABLE:
-if (val  VBE_DISPI_ENABLED) {
+if ((val  VBE_DISPI_ENABLED) 
+!(s-vbe_regs[VBE_DISPI_INDEX_ENABLE]  VBE_DISPI_ENABLED)) {
 int h, shift_control;
 
 s-vbe_regs[VBE_DISPI_INDEX_VIRT_WIDTH] = 
@@ -464,7 +484,7 @@
 s-cr[0x13] = s-vbe_line_offset  3;
 /* width */
 s-cr[0x01] = (s-vbe_regs[VBE_DISPI_INDEX_XRES]  3) - 1;
-/* height */
+/* height (only meaningful if  1024) */
 h = s-vbe_regs[VBE_DISPI_INDEX_YRES] - 1;
 s-cr[0x12] = h;
 s-cr[0x07] = (s-cr[0x07]  ~0x42) | 
@@ -1310,11 +1330,19 @@
 {
 int width, height;
 
+#ifdef CONFIG_BOCHS_VBE
+if (s-vbe_regs[VBE_DISPI_INDEX_ENABLE]  VBE_DISPI_ENABLED) {
+width = s-vbe_regs[VBE_DISPI_INDEX_XRES];
+height = s-vbe_regs[VBE_DISPI_INDEX_YRES];
+} else 
+#endif
+{
 width = (s-cr[0x01] + 1) * 8;
 height = s-cr[0x12] | 
 ((s-cr[0x07]  0x02)  7) | 
 ((s-cr[0x07]  0x40)  3);
 height = (height + 1);
+}
 *pwidth = width;
 *pheight = height;
 }

Index: vga_int.h
===
RCS file: /sources/qemu/qemu/hw/vga_int.h,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- vga_int.h   3 Jul 2005 14:00:51 -   1.6
+++ vga_int.h   13 Jun 2006 16:37:40 -  1.7
@@ -30,8 +30,9 @@
 /* bochs VBE support */
 #define CONFIG_BOCHS_VBE
 
-#define VBE_DISPI_MAX_XRES  1024
-#define VBE_DISPI_MAX_YRES  768
+#define VBE_DISPI_MAX_XRES  1600
+#define VBE_DISPI_MAX_YRES  1200
+#define VBE_DISPI_MAX_BPP   32
 
 #define VBE_DISPI_INDEX_ID  0x0
 #define VBE_DISPI_INDEX_XRES0x1
@@ -51,6 +52,8 @@
   
 #define VBE_DISPI_DISABLED  0x00
 #define VBE_DISPI_ENABLED   0x01
+#define VBE_DISPI_GETCAPS   0x02
+#define VBE_DISPI_8BIT_DAC  0x20
 #define VBE_DISPI_LFB_ENABLED   0x40
 #define VBE_DISPI_NOCLEARMEM0x80
   
@@ -72,7 +75,7 @@
 #endif /* !CONFIG_BOCHS_VBE */
 
 #define CH_ATTR_SIZE (160 * 100)
-#define VGA_MAX_HEIGHT 1024
+#define VGA_MAX_HEIGHT 2048
 
 #define VGA_STATE_COMMON\
 uint8_t *vram_ptr;  \


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] qemu+SDL question..

2006-06-13 Thread Ishwar Rattan


On a new Linux system: (Kanotix-lite)

I compiled and installed SDL-1.2.10
  compiled and installed qemu-0.8.1

but invocation of qemu results in error message:

  Couldn't Initialize SDL -- exiting

any ideas?

-ishwar



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] Support Questions

2006-06-13 Thread Mike Kronenberg


On 13.06.2006, at 16:37, Joe Lee wrote:

I came across a product called Iemulator and think it based on  
QEMU. If so, I wanted to know how possible is it to re-brand qemu  
to something similar to Iemulator.


IEmulator (as of the 1.7.x series) is a rebrand of a early stage  
project Q Build (http://www.kju-app.org/proj/) which is based on QEMU  
itself. Q has different graphic output and some frontend extensions  
compared to QEMU. We tried to port the natural virtualization modul  
qvm86 to OS X, too. But as QEMU has moved on, we have put a hold on  
that. So QEMU on OS X (ppc and intel) remains a simulation.


Mike



Also, I am quite new to QEMU and virtualization in general and  
wanted to know the difference between QEMU and product like OpenVZ.  
Based on my reading on them I think they are quite different. I  
suppose QEMU is more like VMware aimed at end users and OpenVZ  
would be more for Enterprise servers.


Joe



Natalia Portillo wrote:

Well,

Fabrice Bellard is main developer, and KQEMU whole developer.
Paul Brook maintains ARM system, and QVM86 whole developer.
Jocelyn Mayer (away) maintains PPC system.
Blue Swirl maintains Sparc system.
A couple of collaborators do development taks.
I maintain the OS compatibility list and do extensive operating  
system compatibility testing.


Just, for what you want that information?

El 12/06/2006, a las 20:32, Joe Lee escribió:

Wanted to know about individuals that provides support and custom  
development for QEUM.




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel







___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] Support Questions

2006-06-13 Thread Joe Lee
I am looking for a good GUI for QEMU. Below are the one I've found about 
so far. Does anyone know of any other good GUI

that would be similar to VMware?

http://sourceforge.net/projects/kqemu/
http://emeitner.f2o.org/qemu_launcher

Mike Kronenberg wrote:


On 13.06.2006, at 16:37, Joe Lee wrote:

I came across a product called Iemulator and think it based on QEMU. 
If so, I wanted to know how possible is it to re-brand qemu to 
something similar to Iemulator.


IEmulator (as of the 1.7.x series) is a rebrand of a early stage 
project Q Build (http://www.kju-app.org/proj/) which is based on QEMU 
itself. Q has different graphic output and some frontend extensions 
compared to QEMU. We tried to port the natural virtualization modul 
qvm86 to OS X, too. But as QEMU has moved on, we have put a hold on 
that. So QEMU on OS X (ppc and intel) remains a simulation.


Mike



Also, I am quite new to QEMU and virtualization in general and wanted 
to know the difference between QEMU and product like OpenVZ. Based on 
my reading on them I think they are quite different. I suppose QEMU 
is more like VMware aimed at end users and OpenVZ would be more for 
Enterprise servers.


Joe



Natalia Portillo wrote:

Well,

Fabrice Bellard is main developer, and KQEMU whole developer.
Paul Brook maintains ARM system, and QVM86 whole developer.
Jocelyn Mayer (away) maintains PPC system.
Blue Swirl maintains Sparc system.
A couple of collaborators do development taks.
I maintain the OS compatibility list and do extensive operating 
system compatibility testing.


Just, for what you want that information?

El 12/06/2006, a las 20:32, Joe Lee escribió:

Wanted to know about individuals that provides support and custom 
development for QEUM.




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel







___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel






___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] High resolution VGA modes

2006-06-13 Thread Fabrice Bellard

Hi,

The previous commits enable the support of higher resolution VGA modes 
in QEMU (1152x864, 1280x1024 and 1600x1200) when using the VESA device 
driver (-std-vga option). The VESA device driver is known to work with 
Linux and Windows XP.


The VGA memory was increased to 8 MB to enable 1600x1200 with 32 bits 
per pixel. I updated the built-in VNC server so that it supports higher 
resolutions too.


Note that the Cirrus VGA device driver was not modified, so it has the 
same limitations are before (4 MB Video Memory, up to 1280x1024). These 
limitations are unfortunately linked to the emulated Cirrus VGA hardware 
and guest OS video drivers.


Fabrice.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] High resolution VGA modes

2006-06-13 Thread Anthony Liguori

Fabrice Bellard wrote:

Hi,

The previous commits enable the support of higher resolution VGA modes 
in QEMU (1152x864, 1280x1024 and 1600x1200) when using the VESA device 
driver (-std-vga option). The VESA device driver is known to work with 
Linux and Windows XP.


Is 2d acceleration possible with VESA?

Regards,

Anthony Liguori

The VGA memory was increased to 8 MB to enable 1600x1200 with 32 bits 
per pixel. I updated the built-in VNC server so that it supports 
higher resolutions too.


Note that the Cirrus VGA device driver was not modified, so it has the 
same limitations are before (4 MB Video Memory, up to 1280x1024). 
These limitations are unfortunately linked to the emulated Cirrus VGA 
hardware and guest OS video drivers.


Fabrice.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel