Re: qemu-kvm-0.13.0 - winsows 2008 - chkdisk too slow

[Nikola Ciprich <extmaillist@linuxbox.cz>]

> What are the differences between the host the completes chkdsk and the  
> host that fails?  Hardware-wise and software-wise.
Software-wise, I'm not aware of any, both nodes use:
- kernel 2.6.36.2
- qemu-kvm-0.13.0
- seabios-0.6.0

hardware-wise, problematic machine is older 8core, 16GB RAM,
cpuinfo snippet:

processor      : 7
vendor_id      : GenuineIntel
cpu family     : 6
model	       	 : 15
model name	 : Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz
stepping	 : 7
cpu MHz		   : 1599.873
cache size	   : 4096 KB
physical id	   : 1
siblings : 4
core id	   : 3
cpu cores  : 4
apicid	     : 7
initial apicid : 7
fpu	       : yes
fpu_exception  : yes
cpuid level    : 10
wp    	       : yes
flags	       	 : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm dts tpr_shadow
bogomips	 : 3200.27
clflush size	 : 64
cache_alignment	 : 64
address sizes	 : 36 bits physical, 48 bits virtual

nonproblematic machine is 8core 4GB, cpuinfo snippet:
processor      : 7
vendor_id      : GenuineIntel
cpu family     : 6
model	       	 : 30
model name	 : Intel(R) Xeon(R) CPU           X3440  @ 2.53GHz
stepping	 : 5
cpu MHz		   : 2533.260
cache size	   : 8192 KB
physical id	   : 0
siblings : 8
core id	   : 3
cpu cores  : 4
apicid	     : 7
initial apicid : 7
fpu	       : yes
fpu_exception  : yes
cpuid level    : 11
wp    	       : yes
flags	       	 : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
bogomips	 : 5066.35
clflush size	 : 64
cache_alignment	 : 64
address sizes	 : 36 bits physical, 48 bits virtual

important to note is, that botch machines are failover clusters, I can reproduce even on second node
of "problematic" cluster, although CPU is a bit different, snippet follows:
processor	 : 7
vendor_id	 : GenuineIntel
cpu family	 : 6
model		   : 23
model name	   : Intel(R) Xeon(R) CPU           E5420  @ 2.50GHz
stepping	   : 6
cpu MHz		     : 2500.038
cache size	     : 6144 KB
physical id	     : 1
siblings : 4
core id	   : 3
cpu cores  : 4
apicid	     : 7
initial apicid : 7
fpu	       : yes
fpu_exception  : yes
cpuid level    : 10
wp    	       : yes
flags	       	 : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dts tpr_shadow vnmi flexpriority
bogomips	 : 5000.40
clflush size	 : 64
cache_alignment	 : 64
address sizes	 : 38 bits physical, 48 bits virtual

What else could I check?
n.


>
> -- 
> error compiling committee.c: too many arguments to function
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------