search for: mcclatchyinteractive

Ran into a confusing situation today. When I mount an xfs filesystem on a server running centos 5.4 x86_64 with kernel 2.6.18-164.9.1.el5, the barrier/nobarrier mount option as displayed in /proc/mounts is always set to "nobarrier" Here's an example: [root at host ~]# mount -o nobarrier /dev/vg1/homexfs /mnt [root at host ~]# grep xfs /proc/mounts /dev/vg1/homexfs /mnt xfs

I'm running into a situation where a bogus bonded interface named "bond0" is being created, in addition to the desired "bond2" interface. Can anyone confirm this? Anyone know why it's happening or what I do to get rid of it? I wanted to start my numbering scheme at 2 instead of 0, which I didn't think would be a problem. As you can see, I have no reference

I have a python script that monitors the VMs on physical host servers running Xen, but the script doesn't work properly on a server I just built with KVM. The script runs as a non-root user and simply gathers some details on the status and names of the domains running on the host. Both Xen and KVM servers are running the same version of libvirt (libvirt-0.6.3-20.1.el5_4) and have the

I have a python script that monitors the VMs on physical host servers running Xen, but the script doesn't work properly on a server I just built with KVM. The script runs as a non-root user (same on all servers) and simply gathers some details on the status and names of the domains running on the host. Both Xen and KVM servers are running the same version of libvirt

Today I upgraded one of our KVM physical host servers to Centos 5.6. The other server remains on Centos 5.5. I've configured a storage pool in libvirt to use LUNs from an iscsi storage system as the volumes for each VM. After the upgrade, I decommisioned one of the VMs and removed the LUN from the storage system. Normally after this kind of operation, I simply need to run this command

I've configured a libvirt storage pool using an iscsi target from a Sun 7310 storage appliance and am using the LUNs in this target as volumes for my KVM guests. The setup is very similar to what Daniel covered in a recent blog posting: http://berrange.com/posts/2010/05/05/provisioning-kvm-virtual-machines-on-iscsi-the-hard-way-part-2-of-2/ It works great, but I can't figure out how

I have a python script that monitors the guest VMs on a servers running Xen, but the script doesn't work properly on a server I just built with KVM. The script runs as a non-root user (same on all servers) and simply gathers some details on the status and names of the domains running on the host. The Xen and KVM servers are running CentOS 5.4 x86_64 and are using the same version of