From: Daniel Bareiro <daniel-listas@gmx.net>
To: KVM General <kvm@vger.kernel.org>
Subject: Re: Modifying RAM during runtime on guest
Date: Tue, 13 Oct 2009 13:55:09 -0300 [thread overview]
Message-ID: <20091013165509.GF5358@defiant.freesoftware.org> (raw)
In-Reply-To: <20091007182115.GA30245@psychosis.jim.sh>
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
Hi Jim.
On Wednesday, 07 October 2009 14:21:15 -0400,
Jim Paris wrote:
> > > > I noticed no-one answered this, and I just ran into the same
> > > > thing myself. As Avi pointed out earlier, it is a guest bug, and
> > > > upgrading the guest to 2.6.27 should fix it:
> > > > http://www.mail-archive.com/kvm@vger.kernel.org/msg10849.html
> > > In this moment I doesn't have Internet connectivity in my house,
> > > but, as soon as it be possible, I shall download the necessary
> > > software to compile 2.6.27 or superior and then I tell you the
> > > result of the tests.
> > After to have compiled Linux 2.6.30.3 using the Debian way on guest
> > Debian GNU/Linux Lenny, when trying to boot the guest with this
> > kernel, the bootstrapping is freeze on "Loading, please wait..."
> > message.
> >
> > In logs I don't get entries of the bootstrapping process with 2.6.30
> > (I think it is because the process in itself didn't start). Can it
> > be due to a bug using 2.6.30.3 in guest with host KVM-88?
> 2.6.30.3 should work fine, there must be some other problem. If you
> remove "quiet" from the boot command line you should see the kernel
> messages which may indicate the problem. I'd also recommend just
> trying a standard prebuilt Debian kernel.
> http://packages.debian.org/squeeze/linux-image-2.6.30-1-amd64
As we commented in this [1] thread, the problem was due to a patch that
Debian developers have applied to stock kernels enabling only libata for
the systems having a SATA controller.
For that reason the Debian stock kernel saw disks as hdX and kernels
2.6.31.2 and 2.6.30.3 compiled by myself saw disks like sdX. After
booting, with 2.6.3x, no longer panic is observed when restituting the
memory to its initial value.
Thanks for your reply.
Regards,
Daniel
[1] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/41158
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Squeeze - Linux user #188.598
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-10-13 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 20:52 Modifying RAM during runtime on guest Daniel Bareiro
2009-09-08 21:18 ` Brian Jackson
2009-09-09 10:20 ` Daniel Bareiro
2009-09-29 4:55 ` Jim Paris
2009-10-04 23:35 ` Daniel Bareiro
2009-10-06 17:35 ` Daniel Bareiro
2009-10-07 18:21 ` Jim Paris
2009-10-13 16:55 ` Daniel Bareiro [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=20091013165509.GF5358@defiant.freesoftware.org \
--to=daniel-listas@gmx.net \
--cc=dbareiro@gmx.net \
--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;
as well as URLs for NNTP newsgroup(s).