Search results

Hello, I've been attempting to get GVT-g working on this board with an Intel E2146G. I'm able to get IOMMU groups listed, but not seeing the Intel iGPU anywhere. Proxmox GUI is also not showing mediated devices. I know it should work somehow because I see others using this setup with unraid...

I have an AsRock C246 with Coffee Lake as well, but I'm unable to even see any IOMMU groups in proxmox. Can you share what you have in grub and modules to get this working? I've tried seemingly every combination in the documentation.

Is there any sort of replication option in Proxmox that would mimic functionality in Hyper-V? Would love to be able to enable replication for a VM from one proxmox cluster to another across geographical locations and simply flip a switch to do a failover.

Yeah it dawned on me earlier that compression isn't likely to big a large factor since the drive is filled with mostly already compressed items such as video files.

Having an issue with permissions on privileged containers (haven't even started with unprivileged yet). I have a CT made with the bind mount mp0: /rpool/storage,mp=/storage /rpool/storage is a zfs mount on the host and folders/files are owned as root by default. Inside the containers exist...

Correct, I have just one. NAME USED AVAIL REFER MOUNTPOINT rpool 2.62T 11.4T 2.62T /rpool

Not sure what's going on with the compression (lack of) on my pool. This was a fresh ZFS pool without any existing data. Files were then copied into it from an ext4 formatted drive yet still sitting at 1.0x ratio. Any ideas? :/# zfs get compression rpool NAME PROPERTY VALUE SOURCE...

I would argue it would make the selection logic for VMs/CTs the same as if you selected 'All' for the nodes, as every VM Guest is listed below when doing so. It would offer more granularity you selected individual nodes and wanted to drill down to each individual guest. In my preference I don't...

In my example, I have two NFS storage servers. I'd like to send a group of them to backup to the first server, and some others to a different one.

Yeah right now you can select one, or all. I'd like to be able to select part of them. If I'm not doing 'all' then I now have to create a ton of separate backup jobs in the interface

I tried that in my first reply by holding Ctrl down. This does not work in the latest version of chrome and proxmox up-to-date: pve-manager/5.1-43 This is holding ctrl down and clicking on other nodes in the list: https://i.imgur.com/YNfTXm7.gifv

When creating a backup job, is there a way to select more than one node for the job? Previously I had it blank which did them all. This worked fine but now I need to seperate just one node from the rest of them in two independent jobs. Doesn't seem like it's an option using any sort of...

Also having this issue on host via iotop: 99.99 % [z_null_int] Looking forward to the patch in enterprise repo

Good to know I'm not the only one experiencing this https://forum.proxmox.com/threads/windows-guest-hangs-during-backup.36406/ Though I only have this occur with Windows systems, linux and containers both do fine.

Thanks for the information, I'll have to take a look once those reach the subscription repo. I tested the fix from the end of the reported bug on launchpad, no luck. Setting txqueuelen higher at 10000 didn't resolve it - it was actually worse this backup :) The freezing also occurs on the guest...

Unfortunately this still occurs. I've built a new node with SSD disks and have attempted both Server 2016 and 2012R2 with SCSI, VirtIO, IDE, Ballooning Enabled/Disabled, and QEMU Enabled/Disabled. No luck on stable performance during a backup with Windows. All works fine on Linux systems and...

This is a brand new install from within proxmox itself. I've created about 3 different test systems with the same results. I'm going to bring another node online in the next few weeks and will test a windows system from there too. Stumped. I'm going to try a 2012 R2 system as well.

The first post on page two was the results from local storage. I've been writing locally instead of the NFS share to simplify things - the issue still occurs. I'll check out 'fio'.

Here's the result with a file larger than RAM on the system: # dd if=/dev/zero of=temp.dat bs=1G count=150 150+0 records in 150+0 records out 161061273600 bytes (161 GB, 150 GiB) copied, 73.0341 s, 2.2 GB/s I would think 2.2 GB/s should be adequate for a backup write? It's still odd to me why...

Attempting to backup to the local storage instead of NFS produced nearly the same results. The system took a slightly longer time to go unresponsive, but still occurred. Reply from: bytes=32 time<1ms TTL=127 Reply from: bytes=32 time<1ms TTL=127 Reply from: bytes=32 time=2592ms TTL=127 Reply...