ruBSD 2014 is coming

Just like in year 2013 Yandex will be hosting ruBSD 2014 (content is in Russian) event on the 13th of December. It’s funny that I learnt about it from BSD Now podcast which, btw, I highly recommend. In the last episode, apart from the already mentioned ruBSD 2014 conference, Allan Jude and Kris Moore also mentioned that videos from recent MeetBSD California 2014 have been recently published as well as from OpenZFS Developer Summit 2014.
But I digressed. Returning to ruBSD, the agenda looks very promising:

  • VM improvements coming soon to FreeBSD. Scott Long (Netflix).
  • Four years of pkg. Baptiste Daroussin (FreeBSD).
  • Functional and high-performance SCSI target based on CTL and ZFS. Alexander Motin (iXsystems).
  • New sendfile(2). Gleb Smirnov (Nginx, Inc.).
  • Practical use of IPv6. Alexander Chernigov (Yandex).
  • Building packages though emulation. Sean Bruno (Limelight Networks).

Registration is free but the number of seats is limited.

Jumping into another cloud

After almost 4 years of being a Rackspace 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 consider it as permanent so I started to look around. The decision was quick as I knew where to look at – thanks to FreeBSD Journal Issue July/Aug 2014 in which Colin Percival, a well-known FreeBSD committer, describes how to provision FreeBSD on EC2. Besides, he also publishes FreeBSD AMIs which gives hope that we won’t be left in the dark.
Can’t tell anything specific about AWS, it definitely fits my unassuming needs, but what I really like is their aws cli tool and of course waiting for my very first billing invoice.


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__);

Being a non kernel developer in any way that’s all I could tell so far. Time to dive deeper into the code.

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.