The 2014 edition of KVM Forum is less than a week away. The schedule of the talks is available at this location. Use this link to add the schedule to your calendar. A few slides have already been uploaded for some of the talks.
As with last year, we’ll live-stream and record all talks, keep an eye on the wiki page for details.
One notable observation about the schedule is that it’s much relaxed from the last few years, and there are far fewer talks in parallel this time around. There’s a lot of time for interaction / networking / socializing. If you’re in Dusseldorf next week, please come by and say ‘hello!’
I participated in the OpenStack Meetup at the Red Hat Pune office a few weekends ago. I have been too caught up on the lower-level KVM/QEMU layers of the virt stack, and know there aren’t too many people involved in those layers in Pune (or even India); and was curious to learn more about OpenStack and also find out more about the OpenStack community in Pune. The event was on a Saturday, which means sacrificing one day of rest and relaxation – but I went along because curiousity got the better of me.
This was a small, informal event where we had a few talks and several hallway discussions. Praveen has already blogged about his experiences, here are my notes about the meetup.
The KVM Forums are a great way to learn and talk about the future of KVM virtualization. The KVM Forum has been co-located with the Linux Foundation’s LinuxCon events for the past several years, and this year too will be held along with LinuxCon EU in Dusseldorf, Germany.
The KVM Forums also are a great documentation resource on several features, and the slides and videos from the past KVM Forums are freely available online. This year’s Forum will be no different, and we’ll have all the material on the KVM wiki.
For a long time various people have been telling me there’s not much information on the low-level / plumbing details of the virt stack on Linux. Especially information related to qemu and its various settings, devices, and so on.
Documentation surely is difficult to come by, but a quick and straightforward solution is to syndicate all of the blog posts that people doing virt development write into a common stream: a planet virt. I started hosting and testing such an instance on openshift, but was quickly pointed to the existing Virt Tools Planet by Rich Jones and Dan Berrange. Dan added the list of people whose blogs I followed for virt development to that instance.
I updated the KVM and QEMU wikis to ensure the Planet gets more visibility, and hope this goes a small way to quell the complaints of not enough available information.
I participated in the Fedora Activity Day at the RH office in Pune yesterday. There was a decent turnout, 20+ people, and it was fun to test the in-progress version of the upcoming F21 release along with other folks.
I run Piwik on OpenShift to collect stats on visits to this blog. I’m not really interested in knowing who visits my site. I’m only interested in knowing what people are visiting for, and how: which pages are more viewed? where are people landing to my site from? how long after publishing some post do people still visit it? And so on.
One of the ways this is also helpful is to track 404 (page not found) errors that pop up for visitors. After migrating my previous posts from blogger, I kept monitoring for any posts that may have been missed by the automatic migration process, and manually moved them. Continue reading
Experimenting with the new cyanogenmod builds for Android 4.3 (cm-10.2) resulted in a disaster: my phone was setup for encryption, and the updater messed up the usb storage such that the phone wouldn’t recognise the in-built sdcard on the Nexus S anymore. I tried several things: factory reset, formatting via the clockworkmod recovery, etc., to no avail. The recovery wouldn’t recognize the /sdcard partition, too. Continue reading
A few weeks back, a strange bird call started waking me up. Though red-whiskered bulbuls are supposed to be pretty common, I’d not heard them or seen one up close.
Several applications need random numbers for correct and secure operation. When ssh-server gets installed on a system, public and private key paris are generated. Random numbers are needed for this operation. Same with creating a GPG key pair. Initial TCP sequence numbers are randomized. Process PIDs are randomized. Without such randomization, we’d get a predictable set of TCP sequence numbers or PIDs, making it easy for attackers to break into servers or desktops.
On a system without any special hardware, Linux seeds its entropy pool from sources like keyboard and mouse input, disk IO, network IO, and any other sources whose kernel modules indicate they are capable of adding to the kernel’s entropy pool (i.e .the interrupts they receive are from sufficiently non-deterministic sources). For servers, keyboard and mouse inputs are rare (most don’t even have a keyboard / mouse connected). This makes getting true random numbers difficult: applications requesting random numbers from /dev/random have to wait for indefinite periods to get the randomness they desire (like creating ssh keys, typically during firstboot.).