Sefa's Tech Blog

I have a stable proxmox environment. After a while, when I try to reboot or shut down a vm, it gives me the following error: starting worker failed: unable to parse worker upid 'UPID:fsm-05:0005E6C2:13CC0EA5A:539EB0E9:qmshutdown:109:root@pam:'

When I tried to bootsrap a server into Chef, I faced with following error: dpkg: warning: 'ldconfig' not found in PATH or not executable. After a quick research, I found the exact answer. Sudoers file was defected. Following lines were missing: Defaults env_reset Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" After adding these lines into the file, the problem has been solved.

I needed to migrate virtual machines in proxmox to openstack. VMs are in raw format. I needed to take some actions for a succesfull migration. I have perform all actions on Ubuntu 12.04 with virt-manager. qemu-kvm is installed. Here is the list of actions that I took: First, close the machine and copy the image file into your Ubuntu. Convert raw image to qcow2 format: qemu-img convert -O qcow2 image1.raw image1.qcow2 You need the image in qcow2 format for compatibility with openstack platform.  Open the converted image in virt-manager. Before opening, edit disk options. Under ' advanced options ' section, select ' qcow2 ' as ' storage forma t '. Start the virtual machine. You should see the login screen soon. (If you don't set storage format, vm will not find a bootable device. )   If everything is ok so far, close the vm. Take qcow2 image and upload it into glance. It may take time depending on size of it. After this process is completed, open a

After upgrading OS X to latest version (10.9.3), I have faced with a problem that virtual box was not able to create host only networks anymore. This is the error log printed if a host-only-network is tried to be created: Failed to create the host-only network interface. VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory. After some research, I saw that this is a virtualbox bug. The reason is that StartupItems no longer exist in Mac OS 10.9 Mavericks. It is depraceated 8 years ago. Until this bug is solved, a temporary solution is: sudo /Library/StartupItems/VirtualBox/VirtualBox stop sudo /Library/StartupItems/VirtualBox/VirtualBox start Then, you can open Virtualbox application. In network tab, all host only networks will be listed. You can also check it via 'ifconfig' command. You can see the related virtualbox ticket on this link .