Hi Thiago,
Your issue probably isn't related to the one I reported [1322441]. My
issue was with automatic NUMA balancing. You could certainly try
disabling numa balancing ( echo 0 > /proc/sys/kernel/numa_balancing )
and enabling KSM again to see if the fault occurs and if the crash is
resolved it
36,id=interface-5264b6d46e53c81719000236,mac=9a:a5:63:64:6f:76,bus=pci.0,addr=0xb
-incoming tcp:0:3004
Thanks
-Matt
-Original Message-
From: Alex Bligh [mailto:a...@alex.org.uk]
Sent: Tuesday, 22 October 2013 5:36 PM
To: Xiexiangyou; Matthew Anderson
Cc: Stefan Hajnoczi; qemu-devel@nongnu.org; Ale
#x27;t seen the problem since.
Thought to share this with you.
Regards
Anders Fudali
--
From: Xiexiangyou [mailto:xiexiang...@huawei.com]
Sent: Tuesday, 8 October 2013 5:39 PM
To: Matthew Anderson
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] BUG: RTC iss
getting a
tyrade of angry phone called every morning that's making me want to go postal.
Thanks
-Matt
-Original Message-
From: fluxion [mailto:fluks...@gmail.com] On Behalf Of mdroth
Sent: Friday, 22 February 2013 6:23 AM
To: Matthew Anderson
Cc: 'qemu-devel@nongnu.org'
If this isn't the correct list just let me know,
I've run into a bug whereby a Windows guest (tested on Server 2008R2 and 2012)
no longer receives RTC ticks when it has been idle for a random amount of time.
HPET is disabled and the guest is running Hyper-V relaxed timers (same
situation withou
start
restart
/usr/bin/kvm
-Original Message-
From: Alexandre DERUMIER [mailto:aderum...@odiso.com]
Sent: Tuesday, 1 May 2012 7:05 PM
To: Gleb Natapov
Cc: Matthew Anderson; qemu-devel@nongnu.org; anth...@codemonkey.ws
Subject: Re: [Q
Thanks for the quick reply,
I pulled the latest version from Git and on first attempt it said the
hv_relaxed feature was not present. I checked the source and the
'hv_relaxed' feature was not included in a 'feature_name' array so the
flag was being discarded before it could be enabled.
Once added
Public bug reported:
I've been having a consistent problem booting 2008R2 guests with 4096MB
of RAM or greater. On the initial boot the KVM process starts out with a
~200MB memory allocation and will use 100% of all CPU allocated to it.
The RES memory of the KVM process slowly rises by around 200m
