On Wed, 24 Aug 2022 00:54:48 +0530 Prasad Pandit <ppandit@xxxxxxxxxx> wrote: > Hello Steve, > > On Sat, 20 Aug 2022 at 14:51, Prasad Pandit <ppandit@xxxxxxxxxx> wrote: > >> # trace-cmd agent > > * For me `trace-cmd agent` in the guest shows => listening on @4294967295:823 I need to fix that to be more meaningful. That 4294967295 is (unsigned)-1. In other words, the creation of the vsocket failed It means that you do not have vsockets defined for this guest, or you are running inside a container on the guest that prevents you from accessing the vsockets. > > >> # trace-cmd record --poll -M 1E -e all --proxy 2 --name host -e kvm -e sched -e irq /home/test/rt-tests/oslat --cpu-list 1-4 --rtprio 1 --duration 12h -T 30 > > * Running above command with --proxy 4294967295:823 throws an error => > guest 4294967295 not found The rest will not work because the vsocket failed. -- Steve
|