Search results

This is exactly the product I've been waiting for, thanks a lot! I installed it on a testcluster but keep getting an error when trying to backup a pve node: root@pve2:~# export PBS_REPOSITORY="pvetest2@pbs@192.168.178.235:datastore" root@pve2:~# proxmox-backup-client login...

Another error after a snapshot rollback, on the first cluster (production). () 2020-07-10 12:22:00 103-0: start replication job 2020-07-10 12:22:00 103-0: guest => VM 103, running => 40137 2020-07-10 12:22:00 103-0: volumes => local-zfs:vm-103-disk-0,local-zfs:vm-103-state-voor_2_3_install...

My APC ups is hooked up to my proxmox node via usb as well, I use apcupsd for monitoring and logging. Could you try installing the service and setting the "EVENTSFILE" setting to your liking in /etc/apcupsd/apcupsd.conf. Here's a little guide to set up the service for usage with usb...

There's a thing called write amplification on zfs, using trim (implemented in zfs 0.8) will help significantly. I've tries using samsung ssd's for my home lab as well but performance isn't great. Like LnxBil said, consumer ssd's aren't built for zfs. My Intel s3500 480gb ssd's dropped from 30%...

The replication was working rock solid until someone had to rollback a snapshot. This is the content of datacenter.cfg: keyboard: en-us migration: insecure,network=10.1.25.0/24 This was related to the second issue: volume 'rpool/data/vm-102-state-test2' already exists The no tunnel IP received...

Netgate has a guide in their documentation: https://docs.netgate.com/pfsense/en/latest/virtualization/virtualizing-pfsense-with-proxmox.html

I'm glad to see things worked out!!! Very nice of you to make a quick step-by-step guide, I hope it helps other people in the future.

I've had issues with the "INACCESSIBLE_BOOT_DEVICE" message when transfering a hw machine to a vm. The issue was resolved by deleting Intels Rapid storage. I suspect something in the boot process is still looking for a Xen hdd in specific instead of a common (ide) drive. disk2vhd works fine for...

I have a few clusters that use ZFS replication and HA. After a client rolled back a snapshot on one of their vm's a weird error popped up on the next replication. Removing the replication task and recreating it fixed the issue. 2020-06-25 11:36:01 102-0: start replication job 2020-06-25...

I've used the same script to migrate hundreds of vm's from Xen to Proxmox. Even a Windows 2003 vm worked after changing some settings from our default vm template: acpi: 1 agent: 0 bios: seabios boot: cdn bootdisk: ide0 cores: 4 ide0: local-lvm:vm-XXX-disk-0,size=100G ide2: none,media=cdrom...

I patched 2 clusters myself for testing and it works great so far. Thanks devs!!

You should be able to use the gpu in a container when it's not passed through to a vm. https://www.passbe.com/2020/02/19/gpu-nvidia-passthrough-on-proxmox-lxc-container/

I just got around to reading the announcement comments and saw this was already talked about. Thanks!

First of all I'd like to thank the devs for another great update. pve 6.2 has brought some really nice features. During my testing with 6.2 I was pleased to see that live migration with zfs replication works now, this is a feature I've been waiting for. I use HA with zfs replication as...

My fix for nvidia quadro cards is to export the bios and pass the bios file through to the vm. Also simply running the vm as omvf instead of bios (requires reinstall) might work.

Thanks! I'll try it out. Stopped trying to use unprivileged containers because of the hassle a while ago.

The iso must fit in ram uncompressed, I've had some mixed results simply loading the iso. I'm using the following script to convert the iso which has been a better solution in my experience. https://github.com/morph027/pve-iso-2-pxe

Nice! Glad you got it to work. AFAIK it doesn't matter if the EFI disk gets lost since it's just a boot firmware and contains vars like boot order. I did a quick test by copying an existing vm with uefi and deleting the EFI disk. The vm booted after recreating the EFI disk and even without one...

Could you show the output of cat /etc/network/interfaces?

Could you check out the disk using a live cd of some sort? I have never imported a vhdx file directly, all my converted imports went well though. qemu-img convert -f vhdx image.vhdx -O raw image.raw qm importdisk 102 image.raw local-zfs These are the commands I use for importing vhd(x) files.