Here’s the original article.
Xen – Intel GVT-g(XenGT) Pubic Release
Here’s my env.
CPU: i5-4460
OS: Ubuntu 14.04 Desktop
Gernerally, you can follow the XenGT_Setup_Guide.pdf.
Before the kernel building, you may copy /boot/config-3.XX to the XenGT-Preview-kernel/.config.old to make a most adaptive kernel.
Please note that, direct mode will show vm-display to your monitor connected with your iGPU, indirect mode will not show anything to your monitor but a dummy monitor instead, and you can connect to it with VNC or RDP.
And here’s the grub menuentry you should add.
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
|
menuentry 'Ubuntu, with Linux 3.17.0-rc4-vgt' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.17.0-rc4-vgt-advanced-0c268053-24fb-4ff7-8d2a-053a9006ef50' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 4c4f10ff-0c03-40a9-bba7-72fa86fb4b61
else
search --no-floppy --fs-uuid --set=root 4c4f10ff-0c03-40a9-bba7-72fa86fb4b61
fi
echo 'Loading Linux 3.17.0-rc4-vgt ...'
multiboot /xen-vgt.gz dom0_mem=2048M loglvl=all guest_loglvl=all conring_size=4M noreboot
module /vmlinuz-vgt-3.17.0-rc4-vgt placeholder root=UUID=0c268053-24fb-4ff7-8d2a-053a9006ef50 ro quiet splash KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM ignore_loglevel console=tty0 console=hvc0 consoleblank=0 log_buf_len=4M xen_vgt.hvm_boot_foreground=1
module /initrd-vgt-3.17.0-rc4-vgt.img
}
|
If it occurs that you could not create a new VM with vgt=1, just ‘cat /sys/kernel/vgt/control/available_resources’ to see how many resources left. You may change Graphic Memory allocated for your graphic card in BIOS configuration，and it may work..
Below content comes from here.
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
3.1.8 Remaining graphics memory size,the number of fence regs
PATH: /sys/kernel/vgt/control/available_resources
DESCRIPTION: This entry shows remaining free CPU visible graphics memory size,
available CPU invisible graphics memory size and available
fence registers.It can be used to determine how many VMs with
VGT instance can still be created.
The output consists of 3 lines in hexadecimal and looks like this:
(Using "\" to represent the continuing of the same line)
0x00000200, 0x00000180, 0x00000600, 0x00000480, 0x00000010, 0x0000000c\
00000000,00000000,00000000,00000000,00000000,00000000,00000000,\
00000000,00000000,00000000,00000000,00000000,00000000,00000000,\
00000000,00000000,00000000,00000000,00000000,00000000,00000000,\
00000000,00000000,00000000,00000000,00000000,00000000,00000000,\
00000000,00000000,00000000,00000000,00000000,00000000,00000000,\
00000000,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,\
ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,\
ffffffff,00000000,00000000,00000000,00000000,00000000,00000000,\
00000000,00000000,00000000,00000000,00000000,00000000,ffffffff,\
ffffffff
000f
The first line shows 6 numbers:
total CPU visible Graphics memory size,
free CPU visible graphics memory size,
toal CPU invisible graphics memory size,
free CPU invisible graphics memory size,
total number of fence register,
the number of free fence registers. (Note: the first 4 are in 'MB').
The second and third line show the bitmap of graphics memory and
fence register allocation. Bits of "1" mean the resources have
been taken.
|