From: Gerd Hoffmann <kraxel@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: seabios <seabios@seabios.org>,
qemu-devel@nongnu.org, Sebastian <basti@sraa.de>
Subject: Re: [Qemu-devel] WfW setup and DOS display.sys hanging
Date: Wed, 05 Feb 2014 14:19:58 +0100 [thread overview]
Message-ID: <1391606398.17309.10.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <20140204194704.GA2680@dhcp-200-207.str.redhat.com>
[ adding seabios list ]
On Di, 2014-02-04 at 20:47 +0100, Kevin Wolf wrote:
> Hi Gerd,
>
> Am 09.01.2014 um 00:20 hat Sebastian geschrieben:
> > Hi,
> >
> > I noticed in newer versions of Qemu (Debian Jessie) a regression
> > causing DISPLAY.SYS from MS-DOS 6.22 to hang the system as soon as
> > loaded.
>
> now that you sent a pull request for a SeaBIOS update, I tried what
> would happen with this one. Sadly, while it does fix my hanging Win 7
> boot, DOS still hangs while loading display.sys.
[ This is http://www.kraxel.org/cgit/qemu/tag/?id=pull-roms-1
with the 1.7.4 update ]
Digged out my prehistoric msdos floppy images. Can confirm the hang.
Using default vga (i.e. cirrus).
Switching back to lgplvgabios ("make -C roms lgplvgabios" in qemu src
tree) makes the hang go away.
> Any ideas where to look, or are you going to have a look yourself? When
> I tried to debug it a while ago, I didn't see anything obvious, but then
> I didn't invest that much time for it either.
"perf kvm stat live" shows tons of NMIs:
VM-EXIT Samples Samples% Time% Min Time Max Time Avg time
EXCEPTION_NMI 660538 99.82% 99.40% 0us 183us 0.67us ( +- 0.14% )
EXTERNAL_INTERRUPT 1133 0.17% 0.58% 0us 43us 2.25us ( +- 4.86% )
IO_INSTRUCTION 18 0.00% 0.01% 1us 5us 3.39us ( +- 6.50% )
PENDING_INTERRUPT 17 0.00% 0.01% 1us 11us 2.15us ( +- 26.24% )
How can one get a trace log of all the kvm tracepoints these days?
'perf list' shows a bunch of kvm trace events,
but "perf trace -e '*kvm*' doesn't show me anything ...
cheers,
Gerd
> I haven't tried out any of the other cases described below.
[ keeping full quote for seabios list ]
> >
> > The Windows for Workgroups 3.11 SETUP.EXE file hangs with a cleared
> > screen and the cursor blinking in the top left of the screen. The
> > DOSIDLE.EXE[1] file hangs after printing out some system
> > information.
> >
> > Git-Bisecting returned "roms: update vgabios binaries" (commit
> > 6eefccc0bb9c34051b1e21880fc3a1c1c8686edd) as the bad commit.
> >
> > I tested the i386-softmmu target on Debian 7.3 (wheezy), x86_64 host
> > and gcc 4.7.2 (Debian 4.7.2-5) without KVM support.
> >
> > [1] Source and binary are available e.g. at
> > http://maribu.home.xs4all.nl/zeurkous/download/mirror/dosidle/
> >
> > Best Regards,
> > Sebastian
next prev parent reply other threads:[~2014-02-05 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 23:20 [Qemu-devel] WfW setup and DOS display.sys hanging Sebastian
2014-02-04 19:47 ` Kevin Wolf
2014-02-05 13:19 ` Gerd Hoffmann [this message]
2014-02-05 18:34 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2014-02-05 19:08 ` Kevin O'Connor
2014-02-05 20:57 ` Sebastian
2014-02-05 22:39 ` Kevin O'Connor
2014-02-10 14:57 ` Sebastian
2014-02-10 15:39 ` Kevin O'Connor
2014-02-06 8:17 ` Gerd Hoffmann
2014-02-06 16:22 ` Kevin O'Connor
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=1391606398.17309.10.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=basti@sraa.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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;
as well as URLs for NNTP newsgroup(s).