From: Ross Boylan <ross@biostat.ucsf.edu>
To: kvm@vger.kernel.org
Subject: VM hang: how to get latest sources
Date: Sat, 28 Sep 2013 14:22:46 -0700 [thread overview]
Message-ID: <1380403366.5913.108.camel@localhost> (raw)
My VM keeps hanging (high host CPU use, no response except from the
monitor) and I assume the first advice I will get is to use the current
version of qemu/kvm.
Where and what is that? It seems there is a development and production
release, and things have mostly been folded into qemu. I'm not sure
what flavor is appropriate. Some earlier messages on the list referred
to a git repo.
I'm running Debian wheezy amd64 with linux kernel 3.2.0-4-amd64 and
qemu-kvm 1.1.2+dfsg-6. It looks as if the most current version in sid
is qemu-system-x86 (1.6.0+dfsg-1). If the side version is recent enough
it would probably be a bit easier for me to get going.
I would like to avoid upgrading the kernel if possible.
I am invoking with -cpu pentium3 -smp 2. The host processor is
Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz (4 cores, 8 hyperthreads).
If anyone can help me on my problems with the current version, I would
welcome it. Here are some more questions.
Do I get hardware virtualization if I specify -cpu pentium3?
Side note: I'm not sure I need the -cpu at all; I am trying to recover a
32 bit OS (Debian Lenny) that ran on a Pentium 4 before it died. I may
try running without the -cpu argument to see if that helps.
Details of the crashes are at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724798. Any ideas
about what's going on? How can I capture more useful diagnostic
information?
Thanks.
Ross Boylan
next reply other threads:[~2013-09-28 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 21:22 Ross Boylan [this message]
2013-09-30 8:20 ` VM hang: how to get latest sources Stefan Hajnoczi
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=1380403366.5913.108.camel@localhost \
--to=ross@biostat.ucsf.edu \
--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.