NLS

I need to wake this up and ask. Did anybody make ANY change regarding this? Because I think no change happened. MyServers did not get updated, nor do I see any relevant change in 6.11.4 and 6.11.5 changelogs. Will anything be actually done?

Let me take the chance to say that you people should try DoubleCommander too. Krusader is good (this is what I used for years), but I think DC is better.

And what is the problem with using 18?

I suggest you move to binhex-crafty-4. All will be better then.

First of all, never make different backups run at the same time. Why would you do that. It is bad practice any way you look at it. Second, no it doesn't make sense for this to happen, except if there is a "restore" somewhere in your schedules. Even if a backup fails, it doesn't mean it would ruin a running source. So, it shouldn't happen and looks like user error to me. If the files were overwritten and you don't have a backup of the version you want, then it's game over for the data. Why you need so many daily backups? Does your minecraft server have that much traffic and changes? How many backups you keep? Because if you keep too few and take backups too many times, then it is also bad practice as you will find yourself even backing up... problems (if you don't find the whatever problem fast enough) and you will not have "clean" backups to revert to.

It is an issue for sure. The delay I get is not just 3 min, it is maybe 10 (or more!), which means that other things that depend on DNS (?) time-out AND THEY DID NOT (I want to point out the difference) before 6.11 (I think). During boot the system should have some backup solution that kicks in early (after testing for DNS maybe). Either use direct IP connections, or have some static hosts or even use 8.8.8.8 (or similar) in case there is no DNS access early in boot. This will probably solve it if DNS is the issue, but will not solve it if gateway is also within the same machine (so be inaccessible during boot) or there is a real Internet issue, or of course someone wants to setup a machine that will be off-internet on purpose (which is something many people don't think much nowadays, but is certainly an option). Whatever the case, the time-outs are HUGE. Even if there is no other solution, if the time outs just become WAY shorter (like 1/3 of what they are), will be a "passable" solution.

Just kicking this up, because it still happens with 6.11.3.

Good tip. I am used to blocks so...

so you see the folders that seem to be too big look in there

Open a terminal, go to offending container and: du -a | sort -n -r | head -n 10 ...to at least know where to look...

It's not just the container's logs, it's also crafty's own logs (there is a logs folder in crafty) AND each server's within crafty, own logs (there is a logs folder within each server)! Seems one of these is bursting with errors. Also, why you have both crafty and crafty 4?

Check logs!

You have a share just for minecraft backups? That is a weird setup - I mean, people usually make a few basic shares (for example a share for all kinds of backups) and then make sub-category folders inside them. To each their own, I guess. Anyway. Also, it doesn't look like you use a front slash (start with "/"), so I guess the backups made a tree under the working directory of crafty itself (possibly). So, start looking in /appdata/binhex-crafty-4 (and possibly deeper)... Probably not where you want your backups (as they will stay in your cache).

Well this is weird because obvious differences seem more than what is shown in the commits. IF that is the actual source that makes the build (because I am starting to have my doubts).

If everything else fails, just recreate the VM using the same disks. This will create a fresh XML. When you manage to boot, use 225.2, 225.1 seems to be buggy somehow. Also, why not use the latest chipsets emulated by KVM when running Win10 and 11? W10 and W11 are surprisingly resilient to hardware (and virtual hardware) changes.

I know, I already saw those.

Well who knows. I know what happened. Maybe the change was in the installer itself, so it wouldn't be in the commits.

...and I did. It works. Fixes the install issue and after re-creating virtiofs service, it works as before (and hopefully better).

There is a 225.2 driver ISO... anybody tried it?

? Only if you don't use virtiofs you can remove that. If you use it, it needs it. Anyway, my report is that my VM has NOT crashed since yesterday that I booted it to let it idle and test.

My VM Win 11 Pro uses Q35 (latest). I booted 5 minutes ago... I'll let it be and see if it freezes...

do they also know about the new qemupciserial issue?

So, staying to 221. I am using VirtioFS for the last few days. I haven't noticed a freeze yet BUT 1) I haven't kept the VM on long enough (will do during the weekend). 2) I think it needs more RAM than before. I suspect there is a memory leak, this can explain the "timed" freeze. Any other memory sharing methods evaluated? (and anybody really knows the differences?)

BE CAREFUL with 225. It failed for me. Not only it didn't update, it also messed my 221 install. I couldn't remove, repair or reinstall. It deleted the display driver (so I had only low-res VNC), it deleted network connection. I had to use microsoft troubleshooter, which I managed to pass to the VM using a USB stick that I modified the VM config to directly see. At least this properly deleted the crashed setup. Even then, with all virtio drivers removed, 225 would not complete installing. 221 (re)installed fine. So, beware - although your mileage may vary. Do yourselves a favor and keep this in your VM beforehand: https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d