I can confirm problems with --std-vga. I had 4 running win xp sp3 guest with --std-vga (KVM-75). Now, after upgrading to KVM-76 the screen goes black, just before the "welcome" and hangs.
Im using a 2.6.24 kernel (Debian 64) Best Regards, Martin Maurer [EMAIL PROTECTED] http://www.proxmox.com > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Michael Malone > Sent: Sonntag, 28. September 2008 23:45 > To: kvm mailing list > Subject: kvm-76 --std-vga problem > > Hi Everyone, > > I just downloaded and ran the new kvm-76 (upgrading from kvm-74) and I > have a few issues. > I am running Ubuntu 8.04 (Hardy) as my host and Windows XP as my guest. > I am using VT-d and the kernel modules loaded correctly. > > Here is the command I use to start kvm: > kvm-bridge -hda windows2.img -boot c -m 1000 -serial /dev/ttyUSB0 > -serial file:serial.out -smp 2 -usb -usbdevice "tablet" -full-screen > -cdrom /dev/cdrom > > kvm-bridge is a script that configures my network and passes the other > options straight through to qemu-system-x86_64 > > 1) what is the difference between running qemu-system-x86_64 and kvm > directly? > Because, when I run kvm directly, I get this error: > Traceback (most recent call last): > File "/home/malonem/kvm-76/kvm", line 20, in <module> > external_module = config.get('shell', 'want_module') > File "/usr/lib/python2.5/ConfigParser.py", line 511, in get > raise NoSectionError(section) > ConfigParser.NoSectionError: No section: 'shell' > > 2) (this has been around for quite some time, I just haven't done > anything about it) > Even though I start up with -smp 2, windows only reads 1 cpu > > 3) When I run it using the --std-vga parameter, windows boots to just > before it gets to the "welcome" screen and hangs. The output shows a > multitude of "kvm: get_dirty_pages returned -2" Is this something to do > with the kernel version I am using? I am using the standard Ubuntu > Hardy Kernel 2.6.24-19-generic. I read the release notes about the > kernel version with kvm-76 but didn't really understand them and > presumed that I am using the kernel modules supplied with kvm. (I > rmmod'd kvm-intel and kvm before I compiled and installed, then > modprobe'd the modules afterwards and everything seemed to go ok) > > Any help or insight would be much appreciated, > > Michael > > ======================================================================= > This email, including any attachments, is only for the intended > addressee. It is subject to copyright, is confidential and may be > the subject of legal or other privilege, none of which is waived or > lost by reason of this transmission. > If the receiver is not the intended addressee, please accept our > apologies, notify us by return, delete all copies and perform no > other act on the email. > Unfortunately, we cannot warrant that the email has not been > altered or corrupted during transmission. > ======================================================================= > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
