arkilee

Members
  • Content count

    10
  • Joined

  • Last visited

  • Days Won

    1

arkilee last won the day on May 12

arkilee had the most liked content!

Community Reputation

3 Neutral

About arkilee

  • Rank
    Newbie

Recent Profile Visitors

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

  1. arkilee

    Tutorial: DSM 6.x on Proxmox

    Nothing's wrong, It means that you already have "button" and "evdev" modules already loaded in the kernel. Maybe your bootloader has it already or you have run "s30acpid.sh start" several times. Try to reboot your xpenology then try to shut it down with Proxmox VE web interface to see if it works.
  2. arkilee

    Tutorial: DSM 6.x on Proxmox

    For those who are interested to be able to power off DSM 6.1.x VM via ACPI and get the shutdown working through Proxmox Virtual Environment, I have recompiled the button.ko and evdev.ko from the poweroff package of this post in order to get this working on dsm 6.1.x/DS3615xs. power-off_dsm61x_ds3615xs_x86.tar.gz
  3. arkilee

    DSM 6.1.5-15254

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 5.2 - Loader version and model: Jun's Loader v1.02b - DS3615xs (mod with added virtio) - Installation type: PROXMOX (M5A78L-M/USB3 with 2 SATA controller cards passtrhu) - Additional comments: Requires VM reboot
  4. arkilee

    Tutorial: DSM 6.x on Proxmox

    Yes it works for me now, I can save my bios now. Thanks.
  5. arkilee

    Tutorial: DSM 6.x on Proxmox

    Oh thank you, I just noticed that I didn't create a efidisk which seems to store the bios changes. LoL. Well actually I didn't know about that as I never used OVMF (UEFI) bios before. I think this may solves all the usb boot issue I guess :).
  6. arkilee

    Tutorial: DSM 6.x on Proxmox

    Yeah that's weird, I have a proxmox from 2 years ago which I did update up to 5.0-31 ... maybe something wrong with my proxmox. Can you tell me what value did you put for "boot" and "bootdisk" in your <vmid>.conf ?
  7. arkilee

    Tutorial: DSM 6.x on Proxmox

    About me to get my "HDD passthru", I did a "sata controller passthrough" to the vm. It looks like some motherboard can passtrough internal sata controller, I didn't succeed with mine. So I bought a 20$ pci-express sata iii controller, and a successfully passtrough the added sata controller. And I can see disk with real name and SMART data and all work well so far.
  8. arkilee

    Tutorial: DSM 6.x on Proxmox

    Thank you for the tips. I try UEFI bios as you said, then change boot order in bios and save it. But in my proxmox, bios change does not seem to be persistent when you poweroff the vm. It only seems be persistent on a reboot or reset; However I kinda found a way to make it boot automaticaly on the virtual usb key: - Set OVMF (UEFI) bios - Edit <vm id>.conf to set "boot: 1" (or anything else but "a c d n") With this config, the boot argument is invalid and it will not force or prioritize any boot device. Instead it seems to look for an UEFI disk to boot, and it will boot on the virtual usb key which is the only UEFI disk boot.
  9. arkilee

    Tutorial: DSM 6.x on Proxmox

    Following my last post, here is some update about some testing with my proxmox 5 running on an AMD cpu: - virtio_net : working good so far - virtio_pci : Added a virtio disk to vm, I can see it with the linux command "fdisk -l" as "/dev/vda" but it is not recognized by DSM. (can be remap with udev?) - virtio_scsi: Added a scsi disk with "virtio scsi controller" to the vm, it doesn't seems to work and I can find the following errors in "/var/log/dmesg": logs ... [Sun Sep 17 22:46:41 2017] scsi9 : Virtio SCSI HBA [Sun Sep 17 22:46:41 2017] BUG: unable to handle kernel NULL pointer dereference at 00000000000001d8 [Sun Sep 17 22:46:41 2017] IP: [<ffffffffa01c9b80>] virtscsi_queuecommand_single+0x10/0x30 [virtio_scsi] [Sun Sep 17 22:46:41 2017] PGD 78d9f067 PUD 795d5067 PMD 0 [Sun Sep 17 22:46:41 2017] Oops: 0000 [#1] SMP [Sun Sep 17 22:46:41 2017] Modules linked in: virtio_scsi(+) virtio_blk virtio_pci virtio_mmio virtio_ring virtio mpt3sas mpt2sas(O) megaraid_sas ata_piix mptctl mptsas mptspi mptscsih mptbase scsi_transport_spi megaraid megaraid_mbox megaraid_mm vmw_pvscsi BusLogic usb_storage xhci_hcd uhci_hcd ohci_hcd ehci_pci ehci_hcd usbcore usb_common el000(O) [Sun Sep 17 22:46:41 2017] CPU: 0 PID: 4157 Comm: insmod Tainted: G O 3.10.102 #15152 [Sun Sep 17 22:46:41 2017] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014 [Sun Sep 17 22:46:41 2017] task: ffff88007c5ba800 ti: ffff88007c16c000 task.ti: ffff88007c16c000 [Sun Sep 17 22:46:41 2017] RIP: 0010:[<ffffffffa01c9b80>] [<ffffffffa01c9b80>] virtscsi_queuecommand_single+0x10/0x30 [virtio_scsi] [Sun Sep 17 22:46:41 2017] RSP: 0000:ffff88007c16f898 EFLAGS: 00010293 [Sun Sep 17 22:46:41 2017] RAX: ffff88007c179000 RBX: ffff880078c42480 RCX: 0000000000000000 [Sun Sep 17 22:46:41 2017] RDX: ffff880078c42480 RSI: ffff880078c42480 RDI: ffff88007c179000 [Sun Sep 17 22:46:41 2017] RBP: 0000000000000000 R08: ffff88007c16f7d8 R09: ffff88007c16f7c8 [Sun Sep 17 22:46:41 2017] R10: ffff88007c174dc0 R11: 0000000000000000 R12: ffff88007c179000 [Sun Sep 17 22:46:41 2017] R13: ffff880076b82078 R14: ffff88007c268048 R15: ffff880078c42480 [Sun Sep 17 22:46:41 2017] FS: 00007fccd1052700(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000 [Sun Sep 17 22:46:41 2017] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [Sun Sep 17 22:46:41 2017] CR2: 00000000000001d8 CR3: 0000000078c73000 CR4: 00000000000006b0 [Sun Sep 17 22:46:41 2017] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [Sun Sep 17 22:46:41 2017] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [Sun Sep 17 22:46:41 2017] Stack: [Sun Sep 17 22:46:41 2017] ffffffff8130908b ffff88007c179000 ffff88007c268000 ffff88007c179000 [Sun Sep 17 22:46:41 2017] ffff880076b2f210 ffffffff8130ed60 ffff88007c268170 ffffffff810b3c73 [Sun Sep 17 22:46:41 2017] ffffffff810c9036 ffff88007ffcb240 ffff880076b82078 0000000000000001 [Sun Sep 17 22:46:41 2017] Call Trace: [Sun Sep 17 22:46:41 2017] [<ffffffff8130908b>] ? scsi_dispatch_cmd+0xdb/0x370 [Sun Sep 17 22:46:41 2017] [<ffffffff8130ed60>] ? scsi_request_fn+0x2c0/0x4e0 [Sun Sep 17 22:46:41 2017] [<ffffffff810b3c73>] ? mempool_alloc+0x43/0x130 [Sun Sep 17 22:46:41 2017] [<ffffffff810c9036>] ? pcpu_next_pop+0x36/0x50 [Sun Sep 17 22:46:41 2017] [<ffffffff8124d4fa>] ? __blk_run_queue+0x2a/0x40 [Sun Sep 17 22:46:41 2017] [<ffffffff81253a35>] ? blk_execute_rq_nowait+0x65/0xf0 [Sun Sep 17 22:46:41 2017] [<ffffffff81253b17>] ? blk_execute_rq+0x57/0xd0 [Sun Sep 17 22:46:41 2017] [<ffffffff81250000>] ? __blk_end_request_cur+0x20/0x40 [Sun Sep 17 22:46:41 2017] [<ffffffff8112c155>] ? bio_phys_segments+0x15/0x20 [Sun Sep 17 22:46:41 2017] [<ffffffff8125392d>] ? blk_rq_map_kern+0xad/0x150 [Sun Sep 17 22:46:41 2017] [<ffffffff8124f620>] ? blk_get_request+0x50/0xc0 [Sun Sep 17 22:46:41 2017] [<ffffffff8130dadf>] ? scsi_execute+0x11f/0x1d0 [Sun Sep 17 22:46:41 2017] [<ffffffff8130f523>] ? scsi_execute_req_flags+0x83/0xe0 [Sun Sep 17 22:46:41 2017] [<ffffffff8131210e>] ? scsi_probe_and_add_lun+0x1ee/0xf70 [Sun Sep 17 22:46:41 2017] [<ffffffffa01c9405>] ? virtscsi_target_alloc+0x15/0x40 [virtio_scsi] [Sun Sep 17 22:46:41 2017] [<ffffffff81311bc6>] ? scsi_alloc_target+0x276/0x310 [Sun Sep 17 22:46:41 2017] [<ffffffff813131f7>] ? __scsi_scan_target+0xc7/0x5c0 [Sun Sep 17 22:46:41 2017] [<ffffffff81268e0e>] ? kobject_uevent_env+0x11e/0x4a0 [Sun Sep 17 22:46:41 2017] [<ffffffff812f291e>] ? get_device+0xe/0x20 [Sun Sep 17 22:46:41 2017] [<ffffffffa00ceeb2>] ? spi_target_match+0x12/0x94 [scsi_transport_spi] [Sun Sep 17 22:46:41 2017] [<ffffffff81317220>] ? raid_match+0x10/0x40 [Sun Sep 17 22:46:41 2017] [<ffffffff81313824>] ? scsi_scan_channel.part.12+0x54/0x70 [Sun Sep 17 22:46:41 2017] [<ffffffff813139a1>] ? scsi_scan_host_selected+0xc1/0x150 [Sun Sep 17 22:46:41 2017] [<ffffffffa01bd6f0>] ? vp_interrupt+0x60/0x60 [virtio_pci] [Sun Sep 17 22:46:41 2017] [<ffffffffa01af1f4>] ? virtio_dev_probe+0x114/0x140 [virtio] [Sun Sep 17 22:46:41 2017] [<ffffffff812f69aa>] ? really_probe+0x5a/0x220 [Sun Sep 17 22:46:41 2017] [<ffffffff812f6c31>] ? __driver_attach+0x81/0x90 [Sun Sep 17 22:46:41 2017] [<ffffffff812f6bb0>] ? __device_attach+0x40/0x40 [Sun Sep 17 22:46:41 2017] [<ffffffff812f4ca3>] ? bus_for_each_dev+0x53/0x90 [Sun Sep 17 22:46:41 2017] [<ffffffff812f6148>] ? bus_add_driver+0x158/0x250 [Sun Sep 17 22:46:41 2017] [<ffffffffa01cd000>] ? 0xffffffffa01ccfff [Sun Sep 17 22:46:41 2017] [<ffffffff812f7238>] ? driver_register+0x68/0x150 [Sun Sep 17 22:46:41 2017] [<ffffffffa01cd000>] ? 0xffffffffa01ccfff [Sun Sep 17 22:46:41 2017] [<ffffffffa01cd081>] ? init+0x81/0xc7 [virtio_scsi] [Sun Sep 17 22:46:41 2017] [<ffffffffa01cd000>] ? 0xffffffffa01ccfff [Sun Sep 17 22:46:41 2017] [<ffffffff810003aa>] ? do_one_initcall+0xea/0x140 [Sun Sep 17 22:46:41 2017] [<ffffffff8108804f>] ? load_module+0x1d0f/0x2060 [Sun Sep 17 22:46:41 2017] [<ffffffff81084f00>] ? store_uevent+0x40/0x40 [Sun Sep 17 22:46:41 2017] [<ffffffff81088431>] ? SYSC_init_module+0x91/0xc0 [Sun Sep 17 22:46:41 2017] [<ffffffff814ae132>] ? system_call_fastpath+0x16/0x1b [Sun Sep 17 22:46:41 2017] Code: 4c 8d 6c 0d 08 4c 89 6b 08 eb b2 29 d1 39 ca 77 e5 eb f8 0f 1f 84 00 00 00 00 00 48 8b 0e 48 89 f8 48 89 f2 48 8b 89 68 01 00 00 <48> 8b 89 d8 01 00 00 f0 ff 41 04 48 8d bf 08 05 00 00 48 8d b0 [Sun Sep 17 22:46:41 2017] RIP [<ffffffffa01c9b80>] virtscsi_queuecommand_single+0x10/0x30 [virtio_scsi] [Sun Sep 17 22:46:41 2017] RSP <ffff88007c16f898> [Sun Sep 17 22:46:41 2017] CR2: 00000000000001d8 [Sun Sep 17 22:46:41 2017] ---[ end trace c82587c395eefaa2 ]--- [Sun Sep 17 22:46:41 2017] bromolow_synobios: module license 'Synology Inc.' taints kernel. ... Hide Maybe better to stick with sata disk for now.
  10. arkilee

    Tutorial: DSM 6.x on Proxmox

    Hi there, Last night, I have compiled and added virtio modules in 1.02b jun's loader following the tutorial found in xpenology forum. It seems to work well so far on DSM 6.1.3-15152 Update 4 (synology_bromolow_3615xs), as you can see here: For those who want to give a try, you can find the synoboot in attach. About booting automaticaly on the virtual usb disk when starting a vm, it doesn't work for me. In my <Vm id>.conf, I set boot: 3 which is my usb boot number when hit F12, but it doesn't work. And in my proxmox 5.0-31, I cannot find the number boot option in the "man qm" which only says 1 to 4 letters is allowed between "a c d n" : ... -boot [acdn]{1,4} (default = cdn) Boot on floppy (a), hard disk (c), CD-ROM (d), or network (n). -bootdisk (ide|sata|scsi|virtio)\d+ Enable booting from specified disk. ... Maybe one of you can help me about that? ... for now I am doing manual boot with F12. synoboot_jun102b_virtio.zip