Hi,
we are running some stopped (sending "stop" via kvm-monitor socket)
vm's on our system. My intention was to pause (stop) the vm's and
unpause (cont) them on demand (very fast, without time delay, within 2
seconds ..).
After 'stop'ing, the vm's still using CPU-load, like the "top" will
tell:
One more,
> So, how can I prevent the paused/stopped VM's to use my CPU from
> the hostsystem ? Is there a way to handle this ?
If i send a signal STOP/CONT (kill -STOP or kill -CONT )
to the KVM-process, it looks like the kvm does not (sure ;-) use
any host CPU usage.
- Are there some side eff
On 10/01/2009 12:32 PM, Daniel Schwager wrote:
Hi,
we are running some stopped (sending "stop" via kvm-monitor socket)
vm's on our system. My intention was to pause (stop) the vm's and
unpause (cont) them on demand (very fast, without time delay, within 2
seconds ..).
After 'stop'ing, the vm's
On 10/01/2009 01:47 PM, Daniel Schwager wrote:
If i send a signal STOP/CONT (kill -STOP or kill -CONT)
to the KVM-process, it looks like the kvm does not (sure ;-) use
any host CPU usage.
- Are there some side effects using this approach ?
(e.g. with networking, ...)
The monitor, vnc,
> > After 'stop'ing, the vm's still using CPU-load, like the "top" will
tell
> >
> >PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+
COMMAND
> > 25983 root 20 0 495m 407m 1876 R 8.9 2.5 228:09.15
qemu-system-x86
> It shouldn't do that.
ok.
> How long is this after the 's
On 10/04/2009 05:21 PM, Daniel Schwager wrote:
How long is this after the 'stop'?
30 seconds or 2 days ... the process takes CPU all the time
Can you take an oprofile run to see where it's spending its time?
--
error compiling committee.c: too many arguments to function
--
To uns
> On 10/04/2009 05:21 PM, Daniel Schwager wrote:
> >
> >> How long is this after the 'stop'?
> >>
> > 30 seconds or 2 days ... the process takes CPU all the time
> >
>
> Can you take an oprofile run to see where it's spending its time?
I'm not that familiar with oprofile ...
so, setup with
On 10/17/2009 06:35 AM, Daniel Schwager wrote:
I'm not that familiar with oprofile ...
so, setup with
opcontrol --deinit; modprobe oprofile timer=1; opcontrol --start
gave me the following result:
kvm03:~# opreport
Use 'opreport -l'. Make sure your qemu isn't stripped.
Try to
> > so, setup with
> > opcontrol --deinit; modprobe oprofile timer=1; opcontrol --start
> >
> Use 'opreport -l'. Make sure your qemu isn't stripped.
ok ... will do
>
> > Try to start without timer=1 hung up my physical machine after daemon is
> > started:
>
> Is there an oops in dmesg, o
> > > so, setup with
> > > opcontrol --deinit; modprobe oprofile timer=1; opcontrol --start
> > >
>
> > Use 'opreport -l'. Make sure your qemu isn't stripped.
Build kvm-86 with "./configure ... --disable-strip"
and paused vm, now I got:
opreport -l
CPU: CPU with timer interrupt, speed 0 MHz
On 10/19/2009 03:47 AM, Daniel Schwager wrote:
Build kvm-86 with "./configure ... --disable-strip"
and paused vm, now I got:
opreport -l
CPU: CPU with timer interrupt, speed 0 MHz (estimated)
Profiling through timer interrupt
samples %image name app name
symbol name
11218
Hi Avi,
> > > > so, setup with
> > > > opcontrol --deinit; modprobe oprofile timer=1; opcontrol
--start
> > > >
> >
> > > Use 'opreport -l'. Make sure your qemu isn't stripped.
All VM's are in paused state:
top - 22:08:15 up 2 days, 12:18, 8 users, load average: 0.12, 0.19,
0.14
Tasks
On 10/21/2009 10:29 PM, Daniel Schwager wrote:
opreport -l --symbols | less
CPU: CPU with timer interrupt, speed 0 MHz (estimated)
Profiling through timer interrupt
samples %image name app name
symbol name
418814 98.5250 no-vmlinux no-vmlinux
13 matches
Mail list logo
