Avi Kivity wrote:
> Laurent Vivier wrote:
>> Avi Kivity wrote:
>>
>>> Farkas Levente wrote:
>>>
hi,
it seems we've got a real tester:-) for ma all of the bellow are
serious
bugs (tomorrow i'll try to send more detail of our host crash too) and
imho the latest 'stable'
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Farkas Levente wrote:
>>
>>> hi,
>>> it seems we've got a real tester:-) for ma all of the bellow are serious
>>> bugs (tomorrow i'll try to send more detail of our host crash too) and
>>> imho the latest 'stable' version was kvm-36. wouldn't b
Avi Kivity wrote:
> Farkas Levente wrote:
>> hi,
>> it seems we've got a real tester:-) for ma all of the bellow are serious
>> bugs (tomorrow i'll try to send more detail of our host crash too) and
>> imho the latest 'stable' version was kvm-36. wouldn't be better to
>> postpone all patches and in
Farkas Levente wrote:
> hi,
> it seems we've got a real tester:-) for ma all of the bellow are serious
> bugs (tomorrow i'll try to send more detail of our host crash too) and
> imho the latest 'stable' version was kvm-36. wouldn't be better to
> postpone all patches and infrastructure changes (vir
hi,
it seems we've got a real tester:-) for ma all of the bellow are serious
bugs (tomorrow i'll try to send more detail of our host crash too) and
imho the latest 'stable' version was kvm-36. wouldn't be better to
postpone all patches and infrastructure changes (virtio and others)
until these have
Hi, all,
This is today's KVM test result against kvm.git
62d1ea7fdcdb905072198e4cec8f724c8ad33092 and kvm-userspace.git
667f2deff8cea6327f0c832afea2f4952b8f199e.
In today's testing, smp windows still couldn't be booted up.
1 issue is closed
1. save
