summary refs log tree commit diff stats
path: root/results/classifier/108/other/864490
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/108/other/864490')
-rw-r--r--results/classifier/108/other/86449034
1 files changed, 34 insertions, 0 deletions
diff --git a/results/classifier/108/other/864490 b/results/classifier/108/other/864490
new file mode 100644
index 000000000..64c10b51f
--- /dev/null
+++ b/results/classifier/108/other/864490
@@ -0,0 +1,34 @@
+device: 0.802
+other: 0.786
+graphic: 0.755
+performance: 0.708
+semantic: 0.614
+permissions: 0.593
+PID: 0.568
+socket: 0.557
+debug: 0.554
+files: 0.544
+boot: 0.531
+vnc: 0.510
+network: 0.472
+KVM: 0.277
+
+Windows 2008 x64 (SBS Server) freezes randomly when using more than 1 CPU core
+
+This issue has been giving headache to us since a long time.
+Difficult to reproduce as it happens randomly.
+We had this issue when we ran Windows 2008 x64 or Windows SBS Server guests in either XEN 3.3 or Proxmox environments.
+When only one CPU core is assigned to the guest, everything is fine. If 2 or more cores are assigned, the guest stops responding after several hours - and in the host machine one of the cores is using 100%. The only thing that helps is resetting the guest.
+
+I am ready to provide logs/crashdumps if needed, because we want to help resolve this issue. I saw some posts on the web of people having the same problems - for some of the workaround was to fix some BIOS settings, but we did not have success with those (e.g. disabling C1E Support and Intel C-State )
+
+Server is running on Intel® Core™ i7-920 Quad-Core, 24 Gig RAM.
+
+Hi,
+
+Is this bug tracker active or I posted to the wrong place?
+
+thx
+
+Since nobody replied here within the last years: I think you should rather report problems with XEN / Proxmox to the XEN or Proxmox bugtracker instead.
+