similar to: Virsh migrate and paused vm

hi, I have 3 nodes of CentOS 5.3 running xen virtual machines as virtual machine service. This cluster is working fine. One thing I would like to know that how to make failover only to third node. What I mean to say is: I have 3 virtual machine running on node 1 and 2 virtual machines running on node 2. Now if node 1 fails I want my the node1 virtual machines to be stared only on node 3 but

Hi all, When I migrate a live vm with two virtual disk images from one node to another. Bothe of the nodes are in the same LAN and there is no shared storage. I run the following command and get the output blew: yyang@node1:~$ sudo virsh migrate --live --persistent --copy-storage-all --unsafe --verbose vm1 qemu+ssh://192.168.1.3/system root@192.168.1.3's password: root@192.168.1.3's

Background: ---------- I'm trying to debug a two-node pacemaker/corosync cluster where I want to be able to do live migration of KVM/qemu VMs. Storage is backed via dual-primary DRBD (yes, fencing is in place). When moving the VM between nodes via 'pcs resource move RES NODENAME', the live migration fails although pacemaker will shut down the VM and restart it on the other node.

Howdy Folks, I've got a 5 node setup here. My server "home" is the primary server that all other servers connect to. The configs on all the servers look like this: # cat /etc/tinc/home/hosts/node1 Subnet = 10.2.0.0/16 Address = 192.168.2.1 <RSA KEY> # cat /etc/tinc/home/hosts/node2 Subnet = 10.3.0.0/16 Address = 192.168.3.1 <RSA KEY> Etc. All the hosts are setup

Hi there, I want to backup whole VMs every weekend for disaster recovery. The backup target can be a nfs or samba server. To minimize downtime, the VMs should just suspend(pause) instead of shut down(xm save). The VM is Windows 2003 server (HVM) and centos 5 paravirtual. I think of such a procedure: 1. dom0 suspends(pause) VM1 2. dom0 copies VM1 to Backup Server 3. dom0 resumes(unpause) VM1 4.

centOs5.5/samba4/named here is a short guide setting it up to work. I added TSIG for bind-master amd bind-slave. Update to samba4 alpha13 added (installing git on CentOs 5.5). If you do this howto right now you will start with samba4 alpha13. You do not need the update section. But you need git for your installation because the rsync-thing is broken!!!!!! First of all do not install the bind

Hello all, When I live migrate my centos guest from node1 to node2, I can ping the guest, but on node 2 if i do: xm console guest01 , I am not able to access it. When migrating back to node1 , I can access the console. What I noticed is, to access the console, the node ''s drbd resource/disk needs to be in primary status . Is it typical or only I am having this problem. Is there any

Hi, We have two nodes with centos 5.5 x64 and cluster+gfs offering samba and NFS services. Recently one node displayed the following messages in log files: Sep 13 08:19:07 NODE1 gfs_controld[3101]: cpg_mcast_joined error 2 handle 2846d7ad00000000 MSG_PLOCK Sep 13 08:19:07 NODE1 gfs_controld[3101]: send plock message error -1 Sep 13 08:19:11 NODE1 gfs_controld[3101]: cpg_mcast_joined error 2

centOs5.5/samba4/named here is a short guide setting it up to work. First of all do not install the bind package coming with centos 5.5!! Install needs for samba yum install libacl* gnutls* readline* python* gdb* autoconf* Named installation: Here is a description on what to do: http://jason.roysdon.net/2009/10/16/building-bind-9-6-on-rhel5-centos5-for-d nssec-nsec3-support/ The steps, yum

Hello I have a 3 node experiment as detailed below to estimate the bridged networking performance in para-virtualized Xen 3.0 on Emulab (https://www.emulab.net/) Here is how the 3-node topology looks (This topology is specified by means of an NS-2 file) topology: _______________________________ | | Node0:eth0 ------|Node1:eth0

Dear all, after the feedbacks. I renew this HOWTO with replacation of a second SAMBA 4 PDC. We have 2 CentOS 5.5 servers on which we build a SAMBA4 forest with 2 Servers replication. We have one hosts called "node1" and the second "node2" Step1: On node1: Do not install the named coming with CentOs. This version can not do dns updates!!!! Install needs for samba. yum

On Wed, Aug 6, 2014 at 12:27 PM, Eric Blake <eblake@redhat.com> wrote: > On 08/06/2014 10:06 AM, Yuanzhen Gu wrote: > > yes, I got your point, thanks very much Eric. > > not entirely, because you still top-posted. > > got it entirely this time, not top-posted. > > > > If I want to take a distributed snapshot, which need pause all the VMs > and >

centOs5.5/samba4/named here is a short guide setting it up to work. First of all do not install the bind package coming with centos 5.5!! Install needs for samba yum install libacl* gnutls* readline* python* gdb* autoconf* Named installation: Here is a description on what to do: http://jason.roysdon.net/2009/10/16/building-bind-9-6-on-rhel5-centos5-for-d nssec-nsec3-support/ The steps, yum

An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110303/0fbefee6/attachment.html

Hi. I'm in desperate need of some good advice. I have a tinc network with 16 nodes. It's a star topology where all nodes are connecting to the one node (Node1) that have a static IP. Node 1 accepts incomming connections Node 2 through 16 connects to Node1 One of the nodes (Node5) stopped working a while ago (2 - 3 weeks or so), other than that everything was working fine. Today I

Hi, I'm sometimes getting a failure of connecting 2 nodes when Tinc is started and configured in a LAN. In the logs, there are some unexpected dropped packets with very high or negative seq. I can reproduce this issue ~2% of the time. When this happens, the 2 nodes can no longer ping or ssh each other through the tunnel interface but using eth0 works fine. The connection can recover after at

Hello, We have a four-node RHEL4 RAC cluster running OCFS2 version 1.2.8-2 and the 2.6.9-67.0.4hugemem kernel. The cluster has been really stable since we upgraded to 1.2.8-2 early this year, but this morning, one of the nodes fenced and rebooted itself, and I wonder if anyone could glance at the below remote syslogs and offer an opinion as to why. First, here's the output of

On 08/06/2014 10:06 AM, Yuanzhen Gu wrote: > yes, I got your point, thanks very much Eric. not entirely, because you still top-posted. > > If I want to take a distributed snapshot, which need pause all the VMs and > then take snapshot, how can I control the pause for all the VMs? You mean, you have multiple VMs, and want to take a snapshot of all their storage at the same point in

On 08/06/2014 11:17 AM, Yuanzhen Gu wrote: >> Guest freeze/thaw (virDomainFSFreeze) only works on a live guest. So >> what you will have to do is: >> >> virDomainFSFreeze(vm1, ...) >> virDomainFSFreeze(vm2, ...) >> virDomainSuspend(vm1) >> virDomainSuspend(vm2) >> virDomainSnapshotCreateXML(vm1, ...) >> virDomainSnapshotCreateXML(vm2, ...)

Hi all, I'm back again with my speed issues. The past issues where dependant of network I used. Now I run my tests in a lab, with 2 configurations linked by a Gigabit switch : node1: Intel Core i5-2400 with Debian 7.2 node2: Intel Core i5-3570 with Debian 7.2 Both have AES and PCLMULQDQ announced in /proc/cpuinfo. I use Tinc 1.1 from Git. When I run an iperf test from node2 (client) to