Is the i915 module loaded? I noticed that the snd-hda driver was pulling this in. If it is you can just try renaming it to i915.ko.noload and that should stop it from loading
01.02.2017, 20:10, "José A. Gómez" <mailgo...@gmail.com>:
ThanksI tried it in both default linux kernel and linux-vfio with the same results.So I reinstalled again, and now I am having this kernel message when I start the VM:Notes:
...
......
[ 161.395402] DMAR: DRHD: handling fault status reg 3
[ 161.395831] DMAR: [DMA Read] Request device [00:02.0] fault addr ab5c0000 [fault reason 06] PTE Read access is not set
[ 161.396777] DMAR: DRHD: handling fault status reg 3
[ 161.397202] DMAR: [DMA Read] Request device [00:02.0] fault addr ab5ee000 [fault reason 06] PTE Read access is not set
[ 161.398124] DMAR: DRHD: handling fault status reg 3
[ 161.398547] DMAR: [DMA Read] Request device [00:02.0] fault addr ab65b000 [fault reason 06] PTE Read access is not set
[ 161.399474] DMAR: DRHD: handling fault status reg 3
[ 161.399899] DMAR: [DMA Read] Request device [00:02.0] fault addr ab6c7000 [fault reason 06] PTE Read access is not set
[ 161.401084] DMAR: DRHD: handling fault status reg 3
[ 161.401468] DMAR: [DMA Read] Request device [00:02.0] fault addr ab213000 [fault reason 12] non-zero reserved fields in PTE
[ 161.402329] DMAR: DRHD: handling fault status reg 3
[ 161.402709] DMAR: [DMA Read] Request device [00:02.0] fault addr ab277000 [fault reason 06] PTE Read access is not set
[ 161.403583] DMAR: DRHD: handling fault status reg 3
[ 161.403960] DMAR: [DMA Read] Request device [00:02.0] fault addr ab2da000 [fault reason 06] PTE Read access is not set
[ 161.404788] DMAR: DRHD: handling fault status reg 3
[ 161.405167] DMAR: [DMA Read] Request device [00:02.0] fault addr ab33c000 [fault reason 06] PTE Read access is not set
[ 161.405996] DMAR: DRHD: handling fault status reg 3
[ 161.406405] DMAR: [DMA Read] Request device [00:02.0] fault addr ab39c000 [fault reason 06] PTE Read access is not set
[ 161.407256] DMAR: DRHD: handling fault status reg 3
[ 161.407651] DMAR: [DMA Read] Request device [00:02.0] fault addr ab3ff000 [fault reason 06] PTE Read access is not set
[ 161.739597] virbr0: port 2(vnet0) entered learning state
[ 161.810579] vfio-pci 0000:00:02.0: BAR 2: can't reserve [mem 0xb0000000-0xbfffffff 64bit pref]
......
...
(grub config)
GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=1bd6d9d7-4fd2-49bd-9095-fe4d581d9bff rd.modules-load=vfio-pci intel_iommu=on video=vesafb:off,efifb:off"
,2017-01-30 21:55 GMT+01:00 José A. Gómez <mailgo...@gmail.com>:I've launched the vm again:
2017-01-30T20:48:59.235214Z qemu-system-x86_64: terminating on signal 15 from pid 405 (/usr/bin/libvirtd)
2017-01-30 20:48:59.835+0000: shutting down, reason=destroyed
2017-01-30 20:49:58.623+0000: starting up libvirt version: 3.0.0, qemu version: 2.8.0, hostname: antkvm
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/sbin/qemu-system-x86_64 -name guest=win10,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-win10/master-key.aes -machine pc-i440fx-2.8,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu host-passthrough,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid b4adc075-0af9-4a4f-a487-bcc5082b198e -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-win10/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device ahci,id=sata0,bus=pci.0,addr=0x6 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive file=/home/MAQUINAS/win10IGDTEST.qcow2,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,media=cdrom,id=drive-sata0-0-0,readonly=on -device ide-cd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0 -drive if=none,media=cdrom,id=drive-sata0-0-1,readonly=on -device ide-cd,bus=sata0.1,drive=drive-sata0-0-1,id=sata0-0-1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:94:a0:e0,bus=pci.0,addr=0x3 -device usb-host,hostbus=1,hostaddr=5,id=hostdev0,bus=usb.0,port=1 -device vfio-pci,host=00:02.0,id=hostdev1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xb -msg timestamp=on
2017-01-30 21:23 GMT+01:00 Alex Williamson <alex.william...@redhat.com>:On Mon, 30 Jan 2017 20:53:50 +0100
José A. Gómez <mailgo...@gmail.com> wrote:
> Hello,
>
> This is my config
>
> Asus z87 deluxe (socket 1150)
> CPU Intel 4590 (hd4600)
> ati 5770
> memory 16 GB
> Antergos OS
> Kernel version 4.9.6-1-ARCH
>
> I have been working with the ATI as a guest in the VM without big problems
> (although it doesn't have a real uefi rom) and now I wanted to experiment
> with the IGD.
> I'm trying to pass the intel graphics to the VM (W10) but I only get a
> black screen. It is recognized in Windows 10 perfectly (adding the qxl
> graphics previously) but the screen does not turn on using the hdmi output.
>
> What I have done first is install windows 10 with qxl graphics card and
> after the installation add the IGD to the VM. Once inside the VM again
> install the drivers of the intel grapihcs card ( whichs is recognized
> perfectly as a intel hd4600),
> shutdown the VM and remove the qxl card.
>
> I also tried this in ubuntu with the same results.
Are there any errors reported in /var/log/libvirt/qemu/win10.log?_______________________________________________
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users
_______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
