Search results

Hope it gets into next update soon :-)

I've managed to import this backup. First, I extracted it to temporary directory, then I moved extracted qemu-server.conf to /etc/pve/qemu-server directory, removed all disks from config (cloudinit and scsi0), then I imported extracted disk-drive-scsi0.raw to VM and re-created cloudinit disk. It...

cat /etc/pve/storage.cfg dir: local path /var/lib/vz content iso,vztmpl,backup zfspool: zfspool-1 pool rpool/data sparse content images,rootdir zfspool: zfspool-2 pool nvme/data sparse content images,rootdir Backup config: agent: 1 boot: cn bootdisk: scsi0...

Hi I've got the same error: qmrestore /var/lib/vz/dump/vzdump-qemu-20191017-2020_04_28-12_08_15.vma 20191017 --storage zfspool-1 restore vma archive: vma extract -v -r /var/tmp/vzdumptmp318.fifo /var/lib/vz/dump/vzdump-qemu-20191017-2020_04_28-12_08_15.vma /var/tmp/vzdumptmp318 CFG: size: 510...

It is exactly what I was looking for :-) But pct set is a perfect workaround for me.

When I configure Proxmox server, I disable direct access to root account. I set empty password and disable login via password to root. I can only login: to shell via ssh as my user or root with SSH keys only. When I login as my user, I can sudo to root to Proxmox GUI as my user with password...

Hi, I've got a strange problem with Proxmox GUI when I try to edit Features of LXC container. When I'am logged as root, I am able to edit features: But when I'm logged as other user with admin permissions, I can't: My user has Administrator privileges: # /etc/pve/user.cfg...

You need to create dataset not zvol. Proxmox is responsible for creating virtual disks as zvols inside the base dataset.

try to create new VM directly on FreeNAS storage and look at /var/log/syslog what happens.

You need to ask current maintainer of proxmox-freenas at https://github.com/TheGrandWazoo/freenas-proxmox/ I wish he can manage to include it to Proxmox.

First of all: I'm not the creator of these patches :-). I only contributed a few diffs. Second of all: ZFS over iSCSI uses FreeNAS API to manage LUNs and ZFS ZVOLs (create/destroy). But it also uses SSH to get ZFS info. So you need to configure SSH connection between Proxmox cluster and FreeNAS...

I think he removed: bridge-vlan-aware yes bridge-vids 2-4094

Do you use ZFS with swap on it? Try to disable swap.

Read the thread with my problems with Connectx-3: https://forum.proxmox.com/threads/vlan-with-tag-above-126-problem.46072/

I don't recommend Mellanox. I've got Connectx-3 on my cluster and can't pass VLANID above 126 to VMs on bridged interface.

After applying patches, you can configure access to FreeNAS API via Proxmox GUI. Patches also added support for Proxmox to be able to manage LUN and ZFS configuration via API calls.

What do you mean by totaly? These patches allow you to use FreeNAS as a iSCSI storage for your VM's disks. Proxmox can create/destroy/resize virtual disks which are iSCSI LUNs on FreeNAS.

@nomad - https://github.com/UstyuzhaninAV/freenas-proxmox/commits/master Nothing has changed comparing to the source repo. EDIT: it's even 2 commits behind the original repo.

ZFS over iSCSI supports snapshots. But as I said before - you can run KVM VMs only.

You've got dedicated software for site's monitoring (nagios, zabbix, prometheus, etc.). Requesting to have it in Proxmox wastes tons of hours & human-resource in Proxmox dev team ;-)