Michael Riepe wrote:
> Hi!
>
> Carsten Emde wrote:
>
>
>> Actually, the above line can be preserved, if we move the previous line
>> down by 1: Was it a simple race?
>>
>> --- kvm_main-17.c2007-03-24 02:09:00.0 +0100
>> +++ kvm_main.c 2007-03-24 04:10:59.0 +0100
>> @@
Michael Riepe wrote:
> Hi!
>
> Carsten Emde wrote:
>
>> Avi Kivity wrote:
>>
>>
>>> Michael Riepe wrote:
>>>
>>>
With respect to the Core Duo, this is the best release I've seen so far:
>> Unfortunately, kvm-17 was less successful here. FC6 did not boot any
>> lon
Carsten Emde wrote:
> Carsten Emde wrote:
>> I then reverted to kvm-16 and repeated all upgrade changes until the
>> problem occurred. The culprit was found to be
>> [..]
>> +#ifdef THIS_PREVENTS_FC6_FROM_BOOTING
>> emulate_instruction(vcpu, kvm_run, vcpu->mmio_fault_cr2, 0);
>> +#endif
Carsten Emde wrote:
> Avi Kivity wrote:
>> Michael Riepe wrote:
>>> With respect to the Core Duo, this is the best release I've seen so
>>> far:
> Unfortunately, kvm-17 was less successful here. FC6 did not boot any
> longer after I upgraded from kvm-16 to kvm-17, so I was rather
> surprised whe
Hi!
>> Actually, the above line can be preserved, if we move the previous line
>> down by 1: Was it a simple race?
>> --- kvm_main-17.c2007-03-24 02:09:00.0 +0100
>> +++ kvm_main.c 2007-03-24 04:10:59.0 +0100
>> [..]
>> -vcpu->mmio_read_completed = 1;
>>
Michael,
With respect to the Core Duo, this is the best release I've seen so far:
>> Unfortunately, kvm-17 was less successful here. FC6 did not boot any
>> longer after I upgraded from kvm-16 to kvm-17, so I was rather surprised
>> when I read the above message. [..]
> But it was the first
Hi!
Carsten Emde wrote:
> Actually, the above line can be preserved, if we move the previous line
> down by 1: Was it a simple race?
>
> --- kvm_main-17.c 2007-03-24 02:09:00.0 +0100
> +++ kvm_main.c2007-03-24 04:10:59.0 +0100
> @@ -1574,8 +1574,8 @@
>
> if (k
Hi!
Carsten Emde wrote:
> Avi Kivity wrote:
>
>>Michael Riepe wrote:
>>
>>>With respect to the Core Duo, this is the best release I've seen so far:
>
> Unfortunately, kvm-17 was less successful here. FC6 did not boot any
> longer after I upgraded from kvm-16 to kvm-17, so I was rather surprised
Carsten Emde wrote:
> I then reverted to kvm-16 and repeated all upgrade changes until the
> problem occurred. The culprit was found to be
> [..]
> +#ifdef THIS_PREVENTS_FC6_FROM_BOOTING
> emulate_instruction(vcpu, kvm_run, vcpu->mmio_fault_cr2, 0);
> +#endif
> [..]
Actually, the abo
Avi Kivity wrote:
> Michael Riepe wrote:
>> With respect to the Core Duo, this is the best release I've seen so far:
Unfortunately, kvm-17 was less successful here. FC6 did not boot any
longer after I upgraded from kvm-16 to kvm-17, so I was rather surprised
when I read the above message.
This i
Michael Riepe wrote:
> Hi!
>
> With respect to the Core Duo, this is the best release I've seen so far:
>
> - FreeBSD 6.1: works.
> - NetBSD 3.1: works.
> - OpenSuse 10.2 (sans gfxmenu): works.
> - Qemu-Puppy 2.01-3: works.
> - Qemu-Puppy 2.13-1: works.
> - Solaris 10.1: works.
> - XP Pro: works.
>
Michael Riepe wrote:
> Hi!
>
> With respect to the Core Duo, this is the best release I've seen so far:
>
> - FreeBSD 6.1: works.
> - NetBSD 3.1: works.
> - OpenSuse 10.2 (sans gfxmenu): works.
> - Qemu-Puppy 2.01-3: works.
> - Qemu-Puppy 2.13-1: works.
> - Solaris 10.1: works.
> - XP Pro: works.
>
Hi!
With respect to the Core Duo, this is the best release I've seen so far:
- FreeBSD 6.1: works.
- NetBSD 3.1: works.
- OpenSuse 10.2 (sans gfxmenu): works.
- Qemu-Puppy 2.01-3: works.
- Qemu-Puppy 2.13-1: works.
- Solaris 10.1: works.
- XP Pro: works.
Unfortunately, Knoppix (both 5.0 and 5.1.
Highlights: acpi works again.
Changes from kvm-16:
- live migration enhancements (Uri Lublin)
- better/working acpi support
- revert to unhacked qemu bios
- fix some 32-bit nonpae guests (*BSD)
- initial ballooning support
- random fixes
Note that if you use the modules from Linux 2.6.20, you ne
14 matches
Mail list logo
