Arch Linux

Bronek

Member

From: London

Registered: 2014-02-14

Posts: 119

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

@Bronek

Tried with rom which I got from running Atiflash and also some roms from techPowerUp. Every time: black screen after Seabios and boot device choosing.

It's like I'm missing something stupid or something big, dunno

Sorry, I'm out of ideas. Perhaps aw will be able to help. Also, which versions of software are your running? Did you try using ROM from your own card?

Nanori

Member

Registered: 2015-01-13

Posts: 2

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

/me beats head on desk...

If you're using Intel host graphics and VGA mode for the device, you need the i915 patch.  If it didn't work for you, it's probably because you didn't enable it via the kernel commandline.

Even if I use this patch (and specify the i915.enable_hd_vgaarb=1 in command line), the Nvidia card doesn't send any signal to the screen. Without this patch, the ATI card work perfectly. For each test I make, I try the tow kernels (3.17 not patched and 3.18 patched) to optimize the chance of success

Most of your current kernel options are unnecessary.

Yes, but I've try them while reading some other topics about VGA Passthrough (nothing ventured, nothing gained ). Remove those unnecessary options from cmdline doen't solved the issue

And... since you have a Windows guest, don't use q35!

Better yet, use Windows8+ and OVMF.

Doesn't seem like you've been following the thread very carefully...

At this time, I'm trying to have a Windows 7 guest (preferably without using an UEFI bios). Moreover, the "windowsDisk" I use dosen't contain any data (no OS). So I should be able to see the bios on my screen when I boot my VM but it isn't the case.
Does a 440fx is realy better ?

walkindude

Member

Registered: 2012-03-04

Posts: 29

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

@Bronek

Kernel: https://aur.archlinux.org/packages/linux-uksm-ck/

walkindude@Desktop> uname -a                                                                                         ~
Linux Desktop 3.18.2-1-uksm-ck #1 SMP PREEMPT Wed Jan 14 01:23:45 MSK 2015 x86_64 GNU/Linux

Also patched it with ACS patch

Host video driver (radeonsi):

walkindude@Desktop> glxinfo | grep version                                                                           ~
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.5.0-devel (git-0e6f0ee)
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 10.5.0-devel (git-0e6f0ee)
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.5.0-devel (git-0e6f0ee)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.0

walkindude@Desktop> qemu-x86_64 -version                                                                             ~
qemu-x86_64 version 2.2.50, Copyright (c) 2003-2008 Fabrice Bellard

walkindude@Desktop> libvirtd -v                                                                                     
2015-01-13 22:40:53.819+0000: 9697: info : libvirt version: 1.2.1

Yes, I'd booted from FreeDos, and backed up ROM (by ATIflash utility) of my own card - same result.

What I see on desired screen is
http://rghost.net/60334498.view

Whatever option I choose -> dark screen.

Could it be because of (one string for one launch)?

[  140.296537] kvm: zapping shadow pages for mmio generation wraparound
[ 1134.175319] kvm: zapping shadow pages for mmio generation wraparound

Last edited by walkindude (2015-01-13 23:25:51)

walkindude

Member

Registered: 2012-03-04

Posts: 29

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

So I should be able to see the bios on my screen when I boot my VM but it isn't the case.

Maybe you should set

-boot menu=on,splash-time=60000,strict=on

or some other preferable time [1...65535] ?

Wimma77

Member

Registered: 2014-08-12

Posts: 15

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

Has anyone tried the Win10 preview with passthrough?
I assume it's a bit early, but I'm waiting for it as I have no 8.1 license and failed with Win7 & nvidia.

walkindude

Member

Registered: 2012-03-04

Posts: 29

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

@Wimma77
I'm trying to do it the right way (build 9888), read my messages
But for now, I cannot go further than selecting the boot device.
Previously I'd installed it successfully but with VNC and Cirrus, and it gave me a lot of VIDEO_TDR_FAILURE after I installed Catalyst.

Last edited by walkindude (2015-01-13 23:56:56)

Wimma77

Member

Registered: 2014-08-12

Posts: 15

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

@walkindude
Yeah, trying to keep up with progress, but been a while. I did have success with a HD7770 (way back around page 80/90 days), but struggled with my GTX750ti so gave it a break. Hoping that it get a little easier as things mature. Want to try OVMF, and have looked through aw's blog, but I don't have Win8 so can't try yet.
Also my server is in full use at home, so don't have the play time I used to, so need to be confident before I start messing around again.
Think I need another test box ...

Last edited by Wimma77 (2015-01-14 00:11:44)

dam5h

Member

Registered: 2011-08-04

Posts: 21

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

Would this be possible with a haswell laptop with only the integrated graphics?  It would be okay that once the guest boots and takes control of the GPU you could no longer access the host until you shut down the guest.

Thanks.

aw

Member

Registered: 2013-10-04

Posts: 921

Website

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

Would this be possible with a haswell laptop with only the integrated graphics?  It would be okay that once the guest boots and takes control of the GPU you could no longer access the host until you shut down the guest.

Thanks.

No

---

http://vfio.blogspot.com
Looking for a more open forum to discuss vfio related uses?  Try https://www.redhat.com/mailman/listinfo/vfio-users

winie

Member

Registered: 2014-03-01

Posts: 17

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

Would this be possible with a haswell laptop with only the integrated graphics?  It would be okay that once the guest boots and takes control of the GPU you could no longer access the host until you shut down the guest.

Thanks.

use xengt:
https://github.com/01org/XenGT-Preview-kernel
it does the gpu equivalent  of vt-x for the cpu and uses the integrated graphics for host and guest at the same time

slis

Member

Registered: 2014-06-02

Posts: 127

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

or maybe kvmGT? did anyone try it?

Bronek

Member

From: London

Registered: 2014-02-14

Posts: 119

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

@Bronek
Host video driver (radeonsi):

walkindude@Desktop> glxinfo | grep version                                                                           ~
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.5.0-devel (git-0e6f0ee)
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 10.5.0-devel (git-0e6f0ee)
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.5.0-devel (git-0e6f0ee)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.0

OK so you have versions of everything recent enough. How many GPUs have you got? Are you sure that the one you want passed through is not being claimed by radeon driver? I have blacklisted radeon on my machine, and it's being run headless. You can use lspci -vnn -s 03:00.0 for this, you may also need to check /proc/iomem  as suggested by aw on page 130 of this thread.

EDIT: also, capabilities of driver loaded in host are totally irrelevant for passthrough. The whole idea of VGA passthrough is to make the card  unavailable for the host and available for the guest instead. Not some part of the card, but all of it, starting from emulated PCI channel. The only thing that hosts own drivers need to be able to do, is to sod off. Some drivers are not very good in this and will actually claim the card you want to passthrough, just because it has recognized chip type. It might be that the module you have loaded in the host is this kind of a driver.

Last edited by Bronek (2015-01-14 09:19:08)

Bronek

Member

From: London

Registered: 2014-02-14

Posts: 119

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

@walkindude, actually you reminded me I wanted to ask aw something : which video modules are known to cause trouble/ignore VGA arbitration? Assuming guest OS is not EFI compatible (i.e. OVMF is not available) and recent kernel is being used on host. I think the following options are normally available : vga16fb , vesafb , radeon/nouveau, radeonfb/nvidiafb (i915 is not an option for reasons you explained often enough, but what about intelfb?). Some users may run fbcon on top of it, or run a non-free driver instead of regular kernel module.

Also from reading http://vfio.blogspot.co.uk/2014/08/what … ation.html I understand that Xorg does not play (at all) with VGA arbitration, but it not does not imply that another GPU cannot be passed through, does it?

Last edited by Bronek (2015-01-14 10:35:04)

Myranti

Member

Registered: 2010-03-04

Posts: 20

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

After reading a number of the posts here about hugepages I figured I'd give it a shot and have set it up. I'm not sure if there's much of a performance improvement, but I haven't really tested it yet.

I also took the time to finally remove the need for the vfio-bind script since I was still binding a network adapter because I had been too lazy to fix my network config files, which was adding all en* interfaces to my bridge and causing the network on the host not to start. The less messing around with extra scripts that I can do, the better.

I have to say that I'm pretty happy to have everything working well, taking me from 2 separate computers (1 for linux, 1 for windows gaming) down to 1.

Bronek

Member

From: London

Registered: 2014-02-14

Posts: 119

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

@walkindude , one more thing, show us the result of

$ dmesg | grep -E "0000:03:00|radeon|stub|vfio"

Last edited by Bronek (2015-01-14 13:20:07)

walkindude

Member

Registered: 2012-03-04

Posts: 29

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

@Bronek

walkindude@Desktop> sudo dmesg | grep -E "0000:03:00|radeon|stub|vfio"                                               ~
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-uksm-ck root=UUID=7d535c2f-90b6-4f8d-b39f-ff79dd6dfedf rw root=/dev/mapper/lvmVolume-lvmRoot discard rw iommu=pt iommu=1 ivrs_ioapic[9]=00:14.0 ivrs_ioapic[10]=00:00.1 amd_iommu_dump=1 pci-stub.ids=1002:6739,1002:aa88 pcie_acs_override=downstream
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-uksm-ck root=UUID=7d535c2f-90b6-4f8d-b39f-ff79dd6dfedf rw root=/dev/mapper/lvmVolume-lvmRoot discard rw iommu=pt iommu=1 ivrs_ioapic[9]=00:14.0 ivrs_ioapic[10]=00:00.1 amd_iommu_dump=1 pci-stub.ids=1002:6739,1002:aa88 pcie_acs_override=downstream
[    0.502020] pci 0000:03:00.0: [1002:6739] type 00 class 0x030000
[    0.502040] pci 0000:03:00.0: reg 0x10: [mem 0xc0000000-0xcfffffff 64bit pref]
[    0.502053] pci 0000:03:00.0: reg 0x18: [mem 0xfe820000-0xfe83ffff 64bit]
[    0.502061] pci 0000:03:00.0: reg 0x20: [io  0xc000-0xc0ff]
[    0.502075] pci 0000:03:00.0: reg 0x30: [mem 0xfe800000-0xfe81ffff pref]
[    0.502160] pci 0000:03:00.0: supports D1 D2
[    0.502224] pci 0000:03:00.1: [1002:aa88] type 00 class 0x040300
[    0.502243] pci 0000:03:00.1: reg 0x10: [mem 0xfe840000-0xfe843fff 64bit]
[    0.502330] pci 0000:03:00.1: supports D1 D2
[    0.505789] vgaarb: device added: PCI:0000:03:00.0,decodes=io+mem,owns=none,locks=none
[    0.505792] vgaarb: bridge control possible 0000:03:00.0
[    0.512441] pci 0000:03:00.0: can't claim BAR 0 [mem 0xc0000000-0xcfffffff 64bit pref]: no compatible bridge window
[    0.528611] pci 0000:03:00.0: BAR 0: no space for [mem size 0x10000000 64bit pref]
[    0.528614] pci 0000:03:00.0: BAR 0: trying firmware assignment [mem size 0x10000000 64bit pref]
[    0.528616] pci 0000:03:00.0: BAR 0: assigned [mem 0xc0000000-0xcfffffff 64bit pref]
[    3.000492] pci-stub: add 1002:6739 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[    3.000505] pci-stub 0000:03:00.0: claimed by stub
[    3.000511] pci-stub: add 1002:AA88 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[    3.000526] pci-stub 0000:03:00.1: claimed by stub
[    4.984586] [drm] radeon kernel modesetting enabled.
[    4.984674] fb: switching to radeondrmfb from EFI VGA
[    4.989974] radeon 0000:01:00.0: Invalid ROM contents
[    4.990438] radeon 0000:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
[    4.990441] radeon 0000:01:00.0: GTT: 1024M 0x0000000080000000 - 0x00000000BFFFFFFF
[    4.990648] [drm] radeon: 2048M of VRAM memory ready
[    4.990650] [drm] radeon: 1024M of GTT memory ready.
[    5.011140] [drm] radeon: dpm initialized
[    5.023619] radeon 0000:01:00.0: WB enabled
[    5.023623] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff880001cdfc00
[    5.023625] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff880001cdfc04
[    5.023628] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff880001cdfc08
[    5.023630] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff880001cdfc0c
[    5.023633] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff880001cdfc10
[    5.024698] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90011135a18
[    5.024704] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
[    5.024742] radeon 0000:01:00.0: irq 30 for MSI/MSI-X
[    5.024756] radeon 0000:01:00.0: radeon: using MSI.
[    5.024789] [drm] radeon: irq initialized.
[    6.162222] fbcon: radeondrmfb (fb0) is primary device
[    6.208766] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[    6.208768] radeon 0000:01:00.0: registered panic notifier
[    6.216932] [drm] Initialized radeon 2.40.0 20080528 for 0000:01:00.0 on minor 0
[  523.806082] vfio-pci 0000:03:00.0: enabling device (0000 -> 0003)
[  523.879271] vfio-pci 0000:03:00.1: enabling device (0000 -> 0002)

walkindude@Desktop> sudo lspci -vnn -s 03:00.0 
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller])
    Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e174]
    Flags: fast devsel, IRQ 16
    Memory at c0000000 (64-bit, prefetchable) [disabled] [size=256M]
    Memory at fe820000 (64-bit, non-prefetchable) [disabled] [size=128K]
    I/O ports at c000 [disabled] [size=256]
    Expansion ROM at fe800000 [disabled] [size=128K]
    Capabilities: [50] Power Management version 3
    Capabilities: [58] Express Legacy Endpoint, MSI 00
    Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
    Capabilities: [150] Advanced Error Reporting
        Kernel driver in use: pci-stub
    Kernel modules: radeon

walkindude@Desktop> cat /proc/iomem                                                                                                            ~
00000000-00000fff : reserved
00001000-0009ffff : System RAM
000a0000-000bffff : PCI Bus 0000:00
000c0000-000dffff : PCI Bus 0000:00
  000c0000-000cffff : Video ROM
000f0000-000fffff : System ROM
00100000-bda58fff : System RAM
  03000000-0345329d : Kernel code
  0345329e-038e57ff : Kernel data
  03a0a000-03b7afff : Kernel bss
bda59000-bdaa9fff : ACPI Non-volatile Storage
bdaaa000-bdab2fff : ACPI Tables
bdab3000-bdab3fff : ACPI Non-volatile Storage
bdab4000-bdad8fff : reserved
bdad9000-bdae9fff : ACPI Non-volatile Storage
bdaea000-bdaebfff : reserved
bdaec000-bdafcfff : reserved
bdafd000-bdafdfff : reserved
bdafe000-bdafefff : reserved
bdaff000-bdb00fff : ACPI Non-volatile Storage
bdb01000-bdb01fff : reserved
bdb02000-bdb02fff : reserved
bdb03000-bdb09fff : reserved
bdb0a000-bdb0ffff : ACPI Non-volatile Storage
bdb10000-bdb1cfff : reserved
bdb1d000-bdb5efff : reserved
bdb5f000-bdb6efff : reserved
bdb6f000-bdb71fff : reserved
bdb72000-bdd74fff : ACPI Non-volatile Storage
bdd75000-bdefffff : System RAM
bdf00000-bfffffff : RAM buffer
c0000000-cfffffff : 0000:03:00.0
d0000000-ffffffff : PCI Bus 0000:00
  d0000000-dfffffff : PCI Bus 0000:01
    d0000000-dfffffff : 0000:01:00.0
  e0000000-efffffff : PCI MMCONFIG 0000 [bus 00-ff]
    e0000000-efffffff : pnp 00:00
  f8000000-fbffffff : reserved
  fe800000-fe8fffff : PCI Bus 0000:03
    fe800000-fe81ffff : 0000:03:00.0
    fe820000-fe83ffff : 0000:03:00.0
    fe840000-fe843fff : 0000:03:00.1
  fe900000-fe9fffff : PCI Bus 0000:02
    fe900000-fe91ffff : 0000:02:06.0
    fe920000-fe9200ff : 0000:02:06.0
      fe920000-fe9200ff : r8169
  fea00000-feafffff : PCI Bus 0000:01
    fea00000-fea3ffff : 0000:01:00.0
    fea40000-fea5ffff : 0000:01:00.0
    fea60000-fea63fff : 0000:01:00.1
      fea60000-fea63fff : ICH HD audio
  feb00000-feb000ff : 0000:00:16.2
    feb00000-feb000ff : ehci_hcd
  feb01000-feb01fff : 0000:00:16.0
    feb01000-feb01fff : ohci_hcd
  feb02000-feb02fff : 0000:00:14.5
    feb02000-feb02fff : ohci_hcd
  feb03000-feb030ff : 0000:00:13.2
    feb03000-feb030ff : ehci_hcd
  feb04000-feb04fff : 0000:00:13.0
    feb04000-feb04fff : ohci_hcd
  feb05000-feb050ff : 0000:00:12.2
    feb05000-feb050ff : ehci_hcd
  feb06000-feb06fff : 0000:00:12.0
    feb06000-feb06fff : ohci_hcd
  feb07000-feb073ff : 0000:00:11.0
    feb07000-feb073ff : ahci
  feb20000-feb23fff : amd_iommu
  fec00000-fec00fff : reserved
    fec00000-fec003ff : IOAPIC 0
  fec10000-fec10fff : reserved
    fec10000-fec10fff : pnp 00:01
  fec20000-fec20fff : reserved
    fec20000-fec203ff : IOAPIC 1
  fed00000-fed00fff : reserved
    fed00000-fed003ff : HPET 0
      fed00000-fed003ff : PNP0103:00
  fed61000-fed70fff : reserved
    fed61000-fed70fff : pnp 00:01
  fed80000-fed8ffff : reserved
    fed80000-fed8ffff : pnp 00:01
      fed80b00-fed80b07 : SB800 TCO
  fee00000-fee00fff : Local APIC
    fee00000-fee00fff : pnp 00:01
  fef00000-ffffffff : reserved
    ffc00000-ffffffff : pnp 00:01
100001000-23effffff : System RAM
23f000000-23fffffff : RAM buffer

Two GPUs:
HD6850
R9 270

Mobo:
M5A97 Pro

Processor:
Amd FX-8320

Last edited by walkindude (2015-01-14 17:00:25)

Rommy

Member

Registered: 2014-10-17

Posts: 51

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

Since qemu 2.2.0-1 I get the following error:
qemu-system-x86_64: -device ide-hd,bus=ide.0,drive=disk: Property 'ide-hd.drive' can't take value 'disk', it's in use

Is there a workaround?

aw

Member

Registered: 2013-10-04

Posts: 921

Website

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

Since qemu 2.2.0-1 I get the following error:
qemu-system-x86_64: -device ide-hd,bus=ide.0,drive=disk: Property 'ide-hd.drive' can't take value 'disk', it's in use

Is there a workaround?

Don't name your drive "disk"?

---

http://vfio.blogspot.com
Looking for a more open forum to discuss vfio related uses?  Try https://www.redhat.com/mailman/listinfo/vfio-users

Rommy

Member

Registered: 2014-10-17

Posts: 51

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

I tried diska, before posting.
Now I tried 'win', same errors.

Edit:
My full command is:

qemu-system-x86_64 -enable-kvm -M q35 -m 4096 -cpu host,kvm=off -smp 3,sockets=1,cores=3,threads=1 -bios /usr/share/qemu/bios.bin -vga none -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on,romfile=/home/rommy/vms/win8/GF100.rom -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1 -usb -usbdevice host:0079:0006 -usbdevice host:062a:0252 -usbdevice host:04f3:0103 -drive file=/home/rommy/vms/win8/win8_vga_rw.qcow2,id=win,format=qcow2 -device ide-hd,bus=ide.0,drive=win -nographic

Last edited by Rommy (2015-01-14 20:48:38)

aw

Member

Registered: 2013-10-04

Posts: 921

Website

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

I tried diska, before posting.
Now I tried 'win', same errors.

That's the only guess I'm going to give without the rest of your command line.

---

http://vfio.blogspot.com
Looking for a more open forum to discuss vfio related uses?  Try https://www.redhat.com/mailman/listinfo/vfio-users

Rommy

Member

Registered: 2014-10-17

Posts: 51

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

Sorry, I edited it. See above

nbhs

Member

From: Montevideo, Uruguay

Registered: 2013-05-02

Posts: 402

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

I tried diska, before posting.
Now I tried 'win', same errors.

Edit:
My full command is:

qemu-system-x86_64 -enable-kvm -M q35 -m 4096 -cpu host,kvm=off -smp 3,sockets=1,cores=3,threads=1 -bios /usr/share/qemu/bios.bin -vga none -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on,romfile=/home/rommy/vms/win8/GF100.rom -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1 -usb -usbdevice host:0079:0006 -usbdevice host:062a:0252 -usbdevice host:04f3:0103 -drive file=/home/rommy/vms/win8/win8_vga_rw.qcow2,id=win,format=qcow2 -device ide-hd,bus=ide.0,drive=win -nographic

add "if=none"

...,drive=win,if=none

qemu 2.2 should support -cdrom -hda, etc using the q35 chipset

Rommy

Member

Registered: 2014-10-17

Posts: 51

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

qemu-system-x86_64 -enable-kvm -M q35 -m 4096 -cpu host,kvm=off -smp 3,sockets=1,cores=3,threads=1 -bios /usr/share/qemu/bios.bin -vga none -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on,romfile=/home/rommy/vms/win8/GF100.rom -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1 -usb -usbdevice host:0079:0006 -usbdevice host:062a:0252 -usbdevice host:04f3:0103 -drive file=/home/rommy/vms/win8/win8_vga_rw.qcow2,id=win,format=qcow2 -device ide-hd,bus=ide.0,drive=win,if=none -nographic

Error:

qemu-system-x86_64: -device ide-hd,bus=ide.0,drive=win,if=none: Property 'ide-hd.drive' can't take value 'win', it's in use

nbhs

Member

From: Montevideo, Uruguay

Registered: 2013-05-02

Posts: 402

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

qemu-system-x86_64 -enable-kvm -M q35 -m 4096 -cpu host,kvm=off -smp 3,sockets=1,cores=3,threads=1 -bios /usr/share/qemu/bios.bin -vga none -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on,romfile=/home/rommy/vms/win8/GF100.rom -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1 -usb -usbdevice host:0079:0006 -usbdevice host:062a:0252 -usbdevice host:04f3:0103 -drive file=/home/rommy/vms/win8/win8_vga_rw.qcow2,id=win,format=qcow2 -device ide-hd,bus=ide.0,drive=win,if=none -nographic

Error:

qemu-system-x86_64: -device ide-hd,bus=ide.0,drive=win,if=none: Property 'ide-hd.drive' can't take value 'win', it's in use

Yeah sorry it should be like this:

... -drive file=/home/rommy/vms/win8/win8_vga_rw.qcow2,id=win,format=qcow2,if=none  -device ide-hd,bus=ide.0,drive=win ...

EDITED

Last edited by nbhs (2015-01-14 21:03:41)

aw

Member

Registered: 2013-10-04

Posts: 921

Website

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

I think if=none goes on the -drive option...

---

http://vfio.blogspot.com
Looking for a more open forum to discuss vfio related uses?  Try https://www.redhat.com/mailman/listinfo/vfio-users