From: Gerd Hoffmann <kraxel@redhat.com>
To: Jorge Lucangeli Obes <jorgelo@chromium.org>
Cc: Avi Kivity <avi@redhat.com>, Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org
Subject: Re: Running KVM inside a chroot
Date: Wed, 02 Nov 2011 09:36:15 +0100 [thread overview]
Message-ID: <4EB100FF.9020603@redhat.com> (raw)
In-Reply-To: <CAKYuF5T46mW8Ks0TQ4rS5+q0UE9ouFCjbjNdZLqtr+-Ym+8_2w@mail.gmail.com>
Hi,
> OK, I'll check that, thanks. However, KVM inside the chroot was
> already slow when the version outside the chroot was 0.12.3 and the
> version inside was 0.12.5.
That is strange. There are no code changes in the vga emulation between
0.12.3 and 0.12.5 ...
Which vga you are using? The default (cirrus)? Or another one?
Does vesafb (vga=0x317) work inside/outside the chroot?
How do the vesafb boot messages look like (dmesg | grep vesafb)?
How does /proc/iomem look like?
cheers,
Gerd
next prev parent reply other threads:[~2011-11-02 8:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 18:49 Running KVM inside a chroot Jorge Lucangeli Obes
2011-10-12 19:55 ` Alexander Graf
[not found] ` <CAKYuF5TG4+5yaVZh9KX0wLOjjg2h01Maz-VOsr2u4BVHzE8i7g@mail.gmail.com>
2011-10-13 0:51 ` Jorge Lucangeli Obes
2011-10-16 16:23 ` Avi Kivity
2011-10-17 6:10 ` Jorge Lucangeli Obes
2011-10-17 9:56 ` Avi Kivity
2011-10-17 16:37 ` Jorge Lucangeli Obes
2011-10-18 10:29 ` Avi Kivity
2011-10-18 16:43 ` Jorge Lucangeli Obes
2011-10-18 17:28 ` Avi Kivity
2011-10-18 17:39 ` Jorge Lucangeli Obes
2011-10-18 17:46 ` Avi Kivity
2011-10-20 3:30 ` Jorge Lucangeli Obes
2011-10-30 14:36 ` Avi Kivity
2011-10-30 14:41 ` Avi Kivity
2011-11-01 16:06 ` Jorge Lucangeli Obes
2011-11-01 16:29 ` Gerd Hoffmann
2011-11-01 18:10 ` Jorge Lucangeli Obes
2011-11-02 0:12 ` Jorge Lucangeli Obes
2011-11-02 8:36 ` Gerd Hoffmann [this message]
2011-10-19 15:38 ` David Ahern
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=4EB100FF.9020603@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=jorgelo@chromium.org \
--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).