From: Gleb Natapov <gleb@redhat.com>
To: Alec Joseph Rivera <eijhei@gmail.com>
Cc: Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, Meric Mara <mmara@8layertech.com>,
Renan Mara <rmara@8layertech.com>
Subject: Re: 2.6.16 Guest Hangs on Boot
Date: Thu, 16 Sep 2010 09:56:05 +0200 [thread overview]
Message-ID: <20100916075605.GT3008@redhat.com> (raw)
In-Reply-To: <1284623537.7482.169.camel@nami.8liens.com>
On Thu, Sep 16, 2010 at 03:52:17PM +0800, Alec Joseph Rivera wrote:
> On Thu, 2010-09-16 at 08:39 +0200, Gleb Natapov wrote:
> > On Thu, Sep 16, 2010 at 09:55:38AM +0800, Alec Joseph Rivera wrote:
> > > > That should give us a clue on what's going wrong.
> > > >
> > >
> > > I did the steps you mentioned. Here's the gdb transcript:
> > >
> > > $ gdb k12_1009 -ex 'target remote localhost:1234'
> > What is k12_1009? Are you sure this is vmlinux?
> >
>
> Hi Gleb:
>
> Yes, k12_1009 is the kernel image that isolinux loads.
>
> -- isolinux.cfg
>
> > DEFAULT 1
> > TIMEOUT 100
> > PROMPT 1
> > DISPLAY isolinux.txt
> > LABEL 1
> > KERNEL k12_1009
> > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram
> > LABEL 2
> > KERNEL k12_1009
> > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram BOOT_SUPPORT=1
>
> -- file test
> > $ file k12_1009
> > k12_1009: Linux kernel x86 boot executable bzImage, version 2.6.16.54-0.2.5-bigsmp (geeko@b, RO-rootFS, root_dev 0x301, swap_dev 0x1, Normal VGA
>
This is bzImage, You need corresponding vmlinux bzImage was created
from.
> > BTW what version on kvm/qemu are you using.
> >
>
> qemu's version is 0.12.5. modinfo kvm doesn't reveal any version string
> though, however the kernel is 2.6.35 from Arch.
>
> Question: from what I've read so far kvm versions are of 'kvm-xx' where
> xx is a number, on sourceforge there is kvm-kmod-{kernel-version}, am I
> correct in assuming and saying then that my kvm version is 2.6.35?
>
kvm-xx is deprecated. So when asked what kvm are you using you should
provide your kernel version like you did.
--
Gleb.
next prev parent reply other threads:[~2010-09-16 7:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 16:53 2.6.16 Guest Hangs on Boot Alec Joseph Rivera
2010-09-15 17:28 ` Alexander Graf
2010-09-15 17:48 ` Alec Joseph Rivera
2010-09-15 17:51 ` Alexander Graf
2010-09-15 18:07 ` Alec Joseph Rivera
2010-09-15 18:15 ` Alexander Graf
2010-09-15 18:26 ` Alec Joseph Rivera
2010-09-16 1:55 ` Alec Joseph Rivera
2010-09-16 6:39 ` Gleb Natapov
2010-09-16 7:52 ` Alec Joseph Rivera
2010-09-16 7:56 ` Gleb Natapov [this message]
2010-09-16 8:03 ` Alec Joseph Rivera
2010-09-16 10:11 ` Alec Joseph Rivera
2010-09-16 10:14 ` Gleb Natapov
2010-09-16 11:13 ` Alec Joseph Rivera
2010-09-16 11:18 ` Gleb Natapov
2010-09-16 10:27 ` Alexander Graf
2010-09-16 11:02 ` Joerg Roedel
2010-09-16 11:11 ` Alec Joseph Rivera
2010-09-16 11:32 ` Joerg Roedel
2010-09-16 11:35 ` Michael Tokarev
2010-09-16 11:41 ` Gleb Natapov
2010-09-16 11:43 ` Joerg Roedel
2010-09-16 11:37 ` Alec Joseph Rivera
2010-09-16 11:41 ` Gleb Natapov
2010-09-16 11:51 ` Alec Joseph Rivera
2010-09-15 18:37 ` Michael Tokarev
2010-09-16 8:17 ` Alec Joseph Rivera
2010-09-16 8:32 ` Dave Young
2010-09-16 9:56 ` Alec Joseph Rivera
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=20100916075605.GT3008@redhat.com \
--to=gleb@redhat.com \
--cc=agraf@suse.de \
--cc=eijhei@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mmara@8layertech.com \
--cc=rmara@8layertech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox