Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

When Secure Boot is enabled, X server will fail to start on Linux VMs using a kernel older than v3.2 (52253)

Last Updated: 3/6/2018Categories: TroubleshootingTotal Views: 6093Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When Secure Boot is enabled, X server will fail to start on Linux VMs using a kernel older than v3.2.

Cause

The vmwgfx kernel mode driver is required for secure-boot enabled VMs. VMware enabled the vmwgfx kernel driver in Linux kernel v3.2. Therefore, any Linux distribution that is based on a kernel older than v3.2 will not have a fully functional display stack unless the distribution has back ported the vmwgfx driver.

Resolution

To resolve this issue without updating the kernel is by using the fbdev_drv.

To use fbdev_drv in Linux VMs using a kernel older than v3.2:

Launch vSphere Web Client.

Power off the VM.

Right click on the VM and click Edit Settings.

Click Boot Options under VM Options.

Under Secure Boot, deselect Enabled.

Click OK.

Power on the VM.

Log into the guest operating system with root privileges.

Edit /etc/X11/xorg.conf and find Section Device, which looks like below:

Section "Device"
BoardName    "VMWARE0405"
Driver       "vmware"
Identifier   "Device[0]"
VendorName   "VMWare Inc"
EndSection

Replace vmware with fbdev in Section Device:

Section "Device"
Driver "fbdev"
Identifier "Device[0]"
VendorName "fbdev"
EndSection

Save /etc/X11/xorg.conf and quit editing.

Shutdown the guest operating system.

Go to vSphere Web Client.

Right click on the VM and click Edit Settings.

Click Boot Options under VM Options.

Under Secure Boot, select Enabled.

Click OK.

Power on the VM.

Related Information

For more information about X server, refer to http://www.linfo.org/x_server.html.
セキュア ブートを有効にすると、v3.2 よりも古いカーネルを使用した場合に Linux 仮想マシン上で X サーバを起動できない (52955)
中文简体：启用安全引导时，在使用版本低于 v3.2 的内核的 Linux 虚拟机上 X 服务器将无法启动

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant