On Wed, Feb 4, 2015 at 3:06 AM, Nerijus Baliunas
neri...@users.sourceforge.net wrote:
On Tue, 3 Feb 2015 18:07:57 +0400 Andrey Korolyov and...@xdel.ru wrote:
Have you tried to disable turbo mode (assuming you have new enough CPU
model) and fix frequency via frequency governor` settings? If it
On 03/02/2015 14:25, Nerijus Baliunas wrote:
It did not help. Today that commecrial application detects 2400, although
Control Panel - System shows 2.20 GHz.
So my question again - is it possible to patch qemu-kvm that it shows some
constant frequency to the guest? But the answer is probably
It did not help. Today that commecrial application detects 2400, although
Control Panel - System shows 2.20 GHz.
So my question again - is it possible to patch qemu-kvm that it shows some
constant frequency to the guest? But the answer is probably not, because
I don't know how the application
it detects
CPU frequency change (2200 - 2298 in above case). Is it possible to patch
qemu-kvm that it shows some constant frquency to the guest?
Do you know how the application computes the frequency?
In the case of Windows it's probably some timing loop that is executed
at startup
On Tue, 3 Feb 2015 18:07:57 +0400 Andrey Korolyov and...@xdel.ru wrote:
Have you tried to disable turbo mode (assuming you have new enough CPU
model) and fix frequency via frequency governor` settings? If it
helps, it can be an ugly hack with pre-up/post-up libvirt actions,
though you`d
Nerijus Baliunas nerijus at users.sourceforge.net writes:
Paolo Bonzini pbonzini at redhat.com writes:
In the case of Windows it's probably some timing loop that is executed
at startup, and the result depends on frequency scaling in the host.
Try adding this to the XML in the meanwhile,
,
078BFBFD000206A1, 10753, CPU 0
Windows Server 2012 Control Panel - System shows CPU as 2.3 GHZ, but after
reboot it might show 2.2 or 1.97 GHz.
The problem is, that commercial application stops working after it detects
CPU frequency change (2200 - 2298 in above case). Is it possible to patch
qemu-kvm
Family 6 Model 42 Stepping 1, 64, 64, 2298,
078BFBFD000206A1, 10753, CPU 0
Windows Server 2012 Control Panel - System shows CPU as 2.3 GHZ, but after
reboot it might show 2.2 or 1.97 GHz.
The problem is, that commercial application stops working after it detects
CPU frequency change
Paolo Bonzini pbonzini at redhat.com writes:
How are you running qemu-kvm? (Command line, or XML if you're using
libvirt, or similar).
XML - http://paste.fedoraproject.org/162378/14193357
command line - http://paste.fedoraproject.org/162379/93358231
--
To unsubscribe from this list: send the
,
078BFBFD000206A1, 10753, CPU 0
Windows Server 2012 Control Panel - System shows CPU as 2.3 GHZ, but after
reboot it might show 2.2 or 1.97 GHz.
The problem is, that commercial application stops working after it detects
CPU frequency change (2200 - 2298 in above case). Is it possible to patch
qemu
Paolo Bonzini pbonzini at redhat.com writes:
Do you know how the application computes the frequency?
No.
In the case of Windows it's probably some timing loop that is executed
at startup, and the result depends on frequency scaling in the host.
Try adding this to the XML in the meanwhile,
.
Another guest (Ubuntu in native qcow2 image) works fine and reports
correct cpu frequency, so I only see this problem with this particular
.vmdk image.
I’m running
QEMU emulator version 0.15.1 (kvm-0.15.1-0.17.3), Copyright (c)
2003-2008 Fabrice Bellard
on SLES11-SP2 host (3.0
lockups that you can recommend?
What probably was suggested is to disable cpu frequency scaling on the
host. Please provide more details on the host system.
Host is a Quadcore Xeon HP DL320 G5 with CentOS 5.4, old Kernel
2.6.18-128.7.1.el5.
There are no hints toward CPU scaling in /sys
Marcelo Tosatti schrieb:
Can you please share a few more soft lockup messages? (with
backtrace included).
Full dmesg from guest: http://pastebin.com/f51a966df
Also qemu command line.
From ps:
/usr/local/kvm/bin/qemu-system-x86_64 -hda /drbd/vweb/vweb.vmdk -vnc
127.0.0.1:4 -m 512 -net
On Wed, Jan 06, 2010 at 09:15:02AM +0100, Martin Schmitt wrote:
Marcelo Tosatti schrieb:
Can you please share a few more soft lockup messages? (with
backtrace included).
Full dmesg from guest: http://pastebin.com/f51a966df
Also qemu command line.
From ps:
Marcelo Tosatti schrieb:
Hum, can you try converting that vmdk image to qcow2 or raw? (with
qemu-img convert).
AFAICS the QEMU vmdk implementation is synchronous, so the guest
waits on IO operations to complete on the host side.
I'll do so, but I can only make the conversion early morning
scaling in KVM guests? Or is there any other measure against these soft
lockups that you can recommend?
What probably was suggested is to disable cpu frequency scaling on the
host. Please provide more details on the host system.
--
To unsubscribe from this list: send the line unsubscribe kvm
17 matches
Mail list logo
