Changes between Version 1 and Version 2 of Ticket #12747, comment 6
- Timestamp:
- Mar 9, 2014 2:12:17 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12747, comment 6
v1 v2 1 1 Hi, 2 2 3 final thoughts on this issue: all VMs (i686 and X86_64) are working with the 2 real cores of intel i5-4200U cpu. I made a mistake, assuming: 0=real 1=thread 2=real 3= thread, but the two real cores are 0 and 1 for this Haswell cpu (I am pretty sure that for my old sandy-bridge, it was O and 2).3 final thoughts on this issue: all VMs (i686 and X86_64) are working with the 2 real cores of intel i5-4200U cpu. I made a mistake, assuming: 0=real 1=thread 2=real 3= thread, but the two real cores are 0 and 1. 4 4 5 5 So "taskset -c 0,1 /bin/VirtualBox" is a good workaround (for *this* cpu). … … 7 7 I don't know how VB detects "real" cores, but it seems that it doesn't work well for *this* cpu... 8 8 9 I must also enable NX in the bios, because the taskset by itself is not sufficient to avoid crashes. 10 9 11 Regards,
