Hi,
On Wed, Apr 01, 2020 at 11:33:26PM +0200, sterbl.ta--- via wrote:
> Sorry I am not sure if this is the right place to ask but this is the only
> mailing list that most relevant. Apologize if this is not, and please let me
> know which place I should check. Thank you.
>
> My main question i
On Wed, Apr 01, 2020 at 06:46:02PM +0200, Paolo Bonzini wrote:
> On 01/04/20 18:37, Philippe Mathieu-Daudé wrote:
> >
> > * Refactor the open source project's existing documentation to
> > provide an improved user experience or a more accessible
> > information architecture.
>
> This kind of
Dear Stefano,
First thank you for providing the script. It's really useful!
I executed the commands in prerequisite section before running the perf script,
and its output as below
$ cat /sys/kernel/debug/tracing/events/kvm/enable
1
$ cat /proc/sys/kernel/perf_event_paranoid
-1
$ ls -ld /sys/k
On Thu, Apr 02, 2020 at 11:33:42AM +0200, sterbl...@tutanota.com wrote:
> Dear Stefano,
>
> First thank you for providing the script. It's really useful!
You're welcome! I'm happy that it could be useful :-)
>
> I executed the commands in prerequisite section before running the perf
> script,
Hello
On our kernelci lab, each qemu worker pass an healtcheck job each day and after
each job failure, so it is heavily used.
The healtcheck job is a Linux boot with a stable release.
Since we upgraded our worker to buster, the qemu x86_64 healthcheck randomly
panic with:
<6>[0.001000] API
Corentin,
Corentin Labbe writes:
> On our kernelci lab, each qemu worker pass an healtcheck job each day and
> after each job failure, so it is heavily used.
> The healtcheck job is a Linux boot with a stable release.
>
> Since we upgraded our worker to buster, the qemu x86_64 healthcheck random
On 4/2/20 2:57 AM, Thomas Gleixner wrote:
> Corentin,
>
> Corentin Labbe writes:
>> On our kernelci lab, each qemu worker pass an healtcheck job each day and
>> after each job failure, so it is heavily used.
>> The healtcheck job is a Linux boot with a stable release.
>>
>> Since we upgraded
Dongli Zhang writes:
> On 4/2/20 2:57 AM, Thomas Gleixner wrote:
>> Corentin Labbe writes:
>>> On our kernelci lab, each qemu worker pass an healtcheck job each day and
>>> after each job failure, so it is heavily used.
>>> The healtcheck job is a Linux boot with a stable release.
>>>
>>> Since
Hi Peter,
On Tue, Mar 31, 2020 at 6:03 PM Jesus Sanchez-Palencia
wrote:
> Hi Peter,
>
>
> On Tue, Mar 31, 2020 at 2:39 PM Peter Maydell
> wrote:
>
>> (...)
>
>
>
>> Probably there is a mismatch between where the firmware
>> is for you and where configure has told QEMU to look for it.
>> (Though
Placing "sleep 3" before qemu-system-x86_64 command as suggested fixes the
problem. Thank you once again for your kindly help, most appreciate it!
Apr 2, 2020, 09:57 by sgarz...@redhat.com:
> On Thu, Apr 02, 2020 at 11:33:42AM +0200, sterbl...@tutanota.com wrote:
>
>> Dear Stefano,
>>
>> First t
Hi
I have a working QEMU image emulating an ARM vexpress-a9 and I run it like so:
`sudo qemu-system-arm -m 512M -M vexpress-a9 -D qemu.log -d unimp -kernel
buildroot-2019.02.5/output/images/zImage -dtb
buildroot-2019.02.5/output/images/vexpress-v2p-ca9.dtb -append
"console=ttyAMA0,115200 kgdbo
may be adding media=disk to the drive definition : -drive
if=none,format=raw,file=disk.img,media=disk
otherwise, are you sure you packed the right stuff to detect the disc?
Le ven. 3 avr. 2020 à 07:28, a écrit :
> Hi
>
> I have a working QEMU image emulating an ARM vexpress-a9 and I run it like
12 matches
Mail list logo
