-
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,
>
>
Hello Stefan,
you are right that those are initial latencies,
I just gave those example for highlighting my goals.
I have started reading the ../Virtual/kvm/api. Documentation this is from where
I intent to learn the operation I have printed.
still I am stuck with Asocs' testing libvirtd not allo
On Thu, Aug 18, 2016 at 01:31:19PM +, Nir Levy wrote:
> Daniel, Thanks for your response.
>
> But I have succeeded using simpletrace when building libvirt from source file
> into some/other/dir/install
I can only assume you built libvirt so that qemu runs as root,
instead of an unprivileged
On Thu, Aug 18, 2016 at 1:58 PM, Nir Levy wrote:
> I have a progress in tracing qemu,
> I add the thread and tag done for each kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl
> in purpose of investigating pure hypervisor activity and delays on host.
> the kvm type print only for convenience.
>
> for examp
On Thu, Aug 18, 2016 at 12:58:29PM +, Nir Levy wrote:
> Hello everybody,
>
> I have a progress in tracing qemu,
> I add the thread and tag done for each kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl
> in purpose of investigating pure hypervisor activity and delays on host.
> the kvm type print only
Hello everybody,
I have a progress in tracing qemu,
I add the thread and tag done for each kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl
in purpose of investigating pure hypervisor activity and delays on host.
the kvm type print only for convenience.
for example:
kvm_ioctl 3106435.230545 pid=11347 thre
