system toolbox

http://blog.flameeyes.eu/

http://blog.flameeyes.eu/2009/07/28/tinderbox-moves-to-containers

http://blog.flameeyes.eu/2009/11/24/more-tinderbox-notes-just-to-say

http://git.overlays.gentoo.org/gitweb/?p=proj/flameeyes-tinderbox.git;a=summary

nginx build error

 error: ignoring return value of ‘write’, declared with attribute warn_unused_result

fol je da se

ovakav kod:

    ngx_write_fd(log->file->fd, errstr, p - errstr);

zamjeni sa ovim koji preuzima vrijednost write funkcije (naime ngx_write_fd je write macro)

    int ndummy = 0;
    ndummy = ngx_write_fd(log->file->fd, errstr, p - errstr);

ML: Does Proxmox VE use libvirt? If not, why not?

Martin: We do not use libvirt. libvirt is written in C and contains large parts we will never use. With perl, we can do the same in ten times less code and time. Therefore development is much faster without libvirt.

ML: What major features are you planning for the next major release?

Martin: High Availability (HA) for KVM machines is one of the most interesting areas now and we are working on the integration of corosync and pacemaker.

http://www.corosync.org/doku.php

http://clusterlabs.org/wiki/Main_Page

SPICE protocol

http://www.montanalinux.org/spice-release-initial-thoughts.html

http://www.brianmadden.com/blogs/brianmadden/archive/2009/12/10/red-hat-makes-the-qumranet-spice-protocol-open-source-a-free-alternative-to-ica-pcoip.aspx

http://lxc.teegra.net/

http://sysadmin-cookbook.rot13.org/#lxc

lxc-debian¶

ringout@desk-1004-1:~$ sudo apt-get install debootstrap

bringout@desk-1004-1:~$ sudo ./lxc-debian create

prije toga sam uradio:

ringout@desk-1004-1:~$ zcat /usr/share/doc/lxc/examples/lxc-debian.gz > lxc-debian

bringout@desk-1004-1:~$ sudo mkdir -p /cgroup
bringout@desk-1004-1:~$ sudo mount none -t cgroup /cgroup

sudo apt-get install bridge-utils

bringout@desk-1004-1:~$ cat /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# auto eth0
#iface eth0 inet dhcp

auto br0
iface br0 inet dhcp
        bridge_ports eth0
        bridge_stp off
        bridge_maxwait 5

desk-c2¶

root@desk-c2:~# mkdir /cgroup
root@desk-c2:~# mount none -t cgroup /cgroup

br0 ručno¶

root@desk-c2:~# brctl addbr br0
root@desk-c2:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:1d:60:36:35:3e  
          inet addr:192.168.45.115  Bcast:192.168.45.255  Mask:255.255.255.0
          inet6 addr: fe80::21d:60ff:fe36:353e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:224885 errors:0 dropped:0 overruns:0 frame:0
          TX packets:170227 errors:0 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:1000 
          RX bytes:240368597 (240.3 MB)  TX bytes:82806448 (82.8 MB)

root@desk-c2:~# ifconfig eth0 0.0.0.0
root@desk-c2:~# ifconfig br0 192.168.45.115/24 up
root@desk-c2:~# brctl addif br0 eth0
root@desk-c2:~# brctl show
bridge name    bridge id        STP enabled    interfaces
br0        8000.001d6036353e    no        eth0
root@desk-c2:~# ip route show
192.168.45.0/24 dev br0  proto kernel  scope link  src 192.168.45.115 
192.168.185.0/24 dev vmnet8  proto kernel  scope link  src 192.168.185.1 
172.16.79.0/24 dev vmnet1  proto kernel  scope link  src 172.16.79.1 
root@desk-c2:~# ping www.google.ba
connect: Network is unreachable
root@desk-c2:~# ip route add default via br0
Error: an inet address is expected rather than "br0".
root@desk-c2:~# ip route add default via dev br0
Error: an inet address is expected rather than "dev".
root@desk-c2:~# ip route add default dev br0
root@desk-c2:~# ip route show
192.168.45.0/24 dev br0  proto kernel  scope link  src 192.168.45.115 
192.168.185.0/24 dev vmnet8  proto kernel  scope link  src 192.168.185.1 
172.16.79.0/24 dev vmnet1  proto kernel  scope link  src 172.16.79.1 
default dev br0  scope link 
root@desk-c2:~# ping 192.168.45.3
PING 192.168.45.3 (192.168.45.3) 56(84) bytes of data.
64 bytes from 192.168.45.3: icmp_seq=1 ttl=64 time=0.238 ms
^C
--- 192.168.45.3 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.238/0.238/0.238/0.000 ms
root@desk-c2:~# ping www.google.ba
PING www.l.google.com (209.85.135.147) 56(84) bytes of data.
From mraka-2.bring.out.ba (192.168.45.115) icmp_seq=1 Destination Host Unreachable
From mraka-2.bring.out.ba (192.168.45.115) icmp_seq=2 Destination Host Unreachable
From mraka-2.bring.out.ba (192.168.45.115) icmp_seq=3 Destination Host Unreachable
^C
--- www.l.google.com ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4019ms
, pipe 4

root@desk-c2:~# ip route add default src 192.168.45.115 dev br0
RTNETLINK answers: File exists
root@desk-c2:~# ip route delete default
root@desk-c2:~# ip route add default src 192.168.45.115 dev br0
root@desk-c2:~# ip route show
192.168.45.0/24 dev br0  proto kernel  scope link  src 192.168.45.115 
192.168.185.0/24 dev vmnet8  proto kernel  scope link  src 192.168.185.1 
172.16.79.0/24 dev vmnet1  proto kernel  scope link  src 172.16.79.1 
default dev br0  scope link  src 192.168.45.115

root@desk-c2:~# lxc-start --name ubuntu-1

lxc-start: failed to clone(0x6c020000): No space left on device
lxc-start: No space left on device - failed to fork into a new namespace
lxc-start: failed to spawn '/sbin/init'

lxc u karmicu ne radi https://bugs.launchpad.net/ubuntu/karmic/+source/linux/+bug/480739

karmic guest¶

isti problem:

https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/461438

[Bug 461438] [NEW] mountall fails under lxc

Postirao ovdje pitanje, http://www.stgraber.org/2009/11/06/lxc-containers-or-extremely-fast-virtualization#comment-110

Hi Stephane, 

I have read your posts about lxc. I have sucessfully setup lxc guests (hardy amd64, i386) which you submittedl.

Thank you for sharing this.

I have tried to setup lxc ubuntu karmic/lucid guest but with no success (stuck in upstream - mountall procedure - already reported here https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/461438).

On your microblogging site I have found thaty you have succees with running lucid guest. How did you resolve udev/upstart issues ? Can you share this configuration with us ?