From: "Richard W.M. Jones" <rjones@redhat.com>
To: Zetan Drableg <zetan.drableg@gmail.com>
Cc: libguestfs@redhat.com, kvm <kvm@vger.kernel.org>
Subject: Re: hang after seabios
Date: Thu, 31 Jul 2014 20:17:16 +0100 [thread overview]
Message-ID: <20140731191716.GF1302@redhat.com> (raw)
In-Reply-To: <CABviRoSHX_=Gv51mOEOuRurywM06C=0e2648+ttazq4nKFx2UQ@mail.gmail.com>
On Thu, Jul 31, 2014 at 12:12:26PM -0700, Zetan Drableg wrote:
> Hi Richard thanks for the info.
> I took the strace approach and ran into this looping over and over again.
> Is it failing to get time?
>
> timer_gettime(0x8, {it_interval={0, 0}, it_value={0, 0}}) = 0
> timer_settime(0x8, 0, {it_interval={0, 0}, it_value={0, 250000}}, NULL) = 0
> timer_gettime(0x8, {it_interval={0, 0}, it_value={0, 204443}}) = 0
> select(16, [0 6 9 13 15], [], [], {1, 0}) = 2 (in [6 13], left {0, 999998})
> read(13, "\1\0\0\0\0\0\0\0", 4096) = 8
> read(13, 0x7fffa2ed3f70, 4096) = -1 EAGAIN (Resource
> temporarily unavailable)
> read(6, "\0", 512) = 1
> read(6, 0x7fffa2ed4d70, 512) = -1 EAGAIN (Resource
> temporarily unavailable)
> select(16, [0 6 9 13 15], [], [], {1, 0}) = 1 (in [15], left {0, 999998})
> read(15, "\16\0\0\0\0\0\0\0\376\377\377\377\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\0\0\0\0"...,
> 128) = 128
> rt_sigaction(SIGALRM, NULL, {0x7f6d8b8d17d0, ~[KILL STOP RTMIN RT_1],
> SA_RESTORER, 0x7f6d8b211710}, 8) = 0
> write(7, "\0", 1) = 1
> write(14, "\1\0\0\0\0\0\0\0", 8) = 8
> read(15, 0x7fffa2ed4ee0, 128) = -1 EAGAIN (Resource
> temporarily unavailable)
> timer_gettime(0x8, {it_interval={0, 0}, it_value={0, 0}}) = 0
> timer_settime(0x8, 0, {it_interval={0, 0}, it_value={0, 988758000}}, NULL) = 0
> select(16, [0 6 9 13 15], [], [], {1, 0}) = 2 (in [6 13], left {0, 999998})
> read(13, "\1\0\0\0\0\0\0\0", 4096) = 8
> read(13, 0x7fffa2ed3f70, 4096) = -1 EAGAIN (Resource
> temporarily unavailable)
> read(6, "\0", 512) = 1
> read(6, 0x7fffa2ed4d70, 512) = -1 EAGAIN (Resource
> temporarily unavailable)
>
> It looks a lot like the bug you filed here.
> https://bugzilla.redhat.com/show_bug.cgi?id=553689
I'm fairly sure this is just qemu running as normal. It's not a
duplicate of that ancient bug, because you can see from the messages
that SeaBIOS is running.
You need to `gdb' into the guest to see where the emulation got to.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
prev parent reply other threads:[~2014-07-31 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 22:58 hang after seabios Zetan Drableg
2014-07-31 11:31 ` Richard W.M. Jones
2014-07-31 19:12 ` Zetan Drableg
2014-07-31 19:17 ` Richard W.M. Jones [this message]
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=20140731191716.GF1302@redhat.com \
--to=rjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libguestfs@redhat.com \
--cc=zetan.drableg@gmail.com \
/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.