From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: Onkar N Mahajan <kernzap@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Guest freezes "Refined TSC clocksource calibration ..."
Date: Wed, 5 Oct 2011 01:41:53 +0700 [thread overview]
Message-ID: <CAGdaadb8SM2h1155REfeNDu8wCRUESpj4ULe-fAL9XEmsWMtWQ@mail.gmail.com> (raw)
In-Reply-To: <4E8AE7D0.40703@gmail.com>
Hi Onkar :)
On Tue, Oct 4, 2011 at 18:02, Onkar N Mahajan <kernzap@gmail.com> wrote:
> On 10/02/2011 12:54 PM, Mulyadi Santosa wrote:
>>
>> Hi..... :)
>>
> Hey Mulyadi , you seem to be where I go (or may be other way round) :-) ;
> How
> r u buddy ??
Yeah, it's like we always at the same boat :) But it's great, isn't
it? Meaning we might have same interest :)
>> On Sat, Oct 1, 2011 at 19:16, Onkar N Mahajan<kernzap@gmail.com> wrote:
>> Quite simple things you can try first:
>> - what if you use device name like /dev/sda1 instead? does that work?
>>
> I tried this - it's the same !!
OK that's bad. Sure you don't miss things like SCSI/SATA controller
compiled in your kernel?
>> - are you sure you have included the suitable filesystem module for
>> the root partition in the initrd or the main kernel image?
>
> Host is using same vmlinuz and initrd and is workign absolutely ok !!
> looks like some problem with qemu ;-)
>
After thinking again, could you fallback using non -rc kernel? could
be a bug somewhere....
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-10-04 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 12:16 [Qemu-devel] Guest freezes "Refined TSC clocksource calibration ..." Onkar N Mahajan
2011-10-02 7:24 ` Mulyadi Santosa
2011-10-02 8:24 ` Dor Laor
[not found] ` <4E8AE7D0.40703@gmail.com>
2011-10-04 18:41 ` Mulyadi Santosa [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=CAGdaadb8SM2h1155REfeNDu8wCRUESpj4ULe-fAL9XEmsWMtWQ@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernzap@gmail.com \
--cc=qemu-devel@nongnu.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).