[vfio-users] [ Vfio-users ] Intel haswell vga

Jonathan Panozzo jonp at lime-technology.com
Wed Sep 9 23:01:42 UTC 2015


Blank is right, but to go a step further (and maybe he or someone else can clarify), I don’t even know if the that project is going to deliver the solution you’re looking for.  I believe iGVT-g (that’s the new name) is for sharing an intel integrated graphics device with multiple VMs that are then connected to through a remote graphics connection (e.g. Microsoft RDP, VNC, SPICE, etc.).  I’m not sure if it is intended (or will even) support doing graphics output the same way it works with VFIO and a discrete GPU.

- Jon

> On Sep 9, 2015, at 3:48 PM, Blank Field <ihatethisfield at gmail.com> wrote:
> 
> The integrated QEMU VNC server uses your attached Cirrus VGA, which is emulated and disabled because you p-t an intel GPU.
> And VNC doesn't have enough performance to provide viable 3D graphics over the net.
> So you definitely need to connect a screen to that machine.
> But that's not the main problem - intel GPUs are not alike to discrete cards, they share memory with the CPU, they have power management embedded into the CPU and so on, so vfio can't handle this yet, and it may even be theoretically difficult.
> 
> But there's a bright side - google for KVMGT: a project from intel folks which aim to provide virtual functions of intel's GPU.
> I haven't seen it working yet.
> 
> On Sep 9, 2015 11:39 PM, "nicolas prochazka" <prochazka.nicolas at gmail.com <mailto:prochazka.nicolas at gmail.com>> wrote:
> Hello,
> 
> I'm using a linux distribution without graphic card, by disable graphics in kernel config.
> I want to use intel haswell cpu  internal gpu as primary card for my vm
> I can start vm (via ssh), without an error, 
> but nothing display on my screen, on vnc client i can read, " guest has not initalised the display (yet)
> 
> In dmesg : 
> [Tue Aug 11 19:04:00 2015] vfio-pci 0000:00:02.0: enabling device (0400 -> 0403)
> [Tue Aug 11 19:04:00 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x20 (was 0x1, writing 0xf001)
> [Tue Aug 11 19:04:00 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x18 (was 0xc, writing 0xe000000c)
> [Tue Aug 11 19:04:00 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x10 (was 0x4, writing 0xf6000004)
> [Tue Aug 11 19:04:00 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x4 (was 0x900000, writing 0x900003)
> [Tue Aug 11 19:04:00 2015] vfio-pci 0000:00:02.0: BAR 2: can't reserve [mem 0xe0000000-0xefffffff 64bit pref]
> [Tue Aug 11 19:04:00 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x20 (was 0x1, writing 0xf001)
> [Tue Aug 11 19:04:00 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x18 (was 0xc, writing 0xe000000c)
> [Tue Aug 11 19:04:00 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x10 (was 0x4, writing 0xf6000004)
> [Tue Aug 11 19:04:01 2015] kvm: zapping shadow pages for mmio generation wraparound
> 
> and after destroy the vm : 
> 
> [Tue Aug 11 19:07:54 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x20 (was 0x1, writing 0xf001)
> [Tue Aug 11 19:07:54 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x18 (was 0xc, writing 0xe000000c)
> [Tue Aug 11 19:07:54 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x10 (was 0x4, writing 0xf6000004)
> [Tue Aug 11 19:07:54 2015] vfio-pci 0000:00:02.0: restoring config space at offset 0x4 (was 0x900000, writing 0x900400)
> [Tue Aug 11 19:07:54 2015] dmar: DRHD: handling fault status reg 3
> [Tue Aug 11 19:07:54 2015] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 0 
> DMAR:[fault reason 02] Present bit in context entry is clear
> [Tue Aug 11 19:07:54 2015] pci-stub 0000:00:02.0: claimed by stub
> 
> 
> my question is : is it possible to work  , it seems only discrete card can work with vfio-pci, but 
> what is differnce between discrete card and integrate chips
> Regards,
> Nicolas Prochazka
> 
> -----------------
> lspci
> 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
> 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT
> Integrated Graphics Controller (rev 09)
> 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
> 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
> 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
> 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection
> I218-V (rev 04)
> 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
> 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
> 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
> 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1
> [AHCI mode] (rev 04)
> 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
> 
> 
> qemu-system-x86_64 -name My_slitaz2 -S -machine pc-i440fx-2.4,accel=kvm,usb=off -cpu host,hv_relaxed,hv_vapic,hv_spinlocks=0x1000 -m 2600 -mem-prealloc -mem-path /dev/hugepages/libvirt/qemu -realtime mlock=off -smp 2,sockets=1,cores=2,threads=1 -uuid 72e44e57-9712-476d-acb4-f14bdd98580a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/My_slitaz2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/data/VMS/My_slitaz2/hdb.qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=writeback,copy-on-read=off -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=19,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=ac:de:50:00:00:00,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/My_slitaz2.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0 -vnc 10.10.3.223:0 <http://10.10.3.223:0/>,websocket=8000 -k fr -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device vfio-pci,host=00:02.0,x-vga=on,id=hostdev0,bus=pci.0,addr=0x5 -msg timestamp=on
> 
> _______________________________________________
> vfio-users mailing list
> vfio-users at redhat.com <mailto:vfio-users at redhat.com>
> https://www.redhat.com/mailman/listinfo/vfio-users <https://www.redhat.com/mailman/listinfo/vfio-users>
> 
> _______________________________________________
> vfio-users mailing list
> vfio-users at redhat.com
> https://www.redhat.com/mailman/listinfo/vfio-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20150909/a4f3e915/attachment.htm>


More information about the vfio-users mailing list