the behaviour as follows:
* deny switching to fullscreen mode if the resolution is too high and
print a message to the console
* use windowed mode as fallback option if we are already in
fullscreen mode and the new resolution is too high and print a message
to the console
Signed-off-by: Andreas
hi,
I'm sorry for messing up the last patch, I shouldn't work that late...
I added the changes to pc.h (VGA_RAM_SIZE) and split up the patch in a
qemu part and a vgabios part.
cheers,
Andi
--- kvm-61.orig/qemu/hw/vga_int.h 2008-02-19 15:58:28.0 +0100
+++ kvm-61/qemu/hw/vga_int.h
hi,
@Arne: Could you please test the patch with your setup? I hope it works
this time...
Yesno. It does (at least kvm does not crash), but it shows the same
dialog problems as reported by Leslie:
I'm quite sure that this issue isn't related to the widescreen fixes.
This visual bug seems to
hi,
the attached patch fixes the screen corruption issues which were
reported by others, see:
http://article.gmane.org/gmane.comp.emulators.kvm.devel/13543
http://article.gmane.org/gmane.comp.emulators.kvm.devel/13409
The bug is kvm specific and can only be observed in graphics mode using
hi,
What about VGA_RAM_SIZE in qemu/hw/pc.h?
I already tried changing the VGA_RAM_SIZE value in pc.h to 16 * 1024 *
1024 (16MB), but then kvm crashes when the guest os switches to graphics
mode.
Changing VGA_RAM_SIZE in pc.h to 16MB works when I use the latest cvs
snapshot of qemu (didn't
hi,
Most likely it only works with Linux; it was probably written by
reverse-engineering the Linux driver.
actually -vmwarevga works for me when using pure qemu (latest cvs
snapshot) without kqemu (-no-kqemu), but it does not work with kvm when
using -no-kvm.
anyway, I was testing
hi,
D'oh. Must have missed it. :\ Thanks! Unfortunately, it still does not work.
Qemu crashes now as windows switches to graphics mode. Safe mode does not
work either..
For now I'd suggest trying the following:
* download the latest qemu cvs snapshot
cvs -z3 -d:pserver:[EMAIL
hi,
* copy the modified vgabios.bin to the qemu dir
wget http://www.wina.at/vgabios.bin
# cp vgabios.bin /usr/local/qemu-cvs/share/qemu (as root; change to
target path according to the prefix you used above)
I'm guess I've uploaded to wrong vgabios.bin, so if you don't want to compile it
hi,
I found out what crashed kvm when I increased VGA_RAM_SIZE in pc.h. The
crash was caused by a really _dirty_ hack in a kvm specific part of
vga.c (it took me at least an hour to find this amazing piece of code...
at least the HACK ALERT was a good hint ;-) ).
I've attached the patch. It
hi,
I managed to get kvm-61 working at a resolution of 1680x1050 (using -std-vga;
windowed as well as fullscreen) with windows xp as guest os.
Basically I took the following steps:
* increase vga memory from 8MB to 16MB (in vbetables-gen.c)
* add modes to vbetables-gen.c
* change
hi,
the attached patch fixes the issues with widescreen resolutions for me
when using -std-vga.
in vgabios/vbetables-gen.c I changed the video memory from 8MB to 16MB
which is sufficient for resolutions up to 2560x1600. I've also added
some more video modes (up to 2560x1600) with 16, 24,
hi,
After that, I called make which correctly updated vbemodes.h and
compiled the bios. I then copied the bios to /usr/share/kvm
and /usr/share/qemu.
well, I think it is very unlikely that the vgabios is located at /usr/share/kvm
or so. if you are unsure do a locate vgabios.bin. I've
hi,
When moving my mouse slowly upwards the lowest black pixels are not erased.
The attached screenshot shows the effect.
I've also seen this effect on kvm-61 but it is new for me, I didn't see it on
older kvm versions.
I tracked it down a litte bit further:
* I don't see this effect at all
hi,
is there a specific reason why the 1280x960 resolutions have two mode
numbers (one being an exact duplicate of the other) in vbetables-gen.c
(0x180 = 0x182, 0x181 = 0x183, see below)?
...
{ 1280, 960, 24 , 0x180},
{ 1280, 960, 32 , 0x181},
{ 1280,
hi,
I contacted the author of the VBEMP driver. He wrote me that there exist
several methods of requesting the available modes from the BIOS.
Apparently, by adding a mode to the vbetables-gen.c it's only added to
parts of the tables and not to all of them, which is incorrect. By only
using
hi,
I tried using the -vmwarevga switch but I didn't succeed. I've tested it
with kvm-snapshot-20080218, kvm-60 and kvm-61.
as soon as the VM (guest os is windows xp) switches from text mode to
graphics mode lots of messages kvm: get_dirty_pages returned -2 scroll
by on the console. after a
16 matches
Mail list logo