From: Avi Kivity <avi@redhat.com>
To: Farkas Levente <lfarkas@lfarkas.org>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] kvm-83 release
Date: Thu, 15 Jan 2009 16:00:07 +0200 [thread overview]
Message-ID: <496F4167.5090607@redhat.com> (raw)
In-Reply-To: <496CB945.1080400@lfarkas.org>
Farkas Levente wrote:
> Avi Kivity wrote:
>
>> The biggest change this time around is support for the AMD IOMMU for
>> device assignment. As it requires extensive core kernel support, it is
>> only available on Linux 2.6.29rc1 or higher hosts.
>>
>
> status report on rhel/centos-5.2 host:
> - fedora-9 latest kernel now boot again
> - fedora-10 installer stop at "waiting for hardware..." so it's
> currently not able to upgrade fedora-9 guest neither from cdrom nor form
> preupgrade (ie hard disk).
>
Works here. What's your host cpu type? Does the error occur if you pin
the guest to one host cpu?
> and these dozens of warning still comes during compilation on
> rhel/centos 5.2:
> -----------------------------------------
> In file included from
> /home/robot/rpm/BUILD/kvm-83/kernel/include/asm/kvm_host.h:65,
> from
> /home/robot/rpm/BUILD/kvm-83/kernel/include/linux/kvm_host.h:67,
> from /home/robot/rpm/BUILD/kvm-83/kernel/x86/lapic.c:60:
> /home/robot/rpm/BUILD/kvm-83/kernel/include-compat/asm/msr-index.h:30:1:
> warning: "MSR_IA32_PERFCTR0" redefined
>
I've fixed those for kvm-84.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-01-15 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 13:53 [ANNOUNCE] kvm-83 release Avi Kivity
2009-01-13 15:54 ` Farkas Levente
2009-01-15 14:00 ` Avi Kivity [this message]
2009-01-15 20:17 ` Farkas Levente
2009-01-13 16:15 ` John Wong
2009-01-13 17:27 ` Mark McLoughlin
2009-01-13 17:40 ` John Wong
2009-01-13 18:22 ` Amit Shah
2009-01-13 20:32 ` Michael Tokarev
2009-01-13 20:35 ` Michael Tokarev
2009-01-13 20:37 ` Anthony Liguori
2009-01-13 21:01 ` Michael Tokarev
2009-01-13 22:30 ` Mark McLoughlin
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=496F4167.5090607@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lfarkas@lfarkas.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.