November 5, 20169 yr I set up the VM per the LimeTech instructions, but I am not able to get the VM to pass through my GTX 970. I was able to get an Ubuntu instance to work with the card previously, but since a recent USB corruption and re-registration, that is not working either. Attached diag. TIA. largest-diagnostics-20161105-1504.zip
November 6, 20169 yr Nov 4 18:19:10 Tower emhttp: shcmd (578): mkdir -p /mnt/cache Nov 4 18:19:10 Tower emhttp: shcmd (579): set -o pipefail ; mount -t btrfs,xfs,reiserfs -o noatime,nodiratime /dev/sdd1 /mnt/cache |& logger Nov 4 18:19:10 Tower root: mount: wrong fs type, bad option, bad superblock on /dev/sdd1, Nov 4 18:19:10 Tower root: missing codepage or helper program, or other error Nov 4 18:19:10 Tower root: Nov 4 18:19:10 Tower root: In some cases useful info is found in syslog - try Nov 4 18:19:10 Tower root: dmesg | tail or so. Nov 4 18:19:10 Tower emhttp: err: shcmd: shcmd (579): exit status: 32 Nov 4 18:19:10 Tower emhttp: mount error: No file system (32) Nov 4 18:19:10 Tower emhttp: shcmd (580): umount /mnt/cache |& logger Nov 4 18:19:10 Tower root: umount: /mnt/cache: not mounted Nov 4 18:19:10 Tower emhttp: shcmd (581): rmdir /mnt/cache Nov 4 18:19:10 Tower emhttp: shcmd (582): sync Your cache drive appears to have failed? What sort of custom mounting or partitioning is this? It contains three partitions, and is trying to mount sdd1 as the cache. (Check your 250GB SSD.)
November 6, 20169 yr Author Is there a way of formatting it for use as a cache disk in the GUI? That disk was my old OS disk, which I made into the virtual machine I am asking about in this post. After the conversion I assigned it as cache.
November 6, 20169 yr Is there a way of formatting it for use as a cache disk in the GUI? That disk was my old OS disk, which I made into the virtual machine I am asking about in this post. After the conversion I assigned it as cache. Stop the array, and change the file system type for the cache drive from "auto" to something else. If only planning on using a single cache drive, use XFS. If planning in future on creating a cache pool, choose btrfs When starting the array, it'll prompt you to format the drive
November 6, 20169 yr Penguin could not start due to missing USB device. Windows 7 could not start due to inaccessible vdisk1.img on the "domains" share. Interesting excerpts from syslog regarding your GTX 970: Nov 3 18:54:22 Tower kernel: pci 0000:03:00.0: [10de:13c2] type 00 class 0x030000 Nov 3 18:54:22 Tower kernel: pci 0000:03:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff] Nov 3 18:54:22 Tower kernel: pci 0000:03:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref] Nov 3 18:54:22 Tower kernel: pci 0000:03:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref] Nov 3 18:54:22 Tower kernel: pci 0000:03:00.0: reg 0x24: [io 0xcc80-0xccff] Nov 3 18:54:22 Tower kernel: pci 0000:03:00.0: reg 0x30: [mem 0xf7e00000-0xf7e7ffff pref] Nov 3 18:54:22 Tower kernel: pci 0000:03:00.1: [10de:0fbb] type 00 class 0x040300 Nov 3 18:54:22 Tower kernel: pci 0000:03:00.1: reg 0x10: [mem 0xf7dfc000-0xf7dfffff] ... Nov 3 18:54:22 Tower kernel: vgaarb: setting as boot device: PCI:0000:03:00.0 Nov 3 18:54:22 Tower kernel: vgaarb: device added: PCI:0000:03:00.0,decodes=io+mem,owns=io+mem,locks=none Nov 3 18:54:22 Tower kernel: vgaarb: loaded Nov 3 18:54:22 Tower kernel: vgaarb: bridge control possible 0000:03:00.0 ... Nov 3 18:54:22 Tower kernel: pci 0000:03:00.0: Video device with shadowed ROM ... Nov 3 18:54:22 Tower kernel: DMAR: Hardware identity mapping for device 0000:03:00.0 Nov 3 18:54:22 Tower kernel: DMAR: Hardware identity mapping for device 0000:03:00.1 ... Nov 3 18:54:22 Tower kernel: iommu: Adding device 0000:03:00.0 to group 12 Nov 3 18:54:22 Tower kernel: iommu: Adding device 0000:03:00.1 to group 12 ... Nov 4 18:19:25 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Nov 4 18:19:25 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:20:58 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Nov 4 18:20:58 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:22:53 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Nov 4 18:22:53 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:24:12 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:24:16 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x1e@0x258 Nov 4 18:24:16 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x19@0x900 ... Nov 4 18:24:18 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents Nov 4 18:24:18 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents ... Nov 4 18:30:33 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Nov 4 18:30:38 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:30:41 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x1e@0x258 ... Nov 4 18:30:43 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents Nov 4 18:30:43 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents ... Nov 4 18:32:28 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:33:08 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:33:12 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x1e@0x258 ... Nov 4 18:33:14 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents Nov 4 18:33:14 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents ... Nov 4 18:36:14 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:37:24 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:37:28 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x1e@0x258 ... Nov 4 18:37:30 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents Nov 4 18:37:30 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents ... Nov 4 18:43:43 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:47:42 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 4 18:47:45 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x1e@0x258 ... Nov 4 18:47:47 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents Nov 4 18:47:47 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents ... Nov 4 18:50:48 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 5 13:35:38 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Nov 5 13:35:38 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 5 13:56:22 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Nov 5 13:56:22 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 5 14:36:48 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 5 14:36:52 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x1e@0x258 ... Nov 5 14:36:54 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents Nov 5 14:36:54 Tower kernel: vfio-pci 0000:03:00.0: Invalid ROM contents ... Nov 5 14:37:14 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem ... Nov 5 14:44:36 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem So. IOMMU doesn't like the ROM contents. And it appears you're forwarding your boot device to a VM. Special care must be taken when doing that. E1: Yup, that ROM contents issue is probably due to passing your primary GPU through. You'll likely need to acquire a good copy of the ROM BIOS for the card and pass it through your VM configuration.
November 6, 20169 yr Author I have a basically useless GPU that I could add in here as well. Would having another in the machine resolve the issue? Weird that it worked for Penguin before. How would I install/apply the ROM BIOS once I found it? Sorry, very very new to this.
Archived
This topic is now archived and is closed to further replies.