This seems innocuous, and typically, there are no problems with the runtime system. Everything seems to be stable and reliable. But maybe someone can explain why this is occurring.
This occurs in early boot, and the problem IS persistent. I run ipfire in a VM as an appliance. I started noticing this only recently (maybe last 3 months or so).
Yes, I did do google on it, and I did find those pages discussing W+X. But I don’t get these problems with other applications. That’s why my first guess was Ipfire.
More specifically, I was thinking of the specific way that ipfire builds its kernels. It is not beyond reason that ipfire may have compiled a custom kernel and perhaps there might lie the problem.
I am not dismissing the possibility of an issue with virtualbox; that has had its share of issues. But generally, I find that vbox works well with most distros.
The host kernel is x64_64… unless you mean for the guest? Currently, I see the guest (ipfire) is running a PAE kernel. That is the kernel that came with the original install of ipfire. I see there is also a non-PAE kernel for x86. I only have 256M allocated for this VM, so PAE is probably not necessary.
Is there a 64 bit kernel for ipfire, and how would I get it?
No worries, Michael. I appreciate the constructive and non-belligerent responses since those are the ones that get us closer to a solution. The others, not as much…