fonix232

Tutorial: DSM 6.x on Proxmox

Recommended Posts

On 11/06/2017 at 11:55 PM, arm4dillo said:

Jun's loader doesnt seem to support virtio_net and Virtio_scsi. So with Network: VirtIO paravirtualized doesnt seem to work and HDD: scsi doenst seem to work. I'm using Proxmox 5.0 beta2.

 

Maby someone else (Proxmox user) can try/test to get Network and HDD (VirtIO paravirtualized and scsi) to work ?

 

Yes, indeed, virtio drivers are not included, so let's stick with the regular stuff.

 

On 13/06/2017 at 6:42 AM, lemon55 said:

In fact, everything is much simpler!

1. Create HDD, I did SATA0, RAW format (because synology.img is a RAW disk)

2. Replace the resulting disk**1**.raw file with synology.img (where it lies) with renaming.

3. In the UI, we remove the disk (once!). It will become disabled. Then click on it two times - connect sata0, raw. It will be displayed as 50mb.

4. Profit!!!

Only e1000, this has already been discussed - Virtio does not work!

 

I did the USB workaround so e.g. updates won't wipe that disk. This way it is exactly the same as booting from an actual USB stick on barebones. Harder to achieve but you don't need to always overwrite the boot disk.

 

On 15/06/2017 at 4:42 PM, wenlez said:

Running Xpenology 6.1 in Proxmox 5 Beta 2.  I can't get Synology's Virtualization Manager to work.  When I try to start a virtual machine, the log say the following. Had anyone got it to work? 

 


2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: MemSize: ccc/reservation.cpp:477 Start to op(3), ba03cfbc-00ff-451a-aef5-b814a2623589: +1073741824, orig 0
2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: core/utils.cpp:895 Failed to mkdir: /dev/virtualization/libvirt/qemu, error: No such file or directory
2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: MemSize: ccc/reservation.cpp:537 Failed to mkdir
2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: MemSize: ccc/reservation.cpp:488 Failed to op(1), ba03cfbc-00ff-451a-aef5-b814a2623589: 1073741824
2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: ccc/guest.cpp:1575 Failed to edit reservation resource for [ba03cfbc-00ff-451a-aef5-b814a2623589] ret [-2], mem: 1024 / 0, cpu: 4 / 4
2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: ccc/guest.cpp:1686 Failed to prepare for guest [ba03cfbc-00ff-451a-aef5-b814a2623589]
2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: Guest/guest.cpp:3141 Failed creating guest [ba03cfbc-00ff-451a-aef5-b814a2623589] reason [-7]

 

 

Not sure if running a virtualized OS within a virtualized OS is a good idea.

On 17/06/2017 at 11:59 AM, ordimans said:

Not sure to understand what is better than ESXI 6.5 ?
 

 

ESXi has a VERY limited support for various hardware (e.g. my RTL8111H LAN is not supported, many other hw aspects are not supported), and in my opinion management is hard. I'm used to Debian-like systems, so Proxmox is an instant win (especially since if you can't install with the default installer, like me, you can just install the latest Debian and pull it in after install).

Share this post


Link to post
Share on other sites

I have 6.5, and my RTL8111 works :

 

[root@localhost:~] esxcfg-nics -l
Name    PCI          Driver      Link Speed      Duplex MAC Address       MTU    Description
vmnic0  0000:03:00.0 tg3         Up   1000Mbps   Full   00:9c:02:97:53:5d 1500   Broadcom Corporation NetXtreme BCM5723 Gigabit Ethernet
vmnic1  0000:02:00.0 r8168       Down 0Mbps      Half   00:e0:4c:80:1a:50 9000   Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
[root@localhost:~]

 

Share this post


Link to post
Share on other sites
On 6/27/2017 at 2:05 PM, ordimans said:

I have 6.5, and my RTL8111 works :

 


[root@localhost:~] esxcfg-nics -l
Name    PCI          Driver      Link Speed      Duplex MAC Address       MTU    Description
vmnic0  0000:03:00.0 tg3         Up   1000Mbps   Full   00:9c:02:97:53:5d 1500   Broadcom Corporation NetXtreme BCM5723 Gigabit Ethernet
vmnic1  0000:02:00.0 r8168       Down 0Mbps      Half   00:e0:4c:80:1a:50 9000   Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
[root@localhost:~]

 

 

If you can hack the driver into the installer, sure it will work. However I had other system incompatibilities that ended up taking a week of my time. Proxmox setup took maybe 4 hours, 3 of that was finding a proper way for the USB disk, and testing.

Share this post


Link to post
Share on other sites
On 19.06.2017 at 5:46 AM, quicknick said:

 

virtio drivers are supported in my loader which will be released once I iron out ESXi upgrades.  KVM and baremetal are solid though.  

Screenshot_20170618_223221.png.85b5a25006e80b3e37d6da9c22242f25.png

 

Also performance is great as iperf3 has proved great performance.


DiskStation> iperf3 -c 192.168.0.2 -i 1 -t 20 -R  
Connecting to host 192.168.0.2, port 5201
Reverse mode, remote host 10.1.0.2 is sending
[  4] local 192.168.0.212 port 44805 connected to 10.1.0.2 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   844 MBytes  7.08 Gbits/sec                  
[  4]   1.00-2.00   sec   879 MBytes  7.38 Gbits/sec                  
[  4]   2.00-3.00   sec   898 MBytes  7.53 Gbits/sec                  
[  4]   3.00-4.00   sec   768 MBytes  6.44 Gbits/sec                  
[  4]   4.00-5.00   sec   883 MBytes  7.41 Gbits/sec                  
[  4]   5.00-6.00   sec   899 MBytes  7.54 Gbits/sec                  
[  4]   6.00-7.00   sec   900 MBytes  7.55 Gbits/sec                  
[  4]   7.00-8.00   sec   878 MBytes  7.37 Gbits/sec                  
[  4]   8.00-9.00   sec   907 MBytes  7.61 Gbits/sec                  
[  4]   9.00-10.00  sec   883 MBytes  7.40 Gbits/sec                  
[  4]  10.00-11.00  sec   906 MBytes  7.60 Gbits/sec                  
[  4]  11.00-12.00  sec   828 MBytes  6.94 Gbits/sec                  
[  4]  12.00-13.00  sec   898 MBytes  7.54 Gbits/sec                  
[  4]  13.00-14.00  sec   910 MBytes  7.64 Gbits/sec                  
[  4]  14.00-15.00  sec   758 MBytes  6.36 Gbits/sec                  
[  4]  15.00-16.00  sec   753 MBytes  6.32 Gbits/sec                  
[  4]  16.00-17.00  sec   841 MBytes  7.05 Gbits/sec                  
[  4]  17.00-18.00  sec   960 MBytes  8.05 Gbits/sec                  
[  4]  18.00-19.00  sec   858 MBytes  7.20 Gbits/sec                  
[  4]  19.00-20.00  sec   933 MBytes  7.83 Gbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-20.00  sec  17.0 GBytes  7.29 Gbits/sec    0             sender
[  4]   0.00-20.00  sec  17.0 GBytes  7.29 Gbits/sec                  receiver

iperf Done.

 

And it is better to use synoboot.img as virtual USB drive because then it properly works with upgrades.

 

Hello @quicknick

Any updates on your image? Could you tell approximate amount of time you need to finish your work? I'm now installing xpenology on server but performance is quiet low for my taste, I hope virtio drivers will solve this issue at least partially. Thus your image with virtio drivers will be greatly appreciated.

Share this post


Link to post
Share on other sites

+1,maybe make just proxmox loader release and do not wait till all esxi vmware stuff will be ready?

Share this post


Link to post
Share on other sites

Hi all,

 

I am also using PROXMOX and XPenology as virtual machine. So far with DSM 5.2 and 7 disk (passthrough) with 12 TB data (SHR). Yesterday I started a new virtual machine for testing 6.1 DSM. I did installation like mentioned here in this thread. It works within the 2 disks created on PROXMOX for this machine (tiny 32 gigs per disk for testing).

 

I'm a little bit afraid to delete this testing volume and shutting down this VM and passthroug my hard disks - did anybody did a upgrade like this from 5.2 with passthroug of a lot of disks? If yes, it's necessary with sata port mapping?

 

Best regards

 

Marrtin

Share this post


Link to post
Share on other sites
В 13.07.2017 в 16:10, IIIMIIIRIII сказал:

Hi all,

 

I am also using PROXMOX and XPenology as virtual machine. So far with DSM 5.2 and 7 disk (passthrough) with 12 TB data (SHR). Yesterday I started a new virtual machine for testing 6.1 DSM. I did installation like mentioned here in this thread. It works within the 2 disks created on PROXMOX for this machine (tiny 32 gigs per disk for testing).

 

I'm a little bit afraid to delete this testing volume and shutting down this VM and passthroug my hard disks - did anybody did a upgrade like this from 5.2 with passthroug of a lot of disks? If yes, it's necessary with sata port mapping?

 

Best regards

 

Marrtin

Id rather make migration instead of upgrade.backup-new install-restore data.Anyway backup before upgrade.

Share this post


Link to post
Share on other sites
On 13/06/2017 at 6:42 AM, lemon55 said:

In fact, everything is much simpler!

1. Create HDD, I did SATA0, RAW format (because synology.img is a RAW disk)

2. Replace the resulting disk**1**.raw file with synology.img (where it lies) with renaming.

3. In the UI, we remove the disk (once!). It will become disabled. Then click on it two times - connect sata0, raw. It will be displayed as 50mb.

4. Profit!!!

Only e1000, this has already been discussed - Virtio does not work!

 

Hi,

I was going to post the same steps  ;-)

I did that few wekks ago and it works like a charm.

 

Easy and Quick

 

Share this post


Link to post
Share on other sites
On 23/06/2017 at 7:00 AM, quicknick said:

The reason why I recommend using as usb image vs making it a vdisk, because you don't have to waste a sata or scsi port, and disk stays hidden as synoboot and not accessible inside DSM.

could not really get it running. Used 

 

args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/101/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot'

 

with boot: 3 

 

in my case ( verfied with ESC ) but it never booted under proxmox 4.x with the JUNI bootloader https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!ZoFxDQgB

 

Share this post


Link to post
Share on other sites
On 18.7.2017 at 2:23 PM, mXfored said:

could not really get it running. Used 

 

args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/101/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot'

 

with boot: 3 

 

in my case ( verfied with ESC ) but it never booted under proxmox 4.x with the JUNI bootloader https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!ZoFxDQgB

 

 

same problem here (if i understand it correctly)

always have to press ESC and choose the virtual USB Stick to boot from. Doesn't take boot orders form .conf

  • Like 1

Share this post


Link to post
Share on other sites

Hi guys

 

Just a note about how getting the serial connector working in Proxmox so you can see what happens.

You will get all the informations on your screen while its booting, and you will get the prompt at the end of the process


First of all you have to connect to Proxmox via SSH

ssh root@proxmox.local

You need to know the id/number of your VM running Xpenology, you see that in proxmox main web interface in my case it was 109
then add a virtual serial port to the VM

qm set 109 -serial0 socket

Now you can connect to the serial port of the VM

qm terminal 109

That's it     (if you don't see anything on screen just press the space bar twice :smile: )

 

To quit the QM-Terminal press :

ctrl+o

If you login to your vm using that serial connector, it will looks pretty ugly, you can't see what you're really typing, so a simple fix, just type in the prompt one of these 2 commands

sh
bash

now  you'll have a clean shell

 

source

 

PS : I did this a while back, i dunno if you need to reboot the VM to get the serial port working

Edited by anthon

Share this post


Link to post
Share on other sites
On 22. 7. 2017 at 11:35 PM, optic said:

 

same problem here (if i understand it correctly)

always have to press ESC and choose the virtual USB Stick to boot from. Doesn't take boot orders form .conf

hello i have same problem

 

if i pres ESC at boot and then 3 USB img  boots and everything is working - 2 disk passthru -sata , even smart info is passed

 

boot: 3

 

is in my conf

but usb virtual disk is ignored and it allways boot from hard disk and stuck there

so i have to log in proxmox console reset ESC press 3 to get it work

 

somewhat proxmox is ignoring boot: 3 setting (it shows red in webgui as it is wrong)

or is there different syntax ? or we have to set something somewhere , bad proxmox build ?

 

proxmox clean install 2 hours 1 vm 

Share this post


Link to post
Share on other sites
On 8/11/2017 at 6:27 AM, magara said:

hello i have same problem

 

if i pres ESC at boot and then 3 USB img  boots and everything is working - 2 disk passthru -sata , even smart info is passed

 

boot: 3

 

is in my conf

but usb virtual disk is ignored and it allways boot from hard disk and stuck there

so i have to log in proxmox console reset ESC press 3 to get it work

 

somewhat proxmox is ignoring boot: 3 setting (it shows red in webgui as it is wrong)

or is there different syntax ? or we have to set something somewhere , bad proxmox build ?

 

proxmox clean install 2 hours 1 vm 

 

my conf proxmox 5.0.2

args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/100/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot'
bios: seabios
boot: 3 
cores: 4
memory: 4096
name: xpenology
net0: e1000=0A:53:03:D4:08:5D,bridge=vmbr0
numa: 0
ostype: l26
sata0: /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B0_WD-WCAW30781368,size=976762584K
sata1: /dev/disk/by-id/ata-WDC_WD10EZRZ-00HTKB0_WD-WCC4J4TZXSPL,size=976762584K
scsi0: local-zfs:vm-100-disk-1,size=32G
scsihw: megasas
serial0: socket
smbios1: uuid=0a8b84a6-314a-4462-9e87-e986c2d274c6
sockets: 1

press ESC 3 - working

autostart from conf  boot: 3 - doesn't work

 

proxmox 1.jpg autoboot 

proxmox 2.jpg manual reset after stuck at first screen ESC 3 

what to do

 

Pictures  

proxmox 1.jpg

proxmox 2.jpgproxmox 3.jpg

Hide  

 

Share this post


Link to post
Share on other sites

my problem was ZFS local storage

as i have 2 disks in mirror zfs 250GB and vm images are stored at local-zfs rpool/data

 

but finaly i manage create boot disk 

 

so  i created new wm disk 250 mb disk because it has to be some corect size fraction of filesystem

and then aj dd synoboot.img to it, problem was that aj didnt know what the hell zfs is :smile:

 

when i dried

dd if=synoboot.img of=rpool/data/vm-100-disk-2 bs=1M

it says that 52 mb was copied ok but machine didnt start automaticaly

 

after some fidling i found real place of vm-100-disk-2

 

dev as it is block device or what :smile:

dd if=synoboot.img of=dev/rpool/data/vm-100-disk-2 bs=1M

and then i correct boot as c disk and sata:0 as first 

and reboot several times and it is working

 

only problem is that,  i removed  mounting synoboot.img  line from cfg but somehow

DSM automount this sata0 device as usb :smile:

 

i am affraid what i will do, if that zfs raid one day fall

cant understand why i have greyed options as snapshot at local-zfs

 

 

 

Share this post


Link to post
Share on other sites

I am trying to setup Xpenology on Proxmox while I got the loader working properly now when trying to connect through Synology Assistant it never sees any hard disks. My main purpose is just to use several synology apps so all I need are virtual disks. But when I try to add a hard disk it never recognizes it during the install.

 

Could anyone assist me with this on how I can get synology to see the virtual disks? (DS3517xs)

Share this post


Link to post
Share on other sites

Hi, I´ve got another Problem.

I replaced the original disk with the synology.img file. The loader is working, but when I see the Web Assistant to install the DSM it says : 

 

disk could not be formatted (35).

 

Any idea?

 

Pls help

 

Scarface

Share this post


Link to post
Share on other sites

Ok, last problem solved.

 

But I´ve got a new issue. 

 

I set up a system with 3 drives. 1. boot 2. firmware 3. data.

 

But everytime I add some drives with passthrough like :

# qm set <ID VM> -ide[Nr HD] [device]
# also z.B.:
qm set 101 -ide1 /dev/sdb

I get the error message: DSM was reset to default. Pls reinstall DSM.

When I do, it restarts and the same Message comes again.

 

So it does not boot into DSM .

 

Any Idea?

 

 

DSM.jpg

Share this post


Link to post
Share on other sites
On 6/21/2017 at 0:56 AM, ma2002 said:

hi all

this file add virtio-net

can anyone share how to include virtio-scsi?

 

synoboot2.img

Thanks , you saved my day(s).

Copying file over 10gbe at 7.9GB/s now , satisfied ;-)

Share this post


Link to post
Share on other sites

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:
Xpe61Jun102bTestVirtio.JPG.f1cb5de57d2599747764c97e1a34446f.JPG

 

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

Edited by arkilee
add modified synoboot zip file

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Hi. For anyone having problems with setting USB as primary boot device, use UEFI bios from Proxmox "OVMF (UEFI)". When system is booting just press ESC button and in bios change boot device. Works for me. Cheers.

Share this post


Link to post
Share on other sites

In UEFI bios you can save USB as firs boot device. Of course you can save settings there and it works at every boot.

 

Uefi.jpg

Edited by hellbondz
Better explenation.

Share this post


Link to post
Share on other sites
On 18/09/2017 at 9:18 PM, hellbondz said:

Hi. For anyone having problems with setting USB as primary boot device, use UEFI bios from Proxmox "OVMF (UEFI)". When system is booting just press ESC button and in bios change boot device. Works for me. Cheers.

 

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. :smile:

 

 

Share this post


Link to post
Share on other sites

Sorry i had to hijack this thread,

but where to find quicknicks loader?

His thread seems depricated but i dont know why.

Could not send him a messge.

So i try it here :-)

 

Saw some picture with loader v3 *amazed*

@quicknick

 

Edited by Wurstpilot

Share this post


Link to post
Share on other sites
On 11.08.2017 at 1:27 AM, magara said:

...  boots and everything is working - 2 disk passthru -sata , even smart info is passed

 

Hi there, 
I'm considering to migrate my baremetal Xpenology system to proxmox.
So I installed test pve system on my old PC and configured latest DS3617xs DSM with Jun's 1.02b loader. 

 

Thanks everyone for tips from this thread!

 

Found one problem - I've passthru one drive as sata, but DSM can't read SMART data.

 

59c29a8b2e70b_2017-09-20o18_41_54.thumb.png.7e4edde856cb98c515174f8de247159b.png

 

Can someone tell me how to passthru HDD with all smart data?

Edited by sloniu82

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now