Search results

I just did an in-place upgrade to 7.0.10 using the guide and it went very smoothly indeed. Great job! One change/anomaly I noticed after upgrading PVE: A container running a single instance of elastic stack worked fine under pve-6.4. After upgrading PVE, the elastic process (java) in that...

I took a chance and did the following: Commented out suspend related config (lock, runningcpu, runningmachine, vmstate) in /etc/pve/qemu-server/195.conf. Rolback to snapshot The web interface would not allow me to delete the suspend state volume. It claimed it was tied to an existing vm...

I hibernated a vm via the web UI for a few minutes and them attempted to resume it: ~# qm resume 195 Resuming suspended VM activating and using 'vmdisks:vm-195-state-suspend-2021-04-25' as vmstate id 0, group 0, virt start 0, virt end ffffffffffffffff, generation 0, delta 0 id 1, group 1, virt...

RE CA certificate. I have added the relevant CA certificate to the Android user cert store. Should the Proxmox android app recognise this? I still seem to have to turn off SSL validation.

Thank you mira. I've just successfully moved them and they did indeed remain sparse. I took the precaution of shutting down each VM/CT first. One issue I encountered was, the move process stalling at the end of a copy. I tracked this down to attempting a move whilst the pve metrics endpoint was...

I have all VMs and CTs on a single LVM-thin volume, in a dedicated VG consiting of one partiton occupying entire single disk. I'd like to migrate the VM/CT volumes it contains to a new disk. I am not sure what the best way to do this is. I considered disk cloning but the target drive's available...

Given the attribute refers to wearout, it should intuitively increase over time. Perhaps attribute 233 + Media_Wearout_Indicator could be treated as such. I wonder, if it is standard with western digital drives, if it could be catered for? EDIT: OK there's no standard but AIUI it seems...

Thank you Dominik. That is good to know. A shame WD do not conform to the standard. Many thanks for explaining it. I will hold fire on buying a new SSD for a while, though doubt it will be WD next time.

I have LVM thin provisioned on a 1 TB WD Blue SSD. In use for about 10 months and has, until recently, always reported 0% Wearout in PVE web UI. Recently, this has jumped to 98%! The disk is puportedly good for 400TBW and I don't believe I have over taxed it. It's about 25% capacity, I have done...

Thanks Stefan. Really appreciate your advice. AIUI vzdump backs up, snapshots and restores vm disk images and container filesystems at block level. I will certainly be using that to backup VMs and CTs. However, I really want to run file level backups of NAS type storage with rsnapshot/rsync. I...

Thanks for the suggestion. That way, would the PVE host be able to perform a file level backup? I like to use rsnapshot for data backups, so need to mount the fs. The current server (soon to be PVE) is already set up with a working hotplug and rsnapshot backup. I have udev rules that, when it...

Hi, I am formulating a proxmox set up to replace my existing kvm server. On that machine, I run nfs on the host and use a caddy, configured as hot plug sata (in Z77 BIOS), to do rotated backups. One thing I cannot replicate in my virtualised test is this backup. If I put file services in a vm...

Replying to my own post here, I'm now wondering if there is any point having a container solely to run an nfs _kernel_ server.

Hi I am trying to run nfs server in a container (alpine-3.10). Apparently NFS requires some adjustments to the container and I have seen various suggestions. Privileged mode, this seems absolutely necessary. Features/nested - enabled EDIT - seems this is needed. I enabled priveleged mode...

Many thanks for the pointers. Very helpful. I have often separated vm's and containers from their application data. Other than for large media volumes, I'm going to rethink that. The id mapping feature for bind mounts looks good. Thanks again.

Hi, I have recently started exploring Proxmox and it's reignited my enthusiasm for virtualisation. I have been running a home server currently along the lines detailed below. No redundant storage, and rsnapshot backups to multiple drives via sata caddy. It all seems to perform quite well in...

I see similar backtrace as posted in the reddit thread linked above (beginning @93.694 in the xorg log excerpt). If I boot the VM without the hostpci pcie=1 option, no such error and I get to X in passthrough display. But subsequet GPU reset issues and the guest logs amdgpu errors re missing...

Just linking to this recent reddit post I came across, as it details the xorg error seen in manjaro guest above when pcie passthrough turned on. https://www.reddit.com/r/archlinux/comments/dyvj0c/cant_boot_to_gui_on_monitor_works_on_virtual/

I have an Asrock H170 motherboard and RX 580 8GB GPU. I have tried several times over the past year or two to get GPU passthrough working reliably with this setup, using qemu directly and libvirt on Ubuntu 16.04 & 18.04. Whilst I had some success, I usually had to reboot the host when restarting...