Avi Kivity wrote:
> Jeremy Katz wrote:
>>> What do you mean by "current state of migration"? How to run it for
>>> testing?
>>>
>>
>> Yep
>>
>
> I've asked Uri to add a section to the web site.
>
This is now http://kvm.sourceforge.net/migration.html.
--
error compiling committee.c: too
Jeremy Katz wrote:
>> What do you mean by "current state of migration"? How to run it for
>> testing?
>>
>
> Yep
>
I've asked Uri to add a section to the web site.
--
error compiling committee.c: too many arguments to function
-
On Thu, 2006-12-21 at 16:26 +0200, Avi Kivity wrote:
> Jeremy Katz wrote:
> > On Thu, 2006-12-21 at 11:20 +0200, Avi Kivity wrote:
> >> Jeremy Katz wrote:
> >>> Currently, kvm ends up just using the standard qemu cpu initialization.
> >>> This means that all x86_64 virtual machines appear to have a
Jeremy Katz wrote:
> On Thu, 2006-12-21 at 11:20 +0200, Avi Kivity wrote:
>
>> Jeremy Katz wrote:
>>
>>> Currently, kvm ends up just using the standard qemu cpu initialization.
>>> This means that all x86_64 virtual machines appear to have an
>>> AuthenticAMD (AMD64) processor. This ends u
On Thu, 2006-12-21 at 11:20 +0200, Avi Kivity wrote:
> Jeremy Katz wrote:
> > Currently, kvm ends up just using the standard qemu cpu initialization.
> > This means that all x86_64 virtual machines appear to have an
> > AuthenticAMD (AMD64) processor. This ends up causing a problem when
> > bootin
Hi!
Avi Kivity wrote:
> Windows crashes immediately with this patch (STOP: 0x7E (0xc005
> 0xF724879C 0xF7A168DC 0xF7A165D8) for those who know how to decode
> BSODs), so either it's doing too much or not enough.
>
> Note that we support migration from Intel to AMD and vice versa, so it
>
Jeremy Katz wrote:
> Currently, kvm ends up just using the standard qemu cpu initialization.
> This means that all x86_64 virtual machines appear to have an
> AuthenticAMD (AMD64) processor. This ends up causing a problem when
> booting some x86_64 Linux kernels as they attempt to do AMD64 specifi
