From: Daniel Bareiro <dbareiro@uol.com.ar>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Alexander Graf <agraf@suse.de>, KVM General <kvm@vger.kernel.org>
Subject: Re: Testing nested virtualization
Date: Mon, 4 Jan 2010 20:56:54 -0300 [thread overview]
Message-ID: <20100104235654.GH2794@defiant.freesoftware> (raw)
In-Reply-To: <20100104160415.GI14679@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Monday, 04 January 2010 17:04:16 +0100,
Joerg Roedel wrote:
> Hi Daniel,
Hi, Joerg.
> > test:~# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> > kvm-clock
> >
> > test:~# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> > kvm-clock hpet acpi_pm
> Can you try to boot L1 and L2 guest with the 'no-kvmclock' kernel
> parameter? This disables the kvm-clock.
Question: what is L1 and L2? Because it sounds to cache levels, but I
suppose that against this background one will talk about another thing.
Beyond that, using no-kvmclock kernel parameter en 'test', now I have
the following thing:
test:~# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
hpet
test:~# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
hpet acpi_pm
But the same happens. The Debian installer hangs in the initial screen.
Thanks for your reply.
Regards,
Daniel
--
Daniel Bareiro - GNU/Linux registered user #188.598
Proudly running Debian GNU/Linux with uptime:
20:43:21 up 1 day, 5:28, 11 users, load average: 0.21, 0.20, 0.12
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-01-04 23:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 20:20 Testing nested virtualization Daniel Bareiro
2010-01-01 20:56 ` Daniel Bareiro
2010-01-02 13:11 ` Alexander Graf
2010-01-02 13:45 ` Daniel Bareiro
2010-01-02 13:48 ` Alexander Graf
2010-01-02 13:49 ` Alexander Graf
2010-01-04 11:11 ` Joerg Roedel
2010-01-04 14:20 ` Daniel Bareiro
2010-01-04 15:07 ` Alexander Graf
2010-01-04 15:52 ` Daniel Bareiro
2010-01-04 16:04 ` Joerg Roedel
2010-01-04 23:56 ` Daniel Bareiro [this message]
2010-01-02 14:18 ` Daniel Bareiro
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=20100104235654.GH2794@defiant.freesoftware \
--to=dbareiro@uol.com.ar \
--cc=agraf@suse.de \
--cc=dbareiro@gmx.net \
--cc=joerg.roedel@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.