Re: VM Ware Player under Debian Lenny AMD64 on laptop
On Fri, Jul 24, 2009 at 1:48 PM, James Brown<jbrownfirst@gmail.com> wrote:
> Lennart Sorensen wrote:
>> On Fri, Jul 24, 2009 at 09:47:07PM +0400, James Brown wrote:
>>
>>
>> Another option is qemu using kqemu. Not quite as fast as kvm, but still
>> very good and the same feature set. kqemu is probably about the speed
>> of vmware.
>>
> Is it possible install on qemu Windows? It seems to me that only Linux,
> am I wrong?
> Does it maintain booting from raw disks and using USB?
>
>> What CPU do you have? What does /proc/cpuinfo say?
>>
>>
> dmesg | grep CPU
> [ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
> [ 0.000000] PERCPU: Allocating 37168 bytes of per cpu data
> [ 0.000000] NR_CPUS: 32, nr_cpu_ids: 2
> [ 0.000000] Initializing CPU#0
> [ 0.088005] CPU: L1 I cache: 32K, L1 D cache: 32K
> [ 0.088005] CPU: L2 cache: 2048K
> [ 0.088005] CPU 0/0 -> Node 0
> [ 0.088005] CPU: Physical Processor ID: 0
> [ 0.088005] CPU: Processor Core ID: 0
> [ 0.088005] CPU0: Thermal monitoring enabled (TM2)
> [ 0.148009] CPU0: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz stepping 06
> [ 0.160010] Initializing CPU#1
> [ 0.160010] CPU: L1 I cache: 32K, L1 D cache: 32K
> [ 0.160010] CPU: L2 cache: 2048K
> [ 0.160010] CPU 1/1 -> Node 0
> [ 0.160010] CPU: Physical Processor ID: 0
> [ 0.160010] CPU: Processor Core ID: 1
> [ 0.160010] CPU1: Thermal monitoring enabled (TM2)
> [ 0.240015] CPU1: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz stepping 06
> [ 0.240015] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
> [ 0.244015] Brought up 2 CPUs
> [ 0.244015] CPU0 attaching sched-domain:
> [ 0.244015] CPU1 attaching sched-domain:
> [ 1.218889] Switched to high resolution mode on CPU 0
> [ 1.220287] Switched to high resolution mode on CPU 1
> [ 2.094903] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
> [ 2.094903] ACPI: Processor [CPU0] (supports 8 throttling states)
> [ 2.095115] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
> [ 2.095115] ACPI: Processor [CPU1] (supports 8 throttling states)
> [ 89.452525] CPU0 attaching NULL sched-domain.
> [ 89.452536] CPU1 attaching NULL sched-domain.
> [ 89.466722] CPU0 attaching sched-domain:
> [ 89.466753] CPU1 attaching sched-domain:
> [ 8910.407330] CPU0 attaching NULL sched-domain.
> [ 8910.407340] CPU1 attaching NULL sched-domain.
> [ 8910.428628] CPU0 attaching sched-domain:
> [ 8910.428648] CPU1 attaching sched-domain:
>
>
> $ cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz
> stepping : 6
> cpu MHz : 1000.000
> cache size : 2048 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 2
> apicid : 0
> initial apicid : 0
> 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 pni monitor ds_cpl est tm2
> ssse3 cx16 xtpr lahf_lm
> bogomips : 3337.60
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz
> stepping : 6
> cpu MHz : 1000.000
> cache size : 2048 KB
> physical id : 0
> siblings : 2
> core id : 1
> cpu cores : 2
> apicid : 1
> initial apicid : 1
> 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 pni monitor ds_cpl est tm2
> ssse3 cx16 xtpr lahf_lm
> bogomips : 3333.60
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
>
>
> --
> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Acording to this your processor might or might not support
virtualization using kvm:
http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Core_2_Duo_2
I think you can stick with vmware server.
--
Usuario Linux Registrado #452368
Usuario Ubuntu Registrado #28025
"Doing a thing well is often a waste of time."
----------------------------------------------------------------------------------------------------------------------------------
//Netbook - HP Mini 1035NR 2GB 60GB - Windows XP/Ubuntu 9.04
//Desktop - Core 2 Duo 1.86Ghz 8GB 500GB - Windows 7(testing)
//Desktop - Core 2 Duo 2.40Ghz 8GB 320GB - MacOS Leopard
//Desktop - Athlon 64 2.7Ghz 8GB 400GB - Ubuntu Jaunty
//Server - Pentium D 3.2Ghz 8GB 1TB - Debian Lenny
//Server - Celeron 1.8Ghz 1GB 160GB - Pfsense
//Server - NSLU2 266Mhz 32MB 1TB - Debian Lenny
Reply to: