donmimo

Can we get nvidia/nouvou drivers compiled? I have gpu pass through setup but due to lack of nvidia support from the kernel it can't be initialised. I am hoping to get /dev/dri accessable and hopfully face detection will work afterwards if /dev/dri is persent.

ffmpeg delivered with DSM 6.1 is buggy. How I fixed the issue is downloading the latest ffmpeg binaries and replacing the buggy ffmpeg in /bin Download from https://www.johnvansickle.com/ffmpeg/

ffmpeg delivered with DSM 6.1 is buggy. How I fixed the issue is downloading the latest ffmpeg binaries and replacing the buggy ffmpeg in /bin Download from https://www.johnvansickle.com/ffmpeg/

I load the modules in this order: virtio virtio_ring virtio_pci virtio_net [ 148.627764] virtio_pci: Unknown symbol register_virtio_device (err 0) [ 156.005140] virtio-pci 0000:00:03.0: setting latency timer to 64 [ 156.024991] virtio-pci 0000:00:13.0: setting latency timer to 64 [ 156.044885] virtio-pci 0000:00:14.0: setting latency timer to 64 [ 162.012201] virtio-pci 0000:00:13.0: irq 41 for MSI/MSI-X [ 162.012219] virtio-pci 0000:00:13.0: irq 42 for MSI/MSI-X [ 162.012233] virtio-pci 0000:00:13.0: irq 43 for MSI/MSI-X [ 162.016274] virtio_net: probe of virtio1 failed with error -12 [ 162.016437] virtio-pci 0000:00:14.0: irq 41 for MSI/MSI-X [ 162.016454] virtio-pci 0000:00:14.0: irq 42 for MSI/MSI-X [ 162.016473] virtio-pci 0000:00:14.0: irq 43 for MSI/MSI-X [ 162.019253] virtio_net: probe of virtio2 failed with error -12 [ 208.755483] virtio-pci 0000:00:13.0: irq 41 for MSI/MSI-X [ 208.755500] virtio-pci 0000:00:13.0: irq 42 for MSI/MSI-X [ 208.755515] virtio-pci 0000:00:13.0: irq 43 for MSI/MSI-X [ 208.758367] virtio_net: probe of virtio1 failed with error -12 [ 208.758526] virtio-pci 0000:00:14.0: irq 41 for MSI/MSI-X [ 208.758542] virtio-pci 0000:00:14.0: irq 42 for MSI/MSI-X [ 208.758557] virtio-pci 0000:00:14.0: irq 43 for MSI/MSI-X [ 208.761175] virtio_net: probe of virtio2 failed with error -12

@jun Thanks for all work. Did you try compiling the virtio_net module? Everytime if I try to insmod this module and dependencies I get unknown symbol and the module is not loaded.

Are you able to use virtio network card in your kvm vm?

That link was to show you that it's possible to control edit setting of your vm's on esxi from vmware workstation. Don't know man either you are doing something different or your vmware workstation version is not supported. I can definitely connect to esxi and add existing RDM disks. From your workstation: File/Connect to server Fill in the esxi username password and open the settings of your VM on esxi. From there it's self explanatory to add an existing disk and select your RDM disk as SATA and start your VM. That's all, nothing more nothing less.

Actually there is another way which you can try. Install Vmware Workstation 12 and connect to your esxi server from there, there is an option to connect. When you are connected you can edit vm's on esxi and add rdm disks. nope can't find the suggested option http://blogs.vmware.com/workstation/201 ... vms-2.html

Actually there is another way which you can try. Install Vmware Workstation 12 and connect to your esxi server from there, there is an option to connect. When you are connected you can edit vm's on esxi and add rdm disks. nope can't find the suggested option http://blogs.vmware.com/workstation/201 ... vms-2.html

Actually there is another way which you can try. Install Vmware Workstation 12 and connect to your esxi server from there, there is an option to connect. When you are connected you can edit vm's on esxi and add rdm disks.

I allready have the latest version, and I can edit settings just fine, only in this case I have issues with RDM. @ omega syslinux.cfg should be on the boot disk, but I can't be sure, I didn't make it; until now it was there (dsm 4-5) @ koalala Thanks for the RDM information. You are right, it doesn't work when you want to add RDM disks. But you can use vcenter to add RDM disks. If you don't have a vcenter setup you can deploy the VCSA, once you add the disks you can delete the appliance if you don't plan to use it since it's a trial version.

I also had the same issue, fixed it by installing an updated version of the webUI. Download it from here: https://labs.vmware.com/flings/esxi-emb ... ost-client Filename is esxui-signed-3976049.vib. For me it works perfectly, I can edit the vm from the webui.

Is it possible to use this method for kvm? In the end the vmdk files provided can be converted which I did. The installation went fine but the only drawback is that the "run" kernel doesn't include the network drivers I guess. Because if I boot with "run" option the installed synology can not be found in my network anymore.

It would make it easier if the zImage for the "run" option included more drivers like paravirtual drivers from the kernel. Now as it seems the boot of "run" is limited by a handful of hardware which is maybe only supported in esxi (version dependent).