From: Ross Boylan <ross@biostat.ucsf.edu>
To: kvm@vger.kernel.org
Cc: ross@biostat.ucsf.edu
Subject: out of memory error leads to unbootable VM
Date: Tue, 02 Jun 2009 09:15:25 -0700 [thread overview]
Message-ID: <1243959325.14381.27.camel@corn.betterworld.us> (raw)
I had a VM running Linux. While running that SAS installer the kernel
ran out of memory and killed the installer. After that, any attempt to
run a binary inside the VM produced "cannot execute binary file". The
log (inside the VM) also showed messages like
"Buffer I/O error on device hda1, logical block 12243549368".
hda1 is 86\% full.
I killed the VM and attempted to restart. However, the virtual BIOS
says the disk is unrecognizeable.
lvscan shows, among other things,
inactive Original '/dev/turtle/Lenny00' [5.00 GB] inherit
ACTIVE '/dev/turtle/SAS92' [33.00 GB] inherit
inactive Snapshot '/dev/turtle/Lenny01SAS' [3.00 GB] inherit
The active volume has the installation disk; Lenny01SAS was the "disk"
the VM was using; it is a snapshot of Lenny00. I have not deliberately
deactivated either.
lvdisplay does not give any indication of COW overflow, though that may
be because the volumes are inactive.
Only about 11G of SAS92 are in use. The SAS installation docs seem to
indicate 1 to 1.5G for a full installation. Although it looks as if I
had enough room, I suppose a snapshot overflow could account for the
inactive snapshot (and inactive original?).
It probably did run out of virtual RAM, since kvm started
(inadvertently) with the default RAM.
Any ideas what's going on?
Thanks.
Ross Boylan
next reply other threads:[~2009-06-02 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 16:15 Ross Boylan [this message]
2009-06-02 16:27 ` out of memory error leads to unbootable VM Avi Kivity
2009-06-02 17:05 ` Ross Boylan
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=1243959325.14381.27.camel@corn.betterworld.us \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox