public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Milan Plzik <milan.plzik@gmail.com>
To: kvm@vger.kernel.org
Subject: Differences in emulation between kvm and kvm -no-kvm
Date: Tue, 07 Apr 2009 21:59:19 +0200	[thread overview]
Message-ID: <1239134359.8519.2111.camel@localhost> (raw)

  Hello,

  I somehow managed to produce code which behaves slightly differently
when using software emulation and when using kvm. As fas as I know, the
bug should be related to reading cursor position from VGA registers.

  Basically, the bug should be reproducible by executing:

	#define VGA_CURSOR_LOC_HIGH 0xe
	#define VGA_CURSOR_LOC_LOW  0xf

	priv.addr = 0x3d4;
	priv.data = 0x3d5;

	outb (priv.addr, VGA_CURSOR_LOC_HIGH);	/* Cursor location high */
	priv.cursor = inb (priv.data) << 8;

	outb (priv.addr, VGA_CURSOR_LOC_LOW); /* Cursor location low */
	priv.cursor += inb (priv.data);

  I put a testcase at
http://stashbox.org/manage_file/480477/kvm-bug.tar.gz . It's my school
project, so it's a bit more complicated; if neccessary, I can supply the
sources. In kvm -no-kvm it should cause reboot, in plain kvm it should
print few colored 'A's into the left upper corner of the screen (rest of
the code in binary is unreachable). It uses a bit more complicated setup
-- pxegrub2 and tftp loading, but that should not matter -- run.sh
should execute kvm with proper arguments, when executed from the kvm-bug
directory.

  Best regards,
	Milan

P.S:  Please Cc: me as I'm not subscribed to the list; when possible,
I'll be also idling at #kvm (nickname 'mmp').


             reply	other threads:[~2009-04-07 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 19:59 Milan Plzik [this message]
2009-04-07 23:02 ` Differences in emulation between kvm and kvm -no-kvm Milan Plzik

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=1239134359.8519.2111.camel@localhost \
    --to=milan.plzik@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox