Search results

Personally I think this approach is exactly the right one and appreciate the newer kernel for newer hardware. So please keep on doing as you are, I've had no stability problems.

That looks interesting thought it's not been updated for 3 years. I'd like to see LVM thin replication as well but suspect it might be a bit of work for the Proxmox guys to add in. ZFS probably was far easier because it's got this capability natively built in so they don't need to write and...

I’ve got this error as well. Guessing this hasn’t been fixed yet?

Thanks Fabian, appreciate everyone at Proxmox's work on sorting this out. I've a host I can try a new 4.13 kernel on, the main one will need to stay on 4.10 until it's sure it's fixed as I need that stuff to stay running.

I wonder if it's related to the following thread? https://forum.proxmox.com/threads/zfs-memory-issues-leak.37878/#post-188934 It mentions ZFS on the thread but later on you'll see it talks about it not being ZFS but probably the Virtio network card driver. Long shot but might be related to...

OK I’ve just hit this problem now. My host normally runs around 25 - 50% utilised on RAM so wasn’t hitting it. However have some BSOD Windows boxes this morning and looking my RAM is full. KSM has kicked in along with swap. There’s no way this should have got to 100% RAM usage so think the...

Interesting. I've upgraded two hosts so far with no issues but I don't use the qxl driver in Windows at all.

It most certainly does use storage level snapshots for LXC backups. KVM is only half of Proxmox.

This is an awesome feature and I know it's experimental at the moment but it regularly just stops syncing all my VM's. I need to restart the pvesr service and then it'll work again for a day or two before stopping again. I think it's simply getting stuck on the freeze filesystem sometimes on...

Ouch that's bad. I don't think there's anything special about my setup so think most would have performance similar to what I get. Is this on a heavily loaded server and maybe has huge IO Wait or it takes this long after a fresh boot with nothing else running at all? If it's shared storage...

That's not normal, my containers probably take around 1 second to boot. It's amazingly quick compared to a VM and even those I don't consider to be slow. Even doing a storage migration using PVE 5 with local ZFS storage between 2 nodes where it stops the container, replicates the changes since...

Just wondering if this should be working? I'm on the following packages: proxmox-ve: 5.0-16 (running kernel: 4.10.17-1-pve) pve-manager: 5.0-23 (running version: 5.0-23/af4267bf) pve-kernel-4.10.15-1-pve: 4.10.15-15 pve-kernel-4.10.17-1-pve: 4.10.17-16 libpve-http-server-perl: 2.0-5 lvm2...

I've got this working and am running Samba on the Proxmox host which is also AD joined though I don't allow AD users to log into Proxmox directly so it's just enough for Samba to work correctly. Before using ZFS I had a file server LXC however with ZFS passing the root ZFS as a bind mount...

Excellent. I think it's listed as experimental at this stage as it's new but regardless want to say thanks for this new feature. Not sure any other virtualisation platform has something quite this slick for smaller installations to use. Good job :)

Are you sure that's the case Wolfgang? I remember that being an issue on the earlier Qemu Agent's for Windows installers but thought they'd fixed that? Also he's saying if he calls the fsfreeze manually it's working, it's not calling it on the replication however.

Have you tried cache settings for instance? Try changing the ZFS disk to cache=writeback to see how that affects performance and IO delay.

Is this a ZFS issue? I've a host on 4.4 where his works fine but is using LVM Thin. I have another host I've rebuilt onto 5.0 but is using ZFS which gets no Disk IO for containers. Be good if this could be fixed though please :)

Hi, I have an LXC container running on 4.4 which establishes an OpenVPN and then IP Masq to effectively turn that into a router. This has additional lines in the config as follows: lxc.cgroup.devices.allow: c 10:200 rwm lxc.hook.autodev: sh -c "modprobe tun; cd ${LXC_ROOTFS_MOUNT}/dev; mkdir...

I'll have to pass then. It's not officially supported by Microsoft but this blog seems to suggest it's possible at least with general KVM. https://ianmarmour.com/2016/04/23/running-kvmxen-nested-in-microsoft-hyper-v/

Have you got a supported version of Hyper-V for Nested Virtualization and enabled that? Otherwise you won't be able to run KVM machines. LXC containers will be fine however. https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/nested-virtualization Also note that...