FreeBSD 10.1-Release as domU (guest) VM
I’ve been running FreeBSD 10.0-Release for quite a while using Rackspace’s environment and yesterday decided to jump on 10.1-Release bandwagon using exactly the same steps which I described in on of my earlier posts. However it wasn’t successful as expected since I see constant freezes with the following errors being displayed in the console:
network_alloc_rx_buffers: m_cjlget failed
network_alloc_rx_buffers: m_cljget failed
network_alloc_rx_buffers: m_cljget failed
network_alloc_rx_buffers: m_cljget failed
Increasing kern.ipc.nmbclusters and kern.ipc.nmbjumbop as a possible solution mentioned on FreeBSD Xen mailing list made no difference.
From GitHub FreeBSD repository it seems the error is generated by the following code:
if ((m_new->m_flags & M_EXT) == 0) {
printf("%s: m_cljget failed\n", __func__);
m_freem(m_new);
Being a non kernel developer in any way that’s all I could tell so far. Time to dive deeper into the code.
Update
The easiest/dumbest solution was to upgrade my Rackspace instance by adding extra CPU/RAM power. Not the solution I would like to have but at least it’s now possible to update and compile packages from the ports collections.
on November 27, 2014 at 1:20 am
· Permalink
[…] user I’ve moved to a new home – Amazon AWS. The main reason that gave me a nudge was the issue I was hit by after upgrading to 10.1-Release. Temporary solution did work but it was too costly to […]
on September 25, 2017 at 6:58 pm
· Permalink
This is most likely due to available RAM. Creating a swap partition will help a lot but will not eliminate the issue because of the nature of the swap partition on these Rackspace servers.
on September 27, 2017 at 2:20 pm
· Permalink
Hello Stephen,
Thank you for stopping by and leaving a comment.
Really appreciate that.
Kind regards,
Sergey