-
From: Daniel P. Berrange [mailto:berra...@redhat.com]
Sent: Thursday, August 18, 2016 4:11 PM
To: Nir Levy
Cc: qemu-devel@nongnu.org; Stefan Hajnoczi
Subject: Re: [Qemu-devel] errno 13, fopen qemu trace file.
On Thu, Aug 18, 2016 at 12:58:29PM +, Nir Levy wrote:
> Hello everybody,
>
>
d not allowing me to open the trace
file
Regards,
Nir,
-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
Sent: Thursday, August 18, 2016 4:22 PM
To: Nir Levy
Cc: qemu-devel@nongnu.org
Subject: Re: errno 13, fopen qemu trace file.
On Thu, Aug 18, 2016 at 1:58 PM, Nir
ue it will be great.
regards.
Nir Levy
SW Engineer
Nir Levy
SW Engineer
Web: www.asocstech.com<http://www.asocstech.com/> |
[cid:image001.jpg@01D1B599.5A2C9530]
, 2016 6:11 PM
To: Nir Levy
Cc: qemu-devel@nongnu.org; Yan Fridland
Subject: Re: [Qemu-devel] QEMU-guestOS latencies.
On Thu, Jul 28, 2016 at 09:25:41AM +, Nir Levy wrote:
> in addition I wish to understand ram allocation and avoid host swaps.
I didn't read everything but this stood ou
After changing the
inside function qemuMonitorOpenUnix
int timeout to MAX_INT;
in file: ./src/qemu/qemu_monitor.c (libvirt)
I am now able to debug kvm and malloc
I would love hearing some tips regarding tracing for latencies.
regards,
Nir.
From: Nir Levy
Sent: Thursday, July 28, 2016 12:25 PM
ies of guest OS related?
Regards and many thanks.
Nir Levy
SW Engineer
Web: www.asocstech.com<http://www.asocstech.com/> |
[cid:image001.jpg@01D1B599.5A2C9530]
