@Brent Clothier and anyone else running into this issue on the A2SDi boards: I spent a great amount of time on this too, before I remembered what I had long forgotten (the most non-intuitive part of dealing with UEFI bioses is that CSM must often be explicitly enabled, and this is usually in a...
No additional ideas other than that your motherboard components might be going south on you. I just wanted to clear up my earlier assertion. I realized from your latest logs that I was looking at the wrong attribute.
SMART attribute 190 is the difference from 100C, while attribute 194 is the...
The following problem exists on an out of the box install with latest 3.4 ISO installer (pve-kernel-2.6.32-39-pve) and also following a dist-upgrade which installs pve-kernel-2.6.32-40-pve. Manually installing pve-kernel-3.10.0-11-pve seems to fix the problem. I know the 2.6 series is on its way...
Is it possible the machine is rebooting due to a heat issue? If the SMART logs are to be believed, it seems to me that 66-69 degrees Celsius is very high for hard drives, and the temperature can be significantly higher for the CPU/RAM/motherboard.
Actually, I have a use case for booting from a (slightly) mismatched mirror set. It used to be pretty common in some sys-admin circles to use drives from different manufacturers in a raid set (not just drives from different production runs of the same manufacturer).
So if you have two drives of...
FYI, I have some E3-1270 v3 systems running Proxmox 3.3 with the default 2.6.32-33-pve kernel. Not positive, but I think that 64bit FBSD on Haswell problem might have been resolved in the new QEMU package, in case you're not totally comfortable running non-default kernels.
A pfSense VM on a...
Sorry, didn't know you had a problem with virtio NICs, or I would have mentioned the fix. (Some people prefer not to use virtio for various reasons, like I went with a scsi drive on that VM mentioned above.) That's a known issue. I believe the other two were turned off by default recently. I...
Here's something interesting. The increased CPU usage can be seen inside the VM as interrupt and system time. It's not purely on the host side. People with this problem might be able to see it reflected in the System tab of pfSense's RRD graphs page. You'll notice the blue and yellow shaded...
Thanks for the info. Since you're on Opteron, I'm not sure if we can make any meaningful comparisons. I haven't used any of those in 7-8 years. Would love to know what other people are seeing.
Hi mir, can you share some details about your setup?
Physical hardware platform, pfSense version and i386 or amd64, any special tuning parameters, did you upgrade to Proxmox 3.3 from the no-sub repo, etc?
I'm seeing the problem on a Nehalem class server (Supermicro motherboard). I can...
Yes, I happened to upgrade right at the release of 3.3 (great work, and thanks to the devs), but ran into this problem. I use pfSense and other FreeBSD VMs heavily and was dismayed to see idle VMs hit 10-15% of two allocated CPU cores.
For me, this only seems to affect FreeBSD version 8...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.