Rumen Posted May 23, 2023 Share #1 Posted May 23, 2023 Hi, i can't full shutdown or reboot DSM 7.2, Arc Loader 23.5.53, DS3622xs+, build 64561, addons restart, acpid, button all is enabled on real pc Gigabyte brix GB-BRi7H-10710 (rev. 1.0), after i pressing from profile shutdown or reboot dsm not full stop stuck on arc loader and do noting ip address in onlain and no option for comands for ssh, need to press power button on pc for hard shutdown, only way to turn on again arc loader, pc not restart or shutdown from dsm web. Quote Link to comment Share on other sites More sharing options...
Loredan Posted May 23, 2023 Share #2 Posted May 23, 2023 It's better to create Issues for the ARC author. Quote Link to comment Share on other sites More sharing options...
AuxXxilium Posted May 23, 2023 Share #3 Posted May 23, 2023 And again: DSM 7.2 has no ACPI support atm. So you need to use shutdown from inside dsm. 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted May 23, 2023 Share #4 Posted May 23, 2023 (edited) I may be wrong but using ARPL-i18n from @wjz304 I was able to shutdown my VM from Proxmox GUI button... [ 3.457041] ACPI: Power Button [PWRF] Edited May 23, 2023 by Orphée Quote Link to comment Share on other sites More sharing options...
nadiva Posted July 26 Share #5 Posted July 26 I only do improper shutdowns, on all DSM VMs (Arc). I simply restart the host. On one machine with NVME passthrough it made incredible issue of NVME getting corrupted each time, following several days of reinstallation. To atop this, i've had to make sure initrd allocates the drive to vfio. So i can recommned putting disk drive codes fetched from lspci -n to /etc/modprobe.d/vfio.conf. options vfio-pci ids=XXXX:YYYY,XXXX:YYYY Either OS or possibly even BIOS (proactive installation of vendor software) could fiddle with the drive. I'd also welcome any news on Arc ACPI. Quote Link to comment Share on other sites More sharing options...
nadiva Posted August 2 Share #6 Posted August 2 Just follow up on VM reboots, someone might find it useful. VFIO setting stopped the corruption 100% as it was proven by many tests. On the KVM host, the reboot can include waiting for VMs by enabling the service systemctl enable libvirt-guests.service I can't comprehend why this is not on by default. Even the config needs to be created: mcedit /etc/sysconfig/libvirt-guests ON_BOOT=ignore #eventually controlled by libvirtd or cockpit-machines ON_SHUTDOWN=shutdown #we don't need to stupid VM snapshots SHUTDOWN_TIMEOUT=300 #timeout, usually reboot will now take like 3minutes, instead of premature 30sec PARALLEL_SHUTDOWN=2 #enable parallel shutdown of machines, of course So now I have safe reboots, as tested again. All works except "ice" drivers on Epyc baseline. Love the loader. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.