-
Posts
314 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by killeriq
-
-
Please why is "Log" window all Black/White? Now is harder to quick read for errors etc.
Thanks
-
Please fix this issue on all Ryzen 3xxx series - seems like its happening on all chipset X370,X470,X570
My small workaround
AMD Starship/Matisse PCIe Dummy Function | Non-Essential Instrumentation (0c:00.0)
Jul 5 13:02:30 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 1023ms after FLR; waiting Jul 5 13:02:32 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 2047ms after FLR; waiting Jul 5 13:02:35 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 4095ms after FLR; waiting Jul 5 13:02:40 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 8191ms after FLR; waiting Jul 5 13:02:50 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 16383ms after FLR; waiting Jul 5 13:03:07 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 32767ms after FLR; waiting Jul 5 13:03:42 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 65535ms after FLR; giving up Jul 5 13:03:43 unRAIDTower kernel: clocksource: timekeeping watchdog on CPU10: Marking clocksource 'tsc' as unstable because the skew is too large: Jul 5 13:03:43 unRAIDTower kernel: clocksource: 'hpet' wd_now: b4700ed2 wd_last: b3954a18 mask: ffffffff Jul 5 13:03:43 unRAIDTower kernel: clocksource: 'tsc' cs_now: 1d337ecfa60 cs_last: 1d337dd658c mask: ffffffffffffffff Jul 5 13:03:43 unRAIDTower kernel: tsc: Marking TSC unstable due to clocksource watchdog Jul 5 13:03:43 unRAIDTower kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jul 5 13:03:43 unRAIDTower kernel: sched_clock: Marking unstable (510899129422, -8570651)<-(510996221197, -105679272) Jul 5 13:03:45 unRAIDTower kernel: clocksource: Switched to clocksource hpet
-
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. -
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
-
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
-
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
Unraid OS version 6.10.0-rc3 available
-
-
-
-
-
in Prereleases
Posted
Yeah over there is this option and with colors
But why is gone from here? it's much easier/faster to use this Log for quick check, but without colors is not quick anymore