From: Michael Malone <michael.malone@tait.co.nz>
To: kvm mailing list <kvm@vger.kernel.org>
Subject: kvm-76 --std-vga problem
Date: Mon, 29 Sep 2008 10:44:30 +1300 [thread overview]
Message-ID: <48DFFABE.8060304@tait.co.nz> (raw)
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.
=======================================================================
next reply other threads:[~2008-09-28 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 21:44 Michael Malone [this message]
2008-09-29 12:37 ` kvm-76 --std-vga problem Martin Maurer
2008-09-29 12:50 ` Brian Jackson
2008-09-29 17:29 ` Glauber Costa
2008-09-29 18:08 ` Glauber Costa
2008-10-01 7:47 ` Avi Kivity
2008-10-01 19:52 ` Michael Malone
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 0:52 duck
2008-10-06 7:35 ` Niels Berglund
2008-10-06 16:16 ` Glauber Costa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48DFFABE.8060304@tait.co.nz \
--to=michael.malone@tait.co.nz \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.