WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Migration problems ...

To: Xen-Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Migration problems ...
From: Gareth Bult <gareth@xxxxxxxxxxxxx>
Date: Thu, 21 Feb 2008 12:50:40 +0000 (GMT)
Delivery-date: Thu, 21 Feb 2008 04:51:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I'm trying to migrate a VM between two machines using a DRBD device.

Sometimes it works, and sometimes it doesn't .. can anyone give me any clues as to why this might be?

When it doesn't, this is what xentop shows me on the target;

xentop - 12:49:22   Xen 3.2.0
2 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
Mem: 6290816k total, 6129364k used, 161452k free    CPUs: 4 @ 2800MHz
      NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS   VBD_OO   VBD_RD   VBD_WR SSID
      dhcp --b---          0    0.0     131072    2.1     131072       2.1     1    1        3       16    1        0        0        0 2149622432
  Domain-0 -----r       2189    0.2    5892096   93.7   no limit       n/a     4    0        0        0    0        0        0        0 21496224

Effectively it doesn't look like it's able to connect up the device.

However, /proc/drbd confirms that the block-drbd script on each machine has succeeded.
(i.e. primary/secondary are successfully reversed)

My drbd.conf;
----------------------------------
global {
    usage-count no;
}

common {
      syncer { rate 10M; }
}

resource dhcp {
    protocol C;
      startup {
            wfc-timeout  120;
            degr-wfc-timeout 120;
    }
      disk {
           on-io-error   detach;
    }
      net {
        allow-two-primaries; 
        after-sb-0pri discard-zero-changes; 
        after-sb-1pri discard-secondary; 
            max-buffers 128;
    }
      syncer {
           rate 10M;
            #after "something else";
            al-extents 257;
      }
      on nodea {
          device     /dev/drbd0;
          disk       /dev/local/dhcp;
          address    10.0.0.1:7788;
         flexible-meta-disk  internal;
      }
      on nodeb {
          device    /dev/drbd0;
          disk      /dev/local/dhcp;
         address   10.0.0.2:7788;
          meta-disk internal;
      }
}
----------
my instance.cnf;

kernel            = '/boot/vmlinuz-2.6.21-prep'
ramdisk         = '/boot/initrd.img-2.6.21-prep'
disk            = [ 'drbd:dhcp,xvda,w' ]
vif             = [ 'ip=10.0.0.23,mac=00:00:10:00:00:23,bridge=eth0' ]
root            = '/dev/xvda ro'
name            = 'dhcp'
on_poweroff     = 'destroy'
on_reboot       = 'restart'
on_crash        = 'restart'
serial_device    = 'xvc0'
memory          = '128'
vcpus           = '1'
cpus        = '0-1'
extra        = 'clock=jiffies selinux=0'

Any ideas gratefully accepted!
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Migration problems ..., Gareth Bult <=