>> The qemu version we are using is:
>> ii qemu 0.10.1-1 fast processor emulator
>> running on x86:
>> Linux genesis 2.6.26-1-686 #1 SMP Fri Mar 13 18:08:45 UTC 2009 i686 GNU/Linux
>>
>
> I am sorry, but I am not able to use your core, as I don't have the
> exact same version of th
>> > Thanks, I have been able to download it, but I don't know to which
>> > binary it correspond. Could you please give me the architecture and the
>> > version you used to generate this file? Thanks.
>>
>> The qemu version we are using is:
>> ii qemu 0.10.1-1 fast processor emula
On Wed, Apr 01, 2009 at 06:13:11PM -0300, Pedro Bulach Gapski wrote:
> Aurelien,
>
> >> There is a core image at
> >> http://www.reckon.com.br/PedroGapski?action=AttachFile (warning: slow
> >> link)
> >
> > Thanks, I have been able to download it, but I don't know to which
> > binary it correspond
Aurelien,
>> There is a core image at
>> http://www.reckon.com.br/PedroGapski?action=AttachFile (warning: slow
>> link)
>
> Thanks, I have been able to download it, but I don't know to which
> binary it correspond. Could you please give me the architecture and the
> version you used to generate th
On Wed, Apr 01, 2009 at 01:46:29PM -0300, Pedro Bulach Gapski wrote:
> Aurelien,
>
> >> It seems that the lockups happen during high load on the guest, and
> >> the locked qemu process goes on eating 100% CPU. The problem now seems
> >> fairly straighforward to reproduce. Is a core image usefull?
Aurelien,
>> It seems that the lockups happen during high load on the guest, and
>> the locked qemu process goes on eating 100% CPU. The problem now seems
>> fairly straighforward to reproduce. Is a core image usefull?
>>
>
> A core image or at least a backtrace would indeed be useful. Also if
> p
Pedro Bulach Gapski a écrit :
> We have been trying to better isolate this issue.
>
> First test was to use taskset to bind the qemu process to a single
> CPU, following advice found on qemu mailing lists. This proved
> insufficient, as the image locked up during the night.
>
> Next we tried to r
We have been trying to better isolate this issue.
First test was to use taskset to bind the qemu process to a single
CPU, following advice found on qemu mailing lists. This proved
insufficient, as the image locked up during the night.
Next we tried to run qemu without VNC and tap options. After a
8 matches
Mail list logo
