Search results

I am not quite sure what's happening here. I am migrating a VM that has a disk that is 48G vm-101-disk-2 But when migrating it finds a whole lot more to migrate that I expected. Migration In the pool for 101 I find: What are these sub-vols and where did they come from? Are they...

Still occurs but less often so whatever causes it hasn't been fixed. I have both v7 and v8 setups about 32 probably about 320 guest VM's. I may see it every couple of months and then sometimes twice in a row. As I said earlier what you see is that normally it looks like the VM has frozen and...

I asked AI to summarise and I agree with the thread and what you said. So the green bar on HTOP *IS* the best guess. I can see the argument in the thread that cache is used memory but forgets the cache is disposable, it is meaningless and might was well be a png showing 100%. None of that is...

Yeah I was afraid the answer would be a question. Well, memory is cheap. As in doubling the RAM is peanuts compared with adding a complete new node. So what happens if I actually run out of RAM? For some reason across hundreds of VM's and dozens of nodes including on non- server hardware I...

A question I have had for a while and never got around to asking: I have many Proxmox clusters which usually contain 3 nodes, Xeon 128Gb SSD. What I don't really have a feel for is what capacity those nodes have for the number of concurrent VM/containers. As an example I migrated 6 VM's which...

So the problem was that sftp had the file open (even though it didn't) so I killed that process and restarted it and then we can run the file ok. I'll mark as solved and leave it here so I can google it in 3 years time when I fall down the same hole. he he he... vim.... I haven't got the...

yep and yep: $pwd /mnt/pve/replica/snippets $ls -l total 7 -rwxr-xr-x 1 root root 1741 Jul 4 15:08 wms-precheck.pl $ls -l /usr/bin/perl -rwxr-xr-x 2 root root 3681152 Sep 24 2021 /usr/bin/perl I thought it was the line endings but fixed that. Its a simple thing I'm sure.

actually I think I know what it is.... wait....

I created a simple hookscript based on the example and attached to my VM. $ qm start 109 hookscript error for 109 on pre-start: command '/mnt/pve/replica/snippets/wms-precheck.pl 109 pre-start' failed: open3: exec of /mnt/pve/replica/snippets/wms-precheck.pl 109 pre-start failed: Text...

Thanks, I understand quorum. What I was trying to do was have the HA configured between the 3 nodes (on the same site) using the pool grouping and be able to manage a 4th node (whos vm's don't need HA) via the same interface, such that I have a single pane of glass to work with for the same...

Early days, can't make heads or tails of it but we have a cluster of 3 nodes with HA, replication happily chugging along. When we came to add a 3rd node basically looks like all hell broke loose, all 3 nodes restarted red x's on the nodes, couldn't get in on the web interface. All VM's were...

This has to be miles more efficient that the legacy homebrew solution we were using which was rsync based. One of the challenges with such a system is that a long sync (> 1 hour) invariably encounters some brief interruption or bandwidth issues, at which point the command will stall and another...

Maybe the initial sync was just a major pain. My understanding is that it should work out what is missing from the remote and only copy the differences. If thats not the case then its really not fit for purpose and you'd be better using rsync using linking. However, it looks like this may be...

This isn't the same issue I am getting but may be related. In my case on Linux 2.4 kernel guests ONLY, I get a situation where it looks like its frozen, but if you happened to already have an ssh connection open and you're in a root you can see that its still running but that the filesystems...

We're not able to fix this, since we didn't have a problem for 20 years on QEMU it must be a bug in the current version. For now we are able to create a shadow machine with a cron that r-syncs the critical areas and then the shadow machine is snapshotted. What we are finding is that if...

It was obviously important enough to need it and despite huge changes > 2.6 there are no special versions. In my travels, I did look at the differences between 2.4 and 2.6 from a kernel point of view and they would seem to be quite vast - far too many to mention but plenty of fundamental changes.

This may yet be related to qemu after all. I'm running Kernel 2.4.21 and haven't seen that on any other VM's that are later than that. So we seem to have an incompatibility between QEMU and 2.4 kernel. But wait.... Under OS type there are two linux kernel options. l24 Linux 2.4 Kernel...

Just had it happen on another server. (same kernel) .And going back to the previous question, why doesn't replication cause the issue? And also, people are using the autosnap script which as far as I can see, creates a snapshot and that also doesn't cause a problem. Since replication runs all...

I know it maintains state - I mean that its telling that it remains broken when a new instance of QEMU is created. As I see it the "Snapshot" should be completely transparent to the guest but for whatever reason in this instance - its not. And its interesting that its not always, just...

AFAIK /bin and /use/bin are both part of the root fs. so they are the same. This is a bit like the old days when you had the cylinders, head and sectors set wrong. Some files were readable others were wrong addresses. Any writing to the disk in this state probably corrupts it. Its as if the...