Jump to content

killeriq

Members
  • Content Count

    247
  • Joined

  • Last visited

Community Reputation

5 Neutral

About killeriq

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Nothing to do with VM , as ive explained this only happens with latest Bios, when i revert 1 version back, all good again. Ive found few topics about the D3 error on Threadripper like 1y ago, same now with latest Bios
  2. on 6808 bios - issue fixed with "disabling UEFI boot mode" on Unraid Flash drive on 6903 bios - still D3 error
  3. FYI: it might help someone...i'm on v6.7.0rc7 Today ive spend couple of hours investigating what has changed after i did bios update v 6903 of Asus Crosshair Hero VI, ive started to get "2019-04-15T18:30:20.016943Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3" When i force close VM and try to start again, it wont run and is giving "internal error: Unknown PCI header type '127'" So then ive tried to go back 1 version down - v6808, D3 issue was gone. Soon as i've enabled "Permit UEFI boot mode" and booted in UEFI mode 1 card from 2x1080ti in VM is giving those errors. So ive disabled UEFI again and it was working fine. Latest FW 6903 is not working well with VMs, no clue where/what to change 2019-04-15T16:35:43.954749Z qemu-system-x86_64: -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x8,romfile=/mnt/cache/isos/Asus.GTX1080Ti.rom: Failed to mmap 0000:0b:00.0 BAR 3. Performance may be slow 2019-04-15T16:35:45.317557Z qemu-system-x86_64: vfio: Cannot reset device 0000:02:00.0, depends on group 16 which is not owned. 2019-04-15T16:35:46.387464Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 34 which is not owned. 2019-04-15T16:35:47.407551Z qemu-system-x86_64: vfio: Cannot reset device 0000:02:00.0, depends on group 16 which is not owned. 2019-04-15T16:35:47.520017Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 34 which is not owned. 2019-04-15T16:36:27.321705Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x40a8, 0x2bffe101,8) failed: Device or resource busy 2019-04-15T16:36:27.321756Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15000, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321767Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15008, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321780Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15010, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321789Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15018, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321801Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15020, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321812Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15028, 0x0,8) failed: Device or resource busy
  4. Hello, seems like you are still using "old msg" - the "No" is not present anymore in settings....there are 4 other choices Warning: Your system has booted with the PCIe ACS Override setting enabled. The below list doesn't not reflect the way IOMMU would naturally group devices. To see natural IOMMU groups for your hardware, go to the VM Settings page and set the PCIe ACS Override setting to No.
  5. tried to go to bios 6808 and now im getting those errors in VM (no D3 anymore) 2019-04-15T15:28:06.280241Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0x9008c, 4) failed: Device or resource busy 2019-04-15T15:28:06.280260Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa0018, 0x40088,4) failed: Device or resource busy 2019-04-15T15:28:06.280274Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa001c, 0x0,4) failed: Device or resource busy 2019-04-15T15:28:06.280289Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa0020, 0x40084,4) failed: Device or resource busy 2019-04-15T15:28:06.280304Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa0024, 0x0,4) failed: Device or resource busy 2019-04-15T15:28:07.610273Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:15.802311Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:23.994328Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:32.186328Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:40.378322Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:41.703547Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xfdf068c, 0x1,4) failed: Device or resource busy --- So tried to change Settings -> VM Manager -> PCIe ACS override: to "Downstream" before i had "Both" Last time i remember there was only YES/NO option not sure with which OS update it got extended... unraidtower-diagnostics-20190415-1536.zip
  6. @limetech - Im on Version 6.7.0-rc7 2019-04-03 and just upgraded my ASUS CROSSHAIR VI HERO bios to Version 6903 - 2019/04/11 and i start to get this issue now When i Run the VM 1st time it starts but it wont start mining, to i power OFF the VM and try to start again - getting "internal error: Unknown PCI header type '127'" In Logs: 2019-04-15T12:24:56.897909Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2019-04-15T12:24:56.902880Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2019-04-15T12:28:28.784776Z qemu-system-x86_64: terminating on signal 15 from pid 14010 (/usr/sbin/libvirtd) 2019-04-15 12:28:31.422+0000: shutting down, reason=shutdown ---------- Should i roll back BIOS update or what options i've got? thanks unraidtower-diagnostics-20190415-1234.zip
  7. Hello, i just installed this Docker ...used LXTerminal to run "sudo apt get update" but is asking for password and no clue what is it? Thanks EDIT: if i install there somehting it get wiped after reboot?! Ive spend an hour installing weewx and seems like its gone
  8. hmm so seems like all changes of such "clone" needs to be done only in "raw xml" not in UI, otherwise it wont save/change it
  9. Adding one more note - seems like i was manually editing/comparing the XML , also able to "update" so done it this way again. Anyway would be nice feature to have - Cloning VMs with same Disk/OS but different CPU/RAM/GPU settings via UI Thanks
  10. Hello, I have setup some time ago Windows 10 VM - with Pass-through 1080ti cards, but when i dont need them and VM is OFF, they are in other VM - Linux and do some mining. So i cloned the Windows 10 VM and used the same disk, instead 108ti im using VNC so this way i can run without any "real card". Problems are with those parts: 1. In 1080ti VM is the IMG in "/mnt/user/domains/Windows 10-GPU/vdisk2.img" even i set location as "Manual" and save, next time i open setting its again on "Auto" with "/mnt/user/domains/Windows 10-VNC/vdisk2.img" which doest exist. EDIT: After i run Win10 VNC VM im able to see the 2nd disk in System as D drive (same as in VM-GPU) 2. When i want to change CPU cores or RAM amount and i hit save it get stuck in this stage for ages, when i open VMS again , values are the same Im think i was able to change it before, but now not anymore Changes are working in "original" Windows 10 GPU VM, but not in Windows VNC VM - so not sure which part is causing it... Thanks
  11. Anyone? or how to get those containers into Unraid? seems like QNAP has those options Thanks
  12. When i try to change amount of RAM or CPU in VM it get stuck in this stage: Not sure if this was present in previous versions... Thanks
  13. i left it default, cos i didnt thought it can grow that much i was more worried about InfluxDB. So u think backup flows, wipe NodeRed reinstall (with some other data path) and put flows back? EDIT: I just checked now /appdata folder and "nodered" is not even there, so is only inside IMG