Search results

Ah, that's a Realtek 8169? It has a rather long history of disappointment: https://bugzilla.kernel.org/show_bug.cgi?id=107421 See if you can disable power saving on that NIC.

A couple of questions: how many users are we dealing with here, and what is the link speed of the network adaptor? I take it you installed the virtio drivers for windows (like from virtio-win-0.1.229.iso) I'm having difficulty finding it, but is that an HDD RAID array, or an SSD one? [physical host]

Was this installed to a ZFS partition? If so, you're observing the Arc cache caching the disk concerned, which will disappear when the cached drive is deleted. It's completely harmless. You can see how much the arc cache uses by issuing the command arc_summary on the Proxmox shell. (Do this...

Only asking :) No offence intended. Some quite unusual pieces of kit are out there, so all bases need to be checked. The prior link I gave should be quite helpful.

For some more fine-grained control: https://www.kernel.org/doc/html/v4.12/admin-guide/pm/intel_pstate.html

While I think of it, are you running a scavenger board from China?

Okay, this is interesting, I think you'll find Intel's official documentation quite helpful: https://www.intel.com/content/www/us/en/developer/articles/guide/kvm-tuning-guide-on-xeon-based-systems.html Let me know how things go :) Oh, and for the governor you're after: ondemand

Okay, that's a bit blindsiding. Could you describe the environment in full, so that answers to your questions can be given which will work?

I think you need to consider you're comparing apples to oranges there. The first image, of the bootdisk, is the bootdisk... not the LVM disk. That bootdisk is 7.78GB big. 3.29GB is used, which is approx 42.37% of it. Your local-lvm is a different disk partition or drive; it is 162.81GB big, of...

For clarification, the Wan and Lan ports for the PFsense VM are on separate physical switches? No loops?

Sorry for getting back so late; been a hectic week. Okay, this clarifies a lot of things. When you forward a device into a VM, you take that device away from the host. So, the proxmox host won't be able to use the device. In the case of network cards, that can get pretty messy pretty quickly...

Okay, so let's go over a quick config: VMBR0 is connected to ens261, I have assigned an address to the bridge and told it where the internet gateway is; the server connects to the net like a device normally attached to the LAN, but you might use an external IP with a gateway device configured...

Okay, I'll give you an example of a working configuration: The idea here, is for you to examine a working configuration and its output, and to contemplate the differences to your own. Hopefully, it'll provide a few pointers as to why your current configuration is non-functional. Note: I...

Excellent, then you will be able to log in directly, and run the command: ip a This will show you the assigned IP addresses of each interface. If you find the output is too long [you can't scroll] ]use: ip a | more This will allow you to examine the output page by page. Another thing, with...

When you boot the Proxmox server, it will go through its boot routine, eventually arriving at a text screen which tells you the IP address and port that the Proxmox web interface can be accessed on. Do you have a Monitor/LCD attached to the Dell R710 to allow you to see this?

Can you tell us more about this system? One moment it seems to be a physical RAID controller [a physically separate card) and in the next reply, it seems to be a software RAID controller (Onboard motherboard unit.) The term reseating means to physically take the component out, and then put it...

Let's try something different: lower the RAM speed to 2400. I have, occasionally, found it'll fix things; perhaps even 6.2.

Glad to be of help, it's not an obvious thing at all, you actually need to be aware of the filesystem limits; and if you're not, well, interesting things happen. However, this does bring up an interesting thing, the GUI should really have a spot-check that looks at the allocated size vs what is...

Given you had an issue after a physical move, have you tried reseating the RAID card itself? [If the move was violent enough to kill a drive, it'd be violent enough to displace other components. Reseating the RAM might be a good idea too.]

Ummm, if I'm not mistaken, do you have a 19TB qcow2 volume on a filesystem type [ext4] that can handle files up to a max of 16TB when using 4KB clusters? https://en.wikipedia.org/wiki/Ext4