vizkoze

I tried that but that didn't work for me. in the vm settings, ACPI support = yes KVM hardware virtualisation = yes Qemu guest Agent = false qm shutdown 101 (= my vmid) returns shutdown timeout qm stop 101 is ok but i get System booted up from an improper shutdown. in my logs. even tried qm shutdown 101 --timeout 90 but didn't work either.

Just an update: i reverted to DS3615xs with dsm DSM 7.1.1-42962 Update 2 and the virtio network interface is much quicker: iperf3 from WIN10 fysical machine tot DSM guest gives me 767 Mbits/sec. I can live with that number.

Hi, just came here to say my virtualized setup on proxmox works. I installed it using arpl 1.0beta 2 with DS3622xs+ DSM 7.1.1-42962 Update 2 selected the necessary modules V9FS and ACPID and build the loader successfully. I experience a significant slowdown on the virtio network driver when doing an iperf3 speed test between several hosts: WIN10 is physical machine connected on gigabit network swich when running iperf3 From win10 to proxmox host : 933 Mbits/sec -> normal speed from win10 tot debian guest virtio nic: 930Mbits/sec -> normal speed from win10 tot dsm virtio nic: 220Mbits/sec -> abnormal speed from proxmox host to debian guest virtio nic: 7.35 Gbits/sec -> acceptable from proxmox host to dsm guest virtio nic: 6.05 Gbits/sec -> acceptable I tried changing the nic to intel E1000 as a virtual NIC. speed between win10 machine and dsm guest, speed improves to 400Mbits/sec but speed between virtual hosts slows down to same 400Mbits/s The network card on the proxmox host is a builtin Realtek RTL8111GR I wonder if there is a problem with the virtio network drivers and this version of DSM? I noticed also that acpid button doenst work when invoking shutdown from proxmox console. Maybe that modules isn't compatible with this version of DSM?

I had the same problems with my setup and removing the spaces before and after the "_g_" in /etc/synoinfo.conf resolved that wol_enabled_options="g" instead of wol_enabled_options=" g " EDIT: I checked my syslinux.cfg too: my mac1=aa:bb:cc:dd:ee:ff (<-this is just a dummy number!) is seperated with colons (":")

Just go give some info on my workaround: I burned a nanoboot.iso to a dvd disk and i'm booting from that instead. It works fine.

You could try writing the boot.iso to a cd or dvd disk and boot from that if the old computers have an optical drive. I do it like that because my motherboard had problems booting from usb.

I had the same issues. no more disks after update 4. so i went and reinstalled from scratch applied update 3 and left it that way. i'll just wait until they sort that bug out...

Hi everyone, i'm new to this community and I would like to share a weird problem i have using an old repurposed computer that was lying around the house. The problem i'm facing is succesfully starting nanoboot or gnuboot on a usb stick. currently i'm using xpenology x64 5.0.4493 with Nanoboot-5.0.3.2 DSM 5.0-4493 X64. My motherboard is an old asus A8N-E motherboard with a athlon x2 3800+ cpu, 1gig of memory and a 250gig satadrive. When setting the correct bootorder in my bios, the board starts loading the bootloader from usb, after 10 seconds, it selects automatically the first item on the menu, beiing nanoboot. after that step, i get another bootloader with only one option. when the board selects that item after 10 seconds, there is a error stating not known executable found and starts the whole process over. When I start up the computer manually and selecting the boot-options menu by pressing F8 and manually selecting nanoboot before the timeout, i get another bootimg with one option, again by pressing enter before timeout, i sucessfully start DSM5.0.4493 with the latest update. Now this manual procedure is ok for testing purposes, but i'd like to finalize my build and have the computer to boot automatically and starting up correctly. Does anyone knows what could be the problem? should i burn the bootloader to a cdrom and try it that way? are there any other options for booting a usb disk? Vince