HP Elitedesk 800 G3 fails install or display of UIVM with VGA Boot set to PCI


While researching OXT-1593, a series of tests were run to verify the behaviour of PCI GPUs on both Dell and HP systems during both UEFI and Legacy boots. HP Elitedesk 800 G3 encountered bugs with two attempted installs, both when VGA Boot Device was set to the PCI Card:

1: In Legacy BIOS, boot screens will display off PCI card but OXT installer requires switching to onboard graphics card. Installation will fail. Alt+F2 shows:
mkdir -p /mnt/part2/dom0/sys/kernel/security
mount -o bind /sys/kernel/security /mnt/part2/dom0/sys/kernel/security
cp: error writing '/tmp/tmp.xss0ksPq2v/part1/kcmdline': No space left on device
cp: error writing '/tmp/tmp.xss0ksPq2v/part1/a

2: In UEFI mode, boot and installation will run off the PCI card, but once OXT is installed it will require switching to the onboard card to display the UIVM.


HP Elitedesk 800 G3
PCI GPU (tested NVIDIA Quadro P2000 and AMD FirePro W2100)
Bios 02.25
OpenXT Stable 9 Build 6524

Validation Steps


  1. Set VGA Boot Device to PCI card

  2. Attempt install of OXT as described under environment section (measured launch, no SSH access)

  3. installer will require switching to onboard graphics

  4. Installer will fail


  1. Set VGA Boot Device to PCI card

  2. Attempt install of OXT as described under environment section (measured launch, no SSH access)

  3. Installation will succeed, but after reboot UIVM will not display

  4. Switching to onboard graphics will show the UIVM


Eric Chanudet
May 14, 2019, 7:55 PM

Indeed. This is a limitation of Surfman/drm-plugin with the gem-foreign patches queue.

The gem-foreign patches queue takes advantage of the UMA stolen memory to scan the framebuffer of the guest. Without this, linuxfb plugin for Surfman should be the fallback, but lacks testing AFAIK. linuxfb would also provide coarse display at best (limited resolutions, poor performances).

I had a quick look around and this looks fairly undocumented. I seem to remember a splash-screen during installation would warn users to switch the Primary display to the Intel integrated graphics in the firmware, but I no longer see that around.

Eric Chanudet
May 14, 2019, 7:58 PM

This seems unrelated to graphics though, but definitely needs attention.

Tyler McGavran
May 17, 2019, 12:53 PM

Tested with an AMD W2100 and Nvidia K2200 (I don't have access to an P2000) on an HP EliteDesk 800 G3
Can't comment on the "no space left issue", only looked into the display output during installer issue.

Tyler McGavran
May 20, 2019, 5:59 PM

Concerning the 'no space left' issue
I don't see that issue if the onboard VGA device is set as the boot VGA device. It only occurs when the PCI card is the boot VGA device.
In that scenario, if the the proper drivers are missing you'll find a message like
[ 319.118447] [drm:gen8_de_irq_handler] ERROR Fault errors on pipe A: 0x00000080
flooding dmesg. dmesg resides in /var/volatile, but the tmpfs for /var/volatile is only 2M big so it gets filled up quite quickly. If you let the installer sit on the first screen for a couple minutes you'll find that you can't even get past the keyboard layout screen. I bet if you could go through the installer REALLY fast you'd probably avoid this issue (just barely). As it stands though the "Preserve-install-data" stage of the install will fail out due to /tmp (also residing in /var/volatile) having 'no space left'

Nicholas Tsirakis
June 27, 2019, 6:14 PM

Per :

  • Tested with both legacy & UEFI HP 800 G3 w/ AMD W2100 card

  • Warning showed properly during install

  • UIVM showed properly once user switched primary display to built-in card in BIOS





Andrew Jones



QA Assignee

Nicholas Tsirakis

QA Image URL


Epic Link

Fix versions

Affects versions