Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About cartman

  • Rank
  1. cartman

    What hardware are you using?

    Bootloader: XPEnoboot 5.2-5644.5 System: Synology DSM 5.2-5644 update 3 ------------------------------------------------------------ CPU: Intel® Atom™ D525 (Pineview-D) Dual Core, 1.8GHz (13W) processor RAM: 4GB Kingston DDR3 800MHz Mainboard: Supermicro X7SPA-HF-D525 HDD: 4x WD RED 3TB - 1x HGST 4TB - 1x WD RED 5TB USB-Boot: SanDisk Ultra Fit 16GB Case: Lian Li PC-Q08B PSU: Enermax 400W ------------------------------------------------------------
  2. cartman

    Power off from the buttom

    Thank you thordrid, it works for me on a proxmox vm installation. i have tried it with your guide, but lsmod shows no evdev.ko after restart. copy evdev.ko -> /lib/modules copy S10modules -> /usr/syno/etc/rc.d/ - edit MODULES_DIR="/lib/modules/" - chmod 755 /usr/syno/etc/rc.d/ this is the working solution for me. thank you very much thordrid for the cross-compiling !!!
  3. cartman

    Power off from the buttom

    Hello everyone, i updated from XPEnoboot_DS3615xs_5.1-5022.3 to XPEnoboot_DS3615xs_5.2-5565.1 on my proxmox server. now the "vm proxmox shutdown" work anymore. bevore i updated it works with the acpi-button.tgz files from dilshodm post very well. what can i do, to bring the "vm proxmox shutdown" button to work with the latest XPEnoboot_DS3615xs_5.2-5565.1 ?? Thank you very much for your help!
  4. Many thanks for the hint! Unfortunately now I end up in error code 38, same 2nd step in disk manager install. Looks like some conflict in HDD drivers, something wired in my proxmox install (btw, fresh install, xpenology is the first VM). Maybe somebody running xpenology on proxmox 3.2 can give me a short summarize on working config? ide/virtio/... I followed the other threads here, but this gave no real success, ending up on the same step. Thanks to all and best wishes! Hello, xpenology works on proxmox 3.2 RAM ... 512MB CPU ... 1 (KVM64) Disk ... ide0 1GB (were the Nanoboot is installed) Disk ... ide1 100GB (were the Data is stored) Network ... net0 (e1000) then boot from ide0 this works for me a long time now.
  5. nanoboot works with proxmox !!! 01.... create a new kvm machine with 1 cpu (kvm64) ... 512 mb ram ... 1 network card (e1000) 02.... copy the nanoboot image into the new created kvm folder (if the vm have the number 010, replace the *** in the next steps with 010) 03.... qemu-img convert -f raw -O qcow2 /var/lib/vz/images/***/NanoBoot- /var/lib/vz/images/***/vm-***-disk-1.qcow2 04.... mount the vm-***disk-1.qcow2 as ide0 disk and boot from this disk 05.... create a new disk vm-***disk-2.qcow2 (ide1) as data disk 06.... start the vm regards