WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: CONFIG_CRYPTO_CRC32C_INTEL  (Read 2731 times)

Offline danielibarnes

  • Hero Member
  • *****
  • Posts: 548
CONFIG_CRYPTO_CRC32C_INTEL
« on: August 12, 2009, 05:14:03 PM »
I upgraded my system to a new Dell T5500. However, I discovered that I can no longer boot Tiny Core 2.2 within VMware Server 1.0.9 (TC 1.4.3 works fine). It crashes with the following error text:

invalid opcode: 0000 [#1] SMP
last sysfs file:
Modules linked in:

Pid: 17, comm: cryptomgr_test Not tainted (2.6.29.1-tinycore #1337) VMware Virtual Platform
...
SNIP
...
note: cryptomgr_test[17] exited with preempt_count 1

I traced the problem to the CONFIG_CRYPTO_CRC32C_INTEL kernel config option. The help for this option reads:
Quote
In Intel processor with SSE4.2 supported, the processor will support CRC32C implementation using hardware accelerated CRC32 instruction. This option will create 'crc32c-intel' module, which will enable any routine to use the CRC32 instruction to gain performance compared with software implementation. Module will be crc32c-intel.

When I remove this option, Tiny Core boots perfectly. My shiny new core i7 processor supports this feature. My guess is that the guest OS (Tiny Core) recognizes this when querying the CPU and uses the new hardware accelerated CRC32 instruction, although I'm not sure why since the "processor family" of TC is set to i486. It seems that VMware Server cannot handle this instruction and kills the VM. As far as I can tell, VMware Server 1.0.9 does not allow the masking of CPUID, either. The only "advanced" option available is to disable acceleration, and that doesn't help.

If someone has a better solution, please let me know. Otherwise, this post can serve as a hint to anyone who encounters this problem.
« Last Edit: August 12, 2009, 05:19:00 PM by danielibarnes »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10960
Re: CONFIG_CRYPTO_CRC32C_INTEL
« Reply #1 on: August 15, 2009, 11:11:45 AM »
Has this been reported to VMWare?
The only barriers that can stop you are the ones you create yourself.

Offline danielibarnes

  • Hero Member
  • *****
  • Posts: 548
Re: CONFIG_CRYPTO_CRC32C_INTEL
« Reply #2 on: November 21, 2009, 07:29:07 AM »
Quote
Has this been reported to VMWare?

It is still present in the recent 1.0.10 release, so I posted a note in the VMware 1.0 forum:
http://communities.vmware.com/message/1422791