Search results

Hello everyone! I have emails that keep showing up in the queue and they are failing because of a connection time out but I do not care about that. I was wondering why these emails keep showing up in the queue even after I delete them using postsuper -d ALL? Plus, I do not currently have any...

Yes, I agree but the only major thing I've done these past few weeks to that particular node is run an Update --> Refresh and Upgrade followed by a Reboot through the Proxmox UI. I did not perform any Rollbacks but I deleted one or two Snapshots and created those first two Snapshots...

Thank you, that fixed it!!! I created the snapshots within the Proxmox UI...nothing special or anything on the backend was done except the "Test1" and "test" snapshots that were created in the CLI but only after I noticed this problem.

Looks like the snapshots are definitely on the ZFS filesystem: root@proxmox2:~# zfs list rpool/data/vm-110-disk-1 -r -t all NAME USED AVAIL REFER MOUNTPOINT rpool/data/vm-110-disk-1 1.24T 1.43T 1.24T -...

Yes, for the snapshot I mentioned above it shows: "TASK OK" for one entry and then another entry shows: "TASK ERROR: snapshot name 'Test1' already used" when I attempted to take another snapshot using the same name. "Test1" still does not show up in the Proxmox UI for that particular VM.

It's ZFS.

Hello everyone! On Proxmox (pve-manager/5.4-14/b0e640f7 (running kernel: 4.15.18-28-pve)) my snapshots are not working for one of my VMs. They appear to complete in the Proxmox UI and on the CLI: root@proxmox2:~# qm snapshot 110 "Test1" --description "This is a test" root@proxmox2:~# qm...

Yes, I will mark as [SOLVED]. My other VM's on the other Proxmox nodes are also Ubuntu but do not experience this issue. So is this a specific setting in Ubuntu that needs changed?

Yes, sorry it's Ubuntu 18.04.4 LTS. Changing the Display --> Graphic card to: "VMware compatible" worked but none of my other Linux VM's need a "VMware compatible" display. Of course, they are all running on an older Proxmox (pve-manager/5.4-13/aee6f0ec (running kernel: 4.15.18-27-pve)). So I...

Hello everyone! I have a Linux VM running on Proxmox (pve-manager/6.1-8/806edfe1 (running kernel: 5.3.18-3-pve)) and for some reason the console always displays this distortion no matter what I do. This is the only Linux VM on this Proxmox node but the other two Windows 10 consoles work just...

Disabling the: "Turn on fast startup (recommended)" seems to retain the resolution but only if Windows is restarted from within the Windows VM. It will not work on a Reboot executed from Proxmox or with a Shutdown executed from Windows or Proxmox. If you do happen to shutdown Windows then...

Wow, same here! Your suggestion worked but if I reboot the Windows 10 VM it defaults back to the 800X600 resolution. And here's the worst part for me: in order to access the OVMF UEFI I must remove my external USB HDD I have set to passthrough from the Hardware section of the VM but I can...

Yes, you are correct. I get the resolution I want using RDP but I'm using NoMachine for my VM remote connections as it's convenient having everything accessible through "one pane of glass". I've seen where using "SeaBIOS" allows one to change the resolution but this would require a reinstall...

After changing to "SeaBIOS" the Windows 10 VM will no longer boot:

Hello everyone, I have a Windows 10 VM (with the latest updates) running on Proxmox [pve-manager/6.1-5/9bf06119 (running kernel: 5.3.13-1-pve)]. I've gone into the OVMF EFI settings and adjusted the resolution to 1920x1080 but booting back into Windows 10 I'm still stuck at the 800x600...

Thank you for the info! I will give this a try!

Hello everyone, Would anyone be able to provide an update on this matter? I'm still unable to get IGD passthrough to work on an Intel NUC8i7BEH with the latest Proxmox (6.0-11) but is it confirmed this will work in kernel 5.1? I thought about using passthrough on the Thunderbolt port but have...

I removed the disk from VM 101 through the UI and then executed: rbd rm cephfs_vm/vm-101-disk-0 which seems to have done the trick! Doh! You were correct! I was copying the VHDX from an external USB drive plugged into Proxmox1 but VM 101 was sitting on Proxmox4. I thought since everything...

Hi Wolfgang, It's actually VM 101 (vm-101-disk-0) I'm working with...vm-100-disk-0 is attached to another VM that is irrelevant. I created VM 101 and by default vm-101-disk-0 was created in the cephfs_vm pool. I'm now trying to import a converted VHDX file of the same name (vm-101-disk-0) to...

Hello everyone, I'm trying to import a VHDX file which was converted to RAW into a Ceph pool (cephfs_vm) but receive the following error: root@proxmox01:/mnt/pve/cephfs# qm importdisk 101 ./vm-101-disk-0 cephfs_vm Configuration file 'nodes/proxmox01/qemu-server/101.conf' does not exist That...