The changes to the create table command are documented in “Creating a virtually-hashed table”.
dbcc checktable – in addition to the regular checks it performs, checktable verifies that the layout of data and OAM pages in the hash region is correct.
Data pages are not allocated in an extent reserved for OAM pages as per the layout.
The OAM pages are allocated only in the first extent of an allocation unit (AU)
dbcc checkstorage – reports a soft fault if any data page that is not the first data page is empty for non-hashed tables. However, dbcc checkstorage does not report this soft fault for the hashed region of a virtually-hashed table. Any data page in the hashed region of a virtually-hashed table can be empty.