loukaniko85

Members
  • Posts

    23
  • Joined

Recent Profile Visitors

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

loukaniko85's Achievements

Newbie

Newbie (1/14)

7

Reputation

  1. enabled custom CSM in my bios Launch Storage OpROM Policy - UEFI only Launch Video OpROM Policy - Legacy only All working thanks gents.
  2. I disabled csm and now vms can turn on without that error - though no display and vm log show 2021-08-09T02:16:33.519687Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1df, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519692Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e0, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519703Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e1, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519714Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e2, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519720Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e3, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519726Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e4, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519732Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e5, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519738Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e6, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519743Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e7, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519748Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e8, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519753Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e9, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519758Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ea, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519763Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1eb, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519768Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ec, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519773Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ed, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519779Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ee, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519784Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ef, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519789Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f0, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519795Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f1, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519800Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f2, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519805Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f3, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519810Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f4, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519815Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f5, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519820Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f6, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519825Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f7, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519831Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f8, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519836Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f9, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519841Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fa, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519846Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fb, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519851Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fc, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519856Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fd, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519861Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fe, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519866Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ff, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519871Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd200, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519876Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd201, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519882Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd202, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519887Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd203, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519892Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd204, 0x0,1) failed: Device or resource busy 2021-08-09T02:16:33.519897Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd205, 0x0,1) failed: Device or resource busy
  3. sadly no, same issue; though i do have 2 nvmes; 1 passthrough and 1 cache.. perhaps that is why it is showing as being loaded. Also, am having same error on other vms, which do not have the nvme passthrough.. - seems to only occur with gpu passthrough. nvme passes, usb controller passes..
  4. thanks; hopefully someone can assist soon.. or ill have to rollback. I need the vms jj-diagnostics-20210808-1624.zip
  5. jj-diagnostics-20210808-1624.zip This seems to be the issue; ErrorWarningSystem Loading config from /boot/config/vfio-pci.cfg BIND=0000:23:00.0|1987:5016 0000:2e:00.0|10de:2484 0000:2e:00.1|10de:228b --- Processing 0000:23:00.0 1987:5016 Vendor:Device 1987:5016 found at 0000:23:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:23:00.0/iommu_group/devices/0000:23:00.0 Binding... chown: cannot access '/dev/vfio/25': No such file or directory Error: unable to adjust group ownership of /dev/vfio/25 --- Processing 0000:2e:00.0 10de:2484 Vendor:Device 10de:2484 found at 0000:2e:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:2e:00.0/iommu_group/devices/0000:2e:00.0 /sys/bus/pci/devices/0000:2e:00.0/iommu_group/devices/0000:2e:00.1 Binding... chown: cannot access '/dev/vfio/32': No such file or directory Error: unable to adjust group ownership of /dev/vfio/32 --- Processing 0000:2e:00.1 10de:228b Vendor:Device 10de:228b found at 0000:2e:00.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:2e:00.1/iommu_group/devices/0000:2e:00.0 /sys/bus/pci/devices/0000:2e:00.1/iommu_group/devices/0000:2e:00.1 Binding... 0000:2e:00.0 already bound to vfio-pci 0000:2e:00.1 already bound to vfio-pci chown: cannot access '/dev/vfio/32': No such file or directory Error: unable to adjust group ownership of /dev/vfio/32 --- vfio-pci binding complete Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Aug 8 08:42 0000:23:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:01.0/0000:23:00.0 lrwxrwxrwx 1 root root 0 Aug 8 08:42 0000:2e:00.0 -> ../../../../devices/pci0000:00/0000:00:03.1/0000:2e:00.0 lrwxrwxrwx 1 root root 0 Aug 8 08:42 0000:2e:00.1 -> ../../../../devices/pci0000:00/0000:00:03.1/0000:2e:00.1 ls -l /dev/vfio/ ls: cannot access '/dev/vfio/': No such file or directory
  6. upgraded without error; though now my vms, with gpu passthrough, are unable to start. pop up starting; internal error: qemu unexpectedly closed the monitor and the log stating; qemu-system-x86[4682]: segfault at a8 ip 0000558eecc44fb7 sp 00007ffc61aa2cb0 error 4 in qemu-system-x86_64[558eec97a000+53f000] Help please (edit - vms with vnc, work fine)
  7. Fantastic; working perfectly. Thank you. On a side note, any news/eta on an updated Libvirt version?
  8. Add USER and PASS variables in container to set authentication.
  9. Thank you sir - you're correct. I am now able to connect.
  10. I then get this. I have changed the vm libvert storage location from its default - perhaps this is why.
  11. I am using 32GB of ECC ram @ 2666 - one of the Kingstons listed on the supported list for the MB.
  12. I have installed the IPMI plugin and everything is displayed correctly; fan control is something I am still unable to rectify. It states fan is not configured.
  13. actually really well - everything is working perfectly.