PCI pass through

c0mputerking · Oct 11, 2011

Hello all i am trying to install a video capture device on a KVM based virtual machine, my hardware supports visualization and i have managed to get a KVM of Ubuntu 10.04 LTS running. I have also managed to get the video capture software to install and work properly inside the KVM. However there is no Video and i get the dreaded "No valid local video devices were detected" which probably means that KVM is not picking up the hardware.

The card is a 16 port PCI-X card installed into my Dell T110 II on which the card is listed in lspci

04:05.0 Multimedia video controller: Bluecherry BC-H16480A 16 port H.264 video and audio encoder / decoder

I do not see the card detected on the virtual machine

lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 VGA compatible controller: Cirrus Logic GD 5446
00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)

I have found this page on the KVM site but have not put any real effort into it yet, has anyone managed to get a virtual machine working with pci pass through???

http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM

Before i go ahead with this i was wondering if Proxmox 2 supports this out of the box or if i have to add kernel options in grub and the like.

I have found a post here http://forum.proxmox.com/threads/970-Proxmox-1.1-KVM-83-and-PCI-Passthrough and have tryed adding some lines to my /etc/pve/nodes/sun/qemu-server/104.conf and did a stop and start on the VM each time. The first to lines commented out rendered the VM unstartable and gave the start failed command below.

Using the last line "hostpci 04:05.0" allowed the VM to start without error, but I still do not see the PCI device listed in my lspci on the VM hope i am just missing something simple. Again do i need to edit grub?
#args: -pcidevice host=04:05.0 -cpu host
#args: -pcidevice host=04:05.0
hostpci 04:05.0

start failed: command '/usr/bin/kvm -id 104 -chardev socket,id=monitor,path=/var/run/qemu-server/104.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/104.vnc,x509,password -pidfile /var/run/qemu-server/104.pid -daemonize -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,bus=ehci.0,port=6 -name bluccherry2 -smp sockets=1,cores=1 -nodefaults -boot menu=on,order=cdn -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/iso/turnkey-core-11.2-lucid-x86.iso,if=none,id=drive-ide2,media=cdrom,aio=native -device ide-drive,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2 -drive file=/dev/vg1/vm-104-disk-1,if=none,id=drive-ide0,aio=native,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0 -m 512 -netdev type=tap,id=net0,ifname=tap104i0,script=/var/lib/qemu-server/pve-bridge -device rtl8139,romfile=,mac=22:BD:58:6A:16:79,netdev=net0,bus=pci.0,addr=0x12 -cpuunits 1000 -pcidevice host=04:05.0' failed: exit code 1 (500)

c0mputerking · Oct 14, 2011

When i try to edit my VM using the GUI by going to the hardware tab i get the following error

Code:

[COLOR=#000000][FONT=tahoma]unable to parse config file: hostpci 04:05.0 (500)[/FONT][/COLOR]

NOTE this only happens on the VM that i have tried to add the hostpci line into.

Could this be causing problems with pci pass through??

dietmar · Oct 14, 2011

Please can you post the config file (or at least the line in question)?

c0mputerking · Oct 14, 2011

I did post it above, but it was kind of unclear, and not in qoute tags as it should have been! plus sometimes i get carried away and post to much infos all at once here is the entire contents of my /etc/pve/nodes/sun/qemu-server/104.conf file. It is the very last line, the three directly above are commented out just stuff i was trying and read about in other posts, even other forums i think.

Code:

ide0: PVEVMS:vm-104-disk-1
ostype: l24
memory: 512
sockets: 1
net0: rtl8139=22:BD:58:6A:16:79,bridge=vmbr0
ide2: Proxmox-ISO:iso/turnkey-core-11.2-lucid-x86.iso,media=cdrom
name: bluccherry2
bootdisk: ide0
cores: 1
#args: -pcidevice host=04:05.0 -cpu host
#args: -pcidevice host=04:05.0
#args: -device pci-assign,host=04:05.0,id=bluecherry
hostpci 04:05.0

PS thanks in advance for your help this forum is very active and really helpful so far i am quite impressed

PPS i just notice that the os type is l24 could that be causing problems should'nt it be l26

PPS edited because i notice i have created another KMV machine with l26 and it does not have pass through either looks like this

ide0: PVEVMS:vm-105-disk-1
ostype: l26
memory: 1792
sockets: 1
net0: rtl8139=E2:C5:87:8D:4B:BF,bridge=vmbr0
ide2: Proxmox-ISO:iso/ubuntu-10.04-alternate-amd64.iso,media=cdrom
name: bluecherry3
bootdisk: ide0
cores: 4
hostpci 04:05.0

dietmar · Oct 14, 2011

There is a missing colon - use:

hostpci: 04:05.0

c0mputerking · Oct 14, 2011

Ok i have corrected my syntax error and attached the entire config file again for completeness. However the card still does not appear in lspci and it does not seem to work with the installed software on the VM either. Should it appear in lspci, how do i know it is being forwarded?

Code:

ide0: PVEVMS:vm-105-disk-1
ostype: l26
memory: 1024
sockets: 1
net0: rtl8139=E2:C5:87:8D:4B:BF,bridge=vmbr0
ide2: Proxmox-ISO:iso/ubuntu-10.04-alternate-amd64.iso,media=cdrom
name: bluecherry3
bootdisk: ide0
cores: 4
hostpci: 04:05.0

Code:

dietmar · Oct 14, 2011

use the monitor

# info pci
# info qtree

c0mputerking · Oct 14, 2011

what i do not understand

spirit · Oct 14, 2011

use command line :

# qm monitor 104

then

"info pci"

to list the pci devices in your vm.

if the device is present, normally, can you also see it in your guest vm , with lspci.

spirit · Oct 14, 2011

also did you have enabled vt-d/IOMMU in your bios ?

can you send the result of

"dmesg | grep -e DMAR -e IOMMU"

on your host ?

c0mputerking · Oct 14, 2011

Interesting i get an error when starting the monitor about the all important hostpci line, see below, directly below is my DMAR stuff

Code:

dmesg | grep -e DMAR -e IOMMU
ACPI: DMAR 00000000bf7e8000 000B0 (v01 INTEL      SNB  00000001 INTL 00000001)
DMAR: Host address width 36
DMAR: DRHD base: 0x000000fed91000 flags: 0x1
IOMMU fed91000: ver 1:0 cap c9008020660262 ecap f010da
DMAR: RMRR base: 0x000000bf65a000 end: 0x000000bf65bfff
DMAR: No ATSR found

Code:

root@sun:/etc/pve/nodes/sun/qemu-server# qm monitor 105
vm 105 - unable to parse value of 'hostpci' - unknown setting 'hostpci'
Entering Qemu Monitor for VM 105 - type 'help' for help
qm> info pci
  Bus  0, device   0, function 0:
    Host bridge: PCI device 8086:1237
      id ""
  Bus  0, device   1, function 0:
    ISA bridge: PCI device 8086:7000
      id ""
  Bus  0, device   1, function 1:
    IDE controller: PCI device 8086:7010
      BAR4: I/O at 0xc000 [0xc00f].
      id ""
  Bus  0, device   1, function 3:
    Bridge: PCI device 8086:7113
      IRQ 9.
      id ""
  Bus  0, device   2, function 0:
    VGA controller: PCI device 1013:00b8
      BAR0: 32 bit prefetchable memory at 0xf0000000 [0xf1ffffff].
      BAR1: 32 bit memory at 0xf2000000 [0xf2000fff].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
      id ""
  Bus  0, device  18, function 0:
    Ethernet controller: PCI device 10ec:8139
      IRQ 10.
      BAR0: I/O at 0xc100 [0xc1ff].
      BAR1: 32 bit memory at 0xf2020000 [0xf20200ff].
      id ""
  Bus  0, device  29, function 0:
    USB controller: PCI device 8086:2934
      IRQ 11.
      BAR4: I/O at 0xc200 [0xc21f].
      id "uhci-1"
  Bus  0, device  29, function 1:
    USB controller: PCI device 8086:2935
      IRQ 11.
      BAR4: I/O at 0xc220 [0xc23f].
      id "uhci-2"
  Bus  0, device  29, function 2:
    USB controller: PCI device 8086:2936
      IRQ 11.
      BAR4: I/O at 0xc240 [0xc25f].
      id "uhci-3"
  Bus  0, device  29, function 7:
    USB controller: PCI device 8086:293a
      IRQ 11.
      BAR0: 32 bit memory at 0xf2021000 [0xf2021fff].
      id "ehci"
qm>

Here is an info qtree however since the hostpci line is giving error I should probably no expect to see the device right?

Code:

qm> info qtree
bus: main-system-bus
  type System
  dev: hpet, id ""
    gpio-in 1
    dev-prop: timers = 3
    dev-prop: msi = off
    irq 32
    mmio 00000000fed00000/0000000000000400
  dev: i440FX-pcihost, id ""
    irq 0
    bus: pci.0
      type PCI
      dev: rtl8139, id ""
        dev-prop: mac = e2:c5:87:8d:4b:bf
        dev-prop: vlan = <null>
        dev-prop: netdev = net0
        dev-prop: bootindex = -1
        bus-prop: addr = 12.0
        bus-prop: romfile = ""
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        bus-prop: command_serr_enable = on
        class Ethernet controller, addr 00:12.0, pci id 10ec:8139 (sub 1af4:1100)
        bar 0: i/o at 0xc100 [0xc1ff]
        bar 1: mem at 0xf2020000 [0xf20200ff]
      dev: ich9-usb-uhci3, id "uhci-3"
        dev-prop: masterbus = "ehci.0"
        dev-prop: firstport = 4
        bus-prop: addr = 1d.2
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = on
        bus-prop: command_serr_enable = on
        class USB controller, addr 00:1d.2, pci id 8086:2936 (sub 1af4:1100)
        bar 4: i/o at 0xc240 [0xc25f]
      dev: ich9-usb-uhci2, id "uhci-2"
        dev-prop: masterbus = "ehci.0"
        dev-prop: firstport = 2
        bus-prop: addr = 1d.1
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = on
        bus-prop: command_serr_enable = on
        class USB controller, addr 00:1d.1, pci id 8086:2935 (sub 1af4:1100)
        bar 4: i/o at 0xc220 [0xc23f]
      dev: ich9-usb-uhci1, id "uhci-1"
        dev-prop: masterbus = "ehci.0"
        dev-prop: firstport = 0
        bus-prop: addr = 1d.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = on
        bus-prop: command_serr_enable = on
        class USB controller, addr 00:1d.0, pci id 8086:2934 (sub 1af4:1100)
        bar 4: i/o at 0xc200 [0xc21f]
      dev: ich9-usb-ehci1, id "ehci"
        dev-prop: freq = 1000
        dev-prop: maxframes = 128
        bus-prop: addr = 1d.7
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = on
        bus-prop: command_serr_enable = on
        class USB controller, addr 00:1d.7, pci id 8086:293a (sub 1af4:1100)
        bar 0: mem at 0xf2021000 [0xf2021fff]
        bus: ehci.0
          type USB
          dev: usb-tablet, id ""
            bus-prop: port = "6"
            addr 0.2, port 6, speed 12, name QEMU USB Tablet, attached
      dev: PIIX4_PM, id ""
        dev-prop: smb_io_base = 45312
        bus-prop: addr = 01.3
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        bus-prop: command_serr_enable = on
        class Bridge, addr 00:01.3, pci id 8086:7113 (sub 1af4:1100)
        bus: i2c
          type I2C
          dev: smbus-eeprom, id ""
            bus-prop: address = 87
          dev: smbus-eeprom, id ""
            bus-prop: address = 86
          dev: smbus-eeprom, id ""
            bus-prop: address = 85
          dev: smbus-eeprom, id ""
            bus-prop: address = 84
          dev: smbus-eeprom, id ""
            bus-prop: address = 83
          dev: smbus-eeprom, id ""
            bus-prop: address = 82
          dev: smbus-eeprom, id ""
            bus-prop: address = 81
          dev: smbus-eeprom, id ""
            bus-prop: address = 80
      dev: piix3-ide, id ""
        bus-prop: addr = 01.1
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        bus-prop: command_serr_enable = on
        class IDE controller, addr 00:01.1, pci id 8086:7010 (sub 1af4:1100)
        bar 4: i/o at 0xc000 [0xc00f]
        bus: ide.1
          type IDE
          dev: ide-drive, id "device-ide2"
            dev-prop: drive = drive-ide2
            dev-prop: logical_block_size = 512
            dev-prop: physical_block_size = 512
            dev-prop: min_io_size = 0
            dev-prop: opt_io_size = 0
            dev-prop: bootindex = -1
            dev-prop: discard_granularity = 0
            dev-prop: ver = "0.15.0"
            dev-prop: serial = "QM00003"
            bus-prop: unit = 0
        bus: ide.0
          type IDE
          dev: ide-drive, id "device-ide0"
            dev-prop: drive = drive-ide0
            dev-prop: logical_block_size = 512
            dev-prop: physical_block_size = 512
            dev-prop: min_io_size = 0
            dev-prop: opt_io_size = 0
            dev-prop: bootindex = -1
            dev-prop: discard_granularity = 0
            dev-prop: ver = "0.15.0"
            dev-prop: serial = "QM00001"
            bus-prop: unit = 0
      dev: cirrus-vga, id ""
        bus-prop: addr = 02.0
        bus-prop: romfile = "vgabios-cirrus.bin"
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        bus-prop: command_serr_enable = on
        class VGA controller, addr 00:02.0, pci id 1013:00b8 (sub 1af4:1100)
        bar 0: mem at 0xf0000000 [0xf1ffffff]
        bar 1: mem at 0xf2000000 [0xf2000fff]
        bar 6: mem at 0xffffffffffffffff [0xfffe]
      dev: PIIX3, id ""
        bus-prop: addr = 01.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = on
        bus-prop: command_serr_enable = on
        class ISA bridge, addr 00:01.0, pci id 8086:7000 (sub 1af4:1100)
        bus: isa.0
          type ISA
          dev: isa-fdc, id ""
            dev-prop: driveA = <null>
            dev-prop: driveB = <null>
            dev-prop: bootindexA = -1
            dev-prop: bootindexB = -1
            isa irq 6
          dev: port92, id ""
          dev: vmmouse, id ""
          dev: vmport, id ""
          dev: i8042, id ""
            isa irqs 1,12
          dev: isa-pit, id ""
            dev-prop: irq = 0
            dev-prop: iobase = 0x40
          dev: mc146818rtc, id ""
            dev-prop: base_year = 2000
      dev: i440FX, id ""
        bus-prop: addr = 00.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        bus-prop: command_serr_enable = on
        class Host bridge, addr 00:00.0, pci id 8086:1237 (sub 1af4:1100)
  dev: ioapic, id ""
    gpio-in 24
    irq 0
    mmio 00000000fec00000/0000000000001000
  dev: fw_cfg, id ""
    dev-prop: ctl_iobase = 0x510
    dev-prop: data_iobase = 0x511
    irq 0
    mmio ffffffffffffffff/0000000000000002
    mmio ffffffffffffffff/0000000000000002
  dev: kvmclock, id ""
    irq 0
  dev: apic, id ""
    dev-prop: id = 3
    irq 0
    mmio ffffffffffffffff/0000000000100000
  dev: apic, id ""
    dev-prop: id = 2
    irq 0
    mmio ffffffffffffffff/0000000000100000
  dev: apic, id ""
    dev-prop: id = 1
    irq 0
    mmio ffffffffffffffff/0000000000100000
  dev: apic, id ""
    dev-prop: id = 0
    irq 0
    mmio 00000000fee00000/0000000000100000

spirit · Oct 15, 2011

in your vm config file, try:

hostpci0: 04:05.0

(now we have hostpci0 , hostpci1 , 1 line by passthrough device)

c0mputerking · Oct 15, 2011

When i enter "hostpci0: 04:05.0" without quotes of course i get the error below also "hostpci1: 04.05.0" give a similar error.

Code:

start failed: command '/usr/bin/kvm -id 105 -chardev socket,id=monitor,path=/var/run/qemu-server/105.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/105.vnc,x509,password -pidfile /var/run/qemu-server/105.pid -daemonize -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,bus=ehci.0,port=6 -device pci-assign,host=04:05.0,id=hostpci0,bus=pci.0,addr=0x10 -name bluecherry -smp sockets=1,cores=4 -nodefaults -boot menu=on,order=cdn -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/iso/ubuntu-10.04-alternate-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=native -device ide-drive,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2 -drive file=/dev/vg1/vm-105-disk-1,if=none,id=drive-ide0,aio=native,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0 -m 2048 -netdev type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge -device rtl8139,romfile=,mac=E2:C5:87:8D:4B:BF,netdev=net0,bus=pci.0,addr=0x12 -cpuunits 1000' failed: exit code 1 (500)start failed: command '/usr/bin/kvm -id 105 -chardev socket,id=monitor,path=/var/run/qemu-server/105.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/105.vnc,x509,password -pidfile /var/run/qemu-server/105.pid -daemonize -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,bus=ehci.0,port=6 -device pci-assign,host=04:05.0,id=hostpci0,bus=pci.0,addr=0x10 -name bluecherry -smp sockets=1,cores=4 -nodefaults -boot menu=on,order=cdn -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/iso/ubuntu-10.04-alternate-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=native -device ide-drive,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2 -drive file=/dev/vg1/vm-105-disk-1,if=none,id=drive-ide0,aio=native,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0 -m 2048 -netdev type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge -device rtl8139,romfile=,mac=E2:C5:87:8D:4B:BF,netdev=net0,bus=pci.0,addr=0x12 -cpuunits 1000' failed: exit code 1 (500)

maxprox · Oct 16, 2011

Hello,

Please tell us when you're progressed.
For years I have worked with a VDR system (vdr-portal.de). A nice toy.
I'm waiting for the moment when I can virtualize it with Proxmox.

Regards,
maxprox

spirit · Oct 16, 2011

could you try to launch directly the vm with command line? I think you will have more detailed info on error.

/usr/bin/kvm -id 105 -chardev socket,id=monitor,path=/var/run/qemu-server/105.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/105.vnc,x509,password -pidfile /var/run/qemu-server/105.pid -daemonize -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,bus=ehci.0,port=6 -device pci-assign,host=04:05.0,id=hostpci0,bus=pci.0,addr=0x10 -name bluecherry -smp sockets=1,cores=4 -nodefaults -boot menu=on,order=cdn -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/iso/ubuntu-10.04-alternate-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=native -device ide-drive,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2 -drive file=/dev/vg1/vm-105-disk-1,if=none,id=drive-ide0,aio=native,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0 -m 2048 -netdev type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge -device rtl8139,romfile=,mac=E2:C5:87:8D:4B:BF,netdev=net0,bus=pci.0,addr=0x12 -cpuunits 1000

c0mputerking · Oct 16, 2011

Seems kvm could not open disk image

Code:

 /usr/bin/kvm -id 105 -chardev socket,id=monitor,path=/var/run/qemu-server/105.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/105.vnc,x509,password -pidfile /var/run/qemu-server/105.pid -daemonize -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,bus=ehci.0,port=6 -device pci-assign,host=04:05.0,id=hostpci0,bus=pci.0,addr=0x1 0 -name bluecherry -smp sockets=1,cores=4 -nodefaults -boot menu=on,order=cdn -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/iso/ubuntu-10.04-alternate-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=native -device ide-drive,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2 -drive file=/dev/vg1/vm-105-disk-1,if=none,id=drive-ide0,aio=native,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0 -m 2048 -netdev type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge -device rtl8139,romfile=,mac=E2:C5:87:8D:4B:BF,netdev=net0 ,bus=pci.0,addr=0x12 -cpuunits 1000 
kvm: -device pci-assign,host=04:05.0,id=hostpci0,bus=pci.0,addr=0x1: could not open disk image 0: No such file or directory

dietmar · Oct 17, 2011

c0mputerking said:
Seems kvm could not open disk image

And that is related to the hostpci option (you do not get that error when you do not use hostpci)?

spirit · Oct 17, 2011

Damn, my copy/paste add a space after "pci.0,addr=0x1....0"

try this:

Code:

 /usr/bin/kvm -id 105 -chardev socket,id=monitor,path=/var/run/qemu-server/105.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/105.vnc,x509,password -pidfile /var/run/qemu-server/105.pid -daemonize -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,bus=ehci.0,port=6 -device pci-assign,host=04:05.0,id=hostpci0,bus=pci.0,addr=0x10 -name bluecherry -smp sockets=1,cores=4 -nodefaults -boot menu=on,order=cdn -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/iso/ubuntu-10.04-alternate-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=native -device ide-drive,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2 -drive file=/dev/vg1/vm-105-disk-1,if=none,id=drive-ide0,aio=native,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0 -m 2048 -netdev type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge -device rtl8139,romfile=,mac=E2:C5:87:8D:4B:BF,netdev=net0 ,bus=pci.0,addr=0x12 -cpuunits 1000

[/QUOTE]

c0mputerking · Oct 17, 2011

A new error I guess you could call that progress, not sure what you changed the commands probalby not looking close enough i will take a better look once i get this post out. however addr-0x12 is not the dvr card is it? should be 0x10 not that i know much about hardware addresses

could not open disk image ,bus=pci.0,addr=0x12: No such file or directory

Code:

/usr/bin/kvm -id 105 -chardev socket,id=monitor,path=/var/run/qemu-server/105.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/105.vnc,x509,password -pidfile /var/run/qemu-server/105.pid -daemonize -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,bus=ehci.0,port=6 -device pci-assign,host=04:05.0,id=hostpci0,bus=pci.0,addr=0x10 -name bluecherry -smp sockets=1,cores=4 -nodefaults -boot menu=on,order=cdn -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/iso/ubuntu-10.04-alternate-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=native -device ide-drive,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2 -drive file=/dev/vg1/vm-105-disk-1,if=none,id=drive-ide0,aio=native,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0 -m 2048 -netdev type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge -device rtl8139,romfile=,mac=E2:C5:87:8D:4B:BF,netdev=net0 ,bus=pci.0,addr=0x12 -cpuunits 1000
kvm: -device rtl8139,romfile=,mac=E2:C5:87:8D:4B:BF,netdev=net0: could not open disk image ,bus=pci.0,addr=0x12: No such file or directory

c0mputerking · Oct 17, 2011

Nice to see this post is picking up some fan fare

Maxprox

PCI pass through

Renowned Member

Renowned Member

Proxmox Staff Member

Renowned Member

Proxmox Staff Member

Renowned Member

Proxmox Staff Member

Renowned Member

Distinguished Member

Distinguished Member

Renowned Member

Distinguished Member

Renowned Member

Renowned Member

Distinguished Member

Renowned Member

Proxmox Staff Member

Distinguished Member

Renowned Member

Renowned Member