Search results

Direct means just that - direct to the CPU, no HBA or muxing, however in some cases this may not be faster due to NUMA core pinning to VMs and dedicating lanes to each CPU... Then there is yet another option on the R760: "Direct Drive Switched" which adds a PCIe switch to switch the lanes...

Yes, funny I opened a feature request, and that is exactly the response it is available. I was a couple revs behind, and now on 3.3.3 I see there is now push/pull, and Removable Datasets. You might plug in a USB SSD, create a Push sync and set "Transfer Last" to 1 snapshot, Max Depth to 1, and...

Its the opposite, a remote off-site PBS can only PULL to sync, there is no push ability... So yes, you would need to temporarily open 8007 (with source IP restrictions or vpn) at the remote PBS and set it up as a local backup device on the PVE server or as a replication partner for the local PBS...

Whoops a I crossed a couple lines from the bridge config in to the bond config, should have double checked the examples on the wiki... nice it still worked with my fudge-ups.

I have a server (v8.3.2 latest) with a 4 port nic, I just modified the interfaces file manually, everything seems to work, but now I get an error in the GUI if I just try to enter a comment on a network port, it acts like it is expecting interface names to be "eth" My ports are: root@pve1:~#...

FYI... IDE mode severally hinders performance - according to this link VIRTIO is ~5x faster. I believe there might be other limitations such as online expansion, I think to expand an IDE you have to shut down your VM, adding a new Virtio can be done live, or expanded live, make sure to run the...

Yes, thanks Waltar, that was the problem, the source was on ZFS compressed storage.... It was a 8GB disk, showed 4.5GB used, but on the new non-zfs storage it had 9GB used. I adjusted the restore rootfs size to 12GB: pct restore 218 vzdump-lxc-118-2024_12_28-17_32_14.tar.zst --rootfs 12...

I just tried creating a new CT on PVE2 and it works fine, boots I can login and make files. I just cannot restore one.

Sorry, I did do some searching, didnt mention that I checked the inodes, I dont see any excessive usage - especially since I have no other CTs running. and I have tried all of these storage locations, including a new SSD, same result. @wahmed If CT is not enabled on the storage it wont be...

This is just a lab environment, I have 2 PVE, PVE1 is using sshfs to mount backup storage on PVE2 to backup CT to other host. Now I want to restore the backups from PVE1 to a CT on PVE2... no matter what I do I keep getting an error that it cannot create dirs or no space left on device, which...

proxmox already has immutable backups - just run a remote sync PBS, the source PVE host and source PBS know nothing about the remote PBS since it works in a pull manner from the primary, they have no ability to access the remote PBS.... Or rsync/rclone/restic your PBS data store to rsync.net who...

I already use that method, but a few people have said "just use PBS to backup the host", which it does backup, but it does not restore. So if there was a one stop option to always keep my data backed up on the PBS, including the host, with versioning, and quick disaster restore of everything...

I am backing up my pve host successfully, but I wanted to test a restore to another machine- proxmox-backup-client restore host/pve1/2024-01-03T04:53:23Z pve-etc.pxar /etc/ I get this error, it's a brand new machine I just added the PBS storage to: Error: error extracting archive -...

Just wondering if there has been any progress on this, testing and I am not sure how to restore a fresh host, First I ran this on my production pve host: export PBS_PASSWORD="4theB4ackups" export PBS_LOG=warn export PBS_REPOSITORY=root@pbs@10.0.0.9:backup1 proxmox-backup-client backup...

This is pretty troubling, I have tried to install on a R720, and now R730 also fails with 7.1-1 iso image. I am booting the iso via the iDrac IPMI, click on Install Proxmox and on the next screen it fails: waiting for /dev to be fully populated...| ACPI Error: No handler f0331/evregion-130)...

PVE 7.0-11 Just testing a Win10 VM, hotplug/numa enabled, running guest agent. I added 4096 to the existing 4096 ram and it fails. Trying to add a CPU core, it just adds it and waits for a reboot to apply the new CPU. Parameter verification failed. (400) memory: hotplug problem - VM 110 qmp...

Strangely this time booting up set to 5.2 it worked without error. Working 5.0: /usr/bin/kvm \ -id 100 \ -name PLserver \ -no-shutdown \ -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' \ -mon 'chardev=qmp,mode=control' \ -chardev...

This is a brand new installation, I did not change the machine type, and I made 3 VMs that all had the same problem. proxmox-ve: 6.3-1 (running kernel: 5.4.103-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-7 pve-kernel-helper: 6.3-7 pve-kernel-5.4.103-1-pve...

I just loaded up the latest 6.3.1 and ran dist-upgrades to the very latest on a Dell R730, when I try to start a new Win2019 VM with the bare basic defaults selected it fails to start with error: () kvm: no-hpet: unsupported machine type It seems the default machine type 5.2.0 is the issue...

I just did a zfs send | receive of the snapshot I wanted, and was able to directly access the zvol there on the new pool