From: Dor Laor <dlaor@redhat.com>
To: Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: Onkar N Mahajan <kernzap@gmail.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Guest freezes "Refined TSC clocksource calibration ..."
Date: Sun, 02 Oct 2011 10:24:48 +0200 [thread overview]
Message-ID: <4E881FD0.5070501@redhat.com> (raw)
In-Reply-To: <CAGdaadY0WPPEqjy11Yvwa6Wuc0ZpEHrxr6hr9mDHC6-=5Afu5g@mail.gmail.com>
On 10/02/2011 09:24 AM, Mulyadi Santosa wrote:
> Hi..... :)
>
> On Sat, Oct 1, 2011 at 19:16, Onkar N Mahajan<kernzap@gmail.com> wrote:
>>
>> Compiled 3.1.0-rc3+ from source (see attached config file) and updated the
>> host(fc14) kernel ;
>> So host is now running 3.1.0-rc3+
>>
>> Now I also want to try to boot FC14 guest with this updated kernel , like
>> this -
>>
>> ./qemu-kvm-virtfs -drive file=/home/onkar/bin/v9fs-guest.img,if=virtio -m
>> 1024 -smp 4 -net nic,macaddr=54:52:00:46:26:84,model=virtio -net
>> tap,script=./qemu-ifup,ifname=vnet1 --enable-kvm -vnc :10 -kernel
>> /boot/vmlinuz-3.1.0-rc3p -initrd /boot/initrd-3.1.0-rc3p.img -append
>> 'root=UUID=97e4bdfa-c88b-4e1f-8609-10f76d6a35fa' -monitor stdio
>
> Quite simple things you can try first:
> - what if you use device name like /dev/sda1 instead? does that work?
>
> - are you sure you have included the suitable filesystem module for
> the root partition in the initrd or the main kernel image?
>
It indeed looks that this is the problem because your log shows that no
root device was found after the successful tsc calibration stage.
next prev parent reply other threads:[~2011-10-02 8:24 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 [this message]
[not found] ` <4E8AE7D0.40703@gmail.com>
2011-10-04 18:41 ` Mulyadi Santosa
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=4E881FD0.5070501@redhat.com \
--to=dlaor@redhat.com \
--cc=kernzap@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mulyadi.santosa@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).