bastl

Wait, so I can't update NC 17 to 18 with the internal update routine?

Did someone already got the update to NC 18 now called "Nextcloud Hub" with a lot of new features. Most interesting are the preconfigured and already implemented office features. No more extra containers like collabora needed.

Is this docker still maintained? As said before, I didn't received an update in a while

@PeteAsking If you use the snapshot feature it will create a .snap file which collects the changes of the VM during the main vdisk is copied and these changes will be committed to the base vdisk file after the copy process is done. So if there is no error during the process, you only have 1 vdisk file.

As some users mentioned before this particular container usually got multiple updates per day, but now I don't see any updates anymore. I think early december I updated it last time.

First thing I noticed, the page is loaded really quick now. Great improvement 😀 Just an idea which might be possible to implement, maybe not. In case you passthrough a physical device (hdd, ssd, nvme), image the whole disk would be a nice feature. Snapshots won't work, sure, but shutdown the VM and make an image of the physical device would be neat. Did you ever thought about such a functionality and maybe played around with it already? I know thats a big thing I'am asking for, handling all the different kind of source devices and filesystems people maybe using might be a hassle. See it only as an idea in case you have to much time left 😂 Thanks again for this great plugin and the effort you put into it. I wish you and your family and friends a great start into 2020 🥂

Thanks to clear things up. UD+ is only an addon for the addon so to say. Maybe add that info in the first post. I had to read the last couple pages after reading the adjusted first post to find the info. I get the point, why you strip things out to slim down the plugin to the base it always meant to be. Maybe I'am allowed to asked is this the first step to prepare UD to become implemented by default into Unraid by Limetech? I remember there were a couple discussions to implement the functionality of UD into Unraid.

@pankleks Did you tried the card in another pci slot of your board?

Updating the docker is not updating nextcloud itself. Login with an admin account and go to the settings >>> overview ("Übersicht" in my case on the left side) and you should see your current version and a hint if a newer version is available. From there you can start the update/upgrade process

You have to adjust the path for each VM to make the snapshots work.

@JTok Just one little thing I need is a big red button labled "BACKUP NOW" 😂

@JTok Big thanks in the first place for your work. Looks like the plugin works for me with a quick test on a single VM, normal backup+compression. A small issue I've found is when selecting the target path for the backup. It's basically not possible to read the dropdown menu items. I'am using the Black theme with Firefox. Same with Brave browser and Chrome on Unraid 6.8. Just to let you know.

@skroonigan Make sure you type the name for the user correct. It's case sensitive admin vs Admin is different.

@mojotaker Edit your VM like shown above and you should be good.

The question as always is what you need more for your VMs and your workflow? It's kinda easy for a VM which has only one usecase lets say video encoding. Check the specific programs you are using and test it in both scenarios. Each program behaves differently and I think for daily use the lower latency is the way to go. Did you saw any users in the forums yet with the newer TRX4 platform and the 3rd gen chips? @jbartlett The new chip layouts shouldn't have these latency issues.

@joelones It could be possible for some excessive CPU operations you can see performance decreases if a specific CPU feature is emulated. I think if you're not routing hundreds of clients through Pfsense or have couple VPN connections incoming at the same time, you won't notice it. I did a couple tests with a Linux and Win7 VM in parallel using my Test-Pfsense environment and it was stable with full download speeds and no packet drops. Might be different on a larger scale. For me it's fine for testing.

@aim60 The exact same link Farrukh already posted 😂 but thanks anyways 👍

Thanks for the info 👍

I found a workaround for this! The culprit is the cpu-mode "host-passthrough". If I switch to "Emulated QEMU64" the VM boots up again. Switching it in the gui should work if you havn't setup any special CPU flags. Another way is to edit the xml like the following: change <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='1'/> </cpu> to <cpu> <topology sockets='1' cores='2' threads='1'/> </cpu> also forces the CPU into emulated QEMU64 mode. Another option is to emulate a Intel Skylake CPU for example with the following: <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Skylake-Client</model> <topology sockets='1' cores='2' threads='1'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='pcid'/> <feature policy='disable' name='hle'/> <feature policy='disable' name='erms'/> <feature policy='disable' name='invpcid'/> <feature policy='disable' name='rtm'/> <feature policy='disable' name='mpx'/> <feature policy='disable' name='spec-ctrl'/> </cpu> Edit: "AES-NI CPU Crypto" isn't supported on "Emulated QEMU64" mode. For future Pfsense versions this is a requirement if I remember correctly.

@Farrukh Can you explain a bit further what you did? Only creating a dummy vdisk inside the VM folder without attaching it to the VM shouldn't do anything. What is the format your Pfsense VM are using? Qcow2 or RAW?

@MrSmith3101 Are you using OVMF or seabios for your VM? I only have a OVMF setup and hadn't the time yet to test a fresh install on seabios.

I noticed the same yesterday firing up a Pfsense VM that I use from time to time to test some stuff. No device passthrough I only use 2 virtual nics. One on br0 as WAN for pfsense and a internal virbr where usually a VM is connected to to generate some traffic. It never halted on startup nore did I install anything inside or changed any config. I played around a couple hours yesterday but I wasn't able to start the VM at all. Changing different Q35 versions, switching the vdisk type from qcow2 to raw, virtio, scsi, sata nothing worked. Also the restore of an old backup didn't help and also not to generate a new VM with the same vdisk attached. It always halts directly after the boot selection and 1 core utilises 100%

sry, a typo "will never moved to the array by the mover"

@RyanBorh If you already have installed some dockers or VMs, disable docker and VMs first in the settings, set both shares to PREFERED, run the mover so all existing data is moved to the cache. Check if the files are moved over to the cache and check if the shares don't exists on any array drive. Simply click the folder icon on the far right behind the drive in Unraids main tab. After that change both shares to ONLY and startup the docker and VMs again in unraids settings. Every new Docker or VM you install now will always been stored on the cache drive now and newer will be moved by the Mover to the array. For daily backups for the Dockers you can use the "CA Backup / Restore Appdata" plugin from the community applications. For backing up your VMs there are a couple ways to do it. You can use the following script for example and configure a daily schedule for it with the "User Scripts Plugin" Or in case you wanna use the BTRFS snapshot feature you can use a script to do this. This only works if the source and target drive is using BTRFS

@RJ59 Put the following in the "go" file on your Unraid USB flash stick under config and reboot your server #!/bin/bash # Start the Management Utility /usr/local/sbin/zenstates --c6-disable /usr/local/sbin/emhttp &