Search results

Sorry, I don't understand this answer. My question was: Is it possible to include the RAM with the vzdump command when backing up VM snapshots ?

I guess it's a RBD snapshot, in any case it is a disk snapshot: man vzdump ... --mode <snapshot | stop | suspend> (default = snapshot) ... Is there another possibility to get the RAM included, without vzdump ?

Hello, sorry if this is a FAQ: Is it possible to include the RAM with the vzdump command when backing up VM snapshots ? Thanks Stefan

Thanks for your help ! :) Best regards, Stefan

Thank you for this interesting explanation ! I want integrate new servers with Intel CPUs Generation Icelake, more Cores and bigger OSDs in a Proxmox Cluster with Intel CPUs Generation Skylake, less Cores and smaller OSDs. Is this ok ? Best regards, Stefan

Hello, is it possible to integrate computers as nodes into a Proxmox/Ceph cluster that have significantly different equipment (CPU cores, RAM, disk storage) and what are the disadvantages? Thanks, Stefan

No problems at the moment, but only a few vms are running Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 40...

Yes, I have (it's the same at the other cluster): ceph -s cluster: id: aceb952d-7214-4fbe-bd8d-71b863f2d0eb health: HEALTH_OK services: mon: 3 daemons, quorum xxx,yyy,zzz (age 4d) mgr: xxx(active, since 4d), standbys: yyy, zzz osd: 6 osds: 6 up (since 4d), 6 in...

So it's definitly a Proxmox 8 problem. Where are the Proxmox gurus and where is the redemptive update ? ;)

In /var/log/syslog I have a lot of this messages (Proxmox 8, upgrade from 6 to 7 to 8): 2023-07-14T17:59:04.235286+02:00 xxx kernel: [171745.397894] Code: Unable to access opcode bytes at 0x55615db1eab6. 2023-07-14T18:05:44.739292+02:00 xxx kernel: [172145.909735] pverados[841677]: segfault at...

Hello, is there in the meantime a solution for this problem ? https://listman.redhat.com/archives/virtio-fs/2021-June/003491.html: "virtiofsd doesn't garant write access at users allowed by group permission." I still have this problem Stefan

Hello, I've made a shared folder with virtiofs (passthrough), but I cannot export this folder with NFS at the VM: rpc.mountd[1358]: Cannot export /export/home, possibly unsupported filesystem or fsid= required I can mount this home directory over nfs, but it is empty. Any Ideas ? Thanks Stefan

Hmm :(

Another question: There is a Proxmox Book which strongly recommends to set the BIOS feature "restore on ac power loss" to "Power on". In my opinion "Stay off" is the reasonable default in case of voltage fluctuations, UPS problems and so on. But I can't find the recommendation "Power on" in...

I'm new to HA and watchdogs and I do not really understand how to determine which hardware watchdog my servers support. I thought that in case of my Supermicro servers which have IPMI the IPMI watchdog is the obvious solution.

Hello, I've configured the three nodes (Supermicro Server) of my Proxmox/Ceph Cluster (newest version) for using hardware watchdog (https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Hardware_Watchdogs): 1.) Enable watchdog in BIOS 2.) /etc/modprobe.d/ipmi_watchdog.conf: options...

Sorry, my failure. kpartx is the reason. Now it works Stefan

Did not help. Stefan

Hello, now it nearly works, but I get "already mounted or mount point busy". I cannot find any reasons. rbd ls pool2-1 : vm-100-disk-0 vm-101-disk-1 rbd --pool pool2-1 snap create pool2-1/vm-101-disk-1@test rbd --pool pool2-1 snap ls vm-101-disk-1 : SNAPID NAME SIZE PROTECTED TIMESTAMP...

Thank you for your help ! Stefan