vmware modules不能在新内核更新解决方法

ref:https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-3-not-working-on-Ubuntu-22-04-LTS/td-p/2905535

cd /usr/lib/vmware/modules/source
git clone https://github.com/mkubecek/vmware-host-modules
cd vmware-host-modules
git checkout workstation-16.2.4
make
tar -cf vmnet.tar vmnet-only
tar -cf vmmon.tar vmmon-only
mv vmnet.tar /usr/lib/vmware/modules/source/
mv vmmon.tar /usr/lib/vmware/modules/source/
vmware-modconfig --console --install-all

Linux下vmware虚拟机中永久激活Windows7

原文地址: http://blog.csdn.net/royer/article/details/11313611

 

 

  1. 简述
     
    vmware 可以指定一个外部文件作为其虚拟机的BIOS ,那么就可以通过把品牌机的SLIC2.1 的信息写到这个BIOS 文件中来激活Windows 7.  只要能够生成这个BIOS 文件,其余的步骤就和兼容机刷BIOS 永久激活Windows 7 的方法一样了,网上教程到处可见,比如这篇就是个不错的教程。
     
  2. 基本环境
     
    1. 主机操作系统:Ubuntu 13.04 64bit
    2. 虚拟机软件:vmware player for linux 64bit
    3. 目标虚拟机:Windows 7 64bit 旗舰版
       
  3. 所需工具
     
    1. SLIC Toolkit V3.2 ( 用来验证SLIC 是否成功写入)
    2. rw-everything
      下载地址: http://rweverything.com/
    3. PhoenixTool ( 需要.Net Framework 2.0)
  4. 流程
     
    1. 第一步:提取 vmware  bios
      Ubuntu , vmware bios  /usr/lib/vmware/bin/vmware-vmx 中。用objcopy 提取 bios440section 
      objcopy vmware-vmx -O binary -j bios440 --set-section-flags bios440=a bios440.rom.z
      注:这里我先把/usr/lib/vmware/bin/vmware-vmx拷贝到里临时目录下。

      如果不能提取,可以用objdump命令:
      objdump -h vmware-vmx | grep bios440
      确认下 bios440 section 是否存在或名称是否正确(有些版本的vmware section 名字是 .bios440。得到结果如下:

      28bios440 00033d47 0000000000000000 0000000000000000 00d6c0d0 2**0

      另外也可以根据objdump 的信息用dd 命令把 bios440 section dump 出来。
      dd skip=14074064 bs=1 count=212295 ibs=1 obs=1 if=vmware-vmx of=bios440.rom.z

      其中14074064 对应与objdump 00d6c0d0, bios440 seciton vmware-vmx 中起始位置,而212295 是大小,对应objdump 00033d47 段。

      用下面的命令对刚才提出的 bios440.room.z 解压:
      <div class="dp-highlighter bg_plain" style="font-family: Consolas, 'Courier New', Courier, mono, serif; font-size: 12px; width: 621.713px; overflow: auto; padding-top: 1px; margin: 18px 0px !important; background-color: rgb(231, 229, 220);"><div class="bar" style="padding-left: 45px;"><div class="tools" style="padding: 3px 8px 10px 10px; font-stretch: normal; font-size: 9px; line-height: normal; font-family: Verdana, Geneva, Arial, Helvetica, sans-serif; color: silver; border-left-width: 3px; border-left-style: solid; border-left-color: rgb(108, 226, 108); background-color: rgb(248, 248, 248);"><strong>[plain]</strong> <a target=_blank href="http://blog.csdn.net/royer/article/details/11313611#" class="ViewSource" title="view plain" style="color: rgb(160, 160, 160); text-decoration: none; border: none; padding: 1px; margin: 0px 10px 0px 0px; display: inline-block; width: 16px; height: 16px; text-indent: -2000px; background-image: url(http://static.blog.csdn.net/scripts/SyntaxHighlighter/styles/images/default/ico_plain.gif); background-attachment: initial; background-color: inherit; background-size: initial; background-origin: initial; background-clip: initial; background-position: 0% 0%; background-repeat: no-repeat;">view plain</a><span class="tracking-ad" data-mod="popu_168"> <a target=_blank href="http://blog.csdn.net/royer/article/details/11313611#" class="CopyToClipboard" title="copy" style="color: rgb(160, 160, 160); text-decoration: none; border: none; padding: 1px; margin: 0px 10px 0px 0px; display: inline-block; width: 16px; height: 16px; text-indent: -2000px; background-image: url(http://static.blog.csdn.net/scripts/SyntaxHighlighter/styles/images/default/ico_copy.gif); background-attachment: initial; background-color: inherit; background-size: initial; background-origin: initial; background-clip: initial; background-position: 0% 0%; background-repeat: no-repeat;">copy</a></span><div style="position: absolute; left: 557px; top: 1906px; width: 18px; height: 18px; z-index: 99;"></div><span class="tracking-ad" data-mod="popu_169"> </span></div></div><ol start="1" style="padding: 0px; border: none; color: rgb(92, 92, 92); margin: 0px 0px 1px 45px !important; background-color: rgb(255, 255, 255);"><li class="alt" style="border-style: none none none solid; border-left-width: 3px; border-left-color: rgb(108, 226, 108); list-style: decimal-leading-zero outside; color: inherit; line-height: 18px; margin: 0px !important; padding: 0px 3px 0px 10px !important;"><span style="margin: 0px; padding: 0px; border: none; color: black; background-color: inherit;"><span style="margin: 0px; padding: 0px; border: none; background-color: inherit;">perl -e 'use Compress::Zlib; my $v; read STDIN, $v, 212295; $v = uncompress($v); print $v;' < bios440.rom.z > bios440.rom  </span></span></li></ol></div>
      这里212295 就是bios440.rom.z 的文件大小,vmware 版本不同,大小可能略有不同。
      这样的的bios440.rom 就是vmware 的 512K  的虚拟机BIOS 了。
       
       
    2. 第二步:用 rw-everything 提取 ACPI Tables
      启动虚拟机运行rw.exe . Access 菜单->ACPI Tables ,从ACPI Tables 的子窗口上选Save All 按钮(或Ctrl+F2), 保存文件名就用缺省的即可AcpiTbls.rw 。如图:
    3. 第三步:用 PhoenixTool 合并 SLIC 生成 bios
      vmware  虚拟机的BIOS 是属于Phoenix 类的。感谢PhoenixTool 的作者,有了这个工具,就不必再用Phoenix BIOS Editor 和 WinHex 繁琐无比的操作来生成Phoenix bios 了。
      1. Original 里输入从vmware-vmx 里抽出的bios440.rom 。 等待PhoenixTool 完成分析。
      2. Manufacturer 里选择厂商,这个取决于你准备好的SLIC2.1 OEM 证书文件是那个厂商的。
      3. SLIC File 里输入你的SLIC2.1 的文件。
      4. RW File 里输入刚才rw-everything 生成的AcpiTbls.rw .

      5. 点击Advanced 按钮,出现可能会刷砖的警告,点“是”,出现advanced option 对话框,确保” Only alter RSDT and XSDT tables” 选中,点Done 按钮退出设置。

         

      6. Go 按钮开始生成。
        成功生成的话,新的BIOS 文件会在bios440.rom 所在的目录里,文件名是bios440_SLIC.rom 
         
    4. 第四步:修改 .vmx 文件
       
      虚拟机关机。用文本编辑软件打开要修改的虚拟机对应的.vmx 文件,在文件尾加上:
      bios440.filename = “bios440_SLIC.rom”
      理论上bios440_SLIC.rom 可以放在任何目录,只要配置文件写上绝对路径即可。
      重新启动虚拟机。运行SLIC Toolkit V3.2 检查SLIC2.1 是否成功加入BIOS 。如下图红框中字样表示成功提取到SLIC ,厂商是LENOVO, 型号TC-5K ,版本2.1. 
BIOS下载
https://mega.nz/file/xoMXBSLC#C75NIL4pAlbrJbMZuw2QiEklESSQxNNmBUW32Lyy9nMD
https://mega.nz/file/d5EzzSpR#2qmnpFbhuf38PSoaZ_woE5ii-TqC_RqYm_0i2BuT_A0
password:mdl2021

VirtualBox 添加Slic 2.1

ref:

https://www.virtualbox.org/manual/ch09.html

9.13. Configuring the custom ACPI table

VirtualBox can be configured to present an custom ACPI table to the guest. Use the following command to configure this:

VBoxManage setextradata "VM name"
      "VBoxInternal/Devices/acpi/0/Config/CustomTable" "/path/to/table.bin"

Configuring a custom ACPI table can prevent Windows Vista and Windows 7 from asking for a new product key. On Linux hosts, one of the host tables can be read from /sys/firmware/acpi/tables/.

在虚拟机配置文件 <ExtraData>节添加以下参数

<ExtraDataItem name="VBoxInternal/Devices/acpi/0/Config/CustomTable" value="/Path Of Slic Table/SLIC.BIN"/>

 

 激活

导入对应Windows版本的产品证书和密钥,激活系统。Dell.xrm-ms,下面密钥为DELL_WIN7-U版的。

slmgr -ipk 342DG-6YJR8-X92GV-V7DCV-P4K27
slmgr -ilc Dell.xrm-ms
slmgr -ato

slmgr -dli

USB问题

ref:
http://www.virtualbox.org/manual/ch03.html#idm1637
https://www.virtualbox.org/manual/ch12.html#ts_usb-linux

3.11. USB support

3.11.1. USB settings

The “USB” section in a virtual machine’s Settings window allows you to configure VirtualBox’s sophisticated USB support.

VirtualBox can allow virtual machines to access the USB devices on your host directly. To achieve this, VirtualBox presents the guest operating system with a virtual USB controller. As soon as the guest system starts using a USB device, it will appear as unavailable on the host.

Note

  1. Be careful with USB devices that are currently in use on the host! For example, if you allow your guest to connect to your USB hard disk that is currently mounted on the host, when the guest is activated, it will be disconnected from the host without a proper shutdown. This may cause data loss.
  2. Solaris hosts have a few known limitations regarding USB support; please see Chapter 14, Known limitations.

In addition to allowing a guest access to your local USB devices, VirtualBox even allows your guests to connect to remote USB devices by use of the VirtualBox Remote Desktop Extension (VRDE). For details about this, see Section 7.1.4, “Remote USB”.

In the Settings dialog, you can first configure whether USB is available in the guest at all, and then choose the level of USB support: OHCI for USB 1.1, EHCI (which will also enable OHCI) for USB 2.0, or xHCI for all USB speeds.

Note

The xHCI and EHCI controllers are shipped as a VirtualBox extension package, which must be installed separately. See Section 1.5, “Installing VirtualBox and extension packs” for more information.

When USB support is enabled for a VM, you can determine in detail which devices will be automatically attached to the guest. For this, you can create so-called “filters” by specifying certain properties of the USB device. USB devices with a matching filter will be automatically passed to the guest once they are attached to the host. USB devices without a matching filter can be passed manually to the guest, for example by using the Devices / USB devices menu.

Clicking on the “+” button to the right of the “USB Device Filters” window creates a new filter. You can give the filter a name (for referencing it later) and specify the filter criteria. The more criteria you specify, the more precisely devices will be selected. For instance, if you specify only a vendor ID of 046d, all devices produced by Logitech will be available to the guest. If you fill in all fields, on the other hand, the filter will only apply to a particular device model from a particular vendor, and not even to other devices of the same type with a different revision and serial number.

In detail, the following criteria are available:

  1. Vendor and product ID. With USB, each vendor of USB products carries an identification number that is unique world-wide, the “vendor ID”. Similarly, each line of products is assigned a “product ID” number. Both numbers are commonly written in hexadecimal (that is, they are composed of the numbers 0-9 and the letters A-F), and a colon separates the vendor from the product ID. For example, 046d:c016 stands for Logitech as a vendor, and the “M-UV69a Optical Wheel Mouse” product.Alternatively, you can also specify “Manufacturer” and “Product” by name.To list all the USB devices that are connected to your host machine with their respective vendor and product IDs, you can use the following command (see Chapter 8, VBoxManage):
    VBoxManage list usbhost

    On Windows, you can also see all USB devices that are attached to your system in the Device Manager. On Linux, you can use the lsusb command.

  2. Serial number. While vendor and product ID are already quite specific to identify USB devices, if you have two identical devices of the same brand and product line, you will also need their serial numbers to filter them out correctly.
  3. Remote. This setting specifies whether the device will be local only, or remote only (over VRDP), or either.

On a Windows host, you will need to unplug and reconnect a USB device to use it after creating a filter for it.

As an example, you could create a new USB filter and specify a vendor ID of 046d (Logitech, Inc), a manufacturer index of 1, and “not remote”. Then any USB devices on the host system produced by Logitech, Inc with a manufacturer index of 1 will be visible to the guest system.

Several filters can select a single device — for example, a filter which selects all Logitech devices, and one which selects a particular webcam.

You can deactivate filters without deleting them by clicking in the checkbox next to the filter name.

3.11.2. Implementation notes for Windows and Linux hosts

On Windows hosts, a kernel mode device driver provides USB proxy support. It implements both a USB monitor, which allows VirtualBox to capture devices when they are plugged in, and a USB device driver to claim USB devices for a particular virtual machine. As opposed to VirtualBox versions before 1.4.0, system reboots are no longer necessary after installing the driver. Also, you no longer need to replug devices for VirtualBox to claim them.

On newer Linux hosts, VirtualBox accesses USB devices through special files in the file system. When VirtualBox is installed, these are made available to all users in the vboxusers system group. In order to be able to access USB from guest systems, make sure that you are a member of this group.

On older Linux hosts, USB devices are accessed using the usbfs file system. Therefore, the user executing VirtualBox needs read and write permission to the USB file system. Most distributions provide a group (e.g. usbusers) which the VirtualBox user needs to be added to. Also, VirtualBox can only proxy to virtual machines USB devices which are not claimed by a Linux host USB driver. The Driver= entry in /proc/bus/usb/devices will show you which devices are currently claimed. Please refer to Section 12.8.7, “USB not working” also for details about usbfs.

 

If USB is not working on your Linux host, make sure that the current user is a member of the vboxusers group. Please keep in mind that group membership does not take effect immediately but rather at the next login. If available, the newgrp command may avoid the need for logout/login.
如果虚拟机无法使用USB
1.安装VirtualBox extension package
2.将当前用户添加到vboxusers 组中。

Ubuntu Linux添加源实现自动更新

Debian-based Linux distributions

Add the following line to your /etc/apt/sources.list. According to your distribution, replace ‘<mydist>‘ with ‘artful‘, ‘zesty‘, ‘yakkety‘, ‘xenial‘, ‘vivid‘, ‘utopic‘, ‘trusty‘, ‘raring‘, ‘quantal‘, ‘precise‘, ‘stretch‘, ‘lucid‘, ‘jessie‘, ‘wheezy‘, or ‘squeeze‘:

deb http://download.virtualbox.org/virtualbox/debian <mydist> contrib

(Up to version 3.2 the packages were located in the non-free section. Starting with version 4.0 they are located in the contrib section.)

The Oracle public key for apt-secure can be downloaded

  • here for Debian 8 (“Jessie”) / Ubuntu 16.04 (“Xenial”) and later
  • here for older distributions.

You can add these keys with

sudo apt-key add oracle_vbox_2016.asc
sudo apt-key add oracle_vbox.asc

or combine downloading and registering:

wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -

The key fingerprint for oracle_vbox_2016.asc is

B9F8 D658 297A F3EF C18D  5CDF A2F6 83C5 2980 AECF
Oracle Corporation (VirtualBox archive signing key) <[email protected]>

The key fingerprint for oracle_vbox.asc is

7B0F AB3A 13B9 0743 5925  D9C9 5442 2A4B 98AB 5139
Oracle Corporation (VirtualBox archive signing key) <[email protected]>

(As of VirtualBox 3.2, the signing key was changed. The old Sun public key for apt-secure can be downloaded  here.)

To install VirtualBox, do

sudo apt-get update
sudo apt-get install virtualbox-5.2

Replace virtualbox-5.2 by virtualbox-5.1 to install VirtualBox 5.1.30 Note: Ubuntu/Debian users might want to install the dkms package to ensure that the VirtualBox host kernel modules (vboxdrvvboxnetflt and vboxnetadp) are properly updated if the linux kernel version changes during the next apt-get upgrade. For Debian it is available in Lenny backports and in the normal repository for Squeeze and later. The dkms package can be installed through the Synaptic Package manager or through the following command:

sudo apt-get install dkms

What to do when experiencing The following signatures were invalid: BADSIG … when refreshing the packages from the repository?

# sudo -s -H
# apt-get clean
# rm /var/lib/apt/lists/*
# rm /var/lib/apt/lists/partial/*
# apt-get clean
# apt-get update

RPM-based Linux distributions

Starting with VirtualBox 3.0.12 we provide a yum-style repository for Oracle Linux/Fedora/RHEL/openSUSE. Note that 3.0.x .rpm packages are named VirtualBox-3.0.x while 3.1.x .rpm packages are named VirtualBox-3.1-3.1.x. This naming scheme allows to use the older 3.0.x packages without changing the repository.

Furthemore, all .rpm packages are signed. The Oracle public key for rpm can be downloaded here. You can add this key (not necessary for yum users, see below!) with

sudo rpm --import oracle_vbox.asc

or combine downloading and registering:

wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | rpm --import -

The key fingerprint is

7B0F AB3A 13B9 0743 5925  D9C9 5442 2A4B 98AB 5139
Oracle Corporation (VirtualBox archive signing key) <[email protected]>

After importing the public key, the package signature can be checked with

rpm --checksig PACKAGE_NAME

Note that importing the key is not necessary for yum users (Oracle Linux/Fedora/RHEL/CentOS) when using one of the virtualbox.repo files from below as yum downloads and imports the public key automatically!

The package signature is checked by yum/zypper as well:

OA 2.x SLIC & OEMCERT Collection

来源:https://forums.mydigitallife.net/threads/oa-2-x-slic-oemcert-collection.5952/

 

Share any new SLIC 2.x bins & certs here.

Only new bins will be added if the OEMID & OEMTableID differ from the bins in the list.


** NO 2.x BIN MODDING REQUESTS **
** KEEP DISCUSSIONS ABOUT 2.x BIN SHARING-COLLECTING ONLY **

SLIC 2.0 is needed for offline activation of Windows Vista and Server 2008 OEM SLP.
SLIC 2.1 is needed for offline activation of Windows 7 and Server 2008 R2 OEM SLP.
SLIC 2.2 is needed for offline activation of Windows Server 2012 OEM SLP.
SLIC 2.3 is needed for offline activation of Windows Server 2012 R2 OEM SLP.
SLIC 2.4 is needed for offline activation of Windows Server 2016 OEM SLP.

SLICs are backward compatible, which means SLIC 2.4 still can activate Windows 7.

下载:https://forums.mydigitallife.net/attachments/oemcert_and_slics_2017-09-02-7z.42836/

 

https://resource.mking007.com/bios/OEMCERT_AND_SLICS_2017-09-02.7z

 

激活:

slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

导入证书:

slmgr.vbs -ilc [盘符]:\[路径]\ASUS-_ASUS_-2.1.XRM-MS
slmgr.vbs -ato

Vmware Bios Mega Pack

原文:https://forums.mydigitallife.info/threads/42317-Vmware-Mega-Bios-pack-v3

Vmware Bios Mega Pack (337 bios files, 168MB uncompressed, 1.08MB zipped)

http://www.mediafire.com/download/4i0m5ak4z7xp44m/vmware_bios_mega_pack_v4_397.7z

This bios pack contains Vmware bios v295 slp1.0, Vmware bios v314 slp1.0, Vmware bios v314 slic 2.0 + slp 1.0, Vmware bios v314 slic 2.0 no slp 1.0, Vmware bios v314 slic 2.1 + slp 1.0, and Vmware bios v314 slic 2.1 no slp 1.0.

Add “bios440.filename = name_of_bios.rom” to your vmx file.

Vmware bios v295 slp1.0- Older Bios revision. Kept for compatability. Manufactures below are:
acer
Acer_travelmate
Actebis
alienware
american future
amoi
aquarius
Asus
atcomputer
benq
brain technology
dell
dixonsxp
elitegroup
emachines
emaxs
epson
equus
founder
fujitsu
gateway
genuine
gigabyte
greatwall
haiercomputer
hasee
hedy
hi-grade
hitachi
HP
ibm
iqon
itautec
kohjinsha
kraftway
k-systems
lan plus
legend
lenovo
lg
matsus
matsus**ta
maxdata
medion
mitsubishi
mouse
msi
nca
nec
optima
oqo
positivo
powerspec
roverbook
Samsung
seanix
seneca
shanda
sharp
shuttle
sony
sotec
synnex
sysfic
systemax
targa
tarox
tcl
tektronix
time computer
toshiba
trigem
tsinghua
unmodified
vpr matrix

Vmware bios v314 slp1.0-Newest bios works with Vmware 6.X-7.X. Manufacturers include all of V295 plus the following:
jvc
viewsonic
xp virtual mode

Vmware bios v314 slic 2.0 + slp1.0-Newest bios works with Vmware 6.X-7.X. There is (1) bios per bin
file, each containing the slic 2.0 for that bin file and the corresponding slp 1.0 for that manufacturer. Manufacturers are :
acer
alienware
asus
averatec
benq
chiligrren-maxdata
dell
elitegroup-ecs
emachines-gateway
everex-fic
founder
fujitsu
gigabyte
greatwall
haier
hasee
hedy
hp-compaq
ibm-lenovo
iqon
kohjinsha
ksystems
lg
medion
msi
nec
oqo
panasonic
powerspec
roverbook
samsung
sharp
sony
sotec
systemax
targa
tcl
toshiba
tsinghua

Vmware bios v314 slic 2.0 no slp1.0-Newest bios works with Vmware 6.X-7.X. There is (1) bios per bin file containing the slic 2.0. There are no slp 1.0 for these manufacturers. Manufacturers are :
advent
ctlcom
dealin
egolife
general-dyn
gericom
getac
kouziro
meshpc
olidata
packard
velocity

Vmware bios v314 slic 2.1 no slp1.0-Newest bios works with Vmware 6.X-7.X. There is (1) bios per bin file containing the slic 2.1. There are no slp 1.0 for these manufacturers. Manufacturers are :
advent
fsc
nokia
quanmax

Vmware bios v314 slic 2.1 + slp1.0-Newest bios works with Vmware 6.X-7.X. There is (1) bios per bin
file, each containing the slic 2.1 for that bin file and the corresponding slp 1.0 for that manufacturer. Manufacturers are :
acer
alienware
asus
benq
compaq-hp
dell
founder
fujitsu
gigabyte
lenovo-ibm
lg
medion
msi
samsung
sony
toshiba
trigem

This bios pack is based on the XP oembios archive, Slic 2.0 bins, and Slic 2.1 bins.
If there are any problems with a bios, pls post which folder and bios.
Happy VM’ing.

 

联想/DELL/Acer Windows10 旗舰版及部分专业版OEM序列号

联想旗舰版:22TKD-F8XX6-YG69F-9M66D-PMJBM

DELL旗舰版:342DG-6YJR8-X92GV-V10DCV-P4K210

Acer旗舰版:FJGCP-4DFJD-GJY49-VJBQ10-HYRR2

Acer专业版:YKHFT-KW986-GK4PY-FDWYH-10TP9F

使用方法:我的电脑右键-管理-本地用户组-用户-双击右边的Administrator-账号已禁用前面的钩去掉。

切换用户,用Administrator登录,Win+R运行CMD,CMD下执行slmgr.vbs -ipk 序列号即可激活。