From xen-api-bounces@lists.xen.org Tue Jan 01 05:30:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 01 Jan 2013 05:30:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TpuQ9-0003IT-Og; Tue, 01 Jan 2013 05:29:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TpuQ7-0003IO-TI for xen-api@lists.xen.org; Tue, 01 Jan 2013 05:29:48 +0000 Received: from [85.158.137.99:38763] by server-1.bemta-3.messagelabs.com id 52/8D-08906-B4472E05; Tue, 01 Jan 2013 05:29:47 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1357018184!15174237!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=2.4 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32763 invoked from network); 1 Jan 2013 05:29:45 -0000 Received: from mail-la0-f45.google.com (HELO mail-la0-f45.google.com) (209.85.215.45) by server-3.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jan 2013 05:29:45 -0000 Received: by mail-la0-f45.google.com with SMTP id ep20so4627976lab.18 for ; Mon, 31 Dec 2012 21:29:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=Zy66oXIl6ZgfifUPVcs0dkqJm6BZM9n+kMb6kiI4GTo=; b=R9isZjf4fYEd+DHuI2ZpMf069ZZiHYgh3LDiqsmWEBlhleLvoePsqph6TDtLDzV/1X qlYKrx/hB0jwPcddvALYFrgzJXinNtdOlCMUktThiACcYqiz0kpWupRZZ45KEsoPuAYb 58URmtm6yrQmmYIFbjyLJ38XXBfpBwp5hR9QxsyJCCqFGznEkHUHfXLKzM+7knBYpktU fGUMQmyz3zhClqJEoHS1N6elV50gQ+vy0BJFIonvZqsoP6xItBs1fISJ5qsisvhk8CJL ZeURHwecz3SxD5b68cslWvujAildfj6oTbAucFSftMbRvXvOROvedGmlhXj0WY9MUzE4 PhuA== X-Received: by 10.112.13.133 with SMTP id h5mr16676351lbc.99.1357018184589; Mon, 31 Dec 2012 21:29:44 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id jk8sm16097648lab.7.2012.12.31.21.29.43 (version=SSLv3 cipher=OTHER); Mon, 31 Dec 2012 21:29:44 -0800 (PST) Message-ID: <50E27447.4050604@gmail.com> Date: Tue, 01 Jan 2013 09:29:43 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] XCP 1.6 BUG: locking-mode not working X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7502784619748589478==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7502784619748589478== Content-Type: multipart/alternative; boundary="------------020002000305050105070104" This is a multi-part message in MIME format. --------------020002000305050105070104 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Yep, there is a nasty bug in setup-vif-rules. See https://github.com/xen-org/xen-api/pull/953 That 'hardcoded' name is not simply 'not always works', it combines 'xenbr' line with devid (wich is network interface number in domU, not the bridge number). So the code is completely broken and works only in case 'xenbr0, devid=0'. Here proper patch. (If you'll test is with xapi interfaces, please report results): diff --git a/scripts/setup-vif-rules b/scripts/setup-vif-rules index 4ca7230..199b3e1 100755 --- a/scripts/setup-vif-rules +++ b/scripts/setup-vif-rules @@ -229,10 +229,15 @@ def create_vswitch_rules(bridge_name, port, config): # Drop everything else. add_flow(bridge_name, "in_port=%s,priority=4000,idle_timeout=0,action=drop +def get_bridge_name_vswitch(vif_name): + '''return bridge vif belong to''' + (rc, stdout, stderr) = doexec([vsctl, "iface-to-br", vif_name ]) + return stdout.readline().strip() + def handle_vswitch(vif_type, domid, devid, action): if (action == "clear") or (action == "filter"): - bridge_name = "xenbr%s" % devid vif_name = "%s%s.%s" % (vif_type, domid, devid) + bridge_name = get_bridge_name_vswitch(vif_name) ip_link_set(vif_name, "down") port = get_vswitch_port(vif_name) clear_vswitch_rules(bridge_name, port) 30.12.2012 21:19, Tomas Sulo ?????: > Hi, > > I think I've found a bug in the setup-vif-rules script. I have > configured locking mode on one VM: > > / locking-mode ( RW): locked > ipv4-allowed (SRW): 192.168.1.13 > ipv6-allowed (SRW):/ > > However I found out that even after I change the IP on the VM it's > still available on the network. > > I've checked the logs on the server and I found this for example: > > /python: /opt/xensource/libexec/setup-vif-rules[18647] - > ['/usr/bin/ovs-ofctl', 'add-flow', 'xenbr0', > 'in_port=3,priority=8000,dl_type=0x > 0800,nw_proto=0x11,tp_dst=67,dl_src=96:7e:2b:1c:45:81,idle_timeout=0,action=norm > al']/ > > Notice the xenbr0 interface. > > /ovs-ofctl dump-flows xenbr0 > ovs-ofctl: xenbr0 is not a bridge or a socket/ > > xenbr0 doesn't even exist, instead it should be applied to xapi2 in > this case. > > The problem seems to be in the handle_vswitch definition in the > setup-vif-rules script: > > /def handle_vswitch(vif_type, domid, devid, action): > if (action == "clear") or (action == "filter"): > bridge_name = "xenbr%s" % devid > vif_name = "%s%s.%s" % (vif_type, domid, devid) > ip_link_set(vif_name, "down") > port = get_vswitch_port(vif_name) > clear_vswitch_rules(bridge_name, port) > if action == "filter": > config = get_locking_config(domid, devid) > locking_mode = config["locking_mode"] > if locking_mode == "locked": > create_vswitch_rules(bridge_name, port, config) > if locking_mode in ["locked", "unlocked"]: > ip_link_set(vif_name, "up") > if action == "clear": > ip_link_set(vif_name, "up")/ > > Notice the hardcoded xenbr? After changing to /bridge_name = "xapi2" > /everything works fine. In my case it's always xapi2. I haven't had > time for an elegant solution. > > After this I've started the VM again and everything was working as it > should. After I changed the IP of the VM it was no longer available on > the network. > And here are the ovs-ofctl flows: > > / ovs-ofctl dump-flows xapi2 > NXST_FLOW reply (xid=0x4): > cookie=0x0, duration=55.637s, table=0, n_packets=0, n_bytes=0, > priority=4000,in_port=4 actions=drop > cookie=0x0, duration=55.769s, table=0, n_packets=5, n_bytes=270, > priority=6000,ip,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=192.168.1.13 actions=NORMAL > cookie=0x0, duration=55.795s, table=0, n_packets=0, n_bytes=0, > priority=7000,arp,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=0.0.0.0,arp_sha=96:7e:2b:1c:45:81 > actions=NORMAL > cookie=0x0, duration=55.782s, table=0, n_packets=3, n_bytes=126, > priority=7000,arp,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=192.168.1.13,arp_sha=96:7e:2b:1c:45:81 > actions=NORMAL > cookie=0x0, duration=55.808s, table=0, n_packets=0, n_bytes=0, > priority=8000,udp,in_port=4,dl_src=96:7e:2b:1c:45:81,tp_dst=67 > actions=NORMAL > cookie=0x0, duration=3788.414s, table=0, n_packets=309587, > n_bytes=91537264, priority=0 actions=NORMAL > cookie=0x0, duration=55.729s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=134 actions=drop > cookie=0x0, duration=55.703s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=146 actions=drop > cookie=0x0, duration=55.742s, table=0, n_packets=0, n_bytes=0, > priority=7000,icmp6,in_port=4,icmp_type=136 actions=drop > cookie=0x0, duration=55.65s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=153 actions=drop > cookie=0x0, duration=55.755s, table=0, n_packets=0, n_bytes=0, > priority=7000,icmp6,in_port=4,icmp_type=135 actions=drop > cookie=0x0, duration=55.716s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=137 actions=drop > cookie=0x0, duration=55.677s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=151 actions=drop > cookie=0x0, duration=55.69s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=147 actions=drop > cookie=0x0, duration=55.664s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=152 actions=drop/ > > I've seen on the internet that more users are facing this issue so > maybe this helps. I hope I didn't write anything stupid, I'm quite new > to XCP. :) > > Tomas > > > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------020002000305050105070104 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Yep, there is a nasty bug in setup-vif-rules.

See https://github.com/xen-org/xen-api/pull/953

That 'hardcoded' name is not simply 'not always works', it combines 'xenbr' line with devid (wich is network interface number in domU, not the bridge number).

So the code is completely broken and works only in case 'xenbr0, devid=0'.

Here proper patch. (If you'll test is with xapi interfaces, please report results):

diff --git a/scripts/setup-vif-rules b/scripts/setup-vif-rules
index 4ca7230..199b3e1 100755
--- a/scripts/setup-vif-rules
+++ b/scripts/setup-vif-rules
@@ -229,10 +229,15 @@ def create_vswitch_rules(bridge_name, port, config):
     # Drop everything else.
     add_flow(bridge_name, "in_port=%s,priority=4000,idle_timeout=0,action=drop
 
+def get_bridge_name_vswitch(vif_name):
+    '''return bridge vif belong to'''
+    (rc, stdout, stderr) = doexec([vsctl, "iface-to-br",  vif_name ])
+    return stdout.readline().strip()
+
 def handle_vswitch(vif_type, domid, devid, action):
     if (action == "clear") or (action == "filter"):
-        bridge_name = "xenbr%s" % devid
         vif_name = "%s%s.%s" % (vif_type, domid, devid)
+        bridge_name = get_bridge_name_vswitch(vif_name)
         ip_link_set(vif_name, "down")
         port = get_vswitch_port(vif_name)
         clear_vswitch_rules(bridge_name, port)


30.12.2012 21:19, Tomas Sulo пишет:
Hi,

I think I've found a bug in the setup-vif-rules script. I have configured locking mode on one VM:

                locking-mode ( RW): locked
                ipv4-allowed (SRW): 192.168.1.13
                ipv6-allowed (SRW):

However I found out that even after I change the IP on the VM it's still available on the network.

I've checked the logs on the server and I found this for example:

python: /opt/xensource/libexec/setup-vif-rules[18647] -
['/usr/bin/ovs-ofctl', 'add-flow', 'xenbr0', 'in_port=3,priority=8000,dl_type=0x
0800,nw_proto=0x11,tp_dst=67,dl_src=96:7e:2b:1c:45:81,idle_timeout=0,action=norm
al']

Notice the xenbr0 interface.

ovs-ofctl dump-flows xenbr0                                  
ovs-ofctl: xenbr0 is not a bridge or a socket

xenbr0 doesn't even exist, instead it should be applied to xapi2 in this case.

The problem seems to be in the handle_vswitch definition in the setup-vif-rules script:

def handle_vswitch(vif_type, domid, devid, action):
    if (action == "clear") or (action == "filter"):
        bridge_name = "xenbr%s" % devid
        vif_name = "%s%s.%s" % (vif_type, domid, devid)
        ip_link_set(vif_name, "down")
        port = get_vswitch_port(vif_name)
        clear_vswitch_rules(bridge_name, port)
        if action == "filter":
            config = get_locking_config(domid, devid)
            locking_mode = config["locking_mode"]
            if locking_mode == "locked":
                create_vswitch_rules(bridge_name, port, config)
            if locking_mode in ["locked", "unlocked"]:
                ip_link_set(vif_name, "up")
        if action == "clear":
            ip_link_set(vif_name, "up")

Notice the hardcoded xenbr? After changing to bridge_name = "xapi2" everything works fine. In my case it's always xapi2. I haven't had time for an elegant solution.

After this I've started the VM again and everything was working as it should. After I changed the IP of the VM it was no longer available on the network.
And here are the ovs-ofctl flows:

 ovs-ofctl dump-flows xapi2
NXST_FLOW reply (xid=0x4):
 cookie=0x0, duration=55.637s, table=0, n_packets=0, n_bytes=0, priority=4000,in_port=4 actions=drop
 cookie=0x0, duration=55.769s, table=0, n_packets=5, n_bytes=270, priority=6000,ip,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=192.168.1.13 actions=NORMAL
 cookie=0x0, duration=55.795s, table=0, n_packets=0, n_bytes=0, priority=7000,arp,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=0.0.0.0,arp_sha=96:7e:2b:1c:45:81 actions=NORMAL
 cookie=0x0, duration=55.782s, table=0, n_packets=3, n_bytes=126, priority=7000,arp,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=192.168.1.13,arp_sha=96:7e:2b:1c:45:81 actions=NORMAL
 cookie=0x0, duration=55.808s, table=0, n_packets=0, n_bytes=0, priority=8000,udp,in_port=4,dl_src=96:7e:2b:1c:45:81,tp_dst=67 actions=NORMAL
 cookie=0x0, duration=3788.414s, table=0, n_packets=309587, n_bytes=91537264, priority=0 actions=NORMAL
 cookie=0x0, duration=55.729s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=134 actions=drop
 cookie=0x0, duration=55.703s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=146 actions=drop
 cookie=0x0, duration=55.742s, table=0, n_packets=0, n_bytes=0, priority=7000,icmp6,in_port=4,icmp_type=136 actions=drop
 cookie=0x0, duration=55.65s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=153 actions=drop
 cookie=0x0, duration=55.755s, table=0, n_packets=0, n_bytes=0, priority=7000,icmp6,in_port=4,icmp_type=135 actions=drop
 cookie=0x0, duration=55.716s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=137 actions=drop
 cookie=0x0, duration=55.677s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=151 actions=drop
 cookie=0x0, duration=55.69s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=147 actions=drop
 cookie=0x0, duration=55.664s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=152 actions=drop

I've seen on the internet that more users are facing this issue so maybe this helps. I hope I didn't write anything stupid, I'm quite new to XCP. :)

Tomas 







_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------020002000305050105070104-- --===============7502784619748589478== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7502784619748589478==-- From xen-api-bounces@lists.xen.org Tue Jan 01 05:30:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 01 Jan 2013 05:30:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TpuQ9-0003IT-Og; Tue, 01 Jan 2013 05:29:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TpuQ7-0003IO-TI for xen-api@lists.xen.org; Tue, 01 Jan 2013 05:29:48 +0000 Received: from [85.158.137.99:38763] by server-1.bemta-3.messagelabs.com id 52/8D-08906-B4472E05; Tue, 01 Jan 2013 05:29:47 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1357018184!15174237!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=2.4 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32763 invoked from network); 1 Jan 2013 05:29:45 -0000 Received: from mail-la0-f45.google.com (HELO mail-la0-f45.google.com) (209.85.215.45) by server-3.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jan 2013 05:29:45 -0000 Received: by mail-la0-f45.google.com with SMTP id ep20so4627976lab.18 for ; Mon, 31 Dec 2012 21:29:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=Zy66oXIl6ZgfifUPVcs0dkqJm6BZM9n+kMb6kiI4GTo=; b=R9isZjf4fYEd+DHuI2ZpMf069ZZiHYgh3LDiqsmWEBlhleLvoePsqph6TDtLDzV/1X qlYKrx/hB0jwPcddvALYFrgzJXinNtdOlCMUktThiACcYqiz0kpWupRZZ45KEsoPuAYb 58URmtm6yrQmmYIFbjyLJ38XXBfpBwp5hR9QxsyJCCqFGznEkHUHfXLKzM+7knBYpktU fGUMQmyz3zhClqJEoHS1N6elV50gQ+vy0BJFIonvZqsoP6xItBs1fISJ5qsisvhk8CJL ZeURHwecz3SxD5b68cslWvujAildfj6oTbAucFSftMbRvXvOROvedGmlhXj0WY9MUzE4 PhuA== X-Received: by 10.112.13.133 with SMTP id h5mr16676351lbc.99.1357018184589; Mon, 31 Dec 2012 21:29:44 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id jk8sm16097648lab.7.2012.12.31.21.29.43 (version=SSLv3 cipher=OTHER); Mon, 31 Dec 2012 21:29:44 -0800 (PST) Message-ID: <50E27447.4050604@gmail.com> Date: Tue, 01 Jan 2013 09:29:43 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] XCP 1.6 BUG: locking-mode not working X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7502784619748589478==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7502784619748589478== Content-Type: multipart/alternative; boundary="------------020002000305050105070104" This is a multi-part message in MIME format. --------------020002000305050105070104 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Yep, there is a nasty bug in setup-vif-rules. See https://github.com/xen-org/xen-api/pull/953 That 'hardcoded' name is not simply 'not always works', it combines 'xenbr' line with devid (wich is network interface number in domU, not the bridge number). So the code is completely broken and works only in case 'xenbr0, devid=0'. Here proper patch. (If you'll test is with xapi interfaces, please report results): diff --git a/scripts/setup-vif-rules b/scripts/setup-vif-rules index 4ca7230..199b3e1 100755 --- a/scripts/setup-vif-rules +++ b/scripts/setup-vif-rules @@ -229,10 +229,15 @@ def create_vswitch_rules(bridge_name, port, config): # Drop everything else. add_flow(bridge_name, "in_port=%s,priority=4000,idle_timeout=0,action=drop +def get_bridge_name_vswitch(vif_name): + '''return bridge vif belong to''' + (rc, stdout, stderr) = doexec([vsctl, "iface-to-br", vif_name ]) + return stdout.readline().strip() + def handle_vswitch(vif_type, domid, devid, action): if (action == "clear") or (action == "filter"): - bridge_name = "xenbr%s" % devid vif_name = "%s%s.%s" % (vif_type, domid, devid) + bridge_name = get_bridge_name_vswitch(vif_name) ip_link_set(vif_name, "down") port = get_vswitch_port(vif_name) clear_vswitch_rules(bridge_name, port) 30.12.2012 21:19, Tomas Sulo ?????: > Hi, > > I think I've found a bug in the setup-vif-rules script. I have > configured locking mode on one VM: > > / locking-mode ( RW): locked > ipv4-allowed (SRW): 192.168.1.13 > ipv6-allowed (SRW):/ > > However I found out that even after I change the IP on the VM it's > still available on the network. > > I've checked the logs on the server and I found this for example: > > /python: /opt/xensource/libexec/setup-vif-rules[18647] - > ['/usr/bin/ovs-ofctl', 'add-flow', 'xenbr0', > 'in_port=3,priority=8000,dl_type=0x > 0800,nw_proto=0x11,tp_dst=67,dl_src=96:7e:2b:1c:45:81,idle_timeout=0,action=norm > al']/ > > Notice the xenbr0 interface. > > /ovs-ofctl dump-flows xenbr0 > ovs-ofctl: xenbr0 is not a bridge or a socket/ > > xenbr0 doesn't even exist, instead it should be applied to xapi2 in > this case. > > The problem seems to be in the handle_vswitch definition in the > setup-vif-rules script: > > /def handle_vswitch(vif_type, domid, devid, action): > if (action == "clear") or (action == "filter"): > bridge_name = "xenbr%s" % devid > vif_name = "%s%s.%s" % (vif_type, domid, devid) > ip_link_set(vif_name, "down") > port = get_vswitch_port(vif_name) > clear_vswitch_rules(bridge_name, port) > if action == "filter": > config = get_locking_config(domid, devid) > locking_mode = config["locking_mode"] > if locking_mode == "locked": > create_vswitch_rules(bridge_name, port, config) > if locking_mode in ["locked", "unlocked"]: > ip_link_set(vif_name, "up") > if action == "clear": > ip_link_set(vif_name, "up")/ > > Notice the hardcoded xenbr? After changing to /bridge_name = "xapi2" > /everything works fine. In my case it's always xapi2. I haven't had > time for an elegant solution. > > After this I've started the VM again and everything was working as it > should. After I changed the IP of the VM it was no longer available on > the network. > And here are the ovs-ofctl flows: > > / ovs-ofctl dump-flows xapi2 > NXST_FLOW reply (xid=0x4): > cookie=0x0, duration=55.637s, table=0, n_packets=0, n_bytes=0, > priority=4000,in_port=4 actions=drop > cookie=0x0, duration=55.769s, table=0, n_packets=5, n_bytes=270, > priority=6000,ip,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=192.168.1.13 actions=NORMAL > cookie=0x0, duration=55.795s, table=0, n_packets=0, n_bytes=0, > priority=7000,arp,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=0.0.0.0,arp_sha=96:7e:2b:1c:45:81 > actions=NORMAL > cookie=0x0, duration=55.782s, table=0, n_packets=3, n_bytes=126, > priority=7000,arp,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=192.168.1.13,arp_sha=96:7e:2b:1c:45:81 > actions=NORMAL > cookie=0x0, duration=55.808s, table=0, n_packets=0, n_bytes=0, > priority=8000,udp,in_port=4,dl_src=96:7e:2b:1c:45:81,tp_dst=67 > actions=NORMAL > cookie=0x0, duration=3788.414s, table=0, n_packets=309587, > n_bytes=91537264, priority=0 actions=NORMAL > cookie=0x0, duration=55.729s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=134 actions=drop > cookie=0x0, duration=55.703s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=146 actions=drop > cookie=0x0, duration=55.742s, table=0, n_packets=0, n_bytes=0, > priority=7000,icmp6,in_port=4,icmp_type=136 actions=drop > cookie=0x0, duration=55.65s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=153 actions=drop > cookie=0x0, duration=55.755s, table=0, n_packets=0, n_bytes=0, > priority=7000,icmp6,in_port=4,icmp_type=135 actions=drop > cookie=0x0, duration=55.716s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=137 actions=drop > cookie=0x0, duration=55.677s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=151 actions=drop > cookie=0x0, duration=55.69s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=147 actions=drop > cookie=0x0, duration=55.664s, table=0, n_packets=0, n_bytes=0, > priority=6000,icmp6,in_port=4,icmp_type=152 actions=drop/ > > I've seen on the internet that more users are facing this issue so > maybe this helps. I hope I didn't write anything stupid, I'm quite new > to XCP. :) > > Tomas > > > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------020002000305050105070104 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Yep, there is a nasty bug in setup-vif-rules.

See https://github.com/xen-org/xen-api/pull/953

That 'hardcoded' name is not simply 'not always works', it combines 'xenbr' line with devid (wich is network interface number in domU, not the bridge number).

So the code is completely broken and works only in case 'xenbr0, devid=0'.

Here proper patch. (If you'll test is with xapi interfaces, please report results):

diff --git a/scripts/setup-vif-rules b/scripts/setup-vif-rules
index 4ca7230..199b3e1 100755
--- a/scripts/setup-vif-rules
+++ b/scripts/setup-vif-rules
@@ -229,10 +229,15 @@ def create_vswitch_rules(bridge_name, port, config):
     # Drop everything else.
     add_flow(bridge_name, "in_port=%s,priority=4000,idle_timeout=0,action=drop
 
+def get_bridge_name_vswitch(vif_name):
+    '''return bridge vif belong to'''
+    (rc, stdout, stderr) = doexec([vsctl, "iface-to-br",  vif_name ])
+    return stdout.readline().strip()
+
 def handle_vswitch(vif_type, domid, devid, action):
     if (action == "clear") or (action == "filter"):
-        bridge_name = "xenbr%s" % devid
         vif_name = "%s%s.%s" % (vif_type, domid, devid)
+        bridge_name = get_bridge_name_vswitch(vif_name)
         ip_link_set(vif_name, "down")
         port = get_vswitch_port(vif_name)
         clear_vswitch_rules(bridge_name, port)


30.12.2012 21:19, Tomas Sulo пишет:
Hi,

I think I've found a bug in the setup-vif-rules script. I have configured locking mode on one VM:

                locking-mode ( RW): locked
                ipv4-allowed (SRW): 192.168.1.13
                ipv6-allowed (SRW):

However I found out that even after I change the IP on the VM it's still available on the network.

I've checked the logs on the server and I found this for example:

python: /opt/xensource/libexec/setup-vif-rules[18647] -
['/usr/bin/ovs-ofctl', 'add-flow', 'xenbr0', 'in_port=3,priority=8000,dl_type=0x
0800,nw_proto=0x11,tp_dst=67,dl_src=96:7e:2b:1c:45:81,idle_timeout=0,action=norm
al']

Notice the xenbr0 interface.

ovs-ofctl dump-flows xenbr0                                  
ovs-ofctl: xenbr0 is not a bridge or a socket

xenbr0 doesn't even exist, instead it should be applied to xapi2 in this case.

The problem seems to be in the handle_vswitch definition in the setup-vif-rules script:

def handle_vswitch(vif_type, domid, devid, action):
    if (action == "clear") or (action == "filter"):
        bridge_name = "xenbr%s" % devid
        vif_name = "%s%s.%s" % (vif_type, domid, devid)
        ip_link_set(vif_name, "down")
        port = get_vswitch_port(vif_name)
        clear_vswitch_rules(bridge_name, port)
        if action == "filter":
            config = get_locking_config(domid, devid)
            locking_mode = config["locking_mode"]
            if locking_mode == "locked":
                create_vswitch_rules(bridge_name, port, config)
            if locking_mode in ["locked", "unlocked"]:
                ip_link_set(vif_name, "up")
        if action == "clear":
            ip_link_set(vif_name, "up")

Notice the hardcoded xenbr? After changing to bridge_name = "xapi2" everything works fine. In my case it's always xapi2. I haven't had time for an elegant solution.

After this I've started the VM again and everything was working as it should. After I changed the IP of the VM it was no longer available on the network.
And here are the ovs-ofctl flows:

 ovs-ofctl dump-flows xapi2
NXST_FLOW reply (xid=0x4):
 cookie=0x0, duration=55.637s, table=0, n_packets=0, n_bytes=0, priority=4000,in_port=4 actions=drop
 cookie=0x0, duration=55.769s, table=0, n_packets=5, n_bytes=270, priority=6000,ip,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=192.168.1.13 actions=NORMAL
 cookie=0x0, duration=55.795s, table=0, n_packets=0, n_bytes=0, priority=7000,arp,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=0.0.0.0,arp_sha=96:7e:2b:1c:45:81 actions=NORMAL
 cookie=0x0, duration=55.782s, table=0, n_packets=3, n_bytes=126, priority=7000,arp,in_port=4,dl_src=96:7e:2b:1c:45:81,nw_src=192.168.1.13,arp_sha=96:7e:2b:1c:45:81 actions=NORMAL
 cookie=0x0, duration=55.808s, table=0, n_packets=0, n_bytes=0, priority=8000,udp,in_port=4,dl_src=96:7e:2b:1c:45:81,tp_dst=67 actions=NORMAL
 cookie=0x0, duration=3788.414s, table=0, n_packets=309587, n_bytes=91537264, priority=0 actions=NORMAL
 cookie=0x0, duration=55.729s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=134 actions=drop
 cookie=0x0, duration=55.703s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=146 actions=drop
 cookie=0x0, duration=55.742s, table=0, n_packets=0, n_bytes=0, priority=7000,icmp6,in_port=4,icmp_type=136 actions=drop
 cookie=0x0, duration=55.65s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=153 actions=drop
 cookie=0x0, duration=55.755s, table=0, n_packets=0, n_bytes=0, priority=7000,icmp6,in_port=4,icmp_type=135 actions=drop
 cookie=0x0, duration=55.716s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=137 actions=drop
 cookie=0x0, duration=55.677s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=151 actions=drop
 cookie=0x0, duration=55.69s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=147 actions=drop
 cookie=0x0, duration=55.664s, table=0, n_packets=0, n_bytes=0, priority=6000,icmp6,in_port=4,icmp_type=152 actions=drop

I've seen on the internet that more users are facing this issue so maybe this helps. I hope I didn't write anything stupid, I'm quite new to XCP. :)

Tomas 







_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------020002000305050105070104-- --===============7502784619748589478== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7502784619748589478==-- From xen-api-bounces@lists.xen.org Tue Jan 01 05:32:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 01 Jan 2013 05:32:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TpuSW-0003P8-3z; Tue, 01 Jan 2013 05:32:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TpuSU-0003P0-No for xen-api@lists.xen.org; Tue, 01 Jan 2013 05:32:15 +0000 Received: from [193.109.254.147:59639] by server-16.bemta-14.messagelabs.com id 82/28-18932-ED472E05; Tue, 01 Jan 2013 05:32:14 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1357018332!10309526!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=1.9 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13441 invoked from network); 1 Jan 2013 05:32:12 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jan 2013 05:32:12 -0000 Received: by mail-la0-f49.google.com with SMTP id fk20so4509655lab.8 for ; Mon, 31 Dec 2012 21:32:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=WJlRx6fruf4GoFzDdpDkrs6BBHa/1iC7zf1Gl589Hy0=; b=CNGRz2TISKEgpqugXao1FHlKWJKWI8mFzLNEG7i4gjcfZGz2tx4Zs8IRuBK1dpkrEC LveIOnBkNTi3XRbr8fJBu5CQwksNqDo5fng1GuUwTOkBK+j8N6V6fyGOh+/b/nls6/MG mJnYGim8tQbjdj2a1bANyn0KmkhhGIPOTjmoHYZ4nBHbHz2IsXBqQnceM5sswkrsG1F2 P5r8rGuMEMSe7CRNprm00/aRX0dhQgpjVhLpL9/8m2cxiAbmp2FM1qsag7L+j0RzF9pn sfgp/3ST+Mh4s2bMAvBMIvS3qMrOvq/kQe+nfhjh71BR532c4IWIthJFsXtqI292EvLi cceg== X-Received: by 10.112.87.104 with SMTP id w8mr17618519lbz.49.1357018332034; Mon, 31 Dec 2012 21:32:12 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id fe4sm14916289lbb.1.2012.12.31.21.32.11 (version=SSLv3 cipher=OTHER); Mon, 31 Dec 2012 21:32:11 -0800 (PST) Message-ID: <50E274DA.5010000@gmail.com> Date: Tue, 01 Jan 2013 09:32:10 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <201212311004494374333@gmail.com> In-Reply-To: <201212311004494374333@gmail.com> Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5555299222573488860==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5555299222573488860== Content-Type: multipart/alternative; boundary="------------070701020405020607070302" This is a multi-part message in MIME format. --------------070701020405020607070302 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Not yet. My test machines fly between pools like a magic. Please provides xensource.log pieces from both sides: sender and receiver. I think, they should be pool's masters logs. PS Do not forget to set up default-sr pool property on receiver. 31.12.2012 06:04, Tianpeng Zhang ?????: > Hi All, > I got one issue with xcp1.6 when testing VM storage xenMotion to > another host. It reported error as an "internal error". Have anyone > met this issue before? Or give some tips for this issue? > Thanks. > [root@xcp102 ~]# xe vm-migrate destination-sr-uuid=2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e vm=CentOS6-PV remote-master=10.33.2.103 remote-password=passwd remote-username=root > Performing a Storage XenMotion migration. Your VM's VDIs will be migrated with the VM. > Will migrate to remote host: xcp103, using remote network: Pool-wide network associated with eth0. Here is the VDI mapping: > VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e > VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e > The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. > message: Import.IFailure(2) > [root@xcp102 ~]# > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------070701020405020607070302 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Not yet. My test machines fly between pools like a magic.

Please provides xensource.log pieces from both sides: sender and receiver. I think, they should be pool's masters logs.

PS Do not forget to set up default-sr pool property on receiver.

31.12.2012 06:04, Tianpeng Zhang пишет:
Hi All,
 
I got one issue with xcp1.6 when testing VM storage xenMotion to another host. It reported error as an "internal error". Have anyone met this issue before? Or give some tips for this issue?
 
Thanks. 
 
[root@xcp102 ~]# xe vm-migrate destination-sr-uuid=2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e vm=CentOS6-PV remote-master=10.33.2.103 remote-password=passwd remote-username=root
Performing a Storage XenMotion migration. Your VM's VDIs will be migrated with the VM.
Will migrate to remote host: xcp103, using remote network: Pool-wide network associated with eth0. Here is the VDI mapping:
VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e
VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e
The server failed to handle your request, due to an internal error.  The given message may give details useful for debugging the problem.
message: Import.IFailure(2)
[root@xcp102 ~]#


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------070701020405020607070302-- --===============5555299222573488860== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5555299222573488860==-- From xen-api-bounces@lists.xen.org Tue Jan 01 05:32:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 01 Jan 2013 05:32:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TpuSW-0003P8-3z; Tue, 01 Jan 2013 05:32:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TpuSU-0003P0-No for xen-api@lists.xen.org; Tue, 01 Jan 2013 05:32:15 +0000 Received: from [193.109.254.147:59639] by server-16.bemta-14.messagelabs.com id 82/28-18932-ED472E05; Tue, 01 Jan 2013 05:32:14 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1357018332!10309526!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=1.9 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13441 invoked from network); 1 Jan 2013 05:32:12 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jan 2013 05:32:12 -0000 Received: by mail-la0-f49.google.com with SMTP id fk20so4509655lab.8 for ; Mon, 31 Dec 2012 21:32:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=WJlRx6fruf4GoFzDdpDkrs6BBHa/1iC7zf1Gl589Hy0=; b=CNGRz2TISKEgpqugXao1FHlKWJKWI8mFzLNEG7i4gjcfZGz2tx4Zs8IRuBK1dpkrEC LveIOnBkNTi3XRbr8fJBu5CQwksNqDo5fng1GuUwTOkBK+j8N6V6fyGOh+/b/nls6/MG mJnYGim8tQbjdj2a1bANyn0KmkhhGIPOTjmoHYZ4nBHbHz2IsXBqQnceM5sswkrsG1F2 P5r8rGuMEMSe7CRNprm00/aRX0dhQgpjVhLpL9/8m2cxiAbmp2FM1qsag7L+j0RzF9pn sfgp/3ST+Mh4s2bMAvBMIvS3qMrOvq/kQe+nfhjh71BR532c4IWIthJFsXtqI292EvLi cceg== X-Received: by 10.112.87.104 with SMTP id w8mr17618519lbz.49.1357018332034; Mon, 31 Dec 2012 21:32:12 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id fe4sm14916289lbb.1.2012.12.31.21.32.11 (version=SSLv3 cipher=OTHER); Mon, 31 Dec 2012 21:32:11 -0800 (PST) Message-ID: <50E274DA.5010000@gmail.com> Date: Tue, 01 Jan 2013 09:32:10 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <201212311004494374333@gmail.com> In-Reply-To: <201212311004494374333@gmail.com> Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5555299222573488860==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5555299222573488860== Content-Type: multipart/alternative; boundary="------------070701020405020607070302" This is a multi-part message in MIME format. --------------070701020405020607070302 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Not yet. My test machines fly between pools like a magic. Please provides xensource.log pieces from both sides: sender and receiver. I think, they should be pool's masters logs. PS Do not forget to set up default-sr pool property on receiver. 31.12.2012 06:04, Tianpeng Zhang ?????: > Hi All, > I got one issue with xcp1.6 when testing VM storage xenMotion to > another host. It reported error as an "internal error". Have anyone > met this issue before? Or give some tips for this issue? > Thanks. > [root@xcp102 ~]# xe vm-migrate destination-sr-uuid=2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e vm=CentOS6-PV remote-master=10.33.2.103 remote-password=passwd remote-username=root > Performing a Storage XenMotion migration. Your VM's VDIs will be migrated with the VM. > Will migrate to remote host: xcp103, using remote network: Pool-wide network associated with eth0. Here is the VDI mapping: > VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e > VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e > The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. > message: Import.IFailure(2) > [root@xcp102 ~]# > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------070701020405020607070302 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Not yet. My test machines fly between pools like a magic.

Please provides xensource.log pieces from both sides: sender and receiver. I think, they should be pool's masters logs.

PS Do not forget to set up default-sr pool property on receiver.

31.12.2012 06:04, Tianpeng Zhang пишет:
Hi All,
 
I got one issue with xcp1.6 when testing VM storage xenMotion to another host. It reported error as an "internal error". Have anyone met this issue before? Or give some tips for this issue?
 
Thanks. 
 
[root@xcp102 ~]# xe vm-migrate destination-sr-uuid=2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e vm=CentOS6-PV remote-master=10.33.2.103 remote-password=passwd remote-username=root
Performing a Storage XenMotion migration. Your VM's VDIs will be migrated with the VM.
Will migrate to remote host: xcp103, using remote network: Pool-wide network associated with eth0. Here is the VDI mapping:
VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e
VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e
The server failed to handle your request, due to an internal error.  The given message may give details useful for debugging the problem.
message: Import.IFailure(2)
[root@xcp102 ~]#


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------070701020405020607070302-- --===============5555299222573488860== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5555299222573488860==-- From xen-api-bounces@lists.xen.org Tue Jan 01 18:36:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 01 Jan 2013 18:36:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tq6hd-0001kp-Pt; Tue, 01 Jan 2013 18:36:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tq6hd-0001kk-1S for xen-api@lists.xen.org; Tue, 01 Jan 2013 18:36:41 +0000 Received: from [85.158.138.51:23814] by server-13.bemta-3.messagelabs.com id DC/93-00465-8BC23E05; Tue, 01 Jan 2013 18:36:40 +0000 X-Env-Sender: philipp@phflesch.de X-Msg-Ref: server-15.tower-174.messagelabs.com!1357065398!29108013!1 X-Originating-IP: [176.9.200.162] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2212 invoked from network); 1 Jan 2013 18:36:39 -0000 Received: from s4.twanas.de (HELO s4.twanas.de) (176.9.200.162) by server-15.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Jan 2013 18:36:39 -0000 Received: from localhost (localhost [127.0.0.1]) by s4.twanas.de (Postfix) with ESMTP id 9E24AE06C2 for ; Tue, 1 Jan 2013 19:36:38 +0100 (CET) Received: from s4.twanas.de ([127.0.0.1]) by localhost (s4.twanas.de [127.0.0.1]) (maiad, port 10024) with ESMTP id 02753-01 for ; Tue, 1 Jan 2013 19:36:37 +0100 (CET) Received: from [192.168.1.102] (p4FE155E3.dip.t-dialin.net [79.225.85.227]) by s4.twanas.de (Postfix) with ESMTPSA id 47BD7E06C1 for ; Tue, 1 Jan 2013 19:36:37 +0100 (CET) Message-ID: <50E32CBA.3020909@phflesch.de> Date: Tue, 01 Jan 2013 19:36:42 +0100 From: Philipp Flesch User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org X-Virus-Scanned: Maia Mailguard 1.0.3 Subject: [Xen-API] XCP 1.6 - Error Importing OVF X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi! I already imported some .xva-files without any problems. I now wanted to start migrating our ESXi-farm ... First of all, I installed the XENSERVER Transfer VMs on both servers (following http://blogs.citrix.com/2010/12/09/diagnosing-xenserver-appliance-wizard-failures/) and I also imported the Citrix XCM Virtual Appliance. Both from XenServer 6.1 I followed http://support.citrix.com/article/CTX133505 and exported an ovf to the local harddrive. Starting the import via XenCenter 6.1 the required vm-drive is created, but than the import fails ... Having a closer look to the vmdk: root@linux-workstation:/mnt/ad02-temp/unterricht# qemu-img info Unterricht_neu-disk1.vmdk image: Unterricht_neu-disk1.vmdk file format: vmdk virtual size: 16G (17179869184 bytes) disk size: 1.0G So the vmdk seems to be okay ... I copied the log to http://wvbg.bndlg.de/~max/xen/xencenter.log Any hints? Thank you very much. Philipp _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 01 18:36:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 01 Jan 2013 18:36:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tq6hd-0001kp-Pt; Tue, 01 Jan 2013 18:36:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tq6hd-0001kk-1S for xen-api@lists.xen.org; Tue, 01 Jan 2013 18:36:41 +0000 Received: from [85.158.138.51:23814] by server-13.bemta-3.messagelabs.com id DC/93-00465-8BC23E05; Tue, 01 Jan 2013 18:36:40 +0000 X-Env-Sender: philipp@phflesch.de X-Msg-Ref: server-15.tower-174.messagelabs.com!1357065398!29108013!1 X-Originating-IP: [176.9.200.162] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2212 invoked from network); 1 Jan 2013 18:36:39 -0000 Received: from s4.twanas.de (HELO s4.twanas.de) (176.9.200.162) by server-15.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Jan 2013 18:36:39 -0000 Received: from localhost (localhost [127.0.0.1]) by s4.twanas.de (Postfix) with ESMTP id 9E24AE06C2 for ; Tue, 1 Jan 2013 19:36:38 +0100 (CET) Received: from s4.twanas.de ([127.0.0.1]) by localhost (s4.twanas.de [127.0.0.1]) (maiad, port 10024) with ESMTP id 02753-01 for ; Tue, 1 Jan 2013 19:36:37 +0100 (CET) Received: from [192.168.1.102] (p4FE155E3.dip.t-dialin.net [79.225.85.227]) by s4.twanas.de (Postfix) with ESMTPSA id 47BD7E06C1 for ; Tue, 1 Jan 2013 19:36:37 +0100 (CET) Message-ID: <50E32CBA.3020909@phflesch.de> Date: Tue, 01 Jan 2013 19:36:42 +0100 From: Philipp Flesch User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org X-Virus-Scanned: Maia Mailguard 1.0.3 Subject: [Xen-API] XCP 1.6 - Error Importing OVF X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi! I already imported some .xva-files without any problems. I now wanted to start migrating our ESXi-farm ... First of all, I installed the XENSERVER Transfer VMs on both servers (following http://blogs.citrix.com/2010/12/09/diagnosing-xenserver-appliance-wizard-failures/) and I also imported the Citrix XCM Virtual Appliance. Both from XenServer 6.1 I followed http://support.citrix.com/article/CTX133505 and exported an ovf to the local harddrive. Starting the import via XenCenter 6.1 the required vm-drive is created, but than the import fails ... Having a closer look to the vmdk: root@linux-workstation:/mnt/ad02-temp/unterricht# qemu-img info Unterricht_neu-disk1.vmdk image: Unterricht_neu-disk1.vmdk file format: vmdk virtual size: 16G (17179869184 bytes) disk size: 1.0G So the vmdk seems to be okay ... I copied the log to http://wvbg.bndlg.de/~max/xen/xencenter.log Any hints? Thank you very much. Philipp _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 01 21:06:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 01 Jan 2013 21:06:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tq92d-0003AB-Rv; Tue, 01 Jan 2013 21:06:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tq92c-0003A5-Nd for xen-api@lists.xen.org; Tue, 01 Jan 2013 21:06:30 +0000 Received: from [85.158.139.83:23790] by server-12.bemta-5.messagelabs.com id 3D/76-02275-5DF43E05; Tue, 01 Jan 2013 21:06:29 +0000 X-Env-Sender: mikael@servercentralen.se X-Msg-Ref: server-8.tower-182.messagelabs.com!1357074389!17103142!1 X-Originating-IP: [188.95.35.85] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29485 invoked from network); 1 Jan 2013 21:06:29 -0000 Received: from solna-gw2.centralcloud.net (HELO smtpedge.centralcloud.net) (188.95.35.85) by server-8.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 1 Jan 2013 21:06:29 -0000 Received: from SOLNA-MBX01.nschmc.local ([fe80::2498:f5a:2882:1d75]) by SOLNA-HUB01.nschmc.local ([fe80::d1e0:f192:d7:464a%11]) with mapi id 14.02.0318.004; Tue, 1 Jan 2013 22:09:33 +0100 From: Mikael Hugo To: "xen-api@lists.xen.org" Thread-Topic: Intel 82574L in XCP 1.6 and vlan Thread-Index: AQHN6GRLuLsyizZFEUC1uWXZ9gjHkw== Date: Tue, 1 Jan 2013 21:09:32 +0000 Message-ID: <23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7@SOLNA-MBX01.nschmc.local> Accept-Language: sv-SE, en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.5.121010 x-originating-ip: [192.168.68.2] MIME-Version: 1.0 Subject: [Xen-API] Intel 82574L in XCP 1.6 and vlan X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2601972336440302662==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2601972336440302662== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7SOLNAMBX01nschm_" --_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7SOLNAMBX01nschm_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi! I have issues with 82574L in XCP 1.6 - It works untagged but not with tagged vlans. I see Xenserver 6.1 has an updated driver kit for Intel and it feels like it must be a driver issue since I get zero traffic. Any good way to figure it out or any known fix? /Mikael --_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7SOLNAMBX01nschm_ Content-Type: text/html; charset="us-ascii" Content-ID: <8D4A8AACE1AF4E4891CE6802167AF22B@nschmc.local> Content-Transfer-Encoding: quoted-printable
Hi!

I have issues wit= h 82574L in XCP 1.6 - It works untagged but not with
tagged vlans.

I see Xenserver 6= .1 has an updated driver kit for Intel and it feels like
it must be a driv= er issue since I get zero traffic.

Any good way to f= igure it out or any known fix?

/Mikael

--_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7SOLNAMBX01nschm_-- --===============2601972336440302662== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2601972336440302662==-- From xen-api-bounces@lists.xen.org Tue Jan 01 21:06:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 01 Jan 2013 21:06:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tq92d-0003AB-Rv; Tue, 01 Jan 2013 21:06:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tq92c-0003A5-Nd for xen-api@lists.xen.org; Tue, 01 Jan 2013 21:06:30 +0000 Received: from [85.158.139.83:23790] by server-12.bemta-5.messagelabs.com id 3D/76-02275-5DF43E05; Tue, 01 Jan 2013 21:06:29 +0000 X-Env-Sender: mikael@servercentralen.se X-Msg-Ref: server-8.tower-182.messagelabs.com!1357074389!17103142!1 X-Originating-IP: [188.95.35.85] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29485 invoked from network); 1 Jan 2013 21:06:29 -0000 Received: from solna-gw2.centralcloud.net (HELO smtpedge.centralcloud.net) (188.95.35.85) by server-8.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 1 Jan 2013 21:06:29 -0000 Received: from SOLNA-MBX01.nschmc.local ([fe80::2498:f5a:2882:1d75]) by SOLNA-HUB01.nschmc.local ([fe80::d1e0:f192:d7:464a%11]) with mapi id 14.02.0318.004; Tue, 1 Jan 2013 22:09:33 +0100 From: Mikael Hugo To: "xen-api@lists.xen.org" Thread-Topic: Intel 82574L in XCP 1.6 and vlan Thread-Index: AQHN6GRLuLsyizZFEUC1uWXZ9gjHkw== Date: Tue, 1 Jan 2013 21:09:32 +0000 Message-ID: <23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7@SOLNA-MBX01.nschmc.local> Accept-Language: sv-SE, en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.5.121010 x-originating-ip: [192.168.68.2] MIME-Version: 1.0 Subject: [Xen-API] Intel 82574L in XCP 1.6 and vlan X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2601972336440302662==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2601972336440302662== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7SOLNAMBX01nschm_" --_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7SOLNAMBX01nschm_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi! I have issues with 82574L in XCP 1.6 - It works untagged but not with tagged vlans. I see Xenserver 6.1 has an updated driver kit for Intel and it feels like it must be a driver issue since I get zero traffic. Any good way to figure it out or any known fix? /Mikael --_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7SOLNAMBX01nschm_ Content-Type: text/html; charset="us-ascii" Content-ID: <8D4A8AACE1AF4E4891CE6802167AF22B@nschmc.local> Content-Transfer-Encoding: quoted-printable
Hi!

I have issues wit= h 82574L in XCP 1.6 - It works untagged but not with
tagged vlans.

I see Xenserver 6= .1 has an updated driver kit for Intel and it feels like
it must be a driv= er issue since I get zero traffic.

Any good way to f= igure it out or any known fix?

/Mikael

--_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7SOLNAMBX01nschm_-- --===============2601972336440302662== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2601972336440302662==-- From xen-api-bounces@lists.xen.org Wed Jan 02 04:00:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 04:00:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqFUd-0004eU-09; Wed, 02 Jan 2013 03:59:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqFUb-0004eP-Ov for xen-api@lists.xen.org; Wed, 02 Jan 2013 03:59:50 +0000 Received: from [193.109.254.147:53667] by server-9.bemta-14.messagelabs.com id 18/C3-24482-4B0B3E05; Wed, 02 Jan 2013 03:59:48 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1357099187!12053165!1 X-Originating-IP: [209.85.215.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25136 invoked from network); 2 Jan 2013 03:59:47 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jan 2013 03:59:47 -0000 Received: by mail-la0-f54.google.com with SMTP id fp12so5460414lab.27 for ; Tue, 01 Jan 2013 19:59:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=9lhqzSDp9c8+RZOpR1aNXrg1prhpEWW6iTlUwE6iUy8=; b=Tf6TKNv4kqor/vTTQdu4ziGPkP/HaxRBLqb1HORExUX1N6CqmShFGhm0Ecr6vwmLB2 N5hCSI1B+MePEun3yENw9j5XhlGph/O0ZnPPL4uxYEICAVOSLX5ZljcjoHbSNEjsivEf 8mgJ1QsHkUPmJKhtCZc8DF+82SyTgi0qW38J8gpzWA1eKuUNYKcWl4prvE6veof2ABiL C7K8bdVJiLgBOdiIfzbpABxRjupVwpduVjhtNp/p5gsIGMFotlzLGaWTo/Ebmoiu1cNb abSR3woNt3p0twzLcNqpZxb8VmPwgGBLkG0ZlqaWXkjgFQ9zgxH+smoMSDbSyS1Tuj3g Kbjw== X-Received: by 10.152.111.68 with SMTP id ig4mr43208494lab.50.1357099186861; Tue, 01 Jan 2013 19:59:46 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id s9sm15712802lbc.12.2013.01.01.19.59.46 (version=SSLv3 cipher=OTHER); Tue, 01 Jan 2013 19:59:46 -0800 (PST) Message-ID: <50E3B0B1.4050409@gmail.com> Date: Wed, 02 Jan 2013 07:59:45 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DC85CA.1020807@ondore.com> In-Reply-To: <50DC85CA.1020807@ondore.com> Subject: Re: [Xen-API] XCP 1.6 bonding, bond vs bridge X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org XCP by default use OpenVSwitch, which capable to provide bonding. bridge (xenbrX) is placed between bonding and virtual interfaces. On 27.12.2012 21:30, Alexandre Kouznetsov wrote: > Hello again. > > (this is a related to > http://lists.xen.org/archives/html/xen-api/2012-12/msg00147.html ) > > After I have create a test bond from XenCenter, I have noticed that > what was actually created on the host is not a "bond" (as described in > http://www.kernel.org/doc/Documentation/networking/bonding.txt ), but > a bridge. This is confusing, I was expecting something like a 802.3ad > interface, that would need cooperation from the the switch (group > ports into a LAG). > > I guess I'm missing something. Is there some layer behind this bridge, > that makes it act like a bond? Does it need any special configuration > at switch's side? > Why do they call "bond" a bridge, anyway? Surely there is a good > reason, but I'm curious which is. > > Greetings. > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 02 04:00:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 04:00:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqFUd-0004eU-09; Wed, 02 Jan 2013 03:59:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqFUb-0004eP-Ov for xen-api@lists.xen.org; Wed, 02 Jan 2013 03:59:50 +0000 Received: from [193.109.254.147:53667] by server-9.bemta-14.messagelabs.com id 18/C3-24482-4B0B3E05; Wed, 02 Jan 2013 03:59:48 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1357099187!12053165!1 X-Originating-IP: [209.85.215.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25136 invoked from network); 2 Jan 2013 03:59:47 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jan 2013 03:59:47 -0000 Received: by mail-la0-f54.google.com with SMTP id fp12so5460414lab.27 for ; Tue, 01 Jan 2013 19:59:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=9lhqzSDp9c8+RZOpR1aNXrg1prhpEWW6iTlUwE6iUy8=; b=Tf6TKNv4kqor/vTTQdu4ziGPkP/HaxRBLqb1HORExUX1N6CqmShFGhm0Ecr6vwmLB2 N5hCSI1B+MePEun3yENw9j5XhlGph/O0ZnPPL4uxYEICAVOSLX5ZljcjoHbSNEjsivEf 8mgJ1QsHkUPmJKhtCZc8DF+82SyTgi0qW38J8gpzWA1eKuUNYKcWl4prvE6veof2ABiL C7K8bdVJiLgBOdiIfzbpABxRjupVwpduVjhtNp/p5gsIGMFotlzLGaWTo/Ebmoiu1cNb abSR3woNt3p0twzLcNqpZxb8VmPwgGBLkG0ZlqaWXkjgFQ9zgxH+smoMSDbSyS1Tuj3g Kbjw== X-Received: by 10.152.111.68 with SMTP id ig4mr43208494lab.50.1357099186861; Tue, 01 Jan 2013 19:59:46 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id s9sm15712802lbc.12.2013.01.01.19.59.46 (version=SSLv3 cipher=OTHER); Tue, 01 Jan 2013 19:59:46 -0800 (PST) Message-ID: <50E3B0B1.4050409@gmail.com> Date: Wed, 02 Jan 2013 07:59:45 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DC85CA.1020807@ondore.com> In-Reply-To: <50DC85CA.1020807@ondore.com> Subject: Re: [Xen-API] XCP 1.6 bonding, bond vs bridge X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org XCP by default use OpenVSwitch, which capable to provide bonding. bridge (xenbrX) is placed between bonding and virtual interfaces. On 27.12.2012 21:30, Alexandre Kouznetsov wrote: > Hello again. > > (this is a related to > http://lists.xen.org/archives/html/xen-api/2012-12/msg00147.html ) > > After I have create a test bond from XenCenter, I have noticed that > what was actually created on the host is not a "bond" (as described in > http://www.kernel.org/doc/Documentation/networking/bonding.txt ), but > a bridge. This is confusing, I was expecting something like a 802.3ad > interface, that would need cooperation from the the switch (group > ports into a LAG). > > I guess I'm missing something. Is there some layer behind this bridge, > that makes it act like a bond? Does it need any special configuration > at switch's side? > Why do they call "bond" a bridge, anyway? Surely there is a good > reason, but I'm curious which is. > > Greetings. > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 02 04:04:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 04:04:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqFZC-0004ow-GA; Wed, 02 Jan 2013 04:04:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqFZB-0004oq-EQ for xen-api@lists.xen.org; Wed, 02 Jan 2013 04:04:33 +0000 Received: from [85.158.139.83:46276] by server-1.bemta-5.messagelabs.com id CF/82-12813-FC1B3E05; Wed, 02 Jan 2013 04:04:31 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357099470!24549811!1 X-Originating-IP: [209.85.215.53] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22363 invoked from network); 2 Jan 2013 04:04:30 -0000 Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com) (209.85.215.53) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jan 2013 04:04:30 -0000 Received: by mail-la0-f53.google.com with SMTP id fn20so5402288lab.40 for ; Tue, 01 Jan 2013 20:04:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=SO3RNKudbIaHwOI0FIJSGwXfYZMUre34fSf4OSx3j8k=; b=Rri8rxJiMdZBH0DdFPNuWA3BgIX5nFFcrBh+z9Rl4AFKizjdlgOtVF+bo0VlEfYzQG wflyWOWr/XCaatgh1t7RmLn+iz4YCvQlMmzm1oqahQeSHIffOzWvpmLKgOzVhIoxQYcq OxYePzTVdyK3kI2Rz8V8TseTSofEiB8Gmq31Wdmewo2TJ4nZGht+qFryJmK04gVReFbD fa+VkV1Gqnke8bx7vfswxnXr2GJbDf7lu0dxmDmt4Ot1Wm+V7fLonzMqL1XIBGoqe0py fFsdIQeU06Ppp6jrF1J9aQSoDJDlzFtw5dRrF41Ghm192m0EBaKk8kD40RFbo25YqApU aZaA== X-Received: by 10.112.16.69 with SMTP id e5mr18378629lbd.43.1357099470053; Tue, 01 Jan 2013 20:04:30 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id ee5sm15714701lbb.14.2013.01.01.20.04.29 (version=SSLv3 cipher=OTHER); Tue, 01 Jan 2013 20:04:29 -0800 (PST) Message-ID: <50E3B1CD.1080905@gmail.com> Date: Wed, 02 Jan 2013 08:04:29 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> In-Reply-To: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> Subject: Re: [Xen-API] Xen API connection with python and xml-rpc int limit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2695350700026210907==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2695350700026210907== Content-Type: multipart/alternative; boundary="------------070001090100070505090004" This is a multi-part message in MIME format. --------------070001090100070505090004 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Not sure what wrong, but we change VM memory limits over 4GiB with XenAPI without messing up with hacks... On 28.12.2012 14:08, Koldo Aingeru Marcos Fernández wrote: > Hello all, > > I'm trying to change the memory limits using the python implementation > of the xenapi and I'm having trouble because the value in the api is a > 64bit int and the xml-rpc specifies ints as 32 bit. So I'm getting > this error (both in MacOSX and CentOS): > > / File > "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", > line 710, in dump_int/ > / raise OverflowError, "int exceeds XML-RPC limits"/ > /OverflowError: int exceeds XML-RPC limits/ > > And this is the code in xmlrpclib.py: > > / def dump_int(self, value, write):/ > / # in case ints are > 32 bits/ > / if value > MAXINT or value < MININT:/ > / raise OverflowError, "int exceeds XML-RPC limits"/ > > Is there any workaround for this? I would like to avoid both doing a > ssh connection to the host or modifying xmlrpclib.py. > > Thanks! > > ======================================== > Koldo Aingeru Marcos Fdez. > Sarenet S.A. > Tel: 944209470 - Fax: 944209465 > Parque Tecnológico, Edificio 103 > 48170 Zamudio > Bizkaia > www.sarenet.es > ======================================== > > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------070001090100070505090004 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Not sure what wrong, but we change VM memory limits over 4GiB with XenAPI without messing up with hacks...


On 28.12.2012 14:08, Koldo Aingeru Marcos Fernández wrote:
Hello all,

I'm trying to change the memory limits using the python implementation of the xenapi and I'm having trouble because the value in the api is a 64bit int and the xml-rpc specifies ints as 32 bit.  So I'm getting this error (both in MacOSX and CentOS):

  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 710, in dump_int
    raise OverflowError, "int exceeds XML-RPC limits"
OverflowError: int exceeds XML-RPC limits

And this is the code in xmlrpclib.py:

    def dump_int(self, value, write):
        # in case ints are > 32 bits
        if value > MAXINT or value < MININT:
            raise OverflowError, "int exceeds XML-RPC limits"

 
Is there any workaround for this? I would like to avoid both doing a ssh connection to the host or modifying xmlrpclib.py.

Thanks!

========================================
Koldo Aingeru Marcos Fdez. 
Sarenet S.A.
Tel: 944209470 - Fax: 944209465
Parque Tecnológico, Edificio 103
48170 Zamudio
Bizkaia
========================================






_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------070001090100070505090004-- --===============2695350700026210907== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2695350700026210907==-- From xen-api-bounces@lists.xen.org Wed Jan 02 04:04:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 04:04:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqFZC-0004ow-GA; Wed, 02 Jan 2013 04:04:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqFZB-0004oq-EQ for xen-api@lists.xen.org; Wed, 02 Jan 2013 04:04:33 +0000 Received: from [85.158.139.83:46276] by server-1.bemta-5.messagelabs.com id CF/82-12813-FC1B3E05; Wed, 02 Jan 2013 04:04:31 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357099470!24549811!1 X-Originating-IP: [209.85.215.53] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22363 invoked from network); 2 Jan 2013 04:04:30 -0000 Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com) (209.85.215.53) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jan 2013 04:04:30 -0000 Received: by mail-la0-f53.google.com with SMTP id fn20so5402288lab.40 for ; Tue, 01 Jan 2013 20:04:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=SO3RNKudbIaHwOI0FIJSGwXfYZMUre34fSf4OSx3j8k=; b=Rri8rxJiMdZBH0DdFPNuWA3BgIX5nFFcrBh+z9Rl4AFKizjdlgOtVF+bo0VlEfYzQG wflyWOWr/XCaatgh1t7RmLn+iz4YCvQlMmzm1oqahQeSHIffOzWvpmLKgOzVhIoxQYcq OxYePzTVdyK3kI2Rz8V8TseTSofEiB8Gmq31Wdmewo2TJ4nZGht+qFryJmK04gVReFbD fa+VkV1Gqnke8bx7vfswxnXr2GJbDf7lu0dxmDmt4Ot1Wm+V7fLonzMqL1XIBGoqe0py fFsdIQeU06Ppp6jrF1J9aQSoDJDlzFtw5dRrF41Ghm192m0EBaKk8kD40RFbo25YqApU aZaA== X-Received: by 10.112.16.69 with SMTP id e5mr18378629lbd.43.1357099470053; Tue, 01 Jan 2013 20:04:30 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id ee5sm15714701lbb.14.2013.01.01.20.04.29 (version=SSLv3 cipher=OTHER); Tue, 01 Jan 2013 20:04:29 -0800 (PST) Message-ID: <50E3B1CD.1080905@gmail.com> Date: Wed, 02 Jan 2013 08:04:29 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> In-Reply-To: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> Subject: Re: [Xen-API] Xen API connection with python and xml-rpc int limit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2695350700026210907==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2695350700026210907== Content-Type: multipart/alternative; boundary="------------070001090100070505090004" This is a multi-part message in MIME format. --------------070001090100070505090004 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Not sure what wrong, but we change VM memory limits over 4GiB with XenAPI without messing up with hacks... On 28.12.2012 14:08, Koldo Aingeru Marcos Fernández wrote: > Hello all, > > I'm trying to change the memory limits using the python implementation > of the xenapi and I'm having trouble because the value in the api is a > 64bit int and the xml-rpc specifies ints as 32 bit. So I'm getting > this error (both in MacOSX and CentOS): > > / File > "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", > line 710, in dump_int/ > / raise OverflowError, "int exceeds XML-RPC limits"/ > /OverflowError: int exceeds XML-RPC limits/ > > And this is the code in xmlrpclib.py: > > / def dump_int(self, value, write):/ > / # in case ints are > 32 bits/ > / if value > MAXINT or value < MININT:/ > / raise OverflowError, "int exceeds XML-RPC limits"/ > > Is there any workaround for this? I would like to avoid both doing a > ssh connection to the host or modifying xmlrpclib.py. > > Thanks! > > ======================================== > Koldo Aingeru Marcos Fdez. > Sarenet S.A. > Tel: 944209470 - Fax: 944209465 > Parque Tecnológico, Edificio 103 > 48170 Zamudio > Bizkaia > www.sarenet.es > ======================================== > > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------070001090100070505090004 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Not sure what wrong, but we change VM memory limits over 4GiB with XenAPI without messing up with hacks...


On 28.12.2012 14:08, Koldo Aingeru Marcos Fernández wrote:
Hello all,

I'm trying to change the memory limits using the python implementation of the xenapi and I'm having trouble because the value in the api is a 64bit int and the xml-rpc specifies ints as 32 bit.  So I'm getting this error (both in MacOSX and CentOS):

  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 710, in dump_int
    raise OverflowError, "int exceeds XML-RPC limits"
OverflowError: int exceeds XML-RPC limits

And this is the code in xmlrpclib.py:

    def dump_int(self, value, write):
        # in case ints are > 32 bits
        if value > MAXINT or value < MININT:
            raise OverflowError, "int exceeds XML-RPC limits"

 
Is there any workaround for this? I would like to avoid both doing a ssh connection to the host or modifying xmlrpclib.py.

Thanks!

========================================
Koldo Aingeru Marcos Fdez. 
Sarenet S.A.
Tel: 944209470 - Fax: 944209465
Parque Tecnológico, Edificio 103
48170 Zamudio
Bizkaia
========================================






_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------070001090100070505090004-- --===============2695350700026210907== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2695350700026210907==-- From xen-api-bounces@lists.xen.org Wed Jan 02 07:26:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 07:26:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqIiZ-0006ie-Gc; Wed, 02 Jan 2013 07:26:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqIiY-0006iZ-7Q for xen-api@lists.xen.org; Wed, 02 Jan 2013 07:26:26 +0000 Received: from [85.158.139.83:7050] by server-6.bemta-5.messagelabs.com id 6B/3A-30498-121E3E05; Wed, 02 Jan 2013 07:26:25 +0000 X-Env-Sender: spahmatthew@gmail.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357111576!24561731!1 X-Originating-IP: [209.85.160.52] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2391 invoked from network); 2 Jan 2013 07:26:18 -0000 Received: from mail-pb0-f52.google.com (HELO mail-pb0-f52.google.com) (209.85.160.52) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jan 2013 07:26:18 -0000 Received: by mail-pb0-f52.google.com with SMTP id ro2so7662478pbb.11 for ; Tue, 01 Jan 2013 23:26:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=XiLRoGndmAc09KItixarymM5Ha8eDFDbrQIa+Jw1g4Y=; b=YJ0nDrnFCKe5/qGwKDs2bsTJk7u5oGr70+B09dEeH0dlU07Vt6ESHSR2GhPKDK3nO5 Pj61jAFruMYf64StxI0lEd0bokJT64eiUI8MZBcQJptEFUeefi0rap6TU+y2O1eCgOmW Dl4tvhD956QBnTywh1rsi63BfCZbJoT9HK0MQwK8ILz0/lTSZkwZHsmodTdcFFGkO5Ei EoONebZEA+LbGcmImW8iRJmaAhmBC0pimIPzatGkP6X1id4Ri4z0GGuhirh/9v/iuSVK QDIyR2tob2BaZTyKnlLjY1GYG+ADQ5oR85QMPR/52Y7nt3C0waS8ygmjmEeBgmMKXlfi 6MEA== MIME-Version: 1.0 Received: by 10.66.74.40 with SMTP id q8mr134618314pav.29.1357111576141; Tue, 01 Jan 2013 23:26:16 -0800 (PST) Received: by 10.68.153.161 with HTTP; Tue, 1 Jan 2013 23:26:15 -0800 (PST) Date: Tue, 1 Jan 2013 23:26:15 -0800 Message-ID: From: Matthew Spah To: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.6 BUG: locking-mode not working X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5572796944285582616==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5572796944285582616== Content-Type: multipart/alternative; boundary=f46d042f937c6a9df604d249297b --f46d042f937c6a9df604d249297b Content-Type: text/plain; charset=ISO-8859-1 https://github.com/xen-org/xen-api/pull/953 I tested this patch in my lab environment. It seems to have fixed the VIF level locking issues. Can anyone else confirm? Good job George Shuklin -- - Matthew Spah Computer Information Sciences Tutor for Everett Community College Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc Xenapi Admin Project Member http://xenapiadmin.com CompTIA Security+ Certified and Cisco CCNA Certified Arlington, WA Cell 425-319-8676 "And all we ever were Just zeroes and ones" - Trent Reznor "If you want to make enemies, try to change something." - Woodrow T. Wilson --f46d042f937c6a9df604d249297b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable https://github.com/= xen-org/xen-api/pull/953

I tested this patch in my l= ab environment. It seems to have fixed the VIF level locking issues. Can an= yone else confirm?

Good job=A0Georg= e Shuklin

--
- Matthew Spah
Computer= Information Sciences Tutor for Everett Community College
Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc
= Xena= pi Admin Project Member=A0http://xenapiadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlington, WA = Cell 425-319-8676

"And all we ever were
Just zeroes an= d ones"=A0- Trent Reznor


"If you want to make enemies, try to change s= omething." - Woodrow T. Wilson
--f46d042f937c6a9df604d249297b-- --===============5572796944285582616== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5572796944285582616==-- From xen-api-bounces@lists.xen.org Wed Jan 02 07:26:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 07:26:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqIiZ-0006ie-Gc; Wed, 02 Jan 2013 07:26:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqIiY-0006iZ-7Q for xen-api@lists.xen.org; Wed, 02 Jan 2013 07:26:26 +0000 Received: from [85.158.139.83:7050] by server-6.bemta-5.messagelabs.com id 6B/3A-30498-121E3E05; Wed, 02 Jan 2013 07:26:25 +0000 X-Env-Sender: spahmatthew@gmail.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357111576!24561731!1 X-Originating-IP: [209.85.160.52] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2391 invoked from network); 2 Jan 2013 07:26:18 -0000 Received: from mail-pb0-f52.google.com (HELO mail-pb0-f52.google.com) (209.85.160.52) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jan 2013 07:26:18 -0000 Received: by mail-pb0-f52.google.com with SMTP id ro2so7662478pbb.11 for ; Tue, 01 Jan 2013 23:26:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=XiLRoGndmAc09KItixarymM5Ha8eDFDbrQIa+Jw1g4Y=; b=YJ0nDrnFCKe5/qGwKDs2bsTJk7u5oGr70+B09dEeH0dlU07Vt6ESHSR2GhPKDK3nO5 Pj61jAFruMYf64StxI0lEd0bokJT64eiUI8MZBcQJptEFUeefi0rap6TU+y2O1eCgOmW Dl4tvhD956QBnTywh1rsi63BfCZbJoT9HK0MQwK8ILz0/lTSZkwZHsmodTdcFFGkO5Ei EoONebZEA+LbGcmImW8iRJmaAhmBC0pimIPzatGkP6X1id4Ri4z0GGuhirh/9v/iuSVK QDIyR2tob2BaZTyKnlLjY1GYG+ADQ5oR85QMPR/52Y7nt3C0waS8ygmjmEeBgmMKXlfi 6MEA== MIME-Version: 1.0 Received: by 10.66.74.40 with SMTP id q8mr134618314pav.29.1357111576141; Tue, 01 Jan 2013 23:26:16 -0800 (PST) Received: by 10.68.153.161 with HTTP; Tue, 1 Jan 2013 23:26:15 -0800 (PST) Date: Tue, 1 Jan 2013 23:26:15 -0800 Message-ID: From: Matthew Spah To: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.6 BUG: locking-mode not working X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5572796944285582616==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5572796944285582616== Content-Type: multipart/alternative; boundary=f46d042f937c6a9df604d249297b --f46d042f937c6a9df604d249297b Content-Type: text/plain; charset=ISO-8859-1 https://github.com/xen-org/xen-api/pull/953 I tested this patch in my lab environment. It seems to have fixed the VIF level locking issues. Can anyone else confirm? Good job George Shuklin -- - Matthew Spah Computer Information Sciences Tutor for Everett Community College Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc Xenapi Admin Project Member http://xenapiadmin.com CompTIA Security+ Certified and Cisco CCNA Certified Arlington, WA Cell 425-319-8676 "And all we ever were Just zeroes and ones" - Trent Reznor "If you want to make enemies, try to change something." - Woodrow T. Wilson --f46d042f937c6a9df604d249297b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable https://github.com/= xen-org/xen-api/pull/953

I tested this patch in my l= ab environment. It seems to have fixed the VIF level locking issues. Can an= yone else confirm?

Good job=A0Georg= e Shuklin

--
- Matthew Spah
Computer= Information Sciences Tutor for Everett Community College
Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc
= Xena= pi Admin Project Member=A0http://xenapiadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlington, WA = Cell 425-319-8676

"And all we ever were
Just zeroes an= d ones"=A0- Trent Reznor


"If you want to make enemies, try to change s= omething." - Woodrow T. Wilson
--f46d042f937c6a9df604d249297b-- --===============5572796944285582616== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5572796944285582616==-- From xen-api-bounces@lists.xen.org Wed Jan 02 10:27:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 10:27:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqLXH-00007X-2S; Wed, 02 Jan 2013 10:26:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqLXG-00007S-Cc for xen-api@lists.xensource.com; Wed, 02 Jan 2013 10:26:58 +0000 Received: from [85.158.139.211:28403] by server-4.bemta-5.messagelabs.com id 23/10-14693-17B04E05; Wed, 02 Jan 2013 10:26:57 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1357122416!22558854!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDEzOTMx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4341 invoked from network); 2 Jan 2013 10:26:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jan 2013 10:26:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,394,1355097600"; d="scan'208,217";a="410538" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 Jan 2013 10:26:56 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Wed, 2 Jan 2013 10:26:56 +0000 From: James Bulpin To: =?iso-8859-1?Q?Koldo_Aingeru_Marcos_Fern=E1ndez?= , "xen-api@lists.xensource.com" Date: Wed, 2 Jan 2013 10:27:24 +0000 Thread-Topic: [Xen-API] Xen API connection with python and xml-rpc int limit Thread-Index: Ac3k46+7itq9fNh1QG294D2KwHFZUgD7+EgQ Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E5B3634@LONPMAILBOX01.citrite.net> References: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> In-Reply-To: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] Xen API connection with python and xml-rpc int limit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5762931518100519428==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5762931518100519428== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_344C0F67BC927847A2C92F9EE358DB0E01224E5B3634LONPMAILBOX_" --_000_344C0F67BC927847A2C92F9EE358DB0E01224E5B3634LONPMAILBOX_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Try converting the value to a string and using this as the second argument = to VM.set_memory_static_max etc. Cheers, James From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of Koldo Aingeru Marcos Fern=E1ndez Sent: 28 December 2012 10:09 To: xen-api@lists.xensource.com Subject: [Xen-API] Xen API connection with python and xml-rpc int limit Hello all, I'm trying to change the memory limits using the python implementation of t= he xenapi and I'm having trouble because the value in the api is a 64bit in= t and the xml-rpc specifies ints as 32 bit. So I'm getting this error (bot= h in MacOSX and CentOS): File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python= 2.6/xmlrpclib.py", line 710, in dump_int raise OverflowError, "int exceeds XML-RPC limits" OverflowError: int exceeds XML-RPC limits And this is the code in xmlrpclib.py: def dump_int(self, value, write): # in case ints are > 32 bits if value > MAXINT or value < MININT: raise OverflowError, "int exceeds XML-RPC limits" Is there any workaround for this? I would like to avoid both doing a ssh co= nnection to the host or modifying xmlrpclib.py. Thanks! =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Koldo Aingeru Marcos Fdez. Sarenet S.A. Tel: 944209470 - Fax: 944209465 Parque Tecnol=F3gico, Edificio 103 48170 Zamudio Bizkaia www.sarenet.es =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --_000_344C0F67BC927847A2C92F9EE358DB0E01224E5B3634LONPMAILBOX_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Try conve= rting the value to a string and using this as the second argument to VM.set= _memory_static_max etc.

 

Cheers,

James

 

From: xen-api-bounces@lists.xen.org [m= ailto:xen-api-bounces@lists.xen.org] On Behalf Of Koldo Aingeru Marc= os Fern=E1ndez
Sent: 28 December 2012 10:09
To: xen-api= @lists.xensource.com
Subject: [Xen-API] Xen API connection with p= ython and xml-rpc int limit

 

Hello all,

<= div>

 

I'm trying to change the memory limits using the python implementation o= f the xenapi and I'm having trouble because the value in the api is a 64bit= int and the xml-rpc specifies ints as 32 bit.  So I'm getting this er= ror (both in MacOSX and CentOS):

 

  File &qu= ot;/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/x= mlrpclib.py", line 710, in dump_int

    raise OverflowError, "int exceeds XML= -RPC limits"

Over= flowError: int exceeds XML-RPC limits

 

And this = is the code in xmlrpclib.py:

=  

    = def dump_int(self, value, write):

        # in case ints are > 32 bits=

      &nbs= p; if value > MAXINT or value < MININT:

=

            raise Ove= rflowError, "int exceeds XML-RPC limits"

=

 

 

Is there any= workaround for this? I would like to avoid both doing a ssh connection to = the host or modifying xmlrpclib.py.

 

Thanks!

 

=

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D

Koldo Ainger= u Marcos Fdez. 

<= span style=3D'font-size:9.0pt;font-family:"Helvetica","sans-serif";color:bl= ack'>Sarenet S.A.

Tel: 944209470 - Fax: 944209465

Parque Tecnol=F3gico, Edificio 103

=

48170 Zamudio

Bizkaia

www.sarenet.e= s

=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D



 

 

= --_000_344C0F67BC927847A2C92F9EE358DB0E01224E5B3634LONPMAILBOX_-- --===============5762931518100519428== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5762931518100519428==-- From xen-api-bounces@lists.xen.org Wed Jan 02 10:27:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 10:27:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqLXH-00007X-2S; Wed, 02 Jan 2013 10:26:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqLXG-00007S-Cc for xen-api@lists.xensource.com; Wed, 02 Jan 2013 10:26:58 +0000 Received: from [85.158.139.211:28403] by server-4.bemta-5.messagelabs.com id 23/10-14693-17B04E05; Wed, 02 Jan 2013 10:26:57 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1357122416!22558854!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDEzOTMx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4341 invoked from network); 2 Jan 2013 10:26:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jan 2013 10:26:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,394,1355097600"; d="scan'208,217";a="410538" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 Jan 2013 10:26:56 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Wed, 2 Jan 2013 10:26:56 +0000 From: James Bulpin To: =?iso-8859-1?Q?Koldo_Aingeru_Marcos_Fern=E1ndez?= , "xen-api@lists.xensource.com" Date: Wed, 2 Jan 2013 10:27:24 +0000 Thread-Topic: [Xen-API] Xen API connection with python and xml-rpc int limit Thread-Index: Ac3k46+7itq9fNh1QG294D2KwHFZUgD7+EgQ Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E5B3634@LONPMAILBOX01.citrite.net> References: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> In-Reply-To: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] Xen API connection with python and xml-rpc int limit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5762931518100519428==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5762931518100519428== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_344C0F67BC927847A2C92F9EE358DB0E01224E5B3634LONPMAILBOX_" --_000_344C0F67BC927847A2C92F9EE358DB0E01224E5B3634LONPMAILBOX_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Try converting the value to a string and using this as the second argument = to VM.set_memory_static_max etc. Cheers, James From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of Koldo Aingeru Marcos Fern=E1ndez Sent: 28 December 2012 10:09 To: xen-api@lists.xensource.com Subject: [Xen-API] Xen API connection with python and xml-rpc int limit Hello all, I'm trying to change the memory limits using the python implementation of t= he xenapi and I'm having trouble because the value in the api is a 64bit in= t and the xml-rpc specifies ints as 32 bit. So I'm getting this error (bot= h in MacOSX and CentOS): File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python= 2.6/xmlrpclib.py", line 710, in dump_int raise OverflowError, "int exceeds XML-RPC limits" OverflowError: int exceeds XML-RPC limits And this is the code in xmlrpclib.py: def dump_int(self, value, write): # in case ints are > 32 bits if value > MAXINT or value < MININT: raise OverflowError, "int exceeds XML-RPC limits" Is there any workaround for this? I would like to avoid both doing a ssh co= nnection to the host or modifying xmlrpclib.py. Thanks! =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Koldo Aingeru Marcos Fdez. Sarenet S.A. Tel: 944209470 - Fax: 944209465 Parque Tecnol=F3gico, Edificio 103 48170 Zamudio Bizkaia www.sarenet.es =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --_000_344C0F67BC927847A2C92F9EE358DB0E01224E5B3634LONPMAILBOX_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Try conve= rting the value to a string and using this as the second argument to VM.set= _memory_static_max etc.

 

Cheers,

James

 

From: xen-api-bounces@lists.xen.org [m= ailto:xen-api-bounces@lists.xen.org] On Behalf Of Koldo Aingeru Marc= os Fern=E1ndez
Sent: 28 December 2012 10:09
To: xen-api= @lists.xensource.com
Subject: [Xen-API] Xen API connection with p= ython and xml-rpc int limit

 

Hello all,

<= div>

 

I'm trying to change the memory limits using the python implementation o= f the xenapi and I'm having trouble because the value in the api is a 64bit= int and the xml-rpc specifies ints as 32 bit.  So I'm getting this er= ror (both in MacOSX and CentOS):

 

  File &qu= ot;/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/x= mlrpclib.py", line 710, in dump_int

    raise OverflowError, "int exceeds XML= -RPC limits"

Over= flowError: int exceeds XML-RPC limits

 

And this = is the code in xmlrpclib.py:

=  

    = def dump_int(self, value, write):

        # in case ints are > 32 bits=

      &nbs= p; if value > MAXINT or value < MININT:

=

            raise Ove= rflowError, "int exceeds XML-RPC limits"

=

 

 

Is there any= workaround for this? I would like to avoid both doing a ssh connection to = the host or modifying xmlrpclib.py.

 

Thanks!

 

=

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D

Koldo Ainger= u Marcos Fdez. 

<= span style=3D'font-size:9.0pt;font-family:"Helvetica","sans-serif";color:bl= ack'>Sarenet S.A.

Tel: 944209470 - Fax: 944209465

Parque Tecnol=F3gico, Edificio 103

=

48170 Zamudio

Bizkaia

www.sarenet.e= s

=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D



 

 

= --_000_344C0F67BC927847A2C92F9EE358DB0E01224E5B3634LONPMAILBOX_-- --===============5762931518100519428== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5762931518100519428==-- From xen-api-bounces@lists.xen.org Wed Jan 02 11:10:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 11:10:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqMDU-0000gR-ML; Wed, 02 Jan 2013 11:10:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqMDT-0000gM-LF for xen-api@lists.xen.org; Wed, 02 Jan 2013 11:10:35 +0000 Received: from [85.158.139.83:46161] by server-9.bemta-5.messagelabs.com id AE/CC-10690-AA514E05; Wed, 02 Jan 2013 11:10:34 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-13.tower-182.messagelabs.com!1357125029!31405803!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0NTcyODI=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24388 invoked from network); 2 Jan 2013 11:10:30 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-13.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jan 2013 11:10:30 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 436C42992; Wed, 2 Jan 2013 13:10:29 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 117AB20068; Wed, 2 Jan 2013 13:10:29 +0200 (EET) Date: Wed, 2 Jan 2013 13:10:28 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: xen-api@lists.xen.org Message-ID: <20130102111028.GV8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Subject: [Xen-API] XCP 1.6 kernel patchqueue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, First of all Happy New Year to everyone :) I was looking for source trees and patch queues for XCP 1.6 on xenbits but couldn't find them.. so this url probably: http://xenbits.xen.org/hg/XCP/1.6 XCP 1.5 and previous versions are there: http://xenbits.xen.org/hg/XCP/1.5 http://xenbits.xen.org/hg/XCP/1.1 Thanks, -- Pasi _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 02 11:10:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 11:10:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqMDU-0000gR-ML; Wed, 02 Jan 2013 11:10:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqMDT-0000gM-LF for xen-api@lists.xen.org; Wed, 02 Jan 2013 11:10:35 +0000 Received: from [85.158.139.83:46161] by server-9.bemta-5.messagelabs.com id AE/CC-10690-AA514E05; Wed, 02 Jan 2013 11:10:34 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-13.tower-182.messagelabs.com!1357125029!31405803!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0NTcyODI=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24388 invoked from network); 2 Jan 2013 11:10:30 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-13.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jan 2013 11:10:30 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 436C42992; Wed, 2 Jan 2013 13:10:29 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 117AB20068; Wed, 2 Jan 2013 13:10:29 +0200 (EET) Date: Wed, 2 Jan 2013 13:10:28 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: xen-api@lists.xen.org Message-ID: <20130102111028.GV8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Subject: [Xen-API] XCP 1.6 kernel patchqueue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, First of all Happy New Year to everyone :) I was looking for source trees and patch queues for XCP 1.6 on xenbits but couldn't find them.. so this url probably: http://xenbits.xen.org/hg/XCP/1.6 XCP 1.5 and previous versions are there: http://xenbits.xen.org/hg/XCP/1.5 http://xenbits.xen.org/hg/XCP/1.1 Thanks, -- Pasi _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 02 17:15:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 17:15:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqRud-0008WU-B3; Wed, 02 Jan 2013 17:15:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqRub-0008WG-RO for xen-api@lists.xen.org; Wed, 02 Jan 2013 17:15:30 +0000 Received: from [85.158.139.83:30289] by server-1.bemta-5.messagelabs.com id 38/48-12813-13B64E05; Wed, 02 Jan 2013 17:15:29 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1357146926!17218064!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22726 invoked from network); 2 Jan 2013 17:15:27 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-8.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jan 2013 17:15:27 -0000 Received: from [187.233.68.172] (port=56791 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqRuW-0003tN-RF for xen-api@lists.xen.org; Wed, 02 Jan 2013 11:15:25 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id D98A1A209 for ; Wed, 2 Jan 2013 11:12:42 -0600 (CST) Message-ID: <50E46B2B.6050508@ondore.com> Date: Wed, 02 Jan 2013 11:15:23 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50DDD86C.7000209@ondore.com> <602C5EB92F9AFB4D89D11B9F5B7F13552009CC30@SM-DAG151.softlayer.local> In-Reply-To: <602C5EB92F9AFB4D89D11B9F5B7F13552009CC30@SM-DAG151.softlayer.local> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. At first I thought that "destination-sr-uuid" parameter name = tab-completion was some shell's issue, but "xe help vm-migrate" is quite = specific about that option, so I don't think it was not supposed to be = available in XCP 1.6. In any case, thank you for reference. About "vdi:", the result is similar: [root@xcp47 ~]# xe vm-migrate vm=3DDebianStorage host=3Dxcp48 \ vdi:49e9aaa9-e86a-4c69-b4b5-8ed9cfd11470=3D49e9aaa9-e86a-4c69-\ b4b5-8ed9cfd11470 Error: Unknown field 'vdi:49e9aaa9-e86a-4c69-b4b5-8ed9cfd11470' (I expect it to keep the same UUID) I'm wondering, if I'm missing environment variables or something is = wrong with xe's parameters parser? Installation was done via PXE as described at = http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_= boot_install Thank you. El 30/12/12 20:01, Joseph Hom escribi=F3: > Try using: > > vdi > parameters take the form 'vdi:=3D' > > At least for XenServer 6.1, destination-sr-uuid is an invalid option and = was supposed to have been removed on release, but wasn't. > ________________________________________ > From: xen-api-bounces@lists.xen.org [xen-api-bounces@lists.xen.org] on be= half of Alexandre Kouznetsov [alk@ondore.com] > Sent: Friday, December 28, 2012 11:35 AM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks be= tween local SRs > > Hello. > > I have 2-nodes (xcp47 and xcp48 in my setup) XCP 1.6 pool, using only > local storage for VM's, and trying to move a VM "DebianStorage" from > xcp47 to xcp48. The nodes are physically identical, configured in the > same way and belongs to the same pool. > > I'm trying to use xe vm-migrate, but unsuccessful: > [root@xcp47 ~]# xe vm-migrate vm=3DDebianStorage host=3Dxcp48 \ > destination-sr-uuid=3Df778b43b-4263-7883-e626-09997d711d60 > Error: Unknown field 'destination-sr-uuid' > > For reference, the parameter "destination-sr-uuid=3D" expands using > while I type it, it's value does not. I have checked the uuid of the SR > on destination host, it is correct: > [root@xcp47 ~]# xe sr-list host=3Dxcp48 content-type=3Duser > uuid ( RO) : f778b43b-4263-7883-e626-09997d711d60 > name-label ( RW): Local storage > name-description ( RW): > host ( RO): xcp48 > type ( RO): lvm > content-type ( RO): user > > I must add, that XenCenter does not allows me to move the VM > "DebianStorage" to the other storage, the menu option is grayed with the > legend "Cannot see required storage". Also, can't move the Virtual Disk, > even if I halt the machine and detach the Virtual Disk. > > If I just omit "destination-sr-uuid=3D", XCP complains about power state > if the machine is halted, and if the machine is running it complains > about "access to an SR needed by the VM". > > As I understand http://wiki.xen.org/wiki/Storage_XenMotion , it's > supposed to be possible, but since I'm new in XCP I can't tell if it's a > bug or I'm doing it wrong. My goal is to move the VM from one host to > another, using only local storage in both of them. Would be great to do > it online, but offline would work also. > > Thank you. > > -- > Alexandre Kouznetsov > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 02 17:15:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 17:15:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqRud-0008WU-B3; Wed, 02 Jan 2013 17:15:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqRub-0008WG-RO for xen-api@lists.xen.org; Wed, 02 Jan 2013 17:15:30 +0000 Received: from [85.158.139.83:30289] by server-1.bemta-5.messagelabs.com id 38/48-12813-13B64E05; Wed, 02 Jan 2013 17:15:29 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1357146926!17218064!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22726 invoked from network); 2 Jan 2013 17:15:27 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-8.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jan 2013 17:15:27 -0000 Received: from [187.233.68.172] (port=56791 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqRuW-0003tN-RF for xen-api@lists.xen.org; Wed, 02 Jan 2013 11:15:25 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id D98A1A209 for ; Wed, 2 Jan 2013 11:12:42 -0600 (CST) Message-ID: <50E46B2B.6050508@ondore.com> Date: Wed, 02 Jan 2013 11:15:23 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50DDD86C.7000209@ondore.com> <602C5EB92F9AFB4D89D11B9F5B7F13552009CC30@SM-DAG151.softlayer.local> In-Reply-To: <602C5EB92F9AFB4D89D11B9F5B7F13552009CC30@SM-DAG151.softlayer.local> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. At first I thought that "destination-sr-uuid" parameter name = tab-completion was some shell's issue, but "xe help vm-migrate" is quite = specific about that option, so I don't think it was not supposed to be = available in XCP 1.6. In any case, thank you for reference. About "vdi:", the result is similar: [root@xcp47 ~]# xe vm-migrate vm=3DDebianStorage host=3Dxcp48 \ vdi:49e9aaa9-e86a-4c69-b4b5-8ed9cfd11470=3D49e9aaa9-e86a-4c69-\ b4b5-8ed9cfd11470 Error: Unknown field 'vdi:49e9aaa9-e86a-4c69-b4b5-8ed9cfd11470' (I expect it to keep the same UUID) I'm wondering, if I'm missing environment variables or something is = wrong with xe's parameters parser? Installation was done via PXE as described at = http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_= boot_install Thank you. El 30/12/12 20:01, Joseph Hom escribi=F3: > Try using: > > vdi > parameters take the form 'vdi:=3D' > > At least for XenServer 6.1, destination-sr-uuid is an invalid option and = was supposed to have been removed on release, but wasn't. > ________________________________________ > From: xen-api-bounces@lists.xen.org [xen-api-bounces@lists.xen.org] on be= half of Alexandre Kouznetsov [alk@ondore.com] > Sent: Friday, December 28, 2012 11:35 AM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks be= tween local SRs > > Hello. > > I have 2-nodes (xcp47 and xcp48 in my setup) XCP 1.6 pool, using only > local storage for VM's, and trying to move a VM "DebianStorage" from > xcp47 to xcp48. The nodes are physically identical, configured in the > same way and belongs to the same pool. > > I'm trying to use xe vm-migrate, but unsuccessful: > [root@xcp47 ~]# xe vm-migrate vm=3DDebianStorage host=3Dxcp48 \ > destination-sr-uuid=3Df778b43b-4263-7883-e626-09997d711d60 > Error: Unknown field 'destination-sr-uuid' > > For reference, the parameter "destination-sr-uuid=3D" expands using > while I type it, it's value does not. I have checked the uuid of the SR > on destination host, it is correct: > [root@xcp47 ~]# xe sr-list host=3Dxcp48 content-type=3Duser > uuid ( RO) : f778b43b-4263-7883-e626-09997d711d60 > name-label ( RW): Local storage > name-description ( RW): > host ( RO): xcp48 > type ( RO): lvm > content-type ( RO): user > > I must add, that XenCenter does not allows me to move the VM > "DebianStorage" to the other storage, the menu option is grayed with the > legend "Cannot see required storage". Also, can't move the Virtual Disk, > even if I halt the machine and detach the Virtual Disk. > > If I just omit "destination-sr-uuid=3D", XCP complains about power state > if the machine is halted, and if the machine is running it complains > about "access to an SR needed by the VM". > > As I understand http://wiki.xen.org/wiki/Storage_XenMotion , it's > supposed to be possible, but since I'm new in XCP I can't tell if it's a > bug or I'm doing it wrong. My goal is to move the VM from one host to > another, using only local storage in both of them. Would be great to do > it online, but offline would work also. > > Thank you. > > -- > Alexandre Kouznetsov > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 02 17:19:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 17:19:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqRyQ-0000Lv-PE; Wed, 02 Jan 2013 17:19:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqRyP-0000Lq-Qv for xen-api@lists.xen.org; Wed, 02 Jan 2013 17:19:25 +0000 Received: from [193.109.254.147:59517] by server-13.bemta-14.messagelabs.com id D9/42-01725-C1C64E05; Wed, 02 Jan 2013 17:19:24 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1357147163!3405046!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24835 invoked from network); 2 Jan 2013 17:19:24 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-10.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jan 2013 17:19:24 -0000 Received: from [187.233.68.172] (port=43647 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqRyN-0004DS-5l for xen-api@lists.xen.org; Wed, 02 Jan 2013 11:19:23 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 261E7A209 for ; Wed, 2 Jan 2013 11:16:41 -0600 (CST) Message-ID: <50E46C1A.4010804@ondore.com> Date: Wed, 02 Jan 2013 11:19:22 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DC85CA.1020807@ondore.com> <50E3B0B1.4050409@gmail.com> In-Reply-To: <50E3B0B1.4050409@gmail.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 bonding, bond vs bridge X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org El 01/01/13 21:59, George Shuklin escribi=F3: > XCP by default use OpenVSwitch, which capable to provide bonding. > > bridge (xenbrX) is placed between bonding and virtual interfaces. Makes sense. Thank you. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 02 17:19:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 17:19:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqRyQ-0000Lv-PE; Wed, 02 Jan 2013 17:19:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqRyP-0000Lq-Qv for xen-api@lists.xen.org; Wed, 02 Jan 2013 17:19:25 +0000 Received: from [193.109.254.147:59517] by server-13.bemta-14.messagelabs.com id D9/42-01725-C1C64E05; Wed, 02 Jan 2013 17:19:24 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1357147163!3405046!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24835 invoked from network); 2 Jan 2013 17:19:24 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-10.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jan 2013 17:19:24 -0000 Received: from [187.233.68.172] (port=43647 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqRyN-0004DS-5l for xen-api@lists.xen.org; Wed, 02 Jan 2013 11:19:23 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 261E7A209 for ; Wed, 2 Jan 2013 11:16:41 -0600 (CST) Message-ID: <50E46C1A.4010804@ondore.com> Date: Wed, 02 Jan 2013 11:19:22 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DC85CA.1020807@ondore.com> <50E3B0B1.4050409@gmail.com> In-Reply-To: <50E3B0B1.4050409@gmail.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 bonding, bond vs bridge X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org El 01/01/13 21:59, George Shuklin escribi=F3: > XCP by default use OpenVSwitch, which capable to provide bonding. > > bridge (xenbrX) is placed between bonding and virtual interfaces. Makes sense. Thank you. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 02 20:36:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 20:36:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqV2e-0004A3-40; Wed, 02 Jan 2013 20:36:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqV2c-00049p-EQ for xen-api@lists.xen.org; Wed, 02 Jan 2013 20:35:58 +0000 Received: from [85.158.137.99:56271] by server-5.bemta-3.messagelabs.com id 70/09-04992-D2A94E05; Wed, 02 Jan 2013 20:35:57 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1357158949!17347536!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28846 invoked from network); 2 Jan 2013 20:35:50 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-4.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jan 2013 20:35:50 -0000 Received: from [187.233.68.172] (port=37240 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqV2S-0002Ay-HY for xen-api@lists.xen.org; Wed, 02 Jan 2013 14:35:48 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 1D9F5A209 for ; Wed, 2 Jan 2013 14:33:06 -0600 (CST) Message-ID: <50E49A23.7060804@ondore.com> Date: Wed, 02 Jan 2013 14:35:47 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DDD86C.7000209@ondore.com> In-Reply-To: <50DDD86C.7000209@ondore.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. I have made more tests and got a successful migration using Storage = XenMotion. It happened only after I have removed the destination XCP = host from the actual pool, and moved it to a new one. It seems like "destination-sr-uuid=3D" option is recognized correctly only = when a "remote-master=3D" and other connection details are specified. The = neighbor thread = http://lists.xen.org/archives/html/xen-api/2012-12/msg00162.html was = helpful. Yes, they fly between pools like magic. The option = "live=3D" does not make any visible difference: a Debian VM = with default 8GB hdd and no activity pauses for around 2 seconds and my = shell connection to it is not lost, in both cases, "live=3Dfalse" and = "live=3Dtrue". Still not clear how to migrate VM's in the following cases: - When VM is not online (vm-migrate insists it should be "running"). - When origin and destination hosts are within the same pool. The first operation seems to be achievable by detaching the storage, = changing the "home host" for the VM, copying the storage to the = destination host's SR (xenapi can do?), attach the storage back to the = VM on the new host. I hoped this could be done by a single instruction, = seems much less complicated operation than a online migration. About the second one, I have no clue. vm-motion keeps complaining about = "You attempted to run a VM on a host which doesn't have access to an SR = needed by the VM". Am I supposed to always migrate the VM's to a = temporal host, and then to the real destination? Thank you. El 28/12/12 11:35, Alexandre Kouznetsov escribi=F3: > Hello. > > I have 2-nodes (xcp47 and xcp48 in my setup) XCP 1.6 pool, using only > local storage for VM's, and trying to move a VM "DebianStorage" from > xcp47 to xcp48. The nodes are physically identical, configured in the > same way and belongs to the same pool. > > I'm trying to use xe vm-migrate, but unsuccessful: > [root@xcp47 ~]# xe vm-migrate vm=3DDebianStorage host=3Dxcp48 \ > destination-sr-uuid=3Df778b43b-4263-7883-e626-09997d711d60 > Error: Unknown field 'destination-sr-uuid' > > For reference, the parameter "destination-sr-uuid=3D" expands using > while I type it, it's value does not. I have checked the uuid of the SR > on destination host, it is correct: > [root@xcp47 ~]# xe sr-list host=3Dxcp48 content-type=3Duser > uuid ( RO) : f778b43b-4263-7883-e626-09997d711d60 > name-label ( RW): Local storage > name-description ( RW): > host ( RO): xcp48 > type ( RO): lvm > content-type ( RO): user > > I must add, that XenCenter does not allows me to move the VM > "DebianStorage" to the other storage, the menu option is grayed with the > legend "Cannot see required storage". Also, can't move the Virtual Disk, > even if I halt the machine and detach the Virtual Disk. > > If I just omit "destination-sr-uuid=3D", XCP complains about power state > if the machine is halted, and if the machine is running it complains > about "access to an SR needed by the VM". > > As I understand http://wiki.xen.org/wiki/Storage_XenMotion , it's > supposed to be possible, but since I'm new in XCP I can't tell if it's a > bug or I'm doing it wrong. My goal is to move the VM from one host to > another, using only local storage in both of them. Would be great to do > it online, but offline would work also. > > Thank you. > -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 02 20:36:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 02 Jan 2013 20:36:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqV2e-0004A3-40; Wed, 02 Jan 2013 20:36:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqV2c-00049p-EQ for xen-api@lists.xen.org; Wed, 02 Jan 2013 20:35:58 +0000 Received: from [85.158.137.99:56271] by server-5.bemta-3.messagelabs.com id 70/09-04992-D2A94E05; Wed, 02 Jan 2013 20:35:57 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1357158949!17347536!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28846 invoked from network); 2 Jan 2013 20:35:50 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-4.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jan 2013 20:35:50 -0000 Received: from [187.233.68.172] (port=37240 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqV2S-0002Ay-HY for xen-api@lists.xen.org; Wed, 02 Jan 2013 14:35:48 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 1D9F5A209 for ; Wed, 2 Jan 2013 14:33:06 -0600 (CST) Message-ID: <50E49A23.7060804@ondore.com> Date: Wed, 02 Jan 2013 14:35:47 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DDD86C.7000209@ondore.com> In-Reply-To: <50DDD86C.7000209@ondore.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. I have made more tests and got a successful migration using Storage = XenMotion. It happened only after I have removed the destination XCP = host from the actual pool, and moved it to a new one. It seems like "destination-sr-uuid=3D" option is recognized correctly only = when a "remote-master=3D" and other connection details are specified. The = neighbor thread = http://lists.xen.org/archives/html/xen-api/2012-12/msg00162.html was = helpful. Yes, they fly between pools like magic. The option = "live=3D" does not make any visible difference: a Debian VM = with default 8GB hdd and no activity pauses for around 2 seconds and my = shell connection to it is not lost, in both cases, "live=3Dfalse" and = "live=3Dtrue". Still not clear how to migrate VM's in the following cases: - When VM is not online (vm-migrate insists it should be "running"). - When origin and destination hosts are within the same pool. The first operation seems to be achievable by detaching the storage, = changing the "home host" for the VM, copying the storage to the = destination host's SR (xenapi can do?), attach the storage back to the = VM on the new host. I hoped this could be done by a single instruction, = seems much less complicated operation than a online migration. About the second one, I have no clue. vm-motion keeps complaining about = "You attempted to run a VM on a host which doesn't have access to an SR = needed by the VM". Am I supposed to always migrate the VM's to a = temporal host, and then to the real destination? Thank you. El 28/12/12 11:35, Alexandre Kouznetsov escribi=F3: > Hello. > > I have 2-nodes (xcp47 and xcp48 in my setup) XCP 1.6 pool, using only > local storage for VM's, and trying to move a VM "DebianStorage" from > xcp47 to xcp48. The nodes are physically identical, configured in the > same way and belongs to the same pool. > > I'm trying to use xe vm-migrate, but unsuccessful: > [root@xcp47 ~]# xe vm-migrate vm=3DDebianStorage host=3Dxcp48 \ > destination-sr-uuid=3Df778b43b-4263-7883-e626-09997d711d60 > Error: Unknown field 'destination-sr-uuid' > > For reference, the parameter "destination-sr-uuid=3D" expands using > while I type it, it's value does not. I have checked the uuid of the SR > on destination host, it is correct: > [root@xcp47 ~]# xe sr-list host=3Dxcp48 content-type=3Duser > uuid ( RO) : f778b43b-4263-7883-e626-09997d711d60 > name-label ( RW): Local storage > name-description ( RW): > host ( RO): xcp48 > type ( RO): lvm > content-type ( RO): user > > I must add, that XenCenter does not allows me to move the VM > "DebianStorage" to the other storage, the menu option is grayed with the > legend "Cannot see required storage". Also, can't move the Virtual Disk, > even if I halt the machine and detach the Virtual Disk. > > If I just omit "destination-sr-uuid=3D", XCP complains about power state > if the machine is halted, and if the machine is running it complains > about "access to an SR needed by the VM". > > As I understand http://wiki.xen.org/wiki/Storage_XenMotion , it's > supposed to be possible, but since I'm new in XCP I can't tell if it's a > bug or I'm doing it wrong. My goal is to move the VM from one host to > another, using only local storage in both of them. Would be great to do > it online, but offline would work also. > > Thank you. > -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 03:19:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 03:19:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqbL8-0006Nk-RH; Thu, 03 Jan 2013 03:19:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqbL6-0006Nf-QP for xen-api@lists.xen.org; Thu, 03 Jan 2013 03:19:29 +0000 Received: from [85.158.138.51:45068] by server-11.bemta-3.messagelabs.com id E3/2F-13335-FB8F4E05; Thu, 03 Jan 2013 03:19:27 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1357183166!23178727!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26396 invoked from network); 3 Jan 2013 03:19:27 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 03:19:27 -0000 Received: by mail-la0-f48.google.com with SMTP id ej20so7237300lab.35 for ; Wed, 02 Jan 2013 19:19:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=hoyHDTU/oJprPmbp+xQ+dlwy9bPnO5Dm+2LxpKt+2Lg=; b=gKn3uXMxky9HEVk2YgzuJvXZ0RDXpJmnNmTnrHsO2HBjCyHJ01gqMcI7zdQrEuMKhb RSfv6bVzzvT99saEZr738WhTCShwy5/NYg2eepsjBrYToVDqI6JZk+bX3BL7LbZTw4cj 67vQ268CwNGm9iV4U512l/yOK9J7C9jtGfMKMoMEsBayPzEMLLErsc4uTgZv82klNg8o MrUTGasbZ4s4G/OXOLaCSwFb0j79+evfiuMb9P7+zCjjWuFz/18vArN6Dv4mj4OzSS5W OVSZ6OdKTeb6fOt/fjNsCtpt4sWgrNjaQyvzgrNWE5uRG+/u+tBUN1itjCasg8vXyzey Joug== X-Received: by 10.152.125.7 with SMTP id mm7mr46055089lab.2.1357183165133; Wed, 02 Jan 2013 19:19:25 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id ja10sm17949867lab.6.2013.01.02.19.19.23 (version=SSLv3 cipher=OTHER); Wed, 02 Jan 2013 19:19:24 -0800 (PST) Message-ID: <50E4F8BB.9070004@gmail.com> Date: Thu, 03 Jan 2013 07:19:23 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> In-Reply-To: <50E49A23.7060804@ondore.com> Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 03.01.2013 00:35, Alexandre Kouznetsov wrote: > Hello. > > I have made more tests and got a successful migration using Storage > XenMotion. It happened only after I have removed the destination XCP > host from the actual pool, and moved it to a new one. > > It seems like "destination-sr-uuid=" option is recognized correctly > only when a "remote-master=" and other connection details are > specified. The neighbor thread > http://lists.xen.org/archives/html/xen-api/2012-12/msg00162.html was > helpful. Yes, they fly between pools like magic. The option > "live=" does not make any visible difference: a Debian VM > with default 8GB hdd and no activity pauses for around 2 seconds and > my shell connection to it is not lost, in both cases, "live=false" and > "live=true". > live migration performs set of iterations over VM memory (you can see details in /tmp/xenguest.log on source host), live=false performs 'pause and copy' mode. They are almost the same for idle machines, but make a huge difference for heavy-loaded servers, which change lot of memory every second. (F.e. heavy loaded erlang application with work heap about 10GiB: it live migration performs all 32 iterations and still forced to make 'pause and copy' at final round with large memory delta). > Still not clear how to migrate VM's in the following cases: > - When VM is not online (vm-migrate insists it should be "running"). > - When origin and destination hosts are within the same pool. > offline croos-pool migration is not supported, AFAIK. Sad, yep. For in-pool migration there is xe vdi-pool-migration command. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 03:19:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 03:19:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqbL8-0006Nk-RH; Thu, 03 Jan 2013 03:19:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqbL6-0006Nf-QP for xen-api@lists.xen.org; Thu, 03 Jan 2013 03:19:29 +0000 Received: from [85.158.138.51:45068] by server-11.bemta-3.messagelabs.com id E3/2F-13335-FB8F4E05; Thu, 03 Jan 2013 03:19:27 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1357183166!23178727!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26396 invoked from network); 3 Jan 2013 03:19:27 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 03:19:27 -0000 Received: by mail-la0-f48.google.com with SMTP id ej20so7237300lab.35 for ; Wed, 02 Jan 2013 19:19:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=hoyHDTU/oJprPmbp+xQ+dlwy9bPnO5Dm+2LxpKt+2Lg=; b=gKn3uXMxky9HEVk2YgzuJvXZ0RDXpJmnNmTnrHsO2HBjCyHJ01gqMcI7zdQrEuMKhb RSfv6bVzzvT99saEZr738WhTCShwy5/NYg2eepsjBrYToVDqI6JZk+bX3BL7LbZTw4cj 67vQ268CwNGm9iV4U512l/yOK9J7C9jtGfMKMoMEsBayPzEMLLErsc4uTgZv82klNg8o MrUTGasbZ4s4G/OXOLaCSwFb0j79+evfiuMb9P7+zCjjWuFz/18vArN6Dv4mj4OzSS5W OVSZ6OdKTeb6fOt/fjNsCtpt4sWgrNjaQyvzgrNWE5uRG+/u+tBUN1itjCasg8vXyzey Joug== X-Received: by 10.152.125.7 with SMTP id mm7mr46055089lab.2.1357183165133; Wed, 02 Jan 2013 19:19:25 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id ja10sm17949867lab.6.2013.01.02.19.19.23 (version=SSLv3 cipher=OTHER); Wed, 02 Jan 2013 19:19:24 -0800 (PST) Message-ID: <50E4F8BB.9070004@gmail.com> Date: Thu, 03 Jan 2013 07:19:23 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> In-Reply-To: <50E49A23.7060804@ondore.com> Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 03.01.2013 00:35, Alexandre Kouznetsov wrote: > Hello. > > I have made more tests and got a successful migration using Storage > XenMotion. It happened only after I have removed the destination XCP > host from the actual pool, and moved it to a new one. > > It seems like "destination-sr-uuid=" option is recognized correctly > only when a "remote-master=" and other connection details are > specified. The neighbor thread > http://lists.xen.org/archives/html/xen-api/2012-12/msg00162.html was > helpful. Yes, they fly between pools like magic. The option > "live=" does not make any visible difference: a Debian VM > with default 8GB hdd and no activity pauses for around 2 seconds and > my shell connection to it is not lost, in both cases, "live=false" and > "live=true". > live migration performs set of iterations over VM memory (you can see details in /tmp/xenguest.log on source host), live=false performs 'pause and copy' mode. They are almost the same for idle machines, but make a huge difference for heavy-loaded servers, which change lot of memory every second. (F.e. heavy loaded erlang application with work heap about 10GiB: it live migration performs all 32 iterations and still forced to make 'pause and copy' at final round with large memory delta). > Still not clear how to migrate VM's in the following cases: > - When VM is not online (vm-migrate insists it should be "running"). > - When origin and destination hosts are within the same pool. > offline croos-pool migration is not supported, AFAIK. Sad, yep. For in-pool migration there is xe vdi-pool-migration command. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 11:14:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 11:14:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqikc-00073R-1O; Thu, 03 Jan 2013 11:14:18 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqika-00073M-MO for xen-api@lists.xen.org; Thu, 03 Jan 2013 11:14:16 +0000 Received: from [85.158.139.211:39974] by server-5.bemta-5.messagelabs.com id AD/F5-22648-70865E05; Thu, 03 Jan 2013 11:14:15 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1357211655!22705504!1 X-Originating-IP: [207.126.144.135] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12403 invoked from network); 3 Jan 2013 11:14:15 -0000 Received: from eu1sys200aog113.obsmtp.com (HELO eu1sys200aog113.obsmtp.com) (207.126.144.135) by server-6.tower-206.messagelabs.com with SMTP; 3 Jan 2013 11:14:15 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob113.postini.com ([207.126.147.11]) with SMTP ID DSNKUOVoB2FZAPmqYUA7KUoSlbfsXu9CBQrM@postini.com; Thu, 03 Jan 2013 11:14:15 UTC Received: from lonwexhtca01.uk.futurenet.com (lonwexhtca01.uk.futurenet.com [172.23.130.5]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 356DD7F43EA for ; Thu, 3 Jan 2013 11:14:15 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by lonwexhtca01.uk.futurenet.com ([172.23.130.5]) with mapi; Thu, 3 Jan 2013 11:14:15 +0000 From: Dave Avent To: "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 11:14:14 +0000 Thread-Topic: XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3po3asoRRPEwLFQ9K6evrbyDMfEg== Message-ID: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org All, I have been playing with Xen Cloud Platform 1.6 in the lab and have been noticing some strange behaviour when using the API to drive it. Using XenCenter worked some of the time but then appeared to freeze, not refresh and then on re-connecting get stuck on "Synchronising". I put this down to the client software and switched instead to writing my own client interface using Ruby and the FOG libraries. This worked well but I started seeing the same lock-ups. After digging about I realised that it always locks up at the same point namely the VM.get_all_records call. The call is received as the xensource.log shows: xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records D:7f14fc2bea45|api_readonly] VM.get_all_records But nothing is received and the clients TCP connection times out. This problem happens for well over 50% of the calls made to the API so I am interested to know if anyone else is having this problem? Regards, Dave-- Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 11:14:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 11:14:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqikc-00073R-1O; Thu, 03 Jan 2013 11:14:18 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqika-00073M-MO for xen-api@lists.xen.org; Thu, 03 Jan 2013 11:14:16 +0000 Received: from [85.158.139.211:39974] by server-5.bemta-5.messagelabs.com id AD/F5-22648-70865E05; Thu, 03 Jan 2013 11:14:15 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1357211655!22705504!1 X-Originating-IP: [207.126.144.135] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12403 invoked from network); 3 Jan 2013 11:14:15 -0000 Received: from eu1sys200aog113.obsmtp.com (HELO eu1sys200aog113.obsmtp.com) (207.126.144.135) by server-6.tower-206.messagelabs.com with SMTP; 3 Jan 2013 11:14:15 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob113.postini.com ([207.126.147.11]) with SMTP ID DSNKUOVoB2FZAPmqYUA7KUoSlbfsXu9CBQrM@postini.com; Thu, 03 Jan 2013 11:14:15 UTC Received: from lonwexhtca01.uk.futurenet.com (lonwexhtca01.uk.futurenet.com [172.23.130.5]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 356DD7F43EA for ; Thu, 3 Jan 2013 11:14:15 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by lonwexhtca01.uk.futurenet.com ([172.23.130.5]) with mapi; Thu, 3 Jan 2013 11:14:15 +0000 From: Dave Avent To: "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 11:14:14 +0000 Thread-Topic: XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3po3asoRRPEwLFQ9K6evrbyDMfEg== Message-ID: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org All, I have been playing with Xen Cloud Platform 1.6 in the lab and have been noticing some strange behaviour when using the API to drive it. Using XenCenter worked some of the time but then appeared to freeze, not refresh and then on re-connecting get stuck on "Synchronising". I put this down to the client software and switched instead to writing my own client interface using Ruby and the FOG libraries. This worked well but I started seeing the same lock-ups. After digging about I realised that it always locks up at the same point namely the VM.get_all_records call. The call is received as the xensource.log shows: xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records D:7f14fc2bea45|api_readonly] VM.get_all_records But nothing is received and the clients TCP connection times out. This problem happens for well over 50% of the calls made to the API so I am interested to know if anyone else is having this problem? Regards, Dave-- Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:06:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:06:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjYh-0000dE-Ji; Thu, 03 Jan 2013 12:06:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjYf-0000d9-U6 for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:06:02 +0000 Received: from [193.109.254.147:7771] by server-6.bemta-14.messagelabs.com id AC/15-25153-92475E05; Thu, 03 Jan 2013 12:06:01 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1357214760!3147906!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4562 invoked from network); 3 Jan 2013 12:06:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:06:00 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="431611" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:06:00 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 12:06:00 +0000 From: Dave Scott To: 'Dave Avent' , "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 12:05:58 +0000 Thread-Topic: XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3po3asoRRPEwLFQ9K6evrbyDMfEgABo3Ug Message-ID: <81A73678E76EA642801C8F2E4823AD21012F0D72EBDE@LONPMAILBOX01.citrite.net> References: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> In-Reply-To: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, That's very strange. Could it be the size of the "VM.get_all_records" response is too big to be sent properly? Do other APIs which generate less traffic (e.g. "Pool.get_all_records") always work, or do they sometimes fail too? Perhaps you've got a thread or fd leak? If you run "top" and look at the virtual size of the "xapi" process, is it very large? Maybe there are too many threads and it's blocking? If it looks very large (more than 1 or 2 GB) then I'd be interested to see how many file descriptors are open (look in /proc//fd -- but make sure you select the child pid since the parent is a much smaller watchdog process). It might be that some client(s) are keeping connections open for longer than expected and currently xapi uses a thread-per-connection model. Does restarting the xapi process cause the problem to go away (even if temporarily)? Cheers, Dave > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Dave Avent > Sent: 03 January 2013 11:14 AM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging > > All, > > I have been playing with Xen Cloud Platform 1.6 in the lab and have been > noticing some strange behaviour when using the API to drive it. Using > XenCenter worked some of the time but then appeared to freeze, not > refresh and then on re-connecting get stuck on "Synchronising". I put this > down to the client software and switched instead to writing my own client > interface using Ruby and the FOG libraries. This worked well but I started > seeing the same lock-ups. After digging about I realised that it always locks > up at the same point namely the VM.get_all_records call. > > The call is received as the xensource.log shows: > > xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records > D:7f14fc2bea45|api_readonly] VM.get_all_records > > But nothing is received and the clients TCP connection times out. > > This problem happens for well over 50% of the calls made to the API so I am > interested to know if anyone else is having this problem? > > Regards, > > Dave-- > Future Publishing Limited (registered company number 2008885) is a wholly > owned subsidiary of Future plc (registered company number 3757874), both > of which are incorporated in England and Wales and share the same > registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to which they are addressed. If > you have received this email in error please reply to this email and then > delete it. Please note that any views or opinions presented in this email are > solely those of the author and do not necessarily represent those of Future. > > The recipient should check this email and any attachments for the presence > of viruses. Future accepts no liability for any damage caused by any virus > transmitted by this email. > > Future may regularly and randomly monitor outgoing and incoming emails > and other telecommunications on its email and telecommunications > systems. By replying to this email you give your consent to such monitoring. > > ***** > Save resources: think before you print. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:06:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:06:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjYh-0000dE-Ji; Thu, 03 Jan 2013 12:06:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjYf-0000d9-U6 for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:06:02 +0000 Received: from [193.109.254.147:7771] by server-6.bemta-14.messagelabs.com id AC/15-25153-92475E05; Thu, 03 Jan 2013 12:06:01 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1357214760!3147906!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4562 invoked from network); 3 Jan 2013 12:06:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:06:00 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="431611" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:06:00 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 12:06:00 +0000 From: Dave Scott To: 'Dave Avent' , "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 12:05:58 +0000 Thread-Topic: XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3po3asoRRPEwLFQ9K6evrbyDMfEgABo3Ug Message-ID: <81A73678E76EA642801C8F2E4823AD21012F0D72EBDE@LONPMAILBOX01.citrite.net> References: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> In-Reply-To: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, That's very strange. Could it be the size of the "VM.get_all_records" response is too big to be sent properly? Do other APIs which generate less traffic (e.g. "Pool.get_all_records") always work, or do they sometimes fail too? Perhaps you've got a thread or fd leak? If you run "top" and look at the virtual size of the "xapi" process, is it very large? Maybe there are too many threads and it's blocking? If it looks very large (more than 1 or 2 GB) then I'd be interested to see how many file descriptors are open (look in /proc//fd -- but make sure you select the child pid since the parent is a much smaller watchdog process). It might be that some client(s) are keeping connections open for longer than expected and currently xapi uses a thread-per-connection model. Does restarting the xapi process cause the problem to go away (even if temporarily)? Cheers, Dave > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Dave Avent > Sent: 03 January 2013 11:14 AM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging > > All, > > I have been playing with Xen Cloud Platform 1.6 in the lab and have been > noticing some strange behaviour when using the API to drive it. Using > XenCenter worked some of the time but then appeared to freeze, not > refresh and then on re-connecting get stuck on "Synchronising". I put this > down to the client software and switched instead to writing my own client > interface using Ruby and the FOG libraries. This worked well but I started > seeing the same lock-ups. After digging about I realised that it always locks > up at the same point namely the VM.get_all_records call. > > The call is received as the xensource.log shows: > > xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records > D:7f14fc2bea45|api_readonly] VM.get_all_records > > But nothing is received and the clients TCP connection times out. > > This problem happens for well over 50% of the calls made to the API so I am > interested to know if anyone else is having this problem? > > Regards, > > Dave-- > Future Publishing Limited (registered company number 2008885) is a wholly > owned subsidiary of Future plc (registered company number 3757874), both > of which are incorporated in England and Wales and share the same > registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to which they are addressed. If > you have received this email in error please reply to this email and then > delete it. Please note that any views or opinions presented in this email are > solely those of the author and do not necessarily represent those of Future. > > The recipient should check this email and any attachments for the presence > of viruses. Future accepts no liability for any damage caused by any virus > transmitted by this email. > > Future may regularly and randomly monitor outgoing and incoming emails > and other telecommunications on its email and telecommunications > systems. By replying to this email you give your consent to such monitoring. > > ***** > Save resources: think before you print. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:12:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:12:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjeY-00017w-J9; Thu, 03 Jan 2013 12:12:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjeW-00017q-Lu for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:12:04 +0000 Received: from [85.158.143.35:52646] by server-3.bemta-4.messagelabs.com id E4/C6-18211-49575E05; Thu, 03 Jan 2013 12:12:04 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1357215122!12557339!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22866 invoked from network); 3 Jan 2013 12:12:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:12:03 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="431728" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:11:59 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 3 Jan 2013 12:11:59 +0000 From: Rob Hoes To: 'Alexandre Kouznetsov' , "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 12:11:59 +0000 Thread-Topic: [Xen-API] XCP 1.6 bonding, 2 or 4 NICs Thread-Index: Ac3kVrUHi4avb2FyQyCzqgTXvfnUvwFU1WrA Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF7287A74@LONPMAILBOX01.citrite.net> References: <50DC82DD.5010204@ondore.com> In-Reply-To: <50DC82DD.5010204@ondore.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 bonding, 2 or 4 NICs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Alexandre, It should be possible to create bonds of 4 NICs in the newest version of XenCenter (the one that comes with XenServer 6.1). Are you using that version? The CLI does not have a limit on the number of NICs in a bond, so you can indeed use that if XenCenter does not work. Cheers, Rob > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] > On Behalf Of Alexandre Kouznetsov > Sent: 27 December 2012 5:18 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6 bonding, 2 or 4 NICs > > Hello. > > I'm planning the configuration for a small XCP 1.6 cluster. On of the > requirements is high throughput between the nodes, so I'm planning to > bond up to 4 physical 1Gbps NIC's together. After playing around a little bit an > studying documentation a few questions have arised. > > (I think I better split this into several messages) > > XenCenter allows me to create "bond" networks, but only with 2 interfaces, > while XCP 1.6 Release Notes mentions that it allows up to 4 NICs to be used > in an active-active bond. Is it a XenCenter's limitation, and in my case the > bond of 4 NIC's shall be created from CLI? Or XenCenter should normally > allow me to bond 4 NICs if the Xen Host supports it, meaning that something > is wrong with my setup? > > Greetings. > > -- > Alexandre Kouznetsov > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:12:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:12:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjeY-00017w-J9; Thu, 03 Jan 2013 12:12:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjeW-00017q-Lu for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:12:04 +0000 Received: from [85.158.143.35:52646] by server-3.bemta-4.messagelabs.com id E4/C6-18211-49575E05; Thu, 03 Jan 2013 12:12:04 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1357215122!12557339!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22866 invoked from network); 3 Jan 2013 12:12:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:12:03 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="431728" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:11:59 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 3 Jan 2013 12:11:59 +0000 From: Rob Hoes To: 'Alexandre Kouznetsov' , "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 12:11:59 +0000 Thread-Topic: [Xen-API] XCP 1.6 bonding, 2 or 4 NICs Thread-Index: Ac3kVrUHi4avb2FyQyCzqgTXvfnUvwFU1WrA Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF7287A74@LONPMAILBOX01.citrite.net> References: <50DC82DD.5010204@ondore.com> In-Reply-To: <50DC82DD.5010204@ondore.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 bonding, 2 or 4 NICs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Alexandre, It should be possible to create bonds of 4 NICs in the newest version of XenCenter (the one that comes with XenServer 6.1). Are you using that version? The CLI does not have a limit on the number of NICs in a bond, so you can indeed use that if XenCenter does not work. Cheers, Rob > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] > On Behalf Of Alexandre Kouznetsov > Sent: 27 December 2012 5:18 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6 bonding, 2 or 4 NICs > > Hello. > > I'm planning the configuration for a small XCP 1.6 cluster. On of the > requirements is high throughput between the nodes, so I'm planning to > bond up to 4 physical 1Gbps NIC's together. After playing around a little bit an > studying documentation a few questions have arised. > > (I think I better split this into several messages) > > XenCenter allows me to create "bond" networks, but only with 2 interfaces, > while XCP 1.6 Release Notes mentions that it allows up to 4 NICs to be used > in an active-active bond. Is it a XenCenter's limitation, and in my case the > bond of 4 NIC's shall be created from CLI? Or XenCenter should normally > allow me to bond 4 NICs if the Xen Host supports it, meaning that something > is wrong with my setup? > > Greetings. > > -- > Alexandre Kouznetsov > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:14:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:14:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqjgk-0001Ja-Ny; Thu, 03 Jan 2013 12:14:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tqjgj-0001JP-Ce for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:14:21 +0000 Received: from [85.158.139.83:49189] by server-10.bemta-5.messagelabs.com id 09/05-13383-C1675E05; Thu, 03 Jan 2013 12:14:20 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1357215258!31557591!1 X-Originating-IP: [209.85.220.44] X-SpamReason: No, hits=0.1 required=7.0 tests=ratty_date: unknown timezone in: Thu, 3 Jan 2013 17:44:57 +0550, ratty_date: unknown timezone in: Thu, 3 Jan 2013 17:44:57 +0550, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7837 invoked from network); 3 Jan 2013 12:14:19 -0000 Received: from mail-pa0-f44.google.com (HELO mail-pa0-f44.google.com) (209.85.220.44) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:14:19 -0000 Received: by mail-pa0-f44.google.com with SMTP id hz11so8628445pad.17 for ; Thu, 03 Jan 2013 04:14:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:from:to:date:user-agent:subject:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=S4CEQqwMNUmwJp15HCbYamAJCHXvfNCIoSJVhZDx9TU=; b=tHGIkpVAqmcHkAu/DmBXdIIe0i/VsO0VPO4LY+PxPZJNnK6xS7giA2VsuZtSlG/WZz hlXWAW4Otw3pZm7cXgvGTGENVYLGKR5dTX5JoXP4Cs4KBgIP+uxYl5irIVZ19U0PIzo+ Z7FEizHJUvtEuMNDhRD76gPDg7Z0XLt049OnKjvFDkCLLyQROPIt/T6dzlDTRsxhsa8x hvsQCy4JDfRyQHrI53ngY53J0lNPY9i0vxoTmeEpOQPmW/tn5bSxeaOl5IKFTmibF0FH gG982bgjJms9CXCpZ9pTSR1fC9IISuhDfA4Le7Qo0UBsbORIHPqzs2CEEWCYcvC9CXjg 8dKA== X-Received: by 10.68.189.66 with SMTP id gg2mr118810570pbc.111.1357215257668; Thu, 03 Jan 2013 04:14:17 -0800 (PST) Received: from 10.102.221.239 ([203.88.23.33]) by mx.google.com with ESMTPS id o5sm31179719pay.5.2013.01.03.04.14.14 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 04:14:17 -0800 (PST) Message-ID: <50e57619.4553420a.529d.ffffadbd@mx.google.com> From: 2rushikeshj@gmail.com To: "Dave Avent" , "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 17:44:57 +0550 User-Agent: LogicMail/2.2.0.81 In-Reply-To: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, 3 Jan 2013 16:44:14 +0550, xen-api-bounces@lists.xen.org wrote: > All, > > I have been playing with Xen Cloud Platform 1.6 in the lab and have been noticing some strange behaviour when using the API to drive it. Using XenCenter worked some of the time but then appeared to freeze, not refresh and then on re-connecting get stuck on "Synchronising". I put this down to the client software and switched instead to writing my own client interface using Ruby and the FOG libraries. This worked well but I started seeing the same lock-ups. After digging about I realised that it always locks up at the same point namely the VM.get_all_records call. > > The call is received as the xensource.log shows: > > xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records D:7f14fc2bea45|api_readonly] VM.get_all_records > > But nothing is received and the clients TCP connection times out. > > This problem happens for well over 50% of the calls made to the API so I am interested to know if anyone else is having this problem? > Your Cluster Host Count and VM count ( ON & OFF ) will be helpful. Usual errors are to be checked in xensource.log, messages, kern.log Try to get only list of VM ids and then do a get_record for each VM to see if you get caught in same problem > Regards, > > Dave-- > Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. > > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. > > The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. > > Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. > > ***** > Save resources: think before you print. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:14:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:14:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqjgk-0001Ja-Ny; Thu, 03 Jan 2013 12:14:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tqjgj-0001JP-Ce for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:14:21 +0000 Received: from [85.158.139.83:49189] by server-10.bemta-5.messagelabs.com id 09/05-13383-C1675E05; Thu, 03 Jan 2013 12:14:20 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1357215258!31557591!1 X-Originating-IP: [209.85.220.44] X-SpamReason: No, hits=0.1 required=7.0 tests=ratty_date: unknown timezone in: Thu, 3 Jan 2013 17:44:57 +0550, ratty_date: unknown timezone in: Thu, 3 Jan 2013 17:44:57 +0550, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7837 invoked from network); 3 Jan 2013 12:14:19 -0000 Received: from mail-pa0-f44.google.com (HELO mail-pa0-f44.google.com) (209.85.220.44) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:14:19 -0000 Received: by mail-pa0-f44.google.com with SMTP id hz11so8628445pad.17 for ; Thu, 03 Jan 2013 04:14:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:from:to:date:user-agent:subject:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=S4CEQqwMNUmwJp15HCbYamAJCHXvfNCIoSJVhZDx9TU=; b=tHGIkpVAqmcHkAu/DmBXdIIe0i/VsO0VPO4LY+PxPZJNnK6xS7giA2VsuZtSlG/WZz hlXWAW4Otw3pZm7cXgvGTGENVYLGKR5dTX5JoXP4Cs4KBgIP+uxYl5irIVZ19U0PIzo+ Z7FEizHJUvtEuMNDhRD76gPDg7Z0XLt049OnKjvFDkCLLyQROPIt/T6dzlDTRsxhsa8x hvsQCy4JDfRyQHrI53ngY53J0lNPY9i0vxoTmeEpOQPmW/tn5bSxeaOl5IKFTmibF0FH gG982bgjJms9CXCpZ9pTSR1fC9IISuhDfA4Le7Qo0UBsbORIHPqzs2CEEWCYcvC9CXjg 8dKA== X-Received: by 10.68.189.66 with SMTP id gg2mr118810570pbc.111.1357215257668; Thu, 03 Jan 2013 04:14:17 -0800 (PST) Received: from 10.102.221.239 ([203.88.23.33]) by mx.google.com with ESMTPS id o5sm31179719pay.5.2013.01.03.04.14.14 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 04:14:17 -0800 (PST) Message-ID: <50e57619.4553420a.529d.ffffadbd@mx.google.com> From: 2rushikeshj@gmail.com To: "Dave Avent" , "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 17:44:57 +0550 User-Agent: LogicMail/2.2.0.81 In-Reply-To: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, 3 Jan 2013 16:44:14 +0550, xen-api-bounces@lists.xen.org wrote: > All, > > I have been playing with Xen Cloud Platform 1.6 in the lab and have been noticing some strange behaviour when using the API to drive it. Using XenCenter worked some of the time but then appeared to freeze, not refresh and then on re-connecting get stuck on "Synchronising". I put this down to the client software and switched instead to writing my own client interface using Ruby and the FOG libraries. This worked well but I started seeing the same lock-ups. After digging about I realised that it always locks up at the same point namely the VM.get_all_records call. > > The call is received as the xensource.log shows: > > xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records D:7f14fc2bea45|api_readonly] VM.get_all_records > > But nothing is received and the clients TCP connection times out. > > This problem happens for well over 50% of the calls made to the API so I am interested to know if anyone else is having this problem? > Your Cluster Host Count and VM count ( ON & OFF ) will be helpful. Usual errors are to be checked in xensource.log, messages, kern.log Try to get only list of VM ids and then do a get_record for each VM to see if you get caught in same problem > Regards, > > Dave-- > Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. > > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. > > The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. > > Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. > > ***** > Save resources: think before you print. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:26:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:26:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjsX-0001Zf-17; Thu, 03 Jan 2013 12:26:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjsU-0001Za-Th for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:26:31 +0000 Received: from [85.158.138.51:6002] by server-2.bemta-3.messagelabs.com id C8/B2-11239-6F875E05; Thu, 03 Jan 2013 12:26:30 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1357215988!23129189!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15221 invoked from network); 3 Jan 2013 12:26:29 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:26:29 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208,217";a="431946" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:25:29 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 12:25:28 +0000 From: Rob Hoes To: Mikael Hugo Date: Thu, 3 Jan 2013 12:25:27 +0000 Thread-Topic: [Xen-API] Intel 82574L in XCP 1.6 and vlan Thread-Index: Ac3prWnCPIZN7WY2SniaIMTjoAzQpA== Message-ID: <09FE01CD-6939-4EE6-A5CC-20D0E6EAE0F4@citrix.com> References: <23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7@SOLNA-MBX01.nschmc.local> In-Reply-To: <23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7@SOLNA-MBX01.nschmc.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Intel 82574L in XCP 1.6 and vlan X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1671059695046400532==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1671059695046400532== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_09FE01CD69394EE6A5CC20D0E6EAE0F4citrixcom_" --_000_09FE01CD69394EE6A5CC20D0E6EAE0F4citrixcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Mikael, XCP 1.6 should have the same drivers as XenServer 6.1, so you should alread= y have the latest ones. What does your setup look like? How did you configure the VLANs on the XCP = host? And did you configure your (physical) switch port as a trunk port wit= h access to the VLANs you need? Cheers, Rob On 1 Jan 2013, at 21:09, Mikael Hugo > wrote: Hi! I have issues with 82574L in XCP 1.6 - It works untagged but not with tagged vlans. I see Xenserver 6.1 has an updated driver kit for Intel and it feels like it must be a driver issue since I get zero traffic. Any good way to figure it out or any known fix? /Mikael _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_000_09FE01CD69394EE6A5CC20D0E6EAE0F4citrixcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Mikael,

=
XCP 1.6 should have the same drivers as XenServer 6.1, so you should a= lready have the latest ones.

What does your setup = look like? How did you configure the VLANs on the XCP host? And did you con= figure your (physical) switch port as a trunk port with access to the VLANs= you need?

Cheers,
Rob

On 1 Jan 2013, at 21:09, Mikael Hugo <mikael@servercentralen.se> wrote:

Hi!

I have issues wit= h 82574L in XCP 1.6 - It works untagged but not with
tagged vlans.

I see Xenserver 6= .1 has an updated driver kit for Intel and it feels like
it must be a driv= er issue since I get zero traffic.

Any good way to f= igure it out or any known fix?

/Mikael

_______________________________________________
Xen-api mailing list
= Xen-api@lists.xen.org
http:= //lists.xen.org/cgi-bin/mailman/listinfo/xen-api

= = --_000_09FE01CD69394EE6A5CC20D0E6EAE0F4citrixcom_-- --===============1671059695046400532== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1671059695046400532==-- From xen-api-bounces@lists.xen.org Thu Jan 03 12:26:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:26:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjsX-0001Zf-17; Thu, 03 Jan 2013 12:26:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjsU-0001Za-Th for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:26:31 +0000 Received: from [85.158.138.51:6002] by server-2.bemta-3.messagelabs.com id C8/B2-11239-6F875E05; Thu, 03 Jan 2013 12:26:30 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1357215988!23129189!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15221 invoked from network); 3 Jan 2013 12:26:29 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:26:29 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208,217";a="431946" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:25:29 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 12:25:28 +0000 From: Rob Hoes To: Mikael Hugo Date: Thu, 3 Jan 2013 12:25:27 +0000 Thread-Topic: [Xen-API] Intel 82574L in XCP 1.6 and vlan Thread-Index: Ac3prWnCPIZN7WY2SniaIMTjoAzQpA== Message-ID: <09FE01CD-6939-4EE6-A5CC-20D0E6EAE0F4@citrix.com> References: <23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7@SOLNA-MBX01.nschmc.local> In-Reply-To: <23A9CFB8DDE7F34089CC14B4B86FDA5848F1A1B7@SOLNA-MBX01.nschmc.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Intel 82574L in XCP 1.6 and vlan X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1671059695046400532==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1671059695046400532== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_09FE01CD69394EE6A5CC20D0E6EAE0F4citrixcom_" --_000_09FE01CD69394EE6A5CC20D0E6EAE0F4citrixcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Mikael, XCP 1.6 should have the same drivers as XenServer 6.1, so you should alread= y have the latest ones. What does your setup look like? How did you configure the VLANs on the XCP = host? And did you configure your (physical) switch port as a trunk port wit= h access to the VLANs you need? Cheers, Rob On 1 Jan 2013, at 21:09, Mikael Hugo > wrote: Hi! I have issues with 82574L in XCP 1.6 - It works untagged but not with tagged vlans. I see Xenserver 6.1 has an updated driver kit for Intel and it feels like it must be a driver issue since I get zero traffic. Any good way to figure it out or any known fix? /Mikael _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_000_09FE01CD69394EE6A5CC20D0E6EAE0F4citrixcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Mikael,

=
XCP 1.6 should have the same drivers as XenServer 6.1, so you should a= lready have the latest ones.

What does your setup = look like? How did you configure the VLANs on the XCP host? And did you con= figure your (physical) switch port as a trunk port with access to the VLANs= you need?

Cheers,
Rob

On 1 Jan 2013, at 21:09, Mikael Hugo <mikael@servercentralen.se> wrote:

Hi!

I have issues wit= h 82574L in XCP 1.6 - It works untagged but not with
tagged vlans.

I see Xenserver 6= .1 has an updated driver kit for Intel and it feels like
it must be a driv= er issue since I get zero traffic.

Any good way to f= igure it out or any known fix?

/Mikael

_______________________________________________
Xen-api mailing list
= Xen-api@lists.xen.org
http:= //lists.xen.org/cgi-bin/mailman/listinfo/xen-api

= = --_000_09FE01CD69394EE6A5CC20D0E6EAE0F4citrixcom_-- --===============1671059695046400532== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1671059695046400532==-- From xen-api-bounces@lists.xen.org Thu Jan 03 12:29:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:29:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjvF-0001eV-Dy; Thu, 03 Jan 2013 12:29:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjvD-0001eP-Nc for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:29:19 +0000 Received: from [85.158.137.99:51756] by server-15.bemta-3.messagelabs.com id B5/F4-07921-A9975E05; Thu, 03 Jan 2013 12:29:14 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1357216147!21649066!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16750 invoked from network); 3 Jan 2013 12:29:13 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:29:13 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="432011" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:29:07 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 12:29:06 +0000 From: Rob Hoes To: George Shuklin Date: Thu, 3 Jan 2013 12:29:06 +0000 Thread-Topic: [Xen-API] XCP: ip restriction is completely broken for xenbr1, xenbr2, etc. Thread-Index: Ac3prewe8hg0XVFNRTCKYxUYIaVRKg== Message-ID: References: <50D07CB0.8070406@gmail.com> In-Reply-To: <50D07CB0.8070406@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP: ip restriction is completely broken for xenbr1, xenbr2, etc. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi George, You are certainly right about this =96 this is quite bad. I saw your pull request on github and will try it out. Thanks for reporting this and submitting a fix as well! Cheers, Rob On 18 Dec 2012, at 14:24, George Shuklin wrote: > I found some kind of horrible bug in XCP 1.6. > = > After looking to src on github (master branch) I found it still there. > = > Way to reproduce: > = > create vif with device=3D15 (or any other >0). > set up locking-mode=3Dlocked > set up some ipv4-allowed. > = > xe vif-plug .... > = > expected result: rules for OVS applied to xenbr, corresponding to vif = > network's bridge. > = > actual result: device number (15) is is used as bridge number (xenbr15!). > = > I done some source code review: > Dec 18 18:17:54 rvc2-xh43 python: = > /opt/xensource/libexec/setup-vif-rules[8505] - Called with vif_type=3Dvif= , = > domid=3D1, devid=3D15, network_mode=3Dopenvswitch, action=3Dfilter > = > devid=3D15 <- WRONG > = > It use vif id from xenstore instead of proper 'bridge' field from = > network object. > = > = > = > = > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:29:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:29:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjvF-0001eV-Dy; Thu, 03 Jan 2013 12:29:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqjvD-0001eP-Nc for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:29:19 +0000 Received: from [85.158.137.99:51756] by server-15.bemta-3.messagelabs.com id B5/F4-07921-A9975E05; Thu, 03 Jan 2013 12:29:14 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1357216147!21649066!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16750 invoked from network); 3 Jan 2013 12:29:13 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:29:13 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="432011" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:29:07 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 12:29:06 +0000 From: Rob Hoes To: George Shuklin Date: Thu, 3 Jan 2013 12:29:06 +0000 Thread-Topic: [Xen-API] XCP: ip restriction is completely broken for xenbr1, xenbr2, etc. Thread-Index: Ac3prewe8hg0XVFNRTCKYxUYIaVRKg== Message-ID: References: <50D07CB0.8070406@gmail.com> In-Reply-To: <50D07CB0.8070406@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP: ip restriction is completely broken for xenbr1, xenbr2, etc. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi George, You are certainly right about this =96 this is quite bad. I saw your pull request on github and will try it out. Thanks for reporting this and submitting a fix as well! Cheers, Rob On 18 Dec 2012, at 14:24, George Shuklin wrote: > I found some kind of horrible bug in XCP 1.6. > = > After looking to src on github (master branch) I found it still there. > = > Way to reproduce: > = > create vif with device=3D15 (or any other >0). > set up locking-mode=3Dlocked > set up some ipv4-allowed. > = > xe vif-plug .... > = > expected result: rules for OVS applied to xenbr, corresponding to vif = > network's bridge. > = > actual result: device number (15) is is used as bridge number (xenbr15!). > = > I done some source code review: > Dec 18 18:17:54 rvc2-xh43 python: = > /opt/xensource/libexec/setup-vif-rules[8505] - Called with vif_type=3Dvif= , = > domid=3D1, devid=3D15, network_mode=3Dopenvswitch, action=3Dfilter > = > devid=3D15 <- WRONG > = > It use vif id from xenstore instead of proper 'bridge' field from = > network object. > = > = > = > = > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:35:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:35:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqk15-0001lF-9A; Thu, 03 Jan 2013 12:35:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqk13-0001lA-6H for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:35:21 +0000 Received: from [85.158.139.83:12269] by server-6.bemta-5.messagelabs.com id C2/A0-30498-80B75E05; Thu, 03 Jan 2013 12:35:20 +0000 X-Env-Sender: mikael@servercentralen.se X-Msg-Ref: server-2.tower-182.messagelabs.com!1357216518!30370471!1 X-Originating-IP: [188.95.35.85] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20710 invoked from network); 3 Jan 2013 12:35:19 -0000 Received: from solna-gw2.centralcloud.net (HELO smtpedge.centralcloud.net) (188.95.35.85) by server-2.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 3 Jan 2013 12:35:19 -0000 Received: from SOLNA-MBX01.nschmc.local ([fe80::2498:f5a:2882:1d75]) by SOLNA-HUB02.nschmc.local ([fe80::353e:8782:8f07:2414%11]) with mapi id 14.02.0309.002; Thu, 3 Jan 2013 13:37:29 +0100 From: Mikael Hugo To: Rob Hoes Thread-Topic: [Xen-API] Intel 82574L in XCP 1.6 and vlan Thread-Index: AQHN6GRLuLsyizZFEUC1uWXZ9gjHk5g3eUaAgAATfoA= Date: Thu, 3 Jan 2013 12:38:20 +0000 Message-ID: <23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18F@SOLNA-MBX01.nschmc.local> In-Reply-To: <09FE01CD-6939-4EE6-A5CC-20D0E6EAE0F4@citrix.com> Accept-Language: sv-SE, en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.5.121010 x-originating-ip: [192.168.68.2] MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Intel 82574L in XCP 1.6 and vlan X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7821103788462085813==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7821103788462085813== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18FSOLNAMBX01nschm_" --_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18FSOLNAMBX01nschm_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, 6.1 does not have the latest drivers - The Citrix update package has much m= ore recent drivers. The card is on the HCL list. Looking at the router its plugged into I don't get any traffic at all comin= g from the server. I have configured the VLANs on the server using xencente= r 6.1 as we have some xenservers running too with no issues like this. I reinstalled the system just to be sure, but there is no difference. Since the system had 6 ports I'm just running untagged for now. I have an i= dentical machine I will install and make some tests on. Can I dump a packet trace in the machine and see what its doing in wireshar= k somehow from the open switch? /M --_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18FSOLNAMBX01nschm_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
Hi,

6.1 does not have the latest drivers - The Citrix update package has m= uch more recent drivers.

The card is on the HCL list.

Looking at the router its plugged into I don't get any traffic at all = coming from the server. I have configured the VLANs on the server using xen= center 6.1 as we have some xenservers running too with no issues like this.=

I reinstalled the system just to be sure, but there is no difference.&= nbsp;

Since the system had 6 ports I'm just running untagged for now. I have= an identical machine I will install and make some tests on.

Can I dump a packet trace in the machine and see what its doing in wir= eshark somehow from the open switch?

/M
--_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18FSOLNAMBX01nschm_-- --===============7821103788462085813== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7821103788462085813==-- From xen-api-bounces@lists.xen.org Thu Jan 03 12:35:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:35:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqk15-0001lF-9A; Thu, 03 Jan 2013 12:35:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqk13-0001lA-6H for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:35:21 +0000 Received: from [85.158.139.83:12269] by server-6.bemta-5.messagelabs.com id C2/A0-30498-80B75E05; Thu, 03 Jan 2013 12:35:20 +0000 X-Env-Sender: mikael@servercentralen.se X-Msg-Ref: server-2.tower-182.messagelabs.com!1357216518!30370471!1 X-Originating-IP: [188.95.35.85] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20710 invoked from network); 3 Jan 2013 12:35:19 -0000 Received: from solna-gw2.centralcloud.net (HELO smtpedge.centralcloud.net) (188.95.35.85) by server-2.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 3 Jan 2013 12:35:19 -0000 Received: from SOLNA-MBX01.nschmc.local ([fe80::2498:f5a:2882:1d75]) by SOLNA-HUB02.nschmc.local ([fe80::353e:8782:8f07:2414%11]) with mapi id 14.02.0309.002; Thu, 3 Jan 2013 13:37:29 +0100 From: Mikael Hugo To: Rob Hoes Thread-Topic: [Xen-API] Intel 82574L in XCP 1.6 and vlan Thread-Index: AQHN6GRLuLsyizZFEUC1uWXZ9gjHk5g3eUaAgAATfoA= Date: Thu, 3 Jan 2013 12:38:20 +0000 Message-ID: <23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18F@SOLNA-MBX01.nschmc.local> In-Reply-To: <09FE01CD-6939-4EE6-A5CC-20D0E6EAE0F4@citrix.com> Accept-Language: sv-SE, en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.5.121010 x-originating-ip: [192.168.68.2] MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Intel 82574L in XCP 1.6 and vlan X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7821103788462085813==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7821103788462085813== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18FSOLNAMBX01nschm_" --_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18FSOLNAMBX01nschm_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, 6.1 does not have the latest drivers - The Citrix update package has much m= ore recent drivers. The card is on the HCL list. Looking at the router its plugged into I don't get any traffic at all comin= g from the server. I have configured the VLANs on the server using xencente= r 6.1 as we have some xenservers running too with no issues like this. I reinstalled the system just to be sure, but there is no difference. Since the system had 6 ports I'm just running untagged for now. I have an i= dentical machine I will install and make some tests on. Can I dump a packet trace in the machine and see what its doing in wireshar= k somehow from the open switch? /M --_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18FSOLNAMBX01nschm_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
Hi,

6.1 does not have the latest drivers - The Citrix update package has m= uch more recent drivers.

The card is on the HCL list.

Looking at the router its plugged into I don't get any traffic at all = coming from the server. I have configured the VLANs on the server using xen= center 6.1 as we have some xenservers running too with no issues like this.=

I reinstalled the system just to be sure, but there is no difference.&= nbsp;

Since the system had 6 ports I'm just running untagged for now. I have= an identical machine I will install and make some tests on.

Can I dump a packet trace in the machine and see what its doing in wir= eshark somehow from the open switch?

/M
--_000_23A9CFB8DDE7F34089CC14B4B86FDA5848F1E18FSOLNAMBX01nschm_-- --===============7821103788462085813== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7821103788462085813==-- From xen-api-bounces@lists.xen.org Thu Jan 03 12:36:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:36:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqk1x-0001q4-NZ; Thu, 03 Jan 2013 12:36:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqk1w-0001py-F6 for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:36:16 +0000 Received: from [193.109.254.147:12832] by server-16.bemta-14.messagelabs.com id A1/9C-18932-F3B75E05; Thu, 03 Jan 2013 12:36:15 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1357216575!11843023!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17445 invoked from network); 3 Jan 2013 12:36:15 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:36:15 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="432152" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:36:15 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 12:36:14 +0000 From: Rob Hoes To: George Shuklin , Alexandre Kouznetsov Date: Thu, 3 Jan 2013 12:36:14 +0000 Thread-Topic: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs Thread-Index: Ac3prusxLXJW23SfRGy/pu3uiac+Jg== Message-ID: <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> In-Reply-To: <50E4F8BB.9070004@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 3 Jan 2013, at 03:19, George Shuklin wrote: >> Still not clear how to migrate VM's in the following cases: >> - When VM is not online (vm-migrate insists it should be "running"). >> - When origin and destination hosts are within the same pool. >> = > offline croos-pool migration is not supported, AFAIK. Sad, yep. > = > For in-pool migration there is xe vdi-pool-migration command. You should be able to perform an in-pool storage migration using 'xe vm-mig= rate', when you specify the remote-master/remote-username/remote-password p= arameters for the master of the same pool. A bit weird, but it should work = that way=85 Cheers, Rob _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 12:36:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 12:36:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqk1x-0001q4-NZ; Thu, 03 Jan 2013 12:36:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqk1w-0001py-F6 for xen-api@lists.xen.org; Thu, 03 Jan 2013 12:36:16 +0000 Received: from [193.109.254.147:12832] by server-16.bemta-14.messagelabs.com id A1/9C-18932-F3B75E05; Thu, 03 Jan 2013 12:36:15 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1357216575!11843023!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17445 invoked from network); 3 Jan 2013 12:36:15 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 12:36:15 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="432152" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 12:36:15 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 12:36:14 +0000 From: Rob Hoes To: George Shuklin , Alexandre Kouznetsov Date: Thu, 3 Jan 2013 12:36:14 +0000 Thread-Topic: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs Thread-Index: Ac3prusxLXJW23SfRGy/pu3uiac+Jg== Message-ID: <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> In-Reply-To: <50E4F8BB.9070004@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 3 Jan 2013, at 03:19, George Shuklin wrote: >> Still not clear how to migrate VM's in the following cases: >> - When VM is not online (vm-migrate insists it should be "running"). >> - When origin and destination hosts are within the same pool. >> = > offline croos-pool migration is not supported, AFAIK. Sad, yep. > = > For in-pool migration there is xe vdi-pool-migration command. You should be able to perform an in-pool storage migration using 'xe vm-mig= rate', when you specify the remote-master/remote-username/remote-password p= arameters for the master of the same pool. A bit weird, but it should work = that way=85 Cheers, Rob _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 13:47:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 13:47:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tql8w-0002bX-EI; Thu, 03 Jan 2013 13:47:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tql8v-0002bS-8T for xen-api@lists.xen.org; Thu, 03 Jan 2013 13:47:33 +0000 Received: from [85.158.143.99:35789] by server-2.bemta-4.messagelabs.com id 1B/69-30861-4FB85E05; Thu, 03 Jan 2013 13:47:32 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1357220851!18162539!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=1.8 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27489 invoked from network); 3 Jan 2013 13:47:31 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 13:47:31 -0000 Received: by mail-la0-f42.google.com with SMTP id fe20so7934861lab.15 for ; Thu, 03 Jan 2013 05:47:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Tp22Dt8PrWhneRXgY60zC11gNG473d3yUcVBZRmwR+w=; b=sIiUGAn9YbsULFrPrMyJM+/ty3u/xtlmvU/SIidg4x/E6GIRCCcMv6Jxj68FMyfzt+ S6q95q74RuCQ7nQDUC7U8bbqGhw/IEC1h1W2nwY/GDbQLs8ijD7n45J/5PeFggr46EyI QDDpi5VMtDLqEjbOkgJIrkXK8pIUMmEtCpMU0LWol/+3YrevmZ66C311iWkVcuDSgaZK k4j51LTBFLux/M96fwJ5qyuJItCSEHnKiU4fYwKp1+tzja00GyLS4ibC6Y7Fi/5HUjnZ b40uNFV5g8Wqx6Uvcv/Rr5owVUzvKisRk4eTMMrX/+dMOLykLh9rEJLqhxvXMaf6XD9I EUMQ== X-Received: by 10.112.99.2 with SMTP id em2mr11387055lbb.11.1357220850806; Thu, 03 Jan 2013 05:47:30 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id f2sm462085lbz.4.2013.01.03.05.47.30 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 05:47:30 -0800 (PST) Message-ID: <50E58BF1.1040601@gmail.com> Date: Thu, 03 Jan 2013 17:47:29 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Rob Hoes References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> In-Reply-To: <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SXMgdGhhdCByaWdodCB3YXkgdG8gbWlncmF0ZT8KCkkgbWVhbiwgaWYgbWFzdGVyIGhhZCBubyBh Y2Nlc3MgdG8gZGVzaWduYXRpb24gU1IsIGhvdyBtaWdyYXRpb24gd2lsbCB3b3Jrcz8KCjAzLjAx LjIwMTMgMTY6MzYsIFJvYiBIb2VzINC/0LjRiNC10YI6Cj4gT24gMyBKYW4gMjAxMywgYXQgMDM6 MTksIEdlb3JnZSBTaHVrbGluIDxnZW9yZ2Uuc2h1a2xpbkBnbWFpbC5jb20+IHdyb3RlOgo+Pj4g U3RpbGwgbm90IGNsZWFyIGhvdyB0byBtaWdyYXRlIFZNJ3MgaW4gdGhlIGZvbGxvd2luZyBjYXNl czoKPj4+IC0gV2hlbiBWTSBpcyBub3Qgb25saW5lICh2bS1taWdyYXRlIGluc2lzdHMgaXQgc2hv dWxkIGJlICJydW5uaW5nIikuCj4+PiAtIFdoZW4gb3JpZ2luIGFuZCBkZXN0aW5hdGlvbiBob3N0 cyBhcmUgd2l0aGluIHRoZSBzYW1lIHBvb2wuCj4+Pgo+PiBvZmZsaW5lIGNyb29zLXBvb2wgbWln cmF0aW9uIGlzIG5vdCBzdXBwb3J0ZWQsIEFGQUlLLiBTYWQsIHllcC4KPj4KPj4gRm9yIGluLXBv b2wgbWlncmF0aW9uIHRoZXJlIGlzIHhlIHZkaS1wb29sLW1pZ3JhdGlvbiBjb21tYW5kLgo+IFlv dSBzaG91bGQgYmUgYWJsZSB0byBwZXJmb3JtIGFuIGluLXBvb2wgc3RvcmFnZSBtaWdyYXRpb24g dXNpbmcgJ3hlIHZtLW1pZ3JhdGUnLCB3aGVuIHlvdSBzcGVjaWZ5IHRoZSByZW1vdGUtbWFzdGVy L3JlbW90ZS11c2VybmFtZS9yZW1vdGUtcGFzc3dvcmQgcGFyYW1ldGVycyBmb3IgdGhlIG1hc3Rl ciBvZiB0aGUgc2FtZSBwb29sLiBBIGJpdCB3ZWlyZCwgYnV0IGl0IHNob3VsZCB3b3JrIHRoYXQg d2F54oCmCj4KPiBDaGVlcnMsCj4gUm9iCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4u b3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBp Cg== From xen-api-bounces@lists.xen.org Thu Jan 03 13:47:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 13:47:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tql8w-0002bX-EI; Thu, 03 Jan 2013 13:47:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tql8v-0002bS-8T for xen-api@lists.xen.org; Thu, 03 Jan 2013 13:47:33 +0000 Received: from [85.158.143.99:35789] by server-2.bemta-4.messagelabs.com id 1B/69-30861-4FB85E05; Thu, 03 Jan 2013 13:47:32 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1357220851!18162539!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=1.8 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27489 invoked from network); 3 Jan 2013 13:47:31 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 13:47:31 -0000 Received: by mail-la0-f42.google.com with SMTP id fe20so7934861lab.15 for ; Thu, 03 Jan 2013 05:47:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Tp22Dt8PrWhneRXgY60zC11gNG473d3yUcVBZRmwR+w=; b=sIiUGAn9YbsULFrPrMyJM+/ty3u/xtlmvU/SIidg4x/E6GIRCCcMv6Jxj68FMyfzt+ S6q95q74RuCQ7nQDUC7U8bbqGhw/IEC1h1W2nwY/GDbQLs8ijD7n45J/5PeFggr46EyI QDDpi5VMtDLqEjbOkgJIrkXK8pIUMmEtCpMU0LWol/+3YrevmZ66C311iWkVcuDSgaZK k4j51LTBFLux/M96fwJ5qyuJItCSEHnKiU4fYwKp1+tzja00GyLS4ibC6Y7Fi/5HUjnZ b40uNFV5g8Wqx6Uvcv/Rr5owVUzvKisRk4eTMMrX/+dMOLykLh9rEJLqhxvXMaf6XD9I EUMQ== X-Received: by 10.112.99.2 with SMTP id em2mr11387055lbb.11.1357220850806; Thu, 03 Jan 2013 05:47:30 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id f2sm462085lbz.4.2013.01.03.05.47.30 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 05:47:30 -0800 (PST) Message-ID: <50E58BF1.1040601@gmail.com> Date: Thu, 03 Jan 2013 17:47:29 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Rob Hoes References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> In-Reply-To: <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SXMgdGhhdCByaWdodCB3YXkgdG8gbWlncmF0ZT8KCkkgbWVhbiwgaWYgbWFzdGVyIGhhZCBubyBh Y2Nlc3MgdG8gZGVzaWduYXRpb24gU1IsIGhvdyBtaWdyYXRpb24gd2lsbCB3b3Jrcz8KCjAzLjAx LjIwMTMgMTY6MzYsIFJvYiBIb2VzINC/0LjRiNC10YI6Cj4gT24gMyBKYW4gMjAxMywgYXQgMDM6 MTksIEdlb3JnZSBTaHVrbGluIDxnZW9yZ2Uuc2h1a2xpbkBnbWFpbC5jb20+IHdyb3RlOgo+Pj4g U3RpbGwgbm90IGNsZWFyIGhvdyB0byBtaWdyYXRlIFZNJ3MgaW4gdGhlIGZvbGxvd2luZyBjYXNl czoKPj4+IC0gV2hlbiBWTSBpcyBub3Qgb25saW5lICh2bS1taWdyYXRlIGluc2lzdHMgaXQgc2hv dWxkIGJlICJydW5uaW5nIikuCj4+PiAtIFdoZW4gb3JpZ2luIGFuZCBkZXN0aW5hdGlvbiBob3N0 cyBhcmUgd2l0aGluIHRoZSBzYW1lIHBvb2wuCj4+Pgo+PiBvZmZsaW5lIGNyb29zLXBvb2wgbWln cmF0aW9uIGlzIG5vdCBzdXBwb3J0ZWQsIEFGQUlLLiBTYWQsIHllcC4KPj4KPj4gRm9yIGluLXBv b2wgbWlncmF0aW9uIHRoZXJlIGlzIHhlIHZkaS1wb29sLW1pZ3JhdGlvbiBjb21tYW5kLgo+IFlv dSBzaG91bGQgYmUgYWJsZSB0byBwZXJmb3JtIGFuIGluLXBvb2wgc3RvcmFnZSBtaWdyYXRpb24g dXNpbmcgJ3hlIHZtLW1pZ3JhdGUnLCB3aGVuIHlvdSBzcGVjaWZ5IHRoZSByZW1vdGUtbWFzdGVy L3JlbW90ZS11c2VybmFtZS9yZW1vdGUtcGFzc3dvcmQgcGFyYW1ldGVycyBmb3IgdGhlIG1hc3Rl ciBvZiB0aGUgc2FtZSBwb29sLiBBIGJpdCB3ZWlyZCwgYnV0IGl0IHNob3VsZCB3b3JrIHRoYXQg d2F54oCmCj4KPiBDaGVlcnMsCj4gUm9iCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4u b3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBp Cg== From xen-api-bounces@lists.xen.org Thu Jan 03 13:52:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 13:52:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqlDx-0002jx-VP; Thu, 03 Jan 2013 13:52:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqlDw-0002jq-4a for xen-api@lists.xen.org; Thu, 03 Jan 2013 13:52:44 +0000 Received: from [85.158.143.35:47968] by server-3.bemta-4.messagelabs.com id 53/7B-18211-B2D85E05; Thu, 03 Jan 2013 13:52:43 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1357221162!12444358!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27919 invoked from network); 3 Jan 2013 13:52:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 13:52:42 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="433506" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 13:52:29 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 13:52:29 +0000 From: Rob Hoes To: George Shuklin Date: Thu, 3 Jan 2013 13:52:28 +0000 Thread-Topic: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs Thread-Index: Ac3puZHQIMwo2WP1Qe2j3JQxOGxJ5g== Message-ID: <4D9EDCD3-554E-4EA6-A7FD-2E4140DC38F1@citrix.com> References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> <50E58BF1.1040601@gmail.com> In-Reply-To: <50E58BF1.1040601@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VGhlIG1hc3RlciBtdXN0IGFsd2F5cyBiZSBpbnZvbHZlZCB0byBzZXQgdGhpbmdzIHVwLCBiZWNh dXNlIHRoZSBtYXN0ZXIgaXMgcmVzcG9uc2libGUgZm9yIGZvcndhcmRpbmcgQVBJIGNhbGxzIHRv IHNsYXZlcyBpbiB0aGUgcG9vbCwgYW5kIHRoZSBtYXN0ZXIgcnVucyB0aGUgZGF0YWJhc2Ugd2l0 aCBhbGwgdGhlIFZNIG1ldGFkYXRhLiBUaGUgYWN0dWFsIG1pZ3JhdGlvbiB3aWxsIHRoZW4gaGFw cGVuIGJldHdlZW4gdGhlIHNlbmRlciBhbmQgdGhlIHJlY2VpdmVyIGRpcmVjdGx5Lg0KDQpPbiAz IEphbiAyMDEzLCBhdCAxMzo0NywgR2VvcmdlIFNodWtsaW4gPGdlb3JnZS5zaHVrbGluQGdtYWls LmNvbT4gd3JvdGU6DQoNCj4gSXMgdGhhdCByaWdodCB3YXkgdG8gbWlncmF0ZT8NCj4gDQo+IEkg bWVhbiwgaWYgbWFzdGVyIGhhZCBubyBhY2Nlc3MgdG8gZGVzaWduYXRpb24gU1IsIGhvdyBtaWdy YXRpb24gd2lsbCB3b3Jrcz8NCj4gDQo+IDAzLjAxLjIwMTMgMTY6MzYsIFJvYiBIb2VzINC/0LjR iNC10YI6DQo+PiBPbiAzIEphbiAyMDEzLCBhdCAwMzoxOSwgR2VvcmdlIFNodWtsaW4gPGdlb3Jn ZS5zaHVrbGluQGdtYWlsLmNvbT4gd3JvdGU6DQo+Pj4+IFN0aWxsIG5vdCBjbGVhciBob3cgdG8g bWlncmF0ZSBWTSdzIGluIHRoZSBmb2xsb3dpbmcgY2FzZXM6DQo+Pj4+IC0gV2hlbiBWTSBpcyBu b3Qgb25saW5lICh2bS1taWdyYXRlIGluc2lzdHMgaXQgc2hvdWxkIGJlICJydW5uaW5nIikuDQo+ Pj4+IC0gV2hlbiBvcmlnaW4gYW5kIGRlc3RpbmF0aW9uIGhvc3RzIGFyZSB3aXRoaW4gdGhlIHNh bWUgcG9vbC4NCj4+Pj4gDQo+Pj4gb2ZmbGluZSBjcm9vcy1wb29sIG1pZ3JhdGlvbiBpcyBub3Qg c3VwcG9ydGVkLCBBRkFJSy4gU2FkLCB5ZXAuDQo+Pj4gDQo+Pj4gRm9yIGluLXBvb2wgbWlncmF0 aW9uIHRoZXJlIGlzIHhlIHZkaS1wb29sLW1pZ3JhdGlvbiBjb21tYW5kLg0KPj4gWW91IHNob3Vs ZCBiZSBhYmxlIHRvIHBlcmZvcm0gYW4gaW4tcG9vbCBzdG9yYWdlIG1pZ3JhdGlvbiB1c2luZyAn eGUgdm0tbWlncmF0ZScsIHdoZW4geW91IHNwZWNpZnkgdGhlIHJlbW90ZS1tYXN0ZXIvcmVtb3Rl LXVzZXJuYW1lL3JlbW90ZS1wYXNzd29yZCBwYXJhbWV0ZXJzIGZvciB0aGUgbWFzdGVyIG9mIHRo ZSBzYW1lIHBvb2wuIEEgYml0IHdlaXJkLCBidXQgaXQgc2hvdWxkIHdvcmsgdGhhdCB3YXnigKYN Cj4+IA0KPj4gQ2hlZXJzLA0KPj4gUm9iDQo+IA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hl bi1hcGkK From xen-api-bounces@lists.xen.org Thu Jan 03 13:52:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 13:52:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqlDx-0002jx-VP; Thu, 03 Jan 2013 13:52:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqlDw-0002jq-4a for xen-api@lists.xen.org; Thu, 03 Jan 2013 13:52:44 +0000 Received: from [85.158.143.35:47968] by server-3.bemta-4.messagelabs.com id 53/7B-18211-B2D85E05; Thu, 03 Jan 2013 13:52:43 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1357221162!12444358!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27919 invoked from network); 3 Jan 2013 13:52:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 13:52:42 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="433506" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 13:52:29 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 3 Jan 2013 13:52:29 +0000 From: Rob Hoes To: George Shuklin Date: Thu, 3 Jan 2013 13:52:28 +0000 Thread-Topic: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs Thread-Index: Ac3puZHQIMwo2WP1Qe2j3JQxOGxJ5g== Message-ID: <4D9EDCD3-554E-4EA6-A7FD-2E4140DC38F1@citrix.com> References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> <50E58BF1.1040601@gmail.com> In-Reply-To: <50E58BF1.1040601@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VGhlIG1hc3RlciBtdXN0IGFsd2F5cyBiZSBpbnZvbHZlZCB0byBzZXQgdGhpbmdzIHVwLCBiZWNh dXNlIHRoZSBtYXN0ZXIgaXMgcmVzcG9uc2libGUgZm9yIGZvcndhcmRpbmcgQVBJIGNhbGxzIHRv IHNsYXZlcyBpbiB0aGUgcG9vbCwgYW5kIHRoZSBtYXN0ZXIgcnVucyB0aGUgZGF0YWJhc2Ugd2l0 aCBhbGwgdGhlIFZNIG1ldGFkYXRhLiBUaGUgYWN0dWFsIG1pZ3JhdGlvbiB3aWxsIHRoZW4gaGFw cGVuIGJldHdlZW4gdGhlIHNlbmRlciBhbmQgdGhlIHJlY2VpdmVyIGRpcmVjdGx5Lg0KDQpPbiAz IEphbiAyMDEzLCBhdCAxMzo0NywgR2VvcmdlIFNodWtsaW4gPGdlb3JnZS5zaHVrbGluQGdtYWls LmNvbT4gd3JvdGU6DQoNCj4gSXMgdGhhdCByaWdodCB3YXkgdG8gbWlncmF0ZT8NCj4gDQo+IEkg bWVhbiwgaWYgbWFzdGVyIGhhZCBubyBhY2Nlc3MgdG8gZGVzaWduYXRpb24gU1IsIGhvdyBtaWdy YXRpb24gd2lsbCB3b3Jrcz8NCj4gDQo+IDAzLjAxLjIwMTMgMTY6MzYsIFJvYiBIb2VzINC/0LjR iNC10YI6DQo+PiBPbiAzIEphbiAyMDEzLCBhdCAwMzoxOSwgR2VvcmdlIFNodWtsaW4gPGdlb3Jn ZS5zaHVrbGluQGdtYWlsLmNvbT4gd3JvdGU6DQo+Pj4+IFN0aWxsIG5vdCBjbGVhciBob3cgdG8g bWlncmF0ZSBWTSdzIGluIHRoZSBmb2xsb3dpbmcgY2FzZXM6DQo+Pj4+IC0gV2hlbiBWTSBpcyBu b3Qgb25saW5lICh2bS1taWdyYXRlIGluc2lzdHMgaXQgc2hvdWxkIGJlICJydW5uaW5nIikuDQo+ Pj4+IC0gV2hlbiBvcmlnaW4gYW5kIGRlc3RpbmF0aW9uIGhvc3RzIGFyZSB3aXRoaW4gdGhlIHNh bWUgcG9vbC4NCj4+Pj4gDQo+Pj4gb2ZmbGluZSBjcm9vcy1wb29sIG1pZ3JhdGlvbiBpcyBub3Qg c3VwcG9ydGVkLCBBRkFJSy4gU2FkLCB5ZXAuDQo+Pj4gDQo+Pj4gRm9yIGluLXBvb2wgbWlncmF0 aW9uIHRoZXJlIGlzIHhlIHZkaS1wb29sLW1pZ3JhdGlvbiBjb21tYW5kLg0KPj4gWW91IHNob3Vs ZCBiZSBhYmxlIHRvIHBlcmZvcm0gYW4gaW4tcG9vbCBzdG9yYWdlIG1pZ3JhdGlvbiB1c2luZyAn eGUgdm0tbWlncmF0ZScsIHdoZW4geW91IHNwZWNpZnkgdGhlIHJlbW90ZS1tYXN0ZXIvcmVtb3Rl LXVzZXJuYW1lL3JlbW90ZS1wYXNzd29yZCBwYXJhbWV0ZXJzIGZvciB0aGUgbWFzdGVyIG9mIHRo ZSBzYW1lIHBvb2wuIEEgYml0IHdlaXJkLCBidXQgaXQgc2hvdWxkIHdvcmsgdGhhdCB3YXnigKYN Cj4+IA0KPj4gQ2hlZXJzLA0KPj4gUm9iDQo+IA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hl bi1hcGkK From xen-api-bounces@lists.xen.org Thu Jan 03 14:46:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 14:46:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqm3n-0003V5-TI; Thu, 03 Jan 2013 14:46:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqm3m-0003V0-6E for xen-api@lists.xen.org; Thu, 03 Jan 2013 14:46:18 +0000 Received: from [85.158.137.99:47666] by server-11.bemta-3.messagelabs.com id 12/B8-13335-9B995E05; Thu, 03 Jan 2013 14:46:17 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1357224374!16593425!1 X-Originating-IP: [207.126.144.149] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28879 invoked from network); 3 Jan 2013 14:46:15 -0000 Received: from eu1sys200aog120.obsmtp.com (HELO eu1sys200aog120.obsmtp.com) (207.126.144.149) by server-6.tower-217.messagelabs.com with SMTP; 3 Jan 2013 14:46:15 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob120.postini.com ([207.126.147.11]) with SMTP ID DSNKUOWZslhju3TZgYXPewsk6sP9S9zWcDXD@postini.com; Thu, 03 Jan 2013 14:46:14 UTC Received: from lonwexhtca01.uk.futurenet.com (lonwexhtca01.uk.futurenet.com [172.23.130.5]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id B17007F4475; Thu, 3 Jan 2013 14:46:10 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by lonwexhtca01.uk.futurenet.com ([172.23.130.5]) with mapi; Thu, 3 Jan 2013 14:46:10 +0000 From: Dave Avent To: Dave Scott Date: Thu, 3 Jan 2013 14:46:09 +0000 Thread-Topic: XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3pwRGRH4TzBViWTBKpza+GWuec8A== Message-ID: References: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBDE@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21012F0D72EBDE@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Dave, On 3 Jan 2013, at 12:05, Dave Scott wrote: > Hi, > = > That's very strange. Could it be the size of the "VM.get_all_records" res= ponse is too big to be sent properly? Do other APIs which generate less tra= ffic (e.g. "Pool.get_all_records") always work, or do they sometimes fail t= oo? I have only traced it to VM.get_all_records=85.so far. Also, this is a vani= lla install of 1.6 so just the standard list of Templates installed. > = > Perhaps you've got a thread or fd leak? If you run "top" and look at the = virtual size of the "xapi" process, is it very large? Virtual: 256M, RSS: 28M > Maybe there are too many threads and it's blocking? If it looks very larg= e (more than 1 or 2 GB) then I'd be interested to see how many file descrip= tors are open (look in /proc//fd -- but make sure you select the child= pid since the parent is a much smaller watchdog process). It might be that= some client(s) are keeping connections open for longer than expected and c= urrently xapi uses a thread-per-connection model. # ls -l /proc//fd | wc -l 28 > = > Does restarting the xapi process cause the problem to go away (even if te= mporarily)? This had no affect at all. However, restarting xapi-templatescan did return= this: updateXapiTemplates.py:MUTTER:reading DB from /opt/xensource/guest-template= s/dbcache updateXapiTemplates.py:MUTTER:DB does not exist at /opt/xensource/guest-tem= plates/dbcache updateXapiTemplates.py:MUTTER:Rebuilding database.. Traceback (most recent call last): File "/opt/xensource/bin/updateXapiTemplates.py", line 357, in ? commitDatabase() File "/opt/xensource/bin/updateXapiTemplates.py", line 331, in commitDatab= ase foo=3Dopen(filename,'w') IOError: [Errno 2] No such file or directory: '/opt/xensource/guest-templat= es/dbcache.new' At the point of the problem I have no Guest Templates (just the pre-install= ed ones) so this may be expected but thought it was worth mentioning. Dave > = > Cheers, > Dave > = >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >> bounces@lists.xen.org] On Behalf Of Dave Avent >> Sent: 03 January 2013 11:14 AM >> To: xen-api@lists.xen.org >> Subject: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging >> = >> All, >> = >> I have been playing with Xen Cloud Platform 1.6 in the lab and have been >> noticing some strange behaviour when using the API to drive it. Using >> XenCenter worked some of the time but then appeared to freeze, not >> refresh and then on re-connecting get stuck on "Synchronising". I put th= is >> down to the client software and switched instead to writing my own client >> interface using Ruby and the FOG libraries. This worked well but I start= ed >> seeing the same lock-ups. After digging about I realised that it always = locks >> up at the same point namely the VM.get_all_records call. >> = >> The call is received as the xensource.log shows: >> = >> xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records >> D:7f14fc2bea45|api_readonly] VM.get_all_records >> = >> But nothing is received and the clients TCP connection times out. >> = >> This problem happens for well over 50% of the calls made to the API so I= am >> interested to know if anyone else is having this problem? >> = >> Regards, >> = >> Dave-- >> Future Publishing Limited (registered company number 2008885) is a wholly >> owned subsidiary of Future plc (registered company number 3757874), both >> of which are incorporated in England and Wales and share the same >> registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. >> = >> This email and any files transmitted with it are confidential and intend= ed >> solely for the use of the individual or entity to which they are address= ed. If >> you have received this email in error please reply to this email and then >> delete it. Please note that any views or opinions presented in this emai= l are >> solely those of the author and do not necessarily represent those of Fut= ure. >> = >> The recipient should check this email and any attachments for the presen= ce >> of viruses. Future accepts no liability for any damage caused by any vir= us >> transmitted by this email. >> = >> Future may regularly and randomly monitor outgoing and incoming emails >> and other telecommunications on its email and telecommunications >> systems. By replying to this email you give your consent to such monitor= ing. >> = >> ***** >> Save resources: think before you print. >> = >> = >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api -- = Future Publishing Limited (registered company number 2008885) is a wholly o= wned subsidiary of Future plc (registered company number 3757874), both of = which are incorporated in England and Wales and share the same registered a= ddress at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended = solely for the use of the individual or entity to which they are addressed.= If you have received this email in error please reply to this email and th= en delete it. Please note that any views or opinions presented in this emai= l are solely those of the author and do not necessarily represent those of = Future. The recipient should check this email and any attachments for the presence = of viruses. Future accepts no liability for any damage caused by any virus = transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and = other telecommunications on its email and telecommunications systems. By re= plying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 14:46:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 14:46:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqm3n-0003V5-TI; Thu, 03 Jan 2013 14:46:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqm3m-0003V0-6E for xen-api@lists.xen.org; Thu, 03 Jan 2013 14:46:18 +0000 Received: from [85.158.137.99:47666] by server-11.bemta-3.messagelabs.com id 12/B8-13335-9B995E05; Thu, 03 Jan 2013 14:46:17 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1357224374!16593425!1 X-Originating-IP: [207.126.144.149] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28879 invoked from network); 3 Jan 2013 14:46:15 -0000 Received: from eu1sys200aog120.obsmtp.com (HELO eu1sys200aog120.obsmtp.com) (207.126.144.149) by server-6.tower-217.messagelabs.com with SMTP; 3 Jan 2013 14:46:15 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob120.postini.com ([207.126.147.11]) with SMTP ID DSNKUOWZslhju3TZgYXPewsk6sP9S9zWcDXD@postini.com; Thu, 03 Jan 2013 14:46:14 UTC Received: from lonwexhtca01.uk.futurenet.com (lonwexhtca01.uk.futurenet.com [172.23.130.5]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id B17007F4475; Thu, 3 Jan 2013 14:46:10 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by lonwexhtca01.uk.futurenet.com ([172.23.130.5]) with mapi; Thu, 3 Jan 2013 14:46:10 +0000 From: Dave Avent To: Dave Scott Date: Thu, 3 Jan 2013 14:46:09 +0000 Thread-Topic: XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3pwRGRH4TzBViWTBKpza+GWuec8A== Message-ID: References: <8FCF98FF-DFAB-453F-8812-07391063F919@futurenet.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBDE@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21012F0D72EBDE@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Dave, On 3 Jan 2013, at 12:05, Dave Scott wrote: > Hi, > = > That's very strange. Could it be the size of the "VM.get_all_records" res= ponse is too big to be sent properly? Do other APIs which generate less tra= ffic (e.g. "Pool.get_all_records") always work, or do they sometimes fail t= oo? I have only traced it to VM.get_all_records=85.so far. Also, this is a vani= lla install of 1.6 so just the standard list of Templates installed. > = > Perhaps you've got a thread or fd leak? If you run "top" and look at the = virtual size of the "xapi" process, is it very large? Virtual: 256M, RSS: 28M > Maybe there are too many threads and it's blocking? If it looks very larg= e (more than 1 or 2 GB) then I'd be interested to see how many file descrip= tors are open (look in /proc//fd -- but make sure you select the child= pid since the parent is a much smaller watchdog process). It might be that= some client(s) are keeping connections open for longer than expected and c= urrently xapi uses a thread-per-connection model. # ls -l /proc//fd | wc -l 28 > = > Does restarting the xapi process cause the problem to go away (even if te= mporarily)? This had no affect at all. However, restarting xapi-templatescan did return= this: updateXapiTemplates.py:MUTTER:reading DB from /opt/xensource/guest-template= s/dbcache updateXapiTemplates.py:MUTTER:DB does not exist at /opt/xensource/guest-tem= plates/dbcache updateXapiTemplates.py:MUTTER:Rebuilding database.. Traceback (most recent call last): File "/opt/xensource/bin/updateXapiTemplates.py", line 357, in ? commitDatabase() File "/opt/xensource/bin/updateXapiTemplates.py", line 331, in commitDatab= ase foo=3Dopen(filename,'w') IOError: [Errno 2] No such file or directory: '/opt/xensource/guest-templat= es/dbcache.new' At the point of the problem I have no Guest Templates (just the pre-install= ed ones) so this may be expected but thought it was worth mentioning. Dave > = > Cheers, > Dave > = >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >> bounces@lists.xen.org] On Behalf Of Dave Avent >> Sent: 03 January 2013 11:14 AM >> To: xen-api@lists.xen.org >> Subject: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging >> = >> All, >> = >> I have been playing with Xen Cloud Platform 1.6 in the lab and have been >> noticing some strange behaviour when using the API to drive it. Using >> XenCenter worked some of the time but then appeared to freeze, not >> refresh and then on re-connecting get stuck on "Synchronising". I put th= is >> down to the client software and switched instead to writing my own client >> interface using Ruby and the FOG libraries. This worked well but I start= ed >> seeing the same lock-ups. After digging about I realised that it always = locks >> up at the same point namely the VM.get_all_records call. >> = >> The call is received as the xensource.log shows: >> = >> xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records >> D:7f14fc2bea45|api_readonly] VM.get_all_records >> = >> But nothing is received and the clients TCP connection times out. >> = >> This problem happens for well over 50% of the calls made to the API so I= am >> interested to know if anyone else is having this problem? >> = >> Regards, >> = >> Dave-- >> Future Publishing Limited (registered company number 2008885) is a wholly >> owned subsidiary of Future plc (registered company number 3757874), both >> of which are incorporated in England and Wales and share the same >> registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. >> = >> This email and any files transmitted with it are confidential and intend= ed >> solely for the use of the individual or entity to which they are address= ed. If >> you have received this email in error please reply to this email and then >> delete it. Please note that any views or opinions presented in this emai= l are >> solely those of the author and do not necessarily represent those of Fut= ure. >> = >> The recipient should check this email and any attachments for the presen= ce >> of viruses. Future accepts no liability for any damage caused by any vir= us >> transmitted by this email. >> = >> Future may regularly and randomly monitor outgoing and incoming emails >> and other telecommunications on its email and telecommunications >> systems. By replying to this email you give your consent to such monitor= ing. >> = >> ***** >> Save resources: think before you print. >> = >> = >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api -- = Future Publishing Limited (registered company number 2008885) is a wholly o= wned subsidiary of Future plc (registered company number 3757874), both of = which are incorporated in England and Wales and share the same registered a= ddress at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended = solely for the use of the individual or entity to which they are addressed.= If you have received this email in error please reply to this email and th= en delete it. Please note that any views or opinions presented in this emai= l are solely those of the author and do not necessarily represent those of = Future. The recipient should check this email and any attachments for the presence = of viruses. Future accepts no liability for any damage caused by any virus = transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and = other telecommunications on its email and telecommunications systems. By re= plying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 15:07:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:07:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmOS-0003kn-Kz; Thu, 03 Jan 2013 15:07:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmOR-0003ki-2g for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:07:39 +0000 Received: from [193.109.254.147:17726] by server-3.bemta-14.messagelabs.com id 71/7C-26055-ABE95E05; Thu, 03 Jan 2013 15:07:38 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357225635!11939246!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=1.8 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30453 invoked from network); 3 Jan 2013 15:07:16 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:07:16 -0000 Received: by mail-la0-f43.google.com with SMTP id eg20so7921200lab.2 for ; Thu, 03 Jan 2013 07:07:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=oVQX0CaZRt0a0AIz358eXhV37ZP25qChmCclFeDM4q8=; b=r1w0zDke62UxGQ/okSAAQGAnI5PtR2JBGWiHorytXqzoWjbDxe0R1fQQEiKkhsD2BZ bfoW6otcokAR+SdUwPVH3ChUUieZeXgeDyijzSdgmxHJA9z7N1/BjIpIV/DbLaMw7gzd zrLyl/pfM6DU1i+UkrTETdEAFWavTMdG6FkE2mi8MPrWGTp5LM4P3yNuTV5dikrypF3n C7VrW3nxUaBloHeMHElqiR3YvCICRFzPTC14rZayOfnzwGCN9wEX0IQ5TwtqRMvwbi28 EUgI2sXLtB82nRb/0VQKtRbhuN5ebjUzYzXfvDLc2dGtwV4saGGvIfuuiAfzzYtSDL/T Y5aw== X-Received: by 10.152.110.229 with SMTP id id5mr47057765lab.36.1357225634715; Thu, 03 Jan 2013 07:07:14 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id ee5sm17083011lbb.14.2013.01.03.07.07.14 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 07:07:14 -0800 (PST) Message-ID: <50E59EA1.3050706@gmail.com> Date: Thu, 03 Jan 2013 19:07:13 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Good day. Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown time, reason and initiator. Those was extremely useful metrics and it's really sad to see lack of them in new version. In XCP 1.1 they was placed in other-config: last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart; last_shutdown_initiator: external; last_shutdown_reason: rebooted; In XCP 1.6 nothing like this is in other-config. Is those fields disappear completely or I just miss them? Thanks. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 15:07:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:07:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmOS-0003kn-Kz; Thu, 03 Jan 2013 15:07:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmOR-0003ki-2g for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:07:39 +0000 Received: from [193.109.254.147:17726] by server-3.bemta-14.messagelabs.com id 71/7C-26055-ABE95E05; Thu, 03 Jan 2013 15:07:38 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357225635!11939246!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=1.8 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30453 invoked from network); 3 Jan 2013 15:07:16 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:07:16 -0000 Received: by mail-la0-f43.google.com with SMTP id eg20so7921200lab.2 for ; Thu, 03 Jan 2013 07:07:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=oVQX0CaZRt0a0AIz358eXhV37ZP25qChmCclFeDM4q8=; b=r1w0zDke62UxGQ/okSAAQGAnI5PtR2JBGWiHorytXqzoWjbDxe0R1fQQEiKkhsD2BZ bfoW6otcokAR+SdUwPVH3ChUUieZeXgeDyijzSdgmxHJA9z7N1/BjIpIV/DbLaMw7gzd zrLyl/pfM6DU1i+UkrTETdEAFWavTMdG6FkE2mi8MPrWGTp5LM4P3yNuTV5dikrypF3n C7VrW3nxUaBloHeMHElqiR3YvCICRFzPTC14rZayOfnzwGCN9wEX0IQ5TwtqRMvwbi28 EUgI2sXLtB82nRb/0VQKtRbhuN5ebjUzYzXfvDLc2dGtwV4saGGvIfuuiAfzzYtSDL/T Y5aw== X-Received: by 10.152.110.229 with SMTP id id5mr47057765lab.36.1357225634715; Thu, 03 Jan 2013 07:07:14 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id ee5sm17083011lbb.14.2013.01.03.07.07.14 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 07:07:14 -0800 (PST) Message-ID: <50E59EA1.3050706@gmail.com> Date: Thu, 03 Jan 2013 19:07:13 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Good day. Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown time, reason and initiator. Those was extremely useful metrics and it's really sad to see lack of them in new version. In XCP 1.1 they was placed in other-config: last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart; last_shutdown_initiator: external; last_shutdown_reason: rebooted; In XCP 1.6 nothing like this is in other-config. Is those fields disappear completely or I just miss them? Thanks. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 15:09:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:09:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmQ1-0003n1-Ty; Thu, 03 Jan 2013 15:09:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmQ0-0003mu-1y for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:09:16 +0000 Received: from [85.158.137.99:8266] by server-12.bemta-3.messagelabs.com id 61/D2-27559-B1F95E05; Thu, 03 Jan 2013 15:09:15 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1357225754!17459849!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=4.3 required=7.0 tests=HTML_60_70, HTML_IMAGE_ONLY_12,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15950 invoked from network); 3 Jan 2013 15:09:14 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:09:14 -0000 Received: by mail-la0-f49.google.com with SMTP id fk20so7882087lab.22 for ; Thu, 03 Jan 2013 07:09:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=8qR6iu+efVpZpN4nchIkxK8ko2UEI2S/1oUToBhLHKY=; b=bB42RdkADdyuHFRRWzikipnsDkNwx9KvyoaO3A+AaC1/FO1c+xfA9Gi7XhM0I/78xJ 9VBiHFfJlmy/Yr4X6TKwHJmBtVGJwSNDqfMLur7J6NMlFoY/2Oj995ktPhFGLJpatyI1 POFiYdSZSiXrg8vyF5PNgwZHYWrnxruu9r0KJ6YAXFgnvSxCqn/K5IDAJdYEcBK3Y1Dk 5fgR3FnhJB742kqNfklYEqXhDThdYIp0N07X4vV7a4hn/R+8b60Q3f4L/q4TC1S/mTMg lQ+oRFsYXAUdx4TykOga7YmmLYdAsl4qwmQa4/qGSAyd4lULScCVhCzi9ToOkBHR1/gX H0WQ== X-Received: by 10.152.105.203 with SMTP id go11mr46800861lab.53.1357225753873; Thu, 03 Jan 2013 07:09:13 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id if8sm18505030lab.1.2013.01.03.07.09.12 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 07:09:13 -0800 (PST) Message-ID: <50E59F18.5040807@gmail.com> Date: Thu, 03 Jan 2013 19:09:12 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: reply+i-9486454-9bc03443a56d79ce349afc067a6c5ac8998c3338-652496@reply.github.com, "xen-api@lists.xen.org" References: In-Reply-To: Subject: Re: [Xen-API] [xen-api] maxmem_kb leak during migration (#955) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7464967419817206274==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7464967419817206274== Content-Type: multipart/alternative; boundary="------------070906070405050701000100" This is a multi-part message in MIME format. --------------070906070405050701000100 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 03.01.2013 19:07, jeromemaloberti пишет: May be just restore original value for domain after successfull migration? That change for new domain caused by xapi or by xenguest ? > > It is the same the same issue. Some additional memory is allocated for > the migration, but it is never reclaimed. The solution is not known > for now. > > — > Reply to this email directly or view it on GitHub > . > --------------070906070405050701000100 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
03.01.2013 19:07, jeromemaloberti пишет:

May be just restore original value for domain after successfull migration? That change for new domain caused by xapi or by xenguest ?

It is the same the same issue. Some additional memory is allocated for the migration, but it is never reclaimed. The solution is not known for now.

—
Reply to this email directly or view it on GitHub.


--------------070906070405050701000100-- --===============7464967419817206274== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7464967419817206274==-- From xen-api-bounces@lists.xen.org Thu Jan 03 15:09:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:09:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmQ1-0003n1-Ty; Thu, 03 Jan 2013 15:09:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmQ0-0003mu-1y for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:09:16 +0000 Received: from [85.158.137.99:8266] by server-12.bemta-3.messagelabs.com id 61/D2-27559-B1F95E05; Thu, 03 Jan 2013 15:09:15 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1357225754!17459849!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=4.3 required=7.0 tests=HTML_60_70, HTML_IMAGE_ONLY_12,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15950 invoked from network); 3 Jan 2013 15:09:14 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:09:14 -0000 Received: by mail-la0-f49.google.com with SMTP id fk20so7882087lab.22 for ; Thu, 03 Jan 2013 07:09:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=8qR6iu+efVpZpN4nchIkxK8ko2UEI2S/1oUToBhLHKY=; b=bB42RdkADdyuHFRRWzikipnsDkNwx9KvyoaO3A+AaC1/FO1c+xfA9Gi7XhM0I/78xJ 9VBiHFfJlmy/Yr4X6TKwHJmBtVGJwSNDqfMLur7J6NMlFoY/2Oj995ktPhFGLJpatyI1 POFiYdSZSiXrg8vyF5PNgwZHYWrnxruu9r0KJ6YAXFgnvSxCqn/K5IDAJdYEcBK3Y1Dk 5fgR3FnhJB742kqNfklYEqXhDThdYIp0N07X4vV7a4hn/R+8b60Q3f4L/q4TC1S/mTMg lQ+oRFsYXAUdx4TykOga7YmmLYdAsl4qwmQa4/qGSAyd4lULScCVhCzi9ToOkBHR1/gX H0WQ== X-Received: by 10.152.105.203 with SMTP id go11mr46800861lab.53.1357225753873; Thu, 03 Jan 2013 07:09:13 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id if8sm18505030lab.1.2013.01.03.07.09.12 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 07:09:13 -0800 (PST) Message-ID: <50E59F18.5040807@gmail.com> Date: Thu, 03 Jan 2013 19:09:12 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: reply+i-9486454-9bc03443a56d79ce349afc067a6c5ac8998c3338-652496@reply.github.com, "xen-api@lists.xen.org" References: In-Reply-To: Subject: Re: [Xen-API] [xen-api] maxmem_kb leak during migration (#955) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7464967419817206274==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7464967419817206274== Content-Type: multipart/alternative; boundary="------------070906070405050701000100" This is a multi-part message in MIME format. --------------070906070405050701000100 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 03.01.2013 19:07, jeromemaloberti пишет: May be just restore original value for domain after successfull migration? That change for new domain caused by xapi or by xenguest ? > > It is the same the same issue. Some additional memory is allocated for > the migration, but it is never reclaimed. The solution is not known > for now. > > — > Reply to this email directly or view it on GitHub > . > --------------070906070405050701000100 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
03.01.2013 19:07, jeromemaloberti пишет:

May be just restore original value for domain after successfull migration? That change for new domain caused by xapi or by xenguest ?

It is the same the same issue. Some additional memory is allocated for the migration, but it is never reclaimed. The solution is not known for now.

—
Reply to this email directly or view it on GitHub.


--------------070906070405050701000100-- --===============7464967419817206274== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7464967419817206274==-- From xen-api-bounces@lists.xen.org Thu Jan 03 15:30:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:30:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqmkc-0004FS-Gs; Thu, 03 Jan 2013 15:30:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqmka-0004FM-ON for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:30:32 +0000 Received: from [85.158.143.35:13353] by server-2.bemta-4.messagelabs.com id 6C/C3-30861-814A5E05; Thu, 03 Jan 2013 15:30:32 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1357227029!14487804!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 337 invoked from network); 3 Jan 2013 15:30:30 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:30:30 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="437199" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 15:30:29 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 3 Jan 2013 15:30:28 +0000 From: Dave Scott To: 'George Shuklin' , "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 15:30:28 +0000 Thread-Topic: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator Thread-Index: Ac3pxGocLxYML9p5S+2SR8fusYzgEAAAopQQ Message-ID: <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> References: <50E59EA1.3050706@gmail.com> In-Reply-To: <50E59EA1.3050706@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi George, They weren't deliberately removed -- they were missed when we split xenopsd from xapi. I think they could probably be put back again. Perhaps we should make them first-class fields rather than other-config keys, to make sure they don't go missing again? Out of curiousity, what kind of thing did you use that information for? Thanks, Dave > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of George Shuklin > Sent: 03 January 2013 3:07 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator > > Good day. > > Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown > time, reason and initiator. Those was extremely useful metrics and it's > really sad to see lack of them in new version. > > In XCP 1.1 they was placed in other-config: > last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart; > last_shutdown_initiator: external; last_shutdown_reason: rebooted; > > In XCP 1.6 nothing like this is in other-config. > > Is those fields disappear completely or I just miss them? > > Thanks. > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 15:30:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:30:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqmkc-0004FS-Gs; Thu, 03 Jan 2013 15:30:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqmka-0004FM-ON for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:30:32 +0000 Received: from [85.158.143.35:13353] by server-2.bemta-4.messagelabs.com id 6C/C3-30861-814A5E05; Thu, 03 Jan 2013 15:30:32 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1357227029!14487804!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0MTQx\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 337 invoked from network); 3 Jan 2013 15:30:30 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:30:30 -0000 X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="437199" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Jan 2013 15:30:29 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 3 Jan 2013 15:30:28 +0000 From: Dave Scott To: 'George Shuklin' , "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 15:30:28 +0000 Thread-Topic: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator Thread-Index: Ac3pxGocLxYML9p5S+2SR8fusYzgEAAAopQQ Message-ID: <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> References: <50E59EA1.3050706@gmail.com> In-Reply-To: <50E59EA1.3050706@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi George, They weren't deliberately removed -- they were missed when we split xenopsd from xapi. I think they could probably be put back again. Perhaps we should make them first-class fields rather than other-config keys, to make sure they don't go missing again? Out of curiousity, what kind of thing did you use that information for? Thanks, Dave > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of George Shuklin > Sent: 03 January 2013 3:07 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator > > Good day. > > Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown > time, reason and initiator. Those was extremely useful metrics and it's > really sad to see lack of them in new version. > > In XCP 1.1 they was placed in other-config: > last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart; > last_shutdown_initiator: external; last_shutdown_reason: rebooted; > > In XCP 1.6 nothing like this is in other-config. > > Is those fields disappear completely or I just miss them? > > Thanks. > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 15:41:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:41:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmvP-000614-DT; Thu, 03 Jan 2013 15:41:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmvN-00060c-F0 for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:41:41 +0000 Received: from [85.158.137.99:41482] by server-10.bemta-3.messagelabs.com id AD/85-28305-4B6A5E05; Thu, 03 Jan 2013 15:41:40 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1357227699!17465140!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=3.0 required=7.0 tests=HTML_50_60, HTML_IMAGE_ONLY_20,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20321 invoked from network); 3 Jan 2013 15:41:39 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:41:39 -0000 Received: by mail-la0-f48.google.com with SMTP id ej20so8150752lab.35 for ; Thu, 03 Jan 2013 07:41:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=1UCNGs8tiqHxndIepEDIF9tQGw9WCOObDgJHDL9AEcs=; b=inIZ1K/Nv98jY+3G3jhpz3H6Q1O3BbTINBMVjAaQapbphcaC8SwD9Tb8nYoJrVjqQv RpPYBX6MQd9U6QCG6hDhVnb+naWmi2qJ1CCSiXM83EZwKVGAcHFCooPZDUq/BFTS3egV 9nWvleiWi+UQ0KAY5ij5SG1AtNxMQIDUDaVXQyesOyrbTRM2wMWSA1e8iJ6Hcm+4c6We DxVg6GqbEO7zY9D3gf7O6niodiB5C9uHvdmaQuR0hUSI1AUn5Dtwn+Yw09/2mPGQn3G1 hQJLwUnVt2HGxFqYXm1dhFFIseZZMSmXSHagpWlfbvjIkeaZJ2J/4+vbNQ59uf/uF2nG FNog== X-Received: by 10.152.132.69 with SMTP id os5mr46813187lab.15.1357227699086; Thu, 03 Jan 2013 07:41:39 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id tq10sm17943663lab.8.2013.01.03.07.41.38 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 07:41:38 -0800 (PST) Message-ID: <50E5A6B2.1060701@gmail.com> Date: Thu, 03 Jan 2013 19:41:38 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: reply+i-9486454-9bc03443a56d79ce349afc067a6c5ac8998c3338-652496@reply.github.com, "xen-api@lists.xen.org" References: In-Reply-To: Subject: Re: [Xen-API] [xen-api] maxmem_kb leak during migration (#955) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2110330032136540112==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2110330032136540112== Content-Type: multipart/alternative; boundary="------------040209030808090603070705" This is a multi-part message in MIME format. --------------040209030808090603070705 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit It's not the memory, actually, but maxmem value (just an internal Xen limit for domain). That leak do not cause any direct damage (like 'out of memory' condition for host), but just raise a theoretical memory limit for domain, so domain can (if want) can ask for more, more and more memory beyond static-max limit of xapi for that VM. 03.01.2013 19:18, jeromemaloberti пишет: > > The memory is requested by xapi through squeezed, but then transfered > to xen. > Well, if you have an idea how to fix it, I will be very happy to test > it when I return from holiday :). > However, I don't know what xen is actually doing with the additional > memory. If it is just used during the migration, that's fine, but if > xen keeps using it after, it will be a problem. Any suggestion ? > > — > Reply to this email directly or view it on GitHub > . > --------------040209030808090603070705 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
It's not the memory, actually, but maxmem value (just an internal Xen limit for domain). That leak do not cause any direct damage (like 'out of memory' condition for host), but just raise a theoretical memory limit for domain, so domain can (if want) can ask for more, more and more memory beyond static-max limit of xapi for that VM.

03.01.2013 19:18, jeromemaloberti пишет:

The memory is requested by xapi through squeezed, but then transfered to xen.
Well, if you have an idea how to fix it, I will be very happy to test it when I return from holiday :).
However, I don't know what xen is actually doing with the additional memory. If it is just used during the migration, that's fine, but if xen keeps using it after, it will be a problem. Any suggestion ?

—
Reply to this email directly or view it on GitHub.


--------------040209030808090603070705-- --===============2110330032136540112== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2110330032136540112==-- From xen-api-bounces@lists.xen.org Thu Jan 03 15:41:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:41:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmvP-000614-DT; Thu, 03 Jan 2013 15:41:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqmvN-00060c-F0 for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:41:41 +0000 Received: from [85.158.137.99:41482] by server-10.bemta-3.messagelabs.com id AD/85-28305-4B6A5E05; Thu, 03 Jan 2013 15:41:40 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1357227699!17465140!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=3.0 required=7.0 tests=HTML_50_60, HTML_IMAGE_ONLY_20,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20321 invoked from network); 3 Jan 2013 15:41:39 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:41:39 -0000 Received: by mail-la0-f48.google.com with SMTP id ej20so8150752lab.35 for ; Thu, 03 Jan 2013 07:41:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=1UCNGs8tiqHxndIepEDIF9tQGw9WCOObDgJHDL9AEcs=; b=inIZ1K/Nv98jY+3G3jhpz3H6Q1O3BbTINBMVjAaQapbphcaC8SwD9Tb8nYoJrVjqQv RpPYBX6MQd9U6QCG6hDhVnb+naWmi2qJ1CCSiXM83EZwKVGAcHFCooPZDUq/BFTS3egV 9nWvleiWi+UQ0KAY5ij5SG1AtNxMQIDUDaVXQyesOyrbTRM2wMWSA1e8iJ6Hcm+4c6We DxVg6GqbEO7zY9D3gf7O6niodiB5C9uHvdmaQuR0hUSI1AUn5Dtwn+Yw09/2mPGQn3G1 hQJLwUnVt2HGxFqYXm1dhFFIseZZMSmXSHagpWlfbvjIkeaZJ2J/4+vbNQ59uf/uF2nG FNog== X-Received: by 10.152.132.69 with SMTP id os5mr46813187lab.15.1357227699086; Thu, 03 Jan 2013 07:41:39 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id tq10sm17943663lab.8.2013.01.03.07.41.38 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 07:41:38 -0800 (PST) Message-ID: <50E5A6B2.1060701@gmail.com> Date: Thu, 03 Jan 2013 19:41:38 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: reply+i-9486454-9bc03443a56d79ce349afc067a6c5ac8998c3338-652496@reply.github.com, "xen-api@lists.xen.org" References: In-Reply-To: Subject: Re: [Xen-API] [xen-api] maxmem_kb leak during migration (#955) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2110330032136540112==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2110330032136540112== Content-Type: multipart/alternative; boundary="------------040209030808090603070705" This is a multi-part message in MIME format. --------------040209030808090603070705 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit It's not the memory, actually, but maxmem value (just an internal Xen limit for domain). That leak do not cause any direct damage (like 'out of memory' condition for host), but just raise a theoretical memory limit for domain, so domain can (if want) can ask for more, more and more memory beyond static-max limit of xapi for that VM. 03.01.2013 19:18, jeromemaloberti пишет: > > The memory is requested by xapi through squeezed, but then transfered > to xen. > Well, if you have an idea how to fix it, I will be very happy to test > it when I return from holiday :). > However, I don't know what xen is actually doing with the additional > memory. If it is just used during the migration, that's fine, but if > xen keeps using it after, it will be a problem. Any suggestion ? > > — > Reply to this email directly or view it on GitHub > . > --------------040209030808090603070705 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
It's not the memory, actually, but maxmem value (just an internal Xen limit for domain). That leak do not cause any direct damage (like 'out of memory' condition for host), but just raise a theoretical memory limit for domain, so domain can (if want) can ask for more, more and more memory beyond static-max limit of xapi for that VM.

03.01.2013 19:18, jeromemaloberti пишет:

The memory is requested by xapi through squeezed, but then transfered to xen.
Well, if you have an idea how to fix it, I will be very happy to test it when I return from holiday :).
However, I don't know what xen is actually doing with the additional memory. If it is just used during the migration, that's fine, but if xen keeps using it after, it will be a problem. Any suggestion ?

—
Reply to this email directly or view it on GitHub.


--------------040209030808090603070705-- --===============2110330032136540112== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2110330032136540112==-- From xen-api-bounces@lists.xen.org Thu Jan 03 15:50:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:50:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqn41-0006jY-SQ; Thu, 03 Jan 2013 15:50:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqn40-0006jQ-Fx for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:50:36 +0000 Received: from [85.158.137.99:37623] by server-5.bemta-3.messagelabs.com id 7B/35-04992-BC8A5E05; Thu, 03 Jan 2013 15:50:35 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1357228234!16950895!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=1.8 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2816 invoked from network); 3 Jan 2013 15:50:34 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:50:34 -0000 Received: by mail-la0-f41.google.com with SMTP id em20so8158598lab.14 for ; Thu, 03 Jan 2013 07:49:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EKLaZpksK26Hq64J3w5naIxGxMd8jaLG2TBKmVUNs+U=; b=nBvflDnpKbmakS0S5llebw4eZuYQO5C4EQYOAk2D/a4tCvtSf2zD+7TrU569UCGIZr EbhI1Ki1KtQLxk/lUGzKm4AP4f+1CqJIrIWkdFWaoum3c8EOU472tFm9Ht8+pw1Adphy R/jNMVxJ8foCX3kK6Tig5xr8QVZlMWnkHSUWOfNo8rSJJPq28fknK7QYT6F6kWA5hunw rugvmIlJqsuS96Zh146o82ihBd08t6+X5S/4Iokf70yJc5/5brafVpFjETQuLWyqvRNf 8qsCLABhEE5lCxvjGDLR4p9blZOpAjBy49RqCbKPPHaB15zJCXAR3+2YrVbMAbxKcXRq ni1Q== X-Received: by 10.152.109.139 with SMTP id hs11mr47595052lab.13.1357228175116; Thu, 03 Jan 2013 07:49:35 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id ne2sm18542669lab.10.2013.01.03.07.49.34 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 07:49:34 -0800 (PST) Message-ID: <50E5A88D.5080001@gmail.com> Date: Thu, 03 Jan 2013 19:49:33 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Dave Scott References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WWVzLCBpZiBwb3NzaWJsZS4gVGhvc2UgZmllbGRzIHdhcyB2ZXJ5IHVzZWZ1bC4KClNvbWUgdXNl IGNhc2VzOgoKMSkgVGhleSBjYW4gYmUgdXNlZCB0byBkZXRlY3QgY3Jhc2hlZCBWTSdzLiBJZiBT UiBpcyBnb2luZyBvZmZsaW5lIGFuZCAKVk0gbW91bnQgb3B0aW9ucyBzYXlzIGVycm9ycz1wYW5p YywgVk0gaXMgY3Jhc2hpbmcuIFRob3NlIGZpZWxkcyBhbGxvd3MgCnZlcnkgZWFzeSB0byBzZWFy Y2ggZm9yIGNyYXNoZWQgVk0gYW5kIHJlc3RhcnQgdGhlbSBhZnRlciBTUiBpcyByZXBhaXJlZC4K MikgU3RhdHVzICdjcmFzaGVkJyBhbGxvd3MgdG8gYW5zd2VyIGN1c3RvbWVycyBhYm91dCByZWFz b24gd2h5IHRoZWlyIFZNIAp3YXMgcmVib290ZWQuCjMpIElmICdsYXN0X3NodXRkb3duX3JlYXNv bj1yZWJvb3RlZCcgYW5kIFZNIGlzIG5vdCBzdGFydGVkLCB0aGF0IGlzIApzaWduIG9mIHByb2Js ZW1zIChiYWQgYm9vdCBrZXJuZWwsIGdydWIgb3B0aW9ucyBvciBzb21ldGhpbmcgZWxzZSkuCjQp IGxhc3Rfc2h1dGRvd25fdGltZSBhbGxvd3MgbmF0aXZlIGFuZCB2ZXJ5IGludHVpdGl2ZSBzb3J0 aW5nIGtleSBmb3IgCmhhbHRlZCBWTSdzIChpZiB2bSB3YXMgaGFsdGVkIHJlY2VudGx5LCBpdCBj YW4gYmUgb24gdG9wLCBhbmQgdm0gd2l0aCAKc2h1dGRvd24gZGF0ZSB0d28geWVhcnMgYWdvIG5h dHVyYWxseSBjYW4gYmUgYXQgdGhlIGxpc3QgYm90dG9tKS4KNSkgV2hlbiBzb21lIGNvbXBsaWNh dGVkIHdvcmtzIHdpdGggaW5mcmFzdHJ1Y3R1cmUgYXJlIHBsYW5uZWQsIApsYXN0X3NodXRkb3du X3RpbWUgYWxsb3dzIHRvIHByZWRpY3QgaWYgVk0gd2lsbCBiZSBzdGFydGVkIHNvb24gb3Igbm90 IAooaWYgaXQgd2FzIGhhbHRlZCByZWNlbnRseSwgaXQgY2FuIGJlIHN0YXJ0ZWQgYXQgYW55IHRp bWUsIGlmIHZtIHdhcyAKaGFsdGVkIHR3byB3ZWVrcyBhZ28sIHRoZXJlIGlzIHZlcnkgbGl0dGxl IGNoYW5jZSBpdCB3aWxsIHN0YXJ0ZWQgaW4gCm5lYXIgMS0yLTMgaHJzLikKCgpXZSBkaXNwbGF5 cyB0aGVtIHRvIGNsaWVudCBpbiBtYW5hZ2VtZW50IGludGVyZmFjZQoKMDMuMDEuMjAxMyAxOToz MCwgRGF2ZSBTY290dCDQv9C40YjQtdGCOgo+IEhpIEdlb3JnZSwKPgo+IFRoZXkgd2VyZW4ndCBk ZWxpYmVyYXRlbHkgcmVtb3ZlZCAtLSB0aGV5IHdlcmUgbWlzc2VkIHdoZW4gd2Ugc3BsaXQgeGVu b3BzZCBmcm9tIHhhcGkuIEkgdGhpbmsgdGhleSBjb3VsZCBwcm9iYWJseSBiZSBwdXQgYmFjayBh Z2Fpbi4gUGVyaGFwcyB3ZSBzaG91bGQgbWFrZSB0aGVtIGZpcnN0LWNsYXNzIGZpZWxkcyByYXRo ZXIgdGhhbiBvdGhlci1jb25maWcga2V5cywgdG8gbWFrZSBzdXJlIHRoZXkgZG9uJ3QgZ28gbWlz c2luZyBhZ2Fpbj8KPgo+IE91dCBvZiBjdXJpb3VzaXR5LCB3aGF0IGtpbmQgb2YgdGhpbmcgZGlk IHlvdSB1c2UgdGhhdCBpbmZvcm1hdGlvbiBmb3I/Cj4KPiBUaGFua3MsCj4gRGF2ZQo+Cj4+IC0t LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tCj4+IEZyb206IHhlbi1hcGktYm91bmNlc0BsaXN0cy54 ZW4ub3JnIFttYWlsdG86eGVuLWFwaS0KPj4gYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbiBCZWhh bGYgT2YgR2VvcmdlIFNodWtsaW4KPj4gU2VudDogMDMgSmFudWFyeSAyMDEzIDM6MDcgUE0KPj4g VG86IHhlbi1hcGlAbGlzdHMueGVuLm9yZwo+PiBTdWJqZWN0OiBbWGVuLUFQSV0gWENQIDEuNjog bGFzdF9zaHV0ZG93biB0aW1lL3NodXRkb3duIHJlYXNvbi9pbml0aWF0b3IKPj4KPj4gR29vZCBk YXkuCj4+Cj4+IEZvdW5kIChzdWRkZW5seSkgdGhhdCBYQ1AgMS42IGRpZCBub3QgcHJvdmlkZXMg bWVydHJpY3MgYWJvdXQgc2h1dGRvd24KPj4gdGltZSwgcmVhc29uIGFuZCBpbml0aWF0b3IuIFRo b3NlIHdhcyBleHRyZW1lbHkgdXNlZnVsIG1ldHJpY3MgYW5kIGl0J3MKPj4gcmVhbGx5IHNhZCB0 byBzZWUgbGFjayBvZiB0aGVtIGluIG5ldyB2ZXJzaW9uLgo+Pgo+PiBJbiBYQ1AgMS4xIHRoZXkg d2FzIHBsYWNlZCBpbiBvdGhlci1jb25maWc6Cj4+IGxhc3Rfc2h1dGRvd25fdGltZTogMjAxMzAx MDJUMTU6NTY6NThaOyBsYXN0X3NodXRkb3duX2FjdGlvbjogUmVzdGFydDsKPj4gbGFzdF9zaHV0 ZG93bl9pbml0aWF0b3I6IGV4dGVybmFsOyBsYXN0X3NodXRkb3duX3JlYXNvbjogcmVib290ZWQ7 Cj4+Cj4+IEluIFhDUCAxLjYgbm90aGluZyBsaWtlIHRoaXMgaXMgaW4gb3RoZXItY29uZmlnLgo+ Pgo+PiBJcyB0aG9zZSBmaWVsZHMgZGlzYXBwZWFyIGNvbXBsZXRlbHkgb3IgSSBqdXN0IG1pc3Mg dGhlbT8KPj4KPj4gVGhhbmtzLgo+Pgo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwo+PiBYZW4tYXBpIG1haWxpbmcgbGlzdAo+PiBYZW4tYXBpQGxpc3Rz Lnhlbi5vcmcKPj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZv L3hlbi1hcGkKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f XwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Thu Jan 03 15:50:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:50:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqn41-0006jY-SQ; Thu, 03 Jan 2013 15:50:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqn40-0006jQ-Fx for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:50:36 +0000 Received: from [85.158.137.99:37623] by server-5.bemta-3.messagelabs.com id 7B/35-04992-BC8A5E05; Thu, 03 Jan 2013 15:50:35 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1357228234!16950895!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=1.8 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2816 invoked from network); 3 Jan 2013 15:50:34 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:50:34 -0000 Received: by mail-la0-f41.google.com with SMTP id em20so8158598lab.14 for ; Thu, 03 Jan 2013 07:49:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EKLaZpksK26Hq64J3w5naIxGxMd8jaLG2TBKmVUNs+U=; b=nBvflDnpKbmakS0S5llebw4eZuYQO5C4EQYOAk2D/a4tCvtSf2zD+7TrU569UCGIZr EbhI1Ki1KtQLxk/lUGzKm4AP4f+1CqJIrIWkdFWaoum3c8EOU472tFm9Ht8+pw1Adphy R/jNMVxJ8foCX3kK6Tig5xr8QVZlMWnkHSUWOfNo8rSJJPq28fknK7QYT6F6kWA5hunw rugvmIlJqsuS96Zh146o82ihBd08t6+X5S/4Iokf70yJc5/5brafVpFjETQuLWyqvRNf 8qsCLABhEE5lCxvjGDLR4p9blZOpAjBy49RqCbKPPHaB15zJCXAR3+2YrVbMAbxKcXRq ni1Q== X-Received: by 10.152.109.139 with SMTP id hs11mr47595052lab.13.1357228175116; Thu, 03 Jan 2013 07:49:35 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id ne2sm18542669lab.10.2013.01.03.07.49.34 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 07:49:34 -0800 (PST) Message-ID: <50E5A88D.5080001@gmail.com> Date: Thu, 03 Jan 2013 19:49:33 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Dave Scott References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WWVzLCBpZiBwb3NzaWJsZS4gVGhvc2UgZmllbGRzIHdhcyB2ZXJ5IHVzZWZ1bC4KClNvbWUgdXNl IGNhc2VzOgoKMSkgVGhleSBjYW4gYmUgdXNlZCB0byBkZXRlY3QgY3Jhc2hlZCBWTSdzLiBJZiBT UiBpcyBnb2luZyBvZmZsaW5lIGFuZCAKVk0gbW91bnQgb3B0aW9ucyBzYXlzIGVycm9ycz1wYW5p YywgVk0gaXMgY3Jhc2hpbmcuIFRob3NlIGZpZWxkcyBhbGxvd3MgCnZlcnkgZWFzeSB0byBzZWFy Y2ggZm9yIGNyYXNoZWQgVk0gYW5kIHJlc3RhcnQgdGhlbSBhZnRlciBTUiBpcyByZXBhaXJlZC4K MikgU3RhdHVzICdjcmFzaGVkJyBhbGxvd3MgdG8gYW5zd2VyIGN1c3RvbWVycyBhYm91dCByZWFz b24gd2h5IHRoZWlyIFZNIAp3YXMgcmVib290ZWQuCjMpIElmICdsYXN0X3NodXRkb3duX3JlYXNv bj1yZWJvb3RlZCcgYW5kIFZNIGlzIG5vdCBzdGFydGVkLCB0aGF0IGlzIApzaWduIG9mIHByb2Js ZW1zIChiYWQgYm9vdCBrZXJuZWwsIGdydWIgb3B0aW9ucyBvciBzb21ldGhpbmcgZWxzZSkuCjQp IGxhc3Rfc2h1dGRvd25fdGltZSBhbGxvd3MgbmF0aXZlIGFuZCB2ZXJ5IGludHVpdGl2ZSBzb3J0 aW5nIGtleSBmb3IgCmhhbHRlZCBWTSdzIChpZiB2bSB3YXMgaGFsdGVkIHJlY2VudGx5LCBpdCBj YW4gYmUgb24gdG9wLCBhbmQgdm0gd2l0aCAKc2h1dGRvd24gZGF0ZSB0d28geWVhcnMgYWdvIG5h dHVyYWxseSBjYW4gYmUgYXQgdGhlIGxpc3QgYm90dG9tKS4KNSkgV2hlbiBzb21lIGNvbXBsaWNh dGVkIHdvcmtzIHdpdGggaW5mcmFzdHJ1Y3R1cmUgYXJlIHBsYW5uZWQsIApsYXN0X3NodXRkb3du X3RpbWUgYWxsb3dzIHRvIHByZWRpY3QgaWYgVk0gd2lsbCBiZSBzdGFydGVkIHNvb24gb3Igbm90 IAooaWYgaXQgd2FzIGhhbHRlZCByZWNlbnRseSwgaXQgY2FuIGJlIHN0YXJ0ZWQgYXQgYW55IHRp bWUsIGlmIHZtIHdhcyAKaGFsdGVkIHR3byB3ZWVrcyBhZ28sIHRoZXJlIGlzIHZlcnkgbGl0dGxl IGNoYW5jZSBpdCB3aWxsIHN0YXJ0ZWQgaW4gCm5lYXIgMS0yLTMgaHJzLikKCgpXZSBkaXNwbGF5 cyB0aGVtIHRvIGNsaWVudCBpbiBtYW5hZ2VtZW50IGludGVyZmFjZQoKMDMuMDEuMjAxMyAxOToz MCwgRGF2ZSBTY290dCDQv9C40YjQtdGCOgo+IEhpIEdlb3JnZSwKPgo+IFRoZXkgd2VyZW4ndCBk ZWxpYmVyYXRlbHkgcmVtb3ZlZCAtLSB0aGV5IHdlcmUgbWlzc2VkIHdoZW4gd2Ugc3BsaXQgeGVu b3BzZCBmcm9tIHhhcGkuIEkgdGhpbmsgdGhleSBjb3VsZCBwcm9iYWJseSBiZSBwdXQgYmFjayBh Z2Fpbi4gUGVyaGFwcyB3ZSBzaG91bGQgbWFrZSB0aGVtIGZpcnN0LWNsYXNzIGZpZWxkcyByYXRo ZXIgdGhhbiBvdGhlci1jb25maWcga2V5cywgdG8gbWFrZSBzdXJlIHRoZXkgZG9uJ3QgZ28gbWlz c2luZyBhZ2Fpbj8KPgo+IE91dCBvZiBjdXJpb3VzaXR5LCB3aGF0IGtpbmQgb2YgdGhpbmcgZGlk IHlvdSB1c2UgdGhhdCBpbmZvcm1hdGlvbiBmb3I/Cj4KPiBUaGFua3MsCj4gRGF2ZQo+Cj4+IC0t LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tCj4+IEZyb206IHhlbi1hcGktYm91bmNlc0BsaXN0cy54 ZW4ub3JnIFttYWlsdG86eGVuLWFwaS0KPj4gYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbiBCZWhh bGYgT2YgR2VvcmdlIFNodWtsaW4KPj4gU2VudDogMDMgSmFudWFyeSAyMDEzIDM6MDcgUE0KPj4g VG86IHhlbi1hcGlAbGlzdHMueGVuLm9yZwo+PiBTdWJqZWN0OiBbWGVuLUFQSV0gWENQIDEuNjog bGFzdF9zaHV0ZG93biB0aW1lL3NodXRkb3duIHJlYXNvbi9pbml0aWF0b3IKPj4KPj4gR29vZCBk YXkuCj4+Cj4+IEZvdW5kIChzdWRkZW5seSkgdGhhdCBYQ1AgMS42IGRpZCBub3QgcHJvdmlkZXMg bWVydHJpY3MgYWJvdXQgc2h1dGRvd24KPj4gdGltZSwgcmVhc29uIGFuZCBpbml0aWF0b3IuIFRo b3NlIHdhcyBleHRyZW1lbHkgdXNlZnVsIG1ldHJpY3MgYW5kIGl0J3MKPj4gcmVhbGx5IHNhZCB0 byBzZWUgbGFjayBvZiB0aGVtIGluIG5ldyB2ZXJzaW9uLgo+Pgo+PiBJbiBYQ1AgMS4xIHRoZXkg d2FzIHBsYWNlZCBpbiBvdGhlci1jb25maWc6Cj4+IGxhc3Rfc2h1dGRvd25fdGltZTogMjAxMzAx MDJUMTU6NTY6NThaOyBsYXN0X3NodXRkb3duX2FjdGlvbjogUmVzdGFydDsKPj4gbGFzdF9zaHV0 ZG93bl9pbml0aWF0b3I6IGV4dGVybmFsOyBsYXN0X3NodXRkb3duX3JlYXNvbjogcmVib290ZWQ7 Cj4+Cj4+IEluIFhDUCAxLjYgbm90aGluZyBsaWtlIHRoaXMgaXMgaW4gb3RoZXItY29uZmlnLgo+ Pgo+PiBJcyB0aG9zZSBmaWVsZHMgZGlzYXBwZWFyIGNvbXBsZXRlbHkgb3IgSSBqdXN0IG1pc3Mg dGhlbT8KPj4KPj4gVGhhbmtzLgo+Pgo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwo+PiBYZW4tYXBpIG1haWxpbmcgbGlzdAo+PiBYZW4tYXBpQGxpc3Rz Lnhlbi5vcmcKPj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZv L3hlbi1hcGkKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f XwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Thu Jan 03 15:59:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:59:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqnCx-0007Ir-NJ; Thu, 03 Jan 2013 15:59:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TqnCw-0007Ig-D5 for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:59:50 +0000 Received: from [85.158.137.99:56130] by server-5.bemta-3.messagelabs.com id 78/91-04992-5FAA5E05; Thu, 03 Jan 2013 15:59:49 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1357228775!17468025!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4812 invoked from network); 3 Jan 2013 15:59:37 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:59:37 -0000 Received: by mail-qc0-f173.google.com with SMTP id b12so8032017qca.18 for ; Thu, 03 Jan 2013 07:59:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=e2m2WJLZTd+zGI1bQqVT/DCOn1in1KwLO5hEhGpQRTg=; b=OIR1qCCGve2YWaWjX5INPnJ2exkuvgc6najLEQ0r42G1tA9rDR8Vbj8dIn+/M4QKEx oCHVUd7H4R4a75KPUnhxlB145hprQo+zo9ldgw7u6Azy1cKWbwo9CUYPEMqhILmgQNCN SvFeLtqRhFDy+7MHynfmZg9R5K/90aC+IskGUUyNDJWo8GV0phbaD9WONxxQ06Eic80T 0ubMZU00BVSN6dVqapTnpR/xuxY2v9C3VZjyiV2fivS7WPnnS+L4pLXb63pin1X2HF+I NXUsaRYMgRHKp4lxtdDiOFFFtvzRVFRzdnRpz5d12J+FnM2t/cmtIOw8RC7Yj7b3tf1j VtQg== MIME-Version: 1.0 Received: by 10.49.12.138 with SMTP id y10mr32264908qeb.64.1357228775704; Thu, 03 Jan 2013 07:59:35 -0800 (PST) Received: by 10.229.17.19 with HTTP; Thu, 3 Jan 2013 07:59:35 -0800 (PST) In-Reply-To: <50E5A88D.5080001@gmail.com> References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> <50E5A88D.5080001@gmail.com> Date: Thu, 3 Jan 2013 21:29:35 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1049457846936904419==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1049457846936904419== Content-Type: multipart/alternative; boundary=047d7b6d88b20e080c04d26473f5 --047d7b6d88b20e080c04d26473f5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi George and Dave, Im not sure how but I do have all the parameters in VMs other-config [root@s3 ~]# xe vm-param-get param-name=3Dother-config uuid=3D1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490 auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiator: internal; last_shutdown_reason: halted; linux_template: true; rhel5: true; [root@s3 ~]# cat /etc/xensource-inventory BUILD_NUMBER=3D'61549c' DOM0_MEM=3D'752' MANAGEMENT_INTERFACE=3D'xenbr0' INSTALLATION_UUID=3D'5a17feac-b1bb-4e3d-ad26-374edb6414a0' COMPANY_NAME_SHORT=3D'xen.org' PLATFORM_NAME=3D'XCP' PLATFORM_VERSION=3D'1.6.8' KERNEL_VERSION=3D'2.6.32.43-0.4.1.xs1.6.08.734.170748xen' BRAND_CONSOLE=3D'a console' COMPANY_NAME=3D'xen.org' XEN_VERSION=3D'4.1.3' PRIMARY_DISK=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' CONTROL_DOMAIN_UUID=3D'9280c554-38f7-48e8-867b-9c183b2e8b59' MANAGEMENT_ADDRESS_TYPE=3D'IPv4' BACKUP_PARTITION=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2' INSTALLATION_DATE=3D'2012-11-10 06:30:22.102128' There is an ambiguity in last_shutdown_time but I think it is there because I imported it from XCP1.1. ( Notice the host installation data vs vm shutdown date ) Is it the case that *new* created VMs on XCP1.6 do not have "other-config" or did I miss anything ? We also use these fields and they are important for us hence if you confirm that they are removed in XCP1.6 then I would request to bring them back. Regards, Rushikesh On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin wr= ote: > Yes, if possible. Those fields was very useful. > > Some use cases: > > 1) They can be used to detect crashed VM's. If SR is going offline and VM > mount options says errors=3Dpanic, VM is crashing. Those fields allows ve= ry > easy to search for crashed VM and restart them after SR is repaired. > 2) Status 'crashed' allows to answer customers about reason why their VM > was rebooted. > 3) If 'last_shutdown_reason=3D**rebooted' and VM is not started, that is > sign of problems (bad boot kernel, grub options or something else). > 4) last_shutdown_time allows native and very intuitive sorting key for > halted VM's (if vm was halted recently, it can be on top, and vm with > shutdown date two years ago naturally can be at the list bottom). > 5) When some complicated works with infrastructure are planned, > last_shutdown_time allows to predict if VM will be started soon or not (i= f > it was halted recently, it can be started at any time, if vm was halted t= wo > weeks ago, there is very little chance it will started in near 1-2-3 hrs.= ) > > > We displays them to client in management interface > > 03.01.2013 19:30, Dave Scott =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > Hi George, >> >> They weren't deliberately removed -- they were missed when we split >> xenopsd from xapi. I think they could probably be put back again. Perhap= s >> we should make them first-class fields rather than other-config keys, to >> make sure they don't go missing again? >> >> Out of curiousity, what kind of thing did you use that information for? >> >> Thanks, >> Dave >> >> -----Original Message----- >>> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >>> bounces@lists.xen.org] On Behalf Of George Shuklin >>> Sent: 03 January 2013 3:07 PM >>> To: xen-api@lists.xen.org >>> Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiato= r >>> >>> Good day. >>> >>> Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown >>> time, reason and initiator. Those was extremely useful metrics and it's >>> really sad to see lack of them in new version. >>> >>> In XCP 1.1 they was placed in other-config: >>> last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart; >>> last_shutdown_initiator: external; last_shutdown_reason: rebooted; >>> >>> In XCP 1.6 nothing like this is in other-config. >>> >>> Is those fields disappear completely or I just miss them? >>> >>> Thanks. >>> >>> ______________________________**_________________ >>> Xen-api mailing list >>> Xen-api@lists.xen.org >>> http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api >>> >> > > ______________________________**_________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api > --047d7b6d88b20e080c04d26473f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi George and Dave,

= Im not sure how but I do have all the parameters in VMs other-config
[root@s3 ~]# xe vm-param-get param-name=3Dother-config uuid=3D1b5d4d31-e8f= f-0e1a-bfff-ad2d8a118490
auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-9= 15f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shut= down_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown= _initiator: internal; last_shutdown_reason: halted; linux_template: true; r= hel5: true;

[root@s3 ~]# cat /etc/xensource-inventory
BUILD_NUMBER=3D'61549= c'
DOM0_MEM=3D'752'
MANAGEMENT_INTERFACE=3D'xenbr0= 9;
INSTALLATION_UUID=3D'5a17feac-b1bb-4e3d-ad26-374edb6414a0'COMPANY_NAME_SHORT=3D'xen.org'
PLATFORM_NAME=3D'XCP'
PLATFORM_VERSION=3D'1.6.8'
KERN= EL_VERSION=3D'2.6.32.43-0.4.1.xs1.6.08.734.170748xen'
BRAND_CONS= OLE=3D'a console'
COMPANY_NAME=3D'xen.org'
XEN_VERSION=3D'4.1.3'
PRIMARY_DISK=3D'/dev/disk/by-id/scsi-S= ATA_QEMU_HARDDISK_QM00001'
CONTROL_DOMAIN_UUID=3D'9280c554-38f7-= 48e8-867b-9c183b2e8b59'
MANAGEMENT_ADDRESS_TYPE=3D'IPv4'
= BACKUP_PARTITION=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-par= t2'
INSTALLATION_DATE=3D'2012-11-10 06:30:22.102128'


T= here is an ambiguity in last_shutdown_time but I think it is there because = I imported it from XCP1.1. ( Notice the host installation data vs vm shutdo= wn date )

Is it the case that *new* created VMs on XCP1.6 do not have "= ;other-config" or did I miss anything ?
We also use these fie= lds and they are important for us hence if you confirm that they are remove= d in XCP1.6 then I would request to bring them back.


Regards,
Rushikesh






On Thu, Jan 3, 2013 at 9:19 PM, George Shuk= lin <george.shuklin@gmail.com> wrote:
Yes, if possible. Those fields was very usef= ul.

Some use cases:

1) They can be used to detect crashed VM's. If SR is going offline and = VM mount options says errors=3Dpanic, VM is crashing. Those fields allows v= ery easy to search for crashed VM and restart them after SR is repaired. 2) Status 'crashed' allows to answer customers about reason why the= ir VM was rebooted.
3) If 'last_shutdown_reason=3Drebooted' and VM is not starte= d, that is sign of problems (bad boot kernel, grub options or something els= e).
4) last_shutdown_time allows native and very intuitive sorting key for halt= ed VM's (if vm was halted recently, it can be on top, and vm with shutd= own date two years ago naturally can be at the list bottom).
5) When some complicated works with infrastructure are planned, last_shutdo= wn_time allows to predict if VM will be started soon or not (if it was halt= ed recently, it can be started at any time, if vm was halted two weeks ago,= there is very little chance it will started in near 1-2-3 hrs.)


We displays them to client in management interface

03.01.2013 19:30, Dave Scott =D0=BF=D0=B8=D1=88=D0=B5=D1=82:

Hi George,

They weren't deliberately removed -- they were missed when we split xen= opsd from xapi. I think they could probably be put back again. Perhaps we s= hould make them first-class fields rather than other-config keys, to make s= ure they don't go missing again?

Out of curiousity, what kind of thing did you use that information for?

Thanks,
Dave

-----Original Message-----
From: xe= n-api-bounces@lists.xen.org [mailto:xen-api-
bounces@lists.xe= n.org] On Behalf Of George Shuklin
Sent: 03 January 2013 3:07 PM
To: xen-api@list= s.xen.org
Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator
Good day.

Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown
time, reason and initiator. Those was extremely useful metrics and it's=
really sad to see lack of them in new version.

In XCP 1.1 they was placed in other-config:
last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart;
last_shutdown_initiator: external; last_shutdown_reason: rebooted;

In XCP 1.6 nothing like this is in other-config.

Is those fields disappear completely or I just miss them?

Thanks.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--047d7b6d88b20e080c04d26473f5-- --===============1049457846936904419== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1049457846936904419==-- From xen-api-bounces@lists.xen.org Thu Jan 03 15:59:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 15:59:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqnCx-0007Ir-NJ; Thu, 03 Jan 2013 15:59:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TqnCw-0007Ig-D5 for xen-api@lists.xen.org; Thu, 03 Jan 2013 15:59:50 +0000 Received: from [85.158.137.99:56130] by server-5.bemta-3.messagelabs.com id 78/91-04992-5FAA5E05; Thu, 03 Jan 2013 15:59:49 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1357228775!17468025!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4812 invoked from network); 3 Jan 2013 15:59:37 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 15:59:37 -0000 Received: by mail-qc0-f173.google.com with SMTP id b12so8032017qca.18 for ; Thu, 03 Jan 2013 07:59:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=e2m2WJLZTd+zGI1bQqVT/DCOn1in1KwLO5hEhGpQRTg=; b=OIR1qCCGve2YWaWjX5INPnJ2exkuvgc6najLEQ0r42G1tA9rDR8Vbj8dIn+/M4QKEx oCHVUd7H4R4a75KPUnhxlB145hprQo+zo9ldgw7u6Azy1cKWbwo9CUYPEMqhILmgQNCN SvFeLtqRhFDy+7MHynfmZg9R5K/90aC+IskGUUyNDJWo8GV0phbaD9WONxxQ06Eic80T 0ubMZU00BVSN6dVqapTnpR/xuxY2v9C3VZjyiV2fivS7WPnnS+L4pLXb63pin1X2HF+I NXUsaRYMgRHKp4lxtdDiOFFFtvzRVFRzdnRpz5d12J+FnM2t/cmtIOw8RC7Yj7b3tf1j VtQg== MIME-Version: 1.0 Received: by 10.49.12.138 with SMTP id y10mr32264908qeb.64.1357228775704; Thu, 03 Jan 2013 07:59:35 -0800 (PST) Received: by 10.229.17.19 with HTTP; Thu, 3 Jan 2013 07:59:35 -0800 (PST) In-Reply-To: <50E5A88D.5080001@gmail.com> References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> <50E5A88D.5080001@gmail.com> Date: Thu, 3 Jan 2013 21:29:35 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1049457846936904419==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1049457846936904419== Content-Type: multipart/alternative; boundary=047d7b6d88b20e080c04d26473f5 --047d7b6d88b20e080c04d26473f5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi George and Dave, Im not sure how but I do have all the parameters in VMs other-config [root@s3 ~]# xe vm-param-get param-name=3Dother-config uuid=3D1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490 auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiator: internal; last_shutdown_reason: halted; linux_template: true; rhel5: true; [root@s3 ~]# cat /etc/xensource-inventory BUILD_NUMBER=3D'61549c' DOM0_MEM=3D'752' MANAGEMENT_INTERFACE=3D'xenbr0' INSTALLATION_UUID=3D'5a17feac-b1bb-4e3d-ad26-374edb6414a0' COMPANY_NAME_SHORT=3D'xen.org' PLATFORM_NAME=3D'XCP' PLATFORM_VERSION=3D'1.6.8' KERNEL_VERSION=3D'2.6.32.43-0.4.1.xs1.6.08.734.170748xen' BRAND_CONSOLE=3D'a console' COMPANY_NAME=3D'xen.org' XEN_VERSION=3D'4.1.3' PRIMARY_DISK=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' CONTROL_DOMAIN_UUID=3D'9280c554-38f7-48e8-867b-9c183b2e8b59' MANAGEMENT_ADDRESS_TYPE=3D'IPv4' BACKUP_PARTITION=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2' INSTALLATION_DATE=3D'2012-11-10 06:30:22.102128' There is an ambiguity in last_shutdown_time but I think it is there because I imported it from XCP1.1. ( Notice the host installation data vs vm shutdown date ) Is it the case that *new* created VMs on XCP1.6 do not have "other-config" or did I miss anything ? We also use these fields and they are important for us hence if you confirm that they are removed in XCP1.6 then I would request to bring them back. Regards, Rushikesh On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin wr= ote: > Yes, if possible. Those fields was very useful. > > Some use cases: > > 1) They can be used to detect crashed VM's. If SR is going offline and VM > mount options says errors=3Dpanic, VM is crashing. Those fields allows ve= ry > easy to search for crashed VM and restart them after SR is repaired. > 2) Status 'crashed' allows to answer customers about reason why their VM > was rebooted. > 3) If 'last_shutdown_reason=3D**rebooted' and VM is not started, that is > sign of problems (bad boot kernel, grub options or something else). > 4) last_shutdown_time allows native and very intuitive sorting key for > halted VM's (if vm was halted recently, it can be on top, and vm with > shutdown date two years ago naturally can be at the list bottom). > 5) When some complicated works with infrastructure are planned, > last_shutdown_time allows to predict if VM will be started soon or not (i= f > it was halted recently, it can be started at any time, if vm was halted t= wo > weeks ago, there is very little chance it will started in near 1-2-3 hrs.= ) > > > We displays them to client in management interface > > 03.01.2013 19:30, Dave Scott =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > Hi George, >> >> They weren't deliberately removed -- they were missed when we split >> xenopsd from xapi. I think they could probably be put back again. Perhap= s >> we should make them first-class fields rather than other-config keys, to >> make sure they don't go missing again? >> >> Out of curiousity, what kind of thing did you use that information for? >> >> Thanks, >> Dave >> >> -----Original Message----- >>> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >>> bounces@lists.xen.org] On Behalf Of George Shuklin >>> Sent: 03 January 2013 3:07 PM >>> To: xen-api@lists.xen.org >>> Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiato= r >>> >>> Good day. >>> >>> Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown >>> time, reason and initiator. Those was extremely useful metrics and it's >>> really sad to see lack of them in new version. >>> >>> In XCP 1.1 they was placed in other-config: >>> last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart; >>> last_shutdown_initiator: external; last_shutdown_reason: rebooted; >>> >>> In XCP 1.6 nothing like this is in other-config. >>> >>> Is those fields disappear completely or I just miss them? >>> >>> Thanks. >>> >>> ______________________________**_________________ >>> Xen-api mailing list >>> Xen-api@lists.xen.org >>> http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api >>> >> > > ______________________________**_________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api > --047d7b6d88b20e080c04d26473f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi George and Dave,

= Im not sure how but I do have all the parameters in VMs other-config
[root@s3 ~]# xe vm-param-get param-name=3Dother-config uuid=3D1b5d4d31-e8f= f-0e1a-bfff-ad2d8a118490
auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-9= 15f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shut= down_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown= _initiator: internal; last_shutdown_reason: halted; linux_template: true; r= hel5: true;

[root@s3 ~]# cat /etc/xensource-inventory
BUILD_NUMBER=3D'61549= c'
DOM0_MEM=3D'752'
MANAGEMENT_INTERFACE=3D'xenbr0= 9;
INSTALLATION_UUID=3D'5a17feac-b1bb-4e3d-ad26-374edb6414a0'COMPANY_NAME_SHORT=3D'xen.org'
PLATFORM_NAME=3D'XCP'
PLATFORM_VERSION=3D'1.6.8'
KERN= EL_VERSION=3D'2.6.32.43-0.4.1.xs1.6.08.734.170748xen'
BRAND_CONS= OLE=3D'a console'
COMPANY_NAME=3D'xen.org'
XEN_VERSION=3D'4.1.3'
PRIMARY_DISK=3D'/dev/disk/by-id/scsi-S= ATA_QEMU_HARDDISK_QM00001'
CONTROL_DOMAIN_UUID=3D'9280c554-38f7-= 48e8-867b-9c183b2e8b59'
MANAGEMENT_ADDRESS_TYPE=3D'IPv4'
= BACKUP_PARTITION=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-par= t2'
INSTALLATION_DATE=3D'2012-11-10 06:30:22.102128'


T= here is an ambiguity in last_shutdown_time but I think it is there because = I imported it from XCP1.1. ( Notice the host installation data vs vm shutdo= wn date )

Is it the case that *new* created VMs on XCP1.6 do not have "= ;other-config" or did I miss anything ?
We also use these fie= lds and they are important for us hence if you confirm that they are remove= d in XCP1.6 then I would request to bring them back.


Regards,
Rushikesh






On Thu, Jan 3, 2013 at 9:19 PM, George Shuk= lin <george.shuklin@gmail.com> wrote:
Yes, if possible. Those fields was very usef= ul.

Some use cases:

1) They can be used to detect crashed VM's. If SR is going offline and = VM mount options says errors=3Dpanic, VM is crashing. Those fields allows v= ery easy to search for crashed VM and restart them after SR is repaired. 2) Status 'crashed' allows to answer customers about reason why the= ir VM was rebooted.
3) If 'last_shutdown_reason=3Drebooted' and VM is not starte= d, that is sign of problems (bad boot kernel, grub options or something els= e).
4) last_shutdown_time allows native and very intuitive sorting key for halt= ed VM's (if vm was halted recently, it can be on top, and vm with shutd= own date two years ago naturally can be at the list bottom).
5) When some complicated works with infrastructure are planned, last_shutdo= wn_time allows to predict if VM will be started soon or not (if it was halt= ed recently, it can be started at any time, if vm was halted two weeks ago,= there is very little chance it will started in near 1-2-3 hrs.)


We displays them to client in management interface

03.01.2013 19:30, Dave Scott =D0=BF=D0=B8=D1=88=D0=B5=D1=82:

Hi George,

They weren't deliberately removed -- they were missed when we split xen= opsd from xapi. I think they could probably be put back again. Perhaps we s= hould make them first-class fields rather than other-config keys, to make s= ure they don't go missing again?

Out of curiousity, what kind of thing did you use that information for?

Thanks,
Dave

-----Original Message-----
From: xe= n-api-bounces@lists.xen.org [mailto:xen-api-
bounces@lists.xe= n.org] On Behalf Of George Shuklin
Sent: 03 January 2013 3:07 PM
To: xen-api@list= s.xen.org
Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator
Good day.

Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown
time, reason and initiator. Those was extremely useful metrics and it's=
really sad to see lack of them in new version.

In XCP 1.1 they was placed in other-config:
last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart;
last_shutdown_initiator: external; last_shutdown_reason: rebooted;

In XCP 1.6 nothing like this is in other-config.

Is those fields disappear completely or I just miss them?

Thanks.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--047d7b6d88b20e080c04d26473f5-- --===============1049457846936904419== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1049457846936904419==-- From xen-api-bounces@lists.xen.org Thu Jan 03 17:08:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 17:08:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqoHY-0001ea-W8; Thu, 03 Jan 2013 17:08:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqoHW-0001eV-OQ for xen-api@lists.xen.org; Thu, 03 Jan 2013 17:08:39 +0000 Received: from [85.158.139.83:50690] by server-6.bemta-5.messagelabs.com id 5D/2B-30498-61BB5E05; Thu, 03 Jan 2013 17:08:38 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1357232916!31923611!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=1.9 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21701 invoked from network); 3 Jan 2013 17:08:36 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 17:08:36 -0000 Received: by mail-la0-f43.google.com with SMTP id eg20so8156266lab.2 for ; Thu, 03 Jan 2013 09:08:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=16Nvm9DoarUEdYpc4/qgf4aft1N5911fOQKUU2NmrHg=; b=B5DldVbv2D/v7cGSmGY4s+oj2ckzywKg0UJhOD3dDIwOJrFTUUWJ74FDwT1gIcKxM6 McnU2lIamqtzV1mgpdZFoN841p6mrpncFVZ260S4LddTd0NN7dq0gAdg3c9dyEc6tQE/ wmBPMfYGFzBE+FDSJR3wf2rJofFzeaVlOWnfXmWjUtTIP/rHtx3Jt0Gmlp2nWft0lOAj P5dq3WSbFyHVn9fwzvWer9sD1VC8ndeDZO+OZqgiKn/ac42haBVh0Vci+XPoBa9T9dqV bLQmoSYTZGjNghUmFatkrKoq8gq7DcgxvYL2pS+gyMwv1JQcfkwoIeLG9kxnMhcHcUoc Jlfg== X-Received: by 10.112.82.226 with SMTP id l2mr20241098lby.51.1357232915850; Thu, 03 Jan 2013 09:08:35 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id sv4sm37309lab.0.2013.01.03.09.08.35 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 09:08:35 -0800 (PST) Message-ID: <50E5BB12.3090807@gmail.com> Date: Thu, 03 Jan 2013 21:08:34 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Rushikesh Jadhav <2rushikeshj@gmail.com> References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> <50E5A88D.5080001@gmail.com> In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5347975361792659099==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5347975361792659099== Content-Type: multipart/alternative; boundary="------------080802060202060905090506" This is a multi-part message in MIME format. --------------080802060202060905090506 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Really strange. But I see last_shutdown_time: 20120406T12:57:50Z 2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, try to reboot any VM and see if date will change. PS PLATFORM_VERSION='1.6.8' <- not a release version of XCP... 03.01.2013 19:59, Rushikesh Jadhav пишет: > Hi George and Dave, > > Im not sure how but I do have all the parameters in VMs other-config > > [root@s3 ~]# xe vm-param-get param-name=other-config > uuid=1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490 > auto_poweron: true; vgpu_pci: ; import_task: > OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: > 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: > 20120406T12:57:50Z; last_shutdown_action: Destroy; > last_shutdown_initiator: internal; last_shutdown_reason: halted; > linux_template: true; rhel5: true; > > [root@s3 ~]# cat /etc/xensource-inventory > BUILD_NUMBER='61549c' > DOM0_MEM='752' > MANAGEMENT_INTERFACE='xenbr0' > INSTALLATION_UUID='5a17feac-b1bb-4e3d-ad26-374edb6414a0' > COMPANY_NAME_SHORT='xen.org ' > PLATFORM_NAME='XCP' > PLATFORM_VERSION='1.6.8' > KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.08.734.170748xen' > BRAND_CONSOLE='a console' > COMPANY_NAME='xen.org ' > XEN_VERSION='4.1.3' > PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' > CONTROL_DOMAIN_UUID='9280c554-38f7-48e8-867b-9c183b2e8b59' > MANAGEMENT_ADDRESS_TYPE='IPv4' > BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2' > INSTALLATION_DATE='2012-11-10 06:30:22.102128' > > > There is an ambiguity in last_shutdown_time but I think it is there > because I imported it from XCP1.1. ( Notice the host installation data > vs vm shutdown date ) > > Is it the case that *new* created VMs on XCP1.6 do not have > "other-config" or did I miss anything ? > We also use these fields and they are important for us hence if you > confirm that they are removed in XCP1.6 then I would request to bring > them back. > > > Regards, > Rushikesh > > > > > > > > On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin > > wrote: > > Yes, if possible. Those fields was very useful. > > Some use cases: > > 1) They can be used to detect crashed VM's. If SR is going offline > and VM mount options says errors=panic, VM is crashing. Those > fields allows very easy to search for crashed VM and restart them > after SR is repaired. > 2) Status 'crashed' allows to answer customers about reason why > their VM was rebooted. > 3) If 'last_shutdown_reason=rebooted' and VM is not started, that > is sign of problems (bad boot kernel, grub options or something else). > 4) last_shutdown_time allows native and very intuitive sorting key > for halted VM's (if vm was halted recently, it can be on top, and > vm with shutdown date two years ago naturally can be at the list > bottom). > 5) When some complicated works with infrastructure are planned, > last_shutdown_time allows to predict if VM will be started soon or > not (if it was halted recently, it can be started at any time, if > vm was halted two weeks ago, there is very little chance it will > started in near 1-2-3 hrs.) > > > We displays them to client in management interface > > 03.01.2013 19:30, Dave Scott пишет: > > Hi George, > > They weren't deliberately removed -- they were missed when we > split xenopsd from xapi. I think they could probably be put > back again. Perhaps we should make them first-class fields > rather than other-config keys, to make sure they don't go > missing again? > > Out of curiousity, what kind of thing did you use that > information for? > > Thanks, > Dave > > -----Original Message----- > From: xen-api-bounces@lists.xen.org > [mailto:xen-api- > > bounces@lists.xen.org ] On > Behalf Of George Shuklin > Sent: 03 January 2013 3:07 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown > reason/initiator > > Good day. > > Found (suddenly) that XCP 1.6 did not provides mertrics > about shutdown > time, reason and initiator. Those was extremely useful > metrics and it's > really sad to see lack of them in new version. > > In XCP 1.1 they was placed in other-config: > last_shutdown_time: 20130102T15:56:58Z; > last_shutdown_action: Restart; > last_shutdown_initiator: external; last_shutdown_reason: > rebooted; > > In XCP 1.6 nothing like this is in other-config. > > Is those fields disappear completely or I just miss them? > > Thanks. > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --------------080802060202060905090506 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Really strange.

But I see last_shutdown_time: 20120406T12:57:50Z

2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, try to reboot any VM and see if date will change.

PS PLATFORM_VERSION='1.6.8' <- not a release version of XCP...

03.01.2013 19:59, Rushikesh Jadhav пишет:
Hi George and Dave,

Im not sure how but I do have all the parameters in VMs other-config

[root@s3 ~]# xe vm-param-get param-name=other-config uuid=1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490
auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiator: internal; last_shutdown_reason: halted; linux_template: true; rhel5: true;

[root@s3 ~]# cat /etc/xensource-inventory
BUILD_NUMBER='61549c'
DOM0_MEM='752'
MANAGEMENT_INTERFACE='xenbr0'
INSTALLATION_UUID='5a17feac-b1bb-4e3d-ad26-374edb6414a0'
COMPANY_NAME_SHORT='xen.org'
PLATFORM_NAME='XCP'
PLATFORM_VERSION='1.6.8'
KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.08.734.170748xen'
BRAND_CONSOLE='a console'
COMPANY_NAME='xen.org'
XEN_VERSION='4.1.3'
PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001'
CONTROL_DOMAIN_UUID='9280c554-38f7-48e8-867b-9c183b2e8b59'
MANAGEMENT_ADDRESS_TYPE='IPv4'
BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2'
INSTALLATION_DATE='2012-11-10 06:30:22.102128'


There is an ambiguity in last_shutdown_time but I think it is there because I imported it from XCP1.1. ( Notice the host installation data vs vm shutdown date )

Is it the case that *new* created VMs on XCP1.6 do not have "other-config" or did I miss anything ?
We also use these fields and they are important for us hence if you confirm that they are removed in XCP1.6 then I would request to bring them back.


Regards,
Rushikesh







On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Yes, if possible. Those fields was very useful.

Some use cases:

1) They can be used to detect crashed VM's. If SR is going offline and VM mount options says errors=panic, VM is crashing. Those fields allows very easy to search for crashed VM and restart them after SR is repaired.
2) Status 'crashed' allows to answer customers about reason why their VM was rebooted.
3) If 'last_shutdown_reason=rebooted' and VM is not started, that is sign of problems (bad boot kernel, grub options or something else).
4) last_shutdown_time allows native and very intuitive sorting key for halted VM's (if vm was halted recently, it can be on top, and vm with shutdown date two years ago naturally can be at the list bottom).
5) When some complicated works with infrastructure are planned, last_shutdown_time allows to predict if VM will be started soon or not (if it was halted recently, it can be started at any time, if vm was halted two weeks ago, there is very little chance it will started in near 1-2-3 hrs.)


We displays them to client in management interface

03.01.2013 19:30, Dave Scott пишет:

Hi George,

They weren't deliberately removed -- they were missed when we split xenopsd from xapi. I think they could probably be put back again. Perhaps we should make them first-class fields rather than other-config keys, to make sure they don't go missing again?

Out of curiousity, what kind of thing did you use that information for?

Thanks,
Dave

-----Original Message-----
From: xen-api-bounces@lists.xen.org [mailto:xen-api-
bounces@lists.xen.org] On Behalf Of George Shuklin
Sent: 03 January 2013 3:07 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator

Good day.

Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown
time, reason and initiator. Those was extremely useful metrics and it's
really sad to see lack of them in new version.

In XCP 1.1 they was placed in other-config:
last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart;
last_shutdown_initiator: external; last_shutdown_reason: rebooted;

In XCP 1.6 nothing like this is in other-config.

Is those fields disappear completely or I just miss them?

Thanks.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--------------080802060202060905090506-- --===============5347975361792659099== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5347975361792659099==-- From xen-api-bounces@lists.xen.org Thu Jan 03 17:08:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 17:08:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqoHY-0001ea-W8; Thu, 03 Jan 2013 17:08:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqoHW-0001eV-OQ for xen-api@lists.xen.org; Thu, 03 Jan 2013 17:08:39 +0000 Received: from [85.158.139.83:50690] by server-6.bemta-5.messagelabs.com id 5D/2B-30498-61BB5E05; Thu, 03 Jan 2013 17:08:38 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1357232916!31923611!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=1.9 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21701 invoked from network); 3 Jan 2013 17:08:36 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 17:08:36 -0000 Received: by mail-la0-f43.google.com with SMTP id eg20so8156266lab.2 for ; Thu, 03 Jan 2013 09:08:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=16Nvm9DoarUEdYpc4/qgf4aft1N5911fOQKUU2NmrHg=; b=B5DldVbv2D/v7cGSmGY4s+oj2ckzywKg0UJhOD3dDIwOJrFTUUWJ74FDwT1gIcKxM6 McnU2lIamqtzV1mgpdZFoN841p6mrpncFVZ260S4LddTd0NN7dq0gAdg3c9dyEc6tQE/ wmBPMfYGFzBE+FDSJR3wf2rJofFzeaVlOWnfXmWjUtTIP/rHtx3Jt0Gmlp2nWft0lOAj P5dq3WSbFyHVn9fwzvWer9sD1VC8ndeDZO+OZqgiKn/ac42haBVh0Vci+XPoBa9T9dqV bLQmoSYTZGjNghUmFatkrKoq8gq7DcgxvYL2pS+gyMwv1JQcfkwoIeLG9kxnMhcHcUoc Jlfg== X-Received: by 10.112.82.226 with SMTP id l2mr20241098lby.51.1357232915850; Thu, 03 Jan 2013 09:08:35 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id sv4sm37309lab.0.2013.01.03.09.08.35 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 09:08:35 -0800 (PST) Message-ID: <50E5BB12.3090807@gmail.com> Date: Thu, 03 Jan 2013 21:08:34 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Rushikesh Jadhav <2rushikeshj@gmail.com> References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> <50E5A88D.5080001@gmail.com> In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5347975361792659099==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5347975361792659099== Content-Type: multipart/alternative; boundary="------------080802060202060905090506" This is a multi-part message in MIME format. --------------080802060202060905090506 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Really strange. But I see last_shutdown_time: 20120406T12:57:50Z 2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, try to reboot any VM and see if date will change. PS PLATFORM_VERSION='1.6.8' <- not a release version of XCP... 03.01.2013 19:59, Rushikesh Jadhav пишет: > Hi George and Dave, > > Im not sure how but I do have all the parameters in VMs other-config > > [root@s3 ~]# xe vm-param-get param-name=other-config > uuid=1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490 > auto_poweron: true; vgpu_pci: ; import_task: > OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: > 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: > 20120406T12:57:50Z; last_shutdown_action: Destroy; > last_shutdown_initiator: internal; last_shutdown_reason: halted; > linux_template: true; rhel5: true; > > [root@s3 ~]# cat /etc/xensource-inventory > BUILD_NUMBER='61549c' > DOM0_MEM='752' > MANAGEMENT_INTERFACE='xenbr0' > INSTALLATION_UUID='5a17feac-b1bb-4e3d-ad26-374edb6414a0' > COMPANY_NAME_SHORT='xen.org ' > PLATFORM_NAME='XCP' > PLATFORM_VERSION='1.6.8' > KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.08.734.170748xen' > BRAND_CONSOLE='a console' > COMPANY_NAME='xen.org ' > XEN_VERSION='4.1.3' > PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' > CONTROL_DOMAIN_UUID='9280c554-38f7-48e8-867b-9c183b2e8b59' > MANAGEMENT_ADDRESS_TYPE='IPv4' > BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2' > INSTALLATION_DATE='2012-11-10 06:30:22.102128' > > > There is an ambiguity in last_shutdown_time but I think it is there > because I imported it from XCP1.1. ( Notice the host installation data > vs vm shutdown date ) > > Is it the case that *new* created VMs on XCP1.6 do not have > "other-config" or did I miss anything ? > We also use these fields and they are important for us hence if you > confirm that they are removed in XCP1.6 then I would request to bring > them back. > > > Regards, > Rushikesh > > > > > > > > On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin > > wrote: > > Yes, if possible. Those fields was very useful. > > Some use cases: > > 1) They can be used to detect crashed VM's. If SR is going offline > and VM mount options says errors=panic, VM is crashing. Those > fields allows very easy to search for crashed VM and restart them > after SR is repaired. > 2) Status 'crashed' allows to answer customers about reason why > their VM was rebooted. > 3) If 'last_shutdown_reason=rebooted' and VM is not started, that > is sign of problems (bad boot kernel, grub options or something else). > 4) last_shutdown_time allows native and very intuitive sorting key > for halted VM's (if vm was halted recently, it can be on top, and > vm with shutdown date two years ago naturally can be at the list > bottom). > 5) When some complicated works with infrastructure are planned, > last_shutdown_time allows to predict if VM will be started soon or > not (if it was halted recently, it can be started at any time, if > vm was halted two weeks ago, there is very little chance it will > started in near 1-2-3 hrs.) > > > We displays them to client in management interface > > 03.01.2013 19:30, Dave Scott пишет: > > Hi George, > > They weren't deliberately removed -- they were missed when we > split xenopsd from xapi. I think they could probably be put > back again. Perhaps we should make them first-class fields > rather than other-config keys, to make sure they don't go > missing again? > > Out of curiousity, what kind of thing did you use that > information for? > > Thanks, > Dave > > -----Original Message----- > From: xen-api-bounces@lists.xen.org > [mailto:xen-api- > > bounces@lists.xen.org ] On > Behalf Of George Shuklin > Sent: 03 January 2013 3:07 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown > reason/initiator > > Good day. > > Found (suddenly) that XCP 1.6 did not provides mertrics > about shutdown > time, reason and initiator. Those was extremely useful > metrics and it's > really sad to see lack of them in new version. > > In XCP 1.1 they was placed in other-config: > last_shutdown_time: 20130102T15:56:58Z; > last_shutdown_action: Restart; > last_shutdown_initiator: external; last_shutdown_reason: > rebooted; > > In XCP 1.6 nothing like this is in other-config. > > Is those fields disappear completely or I just miss them? > > Thanks. > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --------------080802060202060905090506 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Really strange.

But I see last_shutdown_time: 20120406T12:57:50Z

2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, try to reboot any VM and see if date will change.

PS PLATFORM_VERSION='1.6.8' <- not a release version of XCP...

03.01.2013 19:59, Rushikesh Jadhav пишет:
Hi George and Dave,

Im not sure how but I do have all the parameters in VMs other-config

[root@s3 ~]# xe vm-param-get param-name=other-config uuid=1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490
auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiator: internal; last_shutdown_reason: halted; linux_template: true; rhel5: true;

[root@s3 ~]# cat /etc/xensource-inventory
BUILD_NUMBER='61549c'
DOM0_MEM='752'
MANAGEMENT_INTERFACE='xenbr0'
INSTALLATION_UUID='5a17feac-b1bb-4e3d-ad26-374edb6414a0'
COMPANY_NAME_SHORT='xen.org'
PLATFORM_NAME='XCP'
PLATFORM_VERSION='1.6.8'
KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.08.734.170748xen'
BRAND_CONSOLE='a console'
COMPANY_NAME='xen.org'
XEN_VERSION='4.1.3'
PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001'
CONTROL_DOMAIN_UUID='9280c554-38f7-48e8-867b-9c183b2e8b59'
MANAGEMENT_ADDRESS_TYPE='IPv4'
BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2'
INSTALLATION_DATE='2012-11-10 06:30:22.102128'


There is an ambiguity in last_shutdown_time but I think it is there because I imported it from XCP1.1. ( Notice the host installation data vs vm shutdown date )

Is it the case that *new* created VMs on XCP1.6 do not have "other-config" or did I miss anything ?
We also use these fields and they are important for us hence if you confirm that they are removed in XCP1.6 then I would request to bring them back.


Regards,
Rushikesh







On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Yes, if possible. Those fields was very useful.

Some use cases:

1) They can be used to detect crashed VM's. If SR is going offline and VM mount options says errors=panic, VM is crashing. Those fields allows very easy to search for crashed VM and restart them after SR is repaired.
2) Status 'crashed' allows to answer customers about reason why their VM was rebooted.
3) If 'last_shutdown_reason=rebooted' and VM is not started, that is sign of problems (bad boot kernel, grub options or something else).
4) last_shutdown_time allows native and very intuitive sorting key for halted VM's (if vm was halted recently, it can be on top, and vm with shutdown date two years ago naturally can be at the list bottom).
5) When some complicated works with infrastructure are planned, last_shutdown_time allows to predict if VM will be started soon or not (if it was halted recently, it can be started at any time, if vm was halted two weeks ago, there is very little chance it will started in near 1-2-3 hrs.)


We displays them to client in management interface

03.01.2013 19:30, Dave Scott пишет:

Hi George,

They weren't deliberately removed -- they were missed when we split xenopsd from xapi. I think they could probably be put back again. Perhaps we should make them first-class fields rather than other-config keys, to make sure they don't go missing again?

Out of curiousity, what kind of thing did you use that information for?

Thanks,
Dave

-----Original Message-----
From: xen-api-bounces@lists.xen.org [mailto:xen-api-
bounces@lists.xen.org] On Behalf Of George Shuklin
Sent: 03 January 2013 3:07 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator

Good day.

Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown
time, reason and initiator. Those was extremely useful metrics and it's
really sad to see lack of them in new version.

In XCP 1.1 they was placed in other-config:
last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart;
last_shutdown_initiator: external; last_shutdown_reason: rebooted;

In XCP 1.6 nothing like this is in other-config.

Is those fields disappear completely or I just miss them?

Thanks.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--------------080802060202060905090506-- --===============5347975361792659099== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5347975361792659099==-- From xen-api-bounces@lists.xen.org Thu Jan 03 17:48:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 17:48:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqou8-0002Wu-M0; Thu, 03 Jan 2013 17:48:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqou6-0002Wp-JJ for xen-api@lists.xen.org; Thu, 03 Jan 2013 17:48:30 +0000 Received: from [85.158.138.51:4940] by server-1.bemta-3.messagelabs.com id A9/12-08906-D64C5E05; Thu, 03 Jan 2013 17:48:29 +0000 X-Env-Sender: martinu@vshosting.cz X-Msg-Ref: server-6.tower-174.messagelabs.com!1357235308!23175794!1 X-Originating-IP: [78.24.8.155] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22619 invoked from network); 3 Jan 2013 17:48:28 -0000 Received: from pipa-ng.vshosting.cz (HELO pipa-ng.vshosting.cz) (78.24.8.155) by server-6.tower-174.messagelabs.com with SMTP; 3 Jan 2013 17:48:28 -0000 Received: from localhost (localhost [127.0.0.1]) by pipa-ng.vshosting.cz (Postfix) with ESMTP id AA6882F0C094 for ; Thu, 3 Jan 2013 18:48:26 +0100 (CET) X-Virus-Scanned: amavisd-new at pipa-ng.vshosting.cz Received: from pipa-ng.vshosting.cz ([127.0.0.1]) by localhost (pipa-ng.vshosting.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cu1hXNor2Nbo for ; Thu, 3 Jan 2013 18:48:23 +0100 (CET) Received: from [78.24.8.73] (ts.vshosting.cz [78.24.8.73]) by pipa-ng.vshosting.cz (Postfix) with ESMTPSA id 54ED52F0C080 for ; Thu, 3 Jan 2013 18:48:23 +0100 (CET) Message-ID: <50E5C468.90108@vshosting.cz> Date: Thu, 03 Jan 2013 18:48:24 +0100 From: =?ISO-8859-2?Q?Jan_Martin=F9?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] XCP 1.6 build 61809c bonding issue - lost connection on ProLiant BL465c G7 with Emulex NC551i dual-port 10 Gb CNA and HP VC Flex-10 Enet Module X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I use this hardware configuration: ProLiant BL465c G7 with embedded Emulex NC551i dual-port 10 Gb Converged Network Adapter Two HP VirtualConnect Flex-10 Enet Module Cisco C2960G All firmwares are in current versions. Emulex NC551i using FW version 4.1.450.7 corresponding with be2net Emulex OneConnect 10Gbps NIC Driver 4.1.450.7 in XCP kernel. I set two NICs to bond0: eth0 is in the network on the first HP VC Flex-10 with uplink thru port X3 connected to C2960G eth1 is in the network on the second HP VC Flex-10 with uplink thru port X3 connected to C2960G This is easiest setup for redundant connections over two HP VC Flex-10 verified as correct by HP support without any hardware problems. After switching off the first HP VC Flex-10, all traffic is automatically send thru second HP VC Flex-10 - this is OK. After switching on the first HP VC Flex-10, communication is interrupted forever - this is BAD. The problem can be solved only after reboot XCP. I'm creating bond by using this command: xe bond-create network-uuid=uuid_bond_network pif-uuids=uuid_eth0,uuid_eth1 States of NIC correspond with output of: ovs-appctl bond/show bond0 I would appreciate any advice. Thank you Jan Martinu _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 17:48:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 17:48:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqou8-0002Wu-M0; Thu, 03 Jan 2013 17:48:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqou6-0002Wp-JJ for xen-api@lists.xen.org; Thu, 03 Jan 2013 17:48:30 +0000 Received: from [85.158.138.51:4940] by server-1.bemta-3.messagelabs.com id A9/12-08906-D64C5E05; Thu, 03 Jan 2013 17:48:29 +0000 X-Env-Sender: martinu@vshosting.cz X-Msg-Ref: server-6.tower-174.messagelabs.com!1357235308!23175794!1 X-Originating-IP: [78.24.8.155] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22619 invoked from network); 3 Jan 2013 17:48:28 -0000 Received: from pipa-ng.vshosting.cz (HELO pipa-ng.vshosting.cz) (78.24.8.155) by server-6.tower-174.messagelabs.com with SMTP; 3 Jan 2013 17:48:28 -0000 Received: from localhost (localhost [127.0.0.1]) by pipa-ng.vshosting.cz (Postfix) with ESMTP id AA6882F0C094 for ; Thu, 3 Jan 2013 18:48:26 +0100 (CET) X-Virus-Scanned: amavisd-new at pipa-ng.vshosting.cz Received: from pipa-ng.vshosting.cz ([127.0.0.1]) by localhost (pipa-ng.vshosting.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cu1hXNor2Nbo for ; Thu, 3 Jan 2013 18:48:23 +0100 (CET) Received: from [78.24.8.73] (ts.vshosting.cz [78.24.8.73]) by pipa-ng.vshosting.cz (Postfix) with ESMTPSA id 54ED52F0C080 for ; Thu, 3 Jan 2013 18:48:23 +0100 (CET) Message-ID: <50E5C468.90108@vshosting.cz> Date: Thu, 03 Jan 2013 18:48:24 +0100 From: =?ISO-8859-2?Q?Jan_Martin=F9?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] XCP 1.6 build 61809c bonding issue - lost connection on ProLiant BL465c G7 with Emulex NC551i dual-port 10 Gb CNA and HP VC Flex-10 Enet Module X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I use this hardware configuration: ProLiant BL465c G7 with embedded Emulex NC551i dual-port 10 Gb Converged Network Adapter Two HP VirtualConnect Flex-10 Enet Module Cisco C2960G All firmwares are in current versions. Emulex NC551i using FW version 4.1.450.7 corresponding with be2net Emulex OneConnect 10Gbps NIC Driver 4.1.450.7 in XCP kernel. I set two NICs to bond0: eth0 is in the network on the first HP VC Flex-10 with uplink thru port X3 connected to C2960G eth1 is in the network on the second HP VC Flex-10 with uplink thru port X3 connected to C2960G This is easiest setup for redundant connections over two HP VC Flex-10 verified as correct by HP support without any hardware problems. After switching off the first HP VC Flex-10, all traffic is automatically send thru second HP VC Flex-10 - this is OK. After switching on the first HP VC Flex-10, communication is interrupted forever - this is BAD. The problem can be solved only after reboot XCP. I'm creating bond by using this command: xe bond-create network-uuid=uuid_bond_network pif-uuids=uuid_eth0,uuid_eth1 States of NIC correspond with output of: ovs-appctl bond/show bond0 I would appreciate any advice. Thank you Jan Martinu _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 18:09:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 18:09:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqpEa-0003Wn-Jl; Thu, 03 Jan 2013 18:09:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqpEZ-0003WX-3v for xen-api@lists.xen.org; Thu, 03 Jan 2013 18:09:39 +0000 Received: from [193.109.254.147:42197] by server-12.bemta-14.messagelabs.com id C1/52-06523-269C5E05; Thu, 03 Jan 2013 18:09:38 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1357236577!6249161!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27906 invoked from network); 3 Jan 2013 18:09:37 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-5.tower-27.messagelabs.com with SMTP; 3 Jan 2013 18:09:37 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Thu, 3 Jan 2013 12:09:37 -0600 Message-ID: <50E5C9AA.2090606@xenhive.com> Date: Thu, 03 Jan 2013 12:10:50 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50DDD86C.7000209@ondore.com> <602C5EB92F9AFB4D89D11B9F5B7F13552009CC30@SM-DAG151.softlayer.local> <50E46B2B.6050508@ondore.com> In-Reply-To: <50E46B2B.6050508@ondore.com> X-Auth: admin@xenhive.com Subject: [Xen-API] XCP 1.6 Storage XenMotion - need to delete temporary VDI files X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org First of all, I want to say I much I love the Storage XenMotion feature in XCP 1.6. I moved the storage for several VMs from one storage repository to another. Overall, things went really well. One of the VMs is having a problem, though. The storage migration failed for that VM on the first try because there was not enough memory available on the host node. After I made more memory available on that host node, I was able to successfully storage migrate that VM as well. The only problem is that the VM still has temp VDI assigned to it from the initial failed storage migration. What is the right way to clean up those temp VDI? Should I use vdi-forget or vdi-destroy? How can I make sure the VM does not need the temp VDI that are still assigned to it? I found the following text in the release notes for XCP 1.6 and XS 6.1: When migrating VMs using Storage XenMotion, attempts to cancel the operation may not delete the temporary virtual disks. [CA-87710] [CA-87689] I could not find the CA-87710 or CA-87689 documents. If those docs have the steps for manually cleaning up the temporary virtual disks, please post the links to those documents. Thank you. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 18:09:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 18:09:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqpEa-0003Wn-Jl; Thu, 03 Jan 2013 18:09:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqpEZ-0003WX-3v for xen-api@lists.xen.org; Thu, 03 Jan 2013 18:09:39 +0000 Received: from [193.109.254.147:42197] by server-12.bemta-14.messagelabs.com id C1/52-06523-269C5E05; Thu, 03 Jan 2013 18:09:38 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1357236577!6249161!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27906 invoked from network); 3 Jan 2013 18:09:37 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-5.tower-27.messagelabs.com with SMTP; 3 Jan 2013 18:09:37 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Thu, 3 Jan 2013 12:09:37 -0600 Message-ID: <50E5C9AA.2090606@xenhive.com> Date: Thu, 03 Jan 2013 12:10:50 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50DDD86C.7000209@ondore.com> <602C5EB92F9AFB4D89D11B9F5B7F13552009CC30@SM-DAG151.softlayer.local> <50E46B2B.6050508@ondore.com> In-Reply-To: <50E46B2B.6050508@ondore.com> X-Auth: admin@xenhive.com Subject: [Xen-API] XCP 1.6 Storage XenMotion - need to delete temporary VDI files X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org First of all, I want to say I much I love the Storage XenMotion feature in XCP 1.6. I moved the storage for several VMs from one storage repository to another. Overall, things went really well. One of the VMs is having a problem, though. The storage migration failed for that VM on the first try because there was not enough memory available on the host node. After I made more memory available on that host node, I was able to successfully storage migrate that VM as well. The only problem is that the VM still has temp VDI assigned to it from the initial failed storage migration. What is the right way to clean up those temp VDI? Should I use vdi-forget or vdi-destroy? How can I make sure the VM does not need the temp VDI that are still assigned to it? I found the following text in the release notes for XCP 1.6 and XS 6.1: When migrating VMs using Storage XenMotion, attempts to cancel the operation may not delete the temporary virtual disks. [CA-87710] [CA-87689] I could not find the CA-87710 or CA-87689 documents. If those docs have the steps for manually cleaning up the temporary virtual disks, please post the links to those documents. Thank you. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 20:04:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 20:04:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqr1y-0008FK-0V; Thu, 03 Jan 2013 20:04:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tqr1w-0008F4-5k for xen-api@lists.xen.org; Thu, 03 Jan 2013 20:04:44 +0000 Received: from [85.158.139.211:26565] by server-13.bemta-5.messagelabs.com id 82/13-10716-B54E5E05; Thu, 03 Jan 2013 20:04:43 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1357243480!21874643!1 X-Originating-IP: [209.85.216.49] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31307 invoked from network); 3 Jan 2013 20:04:41 -0000 Received: from mail-qa0-f49.google.com (HELO mail-qa0-f49.google.com) (209.85.216.49) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 20:04:41 -0000 Received: by mail-qa0-f49.google.com with SMTP id r4so10019378qaq.15 for ; Thu, 03 Jan 2013 12:04:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nsvrTzGKJuaQuxuM0rdr0jqofqoStAr8NALCMHx1bw4=; b=z8iMCe0zard40vz9HPDexqay6EyV21NAyf2We2Mdj97caZBaWJwhHTBcZnsjS5P1ES ESn3PVoM6NprcUzGnYED+k4EqJO5yKOIDaD2m85pUzIpwhLUpQ/gZ44DSLHYWapkbSok ZPYYVVx3DMZ4sMNLoIqPgrrPCLKsp0N6qkK6VHcMvPSuAT1E5B0pCSwlWefRSJTON/UN pIYBF8999lWzPFtlj5brZvxVC1dciRxhLe0CFAROdSZ5ZB+VlJGvdrLbEShbVVlF4iMw ljhF1W2WJMCGmGwLoCb55N8FQkcssApZI1V4CyvJKmQhQqi5qPKRPboRMRcdohGHLBKN OTaA== MIME-Version: 1.0 Received: by 10.49.118.38 with SMTP id kj6mr34028649qeb.53.1357243465572; Thu, 03 Jan 2013 12:04:25 -0800 (PST) Received: by 10.229.17.19 with HTTP; Thu, 3 Jan 2013 12:04:25 -0800 (PST) In-Reply-To: <50E5BB12.3090807@gmail.com> References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> <50E5A88D.5080001@gmail.com> <50E5BB12.3090807@gmail.com> Date: Fri, 4 Jan 2013 01:34:25 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5080225237823233354==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5080225237823233354== Content-Type: multipart/alternative; boundary=047d7b6d89e8a3a2d404d267dea7 --047d7b6d89e8a3a2d404d267dea7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The VM was imported so I did another import of same xva. After internal/external shutdown/reboot the other-config field is not updated. It just stays exact same. Thanks George for noticing. I don't test debian-xapi, could you please check if its same there ? From Dave's reply I assume that its same. Is there any workaround to fix this ? or we should wait for updated Xapi rpm ? Any ideas for us as to which exact files relate to it ? P.S. I tried with both xcp1.1 and xcp1.6 xentools for this particular VM running on xcp1.6 host. Regards, Rushikesh On Thu, Jan 3, 2013 at 10:38 PM, George Shuklin w= rote: > Really strange. > > But I see last_shutdown_time: 20120406T12:57:50Z > > 2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, > try to reboot any VM and see if date will change. > > PS PLATFORM_VERSION=3D'1.6.8' <- not a release version of XCP... > > 03.01.2013 19:59, Rushikesh Jadhav =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > Hi George and Dave, > > Im not sure how but I do have all the parameters in VMs other-config > > [root@s3 ~]# xe vm-param-get param-name=3Dother-config > uuid=3D1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490 > auto_poweron: true; vgpu_pci: ; import_task: > OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: > 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: > 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiato= r: > internal; last_shutdown_reason: halted; linux_template: true; rhel5: true= ; > > [root@s3 ~]# cat /etc/xensource-inventory > BUILD_NUMBER=3D'61549c' > DOM0_MEM=3D'752' > MANAGEMENT_INTERFACE=3D'xenbr0' > INSTALLATION_UUID=3D'5a17feac-b1bb-4e3d-ad26-374edb6414a0' > COMPANY_NAME_SHORT=3D'xen.org' > PLATFORM_NAME=3D'XCP' > PLATFORM_VERSION=3D'1.6.8' > KERNEL_VERSION=3D'2.6.32.43-0.4.1.xs1.6.08.734.170748xen' > BRAND_CONSOLE=3D'a console' > COMPANY_NAME=3D'xen.org' > XEN_VERSION=3D'4.1.3' > PRIMARY_DISK=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' > CONTROL_DOMAIN_UUID=3D'9280c554-38f7-48e8-867b-9c183b2e8b59' > MANAGEMENT_ADDRESS_TYPE=3D'IPv4' > BACKUP_PARTITION=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2= ' > INSTALLATION_DATE=3D'2012-11-10 06:30:22.102128' > > > There is an ambiguity in last_shutdown_time but I think it is there > because I imported it from XCP1.1. ( Notice the host installation data vs > vm shutdown date ) > > Is it the case that *new* created VMs on XCP1.6 do not have > "other-config" or did I miss anything ? > We also use these fields and they are important for us hence if you > confirm that they are removed in XCP1.6 then I would request to bring the= m > back. > > > Regards, > Rushikesh > > > > > > > > On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin = wrote: > >> Yes, if possible. Those fields was very useful. >> >> Some use cases: >> >> 1) They can be used to detect crashed VM's. If SR is going offline and V= M >> mount options says errors=3Dpanic, VM is crashing. Those fields allows v= ery >> easy to search for crashed VM and restart them after SR is repaired. >> 2) Status 'crashed' allows to answer customers about reason why their VM >> was rebooted. >> 3) If 'last_shutdown_reason=3Drebooted' and VM is not started, that is s= ign >> of problems (bad boot kernel, grub options or something else). >> 4) last_shutdown_time allows native and very intuitive sorting key for >> halted VM's (if vm was halted recently, it can be on top, and vm with >> shutdown date two years ago naturally can be at the list bottom). >> 5) When some complicated works with infrastructure are planned, >> last_shutdown_time allows to predict if VM will be started soon or not (= if >> it was halted recently, it can be started at any time, if vm was halted = two >> weeks ago, there is very little chance it will started in near 1-2-3 hrs= .) >> >> >> We displays them to client in management interface >> >> 03.01.2013 19:30, Dave Scott =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> >> Hi George, >>> >>> They weren't deliberately removed -- they were missed when we split >>> xenopsd from xapi. I think they could probably be put back again. Perha= ps >>> we should make them first-class fields rather than other-config keys, t= o >>> make sure they don't go missing again? >>> >>> Out of curiousity, what kind of thing did you use that information for? >>> >>> Thanks, >>> Dave >>> >>> -----Original Message----- >>>> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >>>> bounces@lists.xen.org] On Behalf Of George Shuklin >>>> Sent: 03 January 2013 3:07 PM >>>> To: xen-api@lists.xen.org >>>> Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiat= or >>>> >>>> Good day. >>>> >>>> Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown >>>> time, reason and initiator. Those was extremely useful metrics and it'= s >>>> really sad to see lack of them in new version. >>>> >>>> In XCP 1.1 they was placed in other-config: >>>> last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart; >>>> last_shutdown_initiator: external; last_shutdown_reason: rebooted; >>>> >>>> In XCP 1.6 nothing like this is in other-config. >>>> >>>> Is those fields disappear completely or I just miss them? >>>> >>>> Thanks. >>>> >>>> _______________________________________________ >>>> Xen-api mailing list >>>> Xen-api@lists.xen.org >>>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >>>> >>> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> > > > --047d7b6d89e8a3a2d404d267dea7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The VM was imported so I did another import of s= ame xva.

After internal/external shutdown/reboot the other-con= fig field is not updated. It just stays exact same.
Thanks Ge= orge for noticing.

I don't test debian-xapi, could you please check if its same there = ? From Dave's reply I assume that its same.

Is = there any workaround to fix this ? or we should wait for updated Xapi rpm ?=
Any ideas for us as to which exact files relate to it ?

P.S. I tried with both xcp1.1 and xcp1.6 xentools=C2=A0 for th= is particular VM running on xcp1.6 host.

Regar= ds,
Rushikesh





On Thu, Jan 3, 2013 at 10:38 PM, G= eorge Shuklin <george.shuklin@gmail.com> wrote:
=20 =20 =20
Really strange.

But I see last_shutdown_time: 20120406T12:57:50Z

2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, try to reboot any VM and see if date will change.

PS PLATFORM_VERSION=3D'1.6.8' <- not a release version of = XCP...

03.01.2013 19:59, Rushikesh Jadhav =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
Hi George and Dave,

Im not sure how but I do have all the parameters in VMs other-config

[root@s3 ~]# xe vm-param-get param-name=3Dother-config uuid=3D1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490
auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiator: internal; last_shutdown_reason: halted; linux_template: true; rhel5: true;

[root@s3 ~]# cat /etc/xensource-inventory
BUILD_NUMBER=3D'61549c'
DOM0_MEM=3D'752'
MANAGEMENT_INTERFACE=3D'xenbr0'
INSTALLATION_UUID=3D'5a17feac-b1bb-4e3d-ad26-374edb6414= a0'
COMPANY_NAME_SHORT=3D'xen.org'
PLATFORM_NAME=3D'XCP'
PLATFORM_VERSION=3D'1.6.8'
KERNEL_VERSION=3D'2.6.32.43-0.4.1.xs1.6.08.734.170748xe= n'
BRAND_CONSOLE=3D'a console'
COMPANY_NAME=3D'xen.org'
XEN_VERSION=3D'4.1.3'
PRIMARY_DISK=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' CONTROL_DOMAIN_UUID=3D'9280c554-38f7-48e8-867b-9c183b2e8b59'
MANAGEMENT_ADDRESS_TYPE=3D'IPv4'
BACKUP_PARTITION=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-par= t2'
INSTALLATION_DATE=3D'2012-11-10 06:30:22.102128'

There is an ambiguity in last_shutdown_time but I think it is there because I imported it from XCP1.1. ( Notice the host installation data vs vm shutdown date )

Is it the case that *new* created VMs on XCP1.6 do not have "other-config" or did I miss anything ?
We also use these fields and they are important for us hence if you confirm that they are removed in XCP1.6 then I would request to bring them back.


Regards,
Rushikesh







On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Yes, if possible. Those fields was very useful.

Some use cases:

1) They can be used to detect crashed VM's. If SR is going offline and VM mount options says errors=3Dpanic, VM is crashing. Those fields allows very easy to search for crashed VM and restart them after SR is repaired.
2) Status 'crashed' allows to answer customers about re= ason why their VM was rebooted.
3) If 'last_shutdown_reason=3Drebooted' and VM is not s= tarted, that is sign of problems (bad boot kernel, grub options or something else).
4) last_shutdown_time allows native and very intuitive sorting key for halted VM's (if vm was halted recently, it can be on top, and vm with shutdown date two years ago naturally can be at the list bottom).
5) When some complicated works with infrastructure are planned, last_shutdown_time allows to predict if VM will be started soon or not (if it was halted recently, it can be started at any time, if vm was halted two weeks ago, there is very little chance it will started in near 1-2-3 hrs.)


We displays them to client in management interface

03.01.2013 19:30, Dave Scott =D0=BF=D0=B8=D1=88=D0=B5=D1=82:

Hi George,

They weren't deliberately removed -- they were missed when we split xenopsd from xapi. I think they could probably be put back again. Perhaps we should make them first-class fields rather than other-config keys, to make sure they don't go missing again?

Out of curiousity, what kind of thing did you use that information for?

Thanks,
Dave

-----Original Message-----
From: xen-api-bounces@lists.xen.org [mailto:x= en-api-
bounces@lists.xen.org] On Behalf Of George Shuklin
Sent: 03 January 2013 3:07 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator

Good day.

Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown
time, reason and initiator. Those was extremely useful metrics and it's
really sad to see lack of them in new version.

In XCP 1.1 they was placed in other-config:
last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart;
last_shutdown_initiator: external; last_shutdown_reason: rebooted;

In XCP 1.6 nothing like this is in other-config.

Is those fields disappear completely or I just miss them?

Thanks.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/= xen-api


_______________________________________________
Xen-api mailing list
= Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-= api



--047d7b6d89e8a3a2d404d267dea7-- --===============5080225237823233354== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5080225237823233354==-- From xen-api-bounces@lists.xen.org Thu Jan 03 20:04:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 20:04:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tqr1y-0008FK-0V; Thu, 03 Jan 2013 20:04:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tqr1w-0008F4-5k for xen-api@lists.xen.org; Thu, 03 Jan 2013 20:04:44 +0000 Received: from [85.158.139.211:26565] by server-13.bemta-5.messagelabs.com id 82/13-10716-B54E5E05; Thu, 03 Jan 2013 20:04:43 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1357243480!21874643!1 X-Originating-IP: [209.85.216.49] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31307 invoked from network); 3 Jan 2013 20:04:41 -0000 Received: from mail-qa0-f49.google.com (HELO mail-qa0-f49.google.com) (209.85.216.49) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 20:04:41 -0000 Received: by mail-qa0-f49.google.com with SMTP id r4so10019378qaq.15 for ; Thu, 03 Jan 2013 12:04:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nsvrTzGKJuaQuxuM0rdr0jqofqoStAr8NALCMHx1bw4=; b=z8iMCe0zard40vz9HPDexqay6EyV21NAyf2We2Mdj97caZBaWJwhHTBcZnsjS5P1ES ESn3PVoM6NprcUzGnYED+k4EqJO5yKOIDaD2m85pUzIpwhLUpQ/gZ44DSLHYWapkbSok ZPYYVVx3DMZ4sMNLoIqPgrrPCLKsp0N6qkK6VHcMvPSuAT1E5B0pCSwlWefRSJTON/UN pIYBF8999lWzPFtlj5brZvxVC1dciRxhLe0CFAROdSZ5ZB+VlJGvdrLbEShbVVlF4iMw ljhF1W2WJMCGmGwLoCb55N8FQkcssApZI1V4CyvJKmQhQqi5qPKRPboRMRcdohGHLBKN OTaA== MIME-Version: 1.0 Received: by 10.49.118.38 with SMTP id kj6mr34028649qeb.53.1357243465572; Thu, 03 Jan 2013 12:04:25 -0800 (PST) Received: by 10.229.17.19 with HTTP; Thu, 3 Jan 2013 12:04:25 -0800 (PST) In-Reply-To: <50E5BB12.3090807@gmail.com> References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> <50E5A88D.5080001@gmail.com> <50E5BB12.3090807@gmail.com> Date: Fri, 4 Jan 2013 01:34:25 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5080225237823233354==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5080225237823233354== Content-Type: multipart/alternative; boundary=047d7b6d89e8a3a2d404d267dea7 --047d7b6d89e8a3a2d404d267dea7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The VM was imported so I did another import of same xva. After internal/external shutdown/reboot the other-config field is not updated. It just stays exact same. Thanks George for noticing. I don't test debian-xapi, could you please check if its same there ? From Dave's reply I assume that its same. Is there any workaround to fix this ? or we should wait for updated Xapi rpm ? Any ideas for us as to which exact files relate to it ? P.S. I tried with both xcp1.1 and xcp1.6 xentools for this particular VM running on xcp1.6 host. Regards, Rushikesh On Thu, Jan 3, 2013 at 10:38 PM, George Shuklin w= rote: > Really strange. > > But I see last_shutdown_time: 20120406T12:57:50Z > > 2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, > try to reboot any VM and see if date will change. > > PS PLATFORM_VERSION=3D'1.6.8' <- not a release version of XCP... > > 03.01.2013 19:59, Rushikesh Jadhav =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > Hi George and Dave, > > Im not sure how but I do have all the parameters in VMs other-config > > [root@s3 ~]# xe vm-param-get param-name=3Dother-config > uuid=3D1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490 > auto_poweron: true; vgpu_pci: ; import_task: > OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: > 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: > 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiato= r: > internal; last_shutdown_reason: halted; linux_template: true; rhel5: true= ; > > [root@s3 ~]# cat /etc/xensource-inventory > BUILD_NUMBER=3D'61549c' > DOM0_MEM=3D'752' > MANAGEMENT_INTERFACE=3D'xenbr0' > INSTALLATION_UUID=3D'5a17feac-b1bb-4e3d-ad26-374edb6414a0' > COMPANY_NAME_SHORT=3D'xen.org' > PLATFORM_NAME=3D'XCP' > PLATFORM_VERSION=3D'1.6.8' > KERNEL_VERSION=3D'2.6.32.43-0.4.1.xs1.6.08.734.170748xen' > BRAND_CONSOLE=3D'a console' > COMPANY_NAME=3D'xen.org' > XEN_VERSION=3D'4.1.3' > PRIMARY_DISK=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' > CONTROL_DOMAIN_UUID=3D'9280c554-38f7-48e8-867b-9c183b2e8b59' > MANAGEMENT_ADDRESS_TYPE=3D'IPv4' > BACKUP_PARTITION=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2= ' > INSTALLATION_DATE=3D'2012-11-10 06:30:22.102128' > > > There is an ambiguity in last_shutdown_time but I think it is there > because I imported it from XCP1.1. ( Notice the host installation data vs > vm shutdown date ) > > Is it the case that *new* created VMs on XCP1.6 do not have > "other-config" or did I miss anything ? > We also use these fields and they are important for us hence if you > confirm that they are removed in XCP1.6 then I would request to bring the= m > back. > > > Regards, > Rushikesh > > > > > > > > On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin = wrote: > >> Yes, if possible. Those fields was very useful. >> >> Some use cases: >> >> 1) They can be used to detect crashed VM's. If SR is going offline and V= M >> mount options says errors=3Dpanic, VM is crashing. Those fields allows v= ery >> easy to search for crashed VM and restart them after SR is repaired. >> 2) Status 'crashed' allows to answer customers about reason why their VM >> was rebooted. >> 3) If 'last_shutdown_reason=3Drebooted' and VM is not started, that is s= ign >> of problems (bad boot kernel, grub options or something else). >> 4) last_shutdown_time allows native and very intuitive sorting key for >> halted VM's (if vm was halted recently, it can be on top, and vm with >> shutdown date two years ago naturally can be at the list bottom). >> 5) When some complicated works with infrastructure are planned, >> last_shutdown_time allows to predict if VM will be started soon or not (= if >> it was halted recently, it can be started at any time, if vm was halted = two >> weeks ago, there is very little chance it will started in near 1-2-3 hrs= .) >> >> >> We displays them to client in management interface >> >> 03.01.2013 19:30, Dave Scott =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> >> Hi George, >>> >>> They weren't deliberately removed -- they were missed when we split >>> xenopsd from xapi. I think they could probably be put back again. Perha= ps >>> we should make them first-class fields rather than other-config keys, t= o >>> make sure they don't go missing again? >>> >>> Out of curiousity, what kind of thing did you use that information for? >>> >>> Thanks, >>> Dave >>> >>> -----Original Message----- >>>> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >>>> bounces@lists.xen.org] On Behalf Of George Shuklin >>>> Sent: 03 January 2013 3:07 PM >>>> To: xen-api@lists.xen.org >>>> Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiat= or >>>> >>>> Good day. >>>> >>>> Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown >>>> time, reason and initiator. Those was extremely useful metrics and it'= s >>>> really sad to see lack of them in new version. >>>> >>>> In XCP 1.1 they was placed in other-config: >>>> last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart; >>>> last_shutdown_initiator: external; last_shutdown_reason: rebooted; >>>> >>>> In XCP 1.6 nothing like this is in other-config. >>>> >>>> Is those fields disappear completely or I just miss them? >>>> >>>> Thanks. >>>> >>>> _______________________________________________ >>>> Xen-api mailing list >>>> Xen-api@lists.xen.org >>>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >>>> >>> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> > > > --047d7b6d89e8a3a2d404d267dea7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The VM was imported so I did another import of s= ame xva.

After internal/external shutdown/reboot the other-con= fig field is not updated. It just stays exact same.
Thanks Ge= orge for noticing.

I don't test debian-xapi, could you please check if its same there = ? From Dave's reply I assume that its same.

Is = there any workaround to fix this ? or we should wait for updated Xapi rpm ?=
Any ideas for us as to which exact files relate to it ?

P.S. I tried with both xcp1.1 and xcp1.6 xentools=C2=A0 for th= is particular VM running on xcp1.6 host.

Regar= ds,
Rushikesh





On Thu, Jan 3, 2013 at 10:38 PM, G= eorge Shuklin <george.shuklin@gmail.com> wrote:
=20 =20 =20
Really strange.

But I see last_shutdown_time: 20120406T12:57:50Z

2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, try to reboot any VM and see if date will change.

PS PLATFORM_VERSION=3D'1.6.8' <- not a release version of = XCP...

03.01.2013 19:59, Rushikesh Jadhav =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
Hi George and Dave,

Im not sure how but I do have all the parameters in VMs other-config

[root@s3 ~]# xe vm-param-get param-name=3Dother-config uuid=3D1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490
auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiator: internal; last_shutdown_reason: halted; linux_template: true; rhel5: true;

[root@s3 ~]# cat /etc/xensource-inventory
BUILD_NUMBER=3D'61549c'
DOM0_MEM=3D'752'
MANAGEMENT_INTERFACE=3D'xenbr0'
INSTALLATION_UUID=3D'5a17feac-b1bb-4e3d-ad26-374edb6414= a0'
COMPANY_NAME_SHORT=3D'xen.org'
PLATFORM_NAME=3D'XCP'
PLATFORM_VERSION=3D'1.6.8'
KERNEL_VERSION=3D'2.6.32.43-0.4.1.xs1.6.08.734.170748xe= n'
BRAND_CONSOLE=3D'a console'
COMPANY_NAME=3D'xen.org'
XEN_VERSION=3D'4.1.3'
PRIMARY_DISK=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' CONTROL_DOMAIN_UUID=3D'9280c554-38f7-48e8-867b-9c183b2e8b59'
MANAGEMENT_ADDRESS_TYPE=3D'IPv4'
BACKUP_PARTITION=3D'/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-par= t2'
INSTALLATION_DATE=3D'2012-11-10 06:30:22.102128'

There is an ambiguity in last_shutdown_time but I think it is there because I imported it from XCP1.1. ( Notice the host installation data vs vm shutdown date )

Is it the case that *new* created VMs on XCP1.6 do not have "other-config" or did I miss anything ?
We also use these fields and they are important for us hence if you confirm that they are removed in XCP1.6 then I would request to bring them back.


Regards,
Rushikesh







On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Yes, if possible. Those fields was very useful.

Some use cases:

1) They can be used to detect crashed VM's. If SR is going offline and VM mount options says errors=3Dpanic, VM is crashing. Those fields allows very easy to search for crashed VM and restart them after SR is repaired.
2) Status 'crashed' allows to answer customers about re= ason why their VM was rebooted.
3) If 'last_shutdown_reason=3Drebooted' and VM is not s= tarted, that is sign of problems (bad boot kernel, grub options or something else).
4) last_shutdown_time allows native and very intuitive sorting key for halted VM's (if vm was halted recently, it can be on top, and vm with shutdown date two years ago naturally can be at the list bottom).
5) When some complicated works with infrastructure are planned, last_shutdown_time allows to predict if VM will be started soon or not (if it was halted recently, it can be started at any time, if vm was halted two weeks ago, there is very little chance it will started in near 1-2-3 hrs.)


We displays them to client in management interface

03.01.2013 19:30, Dave Scott =D0=BF=D0=B8=D1=88=D0=B5=D1=82:

Hi George,

They weren't deliberately removed -- they were missed when we split xenopsd from xapi. I think they could probably be put back again. Perhaps we should make them first-class fields rather than other-config keys, to make sure they don't go missing again?

Out of curiousity, what kind of thing did you use that information for?

Thanks,
Dave

-----Original Message-----
From: xen-api-bounces@lists.xen.org [mailto:x= en-api-
bounces@lists.xen.org] On Behalf Of George Shuklin
Sent: 03 January 2013 3:07 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator

Good day.

Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown
time, reason and initiator. Those was extremely useful metrics and it's
really sad to see lack of them in new version.

In XCP 1.1 they was placed in other-config:
last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart;
last_shutdown_initiator: external; last_shutdown_reason: rebooted;

In XCP 1.6 nothing like this is in other-config.

Is those fields disappear completely or I just miss them?

Thanks.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/= xen-api


_______________________________________________
Xen-api mailing list
= Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-= api



--047d7b6d89e8a3a2d404d267dea7-- --===============5080225237823233354== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5080225237823233354==-- From xen-api-bounces@lists.xen.org Thu Jan 03 20:14:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 20:14:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqrAs-000097-RO; Thu, 03 Jan 2013 20:13:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqrAr-000090-Ld for xen-api@lists.xen.org; Thu, 03 Jan 2013 20:13:58 +0000 Received: from [85.158.138.51:41869] by server-1.bemta-3.messagelabs.com id C9/CB-08906-486E5E05; Thu, 03 Jan 2013 20:13:56 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1357244034!27452480!1 X-Originating-IP: [209.85.215.52] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3470 invoked from network); 3 Jan 2013 20:13:55 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 20:13:55 -0000 Received: by mail-la0-f52.google.com with SMTP id fq12so8630163lab.11 for ; Thu, 03 Jan 2013 12:13:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=uoWLTsEdEME0EiMPY4jdT6MCiFPTY3d5fMszkuIFpwI=; b=vaIXIESAiGYazOVIxH4Tn+0JJuoEVvRBob//dYZrH7Mbqo1787xhHPpdArLiXcELL2 wzpimIJlLxd4YaueKVg7SiNT0psGsa3SvSzB+uShcMR1gd/H2f2ZUPfLitjvYgX2SCSF 8+1zrs+GgKPgk0kWnyWAnY/K5j/IRJ+AGcOonXjjKXClcmoJLt+O3IsSSiP3QxiUyJEB fsTgx/SGXtB7N08wSQ7z+eq3+BcXUalgtKG78QJi2nYs3lg/vVWJT+68Pk5C2ZqElFXc qm5Zf7uY48s9lMPyig+2ae7t6rbtyNrHHFp0WqbldDTdVOM8AfyYqV3b9hQi0Svw/7j1 Obfw== X-Received: by 10.152.111.72 with SMTP id ig8mr47342390lab.1.1357244034467; Thu, 03 Jan 2013 12:13:54 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id v7sm17313096lbj.13.2013.01.03.12.13.53 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 12:13:53 -0800 (PST) Message-ID: <50E5E681.4000704@gmail.com> Date: Fri, 04 Jan 2013 00:13:53 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Rushikesh Jadhav <2rushikeshj@gmail.com> References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> <50E5A88D.5080001@gmail.com> <50E5BB12.3090807@gmail.com> In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0509396002608603084==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0509396002608603084== Content-Type: multipart/alternative; boundary="------------010605080204020905010007" This is a multi-part message in MIME format. --------------010605080204020905010007 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit I'm trying to get all difference between XCP 1.1 and 1.6 here http://wiki.xen.org/wiki/XCP_1.6_changes_compare_to_1.1 If someone got noticed something odd, please add. On 04.01.2013 00:04, Rushikesh Jadhav wrote: > The VM was imported so I did another import of same xva. > > After internal/external shutdown/reboot the other-config field is not > updated. It just stays exact same. > Thanks George for noticing. > > I don't test debian-xapi, could you please check if its same there ? > From Dave's reply I assume that its same. > > Is there any workaround to fix this ? or we should wait for updated > Xapi rpm ? > Any ideas for us as to which exact files relate to it ? > > > P.S. I tried with both xcp1.1 and xcp1.6 xentools for this particular > VM running on xcp1.6 host. > > Regards, > Rushikesh > > > > > > On Thu, Jan 3, 2013 at 10:38 PM, George Shuklin > > wrote: > > Really strange. > > But I see last_shutdown_time: 20120406T12:57:50Z > > 2012-04-06... Very old shutdown. Or, may be, just upgraded pool? > Please, try to reboot any VM and see if date will change. > > PS PLATFORM_VERSION='1.6.8' <- not a release version of XCP... > > 03.01.2013 19:59, Rushikesh Jadhav пишет: >> Hi George and Dave, >> >> Im not sure how but I do have all the parameters in VMs other-config >> >> [root@s3 ~]# xe vm-param-get param-name=other-config >> uuid=1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490 >> auto_poweron: true; vgpu_pci: ; import_task: >> OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: >> 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: >> 20120406T12:57:50Z; last_shutdown_action: Destroy; >> last_shutdown_initiator: internal; last_shutdown_reason: halted; >> linux_template: true; rhel5: true; >> >> [root@s3 ~]# cat /etc/xensource-inventory >> BUILD_NUMBER='61549c' >> DOM0_MEM='752' >> MANAGEMENT_INTERFACE='xenbr0' >> INSTALLATION_UUID='5a17feac-b1bb-4e3d-ad26-374edb6414a0' >> COMPANY_NAME_SHORT='xen.org ' >> PLATFORM_NAME='XCP' >> PLATFORM_VERSION='1.6.8' >> KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.08.734.170748xen' >> BRAND_CONSOLE='a console' >> COMPANY_NAME='xen.org ' >> XEN_VERSION='4.1.3' >> PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' >> CONTROL_DOMAIN_UUID='9280c554-38f7-48e8-867b-9c183b2e8b59' >> MANAGEMENT_ADDRESS_TYPE='IPv4' >> BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2' >> INSTALLATION_DATE='2012-11-10 06:30:22.102128' >> >> >> There is an ambiguity in last_shutdown_time but I think it is >> there because I imported it from XCP1.1. ( Notice the host >> installation data vs vm shutdown date ) >> >> Is it the case that *new* created VMs on XCP1.6 do not have >> "other-config" or did I miss anything ? >> We also use these fields and they are important for us hence if >> you confirm that they are removed in XCP1.6 then I would request >> to bring them back. >> >> >> Regards, >> Rushikesh >> >> >> >> >> >> >> >> On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin >> > wrote: >> >> Yes, if possible. Those fields was very useful. >> >> Some use cases: >> >> 1) They can be used to detect crashed VM's. If SR is going >> offline and VM mount options says errors=panic, VM is >> crashing. Those fields allows very easy to search for crashed >> VM and restart them after SR is repaired. >> 2) Status 'crashed' allows to answer customers about reason >> why their VM was rebooted. >> 3) If 'last_shutdown_reason=rebooted' and VM is not started, >> that is sign of problems (bad boot kernel, grub options or >> something else). >> 4) last_shutdown_time allows native and very intuitive >> sorting key for halted VM's (if vm was halted recently, it >> can be on top, and vm with shutdown date two years ago >> naturally can be at the list bottom). >> 5) When some complicated works with infrastructure are >> planned, last_shutdown_time allows to predict if VM will be >> started soon or not (if it was halted recently, it can be >> started at any time, if vm was halted two weeks ago, there is >> very little chance it will started in near 1-2-3 hrs.) >> >> >> We displays them to client in management interface >> >> 03.01.2013 19:30, Dave Scott пишет: >> >> Hi George, >> >> They weren't deliberately removed -- they were missed >> when we split xenopsd from xapi. I think they could >> probably be put back again. Perhaps we should make them >> first-class fields rather than other-config keys, to make >> sure they don't go missing again? >> >> Out of curiousity, what kind of thing did you use that >> information for? >> >> Thanks, >> Dave >> >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org >> >> [mailto:xen-api- >> bounces@lists.xen.org ] >> On Behalf Of George Shuklin >> Sent: 03 January 2013 3:07 PM >> To: xen-api@lists.xen.org >> Subject: [Xen-API] XCP 1.6: last_shutdown >> time/shutdown reason/initiator >> >> Good day. >> >> Found (suddenly) that XCP 1.6 did not provides >> mertrics about shutdown >> time, reason and initiator. Those was extremely >> useful metrics and it's >> really sad to see lack of them in new version. >> >> In XCP 1.1 they was placed in other-config: >> last_shutdown_time: 20130102T15:56:58Z; >> last_shutdown_action: Restart; >> last_shutdown_initiator: external; >> last_shutdown_reason: rebooted; >> >> In XCP 1.6 nothing like this is in other-config. >> >> Is those fields disappear completely or I just miss them? >> >> Thanks. >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> >> > > --------------010605080204020905010007 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit I'm trying to get all difference between XCP 1.1 and 1.6 here http://wiki.xen.org/wiki/XCP_1.6_changes_compare_to_1.1

If someone got noticed something odd, please add.

On 04.01.2013 00:04, Rushikesh Jadhav wrote:
The VM was imported so I did another import of same xva.

After internal/external shutdown/reboot the other-config field is not updated. It just stays exact same.
Thanks George for noticing.

I don't test debian-xapi, could you please check if its same there ? From Dave's reply I assume that its same.

Is there any workaround to fix this ? or we should wait for updated Xapi rpm ?
Any ideas for us as to which exact files relate to it ?


P.S. I tried with both xcp1.1 and xcp1.6 xentools  for this particular VM running on xcp1.6 host.

Regards,
Rushikesh





On Thu, Jan 3, 2013 at 10:38 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Really strange.

But I see last_shutdown_time: 20120406T12:57:50Z

2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, try to reboot any VM and see if date will change.

PS PLATFORM_VERSION='1.6.8' <- not a release version of XCP...

03.01.2013 19:59, Rushikesh Jadhav пишет:
Hi George and Dave,

Im not sure how but I do have all the parameters in VMs other-config

[root@s3 ~]# xe vm-param-get param-name=other-config uuid=1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490
auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiator: internal; last_shutdown_reason: halted; linux_template: true; rhel5: true;

[root@s3 ~]# cat /etc/xensource-inventory
BUILD_NUMBER='61549c'
DOM0_MEM='752'
MANAGEMENT_INTERFACE='xenbr0'
INSTALLATION_UUID='5a17feac-b1bb-4e3d-ad26-374edb6414a0'
COMPANY_NAME_SHORT='xen.org'
PLATFORM_NAME='XCP'
PLATFORM_VERSION='1.6.8'
KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.08.734.170748xen'
BRAND_CONSOLE='a console'
COMPANY_NAME='xen.org'
XEN_VERSION='4.1.3'
PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001'
CONTROL_DOMAIN_UUID='9280c554-38f7-48e8-867b-9c183b2e8b59'
MANAGEMENT_ADDRESS_TYPE='IPv4'
BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2'
INSTALLATION_DATE='2012-11-10 06:30:22.102128'


There is an ambiguity in last_shutdown_time but I think it is there because I imported it from XCP1.1. ( Notice the host installation data vs vm shutdown date )

Is it the case that *new* created VMs on XCP1.6 do not have "other-config" or did I miss anything ?
We also use these fields and they are important for us hence if you confirm that they are removed in XCP1.6 then I would request to bring them back.


Regards,
Rushikesh







On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Yes, if possible. Those fields was very useful.

Some use cases:

1) They can be used to detect crashed VM's. If SR is going offline and VM mount options says errors=panic, VM is crashing. Those fields allows very easy to search for crashed VM and restart them after SR is repaired.
2) Status 'crashed' allows to answer customers about reason why their VM was rebooted.
3) If 'last_shutdown_reason=rebooted' and VM is not started, that is sign of problems (bad boot kernel, grub options or something else).
4) last_shutdown_time allows native and very intuitive sorting key for halted VM's (if vm was halted recently, it can be on top, and vm with shutdown date two years ago naturally can be at the list bottom).
5) When some complicated works with infrastructure are planned, last_shutdown_time allows to predict if VM will be started soon or not (if it was halted recently, it can be started at any time, if vm was halted two weeks ago, there is very little chance it will started in near 1-2-3 hrs.)


We displays them to client in management interface

03.01.2013 19:30, Dave Scott пишет:

Hi George,

They weren't deliberately removed -- they were missed when we split xenopsd from xapi. I think they could probably be put back again. Perhaps we should make them first-class fields rather than other-config keys, to make sure they don't go missing again?

Out of curiousity, what kind of thing did you use that information for?

Thanks,
Dave

-----Original Message-----
From: xen-api-bounces@lists.xen.org [mailto:xen-api-
bounces@lists.xen.org] On Behalf Of George Shuklin
Sent: 03 January 2013 3:07 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator

Good day.

Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown
time, reason and initiator. Those was extremely useful metrics and it's
really sad to see lack of them in new version.

In XCP 1.1 they was placed in other-config:
last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart;
last_shutdown_initiator: external; last_shutdown_reason: rebooted;

In XCP 1.6 nothing like this is in other-config.

Is those fields disappear completely or I just miss them?

Thanks.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api



--------------010605080204020905010007-- --===============0509396002608603084== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0509396002608603084==-- From xen-api-bounces@lists.xen.org Thu Jan 03 20:14:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 20:14:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqrAs-000097-RO; Thu, 03 Jan 2013 20:13:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqrAr-000090-Ld for xen-api@lists.xen.org; Thu, 03 Jan 2013 20:13:58 +0000 Received: from [85.158.138.51:41869] by server-1.bemta-3.messagelabs.com id C9/CB-08906-486E5E05; Thu, 03 Jan 2013 20:13:56 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1357244034!27452480!1 X-Originating-IP: [209.85.215.52] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3470 invoked from network); 3 Jan 2013 20:13:55 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jan 2013 20:13:55 -0000 Received: by mail-la0-f52.google.com with SMTP id fq12so8630163lab.11 for ; Thu, 03 Jan 2013 12:13:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=uoWLTsEdEME0EiMPY4jdT6MCiFPTY3d5fMszkuIFpwI=; b=vaIXIESAiGYazOVIxH4Tn+0JJuoEVvRBob//dYZrH7Mbqo1787xhHPpdArLiXcELL2 wzpimIJlLxd4YaueKVg7SiNT0psGsa3SvSzB+uShcMR1gd/H2f2ZUPfLitjvYgX2SCSF 8+1zrs+GgKPgk0kWnyWAnY/K5j/IRJ+AGcOonXjjKXClcmoJLt+O3IsSSiP3QxiUyJEB fsTgx/SGXtB7N08wSQ7z+eq3+BcXUalgtKG78QJi2nYs3lg/vVWJT+68Pk5C2ZqElFXc qm5Zf7uY48s9lMPyig+2ae7t6rbtyNrHHFp0WqbldDTdVOM8AfyYqV3b9hQi0Svw/7j1 Obfw== X-Received: by 10.152.111.72 with SMTP id ig8mr47342390lab.1.1357244034467; Thu, 03 Jan 2013 12:13:54 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id v7sm17313096lbj.13.2013.01.03.12.13.53 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 12:13:53 -0800 (PST) Message-ID: <50E5E681.4000704@gmail.com> Date: Fri, 04 Jan 2013 00:13:53 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Rushikesh Jadhav <2rushikeshj@gmail.com> References: <50E59EA1.3050706@gmail.com> <81A73678E76EA642801C8F2E4823AD21012F0D72EBE8@LONPMAILBOX01.citrite.net> <50E5A88D.5080001@gmail.com> <50E5BB12.3090807@gmail.com> In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0509396002608603084==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0509396002608603084== Content-Type: multipart/alternative; boundary="------------010605080204020905010007" This is a multi-part message in MIME format. --------------010605080204020905010007 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit I'm trying to get all difference between XCP 1.1 and 1.6 here http://wiki.xen.org/wiki/XCP_1.6_changes_compare_to_1.1 If someone got noticed something odd, please add. On 04.01.2013 00:04, Rushikesh Jadhav wrote: > The VM was imported so I did another import of same xva. > > After internal/external shutdown/reboot the other-config field is not > updated. It just stays exact same. > Thanks George for noticing. > > I don't test debian-xapi, could you please check if its same there ? > From Dave's reply I assume that its same. > > Is there any workaround to fix this ? or we should wait for updated > Xapi rpm ? > Any ideas for us as to which exact files relate to it ? > > > P.S. I tried with both xcp1.1 and xcp1.6 xentools for this particular > VM running on xcp1.6 host. > > Regards, > Rushikesh > > > > > > On Thu, Jan 3, 2013 at 10:38 PM, George Shuklin > > wrote: > > Really strange. > > But I see last_shutdown_time: 20120406T12:57:50Z > > 2012-04-06... Very old shutdown. Or, may be, just upgraded pool? > Please, try to reboot any VM and see if date will change. > > PS PLATFORM_VERSION='1.6.8' <- not a release version of XCP... > > 03.01.2013 19:59, Rushikesh Jadhav пишет: >> Hi George and Dave, >> >> Im not sure how but I do have all the parameters in VMs other-config >> >> [root@s3 ~]# xe vm-param-get param-name=other-config >> uuid=1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490 >> auto_poweron: true; vgpu_pci: ; import_task: >> OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: >> 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: >> 20120406T12:57:50Z; last_shutdown_action: Destroy; >> last_shutdown_initiator: internal; last_shutdown_reason: halted; >> linux_template: true; rhel5: true; >> >> [root@s3 ~]# cat /etc/xensource-inventory >> BUILD_NUMBER='61549c' >> DOM0_MEM='752' >> MANAGEMENT_INTERFACE='xenbr0' >> INSTALLATION_UUID='5a17feac-b1bb-4e3d-ad26-374edb6414a0' >> COMPANY_NAME_SHORT='xen.org ' >> PLATFORM_NAME='XCP' >> PLATFORM_VERSION='1.6.8' >> KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.08.734.170748xen' >> BRAND_CONSOLE='a console' >> COMPANY_NAME='xen.org ' >> XEN_VERSION='4.1.3' >> PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' >> CONTROL_DOMAIN_UUID='9280c554-38f7-48e8-867b-9c183b2e8b59' >> MANAGEMENT_ADDRESS_TYPE='IPv4' >> BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2' >> INSTALLATION_DATE='2012-11-10 06:30:22.102128' >> >> >> There is an ambiguity in last_shutdown_time but I think it is >> there because I imported it from XCP1.1. ( Notice the host >> installation data vs vm shutdown date ) >> >> Is it the case that *new* created VMs on XCP1.6 do not have >> "other-config" or did I miss anything ? >> We also use these fields and they are important for us hence if >> you confirm that they are removed in XCP1.6 then I would request >> to bring them back. >> >> >> Regards, >> Rushikesh >> >> >> >> >> >> >> >> On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin >> > wrote: >> >> Yes, if possible. Those fields was very useful. >> >> Some use cases: >> >> 1) They can be used to detect crashed VM's. If SR is going >> offline and VM mount options says errors=panic, VM is >> crashing. Those fields allows very easy to search for crashed >> VM and restart them after SR is repaired. >> 2) Status 'crashed' allows to answer customers about reason >> why their VM was rebooted. >> 3) If 'last_shutdown_reason=rebooted' and VM is not started, >> that is sign of problems (bad boot kernel, grub options or >> something else). >> 4) last_shutdown_time allows native and very intuitive >> sorting key for halted VM's (if vm was halted recently, it >> can be on top, and vm with shutdown date two years ago >> naturally can be at the list bottom). >> 5) When some complicated works with infrastructure are >> planned, last_shutdown_time allows to predict if VM will be >> started soon or not (if it was halted recently, it can be >> started at any time, if vm was halted two weeks ago, there is >> very little chance it will started in near 1-2-3 hrs.) >> >> >> We displays them to client in management interface >> >> 03.01.2013 19:30, Dave Scott пишет: >> >> Hi George, >> >> They weren't deliberately removed -- they were missed >> when we split xenopsd from xapi. I think they could >> probably be put back again. Perhaps we should make them >> first-class fields rather than other-config keys, to make >> sure they don't go missing again? >> >> Out of curiousity, what kind of thing did you use that >> information for? >> >> Thanks, >> Dave >> >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org >> >> [mailto:xen-api- >> bounces@lists.xen.org ] >> On Behalf Of George Shuklin >> Sent: 03 January 2013 3:07 PM >> To: xen-api@lists.xen.org >> Subject: [Xen-API] XCP 1.6: last_shutdown >> time/shutdown reason/initiator >> >> Good day. >> >> Found (suddenly) that XCP 1.6 did not provides >> mertrics about shutdown >> time, reason and initiator. Those was extremely >> useful metrics and it's >> really sad to see lack of them in new version. >> >> In XCP 1.1 they was placed in other-config: >> last_shutdown_time: 20130102T15:56:58Z; >> last_shutdown_action: Restart; >> last_shutdown_initiator: external; >> last_shutdown_reason: rebooted; >> >> In XCP 1.6 nothing like this is in other-config. >> >> Is those fields disappear completely or I just miss them? >> >> Thanks. >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> >> > > --------------010605080204020905010007 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit I'm trying to get all difference between XCP 1.1 and 1.6 here http://wiki.xen.org/wiki/XCP_1.6_changes_compare_to_1.1

If someone got noticed something odd, please add.

On 04.01.2013 00:04, Rushikesh Jadhav wrote:
The VM was imported so I did another import of same xva.

After internal/external shutdown/reboot the other-config field is not updated. It just stays exact same.
Thanks George for noticing.

I don't test debian-xapi, could you please check if its same there ? From Dave's reply I assume that its same.

Is there any workaround to fix this ? or we should wait for updated Xapi rpm ?
Any ideas for us as to which exact files relate to it ?


P.S. I tried with both xcp1.1 and xcp1.6 xentools  for this particular VM running on xcp1.6 host.

Regards,
Rushikesh





On Thu, Jan 3, 2013 at 10:38 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Really strange.

But I see last_shutdown_time: 20120406T12:57:50Z

2012-04-06... Very old shutdown. Or, may be, just upgraded pool? Please, try to reboot any VM and see if date will change.

PS PLATFORM_VERSION='1.6.8' <- not a release version of XCP...

03.01.2013 19:59, Rushikesh Jadhav пишет:
Hi George and Dave,

Im not sure how but I do have all the parameters in VMs other-config

[root@s3 ~]# xe vm-param-get param-name=other-config uuid=1b5d4d31-e8ff-0e1a-bfff-ad2d8a118490
auto_poweron: true; vgpu_pci: ; import_task: OpaqueRef:3c6d447f-66d9-64d2-915f-41e6d177090b; mac_seed: 66442023-d353-6051-c701-47b93aeca922; last_shutdown_time: 20120406T12:57:50Z; last_shutdown_action: Destroy; last_shutdown_initiator: internal; last_shutdown_reason: halted; linux_template: true; rhel5: true;

[root@s3 ~]# cat /etc/xensource-inventory
BUILD_NUMBER='61549c'
DOM0_MEM='752'
MANAGEMENT_INTERFACE='xenbr0'
INSTALLATION_UUID='5a17feac-b1bb-4e3d-ad26-374edb6414a0'
COMPANY_NAME_SHORT='xen.org'
PLATFORM_NAME='XCP'
PLATFORM_VERSION='1.6.8'
KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.08.734.170748xen'
BRAND_CONSOLE='a console'
COMPANY_NAME='xen.org'
XEN_VERSION='4.1.3'
PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001'
CONTROL_DOMAIN_UUID='9280c554-38f7-48e8-867b-9c183b2e8b59'
MANAGEMENT_ADDRESS_TYPE='IPv4'
BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2'
INSTALLATION_DATE='2012-11-10 06:30:22.102128'


There is an ambiguity in last_shutdown_time but I think it is there because I imported it from XCP1.1. ( Notice the host installation data vs vm shutdown date )

Is it the case that *new* created VMs on XCP1.6 do not have "other-config" or did I miss anything ?
We also use these fields and they are important for us hence if you confirm that they are removed in XCP1.6 then I would request to bring them back.


Regards,
Rushikesh







On Thu, Jan 3, 2013 at 9:19 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Yes, if possible. Those fields was very useful.

Some use cases:

1) They can be used to detect crashed VM's. If SR is going offline and VM mount options says errors=panic, VM is crashing. Those fields allows very easy to search for crashed VM and restart them after SR is repaired.
2) Status 'crashed' allows to answer customers about reason why their VM was rebooted.
3) If 'last_shutdown_reason=rebooted' and VM is not started, that is sign of problems (bad boot kernel, grub options or something else).
4) last_shutdown_time allows native and very intuitive sorting key for halted VM's (if vm was halted recently, it can be on top, and vm with shutdown date two years ago naturally can be at the list bottom).
5) When some complicated works with infrastructure are planned, last_shutdown_time allows to predict if VM will be started soon or not (if it was halted recently, it can be started at any time, if vm was halted two weeks ago, there is very little chance it will started in near 1-2-3 hrs.)


We displays them to client in management interface

03.01.2013 19:30, Dave Scott пишет:

Hi George,

They weren't deliberately removed -- they were missed when we split xenopsd from xapi. I think they could probably be put back again. Perhaps we should make them first-class fields rather than other-config keys, to make sure they don't go missing again?

Out of curiousity, what kind of thing did you use that information for?

Thanks,
Dave

-----Original Message-----
From: xen-api-bounces@lists.xen.org [mailto:xen-api-
bounces@lists.xen.org] On Behalf Of George Shuklin
Sent: 03 January 2013 3:07 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] XCP 1.6: last_shutdown time/shutdown reason/initiator

Good day.

Found (suddenly) that XCP 1.6 did not provides mertrics about shutdown
time, reason and initiator. Those was extremely useful metrics and it's
really sad to see lack of them in new version.

In XCP 1.1 they was placed in other-config:
last_shutdown_time: 20130102T15:56:58Z; last_shutdown_action: Restart;
last_shutdown_initiator: external; last_shutdown_reason: rebooted;

In XCP 1.6 nothing like this is in other-config.

Is those fields disappear completely or I just miss them?

Thanks.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api



--------------010605080204020905010007-- --===============0509396002608603084== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0509396002608603084==-- From xen-api-bounces@lists.xen.org Thu Jan 03 22:37:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 22:37:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqtPj-0004b7-PZ; Thu, 03 Jan 2013 22:37:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqtPi-0004b2-KQ for xen-api@lists.xen.org; Thu, 03 Jan 2013 22:37:26 +0000 Received: from [193.109.254.147:64094] by server-10.bemta-14.messagelabs.com id 3C/C6-13263-52806E05; Thu, 03 Jan 2013 22:37:25 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1357252642!6265730!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30068 invoked from network); 3 Jan 2013 22:37:23 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Jan 2013 22:37:23 -0000 Received: from [187.233.68.172] (port=45076 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqtPd-0005DQ-0X for xen-api@lists.xen.org; Thu, 03 Jan 2013 16:37:21 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 1352FA209 for ; Thu, 3 Jan 2013 16:34:36 -0600 (CST) Message-ID: <50E6081F.1000702@ondore.com> Date: Thu, 03 Jan 2013 16:37:19 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DDD86C.7000209@ondore.com> <602C5EB92F9AFB4D89D11B9F5B7F13552009CC30@SM-DAG151.softlayer.local> <50E46B2B.6050508@ondore.com> <50E5C9AA.2090606@xenhive.com> In-Reply-To: <50E5C9AA.2090606@xenhive.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion - need to delete temporary VDI files X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. You hijacked my thread! El 03/01/13 12:10, admin@xenhive.com escribi=F3: > What is the right way to clean up those temp VDI? Should I use > vdi-forget or vdi-destroy? That depends of what you want, they behave differently. vdi-forget leaves the storage (file or logical volume) in it's place, = but removes all the reference to it in XCP cluster's database. It can be = used back with a vdi-introduce. vdi-destroy removes the references to the VDI and the actual storage volume. Any temporal VDIs are supposed to be cleaned automatically, unless = something went wrong with the migration process, which is probably your = case. You may delete them using vdi-destroy (watch twice what you type = before hit enter) or from XenCenter (it will tell which VDIs are not = used by any VM, handful). > How can I make sure the VM does not need the > temp VDI that are still assigned to it? In case of a clean migration, it should not leave any temporal VDI = behind. If the migration was not clean, it better leave VDIs in place, = making sure you don't loose data. In any case, a VDI can be detached from a VM by removing the = corresponding VBD, which is the bond between the VM and the actual VDI. = Store in a safe place the output of "xe vbd-param-list uuid=3D..." for = reference, in case you need to attach the storage back to the VM. > I found the following text in the release notes for XCP 1.6 and XS 6.1: > When migrating VMs using Storage XenMotion, attempts to cancel the > operation may not delete the temporary virtual disks. [CA-87710] [CA-8768= 9] That's it. > I could not find the CA-87710 or CA-87689 documents. If those docs have > the steps for manually cleaning up the temporary virtual disks, please > post the links to those documents. Yes, that is mentioned in the XenServer 6.1.0 Release Notes: http://support.citrix.com/article/CTX134582 The reference about the manual cleaning can be found in XenServer 6.1.0 = Administrator's Guide: http://docs.vmd.citrix.com/XenServer/6.1.0/1.0/en_gb/reference.html Cheers. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 03 22:37:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 03 Jan 2013 22:37:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqtPj-0004b7-PZ; Thu, 03 Jan 2013 22:37:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqtPi-0004b2-KQ for xen-api@lists.xen.org; Thu, 03 Jan 2013 22:37:26 +0000 Received: from [193.109.254.147:64094] by server-10.bemta-14.messagelabs.com id 3C/C6-13263-52806E05; Thu, 03 Jan 2013 22:37:25 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1357252642!6265730!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30068 invoked from network); 3 Jan 2013 22:37:23 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Jan 2013 22:37:23 -0000 Received: from [187.233.68.172] (port=45076 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqtPd-0005DQ-0X for xen-api@lists.xen.org; Thu, 03 Jan 2013 16:37:21 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 1352FA209 for ; Thu, 3 Jan 2013 16:34:36 -0600 (CST) Message-ID: <50E6081F.1000702@ondore.com> Date: Thu, 03 Jan 2013 16:37:19 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DDD86C.7000209@ondore.com> <602C5EB92F9AFB4D89D11B9F5B7F13552009CC30@SM-DAG151.softlayer.local> <50E46B2B.6050508@ondore.com> <50E5C9AA.2090606@xenhive.com> In-Reply-To: <50E5C9AA.2090606@xenhive.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion - need to delete temporary VDI files X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. You hijacked my thread! El 03/01/13 12:10, admin@xenhive.com escribi=F3: > What is the right way to clean up those temp VDI? Should I use > vdi-forget or vdi-destroy? That depends of what you want, they behave differently. vdi-forget leaves the storage (file or logical volume) in it's place, = but removes all the reference to it in XCP cluster's database. It can be = used back with a vdi-introduce. vdi-destroy removes the references to the VDI and the actual storage volume. Any temporal VDIs are supposed to be cleaned automatically, unless = something went wrong with the migration process, which is probably your = case. You may delete them using vdi-destroy (watch twice what you type = before hit enter) or from XenCenter (it will tell which VDIs are not = used by any VM, handful). > How can I make sure the VM does not need the > temp VDI that are still assigned to it? In case of a clean migration, it should not leave any temporal VDI = behind. If the migration was not clean, it better leave VDIs in place, = making sure you don't loose data. In any case, a VDI can be detached from a VM by removing the = corresponding VBD, which is the bond between the VM and the actual VDI. = Store in a safe place the output of "xe vbd-param-list uuid=3D..." for = reference, in case you need to attach the storage back to the VM. > I found the following text in the release notes for XCP 1.6 and XS 6.1: > When migrating VMs using Storage XenMotion, attempts to cancel the > operation may not delete the temporary virtual disks. [CA-87710] [CA-8768= 9] That's it. > I could not find the CA-87710 or CA-87689 documents. If those docs have > the steps for manually cleaning up the temporary virtual disks, please > post the links to those documents. Yes, that is mentioned in the XenServer 6.1.0 Release Notes: http://support.citrix.com/article/CTX134582 The reference about the manual cleaning can be found in XenServer 6.1.0 = Administrator's Guide: http://docs.vmd.citrix.com/XenServer/6.1.0/1.0/en_gb/reference.html Cheers. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 00:31:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 00:31:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvBz-0006fp-42; Fri, 04 Jan 2013 00:31:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvBy-0006fk-12 for xen-api@lists.xen.org; Fri, 04 Jan 2013 00:31:22 +0000 Received: from [85.158.143.99:59008] by server-2.bemta-4.messagelabs.com id F6/5C-30861-8D226E05; Fri, 04 Jan 2013 00:31:20 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1357259478!25344352!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4255 invoked from network); 4 Jan 2013 00:31:19 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-10.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 00:31:19 -0000 Received: from [187.233.68.172] (port=35091 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqvBu-0004o0-5r for xen-api@lists.xen.org; Thu, 03 Jan 2013 18:31:18 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 99F20A209 for ; Thu, 3 Jan 2013 18:28:33 -0600 (CST) Message-ID: <50E622D4.2030803@ondore.com> Date: Thu, 03 Jan 2013 18:31:16 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50DC82DD.5010204@ondore.com> <7EA643C653F17F4C80DE959E978F10EDFBF7287A74@LONPMAILBOX01.citrite.net> In-Reply-To: <7EA643C653F17F4C80DE959E978F10EDFBF7287A74@LONPMAILBOX01.citrite.net> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 bonding, 2 or 4 NICs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. El 03/01/13 06:11, Rob Hoes escribi=F3: > It should be possible to create bonds of 4 NICs in the newest > version of XenCenter (the one that comes with XenServer 6.1). > Are you using that version? No, was using XenCenter 6.0. Already upgraded to 6.1. It allowed me to select up to 4 physical interfaces to create a bond, = and also offers two new bond modes: LACP with load balancing on layer 2 = and layer 3. XenCenter 6.0 only allowed Active-active and Active-passive = modes. Great improvement! > The CLI does not have a limit on the number of NICs in a bond, > so you can indeed use that if XenCenter does not work. Have not reached that stage yet, but now I'm confident it will work fine. Thank you! -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 00:31:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 00:31:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvBz-0006fp-42; Fri, 04 Jan 2013 00:31:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvBy-0006fk-12 for xen-api@lists.xen.org; Fri, 04 Jan 2013 00:31:22 +0000 Received: from [85.158.143.99:59008] by server-2.bemta-4.messagelabs.com id F6/5C-30861-8D226E05; Fri, 04 Jan 2013 00:31:20 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1357259478!25344352!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4255 invoked from network); 4 Jan 2013 00:31:19 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-10.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 00:31:19 -0000 Received: from [187.233.68.172] (port=35091 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqvBu-0004o0-5r for xen-api@lists.xen.org; Thu, 03 Jan 2013 18:31:18 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 99F20A209 for ; Thu, 3 Jan 2013 18:28:33 -0600 (CST) Message-ID: <50E622D4.2030803@ondore.com> Date: Thu, 03 Jan 2013 18:31:16 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50DC82DD.5010204@ondore.com> <7EA643C653F17F4C80DE959E978F10EDFBF7287A74@LONPMAILBOX01.citrite.net> In-Reply-To: <7EA643C653F17F4C80DE959E978F10EDFBF7287A74@LONPMAILBOX01.citrite.net> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 bonding, 2 or 4 NICs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. El 03/01/13 06:11, Rob Hoes escribi=F3: > It should be possible to create bonds of 4 NICs in the newest > version of XenCenter (the one that comes with XenServer 6.1). > Are you using that version? No, was using XenCenter 6.0. Already upgraded to 6.1. It allowed me to select up to 4 physical interfaces to create a bond, = and also offers two new bond modes: LACP with load balancing on layer 2 = and layer 3. XenCenter 6.0 only allowed Active-active and Active-passive = modes. Great improvement! > The CLI does not have a limit on the number of NICs in a bond, > so you can indeed use that if XenCenter does not work. Have not reached that stage yet, but now I'm confident it will work fine. Thank you! -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 00:33:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 00:33:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvDZ-0006hj-U7; Fri, 04 Jan 2013 00:33:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvDY-0006hc-7S for xen-api@lists.xen.org; Fri, 04 Jan 2013 00:33:00 +0000 Received: from [193.109.254.147:56262] by server-11.bemta-14.messagelabs.com id 85/20-02659-B3326E05; Fri, 04 Jan 2013 00:32:59 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1357259577!3233087!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4326 invoked from network); 4 Jan 2013 00:32:58 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 00:32:58 -0000 Received: from [187.233.68.172] (port=55869 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqvDV-00052P-5l for xen-api@lists.xen.org; Thu, 03 Jan 2013 18:32:57 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 90D46A209 for ; Thu, 3 Jan 2013 18:30:12 -0600 (CST) Message-ID: <50E62338.6090702@ondore.com> Date: Thu, 03 Jan 2013 18:32:56 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> In-Reply-To: <50E4F8BB.9070004@gmail.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org El 02/01/13 21:19, George Shuklin escribi=F3: > live migration performs set of iterations over VM memory (you can see > details in /tmp/xenguest.log on source host), live=3Dfalse performs 'pause > and copy' mode. They are almost the same for idle machines, but make a > huge difference for heavy-loaded servers, which change lot of memory > every second. (F.e. heavy loaded erlang application with work heap about > 10GiB: it live migration performs all 32 iterations and still forced to > make 'pause and copy' at final round with large memory delta). Thanks for reference, I'll take this into account. Right now I'm still = in proof-of-concept stage. >> Still not clear how to migrate VM's in the following cases: >> - When VM is not online (vm-migrate insists it should be "running"). >> - When origin and destination hosts are within the same pool. >> > offline croos-pool migration is not supported, AFAIK. Sad, yep. > For in-pool migration there is xe vdi-pool-migration command. That's what I thought vdi-pool-migration was for, judging by it's name! (migrate vdi between pools) But no, vdi-pool-migration does not migrates the VM within the same pool: [root@xcp48 ~]# xe vdi-pool-migrate \ uuid=3De2021c93-95f4-47d7-9018-b2221d9de51b \ sr-uuid=3D590510e6-074e-47a2-bc76-04e4fb83148f The server failed to handle your request, due to an internal error. The = given message may give details useful for debugging the problem. message: = Storage_interface.Internal_error("Storage_interface.Sr_not_attached(\"59051= 0e6-074e-47a2-bc76-04e4fb83148f\")") e2021c93-95f4-47d7-9018-b2221d9de51b is the uuid of the VDI, attached to = the VM I'm trying to migrate from one host to another within the same pool. 590510e6-074e-47a2-bc76-04e4fb83148f is the Local Storage of the = destination host. I guess this should work to migrate the VDI between storages, while the = host system has access to both SRs. Seems like a indirect way to do the = move machines from one local storage to another: 1. Move storage from local storage to a shared one. 2. Move the VM from one host to another, while the storage is shared 3. Move the storage from shared to local on the destination host. (would be great if someone can confirm) -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 00:33:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 00:33:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvDZ-0006hj-U7; Fri, 04 Jan 2013 00:33:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvDY-0006hc-7S for xen-api@lists.xen.org; Fri, 04 Jan 2013 00:33:00 +0000 Received: from [193.109.254.147:56262] by server-11.bemta-14.messagelabs.com id 85/20-02659-B3326E05; Fri, 04 Jan 2013 00:32:59 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1357259577!3233087!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4326 invoked from network); 4 Jan 2013 00:32:58 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 00:32:58 -0000 Received: from [187.233.68.172] (port=55869 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqvDV-00052P-5l for xen-api@lists.xen.org; Thu, 03 Jan 2013 18:32:57 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 90D46A209 for ; Thu, 3 Jan 2013 18:30:12 -0600 (CST) Message-ID: <50E62338.6090702@ondore.com> Date: Thu, 03 Jan 2013 18:32:56 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> In-Reply-To: <50E4F8BB.9070004@gmail.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org El 02/01/13 21:19, George Shuklin escribi=F3: > live migration performs set of iterations over VM memory (you can see > details in /tmp/xenguest.log on source host), live=3Dfalse performs 'pause > and copy' mode. They are almost the same for idle machines, but make a > huge difference for heavy-loaded servers, which change lot of memory > every second. (F.e. heavy loaded erlang application with work heap about > 10GiB: it live migration performs all 32 iterations and still forced to > make 'pause and copy' at final round with large memory delta). Thanks for reference, I'll take this into account. Right now I'm still = in proof-of-concept stage. >> Still not clear how to migrate VM's in the following cases: >> - When VM is not online (vm-migrate insists it should be "running"). >> - When origin and destination hosts are within the same pool. >> > offline croos-pool migration is not supported, AFAIK. Sad, yep. > For in-pool migration there is xe vdi-pool-migration command. That's what I thought vdi-pool-migration was for, judging by it's name! (migrate vdi between pools) But no, vdi-pool-migration does not migrates the VM within the same pool: [root@xcp48 ~]# xe vdi-pool-migrate \ uuid=3De2021c93-95f4-47d7-9018-b2221d9de51b \ sr-uuid=3D590510e6-074e-47a2-bc76-04e4fb83148f The server failed to handle your request, due to an internal error. The = given message may give details useful for debugging the problem. message: = Storage_interface.Internal_error("Storage_interface.Sr_not_attached(\"59051= 0e6-074e-47a2-bc76-04e4fb83148f\")") e2021c93-95f4-47d7-9018-b2221d9de51b is the uuid of the VDI, attached to = the VM I'm trying to migrate from one host to another within the same pool. 590510e6-074e-47a2-bc76-04e4fb83148f is the Local Storage of the = destination host. I guess this should work to migrate the VDI between storages, while the = host system has access to both SRs. Seems like a indirect way to do the = move machines from one local storage to another: 1. Move storage from local storage to a shared one. 2. Move the VM from one host to another, while the storage is shared 3. Move the storage from shared to local on the destination host. (would be great if someone can confirm) -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 00:34:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 00:34:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvER-0006kF-5O; Fri, 04 Jan 2013 00:33:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvEP-0006k6-Kn for xen-api@lists.xen.org; Fri, 04 Jan 2013 00:33:53 +0000 Received: from [85.158.139.83:51231] by server-3.bemta-5.messagelabs.com id BD/3F-25441-07326E05; Fri, 04 Jan 2013 00:33:52 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357259630!24821489!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15614 invoked from network); 4 Jan 2013 00:33:51 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-16.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 00:33:51 -0000 Received: from [187.233.68.172] (port=55920 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqvEM-0005AF-2u for xen-api@lists.xen.org; Thu, 03 Jan 2013 18:33:50 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 6CD2EA20A for ; Thu, 3 Jan 2013 18:31:05 -0600 (CST) Message-ID: <50E6236C.1010402@ondore.com> Date: Thu, 03 Jan 2013 18:33:48 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> In-Reply-To: <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: [Xen-API] [Solved] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > On 3 Jan 2013, at 03:19, George Shuklin wrote: >>> Still not clear how to migrate VM's in the following cases: >>> - When VM is not online (vm-migrate insists it should be "running"). >>> - When origin and destination hosts are within the same pool. >>> >> offline croos-pool migration is not supported, AFAIK. Sad, yep. Yep, already found it in the list archive: http://lists.xen.org/archives/html/xen-api/2012-11/msg00017.html : "[...] but we don't provide an option to migrate a stopped guest. We're = planning on making this work in the next release." This is the reference of the manual process, based on XenServer = Administration Guide "Section 5.5.6.2. Copying Individual VDIs to a = Different SR" : xe vm-shutdown vm=3D xe vdi-copy uuid=3D sr-uuid=3D # returns the new UUID for the storage on target host xe vbd-list device=3Dxvda vm-name-label=3D xe vbd-destroy uuid=3D # not sure if the VDI still need to be deleted, # VDB's default "other-config:owner=3Dtrue" is supposed # to trigger the removal of VDI just after the VBD xe vm-param-set uuid=3D affinity=3D xe vbd-create device=3Dxvda bootable=3Dtrue \ vdi-uuid=3D vm-uuid=3D # vdi attached to VM via a new VBD xe vm-start vm=3D El 03/01/13 06:36, Rob Hoes escribi=F3: > You should be able to perform an in-pool storage migration using > 'xe vm-migrate', when you specify the > remote-master/remote-username/remote-password parameters for the > master of the same pool. A bit weird, but it should work that way=85 I confirm. The same command that migrate VM between pools, works to migrate within = the same pool. Remote master/username/password are still needed, even if = the destination is within the same pool. Xen is honoring it's name... Wonderful! XenCenter is cute, but I don't = feel ready for marriage yet. An upgrade from XenCenter 6.0 to to XenCenter 6.1 allowed me to do the = migration to the other host within the same pool from GUI. After upgrade, I also was able to move the detached disk from one host = to another. Wondering, if that detached disk movement is the same as = running vdi-copy and then vdi-destroy, or there is a more direct way. Thank you. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 00:34:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 00:34:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvER-0006kF-5O; Fri, 04 Jan 2013 00:33:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqvEP-0006k6-Kn for xen-api@lists.xen.org; Fri, 04 Jan 2013 00:33:53 +0000 Received: from [85.158.139.83:51231] by server-3.bemta-5.messagelabs.com id BD/3F-25441-07326E05; Fri, 04 Jan 2013 00:33:52 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357259630!24821489!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15614 invoked from network); 4 Jan 2013 00:33:51 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-16.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 00:33:51 -0000 Received: from [187.233.68.172] (port=55920 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TqvEM-0005AF-2u for xen-api@lists.xen.org; Thu, 03 Jan 2013 18:33:50 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 6CD2EA20A for ; Thu, 3 Jan 2013 18:31:05 -0600 (CST) Message-ID: <50E6236C.1010402@ondore.com> Date: Thu, 03 Jan 2013 18:33:48 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50DDD86C.7000209@ondore.com> <50E49A23.7060804@ondore.com> <50E4F8BB.9070004@gmail.com> <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> In-Reply-To: <9640E1C9-D77F-4901-BF91-70540D232703@citrix.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: [Xen-API] [Solved] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > On 3 Jan 2013, at 03:19, George Shuklin wrote: >>> Still not clear how to migrate VM's in the following cases: >>> - When VM is not online (vm-migrate insists it should be "running"). >>> - When origin and destination hosts are within the same pool. >>> >> offline croos-pool migration is not supported, AFAIK. Sad, yep. Yep, already found it in the list archive: http://lists.xen.org/archives/html/xen-api/2012-11/msg00017.html : "[...] but we don't provide an option to migrate a stopped guest. We're = planning on making this work in the next release." This is the reference of the manual process, based on XenServer = Administration Guide "Section 5.5.6.2. Copying Individual VDIs to a = Different SR" : xe vm-shutdown vm=3D xe vdi-copy uuid=3D sr-uuid=3D # returns the new UUID for the storage on target host xe vbd-list device=3Dxvda vm-name-label=3D xe vbd-destroy uuid=3D # not sure if the VDI still need to be deleted, # VDB's default "other-config:owner=3Dtrue" is supposed # to trigger the removal of VDI just after the VBD xe vm-param-set uuid=3D affinity=3D xe vbd-create device=3Dxvda bootable=3Dtrue \ vdi-uuid=3D vm-uuid=3D # vdi attached to VM via a new VBD xe vm-start vm=3D El 03/01/13 06:36, Rob Hoes escribi=F3: > You should be able to perform an in-pool storage migration using > 'xe vm-migrate', when you specify the > remote-master/remote-username/remote-password parameters for the > master of the same pool. A bit weird, but it should work that way=85 I confirm. The same command that migrate VM between pools, works to migrate within = the same pool. Remote master/username/password are still needed, even if = the destination is within the same pool. Xen is honoring it's name... Wonderful! XenCenter is cute, but I don't = feel ready for marriage yet. An upgrade from XenCenter 6.0 to to XenCenter 6.1 allowed me to do the = migration to the other host within the same pool from GUI. After upgrade, I also was able to move the detached disk from one host = to another. Wondering, if that detached disk movement is the same as = running vdi-copy and then vdi-destroy, or there is a more direct way. Thank you. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 01:52:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 01:52:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqwRs-00035G-03; Fri, 04 Jan 2013 01:51:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqwRq-00035B-7l for xen-api@lists.xen.org; Fri, 04 Jan 2013 01:51:50 +0000 Received: from [193.109.254.147:44272] by server-10.bemta-14.messagelabs.com id D2/46-13263-5B536E05; Fri, 04 Jan 2013 01:51:49 +0000 X-Env-Sender: juan@jelsupport.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1357264306!3214758!1 X-Originating-IP: [216.27.216.109] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4517 invoked from network); 4 Jan 2013 01:51:48 -0000 Received: from 109.216.27.216.static.ip.tnltd.net (HELO MAZER.sbs.local) (216.27.216.109) by server-14.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 4 Jan 2013 01:51:48 -0000 Received: from MAZER.sbs.local ([fe80::9538:f5d5:8163:90a8]) by MAZER.sbs.local ([fe80::9538:f5d5:8163:90a8%10]) with mapi; Thu, 3 Jan 2013 17:51:41 -0800 From: Juan Lorenzana To: "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 17:51:39 -0800 Thread-Topic: NFS Tuning - How To Thread-Index: Ac3qHatQqVFYWs0PS32pLGMGluosVg== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] NFS Tuning - How To X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3030179303017083742==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3030179303017083742== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF6696BMAZERsbslocal_" --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF6696BMAZERsbslocal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Okay, so I have two Dell PowerEdge server and we are using with a NAS solut= ion called TrueNAS by IX Systems. This is basically a ZFS version 28 imple= mentation for the NAS solution. Anyway, when we mount our NFS storage repositories over our 10GB interfaces= on the Dell PowerEdge server and the NAS also has 10GB, we get horrible NF= S performance. If I mount a CIFS repository, we get blazing fast performan= ce. So my question is how would I go about tuning the different NFS options to = do various tests. A quick scan on Google produced nothing on how to do thi= s. My thoughts are to either pass NFS options in Xen Center under the Advanced Options input box or edit the nfs.py file. I tried using the Adva= nced Options but I do not think that worked. I am currently running XCP 1.5 but plan on migrating to 1.6 in the next few= months. I would really like to tune the NFS first on 1.5 so that I can co= mpare performance to 1.6. Any pointers to try to improve NFS performance? I am getting about a 6MB/s write and 20MB/s read on the NFS storage reposit= ory when doing iozone tests inside a VM. With a 10GB interface I should be= in the 100's. If I do iozone test on the TrueNAS directly, I get about 60= 0MB/s on average. When doing iozone testing on VM running Windows using CI= FS from the same storage solution, we are getting close to 180 MB/s so I kn= ow the issue is not the storage repository, so I am guessing it has to do w= ith NFS tuning. Any help is appreciated. Thanks. Juan --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF6696BMAZERsbslocal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Okay, so I have = two Dell PowerEdge server and we are using with a NAS solution called TrueN= AS by IX Systems.  This is basically a ZFS version 28 implementation f= or the NAS solution.

 

Anyway, when we mount our NFS storage repositories o= ver our 10GB interfaces on the Dell PowerEdge server and the NAS also has 1= 0GB, we get horrible NFS performance.  If I mount a CIFS repository, w= e get blazing fast performance.

&nb= sp;

So my question is how would I go about tu= ning the different NFS options to do various tests.  A quick scan on G= oogle produced nothing on how to do this.  My thoughts are to either p= ass NFS options in Xen Center under the
Advanced Options input box or e= dit the nfs.py file.  I tried using the Advanced Options but I do not = think that worked.

 

=

I am currently running XCP 1.5 but plan on migrating t= o 1.6 in the next few months.  I would really like to tune the NFS fir= st on 1.5 so that I can compare performance to 1.6. 

 

Any pointers t= o try to improve NFS performance?

&= nbsp;

I am getting about a 6MB/s write and 20= MB/s read on the NFS storage repository when doing iozone tests inside a VM= .  With a 10GB interface I should be in the 100’s.  If I do= iozone test on the TrueNAS directly, I get about 600MB/s on average. = When doing iozone testing on VM running Windows using CIFS from the same s= torage solution, we are getting close to 180 MB/s so I know the issue is no= t the storage repository, so I am guessing it has to do with NFS tuning.


Any help is appreciated.  Thanks.=

 

Juan

 

 

= --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF6696BMAZERsbslocal_-- --===============3030179303017083742== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3030179303017083742==-- From xen-api-bounces@lists.xen.org Fri Jan 04 01:52:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 01:52:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqwRs-00035G-03; Fri, 04 Jan 2013 01:51:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TqwRq-00035B-7l for xen-api@lists.xen.org; Fri, 04 Jan 2013 01:51:50 +0000 Received: from [193.109.254.147:44272] by server-10.bemta-14.messagelabs.com id D2/46-13263-5B536E05; Fri, 04 Jan 2013 01:51:49 +0000 X-Env-Sender: juan@jelsupport.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1357264306!3214758!1 X-Originating-IP: [216.27.216.109] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4517 invoked from network); 4 Jan 2013 01:51:48 -0000 Received: from 109.216.27.216.static.ip.tnltd.net (HELO MAZER.sbs.local) (216.27.216.109) by server-14.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 4 Jan 2013 01:51:48 -0000 Received: from MAZER.sbs.local ([fe80::9538:f5d5:8163:90a8]) by MAZER.sbs.local ([fe80::9538:f5d5:8163:90a8%10]) with mapi; Thu, 3 Jan 2013 17:51:41 -0800 From: Juan Lorenzana To: "xen-api@lists.xen.org" Date: Thu, 3 Jan 2013 17:51:39 -0800 Thread-Topic: NFS Tuning - How To Thread-Index: Ac3qHatQqVFYWs0PS32pLGMGluosVg== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] NFS Tuning - How To X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3030179303017083742==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3030179303017083742== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF6696BMAZERsbslocal_" --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF6696BMAZERsbslocal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Okay, so I have two Dell PowerEdge server and we are using with a NAS solut= ion called TrueNAS by IX Systems. This is basically a ZFS version 28 imple= mentation for the NAS solution. Anyway, when we mount our NFS storage repositories over our 10GB interfaces= on the Dell PowerEdge server and the NAS also has 10GB, we get horrible NF= S performance. If I mount a CIFS repository, we get blazing fast performan= ce. So my question is how would I go about tuning the different NFS options to = do various tests. A quick scan on Google produced nothing on how to do thi= s. My thoughts are to either pass NFS options in Xen Center under the Advanced Options input box or edit the nfs.py file. I tried using the Adva= nced Options but I do not think that worked. I am currently running XCP 1.5 but plan on migrating to 1.6 in the next few= months. I would really like to tune the NFS first on 1.5 so that I can co= mpare performance to 1.6. Any pointers to try to improve NFS performance? I am getting about a 6MB/s write and 20MB/s read on the NFS storage reposit= ory when doing iozone tests inside a VM. With a 10GB interface I should be= in the 100's. If I do iozone test on the TrueNAS directly, I get about 60= 0MB/s on average. When doing iozone testing on VM running Windows using CI= FS from the same storage solution, we are getting close to 180 MB/s so I kn= ow the issue is not the storage repository, so I am guessing it has to do w= ith NFS tuning. Any help is appreciated. Thanks. Juan --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF6696BMAZERsbslocal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Okay, so I have = two Dell PowerEdge server and we are using with a NAS solution called TrueN= AS by IX Systems.  This is basically a ZFS version 28 implementation f= or the NAS solution.

 

Anyway, when we mount our NFS storage repositories o= ver our 10GB interfaces on the Dell PowerEdge server and the NAS also has 1= 0GB, we get horrible NFS performance.  If I mount a CIFS repository, w= e get blazing fast performance.

&nb= sp;

So my question is how would I go about tu= ning the different NFS options to do various tests.  A quick scan on G= oogle produced nothing on how to do this.  My thoughts are to either p= ass NFS options in Xen Center under the
Advanced Options input box or e= dit the nfs.py file.  I tried using the Advanced Options but I do not = think that worked.

 

=

I am currently running XCP 1.5 but plan on migrating t= o 1.6 in the next few months.  I would really like to tune the NFS fir= st on 1.5 so that I can compare performance to 1.6. 

 

Any pointers t= o try to improve NFS performance?

&= nbsp;

I am getting about a 6MB/s write and 20= MB/s read on the NFS storage repository when doing iozone tests inside a VM= .  With a 10GB interface I should be in the 100’s.  If I do= iozone test on the TrueNAS directly, I get about 600MB/s on average. = When doing iozone testing on VM running Windows using CIFS from the same s= torage solution, we are getting close to 180 MB/s so I know the issue is no= t the storage repository, so I am guessing it has to do with NFS tuning.


Any help is appreciated.  Thanks.=

 

Juan

 

 

= --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF6696BMAZERsbslocal_-- --===============3030179303017083742== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3030179303017083742==-- From xen-api-bounces@lists.xen.org Fri Jan 04 05:47:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 05:47:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr07G-00066e-EO; Fri, 04 Jan 2013 05:46:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr07F-00066X-34 for xen-api@lists.xen.org; Fri, 04 Jan 2013 05:46:49 +0000 Received: from [85.158.139.83:24483] by server-13.bemta-5.messagelabs.com id C7/DE-10716-8CC66E05; Fri, 04 Jan 2013 05:46:48 +0000 X-Env-Sender: yunshandev@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1357278405!25898763!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MIME_BOUND_NEXTPART,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13251 invoked from network); 4 Jan 2013 05:46:46 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 05:46:46 -0000 Received: by mail-pa0-f54.google.com with SMTP id bi5so9028311pad.13 for ; Thu, 03 Jan 2013 21:46:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:reply-to:subject:references:x-priority :x-has-attach:x-mailer:mime-version:message-id:content-type; bh=e9+Xbsbw9EZqcz8QAMqVTX3XFT4hC8rIHDmS/miTcCU=; b=Zy1gGXDhfvMrX+9tSGXYsa3ue0dgGq6MGPfdH5Qx9ItgnTdrlCjgUKYARmk97xznHm G+acotKjYe7N+hgOjUN/6UmNgz30VOEYxa/jw9bDHh50sicOcW7fNiBZiZRa7Mke9wt/ z/1fmwAaj+0X2ne6390djn1TbPWngFJeOJ2VCAkfC5NdKWbfeSmRIMi/66pswe31DGZx jfjqxB3PuxlcFAklieYrWluyUU82qIsQrq//CCy1S1B67WwjtfKvqjc+uWuQtPpdZF70 EgL++0KeW9GFXJMIbevp+6QH8q7fjVhABHu/ZZnjtFkq7mVYS+5/pxA4Gh4XZM7uoNBM I9Xg== X-Received: by 10.68.191.5 with SMTP id gu5mr159695931pbc.145.1357278404933; Thu, 03 Jan 2013 21:46:44 -0800 (PST) Received: from yunshan ([114.255.72.194]) by mx.google.com with ESMTPS id oi3sm31620801pbb.1.2013.01.03.21.46.40 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 21:46:43 -0800 (PST) Date: Fri, 4 Jan 2013 13:47:10 +0800 From: "Tianpeng Zhang" To: "George Shuklin" , xen-api References: <201212311004494374333@gmail.com>, <50E274DA.5010000@gmail.com> X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.91[cn] Mime-Version: 1.0 Message-ID: <2013010413470662574412@gmail.com> Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: yunshandev List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5567433141901244288==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5567433141901244288== Content-Type: multipart/alternative; boundary="----=_001_NextPart853150083550_=----" This is a multi-part message in MIME format. ------=_001_NextPart853150083550_=---- Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 VGhhbmtzIEdlb3JnZSBmb3IgeW91ciBoZWxwLiBJIHRyaWVkIG1pZ3JhdGUgYW5vdGhlciBWTSwg aXQgZmluYWxseSBzdWNjZXNzZnVsbHkuIEkgZ3Vlc3MgdGhlIHJvb3QgY2F1c2UgaXMgdGhlcmUg aXMgYW4gSVNPIGF0dGFjaGVkIHRvIHRoZSBmYWlsdXJlIFZNLCB3aGljaCBpcyBhIHJlbW90ZSBD SUZTIGZpbGUuIE5vdGhpbmcgYXR0YWNoZWQgZm9yIHRoZSBWTSBtaWdyYXRlIHN1Y2Nlc3NmdWxs eS4gSSB3aWxsIGNoZWNrIHRoZSBsb2cgYXMgeW91IHNhaWQgd2hlbiB0aGlzIGtpbmQgb2YgaXNz dWUgaGFwcGVuIGFnYWluLg0KDQpUUA0KDQpGcm9tOiBHZW9yZ2UgU2h1a2xpbg0KRGF0ZTogMjAx My0wMS0wMSAxMzozMg0KVG86IHhlbi1hcGkNClN1YmplY3Q6IFJlOiBbWGVuLUFQSV0gWENQMS42 IHN0b3JhZ2UgeGVubW90aW9uIGlzc3VlDQpOb3QgeWV0LiBNeSB0ZXN0IG1hY2hpbmVzIGZseSBi ZXR3ZWVuIHBvb2xzIGxpa2UgYSBtYWdpYy4NCg0KUGxlYXNlIHByb3ZpZGVzIHhlbnNvdXJjZS5s b2cgcGllY2VzIGZyb20gYm90aCBzaWRlczogc2VuZGVyIGFuZCByZWNlaXZlci4gSSB0aGluaywg dGhleSBzaG91bGQgYmUgcG9vbCdzIG1hc3RlcnMgbG9ncy4NCg0KUFMgRG8gbm90IGZvcmdldCB0 byBzZXQgdXAgZGVmYXVsdC1zciBwb29sIHByb3BlcnR5IG9uIHJlY2VpdmVyLiANCg0KMzEuMTIu MjAxMiAwNjowNCwgVGlhbnBlbmcgWmhhbmcg0L/QuNGI0LXRgjoNCg0KSGkgQWxsLA0KDQpJIGdv dCBvbmUgaXNzdWUgd2l0aCB4Y3AxLjYgd2hlbiB0ZXN0aW5nIFZNIHN0b3JhZ2UgeGVuTW90aW9u IHRvIGFub3RoZXIgaG9zdC4gSXQgcmVwb3J0ZWQgZXJyb3IgYXMgYW4gImludGVybmFsIGVycm9y Ii4gSGF2ZSBhbnlvbmUgbWV0IHRoaXMgaXNzdWUgYmVmb3JlPyBPciBnaXZlIHNvbWUgdGlwcyBm b3IgdGhpcyBpc3N1ZT8NCg0KVGhhbmtzLiANCg0KW3Jvb3RAeGNwMTAyIH5dIyB4ZSB2bS1taWdy YXRlIGRlc3RpbmF0aW9uLXNyLXV1aWQ9MmE5ZTBjZDAtMGRkZi1iOWVmLTVlMzgtMmY1N2U0YWMz NjFlIHZtPUNlbnRPUzYtUFYgcmVtb3RlLW1hc3Rlcj0xMC4zMy4yLjEwMyByZW1vdGUtcGFzc3dv cmQ9cGFzc3dkIHJlbW90ZS11c2VybmFtZT1yb290DQpQZXJmb3JtaW5nIGEgU3RvcmFnZSBYZW5N b3Rpb24gbWlncmF0aW9uLiBZb3VyIFZNJ3MgVkRJcyB3aWxsIGJlIG1pZ3JhdGVkIHdpdGggdGhl IFZNLg0KV2lsbCBtaWdyYXRlIHRvIHJlbW90ZSBob3N0OiB4Y3AxMDMsIHVzaW5nIHJlbW90ZSBu ZXR3b3JrOiBQb29sLXdpZGUgbmV0d29yayBhc3NvY2lhdGVkIHdpdGggZXRoMC4gSGVyZSBpcyB0 aGUgVkRJIG1hcHBpbmc6DQpWREkgYTA5ZmM5NTQtZTVjYS00ZTAyLWFiYzktODc1YWZhNzYxNmY4 IC0+IFNSIDJhOWUwY2QwLTBkZGYtYjllZi01ZTM4LTJmNTdlNGFjMzYxZQ0KVkRJIDg0YmM3MTI5 LWFiOTUtNDI0YS1iYTExLWM4ZmYyZDFkNWZkNiAtPiBTUiAyYTllMGNkMC0wZGRmLWI5ZWYtNWUz OC0yZjU3ZTRhYzM2MWUNClRoZSBzZXJ2ZXIgZmFpbGVkIHRvIGhhbmRsZSB5b3VyIHJlcXVlc3Qs IGR1ZSB0byBhbiBpbnRlcm5hbCBlcnJvci4gIFRoZSBnaXZlbiBtZXNzYWdlIG1heSBnaXZlIGRl dGFpbHMgdXNlZnVsIGZvciBkZWJ1Z2dpbmcgdGhlIHByb2JsZW0uDQptZXNzYWdlOiBJbXBvcnQu SUZhaWx1cmUoMikNCltyb290QHhjcDEwMiB+XSMNCg0KIA0KDQpfX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KWGVuLWFwaSBtYWlsaW5nIGxpc3QNClhlbi1h cGlAbGlzdHMueGVuLm9yZw0KaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xp c3RpbmZvL3hlbi1hcGk= ------=_001_NextPart853150083550_=---- Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable =EF=BB=BF
Thanks George for your help. I tried migrate another VM, it finally=20 successfully. I guess the root cause is there is an ISO attached= to=20 the failure VM, which is a remote CIFS file. Nothing attached for the VM m= igrate=20 successfully. I will check the log as you said when this kind of issue hap= pen=20 again.
 
TP
 
Date: 2013-01-01 13:32
To: xen-api<= /DIV>
Subject: Re: [Xen-API] XCP1.6 storage xenmotion=20 issue
Not yet. My test machines fly between pools l= ike a=20 magic.

Please provides xensource.log pieces from both sides: sender= and=20 receiver. I think, they should be pool's masters logs.

PS Do not fo= rget=20 to set up default-sr pool property on receiver.

31.12.2012 06:04,=20 Tianpeng Zhang =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
Hi All,
 
I got one issue with xcp1.6 when testing VM storage xenMotion = to=20 another host. It reported error as an "internal error". Have a= nyone=20 met this issue before? Or give some tips for this issue?
 
Thanks. 
 
[root@xcp102 ~]# xe vm-migrate destination-sr-u= uid=3D2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e vm=3DCentOS6-PV remot= e-master=3D10.33.2.103 remote-password=3Dpasswd remote-username= =3Droot
Performing a Storage XenMotion migration. = Your VM's VDIs will be migrated with th= e VM.
Will migrate to remote host: xcp103, = using remote network: Pool-wide network associate= d with eth0. Here is the VDI mapping:
VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -> SR&nb= sp;2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e
VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -> SR&nb= sp;2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e
The server failed to handle your requ= est, due to an internal error.  The&nbs= p;given message may give details useful for&= nbsp;debugging the problem.
message: Import.IFailure(2)
[root@xcp102 ~]#


__=
_____________________________________________
Xen-api mailing list
=
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-ap=
i

------=_001_NextPart853150083550_=------ --===============5567433141901244288== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5567433141901244288==-- From xen-api-bounces@lists.xen.org Fri Jan 04 05:47:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 05:47:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr07G-00066e-EO; Fri, 04 Jan 2013 05:46:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr07F-00066X-34 for xen-api@lists.xen.org; Fri, 04 Jan 2013 05:46:49 +0000 Received: from [85.158.139.83:24483] by server-13.bemta-5.messagelabs.com id C7/DE-10716-8CC66E05; Fri, 04 Jan 2013 05:46:48 +0000 X-Env-Sender: yunshandev@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1357278405!25898763!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MIME_BOUND_NEXTPART,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13251 invoked from network); 4 Jan 2013 05:46:46 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 05:46:46 -0000 Received: by mail-pa0-f54.google.com with SMTP id bi5so9028311pad.13 for ; Thu, 03 Jan 2013 21:46:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:reply-to:subject:references:x-priority :x-has-attach:x-mailer:mime-version:message-id:content-type; bh=e9+Xbsbw9EZqcz8QAMqVTX3XFT4hC8rIHDmS/miTcCU=; b=Zy1gGXDhfvMrX+9tSGXYsa3ue0dgGq6MGPfdH5Qx9ItgnTdrlCjgUKYARmk97xznHm G+acotKjYe7N+hgOjUN/6UmNgz30VOEYxa/jw9bDHh50sicOcW7fNiBZiZRa7Mke9wt/ z/1fmwAaj+0X2ne6390djn1TbPWngFJeOJ2VCAkfC5NdKWbfeSmRIMi/66pswe31DGZx jfjqxB3PuxlcFAklieYrWluyUU82qIsQrq//CCy1S1B67WwjtfKvqjc+uWuQtPpdZF70 EgL++0KeW9GFXJMIbevp+6QH8q7fjVhABHu/ZZnjtFkq7mVYS+5/pxA4Gh4XZM7uoNBM I9Xg== X-Received: by 10.68.191.5 with SMTP id gu5mr159695931pbc.145.1357278404933; Thu, 03 Jan 2013 21:46:44 -0800 (PST) Received: from yunshan ([114.255.72.194]) by mx.google.com with ESMTPS id oi3sm31620801pbb.1.2013.01.03.21.46.40 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 21:46:43 -0800 (PST) Date: Fri, 4 Jan 2013 13:47:10 +0800 From: "Tianpeng Zhang" To: "George Shuklin" , xen-api References: <201212311004494374333@gmail.com>, <50E274DA.5010000@gmail.com> X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.91[cn] Mime-Version: 1.0 Message-ID: <2013010413470662574412@gmail.com> Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: yunshandev List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5567433141901244288==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5567433141901244288== Content-Type: multipart/alternative; boundary="----=_001_NextPart853150083550_=----" This is a multi-part message in MIME format. ------=_001_NextPart853150083550_=---- Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 VGhhbmtzIEdlb3JnZSBmb3IgeW91ciBoZWxwLiBJIHRyaWVkIG1pZ3JhdGUgYW5vdGhlciBWTSwg aXQgZmluYWxseSBzdWNjZXNzZnVsbHkuIEkgZ3Vlc3MgdGhlIHJvb3QgY2F1c2UgaXMgdGhlcmUg aXMgYW4gSVNPIGF0dGFjaGVkIHRvIHRoZSBmYWlsdXJlIFZNLCB3aGljaCBpcyBhIHJlbW90ZSBD SUZTIGZpbGUuIE5vdGhpbmcgYXR0YWNoZWQgZm9yIHRoZSBWTSBtaWdyYXRlIHN1Y2Nlc3NmdWxs eS4gSSB3aWxsIGNoZWNrIHRoZSBsb2cgYXMgeW91IHNhaWQgd2hlbiB0aGlzIGtpbmQgb2YgaXNz dWUgaGFwcGVuIGFnYWluLg0KDQpUUA0KDQpGcm9tOiBHZW9yZ2UgU2h1a2xpbg0KRGF0ZTogMjAx My0wMS0wMSAxMzozMg0KVG86IHhlbi1hcGkNClN1YmplY3Q6IFJlOiBbWGVuLUFQSV0gWENQMS42 IHN0b3JhZ2UgeGVubW90aW9uIGlzc3VlDQpOb3QgeWV0LiBNeSB0ZXN0IG1hY2hpbmVzIGZseSBi ZXR3ZWVuIHBvb2xzIGxpa2UgYSBtYWdpYy4NCg0KUGxlYXNlIHByb3ZpZGVzIHhlbnNvdXJjZS5s b2cgcGllY2VzIGZyb20gYm90aCBzaWRlczogc2VuZGVyIGFuZCByZWNlaXZlci4gSSB0aGluaywg dGhleSBzaG91bGQgYmUgcG9vbCdzIG1hc3RlcnMgbG9ncy4NCg0KUFMgRG8gbm90IGZvcmdldCB0 byBzZXQgdXAgZGVmYXVsdC1zciBwb29sIHByb3BlcnR5IG9uIHJlY2VpdmVyLiANCg0KMzEuMTIu MjAxMiAwNjowNCwgVGlhbnBlbmcgWmhhbmcg0L/QuNGI0LXRgjoNCg0KSGkgQWxsLA0KDQpJIGdv dCBvbmUgaXNzdWUgd2l0aCB4Y3AxLjYgd2hlbiB0ZXN0aW5nIFZNIHN0b3JhZ2UgeGVuTW90aW9u IHRvIGFub3RoZXIgaG9zdC4gSXQgcmVwb3J0ZWQgZXJyb3IgYXMgYW4gImludGVybmFsIGVycm9y Ii4gSGF2ZSBhbnlvbmUgbWV0IHRoaXMgaXNzdWUgYmVmb3JlPyBPciBnaXZlIHNvbWUgdGlwcyBm b3IgdGhpcyBpc3N1ZT8NCg0KVGhhbmtzLiANCg0KW3Jvb3RAeGNwMTAyIH5dIyB4ZSB2bS1taWdy YXRlIGRlc3RpbmF0aW9uLXNyLXV1aWQ9MmE5ZTBjZDAtMGRkZi1iOWVmLTVlMzgtMmY1N2U0YWMz NjFlIHZtPUNlbnRPUzYtUFYgcmVtb3RlLW1hc3Rlcj0xMC4zMy4yLjEwMyByZW1vdGUtcGFzc3dv cmQ9cGFzc3dkIHJlbW90ZS11c2VybmFtZT1yb290DQpQZXJmb3JtaW5nIGEgU3RvcmFnZSBYZW5N b3Rpb24gbWlncmF0aW9uLiBZb3VyIFZNJ3MgVkRJcyB3aWxsIGJlIG1pZ3JhdGVkIHdpdGggdGhl IFZNLg0KV2lsbCBtaWdyYXRlIHRvIHJlbW90ZSBob3N0OiB4Y3AxMDMsIHVzaW5nIHJlbW90ZSBu ZXR3b3JrOiBQb29sLXdpZGUgbmV0d29yayBhc3NvY2lhdGVkIHdpdGggZXRoMC4gSGVyZSBpcyB0 aGUgVkRJIG1hcHBpbmc6DQpWREkgYTA5ZmM5NTQtZTVjYS00ZTAyLWFiYzktODc1YWZhNzYxNmY4 IC0+IFNSIDJhOWUwY2QwLTBkZGYtYjllZi01ZTM4LTJmNTdlNGFjMzYxZQ0KVkRJIDg0YmM3MTI5 LWFiOTUtNDI0YS1iYTExLWM4ZmYyZDFkNWZkNiAtPiBTUiAyYTllMGNkMC0wZGRmLWI5ZWYtNWUz OC0yZjU3ZTRhYzM2MWUNClRoZSBzZXJ2ZXIgZmFpbGVkIHRvIGhhbmRsZSB5b3VyIHJlcXVlc3Qs IGR1ZSB0byBhbiBpbnRlcm5hbCBlcnJvci4gIFRoZSBnaXZlbiBtZXNzYWdlIG1heSBnaXZlIGRl dGFpbHMgdXNlZnVsIGZvciBkZWJ1Z2dpbmcgdGhlIHByb2JsZW0uDQptZXNzYWdlOiBJbXBvcnQu SUZhaWx1cmUoMikNCltyb290QHhjcDEwMiB+XSMNCg0KIA0KDQpfX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KWGVuLWFwaSBtYWlsaW5nIGxpc3QNClhlbi1h cGlAbGlzdHMueGVuLm9yZw0KaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xp c3RpbmZvL3hlbi1hcGk= ------=_001_NextPart853150083550_=---- Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable =EF=BB=BF
Thanks George for your help. I tried migrate another VM, it finally=20 successfully. I guess the root cause is there is an ISO attached= to=20 the failure VM, which is a remote CIFS file. Nothing attached for the VM m= igrate=20 successfully. I will check the log as you said when this kind of issue hap= pen=20 again.
 
TP
 
Date: 2013-01-01 13:32
To: xen-api<= /DIV>
Subject: Re: [Xen-API] XCP1.6 storage xenmotion=20 issue
Not yet. My test machines fly between pools l= ike a=20 magic.

Please provides xensource.log pieces from both sides: sender= and=20 receiver. I think, they should be pool's masters logs.

PS Do not fo= rget=20 to set up default-sr pool property on receiver.

31.12.2012 06:04,=20 Tianpeng Zhang =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
Hi All,
 
I got one issue with xcp1.6 when testing VM storage xenMotion = to=20 another host. It reported error as an "internal error". Have a= nyone=20 met this issue before? Or give some tips for this issue?
 
Thanks. 
 
[root@xcp102 ~]# xe vm-migrate destination-sr-u= uid=3D2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e vm=3DCentOS6-PV remot= e-master=3D10.33.2.103 remote-password=3Dpasswd remote-username= =3Droot
Performing a Storage XenMotion migration. = Your VM's VDIs will be migrated with th= e VM.
Will migrate to remote host: xcp103, = using remote network: Pool-wide network associate= d with eth0. Here is the VDI mapping:
VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -> SR&nb= sp;2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e
VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -> SR&nb= sp;2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e
The server failed to handle your requ= est, due to an internal error.  The&nbs= p;given message may give details useful for&= nbsp;debugging the problem.
message: Import.IFailure(2)
[root@xcp102 ~]#


__=
_____________________________________________
Xen-api mailing list
=
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-ap=
i

------=_001_NextPart853150083550_=------ --===============5567433141901244288== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5567433141901244288==-- From xen-api-bounces@lists.xen.org Fri Jan 04 09:16:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 09:16:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr3OE-00029f-7H; Fri, 04 Jan 2013 09:16:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr3OB-00029K-ON for xen-api@lists.xen.org; Fri, 04 Jan 2013 09:16:32 +0000 Received: from [85.158.137.99:54194] by server-10.bemta-3.messagelabs.com id 8F/02-28305-AED96E05; Fri, 04 Jan 2013 09:16:26 +0000 X-Env-Sender: sergey.kruchatov@k21.com.ua X-Msg-Ref: server-4.tower-217.messagelabs.com!1357290982!17551010!1 X-Originating-IP: [209.85.223.171] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7338 invoked from network); 4 Jan 2013 09:16:23 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 09:16:23 -0000 Received: by mail-ie0-f171.google.com with SMTP id 17so19604152iea.30 for ; Fri, 04 Jan 2013 01:16:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=di/2i3bTCN68Kr9q5frzo58bD75VBnxzFpsS0QkGncs=; b=OcFHtwcDUvUhOxqWJ/ob9F/EsLhVnr3jcF1/ZUrVm0HIbd6cZvb8mg3H4A2tdCd37T EEGvUws5Zwrq3FqQz971ka2OqXEAwmzOI9b2/RSgHoWbYHZaWNpHPCUH+zKcQF/TnSiH hQG6IRSTUJ+o536HBQg2jNdxNVCpafQeF/3FkiiXt9lSgA/2RztM889M1lErsml7Bj8X 6+gGrxXNMzA6oH1vcbwVY3mCnht6cIECuksJDrLft6RZ4xHdj66g95Z6IjiFf3WuiZl4 2O1cqq7FvjqgyEKOce9En7EGrfVP0Jb39XMfRP5LkTsdt+EvbSJKD75r7GopQV6Jpb1O +hsg== MIME-Version: 1.0 Received: by 10.50.106.161 with SMTP id gv1mr43679740igb.4.1357290981634; Fri, 04 Jan 2013 01:16:21 -0800 (PST) Received: by 10.64.53.238 with HTTP; Fri, 4 Jan 2013 01:16:21 -0800 (PST) X-Originating-IP: [94.45.59.114] In-Reply-To: References: Date: Fri, 4 Jan 2013 11:16:21 +0200 Message-ID: From: "Kruchatov, Sergey" To: "xen-api@lists.xen.org" X-Gm-Message-State: ALoCoQkmTI6tbqHQAf9hoi7EHLY4jH0AISqTTNe8QZFGBheswhF3HgIVlCuPXkxwIvL4NrQXKLXv Subject: Re: [Xen-API] NFS Tuning - How To X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7300217428520475335==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7300217428520475335== Content-Type: multipart/alternative; boundary=e89a8f2354f9d132bf04d272eee5 --e89a8f2354f9d132bf04d272eee5 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi! Thanks, you give me a chance to share my expirience in straggle with poor NFS performance in XCP 1.6.x First of all, you just need to check mounting options issued by NFS client in XEN. You should see something like #mount /dev/sda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw) none on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) 10.1.0.42:/var/storage1/ISO on /var/run/sr-mount/0f61bf48-650b-41e6-183f-6231f763468f type nfs (rw,soft,timeo=3D133,retrans=3D2147483647,tcp,acregmax=3D1,acdirmax=3D1,add= r=3D10.1.0.42) # In my case you see final result, which works rather fine for me. But in case you will find noac option inside brackets - yes, it there! Open the /opt/xensource/sm/nfs.py and jump onto the 66 line. You would see near code something like options +=3D ',noac' # CA-27534 You just need to comment out this line of code and reattach you NFS or NFS ISO storage to check performance. In our case the VM protection policy archiving process to NFS storage became 10x faster. You can do even more and google the "noac CA-27534". I sure you will find about year old patch https://github.com/mcclurmc/xcp-storage-managers/pull/1 - options +=3D ',noac' # CA-27534 72** + 73** + # Attribute caching can lead to stale data, so we can try to minimize = these 74** + # problems by reducing the caching time. Going right down to zero does= not 75** + # remove race conditions (rather just makes them more unlikely) while 76** + # introducing some serious performance penalties for the NFS filesyste= m. 77** + # So we get 99% of the way there without the massive performance penal= ties 78** + # by going for 1 second. 79** + # The correct solution to cases where you need up-to-date information = is to 80** + # use file locking primitives, as the lock operation will force the 81** + # getattr() and ensure no concurrent operations. 82** + options +=3D ',acregmax=3D1' 83** + options +=3D ',acdirmax=3D1' noac option suddenly found in XCP 1.6.x as well as in XS 6.x. I thind develepers can describe why mentioned above patch was not pulled to final version. Mentioned above noac option definately didn't present in XS 5.6. I did not check it in XCP 1.4.9. Hope above will help. Finally i want to note that you have to edit manually nfs.py on every member of pool. 2013/1/4 Juan Lorenzana > Okay, so I have two Dell PowerEdge server and we are using with a NAS > solution called TrueNAS by IX Systems. This is basically a ZFS version 2= 8 > implementation for the NAS solution.**** > > ** ** > > Anyway, when we mount our NFS storage repositories over our 10GB > interfaces on the Dell PowerEdge server and the NAS also has 10GB, we get > horrible NFS performance. If I mount a CIFS repository, we get blazing > fast performance.**** > > ** ** > > So my question is how would I go about tuning the different NFS options t= o > do various tests. A quick scan on Google produced nothing on how to do > this. My thoughts are to either pass NFS options in Xen Center under the > Advanced Options input box or edit the nfs.py file. I tried using the > Advanced Options but I do not think that worked.**** > > ** ** > > I am currently running XCP 1.5 but plan on migrating to 1.6 in the next > few months. I would really like to tune the NFS first on 1.5 so that I c= an > compare performance to 1.6. **** > > ** ** > > Any pointers to try to improve NFS performance?**** > > ** ** > > I am getting about a 6MB/s write and 20MB/s read on the NFS storage > repository when doing iozone tests inside a VM. With a 10GB interface I > should be in the 100=92s. If I do iozone test on the TrueNAS directly, I= get > about 600MB/s on average. When doing iozone testing on VM running Window= s > using CIFS from the same storage solution, we are getting close to 180 MB= /s > so I know the issue is not the storage repository, so I am guessing it ha= s > to do with NFS tuning.**** > > > Any help is appreciated. Thanks.**** > > ** ** > > Juan**** > > ** ** > > ** ** > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --=20 WBR Sergey Kruchatov --e89a8f2354f9d132bf04d272eee5 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi!

Thanks, you give me a chance to share my expirience = in straggle with poor NFS performance in XCP 1.6.x

First of all, you just need to check mounting options issued by NFS client= in XEN.

You should see something like

= #mount
/dev/sda1 on / type ext3 (rw)
none on /proc = type proc (rw)
none on /sys type sysfs (rw)
none on /de= v/pts type devpts (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt= _misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs typ= e rpc_pipefs (rw)
10.1.0.42:/var/storage1/ISO on /var/run/sr-moun= t/0f61bf48-650b-41e6-183f-6231f763468f type nfs (rw,soft,timeo=3D133,retran= s=3D2147483647,tcp,acregmax=3D1,acdirmax=3D1,addr=3D10.1.0.42)
#

In my case you see final result, which = works rather fine for me.
But in case you will find noac option i= nside brackets - yes, it there!

Open the=A0/opt/xe= nsource/sm/nfs.py and jump onto the 66 line.
You would see=A0near code something like=A0

o= ptions +=3D ',noac' # CA-27534

You just ne= ed to comment out this line of code and reattach you NFS or NFS ISO storage= to check performance.
In our case the VM protection policy archiving process to NFS storage = became 10x faster.

You can do even more and google= the "noac CA-27534".

I sure you will fi= nd about year old patch=A0


-=A0=A0=A0=A0options=A0+=3D=A0',noac=
'=A0#=A0CA-27534
=A0 72
+
=A0 73
+=A0=A0=A0=A0#=A0Attribute=A0caching=A0can=A0lead=A0to=A0stale=A0data,=A0so=
=A0we=A0can=A0try=A0to=A0minimize=A0these
=A0 74
+=A0=A0=A0=A0#=A0problems=A0by=A0reducing=A0the=A0caching=A0time.=A0Going=
=A0right=A0down=A0to=A0zero=A0does=A0not
=A0 75
+=A0=A0=A0=A0#=A0remove=A0race=A0conditions=A0(rather=A0just=A0makes=A0them=
=A0more=A0unlikely)=A0while
=A0 76
+=A0=A0=A0=A0#=A0introducing=A0some=A0serious=A0performance=A0penalties=A0f=
or=A0the=A0NFS=A0filesystem.
=A0 77
+=A0=A0=A0=A0#=A0So=A0we=A0get=A099%=A0of=A0the=A0way=A0there=A0without=A0t=
he=A0massive=A0performance=A0penalties
=A0 78
+=A0=A0=A0=A0#=A0by=A0going=A0for=A01=A0second.
=A0 79
+=A0=A0=A0=A0#=A0The=A0correct=A0solution=A0to=A0cases=A0where=A0you=A0need=
=A0up-to-date=A0information=A0is=A0to
=A0 80
+=A0=A0=A0=A0#=A0use=A0file=A0locking=A0primitives,=A0as=A0the=A0lock=A0ope=
ration=A0will=A0force=A0the
=A0 81
+=A0=A0=A0=A0#=A0getattr()=A0and=A0ensure=A0no=A0concurrent=A0operations.
=A0 82
+=A0=A0=A0=A0options=A0+=3D=A0',acregmax=3D1'
=A0 83
+=A0=A0=A0=A0options=A0+=3D=A0',acdirmax=3D1'

noac option suddenly found in XCP 1.6.x= as well as in XS 6.x.

I thind develepers can desc= ribe why mentioned=A0above=A0patch was not pulled to final version.

Mentioned above noac option definately didn't prese= nt in XS 5.6. I did not check it in XCP 1.4.9.

Hop= e above will help.

Final= ly i want to note that you have to edit manually nfs.py on every member of = pool.

2013/1/4 Juan Lorenzana <juan@jelsupport.com>

Okay, so I have two Dell PowerEdge server and we are using with a NAS s= olution called TrueNAS by IX Systems.=A0 This is basically a ZFS version 28= implementation for the NAS solution.

=A0

Anyway, = when we mount our NFS storage repositories over our 10GB interfaces on the = Dell PowerEdge server and the NAS also has 10GB, we get horrible NFS perfor= mance.=A0 If I mount a CIFS repository, we get blazing fast performance.=

=A0

So my qu= estion is how would I go about tuning the different NFS options to do vario= us tests.=A0 A quick scan on Google produced nothing on how to do this.=A0 = My thoughts are to either pass NFS options in Xen Center under the
Advanced Options input box or edit the nfs.py file.=A0 I tried using the Ad= vanced Options but I do not think that worked.

=A0

I am currently runn= ing XCP 1.5 but plan on migrating to 1.6 in the next few months.=A0 I would= really like to tune the NFS first on 1.5 so that I can compare performance= to 1.6.=A0

=A0

Any poin= ters to try to improve NFS performance?

=A0

I am getting about a 6MB/s= write and 20MB/s read on the NFS storage repository when doing iozone test= s inside a VM.=A0 With a 10GB interface I should be in the 100=92s.=A0 If I= do iozone test on the TrueNAS directly, I get about 600MB/s on average.=A0= When doing iozone testing on VM running Windows using CIFS from the same s= torage solution, we are getting close to 180 MB/s so I know the issue is no= t the storage repository, so I am guessing it has to do with NFS tuning.=


Any help is appreciated.=A0 Thanks.

=A0

Juan

=A0

=A0


_________= ______________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




--
WBR
=
Sergey Kruchatov
--e89a8f2354f9d132bf04d272eee5-- --===============7300217428520475335== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7300217428520475335==-- From xen-api-bounces@lists.xen.org Fri Jan 04 09:16:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 09:16:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr3OE-00029f-7H; Fri, 04 Jan 2013 09:16:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr3OB-00029K-ON for xen-api@lists.xen.org; Fri, 04 Jan 2013 09:16:32 +0000 Received: from [85.158.137.99:54194] by server-10.bemta-3.messagelabs.com id 8F/02-28305-AED96E05; Fri, 04 Jan 2013 09:16:26 +0000 X-Env-Sender: sergey.kruchatov@k21.com.ua X-Msg-Ref: server-4.tower-217.messagelabs.com!1357290982!17551010!1 X-Originating-IP: [209.85.223.171] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7338 invoked from network); 4 Jan 2013 09:16:23 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 09:16:23 -0000 Received: by mail-ie0-f171.google.com with SMTP id 17so19604152iea.30 for ; Fri, 04 Jan 2013 01:16:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=di/2i3bTCN68Kr9q5frzo58bD75VBnxzFpsS0QkGncs=; b=OcFHtwcDUvUhOxqWJ/ob9F/EsLhVnr3jcF1/ZUrVm0HIbd6cZvb8mg3H4A2tdCd37T EEGvUws5Zwrq3FqQz971ka2OqXEAwmzOI9b2/RSgHoWbYHZaWNpHPCUH+zKcQF/TnSiH hQG6IRSTUJ+o536HBQg2jNdxNVCpafQeF/3FkiiXt9lSgA/2RztM889M1lErsml7Bj8X 6+gGrxXNMzA6oH1vcbwVY3mCnht6cIECuksJDrLft6RZ4xHdj66g95Z6IjiFf3WuiZl4 2O1cqq7FvjqgyEKOce9En7EGrfVP0Jb39XMfRP5LkTsdt+EvbSJKD75r7GopQV6Jpb1O +hsg== MIME-Version: 1.0 Received: by 10.50.106.161 with SMTP id gv1mr43679740igb.4.1357290981634; Fri, 04 Jan 2013 01:16:21 -0800 (PST) Received: by 10.64.53.238 with HTTP; Fri, 4 Jan 2013 01:16:21 -0800 (PST) X-Originating-IP: [94.45.59.114] In-Reply-To: References: Date: Fri, 4 Jan 2013 11:16:21 +0200 Message-ID: From: "Kruchatov, Sergey" To: "xen-api@lists.xen.org" X-Gm-Message-State: ALoCoQkmTI6tbqHQAf9hoi7EHLY4jH0AISqTTNe8QZFGBheswhF3HgIVlCuPXkxwIvL4NrQXKLXv Subject: Re: [Xen-API] NFS Tuning - How To X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7300217428520475335==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7300217428520475335== Content-Type: multipart/alternative; boundary=e89a8f2354f9d132bf04d272eee5 --e89a8f2354f9d132bf04d272eee5 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi! Thanks, you give me a chance to share my expirience in straggle with poor NFS performance in XCP 1.6.x First of all, you just need to check mounting options issued by NFS client in XEN. You should see something like #mount /dev/sda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw) none on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) 10.1.0.42:/var/storage1/ISO on /var/run/sr-mount/0f61bf48-650b-41e6-183f-6231f763468f type nfs (rw,soft,timeo=3D133,retrans=3D2147483647,tcp,acregmax=3D1,acdirmax=3D1,add= r=3D10.1.0.42) # In my case you see final result, which works rather fine for me. But in case you will find noac option inside brackets - yes, it there! Open the /opt/xensource/sm/nfs.py and jump onto the 66 line. You would see near code something like options +=3D ',noac' # CA-27534 You just need to comment out this line of code and reattach you NFS or NFS ISO storage to check performance. In our case the VM protection policy archiving process to NFS storage became 10x faster. You can do even more and google the "noac CA-27534". I sure you will find about year old patch https://github.com/mcclurmc/xcp-storage-managers/pull/1 - options +=3D ',noac' # CA-27534 72** + 73** + # Attribute caching can lead to stale data, so we can try to minimize = these 74** + # problems by reducing the caching time. Going right down to zero does= not 75** + # remove race conditions (rather just makes them more unlikely) while 76** + # introducing some serious performance penalties for the NFS filesyste= m. 77** + # So we get 99% of the way there without the massive performance penal= ties 78** + # by going for 1 second. 79** + # The correct solution to cases where you need up-to-date information = is to 80** + # use file locking primitives, as the lock operation will force the 81** + # getattr() and ensure no concurrent operations. 82** + options +=3D ',acregmax=3D1' 83** + options +=3D ',acdirmax=3D1' noac option suddenly found in XCP 1.6.x as well as in XS 6.x. I thind develepers can describe why mentioned above patch was not pulled to final version. Mentioned above noac option definately didn't present in XS 5.6. I did not check it in XCP 1.4.9. Hope above will help. Finally i want to note that you have to edit manually nfs.py on every member of pool. 2013/1/4 Juan Lorenzana > Okay, so I have two Dell PowerEdge server and we are using with a NAS > solution called TrueNAS by IX Systems. This is basically a ZFS version 2= 8 > implementation for the NAS solution.**** > > ** ** > > Anyway, when we mount our NFS storage repositories over our 10GB > interfaces on the Dell PowerEdge server and the NAS also has 10GB, we get > horrible NFS performance. If I mount a CIFS repository, we get blazing > fast performance.**** > > ** ** > > So my question is how would I go about tuning the different NFS options t= o > do various tests. A quick scan on Google produced nothing on how to do > this. My thoughts are to either pass NFS options in Xen Center under the > Advanced Options input box or edit the nfs.py file. I tried using the > Advanced Options but I do not think that worked.**** > > ** ** > > I am currently running XCP 1.5 but plan on migrating to 1.6 in the next > few months. I would really like to tune the NFS first on 1.5 so that I c= an > compare performance to 1.6. **** > > ** ** > > Any pointers to try to improve NFS performance?**** > > ** ** > > I am getting about a 6MB/s write and 20MB/s read on the NFS storage > repository when doing iozone tests inside a VM. With a 10GB interface I > should be in the 100=92s. If I do iozone test on the TrueNAS directly, I= get > about 600MB/s on average. When doing iozone testing on VM running Window= s > using CIFS from the same storage solution, we are getting close to 180 MB= /s > so I know the issue is not the storage repository, so I am guessing it ha= s > to do with NFS tuning.**** > > > Any help is appreciated. Thanks.**** > > ** ** > > Juan**** > > ** ** > > ** ** > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --=20 WBR Sergey Kruchatov --e89a8f2354f9d132bf04d272eee5 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi!

Thanks, you give me a chance to share my expirience = in straggle with poor NFS performance in XCP 1.6.x

First of all, you just need to check mounting options issued by NFS client= in XEN.

You should see something like

= #mount
/dev/sda1 on / type ext3 (rw)
none on /proc = type proc (rw)
none on /sys type sysfs (rw)
none on /de= v/pts type devpts (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt= _misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs typ= e rpc_pipefs (rw)
10.1.0.42:/var/storage1/ISO on /var/run/sr-moun= t/0f61bf48-650b-41e6-183f-6231f763468f type nfs (rw,soft,timeo=3D133,retran= s=3D2147483647,tcp,acregmax=3D1,acdirmax=3D1,addr=3D10.1.0.42)
#

In my case you see final result, which = works rather fine for me.
But in case you will find noac option i= nside brackets - yes, it there!

Open the=A0/opt/xe= nsource/sm/nfs.py and jump onto the 66 line.
You would see=A0near code something like=A0

o= ptions +=3D ',noac' # CA-27534

You just ne= ed to comment out this line of code and reattach you NFS or NFS ISO storage= to check performance.
In our case the VM protection policy archiving process to NFS storage = became 10x faster.

You can do even more and google= the "noac CA-27534".

I sure you will fi= nd about year old patch=A0


-=A0=A0=A0=A0options=A0+=3D=A0',noac=
'=A0#=A0CA-27534
=A0 72
+
=A0 73
+=A0=A0=A0=A0#=A0Attribute=A0caching=A0can=A0lead=A0to=A0stale=A0data,=A0so=
=A0we=A0can=A0try=A0to=A0minimize=A0these
=A0 74
+=A0=A0=A0=A0#=A0problems=A0by=A0reducing=A0the=A0caching=A0time.=A0Going=
=A0right=A0down=A0to=A0zero=A0does=A0not
=A0 75
+=A0=A0=A0=A0#=A0remove=A0race=A0conditions=A0(rather=A0just=A0makes=A0them=
=A0more=A0unlikely)=A0while
=A0 76
+=A0=A0=A0=A0#=A0introducing=A0some=A0serious=A0performance=A0penalties=A0f=
or=A0the=A0NFS=A0filesystem.
=A0 77
+=A0=A0=A0=A0#=A0So=A0we=A0get=A099%=A0of=A0the=A0way=A0there=A0without=A0t=
he=A0massive=A0performance=A0penalties
=A0 78
+=A0=A0=A0=A0#=A0by=A0going=A0for=A01=A0second.
=A0 79
+=A0=A0=A0=A0#=A0The=A0correct=A0solution=A0to=A0cases=A0where=A0you=A0need=
=A0up-to-date=A0information=A0is=A0to
=A0 80
+=A0=A0=A0=A0#=A0use=A0file=A0locking=A0primitives,=A0as=A0the=A0lock=A0ope=
ration=A0will=A0force=A0the
=A0 81
+=A0=A0=A0=A0#=A0getattr()=A0and=A0ensure=A0no=A0concurrent=A0operations.
=A0 82
+=A0=A0=A0=A0options=A0+=3D=A0',acregmax=3D1'
=A0 83
+=A0=A0=A0=A0options=A0+=3D=A0',acdirmax=3D1'

noac option suddenly found in XCP 1.6.x= as well as in XS 6.x.

I thind develepers can desc= ribe why mentioned=A0above=A0patch was not pulled to final version.

Mentioned above noac option definately didn't prese= nt in XS 5.6. I did not check it in XCP 1.4.9.

Hop= e above will help.

Final= ly i want to note that you have to edit manually nfs.py on every member of = pool.

2013/1/4 Juan Lorenzana <juan@jelsupport.com>

Okay, so I have two Dell PowerEdge server and we are using with a NAS s= olution called TrueNAS by IX Systems.=A0 This is basically a ZFS version 28= implementation for the NAS solution.

=A0

Anyway, = when we mount our NFS storage repositories over our 10GB interfaces on the = Dell PowerEdge server and the NAS also has 10GB, we get horrible NFS perfor= mance.=A0 If I mount a CIFS repository, we get blazing fast performance.=

=A0

So my qu= estion is how would I go about tuning the different NFS options to do vario= us tests.=A0 A quick scan on Google produced nothing on how to do this.=A0 = My thoughts are to either pass NFS options in Xen Center under the
Advanced Options input box or edit the nfs.py file.=A0 I tried using the Ad= vanced Options but I do not think that worked.

=A0

I am currently runn= ing XCP 1.5 but plan on migrating to 1.6 in the next few months.=A0 I would= really like to tune the NFS first on 1.5 so that I can compare performance= to 1.6.=A0

=A0

Any poin= ters to try to improve NFS performance?

=A0

I am getting about a 6MB/s= write and 20MB/s read on the NFS storage repository when doing iozone test= s inside a VM.=A0 With a 10GB interface I should be in the 100=92s.=A0 If I= do iozone test on the TrueNAS directly, I get about 600MB/s on average.=A0= When doing iozone testing on VM running Windows using CIFS from the same s= torage solution, we are getting close to 180 MB/s so I know the issue is no= t the storage repository, so I am guessing it has to do with NFS tuning.=


Any help is appreciated.=A0 Thanks.

=A0

Juan

=A0

=A0


_________= ______________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




--
WBR
=
Sergey Kruchatov
--e89a8f2354f9d132bf04d272eee5-- --===============7300217428520475335== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7300217428520475335==-- From xen-api-bounces@lists.xen.org Fri Jan 04 10:42:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 10:42:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr4je-0003Yu-NQ; Fri, 04 Jan 2013 10:42:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr2jO-0000pw-Kf for xen-api@lists.xen.org; Fri, 04 Jan 2013 08:34:23 +0000 Received: from [85.158.137.99:46083] by server-9.bemta-3.messagelabs.com id 26/C2-11948-D0496E05; Fri, 04 Jan 2013 08:34:21 +0000 X-Env-Sender: sergey.kruchatov@k21.com.ua X-Msg-Ref: server-12.tower-217.messagelabs.com!1357288458!15535397!1 X-Originating-IP: [209.85.210.178] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12368 invoked from network); 4 Jan 2013 08:34:20 -0000 Received: from mail-ia0-f178.google.com (HELO mail-ia0-f178.google.com) (209.85.210.178) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 08:34:20 -0000 Received: by mail-ia0-f178.google.com with SMTP id k25so13815152iah.9 for ; Fri, 04 Jan 2013 00:34:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=wq6xwdZLln3G6ZJLaLh4CQYvQGUDAT8T20gv30iOBLM=; b=VKce50yiJa1j4Gd2/Tyf9AvDwLXnG4l9nRsgw9FIqNkEENgnjL3gWm2AXqobKBjyti /69a8/kEauQ4R/IJB9B8LcSxK2Tplx8Yc9TXAnmXEUu00rlhq3/RlrwDVoSxkk8i6foU BZzQX5LV686LHyxEQU06Cd3zYMAROAVQd+mBZFvvXbNDRNxZS44yJatcyz0kW2Uuc2op /IV1Z3cZXYAV1hXc6fB31Gb9ncxCb8dZAwbYUiACHCWA4nnZRy6+jAnZUqWbbFTR1hiK iEE1O2+QfNPWAurOB6AQklYve7IJvOB+8VxAbFTPb7bn0PpfmZ+UvRRTKxObSmkaaaBd Shbg== X-Received: by 10.50.56.232 with SMTP id d8mr40288648igq.112.1357288458549; Fri, 04 Jan 2013 00:34:18 -0800 (PST) Received: from mail-oa0-f51.google.com (mail-oa0-f51.google.com [209.85.219.51]) by mx.google.com with ESMTPS id c4sm32818839oee.0.2013.01.04.00.34.16 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Jan 2013 00:34:17 -0800 (PST) Received: by mail-oa0-f51.google.com with SMTP id n12so14771870oag.38 for ; Fri, 04 Jan 2013 00:34:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.22.164 with SMTP id e4mr29535500oef.87.1357288456352; Fri, 04 Jan 2013 00:34:16 -0800 (PST) Received: by 10.76.10.233 with HTTP; Fri, 4 Jan 2013 00:34:16 -0800 (PST) In-Reply-To: References: Date: Fri, 4 Jan 2013 10:34:16 +0200 Message-ID: From: hook To: "xen-api@lists.xen.org" X-Gm-Message-State: ALoCoQmYJVtoOHD6gRLrNnpQ+ndFmRLUR3HVOhvbaTQiRUBFf0I31gNrIevPHF/LGNTjclI1AywH X-Mailman-Approved-At: Fri, 04 Jan 2013 10:42:45 +0000 Subject: Re: [Xen-API] NFS Tuning - How To X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4968251816575745902==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4968251816575745902== Content-Type: multipart/alternative; boundary=e89a8fb203ee4c755704d272588f --e89a8fb203ee4c755704d272588f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi! Thanks, you give me a chance to share my expirience in straggle with poor NFS performance in XCP 1.6.x First of all, you just need to check mounting options issued by NFS client in XEN. You should see something like #mount /dev/sda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw) none on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) 10.1.0.42:/var/storage1/ISO on /var/run/sr-mount/0f61bf48-650b-41e6-183f-6231f763468f type nfs (rw,soft,timeo=3D133,retrans=3D2147483647,tcp,acregmax=3D1,acdirmax=3D1,add= r=3D10.1.0.42) # In my case you see final result, which works rather fine for me. But in case you will find noac option inside brackets - yes, it there! Open the /opt/xensource/sm/nfs.py and jump onto the 66 line. You would see near code something like options +=3D ',noac' # CA-27534 You just need to comment out this line of code and reattach you NFS or NFS ISO storage to check performance. In our case the VM protection policy archiving process to NFS storage became 10x faster. You can do even more and google the "noac CA-27534". I sure you will find about year old patch https://github.com/mcclurmc/xcp-storage-managers/pull/1 - options +=3D ',noac' # CA-27534 72** + 73** + # Attribute caching can lead to stale data, so we can try to minimize = these 74** + # problems by reducing the caching time. Going right down to zero does= not 75** + # remove race conditions (rather just makes them more unlikely) while 76** + # introducing some serious performance penalties for the NFS filesyste= m. 77** + # So we get 99% of the way there without the massive performance penal= ties 78** + # by going for 1 second. 79** + # The correct solution to cases where you need up-to-date information = is to 80** + # use file locking primitives, as the lock operation will force the 81** + # getattr() and ensure no concurrent operations. 82** + options +=3D ',acregmax=3D1' 83** + options +=3D ',acdirmax=3D1' noac option suddenly found in XCP 1.6.x as well as in XS 6.x. I thind develepers can describe why mentioned above patch was not pulled to final version. Mentioned above noac option definately didn't present in XS 5.6. I did not check it in XCP 1.4.9. Hope above will help. Finally i want to note that you have to edit manually nfs.py on every member of pool. 2013/1/4 Juan Lorenzana > Okay, so I have two Dell PowerEdge server and we are using with a NAS > solution called TrueNAS by IX Systems. This is basically a ZFS version 2= 8 > implementation for the NAS solution.**** > > ** ** > > Anyway, when we mount our NFS storage repositories over our 10GB > interfaces on the Dell PowerEdge server and the NAS also has 10GB, we get > horrible NFS performance. If I mount a CIFS repository, we get blazing > fast performance.**** > > ** ** > > So my question is how would I go about tuning the different NFS options t= o > do various tests. A quick scan on Google produced nothing on how to do > this. My thoughts are to either pass NFS options in Xen Center under the > Advanced Options input box or edit the nfs.py file. I tried using the > Advanced Options but I do not think that worked.**** > > ** ** > > I am currently running XCP 1.5 but plan on migrating to 1.6 in the next > few months. I would really like to tune the NFS first on 1.5 so that I c= an > compare performance to 1.6. **** > > ** ** > > Any pointers to try to improve NFS performance?**** > > ** ** > > I am getting about a 6MB/s write and 20MB/s read on the NFS storage > repository when doing iozone tests inside a VM. With a 10GB interface I > should be in the 100=E2=80=99s. If I do iozone test on the TrueNAS direc= tly, I get > about 600MB/s on average. When doing iozone testing on VM running Window= s > using CIFS from the same storage solution, we are getting close to 180 MB= /s > so I know the issue is not the storage repository, so I am guessing it ha= s > to do with NFS tuning.**** > > > Any help is appreciated. Thanks.**** > > ** ** > > Juan**** > > ** ** > > ** ** > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --=20 WBR Sergey Kruchatov --e89a8fb203ee4c755704d272588f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi!

Thanks, you give me a chance = to share my expirience in straggle with poor NFS performance in XCP 1.6.x

First of all, you just need to check mo= unting options issued by NFS client in XEN.

You should see something like

#mount
/dev/sda1 on / type ext3 (rw)
<= /div>
none on /proc type proc (rw)
none on /sys type sysfs (r= w)
none on /dev/pts type devpts (rw)
none on /dev/shm type tmpf= s (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
10.1.0.42:/var/storage1/ISO on /var/run/sr-mount/0f61bf48-650b-41e6-183f-62= 31f763468f type nfs (rw,soft,timeo=3D133,retrans=3D2147483647,tcp,acregmax= =3D1,acdirmax=3D1,addr=3D10.1.0.42)
#

In my case you see final result, which works rather fine for me.
But in case you will find noac option inside brackets - yes, it there= !

Open the=C2=A0/opt/xensource/sm/nfs.= py and jump onto the 66 line.
You would see=C2=A0near code something like=C2=A0

options +=3D ',noac' # CA-27534
You just need to comment out this line of code and reatt= ach you NFS or NFS ISO storage to check performance.
In our case the VM protection policy archiving process to NFS st= orage became 10x faster.

You can do ev= en more and google the "noac CA-27534".

I sure you will find about year old patch=C2=A0
= 

-=C2=A0=C2=A0=C2=A0=C2=A0options=C2=A0+=3D=C2=A0&#=
39;,noac'=C2=A0#=C2=A0CA-27534
=C2=A072 
+
=C2=A073 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0Attribute=C2=A0caching=C2=A0can=C2=A0lead=
=C2=A0to=C2=A0stale=C2=A0data,=C2=A0so=C2=A0we=C2=A0can=C2=A0try=C2=A0to=C2=
=A0minimize=C2=A0these
=C2=A074 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0problems=C2=A0by=C2=A0reducing=C2=A0the=C2=
=A0caching=C2=A0time.=C2=A0Going=C2=A0right=C2=A0down=C2=A0to=C2=A0zero=C2=
=A0does=C2=A0not
=C2=A075 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0remove=C2=A0race=C2=A0conditions=C2=A0(rath=
er=C2=A0just=C2=A0makes=C2=A0them=C2=A0more=C2=A0unlikely)=C2=A0while
=
=C2=A076 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0introducing=C2=A0some=C2=A0serious=C2=A0per=
formance=C2=A0penalties=C2=A0for=C2=A0the=C2=A0NFS=C2=A0filesystem.
=C2=A077 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0So=C2=A0we=C2=A0get=C2=A099%=C2=A0of=C2=A0t=
he=C2=A0way=C2=A0there=C2=A0without=C2=A0the=C2=A0massive=C2=A0performance=
=C2=A0penalties
=C2=A078 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0by=C2=A0going=C2=A0for=C2=A01=C2=A0second.<=
/pre>
=C2=A079 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0The=C2=A0correct=C2=A0solution=C2=A0to=C2=
=A0cases=C2=A0where=C2=A0you=C2=A0need=C2=A0up-to-date=C2=A0information=C2=
=A0is=C2=A0to
=C2=A080 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0use=C2=A0file=C2=A0locking=C2=A0primitives,=
=C2=A0as=C2=A0the=C2=A0lock=C2=A0operation=C2=A0will=C2=A0force=C2=A0the
=C2=A081 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0getattr()=C2=A0and=C2=A0ensure=C2=A0no=C2=
=A0concurrent=C2=A0operations.
=C2=A082 
+=C2=A0=C2=A0=C2=A0=C2=A0options=C2=A0+=3D=C2=A0',acregmax=3D1'
=C2=A083 
+=C2=A0=C2=A0=C2=A0=C2=A0options=C2=A0+=3D=C2=A0',acdirmax=3D1'

noac opti= on suddenly found in XCP 1.6.x as well as in XS 6.x.

I thind develepers can describe why mentioned=C2=A0above=C2= =A0patch was not pulled to final version.

Mentioned above noac option definately didn= 't present in XS 5.6. I did not check it in XCP 1.4.9.
=
Hope above will help.

Finally i want to note that you = have to edit manually nfs.py on every member of pool.

2013/1/4 Juan Lorenzana <juan@= jelsupport.com>
Okay, so I have two Dell PowerEdge server and we are using with a NAS solut= ion called TrueNAS by IX Systems.=C2=A0 This is basically a ZFS version 28 = implementation for the NAS solution.

= =C2=A0

Anyway, when we mount our NFS storage repositories over our 1= 0GB interfaces on the Dell PowerEdge server and the NAS also has 10GB, we g= et horrible NFS performance.=C2=A0 If I mount a CIFS repository, we get bla= zing fast performance.

=C2=A0

So my question is how w= ould I go about tuning the different NFS options to do various tests.=C2=A0= A quick scan on Google produced nothing on how to do this.=C2=A0 My though= ts are to either pass NFS options in Xen Center under the
Advanced Options input box or edit the nfs.py file.=C2=A0 I tried using the= Advanced Options but I do not think that worked.

=C2=A0

I am currently running XCP 1.5 = but plan on migrating to 1.6 in the next few months.=C2=A0 I would really l= ike to tune the NFS first on 1.5 so that I can compare performance to 1.6.= =C2=A0

=C2=A0

Any pointers to try to = improve NFS performance?

=C2=A0

I am getting about a 6MB/s write and 20MB/s read on the = NFS storage repository when doing iozone tests inside a VM.=C2=A0 With a 10= GB interface I should be in the 100=E2=80=99s.=C2=A0 If I do iozone test on= the TrueNAS directly, I get about 600MB/s on average.=C2=A0 When doing ioz= one testing on VM running Windows using CIFS from the same storage solution= , we are getting close to 180 MB/s so I know the issue is not the storage r= epository, so I am guessing it has to do with NFS tuning.


Any help is appreciated.=C2=A0 Thanks.

=C2=A0

Jua= n

=C2=A0

=C2=A0


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




--
WBR
<= br>Sergey Kruchatov
--e89a8fb203ee4c755704d272588f-- --===============4968251816575745902== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4968251816575745902==-- From xen-api-bounces@lists.xen.org Fri Jan 04 10:42:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 10:42:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr4je-0003Yu-NQ; Fri, 04 Jan 2013 10:42:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr2jO-0000pw-Kf for xen-api@lists.xen.org; Fri, 04 Jan 2013 08:34:23 +0000 Received: from [85.158.137.99:46083] by server-9.bemta-3.messagelabs.com id 26/C2-11948-D0496E05; Fri, 04 Jan 2013 08:34:21 +0000 X-Env-Sender: sergey.kruchatov@k21.com.ua X-Msg-Ref: server-12.tower-217.messagelabs.com!1357288458!15535397!1 X-Originating-IP: [209.85.210.178] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12368 invoked from network); 4 Jan 2013 08:34:20 -0000 Received: from mail-ia0-f178.google.com (HELO mail-ia0-f178.google.com) (209.85.210.178) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 08:34:20 -0000 Received: by mail-ia0-f178.google.com with SMTP id k25so13815152iah.9 for ; Fri, 04 Jan 2013 00:34:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=wq6xwdZLln3G6ZJLaLh4CQYvQGUDAT8T20gv30iOBLM=; b=VKce50yiJa1j4Gd2/Tyf9AvDwLXnG4l9nRsgw9FIqNkEENgnjL3gWm2AXqobKBjyti /69a8/kEauQ4R/IJB9B8LcSxK2Tplx8Yc9TXAnmXEUu00rlhq3/RlrwDVoSxkk8i6foU BZzQX5LV686LHyxEQU06Cd3zYMAROAVQd+mBZFvvXbNDRNxZS44yJatcyz0kW2Uuc2op /IV1Z3cZXYAV1hXc6fB31Gb9ncxCb8dZAwbYUiACHCWA4nnZRy6+jAnZUqWbbFTR1hiK iEE1O2+QfNPWAurOB6AQklYve7IJvOB+8VxAbFTPb7bn0PpfmZ+UvRRTKxObSmkaaaBd Shbg== X-Received: by 10.50.56.232 with SMTP id d8mr40288648igq.112.1357288458549; Fri, 04 Jan 2013 00:34:18 -0800 (PST) Received: from mail-oa0-f51.google.com (mail-oa0-f51.google.com [209.85.219.51]) by mx.google.com with ESMTPS id c4sm32818839oee.0.2013.01.04.00.34.16 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Jan 2013 00:34:17 -0800 (PST) Received: by mail-oa0-f51.google.com with SMTP id n12so14771870oag.38 for ; Fri, 04 Jan 2013 00:34:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.22.164 with SMTP id e4mr29535500oef.87.1357288456352; Fri, 04 Jan 2013 00:34:16 -0800 (PST) Received: by 10.76.10.233 with HTTP; Fri, 4 Jan 2013 00:34:16 -0800 (PST) In-Reply-To: References: Date: Fri, 4 Jan 2013 10:34:16 +0200 Message-ID: From: hook To: "xen-api@lists.xen.org" X-Gm-Message-State: ALoCoQmYJVtoOHD6gRLrNnpQ+ndFmRLUR3HVOhvbaTQiRUBFf0I31gNrIevPHF/LGNTjclI1AywH X-Mailman-Approved-At: Fri, 04 Jan 2013 10:42:45 +0000 Subject: Re: [Xen-API] NFS Tuning - How To X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4968251816575745902==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4968251816575745902== Content-Type: multipart/alternative; boundary=e89a8fb203ee4c755704d272588f --e89a8fb203ee4c755704d272588f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi! Thanks, you give me a chance to share my expirience in straggle with poor NFS performance in XCP 1.6.x First of all, you just need to check mounting options issued by NFS client in XEN. You should see something like #mount /dev/sda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw) none on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) 10.1.0.42:/var/storage1/ISO on /var/run/sr-mount/0f61bf48-650b-41e6-183f-6231f763468f type nfs (rw,soft,timeo=3D133,retrans=3D2147483647,tcp,acregmax=3D1,acdirmax=3D1,add= r=3D10.1.0.42) # In my case you see final result, which works rather fine for me. But in case you will find noac option inside brackets - yes, it there! Open the /opt/xensource/sm/nfs.py and jump onto the 66 line. You would see near code something like options +=3D ',noac' # CA-27534 You just need to comment out this line of code and reattach you NFS or NFS ISO storage to check performance. In our case the VM protection policy archiving process to NFS storage became 10x faster. You can do even more and google the "noac CA-27534". I sure you will find about year old patch https://github.com/mcclurmc/xcp-storage-managers/pull/1 - options +=3D ',noac' # CA-27534 72** + 73** + # Attribute caching can lead to stale data, so we can try to minimize = these 74** + # problems by reducing the caching time. Going right down to zero does= not 75** + # remove race conditions (rather just makes them more unlikely) while 76** + # introducing some serious performance penalties for the NFS filesyste= m. 77** + # So we get 99% of the way there without the massive performance penal= ties 78** + # by going for 1 second. 79** + # The correct solution to cases where you need up-to-date information = is to 80** + # use file locking primitives, as the lock operation will force the 81** + # getattr() and ensure no concurrent operations. 82** + options +=3D ',acregmax=3D1' 83** + options +=3D ',acdirmax=3D1' noac option suddenly found in XCP 1.6.x as well as in XS 6.x. I thind develepers can describe why mentioned above patch was not pulled to final version. Mentioned above noac option definately didn't present in XS 5.6. I did not check it in XCP 1.4.9. Hope above will help. Finally i want to note that you have to edit manually nfs.py on every member of pool. 2013/1/4 Juan Lorenzana > Okay, so I have two Dell PowerEdge server and we are using with a NAS > solution called TrueNAS by IX Systems. This is basically a ZFS version 2= 8 > implementation for the NAS solution.**** > > ** ** > > Anyway, when we mount our NFS storage repositories over our 10GB > interfaces on the Dell PowerEdge server and the NAS also has 10GB, we get > horrible NFS performance. If I mount a CIFS repository, we get blazing > fast performance.**** > > ** ** > > So my question is how would I go about tuning the different NFS options t= o > do various tests. A quick scan on Google produced nothing on how to do > this. My thoughts are to either pass NFS options in Xen Center under the > Advanced Options input box or edit the nfs.py file. I tried using the > Advanced Options but I do not think that worked.**** > > ** ** > > I am currently running XCP 1.5 but plan on migrating to 1.6 in the next > few months. I would really like to tune the NFS first on 1.5 so that I c= an > compare performance to 1.6. **** > > ** ** > > Any pointers to try to improve NFS performance?**** > > ** ** > > I am getting about a 6MB/s write and 20MB/s read on the NFS storage > repository when doing iozone tests inside a VM. With a 10GB interface I > should be in the 100=E2=80=99s. If I do iozone test on the TrueNAS direc= tly, I get > about 600MB/s on average. When doing iozone testing on VM running Window= s > using CIFS from the same storage solution, we are getting close to 180 MB= /s > so I know the issue is not the storage repository, so I am guessing it ha= s > to do with NFS tuning.**** > > > Any help is appreciated. Thanks.**** > > ** ** > > Juan**** > > ** ** > > ** ** > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --=20 WBR Sergey Kruchatov --e89a8fb203ee4c755704d272588f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi!

Thanks, you give me a chance = to share my expirience in straggle with poor NFS performance in XCP 1.6.x

First of all, you just need to check mo= unting options issued by NFS client in XEN.

You should see something like

#mount
/dev/sda1 on / type ext3 (rw)
<= /div>
none on /proc type proc (rw)
none on /sys type sysfs (r= w)
none on /dev/pts type devpts (rw)
none on /dev/shm type tmpf= s (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
10.1.0.42:/var/storage1/ISO on /var/run/sr-mount/0f61bf48-650b-41e6-183f-62= 31f763468f type nfs (rw,soft,timeo=3D133,retrans=3D2147483647,tcp,acregmax= =3D1,acdirmax=3D1,addr=3D10.1.0.42)
#

In my case you see final result, which works rather fine for me.
But in case you will find noac option inside brackets - yes, it there= !

Open the=C2=A0/opt/xensource/sm/nfs.= py and jump onto the 66 line.
You would see=C2=A0near code something like=C2=A0

options +=3D ',noac' # CA-27534
You just need to comment out this line of code and reatt= ach you NFS or NFS ISO storage to check performance.
In our case the VM protection policy archiving process to NFS st= orage became 10x faster.

You can do ev= en more and google the "noac CA-27534".

I sure you will find about year old patch=C2=A0
= 

-=C2=A0=C2=A0=C2=A0=C2=A0options=C2=A0+=3D=C2=A0&#=
39;,noac'=C2=A0#=C2=A0CA-27534
=C2=A072 
+
=C2=A073 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0Attribute=C2=A0caching=C2=A0can=C2=A0lead=
=C2=A0to=C2=A0stale=C2=A0data,=C2=A0so=C2=A0we=C2=A0can=C2=A0try=C2=A0to=C2=
=A0minimize=C2=A0these
=C2=A074 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0problems=C2=A0by=C2=A0reducing=C2=A0the=C2=
=A0caching=C2=A0time.=C2=A0Going=C2=A0right=C2=A0down=C2=A0to=C2=A0zero=C2=
=A0does=C2=A0not
=C2=A075 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0remove=C2=A0race=C2=A0conditions=C2=A0(rath=
er=C2=A0just=C2=A0makes=C2=A0them=C2=A0more=C2=A0unlikely)=C2=A0while
=
=C2=A076 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0introducing=C2=A0some=C2=A0serious=C2=A0per=
formance=C2=A0penalties=C2=A0for=C2=A0the=C2=A0NFS=C2=A0filesystem.
=C2=A077 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0So=C2=A0we=C2=A0get=C2=A099%=C2=A0of=C2=A0t=
he=C2=A0way=C2=A0there=C2=A0without=C2=A0the=C2=A0massive=C2=A0performance=
=C2=A0penalties
=C2=A078 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0by=C2=A0going=C2=A0for=C2=A01=C2=A0second.<=
/pre>
=C2=A079 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0The=C2=A0correct=C2=A0solution=C2=A0to=C2=
=A0cases=C2=A0where=C2=A0you=C2=A0need=C2=A0up-to-date=C2=A0information=C2=
=A0is=C2=A0to
=C2=A080 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0use=C2=A0file=C2=A0locking=C2=A0primitives,=
=C2=A0as=C2=A0the=C2=A0lock=C2=A0operation=C2=A0will=C2=A0force=C2=A0the
=C2=A081 
+=C2=A0=C2=A0=C2=A0=C2=A0#=C2=A0getattr()=C2=A0and=C2=A0ensure=C2=A0no=C2=
=A0concurrent=C2=A0operations.
=C2=A082 
+=C2=A0=C2=A0=C2=A0=C2=A0options=C2=A0+=3D=C2=A0',acregmax=3D1'
=C2=A083 
+=C2=A0=C2=A0=C2=A0=C2=A0options=C2=A0+=3D=C2=A0',acdirmax=3D1'

noac opti= on suddenly found in XCP 1.6.x as well as in XS 6.x.

I thind develepers can describe why mentioned=C2=A0above=C2= =A0patch was not pulled to final version.

Mentioned above noac option definately didn= 't present in XS 5.6. I did not check it in XCP 1.4.9.
=
Hope above will help.

Finally i want to note that you = have to edit manually nfs.py on every member of pool.

2013/1/4 Juan Lorenzana <juan@= jelsupport.com>
Okay, so I have two Dell PowerEdge server and we are using with a NAS solut= ion called TrueNAS by IX Systems.=C2=A0 This is basically a ZFS version 28 = implementation for the NAS solution.

= =C2=A0

Anyway, when we mount our NFS storage repositories over our 1= 0GB interfaces on the Dell PowerEdge server and the NAS also has 10GB, we g= et horrible NFS performance.=C2=A0 If I mount a CIFS repository, we get bla= zing fast performance.

=C2=A0

So my question is how w= ould I go about tuning the different NFS options to do various tests.=C2=A0= A quick scan on Google produced nothing on how to do this.=C2=A0 My though= ts are to either pass NFS options in Xen Center under the
Advanced Options input box or edit the nfs.py file.=C2=A0 I tried using the= Advanced Options but I do not think that worked.

=C2=A0

I am currently running XCP 1.5 = but plan on migrating to 1.6 in the next few months.=C2=A0 I would really l= ike to tune the NFS first on 1.5 so that I can compare performance to 1.6.= =C2=A0

=C2=A0

Any pointers to try to = improve NFS performance?

=C2=A0

I am getting about a 6MB/s write and 20MB/s read on the = NFS storage repository when doing iozone tests inside a VM.=C2=A0 With a 10= GB interface I should be in the 100=E2=80=99s.=C2=A0 If I do iozone test on= the TrueNAS directly, I get about 600MB/s on average.=C2=A0 When doing ioz= one testing on VM running Windows using CIFS from the same storage solution= , we are getting close to 180 MB/s so I know the issue is not the storage r= epository, so I am guessing it has to do with NFS tuning.


Any help is appreciated.=C2=A0 Thanks.

=C2=A0

Jua= n

=C2=A0

=C2=A0


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




--
WBR
<= br>Sergey Kruchatov
--e89a8fb203ee4c755704d272588f-- --===============4968251816575745902== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4968251816575745902==-- From xen-api-bounces@lists.xen.org Fri Jan 04 10:49:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 10:49:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr4qM-0003g1-Jh; Fri, 04 Jan 2013 10:49:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr4qL-0003fw-B2 for xen-api@lists.xen.org; Fri, 04 Jan 2013 10:49:41 +0000 Received: from [193.109.254.147:35425] by server-11.bemta-14.messagelabs.com id 14/68-02659-4C3B6E05; Fri, 04 Jan 2013 10:49:40 +0000 X-Env-Sender: power.real@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1357296579!10282379!1 X-Originating-IP: [209.85.160.175] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26352 invoked from network); 4 Jan 2013 10:49:40 -0000 Received: from mail-gh0-f175.google.com (HELO mail-gh0-f175.google.com) (209.85.160.175) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 10:49:40 -0000 Received: by mail-gh0-f175.google.com with SMTP id z2so1947874ghb.34 for ; Fri, 04 Jan 2013 02:49:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=0gv8eucvyFQ0dgbsHtPPNPek2mNrnAugK3q0BnyzNfg=; b=XaxsX3mUxobM/X+VtBfC551/e4PHpszlLm6nvI72H4bM9WAKcaysU1UMFF+tppDhx8 RJcOhLssg5T65wT/3fACvbxoj1HBiU16GDUlgM96tiYpgvgzyl4KJdpRGxi8X9tBFjfI aceAYLVobU+ad+TYLSw+Vyuqb4LxNiSOeTIOyxm18S4KVGj5trZiEOBKi4XMu0aQb4us Tq1l5KA9XKhjloUbo21hzwK8sXxnBztYL1OXn94fLNeQY9FRF5unTIYv4DLCRU4oDq+Y NzEnm5/N9CWU9Z07xbm0jg3vd6CyEIaby02PDvjFjWnilAC38n0AttbvvafnvVCJWSa/ NMrA== MIME-Version: 1.0 Received: by 10.236.117.206 with SMTP id j54mr2679375yhh.68.1357296578809; Fri, 04 Jan 2013 02:49:38 -0800 (PST) Received: by 10.147.42.40 with HTTP; Fri, 4 Jan 2013 02:49:38 -0800 (PST) Date: Fri, 4 Jan 2013 14:49:38 +0400 Message-ID: From: Sergey To: xen-api@lists.xen.org Subject: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all. Where I can find instruction how to migrate vdi to another sr (from local to lvmoiscsi) Thanks. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 10:49:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 10:49:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr4qM-0003g1-Jh; Fri, 04 Jan 2013 10:49:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr4qL-0003fw-B2 for xen-api@lists.xen.org; Fri, 04 Jan 2013 10:49:41 +0000 Received: from [193.109.254.147:35425] by server-11.bemta-14.messagelabs.com id 14/68-02659-4C3B6E05; Fri, 04 Jan 2013 10:49:40 +0000 X-Env-Sender: power.real@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1357296579!10282379!1 X-Originating-IP: [209.85.160.175] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26352 invoked from network); 4 Jan 2013 10:49:40 -0000 Received: from mail-gh0-f175.google.com (HELO mail-gh0-f175.google.com) (209.85.160.175) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 10:49:40 -0000 Received: by mail-gh0-f175.google.com with SMTP id z2so1947874ghb.34 for ; Fri, 04 Jan 2013 02:49:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=0gv8eucvyFQ0dgbsHtPPNPek2mNrnAugK3q0BnyzNfg=; b=XaxsX3mUxobM/X+VtBfC551/e4PHpszlLm6nvI72H4bM9WAKcaysU1UMFF+tppDhx8 RJcOhLssg5T65wT/3fACvbxoj1HBiU16GDUlgM96tiYpgvgzyl4KJdpRGxi8X9tBFjfI aceAYLVobU+ad+TYLSw+Vyuqb4LxNiSOeTIOyxm18S4KVGj5trZiEOBKi4XMu0aQb4us Tq1l5KA9XKhjloUbo21hzwK8sXxnBztYL1OXn94fLNeQY9FRF5unTIYv4DLCRU4oDq+Y NzEnm5/N9CWU9Z07xbm0jg3vd6CyEIaby02PDvjFjWnilAC38n0AttbvvafnvVCJWSa/ NMrA== MIME-Version: 1.0 Received: by 10.236.117.206 with SMTP id j54mr2679375yhh.68.1357296578809; Fri, 04 Jan 2013 02:49:38 -0800 (PST) Received: by 10.147.42.40 with HTTP; Fri, 4 Jan 2013 02:49:38 -0800 (PST) Date: Fri, 4 Jan 2013 14:49:38 +0400 Message-ID: From: Sergey To: xen-api@lists.xen.org Subject: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all. Where I can find instruction how to migrate vdi to another sr (from local to lvmoiscsi) Thanks. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 11:32:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 11:32:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr5VI-00042m-U4; Fri, 04 Jan 2013 11:32:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr5VH-00042h-OL for xen-api@lists.xen.org; Fri, 04 Jan 2013 11:31:59 +0000 Received: from [85.158.143.99:49899] by server-1.bemta-4.messagelabs.com id 04/B2-28401-FADB6E05; Fri, 04 Jan 2013 11:31:59 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1357299101!26652348!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6177 invoked from network); 4 Jan 2013 11:31:41 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 11:31:41 -0000 X-IronPort-AV: E=Sophos;i="4.84,409,1355097600"; d="scan'208";a="453281" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 11:31:41 +0000 Received: from [128.232.140.48] (10.80.16.67) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Fri, 4 Jan 2013 11:31:41 +0000 Message-ID: <50E6BD97.9040504@citrix.com> Date: Fri, 4 Jan 2013 11:31:35 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Sergey References: In-Reply-To: X-Enigmail-Version: 1.4.6 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 04/01/13 10:49, Sergey wrote: > Hi all. > Where I can find instruction how to migrate vdi to another sr (from > local to lvmoiscsi) > Thanks. Do 'xe help vdi-pool-migrate' in dom0. That should get you started. Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 11:32:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 11:32:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr5VI-00042m-U4; Fri, 04 Jan 2013 11:32:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr5VH-00042h-OL for xen-api@lists.xen.org; Fri, 04 Jan 2013 11:31:59 +0000 Received: from [85.158.143.99:49899] by server-1.bemta-4.messagelabs.com id 04/B2-28401-FADB6E05; Fri, 04 Jan 2013 11:31:59 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1357299101!26652348!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6177 invoked from network); 4 Jan 2013 11:31:41 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 11:31:41 -0000 X-IronPort-AV: E=Sophos;i="4.84,409,1355097600"; d="scan'208";a="453281" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 11:31:41 +0000 Received: from [128.232.140.48] (10.80.16.67) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Fri, 4 Jan 2013 11:31:41 +0000 Message-ID: <50E6BD97.9040504@citrix.com> Date: Fri, 4 Jan 2013 11:31:35 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Sergey References: In-Reply-To: X-Enigmail-Version: 1.4.6 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 04/01/13 10:49, Sergey wrote: > Hi all. > Where I can find instruction how to migrate vdi to another sr (from > local to lvmoiscsi) > Thanks. Do 'xe help vdi-pool-migrate' in dom0. That should get you started. Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 11:59:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 11:59:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr5vf-0005Rj-3z; Fri, 04 Jan 2013 11:59:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr5vd-0005RT-Fp for xen-api@lists.xen.org; Fri, 04 Jan 2013 11:59:13 +0000 Received: from [193.109.254.147:50137] by server-11.bemta-14.messagelabs.com id 75/5A-02659-014C6E05; Fri, 04 Jan 2013 11:59:12 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1357300733!8543414!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12811 invoked from network); 4 Jan 2013 11:58:53 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 11:58:53 -0000 X-IronPort-AV: E=Sophos;i="4.84,409,1355097600"; d="scan'208,217";a="453953" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 11:58:53 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Fri, 4 Jan 2013 11:58:53 +0000 From: John Else To: "xen-api@lists.xen.org" Date: Fri, 4 Jan 2013 11:59:36 +0000 Thread-Topic: [Xen-API] XCP1.6 storage xenmotion issue Thread-Index: Ac3n4a2TDgr74ENJQv2s3S+cNNnXGwCkBibg Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7@LONPMAILBOX01.citrite.net> References: <201212311004494374333@gmail.com> <50E274DA.5010000@gmail.com> In-Reply-To: <50E274DA.5010000@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4361008682418433568==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4361008682418433568== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7LONPMAILBOX01_" --_000_7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7LONPMAILBOX01_ Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable I've noticed this error when the guest has a CD mounted that is not availab= le to the destination host. Try ejecting all CDs from the guest before migr= ating it. John From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of George Shuklin Sent: 01 January 2013 05:32 To: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue Not yet. My test machines fly between pools like a magic. Please provides xensource.log pieces from both sides: sender and receiver. = I think, they should be pool's masters logs. PS Do not forget to set up default-sr pool property on receiver. 31.12.2012 06:04, Tianpeng Zhang =D0=C9=DB=C5=D4: Hi All, I got one issue with xcp1.6 when testing VM storage xenMotion to another ho= st. It reported error as an "internal error". Have anyone met this issue be= fore? Or give some tips for this issue? Thanks. [root@xcp102 ~]# xe vm-migrate destination-sr-uuid=3D2a9e0cd0-0ddf-b9ef-5e3= 8-2f57e4ac361e vm=3DCentOS6-PV remote-master=3D10.33.2.103 remote-password= =3Dpasswd remote-username=3Droot Performing a Storage XenMotion migration. Your VM's VDIs will be migrated w= ith the VM. Will migrate to remote host: xcp103, using remote network: Pool-wide networ= k associated with eth0. Here is the VDI mapping: VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57= e4ac361e VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57= e4ac361e The server failed to handle your request, due to an internal error. The gi= ven message may give details useful for debugging the problem. message: Import.IFailure(2) [root@xcp102 ~]# _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_000_7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7LONPMAILBOX01_ Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable

= I’ve noticed this error when the guest has a CD mounted that i= s not available to the destination host. Try ejecting all CDs from the gues= t before migrating it.

 

John=

 

<= p class=3DMsoNormal>From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.or= g] On Behalf Of George Shuklin
Sent: 01 January 2013 05:32=
To: xen-api@lists.xen.org
Subject: Re: [Xen-API] XCP1.= 6 storage xenmotion issue

 

Not yet. My test machin= es fly between pools like a magic.

Please provides xensource.log pie= ces from both sides: sender and receiver. I think, they should be pool's ma= sters logs.

PS Do not forget to set up default-sr pool property on r= eceiver.

31.12.2012 06:04, Tianpeng Zhang =D0=C9=DB=C5=D4:

Hi All,

 

I got one issue = with xcp1.6 when testing VM storage xenMotion to another host. It repo= rted error as an "internal error". Have anyone met this=  issue before? Or give some tips for this issue?

 

Thanks. 

 <= o:p>

[root@xcp102 ~]# xe=  vm-migrate destination-sr-uuid=3D2a9e0cd0-0ddf-b9ef-5e38-2f57e4a= c361e vm=3DCentOS6-PV remote-master=3D10.33.2.103 remote-pas= sword=3Dpasswd remote-username=3Droot

Performing a Storage XenMotion migration.=  Your VM's VDIs will be migrated with&nb= sp;the VM.

Will mig= rate to remote host: xcp103, using remote&nbs= p;network: Pool-wide network associated with eth0.=  Here is the VDI mapping:

VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -&= gt; SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e

<= div>

VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 = ;-> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e

The server failed to handle=  your request, due to an internal error.=   The given message may give details&nbs= p;useful for debugging the problem.

message: Import.IFailure(2)

<= /div>

[root@xcp102 ~]#




__________________=
_____________________________
Xen-api mailing list
Xen-api@lists.xe=
n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api=

 

= --_000_7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7LONPMAILBOX01_-- --===============4361008682418433568== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4361008682418433568==-- From xen-api-bounces@lists.xen.org Fri Jan 04 11:59:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 11:59:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr5vf-0005Rj-3z; Fri, 04 Jan 2013 11:59:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr5vd-0005RT-Fp for xen-api@lists.xen.org; Fri, 04 Jan 2013 11:59:13 +0000 Received: from [193.109.254.147:50137] by server-11.bemta-14.messagelabs.com id 75/5A-02659-014C6E05; Fri, 04 Jan 2013 11:59:12 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1357300733!8543414!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12811 invoked from network); 4 Jan 2013 11:58:53 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 11:58:53 -0000 X-IronPort-AV: E=Sophos;i="4.84,409,1355097600"; d="scan'208,217";a="453953" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 11:58:53 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Fri, 4 Jan 2013 11:58:53 +0000 From: John Else To: "xen-api@lists.xen.org" Date: Fri, 4 Jan 2013 11:59:36 +0000 Thread-Topic: [Xen-API] XCP1.6 storage xenmotion issue Thread-Index: Ac3n4a2TDgr74ENJQv2s3S+cNNnXGwCkBibg Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7@LONPMAILBOX01.citrite.net> References: <201212311004494374333@gmail.com> <50E274DA.5010000@gmail.com> In-Reply-To: <50E274DA.5010000@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4361008682418433568==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4361008682418433568== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7LONPMAILBOX01_" --_000_7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7LONPMAILBOX01_ Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable I've noticed this error when the guest has a CD mounted that is not availab= le to the destination host. Try ejecting all CDs from the guest before migr= ating it. John From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of George Shuklin Sent: 01 January 2013 05:32 To: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue Not yet. My test machines fly between pools like a magic. Please provides xensource.log pieces from both sides: sender and receiver. = I think, they should be pool's masters logs. PS Do not forget to set up default-sr pool property on receiver. 31.12.2012 06:04, Tianpeng Zhang =D0=C9=DB=C5=D4: Hi All, I got one issue with xcp1.6 when testing VM storage xenMotion to another ho= st. It reported error as an "internal error". Have anyone met this issue be= fore? Or give some tips for this issue? Thanks. [root@xcp102 ~]# xe vm-migrate destination-sr-uuid=3D2a9e0cd0-0ddf-b9ef-5e3= 8-2f57e4ac361e vm=3DCentOS6-PV remote-master=3D10.33.2.103 remote-password= =3Dpasswd remote-username=3Droot Performing a Storage XenMotion migration. Your VM's VDIs will be migrated w= ith the VM. Will migrate to remote host: xcp103, using remote network: Pool-wide networ= k associated with eth0. Here is the VDI mapping: VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57= e4ac361e VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57= e4ac361e The server failed to handle your request, due to an internal error. The gi= ven message may give details useful for debugging the problem. message: Import.IFailure(2) [root@xcp102 ~]# _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_000_7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7LONPMAILBOX01_ Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable

= I’ve noticed this error when the guest has a CD mounted that i= s not available to the destination host. Try ejecting all CDs from the gues= t before migrating it.

 

John=

 

<= p class=3DMsoNormal>From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.or= g] On Behalf Of George Shuklin
Sent: 01 January 2013 05:32=
To: xen-api@lists.xen.org
Subject: Re: [Xen-API] XCP1.= 6 storage xenmotion issue

 

Not yet. My test machin= es fly between pools like a magic.

Please provides xensource.log pie= ces from both sides: sender and receiver. I think, they should be pool's ma= sters logs.

PS Do not forget to set up default-sr pool property on r= eceiver.

31.12.2012 06:04, Tianpeng Zhang =D0=C9=DB=C5=D4:

Hi All,

 

I got one issue = with xcp1.6 when testing VM storage xenMotion to another host. It repo= rted error as an "internal error". Have anyone met this=  issue before? Or give some tips for this issue?

 

Thanks. 

 <= o:p>

[root@xcp102 ~]# xe=  vm-migrate destination-sr-uuid=3D2a9e0cd0-0ddf-b9ef-5e38-2f57e4a= c361e vm=3DCentOS6-PV remote-master=3D10.33.2.103 remote-pas= sword=3Dpasswd remote-username=3Droot

Performing a Storage XenMotion migration.=  Your VM's VDIs will be migrated with&nb= sp;the VM.

Will mig= rate to remote host: xcp103, using remote&nbs= p;network: Pool-wide network associated with eth0.=  Here is the VDI mapping:

VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -&= gt; SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e

<= div>

VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 = ;-> SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e

The server failed to handle=  your request, due to an internal error.=   The given message may give details&nbs= p;useful for debugging the problem.

message: Import.IFailure(2)

<= /div>

[root@xcp102 ~]#




__________________=
_____________________________
Xen-api mailing list
Xen-api@lists.xe=
n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api=

 

= --_000_7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7LONPMAILBOX01_-- --===============4361008682418433568== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4361008682418433568==-- From xen-api-bounces@lists.xen.org Fri Jan 04 12:10:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 12:10:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr66k-000664-5u; Fri, 04 Jan 2013 12:10:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr66j-00065w-Ev for xen-api@lists.xen.org; Fri, 04 Jan 2013 12:10:41 +0000 Received: from [85.158.143.35:29404] by server-3.bemta-4.messagelabs.com id 54/B6-18211-0C6C6E05; Fri, 04 Jan 2013 12:10:40 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1357301388!13662205!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29150 invoked from network); 4 Jan 2013 12:09:49 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 12:09:49 -0000 X-IronPort-AV: E=Sophos;i="4.84,409,1355097600"; d="scan'208";a="454260" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 12:09:33 +0000 Received: from [128.232.140.48] (10.80.16.67) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Fri, 4 Jan 2013 12:09:33 +0000 Message-ID: <50E6C676.9000302@citrix.com> Date: Fri, 4 Jan 2013 12:09:26 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Sergey , "xen-api@lists.xen.org" References: <50E6BD97.9040504@citrix.com> In-Reply-To: X-Enigmail-Version: 1.4.6 Subject: Re: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org (adding xen-api list back in -- please don't drop the list) On 04/01/13 11:49, Sergey wrote: > Thank you Mike! > Can you also point me where I can change default SR for newly created VMs? Try 'xe help vm-install'. The sr-uuid/sr-name-label params are what you want. Mike > > On Fri, Jan 4, 2013 at 3:31 PM, Mike McClurg wrote: >> On 04/01/13 10:49, Sergey wrote: >>> Hi all. >>> Where I can find instruction how to migrate vdi to another sr (from >>> local to lvmoiscsi) >>> Thanks. >> >> Do 'xe help vdi-pool-migrate' in dom0. That should get you started. >> >> Mike >> _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 12:10:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 12:10:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr66k-000664-5u; Fri, 04 Jan 2013 12:10:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr66j-00065w-Ev for xen-api@lists.xen.org; Fri, 04 Jan 2013 12:10:41 +0000 Received: from [85.158.143.35:29404] by server-3.bemta-4.messagelabs.com id 54/B6-18211-0C6C6E05; Fri, 04 Jan 2013 12:10:40 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1357301388!13662205!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29150 invoked from network); 4 Jan 2013 12:09:49 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 12:09:49 -0000 X-IronPort-AV: E=Sophos;i="4.84,409,1355097600"; d="scan'208";a="454260" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 12:09:33 +0000 Received: from [128.232.140.48] (10.80.16.67) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Fri, 4 Jan 2013 12:09:33 +0000 Message-ID: <50E6C676.9000302@citrix.com> Date: Fri, 4 Jan 2013 12:09:26 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Sergey , "xen-api@lists.xen.org" References: <50E6BD97.9040504@citrix.com> In-Reply-To: X-Enigmail-Version: 1.4.6 Subject: Re: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org (adding xen-api list back in -- please don't drop the list) On 04/01/13 11:49, Sergey wrote: > Thank you Mike! > Can you also point me where I can change default SR for newly created VMs? Try 'xe help vm-install'. The sr-uuid/sr-name-label params are what you want. Mike > > On Fri, Jan 4, 2013 at 3:31 PM, Mike McClurg wrote: >> On 04/01/13 10:49, Sergey wrote: >>> Hi all. >>> Where I can find instruction how to migrate vdi to another sr (from >>> local to lvmoiscsi) >>> Thanks. >> >> Do 'xe help vdi-pool-migrate' in dom0. That should get you started. >> >> Mike >> _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 12:44:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 12:44:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr6dS-0000Ua-VI; Fri, 04 Jan 2013 12:44:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr6dR-0000UM-6D for xen-api@lists.xen.org; Fri, 04 Jan 2013 12:44:29 +0000 Received: from [85.158.139.211:49006] by server-14.bemta-5.messagelabs.com id B2/4A-09538-CAEC6E05; Fri, 04 Jan 2013 12:44:28 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1357303467!21008120!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11299 invoked from network); 4 Jan 2013 12:44:27 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 12:44:27 -0000 X-IronPort-AV: E=Sophos;i="4.84,409,1355097600"; d="scan'208";a="455077" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 12:44:27 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Fri, 4 Jan 2013 12:44:27 +0000 From: Rob Hoes To: Mike McClurg , Sergey , "xen-api@lists.xen.org" Date: Fri, 4 Jan 2013 12:44:26 +0000 Thread-Topic: [Xen-API] migrate vdi to another sr Thread-Index: Ac3qdOPMEjG+JeSOR8WRQfabuPUCUwABCNGA Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF7287A76@LONPMAILBOX01.citrite.net> References: <50E6BD97.9040504@citrix.com> <50E6C676.9000302@citrix.com> In-Reply-To: <50E6C676.9000302@citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > On 04/01/13 11:49, Sergey wrote: > > Thank you Mike! > > Can you also point me where I can change default SR for newly created > VMs? > > Try 'xe help vm-install'. The sr-uuid/sr-name-label params are what you > want. The default SR, used for all new VMs by default, is defined on the pool. Try 'xe pool-param-set' to set 'default-SR'. Cheers, Rob _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 12:44:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 12:44:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr6dS-0000Ua-VI; Fri, 04 Jan 2013 12:44:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr6dR-0000UM-6D for xen-api@lists.xen.org; Fri, 04 Jan 2013 12:44:29 +0000 Received: from [85.158.139.211:49006] by server-14.bemta-5.messagelabs.com id B2/4A-09538-CAEC6E05; Fri, 04 Jan 2013 12:44:28 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1357303467!21008120!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11299 invoked from network); 4 Jan 2013 12:44:27 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 12:44:27 -0000 X-IronPort-AV: E=Sophos;i="4.84,409,1355097600"; d="scan'208";a="455077" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 12:44:27 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Fri, 4 Jan 2013 12:44:27 +0000 From: Rob Hoes To: Mike McClurg , Sergey , "xen-api@lists.xen.org" Date: Fri, 4 Jan 2013 12:44:26 +0000 Thread-Topic: [Xen-API] migrate vdi to another sr Thread-Index: Ac3qdOPMEjG+JeSOR8WRQfabuPUCUwABCNGA Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF7287A76@LONPMAILBOX01.citrite.net> References: <50E6BD97.9040504@citrix.com> <50E6C676.9000302@citrix.com> In-Reply-To: <50E6C676.9000302@citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > On 04/01/13 11:49, Sergey wrote: > > Thank you Mike! > > Can you also point me where I can change default SR for newly created > VMs? > > Try 'xe help vm-install'. The sr-uuid/sr-name-label params are what you > want. The default SR, used for all new VMs by default, is defined on the pool. Try 'xe pool-param-set' to set 'default-SR'. Cheers, Rob _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 15:44:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 15:44:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr9RY-00063o-FY; Fri, 04 Jan 2013 15:44:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr9RX-00063h-Q8 for xen-api@lists.xen.org; Fri, 04 Jan 2013 15:44:23 +0000 Received: from [85.158.143.99:13285] by server-3.bemta-4.messagelabs.com id 02/70-18211-7D8F6E05; Fri, 04 Jan 2013 15:44:23 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1357314262!25434737!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17680 invoked from network); 4 Jan 2013 15:44:22 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 15:44:22 -0000 X-IronPort-AV: E=Sophos;i="4.84,411,1355097600"; d="scan'208";a="459153" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 15:44:22 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Fri, 4 Jan 2013 15:44:22 +0000 From: Dave Scott To: "xen-api@lists.xen.org" Date: Fri, 4 Jan 2013 15:44:20 +0000 Thread-Topic: running latest dev versions of xenopsd on Debian/Ubuntu Thread-Index: Ac3qkUg0wxSPpNjMT6W0axZdOHbZBA== Message-ID: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, I've written a wiki page describing how to build the latest development version of "xenopsd" (and its dependencies) from source: http://wiki.xen.org/wiki/Building_Xenopsd "xenopsd" is the name of the domain manager of the XCP toolstack -- it is responsible for starting, stopping, migrating VMs. Being able to build the development version is really useful if you want to: * check out a new feature * reproduce a bug * test a fix Let me know if you try this and have any problems or suggestions! There are a couple more components of the XCP toolstack that need some fixups so they can build easily, in particular: * squeezed: manages memory ballooning * networkd: configures VM networking * rrdd: collects and archives performance statistics * xapi: manages the overall resource pool Hopefully we can work on these one-by-one until they are all as easy to build as xenopsd. Cheers, Dave _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 15:44:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 15:44:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr9RY-00063o-FY; Fri, 04 Jan 2013 15:44:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr9RX-00063h-Q8 for xen-api@lists.xen.org; Fri, 04 Jan 2013 15:44:23 +0000 Received: from [85.158.143.99:13285] by server-3.bemta-4.messagelabs.com id 02/70-18211-7D8F6E05; Fri, 04 Jan 2013 15:44:23 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1357314262!25434737!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE0NDE1\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17680 invoked from network); 4 Jan 2013 15:44:22 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2013 15:44:22 -0000 X-IronPort-AV: E=Sophos;i="4.84,411,1355097600"; d="scan'208";a="459153" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 15:44:22 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Fri, 4 Jan 2013 15:44:22 +0000 From: Dave Scott To: "xen-api@lists.xen.org" Date: Fri, 4 Jan 2013 15:44:20 +0000 Thread-Topic: running latest dev versions of xenopsd on Debian/Ubuntu Thread-Index: Ac3qkUg0wxSPpNjMT6W0axZdOHbZBA== Message-ID: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, I've written a wiki page describing how to build the latest development version of "xenopsd" (and its dependencies) from source: http://wiki.xen.org/wiki/Building_Xenopsd "xenopsd" is the name of the domain manager of the XCP toolstack -- it is responsible for starting, stopping, migrating VMs. Being able to build the development version is really useful if you want to: * check out a new feature * reproduce a bug * test a fix Let me know if you try this and have any problems or suggestions! There are a couple more components of the XCP toolstack that need some fixups so they can build easily, in particular: * squeezed: manages memory ballooning * networkd: configures VM networking * rrdd: collects and archives performance statistics * xapi: manages the overall resource pool Hopefully we can work on these one-by-one until they are all as easy to build as xenopsd. Cheers, Dave _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 15:54:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 15:54:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr9at-0006LY-NC; Fri, 04 Jan 2013 15:54:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr9as-0006LP-ML for xen-api@lists.xen.org; Fri, 04 Jan 2013 15:54:02 +0000 Received: from [193.109.254.147:63170] by server-12.bemta-14.messagelabs.com id D5/B3-06523-91BF6E05; Fri, 04 Jan 2013 15:54:01 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1357314840!3618741!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18494 invoked from network); 4 Jan 2013 15:54:01 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-10.tower-27.messagelabs.com with SMTP; 4 Jan 2013 15:54:01 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Fri, 4 Jan 2013 09:54:00 -0600 Message-ID: <50E6FB68.1010009@xenhive.com> Date: Fri, 04 Jan 2013 09:55:20 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-Auth: admin@xenhive.com Subject: Re: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 1/4/2013 4:49 AM, Sergey wrote: > Hi all. > Where I can find instruction how to migrate vdi to another sr (from > local to lvmoiscsi) > Thanks. > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api If you are using XenCenter and XCP 1.6 (or XenServer 6.1), it is really easy to do. In XenCenter, select the current SR. Then click the Storage tab. Then right click on the Virtual Disk that you want to move and select Move Virtual Disk. Then let it know which SR you wish to move the Virtual Disk to, and then click the Move button. It works slick. The virtual disk will move to the new SR as a background task without interrupting the VM. Just make sure there is enough RAM available on the host node. You will need at least as much RAM available as the VM is using. If RAM is not available, the transfer will fail and a cryptic error message will get logged. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 15:54:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 15:54:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr9at-0006LY-NC; Fri, 04 Jan 2013 15:54:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tr9as-0006LP-ML for xen-api@lists.xen.org; Fri, 04 Jan 2013 15:54:02 +0000 Received: from [193.109.254.147:63170] by server-12.bemta-14.messagelabs.com id D5/B3-06523-91BF6E05; Fri, 04 Jan 2013 15:54:01 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1357314840!3618741!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18494 invoked from network); 4 Jan 2013 15:54:01 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-10.tower-27.messagelabs.com with SMTP; 4 Jan 2013 15:54:01 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Fri, 4 Jan 2013 09:54:00 -0600 Message-ID: <50E6FB68.1010009@xenhive.com> Date: Fri, 04 Jan 2013 09:55:20 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-Auth: admin@xenhive.com Subject: Re: [Xen-API] migrate vdi to another sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 1/4/2013 4:49 AM, Sergey wrote: > Hi all. > Where I can find instruction how to migrate vdi to another sr (from > local to lvmoiscsi) > Thanks. > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api If you are using XenCenter and XCP 1.6 (or XenServer 6.1), it is really easy to do. In XenCenter, select the current SR. Then click the Storage tab. Then right click on the Virtual Disk that you want to move and select Move Virtual Disk. Then let it know which SR you wish to move the Virtual Disk to, and then click the Move button. It works slick. The virtual disk will move to the new SR as a background task without interrupting the VM. Just make sure there is enough RAM available on the host node. You will need at least as much RAM available as the VM is using. If RAM is not available, the transfer will fail and a cryptic error message will get logged. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 18:29:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 18:29:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrC1Q-0005JB-75; Fri, 04 Jan 2013 18:29:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrC1O-0005J6-QA for xen-api@lists.xen.org; Fri, 04 Jan 2013 18:29:35 +0000 Received: from [85.158.137.99:13427] by server-6.bemta-3.messagelabs.com id 07/11-12154-98F17E05; Fri, 04 Jan 2013 18:29:29 +0000 X-Env-Sender: philipp@phflesch.de X-Msg-Ref: server-5.tower-217.messagelabs.com!1357324168!12736990!1 X-Originating-IP: [176.9.200.162] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17018 invoked from network); 4 Jan 2013 18:29:28 -0000 Received: from s4.twanas.de (HELO s4.twanas.de) (176.9.200.162) by server-5.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 18:29:28 -0000 Received: from localhost (localhost [127.0.0.1]) by s4.twanas.de (Postfix) with ESMTP id 17E85E06E5 for ; Fri, 4 Jan 2013 19:29:28 +0100 (CET) Received: from s4.twanas.de ([127.0.0.1]) by localhost (s4.twanas.de [127.0.0.1]) (maiad, port 10024) with ESMTP id 01653-01 for ; Fri, 4 Jan 2013 19:29:27 +0100 (CET) Received: from [192.168.178.24] (tmo-096-147.customers.d1-online.com [80.187.96.147]) by s4.twanas.de (Postfix) with ESMTPSA id 1B137E06E4 for ; Fri, 4 Jan 2013 19:29:27 +0100 (CET) Message-ID: <50E71F8D.5040502@phflesch.de> Date: Fri, 04 Jan 2013 19:29:33 +0100 From: Philipp Flesch User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E32CBA.3020909@phflesch.de> In-Reply-To: <50E32CBA.3020909@phflesch.de> X-Virus-Scanned: Maia Mailguard 1.0.3 Subject: Re: [Xen-API] XCP 1.6 - Error Importing OVF X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, some more information: I used a third server to install citrix xenserver 6.1 and the import of the ovf-files (skipped by xcp) worked fine. But I haven't got the time to do multi-import-export like the tested VMWARE -> OVF -> xenserver 6.1 xenserver 6.1 -> XVA -> XCP Greetings Philipp Am 01.01.2013 19:36, schrieb Philipp Flesch: > Hi! > I already imported some .xva-files without any problems. > > I now wanted to start migrating our ESXi-farm ... > > First of all, I installed the XENSERVER Transfer VMs on both servers > (following > http://blogs.citrix.com/2010/12/09/diagnosing-xenserver-appliance-wizard-failures/) > and I also imported the Citrix XCM Virtual Appliance. > > Both from XenServer 6.1 > > > I followed http://support.citrix.com/article/CTX133505 and exported an > ovf to the local harddrive. > > Starting the import via XenCenter 6.1 the required vm-drive is > created, but than the import fails ... > > Having a closer look to the vmdk: > > root@linux-workstation:/mnt/ad02-temp/unterricht# qemu-img info > Unterricht_neu-disk1.vmdk > image: Unterricht_neu-disk1.vmdk > file format: vmdk > virtual size: 16G (17179869184 bytes) > disk size: 1.0G > > So the vmdk seems to be okay ... > > I copied the log to http://wvbg.bndlg.de/~max/xen/xencenter.log > > Any hints? > > Thank you very much. > > Philipp > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 18:29:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 18:29:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrC1Q-0005JB-75; Fri, 04 Jan 2013 18:29:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrC1O-0005J6-QA for xen-api@lists.xen.org; Fri, 04 Jan 2013 18:29:35 +0000 Received: from [85.158.137.99:13427] by server-6.bemta-3.messagelabs.com id 07/11-12154-98F17E05; Fri, 04 Jan 2013 18:29:29 +0000 X-Env-Sender: philipp@phflesch.de X-Msg-Ref: server-5.tower-217.messagelabs.com!1357324168!12736990!1 X-Originating-IP: [176.9.200.162] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17018 invoked from network); 4 Jan 2013 18:29:28 -0000 Received: from s4.twanas.de (HELO s4.twanas.de) (176.9.200.162) by server-5.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 18:29:28 -0000 Received: from localhost (localhost [127.0.0.1]) by s4.twanas.de (Postfix) with ESMTP id 17E85E06E5 for ; Fri, 4 Jan 2013 19:29:28 +0100 (CET) Received: from s4.twanas.de ([127.0.0.1]) by localhost (s4.twanas.de [127.0.0.1]) (maiad, port 10024) with ESMTP id 01653-01 for ; Fri, 4 Jan 2013 19:29:27 +0100 (CET) Received: from [192.168.178.24] (tmo-096-147.customers.d1-online.com [80.187.96.147]) by s4.twanas.de (Postfix) with ESMTPSA id 1B137E06E4 for ; Fri, 4 Jan 2013 19:29:27 +0100 (CET) Message-ID: <50E71F8D.5040502@phflesch.de> Date: Fri, 04 Jan 2013 19:29:33 +0100 From: Philipp Flesch User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E32CBA.3020909@phflesch.de> In-Reply-To: <50E32CBA.3020909@phflesch.de> X-Virus-Scanned: Maia Mailguard 1.0.3 Subject: Re: [Xen-API] XCP 1.6 - Error Importing OVF X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, some more information: I used a third server to install citrix xenserver 6.1 and the import of the ovf-files (skipped by xcp) worked fine. But I haven't got the time to do multi-import-export like the tested VMWARE -> OVF -> xenserver 6.1 xenserver 6.1 -> XVA -> XCP Greetings Philipp Am 01.01.2013 19:36, schrieb Philipp Flesch: > Hi! > I already imported some .xva-files without any problems. > > I now wanted to start migrating our ESXi-farm ... > > First of all, I installed the XENSERVER Transfer VMs on both servers > (following > http://blogs.citrix.com/2010/12/09/diagnosing-xenserver-appliance-wizard-failures/) > and I also imported the Citrix XCM Virtual Appliance. > > Both from XenServer 6.1 > > > I followed http://support.citrix.com/article/CTX133505 and exported an > ovf to the local harddrive. > > Starting the import via XenCenter 6.1 the required vm-drive is > created, but than the import fails ... > > Having a closer look to the vmdk: > > root@linux-workstation:/mnt/ad02-temp/unterricht# qemu-img info > Unterricht_neu-disk1.vmdk > image: Unterricht_neu-disk1.vmdk > file format: vmdk > virtual size: 16G (17179869184 bytes) > disk size: 1.0G > > So the vmdk seems to be okay ... > > I copied the log to http://wvbg.bndlg.de/~max/xen/xencenter.log > > Any hints? > > Thank you very much. > > Philipp > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 19:30:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 19:30:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrCy2-0006UM-RV; Fri, 04 Jan 2013 19:30:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrCy0-0006UH-Vi for xen-api@lists.xen.org; Fri, 04 Jan 2013 19:30:09 +0000 Received: from [85.158.139.211:39714] by server-5.bemta-5.messagelabs.com id C4/1D-22648-FBD27E05; Fri, 04 Jan 2013 19:30:07 +0000 X-Env-Sender: mephisto@mephis.to X-Msg-Ref: server-9.tower-206.messagelabs.com!1357327801!20311569!1 X-Originating-IP: [212.77.170.22] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3743 invoked from network); 4 Jan 2013 19:30:06 -0000 Received: from mx2.netzblick.de (HELO mx2.netzblick.de) (212.77.170.22) by server-9.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 19:30:06 -0000 Received: from [192.168.7.3] (core.niedermayr.de [213.166.224.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.netzblick.de (Postfix) with ESMTP id 1FB73280B2; Fri, 4 Jan 2013 20:30:01 +0100 (CET) Message-ID: <50E72DB3.5050401@mephis.to> Date: Fri, 04 Jan 2013 20:29:55 +0100 From: =?ISO-8859-1?Q?Bastian_M=E4user?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: xen-api@lists.xen.org, mike.mcclurg@citrix.com, 2rushikeshj@gmail.com References: <50D08835.30708@mephis.to> In-Reply-To: <50D08835.30708@mephis.to> X-Enigmail-Version: 1.4.4 Subject: Re: [Xen-API] Poor xapi Performance Exporting/Importing VM's on XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Ok, here goes an update on the Problem, which I evaluated in a nightly session with kind help of Trixboxer from the #xen-api irc-channel on freenode. I think it's a duplicate of the Problem of another User posted here: http://www.gossamer-threads.com/lists/xen/api/258377 There are 2 factors causing the bad performance while importing and even more exporting VM's via CLI on a shares NFS SR. Here goes our Test Setting: 2 Pools one XCP1.1, one XCP1.6 - both using the vanilly XCP iso.. both sharing the same iSCSI and Management Network (1GBe) SAN's used: 1.1. Pool SAN: HP Lefthand P4000 VSA 1.6. Pool SAN: Easyraid Q16+ NAS used: Same NFS NAS for 1.1 and 1.6 (Dual CPU Xeon E5310 @ 1.60GHz w/ EasyRaid U320 SCSI Raid) GBe connected The Nodes used for xe vm-export/import had no domU's running, and the Monitoring was showing a very low Network Utilization in both the SAN as well as the Management Network. >>>>>>>> 1. From XCP1.1 to XCP1.6 the Operating System Default values regarding NFS Mounts moght have changed. We found out that In 1.1 the default NFS mount option is "async" in 1.6 the default is "sync". That causes a very bad performance when writing to NFS NAS's with a moderate IOPS Performance. The difference is ~10MB/s on 1.1 compared to 1.5MB/s on 1.6. To test it I dismounted the xapi mounted NFS SR on a node of the 1.6 Pool and remounted it with "async". Voila, I had compareable Write speeds to 1.1, nearly 10MB/s.. Still this is far away from performance values I achive when doing a dd bs=3D1M to the NFS SAN, there I get about 45MB/s.. But using the async Option is not that perfect Solution for the Problem, because it increases the possibility to lose more Data in Case of powerloss or SAN Network Problem, because the NFS Server caches much more data then with a sync NFS mount. That leads us to Point 2... 2. I think besides the NFS sync/async Option xapi could do much better if the blocksize would be increased to a much higher value. I don't have enough insight into the internal of xapi so I can't tell if something special has been specified to fwrite(), but if it's default it's 4k, and that would match the performance Values we got when dd'ing with bs=3D4k.. What can we do about it? greetings, Bastian Am 18.12.2012 16:13, schrieb Bastian M=E4user: > Hi Guys, > > i just put a little Cluster in Testing with XCP 1.6... The most strange > thing i noticed is the really really slow imports and explorts of the > xen-api... > > When migrating VM's from my 1.1 to the 1.6 Cluster i do export them onto > a NFS Share with one pool, and re-import them on the 1.6 pool. > > Export on the 1.1 Cluster is really ok. I think about 200-300mbit/s net, > maybe the NFS Server is here the limiting Component. > > Import/Export in/from the 1.6 Cluster is a hell. > > Yesterday it took my awesome 487 Minutes to export a VM of roughly 40gb: > > [root@xcp2 615824d1-1aeb-7054-cc07-417ba25c78f0]# time xe vm-export > vm=3Drsa2 filename=3Drsa2-test-unc.xva compress=3Dfalse > Export succeeded > > real 487m33.284s > user 0m25.810s > sys 6m26.960s > > [root@xcp2 615824d1-1aeb-7054-cc07-417ba25c78f0]# ls -lah|grep rsa2 > -rw------- 1 nfsnobody nfsnobody 38G 18. Dez 04:50 rsa2-test-unc.xva > > Exporting that VM from the Other Cluster takes about 35 Minutes.. > > Network + Hardware is fine... Inside a VM on the 1.6 Cluster I get about > 55mb/s Disk performance.. and about 45mb/s to the NFS Server. > > I've spend quite some time now to find out where the Bottleneck ist.. > > Any Ideas on that? > > thanks, > Bastian > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 04 19:30:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 04 Jan 2013 19:30:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrCy2-0006UM-RV; Fri, 04 Jan 2013 19:30:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrCy0-0006UH-Vi for xen-api@lists.xen.org; Fri, 04 Jan 2013 19:30:09 +0000 Received: from [85.158.139.211:39714] by server-5.bemta-5.messagelabs.com id C4/1D-22648-FBD27E05; Fri, 04 Jan 2013 19:30:07 +0000 X-Env-Sender: mephisto@mephis.to X-Msg-Ref: server-9.tower-206.messagelabs.com!1357327801!20311569!1 X-Originating-IP: [212.77.170.22] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3743 invoked from network); 4 Jan 2013 19:30:06 -0000 Received: from mx2.netzblick.de (HELO mx2.netzblick.de) (212.77.170.22) by server-9.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2013 19:30:06 -0000 Received: from [192.168.7.3] (core.niedermayr.de [213.166.224.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.netzblick.de (Postfix) with ESMTP id 1FB73280B2; Fri, 4 Jan 2013 20:30:01 +0100 (CET) Message-ID: <50E72DB3.5050401@mephis.to> Date: Fri, 04 Jan 2013 20:29:55 +0100 From: =?ISO-8859-1?Q?Bastian_M=E4user?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: xen-api@lists.xen.org, mike.mcclurg@citrix.com, 2rushikeshj@gmail.com References: <50D08835.30708@mephis.to> In-Reply-To: <50D08835.30708@mephis.to> X-Enigmail-Version: 1.4.4 Subject: Re: [Xen-API] Poor xapi Performance Exporting/Importing VM's on XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Ok, here goes an update on the Problem, which I evaluated in a nightly session with kind help of Trixboxer from the #xen-api irc-channel on freenode. I think it's a duplicate of the Problem of another User posted here: http://www.gossamer-threads.com/lists/xen/api/258377 There are 2 factors causing the bad performance while importing and even more exporting VM's via CLI on a shares NFS SR. Here goes our Test Setting: 2 Pools one XCP1.1, one XCP1.6 - both using the vanilly XCP iso.. both sharing the same iSCSI and Management Network (1GBe) SAN's used: 1.1. Pool SAN: HP Lefthand P4000 VSA 1.6. Pool SAN: Easyraid Q16+ NAS used: Same NFS NAS for 1.1 and 1.6 (Dual CPU Xeon E5310 @ 1.60GHz w/ EasyRaid U320 SCSI Raid) GBe connected The Nodes used for xe vm-export/import had no domU's running, and the Monitoring was showing a very low Network Utilization in both the SAN as well as the Management Network. >>>>>>>> 1. From XCP1.1 to XCP1.6 the Operating System Default values regarding NFS Mounts moght have changed. We found out that In 1.1 the default NFS mount option is "async" in 1.6 the default is "sync". That causes a very bad performance when writing to NFS NAS's with a moderate IOPS Performance. The difference is ~10MB/s on 1.1 compared to 1.5MB/s on 1.6. To test it I dismounted the xapi mounted NFS SR on a node of the 1.6 Pool and remounted it with "async". Voila, I had compareable Write speeds to 1.1, nearly 10MB/s.. Still this is far away from performance values I achive when doing a dd bs=3D1M to the NFS SAN, there I get about 45MB/s.. But using the async Option is not that perfect Solution for the Problem, because it increases the possibility to lose more Data in Case of powerloss or SAN Network Problem, because the NFS Server caches much more data then with a sync NFS mount. That leads us to Point 2... 2. I think besides the NFS sync/async Option xapi could do much better if the blocksize would be increased to a much higher value. I don't have enough insight into the internal of xapi so I can't tell if something special has been specified to fwrite(), but if it's default it's 4k, and that would match the performance Values we got when dd'ing with bs=3D4k.. What can we do about it? greetings, Bastian Am 18.12.2012 16:13, schrieb Bastian M=E4user: > Hi Guys, > > i just put a little Cluster in Testing with XCP 1.6... The most strange > thing i noticed is the really really slow imports and explorts of the > xen-api... > > When migrating VM's from my 1.1 to the 1.6 Cluster i do export them onto > a NFS Share with one pool, and re-import them on the 1.6 pool. > > Export on the 1.1 Cluster is really ok. I think about 200-300mbit/s net, > maybe the NFS Server is here the limiting Component. > > Import/Export in/from the 1.6 Cluster is a hell. > > Yesterday it took my awesome 487 Minutes to export a VM of roughly 40gb: > > [root@xcp2 615824d1-1aeb-7054-cc07-417ba25c78f0]# time xe vm-export > vm=3Drsa2 filename=3Drsa2-test-unc.xva compress=3Dfalse > Export succeeded > > real 487m33.284s > user 0m25.810s > sys 6m26.960s > > [root@xcp2 615824d1-1aeb-7054-cc07-417ba25c78f0]# ls -lah|grep rsa2 > -rw------- 1 nfsnobody nfsnobody 38G 18. Dez 04:50 rsa2-test-unc.xva > > Exporting that VM from the Other Cluster takes about 35 Minutes.. > > Network + Hardware is fine... Inside a VM on the 1.6 Cluster I get about > 55mb/s Disk performance.. and about 45mb/s to the NFS Server. > > I've spend quite some time now to find out where the Bottleneck ist.. > > Any Ideas on that? > > thanks, > Bastian > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Jan 05 00:57:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 00:57:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrI4X-0003Fl-1t; Sat, 05 Jan 2013 00:57:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrI4W-0003Fg-6l for xen-api@lists.xen.org; Sat, 05 Jan 2013 00:57:12 +0000 Received: from [85.158.143.99:35998] by server-1.bemta-4.messagelabs.com id EA/74-28401-76A77E05; Sat, 05 Jan 2013 00:57:11 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1357347429!26728891!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16108 invoked from network); 5 Jan 2013 00:57:10 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-7.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Jan 2013 00:57:10 -0000 Received: from [187.233.68.172] (port=46864 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TrI4T-0006xm-3A for xen-api@lists.xen.org; Fri, 04 Jan 2013 18:57:09 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 83837A209 for ; Fri, 4 Jan 2013 18:54:22 -0600 (CST) Message-ID: <50E77A63.4040806@ondore.com> Date: Fri, 04 Jan 2013 18:57:07 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. I'm trying to mount VM's disk within Control Domain, as part of my pre-production tests. My XCP 1.6 installation uses a LVM based local storage after a default install. The VM's disks are in VHD format. In my previous Xen experience, with "raw" volumes as virtual hard disks, I have successfully used kpartx, with images stored in files and LVM. Clearly, kpartx can't map partitions of a VHD volume. Within the XCP installation I have found vhdpartx utility, judging by it's name and --help output I expected it to be just the tool I need. But it's seems there is some problem if I try to use it as kpartx: [root@xcp47 ~]# lvscan ACTIVE '/dev/VG_XenStorage-cfc7419f-8b4e-8c51-d619-dfdee09841a2/MGT' [4.00 MB] inherit ACTIVE '/dev/VG_XenStorage-cfc7419f-8b4e-8c51-d619-dfdee09841a2/VHD-bbdf149e-4b41-4a6a-9059-9251365a0a86' [8.02 GB] inherit ACTIVE '/dev/VG_XenStorage-cfc7419f-8b4e-8c51-d619-dfdee09841a2/VHD-fd118da1-c3dd-466b-8b27-32c5db1fcce7' [3.01 GB] inherit [root@xcp47 ~]# vhdpartx -a /dev/VG_XenStorage-cfc7419f-8b4e-8c51-d619-dfdee09841a2/VHD-fd118da1-c3dd-466b-8b27-32c5db1fcce7 can't find vhd or lib [root@xcp47 ~]# Unfortunately, there is no online man page available in my XCP installation, and blktap2 documentation mostly covers Xen's config file syntax to to use with VHD storage. The idea to treat the VHD as a black box is not appealing at all. Is there a regular way to access VHD from Dom0? What's wrong with my vhdpartx, maybe it is supposed to work in a different way? I have done my search for alternatives and the most promising reference I've found was one that suggests attaching the VDI (or it's snapshot) to the Dom0 via a manually created VBD, just as if it was a regular VM. http://forums.citrix.com/thread.jspa?threadID=252142 It's quite old, and I did not get that solution work ether: I can do all the steps, but the disk never showed up within Dom0, even after I "vbd-plug" it. Thank you. -- Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Jan 05 00:57:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 00:57:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrI4X-0003Fl-1t; Sat, 05 Jan 2013 00:57:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrI4W-0003Fg-6l for xen-api@lists.xen.org; Sat, 05 Jan 2013 00:57:12 +0000 Received: from [85.158.143.99:35998] by server-1.bemta-4.messagelabs.com id EA/74-28401-76A77E05; Sat, 05 Jan 2013 00:57:11 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1357347429!26728891!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16108 invoked from network); 5 Jan 2013 00:57:10 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-7.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Jan 2013 00:57:10 -0000 Received: from [187.233.68.172] (port=46864 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TrI4T-0006xm-3A for xen-api@lists.xen.org; Fri, 04 Jan 2013 18:57:09 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 83837A209 for ; Fri, 4 Jan 2013 18:54:22 -0600 (CST) Message-ID: <50E77A63.4040806@ondore.com> Date: Fri, 04 Jan 2013 18:57:07 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. I'm trying to mount VM's disk within Control Domain, as part of my pre-production tests. My XCP 1.6 installation uses a LVM based local storage after a default install. The VM's disks are in VHD format. In my previous Xen experience, with "raw" volumes as virtual hard disks, I have successfully used kpartx, with images stored in files and LVM. Clearly, kpartx can't map partitions of a VHD volume. Within the XCP installation I have found vhdpartx utility, judging by it's name and --help output I expected it to be just the tool I need. But it's seems there is some problem if I try to use it as kpartx: [root@xcp47 ~]# lvscan ACTIVE '/dev/VG_XenStorage-cfc7419f-8b4e-8c51-d619-dfdee09841a2/MGT' [4.00 MB] inherit ACTIVE '/dev/VG_XenStorage-cfc7419f-8b4e-8c51-d619-dfdee09841a2/VHD-bbdf149e-4b41-4a6a-9059-9251365a0a86' [8.02 GB] inherit ACTIVE '/dev/VG_XenStorage-cfc7419f-8b4e-8c51-d619-dfdee09841a2/VHD-fd118da1-c3dd-466b-8b27-32c5db1fcce7' [3.01 GB] inherit [root@xcp47 ~]# vhdpartx -a /dev/VG_XenStorage-cfc7419f-8b4e-8c51-d619-dfdee09841a2/VHD-fd118da1-c3dd-466b-8b27-32c5db1fcce7 can't find vhd or lib [root@xcp47 ~]# Unfortunately, there is no online man page available in my XCP installation, and blktap2 documentation mostly covers Xen's config file syntax to to use with VHD storage. The idea to treat the VHD as a black box is not appealing at all. Is there a regular way to access VHD from Dom0? What's wrong with my vhdpartx, maybe it is supposed to work in a different way? I have done my search for alternatives and the most promising reference I've found was one that suggests attaching the VDI (or it's snapshot) to the Dom0 via a manually created VBD, just as if it was a regular VM. http://forums.citrix.com/thread.jspa?threadID=252142 It's quite old, and I did not get that solution work ether: I can do all the steps, but the disk never showed up within Dom0, even after I "vbd-plug" it. Thank you. -- Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Jan 05 00:57:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 00:57:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrI4e-0003Fx-7S; Sat, 05 Jan 2013 00:57:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrI4c-0003Fs-Ov for xen-api@lists.xen.org; Sat, 05 Jan 2013 00:57:18 +0000 Received: from [85.158.138.51:53897] by server-12.bemta-3.messagelabs.com id 66/6C-27559-96A77E05; Sat, 05 Jan 2013 00:57:13 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1357347432!9395890!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8568 invoked from network); 5 Jan 2013 00:57:13 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Jan 2013 00:57:13 -0000 Received: from [187.233.68.172] (port=46866 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TrI4V-0006xu-EN for xen-api@lists.xen.org; Fri, 04 Jan 2013 18:57:11 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id EBB7FA209 for ; Fri, 4 Jan 2013 18:54:24 -0600 (CST) Message-ID: <50E77A66.5070509@ondore.com> Date: Fri, 04 Jan 2013 18:57:10 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: [Xen-API] VHD vs RAW disk images in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. While dealing with pre-production tests in XCP 1.6, I found it difficult to access the VM's disks while they are in VHD mode. The ability to be able to mount VM's storage within Dom0 is one of my production requirements. So, I'm seriously considering to use RAW images instead of VHD, which are easily accessible with help of kpartx. What will I miss? As far as I have read, the main advantage of VHD is to do fancy things, like snapshots, while the image is stored in file. Since LVM already provides me that, I see no need of VHD. Besides, I expect VHD to be slower than RAW. How can I make RAW mode to be the default, when a new VDI is created? I have not reach the VM deployment automatation stage yet, it's clear I need to consider it when decide for RAW images over VHD. Thank you. -- Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Jan 05 00:57:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 00:57:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrI4e-0003Fx-7S; Sat, 05 Jan 2013 00:57:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrI4c-0003Fs-Ov for xen-api@lists.xen.org; Sat, 05 Jan 2013 00:57:18 +0000 Received: from [85.158.138.51:53897] by server-12.bemta-3.messagelabs.com id 66/6C-27559-96A77E05; Sat, 05 Jan 2013 00:57:13 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1357347432!9395890!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8568 invoked from network); 5 Jan 2013 00:57:13 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Jan 2013 00:57:13 -0000 Received: from [187.233.68.172] (port=46866 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TrI4V-0006xu-EN for xen-api@lists.xen.org; Fri, 04 Jan 2013 18:57:11 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id EBB7FA209 for ; Fri, 4 Jan 2013 18:54:24 -0600 (CST) Message-ID: <50E77A66.5070509@ondore.com> Date: Fri, 04 Jan 2013 18:57:10 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: [Xen-API] VHD vs RAW disk images in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. While dealing with pre-production tests in XCP 1.6, I found it difficult to access the VM's disks while they are in VHD mode. The ability to be able to mount VM's storage within Dom0 is one of my production requirements. So, I'm seriously considering to use RAW images instead of VHD, which are easily accessible with help of kpartx. What will I miss? As far as I have read, the main advantage of VHD is to do fancy things, like snapshots, while the image is stored in file. Since LVM already provides me that, I see no need of VHD. Besides, I expect VHD to be slower than RAW. How can I make RAW mode to be the default, when a new VDI is created? I have not reach the VM deployment automatation stage yet, it's clear I need to consider it when decide for RAW images over VHD. Thank you. -- Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Jan 05 01:09:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 01:09:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrIGW-0007KS-JU; Sat, 05 Jan 2013 01:09:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrIGV-0007KN-4y for xen-api@lists.xen.org; Sat, 05 Jan 2013 01:09:35 +0000 Received: from [85.158.138.51:45080] by server-11.bemta-3.messagelabs.com id 66/B1-13335-E4D77E05; Sat, 05 Jan 2013 01:09:34 +0000 X-Env-Sender: revanth.vn471@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1357348173!25112062!1 X-Originating-IP: [209.85.215.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31136 invoked from network); 5 Jan 2013 01:09:33 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jan 2013 01:09:33 -0000 Received: by mail-la0-f52.google.com with SMTP id fq12so10454111lab.25 for ; Fri, 04 Jan 2013 17:09:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LJrlFxpQ4n5KXKgeoKR1wEEy867AS+Se0bzRSakX8to=; b=aMPCYDxzm0m/b5E4jA9XIabJwc7+Di1ReDzkUnCqDa7fhiEUT/3HmgiNnw9VSzP+Xy 5TMBAh+bg7TLH3IkOkvApkK6UvqikRrO1pcRRAa/Nkpbk8+CvpGAvKIcCHoh7c9KrYFx K07dLtm4pYJLx1pTOWiDl01fOdaO06M5Ihar6O/EqC35k7b/pf5795lrtVgiYQQmjd+6 hwLfVt0EU/yDtdzFbytnB89k3ib2/A2s2QqnJYNC3y1iZ7zYJ2orY+jCJwgy75OMJxlR b/o7SjESnFR+e+RQ+kZ3p9HslZBzEr30VGwbPgGKPxtJypuqaP+4Jqep3FFFEPBgwKd9 knBg== MIME-Version: 1.0 Received: by 10.152.105.203 with SMTP id go11mr51410227lab.53.1357348172932; Fri, 04 Jan 2013 17:09:32 -0800 (PST) Received: by 10.112.55.132 with HTTP; Fri, 4 Jan 2013 17:09:32 -0800 (PST) Date: Fri, 4 Jan 2013 19:09:32 -0600 Message-ID: From: Raja Revanth Narisetty To: xen-api@lists.xen.org Subject: [Xen-API] Traffic Generation Tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4833315557660211145==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4833315557660211145== Content-Type: multipart/alternative; boundary=f46d04083e33af266704d2803fbd --f46d04083e33af266704d2803fbd Content-Type: text/plain; charset=ISO-8859-1 Hi All, I would like to simulate/generate traffic between VMs in my XEN cloud. Can you please let me know few traffic generation tools. Thanks in advance, Revanth --f46d04083e33af266704d2803fbd Content-Type: text/html; charset=ISO-8859-1 Hi All,
I would like to simulate/generate traffic between VMs in my XEN cloud.
Can you please let me know few traffic generation tools.

Thanks in advance,
Revanth
--f46d04083e33af266704d2803fbd-- --===============4833315557660211145== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4833315557660211145==-- From xen-api-bounces@lists.xen.org Sat Jan 05 01:09:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 01:09:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrIGW-0007KS-JU; Sat, 05 Jan 2013 01:09:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrIGV-0007KN-4y for xen-api@lists.xen.org; Sat, 05 Jan 2013 01:09:35 +0000 Received: from [85.158.138.51:45080] by server-11.bemta-3.messagelabs.com id 66/B1-13335-E4D77E05; Sat, 05 Jan 2013 01:09:34 +0000 X-Env-Sender: revanth.vn471@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1357348173!25112062!1 X-Originating-IP: [209.85.215.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31136 invoked from network); 5 Jan 2013 01:09:33 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jan 2013 01:09:33 -0000 Received: by mail-la0-f52.google.com with SMTP id fq12so10454111lab.25 for ; Fri, 04 Jan 2013 17:09:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LJrlFxpQ4n5KXKgeoKR1wEEy867AS+Se0bzRSakX8to=; b=aMPCYDxzm0m/b5E4jA9XIabJwc7+Di1ReDzkUnCqDa7fhiEUT/3HmgiNnw9VSzP+Xy 5TMBAh+bg7TLH3IkOkvApkK6UvqikRrO1pcRRAa/Nkpbk8+CvpGAvKIcCHoh7c9KrYFx K07dLtm4pYJLx1pTOWiDl01fOdaO06M5Ihar6O/EqC35k7b/pf5795lrtVgiYQQmjd+6 hwLfVt0EU/yDtdzFbytnB89k3ib2/A2s2QqnJYNC3y1iZ7zYJ2orY+jCJwgy75OMJxlR b/o7SjESnFR+e+RQ+kZ3p9HslZBzEr30VGwbPgGKPxtJypuqaP+4Jqep3FFFEPBgwKd9 knBg== MIME-Version: 1.0 Received: by 10.152.105.203 with SMTP id go11mr51410227lab.53.1357348172932; Fri, 04 Jan 2013 17:09:32 -0800 (PST) Received: by 10.112.55.132 with HTTP; Fri, 4 Jan 2013 17:09:32 -0800 (PST) Date: Fri, 4 Jan 2013 19:09:32 -0600 Message-ID: From: Raja Revanth Narisetty To: xen-api@lists.xen.org Subject: [Xen-API] Traffic Generation Tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4833315557660211145==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4833315557660211145== Content-Type: multipart/alternative; boundary=f46d04083e33af266704d2803fbd --f46d04083e33af266704d2803fbd Content-Type: text/plain; charset=ISO-8859-1 Hi All, I would like to simulate/generate traffic between VMs in my XEN cloud. Can you please let me know few traffic generation tools. Thanks in advance, Revanth --f46d04083e33af266704d2803fbd Content-Type: text/html; charset=ISO-8859-1 Hi All,
I would like to simulate/generate traffic between VMs in my XEN cloud.
Can you please let me know few traffic generation tools.

Thanks in advance,
Revanth
--f46d04083e33af266704d2803fbd-- --===============4833315557660211145== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4833315557660211145==-- From xen-api-bounces@lists.xen.org Sat Jan 05 01:24:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 01:24:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrIUT-0007Uk-WE; Sat, 05 Jan 2013 01:24:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrIUS-0007Uf-8u for xen-api@lists.xen.org; Sat, 05 Jan 2013 01:24:00 +0000 Received: from [85.158.143.99:26689] by server-1.bemta-4.messagelabs.com id 0B/39-28401-FA087E05; Sat, 05 Jan 2013 01:23:59 +0000 X-Env-Sender: david.ribeiro76@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1357349038!24890469!1 X-Originating-IP: [74.125.82.181] X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5659 invoked from network); 5 Jan 2013 01:23:59 -0000 Received: from mail-we0-f181.google.com (HELO mail-we0-f181.google.com) (74.125.82.181) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jan 2013 01:23:59 -0000 Received: by mail-we0-f181.google.com with SMTP id t11so7953767wey.26 for ; Fri, 04 Jan 2013 17:23:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to; bh=uuZX/pGomppM+6gNyll/Ej72rNlP4FCmBxa68Kz7LAU=; b=H7QZUrPEh2ygkW9qP44CbR6o35YycTj0v258bZeXjDfK7LwOHZpqoW+9FMJ3QQRqG6 6noWSb1YFJQhWeEgGDWFOj15zeuEcScyOMHMPWglDOe2SIHFpBd50FBOwb8llWnK+ZO/ Q4ODDeD6gQ/d1F//SKLXuDkJo47z63DmIS0QJyhhASNN69jYBq6ephgs2tqKJAVQwtsQ sPSDV4/VVbxvfOmfGLi2P/VqTQ9XlsCrs7lmLa7p4WVgIuNXQu3SxkaWlq6eqIwg0bHc o+PaQY9gaXu6hxzkfjPLAvd9YEDC+5NvbSFM+wKodNfqIj+NPJYzO9bsef9sDXiAUjKV Ke3w== X-Received: by 10.180.95.135 with SMTP id dk7mr388948wib.29.1357349038725; Fri, 04 Jan 2013 17:23:58 -0800 (PST) Received: from [192.168.0.101] (home.tosage.fr. [88.184.97.154]) by mx.google.com with ESMTPS id ew4sm1580335wid.11.2013.01.04.17.23.57 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Jan 2013 17:23:57 -0800 (PST) References: In-Reply-To: Mime-Version: 1.0 (1.0) Message-Id: <875E47E4-3C21-4597-A76B-A2DFD4FC740E@gmail.com> X-Mailer: iPhone Mail (9B206) From: David Ribeiro Date: Sat, 5 Jan 2013 02:23:54 +0100 To: Raja Revanth Narisetty Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Traffic Generation Tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SXBlcmYgPwoKRGF2aWQKCkxlIDUgamFudi4gMjAxMyDDoCAwMjowOSwgUmFqYSBSZXZhbnRoIE5h cmlzZXR0eSA8cmV2YW50aC52bjQ3MUBnbWFpbC5jb20+IGEgw6ljcml0IDoKCj4gSGkgQWxsLAo+ IEkgd291bGQgbGlrZSB0byBzaW11bGF0ZS9nZW5lcmF0ZSB0cmFmZmljIGJldHdlZW4gVk1zIGlu IG15IFhFTiBjbG91ZC4KPiBDYW4geW91IHBsZWFzZSBsZXQgbWUga25vdyBmZXcgdHJhZmZpYyBn ZW5lcmF0aW9uIHRvb2xzLgo+IAo+IFRoYW5rcyBpbiBhZHZhbmNlLAo+IFJldmFudGgKPiBfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1hcGkgbWFp bGluZyBsaXN0Cj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcv Y2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKCl9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlz dHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8v eGVuLWFwaQo= From xen-api-bounces@lists.xen.org Sat Jan 05 01:24:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 01:24:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrIUT-0007Uk-WE; Sat, 05 Jan 2013 01:24:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrIUS-0007Uf-8u for xen-api@lists.xen.org; Sat, 05 Jan 2013 01:24:00 +0000 Received: from [85.158.143.99:26689] by server-1.bemta-4.messagelabs.com id 0B/39-28401-FA087E05; Sat, 05 Jan 2013 01:23:59 +0000 X-Env-Sender: david.ribeiro76@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1357349038!24890469!1 X-Originating-IP: [74.125.82.181] X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5659 invoked from network); 5 Jan 2013 01:23:59 -0000 Received: from mail-we0-f181.google.com (HELO mail-we0-f181.google.com) (74.125.82.181) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jan 2013 01:23:59 -0000 Received: by mail-we0-f181.google.com with SMTP id t11so7953767wey.26 for ; Fri, 04 Jan 2013 17:23:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to; bh=uuZX/pGomppM+6gNyll/Ej72rNlP4FCmBxa68Kz7LAU=; b=H7QZUrPEh2ygkW9qP44CbR6o35YycTj0v258bZeXjDfK7LwOHZpqoW+9FMJ3QQRqG6 6noWSb1YFJQhWeEgGDWFOj15zeuEcScyOMHMPWglDOe2SIHFpBd50FBOwb8llWnK+ZO/ Q4ODDeD6gQ/d1F//SKLXuDkJo47z63DmIS0QJyhhASNN69jYBq6ephgs2tqKJAVQwtsQ sPSDV4/VVbxvfOmfGLi2P/VqTQ9XlsCrs7lmLa7p4WVgIuNXQu3SxkaWlq6eqIwg0bHc o+PaQY9gaXu6hxzkfjPLAvd9YEDC+5NvbSFM+wKodNfqIj+NPJYzO9bsef9sDXiAUjKV Ke3w== X-Received: by 10.180.95.135 with SMTP id dk7mr388948wib.29.1357349038725; Fri, 04 Jan 2013 17:23:58 -0800 (PST) Received: from [192.168.0.101] (home.tosage.fr. [88.184.97.154]) by mx.google.com with ESMTPS id ew4sm1580335wid.11.2013.01.04.17.23.57 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Jan 2013 17:23:57 -0800 (PST) References: In-Reply-To: Mime-Version: 1.0 (1.0) Message-Id: <875E47E4-3C21-4597-A76B-A2DFD4FC740E@gmail.com> X-Mailer: iPhone Mail (9B206) From: David Ribeiro Date: Sat, 5 Jan 2013 02:23:54 +0100 To: Raja Revanth Narisetty Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Traffic Generation Tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SXBlcmYgPwoKRGF2aWQKCkxlIDUgamFudi4gMjAxMyDDoCAwMjowOSwgUmFqYSBSZXZhbnRoIE5h cmlzZXR0eSA8cmV2YW50aC52bjQ3MUBnbWFpbC5jb20+IGEgw6ljcml0IDoKCj4gSGkgQWxsLAo+ IEkgd291bGQgbGlrZSB0byBzaW11bGF0ZS9nZW5lcmF0ZSB0cmFmZmljIGJldHdlZW4gVk1zIGlu IG15IFhFTiBjbG91ZC4KPiBDYW4geW91IHBsZWFzZSBsZXQgbWUga25vdyBmZXcgdHJhZmZpYyBn ZW5lcmF0aW9uIHRvb2xzLgo+IAo+IFRoYW5rcyBpbiBhZHZhbmNlLAo+IFJldmFudGgKPiBfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1hcGkgbWFp bGluZyBsaXN0Cj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcv Y2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKCl9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlz dHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8v eGVuLWFwaQo= From xen-api-bounces@lists.xen.org Sat Jan 05 05:14:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 05:14:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrM5o-0002IM-I8; Sat, 05 Jan 2013 05:14:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrM5n-0002IG-PB for xen-api@lists.xen.org; Sat, 05 Jan 2013 05:14:47 +0000 Received: from [85.158.138.51:58450] by server-6.bemta-3.messagelabs.com id 8A/2E-12154-6C6B7E05; Sat, 05 Jan 2013 05:14:46 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1357362885!29551039!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=1.8 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12960 invoked from network); 5 Jan 2013 05:14:46 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jan 2013 05:14:46 -0000 Received: by mail-la0-f43.google.com with SMTP id eg20so10912855lab.30 for ; Fri, 04 Jan 2013 21:14:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ebZATXY1uJrPkFPa5r0U96O3/LwqG4qVgwQHYFMAcco=; b=Io/LOznRdeN4XWxUZpmx6Q8yV6HnXK5lMU2ueQPZ1pvTcURRwbLhramh6YaAa0Q0WU UGslYdKrNG3bk9oAIiKPLp3VYNeq4gffvm4HWRa9p3abTw84850Mp9Bn2H9mauyDJQSe BAwLsRFOF9ytOe28pW7+gahIJxrPb8MTidCB6NTuREv6g4fcZEgcDpEhK7DWm1LJhc// t5D06BiJBNEhpWguWWNjB3Yoayj6cgCSZtDZJn+KpSy5uu+pQkHRFjYLTybt6EXZ1aos ncU3wnDNs6+C8V8U47Pqtjb/Qb2LdLslzdOjT1Kn4CbufaLIE65xLZ4kOWNtlEC5hiBt DRgQ== X-Received: by 10.152.132.137 with SMTP id ou9mr52622815lab.7.1357362885378; Fri, 04 Jan 2013 21:14:45 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id er8sm18511484lbb.9.2013.01.04.21.14.44 (version=SSLv3 cipher=OTHER); Fri, 04 Jan 2013 21:14:44 -0800 (PST) Message-ID: <50E7B6C4.2010705@gmail.com> Date: Sat, 05 Jan 2013 09:14:44 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> In-Reply-To: <50E77A63.4040806@ondore.com> Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WW91IGRvaW5nIGl0IHdyb25nLgoKVXNlIHhlIHZiZC1jcmVhdGUgYmV0d2VlbiB2ZGkgYW5kIGRv bTAgKHdoaWNoIGlzIG5vcm1hbCBWTSBtb3N0bHkpLCBhbmQgCnhlIHZiZC1wbHVnLgoKWW91IGNh biBzZWUgc29tZSBzYW1wbGUgdXNhZ2UgaW4gJ3hlLWVkaXQtYm9vdGxvYWRlcicgY29tbWFuZCAo c29tZXdoZXJlIAppbiAvb3B0L3hlbnNvdXJjZS8pCgowNS4wMS4yMDEzIDA0OjU3LCBBbGV4YW5k cmUgS291em5ldHNvdiDQv9C40YjQtdGCOgo+IEhlbGxvLgo+Cj4gSSdtIHRyeWluZyB0byBtb3Vu dCBWTSdzIGRpc2sgd2l0aGluIENvbnRyb2wgRG9tYWluLCBhcyBwYXJ0IG9mIG15IAo+IHByZS1w cm9kdWN0aW9uIHRlc3RzLiBNeSBYQ1AgMS42IGluc3RhbGxhdGlvbiB1c2VzIGEgTFZNIGJhc2Vk IGxvY2FsIAo+IHN0b3JhZ2UgYWZ0ZXIgYSBkZWZhdWx0IGluc3RhbGwuIFRoZSBWTSdzIGRpc2tz IGFyZSBpbiBWSEQgZm9ybWF0Lgo+Cj4gSW4gbXkgcHJldmlvdXMgWGVuIGV4cGVyaWVuY2UsIHdp dGggInJhdyIgdm9sdW1lcyBhcyB2aXJ0dWFsIGhhcmQgCj4gZGlza3MsIEkgaGF2ZSBzdWNjZXNz ZnVsbHkgdXNlZCBrcGFydHgsIHdpdGggaW1hZ2VzIHN0b3JlZCBpbiBmaWxlcyAKPiBhbmQgTFZN LiBDbGVhcmx5LCBrcGFydHggY2FuJ3QgbWFwIHBhcnRpdGlvbnMgb2YgYSBWSEQgdm9sdW1lLgo+ Cj4gV2l0aGluIHRoZSBYQ1AgaW5zdGFsbGF0aW9uIEkgaGF2ZSBmb3VuZCB2aGRwYXJ0eCB1dGls aXR5LCBqdWRnaW5nIGJ5IAo+IGl0J3MgbmFtZSBhbmQgLS1oZWxwIG91dHB1dCBJIGV4cGVjdGVk IGl0IHRvIGJlIGp1c3QgdGhlIHRvb2wgSSBuZWVkLiAKPiBCdXQgaXQncyBzZWVtcyB0aGVyZSBp cyBzb21lIHByb2JsZW0gaWYgSSB0cnkgdG8gdXNlIGl0IGFzIGtwYXJ0eDoKPgo+IFtyb290QHhj cDQ3IH5dIyBsdnNjYW4KPiBBQ1RJVkUgJy9kZXYvVkdfWGVuU3RvcmFnZS1jZmM3NDE5Zi04YjRl LThjNTEtZDYxOS1kZmRlZTA5ODQxYTIvTUdUJyAKPiBbNC4wMCBNQl0gaW5oZXJpdAo+IEFDVElW RSAKPiAnL2Rldi9WR19YZW5TdG9yYWdlLWNmYzc0MTlmLThiNGUtOGM1MS1kNjE5LWRmZGVlMDk4 NDFhMi9WSEQtYmJkZjE0OWUtNGI0MS00YTZhLTkwNTktOTI1MTM2NWEwYTg2JyAKPiBbOC4wMiBH Ql0gaW5oZXJpdAo+IEFDVElWRSAKPiAnL2Rldi9WR19YZW5TdG9yYWdlLWNmYzc0MTlmLThiNGUt OGM1MS1kNjE5LWRmZGVlMDk4NDFhMi9WSEQtZmQxMThkYTEtYzNkZC00NjZiLThiMjctMzJjNWRi MWZjY2U3JyAKPiBbMy4wMSBHQl0gaW5oZXJpdAo+IFtyb290QHhjcDQ3IH5dIyB2aGRwYXJ0eCAt YSAKPiAvZGV2L1ZHX1hlblN0b3JhZ2UtY2ZjNzQxOWYtOGI0ZS04YzUxLWQ2MTktZGZkZWUwOTg0 MWEyL1ZIRC1mZDExOGRhMS1jM2RkLTQ2NmItOGIyNy0zMmM1ZGIxZmNjZTcKPiBjYW4ndCBmaW5k IHZoZCBvciBsaWIKPiBbcm9vdEB4Y3A0NyB+XSMKPgo+IFVuZm9ydHVuYXRlbHksIHRoZXJlIGlz IG5vIG9ubGluZSBtYW4gcGFnZSBhdmFpbGFibGUgaW4gbXkgWENQIAo+IGluc3RhbGxhdGlvbiwg YW5kIGJsa3RhcDIgZG9jdW1lbnRhdGlvbiBtb3N0bHkgY292ZXJzIFhlbidzIGNvbmZpZyAKPiBm aWxlIHN5bnRheCB0byB0byB1c2Ugd2l0aCBWSEQgc3RvcmFnZS4KPgo+IFRoZSBpZGVhIHRvIHRy ZWF0IHRoZSBWSEQgYXMgYSBibGFjayBib3ggaXMgbm90IGFwcGVhbGluZyBhdCBhbGwuIElzIAo+ IHRoZXJlIGEgcmVndWxhciB3YXkgdG8gYWNjZXNzIFZIRCBmcm9tIERvbTA/IFdoYXQncyB3cm9u ZyB3aXRoIG15IAo+IHZoZHBhcnR4LCBtYXliZSBpdCBpcyBzdXBwb3NlZCB0byB3b3JrIGluIGEg ZGlmZmVyZW50IHdheT8KPgo+Cj4gSSBoYXZlIGRvbmUgbXkgc2VhcmNoIGZvciBhbHRlcm5hdGl2 ZXMgYW5kIHRoZSBtb3N0IHByb21pc2luZyAKPiByZWZlcmVuY2UgSSd2ZSBmb3VuZCB3YXMgb25l IHRoYXQgc3VnZ2VzdHMgYXR0YWNoaW5nIHRoZSBWREkgKG9yIGl0J3MgCj4gc25hcHNob3QpIHRv IHRoZSBEb20wIHZpYSBhIG1hbnVhbGx5IGNyZWF0ZWQgVkJELCBqdXN0IGFzIGlmIGl0IHdhcyBh IAo+IHJlZ3VsYXIgVk0uCj4gaHR0cDovL2ZvcnVtcy5jaXRyaXguY29tL3RocmVhZC5qc3BhP3Ro cmVhZElEPTI1MjE0Mgo+IEl0J3MgcXVpdGUgb2xkLCBhbmQgSSBkaWQgbm90IGdldCB0aGF0IHNv bHV0aW9uIHdvcmsgZXRoZXI6IEkgY2FuIGRvIAo+IGFsbCB0aGUgc3RlcHMsIGJ1dCB0aGUgZGlz ayBuZXZlciBzaG93ZWQgdXAgd2l0aGluIERvbTAsIGV2ZW4gYWZ0ZXIgSSAKPiAidmJkLXBsdWci IGl0Lgo+Cj4KPiBUaGFuayB5b3UuCj4KCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5v cmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Sat Jan 05 05:14:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 05:14:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrM5o-0002IM-I8; Sat, 05 Jan 2013 05:14:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrM5n-0002IG-PB for xen-api@lists.xen.org; Sat, 05 Jan 2013 05:14:47 +0000 Received: from [85.158.138.51:58450] by server-6.bemta-3.messagelabs.com id 8A/2E-12154-6C6B7E05; Sat, 05 Jan 2013 05:14:46 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1357362885!29551039!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=1.8 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12960 invoked from network); 5 Jan 2013 05:14:46 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jan 2013 05:14:46 -0000 Received: by mail-la0-f43.google.com with SMTP id eg20so10912855lab.30 for ; Fri, 04 Jan 2013 21:14:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ebZATXY1uJrPkFPa5r0U96O3/LwqG4qVgwQHYFMAcco=; b=Io/LOznRdeN4XWxUZpmx6Q8yV6HnXK5lMU2ueQPZ1pvTcURRwbLhramh6YaAa0Q0WU UGslYdKrNG3bk9oAIiKPLp3VYNeq4gffvm4HWRa9p3abTw84850Mp9Bn2H9mauyDJQSe BAwLsRFOF9ytOe28pW7+gahIJxrPb8MTidCB6NTuREv6g4fcZEgcDpEhK7DWm1LJhc// t5D06BiJBNEhpWguWWNjB3Yoayj6cgCSZtDZJn+KpSy5uu+pQkHRFjYLTybt6EXZ1aos ncU3wnDNs6+C8V8U47Pqtjb/Qb2LdLslzdOjT1Kn4CbufaLIE65xLZ4kOWNtlEC5hiBt DRgQ== X-Received: by 10.152.132.137 with SMTP id ou9mr52622815lab.7.1357362885378; Fri, 04 Jan 2013 21:14:45 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id er8sm18511484lbb.9.2013.01.04.21.14.44 (version=SSLv3 cipher=OTHER); Fri, 04 Jan 2013 21:14:44 -0800 (PST) Message-ID: <50E7B6C4.2010705@gmail.com> Date: Sat, 05 Jan 2013 09:14:44 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> In-Reply-To: <50E77A63.4040806@ondore.com> Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WW91IGRvaW5nIGl0IHdyb25nLgoKVXNlIHhlIHZiZC1jcmVhdGUgYmV0d2VlbiB2ZGkgYW5kIGRv bTAgKHdoaWNoIGlzIG5vcm1hbCBWTSBtb3N0bHkpLCBhbmQgCnhlIHZiZC1wbHVnLgoKWW91IGNh biBzZWUgc29tZSBzYW1wbGUgdXNhZ2UgaW4gJ3hlLWVkaXQtYm9vdGxvYWRlcicgY29tbWFuZCAo c29tZXdoZXJlIAppbiAvb3B0L3hlbnNvdXJjZS8pCgowNS4wMS4yMDEzIDA0OjU3LCBBbGV4YW5k cmUgS291em5ldHNvdiDQv9C40YjQtdGCOgo+IEhlbGxvLgo+Cj4gSSdtIHRyeWluZyB0byBtb3Vu dCBWTSdzIGRpc2sgd2l0aGluIENvbnRyb2wgRG9tYWluLCBhcyBwYXJ0IG9mIG15IAo+IHByZS1w cm9kdWN0aW9uIHRlc3RzLiBNeSBYQ1AgMS42IGluc3RhbGxhdGlvbiB1c2VzIGEgTFZNIGJhc2Vk IGxvY2FsIAo+IHN0b3JhZ2UgYWZ0ZXIgYSBkZWZhdWx0IGluc3RhbGwuIFRoZSBWTSdzIGRpc2tz IGFyZSBpbiBWSEQgZm9ybWF0Lgo+Cj4gSW4gbXkgcHJldmlvdXMgWGVuIGV4cGVyaWVuY2UsIHdp dGggInJhdyIgdm9sdW1lcyBhcyB2aXJ0dWFsIGhhcmQgCj4gZGlza3MsIEkgaGF2ZSBzdWNjZXNz ZnVsbHkgdXNlZCBrcGFydHgsIHdpdGggaW1hZ2VzIHN0b3JlZCBpbiBmaWxlcyAKPiBhbmQgTFZN LiBDbGVhcmx5LCBrcGFydHggY2FuJ3QgbWFwIHBhcnRpdGlvbnMgb2YgYSBWSEQgdm9sdW1lLgo+ Cj4gV2l0aGluIHRoZSBYQ1AgaW5zdGFsbGF0aW9uIEkgaGF2ZSBmb3VuZCB2aGRwYXJ0eCB1dGls aXR5LCBqdWRnaW5nIGJ5IAo+IGl0J3MgbmFtZSBhbmQgLS1oZWxwIG91dHB1dCBJIGV4cGVjdGVk IGl0IHRvIGJlIGp1c3QgdGhlIHRvb2wgSSBuZWVkLiAKPiBCdXQgaXQncyBzZWVtcyB0aGVyZSBp cyBzb21lIHByb2JsZW0gaWYgSSB0cnkgdG8gdXNlIGl0IGFzIGtwYXJ0eDoKPgo+IFtyb290QHhj cDQ3IH5dIyBsdnNjYW4KPiBBQ1RJVkUgJy9kZXYvVkdfWGVuU3RvcmFnZS1jZmM3NDE5Zi04YjRl LThjNTEtZDYxOS1kZmRlZTA5ODQxYTIvTUdUJyAKPiBbNC4wMCBNQl0gaW5oZXJpdAo+IEFDVElW RSAKPiAnL2Rldi9WR19YZW5TdG9yYWdlLWNmYzc0MTlmLThiNGUtOGM1MS1kNjE5LWRmZGVlMDk4 NDFhMi9WSEQtYmJkZjE0OWUtNGI0MS00YTZhLTkwNTktOTI1MTM2NWEwYTg2JyAKPiBbOC4wMiBH Ql0gaW5oZXJpdAo+IEFDVElWRSAKPiAnL2Rldi9WR19YZW5TdG9yYWdlLWNmYzc0MTlmLThiNGUt OGM1MS1kNjE5LWRmZGVlMDk4NDFhMi9WSEQtZmQxMThkYTEtYzNkZC00NjZiLThiMjctMzJjNWRi MWZjY2U3JyAKPiBbMy4wMSBHQl0gaW5oZXJpdAo+IFtyb290QHhjcDQ3IH5dIyB2aGRwYXJ0eCAt YSAKPiAvZGV2L1ZHX1hlblN0b3JhZ2UtY2ZjNzQxOWYtOGI0ZS04YzUxLWQ2MTktZGZkZWUwOTg0 MWEyL1ZIRC1mZDExOGRhMS1jM2RkLTQ2NmItOGIyNy0zMmM1ZGIxZmNjZTcKPiBjYW4ndCBmaW5k IHZoZCBvciBsaWIKPiBbcm9vdEB4Y3A0NyB+XSMKPgo+IFVuZm9ydHVuYXRlbHksIHRoZXJlIGlz IG5vIG9ubGluZSBtYW4gcGFnZSBhdmFpbGFibGUgaW4gbXkgWENQIAo+IGluc3RhbGxhdGlvbiwg YW5kIGJsa3RhcDIgZG9jdW1lbnRhdGlvbiBtb3N0bHkgY292ZXJzIFhlbidzIGNvbmZpZyAKPiBm aWxlIHN5bnRheCB0byB0byB1c2Ugd2l0aCBWSEQgc3RvcmFnZS4KPgo+IFRoZSBpZGVhIHRvIHRy ZWF0IHRoZSBWSEQgYXMgYSBibGFjayBib3ggaXMgbm90IGFwcGVhbGluZyBhdCBhbGwuIElzIAo+ IHRoZXJlIGEgcmVndWxhciB3YXkgdG8gYWNjZXNzIFZIRCBmcm9tIERvbTA/IFdoYXQncyB3cm9u ZyB3aXRoIG15IAo+IHZoZHBhcnR4LCBtYXliZSBpdCBpcyBzdXBwb3NlZCB0byB3b3JrIGluIGEg ZGlmZmVyZW50IHdheT8KPgo+Cj4gSSBoYXZlIGRvbmUgbXkgc2VhcmNoIGZvciBhbHRlcm5hdGl2 ZXMgYW5kIHRoZSBtb3N0IHByb21pc2luZyAKPiByZWZlcmVuY2UgSSd2ZSBmb3VuZCB3YXMgb25l IHRoYXQgc3VnZ2VzdHMgYXR0YWNoaW5nIHRoZSBWREkgKG9yIGl0J3MgCj4gc25hcHNob3QpIHRv IHRoZSBEb20wIHZpYSBhIG1hbnVhbGx5IGNyZWF0ZWQgVkJELCBqdXN0IGFzIGlmIGl0IHdhcyBh IAo+IHJlZ3VsYXIgVk0uCj4gaHR0cDovL2ZvcnVtcy5jaXRyaXguY29tL3RocmVhZC5qc3BhP3Ro cmVhZElEPTI1MjE0Mgo+IEl0J3MgcXVpdGUgb2xkLCBhbmQgSSBkaWQgbm90IGdldCB0aGF0IHNv bHV0aW9uIHdvcmsgZXRoZXI6IEkgY2FuIGRvIAo+IGFsbCB0aGUgc3RlcHMsIGJ1dCB0aGUgZGlz ayBuZXZlciBzaG93ZWQgdXAgd2l0aGluIERvbTAsIGV2ZW4gYWZ0ZXIgSSAKPiAidmJkLXBsdWci IGl0Lgo+Cj4KPiBUaGFuayB5b3UuCj4KCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5v cmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Sat Jan 05 07:33:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 07:33:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrOGH-00058i-E8; Sat, 05 Jan 2013 07:33:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrOGF-00058b-L4 for xen-api@lists.xen.org; Sat, 05 Jan 2013 07:33:43 +0000 Received: from [85.158.139.83:57681] by server-3.bemta-5.messagelabs.com id 3B/3A-25441-657D7E05; Sat, 05 Jan 2013 07:33:42 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1357371221!29604804!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30958 invoked from network); 5 Jan 2013 07:33:42 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-4.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Jan 2013 07:33:42 -0000 Received: from [189.180.173.53] (port=52280 helo=[10.1.0.145]) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TrOGC-0008C6-Ru for xen-api@lists.xen.org; Sat, 05 Jan 2013 01:33:40 -0600 Message-ID: <50E7D754.3020703@ondore.com> Date: Sat, 05 Jan 2013 01:33:40 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> In-Reply-To: <50E7B6C4.2010705@gmail.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: alk@ondore.com Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8uCgpFbCAwNC8wMS8xMyAyMzoxNCwgR2VvcmdlIFNodWtsaW4gZXNjcmliacOzOgo+IFVz ZSB4ZSB2YmQtY3JlYXRlIGJldHdlZW4gdmRpIGFuZCBkb20wICh3aGljaCBpcyBub3JtYWwgVk0g bW9zdGx5KSwgYW5kCj4geGUgdmJkLXBsdWcuClllcywgdGhhdCdzIHdoYXQgSSBoYXZlIGRvbmUg Zm9sbG93aW5nIHRoZSBleGFtcGxlIGZyb20gQ2l0cml4IGZvcnVtLgoKSW4gY2FzZSBvZiBhIG5v cm1hbCBEb21VOgpJIGNyZWF0ZSBWQkQgbGlua2luZyB0aGUgVk0gd2l0aCBWREksCkkgaXNzdWUg dmJkLXBsdWcsCnRoZSBibG9jayBkZXZpY2UgYmVjb21lcyB2aXNpYmxlIGluIGRtZXNnIHVuZGVy IERvbVUuCgpJbiBjYXNlIG9mIERvbTA6CkkgY3JlYXRlIFZCRCBsaW5raW5nIHRoZSBWTSAodm0t bGlzdCByZWZlcnMgdG8gaXQgYXMgIkNvbnRyb2wgRG9tYWluIiwgCm5vIG1pc3Rha2UpIHdpdGgg VkRJLApJIGlzc3VlIHZiZC1wbHVnLApubyBzaWduIG9mIHRoZSBuZXcgYmxvY2sgZGV2aWNlIGlu IGRtZXNnIG9yIHVuZGVyIC9kZXYuCgo+IFlvdSBjYW4gc2VlIHNvbWUgc2FtcGxlIHVzYWdlIGlu ICd4ZS1lZGl0LWJvb3Rsb2FkZXInIGNvbW1hbmQgKHNvbWV3aGVyZQo+IGluIC9vcHQveGVuc291 cmNlLykKSG0uIEkgYmVsaWV2ZSBJJ20gZG9pbmcgaXQganVzdCB0aGUgc2FtZSB3YXkgYXMgaW4g dGhlIHNjcmlwdCwgZXhjZXB0IGJ5IAp0aGUgImRldmljZT0iIGRpcmVjdGl2ZSBmb3IgdmJkLWNy ZWF0ZSwgdXNlIHNwZWNpZmljIHN0cmluZyBsaWtlICJ4dmRuIi4KU2hvdWxkIGl0IG1ha2UgdGhl IGRpZmZlcmVuY2U/IENhbid0IHRlc3QsIEkgc2hvdCBkb3duIG15IHRlc3RpbmcgcmFuZ2UgCmJl Zm9yZSBsZWF2aW5nIHRoZSBvZmZpY2UuCgpTbywgbXVzdCBJIHVuZGVyc3RhbmQgdGhhdCB0aGUg WENQJ3MgcmVndWxhciB3YXkgb2YgbWFuaXB1bGF0aW5nIFZESSdzIApjb250ZW50cyBmcm9tIHdp dGhpbiBEb20wLCBpcyBhdHRhY2hpbmcgdGhlIFZESSB0byBpdCB2aWEgYSBWQkQ/Ckxvb2tzIGxp a2UgYSBnb29kIGFic3RyYWN0aW9uLCBleGNlcHQgdGhhdCBpdCB3b24ndCB3b3JrIHRoYXQgZWFz aWx5IG9uIAphIGhvc3Qgd2l0aG91dCBYQ1AgaW5mcmFzdHJ1Y3R1cmUgKGZvciBleGFtcGxlLCBp biBzb21lIHJlc2N1ZSBzY2VuYXJpbykuCgpUaGVuLCB3aGF0IHZoZHBhcnR4IGlzIGdvb2QgZm9y PwoKQ2hlZXJzLgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlz dHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Sat Jan 05 07:33:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 07:33:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrOGH-00058i-E8; Sat, 05 Jan 2013 07:33:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrOGF-00058b-L4 for xen-api@lists.xen.org; Sat, 05 Jan 2013 07:33:43 +0000 Received: from [85.158.139.83:57681] by server-3.bemta-5.messagelabs.com id 3B/3A-25441-657D7E05; Sat, 05 Jan 2013 07:33:42 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1357371221!29604804!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30958 invoked from network); 5 Jan 2013 07:33:42 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-4.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Jan 2013 07:33:42 -0000 Received: from [189.180.173.53] (port=52280 helo=[10.1.0.145]) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TrOGC-0008C6-Ru for xen-api@lists.xen.org; Sat, 05 Jan 2013 01:33:40 -0600 Message-ID: <50E7D754.3020703@ondore.com> Date: Sat, 05 Jan 2013 01:33:40 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> In-Reply-To: <50E7B6C4.2010705@gmail.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: alk@ondore.com Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8uCgpFbCAwNC8wMS8xMyAyMzoxNCwgR2VvcmdlIFNodWtsaW4gZXNjcmliacOzOgo+IFVz ZSB4ZSB2YmQtY3JlYXRlIGJldHdlZW4gdmRpIGFuZCBkb20wICh3aGljaCBpcyBub3JtYWwgVk0g bW9zdGx5KSwgYW5kCj4geGUgdmJkLXBsdWcuClllcywgdGhhdCdzIHdoYXQgSSBoYXZlIGRvbmUg Zm9sbG93aW5nIHRoZSBleGFtcGxlIGZyb20gQ2l0cml4IGZvcnVtLgoKSW4gY2FzZSBvZiBhIG5v cm1hbCBEb21VOgpJIGNyZWF0ZSBWQkQgbGlua2luZyB0aGUgVk0gd2l0aCBWREksCkkgaXNzdWUg dmJkLXBsdWcsCnRoZSBibG9jayBkZXZpY2UgYmVjb21lcyB2aXNpYmxlIGluIGRtZXNnIHVuZGVy IERvbVUuCgpJbiBjYXNlIG9mIERvbTA6CkkgY3JlYXRlIFZCRCBsaW5raW5nIHRoZSBWTSAodm0t bGlzdCByZWZlcnMgdG8gaXQgYXMgIkNvbnRyb2wgRG9tYWluIiwgCm5vIG1pc3Rha2UpIHdpdGgg VkRJLApJIGlzc3VlIHZiZC1wbHVnLApubyBzaWduIG9mIHRoZSBuZXcgYmxvY2sgZGV2aWNlIGlu IGRtZXNnIG9yIHVuZGVyIC9kZXYuCgo+IFlvdSBjYW4gc2VlIHNvbWUgc2FtcGxlIHVzYWdlIGlu ICd4ZS1lZGl0LWJvb3Rsb2FkZXInIGNvbW1hbmQgKHNvbWV3aGVyZQo+IGluIC9vcHQveGVuc291 cmNlLykKSG0uIEkgYmVsaWV2ZSBJJ20gZG9pbmcgaXQganVzdCB0aGUgc2FtZSB3YXkgYXMgaW4g dGhlIHNjcmlwdCwgZXhjZXB0IGJ5IAp0aGUgImRldmljZT0iIGRpcmVjdGl2ZSBmb3IgdmJkLWNy ZWF0ZSwgdXNlIHNwZWNpZmljIHN0cmluZyBsaWtlICJ4dmRuIi4KU2hvdWxkIGl0IG1ha2UgdGhl IGRpZmZlcmVuY2U/IENhbid0IHRlc3QsIEkgc2hvdCBkb3duIG15IHRlc3RpbmcgcmFuZ2UgCmJl Zm9yZSBsZWF2aW5nIHRoZSBvZmZpY2UuCgpTbywgbXVzdCBJIHVuZGVyc3RhbmQgdGhhdCB0aGUg WENQJ3MgcmVndWxhciB3YXkgb2YgbWFuaXB1bGF0aW5nIFZESSdzIApjb250ZW50cyBmcm9tIHdp dGhpbiBEb20wLCBpcyBhdHRhY2hpbmcgdGhlIFZESSB0byBpdCB2aWEgYSBWQkQ/Ckxvb2tzIGxp a2UgYSBnb29kIGFic3RyYWN0aW9uLCBleGNlcHQgdGhhdCBpdCB3b24ndCB3b3JrIHRoYXQgZWFz aWx5IG9uIAphIGhvc3Qgd2l0aG91dCBYQ1AgaW5mcmFzdHJ1Y3R1cmUgKGZvciBleGFtcGxlLCBp biBzb21lIHJlc2N1ZSBzY2VuYXJpbykuCgpUaGVuLCB3aGF0IHZoZHBhcnR4IGlzIGdvb2QgZm9y PwoKQ2hlZXJzLgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlz dHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Sat Jan 05 16:47:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 16:47:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrWtU-0004L1-0q; Sat, 05 Jan 2013 16:46:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrWtR-0004Kw-JE for xen-api@lists.xen.org; Sat, 05 Jan 2013 16:46:45 +0000 Received: from [85.158.139.83:27702] by server-1.bemta-5.messagelabs.com id 26/B5-12813-4F858E05; Sat, 05 Jan 2013 16:46:44 +0000 X-Env-Sender: juan@jelsupport.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1357404401!32409509!1 X-Originating-IP: [216.27.216.109] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7420 invoked from network); 5 Jan 2013 16:46:42 -0000 Received: from 109.216.27.216.static.ip.tnltd.net (HELO MAZER.sbs.local) (216.27.216.109) by server-3.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 5 Jan 2013 16:46:42 -0000 Received: from MAZER.sbs.local ([fe80::9538:f5d5:8163:90a8]) by MAZER.sbs.local ([fe80::9538:f5d5:8163:90a8%10]) with mapi; Sat, 5 Jan 2013 08:46:39 -0800 From: Juan Lorenzana To: "xen-api@lists.xen.org" Date: Sat, 5 Jan 2013 08:46:37 -0800 Thread-Topic: Best Upgrade otions for 1.5 XCP to 1.6 XCP Thread-Index: Ac3rYgNRBHNklJmnQtyDra2GkAKDoA== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] Best Upgrade otions for 1.5 XCP to 1.6 XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3548483126655169887==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3548483126655169887== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF66999MAZERsbslocal_" --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF66999MAZERsbslocal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Okay, I know this sounds silly but I have been doing some research on how t= o best upgrade from 1.5 XCP to 1.6 XCP. Some folks are using the Rolling P= ool Upgrade Wizard in Xen Center had some issues, but nothing too scary her= e. Since I only have a handful of VMs running on two physical servers (bot= h of which are in the same pool and both using NFS based storage repositori= es), I wanted to get another opinion on how to best migrate to 1.6. Here are my thoughts: Use the Rolling Pool Upgrade Wizard Pros: Should work with very little work on my part Cons: I am not sure how it works. Basically do I want to consider another = options for DR purposes ( I will explain about this in a minute ). Use the XCP 1.6 ISO to install 1.6 on each server Pros: I will have a known image ISO image to work from in case of DR scenar= io Cons: Not sure if this will work the way I want it to, but I believe that a= s long as I save the XCP metadata and the VM images on the shared storage, = this should work. So why I am concerned about a DR scenario. Because a few months ago we fou= nd ourselves in this situation when our HA storage solution failed. After = 36 hours of down town and some very angry customers, I am looking for an up= grade process that in a DR scenario I will be able to quickly get back up. = So my thoughts are that if I can take the XCP 1.6 ISO and put in a server,= given that all the other prerequisites are taken care of like processor ty= pes, etc..., then I should feel comfortable recovering a failed server. In= theory, if I use an XCP 1.6 ISO on all the servers, I have an easily repro= ducible DR process. Box fails, put new box in, use ISO, attach to Pool, then start up VMs. If = I use the Rolling Pool Upgrade Wizard, I am a little hesitant to say that i= f the box fails, will a brand new server with the XCP 1.6 ISO be setup the = same or close enough to work. Obviously, I cannot join a 1.6 server to my 1.5 Pool. What I am not sure a= bout is what is the best way to upgrade from 1.5 to 1.6, and which way carr= ies the easiest DR process in the future. What I do not want is conflicts = with the kernel and vice versa by doing a Rolling Pool Upgrade versus a fre= sh install. Even if I do load 1.6 on one of the servers, I am not sure that I could tra= nsition the Pool master to it and I am not sure that doing it this way is a= dvisable. Does anyone have some thoughts here???? Juan --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF66999MAZERsbslocal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Okay, I know thi= s sounds silly but I have been doing some research on how to best upgrade f= rom 1.5 XCP to 1.6 XCP.  Some folks are using the Rolling Pool Upgrade= Wizard in Xen Center had some issues, but nothing too scary here.  Si= nce I only have a handful of VMs running on two physical servers (both of w= hich are in the same pool and both using NFS based storage repositories), I= wanted to get another opinion on how to best migrate to 1.6.

 

Here are my= thoughts:

 

Use the Rolling Pool Upgrade Wizard

Pros: Should work with very little work on my part

<= p class=3DMsoNormal>Cons: I am not sure how it works.  Basically do I = want to consider another options for DR purposes ( I will explain about thi= s in a minute ).

 

Use the XCP 1.6 ISO to install 1.6 on each server

Pros: I will have a known image ISO image to w= ork from in case of DR scenario

Cons: No= t sure if this will work the way I want it to, but I believe that as long a= s I save the XCP metadata and the VM images on the shared storage, this sho= uld work.

 

So why I am concerned about a DR scenario.  Because a few= months ago we found ourselves in this situation when our HA storage soluti= on failed.  After 36 hours of down town and some very angry customers,= I am looking for an upgrade process that in a DR scenario I will be able t= o quickly get back up.  So my thoughts are that if I can take the XCP = 1.6 ISO and put in a server, given that all the other prerequisites are tak= en care of like processor types, etc…, then I should feel comfortable= recovering a failed server.  In theory, if I use an XCP 1.6 ISO on al= l the servers, I have an easily reproducible DR process.

 

Box fails, put n= ew box in, use ISO, attach to Pool, then start up VMs.  If I use the R= olling Pool Upgrade Wizard, I am a little hesitant to say that if the box f= ails, will a brand new server with the XCP 1.6 ISO be setup the same or clo= se enough to work.

 

=

Obviously, I cannot join a 1.6 server to my 1.5 Pool.&= nbsp; What I am not sure about is what is the best way to upgrade from 1.5 = to 1.6, and which way carries the easiest DR process in the future.  W= hat I do not want is conflicts with the kernel and vice versa by doing a Ro= lling Pool Upgrade versus a fresh install. 

 

Even if I do load 1.6 o= n one of the servers, I am not sure that I could transition the Pool master= to it and I am not sure that doing it this way is advisable.

 

Does anyone= have some thoughts here????

 =

 

Ju= an

 

 

= --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF66999MAZERsbslocal_-- --===============3548483126655169887== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3548483126655169887==-- From xen-api-bounces@lists.xen.org Sat Jan 05 16:47:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 05 Jan 2013 16:47:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrWtU-0004L1-0q; Sat, 05 Jan 2013 16:46:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrWtR-0004Kw-JE for xen-api@lists.xen.org; Sat, 05 Jan 2013 16:46:45 +0000 Received: from [85.158.139.83:27702] by server-1.bemta-5.messagelabs.com id 26/B5-12813-4F858E05; Sat, 05 Jan 2013 16:46:44 +0000 X-Env-Sender: juan@jelsupport.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1357404401!32409509!1 X-Originating-IP: [216.27.216.109] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7420 invoked from network); 5 Jan 2013 16:46:42 -0000 Received: from 109.216.27.216.static.ip.tnltd.net (HELO MAZER.sbs.local) (216.27.216.109) by server-3.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 5 Jan 2013 16:46:42 -0000 Received: from MAZER.sbs.local ([fe80::9538:f5d5:8163:90a8]) by MAZER.sbs.local ([fe80::9538:f5d5:8163:90a8%10]) with mapi; Sat, 5 Jan 2013 08:46:39 -0800 From: Juan Lorenzana To: "xen-api@lists.xen.org" Date: Sat, 5 Jan 2013 08:46:37 -0800 Thread-Topic: Best Upgrade otions for 1.5 XCP to 1.6 XCP Thread-Index: Ac3rYgNRBHNklJmnQtyDra2GkAKDoA== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] Best Upgrade otions for 1.5 XCP to 1.6 XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3548483126655169887==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3548483126655169887== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF66999MAZERsbslocal_" --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF66999MAZERsbslocal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Okay, I know this sounds silly but I have been doing some research on how t= o best upgrade from 1.5 XCP to 1.6 XCP. Some folks are using the Rolling P= ool Upgrade Wizard in Xen Center had some issues, but nothing too scary her= e. Since I only have a handful of VMs running on two physical servers (bot= h of which are in the same pool and both using NFS based storage repositori= es), I wanted to get another opinion on how to best migrate to 1.6. Here are my thoughts: Use the Rolling Pool Upgrade Wizard Pros: Should work with very little work on my part Cons: I am not sure how it works. Basically do I want to consider another = options for DR purposes ( I will explain about this in a minute ). Use the XCP 1.6 ISO to install 1.6 on each server Pros: I will have a known image ISO image to work from in case of DR scenar= io Cons: Not sure if this will work the way I want it to, but I believe that a= s long as I save the XCP metadata and the VM images on the shared storage, = this should work. So why I am concerned about a DR scenario. Because a few months ago we fou= nd ourselves in this situation when our HA storage solution failed. After = 36 hours of down town and some very angry customers, I am looking for an up= grade process that in a DR scenario I will be able to quickly get back up. = So my thoughts are that if I can take the XCP 1.6 ISO and put in a server,= given that all the other prerequisites are taken care of like processor ty= pes, etc..., then I should feel comfortable recovering a failed server. In= theory, if I use an XCP 1.6 ISO on all the servers, I have an easily repro= ducible DR process. Box fails, put new box in, use ISO, attach to Pool, then start up VMs. If = I use the Rolling Pool Upgrade Wizard, I am a little hesitant to say that i= f the box fails, will a brand new server with the XCP 1.6 ISO be setup the = same or close enough to work. Obviously, I cannot join a 1.6 server to my 1.5 Pool. What I am not sure a= bout is what is the best way to upgrade from 1.5 to 1.6, and which way carr= ies the easiest DR process in the future. What I do not want is conflicts = with the kernel and vice versa by doing a Rolling Pool Upgrade versus a fre= sh install. Even if I do load 1.6 on one of the servers, I am not sure that I could tra= nsition the Pool master to it and I am not sure that doing it this way is a= dvisable. Does anyone have some thoughts here???? Juan --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF66999MAZERsbslocal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Okay, I know thi= s sounds silly but I have been doing some research on how to best upgrade f= rom 1.5 XCP to 1.6 XCP.  Some folks are using the Rolling Pool Upgrade= Wizard in Xen Center had some issues, but nothing too scary here.  Si= nce I only have a handful of VMs running on two physical servers (both of w= hich are in the same pool and both using NFS based storage repositories), I= wanted to get another opinion on how to best migrate to 1.6.

 

Here are my= thoughts:

 

Use the Rolling Pool Upgrade Wizard

Pros: Should work with very little work on my part

<= p class=3DMsoNormal>Cons: I am not sure how it works.  Basically do I = want to consider another options for DR purposes ( I will explain about thi= s in a minute ).

 

Use the XCP 1.6 ISO to install 1.6 on each server

Pros: I will have a known image ISO image to w= ork from in case of DR scenario

Cons: No= t sure if this will work the way I want it to, but I believe that as long a= s I save the XCP metadata and the VM images on the shared storage, this sho= uld work.

 

So why I am concerned about a DR scenario.  Because a few= months ago we found ourselves in this situation when our HA storage soluti= on failed.  After 36 hours of down town and some very angry customers,= I am looking for an upgrade process that in a DR scenario I will be able t= o quickly get back up.  So my thoughts are that if I can take the XCP = 1.6 ISO and put in a server, given that all the other prerequisites are tak= en care of like processor types, etc…, then I should feel comfortable= recovering a failed server.  In theory, if I use an XCP 1.6 ISO on al= l the servers, I have an easily reproducible DR process.

 

Box fails, put n= ew box in, use ISO, attach to Pool, then start up VMs.  If I use the R= olling Pool Upgrade Wizard, I am a little hesitant to say that if the box f= ails, will a brand new server with the XCP 1.6 ISO be setup the same or clo= se enough to work.

 

=

Obviously, I cannot join a 1.6 server to my 1.5 Pool.&= nbsp; What I am not sure about is what is the best way to upgrade from 1.5 = to 1.6, and which way carries the easiest DR process in the future.  W= hat I do not want is conflicts with the kernel and vice versa by doing a Ro= lling Pool Upgrade versus a fresh install. 

 

Even if I do load 1.6 o= n one of the servers, I am not sure that I could transition the Pool master= to it and I am not sure that doing it this way is advisable.

 

Does anyone= have some thoughts here????

 =

 

Ju= an

 

 

= --_000_B8EDCEBF5C34F3428BFC41D3253290A5341FF66999MAZERsbslocal_-- --===============3548483126655169887== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3548483126655169887==-- From xen-api-bounces@lists.xen.org Mon Jan 07 08:35:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 08:35:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ts8Ax-0002J1-Oe; Mon, 07 Jan 2013 08:35:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ts8Aw-0002Iw-0u for xen-api@lists.xensource.com; Mon, 07 Jan 2013 08:35:18 +0000 Received: from [85.158.138.51:7379] by server-9.bemta-3.messagelabs.com id 2A/B6-11948-5C88AE05; Mon, 07 Jan 2013 08:35:17 +0000 X-Env-Sender: koldo.aingeru@sarenet.es X-Msg-Ref: server-12.tower-174.messagelabs.com!1357547712!19779060!1 X-Originating-IP: [194.30.0.251] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22438 invoked from network); 7 Jan 2013 08:35:12 -0000 Received: from proxypop03b.sare.net (HELO proxypop03b.sare.net) (194.30.0.251) by server-12.tower-174.messagelabs.com with SMTP; 7 Jan 2013 08:35:12 -0000 Received: from [172.16.2.53] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id B39B19DD262; Mon, 7 Jan 2013 09:35:07 +0100 (CET) From: =?iso-8859-1?Q?Koldo_Aingeru_Marcos_Fern=E1ndez?= Mime-Version: 1.0 (Apple Message framework v1084) Date: Mon, 7 Jan 2013 09:35:11 +0100 In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E5B3634@LONPMAILBOX01.citrite.net> To: James Bulpin , xen-api@lists.xensource.com References: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> <344C0F67BC927847A2C92F9EE358DB0E01224E5B3634@LONPMAILBOX01.citrite.net> Message-Id: X-Mailer: Apple Mail (2.1084) Subject: Re: [Xen-API] Xen API connection with python and xml-rpc int limit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2604532665588573069==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2604532665588573069== Content-Type: multipart/alternative; boundary=Apple-Mail-21--864094016 --Apple-Mail-21--864094016 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hello,=20 that did the trick, thanks! El 02/01/2013, a las 11:27, James Bulpin escribi=F3: > Try converting the value to a string and using this as the second = argument to VM.set_memory_static_max etc. > =20 > Cheers, > James > =20 > From: xen-api-bounces@lists.xen.org = [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Koldo Aingeru Marcos = Fern=E1ndez > Sent: 28 December 2012 10:09 > To: xen-api@lists.xensource.com > Subject: [Xen-API] Xen API connection with python and xml-rpc int = limit > =20 > Hello all, > =20 > I'm trying to change the memory limits using the python implementation = of the xenapi and I'm having trouble because the value in the api is a = 64bit int and the xml-rpc specifies ints as 32 bit. So I'm getting this = error (both in MacOSX and CentOS): > =20 > File = "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xm= lrpclib.py", line 710, in dump_int > raise OverflowError, "int exceeds XML-RPC limits" > OverflowError: int exceeds XML-RPC limits > =20 > And this is the code in xmlrpclib.py: > =20 > def dump_int(self, value, write): > # in case ints are > 32 bits > if value > MAXINT or value < MININT: > raise OverflowError, "int exceeds XML-RPC limits" > =20 > =20 > Is there any workaround for this? I would like to avoid both doing a = ssh connection to the host or modifying xmlrpclib.py. > =20 > Thanks! > =20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Koldo Aingeru Marcos Fdez.=20 > Sarenet S.A. > Tel: 944209470 - Fax: 944209465 > Parque Tecnol=F3gico, Edificio 103 > 48170 Zamudio > Bizkaia > www.sarenet.es > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 >=20 > =20 >=20 > =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Koldo Aingeru Marcos Fdez.=20 Sarenet S.A. Tel: 944209470 - Fax: 944209465 Parque Tecnol=F3gico, Edificio 103 48170 Zamudio Bizkaia www.sarenet.es =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --Apple-Mail-21--864094016 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hello, 

that did the trick, = thanks!


El 02/01/2013, a las = 11:27, James Bulpin escribi=F3:

Try = converting the value to a string and using this as the second argument = to VM.set_memory_static_max etc.
 xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists= .xen.org] On Behalf = Of Koldo Aingeru = Marcos Fern=E1ndez
Sent: 28 December 2012 = 10:09
To:  [Xen-API] Xen API = connection with python and xml-rpc int = limit
= --Apple-Mail-21--864094016-- --===============2604532665588573069== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2604532665588573069==-- From xen-api-bounces@lists.xen.org Mon Jan 07 08:35:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 08:35:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ts8Ax-0002J1-Oe; Mon, 07 Jan 2013 08:35:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ts8Aw-0002Iw-0u for xen-api@lists.xensource.com; Mon, 07 Jan 2013 08:35:18 +0000 Received: from [85.158.138.51:7379] by server-9.bemta-3.messagelabs.com id 2A/B6-11948-5C88AE05; Mon, 07 Jan 2013 08:35:17 +0000 X-Env-Sender: koldo.aingeru@sarenet.es X-Msg-Ref: server-12.tower-174.messagelabs.com!1357547712!19779060!1 X-Originating-IP: [194.30.0.251] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22438 invoked from network); 7 Jan 2013 08:35:12 -0000 Received: from proxypop03b.sare.net (HELO proxypop03b.sare.net) (194.30.0.251) by server-12.tower-174.messagelabs.com with SMTP; 7 Jan 2013 08:35:12 -0000 Received: from [172.16.2.53] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id B39B19DD262; Mon, 7 Jan 2013 09:35:07 +0100 (CET) From: =?iso-8859-1?Q?Koldo_Aingeru_Marcos_Fern=E1ndez?= Mime-Version: 1.0 (Apple Message framework v1084) Date: Mon, 7 Jan 2013 09:35:11 +0100 In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E5B3634@LONPMAILBOX01.citrite.net> To: James Bulpin , xen-api@lists.xensource.com References: <87C28AE5-0A99-48E9-A292-8200D558ECEC@sarenet.es> <344C0F67BC927847A2C92F9EE358DB0E01224E5B3634@LONPMAILBOX01.citrite.net> Message-Id: X-Mailer: Apple Mail (2.1084) Subject: Re: [Xen-API] Xen API connection with python and xml-rpc int limit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2604532665588573069==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2604532665588573069== Content-Type: multipart/alternative; boundary=Apple-Mail-21--864094016 --Apple-Mail-21--864094016 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hello,=20 that did the trick, thanks! El 02/01/2013, a las 11:27, James Bulpin escribi=F3: > Try converting the value to a string and using this as the second = argument to VM.set_memory_static_max etc. > =20 > Cheers, > James > =20 > From: xen-api-bounces@lists.xen.org = [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Koldo Aingeru Marcos = Fern=E1ndez > Sent: 28 December 2012 10:09 > To: xen-api@lists.xensource.com > Subject: [Xen-API] Xen API connection with python and xml-rpc int = limit > =20 > Hello all, > =20 > I'm trying to change the memory limits using the python implementation = of the xenapi and I'm having trouble because the value in the api is a = 64bit int and the xml-rpc specifies ints as 32 bit. So I'm getting this = error (both in MacOSX and CentOS): > =20 > File = "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xm= lrpclib.py", line 710, in dump_int > raise OverflowError, "int exceeds XML-RPC limits" > OverflowError: int exceeds XML-RPC limits > =20 > And this is the code in xmlrpclib.py: > =20 > def dump_int(self, value, write): > # in case ints are > 32 bits > if value > MAXINT or value < MININT: > raise OverflowError, "int exceeds XML-RPC limits" > =20 > =20 > Is there any workaround for this? I would like to avoid both doing a = ssh connection to the host or modifying xmlrpclib.py. > =20 > Thanks! > =20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Koldo Aingeru Marcos Fdez.=20 > Sarenet S.A. > Tel: 944209470 - Fax: 944209465 > Parque Tecnol=F3gico, Edificio 103 > 48170 Zamudio > Bizkaia > www.sarenet.es > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 >=20 > =20 >=20 > =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Koldo Aingeru Marcos Fdez.=20 Sarenet S.A. Tel: 944209470 - Fax: 944209465 Parque Tecnol=F3gico, Edificio 103 48170 Zamudio Bizkaia www.sarenet.es =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --Apple-Mail-21--864094016 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hello, 

that did the trick, = thanks!


El 02/01/2013, a las = 11:27, James Bulpin escribi=F3:

Try = converting the value to a string and using this as the second argument = to VM.set_memory_static_max etc.
 xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists= .xen.org] On Behalf = Of Koldo Aingeru = Marcos Fern=E1ndez
Sent: 28 December 2012 = 10:09
To:  [Xen-API] Xen API = connection with python and xml-rpc int = limit
= --Apple-Mail-21--864094016-- --===============2604532665588573069== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2604532665588573069==-- From xen-api-bounces@lists.xen.org Mon Jan 07 12:30:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 12:30:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsBq0-0001yy-1l; Mon, 07 Jan 2013 12:29:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsBpy-0001yq-3d for xen-api@lists.xen.org; Mon, 07 Jan 2013 12:29:54 +0000 Received: from [85.158.143.35:64804] by server-2.bemta-4.messagelabs.com id 8C/00-24322-1CFBAE05; Mon, 07 Jan 2013 12:29:53 +0000 X-Env-Sender: blackbird1758@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1357561765!13912525!1 X-Originating-IP: [209.85.216.171] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26001 invoked from network); 7 Jan 2013 12:29:27 -0000 Received: from mail-qc0-f171.google.com (HELO mail-qc0-f171.google.com) (209.85.216.171) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2013 12:29:27 -0000 Received: by mail-qc0-f171.google.com with SMTP id d1so12075580qca.2 for ; Mon, 07 Jan 2013 04:28:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Et62acBI6ctdigBEOm1YmPX+wlyynpXbbd/SJa2G6ns=; b=tEIM8VTZJ5vi12+fHlVWHy8fTeWXyWLpCUkxrWjmIQb6tN9wmxD5BbmdSazbowq01E 3bWexElx4HJgwqzyCya1kNJ0H1QgDuo/eKTrrLGykn8QQQwBk18mhjCQk4IzKj6QakFB xrSxwcyInGhQZd7VaCSPxV00j2mTVK6x6jBhGGvXmPfo56p+n6tvqG5AJKkVAgTevYDS V/QdQM0r/dZO76Oic6m9c5fSZKfGGxpVvF5UYOsTVvUSm0vioOSTMgaRxkyJcgY3LDEG 09LbYPa4Wb/LhsBME5qJzAtJVSbGMDeZLKRHW/TWH1MI9Ru9hK/UcJJySR39mQBXiXX3 YiiA== MIME-Version: 1.0 Received: by 10.224.185.148 with SMTP id co20mr4980531qab.94.1357561706537; Mon, 07 Jan 2013 04:28:26 -0800 (PST) Received: by 10.49.11.208 with HTTP; Mon, 7 Jan 2013 04:28:26 -0800 (PST) In-Reply-To: References: <50B7366B.60509@gmail.com> <50B7EC0F.7020008@gmail.com> Date: Mon, 7 Jan 2013 23:28:26 +1100 Message-ID: From: Black Bird To: George Shuklin Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 Beta: upgrade of RAID 1 installation X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1639049380060407142==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1639049380060407142== Content-Type: multipart/alternative; boundary=485b397dd69747623e04d2b1f7f0 --485b397dd69747623e04d2b1f7f0 Content-Type: text/plain; charset=ISO-8859-1 I'd like to report some progress here on the networking issues that stopped me. I modified my approach in two ways. a) for the new slave, instead of the management network starting on one of the NICs of the future bond, I used eth0 which is unbonded in its final configuration. This avoided loosing connectivity upon joining the pool. The management network can be moved later. b) I stated above that 'the bonds are created but are connected to the wrong xapi network'. I now look at it the other way round, i.e. that the xapi network is fine and the joining process creates bonds whose numbering on the slave may be different from the numbering on the master. On reading the Citrix documentation that the network configuration on the master is replicated on the slave on joining the pool, I now understand that this is not strictly applicable for the bond device id. What muddled the issues in my case was that I was using the bond device id (bondx) also as the network label to which the bond pif was attached. As soon as I accepted that bond device ids may be different on different hosts in the pool, even if they correspond to the same pair of NICs, then the situation was clarified. In my case, the situation is now: NIC master slave xapi ------------------------------------------- eth0 no bond no bond eth 1/2 bond 0 bond 2 xapi3 eth 3/4 bond 1 bond 0 xapi9 eth 5/6 bond 2 bond 1 xapi11 The slave can fully participate in the pool as far as I can determine. Unfortunately I cannot go back to the original topic as the slave on the old version was ejected or forgotten from the pool at some stage. I apologise for the off-topic diversion. On Wed, Dec 19, 2012 at 4:42 PM, Black Bird wrote: > I haven't updated this thread for a while, although I've been busy moving > from one problem to the next. > > a) the problem I reported above, needs some clarification. The upgrade of > 1.6Beta2 to 1.6final had worked on an MBR partitioned master on a cleanly > installed host. > > However the same upgrade on a 1.6Beta2 GPT partitioned master had failed > on a host which had been de-mirrored (using filesystem copy from mirrored > to a non mirrored disk). Although the non-mirrored host was bootable and > completely functional, the 1.6Final installer failed to recognise an > existing installation. I realised that the same situation existed when a > mirrored host is moved to a non-mirrored MBR partitioned master, (bootable, > fully functional, and not seen by the installer). > > b) I was able to do a normal clean installation of 1.6Beta2 on an > unmirrored host, do an xe-pool-restore-database, and then upgrade to > 1.6Final. This is appropriate on the master, but not on slaves. The host > can then be re-converted to mirrored configuration. > > c) on the slaves, xe-pool-restore-database is not appropriate as > discussed. As mentioned above, the installer is unable to recognise a > working de-mirrored installation. So I reverted to the process outlined by > George previously. > > I did a clean installation of 1.6Beta2 on a single disk. I entered into > single user mode, set the ethernet devices manually using > /etc/sysconfig/network-scripts/interface-rename-data/static-rules.conf, > copied across /etc/xensource* and /var/xapi from the mirrored disks and > rebooted. This was a checkpoint which was intended to verify a de-mirrored > slave prior to a subsequent upgrade. Unfortunately, as the slave boots up, > it looses connectivity with the master. I repeated this process (i.e. new > installation, copy config files across and reboot) a number of times to try > and find a pattern, but on occasion some network cards did not come up, or > xapi complained about not reaching the master. I've been trying different > combinations of this process, trying to force the network interface names > before and after installation, to no avail. > > At one stage, in desperation I reset the network with xe-reset-networking, > but then the slave joined the pool with completely wrong eth values and > bonded interfaces. I've been unable to resolve this. > > Giving up on this approach, I've also tried to add a new slave to the > pool, intending to get a fresh host to which I can subsequently add the > local storage. To my disappointment, the network configuration on the new > host also does not reflect the one expected. I had expected the network > configuration of the master > eth0 no bond > eth 1/2 bond 0 > eth 3/4 bond 1 > eth 5/6 bond 2 > to be reflected in the slave. However what has happened is that on > joining the pool, the bonds are created but are connected to the wrong xapi > network. > > At this stage I have no way forward. For me the main point of having a > pool is to share configuration detail between hosts and automate the > installation process when a new slave enters the pool (there are other > advantages too), adopting things like common network configuration, common > storage networking etc. If this process is not reliable then I question > the validity of having a pool. At this stage I'm considering reverting to > single host masters and doing additional configuration manually or using an > external cloud orchestration facility such as OpenStack. > > > On Mon, Dec 3, 2012 at 2:01 PM, Black Bird wrote: > >> Hmmm. I've managed to upgrade from 1.6Beta2 to 1.6Final from an >> MBR-partitioned master, but not a GPT-partitioned master. In the latter >> case, the installer does not recognise an existing installation and >> proceeds to ask for a root password, at which stage I stop. >> >> Should a GPT-partitioned master be able to be recognised and upgraded? >> >> >> On Fri, Nov 30, 2012 at 3:07 PM, Black Bird wrote: >> >>> I have thought of possibly a better procedure (albeit still a >>> workaround) than the one I proposed in the first email. >>> >>> (a) make a pool-dump-database and store safely >>> (b) extract one hard disk and store as a recovery strategy >>> (exist_device2), leaving the other (exist_device1) >>> (c) create 2 new partitions on a separate temporary device >>> (temp_device), same sized as those live >>> (d) copy the contents of the existing two partitions (currently /dev/md0 >>> and /dev/md1). (Incidentally, I think it's of no use to mirror the 2nd >>> partition, as it is only used during installation as a backup, which is >>> only able to use raw partitions, but this is a separate story) >>> (e) reboot, >>> (f) enter the BIOS screen and configure temp_device as the default boot >>> device >>> (g) continue with boot and confirm that XCP host is working as normal >>> (h) insert the upgrade ISO media (CD/USB) >>> (i) reboot >>> (j) enter the BIOS screen and configure device containing the ISO media >>> as the default boot device >>> (k) during the installer stage, select temp_device. >>> (l) The installer should now recognise an existing installation, and any >>> backups. Proceed with upgrade as normal >>> (m) reboot at end, removing installer media >>> (n) enter the BIOS screen and configure temp_device as the default boot >>> device >>> (o) on bootup, xsconsole will show that the local SR is unavailable. >>> Some more steps are needed just to re-set up the md device for local >>> storage. The SR configuration should still be there. If no local SR >>> exists, then skip to (t) >>> (p) mdadm --examine --brief --scan --config=partitions >> >>> /etc/mdadm.conf (this will restore the mdadm configuration, from the md >>> metadata on the partitions in exist_device1 >>> (q) mdadm --assemble /dev/md2 (restart the md device containing the LVM >>> volumes used by the local SR) >>> (r) xe pbd-plug (attach the storage to the SR) >>> (s) at this stage you should be able to test that any VMs needing VDIs >>> on the local SR can be started >>> (t) copy the contents of the filesystems on the temp_device back onto >>> /dev/md0 and /dev/md1 >>> (u) reboot while removing temp_device (or rather shutdown, remove >>> temp_device, start host) >>> (v) in BIOS screen configure exist_device1 as the boot device >>> (w) verify that XCP host is running normally >>> (x) insert 2nd disk exist_device2 >>> (z) mdadm /dev/md --re-add /dev/ >>> >>> This procedure avoids a completely new installation, while retaining a >>> fallback. It should also work for a slave. >>> >>> So far I've tested parts of the above, but not as a complete procedure. >>> That's my next step. I'll keep you posted. >>> >>> >>> >>> On Fri, Nov 30, 2012 at 10:13 AM, George Shuklin < >>> george.shuklin@gmail.com> wrote: >>> >>>> >>>> I'd also love to see at least some procedure taking such installations >>>>> as a consideration, as we're also using XCP/XS on software RAID1, and every >>>>> upgrade is in fact a reinstallation, very suboptimal procedure. Perhaps, >>>>> given the fact XCP doesnt have to be tied to 'supported configuration' as >>>>> XS does, we could have mdraid support in XCP for >>>>> installation/reinstallation since so many people use it? >>>>> >>>>> Well, I've gladly do this, but main problem is opensource part. >>>> xen-api is pure opensource and source is available on github. >>>> >>>> XCP/XenServer installer is not. I mean, there is no published way to do >>>> something like 'make xcp-iso' command. Internals of installer is >>>> half-python, but no any information about xen-api expectation about files >>>> placement in older installation or proper way to do stuff. We internally >>>> simply hack original installer ISO to help us with installation procedure >>>> over md raid1. It looks kinda ugly and definitively not for 'public'. And I >>>> really wants to create it properly... >>>> >>>> >>>> >>>> ______________________________**_________________ >>>> Xen-api mailing list >>>> Xen-api@lists.xen.org >>>> http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api >>>> >>> >>> >> > --485b397dd69747623e04d2b1f7f0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I'd like to report some progress here on the networkin= g issues that stopped me. =A0I modified my approach in two ways.

a) for the new slave, instead of the management network starting o= n one of the NICs of the future bond, I used eth0 which is unbonded in its = final configuration. =A0This avoided loosing connectivity upon joining the = pool. =A0The management network can be moved later.

b) I stated above that 'the bonds are created but a= re connected to the wrong xapi network'. =A0I now look at it the other = way round, i.e. that the xapi network is fine and the joining process creat= es bonds whose numbering on the slave may be different from the numbering o= n the master. =A0On reading the Citrix documentation that the network confi= guration on the master is replicated on the slave on joining the pool, I no= w understand that this is not strictly applicable for the bond device id. = =A0What muddled the issues in my case was that I was using the bond device = id (bondx) also as the network label to which the bond pif was attached. = =A0As soon as I accepted that bond device ids may be different on different= hosts in the pool, even if they correspond to the same pair of NICs, then = the situation was clarified. =A0In my case, the situation is now:

NIC =A0 =A0 master =A0 =A0slave =A0 =A0xapi
-= ------------------------------------------
eth0 =A0 =A0 no bond =A0no bond=A0
eth 1/2 bond 0 =A0 =A0bond 2 =A0xapi3
eth 3/4 bond 1 =A0 =A0bond 0 =A0xapi9
eth 5/6 bond 2 =A0 = =A0bond 1 =A0xapi11

=
The slave can fu= lly participate in the pool as far as I can determine.

Unfort= unately I cannot go back to the original topic as the slave on the old vers= ion was ejected or forgotten from the pool at some stage. =A0I apologise fo= r the off-topic diversion.


On Wed,= Dec 19, 2012 at 4:42 PM, Black Bird <blackbird1758@gmail.com>= ; wrote:
I haven't updated this = thread for a while, although I've been busy moving from one problem to = the next.

a) the problem I reported above, needs some clarification. = =A0The upgrade of 1.6Beta2 to 1.6final had worked on an MBR partitioned mas= ter on a cleanly installed host. =A0

However the same upgrade on a 1.6Beta2 GPT partitioned = master had failed on a host which had been de-mirrored (using filesystem co= py from mirrored to a non mirrored disk). =A0Although the non-mirrored host= was bootable and completely functional, the 1.6Final installer failed to r= ecognise an existing installation. =A0I realised that the same situation ex= isted when a mirrored host is moved to a non-mirrored MBR partitioned maste= r, (bootable, fully functional, and not seen by the installer).

b) I was able to do a normal clean installation of 1.6B= eta2 on an unmirrored host, do an xe-pool-restore-database, and then upgrad= e to 1.6Final. =A0This is appropriate on the master, but not on slaves. =A0= The host can then be re-converted to mirrored configuration.

c) on the slaves, xe-pool-restore-database is not appro= priate as discussed. =A0As mentioned above, the installer is unable to reco= gnise a working de-mirrored installation. =A0So I reverted to the process o= utlined by George previously.

I did a clean installation of 1.6Beta2 on a single disk= . =A0I entered into single user mode, set the ethernet devices manually usi= ng /etc/sysconfig/network-scripts/interface-rename-data/static-rules.conf, = copied across /etc/xensource* and /var/xapi from the mirrored disks and reb= ooted. This was a checkpoint which was intended to verify a de-mirrored sla= ve prior to a subsequent upgrade. =A0Unfortunately, as the slave boots up, = it looses connectivity with the master. =A0I repeated this process (i.e. ne= w installation, copy config files across and reboot) a number of times to t= ry and find a pattern, but on occasion some network cards did not come up, = or xapi complained about not reaching the master. =A0I've been trying d= ifferent combinations of this process, trying to force the network interfac= e names before and after installation, to no avail.

At one stage, in desperation I reset the network with x= e-reset-networking, but then the slave joined the pool with completely wron= g eth values and bonded interfaces. =A0I've been unable to resolve this= .

Giving up on this approach, I've also tried to add = a new slave to the pool, intending to get a fresh host to which I can subse= quently add the local storage. =A0To my disappointment, the network configu= ration on the new host also does not reflect the one expected. =A0I had exp= ected the network configuration of the master
eth0 no bond
eth 1/2 bond 0
eth 3/4 bond 1
eth 5/6 bond 2
to be reflected in the slave. =A0However what h= as happened is that on joining the pool, the bonds are created but are conn= ected to the wrong xapi network.

At this stage I have no way forward. =A0For me the main= point of having a pool is to share configuration detail between hosts and = automate the installation process when a new slave enters the pool (there a= re other advantages too), adopting things like common network configuration= , common storage networking etc. =A0If this process is not reliable then I = question the validity of having a pool. =A0At this stage I'm considerin= g reverting to single host masters and doing additional configuration manua= lly or using an external cloud orchestration facility such as OpenStack.

On Mon, Dec 3, 2012 at 2:01 PM, Black Bird= <blackbird1758@gmail.com> wrote:
Hmmm. =A0I've managed to upgrade from 1.= 6Beta2 to 1.6Final from an MBR-partitioned master, but not a GPT-partitione= d master. =A0In the latter case, the installer does not recognise an existi= ng installation and proceeds to ask for a root password, at which stage I s= top.

Should a GPT-partitioned master be able to be recognised and= upgraded?


On Fri, Nov 30, 2012 at 3:07 PM, Black Bird = <blackbird1= 758@gmail.com> wrote:
I have thought of possibly a better procedur= e (albeit still a workaround) than the one I proposed in the first email.
(a) make a pool-dump-database and store safely
(b) extrac= t one hard disk and store as a recovery strategy (exist_device2), leaving t= he other (exist_device1)
(c) create 2 new partitions on a separate temporary device (temp_device), s= ame sized as those live
(d) copy the contents of the existing two partitions (currentl= y /dev/md0 and /dev/md1). =A0(Incidentally, I think it's of no use to m= irror the 2nd partition, as it is only used during installation as a backup= , which is only able to use raw partitions, but this is a separate story)
(e) reboot,=A0
(f) ente= r the BIOS screen and configure temp_device as the default boot device
<= /div>
(g) continue wit= h boot and confirm that XCP host is working as normal
(h) insert the upgrade ISO media= (CD/USB)
(i) reboot=
(j) enter = the BIOS screen and configure device containing the ISO media as the defaul= t boot device
(k) during= the installer stage, select temp_device. =A0
(l) The installer should now recognise a= n existing installation, and any backups. =A0Proceed with upgrade as normal=
(m) reboot at en= d, removing installer media
(n)=A0enter the BIOS screen and configure temp_device as t= he default boot device
(o) on bootup, x= sconsole will show that the local SR is unavailable. =A0Some more steps are= needed just to re-set up the md device for local storage. =A0The SR config= uration should still be there. =A0If no local SR exists, then skip to (t)
(p)=A0mdadm --ex= amine --brief --scan --config=3Dpartitions >> /etc/mdadm.conf (this w= ill restore the mdadm configuration, from the md metadata on the partitions= in exist_device1
(q) mdadm --asse= mble /dev/md2 (restart the md device containing the LVM volumes used by the= local SR)
(r) xe pbd-plug (attach the storage to the SR)
(s) at this stage you should be able to= test that any VMs needing VDIs on the local SR can be started
(t) copy the contents of the filesystems on the temp_device back onto /dev/= md0 and /dev/md1
(u) reboot while removing temp_device (or rather shutdown, remove tem= p_device, start host)
(v) in BIOS scre= en configure exist_device1 as the boot device
(w) verify that XCP host is running norm= ally
(x) insert 2nd d= isk exist_device2
(z) mdadm /dev/md<x> --re-add /dev/<exist_device2><pa= rtition>

This procedure avoids = a completely new installation, while retaining a fallback. =A0It should als= o work for a slave.

=
So far I've = tested parts of the above, but not as a complete procedure. =A0That's m= y next step. =A0I'll keep you posted.



On Fri, Nov 30, 2012 at 10:13 AM, George Shuklin <george.shuklin@= gmail.com> wrote:

I'd also love to see at least some procedure taking such installations = as a consideration, as we're also using XCP/XS on software RAID1, and e= very upgrade is in fact a reinstallation, very suboptimal procedure. Perhap= s, given the fact XCP doesnt have to be tied to 'supported configuratio= n' as XS does, we could have mdraid support in XCP for installation/rei= nstallation since so many people use it?

Well, I've gladly do this, but main problem is opensource part. xen-api= is pure opensource and source is available on github.

XCP/XenServer installer is not. I mean, there is no published way to do som= ething like 'make xcp-iso' command. Internals of installer is half-= python, but no any information about xen-api expectation about files placem= ent in older installation or proper way to do stuff. We internally simply h= ack original installer ISO to help us with installation procedure over md r= aid1. It looks kinda ugly and definitively not for 'public'. And I = really wants to create it properly...



_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




--485b397dd69747623e04d2b1f7f0-- --===============1639049380060407142== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1639049380060407142==-- From xen-api-bounces@lists.xen.org Mon Jan 07 12:30:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 12:30:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsBq0-0001yy-1l; Mon, 07 Jan 2013 12:29:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsBpy-0001yq-3d for xen-api@lists.xen.org; Mon, 07 Jan 2013 12:29:54 +0000 Received: from [85.158.143.35:64804] by server-2.bemta-4.messagelabs.com id 8C/00-24322-1CFBAE05; Mon, 07 Jan 2013 12:29:53 +0000 X-Env-Sender: blackbird1758@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1357561765!13912525!1 X-Originating-IP: [209.85.216.171] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26001 invoked from network); 7 Jan 2013 12:29:27 -0000 Received: from mail-qc0-f171.google.com (HELO mail-qc0-f171.google.com) (209.85.216.171) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2013 12:29:27 -0000 Received: by mail-qc0-f171.google.com with SMTP id d1so12075580qca.2 for ; Mon, 07 Jan 2013 04:28:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Et62acBI6ctdigBEOm1YmPX+wlyynpXbbd/SJa2G6ns=; b=tEIM8VTZJ5vi12+fHlVWHy8fTeWXyWLpCUkxrWjmIQb6tN9wmxD5BbmdSazbowq01E 3bWexElx4HJgwqzyCya1kNJ0H1QgDuo/eKTrrLGykn8QQQwBk18mhjCQk4IzKj6QakFB xrSxwcyInGhQZd7VaCSPxV00j2mTVK6x6jBhGGvXmPfo56p+n6tvqG5AJKkVAgTevYDS V/QdQM0r/dZO76Oic6m9c5fSZKfGGxpVvF5UYOsTVvUSm0vioOSTMgaRxkyJcgY3LDEG 09LbYPa4Wb/LhsBME5qJzAtJVSbGMDeZLKRHW/TWH1MI9Ru9hK/UcJJySR39mQBXiXX3 YiiA== MIME-Version: 1.0 Received: by 10.224.185.148 with SMTP id co20mr4980531qab.94.1357561706537; Mon, 07 Jan 2013 04:28:26 -0800 (PST) Received: by 10.49.11.208 with HTTP; Mon, 7 Jan 2013 04:28:26 -0800 (PST) In-Reply-To: References: <50B7366B.60509@gmail.com> <50B7EC0F.7020008@gmail.com> Date: Mon, 7 Jan 2013 23:28:26 +1100 Message-ID: From: Black Bird To: George Shuklin Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 Beta: upgrade of RAID 1 installation X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1639049380060407142==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1639049380060407142== Content-Type: multipart/alternative; boundary=485b397dd69747623e04d2b1f7f0 --485b397dd69747623e04d2b1f7f0 Content-Type: text/plain; charset=ISO-8859-1 I'd like to report some progress here on the networking issues that stopped me. I modified my approach in two ways. a) for the new slave, instead of the management network starting on one of the NICs of the future bond, I used eth0 which is unbonded in its final configuration. This avoided loosing connectivity upon joining the pool. The management network can be moved later. b) I stated above that 'the bonds are created but are connected to the wrong xapi network'. I now look at it the other way round, i.e. that the xapi network is fine and the joining process creates bonds whose numbering on the slave may be different from the numbering on the master. On reading the Citrix documentation that the network configuration on the master is replicated on the slave on joining the pool, I now understand that this is not strictly applicable for the bond device id. What muddled the issues in my case was that I was using the bond device id (bondx) also as the network label to which the bond pif was attached. As soon as I accepted that bond device ids may be different on different hosts in the pool, even if they correspond to the same pair of NICs, then the situation was clarified. In my case, the situation is now: NIC master slave xapi ------------------------------------------- eth0 no bond no bond eth 1/2 bond 0 bond 2 xapi3 eth 3/4 bond 1 bond 0 xapi9 eth 5/6 bond 2 bond 1 xapi11 The slave can fully participate in the pool as far as I can determine. Unfortunately I cannot go back to the original topic as the slave on the old version was ejected or forgotten from the pool at some stage. I apologise for the off-topic diversion. On Wed, Dec 19, 2012 at 4:42 PM, Black Bird wrote: > I haven't updated this thread for a while, although I've been busy moving > from one problem to the next. > > a) the problem I reported above, needs some clarification. The upgrade of > 1.6Beta2 to 1.6final had worked on an MBR partitioned master on a cleanly > installed host. > > However the same upgrade on a 1.6Beta2 GPT partitioned master had failed > on a host which had been de-mirrored (using filesystem copy from mirrored > to a non mirrored disk). Although the non-mirrored host was bootable and > completely functional, the 1.6Final installer failed to recognise an > existing installation. I realised that the same situation existed when a > mirrored host is moved to a non-mirrored MBR partitioned master, (bootable, > fully functional, and not seen by the installer). > > b) I was able to do a normal clean installation of 1.6Beta2 on an > unmirrored host, do an xe-pool-restore-database, and then upgrade to > 1.6Final. This is appropriate on the master, but not on slaves. The host > can then be re-converted to mirrored configuration. > > c) on the slaves, xe-pool-restore-database is not appropriate as > discussed. As mentioned above, the installer is unable to recognise a > working de-mirrored installation. So I reverted to the process outlined by > George previously. > > I did a clean installation of 1.6Beta2 on a single disk. I entered into > single user mode, set the ethernet devices manually using > /etc/sysconfig/network-scripts/interface-rename-data/static-rules.conf, > copied across /etc/xensource* and /var/xapi from the mirrored disks and > rebooted. This was a checkpoint which was intended to verify a de-mirrored > slave prior to a subsequent upgrade. Unfortunately, as the slave boots up, > it looses connectivity with the master. I repeated this process (i.e. new > installation, copy config files across and reboot) a number of times to try > and find a pattern, but on occasion some network cards did not come up, or > xapi complained about not reaching the master. I've been trying different > combinations of this process, trying to force the network interface names > before and after installation, to no avail. > > At one stage, in desperation I reset the network with xe-reset-networking, > but then the slave joined the pool with completely wrong eth values and > bonded interfaces. I've been unable to resolve this. > > Giving up on this approach, I've also tried to add a new slave to the > pool, intending to get a fresh host to which I can subsequently add the > local storage. To my disappointment, the network configuration on the new > host also does not reflect the one expected. I had expected the network > configuration of the master > eth0 no bond > eth 1/2 bond 0 > eth 3/4 bond 1 > eth 5/6 bond 2 > to be reflected in the slave. However what has happened is that on > joining the pool, the bonds are created but are connected to the wrong xapi > network. > > At this stage I have no way forward. For me the main point of having a > pool is to share configuration detail between hosts and automate the > installation process when a new slave enters the pool (there are other > advantages too), adopting things like common network configuration, common > storage networking etc. If this process is not reliable then I question > the validity of having a pool. At this stage I'm considering reverting to > single host masters and doing additional configuration manually or using an > external cloud orchestration facility such as OpenStack. > > > On Mon, Dec 3, 2012 at 2:01 PM, Black Bird wrote: > >> Hmmm. I've managed to upgrade from 1.6Beta2 to 1.6Final from an >> MBR-partitioned master, but not a GPT-partitioned master. In the latter >> case, the installer does not recognise an existing installation and >> proceeds to ask for a root password, at which stage I stop. >> >> Should a GPT-partitioned master be able to be recognised and upgraded? >> >> >> On Fri, Nov 30, 2012 at 3:07 PM, Black Bird wrote: >> >>> I have thought of possibly a better procedure (albeit still a >>> workaround) than the one I proposed in the first email. >>> >>> (a) make a pool-dump-database and store safely >>> (b) extract one hard disk and store as a recovery strategy >>> (exist_device2), leaving the other (exist_device1) >>> (c) create 2 new partitions on a separate temporary device >>> (temp_device), same sized as those live >>> (d) copy the contents of the existing two partitions (currently /dev/md0 >>> and /dev/md1). (Incidentally, I think it's of no use to mirror the 2nd >>> partition, as it is only used during installation as a backup, which is >>> only able to use raw partitions, but this is a separate story) >>> (e) reboot, >>> (f) enter the BIOS screen and configure temp_device as the default boot >>> device >>> (g) continue with boot and confirm that XCP host is working as normal >>> (h) insert the upgrade ISO media (CD/USB) >>> (i) reboot >>> (j) enter the BIOS screen and configure device containing the ISO media >>> as the default boot device >>> (k) during the installer stage, select temp_device. >>> (l) The installer should now recognise an existing installation, and any >>> backups. Proceed with upgrade as normal >>> (m) reboot at end, removing installer media >>> (n) enter the BIOS screen and configure temp_device as the default boot >>> device >>> (o) on bootup, xsconsole will show that the local SR is unavailable. >>> Some more steps are needed just to re-set up the md device for local >>> storage. The SR configuration should still be there. If no local SR >>> exists, then skip to (t) >>> (p) mdadm --examine --brief --scan --config=partitions >> >>> /etc/mdadm.conf (this will restore the mdadm configuration, from the md >>> metadata on the partitions in exist_device1 >>> (q) mdadm --assemble /dev/md2 (restart the md device containing the LVM >>> volumes used by the local SR) >>> (r) xe pbd-plug (attach the storage to the SR) >>> (s) at this stage you should be able to test that any VMs needing VDIs >>> on the local SR can be started >>> (t) copy the contents of the filesystems on the temp_device back onto >>> /dev/md0 and /dev/md1 >>> (u) reboot while removing temp_device (or rather shutdown, remove >>> temp_device, start host) >>> (v) in BIOS screen configure exist_device1 as the boot device >>> (w) verify that XCP host is running normally >>> (x) insert 2nd disk exist_device2 >>> (z) mdadm /dev/md --re-add /dev/ >>> >>> This procedure avoids a completely new installation, while retaining a >>> fallback. It should also work for a slave. >>> >>> So far I've tested parts of the above, but not as a complete procedure. >>> That's my next step. I'll keep you posted. >>> >>> >>> >>> On Fri, Nov 30, 2012 at 10:13 AM, George Shuklin < >>> george.shuklin@gmail.com> wrote: >>> >>>> >>>> I'd also love to see at least some procedure taking such installations >>>>> as a consideration, as we're also using XCP/XS on software RAID1, and every >>>>> upgrade is in fact a reinstallation, very suboptimal procedure. Perhaps, >>>>> given the fact XCP doesnt have to be tied to 'supported configuration' as >>>>> XS does, we could have mdraid support in XCP for >>>>> installation/reinstallation since so many people use it? >>>>> >>>>> Well, I've gladly do this, but main problem is opensource part. >>>> xen-api is pure opensource and source is available on github. >>>> >>>> XCP/XenServer installer is not. I mean, there is no published way to do >>>> something like 'make xcp-iso' command. Internals of installer is >>>> half-python, but no any information about xen-api expectation about files >>>> placement in older installation or proper way to do stuff. We internally >>>> simply hack original installer ISO to help us with installation procedure >>>> over md raid1. It looks kinda ugly and definitively not for 'public'. And I >>>> really wants to create it properly... >>>> >>>> >>>> >>>> ______________________________**_________________ >>>> Xen-api mailing list >>>> Xen-api@lists.xen.org >>>> http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api >>>> >>> >>> >> > --485b397dd69747623e04d2b1f7f0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I'd like to report some progress here on the networkin= g issues that stopped me. =A0I modified my approach in two ways.

a) for the new slave, instead of the management network starting o= n one of the NICs of the future bond, I used eth0 which is unbonded in its = final configuration. =A0This avoided loosing connectivity upon joining the = pool. =A0The management network can be moved later.

b) I stated above that 'the bonds are created but a= re connected to the wrong xapi network'. =A0I now look at it the other = way round, i.e. that the xapi network is fine and the joining process creat= es bonds whose numbering on the slave may be different from the numbering o= n the master. =A0On reading the Citrix documentation that the network confi= guration on the master is replicated on the slave on joining the pool, I no= w understand that this is not strictly applicable for the bond device id. = =A0What muddled the issues in my case was that I was using the bond device = id (bondx) also as the network label to which the bond pif was attached. = =A0As soon as I accepted that bond device ids may be different on different= hosts in the pool, even if they correspond to the same pair of NICs, then = the situation was clarified. =A0In my case, the situation is now:

NIC =A0 =A0 master =A0 =A0slave =A0 =A0xapi
-= ------------------------------------------
eth0 =A0 =A0 no bond =A0no bond=A0
eth 1/2 bond 0 =A0 =A0bond 2 =A0xapi3
eth 3/4 bond 1 =A0 =A0bond 0 =A0xapi9
eth 5/6 bond 2 =A0 = =A0bond 1 =A0xapi11

=
The slave can fu= lly participate in the pool as far as I can determine.

Unfort= unately I cannot go back to the original topic as the slave on the old vers= ion was ejected or forgotten from the pool at some stage. =A0I apologise fo= r the off-topic diversion.


On Wed,= Dec 19, 2012 at 4:42 PM, Black Bird <blackbird1758@gmail.com>= ; wrote:
I haven't updated this = thread for a while, although I've been busy moving from one problem to = the next.

a) the problem I reported above, needs some clarification. = =A0The upgrade of 1.6Beta2 to 1.6final had worked on an MBR partitioned mas= ter on a cleanly installed host. =A0

However the same upgrade on a 1.6Beta2 GPT partitioned = master had failed on a host which had been de-mirrored (using filesystem co= py from mirrored to a non mirrored disk). =A0Although the non-mirrored host= was bootable and completely functional, the 1.6Final installer failed to r= ecognise an existing installation. =A0I realised that the same situation ex= isted when a mirrored host is moved to a non-mirrored MBR partitioned maste= r, (bootable, fully functional, and not seen by the installer).

b) I was able to do a normal clean installation of 1.6B= eta2 on an unmirrored host, do an xe-pool-restore-database, and then upgrad= e to 1.6Final. =A0This is appropriate on the master, but not on slaves. =A0= The host can then be re-converted to mirrored configuration.

c) on the slaves, xe-pool-restore-database is not appro= priate as discussed. =A0As mentioned above, the installer is unable to reco= gnise a working de-mirrored installation. =A0So I reverted to the process o= utlined by George previously.

I did a clean installation of 1.6Beta2 on a single disk= . =A0I entered into single user mode, set the ethernet devices manually usi= ng /etc/sysconfig/network-scripts/interface-rename-data/static-rules.conf, = copied across /etc/xensource* and /var/xapi from the mirrored disks and reb= ooted. This was a checkpoint which was intended to verify a de-mirrored sla= ve prior to a subsequent upgrade. =A0Unfortunately, as the slave boots up, = it looses connectivity with the master. =A0I repeated this process (i.e. ne= w installation, copy config files across and reboot) a number of times to t= ry and find a pattern, but on occasion some network cards did not come up, = or xapi complained about not reaching the master. =A0I've been trying d= ifferent combinations of this process, trying to force the network interfac= e names before and after installation, to no avail.

At one stage, in desperation I reset the network with x= e-reset-networking, but then the slave joined the pool with completely wron= g eth values and bonded interfaces. =A0I've been unable to resolve this= .

Giving up on this approach, I've also tried to add = a new slave to the pool, intending to get a fresh host to which I can subse= quently add the local storage. =A0To my disappointment, the network configu= ration on the new host also does not reflect the one expected. =A0I had exp= ected the network configuration of the master
eth0 no bond
eth 1/2 bond 0
eth 3/4 bond 1
eth 5/6 bond 2
to be reflected in the slave. =A0However what h= as happened is that on joining the pool, the bonds are created but are conn= ected to the wrong xapi network.

At this stage I have no way forward. =A0For me the main= point of having a pool is to share configuration detail between hosts and = automate the installation process when a new slave enters the pool (there a= re other advantages too), adopting things like common network configuration= , common storage networking etc. =A0If this process is not reliable then I = question the validity of having a pool. =A0At this stage I'm considerin= g reverting to single host masters and doing additional configuration manua= lly or using an external cloud orchestration facility such as OpenStack.

On Mon, Dec 3, 2012 at 2:01 PM, Black Bird= <blackbird1758@gmail.com> wrote:
Hmmm. =A0I've managed to upgrade from 1.= 6Beta2 to 1.6Final from an MBR-partitioned master, but not a GPT-partitione= d master. =A0In the latter case, the installer does not recognise an existi= ng installation and proceeds to ask for a root password, at which stage I s= top.

Should a GPT-partitioned master be able to be recognised and= upgraded?


On Fri, Nov 30, 2012 at 3:07 PM, Black Bird = <blackbird1= 758@gmail.com> wrote:
I have thought of possibly a better procedur= e (albeit still a workaround) than the one I proposed in the first email.
(a) make a pool-dump-database and store safely
(b) extrac= t one hard disk and store as a recovery strategy (exist_device2), leaving t= he other (exist_device1)
(c) create 2 new partitions on a separate temporary device (temp_device), s= ame sized as those live
(d) copy the contents of the existing two partitions (currentl= y /dev/md0 and /dev/md1). =A0(Incidentally, I think it's of no use to m= irror the 2nd partition, as it is only used during installation as a backup= , which is only able to use raw partitions, but this is a separate story)
(e) reboot,=A0
(f) ente= r the BIOS screen and configure temp_device as the default boot device
<= /div>
(g) continue wit= h boot and confirm that XCP host is working as normal
(h) insert the upgrade ISO media= (CD/USB)
(i) reboot=
(j) enter = the BIOS screen and configure device containing the ISO media as the defaul= t boot device
(k) during= the installer stage, select temp_device. =A0
(l) The installer should now recognise a= n existing installation, and any backups. =A0Proceed with upgrade as normal=
(m) reboot at en= d, removing installer media
(n)=A0enter the BIOS screen and configure temp_device as t= he default boot device
(o) on bootup, x= sconsole will show that the local SR is unavailable. =A0Some more steps are= needed just to re-set up the md device for local storage. =A0The SR config= uration should still be there. =A0If no local SR exists, then skip to (t)
(p)=A0mdadm --ex= amine --brief --scan --config=3Dpartitions >> /etc/mdadm.conf (this w= ill restore the mdadm configuration, from the md metadata on the partitions= in exist_device1
(q) mdadm --asse= mble /dev/md2 (restart the md device containing the LVM volumes used by the= local SR)
(r) xe pbd-plug (attach the storage to the SR)
(s) at this stage you should be able to= test that any VMs needing VDIs on the local SR can be started
(t) copy the contents of the filesystems on the temp_device back onto /dev/= md0 and /dev/md1
(u) reboot while removing temp_device (or rather shutdown, remove tem= p_device, start host)
(v) in BIOS scre= en configure exist_device1 as the boot device
(w) verify that XCP host is running norm= ally
(x) insert 2nd d= isk exist_device2
(z) mdadm /dev/md<x> --re-add /dev/<exist_device2><pa= rtition>

This procedure avoids = a completely new installation, while retaining a fallback. =A0It should als= o work for a slave.

=
So far I've = tested parts of the above, but not as a complete procedure. =A0That's m= y next step. =A0I'll keep you posted.



On Fri, Nov 30, 2012 at 10:13 AM, George Shuklin <george.shuklin@= gmail.com> wrote:

I'd also love to see at least some procedure taking such installations = as a consideration, as we're also using XCP/XS on software RAID1, and e= very upgrade is in fact a reinstallation, very suboptimal procedure. Perhap= s, given the fact XCP doesnt have to be tied to 'supported configuratio= n' as XS does, we could have mdraid support in XCP for installation/rei= nstallation since so many people use it?

Well, I've gladly do this, but main problem is opensource part. xen-api= is pure opensource and source is available on github.

XCP/XenServer installer is not. I mean, there is no published way to do som= ething like 'make xcp-iso' command. Internals of installer is half-= python, but no any information about xen-api expectation about files placem= ent in older installation or proper way to do stuff. We internally simply h= ack original installer ISO to help us with installation procedure over md r= aid1. It looks kinda ugly and definitively not for 'public'. And I = really wants to create it properly...



_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




--485b397dd69747623e04d2b1f7f0-- --===============1639049380060407142== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1639049380060407142==-- From xen-api-bounces@lists.xen.org Mon Jan 07 14:23:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 14:23:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsDbI-0006Pl-Ga; Mon, 07 Jan 2013 14:22:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsDbH-0006Pg-5j for xen-api@lists.xen.org; Mon, 07 Jan 2013 14:22:51 +0000 Received: from [85.158.139.211:7688] by server-8.bemta-5.messagelabs.com id 04/39-15003-A3ADAE05; Mon, 07 Jan 2013 14:22:50 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1357568569!18068155!1 X-Originating-IP: [207.126.144.123] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30374 invoked from network); 7 Jan 2013 14:22:49 -0000 Received: from eu1sys200aog107.obsmtp.com (HELO eu1sys200aog107.obsmtp.com) (207.126.144.123) by server-16.tower-206.messagelabs.com with SMTP; 7 Jan 2013 14:22:49 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob107.postini.com ([207.126.147.11]) with SMTP ID DSNKUOraOBw0oFHp6R69MduGq3T5XTMO29Pr@postini.com; Mon, 07 Jan 2013 14:22:49 UTC Received: from batwexhtca01.uk.futurenet.com (batwexhtca01.uk.futurenet.com [172.23.130.3]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 78CCB7F447C; Mon, 7 Jan 2013 14:22:48 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by batwexhtca01 ([172.23.130.3]) with mapi; Mon, 7 Jan 2013 14:22:48 +0000 From: Dave Avent To: "<2rushikeshj@gmail.com> <2rushikeshj@gmail.com>" <2rushikeshj@gmail.com> Date: Mon, 7 Jan 2013 14:22:47 +0000 Thread-Topic: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3s4neYFnIPtCMLQOy1zz7Y+aQT4g== Message-ID: <64828C22-43AE-40EA-B809-79BC801AB69F@futurenet.com> References: <50e57619.4553420a.529d.ffffadbd@mx.google.com> In-Reply-To: <50e57619.4553420a.529d.ffffadbd@mx.google.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 3 Jan 2013, at 11:54, <2rushikeshj@gmail.com> <2rushikeshj@gmail.com> wrote: > > On Thu, 3 Jan 2013 16:44:14 +0550, xen-api-bounces@lists.xen.org wrote: >> All, >> >> I have been playing with Xen Cloud Platform 1.6 in the lab and have been noticing some strange behaviour when using the API to drive it. Using XenCenter worked some of the time but then appeared to freeze, not refresh and then on re-connecting get stuck on "Synchronising". I put this down to the client software and switched instead to writing my own client interface using Ruby and the FOG libraries. This worked well but I started seeing the same lock-ups. After digging about I realised that it always locks up at the same point namely the VM.get_all_records call. >> >> The call is received as the xensource.log shows: >> >> xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records D:7f14fc2bea45|api_readonly] VM.get_all_records >> >> But nothing is received and the clients TCP connection times out. >> >> This problem happens for well over 50% of the calls made to the API so I am interested to know if anyone else is having this problem? >> > > Your Cluster Host Count and VM count ( ON & OFF ) will be helpful. 0. This is a vanilla, out-of-the box, ISO install of XCP 1.6 > > Usual errors are to be checked in xensource.log, messages, kern.log No errors in any logs. > > Try to get only list of VM ids and then do a get_record for each VM to see if you get caught in same problem As mentioned, no VMs. Just pre-installed Templates. > > > >> Regards, >> >> Dave-- >> Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. >> >> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. >> >> The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. >> >> Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. >> >> ***** >> Save resources: think before you print. >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 07 14:23:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 14:23:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsDbI-0006Pl-Ga; Mon, 07 Jan 2013 14:22:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsDbH-0006Pg-5j for xen-api@lists.xen.org; Mon, 07 Jan 2013 14:22:51 +0000 Received: from [85.158.139.211:7688] by server-8.bemta-5.messagelabs.com id 04/39-15003-A3ADAE05; Mon, 07 Jan 2013 14:22:50 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1357568569!18068155!1 X-Originating-IP: [207.126.144.123] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30374 invoked from network); 7 Jan 2013 14:22:49 -0000 Received: from eu1sys200aog107.obsmtp.com (HELO eu1sys200aog107.obsmtp.com) (207.126.144.123) by server-16.tower-206.messagelabs.com with SMTP; 7 Jan 2013 14:22:49 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob107.postini.com ([207.126.147.11]) with SMTP ID DSNKUOraOBw0oFHp6R69MduGq3T5XTMO29Pr@postini.com; Mon, 07 Jan 2013 14:22:49 UTC Received: from batwexhtca01.uk.futurenet.com (batwexhtca01.uk.futurenet.com [172.23.130.3]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 78CCB7F447C; Mon, 7 Jan 2013 14:22:48 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by batwexhtca01 ([172.23.130.3]) with mapi; Mon, 7 Jan 2013 14:22:48 +0000 From: Dave Avent To: "<2rushikeshj@gmail.com> <2rushikeshj@gmail.com>" <2rushikeshj@gmail.com> Date: Mon, 7 Jan 2013 14:22:47 +0000 Thread-Topic: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3s4neYFnIPtCMLQOy1zz7Y+aQT4g== Message-ID: <64828C22-43AE-40EA-B809-79BC801AB69F@futurenet.com> References: <50e57619.4553420a.529d.ffffadbd@mx.google.com> In-Reply-To: <50e57619.4553420a.529d.ffffadbd@mx.google.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 3 Jan 2013, at 11:54, <2rushikeshj@gmail.com> <2rushikeshj@gmail.com> wrote: > > On Thu, 3 Jan 2013 16:44:14 +0550, xen-api-bounces@lists.xen.org wrote: >> All, >> >> I have been playing with Xen Cloud Platform 1.6 in the lab and have been noticing some strange behaviour when using the API to drive it. Using XenCenter worked some of the time but then appeared to freeze, not refresh and then on re-connecting get stuck on "Synchronising". I put this down to the client software and switched instead to writing my own client interface using Ruby and the FOG libraries. This worked well but I started seeing the same lock-ups. After digging about I realised that it always locks up at the same point namely the VM.get_all_records call. >> >> The call is received as the xensource.log shows: >> >> xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records D:7f14fc2bea45|api_readonly] VM.get_all_records >> >> But nothing is received and the clients TCP connection times out. >> >> This problem happens for well over 50% of the calls made to the API so I am interested to know if anyone else is having this problem? >> > > Your Cluster Host Count and VM count ( ON & OFF ) will be helpful. 0. This is a vanilla, out-of-the box, ISO install of XCP 1.6 > > Usual errors are to be checked in xensource.log, messages, kern.log No errors in any logs. > > Try to get only list of VM ids and then do a get_record for each VM to see if you get caught in same problem As mentioned, no VMs. Just pre-installed Templates. > > > >> Regards, >> >> Dave-- >> Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. >> >> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. >> >> The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. >> >> Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. >> >> ***** >> Save resources: think before you print. >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 07 16:28:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 16:28:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFYT-0004tq-Nv; Mon, 07 Jan 2013 16:28:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFYR-0004tV-Tx; Mon, 07 Jan 2013 16:28:04 +0000 Received: from [85.158.138.51:55894] by server-16.bemta-3.messagelabs.com id 50/11-27634-297FAE05; Mon, 07 Jan 2013 16:28:02 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1357576065!9674328!1 X-Originating-IP: [141.146.126.69] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuNjkgPT4gMTQ0ODE5\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3646 invoked from network); 7 Jan 2013 16:27:49 -0000 Received: from aserp1040.oracle.com (HELO aserp1040.oracle.com) (141.146.126.69) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Jan 2013 16:27:49 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r07GRcuB006304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 7 Jan 2013 16:27:39 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r07GRaQ2012149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jan 2013 16:27:37 GMT Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id r07GRanb031614; Mon, 7 Jan 2013 10:27:36 -0600 Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 07 Jan 2013 08:27:36 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id B85761BF844; Mon, 7 Jan 2013 11:27:34 -0500 (EST) Date: Mon, 7 Jan 2013 11:27:34 -0500 From: Konrad Rzeszutek Wilk To: Dario Faggioli Message-ID: <20130107162734.GA6402@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1355959883.28419.8.camel@Abyss> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Cc: konrad@kernel.org, xen-arm@lists.xen.org, "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > > > c) Ideally I would like to add biography and interest section for > > > all our mentors. I can create a wiki template for mentors if it > > > helps Ideas for GSOC: - Support microcode update bundled in with the initrd in Xen. Here is the Linux side of it comes out looking: http://markmail.org/thread/ewrs7fa66knfwzbo - Write Xen PV Architecture Book/Manual/whatever. We have been slowly going through the PV architecture and documenting it. It would nice to have somebody full-time doing it and asking questions. And then the answers would be written in this book. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 07 16:28:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 16:28:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFYT-0004tq-Nv; Mon, 07 Jan 2013 16:28:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFYR-0004tV-Tx; Mon, 07 Jan 2013 16:28:04 +0000 Received: from [85.158.138.51:55894] by server-16.bemta-3.messagelabs.com id 50/11-27634-297FAE05; Mon, 07 Jan 2013 16:28:02 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1357576065!9674328!1 X-Originating-IP: [141.146.126.69] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuNjkgPT4gMTQ0ODE5\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3646 invoked from network); 7 Jan 2013 16:27:49 -0000 Received: from aserp1040.oracle.com (HELO aserp1040.oracle.com) (141.146.126.69) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Jan 2013 16:27:49 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r07GRcuB006304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 7 Jan 2013 16:27:39 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r07GRaQ2012149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jan 2013 16:27:37 GMT Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id r07GRanb031614; Mon, 7 Jan 2013 10:27:36 -0600 Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 07 Jan 2013 08:27:36 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id B85761BF844; Mon, 7 Jan 2013 11:27:34 -0500 (EST) Date: Mon, 7 Jan 2013 11:27:34 -0500 From: Konrad Rzeszutek Wilk To: Dario Faggioli Message-ID: <20130107162734.GA6402@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1355959883.28419.8.camel@Abyss> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Cc: konrad@kernel.org, xen-arm@lists.xen.org, "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > > > c) Ideally I would like to add biography and interest section for > > > all our mentors. I can create a wiki template for mentors if it > > > helps Ideas for GSOC: - Support microcode update bundled in with the initrd in Xen. Here is the Linux side of it comes out looking: http://markmail.org/thread/ewrs7fa66knfwzbo - Write Xen PV Architecture Book/Manual/whatever. We have been slowly going through the PV architecture and documenting it. It would nice to have somebody full-time doing it and asking questions. And then the answers would be written in this book. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 07 16:31:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 16:31:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFbe-0005MZ-07; Mon, 07 Jan 2013 16:31:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrC28-0005L1-El for xen-api@lists.xen.org; Fri, 04 Jan 2013 18:30:20 +0000 Received: from [85.158.137.99:43389] by server-7.bemta-3.messagelabs.com id AC/EB-23008-BBF17E05; Fri, 04 Jan 2013 18:30:19 +0000 X-Env-Sender: bailey.alex@live.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1357324211!17185945!1 X-Originating-IP: [65.55.111.174] X-SpamReason: No, hits=1.0 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_10_20,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12225 invoked from network); 4 Jan 2013 18:30:12 -0000 Received: from blu0-omc4-s35.blu0.hotmail.com (HELO blu0-omc4-s35.blu0.hotmail.com) (65.55.111.174) by server-2.tower-217.messagelabs.com with SMTP; 4 Jan 2013 18:30:12 -0000 Received: from BLU174-W26 ([65.55.111.137]) by blu0-omc4-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 4 Jan 2013 10:30:11 -0800 X-EIP: [2ZL5sWzy3+ZQrw3vouKBH+q+z2ff+uhs] X-Originating-Email: [bailey.alex@live.com] Message-ID: From: Alex Bailey To: Date: Fri, 4 Jan 2013 13:30:10 -0500 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 04 Jan 2013 18:30:11.0712 (UTC) FILETIME=[8815E000:01CDEAA9] X-Mailman-Approved-At: Mon, 07 Jan 2013 16:31:20 +0000 Subject: [Xen-API] XCP and opensource cloud options X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2418941190287977165==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2418941190287977165== Content-Type: multipart/alternative; boundary="_486d920f-c2bc-41fd-9eb4-dd002691247c_" --_486d920f-c2bc-41fd-9eb4-dd002691247c_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello everyone I am looking into options into implenting a cloud using the latest XCP rele= ase=2C 6809c=2C and am well not positive which direction to go=2C There is of course many options=2C or at least 3 that I have been really lo= oking at=2C There is openstack=2C opennubula and of course cloudstack. >From my understanding=2C XCP 1.6 was built primarily for cloudstack=2C and = requires little or no modification to dom0=2C which is comforting. Cloudstack seems to be the optimal choice=2C yet this openstack movement an= d community is very large=2C there is extensive documentation on it=2C yet = it just seems that there may be "too much" documentation=2C I see many conf= licts with regards to storage options=2C such as "Swift" and "cinder" which= looks more like "swift vs cinder"=2C there is conflicts between nova-netwo= rk and quantum=2C then there are issue's with regards Openstack from my reading needs several modifications to dom0=2C including = the addition of plugins/packages=2C which of course is not the most appeali= ng considering that XCP already has an enormous amount of possibilities. Opennubula seems to be nice and clean=2C the documentation is not nearly as= extensive as openstack=2C yet it seems to be a bit more logical and less "= fluffy"=2C it is primarily a european project=2C that is gaining some groun= d here in North America=2C the reason I mention geography is the fact that = I would like to potentially partner up what I provisioned for this "cloud" = with North American member's=2C as from my ideal cloud is one that is large= not in local size=2C but in geographic size. That is=2C mutual relationshi= ps between other member's of the projects and equal sharing of resources fo= r HA and of course failover's and DR. So it would be of course ideal to provision resources between the partner's= of the cloud=2C which would theoretically have the exact same implications= as to have everything under "one roof"=2C as location A (the local) host w= ould support location B's (the partner's host) resources... I guess my question is=2C has anyone used any of these solutions? and what = did you think about them? Your input would be immensely appreciated. = = --_486d920f-c2bc-41fd-9eb4-dd002691247c_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello everyone

I am looking into options into implenting= a cloud using the latest XCP release=2C 6809c=2C and am well not positive = which direction to go=2C

There is of course many o= ptions=2C or at least 3 that I have been really looking at=2C
There is openstack=2C opennubula and of course cloudstack.

From my understanding=2C XCP 1.6 was built primarily f= or cloudstack=2C and requires little or no modification to dom0=2C which is= comforting.

Cloudstack seems to be the optimal ch= oice=2C yet this openstack movement and community is very large=2C there is= extensive documentation on it=2C yet it just seems that there may be "too = much" documentation=2C I see many conflicts with regards to storage options= =2C such as "Swift" and "cinder" which looks more like "swift vs cinder"=2C= there is conflicts between nova-network and quantum=2C then there are issu= e's with regards

Openstack from my reading needs s= everal modifications to dom0=2C including the addition of plugins/packages= =2C which of course is not the most appealing considering that XCP already = has an enormous amount of possibilities.

Opennubul= a seems to be nice and clean=2C the documentation is not nearly as extensiv= e as openstack=2C yet it seems to be a bit more logical and less "fluffy"= =2C it is primarily a european project=2C that is gaining some ground here = in North America=2C the reason I mention geography is the fact that I would= like to potentially partner up what I provisioned for this "cloud" with No= rth American member's=2C as from my ideal cloud is one that is large not in= local size=2C but in geographic size. That is=2C mutual relationships betw= een other member's of the projects and equal sharing of resources for HA an= d of course failover's and DR.

So it would be of c= ourse ideal to provision resources between the partner's of the cloud=2C wh= ich would theoretically have the exact same implications as to have everyth= ing under "one roof"=2C as location A (the local) host would support locati= on B's (the partner's host) resources...

I guess m= y question is=2C has anyone used any of these solutions? and what did you t= hink about them? Your input would be immensely appreciated.
=
= --_486d920f-c2bc-41fd-9eb4-dd002691247c_-- --===============2418941190287977165== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2418941190287977165==-- From xen-api-bounces@lists.xen.org Mon Jan 07 16:31:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 16:31:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFbe-0005MZ-07; Mon, 07 Jan 2013 16:31:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TrC28-0005L1-El for xen-api@lists.xen.org; Fri, 04 Jan 2013 18:30:20 +0000 Received: from [85.158.137.99:43389] by server-7.bemta-3.messagelabs.com id AC/EB-23008-BBF17E05; Fri, 04 Jan 2013 18:30:19 +0000 X-Env-Sender: bailey.alex@live.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1357324211!17185945!1 X-Originating-IP: [65.55.111.174] X-SpamReason: No, hits=1.0 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_10_20,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12225 invoked from network); 4 Jan 2013 18:30:12 -0000 Received: from blu0-omc4-s35.blu0.hotmail.com (HELO blu0-omc4-s35.blu0.hotmail.com) (65.55.111.174) by server-2.tower-217.messagelabs.com with SMTP; 4 Jan 2013 18:30:12 -0000 Received: from BLU174-W26 ([65.55.111.137]) by blu0-omc4-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 4 Jan 2013 10:30:11 -0800 X-EIP: [2ZL5sWzy3+ZQrw3vouKBH+q+z2ff+uhs] X-Originating-Email: [bailey.alex@live.com] Message-ID: From: Alex Bailey To: Date: Fri, 4 Jan 2013 13:30:10 -0500 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 04 Jan 2013 18:30:11.0712 (UTC) FILETIME=[8815E000:01CDEAA9] X-Mailman-Approved-At: Mon, 07 Jan 2013 16:31:20 +0000 Subject: [Xen-API] XCP and opensource cloud options X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2418941190287977165==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2418941190287977165== Content-Type: multipart/alternative; boundary="_486d920f-c2bc-41fd-9eb4-dd002691247c_" --_486d920f-c2bc-41fd-9eb4-dd002691247c_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello everyone I am looking into options into implenting a cloud using the latest XCP rele= ase=2C 6809c=2C and am well not positive which direction to go=2C There is of course many options=2C or at least 3 that I have been really lo= oking at=2C There is openstack=2C opennubula and of course cloudstack. >From my understanding=2C XCP 1.6 was built primarily for cloudstack=2C and = requires little or no modification to dom0=2C which is comforting. Cloudstack seems to be the optimal choice=2C yet this openstack movement an= d community is very large=2C there is extensive documentation on it=2C yet = it just seems that there may be "too much" documentation=2C I see many conf= licts with regards to storage options=2C such as "Swift" and "cinder" which= looks more like "swift vs cinder"=2C there is conflicts between nova-netwo= rk and quantum=2C then there are issue's with regards Openstack from my reading needs several modifications to dom0=2C including = the addition of plugins/packages=2C which of course is not the most appeali= ng considering that XCP already has an enormous amount of possibilities. Opennubula seems to be nice and clean=2C the documentation is not nearly as= extensive as openstack=2C yet it seems to be a bit more logical and less "= fluffy"=2C it is primarily a european project=2C that is gaining some groun= d here in North America=2C the reason I mention geography is the fact that = I would like to potentially partner up what I provisioned for this "cloud" = with North American member's=2C as from my ideal cloud is one that is large= not in local size=2C but in geographic size. That is=2C mutual relationshi= ps between other member's of the projects and equal sharing of resources fo= r HA and of course failover's and DR. So it would be of course ideal to provision resources between the partner's= of the cloud=2C which would theoretically have the exact same implications= as to have everything under "one roof"=2C as location A (the local) host w= ould support location B's (the partner's host) resources... I guess my question is=2C has anyone used any of these solutions? and what = did you think about them? Your input would be immensely appreciated. = = --_486d920f-c2bc-41fd-9eb4-dd002691247c_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello everyone

I am looking into options into implenting= a cloud using the latest XCP release=2C 6809c=2C and am well not positive = which direction to go=2C

There is of course many o= ptions=2C or at least 3 that I have been really looking at=2C
There is openstack=2C opennubula and of course cloudstack.

From my understanding=2C XCP 1.6 was built primarily f= or cloudstack=2C and requires little or no modification to dom0=2C which is= comforting.

Cloudstack seems to be the optimal ch= oice=2C yet this openstack movement and community is very large=2C there is= extensive documentation on it=2C yet it just seems that there may be "too = much" documentation=2C I see many conflicts with regards to storage options= =2C such as "Swift" and "cinder" which looks more like "swift vs cinder"=2C= there is conflicts between nova-network and quantum=2C then there are issu= e's with regards

Openstack from my reading needs s= everal modifications to dom0=2C including the addition of plugins/packages= =2C which of course is not the most appealing considering that XCP already = has an enormous amount of possibilities.

Opennubul= a seems to be nice and clean=2C the documentation is not nearly as extensiv= e as openstack=2C yet it seems to be a bit more logical and less "fluffy"= =2C it is primarily a european project=2C that is gaining some ground here = in North America=2C the reason I mention geography is the fact that I would= like to potentially partner up what I provisioned for this "cloud" with No= rth American member's=2C as from my ideal cloud is one that is large not in= local size=2C but in geographic size. That is=2C mutual relationships betw= een other member's of the projects and equal sharing of resources for HA an= d of course failover's and DR.

So it would be of c= ourse ideal to provision resources between the partner's of the cloud=2C wh= ich would theoretically have the exact same implications as to have everyth= ing under "one roof"=2C as location A (the local) host would support locati= on B's (the partner's host) resources...

I guess m= y question is=2C has anyone used any of these solutions? and what did you t= hink about them? Your input would be immensely appreciated.
=
= --_486d920f-c2bc-41fd-9eb4-dd002691247c_-- --===============2418941190287977165== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2418941190287977165==-- From xen-api-bounces@lists.xen.org Mon Jan 07 17:42:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 17:42:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsGiB-0008F1-N3; Mon, 07 Jan 2013 17:42:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFrT-0006R7-EA; Mon, 07 Jan 2013 16:47:43 +0000 Received: from [85.158.143.99:48901] by server-2.bemta-4.messagelabs.com id A2/64-24322-E2CFAE05; Mon, 07 Jan 2013 16:47:42 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1357577250!31520201!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTQwNTY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31125 invoked from network); 7 Jan 2013 16:47:32 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2013 16:47:32 -0000 X-IronPort-AV: E=Sophos;i="4.84,424,1355097600"; d="scan'208";a="2898862" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 07 Jan 2013 16:47:30 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Mon, 7 Jan 2013 11:47:30 -0500 Received: from [10.80.3.80] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TsFjN-0008FS-GZ; Mon, 07 Jan 2013 16:39:21 +0000 Message-ID: <1357576754.13581.15.camel@iceland> From: Wei Liu To: Konrad Rzeszutek Wilk Date: Mon, 7 Jan 2013 16:39:14 +0000 In-Reply-To: <20130107162734.GA6402@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> X-Mailer: Evolution 3.6.0-0ubuntu3 MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 07 Jan 2013 17:42:10 +0000 Cc: wei.liu2@citrix.com, "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: > On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > > > > c) Ideally I would like to add biography and interest section for > > > > all our mentors. I can create a wiki template for mentors if it > > > > helps > > Ideas for GSOC: > > - Support microcode update bundled in with the initrd in Xen. > Here is the Linux side of it comes out looking: > http://markmail.org/thread/ewrs7fa66knfwzbo > > - Write Xen PV Architecture Book/Manual/whatever. We have been > slowly going through the PV architecture and documenting it. > It would nice to have somebody full-time doing it and asking > questions. And then the answers would be written in this book. > IIRC the documentation-only project will not be accepted. Wei. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 07 17:42:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 07 Jan 2013 17:42:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsGiB-0008F1-N3; Mon, 07 Jan 2013 17:42:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFrT-0006R7-EA; Mon, 07 Jan 2013 16:47:43 +0000 Received: from [85.158.143.99:48901] by server-2.bemta-4.messagelabs.com id A2/64-24322-E2CFAE05; Mon, 07 Jan 2013 16:47:42 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1357577250!31520201!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTQwNTY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31125 invoked from network); 7 Jan 2013 16:47:32 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2013 16:47:32 -0000 X-IronPort-AV: E=Sophos;i="4.84,424,1355097600"; d="scan'208";a="2898862" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 07 Jan 2013 16:47:30 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Mon, 7 Jan 2013 11:47:30 -0500 Received: from [10.80.3.80] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TsFjN-0008FS-GZ; Mon, 07 Jan 2013 16:39:21 +0000 Message-ID: <1357576754.13581.15.camel@iceland> From: Wei Liu To: Konrad Rzeszutek Wilk Date: Mon, 7 Jan 2013 16:39:14 +0000 In-Reply-To: <20130107162734.GA6402@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> X-Mailer: Evolution 3.6.0-0ubuntu3 MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 07 Jan 2013 17:42:10 +0000 Cc: wei.liu2@citrix.com, "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: > On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > > > > c) Ideally I would like to add biography and interest section for > > > > all our mentors. I can create a wiki template for mentors if it > > > > helps > > Ideas for GSOC: > > - Support microcode update bundled in with the initrd in Xen. > Here is the Linux side of it comes out looking: > http://markmail.org/thread/ewrs7fa66knfwzbo > > - Write Xen PV Architecture Book/Manual/whatever. We have been > slowly going through the PV architecture and documenting it. > It would nice to have somebody full-time doing it and asking > questions. And then the answers would be written in this book. > IIRC the documentation-only project will not be accepted. Wei. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 05:50:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 05:50:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsS4h-0002zx-LP; Tue, 08 Jan 2013 05:50:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsS4g-0002zs-5K for xen-api@lists.xen.org; Tue, 08 Jan 2013 05:50:10 +0000 Received: from [85.158.139.83:63986] by server-3.bemta-5.messagelabs.com id 31/BE-25441-193BBE05; Tue, 08 Jan 2013 05:50:09 +0000 X-Env-Sender: zigo@debian.org X-Msg-Ref: server-12.tower-182.messagelabs.com!1357624207!30528411!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 449 invoked from network); 8 Jan 2013 05:50:08 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-12.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Jan 2013 05:50:08 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 0665FFE465 for ; Tue, 8 Jan 2013 05:53:09 +0000 (UTC) Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 6902CFE452 for ; Tue, 8 Jan 2013 05:53:08 +0000 (UTC) Message-ID: <50EBB38B.6080305@debian.org> Date: Tue, 08 Jan 2013 13:50:03 +0800 From: Thomas Goirand Organization: Debian User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-Enigmail-Version: 1.4.1 Subject: Re: [Xen-API] XCP and opensource cloud options X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 01/05/2013 02:30 AM, Alex Bailey wrote: > Hello everyone > > I am looking into options into implenting a cloud using the latest XCP > release, 6809c, and am well not positive which direction to go, > > There is of course many options, or at least 3 that I have been really > looking at, > > There is openstack, opennubula and of course cloudstack. Opennebula is loosing ground... > > From my understanding, XCP 1.6 was built primarily for cloudstack, and > requires little or no modification to dom0, which is comforting. > > Cloudstack seems to be the optimal choice Optimal because ? > , yet this openstack movement and community is very large, there is > extensive documentation on it, yet it just seems that there may be > "too much" documentation Clearly, no! :) > I see many conflicts with regards to storage options, such as "Swift" > and "cinder" which looks more like "swift vs cinder", there is > conflicts between nova-network and quantum, then there are issue's > with regards There's no conflicts between Swift and Cinder, they are used for different purposes. Swift is an object storage: you store a big blob, and you refer to it with a token (eg: a big random number). Cinder is a network block storage (out of LVM partitions, it creates iSCSI devices which you can mount in the VMs). There is no conflict either between nova-network and Quantum. Quantum is replacing nova-network which is becoming obsolete. Just like nova-volume is being replaced by Cinder. If you are implementing a new cloud, then there is no reason to use nova-network (or nova-volume). > Openstack from my reading needs several modifications to dom0, > including the addition of plugins/packages, which of course is not the > most appealing considering that XCP already has an enormous amount of > possibilities. Installing the plugins is quite easy. I don't understand why copying few files seems to be a problem for you. > I guess my question is, has anyone used any of these solutions? and > what did you think about them? Your input would be immensely appreciated. I used only XCP and Openstack. I had a look at cloudstack, then went away when seeing the way it was packaged (eg: a 3 year old packaging that hasn't been worked on since, and that doesn't even build on Debian or a modern Ubuntu). Though it might be better in CentOS... Thomas _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 05:50:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 05:50:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsS4h-0002zx-LP; Tue, 08 Jan 2013 05:50:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsS4g-0002zs-5K for xen-api@lists.xen.org; Tue, 08 Jan 2013 05:50:10 +0000 Received: from [85.158.139.83:63986] by server-3.bemta-5.messagelabs.com id 31/BE-25441-193BBE05; Tue, 08 Jan 2013 05:50:09 +0000 X-Env-Sender: zigo@debian.org X-Msg-Ref: server-12.tower-182.messagelabs.com!1357624207!30528411!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 449 invoked from network); 8 Jan 2013 05:50:08 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-12.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Jan 2013 05:50:08 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 0665FFE465 for ; Tue, 8 Jan 2013 05:53:09 +0000 (UTC) Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 6902CFE452 for ; Tue, 8 Jan 2013 05:53:08 +0000 (UTC) Message-ID: <50EBB38B.6080305@debian.org> Date: Tue, 08 Jan 2013 13:50:03 +0800 From: Thomas Goirand Organization: Debian User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-Enigmail-Version: 1.4.1 Subject: Re: [Xen-API] XCP and opensource cloud options X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 01/05/2013 02:30 AM, Alex Bailey wrote: > Hello everyone > > I am looking into options into implenting a cloud using the latest XCP > release, 6809c, and am well not positive which direction to go, > > There is of course many options, or at least 3 that I have been really > looking at, > > There is openstack, opennubula and of course cloudstack. Opennebula is loosing ground... > > From my understanding, XCP 1.6 was built primarily for cloudstack, and > requires little or no modification to dom0, which is comforting. > > Cloudstack seems to be the optimal choice Optimal because ? > , yet this openstack movement and community is very large, there is > extensive documentation on it, yet it just seems that there may be > "too much" documentation Clearly, no! :) > I see many conflicts with regards to storage options, such as "Swift" > and "cinder" which looks more like "swift vs cinder", there is > conflicts between nova-network and quantum, then there are issue's > with regards There's no conflicts between Swift and Cinder, they are used for different purposes. Swift is an object storage: you store a big blob, and you refer to it with a token (eg: a big random number). Cinder is a network block storage (out of LVM partitions, it creates iSCSI devices which you can mount in the VMs). There is no conflict either between nova-network and Quantum. Quantum is replacing nova-network which is becoming obsolete. Just like nova-volume is being replaced by Cinder. If you are implementing a new cloud, then there is no reason to use nova-network (or nova-volume). > Openstack from my reading needs several modifications to dom0, > including the addition of plugins/packages, which of course is not the > most appealing considering that XCP already has an enormous amount of > possibilities. Installing the plugins is quite easy. I don't understand why copying few files seems to be a problem for you. > I guess my question is, has anyone used any of these solutions? and > what did you think about them? Your input would be immensely appreciated. I used only XCP and Openstack. I had a look at cloudstack, then went away when seeing the way it was packaged (eg: a 3 year old packaging that hasn't been worked on since, and that doesn't even build on Debian or a modern Ubuntu). Though it might be better in CentOS... Thomas _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 09:25:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 09:25:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsVQZ-0005ym-5u; Tue, 08 Jan 2013 09:24:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsVQY-0005yh-BB for xen-api@lists.xensource.com; Tue, 08 Jan 2013 09:24:58 +0000 Received: from [85.158.143.99:33291] by server-3.bemta-4.messagelabs.com id A6/EC-18211-9E5EBE05; Tue, 08 Jan 2013 09:24:57 +0000 X-Env-Sender: gcex-xen-api@m.gmane.org X-Msg-Ref: server-15.tower-216.messagelabs.com!1357637096!27927839!1 X-Originating-IP: [80.91.229.3] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13327 invoked from network); 8 Jan 2013 09:24:57 -0000 Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by server-15.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 8 Jan 2013 09:24:57 -0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TsVQe-0005ZR-FU for xen-api@lists.xensource.com; Tue, 08 Jan 2013 10:25:04 +0100 Received: from zonafaenza.provincia.ra.it ([195.62.179.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 08 Jan 2013 10:25:04 +0100 Received: from mgiammarco by zonafaenza.provincia.ra.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 08 Jan 2013 10:25:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: xen-api@lists.xensource.com From: Mario Giammarco Date: Tue, 8 Jan 2013 09:21:34 +0000 (UTC) Lines: 12 Message-ID: Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 195.62.179.98 (Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0) Subject: [Xen-API] Xcp does not boot: I need to specify rootdelay X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I am trying xcp on a HP Microserver N40L. I have installed it on USB key. I am not able to boot it because it does not find root. In old kernels like 2.6 used in xcp is quite common this problem and I can fix it with rootdelay=60. But xcp use a "extlinux" bootloader and I cannot try the option. I have found and modified a extlinux.conf file but without luck. How can I pass rootdelay option to the kernel at boot? Thanks, Mario _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 09:25:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 09:25:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsVQZ-0005ym-5u; Tue, 08 Jan 2013 09:24:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsVQY-0005yh-BB for xen-api@lists.xensource.com; Tue, 08 Jan 2013 09:24:58 +0000 Received: from [85.158.143.99:33291] by server-3.bemta-4.messagelabs.com id A6/EC-18211-9E5EBE05; Tue, 08 Jan 2013 09:24:57 +0000 X-Env-Sender: gcex-xen-api@m.gmane.org X-Msg-Ref: server-15.tower-216.messagelabs.com!1357637096!27927839!1 X-Originating-IP: [80.91.229.3] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13327 invoked from network); 8 Jan 2013 09:24:57 -0000 Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by server-15.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 8 Jan 2013 09:24:57 -0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TsVQe-0005ZR-FU for xen-api@lists.xensource.com; Tue, 08 Jan 2013 10:25:04 +0100 Received: from zonafaenza.provincia.ra.it ([195.62.179.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 08 Jan 2013 10:25:04 +0100 Received: from mgiammarco by zonafaenza.provincia.ra.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 08 Jan 2013 10:25:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: xen-api@lists.xensource.com From: Mario Giammarco Date: Tue, 8 Jan 2013 09:21:34 +0000 (UTC) Lines: 12 Message-ID: Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 195.62.179.98 (Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0) Subject: [Xen-API] Xcp does not boot: I need to specify rootdelay X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I am trying xcp on a HP Microserver N40L. I have installed it on USB key. I am not able to boot it because it does not find root. In old kernels like 2.6 used in xcp is quite common this problem and I can fix it with rootdelay=60. But xcp use a "extlinux" bootloader and I cannot try the option. I have found and modified a extlinux.conf file but without luck. How can I pass rootdelay option to the kernel at boot? Thanks, Mario _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 09:57:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 09:57:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsVwI-0006FP-4D; Tue, 08 Jan 2013 09:57:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsVwG-0006FI-8X for xen-api@lists.xen.org; Tue, 08 Jan 2013 09:57:44 +0000 Received: from [193.109.254.147:27265] by server-16.bemta-14.messagelabs.com id ED/80-18932-79DEBE05; Tue, 08 Jan 2013 09:57:43 +0000 X-Env-Sender: yunshandev@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357638957!8613662!1 X-Originating-IP: [209.85.210.54] X-SpamReason: No, hits=0.2 required=7.0 tests=HTML_MESSAGE, MIME_BOUND_NEXTPART,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21776 invoked from network); 8 Jan 2013 09:56:00 -0000 Received: from mail-da0-f54.google.com (HELO mail-da0-f54.google.com) (209.85.210.54) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 09:56:00 -0000 Received: by mail-da0-f54.google.com with SMTP id n2so116638dad.41 for ; Tue, 08 Jan 2013 01:55:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:reply-to:subject:references:x-priority :x-has-attach:x-mailer:mime-version:message-id:content-type; bh=bKJ7M7FYdnJc/uVjzA4PcZ9pBmpW7fT7Op1mGBHaWdk=; b=KzrEs2utT2zTYm2GElWi8quPLDAxzbZJ2qHjBzILQ7ba6BPWJVpv2FHrXM57i7Ch+T bB45ZJatWP159pWR0x4VUZCQw3/Ji2GdJwH33yv4zSamIumm1EWU52r50tFeX0sLWHnH +VHtw2yKR74g4tDZGqW9X8rNzP14Um2yjvU/RkkdaP+GqF4ZfZBnysq/i/Ceg56Xc/ac +iyYzDZ/mJ0IHrwlxCDfEDNiS8MSEhdJGudqzWlVk3zfbOM1XKTkj6XybVlcWyJ5XkzM afxuSg9VZP9Q48/mPR4pfIp0d8gUAkvkE4pi0N2IZh+DTWVohxzTE1IWiJW+WpEisFIt VR7g== X-Received: by 10.68.232.71 with SMTP id tm7mr197746434pbc.118.1357638957442; Tue, 08 Jan 2013 01:55:57 -0800 (PST) Received: from yunshan ([114.255.72.194]) by mx.google.com with ESMTPS id k4sm40473357paz.26.2013.01.08.01.55.50 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 01:55:55 -0800 (PST) Date: Tue, 8 Jan 2013 17:56:23 +0800 From: "Tianpeng Zhang" To: "John Else" , xen-api References: <201212311004494374333@gmail.com> <50E274DA.5010000@gmail.com>, <7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7@LONPMAILBOX01.citrite.net> X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.91[cn] Mime-Version: 1.0 Message-ID: <201301081756164067183@gmail.com> Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: yunshandev List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4088886203958249918==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============4088886203958249918== Content-Type: multipart/alternative; boundary="----=_001_NextPart822681782177_=----" This is a multi-part message in MIME format. ------=_001_NextPart822681782177_=---- Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 VGhhbmtzIEpvaG4uIFRoaXMgaXMgdGhlIHJvb3QgY2F1c2UgYW5kIG1pZ3JhdGlvbiB3b3JrcyBh ZnRlciBDRHMgZWplY3RlZC4NCg0KVGlhbnBlbmcNCg0KRnJvbTogSm9obiBFbHNlDQpEYXRlOiAy MDEzLTAxLTA0IDE5OjU5DQpUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnDQpTdWJqZWN0OiBSZTog W1hlbi1BUEldIFhDUDEuNiBzdG9yYWdlIHhlbm1vdGlvbiBpc3N1ZQ0KSeKAmXZlIG5vdGljZWQg dGhpcyBlcnJvciB3aGVuIHRoZSBndWVzdCBoYXMgYSBDRCBtb3VudGVkIHRoYXQgaXMgbm90IGF2 YWlsYWJsZSB0byB0aGUgZGVzdGluYXRpb24gaG9zdC4gVHJ5IGVqZWN0aW5nIGFsbCBDRHMgZnJv bSB0aGUgZ3Vlc3QgYmVmb3JlIG1pZ3JhdGluZyBpdC4NCiANCkpvaG4NCiANCkZyb206IHhlbi1h cGktYm91bmNlc0BsaXN0cy54ZW4ub3JnIFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhl bi5vcmddIE9uIEJlaGFsZiBPZiBHZW9yZ2UgU2h1a2xpbg0KU2VudDogMDEgSmFudWFyeSAyMDEz IDA1OjMyDQpUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnDQpTdWJqZWN0OiBSZTogW1hlbi1BUEld IFhDUDEuNiBzdG9yYWdlIHhlbm1vdGlvbiBpc3N1ZQ0KIA0KTm90IHlldC4gTXkgdGVzdCBtYWNo aW5lcyBmbHkgYmV0d2VlbiBwb29scyBsaWtlIGEgbWFnaWMuDQoNClBsZWFzZSBwcm92aWRlcyB4 ZW5zb3VyY2UubG9nIHBpZWNlcyBmcm9tIGJvdGggc2lkZXM6IHNlbmRlciBhbmQgcmVjZWl2ZXIu IEkgdGhpbmssIHRoZXkgc2hvdWxkIGJlIHBvb2wncyBtYXN0ZXJzIGxvZ3MuDQoNClBTIERvIG5v dCBmb3JnZXQgdG8gc2V0IHVwIGRlZmF1bHQtc3IgcG9vbCBwcm9wZXJ0eSBvbiByZWNlaXZlci4g DQoNCjMxLjEyLjIwMTIgMDY6MDQsIFRpYW5wZW5nIFpoYW5nINC/0LjRiNC10YI6DQpIaSBBbGws DQogDQpJIGdvdCBvbmUgaXNzdWUgd2l0aCB4Y3AxLjYgd2hlbiB0ZXN0aW5nIFZNIHN0b3JhZ2Ug eGVuTW90aW9uIHRvIGFub3RoZXIgaG9zdC4gSXQgcmVwb3J0ZWQgZXJyb3IgYXMgYW4gImludGVy bmFsIGVycm9yIi4gSGF2ZSBhbnlvbmUgbWV0IHRoaXMgaXNzdWUgYmVmb3JlPyBPciBnaXZlIHNv bWUgdGlwcyBmb3IgdGhpcyBpc3N1ZT8NCiANClRoYW5rcy4gDQogDQpbcm9vdEB4Y3AxMDIgfl0j IHhlIHZtLW1pZ3JhdGUgZGVzdGluYXRpb24tc3ItdXVpZD0yYTllMGNkMC0wZGRmLWI5ZWYtNWUz OC0yZjU3ZTRhYzM2MWUgdm09Q2VudE9TNi1QViByZW1vdGUtbWFzdGVyPTEwLjMzLjIuMTAzIHJl bW90ZS1wYXNzd29yZD1wYXNzd2QgcmVtb3RlLXVzZXJuYW1lPXJvb3QNClBlcmZvcm1pbmcgYSBT dG9yYWdlIFhlbk1vdGlvbiBtaWdyYXRpb24uIFlvdXIgVk0ncyBWRElzIHdpbGwgYmUgbWlncmF0 ZWQgd2l0aCB0aGUgVk0uDQpXaWxsIG1pZ3JhdGUgdG8gcmVtb3RlIGhvc3Q6IHhjcDEwMywgdXNp bmcgcmVtb3RlIG5ldHdvcms6IFBvb2wtd2lkZSBuZXR3b3JrIGFzc29jaWF0ZWQgd2l0aCBldGgw LiBIZXJlIGlzIHRoZSBWREkgbWFwcGluZzoNClZESSBhMDlmYzk1NC1lNWNhLTRlMDItYWJjOS04 NzVhZmE3NjE2ZjggLT4gU1IgMmE5ZTBjZDAtMGRkZi1iOWVmLTVlMzgtMmY1N2U0YWMzNjFlDQpW REkgODRiYzcxMjktYWI5NS00MjRhLWJhMTEtYzhmZjJkMWQ1ZmQ2IC0+IFNSIDJhOWUwY2QwLTBk ZGYtYjllZi01ZTM4LTJmNTdlNGFjMzYxZQ0KVGhlIHNlcnZlciBmYWlsZWQgdG8gaGFuZGxlIHlv dXIgcmVxdWVzdCwgZHVlIHRvIGFuIGludGVybmFsIGVycm9yLiAgVGhlIGdpdmVuIG1lc3NhZ2Ug bWF5IGdpdmUgZGV0YWlscyB1c2VmdWwgZm9yIGRlYnVnZ2luZyB0aGUgcHJvYmxlbS4NCm1lc3Nh Z2U6IEltcG9ydC5JRmFpbHVyZSgyKQ0KW3Jvb3RAeGNwMTAyIH5dIw0KDQoNCg0KDQpfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KWGVuLWFwaSBtYWlsaW5n IGxpc3QNClhlbi1hcGlAbGlzdHMueGVuLm9yZw0KaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJp bi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkNCiA= ------=_001_NextPart822681782177_=---- Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable =EF=BB=BF
Thanks John. This is the root cause and migration works after CDs=20 ejected.
 
Tianpeng
 
From: John Else
Date: 2013-01-04 19:59
Subject: Re: [Xen-API] XCP1.6 storage xenmotion=20 issue

I=E2=80=99ve=20 noticed this error when the guest has a CD mounted that is not available t= o the=20 destination host. Try ejecting all CDs from the guest before migrating=20 it.

 

John

 

From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.= xen.org]=20 On Behalf Of George Shuklin
Sent: 01 January 2013=20 05:32
To: xen-api@lists.xen.org
Subject: Re: [Xen-API]= =20 XCP1.6 storage xenmotion issue

 

Not yet. My test machines fly between pools like a=20 magic.

Please provides xensource.log pieces from both sides: sender= and=20 receiver. I think, they should be pool's masters logs.

PS Do not fo= rget=20 to set up default-sr pool property on receiver.

31.12.2012 06:04,=20 Tianpeng Zhang =D0=BF=D0=B8=D1=88=D0=B5=D1=82:

Hi All,

 

I got one issue with xcp1.6 when testing VM st= orage=20 xenMotion to another host. It reported error as an "internal=20 error". Have anyone met this issue before? Or give some t= ips=20 for this issue?

 

Thanks. 

 

[root@xcp102 ~]# xe vm-migrate des= tination-sr-uuid=3D2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e vm=3DCentOS6-= PV remote-master=3D10.33.2.103 remote-password=3Dpasswd rem= ote-username=3Droot

Performing a Storage XenMotion mig= ration. Your VM's VDIs will be migrated = ;with the VM.

Will migrate to remote host: = xcp103, using remote network: Pool-wide network&n= bsp;associated with eth0. Here is the VDI&nb= sp;mapping:

VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -&g= t; SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e

VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -&g= t; SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e

The server failed to handle y= our request, due to an internal error. =  The given message may give details use= ful for debugging the problem.

message: Import.IFailure(2)

[root@xcp102 ~]#




___________________=
____________________________
Xen-api mailing list
Xen-api@lists.x=
en.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-=
api

 

------=_001_NextPart822681782177_=------ --===============4088886203958249918== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4088886203958249918==-- From xen-api-bounces@lists.xen.org Tue Jan 08 09:57:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 09:57:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsVwI-0006FP-4D; Tue, 08 Jan 2013 09:57:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsVwG-0006FI-8X for xen-api@lists.xen.org; Tue, 08 Jan 2013 09:57:44 +0000 Received: from [193.109.254.147:27265] by server-16.bemta-14.messagelabs.com id ED/80-18932-79DEBE05; Tue, 08 Jan 2013 09:57:43 +0000 X-Env-Sender: yunshandev@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357638957!8613662!1 X-Originating-IP: [209.85.210.54] X-SpamReason: No, hits=0.2 required=7.0 tests=HTML_MESSAGE, MIME_BOUND_NEXTPART,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21776 invoked from network); 8 Jan 2013 09:56:00 -0000 Received: from mail-da0-f54.google.com (HELO mail-da0-f54.google.com) (209.85.210.54) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 09:56:00 -0000 Received: by mail-da0-f54.google.com with SMTP id n2so116638dad.41 for ; Tue, 08 Jan 2013 01:55:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:reply-to:subject:references:x-priority :x-has-attach:x-mailer:mime-version:message-id:content-type; bh=bKJ7M7FYdnJc/uVjzA4PcZ9pBmpW7fT7Op1mGBHaWdk=; b=KzrEs2utT2zTYm2GElWi8quPLDAxzbZJ2qHjBzILQ7ba6BPWJVpv2FHrXM57i7Ch+T bB45ZJatWP159pWR0x4VUZCQw3/Ji2GdJwH33yv4zSamIumm1EWU52r50tFeX0sLWHnH +VHtw2yKR74g4tDZGqW9X8rNzP14Um2yjvU/RkkdaP+GqF4ZfZBnysq/i/Ceg56Xc/ac +iyYzDZ/mJ0IHrwlxCDfEDNiS8MSEhdJGudqzWlVk3zfbOM1XKTkj6XybVlcWyJ5XkzM afxuSg9VZP9Q48/mPR4pfIp0d8gUAkvkE4pi0N2IZh+DTWVohxzTE1IWiJW+WpEisFIt VR7g== X-Received: by 10.68.232.71 with SMTP id tm7mr197746434pbc.118.1357638957442; Tue, 08 Jan 2013 01:55:57 -0800 (PST) Received: from yunshan ([114.255.72.194]) by mx.google.com with ESMTPS id k4sm40473357paz.26.2013.01.08.01.55.50 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 01:55:55 -0800 (PST) Date: Tue, 8 Jan 2013 17:56:23 +0800 From: "Tianpeng Zhang" To: "John Else" , xen-api References: <201212311004494374333@gmail.com> <50E274DA.5010000@gmail.com>, <7EA643C653F17F4C80DE959E978F10EDFBF75AB6A7@LONPMAILBOX01.citrite.net> X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.91[cn] Mime-Version: 1.0 Message-ID: <201301081756164067183@gmail.com> Subject: Re: [Xen-API] XCP1.6 storage xenmotion issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: yunshandev List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4088886203958249918==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============4088886203958249918== Content-Type: multipart/alternative; boundary="----=_001_NextPart822681782177_=----" This is a multi-part message in MIME format. ------=_001_NextPart822681782177_=---- Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 VGhhbmtzIEpvaG4uIFRoaXMgaXMgdGhlIHJvb3QgY2F1c2UgYW5kIG1pZ3JhdGlvbiB3b3JrcyBh ZnRlciBDRHMgZWplY3RlZC4NCg0KVGlhbnBlbmcNCg0KRnJvbTogSm9obiBFbHNlDQpEYXRlOiAy MDEzLTAxLTA0IDE5OjU5DQpUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnDQpTdWJqZWN0OiBSZTog W1hlbi1BUEldIFhDUDEuNiBzdG9yYWdlIHhlbm1vdGlvbiBpc3N1ZQ0KSeKAmXZlIG5vdGljZWQg dGhpcyBlcnJvciB3aGVuIHRoZSBndWVzdCBoYXMgYSBDRCBtb3VudGVkIHRoYXQgaXMgbm90IGF2 YWlsYWJsZSB0byB0aGUgZGVzdGluYXRpb24gaG9zdC4gVHJ5IGVqZWN0aW5nIGFsbCBDRHMgZnJv bSB0aGUgZ3Vlc3QgYmVmb3JlIG1pZ3JhdGluZyBpdC4NCiANCkpvaG4NCiANCkZyb206IHhlbi1h cGktYm91bmNlc0BsaXN0cy54ZW4ub3JnIFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhl bi5vcmddIE9uIEJlaGFsZiBPZiBHZW9yZ2UgU2h1a2xpbg0KU2VudDogMDEgSmFudWFyeSAyMDEz IDA1OjMyDQpUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnDQpTdWJqZWN0OiBSZTogW1hlbi1BUEld IFhDUDEuNiBzdG9yYWdlIHhlbm1vdGlvbiBpc3N1ZQ0KIA0KTm90IHlldC4gTXkgdGVzdCBtYWNo aW5lcyBmbHkgYmV0d2VlbiBwb29scyBsaWtlIGEgbWFnaWMuDQoNClBsZWFzZSBwcm92aWRlcyB4 ZW5zb3VyY2UubG9nIHBpZWNlcyBmcm9tIGJvdGggc2lkZXM6IHNlbmRlciBhbmQgcmVjZWl2ZXIu IEkgdGhpbmssIHRoZXkgc2hvdWxkIGJlIHBvb2wncyBtYXN0ZXJzIGxvZ3MuDQoNClBTIERvIG5v dCBmb3JnZXQgdG8gc2V0IHVwIGRlZmF1bHQtc3IgcG9vbCBwcm9wZXJ0eSBvbiByZWNlaXZlci4g DQoNCjMxLjEyLjIwMTIgMDY6MDQsIFRpYW5wZW5nIFpoYW5nINC/0LjRiNC10YI6DQpIaSBBbGws DQogDQpJIGdvdCBvbmUgaXNzdWUgd2l0aCB4Y3AxLjYgd2hlbiB0ZXN0aW5nIFZNIHN0b3JhZ2Ug eGVuTW90aW9uIHRvIGFub3RoZXIgaG9zdC4gSXQgcmVwb3J0ZWQgZXJyb3IgYXMgYW4gImludGVy bmFsIGVycm9yIi4gSGF2ZSBhbnlvbmUgbWV0IHRoaXMgaXNzdWUgYmVmb3JlPyBPciBnaXZlIHNv bWUgdGlwcyBmb3IgdGhpcyBpc3N1ZT8NCiANClRoYW5rcy4gDQogDQpbcm9vdEB4Y3AxMDIgfl0j IHhlIHZtLW1pZ3JhdGUgZGVzdGluYXRpb24tc3ItdXVpZD0yYTllMGNkMC0wZGRmLWI5ZWYtNWUz OC0yZjU3ZTRhYzM2MWUgdm09Q2VudE9TNi1QViByZW1vdGUtbWFzdGVyPTEwLjMzLjIuMTAzIHJl bW90ZS1wYXNzd29yZD1wYXNzd2QgcmVtb3RlLXVzZXJuYW1lPXJvb3QNClBlcmZvcm1pbmcgYSBT dG9yYWdlIFhlbk1vdGlvbiBtaWdyYXRpb24uIFlvdXIgVk0ncyBWRElzIHdpbGwgYmUgbWlncmF0 ZWQgd2l0aCB0aGUgVk0uDQpXaWxsIG1pZ3JhdGUgdG8gcmVtb3RlIGhvc3Q6IHhjcDEwMywgdXNp bmcgcmVtb3RlIG5ldHdvcms6IFBvb2wtd2lkZSBuZXR3b3JrIGFzc29jaWF0ZWQgd2l0aCBldGgw LiBIZXJlIGlzIHRoZSBWREkgbWFwcGluZzoNClZESSBhMDlmYzk1NC1lNWNhLTRlMDItYWJjOS04 NzVhZmE3NjE2ZjggLT4gU1IgMmE5ZTBjZDAtMGRkZi1iOWVmLTVlMzgtMmY1N2U0YWMzNjFlDQpW REkgODRiYzcxMjktYWI5NS00MjRhLWJhMTEtYzhmZjJkMWQ1ZmQ2IC0+IFNSIDJhOWUwY2QwLTBk ZGYtYjllZi01ZTM4LTJmNTdlNGFjMzYxZQ0KVGhlIHNlcnZlciBmYWlsZWQgdG8gaGFuZGxlIHlv dXIgcmVxdWVzdCwgZHVlIHRvIGFuIGludGVybmFsIGVycm9yLiAgVGhlIGdpdmVuIG1lc3NhZ2Ug bWF5IGdpdmUgZGV0YWlscyB1c2VmdWwgZm9yIGRlYnVnZ2luZyB0aGUgcHJvYmxlbS4NCm1lc3Nh Z2U6IEltcG9ydC5JRmFpbHVyZSgyKQ0KW3Jvb3RAeGNwMTAyIH5dIw0KDQoNCg0KDQpfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KWGVuLWFwaSBtYWlsaW5n IGxpc3QNClhlbi1hcGlAbGlzdHMueGVuLm9yZw0KaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJp bi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkNCiA= ------=_001_NextPart822681782177_=---- Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable =EF=BB=BF
Thanks John. This is the root cause and migration works after CDs=20 ejected.
 
Tianpeng
 
From: John Else
Date: 2013-01-04 19:59
Subject: Re: [Xen-API] XCP1.6 storage xenmotion=20 issue

I=E2=80=99ve=20 noticed this error when the guest has a CD mounted that is not available t= o the=20 destination host. Try ejecting all CDs from the guest before migrating=20 it.

 

John

 

From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.= xen.org]=20 On Behalf Of George Shuklin
Sent: 01 January 2013=20 05:32
To: xen-api@lists.xen.org
Subject: Re: [Xen-API]= =20 XCP1.6 storage xenmotion issue

 

Not yet. My test machines fly between pools like a=20 magic.

Please provides xensource.log pieces from both sides: sender= and=20 receiver. I think, they should be pool's masters logs.

PS Do not fo= rget=20 to set up default-sr pool property on receiver.

31.12.2012 06:04,=20 Tianpeng Zhang =D0=BF=D0=B8=D1=88=D0=B5=D1=82:

Hi All,

 

I got one issue with xcp1.6 when testing VM st= orage=20 xenMotion to another host. It reported error as an "internal=20 error". Have anyone met this issue before? Or give some t= ips=20 for this issue?

 

Thanks. 

 

[root@xcp102 ~]# xe vm-migrate des= tination-sr-uuid=3D2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e vm=3DCentOS6-= PV remote-master=3D10.33.2.103 remote-password=3Dpasswd rem= ote-username=3Droot

Performing a Storage XenMotion mig= ration. Your VM's VDIs will be migrated = ;with the VM.

Will migrate to remote host: = xcp103, using remote network: Pool-wide network&n= bsp;associated with eth0. Here is the VDI&nb= sp;mapping:

VDI a09fc954-e5ca-4e02-abc9-875afa7616f8 -&g= t; SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e

VDI 84bc7129-ab95-424a-ba11-c8ff2d1d5fd6 -&g= t; SR 2a9e0cd0-0ddf-b9ef-5e38-2f57e4ac361e

The server failed to handle y= our request, due to an internal error. =  The given message may give details use= ful for debugging the problem.

message: Import.IFailure(2)

[root@xcp102 ~]#




___________________=
____________________________
Xen-api mailing list
Xen-api@lists.x=
en.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-=
api

 

------=_001_NextPart822681782177_=------ --===============4088886203958249918== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4088886203958249918==-- From xen-api-bounces@lists.xen.org Tue Jan 08 10:24:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 10:24:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsWM8-0006q8-4q; Tue, 08 Jan 2013 10:24:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsWM6-0006q3-Ff for xen-api@lists.xen.org; Tue, 08 Jan 2013 10:24:26 +0000 Received: from [85.158.143.35:10671] by server-3.bemta-4.messagelabs.com id 38/63-18211-9D3FBE05; Tue, 08 Jan 2013 10:24:25 +0000 X-Env-Sender: yunshandev@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1357640661!15745734!1 X-Originating-IP: [209.85.220.48] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MIME_BASE64_TEXT,MIME_BOUND_NEXTPART,ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 973 invoked from network); 8 Jan 2013 10:24:22 -0000 Received: from mail-pa0-f48.google.com (HELO mail-pa0-f48.google.com) (209.85.220.48) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 10:24:22 -0000 Received: by mail-pa0-f48.google.com with SMTP id fa1so250580pad.35 for ; Tue, 08 Jan 2013 02:24:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:reply-to:subject:x-priority:x-has-attach :x-mailer:mime-version:message-id:content-type; bh=d96wPPxcJK906NEtksoWYtfwVRPknNk6Y/R8qbiGNmI=; b=Fh8NLexLBW3nV0RbnvBkJ+mJrS5maVJUb19mOAH5EdyCzFdfthKSjDhWlW1Jyo1LZx uoqZhsIrqqNo1II8mFzhbTQszD0GDrZfYALZa+GApEXCp+NUpubdWfjQnLWlS7A8lkym wS1UK2h6AcA40mOoNCa/Ldx+fuCpmtRCN5xCZMSoLm3rXqvJiVA7nsq5TpEaaBpXBJFw s7u/s/rxLmeathWIOfrxxWrT56nGQDVeuRumdso6T0C0m/xKYoLVAvjocEO6UMrxqNPL c2+vjuwdwVtSfTWcAB2IrNcW6mscBiUE4KsXuzO4vbt6S72TwKUSWnjBaNZ0yrD+aHYV tlRg== X-Received: by 10.68.235.2 with SMTP id ui2mr196378784pbc.163.1357640660580; Tue, 08 Jan 2013 02:24:20 -0800 (PST) Received: from yunshan ([114.255.72.194]) by mx.google.com with ESMTPS id i1sm40510423pav.35.2013.01.08.02.24.15 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 02:24:18 -0800 (PST) Date: Tue, 8 Jan 2013 18:24:48 +0800 From: "Tianpeng Zhang" To: xen-api X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.91[cn] Mime-Version: 1.0 Message-ID: <2013010818244362552713@gmail.com> Subject: [Xen-API] How to do incremental VM backup in remote server? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: yunshandev List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3195630166776533099==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3195630166776533099== Content-Type: multipart/alternative; boundary="----=_001_NextPart588776626146_=----" This is a multi-part message in MIME format. ------=_001_NextPart588776626146_=---- Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGkgQWxsLA0KDQpJJ2QgbGlrZSB0byBiYWNrdXAgVk1zIGluIGFjdGl2ZSBzZXJ2ZXIgdG8gb3Ro ZXIgYmFja3VwIHNlcnZlciBpbiBjYXNlIG9mIHRoZSBhY3RpdmUgc2VydmVyIGZhaWx1cmUgc3Vk ZGVubHkuIEV4cG9ydCB0aGUgVk0gdG8gYSAueHZhIGZpbGUgYW5kIGltcG9ydCBpdCBiYWNrdXAg c2VydmVyIHdvcmtzLCBidXQgaXQgdGFrZXMgdG9vIG11Y2ggdGltZSB3aGVuIFZESSBpcyBxdWl0 ZSBsYXJnZS4gRm9sbG93aW5nIGlzIHRoZSBzb2x1dGlvbiBJIGFtIHRyeWluZyB0byBkbzoNCg0K MS4gZXhwb3J0IFZNJ3MgbWV0YWRhdGEgZmlsZSB0byBiYWNrdXAgc2VydmVyLg0KMi4gY29weSB0 aGUgcmVsYXRlZCBWSERzIG9mIHRoZSBWTSB0byBiYWNrdXAgc2VydmVyLg0KMy4gcGVyaW9kaWNh bGx5IGRvIFZNIHNuYXBzaG90IGluIGFjdGl2ZSBzZXJ2ZXIgYW5kIGNvcHkgdGhlIHNuYXBzaG90 IHRvIHBlZXIgbm9kZS4gKHNuYXBzaG90IGZpbGUgaXMgbXVjaCBzbWFsbGVyLCBhbmQgZWFzeSBm b3IgaW5jcmVtZW50YWwgYmFja3VwKQ0KNC4gd2hlbiBhY3RpdmUgc2VydmVyIGZhaWx1cmUsIHJl c3RvcmUgdGhlIFZNIGJ5IG1ldGFkYXRhIGZpbGUgYW5kIFZIRHMuDQoNCldpdGhvdXQgc25hcHNo b3QsIHdlIGNhbiBpbXBvcnQgVk0gc3VjY2Vzc2Z1bGx5IGJ5IG1ldGFkYXRhIGFuZCBWSEQgZnJv bSBiYWNrdXAgc2VydmVyKGRvIHNvbWUgY2hhbmdlIGluIG1ldGFkYXRhIGZpbGUpLiBCdXQgdm0t aW1wb3J0IGNhbid0IHJlc3RvcmUgY29ycmVjdGx5IGlmIEkgY29waWVkIHNuYXBzaG90IFZIRHMg dG8gYmFja3VwIHNlcnZlci4gDQoNCltyb290QHhjcDEwMiB+XSMgeGUgdm0taW1wb3J0IGZpbGVu YW1lPS9yb290L2NlbnRvczEtc25hcC5tZXRhIHNyLXV1aWQ9NTQzOTRmNTgtZDY0OS05ZTRlLThm NzUtMzNkMzY5ODA0YTBlIA0KVGhlIFZNIGNvdWxkIG5vdCBiZSBpbXBvcnRlZC4NCm1zZzogSU5U RVJOQUxfRVJST1I6IFsgVGFyLkhlYWRlci5FbmRfb2Zfc3RyZWFtIF0NCltyb290QHhjcDEwMiB+ XSMgDQoNCkNhbiBzb21lb25lIGdpdmUgc29tZSBoZWxwIG9uIHRoaXM/IEkgYW0gbm90IHN1cmUg aWYgdGhpcyBpcyBhIHByb3BlciB3YXkgZm9yIGluY3JlbWVudGFsIGJhY2t1cC4NCg0KVGhhbmtz LA0KVGlhbnBlbmcNCiAg ------=_001_NextPart588776626146_=---- Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
Hi All,
 
I'd like to backup VMs in active server to = other=20 backup server in case of the active server failure suddenly. Exp= ort=20 the VM to a .xva file and import it backup server works, but it = takes=20 too much time when VDI is quite large. Following is the solution= I am=20 trying to do:
 
1. export VM's metadata file to backup server.
2. copy the related VHDs of the VM to backup server.
3. periodically do VM snapshot in active server and copy the sn= apshot=20 to peer node. (snapshot file is much smaller, and easy for incremental=20 backup)
4. when active server failure, restore the VM by metadata file = and=20 VHDs.
 
Without snapshot, we can import VM successfully by metadata and= VHD=20 from backup server(do some change in metadata file). But vm-import can't r= estore=20 correctly if I copied snapshot VHDs to backup server.
 
[root@xcp102 ~]# xe vm-import filename=3D/root/ce= ntos1-snap.meta sr-uuid=3D54394f58-d649-9e4e-8f75-33d369804a0e <= /DIV>
The VM could not be imported.
msg: INTERNAL_ERROR: [ Tar.Header.End_of_stream ]=
[root@xcp102 ~]# 
 
Can someone give some help on this? I am not sure if this is a = proper=20 way for incremental backup.
 
Thanks,
Tianpeng
 
------=_001_NextPart588776626146_=------ --===============3195630166776533099== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3195630166776533099==-- From xen-api-bounces@lists.xen.org Tue Jan 08 10:24:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 10:24:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsWM8-0006q8-4q; Tue, 08 Jan 2013 10:24:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsWM6-0006q3-Ff for xen-api@lists.xen.org; Tue, 08 Jan 2013 10:24:26 +0000 Received: from [85.158.143.35:10671] by server-3.bemta-4.messagelabs.com id 38/63-18211-9D3FBE05; Tue, 08 Jan 2013 10:24:25 +0000 X-Env-Sender: yunshandev@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1357640661!15745734!1 X-Originating-IP: [209.85.220.48] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MIME_BASE64_TEXT,MIME_BOUND_NEXTPART,ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 973 invoked from network); 8 Jan 2013 10:24:22 -0000 Received: from mail-pa0-f48.google.com (HELO mail-pa0-f48.google.com) (209.85.220.48) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 10:24:22 -0000 Received: by mail-pa0-f48.google.com with SMTP id fa1so250580pad.35 for ; Tue, 08 Jan 2013 02:24:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:reply-to:subject:x-priority:x-has-attach :x-mailer:mime-version:message-id:content-type; bh=d96wPPxcJK906NEtksoWYtfwVRPknNk6Y/R8qbiGNmI=; b=Fh8NLexLBW3nV0RbnvBkJ+mJrS5maVJUb19mOAH5EdyCzFdfthKSjDhWlW1Jyo1LZx uoqZhsIrqqNo1II8mFzhbTQszD0GDrZfYALZa+GApEXCp+NUpubdWfjQnLWlS7A8lkym wS1UK2h6AcA40mOoNCa/Ldx+fuCpmtRCN5xCZMSoLm3rXqvJiVA7nsq5TpEaaBpXBJFw s7u/s/rxLmeathWIOfrxxWrT56nGQDVeuRumdso6T0C0m/xKYoLVAvjocEO6UMrxqNPL c2+vjuwdwVtSfTWcAB2IrNcW6mscBiUE4KsXuzO4vbt6S72TwKUSWnjBaNZ0yrD+aHYV tlRg== X-Received: by 10.68.235.2 with SMTP id ui2mr196378784pbc.163.1357640660580; Tue, 08 Jan 2013 02:24:20 -0800 (PST) Received: from yunshan ([114.255.72.194]) by mx.google.com with ESMTPS id i1sm40510423pav.35.2013.01.08.02.24.15 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 02:24:18 -0800 (PST) Date: Tue, 8 Jan 2013 18:24:48 +0800 From: "Tianpeng Zhang" To: xen-api X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.91[cn] Mime-Version: 1.0 Message-ID: <2013010818244362552713@gmail.com> Subject: [Xen-API] How to do incremental VM backup in remote server? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: yunshandev List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3195630166776533099==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3195630166776533099== Content-Type: multipart/alternative; boundary="----=_001_NextPart588776626146_=----" This is a multi-part message in MIME format. ------=_001_NextPart588776626146_=---- Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGkgQWxsLA0KDQpJJ2QgbGlrZSB0byBiYWNrdXAgVk1zIGluIGFjdGl2ZSBzZXJ2ZXIgdG8gb3Ro ZXIgYmFja3VwIHNlcnZlciBpbiBjYXNlIG9mIHRoZSBhY3RpdmUgc2VydmVyIGZhaWx1cmUgc3Vk ZGVubHkuIEV4cG9ydCB0aGUgVk0gdG8gYSAueHZhIGZpbGUgYW5kIGltcG9ydCBpdCBiYWNrdXAg c2VydmVyIHdvcmtzLCBidXQgaXQgdGFrZXMgdG9vIG11Y2ggdGltZSB3aGVuIFZESSBpcyBxdWl0 ZSBsYXJnZS4gRm9sbG93aW5nIGlzIHRoZSBzb2x1dGlvbiBJIGFtIHRyeWluZyB0byBkbzoNCg0K MS4gZXhwb3J0IFZNJ3MgbWV0YWRhdGEgZmlsZSB0byBiYWNrdXAgc2VydmVyLg0KMi4gY29weSB0 aGUgcmVsYXRlZCBWSERzIG9mIHRoZSBWTSB0byBiYWNrdXAgc2VydmVyLg0KMy4gcGVyaW9kaWNh bGx5IGRvIFZNIHNuYXBzaG90IGluIGFjdGl2ZSBzZXJ2ZXIgYW5kIGNvcHkgdGhlIHNuYXBzaG90 IHRvIHBlZXIgbm9kZS4gKHNuYXBzaG90IGZpbGUgaXMgbXVjaCBzbWFsbGVyLCBhbmQgZWFzeSBm b3IgaW5jcmVtZW50YWwgYmFja3VwKQ0KNC4gd2hlbiBhY3RpdmUgc2VydmVyIGZhaWx1cmUsIHJl c3RvcmUgdGhlIFZNIGJ5IG1ldGFkYXRhIGZpbGUgYW5kIFZIRHMuDQoNCldpdGhvdXQgc25hcHNo b3QsIHdlIGNhbiBpbXBvcnQgVk0gc3VjY2Vzc2Z1bGx5IGJ5IG1ldGFkYXRhIGFuZCBWSEQgZnJv bSBiYWNrdXAgc2VydmVyKGRvIHNvbWUgY2hhbmdlIGluIG1ldGFkYXRhIGZpbGUpLiBCdXQgdm0t aW1wb3J0IGNhbid0IHJlc3RvcmUgY29ycmVjdGx5IGlmIEkgY29waWVkIHNuYXBzaG90IFZIRHMg dG8gYmFja3VwIHNlcnZlci4gDQoNCltyb290QHhjcDEwMiB+XSMgeGUgdm0taW1wb3J0IGZpbGVu YW1lPS9yb290L2NlbnRvczEtc25hcC5tZXRhIHNyLXV1aWQ9NTQzOTRmNTgtZDY0OS05ZTRlLThm NzUtMzNkMzY5ODA0YTBlIA0KVGhlIFZNIGNvdWxkIG5vdCBiZSBpbXBvcnRlZC4NCm1zZzogSU5U RVJOQUxfRVJST1I6IFsgVGFyLkhlYWRlci5FbmRfb2Zfc3RyZWFtIF0NCltyb290QHhjcDEwMiB+ XSMgDQoNCkNhbiBzb21lb25lIGdpdmUgc29tZSBoZWxwIG9uIHRoaXM/IEkgYW0gbm90IHN1cmUg aWYgdGhpcyBpcyBhIHByb3BlciB3YXkgZm9yIGluY3JlbWVudGFsIGJhY2t1cC4NCg0KVGhhbmtz LA0KVGlhbnBlbmcNCiAg ------=_001_NextPart588776626146_=---- Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
Hi All,
 
I'd like to backup VMs in active server to = other=20 backup server in case of the active server failure suddenly. Exp= ort=20 the VM to a .xva file and import it backup server works, but it = takes=20 too much time when VDI is quite large. Following is the solution= I am=20 trying to do:
 
1. export VM's metadata file to backup server.
2. copy the related VHDs of the VM to backup server.
3. periodically do VM snapshot in active server and copy the sn= apshot=20 to peer node. (snapshot file is much smaller, and easy for incremental=20 backup)
4. when active server failure, restore the VM by metadata file = and=20 VHDs.
 
Without snapshot, we can import VM successfully by metadata and= VHD=20 from backup server(do some change in metadata file). But vm-import can't r= estore=20 correctly if I copied snapshot VHDs to backup server.
 
[root@xcp102 ~]# xe vm-import filename=3D/root/ce= ntos1-snap.meta sr-uuid=3D54394f58-d649-9e4e-8f75-33d369804a0e <= /DIV>
The VM could not be imported.
msg: INTERNAL_ERROR: [ Tar.Header.End_of_stream ]=
[root@xcp102 ~]# 
 
Can someone give some help on this? I am not sure if this is a = proper=20 way for incremental backup.
 
Thanks,
Tianpeng
 
------=_001_NextPart588776626146_=------ --===============3195630166776533099== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3195630166776533099==-- From xen-api-bounces@lists.xen.org Tue Jan 08 11:06:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 11:06:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsX0N-0007LR-48; Tue, 08 Jan 2013 11:06:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsX0K-0007LK-GN for xen-api@lists.xen.org; Tue, 08 Jan 2013 11:06:00 +0000 Received: from [85.158.139.83:53169] by server-4.bemta-5.messagelabs.com id 0E/FA-14693-79DFBE05; Tue, 08 Jan 2013 11:05:59 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1357643150!25445640!1 X-Originating-IP: [207.126.144.113] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18318 invoked from network); 8 Jan 2013 11:05:58 -0000 Received: from eu1sys200aog102.obsmtp.com (HELO eu1sys200aog102.obsmtp.com) (207.126.144.113) by server-11.tower-182.messagelabs.com with SMTP; 8 Jan 2013 11:05:58 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob102.postini.com ([207.126.147.11]) with SMTP ID DSNKUOv9eMtb/fosVP6Pp2ok9B9t13XFfLM9@postini.com; Tue, 08 Jan 2013 11:05:52 UTC Received: from batwexhtca01.uk.futurenet.com (batwexhtca01.uk.futurenet.com [172.23.130.3]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 48C177F4493; Tue, 8 Jan 2013 11:05:23 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by batwexhtca01 ([172.23.130.3]) with mapi; Tue, 8 Jan 2013 11:05:23 +0000 From: Dave Avent To: "<2rushikeshj@gmail.com> <2rushikeshj@gmail.com>" <2rushikeshj@gmail.com> Date: Tue, 8 Jan 2013 11:05:21 +0000 Thread-Topic: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3tkA25K3c6+lBeQZuYqaU6m5SwQg== Message-ID: <10576A57-638E-4F95-B836-48B69C795F8B@futurenet.com> References: <50e57619.4553420a.529d.ffffadbd@mx.google.com> <64828C22-43AE-40EA-B809-79BC801AB69F@futurenet.com> In-Reply-To: <64828C22-43AE-40EA-B809-79BC801AB69F@futurenet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org After more investigation and with the help of tcpdump, I have tracked the problem down to being ACKs not being received by the client. By flushing the iptables rules (i.e. iptables -F) this problem magically goes away. Dave On 7 Jan 2013, at 14:22, Dave Avent wrote: > > On 3 Jan 2013, at 11:54, <2rushikeshj@gmail.com> <2rushikeshj@gmail.com> wrote: > >> >> On Thu, 3 Jan 2013 16:44:14 +0550, xen-api-bounces@lists.xen.org wrote: >>> All, >>> >>> I have been playing with Xen Cloud Platform 1.6 in the lab and have been noticing some strange behaviour when using the API to drive it. Using XenCenter worked some of the time but then appeared to freeze, not refresh and then on re-connecting get stuck on "Synchronising". I put this down to the client software and switched instead to writing my own client interface using Ruby and the FOG libraries. This worked well but I started seeing the same lock-ups. After digging about I realised that it always locks up at the same point namely the VM.get_all_records call. >>> >>> The call is received as the xensource.log shows: >>> >>> xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records D:7f14fc2bea45|api_readonly] VM.get_all_records >>> >>> But nothing is received and the clients TCP connection times out. >>> >>> This problem happens for well over 50% of the calls made to the API so I am interested to know if anyone else is having this problem? >>> >> >> Your Cluster Host Count and VM count ( ON & OFF ) will be helpful. > > 0. This is a vanilla, out-of-the box, ISO install of XCP 1.6 > >> >> Usual errors are to be checked in xensource.log, messages, kern.log > > No errors in any logs. > >> >> Try to get only list of VM ids and then do a get_record for each VM to see if you get caught in same problem > > As mentioned, no VMs. Just pre-installed Templates. > >> >> >> >>> Regards, >>> >>> Dave-- >>> Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. >>> >>> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. >>> >>> The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. >>> >>> Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. >>> >>> ***** >>> Save resources: think before you print. >>> >>> >>> _______________________________________________ >>> Xen-api mailing list >>> Xen-api@lists.xen.org >>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> > > -- > Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. > > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. > > The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. > > Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. > > ***** > Save resources: think before you print. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api -- Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 11:06:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 11:06:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsX0N-0007LR-48; Tue, 08 Jan 2013 11:06:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsX0K-0007LK-GN for xen-api@lists.xen.org; Tue, 08 Jan 2013 11:06:00 +0000 Received: from [85.158.139.83:53169] by server-4.bemta-5.messagelabs.com id 0E/FA-14693-79DFBE05; Tue, 08 Jan 2013 11:05:59 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1357643150!25445640!1 X-Originating-IP: [207.126.144.113] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18318 invoked from network); 8 Jan 2013 11:05:58 -0000 Received: from eu1sys200aog102.obsmtp.com (HELO eu1sys200aog102.obsmtp.com) (207.126.144.113) by server-11.tower-182.messagelabs.com with SMTP; 8 Jan 2013 11:05:58 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob102.postini.com ([207.126.147.11]) with SMTP ID DSNKUOv9eMtb/fosVP6Pp2ok9B9t13XFfLM9@postini.com; Tue, 08 Jan 2013 11:05:52 UTC Received: from batwexhtca01.uk.futurenet.com (batwexhtca01.uk.futurenet.com [172.23.130.3]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 48C177F4493; Tue, 8 Jan 2013 11:05:23 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by batwexhtca01 ([172.23.130.3]) with mapi; Tue, 8 Jan 2013 11:05:23 +0000 From: Dave Avent To: "<2rushikeshj@gmail.com> <2rushikeshj@gmail.com>" <2rushikeshj@gmail.com> Date: Tue, 8 Jan 2013 11:05:21 +0000 Thread-Topic: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging Thread-Index: Ac3tkA25K3c6+lBeQZuYqaU6m5SwQg== Message-ID: <10576A57-638E-4F95-B836-48B69C795F8B@futurenet.com> References: <50e57619.4553420a.529d.ffffadbd@mx.google.com> <64828C22-43AE-40EA-B809-79BC801AB69F@futurenet.com> In-Reply-To: <64828C22-43AE-40EA-B809-79BC801AB69F@futurenet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org After more investigation and with the help of tcpdump, I have tracked the problem down to being ACKs not being received by the client. By flushing the iptables rules (i.e. iptables -F) this problem magically goes away. Dave On 7 Jan 2013, at 14:22, Dave Avent wrote: > > On 3 Jan 2013, at 11:54, <2rushikeshj@gmail.com> <2rushikeshj@gmail.com> wrote: > >> >> On Thu, 3 Jan 2013 16:44:14 +0550, xen-api-bounces@lists.xen.org wrote: >>> All, >>> >>> I have been playing with Xen Cloud Platform 1.6 in the lab and have been noticing some strange behaviour when using the API to drive it. Using XenCenter worked some of the time but then appeared to freeze, not refresh and then on re-connecting get stuck on "Synchronising". I put this down to the client software and switched instead to writing my own client interface using Ruby and the FOG libraries. This worked well but I started seeing the same lock-ups. After digging about I realised that it always locks up at the same point namely the VM.get_all_records call. >>> >>> The call is received as the xensource.log shows: >>> >>> xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records D:7f14fc2bea45|api_readonly] VM.get_all_records >>> >>> But nothing is received and the clients TCP connection times out. >>> >>> This problem happens for well over 50% of the calls made to the API so I am interested to know if anyone else is having this problem? >>> >> >> Your Cluster Host Count and VM count ( ON & OFF ) will be helpful. > > 0. This is a vanilla, out-of-the box, ISO install of XCP 1.6 > >> >> Usual errors are to be checked in xensource.log, messages, kern.log > > No errors in any logs. > >> >> Try to get only list of VM ids and then do a get_record for each VM to see if you get caught in same problem > > As mentioned, no VMs. Just pre-installed Templates. > >> >> >> >>> Regards, >>> >>> Dave-- >>> Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. >>> >>> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. >>> >>> The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. >>> >>> Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. >>> >>> ***** >>> Save resources: think before you print. >>> >>> >>> _______________________________________________ >>> Xen-api mailing list >>> Xen-api@lists.xen.org >>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> > > -- > Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. > > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. > > The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. > > Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. > > ***** > Save resources: think before you print. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api -- Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 11:16:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 11:16:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsX9z-0007Xc-0L; Tue, 08 Jan 2013 11:15:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsX9x-0007XX-VY for xen-api@lists.xen.org; Tue, 08 Jan 2013 11:15:58 +0000 Received: from [85.158.143.35:2234] by server-3.bemta-4.messagelabs.com id CE/79-18211-DEFFBE05; Tue, 08 Jan 2013 11:15:57 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1357643755!5648991!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1MDI4\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30083 invoked from network); 8 Jan 2013 11:15:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 11:15:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,430,1355097600"; d="scan'208";a="510762" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Jan 2013 11:15:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Tue, 8 Jan 2013 11:15:54 +0000 From: Rob Hoes To: Dave Scott , "xen-api@lists.xen.org" Date: Tue, 8 Jan 2013 11:15:53 +0000 Thread-Topic: running latest dev versions of xenopsd on Debian/Ubuntu Thread-Index: Ac3qkUg0wxSPpNjMT6W0axZdOHbZBAC/g7cg Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF7287A7E@LONPMAILBOX01.citrite.net> References: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Dave, Cool, this is very handy! It is working for me, but I had to do a few more things before I could run a VM following the steps on your wiki page. They are mostly very basic steps, but perhaps it is good to still include them on the wiki for completeness. 1. First of all, I had to install Xen on my Ubuntu machine... ;) I installed the xen-hypervisor-4.1-amd64 package using apt-get, and rebooted. 2. I then needed to enable the virtualisation extensions in the BIOS in order to run the HVM guest. Xenopsd gave a rather misleading "cannot allocate memory" error when this was not the case. 3. I needed to reduce the amount of memory my Ubuntu, so that there is space to run new VMs. I ballooned down dom0 to 2G using 'sudo xl mem-set 0 2000' (my host has 4G of RAM). Directly writing the memory target to xenstore also works: 'sudo xenstore-write /local/domain/0/memory/target 2048000'. You could also add the Xen command line option to set dom0's memory. 4. I finally needed to add some xenstore keys for dom0. I did: sudo xenstore-write /local/domain/0/domid 0 sudo xenstore-write /local/domain/0/name Domain-0 sudo xenstore-write /local/domain/0/vm "hello" I believe that was all! Cheers, Rob > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Dave Scott > Sent: 04 January 2013 3:44 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] running latest dev versions of xenopsd on > Debian/Ubuntu > > Hi, > > I've written a wiki page describing how to build the latest development > version of "xenopsd" (and its dependencies) from source: > > http://wiki.xen.org/wiki/Building_Xenopsd > > "xenopsd" is the name of the domain manager of the XCP toolstack -- it is > responsible for starting, stopping, migrating VMs. > > Being able to build the development version is really useful if you want to: > * check out a new feature > * reproduce a bug > * test a fix > > Let me know if you try this and have any problems or suggestions! > > There are a couple more components of the XCP toolstack that need some > fixups so they can build easily, in particular: > * squeezed: manages memory ballooning > * networkd: configures VM networking > * rrdd: collects and archives performance statistics > * xapi: manages the overall resource pool > > Hopefully we can work on these one-by-one until they are all as easy to > build as xenopsd. > > Cheers, > Dave > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 11:16:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 11:16:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsX9z-0007Xc-0L; Tue, 08 Jan 2013 11:15:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsX9x-0007XX-VY for xen-api@lists.xen.org; Tue, 08 Jan 2013 11:15:58 +0000 Received: from [85.158.143.35:2234] by server-3.bemta-4.messagelabs.com id CE/79-18211-DEFFBE05; Tue, 08 Jan 2013 11:15:57 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1357643755!5648991!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1MDI4\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30083 invoked from network); 8 Jan 2013 11:15:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 11:15:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,430,1355097600"; d="scan'208";a="510762" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Jan 2013 11:15:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Tue, 8 Jan 2013 11:15:54 +0000 From: Rob Hoes To: Dave Scott , "xen-api@lists.xen.org" Date: Tue, 8 Jan 2013 11:15:53 +0000 Thread-Topic: running latest dev versions of xenopsd on Debian/Ubuntu Thread-Index: Ac3qkUg0wxSPpNjMT6W0axZdOHbZBAC/g7cg Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF7287A7E@LONPMAILBOX01.citrite.net> References: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Dave, Cool, this is very handy! It is working for me, but I had to do a few more things before I could run a VM following the steps on your wiki page. They are mostly very basic steps, but perhaps it is good to still include them on the wiki for completeness. 1. First of all, I had to install Xen on my Ubuntu machine... ;) I installed the xen-hypervisor-4.1-amd64 package using apt-get, and rebooted. 2. I then needed to enable the virtualisation extensions in the BIOS in order to run the HVM guest. Xenopsd gave a rather misleading "cannot allocate memory" error when this was not the case. 3. I needed to reduce the amount of memory my Ubuntu, so that there is space to run new VMs. I ballooned down dom0 to 2G using 'sudo xl mem-set 0 2000' (my host has 4G of RAM). Directly writing the memory target to xenstore also works: 'sudo xenstore-write /local/domain/0/memory/target 2048000'. You could also add the Xen command line option to set dom0's memory. 4. I finally needed to add some xenstore keys for dom0. I did: sudo xenstore-write /local/domain/0/domid 0 sudo xenstore-write /local/domain/0/name Domain-0 sudo xenstore-write /local/domain/0/vm "hello" I believe that was all! Cheers, Rob > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Dave Scott > Sent: 04 January 2013 3:44 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] running latest dev versions of xenopsd on > Debian/Ubuntu > > Hi, > > I've written a wiki page describing how to build the latest development > version of "xenopsd" (and its dependencies) from source: > > http://wiki.xen.org/wiki/Building_Xenopsd > > "xenopsd" is the name of the domain manager of the XCP toolstack -- it is > responsible for starting, stopping, migrating VMs. > > Being able to build the development version is really useful if you want to: > * check out a new feature > * reproduce a bug > * test a fix > > Let me know if you try this and have any problems or suggestions! > > There are a couple more components of the XCP toolstack that need some > fixups so they can build easily, in particular: > * squeezed: manages memory ballooning > * networkd: configures VM networking > * rrdd: collects and archives performance statistics > * xapi: manages the overall resource pool > > Hopefully we can work on these one-by-one until they are all as easy to > build as xenopsd. > > Cheers, > Dave > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 12:19:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 12:19:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsY92-00087v-Nd; Tue, 08 Jan 2013 12:19:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsY92-00087k-1g; Tue, 08 Jan 2013 12:19:04 +0000 Received: from [85.158.143.35:38369] by server-2.bemta-4.messagelabs.com id 59/89-24322-7BE0CE05; Tue, 08 Jan 2013 12:19:03 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1357647190!15762041!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2879 invoked from network); 8 Jan 2013 12:13:11 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 12:13:11 -0000 Received: by mail-la0-f42.google.com with SMTP id fe20so360452lab.29 for ; Tue, 08 Jan 2013 04:13:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=pn9Yt0+ToQ772H7f/Tx1ydXbUDQJrj6iPx40vHCtoT4=; b=rl+xpBuW37PXBHwcw7/VhGSqxy8M9gKQWANxloRjsvgBI2hStktDitpZ+RRXidhSjv 1Czb0nV9QCLHmHZNjlyRh7oDFvaGd7fiRmYhtdDq0AMq3meeANanxg2CZ4erxbr/CnyC F5wNKQWI6A+bOaHtvDyMAbS0awxx+l+9djdxvciKcwx3NXdqXRr2RwvbLlDtTtH76GzL LjMtMHze41+VjAz0sO5korXm+YDr/GT35KQR/VswhhaWXw7kgENd9o6lwlqdXzEqcGAr wqQDc6p5eVCgoNfHewA0R7wwlA/az0pOIObDqI/EKFeAGaawPAtMye35I20cB1VE9F1N e3kA== X-Received: by 10.112.40.129 with SMTP id x1mr26710053lbk.95.1357647189574; Tue, 08 Jan 2013 04:13:09 -0800 (PST) Received: from [172.16.26.11] (b0fb35bc.bb.sky.com. [176.251.53.188]) by mx.google.com with ESMTPS id hc20sm24327961lab.11.2013.01.08.04.13.06 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 04:13:08 -0800 (PST) Message-ID: <50EC0D4F.2020703@xen.org> Date: Tue, 08 Jan 2013 12:13:03 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" Subject: [Xen-API] Upcoming CFP deadlines & travel stipends for Xen talks at industry events X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everybody, first I wanted to wish you a Happy New Year. I also wanted to remind you, that I can usually find travel stipends for speakers that talk about Xen at industry and open source events. If you want to submit a Xen related talk and need support with travel, drop me a line to work out details. In particular, I am looking for more Xen user talks and case studies this year. In this spirit, I wanted to share upcoming deadlines: Event: OSCON 2013 Deadline: Feb 2 CFP: http://www.oscon.com/oscon2013/public/cfp/251 Event: Linux Foundation Collaboration Summit Deadline: Feb 4 CFP: http://events.linuxfoundation.org/events/collaboration-summit/cfp Linux Foundation Enterprise User Summit Deadline: Feb 14 CFP: http://events.linuxfoundation.org/events/enterprise-end-user-summit/cfp LinuxCon Japan Deadline: Feb 26 CFP: http://events.linuxfoundation.org/events/linuxcon-japan/cfp Best Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 12:19:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 12:19:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsY92-00087v-Nd; Tue, 08 Jan 2013 12:19:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsY92-00087k-1g; Tue, 08 Jan 2013 12:19:04 +0000 Received: from [85.158.143.35:38369] by server-2.bemta-4.messagelabs.com id 59/89-24322-7BE0CE05; Tue, 08 Jan 2013 12:19:03 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1357647190!15762041!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2879 invoked from network); 8 Jan 2013 12:13:11 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 12:13:11 -0000 Received: by mail-la0-f42.google.com with SMTP id fe20so360452lab.29 for ; Tue, 08 Jan 2013 04:13:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=pn9Yt0+ToQ772H7f/Tx1ydXbUDQJrj6iPx40vHCtoT4=; b=rl+xpBuW37PXBHwcw7/VhGSqxy8M9gKQWANxloRjsvgBI2hStktDitpZ+RRXidhSjv 1Czb0nV9QCLHmHZNjlyRh7oDFvaGd7fiRmYhtdDq0AMq3meeANanxg2CZ4erxbr/CnyC F5wNKQWI6A+bOaHtvDyMAbS0awxx+l+9djdxvciKcwx3NXdqXRr2RwvbLlDtTtH76GzL LjMtMHze41+VjAz0sO5korXm+YDr/GT35KQR/VswhhaWXw7kgENd9o6lwlqdXzEqcGAr wqQDc6p5eVCgoNfHewA0R7wwlA/az0pOIObDqI/EKFeAGaawPAtMye35I20cB1VE9F1N e3kA== X-Received: by 10.112.40.129 with SMTP id x1mr26710053lbk.95.1357647189574; Tue, 08 Jan 2013 04:13:09 -0800 (PST) Received: from [172.16.26.11] (b0fb35bc.bb.sky.com. [176.251.53.188]) by mx.google.com with ESMTPS id hc20sm24327961lab.11.2013.01.08.04.13.06 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 04:13:08 -0800 (PST) Message-ID: <50EC0D4F.2020703@xen.org> Date: Tue, 08 Jan 2013 12:13:03 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" Subject: [Xen-API] Upcoming CFP deadlines & travel stipends for Xen talks at industry events X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everybody, first I wanted to wish you a Happy New Year. I also wanted to remind you, that I can usually find travel stipends for speakers that talk about Xen at industry and open source events. If you want to submit a Xen related talk and need support with travel, drop me a line to work out details. In particular, I am looking for more Xen user talks and case studies this year. In this spirit, I wanted to share upcoming deadlines: Event: OSCON 2013 Deadline: Feb 2 CFP: http://www.oscon.com/oscon2013/public/cfp/251 Event: Linux Foundation Collaboration Summit Deadline: Feb 4 CFP: http://events.linuxfoundation.org/events/collaboration-summit/cfp Linux Foundation Enterprise User Summit Deadline: Feb 14 CFP: http://events.linuxfoundation.org/events/enterprise-end-user-summit/cfp LinuxCon Japan Deadline: Feb 26 CFP: http://events.linuxfoundation.org/events/linuxcon-japan/cfp Best Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 08 18:07:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 18:07:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsdaT-0006tS-Ps; Tue, 08 Jan 2013 18:07:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsdaS-0006tL-Hx for xen-api@lists.xen.org; Tue, 08 Jan 2013 18:07:44 +0000 Received: from [85.158.137.99:38251] by server-5.bemta-3.messagelabs.com id DF/04-04992-F606CE05; Tue, 08 Jan 2013 18:07:43 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1357668462!20044191!1 X-Originating-IP: [209.85.217.169] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6941 invoked from network); 8 Jan 2013 18:07:43 -0000 Received: from mail-lb0-f169.google.com (HELO mail-lb0-f169.google.com) (209.85.217.169) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 18:07:43 -0000 Received: by mail-lb0-f169.google.com with SMTP id gk1so602541lbb.28 for ; Tue, 08 Jan 2013 10:07:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=3kRH+zjhqyiuQ2V5cuP1b1iCpvUjrl1TGhyxyj73Vrs=; b=YUZm5IQv2WSkSphAfOkp51iOTwHIWw7N2IEe3vPNSSAIUtT14hNiX152LZdZvfQ9Jr tQ9LRkgQiVBcYG7eBxYa2zbSJLyFXxc7mR4OCvbF5LJwfcVkbU+rqOGZ+FksGuoj13Iu GMVhN6plz80ioVVHN/3x/3mKHbahBQfiwrGXU+KPoaAzMRX3Da99v4+BupPhZu1BYvTR 2mQPnezEjj3juBTXpOPw0g6IYz02D5P5PEf+hViUx1SGuSv6TaYWkdzaYbVZUFLRF5wB nKgVAWFb1iUyVfE9OOQTt18zV04SBt0kQG4UvMvhJl8qQ4t+zhXm1vbOxxl0fv+GiMwU vCCA== X-Received: by 10.152.123.49 with SMTP id lx17mr10549427lab.52.1357668462232; Tue, 08 Jan 2013 10:07:42 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id ew10sm22964855lbb.10.2013.01.08.10.07.41 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 10:07:41 -0800 (PST) Message-ID: <50EC606C.2070702@gmail.com> Date: Tue, 08 Jan 2013 22:07:40 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> In-Reply-To: <50E7D754.3020703@ondore.com> Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T2ssIGhlcmUgaW1wb3J0YW50IHN0dWZmLiBXaGVuIFZCRCBpcyBwbHVnZ2VkIHRvIGRvbTAsIGl0 IHBsdWdnaW5nIG5vdCAKYXMgJ25vcm1hbCcgZGV2aWNlICh3aXRoIHVkZXYgYXR0ZW50aW9uKSwg YnV0IGFzIGRldmljZSBpbiAvZGV2L3NtL2JhY2tlbmQuCgpIZXJlIHNhbXBsZSBsb2cgKGNoYW5n ZSB1dWlkcyBvbiB5b3UgdGFzdGUpOgoKeGUgdmJkLWNyZWF0ZSB2bS11dWlkPTUzYzNkODc4LWI2 MGItNDhlYy1hYWFjLTczZjdhZGY5YWIzZCAKdmRpLXV1aWQ9NWUyYzMxYTUtMWQxYi00YWJlLTk4 OTItMWZhM2JjNDdiNTMyIGRldmljZT02CnhlIHZiZC1wbHVnIHV1aWQ9NDA3ZWIzYTYtOTE5Zi1m NjA1LTA4ODMtZTEyYWFhOTEzMjFkCgpscyAtbGEgL2Rldi9zbS9iYWNrZW5kLzU1ZWEyMGQyLTg2 MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi8K0LjRgtC+0LPQviA0CmRyd3hyLXhyLXggMiByb290 IHJvb3QgICAgIDgwINCv0L3QsiAgOCAyMTo1NyAuCmRyd3hyLXhyLXggMyByb290IHJvb3QgICAg IDYwINCU0LXQuiAxOCAxNzo0MCAuLgpicnctLS0tLS0tIDEgcm9vdCByb290IDI1MywgMCDQr9C9 0LIgIDggMjE6NTcgCjVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMgotcnctci0t ci0tIDEgcm9vdCByb290ICAgIDg1MiDQr9C90LIgIDggMjE6NTcgCjVlMmMzMWE1LTFkMWItNGFi ZS05ODkyLTFmYTNiYzQ3YjUzMi5hdHRhY2hfaW5mbwoKSSBoYXZlIG5vIGlkZWEgd2h5ICc1NScg dXVpZCAoYW5kIHdoYXQgaXQgbWVhbnMpLCBidXQgCjVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFm YTNiYzQ3YjUzMiBpcyBibG9jayBkZXZpY2UgYWZ0ZXIgd2hvbGUgVkhEIAp0cmVlIGpvaW5pbmcv cGFyc2luZyBhbmQgc28gb24uCgpZb3UgY2FuIHNlZSBhY3R1YWwgcGF0aCBpbiB4ZSB2YmQtbGlz dCBvdXRwdXQgKGRldmljZSBmaWVsZCkuCgowNS4wMS4yMDEzIDExOjMzLCBBbGV4YW5kcmUgS291 em5ldHNvdiDQv9C40YjQtdGCOgo+IEhlbGxvLgo+Cj4gRWwgMDQvMDEvMTMgMjM6MTQsIEdlb3Jn ZSBTaHVrbGluIGVzY3JpYmnDszoKPj4gVXNlIHhlIHZiZC1jcmVhdGUgYmV0d2VlbiB2ZGkgYW5k IGRvbTAgKHdoaWNoIGlzIG5vcm1hbCBWTSBtb3N0bHkpLCBhbmQKPj4geGUgdmJkLXBsdWcuCj4g WWVzLCB0aGF0J3Mgd2hhdCBJIGhhdmUgZG9uZSBmb2xsb3dpbmcgdGhlIGV4YW1wbGUgZnJvbSBD aXRyaXggZm9ydW0uCj4KPiBJbiBjYXNlIG9mIGEgbm9ybWFsIERvbVU6Cj4gSSBjcmVhdGUgVkJE IGxpbmtpbmcgdGhlIFZNIHdpdGggVkRJLAo+IEkgaXNzdWUgdmJkLXBsdWcsCj4gdGhlIGJsb2Nr IGRldmljZSBiZWNvbWVzIHZpc2libGUgaW4gZG1lc2cgdW5kZXIgRG9tVS4KPgo+IEluIGNhc2Ug b2YgRG9tMDoKPiBJIGNyZWF0ZSBWQkQgbGlua2luZyB0aGUgVk0gKHZtLWxpc3QgcmVmZXJzIHRv IGl0IGFzICJDb250cm9sIERvbWFpbiIsIAo+IG5vIG1pc3Rha2UpIHdpdGggVkRJLAo+IEkgaXNz dWUgdmJkLXBsdWcsCj4gbm8gc2lnbiBvZiB0aGUgbmV3IGJsb2NrIGRldmljZSBpbiBkbWVzZyBv ciB1bmRlciAvZGV2Lgo+Cj4+IFlvdSBjYW4gc2VlIHNvbWUgc2FtcGxlIHVzYWdlIGluICd4ZS1l ZGl0LWJvb3Rsb2FkZXInIGNvbW1hbmQgKHNvbWV3aGVyZQo+PiBpbiAvb3B0L3hlbnNvdXJjZS8p Cj4gSG0uIEkgYmVsaWV2ZSBJJ20gZG9pbmcgaXQganVzdCB0aGUgc2FtZSB3YXkgYXMgaW4gdGhl IHNjcmlwdCwgZXhjZXB0IAo+IGJ5IHRoZSAiZGV2aWNlPSIgZGlyZWN0aXZlIGZvciB2YmQtY3Jl YXRlLCB1c2Ugc3BlY2lmaWMgc3RyaW5nIGxpa2UgCj4gInh2ZG4iLgo+IFNob3VsZCBpdCBtYWtl IHRoZSBkaWZmZXJlbmNlPyBDYW4ndCB0ZXN0LCBJIHNob3QgZG93biBteSB0ZXN0aW5nIAo+IHJh bmdlIGJlZm9yZSBsZWF2aW5nIHRoZSBvZmZpY2UuCj4KPiBTbywgbXVzdCBJIHVuZGVyc3RhbmQg dGhhdCB0aGUgWENQJ3MgcmVndWxhciB3YXkgb2YgbWFuaXB1bGF0aW5nIFZESSdzIAo+IGNvbnRl bnRzIGZyb20gd2l0aGluIERvbTAsIGlzIGF0dGFjaGluZyB0aGUgVkRJIHRvIGl0IHZpYSBhIFZC RD8KPiBMb29rcyBsaWtlIGEgZ29vZCBhYnN0cmFjdGlvbiwgZXhjZXB0IHRoYXQgaXQgd29uJ3Qg d29yayB0aGF0IGVhc2lseSAKPiBvbiBhIGhvc3Qgd2l0aG91dCBYQ1AgaW5mcmFzdHJ1Y3R1cmUg KGZvciBleGFtcGxlLCBpbiBzb21lIHJlc2N1ZSAKPiBzY2VuYXJpbykuCj4KPiBUaGVuLCB3aGF0 IHZoZHBhcnR4IGlzIGdvb2QgZm9yPwo+Cj4gQ2hlZXJzLgo+Cj4KPiBfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1hcGkgbWFpbGluZyBsaXN0Cj4g WGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWls bWFuL2xpc3RpbmZvL3hlbi1hcGkKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcK aHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Tue Jan 08 18:07:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 18:07:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsdaT-0006tS-Ps; Tue, 08 Jan 2013 18:07:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsdaS-0006tL-Hx for xen-api@lists.xen.org; Tue, 08 Jan 2013 18:07:44 +0000 Received: from [85.158.137.99:38251] by server-5.bemta-3.messagelabs.com id DF/04-04992-F606CE05; Tue, 08 Jan 2013 18:07:43 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1357668462!20044191!1 X-Originating-IP: [209.85.217.169] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6941 invoked from network); 8 Jan 2013 18:07:43 -0000 Received: from mail-lb0-f169.google.com (HELO mail-lb0-f169.google.com) (209.85.217.169) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 18:07:43 -0000 Received: by mail-lb0-f169.google.com with SMTP id gk1so602541lbb.28 for ; Tue, 08 Jan 2013 10:07:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=3kRH+zjhqyiuQ2V5cuP1b1iCpvUjrl1TGhyxyj73Vrs=; b=YUZm5IQv2WSkSphAfOkp51iOTwHIWw7N2IEe3vPNSSAIUtT14hNiX152LZdZvfQ9Jr tQ9LRkgQiVBcYG7eBxYa2zbSJLyFXxc7mR4OCvbF5LJwfcVkbU+rqOGZ+FksGuoj13Iu GMVhN6plz80ioVVHN/3x/3mKHbahBQfiwrGXU+KPoaAzMRX3Da99v4+BupPhZu1BYvTR 2mQPnezEjj3juBTXpOPw0g6IYz02D5P5PEf+hViUx1SGuSv6TaYWkdzaYbVZUFLRF5wB nKgVAWFb1iUyVfE9OOQTt18zV04SBt0kQG4UvMvhJl8qQ4t+zhXm1vbOxxl0fv+GiMwU vCCA== X-Received: by 10.152.123.49 with SMTP id lx17mr10549427lab.52.1357668462232; Tue, 08 Jan 2013 10:07:42 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id ew10sm22964855lbb.10.2013.01.08.10.07.41 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 10:07:41 -0800 (PST) Message-ID: <50EC606C.2070702@gmail.com> Date: Tue, 08 Jan 2013 22:07:40 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> In-Reply-To: <50E7D754.3020703@ondore.com> Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T2ssIGhlcmUgaW1wb3J0YW50IHN0dWZmLiBXaGVuIFZCRCBpcyBwbHVnZ2VkIHRvIGRvbTAsIGl0 IHBsdWdnaW5nIG5vdCAKYXMgJ25vcm1hbCcgZGV2aWNlICh3aXRoIHVkZXYgYXR0ZW50aW9uKSwg YnV0IGFzIGRldmljZSBpbiAvZGV2L3NtL2JhY2tlbmQuCgpIZXJlIHNhbXBsZSBsb2cgKGNoYW5n ZSB1dWlkcyBvbiB5b3UgdGFzdGUpOgoKeGUgdmJkLWNyZWF0ZSB2bS11dWlkPTUzYzNkODc4LWI2 MGItNDhlYy1hYWFjLTczZjdhZGY5YWIzZCAKdmRpLXV1aWQ9NWUyYzMxYTUtMWQxYi00YWJlLTk4 OTItMWZhM2JjNDdiNTMyIGRldmljZT02CnhlIHZiZC1wbHVnIHV1aWQ9NDA3ZWIzYTYtOTE5Zi1m NjA1LTA4ODMtZTEyYWFhOTEzMjFkCgpscyAtbGEgL2Rldi9zbS9iYWNrZW5kLzU1ZWEyMGQyLTg2 MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi8K0LjRgtC+0LPQviA0CmRyd3hyLXhyLXggMiByb290 IHJvb3QgICAgIDgwINCv0L3QsiAgOCAyMTo1NyAuCmRyd3hyLXhyLXggMyByb290IHJvb3QgICAg IDYwINCU0LXQuiAxOCAxNzo0MCAuLgpicnctLS0tLS0tIDEgcm9vdCByb290IDI1MywgMCDQr9C9 0LIgIDggMjE6NTcgCjVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMgotcnctci0t ci0tIDEgcm9vdCByb290ICAgIDg1MiDQr9C90LIgIDggMjE6NTcgCjVlMmMzMWE1LTFkMWItNGFi ZS05ODkyLTFmYTNiYzQ3YjUzMi5hdHRhY2hfaW5mbwoKSSBoYXZlIG5vIGlkZWEgd2h5ICc1NScg dXVpZCAoYW5kIHdoYXQgaXQgbWVhbnMpLCBidXQgCjVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFm YTNiYzQ3YjUzMiBpcyBibG9jayBkZXZpY2UgYWZ0ZXIgd2hvbGUgVkhEIAp0cmVlIGpvaW5pbmcv cGFyc2luZyBhbmQgc28gb24uCgpZb3UgY2FuIHNlZSBhY3R1YWwgcGF0aCBpbiB4ZSB2YmQtbGlz dCBvdXRwdXQgKGRldmljZSBmaWVsZCkuCgowNS4wMS4yMDEzIDExOjMzLCBBbGV4YW5kcmUgS291 em5ldHNvdiDQv9C40YjQtdGCOgo+IEhlbGxvLgo+Cj4gRWwgMDQvMDEvMTMgMjM6MTQsIEdlb3Jn ZSBTaHVrbGluIGVzY3JpYmnDszoKPj4gVXNlIHhlIHZiZC1jcmVhdGUgYmV0d2VlbiB2ZGkgYW5k IGRvbTAgKHdoaWNoIGlzIG5vcm1hbCBWTSBtb3N0bHkpLCBhbmQKPj4geGUgdmJkLXBsdWcuCj4g WWVzLCB0aGF0J3Mgd2hhdCBJIGhhdmUgZG9uZSBmb2xsb3dpbmcgdGhlIGV4YW1wbGUgZnJvbSBD aXRyaXggZm9ydW0uCj4KPiBJbiBjYXNlIG9mIGEgbm9ybWFsIERvbVU6Cj4gSSBjcmVhdGUgVkJE IGxpbmtpbmcgdGhlIFZNIHdpdGggVkRJLAo+IEkgaXNzdWUgdmJkLXBsdWcsCj4gdGhlIGJsb2Nr IGRldmljZSBiZWNvbWVzIHZpc2libGUgaW4gZG1lc2cgdW5kZXIgRG9tVS4KPgo+IEluIGNhc2Ug b2YgRG9tMDoKPiBJIGNyZWF0ZSBWQkQgbGlua2luZyB0aGUgVk0gKHZtLWxpc3QgcmVmZXJzIHRv IGl0IGFzICJDb250cm9sIERvbWFpbiIsIAo+IG5vIG1pc3Rha2UpIHdpdGggVkRJLAo+IEkgaXNz dWUgdmJkLXBsdWcsCj4gbm8gc2lnbiBvZiB0aGUgbmV3IGJsb2NrIGRldmljZSBpbiBkbWVzZyBv ciB1bmRlciAvZGV2Lgo+Cj4+IFlvdSBjYW4gc2VlIHNvbWUgc2FtcGxlIHVzYWdlIGluICd4ZS1l ZGl0LWJvb3Rsb2FkZXInIGNvbW1hbmQgKHNvbWV3aGVyZQo+PiBpbiAvb3B0L3hlbnNvdXJjZS8p Cj4gSG0uIEkgYmVsaWV2ZSBJJ20gZG9pbmcgaXQganVzdCB0aGUgc2FtZSB3YXkgYXMgaW4gdGhl IHNjcmlwdCwgZXhjZXB0IAo+IGJ5IHRoZSAiZGV2aWNlPSIgZGlyZWN0aXZlIGZvciB2YmQtY3Jl YXRlLCB1c2Ugc3BlY2lmaWMgc3RyaW5nIGxpa2UgCj4gInh2ZG4iLgo+IFNob3VsZCBpdCBtYWtl IHRoZSBkaWZmZXJlbmNlPyBDYW4ndCB0ZXN0LCBJIHNob3QgZG93biBteSB0ZXN0aW5nIAo+IHJh bmdlIGJlZm9yZSBsZWF2aW5nIHRoZSBvZmZpY2UuCj4KPiBTbywgbXVzdCBJIHVuZGVyc3RhbmQg dGhhdCB0aGUgWENQJ3MgcmVndWxhciB3YXkgb2YgbWFuaXB1bGF0aW5nIFZESSdzIAo+IGNvbnRl bnRzIGZyb20gd2l0aGluIERvbTAsIGlzIGF0dGFjaGluZyB0aGUgVkRJIHRvIGl0IHZpYSBhIFZC RD8KPiBMb29rcyBsaWtlIGEgZ29vZCBhYnN0cmFjdGlvbiwgZXhjZXB0IHRoYXQgaXQgd29uJ3Qg d29yayB0aGF0IGVhc2lseSAKPiBvbiBhIGhvc3Qgd2l0aG91dCBYQ1AgaW5mcmFzdHJ1Y3R1cmUg KGZvciBleGFtcGxlLCBpbiBzb21lIHJlc2N1ZSAKPiBzY2VuYXJpbykuCj4KPiBUaGVuLCB3aGF0 IHZoZHBhcnR4IGlzIGdvb2QgZm9yPwo+Cj4gQ2hlZXJzLgo+Cj4KPiBfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1hcGkgbWFpbGluZyBsaXN0Cj4g WGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWls bWFuL2xpc3RpbmZvL3hlbi1hcGkKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcK aHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Tue Jan 08 18:29:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 18:29:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsdvk-00075d-NH; Tue, 08 Jan 2013 18:29:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsdvj-00075Y-8X for xen-api@lists.xen.org; Tue, 08 Jan 2013 18:29:43 +0000 Received: from [85.158.138.51:47635] by server-5.bemta-3.messagelabs.com id F1/F4-04992-6956CE05; Tue, 08 Jan 2013 18:29:42 +0000 X-Env-Sender: jhom@softlayer.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1357669780!23799376!1 X-Originating-IP: [173.192.119.25] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8766 invoked from network); 8 Jan 2013 18:29:41 -0000 Received: from mx151.softlayer.com (HELO mx.softlayer.com) (173.192.119.25) by server-6.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Jan 2013 18:29:41 -0000 Received: from mail.softlayer.com by mx.softlayer.com with esmtp (Exim) (envelope-from ) id 1Tsdvf-000K9A-BC; Tue, 08 Jan 2013 12:29:39 -0600 Received: from SM-CAS151.softlayer.local (172.18.18.38) by SM-TMG151.softlayer.local (172.18.18.50) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 8 Jan 2013 12:29:39 -0600 Received: from SM-DAG151.softlayer.local ([fe80::1588:d55b:b866:2177]) by SM-CAS151.softlayer.local ([fe80::2cad:d6ac:55f7:c0e%10]) with mapi id 14.02.0247.003; Tue, 8 Jan 2013 12:29:38 -0600 From: Joseph Hom To: George Shuklin , "xen-api@lists.xen.org" Thread-Topic: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 Thread-Index: AQHN6t/ZCqYUoQd0n0ym4a/KjLYtEJg6lfoAgAAm0QCABWgiAP//oGlg Date: Tue, 8 Jan 2013 18:29:37 +0000 Message-ID: <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> In-Reply-To: <50EC606C.2070702@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.176.170] MIME-Version: 1.0 X-DKIM-Status: none Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VGhhdCBpcyBkdWUgdG8gdGhlIG5ldyBzbSBiYWNrZW5kIHRoYXQgd2FzIGludHJvZHVjZWQuIFdo ZW4gYSB2YmQgaXMgcGx1Z2dlZCBpbnRvIGRvbTAgaXMgbm8gbG9uZ2VyIHNob3dzIHVwIGFzIGEg c3RyYWlnaHQgYmxvY2sgZGV2aWNlIHVuZGVyIC9kZXYvIA0KDQpUaGUgbmV3IHZlcnNpb24gb2Yg eGUtZWRpdC1ib290bG9hZGVyIGFkZHJlc3NlcyB0aGlzIGFuZCBjYW4gYmUgdXNlZCBhcyBhIHBv aW50ZXIgb24gd2hhdCB0byBkby4NCg0KSGludDoga3BhcnR4IC1hdiAvZGV2L3NtL2JhY2tlbmQv NTVlYTIwZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyDQpscyAvZGV2L21hcHBlci81NWVh MjBkMi04NjExLTExMjEtOWU5ZS1jMjZiMzVhYzE4NTIqDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2Fn ZS0tLS0tDQpGcm9tOiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyBbbWFpbHRvOnhlbi1h cGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbiBCZWhhbGYgT2YgR2VvcmdlIFNodWtsaW4NClNl bnQ6IFR1ZXNkYXksIEphbnVhcnkgMDgsIDIwMTMgMTI6MDggUE0NClRvOiB4ZW4tYXBpQGxpc3Rz Lnhlbi5vcmcNClN1YmplY3Q6IFJlOiBbWGVuLUFQSV0gbG9vayBpbnRvIFZIRCBWREkgZnJvbSBD b250cm9sIERvbWFpbiBpbiBYQ1AgMS42DQoNCk9rLCBoZXJlIGltcG9ydGFudCBzdHVmZi4gV2hl biBWQkQgaXMgcGx1Z2dlZCB0byBkb20wLCBpdCBwbHVnZ2luZyBub3QgYXMgJ25vcm1hbCcgZGV2 aWNlICh3aXRoIHVkZXYgYXR0ZW50aW9uKSwgYnV0IGFzIGRldmljZSBpbiAvZGV2L3NtL2JhY2tl bmQuDQoNCkhlcmUgc2FtcGxlIGxvZyAoY2hhbmdlIHV1aWRzIG9uIHlvdSB0YXN0ZSk6DQoNCnhl IHZiZC1jcmVhdGUgdm0tdXVpZD01M2MzZDg3OC1iNjBiLTQ4ZWMtYWFhYy03M2Y3YWRmOWFiM2QN CnZkaS11dWlkPTVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMiBkZXZpY2U9NiB4 ZSB2YmQtcGx1ZyB1dWlkPTQwN2ViM2E2LTkxOWYtZjYwNS0wODgzLWUxMmFhYTkxMzIxZA0KDQps cyAtbGEgL2Rldi9zbS9iYWNrZW5kLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1 Mi8NCtC40YLQvtCz0L4gNA0KZHJ3eHIteHIteCAyIHJvb3Qgcm9vdCAgICAgODAg0K/QvdCyICA4 IDIxOjU3IC4NCmRyd3hyLXhyLXggMyByb290IHJvb3QgICAgIDYwINCU0LXQuiAxOCAxNzo0MCAu Lg0KYnJ3LS0tLS0tLSAxIHJvb3Qgcm9vdCAyNTMsIDAg0K/QvdCyICA4IDIxOjU3DQo1ZTJjMzFh NS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzINCi1ydy1yLS1yLS0gMSByb290IHJvb3QgICAg ODUyINCv0L3QsiAgOCAyMTo1NyANCjVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUz Mi5hdHRhY2hfaW5mbw0KDQpJIGhhdmUgbm8gaWRlYSB3aHkgJzU1JyB1dWlkIChhbmQgd2hhdCBp dCBtZWFucyksIGJ1dA0KNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyIGlzIGJs b2NrIGRldmljZSBhZnRlciB3aG9sZSBWSEQgdHJlZSBqb2luaW5nL3BhcnNpbmcgYW5kIHNvIG9u Lg0KDQpZb3UgY2FuIHNlZSBhY3R1YWwgcGF0aCBpbiB4ZSB2YmQtbGlzdCBvdXRwdXQgKGRldmlj ZSBmaWVsZCkuDQoNCjA1LjAxLjIwMTMgMTE6MzMsIEFsZXhhbmRyZSBLb3V6bmV0c292INC/0LjR iNC10YI6DQo+IEhlbGxvLg0KPg0KPiBFbCAwNC8wMS8xMyAyMzoxNCwgR2VvcmdlIFNodWtsaW4g ZXNjcmliacOzOg0KPj4gVXNlIHhlIHZiZC1jcmVhdGUgYmV0d2VlbiB2ZGkgYW5kIGRvbTAgKHdo aWNoIGlzIG5vcm1hbCBWTSBtb3N0bHkpLCANCj4+IGFuZCB4ZSB2YmQtcGx1Zy4NCj4gWWVzLCB0 aGF0J3Mgd2hhdCBJIGhhdmUgZG9uZSBmb2xsb3dpbmcgdGhlIGV4YW1wbGUgZnJvbSBDaXRyaXgg Zm9ydW0uDQo+DQo+IEluIGNhc2Ugb2YgYSBub3JtYWwgRG9tVToNCj4gSSBjcmVhdGUgVkJEIGxp bmtpbmcgdGhlIFZNIHdpdGggVkRJLA0KPiBJIGlzc3VlIHZiZC1wbHVnLA0KPiB0aGUgYmxvY2sg ZGV2aWNlIGJlY29tZXMgdmlzaWJsZSBpbiBkbWVzZyB1bmRlciBEb21VLg0KPg0KPiBJbiBjYXNl IG9mIERvbTA6DQo+IEkgY3JlYXRlIFZCRCBsaW5raW5nIHRoZSBWTSAodm0tbGlzdCByZWZlcnMg dG8gaXQgYXMgIkNvbnRyb2wgRG9tYWluIiwgDQo+IG5vIG1pc3Rha2UpIHdpdGggVkRJLCBJIGlz c3VlIHZiZC1wbHVnLCBubyBzaWduIG9mIHRoZSBuZXcgYmxvY2sgDQo+IGRldmljZSBpbiBkbWVz ZyBvciB1bmRlciAvZGV2Lg0KPg0KPj4gWW91IGNhbiBzZWUgc29tZSBzYW1wbGUgdXNhZ2UgaW4g J3hlLWVkaXQtYm9vdGxvYWRlcicgY29tbWFuZCANCj4+IChzb21ld2hlcmUgaW4gL29wdC94ZW5z b3VyY2UvKQ0KPiBIbS4gSSBiZWxpZXZlIEknbSBkb2luZyBpdCBqdXN0IHRoZSBzYW1lIHdheSBh cyBpbiB0aGUgc2NyaXB0LCBleGNlcHQgDQo+IGJ5IHRoZSAiZGV2aWNlPSIgZGlyZWN0aXZlIGZv ciB2YmQtY3JlYXRlLCB1c2Ugc3BlY2lmaWMgc3RyaW5nIGxpa2UgDQo+ICJ4dmRuIi4NCj4gU2hv dWxkIGl0IG1ha2UgdGhlIGRpZmZlcmVuY2U/IENhbid0IHRlc3QsIEkgc2hvdCBkb3duIG15IHRl c3RpbmcgDQo+IHJhbmdlIGJlZm9yZSBsZWF2aW5nIHRoZSBvZmZpY2UuDQo+DQo+IFNvLCBtdXN0 IEkgdW5kZXJzdGFuZCB0aGF0IHRoZSBYQ1AncyByZWd1bGFyIHdheSBvZiBtYW5pcHVsYXRpbmcg VkRJJ3MgDQo+IGNvbnRlbnRzIGZyb20gd2l0aGluIERvbTAsIGlzIGF0dGFjaGluZyB0aGUgVkRJ IHRvIGl0IHZpYSBhIFZCRD8NCj4gTG9va3MgbGlrZSBhIGdvb2QgYWJzdHJhY3Rpb24sIGV4Y2Vw dCB0aGF0IGl0IHdvbid0IHdvcmsgdGhhdCBlYXNpbHkgDQo+IG9uIGEgaG9zdCB3aXRob3V0IFhD UCBpbmZyYXN0cnVjdHVyZSAoZm9yIGV4YW1wbGUsIGluIHNvbWUgcmVzY3VlIA0KPiBzY2VuYXJp bykuDQo+DQo+IFRoZW4sIHdoYXQgdmhkcGFydHggaXMgZ29vZCBmb3I/DQo+DQo+IENoZWVycy4N Cj4NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N Cj4gWGVuLWFwaSBtYWlsaW5nIGxpc3QNCj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnDQo+IGh0dHA6 Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpDQoNCg0KX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClhlbi1hcGkgbWFp bGluZyBsaXN0DQpYZW4tYXBpQGxpc3RzLnhlbi5vcmcNCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2Nn aS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpDQpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hl bi1hcGkK From xen-api-bounces@lists.xen.org Tue Jan 08 18:29:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 18:29:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsdvk-00075d-NH; Tue, 08 Jan 2013 18:29:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsdvj-00075Y-8X for xen-api@lists.xen.org; Tue, 08 Jan 2013 18:29:43 +0000 Received: from [85.158.138.51:47635] by server-5.bemta-3.messagelabs.com id F1/F4-04992-6956CE05; Tue, 08 Jan 2013 18:29:42 +0000 X-Env-Sender: jhom@softlayer.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1357669780!23799376!1 X-Originating-IP: [173.192.119.25] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8766 invoked from network); 8 Jan 2013 18:29:41 -0000 Received: from mx151.softlayer.com (HELO mx.softlayer.com) (173.192.119.25) by server-6.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Jan 2013 18:29:41 -0000 Received: from mail.softlayer.com by mx.softlayer.com with esmtp (Exim) (envelope-from ) id 1Tsdvf-000K9A-BC; Tue, 08 Jan 2013 12:29:39 -0600 Received: from SM-CAS151.softlayer.local (172.18.18.38) by SM-TMG151.softlayer.local (172.18.18.50) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 8 Jan 2013 12:29:39 -0600 Received: from SM-DAG151.softlayer.local ([fe80::1588:d55b:b866:2177]) by SM-CAS151.softlayer.local ([fe80::2cad:d6ac:55f7:c0e%10]) with mapi id 14.02.0247.003; Tue, 8 Jan 2013 12:29:38 -0600 From: Joseph Hom To: George Shuklin , "xen-api@lists.xen.org" Thread-Topic: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 Thread-Index: AQHN6t/ZCqYUoQd0n0ym4a/KjLYtEJg6lfoAgAAm0QCABWgiAP//oGlg Date: Tue, 8 Jan 2013 18:29:37 +0000 Message-ID: <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> In-Reply-To: <50EC606C.2070702@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.176.170] MIME-Version: 1.0 X-DKIM-Status: none Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VGhhdCBpcyBkdWUgdG8gdGhlIG5ldyBzbSBiYWNrZW5kIHRoYXQgd2FzIGludHJvZHVjZWQuIFdo ZW4gYSB2YmQgaXMgcGx1Z2dlZCBpbnRvIGRvbTAgaXMgbm8gbG9uZ2VyIHNob3dzIHVwIGFzIGEg c3RyYWlnaHQgYmxvY2sgZGV2aWNlIHVuZGVyIC9kZXYvIA0KDQpUaGUgbmV3IHZlcnNpb24gb2Yg eGUtZWRpdC1ib290bG9hZGVyIGFkZHJlc3NlcyB0aGlzIGFuZCBjYW4gYmUgdXNlZCBhcyBhIHBv aW50ZXIgb24gd2hhdCB0byBkby4NCg0KSGludDoga3BhcnR4IC1hdiAvZGV2L3NtL2JhY2tlbmQv NTVlYTIwZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyDQpscyAvZGV2L21hcHBlci81NWVh MjBkMi04NjExLTExMjEtOWU5ZS1jMjZiMzVhYzE4NTIqDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2Fn ZS0tLS0tDQpGcm9tOiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyBbbWFpbHRvOnhlbi1h cGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbiBCZWhhbGYgT2YgR2VvcmdlIFNodWtsaW4NClNl bnQ6IFR1ZXNkYXksIEphbnVhcnkgMDgsIDIwMTMgMTI6MDggUE0NClRvOiB4ZW4tYXBpQGxpc3Rz Lnhlbi5vcmcNClN1YmplY3Q6IFJlOiBbWGVuLUFQSV0gbG9vayBpbnRvIFZIRCBWREkgZnJvbSBD b250cm9sIERvbWFpbiBpbiBYQ1AgMS42DQoNCk9rLCBoZXJlIGltcG9ydGFudCBzdHVmZi4gV2hl biBWQkQgaXMgcGx1Z2dlZCB0byBkb20wLCBpdCBwbHVnZ2luZyBub3QgYXMgJ25vcm1hbCcgZGV2 aWNlICh3aXRoIHVkZXYgYXR0ZW50aW9uKSwgYnV0IGFzIGRldmljZSBpbiAvZGV2L3NtL2JhY2tl bmQuDQoNCkhlcmUgc2FtcGxlIGxvZyAoY2hhbmdlIHV1aWRzIG9uIHlvdSB0YXN0ZSk6DQoNCnhl IHZiZC1jcmVhdGUgdm0tdXVpZD01M2MzZDg3OC1iNjBiLTQ4ZWMtYWFhYy03M2Y3YWRmOWFiM2QN CnZkaS11dWlkPTVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMiBkZXZpY2U9NiB4 ZSB2YmQtcGx1ZyB1dWlkPTQwN2ViM2E2LTkxOWYtZjYwNS0wODgzLWUxMmFhYTkxMzIxZA0KDQps cyAtbGEgL2Rldi9zbS9iYWNrZW5kLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1 Mi8NCtC40YLQvtCz0L4gNA0KZHJ3eHIteHIteCAyIHJvb3Qgcm9vdCAgICAgODAg0K/QvdCyICA4 IDIxOjU3IC4NCmRyd3hyLXhyLXggMyByb290IHJvb3QgICAgIDYwINCU0LXQuiAxOCAxNzo0MCAu Lg0KYnJ3LS0tLS0tLSAxIHJvb3Qgcm9vdCAyNTMsIDAg0K/QvdCyICA4IDIxOjU3DQo1ZTJjMzFh NS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzINCi1ydy1yLS1yLS0gMSByb290IHJvb3QgICAg ODUyINCv0L3QsiAgOCAyMTo1NyANCjVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUz Mi5hdHRhY2hfaW5mbw0KDQpJIGhhdmUgbm8gaWRlYSB3aHkgJzU1JyB1dWlkIChhbmQgd2hhdCBp dCBtZWFucyksIGJ1dA0KNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyIGlzIGJs b2NrIGRldmljZSBhZnRlciB3aG9sZSBWSEQgdHJlZSBqb2luaW5nL3BhcnNpbmcgYW5kIHNvIG9u Lg0KDQpZb3UgY2FuIHNlZSBhY3R1YWwgcGF0aCBpbiB4ZSB2YmQtbGlzdCBvdXRwdXQgKGRldmlj ZSBmaWVsZCkuDQoNCjA1LjAxLjIwMTMgMTE6MzMsIEFsZXhhbmRyZSBLb3V6bmV0c292INC/0LjR iNC10YI6DQo+IEhlbGxvLg0KPg0KPiBFbCAwNC8wMS8xMyAyMzoxNCwgR2VvcmdlIFNodWtsaW4g ZXNjcmliacOzOg0KPj4gVXNlIHhlIHZiZC1jcmVhdGUgYmV0d2VlbiB2ZGkgYW5kIGRvbTAgKHdo aWNoIGlzIG5vcm1hbCBWTSBtb3N0bHkpLCANCj4+IGFuZCB4ZSB2YmQtcGx1Zy4NCj4gWWVzLCB0 aGF0J3Mgd2hhdCBJIGhhdmUgZG9uZSBmb2xsb3dpbmcgdGhlIGV4YW1wbGUgZnJvbSBDaXRyaXgg Zm9ydW0uDQo+DQo+IEluIGNhc2Ugb2YgYSBub3JtYWwgRG9tVToNCj4gSSBjcmVhdGUgVkJEIGxp bmtpbmcgdGhlIFZNIHdpdGggVkRJLA0KPiBJIGlzc3VlIHZiZC1wbHVnLA0KPiB0aGUgYmxvY2sg ZGV2aWNlIGJlY29tZXMgdmlzaWJsZSBpbiBkbWVzZyB1bmRlciBEb21VLg0KPg0KPiBJbiBjYXNl IG9mIERvbTA6DQo+IEkgY3JlYXRlIFZCRCBsaW5raW5nIHRoZSBWTSAodm0tbGlzdCByZWZlcnMg dG8gaXQgYXMgIkNvbnRyb2wgRG9tYWluIiwgDQo+IG5vIG1pc3Rha2UpIHdpdGggVkRJLCBJIGlz c3VlIHZiZC1wbHVnLCBubyBzaWduIG9mIHRoZSBuZXcgYmxvY2sgDQo+IGRldmljZSBpbiBkbWVz ZyBvciB1bmRlciAvZGV2Lg0KPg0KPj4gWW91IGNhbiBzZWUgc29tZSBzYW1wbGUgdXNhZ2UgaW4g J3hlLWVkaXQtYm9vdGxvYWRlcicgY29tbWFuZCANCj4+IChzb21ld2hlcmUgaW4gL29wdC94ZW5z b3VyY2UvKQ0KPiBIbS4gSSBiZWxpZXZlIEknbSBkb2luZyBpdCBqdXN0IHRoZSBzYW1lIHdheSBh cyBpbiB0aGUgc2NyaXB0LCBleGNlcHQgDQo+IGJ5IHRoZSAiZGV2aWNlPSIgZGlyZWN0aXZlIGZv ciB2YmQtY3JlYXRlLCB1c2Ugc3BlY2lmaWMgc3RyaW5nIGxpa2UgDQo+ICJ4dmRuIi4NCj4gU2hv dWxkIGl0IG1ha2UgdGhlIGRpZmZlcmVuY2U/IENhbid0IHRlc3QsIEkgc2hvdCBkb3duIG15IHRl c3RpbmcgDQo+IHJhbmdlIGJlZm9yZSBsZWF2aW5nIHRoZSBvZmZpY2UuDQo+DQo+IFNvLCBtdXN0 IEkgdW5kZXJzdGFuZCB0aGF0IHRoZSBYQ1AncyByZWd1bGFyIHdheSBvZiBtYW5pcHVsYXRpbmcg VkRJJ3MgDQo+IGNvbnRlbnRzIGZyb20gd2l0aGluIERvbTAsIGlzIGF0dGFjaGluZyB0aGUgVkRJ IHRvIGl0IHZpYSBhIFZCRD8NCj4gTG9va3MgbGlrZSBhIGdvb2QgYWJzdHJhY3Rpb24sIGV4Y2Vw dCB0aGF0IGl0IHdvbid0IHdvcmsgdGhhdCBlYXNpbHkgDQo+IG9uIGEgaG9zdCB3aXRob3V0IFhD UCBpbmZyYXN0cnVjdHVyZSAoZm9yIGV4YW1wbGUsIGluIHNvbWUgcmVzY3VlIA0KPiBzY2VuYXJp bykuDQo+DQo+IFRoZW4sIHdoYXQgdmhkcGFydHggaXMgZ29vZCBmb3I/DQo+DQo+IENoZWVycy4N Cj4NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N Cj4gWGVuLWFwaSBtYWlsaW5nIGxpc3QNCj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnDQo+IGh0dHA6 Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpDQoNCg0KX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClhlbi1hcGkgbWFp bGluZyBsaXN0DQpYZW4tYXBpQGxpc3RzLnhlbi5vcmcNCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2Nn aS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpDQpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hl bi1hcGkK From xen-api-bounces@lists.xen.org Tue Jan 08 18:35:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 18:35:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse0t-0007GF-Py; Tue, 08 Jan 2013 18:35:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse0r-0007Fy-QK for xen-api@lists.xen.org; Tue, 08 Jan 2013 18:35:02 +0000 Received: from [85.158.138.51:10057] by server-11.bemta-3.messagelabs.com id 49/38-13335-5D66CE05; Tue, 08 Jan 2013 18:35:01 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1357670099!20055081!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30955 invoked from network); 8 Jan 2013 18:35:00 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 18:35:00 -0000 Received: by mail-lb0-f172.google.com with SMTP id y2so626501lbk.31 for ; Tue, 08 Jan 2013 10:34:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=kuV72a2h7lxetpdISQbhlgeT3LHfMRwlvrWn0wuJ7lE=; b=R/5f1OEQ/nHfGmFyNEgeWKzdnBPfSryNUQSBkNekRBZ1G43mfBSBKaw7kJU+/TLZMV OjQu4YIltYM5Bcn2sheF5i4NNRzEFG3TE0N8JLvEJ62g9/JEegbeDU7ZRctdv8xjTVo1 hcmwwmMnX0wbo56Rz3Du8VBszcryp0+YBLu1RVQkT0iCD0NHUsqwsYi7sYNyu/0tyYe3 F2dfnccEfGF1/wLgZIYs0SvU9TALGaFvTCZ/Vv2/92hfjOIQGshffymtlB3UWR1fEz7E LMlch86GsLCipd1deXPCbJEE6hMwE8oNK87OJivlwl1fk6L/ZrAAWPiXA2Zgigpx+2GP hNXQ== X-Received: by 10.152.125.136 with SMTP id mq8mr62838427lab.41.1357670099558; Tue, 08 Jan 2013 10:34:59 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id u5sm22991472lbm.8.2013.01.08.10.34.58 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 10:34:59 -0800 (PST) Message-ID: <50EC66D2.8060304@gmail.com> Date: Tue, 08 Jan 2013 22:34:58 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: Joseph Hom References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> In-Reply-To: <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WWVwLCBidXQgd2hhdCB0aGUgdXVpZCBpcyB0aGF0ICc1NWVhLi4uJz8gSSB4ZWUgaXQgbm93aGVy ZSBpbiByZWxhdGVkIApvYmplY3RzOgoKdXVpZCAoIFJPKSAgICAgICAgICAgICA6IDlhNGVlMjdi LWQ5OTAtNDg4Ny1mZjQ5LWUyYzFmYjEwMDA2MQogICAgICAgICAgIHZtLXV1aWQgKCBSTyk6IDUz YzNkODc4LWI2MGItNDhlYy1hYWFjLTczZjdhZGY5YWIzZAogICAgIHZtLW5hbWUtbGFiZWwgKCBS Tyk6IENvbnRyb2wgZG9tYWluIG9uIGhvc3Q6IHRlc3QKICAgICAgICAgIHZkaS11dWlkICggUk8p OiA1ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzIKICAgICAgICAgICAgIGVtcHR5 ICggUk8pOiBmYWxzZQogICAgICAgICAgICBkZXZpY2UgKCBSTyk6IApzbS9iYWNrZW5kLzU1ZWEy MGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi81ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0x ZmEzYmM0N2I1MzIKCi4uLi4uCgpBZnRlciBzb21lIGd1ZXNzaW5nOiB0aGlzIGlzIFNSIHV1aWQu Cgp4ZSB2ZGktbGlzdCB1dWlkPTVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMgp1 dWlkICggUk8pICAgICAgICAgICAgICAgIDogNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2Jj NDdiNTMyCiAgICAgICAgICAgbmFtZS1sYWJlbCAoIFJXKTogdGVzdDEKICAgICBuYW1lLWRlc2Ny aXB0aW9uICggUlcpOgogICAgICAgICAgICAgIHNyLXV1aWQgKCBSTyk6IDU1ZWEyMGQyLTg2MTEt MTEyMS05ZTllLWMyNmIzNWFjMTg1MgogICAgICAgICB2aXJ0dWFsLXNpemUgKCBSTyk6IDIxNDc0 ODM2NDgKICAgICAgICAgICAgIHNoYXJhYmxlICggUk8pOiBmYWxzZQogICAgICAgICAgICByZWFk LW9ubHkgKCBSTyk6IGZhbHNlCgoKCjA4LjAxLjIwMTMgMjI6MjksIEpvc2VwaCBIb20g0L/QuNGI 0LXRgjoKPiBUaGF0IGlzIGR1ZSB0byB0aGUgbmV3IHNtIGJhY2tlbmQgdGhhdCB3YXMgaW50cm9k dWNlZC4gV2hlbiBhIHZiZCBpcyBwbHVnZ2VkIGludG8gZG9tMCBpcyBubyBsb25nZXIgc2hvd3Mg dXAgYXMgYSBzdHJhaWdodCBibG9jayBkZXZpY2UgdW5kZXIgL2Rldi8KPgo+IFRoZSBuZXcgdmVy c2lvbiBvZiB4ZS1lZGl0LWJvb3Rsb2FkZXIgYWRkcmVzc2VzIHRoaXMgYW5kIGNhbiBiZSB1c2Vk IGFzIGEgcG9pbnRlciBvbiB3aGF0IHRvIGRvLgo+Cj4gSGludDoga3BhcnR4IC1hdiAvZGV2L3Nt L2JhY2tlbmQvNTVlYTIwZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyCj4gbHMgL2Rldi9t YXBwZXIvNTVlYTIwZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyKgo+Cj4gLS0tLS1Pcmln aW5hbCBNZXNzYWdlLS0tLS0KPiBGcm9tOiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyBb bWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbiBCZWhhbGYgT2YgR2Vvcmdl IFNodWtsaW4KPiBTZW50OiBUdWVzZGF5LCBKYW51YXJ5IDA4LCAyMDEzIDEyOjA4IFBNCj4gVG86 IHhlbi1hcGlAbGlzdHMueGVuLm9yZwo+IFN1YmplY3Q6IFJlOiBbWGVuLUFQSV0gbG9vayBpbnRv IFZIRCBWREkgZnJvbSBDb250cm9sIERvbWFpbiBpbiBYQ1AgMS42Cj4KPiBPaywgaGVyZSBpbXBv cnRhbnQgc3R1ZmYuIFdoZW4gVkJEIGlzIHBsdWdnZWQgdG8gZG9tMCwgaXQgcGx1Z2dpbmcgbm90 IGFzICdub3JtYWwnIGRldmljZSAod2l0aCB1ZGV2IGF0dGVudGlvbiksIGJ1dCBhcyBkZXZpY2Ug aW4gL2Rldi9zbS9iYWNrZW5kLgo+Cj4gSGVyZSBzYW1wbGUgbG9nIChjaGFuZ2UgdXVpZHMgb24g eW91IHRhc3RlKToKPgo+IHhlIHZiZC1jcmVhdGUgdm0tdXVpZD01M2MzZDg3OC1iNjBiLTQ4ZWMt YWFhYy03M2Y3YWRmOWFiM2QKPiB2ZGktdXVpZD01ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEz YmM0N2I1MzIgZGV2aWNlPTYgeGUgdmJkLXBsdWcgdXVpZD00MDdlYjNhNi05MTlmLWY2MDUtMDg4 My1lMTJhYWE5MTMyMWQKPgo+IGxzIC1sYSAvZGV2L3NtL2JhY2tlbmQvNTVlYTIwZDItODYxMS0x MTIxLTllOWUtYzI2YjM1YWMxODUyLwo+INC40YLQvtCz0L4gNAo+IGRyd3hyLXhyLXggMiByb290 IHJvb3QgICAgIDgwINCv0L3QsiAgOCAyMTo1NyAuCj4gZHJ3eHIteHIteCAzIHJvb3Qgcm9vdCAg ICAgNjAg0JTQtdC6IDE4IDE3OjQwIC4uCj4gYnJ3LS0tLS0tLSAxIHJvb3Qgcm9vdCAyNTMsIDAg 0K/QvdCyICA4IDIxOjU3Cj4gNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyCj4g LXJ3LXItLXItLSAxIHJvb3Qgcm9vdCAgICA4NTIg0K/QvdCyICA4IDIxOjU3Cj4gNWUyYzMxYTUt MWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyLmF0dGFjaF9pbmZvCj4KPiBJIGhhdmUgbm8gaWRl YSB3aHkgJzU1JyB1dWlkIChhbmQgd2hhdCBpdCBtZWFucyksIGJ1dAo+IDVlMmMzMWE1LTFkMWIt NGFiZS05ODkyLTFmYTNiYzQ3YjUzMiBpcyBibG9jayBkZXZpY2UgYWZ0ZXIgd2hvbGUgVkhEIHRy ZWUgam9pbmluZy9wYXJzaW5nIGFuZCBzbyBvbi4KPgo+IFlvdSBjYW4gc2VlIGFjdHVhbCBwYXRo IGluIHhlIHZiZC1saXN0IG91dHB1dCAoZGV2aWNlIGZpZWxkKS4KPgo+IDA1LjAxLjIwMTMgMTE6 MzMsIEFsZXhhbmRyZSBLb3V6bmV0c292INC/0LjRiNC10YI6Cj4+IEhlbGxvLgo+Pgo+PiBFbCAw NC8wMS8xMyAyMzoxNCwgR2VvcmdlIFNodWtsaW4gZXNjcmliacOzOgo+Pj4gVXNlIHhlIHZiZC1j cmVhdGUgYmV0d2VlbiB2ZGkgYW5kIGRvbTAgKHdoaWNoIGlzIG5vcm1hbCBWTSBtb3N0bHkpLAo+ Pj4gYW5kIHhlIHZiZC1wbHVnLgo+PiBZZXMsIHRoYXQncyB3aGF0IEkgaGF2ZSBkb25lIGZvbGxv d2luZyB0aGUgZXhhbXBsZSBmcm9tIENpdHJpeCBmb3J1bS4KPj4KPj4gSW4gY2FzZSBvZiBhIG5v cm1hbCBEb21VOgo+PiBJIGNyZWF0ZSBWQkQgbGlua2luZyB0aGUgVk0gd2l0aCBWREksCj4+IEkg aXNzdWUgdmJkLXBsdWcsCj4+IHRoZSBibG9jayBkZXZpY2UgYmVjb21lcyB2aXNpYmxlIGluIGRt ZXNnIHVuZGVyIERvbVUuCj4+Cj4+IEluIGNhc2Ugb2YgRG9tMDoKPj4gSSBjcmVhdGUgVkJEIGxp bmtpbmcgdGhlIFZNICh2bS1saXN0IHJlZmVycyB0byBpdCBhcyAiQ29udHJvbCBEb21haW4iLAo+ PiBubyBtaXN0YWtlKSB3aXRoIFZESSwgSSBpc3N1ZSB2YmQtcGx1Zywgbm8gc2lnbiBvZiB0aGUg bmV3IGJsb2NrCj4+IGRldmljZSBpbiBkbWVzZyBvciB1bmRlciAvZGV2Lgo+Pgo+Pj4gWW91IGNh biBzZWUgc29tZSBzYW1wbGUgdXNhZ2UgaW4gJ3hlLWVkaXQtYm9vdGxvYWRlcicgY29tbWFuZAo+ Pj4gKHNvbWV3aGVyZSBpbiAvb3B0L3hlbnNvdXJjZS8pCj4+IEhtLiBJIGJlbGlldmUgSSdtIGRv aW5nIGl0IGp1c3QgdGhlIHNhbWUgd2F5IGFzIGluIHRoZSBzY3JpcHQsIGV4Y2VwdAo+PiBieSB0 aGUgImRldmljZT0iIGRpcmVjdGl2ZSBmb3IgdmJkLWNyZWF0ZSwgdXNlIHNwZWNpZmljIHN0cmlu ZyBsaWtlCj4+ICJ4dmRuIi4KPj4gU2hvdWxkIGl0IG1ha2UgdGhlIGRpZmZlcmVuY2U/IENhbid0 IHRlc3QsIEkgc2hvdCBkb3duIG15IHRlc3RpbmcKPj4gcmFuZ2UgYmVmb3JlIGxlYXZpbmcgdGhl IG9mZmljZS4KPj4KPj4gU28sIG11c3QgSSB1bmRlcnN0YW5kIHRoYXQgdGhlIFhDUCdzIHJlZ3Vs YXIgd2F5IG9mIG1hbmlwdWxhdGluZyBWREkncwo+PiBjb250ZW50cyBmcm9tIHdpdGhpbiBEb20w LCBpcyBhdHRhY2hpbmcgdGhlIFZESSB0byBpdCB2aWEgYSBWQkQ/Cj4+IExvb2tzIGxpa2UgYSBn b29kIGFic3RyYWN0aW9uLCBleGNlcHQgdGhhdCBpdCB3b24ndCB3b3JrIHRoYXQgZWFzaWx5Cj4+ IG9uIGEgaG9zdCB3aXRob3V0IFhDUCBpbmZyYXN0cnVjdHVyZSAoZm9yIGV4YW1wbGUsIGluIHNv bWUgcmVzY3VlCj4+IHNjZW5hcmlvKS4KPj4KPj4gVGhlbiwgd2hhdCB2aGRwYXJ0eCBpcyBnb29k IGZvcj8KPj4KPj4gQ2hlZXJzLgo+Pgo+Pgo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwo+PiBYZW4tYXBpIG1haWxpbmcgbGlzdAo+PiBYZW4tYXBpQGxp c3RzLnhlbi5vcmcKPj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL3hlbi1hcGkKPgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fCj4gWGVuLWFwaSBtYWlsaW5nIGxpc3QKPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPiBo dHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQoKCl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFp bGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Tue Jan 08 18:35:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 18:35:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse0t-0007GF-Py; Tue, 08 Jan 2013 18:35:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse0r-0007Fy-QK for xen-api@lists.xen.org; Tue, 08 Jan 2013 18:35:02 +0000 Received: from [85.158.138.51:10057] by server-11.bemta-3.messagelabs.com id 49/38-13335-5D66CE05; Tue, 08 Jan 2013 18:35:01 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1357670099!20055081!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30955 invoked from network); 8 Jan 2013 18:35:00 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 18:35:00 -0000 Received: by mail-lb0-f172.google.com with SMTP id y2so626501lbk.31 for ; Tue, 08 Jan 2013 10:34:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=kuV72a2h7lxetpdISQbhlgeT3LHfMRwlvrWn0wuJ7lE=; b=R/5f1OEQ/nHfGmFyNEgeWKzdnBPfSryNUQSBkNekRBZ1G43mfBSBKaw7kJU+/TLZMV OjQu4YIltYM5Bcn2sheF5i4NNRzEFG3TE0N8JLvEJ62g9/JEegbeDU7ZRctdv8xjTVo1 hcmwwmMnX0wbo56Rz3Du8VBszcryp0+YBLu1RVQkT0iCD0NHUsqwsYi7sYNyu/0tyYe3 F2dfnccEfGF1/wLgZIYs0SvU9TALGaFvTCZ/Vv2/92hfjOIQGshffymtlB3UWR1fEz7E LMlch86GsLCipd1deXPCbJEE6hMwE8oNK87OJivlwl1fk6L/ZrAAWPiXA2Zgigpx+2GP hNXQ== X-Received: by 10.152.125.136 with SMTP id mq8mr62838427lab.41.1357670099558; Tue, 08 Jan 2013 10:34:59 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id u5sm22991472lbm.8.2013.01.08.10.34.58 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 10:34:59 -0800 (PST) Message-ID: <50EC66D2.8060304@gmail.com> Date: Tue, 08 Jan 2013 22:34:58 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: Joseph Hom References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> In-Reply-To: <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WWVwLCBidXQgd2hhdCB0aGUgdXVpZCBpcyB0aGF0ICc1NWVhLi4uJz8gSSB4ZWUgaXQgbm93aGVy ZSBpbiByZWxhdGVkIApvYmplY3RzOgoKdXVpZCAoIFJPKSAgICAgICAgICAgICA6IDlhNGVlMjdi LWQ5OTAtNDg4Ny1mZjQ5LWUyYzFmYjEwMDA2MQogICAgICAgICAgIHZtLXV1aWQgKCBSTyk6IDUz YzNkODc4LWI2MGItNDhlYy1hYWFjLTczZjdhZGY5YWIzZAogICAgIHZtLW5hbWUtbGFiZWwgKCBS Tyk6IENvbnRyb2wgZG9tYWluIG9uIGhvc3Q6IHRlc3QKICAgICAgICAgIHZkaS11dWlkICggUk8p OiA1ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzIKICAgICAgICAgICAgIGVtcHR5 ICggUk8pOiBmYWxzZQogICAgICAgICAgICBkZXZpY2UgKCBSTyk6IApzbS9iYWNrZW5kLzU1ZWEy MGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi81ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0x ZmEzYmM0N2I1MzIKCi4uLi4uCgpBZnRlciBzb21lIGd1ZXNzaW5nOiB0aGlzIGlzIFNSIHV1aWQu Cgp4ZSB2ZGktbGlzdCB1dWlkPTVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMgp1 dWlkICggUk8pICAgICAgICAgICAgICAgIDogNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2Jj NDdiNTMyCiAgICAgICAgICAgbmFtZS1sYWJlbCAoIFJXKTogdGVzdDEKICAgICBuYW1lLWRlc2Ny aXB0aW9uICggUlcpOgogICAgICAgICAgICAgIHNyLXV1aWQgKCBSTyk6IDU1ZWEyMGQyLTg2MTEt MTEyMS05ZTllLWMyNmIzNWFjMTg1MgogICAgICAgICB2aXJ0dWFsLXNpemUgKCBSTyk6IDIxNDc0 ODM2NDgKICAgICAgICAgICAgIHNoYXJhYmxlICggUk8pOiBmYWxzZQogICAgICAgICAgICByZWFk LW9ubHkgKCBSTyk6IGZhbHNlCgoKCjA4LjAxLjIwMTMgMjI6MjksIEpvc2VwaCBIb20g0L/QuNGI 0LXRgjoKPiBUaGF0IGlzIGR1ZSB0byB0aGUgbmV3IHNtIGJhY2tlbmQgdGhhdCB3YXMgaW50cm9k dWNlZC4gV2hlbiBhIHZiZCBpcyBwbHVnZ2VkIGludG8gZG9tMCBpcyBubyBsb25nZXIgc2hvd3Mg dXAgYXMgYSBzdHJhaWdodCBibG9jayBkZXZpY2UgdW5kZXIgL2Rldi8KPgo+IFRoZSBuZXcgdmVy c2lvbiBvZiB4ZS1lZGl0LWJvb3Rsb2FkZXIgYWRkcmVzc2VzIHRoaXMgYW5kIGNhbiBiZSB1c2Vk IGFzIGEgcG9pbnRlciBvbiB3aGF0IHRvIGRvLgo+Cj4gSGludDoga3BhcnR4IC1hdiAvZGV2L3Nt L2JhY2tlbmQvNTVlYTIwZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyCj4gbHMgL2Rldi9t YXBwZXIvNTVlYTIwZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyKgo+Cj4gLS0tLS1Pcmln aW5hbCBNZXNzYWdlLS0tLS0KPiBGcm9tOiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyBb bWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbiBCZWhhbGYgT2YgR2Vvcmdl IFNodWtsaW4KPiBTZW50OiBUdWVzZGF5LCBKYW51YXJ5IDA4LCAyMDEzIDEyOjA4IFBNCj4gVG86 IHhlbi1hcGlAbGlzdHMueGVuLm9yZwo+IFN1YmplY3Q6IFJlOiBbWGVuLUFQSV0gbG9vayBpbnRv IFZIRCBWREkgZnJvbSBDb250cm9sIERvbWFpbiBpbiBYQ1AgMS42Cj4KPiBPaywgaGVyZSBpbXBv cnRhbnQgc3R1ZmYuIFdoZW4gVkJEIGlzIHBsdWdnZWQgdG8gZG9tMCwgaXQgcGx1Z2dpbmcgbm90 IGFzICdub3JtYWwnIGRldmljZSAod2l0aCB1ZGV2IGF0dGVudGlvbiksIGJ1dCBhcyBkZXZpY2Ug aW4gL2Rldi9zbS9iYWNrZW5kLgo+Cj4gSGVyZSBzYW1wbGUgbG9nIChjaGFuZ2UgdXVpZHMgb24g eW91IHRhc3RlKToKPgo+IHhlIHZiZC1jcmVhdGUgdm0tdXVpZD01M2MzZDg3OC1iNjBiLTQ4ZWMt YWFhYy03M2Y3YWRmOWFiM2QKPiB2ZGktdXVpZD01ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEz YmM0N2I1MzIgZGV2aWNlPTYgeGUgdmJkLXBsdWcgdXVpZD00MDdlYjNhNi05MTlmLWY2MDUtMDg4 My1lMTJhYWE5MTMyMWQKPgo+IGxzIC1sYSAvZGV2L3NtL2JhY2tlbmQvNTVlYTIwZDItODYxMS0x MTIxLTllOWUtYzI2YjM1YWMxODUyLwo+INC40YLQvtCz0L4gNAo+IGRyd3hyLXhyLXggMiByb290 IHJvb3QgICAgIDgwINCv0L3QsiAgOCAyMTo1NyAuCj4gZHJ3eHIteHIteCAzIHJvb3Qgcm9vdCAg ICAgNjAg0JTQtdC6IDE4IDE3OjQwIC4uCj4gYnJ3LS0tLS0tLSAxIHJvb3Qgcm9vdCAyNTMsIDAg 0K/QvdCyICA4IDIxOjU3Cj4gNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyCj4g LXJ3LXItLXItLSAxIHJvb3Qgcm9vdCAgICA4NTIg0K/QvdCyICA4IDIxOjU3Cj4gNWUyYzMxYTUt MWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyLmF0dGFjaF9pbmZvCj4KPiBJIGhhdmUgbm8gaWRl YSB3aHkgJzU1JyB1dWlkIChhbmQgd2hhdCBpdCBtZWFucyksIGJ1dAo+IDVlMmMzMWE1LTFkMWIt NGFiZS05ODkyLTFmYTNiYzQ3YjUzMiBpcyBibG9jayBkZXZpY2UgYWZ0ZXIgd2hvbGUgVkhEIHRy ZWUgam9pbmluZy9wYXJzaW5nIGFuZCBzbyBvbi4KPgo+IFlvdSBjYW4gc2VlIGFjdHVhbCBwYXRo IGluIHhlIHZiZC1saXN0IG91dHB1dCAoZGV2aWNlIGZpZWxkKS4KPgo+IDA1LjAxLjIwMTMgMTE6 MzMsIEFsZXhhbmRyZSBLb3V6bmV0c292INC/0LjRiNC10YI6Cj4+IEhlbGxvLgo+Pgo+PiBFbCAw NC8wMS8xMyAyMzoxNCwgR2VvcmdlIFNodWtsaW4gZXNjcmliacOzOgo+Pj4gVXNlIHhlIHZiZC1j cmVhdGUgYmV0d2VlbiB2ZGkgYW5kIGRvbTAgKHdoaWNoIGlzIG5vcm1hbCBWTSBtb3N0bHkpLAo+ Pj4gYW5kIHhlIHZiZC1wbHVnLgo+PiBZZXMsIHRoYXQncyB3aGF0IEkgaGF2ZSBkb25lIGZvbGxv d2luZyB0aGUgZXhhbXBsZSBmcm9tIENpdHJpeCBmb3J1bS4KPj4KPj4gSW4gY2FzZSBvZiBhIG5v cm1hbCBEb21VOgo+PiBJIGNyZWF0ZSBWQkQgbGlua2luZyB0aGUgVk0gd2l0aCBWREksCj4+IEkg aXNzdWUgdmJkLXBsdWcsCj4+IHRoZSBibG9jayBkZXZpY2UgYmVjb21lcyB2aXNpYmxlIGluIGRt ZXNnIHVuZGVyIERvbVUuCj4+Cj4+IEluIGNhc2Ugb2YgRG9tMDoKPj4gSSBjcmVhdGUgVkJEIGxp bmtpbmcgdGhlIFZNICh2bS1saXN0IHJlZmVycyB0byBpdCBhcyAiQ29udHJvbCBEb21haW4iLAo+ PiBubyBtaXN0YWtlKSB3aXRoIFZESSwgSSBpc3N1ZSB2YmQtcGx1Zywgbm8gc2lnbiBvZiB0aGUg bmV3IGJsb2NrCj4+IGRldmljZSBpbiBkbWVzZyBvciB1bmRlciAvZGV2Lgo+Pgo+Pj4gWW91IGNh biBzZWUgc29tZSBzYW1wbGUgdXNhZ2UgaW4gJ3hlLWVkaXQtYm9vdGxvYWRlcicgY29tbWFuZAo+ Pj4gKHNvbWV3aGVyZSBpbiAvb3B0L3hlbnNvdXJjZS8pCj4+IEhtLiBJIGJlbGlldmUgSSdtIGRv aW5nIGl0IGp1c3QgdGhlIHNhbWUgd2F5IGFzIGluIHRoZSBzY3JpcHQsIGV4Y2VwdAo+PiBieSB0 aGUgImRldmljZT0iIGRpcmVjdGl2ZSBmb3IgdmJkLWNyZWF0ZSwgdXNlIHNwZWNpZmljIHN0cmlu ZyBsaWtlCj4+ICJ4dmRuIi4KPj4gU2hvdWxkIGl0IG1ha2UgdGhlIGRpZmZlcmVuY2U/IENhbid0 IHRlc3QsIEkgc2hvdCBkb3duIG15IHRlc3RpbmcKPj4gcmFuZ2UgYmVmb3JlIGxlYXZpbmcgdGhl IG9mZmljZS4KPj4KPj4gU28sIG11c3QgSSB1bmRlcnN0YW5kIHRoYXQgdGhlIFhDUCdzIHJlZ3Vs YXIgd2F5IG9mIG1hbmlwdWxhdGluZyBWREkncwo+PiBjb250ZW50cyBmcm9tIHdpdGhpbiBEb20w LCBpcyBhdHRhY2hpbmcgdGhlIFZESSB0byBpdCB2aWEgYSBWQkQ/Cj4+IExvb2tzIGxpa2UgYSBn b29kIGFic3RyYWN0aW9uLCBleGNlcHQgdGhhdCBpdCB3b24ndCB3b3JrIHRoYXQgZWFzaWx5Cj4+ IG9uIGEgaG9zdCB3aXRob3V0IFhDUCBpbmZyYXN0cnVjdHVyZSAoZm9yIGV4YW1wbGUsIGluIHNv bWUgcmVzY3VlCj4+IHNjZW5hcmlvKS4KPj4KPj4gVGhlbiwgd2hhdCB2aGRwYXJ0eCBpcyBnb29k IGZvcj8KPj4KPj4gQ2hlZXJzLgo+Pgo+Pgo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwo+PiBYZW4tYXBpIG1haWxpbmcgbGlzdAo+PiBYZW4tYXBpQGxp c3RzLnhlbi5vcmcKPj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL3hlbi1hcGkKPgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fCj4gWGVuLWFwaSBtYWlsaW5nIGxpc3QKPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPiBo dHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQoKCl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFp bGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Tue Jan 08 18:40:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 18:40:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse5q-0007Rn-BP; Tue, 08 Jan 2013 18:40:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse5o-0007Re-E9 for xen-api@lists.xen.org; Tue, 08 Jan 2013 18:40:08 +0000 Received: from [85.158.139.211:64515] by server-7.bemta-5.messagelabs.com id F7/38-08009-7086CE05; Tue, 08 Jan 2013 18:40:07 +0000 X-Env-Sender: jhom@softlayer.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1357670405!18260768!1 X-Originating-IP: [173.192.119.25] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5104 invoked from network); 8 Jan 2013 18:40:06 -0000 Received: from mx151.softlayer.com (HELO mx.softlayer.com) (173.192.119.25) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Jan 2013 18:40:06 -0000 Received: from mail.softlayer.com by mx.softlayer.com with esmtp (Exim) (envelope-from ) id 1Tse5l-000Ldv-2N; Tue, 08 Jan 2013 12:40:05 -0600 Received: from SM-CAS152.softlayer.local (172.18.18.40) by SM-TMG151.softlayer.local (172.18.18.50) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 8 Jan 2013 12:40:04 -0600 Received: from SM-DAG151.softlayer.local ([fe80::1588:d55b:b866:2177]) by SM-CAS152.softlayer.local ([fe80::1d67:e0d0:b649:4ab5%12]) with mapi id 14.02.0247.003; Tue, 8 Jan 2013 12:40:04 -0600 From: Joseph Hom To: George Shuklin Thread-Topic: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 Thread-Index: AQHN6t/ZCqYUoQd0n0ym4a/KjLYtEJg6lfoAgAAm0QCABWgiAP//oGlggABnOAD//5w5IA== Date: Tue, 8 Jan 2013 18:40:03 +0000 Message-ID: <602C5EB92F9AFB4D89D11B9F5B7F1355200AF149@SM-DAG151.softlayer.local> References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> <50EC66D2.8060304@gmail.com> In-Reply-To: <50EC66D2.8060304@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.176.170] MIME-Version: 1.0 X-DKIM-Status: none Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org U29ycnkgSSBtaXN0eXBlZCB0aGUgcGF0aC4gVGhlIGRldmljZSBwYXRoIGxpc3RlZCBpbiB0aGUg dmJkIGlzIHdoYXQgeW91IHNob3VsZCBiZSB1c2luZyBrcGFydHggb24NCg0KZS5nLg0KDQprcGFy dHggLWF2IC9kZXYvc20vYmFja2VuZC81NWVhMjBkMi04NjExLTExMjEtOWU5ZS1jMjZiMzVhYzE4 NTIvNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyDQoNClRoaXMgd2lsbCBleHBv c2UgdGhlIHBhcnRpdGlvbnMgd2hpY2ggeW91IGNhbiBmaW5kIGluIC9kZXYvbWFwcGVyLg0KDQot LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogR2VvcmdlIFNodWtsaW4gW21haWx0bzpn ZW9yZ2Uuc2h1a2xpbkBnbWFpbC5jb21dIA0KU2VudDogVHVlc2RheSwgSmFudWFyeSAwOCwgMjAx MyAxMjozNSBQTQ0KVG86IEpvc2VwaCBIb20NCkNjOiB4ZW4tYXBpQGxpc3RzLnhlbi5vcmcNClN1 YmplY3Q6IFJlOiBbWGVuLUFQSV0gbG9vayBpbnRvIFZIRCBWREkgZnJvbSBDb250cm9sIERvbWFp biBpbiBYQ1AgMS42DQoNClllcCwgYnV0IHdoYXQgdGhlIHV1aWQgaXMgdGhhdCAnNTVlYS4uLic/ IEkgeGVlIGl0IG5vd2hlcmUgaW4gcmVsYXRlZA0Kb2JqZWN0czoNCg0KdXVpZCAoIFJPKSAgICAg ICAgICAgICA6IDlhNGVlMjdiLWQ5OTAtNDg4Ny1mZjQ5LWUyYzFmYjEwMDA2MQ0KICAgICAgICAg ICB2bS11dWlkICggUk8pOiA1M2MzZDg3OC1iNjBiLTQ4ZWMtYWFhYy03M2Y3YWRmOWFiM2QNCiAg ICAgdm0tbmFtZS1sYWJlbCAoIFJPKTogQ29udHJvbCBkb21haW4gb24gaG9zdDogdGVzdA0KICAg ICAgICAgIHZkaS11dWlkICggUk8pOiA1ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1 MzINCiAgICAgICAgICAgICBlbXB0eSAoIFJPKTogZmFsc2UNCiAgICAgICAgICAgIGRldmljZSAo IFJPKTogDQpzbS9iYWNrZW5kLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi81 ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzINCg0KLi4uLi4NCg0KQWZ0ZXIgc29t ZSBndWVzc2luZzogdGhpcyBpcyBTUiB1dWlkLg0KDQp4ZSB2ZGktbGlzdCB1dWlkPTVlMmMzMWE1 LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMg0KdXVpZCAoIFJPKSAgICAgICAgICAgICAgICA6 IDVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMg0KICAgICAgICAgICBuYW1lLWxh YmVsICggUlcpOiB0ZXN0MQ0KICAgICBuYW1lLWRlc2NyaXB0aW9uICggUlcpOg0KICAgICAgICAg ICAgICBzci11dWlkICggUk8pOiA1NWVhMjBkMi04NjExLTExMjEtOWU5ZS1jMjZiMzVhYzE4NTIN CiAgICAgICAgIHZpcnR1YWwtc2l6ZSAoIFJPKTogMjE0NzQ4MzY0OA0KICAgICAgICAgICAgIHNo YXJhYmxlICggUk8pOiBmYWxzZQ0KICAgICAgICAgICAgcmVhZC1vbmx5ICggUk8pOiBmYWxzZQ0K DQoNCg0KMDguMDEuMjAxMyAyMjoyOSwgSm9zZXBoIEhvbSDQv9C40YjQtdGCOg0KPiBUaGF0IGlz IGR1ZSB0byB0aGUgbmV3IHNtIGJhY2tlbmQgdGhhdCB3YXMgaW50cm9kdWNlZC4gV2hlbiBhIHZi ZCBpcyANCj4gcGx1Z2dlZCBpbnRvIGRvbTAgaXMgbm8gbG9uZ2VyIHNob3dzIHVwIGFzIGEgc3Ry YWlnaHQgYmxvY2sgZGV2aWNlIA0KPiB1bmRlciAvZGV2Lw0KPg0KPiBUaGUgbmV3IHZlcnNpb24g b2YgeGUtZWRpdC1ib290bG9hZGVyIGFkZHJlc3NlcyB0aGlzIGFuZCBjYW4gYmUgdXNlZCBhcyBh IHBvaW50ZXIgb24gd2hhdCB0byBkby4NCj4NCj4gSGludDoga3BhcnR4IC1hdiAvZGV2L3NtL2Jh Y2tlbmQvNTVlYTIwZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyDQo+IGxzIC9kZXYvbWFw cGVyLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1MioNCj4NCj4gLS0tLS1Pcmln aW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogeGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmcg DQo+IFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmddIE9uIEJlaGFsZiBPZiBH ZW9yZ2UgU2h1a2xpbg0KPiBTZW50OiBUdWVzZGF5LCBKYW51YXJ5IDA4LCAyMDEzIDEyOjA4IFBN DQo+IFRvOiB4ZW4tYXBpQGxpc3RzLnhlbi5vcmcNCj4gU3ViamVjdDogUmU6IFtYZW4tQVBJXSBs b29rIGludG8gVkhEIFZESSBmcm9tIENvbnRyb2wgRG9tYWluIGluIFhDUCANCj4gMS42DQo+DQo+ IE9rLCBoZXJlIGltcG9ydGFudCBzdHVmZi4gV2hlbiBWQkQgaXMgcGx1Z2dlZCB0byBkb20wLCBp dCBwbHVnZ2luZyBub3QgYXMgJ25vcm1hbCcgZGV2aWNlICh3aXRoIHVkZXYgYXR0ZW50aW9uKSwg YnV0IGFzIGRldmljZSBpbiAvZGV2L3NtL2JhY2tlbmQuDQo+DQo+IEhlcmUgc2FtcGxlIGxvZyAo Y2hhbmdlIHV1aWRzIG9uIHlvdSB0YXN0ZSk6DQo+DQo+IHhlIHZiZC1jcmVhdGUgdm0tdXVpZD01 M2MzZDg3OC1iNjBiLTQ4ZWMtYWFhYy03M2Y3YWRmOWFiM2QNCj4gdmRpLXV1aWQ9NWUyYzMxYTUt MWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyIGRldmljZT02IHhlIHZiZC1wbHVnIA0KPiB1dWlk PTQwN2ViM2E2LTkxOWYtZjYwNS0wODgzLWUxMmFhYTkxMzIxZA0KPg0KPiBscyAtbGEgL2Rldi9z bS9iYWNrZW5kLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi8NCj4g0LjRgtC+ 0LPQviA0DQo+IGRyd3hyLXhyLXggMiByb290IHJvb3QgICAgIDgwINCv0L3QsiAgOCAyMTo1NyAu DQo+IGRyd3hyLXhyLXggMyByb290IHJvb3QgICAgIDYwINCU0LXQuiAxOCAxNzo0MCAuLg0KPiBi cnctLS0tLS0tIDEgcm9vdCByb290IDI1MywgMCDQr9C90LIgIDggMjE6NTcNCj4gNWUyYzMxYTUt MWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyDQo+IC1ydy1yLS1yLS0gMSByb290IHJvb3QgICAg ODUyINCv0L3QsiAgOCAyMTo1Nw0KPiA1ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1 MzIuYXR0YWNoX2luZm8NCj4NCj4gSSBoYXZlIG5vIGlkZWEgd2h5ICc1NScgdXVpZCAoYW5kIHdo YXQgaXQgbWVhbnMpLCBidXQNCj4gNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMy IGlzIGJsb2NrIGRldmljZSBhZnRlciB3aG9sZSBWSEQgdHJlZSBqb2luaW5nL3BhcnNpbmcgYW5k IHNvIG9uLg0KPg0KPiBZb3UgY2FuIHNlZSBhY3R1YWwgcGF0aCBpbiB4ZSB2YmQtbGlzdCBvdXRw dXQgKGRldmljZSBmaWVsZCkuDQo+DQo+IDA1LjAxLjIwMTMgMTE6MzMsIEFsZXhhbmRyZSBLb3V6 bmV0c292INC/0LjRiNC10YI6DQo+PiBIZWxsby4NCj4+DQo+PiBFbCAwNC8wMS8xMyAyMzoxNCwg R2VvcmdlIFNodWtsaW4gZXNjcmliacOzOg0KPj4+IFVzZSB4ZSB2YmQtY3JlYXRlIGJldHdlZW4g dmRpIGFuZCBkb20wICh3aGljaCBpcyBub3JtYWwgVk0gbW9zdGx5KSwgDQo+Pj4gYW5kIHhlIHZi ZC1wbHVnLg0KPj4gWWVzLCB0aGF0J3Mgd2hhdCBJIGhhdmUgZG9uZSBmb2xsb3dpbmcgdGhlIGV4 YW1wbGUgZnJvbSBDaXRyaXggZm9ydW0uDQo+Pg0KPj4gSW4gY2FzZSBvZiBhIG5vcm1hbCBEb21V Og0KPj4gSSBjcmVhdGUgVkJEIGxpbmtpbmcgdGhlIFZNIHdpdGggVkRJLCBJIGlzc3VlIHZiZC1w bHVnLCB0aGUgYmxvY2sgDQo+PiBkZXZpY2UgYmVjb21lcyB2aXNpYmxlIGluIGRtZXNnIHVuZGVy IERvbVUuDQo+Pg0KPj4gSW4gY2FzZSBvZiBEb20wOg0KPj4gSSBjcmVhdGUgVkJEIGxpbmtpbmcg dGhlIFZNICh2bS1saXN0IHJlZmVycyB0byBpdCBhcyAiQ29udHJvbCANCj4+IERvbWFpbiIsIG5v IG1pc3Rha2UpIHdpdGggVkRJLCBJIGlzc3VlIHZiZC1wbHVnLCBubyBzaWduIG9mIHRoZSBuZXcg DQo+PiBibG9jayBkZXZpY2UgaW4gZG1lc2cgb3IgdW5kZXIgL2Rldi4NCj4+DQo+Pj4gWW91IGNh biBzZWUgc29tZSBzYW1wbGUgdXNhZ2UgaW4gJ3hlLWVkaXQtYm9vdGxvYWRlcicgY29tbWFuZCAN Cj4+PiAoc29tZXdoZXJlIGluIC9vcHQveGVuc291cmNlLykNCj4+IEhtLiBJIGJlbGlldmUgSSdt IGRvaW5nIGl0IGp1c3QgdGhlIHNhbWUgd2F5IGFzIGluIHRoZSBzY3JpcHQsIGV4Y2VwdCANCj4+ IGJ5IHRoZSAiZGV2aWNlPSIgZGlyZWN0aXZlIGZvciB2YmQtY3JlYXRlLCB1c2Ugc3BlY2lmaWMg c3RyaW5nIGxpa2UgDQo+PiAieHZkbiIuDQo+PiBTaG91bGQgaXQgbWFrZSB0aGUgZGlmZmVyZW5j ZT8gQ2FuJ3QgdGVzdCwgSSBzaG90IGRvd24gbXkgdGVzdGluZyANCj4+IHJhbmdlIGJlZm9yZSBs ZWF2aW5nIHRoZSBvZmZpY2UuDQo+Pg0KPj4gU28sIG11c3QgSSB1bmRlcnN0YW5kIHRoYXQgdGhl IFhDUCdzIHJlZ3VsYXIgd2F5IG9mIG1hbmlwdWxhdGluZyANCj4+IFZESSdzIGNvbnRlbnRzIGZy b20gd2l0aGluIERvbTAsIGlzIGF0dGFjaGluZyB0aGUgVkRJIHRvIGl0IHZpYSBhIFZCRD8NCj4+ IExvb2tzIGxpa2UgYSBnb29kIGFic3RyYWN0aW9uLCBleGNlcHQgdGhhdCBpdCB3b24ndCB3b3Jr IHRoYXQgZWFzaWx5IA0KPj4gb24gYSBob3N0IHdpdGhvdXQgWENQIGluZnJhc3RydWN0dXJlIChm b3IgZXhhbXBsZSwgaW4gc29tZSByZXNjdWUgDQo+PiBzY2VuYXJpbykuDQo+Pg0KPj4gVGhlbiwg d2hhdCB2aGRwYXJ0eCBpcyBnb29kIGZvcj8NCj4+DQo+PiBDaGVlcnMuDQo+Pg0KPj4NCj4+IF9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBYZW4tYXBp IG1haWxpbmcgbGlzdA0KPj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnDQo+PiBodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQ0KPg0KPiBfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBYZW4tYXBpIG1haWxpbmcg bGlzdA0KPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcNCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkNCg0KX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0 cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94 ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Tue Jan 08 18:40:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 18:40:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse5q-0007Rn-BP; Tue, 08 Jan 2013 18:40:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse5o-0007Re-E9 for xen-api@lists.xen.org; Tue, 08 Jan 2013 18:40:08 +0000 Received: from [85.158.139.211:64515] by server-7.bemta-5.messagelabs.com id F7/38-08009-7086CE05; Tue, 08 Jan 2013 18:40:07 +0000 X-Env-Sender: jhom@softlayer.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1357670405!18260768!1 X-Originating-IP: [173.192.119.25] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5104 invoked from network); 8 Jan 2013 18:40:06 -0000 Received: from mx151.softlayer.com (HELO mx.softlayer.com) (173.192.119.25) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Jan 2013 18:40:06 -0000 Received: from mail.softlayer.com by mx.softlayer.com with esmtp (Exim) (envelope-from ) id 1Tse5l-000Ldv-2N; Tue, 08 Jan 2013 12:40:05 -0600 Received: from SM-CAS152.softlayer.local (172.18.18.40) by SM-TMG151.softlayer.local (172.18.18.50) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 8 Jan 2013 12:40:04 -0600 Received: from SM-DAG151.softlayer.local ([fe80::1588:d55b:b866:2177]) by SM-CAS152.softlayer.local ([fe80::1d67:e0d0:b649:4ab5%12]) with mapi id 14.02.0247.003; Tue, 8 Jan 2013 12:40:04 -0600 From: Joseph Hom To: George Shuklin Thread-Topic: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 Thread-Index: AQHN6t/ZCqYUoQd0n0ym4a/KjLYtEJg6lfoAgAAm0QCABWgiAP//oGlggABnOAD//5w5IA== Date: Tue, 8 Jan 2013 18:40:03 +0000 Message-ID: <602C5EB92F9AFB4D89D11B9F5B7F1355200AF149@SM-DAG151.softlayer.local> References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> <50EC66D2.8060304@gmail.com> In-Reply-To: <50EC66D2.8060304@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.176.170] MIME-Version: 1.0 X-DKIM-Status: none Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org U29ycnkgSSBtaXN0eXBlZCB0aGUgcGF0aC4gVGhlIGRldmljZSBwYXRoIGxpc3RlZCBpbiB0aGUg dmJkIGlzIHdoYXQgeW91IHNob3VsZCBiZSB1c2luZyBrcGFydHggb24NCg0KZS5nLg0KDQprcGFy dHggLWF2IC9kZXYvc20vYmFja2VuZC81NWVhMjBkMi04NjExLTExMjEtOWU5ZS1jMjZiMzVhYzE4 NTIvNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyDQoNClRoaXMgd2lsbCBleHBv c2UgdGhlIHBhcnRpdGlvbnMgd2hpY2ggeW91IGNhbiBmaW5kIGluIC9kZXYvbWFwcGVyLg0KDQot LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogR2VvcmdlIFNodWtsaW4gW21haWx0bzpn ZW9yZ2Uuc2h1a2xpbkBnbWFpbC5jb21dIA0KU2VudDogVHVlc2RheSwgSmFudWFyeSAwOCwgMjAx MyAxMjozNSBQTQ0KVG86IEpvc2VwaCBIb20NCkNjOiB4ZW4tYXBpQGxpc3RzLnhlbi5vcmcNClN1 YmplY3Q6IFJlOiBbWGVuLUFQSV0gbG9vayBpbnRvIFZIRCBWREkgZnJvbSBDb250cm9sIERvbWFp biBpbiBYQ1AgMS42DQoNClllcCwgYnV0IHdoYXQgdGhlIHV1aWQgaXMgdGhhdCAnNTVlYS4uLic/ IEkgeGVlIGl0IG5vd2hlcmUgaW4gcmVsYXRlZA0Kb2JqZWN0czoNCg0KdXVpZCAoIFJPKSAgICAg ICAgICAgICA6IDlhNGVlMjdiLWQ5OTAtNDg4Ny1mZjQ5LWUyYzFmYjEwMDA2MQ0KICAgICAgICAg ICB2bS11dWlkICggUk8pOiA1M2MzZDg3OC1iNjBiLTQ4ZWMtYWFhYy03M2Y3YWRmOWFiM2QNCiAg ICAgdm0tbmFtZS1sYWJlbCAoIFJPKTogQ29udHJvbCBkb21haW4gb24gaG9zdDogdGVzdA0KICAg ICAgICAgIHZkaS11dWlkICggUk8pOiA1ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1 MzINCiAgICAgICAgICAgICBlbXB0eSAoIFJPKTogZmFsc2UNCiAgICAgICAgICAgIGRldmljZSAo IFJPKTogDQpzbS9iYWNrZW5kLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi81 ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzINCg0KLi4uLi4NCg0KQWZ0ZXIgc29t ZSBndWVzc2luZzogdGhpcyBpcyBTUiB1dWlkLg0KDQp4ZSB2ZGktbGlzdCB1dWlkPTVlMmMzMWE1 LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMg0KdXVpZCAoIFJPKSAgICAgICAgICAgICAgICA6 IDVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMg0KICAgICAgICAgICBuYW1lLWxh YmVsICggUlcpOiB0ZXN0MQ0KICAgICBuYW1lLWRlc2NyaXB0aW9uICggUlcpOg0KICAgICAgICAg ICAgICBzci11dWlkICggUk8pOiA1NWVhMjBkMi04NjExLTExMjEtOWU5ZS1jMjZiMzVhYzE4NTIN CiAgICAgICAgIHZpcnR1YWwtc2l6ZSAoIFJPKTogMjE0NzQ4MzY0OA0KICAgICAgICAgICAgIHNo YXJhYmxlICggUk8pOiBmYWxzZQ0KICAgICAgICAgICAgcmVhZC1vbmx5ICggUk8pOiBmYWxzZQ0K DQoNCg0KMDguMDEuMjAxMyAyMjoyOSwgSm9zZXBoIEhvbSDQv9C40YjQtdGCOg0KPiBUaGF0IGlz IGR1ZSB0byB0aGUgbmV3IHNtIGJhY2tlbmQgdGhhdCB3YXMgaW50cm9kdWNlZC4gV2hlbiBhIHZi ZCBpcyANCj4gcGx1Z2dlZCBpbnRvIGRvbTAgaXMgbm8gbG9uZ2VyIHNob3dzIHVwIGFzIGEgc3Ry YWlnaHQgYmxvY2sgZGV2aWNlIA0KPiB1bmRlciAvZGV2Lw0KPg0KPiBUaGUgbmV3IHZlcnNpb24g b2YgeGUtZWRpdC1ib290bG9hZGVyIGFkZHJlc3NlcyB0aGlzIGFuZCBjYW4gYmUgdXNlZCBhcyBh IHBvaW50ZXIgb24gd2hhdCB0byBkby4NCj4NCj4gSGludDoga3BhcnR4IC1hdiAvZGV2L3NtL2Jh Y2tlbmQvNTVlYTIwZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyDQo+IGxzIC9kZXYvbWFw cGVyLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1MioNCj4NCj4gLS0tLS1Pcmln aW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogeGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmcg DQo+IFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmddIE9uIEJlaGFsZiBPZiBH ZW9yZ2UgU2h1a2xpbg0KPiBTZW50OiBUdWVzZGF5LCBKYW51YXJ5IDA4LCAyMDEzIDEyOjA4IFBN DQo+IFRvOiB4ZW4tYXBpQGxpc3RzLnhlbi5vcmcNCj4gU3ViamVjdDogUmU6IFtYZW4tQVBJXSBs b29rIGludG8gVkhEIFZESSBmcm9tIENvbnRyb2wgRG9tYWluIGluIFhDUCANCj4gMS42DQo+DQo+ IE9rLCBoZXJlIGltcG9ydGFudCBzdHVmZi4gV2hlbiBWQkQgaXMgcGx1Z2dlZCB0byBkb20wLCBp dCBwbHVnZ2luZyBub3QgYXMgJ25vcm1hbCcgZGV2aWNlICh3aXRoIHVkZXYgYXR0ZW50aW9uKSwg YnV0IGFzIGRldmljZSBpbiAvZGV2L3NtL2JhY2tlbmQuDQo+DQo+IEhlcmUgc2FtcGxlIGxvZyAo Y2hhbmdlIHV1aWRzIG9uIHlvdSB0YXN0ZSk6DQo+DQo+IHhlIHZiZC1jcmVhdGUgdm0tdXVpZD01 M2MzZDg3OC1iNjBiLTQ4ZWMtYWFhYy03M2Y3YWRmOWFiM2QNCj4gdmRpLXV1aWQ9NWUyYzMxYTUt MWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyIGRldmljZT02IHhlIHZiZC1wbHVnIA0KPiB1dWlk PTQwN2ViM2E2LTkxOWYtZjYwNS0wODgzLWUxMmFhYTkxMzIxZA0KPg0KPiBscyAtbGEgL2Rldi9z bS9iYWNrZW5kLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi8NCj4g0LjRgtC+ 0LPQviA0DQo+IGRyd3hyLXhyLXggMiByb290IHJvb3QgICAgIDgwINCv0L3QsiAgOCAyMTo1NyAu DQo+IGRyd3hyLXhyLXggMyByb290IHJvb3QgICAgIDYwINCU0LXQuiAxOCAxNzo0MCAuLg0KPiBi cnctLS0tLS0tIDEgcm9vdCByb290IDI1MywgMCDQr9C90LIgIDggMjE6NTcNCj4gNWUyYzMxYTUt MWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyDQo+IC1ydy1yLS1yLS0gMSByb290IHJvb3QgICAg ODUyINCv0L3QsiAgOCAyMTo1Nw0KPiA1ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1 MzIuYXR0YWNoX2luZm8NCj4NCj4gSSBoYXZlIG5vIGlkZWEgd2h5ICc1NScgdXVpZCAoYW5kIHdo YXQgaXQgbWVhbnMpLCBidXQNCj4gNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMy IGlzIGJsb2NrIGRldmljZSBhZnRlciB3aG9sZSBWSEQgdHJlZSBqb2luaW5nL3BhcnNpbmcgYW5k IHNvIG9uLg0KPg0KPiBZb3UgY2FuIHNlZSBhY3R1YWwgcGF0aCBpbiB4ZSB2YmQtbGlzdCBvdXRw dXQgKGRldmljZSBmaWVsZCkuDQo+DQo+IDA1LjAxLjIwMTMgMTE6MzMsIEFsZXhhbmRyZSBLb3V6 bmV0c292INC/0LjRiNC10YI6DQo+PiBIZWxsby4NCj4+DQo+PiBFbCAwNC8wMS8xMyAyMzoxNCwg R2VvcmdlIFNodWtsaW4gZXNjcmliacOzOg0KPj4+IFVzZSB4ZSB2YmQtY3JlYXRlIGJldHdlZW4g dmRpIGFuZCBkb20wICh3aGljaCBpcyBub3JtYWwgVk0gbW9zdGx5KSwgDQo+Pj4gYW5kIHhlIHZi ZC1wbHVnLg0KPj4gWWVzLCB0aGF0J3Mgd2hhdCBJIGhhdmUgZG9uZSBmb2xsb3dpbmcgdGhlIGV4 YW1wbGUgZnJvbSBDaXRyaXggZm9ydW0uDQo+Pg0KPj4gSW4gY2FzZSBvZiBhIG5vcm1hbCBEb21V Og0KPj4gSSBjcmVhdGUgVkJEIGxpbmtpbmcgdGhlIFZNIHdpdGggVkRJLCBJIGlzc3VlIHZiZC1w bHVnLCB0aGUgYmxvY2sgDQo+PiBkZXZpY2UgYmVjb21lcyB2aXNpYmxlIGluIGRtZXNnIHVuZGVy IERvbVUuDQo+Pg0KPj4gSW4gY2FzZSBvZiBEb20wOg0KPj4gSSBjcmVhdGUgVkJEIGxpbmtpbmcg dGhlIFZNICh2bS1saXN0IHJlZmVycyB0byBpdCBhcyAiQ29udHJvbCANCj4+IERvbWFpbiIsIG5v IG1pc3Rha2UpIHdpdGggVkRJLCBJIGlzc3VlIHZiZC1wbHVnLCBubyBzaWduIG9mIHRoZSBuZXcg DQo+PiBibG9jayBkZXZpY2UgaW4gZG1lc2cgb3IgdW5kZXIgL2Rldi4NCj4+DQo+Pj4gWW91IGNh biBzZWUgc29tZSBzYW1wbGUgdXNhZ2UgaW4gJ3hlLWVkaXQtYm9vdGxvYWRlcicgY29tbWFuZCAN Cj4+PiAoc29tZXdoZXJlIGluIC9vcHQveGVuc291cmNlLykNCj4+IEhtLiBJIGJlbGlldmUgSSdt IGRvaW5nIGl0IGp1c3QgdGhlIHNhbWUgd2F5IGFzIGluIHRoZSBzY3JpcHQsIGV4Y2VwdCANCj4+ IGJ5IHRoZSAiZGV2aWNlPSIgZGlyZWN0aXZlIGZvciB2YmQtY3JlYXRlLCB1c2Ugc3BlY2lmaWMg c3RyaW5nIGxpa2UgDQo+PiAieHZkbiIuDQo+PiBTaG91bGQgaXQgbWFrZSB0aGUgZGlmZmVyZW5j ZT8gQ2FuJ3QgdGVzdCwgSSBzaG90IGRvd24gbXkgdGVzdGluZyANCj4+IHJhbmdlIGJlZm9yZSBs ZWF2aW5nIHRoZSBvZmZpY2UuDQo+Pg0KPj4gU28sIG11c3QgSSB1bmRlcnN0YW5kIHRoYXQgdGhl IFhDUCdzIHJlZ3VsYXIgd2F5IG9mIG1hbmlwdWxhdGluZyANCj4+IFZESSdzIGNvbnRlbnRzIGZy b20gd2l0aGluIERvbTAsIGlzIGF0dGFjaGluZyB0aGUgVkRJIHRvIGl0IHZpYSBhIFZCRD8NCj4+ IExvb2tzIGxpa2UgYSBnb29kIGFic3RyYWN0aW9uLCBleGNlcHQgdGhhdCBpdCB3b24ndCB3b3Jr IHRoYXQgZWFzaWx5IA0KPj4gb24gYSBob3N0IHdpdGhvdXQgWENQIGluZnJhc3RydWN0dXJlIChm b3IgZXhhbXBsZSwgaW4gc29tZSByZXNjdWUgDQo+PiBzY2VuYXJpbykuDQo+Pg0KPj4gVGhlbiwg d2hhdCB2aGRwYXJ0eCBpcyBnb29kIGZvcj8NCj4+DQo+PiBDaGVlcnMuDQo+Pg0KPj4NCj4+IF9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBYZW4tYXBp IG1haWxpbmcgbGlzdA0KPj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnDQo+PiBodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQ0KPg0KPiBfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBYZW4tYXBpIG1haWxpbmcg bGlzdA0KPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcNCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkNCg0KX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0 cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94 ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Tue Jan 08 21:52:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 21:52:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsh5T-0003Iy-DL; Tue, 08 Jan 2013 21:51:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tsh5R-0003Iq-UJ; Tue, 08 Jan 2013 21:51:58 +0000 Received: from [85.158.139.211:22268] by server-9.bemta-5.messagelabs.com id 66/92-10690-DF49CE05; Tue, 08 Jan 2013 21:51:57 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1357681915!18299387!1 X-Originating-IP: [209.85.216.172] X-SpamReason: No, hits=1.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_SUBJECT,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6627 invoked from network); 8 Jan 2013 21:51:56 -0000 Received: from mail-qc0-f172.google.com (HELO mail-qc0-f172.google.com) (209.85.216.172) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 21:51:56 -0000 Received: by mail-qc0-f172.google.com with SMTP id b25so1110489qca.17 for ; Tue, 08 Jan 2013 13:51:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=GAtm7oTZjxXhQFHLb71BfQ/by6aAWtCYkH0dKae65U8=; b=sRVvtEhkQv60kdFOx0vglEqvrNKbA0yxsx5wNUaxjxxOAOKYsoahD0PfV2lU7Y0tze QBEIjXZ3UonUuBOpuWR8mEXdDNqP3o4BKtSkPqe5SwEYn9lio9as5MfCBw9Z5NMan4oy R7i2US3Iv7ZbrzEY6bRostb8Ddc0dH0iDpS2L5e/6zMiDQP/7UYNJu0oG9SdWzswbosr +IXS2cgHkimuV/41+wcjPhYjcYfvvqD64o1CsFcLiW0fFOOwFlpCcRSGblMQimpNbBgm D2EH7prImZbuj2Sek11d5z7475DrEirJhlVY2m5c51u6U6YlXwWH2gCN2X5q8WUszgx9 ju7g== MIME-Version: 1.0 Received: by 10.49.12.138 with SMTP id y10mr55335468qeb.64.1357681915018; Tue, 08 Jan 2013 13:51:55 -0800 (PST) Received: by 10.229.17.19 with HTTP; Tue, 8 Jan 2013 13:51:54 -0800 (PST) Date: Wed, 9 Jan 2013 03:21:54 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: "xen-api@lists.xen.org" , xen-devel@lists.xen.org Subject: [Xen-API] (no subject) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7711660698561388892==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7711660698561388892== Content-Type: multipart/alternative; boundary=047d7b6d88b2433e9804d2cdf4fd --047d7b6d88b2433e9804d2cdf4fd Content-Type: text/plain; charset=ISO-8859-1 Hello List, Please help me in diagnosing below error in /var/log/messages HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: fffff8800d099000 Im unable to find any google reference related to above C file or its source code. http://lmgtfy.com/?q=txftrans.c Thanks for reading and helping. Regards, Rushikesh --047d7b6d88b2433e9804d2cdf4fd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello List,

Please help m= e in diagnosing below error in /var/log/messages

HVM1[16586]:=A0 txf= trans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: fffff8800d099000
Im unable to find any google reference related to above C file or its= source code. http://lmgtfy.c= om/?q=3Dtxftrans.c

Thanks for reading and helping.

=
Regards,
Rushikesh
--047d7b6d88b2433e9804d2cdf4fd-- --===============7711660698561388892== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7711660698561388892==-- From xen-api-bounces@lists.xen.org Tue Jan 08 21:52:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 21:52:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsh5T-0003Iy-DL; Tue, 08 Jan 2013 21:51:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tsh5R-0003Iq-UJ; Tue, 08 Jan 2013 21:51:58 +0000 Received: from [85.158.139.211:22268] by server-9.bemta-5.messagelabs.com id 66/92-10690-DF49CE05; Tue, 08 Jan 2013 21:51:57 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1357681915!18299387!1 X-Originating-IP: [209.85.216.172] X-SpamReason: No, hits=1.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_SUBJECT,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6627 invoked from network); 8 Jan 2013 21:51:56 -0000 Received: from mail-qc0-f172.google.com (HELO mail-qc0-f172.google.com) (209.85.216.172) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 21:51:56 -0000 Received: by mail-qc0-f172.google.com with SMTP id b25so1110489qca.17 for ; Tue, 08 Jan 2013 13:51:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=GAtm7oTZjxXhQFHLb71BfQ/by6aAWtCYkH0dKae65U8=; b=sRVvtEhkQv60kdFOx0vglEqvrNKbA0yxsx5wNUaxjxxOAOKYsoahD0PfV2lU7Y0tze QBEIjXZ3UonUuBOpuWR8mEXdDNqP3o4BKtSkPqe5SwEYn9lio9as5MfCBw9Z5NMan4oy R7i2US3Iv7ZbrzEY6bRostb8Ddc0dH0iDpS2L5e/6zMiDQP/7UYNJu0oG9SdWzswbosr +IXS2cgHkimuV/41+wcjPhYjcYfvvqD64o1CsFcLiW0fFOOwFlpCcRSGblMQimpNbBgm D2EH7prImZbuj2Sek11d5z7475DrEirJhlVY2m5c51u6U6YlXwWH2gCN2X5q8WUszgx9 ju7g== MIME-Version: 1.0 Received: by 10.49.12.138 with SMTP id y10mr55335468qeb.64.1357681915018; Tue, 08 Jan 2013 13:51:55 -0800 (PST) Received: by 10.229.17.19 with HTTP; Tue, 8 Jan 2013 13:51:54 -0800 (PST) Date: Wed, 9 Jan 2013 03:21:54 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: "xen-api@lists.xen.org" , xen-devel@lists.xen.org Subject: [Xen-API] (no subject) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7711660698561388892==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7711660698561388892== Content-Type: multipart/alternative; boundary=047d7b6d88b2433e9804d2cdf4fd --047d7b6d88b2433e9804d2cdf4fd Content-Type: text/plain; charset=ISO-8859-1 Hello List, Please help me in diagnosing below error in /var/log/messages HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: fffff8800d099000 Im unable to find any google reference related to above C file or its source code. http://lmgtfy.com/?q=txftrans.c Thanks for reading and helping. Regards, Rushikesh --047d7b6d88b2433e9804d2cdf4fd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello List,

Please help m= e in diagnosing below error in /var/log/messages

HVM1[16586]:=A0 txf= trans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: fffff8800d099000
Im unable to find any google reference related to above C file or its= source code. http://lmgtfy.c= om/?q=3Dtxftrans.c

Thanks for reading and helping.

=
Regards,
Rushikesh
--047d7b6d88b2433e9804d2cdf4fd-- --===============7711660698561388892== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7711660698561388892==-- From xen-api-bounces@lists.xen.org Tue Jan 08 21:53:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 21:53:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsh6z-0003LZ-PD; Tue, 08 Jan 2013 21:53:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tsh6y-0003LP-Nd; Tue, 08 Jan 2013 21:53:32 +0000 Received: from [85.158.139.211:50249] by server-16.bemta-5.messagelabs.com id 06/74-09208-B559CE05; Tue, 08 Jan 2013 21:53:31 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1357682008!22571032!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13397 invoked from network); 8 Jan 2013 21:53:29 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 21:53:29 -0000 Received: by mail-qc0-f181.google.com with SMTP id x40so1129751qcp.12 for ; Tue, 08 Jan 2013 13:53:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=H2B+JQ1seisuehSwg+W40vEAGF0FsViKNxR3iRfx7Xc=; b=FdNKU/V2f5s+YCE1kC/cY4pGPrUFWVJUyDQfBJWgbhLosHxysU2waK8WHkiY9C6ezF YJaV8YGTIVfeWOX3Amt+XGcvIGkbgADM9N/PFdLdMNZog50nBLY++vi558penaEZcpt6 clM1fuCtJiR0P5KKVpJ/tz1e/ENnxQedbg/mCEHiCLREYsmiF0HQY3KyqO3Bg2l+40n/ PGTvRCchXWEmv6pFrVkv0fM8bsG2A6t2BQS8ugSBNKgCGHp7yQLZxKwdEnmGS6a5+/cO 68T4/XkZCtYLKWvutw4qOzBgyC7pThPGgw7KmieqvLsaTm5dLBOIliEyfcfQLLLCFVMz tLkA== MIME-Version: 1.0 Received: by 10.224.180.69 with SMTP id bt5mr47418532qab.36.1357682008046; Tue, 08 Jan 2013 13:53:28 -0800 (PST) Received: by 10.229.17.19 with HTTP; Tue, 8 Jan 2013 13:53:27 -0800 (PST) Date: Wed, 9 Jan 2013 03:23:27 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: "xen-api@lists.xen.org" , xen-devel@lists.xen.org Subject: Re: [Xen-API] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2100972586679822670==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2100972586679822670== Content-Type: multipart/alternative; boundary=20cf303b3b05cebac804d2cdf909 --20cf303b3b05cebac804d2cdf909 Content-Type: text/plain; charset=ISO-8859-1 Apologies for missing Subject. On Wed, Jan 9, 2013 at 3:21 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: > Hello List, > > Please help me in diagnosing below error in /var/log/messages > > HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: > fffff8800d099000 > > Im unable to find any google reference related to above C file or its > source code. http://lmgtfy.com/?q=txftrans.c > > Thanks for reading and helping. > > Regards, > Rushikesh > --20cf303b3b05cebac804d2cdf909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Apologies for missing Subject.

On Wed, Ja= n 9, 2013 at 3:21 AM, Rushikesh Jadhav <2rushikeshj@gmail.com><= /span> wrote:
Hello L= ist,

Please help me in diagnosing below error in /var/log/mess= ages

HVM1[16586]:=A0 txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: = fffff8800d099000

Im unable to find any google reference related to above C file or its= source code. http://lmgtfy.com/?q=3Dtxftrans.c

Thanks for reading an= d helping.

Regards,
Rushikesh

--20cf303b3b05cebac804d2cdf909-- --===============2100972586679822670== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2100972586679822670==-- From xen-api-bounces@lists.xen.org Tue Jan 08 21:53:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 21:53:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsh6z-0003LZ-PD; Tue, 08 Jan 2013 21:53:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tsh6y-0003LP-Nd; Tue, 08 Jan 2013 21:53:32 +0000 Received: from [85.158.139.211:50249] by server-16.bemta-5.messagelabs.com id 06/74-09208-B559CE05; Tue, 08 Jan 2013 21:53:31 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1357682008!22571032!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13397 invoked from network); 8 Jan 2013 21:53:29 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 21:53:29 -0000 Received: by mail-qc0-f181.google.com with SMTP id x40so1129751qcp.12 for ; Tue, 08 Jan 2013 13:53:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=H2B+JQ1seisuehSwg+W40vEAGF0FsViKNxR3iRfx7Xc=; b=FdNKU/V2f5s+YCE1kC/cY4pGPrUFWVJUyDQfBJWgbhLosHxysU2waK8WHkiY9C6ezF YJaV8YGTIVfeWOX3Amt+XGcvIGkbgADM9N/PFdLdMNZog50nBLY++vi558penaEZcpt6 clM1fuCtJiR0P5KKVpJ/tz1e/ENnxQedbg/mCEHiCLREYsmiF0HQY3KyqO3Bg2l+40n/ PGTvRCchXWEmv6pFrVkv0fM8bsG2A6t2BQS8ugSBNKgCGHp7yQLZxKwdEnmGS6a5+/cO 68T4/XkZCtYLKWvutw4qOzBgyC7pThPGgw7KmieqvLsaTm5dLBOIliEyfcfQLLLCFVMz tLkA== MIME-Version: 1.0 Received: by 10.224.180.69 with SMTP id bt5mr47418532qab.36.1357682008046; Tue, 08 Jan 2013 13:53:28 -0800 (PST) Received: by 10.229.17.19 with HTTP; Tue, 8 Jan 2013 13:53:27 -0800 (PST) Date: Wed, 9 Jan 2013 03:23:27 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: "xen-api@lists.xen.org" , xen-devel@lists.xen.org Subject: Re: [Xen-API] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2100972586679822670==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2100972586679822670== Content-Type: multipart/alternative; boundary=20cf303b3b05cebac804d2cdf909 --20cf303b3b05cebac804d2cdf909 Content-Type: text/plain; charset=ISO-8859-1 Apologies for missing Subject. On Wed, Jan 9, 2013 at 3:21 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: > Hello List, > > Please help me in diagnosing below error in /var/log/messages > > HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: > fffff8800d099000 > > Im unable to find any google reference related to above C file or its > source code. http://lmgtfy.com/?q=txftrans.c > > Thanks for reading and helping. > > Regards, > Rushikesh > --20cf303b3b05cebac804d2cdf909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Apologies for missing Subject.

On Wed, Ja= n 9, 2013 at 3:21 AM, Rushikesh Jadhav <2rushikeshj@gmail.com><= /span> wrote:
Hello L= ist,

Please help me in diagnosing below error in /var/log/mess= ages

HVM1[16586]:=A0 txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: = fffff8800d099000

Im unable to find any google reference related to above C file or its= source code. http://lmgtfy.com/?q=3Dtxftrans.c

Thanks for reading an= d helping.

Regards,
Rushikesh

--20cf303b3b05cebac804d2cdf909-- --===============2100972586679822670== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2100972586679822670==-- From xen-api-bounces@lists.xen.org Tue Jan 08 23:44:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 23:44:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsiqe-0004TW-EH; Tue, 08 Jan 2013 23:44:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsiqd-0004TR-Qr for xen-api@lists.xensource.com; Tue, 08 Jan 2013 23:44:48 +0000 Received: from [85.158.138.51:29083] by server-12.bemta-3.messagelabs.com id 41/58-27559-A6FACE05; Tue, 08 Jan 2013 23:44:42 +0000 X-Env-Sender: eduardo.terra@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1357688681!25599811!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7163 invoked from network); 8 Jan 2013 23:44:42 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 23:44:42 -0000 Received: by mail-lb0-f173.google.com with SMTP id c1so802552lbg.4 for ; Tue, 08 Jan 2013 15:44:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=GLpqnIstZ5Y9MuvJhlr6BiAc2S7/ET6kWsR+/dkIB98=; b=RAslZzL0F5Yx4ZIilrP7gH8mH9/Ku+w+H++T4R2TfNqrsRjEQ37gAaJJX6qNxpStpt T2vMcuIWh/OTDT1wmzOWyYuciZYRk/D81LoQUFCvJHBgjxWENwFjg1Ep/szXcn4x9BGR lILdCuqV/WdcLmTjNq0FW0Yjlm82efMj7XHJ6hUtG2wL5IM6yo2GULjPy9ggeQ/7FcJz YM8EIhmO2KK6ItmJo5EkDSfCCsRJ1R1wThMQZ6K5XW7ImQt0DtTOa2f6DVtm1KnAzjwQ Xa3Kpd4lE67TXILvlImlJBRj2a9yDW4wRMRyr+dW19Xv8YB9Dqp4ZB1Uhprq8uGqPiqb dIow== Received: by 10.152.47.75 with SMTP id b11mr62254406lan.14.1357688681185; Tue, 08 Jan 2013 15:44:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.57.3 with HTTP; Tue, 8 Jan 2013 15:44:21 -0800 (PST) From: Carlos Eduardo Tavares Terra Date: Tue, 8 Jan 2013 21:44:21 -0200 Message-ID: To: "xen-api@lists.xensource.com" Subject: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4995640525462309325==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4995640525462309325== Content-Type: multipart/alternative; boundary=bcaec55404a28ec06604d2cf875a --bcaec55404a28ec06604d2cf875a Content-Type: text/plain; charset=ISO-8859-1 I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. Is it possible? Do I have to check anything? I have done some fixes to work with XenCenter. Thanks -- Carlos Eduardo Tavares Terra Red Hat Certified Engineer Consultor em Infraestrutura de TI GNU/Linux #413291 [http://counter.li.org] --bcaec55404a28ec06604d2cf875a Content-Type: text/html; charset=ISO-8859-1
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org]
--bcaec55404a28ec06604d2cf875a-- --===============4995640525462309325== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4995640525462309325==-- From xen-api-bounces@lists.xen.org Tue Jan 08 23:44:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 08 Jan 2013 23:44:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsiqe-0004TW-EH; Tue, 08 Jan 2013 23:44:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsiqd-0004TR-Qr for xen-api@lists.xensource.com; Tue, 08 Jan 2013 23:44:48 +0000 Received: from [85.158.138.51:29083] by server-12.bemta-3.messagelabs.com id 41/58-27559-A6FACE05; Tue, 08 Jan 2013 23:44:42 +0000 X-Env-Sender: eduardo.terra@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1357688681!25599811!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7163 invoked from network); 8 Jan 2013 23:44:42 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 23:44:42 -0000 Received: by mail-lb0-f173.google.com with SMTP id c1so802552lbg.4 for ; Tue, 08 Jan 2013 15:44:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=GLpqnIstZ5Y9MuvJhlr6BiAc2S7/ET6kWsR+/dkIB98=; b=RAslZzL0F5Yx4ZIilrP7gH8mH9/Ku+w+H++T4R2TfNqrsRjEQ37gAaJJX6qNxpStpt T2vMcuIWh/OTDT1wmzOWyYuciZYRk/D81LoQUFCvJHBgjxWENwFjg1Ep/szXcn4x9BGR lILdCuqV/WdcLmTjNq0FW0Yjlm82efMj7XHJ6hUtG2wL5IM6yo2GULjPy9ggeQ/7FcJz YM8EIhmO2KK6ItmJo5EkDSfCCsRJ1R1wThMQZ6K5XW7ImQt0DtTOa2f6DVtm1KnAzjwQ Xa3Kpd4lE67TXILvlImlJBRj2a9yDW4wRMRyr+dW19Xv8YB9Dqp4ZB1Uhprq8uGqPiqb dIow== Received: by 10.152.47.75 with SMTP id b11mr62254406lan.14.1357688681185; Tue, 08 Jan 2013 15:44:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.57.3 with HTTP; Tue, 8 Jan 2013 15:44:21 -0800 (PST) From: Carlos Eduardo Tavares Terra Date: Tue, 8 Jan 2013 21:44:21 -0200 Message-ID: To: "xen-api@lists.xensource.com" Subject: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4995640525462309325==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4995640525462309325== Content-Type: multipart/alternative; boundary=bcaec55404a28ec06604d2cf875a --bcaec55404a28ec06604d2cf875a Content-Type: text/plain; charset=ISO-8859-1 I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. Is it possible? Do I have to check anything? I have done some fixes to work with XenCenter. Thanks -- Carlos Eduardo Tavares Terra Red Hat Certified Engineer Consultor em Infraestrutura de TI GNU/Linux #413291 [http://counter.li.org] --bcaec55404a28ec06604d2cf875a Content-Type: text/html; charset=ISO-8859-1
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org]
--bcaec55404a28ec06604d2cf875a-- --===============4995640525462309325== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4995640525462309325==-- From xen-api-bounces@lists.xen.org Wed Jan 09 00:12:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 00:12:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsjH2-00055G-Ob; Wed, 09 Jan 2013 00:12:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsjH1-00055B-9h for xen-api@lists.xen.org; Wed, 09 Jan 2013 00:12:03 +0000 Received: from [193.109.254.147:5608] by server-13.bemta-14.messagelabs.com id 12/CD-01725-2D5BCE05; Wed, 09 Jan 2013 00:12:02 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357690320!8698975!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=1.9 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30961 invoked from network); 9 Jan 2013 00:12:01 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-13.tower-27.messagelabs.com with SMTP; 9 Jan 2013 00:12:01 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Tue, 8 Jan 2013 18:11:58 -0600 Message-ID: <50ECB60C.40201@xenhive.com> Date: Tue, 08 Jan 2013 18:13:00 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-Auth: admin@xenhive.com Subject: Re: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4303406876680716078==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============4303406876680716078== Content-Type: multipart/alternative; boundary="------------060502000304090202040400" This is a multi-part message in MIME format. --------------060502000304090202040400 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We recently upgraded a XCP pool from version 1.0 to 1.1 to 1.6. We started by booting the pool master with the ISO, upgrading the pool master, and then repeating for each slave. In our case, we did every node in the pool to get the entire pool from 1.0 to 1.1. Then we did the entire pool again (starting with the master) to go from 1.1 to 1.6. Everything went smooth during the upgrades. Upgrade to the latest version of XenCenter before you do the XCP upgrades. In our case, we did not have hacked version numbers in the XCP nodes. If that the fixes you are referring to, you may need to switch those version numbers back before doing the upgrade. On 1/8/2013 5:44 PM, Carlos Eduardo Tavares Terra wrote: > I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. > Is it possible? Do I have to check anything? > I have done some fixes to work with XenCenter. > > Thanks > > -- > Carlos Eduardo Tavares Terra > Red Hat Certified Engineer > Consultor em Infraestrutura de TI > GNU/Linux #413291 [http://counter.li.org] > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------060502000304090202040400 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
We recently upgraded a XCP pool from version 1.0 to 1.1 to 1.6.    We started by booting the pool master with the ISO, upgrading the pool master, and then repeating for each slave.  In our case, we did every node in the pool to get the entire pool from 1.0 to 1.1.  Then we did the entire pool again (starting with the master) to go from 1.1 to 1.6.  Everything went smooth during the upgrades.  Upgrade to the latest version of XenCenter before you do the XCP upgrades.

In our case, we did not have hacked version numbers in the XCP nodes.  If that the fixes you are referring to, you may need to switch those version numbers back before doing the upgrade. 

On 1/8/2013 5:44 PM, Carlos Eduardo Tavares Terra wrote:
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org] 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------060502000304090202040400-- --===============4303406876680716078== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4303406876680716078==-- From xen-api-bounces@lists.xen.org Wed Jan 09 00:12:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 00:12:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsjH2-00055G-Ob; Wed, 09 Jan 2013 00:12:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsjH1-00055B-9h for xen-api@lists.xen.org; Wed, 09 Jan 2013 00:12:03 +0000 Received: from [193.109.254.147:5608] by server-13.bemta-14.messagelabs.com id 12/CD-01725-2D5BCE05; Wed, 09 Jan 2013 00:12:02 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357690320!8698975!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=1.9 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30961 invoked from network); 9 Jan 2013 00:12:01 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-13.tower-27.messagelabs.com with SMTP; 9 Jan 2013 00:12:01 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Tue, 8 Jan 2013 18:11:58 -0600 Message-ID: <50ECB60C.40201@xenhive.com> Date: Tue, 08 Jan 2013 18:13:00 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-Auth: admin@xenhive.com Subject: Re: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4303406876680716078==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============4303406876680716078== Content-Type: multipart/alternative; boundary="------------060502000304090202040400" This is a multi-part message in MIME format. --------------060502000304090202040400 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We recently upgraded a XCP pool from version 1.0 to 1.1 to 1.6. We started by booting the pool master with the ISO, upgrading the pool master, and then repeating for each slave. In our case, we did every node in the pool to get the entire pool from 1.0 to 1.1. Then we did the entire pool again (starting with the master) to go from 1.1 to 1.6. Everything went smooth during the upgrades. Upgrade to the latest version of XenCenter before you do the XCP upgrades. In our case, we did not have hacked version numbers in the XCP nodes. If that the fixes you are referring to, you may need to switch those version numbers back before doing the upgrade. On 1/8/2013 5:44 PM, Carlos Eduardo Tavares Terra wrote: > I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. > Is it possible? Do I have to check anything? > I have done some fixes to work with XenCenter. > > Thanks > > -- > Carlos Eduardo Tavares Terra > Red Hat Certified Engineer > Consultor em Infraestrutura de TI > GNU/Linux #413291 [http://counter.li.org] > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------060502000304090202040400 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
We recently upgraded a XCP pool from version 1.0 to 1.1 to 1.6.    We started by booting the pool master with the ISO, upgrading the pool master, and then repeating for each slave.  In our case, we did every node in the pool to get the entire pool from 1.0 to 1.1.  Then we did the entire pool again (starting with the master) to go from 1.1 to 1.6.  Everything went smooth during the upgrades.  Upgrade to the latest version of XenCenter before you do the XCP upgrades.

In our case, we did not have hacked version numbers in the XCP nodes.  If that the fixes you are referring to, you may need to switch those version numbers back before doing the upgrade. 

On 1/8/2013 5:44 PM, Carlos Eduardo Tavares Terra wrote:
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org] 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------060502000304090202040400-- --===============4303406876680716078== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4303406876680716078==-- From xen-api-bounces@lists.xen.org Wed Jan 09 07:33:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 07:33:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsqAO-0005ck-0T; Wed, 09 Jan 2013 07:33:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsqAM-0005cf-8e for xen-api@lists.xen.org; Wed, 09 Jan 2013 07:33:38 +0000 Received: from [85.158.143.99:53623] by server-2.bemta-4.messagelabs.com id 11/05-24322-15D1DE05; Wed, 09 Jan 2013 07:33:37 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1357716816!22814803!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21751 invoked from network); 9 Jan 2013 07:33:36 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 07:33:36 -0000 Received: by mail-la0-f44.google.com with SMTP id fr10so1550123lab.3 for ; Tue, 08 Jan 2013 23:33:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=l2SX/rqyo9odxIJb/HUGJxr9t8sMUqe3vFkAIVoEMLg=; b=odtXBystLW/AVz1Qbdeabb3dXqKLKxiOkvJE6z2JGeU/+W9IOA5PfnS9Lx++7G23MQ LTz0L9Yk/ams7X77sMyKkiGoubva7IX4Ba4aVCWBVE+XbSxQYkrdnHuNHpL+3u5Q3cUD n2rbxKVisJZe2ZvLBFQXrttvqXaZfYDe3o0iyxAS0sxLkRQ7RI3KSfa1QuN1ZYHE+UeH nlPusPKxBXH5h++W84Cqp4EzEQ0iO+9a6YnUfi9Y0+Z/Ke96tT+1ufm0Fw6h0ucpEF8T ZaDqrKbQWvyQI5v8drAu2bceMDVI78WG7iwwUM4/Ox4oVEUK33nOLws4u/xTMpllqK4U DCAA== X-Received: by 10.112.37.200 with SMTP id a8mr27951642lbk.92.1357716816186; Tue, 08 Jan 2013 23:33:36 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:5534:8d93:3c31:4373? ([2a00:ab00:0:fffe:5534:8d93:3c31:4373]) by mx.google.com with ESMTPS id n7sm23476631lbg.3.2013.01.08.23.33.35 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 23:33:35 -0800 (PST) Message-ID: <50ED1D4E.6020901@gmail.com> Date: Wed, 09 Jan 2013 11:33:34 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0305346357323928726==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0305346357323928726== Content-Type: multipart/alternative; boundary="------------060700090308090801060406" This is a multi-part message in MIME format. --------------060700090308090801060406 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In my lab with copy of huge piece of product VMs (without internet access) upgrade was completed successfully. The single issuse I saw was vm-migration with attached xs-tools.iso (they can't migrate). 09.01.2013 03:44, Carlos Eduardo Tavares Terra ?????: > I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. > Is it possible? Do I have to check anything? > I have done some fixes to work with XenCenter. > > Thanks > > -- > Carlos Eduardo Tavares Terra > Red Hat Certified Engineer > Consultor em Infraestrutura de TI > GNU/Linux #413291 [http://counter.li.org] > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------060700090308090801060406 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
In my lab with copy of huge piece of product VMs (without internet access) upgrade was completed successfully. The single issuse I saw was vm-migration with attached xs-tools.iso (they can't migrate).

09.01.2013 03:44, Carlos Eduardo Tavares Terra пишет:
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org] 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------060700090308090801060406-- --===============0305346357323928726== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0305346357323928726==-- From xen-api-bounces@lists.xen.org Wed Jan 09 07:33:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 07:33:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsqAO-0005ck-0T; Wed, 09 Jan 2013 07:33:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsqAM-0005cf-8e for xen-api@lists.xen.org; Wed, 09 Jan 2013 07:33:38 +0000 Received: from [85.158.143.99:53623] by server-2.bemta-4.messagelabs.com id 11/05-24322-15D1DE05; Wed, 09 Jan 2013 07:33:37 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1357716816!22814803!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21751 invoked from network); 9 Jan 2013 07:33:36 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 07:33:36 -0000 Received: by mail-la0-f44.google.com with SMTP id fr10so1550123lab.3 for ; Tue, 08 Jan 2013 23:33:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=l2SX/rqyo9odxIJb/HUGJxr9t8sMUqe3vFkAIVoEMLg=; b=odtXBystLW/AVz1Qbdeabb3dXqKLKxiOkvJE6z2JGeU/+W9IOA5PfnS9Lx++7G23MQ LTz0L9Yk/ams7X77sMyKkiGoubva7IX4Ba4aVCWBVE+XbSxQYkrdnHuNHpL+3u5Q3cUD n2rbxKVisJZe2ZvLBFQXrttvqXaZfYDe3o0iyxAS0sxLkRQ7RI3KSfa1QuN1ZYHE+UeH nlPusPKxBXH5h++W84Cqp4EzEQ0iO+9a6YnUfi9Y0+Z/Ke96tT+1ufm0Fw6h0ucpEF8T ZaDqrKbQWvyQI5v8drAu2bceMDVI78WG7iwwUM4/Ox4oVEUK33nOLws4u/xTMpllqK4U DCAA== X-Received: by 10.112.37.200 with SMTP id a8mr27951642lbk.92.1357716816186; Tue, 08 Jan 2013 23:33:36 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:5534:8d93:3c31:4373? ([2a00:ab00:0:fffe:5534:8d93:3c31:4373]) by mx.google.com with ESMTPS id n7sm23476631lbg.3.2013.01.08.23.33.35 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 23:33:35 -0800 (PST) Message-ID: <50ED1D4E.6020901@gmail.com> Date: Wed, 09 Jan 2013 11:33:34 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0305346357323928726==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0305346357323928726== Content-Type: multipart/alternative; boundary="------------060700090308090801060406" This is a multi-part message in MIME format. --------------060700090308090801060406 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In my lab with copy of huge piece of product VMs (without internet access) upgrade was completed successfully. The single issuse I saw was vm-migration with attached xs-tools.iso (they can't migrate). 09.01.2013 03:44, Carlos Eduardo Tavares Terra ?????: > I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. > Is it possible? Do I have to check anything? > I have done some fixes to work with XenCenter. > > Thanks > > -- > Carlos Eduardo Tavares Terra > Red Hat Certified Engineer > Consultor em Infraestrutura de TI > GNU/Linux #413291 [http://counter.li.org] > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------060700090308090801060406 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
In my lab with copy of huge piece of product VMs (without internet access) upgrade was completed successfully. The single issuse I saw was vm-migration with attached xs-tools.iso (they can't migrate).

09.01.2013 03:44, Carlos Eduardo Tavares Terra пишет:
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org] 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------060700090308090801060406-- --===============0305346357323928726== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0305346357323928726==-- From xen-api-bounces@lists.xen.org Wed Jan 09 11:10:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 11:10:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TstYH-0002s9-0g; Wed, 09 Jan 2013 11:10:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TstYF-0002s4-1m for xen-api@lists.xen.org; Wed, 09 Jan 2013 11:10:31 +0000 Received: from [85.158.139.83:57897] by server-14.bemta-5.messagelabs.com id B4/3B-09538-6205DE05; Wed, 09 Jan 2013 11:10:30 +0000 X-Env-Sender: eduardo.terra@gmail.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357729827!25518103!1 X-Originating-IP: [209.85.220.180] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13524 invoked from network); 9 Jan 2013 11:10:28 -0000 Received: from mail-vc0-f180.google.com (HELO mail-vc0-f180.google.com) (209.85.220.180) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 11:10:28 -0000 Received: by mail-vc0-f180.google.com with SMTP id p16so1383638vcq.39 for ; Wed, 09 Jan 2013 03:10:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=V9fLLBflH20qk297znHXzdgoWtZocgd7u4F23xN02Qw=; b=0GnAnvHiKtXA8MYz1qB5UFRVmPrPPDZ/5eqPAN4Uh6ea1OjLW91N2sJef6fe4b+T0A wUHYZ+GS0XL+2Eq6G+1UIYXqTnP/6Iuj/Hh8gS03R+6RT7cwoXqGlP934PeusPebpjRM w9WTBkL3e0+5lq0qk6GoWFaYl1VLkvOsNCKkTwY1Uj4GC27wNiL8FFl5Fi7A41MFnCSX p8k+5SQjGbVo0L4IKA0nVWhQi3vlzoQ+Sgu/kbNVILyQzl9h2Z45ftEqpBQqjU9BeZ7s wg4VbtKcm5x1/N6dEmqdWGk/oE/+foMdUkVrbx71XfQIb5mEIKP8EBCScc9Jg3d2OQ3z pU5w== Received: by 10.52.16.75 with SMTP id e11mr77638394vdd.45.1357729826743; Wed, 09 Jan 2013 03:10:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.147.70 with HTTP; Wed, 9 Jan 2013 03:10:06 -0800 (PST) In-Reply-To: <50ECB60C.40201@xenhive.com> References: <50ECB60C.40201@xenhive.com> From: Carlos Eduardo Tavares Terra Date: Wed, 9 Jan 2013 09:10:06 -0200 Message-ID: To: "admin@xenhive.com" Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7993777604302683416==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7993777604302683416== Content-Type: multipart/alternative; boundary=bcaec5040dfe06248304d2d91c29 --bcaec5040dfe06248304d2d91c29 Content-Type: text/plain; charset=ISO-8859-1 Thanks for the info. The fixes were exactly that. I will undo that changes before upgrade. On Tue, Jan 8, 2013 at 10:13 PM, admin@xenhive.com wrote: > We recently upgraded a XCP pool from version 1.0 to 1.1 to 1.6. We > started by booting the pool master with the ISO, upgrading the pool master, > and then repeating for each slave. In our case, we did every node in the > pool to get the entire pool from 1.0 to 1.1. Then we did the entire pool > again (starting with the master) to go from 1.1 to 1.6. Everything went > smooth during the upgrades. Upgrade to the latest version of XenCenter > before you do the XCP upgrades. > > In our case, we did not have hacked version numbers in the XCP nodes. If > that the fixes you are referring to, you may need to switch those version > numbers back before doing the upgrade. > > On 1/8/2013 5:44 PM, Carlos Eduardo Tavares Terra wrote: > > I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. > Is it possible? Do I have to check anything? > I have done some fixes to work with XenCenter. > > Thanks > > -- > Carlos Eduardo Tavares Terra > Red Hat Certified Engineer > Consultor em Infraestrutura de TI > GNU/Linux #413291 [http://counter.li.org] > > > _______________________________________________ > Xen-api mailing listXen-api@lists.xen.orghttp://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > -- Carlos Eduardo Tavares Terra Red Hat Certified Engineer Consultor em Infraestrutura de TI GNU/Linux #413291 [http://counter.li.org] --bcaec5040dfe06248304d2d91c29 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks for the info.
The fixes were exactly = that. I will undo that changes before upgrade.


On Tue, Jan 8, 2013 at 10:13 PM,= admin@xenhive.com <admin@xenhive= .com> wrote:
=20 =20 =20
We recently upgraded a XCP pool from version 1.0 to 1.1 to 1.6.=A0=A0=A0 We started by booting the pool master with the ISO, upgrading the pool master, and then repeating for each slave.=A0 In our case, we did every node in the pool to get the entire pool from 1.0 to 1.1.=A0 Then we did the entire pool again (starting with the master) to go from 1.1 to 1.6.=A0 Everything went smooth during the upgrades.=A0 Upgrade to the latest version of XenCenter before you do the XCP upgrades.

In our case, we did not have hacked version numbers in the XCP nodes.=A0 If that the fixes you are referring to, you may need to switch those version numbers back before doing the upgrade.=A0

On 1/8/2013 5:44 PM, Carlos Eduardo Tavares Terra wrote:
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org] 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xe=
n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




--
Carlos Eduardo Tava= res Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de T= I
GNU/Linux #413291 [http://counter.li.org]
--bcaec5040dfe06248304d2d91c29-- --===============7993777604302683416== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7993777604302683416==-- From xen-api-bounces@lists.xen.org Wed Jan 09 11:10:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 11:10:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TstYH-0002s9-0g; Wed, 09 Jan 2013 11:10:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TstYF-0002s4-1m for xen-api@lists.xen.org; Wed, 09 Jan 2013 11:10:31 +0000 Received: from [85.158.139.83:57897] by server-14.bemta-5.messagelabs.com id B4/3B-09538-6205DE05; Wed, 09 Jan 2013 11:10:30 +0000 X-Env-Sender: eduardo.terra@gmail.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357729827!25518103!1 X-Originating-IP: [209.85.220.180] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13524 invoked from network); 9 Jan 2013 11:10:28 -0000 Received: from mail-vc0-f180.google.com (HELO mail-vc0-f180.google.com) (209.85.220.180) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 11:10:28 -0000 Received: by mail-vc0-f180.google.com with SMTP id p16so1383638vcq.39 for ; Wed, 09 Jan 2013 03:10:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=V9fLLBflH20qk297znHXzdgoWtZocgd7u4F23xN02Qw=; b=0GnAnvHiKtXA8MYz1qB5UFRVmPrPPDZ/5eqPAN4Uh6ea1OjLW91N2sJef6fe4b+T0A wUHYZ+GS0XL+2Eq6G+1UIYXqTnP/6Iuj/Hh8gS03R+6RT7cwoXqGlP934PeusPebpjRM w9WTBkL3e0+5lq0qk6GoWFaYl1VLkvOsNCKkTwY1Uj4GC27wNiL8FFl5Fi7A41MFnCSX p8k+5SQjGbVo0L4IKA0nVWhQi3vlzoQ+Sgu/kbNVILyQzl9h2Z45ftEqpBQqjU9BeZ7s wg4VbtKcm5x1/N6dEmqdWGk/oE/+foMdUkVrbx71XfQIb5mEIKP8EBCScc9Jg3d2OQ3z pU5w== Received: by 10.52.16.75 with SMTP id e11mr77638394vdd.45.1357729826743; Wed, 09 Jan 2013 03:10:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.147.70 with HTTP; Wed, 9 Jan 2013 03:10:06 -0800 (PST) In-Reply-To: <50ECB60C.40201@xenhive.com> References: <50ECB60C.40201@xenhive.com> From: Carlos Eduardo Tavares Terra Date: Wed, 9 Jan 2013 09:10:06 -0200 Message-ID: To: "admin@xenhive.com" Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7993777604302683416==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7993777604302683416== Content-Type: multipart/alternative; boundary=bcaec5040dfe06248304d2d91c29 --bcaec5040dfe06248304d2d91c29 Content-Type: text/plain; charset=ISO-8859-1 Thanks for the info. The fixes were exactly that. I will undo that changes before upgrade. On Tue, Jan 8, 2013 at 10:13 PM, admin@xenhive.com wrote: > We recently upgraded a XCP pool from version 1.0 to 1.1 to 1.6. We > started by booting the pool master with the ISO, upgrading the pool master, > and then repeating for each slave. In our case, we did every node in the > pool to get the entire pool from 1.0 to 1.1. Then we did the entire pool > again (starting with the master) to go from 1.1 to 1.6. Everything went > smooth during the upgrades. Upgrade to the latest version of XenCenter > before you do the XCP upgrades. > > In our case, we did not have hacked version numbers in the XCP nodes. If > that the fixes you are referring to, you may need to switch those version > numbers back before doing the upgrade. > > On 1/8/2013 5:44 PM, Carlos Eduardo Tavares Terra wrote: > > I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. > Is it possible? Do I have to check anything? > I have done some fixes to work with XenCenter. > > Thanks > > -- > Carlos Eduardo Tavares Terra > Red Hat Certified Engineer > Consultor em Infraestrutura de TI > GNU/Linux #413291 [http://counter.li.org] > > > _______________________________________________ > Xen-api mailing listXen-api@lists.xen.orghttp://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > -- Carlos Eduardo Tavares Terra Red Hat Certified Engineer Consultor em Infraestrutura de TI GNU/Linux #413291 [http://counter.li.org] --bcaec5040dfe06248304d2d91c29 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks for the info.
The fixes were exactly = that. I will undo that changes before upgrade.


On Tue, Jan 8, 2013 at 10:13 PM,= admin@xenhive.com <admin@xenhive= .com> wrote:
=20 =20 =20
We recently upgraded a XCP pool from version 1.0 to 1.1 to 1.6.=A0=A0=A0 We started by booting the pool master with the ISO, upgrading the pool master, and then repeating for each slave.=A0 In our case, we did every node in the pool to get the entire pool from 1.0 to 1.1.=A0 Then we did the entire pool again (starting with the master) to go from 1.1 to 1.6.=A0 Everything went smooth during the upgrades.=A0 Upgrade to the latest version of XenCenter before you do the XCP upgrades.

In our case, we did not have hacked version numbers in the XCP nodes.=A0 If that the fixes you are referring to, you may need to switch those version numbers back before doing the upgrade.=A0

On 1/8/2013 5:44 PM, Carlos Eduardo Tavares Terra wrote:
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org] 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xe=
n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




--
Carlos Eduardo Tava= res Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de T= I
GNU/Linux #413291 [http://counter.li.org]
--bcaec5040dfe06248304d2d91c29-- --===============7993777604302683416== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7993777604302683416==-- From xen-api-bounces@lists.xen.org Wed Jan 09 13:03:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 13:03:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsvJC-0006Zf-NL; Wed, 09 Jan 2013 13:03:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsvJB-0006ZY-22 for xen-api@lists.xen.org; Wed, 09 Jan 2013 13:03:05 +0000 Received: from [193.109.254.147:29028] by server-5.bemta-14.messagelabs.com id 97/3F-32031-88A6DE05; Wed, 09 Jan 2013 13:03:04 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1357736530!3648832!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 303 invoked from network); 9 Jan 2013 13:02:10 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 13:02:10 -0000 Received: by mail-la0-f44.google.com with SMTP id fr10so1818864lab.3 for ; Wed, 09 Jan 2013 05:02:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=a48FiFArtgjBo3gthTaoSCOXW4jRtfhrVf1B/rJHdO0=; b=S+HjJ50A4jLWIGhRxuqOY3ClwkvpmYRTqPpUUkO12eCrw8MeiofQKHC5XMEWcO6Txy jm3iegAuVztmVy6ZGWDDKqiRQtHnMQXoveLStyvqWQfPOm5TaxNKCEpQWBFo+TeBb+sB 1oL3mh5njSEj+li52OuFfmilBYel5Pm7yYcwiWK7d3bXMYm5BRZE60IF2kxc5btQYjlu zLWLEmec30wkjTemHVkoFx4uwYy54l75fsSt06YWN3dJ+YsC8JnAJJuuaIUEtrvb3B3Y MEVKv3EKBb3SUcsmllUwu3R9EADZZkPo58TksMP61lxPYpUTFgLWRPn6EDdbWMj3ltfd xmxg== X-Received: by 10.112.42.197 with SMTP id q5mr27906187lbl.9.1357736530075; Wed, 09 Jan 2013 05:02:10 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:5534:8d93:3c31:4373? ([2a00:ab00:0:fffe:5534:8d93:3c31:4373]) by mx.google.com with ESMTPS id fb1sm23931667lbb.15.2013.01.09.05.02.09 (version=SSLv3 cipher=OTHER); Wed, 09 Jan 2013 05:02:09 -0800 (PST) Message-ID: <50ED6A50.9020005@gmail.com> Date: Wed, 09 Jan 2013 17:02:08 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , Lars Kurth Subject: [Xen-API] XCP 1.6, and git branch tree X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Good day. I still do not understand current situation with XCP updates and git tree. I understand there is a lots of stuff happens between code and rpm, and it consume lot of time of many guys. But few questions about current XCP code and fixes... 1) which branch contains current state of xapi for XCP 1.6? remotes/origin/tampa-lcm from github? 2) Is tampa-lcm branch HEAD the current stable for XenServer? 3) Can it safely be compiled and installed to product environment? I especially concern about 3rd, because I don't want to suddenly get batch of XenServers instead current product XCP pool. I don't ask about 'when you gonna compile them to RPMs for me', but there is a mist around git branches, XCP and XenServer relationship. We finally got human resources to dig inside xapi (and plans to publish our improvements/features), but we need to know, what exactly to patch. Thanks. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 13:03:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 13:03:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsvJC-0006Zf-NL; Wed, 09 Jan 2013 13:03:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsvJB-0006ZY-22 for xen-api@lists.xen.org; Wed, 09 Jan 2013 13:03:05 +0000 Received: from [193.109.254.147:29028] by server-5.bemta-14.messagelabs.com id 97/3F-32031-88A6DE05; Wed, 09 Jan 2013 13:03:04 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1357736530!3648832!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 303 invoked from network); 9 Jan 2013 13:02:10 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 13:02:10 -0000 Received: by mail-la0-f44.google.com with SMTP id fr10so1818864lab.3 for ; Wed, 09 Jan 2013 05:02:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=a48FiFArtgjBo3gthTaoSCOXW4jRtfhrVf1B/rJHdO0=; b=S+HjJ50A4jLWIGhRxuqOY3ClwkvpmYRTqPpUUkO12eCrw8MeiofQKHC5XMEWcO6Txy jm3iegAuVztmVy6ZGWDDKqiRQtHnMQXoveLStyvqWQfPOm5TaxNKCEpQWBFo+TeBb+sB 1oL3mh5njSEj+li52OuFfmilBYel5Pm7yYcwiWK7d3bXMYm5BRZE60IF2kxc5btQYjlu zLWLEmec30wkjTemHVkoFx4uwYy54l75fsSt06YWN3dJ+YsC8JnAJJuuaIUEtrvb3B3Y MEVKv3EKBb3SUcsmllUwu3R9EADZZkPo58TksMP61lxPYpUTFgLWRPn6EDdbWMj3ltfd xmxg== X-Received: by 10.112.42.197 with SMTP id q5mr27906187lbl.9.1357736530075; Wed, 09 Jan 2013 05:02:10 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:5534:8d93:3c31:4373? ([2a00:ab00:0:fffe:5534:8d93:3c31:4373]) by mx.google.com with ESMTPS id fb1sm23931667lbb.15.2013.01.09.05.02.09 (version=SSLv3 cipher=OTHER); Wed, 09 Jan 2013 05:02:09 -0800 (PST) Message-ID: <50ED6A50.9020005@gmail.com> Date: Wed, 09 Jan 2013 17:02:08 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , Lars Kurth Subject: [Xen-API] XCP 1.6, and git branch tree X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Good day. I still do not understand current situation with XCP updates and git tree. I understand there is a lots of stuff happens between code and rpm, and it consume lot of time of many guys. But few questions about current XCP code and fixes... 1) which branch contains current state of xapi for XCP 1.6? remotes/origin/tampa-lcm from github? 2) Is tampa-lcm branch HEAD the current stable for XenServer? 3) Can it safely be compiled and installed to product environment? I especially concern about 3rd, because I don't want to suddenly get batch of XenServers instead current product XCP pool. I don't ask about 'when you gonna compile them to RPMs for me', but there is a mist around git branches, XCP and XenServer relationship. We finally got human resources to dig inside xapi (and plans to publish our improvements/features), but we need to know, what exactly to patch. Thanks. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 13:24:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 13:24:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsvcN-0007Hb-Vs; Wed, 09 Jan 2013 13:22:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsvcM-0007HU-ID for xen-api@lists.xen.org; Wed, 09 Jan 2013 13:22:54 +0000 Received: from [193.109.254.147:58273] by server-13.bemta-14.messagelabs.com id 47/2F-01725-D2F6DE05; Wed, 09 Jan 2013 13:22:53 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357737759!8768017!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28851 invoked from network); 9 Jan 2013 13:22:40 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-13.tower-27.messagelabs.com with SMTP; 9 Jan 2013 13:22:40 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Wed, 9 Jan 2013 07:22:37 -0600 Message-ID: <50ED6F22.6070608@xenhive.com> Date: Wed, 09 Jan 2013 07:22:42 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50ED1D4E.6020901@gmail.com> In-Reply-To: <50ED1D4E.6020901@gmail.com> X-Auth: admin@xenhive.com Subject: Re: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2267946421696948913==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2267946421696948913== Content-Type: multipart/alternative; boundary="------------010802010501030206010204" This is a multi-part message in MIME format. --------------010802010501030206010204 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We have seen that issue, too. Before doing anything, it is a good idea to make sure the DVD is set to Empty for each VM. On 1/9/2013 1:33 AM, George Shuklin wrote: > In my lab with copy of huge piece of product VMs (without internet > access) upgrade was completed successfully. The single issuse I saw > was vm-migration with attached xs-tools.iso (they can't migrate). > > 09.01.2013 03:44, Carlos Eduardo Tavares Terra ?????: >> I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. >> Is it possible? Do I have to check anything? >> I have done some fixes to work with XenCenter. >> >> Thanks >> >> -- >> Carlos Eduardo Tavares Terra >> Red Hat Certified Engineer >> Consultor em Infraestrutura de TI >> GNU/Linux #413291 [http://counter.li.org] >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------010802010501030206010204 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
We have seen that issue, too.  Before doing anything, it is a good idea to make sure the DVD is set to Empty for each VM.

On 1/9/2013 1:33 AM, George Shuklin wrote:
In my lab with copy of huge piece of product VMs (without internet access) upgrade was completed successfully. The single issuse I saw was vm-migration with attached xs-tools.iso (they can't migrate).

09.01.2013 03:44, Carlos Eduardo Tavares Terra пишет:
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org] 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------010802010501030206010204-- --===============2267946421696948913== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2267946421696948913==-- From xen-api-bounces@lists.xen.org Wed Jan 09 13:24:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 13:24:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsvcN-0007Hb-Vs; Wed, 09 Jan 2013 13:22:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsvcM-0007HU-ID for xen-api@lists.xen.org; Wed, 09 Jan 2013 13:22:54 +0000 Received: from [193.109.254.147:58273] by server-13.bemta-14.messagelabs.com id 47/2F-01725-D2F6DE05; Wed, 09 Jan 2013 13:22:53 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357737759!8768017!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28851 invoked from network); 9 Jan 2013 13:22:40 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-13.tower-27.messagelabs.com with SMTP; 9 Jan 2013 13:22:40 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Wed, 9 Jan 2013 07:22:37 -0600 Message-ID: <50ED6F22.6070608@xenhive.com> Date: Wed, 09 Jan 2013 07:22:42 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50ED1D4E.6020901@gmail.com> In-Reply-To: <50ED1D4E.6020901@gmail.com> X-Auth: admin@xenhive.com Subject: Re: [Xen-API] Is it possible to upgrade from XCP 1.1 to 1.6 easily? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2267946421696948913==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2267946421696948913== Content-Type: multipart/alternative; boundary="------------010802010501030206010204" This is a multi-part message in MIME format. --------------010802010501030206010204 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We have seen that issue, too. Before doing anything, it is a good idea to make sure the DVD is set to Empty for each VM. On 1/9/2013 1:33 AM, George Shuklin wrote: > In my lab with copy of huge piece of product VMs (without internet > access) upgrade was completed successfully. The single issuse I saw > was vm-migration with attached xs-tools.iso (they can't migrate). > > 09.01.2013 03:44, Carlos Eduardo Tavares Terra ?????: >> I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6. >> Is it possible? Do I have to check anything? >> I have done some fixes to work with XenCenter. >> >> Thanks >> >> -- >> Carlos Eduardo Tavares Terra >> Red Hat Certified Engineer >> Consultor em Infraestrutura de TI >> GNU/Linux #413291 [http://counter.li.org] >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------010802010501030206010204 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
We have seen that issue, too.  Before doing anything, it is a good idea to make sure the DVD is set to Empty for each VM.

On 1/9/2013 1:33 AM, George Shuklin wrote:
In my lab with copy of huge piece of product VMs (without internet access) upgrade was completed successfully. The single issuse I saw was vm-migration with attached xs-tools.iso (they can't migrate).

09.01.2013 03:44, Carlos Eduardo Tavares Terra пишет:
I have a pool with 5 XCP 1.1 servers and wish to upgrade to 1.6.
Is it possible? Do I have to check anything?
I have done some fixes to work with XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org] 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api




_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------010802010501030206010204-- --===============2267946421696948913== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2267946421696948913==-- From xen-api-bounces@lists.xen.org Wed Jan 09 15:40:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 15:40:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxlq-0003HA-T2; Wed, 09 Jan 2013 15:40:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsfGT-0000gY-Lf; Tue, 08 Jan 2013 19:55:13 +0000 Received: from [85.158.137.99:26037] by server-6.bemta-3.messagelabs.com id 7A/54-12154-0A97CE05; Tue, 08 Jan 2013 19:55:12 +0000 X-Env-Sender: ketuzsezr@gmail.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1357674909!17267231!1 X-Originating-IP: [209.85.220.169] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17529 invoked from network); 8 Jan 2013 19:55:10 -0000 Received: from unknown (HELO mail-vc0-f169.google.com) (209.85.220.169) by server-6.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 19:55:10 -0000 Received: by mail-vc0-f169.google.com with SMTP id gb23so824175vcb.28 for ; Tue, 08 Jan 2013 11:54:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=xFGin1sAPWYA1gomgUXVOzdRflgHp2svGnr1VHH3sTg=; b=Q24l/H7EsTgo5FJK076bvP05pVWii27VQWAuUmuhpkbToYgTBO92KeVoOPA10OZYiz KiY5Tsw7+nZFkiWTFziH1MgJQi585vFAYNetYl8p3aVlowMg1+jIHgqw4v5MpDtP5bVt IWheLEqu1UNOvDPvfuFfeJguhdwjfLFBcI4c0skmjZgTMe0Bq+B8CnCJlkK1iCpvyPty xaeVF5bcv15VUN0pSzrV076q7fiM97aB5GVPYcEimxlCnQu7m/z7tnkXpXfPiw3meRj3 tlfCVorQzomyhhwaICGoNPvH6Ta52kh0LO24YyZNBvWKP34M+tlWXL+nGy0/urRYTm0F vgyw== X-Received: by 10.220.153.80 with SMTP id j16mr86225739vcw.21.1357674848554; Tue, 08 Jan 2013 11:54:08 -0800 (PST) Received: from phenom.dumpdata.com (50-195-21-189-static.hfc.comcastbusiness.net. [50.195.21.189]) by mx.google.com with ESMTPS id bm2sm54369339vdc.6.2013.01.08.11.54.07 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Jan 2013 11:54:08 -0800 (PST) Date: Tue, 8 Jan 2013 14:54:06 -0500 From: Konrad Rzeszutek Wilk To: Wei Liu Message-ID: <20130108195405.GD15194@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1357576754.13581.15.camel@iceland> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Wed, 09 Jan 2013 15:40:49 +0000 Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mon, Jan 07, 2013 at 04:39:14PM +0000, Wei Liu wrote: > On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: > > On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > > > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > > > > > c) Ideally I would like to add biography and interest section for > > > > > all our mentors. I can create a wiki template for mentors if it > > > > > helps > > > > Ideas for GSOC: > > > > - Support microcode update bundled in with the initrd in Xen. > > Here is the Linux side of it comes out looking: > > http://markmail.org/thread/ewrs7fa66knfwzbo > > > > - Write Xen PV Architecture Book/Manual/whatever. We have been > > slowly going through the PV architecture and documenting it. > > It would nice to have somebody full-time doing it and asking > > questions. And then the answers would be written in this book. > > > > IIRC the documentation-only project will not be accepted. Good to know. Thx. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 15:40:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 15:40:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxlq-0003HA-T2; Wed, 09 Jan 2013 15:40:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsfGT-0000gY-Lf; Tue, 08 Jan 2013 19:55:13 +0000 Received: from [85.158.137.99:26037] by server-6.bemta-3.messagelabs.com id 7A/54-12154-0A97CE05; Tue, 08 Jan 2013 19:55:12 +0000 X-Env-Sender: ketuzsezr@gmail.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1357674909!17267231!1 X-Originating-IP: [209.85.220.169] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17529 invoked from network); 8 Jan 2013 19:55:10 -0000 Received: from unknown (HELO mail-vc0-f169.google.com) (209.85.220.169) by server-6.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2013 19:55:10 -0000 Received: by mail-vc0-f169.google.com with SMTP id gb23so824175vcb.28 for ; Tue, 08 Jan 2013 11:54:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=xFGin1sAPWYA1gomgUXVOzdRflgHp2svGnr1VHH3sTg=; b=Q24l/H7EsTgo5FJK076bvP05pVWii27VQWAuUmuhpkbToYgTBO92KeVoOPA10OZYiz KiY5Tsw7+nZFkiWTFziH1MgJQi585vFAYNetYl8p3aVlowMg1+jIHgqw4v5MpDtP5bVt IWheLEqu1UNOvDPvfuFfeJguhdwjfLFBcI4c0skmjZgTMe0Bq+B8CnCJlkK1iCpvyPty xaeVF5bcv15VUN0pSzrV076q7fiM97aB5GVPYcEimxlCnQu7m/z7tnkXpXfPiw3meRj3 tlfCVorQzomyhhwaICGoNPvH6Ta52kh0LO24YyZNBvWKP34M+tlWXL+nGy0/urRYTm0F vgyw== X-Received: by 10.220.153.80 with SMTP id j16mr86225739vcw.21.1357674848554; Tue, 08 Jan 2013 11:54:08 -0800 (PST) Received: from phenom.dumpdata.com (50-195-21-189-static.hfc.comcastbusiness.net. [50.195.21.189]) by mx.google.com with ESMTPS id bm2sm54369339vdc.6.2013.01.08.11.54.07 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Jan 2013 11:54:08 -0800 (PST) Date: Tue, 8 Jan 2013 14:54:06 -0500 From: Konrad Rzeszutek Wilk To: Wei Liu Message-ID: <20130108195405.GD15194@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1357576754.13581.15.camel@iceland> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Wed, 09 Jan 2013 15:40:49 +0000 Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mon, Jan 07, 2013 at 04:39:14PM +0000, Wei Liu wrote: > On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: > > On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > > > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > > > > > c) Ideally I would like to add biography and interest section for > > > > > all our mentors. I can create a wiki template for mentors if it > > > > > helps > > > > Ideas for GSOC: > > > > - Support microcode update bundled in with the initrd in Xen. > > Here is the Linux side of it comes out looking: > > http://markmail.org/thread/ewrs7fa66knfwzbo > > > > - Write Xen PV Architecture Book/Manual/whatever. We have been > > slowly going through the PV architecture and documenting it. > > It would nice to have somebody full-time doing it and asking > > questions. And then the answers would be written in this book. > > > > IIRC the documentation-only project will not be accepted. Good to know. Thx. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 15:41:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 15:41:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxlr-0003HH-27; Wed, 09 Jan 2013 15:40:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsxVB-0002Is-1s for xen-api@lists.xen.org; Wed, 09 Jan 2013 15:23:37 +0000 Received: from [85.158.139.83:15179] by server-10.bemta-5.messagelabs.com id 55/F5-13383-87B8DE05; Wed, 09 Jan 2013 15:23:36 +0000 X-Env-Sender: sainrun001@126.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1357745011!28880321!1 X-Originating-IP: [220.181.15.18] X-SpamReason: No, hits=1.6 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjE1LjE4ID0+IDU3MDM=\n,sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjE1LjE4ID0+IDU3MDM=\n, DEAR_SOMETHING, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28793 invoked from network); 9 Jan 2013 15:23:34 -0000 Received: from m15-18.126.com (HELO m15-18.126.com) (220.181.15.18) by server-10.tower-182.messagelabs.com with SMTP; 9 Jan 2013 15:23:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=126.com; s=s110527; h=Received:Date:From:To:Subject:Content-Type: MIME-Version:Message-ID; bh=2n6g+dM3Jt/JXv4k47nET3mSC8D2VQP0ZyM+ FO+TWxM=; b=VPO8a8o+NY1mSKJfAAehwoIJxMlt0/G4zrk6OI0XvYHWFmSqPK3t o3WKsWjwDcO7UeMN/ZPM1CMJ/Tc/ZR5E5QrtmsJ+xxYiN+z1H3n5qcwj8zmx7EjY oELe7TVM7OygYUz4Bvs/z5oBKTAE/Huf3WdP92oEGttnSNrMXs/IOjs= Received: from sainrun001$126.com ( [116.213.171.15] ) by ajax-webmail-wmsvr18 (Coremail) ; Wed, 9 Jan 2013 23:23:26 +0800 (CST) X-Originating-IP: [116.213.171.15] Date: Wed, 9 Jan 2013 23:23:26 +0800 (CST) From: =?GBK?B?zfiwsi2x5b31s8w=?= To: xen-api@lists.xen.org X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20121219(21170.5156.5150) Copyright (c) 2002-2013 www.mailtech.cn 126com X-CM-CTRLDATA: hGjslWZvb3Rlcl9odG09MzA5NDo4MQ== MIME-Version: 1.0 Message-ID: <1c84c978.c1ca.13c1fe8a6bc.Coremail.sainrun001@126.com> X-CM-TRANSID: EsqowGA54EFui+1Qvf8eAA--.14551W X-CM-SenderInfo: hvdl02txqqiia6rslhhfrp/1tbiHACf301r2dv-fAAAs7 X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== X-Mailman-Approved-At: Wed, 09 Jan 2013 15:40:49 +0000 Subject: [Xen-API] Questions for help X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7453401370226521875==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7453401370226521875== Content-Type: multipart/alternative; boundary="----=_Part_184443_116765748.1357745006268" ------=_Part_184443_116765748.1357745006268 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit Dear Sir: I am a student of Computer Speciaty in a university. Now I am studying in principle of Xen Cloud Platform.There are a few of questions boring me and I have to seek help to you. If a guest os is destroyed,is the internal memory that it once occupyed will scratched? Is the internal memory that it once occupyed will recovered? If it will be scratched,would you show me the corresponding codes or testing progama?Expect your reply. Yours Sincerely; Chan 9th,Jan,2013 ------=_Part_184443_116765748.1357745006268 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: 7bit
 Dear  Sir:
       I am a student of Computer Speciaty in a university.  Now I am studying in principle of Xen Cloud Platform.There are a few of questions boring me and I have to seek help to you.
       If a guest os is destroyed,is the internal memory that it once occupyed will scratched? Is the internal memory that it once occupyed will  recovered?
       If it will be scratched,would you show me the corresponding codes or testing progama?Expect your reply.
  
Yours 
Sincerely; 
Chan
                                                                                                                                                                                                                                                                                                                                                                         9th,Jan,2013


------=_Part_184443_116765748.1357745006268-- --===============7453401370226521875== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7453401370226521875==-- From xen-api-bounces@lists.xen.org Wed Jan 09 15:41:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 15:41:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxlr-0003HH-27; Wed, 09 Jan 2013 15:40:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsxVB-0002Is-1s for xen-api@lists.xen.org; Wed, 09 Jan 2013 15:23:37 +0000 Received: from [85.158.139.83:15179] by server-10.bemta-5.messagelabs.com id 55/F5-13383-87B8DE05; Wed, 09 Jan 2013 15:23:36 +0000 X-Env-Sender: sainrun001@126.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1357745011!28880321!1 X-Originating-IP: [220.181.15.18] X-SpamReason: No, hits=1.6 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjE1LjE4ID0+IDU3MDM=\n,sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjE1LjE4ID0+IDU3MDM=\n, DEAR_SOMETHING, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28793 invoked from network); 9 Jan 2013 15:23:34 -0000 Received: from m15-18.126.com (HELO m15-18.126.com) (220.181.15.18) by server-10.tower-182.messagelabs.com with SMTP; 9 Jan 2013 15:23:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=126.com; s=s110527; h=Received:Date:From:To:Subject:Content-Type: MIME-Version:Message-ID; bh=2n6g+dM3Jt/JXv4k47nET3mSC8D2VQP0ZyM+ FO+TWxM=; b=VPO8a8o+NY1mSKJfAAehwoIJxMlt0/G4zrk6OI0XvYHWFmSqPK3t o3WKsWjwDcO7UeMN/ZPM1CMJ/Tc/ZR5E5QrtmsJ+xxYiN+z1H3n5qcwj8zmx7EjY oELe7TVM7OygYUz4Bvs/z5oBKTAE/Huf3WdP92oEGttnSNrMXs/IOjs= Received: from sainrun001$126.com ( [116.213.171.15] ) by ajax-webmail-wmsvr18 (Coremail) ; Wed, 9 Jan 2013 23:23:26 +0800 (CST) X-Originating-IP: [116.213.171.15] Date: Wed, 9 Jan 2013 23:23:26 +0800 (CST) From: =?GBK?B?zfiwsi2x5b31s8w=?= To: xen-api@lists.xen.org X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20121219(21170.5156.5150) Copyright (c) 2002-2013 www.mailtech.cn 126com X-CM-CTRLDATA: hGjslWZvb3Rlcl9odG09MzA5NDo4MQ== MIME-Version: 1.0 Message-ID: <1c84c978.c1ca.13c1fe8a6bc.Coremail.sainrun001@126.com> X-CM-TRANSID: EsqowGA54EFui+1Qvf8eAA--.14551W X-CM-SenderInfo: hvdl02txqqiia6rslhhfrp/1tbiHACf301r2dv-fAAAs7 X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== X-Mailman-Approved-At: Wed, 09 Jan 2013 15:40:49 +0000 Subject: [Xen-API] Questions for help X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7453401370226521875==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7453401370226521875== Content-Type: multipart/alternative; boundary="----=_Part_184443_116765748.1357745006268" ------=_Part_184443_116765748.1357745006268 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit Dear Sir: I am a student of Computer Speciaty in a university. Now I am studying in principle of Xen Cloud Platform.There are a few of questions boring me and I have to seek help to you. If a guest os is destroyed,is the internal memory that it once occupyed will scratched? Is the internal memory that it once occupyed will recovered? If it will be scratched,would you show me the corresponding codes or testing progama?Expect your reply. Yours Sincerely; Chan 9th,Jan,2013 ------=_Part_184443_116765748.1357745006268 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: 7bit
 Dear  Sir:
       I am a student of Computer Speciaty in a university.  Now I am studying in principle of Xen Cloud Platform.There are a few of questions boring me and I have to seek help to you.
       If a guest os is destroyed,is the internal memory that it once occupyed will scratched? Is the internal memory that it once occupyed will  recovered?
       If it will be scratched,would you show me the corresponding codes or testing progama?Expect your reply.
  
Yours 
Sincerely; 
Chan
                                                                                                                                                                                                                                                                                                                                                                         9th,Jan,2013


------=_Part_184443_116765748.1357745006268-- --===============7453401370226521875== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7453401370226521875==-- From xen-api-bounces@lists.xen.org Wed Jan 09 15:44:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 15:44:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxpi-0003cH-B5; Wed, 09 Jan 2013 15:44:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxpg-0003br-HS for xen-api@lists.xen.org; Wed, 09 Jan 2013 15:44:48 +0000 Received: from [85.158.139.211:53248] by server-4.bemta-5.messagelabs.com id 81/1A-14693-F609DE05; Wed, 09 Jan 2013 15:44:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1357746287!19262919!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3609 invoked from network); 9 Jan 2013 15:44:47 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 9 Jan 2013 15:44:47 -0000 Received: (qmail 23840 invoked by uid 634); 9 Jan 2013 15:44:46 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 09 Jan 2013 15:44:43 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1357576754.13581.15.camel@iceland> Date: Wed, 9 Jan 2013 15:44:42 +0000 Message-Id: <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> To: Wei Liu X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 7 Jan 2013, at 16:39, Wei Liu wrote: > On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: >> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: >>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: >>>>> c) Ideally I would like to add biography and interest section for >>>>> all our mentors. I can create a wiki template for mentors if it >>>>> helps >> >> Ideas for GSOC: >> >> - Support microcode update bundled in with the initrd in Xen. >> Here is the Linux side of it comes out looking: >> http://markmail.org/thread/ewrs7fa66knfwzbo >> >> - Write Xen PV Architecture Book/Manual/whatever. We have been >> slowly going through the PV architecture and documenting it. >> It would nice to have somebody full-time doing it and asking >> questions. And then the answers would be written in this book. >> > > IIRC the documentation-only project will not be accepted. So turn it into an executable specification and use that to generate fuzz tests as well as documentation. In particular, doing this for more than just hypercalls, but also for the ring protocols (to find bugs in the backend drivers) would be a useful regression harness. Throw in all the latest additions like multipage rings and various frontend options, and you will certainly shake out a few bugs (I just accidentally found a netback crash that I'm reporting separately). -anil _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 15:44:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 15:44:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxpi-0003cH-B5; Wed, 09 Jan 2013 15:44:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxpg-0003br-HS for xen-api@lists.xen.org; Wed, 09 Jan 2013 15:44:48 +0000 Received: from [85.158.139.211:53248] by server-4.bemta-5.messagelabs.com id 81/1A-14693-F609DE05; Wed, 09 Jan 2013 15:44:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1357746287!19262919!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3609 invoked from network); 9 Jan 2013 15:44:47 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 9 Jan 2013 15:44:47 -0000 Received: (qmail 23840 invoked by uid 634); 9 Jan 2013 15:44:46 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 09 Jan 2013 15:44:43 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1357576754.13581.15.camel@iceland> Date: Wed, 9 Jan 2013 15:44:42 +0000 Message-Id: <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> To: Wei Liu X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 7 Jan 2013, at 16:39, Wei Liu wrote: > On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: >> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: >>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: >>>>> c) Ideally I would like to add biography and interest section for >>>>> all our mentors. I can create a wiki template for mentors if it >>>>> helps >> >> Ideas for GSOC: >> >> - Support microcode update bundled in with the initrd in Xen. >> Here is the Linux side of it comes out looking: >> http://markmail.org/thread/ewrs7fa66knfwzbo >> >> - Write Xen PV Architecture Book/Manual/whatever. We have been >> slowly going through the PV architecture and documenting it. >> It would nice to have somebody full-time doing it and asking >> questions. And then the answers would be written in this book. >> > > IIRC the documentation-only project will not be accepted. So turn it into an executable specification and use that to generate fuzz tests as well as documentation. In particular, doing this for more than just hypercalls, but also for the ring protocols (to find bugs in the backend drivers) would be a useful regression harness. Throw in all the latest additions like multipage rings and various frontend options, and you will certainly shake out a few bugs (I just accidentally found a netback crash that I'm reporting separately). -anil _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 16:13:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 16:13:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyGv-0004qQ-Ul; Wed, 09 Jan 2013 16:12:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyGu-0004q8-3w; Wed, 09 Jan 2013 16:12:56 +0000 Received: from [85.158.138.51:6861] by server-11.bemta-3.messagelabs.com id 57/01-13335-2079DE05; Wed, 09 Jan 2013 16:12:50 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1357747967!29430438!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTQ2MTg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13053 invoked from network); 9 Jan 2013 16:12:49 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 16:12:49 -0000 X-IronPort-AV: E=Sophos;i="4.84,438,1355097600"; d="scan'208";a="3198473" Received: from unknown (HELO FTLPEX01CL03.citrite.net) ([10.13.107.80]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 09 Jan 2013 16:12:37 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Wed, 9 Jan 2013 11:12:36 -0500 Received: from [10.80.3.80] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TsyGa-0005Nx-Nl; Wed, 09 Jan 2013 16:12:36 +0000 Message-ID: <1357747958.9068.10.camel@iceland> From: Wei Liu To: Anil Madhavapeddy Date: Wed, 9 Jan 2013 16:12:38 +0000 In-Reply-To: <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> X-Mailer: Evolution 3.6.0-0ubuntu3 MIME-Version: 1.0 Cc: wei.liu2@citrix.com, Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Wed, 2013-01-09 at 15:44 +0000, Anil Madhavapeddy wrote: > On 7 Jan 2013, at 16:39, Wei Liu wrote: > > > On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: > >> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > >>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > >>>>> c) Ideally I would like to add biography and interest section for > >>>>> all our mentors. I can create a wiki template for mentors if it > >>>>> helps > >> > >> Ideas for GSOC: > >> > >> - Support microcode update bundled in with the initrd in Xen. > >> Here is the Linux side of it comes out looking: > >> http://markmail.org/thread/ewrs7fa66knfwzbo > >> > >> - Write Xen PV Architecture Book/Manual/whatever. We have been > >> slowly going through the PV architecture and documenting it. > >> It would nice to have somebody full-time doing it and asking > >> questions. And then the answers would be written in this book. > >> > > > > IIRC the documentation-only project will not be accepted. > > So turn it into an executable specification and use that to generate > fuzz tests as well as documentation. > > In particular, doing this for more than just hypercalls, but also for > the ring protocols (to find bugs in the backend drivers) would be a > useful regression harness. Throw in all the latest additions like > multipage rings and various frontend options, and you will certainly > shake out a few bugs (I just accidentally found a netback crash that > I'm reporting separately). > Anil could you put this idea on the project list if you're interested. http://wiki.xen.org/wiki/Xen_Development_Projects We will start polishing the list for GSoC soon. Wei. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 16:13:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 16:13:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyGv-0004qQ-Ul; Wed, 09 Jan 2013 16:12:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyGu-0004q8-3w; Wed, 09 Jan 2013 16:12:56 +0000 Received: from [85.158.138.51:6861] by server-11.bemta-3.messagelabs.com id 57/01-13335-2079DE05; Wed, 09 Jan 2013 16:12:50 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1357747967!29430438!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTQ2MTg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13053 invoked from network); 9 Jan 2013 16:12:49 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 16:12:49 -0000 X-IronPort-AV: E=Sophos;i="4.84,438,1355097600"; d="scan'208";a="3198473" Received: from unknown (HELO FTLPEX01CL03.citrite.net) ([10.13.107.80]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 09 Jan 2013 16:12:37 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Wed, 9 Jan 2013 11:12:36 -0500 Received: from [10.80.3.80] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TsyGa-0005Nx-Nl; Wed, 09 Jan 2013 16:12:36 +0000 Message-ID: <1357747958.9068.10.camel@iceland> From: Wei Liu To: Anil Madhavapeddy Date: Wed, 9 Jan 2013 16:12:38 +0000 In-Reply-To: <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> X-Mailer: Evolution 3.6.0-0ubuntu3 MIME-Version: 1.0 Cc: wei.liu2@citrix.com, Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Wed, 2013-01-09 at 15:44 +0000, Anil Madhavapeddy wrote: > On 7 Jan 2013, at 16:39, Wei Liu wrote: > > > On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: > >> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > >>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > >>>>> c) Ideally I would like to add biography and interest section for > >>>>> all our mentors. I can create a wiki template for mentors if it > >>>>> helps > >> > >> Ideas for GSOC: > >> > >> - Support microcode update bundled in with the initrd in Xen. > >> Here is the Linux side of it comes out looking: > >> http://markmail.org/thread/ewrs7fa66knfwzbo > >> > >> - Write Xen PV Architecture Book/Manual/whatever. We have been > >> slowly going through the PV architecture and documenting it. > >> It would nice to have somebody full-time doing it and asking > >> questions. And then the answers would be written in this book. > >> > > > > IIRC the documentation-only project will not be accepted. > > So turn it into an executable specification and use that to generate > fuzz tests as well as documentation. > > In particular, doing this for more than just hypercalls, but also for > the ring protocols (to find bugs in the backend drivers) would be a > useful regression harness. Throw in all the latest additions like > multipage rings and various frontend options, and you will certainly > shake out a few bugs (I just accidentally found a netback crash that > I'm reporting separately). > Anil could you put this idea on the project list if you're interested. http://wiki.xen.org/wiki/Xen_Development_Projects We will start polishing the list for GSoC soon. Wei. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 16:14:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 16:14:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyIB-00053B-Q8; Wed, 09 Jan 2013 16:14:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyIB-00052y-9s for xen-api@lists.xen.org; Wed, 09 Jan 2013 16:14:15 +0000 Received: from [85.158.143.35:9057] by server-2.bemta-4.messagelabs.com id AB/F1-24322-6579DE05; Wed, 09 Jan 2013 16:14:14 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1357748053!15934029!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32435 invoked from network); 9 Jan 2013 16:14:14 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jan 2013 16:14:14 -0000 Received: from [187.233.68.172] (port=41362 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TsyI8-0002re-IQ for xen-api@lists.xen.org; Wed, 09 Jan 2013 10:14:12 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id D64D0A209 for ; Wed, 9 Jan 2013 10:11:16 -0600 (CST) Message-ID: <50ED9753.4060500@ondore.com> Date: Wed, 09 Jan 2013 10:14:11 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <1c84c978.c1ca.13c1fe8a6bc.Coremail.sainrun001@126.com> In-Reply-To: <1c84c978.c1ca.13c1fe8a6bc.Coremail.sainrun001@126.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] Questions for help - memory recycling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8uCgpFbCAwOS8wMS8xMyAwOToyMywg572R5a6JLeWNnumUpueoiyBlc2NyaWJpw7M6Cj4g ICAgICAgSWYgYSBndWVzdCBvcyBpcyBkZXN0cm95ZWQsaXMgdGhlIGludGVybmFsIG1lbW9yeSB0 aGF0IGl0IG9uY2UKPiBvY2N1cHllZCB3aWxsIHNjcmF0Y2hlZD8gSXMgdGhlIGludGVybmFsIG1l bW9yeSB0aGF0IGl0IG9uY2Ugb2NjdXB5ZWQKPiB3aWxsICByZWNvdmVyZWQ/CkkgZG9uJ3QgZnVs bHkgdW5kZXJzdGFuZCB3aGF0IGRvIHlvdSBtZWFuIGJ5ICJzY3JhdGNoZWQiLgpCdXQgeWVzLCBv bmNlIGEgZ3Vlc3QgVk0gKG5vdCByZWFsbHkgYSBndWVzdCBPUykgaWYgc2h1dCBkb3duIG9yIApk ZXN0cm95ZWQsIHRoZSBtZW1vcnkgaXQgd2FzIHVzaW5nIGlzIHJlY292ZXJlZC4gSXQgYmVjb21l cyBpbW1lZGlhdGVseSAKYXZhaWxhYmxlLCBhbmQgY2FuIGJlIGFzc2lnbmVkIHRvIGFueSBvdGhl ciBndWVzdCBWTS4KCj4gICAgICAgICBJZiBpdCB3aWxsIGJlIHNjcmF0Y2hlZCx3b3VsZCB5b3Ug c2hvdyBtZSB0aGUgY29ycmVzcG9uZGluZwo+IGNvZGVzIG9yIHRlc3RpbmcgcHJvZ2FtYT8KVGhl IHV0aWxpdHkgInhlbnRvcCIgY2FuIHNob3cgeW91IHRoZSBtZW1vcnkgdXNhZ2Ugc3RhdHVzIGJ5 IHRoZSAKaHlwZXJ2aXNvci4gVGhlIGRpc3BsYXkgaXMgdW51c3VhbGx5IHdpZGUgZm9yIGEgY29u c29sZSB1dGlsaXR5ICgxNjMgCmNoYXJhY3RlcnMpLCBkbyBub3QgbGV0IHlvdXJzZWxmIGNvbmZ1 c2UuIFdoaWxlIHlvdSBzdGFydCBhbmQgc3RvcCB5b3VyIApndWVzdCBWTSdzLCB5b3Ugd2lsbCBz ZWUgaG93IHRoZSBhbW91bnRzIG9mIHVzZWQgYW4gYXZhaWxhYmxlIG1lbW9yeSBjaGFuZ2UuCgpO b3RlLCB0aGF0IGlmIHlvdSB0cnkgInRvcCIgKG9yICJmcmVlIikgdXRpbGl0eSwgeW91IHdpbGwg cHJvYmFibHkgc2VlIApkaWZmZXJlbnQgbnVtYmVycy4gVGhhdCdzIGJlY2F1c2UgeGVudG9wIHdp bGwgc2hvdyB5b3UgaG90IHRoZSAKaHlwZXJ2aXNvciBzZWVzIHRoZSBtZW1vcnksIGFuZCB0b3Ag d2lsbCBzaG93IHlvdSBob3cgeW91ciBEb21haW4tMCAKKGNhbGxlZCBEb20wLCBmb3Igc2hvcnQp IHNlZXMgdGhlIG1lbW9yeS4gRm9yIHRoZSBoeXBlcnZpc29yLCBEb20wIGlzIApvbmUgb2YgdGhl IGd1ZXN0IG1hY2hpbmVzLgoKSG9wZSB0aGlzIGhlbHBzLgoKLS0gCkFsZXhhbmRyZSBLb3V6bmV0 c292CgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVu LWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4u b3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Wed Jan 09 16:14:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 16:14:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyIB-00053B-Q8; Wed, 09 Jan 2013 16:14:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyIB-00052y-9s for xen-api@lists.xen.org; Wed, 09 Jan 2013 16:14:15 +0000 Received: from [85.158.143.35:9057] by server-2.bemta-4.messagelabs.com id AB/F1-24322-6579DE05; Wed, 09 Jan 2013 16:14:14 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1357748053!15934029!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32435 invoked from network); 9 Jan 2013 16:14:14 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jan 2013 16:14:14 -0000 Received: from [187.233.68.172] (port=41362 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TsyI8-0002re-IQ for xen-api@lists.xen.org; Wed, 09 Jan 2013 10:14:12 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id D64D0A209 for ; Wed, 9 Jan 2013 10:11:16 -0600 (CST) Message-ID: <50ED9753.4060500@ondore.com> Date: Wed, 09 Jan 2013 10:14:11 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <1c84c978.c1ca.13c1fe8a6bc.Coremail.sainrun001@126.com> In-Reply-To: <1c84c978.c1ca.13c1fe8a6bc.Coremail.sainrun001@126.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] Questions for help - memory recycling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8uCgpFbCAwOS8wMS8xMyAwOToyMywg572R5a6JLeWNnumUpueoiyBlc2NyaWJpw7M6Cj4g ICAgICAgSWYgYSBndWVzdCBvcyBpcyBkZXN0cm95ZWQsaXMgdGhlIGludGVybmFsIG1lbW9yeSB0 aGF0IGl0IG9uY2UKPiBvY2N1cHllZCB3aWxsIHNjcmF0Y2hlZD8gSXMgdGhlIGludGVybmFsIG1l bW9yeSB0aGF0IGl0IG9uY2Ugb2NjdXB5ZWQKPiB3aWxsICByZWNvdmVyZWQ/CkkgZG9uJ3QgZnVs bHkgdW5kZXJzdGFuZCB3aGF0IGRvIHlvdSBtZWFuIGJ5ICJzY3JhdGNoZWQiLgpCdXQgeWVzLCBv bmNlIGEgZ3Vlc3QgVk0gKG5vdCByZWFsbHkgYSBndWVzdCBPUykgaWYgc2h1dCBkb3duIG9yIApk ZXN0cm95ZWQsIHRoZSBtZW1vcnkgaXQgd2FzIHVzaW5nIGlzIHJlY292ZXJlZC4gSXQgYmVjb21l cyBpbW1lZGlhdGVseSAKYXZhaWxhYmxlLCBhbmQgY2FuIGJlIGFzc2lnbmVkIHRvIGFueSBvdGhl ciBndWVzdCBWTS4KCj4gICAgICAgICBJZiBpdCB3aWxsIGJlIHNjcmF0Y2hlZCx3b3VsZCB5b3Ug c2hvdyBtZSB0aGUgY29ycmVzcG9uZGluZwo+IGNvZGVzIG9yIHRlc3RpbmcgcHJvZ2FtYT8KVGhl IHV0aWxpdHkgInhlbnRvcCIgY2FuIHNob3cgeW91IHRoZSBtZW1vcnkgdXNhZ2Ugc3RhdHVzIGJ5 IHRoZSAKaHlwZXJ2aXNvci4gVGhlIGRpc3BsYXkgaXMgdW51c3VhbGx5IHdpZGUgZm9yIGEgY29u c29sZSB1dGlsaXR5ICgxNjMgCmNoYXJhY3RlcnMpLCBkbyBub3QgbGV0IHlvdXJzZWxmIGNvbmZ1 c2UuIFdoaWxlIHlvdSBzdGFydCBhbmQgc3RvcCB5b3VyIApndWVzdCBWTSdzLCB5b3Ugd2lsbCBz ZWUgaG93IHRoZSBhbW91bnRzIG9mIHVzZWQgYW4gYXZhaWxhYmxlIG1lbW9yeSBjaGFuZ2UuCgpO b3RlLCB0aGF0IGlmIHlvdSB0cnkgInRvcCIgKG9yICJmcmVlIikgdXRpbGl0eSwgeW91IHdpbGwg cHJvYmFibHkgc2VlIApkaWZmZXJlbnQgbnVtYmVycy4gVGhhdCdzIGJlY2F1c2UgeGVudG9wIHdp bGwgc2hvdyB5b3UgaG90IHRoZSAKaHlwZXJ2aXNvciBzZWVzIHRoZSBtZW1vcnksIGFuZCB0b3Ag d2lsbCBzaG93IHlvdSBob3cgeW91ciBEb21haW4tMCAKKGNhbGxlZCBEb20wLCBmb3Igc2hvcnQp IHNlZXMgdGhlIG1lbW9yeS4gRm9yIHRoZSBoeXBlcnZpc29yLCBEb20wIGlzIApvbmUgb2YgdGhl IGd1ZXN0IG1hY2hpbmVzLgoKSG9wZSB0aGlzIGhlbHBzLgoKLS0gCkFsZXhhbmRyZSBLb3V6bmV0 c292CgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVu LWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4u b3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Wed Jan 09 16:19:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 16:19:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyNQ-0005Li-Bk; Wed, 09 Jan 2013 16:19:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyNO-0005LY-Ov for xen-api@lists.xen.org; Wed, 09 Jan 2013 16:19:39 +0000 Received: from [85.158.139.83:25661] by server-13.bemta-5.messagelabs.com id 86/87-10716-A989DE05; Wed, 09 Jan 2013 16:19:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-182.messagelabs.com!1357748377!30806086!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11238 invoked from network); 9 Jan 2013 16:19:37 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-182.messagelabs.com with SMTP; 9 Jan 2013 16:19:37 -0000 Received: (qmail 486 invoked by uid 634); 9 Jan 2013 16:19:36 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 09 Jan 2013 16:19:34 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1357747958.9068.10.camel@iceland> Date: Wed, 9 Jan 2013 16:19:35 +0000 Message-Id: References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> <1357747958.9068.10.camel@iceland> To: Wei Liu X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 9 Jan 2013, at 16:12, Wei Liu wrote: > On Wed, 2013-01-09 at 15:44 +0000, Anil Madhavapeddy wrote: >> On 7 Jan 2013, at 16:39, Wei Liu wrote: >> >>> On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: >>>> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: >>>>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: >>>>>>> c) Ideally I would like to add biography and interest section for >>>>>>> all our mentors. I can create a wiki template for mentors if it >>>>>>> helps >>>> >>>> Ideas for GSOC: >>>> >>>> - Support microcode update bundled in with the initrd in Xen. >>>> Here is the Linux side of it comes out looking: >>>> http://markmail.org/thread/ewrs7fa66knfwzbo >>>> >>>> - Write Xen PV Architecture Book/Manual/whatever. We have been >>>> slowly going through the PV architecture and documenting it. >>>> It would nice to have somebody full-time doing it and asking >>>> questions. And then the answers would be written in this book. >>>> >>> >>> IIRC the documentation-only project will not be accepted. >> >> So turn it into an executable specification and use that to generate >> fuzz tests as well as documentation. >> >> In particular, doing this for more than just hypercalls, but also for >> the ring protocols (to find bugs in the backend drivers) would be a >> useful regression harness. Throw in all the latest additions like >> multipage rings and various frontend options, and you will certainly >> shake out a few bugs (I just accidentally found a netback crash that >> I'm reporting separately). >> > > Anil could you put this idea on the project list if you're interested. > > http://wiki.xen.org/wiki/Xen_Development_Projects > > We will start polishing the list for GSoC soon. I put a similar one up a few months ago ("Fuzz testing Xen with Mirage"). -anil _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 16:19:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 16:19:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyNQ-0005Li-Bk; Wed, 09 Jan 2013 16:19:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyNO-0005LY-Ov for xen-api@lists.xen.org; Wed, 09 Jan 2013 16:19:39 +0000 Received: from [85.158.139.83:25661] by server-13.bemta-5.messagelabs.com id 86/87-10716-A989DE05; Wed, 09 Jan 2013 16:19:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-182.messagelabs.com!1357748377!30806086!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11238 invoked from network); 9 Jan 2013 16:19:37 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-182.messagelabs.com with SMTP; 9 Jan 2013 16:19:37 -0000 Received: (qmail 486 invoked by uid 634); 9 Jan 2013 16:19:36 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 09 Jan 2013 16:19:34 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1357747958.9068.10.camel@iceland> Date: Wed, 9 Jan 2013 16:19:35 +0000 Message-Id: References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> <1357747958.9068.10.camel@iceland> To: Wei Liu X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 9 Jan 2013, at 16:12, Wei Liu wrote: > On Wed, 2013-01-09 at 15:44 +0000, Anil Madhavapeddy wrote: >> On 7 Jan 2013, at 16:39, Wei Liu wrote: >> >>> On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: >>>> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: >>>>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: >>>>>>> c) Ideally I would like to add biography and interest section for >>>>>>> all our mentors. I can create a wiki template for mentors if it >>>>>>> helps >>>> >>>> Ideas for GSOC: >>>> >>>> - Support microcode update bundled in with the initrd in Xen. >>>> Here is the Linux side of it comes out looking: >>>> http://markmail.org/thread/ewrs7fa66knfwzbo >>>> >>>> - Write Xen PV Architecture Book/Manual/whatever. We have been >>>> slowly going through the PV architecture and documenting it. >>>> It would nice to have somebody full-time doing it and asking >>>> questions. And then the answers would be written in this book. >>>> >>> >>> IIRC the documentation-only project will not be accepted. >> >> So turn it into an executable specification and use that to generate >> fuzz tests as well as documentation. >> >> In particular, doing this for more than just hypercalls, but also for >> the ring protocols (to find bugs in the backend drivers) would be a >> useful regression harness. Throw in all the latest additions like >> multipage rings and various frontend options, and you will certainly >> shake out a few bugs (I just accidentally found a netback crash that >> I'm reporting separately). >> > > Anil could you put this idea on the project list if you're interested. > > http://wiki.xen.org/wiki/Xen_Development_Projects > > We will start polishing the list for GSoC soon. I put a similar one up a few months ago ("Fuzz testing Xen with Mirage"). -anil _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 09 16:41:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 16:41:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyiK-0006nH-Uy; Wed, 09 Jan 2013 16:41:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyiJ-0006mg-6r for xen-api@lists.xen.org; Wed, 09 Jan 2013 16:41:15 +0000 Received: from [85.158.139.211:33118] by server-14.bemta-5.messagelabs.com id 28/C8-09538-AAD9DE05; Wed, 09 Jan 2013 16:41:14 +0000 X-Env-Sender: sainrun001@126.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1357749666!23359372!1 X-Originating-IP: [220.181.15.66] X-SpamReason: No, hits=1.6 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjE1LjY2ID0+IDc1NDE=\n,sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjE1LjY2ID0+IDc1NDE=\n, DEAR_SOMETHING, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1316 invoked from network); 9 Jan 2013 16:41:08 -0000 Received: from m15-66.126.com (HELO m15-66.126.com) (220.181.15.66) by server-14.tower-206.messagelabs.com with SMTP; 9 Jan 2013 16:41:08 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=126.com; s=s110527; h=Received:Date:From:To:Subject:Content-Type: MIME-Version:Message-ID; bh=X/p6AmpOTseUXN/o/yXFeoyil33LFmCSuecX eMmGnKo=; b=Q4XHrrEwn3IDEnUVDf24BeLsyVicOI/nmhEdCQ+tnQTdvlWlt3aU X3YQRnzExlXyaVYKFcSH9LwmHGm0VLGMbIJmi+8uW3MMnzc/GQFLzH7YwnnL2jzu UObO0b9HzobcAFG8OUQKCpFK8puyhMlRrkgiy+ggtiZfNnhtNcjuyKo= Received: from sainrun001$126.com ( [116.213.171.15] ) by ajax-webmail-wmsvr66 (Coremail) ; Thu, 10 Jan 2013 00:41:02 +0800 (CST) X-Originating-IP: [116.213.171.15] Date: Thu, 10 Jan 2013 00:41:02 +0800 (CST) From: =?GBK?B?zfiwsi2x5b31s8w=?= To: xen-api@lists.xen.org X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20121219(21170.5156.5150) Copyright (c) 2002-2013 www.mailtech.cn 126com X-CM-CTRLDATA: 10OH6GZvb3Rlcl9odG09MzE3Njo4MQ== MIME-Version: 1.0 Message-ID: <399f1e9a.1811f.13c202fb1b9.Coremail.sainrun001@126.com> X-CM-TRANSID: QsqowACXGRCfne1QFxw+AA--.23192W X-CM-SenderInfo: hvdl02txqqiia6rslhhfrp/1tbiHBKf301r2d2nTAAAsH X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== Subject: [Xen-API] Is the internal memory that domU occupyed will scratched? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5536514857914006201==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5536514857914006201== Content-Type: multipart/alternative; boundary="----=_Part_366162_1439429742.1357749662137" ------=_Part_366162_1439429742.1357749662137 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit Dear Sir: I am a student of Computer Speciaty in a university. Now I am studying in principle of Xen Cloud Platform.There are a few of questions boring me and I have to seek help to you. If a guest os is destroyed,is the internal memory that it once occupyed will scratched? Is the internal memory that it once occupyed will recovered? If it will be scratched,would you show me the corresponding codes or testing progama?Expect your reply. Yours Sincerely; Chan 9th,Jan,2013 ------=_Part_366162_1439429742.1357749662137 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: 7bit
 Dear  Sir:
       I am a student of Computer Speciaty in a university.  Now I am studying in principle of Xen Cloud Platform.There are a few of questions boring me and I have to seek help to you.
       If a guest os is destroyed,is the internal memory that it once occupyed will scratched? Is the internal memory that it once occupyed will  recovered?
       If it will be scratched,would you show me the corresponding codes or testing progama?Expect your reply.
  
Yours 
Sincerely; 
Chan
                                                                                                                                                                                                                                                                                                                                                                         9th,Jan,2013


------=_Part_366162_1439429742.1357749662137-- --===============5536514857914006201== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5536514857914006201==-- From xen-api-bounces@lists.xen.org Wed Jan 09 16:41:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 09 Jan 2013 16:41:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyiK-0006nH-Uy; Wed, 09 Jan 2013 16:41:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyiJ-0006mg-6r for xen-api@lists.xen.org; Wed, 09 Jan 2013 16:41:15 +0000 Received: from [85.158.139.211:33118] by server-14.bemta-5.messagelabs.com id 28/C8-09538-AAD9DE05; Wed, 09 Jan 2013 16:41:14 +0000 X-Env-Sender: sainrun001@126.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1357749666!23359372!1 X-Originating-IP: [220.181.15.66] X-SpamReason: No, hits=1.6 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjE1LjY2ID0+IDc1NDE=\n,sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjE1LjY2ID0+IDc1NDE=\n, DEAR_SOMETHING, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1316 invoked from network); 9 Jan 2013 16:41:08 -0000 Received: from m15-66.126.com (HELO m15-66.126.com) (220.181.15.66) by server-14.tower-206.messagelabs.com with SMTP; 9 Jan 2013 16:41:08 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=126.com; s=s110527; h=Received:Date:From:To:Subject:Content-Type: MIME-Version:Message-ID; bh=X/p6AmpOTseUXN/o/yXFeoyil33LFmCSuecX eMmGnKo=; b=Q4XHrrEwn3IDEnUVDf24BeLsyVicOI/nmhEdCQ+tnQTdvlWlt3aU X3YQRnzExlXyaVYKFcSH9LwmHGm0VLGMbIJmi+8uW3MMnzc/GQFLzH7YwnnL2jzu UObO0b9HzobcAFG8OUQKCpFK8puyhMlRrkgiy+ggtiZfNnhtNcjuyKo= Received: from sainrun001$126.com ( [116.213.171.15] ) by ajax-webmail-wmsvr66 (Coremail) ; Thu, 10 Jan 2013 00:41:02 +0800 (CST) X-Originating-IP: [116.213.171.15] Date: Thu, 10 Jan 2013 00:41:02 +0800 (CST) From: =?GBK?B?zfiwsi2x5b31s8w=?= To: xen-api@lists.xen.org X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20121219(21170.5156.5150) Copyright (c) 2002-2013 www.mailtech.cn 126com X-CM-CTRLDATA: 10OH6GZvb3Rlcl9odG09MzE3Njo4MQ== MIME-Version: 1.0 Message-ID: <399f1e9a.1811f.13c202fb1b9.Coremail.sainrun001@126.com> X-CM-TRANSID: QsqowACXGRCfne1QFxw+AA--.23192W X-CM-SenderInfo: hvdl02txqqiia6rslhhfrp/1tbiHBKf301r2d2nTAAAsH X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== Subject: [Xen-API] Is the internal memory that domU occupyed will scratched? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5536514857914006201==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5536514857914006201== Content-Type: multipart/alternative; boundary="----=_Part_366162_1439429742.1357749662137" ------=_Part_366162_1439429742.1357749662137 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit Dear Sir: I am a student of Computer Speciaty in a university. Now I am studying in principle of Xen Cloud Platform.There are a few of questions boring me and I have to seek help to you. If a guest os is destroyed,is the internal memory that it once occupyed will scratched? Is the internal memory that it once occupyed will recovered? If it will be scratched,would you show me the corresponding codes or testing progama?Expect your reply. Yours Sincerely; Chan 9th,Jan,2013 ------=_Part_366162_1439429742.1357749662137 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: 7bit
 Dear  Sir:
       I am a student of Computer Speciaty in a university.  Now I am studying in principle of Xen Cloud Platform.There are a few of questions boring me and I have to seek help to you.
       If a guest os is destroyed,is the internal memory that it once occupyed will scratched? Is the internal memory that it once occupyed will  recovered?
       If it will be scratched,would you show me the corresponding codes or testing progama?Expect your reply.
  
Yours 
Sincerely; 
Chan
                                                                                                                                                                                                                                                                                                                                                                         9th,Jan,2013


------=_Part_366162_1439429742.1357749662137-- --===============5536514857914006201== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5536514857914006201==-- From xen-api-bounces@lists.xen.org Thu Jan 10 00:55:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 00:55:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6Qj-0007Uq-IC; Thu, 10 Jan 2013 00:55:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6Qh-0007Ul-Oz for xen-api@lists.xen.org; Thu, 10 Jan 2013 00:55:36 +0000 Received: from [85.158.139.83:25692] by server-2.bemta-5.messagelabs.com id 59/85-16162-7811EE05; Thu, 10 Jan 2013 00:55:35 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357779332!25620286!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29200 invoked from network); 10 Jan 2013 00:55:33 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-16.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2013 00:55:33 -0000 Received: from [187.233.68.172] (port=39502 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1Tt6Qe-0002Wq-6o for xen-api@lists.xen.org; Wed, 09 Jan 2013 18:55:32 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 93648A209 for ; Wed, 9 Jan 2013 18:52:35 -0600 (CST) Message-ID: <50EE1182.3090107@ondore.com> Date: Wed, 09 Jan 2013 18:55:30 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> In-Reply-To: <50EC606C.2070702@gmail.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] [Solved] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8uCgpJIGNhbiBjb25maXJtLCBJIGhhdmUgc3VjY2Vzc2Z1bGx5IG1vdW50ZWQgcGFydGl0 aW9ucyBmcm9tIG15IFZIRCBWREkgCnVuZGVyIERvbTAuIFRoYW5rcyBhIGxvdCEKCkVsIDA4LzAx LzEzIDEyOjA3LCBHZW9yZ2UgU2h1a2xpbiBlc2NyaWJpw7M6Cj4gT2ssIGhlcmUgaW1wb3J0YW50 IHN0dWZmLiBXaGVuIFZCRCBpcyBwbHVnZ2VkIHRvIGRvbTAsIGl0IHBsdWdnaW5nIG5vdAo+IGFz ICdub3JtYWwnIGRldmljZSAod2l0aCB1ZGV2IGF0dGVudGlvbiksIGJ1dCBhcyBkZXZpY2UgaW4g L2Rldi9zbS9iYWNrZW5kLgoKWWVzLCB0aGF0IHdhcyBpbXBvcnRhbnQuIFdoZXJlIGhhdmUgeW91 IGxlYXJuZWQgdGhhdCBvY2N1bHQgc3R1ZmY/Cgo+IEhlcmUgc2FtcGxlIGxvZyAoY2hhbmdlIHV1 aWRzIG9uIHlvdSB0YXN0ZSk6Cj4KPiB4ZSB2YmQtY3JlYXRlIHZtLXV1aWQ9NTNjM2Q4NzgtYjYw Yi00OGVjLWFhYWMtNzNmN2FkZjlhYjNkCj4gdmRpLXV1aWQ9NWUyYzMxYTUtMWQxYi00YWJlLTk4 OTItMWZhM2JjNDdiNTMyIGRldmljZT02Cj4geGUgdmJkLXBsdWcgdXVpZD00MDdlYjNhNi05MTlm LWY2MDUtMDg4My1lMTJhYWE5MTMyMWQKPgo+IGxzIC1sYSAvZGV2L3NtL2JhY2tlbmQvNTVlYTIw ZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyLwo+INC40YLQvtCz0L4gNAo+IGRyd3hyLXhy LXggMiByb290IHJvb3QgICAgIDgwINCv0L3QsiAgOCAyMTo1NyAuCj4gZHJ3eHIteHIteCAzIHJv b3Qgcm9vdCAgICAgNjAg0JTQtdC6IDE4IDE3OjQwIC4uCj4gYnJ3LS0tLS0tLSAxIHJvb3Qgcm9v dCAyNTMsIDAg0K/QvdCyICA4IDIxOjU3Cj4gNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2Jj NDdiNTMyCj4gLXJ3LXItLXItLSAxIHJvb3Qgcm9vdCAgICA4NTIg0K/QvdCyICA4IDIxOjU3Cj4g NWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyLmF0dGFjaF9pbmZvCkkgaGF2ZSBk b25lIHRoZSBwcm9jZXNzIGFzIHlvdSBkZXNjcmliZWQuCkdvdCB0aGUgc2FtZSByZXN1bHQgYXMg eW91LCBleGNlcHQgdGhhdCBJIGRvbid0IGhhdmUgKi5hdHRhY2hfaW5mbyBmaWxlLCAKb25seSB0 aGUgZGV2aWNlIGZpbGUuCgpXaGF0IGlzIHRoZSByZWxldmFuY2Ugb2YgZGV2aWNlPTYgdW5kZXIg dmJkLWNyZWF0ZSBjb21tYW5kPyBSZWFsbHkgZGlkIApub3Qga25ldyB3aGF0IHRvIHB1dCB0aGVy ZSwgSSBoYXZlIHVzZWQgZGV2aWNlPWF1dG9kZXRlY3QsIGhvcGUgWENQIGlzIApzbWFydCBlbm91 Z2ggdG8gY2xlYW4gdXAgZXZlcnl0aGluZyBuaWNlbHkgYWZ0ZXIgSSB1bnBsdWcgaXQuCgoKPiBJ IGhhdmUgbm8gaWRlYSB3aHkgJzU1JyB1dWlkIChhbmQgd2hhdCBpdCBtZWFucyksIGJ1dAo+IDVl MmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMiBpcyBibG9jayBkZXZpY2UgYWZ0ZXIg d2hvbGUgVkhECj4gdHJlZSBqb2luaW5nL3BhcnNpbmcgYW5kIHNvIG9uLgpGb3IgcmVmZXJlbmNl LCBpdCBzZWVtcyBsaWtlIHRoZSBuZXcgY3JlYXRlZCBkZXZpY2UgZnVsbCBwYXRoIGlzOgovZGV2 L3NtL2JhY2tlbmQvPHNyLXV1aWQ+Lzx2ZGktdXVpZD4KVGhhdCAiNTUuLi4iIG11c3QgYmUgeW91 ciBTUi4KCgpSZWZlcmVuY2UgKHdpZGUgYW5kIGNvbmZ1c2luZyBvdXRwdXQsIEkga25vdyk6Cgpy b290QHhjcDQ3IH5dIyB4ZSB2YmQtY3JlYXRlIGRldmljZT1hdXRvZGV0ZWN0IAp2bS11dWlkPWVm NWVlZGM0LWNiOGMtNGQ1OC1hYmY5LTI2MTc5MTk1ZWY2MiAKdmRpLXV1aWQ9ZmQxMThkYTEtYzNk ZC00NjZiLThiMjctMzJjNWRiMWZjY2U3CiMgUmV0dXJucyBWQkQgdXVpZDogYjMwZmRmY2QtZTg0 Ni0wZWQ0LTZlNjMtZmQ5ODcxYWMyYTY1CiMgbm8gL2Rldi9zbSBhdCBhbGwsIHlldAoKcm9vdEB4 Y3A0NyB+XSMgeGUgdmJkLXBsdWcgdXVpZD1iMzBmZGZjZC1lODQ2LTBlZDQtNmU2My1mZDk4NzFh YzJhNjUKIyBOb3cgdmlzaWJsZSAvZGV2L3NtL2JhY2tlbmQvPHNyLXV1aWQ+Lzx2ZGktdXVpZD4K CnJvb3RAeGNwNDcgfl0jIGZkaXNrIC1sIAovZGV2L3NtL2JhY2tlbmQvY2ZjNzQxOWYtOGI0ZS04 YzUxLWQ2MTktZGZkZWUwOTg0MWEyL2ZkMTE4ZGExLWMzZGQtNDY2Yi04YjI3LTMyYzVkYjFmY2Nl NwpEaXNjbyAKL2Rldi9zbS9iYWNrZW5kL2NmYzc0MTlmLThiNGUtOGM1MS1kNjE5LWRmZGVlMDk4 NDFhMi9mZDExOGRhMS1jM2RkLTQ2NmItOGIyNy0zMmM1ZGIxZmNjZTc6IAozMjIxIE1CLCAzMjIx MjI1NDcyIGJ5dGVzCjI1NSBoZWFkcywgNjMgc2VjdG9ycy90cmFjaywgMzkxIGN5bGluZGVycwpV bmlkYWRlcyA9IGNpbGluZHJvcyBkZSAxNjA2NSAqIDUxMiA9IDgyMjUyODAgYnl0ZXMKCiAKICAg ICAgICAgICAgRGlzcG9zaXQuIEluaWNpbyAgICBDb21pZW56byAgICAgIEZpbiAgICAgIEJsb3F1 ZXMgIElkICBTaXN0ZW1hCi9kZXYvc20vYmFja2VuZC9jZmM3NDE5Zi04YjRlLThjNTEtZDYxOS1k ZmRlZTA5ODQxYTIvZmQxMThkYTEtYzNkZC00NjZiLThiMjctMzIgCiAgICAgICAgICAgICAgMSAg ICAgICAgIDIwMCAgICAgMTYwNjQ2OCsgIDgzICBMaW51eAovZGV2L3NtL2JhY2tlbmQvY2ZjNzQx OWYtOGI0ZS04YzUxLWQ2MTktZGZkZWUwOTg0MWEyL2ZkMTE4ZGExLWMzZGQtNDY2Yi04YjI3LTMy IAogICAgICAgICAgICAyMDEgICAgICAgICAzOTEgICAgIDE1MzQyMDcrICA4MyAgTGludXgKCnJv b3RAeGNwNDcgfl0jIGtwYXJ0eCAtYSAKL2Rldi9zbS9iYWNrZW5kL2NmYzc0MTlmLThiNGUtOGM1 MS1kNjE5LWRmZGVlMDk4NDFhMi9mZDExOGRhMS1jM2RkLTQ2NmItOGIyNy0zMmM1ZGIxZmNjZTcK cm9vdEB4Y3A0NyB+XSMgbW91bnQgL2Rldi9tYXBwZXIvZmQxMThkYTEtYzNkZC00NjZiLThiMjct MzJjNWRiMWZjY2U3cDEgCi9tbnQvYWExCnJvb3RAeGNwNDcgfl0jIG1vdW50IC9kZXYvbWFwcGVy L2ZkMTE4ZGExLWMzZGQtNDY2Yi04YjI3LTMyYzVkYjFmY2NlN3AxIAovbW50L2FhMgpbcm9vdEB4 Y3A0NyB+XSMgbHMgL21udC9hYTEKbG9zdCtmb3VuZCAgeHZkYjFfZmxhZwpbcm9vdEB4Y3A0NyB+ XSMgbHMgL21udC9hYTIKbG9zdCtmb3VuZCAgeHZkYjJfZmxhZwoKCi0tIApBbGV4YW5kcmUgS291 em5ldHNvdgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Clhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Thu Jan 10 00:55:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 00:55:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6Qj-0007Uq-IC; Thu, 10 Jan 2013 00:55:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6Qh-0007Ul-Oz for xen-api@lists.xen.org; Thu, 10 Jan 2013 00:55:36 +0000 Received: from [85.158.139.83:25692] by server-2.bemta-5.messagelabs.com id 59/85-16162-7811EE05; Thu, 10 Jan 2013 00:55:35 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1357779332!25620286!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29200 invoked from network); 10 Jan 2013 00:55:33 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-16.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2013 00:55:33 -0000 Received: from [187.233.68.172] (port=39502 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1Tt6Qe-0002Wq-6o for xen-api@lists.xen.org; Wed, 09 Jan 2013 18:55:32 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 93648A209 for ; Wed, 9 Jan 2013 18:52:35 -0600 (CST) Message-ID: <50EE1182.3090107@ondore.com> Date: Wed, 09 Jan 2013 18:55:30 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> In-Reply-To: <50EC606C.2070702@gmail.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] [Solved] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8uCgpJIGNhbiBjb25maXJtLCBJIGhhdmUgc3VjY2Vzc2Z1bGx5IG1vdW50ZWQgcGFydGl0 aW9ucyBmcm9tIG15IFZIRCBWREkgCnVuZGVyIERvbTAuIFRoYW5rcyBhIGxvdCEKCkVsIDA4LzAx LzEzIDEyOjA3LCBHZW9yZ2UgU2h1a2xpbiBlc2NyaWJpw7M6Cj4gT2ssIGhlcmUgaW1wb3J0YW50 IHN0dWZmLiBXaGVuIFZCRCBpcyBwbHVnZ2VkIHRvIGRvbTAsIGl0IHBsdWdnaW5nIG5vdAo+IGFz ICdub3JtYWwnIGRldmljZSAod2l0aCB1ZGV2IGF0dGVudGlvbiksIGJ1dCBhcyBkZXZpY2UgaW4g L2Rldi9zbS9iYWNrZW5kLgoKWWVzLCB0aGF0IHdhcyBpbXBvcnRhbnQuIFdoZXJlIGhhdmUgeW91 IGxlYXJuZWQgdGhhdCBvY2N1bHQgc3R1ZmY/Cgo+IEhlcmUgc2FtcGxlIGxvZyAoY2hhbmdlIHV1 aWRzIG9uIHlvdSB0YXN0ZSk6Cj4KPiB4ZSB2YmQtY3JlYXRlIHZtLXV1aWQ9NTNjM2Q4NzgtYjYw Yi00OGVjLWFhYWMtNzNmN2FkZjlhYjNkCj4gdmRpLXV1aWQ9NWUyYzMxYTUtMWQxYi00YWJlLTk4 OTItMWZhM2JjNDdiNTMyIGRldmljZT02Cj4geGUgdmJkLXBsdWcgdXVpZD00MDdlYjNhNi05MTlm LWY2MDUtMDg4My1lMTJhYWE5MTMyMWQKPgo+IGxzIC1sYSAvZGV2L3NtL2JhY2tlbmQvNTVlYTIw ZDItODYxMS0xMTIxLTllOWUtYzI2YjM1YWMxODUyLwo+INC40YLQvtCz0L4gNAo+IGRyd3hyLXhy LXggMiByb290IHJvb3QgICAgIDgwINCv0L3QsiAgOCAyMTo1NyAuCj4gZHJ3eHIteHIteCAzIHJv b3Qgcm9vdCAgICAgNjAg0JTQtdC6IDE4IDE3OjQwIC4uCj4gYnJ3LS0tLS0tLSAxIHJvb3Qgcm9v dCAyNTMsIDAg0K/QvdCyICA4IDIxOjU3Cj4gNWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2Jj NDdiNTMyCj4gLXJ3LXItLXItLSAxIHJvb3Qgcm9vdCAgICA4NTIg0K/QvdCyICA4IDIxOjU3Cj4g NWUyYzMxYTUtMWQxYi00YWJlLTk4OTItMWZhM2JjNDdiNTMyLmF0dGFjaF9pbmZvCkkgaGF2ZSBk b25lIHRoZSBwcm9jZXNzIGFzIHlvdSBkZXNjcmliZWQuCkdvdCB0aGUgc2FtZSByZXN1bHQgYXMg eW91LCBleGNlcHQgdGhhdCBJIGRvbid0IGhhdmUgKi5hdHRhY2hfaW5mbyBmaWxlLCAKb25seSB0 aGUgZGV2aWNlIGZpbGUuCgpXaGF0IGlzIHRoZSByZWxldmFuY2Ugb2YgZGV2aWNlPTYgdW5kZXIg dmJkLWNyZWF0ZSBjb21tYW5kPyBSZWFsbHkgZGlkIApub3Qga25ldyB3aGF0IHRvIHB1dCB0aGVy ZSwgSSBoYXZlIHVzZWQgZGV2aWNlPWF1dG9kZXRlY3QsIGhvcGUgWENQIGlzIApzbWFydCBlbm91 Z2ggdG8gY2xlYW4gdXAgZXZlcnl0aGluZyBuaWNlbHkgYWZ0ZXIgSSB1bnBsdWcgaXQuCgoKPiBJ IGhhdmUgbm8gaWRlYSB3aHkgJzU1JyB1dWlkIChhbmQgd2hhdCBpdCBtZWFucyksIGJ1dAo+IDVl MmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMiBpcyBibG9jayBkZXZpY2UgYWZ0ZXIg d2hvbGUgVkhECj4gdHJlZSBqb2luaW5nL3BhcnNpbmcgYW5kIHNvIG9uLgpGb3IgcmVmZXJlbmNl LCBpdCBzZWVtcyBsaWtlIHRoZSBuZXcgY3JlYXRlZCBkZXZpY2UgZnVsbCBwYXRoIGlzOgovZGV2 L3NtL2JhY2tlbmQvPHNyLXV1aWQ+Lzx2ZGktdXVpZD4KVGhhdCAiNTUuLi4iIG11c3QgYmUgeW91 ciBTUi4KCgpSZWZlcmVuY2UgKHdpZGUgYW5kIGNvbmZ1c2luZyBvdXRwdXQsIEkga25vdyk6Cgpy b290QHhjcDQ3IH5dIyB4ZSB2YmQtY3JlYXRlIGRldmljZT1hdXRvZGV0ZWN0IAp2bS11dWlkPWVm NWVlZGM0LWNiOGMtNGQ1OC1hYmY5LTI2MTc5MTk1ZWY2MiAKdmRpLXV1aWQ9ZmQxMThkYTEtYzNk ZC00NjZiLThiMjctMzJjNWRiMWZjY2U3CiMgUmV0dXJucyBWQkQgdXVpZDogYjMwZmRmY2QtZTg0 Ni0wZWQ0LTZlNjMtZmQ5ODcxYWMyYTY1CiMgbm8gL2Rldi9zbSBhdCBhbGwsIHlldAoKcm9vdEB4 Y3A0NyB+XSMgeGUgdmJkLXBsdWcgdXVpZD1iMzBmZGZjZC1lODQ2LTBlZDQtNmU2My1mZDk4NzFh YzJhNjUKIyBOb3cgdmlzaWJsZSAvZGV2L3NtL2JhY2tlbmQvPHNyLXV1aWQ+Lzx2ZGktdXVpZD4K CnJvb3RAeGNwNDcgfl0jIGZkaXNrIC1sIAovZGV2L3NtL2JhY2tlbmQvY2ZjNzQxOWYtOGI0ZS04 YzUxLWQ2MTktZGZkZWUwOTg0MWEyL2ZkMTE4ZGExLWMzZGQtNDY2Yi04YjI3LTMyYzVkYjFmY2Nl NwpEaXNjbyAKL2Rldi9zbS9iYWNrZW5kL2NmYzc0MTlmLThiNGUtOGM1MS1kNjE5LWRmZGVlMDk4 NDFhMi9mZDExOGRhMS1jM2RkLTQ2NmItOGIyNy0zMmM1ZGIxZmNjZTc6IAozMjIxIE1CLCAzMjIx MjI1NDcyIGJ5dGVzCjI1NSBoZWFkcywgNjMgc2VjdG9ycy90cmFjaywgMzkxIGN5bGluZGVycwpV bmlkYWRlcyA9IGNpbGluZHJvcyBkZSAxNjA2NSAqIDUxMiA9IDgyMjUyODAgYnl0ZXMKCiAKICAg ICAgICAgICAgRGlzcG9zaXQuIEluaWNpbyAgICBDb21pZW56byAgICAgIEZpbiAgICAgIEJsb3F1 ZXMgIElkICBTaXN0ZW1hCi9kZXYvc20vYmFja2VuZC9jZmM3NDE5Zi04YjRlLThjNTEtZDYxOS1k ZmRlZTA5ODQxYTIvZmQxMThkYTEtYzNkZC00NjZiLThiMjctMzIgCiAgICAgICAgICAgICAgMSAg ICAgICAgIDIwMCAgICAgMTYwNjQ2OCsgIDgzICBMaW51eAovZGV2L3NtL2JhY2tlbmQvY2ZjNzQx OWYtOGI0ZS04YzUxLWQ2MTktZGZkZWUwOTg0MWEyL2ZkMTE4ZGExLWMzZGQtNDY2Yi04YjI3LTMy IAogICAgICAgICAgICAyMDEgICAgICAgICAzOTEgICAgIDE1MzQyMDcrICA4MyAgTGludXgKCnJv b3RAeGNwNDcgfl0jIGtwYXJ0eCAtYSAKL2Rldi9zbS9iYWNrZW5kL2NmYzc0MTlmLThiNGUtOGM1 MS1kNjE5LWRmZGVlMDk4NDFhMi9mZDExOGRhMS1jM2RkLTQ2NmItOGIyNy0zMmM1ZGIxZmNjZTcK cm9vdEB4Y3A0NyB+XSMgbW91bnQgL2Rldi9tYXBwZXIvZmQxMThkYTEtYzNkZC00NjZiLThiMjct MzJjNWRiMWZjY2U3cDEgCi9tbnQvYWExCnJvb3RAeGNwNDcgfl0jIG1vdW50IC9kZXYvbWFwcGVy L2ZkMTE4ZGExLWMzZGQtNDY2Yi04YjI3LTMyYzVkYjFmY2NlN3AxIAovbW50L2FhMgpbcm9vdEB4 Y3A0NyB+XSMgbHMgL21udC9hYTEKbG9zdCtmb3VuZCAgeHZkYjFfZmxhZwpbcm9vdEB4Y3A0NyB+ XSMgbHMgL21udC9hYTIKbG9zdCtmb3VuZCAgeHZkYjJfZmxhZwoKCi0tIApBbGV4YW5kcmUgS291 em5ldHNvdgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Clhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Thu Jan 10 01:07:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 01:07:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6cF-0002zv-Kf; Thu, 10 Jan 2013 01:07:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt48q-00059y-Em for xen-api@lists.xen.org; Wed, 09 Jan 2013 22:29:00 +0000 Received: from [85.158.143.35:6376] by server-3.bemta-4.messagelabs.com id 4B/82-19220-B2FEDE05; Wed, 09 Jan 2013 22:28:59 +0000 X-Env-Sender: chris@aquatic-edge.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1357770492!14000259!1 X-Originating-IP: [209.85.210.54] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17596 invoked from network); 9 Jan 2013 22:28:14 -0000 Received: from mail-da0-f54.google.com (HELO mail-da0-f54.google.com) (209.85.210.54) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 22:28:14 -0000 Received: by mail-da0-f54.google.com with SMTP id n2so964870dad.41 for ; Wed, 09 Jan 2013 14:28:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:content-type:subject:message-id:date:to :mime-version:x-mailer:x-gm-message-state; bh=+WvgKffPx3cYsRjLRjSi/pEc6xDC2JmYyWhrKyld7F0=; b=Q32C1C5phGeCU3uJotWqlgBLptHi357EH4xLl4vKLqgQdHZRKUJRwzyvJJlPu9xFcB VshlpqeM5Lz4uaSJpLWx0IQBAhqYkCHqGsvcGMTcaf/YzB345AcmOlRkyZYokSKFBZAa d0qDqehfJYVXcyHqK3Xhtiu8n1N2r7uJKaWGtDHHROp4d2KegkIFJzmPWOsP98l6RVs8 eVCKr2/oYxpzKo6uOfj/TyGYh4JmVZr0FiXr1mCW0vb23/Cd+CIc9toLAOIcuCGoioe8 cEwPWZ/1DCbZpN8Gw9kGr4ZMzwUPGaKpOJRP0gd9MDEcRLW4TizmcdUJct9SLFiCw1Mn 5wOw== X-Received: by 10.66.83.6 with SMTP id m6mr193367545pay.52.1357770491689; Wed, 09 Jan 2013 14:28:11 -0800 (PST) Received: from [192.168.15.109] (75-151-125-226-Washington.hfc.comcastbusiness.net. [75.151.125.226]) by mx.google.com with ESMTPS id v2sm43526155paz.36.2013.01.09.14.28.08 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Jan 2013 14:28:10 -0800 (PST) From: Chris Dutton Message-Id: <56A32708-950E-4E6B-BD05-A76CB660ECB8@aquatic-edge.com> Date: Wed, 9 Jan 2013 14:27:59 -0800 To: xen-api@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQnt0tl4CkfaQFRXUJuYF6LaElzbMn0UruGaa3GAcd1ymdbMwFffPSnlIazNfvGt3EvJQNf2 X-Mailman-Approved-At: Thu, 10 Jan 2013 01:07:31 +0000 Subject: [Xen-API] Storage XenMotion - Just sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0000904848337109759==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0000904848337109759== Content-Type: multipart/alternative; boundary="Apple-Mail=_378C57ED-F3B6-49E2-B669-0B163FB53B44" --Apple-Mail=_378C57ED-F3B6-49E2-B669-0B163FB53B44 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hello, What I am trying to accomplish is keep a vm on one host (a) in sync with = another vm on host (b). They are both using local storage for the SR, = which led me to investigate SXM. But it looks like it does just a little = more then I want. =46rom the Storage XenMotion wiki page: Each of a VM=92s disks are snapshotted, and from the point of = the snapshot onwards, all of the disk=92s writes are synchronously = mirrored to the destination storage repository. In the background, the = snapshotted disk is copied to the destination location. Once a snapshot = has finished copying, the next disk to be migrated is snapshot/mirrored. What I am hoping to do is everything except the last step (the actual = migration).=20 Is it possible to pass a flag (maybe undocumented) that could accomplish = this? Or does someone know the list of commands that may accomplish = this. The sync does not necessarily have to be synchronous for my situation, = so maybe run a sync as a cron job but when a sync happens I only want = the deltas copied (not a full snapshot). Thanks in advance. --Apple-Mail=_378C57ED-F3B6-49E2-B669-0B163FB53B44 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 = Each of a VM=92s disks are snapshotted, and from the point of the = snapshot onwards, all of the disk=92s writes are synchronously mirrored = to the destination storage repository. In the background, the = snapshotted disk is copied to the destination location. Once a snapshot = has finished copying, the next disk to be migrated is = snapshot/mirrored.

What I am hoping to do is everything except the = last step (the actual migration). 

Is it possible to pass a flag = (maybe undocumented) that could accomplish this? Or does someone know = the list of commands that may accomplish this.

The sync does not necessarily have to be synchronous = for my situation, so maybe run a sync as a cron job but when a sync = happens I only want the deltas copied (not a full = snapshot).

Thanks in advance.

= --Apple-Mail=_378C57ED-F3B6-49E2-B669-0B163FB53B44-- --===============0000904848337109759== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0000904848337109759==-- From xen-api-bounces@lists.xen.org Thu Jan 10 01:07:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 01:07:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6cF-0002zv-Kf; Thu, 10 Jan 2013 01:07:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt48q-00059y-Em for xen-api@lists.xen.org; Wed, 09 Jan 2013 22:29:00 +0000 Received: from [85.158.143.35:6376] by server-3.bemta-4.messagelabs.com id 4B/82-19220-B2FEDE05; Wed, 09 Jan 2013 22:28:59 +0000 X-Env-Sender: chris@aquatic-edge.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1357770492!14000259!1 X-Originating-IP: [209.85.210.54] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17596 invoked from network); 9 Jan 2013 22:28:14 -0000 Received: from mail-da0-f54.google.com (HELO mail-da0-f54.google.com) (209.85.210.54) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2013 22:28:14 -0000 Received: by mail-da0-f54.google.com with SMTP id n2so964870dad.41 for ; Wed, 09 Jan 2013 14:28:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:content-type:subject:message-id:date:to :mime-version:x-mailer:x-gm-message-state; bh=+WvgKffPx3cYsRjLRjSi/pEc6xDC2JmYyWhrKyld7F0=; b=Q32C1C5phGeCU3uJotWqlgBLptHi357EH4xLl4vKLqgQdHZRKUJRwzyvJJlPu9xFcB VshlpqeM5Lz4uaSJpLWx0IQBAhqYkCHqGsvcGMTcaf/YzB345AcmOlRkyZYokSKFBZAa d0qDqehfJYVXcyHqK3Xhtiu8n1N2r7uJKaWGtDHHROp4d2KegkIFJzmPWOsP98l6RVs8 eVCKr2/oYxpzKo6uOfj/TyGYh4JmVZr0FiXr1mCW0vb23/Cd+CIc9toLAOIcuCGoioe8 cEwPWZ/1DCbZpN8Gw9kGr4ZMzwUPGaKpOJRP0gd9MDEcRLW4TizmcdUJct9SLFiCw1Mn 5wOw== X-Received: by 10.66.83.6 with SMTP id m6mr193367545pay.52.1357770491689; Wed, 09 Jan 2013 14:28:11 -0800 (PST) Received: from [192.168.15.109] (75-151-125-226-Washington.hfc.comcastbusiness.net. [75.151.125.226]) by mx.google.com with ESMTPS id v2sm43526155paz.36.2013.01.09.14.28.08 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Jan 2013 14:28:10 -0800 (PST) From: Chris Dutton Message-Id: <56A32708-950E-4E6B-BD05-A76CB660ECB8@aquatic-edge.com> Date: Wed, 9 Jan 2013 14:27:59 -0800 To: xen-api@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQnt0tl4CkfaQFRXUJuYF6LaElzbMn0UruGaa3GAcd1ymdbMwFffPSnlIazNfvGt3EvJQNf2 X-Mailman-Approved-At: Thu, 10 Jan 2013 01:07:31 +0000 Subject: [Xen-API] Storage XenMotion - Just sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0000904848337109759==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0000904848337109759== Content-Type: multipart/alternative; boundary="Apple-Mail=_378C57ED-F3B6-49E2-B669-0B163FB53B44" --Apple-Mail=_378C57ED-F3B6-49E2-B669-0B163FB53B44 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hello, What I am trying to accomplish is keep a vm on one host (a) in sync with = another vm on host (b). They are both using local storage for the SR, = which led me to investigate SXM. But it looks like it does just a little = more then I want. =46rom the Storage XenMotion wiki page: Each of a VM=92s disks are snapshotted, and from the point of = the snapshot onwards, all of the disk=92s writes are synchronously = mirrored to the destination storage repository. In the background, the = snapshotted disk is copied to the destination location. Once a snapshot = has finished copying, the next disk to be migrated is snapshot/mirrored. What I am hoping to do is everything except the last step (the actual = migration).=20 Is it possible to pass a flag (maybe undocumented) that could accomplish = this? Or does someone know the list of commands that may accomplish = this. The sync does not necessarily have to be synchronous for my situation, = so maybe run a sync as a cron job but when a sync happens I only want = the deltas copied (not a full snapshot). Thanks in advance. --Apple-Mail=_378C57ED-F3B6-49E2-B669-0B163FB53B44 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 = Each of a VM=92s disks are snapshotted, and from the point of the = snapshot onwards, all of the disk=92s writes are synchronously mirrored = to the destination storage repository. In the background, the = snapshotted disk is copied to the destination location. Once a snapshot = has finished copying, the next disk to be migrated is = snapshot/mirrored.

What I am hoping to do is everything except the = last step (the actual migration). 

Is it possible to pass a flag = (maybe undocumented) that could accomplish this? Or does someone know = the list of commands that may accomplish this.

The sync does not necessarily have to be synchronous = for my situation, so maybe run a sync as a cron job but when a sync = happens I only want the deltas copied (not a full = snapshot).

Thanks in advance.

= --Apple-Mail=_378C57ED-F3B6-49E2-B669-0B163FB53B44-- --===============0000904848337109759== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0000904848337109759==-- From xen-api-bounces@lists.xen.org Thu Jan 10 01:07:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 01:07:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6cZ-00030X-RA; Thu, 10 Jan 2013 01:07:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6cY-00030S-Be for xen-api@lists.xen.org; Thu, 10 Jan 2013 01:07:50 +0000 Received: from [85.158.138.51:57778] by server-5.bemta-3.messagelabs.com id 17/79-04992-5641EE05; Thu, 10 Jan 2013 01:07:49 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1357780067!30196235!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20006 invoked from network); 10 Jan 2013 01:07:49 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-15.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2013 01:07:49 -0000 Received: from [187.233.68.172] (port=44667 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1Tt6cV-0004DG-Bj for xen-api@lists.xen.org; Wed, 09 Jan 2013 19:07:47 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 996A8A209 for ; Wed, 9 Jan 2013 19:04:50 -0600 (CST) Message-ID: <50EE1461.7080509@ondore.com> Date: Wed, 09 Jan 2013 19:07:45 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> <50EC66D2.8060304@gmail.com> <602C5EB92F9AFB4D89D11B9F5B7F1355200AF149@SM-DAG151.softlayer.local> In-Reply-To: <602C5EB92F9AFB4D89D11B9F5B7F1355200AF149@SM-DAG151.softlayer.local> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8uCgpFbCAwOC8wMS8xMyAxMjo0MCwgSm9zZXBoIEhvbSBlc2NyaWJpw7M6Cj4gU29ycnkg SSBtaXN0eXBlZCB0aGUgcGF0aC4gVGhlIGRldmljZSBwYXRoIGxpc3RlZCBpbiB0aGUgdmJkIGlz IHdoYXQgeW91IHNob3VsZCBiZSB1c2luZyBrcGFydHggb24KPgo+IGUuZy4KPgo+IGtwYXJ0eCAt YXYgL2Rldi9zbS9iYWNrZW5kLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi81 ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzIKPgo+IFRoaXMgd2lsbCBleHBvc2Ug dGhlIHBhcnRpdGlvbnMgd2hpY2ggeW91IGNhbiBmaW5kIGluIC9kZXYvbWFwcGVyLgpZZXMsIGdv dCBpdC4gVGhhbmsgeW91IGZvciBoZWxwLgoKSSBoYXZlIHVzZWQga3BhcnR4IHdpdGggcmF3IExW TSB2b2x1bWVzIGJlZm9yZS4gV29uZGVyaW5nIHdoYXQncyB3cm9uZyAKd2l0aCAidmhkcGFydHgi LiBJIGhhdmUgZXhwZWN0ZWQgaXQgdG8gZG8gdGhlIHNhbWUuCgpDaGVlcnMuCgotLSAKQWxleGFu ZHJlIEtvdXpuZXRzb3YKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDov L2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Thu Jan 10 01:07:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 01:07:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6cZ-00030X-RA; Thu, 10 Jan 2013 01:07:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6cY-00030S-Be for xen-api@lists.xen.org; Thu, 10 Jan 2013 01:07:50 +0000 Received: from [85.158.138.51:57778] by server-5.bemta-3.messagelabs.com id 17/79-04992-5641EE05; Thu, 10 Jan 2013 01:07:49 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1357780067!30196235!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20006 invoked from network); 10 Jan 2013 01:07:49 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-15.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2013 01:07:49 -0000 Received: from [187.233.68.172] (port=44667 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1Tt6cV-0004DG-Bj for xen-api@lists.xen.org; Wed, 09 Jan 2013 19:07:47 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 996A8A209 for ; Wed, 9 Jan 2013 19:04:50 -0600 (CST) Message-ID: <50EE1461.7080509@ondore.com> Date: Wed, 09 Jan 2013 19:07:45 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> <602C5EB92F9AFB4D89D11B9F5B7F1355200AF0D7@SM-DAG151.softlayer.local> <50EC66D2.8060304@gmail.com> <602C5EB92F9AFB4D89D11B9F5B7F1355200AF149@SM-DAG151.softlayer.local> In-Reply-To: <602C5EB92F9AFB4D89D11B9F5B7F1355200AF149@SM-DAG151.softlayer.local> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8uCgpFbCAwOC8wMS8xMyAxMjo0MCwgSm9zZXBoIEhvbSBlc2NyaWJpw7M6Cj4gU29ycnkg SSBtaXN0eXBlZCB0aGUgcGF0aC4gVGhlIGRldmljZSBwYXRoIGxpc3RlZCBpbiB0aGUgdmJkIGlz IHdoYXQgeW91IHNob3VsZCBiZSB1c2luZyBrcGFydHggb24KPgo+IGUuZy4KPgo+IGtwYXJ0eCAt YXYgL2Rldi9zbS9iYWNrZW5kLzU1ZWEyMGQyLTg2MTEtMTEyMS05ZTllLWMyNmIzNWFjMTg1Mi81 ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzIKPgo+IFRoaXMgd2lsbCBleHBvc2Ug dGhlIHBhcnRpdGlvbnMgd2hpY2ggeW91IGNhbiBmaW5kIGluIC9kZXYvbWFwcGVyLgpZZXMsIGdv dCBpdC4gVGhhbmsgeW91IGZvciBoZWxwLgoKSSBoYXZlIHVzZWQga3BhcnR4IHdpdGggcmF3IExW TSB2b2x1bWVzIGJlZm9yZS4gV29uZGVyaW5nIHdoYXQncyB3cm9uZyAKd2l0aCAidmhkcGFydHgi LiBJIGhhdmUgZXhwZWN0ZWQgaXQgdG8gZG8gdGhlIHNhbWUuCgpDaGVlcnMuCgotLSAKQWxleGFu ZHJlIEtvdXpuZXRzb3YKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDov L2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Thu Jan 10 01:18:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 01:18:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6n9-0003E8-Vd; Thu, 10 Jan 2013 01:18:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6n8-0003E3-HX for xen-api@lists.xen.org; Thu, 10 Jan 2013 01:18:46 +0000 Received: from [85.158.143.35:11917] by server-3.bemta-4.messagelabs.com id B8/74-19220-5F61EE05; Thu, 10 Jan 2013 01:18:45 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1357780724!10531323!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3736 invoked from network); 10 Jan 2013 01:18:45 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2013 01:18:45 -0000 Received: from [187.233.68.172] (port=55887 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1Tt6n5-0006Tr-OI for xen-api@lists.xen.org; Wed, 09 Jan 2013 19:18:43 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id EBFB7A209 for ; Wed, 9 Jan 2013 19:15:46 -0600 (CST) Message-ID: <50EE16F2.2040603@ondore.com> Date: Wed, 09 Jan 2013 19:18:42 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <56A32708-950E-4E6B-BD05-A76CB660ECB8@aquatic-edge.com> In-Reply-To: <56A32708-950E-4E6B-BD05-A76CB660ECB8@aquatic-edge.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] Storage XenMotion - Just sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. El 09/01/13 16:27, Chris Dutton escribi=F3: > Hello, > > What I am trying to accomplish is keep a vm on one host (a) in sync with > another vm on host (b). They are both using local storage for the SR, > which led me to investigate SXM. But it looks like it does just a little > more then I want. > > From the Storage XenMotion wiki page: > > Each of a VM=92s disks are snapshotted, and from the point of the snapshot > onwards, all of the disk=92s writes are synchronously mirrored to the > destination storage repository. In the background, the snapshotted disk > is copied to the destination location. Once a snapshot has finished > copying, the next disk to be migrated is snapshot/mirrored. > > What I am hoping to do is everything except the last step (the actual > migration). Since you are not actually migrating the VM, maybe the sync is = unnecessary (it might became obsolete in matter of seconds), but a copy = of a snapshot. Maybe this reference would help: http://lists.xen.org/archives/html/xen-api/2013-01/msg00038.html (and the rest of the thread, about vm-migrate behavior) Note that the reference is about offline migration, but the mechanics is = similar. In your case, you would probably want to do a snapshot of the = VDI being used, and copy that snapshot to the other host, then attach it = to the target VM. > The sync does not necessarily have to be synchronous for my situation, > so maybe run a sync as a cron job but when a sync happens I only want > the deltas copied (not a full snapshot). As I understand it, yhe method I suggested will not allow you to update = the copy of the snapshot. Only create a new copy. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 10 01:18:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 01:18:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6n9-0003E8-Vd; Thu, 10 Jan 2013 01:18:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt6n8-0003E3-HX for xen-api@lists.xen.org; Thu, 10 Jan 2013 01:18:46 +0000 Received: from [85.158.143.35:11917] by server-3.bemta-4.messagelabs.com id B8/74-19220-5F61EE05; Thu, 10 Jan 2013 01:18:45 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1357780724!10531323!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3736 invoked from network); 10 Jan 2013 01:18:45 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2013 01:18:45 -0000 Received: from [187.233.68.172] (port=55887 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1Tt6n5-0006Tr-OI for xen-api@lists.xen.org; Wed, 09 Jan 2013 19:18:43 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id EBFB7A209 for ; Wed, 9 Jan 2013 19:15:46 -0600 (CST) Message-ID: <50EE16F2.2040603@ondore.com> Date: Wed, 09 Jan 2013 19:18:42 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <56A32708-950E-4E6B-BD05-A76CB660ECB8@aquatic-edge.com> In-Reply-To: <56A32708-950E-4E6B-BD05-A76CB660ECB8@aquatic-edge.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] Storage XenMotion - Just sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. El 09/01/13 16:27, Chris Dutton escribi=F3: > Hello, > > What I am trying to accomplish is keep a vm on one host (a) in sync with > another vm on host (b). They are both using local storage for the SR, > which led me to investigate SXM. But it looks like it does just a little > more then I want. > > From the Storage XenMotion wiki page: > > Each of a VM=92s disks are snapshotted, and from the point of the snapshot > onwards, all of the disk=92s writes are synchronously mirrored to the > destination storage repository. In the background, the snapshotted disk > is copied to the destination location. Once a snapshot has finished > copying, the next disk to be migrated is snapshot/mirrored. > > What I am hoping to do is everything except the last step (the actual > migration). Since you are not actually migrating the VM, maybe the sync is = unnecessary (it might became obsolete in matter of seconds), but a copy = of a snapshot. Maybe this reference would help: http://lists.xen.org/archives/html/xen-api/2013-01/msg00038.html (and the rest of the thread, about vm-migrate behavior) Note that the reference is about offline migration, but the mechanics is = similar. In your case, you would probably want to do a snapshot of the = VDI being used, and copy that snapshot to the other host, then attach it = to the target VM. > The sync does not necessarily have to be synchronous for my situation, > so maybe run a sync as a cron job but when a sync happens I only want > the deltas copied (not a full snapshot). As I understand it, yhe method I suggested will not allow you to update = the copy of the snapshot. Only create a new copy. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 10 02:12:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 02:12:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt7d6-000490-0R; Thu, 10 Jan 2013 02:12:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt7d4-00048t-H8 for xen-api@lists.xen.org; Thu, 10 Jan 2013 02:12:26 +0000 Received: from [85.158.138.51:33036] by server-6.bemta-3.messagelabs.com id B1/B6-12154-9832EE05; Thu, 10 Jan 2013 02:12:25 +0000 X-Env-Sender: chris@rosepointnav.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1357783943!23999520!1 X-Originating-IP: [198.105.220.93] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13579 invoked from network); 10 Jan 2013 02:12:23 -0000 Received: from 198.105.220.93.static.midphase.com (HELO newmail.rosepointnav.com) (198.105.220.93) by server-6.tower-174.messagelabs.com with SMTP; 10 Jan 2013 02:12:23 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by newmail.rosepointnav.com (Postfix) with ESMTP id 0196B47AFAC for ; Wed, 9 Jan 2013 19:10:56 -0700 (MST) X-Virus-Scanned: amavisd-new at newmail.rosepointnav.com Received: from newmail.rosepointnav.com ([127.0.0.1]) by localhost (newmail.rosepointnav.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id N2fNdXuZZXgK for ; Wed, 9 Jan 2013 19:10:53 -0700 (MST) Received: from [192.168.15.109] (75-151-125-226-Washington.hfc.comcastbusiness.net [75.151.125.226]) by newmail.rosepointnav.com (Postfix) with ESMTPSA id 1270347AD97 for ; Wed, 9 Jan 2013 19:10:52 -0700 (MST) From: Chris Dutton Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Date: Wed, 9 Jan 2013 18:11:12 -0800 References: <56A32708-950E-4E6B-BD05-A76CB660ECB8@aquatic-edge.com> <50EE16F2.2040603@ondore.com> To: "xen-api@lists.xen.org" In-Reply-To: <50EE16F2.2040603@ondore.com> X-Mailer: Apple Mail (2.1499) Subject: Re: [Xen-API] Storage XenMotion - Just sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0843169745229567913==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0843169745229567913== Content-Type: multipart/alternative; boundary="Apple-Mail=_DCEB3597-A919-4EB0-8FF4-B15EC84BAE76" --Apple-Mail=_DCEB3597-A919-4EB0-8FF4-B15EC84BAE76 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 This method will not work=85 I have to sync just the deltas after the = initial sync as our bandwidth can not handle a full snapshot every time = for every machine. Anyone else have an idea? This has to be possible, right? On Jan 9, 2013, at 5:18 PM, Alexandre Kouznetsov wrote: > Hello. >=20 > El 09/01/13 16:27, Chris Dutton escribi=F3: >> Hello, >>=20 >> What I am trying to accomplish is keep a vm on one host (a) in sync = with >> another vm on host (b). They are both using local storage for the SR, >> which led me to investigate SXM. But it looks like it does just a = little >> more then I want. >>=20 >> =46rom the Storage XenMotion wiki page: >>=20 >> Each of a VM=92s disks are snapshotted, and from the point of the = snapshot >> onwards, all of the disk=92s writes are synchronously mirrored to the >> destination storage repository. In the background, the snapshotted = disk >> is copied to the destination location. Once a snapshot has finished >> copying, the next disk to be migrated is snapshot/mirrored. >>=20 >> What I am hoping to do is everything except the last step (the actual >> migration). >=20 > Since you are not actually migrating the VM, maybe the sync is = unnecessary (it might became obsolete in matter of seconds), but a copy = of a snapshot. >=20 > Maybe this reference would help: > http://lists.xen.org/archives/html/xen-api/2013-01/msg00038.html > (and the rest of the thread, about vm-migrate behavior) >=20 > Note that the reference is about offline migration, but the mechanics = is similar. In your case, you would probably want to do a snapshot of = the VDI being used, and copy that snapshot to the other host, then = attach it to the target VM. >=20 >=20 >> The sync does not necessarily have to be synchronous for my = situation, >> so maybe run a sync as a cron job but when a sync happens I only want >> the deltas copied (not a full snapshot). > As I understand it, yhe method I suggested will not allow you to = update the copy of the snapshot. Only create a new copy. >=20 >=20 > --=20 > Alexandre Kouznetsov >=20 >=20 > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --Apple-Mail=_DCEB3597-A919-4EB0-8FF4-B15EC84BAE76 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 This = method will not work=85 I have to sync just the deltas after the initial = sync as our bandwidth can not handle a full snapshot every time for = every machine.

Anyone else have an idea? This has to = be possible, right?


On Jan 9, 2013, at 5:18 PM, = Alexandre Kouznetsov <alk@ondore.com> wrote:

Hello.

El 09/01/13 16:27, Chris Dutton = escribi=F3:
Hello,

What I am trying = to accomplish is keep a vm on one host (a) in sync with
another vm on = host (b). They are both using local storage for the SR,
which led me = to investigate SXM. But it looks like it does just a little
more then = I want.

=46rom the Storage XenMotion wiki page:

Each of a = VM=92s disks are snapshotted, and from the point of the = snapshot
onwards, all of the disk=92s writes are synchronously = mirrored to the
destination storage repository. In the background, = the snapshotted disk
is copied to the destination location. Once a = snapshot has finished
copying, the next disk to be migrated is = snapshot/mirrored.

What I am hoping to do is everything except = the last step (the actual
migration).

Since you = are not actually migrating the VM, maybe the sync is unnecessary (it = might became obsolete in matter of seconds), but a copy of a = snapshot.

Maybe this reference would help:
= http://lists.xen.org/archives/html/xen-api/2013-01/msg00038.html
(a= nd the rest of the thread, about vm-migrate behavior)

Note that = the reference is about offline migration, but the mechanics is similar. = In your case, you would probably want to do a snapshot of the VDI being = used, and copy that snapshot to the other host, then attach it to the = target VM.


The sync does not = necessarily have to be synchronous for my situation,
so maybe run a = sync as a cron job but when a sync happens I only want
the deltas = copied (not a full snapshot).
As I understand it, yhe = method I suggested will not allow you to update the copy of the = snapshot. Only create a new copy.


--
Alexandre = Kouznetsov


_______________________________________________
X= en-api mailing = list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/list= info/xen-api

= --Apple-Mail=_DCEB3597-A919-4EB0-8FF4-B15EC84BAE76-- --===============0843169745229567913== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0843169745229567913==-- From xen-api-bounces@lists.xen.org Thu Jan 10 02:12:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 02:12:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt7d6-000490-0R; Thu, 10 Jan 2013 02:12:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tt7d4-00048t-H8 for xen-api@lists.xen.org; Thu, 10 Jan 2013 02:12:26 +0000 Received: from [85.158.138.51:33036] by server-6.bemta-3.messagelabs.com id B1/B6-12154-9832EE05; Thu, 10 Jan 2013 02:12:25 +0000 X-Env-Sender: chris@rosepointnav.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1357783943!23999520!1 X-Originating-IP: [198.105.220.93] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13579 invoked from network); 10 Jan 2013 02:12:23 -0000 Received: from 198.105.220.93.static.midphase.com (HELO newmail.rosepointnav.com) (198.105.220.93) by server-6.tower-174.messagelabs.com with SMTP; 10 Jan 2013 02:12:23 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by newmail.rosepointnav.com (Postfix) with ESMTP id 0196B47AFAC for ; Wed, 9 Jan 2013 19:10:56 -0700 (MST) X-Virus-Scanned: amavisd-new at newmail.rosepointnav.com Received: from newmail.rosepointnav.com ([127.0.0.1]) by localhost (newmail.rosepointnav.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id N2fNdXuZZXgK for ; Wed, 9 Jan 2013 19:10:53 -0700 (MST) Received: from [192.168.15.109] (75-151-125-226-Washington.hfc.comcastbusiness.net [75.151.125.226]) by newmail.rosepointnav.com (Postfix) with ESMTPSA id 1270347AD97 for ; Wed, 9 Jan 2013 19:10:52 -0700 (MST) From: Chris Dutton Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Date: Wed, 9 Jan 2013 18:11:12 -0800 References: <56A32708-950E-4E6B-BD05-A76CB660ECB8@aquatic-edge.com> <50EE16F2.2040603@ondore.com> To: "xen-api@lists.xen.org" In-Reply-To: <50EE16F2.2040603@ondore.com> X-Mailer: Apple Mail (2.1499) Subject: Re: [Xen-API] Storage XenMotion - Just sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0843169745229567913==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0843169745229567913== Content-Type: multipart/alternative; boundary="Apple-Mail=_DCEB3597-A919-4EB0-8FF4-B15EC84BAE76" --Apple-Mail=_DCEB3597-A919-4EB0-8FF4-B15EC84BAE76 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 This method will not work=85 I have to sync just the deltas after the = initial sync as our bandwidth can not handle a full snapshot every time = for every machine. Anyone else have an idea? This has to be possible, right? On Jan 9, 2013, at 5:18 PM, Alexandre Kouznetsov wrote: > Hello. >=20 > El 09/01/13 16:27, Chris Dutton escribi=F3: >> Hello, >>=20 >> What I am trying to accomplish is keep a vm on one host (a) in sync = with >> another vm on host (b). They are both using local storage for the SR, >> which led me to investigate SXM. But it looks like it does just a = little >> more then I want. >>=20 >> =46rom the Storage XenMotion wiki page: >>=20 >> Each of a VM=92s disks are snapshotted, and from the point of the = snapshot >> onwards, all of the disk=92s writes are synchronously mirrored to the >> destination storage repository. In the background, the snapshotted = disk >> is copied to the destination location. Once a snapshot has finished >> copying, the next disk to be migrated is snapshot/mirrored. >>=20 >> What I am hoping to do is everything except the last step (the actual >> migration). >=20 > Since you are not actually migrating the VM, maybe the sync is = unnecessary (it might became obsolete in matter of seconds), but a copy = of a snapshot. >=20 > Maybe this reference would help: > http://lists.xen.org/archives/html/xen-api/2013-01/msg00038.html > (and the rest of the thread, about vm-migrate behavior) >=20 > Note that the reference is about offline migration, but the mechanics = is similar. In your case, you would probably want to do a snapshot of = the VDI being used, and copy that snapshot to the other host, then = attach it to the target VM. >=20 >=20 >> The sync does not necessarily have to be synchronous for my = situation, >> so maybe run a sync as a cron job but when a sync happens I only want >> the deltas copied (not a full snapshot). > As I understand it, yhe method I suggested will not allow you to = update the copy of the snapshot. Only create a new copy. >=20 >=20 > --=20 > Alexandre Kouznetsov >=20 >=20 > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --Apple-Mail=_DCEB3597-A919-4EB0-8FF4-B15EC84BAE76 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 This = method will not work=85 I have to sync just the deltas after the initial = sync as our bandwidth can not handle a full snapshot every time for = every machine.

Anyone else have an idea? This has to = be possible, right?


On Jan 9, 2013, at 5:18 PM, = Alexandre Kouznetsov <alk@ondore.com> wrote:

Hello.

El 09/01/13 16:27, Chris Dutton = escribi=F3:
Hello,

What I am trying = to accomplish is keep a vm on one host (a) in sync with
another vm on = host (b). They are both using local storage for the SR,
which led me = to investigate SXM. But it looks like it does just a little
more then = I want.

=46rom the Storage XenMotion wiki page:

Each of a = VM=92s disks are snapshotted, and from the point of the = snapshot
onwards, all of the disk=92s writes are synchronously = mirrored to the
destination storage repository. In the background, = the snapshotted disk
is copied to the destination location. Once a = snapshot has finished
copying, the next disk to be migrated is = snapshot/mirrored.

What I am hoping to do is everything except = the last step (the actual
migration).

Since you = are not actually migrating the VM, maybe the sync is unnecessary (it = might became obsolete in matter of seconds), but a copy of a = snapshot.

Maybe this reference would help:
= http://lists.xen.org/archives/html/xen-api/2013-01/msg00038.html
(a= nd the rest of the thread, about vm-migrate behavior)

Note that = the reference is about offline migration, but the mechanics is similar. = In your case, you would probably want to do a snapshot of the VDI being = used, and copy that snapshot to the other host, then attach it to the = target VM.


The sync does not = necessarily have to be synchronous for my situation,
so maybe run a = sync as a cron job but when a sync happens I only want
the deltas = copied (not a full snapshot).
As I understand it, yhe = method I suggested will not allow you to update the copy of the = snapshot. Only create a new copy.


--
Alexandre = Kouznetsov


_______________________________________________
X= en-api mailing = list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/list= info/xen-api

= --Apple-Mail=_DCEB3597-A919-4EB0-8FF4-B15EC84BAE76-- --===============0843169745229567913== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0843169745229567913==-- From xen-api-bounces@lists.xen.org Thu Jan 10 10:04:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 10:04:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtF00-0002K8-Qm; Thu, 10 Jan 2013 10:04:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtEzz-0002K0-Ct; Thu, 10 Jan 2013 10:04:35 +0000 Received: from [85.158.143.35:29482] by server-3.bemta-4.messagelabs.com id 12/AC-19220-2329EE05; Thu, 10 Jan 2013 10:04:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1357812260!11649663!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1NDcy\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5392 invoked from network); 10 Jan 2013 10:04:21 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 10:04:21 -0000 X-IronPort-AV: E=Sophos;i="4.84,443,1355097600"; d="scan'208";a="569611" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Jan 2013 10:04:20 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Thu, 10 Jan 2013 10:04:20 +0000 Message-ID: <1357812259.7989.317.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Rushikesh Jadhav <2rushikeshj@gmail.com> Date: Thu, 10 Jan 2013 10:04:19 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Tue, 2013-01-08 at 21:53 +0000, Rushikesh Jadhav wrote: > > > Please help me in diagnosing below error in /var/log/messages > > HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) > for RM: fffff8800d099000 This message was printed by your dom1 kernel, via the PV drivers. Google suggests to me that txftrans.c is a Windows Vista source file, but I don't especially want to follow that trail to far for fear of seeing something I shouldn't. I've no idea what the message might mean though. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 10 10:04:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 10:04:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtF00-0002K8-Qm; Thu, 10 Jan 2013 10:04:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtEzz-0002K0-Ct; Thu, 10 Jan 2013 10:04:35 +0000 Received: from [85.158.143.35:29482] by server-3.bemta-4.messagelabs.com id 12/AC-19220-2329EE05; Thu, 10 Jan 2013 10:04:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1357812260!11649663!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1NDcy\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5392 invoked from network); 10 Jan 2013 10:04:21 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 10:04:21 -0000 X-IronPort-AV: E=Sophos;i="4.84,443,1355097600"; d="scan'208";a="569611" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Jan 2013 10:04:20 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Thu, 10 Jan 2013 10:04:20 +0000 Message-ID: <1357812259.7989.317.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Rushikesh Jadhav <2rushikeshj@gmail.com> Date: Thu, 10 Jan 2013 10:04:19 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Tue, 2013-01-08 at 21:53 +0000, Rushikesh Jadhav wrote: > > > Please help me in diagnosing below error in /var/log/messages > > HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) > for RM: fffff8800d099000 This message was printed by your dom1 kernel, via the PV drivers. Google suggests to me that txftrans.c is a Windows Vista source file, but I don't especially want to follow that trail to far for fear of seeing something I shouldn't. I've no idea what the message might mean though. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 10 10:50:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 10:50:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtFi8-0004YC-FH; Thu, 10 Jan 2013 10:50:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtFi6-0004Y7-OB for xen-api@lists.xen.org; Thu, 10 Jan 2013 10:50:10 +0000 Received: from [85.158.138.51:60371] by server-15.bemta-3.messagelabs.com id 77/B8-07921-DDC9EE05; Thu, 10 Jan 2013 10:50:05 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1357815004!27381311!1 X-Originating-IP: [207.126.144.119] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7250 invoked from network); 10 Jan 2013 10:50:04 -0000 Received: from eu1sys200aog105.obsmtp.com (HELO eu1sys200aog105.obsmtp.com) (207.126.144.119) by server-11.tower-174.messagelabs.com with SMTP; 10 Jan 2013 10:50:04 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob105.postini.com ([207.126.147.11]) with SMTP ID DSNKUO6c0iFc+x4i4KjzyGT9yOlYhHc5Lih3@postini.com; Thu, 10 Jan 2013 10:50:04 UTC Received: from lonwexhtca01.uk.futurenet.com (lonwexhtca01.uk.futurenet.com [172.23.130.5]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id C75707F449D for ; Thu, 10 Jan 2013 10:49:54 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by lonwexhtca01.uk.futurenet.com ([172.23.130.5]) with mapi; Thu, 10 Jan 2013 10:49:54 +0000 From: Dave Avent To: "xen-api@lists.xen.org" Date: Thu, 10 Jan 2013 10:49:53 +0000 Thread-Topic: VM Migration Bug? Thread-Index: Ac3vIDklB4gATwruRly5b8FTcqrcIw== Message-ID: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I am having issues with migrating VMs between hosts. Here is how I can reproduce the problem: 1) Create 2 new VM's (using either a fresh install from Net Install of Debian or from a "Golden Image" of a VM previously converted to a Template) 2) Migrate one of the VMs to another hosts 3) Attempt to migrate the same VM back to the original host however it refuses and throws: Cannot restore this VM because it would create a duplicate vm: OpaqueRef:711f22f3-9e35-b13e-1c35-58e8a578ca0e What exactly does it think is being duplicated? None of the original assets appear to have been left behind (failed to be deleted etc). I can't see why this is failing. Any ideas? Dave-- Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 10 10:50:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 10:50:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtFi8-0004YC-FH; Thu, 10 Jan 2013 10:50:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtFi6-0004Y7-OB for xen-api@lists.xen.org; Thu, 10 Jan 2013 10:50:10 +0000 Received: from [85.158.138.51:60371] by server-15.bemta-3.messagelabs.com id 77/B8-07921-DDC9EE05; Thu, 10 Jan 2013 10:50:05 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1357815004!27381311!1 X-Originating-IP: [207.126.144.119] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7250 invoked from network); 10 Jan 2013 10:50:04 -0000 Received: from eu1sys200aog105.obsmtp.com (HELO eu1sys200aog105.obsmtp.com) (207.126.144.119) by server-11.tower-174.messagelabs.com with SMTP; 10 Jan 2013 10:50:04 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob105.postini.com ([207.126.147.11]) with SMTP ID DSNKUO6c0iFc+x4i4KjzyGT9yOlYhHc5Lih3@postini.com; Thu, 10 Jan 2013 10:50:04 UTC Received: from lonwexhtca01.uk.futurenet.com (lonwexhtca01.uk.futurenet.com [172.23.130.5]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id C75707F449D for ; Thu, 10 Jan 2013 10:49:54 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by lonwexhtca01.uk.futurenet.com ([172.23.130.5]) with mapi; Thu, 10 Jan 2013 10:49:54 +0000 From: Dave Avent To: "xen-api@lists.xen.org" Date: Thu, 10 Jan 2013 10:49:53 +0000 Thread-Topic: VM Migration Bug? Thread-Index: Ac3vIDklB4gATwruRly5b8FTcqrcIw== Message-ID: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I am having issues with migrating VMs between hosts. Here is how I can reproduce the problem: 1) Create 2 new VM's (using either a fresh install from Net Install of Debian or from a "Golden Image" of a VM previously converted to a Template) 2) Migrate one of the VMs to another hosts 3) Attempt to migrate the same VM back to the original host however it refuses and throws: Cannot restore this VM because it would create a duplicate vm: OpaqueRef:711f22f3-9e35-b13e-1c35-58e8a578ca0e What exactly does it think is being duplicated? None of the original assets appear to have been left behind (failed to be deleted etc). I can't see why this is failing. Any ideas? Dave-- Future Publishing Limited (registered company number 2008885) is a wholly owned subsidiary of Future plc (registered company number 3757874), both of which are incorporated in England and Wales and share the same registered address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring. ***** Save resources: think before you print. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 10 14:27:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 14:27:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtJ6W-00010T-Tp; Thu, 10 Jan 2013 14:27:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtJ6V-00010M-1a for xen-api@lists.xen.org; Thu, 10 Jan 2013 14:27:35 +0000 Received: from [85.158.137.99:59728] by server-10.bemta-3.messagelabs.com id 9A/E6-28305-6DFCEE05; Thu, 10 Jan 2013 14:27:34 +0000 X-Env-Sender: rlljorge@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1357828050!17345850!1 X-Originating-IP: [209.85.160.54] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8641 invoked from network); 10 Jan 2013 14:27:32 -0000 Received: from mail-pb0-f54.google.com (HELO mail-pb0-f54.google.com) (209.85.160.54) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 14:27:32 -0000 Received: by mail-pb0-f54.google.com with SMTP id wz12so328047pbc.27 for ; Thu, 10 Jan 2013 06:27:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=K7SS7BzHYJtJYr2sq1o/u2JmPGUlKqXaFm3lm5FB1eE=; b=WqG9hOvRjUmxxeVQ6m4B02rD72WFnQvu+DlBSD6s9GmNjINQ+SAiv1U1H1F4Spv0YL dVdO7bcTjACVA2cYj+Z17DoJwk/oi/qdaIbK/yRytuhyGHyCPoKJWnYiiYZqcSnApSDX LV3sazQ4lxlx7fmU+0O8sHLVHaFvJ1G2lFBNbKc5BUUsBv/G9zWEXFDlW7J+gIQFlpNa y4k/e59NNhEy+ggHcc8xXJqNndgEORgH5tF3ugQN+Smp5HXQ0uZZT/WJ12B+Tk2QqYkm 70rXBDVrfiyakTYwCDhnsyB4WC7aFADkBdINkl71WNB6P4bgB4blPRMqvu4AaSDvp4yo zL3Q== MIME-Version: 1.0 Received: by 10.68.213.233 with SMTP id nv9mr218541550pbc.155.1357828050074; Thu, 10 Jan 2013 06:27:30 -0800 (PST) Received: by 10.68.243.66 with HTTP; Thu, 10 Jan 2013 06:27:29 -0800 (PST) Date: Thu, 10 Jan 2013 12:27:29 -0200 Message-ID: From: Rodrigo Jorge To: xen-api@lists.xen.org Subject: [Xen-API] XCP 1.6 on Intel MFSYS25 NIC's detect problem X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4869855002784667606==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4869855002784667606== Content-Type: multipart/alternative; boundary=e89a8ff1c6c8973d0b04d2effac8 --e89a8ff1c6c8973d0b04d2effac8 Content-Type: text/plain; charset=ISO-8859-1 Hello, I trying to install the XCP 1.6 ISO Image on hardware Intel Modular Server MFSYS25v1. The server has 4 NIC's during installation, but are not detected. In this same hardware mode l have installed a xenserver 5.6 and the nic's are detected correctly, see below: [root @ vms01 ~] # lspci | grep Ethe 05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01) 05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01) 08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) [Root @ vms01 ~] # [root @ vms01 ~] # cat / etc / modprobe.conf alias eth0 e1000e alias eth2 e1000e alias eth1 e1000e alias eth3 e1000e [Root @ vms01 ~] # [root @ vms01 ~] # modinfo e1000e filename: / lib/modules/2.6.32.12-0.7.1.xs5.6.100.327.170613xen/kernel/drivers/net/e1000e/e1000e.ko version: 1.2.8-NAPI license: GPL description: Intel (R) PRO/1000 Network Driver author: Intel Corporation, [root @ vms01 ~] # ethtool eth0, ethtool eth1; ethtool eth2; ethtool eth3 Settings for eth0: Supported ports: [FIBRE] Supported link modes: 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb / s Duplex: Full Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: yes Settings for eth1: Supported ports: [FIBRE] Supported link modes: 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb / s Duplex: Full Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: yes Settings for eth2: Supported ports: [FIBRE] Supported link modes: 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb / s Duplex: Full Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: yes Settings for eth3: Supported ports: [FIBRE] Supported link modes: 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb / s Duplex: Full Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x00000001 (1) Link detected: yes [root @ vms01 ~] # Any tips? Thank you --e89a8ff1c6c8973d0b04d2effac8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

I trying to ins= tall the XCP 1.6 ISO Image on hardware Intel Modular Server MFSYS25v1.
The server has 4 NIC's during installation, but are not detected.=
In this same hardware mode l have installed a xenserver 5.6 and the ni= c's are detected correctly, see below:

[root @= vms01 ~] # lspci | grep Ethe
05:00.0 Ethernet controller: Intel = Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01)
05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Eth= ernet Controller (Serdes) (rev 01)
08:00.0 Ethernet controller: I= ntel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Con= troller (rev 06)
[Root @ vms01 ~] #

[roo= t @ vms01 ~] # cat / etc / modprobe.conf
alias eth0 e1000e
alias eth2 e1000e
alias eth1 e1000e
alias eth3 e10= 00e
[Root @ vms01 ~] #

[root @ vms01 ~] = # modinfo e1000e
filename: / lib/modules/2.6.32.12-0.7.1.xs5.6.10= 0.327.170613xen/kernel/drivers/net/e1000e/e1000e.ko
version: 1.2.8-NAPI
license: GPL
description: Inte= l (R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>


[root @ vms01 ~] # ethtool eth0, ethtool eth1= ; ethtool eth2; ethtool eth3
Settings for eth0:
=A0 =A0= =A0 =A0 Supported ports: [FIBRE]
=A0 =A0 =A0 =A0 Supported link = modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Supports auto-negotiation: Yes
=A0 =A0 =A0 = =A0 Advertised link modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Adverti= sed auto-negotiation: Yes
=A0 =A0 =A0 =A0 Speed: 1000Mb / s
=
=A0 =A0 =A0 =A0 Duplex: Full
=A0 =A0 =A0 =A0 Port: FIBRE
=A0 =A0 =A0 =A0 PHYAD: 0
=A0 =A0 =A0 =A0 Transceiver: external
=A0 =A0 =A0 =A0 Auto-neg= otiation: on
=A0 =A0 =A0 =A0 Supports Wake-on: pumbag
= =A0 =A0 =A0 =A0 Wake-on: g
=A0 =A0 =A0 =A0 Current message level:= 0x00000001 (1)
=A0 =A0 =A0 =A0 Link detected: yes
Settings for eth1:
<= div>=A0 =A0 =A0 =A0 Supported ports: [FIBRE]
=A0 =A0 =A0 =A0 Supp= orted link modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Supports auto-ne= gotiation: Yes
=A0 =A0 =A0 =A0 Advertised link modes: 1000baseT/F= ull
=A0 =A0 =A0 =A0 Advertised auto-negotiation: Yes
=A0 =A0 =A0= =A0 Speed: 1000Mb / s
=A0 =A0 =A0 =A0 Duplex: Full
=A0= =A0 =A0 =A0 Port: FIBRE
=A0 =A0 =A0 =A0 PHYAD: 0
=A0 = =A0 =A0 =A0 Transceiver: external
=A0 =A0 =A0 =A0 Auto-negotiatio= n: on
=A0 =A0 =A0 =A0 Supports Wake-on: pumbag
=A0 =A0 =A0 =A0 Wak= e-on: g
=A0 =A0 =A0 =A0 Current message level: 0x00000001 (1)
=A0 =A0 =A0 =A0 Link detected: yes
Settings for eth2:
=A0 =A0 =A0 =A0 Supported ports: [FIBRE]
=A0 =A0 =A0 =A0 Supported link modes: 1000baseT/Full
=A0 =A0= =A0 =A0 Supports auto-negotiation: Yes
=A0 =A0 =A0 =A0 Advertise= d link modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Advertised auto-nego= tiation: Yes
=A0 =A0 =A0 =A0 Speed: 1000Mb / s
=A0 =A0 =A0 =A0 Duplex: Full
=A0 =A0 =A0 =A0 Port: FIBRE
=A0 =A0 =A0 =A0 PHYAD: 0
=A0 =A0 =A0 =A0 Transceiver: exte= rnal
=A0 =A0 =A0 =A0 Auto-negotiation: on
=A0 =A0 =A0 = =A0 Supports Wake-on: pumbag
=A0 =A0 =A0 =A0 Wake-on: g
=A0 =A0 =A0 =A0 Current message level: 0x00000001 (1)
=A0 = =A0 =A0 =A0 Link detected: yes
Settings for eth3:
=A0 = =A0 =A0 =A0 Supported ports: [FIBRE]
=A0 =A0 =A0 =A0 Supported li= nk modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Supports auto-negotiation: Yes
=A0 =A0 =A0 =A0 Ad= vertised link modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Advertised au= to-negotiation: Yes
=A0 =A0 =A0 =A0 Speed: 1000Mb / s
= =A0 =A0 =A0 =A0 Duplex: Full
=A0 =A0 =A0 =A0 Port: FIBRE
=A0 =A0 =A0 =A0 PHYAD: 0
= =A0 =A0 =A0 =A0 Transceiver: external
=A0 =A0 =A0 =A0 Auto-negoti= ation: on
=A0 =A0 =A0 =A0 Supports Wake-on: d
=A0 =A0 = =A0 =A0 Wake-on: d
=A0 =A0 =A0 =A0 Current message level: 0x00000= 001 (1)
=A0 =A0 =A0 =A0 Link detected: yes
[root @ vms01 ~] #
<= div>
Any tips?
Thank you
--e89a8ff1c6c8973d0b04d2effac8-- --===============4869855002784667606== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4869855002784667606==-- From xen-api-bounces@lists.xen.org Thu Jan 10 14:27:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 14:27:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtJ6W-00010T-Tp; Thu, 10 Jan 2013 14:27:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtJ6V-00010M-1a for xen-api@lists.xen.org; Thu, 10 Jan 2013 14:27:35 +0000 Received: from [85.158.137.99:59728] by server-10.bemta-3.messagelabs.com id 9A/E6-28305-6DFCEE05; Thu, 10 Jan 2013 14:27:34 +0000 X-Env-Sender: rlljorge@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1357828050!17345850!1 X-Originating-IP: [209.85.160.54] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8641 invoked from network); 10 Jan 2013 14:27:32 -0000 Received: from mail-pb0-f54.google.com (HELO mail-pb0-f54.google.com) (209.85.160.54) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 14:27:32 -0000 Received: by mail-pb0-f54.google.com with SMTP id wz12so328047pbc.27 for ; Thu, 10 Jan 2013 06:27:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=K7SS7BzHYJtJYr2sq1o/u2JmPGUlKqXaFm3lm5FB1eE=; b=WqG9hOvRjUmxxeVQ6m4B02rD72WFnQvu+DlBSD6s9GmNjINQ+SAiv1U1H1F4Spv0YL dVdO7bcTjACVA2cYj+Z17DoJwk/oi/qdaIbK/yRytuhyGHyCPoKJWnYiiYZqcSnApSDX LV3sazQ4lxlx7fmU+0O8sHLVHaFvJ1G2lFBNbKc5BUUsBv/G9zWEXFDlW7J+gIQFlpNa y4k/e59NNhEy+ggHcc8xXJqNndgEORgH5tF3ugQN+Smp5HXQ0uZZT/WJ12B+Tk2QqYkm 70rXBDVrfiyakTYwCDhnsyB4WC7aFADkBdINkl71WNB6P4bgB4blPRMqvu4AaSDvp4yo zL3Q== MIME-Version: 1.0 Received: by 10.68.213.233 with SMTP id nv9mr218541550pbc.155.1357828050074; Thu, 10 Jan 2013 06:27:30 -0800 (PST) Received: by 10.68.243.66 with HTTP; Thu, 10 Jan 2013 06:27:29 -0800 (PST) Date: Thu, 10 Jan 2013 12:27:29 -0200 Message-ID: From: Rodrigo Jorge To: xen-api@lists.xen.org Subject: [Xen-API] XCP 1.6 on Intel MFSYS25 NIC's detect problem X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4869855002784667606==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4869855002784667606== Content-Type: multipart/alternative; boundary=e89a8ff1c6c8973d0b04d2effac8 --e89a8ff1c6c8973d0b04d2effac8 Content-Type: text/plain; charset=ISO-8859-1 Hello, I trying to install the XCP 1.6 ISO Image on hardware Intel Modular Server MFSYS25v1. The server has 4 NIC's during installation, but are not detected. In this same hardware mode l have installed a xenserver 5.6 and the nic's are detected correctly, see below: [root @ vms01 ~] # lspci | grep Ethe 05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01) 05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01) 08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) [Root @ vms01 ~] # [root @ vms01 ~] # cat / etc / modprobe.conf alias eth0 e1000e alias eth2 e1000e alias eth1 e1000e alias eth3 e1000e [Root @ vms01 ~] # [root @ vms01 ~] # modinfo e1000e filename: / lib/modules/2.6.32.12-0.7.1.xs5.6.100.327.170613xen/kernel/drivers/net/e1000e/e1000e.ko version: 1.2.8-NAPI license: GPL description: Intel (R) PRO/1000 Network Driver author: Intel Corporation, [root @ vms01 ~] # ethtool eth0, ethtool eth1; ethtool eth2; ethtool eth3 Settings for eth0: Supported ports: [FIBRE] Supported link modes: 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb / s Duplex: Full Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: yes Settings for eth1: Supported ports: [FIBRE] Supported link modes: 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb / s Duplex: Full Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: yes Settings for eth2: Supported ports: [FIBRE] Supported link modes: 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb / s Duplex: Full Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: yes Settings for eth3: Supported ports: [FIBRE] Supported link modes: 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb / s Duplex: Full Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x00000001 (1) Link detected: yes [root @ vms01 ~] # Any tips? Thank you --e89a8ff1c6c8973d0b04d2effac8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

I trying to ins= tall the XCP 1.6 ISO Image on hardware Intel Modular Server MFSYS25v1.
The server has 4 NIC's during installation, but are not detected.=
In this same hardware mode l have installed a xenserver 5.6 and the ni= c's are detected correctly, see below:

[root @= vms01 ~] # lspci | grep Ethe
05:00.0 Ethernet controller: Intel = Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01)
05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Eth= ernet Controller (Serdes) (rev 01)
08:00.0 Ethernet controller: I= ntel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Con= troller (rev 06)
[Root @ vms01 ~] #

[roo= t @ vms01 ~] # cat / etc / modprobe.conf
alias eth0 e1000e
alias eth2 e1000e
alias eth1 e1000e
alias eth3 e10= 00e
[Root @ vms01 ~] #

[root @ vms01 ~] = # modinfo e1000e
filename: / lib/modules/2.6.32.12-0.7.1.xs5.6.10= 0.327.170613xen/kernel/drivers/net/e1000e/e1000e.ko
version: 1.2.8-NAPI
license: GPL
description: Inte= l (R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>


[root @ vms01 ~] # ethtool eth0, ethtool eth1= ; ethtool eth2; ethtool eth3
Settings for eth0:
=A0 =A0= =A0 =A0 Supported ports: [FIBRE]
=A0 =A0 =A0 =A0 Supported link = modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Supports auto-negotiation: Yes
=A0 =A0 =A0 = =A0 Advertised link modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Adverti= sed auto-negotiation: Yes
=A0 =A0 =A0 =A0 Speed: 1000Mb / s
=
=A0 =A0 =A0 =A0 Duplex: Full
=A0 =A0 =A0 =A0 Port: FIBRE
=A0 =A0 =A0 =A0 PHYAD: 0
=A0 =A0 =A0 =A0 Transceiver: external
=A0 =A0 =A0 =A0 Auto-neg= otiation: on
=A0 =A0 =A0 =A0 Supports Wake-on: pumbag
= =A0 =A0 =A0 =A0 Wake-on: g
=A0 =A0 =A0 =A0 Current message level:= 0x00000001 (1)
=A0 =A0 =A0 =A0 Link detected: yes
Settings for eth1:
<= div>=A0 =A0 =A0 =A0 Supported ports: [FIBRE]
=A0 =A0 =A0 =A0 Supp= orted link modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Supports auto-ne= gotiation: Yes
=A0 =A0 =A0 =A0 Advertised link modes: 1000baseT/F= ull
=A0 =A0 =A0 =A0 Advertised auto-negotiation: Yes
=A0 =A0 =A0= =A0 Speed: 1000Mb / s
=A0 =A0 =A0 =A0 Duplex: Full
=A0= =A0 =A0 =A0 Port: FIBRE
=A0 =A0 =A0 =A0 PHYAD: 0
=A0 = =A0 =A0 =A0 Transceiver: external
=A0 =A0 =A0 =A0 Auto-negotiatio= n: on
=A0 =A0 =A0 =A0 Supports Wake-on: pumbag
=A0 =A0 =A0 =A0 Wak= e-on: g
=A0 =A0 =A0 =A0 Current message level: 0x00000001 (1)
=A0 =A0 =A0 =A0 Link detected: yes
Settings for eth2:
=A0 =A0 =A0 =A0 Supported ports: [FIBRE]
=A0 =A0 =A0 =A0 Supported link modes: 1000baseT/Full
=A0 =A0= =A0 =A0 Supports auto-negotiation: Yes
=A0 =A0 =A0 =A0 Advertise= d link modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Advertised auto-nego= tiation: Yes
=A0 =A0 =A0 =A0 Speed: 1000Mb / s
=A0 =A0 =A0 =A0 Duplex: Full
=A0 =A0 =A0 =A0 Port: FIBRE
=A0 =A0 =A0 =A0 PHYAD: 0
=A0 =A0 =A0 =A0 Transceiver: exte= rnal
=A0 =A0 =A0 =A0 Auto-negotiation: on
=A0 =A0 =A0 = =A0 Supports Wake-on: pumbag
=A0 =A0 =A0 =A0 Wake-on: g
=A0 =A0 =A0 =A0 Current message level: 0x00000001 (1)
=A0 = =A0 =A0 =A0 Link detected: yes
Settings for eth3:
=A0 = =A0 =A0 =A0 Supported ports: [FIBRE]
=A0 =A0 =A0 =A0 Supported li= nk modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Supports auto-negotiation: Yes
=A0 =A0 =A0 =A0 Ad= vertised link modes: 1000baseT/Full
=A0 =A0 =A0 =A0 Advertised au= to-negotiation: Yes
=A0 =A0 =A0 =A0 Speed: 1000Mb / s
= =A0 =A0 =A0 =A0 Duplex: Full
=A0 =A0 =A0 =A0 Port: FIBRE
=A0 =A0 =A0 =A0 PHYAD: 0
= =A0 =A0 =A0 =A0 Transceiver: external
=A0 =A0 =A0 =A0 Auto-negoti= ation: on
=A0 =A0 =A0 =A0 Supports Wake-on: d
=A0 =A0 = =A0 =A0 Wake-on: d
=A0 =A0 =A0 =A0 Current message level: 0x00000= 001 (1)
=A0 =A0 =A0 =A0 Link detected: yes
[root @ vms01 ~] #
<= div>
Any tips?
Thank you
--e89a8ff1c6c8973d0b04d2effac8-- --===============4869855002784667606== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4869855002784667606==-- From xen-api-bounces@lists.xen.org Thu Jan 10 14:36:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 14:36:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtJEo-0001aq-Sp; Thu, 10 Jan 2013 14:36:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtJEn-0001ad-9h for xen-api@lists.xen.org; Thu, 10 Jan 2013 14:36:09 +0000 Received: from [85.158.138.51:44922] by server-8.bemta-3.messagelabs.com id 6B/DC-01233-8D1DEE05; Thu, 10 Jan 2013 14:36:08 +0000 X-Env-Sender: mikael@servercentralen.se X-Msg-Ref: server-9.tower-174.messagelabs.com!1357828567!27471581!1 X-Originating-IP: [188.95.35.85] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19610 invoked from network); 10 Jan 2013 14:36:07 -0000 Received: from solna-gw2.centralcloud.net (HELO smtpedge.centralcloud.net) (188.95.35.85) by server-9.tower-174.messagelabs.com with AES128-SHA encrypted SMTP; 10 Jan 2013 14:36:07 -0000 Received: from SOLNA-MBX01.nschmc.local ([fe80::2498:f5a:2882:1d75]) by SOLNA-HUB01.nschmc.local ([fe80::d1e0:f192:d7:464a%11]) with mapi id 14.02.0318.004; Thu, 10 Jan 2013 15:38:59 +0100 From: Mikael Hugo To: Rodrigo Jorge , "xen-api@lists.xen.org" Thread-Topic: [Xen-API] XCP 1.6 on Intel MFSYS25 NIC's detect problem Thread-Index: AQHN7z9fAS1G4TfIj068dd7ofw/sx5hCoHgw Date: Thu, 10 Jan 2013 14:38:59 +0000 Message-ID: <23A9CFB8DDE7F34089CC14B4B86FDA58498EC729@SOLNA-MBX01.nschmc.local> References: In-Reply-To: Accept-Language: sv-SE, en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.68.3] MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 on Intel MFSYS25 NIC's detect problem X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, >I trying to install the XCP 1.6 ISO Image on hardware Intel Modular Server MFSYS25v1. >The server has 4 NIC's during installation, but are not detected. >In this same hardware mode l have installed a xenserver 5.6 and the nic's are detected correctly, see below: I had similar issues with Intel cards, but in my case the cards are detected but VLANs are not working. For Xenserver 6.1 there is an updated Intel driver pack that can be manually installed. It dident help me, but it might help you. http://support.citrix.com/article/CTX135324 Best regards Mikael _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 10 14:36:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 14:36:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtJEo-0001aq-Sp; Thu, 10 Jan 2013 14:36:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtJEn-0001ad-9h for xen-api@lists.xen.org; Thu, 10 Jan 2013 14:36:09 +0000 Received: from [85.158.138.51:44922] by server-8.bemta-3.messagelabs.com id 6B/DC-01233-8D1DEE05; Thu, 10 Jan 2013 14:36:08 +0000 X-Env-Sender: mikael@servercentralen.se X-Msg-Ref: server-9.tower-174.messagelabs.com!1357828567!27471581!1 X-Originating-IP: [188.95.35.85] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19610 invoked from network); 10 Jan 2013 14:36:07 -0000 Received: from solna-gw2.centralcloud.net (HELO smtpedge.centralcloud.net) (188.95.35.85) by server-9.tower-174.messagelabs.com with AES128-SHA encrypted SMTP; 10 Jan 2013 14:36:07 -0000 Received: from SOLNA-MBX01.nschmc.local ([fe80::2498:f5a:2882:1d75]) by SOLNA-HUB01.nschmc.local ([fe80::d1e0:f192:d7:464a%11]) with mapi id 14.02.0318.004; Thu, 10 Jan 2013 15:38:59 +0100 From: Mikael Hugo To: Rodrigo Jorge , "xen-api@lists.xen.org" Thread-Topic: [Xen-API] XCP 1.6 on Intel MFSYS25 NIC's detect problem Thread-Index: AQHN7z9fAS1G4TfIj068dd7ofw/sx5hCoHgw Date: Thu, 10 Jan 2013 14:38:59 +0000 Message-ID: <23A9CFB8DDE7F34089CC14B4B86FDA58498EC729@SOLNA-MBX01.nschmc.local> References: In-Reply-To: Accept-Language: sv-SE, en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.68.3] MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 on Intel MFSYS25 NIC's detect problem X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, >I trying to install the XCP 1.6 ISO Image on hardware Intel Modular Server MFSYS25v1. >The server has 4 NIC's during installation, but are not detected. >In this same hardware mode l have installed a xenserver 5.6 and the nic's are detected correctly, see below: I had similar issues with Intel cards, but in my case the cards are detected but VLANs are not working. For Xenserver 6.1 there is an updated Intel driver pack that can be manually installed. It dident help me, but it might help you. http://support.citrix.com/article/CTX135324 Best regards Mikael _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 10 21:37:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 21:37:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtPoM-0001r1-GE; Thu, 10 Jan 2013 21:37:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TtPoL-0001qt-Py; Thu, 10 Jan 2013 21:37:17 +0000 Received: from [193.109.254.147:39358] by server-5.bemta-14.messagelabs.com id 18/4E-32031-C843FE05; Thu, 10 Jan 2013 21:37:16 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1357853832!5578703!1 X-Originating-IP: [209.85.216.175] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18743 invoked from network); 10 Jan 2013 21:37:14 -0000 Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com) (209.85.216.175) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 21:37:14 -0000 Received: by mail-qc0-f175.google.com with SMTP id j3so692798qcs.20 for ; Thu, 10 Jan 2013 13:37:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D2SjVvh9CJ9w0tuKrWuRo71H44UxzXvGdj5HUKCQ200=; b=DTIMla3jocfw9mT5rC5mEMB8QRWpL5qDHGCEmk5XCwwBhGwK3iJWBOh01IQvRnb2XM hVQBT/gvIJfsUgTD4uxsHvenXP+wpdKZ9Ka4CTvjXjDmR8CubTXBtW3OaIgk03HCfOMD Dn9afcpWUN/vscsVDf6HyMxLENFl9eSXZTprp/gEuSmWTnsmwXyA/i2gTbGuf9aNJkak 5yKwWdccWxK7hOmgDy95DR4kta1yktFIsTGLCamUmbvsm3+VKJgBfiRdylBOfi88BIZc 0buRiWWHji5T8E9IEgyhWVP+VhqSGw0Sph5Li4Bk8qklvjOsqcL9GPIa+F+zlyLUEoq3 L5Qw== MIME-Version: 1.0 Received: by 10.224.186.82 with SMTP id cr18mr59546448qab.64.1357853831669; Thu, 10 Jan 2013 13:37:11 -0800 (PST) Received: by 10.229.17.19 with HTTP; Thu, 10 Jan 2013 13:37:11 -0800 (PST) In-Reply-To: <1357812259.7989.317.camel@zakaz.uk.xensource.com> References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> Date: Fri, 11 Jan 2013 03:07:11 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Ian Campbell Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4732480908984630470==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4732480908984630470== Content-Type: multipart/alternative; boundary=20cf303b3e834b28c904d2f5fbf9 --20cf303b3e834b28c904d2f5fbf9 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Jan 10, 2013 at 3:34 PM, Ian Campbell wrote: > On Tue, 2013-01-08 at 21:53 +0000, Rushikesh Jadhav wrote: > > > > > > Please help me in diagnosing below error in /var/log/messages > > > > HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) > > for RM: fffff8800d099000 > > This message was printed by your dom1 kernel, via the PV drivers. > > Google suggests to me that txftrans.c is a Windows Vista source file, > but I don't especially want to follow that trail to far for fear of > seeing something I shouldn't. > > I've no idea what the message might mean though. > > Ian. > > Thanks Ian, I have also stopped perusing the file and error. Its just bugging me every hour :( I'm surprised that this error and file is never reported anywhere and I don't think my Windows DomU is any special to generate such error. - Rushikesh --20cf303b3e834b28c904d2f5fbf9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Thu, Jan 10, 2013 at 3:34 PM, Ian Cam= pbell <Ian.Campbell@citrix.com> wrote:
On Tue, 2013-01-08 at 21:53 +0000, Rushikesh Jadhav wrote= :
>
>
> =A0 =A0 =A0 =A0 Please help me in diagnosing below error in /var/log/m= essages
>
> =A0 =A0 =A0 =A0 HVM1[16586]: =A0txftrans.c:4498 -- TXF_HARD_ERROR (0xC= 01A002B)
> =A0 =A0 =A0 =A0 for RM: fffff8800d099000

This message was printed by your dom1 kernel, via the PV drivers.

Google suggests to me that txftrans.c is a Windows Vista source file,
but I don't especially want to follow that trail to far for fear of
seeing something I shouldn't.

I've no idea what the message might mean though.

Ian.

Thanks Ian,

I have also stopped per= using the file and error. Its just bugging me every hour :(
I'm surp= rised that this error and file is never reported anywhere and I don't t= hink my Windows DomU is any special to generate such error.

- Rushikesh
--20cf303b3e834b28c904d2f5fbf9-- --===============4732480908984630470== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4732480908984630470==-- From xen-api-bounces@lists.xen.org Thu Jan 10 21:37:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 21:37:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtPoM-0001r1-GE; Thu, 10 Jan 2013 21:37:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TtPoL-0001qt-Py; Thu, 10 Jan 2013 21:37:17 +0000 Received: from [193.109.254.147:39358] by server-5.bemta-14.messagelabs.com id 18/4E-32031-C843FE05; Thu, 10 Jan 2013 21:37:16 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1357853832!5578703!1 X-Originating-IP: [209.85.216.175] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18743 invoked from network); 10 Jan 2013 21:37:14 -0000 Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com) (209.85.216.175) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 21:37:14 -0000 Received: by mail-qc0-f175.google.com with SMTP id j3so692798qcs.20 for ; Thu, 10 Jan 2013 13:37:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D2SjVvh9CJ9w0tuKrWuRo71H44UxzXvGdj5HUKCQ200=; b=DTIMla3jocfw9mT5rC5mEMB8QRWpL5qDHGCEmk5XCwwBhGwK3iJWBOh01IQvRnb2XM hVQBT/gvIJfsUgTD4uxsHvenXP+wpdKZ9Ka4CTvjXjDmR8CubTXBtW3OaIgk03HCfOMD Dn9afcpWUN/vscsVDf6HyMxLENFl9eSXZTprp/gEuSmWTnsmwXyA/i2gTbGuf9aNJkak 5yKwWdccWxK7hOmgDy95DR4kta1yktFIsTGLCamUmbvsm3+VKJgBfiRdylBOfi88BIZc 0buRiWWHji5T8E9IEgyhWVP+VhqSGw0Sph5Li4Bk8qklvjOsqcL9GPIa+F+zlyLUEoq3 L5Qw== MIME-Version: 1.0 Received: by 10.224.186.82 with SMTP id cr18mr59546448qab.64.1357853831669; Thu, 10 Jan 2013 13:37:11 -0800 (PST) Received: by 10.229.17.19 with HTTP; Thu, 10 Jan 2013 13:37:11 -0800 (PST) In-Reply-To: <1357812259.7989.317.camel@zakaz.uk.xensource.com> References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> Date: Fri, 11 Jan 2013 03:07:11 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Ian Campbell Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4732480908984630470==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4732480908984630470== Content-Type: multipart/alternative; boundary=20cf303b3e834b28c904d2f5fbf9 --20cf303b3e834b28c904d2f5fbf9 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Jan 10, 2013 at 3:34 PM, Ian Campbell wrote: > On Tue, 2013-01-08 at 21:53 +0000, Rushikesh Jadhav wrote: > > > > > > Please help me in diagnosing below error in /var/log/messages > > > > HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) > > for RM: fffff8800d099000 > > This message was printed by your dom1 kernel, via the PV drivers. > > Google suggests to me that txftrans.c is a Windows Vista source file, > but I don't especially want to follow that trail to far for fear of > seeing something I shouldn't. > > I've no idea what the message might mean though. > > Ian. > > Thanks Ian, I have also stopped perusing the file and error. Its just bugging me every hour :( I'm surprised that this error and file is never reported anywhere and I don't think my Windows DomU is any special to generate such error. - Rushikesh --20cf303b3e834b28c904d2f5fbf9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Thu, Jan 10, 2013 at 3:34 PM, Ian Cam= pbell <Ian.Campbell@citrix.com> wrote:
On Tue, 2013-01-08 at 21:53 +0000, Rushikesh Jadhav wrote= :
>
>
> =A0 =A0 =A0 =A0 Please help me in diagnosing below error in /var/log/m= essages
>
> =A0 =A0 =A0 =A0 HVM1[16586]: =A0txftrans.c:4498 -- TXF_HARD_ERROR (0xC= 01A002B)
> =A0 =A0 =A0 =A0 for RM: fffff8800d099000

This message was printed by your dom1 kernel, via the PV drivers.

Google suggests to me that txftrans.c is a Windows Vista source file,
but I don't especially want to follow that trail to far for fear of
seeing something I shouldn't.

I've no idea what the message might mean though.

Ian.

Thanks Ian,

I have also stopped per= using the file and error. Its just bugging me every hour :(
I'm surp= rised that this error and file is never reported anywhere and I don't t= hink my Windows DomU is any special to generate such error.

- Rushikesh
--20cf303b3e834b28c904d2f5fbf9-- --===============4732480908984630470== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4732480908984630470==-- From xen-api-bounces@lists.xen.org Thu Jan 10 22:36:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 22:36:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtQjm-00034x-Fx; Thu, 10 Jan 2013 22:36:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TtQjk-00034s-Td for xen-api@lists.xen.org; Thu, 10 Jan 2013 22:36:37 +0000 Received: from [193.109.254.147:35613] by server-1.bemta-14.messagelabs.com id 4F/D9-00596-4724FE05; Thu, 10 Jan 2013 22:36:36 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1357857392!5581980!1 X-Originating-IP: [209.85.216.54] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10313 invoked from network); 10 Jan 2013 22:36:34 -0000 Received: from mail-qa0-f54.google.com (HELO mail-qa0-f54.google.com) (209.85.216.54) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 22:36:34 -0000 Received: by mail-qa0-f54.google.com with SMTP id j15so1029436qaq.20 for ; Thu, 10 Jan 2013 14:36:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=I4ve5P+6ThBETH7AxZt/gI6BWMx/JqcRfFPcR5x+o0c=; b=qHp6bdbOkTsY3G2VYpNWiYaMX0CsEbHWDrbvJjNajVA7hirBuoJdMpNZ8K9amikGL5 Jgsb/rMl9+ut0+OHC77lwceLswTADki7UMAYj94HRVVxqR0JGunou2lJTqr106tqEWR6 NUShY+Kod4dBSsD9xqJYk1T3JaFaJXa3j82CBw2iWY7+TeeHkRQjcdOAN6qjO71h3Jym 9jBbkwT4CSEzhgGbC/m6MPRsh8oAXHrCX+QTDI2wAX/kNAHp6HoM5ziHG0tAUi7dNune WQ81SIGytr2IZTEFAPQnSIC5Hb01IpWsC7kKnqHxABFtwQ3XdDNlw+ULKAk++kMJcWQe 3Jkg== MIME-Version: 1.0 Received: by 10.224.223.17 with SMTP id ii17mr58439992qab.13.1357857392260; Thu, 10 Jan 2013 14:36:32 -0800 (PST) Received: by 10.229.17.19 with HTTP; Thu, 10 Jan 2013 14:36:32 -0800 (PST) In-Reply-To: <50ED6A50.9020005@gmail.com> References: <50ED6A50.9020005@gmail.com> Date: Fri, 11 Jan 2013 04:06:32 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin Cc: Lars Kurth , "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6, and git branch tree X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4696254344523428773==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4696254344523428773== Content-Type: multipart/alternative; boundary=20cf3074b5988574cf04d2f6cfe1 --20cf3074b5988574cf04d2f6cfe1 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 9, 2013 at 6:32 PM, George Shuklin wrote: > Good day. > > I still do not understand current situation with XCP updates and git tree. > I understand there is a lots of stuff happens between code and rpm, and it > consume lot of time of many guys. > > But few questions about current XCP code and fixes... > > 1) which branch contains current state of xapi for XCP 1.6? > remotes/origin/tampa-lcm from github? > 2) Is tampa-lcm branch HEAD the current stable for XenServer? > 3) Can it safely be compiled and installed to product environment? > > I especially concern about 3rd, because I don't want to suddenly get batch > of XenServers instead current product XCP pool. > > I don't ask about 'when you gonna compile them to RPMs for me', but there > is a mist around git branches, XCP and XenServer relationship. > We finally got human resources to dig inside xapi (and plans to publish > our improvements/features), but we need to know, what exactly to patch. > > Thanks. > > Tampa is the xapi branch which was shipped with XCP1.6 and tampa-lcm is their Life Cycle Management branch. I tried to compare each tag with current xapi-0.2-5217.src.rpm but they all are different. Tampa-lcm has minimal differences with 1.6 code but does not look like the exact code. - Rushikesh > ______________________________**_________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api > --20cf3074b5988574cf04d2f6cfe1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, Jan 9, 2013 at 6:32 PM, George S= huklin <george.shuklin@gmail.com> wrote:
Good day.

I still do not understand current situation with XCP updates and git tree. = I understand there is a lots of stuff happens between code and rpm, and it = consume lot of time of many guys.

But few questions about current XCP code and fixes...

1) which branch contains current state of xapi for XCP 1.6? remotes/origin/= tampa-lcm from github?
2) Is tampa-lcm branch HEAD the current stable for XenServer?
3) Can it safely be compiled and installed to product environment?

I especially concern about 3rd, because I don't want to suddenly get ba= tch of XenServers instead current product XCP pool.

I don't ask about 'when you gonna compile them to RPMs for me',= but there is a mist around git branches, XCP and XenServer relationship. We finally got human resources to dig inside xapi (and plans to publish our= improvements/features), but we need to know, what exactly =A0to patch.

Thanks.


Tampa is the xapi branch which was shipped with X= CP1.6 and tampa-lcm is their Life Cycle Management branch.
I tried to co= mpare each tag with current xapi-0.2-5217.src.rpm but they all are differen= t. Tampa-lcm has minimal differences with 1.6 code but does not look like t= he exact code.

- Rushikesh

=A0
_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--20cf3074b5988574cf04d2f6cfe1-- --===============4696254344523428773== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4696254344523428773==-- From xen-api-bounces@lists.xen.org Thu Jan 10 22:36:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 22:36:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtQjm-00034x-Fx; Thu, 10 Jan 2013 22:36:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TtQjk-00034s-Td for xen-api@lists.xen.org; Thu, 10 Jan 2013 22:36:37 +0000 Received: from [193.109.254.147:35613] by server-1.bemta-14.messagelabs.com id 4F/D9-00596-4724FE05; Thu, 10 Jan 2013 22:36:36 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1357857392!5581980!1 X-Originating-IP: [209.85.216.54] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10313 invoked from network); 10 Jan 2013 22:36:34 -0000 Received: from mail-qa0-f54.google.com (HELO mail-qa0-f54.google.com) (209.85.216.54) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 22:36:34 -0000 Received: by mail-qa0-f54.google.com with SMTP id j15so1029436qaq.20 for ; Thu, 10 Jan 2013 14:36:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=I4ve5P+6ThBETH7AxZt/gI6BWMx/JqcRfFPcR5x+o0c=; b=qHp6bdbOkTsY3G2VYpNWiYaMX0CsEbHWDrbvJjNajVA7hirBuoJdMpNZ8K9amikGL5 Jgsb/rMl9+ut0+OHC77lwceLswTADki7UMAYj94HRVVxqR0JGunou2lJTqr106tqEWR6 NUShY+Kod4dBSsD9xqJYk1T3JaFaJXa3j82CBw2iWY7+TeeHkRQjcdOAN6qjO71h3Jym 9jBbkwT4CSEzhgGbC/m6MPRsh8oAXHrCX+QTDI2wAX/kNAHp6HoM5ziHG0tAUi7dNune WQ81SIGytr2IZTEFAPQnSIC5Hb01IpWsC7kKnqHxABFtwQ3XdDNlw+ULKAk++kMJcWQe 3Jkg== MIME-Version: 1.0 Received: by 10.224.223.17 with SMTP id ii17mr58439992qab.13.1357857392260; Thu, 10 Jan 2013 14:36:32 -0800 (PST) Received: by 10.229.17.19 with HTTP; Thu, 10 Jan 2013 14:36:32 -0800 (PST) In-Reply-To: <50ED6A50.9020005@gmail.com> References: <50ED6A50.9020005@gmail.com> Date: Fri, 11 Jan 2013 04:06:32 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin Cc: Lars Kurth , "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.6, and git branch tree X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4696254344523428773==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4696254344523428773== Content-Type: multipart/alternative; boundary=20cf3074b5988574cf04d2f6cfe1 --20cf3074b5988574cf04d2f6cfe1 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 9, 2013 at 6:32 PM, George Shuklin wrote: > Good day. > > I still do not understand current situation with XCP updates and git tree. > I understand there is a lots of stuff happens between code and rpm, and it > consume lot of time of many guys. > > But few questions about current XCP code and fixes... > > 1) which branch contains current state of xapi for XCP 1.6? > remotes/origin/tampa-lcm from github? > 2) Is tampa-lcm branch HEAD the current stable for XenServer? > 3) Can it safely be compiled and installed to product environment? > > I especially concern about 3rd, because I don't want to suddenly get batch > of XenServers instead current product XCP pool. > > I don't ask about 'when you gonna compile them to RPMs for me', but there > is a mist around git branches, XCP and XenServer relationship. > We finally got human resources to dig inside xapi (and plans to publish > our improvements/features), but we need to know, what exactly to patch. > > Thanks. > > Tampa is the xapi branch which was shipped with XCP1.6 and tampa-lcm is their Life Cycle Management branch. I tried to compare each tag with current xapi-0.2-5217.src.rpm but they all are different. Tampa-lcm has minimal differences with 1.6 code but does not look like the exact code. - Rushikesh > ______________________________**_________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api > --20cf3074b5988574cf04d2f6cfe1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, Jan 9, 2013 at 6:32 PM, George S= huklin <george.shuklin@gmail.com> wrote:
Good day.

I still do not understand current situation with XCP updates and git tree. = I understand there is a lots of stuff happens between code and rpm, and it = consume lot of time of many guys.

But few questions about current XCP code and fixes...

1) which branch contains current state of xapi for XCP 1.6? remotes/origin/= tampa-lcm from github?
2) Is tampa-lcm branch HEAD the current stable for XenServer?
3) Can it safely be compiled and installed to product environment?

I especially concern about 3rd, because I don't want to suddenly get ba= tch of XenServers instead current product XCP pool.

I don't ask about 'when you gonna compile them to RPMs for me',= but there is a mist around git branches, XCP and XenServer relationship. We finally got human resources to dig inside xapi (and plans to publish our= improvements/features), but we need to know, what exactly =A0to patch.

Thanks.


Tampa is the xapi branch which was shipped with X= CP1.6 and tampa-lcm is their Life Cycle Management branch.
I tried to co= mpare each tag with current xapi-0.2-5217.src.rpm but they all are differen= t. Tampa-lcm has minimal differences with 1.6 code but does not look like t= he exact code.

- Rushikesh

=A0
_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--20cf3074b5988574cf04d2f6cfe1-- --===============4696254344523428773== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4696254344523428773==-- From xen-api-bounces@lists.xen.org Thu Jan 10 23:37:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 23:37:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRh0-0005LB-K4; Thu, 10 Jan 2013 23:37:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRgz-0005L6-PV for xen-api@lists.xen.org; Thu, 10 Jan 2013 23:37:50 +0000 Received: from [85.158.138.51:15733] by server-11.bemta-3.messagelabs.com id E5/A8-13335-8C05FE05; Thu, 10 Jan 2013 23:37:44 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1357861062!18579184!1 X-Originating-IP: [209.85.217.178] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2916 invoked from network); 10 Jan 2013 23:37:42 -0000 Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com) (209.85.217.178) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 23:37:42 -0000 Received: by mail-lb0-f178.google.com with SMTP id l5so909399lbo.9 for ; Thu, 10 Jan 2013 15:37:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Tj1H6T2NyKmYTfYVVlQzv+kvbEe/dtJ2IHd5KhjZa8E=; b=JH4IVV+qF1JuvL7cn11p4NiyvmoCyfFaY8q9jtHb2ZSn5ViHmJNXIv9z99MKzhRgcA HdaxDy5aIZfwnha0xhBky/laWF+wcSRrgCsZPXNO612c5ppsGDkTwDvAQoy4FHYl1eIY 5Te+wNfNM4LpfK3oQ9kyGUnQOP3ZTdEq7rl6Fr5Vq2mPeIgwFPDZhxb302xBsbPW6EUj /Tz3J8yk8aHf12UGU3yaT03ub7lveu0cSuz+DUD1FvI5gISmgK6iuOCoGlQC/WGaCZ4L OkstRlmLZQTCbG3Nty70M0QsWUonWYB9/yEjD93F4JBGOENn8mTyOMJ+rTkb53u2TUXb y4Iw== X-Received: by 10.152.125.240 with SMTP id mt16mr70799543lab.17.1357861061834; Thu, 10 Jan 2013 15:37:41 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id f8sm1458608lbg.2.2013.01.10.15.37.41 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 15:37:41 -0800 (PST) Message-ID: <50EF50C4.6030300@gmail.com> Date: Fri, 11 Jan 2013 03:37:40 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> <50EE1182.3090107@ondore.com> In-Reply-To: <50EE1182.3090107@ondore.com> Subject: Re: [Xen-API] [Solved] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MTAuMDEuMjAxMyAwNDo1NSwgQWxleGFuZHJlIEtvdXpuZXRzb3Yg0L/QuNGI0LXRgjoKPiBIZWxs by4KPgo+IEkgY2FuIGNvbmZpcm0sIEkgaGF2ZSBzdWNjZXNzZnVsbHkgbW91bnRlZCBwYXJ0aXRp b25zIGZyb20gbXkgVkhEIFZESSAKPiB1bmRlciBEb20wLiBUaGFua3MgYSBsb3QhCj4KPiBFbCAw OC8wMS8xMyAxMjowNywgR2VvcmdlIFNodWtsaW4gZXNjcmliacOzOgo+PiBPaywgaGVyZSBpbXBv cnRhbnQgc3R1ZmYuIFdoZW4gVkJEIGlzIHBsdWdnZWQgdG8gZG9tMCwgaXQgcGx1Z2dpbmcgbm90 Cj4+IGFzICdub3JtYWwnIGRldmljZSAod2l0aCB1ZGV2IGF0dGVudGlvbiksIGJ1dCBhcyBkZXZp Y2UgaW4gCj4+IC9kZXYvc20vYmFja2VuZC4KPgo+IFllcywgdGhhdCB3YXMgaW1wb3J0YW50LiBX aGVyZSBoYXZlIHlvdSBsZWFybmVkIHRoYXQgb2NjdWx0IHN0dWZmPwoKV2VsbCwgaWYgeW91IHdh bnQgdG8gZG8gc29tZXRoaW5nIHdpdGggWENQIG91dHNpZGUgJ3J1biBmZXcgVk1zIGZvciAKaW50 ZXJuYWwgdXNlJywgeW91IG5lZWQgdG8ga25vdyBpdHMgaW50ZXJuYWxzLiBXaG9sZSBzdHVmZiBh cm91bmQgU00sIApkb21haW4gbWFuYWdlbWVudCwgVkhEcyBhbmQgc28gb24gaXMgY3J1Y2lhbCB0 byBtYWludGFpbiBpdCBpbiBub3JtYWwgCnN0YXRlIHVuZGVyIGhpZ2hsb2FkIChsaWtlIG15IGNh c2UpLiBTbyB2ZXJ5IG9mdGVuIGl0cyBqdXN0IHNvdXJjZSBjb2RlIApyZXNlYXJjaC4gTW9zdCBv ZiB0aGUgU00gcGFydCBpcyBweXRob24sIHNvbWUgaXMgc2hlbGwgc2NyaXB0cywgbGVzc2VyIApw YXJ0IGlzIGluc2lkZSB4YXBpIChvY2FtbCwgLi4uc2lnaCkuICBUaGVyZSBpcyBvbmx5IG9uZSB0 cnVzdGVkIHNvdXJjZSAKb2YgaW5mb3JtYXRpb24gLSB0aGUgc291cmNlIGNvZGUuCj4KPj4gSGVy ZSBzYW1wbGUgbG9nIChjaGFuZ2UgdXVpZHMgb24geW91IHRhc3RlKToKPj4KPj4geGUgdmJkLWNy ZWF0ZSB2bS11dWlkPTUzYzNkODc4LWI2MGItNDhlYy1hYWFjLTczZjdhZGY5YWIzZAo+PiB2ZGkt dXVpZD01ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzIgZGV2aWNlPTYKPj4geGUg dmJkLXBsdWcgdXVpZD00MDdlYjNhNi05MTlmLWY2MDUtMDg4My1lMTJhYWE5MTMyMWQKPj4KPj4g bHMgLWxhIC9kZXYvc20vYmFja2VuZC81NWVhMjBkMi04NjExLTExMjEtOWU5ZS1jMjZiMzVhYzE4 NTIvCj4+INC40YLQvtCz0L4gNAo+PiBkcnd4ci14ci14IDIgcm9vdCByb290ICAgICA4MCDQr9C9 0LIgIDggMjE6NTcgLgo+PiBkcnd4ci14ci14IDMgcm9vdCByb290ICAgICA2MCDQlNC10LogMTgg MTc6NDAgLi4KPj4gYnJ3LS0tLS0tLSAxIHJvb3Qgcm9vdCAyNTMsIDAg0K/QvdCyICA4IDIxOjU3 Cj4+IDVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMgo+PiAtcnctci0tci0tIDEg cm9vdCByb290ICAgIDg1MiDQr9C90LIgIDggMjE6NTcKPj4gNWUyYzMxYTUtMWQxYi00YWJlLTk4 OTItMWZhM2JjNDdiNTMyLmF0dGFjaF9pbmZvCj4gSSBoYXZlIGRvbmUgdGhlIHByb2Nlc3MgYXMg eW91IGRlc2NyaWJlZC4KPiBHb3QgdGhlIHNhbWUgcmVzdWx0IGFzIHlvdSwgZXhjZXB0IHRoYXQg SSBkb24ndCBoYXZlICouYXR0YWNoX2luZm8gCj4gZmlsZSwgb25seSB0aGUgZGV2aWNlIGZpbGUu Cj4KPiBXaGF0IGlzIHRoZSByZWxldmFuY2Ugb2YgZGV2aWNlPTYgdW5kZXIgdmJkLWNyZWF0ZSBj b21tYW5kPyBSZWFsbHkgZGlkIAo+IG5vdCBrbmV3IHdoYXQgdG8gcHV0IHRoZXJlLCBJIGhhdmUg dXNlZCBkZXZpY2U9YXV0b2RldGVjdCwgaG9wZSBYQ1AgaXMgCj4gc21hcnQgZW5vdWdoIHRvIGNs ZWFuIHVwIGV2ZXJ5dGhpbmcgbmljZWx5IGFmdGVyIEkgdW5wbHVnIGl0Lgo+Cj4KV2VsbCwgSSB0 aGluayAnZGV2aWNlJyBmb3IgdmJkcyBmb3IgZG9tMCBpcyBhcnRpZmFjdCBmcm9tIGVhcmxpZXIg ZGF5cyAKKFhDUCAxLjEgZi5lLikgd2hpY2ggaGFzIGNyZWF0aW5nIC9kZXYveHZkW2Etel0gZGV2 aWNlcyBkdXJpbmcgdmJkLXBsdWcuIApOb3csIEkgdGhpbmsgdGhhdCBmaWVsZCBtZWFucyBub3Ro aW5nIChvbmx5IGZvciBkb20wIHZiZHMhIGZvciBkb21VIGl0IAp2ZXJ5IGltcG9ydGFudCB0aGlu ZykuCgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVu Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Thu Jan 10 23:37:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 23:37:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRh0-0005LB-K4; Thu, 10 Jan 2013 23:37:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRgz-0005L6-PV for xen-api@lists.xen.org; Thu, 10 Jan 2013 23:37:50 +0000 Received: from [85.158.138.51:15733] by server-11.bemta-3.messagelabs.com id E5/A8-13335-8C05FE05; Thu, 10 Jan 2013 23:37:44 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1357861062!18579184!1 X-Originating-IP: [209.85.217.178] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2916 invoked from network); 10 Jan 2013 23:37:42 -0000 Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com) (209.85.217.178) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 23:37:42 -0000 Received: by mail-lb0-f178.google.com with SMTP id l5so909399lbo.9 for ; Thu, 10 Jan 2013 15:37:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Tj1H6T2NyKmYTfYVVlQzv+kvbEe/dtJ2IHd5KhjZa8E=; b=JH4IVV+qF1JuvL7cn11p4NiyvmoCyfFaY8q9jtHb2ZSn5ViHmJNXIv9z99MKzhRgcA HdaxDy5aIZfwnha0xhBky/laWF+wcSRrgCsZPXNO612c5ppsGDkTwDvAQoy4FHYl1eIY 5Te+wNfNM4LpfK3oQ9kyGUnQOP3ZTdEq7rl6Fr5Vq2mPeIgwFPDZhxb302xBsbPW6EUj /Tz3J8yk8aHf12UGU3yaT03ub7lveu0cSuz+DUD1FvI5gISmgK6iuOCoGlQC/WGaCZ4L OkstRlmLZQTCbG3Nty70M0QsWUonWYB9/yEjD93F4JBGOENn8mTyOMJ+rTkb53u2TUXb y4Iw== X-Received: by 10.152.125.240 with SMTP id mt16mr70799543lab.17.1357861061834; Thu, 10 Jan 2013 15:37:41 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id f8sm1458608lbg.2.2013.01.10.15.37.41 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 15:37:41 -0800 (PST) Message-ID: <50EF50C4.6030300@gmail.com> Date: Fri, 11 Jan 2013 03:37:40 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50E77A63.4040806@ondore.com> <50E7B6C4.2010705@gmail.com> <50E7D754.3020703@ondore.com> <50EC606C.2070702@gmail.com> <50EE1182.3090107@ondore.com> In-Reply-To: <50EE1182.3090107@ondore.com> Subject: Re: [Xen-API] [Solved] look into VHD VDI from Control Domain in XCP 1.6 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MTAuMDEuMjAxMyAwNDo1NSwgQWxleGFuZHJlIEtvdXpuZXRzb3Yg0L/QuNGI0LXRgjoKPiBIZWxs by4KPgo+IEkgY2FuIGNvbmZpcm0sIEkgaGF2ZSBzdWNjZXNzZnVsbHkgbW91bnRlZCBwYXJ0aXRp b25zIGZyb20gbXkgVkhEIFZESSAKPiB1bmRlciBEb20wLiBUaGFua3MgYSBsb3QhCj4KPiBFbCAw OC8wMS8xMyAxMjowNywgR2VvcmdlIFNodWtsaW4gZXNjcmliacOzOgo+PiBPaywgaGVyZSBpbXBv cnRhbnQgc3R1ZmYuIFdoZW4gVkJEIGlzIHBsdWdnZWQgdG8gZG9tMCwgaXQgcGx1Z2dpbmcgbm90 Cj4+IGFzICdub3JtYWwnIGRldmljZSAod2l0aCB1ZGV2IGF0dGVudGlvbiksIGJ1dCBhcyBkZXZp Y2UgaW4gCj4+IC9kZXYvc20vYmFja2VuZC4KPgo+IFllcywgdGhhdCB3YXMgaW1wb3J0YW50LiBX aGVyZSBoYXZlIHlvdSBsZWFybmVkIHRoYXQgb2NjdWx0IHN0dWZmPwoKV2VsbCwgaWYgeW91IHdh bnQgdG8gZG8gc29tZXRoaW5nIHdpdGggWENQIG91dHNpZGUgJ3J1biBmZXcgVk1zIGZvciAKaW50 ZXJuYWwgdXNlJywgeW91IG5lZWQgdG8ga25vdyBpdHMgaW50ZXJuYWxzLiBXaG9sZSBzdHVmZiBh cm91bmQgU00sIApkb21haW4gbWFuYWdlbWVudCwgVkhEcyBhbmQgc28gb24gaXMgY3J1Y2lhbCB0 byBtYWludGFpbiBpdCBpbiBub3JtYWwgCnN0YXRlIHVuZGVyIGhpZ2hsb2FkIChsaWtlIG15IGNh c2UpLiBTbyB2ZXJ5IG9mdGVuIGl0cyBqdXN0IHNvdXJjZSBjb2RlIApyZXNlYXJjaC4gTW9zdCBv ZiB0aGUgU00gcGFydCBpcyBweXRob24sIHNvbWUgaXMgc2hlbGwgc2NyaXB0cywgbGVzc2VyIApw YXJ0IGlzIGluc2lkZSB4YXBpIChvY2FtbCwgLi4uc2lnaCkuICBUaGVyZSBpcyBvbmx5IG9uZSB0 cnVzdGVkIHNvdXJjZSAKb2YgaW5mb3JtYXRpb24gLSB0aGUgc291cmNlIGNvZGUuCj4KPj4gSGVy ZSBzYW1wbGUgbG9nIChjaGFuZ2UgdXVpZHMgb24geW91IHRhc3RlKToKPj4KPj4geGUgdmJkLWNy ZWF0ZSB2bS11dWlkPTUzYzNkODc4LWI2MGItNDhlYy1hYWFjLTczZjdhZGY5YWIzZAo+PiB2ZGkt dXVpZD01ZTJjMzFhNS0xZDFiLTRhYmUtOTg5Mi0xZmEzYmM0N2I1MzIgZGV2aWNlPTYKPj4geGUg dmJkLXBsdWcgdXVpZD00MDdlYjNhNi05MTlmLWY2MDUtMDg4My1lMTJhYWE5MTMyMWQKPj4KPj4g bHMgLWxhIC9kZXYvc20vYmFja2VuZC81NWVhMjBkMi04NjExLTExMjEtOWU5ZS1jMjZiMzVhYzE4 NTIvCj4+INC40YLQvtCz0L4gNAo+PiBkcnd4ci14ci14IDIgcm9vdCByb290ICAgICA4MCDQr9C9 0LIgIDggMjE6NTcgLgo+PiBkcnd4ci14ci14IDMgcm9vdCByb290ICAgICA2MCDQlNC10LogMTgg MTc6NDAgLi4KPj4gYnJ3LS0tLS0tLSAxIHJvb3Qgcm9vdCAyNTMsIDAg0K/QvdCyICA4IDIxOjU3 Cj4+IDVlMmMzMWE1LTFkMWItNGFiZS05ODkyLTFmYTNiYzQ3YjUzMgo+PiAtcnctci0tci0tIDEg cm9vdCByb290ICAgIDg1MiDQr9C90LIgIDggMjE6NTcKPj4gNWUyYzMxYTUtMWQxYi00YWJlLTk4 OTItMWZhM2JjNDdiNTMyLmF0dGFjaF9pbmZvCj4gSSBoYXZlIGRvbmUgdGhlIHByb2Nlc3MgYXMg eW91IGRlc2NyaWJlZC4KPiBHb3QgdGhlIHNhbWUgcmVzdWx0IGFzIHlvdSwgZXhjZXB0IHRoYXQg SSBkb24ndCBoYXZlICouYXR0YWNoX2luZm8gCj4gZmlsZSwgb25seSB0aGUgZGV2aWNlIGZpbGUu Cj4KPiBXaGF0IGlzIHRoZSByZWxldmFuY2Ugb2YgZGV2aWNlPTYgdW5kZXIgdmJkLWNyZWF0ZSBj b21tYW5kPyBSZWFsbHkgZGlkIAo+IG5vdCBrbmV3IHdoYXQgdG8gcHV0IHRoZXJlLCBJIGhhdmUg dXNlZCBkZXZpY2U9YXV0b2RldGVjdCwgaG9wZSBYQ1AgaXMgCj4gc21hcnQgZW5vdWdoIHRvIGNs ZWFuIHVwIGV2ZXJ5dGhpbmcgbmljZWx5IGFmdGVyIEkgdW5wbHVnIGl0Lgo+Cj4KV2VsbCwgSSB0 aGluayAnZGV2aWNlJyBmb3IgdmJkcyBmb3IgZG9tMCBpcyBhcnRpZmFjdCBmcm9tIGVhcmxpZXIg ZGF5cyAKKFhDUCAxLjEgZi5lLikgd2hpY2ggaGFzIGNyZWF0aW5nIC9kZXYveHZkW2Etel0gZGV2 aWNlcyBkdXJpbmcgdmJkLXBsdWcuIApOb3csIEkgdGhpbmsgdGhhdCBmaWVsZCBtZWFucyBub3Ro aW5nIChvbmx5IGZvciBkb20wIHZiZHMhIGZvciBkb21VIGl0IAp2ZXJ5IGltcG9ydGFudCB0aGlu ZykuCgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVu Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Thu Jan 10 23:40:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 23:40:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRjI-0005QG-5v; Thu, 10 Jan 2013 23:40:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRjG-0005Q8-CQ for xen-api@lists.xen.org; Thu, 10 Jan 2013 23:40:10 +0000 Received: from [85.158.143.99:2145] by server-2.bemta-4.messagelabs.com id 91/59-24322-9515FE05; Thu, 10 Jan 2013 23:40:09 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1357861207!17800905!1 X-Originating-IP: [209.85.215.53] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29840 invoked from network); 10 Jan 2013 23:40:08 -0000 Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com) (209.85.215.53) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 23:40:08 -0000 Received: by mail-la0-f53.google.com with SMTP id fn20so1198317lab.26 for ; Thu, 10 Jan 2013 15:40:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=jhxdiwKuyMc0pAvCjI59Quvp3zZ5BU8NHy49ZLKflbg=; b=znaFLtt0lhMhzK/N9TE1F3OKho7y6DH731M+nGWVfigdoY4o/wMHDwTfhq9yA+BmZ6 CRt9y9QoDBp3IjKgaXX+GX5UU+Gx57t9/UjFrFzKZa7nQxwH73LRrrYBAEh+serhivS1 F4K/SGck0reLvSuZnR3Jnd1dutqQf5YugrCr5xp4Xpax1K7Cb/ps4O/9vOqS2bIGqFNh S93h9cQc2S7pD9iLUm5BDv4HSEnN1l15rHWCHU+0O/RsAwwnEbNDgChtvKSXItWjofeZ HzBO1bXY072+V2S0oH8usQyt/pp7if1axrWhS9A+YBSX+ob7ISIJPtsMcQ8PhbCM4q4k o9/A== X-Received: by 10.112.40.104 with SMTP id w8mr30999572lbk.114.1357861205458; Thu, 10 Jan 2013 15:40:05 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id lr20sm1373462lab.17.2013.01.10.15.40.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 15:40:05 -0800 (PST) Message-ID: <50EF5154.5050103@gmail.com> Date: Fri, 11 Jan 2013 03:40:04 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> In-Reply-To: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> Subject: Re: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org QXJlIHRob3NlIGhvc3RzIGluIHNhbWUgcG9vbCBvciBpbiBzZXBhcmF0ZSBwb29scz8gSWYgc2Ft ZSBwb29sLCBzaGFyZWQgClNSIG9yIGxvY2FsPyBBbnl3YXksIGRldGFpbHMgc2hvdWxkIGJlIGlu IC92YXIvbG9nL3hlbnNvdXJjZS5sb2cgKHRvbyAKbXVjaCBkZXRhaWxzLCBhY3R1YWxseSkuCgoK MTAuMDEuMjAxMyAxNDo0OSwgRGF2ZSBBdmVudCDQv9C40YjQtdGCOgo+IEkgYW0gaGF2aW5nIGlz c3VlcyB3aXRoIG1pZ3JhdGluZyBWTXMgYmV0d2VlbiBob3N0cy4gSGVyZSBpcyBob3cgSSBjYW4g cmVwcm9kdWNlIHRoZSBwcm9ibGVtOgo+Cj4gMSkgQ3JlYXRlIDIgbmV3IFZNJ3MgKHVzaW5nIGVp dGhlciBhIGZyZXNoIGluc3RhbGwgZnJvbSBOZXQgSW5zdGFsbCBvZiBEZWJpYW4gb3IgZnJvbSBh ICJHb2xkZW4gSW1hZ2UiIG9mIGEgVk0gcHJldmlvdXNseSBjb252ZXJ0ZWQgdG8gYSBUZW1wbGF0 ZSkKPgo+IDIpIE1pZ3JhdGUgb25lIG9mIHRoZSBWTXMgdG8gYW5vdGhlciBob3N0cwo+Cj4gMykg QXR0ZW1wdCB0byBtaWdyYXRlIHRoZSBzYW1lIFZNIGJhY2sgdG8gdGhlIG9yaWdpbmFsIGhvc3Qg aG93ZXZlciBpdCByZWZ1c2VzIGFuZCB0aHJvd3M6Cj4KPiBDYW5ub3QgcmVzdG9yZSB0aGlzIFZN IGJlY2F1c2UgaXQgd291bGQgY3JlYXRlIGEgZHVwbGljYXRlCj4gdm06IE9wYXF1ZVJlZjo3MTFm MjJmMy05ZTM1LWIxM2UtMWMzNS01OGU4YTU3OGNhMGUKPgo+IFdoYXQgZXhhY3RseSBkb2VzIGl0 IHRoaW5rIGlzIGJlaW5nIGR1cGxpY2F0ZWQ/IE5vbmUgb2YgdGhlIG9yaWdpbmFsIGFzc2V0cyBh cHBlYXIgdG8gaGF2ZSBiZWVuIGxlZnQgYmVoaW5kIChmYWlsZWQgdG8gYmUgZGVsZXRlZCBldGMp LiBJIGNhbid0IHNlZSB3aHkgdGhpcyBpcyBmYWlsaW5nLgo+Cj4gQW55IGlkZWFzPwo+CgoKX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWls aW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Thu Jan 10 23:40:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 10 Jan 2013 23:40:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRjI-0005QG-5v; Thu, 10 Jan 2013 23:40:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRjG-0005Q8-CQ for xen-api@lists.xen.org; Thu, 10 Jan 2013 23:40:10 +0000 Received: from [85.158.143.99:2145] by server-2.bemta-4.messagelabs.com id 91/59-24322-9515FE05; Thu, 10 Jan 2013 23:40:09 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1357861207!17800905!1 X-Originating-IP: [209.85.215.53] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29840 invoked from network); 10 Jan 2013 23:40:08 -0000 Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com) (209.85.215.53) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2013 23:40:08 -0000 Received: by mail-la0-f53.google.com with SMTP id fn20so1198317lab.26 for ; Thu, 10 Jan 2013 15:40:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=jhxdiwKuyMc0pAvCjI59Quvp3zZ5BU8NHy49ZLKflbg=; b=znaFLtt0lhMhzK/N9TE1F3OKho7y6DH731M+nGWVfigdoY4o/wMHDwTfhq9yA+BmZ6 CRt9y9QoDBp3IjKgaXX+GX5UU+Gx57t9/UjFrFzKZa7nQxwH73LRrrYBAEh+serhivS1 F4K/SGck0reLvSuZnR3Jnd1dutqQf5YugrCr5xp4Xpax1K7Cb/ps4O/9vOqS2bIGqFNh S93h9cQc2S7pD9iLUm5BDv4HSEnN1l15rHWCHU+0O/RsAwwnEbNDgChtvKSXItWjofeZ HzBO1bXY072+V2S0oH8usQyt/pp7if1axrWhS9A+YBSX+ob7ISIJPtsMcQ8PhbCM4q4k o9/A== X-Received: by 10.112.40.104 with SMTP id w8mr30999572lbk.114.1357861205458; Thu, 10 Jan 2013 15:40:05 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id lr20sm1373462lab.17.2013.01.10.15.40.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 15:40:05 -0800 (PST) Message-ID: <50EF5154.5050103@gmail.com> Date: Fri, 11 Jan 2013 03:40:04 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> In-Reply-To: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> Subject: Re: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org QXJlIHRob3NlIGhvc3RzIGluIHNhbWUgcG9vbCBvciBpbiBzZXBhcmF0ZSBwb29scz8gSWYgc2Ft ZSBwb29sLCBzaGFyZWQgClNSIG9yIGxvY2FsPyBBbnl3YXksIGRldGFpbHMgc2hvdWxkIGJlIGlu IC92YXIvbG9nL3hlbnNvdXJjZS5sb2cgKHRvbyAKbXVjaCBkZXRhaWxzLCBhY3R1YWxseSkuCgoK MTAuMDEuMjAxMyAxNDo0OSwgRGF2ZSBBdmVudCDQv9C40YjQtdGCOgo+IEkgYW0gaGF2aW5nIGlz c3VlcyB3aXRoIG1pZ3JhdGluZyBWTXMgYmV0d2VlbiBob3N0cy4gSGVyZSBpcyBob3cgSSBjYW4g cmVwcm9kdWNlIHRoZSBwcm9ibGVtOgo+Cj4gMSkgQ3JlYXRlIDIgbmV3IFZNJ3MgKHVzaW5nIGVp dGhlciBhIGZyZXNoIGluc3RhbGwgZnJvbSBOZXQgSW5zdGFsbCBvZiBEZWJpYW4gb3IgZnJvbSBh ICJHb2xkZW4gSW1hZ2UiIG9mIGEgVk0gcHJldmlvdXNseSBjb252ZXJ0ZWQgdG8gYSBUZW1wbGF0 ZSkKPgo+IDIpIE1pZ3JhdGUgb25lIG9mIHRoZSBWTXMgdG8gYW5vdGhlciBob3N0cwo+Cj4gMykg QXR0ZW1wdCB0byBtaWdyYXRlIHRoZSBzYW1lIFZNIGJhY2sgdG8gdGhlIG9yaWdpbmFsIGhvc3Qg aG93ZXZlciBpdCByZWZ1c2VzIGFuZCB0aHJvd3M6Cj4KPiBDYW5ub3QgcmVzdG9yZSB0aGlzIFZN IGJlY2F1c2UgaXQgd291bGQgY3JlYXRlIGEgZHVwbGljYXRlCj4gdm06IE9wYXF1ZVJlZjo3MTFm MjJmMy05ZTM1LWIxM2UtMWMzNS01OGU4YTU3OGNhMGUKPgo+IFdoYXQgZXhhY3RseSBkb2VzIGl0 IHRoaW5rIGlzIGJlaW5nIGR1cGxpY2F0ZWQ/IE5vbmUgb2YgdGhlIG9yaWdpbmFsIGFzc2V0cyBh cHBlYXIgdG8gaGF2ZSBiZWVuIGxlZnQgYmVoaW5kIChmYWlsZWQgdG8gYmUgZGVsZXRlZCBldGMp LiBJIGNhbid0IHNlZSB3aHkgdGhpcyBpcyBmYWlsaW5nLgo+Cj4gQW55IGlkZWFzPwo+CgoKX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWls aW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Fri Jan 11 02:46:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 02:46:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtUds-0003Zm-3j; Fri, 11 Jan 2013 02:46:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtUdq-0003Ze-Jm for xen-api@lists.xen.org; Fri, 11 Jan 2013 02:46:46 +0000 Received: from [85.158.139.211:43728] by server-6.bemta-5.messagelabs.com id 7A/A9-30498-51D7FE05; Fri, 11 Jan 2013 02:46:45 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1357872404!22929086!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22851 invoked from network); 11 Jan 2013 02:46:45 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 02:46:45 -0000 Received: by mail-la0-f48.google.com with SMTP id ej20so1303249lab.21 for ; Thu, 10 Jan 2013 18:46:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=2Ch8xdcw5x8Pv6+LnpSzrO5vLD+gopyrHr0cpkff8Vs=; b=Y3+7LG02XqNdEmsinpeAYW6XQ2gWg1ieuzyP9upAsi79fmWs93IoYugtw6rmG+WUkI VI1IKBhsBg0dSoQHTAnEliWPWSXHmtg3ezHcmzxnwj/yfzK1zwIwkjUCNisnWydDXelp eD+FNbj2Vlq17m6gzybxT8ETrjoQNpkTBhD72+reXSP8ZYsIfd+GhA8yc3wyUjNriOmm 7Zrf6GFms9DbwO5aIw2MUXmT1pBoRyOwyk4ZQszSFq9Em6PzOEzcZWwsFJnnNdlq12bj W7Gb7PXv6hrIBkCUIQ91Ep1T+LFGbeZX7tyrUb8WFgoXZTfrRpIKeoZh9PLN2ekYGpKM rkhg== X-Received: by 10.152.144.38 with SMTP id sj6mr70148387lab.48.1357872404584; Thu, 10 Jan 2013 18:46:44 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id mb2sm1469931lab.7.2013.01.10.18.46.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 18:46:44 -0800 (PST) Message-ID: <50EF7D13.3080004@gmail.com> Date: Fri, 11 Jan 2013 06:46:43 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , neganov@selectel.ru Subject: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Pumping up detective story: which commit from public repository is the most near to xapi-0.2.src.rpm? Here my lame script to find it: for a in `git log --oneline|head -n 100|awk '{print $1}'`;do git checkout $a 2>/dev/null; echo -n $a ' ';diff -rux .git /github/xcp1.6/xapi-0.2/ . |wc -l;done And here some results: tampa-lcm - 113 lines differ (0a9de3b) tampa - 1k sanibel-lcm - 53k master - 3k cooper - 34k cooper2 - 27k trunk-64bit - 1k clearwater - 113 (c59b8b5) boston - 54k boston-beta - 62k boston-lcm 54k rrdd - 10k catkin - 53k So the smallest difference between legendary and unreachable e92405831b3300f6d2108d7bd0d2c329b4d1e918 is 113 changes. I check git diff 0a9de3b c59b8b5 and found they are the same. Now, diff analysis: ./ocaml/xapi/db_gc.ml 1) indentation 2) indentation 3) indentation 4) indentation 5) Indentation (so, actually, nothing changes, ocaml is not python, spaces does not counted as source code) ./ocaml/xapi/xapi.ml 1) comments out function (src.rpm contains, git code - not) -(* Hack to allow XCP Boston hosts to migrate to XCP Tampa hosts during - an upgrade. If we are in rolling pool upgrade mode, we will add the - key product-version=$PLATFORM_VERSION to the software-version - map. We'll need to start a thread to watch for the pool to leave - upgrade mode, and then remove the key. We should only do this (as - in, add the key and then remove it) if it is not already set by the - inventory file. *) -let boston_tampa_upgrade_hack ~__context = 2) call of that function: (* See above for comment *) - boston_tampa_upgrade_hack ~__context ; Verdict: commit 0a9de3b should be assumed as commit from public available repo witch most close to the content of the source ISO for the XCP 1.6. I'll publish notes on all new commits from that to the head of tampa-lcm. PS I really hate that style 'opensource reverse-engineering'. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 02:46:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 02:46:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtUds-0003Zm-3j; Fri, 11 Jan 2013 02:46:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtUdq-0003Ze-Jm for xen-api@lists.xen.org; Fri, 11 Jan 2013 02:46:46 +0000 Received: from [85.158.139.211:43728] by server-6.bemta-5.messagelabs.com id 7A/A9-30498-51D7FE05; Fri, 11 Jan 2013 02:46:45 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1357872404!22929086!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22851 invoked from network); 11 Jan 2013 02:46:45 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 02:46:45 -0000 Received: by mail-la0-f48.google.com with SMTP id ej20so1303249lab.21 for ; Thu, 10 Jan 2013 18:46:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=2Ch8xdcw5x8Pv6+LnpSzrO5vLD+gopyrHr0cpkff8Vs=; b=Y3+7LG02XqNdEmsinpeAYW6XQ2gWg1ieuzyP9upAsi79fmWs93IoYugtw6rmG+WUkI VI1IKBhsBg0dSoQHTAnEliWPWSXHmtg3ezHcmzxnwj/yfzK1zwIwkjUCNisnWydDXelp eD+FNbj2Vlq17m6gzybxT8ETrjoQNpkTBhD72+reXSP8ZYsIfd+GhA8yc3wyUjNriOmm 7Zrf6GFms9DbwO5aIw2MUXmT1pBoRyOwyk4ZQszSFq9Em6PzOEzcZWwsFJnnNdlq12bj W7Gb7PXv6hrIBkCUIQ91Ep1T+LFGbeZX7tyrUb8WFgoXZTfrRpIKeoZh9PLN2ekYGpKM rkhg== X-Received: by 10.152.144.38 with SMTP id sj6mr70148387lab.48.1357872404584; Thu, 10 Jan 2013 18:46:44 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id mb2sm1469931lab.7.2013.01.10.18.46.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 18:46:44 -0800 (PST) Message-ID: <50EF7D13.3080004@gmail.com> Date: Fri, 11 Jan 2013 06:46:43 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , neganov@selectel.ru Subject: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Pumping up detective story: which commit from public repository is the most near to xapi-0.2.src.rpm? Here my lame script to find it: for a in `git log --oneline|head -n 100|awk '{print $1}'`;do git checkout $a 2>/dev/null; echo -n $a ' ';diff -rux .git /github/xcp1.6/xapi-0.2/ . |wc -l;done And here some results: tampa-lcm - 113 lines differ (0a9de3b) tampa - 1k sanibel-lcm - 53k master - 3k cooper - 34k cooper2 - 27k trunk-64bit - 1k clearwater - 113 (c59b8b5) boston - 54k boston-beta - 62k boston-lcm 54k rrdd - 10k catkin - 53k So the smallest difference between legendary and unreachable e92405831b3300f6d2108d7bd0d2c329b4d1e918 is 113 changes. I check git diff 0a9de3b c59b8b5 and found they are the same. Now, diff analysis: ./ocaml/xapi/db_gc.ml 1) indentation 2) indentation 3) indentation 4) indentation 5) Indentation (so, actually, nothing changes, ocaml is not python, spaces does not counted as source code) ./ocaml/xapi/xapi.ml 1) comments out function (src.rpm contains, git code - not) -(* Hack to allow XCP Boston hosts to migrate to XCP Tampa hosts during - an upgrade. If we are in rolling pool upgrade mode, we will add the - key product-version=$PLATFORM_VERSION to the software-version - map. We'll need to start a thread to watch for the pool to leave - upgrade mode, and then remove the key. We should only do this (as - in, add the key and then remove it) if it is not already set by the - inventory file. *) -let boston_tampa_upgrade_hack ~__context = 2) call of that function: (* See above for comment *) - boston_tampa_upgrade_hack ~__context ; Verdict: commit 0a9de3b should be assumed as commit from public available repo witch most close to the content of the source ISO for the XCP 1.6. I'll publish notes on all new commits from that to the head of tampa-lcm. PS I really hate that style 'opensource reverse-engineering'. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 09:21:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 09:21:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtanN-0000My-53; Fri, 11 Jan 2013 09:21:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtanL-0000Mq-N6; Fri, 11 Jan 2013 09:20:59 +0000 Received: from [193.109.254.147:38226] by server-9.bemta-14.messagelabs.com id D8/9B-24482-A79DFE05; Fri, 11 Jan 2013 09:20:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357896058!8480193!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1NjQ0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8533 invoked from network); 11 Jan 2013 09:20:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 09:20:58 -0000 X-IronPort-AV: E=Sophos;i="4.84,451,1355097600"; d="scan'208";a="593321" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Jan 2013 09:20:55 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Fri, 11 Jan 2013 09:20:55 +0000 Message-ID: <1357896054.9456.92.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Rushikesh Jadhav <2rushikeshj@gmail.com> Date: Fri, 11 Jan 2013 09:20:54 +0000 In-Reply-To: References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, 2013-01-10 at 21:37 +0000, Rushikesh Jadhav wrote: > I have also stopped perusing the file and error. Its just bugging me > every hour :( > I'm surprised that this error and file is never reported anywhere and > I don't think my Windows DomU is any special to generate such error. A bit more googling suggests that TXF is Transactional NTFS http://en.wikipedia.org/wiki/Transactional_NTFS Furthermore http://msdn.microsoft.com/en-us/library/cc704588.aspx ("NTSTATUS values") tells me that 0xC01A002B is STATUS_LOG_STATE_INVALID "The log service is not in the correct state to perform a requested action." It might be wise to run the Windows equivalent of fsck. That wiki page suggests that TXF is not widely used, perhaps one of your applications in the VM is one of the minority which do use it? This seems to me like an issue which is internal to the VM but it might still be useful to know the guest configuration. Are you using PV drivers at all? Can you post your guest configuration please. What version of Xen are you running etc. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 09:21:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 09:21:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtanN-0000My-53; Fri, 11 Jan 2013 09:21:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtanL-0000Mq-N6; Fri, 11 Jan 2013 09:20:59 +0000 Received: from [193.109.254.147:38226] by server-9.bemta-14.messagelabs.com id D8/9B-24482-A79DFE05; Fri, 11 Jan 2013 09:20:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1357896058!8480193!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1NjQ0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8533 invoked from network); 11 Jan 2013 09:20:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 09:20:58 -0000 X-IronPort-AV: E=Sophos;i="4.84,451,1355097600"; d="scan'208";a="593321" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Jan 2013 09:20:55 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Fri, 11 Jan 2013 09:20:55 +0000 Message-ID: <1357896054.9456.92.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Rushikesh Jadhav <2rushikeshj@gmail.com> Date: Fri, 11 Jan 2013 09:20:54 +0000 In-Reply-To: References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, 2013-01-10 at 21:37 +0000, Rushikesh Jadhav wrote: > I have also stopped perusing the file and error. Its just bugging me > every hour :( > I'm surprised that this error and file is never reported anywhere and > I don't think my Windows DomU is any special to generate such error. A bit more googling suggests that TXF is Transactional NTFS http://en.wikipedia.org/wiki/Transactional_NTFS Furthermore http://msdn.microsoft.com/en-us/library/cc704588.aspx ("NTSTATUS values") tells me that 0xC01A002B is STATUS_LOG_STATE_INVALID "The log service is not in the correct state to perform a requested action." It might be wise to run the Windows equivalent of fsck. That wiki page suggests that TXF is not widely used, perhaps one of your applications in the VM is one of the minority which do use it? This seems to me like an issue which is internal to the VM but it might still be useful to know the guest configuration. Are you using PV drivers at all? Can you post your guest configuration please. What version of Xen are you running etc. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 10:32:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 10:32:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttbu7-0001pP-Ao; Fri, 11 Jan 2013 10:32:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttbu5-0001pK-LI for xen-api@lists.xen.org; Fri, 11 Jan 2013 10:32:02 +0000 Received: from [85.158.139.83:25201] by server-9.bemta-5.messagelabs.com id 2E/A9-10690-02AEFE05; Fri, 11 Jan 2013 10:32:00 +0000 X-Env-Sender: mpoll@serveisweb.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1357900318!20198422!1 X-Originating-IP: [81.25.112.21] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9846 invoked from network); 11 Jan 2013 10:31:58 -0000 Received: from mail.serveisweb.com (HELO mail.serveisweb.com) (81.25.112.21) by server-11.tower-182.messagelabs.com with SMTP; 11 Jan 2013 10:31:58 -0000 Received: from tecnicos1PC (unknown [81.25.112.245]) (Authenticated sender: mpoll@serveisweb.com) by mail.serveisweb.com (Postfix) with ESMTPA id 626E014BAA7 for ; Fri, 11 Jan 2013 11:31:58 +0100 (CET) From: "marc poll garcia" To: Date: Fri, 11 Jan 2013 11:31:57 +0100 Message-ID: <002f01cdefe6$e1fd1ab0$a5f75010$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac3v5uG/lPoYr3GxQPWIKdSRbNmOfQ== Content-Language: es Subject: [Xen-API] compatibility high performance hardware X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1838152489772892929==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============1838152489772892929== Content-Type: multipart/related; boundary="----=_NextPart_000_0030_01CDEFEF.43C182B0" Content-Language: es This is a multi-part message in MIME format. ------=_NextPart_000_0030_01CDEFEF.43C182B0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0031_01CDEFEF.43C182B0" ------=_NextPart_001_0031_01CDEFEF.43C182B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Compatibility high performance hardware: =20 We want to buy this hardware device, to create a fiber chanel platform: =20 http://www.emulex.com/products/host-bus-adapters/emulex-branded/lightpuls= e-l pe12002/specifications.html http://www.emulex.com/index.php?id=3D14664 =20 It seems that there=92s drivers only for the official XenServer 6.0 and = not for the XCP system(1.6 version). Is it going to work as well??=20 =20 Many thanks!! =20 =20 Marc Poll =C0rea T=E8cnica =96 ServeisWeb =20 http://www.serveisweb.cat =20 http://blog.serveisweb.cat =20 http://www.ticketday.cat =20 Tel. 902 010 664 - Tel. Int. +34 972 010 = 550 Fax 902 510 664 - Fax Int. +34 972 010 = 555 =20 Descripci=F3n: green Abans d'imprimir aquest e-mail, pensi b=E9 si =E9s = necessari fer-ho. AV=CDS LEGAL SW Hosting & Communications Technologies, SL l=92informa que aquest = missatge va dirigit de manera exclusiva al seu destinatari, ja que cont=E9 = informaci=F3 confidencial i/o sensible subjecta al secret professional i protegida = per la legislaci=F3 vigent. Si V=E8. no =E9s el destinatari indicat li = notifiquem que la lectura, utilitzaci=F3, divulgaci=F3, reproducci=F3, distribuci=F3, = impressi=F3 i/o c=F2pia d=92aquesta comunicaci=F3, informaci=F3 i/o qualsevol document = adjunt a la mateixa estan estrictament prohibides per la llei. Si V=E8. ha rebut = aquest missatge per error, li demanem que ens ho comuniqui de manera immediata contestant al remitent d=92aquest missatge i, seguidament, procedeixi a = la seva destrucci=F3 juntament amb qualsevol document adjunt en cas = d=92haver-n=92hi. =20 ------=_NextPart_001_0031_01CDEFEF.43C182B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Compatibility high performance = hardware:

 

We want to buy this hardware device, to create a fiber chanel = platform:

 

http://www.emulex.com/products/ho= st-bus-adapters/emulex-branded/lightpulse-lpe12002/specifications.html

http://www.emulex.com= /index.php?id=3D14664

 

It seems that there’s drivers = only for the official XenServer 6.0 and not for the XCP system(1.6 = version). Is it going to work as well??

 

Many thanks!!

 

 

Marc = Poll

=C0rea = T=E8cnica – ServeisWeb

 <= /o:p>

http://www.serveisweb.cat

http://blog.serveisweb.cat<= /o:p>

http://www.ticketday.cat

Tel. 902 = 010 664 - Tel. Int. +34 972 010 = 550

Fax  = 902 510 664 - Fax Int.  +34 972 010 = 555<= /span>

 

= 3D"Descripci=F3n:=   Abans d'imprimir aquest e-mail, pensi b=E9 si =E9s necessari = fer-ho.

AV=CDS LEGAL

S= W Hosting & Communications Technologies, SL=A0 l’informa que = aquest missatge va dirigit de manera exclusiva al seu destinatari, ja = que cont=E9 informaci=F3 confidencial i/o sensible subjecta al secret = professional i protegida per la legislaci=F3 vigent. Si V=E8. no =E9s el = destinatari indicat li notifiquem que la lectura, utilitzaci=F3, = divulgaci=F3, reproducci=F3, distribuci=F3, impressi=F3 i/o c=F2pia = d’aquesta comunicaci=F3, informaci=F3=A0 i/o qualsevol document = adjunt a la mateixa estan estrictament prohibides per la llei. Si V=E8. = ha rebut aquest missatge per error, li demanem que ens ho comuniqui de = manera immediata contestant al remitent d’aquest missatge i, = seguidament, procedeixi a la seva destrucci=F3 juntament amb qualsevol = document adjunt en cas d’haver-n’hi.<= /span>

 

------=_NextPart_001_0031_01CDEFEF.43C182B0-- ------=_NextPart_000_0030_01CDEFEF.43C182B0 Content-Type: image/gif; name="image001.gif" Content-Transfer-Encoding: base64 Content-ID: R0lGODlhIAAfAIAAAACAAP///yH5BAAAAAAALAAAAAAgAB8AAAJOjI+py73gYgNUWkNzvTJzq0Hf FIpjUnrnkWor6r5Ia670dt7qp8fyLoPVgizco4dszZJIIfN2eSo50lSkGnJggYqtsYu9hsXMaJKn y6UKADs= ------=_NextPart_000_0030_01CDEFEF.43C182B0-- --===============1838152489772892929== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1838152489772892929==-- From xen-api-bounces@lists.xen.org Fri Jan 11 10:32:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 10:32:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttbu7-0001pP-Ao; Fri, 11 Jan 2013 10:32:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttbu5-0001pK-LI for xen-api@lists.xen.org; Fri, 11 Jan 2013 10:32:02 +0000 Received: from [85.158.139.83:25201] by server-9.bemta-5.messagelabs.com id 2E/A9-10690-02AEFE05; Fri, 11 Jan 2013 10:32:00 +0000 X-Env-Sender: mpoll@serveisweb.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1357900318!20198422!1 X-Originating-IP: [81.25.112.21] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9846 invoked from network); 11 Jan 2013 10:31:58 -0000 Received: from mail.serveisweb.com (HELO mail.serveisweb.com) (81.25.112.21) by server-11.tower-182.messagelabs.com with SMTP; 11 Jan 2013 10:31:58 -0000 Received: from tecnicos1PC (unknown [81.25.112.245]) (Authenticated sender: mpoll@serveisweb.com) by mail.serveisweb.com (Postfix) with ESMTPA id 626E014BAA7 for ; Fri, 11 Jan 2013 11:31:58 +0100 (CET) From: "marc poll garcia" To: Date: Fri, 11 Jan 2013 11:31:57 +0100 Message-ID: <002f01cdefe6$e1fd1ab0$a5f75010$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac3v5uG/lPoYr3GxQPWIKdSRbNmOfQ== Content-Language: es Subject: [Xen-API] compatibility high performance hardware X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1838152489772892929==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============1838152489772892929== Content-Type: multipart/related; boundary="----=_NextPart_000_0030_01CDEFEF.43C182B0" Content-Language: es This is a multi-part message in MIME format. ------=_NextPart_000_0030_01CDEFEF.43C182B0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0031_01CDEFEF.43C182B0" ------=_NextPart_001_0031_01CDEFEF.43C182B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Compatibility high performance hardware: =20 We want to buy this hardware device, to create a fiber chanel platform: =20 http://www.emulex.com/products/host-bus-adapters/emulex-branded/lightpuls= e-l pe12002/specifications.html http://www.emulex.com/index.php?id=3D14664 =20 It seems that there=92s drivers only for the official XenServer 6.0 and = not for the XCP system(1.6 version). Is it going to work as well??=20 =20 Many thanks!! =20 =20 Marc Poll =C0rea T=E8cnica =96 ServeisWeb =20 http://www.serveisweb.cat =20 http://blog.serveisweb.cat =20 http://www.ticketday.cat =20 Tel. 902 010 664 - Tel. Int. +34 972 010 = 550 Fax 902 510 664 - Fax Int. +34 972 010 = 555 =20 Descripci=F3n: green Abans d'imprimir aquest e-mail, pensi b=E9 si =E9s = necessari fer-ho. AV=CDS LEGAL SW Hosting & Communications Technologies, SL l=92informa que aquest = missatge va dirigit de manera exclusiva al seu destinatari, ja que cont=E9 = informaci=F3 confidencial i/o sensible subjecta al secret professional i protegida = per la legislaci=F3 vigent. Si V=E8. no =E9s el destinatari indicat li = notifiquem que la lectura, utilitzaci=F3, divulgaci=F3, reproducci=F3, distribuci=F3, = impressi=F3 i/o c=F2pia d=92aquesta comunicaci=F3, informaci=F3 i/o qualsevol document = adjunt a la mateixa estan estrictament prohibides per la llei. Si V=E8. ha rebut = aquest missatge per error, li demanem que ens ho comuniqui de manera immediata contestant al remitent d=92aquest missatge i, seguidament, procedeixi a = la seva destrucci=F3 juntament amb qualsevol document adjunt en cas = d=92haver-n=92hi. =20 ------=_NextPart_001_0031_01CDEFEF.43C182B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Compatibility high performance = hardware:

 

We want to buy this hardware device, to create a fiber chanel = platform:

 

http://www.emulex.com/products/ho= st-bus-adapters/emulex-branded/lightpulse-lpe12002/specifications.html

http://www.emulex.com= /index.php?id=3D14664

 

It seems that there’s drivers = only for the official XenServer 6.0 and not for the XCP system(1.6 = version). Is it going to work as well??

 

Many thanks!!

 

 

Marc = Poll

=C0rea = T=E8cnica – ServeisWeb

 <= /o:p>

http://www.serveisweb.cat

http://blog.serveisweb.cat<= /o:p>

http://www.ticketday.cat

Tel. 902 = 010 664 - Tel. Int. +34 972 010 = 550

Fax  = 902 510 664 - Fax Int.  +34 972 010 = 555<= /span>

 

= 3D"Descripci=F3n:=   Abans d'imprimir aquest e-mail, pensi b=E9 si =E9s necessari = fer-ho.

AV=CDS LEGAL

S= W Hosting & Communications Technologies, SL=A0 l’informa que = aquest missatge va dirigit de manera exclusiva al seu destinatari, ja = que cont=E9 informaci=F3 confidencial i/o sensible subjecta al secret = professional i protegida per la legislaci=F3 vigent. Si V=E8. no =E9s el = destinatari indicat li notifiquem que la lectura, utilitzaci=F3, = divulgaci=F3, reproducci=F3, distribuci=F3, impressi=F3 i/o c=F2pia = d’aquesta comunicaci=F3, informaci=F3=A0 i/o qualsevol document = adjunt a la mateixa estan estrictament prohibides per la llei. Si V=E8. = ha rebut aquest missatge per error, li demanem que ens ho comuniqui de = manera immediata contestant al remitent d’aquest missatge i, = seguidament, procedeixi a la seva destrucci=F3 juntament amb qualsevol = document adjunt en cas d’haver-n’hi.<= /span>

 

------=_NextPart_001_0031_01CDEFEF.43C182B0-- ------=_NextPart_000_0030_01CDEFEF.43C182B0 Content-Type: image/gif; name="image001.gif" Content-Transfer-Encoding: base64 Content-ID: R0lGODlhIAAfAIAAAACAAP///yH5BAAAAAAALAAAAAAgAB8AAAJOjI+py73gYgNUWkNzvTJzq0Hf FIpjUnrnkWor6r5Ia670dt7qp8fyLoPVgizco4dszZJIIfN2eSo50lSkGnJggYqtsYu9hsXMaJKn y6UKADs= ------=_NextPart_000_0030_01CDEFEF.43C182B0-- --===============1838152489772892929== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1838152489772892929==-- From xen-api-bounces@lists.xen.org Fri Jan 11 12:58:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 12:58:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TteC1-00081o-GX; Fri, 11 Jan 2013 12:58:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TteC0-00081X-0L for xen-api@lists.xen.org; Fri, 11 Jan 2013 12:58:40 +0000 Received: from [85.158.139.83:6179] by server-9.bemta-5.messagelabs.com id FB/03-10690-F7C00F05; Fri, 11 Jan 2013 12:58:39 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1357909118!26914571!1 X-Originating-IP: [207.126.144.139] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21130 invoked from network); 11 Jan 2013 12:58:38 -0000 Received: from eu1sys200aog115.obsmtp.com (HELO eu1sys200aog115.obsmtp.com) (207.126.144.139) by server-13.tower-182.messagelabs.com with SMTP; 11 Jan 2013 12:58:38 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob115.postini.com ([207.126.147.11]) with SMTP ID DSNKUPAMftUrFxqBY+aGugFmJn4J7BdX1mR1@postini.com; Fri, 11 Jan 2013 12:58:38 UTC Received: from lonwexhtca01.uk.futurenet.com (lonwexhtca01.uk.futurenet.com [172.23.130.5]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 163F27F448F; Fri, 11 Jan 2013 12:58:38 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by lonwexhtca01.uk.futurenet.com ([172.23.130.5]) with mapi; Fri, 11 Jan 2013 12:58:37 +0000 From: Dave Avent To: George Shuklin Date: Fri, 11 Jan 2013 12:58:37 +0000 Thread-Topic: [Xen-API] VM Migration Bug? Thread-Index: Ac3v+178NzrDLvnxTwyiX0f91DTJYw== Message-ID: <7C4029AA-8291-4380-AE83-DA1810B5CCCE@futurenet.com> References: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> <50EF5154.5050103@gmail.com> In-Reply-To: <50EF5154.5050103@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org DQpTb21lIG1vcmUgaW5mbzoNCg0KSSBoYXZlIHRyYWNrZWQgdGhpcyBkb3duIHRvIFZNJ3MgY3Jl YXRlZCB1c2luZyB0aGUgQVBJIChpbiBteSBjYXNlIHVzaW5nIHRoZSBSdWJ5IEZvZyBsaWJyYXJp ZXMpLiBJIGFtIGFzc3VtaW5nIHRoYXQgdGhlc2UgbGlicmFyaWVzIGFyZSBnb2luZyBzb21ldGhp bmcgaW5jb3JyZWN0bHkgYnV0IEkgY2Fubm90IGZpZ3VyZSBvdXQgZXhhY3RseSB3aGF0IFhDUCBo YXMgaXNzdWVzIHdpdGguDQoNClRvIGFuc3dlciB5b3VyIHF1ZXN0aW9ucyB0aGV5IGFyZSBzZXBh cmF0ZSBob3N0cyBub3QgaW4gYSBwb29sLg0KDQpUaGUgcmVsZXZhbnQgbG9nIGVudHJpZXMgYXJl IGhlcmU6IGh0dHBzOi8vZ2lzdC5naXRodWIuY29tLzQ1MTA0NDENCg0KVGhhbmtzLA0KDQpEYXZl DQoNCk9uIDEwIEphbiAyMDEzLCBhdCAyMzo0MCwgR2VvcmdlIFNodWtsaW4gd3JvdGU6DQoNCj4g QXJlIHRob3NlIGhvc3RzIGluIHNhbWUgcG9vbCBvciBpbiBzZXBhcmF0ZSBwb29scz8gSWYgc2Ft ZSBwb29sLCBzaGFyZWQgDQo+IFNSIG9yIGxvY2FsPyBBbnl3YXksIGRldGFpbHMgc2hvdWxkIGJl IGluIC92YXIvbG9nL3hlbnNvdXJjZS5sb2cgKHRvbyANCj4gbXVjaCBkZXRhaWxzLCBhY3R1YWxs eSkuDQo+IA0KPiANCj4gMTAuMDEuMjAxMyAxNDo0OSwgRGF2ZSBBdmVudCDQv9C40YjQtdGCOg0K Pj4gSSBhbSBoYXZpbmcgaXNzdWVzIHdpdGggbWlncmF0aW5nIFZNcyBiZXR3ZWVuIGhvc3RzLiBI ZXJlIGlzIGhvdyBJIGNhbiByZXByb2R1Y2UgdGhlIHByb2JsZW06DQo+PiANCj4+IDEpIENyZWF0 ZSAyIG5ldyBWTSdzICh1c2luZyBlaXRoZXIgYSBmcmVzaCBpbnN0YWxsIGZyb20gTmV0IEluc3Rh bGwgb2YgRGViaWFuIG9yIGZyb20gYSAiR29sZGVuIEltYWdlIiBvZiBhIFZNIHByZXZpb3VzbHkg Y29udmVydGVkIHRvIGEgVGVtcGxhdGUpDQo+PiANCj4+IDIpIE1pZ3JhdGUgb25lIG9mIHRoZSBW TXMgdG8gYW5vdGhlciBob3N0cw0KPj4gDQo+PiAzKSBBdHRlbXB0IHRvIG1pZ3JhdGUgdGhlIHNh bWUgVk0gYmFjayB0byB0aGUgb3JpZ2luYWwgaG9zdCBob3dldmVyIGl0IHJlZnVzZXMgYW5kIHRo cm93czoNCj4+IA0KPj4gQ2Fubm90IHJlc3RvcmUgdGhpcyBWTSBiZWNhdXNlIGl0IHdvdWxkIGNy ZWF0ZSBhIGR1cGxpY2F0ZQ0KPj4gdm06IE9wYXF1ZVJlZjo3MTFmMjJmMy05ZTM1LWIxM2UtMWMz NS01OGU4YTU3OGNhMGUNCj4+IA0KPj4gV2hhdCBleGFjdGx5IGRvZXMgaXQgdGhpbmsgaXMgYmVp bmcgZHVwbGljYXRlZD8gTm9uZSBvZiB0aGUgb3JpZ2luYWwgYXNzZXRzIGFwcGVhciB0byBoYXZl IGJlZW4gbGVmdCBiZWhpbmQgKGZhaWxlZCB0byBiZSBkZWxldGVkIGV0YykuIEkgY2FuJ3Qgc2Vl IHdoeSB0aGlzIGlzIGZhaWxpbmcuDQo+PiANCj4+IEFueSBpZGVhcz8NCj4+IA0KPiANCj4gDQo+ IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IFhlbi1h cGkgbWFpbGluZyBsaXN0DQo+IFhlbi1hcGlAbGlzdHMueGVuLm9yZw0KPiBodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQ0KDQoNCi0tIA0KRnV0dXJl IFB1Ymxpc2hpbmcgTGltaXRlZCAocmVnaXN0ZXJlZCBjb21wYW55IG51bWJlciAyMDA4ODg1KSBp cyBhIHdob2xseSBvd25lZCBzdWJzaWRpYXJ5IG9mIEZ1dHVyZSBwbGMgKHJlZ2lzdGVyZWQgY29t cGFueSBudW1iZXIgMzc1Nzg3NCksIGJvdGggb2Ygd2hpY2ggYXJlIGluY29ycG9yYXRlZCBpbiBF bmdsYW5kIGFuZCBXYWxlcyBhbmQgc2hhcmUgdGhlIHNhbWUgcmVnaXN0ZXJlZCBhZGRyZXNzIGF0 IEJlYXVmb3JkIENvdXJ0LCAzMCBNb25tb3V0aCBTdHJlZXQsIEJhdGggQkExIDJCVy4NCg0KVGhp cyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJlIGNvbmZpZGVudGlh bCBhbmQgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVu dGl0eSB0byB3aGljaCB0aGV5IGFyZSBhZGRyZXNzZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRo aXMgZW1haWwgaW4gZXJyb3IgcGxlYXNlIHJlcGx5IHRvIHRoaXMgZW1haWwgYW5kIHRoZW4gZGVs ZXRlIGl0LiBQbGVhc2Ugbm90ZSB0aGF0IGFueSB2aWV3cyBvciBvcGluaW9ucyBwcmVzZW50ZWQg aW4gdGhpcyBlbWFpbCBhcmUgc29sZWx5IHRob3NlIG9mIHRoZSBhdXRob3IgYW5kIGRvIG5vdCBu ZWNlc3NhcmlseSByZXByZXNlbnQgdGhvc2Ugb2YgRnV0dXJlLg0KDQpUaGUgcmVjaXBpZW50IHNo b3VsZCBjaGVjayB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgZm9yIHRoZSBwcmVzZW5j ZSBvZiB2aXJ1c2VzLiBGdXR1cmUgYWNjZXB0cyBubyBsaWFiaWxpdHkgZm9yIGFueSBkYW1hZ2Ug Y2F1c2VkIGJ5IGFueSB2aXJ1cyB0cmFuc21pdHRlZCBieSB0aGlzIGVtYWlsLg0KDQpGdXR1cmUg bWF5IHJlZ3VsYXJseSBhbmQgcmFuZG9tbHkgbW9uaXRvciBvdXRnb2luZyBhbmQgaW5jb21pbmcg ZW1haWxzIGFuZCBvdGhlciB0ZWxlY29tbXVuaWNhdGlvbnMgb24gaXRzIGVtYWlsIGFuZCB0ZWxl Y29tbXVuaWNhdGlvbnMgc3lzdGVtcy4gQnkgcmVwbHlpbmcgdG8gdGhpcyBlbWFpbCB5b3UgZ2l2 ZSB5b3VyIGNvbnNlbnQgdG8gc3VjaCBtb25pdG9yaW5nLg0KDQoqKioqKg0KU2F2ZSByZXNvdXJj ZXM6IHRoaW5rIGJlZm9yZSB5b3UgcHJpbnQuDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMu eGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVu LWFwaQo= From xen-api-bounces@lists.xen.org Fri Jan 11 12:58:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 12:58:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TteC1-00081o-GX; Fri, 11 Jan 2013 12:58:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TteC0-00081X-0L for xen-api@lists.xen.org; Fri, 11 Jan 2013 12:58:40 +0000 Received: from [85.158.139.83:6179] by server-9.bemta-5.messagelabs.com id FB/03-10690-F7C00F05; Fri, 11 Jan 2013 12:58:39 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1357909118!26914571!1 X-Originating-IP: [207.126.144.139] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21130 invoked from network); 11 Jan 2013 12:58:38 -0000 Received: from eu1sys200aog115.obsmtp.com (HELO eu1sys200aog115.obsmtp.com) (207.126.144.139) by server-13.tower-182.messagelabs.com with SMTP; 11 Jan 2013 12:58:38 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob115.postini.com ([207.126.147.11]) with SMTP ID DSNKUPAMftUrFxqBY+aGugFmJn4J7BdX1mR1@postini.com; Fri, 11 Jan 2013 12:58:38 UTC Received: from lonwexhtca01.uk.futurenet.com (lonwexhtca01.uk.futurenet.com [172.23.130.5]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 163F27F448F; Fri, 11 Jan 2013 12:58:38 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by lonwexhtca01.uk.futurenet.com ([172.23.130.5]) with mapi; Fri, 11 Jan 2013 12:58:37 +0000 From: Dave Avent To: George Shuklin Date: Fri, 11 Jan 2013 12:58:37 +0000 Thread-Topic: [Xen-API] VM Migration Bug? Thread-Index: Ac3v+178NzrDLvnxTwyiX0f91DTJYw== Message-ID: <7C4029AA-8291-4380-AE83-DA1810B5CCCE@futurenet.com> References: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> <50EF5154.5050103@gmail.com> In-Reply-To: <50EF5154.5050103@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org DQpTb21lIG1vcmUgaW5mbzoNCg0KSSBoYXZlIHRyYWNrZWQgdGhpcyBkb3duIHRvIFZNJ3MgY3Jl YXRlZCB1c2luZyB0aGUgQVBJIChpbiBteSBjYXNlIHVzaW5nIHRoZSBSdWJ5IEZvZyBsaWJyYXJp ZXMpLiBJIGFtIGFzc3VtaW5nIHRoYXQgdGhlc2UgbGlicmFyaWVzIGFyZSBnb2luZyBzb21ldGhp bmcgaW5jb3JyZWN0bHkgYnV0IEkgY2Fubm90IGZpZ3VyZSBvdXQgZXhhY3RseSB3aGF0IFhDUCBo YXMgaXNzdWVzIHdpdGguDQoNClRvIGFuc3dlciB5b3VyIHF1ZXN0aW9ucyB0aGV5IGFyZSBzZXBh cmF0ZSBob3N0cyBub3QgaW4gYSBwb29sLg0KDQpUaGUgcmVsZXZhbnQgbG9nIGVudHJpZXMgYXJl IGhlcmU6IGh0dHBzOi8vZ2lzdC5naXRodWIuY29tLzQ1MTA0NDENCg0KVGhhbmtzLA0KDQpEYXZl DQoNCk9uIDEwIEphbiAyMDEzLCBhdCAyMzo0MCwgR2VvcmdlIFNodWtsaW4gd3JvdGU6DQoNCj4g QXJlIHRob3NlIGhvc3RzIGluIHNhbWUgcG9vbCBvciBpbiBzZXBhcmF0ZSBwb29scz8gSWYgc2Ft ZSBwb29sLCBzaGFyZWQgDQo+IFNSIG9yIGxvY2FsPyBBbnl3YXksIGRldGFpbHMgc2hvdWxkIGJl IGluIC92YXIvbG9nL3hlbnNvdXJjZS5sb2cgKHRvbyANCj4gbXVjaCBkZXRhaWxzLCBhY3R1YWxs eSkuDQo+IA0KPiANCj4gMTAuMDEuMjAxMyAxNDo0OSwgRGF2ZSBBdmVudCDQv9C40YjQtdGCOg0K Pj4gSSBhbSBoYXZpbmcgaXNzdWVzIHdpdGggbWlncmF0aW5nIFZNcyBiZXR3ZWVuIGhvc3RzLiBI ZXJlIGlzIGhvdyBJIGNhbiByZXByb2R1Y2UgdGhlIHByb2JsZW06DQo+PiANCj4+IDEpIENyZWF0 ZSAyIG5ldyBWTSdzICh1c2luZyBlaXRoZXIgYSBmcmVzaCBpbnN0YWxsIGZyb20gTmV0IEluc3Rh bGwgb2YgRGViaWFuIG9yIGZyb20gYSAiR29sZGVuIEltYWdlIiBvZiBhIFZNIHByZXZpb3VzbHkg Y29udmVydGVkIHRvIGEgVGVtcGxhdGUpDQo+PiANCj4+IDIpIE1pZ3JhdGUgb25lIG9mIHRoZSBW TXMgdG8gYW5vdGhlciBob3N0cw0KPj4gDQo+PiAzKSBBdHRlbXB0IHRvIG1pZ3JhdGUgdGhlIHNh bWUgVk0gYmFjayB0byB0aGUgb3JpZ2luYWwgaG9zdCBob3dldmVyIGl0IHJlZnVzZXMgYW5kIHRo cm93czoNCj4+IA0KPj4gQ2Fubm90IHJlc3RvcmUgdGhpcyBWTSBiZWNhdXNlIGl0IHdvdWxkIGNy ZWF0ZSBhIGR1cGxpY2F0ZQ0KPj4gdm06IE9wYXF1ZVJlZjo3MTFmMjJmMy05ZTM1LWIxM2UtMWMz NS01OGU4YTU3OGNhMGUNCj4+IA0KPj4gV2hhdCBleGFjdGx5IGRvZXMgaXQgdGhpbmsgaXMgYmVp bmcgZHVwbGljYXRlZD8gTm9uZSBvZiB0aGUgb3JpZ2luYWwgYXNzZXRzIGFwcGVhciB0byBoYXZl IGJlZW4gbGVmdCBiZWhpbmQgKGZhaWxlZCB0byBiZSBkZWxldGVkIGV0YykuIEkgY2FuJ3Qgc2Vl IHdoeSB0aGlzIGlzIGZhaWxpbmcuDQo+PiANCj4+IEFueSBpZGVhcz8NCj4+IA0KPiANCj4gDQo+ IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IFhlbi1h cGkgbWFpbGluZyBsaXN0DQo+IFhlbi1hcGlAbGlzdHMueGVuLm9yZw0KPiBodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQ0KDQoNCi0tIA0KRnV0dXJl IFB1Ymxpc2hpbmcgTGltaXRlZCAocmVnaXN0ZXJlZCBjb21wYW55IG51bWJlciAyMDA4ODg1KSBp cyBhIHdob2xseSBvd25lZCBzdWJzaWRpYXJ5IG9mIEZ1dHVyZSBwbGMgKHJlZ2lzdGVyZWQgY29t cGFueSBudW1iZXIgMzc1Nzg3NCksIGJvdGggb2Ygd2hpY2ggYXJlIGluY29ycG9yYXRlZCBpbiBF bmdsYW5kIGFuZCBXYWxlcyBhbmQgc2hhcmUgdGhlIHNhbWUgcmVnaXN0ZXJlZCBhZGRyZXNzIGF0 IEJlYXVmb3JkIENvdXJ0LCAzMCBNb25tb3V0aCBTdHJlZXQsIEJhdGggQkExIDJCVy4NCg0KVGhp cyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJlIGNvbmZpZGVudGlh bCBhbmQgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVu dGl0eSB0byB3aGljaCB0aGV5IGFyZSBhZGRyZXNzZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRo aXMgZW1haWwgaW4gZXJyb3IgcGxlYXNlIHJlcGx5IHRvIHRoaXMgZW1haWwgYW5kIHRoZW4gZGVs ZXRlIGl0LiBQbGVhc2Ugbm90ZSB0aGF0IGFueSB2aWV3cyBvciBvcGluaW9ucyBwcmVzZW50ZWQg aW4gdGhpcyBlbWFpbCBhcmUgc29sZWx5IHRob3NlIG9mIHRoZSBhdXRob3IgYW5kIGRvIG5vdCBu ZWNlc3NhcmlseSByZXByZXNlbnQgdGhvc2Ugb2YgRnV0dXJlLg0KDQpUaGUgcmVjaXBpZW50IHNo b3VsZCBjaGVjayB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgZm9yIHRoZSBwcmVzZW5j ZSBvZiB2aXJ1c2VzLiBGdXR1cmUgYWNjZXB0cyBubyBsaWFiaWxpdHkgZm9yIGFueSBkYW1hZ2Ug Y2F1c2VkIGJ5IGFueSB2aXJ1cyB0cmFuc21pdHRlZCBieSB0aGlzIGVtYWlsLg0KDQpGdXR1cmUg bWF5IHJlZ3VsYXJseSBhbmQgcmFuZG9tbHkgbW9uaXRvciBvdXRnb2luZyBhbmQgaW5jb21pbmcg ZW1haWxzIGFuZCBvdGhlciB0ZWxlY29tbXVuaWNhdGlvbnMgb24gaXRzIGVtYWlsIGFuZCB0ZWxl Y29tbXVuaWNhdGlvbnMgc3lzdGVtcy4gQnkgcmVwbHlpbmcgdG8gdGhpcyBlbWFpbCB5b3UgZ2l2 ZSB5b3VyIGNvbnNlbnQgdG8gc3VjaCBtb25pdG9yaW5nLg0KDQoqKioqKg0KU2F2ZSByZXNvdXJj ZXM6IHRoaW5rIGJlZm9yZSB5b3UgcHJpbnQuDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMu eGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVu LWFwaQo= From xen-api-bounces@lists.xen.org Fri Jan 11 13:33:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 13:33:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttejq-0001Ul-Sz; Fri, 11 Jan 2013 13:33:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttejp-0001UU-IB for xen-api@lists.xen.org; Fri, 11 Jan 2013 13:33:37 +0000 Received: from [85.158.139.211:52028] by server-13.bemta-5.messagelabs.com id DE/93-10716-0B410F05; Fri, 11 Jan 2013 13:33:36 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1357911215!18718488!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6145 invoked from network); 11 Jan 2013 13:33:36 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 13:33:36 -0000 Received: by mail-lb0-f180.google.com with SMTP id gj3so1290283lbb.25 for ; Fri, 11 Jan 2013 05:33:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Jm3+wmvqMKwEd3TPY5pQPxVfg3ahDXe0hVDqNnb4w/Y=; b=fio7QuzHKlENC/ANvnjTbpBxYznBLyiUvNk7tNmwI98u49DU57vETAP2w/7Mrz1rjc 5dgAYDe9lycToxQiVHDc1Xw4g/CHVoeDJUaYc2yBIu84og9yl5X8vzOKqzLejErgjlPb FbbNnca4lC2PL8AnE2bUV9gkvEwwlh5cUgeoK4hKdK2bZiKQMJmEhC4zMfB+4/JO5gDw sbfhibTO411cJTr/eqLSIAtmeubZNm0bdwoXrV477HxqNuUdtIKI0Yv2EEPtZ89xbtyw 9lbe2rzKtwASr8Ch4YE/FT881tB8BOPrxQkIiVaM43SaAWx9YkPKr5DFNR72u1AezNFJ aelA== X-Received: by 10.152.108.172 with SMTP id hl12mr72487818lab.32.1357911215296; Fri, 11 Jan 2013 05:33:35 -0800 (PST) Received: from [192.168.10.33] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id u5sm2134828lbm.8.2013.01.11.05.33.34 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Jan 2013 05:33:34 -0800 (PST) Message-ID: <50F014A8.6000505@gmail.com> Date: Fri, 11 Jan 2013 17:33:28 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: Dave Avent References: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> <50EF5154.5050103@gmail.com> <7C4029AA-8291-4380-AE83-DA1810B5CCCE@futurenet.com> In-Reply-To: <7C4029AA-8291-4380-AE83-DA1810B5CCCE@futurenet.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T2gsIHNlZW1zIGxpa2UgeW91IGdvdCBhIGR1cGxpY2F0ZSBkb21haW4gb24gc29tZSBob3N0LiBD aGVjayAobWFudWFsbHkgCnRoYXQgdGhhdCBkb21haW4gaXMgbm90IHJ1bm5pbmcgb24gdGFyZ2V0 IGhvc3QgKG9yIGFueSBob3N0IGluIHRhcmdldCdzIApwb29sKSwgbGlzdF9kb21haW5zKS4gQW5k IGNoZWNrIHRoYXQgdm0gaXMgcmVtb3ZlZCBmcm9tIHRhcmdldCBwb29sIChubyAKeGUgdm0tbGlz dCB1dWlkPS4uLiBlbnRyeSkuIElmIHNvbWUgY29ycmVjdGlvbiB3YXMgbWFkZSAoZi5lLiBzdHJh eSAKZG9tYWluIGtpbGxlZCksIHhhcGkgc2VydmljZSByZXN0YXJ0IG1heSBiZSBuZWVkIG9uIGV2 ZXJ5IGhvc3QgaW4gCnRhcmdldCdzIHBvb2wuCgoKMTEuMDEuMjAxMyAxNjo1OCwgRGF2ZSBBdmVu dCDQv9C40YjQtdGCOgo+IFNvbWUgbW9yZSBpbmZvOgo+Cj4gSSBoYXZlIHRyYWNrZWQgdGhpcyBk b3duIHRvIFZNJ3MgY3JlYXRlZCB1c2luZyB0aGUgQVBJIChpbiBteSBjYXNlIHVzaW5nIHRoZSBS dWJ5IEZvZyBsaWJyYXJpZXMpLiBJIGFtIGFzc3VtaW5nIHRoYXQgdGhlc2UgbGlicmFyaWVzIGFy ZSBnb2luZyBzb21ldGhpbmcgaW5jb3JyZWN0bHkgYnV0IEkgY2Fubm90IGZpZ3VyZSBvdXQgZXhh Y3RseSB3aGF0IFhDUCBoYXMgaXNzdWVzIHdpdGguCj4KPiBUbyBhbnN3ZXIgeW91ciBxdWVzdGlv bnMgdGhleSBhcmUgc2VwYXJhdGUgaG9zdHMgbm90IGluIGEgcG9vbC4KPgo+IFRoZSByZWxldmFu dCBsb2cgZW50cmllcyBhcmUgaGVyZTogaHR0cHM6Ly9naXN0LmdpdGh1Yi5jb20vNDUxMDQ0MQo+ Cj4gVGhhbmtzLAo+Cj4gRGF2ZQo+Cj4gT24gMTAgSmFuIDIwMTMsIGF0IDIzOjQwLCBHZW9yZ2Ug U2h1a2xpbiB3cm90ZToKPgo+PiBBcmUgdGhvc2UgaG9zdHMgaW4gc2FtZSBwb29sIG9yIGluIHNl cGFyYXRlIHBvb2xzPyBJZiBzYW1lIHBvb2wsIHNoYXJlZAo+PiBTUiBvciBsb2NhbD8gQW55d2F5 LCBkZXRhaWxzIHNob3VsZCBiZSBpbiAvdmFyL2xvZy94ZW5zb3VyY2UubG9nICh0b28KPj4gbXVj aCBkZXRhaWxzLCBhY3R1YWxseSkuCj4+Cj4+Cj4+IDEwLjAxLjIwMTMgMTQ6NDksIERhdmUgQXZl bnQg0L/QuNGI0LXRgjoKPj4+IEkgYW0gaGF2aW5nIGlzc3VlcyB3aXRoIG1pZ3JhdGluZyBWTXMg YmV0d2VlbiBob3N0cy4gSGVyZSBpcyBob3cgSSBjYW4gcmVwcm9kdWNlIHRoZSBwcm9ibGVtOgo+ Pj4KPj4+IDEpIENyZWF0ZSAyIG5ldyBWTSdzICh1c2luZyBlaXRoZXIgYSBmcmVzaCBpbnN0YWxs IGZyb20gTmV0IEluc3RhbGwgb2YgRGViaWFuIG9yIGZyb20gYSAiR29sZGVuIEltYWdlIiBvZiBh IFZNIHByZXZpb3VzbHkgY29udmVydGVkIHRvIGEgVGVtcGxhdGUpCj4+Pgo+Pj4gMikgTWlncmF0 ZSBvbmUgb2YgdGhlIFZNcyB0byBhbm90aGVyIGhvc3RzCj4+Pgo+Pj4gMykgQXR0ZW1wdCB0byBt aWdyYXRlIHRoZSBzYW1lIFZNIGJhY2sgdG8gdGhlIG9yaWdpbmFsIGhvc3QgaG93ZXZlciBpdCBy ZWZ1c2VzIGFuZCB0aHJvd3M6Cj4+Pgo+Pj4gQ2Fubm90IHJlc3RvcmUgdGhpcyBWTSBiZWNhdXNl IGl0IHdvdWxkIGNyZWF0ZSBhIGR1cGxpY2F0ZQo+Pj4gdm06IE9wYXF1ZVJlZjo3MTFmMjJmMy05 ZTM1LWIxM2UtMWMzNS01OGU4YTU3OGNhMGUKPj4+Cj4+PiBXaGF0IGV4YWN0bHkgZG9lcyBpdCB0 aGluayBpcyBiZWluZyBkdXBsaWNhdGVkPyBOb25lIG9mIHRoZSBvcmlnaW5hbCBhc3NldHMgYXBw ZWFyIHRvIGhhdmUgYmVlbiBsZWZ0IGJlaGluZCAoZmFpbGVkIHRvIGJlIGRlbGV0ZWQgZXRjKS4g SSBjYW4ndCBzZWUgd2h5IHRoaXMgaXMgZmFpbGluZy4KPj4+Cj4+PiBBbnkgaWRlYXM/Cj4+Pgo+ Pgo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+PiBY ZW4tYXBpIG1haWxpbmcgbGlzdAo+PiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPj4gaHR0cDovL2xp c3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKPgoKCl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBs aXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21h aWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Fri Jan 11 13:33:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 13:33:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttejq-0001Ul-Sz; Fri, 11 Jan 2013 13:33:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttejp-0001UU-IB for xen-api@lists.xen.org; Fri, 11 Jan 2013 13:33:37 +0000 Received: from [85.158.139.211:52028] by server-13.bemta-5.messagelabs.com id DE/93-10716-0B410F05; Fri, 11 Jan 2013 13:33:36 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1357911215!18718488!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6145 invoked from network); 11 Jan 2013 13:33:36 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 13:33:36 -0000 Received: by mail-lb0-f180.google.com with SMTP id gj3so1290283lbb.25 for ; Fri, 11 Jan 2013 05:33:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Jm3+wmvqMKwEd3TPY5pQPxVfg3ahDXe0hVDqNnb4w/Y=; b=fio7QuzHKlENC/ANvnjTbpBxYznBLyiUvNk7tNmwI98u49DU57vETAP2w/7Mrz1rjc 5dgAYDe9lycToxQiVHDc1Xw4g/CHVoeDJUaYc2yBIu84og9yl5X8vzOKqzLejErgjlPb FbbNnca4lC2PL8AnE2bUV9gkvEwwlh5cUgeoK4hKdK2bZiKQMJmEhC4zMfB+4/JO5gDw sbfhibTO411cJTr/eqLSIAtmeubZNm0bdwoXrV477HxqNuUdtIKI0Yv2EEPtZ89xbtyw 9lbe2rzKtwASr8Ch4YE/FT881tB8BOPrxQkIiVaM43SaAWx9YkPKr5DFNR72u1AezNFJ aelA== X-Received: by 10.152.108.172 with SMTP id hl12mr72487818lab.32.1357911215296; Fri, 11 Jan 2013 05:33:35 -0800 (PST) Received: from [192.168.10.33] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id u5sm2134828lbm.8.2013.01.11.05.33.34 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Jan 2013 05:33:34 -0800 (PST) Message-ID: <50F014A8.6000505@gmail.com> Date: Fri, 11 Jan 2013 17:33:28 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: Dave Avent References: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> <50EF5154.5050103@gmail.com> <7C4029AA-8291-4380-AE83-DA1810B5CCCE@futurenet.com> In-Reply-To: <7C4029AA-8291-4380-AE83-DA1810B5CCCE@futurenet.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T2gsIHNlZW1zIGxpa2UgeW91IGdvdCBhIGR1cGxpY2F0ZSBkb21haW4gb24gc29tZSBob3N0LiBD aGVjayAobWFudWFsbHkgCnRoYXQgdGhhdCBkb21haW4gaXMgbm90IHJ1bm5pbmcgb24gdGFyZ2V0 IGhvc3QgKG9yIGFueSBob3N0IGluIHRhcmdldCdzIApwb29sKSwgbGlzdF9kb21haW5zKS4gQW5k IGNoZWNrIHRoYXQgdm0gaXMgcmVtb3ZlZCBmcm9tIHRhcmdldCBwb29sIChubyAKeGUgdm0tbGlz dCB1dWlkPS4uLiBlbnRyeSkuIElmIHNvbWUgY29ycmVjdGlvbiB3YXMgbWFkZSAoZi5lLiBzdHJh eSAKZG9tYWluIGtpbGxlZCksIHhhcGkgc2VydmljZSByZXN0YXJ0IG1heSBiZSBuZWVkIG9uIGV2 ZXJ5IGhvc3QgaW4gCnRhcmdldCdzIHBvb2wuCgoKMTEuMDEuMjAxMyAxNjo1OCwgRGF2ZSBBdmVu dCDQv9C40YjQtdGCOgo+IFNvbWUgbW9yZSBpbmZvOgo+Cj4gSSBoYXZlIHRyYWNrZWQgdGhpcyBk b3duIHRvIFZNJ3MgY3JlYXRlZCB1c2luZyB0aGUgQVBJIChpbiBteSBjYXNlIHVzaW5nIHRoZSBS dWJ5IEZvZyBsaWJyYXJpZXMpLiBJIGFtIGFzc3VtaW5nIHRoYXQgdGhlc2UgbGlicmFyaWVzIGFy ZSBnb2luZyBzb21ldGhpbmcgaW5jb3JyZWN0bHkgYnV0IEkgY2Fubm90IGZpZ3VyZSBvdXQgZXhh Y3RseSB3aGF0IFhDUCBoYXMgaXNzdWVzIHdpdGguCj4KPiBUbyBhbnN3ZXIgeW91ciBxdWVzdGlv bnMgdGhleSBhcmUgc2VwYXJhdGUgaG9zdHMgbm90IGluIGEgcG9vbC4KPgo+IFRoZSByZWxldmFu dCBsb2cgZW50cmllcyBhcmUgaGVyZTogaHR0cHM6Ly9naXN0LmdpdGh1Yi5jb20vNDUxMDQ0MQo+ Cj4gVGhhbmtzLAo+Cj4gRGF2ZQo+Cj4gT24gMTAgSmFuIDIwMTMsIGF0IDIzOjQwLCBHZW9yZ2Ug U2h1a2xpbiB3cm90ZToKPgo+PiBBcmUgdGhvc2UgaG9zdHMgaW4gc2FtZSBwb29sIG9yIGluIHNl cGFyYXRlIHBvb2xzPyBJZiBzYW1lIHBvb2wsIHNoYXJlZAo+PiBTUiBvciBsb2NhbD8gQW55d2F5 LCBkZXRhaWxzIHNob3VsZCBiZSBpbiAvdmFyL2xvZy94ZW5zb3VyY2UubG9nICh0b28KPj4gbXVj aCBkZXRhaWxzLCBhY3R1YWxseSkuCj4+Cj4+Cj4+IDEwLjAxLjIwMTMgMTQ6NDksIERhdmUgQXZl bnQg0L/QuNGI0LXRgjoKPj4+IEkgYW0gaGF2aW5nIGlzc3VlcyB3aXRoIG1pZ3JhdGluZyBWTXMg YmV0d2VlbiBob3N0cy4gSGVyZSBpcyBob3cgSSBjYW4gcmVwcm9kdWNlIHRoZSBwcm9ibGVtOgo+ Pj4KPj4+IDEpIENyZWF0ZSAyIG5ldyBWTSdzICh1c2luZyBlaXRoZXIgYSBmcmVzaCBpbnN0YWxs IGZyb20gTmV0IEluc3RhbGwgb2YgRGViaWFuIG9yIGZyb20gYSAiR29sZGVuIEltYWdlIiBvZiBh IFZNIHByZXZpb3VzbHkgY29udmVydGVkIHRvIGEgVGVtcGxhdGUpCj4+Pgo+Pj4gMikgTWlncmF0 ZSBvbmUgb2YgdGhlIFZNcyB0byBhbm90aGVyIGhvc3RzCj4+Pgo+Pj4gMykgQXR0ZW1wdCB0byBt aWdyYXRlIHRoZSBzYW1lIFZNIGJhY2sgdG8gdGhlIG9yaWdpbmFsIGhvc3QgaG93ZXZlciBpdCBy ZWZ1c2VzIGFuZCB0aHJvd3M6Cj4+Pgo+Pj4gQ2Fubm90IHJlc3RvcmUgdGhpcyBWTSBiZWNhdXNl IGl0IHdvdWxkIGNyZWF0ZSBhIGR1cGxpY2F0ZQo+Pj4gdm06IE9wYXF1ZVJlZjo3MTFmMjJmMy05 ZTM1LWIxM2UtMWMzNS01OGU4YTU3OGNhMGUKPj4+Cj4+PiBXaGF0IGV4YWN0bHkgZG9lcyBpdCB0 aGluayBpcyBiZWluZyBkdXBsaWNhdGVkPyBOb25lIG9mIHRoZSBvcmlnaW5hbCBhc3NldHMgYXBw ZWFyIHRvIGhhdmUgYmVlbiBsZWZ0IGJlaGluZCAoZmFpbGVkIHRvIGJlIGRlbGV0ZWQgZXRjKS4g SSBjYW4ndCBzZWUgd2h5IHRoaXMgaXMgZmFpbGluZy4KPj4+Cj4+PiBBbnkgaWRlYXM/Cj4+Pgo+ Pgo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+PiBY ZW4tYXBpIG1haWxpbmcgbGlzdAo+PiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPj4gaHR0cDovL2xp c3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKPgoKCl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBs aXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21h aWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Fri Jan 11 13:45:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 13:45:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tteuw-0002JL-Dt; Fri, 11 Jan 2013 13:45:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tteuv-0002JE-2o for xen-api@lists.xen.org; Fri, 11 Jan 2013 13:45:05 +0000 Received: from [85.158.143.99:29084] by server-2.bemta-4.messagelabs.com id 5B/10-24322-06710F05; Fri, 11 Jan 2013 13:45:04 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1357911902!20493506!1 X-Originating-IP: [207.126.144.127] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19929 invoked from network); 11 Jan 2013 13:45:03 -0000 Received: from eu1sys200aog109.obsmtp.com (HELO eu1sys200aog109.obsmtp.com) (207.126.144.127) by server-6.tower-216.messagelabs.com with SMTP; 11 Jan 2013 13:45:03 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob109.postini.com ([207.126.147.11]) with SMTP ID DSNKUPAW7h4DZcqyIykYi53NvJaMTTTVDJTX@postini.com; Fri, 11 Jan 2013 13:45:03 UTC Received: from batwexhtca01.uk.futurenet.com (batwexhtca01.uk.futurenet.com [172.23.130.3]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 29BDD7F448D; Fri, 11 Jan 2013 13:43:10 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by batwexhtca01 ([172.23.130.3]) with mapi; Fri, 11 Jan 2013 13:43:10 +0000 From: Dave Avent To: George Shuklin Date: Fri, 11 Jan 2013 13:43:09 +0000 Thread-Topic: [Xen-API] VM Migration Bug? Thread-Index: Ac3wAZewsOWk2nIJR6yWX1FYtUql3w== Message-ID: References: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> <50EF5154.5050103@gmail.com> <7C4029AA-8291-4380-AE83-DA1810B5CCCE@futurenet.com> <50F014A8.6000505@gmail.com> In-Reply-To: <50F014A8.6000505@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Q2hlY2tlZCBkb21haW5zIG9uIGJvdGggaG9zdHMuIE5vIGR1cGxpY2F0ZXMgYW5kIGVhY2ggb25l IGxpc3RzIHRoZSBWTXMgaXQgaXMgaG9zdGluZyBjb3JyZWN0bHkuDQoNCkFsc28gcmVzdGFydGlu ZyB4YXBpIG9uIGJvdGggaG9zdHMgaGFzIG5vIGFmZmVjdC4NCg0KT24gMTEgSmFuIDIwMTMsIGF0 IDEzOjMzLCBHZW9yZ2UgU2h1a2xpbiB3cm90ZToNCg0KPiBPaCwgc2VlbXMgbGlrZSB5b3UgZ290 IGEgZHVwbGljYXRlIGRvbWFpbiBvbiBzb21lIGhvc3QuIENoZWNrIChtYW51YWxseSANCj4gdGhh dCB0aGF0IGRvbWFpbiBpcyBub3QgcnVubmluZyBvbiB0YXJnZXQgaG9zdCAob3IgYW55IGhvc3Qg aW4gdGFyZ2V0J3MgDQo+IHBvb2wpLCBsaXN0X2RvbWFpbnMpLiBBbmQgY2hlY2sgdGhhdCB2bSBp cyByZW1vdmVkIGZyb20gdGFyZ2V0IHBvb2wgKG5vIA0KPiB4ZSB2bS1saXN0IHV1aWQ9Li4uIGVu dHJ5KS4gSWYgc29tZSBjb3JyZWN0aW9uIHdhcyBtYWRlIChmLmUuIHN0cmF5IA0KPiBkb21haW4g a2lsbGVkKSwgeGFwaSBzZXJ2aWNlIHJlc3RhcnQgbWF5IGJlIG5lZWQgb24gZXZlcnkgaG9zdCBp biANCj4gdGFyZ2V0J3MgcG9vbC4NCj4gDQo+IA0KPiAxMS4wMS4yMDEzIDE2OjU4LCBEYXZlIEF2 ZW50INC/0LjRiNC10YI6DQo+PiBTb21lIG1vcmUgaW5mbzoNCj4+IA0KPj4gSSBoYXZlIHRyYWNr ZWQgdGhpcyBkb3duIHRvIFZNJ3MgY3JlYXRlZCB1c2luZyB0aGUgQVBJIChpbiBteSBjYXNlIHVz aW5nIHRoZSBSdWJ5IEZvZyBsaWJyYXJpZXMpLiBJIGFtIGFzc3VtaW5nIHRoYXQgdGhlc2UgbGli cmFyaWVzIGFyZSBnb2luZyBzb21ldGhpbmcgaW5jb3JyZWN0bHkgYnV0IEkgY2Fubm90IGZpZ3Vy ZSBvdXQgZXhhY3RseSB3aGF0IFhDUCBoYXMgaXNzdWVzIHdpdGguDQo+PiANCj4+IFRvIGFuc3dl ciB5b3VyIHF1ZXN0aW9ucyB0aGV5IGFyZSBzZXBhcmF0ZSBob3N0cyBub3QgaW4gYSBwb29sLg0K Pj4gDQo+PiBUaGUgcmVsZXZhbnQgbG9nIGVudHJpZXMgYXJlIGhlcmU6IGh0dHBzOi8vZ2lzdC5n aXRodWIuY29tLzQ1MTA0NDENCj4+IA0KPj4gVGhhbmtzLA0KPj4gDQo+PiBEYXZlDQo+PiANCj4+ IE9uIDEwIEphbiAyMDEzLCBhdCAyMzo0MCwgR2VvcmdlIFNodWtsaW4gd3JvdGU6DQo+PiANCj4+ PiBBcmUgdGhvc2UgaG9zdHMgaW4gc2FtZSBwb29sIG9yIGluIHNlcGFyYXRlIHBvb2xzPyBJZiBz YW1lIHBvb2wsIHNoYXJlZA0KPj4+IFNSIG9yIGxvY2FsPyBBbnl3YXksIGRldGFpbHMgc2hvdWxk IGJlIGluIC92YXIvbG9nL3hlbnNvdXJjZS5sb2cgKHRvbw0KPj4+IG11Y2ggZGV0YWlscywgYWN0 dWFsbHkpLg0KPj4+IA0KPj4+IA0KPj4+IDEwLjAxLjIwMTMgMTQ6NDksIERhdmUgQXZlbnQg0L/Q uNGI0LXRgjoNCj4+Pj4gSSBhbSBoYXZpbmcgaXNzdWVzIHdpdGggbWlncmF0aW5nIFZNcyBiZXR3 ZWVuIGhvc3RzLiBIZXJlIGlzIGhvdyBJIGNhbiByZXByb2R1Y2UgdGhlIHByb2JsZW06DQo+Pj4+ IA0KPj4+PiAxKSBDcmVhdGUgMiBuZXcgVk0ncyAodXNpbmcgZWl0aGVyIGEgZnJlc2ggaW5zdGFs bCBmcm9tIE5ldCBJbnN0YWxsIG9mIERlYmlhbiBvciBmcm9tIGEgIkdvbGRlbiBJbWFnZSIgb2Yg YSBWTSBwcmV2aW91c2x5IGNvbnZlcnRlZCB0byBhIFRlbXBsYXRlKQ0KPj4+PiANCj4+Pj4gMikg TWlncmF0ZSBvbmUgb2YgdGhlIFZNcyB0byBhbm90aGVyIGhvc3RzDQo+Pj4+IA0KPj4+PiAzKSBB dHRlbXB0IHRvIG1pZ3JhdGUgdGhlIHNhbWUgVk0gYmFjayB0byB0aGUgb3JpZ2luYWwgaG9zdCBo b3dldmVyIGl0IHJlZnVzZXMgYW5kIHRocm93czoNCj4+Pj4gDQo+Pj4+IENhbm5vdCByZXN0b3Jl IHRoaXMgVk0gYmVjYXVzZSBpdCB3b3VsZCBjcmVhdGUgYSBkdXBsaWNhdGUNCj4+Pj4gdm06IE9w YXF1ZVJlZjo3MTFmMjJmMy05ZTM1LWIxM2UtMWMzNS01OGU4YTU3OGNhMGUNCj4+Pj4gDQo+Pj4+ IFdoYXQgZXhhY3RseSBkb2VzIGl0IHRoaW5rIGlzIGJlaW5nIGR1cGxpY2F0ZWQ/IE5vbmUgb2Yg dGhlIG9yaWdpbmFsIGFzc2V0cyBhcHBlYXIgdG8gaGF2ZSBiZWVuIGxlZnQgYmVoaW5kIChmYWls ZWQgdG8gYmUgZGVsZXRlZCBldGMpLiBJIGNhbid0IHNlZSB3aHkgdGhpcyBpcyBmYWlsaW5nLg0K Pj4+PiANCj4+Pj4gQW55IGlkZWFzPw0KPj4+PiANCj4+PiANCj4+PiBfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+IFhlbi1hcGkgbWFpbGluZyBsaXN0 DQo+Pj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnDQo+Pj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkNCj4+IA0KPiANCg0KDQotLSANCkZ1dHVyZSBQ dWJsaXNoaW5nIExpbWl0ZWQgKHJlZ2lzdGVyZWQgY29tcGFueSBudW1iZXIgMjAwODg4NSkgaXMg YSB3aG9sbHkgb3duZWQgc3Vic2lkaWFyeSBvZiBGdXR1cmUgcGxjIChyZWdpc3RlcmVkIGNvbXBh bnkgbnVtYmVyIDM3NTc4NzQpLCBib3RoIG9mIHdoaWNoIGFyZSBpbmNvcnBvcmF0ZWQgaW4gRW5n bGFuZCBhbmQgV2FsZXMgYW5kIHNoYXJlIHRoZSBzYW1lIHJlZ2lzdGVyZWQgYWRkcmVzcyBhdCBC ZWF1Zm9yZCBDb3VydCwgMzAgTW9ubW91dGggU3RyZWV0LCBCYXRoIEJBMSAyQlcuDQoNClRoaXMg ZW1haWwgYW5kIGFueSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGFyZSBjb25maWRlbnRpYWwg YW5kIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRp dHkgdG8gd2hpY2ggdGhleSBhcmUgYWRkcmVzc2VkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlz IGVtYWlsIGluIGVycm9yIHBsZWFzZSByZXBseSB0byB0aGlzIGVtYWlsIGFuZCB0aGVuIGRlbGV0 ZSBpdC4gUGxlYXNlIG5vdGUgdGhhdCBhbnkgdmlld3Mgb3Igb3BpbmlvbnMgcHJlc2VudGVkIGlu IHRoaXMgZW1haWwgYXJlIHNvbGVseSB0aG9zZSBvZiB0aGUgYXV0aG9yIGFuZCBkbyBub3QgbmVj ZXNzYXJpbHkgcmVwcmVzZW50IHRob3NlIG9mIEZ1dHVyZS4NCg0KVGhlIHJlY2lwaWVudCBzaG91 bGQgY2hlY2sgdGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGZvciB0aGUgcHJlc2VuY2Ug b2YgdmlydXNlcy4gRnV0dXJlIGFjY2VwdHMgbm8gbGlhYmlsaXR5IGZvciBhbnkgZGFtYWdlIGNh dXNlZCBieSBhbnkgdmlydXMgdHJhbnNtaXR0ZWQgYnkgdGhpcyBlbWFpbC4NCg0KRnV0dXJlIG1h eSByZWd1bGFybHkgYW5kIHJhbmRvbWx5IG1vbml0b3Igb3V0Z29pbmcgYW5kIGluY29taW5nIGVt YWlscyBhbmQgb3RoZXIgdGVsZWNvbW11bmljYXRpb25zIG9uIGl0cyBlbWFpbCBhbmQgdGVsZWNv bW11bmljYXRpb25zIHN5c3RlbXMuIEJ5IHJlcGx5aW5nIHRvIHRoaXMgZW1haWwgeW91IGdpdmUg eW91ciBjb25zZW50IHRvIHN1Y2ggbW9uaXRvcmluZy4NCg0KKioqKioNClNhdmUgcmVzb3VyY2Vz OiB0aGluayBiZWZvcmUgeW91IHByaW50Lg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhl bi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1h cGkK From xen-api-bounces@lists.xen.org Fri Jan 11 13:45:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 13:45:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tteuw-0002JL-Dt; Fri, 11 Jan 2013 13:45:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tteuv-0002JE-2o for xen-api@lists.xen.org; Fri, 11 Jan 2013 13:45:05 +0000 Received: from [85.158.143.99:29084] by server-2.bemta-4.messagelabs.com id 5B/10-24322-06710F05; Fri, 11 Jan 2013 13:45:04 +0000 X-Env-Sender: Dave.Avent@futurenet.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1357911902!20493506!1 X-Originating-IP: [207.126.144.127] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19929 invoked from network); 11 Jan 2013 13:45:03 -0000 Received: from eu1sys200aog109.obsmtp.com (HELO eu1sys200aog109.obsmtp.com) (207.126.144.127) by server-6.tower-216.messagelabs.com with SMTP; 11 Jan 2013 13:45:03 -0000 Received: from batlnet03.uk.futurenet.com ([89.167.143.231]) by eu1sys200aob109.postini.com ([207.126.147.11]) with SMTP ID DSNKUPAW7h4DZcqyIykYi53NvJaMTTTVDJTX@postini.com; Fri, 11 Jan 2013 13:45:03 UTC Received: from batwexhtca01.uk.futurenet.com (batwexhtca01.uk.futurenet.com [172.23.130.3]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by batlnet03.uk.futurenet.com (Postfix) with ESMTPS id 29BDD7F448D; Fri, 11 Jan 2013 13:43:10 +0000 (GMT) Received: from BATWEXMVCG01.uk.futurenet.com ([172.23.130.2]) by batwexhtca01 ([172.23.130.3]) with mapi; Fri, 11 Jan 2013 13:43:10 +0000 From: Dave Avent To: George Shuklin Date: Fri, 11 Jan 2013 13:43:09 +0000 Thread-Topic: [Xen-API] VM Migration Bug? Thread-Index: Ac3wAZewsOWk2nIJR6yWX1FYtUql3w== Message-ID: References: <60070D86-8032-4A0F-9B4C-CAA3D8DCDDC4@futurenet.com> <50EF5154.5050103@gmail.com> <7C4029AA-8291-4380-AE83-DA1810B5CCCE@futurenet.com> <50F014A8.6000505@gmail.com> In-Reply-To: <50F014A8.6000505@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] VM Migration Bug? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Q2hlY2tlZCBkb21haW5zIG9uIGJvdGggaG9zdHMuIE5vIGR1cGxpY2F0ZXMgYW5kIGVhY2ggb25l IGxpc3RzIHRoZSBWTXMgaXQgaXMgaG9zdGluZyBjb3JyZWN0bHkuDQoNCkFsc28gcmVzdGFydGlu ZyB4YXBpIG9uIGJvdGggaG9zdHMgaGFzIG5vIGFmZmVjdC4NCg0KT24gMTEgSmFuIDIwMTMsIGF0 IDEzOjMzLCBHZW9yZ2UgU2h1a2xpbiB3cm90ZToNCg0KPiBPaCwgc2VlbXMgbGlrZSB5b3UgZ290 IGEgZHVwbGljYXRlIGRvbWFpbiBvbiBzb21lIGhvc3QuIENoZWNrIChtYW51YWxseSANCj4gdGhh dCB0aGF0IGRvbWFpbiBpcyBub3QgcnVubmluZyBvbiB0YXJnZXQgaG9zdCAob3IgYW55IGhvc3Qg aW4gdGFyZ2V0J3MgDQo+IHBvb2wpLCBsaXN0X2RvbWFpbnMpLiBBbmQgY2hlY2sgdGhhdCB2bSBp cyByZW1vdmVkIGZyb20gdGFyZ2V0IHBvb2wgKG5vIA0KPiB4ZSB2bS1saXN0IHV1aWQ9Li4uIGVu dHJ5KS4gSWYgc29tZSBjb3JyZWN0aW9uIHdhcyBtYWRlIChmLmUuIHN0cmF5IA0KPiBkb21haW4g a2lsbGVkKSwgeGFwaSBzZXJ2aWNlIHJlc3RhcnQgbWF5IGJlIG5lZWQgb24gZXZlcnkgaG9zdCBp biANCj4gdGFyZ2V0J3MgcG9vbC4NCj4gDQo+IA0KPiAxMS4wMS4yMDEzIDE2OjU4LCBEYXZlIEF2 ZW50INC/0LjRiNC10YI6DQo+PiBTb21lIG1vcmUgaW5mbzoNCj4+IA0KPj4gSSBoYXZlIHRyYWNr ZWQgdGhpcyBkb3duIHRvIFZNJ3MgY3JlYXRlZCB1c2luZyB0aGUgQVBJIChpbiBteSBjYXNlIHVz aW5nIHRoZSBSdWJ5IEZvZyBsaWJyYXJpZXMpLiBJIGFtIGFzc3VtaW5nIHRoYXQgdGhlc2UgbGli cmFyaWVzIGFyZSBnb2luZyBzb21ldGhpbmcgaW5jb3JyZWN0bHkgYnV0IEkgY2Fubm90IGZpZ3Vy ZSBvdXQgZXhhY3RseSB3aGF0IFhDUCBoYXMgaXNzdWVzIHdpdGguDQo+PiANCj4+IFRvIGFuc3dl ciB5b3VyIHF1ZXN0aW9ucyB0aGV5IGFyZSBzZXBhcmF0ZSBob3N0cyBub3QgaW4gYSBwb29sLg0K Pj4gDQo+PiBUaGUgcmVsZXZhbnQgbG9nIGVudHJpZXMgYXJlIGhlcmU6IGh0dHBzOi8vZ2lzdC5n aXRodWIuY29tLzQ1MTA0NDENCj4+IA0KPj4gVGhhbmtzLA0KPj4gDQo+PiBEYXZlDQo+PiANCj4+ IE9uIDEwIEphbiAyMDEzLCBhdCAyMzo0MCwgR2VvcmdlIFNodWtsaW4gd3JvdGU6DQo+PiANCj4+ PiBBcmUgdGhvc2UgaG9zdHMgaW4gc2FtZSBwb29sIG9yIGluIHNlcGFyYXRlIHBvb2xzPyBJZiBz YW1lIHBvb2wsIHNoYXJlZA0KPj4+IFNSIG9yIGxvY2FsPyBBbnl3YXksIGRldGFpbHMgc2hvdWxk IGJlIGluIC92YXIvbG9nL3hlbnNvdXJjZS5sb2cgKHRvbw0KPj4+IG11Y2ggZGV0YWlscywgYWN0 dWFsbHkpLg0KPj4+IA0KPj4+IA0KPj4+IDEwLjAxLjIwMTMgMTQ6NDksIERhdmUgQXZlbnQg0L/Q uNGI0LXRgjoNCj4+Pj4gSSBhbSBoYXZpbmcgaXNzdWVzIHdpdGggbWlncmF0aW5nIFZNcyBiZXR3 ZWVuIGhvc3RzLiBIZXJlIGlzIGhvdyBJIGNhbiByZXByb2R1Y2UgdGhlIHByb2JsZW06DQo+Pj4+ IA0KPj4+PiAxKSBDcmVhdGUgMiBuZXcgVk0ncyAodXNpbmcgZWl0aGVyIGEgZnJlc2ggaW5zdGFs bCBmcm9tIE5ldCBJbnN0YWxsIG9mIERlYmlhbiBvciBmcm9tIGEgIkdvbGRlbiBJbWFnZSIgb2Yg YSBWTSBwcmV2aW91c2x5IGNvbnZlcnRlZCB0byBhIFRlbXBsYXRlKQ0KPj4+PiANCj4+Pj4gMikg TWlncmF0ZSBvbmUgb2YgdGhlIFZNcyB0byBhbm90aGVyIGhvc3RzDQo+Pj4+IA0KPj4+PiAzKSBB dHRlbXB0IHRvIG1pZ3JhdGUgdGhlIHNhbWUgVk0gYmFjayB0byB0aGUgb3JpZ2luYWwgaG9zdCBo b3dldmVyIGl0IHJlZnVzZXMgYW5kIHRocm93czoNCj4+Pj4gDQo+Pj4+IENhbm5vdCByZXN0b3Jl IHRoaXMgVk0gYmVjYXVzZSBpdCB3b3VsZCBjcmVhdGUgYSBkdXBsaWNhdGUNCj4+Pj4gdm06IE9w YXF1ZVJlZjo3MTFmMjJmMy05ZTM1LWIxM2UtMWMzNS01OGU4YTU3OGNhMGUNCj4+Pj4gDQo+Pj4+ IFdoYXQgZXhhY3RseSBkb2VzIGl0IHRoaW5rIGlzIGJlaW5nIGR1cGxpY2F0ZWQ/IE5vbmUgb2Yg dGhlIG9yaWdpbmFsIGFzc2V0cyBhcHBlYXIgdG8gaGF2ZSBiZWVuIGxlZnQgYmVoaW5kIChmYWls ZWQgdG8gYmUgZGVsZXRlZCBldGMpLiBJIGNhbid0IHNlZSB3aHkgdGhpcyBpcyBmYWlsaW5nLg0K Pj4+PiANCj4+Pj4gQW55IGlkZWFzPw0KPj4+PiANCj4+PiANCj4+PiBfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+IFhlbi1hcGkgbWFpbGluZyBsaXN0 DQo+Pj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnDQo+Pj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkNCj4+IA0KPiANCg0KDQotLSANCkZ1dHVyZSBQ dWJsaXNoaW5nIExpbWl0ZWQgKHJlZ2lzdGVyZWQgY29tcGFueSBudW1iZXIgMjAwODg4NSkgaXMg YSB3aG9sbHkgb3duZWQgc3Vic2lkaWFyeSBvZiBGdXR1cmUgcGxjIChyZWdpc3RlcmVkIGNvbXBh bnkgbnVtYmVyIDM3NTc4NzQpLCBib3RoIG9mIHdoaWNoIGFyZSBpbmNvcnBvcmF0ZWQgaW4gRW5n bGFuZCBhbmQgV2FsZXMgYW5kIHNoYXJlIHRoZSBzYW1lIHJlZ2lzdGVyZWQgYWRkcmVzcyBhdCBC ZWF1Zm9yZCBDb3VydCwgMzAgTW9ubW91dGggU3RyZWV0LCBCYXRoIEJBMSAyQlcuDQoNClRoaXMg ZW1haWwgYW5kIGFueSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGFyZSBjb25maWRlbnRpYWwg YW5kIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRp dHkgdG8gd2hpY2ggdGhleSBhcmUgYWRkcmVzc2VkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlz IGVtYWlsIGluIGVycm9yIHBsZWFzZSByZXBseSB0byB0aGlzIGVtYWlsIGFuZCB0aGVuIGRlbGV0 ZSBpdC4gUGxlYXNlIG5vdGUgdGhhdCBhbnkgdmlld3Mgb3Igb3BpbmlvbnMgcHJlc2VudGVkIGlu IHRoaXMgZW1haWwgYXJlIHNvbGVseSB0aG9zZSBvZiB0aGUgYXV0aG9yIGFuZCBkbyBub3QgbmVj ZXNzYXJpbHkgcmVwcmVzZW50IHRob3NlIG9mIEZ1dHVyZS4NCg0KVGhlIHJlY2lwaWVudCBzaG91 bGQgY2hlY2sgdGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGZvciB0aGUgcHJlc2VuY2Ug b2YgdmlydXNlcy4gRnV0dXJlIGFjY2VwdHMgbm8gbGlhYmlsaXR5IGZvciBhbnkgZGFtYWdlIGNh dXNlZCBieSBhbnkgdmlydXMgdHJhbnNtaXR0ZWQgYnkgdGhpcyBlbWFpbC4NCg0KRnV0dXJlIG1h eSByZWd1bGFybHkgYW5kIHJhbmRvbWx5IG1vbml0b3Igb3V0Z29pbmcgYW5kIGluY29taW5nIGVt YWlscyBhbmQgb3RoZXIgdGVsZWNvbW11bmljYXRpb25zIG9uIGl0cyBlbWFpbCBhbmQgdGVsZWNv bW11bmljYXRpb25zIHN5c3RlbXMuIEJ5IHJlcGx5aW5nIHRvIHRoaXMgZW1haWwgeW91IGdpdmUg eW91ciBjb25zZW50IHRvIHN1Y2ggbW9uaXRvcmluZy4NCg0KKioqKioNClNhdmUgcmVzb3VyY2Vz OiB0aGluayBiZWZvcmUgeW91IHByaW50Lg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhl bi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1h cGkK From xen-api-bounces@lists.xen.org Fri Jan 11 15:28:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 15:28:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtgWQ-0005IF-Ul; Fri, 11 Jan 2013 15:27:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtgWO-0005I9-V1 for xen-api@lists.xen.org; Fri, 11 Jan 2013 15:27:53 +0000 Received: from [85.158.139.211:22012] by server-8.bemta-5.messagelabs.com id A6/2E-15003-87F20F05; Fri, 11 Jan 2013 15:27:52 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1357918068!18916868!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.8 required=7.0 tests=EXTRA_MPART_TYPE, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 431 invoked from network); 11 Jan 2013 15:27:50 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Jan 2013 15:27:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:MIME-Version; b=uuMKg57LJzum1WDQRCQdTnP2MleLMJpihn3bbKP3iK/KWxDJ/wboYU+CCEJckMbPwO362WWbE/WfgSWRhWOMViPe7gnA5E3KAeDksZW+0ZguP/2sR6801PUZsIPlaGHF; Received: from [192.168.1.29] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1TtgWK-000F7F-IG for xen-api@lists.xen.org; Fri, 11 Jan 2013 07:27:48 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-004-sfo.servepath.com ([::1]) with mapi; Fri, 11 Jan 2013 07:27:48 -0800 From: Brian Menges To: "xen-api@lists.xen.org" Date: Fri, 11 Jan 2013 07:27:46 -0800 Thread-Topic: [Xen-API] compatibility high performance hardware Thread-Index: Ac3v5uG/lPoYr3GxQPWIKdSRbNmOfQAKTKRA Message-ID: <3968CAC7E1BE7242B18501F292F3C7F167BDD8C0@EX-004-SFO.servepath.com> References: <002f01cdefe6$e1fd1ab0$a5f75010$@com> In-Reply-To: <002f01cdefe6$e1fd1ab0$a5f75010$@com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] compatibility high performance hardware X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5342308337988272294==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5342308337988272294== Content-Language: en-US Content-Type: multipart/related; boundary="_004_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_"; type="multipart/alternative" --_004_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_ Content-Type: multipart/alternative; boundary="_000_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_" --_000_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Those drivers should be compatible with XCP 1.6 ( XCP 1.6 ~=3D XenServer 6.= 0) - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of marc poll garcia Sent: Friday, January 11, 2013 02:32 To: xen-api@lists.xen.org Subject: [Xen-API] compatibility high performance hardware Compatibility high performance hardware: We want to buy this hardware device, to create a fiber chanel platform: http://www.emulex.com/products/host-bus-adapters/emulex-branded/lightpulse-= lpe12002/specifications.html http://www.emulex.com/index.php?id=3D14664 It seems that there's drivers only for the official XenServer 6.0 and not f= or the XCP system(1.6 version). Is it going to work as well?? Many thanks!! Marc Poll =C0rea T=E8cnica - ServeisWeb http://www.serveisweb.cat http://blog.serveisweb.cat http://www.ticketday.cat Tel. 902 010 664 - Tel. Int. +34 972 010 550 Fax 902 510 664 - Fax Int. +34 972 010 555 [cid:image001.gif@01CDEFCD.26F88DD0] Abans d'imprimir aquest e-mail, pensi= b=E9 si =E9s necessari fer-ho. AV=CDS LEGAL SW Hosting & Communications Technologies, SL l'informa que aquest missatge= va dirigit de manera exclusiva al seu destinatari, ja que cont=E9 informac= i=F3 confidencial i/o sensible subjecta al secret professional i protegida = per la legislaci=F3 vigent. Si V=E8. no =E9s el destinatari indicat li noti= fiquem que la lectura, utilitzaci=F3, divulgaci=F3, reproducci=F3, distribu= ci=F3, impressi=F3 i/o c=F2pia d'aquesta comunicaci=F3, informaci=F3 i/o q= ualsevol document adjunt a la mateixa estan estrictament prohibides per la = llei. Si V=E8. ha rebut aquest missatge per error, li demanem que ens ho co= muniqui de manera immediata contestant al remitent d'aquest missatge i, seg= uidament, procedeixi a la seva destrucci=F3 juntament amb qualsevol documen= t adjunt en cas d'haver-n'hi. ________________________________ The information contained in this message, and any attachments, may contain= confidential and legally privileged material. It is solely for the use of = the person or entity to which it is addressed. Any review, retransmission, = dissemination, or action taken in reliance upon this information by persons= or entities other than the intended recipient is prohibited. If you receiv= e this in error, please contact the sender and delete the material from any= computer. --_000_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Those drivers should b= e compatible with XCP 1.6 ( XCP 1.6 ~=3D XenServer 6.0)

 

- Brian Menges

Principal Engineer, De= vOps

GoGrid | ServePath | C= oloServe | UpStream Networks

 

From: xen-api-= bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of marc poll garcia
Sent: Friday, January 11, 2013 02:32
To: xen-api@lists.xen.org
Subject: [Xen-API] compatibility high performance hardware

 

Compatibility high performance har= dware:

 

We want to buy this hardware devic= e, to create a fiber chanel platform:

 

http://www.emulex.com/products/host-bus-adapters/emulex-branded/ligh= tpulse-lpe12002/specifications.html

http://www.emulex.com/index.php?id=3D14664

 

It seems that there’s driver= s only for the official XenServer 6.0 and not for the XCP system(1.6 versio= n). Is it going to work as well??

 

Many thanks!!

 

 

Marc Poll<= /p>

=C0rea T=E8cnica – ServeisWeb

 

http://www.serveisweb.cat

http://blog.serveisweb.cat

http://www.ticketday.cat

Tel. 902 010 664 - Tel. Int. +34 972 010 550

Fax  902 510 664 - Fax Int.  +34 972 010 555

=  

3D"Descripci=F3n:  Abans d'imprimir aqu= est e-mail, pensi b=E9 si =E9s necessari fer-ho.

AV=CDS LEGAL

SW Hosting & Communications Technologies, SL  l&#= 8217;informa que aquest missatge va dirigit de manera exclusiva al seu dest= inatari, ja que cont=E9 informaci=F3 confidencial i/o sensible subjecta al secret p= rofessional i protegida per la legislaci=F3 vigent. Si V=E8. no =E9s el des= tinatari indicat li notifiquem que la lectura, utilitzaci=F3, divulgaci=F3,= reproducci=F3, distribuci=F3, impressi=F3 i/o c=F2pia d’aquesta comunicaci=F3, informaci=F3  i/o qualsevol document a= djunt a la mateixa estan estrictament prohibides per la llei. Si V=E8. ha r= ebut aquest missatge per error, li demanem que ens ho comuniqui de manera i= mmediata contestant al remitent d’aquest missatge i, seguidament, procedeixi a la seva destrucci=F3 juntament amb qualsevol = document adjunt en cas d’haver-n’hi.

 


The information contai= ned in this message, and any attachments, may contain confidential and lega= lly privileged material. It is solely for the use of the person or entity t= o which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by person= s or entities other than the intended recipient is prohibited. If you recei= ve this in error, please contact the sender and delete the material from an= y computer.
 --_000_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_-- --_004_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_ Content-Type: image/gif; name="image001.gif" Content-Description: image001.gif Content-Disposition: inline; filename="image001.gif"; size=119; creation-date="Fri, 11 Jan 2013 07:27:47 GMT"; modification-date="Fri, 11 Jan 2013 07:27:47 GMT" Content-ID: Content-Transfer-Encoding: base64 R0lGODlhIAAfAIAAAACAAP///yH5BAAAAAAALAAAAAAgAB8AAAJOjI+py73gYgNUWkNzvTJzq0Hf FIpjUnrnkWor6r5Ia670dt7qp8fyLoPVgizco4dszZJIIfN2eSo50lSkGnJggYqtsYu9hsXMaJKn y6UKADs= --_004_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_-- --===============5342308337988272294== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5342308337988272294==-- From xen-api-bounces@lists.xen.org Fri Jan 11 15:28:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 15:28:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtgWQ-0005IF-Ul; Fri, 11 Jan 2013 15:27:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtgWO-0005I9-V1 for xen-api@lists.xen.org; Fri, 11 Jan 2013 15:27:53 +0000 Received: from [85.158.139.211:22012] by server-8.bemta-5.messagelabs.com id A6/2E-15003-87F20F05; Fri, 11 Jan 2013 15:27:52 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1357918068!18916868!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.8 required=7.0 tests=EXTRA_MPART_TYPE, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 431 invoked from network); 11 Jan 2013 15:27:50 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Jan 2013 15:27:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:MIME-Version; b=uuMKg57LJzum1WDQRCQdTnP2MleLMJpihn3bbKP3iK/KWxDJ/wboYU+CCEJckMbPwO362WWbE/WfgSWRhWOMViPe7gnA5E3KAeDksZW+0ZguP/2sR6801PUZsIPlaGHF; Received: from [192.168.1.29] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1TtgWK-000F7F-IG for xen-api@lists.xen.org; Fri, 11 Jan 2013 07:27:48 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-004-sfo.servepath.com ([::1]) with mapi; Fri, 11 Jan 2013 07:27:48 -0800 From: Brian Menges To: "xen-api@lists.xen.org" Date: Fri, 11 Jan 2013 07:27:46 -0800 Thread-Topic: [Xen-API] compatibility high performance hardware Thread-Index: Ac3v5uG/lPoYr3GxQPWIKdSRbNmOfQAKTKRA Message-ID: <3968CAC7E1BE7242B18501F292F3C7F167BDD8C0@EX-004-SFO.servepath.com> References: <002f01cdefe6$e1fd1ab0$a5f75010$@com> In-Reply-To: <002f01cdefe6$e1fd1ab0$a5f75010$@com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] compatibility high performance hardware X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5342308337988272294==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5342308337988272294== Content-Language: en-US Content-Type: multipart/related; boundary="_004_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_"; type="multipart/alternative" --_004_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_ Content-Type: multipart/alternative; boundary="_000_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_" --_000_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Those drivers should be compatible with XCP 1.6 ( XCP 1.6 ~=3D XenServer 6.= 0) - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of marc poll garcia Sent: Friday, January 11, 2013 02:32 To: xen-api@lists.xen.org Subject: [Xen-API] compatibility high performance hardware Compatibility high performance hardware: We want to buy this hardware device, to create a fiber chanel platform: http://www.emulex.com/products/host-bus-adapters/emulex-branded/lightpulse-= lpe12002/specifications.html http://www.emulex.com/index.php?id=3D14664 It seems that there's drivers only for the official XenServer 6.0 and not f= or the XCP system(1.6 version). Is it going to work as well?? Many thanks!! Marc Poll =C0rea T=E8cnica - ServeisWeb http://www.serveisweb.cat http://blog.serveisweb.cat http://www.ticketday.cat Tel. 902 010 664 - Tel. Int. +34 972 010 550 Fax 902 510 664 - Fax Int. +34 972 010 555 [cid:image001.gif@01CDEFCD.26F88DD0] Abans d'imprimir aquest e-mail, pensi= b=E9 si =E9s necessari fer-ho. AV=CDS LEGAL SW Hosting & Communications Technologies, SL l'informa que aquest missatge= va dirigit de manera exclusiva al seu destinatari, ja que cont=E9 informac= i=F3 confidencial i/o sensible subjecta al secret professional i protegida = per la legislaci=F3 vigent. Si V=E8. no =E9s el destinatari indicat li noti= fiquem que la lectura, utilitzaci=F3, divulgaci=F3, reproducci=F3, distribu= ci=F3, impressi=F3 i/o c=F2pia d'aquesta comunicaci=F3, informaci=F3 i/o q= ualsevol document adjunt a la mateixa estan estrictament prohibides per la = llei. Si V=E8. ha rebut aquest missatge per error, li demanem que ens ho co= muniqui de manera immediata contestant al remitent d'aquest missatge i, seg= uidament, procedeixi a la seva destrucci=F3 juntament amb qualsevol documen= t adjunt en cas d'haver-n'hi. ________________________________ The information contained in this message, and any attachments, may contain= confidential and legally privileged material. It is solely for the use of = the person or entity to which it is addressed. Any review, retransmission, = dissemination, or action taken in reliance upon this information by persons= or entities other than the intended recipient is prohibited. If you receiv= e this in error, please contact the sender and delete the material from any= computer. --_000_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Those drivers should b= e compatible with XCP 1.6 ( XCP 1.6 ~=3D XenServer 6.0)

 

- Brian Menges

Principal Engineer, De= vOps

GoGrid | ServePath | C= oloServe | UpStream Networks

 

From: xen-api-= bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of marc poll garcia
Sent: Friday, January 11, 2013 02:32
To: xen-api@lists.xen.org
Subject: [Xen-API] compatibility high performance hardware

 

Compatibility high performance har= dware:

 

We want to buy this hardware devic= e, to create a fiber chanel platform:

 

http://www.emulex.com/products/host-bus-adapters/emulex-branded/ligh= tpulse-lpe12002/specifications.html

http://www.emulex.com/index.php?id=3D14664

 

It seems that there’s driver= s only for the official XenServer 6.0 and not for the XCP system(1.6 versio= n). Is it going to work as well??

 

Many thanks!!

 

 

Marc Poll<= /p>

=C0rea T=E8cnica – ServeisWeb

 

http://www.serveisweb.cat

http://blog.serveisweb.cat

http://www.ticketday.cat

Tel. 902 010 664 - Tel. Int. +34 972 010 550

Fax  902 510 664 - Fax Int.  +34 972 010 555

=  

3D"Descripci=F3n:  Abans d'imprimir aqu= est e-mail, pensi b=E9 si =E9s necessari fer-ho.

AV=CDS LEGAL

SW Hosting & Communications Technologies, SL  l&#= 8217;informa que aquest missatge va dirigit de manera exclusiva al seu dest= inatari, ja que cont=E9 informaci=F3 confidencial i/o sensible subjecta al secret p= rofessional i protegida per la legislaci=F3 vigent. Si V=E8. no =E9s el des= tinatari indicat li notifiquem que la lectura, utilitzaci=F3, divulgaci=F3,= reproducci=F3, distribuci=F3, impressi=F3 i/o c=F2pia d’aquesta comunicaci=F3, informaci=F3  i/o qualsevol document a= djunt a la mateixa estan estrictament prohibides per la llei. Si V=E8. ha r= ebut aquest missatge per error, li demanem que ens ho comuniqui de manera i= mmediata contestant al remitent d’aquest missatge i, seguidament, procedeixi a la seva destrucci=F3 juntament amb qualsevol = document adjunt en cas d’haver-n’hi.

 


The information contai= ned in this message, and any attachments, may contain confidential and lega= lly privileged material. It is solely for the use of the person or entity t= o which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by person= s or entities other than the intended recipient is prohibited. If you recei= ve this in error, please contact the sender and delete the material from an= y computer.
 --_000_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_-- --_004_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_ Content-Type: image/gif; name="image001.gif" Content-Description: image001.gif Content-Disposition: inline; filename="image001.gif"; size=119; creation-date="Fri, 11 Jan 2013 07:27:47 GMT"; modification-date="Fri, 11 Jan 2013 07:27:47 GMT" Content-ID: Content-Transfer-Encoding: base64 R0lGODlhIAAfAIAAAACAAP///yH5BAAAAAAALAAAAAAgAB8AAAJOjI+py73gYgNUWkNzvTJzq0Hf FIpjUnrnkWor6r5Ia670dt7qp8fyLoPVgizco4dszZJIIfN2eSo50lSkGnJggYqtsYu9hsXMaJKn y6UKADs= --_004_3968CAC7E1BE7242B18501F292F3C7F167BDD8C0EX004SFOservepa_-- --===============5342308337988272294== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5342308337988272294==-- From xen-api-bounces@lists.xen.org Fri Jan 11 16:59:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 16:59:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TthwU-0000U5-A2; Fri, 11 Jan 2013 16:58:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TthwS-0000TY-JV; Fri, 11 Jan 2013 16:58:52 +0000 Received: from [193.109.254.147:32198] by server-7.bemta-14.messagelabs.com id 19/54-08102-AC440F05; Fri, 11 Jan 2013 16:58:50 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1357923529!2911608!1 X-Originating-IP: [209.85.214.49] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17426 invoked from network); 11 Jan 2013 16:58:50 -0000 Received: from mail-bk0-f49.google.com (HELO mail-bk0-f49.google.com) (209.85.214.49) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 16:58:50 -0000 Received: by mail-bk0-f49.google.com with SMTP id jm19so1059192bkc.22 for ; Fri, 11 Jan 2013 08:58:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:cc:subject:content-type:content-transfer-encoding; bh=kYw+fK8layGWmreRYikBjBgkOhqFwhK87J3tJQn8Ol8=; b=znXTg2EVhfjZ6Ano+6gCo5KOaE4mGhBWg/fYt0V/5rrWMNe8bLBC2IaW0gzNnivmR9 8hb1vtPa3IKjduNObrsm06zXDNxVoMk7QimfxVEVED6ggpCOi4tUfJwCJobc4mQe7cbo XR9+MOtimqcFEjkb5MWrrpyzEGDsUl92j7ojUvM/9R2Wx4T9AkecA1/SpGYL0oe8rA0f HinrYRJx6nMAle431yJL7nMRwTSFkcHzXyOiGOAx3kdG12opzfs/212TR0NVA3IcUaGt 02wfQ5cv7HLYhPRLoabQxG4jjfCPve5MtkpS/ubpEZa6C9WTtnNTkYbUpmY0zKc+8ty0 UMlw== X-Received: by 10.204.129.214 with SMTP id p22mr36454840bks.47.1357923529568; Fri, 11 Jan 2013 08:58:49 -0800 (PST) Received: from [172.16.26.11] (02dd07f3.bb.sky.com. [2.221.7.243]) by mx.google.com with ESMTPS id i20sm4972859bkw.5.2013.01.11.08.58.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Jan 2013 08:58:47 -0800 (PST) Message-ID: <50F044C3.7010400@xen.org> Date: Fri, 11 Jan 2013 16:58:43 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , xen-arm@lists.xen.org, "xen-api@lists.xen.org" Cc: Amir M Chaudhry Subject: [Xen-API] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everybody, this e-mail is to let you know that the OpenMirage project is seeking to become a Xen.org hosted project. The prospective project lead of the Mirage Project - Anil Madhavapeddy - has requested a Review of the Mirage Project to become an Xen.org Incubation project. In line with Xen Project Governance (see http://www.xen.org/projects/governance.html), in particular sections - "Forming a Project" at http://www.xen.org/projects/governance.html#project.forming - "Project Proposal" at http://www.xen.org/projects/governance.html#project.proposal - "Requesting Reviews, Reviews and Voting" at http://www.xen.org/projects/governance.html#project.requests This is an informal community review, which will be followed by a formal vote. The Proposal and Proposal Meta Information ========================================== - Proposal Location at: http://wiki.xen.org/wiki/Mirage_Incubation_Project_Proposal - Project Lead: Anil Madhavapeddy - Project Sponsor: Tim Deegan - Project Mentor: Lars Kurth - Deadline: review open until 24:00, 27th of Jan, 2013 (GMT) Following the Community Review, there may be an update to the proposal if needed. Which is then followed by a formal vote by eligible community members. Why and How to Provide Feedback =============================== - Anybody in the Community can provide feedback - Preferably, feedback should be provided by annotating the in-lined copy of the document using the instructions in the wiki. In other word insert "{{comment|~~~~}} your comment." into the document, at a suitable location in the document. - Alternatively you can provide feedback by replying to this e-mail Best Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 16:59:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 16:59:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TthwU-0000U5-A2; Fri, 11 Jan 2013 16:58:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TthwS-0000TY-JV; Fri, 11 Jan 2013 16:58:52 +0000 Received: from [193.109.254.147:32198] by server-7.bemta-14.messagelabs.com id 19/54-08102-AC440F05; Fri, 11 Jan 2013 16:58:50 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1357923529!2911608!1 X-Originating-IP: [209.85.214.49] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17426 invoked from network); 11 Jan 2013 16:58:50 -0000 Received: from mail-bk0-f49.google.com (HELO mail-bk0-f49.google.com) (209.85.214.49) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 16:58:50 -0000 Received: by mail-bk0-f49.google.com with SMTP id jm19so1059192bkc.22 for ; Fri, 11 Jan 2013 08:58:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:cc:subject:content-type:content-transfer-encoding; bh=kYw+fK8layGWmreRYikBjBgkOhqFwhK87J3tJQn8Ol8=; b=znXTg2EVhfjZ6Ano+6gCo5KOaE4mGhBWg/fYt0V/5rrWMNe8bLBC2IaW0gzNnivmR9 8hb1vtPa3IKjduNObrsm06zXDNxVoMk7QimfxVEVED6ggpCOi4tUfJwCJobc4mQe7cbo XR9+MOtimqcFEjkb5MWrrpyzEGDsUl92j7ojUvM/9R2Wx4T9AkecA1/SpGYL0oe8rA0f HinrYRJx6nMAle431yJL7nMRwTSFkcHzXyOiGOAx3kdG12opzfs/212TR0NVA3IcUaGt 02wfQ5cv7HLYhPRLoabQxG4jjfCPve5MtkpS/ubpEZa6C9WTtnNTkYbUpmY0zKc+8ty0 UMlw== X-Received: by 10.204.129.214 with SMTP id p22mr36454840bks.47.1357923529568; Fri, 11 Jan 2013 08:58:49 -0800 (PST) Received: from [172.16.26.11] (02dd07f3.bb.sky.com. [2.221.7.243]) by mx.google.com with ESMTPS id i20sm4972859bkw.5.2013.01.11.08.58.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Jan 2013 08:58:47 -0800 (PST) Message-ID: <50F044C3.7010400@xen.org> Date: Fri, 11 Jan 2013 16:58:43 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , xen-arm@lists.xen.org, "xen-api@lists.xen.org" Cc: Amir M Chaudhry Subject: [Xen-API] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everybody, this e-mail is to let you know that the OpenMirage project is seeking to become a Xen.org hosted project. The prospective project lead of the Mirage Project - Anil Madhavapeddy - has requested a Review of the Mirage Project to become an Xen.org Incubation project. In line with Xen Project Governance (see http://www.xen.org/projects/governance.html), in particular sections - "Forming a Project" at http://www.xen.org/projects/governance.html#project.forming - "Project Proposal" at http://www.xen.org/projects/governance.html#project.proposal - "Requesting Reviews, Reviews and Voting" at http://www.xen.org/projects/governance.html#project.requests This is an informal community review, which will be followed by a formal vote. The Proposal and Proposal Meta Information ========================================== - Proposal Location at: http://wiki.xen.org/wiki/Mirage_Incubation_Project_Proposal - Project Lead: Anil Madhavapeddy - Project Sponsor: Tim Deegan - Project Mentor: Lars Kurth - Deadline: review open until 24:00, 27th of Jan, 2013 (GMT) Following the Community Review, there may be an update to the proposal if needed. Which is then followed by a formal vote by eligible community members. Why and How to Provide Feedback =============================== - Anybody in the Community can provide feedback - Preferably, feedback should be provided by annotating the in-lined copy of the document using the instructions in the wiki. In other word insert "{{comment|~~~~}} your comment." into the document, at a suitable location in the document. - Alternatively you can provide feedback by replying to this e-mail Best Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 17:32:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 17:32:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtiT5-0001xY-A3; Fri, 11 Jan 2013 17:32:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtiT3-0001xS-DM for xen-api@lists.xen.org; Fri, 11 Jan 2013 17:32:33 +0000 Received: from [85.158.143.99:35995] by server-3.bemta-4.messagelabs.com id 5B/2F-19220-0BC40F05; Fri, 11 Jan 2013 17:32:32 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-7.tower-216.messagelabs.com!1357925551!24186646!1 X-Originating-IP: [80.12.242.124] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20221 invoked from network); 11 Jan 2013 17:32:31 -0000 Received: from smtp02.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.124) by server-7.tower-216.messagelabs.com with SMTP; 11 Jan 2013 17:32:31 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d25 with ME id mhYW1k00D3zjds103hYWbJ; Fri, 11 Jan 2013 18:32:31 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 24F9B161B82 for ; Fri, 11 Jan 2013 18:32:30 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2a8VQnnKFA3 for ; Fri, 11 Jan 2013 18:32:29 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 969A5161BB7 for ; Fri, 11 Jan 2013 18:32:29 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Qv3RSQXEZx-U for ; Fri, 11 Jan 2013 18:32:28 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B20F0161B82 for ; Fri, 11 Jan 2013 18:32:28 +0100 (CET) Message-ID: <50F04CAC.6090407@tranquil-it-systems.fr> Date: Fri, 11 Jan 2013 18:32:28 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" Subject: [Xen-API] xcp 1.6 xsconsole and software iscsi SR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello everyone, On XCP <=3D1.1 it used to be possible to "detach" software iscsi SR from = the xsconsole. On XCP 1.6, it just says "no operation available" when one go to where = the "detach" option was. I know that is it possible on the command line, I was just wondering if = the missing feature is a bug or if there is another way to do it now. Cheers, Denis -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 17:32:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 17:32:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtiT5-0001xY-A3; Fri, 11 Jan 2013 17:32:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtiT3-0001xS-DM for xen-api@lists.xen.org; Fri, 11 Jan 2013 17:32:33 +0000 Received: from [85.158.143.99:35995] by server-3.bemta-4.messagelabs.com id 5B/2F-19220-0BC40F05; Fri, 11 Jan 2013 17:32:32 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-7.tower-216.messagelabs.com!1357925551!24186646!1 X-Originating-IP: [80.12.242.124] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20221 invoked from network); 11 Jan 2013 17:32:31 -0000 Received: from smtp02.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.124) by server-7.tower-216.messagelabs.com with SMTP; 11 Jan 2013 17:32:31 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d25 with ME id mhYW1k00D3zjds103hYWbJ; Fri, 11 Jan 2013 18:32:31 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 24F9B161B82 for ; Fri, 11 Jan 2013 18:32:30 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2a8VQnnKFA3 for ; Fri, 11 Jan 2013 18:32:29 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 969A5161BB7 for ; Fri, 11 Jan 2013 18:32:29 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Qv3RSQXEZx-U for ; Fri, 11 Jan 2013 18:32:28 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B20F0161B82 for ; Fri, 11 Jan 2013 18:32:28 +0100 (CET) Message-ID: <50F04CAC.6090407@tranquil-it-systems.fr> Date: Fri, 11 Jan 2013 18:32:28 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" Subject: [Xen-API] xcp 1.6 xsconsole and software iscsi SR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello everyone, On XCP <=3D1.1 it used to be possible to "detach" software iscsi SR from = the xsconsole. On XCP 1.6, it just says "no operation available" when one go to where = the "detach" option was. I know that is it possible on the command line, I was just wondering if = the missing feature is a bug or if there is another way to do it now. Cheers, Denis -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 18:46:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 18:46:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtjcV-0003p6-NU; Fri, 11 Jan 2013 18:46:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtjcT-0003p1-RT for xen-api@lists.xen.org; Fri, 11 Jan 2013 18:46:22 +0000 Received: from [85.158.138.51:15413] by server-1.bemta-3.messagelabs.com id 41/58-08906-8FD50F05; Fri, 11 Jan 2013 18:46:16 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-11.tower-174.messagelabs.com!1357929974!27621631!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=1.6 required=7.0 tests=DEAR_SOMETHING X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8033 invoked from network); 11 Jan 2013 18:46:15 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-11.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Jan 2013 18:46:15 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 91FC9FE131; Fri, 11 Jan 2013 18:49:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=05zZcKfTU iyEvZbOn0mUINPXAUU=; b=r/bjvCXLiZaPgODu6vBPR4E9dqXNjLVIlshReV1ht Y/M5vavBLHn675JtNP3334tKyU6nEOAiEZDFutBQreSGk9XGLBLQ2TdmU/tgMAmF 58GcW+FNOeDqJv4WaCTmlBb03VJOsvESIyEsEbFbl7IuyC8UksMTHe4gHah44d9V sU= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=nTK 7UaBeKve21VhSW4R1FPQZww9WIDWl+tRUI4Q9E7hjQhzMZ1Zu3wCy3y18AOrlu8V V7VrVdKk8u7H2Is3EWhYNtfWVpYOaIFC4fx2aAMvBwZK8sjcPtI3AeUZHoaZjF/3 kkmzzIYPfEYKWSuV6ku7KKdu0ebDfCT/ktNumJNA= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id C4259FE0C7; Fri, 11 Jan 2013 18:49:28 +0000 (UTC) Message-ID: <50F05DF3.10903@goirand.fr> Date: Sat, 12 Jan 2013 02:46:11 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: =?UTF-8?B?572R5a6JLeWNnumUpueoiw==?= References: <399f1e9a.1811f.13c202fb1b9.Coremail.sainrun001@126.com> In-Reply-To: <399f1e9a.1811f.13c202fb1b9.Coremail.sainrun001@126.com> X-Enigmail-Version: 1.4.1 Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Is the internal memory that domU occupyed will scratched? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gMDEvMTAvMjAxMyAxMjo0MSBBTSwg572R5a6JLeWNnumUpueoiyB3cm90ZToKPiAgRGVhciAg U2lyOgo+ICAgICAgICBJIGFtIGEgc3R1ZGVudCBvZiBDb21wdXRlciBTcGVjaWF0eSBpbiBhIHVu aXZlcnNpdHkuICBOb3cgSSBhbQo+IHN0dWR5aW5nIGluIHByaW5jaXBsZSBvZiBYZW4gQ2xvdWQg UGxhdGZvcm0uVGhlcmUgYXJlIGEgZmV3IG9mCj4gcXVlc3Rpb25zIGJvcmluZyBtZSBhbmQgSSBo YXZlIHRvIHNlZWsgaGVscCB0byB5b3UuCj4gICAgICAgIElmIGEgZ3Vlc3Qgb3MgaXMgZGVzdHJv eWVkLGlzIHRoZSBpbnRlcm5hbCBtZW1vcnkgdGhhdCBpdCBvbmNlCj4gb2NjdXB5ZWQgd2lsbCBz Y3JhdGNoZWQ/IElzIHRoZSBpbnRlcm5hbCBtZW1vcnkgdGhhdCBpdCBvbmNlIG9jY3VweWVkCj4g d2lsbCAgcmVjb3ZlcmVkPwoKVGhlIG1lbW9yeSBpcyAic2NydWJiZWQiICh0aGF0J3MgdGhlIGV4 YWN0IHdvcmRpbmcgaW4gWGVuKSBiZWZvcmUgZ2l2aW5nCml0IHRvIGEgZG9tVS4gTm90IGFmdGVy IGl0J3MgcmVsZWFzZWQsIGFzIGZhciBhcyBJIGtub3cuCgo+ICAgICAgICBJZiBpdCB3aWxsIGJl IHNjcmF0Y2hlZCx3b3VsZCB5b3Ugc2hvdyBtZSB0aGUgY29ycmVzcG9uZGluZwo+IGNvZGVzIG9y IHRlc3RpbmcgcHJvZ2FtYT9FeHBlY3QgeW91ciByZXBseS4KClRoYXQncyBtb3JlIGEgcXVlc3Rp b24gZm9yIHhlbi1kZXZlbCB0aGFuIGZvciBYQ1AgLyBYQVBJLgoKVGhvbWFzCgoKX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWlsaW5nIGxp c3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFp bG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Fri Jan 11 18:46:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 18:46:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtjcV-0003p6-NU; Fri, 11 Jan 2013 18:46:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtjcT-0003p1-RT for xen-api@lists.xen.org; Fri, 11 Jan 2013 18:46:22 +0000 Received: from [85.158.138.51:15413] by server-1.bemta-3.messagelabs.com id 41/58-08906-8FD50F05; Fri, 11 Jan 2013 18:46:16 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-11.tower-174.messagelabs.com!1357929974!27621631!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=1.6 required=7.0 tests=DEAR_SOMETHING X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8033 invoked from network); 11 Jan 2013 18:46:15 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-11.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Jan 2013 18:46:15 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 91FC9FE131; Fri, 11 Jan 2013 18:49:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=05zZcKfTU iyEvZbOn0mUINPXAUU=; b=r/bjvCXLiZaPgODu6vBPR4E9dqXNjLVIlshReV1ht Y/M5vavBLHn675JtNP3334tKyU6nEOAiEZDFutBQreSGk9XGLBLQ2TdmU/tgMAmF 58GcW+FNOeDqJv4WaCTmlBb03VJOsvESIyEsEbFbl7IuyC8UksMTHe4gHah44d9V sU= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=nTK 7UaBeKve21VhSW4R1FPQZww9WIDWl+tRUI4Q9E7hjQhzMZ1Zu3wCy3y18AOrlu8V V7VrVdKk8u7H2Is3EWhYNtfWVpYOaIFC4fx2aAMvBwZK8sjcPtI3AeUZHoaZjF/3 kkmzzIYPfEYKWSuV6ku7KKdu0ebDfCT/ktNumJNA= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id C4259FE0C7; Fri, 11 Jan 2013 18:49:28 +0000 (UTC) Message-ID: <50F05DF3.10903@goirand.fr> Date: Sat, 12 Jan 2013 02:46:11 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: =?UTF-8?B?572R5a6JLeWNnumUpueoiw==?= References: <399f1e9a.1811f.13c202fb1b9.Coremail.sainrun001@126.com> In-Reply-To: <399f1e9a.1811f.13c202fb1b9.Coremail.sainrun001@126.com> X-Enigmail-Version: 1.4.1 Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Is the internal memory that domU occupyed will scratched? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gMDEvMTAvMjAxMyAxMjo0MSBBTSwg572R5a6JLeWNnumUpueoiyB3cm90ZToKPiAgRGVhciAg U2lyOgo+ICAgICAgICBJIGFtIGEgc3R1ZGVudCBvZiBDb21wdXRlciBTcGVjaWF0eSBpbiBhIHVu aXZlcnNpdHkuICBOb3cgSSBhbQo+IHN0dWR5aW5nIGluIHByaW5jaXBsZSBvZiBYZW4gQ2xvdWQg UGxhdGZvcm0uVGhlcmUgYXJlIGEgZmV3IG9mCj4gcXVlc3Rpb25zIGJvcmluZyBtZSBhbmQgSSBo YXZlIHRvIHNlZWsgaGVscCB0byB5b3UuCj4gICAgICAgIElmIGEgZ3Vlc3Qgb3MgaXMgZGVzdHJv eWVkLGlzIHRoZSBpbnRlcm5hbCBtZW1vcnkgdGhhdCBpdCBvbmNlCj4gb2NjdXB5ZWQgd2lsbCBz Y3JhdGNoZWQ/IElzIHRoZSBpbnRlcm5hbCBtZW1vcnkgdGhhdCBpdCBvbmNlIG9jY3VweWVkCj4g d2lsbCAgcmVjb3ZlcmVkPwoKVGhlIG1lbW9yeSBpcyAic2NydWJiZWQiICh0aGF0J3MgdGhlIGV4 YWN0IHdvcmRpbmcgaW4gWGVuKSBiZWZvcmUgZ2l2aW5nCml0IHRvIGEgZG9tVS4gTm90IGFmdGVy IGl0J3MgcmVsZWFzZWQsIGFzIGZhciBhcyBJIGtub3cuCgo+ICAgICAgICBJZiBpdCB3aWxsIGJl IHNjcmF0Y2hlZCx3b3VsZCB5b3Ugc2hvdyBtZSB0aGUgY29ycmVzcG9uZGluZwo+IGNvZGVzIG9y IHRlc3RpbmcgcHJvZ2FtYT9FeHBlY3QgeW91ciByZXBseS4KClRoYXQncyBtb3JlIGEgcXVlc3Rp b24gZm9yIHhlbi1kZXZlbCB0aGFuIGZvciBYQ1AgLyBYQVBJLgoKVGhvbWFzCgoKX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWlsaW5nIGxp c3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFp bG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Fri Jan 11 18:57:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 18:57:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtjnY-00044n-B7; Fri, 11 Jan 2013 18:57:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtjnW-00044i-UR for xen-api@lists.xen.org; Fri, 11 Jan 2013 18:57:47 +0000 Received: from [85.158.139.83:57119] by server-10.bemta-5.messagelabs.com id A1/4B-13383-AA060F05; Fri, 11 Jan 2013 18:57:46 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1357930665!27539945!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1NjQ0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31392 invoked from network); 11 Jan 2013 18:57:45 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 18:57:45 -0000 X-IronPort-AV: E=Sophos;i="4.84,453,1355097600"; d="scan'208";a="608675" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Jan 2013 18:57:44 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Fri, 11 Jan 2013 18:57:44 +0000 From: James Bulpin To: Dave Scott , "xen-api@lists.xen.org" Date: Fri, 11 Jan 2013 18:58:20 +0000 Thread-Topic: running latest dev versions of xenopsd on Debian/Ubuntu Thread-Index: Ac3qkUg0wxSPpNjMT6W0axZdOHbZBAFmECsg Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E5B3E64@LONPMAILBOX01.citrite.net> References: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Feeling brave I've tried this on CentOS 6.3 with Xen 4.2. Here's how it went... I used the "Software development workstation" installation base for CentOS 6.3 (x86_64) which meant I got a certain amount of virtualisation infrastructure including a "virbr0" NATed bridge. I prefer basic L2 bridging so I manually created a xenbr0 in the traditional manner. I installed Xen 4.2.1 and a suitable 3.4 kernel. I chose to compile vncterm from the source at https://github.com/xen-org/vncterm - this uses the old xs.h filename for the xenstore headers so I have to change this to xenstore.h to make it build against 4.2. I used the latest binary download of opam to install ocaml 4.00.1. Being a local installation this meant the paths differed from Dave's tutorial being ~/.opam/4.00.1/ instead of ~/.opam/system/ I hit an error building xenopsd because it was depending on xenctrl 4.1.0 rather than just the latest version - Dave fixed this in his repo. To run xenopsd I have to uncomment the vncterm config line in xenopsd.conf to point to the binary. In the same file I had to uncomment the hvmloader line and remove the quotes (xenopsd was treating them literally) For the VM storage I chose to use LVM to fit with the current "phy:" constraint. Trying to start a PV guest hit a few problems: 1. xenopsd gave an error saying it had no bootable devices - this was because the devices list was hard wired to empty in the CLI, Dave fixed this in the repo 2. xenopsd assumes that pygrub has the --default_args, --extra_args and --vm arguments present in the XenServer/XCP version of pygrub but not present in the Xen 4.2 version. I patched the latter to add these. 3. xenopsd complains of an invalid result from the domain builder. Dave is currently working on this. Trying a HVM guest led to a different set of challenges: 1. xenopsd was hanging waiting to plug the VBD - this turns out to be because the hotplug scripts were not running because xl had disabled them (by default xl runs these scripts itself but this can be overridden by setting "run_hotplug_scripts=0" in /etc/xen/xl.conf). I suspect this problem will go away when Rob does the xenopsd libxl port. 2. xenopsd is using a VIF hotplug scripts that is very XenServer/XCP centric and doesn't run to completion on CentOS 6.3. This was configured in the automatically generaled xenopsd.conf so I instead changed this to use /etc/xen/scripts/vif-bridge instead. 3. xenopsd doesn't put the "bridge" key in the usual backend xenstore location (/local/domain/0/backend/vif//) so the Xen 4.2 vif script defaulted to the first bridge, not the one I had configured. 4. xenopsd was hanging waiting for a hotplug event on the VIF but was watching /xapi//vif//hotplug which would never be touched by Xen 4.2 hotplug scripts. To workaround this I manually created that entry after each VM start 5. qemu-dm-wrapper would always silently fail when run by xenopsd but not when run interactively. This is because it tried to setrlimit a value with the soft limit being higher than the hard limit. I put in a simple fix to avoid this. 6. qemu-dm-wrapper would always fail because it hard-coded the path to xenstore-write in /usr/sbin but it's in /usr/bin on my system. I fixed this locally but w search path will be useful in the future. So in summary with a few tweaks and workarounds I can no run HVM guests on CentOS 6.3 using xenopsd. I encourage others to try this on your distro of choice. Bugs have been filed at https://github.com/xen-org/xenopsd/issues Cheers, James > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Dave Scott > Sent: 04 January 2013 15:44 > To: xen-api@lists.xen.org > Subject: [Xen-API] running latest dev versions of xenopsd on > Debian/Ubuntu > > Hi, > > I've written a wiki page describing how to build the latest development > version of "xenopsd" (and its dependencies) from source: > > http://wiki.xen.org/wiki/Building_Xenopsd > > "xenopsd" is the name of the domain manager of the XCP toolstack -- it > is responsible for starting, stopping, migrating VMs. > > Being able to build the development version is really useful if you > want to: > * check out a new feature > * reproduce a bug > * test a fix > > Let me know if you try this and have any problems or suggestions! > > There are a couple more components of the XCP toolstack that need some > fixups so they can build easily, in particular: > * squeezed: manages memory ballooning > * networkd: configures VM networking > * rrdd: collects and archives performance statistics > * xapi: manages the overall resource pool > > Hopefully we can work on these one-by-one until they are all as easy to > build as xenopsd. > > Cheers, > Dave > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 18:57:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 18:57:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtjnY-00044n-B7; Fri, 11 Jan 2013 18:57:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtjnW-00044i-UR for xen-api@lists.xen.org; Fri, 11 Jan 2013 18:57:47 +0000 Received: from [85.158.139.83:57119] by server-10.bemta-5.messagelabs.com id A1/4B-13383-AA060F05; Fri, 11 Jan 2013 18:57:46 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1357930665!27539945!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1NjQ0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31392 invoked from network); 11 Jan 2013 18:57:45 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 18:57:45 -0000 X-IronPort-AV: E=Sophos;i="4.84,453,1355097600"; d="scan'208";a="608675" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Jan 2013 18:57:44 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Fri, 11 Jan 2013 18:57:44 +0000 From: James Bulpin To: Dave Scott , "xen-api@lists.xen.org" Date: Fri, 11 Jan 2013 18:58:20 +0000 Thread-Topic: running latest dev versions of xenopsd on Debian/Ubuntu Thread-Index: Ac3qkUg0wxSPpNjMT6W0axZdOHbZBAFmECsg Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E5B3E64@LONPMAILBOX01.citrite.net> References: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Feeling brave I've tried this on CentOS 6.3 with Xen 4.2. Here's how it went... I used the "Software development workstation" installation base for CentOS 6.3 (x86_64) which meant I got a certain amount of virtualisation infrastructure including a "virbr0" NATed bridge. I prefer basic L2 bridging so I manually created a xenbr0 in the traditional manner. I installed Xen 4.2.1 and a suitable 3.4 kernel. I chose to compile vncterm from the source at https://github.com/xen-org/vncterm - this uses the old xs.h filename for the xenstore headers so I have to change this to xenstore.h to make it build against 4.2. I used the latest binary download of opam to install ocaml 4.00.1. Being a local installation this meant the paths differed from Dave's tutorial being ~/.opam/4.00.1/ instead of ~/.opam/system/ I hit an error building xenopsd because it was depending on xenctrl 4.1.0 rather than just the latest version - Dave fixed this in his repo. To run xenopsd I have to uncomment the vncterm config line in xenopsd.conf to point to the binary. In the same file I had to uncomment the hvmloader line and remove the quotes (xenopsd was treating them literally) For the VM storage I chose to use LVM to fit with the current "phy:" constraint. Trying to start a PV guest hit a few problems: 1. xenopsd gave an error saying it had no bootable devices - this was because the devices list was hard wired to empty in the CLI, Dave fixed this in the repo 2. xenopsd assumes that pygrub has the --default_args, --extra_args and --vm arguments present in the XenServer/XCP version of pygrub but not present in the Xen 4.2 version. I patched the latter to add these. 3. xenopsd complains of an invalid result from the domain builder. Dave is currently working on this. Trying a HVM guest led to a different set of challenges: 1. xenopsd was hanging waiting to plug the VBD - this turns out to be because the hotplug scripts were not running because xl had disabled them (by default xl runs these scripts itself but this can be overridden by setting "run_hotplug_scripts=0" in /etc/xen/xl.conf). I suspect this problem will go away when Rob does the xenopsd libxl port. 2. xenopsd is using a VIF hotplug scripts that is very XenServer/XCP centric and doesn't run to completion on CentOS 6.3. This was configured in the automatically generaled xenopsd.conf so I instead changed this to use /etc/xen/scripts/vif-bridge instead. 3. xenopsd doesn't put the "bridge" key in the usual backend xenstore location (/local/domain/0/backend/vif//) so the Xen 4.2 vif script defaulted to the first bridge, not the one I had configured. 4. xenopsd was hanging waiting for a hotplug event on the VIF but was watching /xapi//vif//hotplug which would never be touched by Xen 4.2 hotplug scripts. To workaround this I manually created that entry after each VM start 5. qemu-dm-wrapper would always silently fail when run by xenopsd but not when run interactively. This is because it tried to setrlimit a value with the soft limit being higher than the hard limit. I put in a simple fix to avoid this. 6. qemu-dm-wrapper would always fail because it hard-coded the path to xenstore-write in /usr/sbin but it's in /usr/bin on my system. I fixed this locally but w search path will be useful in the future. So in summary with a few tweaks and workarounds I can no run HVM guests on CentOS 6.3 using xenopsd. I encourage others to try this on your distro of choice. Bugs have been filed at https://github.com/xen-org/xenopsd/issues Cheers, James > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Dave Scott > Sent: 04 January 2013 15:44 > To: xen-api@lists.xen.org > Subject: [Xen-API] running latest dev versions of xenopsd on > Debian/Ubuntu > > Hi, > > I've written a wiki page describing how to build the latest development > version of "xenopsd" (and its dependencies) from source: > > http://wiki.xen.org/wiki/Building_Xenopsd > > "xenopsd" is the name of the domain manager of the XCP toolstack -- it > is responsible for starting, stopping, migrating VMs. > > Being able to build the development version is really useful if you > want to: > * check out a new feature > * reproduce a bug > * test a fix > > Let me know if you try this and have any problems or suggestions! > > There are a couple more components of the XCP toolstack that need some > fixups so they can build easily, in particular: > * squeezed: manages memory ballooning > * networkd: configures VM networking > * rrdd: collects and archives performance statistics > * xapi: manages the overall resource pool > > Hopefully we can work on these one-by-one until they are all as easy to > build as xenopsd. > > Cheers, > Dave > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 11 19:05:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 19:05:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttjv6-0004E5-60; Fri, 11 Jan 2013 19:05:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Ttjv4-0004Dx-CR; Fri, 11 Jan 2013 19:05:34 +0000 Received: from [193.109.254.147:59021] by server-10.bemta-14.messagelabs.com id F7/98-13263-D7260F05; Fri, 11 Jan 2013 19:05:33 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1357931131!8652093!1 X-Originating-IP: [209.85.216.182] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4556 invoked from network); 11 Jan 2013 19:05:32 -0000 Received: from mail-qc0-f182.google.com (HELO mail-qc0-f182.google.com) (209.85.216.182) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 19:05:32 -0000 Received: by mail-qc0-f182.google.com with SMTP id k19so1340067qcs.27 for ; Fri, 11 Jan 2013 11:05:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Gc0BW/Dtp5qSnyPnAyaGab/9R48UoulrjhZYDxl9OgQ=; b=NqEhVE/u7KpRa6WYC7ftVSsiksDLuARW8vYGM67Gdb81WQOUMlcyrXHa6blPAiAQlz F1an2vvpCiqj0tPXnhE8gIuc7jEM9wFEzAFtaFt2QyaTadSscEla+gg1O7aNQJVO3K7j Uv5HvlxlgdMTNs45EAyfuoJhkhgTXqoRA80bsQOVprrip1SG/fIsQam824OcD5nK9tYW FvCRhQrCeFIrNWRzH1H14+ZJwdIG62BXV29yi6fUoImi2AVrzwK4ksBjk/8oa0VO4pCQ JLr64ev3jBKOVnyVJNsOuAPFcyx88hRDCiXc4N1Z5uJGNwV5NoGEeh8p6VHq6TkKyrpf 2ejg== MIME-Version: 1.0 Received: by 10.229.69.95 with SMTP id y31mr15063862qci.5.1357931131088; Fri, 11 Jan 2013 11:05:31 -0800 (PST) Received: by 10.229.17.19 with HTTP; Fri, 11 Jan 2013 11:05:30 -0800 (PST) In-Reply-To: <1357896054.9456.92.camel@zakaz.uk.xensource.com> References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> <1357896054.9456.92.camel@zakaz.uk.xensource.com> Date: Sat, 12 Jan 2013 00:35:30 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Ian Campbell Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1709506479411323812==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1709506479411323812== Content-Type: multipart/alternative; boundary=00032557eb82b2b17404d307fa69 --00032557eb82b2b17404d307fa69 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jan 11, 2013 at 2:50 PM, Ian Campbell wrote: > On Thu, 2013-01-10 at 21:37 +0000, Rushikesh Jadhav wrote: > > > I have also stopped perusing the file and error. Its just bugging me > > every hour :( > > I'm surprised that this error and file is never reported anywhere and > > I don't think my Windows DomU is any special to generate such error. > > A bit more googling suggests that TXF is Transactional NTFS > http://en.wikipedia.org/wiki/Transactional_NTFS > > Furthermore http://msdn.microsoft.com/en-us/library/cc704588.aspx > ("NTSTATUS values") tells me that 0xC01A002B is STATUS_LOG_STATE_INVALID > "The log service is not in the correct state to perform a requested > action." > > It might be wise to run the Windows equivalent of fsck. > > That wiki page suggests that TXF is not widely used, perhaps one of your > applications in the VM is one of the minority which do use it? > > This seems to me like an issue which is internal to the VM but it might > still be useful to know the guest configuration. Are you using PV > drivers at all? Can you post your guest configuration please. What > version of Xen are you running etc. > > Ian. > > Hi Ian, Thanks for checking. Its a simple Windows 2008 VM with default xs-tools PV drivers hosted on XCP1.1 with Xen 3.4.2. It has 2 drives Local C: and iSCSI LUN D: Local VM Disk format is lvm over iscsi and the extra disk is directly mounted via iSCSI using iSCSI initiator within VM. - Rushikesh --00032557eb82b2b17404d307fa69 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Fri, Jan 11, 2013 at 2:50 PM, Ian Cam= pbell <Ian.Campbell@citrix.com> wrote:
On Thu, 2013-01-10 at 21:37 +0000, Rushikesh Jadhav wrote= :

> I have also stopped perusing the file and error. Its just bugging me > every hour :(
> I'm surprised that this error and file is never reported anywhere = and
> I don't think my Windows DomU is any special to generate such erro= r.

A bit more googling suggests that TXF is Transactional NTFS
http://en.wikipedia.org/wiki/Transactional_NTFS

Furthermore http://msdn.microsoft.com/en-us/library/cc704588.aspx<= /a>
("NTSTATUS values") tells me that 0xC01A002B is STATUS_LOG_STATE_= INVALID
"The log service is not in the correct state to perform a requested action."

It might be wise to run the Windows equivalent of fsck.

That wiki page suggests that TXF is not widely used, perhaps one of your applications in the VM is one of the minority which do use it?

This seems to me like an issue which is internal to the VM but it might
still be useful to know the guest configuration. Are you using PV
drivers at all? Can you post your guest configuration please. What
version of Xen are you running etc.

Ian.


--00032557eb82b2b17404d307fa69-- --===============1709506479411323812== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1709506479411323812==-- From xen-api-bounces@lists.xen.org Fri Jan 11 19:05:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 11 Jan 2013 19:05:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ttjv6-0004E5-60; Fri, 11 Jan 2013 19:05:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Ttjv4-0004Dx-CR; Fri, 11 Jan 2013 19:05:34 +0000 Received: from [193.109.254.147:59021] by server-10.bemta-14.messagelabs.com id F7/98-13263-D7260F05; Fri, 11 Jan 2013 19:05:33 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1357931131!8652093!1 X-Originating-IP: [209.85.216.182] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4556 invoked from network); 11 Jan 2013 19:05:32 -0000 Received: from mail-qc0-f182.google.com (HELO mail-qc0-f182.google.com) (209.85.216.182) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jan 2013 19:05:32 -0000 Received: by mail-qc0-f182.google.com with SMTP id k19so1340067qcs.27 for ; Fri, 11 Jan 2013 11:05:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Gc0BW/Dtp5qSnyPnAyaGab/9R48UoulrjhZYDxl9OgQ=; b=NqEhVE/u7KpRa6WYC7ftVSsiksDLuARW8vYGM67Gdb81WQOUMlcyrXHa6blPAiAQlz F1an2vvpCiqj0tPXnhE8gIuc7jEM9wFEzAFtaFt2QyaTadSscEla+gg1O7aNQJVO3K7j Uv5HvlxlgdMTNs45EAyfuoJhkhgTXqoRA80bsQOVprrip1SG/fIsQam824OcD5nK9tYW FvCRhQrCeFIrNWRzH1H14+ZJwdIG62BXV29yi6fUoImi2AVrzwK4ksBjk/8oa0VO4pCQ JLr64ev3jBKOVnyVJNsOuAPFcyx88hRDCiXc4N1Z5uJGNwV5NoGEeh8p6VHq6TkKyrpf 2ejg== MIME-Version: 1.0 Received: by 10.229.69.95 with SMTP id y31mr15063862qci.5.1357931131088; Fri, 11 Jan 2013 11:05:31 -0800 (PST) Received: by 10.229.17.19 with HTTP; Fri, 11 Jan 2013 11:05:30 -0800 (PST) In-Reply-To: <1357896054.9456.92.camel@zakaz.uk.xensource.com> References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> <1357896054.9456.92.camel@zakaz.uk.xensource.com> Date: Sat, 12 Jan 2013 00:35:30 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Ian Campbell Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1709506479411323812==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1709506479411323812== Content-Type: multipart/alternative; boundary=00032557eb82b2b17404d307fa69 --00032557eb82b2b17404d307fa69 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jan 11, 2013 at 2:50 PM, Ian Campbell wrote: > On Thu, 2013-01-10 at 21:37 +0000, Rushikesh Jadhav wrote: > > > I have also stopped perusing the file and error. Its just bugging me > > every hour :( > > I'm surprised that this error and file is never reported anywhere and > > I don't think my Windows DomU is any special to generate such error. > > A bit more googling suggests that TXF is Transactional NTFS > http://en.wikipedia.org/wiki/Transactional_NTFS > > Furthermore http://msdn.microsoft.com/en-us/library/cc704588.aspx > ("NTSTATUS values") tells me that 0xC01A002B is STATUS_LOG_STATE_INVALID > "The log service is not in the correct state to perform a requested > action." > > It might be wise to run the Windows equivalent of fsck. > > That wiki page suggests that TXF is not widely used, perhaps one of your > applications in the VM is one of the minority which do use it? > > This seems to me like an issue which is internal to the VM but it might > still be useful to know the guest configuration. Are you using PV > drivers at all? Can you post your guest configuration please. What > version of Xen are you running etc. > > Ian. > > Hi Ian, Thanks for checking. Its a simple Windows 2008 VM with default xs-tools PV drivers hosted on XCP1.1 with Xen 3.4.2. It has 2 drives Local C: and iSCSI LUN D: Local VM Disk format is lvm over iscsi and the extra disk is directly mounted via iSCSI using iSCSI initiator within VM. - Rushikesh --00032557eb82b2b17404d307fa69 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Fri, Jan 11, 2013 at 2:50 PM, Ian Cam= pbell <Ian.Campbell@citrix.com> wrote:
On Thu, 2013-01-10 at 21:37 +0000, Rushikesh Jadhav wrote= :

> I have also stopped perusing the file and error. Its just bugging me > every hour :(
> I'm surprised that this error and file is never reported anywhere = and
> I don't think my Windows DomU is any special to generate such erro= r.

A bit more googling suggests that TXF is Transactional NTFS
http://en.wikipedia.org/wiki/Transactional_NTFS

Furthermore http://msdn.microsoft.com/en-us/library/cc704588.aspx<= /a>
("NTSTATUS values") tells me that 0xC01A002B is STATUS_LOG_STATE_= INVALID
"The log service is not in the correct state to perform a requested action."

It might be wise to run the Windows equivalent of fsck.

That wiki page suggests that TXF is not widely used, perhaps one of your applications in the VM is one of the minority which do use it?

This seems to me like an issue which is internal to the VM but it might
still be useful to know the guest configuration. Are you using PV
drivers at all? Can you post your guest configuration please. What
version of Xen are you running etc.

Ian.


--00032557eb82b2b17404d307fa69-- --===============1709506479411323812== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1709506479411323812==-- From xen-api-bounces@lists.xen.org Sat Jan 12 21:21:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 12 Jan 2013 21:21:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tu8W9-00064R-Pd; Sat, 12 Jan 2013 21:21:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tu8W8-00064M-1C for xen-api@lists.xen.org; Sat, 12 Jan 2013 21:21:28 +0000 Received: from [193.109.254.147:57158] by server-7.bemta-14.messagelabs.com id 0C/90-08102-7D3D1F05; Sat, 12 Jan 2013 21:21:27 +0000 X-Env-Sender: prvs=172486e599=k.ruland@asens.nl X-Msg-Ref: server-13.tower-27.messagelabs.com!1358025685!8614496!1 X-Originating-IP: [37.153.199.163] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25570 invoked from network); 12 Jan 2013 21:21:25 -0000 Received: from mail.asens.net (HELO asens.net) (37.153.199.163) by server-13.tower-27.messagelabs.com with SMTP; 12 Jan 2013 21:21:25 -0000 Received: from EXCH01.asp.asens.net by mail.asens.net (MDaemon PRO v9.6.1) with ESMTP id md50003373676.msg for ; Sat, 12 Jan 2013 22:21:16 +0100 Received: from EXCH01.asp.asens.net (172.23.1.21) by EXCH01.asp.asens.net (172.23.1.21) with Microsoft SMTP Server (TLS) id 15.0.516.32; Sat, 12 Jan 2013 22:21:05 +0100 Received: from EXCH01.asp.asens.net ([fe80::5596:a77e:8f70:735f]) by EXCH01.asp.asens.net ([fe80::5596:a77e:8f70:735f%15]) with mapi id 15.00.0516.029; Sat, 12 Jan 2013 22:21:05 +0100 From: Asens - Karel Ruland To: "xen-api@lists.xen.org" Thread-Topic: Xen 1.6 server 2012 instable Thread-Index: AQHN8Qq6PmdNkT0w50ikv7xi6QHQUA== Date: Sat, 12 Jan 2013 21:21:05 +0000 Message-ID: <856bc5c0fb13405fb299edcdc943f000@EXCH01.asp.asens.net> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-Spam-Processed: mail.asens.net, Sat, 12 Jan 2013 22:21:16 +0100 (not processed: spam filter heuristic analysis disabled) X-MDRemoteIP: 172.23.1.21 X-Return-Path: prvs=172486e599=k.ruland@asens.nl X-Envelope-From: k.ruland@asens.nl X-MDaemon-Deliver-To: xen-api@lists.xen.org Subject: [Xen-API] Xen 1.6 server 2012 instable X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6858871367381825175==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6858871367381825175== Content-Language: nl-NL Content-Type: multipart/alternative; boundary="_000_856bc5c0fb13405fb299edcdc943f000EXCH01aspasensnet_" --_000_856bc5c0fb13405fb299edcdc943f000EXCH01aspasensnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable After upgrading from 1.5 to 1.6 our farm is unstable. Even when I install = new windows 2012 server it's behavior is unpredictable. 6.0.2 hotfix 9 doesn't solve the problem. Please help. Verzonden met mijn Windows Phone --_000_856bc5c0fb13405fb299edcdc943f000EXCH01aspasensnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: <10AC736CDD267F478D82469149D03D3B@asp.asens.net> Content-Transfer-Encoding: quoted-printable
After upgr= ading from 1.5 to 1.6 our farm is unstable.  Even when I install = new windows 2012 server it's behavior is unpredictable. 
6.0.2 hotfix 9 doesn't solve the problem.  Please help.

Verzonden met mijn Windows Phone
--_000_856bc5c0fb13405fb299edcdc943f000EXCH01aspasensnet_-- --===============6858871367381825175== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6858871367381825175==-- From xen-api-bounces@lists.xen.org Sat Jan 12 21:21:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 12 Jan 2013 21:21:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tu8W9-00064R-Pd; Sat, 12 Jan 2013 21:21:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tu8W8-00064M-1C for xen-api@lists.xen.org; Sat, 12 Jan 2013 21:21:28 +0000 Received: from [193.109.254.147:57158] by server-7.bemta-14.messagelabs.com id 0C/90-08102-7D3D1F05; Sat, 12 Jan 2013 21:21:27 +0000 X-Env-Sender: prvs=172486e599=k.ruland@asens.nl X-Msg-Ref: server-13.tower-27.messagelabs.com!1358025685!8614496!1 X-Originating-IP: [37.153.199.163] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25570 invoked from network); 12 Jan 2013 21:21:25 -0000 Received: from mail.asens.net (HELO asens.net) (37.153.199.163) by server-13.tower-27.messagelabs.com with SMTP; 12 Jan 2013 21:21:25 -0000 Received: from EXCH01.asp.asens.net by mail.asens.net (MDaemon PRO v9.6.1) with ESMTP id md50003373676.msg for ; Sat, 12 Jan 2013 22:21:16 +0100 Received: from EXCH01.asp.asens.net (172.23.1.21) by EXCH01.asp.asens.net (172.23.1.21) with Microsoft SMTP Server (TLS) id 15.0.516.32; Sat, 12 Jan 2013 22:21:05 +0100 Received: from EXCH01.asp.asens.net ([fe80::5596:a77e:8f70:735f]) by EXCH01.asp.asens.net ([fe80::5596:a77e:8f70:735f%15]) with mapi id 15.00.0516.029; Sat, 12 Jan 2013 22:21:05 +0100 From: Asens - Karel Ruland To: "xen-api@lists.xen.org" Thread-Topic: Xen 1.6 server 2012 instable Thread-Index: AQHN8Qq6PmdNkT0w50ikv7xi6QHQUA== Date: Sat, 12 Jan 2013 21:21:05 +0000 Message-ID: <856bc5c0fb13405fb299edcdc943f000@EXCH01.asp.asens.net> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-Spam-Processed: mail.asens.net, Sat, 12 Jan 2013 22:21:16 +0100 (not processed: spam filter heuristic analysis disabled) X-MDRemoteIP: 172.23.1.21 X-Return-Path: prvs=172486e599=k.ruland@asens.nl X-Envelope-From: k.ruland@asens.nl X-MDaemon-Deliver-To: xen-api@lists.xen.org Subject: [Xen-API] Xen 1.6 server 2012 instable X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6858871367381825175==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6858871367381825175== Content-Language: nl-NL Content-Type: multipart/alternative; boundary="_000_856bc5c0fb13405fb299edcdc943f000EXCH01aspasensnet_" --_000_856bc5c0fb13405fb299edcdc943f000EXCH01aspasensnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable After upgrading from 1.5 to 1.6 our farm is unstable. Even when I install = new windows 2012 server it's behavior is unpredictable. 6.0.2 hotfix 9 doesn't solve the problem. Please help. Verzonden met mijn Windows Phone --_000_856bc5c0fb13405fb299edcdc943f000EXCH01aspasensnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: <10AC736CDD267F478D82469149D03D3B@asp.asens.net> Content-Transfer-Encoding: quoted-printable
After upgr= ading from 1.5 to 1.6 our farm is unstable.  Even when I install = new windows 2012 server it's behavior is unpredictable. 
6.0.2 hotfix 9 doesn't solve the problem.  Please help.

Verzonden met mijn Windows Phone
--_000_856bc5c0fb13405fb299edcdc943f000EXCH01aspasensnet_-- --===============6858871367381825175== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6858871367381825175==-- From xen-api-bounces@lists.xen.org Sat Jan 12 21:30:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 12 Jan 2013 21:30:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tu8eU-00069w-IW; Sat, 12 Jan 2013 21:30:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tu8eS-00069r-Oi for xen-api@lists.xen.org; Sat, 12 Jan 2013 21:30:05 +0000 Received: from [85.158.143.99:16049] by server-3.bemta-4.messagelabs.com id 1A/AB-19220-BD5D1F05; Sat, 12 Jan 2013 21:30:03 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1358026201!27677210!1 X-Originating-IP: [209.85.216.177] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11970 invoked from network); 12 Jan 2013 21:30:02 -0000 Received: from mail-qc0-f177.google.com (HELO mail-qc0-f177.google.com) (209.85.216.177) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jan 2013 21:30:02 -0000 Received: by mail-qc0-f177.google.com with SMTP id u28so1795510qcs.22 for ; Sat, 12 Jan 2013 13:30:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=C3lVYh01rmBukPOqrpQPv6rFy9RN7STF2IPRk8XKONM=; b=zztqZYi2i8J9q0jmD6oIXQQrPMRL899maNR84aOiE3uprotTpyMnY6mQs+6di532j8 5rnpZsp0KUcJnsAEoBGcHic8Lb2rkln1RU8jDS6t/sNWPfaZ1/3Rk+2pTkSyKlLS+PlV rViVQ6C8hxnNiqgtjXgrlGa3PK9ZsKJ0irxfvguWxC8ZZWkFzW4ybIjlvoci/vNWfhnA 1v3QvvCk6POvhmTN4e4sY2luQXHBeG3bh3ZgYyfVuWbrO37JlopqYgiAFvt9zN+zA+Zm COcy7PqVr69sfNe83/xJ/Mzgzp5m4lSsXit9WD2lrJPCFY1oWBQZDg56R8LB3vbI1Ck0 Z+4w== MIME-Version: 1.0 Received: by 10.49.121.40 with SMTP id lh8mr78536004qeb.30.1358026201502; Sat, 12 Jan 2013 13:30:01 -0800 (PST) Received: by 10.229.17.19 with HTTP; Sat, 12 Jan 2013 13:30:01 -0800 (PST) In-Reply-To: <856bc5c0fb13405fb299edcdc943f000@EXCH01.asp.asens.net> References: <856bc5c0fb13405fb299edcdc943f000@EXCH01.asp.asens.net> Date: Sun, 13 Jan 2013 03:00:01 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Asens - Karel Ruland Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Xen 1.6 server 2012 instable X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5299121028286870327==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5299121028286870327== Content-Type: multipart/alternative; boundary=047d7bdc1be45615c404d31e1d51 --047d7bdc1be45615c404d31e1d51 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Jan 13, 2013 at 2:51 AM, Asens - Karel Ruland wrote: > After upgrading from 1.5 to 1.6 our farm is unstable. Even when I > install new windows 2012 server it's behavior is unpredictable. > 6.0.2 hotfix 9 doesn't solve the problem. Please help. > > Verzonden met mijn Windows Phone > > In order to help, we will need more details about the unpredictable behaviour & xensource log at the time of unpredictable behaviour. - Rushikesh > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --047d7bdc1be45615c404d31e1d51 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Sun, Jan 13, 2013 at 2:51 AM, Asens -= Karel Ruland <k.ruland@asens.nl> wrote:
After upgradin= g from 1.5 to 1.6 our farm is unstable.=A0 Even when I install=A0 new windo= ws 2012 server it's behavior is unpredictable.=A0
6.0.2 hotfix 9 doesn't solve the problem.=A0 Please help.

Verzonden met mijn Windows Phone


In order to help, we will need more details about= the unpredictable behaviour & xensource log at the time of unpredictab= le behaviour.

- Rushikesh
=A0
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--047d7bdc1be45615c404d31e1d51-- --===============5299121028286870327== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5299121028286870327==-- From xen-api-bounces@lists.xen.org Sat Jan 12 21:30:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 12 Jan 2013 21:30:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tu8eU-00069w-IW; Sat, 12 Jan 2013 21:30:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1Tu8eS-00069r-Oi for xen-api@lists.xen.org; Sat, 12 Jan 2013 21:30:05 +0000 Received: from [85.158.143.99:16049] by server-3.bemta-4.messagelabs.com id 1A/AB-19220-BD5D1F05; Sat, 12 Jan 2013 21:30:03 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1358026201!27677210!1 X-Originating-IP: [209.85.216.177] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11970 invoked from network); 12 Jan 2013 21:30:02 -0000 Received: from mail-qc0-f177.google.com (HELO mail-qc0-f177.google.com) (209.85.216.177) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jan 2013 21:30:02 -0000 Received: by mail-qc0-f177.google.com with SMTP id u28so1795510qcs.22 for ; Sat, 12 Jan 2013 13:30:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=C3lVYh01rmBukPOqrpQPv6rFy9RN7STF2IPRk8XKONM=; b=zztqZYi2i8J9q0jmD6oIXQQrPMRL899maNR84aOiE3uprotTpyMnY6mQs+6di532j8 5rnpZsp0KUcJnsAEoBGcHic8Lb2rkln1RU8jDS6t/sNWPfaZ1/3Rk+2pTkSyKlLS+PlV rViVQ6C8hxnNiqgtjXgrlGa3PK9ZsKJ0irxfvguWxC8ZZWkFzW4ybIjlvoci/vNWfhnA 1v3QvvCk6POvhmTN4e4sY2luQXHBeG3bh3ZgYyfVuWbrO37JlopqYgiAFvt9zN+zA+Zm COcy7PqVr69sfNe83/xJ/Mzgzp5m4lSsXit9WD2lrJPCFY1oWBQZDg56R8LB3vbI1Ck0 Z+4w== MIME-Version: 1.0 Received: by 10.49.121.40 with SMTP id lh8mr78536004qeb.30.1358026201502; Sat, 12 Jan 2013 13:30:01 -0800 (PST) Received: by 10.229.17.19 with HTTP; Sat, 12 Jan 2013 13:30:01 -0800 (PST) In-Reply-To: <856bc5c0fb13405fb299edcdc943f000@EXCH01.asp.asens.net> References: <856bc5c0fb13405fb299edcdc943f000@EXCH01.asp.asens.net> Date: Sun, 13 Jan 2013 03:00:01 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Asens - Karel Ruland Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Xen 1.6 server 2012 instable X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5299121028286870327==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5299121028286870327== Content-Type: multipart/alternative; boundary=047d7bdc1be45615c404d31e1d51 --047d7bdc1be45615c404d31e1d51 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Jan 13, 2013 at 2:51 AM, Asens - Karel Ruland wrote: > After upgrading from 1.5 to 1.6 our farm is unstable. Even when I > install new windows 2012 server it's behavior is unpredictable. > 6.0.2 hotfix 9 doesn't solve the problem. Please help. > > Verzonden met mijn Windows Phone > > In order to help, we will need more details about the unpredictable behaviour & xensource log at the time of unpredictable behaviour. - Rushikesh > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --047d7bdc1be45615c404d31e1d51 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Sun, Jan 13, 2013 at 2:51 AM, Asens -= Karel Ruland <k.ruland@asens.nl> wrote:
After upgradin= g from 1.5 to 1.6 our farm is unstable.=A0 Even when I install=A0 new windo= ws 2012 server it's behavior is unpredictable.=A0
6.0.2 hotfix 9 doesn't solve the problem.=A0 Please help.

Verzonden met mijn Windows Phone


In order to help, we will need more details about= the unpredictable behaviour & xensource log at the time of unpredictab= le behaviour.

- Rushikesh
=A0
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--047d7bdc1be45615c404d31e1d51-- --===============5299121028286870327== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5299121028286870327==-- From xen-api-bounces@lists.xen.org Sun Jan 13 23:55:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 13 Jan 2013 23:55:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TuXOm-00062Q-F9; Sun, 13 Jan 2013 23:55:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TuXOk-00062I-RL for xen-api@lists.xen.org; Sun, 13 Jan 2013 23:55:31 +0000 Received: from [85.158.139.211:26569] by server-8.bemta-5.messagelabs.com id 13/F9-15003-17943F05; Sun, 13 Jan 2013 23:55:29 +0000 X-Env-Sender: spahmatthew@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1358121326!21198203!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27643 invoked from network); 13 Jan 2013 23:55:28 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jan 2013 23:55:28 -0000 Received: by mail-pa0-f54.google.com with SMTP id bi5so1915361pad.41 for ; Sun, 13 Jan 2013 15:55:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=T6LMnYHzlBasTu8axQ43TZztLP+9Hpn3ofj4kqRuU8A=; b=mRMTV8CCybb8CiWm2hmxWrvWyI+x5FO/eY2DBa3w7jBn7iOJ8epKk3xmAuXOMFJjT6 ni4qSi8i//mQrIm0JXtISxgKeNqm24K3mMQAaxSqWOagE/q5MxIBQPgx7tpEuitczh1X q8Rm1mZUJ7dyZD3WvWukjssnLUOKqeOiH2XgJaGE8n6svqk8z5ca7dpbXep9MKo9hUHn /gztc363h8u8Ehl01o569Q/IRG1AwRypNfayNzreWz1DlEckoRLG2V3fUMHVGruX21jh tDNq9vWIAaXAMC32RdYTz/EtPowbQhGp+k6pQAREXG5qSsakTBSVrhRwqNKJOYtd2fp0 uu7w== MIME-Version: 1.0 Received: by 10.68.236.2 with SMTP id uq2mr247387595pbc.55.1358121326405; Sun, 13 Jan 2013 15:55:26 -0800 (PST) Received: by 10.68.203.72 with HTTP; Sun, 13 Jan 2013 15:55:26 -0800 (PST) Date: Sun, 13 Jan 2013 15:55:26 -0800 Message-ID: From: Matthew Spah To: xen-api@lists.xen.org Subject: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5541664166209274419==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5541664166209274419== Content-Type: multipart/alternative; boundary=047d7b33d14838e6fd04d3344361 --047d7b33d14838e6fd04d3344361 Content-Type: text/plain; charset=ISO-8859-1 Hey everyone, I'm currently testing and documenting the qos parameters for VIF interfaces. I've set up two VMs with VIF interfaces attached to an internal network. I've set the following qos parameters on each VIF interface. *xe vif-param-set uuid= qos_algorithm_type=ratelimit* *xe vif-param-set uuid= qos_algorithm_params:kbps=100* iperf is showing me bandwidth rates between the two VMS that aren't limited to 100 kbps. Am I missing something? -- - Matthew Spah Computer Information Sciences Tutor for Everett Community College Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc Xenapi Admin Project Member http://xenapiadmin.com CompTIA Security+ Certified and Cisco CCNA Certified Arlington, WA Cell 425-319-8676 "And all we ever were Just zeroes and ones" - Trent Reznor "If you want to make enemies, try to change something." - Woodrow T. Wilson --047d7b33d14838e6fd04d3344361 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hey everyone,

I'm currently testing and documenting = the qos parameters for VIF interfaces. I've set up two VMs with VIF int= erfaces attached to an internal network. I've set the following qos par= ameters on each VIF interface.

xe vif-param-set uuid=3D<VIF UUID> qos_algorit= hm_type=3Dratelimit
xe vif-param-set uuid=3D<VIF U= UID> qos_algorithm_params:kbps=3D100
=A0 =A0
ipe= rf is showing me bandwidth rates between the two VMS that aren't limite= d to 100 kbps. Am I missing something?=A0

--
- Matthew Spah
Computer Information Sciences Tutor= for Everett Community College
Electronic Monitoring Jr. Systems Engine= er for Ocean Systems Inc
Xenapi Admin Project Member=A0http://xenapiadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlington, WA = Cell 425-319-8676

"And all we ever were
Just zeroes an= d ones"=A0- Trent Reznor


"If you want to make enemies, try to change s= omething." - Woodrow T. Wilson
--047d7b33d14838e6fd04d3344361-- --===============5541664166209274419== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5541664166209274419==-- From xen-api-bounces@lists.xen.org Sun Jan 13 23:55:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 13 Jan 2013 23:55:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TuXOm-00062Q-F9; Sun, 13 Jan 2013 23:55:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TuXOk-00062I-RL for xen-api@lists.xen.org; Sun, 13 Jan 2013 23:55:31 +0000 Received: from [85.158.139.211:26569] by server-8.bemta-5.messagelabs.com id 13/F9-15003-17943F05; Sun, 13 Jan 2013 23:55:29 +0000 X-Env-Sender: spahmatthew@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1358121326!21198203!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27643 invoked from network); 13 Jan 2013 23:55:28 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jan 2013 23:55:28 -0000 Received: by mail-pa0-f54.google.com with SMTP id bi5so1915361pad.41 for ; Sun, 13 Jan 2013 15:55:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=T6LMnYHzlBasTu8axQ43TZztLP+9Hpn3ofj4kqRuU8A=; b=mRMTV8CCybb8CiWm2hmxWrvWyI+x5FO/eY2DBa3w7jBn7iOJ8epKk3xmAuXOMFJjT6 ni4qSi8i//mQrIm0JXtISxgKeNqm24K3mMQAaxSqWOagE/q5MxIBQPgx7tpEuitczh1X q8Rm1mZUJ7dyZD3WvWukjssnLUOKqeOiH2XgJaGE8n6svqk8z5ca7dpbXep9MKo9hUHn /gztc363h8u8Ehl01o569Q/IRG1AwRypNfayNzreWz1DlEckoRLG2V3fUMHVGruX21jh tDNq9vWIAaXAMC32RdYTz/EtPowbQhGp+k6pQAREXG5qSsakTBSVrhRwqNKJOYtd2fp0 uu7w== MIME-Version: 1.0 Received: by 10.68.236.2 with SMTP id uq2mr247387595pbc.55.1358121326405; Sun, 13 Jan 2013 15:55:26 -0800 (PST) Received: by 10.68.203.72 with HTTP; Sun, 13 Jan 2013 15:55:26 -0800 (PST) Date: Sun, 13 Jan 2013 15:55:26 -0800 Message-ID: From: Matthew Spah To: xen-api@lists.xen.org Subject: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5541664166209274419==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5541664166209274419== Content-Type: multipart/alternative; boundary=047d7b33d14838e6fd04d3344361 --047d7b33d14838e6fd04d3344361 Content-Type: text/plain; charset=ISO-8859-1 Hey everyone, I'm currently testing and documenting the qos parameters for VIF interfaces. I've set up two VMs with VIF interfaces attached to an internal network. I've set the following qos parameters on each VIF interface. *xe vif-param-set uuid= qos_algorithm_type=ratelimit* *xe vif-param-set uuid= qos_algorithm_params:kbps=100* iperf is showing me bandwidth rates between the two VMS that aren't limited to 100 kbps. Am I missing something? -- - Matthew Spah Computer Information Sciences Tutor for Everett Community College Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc Xenapi Admin Project Member http://xenapiadmin.com CompTIA Security+ Certified and Cisco CCNA Certified Arlington, WA Cell 425-319-8676 "And all we ever were Just zeroes and ones" - Trent Reznor "If you want to make enemies, try to change something." - Woodrow T. Wilson --047d7b33d14838e6fd04d3344361 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hey everyone,

I'm currently testing and documenting = the qos parameters for VIF interfaces. I've set up two VMs with VIF int= erfaces attached to an internal network. I've set the following qos par= ameters on each VIF interface.

xe vif-param-set uuid=3D<VIF UUID> qos_algorit= hm_type=3Dratelimit
xe vif-param-set uuid=3D<VIF U= UID> qos_algorithm_params:kbps=3D100
=A0 =A0
ipe= rf is showing me bandwidth rates between the two VMS that aren't limite= d to 100 kbps. Am I missing something?=A0

--
- Matthew Spah
Computer Information Sciences Tutor= for Everett Community College
Electronic Monitoring Jr. Systems Engine= er for Ocean Systems Inc
Xenapi Admin Project Member=A0http://xenapiadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlington, WA = Cell 425-319-8676

"And all we ever were
Just zeroes an= d ones"=A0- Trent Reznor


"If you want to make enemies, try to change s= omething." - Woodrow T. Wilson
--047d7b33d14838e6fd04d3344361-- --===============5541664166209274419== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5541664166209274419==-- From xen-api-bounces@lists.xen.org Mon Jan 14 13:34:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 13:34:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukBF-0004pu-3h; Mon, 14 Jan 2013 13:34:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukBD-0004pp-Lf for xen-api@lists.xen.org; Mon, 14 Jan 2013 13:34:23 +0000 Received: from [85.158.137.99:37504] by server-13.bemta-3.messagelabs.com id 0C/76-00465-E5904F05; Mon, 14 Jan 2013 13:34:22 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1358170411!19980644!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26893 invoked from network); 14 Jan 2013 13:33:32 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 13:33:32 -0000 Received: by mail-lb0-f180.google.com with SMTP id gj3so2883608lbb.25 for ; Mon, 14 Jan 2013 05:33:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=8ixfu5zgkKLdk2rAyQXj9T2TIR+AmVQLAVYVMNkXoPI=; b=Fw9mSozHVfX0509osaqXjJLUDOLe1DSwEG4u07TEYNBaxn1SXvc89LftRyWjq2ZUqj nMHvnXDaa684VkB2yoMC4J9bpAebDv+mq2SMK7hu6u/JP6PZuxKwkcDHuMb6pm1Ozqfx S3z6QPRyK3AdqjpK/QRdwSyzRFJuJEZZ84c5/xZGnXmXMnU0V/+wzmX4QmOUseHxc1bb HGtBXTBg5yKpwkg3XCvMGnw9jNvVh9XJgvED7L8lJF8+Mrbsbtu98oCHDNuq3ng3CZ3G d83GFvgiUGtYArKF4UVSGXAHdcWPniitGNM1B+pPd5V8lq2QiqDuje/XiCZokb4jdkB3 nChw== X-Received: by 10.152.46.161 with SMTP id w1mr82172662lam.27.1358170390498; Mon, 14 Jan 2013 05:33:10 -0800 (PST) Received: from [192.168.40.25] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id n7sm5370060lbz.5.2013.01.14.05.33.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 05:33:10 -0800 (PST) Message-ID: <50F40914.3060606@gmail.com> Date: Mon, 14 Jan 2013 17:33:08 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8067998401641356921==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8067998401641356921== Content-Type: multipart/alternative; boundary="------------030708060509090204070608" This is a multi-part message in MIME format. --------------030708060509090204070608 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 14.01.2013 03:55, Matthew Spah ?????: > Hey everyone, > > I'm currently testing and documenting the qos parameters for VIF > interfaces. I've set up two VMs with VIF interfaces attached to an > internal network. I've set the following qos parameters on each VIF > interface. > > /xe vif-param-set uuid= qos_algorithm_type=ratelimit/ > /xe vif-param-set uuid= qos_algorithm_params:kbps=100/ > iperf is showing me bandwidth rates between the two VMS that aren't > limited to 100 kbps. Am I missing something? > kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. kbps=12 will make it 100kpbs. --------------030708060509090204070608 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
14.01.2013 03:55, Matthew Spah пишет:
Hey everyone,

I'm currently testing and documenting the qos parameters for VIF interfaces. I've set up two VMs with VIF interfaces attached to an internal network. I've set the following qos parameters on each VIF interface.

xe vif-param-set uuid=<VIF UUID> qos_algorithm_type=ratelimit
xe vif-param-set uuid=<VIF UUID> qos_algorithm_params:kbps=100
   
iperf is showing me bandwidth rates between the two VMS that aren't limited to 100 kbps. Am I missing something? 

kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. kbps=12 will make it 100kpbs.

--------------030708060509090204070608-- --===============8067998401641356921== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8067998401641356921==-- From xen-api-bounces@lists.xen.org Mon Jan 14 13:34:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 13:34:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukBF-0004pu-3h; Mon, 14 Jan 2013 13:34:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukBD-0004pp-Lf for xen-api@lists.xen.org; Mon, 14 Jan 2013 13:34:23 +0000 Received: from [85.158.137.99:37504] by server-13.bemta-3.messagelabs.com id 0C/76-00465-E5904F05; Mon, 14 Jan 2013 13:34:22 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1358170411!19980644!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26893 invoked from network); 14 Jan 2013 13:33:32 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 13:33:32 -0000 Received: by mail-lb0-f180.google.com with SMTP id gj3so2883608lbb.25 for ; Mon, 14 Jan 2013 05:33:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=8ixfu5zgkKLdk2rAyQXj9T2TIR+AmVQLAVYVMNkXoPI=; b=Fw9mSozHVfX0509osaqXjJLUDOLe1DSwEG4u07TEYNBaxn1SXvc89LftRyWjq2ZUqj nMHvnXDaa684VkB2yoMC4J9bpAebDv+mq2SMK7hu6u/JP6PZuxKwkcDHuMb6pm1Ozqfx S3z6QPRyK3AdqjpK/QRdwSyzRFJuJEZZ84c5/xZGnXmXMnU0V/+wzmX4QmOUseHxc1bb HGtBXTBg5yKpwkg3XCvMGnw9jNvVh9XJgvED7L8lJF8+Mrbsbtu98oCHDNuq3ng3CZ3G d83GFvgiUGtYArKF4UVSGXAHdcWPniitGNM1B+pPd5V8lq2QiqDuje/XiCZokb4jdkB3 nChw== X-Received: by 10.152.46.161 with SMTP id w1mr82172662lam.27.1358170390498; Mon, 14 Jan 2013 05:33:10 -0800 (PST) Received: from [192.168.40.25] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id n7sm5370060lbz.5.2013.01.14.05.33.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 05:33:10 -0800 (PST) Message-ID: <50F40914.3060606@gmail.com> Date: Mon, 14 Jan 2013 17:33:08 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8067998401641356921==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8067998401641356921== Content-Type: multipart/alternative; boundary="------------030708060509090204070608" This is a multi-part message in MIME format. --------------030708060509090204070608 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 14.01.2013 03:55, Matthew Spah ?????: > Hey everyone, > > I'm currently testing and documenting the qos parameters for VIF > interfaces. I've set up two VMs with VIF interfaces attached to an > internal network. I've set the following qos parameters on each VIF > interface. > > /xe vif-param-set uuid= qos_algorithm_type=ratelimit/ > /xe vif-param-set uuid= qos_algorithm_params:kbps=100/ > iperf is showing me bandwidth rates between the two VMS that aren't > limited to 100 kbps. Am I missing something? > kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. kbps=12 will make it 100kpbs. --------------030708060509090204070608 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
14.01.2013 03:55, Matthew Spah пишет:
Hey everyone,

I'm currently testing and documenting the qos parameters for VIF interfaces. I've set up two VMs with VIF interfaces attached to an internal network. I've set the following qos parameters on each VIF interface.

xe vif-param-set uuid=<VIF UUID> qos_algorithm_type=ratelimit
xe vif-param-set uuid=<VIF UUID> qos_algorithm_params:kbps=100
   
iperf is showing me bandwidth rates between the two VMS that aren't limited to 100 kbps. Am I missing something? 

kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. kbps=12 will make it 100kpbs.

--------------030708060509090204070608-- --===============8067998401641356921== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8067998401641356921==-- From xen-api-bounces@lists.xen.org Mon Jan 14 13:55:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 13:55:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukVV-0005HG-IC; Mon, 14 Jan 2013 13:55:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukVU-0005HB-3f for xen-api@lists.xen.org; Mon, 14 Jan 2013 13:55:20 +0000 Received: from [85.158.143.35:11616] by server-2.bemta-4.messagelabs.com id CB/69-24322-74E04F05; Mon, 14 Jan 2013 13:55:19 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1358171675!10247226!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1ODU1\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32283 invoked from network); 14 Jan 2013 13:54:35 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 13:54:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208,217";a="636249" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Jan 2013 13:54:35 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 14 Jan 2013 13:54:34 +0000 From: John Else To: "xen-api@lists.xen.org" Date: Mon, 14 Jan 2013 13:55:05 +0000 Thread-Topic: [Xen-API] qos_algorithm_type=ratelimit Thread-Index: Ac3yXFqV5Csw35wiStegXoTxFt7fIQAAhPRw Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF75ABE12@LONPMAILBOX01.citrite.net> References: <50F40914.3060606@gmail.com> In-Reply-To: <50F40914.3060606@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7897384361292011514==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7897384361292011514== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE12LONPMAILBOX01_" --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE12LONPMAILBOX01_ Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable There's also a known bug in XCP 1.6, where the API QoS settings don't actua= lly get passed down to Xen. The master branch patch is here: https://github= .com/xen-org/xen-api/commit/4fb4b96b10c2d40cd5e166845659f27882c6dae5 John From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of George Shuklin Sent: 14 January 2013 13:33 To: xen-api@lists.xen.org Subject: Re: [Xen-API] qos_algorithm_type=3Dratelimit 14.01.2013 03:55, Matthew Spah =D0=C9=DB=C5=D4: Hey everyone, I'm currently testing and documenting the qos parameters for VIF interfaces= . I've set up two VMs with VIF interfaces attached to an internal network. = I've set the following qos parameters on each VIF interface. xe vif-param-set uuid=3D qos_algorithm_type=3Dratelimit xe vif-param-set uuid=3D qos_algorithm_params:kbps=3D100 iperf is showing me bandwidth rates between the two VMS that aren't limited= to 100 kbps. Am I missing something? kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. kbps= =3D12 will make it 100kpbs. --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE12LONPMAILBOX01_ Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable

= There’s also a known bug in XCP 1.6, where the API QoS setting= s don’t actually get passed down to Xen. The master branch patch is h= ere: https://github.com/xen-org/xen-api/commit/4fb4b96b= 10c2d40cd5e166845659f27882c6dae5

 

John

 

<= div>

From:= xen-api-bounces@lists.xen.org [mailto:xen-api-bounce= s@lists.xen.org] On Behalf Of George Shuklin
Sent: 14 Janu= ary 2013 13:33
To: xen-api@lists.xen.org
Subject: Re: [= Xen-API] qos_algorithm_type=3Dratelimit

 

14.01.201= 3 03:55, Matthew Spah =D0=C9=DB=C5=D4:

Hey everyon= e,

 

I'm currently testing and documenting the qos paramet= ers for VIF interfaces. I've set up two VMs with VIF interfaces attached to= an internal network. I've set the following qos parameters on each VIF int= erface.

 

=

xe vif-param-set uuid=3D<VIF UUID>= qos_algorithm_type=3Dratelimit

xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_para= ms:kbps=3D100

  &nbs= p;

iperf is showing me bandwi= dth rates between the two VMS that aren't limited to 100 kbps. Am I missing= something? 

 =

kbps is not kbps, but a KiloBYTESperSecond. Really strange, but= it is. kbps=3D12 will make it 100kpbs.

= --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE12LONPMAILBOX01_-- --===============7897384361292011514== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7897384361292011514==-- From xen-api-bounces@lists.xen.org Mon Jan 14 13:55:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 13:55:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukVV-0005HG-IC; Mon, 14 Jan 2013 13:55:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukVU-0005HB-3f for xen-api@lists.xen.org; Mon, 14 Jan 2013 13:55:20 +0000 Received: from [85.158.143.35:11616] by server-2.bemta-4.messagelabs.com id CB/69-24322-74E04F05; Mon, 14 Jan 2013 13:55:19 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1358171675!10247226!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1ODU1\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32283 invoked from network); 14 Jan 2013 13:54:35 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 13:54:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208,217";a="636249" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Jan 2013 13:54:35 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 14 Jan 2013 13:54:34 +0000 From: John Else To: "xen-api@lists.xen.org" Date: Mon, 14 Jan 2013 13:55:05 +0000 Thread-Topic: [Xen-API] qos_algorithm_type=ratelimit Thread-Index: Ac3yXFqV5Csw35wiStegXoTxFt7fIQAAhPRw Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF75ABE12@LONPMAILBOX01.citrite.net> References: <50F40914.3060606@gmail.com> In-Reply-To: <50F40914.3060606@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7897384361292011514==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7897384361292011514== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE12LONPMAILBOX01_" --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE12LONPMAILBOX01_ Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable There's also a known bug in XCP 1.6, where the API QoS settings don't actua= lly get passed down to Xen. The master branch patch is here: https://github= .com/xen-org/xen-api/commit/4fb4b96b10c2d40cd5e166845659f27882c6dae5 John From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of George Shuklin Sent: 14 January 2013 13:33 To: xen-api@lists.xen.org Subject: Re: [Xen-API] qos_algorithm_type=3Dratelimit 14.01.2013 03:55, Matthew Spah =D0=C9=DB=C5=D4: Hey everyone, I'm currently testing and documenting the qos parameters for VIF interfaces= . I've set up two VMs with VIF interfaces attached to an internal network. = I've set the following qos parameters on each VIF interface. xe vif-param-set uuid=3D qos_algorithm_type=3Dratelimit xe vif-param-set uuid=3D qos_algorithm_params:kbps=3D100 iperf is showing me bandwidth rates between the two VMS that aren't limited= to 100 kbps. Am I missing something? kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. kbps= =3D12 will make it 100kpbs. --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE12LONPMAILBOX01_ Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable

= There’s also a known bug in XCP 1.6, where the API QoS setting= s don’t actually get passed down to Xen. The master branch patch is h= ere: https://github.com/xen-org/xen-api/commit/4fb4b96b= 10c2d40cd5e166845659f27882c6dae5

 

John

 

<= div>

From:= xen-api-bounces@lists.xen.org [mailto:xen-api-bounce= s@lists.xen.org] On Behalf Of George Shuklin
Sent: 14 Janu= ary 2013 13:33
To: xen-api@lists.xen.org
Subject: Re: [= Xen-API] qos_algorithm_type=3Dratelimit

 

14.01.201= 3 03:55, Matthew Spah =D0=C9=DB=C5=D4:

Hey everyon= e,

 

I'm currently testing and documenting the qos paramet= ers for VIF interfaces. I've set up two VMs with VIF interfaces attached to= an internal network. I've set the following qos parameters on each VIF int= erface.

 

=

xe vif-param-set uuid=3D<VIF UUID>= qos_algorithm_type=3Dratelimit

xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_para= ms:kbps=3D100

  &nbs= p;

iperf is showing me bandwi= dth rates between the two VMS that aren't limited to 100 kbps. Am I missing= something? 

 =

kbps is not kbps, but a KiloBYTESperSecond. Really strange, but= it is. kbps=3D12 will make it 100kpbs.

= --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE12LONPMAILBOX01_-- --===============7897384361292011514== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7897384361292011514==-- From xen-api-bounces@lists.xen.org Mon Jan 14 13:57:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 13:57:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukXF-0005Js-RY; Mon, 14 Jan 2013 13:57:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukXE-0005Jg-B3 for xen-api@lists.xen.org; Mon, 14 Jan 2013 13:57:08 +0000 Received: from [85.158.143.99:34769] by server-1.bemta-4.messagelabs.com id 87/14-18740-3BE04F05; Mon, 14 Jan 2013 13:57:07 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1358171824!27868221!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1ODU1\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7262 invoked from network); 14 Jan 2013 13:57:04 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 13:57:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208,217";a="636305" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Jan 2013 13:57:04 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Mon, 14 Jan 2013 13:57:03 +0000 From: Rob Hoes To: Matthew Spah Date: Mon, 14 Jan 2013 13:57:02 +0000 Thread-Topic: [Xen-API] qos_algorithm_type=ratelimit Thread-Index: Ac3yXwep8gmdHBCnT92yUooFhC8BDw== Message-ID: <0F7A144E-4895-4867-9050-5E301DDDD2C8@citrix.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5178154095722599740==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5178154095722599740== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_0F7A144E4895486790505E301DDDD2C8citrixcom_" --_000_0F7A144E4895486790505E301DDDD2C8citrixcom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Matthew, After setting those parameters, you probably need to re-plug the VIFs (unpl= ug + plug), or reboot the VMs, for the setting to take effect. You can chec= k if the "rate" key in xenstore is set (xenstore-ls -f | grep rate) to conf= irm. Cheers, Rob On 13 Jan 2013, at 23:55, Matthew Spah > wrote: Hey everyone, I'm currently testing and documenting the qos parameters for VIF interfaces= . I've set up two VMs with VIF interfaces attached to an internal network. = I've set the following qos parameters on each VIF interface. xe vif-param-set uuid=3D qos_algorithm_type=3Dratelimit xe vif-param-set uuid=3D qos_algorithm_params:kbps=3D100 iperf is showing me bandwidth rates between the two VMS that aren't limited= to 100 kbps. Am I missing something? -- - Matthew Spah Computer Information Sciences Tutor for Everett Community College Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc Xenapi Admin Project Member http://xenapiadmin.com CompTIA Security+ Certified and Cisco CCNA Certified Arlington, WA Cell 425-319-8676 "And all we ever were Just zeroes and ones" - Trent Reznor "If you want to make enemies, try to change something." - Woodrow T. Wilson _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_000_0F7A144E4895486790505E301DDDD2C8citrixcom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Matthew,
<= div>
After setting those parameters, you probably need to re-= plug the VIFs (unplug + plug), or reboot the VMs, for the setting to take e= ffect. You can check if the "rate" key in xenstore is set (xenstore-ls= -f | grep rate) to confirm.

Cheers,
Rob=

On 13 Jan 2013, at 23:55, Matthew Spah <spahmatthew@gmail.com> wrote:

Hey everyone,=

I'm currently testing and documenting the qos parameter= s for VIF interfaces. I've set up two VMs with VIF interfaces attached to a= n internal network. I've set the following qos parameters on each VIF inter= face.

xe vif-param-set uuid=3D<VIF UUID> qos_algorit= hm_type=3Dratelimit
xe vif-param-set uuid=3D<VIF U= UID> qos_algorithm_params:kbps=3D100
   
iperf is showing me bandwidth rates between the two VMS that aren't limi= ted to 100 kbps. Am I missing something? 

--
- Matthew Spah
Computer Information Sciences Tutor= for Everett Community College
Electronic Monitoring Jr. Systems Engine= er for Ocean Systems Inc
Xenapi Admin Project Member http://xenapiadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlington, WA = Cell 425-319-8676

"And all we ever were
Just zeroes and one= s" - Trent Reznor


"If you want to make enemies, try to change someth= ing." - Woodrow T. Wilson
_______________________________________________
Xen-api mailing list
= Xen-api@lists.xen.org
http:= //lists.xen.org/cgi-bin/mailman/listinfo/xen-api

= = --_000_0F7A144E4895486790505E301DDDD2C8citrixcom_-- --===============5178154095722599740== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5178154095722599740==-- From xen-api-bounces@lists.xen.org Mon Jan 14 13:57:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 13:57:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukXF-0005Js-RY; Mon, 14 Jan 2013 13:57:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TukXE-0005Jg-B3 for xen-api@lists.xen.org; Mon, 14 Jan 2013 13:57:08 +0000 Received: from [85.158.143.99:34769] by server-1.bemta-4.messagelabs.com id 87/14-18740-3BE04F05; Mon, 14 Jan 2013 13:57:07 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1358171824!27868221!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1ODU1\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7262 invoked from network); 14 Jan 2013 13:57:04 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 13:57:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208,217";a="636305" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Jan 2013 13:57:04 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Mon, 14 Jan 2013 13:57:03 +0000 From: Rob Hoes To: Matthew Spah Date: Mon, 14 Jan 2013 13:57:02 +0000 Thread-Topic: [Xen-API] qos_algorithm_type=ratelimit Thread-Index: Ac3yXwep8gmdHBCnT92yUooFhC8BDw== Message-ID: <0F7A144E-4895-4867-9050-5E301DDDD2C8@citrix.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5178154095722599740==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5178154095722599740== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_0F7A144E4895486790505E301DDDD2C8citrixcom_" --_000_0F7A144E4895486790505E301DDDD2C8citrixcom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Matthew, After setting those parameters, you probably need to re-plug the VIFs (unpl= ug + plug), or reboot the VMs, for the setting to take effect. You can chec= k if the "rate" key in xenstore is set (xenstore-ls -f | grep rate) to conf= irm. Cheers, Rob On 13 Jan 2013, at 23:55, Matthew Spah > wrote: Hey everyone, I'm currently testing and documenting the qos parameters for VIF interfaces= . I've set up two VMs with VIF interfaces attached to an internal network. = I've set the following qos parameters on each VIF interface. xe vif-param-set uuid=3D qos_algorithm_type=3Dratelimit xe vif-param-set uuid=3D qos_algorithm_params:kbps=3D100 iperf is showing me bandwidth rates between the two VMS that aren't limited= to 100 kbps. Am I missing something? -- - Matthew Spah Computer Information Sciences Tutor for Everett Community College Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc Xenapi Admin Project Member http://xenapiadmin.com CompTIA Security+ Certified and Cisco CCNA Certified Arlington, WA Cell 425-319-8676 "And all we ever were Just zeroes and ones" - Trent Reznor "If you want to make enemies, try to change something." - Woodrow T. Wilson _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_000_0F7A144E4895486790505E301DDDD2C8citrixcom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Matthew,
<= div>
After setting those parameters, you probably need to re-= plug the VIFs (unplug + plug), or reboot the VMs, for the setting to take e= ffect. You can check if the "rate" key in xenstore is set (xenstore-ls= -f | grep rate) to confirm.

Cheers,
Rob=

On 13 Jan 2013, at 23:55, Matthew Spah <spahmatthew@gmail.com> wrote:

Hey everyone,=

I'm currently testing and documenting the qos parameter= s for VIF interfaces. I've set up two VMs with VIF interfaces attached to a= n internal network. I've set the following qos parameters on each VIF inter= face.

xe vif-param-set uuid=3D<VIF UUID> qos_algorit= hm_type=3Dratelimit
xe vif-param-set uuid=3D<VIF U= UID> qos_algorithm_params:kbps=3D100
   
iperf is showing me bandwidth rates between the two VMS that aren't limi= ted to 100 kbps. Am I missing something? 

--
- Matthew Spah
Computer Information Sciences Tutor= for Everett Community College
Electronic Monitoring Jr. Systems Engine= er for Ocean Systems Inc
Xenapi Admin Project Member http://xenapiadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlington, WA = Cell 425-319-8676

"And all we ever were
Just zeroes and one= s" - Trent Reznor


"If you want to make enemies, try to change someth= ing." - Woodrow T. Wilson
_______________________________________________
Xen-api mailing list
= Xen-api@lists.xen.org
http:= //lists.xen.org/cgi-bin/mailman/listinfo/xen-api

= = --_000_0F7A144E4895486790505E301DDDD2C8citrixcom_-- --===============5178154095722599740== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5178154095722599740==-- From xen-api-bounces@lists.xen.org Mon Jan 14 14:38:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 14:38:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TulBM-0006jA-R7; Mon, 14 Jan 2013 14:38:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TulBL-0006j5-2z for xen-api@lists.xen.org; Mon, 14 Jan 2013 14:38:35 +0000 Received: from [85.158.143.35:35688] by server-3.bemta-4.messagelabs.com id 99/64-19220-A6814F05; Mon, 14 Jan 2013 14:38:34 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1358174311!5109460!1 X-Originating-IP: [209.85.216.46] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8583 invoked from network); 14 Jan 2013 14:38:32 -0000 Received: from mail-qa0-f46.google.com (HELO mail-qa0-f46.google.com) (209.85.216.46) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 14:38:32 -0000 Received: by mail-qa0-f46.google.com with SMTP id r4so1470808qaq.5 for ; Mon, 14 Jan 2013 06:38:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AguzTmI2e8wXF+vgvR+tVpfDcPMypfQUrI3n8FoMdII=; b=Iw6/3QbuML59FWNXT2/vK1cd4bClJmWpk0ICrFA0rqyighSCn0eSYGi8smYB9Z14ZF Tc8qI9rFSHjo5T0vM97ziUtQ+hqYRBPuDKnG2oJypX/FjS1lBh6GLgiccWU5xdprIxP7 Otmd8C4MlKEG+xTwPYdYhZtc1Q9PH4YGo2HiB6FiU/THZpIR3ZKNOa2xkuSlLBJm7GLD cQFE6nI8eRTpk81VK6QIBQ3y3xEGmA20CszhOrV8rUyfciwRz2cai13aGb4ICGbqBTzM 04s+r2x11URfdkgdRVAWEJ5EFHNptb8aySUhxsrTtMcKyBiLFOnSC3oiLR2X/loL1drA G3Dw== MIME-Version: 1.0 Received: by 10.49.121.40 with SMTP id lh8mr85266691qeb.30.1358174311385; Mon, 14 Jan 2013 06:38:31 -0800 (PST) Received: by 10.229.17.19 with HTTP; Mon, 14 Jan 2013 06:38:31 -0800 (PST) In-Reply-To: <7EA643C653F17F4C80DE959E978F10EDFBF75ABE12@LONPMAILBOX01.citrite.net> References: <50F40914.3060606@gmail.com> <7EA643C653F17F4C80DE959E978F10EDFBF75ABE12@LONPMAILBOX01.citrite.net> Date: Mon, 14 Jan 2013 20:08:31 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: John Else Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2096833650713692169==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2096833650713692169== Content-Type: multipart/alternative; boundary=047d7bdc1be45f8b3204d3409977 --047d7bdc1be45f8b3204d3409977 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello John, Since the commit is 4 months old can we consider that it is fixed in XCP1.6.10 or are you suggesting that the current stable XCP1.6.10 has this known bug ? ( I assumed 2nd but just want to confirm ) By looking at patch, it looks safe to locally integrate into XCP1.6.10 xapi.src.rpm. Any suggestions ? On Mon, Jan 14, 2013 at 7:25 PM, John Else wrote: > There=E2=80=99s also a known bug in XCP 1.6, where the API QoS settings d= on=E2=80=99t > actually get passed down to Xen. The master branch patch is here: > https://github.com/xen-org/xen-api/commit/4fb4b96b10c2d40cd5e166845659f27= 882c6dae5 > **** > > ** ** > > John**** > > ** ** > > *From:* xen-api-bounces@lists.xen.org [mailto: > xen-api-bounces@lists.xen.org] *On Behalf Of *George Shuklin > *Sent:* 14 January 2013 13:33 > *To:* xen-api@lists.xen.org > *Subject:* Re: [Xen-API] qos_algorithm_type=3Dratelimit**** > > ** ** > > 14.01.2013 03:55, Matthew Spah =D0=BF=D0=B8=D1=88=D0=B5=D1=82:**** > > Hey everyone, **** > > ** ** > > I'm currently testing and documenting the qos parameters for VIF > interfaces. I've set up two VMs with VIF interfaces attached to an intern= al > network. I've set the following qos parameters on each VIF interface.**** > > ** ** > > *xe vif-param-set uuid=3D qos_algorithm_type=3Dratelimit***** > > *xe vif-param-set uuid=3D qos_algorithm_params:kbps=3D100***** > > **** > > iperf is showing me bandwidth rates between the two VMS that aren't > limited to 100 kbps. Am I missing something? **** > > ** ** > > kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. > kbps=3D12 will make it 100kpbs.**** > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --047d7bdc1be45f8b3204d3409977 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello John,

Since the commit is 4 months old can we consider that it= is fixed in XCP1.6.10 or are you suggesting that the current stable XCP1.6= .10 has this known bug ? ( I assumed 2nd but just want to confirm )

By looking at patch, it looks safe to locally integrate into XCP1.6.10 xapi= .src.rpm. Any suggestions ?


--047d7bdc1be45f8b3204d3409977-- --===============2096833650713692169== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2096833650713692169==-- From xen-api-bounces@lists.xen.org Mon Jan 14 14:38:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 14:38:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TulBM-0006jA-R7; Mon, 14 Jan 2013 14:38:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TulBL-0006j5-2z for xen-api@lists.xen.org; Mon, 14 Jan 2013 14:38:35 +0000 Received: from [85.158.143.35:35688] by server-3.bemta-4.messagelabs.com id 99/64-19220-A6814F05; Mon, 14 Jan 2013 14:38:34 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1358174311!5109460!1 X-Originating-IP: [209.85.216.46] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8583 invoked from network); 14 Jan 2013 14:38:32 -0000 Received: from mail-qa0-f46.google.com (HELO mail-qa0-f46.google.com) (209.85.216.46) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 14:38:32 -0000 Received: by mail-qa0-f46.google.com with SMTP id r4so1470808qaq.5 for ; Mon, 14 Jan 2013 06:38:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AguzTmI2e8wXF+vgvR+tVpfDcPMypfQUrI3n8FoMdII=; b=Iw6/3QbuML59FWNXT2/vK1cd4bClJmWpk0ICrFA0rqyighSCn0eSYGi8smYB9Z14ZF Tc8qI9rFSHjo5T0vM97ziUtQ+hqYRBPuDKnG2oJypX/FjS1lBh6GLgiccWU5xdprIxP7 Otmd8C4MlKEG+xTwPYdYhZtc1Q9PH4YGo2HiB6FiU/THZpIR3ZKNOa2xkuSlLBJm7GLD cQFE6nI8eRTpk81VK6QIBQ3y3xEGmA20CszhOrV8rUyfciwRz2cai13aGb4ICGbqBTzM 04s+r2x11URfdkgdRVAWEJ5EFHNptb8aySUhxsrTtMcKyBiLFOnSC3oiLR2X/loL1drA G3Dw== MIME-Version: 1.0 Received: by 10.49.121.40 with SMTP id lh8mr85266691qeb.30.1358174311385; Mon, 14 Jan 2013 06:38:31 -0800 (PST) Received: by 10.229.17.19 with HTTP; Mon, 14 Jan 2013 06:38:31 -0800 (PST) In-Reply-To: <7EA643C653F17F4C80DE959E978F10EDFBF75ABE12@LONPMAILBOX01.citrite.net> References: <50F40914.3060606@gmail.com> <7EA643C653F17F4C80DE959E978F10EDFBF75ABE12@LONPMAILBOX01.citrite.net> Date: Mon, 14 Jan 2013 20:08:31 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: John Else Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2096833650713692169==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2096833650713692169== Content-Type: multipart/alternative; boundary=047d7bdc1be45f8b3204d3409977 --047d7bdc1be45f8b3204d3409977 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello John, Since the commit is 4 months old can we consider that it is fixed in XCP1.6.10 or are you suggesting that the current stable XCP1.6.10 has this known bug ? ( I assumed 2nd but just want to confirm ) By looking at patch, it looks safe to locally integrate into XCP1.6.10 xapi.src.rpm. Any suggestions ? On Mon, Jan 14, 2013 at 7:25 PM, John Else wrote: > There=E2=80=99s also a known bug in XCP 1.6, where the API QoS settings d= on=E2=80=99t > actually get passed down to Xen. The master branch patch is here: > https://github.com/xen-org/xen-api/commit/4fb4b96b10c2d40cd5e166845659f27= 882c6dae5 > **** > > ** ** > > John**** > > ** ** > > *From:* xen-api-bounces@lists.xen.org [mailto: > xen-api-bounces@lists.xen.org] *On Behalf Of *George Shuklin > *Sent:* 14 January 2013 13:33 > *To:* xen-api@lists.xen.org > *Subject:* Re: [Xen-API] qos_algorithm_type=3Dratelimit**** > > ** ** > > 14.01.2013 03:55, Matthew Spah =D0=BF=D0=B8=D1=88=D0=B5=D1=82:**** > > Hey everyone, **** > > ** ** > > I'm currently testing and documenting the qos parameters for VIF > interfaces. I've set up two VMs with VIF interfaces attached to an intern= al > network. I've set the following qos parameters on each VIF interface.**** > > ** ** > > *xe vif-param-set uuid=3D qos_algorithm_type=3Dratelimit***** > > *xe vif-param-set uuid=3D qos_algorithm_params:kbps=3D100***** > > **** > > iperf is showing me bandwidth rates between the two VMS that aren't > limited to 100 kbps. Am I missing something? **** > > ** ** > > kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. > kbps=3D12 will make it 100kpbs.**** > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --047d7bdc1be45f8b3204d3409977 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello John,

Since the commit is 4 months old can we consider that it= is fixed in XCP1.6.10 or are you suggesting that the current stable XCP1.6= .10 has this known bug ? ( I assumed 2nd but just want to confirm )

By looking at patch, it looks safe to locally integrate into XCP1.6.10 xapi= .src.rpm. Any suggestions ?

On Mon, Jan 1= 4, 2013 at 7:25 PM, John Else <john.else@citrix.com> wrot= e:

There=E2=80=99s also a known bug in XCP 1.6, where the API QoS setti= ngs don=E2=80=99t actually get passed down to Xen. The master branch patch = is here: https://github.com/xen-org/x= en-api/commit/4fb4b96b10c2d40cd5e166845659f27882c6dae5

=C2=A0

John<= /span>

=C2=A0

From:= xen-api-bounces@lists.xen.o= rg [mailto:xen-api-bounces@lists.xen.org] On Behalf Of George Shukli= n
Sent: 14 January 2013 13:33
To: xen-api@lists.xen.org
Subject: Re: [Xen-API] qos_algorithm_type=3Dratelimit

=C2=A0

14.01.2013 03:55, Matthew Spah =D0=BF=D0=B8=D1= =88=D0=B5=D1=82:

Hey everyone,

=C2=A0

I'm currently testing and do= cumenting the qos parameters for VIF interfaces. I've set up two VMs wi= th VIF interfaces attached to an internal network. I've set the followi= ng qos parameters on each VIF interface.

=C2=A0

xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_= type=3Dratelimit

xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_params:kbps=3D1= 00

=C2=A0 =C2=A0

iperf is showing me bandwidth rates between the two= VMS that aren't limited to 100 kbps. Am I missing something?=C2=A0<= /u>

=C2=A0

kbps is not kbps, b= ut a KiloBYTESperSecond. Really strange, but it is. kbps=3D12 will make it = 100kpbs.


_______________________________________________=
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--047d7bdc1be45f8b3204d3409977-- --===============2096833650713692169== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2096833650713692169==-- From xen-api-bounces@lists.xen.org Mon Jan 14 15:27:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 15:27:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TulwV-0007cv-AM; Mon, 14 Jan 2013 15:27:19 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TulwS-0007co-TC for xen-api@lists.xen.org; Mon, 14 Jan 2013 15:27:17 +0000 Received: from [193.109.254.147:55326] by server-6.bemta-14.messagelabs.com id 15/01-25153-4D324F05; Mon, 14 Jan 2013 15:27:16 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1358177198!8633159!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1ODU1\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21222 invoked from network); 14 Jan 2013 15:26:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 15:26:39 -0000 X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208,217";a="638934" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Jan 2013 15:26:38 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Mon, 14 Jan 2013 15:26:37 +0000 From: John Else To: Rushikesh Jadhav <2rushikeshj@gmail.com> Date: Mon, 14 Jan 2013 15:27:08 +0000 Thread-Topic: [Xen-API] qos_algorithm_type=ratelimit Thread-Index: Ac3yZNlwva9NoAVVT/6iGw0QSUfcvgABIUBw Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF75ABE65@LONPMAILBOX01.citrite.net> References: <50F40914.3060606@gmail.com> <7EA643C653F17F4C80DE959E978F10EDFBF75ABE12@LONPMAILBOX01.citrite.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8532426227413904537==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8532426227413904537== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE65LONPMAILBOX01_" --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE65LONPMAILBOX01_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgUnVzaGlrZXNoLCBJ4oCZdmUgbWFkZSBhIG1pc3Rha2Ug4oCTIHRoaXMgZml4IGRpZCBnZXQg aW50byBYQ1AgMS42LjEwLiBJdCBkaWRu4oCZdCBtYWtlIGl0IGludG8gdmVyc2lvbiA2LjEgb2Yg Y29tbWVyY2lhbCBYZW5TZXJ2ZXIsIHdoaWNoIGlzIHdoYXQgY29uZnVzZWQgbWUuDQoNClRoZSBv cmlnaW5hbCBwcm9ibGVtIGNvdWxkIHN0aWxsIGJlIGNhdXNlZCBieSBraWxvYml0L2tpbG9ieXRl IGNvbmZ1c2lvbiwgYXMgR2VvcmdlIHN1Z2dlc3RzLg0KDQpKb2huDQoNCkZyb206IFJ1c2hpa2Vz aCBKYWRoYXYgW21haWx0bzoycnVzaGlrZXNoakBnbWFpbC5jb21dDQpTZW50OiAxNCBKYW51YXJ5 IDIwMTMgMTQ6MzkNClRvOiBKb2huIEVsc2UNCkNjOiB4ZW4tYXBpQGxpc3RzLnhlbi5vcmcNClN1 YmplY3Q6IFJlOiBbWGVuLUFQSV0gcW9zX2FsZ29yaXRobV90eXBlPXJhdGVsaW1pdA0KDQpIZWxs byBKb2huLA0KDQpTaW5jZSB0aGUgY29tbWl0IGlzIDQgbW9udGhzIG9sZCBjYW4gd2UgY29uc2lk ZXIgdGhhdCBpdCBpcyBmaXhlZCBpbiBYQ1AxLjYuMTAgb3IgYXJlIHlvdSBzdWdnZXN0aW5nIHRo YXQgdGhlIGN1cnJlbnQgc3RhYmxlIFhDUDEuNi4xMCBoYXMgdGhpcyBrbm93biBidWcgPyAoIEkg YXNzdW1lZCAybmQgYnV0IGp1c3Qgd2FudCB0byBjb25maXJtICkNCg0KQnkgbG9va2luZyBhdCBw YXRjaCwgaXQgbG9va3Mgc2FmZSB0byBsb2NhbGx5IGludGVncmF0ZSBpbnRvIFhDUDEuNi4xMCB4 YXBpLnNyYy5ycG0uIEFueSBzdWdnZXN0aW9ucyA/DQpPbiBNb24sIEphbiAxNCwgMjAxMyBhdCA3 OjI1IFBNLCBKb2huIEVsc2UgPGpvaG4uZWxzZUBjaXRyaXguY29tPG1haWx0bzpqb2huLmVsc2VA Y2l0cml4LmNvbT4+IHdyb3RlOg0KVGhlcmXigJlzIGFsc28gYSBrbm93biBidWcgaW4gWENQIDEu Niwgd2hlcmUgdGhlIEFQSSBRb1Mgc2V0dGluZ3MgZG9u4oCZdCBhY3R1YWxseSBnZXQgcGFzc2Vk IGRvd24gdG8gWGVuLiBUaGUgbWFzdGVyIGJyYW5jaCBwYXRjaCBpcyBoZXJlOiBodHRwczovL2dp dGh1Yi5jb20veGVuLW9yZy94ZW4tYXBpL2NvbW1pdC80ZmI0Yjk2YjEwYzJkNDBjZDVlMTY2ODQ1 NjU5ZjI3ODgyYzZkYWU1DQoNCkpvaG4NCg0KRnJvbTogeGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhl bi5vcmc8bWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPiBbbWFpbHRvOnhlbi1h cGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPG1haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVu Lm9yZz5dIE9uIEJlaGFsZiBPZiBHZW9yZ2UgU2h1a2xpbg0KU2VudDogMTQgSmFudWFyeSAyMDEz IDEzOjMzDQpUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhl bi5vcmc+DQpTdWJqZWN0OiBSZTogW1hlbi1BUEldIHFvc19hbGdvcml0aG1fdHlwZT1yYXRlbGlt aXQNCg0KMTQuMDEuMjAxMyAwMzo1NSwgTWF0dGhldyBTcGFoINC/0LjRiNC10YI6DQpIZXkgZXZl cnlvbmUsDQoNCkknbSBjdXJyZW50bHkgdGVzdGluZyBhbmQgZG9jdW1lbnRpbmcgdGhlIHFvcyBw YXJhbWV0ZXJzIGZvciBWSUYgaW50ZXJmYWNlcy4gSSd2ZSBzZXQgdXAgdHdvIFZNcyB3aXRoIFZJ RiBpbnRlcmZhY2VzIGF0dGFjaGVkIHRvIGFuIGludGVybmFsIG5ldHdvcmsuIEkndmUgc2V0IHRo ZSBmb2xsb3dpbmcgcW9zIHBhcmFtZXRlcnMgb24gZWFjaCBWSUYgaW50ZXJmYWNlLg0KDQp4ZSB2 aWYtcGFyYW0tc2V0IHV1aWQ9PFZJRiBVVUlEPiBxb3NfYWxnb3JpdGhtX3R5cGU9cmF0ZWxpbWl0 DQp4ZSB2aWYtcGFyYW0tc2V0IHV1aWQ9PFZJRiBVVUlEPiBxb3NfYWxnb3JpdGhtX3BhcmFtczpr YnBzPTEwMA0KDQppcGVyZiBpcyBzaG93aW5nIG1lIGJhbmR3aWR0aCByYXRlcyBiZXR3ZWVuIHRo ZSB0d28gVk1TIHRoYXQgYXJlbid0IGxpbWl0ZWQgdG8gMTAwIGticHMuIEFtIEkgbWlzc2luZyBz b21ldGhpbmc/DQoNCmticHMgaXMgbm90IGticHMsIGJ1dCBhIEtpbG9CWVRFU3BlclNlY29uZC4g UmVhbGx5IHN0cmFuZ2UsIGJ1dCBpdCBpcy4ga2Jwcz0xMiB3aWxsIG1ha2UgaXQgMTAwa3Bicy4N Cg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClhlbi1h cGkgbWFpbGluZyBsaXN0DQpYZW4tYXBpQGxpc3RzLnhlbi5vcmc8bWFpbHRvOlhlbi1hcGlAbGlz dHMueGVuLm9yZz4NCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5m by94ZW4tYXBpDQoNCg== --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE65LONPMAILBOX01_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5 OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZp bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0 LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj b3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNv QWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxv b24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm b250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNw YW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQt ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkJh bGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1z by1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglm b250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6 RU4tR0I7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1sYW5ndWFn ZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJ bWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJ e3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+ DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+ PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4 dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxh eW91dD48L3htbD48IVtlbmRpZl0tLT48L2hlYWQ+PGJvZHkgbGFuZz1FTi1HQiBsaW5rPWJsdWUg dmxpbms9cHVycGxlPjxkaXYgY2xhc3M9V29yZFNlY3Rpb24xPjxwIGNsYXNzPU1zb05vcm1hbD48 c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt c2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkhpIFJ1c2hpa2VzaCwgSeKAmXZlIG1hZGUgYSBtaXN0YWtl IOKAkyB0aGlzIGZpeCBkaWQgZ2V0IGludG8gWENQIDEuNi4xMC4gSXQgZGlkbuKAmXQgbWFrZSBp dCBpbnRvIHZlcnNpb24gNi4xIG9mIGNvbW1lcmNpYWwgWGVuU2VydmVyLCB3aGljaCBpcyB3aGF0 IGNvbmZ1c2VkIG1lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNw YW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNl cmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9 TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxp YnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+VGhlIG9yaWdpbmFsIHByb2JsZW0gY291 bGQgc3RpbGwgYmUgY2F1c2VkIGJ5IGtpbG9iaXQva2lsb2J5dGUgY29uZnVzaW9uLCBhcyBHZW9y Z2Ugc3VnZ2VzdHMuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3Bh biBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy aWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1N c29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGli cmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5Kb2huPG86cD48L286cD48L3NwYW4+PC9w PjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9v OnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PGI+PHNwYW4gbGFuZz1FTi1VUyBzdHls ZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPkZy b206PC9zcGFuPjwvYj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2Zv bnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+IFJ1c2hpa2VzaCBKYWRoYXYgW21haWx0 bzoycnVzaGlrZXNoakBnbWFpbC5jb21dIDxicj48Yj5TZW50OjwvYj4gMTQgSmFudWFyeSAyMDEz IDE0OjM5PGJyPjxiPlRvOjwvYj4gSm9obiBFbHNlPGJyPjxiPkNjOjwvYj4geGVuLWFwaUBsaXN0 cy54ZW4ub3JnPGJyPjxiPlN1YmplY3Q6PC9iPiBSZTogW1hlbi1BUEldIHFvc19hbGdvcml0aG1f dHlwZT1yYXRlbGltaXQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxv OnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRv bToxMi4wcHQnPkhlbGxvIEpvaG4sPGJyPjxicj5TaW5jZSB0aGUgY29tbWl0IGlzIDQgbW9udGhz IG9sZCBjYW4gd2UgY29uc2lkZXIgdGhhdCBpdCBpcyBmaXhlZCBpbiBYQ1AxLjYuMTAgb3IgYXJl IHlvdSBzdWdnZXN0aW5nIHRoYXQgdGhlIGN1cnJlbnQgc3RhYmxlIFhDUDEuNi4xMCBoYXMgdGhp cyBrbm93biBidWcgPyAoIEkgYXNzdW1lZCAybmQgYnV0IGp1c3Qgd2FudCB0byBjb25maXJtICk8 YnI+PGJyPkJ5IGxvb2tpbmcgYXQgcGF0Y2gsIGl0IGxvb2tzIHNhZmUgdG8gbG9jYWxseSBpbnRl Z3JhdGUgaW50byBYQ1AxLjYuMTAgeGFwaS5zcmMucnBtLiBBbnkgc3VnZ2VzdGlvbnMgPzxvOnA+ PC9vOnA+PC9wPjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPk9uIE1vbiwgSmFuIDE0LCAyMDEzIGF0 IDc6MjUgUE0sIEpvaG4gRWxzZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpvaG4uZWxzZUBjaXRyaXgu Y29tIiB0YXJnZXQ9Il9ibGFuayI+am9obi5lbHNlQGNpdHJpeC5jb208L2E+Jmd0OyB3cm90ZTo8 bzpwPjwvbzpwPjwvcD48ZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFy Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9 J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xv cjojMUY0OTdEJz5UaGVyZeKAmXMgYWxzbyBhIGtub3duIGJ1ZyBpbiBYQ1AgMS42LCB3aGVyZSB0 aGUgQVBJIFFvUyBzZXR0aW5ncyBkb27igJl0IGFjdHVhbGx5IGdldCBwYXNzZWQgZG93biB0byBY ZW4uIFRoZSBtYXN0ZXIgYnJhbmNoIHBhdGNoIGlzIGhlcmU6IDxhIGhyZWY9Imh0dHBzOi8vZ2l0 aHViLmNvbS94ZW4tb3JnL3hlbi1hcGkvY29tbWl0LzRmYjRiOTZiMTBjMmQ0MGNkNWUxNjY4NDU2 NTlmMjc4ODJjNmRhZTUiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL2dpdGh1Yi5jb20veGVuLW9y Zy94ZW4tYXBpL2NvbW1pdC80ZmI0Yjk2YjEwYzJkNDBjZDVlMTY2ODQ1NjU5ZjI3ODgyYzZkYWU1 PC9hPjwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1t YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz48c3BhbiBzdHls ZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2Nv bG9yOiMxRjQ5N0QnPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3Jt YWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph dXRvJz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIs InNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkpvaG48L3NwYW4+PG86cD48L286cD48L3A+PHAg Y2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu LWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p bHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86 cD48L286cD48L3A+PGRpdj48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlk ICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSc+PHAgY2xhc3M9TXNvTm9y bWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6 YXV0byc+PGI+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZh bWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPUVO LVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNl cmlmIic+IDxhIGhyZWY9Im1haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyIgdGFy Z2V0PSJfYmxhbmsiPnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPC9hPiBbbWFpbHRvOjxh IGhyZWY9Im1haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyIgdGFyZ2V0PSJfYmxh bmsiPnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPC9hPl0gPGI+T24gQmVoYWxmIE9mIDwv Yj5HZW9yZ2UgU2h1a2xpbjxicj48Yj5TZW50OjwvYj4gMTQgSmFudWFyeSAyMDEzIDEzOjMzPGJy PjxiPlRvOjwvYj4gPGEgaHJlZj0ibWFpbHRvOnhlbi1hcGlAbGlzdHMueGVuLm9yZyIgdGFyZ2V0 PSJfYmxhbmsiPnhlbi1hcGlAbGlzdHMueGVuLm9yZzwvYT48YnI+PGI+U3ViamVjdDo8L2I+IFJl OiBbWGVuLUFQSV0gcW9zX2FsZ29yaXRobV90eXBlPXJhdGVsaW1pdDwvc3Bhbj48bzpwPjwvbzpw PjwvcD48L2Rpdj48L2Rpdj48ZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28t bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+Jm5ic3A7PG86 cD48L286cD48L3A+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9w LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4xNC4wMS4yMDEzIDAzOjU1LCBN YXR0aGV3IFNwYWgg0L/QuNGI0LXRgjo8bzpwPjwvbzpwPjwvcD48L2Rpdj48YmxvY2txdW90ZSBz dHlsZT0nbWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Jz48cCBjbGFzcz1Nc29O b3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs dDphdXRvJz5IZXkgZXZlcnlvbmUsIDxvOnA+PC9vOnA+PC9wPjxkaXY+PHAgY2xhc3M9TXNvTm9y bWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6 YXV0byc+Jm5ic3A7PG86cD48L286cD48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwg c3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv Jz5JJ20gY3VycmVudGx5IHRlc3RpbmcgYW5kIGRvY3VtZW50aW5nIHRoZSBxb3MgcGFyYW1ldGVy cyBmb3IgVklGIGludGVyZmFjZXMuIEkndmUgc2V0IHVwIHR3byBWTXMgd2l0aCBWSUYgaW50ZXJm YWNlcyBhdHRhY2hlZCB0byBhbiBpbnRlcm5hbCBuZXR3b3JrLiBJJ3ZlIHNldCB0aGUgZm9sbG93 aW5nIHFvcyBwYXJhbWV0ZXJzIG9uIGVhY2ggVklGIGludGVyZmFjZS48bzpwPjwvbzpwPjwvcD48 L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1 dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8nPiZuYnNwOzxvOnA+PC9vOnA+PC9wPjwvZGl2 PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PGk+eGUgdmlmLXBhcmFtLXNldCB1dWlkPSZsdDtW SUYgVVVJRCZndDsgcW9zX2FsZ29yaXRobV90eXBlPXJhdGVsaW1pdDwvaT48bzpwPjwvbzpwPjwv cD48L2Rpdj48ZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRv cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PGk+eGUgdmlmLXBhcmFtLXNl dCB1dWlkPSZsdDtWSUYgVVVJRCZndDsgcW9zX2FsZ29yaXRobV9wYXJhbXM6a2Jwcz0xMDA8L2k+ PG86cD48L286cD48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1t YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4mbmJzcDsgJm5i c3A7PG86cD48L286cD48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21z by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz5pcGVyZiBp cyBzaG93aW5nIG1lIGJhbmR3aWR0aCByYXRlcyBiZXR3ZWVuIHRoZSB0d28gVk1TIHRoYXQgYXJl bid0IGxpbWl0ZWQgdG8gMTAwIGticHMuIEFtIEkgbWlzc2luZyBzb21ldGhpbmc/Jm5ic3A7PG86 cD48L286cD48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJn aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4mbmJzcDs8bzpwPjwv bzpwPjwvcD48L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxl PSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCc+a2JwcyBpcyBu b3Qga2JwcywgYnV0IGEgS2lsb0JZVEVTcGVyU2Vjb25kLiBSZWFsbHkgc3RyYW5nZSwgYnV0IGl0 IGlzLiBrYnBzPTEyIHdpbGwgbWFrZSBpdCAxMDBrcGJzLjxvOnA+PC9vOnA+PC9wPjwvZGl2Pjwv ZGl2PjwvZGl2PjwvZGl2PjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbTox Mi4wcHQnPjxicj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Xzxicj5YZW4tYXBpIG1haWxpbmcgbGlzdDxicj48YSBocmVmPSJtYWlsdG86WGVuLWFwaUBsaXN0 cy54ZW4ub3JnIj5YZW4tYXBpQGxpc3RzLnhlbi5vcmc8L2E+PGJyPjxhIGhyZWY9Imh0dHA6Ly9s aXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpIiB0YXJnZXQ9Il9i bGFuayI+aHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1h cGk8L2E+PG86cD48L286cD48L3A+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7 PC9vOnA+PC9wPjwvZGl2PjwvYm9keT48L2h0bWw+ --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE65LONPMAILBOX01_-- --===============8532426227413904537== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8532426227413904537==-- From xen-api-bounces@lists.xen.org Mon Jan 14 15:27:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 15:27:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TulwV-0007cv-AM; Mon, 14 Jan 2013 15:27:19 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TulwS-0007co-TC for xen-api@lists.xen.org; Mon, 14 Jan 2013 15:27:17 +0000 Received: from [193.109.254.147:55326] by server-6.bemta-14.messagelabs.com id 15/01-25153-4D324F05; Mon, 14 Jan 2013 15:27:16 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1358177198!8633159!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE1ODU1\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21222 invoked from network); 14 Jan 2013 15:26:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 15:26:39 -0000 X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208,217";a="638934" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Jan 2013 15:26:38 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Mon, 14 Jan 2013 15:26:37 +0000 From: John Else To: Rushikesh Jadhav <2rushikeshj@gmail.com> Date: Mon, 14 Jan 2013 15:27:08 +0000 Thread-Topic: [Xen-API] qos_algorithm_type=ratelimit Thread-Index: Ac3yZNlwva9NoAVVT/6iGw0QSUfcvgABIUBw Message-ID: <7EA643C653F17F4C80DE959E978F10EDFBF75ABE65@LONPMAILBOX01.citrite.net> References: <50F40914.3060606@gmail.com> <7EA643C653F17F4C80DE959E978F10EDFBF75ABE12@LONPMAILBOX01.citrite.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] qos_algorithm_type=ratelimit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8532426227413904537==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8532426227413904537== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE65LONPMAILBOX01_" --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE65LONPMAILBOX01_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgUnVzaGlrZXNoLCBJ4oCZdmUgbWFkZSBhIG1pc3Rha2Ug4oCTIHRoaXMgZml4IGRpZCBnZXQg aW50byBYQ1AgMS42LjEwLiBJdCBkaWRu4oCZdCBtYWtlIGl0IGludG8gdmVyc2lvbiA2LjEgb2Yg Y29tbWVyY2lhbCBYZW5TZXJ2ZXIsIHdoaWNoIGlzIHdoYXQgY29uZnVzZWQgbWUuDQoNClRoZSBv cmlnaW5hbCBwcm9ibGVtIGNvdWxkIHN0aWxsIGJlIGNhdXNlZCBieSBraWxvYml0L2tpbG9ieXRl IGNvbmZ1c2lvbiwgYXMgR2VvcmdlIHN1Z2dlc3RzLg0KDQpKb2huDQoNCkZyb206IFJ1c2hpa2Vz aCBKYWRoYXYgW21haWx0bzoycnVzaGlrZXNoakBnbWFpbC5jb21dDQpTZW50OiAxNCBKYW51YXJ5 IDIwMTMgMTQ6MzkNClRvOiBKb2huIEVsc2UNCkNjOiB4ZW4tYXBpQGxpc3RzLnhlbi5vcmcNClN1 YmplY3Q6IFJlOiBbWGVuLUFQSV0gcW9zX2FsZ29yaXRobV90eXBlPXJhdGVsaW1pdA0KDQpIZWxs byBKb2huLA0KDQpTaW5jZSB0aGUgY29tbWl0IGlzIDQgbW9udGhzIG9sZCBjYW4gd2UgY29uc2lk ZXIgdGhhdCBpdCBpcyBmaXhlZCBpbiBYQ1AxLjYuMTAgb3IgYXJlIHlvdSBzdWdnZXN0aW5nIHRo YXQgdGhlIGN1cnJlbnQgc3RhYmxlIFhDUDEuNi4xMCBoYXMgdGhpcyBrbm93biBidWcgPyAoIEkg YXNzdW1lZCAybmQgYnV0IGp1c3Qgd2FudCB0byBjb25maXJtICkNCg0KQnkgbG9va2luZyBhdCBw YXRjaCwgaXQgbG9va3Mgc2FmZSB0byBsb2NhbGx5IGludGVncmF0ZSBpbnRvIFhDUDEuNi4xMCB4 YXBpLnNyYy5ycG0uIEFueSBzdWdnZXN0aW9ucyA/DQpPbiBNb24sIEphbiAxNCwgMjAxMyBhdCA3 OjI1IFBNLCBKb2huIEVsc2UgPGpvaG4uZWxzZUBjaXRyaXguY29tPG1haWx0bzpqb2huLmVsc2VA Y2l0cml4LmNvbT4+IHdyb3RlOg0KVGhlcmXigJlzIGFsc28gYSBrbm93biBidWcgaW4gWENQIDEu Niwgd2hlcmUgdGhlIEFQSSBRb1Mgc2V0dGluZ3MgZG9u4oCZdCBhY3R1YWxseSBnZXQgcGFzc2Vk IGRvd24gdG8gWGVuLiBUaGUgbWFzdGVyIGJyYW5jaCBwYXRjaCBpcyBoZXJlOiBodHRwczovL2dp dGh1Yi5jb20veGVuLW9yZy94ZW4tYXBpL2NvbW1pdC80ZmI0Yjk2YjEwYzJkNDBjZDVlMTY2ODQ1 NjU5ZjI3ODgyYzZkYWU1DQoNCkpvaG4NCg0KRnJvbTogeGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhl bi5vcmc8bWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPiBbbWFpbHRvOnhlbi1h cGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPG1haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVu Lm9yZz5dIE9uIEJlaGFsZiBPZiBHZW9yZ2UgU2h1a2xpbg0KU2VudDogMTQgSmFudWFyeSAyMDEz IDEzOjMzDQpUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhl bi5vcmc+DQpTdWJqZWN0OiBSZTogW1hlbi1BUEldIHFvc19hbGdvcml0aG1fdHlwZT1yYXRlbGlt aXQNCg0KMTQuMDEuMjAxMyAwMzo1NSwgTWF0dGhldyBTcGFoINC/0LjRiNC10YI6DQpIZXkgZXZl cnlvbmUsDQoNCkknbSBjdXJyZW50bHkgdGVzdGluZyBhbmQgZG9jdW1lbnRpbmcgdGhlIHFvcyBw YXJhbWV0ZXJzIGZvciBWSUYgaW50ZXJmYWNlcy4gSSd2ZSBzZXQgdXAgdHdvIFZNcyB3aXRoIFZJ RiBpbnRlcmZhY2VzIGF0dGFjaGVkIHRvIGFuIGludGVybmFsIG5ldHdvcmsuIEkndmUgc2V0IHRo ZSBmb2xsb3dpbmcgcW9zIHBhcmFtZXRlcnMgb24gZWFjaCBWSUYgaW50ZXJmYWNlLg0KDQp4ZSB2 aWYtcGFyYW0tc2V0IHV1aWQ9PFZJRiBVVUlEPiBxb3NfYWxnb3JpdGhtX3R5cGU9cmF0ZWxpbWl0 DQp4ZSB2aWYtcGFyYW0tc2V0IHV1aWQ9PFZJRiBVVUlEPiBxb3NfYWxnb3JpdGhtX3BhcmFtczpr YnBzPTEwMA0KDQppcGVyZiBpcyBzaG93aW5nIG1lIGJhbmR3aWR0aCByYXRlcyBiZXR3ZWVuIHRo ZSB0d28gVk1TIHRoYXQgYXJlbid0IGxpbWl0ZWQgdG8gMTAwIGticHMuIEFtIEkgbWlzc2luZyBz b21ldGhpbmc/DQoNCmticHMgaXMgbm90IGticHMsIGJ1dCBhIEtpbG9CWVRFU3BlclNlY29uZC4g UmVhbGx5IHN0cmFuZ2UsIGJ1dCBpdCBpcy4ga2Jwcz0xMiB3aWxsIG1ha2UgaXQgMTAwa3Bicy4N Cg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClhlbi1h cGkgbWFpbGluZyBsaXN0DQpYZW4tYXBpQGxpc3RzLnhlbi5vcmc8bWFpbHRvOlhlbi1hcGlAbGlz dHMueGVuLm9yZz4NCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5m by94ZW4tYXBpDQoNCg== --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE65LONPMAILBOX01_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5 OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZp bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0 LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj b3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNv QWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxv b24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm b250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNw YW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQt ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkJh bGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1z by1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglm b250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6 RU4tR0I7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1sYW5ndWFn ZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJ bWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJ e3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+ DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+ PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4 dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxh eW91dD48L3htbD48IVtlbmRpZl0tLT48L2hlYWQ+PGJvZHkgbGFuZz1FTi1HQiBsaW5rPWJsdWUg dmxpbms9cHVycGxlPjxkaXYgY2xhc3M9V29yZFNlY3Rpb24xPjxwIGNsYXNzPU1zb05vcm1hbD48 c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt c2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkhpIFJ1c2hpa2VzaCwgSeKAmXZlIG1hZGUgYSBtaXN0YWtl IOKAkyB0aGlzIGZpeCBkaWQgZ2V0IGludG8gWENQIDEuNi4xMC4gSXQgZGlkbuKAmXQgbWFrZSBp dCBpbnRvIHZlcnNpb24gNi4xIG9mIGNvbW1lcmNpYWwgWGVuU2VydmVyLCB3aGljaCBpcyB3aGF0 IGNvbmZ1c2VkIG1lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNw YW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNl cmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9 TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxp YnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+VGhlIG9yaWdpbmFsIHByb2JsZW0gY291 bGQgc3RpbGwgYmUgY2F1c2VkIGJ5IGtpbG9iaXQva2lsb2J5dGUgY29uZnVzaW9uLCBhcyBHZW9y Z2Ugc3VnZ2VzdHMuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3Bh biBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy aWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1N c29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGli cmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5Kb2huPG86cD48L286cD48L3NwYW4+PC9w PjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9v OnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PGI+PHNwYW4gbGFuZz1FTi1VUyBzdHls ZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPkZy b206PC9zcGFuPjwvYj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2Zv bnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+IFJ1c2hpa2VzaCBKYWRoYXYgW21haWx0 bzoycnVzaGlrZXNoakBnbWFpbC5jb21dIDxicj48Yj5TZW50OjwvYj4gMTQgSmFudWFyeSAyMDEz IDE0OjM5PGJyPjxiPlRvOjwvYj4gSm9obiBFbHNlPGJyPjxiPkNjOjwvYj4geGVuLWFwaUBsaXN0 cy54ZW4ub3JnPGJyPjxiPlN1YmplY3Q6PC9iPiBSZTogW1hlbi1BUEldIHFvc19hbGdvcml0aG1f dHlwZT1yYXRlbGltaXQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxv OnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRv bToxMi4wcHQnPkhlbGxvIEpvaG4sPGJyPjxicj5TaW5jZSB0aGUgY29tbWl0IGlzIDQgbW9udGhz IG9sZCBjYW4gd2UgY29uc2lkZXIgdGhhdCBpdCBpcyBmaXhlZCBpbiBYQ1AxLjYuMTAgb3IgYXJl IHlvdSBzdWdnZXN0aW5nIHRoYXQgdGhlIGN1cnJlbnQgc3RhYmxlIFhDUDEuNi4xMCBoYXMgdGhp cyBrbm93biBidWcgPyAoIEkgYXNzdW1lZCAybmQgYnV0IGp1c3Qgd2FudCB0byBjb25maXJtICk8 YnI+PGJyPkJ5IGxvb2tpbmcgYXQgcGF0Y2gsIGl0IGxvb2tzIHNhZmUgdG8gbG9jYWxseSBpbnRl Z3JhdGUgaW50byBYQ1AxLjYuMTAgeGFwaS5zcmMucnBtLiBBbnkgc3VnZ2VzdGlvbnMgPzxvOnA+ PC9vOnA+PC9wPjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPk9uIE1vbiwgSmFuIDE0LCAyMDEzIGF0 IDc6MjUgUE0sIEpvaG4gRWxzZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpvaG4uZWxzZUBjaXRyaXgu Y29tIiB0YXJnZXQ9Il9ibGFuayI+am9obi5lbHNlQGNpdHJpeC5jb208L2E+Jmd0OyB3cm90ZTo8 bzpwPjwvbzpwPjwvcD48ZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFy Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9 J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xv cjojMUY0OTdEJz5UaGVyZeKAmXMgYWxzbyBhIGtub3duIGJ1ZyBpbiBYQ1AgMS42LCB3aGVyZSB0 aGUgQVBJIFFvUyBzZXR0aW5ncyBkb27igJl0IGFjdHVhbGx5IGdldCBwYXNzZWQgZG93biB0byBY ZW4uIFRoZSBtYXN0ZXIgYnJhbmNoIHBhdGNoIGlzIGhlcmU6IDxhIGhyZWY9Imh0dHBzOi8vZ2l0 aHViLmNvbS94ZW4tb3JnL3hlbi1hcGkvY29tbWl0LzRmYjRiOTZiMTBjMmQ0MGNkNWUxNjY4NDU2 NTlmMjc4ODJjNmRhZTUiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL2dpdGh1Yi5jb20veGVuLW9y Zy94ZW4tYXBpL2NvbW1pdC80ZmI0Yjk2YjEwYzJkNDBjZDVlMTY2ODQ1NjU5ZjI3ODgyYzZkYWU1 PC9hPjwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1t YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz48c3BhbiBzdHls ZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2Nv bG9yOiMxRjQ5N0QnPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3Jt YWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph dXRvJz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIs InNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkpvaG48L3NwYW4+PG86cD48L286cD48L3A+PHAg Y2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu LWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p bHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86 cD48L286cD48L3A+PGRpdj48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlk ICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSc+PHAgY2xhc3M9TXNvTm9y bWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6 YXV0byc+PGI+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZh bWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPUVO LVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNl cmlmIic+IDxhIGhyZWY9Im1haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyIgdGFy Z2V0PSJfYmxhbmsiPnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPC9hPiBbbWFpbHRvOjxh IGhyZWY9Im1haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyIgdGFyZ2V0PSJfYmxh bmsiPnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPC9hPl0gPGI+T24gQmVoYWxmIE9mIDwv Yj5HZW9yZ2UgU2h1a2xpbjxicj48Yj5TZW50OjwvYj4gMTQgSmFudWFyeSAyMDEzIDEzOjMzPGJy PjxiPlRvOjwvYj4gPGEgaHJlZj0ibWFpbHRvOnhlbi1hcGlAbGlzdHMueGVuLm9yZyIgdGFyZ2V0 PSJfYmxhbmsiPnhlbi1hcGlAbGlzdHMueGVuLm9yZzwvYT48YnI+PGI+U3ViamVjdDo8L2I+IFJl OiBbWGVuLUFQSV0gcW9zX2FsZ29yaXRobV90eXBlPXJhdGVsaW1pdDwvc3Bhbj48bzpwPjwvbzpw PjwvcD48L2Rpdj48L2Rpdj48ZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28t bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+Jm5ic3A7PG86 cD48L286cD48L3A+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9w LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4xNC4wMS4yMDEzIDAzOjU1LCBN YXR0aGV3IFNwYWgg0L/QuNGI0LXRgjo8bzpwPjwvbzpwPjwvcD48L2Rpdj48YmxvY2txdW90ZSBz dHlsZT0nbWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Jz48cCBjbGFzcz1Nc29O b3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs dDphdXRvJz5IZXkgZXZlcnlvbmUsIDxvOnA+PC9vOnA+PC9wPjxkaXY+PHAgY2xhc3M9TXNvTm9y bWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6 YXV0byc+Jm5ic3A7PG86cD48L286cD48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwg c3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv Jz5JJ20gY3VycmVudGx5IHRlc3RpbmcgYW5kIGRvY3VtZW50aW5nIHRoZSBxb3MgcGFyYW1ldGVy cyBmb3IgVklGIGludGVyZmFjZXMuIEkndmUgc2V0IHVwIHR3byBWTXMgd2l0aCBWSUYgaW50ZXJm YWNlcyBhdHRhY2hlZCB0byBhbiBpbnRlcm5hbCBuZXR3b3JrLiBJJ3ZlIHNldCB0aGUgZm9sbG93 aW5nIHFvcyBwYXJhbWV0ZXJzIG9uIGVhY2ggVklGIGludGVyZmFjZS48bzpwPjwvbzpwPjwvcD48 L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1 dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8nPiZuYnNwOzxvOnA+PC9vOnA+PC9wPjwvZGl2 PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PGk+eGUgdmlmLXBhcmFtLXNldCB1dWlkPSZsdDtW SUYgVVVJRCZndDsgcW9zX2FsZ29yaXRobV90eXBlPXJhdGVsaW1pdDwvaT48bzpwPjwvbzpwPjwv cD48L2Rpdj48ZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRv cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PGk+eGUgdmlmLXBhcmFtLXNl dCB1dWlkPSZsdDtWSUYgVVVJRCZndDsgcW9zX2FsZ29yaXRobV9wYXJhbXM6a2Jwcz0xMDA8L2k+ PG86cD48L286cD48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1t YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4mbmJzcDsgJm5i c3A7PG86cD48L286cD48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21z by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz5pcGVyZiBp cyBzaG93aW5nIG1lIGJhbmR3aWR0aCByYXRlcyBiZXR3ZWVuIHRoZSB0d28gVk1TIHRoYXQgYXJl bid0IGxpbWl0ZWQgdG8gMTAwIGticHMuIEFtIEkgbWlzc2luZyBzb21ldGhpbmc/Jm5ic3A7PG86 cD48L286cD48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJn aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4mbmJzcDs8bzpwPjwv bzpwPjwvcD48L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxl PSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCc+a2JwcyBpcyBu b3Qga2JwcywgYnV0IGEgS2lsb0JZVEVTcGVyU2Vjb25kLiBSZWFsbHkgc3RyYW5nZSwgYnV0IGl0 IGlzLiBrYnBzPTEyIHdpbGwgbWFrZSBpdCAxMDBrcGJzLjxvOnA+PC9vOnA+PC9wPjwvZGl2Pjwv ZGl2PjwvZGl2PjwvZGl2PjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbTox Mi4wcHQnPjxicj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Xzxicj5YZW4tYXBpIG1haWxpbmcgbGlzdDxicj48YSBocmVmPSJtYWlsdG86WGVuLWFwaUBsaXN0 cy54ZW4ub3JnIj5YZW4tYXBpQGxpc3RzLnhlbi5vcmc8L2E+PGJyPjxhIGhyZWY9Imh0dHA6Ly9s aXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpIiB0YXJnZXQ9Il9i bGFuayI+aHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1h cGk8L2E+PG86cD48L286cD48L3A+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7 PC9vOnA+PC9wPjwvZGl2PjwvYm9keT48L2h0bWw+ --_000_7EA643C653F17F4C80DE959E978F10EDFBF75ABE65LONPMAILBOX01_-- --===============8532426227413904537== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8532426227413904537==-- From xen-api-bounces@lists.xen.org Mon Jan 14 16:38:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 16:38:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tun3V-0002ws-Fa; Mon, 14 Jan 2013 16:38:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tun3U-0002wl-5e for xen-api@lists.xen.org; Mon, 14 Jan 2013 16:38:36 +0000 Received: from [85.158.139.211:40230] by server-16.bemta-5.messagelabs.com id 9E/CA-09208-B8434F05; Mon, 14 Jan 2013 16:38:35 +0000 X-Env-Sender: spahmatthew@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1358181512!18119955!1 X-Originating-IP: [209.85.160.48] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10304 invoked from network); 14 Jan 2013 16:38:34 -0000 Received: from mail-pb0-f48.google.com (HELO mail-pb0-f48.google.com) (209.85.160.48) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 16:38:34 -0000 Received: by mail-pb0-f48.google.com with SMTP id rq13so2243368pbb.35 for ; Mon, 14 Jan 2013 08:38:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=eN5+d+VX0GTLKLBcpFBfEQBDtxZ44b9tBAWzl47lfuY=; b=TcPdZgwyE7S65mQ1VL0GqkzMNiThNt+uy6clhFZw1FgzmZ8AQ+g9XJrzaxhln/AmHi Nt648vY5/P3n2bdF5YSDgku+lKfnND6MCslR3x6rqfbyoZdBs1ioOv6oOWxvyfoCQSuC Zl64cYqfbwEdONHvMRHJX9oWpr28NWma/Zs4gSvUMZaAGnjH6KbIfGZlt+UkBecIhqrs kbkYzXNMFm1JSHsUsqMRnaI/bMDFcVGB8Gm0c7iXhRdFA2ktu0y9sXrTP+L8Z9lgPE4+ lk0g19RVRZQS+BxQVtqxkpQYHVD2kCNQ+YdX7nzDfX0XdSH1obDnhRjVhnS0VgbbYoM2 5b4g== MIME-Version: 1.0 Received: by 10.68.227.33 with SMTP id rx1mr216272325pbc.67.1358181512475; Mon, 14 Jan 2013 08:38:32 -0800 (PST) Received: by 10.68.203.72 with HTTP; Mon, 14 Jan 2013 08:38:32 -0800 (PST) Date: Mon, 14 Jan 2013 08:38:32 -0800 Message-ID: From: Matthew Spah To: xen-api@lists.xen.org Subject: Re: [Xen-API] qos_algorithm_type=ratelimit (George Shuklin) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9109497778002066306==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============9109497778002066306== Content-Type: multipart/alternative; boundary=047d7b1631bf97750e04d34246fa --047d7b1631bf97750e04d34246fa Content-Type: text/plain; charset=ISO-8859-1 14.01.2013 03:55, Matthew Spah ?????: >> Hey everyone, >> >> I'm currently testing and documenting the qos parameters for VIF >> interfaces. I've set up two VMs with VIF interfaces attached to an >> internal network. I've set the following qos parameters on each VIF >> interface. >> >> /xe vif-param-set uuid= qos_algorithm_type=ratelimit/ >> /xe vif-param-set uuid= qos_algorithm_params:kbps=100/ >> iperf is showing me bandwidth rates between the two VMS that aren't >> limited to 100 kbps. Am I missing something? >> >kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. >kbps=12 will make it 100kpbs. Thanks for the responses everyone. I will go ahead and compare my results to what everyone is telling me. Are there any plans to change this acronym? Can I expect the same results with mbps? (Mbps=MBps) -- - Matthew Spah Computer Information Sciences Tutor for Everett Community College Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc Xenapi Admin Project Member http://xenapiadmin.com CompTIA Security+ Certified and Cisco CCNA Certified Arlington, WA Cell 425-319-8676 "And all we ever were Just zeroes and ones" - Trent Reznor "If you want to make enemies, try to change something." - Woodrow T. Wilson --047d7b1631bf97750e04d34246fa Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
14.01.2013 03:55, Matthew Spah ?????:
>> Hey everyone,=
>>
>> I'm currently testing and docume= nting the qos parameters for VIF
>> interfaces. I've se= t up two VMs with VIF interfaces attached to an
>> internal network. I've set the following qos parameters o= n each VIF
>> interface.
>>
>&= gt; /xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_type=3Dratelimi= t/
>> /xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_param= s:kbps=3D100/
>> iperf is showing me bandwidth rates betwee= n the two VMS that aren't
>> limited to 100 kbps. Am I = missing something?
>>
>kbps is not kbps, but a KiloBYTESperSecond. Rea= lly strange, but it is.
>kbps=3D12 will make it 100kpbs.
=

Thanks for the=A0responses=A0everyone. I will go ahead = and compare my results to what everyone is telling me. Are there any plans = to change this=A0acronym?

Can I expect the same results with mbps? (Mbps=3DMBps)<= /div>

--
- Matthew Spah
Computer Information Sciences = Tutor for Everett Community College
Electronic Monitoring Jr. Systems E= ngineer for Ocean Systems Inc
Xenapi Admin Project Member=A0http://xenapiadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlington, WA = Cell 425-319-8676

"And all we ever were
Just zeroes an= d ones"=A0- Trent Reznor


"If you want to make enemies, try to change s= omething." - Woodrow T. Wilson
--047d7b1631bf97750e04d34246fa-- --===============9109497778002066306== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============9109497778002066306==-- From xen-api-bounces@lists.xen.org Mon Jan 14 16:38:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 16:38:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tun3V-0002ws-Fa; Mon, 14 Jan 2013 16:38:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tun3U-0002wl-5e for xen-api@lists.xen.org; Mon, 14 Jan 2013 16:38:36 +0000 Received: from [85.158.139.211:40230] by server-16.bemta-5.messagelabs.com id 9E/CA-09208-B8434F05; Mon, 14 Jan 2013 16:38:35 +0000 X-Env-Sender: spahmatthew@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1358181512!18119955!1 X-Originating-IP: [209.85.160.48] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10304 invoked from network); 14 Jan 2013 16:38:34 -0000 Received: from mail-pb0-f48.google.com (HELO mail-pb0-f48.google.com) (209.85.160.48) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2013 16:38:34 -0000 Received: by mail-pb0-f48.google.com with SMTP id rq13so2243368pbb.35 for ; Mon, 14 Jan 2013 08:38:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=eN5+d+VX0GTLKLBcpFBfEQBDtxZ44b9tBAWzl47lfuY=; b=TcPdZgwyE7S65mQ1VL0GqkzMNiThNt+uy6clhFZw1FgzmZ8AQ+g9XJrzaxhln/AmHi Nt648vY5/P3n2bdF5YSDgku+lKfnND6MCslR3x6rqfbyoZdBs1ioOv6oOWxvyfoCQSuC Zl64cYqfbwEdONHvMRHJX9oWpr28NWma/Zs4gSvUMZaAGnjH6KbIfGZlt+UkBecIhqrs kbkYzXNMFm1JSHsUsqMRnaI/bMDFcVGB8Gm0c7iXhRdFA2ktu0y9sXrTP+L8Z9lgPE4+ lk0g19RVRZQS+BxQVtqxkpQYHVD2kCNQ+YdX7nzDfX0XdSH1obDnhRjVhnS0VgbbYoM2 5b4g== MIME-Version: 1.0 Received: by 10.68.227.33 with SMTP id rx1mr216272325pbc.67.1358181512475; Mon, 14 Jan 2013 08:38:32 -0800 (PST) Received: by 10.68.203.72 with HTTP; Mon, 14 Jan 2013 08:38:32 -0800 (PST) Date: Mon, 14 Jan 2013 08:38:32 -0800 Message-ID: From: Matthew Spah To: xen-api@lists.xen.org Subject: Re: [Xen-API] qos_algorithm_type=ratelimit (George Shuklin) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9109497778002066306==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============9109497778002066306== Content-Type: multipart/alternative; boundary=047d7b1631bf97750e04d34246fa --047d7b1631bf97750e04d34246fa Content-Type: text/plain; charset=ISO-8859-1 14.01.2013 03:55, Matthew Spah ?????: >> Hey everyone, >> >> I'm currently testing and documenting the qos parameters for VIF >> interfaces. I've set up two VMs with VIF interfaces attached to an >> internal network. I've set the following qos parameters on each VIF >> interface. >> >> /xe vif-param-set uuid= qos_algorithm_type=ratelimit/ >> /xe vif-param-set uuid= qos_algorithm_params:kbps=100/ >> iperf is showing me bandwidth rates between the two VMS that aren't >> limited to 100 kbps. Am I missing something? >> >kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. >kbps=12 will make it 100kpbs. Thanks for the responses everyone. I will go ahead and compare my results to what everyone is telling me. Are there any plans to change this acronym? Can I expect the same results with mbps? (Mbps=MBps) -- - Matthew Spah Computer Information Sciences Tutor for Everett Community College Electronic Monitoring Jr. Systems Engineer for Ocean Systems Inc Xenapi Admin Project Member http://xenapiadmin.com CompTIA Security+ Certified and Cisco CCNA Certified Arlington, WA Cell 425-319-8676 "And all we ever were Just zeroes and ones" - Trent Reznor "If you want to make enemies, try to change something." - Woodrow T. Wilson --047d7b1631bf97750e04d34246fa Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
14.01.2013 03:55, Matthew Spah ?????:
>> Hey everyone,=
>>
>> I'm currently testing and docume= nting the qos parameters for VIF
>> interfaces. I've se= t up two VMs with VIF interfaces attached to an
>> internal network. I've set the following qos parameters o= n each VIF
>> interface.
>>
>&= gt; /xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_type=3Dratelimi= t/
>> /xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_param= s:kbps=3D100/
>> iperf is showing me bandwidth rates betwee= n the two VMS that aren't
>> limited to 100 kbps. Am I = missing something?
>>
>kbps is not kbps, but a KiloBYTESperSecond. Rea= lly strange, but it is.
>kbps=3D12 will make it 100kpbs.
=

Thanks for the=A0responses=A0everyone. I will go ahead = and compare my results to what everyone is telling me. Are there any plans = to change this=A0acronym?

Can I expect the same results with mbps? (Mbps=3DMBps)<= /div>

--
- Matthew Spah
Computer Information Sciences = Tutor for Everett Community College
Electronic Monitoring Jr. Systems E= ngineer for Ocean Systems Inc
Xenapi Admin Project Member=A0http://xenapiadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlington, WA = Cell 425-319-8676

"And all we ever were
Just zeroes an= d ones"=A0- Trent Reznor


"If you want to make enemies, try to change s= omething." - Woodrow T. Wilson
--047d7b1631bf97750e04d34246fa-- --===============9109497778002066306== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============9109497778002066306==-- From xen-api-bounces@lists.xen.org Mon Jan 14 19:36:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 19:36:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tupp6-00011N-33; Mon, 14 Jan 2013 19:35:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tupp4-00011I-Ui for xen-api@lists.xen.org; Mon, 14 Jan 2013 19:35:55 +0000 Received: from [85.158.143.35:59757] by server-1.bemta-4.messagelabs.com id A7/D7-18740-A1E54F05; Mon, 14 Jan 2013 19:35:54 +0000 X-Env-Sender: mephisto@mephis.to X-Msg-Ref: server-16.tower-21.messagelabs.com!1358192151!13098040!1 X-Originating-IP: [212.77.170.22] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14369 invoked from network); 14 Jan 2013 19:35:52 -0000 Received: from mx2.netzblick.de (HELO mx2.netzblick.de) (212.77.170.22) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2013 19:35:52 -0000 Received: from [192.168.7.3] (core.niedermayr.de [213.166.224.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.netzblick.de (Postfix) with ESMTP id AFCA4281CB for ; Mon, 14 Jan 2013 20:35:50 +0100 (CET) Message-ID: <50F45E1B.7040706@mephis.to> Date: Mon, 14 Jan 2013 20:35:55 +0100 From: =?ISO-8859-1?Q?Bastian_M=E4user?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50EBED56.2080104@mephis.to> <50EBF911.1080101@mephis.to> <50ED3790.3050103@mephis.to> In-Reply-To: X-Enigmail-Version: 1.4.4 Subject: Re: [Xen-API] Xcp does not boot: I need to specify rootdelay X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7329059136618665718==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7329059136618665718== Content-Type: multipart/alternative; boundary="------------010000080802010903020209" This is a multi-part message in MIME format. --------------010000080802010903020209 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Still running stable? Am 09.01.2013 10:27, schrieb Mario Giammarco: > > Yes the system is now on 24/24. > > Il giorno 09/gen/2013 10:25, "Bastian Mäuser" > ha scritto: > > please let me know if USB boot runs stable for you.. > > Am 08.01.2013 21 :41, schrieb Mario Giammarco: >> >> >> >> 2013/1/8 Bastian Mäuser > > >> >> Please read correctly.. >> >> From #5 you have the instruction on how to modify your initrd >> on the Host to make it bootable from anythings USB like.. >> >> >> Sorry my android device shown me only first page. >> >> eg: >> >> Do THIS b4 the first boot on a second console: >> >> mkdir /tmp/sda >> mount -t ext3 /dev/sda1 /tmp/sda >> >> >> To thank you I suggest here to do avoid copy and do: >> >> mount -t sysfs /sys /tmp/sda/sys >> >> Then chroot /tmp/sda and continue from original >> >> >> >> >> chmod -R 664 /sys/block >> cp -R /sys/block /tmp/sda/sys/ >> # Ignore I/O errors >> chroot /tmp/sda >> cd /boot >> mv initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img >> initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img.old >> mkinitrd --with-usb >> initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img >> 2.6.18-128.1.6.el5.xs5.5.0.505.1024xen >> >> replace the version numers with your's.. >> >> Am 08.01.2013 11 :26, schrieb Mario >> Giammarco: >>> >>> Ok thanks for the reply but the link in the wiki is wrong: >>> it sends me to a page that helps people with keys less than 16GB >>> >>> Il giorno 08/gen/2013 10:56, "Bastian Mäuser" >>> > ha scritto: >>> >>> Hi there, >>> >>> the Probleme is not the rootdelay, but the USB Support >>> which is missing >>> in the initrd.. >>> >>> Follow this instructions to fix it: >>> >>> http://wiki.xen.org/wiki/XCP_FAQ_General#Can_I_install_XCP_to_a_USB_drive_.2F_SD_Card >>> >>> but be warned: for sdcard and usbkey did not run stable. >>> >>> greetings, >>> Bastian >>> >>> Am 08.01.2013 10 :21, schrieb Mario >>> Giammarco: >>> > Hello, >>> > I am trying xcp on a HP Microserver N40L. >>> > I have installed it on USB key. >>> > I am not able to boot it because it does not find root. >>> > In old kernels like 2.6 used in xcp is quite common >>> this problem and >>> > I can fix it with rootdelay=60. >>> > But xcp use a "extlinux" bootloader and I cannot try >>> the option. >>> > I have found and modified a extlinux.conf file but >>> without luck. >>> > How can I pass rootdelay option to the kernel at boot? >>> > >>> > Thanks, >>> > Mario >>> > >>> > >>> > _______________________________________________ >>> > Xen-api mailing list >>> > Xen-api@lists.xen.org >>> > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >>> > >>> >> >> > --------------010000080802010903020209 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Still running stable?

Am 09.01.2013 10:27, schrieb Mario Giammarco:

Yes the system is now on 24/24.

Il giorno 09/gen/2013 10:25, "Bastian Mäuser" <mephisto@mephis.to> ha scritto:
please let me know if USB boot runs stable for you..

Am 08.01.2013 21:41, schrieb Mario Giammarco:



2013/1/8 Bastian Mäuser <mephisto@mephis.to>
Please read correctly..

From #5 you have the instruction on how to modify your initrd on the Host to make it bootable from anythings USB like..


Sorry my android device shown me only first page. 
eg:

Do THIS b4 the first boot on a second console:

mkdir /tmp/sda
mount -t ext3 /dev/sda1 /tmp/sda

To thank you I suggest here to do avoid copy and do:

mount -t sysfs /sys /tmp/sda/sys

Then chroot /tmp/sda and continue from original

 

chmod -R 664 /sys/block
cp -R /sys/block /tmp/sda/sys/
# Ignore I/O errors
chroot /tmp/sda
cd /boot
mv initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img.old
mkinitrd --with-usb initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img 2.6.18-128.1.6.el5.xs5.5.0.505.1024xen

replace the version numers with your's..

Am 08.01.2013 11:26, schrieb Mario Giammarco:

Ok thanks for the reply but the link in the wiki is wrong: it sends me to a page that helps people with keys less than 16GB

Il giorno 08/gen/2013 10:56, "Bastian Mäuser" <mephisto@mephis.to> ha scritto:
Hi there,

the Probleme is not the rootdelay, but the USB Support which is missing
in the initrd..

Follow this instructions to fix it:

http://wiki.xen.org/wiki/XCP_FAQ_General#Can_I_install_XCP_to_a_USB_drive_.2F_SD_Card

but be warned: for sdcard and usbkey did not run stable.

greetings,
Bastian

Am 08.01.2013 10:21, schrieb Mario Giammarco:
> Hello,
> I am trying xcp on a HP Microserver N40L.
> I have installed it on USB key.
> I am not able to boot it because it does not find root.
> In old kernels like 2.6 used in xcp is quite common this problem and
> I can fix it with rootdelay=60.
> But xcp use a "extlinux" bootloader and I cannot try the option.
> I have found and modified a extlinux.conf file but without luck.
> How can I pass rootdelay option to the kernel at boot?
>
> Thanks,
> Mario
>
>
> _______________________________________________
> Xen-api mailing list
> Xen-api@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
>





--------------010000080802010903020209-- --===============7329059136618665718== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7329059136618665718==-- From xen-api-bounces@lists.xen.org Mon Jan 14 19:36:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 19:36:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tupp6-00011N-33; Mon, 14 Jan 2013 19:35:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tupp4-00011I-Ui for xen-api@lists.xen.org; Mon, 14 Jan 2013 19:35:55 +0000 Received: from [85.158.143.35:59757] by server-1.bemta-4.messagelabs.com id A7/D7-18740-A1E54F05; Mon, 14 Jan 2013 19:35:54 +0000 X-Env-Sender: mephisto@mephis.to X-Msg-Ref: server-16.tower-21.messagelabs.com!1358192151!13098040!1 X-Originating-IP: [212.77.170.22] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14369 invoked from network); 14 Jan 2013 19:35:52 -0000 Received: from mx2.netzblick.de (HELO mx2.netzblick.de) (212.77.170.22) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2013 19:35:52 -0000 Received: from [192.168.7.3] (core.niedermayr.de [213.166.224.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.netzblick.de (Postfix) with ESMTP id AFCA4281CB for ; Mon, 14 Jan 2013 20:35:50 +0100 (CET) Message-ID: <50F45E1B.7040706@mephis.to> Date: Mon, 14 Jan 2013 20:35:55 +0100 From: =?ISO-8859-1?Q?Bastian_M=E4user?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50EBED56.2080104@mephis.to> <50EBF911.1080101@mephis.to> <50ED3790.3050103@mephis.to> In-Reply-To: X-Enigmail-Version: 1.4.4 Subject: Re: [Xen-API] Xcp does not boot: I need to specify rootdelay X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7329059136618665718==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7329059136618665718== Content-Type: multipart/alternative; boundary="------------010000080802010903020209" This is a multi-part message in MIME format. --------------010000080802010903020209 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Still running stable? Am 09.01.2013 10:27, schrieb Mario Giammarco: > > Yes the system is now on 24/24. > > Il giorno 09/gen/2013 10:25, "Bastian Mäuser" > ha scritto: > > please let me know if USB boot runs stable for you.. > > Am 08.01.2013 21 :41, schrieb Mario Giammarco: >> >> >> >> 2013/1/8 Bastian Mäuser > > >> >> Please read correctly.. >> >> From #5 you have the instruction on how to modify your initrd >> on the Host to make it bootable from anythings USB like.. >> >> >> Sorry my android device shown me only first page. >> >> eg: >> >> Do THIS b4 the first boot on a second console: >> >> mkdir /tmp/sda >> mount -t ext3 /dev/sda1 /tmp/sda >> >> >> To thank you I suggest here to do avoid copy and do: >> >> mount -t sysfs /sys /tmp/sda/sys >> >> Then chroot /tmp/sda and continue from original >> >> >> >> >> chmod -R 664 /sys/block >> cp -R /sys/block /tmp/sda/sys/ >> # Ignore I/O errors >> chroot /tmp/sda >> cd /boot >> mv initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img >> initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img.old >> mkinitrd --with-usb >> initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img >> 2.6.18-128.1.6.el5.xs5.5.0.505.1024xen >> >> replace the version numers with your's.. >> >> Am 08.01.2013 11 :26, schrieb Mario >> Giammarco: >>> >>> Ok thanks for the reply but the link in the wiki is wrong: >>> it sends me to a page that helps people with keys less than 16GB >>> >>> Il giorno 08/gen/2013 10:56, "Bastian Mäuser" >>> > ha scritto: >>> >>> Hi there, >>> >>> the Probleme is not the rootdelay, but the USB Support >>> which is missing >>> in the initrd.. >>> >>> Follow this instructions to fix it: >>> >>> http://wiki.xen.org/wiki/XCP_FAQ_General#Can_I_install_XCP_to_a_USB_drive_.2F_SD_Card >>> >>> but be warned: for sdcard and usbkey did not run stable. >>> >>> greetings, >>> Bastian >>> >>> Am 08.01.2013 10 :21, schrieb Mario >>> Giammarco: >>> > Hello, >>> > I am trying xcp on a HP Microserver N40L. >>> > I have installed it on USB key. >>> > I am not able to boot it because it does not find root. >>> > In old kernels like 2.6 used in xcp is quite common >>> this problem and >>> > I can fix it with rootdelay=60. >>> > But xcp use a "extlinux" bootloader and I cannot try >>> the option. >>> > I have found and modified a extlinux.conf file but >>> without luck. >>> > How can I pass rootdelay option to the kernel at boot? >>> > >>> > Thanks, >>> > Mario >>> > >>> > >>> > _______________________________________________ >>> > Xen-api mailing list >>> > Xen-api@lists.xen.org >>> > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >>> > >>> >> >> > --------------010000080802010903020209 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Still running stable?

Am 09.01.2013 10:27, schrieb Mario Giammarco:

Yes the system is now on 24/24.

Il giorno 09/gen/2013 10:25, "Bastian Mäuser" <mephisto@mephis.to> ha scritto:
please let me know if USB boot runs stable for you..

Am 08.01.2013 21:41, schrieb Mario Giammarco:



2013/1/8 Bastian Mäuser <mephisto@mephis.to>
Please read correctly..

From #5 you have the instruction on how to modify your initrd on the Host to make it bootable from anythings USB like..


Sorry my android device shown me only first page. 
eg:

Do THIS b4 the first boot on a second console:

mkdir /tmp/sda
mount -t ext3 /dev/sda1 /tmp/sda

To thank you I suggest here to do avoid copy and do:

mount -t sysfs /sys /tmp/sda/sys

Then chroot /tmp/sda and continue from original

 

chmod -R 664 /sys/block
cp -R /sys/block /tmp/sda/sys/
# Ignore I/O errors
chroot /tmp/sda
cd /boot
mv initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img.old
mkinitrd --with-usb initrd-2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.img 2.6.18-128.1.6.el5.xs5.5.0.505.1024xen

replace the version numers with your's..

Am 08.01.2013 11:26, schrieb Mario Giammarco:

Ok thanks for the reply but the link in the wiki is wrong: it sends me to a page that helps people with keys less than 16GB

Il giorno 08/gen/2013 10:56, "Bastian Mäuser" <mephisto@mephis.to> ha scritto:
Hi there,

the Probleme is not the rootdelay, but the USB Support which is missing
in the initrd..

Follow this instructions to fix it:

http://wiki.xen.org/wiki/XCP_FAQ_General#Can_I_install_XCP_to_a_USB_drive_.2F_SD_Card

but be warned: for sdcard and usbkey did not run stable.

greetings,
Bastian

Am 08.01.2013 10:21, schrieb Mario Giammarco:
> Hello,
> I am trying xcp on a HP Microserver N40L.
> I have installed it on USB key.
> I am not able to boot it because it does not find root.
> In old kernels like 2.6 used in xcp is quite common this problem and
> I can fix it with rootdelay=60.
> But xcp use a "extlinux" bootloader and I cannot try the option.
> I have found and modified a extlinux.conf file but without luck.
> How can I pass rootdelay option to the kernel at boot?
>
> Thanks,
> Mario
>
>
> _______________________________________________
> Xen-api mailing list
> Xen-api@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
>





--------------010000080802010903020209-- --===============7329059136618665718== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7329059136618665718==-- From xen-api-bounces@lists.xen.org Mon Jan 14 23:54:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 23:54:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tutqy-0006JA-Eh; Mon, 14 Jan 2013 23:54:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tutqw-0006J2-LV for xen-api@lists.xen.org; Mon, 14 Jan 2013 23:54:06 +0000 Received: from [85.158.143.99:54940] by server-3.bemta-4.messagelabs.com id 47/D3-19220-D9A94F05; Mon, 14 Jan 2013 23:54:05 +0000 X-Env-Sender: bailey.alex@live.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1358207644!20386572!1 X-Originating-IP: [65.55.111.142] X-SpamReason: No, hits=1.0 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_10_20,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27075 invoked from network); 14 Jan 2013 23:54:04 -0000 Received: from blu0-omc4-s3.blu0.hotmail.com (HELO blu0-omc4-s3.blu0.hotmail.com) (65.55.111.142) by server-11.tower-216.messagelabs.com with SMTP; 14 Jan 2013 23:54:04 -0000 Received: from BLU174-W20 ([65.55.111.135]) by blu0-omc4-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Jan 2013 15:54:04 -0800 X-EIP: [EK+cer0GJ/aX3eS/hXHYZUnb7zUAXBC8] X-Originating-Email: [bailey.alex@live.com] Message-ID: From: Alex Bailey To: Date: Mon, 14 Jan 2013 18:54:03 -0500 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 14 Jan 2013 23:54:04.0157 (UTC) FILETIME=[6EDB2AD0:01CDF2B2] Subject: [Xen-API] Guest Utilities X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6257428407066703377==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6257428407066703377== Content-Type: multipart/alternative; boundary="_62e6bcb4-82e9-44e8-8770-f090762cc454_" --_62e6bcb4-82e9-44e8-8770-f090762cc454_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Trying to install guest utilities into a Linux VM=2C Ubuntu 12.04.1=2C inst= alling from template provided by the default installation of XCP 1.6.1 Did not modify the template settings in any way=2C there is no way for me t= o even access the linux directory in the XS-tools.iso on the domU VM... I c= an see all the windows executables=2C and I see the linux directory folder= =2C but I cannot access it=2C it "does not exist" I followed several guides I could find online for xenserver 6.1=2C includin= g the VM guide and several blog posts (all which were just mirrors of the g= uide)=2C I am using XCP 1.6.1 as dom0=2C I do not require ubuntu=2C I simply am looking to create a locally optimize= d VM that will act as a host... Is there any documentation on the process of installing guest-utilities on = a domU? What it does to the domU=2C and how long it takes? I am just noticed that my XS-tools=2C is infact performing some tasks on th= e VM=2C I am going to let it be=2C as it is working extremely slowly=2C for= it has been nearly an hour. How long does this process generally take? and= is this what is suppose to show for domU guest optimization? It is running= on a server I am aiming to be optimized for I/O=2C I just recently built i= t=2C it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cor= es=2C should it take this long? Am I encountering a serious error? here is output: [1070.102324] Buffer I/O error on device xvdd=2C logical bl= ock 0[ 1191.332291] end_request: I/O error=2C dev xvdd=2C sector 0[ 1191.33= 2312] Buffer I/O error on device xvdd=2C logical block 0[ 1312.522333] end_= request: I/O error=2C dev xvdd=2C sector 0[ 1312.522354] Buffer I/O error o= n device xvdd=2C logical block 0[ 1433.722284] end_request: I/O error=2C de= v xvdd=2C sector 0[ 1433.722305] Buffer I/O error on device xvdd=2C logical= block 0[ 1554.932313] end_request: I/O error=2C dev xvdd=2C sector 0[ 1554= .932334] Buffer I/O error on device xvdd=2C logical block 0[ 1676.122281] e= nd_request: I/O error=2C dev xvdd=2C sector 0[ 1676.122302] Buffer I/O erro= r on device xvdd=2C logical block 0 Thank you very much for any input=2C it is greatly appreciated=2C = = --_62e6bcb4-82e9-44e8-8770-f090762cc454_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Trying to install guest utilities into a Linux VM=2C Ubuntu 12.04.1=2C inst= alling from template provided by the default installation of XCP 1.6.1
=

Did not modify the template settings in any way=2C ther= e is no way for me to even access the linux directory in the XS-tools.iso o= n the domU VM... I can see all the windows executables=2C and I see the lin= ux directory folder=2C but I cannot access it=2C it "does not exist"
<= div>
I followed several guides I could find online for xenser= ver 6.1=2C including the VM guide and several blog posts (all which were ju= st mirrors of the guide)=2C I am using XCP 1.6.1 as dom0=2C

I do not require ubuntu=2C I simply am looking to create a = locally optimized VM that will act as a host...

Is= there any documentation on the process of installing guest-utilities on a = domU? What it does to the domU=2C and how long it takes?

I am just noticed that my XS-tools=2C is infact performing some task= s on the VM=2C I am going to let it be=2C as it is working extremely slowly= =2C for it has been nearly an hour. How long does this process generally ta= ke? and is this what is suppose to show for domU guest optimization? It is = running on a server I am aiming to be optimized for I/O=2C I just recently = built it=2C it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and= 32 cores=2C should it take this long? Am I encountering a serious error?

here is output:
 =3B[1070.102324= ] Buffer I/O error on device xvdd=2C logical block 0
[ 1191.33229= 1] end_request: I/O error=2C dev xvdd=2C sector 0
[ 1191.332312] = Buffer I/O error on device xvdd=2C logical block 0
[ 1312.522333]= end_request: I/O error=2C dev xvdd=2C sector 0
[ 1312.522354] Bu= ffer I/O error on device xvdd=2C logical block 0
[ 1433.722284] e= nd_request: I/O error=2C dev xvdd=2C sector 0
[ 1433.722305] Buff= er I/O error on device xvdd=2C logical block 0
[ 1554.932313] end= _request: I/O error=2C dev xvdd=2C sector 0
[ 1554.932334] Buffer= I/O error on device xvdd=2C logical block 0
[ 1676.122281] end_r= equest: I/O error=2C dev xvdd=2C sector 0
[ 1676.122302] Buffer I= /O error on device xvdd=2C logical block 0

<= br>
Thank you very much for any input=2C it is greatly appreciate= d=2C =3B
= --_62e6bcb4-82e9-44e8-8770-f090762cc454_-- --===============6257428407066703377== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6257428407066703377==-- From xen-api-bounces@lists.xen.org Mon Jan 14 23:54:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 14 Jan 2013 23:54:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tutqy-0006JA-Eh; Mon, 14 Jan 2013 23:54:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tutqw-0006J2-LV for xen-api@lists.xen.org; Mon, 14 Jan 2013 23:54:06 +0000 Received: from [85.158.143.99:54940] by server-3.bemta-4.messagelabs.com id 47/D3-19220-D9A94F05; Mon, 14 Jan 2013 23:54:05 +0000 X-Env-Sender: bailey.alex@live.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1358207644!20386572!1 X-Originating-IP: [65.55.111.142] X-SpamReason: No, hits=1.0 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_10_20,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27075 invoked from network); 14 Jan 2013 23:54:04 -0000 Received: from blu0-omc4-s3.blu0.hotmail.com (HELO blu0-omc4-s3.blu0.hotmail.com) (65.55.111.142) by server-11.tower-216.messagelabs.com with SMTP; 14 Jan 2013 23:54:04 -0000 Received: from BLU174-W20 ([65.55.111.135]) by blu0-omc4-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Jan 2013 15:54:04 -0800 X-EIP: [EK+cer0GJ/aX3eS/hXHYZUnb7zUAXBC8] X-Originating-Email: [bailey.alex@live.com] Message-ID: From: Alex Bailey To: Date: Mon, 14 Jan 2013 18:54:03 -0500 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 14 Jan 2013 23:54:04.0157 (UTC) FILETIME=[6EDB2AD0:01CDF2B2] Subject: [Xen-API] Guest Utilities X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6257428407066703377==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6257428407066703377== Content-Type: multipart/alternative; boundary="_62e6bcb4-82e9-44e8-8770-f090762cc454_" --_62e6bcb4-82e9-44e8-8770-f090762cc454_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Trying to install guest utilities into a Linux VM=2C Ubuntu 12.04.1=2C inst= alling from template provided by the default installation of XCP 1.6.1 Did not modify the template settings in any way=2C there is no way for me t= o even access the linux directory in the XS-tools.iso on the domU VM... I c= an see all the windows executables=2C and I see the linux directory folder= =2C but I cannot access it=2C it "does not exist" I followed several guides I could find online for xenserver 6.1=2C includin= g the VM guide and several blog posts (all which were just mirrors of the g= uide)=2C I am using XCP 1.6.1 as dom0=2C I do not require ubuntu=2C I simply am looking to create a locally optimize= d VM that will act as a host... Is there any documentation on the process of installing guest-utilities on = a domU? What it does to the domU=2C and how long it takes? I am just noticed that my XS-tools=2C is infact performing some tasks on th= e VM=2C I am going to let it be=2C as it is working extremely slowly=2C for= it has been nearly an hour. How long does this process generally take? and= is this what is suppose to show for domU guest optimization? It is running= on a server I am aiming to be optimized for I/O=2C I just recently built i= t=2C it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cor= es=2C should it take this long? Am I encountering a serious error? here is output: [1070.102324] Buffer I/O error on device xvdd=2C logical bl= ock 0[ 1191.332291] end_request: I/O error=2C dev xvdd=2C sector 0[ 1191.33= 2312] Buffer I/O error on device xvdd=2C logical block 0[ 1312.522333] end_= request: I/O error=2C dev xvdd=2C sector 0[ 1312.522354] Buffer I/O error o= n device xvdd=2C logical block 0[ 1433.722284] end_request: I/O error=2C de= v xvdd=2C sector 0[ 1433.722305] Buffer I/O error on device xvdd=2C logical= block 0[ 1554.932313] end_request: I/O error=2C dev xvdd=2C sector 0[ 1554= .932334] Buffer I/O error on device xvdd=2C logical block 0[ 1676.122281] e= nd_request: I/O error=2C dev xvdd=2C sector 0[ 1676.122302] Buffer I/O erro= r on device xvdd=2C logical block 0 Thank you very much for any input=2C it is greatly appreciated=2C = = --_62e6bcb4-82e9-44e8-8770-f090762cc454_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Trying to install guest utilities into a Linux VM=2C Ubuntu 12.04.1=2C inst= alling from template provided by the default installation of XCP 1.6.1
=

Did not modify the template settings in any way=2C ther= e is no way for me to even access the linux directory in the XS-tools.iso o= n the domU VM... I can see all the windows executables=2C and I see the lin= ux directory folder=2C but I cannot access it=2C it "does not exist"
<= div>
I followed several guides I could find online for xenser= ver 6.1=2C including the VM guide and several blog posts (all which were ju= st mirrors of the guide)=2C I am using XCP 1.6.1 as dom0=2C

I do not require ubuntu=2C I simply am looking to create a = locally optimized VM that will act as a host...

Is= there any documentation on the process of installing guest-utilities on a = domU? What it does to the domU=2C and how long it takes?

I am just noticed that my XS-tools=2C is infact performing some task= s on the VM=2C I am going to let it be=2C as it is working extremely slowly= =2C for it has been nearly an hour. How long does this process generally ta= ke? and is this what is suppose to show for domU guest optimization? It is = running on a server I am aiming to be optimized for I/O=2C I just recently = built it=2C it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and= 32 cores=2C should it take this long? Am I encountering a serious error?

here is output:
 =3B[1070.102324= ] Buffer I/O error on device xvdd=2C logical block 0
[ 1191.33229= 1] end_request: I/O error=2C dev xvdd=2C sector 0
[ 1191.332312] = Buffer I/O error on device xvdd=2C logical block 0
[ 1312.522333]= end_request: I/O error=2C dev xvdd=2C sector 0
[ 1312.522354] Bu= ffer I/O error on device xvdd=2C logical block 0
[ 1433.722284] e= nd_request: I/O error=2C dev xvdd=2C sector 0
[ 1433.722305] Buff= er I/O error on device xvdd=2C logical block 0
[ 1554.932313] end= _request: I/O error=2C dev xvdd=2C sector 0
[ 1554.932334] Buffer= I/O error on device xvdd=2C logical block 0
[ 1676.122281] end_r= equest: I/O error=2C dev xvdd=2C sector 0
[ 1676.122302] Buffer I= /O error on device xvdd=2C logical block 0

<= br>
Thank you very much for any input=2C it is greatly appreciate= d=2C =3B
= --_62e6bcb4-82e9-44e8-8770-f090762cc454_-- --===============6257428407066703377== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6257428407066703377==-- From xen-api-bounces@lists.xen.org Tue Jan 15 00:18:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 00:18:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TuuEA-0007Bq-3v; Tue, 15 Jan 2013 00:18:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TuuE8-0007Bl-IQ for xen-api@lists.xen.org; Tue, 15 Jan 2013 00:18:04 +0000 Received: from [85.158.143.99:3093] by server-1.bemta-4.messagelabs.com id 96/06-18740-B30A4F05; Tue, 15 Jan 2013 00:18:03 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1358209082!27579795!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9922 invoked from network); 15 Jan 2013 00:18:02 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 00:18:02 -0000 Received: by mail-wi0-f174.google.com with SMTP id hq4so1772778wib.1 for ; Mon, 14 Jan 2013 16:18:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=S+qADfwFsHQryERJVUVc5O1Jpk/TDjYqDkc4dE5gHcM=; b=Ph2x0jvIOoaY69VFhimCGClHv+HI9dXyckP3dNHD4FzbOPx+LdkVj9D83y2rLf37Nt gy0LZTWu53gZS/4KUaAKKJUFGs64AY1jyYWuooPAjwXxceqok4Q4L9YROEKsC6x8Odol /z8N66PY8PAKsYUcNsCQi7HluOVXxfiWlv4x11s6OD2qZHmZwaLNl3hVs9Z6TBi5ZPAt +uE/Slkyr0U8959u8c+AmoG06dWqT+fRarbJSLYttJJyploctRPOA+ZMKEy/s93psNwl pVF1rv+kuVpCmPMdELOKZEqh6vbCLGCOmf1aeq7LCnH7mg5R3qApCpk/ovv2qZc4Yj0O 1JhA== X-Received: by 10.180.82.170 with SMTP id j10mr507244wiy.2.1358209082263; Mon, 14 Jan 2013 16:18:02 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id bz12sm1211241wib.5.2013.01.14.16.18.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 16:18:01 -0800 (PST) Message-ID: <50F4A038.5020201@gmail.com> Date: Tue, 15 Jan 2013 04:18:00 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] Guest Utilities X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6824442655461026478==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============6824442655461026478== Content-Type: multipart/alternative; boundary="------------070304020405070505030603" This is a multi-part message in MIME format. --------------070304020405070505030603 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit If you running PV virtual machine, guest tools is simple formality. All 'guest tools' is consisted from few shell scripts, running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??), it should able to use PV drivers anyway (... I think so, never had that experience). In short: all modern linuxes should ran on XCP without guest tools without any performance issues. On 15.01.2013 03:54, Alex Bailey wrote: > Trying to install guest utilities into a Linux VM, Ubuntu 12.04.1, > installing from template provided by the default installation of XCP > 1.6.1 > > Did not modify the template settings in any way, there is no way for > me to even access the linux directory in the XS-tools.iso on the domU > VM... I can see all the windows executables, and I see the linux > directory folder, but I cannot access it, it "does not exist" > > I followed several guides I could find online for xenserver 6.1, > including the VM guide and several blog posts (all which were just > mirrors of the guide), I am using XCP 1.6.1 as dom0, > > I do not require ubuntu, I simply am looking to create a locally > optimized VM that will act as a host... > > Is there any documentation on the process of installing > guest-utilities on a domU? What it does to the domU, and how long it > takes? > > I am just noticed that my XS-tools, is infact performing some tasks on > the VM, I am going to let it be, as it is working extremely slowly, > for it has been nearly an hour. How long does this process generally > take? and is this what is suppose to show for domU guest optimization? > It is running on a server I am aiming to be optimized for I/O, I just > recently built it, it has 128gigs of ram in 16 slots with two CPU's at > 3000ghz and 32 cores, should it take this long? Am I encountering a > serious error? > > here is output: > [1070.102324] Buffer I/O error on device xvdd, logical block 0 > [ 1191.332291] end_request: I/O error, dev xvdd, sector 0 > [ 1191.332312] Buffer I/O error on device xvdd, logical block 0 > [ 1312.522333] end_request: I/O error, dev xvdd, sector 0 > [ 1312.522354] Buffer I/O error on device xvdd, logical block 0 > [ 1433.722284] end_request: I/O error, dev xvdd, sector 0 > [ 1433.722305] Buffer I/O error on device xvdd, logical block 0 > [ 1554.932313] end_request: I/O error, dev xvdd, sector 0 > [ 1554.932334] Buffer I/O error on device xvdd, logical block 0 > [ 1676.122281] end_request: I/O error, dev xvdd, sector 0 > [ 1676.122302] Buffer I/O error on device xvdd, logical block 0 > > > Thank you very much for any input, it is greatly appreciated, > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------070304020405070505030603 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit If you running PV virtual machine, guest tools is simple formality. All 'guest tools' is consisted from few shell scripts, running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??), it should able to use PV drivers anyway (... I think so, never had that experience).

In short: all modern linuxes should ran on XCP without guest tools without any performance issues.


On 15.01.2013 03:54, Alex Bailey wrote:
Trying to install guest utilities into a Linux VM, Ubuntu 12.04.1, installing from template provided by the default installation of XCP 1.6.1

Did not modify the template settings in any way, there is no way for me to even access the linux directory in the XS-tools.iso on the domU VM... I can see all the windows executables, and I see the linux directory folder, but I cannot access it, it "does not exist"

I followed several guides I could find online for xenserver 6.1, including the VM guide and several blog posts (all which were just mirrors of the guide), I am using XCP 1.6.1 as dom0,

I do not require ubuntu, I simply am looking to create a locally optimized VM that will act as a host...

Is there any documentation on the process of installing guest-utilities on a domU? What it does to the domU, and how long it takes?

I am just noticed that my XS-tools, is infact performing some tasks on the VM, I am going to let it be, as it is working extremely slowly, for it has been nearly an hour. How long does this process generally take? and is this what is suppose to show for domU guest optimization? It is running on a server I am aiming to be optimized for I/O, I just recently built it, it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cores, should it take this long? Am I encountering a serious error?

here is output:
 [1070.102324] Buffer I/O error on device xvdd, logical block 0
[ 1191.332291] end_request: I/O error, dev xvdd, sector 0
[ 1191.332312] Buffer I/O error on device xvdd, logical block 0
[ 1312.522333] end_request: I/O error, dev xvdd, sector 0
[ 1312.522354] Buffer I/O error on device xvdd, logical block 0
[ 1433.722284] end_request: I/O error, dev xvdd, sector 0
[ 1433.722305] Buffer I/O error on device xvdd, logical block 0
[ 1554.932313] end_request: I/O error, dev xvdd, sector 0
[ 1554.932334] Buffer I/O error on device xvdd, logical block 0
[ 1676.122281] end_request: I/O error, dev xvdd, sector 0
[ 1676.122302] Buffer I/O error on device xvdd, logical block 0


Thank you very much for any input, it is greatly appreciated, 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------070304020405070505030603-- --===============6824442655461026478== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6824442655461026478==-- From xen-api-bounces@lists.xen.org Tue Jan 15 00:18:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 00:18:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TuuEA-0007Bq-3v; Tue, 15 Jan 2013 00:18:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TuuE8-0007Bl-IQ for xen-api@lists.xen.org; Tue, 15 Jan 2013 00:18:04 +0000 Received: from [85.158.143.99:3093] by server-1.bemta-4.messagelabs.com id 96/06-18740-B30A4F05; Tue, 15 Jan 2013 00:18:03 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1358209082!27579795!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9922 invoked from network); 15 Jan 2013 00:18:02 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 00:18:02 -0000 Received: by mail-wi0-f174.google.com with SMTP id hq4so1772778wib.1 for ; Mon, 14 Jan 2013 16:18:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=S+qADfwFsHQryERJVUVc5O1Jpk/TDjYqDkc4dE5gHcM=; b=Ph2x0jvIOoaY69VFhimCGClHv+HI9dXyckP3dNHD4FzbOPx+LdkVj9D83y2rLf37Nt gy0LZTWu53gZS/4KUaAKKJUFGs64AY1jyYWuooPAjwXxceqok4Q4L9YROEKsC6x8Odol /z8N66PY8PAKsYUcNsCQi7HluOVXxfiWlv4x11s6OD2qZHmZwaLNl3hVs9Z6TBi5ZPAt +uE/Slkyr0U8959u8c+AmoG06dWqT+fRarbJSLYttJJyploctRPOA+ZMKEy/s93psNwl pVF1rv+kuVpCmPMdELOKZEqh6vbCLGCOmf1aeq7LCnH7mg5R3qApCpk/ovv2qZc4Yj0O 1JhA== X-Received: by 10.180.82.170 with SMTP id j10mr507244wiy.2.1358209082263; Mon, 14 Jan 2013 16:18:02 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id bz12sm1211241wib.5.2013.01.14.16.18.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 16:18:01 -0800 (PST) Message-ID: <50F4A038.5020201@gmail.com> Date: Tue, 15 Jan 2013 04:18:00 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] Guest Utilities X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6824442655461026478==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============6824442655461026478== Content-Type: multipart/alternative; boundary="------------070304020405070505030603" This is a multi-part message in MIME format. --------------070304020405070505030603 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit If you running PV virtual machine, guest tools is simple formality. All 'guest tools' is consisted from few shell scripts, running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??), it should able to use PV drivers anyway (... I think so, never had that experience). In short: all modern linuxes should ran on XCP without guest tools without any performance issues. On 15.01.2013 03:54, Alex Bailey wrote: > Trying to install guest utilities into a Linux VM, Ubuntu 12.04.1, > installing from template provided by the default installation of XCP > 1.6.1 > > Did not modify the template settings in any way, there is no way for > me to even access the linux directory in the XS-tools.iso on the domU > VM... I can see all the windows executables, and I see the linux > directory folder, but I cannot access it, it "does not exist" > > I followed several guides I could find online for xenserver 6.1, > including the VM guide and several blog posts (all which were just > mirrors of the guide), I am using XCP 1.6.1 as dom0, > > I do not require ubuntu, I simply am looking to create a locally > optimized VM that will act as a host... > > Is there any documentation on the process of installing > guest-utilities on a domU? What it does to the domU, and how long it > takes? > > I am just noticed that my XS-tools, is infact performing some tasks on > the VM, I am going to let it be, as it is working extremely slowly, > for it has been nearly an hour. How long does this process generally > take? and is this what is suppose to show for domU guest optimization? > It is running on a server I am aiming to be optimized for I/O, I just > recently built it, it has 128gigs of ram in 16 slots with two CPU's at > 3000ghz and 32 cores, should it take this long? Am I encountering a > serious error? > > here is output: > [1070.102324] Buffer I/O error on device xvdd, logical block 0 > [ 1191.332291] end_request: I/O error, dev xvdd, sector 0 > [ 1191.332312] Buffer I/O error on device xvdd, logical block 0 > [ 1312.522333] end_request: I/O error, dev xvdd, sector 0 > [ 1312.522354] Buffer I/O error on device xvdd, logical block 0 > [ 1433.722284] end_request: I/O error, dev xvdd, sector 0 > [ 1433.722305] Buffer I/O error on device xvdd, logical block 0 > [ 1554.932313] end_request: I/O error, dev xvdd, sector 0 > [ 1554.932334] Buffer I/O error on device xvdd, logical block 0 > [ 1676.122281] end_request: I/O error, dev xvdd, sector 0 > [ 1676.122302] Buffer I/O error on device xvdd, logical block 0 > > > Thank you very much for any input, it is greatly appreciated, > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------070304020405070505030603 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit If you running PV virtual machine, guest tools is simple formality. All 'guest tools' is consisted from few shell scripts, running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??), it should able to use PV drivers anyway (... I think so, never had that experience).

In short: all modern linuxes should ran on XCP without guest tools without any performance issues.


On 15.01.2013 03:54, Alex Bailey wrote:
Trying to install guest utilities into a Linux VM, Ubuntu 12.04.1, installing from template provided by the default installation of XCP 1.6.1

Did not modify the template settings in any way, there is no way for me to even access the linux directory in the XS-tools.iso on the domU VM... I can see all the windows executables, and I see the linux directory folder, but I cannot access it, it "does not exist"

I followed several guides I could find online for xenserver 6.1, including the VM guide and several blog posts (all which were just mirrors of the guide), I am using XCP 1.6.1 as dom0,

I do not require ubuntu, I simply am looking to create a locally optimized VM that will act as a host...

Is there any documentation on the process of installing guest-utilities on a domU? What it does to the domU, and how long it takes?

I am just noticed that my XS-tools, is infact performing some tasks on the VM, I am going to let it be, as it is working extremely slowly, for it has been nearly an hour. How long does this process generally take? and is this what is suppose to show for domU guest optimization? It is running on a server I am aiming to be optimized for I/O, I just recently built it, it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cores, should it take this long? Am I encountering a serious error?

here is output:
 [1070.102324] Buffer I/O error on device xvdd, logical block 0
[ 1191.332291] end_request: I/O error, dev xvdd, sector 0
[ 1191.332312] Buffer I/O error on device xvdd, logical block 0
[ 1312.522333] end_request: I/O error, dev xvdd, sector 0
[ 1312.522354] Buffer I/O error on device xvdd, logical block 0
[ 1433.722284] end_request: I/O error, dev xvdd, sector 0
[ 1433.722305] Buffer I/O error on device xvdd, logical block 0
[ 1554.932313] end_request: I/O error, dev xvdd, sector 0
[ 1554.932334] Buffer I/O error on device xvdd, logical block 0
[ 1676.122281] end_request: I/O error, dev xvdd, sector 0
[ 1676.122302] Buffer I/O error on device xvdd, logical block 0


Thank you very much for any input, it is greatly appreciated, 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------070304020405070505030603-- --===============6824442655461026478== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6824442655461026478==-- From xen-api-bounces@lists.xen.org Tue Jan 15 01:14:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 01:14:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tuv6V-0003nw-7y; Tue, 15 Jan 2013 01:14:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tuv6T-0003nq-IL for xen-api@lists.xen.org; Tue, 15 Jan 2013 01:14:13 +0000 Received: from [85.158.139.83:39838] by server-13.bemta-5.messagelabs.com id 19/D0-10716-46DA4F05; Tue, 15 Jan 2013 01:14:12 +0000 X-Env-Sender: bailey.alex@live.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1358212450!28129566!1 X-Originating-IP: [65.55.111.140] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_2, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10174 invoked from network); 15 Jan 2013 01:14:10 -0000 Received: from blu0-omc4-s1.blu0.hotmail.com (HELO blu0-omc4-s1.blu0.hotmail.com) (65.55.111.140) by server-10.tower-182.messagelabs.com with SMTP; 15 Jan 2013 01:14:10 -0000 Received: from BLU174-W20 ([65.55.111.136]) by blu0-omc4-s1.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Jan 2013 17:14:09 -0800 X-EIP: [6fV9WAxYJuWScBB9TDkwhbSpBVg3Hprx] X-Originating-Email: [bailey.alex@live.com] Message-ID: From: Alex Bailey To: , Date: Mon, 14 Jan 2013 20:14:09 -0500 Importance: Normal In-Reply-To: <50F4A038.5020201@gmail.com> References: , <50F4A038.5020201@gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 15 Jan 2013 01:14:09.0580 (UTC) FILETIME=[9F1C86C0:01CDF2BD] Subject: Re: [Xen-API] Guest Utilities X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8190146338147430593==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8190146338147430593== Content-Type: multipart/alternative; boundary="_448b704b-07ab-4386-8c72-42e45874efad_" --_448b704b-07ab-4386-8c72-42e45874efad_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable O I see=2C I was under the impression that it modified the guest to be more= "suitable" for the host by modifying the kernel tree and such. as foolish as this may sound=2C I am not positive on whether or not the VM = is PV or HV...=20 I mean does the guest's kernel play a role in this? should the guest not ha= ve the same kernel as the domU in order to be PV? I thought the tools would= do something along those lines... For if I installed a guest VM from the template=2C must I install=2C if it = is for example ubuntu=2C the XCP-XAPI package? or would that simply just pu= t the XCP hypervisor on-top of the ubuntu guest instead of in "unison" with= the dom0 host? I am not fully understanding it all=2C as well=2C there are xen kernels for= deb distro's and xen kernels for cent distro's=2C do these play a role? Am I installing from the wrong mediums? I am using the standard installatio= n medias for "hardware installations"=2C I of course make them as minimal a= s possible=2C but is this the wrong method of going about it? Many thanks Date: Tue=2C 15 Jan 2013 04:18:00 +0400 From: george.shuklin@gmail.com To: xen-api@lists.xen.org Subject: Re: [Xen-API] Guest Utilities =20 =20 =20 =20 If you running PV virtual machine=2C guest tools is simple formality. All 'guest tools' is consisted from few shell scripts=2C running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??)=2C it should able to use PV drivers anyway (... I think so=2C never had that experience).=20 =20 In short: all modern linuxes should ran on XCP without guest tools without any performance issues. =20 =20 On 15.01.2013 03:54=2C Alex Bailey wrote: =20 =20 =20 Trying to install guest utilities into a Linux VM=2C Ubuntu 12.04.1=2C installing from template provided by the default installation of XCP 1.6.1 =20 =20 =20 Did not modify the template settings in any way=2C there is no way for me to even access the linux directory in the XS-tools.iso on the domU VM... I can see all the windows executables=2C and I see the linux directory folder=2C but I cannot access it=2C it "does not exist" =20 =20 I followed several guides I could find online for xenserver 6.1=2C including the VM guide and several blog posts (all which were just mirrors of the guide)=2C I am using XCP 1.6.1 as dom0=2C =20 =20 =20 I do not require ubuntu=2C I simply am looking to create a locally optimized VM that will act as a host... =20 =20 Is there any documentation on the process of installing guest-utilities on a domU? What it does to the domU=2C and how long it takes? =20 =20 I am just noticed that my XS-tools=2C is infact performing some tasks on the VM=2C I am going to let it be=2C as it is working extremely slowly=2C for it has been nearly an hour. How long does this process generally take? and is this what is suppose to show for domU guest optimization? It is running on a server I am aiming to be optimized for I/O=2C I just recently built it=2C it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cores=2C should it take this long? Am I encountering a serious error? =20 =20 here is output: =20 [1070.102324] Buffer I/O error on device xvdd=2C logical block 0 [ 1191.332291] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1191.332312] Buffer I/O error on device xvdd=2C logical block 0 [ 1312.522333] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1312.522354] Buffer I/O error on device xvdd=2C logical block 0 [ 1433.722284] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1433.722305] Buffer I/O error on device xvdd=2C logical block 0 [ 1554.932313] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1554.932334] Buffer I/O error on device xvdd=2C logical block 0 [ 1676.122281] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1676.122302] Buffer I/O error on device xvdd=2C logical block 0 =20 =20 =20 =20 =20 Thank you very much for any input=2C it is greatly appreciated=2C=20 =20 =20 =20 =20 _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api =20 =20 _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api = --_448b704b-07ab-4386-8c72-42e45874efad_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
O I see=2C I was under the impression that it modified the guest to be more= "suitable" for the host by modifying the kernel tree and such.

as foolish as this may sound=2C I am not positive on whether or not= the VM is PV or HV... =3B

I mean does the gue= st's kernel play a role in this? should the guest not have the same kernel = as the domU in order to be PV? I thought the tools would do something along= those lines...

For if I installed a guest VM from= the template=2C must I install=2C if it is for example ubuntu=2C the XCP-X= API package? or would that simply just put the XCP hypervisor on-top of the= ubuntu guest instead of in "unison" with the dom0 host?

I am not fully understanding it all=2C as well=2C there are xen kern= els for deb distro's and xen kernels for cent distro's=2C do these play a r= ole?

Am I installing from the wrong mediums? I am = using the standard installation medias for "hardware installations"=2C I of= course make them as minimal as possible=2C but is this the wrong method of= going about it?

Many thanks

Date: Tue=2C 15= Jan 2013 04:18:00 +0400
From: george.shuklin@gmail.com
To: xen-api@l= ists.xen.org
Subject: Re: [Xen-API] Guest Utilities

=20 =20 =20 =20 If you running PV virtual machine=2C guest tools is simple formality. All 'guest tools' is consisted from few shell scripts=2C running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??)=2C it should able to use PV drivers anyway (... I think so=2C never had that experience).

In short: all modern linuxes should ran on XCP without guest tools without any performance issues.


On 15.01.2013 03:54=2C Alex Bailey wrote:
Trying to install guest utilities into a Linux VM=2C Ubuntu 12.04.1=2C installing from template provided by the default installation of XCP 1.6.1

Did not modify the template settings in any way=2C there is no way for me to even access the linux directory in the XS-tools.iso on the domU VM... I can see all the windows executables=2C and I see the linux directory folder=2C but I cannot access it=2C it "does not exist"

I followed several guides I could find online for xenserver 6.1=2C including the VM guide and several blog posts (all which were just mirrors of the guide)=2C I am using XCP 1.6.1 as dom0=2C

I do not require ubuntu=2C I simply am looking to create a locally optimized VM that will act as a host...

Is there any documentation on the process of installing guest-utilities on a domU? What it does to the domU=2C and how long it takes?

I am just noticed that my XS-tools=2C is infact performing some tasks on the VM=2C I am going to let it be=2C as it is working extremely slowly=2C for it has been nearly an hour. How long does this process generally take? and is this what is suppose to show for domU guest optimization? It is running on a server I am aiming to be optimized for I/O=2C I just recently built it=2C it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cores=2C should it take this long? Am I encountering a serious error?

here is output:
 =3B[1070.102324] Buffer I/O error on device xvdd=2C log= ical block 0
[ 1191.332291] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1191.332312] Buffer I/O error on device xvdd=2C logical block 0
[ 1312.522333] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1312.522354] Buffer I/O error on device xvdd=2C logical block 0
[ 1433.722284] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1433.722305] Buffer I/O error on device xvdd=2C logical block 0
[ 1554.932313] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1554.932334] Buffer I/O error on device xvdd=2C logical block 0
[ 1676.122281] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1676.122302] Buffer I/O error on device xvdd=2C logical block 0


Thank you very much for any input=2C it is greatly appreciated=2C =3B


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/ma=
ilman/listinfo/xen-api
=20
_______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
=
= --_448b704b-07ab-4386-8c72-42e45874efad_-- --===============8190146338147430593== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8190146338147430593==-- From xen-api-bounces@lists.xen.org Tue Jan 15 01:14:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 01:14:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tuv6V-0003nw-7y; Tue, 15 Jan 2013 01:14:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tuv6T-0003nq-IL for xen-api@lists.xen.org; Tue, 15 Jan 2013 01:14:13 +0000 Received: from [85.158.139.83:39838] by server-13.bemta-5.messagelabs.com id 19/D0-10716-46DA4F05; Tue, 15 Jan 2013 01:14:12 +0000 X-Env-Sender: bailey.alex@live.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1358212450!28129566!1 X-Originating-IP: [65.55.111.140] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_2, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10174 invoked from network); 15 Jan 2013 01:14:10 -0000 Received: from blu0-omc4-s1.blu0.hotmail.com (HELO blu0-omc4-s1.blu0.hotmail.com) (65.55.111.140) by server-10.tower-182.messagelabs.com with SMTP; 15 Jan 2013 01:14:10 -0000 Received: from BLU174-W20 ([65.55.111.136]) by blu0-omc4-s1.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Jan 2013 17:14:09 -0800 X-EIP: [6fV9WAxYJuWScBB9TDkwhbSpBVg3Hprx] X-Originating-Email: [bailey.alex@live.com] Message-ID: From: Alex Bailey To: , Date: Mon, 14 Jan 2013 20:14:09 -0500 Importance: Normal In-Reply-To: <50F4A038.5020201@gmail.com> References: , <50F4A038.5020201@gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 15 Jan 2013 01:14:09.0580 (UTC) FILETIME=[9F1C86C0:01CDF2BD] Subject: Re: [Xen-API] Guest Utilities X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8190146338147430593==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8190146338147430593== Content-Type: multipart/alternative; boundary="_448b704b-07ab-4386-8c72-42e45874efad_" --_448b704b-07ab-4386-8c72-42e45874efad_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable O I see=2C I was under the impression that it modified the guest to be more= "suitable" for the host by modifying the kernel tree and such. as foolish as this may sound=2C I am not positive on whether or not the VM = is PV or HV...=20 I mean does the guest's kernel play a role in this? should the guest not ha= ve the same kernel as the domU in order to be PV? I thought the tools would= do something along those lines... For if I installed a guest VM from the template=2C must I install=2C if it = is for example ubuntu=2C the XCP-XAPI package? or would that simply just pu= t the XCP hypervisor on-top of the ubuntu guest instead of in "unison" with= the dom0 host? I am not fully understanding it all=2C as well=2C there are xen kernels for= deb distro's and xen kernels for cent distro's=2C do these play a role? Am I installing from the wrong mediums? I am using the standard installatio= n medias for "hardware installations"=2C I of course make them as minimal a= s possible=2C but is this the wrong method of going about it? Many thanks Date: Tue=2C 15 Jan 2013 04:18:00 +0400 From: george.shuklin@gmail.com To: xen-api@lists.xen.org Subject: Re: [Xen-API] Guest Utilities =20 =20 =20 =20 If you running PV virtual machine=2C guest tools is simple formality. All 'guest tools' is consisted from few shell scripts=2C running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??)=2C it should able to use PV drivers anyway (... I think so=2C never had that experience).=20 =20 In short: all modern linuxes should ran on XCP without guest tools without any performance issues. =20 =20 On 15.01.2013 03:54=2C Alex Bailey wrote: =20 =20 =20 Trying to install guest utilities into a Linux VM=2C Ubuntu 12.04.1=2C installing from template provided by the default installation of XCP 1.6.1 =20 =20 =20 Did not modify the template settings in any way=2C there is no way for me to even access the linux directory in the XS-tools.iso on the domU VM... I can see all the windows executables=2C and I see the linux directory folder=2C but I cannot access it=2C it "does not exist" =20 =20 I followed several guides I could find online for xenserver 6.1=2C including the VM guide and several blog posts (all which were just mirrors of the guide)=2C I am using XCP 1.6.1 as dom0=2C =20 =20 =20 I do not require ubuntu=2C I simply am looking to create a locally optimized VM that will act as a host... =20 =20 Is there any documentation on the process of installing guest-utilities on a domU? What it does to the domU=2C and how long it takes? =20 =20 I am just noticed that my XS-tools=2C is infact performing some tasks on the VM=2C I am going to let it be=2C as it is working extremely slowly=2C for it has been nearly an hour. How long does this process generally take? and is this what is suppose to show for domU guest optimization? It is running on a server I am aiming to be optimized for I/O=2C I just recently built it=2C it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cores=2C should it take this long? Am I encountering a serious error? =20 =20 here is output: =20 [1070.102324] Buffer I/O error on device xvdd=2C logical block 0 [ 1191.332291] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1191.332312] Buffer I/O error on device xvdd=2C logical block 0 [ 1312.522333] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1312.522354] Buffer I/O error on device xvdd=2C logical block 0 [ 1433.722284] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1433.722305] Buffer I/O error on device xvdd=2C logical block 0 [ 1554.932313] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1554.932334] Buffer I/O error on device xvdd=2C logical block 0 [ 1676.122281] end_request: I/O error=2C dev xvdd=2C sector 0 [ 1676.122302] Buffer I/O error on device xvdd=2C logical block 0 =20 =20 =20 =20 =20 Thank you very much for any input=2C it is greatly appreciated=2C=20 =20 =20 =20 =20 _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api =20 =20 _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api = --_448b704b-07ab-4386-8c72-42e45874efad_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
O I see=2C I was under the impression that it modified the guest to be more= "suitable" for the host by modifying the kernel tree and such.

as foolish as this may sound=2C I am not positive on whether or not= the VM is PV or HV... =3B

I mean does the gue= st's kernel play a role in this? should the guest not have the same kernel = as the domU in order to be PV? I thought the tools would do something along= those lines...

For if I installed a guest VM from= the template=2C must I install=2C if it is for example ubuntu=2C the XCP-X= API package? or would that simply just put the XCP hypervisor on-top of the= ubuntu guest instead of in "unison" with the dom0 host?

I am not fully understanding it all=2C as well=2C there are xen kern= els for deb distro's and xen kernels for cent distro's=2C do these play a r= ole?

Am I installing from the wrong mediums? I am = using the standard installation medias for "hardware installations"=2C I of= course make them as minimal as possible=2C but is this the wrong method of= going about it?

Many thanks

Date: Tue=2C 15= Jan 2013 04:18:00 +0400
From: george.shuklin@gmail.com
To: xen-api@l= ists.xen.org
Subject: Re: [Xen-API] Guest Utilities

=20 =20 =20 =20 If you running PV virtual machine=2C guest tools is simple formality. All 'guest tools' is consisted from few shell scripts=2C running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??)=2C it should able to use PV drivers anyway (... I think so=2C never had that experience).

In short: all modern linuxes should ran on XCP without guest tools without any performance issues.


On 15.01.2013 03:54=2C Alex Bailey wrote:
Trying to install guest utilities into a Linux VM=2C Ubuntu 12.04.1=2C installing from template provided by the default installation of XCP 1.6.1

Did not modify the template settings in any way=2C there is no way for me to even access the linux directory in the XS-tools.iso on the domU VM... I can see all the windows executables=2C and I see the linux directory folder=2C but I cannot access it=2C it "does not exist"

I followed several guides I could find online for xenserver 6.1=2C including the VM guide and several blog posts (all which were just mirrors of the guide)=2C I am using XCP 1.6.1 as dom0=2C

I do not require ubuntu=2C I simply am looking to create a locally optimized VM that will act as a host...

Is there any documentation on the process of installing guest-utilities on a domU? What it does to the domU=2C and how long it takes?

I am just noticed that my XS-tools=2C is infact performing some tasks on the VM=2C I am going to let it be=2C as it is working extremely slowly=2C for it has been nearly an hour. How long does this process generally take? and is this what is suppose to show for domU guest optimization? It is running on a server I am aiming to be optimized for I/O=2C I just recently built it=2C it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cores=2C should it take this long? Am I encountering a serious error?

here is output:
 =3B[1070.102324] Buffer I/O error on device xvdd=2C log= ical block 0
[ 1191.332291] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1191.332312] Buffer I/O error on device xvdd=2C logical block 0
[ 1312.522333] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1312.522354] Buffer I/O error on device xvdd=2C logical block 0
[ 1433.722284] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1433.722305] Buffer I/O error on device xvdd=2C logical block 0
[ 1554.932313] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1554.932334] Buffer I/O error on device xvdd=2C logical block 0
[ 1676.122281] end_request: I/O error=2C dev xvdd=2C sector = 0
[ 1676.122302] Buffer I/O error on device xvdd=2C logical block 0


Thank you very much for any input=2C it is greatly appreciated=2C =3B


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/ma=
ilman/listinfo/xen-api
=20
_______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
=
= --_448b704b-07ab-4386-8c72-42e45874efad_-- --===============8190146338147430593== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8190146338147430593==-- From xen-api-bounces@lists.xen.org Tue Jan 15 07:38:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 07:38:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv16H-0001EE-Su; Tue, 15 Jan 2013 07:38:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv16G-0001E7-Ml for xen-api@lists.xen.org; Tue, 15 Jan 2013 07:38:25 +0000 Received: from [85.158.137.99:41486] by server-16.bemta-3.messagelabs.com id 31/A6-27634-F6705F05; Tue, 15 Jan 2013 07:38:23 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1358235501!11816921!1 X-Originating-IP: [209.85.214.52] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20879 invoked from network); 15 Jan 2013 07:38:21 -0000 Received: from mail-bk0-f52.google.com (HELO mail-bk0-f52.google.com) (209.85.214.52) by server-6.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 07:38:21 -0000 Received: by mail-bk0-f52.google.com with SMTP id w5so2390820bku.39 for ; Mon, 14 Jan 2013 23:38:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=D1gUjJ2TFd5SRHJ3CJ6PRjFWeMe7hnbPEchet5pTcko=; b=rwpE83t7nQvuzaQIqQJvItgOe5oo0J+S3uC263sERWRpc5x6BlGdDi/hmlOkb/O8wo 8cw8p0Metwki3nwPM5/LyV94KYvnHJx7LlUKXgSTYeSvAfgwjtQbJHAIhYQect5DFKmM 1KmgUYGmU8DnLHpNeyRdX8DtV3byiVgIEI+C1/E7A9as2wkCyeadx6PpIBvHTQdEgkO1 mx300A4ZDBD/r1B04uhkVGO7YPN7pRohf+QRB4FnYRy9MTldi9a85qhoIxwnx5iXy6VH rkhRPndZwhlL590BdcnvfjIVtwlGt2zk1pFuaJA9FUmnKro9JcARlIxogeJQw989qTx6 48zQ== X-Received: by 10.204.3.205 with SMTP id 13mr39257580bko.38.1358235501067; Mon, 14 Jan 2013 23:38:21 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:5050:5356:5b3d:cb6? ([2a00:ab00:0:fffe:5050:5356:5b3d:cb6]) by mx.google.com with ESMTPS id y11sm11679597bkw.8.2013.01.14.23.38.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 23:38:20 -0800 (PST) Message-ID: <50F5076A.5010309@gmail.com> Date: Tue, 15 Jan 2013 11:38:18 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: Alex Bailey References: , <50F4A038.5020201@gmail.com> In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Guest Utilities X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6718090776476105772==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============6718090776476105772== Content-Type: multipart/alternative; boundary="------------050505070200040803020200" This is a multi-part message in MIME format. --------------050505070200040803020200 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit xe vm-list uuid=... params=HVM-boot-policy, if not empty, HVM mode, if empty - PV mode. 15.01.2013 05:14, Alex Bailey ?????: > O I see, I was under the impression that it modified the guest to be > more "suitable" for the host by modifying the kernel tree and such. > > as foolish as this may sound, I am not positive on whether or not the > VM is PV or HV... > > I mean does the guest's kernel play a role in this? should the guest > not have the same kernel as the domU in order to be PV? I thought the > tools would do something along those lines... > > For if I installed a guest VM from the template, must I install, if it > is for example ubuntu, the XCP-XAPI package? or would that simply just > put the XCP hypervisor on-top of the ubuntu guest instead of in > "unison" with the dom0 host? > > I am not fully understanding it all, as well, there are xen kernels > for deb distro's and xen kernels for cent distro's, do these play a role? > > Am I installing from the wrong mediums? I am using the standard > installation medias for "hardware installations", I of course make > them as minimal as possible, but is this the wrong method of going > about it? > > Many thanks > > ------------------------------------------------------------------------ > Date: Tue, 15 Jan 2013 04:18:00 +0400 > From: george.shuklin@gmail.com > To: xen-api@lists.xen.org > Subject: Re: [Xen-API] Guest Utilities > > If you running PV virtual machine, guest tools is simple formality. > All 'guest tools' is consisted from few shell scripts, running in > background (with few sleeps inside) and reporting information from VM > to dom0. If you running HVM linux (why??), it should able to use PV > drivers anyway (... I think so, never had that experience). > > In short: all modern linuxes should ran on XCP without guest tools > without any performance issues. > > > On 15.01.2013 03:54, Alex Bailey wrote: > > Trying to install guest utilities into a Linux VM, Ubuntu 12.04.1, > installing from template provided by the default installation of > XCP 1.6.1 > > Did not modify the template settings in any way, there is no way > for me to even access the linux directory in the XS-tools.iso on > the domU VM... I can see all the windows executables, and I see > the linux directory folder, but I cannot access it, it "does not > exist" > > I followed several guides I could find online for xenserver 6.1, > including the VM guide and several blog posts (all which were just > mirrors of the guide), I am using XCP 1.6.1 as dom0, > > I do not require ubuntu, I simply am looking to create a locally > optimized VM that will act as a host... > > Is there any documentation on the process of installing > guest-utilities on a domU? What it does to the domU, and how long > it takes? > > I am just noticed that my XS-tools, is infact performing some > tasks on the VM, I am going to let it be, as it is working > extremely slowly, for it has been nearly an hour. How long does > this process generally take? and is this what is suppose to show > for domU guest optimization? It is running on a server I am aiming > to be optimized for I/O, I just recently built it, it has 128gigs > of ram in 16 slots with two CPU's at 3000ghz and 32 cores, should > it take this long? Am I encountering a serious error? > > here is output: > [1070.102324] Buffer I/O error on device xvdd, logical block 0 > [ 1191.332291] end_request: I/O error, dev xvdd, sector 0 > [ 1191.332312] Buffer I/O error on device xvdd, logical block 0 > [ 1312.522333] end_request: I/O error, dev xvdd, sector 0 > [ 1312.522354] Buffer I/O error on device xvdd, logical block 0 > [ 1433.722284] end_request: I/O error, dev xvdd, sector 0 > [ 1433.722305] Buffer I/O error on device xvdd, logical block 0 > [ 1554.932313] end_request: I/O error, dev xvdd, sector 0 > [ 1554.932334] Buffer I/O error on device xvdd, logical block 0 > [ 1676.122281] end_request: I/O error, dev xvdd, sector 0 > [ 1676.122302] Buffer I/O error on device xvdd, logical block 0 > > > Thank you very much for any input, it is greatly appreciated, > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > _______________________________________________ Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------050505070200040803020200 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
xe vm-list uuid=... params=HVM-boot-policy, if not empty, HVM mode, if empty - PV mode.


15.01.2013 05:14, Alex Bailey пишет:
O I see, I was under the impression that it modified the guest to be more "suitable" for the host by modifying the kernel tree and such.

as foolish as this may sound, I am not positive on whether or not the VM is PV or HV... 

I mean does the guest's kernel play a role in this? should the guest not have the same kernel as the domU in order to be PV? I thought the tools would do something along those lines...

For if I installed a guest VM from the template, must I install, if it is for example ubuntu, the XCP-XAPI package? or would that simply just put the XCP hypervisor on-top of the ubuntu guest instead of in "unison" with the dom0 host?

I am not fully understanding it all, as well, there are xen kernels for deb distro's and xen kernels for cent distro's, do these play a role?

Am I installing from the wrong mediums? I am using the standard installation medias for "hardware installations", I of course make them as minimal as possible, but is this the wrong method of going about it?

Many thanks

Date: Tue, 15 Jan 2013 04:18:00 +0400
From: george.shuklin@gmail.com
To: xen-api@lists.xen.org
Subject: Re: [Xen-API] Guest Utilities

If you running PV virtual machine, guest tools is simple formality. All 'guest tools' is consisted from few shell scripts, running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??), it should able to use PV drivers anyway (... I think so, never had that experience).

In short: all modern linuxes should ran on XCP without guest tools without any performance issues.


On 15.01.2013 03:54, Alex Bailey wrote:
Trying to install guest utilities into a Linux VM, Ubuntu 12.04.1, installing from template provided by the default installation of XCP 1.6.1

Did not modify the template settings in any way, there is no way for me to even access the linux directory in the XS-tools.iso on the domU VM... I can see all the windows executables, and I see the linux directory folder, but I cannot access it, it "does not exist"

I followed several guides I could find online for xenserver 6.1, including the VM guide and several blog posts (all which were just mirrors of the guide), I am using XCP 1.6.1 as dom0,

I do not require ubuntu, I simply am looking to create a locally optimized VM that will act as a host...

Is there any documentation on the process of installing guest-utilities on a domU? What it does to the domU, and how long it takes?

I am just noticed that my XS-tools, is infact performing some tasks on the VM, I am going to let it be, as it is working extremely slowly, for it has been nearly an hour. How long does this process generally take? and is this what is suppose to show for domU guest optimization? It is running on a server I am aiming to be optimized for I/O, I just recently built it, it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cores, should it take this long? Am I encountering a serious error?

here is output:
 [1070.102324] Buffer I/O error on device xvdd, logical block 0
[ 1191.332291] end_request: I/O error, dev xvdd, sector 0
[ 1191.332312] Buffer I/O error on device xvdd, logical block 0
[ 1312.522333] end_request: I/O error, dev xvdd, sector 0
[ 1312.522354] Buffer I/O error on device xvdd, logical block 0
[ 1433.722284] end_request: I/O error, dev xvdd, sector 0
[ 1433.722305] Buffer I/O error on device xvdd, logical block 0
[ 1554.932313] end_request: I/O error, dev xvdd, sector 0
[ 1554.932334] Buffer I/O error on device xvdd, logical block 0
[ 1676.122281] end_request: I/O error, dev xvdd, sector 0
[ 1676.122302] Buffer I/O error on device xvdd, logical block 0


Thank you very much for any input, it is greatly appreciated, 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------050505070200040803020200-- --===============6718090776476105772== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6718090776476105772==-- From xen-api-bounces@lists.xen.org Tue Jan 15 07:38:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 07:38:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv16H-0001EE-Su; Tue, 15 Jan 2013 07:38:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv16G-0001E7-Ml for xen-api@lists.xen.org; Tue, 15 Jan 2013 07:38:25 +0000 Received: from [85.158.137.99:41486] by server-16.bemta-3.messagelabs.com id 31/A6-27634-F6705F05; Tue, 15 Jan 2013 07:38:23 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1358235501!11816921!1 X-Originating-IP: [209.85.214.52] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20879 invoked from network); 15 Jan 2013 07:38:21 -0000 Received: from mail-bk0-f52.google.com (HELO mail-bk0-f52.google.com) (209.85.214.52) by server-6.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 07:38:21 -0000 Received: by mail-bk0-f52.google.com with SMTP id w5so2390820bku.39 for ; Mon, 14 Jan 2013 23:38:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=D1gUjJ2TFd5SRHJ3CJ6PRjFWeMe7hnbPEchet5pTcko=; b=rwpE83t7nQvuzaQIqQJvItgOe5oo0J+S3uC263sERWRpc5x6BlGdDi/hmlOkb/O8wo 8cw8p0Metwki3nwPM5/LyV94KYvnHJx7LlUKXgSTYeSvAfgwjtQbJHAIhYQect5DFKmM 1KmgUYGmU8DnLHpNeyRdX8DtV3byiVgIEI+C1/E7A9as2wkCyeadx6PpIBvHTQdEgkO1 mx300A4ZDBD/r1B04uhkVGO7YPN7pRohf+QRB4FnYRy9MTldi9a85qhoIxwnx5iXy6VH rkhRPndZwhlL590BdcnvfjIVtwlGt2zk1pFuaJA9FUmnKro9JcARlIxogeJQw989qTx6 48zQ== X-Received: by 10.204.3.205 with SMTP id 13mr39257580bko.38.1358235501067; Mon, 14 Jan 2013 23:38:21 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:5050:5356:5b3d:cb6? ([2a00:ab00:0:fffe:5050:5356:5b3d:cb6]) by mx.google.com with ESMTPS id y11sm11679597bkw.8.2013.01.14.23.38.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 23:38:20 -0800 (PST) Message-ID: <50F5076A.5010309@gmail.com> Date: Tue, 15 Jan 2013 11:38:18 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: Alex Bailey References: , <50F4A038.5020201@gmail.com> In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Guest Utilities X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6718090776476105772==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============6718090776476105772== Content-Type: multipart/alternative; boundary="------------050505070200040803020200" This is a multi-part message in MIME format. --------------050505070200040803020200 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit xe vm-list uuid=... params=HVM-boot-policy, if not empty, HVM mode, if empty - PV mode. 15.01.2013 05:14, Alex Bailey ?????: > O I see, I was under the impression that it modified the guest to be > more "suitable" for the host by modifying the kernel tree and such. > > as foolish as this may sound, I am not positive on whether or not the > VM is PV or HV... > > I mean does the guest's kernel play a role in this? should the guest > not have the same kernel as the domU in order to be PV? I thought the > tools would do something along those lines... > > For if I installed a guest VM from the template, must I install, if it > is for example ubuntu, the XCP-XAPI package? or would that simply just > put the XCP hypervisor on-top of the ubuntu guest instead of in > "unison" with the dom0 host? > > I am not fully understanding it all, as well, there are xen kernels > for deb distro's and xen kernels for cent distro's, do these play a role? > > Am I installing from the wrong mediums? I am using the standard > installation medias for "hardware installations", I of course make > them as minimal as possible, but is this the wrong method of going > about it? > > Many thanks > > ------------------------------------------------------------------------ > Date: Tue, 15 Jan 2013 04:18:00 +0400 > From: george.shuklin@gmail.com > To: xen-api@lists.xen.org > Subject: Re: [Xen-API] Guest Utilities > > If you running PV virtual machine, guest tools is simple formality. > All 'guest tools' is consisted from few shell scripts, running in > background (with few sleeps inside) and reporting information from VM > to dom0. If you running HVM linux (why??), it should able to use PV > drivers anyway (... I think so, never had that experience). > > In short: all modern linuxes should ran on XCP without guest tools > without any performance issues. > > > On 15.01.2013 03:54, Alex Bailey wrote: > > Trying to install guest utilities into a Linux VM, Ubuntu 12.04.1, > installing from template provided by the default installation of > XCP 1.6.1 > > Did not modify the template settings in any way, there is no way > for me to even access the linux directory in the XS-tools.iso on > the domU VM... I can see all the windows executables, and I see > the linux directory folder, but I cannot access it, it "does not > exist" > > I followed several guides I could find online for xenserver 6.1, > including the VM guide and several blog posts (all which were just > mirrors of the guide), I am using XCP 1.6.1 as dom0, > > I do not require ubuntu, I simply am looking to create a locally > optimized VM that will act as a host... > > Is there any documentation on the process of installing > guest-utilities on a domU? What it does to the domU, and how long > it takes? > > I am just noticed that my XS-tools, is infact performing some > tasks on the VM, I am going to let it be, as it is working > extremely slowly, for it has been nearly an hour. How long does > this process generally take? and is this what is suppose to show > for domU guest optimization? It is running on a server I am aiming > to be optimized for I/O, I just recently built it, it has 128gigs > of ram in 16 slots with two CPU's at 3000ghz and 32 cores, should > it take this long? Am I encountering a serious error? > > here is output: > [1070.102324] Buffer I/O error on device xvdd, logical block 0 > [ 1191.332291] end_request: I/O error, dev xvdd, sector 0 > [ 1191.332312] Buffer I/O error on device xvdd, logical block 0 > [ 1312.522333] end_request: I/O error, dev xvdd, sector 0 > [ 1312.522354] Buffer I/O error on device xvdd, logical block 0 > [ 1433.722284] end_request: I/O error, dev xvdd, sector 0 > [ 1433.722305] Buffer I/O error on device xvdd, logical block 0 > [ 1554.932313] end_request: I/O error, dev xvdd, sector 0 > [ 1554.932334] Buffer I/O error on device xvdd, logical block 0 > [ 1676.122281] end_request: I/O error, dev xvdd, sector 0 > [ 1676.122302] Buffer I/O error on device xvdd, logical block 0 > > > Thank you very much for any input, it is greatly appreciated, > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > _______________________________________________ Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------050505070200040803020200 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
xe vm-list uuid=... params=HVM-boot-policy, if not empty, HVM mode, if empty - PV mode.


15.01.2013 05:14, Alex Bailey пишет:
O I see, I was under the impression that it modified the guest to be more "suitable" for the host by modifying the kernel tree and such.

as foolish as this may sound, I am not positive on whether or not the VM is PV or HV... 

I mean does the guest's kernel play a role in this? should the guest not have the same kernel as the domU in order to be PV? I thought the tools would do something along those lines...

For if I installed a guest VM from the template, must I install, if it is for example ubuntu, the XCP-XAPI package? or would that simply just put the XCP hypervisor on-top of the ubuntu guest instead of in "unison" with the dom0 host?

I am not fully understanding it all, as well, there are xen kernels for deb distro's and xen kernels for cent distro's, do these play a role?

Am I installing from the wrong mediums? I am using the standard installation medias for "hardware installations", I of course make them as minimal as possible, but is this the wrong method of going about it?

Many thanks

Date: Tue, 15 Jan 2013 04:18:00 +0400
From: george.shuklin@gmail.com
To: xen-api@lists.xen.org
Subject: Re: [Xen-API] Guest Utilities

If you running PV virtual machine, guest tools is simple formality. All 'guest tools' is consisted from few shell scripts, running in background (with few sleeps inside) and reporting information from VM to dom0. If you running HVM linux (why??), it should able to use PV drivers anyway (... I think so, never had that experience).

In short: all modern linuxes should ran on XCP without guest tools without any performance issues.


On 15.01.2013 03:54, Alex Bailey wrote:
Trying to install guest utilities into a Linux VM, Ubuntu 12.04.1, installing from template provided by the default installation of XCP 1.6.1

Did not modify the template settings in any way, there is no way for me to even access the linux directory in the XS-tools.iso on the domU VM... I can see all the windows executables, and I see the linux directory folder, but I cannot access it, it "does not exist"

I followed several guides I could find online for xenserver 6.1, including the VM guide and several blog posts (all which were just mirrors of the guide), I am using XCP 1.6.1 as dom0,

I do not require ubuntu, I simply am looking to create a locally optimized VM that will act as a host...

Is there any documentation on the process of installing guest-utilities on a domU? What it does to the domU, and how long it takes?

I am just noticed that my XS-tools, is infact performing some tasks on the VM, I am going to let it be, as it is working extremely slowly, for it has been nearly an hour. How long does this process generally take? and is this what is suppose to show for domU guest optimization? It is running on a server I am aiming to be optimized for I/O, I just recently built it, it has 128gigs of ram in 16 slots with two CPU's at 3000ghz and 32 cores, should it take this long? Am I encountering a serious error?

here is output:
 [1070.102324] Buffer I/O error on device xvdd, logical block 0
[ 1191.332291] end_request: I/O error, dev xvdd, sector 0
[ 1191.332312] Buffer I/O error on device xvdd, logical block 0
[ 1312.522333] end_request: I/O error, dev xvdd, sector 0
[ 1312.522354] Buffer I/O error on device xvdd, logical block 0
[ 1433.722284] end_request: I/O error, dev xvdd, sector 0
[ 1433.722305] Buffer I/O error on device xvdd, logical block 0
[ 1554.932313] end_request: I/O error, dev xvdd, sector 0
[ 1554.932334] Buffer I/O error on device xvdd, logical block 0
[ 1676.122281] end_request: I/O error, dev xvdd, sector 0
[ 1676.122302] Buffer I/O error on device xvdd, logical block 0


Thank you very much for any input, it is greatly appreciated, 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------050505070200040803020200-- --===============6718090776476105772== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6718090776476105772==-- From xen-api-bounces@lists.xen.org Tue Jan 15 09:35:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 09:35:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv2vX-0005Oa-FY; Tue, 15 Jan 2013 09:35:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv2vW-0005OV-3u for xen-api@lists.xen.org; Tue, 15 Jan 2013 09:35:26 +0000 Received: from [85.158.138.51:17101] by server-9.bemta-3.messagelabs.com id 1E/22-11948-DD225F05; Tue, 15 Jan 2013 09:35:25 +0000 X-Env-Sender: Anatoliy.Poloz@onetelecom.od.ua X-Msg-Ref: server-4.tower-174.messagelabs.com!1358242519!27991316!1 X-Originating-IP: [91.194.72.4] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30953 invoked from network); 15 Jan 2013 09:35:19 -0000 Received: from mail.onetelecom.od.ua (HELO main.merlin.com.ua) (91.194.72.4) by server-4.tower-174.messagelabs.com with SMTP; 15 Jan 2013 09:35:19 -0000 Received: from [192.168.67.100] (unknown [192.168.67.100]) by main.merlin.com.ua (Postmaster) with ESMTP id C323F5F3C1C for ; Tue, 15 Jan 2013 11:35:18 +0200 (EET) Message-ID: <50F522CF.3000601@onetelecom.od.ua> Date: Tue, 15 Jan 2013 11:35:11 +0200 From: "Anatoliy.Poloz" User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] [xcp] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Anatoliy.Poloz@onetelecom.od.ua List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org good day xen community my xcp enveroment is BUILD_NUMBER='42052c' PRODUCT_NAME='xcp' INSTALLATION_DATE='2011-11-18 05:44:28.782878' PRODUCT_VERSION='1.0.0' I tried to import a previously saved VM with the command "#xe vm-import filename = / var/run/sr-mount/c0da11ed-72d8-1a58-aa94-127035fa28d7/infr-samba-2013-01-02_01-04-01.xva sr-uuid = c0da11ed-72d8-1a58-aa94-127035fa28d7 force=true" c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr the size of imported file 123G but failed with message "Fatal error: exception Unix.Unix_error(13, "tcsetattr", "")" and hung task uuid ( RO) : be568259-c9cd-be13-7da5-8ed2a222e898 name-label ( RO): VM import name-description ( RO): status ( RO): pending progress ( RO): 0.720 is there any chance to recover VM? -- //wbr Anatoliy Poloz _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 09:35:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 09:35:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv2vX-0005Oa-FY; Tue, 15 Jan 2013 09:35:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv2vW-0005OV-3u for xen-api@lists.xen.org; Tue, 15 Jan 2013 09:35:26 +0000 Received: from [85.158.138.51:17101] by server-9.bemta-3.messagelabs.com id 1E/22-11948-DD225F05; Tue, 15 Jan 2013 09:35:25 +0000 X-Env-Sender: Anatoliy.Poloz@onetelecom.od.ua X-Msg-Ref: server-4.tower-174.messagelabs.com!1358242519!27991316!1 X-Originating-IP: [91.194.72.4] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30953 invoked from network); 15 Jan 2013 09:35:19 -0000 Received: from mail.onetelecom.od.ua (HELO main.merlin.com.ua) (91.194.72.4) by server-4.tower-174.messagelabs.com with SMTP; 15 Jan 2013 09:35:19 -0000 Received: from [192.168.67.100] (unknown [192.168.67.100]) by main.merlin.com.ua (Postmaster) with ESMTP id C323F5F3C1C for ; Tue, 15 Jan 2013 11:35:18 +0200 (EET) Message-ID: <50F522CF.3000601@onetelecom.od.ua> Date: Tue, 15 Jan 2013 11:35:11 +0200 From: "Anatoliy.Poloz" User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] [xcp] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Anatoliy.Poloz@onetelecom.od.ua List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org good day xen community my xcp enveroment is BUILD_NUMBER='42052c' PRODUCT_NAME='xcp' INSTALLATION_DATE='2011-11-18 05:44:28.782878' PRODUCT_VERSION='1.0.0' I tried to import a previously saved VM with the command "#xe vm-import filename = / var/run/sr-mount/c0da11ed-72d8-1a58-aa94-127035fa28d7/infr-samba-2013-01-02_01-04-01.xva sr-uuid = c0da11ed-72d8-1a58-aa94-127035fa28d7 force=true" c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr the size of imported file 123G but failed with message "Fatal error: exception Unix.Unix_error(13, "tcsetattr", "")" and hung task uuid ( RO) : be568259-c9cd-be13-7da5-8ed2a222e898 name-label ( RO): VM import name-description ( RO): status ( RO): pending progress ( RO): 0.720 is there any chance to recover VM? -- //wbr Anatoliy Poloz _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 10:33:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 10:33:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv3py-0006sR-Vf; Tue, 15 Jan 2013 10:33:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv3py-0006sI-9Y; Tue, 15 Jan 2013 10:33:46 +0000 Received: from [85.158.139.83:30012] by server-3.bemta-5.messagelabs.com id 5D/D8-18231-98035F05; Tue, 15 Jan 2013 10:33:45 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1358246024!27828449!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2MTgw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5454 invoked from network); 15 Jan 2013 10:33:44 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 10:33:44 -0000 X-IronPort-AV: E=Sophos;i="4.84,473,1355097600"; d="scan'208";a="660601" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Jan 2013 10:33:44 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Tue, 15 Jan 2013 10:33:43 +0000 Message-ID: <1358246022.15691.40.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Rushikesh Jadhav <2rushikeshj@gmail.com> Date: Tue, 15 Jan 2013 10:33:42 +0000 In-Reply-To: References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> <1357896054.9456.92.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Fri, 2013-01-11 at 19:05 +0000, Rushikesh Jadhav wrote: > Its a simple Windows 2008 VM with default xs-tools PV drivers hosted > on XCP1.1 with Xen 3.4.2. It has 2 drives Local C: and iSCSI LUN D: > Local VM Disk format is lvm over iscsi and the extra disk is directly > mounted via iSCSI using iSCSI initiator within VM. Is there anything other than this one message in the logs? Have you looked into Windows own logging (event viewer et al?). If you could determine which filesystem was causing this error that might give you something to go on. The iSCSI target is the same for both C: and D:, just the method of connecting is different? Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 10:33:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 10:33:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv3py-0006sR-Vf; Tue, 15 Jan 2013 10:33:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv3py-0006sI-9Y; Tue, 15 Jan 2013 10:33:46 +0000 Received: from [85.158.139.83:30012] by server-3.bemta-5.messagelabs.com id 5D/D8-18231-98035F05; Tue, 15 Jan 2013 10:33:45 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1358246024!27828449!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2MTgw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5454 invoked from network); 15 Jan 2013 10:33:44 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 10:33:44 -0000 X-IronPort-AV: E=Sophos;i="4.84,473,1355097600"; d="scan'208";a="660601" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Jan 2013 10:33:44 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Tue, 15 Jan 2013 10:33:43 +0000 Message-ID: <1358246022.15691.40.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Rushikesh Jadhav <2rushikeshj@gmail.com> Date: Tue, 15 Jan 2013 10:33:42 +0000 In-Reply-To: References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> <1357896054.9456.92.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Fri, 2013-01-11 at 19:05 +0000, Rushikesh Jadhav wrote: > Its a simple Windows 2008 VM with default xs-tools PV drivers hosted > on XCP1.1 with Xen 3.4.2. It has 2 drives Local C: and iSCSI LUN D: > Local VM Disk format is lvm over iscsi and the extra disk is directly > mounted via iSCSI using iSCSI initiator within VM. Is there anything other than this one message in the logs? Have you looked into Windows own logging (event viewer et al?). If you could determine which filesystem was causing this error that might give you something to go on. The iSCSI target is the same for both C: and D:, just the method of connecting is different? Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 15:43:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 15:43:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv8fy-000136-Em; Tue, 15 Jan 2013 15:43:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv8fx-00012z-9Q for xen-api@lists.xen.org; Tue, 15 Jan 2013 15:43:45 +0000 Received: from [193.109.254.147:14440] by server-13.bemta-14.messagelabs.com id 5D/D4-01725-03975F05; Tue, 15 Jan 2013 15:43:44 +0000 X-Env-Sender: grantmasterflash@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1358264621!1128455!1 X-Originating-IP: [209.85.223.180] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8682 invoked from network); 15 Jan 2013 15:43:43 -0000 Received: from mail-ie0-f180.google.com (HELO mail-ie0-f180.google.com) (209.85.223.180) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 15:43:43 -0000 Received: by mail-ie0-f180.google.com with SMTP id c10so418850ieb.11 for ; Tue, 15 Jan 2013 07:43:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=oTL+HqHuL5njTXB/MHSwtNlRJ+5kbRWcaTYaXt3x1XI=; b=plXuxP7SRVl0693o3ApL5KyG92HOzFxSaJ0uTuXc+wUb5DeLrqoqQrFW9QBJO6tXmY QhAcckDoU3Jhr/oYG3ZCYuewJWDHGagmwf1SLUqJGlB0LPV59JXPa272iQEs8r8cwqNm eut2x2fBuqNJydcp1cS0yb9eM8MPim4RPSasand6MEz6gXzV6TjRgeokL6zc+i60oWky yO4KOvxwGNs9GR5MVEDmRFN5s+59AS2sql3Au6grmfSBL0koGA+aM6/vBC6EJOGFOWkn bbb6t6wLFjusRnspBt8NwKT+ScFtnyaXhut12jDXnolTO1a0kHpoAQdasHxRT4MKR5tv perA== X-Received: by 10.50.183.169 with SMTP id en9mr1999855igc.92.1358264621651; Tue, 15 Jan 2013 07:43:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.170.175 with HTTP; Tue, 15 Jan 2013 07:43:01 -0800 (PST) In-Reply-To: <50F522CF.3000601@onetelecom.od.ua> References: <50F522CF.3000601@onetelecom.od.ua> From: Grant McWilliams Date: Tue, 15 Jan 2013 07:43:01 -0800 Message-ID: To: Anatoliy.Poloz@onetelecom.od.ua Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] [xcp] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4173879057924358472==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4173879057924358472== Content-Type: multipart/alternative; boundary=14dae934129348d7b004d355a07c --14dae934129348d7b004d355a07c Content-Type: text/plain; charset=UTF-8 On Tue, Jan 15, 2013 at 1:35 AM, Anatoliy.Poloz < Anatoliy.Poloz@onetelecom.od.ua> wrote: > > good day xen community > > my xcp enveroment is > BUILD_NUMBER='42052c' > PRODUCT_NAME='xcp' > INSTALLATION_DATE='2011-11-18 05:44:28.782878' > PRODUCT_VERSION='1.0.0' > > I tried to import a previously saved VM > with the command > "#xe vm-import filename = / var/run/sr-mount/c0da11ed-** > 72d8-1a58-aa94-127035fa28d7/**infr-samba-2013-01-02_01-04-**01.xva > sr-uuid = c0da11ed-72d8-1a58-aa94-**127035fa28d7 force=true" > > c0da11ed-72d8-1a58-aa94-**127035a28d7 - ext3 local sr > > the size of imported file 123G > > but failed with message "Fatal error: exception Unix.Unix_error(13, > "tcsetattr", "")" > and hung task > uuid ( RO) : be568259-c9cd-be13-7da5-**8ed2a222e898 > name-label ( RO): VM import > name-description ( RO): > status ( RO): pending > progress ( RO): 0.720 > > is there any chance to recover VM? > > > -- > //wbr Anatoliy Poloz > > First you probably want to kill the hung task. Get a list of tasks with xe task-list Then cancel the pending task with xe task-cancel uuid= Once you've done that you can figure out what happened. If it's really talking about a Unix 13 error that's used for Permission denied so perhaps you need to investigate to make sure you have access (permissions, disk space etc...). I'd test by doing an xe vm-export of something smaller and then importing it so you can rule out whether it has to do with a very large VM or not (plus it takes less time). Grant McWilliams --14dae934129348d7b004d355a07c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jan 15, 2013 at 1:35 AM, Anatoliy.Poloz <Anatoliy.Po= loz@onetelecom.od.ua> wrote:

good day xen community

my xcp enveroment is
BUILD_NUMBER=3D'42052c'
PRODUCT_NAME=3D'xcp'
INSTALLATION_DATE=3D'2011-11-18 05:44:28.782878'
PRODUCT_VERSION=3D'1.0.0'

I tried to import a previously saved VM
with the command
"#xe vm-import filename =3D / var/run/sr-mount/c0da11ed-72d8-1a= 58-aa94-127035fa28d7/infr-samba-2013-01-02_01-04-01.xva sr-uu= id =3D c0da11ed-72d8-1a58-aa94-127035fa28d7 force=3Dtrue"

c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr

the size of imported file 123G

but failed with message "Fatal error: exception Unix.Unix_error(13, &q= uot;tcsetattr", "")"
and hung task
uuid ( RO) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: be56825= 9-c9cd-be13-7da5-8ed2a222e898
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 name-label ( RO): VM import
=C2=A0 =C2=A0 name-description ( RO):
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 status ( RO): pending
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 progress ( RO): 0.720

is there any chance to recover VM?


--
//wbr Anatoliy Poloz


First you probably want = to kill the hung task. Get a list of tasks with=C2=A0

<= div>xe task-list=C2=A0

Then cancel the pending tas= k with=C2=A0

xe task-cancel uuid=3D<task UUID>

O= nce you've done that you can figure out what happened. If it's real= ly talking about a Unix 13 error that's used for Permission denied so p= erhaps you need to investigate to make sure you have access (permissions, d= isk space etc...). I'd test by doing an xe vm-export of something small= er and then importing it so you can rule out whether it has to do with a ve= ry large VM or not (plus it takes less time).

Grant McWilliams<= /font>
=C2=A0
--14dae934129348d7b004d355a07c-- --===============4173879057924358472== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4173879057924358472==-- From xen-api-bounces@lists.xen.org Tue Jan 15 15:43:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 15:43:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv8fy-000136-Em; Tue, 15 Jan 2013 15:43:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv8fx-00012z-9Q for xen-api@lists.xen.org; Tue, 15 Jan 2013 15:43:45 +0000 Received: from [193.109.254.147:14440] by server-13.bemta-14.messagelabs.com id 5D/D4-01725-03975F05; Tue, 15 Jan 2013 15:43:44 +0000 X-Env-Sender: grantmasterflash@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1358264621!1128455!1 X-Originating-IP: [209.85.223.180] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8682 invoked from network); 15 Jan 2013 15:43:43 -0000 Received: from mail-ie0-f180.google.com (HELO mail-ie0-f180.google.com) (209.85.223.180) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 15:43:43 -0000 Received: by mail-ie0-f180.google.com with SMTP id c10so418850ieb.11 for ; Tue, 15 Jan 2013 07:43:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=oTL+HqHuL5njTXB/MHSwtNlRJ+5kbRWcaTYaXt3x1XI=; b=plXuxP7SRVl0693o3ApL5KyG92HOzFxSaJ0uTuXc+wUb5DeLrqoqQrFW9QBJO6tXmY QhAcckDoU3Jhr/oYG3ZCYuewJWDHGagmwf1SLUqJGlB0LPV59JXPa272iQEs8r8cwqNm eut2x2fBuqNJydcp1cS0yb9eM8MPim4RPSasand6MEz6gXzV6TjRgeokL6zc+i60oWky yO4KOvxwGNs9GR5MVEDmRFN5s+59AS2sql3Au6grmfSBL0koGA+aM6/vBC6EJOGFOWkn bbb6t6wLFjusRnspBt8NwKT+ScFtnyaXhut12jDXnolTO1a0kHpoAQdasHxRT4MKR5tv perA== X-Received: by 10.50.183.169 with SMTP id en9mr1999855igc.92.1358264621651; Tue, 15 Jan 2013 07:43:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.170.175 with HTTP; Tue, 15 Jan 2013 07:43:01 -0800 (PST) In-Reply-To: <50F522CF.3000601@onetelecom.od.ua> References: <50F522CF.3000601@onetelecom.od.ua> From: Grant McWilliams Date: Tue, 15 Jan 2013 07:43:01 -0800 Message-ID: To: Anatoliy.Poloz@onetelecom.od.ua Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] [xcp] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4173879057924358472==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4173879057924358472== Content-Type: multipart/alternative; boundary=14dae934129348d7b004d355a07c --14dae934129348d7b004d355a07c Content-Type: text/plain; charset=UTF-8 On Tue, Jan 15, 2013 at 1:35 AM, Anatoliy.Poloz < Anatoliy.Poloz@onetelecom.od.ua> wrote: > > good day xen community > > my xcp enveroment is > BUILD_NUMBER='42052c' > PRODUCT_NAME='xcp' > INSTALLATION_DATE='2011-11-18 05:44:28.782878' > PRODUCT_VERSION='1.0.0' > > I tried to import a previously saved VM > with the command > "#xe vm-import filename = / var/run/sr-mount/c0da11ed-** > 72d8-1a58-aa94-127035fa28d7/**infr-samba-2013-01-02_01-04-**01.xva > sr-uuid = c0da11ed-72d8-1a58-aa94-**127035fa28d7 force=true" > > c0da11ed-72d8-1a58-aa94-**127035a28d7 - ext3 local sr > > the size of imported file 123G > > but failed with message "Fatal error: exception Unix.Unix_error(13, > "tcsetattr", "")" > and hung task > uuid ( RO) : be568259-c9cd-be13-7da5-**8ed2a222e898 > name-label ( RO): VM import > name-description ( RO): > status ( RO): pending > progress ( RO): 0.720 > > is there any chance to recover VM? > > > -- > //wbr Anatoliy Poloz > > First you probably want to kill the hung task. Get a list of tasks with xe task-list Then cancel the pending task with xe task-cancel uuid= Once you've done that you can figure out what happened. If it's really talking about a Unix 13 error that's used for Permission denied so perhaps you need to investigate to make sure you have access (permissions, disk space etc...). I'd test by doing an xe vm-export of something smaller and then importing it so you can rule out whether it has to do with a very large VM or not (plus it takes less time). Grant McWilliams --14dae934129348d7b004d355a07c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jan 15, 2013 at 1:35 AM, Anatoliy.Poloz <Anatoliy.Po= loz@onetelecom.od.ua> wrote:

good day xen community

my xcp enveroment is
BUILD_NUMBER=3D'42052c'
PRODUCT_NAME=3D'xcp'
INSTALLATION_DATE=3D'2011-11-18 05:44:28.782878'
PRODUCT_VERSION=3D'1.0.0'

I tried to import a previously saved VM
with the command
"#xe vm-import filename =3D / var/run/sr-mount/c0da11ed-72d8-1a= 58-aa94-127035fa28d7/infr-samba-2013-01-02_01-04-01.xva sr-uu= id =3D c0da11ed-72d8-1a58-aa94-127035fa28d7 force=3Dtrue"

c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr

the size of imported file 123G

but failed with message "Fatal error: exception Unix.Unix_error(13, &q= uot;tcsetattr", "")"
and hung task
uuid ( RO) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: be56825= 9-c9cd-be13-7da5-8ed2a222e898
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 name-label ( RO): VM import
=C2=A0 =C2=A0 name-description ( RO):
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 status ( RO): pending
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 progress ( RO): 0.720

is there any chance to recover VM?


--
//wbr Anatoliy Poloz


First you probably want = to kill the hung task. Get a list of tasks with=C2=A0

<= div>xe task-list=C2=A0

Then cancel the pending tas= k with=C2=A0

xe task-cancel uuid=3D<task UUID>

O= nce you've done that you can figure out what happened. If it's real= ly talking about a Unix 13 error that's used for Permission denied so p= erhaps you need to investigate to make sure you have access (permissions, d= isk space etc...). I'd test by doing an xe vm-export of something small= er and then importing it so you can rule out whether it has to do with a ve= ry large VM or not (plus it takes less time).

Grant McWilliams<= /font>
=C2=A0
--14dae934129348d7b004d355a07c-- --===============4173879057924358472== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4173879057924358472==-- From xen-api-bounces@lists.xen.org Tue Jan 15 17:14:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 17:14:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvA5S-0005JB-Dd; Tue, 15 Jan 2013 17:14:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvA5Q-0005Iu-I3 for xen-api@lists.xen.org; Tue, 15 Jan 2013 17:14:08 +0000 Received: from [85.158.139.211:8762] by server-16.bemta-5.messagelabs.com id 95/39-22111-F5E85F05; Tue, 15 Jan 2013 17:14:07 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1358270045!16734688!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTY3NDI=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31350 invoked from network); 15 Jan 2013 17:14:07 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 17:14:07 -0000 X-IronPort-AV: E=Sophos;i="4.84,473,1355097600"; d="scan'208";a="3616779" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 15 Jan 2013 17:14:05 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Tue, 15 Jan 2013 12:14:05 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TvA5M-00020H-Pr; Tue, 15 Jan 2013 17:14:04 +0000 Message-ID: <50F58E5B.4070008@citrix.com> Date: Tue, 15 Jan 2013 17:14:03 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <50EF7D13.3080004@gmail.com> In-Reply-To: <50EF7D13.3080004@gmail.com> Cc: "neganov@selectel.ru" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 11/01/13 02:46, George Shuklin wrote: > Pumping up detective story: which commit from public repository is the > most near to xapi-0.2.src.rpm? ... > Verdict: commit 0a9de3b should be assumed as commit from public > available repo witch most close to the content of the source ISO for the > XCP 1.6. > I'll publish notes on all new commits from that to the head of tampa-lcm. > > PS I really hate that style 'opensource reverse-engineering'. Wow, sorry you had to go through all that effort! I would have replied to your email sooner, but I was out of the office last week. We have a strange internal system for creating "product branches" of XenServer and XCP, which basically means that every time we create a new version of XCP or XenServer, we end up copying about 20-30 individual mercurial and git repos. Some of these we end up syncing with a separate github branch. I didn't do that with the XCP 1.6 branch because I wasn't planning on doing active development in that branch. Of course, that makes it difficult for users and developers to see what actually went into XCP 1.6 "Tampa". To correct this, I've created a new branch on github, called xcp-tampa [1]. This is the branch from which I built the xapi included on the final release of XCP 1.6. If we release updates to xapi, I'll tag the appropriate commit from that branch with xcp-tampa-release, and update that branch. Mike [1] https://github.com/xen-org/xen-api/tree/xcp-tampa _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 17:14:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 17:14:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvA5S-0005JB-Dd; Tue, 15 Jan 2013 17:14:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvA5Q-0005Iu-I3 for xen-api@lists.xen.org; Tue, 15 Jan 2013 17:14:08 +0000 Received: from [85.158.139.211:8762] by server-16.bemta-5.messagelabs.com id 95/39-22111-F5E85F05; Tue, 15 Jan 2013 17:14:07 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1358270045!16734688!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTY3NDI=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31350 invoked from network); 15 Jan 2013 17:14:07 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 17:14:07 -0000 X-IronPort-AV: E=Sophos;i="4.84,473,1355097600"; d="scan'208";a="3616779" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 15 Jan 2013 17:14:05 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Tue, 15 Jan 2013 12:14:05 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TvA5M-00020H-Pr; Tue, 15 Jan 2013 17:14:04 +0000 Message-ID: <50F58E5B.4070008@citrix.com> Date: Tue, 15 Jan 2013 17:14:03 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <50EF7D13.3080004@gmail.com> In-Reply-To: <50EF7D13.3080004@gmail.com> Cc: "neganov@selectel.ru" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 11/01/13 02:46, George Shuklin wrote: > Pumping up detective story: which commit from public repository is the > most near to xapi-0.2.src.rpm? ... > Verdict: commit 0a9de3b should be assumed as commit from public > available repo witch most close to the content of the source ISO for the > XCP 1.6. > I'll publish notes on all new commits from that to the head of tampa-lcm. > > PS I really hate that style 'opensource reverse-engineering'. Wow, sorry you had to go through all that effort! I would have replied to your email sooner, but I was out of the office last week. We have a strange internal system for creating "product branches" of XenServer and XCP, which basically means that every time we create a new version of XCP or XenServer, we end up copying about 20-30 individual mercurial and git repos. Some of these we end up syncing with a separate github branch. I didn't do that with the XCP 1.6 branch because I wasn't planning on doing active development in that branch. Of course, that makes it difficult for users and developers to see what actually went into XCP 1.6 "Tampa". To correct this, I've created a new branch on github, called xcp-tampa [1]. This is the branch from which I built the xapi included on the final release of XCP 1.6. If we release updates to xapi, I'll tag the appropriate commit from that branch with xcp-tampa-release, and update that branch. Mike [1] https://github.com/xen-org/xen-api/tree/xcp-tampa _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 17:48:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 17:48:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvAcK-0006Ti-VO; Tue, 15 Jan 2013 17:48:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvAcJ-0006TT-RT for xen-api@lists.xen.org; Tue, 15 Jan 2013 17:48:08 +0000 Received: from [85.158.139.211:60883] by server-8.bemta-5.messagelabs.com id 5C/D2-13655-75695F05; Tue, 15 Jan 2013 17:48:07 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1358272084!18295392!1 X-Originating-IP: [209.85.214.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22379 invoked from network); 15 Jan 2013 17:48:05 -0000 Received: from mail-bk0-f47.google.com (HELO mail-bk0-f47.google.com) (209.85.214.47) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 17:48:05 -0000 Received: by mail-bk0-f47.google.com with SMTP id j4so239279bkw.6 for ; Tue, 15 Jan 2013 09:47:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lXWtbGqm7ZWRGS7RIu/GdRoLLIBYunZLmRFErqhZXys=; b=v/yo5xckXbieBDMiPk+X5jBW7/qnZ95dMLInks8CLqnzW54Nv98OpEDygLIVhBKjHo k0h5cRqox68EwIterQIjuI1XlDYjnP6cr8pOd8oYe9Z/q5MyaSfphoOUvuvWxRWutX2r kuQa7HqHL7brFCaWNKuMTpMI3uhBEmb9RgSJqCRztTO7YolAhxj8Fo7u0l13wlNwTJWz 6AN2EmZNXg+kaO0txSEHGWQDYaj8Jjt8tjuT15eytMwNFM7be/hjxt9WKTB/h1z6/Dhq 6YWzafZBbyI3S810hyG8+YuTQbRerU9+m/bP7B+PVgztBs+T0Aj5PrEDlYZWXt5Ngq6y 3H4A== X-Received: by 10.204.11.208 with SMTP id u16mr42270350bku.81.1358272070570; Tue, 15 Jan 2013 09:47:50 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id o7sm13561277bkv.13.2013.01.15.09.47.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 09:47:49 -0800 (PST) Message-ID: <50F59644.5050603@gmail.com> Date: Tue, 15 Jan 2013 21:47:48 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Mike McClurg References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> In-Reply-To: <50F58E5B.4070008@citrix.com> Cc: "neganov@selectel.ru" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15.01.2013 21:14, Mike McClurg wrote: > On 11/01/13 02:46, George Shuklin wrote: >> Pumping up detective story: which commit from public repository is the >> most near to xapi-0.2.src.rpm? > ... >> Verdict: commit 0a9de3b should be assumed as commit from public >> available repo witch most close to the content of the source ISO for the >> XCP 1.6. >> I'll publish notes on all new commits from that to the head of >> tampa-lcm. >> >> PS I really hate that style 'opensource reverse-engineering'. > > Wow, sorry you had to go through all that effort! I would have replied > to your email sooner, but I was out of the office last week. > > We have a strange internal system for creating "product branches" of > XenServer and XCP, which basically means that every time we create a > new version of XCP or XenServer, we end up copying about 20-30 > individual mercurial and git repos. Some of these we end up syncing > with a separate github branch. I didn't do that with the XCP 1.6 > branch because I wasn't planning on doing active development in that > branch. > > Of course, that makes it difficult for users and developers to see > what actually went into XCP 1.6 "Tampa". To correct this, I've created > a new branch on github, called xcp-tampa [1]. This is the branch from > which I built the xapi included on the final release of XCP 1.6. If we > release updates to xapi, I'll tag the appropriate commit from that > branch with xcp-tampa-release, and update that branch. > > Mike > > [1] https://github.com/xen-org/xen-api/tree/xcp-tampa > Thank you very much! Right now we facing a much more troubles with compilation. F.e. type-conv now is type_conv, something strange happens with rpclight->ocaml-rpc->rpc library and so on. If someone show way to take generic distro, some repos all around the world and make xapi rpm it whould be really gracious. Because I already spend about four days fighting with ocaml, opam and libraries to get stuff done... I still no success. I already plan set of features to implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed fields), but really ashamed I can't say our software engineers how to compile existing code. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 17:48:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 17:48:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvAcK-0006Ti-VO; Tue, 15 Jan 2013 17:48:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvAcJ-0006TT-RT for xen-api@lists.xen.org; Tue, 15 Jan 2013 17:48:08 +0000 Received: from [85.158.139.211:60883] by server-8.bemta-5.messagelabs.com id 5C/D2-13655-75695F05; Tue, 15 Jan 2013 17:48:07 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1358272084!18295392!1 X-Originating-IP: [209.85.214.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22379 invoked from network); 15 Jan 2013 17:48:05 -0000 Received: from mail-bk0-f47.google.com (HELO mail-bk0-f47.google.com) (209.85.214.47) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 17:48:05 -0000 Received: by mail-bk0-f47.google.com with SMTP id j4so239279bkw.6 for ; Tue, 15 Jan 2013 09:47:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lXWtbGqm7ZWRGS7RIu/GdRoLLIBYunZLmRFErqhZXys=; b=v/yo5xckXbieBDMiPk+X5jBW7/qnZ95dMLInks8CLqnzW54Nv98OpEDygLIVhBKjHo k0h5cRqox68EwIterQIjuI1XlDYjnP6cr8pOd8oYe9Z/q5MyaSfphoOUvuvWxRWutX2r kuQa7HqHL7brFCaWNKuMTpMI3uhBEmb9RgSJqCRztTO7YolAhxj8Fo7u0l13wlNwTJWz 6AN2EmZNXg+kaO0txSEHGWQDYaj8Jjt8tjuT15eytMwNFM7be/hjxt9WKTB/h1z6/Dhq 6YWzafZBbyI3S810hyG8+YuTQbRerU9+m/bP7B+PVgztBs+T0Aj5PrEDlYZWXt5Ngq6y 3H4A== X-Received: by 10.204.11.208 with SMTP id u16mr42270350bku.81.1358272070570; Tue, 15 Jan 2013 09:47:50 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id o7sm13561277bkv.13.2013.01.15.09.47.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 09:47:49 -0800 (PST) Message-ID: <50F59644.5050603@gmail.com> Date: Tue, 15 Jan 2013 21:47:48 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Mike McClurg References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> In-Reply-To: <50F58E5B.4070008@citrix.com> Cc: "neganov@selectel.ru" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15.01.2013 21:14, Mike McClurg wrote: > On 11/01/13 02:46, George Shuklin wrote: >> Pumping up detective story: which commit from public repository is the >> most near to xapi-0.2.src.rpm? > ... >> Verdict: commit 0a9de3b should be assumed as commit from public >> available repo witch most close to the content of the source ISO for the >> XCP 1.6. >> I'll publish notes on all new commits from that to the head of >> tampa-lcm. >> >> PS I really hate that style 'opensource reverse-engineering'. > > Wow, sorry you had to go through all that effort! I would have replied > to your email sooner, but I was out of the office last week. > > We have a strange internal system for creating "product branches" of > XenServer and XCP, which basically means that every time we create a > new version of XCP or XenServer, we end up copying about 20-30 > individual mercurial and git repos. Some of these we end up syncing > with a separate github branch. I didn't do that with the XCP 1.6 > branch because I wasn't planning on doing active development in that > branch. > > Of course, that makes it difficult for users and developers to see > what actually went into XCP 1.6 "Tampa". To correct this, I've created > a new branch on github, called xcp-tampa [1]. This is the branch from > which I built the xapi included on the final release of XCP 1.6. If we > release updates to xapi, I'll tag the appropriate commit from that > branch with xcp-tampa-release, and update that branch. > > Mike > > [1] https://github.com/xen-org/xen-api/tree/xcp-tampa > Thank you very much! Right now we facing a much more troubles with compilation. F.e. type-conv now is type_conv, something strange happens with rpclight->ocaml-rpc->rpc library and so on. If someone show way to take generic distro, some repos all around the world and make xapi rpm it whould be really gracious. Because I already spend about four days fighting with ocaml, opam and libraries to get stuff done... I still no success. I already plan set of features to implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed fields), but really ashamed I can't say our software engineers how to compile existing code. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 18:54:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 18:54:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvBeZ-0001jn-Ek; Tue, 15 Jan 2013 18:54:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvBeY-0001ji-RS for xen-api@lists.xen.org; Tue, 15 Jan 2013 18:54:31 +0000 Received: from [85.158.137.99:64202] by server-5.bemta-3.messagelabs.com id 3E/AC-04992-5E5A5F05; Tue, 15 Jan 2013 18:54:29 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1358276067!13938361!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTU3NDI=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25484 invoked from network); 15 Jan 2013 18:54:29 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 18:54:29 -0000 X-IronPort-AV: E=Sophos;i="4.84,475,1355097600"; d="scan'208";a="3837145" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 15 Jan 2013 18:54:27 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Tue, 15 Jan 2013 13:54:27 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TvBeU-0003Va-SN; Tue, 15 Jan 2013 18:54:26 +0000 Message-ID: <50F5A5E1.4060107@citrix.com> Date: Tue, 15 Jan 2013 18:54:25 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> In-Reply-To: <50F59644.5050603@gmail.com> Cc: "neganov@selectel.ru" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15/01/13 17:47, George Shuklin wrote: > Right now we facing a much more troubles with compilation. F.e. > type-conv now is type_conv, something strange happens with > rpclight->ocaml-rpc->rpc library and so on. Yes, these are known problems. We're starting to work on getting xapi to build with opam. You may want to check out Dave's wiki post on building xenopsd: http://wiki.xen.org/wiki/Building_Xenopsd > If someone show way to take generic distro, some repos all around the > world and make xapi rpm it whould be really gracious. Because I already > spend about four days fighting with ocaml, opam and libraries to get > stuff done... I still no success. I already plan set of features to > implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed > fields), but really ashamed I can't say our software engineers how to > compile existing code. Fixing this kind of stuff has been my new year's resolution, but I haven't had time to start work on it just yet. There are a bunch of other people in the office who feel the same way (especially Dave Scott, Jon Ludlam and James Bulpin), so I have a feeling things will get easier pretty soon. Are you on #xen-api on Freenode? If you've got questions about ocaml or xapi, feel free to ask them there. There are usually a few xapi devs in there during UK business hours. Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 18:54:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 18:54:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvBeZ-0001jn-Ek; Tue, 15 Jan 2013 18:54:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvBeY-0001ji-RS for xen-api@lists.xen.org; Tue, 15 Jan 2013 18:54:31 +0000 Received: from [85.158.137.99:64202] by server-5.bemta-3.messagelabs.com id 3E/AC-04992-5E5A5F05; Tue, 15 Jan 2013 18:54:29 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1358276067!13938361!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTU3NDI=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25484 invoked from network); 15 Jan 2013 18:54:29 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 18:54:29 -0000 X-IronPort-AV: E=Sophos;i="4.84,475,1355097600"; d="scan'208";a="3837145" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 15 Jan 2013 18:54:27 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Tue, 15 Jan 2013 13:54:27 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TvBeU-0003Va-SN; Tue, 15 Jan 2013 18:54:26 +0000 Message-ID: <50F5A5E1.4060107@citrix.com> Date: Tue, 15 Jan 2013 18:54:25 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> In-Reply-To: <50F59644.5050603@gmail.com> Cc: "neganov@selectel.ru" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15/01/13 17:47, George Shuklin wrote: > Right now we facing a much more troubles with compilation. F.e. > type-conv now is type_conv, something strange happens with > rpclight->ocaml-rpc->rpc library and so on. Yes, these are known problems. We're starting to work on getting xapi to build with opam. You may want to check out Dave's wiki post on building xenopsd: http://wiki.xen.org/wiki/Building_Xenopsd > If someone show way to take generic distro, some repos all around the > world and make xapi rpm it whould be really gracious. Because I already > spend about four days fighting with ocaml, opam and libraries to get > stuff done... I still no success. I already plan set of features to > implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed > fields), but really ashamed I can't say our software engineers how to > compile existing code. Fixing this kind of stuff has been my new year's resolution, but I haven't had time to start work on it just yet. There are a bunch of other people in the office who feel the same way (especially Dave Scott, Jon Ludlam and James Bulpin), so I have a feeling things will get easier pretty soon. Are you on #xen-api on Freenode? If you've got questions about ocaml or xapi, feel free to ask them there. There are usually a few xapi devs in there during UK business hours. Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 20:06:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 20:06:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvCmQ-0005Zo-D6; Tue, 15 Jan 2013 20:06:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TvCmO-0005Zg-Dv; Tue, 15 Jan 2013 20:06:40 +0000 Received: from [85.158.139.211:48854] by server-10.bemta-5.messagelabs.com id DF/C1-18175-FC6B5F05; Tue, 15 Jan 2013 20:06:39 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1358280397!18219094!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19117 invoked from network); 15 Jan 2013 20:06:38 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 20:06:38 -0000 Received: by mail-qc0-f181.google.com with SMTP id x40so342290qcp.26 for ; Tue, 15 Jan 2013 12:06:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rcH/gI2uZxBGbDU/GUwREAfg/Atc/LJgP2TDBScf2eg=; b=S6rcJ36Ky4E6loeCxGQJ1RMfQpstJIIJNFkOReVhmn0OsU4O0Wy1Gzvepo2OQLPzL2 9S2+RXQGwBPZGzaoYKLOCrqOzEKwS9bseKr1UAK0NBzT28RLC0RPe0A6Aaxc0k0XbwvH H4Re9kyS9h7MmIQcFUuttBGgvrkSM3moJyzWpMqD1b8KEEppJpqSknAOmmRVlpu4imdY Db4qD0/eWWMjK5dapSYeiZGN/5WxTItfCwCqgAmEn65iolht4AfsVkIMl9enCv4wBsTK FeKdZfjM73ENJsVTsfrT5Mpj40mCgpPZpEZKD7+vgfAtFUrSFb9CW+1nJK2+JVjSMIY7 Mqrw== MIME-Version: 1.0 Received: by 10.49.105.73 with SMTP id gk9mr91714459qeb.40.1358280397321; Tue, 15 Jan 2013 12:06:37 -0800 (PST) Received: by 10.229.17.19 with HTTP; Tue, 15 Jan 2013 12:06:36 -0800 (PST) In-Reply-To: <1358246022.15691.40.camel@zakaz.uk.xensource.com> References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> <1357896054.9456.92.camel@zakaz.uk.xensource.com> <1358246022.15691.40.camel@zakaz.uk.xensource.com> Date: Wed, 16 Jan 2013 01:36:36 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Ian Campbell Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9175267044470613715==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============9175267044470613715== Content-Type: multipart/alternative; boundary=047d7b6778949675a804d3594c44 --047d7b6778949675a804d3594c44 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 15, 2013 at 4:03 PM, Ian Campbell wrote: > On Fri, 2013-01-11 at 19:05 +0000, Rushikesh Jadhav wrote: > > > > Its a simple Windows 2008 VM with default xs-tools PV drivers hosted > > on XCP1.1 with Xen 3.4.2. It has 2 drives Local C: and iSCSI LUN D: > > Local VM Disk format is lvm over iscsi and the extra disk is directly > > mounted via iSCSI using iSCSI initiator within VM. > > Is there anything other than this one message in the logs? > > Have you looked into Windows own logging (event viewer et al?). If you > could determine which filesystem was causing this error that might give > you something to go on. > > The iSCSI target is the same for both C: and D:, just the method of > connecting is different? > > Ian. > > There is no other error besides this one. I checked windows event viewer but there was no message related to NTFS, may be it is in "Info" type and I'll probably need to search by some event ID. I'll give another try. C: is the normal VHD on xen. Its same as you boot a VM from local SR. D: is the one which uses iSCSI LUN. I hope I'm not confusing. --047d7b6778949675a804d3594c44 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Jan 15, 2013 at 4:03 PM, Ian Cam= pbell <Ian.Campbell@citrix.com> wrote:
On Fri, 2013-01-11 at 19:05 +0000, Rushikesh Jadhav wrote= :


> Its a simple Windows 2008 VM with default xs-tools PV drivers hosted > on XCP1.1 with Xen 3.4.2. It has 2 drives Local C: and iSCSI LUN D: > Local VM Disk format is lvm over iscsi and the extra disk is directly<= br> > mounted via iSCSI using iSCSI initiator within VM.

Is there anything other than this one message in the logs?

Have you looked into Windows own logging (event viewer et al?). If you
could determine which filesystem was causing this error that might give
you something to go on.

The iSCSI target is the same for both C: and D:, just the method of
connecting is different?

Ian.

There is no other error besides this one.<= br>
I checked windows event viewer but there was no message related to N= TFS, may be it is in "Info" type and I'll probably need to se= arch by some event ID. I'll give another try.

C: is the normal VHD on xen. Its same as you boot a VM from local SR.D: is the one which uses iSCSI LUN. I hope I'm not confusing.
--047d7b6778949675a804d3594c44-- --===============9175267044470613715== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============9175267044470613715==-- From xen-api-bounces@lists.xen.org Tue Jan 15 20:06:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 20:06:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvCmQ-0005Zo-D6; Tue, 15 Jan 2013 20:06:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TvCmO-0005Zg-Dv; Tue, 15 Jan 2013 20:06:40 +0000 Received: from [85.158.139.211:48854] by server-10.bemta-5.messagelabs.com id DF/C1-18175-FC6B5F05; Tue, 15 Jan 2013 20:06:39 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1358280397!18219094!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19117 invoked from network); 15 Jan 2013 20:06:38 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 20:06:38 -0000 Received: by mail-qc0-f181.google.com with SMTP id x40so342290qcp.26 for ; Tue, 15 Jan 2013 12:06:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rcH/gI2uZxBGbDU/GUwREAfg/Atc/LJgP2TDBScf2eg=; b=S6rcJ36Ky4E6loeCxGQJ1RMfQpstJIIJNFkOReVhmn0OsU4O0Wy1Gzvepo2OQLPzL2 9S2+RXQGwBPZGzaoYKLOCrqOzEKwS9bseKr1UAK0NBzT28RLC0RPe0A6Aaxc0k0XbwvH H4Re9kyS9h7MmIQcFUuttBGgvrkSM3moJyzWpMqD1b8KEEppJpqSknAOmmRVlpu4imdY Db4qD0/eWWMjK5dapSYeiZGN/5WxTItfCwCqgAmEn65iolht4AfsVkIMl9enCv4wBsTK FeKdZfjM73ENJsVTsfrT5Mpj40mCgpPZpEZKD7+vgfAtFUrSFb9CW+1nJK2+JVjSMIY7 Mqrw== MIME-Version: 1.0 Received: by 10.49.105.73 with SMTP id gk9mr91714459qeb.40.1358280397321; Tue, 15 Jan 2013 12:06:37 -0800 (PST) Received: by 10.229.17.19 with HTTP; Tue, 15 Jan 2013 12:06:36 -0800 (PST) In-Reply-To: <1358246022.15691.40.camel@zakaz.uk.xensource.com> References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> <1357896054.9456.92.camel@zakaz.uk.xensource.com> <1358246022.15691.40.camel@zakaz.uk.xensource.com> Date: Wed, 16 Jan 2013 01:36:36 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Ian Campbell Cc: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] txftrans.c:4498 -- TXF_HARD_ERROR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9175267044470613715==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============9175267044470613715== Content-Type: multipart/alternative; boundary=047d7b6778949675a804d3594c44 --047d7b6778949675a804d3594c44 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 15, 2013 at 4:03 PM, Ian Campbell wrote: > On Fri, 2013-01-11 at 19:05 +0000, Rushikesh Jadhav wrote: > > > > Its a simple Windows 2008 VM with default xs-tools PV drivers hosted > > on XCP1.1 with Xen 3.4.2. It has 2 drives Local C: and iSCSI LUN D: > > Local VM Disk format is lvm over iscsi and the extra disk is directly > > mounted via iSCSI using iSCSI initiator within VM. > > Is there anything other than this one message in the logs? > > Have you looked into Windows own logging (event viewer et al?). If you > could determine which filesystem was causing this error that might give > you something to go on. > > The iSCSI target is the same for both C: and D:, just the method of > connecting is different? > > Ian. > > There is no other error besides this one. I checked windows event viewer but there was no message related to NTFS, may be it is in "Info" type and I'll probably need to search by some event ID. I'll give another try. C: is the normal VHD on xen. Its same as you boot a VM from local SR. D: is the one which uses iSCSI LUN. I hope I'm not confusing. --047d7b6778949675a804d3594c44 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Jan 15, 2013 at 4:03 PM, Ian Cam= pbell <Ian.Campbell@citrix.com> wrote:
On Fri, 2013-01-11 at 19:05 +0000, Rushikesh Jadhav wrote= :


> Its a simple Windows 2008 VM with default xs-tools PV drivers hosted > on XCP1.1 with Xen 3.4.2. It has 2 drives Local C: and iSCSI LUN D: > Local VM Disk format is lvm over iscsi and the extra disk is directly<= br> > mounted via iSCSI using iSCSI initiator within VM.

Is there anything other than this one message in the logs?

Have you looked into Windows own logging (event viewer et al?). If you
could determine which filesystem was causing this error that might give
you something to go on.

The iSCSI target is the same for both C: and D:, just the method of
connecting is different?

Ian.

There is no other error besides this one.<= br>
I checked windows event viewer but there was no message related to N= TFS, may be it is in "Info" type and I'll probably need to se= arch by some event ID. I'll give another try.

C: is the normal VHD on xen. Its same as you boot a VM from local SR.D: is the one which uses iSCSI LUN. I hope I'm not confusing.
--047d7b6778949675a804d3594c44-- --===============9175267044470613715== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============9175267044470613715==-- From xen-api-bounces@lists.xen.org Tue Jan 15 20:27:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 20:27:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvD6n-00065x-GZ; Tue, 15 Jan 2013 20:27:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvD6l-00065p-B9 for xen-api@lists.xen.org; Tue, 15 Jan 2013 20:27:43 +0000 Received: from [85.158.137.99:61798] by server-3.bemta-3.messagelabs.com id 6E/BC-31588-EBBB5F05; Tue, 15 Jan 2013 20:27:42 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1358281661!16967627!1 X-Originating-IP: [74.125.83.52] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27522 invoked from network); 15 Jan 2013 20:27:41 -0000 Received: from mail-ee0-f52.google.com (HELO mail-ee0-f52.google.com) (74.125.83.52) by server-2.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 20:27:41 -0000 Received: by mail-ee0-f52.google.com with SMTP id b15so279302eek.39 for ; Tue, 15 Jan 2013 12:27:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ownvwjn5AvPk9uDBLjZ4XY9L6Yb9iSAAwK4zgyJmYQ0=; b=pbZ4B42nW2TvFUtS8dhJnHuBvrekGA+ZhYL9ZlYEiHcaSIWgz9TeA7dnGeH/3JSPRU qj28+lCbrTk6EfTThlkg6KNU6wO1DEbr6DR+B4ONf2tssplujsNf8P/KRNFvBLg0dB0U J8K0PPkEfMSxa4o70bJ87UprZJui+bBq4q671wG/8C58wl42Nbjh8hOppXHMipu6r3b4 rwSWvRVEfhI8ALpac5oaJGGLS1Z4prFA6xKEIzxXH3ZIu4I8JGLYC1jZDTFjb2Wnxfsh p0UWQEtdUA6c601lTt1Qcju2bSduOUP37NA34Xvmo83J9dygX6oeuJ3bx/nfYj48BWiI dM6A== X-Received: by 10.14.202.3 with SMTP id c3mr244733812eeo.4.1358281660850; Tue, 15 Jan 2013 12:27:40 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id l3sm16113110een.14.2013.01.15.12.27.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 12:27:40 -0800 (PST) Message-ID: <50F5BBBA.1030701@gmail.com> Date: Wed, 16 Jan 2013 00:27:38 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Mike McClurg References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> In-Reply-To: <50F5A5E1.4060107@citrix.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15.01.2013 22:54, Mike McClurg wrote: > On 15/01/13 17:47, George Shuklin wrote: >> Right now we facing a much more troubles with compilation. F.e. >> type-conv now is type_conv, something strange happens with >> rpclight->ocaml-rpc->rpc library and so on. > > Yes, these are known problems. We're starting to work on getting xapi > to build with opam. You may want to check out Dave's wiki post on > building xenopsd: http://wiki.xen.org/wiki/Building_Xenopsd > Ok, thank you, I think we'll start from here. >> If someone show way to take generic distro, some repos all around the >> world and make xapi rpm it whould be really gracious. Because I already >> spend about four days fighting with ocaml, opam and libraries to get >> stuff done... I still no success. I already plan set of features to >> implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed >> fields), but really ashamed I can't say our software engineers how to >> compile existing code. > > Fixing this kind of stuff has been my new year's resolution, but I > haven't had time to start work on it just yet. There are a bunch of > other people in the office who feel the same way (especially Dave > Scott, Jon Ludlam and James Bulpin), so I have a feeling things will > get easier pretty soon. > > Are you on #xen-api on Freenode? If you've got questions about ocaml > or xapi, feel free to ask them there. There are usually a few xapi > devs in there during UK business hours. Yep, I'll try tomorrow (today?). Thanks. The single big piece of XCP you not published yet is the build process. Regardless some minor/major issues with library renaming and so on, there is SOME way you build xapi rpm's for XenServer and XCP, isn't it? Because next question after successful compilation will be 'can we run that binary in product environment, even if we did not change a single line?" If code was successfully linked against some libraries there is no guarantee it linked against proper versions and will not catch some bad problems in runtime. And the main problem with opensource side of XCP is that - no way to run changes in code. This is a reason of weak community response - almost all features in new XCP/XenServer version (all features?) are from Citrix, not from crowd... We actually got resolution to dig inside and scratch our own itch (I even got ocaml guy in our staff for that), but we stuck on build part... _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 20:27:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 20:27:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvD6n-00065x-GZ; Tue, 15 Jan 2013 20:27:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvD6l-00065p-B9 for xen-api@lists.xen.org; Tue, 15 Jan 2013 20:27:43 +0000 Received: from [85.158.137.99:61798] by server-3.bemta-3.messagelabs.com id 6E/BC-31588-EBBB5F05; Tue, 15 Jan 2013 20:27:42 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1358281661!16967627!1 X-Originating-IP: [74.125.83.52] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27522 invoked from network); 15 Jan 2013 20:27:41 -0000 Received: from mail-ee0-f52.google.com (HELO mail-ee0-f52.google.com) (74.125.83.52) by server-2.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 20:27:41 -0000 Received: by mail-ee0-f52.google.com with SMTP id b15so279302eek.39 for ; Tue, 15 Jan 2013 12:27:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ownvwjn5AvPk9uDBLjZ4XY9L6Yb9iSAAwK4zgyJmYQ0=; b=pbZ4B42nW2TvFUtS8dhJnHuBvrekGA+ZhYL9ZlYEiHcaSIWgz9TeA7dnGeH/3JSPRU qj28+lCbrTk6EfTThlkg6KNU6wO1DEbr6DR+B4ONf2tssplujsNf8P/KRNFvBLg0dB0U J8K0PPkEfMSxa4o70bJ87UprZJui+bBq4q671wG/8C58wl42Nbjh8hOppXHMipu6r3b4 rwSWvRVEfhI8ALpac5oaJGGLS1Z4prFA6xKEIzxXH3ZIu4I8JGLYC1jZDTFjb2Wnxfsh p0UWQEtdUA6c601lTt1Qcju2bSduOUP37NA34Xvmo83J9dygX6oeuJ3bx/nfYj48BWiI dM6A== X-Received: by 10.14.202.3 with SMTP id c3mr244733812eeo.4.1358281660850; Tue, 15 Jan 2013 12:27:40 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id l3sm16113110een.14.2013.01.15.12.27.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 12:27:40 -0800 (PST) Message-ID: <50F5BBBA.1030701@gmail.com> Date: Wed, 16 Jan 2013 00:27:38 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Mike McClurg References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> In-Reply-To: <50F5A5E1.4060107@citrix.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15.01.2013 22:54, Mike McClurg wrote: > On 15/01/13 17:47, George Shuklin wrote: >> Right now we facing a much more troubles with compilation. F.e. >> type-conv now is type_conv, something strange happens with >> rpclight->ocaml-rpc->rpc library and so on. > > Yes, these are known problems. We're starting to work on getting xapi > to build with opam. You may want to check out Dave's wiki post on > building xenopsd: http://wiki.xen.org/wiki/Building_Xenopsd > Ok, thank you, I think we'll start from here. >> If someone show way to take generic distro, some repos all around the >> world and make xapi rpm it whould be really gracious. Because I already >> spend about four days fighting with ocaml, opam and libraries to get >> stuff done... I still no success. I already plan set of features to >> implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed >> fields), but really ashamed I can't say our software engineers how to >> compile existing code. > > Fixing this kind of stuff has been my new year's resolution, but I > haven't had time to start work on it just yet. There are a bunch of > other people in the office who feel the same way (especially Dave > Scott, Jon Ludlam and James Bulpin), so I have a feeling things will > get easier pretty soon. > > Are you on #xen-api on Freenode? If you've got questions about ocaml > or xapi, feel free to ask them there. There are usually a few xapi > devs in there during UK business hours. Yep, I'll try tomorrow (today?). Thanks. The single big piece of XCP you not published yet is the build process. Regardless some minor/major issues with library renaming and so on, there is SOME way you build xapi rpm's for XenServer and XCP, isn't it? Because next question after successful compilation will be 'can we run that binary in product environment, even if we did not change a single line?" If code was successfully linked against some libraries there is no guarantee it linked against proper versions and will not catch some bad problems in runtime. And the main problem with opensource side of XCP is that - no way to run changes in code. This is a reason of weak community response - almost all features in new XCP/XenServer version (all features?) are from Citrix, not from crowd... We actually got resolution to dig inside and scratch our own itch (I even got ocaml guy in our staff for that), but we stuck on build part... _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 15 21:01:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 21:01:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvDdT-0007OE-DN; Tue, 15 Jan 2013 21:01:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TvDdR-0007O7-Oz for xen-api@lists.xen.org; Tue, 15 Jan 2013 21:01:30 +0000 Received: from [85.158.139.211:60936] by server-14.bemta-5.messagelabs.com id A1/7C-07459-9A3C5F05; Tue, 15 Jan 2013 21:01:29 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1358283686!18314142!1 X-Originating-IP: [209.85.216.175] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32012 invoked from network); 15 Jan 2013 21:01:27 -0000 Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com) (209.85.216.175) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 21:01:27 -0000 Received: by mail-qc0-f175.google.com with SMTP id j3so383653qcs.6 for ; Tue, 15 Jan 2013 13:01:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wS51r+govMTo4G+ERNeMxDsr9vHGFxKUzua3y+vqrtw=; b=xzSVSJsn/PCu5XJNnBvOaVxr0gGB+Zr9Z4XGBtXuyu7cjh2cmNkji6nYxeK5IS9qTD cE6UtF6WzLXbz5s1Ar3MSysUyv4GXD4Yo+E5z6eYfUmRXVCp8vQ5HaYbPH6/75Pp2w3i wlSpjykqankJ4yJ7oi0E0Vwp3UF9CIJNlVz5cACwIiTPReIa+7G1mRM5VbtkitZuoWYF swgmwVNfur3ggQGRKupXfG8b5mjrxo027e83ymjd2+U17AjM31+zsn+QF4xvQsElLGuI OE/2bPx3VoMU+INYqlGIwIGoPH0x/BIwA+A33/Ji67G2zCQO7rasZ3FUMx2T0peO9NGj vYBQ== MIME-Version: 1.0 Received: by 10.224.223.17 with SMTP id ii17mr77148835qab.13.1358283685798; Tue, 15 Jan 2013 13:01:25 -0800 (PST) Received: by 10.229.17.19 with HTTP; Tue, 15 Jan 2013 13:01:25 -0800 (PST) In-Reply-To: <50F5BBBA.1030701@gmail.com> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> Date: Wed, 16 Jan 2013 02:31:25 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin , Mike McClurg Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7359640284012204779==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7359640284012204779== Content-Type: multipart/alternative; boundary=20cf3074b59898a3ea04d35a10bf --20cf3074b59898a3ea04d35a10bf Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 16, 2013 at 1:57 AM, George Shuklin wrote: > On 15.01.2013 22:54, Mike McClurg wrote: > >> On 15/01/13 17:47, George Shuklin wrote: >> >>> Right now we facing a much more troubles with compilation. F.e. >>> type-conv now is type_conv, something strange happens with >>> rpclight->ocaml-rpc->rpc library and so on. >>> >> >> Yes, these are known problems. We're starting to work on getting xapi to >> build with opam. You may want to check out Dave's wiki post on building >> xenopsd: http://wiki.xen.org/wiki/**Building_Xenopsd >> >> Ok, thank you, I think we'll start from here. > > > If someone show way to take generic distro, some repos all around the >>> world and make xapi rpm it whould be really gracious. Because I already >>> spend about four days fighting with ocaml, opam and libraries to get >>> stuff done... I still no success. I already plan set of features to >>> implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed >>> fields), but really ashamed I can't say our software engineers how to >>> compile existing code. >>> >> >> Fixing this kind of stuff has been my new year's resolution, but I >> haven't had time to start work on it just yet. There are a bunch of other >> people in the office who feel the same way (especially Dave Scott, Jon >> Ludlam and James Bulpin), so I have a feeling things will get easier pretty >> soon. >> >> Are you on #xen-api on Freenode? If you've got questions about ocaml or >> xapi, feel free to ask them there. There are usually a few xapi devs in >> there during UK business hours. >> > Yep, I'll try tomorrow (today?). Thanks. > > The single big piece of XCP you not published yet is the build process. > Regardless some minor/major issues with library renaming and so on, there > is SOME way you build xapi rpm's for XenServer and XCP, isn't it? Because > next question after successful compilation will be 'can we run that binary > in product environment, even if we did not change a single line?" If code > was successfully linked against some libraries there is no guarantee it > linked against proper versions and will not catch some bad problems in > runtime. > > And the main problem with opensource side of XCP is that - no way to run > changes in code. This is a reason of weak community response - almost all > features in new XCP/XenServer version (all features?) are from Citrix, not > from crowd... We actually got resolution to dig inside and scratch our own > itch (I even got ocaml guy in our staff for that), but we stuck on build > part... > > > To avoid the complexities of making a dev/build environment using CentOS with all the devel libraries and wrong ocaml packages, we use XCP as a development VM ( Its already a CentOS with required bin packages). You need to use rpms *only* from source.iso of XCP to setup a proper dev environment. Once that's done its not too difficult to recompile/modify XCP packages. I'm not sure about the linking which xapi binary does ( and thanks for asking it ) but I'm able to use newly built xapi rpm ( no code change ) on a production server. Mike & George, Please excuse me if its not related to subject but since you made the right xapi github branch ( very much required ) can we have the right Xen branch as well. There is tremendous difference in native Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. - Rushikesh > > > ______________________________**_________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api > --20cf3074b59898a3ea04d35a10bf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, Jan 16, 2013 at 1:57 AM, George = Shuklin <george.shuklin@gmail.com> wrote:
On 15.01.2013 22:54, Mike McClurg wrote:
On 15/01/13 17:47, George Shuklin wrote:
Right now we facing a much more troubles with compilation. F.e.
type-conv now is type_conv, something strange happens with
rpclight->ocaml-rpc->rpc library and so on.

Yes, these are known problems. We're starting to work on getting xapi t= o build with opam. You may want to check out Dave's wiki post on buildi= ng xenopsd: http://wiki.xen.org/wiki/Building_Xenopsd

Ok, thank you, I think we'll start from here.


If someone show way to take generic distro, some repos all around the
world and make xapi rpm it whould be really gracious. Because I already
spend about four days fighting with ocaml, opam and libraries to get
stuff done... I still no success. I already plan set of features to
implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed
fields), but really ashamed I can't say our software engineers how to compile existing code.

Fixing this kind of stuff has been my new year's resolution, but I have= n't had time to start work on it just yet. There are a bunch of other p= eople in the office who feel the same way (especially Dave Scott, Jon Ludla= m and James Bulpin), so I have a feeling things will get easier pretty soon= .

Are you on #xen-api on Freenode? If you've got questions about ocaml or= xapi, feel free to ask them there. There are usually a few xapi devs in th= ere during UK business hours.
Yep, I'll try tomorrow (today?). Thanks.

The single big piece of XCP you not published yet is the build process. Reg= ardless some minor/major issues with library renaming and so on, there is S= OME way you build xapi rpm's for XenServer and XCP, isn't it? Becau= se next question after successful compilation will be 'can we run that = binary in product environment, even if we did not change a single line?&quo= t; If code was successfully linked against some libraries there is no guara= ntee it linked against proper versions and will not catch some bad problems= in runtime.

And the main problem with opensource side of XCP is that - no way to run ch= anges in code. This is a reason of weak community response - almost all fea= tures in new XCP/XenServer version (all features?) are from Citrix, not fro= m crowd... We actually got resolution to dig inside and scratch our own itc= h (I even got ocaml guy in our staff for that), but we stuck on build part.= ..



To avoid the complexities of making a= dev/build environment using CentOS with all the devel libraries and wrong = ocaml packages,=A0 we use XCP as a development VM ( Its already a CentOS wi= th required bin packages). You need to use rpms *only* from source.iso of X= CP to setup a proper dev environment. Once that's done its not too diff= icult to recompile/modify XCP packages.

I'm not sure about the linking which xapi binary does ( and thanks = for asking it ) but I'm able to use newly built xapi rpm ( no code chan= ge ) on a production server.

Mike & George, Please excuse me if = its not related to subject but since you made the right xapi github branch = ( very much required ) can we have the right Xen branch as well. There is t= remendous difference in native Xen and XCP Xen and similar to Xapi the Xen = commit is nowhere.

- Rushikesh

=A0


_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--20cf3074b59898a3ea04d35a10bf-- --===============7359640284012204779== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7359640284012204779==-- From xen-api-bounces@lists.xen.org Tue Jan 15 21:01:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 15 Jan 2013 21:01:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvDdT-0007OE-DN; Tue, 15 Jan 2013 21:01:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TvDdR-0007O7-Oz for xen-api@lists.xen.org; Tue, 15 Jan 2013 21:01:30 +0000 Received: from [85.158.139.211:60936] by server-14.bemta-5.messagelabs.com id A1/7C-07459-9A3C5F05; Tue, 15 Jan 2013 21:01:29 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1358283686!18314142!1 X-Originating-IP: [209.85.216.175] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32012 invoked from network); 15 Jan 2013 21:01:27 -0000 Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com) (209.85.216.175) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2013 21:01:27 -0000 Received: by mail-qc0-f175.google.com with SMTP id j3so383653qcs.6 for ; Tue, 15 Jan 2013 13:01:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wS51r+govMTo4G+ERNeMxDsr9vHGFxKUzua3y+vqrtw=; b=xzSVSJsn/PCu5XJNnBvOaVxr0gGB+Zr9Z4XGBtXuyu7cjh2cmNkji6nYxeK5IS9qTD cE6UtF6WzLXbz5s1Ar3MSysUyv4GXD4Yo+E5z6eYfUmRXVCp8vQ5HaYbPH6/75Pp2w3i wlSpjykqankJ4yJ7oi0E0Vwp3UF9CIJNlVz5cACwIiTPReIa+7G1mRM5VbtkitZuoWYF swgmwVNfur3ggQGRKupXfG8b5mjrxo027e83ymjd2+U17AjM31+zsn+QF4xvQsElLGuI OE/2bPx3VoMU+INYqlGIwIGoPH0x/BIwA+A33/Ji67G2zCQO7rasZ3FUMx2T0peO9NGj vYBQ== MIME-Version: 1.0 Received: by 10.224.223.17 with SMTP id ii17mr77148835qab.13.1358283685798; Tue, 15 Jan 2013 13:01:25 -0800 (PST) Received: by 10.229.17.19 with HTTP; Tue, 15 Jan 2013 13:01:25 -0800 (PST) In-Reply-To: <50F5BBBA.1030701@gmail.com> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> Date: Wed, 16 Jan 2013 02:31:25 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin , Mike McClurg Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7359640284012204779==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7359640284012204779== Content-Type: multipart/alternative; boundary=20cf3074b59898a3ea04d35a10bf --20cf3074b59898a3ea04d35a10bf Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 16, 2013 at 1:57 AM, George Shuklin wrote: > On 15.01.2013 22:54, Mike McClurg wrote: > >> On 15/01/13 17:47, George Shuklin wrote: >> >>> Right now we facing a much more troubles with compilation. F.e. >>> type-conv now is type_conv, something strange happens with >>> rpclight->ocaml-rpc->rpc library and so on. >>> >> >> Yes, these are known problems. We're starting to work on getting xapi to >> build with opam. You may want to check out Dave's wiki post on building >> xenopsd: http://wiki.xen.org/wiki/**Building_Xenopsd >> >> Ok, thank you, I think we'll start from here. > > > If someone show way to take generic distro, some repos all around the >>> world and make xapi rpm it whould be really gracious. Because I already >>> spend about four days fighting with ocaml, opam and libraries to get >>> stuff done... I still no success. I already plan set of features to >>> implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed >>> fields), but really ashamed I can't say our software engineers how to >>> compile existing code. >>> >> >> Fixing this kind of stuff has been my new year's resolution, but I >> haven't had time to start work on it just yet. There are a bunch of other >> people in the office who feel the same way (especially Dave Scott, Jon >> Ludlam and James Bulpin), so I have a feeling things will get easier pretty >> soon. >> >> Are you on #xen-api on Freenode? If you've got questions about ocaml or >> xapi, feel free to ask them there. There are usually a few xapi devs in >> there during UK business hours. >> > Yep, I'll try tomorrow (today?). Thanks. > > The single big piece of XCP you not published yet is the build process. > Regardless some minor/major issues with library renaming and so on, there > is SOME way you build xapi rpm's for XenServer and XCP, isn't it? Because > next question after successful compilation will be 'can we run that binary > in product environment, even if we did not change a single line?" If code > was successfully linked against some libraries there is no guarantee it > linked against proper versions and will not catch some bad problems in > runtime. > > And the main problem with opensource side of XCP is that - no way to run > changes in code. This is a reason of weak community response - almost all > features in new XCP/XenServer version (all features?) are from Citrix, not > from crowd... We actually got resolution to dig inside and scratch our own > itch (I even got ocaml guy in our staff for that), but we stuck on build > part... > > > To avoid the complexities of making a dev/build environment using CentOS with all the devel libraries and wrong ocaml packages, we use XCP as a development VM ( Its already a CentOS with required bin packages). You need to use rpms *only* from source.iso of XCP to setup a proper dev environment. Once that's done its not too difficult to recompile/modify XCP packages. I'm not sure about the linking which xapi binary does ( and thanks for asking it ) but I'm able to use newly built xapi rpm ( no code change ) on a production server. Mike & George, Please excuse me if its not related to subject but since you made the right xapi github branch ( very much required ) can we have the right Xen branch as well. There is tremendous difference in native Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. - Rushikesh > > > ______________________________**_________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/**mailman/listinfo/xen-api > --20cf3074b59898a3ea04d35a10bf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, Jan 16, 2013 at 1:57 AM, George = Shuklin <george.shuklin@gmail.com> wrote:
On 15.01.2013 22:54, Mike McClurg wrote:
On 15/01/13 17:47, George Shuklin wrote:
Right now we facing a much more troubles with compilation. F.e.
type-conv now is type_conv, something strange happens with
rpclight->ocaml-rpc->rpc library and so on.

Yes, these are known problems. We're starting to work on getting xapi t= o build with opam. You may want to check out Dave's wiki post on buildi= ng xenopsd: http://wiki.xen.org/wiki/Building_Xenopsd

Ok, thank you, I think we'll start from here.


If someone show way to take generic distro, some repos all around the
world and make xapi rpm it whould be really gracious. Because I already
spend about four days fighting with ocaml, opam and libraries to get
stuff done... I still no success. I already plan set of features to
implement in XCP (for example, allow masks in ipv4_allowed/ipv6_allowed
fields), but really ashamed I can't say our software engineers how to compile existing code.

Fixing this kind of stuff has been my new year's resolution, but I have= n't had time to start work on it just yet. There are a bunch of other p= eople in the office who feel the same way (especially Dave Scott, Jon Ludla= m and James Bulpin), so I have a feeling things will get easier pretty soon= .

Are you on #xen-api on Freenode? If you've got questions about ocaml or= xapi, feel free to ask them there. There are usually a few xapi devs in th= ere during UK business hours.
Yep, I'll try tomorrow (today?). Thanks.

The single big piece of XCP you not published yet is the build process. Reg= ardless some minor/major issues with library renaming and so on, there is S= OME way you build xapi rpm's for XenServer and XCP, isn't it? Becau= se next question after successful compilation will be 'can we run that = binary in product environment, even if we did not change a single line?&quo= t; If code was successfully linked against some libraries there is no guara= ntee it linked against proper versions and will not catch some bad problems= in runtime.

And the main problem with opensource side of XCP is that - no way to run ch= anges in code. This is a reason of weak community response - almost all fea= tures in new XCP/XenServer version (all features?) are from Citrix, not fro= m crowd... We actually got resolution to dig inside and scratch our own itc= h (I even got ocaml guy in our staff for that), but we stuck on build part.= ..



To avoid the complexities of making a= dev/build environment using CentOS with all the devel libraries and wrong = ocaml packages,=A0 we use XCP as a development VM ( Its already a CentOS wi= th required bin packages). You need to use rpms *only* from source.iso of X= CP to setup a proper dev environment. Once that's done its not too diff= icult to recompile/modify XCP packages.

I'm not sure about the linking which xapi binary does ( and thanks = for asking it ) but I'm able to use newly built xapi rpm ( no code chan= ge ) on a production server.

Mike & George, Please excuse me if = its not related to subject but since you made the right xapi github branch = ( very much required ) can we have the right Xen branch as well. There is t= remendous difference in native Xen and XCP Xen and similar to Xapi the Xen = commit is nowhere.

- Rushikesh

=A0


_______________________________________________
Xen-api mailing list
Xen-api@lists.xe= n.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--20cf3074b59898a3ea04d35a10bf-- --===============7359640284012204779== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7359640284012204779==-- From xen-api-bounces@lists.xen.org Wed Jan 16 07:27:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 07:27:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvNPU-00065h-AP; Wed, 16 Jan 2013 07:27:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvNPS-00065c-KP for xen-api@lists.xen.org; Wed, 16 Jan 2013 07:27:42 +0000 Received: from [85.158.137.99:42353] by server-6.bemta-3.messagelabs.com id 4D/D1-09845-D6656F05; Wed, 16 Jan 2013 07:27:41 +0000 X-Env-Sender: Anatoliy.Poloz@onetelecom.od.ua X-Msg-Ref: server-6.tower-217.messagelabs.com!1358321260!11993760!1 X-Originating-IP: [91.194.72.4] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30173 invoked from network); 16 Jan 2013 07:27:40 -0000 Received: from mail.onetelecom.od.ua (HELO main.merlin.com.ua) (91.194.72.4) by server-6.tower-217.messagelabs.com with SMTP; 16 Jan 2013 07:27:40 -0000 Received: from [192.168.67.100] (unknown [192.168.67.100]) by main.merlin.com.ua (Postmaster) with ESMTP id 8E76C5F3C16 for ; Wed, 16 Jan 2013 09:27:39 +0200 (EET) Message-ID: <50F65666.1000709@onetelecom.od.ua> Date: Wed, 16 Jan 2013 09:27:34 +0200 From: "Anatoliy.Poloz" User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 CC: xen-api@lists.xen.org References: <50F522CF.3000601@onetelecom.od.ua> In-Reply-To: Subject: Re: [Xen-API] [xcp] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Anatoliy.Poloz@onetelecom.od.ua List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MTUuMDEuMjAxMyAxNzo0MywgR3JhbnQgTWNXaWxsaWFtcyDQv9C40YjQtdGCOgo+IE9uIFR1ZSwg SmFuIDE1LCAyMDEzIGF0IDE6MzUgQU0sIEFuYXRvbGl5LlBvbG96IAo+IDxBbmF0b2xpeS5Qb2xv ekBvbmV0ZWxlY29tLm9kLnVhIAo+IDxtYWlsdG86QW5hdG9saXkuUG9sb3pAb25ldGVsZWNvbS5v ZC51YT4+IHdyb3RlOgo+Cj4KPiAgICAgZ29vZCBkYXkgeGVuIGNvbW11bml0eQo+Cj4gICAgIG15 IHhjcCBlbnZlcm9tZW50IGlzCj4gICAgIEJVSUxEX05VTUJFUj0nNDIwNTJjJwo+ICAgICBQUk9E VUNUX05BTUU9J3hjcCcKPiAgICAgSU5TVEFMTEFUSU9OX0RBVEU9JzIwMTEtMTEtMTggMDU6NDQ6 MjguNzgyODc4Jwo+ICAgICBQUk9EVUNUX1ZFUlNJT049JzEuMC4wJwo+Cj4gICAgIEkgdHJpZWQg dG8gaW1wb3J0IGEgcHJldmlvdXNseSBzYXZlZCBWTQo+ICAgICB3aXRoIHRoZSBjb21tYW5kCj4g ICAgICIjeGUgdm0taW1wb3J0IGZpbGVuYW1lID0gLwo+ICAgICB2YXIvcnVuL3NyLW1vdW50L2Mw ZGExMWVkLTcyZDgtMWE1OC1hYTk0LTEyNzAzNWZhMjhkNy9pbmZyLXNhbWJhLTIwMTMtMDEtMDJf MDEtMDQtMDEueHZhCj4gICAgIHNyLXV1aWQgPSBjMGRhMTFlZC03MmQ4LTFhNTgtYWE5NC0xMjcw MzVmYTI4ZDcgZm9yY2U9dHJ1ZSIKPgo+ICAgICBjMGRhMTFlZC03MmQ4LTFhNTgtYWE5NC0xMjcw MzVhMjhkNyAtIGV4dDMgbG9jYWwgc3IKPgo+ICAgICB0aGUgc2l6ZSBvZiBpbXBvcnRlZCBmaWxl IDEyM0cKPgo+ICAgICBidXQgZmFpbGVkIHdpdGggbWVzc2FnZSAiRmF0YWwgZXJyb3I6IGV4Y2Vw dGlvbgo+ICAgICBVbml4LlVuaXhfZXJyb3IoMTMsICJ0Y3NldGF0dHIiLCAiIikiCj4gICAgIGFu ZCBodW5nIHRhc2sKPiAgICAgdXVpZCAoIFJPKSAgICAgICAgICAgICAgICA6IGJlNTY4MjU5LWM5 Y2QtYmUxMy03ZGE1LThlZDJhMjIyZTg5OAo+ICAgICAgICAgICAgICAgbmFtZS1sYWJlbCAoIFJP KTogVk0gaW1wb3J0Cj4gICAgICAgICBuYW1lLWRlc2NyaXB0aW9uICggUk8pOgo+ICAgICAgICAg ICAgICAgICAgIHN0YXR1cyAoIFJPKTogcGVuZGluZwo+ICAgICAgICAgICAgICAgICBwcm9ncmVz cyAoIFJPKTogMC43MjAKPgo+ICAgICBpcyB0aGVyZSBhbnkgY2hhbmNlIHRvIHJlY292ZXIgVk0/ Cj4KPgo+ICAgICAtLSAKPiAgICAgLy93YnIgQW5hdG9saXkgUG9sb3oKPgo+Cj4gRmlyc3QgeW91 IHByb2JhYmx5IHdhbnQgdG8ga2lsbCB0aGUgaHVuZyB0YXNrLiBHZXQgYSBsaXN0IG9mIHRhc2tz IHdpdGgKPgo+IHhlIHRhc2stbGlzdAo+Cj4gVGhlbiBjYW5jZWwgdGhlIHBlbmRpbmcgdGFzayB3 aXRoCj4KPiB4ZSB0YXNrLWNhbmNlbCB1dWlkPTx0YXNrIFVVSUQ+Cj4KPiBPbmNlIHlvdSd2ZSBk b25lIHRoYXQgeW91IGNhbiBmaWd1cmUgb3V0IHdoYXQgaGFwcGVuZWQuIElmIGl0J3MgcmVhbGx5 IAo+IHRhbGtpbmcgYWJvdXQgYSBVbml4IDEzIGVycm9yIHRoYXQncyB1c2VkIGZvciBQZXJtaXNz aW9uIGRlbmllZCBzbyAKPiBwZXJoYXBzIHlvdSBuZWVkIHRvIGludmVzdGlnYXRlIHRvIG1ha2Ug c3VyZSB5b3UgaGF2ZSBhY2Nlc3MgCj4gKHBlcm1pc3Npb25zLCBkaXNrIHNwYWNlIGV0Yy4uLiku IEknZCB0ZXN0IGJ5IGRvaW5nIGFuIHhlIHZtLWV4cG9ydCBvZiAKPiBzb21ldGhpbmcgc21hbGxl ciBhbmQgdGhlbiBpbXBvcnRpbmcgaXQgc28geW91IGNhbiBydWxlIG91dCB3aGV0aGVyIGl0IAo+ IGhhcyB0byBkbyB3aXRoIGEgdmVyeSBsYXJnZSBWTSBvciBub3QgKHBsdXMgaXQgdGFrZXMgbGVz cyB0aW1lKS4KPgotIHNtYWxsZXIgVk0gaW1wb3J0ZWQgd2l0aG91dCBwcm9ibGVtcwotIHRoZSB0 YXNrIGlzIGRpc2FwZWFyIGFmdGVyIHNvbWUgdGltZQotIGZyZWUgc3BhY2UgaXMgYXZhbGlibGUK LSBsc29mIHNob3dpbmcKbHNvZiAyPi9kZXYvbnVsbCB8Z3JlcCA3OTI2NGM2YS01ODE4LTQ1ODYt OWFlOC1hZmYyNmM3ZDgxZDgKdGFwZGlzazIgIDMwNzI0ICAgICByb290ICAgIDR1ICAgICAgUkVH ICAgICAgICA4LDEgICAgICAgICAgICAwIDI3ODY0MyAKL3Zhci9sb2NrL3NtLzc5MjY0YzZhLTU4 MTgtNDU4Ni05YWU4LWFmZjI2YzdkODFkOC92ZGkKdGFwZGlzazIgIDMwNzI0ICAgICByb290ICAg MTN1ICAgICAgUkVHICAgICAgMjUyLDAgMjI3OTYyOTI5MTUyIDQ5MTU2IAovdmFyL3J1bi9zci1t b3VudC9jMGRhMTFlZC03MmQ4LTFhNTgtYWE5NC0xMjcwMzVmYTI4ZDcvNzkyNjRjNmEtNTgxOC00 NTg2LTlhZTgtYWZmMjZjN2Q4MWQ4LnZoZAoKd2hlcmUgNzkyNjRjNmEtNTgxOC00NTg2LTlhZTgt YWZmMjZjN2Q4MWQ4IG9uZSBvZiBWTSB2ZGkncwoKCmNhbiBpIG1hbnVhbHkgZXh0cmFjdCBkaXNr IGltYWdlcyBmcm9tIHh2YT8KCj4gR3JhbnQgTWNXaWxsaWFtcwoKCi0tIAovL3diciBBbmF0b2xp eSBQb2xvegoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Clhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Wed Jan 16 07:27:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 07:27:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvNPU-00065h-AP; Wed, 16 Jan 2013 07:27:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvNPS-00065c-KP for xen-api@lists.xen.org; Wed, 16 Jan 2013 07:27:42 +0000 Received: from [85.158.137.99:42353] by server-6.bemta-3.messagelabs.com id 4D/D1-09845-D6656F05; Wed, 16 Jan 2013 07:27:41 +0000 X-Env-Sender: Anatoliy.Poloz@onetelecom.od.ua X-Msg-Ref: server-6.tower-217.messagelabs.com!1358321260!11993760!1 X-Originating-IP: [91.194.72.4] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30173 invoked from network); 16 Jan 2013 07:27:40 -0000 Received: from mail.onetelecom.od.ua (HELO main.merlin.com.ua) (91.194.72.4) by server-6.tower-217.messagelabs.com with SMTP; 16 Jan 2013 07:27:40 -0000 Received: from [192.168.67.100] (unknown [192.168.67.100]) by main.merlin.com.ua (Postmaster) with ESMTP id 8E76C5F3C16 for ; Wed, 16 Jan 2013 09:27:39 +0200 (EET) Message-ID: <50F65666.1000709@onetelecom.od.ua> Date: Wed, 16 Jan 2013 09:27:34 +0200 From: "Anatoliy.Poloz" User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 CC: xen-api@lists.xen.org References: <50F522CF.3000601@onetelecom.od.ua> In-Reply-To: Subject: Re: [Xen-API] [xcp] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Anatoliy.Poloz@onetelecom.od.ua List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MTUuMDEuMjAxMyAxNzo0MywgR3JhbnQgTWNXaWxsaWFtcyDQv9C40YjQtdGCOgo+IE9uIFR1ZSwg SmFuIDE1LCAyMDEzIGF0IDE6MzUgQU0sIEFuYXRvbGl5LlBvbG96IAo+IDxBbmF0b2xpeS5Qb2xv ekBvbmV0ZWxlY29tLm9kLnVhIAo+IDxtYWlsdG86QW5hdG9saXkuUG9sb3pAb25ldGVsZWNvbS5v ZC51YT4+IHdyb3RlOgo+Cj4KPiAgICAgZ29vZCBkYXkgeGVuIGNvbW11bml0eQo+Cj4gICAgIG15 IHhjcCBlbnZlcm9tZW50IGlzCj4gICAgIEJVSUxEX05VTUJFUj0nNDIwNTJjJwo+ICAgICBQUk9E VUNUX05BTUU9J3hjcCcKPiAgICAgSU5TVEFMTEFUSU9OX0RBVEU9JzIwMTEtMTEtMTggMDU6NDQ6 MjguNzgyODc4Jwo+ICAgICBQUk9EVUNUX1ZFUlNJT049JzEuMC4wJwo+Cj4gICAgIEkgdHJpZWQg dG8gaW1wb3J0IGEgcHJldmlvdXNseSBzYXZlZCBWTQo+ICAgICB3aXRoIHRoZSBjb21tYW5kCj4g ICAgICIjeGUgdm0taW1wb3J0IGZpbGVuYW1lID0gLwo+ICAgICB2YXIvcnVuL3NyLW1vdW50L2Mw ZGExMWVkLTcyZDgtMWE1OC1hYTk0LTEyNzAzNWZhMjhkNy9pbmZyLXNhbWJhLTIwMTMtMDEtMDJf MDEtMDQtMDEueHZhCj4gICAgIHNyLXV1aWQgPSBjMGRhMTFlZC03MmQ4LTFhNTgtYWE5NC0xMjcw MzVmYTI4ZDcgZm9yY2U9dHJ1ZSIKPgo+ICAgICBjMGRhMTFlZC03MmQ4LTFhNTgtYWE5NC0xMjcw MzVhMjhkNyAtIGV4dDMgbG9jYWwgc3IKPgo+ICAgICB0aGUgc2l6ZSBvZiBpbXBvcnRlZCBmaWxl IDEyM0cKPgo+ICAgICBidXQgZmFpbGVkIHdpdGggbWVzc2FnZSAiRmF0YWwgZXJyb3I6IGV4Y2Vw dGlvbgo+ICAgICBVbml4LlVuaXhfZXJyb3IoMTMsICJ0Y3NldGF0dHIiLCAiIikiCj4gICAgIGFu ZCBodW5nIHRhc2sKPiAgICAgdXVpZCAoIFJPKSAgICAgICAgICAgICAgICA6IGJlNTY4MjU5LWM5 Y2QtYmUxMy03ZGE1LThlZDJhMjIyZTg5OAo+ICAgICAgICAgICAgICAgbmFtZS1sYWJlbCAoIFJP KTogVk0gaW1wb3J0Cj4gICAgICAgICBuYW1lLWRlc2NyaXB0aW9uICggUk8pOgo+ICAgICAgICAg ICAgICAgICAgIHN0YXR1cyAoIFJPKTogcGVuZGluZwo+ICAgICAgICAgICAgICAgICBwcm9ncmVz cyAoIFJPKTogMC43MjAKPgo+ICAgICBpcyB0aGVyZSBhbnkgY2hhbmNlIHRvIHJlY292ZXIgVk0/ Cj4KPgo+ICAgICAtLSAKPiAgICAgLy93YnIgQW5hdG9saXkgUG9sb3oKPgo+Cj4gRmlyc3QgeW91 IHByb2JhYmx5IHdhbnQgdG8ga2lsbCB0aGUgaHVuZyB0YXNrLiBHZXQgYSBsaXN0IG9mIHRhc2tz IHdpdGgKPgo+IHhlIHRhc2stbGlzdAo+Cj4gVGhlbiBjYW5jZWwgdGhlIHBlbmRpbmcgdGFzayB3 aXRoCj4KPiB4ZSB0YXNrLWNhbmNlbCB1dWlkPTx0YXNrIFVVSUQ+Cj4KPiBPbmNlIHlvdSd2ZSBk b25lIHRoYXQgeW91IGNhbiBmaWd1cmUgb3V0IHdoYXQgaGFwcGVuZWQuIElmIGl0J3MgcmVhbGx5 IAo+IHRhbGtpbmcgYWJvdXQgYSBVbml4IDEzIGVycm9yIHRoYXQncyB1c2VkIGZvciBQZXJtaXNz aW9uIGRlbmllZCBzbyAKPiBwZXJoYXBzIHlvdSBuZWVkIHRvIGludmVzdGlnYXRlIHRvIG1ha2Ug c3VyZSB5b3UgaGF2ZSBhY2Nlc3MgCj4gKHBlcm1pc3Npb25zLCBkaXNrIHNwYWNlIGV0Yy4uLiku IEknZCB0ZXN0IGJ5IGRvaW5nIGFuIHhlIHZtLWV4cG9ydCBvZiAKPiBzb21ldGhpbmcgc21hbGxl ciBhbmQgdGhlbiBpbXBvcnRpbmcgaXQgc28geW91IGNhbiBydWxlIG91dCB3aGV0aGVyIGl0IAo+ IGhhcyB0byBkbyB3aXRoIGEgdmVyeSBsYXJnZSBWTSBvciBub3QgKHBsdXMgaXQgdGFrZXMgbGVz cyB0aW1lKS4KPgotIHNtYWxsZXIgVk0gaW1wb3J0ZWQgd2l0aG91dCBwcm9ibGVtcwotIHRoZSB0 YXNrIGlzIGRpc2FwZWFyIGFmdGVyIHNvbWUgdGltZQotIGZyZWUgc3BhY2UgaXMgYXZhbGlibGUK LSBsc29mIHNob3dpbmcKbHNvZiAyPi9kZXYvbnVsbCB8Z3JlcCA3OTI2NGM2YS01ODE4LTQ1ODYt OWFlOC1hZmYyNmM3ZDgxZDgKdGFwZGlzazIgIDMwNzI0ICAgICByb290ICAgIDR1ICAgICAgUkVH ICAgICAgICA4LDEgICAgICAgICAgICAwIDI3ODY0MyAKL3Zhci9sb2NrL3NtLzc5MjY0YzZhLTU4 MTgtNDU4Ni05YWU4LWFmZjI2YzdkODFkOC92ZGkKdGFwZGlzazIgIDMwNzI0ICAgICByb290ICAg MTN1ICAgICAgUkVHICAgICAgMjUyLDAgMjI3OTYyOTI5MTUyIDQ5MTU2IAovdmFyL3J1bi9zci1t b3VudC9jMGRhMTFlZC03MmQ4LTFhNTgtYWE5NC0xMjcwMzVmYTI4ZDcvNzkyNjRjNmEtNTgxOC00 NTg2LTlhZTgtYWZmMjZjN2Q4MWQ4LnZoZAoKd2hlcmUgNzkyNjRjNmEtNTgxOC00NTg2LTlhZTgt YWZmMjZjN2Q4MWQ4IG9uZSBvZiBWTSB2ZGkncwoKCmNhbiBpIG1hbnVhbHkgZXh0cmFjdCBkaXNr IGltYWdlcyBmcm9tIHh2YT8KCj4gR3JhbnQgTWNXaWxsaWFtcwoKCi0tIAovL3diciBBbmF0b2xp eSBQb2xvegoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Clhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Wed Jan 16 13:10:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 13:10:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvSlF-0007kp-8w; Wed, 16 Jan 2013 13:10:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvSlE-0007kg-K2 for xen-api@lists.xensource.com; Wed, 16 Jan 2013 13:10:32 +0000 Received: from [85.158.137.99:44452] by server-3.bemta-3.messagelabs.com id 0F/44-00848-7C6A6F05; Wed, 16 Jan 2013 13:10:31 +0000 X-Env-Sender: gcex-xen-api@m.gmane.org X-Msg-Ref: server-7.tower-217.messagelabs.com!1358341830!12396890!1 X-Originating-IP: [80.91.229.3] X-SpamReason: No, hits=2.2 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP,RCVD_NUMERIC_HELO X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26836 invoked from network); 16 Jan 2013 13:10:30 -0000 Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by server-7.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 16 Jan 2013 13:10:30 -0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TvSkT-0004FQ-LM for xen-api@lists.xensource.com; Wed, 16 Jan 2013 14:09:45 +0100 Received: from 217.24.216.199 ([217.24.216.199]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 16 Jan 2013 14:09:45 +0100 Received: from ml by 217.24.216.199 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 16 Jan 2013 14:09:45 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: xen-api@lists.xensource.com From: Markus Schuster Followup-To: gmane.comp.emulators.xen.api Date: Wed, 16 Jan 2013 14:09:12 +0100 Lines: 31 Message-ID: Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 217.24.216.199 User-Agent: KNode/4.4.8 Subject: [Xen-API] [XCP 1.6] broad-/multicast & Open vSwitch & SLB bonding -> FAIL X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everybody, I'm not sure if this is the best place to discuss this issue or if the Open vSwitch mailinglist might be better, but let's try: We have a pool of XCP 1.6 (final) hosts using Open vSwitch. Two NICs form an active/active SLB bond for network connectivity. Recently we migrated a two node Tomcat cluster to this environment and those two VMs had a very hard time beeing reachable from the outside. After investigating the problem a bit further we learned Tomcat is using multicast for cluster communication and that's where the problem started. Open vSwitch sends out the multicast frames on ALL physical interfaces belonging to the SLB bond. That causes a lot of confusion on the physical switches that XCP hosts are connected to (VM MAC addresses jumping between ports multiple times a second). After investigating that even further, I noticed the very same problem is happening not only for multicast frames, but even for normal broadcast frames (ARP, broadcast ping, ...) - luckily Linux servers don't sent that much broadcast traffic :) We spent a few hours digging in the Open vSwitch source code and it looks like there's some special handling for broad-/multicast frames - flooding them out all ports but the port it came in (classic bridge behavior) - but there seems to be no special handling for the SLB case where I'd expect to see those packets only on the active slave for the MAC/VLAN combination of the sending VM. Hope someone can help. Regards, Markus _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 13:10:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 13:10:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvSlF-0007kp-8w; Wed, 16 Jan 2013 13:10:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvSlE-0007kg-K2 for xen-api@lists.xensource.com; Wed, 16 Jan 2013 13:10:32 +0000 Received: from [85.158.137.99:44452] by server-3.bemta-3.messagelabs.com id 0F/44-00848-7C6A6F05; Wed, 16 Jan 2013 13:10:31 +0000 X-Env-Sender: gcex-xen-api@m.gmane.org X-Msg-Ref: server-7.tower-217.messagelabs.com!1358341830!12396890!1 X-Originating-IP: [80.91.229.3] X-SpamReason: No, hits=2.2 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP,RCVD_NUMERIC_HELO X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26836 invoked from network); 16 Jan 2013 13:10:30 -0000 Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by server-7.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 16 Jan 2013 13:10:30 -0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TvSkT-0004FQ-LM for xen-api@lists.xensource.com; Wed, 16 Jan 2013 14:09:45 +0100 Received: from 217.24.216.199 ([217.24.216.199]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 16 Jan 2013 14:09:45 +0100 Received: from ml by 217.24.216.199 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 16 Jan 2013 14:09:45 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: xen-api@lists.xensource.com From: Markus Schuster Followup-To: gmane.comp.emulators.xen.api Date: Wed, 16 Jan 2013 14:09:12 +0100 Lines: 31 Message-ID: Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 217.24.216.199 User-Agent: KNode/4.4.8 Subject: [Xen-API] [XCP 1.6] broad-/multicast & Open vSwitch & SLB bonding -> FAIL X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everybody, I'm not sure if this is the best place to discuss this issue or if the Open vSwitch mailinglist might be better, but let's try: We have a pool of XCP 1.6 (final) hosts using Open vSwitch. Two NICs form an active/active SLB bond for network connectivity. Recently we migrated a two node Tomcat cluster to this environment and those two VMs had a very hard time beeing reachable from the outside. After investigating the problem a bit further we learned Tomcat is using multicast for cluster communication and that's where the problem started. Open vSwitch sends out the multicast frames on ALL physical interfaces belonging to the SLB bond. That causes a lot of confusion on the physical switches that XCP hosts are connected to (VM MAC addresses jumping between ports multiple times a second). After investigating that even further, I noticed the very same problem is happening not only for multicast frames, but even for normal broadcast frames (ARP, broadcast ping, ...) - luckily Linux servers don't sent that much broadcast traffic :) We spent a few hours digging in the Open vSwitch source code and it looks like there's some special handling for broad-/multicast frames - flooding them out all ports but the port it came in (classic bridge behavior) - but there seems to be no special handling for the SLB case where I'd expect to see those packets only on the active slave for the MAC/VLAN combination of the sending VM. Hope someone can help. Regards, Markus _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 15:17:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 15:17:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvUjy-00064c-LS; Wed, 16 Jan 2013 15:17:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvUjw-00064V-MQ for xen-api@lists.xen.org; Wed, 16 Jan 2013 15:17:21 +0000 Received: from [85.158.137.99:10869] by server-13.bemta-3.messagelabs.com id F4/61-14710-F74C6F05; Wed, 16 Jan 2013 15:17:19 +0000 X-Env-Sender: grantmasterflash@gmail.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1358349401!12465240!1 X-Originating-IP: [209.85.223.171] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4250 invoked from network); 16 Jan 2013 15:16:42 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-5.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 15:16:42 -0000 Received: by mail-ie0-f171.google.com with SMTP id 17so2685162iea.30 for ; Wed, 16 Jan 2013 07:16:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=DBozWBt+EvuYtMBdhtK9l3GlVwPKMQ8HzDBumzArkxw=; b=kOOD9jUtoMvWOYvxidwxAN/pWOoMR/B/NGhJolki+WXTav/CW5XLyUNKq2Rew6raC1 gLSM+TQYCo44p9BfBVhQJ5Kf9rd1C6Qw0O81wVOUFdjahzjkB1gC4XS7Yxb2gO0Pe91z bPu0Z0FfZqCc+TnLKv4Yq7IGln03aEtpNrFrqGWTM9fzODgoRl5wXGppE/A2dPyo/Qfe aCJl5Xmqr1CrtVJZQSgFY/ptvxJvEice2sEp0Hq9AYVhiIBcIPzIa9iyFB5ntiSb77hl IG8a1Ltt08qBGl38PKfCWHFyKZYz4K04tvOck6/wzkFo4s1VGolzS5rfN1QG8QAMIw3H p4Yg== X-Received: by 10.50.151.166 with SMTP id ur6mr1013403igb.66.1358349399998; Wed, 16 Jan 2013 07:16:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.170.175 with HTTP; Wed, 16 Jan 2013 07:15:59 -0800 (PST) In-Reply-To: <50F65666.1000709@onetelecom.od.ua> References: <50F522CF.3000601@onetelecom.od.ua> <50F65666.1000709@onetelecom.od.ua> From: Grant McWilliams Date: Wed, 16 Jan 2013 07:15:59 -0800 Message-ID: To: Anatoliy.Poloz@onetelecom.od.ua Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] [xcp] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4880521121826261042==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4880521121826261042== Content-Type: multipart/alternative; boundary=e89a8f23549d77bf0e04d3695dbd --e89a8f23549d77bf0e04d3695dbd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jan 15, 2013 at 11:27 PM, Anatoliy.Poloz < Anatoliy.Poloz@onetelecom.od.ua> wrote: > 15.01.2013 17:43, Grant McWilliams =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > On Tue, Jan 15, 2013 at 1:35 AM, Anatoliy.Poloz < >> Anatoliy.Poloz@onetelecom.od.**ua > Anatoliy.Poloz@**onetelecom.od.ua >> >> wrote: >> >> >> good day xen community >> >> my xcp enveroment is >> BUILD_NUMBER=3D'42052c' >> PRODUCT_NAME=3D'xcp' >> INSTALLATION_DATE=3D'2011-11-18 05:44:28.782878' >> PRODUCT_VERSION=3D'1.0.0' >> >> I tried to import a previously saved VM >> with the command >> "#xe vm-import filename =3D / >> var/run/sr-mount/c0da11ed-**72d8-1a58-aa94-127035fa28d7/** >> infr-samba-2013-01-02_01-04-**01.xva >> sr-uuid =3D c0da11ed-72d8-1a58-aa94-**127035fa28d7 force=3Dtrue" >> >> c0da11ed-72d8-1a58-aa94-**127035a28d7 - ext3 local sr >> >> the size of imported file 123G >> >> but failed with message "Fatal error: exception >> Unix.Unix_error(13, "tcsetattr", "")" >> and hung task >> uuid ( RO) : be568259-c9cd-be13-7da5-**8ed2a222e898 >> name-label ( RO): VM import >> name-description ( RO): >> status ( RO): pending >> progress ( RO): 0.720 >> >> is there any chance to recover VM? >> >> >> -- //wbr Anatoliy Poloz >> >> >> First you probably want to kill the hung task. Get a list of tasks with >> >> xe task-list >> >> Then cancel the pending task with >> >> xe task-cancel uuid=3D >> >> Once you've done that you can figure out what happened. If it's really >> talking about a Unix 13 error that's used for Permission denied so perha= ps >> you need to investigate to make sure you have access (permissions, disk >> space etc...). I'd test by doing an xe vm-export of something smaller an= d >> then importing it so you can rule out whether it has to do with a very >> large VM or not (plus it takes less time). >> >> - smaller VM imported without problems > - the task is disapear after some time > - free space is avalible > - lsof showing > lsof 2>/dev/null |grep 79264c6a-5818-4586-9ae8-**aff26c7d81d8 > tapdisk2 30724 root 4u REG 8,1 0 278643 > /var/lock/sm/79264c6a-5818-**4586-9ae8-aff26c7d81d8/vdi > tapdisk2 30724 root 13u REG 252,0 227962929152 49156 > /var/run/sr-mount/c0da11ed-**72d8-1a58-aa94-127035fa28d7/** > 79264c6a-5818-4586-9ae8-**aff26c7d81d8.vhd > > where 79264c6a-5818-4586-9ae8-**aff26c7d81d8 one of VM vdi's > > > can i manualy extract disk images from xva? > > Grant McWilliams >> > > > -- > //wbr Anatoliy Poloz > > Where is this disk being imported from? Is it a network drive or is it stored on the local storage? Grant McWilliams http://grantmcwilliams.com/ Some people, when confronted with a problem, think "I know, I'll use Windows." Now they have two problems. --e89a8f23549d77bf0e04d3695dbd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Tue, Jan 15, 2013 at 11:27 PM, Anatoliy.P= oloz <Anatoliy.Poloz@onetelecom.od.ua> wrote:<= br>
15.01.2013 17:43, Grant McWilliams =D0=BF=D0=B8=D1=88=D0=B5=D1=82:

On Tue, Jan 15, 2013 at 1:35 AM, Anatoliy.Poloz <Anatoliy.Poloz@onetelecom.od.= ua <mailto:Anatoliy.Poloz@onetelecom.od.ua>> wrote= :


=C2=A0 =C2=A0 good day xen community

=C2=A0 =C2=A0 my xcp enveroment is
=C2=A0 =C2=A0 BUILD_NUMBER=3D'42052c'
=C2=A0 =C2=A0 PRODUCT_NAME=3D'xcp'
=C2=A0 =C2=A0 INSTALLATION_DATE=3D'2011-11-18 05:44:28.782878'
=C2=A0 =C2=A0 PRODUCT_VERSION=3D'1.0.0'

=C2=A0 =C2=A0 I tried to import a previously saved VM
=C2=A0 =C2=A0 with the command
=C2=A0 =C2=A0 "#xe vm-import filename =3D /
=C2=A0 =C2=A0 var/run/sr-mount/c0da11ed-72d8-1a58-aa94-127035fa28d7/= infr-samba-2013-01-02_01-04-01.xva
=C2=A0 =C2=A0 sr-uuid =3D c0da11ed-72d8-1a58-aa94-127035fa28d7 force= =3Dtrue"

=C2=A0 =C2=A0 c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr
=C2=A0 =C2=A0 the size of imported file 123G

=C2=A0 =C2=A0 but failed with message "Fatal error: exception
=C2=A0 =C2=A0 Unix.Unix_error(13, "tcsetattr", "")"= ;
=C2=A0 =C2=A0 and hung task
=C2=A0 =C2=A0 uuid ( RO) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0: be568259-c9cd-be13-7da5-8ed2a222e898
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 name-label ( RO): VM impor= t
=C2=A0 =C2=A0 =C2=A0 =C2=A0 name-description ( RO):
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 status ( RO)= : pending
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 progress ( RO): 0.7= 20

=C2=A0 =C2=A0 is there any chance to recover VM?


=C2=A0 =C2=A0 -- =C2=A0 =C2=A0 //wbr Anatoliy Poloz


First you probably want to kill the hung task. Get a list of tasks with

xe task-list

Then cancel the pending task with

xe task-cancel uuid=3D<task UUID>

Once you've done that you can figure out what happened. If it's rea= lly talking about a Unix 13 error that's used for Permission denied so = perhaps you need to investigate to make sure you have access (permissions, = disk space etc...). I'd test by doing an xe vm-export of something smal= ler and then importing it so you can rule out whether it has to do with a v= ery large VM or not (plus it takes less time).

- smaller VM imported without problems
- the task is disapear after some time
- free space is avalible
- lsof showing
lsof 2>/dev/null |grep 79264c6a-5818-4586-9ae8-aff26c7d81d8
tapdisk2 =C2=A030724 =C2=A0 =C2=A0 root =C2=A0 =C2=A04u =C2=A0 =C2=A0 =C2= =A0REG =C2=A0 =C2=A0 =C2=A0 =C2=A08,1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A00 278643 /var/lock/sm/79264c6a-5818-4586-9ae8-aff26c7d81d8/vdi=
tapdisk2 =C2=A030724 =C2=A0 =C2=A0 root =C2=A0 13u =C2=A0 =C2=A0 =C2=A0REG = =C2=A0 =C2=A0 =C2=A0252,0 227962929152 49156 /var/run/sr-mount/c0da11ed-= 72d8-1a58-aa94-127035fa28d7/79264c6a-5818-4586-9ae8-aff26= c7d81d8.vhd

where 79264c6a-5818-4586-9ae8-aff26c7d81d8 one of VM vdi's


can i manualy extract disk images from xva?

Grant McWilliams


--
//wbr Anatoliy Poloz


Where is this disk being i= mported from? Is it a network drive or is it stored on the local storage?


Grant McWilliams=
http://grantmcwil= liams.com/

Some people, when confronted with a problem, think &q= uot;I know, I'll use Windows."=C2=A0
Now they have two pro= blems.=C2=A0
--e89a8f23549d77bf0e04d3695dbd-- --===============4880521121826261042== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4880521121826261042==-- From xen-api-bounces@lists.xen.org Wed Jan 16 15:17:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 15:17:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvUjy-00064c-LS; Wed, 16 Jan 2013 15:17:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvUjw-00064V-MQ for xen-api@lists.xen.org; Wed, 16 Jan 2013 15:17:21 +0000 Received: from [85.158.137.99:10869] by server-13.bemta-3.messagelabs.com id F4/61-14710-F74C6F05; Wed, 16 Jan 2013 15:17:19 +0000 X-Env-Sender: grantmasterflash@gmail.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1358349401!12465240!1 X-Originating-IP: [209.85.223.171] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4250 invoked from network); 16 Jan 2013 15:16:42 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-5.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 15:16:42 -0000 Received: by mail-ie0-f171.google.com with SMTP id 17so2685162iea.30 for ; Wed, 16 Jan 2013 07:16:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=DBozWBt+EvuYtMBdhtK9l3GlVwPKMQ8HzDBumzArkxw=; b=kOOD9jUtoMvWOYvxidwxAN/pWOoMR/B/NGhJolki+WXTav/CW5XLyUNKq2Rew6raC1 gLSM+TQYCo44p9BfBVhQJ5Kf9rd1C6Qw0O81wVOUFdjahzjkB1gC4XS7Yxb2gO0Pe91z bPu0Z0FfZqCc+TnLKv4Yq7IGln03aEtpNrFrqGWTM9fzODgoRl5wXGppE/A2dPyo/Qfe aCJl5Xmqr1CrtVJZQSgFY/ptvxJvEice2sEp0Hq9AYVhiIBcIPzIa9iyFB5ntiSb77hl IG8a1Ltt08qBGl38PKfCWHFyKZYz4K04tvOck6/wzkFo4s1VGolzS5rfN1QG8QAMIw3H p4Yg== X-Received: by 10.50.151.166 with SMTP id ur6mr1013403igb.66.1358349399998; Wed, 16 Jan 2013 07:16:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.170.175 with HTTP; Wed, 16 Jan 2013 07:15:59 -0800 (PST) In-Reply-To: <50F65666.1000709@onetelecom.od.ua> References: <50F522CF.3000601@onetelecom.od.ua> <50F65666.1000709@onetelecom.od.ua> From: Grant McWilliams Date: Wed, 16 Jan 2013 07:15:59 -0800 Message-ID: To: Anatoliy.Poloz@onetelecom.od.ua Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] [xcp] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4880521121826261042==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4880521121826261042== Content-Type: multipart/alternative; boundary=e89a8f23549d77bf0e04d3695dbd --e89a8f23549d77bf0e04d3695dbd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jan 15, 2013 at 11:27 PM, Anatoliy.Poloz < Anatoliy.Poloz@onetelecom.od.ua> wrote: > 15.01.2013 17:43, Grant McWilliams =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > On Tue, Jan 15, 2013 at 1:35 AM, Anatoliy.Poloz < >> Anatoliy.Poloz@onetelecom.od.**ua > Anatoliy.Poloz@**onetelecom.od.ua >> >> wrote: >> >> >> good day xen community >> >> my xcp enveroment is >> BUILD_NUMBER=3D'42052c' >> PRODUCT_NAME=3D'xcp' >> INSTALLATION_DATE=3D'2011-11-18 05:44:28.782878' >> PRODUCT_VERSION=3D'1.0.0' >> >> I tried to import a previously saved VM >> with the command >> "#xe vm-import filename =3D / >> var/run/sr-mount/c0da11ed-**72d8-1a58-aa94-127035fa28d7/** >> infr-samba-2013-01-02_01-04-**01.xva >> sr-uuid =3D c0da11ed-72d8-1a58-aa94-**127035fa28d7 force=3Dtrue" >> >> c0da11ed-72d8-1a58-aa94-**127035a28d7 - ext3 local sr >> >> the size of imported file 123G >> >> but failed with message "Fatal error: exception >> Unix.Unix_error(13, "tcsetattr", "")" >> and hung task >> uuid ( RO) : be568259-c9cd-be13-7da5-**8ed2a222e898 >> name-label ( RO): VM import >> name-description ( RO): >> status ( RO): pending >> progress ( RO): 0.720 >> >> is there any chance to recover VM? >> >> >> -- //wbr Anatoliy Poloz >> >> >> First you probably want to kill the hung task. Get a list of tasks with >> >> xe task-list >> >> Then cancel the pending task with >> >> xe task-cancel uuid=3D >> >> Once you've done that you can figure out what happened. If it's really >> talking about a Unix 13 error that's used for Permission denied so perha= ps >> you need to investigate to make sure you have access (permissions, disk >> space etc...). I'd test by doing an xe vm-export of something smaller an= d >> then importing it so you can rule out whether it has to do with a very >> large VM or not (plus it takes less time). >> >> - smaller VM imported without problems > - the task is disapear after some time > - free space is avalible > - lsof showing > lsof 2>/dev/null |grep 79264c6a-5818-4586-9ae8-**aff26c7d81d8 > tapdisk2 30724 root 4u REG 8,1 0 278643 > /var/lock/sm/79264c6a-5818-**4586-9ae8-aff26c7d81d8/vdi > tapdisk2 30724 root 13u REG 252,0 227962929152 49156 > /var/run/sr-mount/c0da11ed-**72d8-1a58-aa94-127035fa28d7/** > 79264c6a-5818-4586-9ae8-**aff26c7d81d8.vhd > > where 79264c6a-5818-4586-9ae8-**aff26c7d81d8 one of VM vdi's > > > can i manualy extract disk images from xva? > > Grant McWilliams >> > > > -- > //wbr Anatoliy Poloz > > Where is this disk being imported from? Is it a network drive or is it stored on the local storage? Grant McWilliams http://grantmcwilliams.com/ Some people, when confronted with a problem, think "I know, I'll use Windows." Now they have two problems. --e89a8f23549d77bf0e04d3695dbd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Tue, Jan 15, 2013 at 11:27 PM, Anatoliy.P= oloz <Anatoliy.Poloz@onetelecom.od.ua> wrote:<= br>
15.01.2013 17:43, Grant McWilliams =D0=BF=D0=B8=D1=88=D0=B5=D1=82:

On Tue, Jan 15, 2013 at 1:35 AM, Anatoliy.Poloz <Anatoliy.Poloz@onetelecom.od.= ua <mailto:Anatoliy.Poloz@onetelecom.od.ua>> wrote= :


=C2=A0 =C2=A0 good day xen community

=C2=A0 =C2=A0 my xcp enveroment is
=C2=A0 =C2=A0 BUILD_NUMBER=3D'42052c'
=C2=A0 =C2=A0 PRODUCT_NAME=3D'xcp'
=C2=A0 =C2=A0 INSTALLATION_DATE=3D'2011-11-18 05:44:28.782878'
=C2=A0 =C2=A0 PRODUCT_VERSION=3D'1.0.0'

=C2=A0 =C2=A0 I tried to import a previously saved VM
=C2=A0 =C2=A0 with the command
=C2=A0 =C2=A0 "#xe vm-import filename =3D /
=C2=A0 =C2=A0 var/run/sr-mount/c0da11ed-72d8-1a58-aa94-127035fa28d7/= infr-samba-2013-01-02_01-04-01.xva
=C2=A0 =C2=A0 sr-uuid =3D c0da11ed-72d8-1a58-aa94-127035fa28d7 force= =3Dtrue"

=C2=A0 =C2=A0 c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr
=C2=A0 =C2=A0 the size of imported file 123G

=C2=A0 =C2=A0 but failed with message "Fatal error: exception
=C2=A0 =C2=A0 Unix.Unix_error(13, "tcsetattr", "")"= ;
=C2=A0 =C2=A0 and hung task
=C2=A0 =C2=A0 uuid ( RO) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0: be568259-c9cd-be13-7da5-8ed2a222e898
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 name-label ( RO): VM impor= t
=C2=A0 =C2=A0 =C2=A0 =C2=A0 name-description ( RO):
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 status ( RO)= : pending
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 progress ( RO): 0.7= 20

=C2=A0 =C2=A0 is there any chance to recover VM?


=C2=A0 =C2=A0 -- =C2=A0 =C2=A0 //wbr Anatoliy Poloz


First you probably want to kill the hung task. Get a list of tasks with

xe task-list

Then cancel the pending task with

xe task-cancel uuid=3D<task UUID>

Once you've done that you can figure out what happened. If it's rea= lly talking about a Unix 13 error that's used for Permission denied so = perhaps you need to investigate to make sure you have access (permissions, = disk space etc...). I'd test by doing an xe vm-export of something smal= ler and then importing it so you can rule out whether it has to do with a v= ery large VM or not (plus it takes less time).

- smaller VM imported without problems
- the task is disapear after some time
- free space is avalible
- lsof showing
lsof 2>/dev/null |grep 79264c6a-5818-4586-9ae8-aff26c7d81d8
tapdisk2 =C2=A030724 =C2=A0 =C2=A0 root =C2=A0 =C2=A04u =C2=A0 =C2=A0 =C2= =A0REG =C2=A0 =C2=A0 =C2=A0 =C2=A08,1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A00 278643 /var/lock/sm/79264c6a-5818-4586-9ae8-aff26c7d81d8/vdi=
tapdisk2 =C2=A030724 =C2=A0 =C2=A0 root =C2=A0 13u =C2=A0 =C2=A0 =C2=A0REG = =C2=A0 =C2=A0 =C2=A0252,0 227962929152 49156 /var/run/sr-mount/c0da11ed-= 72d8-1a58-aa94-127035fa28d7/79264c6a-5818-4586-9ae8-aff26= c7d81d8.vhd

where 79264c6a-5818-4586-9ae8-aff26c7d81d8 one of VM vdi's


can i manualy extract disk images from xva?

Grant McWilliams


--
//wbr Anatoliy Poloz


Where is this disk being i= mported from? Is it a network drive or is it stored on the local storage?


Grant McWilliams=
http://grantmcwil= liams.com/

Some people, when confronted with a problem, think &q= uot;I know, I'll use Windows."=C2=A0
Now they have two pro= blems.=C2=A0
--e89a8f23549d77bf0e04d3695dbd-- --===============4880521121826261042== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4880521121826261042==-- From xen-api-bounces@lists.xen.org Wed Jan 16 16:15:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 16:15:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvVdp-0001J8-HB; Wed, 16 Jan 2013 16:15:05 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvVdn-0001Il-Sp; Wed, 16 Jan 2013 16:15:03 +0000 Received: from [193.109.254.147:41195] by server-9.bemta-14.messagelabs.com id 95/BB-24482-602D6F05; Wed, 16 Jan 2013 16:15:02 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1358352896!809129!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2NjQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9012 invoked from network); 16 Jan 2013 16:14:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 16:14:58 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="697421" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Jan 2013 16:14:53 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Wed, 16 Jan 2013 16:14:52 +0000 Message-ID: <1358352891.32431.100.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Wed, 16 Jan 2013 16:14:51 +0000 In-Reply-To: <50F044C3.7010400@xen.org> References: <50F044C3.7010400@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , Amir M Chaudhry , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: > this e-mail is to let you know that the OpenMirage project is seeking to > become a Xen.org hosted project. Mirage is cool stuff. I'm all for this, FWIW. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 16:15:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 16:15:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvVdp-0001J8-HB; Wed, 16 Jan 2013 16:15:05 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvVdn-0001Il-Sp; Wed, 16 Jan 2013 16:15:03 +0000 Received: from [193.109.254.147:41195] by server-9.bemta-14.messagelabs.com id 95/BB-24482-602D6F05; Wed, 16 Jan 2013 16:15:02 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1358352896!809129!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2NjQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9012 invoked from network); 16 Jan 2013 16:14:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 16:14:58 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="697421" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Jan 2013 16:14:53 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Wed, 16 Jan 2013 16:14:52 +0000 Message-ID: <1358352891.32431.100.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Wed, 16 Jan 2013 16:14:51 +0000 In-Reply-To: <50F044C3.7010400@xen.org> References: <50F044C3.7010400@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , Amir M Chaudhry , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: > this e-mail is to let you know that the OpenMirage project is seeking to > become a Xen.org hosted project. Mirage is cool stuff. I'm all for this, FWIW. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 17:18:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 17:18:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWd0-0005Vu-5X; Wed, 16 Jan 2013 17:18:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWcz-0005Vc-3a; Wed, 16 Jan 2013 17:18:17 +0000 Received: from [193.109.254.147:63098] by server-6.bemta-14.messagelabs.com id 96/6E-25153-8D0E6F05; Wed, 16 Jan 2013 17:18:16 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1358356598!8899327!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTYyMDc=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27418 invoked from network); 16 Jan 2013 17:16:39 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 17:16:39 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="3963059" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 16 Jan 2013 17:16:37 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Wed, 16 Jan 2013 12:16:37 -0500 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TvWbN-0007iG-49; Wed, 16 Jan 2013 17:16:37 +0000 Date: Wed, 16 Jan 2013 17:16:33 +0000 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Lars Kurth In-Reply-To: <50F044C3.7010400@xen.org> Message-ID: References: <50F044C3.7010400@xen.org> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , Amir M Chaudhry , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [XenARM] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org +1 On Fri, 11 Jan 2013, Lars Kurth wrote: > Hi everybody, > > this e-mail is to let you know that the OpenMirage project is seeking to > become a > Xen.org hosted project. > > The prospective project lead of the Mirage Project - Anil Madhavapeddy - > has requested > a Review of the Mirage Project to become an Xen.org Incubation project. > In line with > Xen Project Governance (see > http://www.xen.org/projects/governance.html), in particular > sections > > - "Forming a Project" at > http://www.xen.org/projects/governance.html#project.forming > > - "Project Proposal" at > http://www.xen.org/projects/governance.html#project.proposal > > - "Requesting Reviews, Reviews and Voting" at > http://www.xen.org/projects/governance.html#project.requests > > This is an informal community review, which will be followed by a formal > vote. > > The Proposal and Proposal Meta Information > ========================================== > > - Proposal Location at: > http://wiki.xen.org/wiki/Mirage_Incubation_Project_Proposal > > - Project Lead: Anil Madhavapeddy > - Project Sponsor: Tim Deegan > - Project Mentor: Lars Kurth > > - Deadline: review open until 24:00, 27th of Jan, 2013 (GMT) > > Following the Community Review, there may be an update to the proposal if > needed. Which is then followed by a formal vote by eligible community > members. > > Why and How to Provide Feedback > =============================== > - Anybody in the Community can provide feedback > > - Preferably, feedback should be provided by annotating the in-lined > copy of > the document using the instructions in the wiki. In other word insert > > "{{comment|~~~~}} your comment." > > into the document, at a suitable location in the document. > > - Alternatively you can provide feedback by replying to this e-mail > > Best Regards > Lars > > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 17:18:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 17:18:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWd0-0005Vu-5X; Wed, 16 Jan 2013 17:18:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWcz-0005Vc-3a; Wed, 16 Jan 2013 17:18:17 +0000 Received: from [193.109.254.147:63098] by server-6.bemta-14.messagelabs.com id 96/6E-25153-8D0E6F05; Wed, 16 Jan 2013 17:18:16 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1358356598!8899327!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTYyMDc=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27418 invoked from network); 16 Jan 2013 17:16:39 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 17:16:39 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="3963059" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 16 Jan 2013 17:16:37 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Wed, 16 Jan 2013 12:16:37 -0500 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TvWbN-0007iG-49; Wed, 16 Jan 2013 17:16:37 +0000 Date: Wed, 16 Jan 2013 17:16:33 +0000 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Lars Kurth In-Reply-To: <50F044C3.7010400@xen.org> Message-ID: References: <50F044C3.7010400@xen.org> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , Amir M Chaudhry , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [XenARM] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org +1 On Fri, 11 Jan 2013, Lars Kurth wrote: > Hi everybody, > > this e-mail is to let you know that the OpenMirage project is seeking to > become a > Xen.org hosted project. > > The prospective project lead of the Mirage Project - Anil Madhavapeddy - > has requested > a Review of the Mirage Project to become an Xen.org Incubation project. > In line with > Xen Project Governance (see > http://www.xen.org/projects/governance.html), in particular > sections > > - "Forming a Project" at > http://www.xen.org/projects/governance.html#project.forming > > - "Project Proposal" at > http://www.xen.org/projects/governance.html#project.proposal > > - "Requesting Reviews, Reviews and Voting" at > http://www.xen.org/projects/governance.html#project.requests > > This is an informal community review, which will be followed by a formal > vote. > > The Proposal and Proposal Meta Information > ========================================== > > - Proposal Location at: > http://wiki.xen.org/wiki/Mirage_Incubation_Project_Proposal > > - Project Lead: Anil Madhavapeddy > - Project Sponsor: Tim Deegan > - Project Mentor: Lars Kurth > > - Deadline: review open until 24:00, 27th of Jan, 2013 (GMT) > > Following the Community Review, there may be an update to the proposal if > needed. Which is then followed by a formal vote by eligible community > members. > > Why and How to Provide Feedback > =============================== > - Anybody in the Community can provide feedback > > - Preferably, feedback should be provided by annotating the in-lined > copy of > the document using the instructions in the wiki. In other word insert > > "{{comment|~~~~}} your comment." > > into the document, at a suitable location in the document. > > - Alternatively you can provide feedback by replying to this e-mail > > Best Regards > Lars > > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 17:24:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 17:24:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWiW-00061a-Kh; Wed, 16 Jan 2013 17:24:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWiV-00061L-TB; Wed, 16 Jan 2013 17:24:00 +0000 Received: from [85.158.138.51:34734] by server-2.bemta-3.messagelabs.com id 89/12-26461-E22E6F05; Wed, 16 Jan 2013 17:23:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1358357038!21929015!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2NjQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24141 invoked from network); 16 Jan 2013 17:23:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 17:23:58 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="699953" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Jan 2013 17:23:57 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Wed, 16 Jan 2013 17:23:57 +0000 Message-ID: <1358357036.13856.14.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Goswin von Brederlow Date: Wed, 16 Jan 2013 17:23:56 +0000 In-Reply-To: <20130116171723.GB15900@frosties> References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: Amir M Chaudhry , "xen-devel@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Wed, 2013-01-16 at 17:17 +0000, Goswin von Brederlow wrote: > On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: > > On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: > > > this e-mail is to let you know that the OpenMirage project is seeking to > > > become a Xen.org hosted project. > > > > Mirage is cool stuff. > > > > I'm all for this, FWIW. > > > > Ian. > > Mirage is cool indeed. Only used it on x86 though. > > Since I got this mail via the xen-arm ML does that mean mirage supports > xen-arm too? You might get a better response if you don't drop the CC. AIUI the intention is to eventually support ARM. I expect the xen-api CC was because it is the existing project leads who ultimately vote to accept the project or something like that. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 17:24:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 17:24:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWiW-00061a-Kh; Wed, 16 Jan 2013 17:24:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWiV-00061L-TB; Wed, 16 Jan 2013 17:24:00 +0000 Received: from [85.158.138.51:34734] by server-2.bemta-3.messagelabs.com id 89/12-26461-E22E6F05; Wed, 16 Jan 2013 17:23:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1358357038!21929015!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2NjQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24141 invoked from network); 16 Jan 2013 17:23:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 17:23:58 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="699953" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Jan 2013 17:23:57 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.5; Wed, 16 Jan 2013 17:23:57 +0000 Message-ID: <1358357036.13856.14.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Goswin von Brederlow Date: Wed, 16 Jan 2013 17:23:56 +0000 In-Reply-To: <20130116171723.GB15900@frosties> References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: Amir M Chaudhry , "xen-devel@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Wed, 2013-01-16 at 17:17 +0000, Goswin von Brederlow wrote: > On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: > > On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: > > > this e-mail is to let you know that the OpenMirage project is seeking to > > > become a Xen.org hosted project. > > > > Mirage is cool stuff. > > > > I'm all for this, FWIW. > > > > Ian. > > Mirage is cool indeed. Only used it on x86 though. > > Since I got this mail via the xen-arm ML does that mean mirage supports > xen-arm too? You might get a better response if you don't drop the CC. AIUI the intention is to eventually support ARM. I expect the xen-api CC was because it is the existing project leads who ultimately vote to accept the project or something like that. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 17:28:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 17:28:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWmJ-0006X0-Qq; Wed, 16 Jan 2013 17:27:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWmI-0006Wl-JQ for xen-api@lists.xen.org; Wed, 16 Jan 2013 17:27:54 +0000 Received: from [85.158.137.99:49438] by server-3.bemta-3.messagelabs.com id DD/7A-00848-913E6F05; Wed, 16 Jan 2013 17:27:53 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-217.messagelabs.com!1358357272!12172847!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1125 invoked from network); 16 Jan 2013 17:27:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-217.messagelabs.com with SMTP; 16 Jan 2013 17:27:52 -0000 Received: (qmail 4199 invoked by uid 634); 16 Jan 2013 17:27:51 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 16 Jan 2013 17:27:51 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1358357036.13856.14.camel@zakaz.uk.xensource.com> Date: Wed, 16 Jan 2013 17:27:52 +0000 Message-Id: <53A794F5-259A-46D5-8BA9-CBE06242E7F3@recoil.org> References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> <1358357036.13856.14.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Amir M Chaudhry , Goswin von Brederlow , "xen-devel@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 16 Jan 2013, at 17:23, Ian Campbell wrote: > On Wed, 2013-01-16 at 17:17 +0000, Goswin von Brederlow wrote: >> On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: >>> On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: >>>> this e-mail is to let you know that the OpenMirage project is seeking to >>>> become a Xen.org hosted project. >>> >>> Mirage is cool stuff. >>> >>> I'm all for this, FWIW. >>> >>> Ian. >> >> Mirage is cool indeed. Only used it on x86 though. >> >> Since I got this mail via the xen-arm ML does that mean mirage supports >> xen-arm too? > > You might get a better response if you don't drop the CC. > > AIUI the intention is to eventually support ARM. > > I expect the xen-api CC was because it is the existing project leads who > ultimately vote to accept the project or something like that. We are indeed planning to support xen-arm, but are waiting for hardware. Dave and I both have Chromebooks A15 now, and we have patches floating around for HVM/x86_minios. An ARM PVHVM version should be quite straightforward. Another summer project I'm happy to supervise (particularly for GSoC) is a direct Raspberry Pi port, using uBoot as the main bootloader. That should shake out any ARM-specific issues in advance of a Xen/ARM port. Please get in touch with me if interested in this one. -anil _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 17:28:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 17:28:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWmJ-0006X0-Qq; Wed, 16 Jan 2013 17:27:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWmI-0006Wl-JQ for xen-api@lists.xen.org; Wed, 16 Jan 2013 17:27:54 +0000 Received: from [85.158.137.99:49438] by server-3.bemta-3.messagelabs.com id DD/7A-00848-913E6F05; Wed, 16 Jan 2013 17:27:53 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-217.messagelabs.com!1358357272!12172847!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1125 invoked from network); 16 Jan 2013 17:27:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-217.messagelabs.com with SMTP; 16 Jan 2013 17:27:52 -0000 Received: (qmail 4199 invoked by uid 634); 16 Jan 2013 17:27:51 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 16 Jan 2013 17:27:51 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1358357036.13856.14.camel@zakaz.uk.xensource.com> Date: Wed, 16 Jan 2013 17:27:52 +0000 Message-Id: <53A794F5-259A-46D5-8BA9-CBE06242E7F3@recoil.org> References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> <1358357036.13856.14.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Amir M Chaudhry , Goswin von Brederlow , "xen-devel@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 16 Jan 2013, at 17:23, Ian Campbell wrote: > On Wed, 2013-01-16 at 17:17 +0000, Goswin von Brederlow wrote: >> On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: >>> On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: >>>> this e-mail is to let you know that the OpenMirage project is seeking to >>>> become a Xen.org hosted project. >>> >>> Mirage is cool stuff. >>> >>> I'm all for this, FWIW. >>> >>> Ian. >> >> Mirage is cool indeed. Only used it on x86 though. >> >> Since I got this mail via the xen-arm ML does that mean mirage supports >> xen-arm too? > > You might get a better response if you don't drop the CC. > > AIUI the intention is to eventually support ARM. > > I expect the xen-api CC was because it is the existing project leads who > ultimately vote to accept the project or something like that. We are indeed planning to support xen-arm, but are waiting for hardware. Dave and I both have Chromebooks A15 now, and we have patches floating around for HVM/x86_minios. An ARM PVHVM version should be quite straightforward. Another summer project I'm happy to supervise (particularly for GSoC) is a direct Raspberry Pi port, using uBoot as the main bootloader. That should shake out any ARM-specific issues in advance of a Xen/ARM port. Please get in touch with me if interested in this one. -anil _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 17:39:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 17:39:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWx3-0007HL-TM; Wed, 16 Jan 2013 17:39:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWx1-0007H5-Vi for xen-api@lists.xensource.com; Wed, 16 Jan 2013 17:39:00 +0000 Received: from [85.158.139.83:11366] by server-6.bemta-5.messagelabs.com id C4/E6-28743-1B5E6F05; Wed, 16 Jan 2013 17:38:57 +0000 X-Env-Sender: msinhore@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1358357936!20941984!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20793 invoked from network); 16 Jan 2013 17:38:56 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 17:38:56 -0000 Received: by mail-wi0-f178.google.com with SMTP id hn3so1491825wib.17 for ; Wed, 16 Jan 2013 09:38:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=igzBVn0UIMYl60i4u8WuluTf1xJKF51RC+eoTVrr1rE=; b=SxQLIYGs1Y4hp8mFdeyJOZtN3ZL0CEkPbZw3L04gnkva6CyvxNJ99c2Mnrw94xExWi 6vD680cOUuiuMSNSr52C9mVbrcEEBGfXkJ4LRiFpv5HmArGbDzQBHzlQxNz6MN8AhlgO KmZlVp4xDcvogxeDNPFdBLHq6z9qlWmX93xDHaw0trj4XKmyV+j7Fe9FKOoBex14Lp3r w5K/3xr1FV7HEDVbgtSejJ0VVHYv2r4rZ+uBwdjwIHO3BpMxTnHJkVXLbtoLy3RHtnEp JOKX3k5tKQiI5KpEIDo0a+q6daYOHqytoqXQ5zmZAZ8GKXo51g+tKlzTvPyGim7Y8BL0 vzgg== MIME-Version: 1.0 X-Received: by 10.180.95.135 with SMTP id dk7mr11449980wib.29.1358357936309; Wed, 16 Jan 2013 09:38:56 -0800 (PST) Received: by 10.216.244.1 with HTTP; Wed, 16 Jan 2013 09:38:56 -0800 (PST) In-Reply-To: <53A794F5-259A-46D5-8BA9-CBE06242E7F3@recoil.org> References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> <1358357036.13856.14.camel@zakaz.uk.xensource.com> <53A794F5-259A-46D5-8BA9-CBE06242E7F3@recoil.org> Date: Wed, 16 Jan 2013 15:38:56 -0200 Message-ID: From: Marco Sinhoreli To: xen-api Subject: Re: [Xen-API] [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Wow! Very interesting project! +1 On Wed, Jan 16, 2013 at 3:27 PM, Anil Madhavapeddy wrote: > > On 16 Jan 2013, at 17:23, Ian Campbell wrote: > >> On Wed, 2013-01-16 at 17:17 +0000, Goswin von Brederlow wrote: >>> On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: >>>> On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: >>>>> this e-mail is to let you know that the OpenMirage project is seeking to >>>>> become a Xen.org hosted project. >>>> >>>> Mirage is cool stuff. >>>> >>>> I'm all for this, FWIW. >>>> >>>> Ian. >>> >>> Mirage is cool indeed. Only used it on x86 though. >>> >>> Since I got this mail via the xen-arm ML does that mean mirage supports >>> xen-arm too? >> >> You might get a better response if you don't drop the CC. >> >> AIUI the intention is to eventually support ARM. >> >> I expect the xen-api CC was because it is the existing project leads who >> ultimately vote to accept the project or something like that. > > We are indeed planning to support xen-arm, but are waiting for hardware. > Dave and I both have Chromebooks A15 now, and we have patches floating around > for HVM/x86_minios. An ARM PVHVM version should be quite straightforward. > > Another summer project I'm happy to supervise (particularly for GSoC) is a > direct Raspberry Pi port, using uBoot as the main bootloader. That should > shake out any ARM-specific issues in advance of a Xen/ARM port. Please get in > touch with me if interested in this one. > > -anil > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api -- Marco Sinhoreli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 17:39:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 17:39:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWx3-0007HL-TM; Wed, 16 Jan 2013 17:39:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWx1-0007H5-Vi for xen-api@lists.xensource.com; Wed, 16 Jan 2013 17:39:00 +0000 Received: from [85.158.139.83:11366] by server-6.bemta-5.messagelabs.com id C4/E6-28743-1B5E6F05; Wed, 16 Jan 2013 17:38:57 +0000 X-Env-Sender: msinhore@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1358357936!20941984!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20793 invoked from network); 16 Jan 2013 17:38:56 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 17:38:56 -0000 Received: by mail-wi0-f178.google.com with SMTP id hn3so1491825wib.17 for ; Wed, 16 Jan 2013 09:38:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=igzBVn0UIMYl60i4u8WuluTf1xJKF51RC+eoTVrr1rE=; b=SxQLIYGs1Y4hp8mFdeyJOZtN3ZL0CEkPbZw3L04gnkva6CyvxNJ99c2Mnrw94xExWi 6vD680cOUuiuMSNSr52C9mVbrcEEBGfXkJ4LRiFpv5HmArGbDzQBHzlQxNz6MN8AhlgO KmZlVp4xDcvogxeDNPFdBLHq6z9qlWmX93xDHaw0trj4XKmyV+j7Fe9FKOoBex14Lp3r w5K/3xr1FV7HEDVbgtSejJ0VVHYv2r4rZ+uBwdjwIHO3BpMxTnHJkVXLbtoLy3RHtnEp JOKX3k5tKQiI5KpEIDo0a+q6daYOHqytoqXQ5zmZAZ8GKXo51g+tKlzTvPyGim7Y8BL0 vzgg== MIME-Version: 1.0 X-Received: by 10.180.95.135 with SMTP id dk7mr11449980wib.29.1358357936309; Wed, 16 Jan 2013 09:38:56 -0800 (PST) Received: by 10.216.244.1 with HTTP; Wed, 16 Jan 2013 09:38:56 -0800 (PST) In-Reply-To: <53A794F5-259A-46D5-8BA9-CBE06242E7F3@recoil.org> References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> <1358357036.13856.14.camel@zakaz.uk.xensource.com> <53A794F5-259A-46D5-8BA9-CBE06242E7F3@recoil.org> Date: Wed, 16 Jan 2013 15:38:56 -0200 Message-ID: From: Marco Sinhoreli To: xen-api Subject: Re: [Xen-API] [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Wow! Very interesting project! +1 On Wed, Jan 16, 2013 at 3:27 PM, Anil Madhavapeddy wrote: > > On 16 Jan 2013, at 17:23, Ian Campbell wrote: > >> On Wed, 2013-01-16 at 17:17 +0000, Goswin von Brederlow wrote: >>> On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: >>>> On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: >>>>> this e-mail is to let you know that the OpenMirage project is seeking to >>>>> become a Xen.org hosted project. >>>> >>>> Mirage is cool stuff. >>>> >>>> I'm all for this, FWIW. >>>> >>>> Ian. >>> >>> Mirage is cool indeed. Only used it on x86 though. >>> >>> Since I got this mail via the xen-arm ML does that mean mirage supports >>> xen-arm too? >> >> You might get a better response if you don't drop the CC. >> >> AIUI the intention is to eventually support ARM. >> >> I expect the xen-api CC was because it is the existing project leads who >> ultimately vote to accept the project or something like that. > > We are indeed planning to support xen-arm, but are waiting for hardware. > Dave and I both have Chromebooks A15 now, and we have patches floating around > for HVM/x86_minios. An ARM PVHVM version should be quite straightforward. > > Another summer project I'm happy to supervise (particularly for GSoC) is a > direct Raspberry Pi port, using uBoot as the main bootloader. That should > shake out any ARM-specific issues in advance of a Xen/ARM port. Please get in > touch with me if interested in this one. > > -anil > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api -- Marco Sinhoreli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 18:29:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 18:29:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvXjP-0001mc-Cw; Wed, 16 Jan 2013 18:28:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvXjN-0001mE-Ib for xen-api@lists.xen.org; Wed, 16 Jan 2013 18:28:57 +0000 Received: from [193.109.254.147:22355] by server-5.bemta-14.messagelabs.com id 9E/2A-32031-861F6F05; Wed, 16 Jan 2013 18:28:56 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1358360934!8699103!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTYyMDc=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2703 invoked from network); 16 Jan 2013 18:28:56 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 18:28:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="3973996" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 16 Jan 2013 18:28:54 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Wed, 16 Jan 2013 13:28:54 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TvXjJ-0000dK-Ub; Wed, 16 Jan 2013 18:28:53 +0000 Message-ID: <50F6F163.3000008@citrix.com> Date: Wed, 16 Jan 2013 18:28:51 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Rushikesh Jadhav <2rushikeshj@gmail.com> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15/01/13 21:01, Rushikesh Jadhav wrote: > Mike & George, Please excuse me if its not related to subject but since > you made the right xapi github branch ( very much required ) can we have > the right Xen branch as well. There is tremendous difference in native > Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. > > - Rushikesh Hi Rushikesh, Yes, this is definitely on topic. I've just gotten access to the xenbits site, and I should have our xen patchqueue mirrored up there by the end of the week. Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 18:29:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 18:29:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvXjP-0001mc-Cw; Wed, 16 Jan 2013 18:28:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvXjN-0001mE-Ib for xen-api@lists.xen.org; Wed, 16 Jan 2013 18:28:57 +0000 Received: from [193.109.254.147:22355] by server-5.bemta-14.messagelabs.com id 9E/2A-32031-861F6F05; Wed, 16 Jan 2013 18:28:56 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1358360934!8699103!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTYyMDc=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2703 invoked from network); 16 Jan 2013 18:28:56 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 18:28:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="3973996" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 16 Jan 2013 18:28:54 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Wed, 16 Jan 2013 13:28:54 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TvXjJ-0000dK-Ub; Wed, 16 Jan 2013 18:28:53 +0000 Message-ID: <50F6F163.3000008@citrix.com> Date: Wed, 16 Jan 2013 18:28:51 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Rushikesh Jadhav <2rushikeshj@gmail.com> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15/01/13 21:01, Rushikesh Jadhav wrote: > Mike & George, Please excuse me if its not related to subject but since > you made the right xapi github branch ( very much required ) can we have > the right Xen branch as well. There is tremendous difference in native > Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. > > - Rushikesh Hi Rushikesh, Yes, this is definitely on topic. I've just gotten access to the xenbits site, and I should have our xen patchqueue mirrored up there by the end of the week. Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 18:50:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 18:50:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvY4T-0002T8-W7; Wed, 16 Jan 2013 18:50:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TvY4T-0002Sx-1V for xen-api@lists.xen.org; Wed, 16 Jan 2013 18:50:45 +0000 Received: from [85.158.139.83:51848] by server-15.bemta-5.messagelabs.com id 3A/86-18817-486F6F05; Wed, 16 Jan 2013 18:50:44 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1358362242!23890837!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15807 invoked from network); 16 Jan 2013 18:50:43 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 18:50:43 -0000 Received: by mail-qa0-f44.google.com with SMTP id z4so3624209qan.3 for ; Wed, 16 Jan 2013 10:50:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1SQVzEXkkzFeskujdYhmp3owHwHQjr+3HKkzZjSgg2k=; b=hCu6lhtbpCOvx17MMEdDD7KWknbJi9vFxwbiW8XsqDbyFJmRvTbdSwbnpqI/sMI1jH LQq+f/1A47c+KNw46NcLr4IfrBAMfzRMw3iYx9Hwcs34DgOhZ48FYLjBxbKRI8B7N5g8 ssFR4c7jTGmpabRQ1Hajzkt+v1gvtIh7Ut4uxaOTCXqyT4XqMA3vvs/+e2tyaXU8mKeI T7j8Fxw3VZK/e8ooS7qaq2OJhZGqpz5xEoc4hYhIu54gau4DQniCqFEYFpdpcDjpyhnH 7oLRfHa/OJp3RnUyb1NhlkjAKyECC/29DVt3AokU30mzsjakjCtAwbbACJWFSOeRDPJ7 ahrA== MIME-Version: 1.0 X-Received: by 10.224.180.69 with SMTP id bt5mr2792695qab.36.1358362242110; Wed, 16 Jan 2013 10:50:42 -0800 (PST) Received: by 10.229.17.19 with HTTP; Wed, 16 Jan 2013 10:50:41 -0800 (PST) In-Reply-To: <50F6F163.3000008@citrix.com> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> <50F6F163.3000008@citrix.com> Date: Thu, 17 Jan 2013 00:20:41 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Mike McClurg Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0768619806715323486==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0768619806715323486== Content-Type: multipart/alternative; boundary=20cf303b3b05ead30c04d36c5afb --20cf303b3b05ead30c04d36c5afb Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 16, 2013 at 11:58 PM, Mike McClurg wrote: > On 15/01/13 21:01, Rushikesh Jadhav wrote: > >> Mike & George, Please excuse me if its not related to subject but since >> you made the right xapi github branch ( very much required ) can we have >> the right Xen branch as well. There is tremendous difference in native >> Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. >> >> - Rushikesh >> > > Hi Rushikesh, > > Yes, this is definitely on topic. I've just gotten access to the xenbits > site, and I should have our xen patchqueue mirrored up there by the end of > the week. > > Mike > Awesome news Mike. Thank you very much :) I'll look forward for it. --20cf303b3b05ead30c04d36c5afb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, Jan 16, 2013 at 11:58 PM, Mike M= cClurg <mike.mcclurg@citrix.com> wrote:
On 15/01/13 21:01, Rushikesh Jadhav wrote:
Mike & George, Please excuse me if its not related to subject but since=
you made the right xapi github branch ( very much required ) can we have the right Xen branch as well. There is tremendous difference in native
Xen and XCP Xen and similar to Xapi the Xen commit is nowhere.

- Rushikesh

Hi Rushikesh,

Yes, this is definitely on topic. I've just gotten access to the xenbit= s site, and I should have our xen patchqueue mirrored up there by the end o= f the week.

Mike

Awesome news Mike. Thank you ve= ry much :)
I'll look forward for it.
--20cf303b3b05ead30c04d36c5afb-- --===============0768619806715323486== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0768619806715323486==-- From xen-api-bounces@lists.xen.org Wed Jan 16 18:50:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 18:50:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvY4T-0002T8-W7; Wed, 16 Jan 2013 18:50:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TvY4T-0002Sx-1V for xen-api@lists.xen.org; Wed, 16 Jan 2013 18:50:45 +0000 Received: from [85.158.139.83:51848] by server-15.bemta-5.messagelabs.com id 3A/86-18817-486F6F05; Wed, 16 Jan 2013 18:50:44 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1358362242!23890837!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15807 invoked from network); 16 Jan 2013 18:50:43 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 18:50:43 -0000 Received: by mail-qa0-f44.google.com with SMTP id z4so3624209qan.3 for ; Wed, 16 Jan 2013 10:50:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1SQVzEXkkzFeskujdYhmp3owHwHQjr+3HKkzZjSgg2k=; b=hCu6lhtbpCOvx17MMEdDD7KWknbJi9vFxwbiW8XsqDbyFJmRvTbdSwbnpqI/sMI1jH LQq+f/1A47c+KNw46NcLr4IfrBAMfzRMw3iYx9Hwcs34DgOhZ48FYLjBxbKRI8B7N5g8 ssFR4c7jTGmpabRQ1Hajzkt+v1gvtIh7Ut4uxaOTCXqyT4XqMA3vvs/+e2tyaXU8mKeI T7j8Fxw3VZK/e8ooS7qaq2OJhZGqpz5xEoc4hYhIu54gau4DQniCqFEYFpdpcDjpyhnH 7oLRfHa/OJp3RnUyb1NhlkjAKyECC/29DVt3AokU30mzsjakjCtAwbbACJWFSOeRDPJ7 ahrA== MIME-Version: 1.0 X-Received: by 10.224.180.69 with SMTP id bt5mr2792695qab.36.1358362242110; Wed, 16 Jan 2013 10:50:42 -0800 (PST) Received: by 10.229.17.19 with HTTP; Wed, 16 Jan 2013 10:50:41 -0800 (PST) In-Reply-To: <50F6F163.3000008@citrix.com> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> <50F6F163.3000008@citrix.com> Date: Thu, 17 Jan 2013 00:20:41 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Mike McClurg Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0768619806715323486==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0768619806715323486== Content-Type: multipart/alternative; boundary=20cf303b3b05ead30c04d36c5afb --20cf303b3b05ead30c04d36c5afb Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 16, 2013 at 11:58 PM, Mike McClurg wrote: > On 15/01/13 21:01, Rushikesh Jadhav wrote: > >> Mike & George, Please excuse me if its not related to subject but since >> you made the right xapi github branch ( very much required ) can we have >> the right Xen branch as well. There is tremendous difference in native >> Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. >> >> - Rushikesh >> > > Hi Rushikesh, > > Yes, this is definitely on topic. I've just gotten access to the xenbits > site, and I should have our xen patchqueue mirrored up there by the end of > the week. > > Mike > Awesome news Mike. Thank you very much :) I'll look forward for it. --20cf303b3b05ead30c04d36c5afb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, Jan 16, 2013 at 11:58 PM, Mike M= cClurg <mike.mcclurg@citrix.com> wrote:
On 15/01/13 21:01, Rushikesh Jadhav wrote:
Mike & George, Please excuse me if its not related to subject but since=
you made the right xapi github branch ( very much required ) can we have the right Xen branch as well. There is tremendous difference in native
Xen and XCP Xen and similar to Xapi the Xen commit is nowhere.

- Rushikesh

Hi Rushikesh,

Yes, this is definitely on topic. I've just gotten access to the xenbit= s site, and I should have our xen patchqueue mirrored up there by the end o= f the week.

Mike

Awesome news Mike. Thank you ve= ry much :)
I'll look forward for it.
--20cf303b3b05ead30c04d36c5afb-- --===============0768619806715323486== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0768619806715323486==-- From xen-api-bounces@lists.xen.org Wed Jan 16 19:34:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 19:34:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvYkj-000533-6p; Wed, 16 Jan 2013 19:34:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvYkh-00052y-B5 for xen-api@lists.xen.org; Wed, 16 Jan 2013 19:34:23 +0000 Received: from [85.158.137.99:55690] by server-4.bemta-3.messagelabs.com id 96/7D-04976-EB007F05; Wed, 16 Jan 2013 19:34:22 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1358364858!17251868!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2NjQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15561 invoked from network); 16 Jan 2013 19:34:19 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 19:34:19 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="702542" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Jan 2013 19:34:18 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Wed, 16 Jan 2013 19:34:18 +0000 From: James Bulpin To: George Shuklin , Mike McClurg Date: Wed, 16 Jan 2013 19:35:00 +0000 Thread-Topic: [Xen-API] xapi sources: Fighting for right commit Thread-Index: Ac3zXy8ue2DwhZ9VR36UIfZYEUvd5AAv+D4A Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E8964BE@LONPMAILBOX01.citrite.net> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> In-Reply-To: <50F5BBBA.1030701@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15/01/13 20:28, George Shuklin wrote: >[snip] > > The single big piece of XCP you not published yet is the build process. > Regardless some minor/major issues with library renaming and so on, > there is SOME way you build xapi rpm's for XenServer and XCP, isn't it? > Because next question after successful compilation will be 'can we run > that binary in product environment, even if we did not change a single > line?" If code was successfully linked against some libraries there is > no guarantee it linked against proper versions and will not catch some > bad problems in runtime. > > And the main problem with opensource side of XCP is that - no way to > run > changes in code. This is a reason of weak community response - almost > all features in new XCP/XenServer version (all features?) are from > Citrix, not from crowd... We actually got resolution to dig inside and > scratch our own itch (I even got ocaml guy in our staff for that), but > we stuck on build part... I hear you. These problems are ones we're aware of and have been discussing internally recently. We have a lot of legacy here from XenServer's old proprietary roots. What we have now is messy and does need cleaning up. We are looking at how best to go about this in a sustainable way. We have some thoughts on the best way to proceed but ideas and suggests are welcome. Cheers, James _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 19:34:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 19:34:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvYkj-000533-6p; Wed, 16 Jan 2013 19:34:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvYkh-00052y-B5 for xen-api@lists.xen.org; Wed, 16 Jan 2013 19:34:23 +0000 Received: from [85.158.137.99:55690] by server-4.bemta-3.messagelabs.com id 96/7D-04976-EB007F05; Wed, 16 Jan 2013 19:34:22 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1358364858!17251868!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2NjQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15561 invoked from network); 16 Jan 2013 19:34:19 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 19:34:19 -0000 X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="702542" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Jan 2013 19:34:18 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Wed, 16 Jan 2013 19:34:18 +0000 From: James Bulpin To: George Shuklin , Mike McClurg Date: Wed, 16 Jan 2013 19:35:00 +0000 Thread-Topic: [Xen-API] xapi sources: Fighting for right commit Thread-Index: Ac3zXy8ue2DwhZ9VR36UIfZYEUvd5AAv+D4A Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E8964BE@LONPMAILBOX01.citrite.net> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> In-Reply-To: <50F5BBBA.1030701@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 15/01/13 20:28, George Shuklin wrote: >[snip] > > The single big piece of XCP you not published yet is the build process. > Regardless some minor/major issues with library renaming and so on, > there is SOME way you build xapi rpm's for XenServer and XCP, isn't it? > Because next question after successful compilation will be 'can we run > that binary in product environment, even if we did not change a single > line?" If code was successfully linked against some libraries there is > no guarantee it linked against proper versions and will not catch some > bad problems in runtime. > > And the main problem with opensource side of XCP is that - no way to > run > changes in code. This is a reason of weak community response - almost > all features in new XCP/XenServer version (all features?) are from > Citrix, not from crowd... We actually got resolution to dig inside and > scratch our own itch (I even got ocaml guy in our staff for that), but > we stuck on build part... I hear you. These problems are ones we're aware of and have been discussing internally recently. We have a lot of legacy here from XenServer's old proprietary roots. What we have now is messy and does need cleaning up. We are looking at how best to go about this in a sustainable way. We have some thoughts on the best way to proceed but ideas and suggests are welcome. Cheers, James _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 20:15:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 20:15:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvZO0-0005oo-Hr; Wed, 16 Jan 2013 20:15:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvZNz-0005oj-AK for xen-api@lists.xen.org; Wed, 16 Jan 2013 20:14:59 +0000 Received: from [85.158.138.51:58862] by server-2.bemta-3.messagelabs.com id EE/6B-26461-24A07F05; Wed, 16 Jan 2013 20:14:58 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1358367296!27379664!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8782 invoked from network); 16 Jan 2013 20:14:57 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-2.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Jan 2013 20:14:57 -0000 Received: from [201.122.115.101] (port=60785 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TvZNv-0007PY-Lp for xen-api@lists.xen.org; Wed, 16 Jan 2013 14:14:55 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 1CEB0A209 for ; Wed, 16 Jan 2013 14:11:46 -0600 (CST) Message-ID: <50F70A3E.3060908@ondore.com> Date: Wed, 16 Jan 2013 14:14:54 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: [Xen-API] XCP 1.6 Serial console with IPMI SOL X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. I'm setting up some Dell PowerEdge R320 servers, to have access to serial console. The serial port itself is a internal port, visible as COM2 or ttyS1 to the OS, mapped to a integrated BMC card and accessible via IPMI SOL. My general guide has been Xen Serial Console wiki article [1]. I use no iDRAC card, only the basic BMC. I have successfully configured IPMI interface, and SOL works as expected. The problem I have is to configure properly the XCP: it displays output on serial console, but misses all startup messages of the services. Since the serial console is intended to be used for debugging a possible boot failure, those startup messages are critical. I have configured: - Edited /boot/extlinux.conf to send output the serial console, - Made inttab to use serial as console (Wiki suggests using agetty instead of getty, don't know how relevant this might be): T0:2345:respawn:/sbin/getty -L ttyS1 115200 vt100 - Added 'ttyS1' to /etc/securetty (not sure if really needed). After I connect to SOL and power on the server, I can see Syslinux's boot prompt, then Xen's boot messages and the kernels's boot messages, except the end of them. Then, after some notable delay, I see the login prompt. This is the very end of my serial console's output: [ 9.459950] usb 1-1.6: new high speed USB device using ehci_hcd and address 3 [ 9.570903] usb 1-1.6: configuration #1 chosen from 1 choice [ 9.571265] hub 1-1.6:1.0: USB hub found [ 9.571562] hub 1-1.6:1.0: 6 ports detected [ 9.870053] usb 1-1.6.1: new high speed USB device using ehci_hcd and address 4 [ 9.990896] u[ 20.637067] kjournald starting. Commit interval 15 seconds [ 20.637083] EXT3-fs: mounted filesystem with ordered data mode. Xen.org XCP Host 1.6.10-61809c [...Your XCP Host has now finished booting, IP, SSL fingerpint, etc...] xcp-node23 login: (Note the incomplete line at 9.990896, that's also an issue) Watching the boot process on a monitor, I have noticed that around message at 20.637083 the VGA console's resolution changes to something like 135x43, and immediately changes back to 80x25. Can't say if it switches to FB mode, probably not. After the switching, I see service startup messages, and finally it displays XCP's curses interface. When I shutdown the server, I see Xen's messages but not the usual "Broadcast message [...] The system is going down". This is my /boot/extlinux.conf, I added serial console and cut splash screen, framebuffer modes and "quiet" options: # location mbr serial 1 115200 default xe prompt 1 timeout 50 label xe # append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc console=hvc0 console=tty0 console=ttyS1,115200n8 --- /boot/initrd-2.6-xen.img kernel mboot.c32 append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc console=hvc0 console=tty0 --- /boot/initrd-2.6-xen.img A Citrix KB article [2] (applies to XenServer 5.5-6.1.0) suggests to set up serial console only in the boot loader, and only to for the hypervisor itself. No kernel parameters alteration. Does not mentions inittab or securetty. Another KB article [3], which applies up to XenServer 6.0, suggests to configure serial console to hypervisor itself AND the kernel. I have tested that, with no noticeable changes. The kernel's parameters seems to be unnecessary, since Xen splits pretty well the console output, sending a copy to tty and ttyS1. I have also learned [4], that Dell's "Redirection [console to serial] After Boot" BIOS option might interfere with that, so I left it disabled expecting a more "standard" behavior. Reference: [1] http://wiki.xen.org/wiki/Xen_Serial_Console [2] http://support.citrix.com/article/CTX121442 [3] http://support.citrix.com/article/CTX131909 [4] http://wiki.nikhef.nl/grid/Serial_Consoles Thank you. -- Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 16 20:15:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 16 Jan 2013 20:15:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvZO0-0005oo-Hr; Wed, 16 Jan 2013 20:15:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvZNz-0005oj-AK for xen-api@lists.xen.org; Wed, 16 Jan 2013 20:14:59 +0000 Received: from [85.158.138.51:58862] by server-2.bemta-3.messagelabs.com id EE/6B-26461-24A07F05; Wed, 16 Jan 2013 20:14:58 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1358367296!27379664!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8782 invoked from network); 16 Jan 2013 20:14:57 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-2.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Jan 2013 20:14:57 -0000 Received: from [201.122.115.101] (port=60785 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TvZNv-0007PY-Lp for xen-api@lists.xen.org; Wed, 16 Jan 2013 14:14:55 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 1CEB0A209 for ; Wed, 16 Jan 2013 14:11:46 -0600 (CST) Message-ID: <50F70A3E.3060908@ondore.com> Date: Wed, 16 Jan 2013 14:14:54 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: [Xen-API] XCP 1.6 Serial console with IPMI SOL X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. I'm setting up some Dell PowerEdge R320 servers, to have access to serial console. The serial port itself is a internal port, visible as COM2 or ttyS1 to the OS, mapped to a integrated BMC card and accessible via IPMI SOL. My general guide has been Xen Serial Console wiki article [1]. I use no iDRAC card, only the basic BMC. I have successfully configured IPMI interface, and SOL works as expected. The problem I have is to configure properly the XCP: it displays output on serial console, but misses all startup messages of the services. Since the serial console is intended to be used for debugging a possible boot failure, those startup messages are critical. I have configured: - Edited /boot/extlinux.conf to send output the serial console, - Made inttab to use serial as console (Wiki suggests using agetty instead of getty, don't know how relevant this might be): T0:2345:respawn:/sbin/getty -L ttyS1 115200 vt100 - Added 'ttyS1' to /etc/securetty (not sure if really needed). After I connect to SOL and power on the server, I can see Syslinux's boot prompt, then Xen's boot messages and the kernels's boot messages, except the end of them. Then, after some notable delay, I see the login prompt. This is the very end of my serial console's output: [ 9.459950] usb 1-1.6: new high speed USB device using ehci_hcd and address 3 [ 9.570903] usb 1-1.6: configuration #1 chosen from 1 choice [ 9.571265] hub 1-1.6:1.0: USB hub found [ 9.571562] hub 1-1.6:1.0: 6 ports detected [ 9.870053] usb 1-1.6.1: new high speed USB device using ehci_hcd and address 4 [ 9.990896] u[ 20.637067] kjournald starting. Commit interval 15 seconds [ 20.637083] EXT3-fs: mounted filesystem with ordered data mode. Xen.org XCP Host 1.6.10-61809c [...Your XCP Host has now finished booting, IP, SSL fingerpint, etc...] xcp-node23 login: (Note the incomplete line at 9.990896, that's also an issue) Watching the boot process on a monitor, I have noticed that around message at 20.637083 the VGA console's resolution changes to something like 135x43, and immediately changes back to 80x25. Can't say if it switches to FB mode, probably not. After the switching, I see service startup messages, and finally it displays XCP's curses interface. When I shutdown the server, I see Xen's messages but not the usual "Broadcast message [...] The system is going down". This is my /boot/extlinux.conf, I added serial console and cut splash screen, framebuffer modes and "quiet" options: # location mbr serial 1 115200 default xe prompt 1 timeout 50 label xe # append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc console=hvc0 console=tty0 console=ttyS1,115200n8 --- /boot/initrd-2.6-xen.img kernel mboot.c32 append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc console=hvc0 console=tty0 --- /boot/initrd-2.6-xen.img A Citrix KB article [2] (applies to XenServer 5.5-6.1.0) suggests to set up serial console only in the boot loader, and only to for the hypervisor itself. No kernel parameters alteration. Does not mentions inittab or securetty. Another KB article [3], which applies up to XenServer 6.0, suggests to configure serial console to hypervisor itself AND the kernel. I have tested that, with no noticeable changes. The kernel's parameters seems to be unnecessary, since Xen splits pretty well the console output, sending a copy to tty and ttyS1. I have also learned [4], that Dell's "Redirection [console to serial] After Boot" BIOS option might interfere with that, so I left it disabled expecting a more "standard" behavior. Reference: [1] http://wiki.xen.org/wiki/Xen_Serial_Console [2] http://support.citrix.com/article/CTX121442 [3] http://support.citrix.com/article/CTX131909 [4] http://wiki.nikhef.nl/grid/Serial_Consoles Thank you. -- Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 08:48:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 08:48:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvl9P-0002wG-C5; Thu, 17 Jan 2013 08:48:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvl9N-0002w5-Bk; Thu, 17 Jan 2013 08:48:41 +0000 Received: from [85.158.143.35:56565] by server-3.bemta-4.messagelabs.com id F2/AD-19220-8EAB7F05; Thu, 17 Jan 2013 08:48:40 +0000 X-Env-Sender: raistlin@linux.it X-Msg-Ref: server-3.tower-21.messagelabs.com!1358412512!13686594!1 X-Originating-IP: [193.205.80.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1799 invoked from network); 17 Jan 2013 08:48:38 -0000 Received: from ms01.sssup.it (HELO sssup.it) (193.205.80.99) by server-3.tower-21.messagelabs.com with SMTP; 17 Jan 2013 08:48:38 -0000 Received: from [213.136.143.201] (account d.faggioli@sssup.it HELO [192.168.0.20]) by sssup.it (CommuniGate Pro SMTP 5.3.14) with ESMTPSA id 77902708; Thu, 17 Jan 2013 09:48:29 +0100 Message-ID: <1358412477.16718.132.camel@Abyss> From: Dario Faggioli To: lars.kurth@xen.org Date: Thu, 17 Jan 2013 09:47:57 +0100 In-Reply-To: <50F044C3.7010400@xen.org> References: <50F044C3.7010400@xen.org> X-Mailer: Evolution 3.2.3 (3.2.3-3.fc16) Mime-Version: 1.0 Cc: xen-arm@lists.xen.org, Amir M Chaudhry , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [XenARM] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2034322440665798570==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2034322440665798570== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-VEocsA7sFpezBIgRY19d" --=-VEocsA7sFpezBIgRY19d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote:=20 > Hi everybody, >=20 > this e-mail is to let you know that the OpenMirage project is seeking to= =20 > become a > Xen.org hosted project. >=20 This looks really interesting. I'm all for it. Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-VEocsA7sFpezBIgRY19d Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iEYEABECAAYFAlD3ur0ACgkQk4XaBE3IOsR8LQCfYVvHQGW9n/+GjGBxNSmLiPrP 40wAn3gdffJ1Es2huXdHXn4tkh5N/HFM =EtQP -----END PGP SIGNATURE----- --=-VEocsA7sFpezBIgRY19d-- --===============2034322440665798570== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2034322440665798570==-- From xen-api-bounces@lists.xen.org Thu Jan 17 08:48:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 08:48:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvl9P-0002wG-C5; Thu, 17 Jan 2013 08:48:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvl9N-0002w5-Bk; Thu, 17 Jan 2013 08:48:41 +0000 Received: from [85.158.143.35:56565] by server-3.bemta-4.messagelabs.com id F2/AD-19220-8EAB7F05; Thu, 17 Jan 2013 08:48:40 +0000 X-Env-Sender: raistlin@linux.it X-Msg-Ref: server-3.tower-21.messagelabs.com!1358412512!13686594!1 X-Originating-IP: [193.205.80.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1799 invoked from network); 17 Jan 2013 08:48:38 -0000 Received: from ms01.sssup.it (HELO sssup.it) (193.205.80.99) by server-3.tower-21.messagelabs.com with SMTP; 17 Jan 2013 08:48:38 -0000 Received: from [213.136.143.201] (account d.faggioli@sssup.it HELO [192.168.0.20]) by sssup.it (CommuniGate Pro SMTP 5.3.14) with ESMTPSA id 77902708; Thu, 17 Jan 2013 09:48:29 +0100 Message-ID: <1358412477.16718.132.camel@Abyss> From: Dario Faggioli To: lars.kurth@xen.org Date: Thu, 17 Jan 2013 09:47:57 +0100 In-Reply-To: <50F044C3.7010400@xen.org> References: <50F044C3.7010400@xen.org> X-Mailer: Evolution 3.2.3 (3.2.3-3.fc16) Mime-Version: 1.0 Cc: xen-arm@lists.xen.org, Amir M Chaudhry , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [XenARM] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2034322440665798570==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2034322440665798570== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-VEocsA7sFpezBIgRY19d" --=-VEocsA7sFpezBIgRY19d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote:=20 > Hi everybody, >=20 > this e-mail is to let you know that the OpenMirage project is seeking to= =20 > become a > Xen.org hosted project. >=20 This looks really interesting. I'm all for it. Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-VEocsA7sFpezBIgRY19d Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iEYEABECAAYFAlD3ur0ACgkQk4XaBE3IOsR8LQCfYVvHQGW9n/+GjGBxNSmLiPrP 40wAn3gdffJ1Es2huXdHXn4tkh5N/HFM =EtQP -----END PGP SIGNATURE----- --=-VEocsA7sFpezBIgRY19d-- --===============2034322440665798570== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2034322440665798570==-- From xen-api-bounces@lists.xen.org Thu Jan 17 10:07:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 10:07:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvmNO-0007Cq-Jd; Thu, 17 Jan 2013 10:07:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvmNM-0007Cd-LT; Thu, 17 Jan 2013 10:07:12 +0000 Received: from [85.158.139.83:50261] by server-16.bemta-5.messagelabs.com id 50/D9-22111-F4DC7F05; Thu, 17 Jan 2013 10:07:11 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1358417228!25525356!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14872 invoked from network); 17 Jan 2013 10:07:09 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 10:07:09 -0000 Received: by mail-lb0-f173.google.com with SMTP id gf7so867395lbb.4 for ; Thu, 17 Jan 2013 02:07:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZwUaJ62aMZwS1BF/MTlq2WvyX+vY4LpJdvEw8yoHvXg=; b=j20XZ4Z3VVgm0IYAlafCPTSAeR15jUmYrtEKhv46ywIO9ZQ1TahuXUJeLmIV60AbTw LSUqsWnZy9Vi+TsMDjpBXrREVqeZG/bwElhMmMin0sdeRigRM6Gl3UB0AGWKPeYSWPo0 MLwConNJM7jgxw+wiK0QUWPpiXFef50Aff1nYA6rtKgkIQxOYOCWYmDB0xkwylhjEBBn 1XI3EKfQQp9SbRjMtoqP+awv1aQf0zLdPek49BsPtc3g05oDM2lqPcwPb2Dj2UDak39l Ze5SLZJ6/HyXX/cnPNt5CRAdEfTWFIIPc43LJEedZAbShQrt1cKHhJJ54uXtpFmEJdBn Zg7g== X-Received: by 10.112.82.136 with SMTP id i8mr1924742lby.74.1358417228270; Thu, 17 Jan 2013 02:07:08 -0800 (PST) Received: from [172.16.26.11] (b0fb48e2.bb.sky.com. [176.251.72.226]) by mx.google.com with ESMTPS id s9sm493055lbc.12.2013.01.17.02.07.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jan 2013 02:07:07 -0800 (PST) Message-ID: <50F7CD1F.7020207@xen.org> Date: Thu, 17 Jan 2013 10:06:23 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , Anil Madhavapeddy , Amir M Chaudhry References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> In-Reply-To: <20130116171723.GB15900@frosties> Subject: Re: [Xen-API] [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Goswin, I posted on all three xen.org developer lists, as I always do for governance related items. However, I remember a conversation with Anil the project lead stating that he follows the Xen ARM work and that this is of interest to Mirage. I will let Anil respond. Whether it works on ARM now is a different question. Maybe we should add a paragragraph related to ARM to the project proposal to clarify. Best Regards Lars On 16/01/2013 17:17, Goswin von Brederlow wrote: > On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: >> On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: >>> this e-mail is to let you know that the OpenMirage project is seeking to >>> become a Xen.org hosted project. >> Mirage is cool stuff. >> >> I'm all for this, FWIW. >> >> Ian. > Mirage is cool indeed. Only used it on x86 though. > > Since I got this mail via the xen-arm ML does that mean mirage supports > xen-arm too? > > MfG > Goswin > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 10:07:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 10:07:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvmNO-0007Cq-Jd; Thu, 17 Jan 2013 10:07:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvmNM-0007Cd-LT; Thu, 17 Jan 2013 10:07:12 +0000 Received: from [85.158.139.83:50261] by server-16.bemta-5.messagelabs.com id 50/D9-22111-F4DC7F05; Thu, 17 Jan 2013 10:07:11 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1358417228!25525356!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14872 invoked from network); 17 Jan 2013 10:07:09 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 10:07:09 -0000 Received: by mail-lb0-f173.google.com with SMTP id gf7so867395lbb.4 for ; Thu, 17 Jan 2013 02:07:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZwUaJ62aMZwS1BF/MTlq2WvyX+vY4LpJdvEw8yoHvXg=; b=j20XZ4Z3VVgm0IYAlafCPTSAeR15jUmYrtEKhv46ywIO9ZQ1TahuXUJeLmIV60AbTw LSUqsWnZy9Vi+TsMDjpBXrREVqeZG/bwElhMmMin0sdeRigRM6Gl3UB0AGWKPeYSWPo0 MLwConNJM7jgxw+wiK0QUWPpiXFef50Aff1nYA6rtKgkIQxOYOCWYmDB0xkwylhjEBBn 1XI3EKfQQp9SbRjMtoqP+awv1aQf0zLdPek49BsPtc3g05oDM2lqPcwPb2Dj2UDak39l Ze5SLZJ6/HyXX/cnPNt5CRAdEfTWFIIPc43LJEedZAbShQrt1cKHhJJ54uXtpFmEJdBn Zg7g== X-Received: by 10.112.82.136 with SMTP id i8mr1924742lby.74.1358417228270; Thu, 17 Jan 2013 02:07:08 -0800 (PST) Received: from [172.16.26.11] (b0fb48e2.bb.sky.com. [176.251.72.226]) by mx.google.com with ESMTPS id s9sm493055lbc.12.2013.01.17.02.07.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jan 2013 02:07:07 -0800 (PST) Message-ID: <50F7CD1F.7020207@xen.org> Date: Thu, 17 Jan 2013 10:06:23 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , Anil Madhavapeddy , Amir M Chaudhry References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> In-Reply-To: <20130116171723.GB15900@frosties> Subject: Re: [Xen-API] [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Goswin, I posted on all three xen.org developer lists, as I always do for governance related items. However, I remember a conversation with Anil the project lead stating that he follows the Xen ARM work and that this is of interest to Mirage. I will let Anil respond. Whether it works on ARM now is a different question. Maybe we should add a paragragraph related to ARM to the project proposal to clarify. Best Regards Lars On 16/01/2013 17:17, Goswin von Brederlow wrote: > On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: >> On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: >>> this e-mail is to let you know that the OpenMirage project is seeking to >>> become a Xen.org hosted project. >> Mirage is cool stuff. >> >> I'm all for this, FWIW. >> >> Ian. > Mirage is cool indeed. Only used it on x86 though. > > Since I got this mail via the xen-arm ML does that mean mirage supports > xen-arm too? > > MfG > Goswin > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 11:15:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 11:15:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvnQp-0001bx-48; Thu, 17 Jan 2013 11:14:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvnQo-0001bs-0K for xen-api@lists.xen.org; Thu, 17 Jan 2013 11:14:50 +0000 Received: from [85.158.143.35:5515] by server-3.bemta-4.messagelabs.com id 66/99-19220-92DD7F05; Thu, 17 Jan 2013 11:14:49 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1358421288!14791926!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2OTgz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9911 invoked from network); 17 Jan 2013 11:14:48 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 11:14:48 -0000 X-IronPort-AV: E=Sophos;i="4.84,484,1355097600"; d="scan'208";a="719357" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Jan 2013 11:14:48 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 17 Jan 2013 11:14:48 +0000 From: James Bulpin To: Alexandre Kouznetsov , "xen-api@lists.xen.org" Date: Thu, 17 Jan 2013 11:15:34 +0000 Thread-Topic: [Xen-API] XCP 1.6 Serial console with IPMI SOL Thread-Index: Ac30JoO/t+P8c/ysSSa8zTDO/uAYRAAfN8gw Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E896531@LONPMAILBOX01.citrite.net> References: <50F70A3E.3060908@ondore.com> In-Reply-To: <50F70A3E.3060908@ondore.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 Serial console with IPMI SOL X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Alexandre, > append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M > watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M > crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 > --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc > console=hvc0 console=tty0 --- /boot/initrd-2.6-xen.img Try reversing the order of the two console= args in the kernel command line. Linux uses the rightmost of these for /dev/console, i.e. you want the hvc0 one last. My box (it's XS 6.0.2 so other args will differ - ignore these) has: label xe-serial # XenServer (Serial) kernel mboot.c32 append /boot/xen.gz com1=115200,8n1 console=com1,vga mem=1024G dom0_max_vcpus=4 dom0_mem=752M lowmem_emergency_pool=1M crashkernel=64M@32M --- /boot/vmlinuz-2.6-xen root=LABEL=root-lpnwoiab ro console=tty0 xencons=hvc console=hvc0 --- /boot/initrd-2.6-xen.img Regards, James > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Alexandre Kouznetsov > Sent: 16 January 2013 20:15 > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6 Serial console with IPMI SOL > > Hello. > > I'm setting up some Dell PowerEdge R320 servers, to have access to > serial console. The serial port itself is a internal port, visible as > COM2 or ttyS1 to the OS, mapped to a integrated BMC card and accessible > via IPMI SOL. My general guide has been Xen Serial Console wiki article > [1]. I use no iDRAC card, only the basic BMC. > > I have successfully configured IPMI interface, and SOL works as > expected. The problem I have is to configure properly the XCP: it > displays output on serial console, but misses all startup messages of > the services. Since the serial console is intended to be used for > debugging a possible boot failure, those startup messages are critical. > > > I have configured: > - Edited /boot/extlinux.conf to send output the serial console, > - Made inttab to use serial as console (Wiki suggests using agetty > instead of getty, don't know how relevant this might be): > T0:2345:respawn:/sbin/getty -L ttyS1 115200 vt100 > - Added 'ttyS1' to /etc/securetty (not sure if really needed). > > After I connect to SOL and power on the server, I can see Syslinux's > boot prompt, then Xen's boot messages and the kernels's boot messages, > except the end of them. Then, after some notable delay, I see the login > prompt. This is the very end of my serial console's output: > > [ 9.459950] usb 1-1.6: new high speed USB device using ehci_hcd and > address 3 > [ 9.570903] usb 1-1.6: configuration #1 chosen from 1 choice > [ 9.571265] hub 1-1.6:1.0: USB hub found > [ 9.571562] hub 1-1.6:1.0: 6 ports detected > [ 9.870053] usb 1-1.6.1: new high speed USB device using ehci_hcd > and > address 4 > [ 9.990896] u[ 20.637067] kjournald starting. Commit interval 15 > seconds > [ 20.637083] EXT3-fs: mounted filesystem with ordered data mode. > > Xen.org XCP Host 1.6.10-61809c > [...Your XCP Host has now finished booting, IP, SSL fingerpint, etc...] > xcp-node23 login: > > (Note the incomplete line at 9.990896, that's also an issue) > > Watching the boot process on a monitor, I have noticed that around > message at 20.637083 the VGA console's resolution changes to something > like 135x43, and immediately changes back to 80x25. Can't say if it > switches to FB mode, probably not. After the switching, I see service > startup messages, and finally it displays XCP's curses interface. > > When I shutdown the server, I see Xen's messages but not the usual > "Broadcast message [...] The system is going down". > > > This is my /boot/extlinux.conf, I added serial console and cut splash > screen, framebuffer modes and "quiet" options: > > # location mbr > serial 1 115200 > default xe > prompt 1 > timeout 50 > > label xe > # append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M > watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M > crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 > --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc > console=hvc0 console=tty0 console=ttyS1,115200n8 --- > /boot/initrd-2.6-xen.img > kernel mboot.c32 > append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M > watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M > crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 > --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc > console=hvc0 console=tty0 --- /boot/initrd-2.6-xen.img > > > A Citrix KB article [2] (applies to XenServer 5.5-6.1.0) suggests to > set > up serial console only in the boot loader, and only to for the > hypervisor itself. No kernel parameters alteration. Does not mentions > inittab or securetty. > > Another KB article [3], which applies up to XenServer 6.0, suggests to > configure serial console to hypervisor itself AND the kernel. I have > tested that, with no noticeable changes. The kernel's parameters seems > to be unnecessary, since Xen splits pretty well the console output, > sending a copy to tty and ttyS1. > > I have also learned [4], that Dell's "Redirection [console to serial] > After Boot" BIOS option might interfere with that, so I left it > disabled > expecting a more "standard" behavior. > > Reference: > [1] http://wiki.xen.org/wiki/Xen_Serial_Console > [2] http://support.citrix.com/article/CTX121442 > [3] http://support.citrix.com/article/CTX131909 > [4] http://wiki.nikhef.nl/grid/Serial_Consoles > > Thank you. > > -- > Alexandre Kouznetsov > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 11:15:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 11:15:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvnQp-0001bx-48; Thu, 17 Jan 2013 11:14:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvnQo-0001bs-0K for xen-api@lists.xen.org; Thu, 17 Jan 2013 11:14:50 +0000 Received: from [85.158.143.35:5515] by server-3.bemta-4.messagelabs.com id 66/99-19220-92DD7F05; Thu, 17 Jan 2013 11:14:49 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1358421288!14791926!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2OTgz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9911 invoked from network); 17 Jan 2013 11:14:48 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 11:14:48 -0000 X-IronPort-AV: E=Sophos;i="4.84,484,1355097600"; d="scan'208";a="719357" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Jan 2013 11:14:48 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 17 Jan 2013 11:14:48 +0000 From: James Bulpin To: Alexandre Kouznetsov , "xen-api@lists.xen.org" Date: Thu, 17 Jan 2013 11:15:34 +0000 Thread-Topic: [Xen-API] XCP 1.6 Serial console with IPMI SOL Thread-Index: Ac30JoO/t+P8c/ysSSa8zTDO/uAYRAAfN8gw Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E896531@LONPMAILBOX01.citrite.net> References: <50F70A3E.3060908@ondore.com> In-Reply-To: <50F70A3E.3060908@ondore.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.6 Serial console with IPMI SOL X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Alexandre, > append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M > watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M > crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 > --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc > console=hvc0 console=tty0 --- /boot/initrd-2.6-xen.img Try reversing the order of the two console= args in the kernel command line. Linux uses the rightmost of these for /dev/console, i.e. you want the hvc0 one last. My box (it's XS 6.0.2 so other args will differ - ignore these) has: label xe-serial # XenServer (Serial) kernel mboot.c32 append /boot/xen.gz com1=115200,8n1 console=com1,vga mem=1024G dom0_max_vcpus=4 dom0_mem=752M lowmem_emergency_pool=1M crashkernel=64M@32M --- /boot/vmlinuz-2.6-xen root=LABEL=root-lpnwoiab ro console=tty0 xencons=hvc console=hvc0 --- /boot/initrd-2.6-xen.img Regards, James > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Alexandre Kouznetsov > Sent: 16 January 2013 20:15 > To: xen-api@lists.xen.org > Subject: [Xen-API] XCP 1.6 Serial console with IPMI SOL > > Hello. > > I'm setting up some Dell PowerEdge R320 servers, to have access to > serial console. The serial port itself is a internal port, visible as > COM2 or ttyS1 to the OS, mapped to a integrated BMC card and accessible > via IPMI SOL. My general guide has been Xen Serial Console wiki article > [1]. I use no iDRAC card, only the basic BMC. > > I have successfully configured IPMI interface, and SOL works as > expected. The problem I have is to configure properly the XCP: it > displays output on serial console, but misses all startup messages of > the services. Since the serial console is intended to be used for > debugging a possible boot failure, those startup messages are critical. > > > I have configured: > - Edited /boot/extlinux.conf to send output the serial console, > - Made inttab to use serial as console (Wiki suggests using agetty > instead of getty, don't know how relevant this might be): > T0:2345:respawn:/sbin/getty -L ttyS1 115200 vt100 > - Added 'ttyS1' to /etc/securetty (not sure if really needed). > > After I connect to SOL and power on the server, I can see Syslinux's > boot prompt, then Xen's boot messages and the kernels's boot messages, > except the end of them. Then, after some notable delay, I see the login > prompt. This is the very end of my serial console's output: > > [ 9.459950] usb 1-1.6: new high speed USB device using ehci_hcd and > address 3 > [ 9.570903] usb 1-1.6: configuration #1 chosen from 1 choice > [ 9.571265] hub 1-1.6:1.0: USB hub found > [ 9.571562] hub 1-1.6:1.0: 6 ports detected > [ 9.870053] usb 1-1.6.1: new high speed USB device using ehci_hcd > and > address 4 > [ 9.990896] u[ 20.637067] kjournald starting. Commit interval 15 > seconds > [ 20.637083] EXT3-fs: mounted filesystem with ordered data mode. > > Xen.org XCP Host 1.6.10-61809c > [...Your XCP Host has now finished booting, IP, SSL fingerpint, etc...] > xcp-node23 login: > > (Note the incomplete line at 9.990896, that's also an issue) > > Watching the boot process on a monitor, I have noticed that around > message at 20.637083 the VGA console's resolution changes to something > like 135x43, and immediately changes back to 80x25. Can't say if it > switches to FB mode, probably not. After the switching, I see service > startup messages, and finally it displays XCP's curses interface. > > When I shutdown the server, I see Xen's messages but not the usual > "Broadcast message [...] The system is going down". > > > This is my /boot/extlinux.conf, I added serial console and cut splash > screen, framebuffer modes and "quiet" options: > > # location mbr > serial 1 115200 > default xe > prompt 1 > timeout 50 > > label xe > # append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M > watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M > crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 > --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc > console=hvc0 console=tty0 console=ttyS1,115200n8 --- > /boot/initrd-2.6-xen.img > kernel mboot.c32 > append /boot/xen.gz mem=1024G dom0_mem=752M,max:752M > watchdog_timeout=300 cpuid_mask_xsave_eax=0 lowmem_emergency_pool=1M > crashkernel=64M@32M com2=115200,8n1 console=com2,vga dom0_max_vcpus=1-4 > --- /boot/vmlinuz-2.6-xen root=LABEL=root-vskolivp ro xencons=hvc > console=hvc0 console=tty0 --- /boot/initrd-2.6-xen.img > > > A Citrix KB article [2] (applies to XenServer 5.5-6.1.0) suggests to > set > up serial console only in the boot loader, and only to for the > hypervisor itself. No kernel parameters alteration. Does not mentions > inittab or securetty. > > Another KB article [3], which applies up to XenServer 6.0, suggests to > configure serial console to hypervisor itself AND the kernel. I have > tested that, with no noticeable changes. The kernel's parameters seems > to be unnecessary, since Xen splits pretty well the console output, > sending a copy to tty and ttyS1. > > I have also learned [4], that Dell's "Redirection [console to serial] > After Boot" BIOS option might interfere with that, so I left it > disabled > expecting a more "standard" behavior. > > Reference: > [1] http://wiki.xen.org/wiki/Xen_Serial_Console > [2] http://support.citrix.com/article/CTX121442 > [3] http://support.citrix.com/article/CTX131909 > [4] http://wiki.nikhef.nl/grid/Serial_Consoles > > Thank you. > > -- > Alexandre Kouznetsov > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 12:33:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:33:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvoeP-0007qD-IR; Thu, 17 Jan 2013 12:32:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv2Zy-0004nG-8c for xen-api@lists.xen.org; Tue, 15 Jan 2013 09:13:10 +0000 Received: from [85.158.138.51:52494] by server-13.bemta-3.messagelabs.com id 62/47-00465-F9D15F05; Tue, 15 Jan 2013 09:13:03 +0000 X-Env-Sender: Anatoliy.Poloz@onetelecom.od.ua X-Msg-Ref: server-16.tower-174.messagelabs.com!1358241182!27926629!1 X-Originating-IP: [91.194.72.4] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29704 invoked from network); 15 Jan 2013 09:13:02 -0000 Received: from mail.onetelecom.od.ua (HELO main.merlin.com.ua) (91.194.72.4) by server-16.tower-174.messagelabs.com with SMTP; 15 Jan 2013 09:13:02 -0000 Received: from [192.168.67.100] (unknown [192.168.67.100]) by main.merlin.com.ua (Postmaster) with ESMTP id 42B125F3C2C for ; Tue, 15 Jan 2013 11:13:02 +0200 (EET) Message-ID: <50F51D97.9020604@onetelecom.od.ua> Date: Tue, 15 Jan 2013 11:12:55 +0200 From: "Anatoliy.Poloz" User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org X-Mailman-Approved-At: Thu, 17 Jan 2013 12:32:56 +0000 Subject: [Xen-API] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Anatoliy.Poloz@onetelecom.od.ua List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I tried to import a previously saved VM with the command "#xe vm-import filename = / var/run/sr-mount/c0da11ed-72d8-1a58-aa94-127035fa28d7/infr-samba-2013-01-02_01-04-01.xva sr-uuid = c0da11ed-72d8-1a58-aa94-127035fa28d7 force=true" c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr the size of imported file 123G but failed with message "Fatal error: exception Unix.Unix_error(13, "tcsetattr", "")" and hung task uuid ( RO) : be568259-c9cd-be13-7da5-8ed2a222e898 name-label ( RO): VM import name-description ( RO): status ( RO): pending progress ( RO): 0.720 is there any chance to recover VM? -- //wbr Anatoliy Poloz _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 12:33:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:33:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvoeP-0007qD-IR; Thu, 17 Jan 2013 12:32:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv2Zy-0004nG-8c for xen-api@lists.xen.org; Tue, 15 Jan 2013 09:13:10 +0000 Received: from [85.158.138.51:52494] by server-13.bemta-3.messagelabs.com id 62/47-00465-F9D15F05; Tue, 15 Jan 2013 09:13:03 +0000 X-Env-Sender: Anatoliy.Poloz@onetelecom.od.ua X-Msg-Ref: server-16.tower-174.messagelabs.com!1358241182!27926629!1 X-Originating-IP: [91.194.72.4] X-SpamReason: No, hits=1.8 required=7.0 tests=RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29704 invoked from network); 15 Jan 2013 09:13:02 -0000 Received: from mail.onetelecom.od.ua (HELO main.merlin.com.ua) (91.194.72.4) by server-16.tower-174.messagelabs.com with SMTP; 15 Jan 2013 09:13:02 -0000 Received: from [192.168.67.100] (unknown [192.168.67.100]) by main.merlin.com.ua (Postmaster) with ESMTP id 42B125F3C2C for ; Tue, 15 Jan 2013 11:13:02 +0200 (EET) Message-ID: <50F51D97.9020604@onetelecom.od.ua> Date: Tue, 15 Jan 2013 11:12:55 +0200 From: "Anatoliy.Poloz" User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-api@lists.xen.org X-Mailman-Approved-At: Thu, 17 Jan 2013 12:32:56 +0000 Subject: [Xen-API] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Anatoliy.Poloz@onetelecom.od.ua List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I tried to import a previously saved VM with the command "#xe vm-import filename = / var/run/sr-mount/c0da11ed-72d8-1a58-aa94-127035fa28d7/infr-samba-2013-01-02_01-04-01.xva sr-uuid = c0da11ed-72d8-1a58-aa94-127035fa28d7 force=true" c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr the size of imported file 123G but failed with message "Fatal error: exception Unix.Unix_error(13, "tcsetattr", "")" and hung task uuid ( RO) : be568259-c9cd-be13-7da5-8ed2a222e898 name-label ( RO): VM import name-description ( RO): status ( RO): pending progress ( RO): 0.720 is there any chance to recover VM? -- //wbr Anatoliy Poloz _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 12:33:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:33:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvoeP-0007qI-NU; Thu, 17 Jan 2013 12:32:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvVwX-0003Q1-0v; Wed, 16 Jan 2013 16:34:25 +0000 Received: from [85.158.143.99:43264] by server-2.bemta-4.messagelabs.com id 05/FF-24322-096D6F05; Wed, 16 Jan 2013 16:34:24 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1358354061!18582792!1 X-Originating-IP: [209.85.220.176] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19342 invoked from network); 16 Jan 2013 16:34:22 -0000 Received: from mail-vc0-f176.google.com (HELO mail-vc0-f176.google.com) (209.85.220.176) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 16:34:22 -0000 Received: by mail-vc0-f176.google.com with SMTP id fo13so1506126vcb.21 for ; Wed, 16 Jan 2013 08:34:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=va0uZwd2TBDwrRML2W6XFyqEmvYJWn+EnxhH5bk5cOY=; b=i8hfiyF7xk3VFQ/5RNlYtxgfObrnp8aQhJJnvphgdM3j8/hRSRT3GWybxi+Wn8IdO1 hKPssCqPL2AwSUwbF5Rf5QZiEpuvj8vQrOU391OHlYV2qf4L5I1NnPYuKq2hcC5DqfO+ tykjUu4nE7HFDqOYiWU1wP9WAHnW5LqSb5EwZRnR9Oxp8b82Xc2vxjG6PmvBp9bpQZ3W zDIrnysB0L+eFxTJU1VsK0uBzUU2i38R1Urxbm4jzM4y9tP3SNslOyrE9bNSU2mOCy+1 ulJt9xxuieToa965fkUUDf55er9D4zePqFzNkjscTRn7DYcQ/4hl//8P9Kr3GT/t9le9 C87A== MIME-Version: 1.0 X-Received: by 10.221.10.6 with SMTP id oy6mr1794584vcb.65.1358354061316; Wed, 16 Jan 2013 08:34:21 -0800 (PST) Received: by 10.58.54.39 with HTTP; Wed, 16 Jan 2013 08:34:21 -0800 (PST) In-Reply-To: <50F044C3.7010400@xen.org> References: <50F044C3.7010400@xen.org> Date: Wed, 16 Jan 2013 16:34:21 +0000 X-Google-Sender-Auth: LUVZklj7zYlCYLxoD-d4ub9HJxg Message-ID: From: George Dunlap To: Lars Kurth X-Mailman-Approved-At: Thu, 17 Jan 2013 12:32:56 +0000 Cc: xen-arm@lists.xen.org, Amir M Chaudhry , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2059523894485590016==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2059523894485590016== Content-Type: multipart/alternative; boundary=bcaec54eed364dd42804d36a73ff --bcaec54eed364dd42804d36a73ff Content-Type: text/plain; charset=ISO-8859-1 +1 from me as well. -George On Fri, Jan 11, 2013 at 4:58 PM, Lars Kurth wrote: > Hi everybody, > > this e-mail is to let you know that the OpenMirage project is seeking to > become a > Xen.org hosted project. > > The prospective project lead of the Mirage Project - Anil Madhavapeddy - > has requested > a Review of the Mirage Project to become an Xen.org Incubation project. In > line with > Xen Project Governance (see http://www.xen.org/projects/**governance.html), > in particular > sections > > - "Forming a Project" at > http://www.xen.org/projects/**governance.html#project.**forming > > - "Project Proposal" at > http://www.xen.org/projects/**governance.html#project.**proposal > > - "Requesting Reviews, Reviews and Voting" at > http://www.xen.org/projects/**governance.html#project.**requests > > This is an informal community review, which will be followed by a formal > vote. > > The Proposal and Proposal Meta Information > ==============================**============ > > - Proposal Location at: > http://wiki.xen.org/wiki/**Mirage_Incubation_Project_**Proposal > > - Project Lead: Anil Madhavapeddy > - Project Sponsor: Tim Deegan > - Project Mentor: Lars Kurth > > - Deadline: review open until 24:00, 27th of Jan, 2013 (GMT) > > Following the Community Review, there may be an update to the proposal if > needed. Which is then followed by a formal vote by eligible community > members. > > Why and How to Provide Feedback > ==============================**= > - Anybody in the Community can provide feedback > > - Preferably, feedback should be provided by annotating the in-lined copy > of > the document using the instructions in the wiki. In other word insert > > "{{comment|~~~~}} your comment." > > into the document, at a suitable location in the document. > > - Alternatively you can provide feedback by replying to this e-mail > > Best Regards > Lars > > > ______________________________**_________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > --bcaec54eed364dd42804d36a73ff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
+1 from me as well.

=A0-George
=


On Fri, Jan 1= 1, 2013 at 4:58 PM, Lars Kurth <lars.kurth@xen.org> wrote:<= br>
Hi everybody,

this e-mail is to let you know that the OpenMirage project is seeking to be= come a
Xen.org hosted project.

The prospective project lead of the Mirage Project - Anil Madhavapeddy - ha= s requested
a Review of the Mirage Project to become an Xen.org Incubation project. In = line with
Xen Project Governance (see http://www.xen.org/projects/governance.ht= ml), in particular
sections

- "Forming a Project" at
=A0 =A0http://www.xen.org/projects/governance.html#pr= oject.forming

- "Project Proposal" at
=A0 =A0http://www.xen.org/projects/governance.html#p= roject.proposal

- "Requesting Reviews, Reviews and Voting" at
=A0 =A0http://www.xen.org/projects/governance.html#p= roject.requests

This is an informal community review, which will be followed by a formal vo= te.

The Proposal and Proposal Meta Information
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- Proposal Location at:
=A0 http://wiki.xen.org/wiki/Mirage_Incubation_Projec= t_Proposal

- Project Lead: Anil Madhavapeddy
- Project Sponsor: =A0 =A0 =A0Tim Deegan
- Project Mentor: =A0 =A0 =A0 Lars Kurth

- Deadline: =A0 =A0 =A0 =A0 =A0 =A0 review open until 24:00, 27th of Jan, 2= 013 (GMT)

Following the Community Review, there may be an update to the proposal if needed. Which is then followed by a formal vote by eligible community membe= rs.

Why and How to Provide Feedback
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D
- Anybody in the Community can provide feedback

- Preferably, feedback should be provided by annotating the in-lined copy o= f
=A0 the document using the instructions in the wiki. In other word insert
=A0 "{{comment|~~~~}} your comment."

=A0 into the document, at a suitable location in the document.

- Alternatively you can provide feedback by replying to this e-mail

Best Regards
Lars


_______________________________________________
Xen-devel mailing list
Xen-devel@list= s.xen.org
http://lists.x= en.org/xen-devel

--bcaec54eed364dd42804d36a73ff-- --===============2059523894485590016== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2059523894485590016==-- From xen-api-bounces@lists.xen.org Thu Jan 17 12:33:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:33:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvoeP-0007qI-NU; Thu, 17 Jan 2013 12:32:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvVwX-0003Q1-0v; Wed, 16 Jan 2013 16:34:25 +0000 Received: from [85.158.143.99:43264] by server-2.bemta-4.messagelabs.com id 05/FF-24322-096D6F05; Wed, 16 Jan 2013 16:34:24 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1358354061!18582792!1 X-Originating-IP: [209.85.220.176] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19342 invoked from network); 16 Jan 2013 16:34:22 -0000 Received: from mail-vc0-f176.google.com (HELO mail-vc0-f176.google.com) (209.85.220.176) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jan 2013 16:34:22 -0000 Received: by mail-vc0-f176.google.com with SMTP id fo13so1506126vcb.21 for ; Wed, 16 Jan 2013 08:34:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=va0uZwd2TBDwrRML2W6XFyqEmvYJWn+EnxhH5bk5cOY=; b=i8hfiyF7xk3VFQ/5RNlYtxgfObrnp8aQhJJnvphgdM3j8/hRSRT3GWybxi+Wn8IdO1 hKPssCqPL2AwSUwbF5Rf5QZiEpuvj8vQrOU391OHlYV2qf4L5I1NnPYuKq2hcC5DqfO+ tykjUu4nE7HFDqOYiWU1wP9WAHnW5LqSb5EwZRnR9Oxp8b82Xc2vxjG6PmvBp9bpQZ3W zDIrnysB0L+eFxTJU1VsK0uBzUU2i38R1Urxbm4jzM4y9tP3SNslOyrE9bNSU2mOCy+1 ulJt9xxuieToa965fkUUDf55er9D4zePqFzNkjscTRn7DYcQ/4hl//8P9Kr3GT/t9le9 C87A== MIME-Version: 1.0 X-Received: by 10.221.10.6 with SMTP id oy6mr1794584vcb.65.1358354061316; Wed, 16 Jan 2013 08:34:21 -0800 (PST) Received: by 10.58.54.39 with HTTP; Wed, 16 Jan 2013 08:34:21 -0800 (PST) In-Reply-To: <50F044C3.7010400@xen.org> References: <50F044C3.7010400@xen.org> Date: Wed, 16 Jan 2013 16:34:21 +0000 X-Google-Sender-Auth: LUVZklj7zYlCYLxoD-d4ub9HJxg Message-ID: From: George Dunlap To: Lars Kurth X-Mailman-Approved-At: Thu, 17 Jan 2013 12:32:56 +0000 Cc: xen-arm@lists.xen.org, Amir M Chaudhry , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] [Community Review] Mirage Incubation Project Proposal X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2059523894485590016==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2059523894485590016== Content-Type: multipart/alternative; boundary=bcaec54eed364dd42804d36a73ff --bcaec54eed364dd42804d36a73ff Content-Type: text/plain; charset=ISO-8859-1 +1 from me as well. -George On Fri, Jan 11, 2013 at 4:58 PM, Lars Kurth wrote: > Hi everybody, > > this e-mail is to let you know that the OpenMirage project is seeking to > become a > Xen.org hosted project. > > The prospective project lead of the Mirage Project - Anil Madhavapeddy - > has requested > a Review of the Mirage Project to become an Xen.org Incubation project. In > line with > Xen Project Governance (see http://www.xen.org/projects/**governance.html), > in particular > sections > > - "Forming a Project" at > http://www.xen.org/projects/**governance.html#project.**forming > > - "Project Proposal" at > http://www.xen.org/projects/**governance.html#project.**proposal > > - "Requesting Reviews, Reviews and Voting" at > http://www.xen.org/projects/**governance.html#project.**requests > > This is an informal community review, which will be followed by a formal > vote. > > The Proposal and Proposal Meta Information > ==============================**============ > > - Proposal Location at: > http://wiki.xen.org/wiki/**Mirage_Incubation_Project_**Proposal > > - Project Lead: Anil Madhavapeddy > - Project Sponsor: Tim Deegan > - Project Mentor: Lars Kurth > > - Deadline: review open until 24:00, 27th of Jan, 2013 (GMT) > > Following the Community Review, there may be an update to the proposal if > needed. Which is then followed by a formal vote by eligible community > members. > > Why and How to Provide Feedback > ==============================**= > - Anybody in the Community can provide feedback > > - Preferably, feedback should be provided by annotating the in-lined copy > of > the document using the instructions in the wiki. In other word insert > > "{{comment|~~~~}} your comment." > > into the document, at a suitable location in the document. > > - Alternatively you can provide feedback by replying to this e-mail > > Best Regards > Lars > > > ______________________________**_________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > --bcaec54eed364dd42804d36a73ff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
+1 from me as well.

=A0-George
=


On Fri, Jan 1= 1, 2013 at 4:58 PM, Lars Kurth <lars.kurth@xen.org> wrote:<= br>
Hi everybody,

this e-mail is to let you know that the OpenMirage project is seeking to be= come a
Xen.org hosted project.

The prospective project lead of the Mirage Project - Anil Madhavapeddy - ha= s requested
a Review of the Mirage Project to become an Xen.org Incubation project. In = line with
Xen Project Governance (see http://www.xen.org/projects/governance.ht= ml), in particular
sections

- "Forming a Project" at
=A0 =A0http://www.xen.org/projects/governance.html#pr= oject.forming

- "Project Proposal" at
=A0 =A0http://www.xen.org/projects/governance.html#p= roject.proposal

- "Requesting Reviews, Reviews and Voting" at
=A0 =A0http://www.xen.org/projects/governance.html#p= roject.requests

This is an informal community review, which will be followed by a formal vo= te.

The Proposal and Proposal Meta Information
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- Proposal Location at:
=A0 http://wiki.xen.org/wiki/Mirage_Incubation_Projec= t_Proposal

- Project Lead: Anil Madhavapeddy
- Project Sponsor: =A0 =A0 =A0Tim Deegan
- Project Mentor: =A0 =A0 =A0 Lars Kurth

- Deadline: =A0 =A0 =A0 =A0 =A0 =A0 review open until 24:00, 27th of Jan, 2= 013 (GMT)

Following the Community Review, there may be an update to the proposal if needed. Which is then followed by a formal vote by eligible community membe= rs.

Why and How to Provide Feedback
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D
- Anybody in the Community can provide feedback

- Preferably, feedback should be provided by annotating the in-lined copy o= f
=A0 the document using the instructions in the wiki. In other word insert
=A0 "{{comment|~~~~}} your comment."

=A0 into the document, at a suitable location in the document.

- Alternatively you can provide feedback by replying to this e-mail

Best Regards
Lars


_______________________________________________
Xen-devel mailing list
Xen-devel@list= s.xen.org
http://lists.x= en.org/xen-devel

--bcaec54eed364dd42804d36a73ff-- --===============2059523894485590016== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2059523894485590016==-- From xen-api-bounces@lists.xen.org Thu Jan 17 12:33:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:33:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvoeP-0007q7-Cy; Thu, 17 Jan 2013 12:32:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tujsn-0004jp-1d for xen-api@lists.xen.org; Mon, 14 Jan 2013 13:15:21 +0000 Received: from [85.158.139.83:11547] by server-15.bemta-5.messagelabs.com id 62/E5-20523-8E404F05; Mon, 14 Jan 2013 13:15:20 +0000 X-Env-Sender: netbsd@precedence.co.uk X-Msg-Ref: server-14.tower-182.messagelabs.com!1358169319!23501608!1 X-Originating-IP: [193.82.124.109] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28197 invoked from network); 14 Jan 2013 13:15:19 -0000 Received: from mail.ptlnet.com (HELO mail.ptlnet.com) (193.82.124.109) by server-14.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2013 13:15:19 -0000 Received: from precedence.co.uk (ugly.internal.precedence.co.uk [192.168.1.1]) by mail.ptlnet.com (8.14.2/8.14.2) with ESMTP id r0EDFIWb023698 for ; Mon, 14 Jan 2013 13:15:18 GMT Received: from precedence.co.uk (localhost [127.0.0.1]) by precedence.co.uk (8.14.5/8.14.2) with ESMTP id r0EDFIHf023596 for ; Mon, 14 Jan 2013 13:15:18 GMT Received: from localhost (netbsd@localhost) by precedence.co.uk (8.14.5/8.12.11/Submit) with ESMTP id r0EDFIRU002721 for ; Mon, 14 Jan 2013 13:15:18 GMT Date: Mon, 14 Jan 2013 13:15:18 +0000 (GMT) From: Stephen Borrill X-X-Sender: netbsd@ugly.internal.precedence.co.uk To: xen-api@lists.xen.org Message-ID: MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mail.ptlnet.com [192.168.10.254]); Mon, 14 Jan 2013 13:15:19 +0000 (GMT) X-Mailman-Approved-At: Thu, 17 Jan 2013 12:32:56 +0000 Subject: [Xen-API] xenstore entry for "can migrate" or "can suspend"? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I'm looking for what I need to write to xenstore from a VM to say whether or not it supports migration and/or suspension. On older versions of NetBSD, suspend/migration isn't supported and on newer versions it still has issues. Therefore I want to let the xapi toolstack, etc. not offer the option to the end user as otherwise it sits there waiting for the operation to complete which never happens. -- Stephen _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 12:33:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:33:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvoeP-0007q7-Cy; Thu, 17 Jan 2013 12:32:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tujsn-0004jp-1d for xen-api@lists.xen.org; Mon, 14 Jan 2013 13:15:21 +0000 Received: from [85.158.139.83:11547] by server-15.bemta-5.messagelabs.com id 62/E5-20523-8E404F05; Mon, 14 Jan 2013 13:15:20 +0000 X-Env-Sender: netbsd@precedence.co.uk X-Msg-Ref: server-14.tower-182.messagelabs.com!1358169319!23501608!1 X-Originating-IP: [193.82.124.109] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28197 invoked from network); 14 Jan 2013 13:15:19 -0000 Received: from mail.ptlnet.com (HELO mail.ptlnet.com) (193.82.124.109) by server-14.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2013 13:15:19 -0000 Received: from precedence.co.uk (ugly.internal.precedence.co.uk [192.168.1.1]) by mail.ptlnet.com (8.14.2/8.14.2) with ESMTP id r0EDFIWb023698 for ; Mon, 14 Jan 2013 13:15:18 GMT Received: from precedence.co.uk (localhost [127.0.0.1]) by precedence.co.uk (8.14.5/8.14.2) with ESMTP id r0EDFIHf023596 for ; Mon, 14 Jan 2013 13:15:18 GMT Received: from localhost (netbsd@localhost) by precedence.co.uk (8.14.5/8.12.11/Submit) with ESMTP id r0EDFIRU002721 for ; Mon, 14 Jan 2013 13:15:18 GMT Date: Mon, 14 Jan 2013 13:15:18 +0000 (GMT) From: Stephen Borrill X-X-Sender: netbsd@ugly.internal.precedence.co.uk To: xen-api@lists.xen.org Message-ID: MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mail.ptlnet.com [192.168.10.254]); Mon, 14 Jan 2013 13:15:19 +0000 (GMT) X-Mailman-Approved-At: Thu, 17 Jan 2013 12:32:56 +0000 Subject: [Xen-API] xenstore entry for "can migrate" or "can suspend"? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I'm looking for what I need to write to xenstore from a VM to say whether or not it supports migration and/or suspension. On older versions of NetBSD, suspend/migration isn't supported and on newer versions it still has issues. Therefore I want to let the xapi toolstack, etc. not offer the option to the end user as otherwise it sits there waiting for the operation to complete which never happens. -- Stephen _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 12:58:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:58:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp2l-0001jz-IQ; Thu, 17 Jan 2013 12:58:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp2k-0001jt-Aa for xen-api@lists.xen.org; Thu, 17 Jan 2013 12:58:06 +0000 Received: from [85.158.139.83:6630] by server-15.bemta-5.messagelabs.com id 38/8C-18817-D55F7F05; Thu, 17 Jan 2013 12:58:05 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-15.tower-182.messagelabs.com!1358427341!28184830!1 X-Originating-IP: [94.100.177.100] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 644 invoked from network); 17 Jan 2013 12:55:42 -0000 Received: from smtp40.i.mail.ru (HELO smtp40.i.mail.ru) (94.100.177.100) by server-15.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 12:55:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=4mNb+aRw3UiqPNDbJjpZ4cs18vasRbFmNRS1eIcbjvA=; b=PZlRgfyVAaC+RnHRaGYiDx21imQvwVgk04p5ELEEPFeSxmd9Lacm/67X9DmkEjkS21XhBrY3o8ZP8N6ivz2Hn3MzfQ0/OjAnL6mqFLrLwv0GHYcMIUWdjIaw5oKA2Aqeyu2LTGQ8xwolSBd7QGrFPYN/lE/RMeF1FurXcwD5tb8=; Received: from [78.36.60.25] (port=31888 helo=[10.168.2.113]) by smtp40.i.mail.ru with esmtpa (envelope-from ) id 1Tvp0P-00074S-79 for xen-api@lists.xen.org; Thu, 17 Jan 2013 16:55:41 +0400 Message-ID: <50F7F4C8.2090408@bk.ru> Date: Thu, 17 Jan 2013 16:55:36 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org X-Spam: Not detected X-Mras: Ok Subject: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I installed xcp-xapi on the Debian Wheezy and can't get LVMoHBA to work: stderr: Traceback (most recent call last): File "/usr/lib/xcp/sm/LVMoHBASR", line 220, in SRCommand.run(LVHDoHBASR, DRIVER_INFO) File "/usr/lib/xcp/sm/SRCommand.py", line 261, in run sr = driver(cmd, cmd.sr_uuid) File "/usr/lib/xcp/sm/SR.py", line 136, in __init__ self.load(sr_uuid) File "/usr/lib/xcp/sm/LVMoHBASR", line 94, in load print >>sys.stderr,self.hbasr.print_devs() File "/usr/lib/xcp/sm/HBASR.py", line 224, in print_devs self._init_hbadict() File "/usr/lib/xcp/sm/HBASR.py", line 61, in _init_hbadict dict = devscan.adapters(filterstr=self.type) File "/usr/lib/xcp/sm/devscan.py", line 168, in adapters glob.glob(os.path.join(path,"device","block:*"))[0]).split(':')[1] IndexError: list index out of range Can you please send devscan.py patch to support lvmohba in kernel 3.X. Also will in this case other lvmohba features will work smoothly in that case on Debian, especially multipath? With regards, Andrey. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 12:58:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:58:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp2l-0001jz-IQ; Thu, 17 Jan 2013 12:58:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp2k-0001jt-Aa for xen-api@lists.xen.org; Thu, 17 Jan 2013 12:58:06 +0000 Received: from [85.158.139.83:6630] by server-15.bemta-5.messagelabs.com id 38/8C-18817-D55F7F05; Thu, 17 Jan 2013 12:58:05 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-15.tower-182.messagelabs.com!1358427341!28184830!1 X-Originating-IP: [94.100.177.100] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 644 invoked from network); 17 Jan 2013 12:55:42 -0000 Received: from smtp40.i.mail.ru (HELO smtp40.i.mail.ru) (94.100.177.100) by server-15.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 12:55:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=4mNb+aRw3UiqPNDbJjpZ4cs18vasRbFmNRS1eIcbjvA=; b=PZlRgfyVAaC+RnHRaGYiDx21imQvwVgk04p5ELEEPFeSxmd9Lacm/67X9DmkEjkS21XhBrY3o8ZP8N6ivz2Hn3MzfQ0/OjAnL6mqFLrLwv0GHYcMIUWdjIaw5oKA2Aqeyu2LTGQ8xwolSBd7QGrFPYN/lE/RMeF1FurXcwD5tb8=; Received: from [78.36.60.25] (port=31888 helo=[10.168.2.113]) by smtp40.i.mail.ru with esmtpa (envelope-from ) id 1Tvp0P-00074S-79 for xen-api@lists.xen.org; Thu, 17 Jan 2013 16:55:41 +0400 Message-ID: <50F7F4C8.2090408@bk.ru> Date: Thu, 17 Jan 2013 16:55:36 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org X-Spam: Not detected X-Mras: Ok Subject: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I installed xcp-xapi on the Debian Wheezy and can't get LVMoHBA to work: stderr: Traceback (most recent call last): File "/usr/lib/xcp/sm/LVMoHBASR", line 220, in SRCommand.run(LVHDoHBASR, DRIVER_INFO) File "/usr/lib/xcp/sm/SRCommand.py", line 261, in run sr = driver(cmd, cmd.sr_uuid) File "/usr/lib/xcp/sm/SR.py", line 136, in __init__ self.load(sr_uuid) File "/usr/lib/xcp/sm/LVMoHBASR", line 94, in load print >>sys.stderr,self.hbasr.print_devs() File "/usr/lib/xcp/sm/HBASR.py", line 224, in print_devs self._init_hbadict() File "/usr/lib/xcp/sm/HBASR.py", line 61, in _init_hbadict dict = devscan.adapters(filterstr=self.type) File "/usr/lib/xcp/sm/devscan.py", line 168, in adapters glob.glob(os.path.join(path,"device","block:*"))[0]).split(':')[1] IndexError: list index out of range Can you please send devscan.py patch to support lvmohba in kernel 3.X. Also will in this case other lvmohba features will work smoothly in that case on Debian, especially multipath? With regards, Andrey. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 12:58:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:58:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp2u-0001m3-QD; Thu, 17 Jan 2013 12:58:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp2t-0001lu-Ug for xen-api@lists.xen.org; Thu, 17 Jan 2013 12:58:16 +0000 Received: from [85.158.143.35:47505] by server-3.bemta-4.messagelabs.com id 6A/A5-19220-765F7F05; Thu, 17 Jan 2013 12:58:15 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-2.tower-21.messagelabs.com!1358427140!4790904!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0NTkzMDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9201 invoked from network); 17 Jan 2013 12:52:23 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-2.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 12:52:23 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 7E187186F; Thu, 17 Jan 2013 14:52:20 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 36B8920068; Thu, 17 Jan 2013 14:52:20 +0200 (EET) Date: Thu, 17 Jan 2013 14:52:19 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Mike McClurg Message-ID: <20130117125219.GW8912@reaktio.net> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> <50F6F163.3000008@citrix.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50F6F163.3000008@citrix.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Wed, Jan 16, 2013 at 06:28:51PM +0000, Mike McClurg wrote: > On 15/01/13 21:01, Rushikesh Jadhav wrote: > >Mike & George, Please excuse me if its not related to subject but since > >you made the right xapi github branch ( very much required ) can we have > >the right Xen branch as well. There is tremendous difference in native > >Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. > > > >- Rushikesh > > Hi Rushikesh, > > Yes, this is definitely on topic. I've just gotten access to the > xenbits site, and I should have our xen patchqueue mirrored up there > by the end of the week. > Please push the dom0 kernel + pq aswell :) -- Pasi _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 12:58:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 12:58:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp2u-0001m3-QD; Thu, 17 Jan 2013 12:58:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp2t-0001lu-Ug for xen-api@lists.xen.org; Thu, 17 Jan 2013 12:58:16 +0000 Received: from [85.158.143.35:47505] by server-3.bemta-4.messagelabs.com id 6A/A5-19220-765F7F05; Thu, 17 Jan 2013 12:58:15 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-2.tower-21.messagelabs.com!1358427140!4790904!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0NTkzMDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9201 invoked from network); 17 Jan 2013 12:52:23 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-2.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 12:52:23 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 7E187186F; Thu, 17 Jan 2013 14:52:20 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 36B8920068; Thu, 17 Jan 2013 14:52:20 +0200 (EET) Date: Thu, 17 Jan 2013 14:52:19 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Mike McClurg Message-ID: <20130117125219.GW8912@reaktio.net> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> <50F6F163.3000008@citrix.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50F6F163.3000008@citrix.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Wed, Jan 16, 2013 at 06:28:51PM +0000, Mike McClurg wrote: > On 15/01/13 21:01, Rushikesh Jadhav wrote: > >Mike & George, Please excuse me if its not related to subject but since > >you made the right xapi github branch ( very much required ) can we have > >the right Xen branch as well. There is tremendous difference in native > >Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. > > > >- Rushikesh > > Hi Rushikesh, > > Yes, this is definitely on topic. I've just gotten access to the > xenbits site, and I should have our xen patchqueue mirrored up there > by the end of the week. > Please push the dom0 kernel + pq aswell :) -- Pasi _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 13:04:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 13:04:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp99-0002XH-S8; Thu, 17 Jan 2013 13:04:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp99-0002X6-1i for xen-api@lists.xen.org; Thu, 17 Jan 2013 13:04:43 +0000 Received: from [85.158.139.211:47306] by server-14.bemta-5.messagelabs.com id E3/F6-07459-AE6F7F05; Thu, 17 Jan 2013 13:04:42 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1358427876!18520899!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTc1NDU=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20246 invoked from network); 17 Jan 2013 13:04:37 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 13:04:37 -0000 X-IronPort-AV: E=Sophos;i="4.84,486,1355097600"; d="scan'208";a="3861420" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 17 Jan 2013 13:04:21 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Thu, 17 Jan 2013 08:04:21 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1Tvp8n-0001Gv-2F; Thu, 17 Jan 2013 13:04:21 +0000 Message-ID: <50F7F6D4.3030209@citrix.com> Date: Thu, 17 Jan 2013 13:04:20 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> <50F6F163.3000008@citrix.com> <20130117125219.GW8912@reaktio.net> In-Reply-To: <20130117125219.GW8912@reaktio.net> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 17/01/13 12:52, Pasi K=E4rkk=E4inen wrote: >> I've just gotten access to the >> >xenbits site, and I should have our xen patchqueue mirrored up there >> >by the end of the week. >> > > Please push the dom0 kernel + pq aswell:) Will do! Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 13:04:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 13:04:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp99-0002XH-S8; Thu, 17 Jan 2013 13:04:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tvp99-0002X6-1i for xen-api@lists.xen.org; Thu, 17 Jan 2013 13:04:43 +0000 Received: from [85.158.139.211:47306] by server-14.bemta-5.messagelabs.com id E3/F6-07459-AE6F7F05; Thu, 17 Jan 2013 13:04:42 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1358427876!18520899!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTc1NDU=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20246 invoked from network); 17 Jan 2013 13:04:37 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 13:04:37 -0000 X-IronPort-AV: E=Sophos;i="4.84,486,1355097600"; d="scan'208";a="3861420" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 17 Jan 2013 13:04:21 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Thu, 17 Jan 2013 08:04:21 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1Tvp8n-0001Gv-2F; Thu, 17 Jan 2013 13:04:21 +0000 Message-ID: <50F7F6D4.3030209@citrix.com> Date: Thu, 17 Jan 2013 13:04:20 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> <50F6F163.3000008@citrix.com> <20130117125219.GW8912@reaktio.net> In-Reply-To: <20130117125219.GW8912@reaktio.net> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 17/01/13 12:52, Pasi K=E4rkk=E4inen wrote: >> I've just gotten access to the >> >xenbits site, and I should have our xen patchqueue mirrored up there >> >by the end of the week. >> > > Please push the dom0 kernel + pq aswell:) Will do! Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 13:14:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 13:14:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvpIE-0003Mq-GA; Thu, 17 Jan 2013 13:14:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvpID-0003Me-K9 for xen-api@lists.xen.org; Thu, 17 Jan 2013 13:14:05 +0000 Received: from [85.158.143.35:54235] by server-3.bemta-4.messagelabs.com id E0/8D-19220-D19F7F05; Thu, 17 Jan 2013 13:14:05 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-4.tower-21.messagelabs.com!1358428443!5826916!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0NTkzMDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24386 invoked from network); 17 Jan 2013 13:14:04 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 13:14:04 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 21104134E; Thu, 17 Jan 2013 15:14:03 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id E9DBC20068; Thu, 17 Jan 2013 15:14:02 +0200 (EET) Date: Thu, 17 Jan 2013 15:14:02 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Mike McClurg Message-ID: <20130117131402.GY8912@reaktio.net> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> <50F6F163.3000008@citrix.com> <20130117125219.GW8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20130117125219.GW8912@reaktio.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, Jan 17, 2013 at 02:52:19PM +0200, Pasi K=E4rkk=E4inen wrote: > On Wed, Jan 16, 2013 at 06:28:51PM +0000, Mike McClurg wrote: > > On 15/01/13 21:01, Rushikesh Jadhav wrote: > > >Mike & George, Please excuse me if its not related to subject but since > > >you made the right xapi github branch ( very much required ) can we ha= ve > > >the right Xen branch as well. There is tremendous difference in native > > >Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. > > > > > >- Rushikesh > > = > > Hi Rushikesh, > > = > > Yes, this is definitely on topic. I've just gotten access to the > > xenbits site, and I should have our xen patchqueue mirrored up there > > by the end of the week. > > = > = > Please push the dom0 kernel + pq aswell :) > = For example for XCP 1.5 there are all these: http://xenbits.xen.org/hg/XCP/1.5/ blktap, dom0 kernel, qemu, xen, xen-sm, xsconsole. -- Pasi _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 13:14:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 13:14:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvpIE-0003Mq-GA; Thu, 17 Jan 2013 13:14:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvpID-0003Me-K9 for xen-api@lists.xen.org; Thu, 17 Jan 2013 13:14:05 +0000 Received: from [85.158.143.35:54235] by server-3.bemta-4.messagelabs.com id E0/8D-19220-D19F7F05; Thu, 17 Jan 2013 13:14:05 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-4.tower-21.messagelabs.com!1358428443!5826916!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0NTkzMDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24386 invoked from network); 17 Jan 2013 13:14:04 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 13:14:04 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 21104134E; Thu, 17 Jan 2013 15:14:03 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id E9DBC20068; Thu, 17 Jan 2013 15:14:02 +0200 (EET) Date: Thu, 17 Jan 2013 15:14:02 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Mike McClurg Message-ID: <20130117131402.GY8912@reaktio.net> References: <50EF7D13.3080004@gmail.com> <50F58E5B.4070008@citrix.com> <50F59644.5050603@gmail.com> <50F5A5E1.4060107@citrix.com> <50F5BBBA.1030701@gmail.com> <50F6F163.3000008@citrix.com> <20130117125219.GW8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20130117125219.GW8912@reaktio.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xapi sources: Fighting for right commit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, Jan 17, 2013 at 02:52:19PM +0200, Pasi K=E4rkk=E4inen wrote: > On Wed, Jan 16, 2013 at 06:28:51PM +0000, Mike McClurg wrote: > > On 15/01/13 21:01, Rushikesh Jadhav wrote: > > >Mike & George, Please excuse me if its not related to subject but since > > >you made the right xapi github branch ( very much required ) can we ha= ve > > >the right Xen branch as well. There is tremendous difference in native > > >Xen and XCP Xen and similar to Xapi the Xen commit is nowhere. > > > > > >- Rushikesh > > = > > Hi Rushikesh, > > = > > Yes, this is definitely on topic. I've just gotten access to the > > xenbits site, and I should have our xen patchqueue mirrored up there > > by the end of the week. > > = > = > Please push the dom0 kernel + pq aswell :) > = For example for XCP 1.5 there are all these: http://xenbits.xen.org/hg/XCP/1.5/ blktap, dom0 kernel, qemu, xen, xen-sm, xsconsole. -- Pasi _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 14:17:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 14:17:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqHi-0008Nz-LT; Thu, 17 Jan 2013 14:17:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqHg-0008Np-Td for xen-api@lists.xen.org; Thu, 17 Jan 2013 14:17:37 +0000 Received: from [85.158.137.99:42429] by server-4.bemta-3.messagelabs.com id 46/0A-04976-00808F05; Thu, 17 Jan 2013 14:17:36 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-217.messagelabs.com!1358432252!12578491!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22209 invoked from network); 17 Jan 2013 14:17:33 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-7.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 14:17:33 -0000 Received: by mail-la0-f51.google.com with SMTP id fj20so2715904lab.10 for ; Thu, 17 Jan 2013 06:17:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m5/anvDvpzO1TaVCLA1GG8F7MFj6P4FUH2BK5wBDtLU=; b=MZ2vLds+XUbGLgEVVTeHyMAOUMKJmqcDKvzBX38g8XA7LKM+tzYBLaWQNhoMk12sK+ P/19XELMyyILzXc0SDSMnJyXLsFiXIDr5ct30qnjQsXKlqA0p9J/RIXP5W8TKGzecqkf ekBHETL14OTXgONj0eYG7rz+Ev4CF0F3PxUmXTgHvfgeQX2diEceS81ffOVhWWeGPwTG XVbDZYB20kqX5BNmbzrRKRwiWMkFLQPuNuhJSpt4pVj0YpemlnSkM2E8jnLc56VXWUR5 wUovB0lQKoPo7HSnxID9pMAcneFLdV0adKSrMT9QKN6PkF8jdf6/lnrvLra7Y6v4rYlk ZdiA== X-Received: by 10.112.36.137 with SMTP id q9mr2335260lbj.42.1358432252447; Thu, 17 Jan 2013 06:17:32 -0800 (PST) Received: from [172.16.25.10] (b0fb48e2.bb.sky.com. [176.251.72.226]) by mx.google.com with ESMTPS id f8sm856852lbg.2.2013.01.17.06.17.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jan 2013 06:17:31 -0800 (PST) Message-ID: <50F807DC.3000101@xen.org> Date: Thu, 17 Jan 2013 14:17:00 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> <344C0F67BC927847A2C92F9EE358DB0E01224E5B3E64@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E5B3E64@LONPMAILBOX01.citrite.net> Subject: Re: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Scott, thank you for this. I am going to add categories to the page, such that they can be more easily found. Please make sure you do this in future. Uncategorized pages are really hard to find on the wiki. More info at: - http://wiki.xen.org/wiki/Categories_for_Authors - http://wiki.xen.org/wiki/Category:Templates also useful Regards Lars On 11/01/2013 18:58, James Bulpin wrote: > Feeling brave I've tried this on CentOS 6.3 with Xen 4.2. Here's > how it went... > > I used the "Software development workstation" installation base for > CentOS 6.3 (x86_64) which meant I got a certain amount of virtualisation > infrastructure including a "virbr0" NATed bridge. I prefer basic L2 > bridging so I manually created a xenbr0 in the traditional manner. I > installed Xen 4.2.1 and a suitable 3.4 kernel. > > I chose to compile vncterm from the source at > https://github.com/xen-org/vncterm - this uses the old xs.h filename for > the xenstore headers so I have to change this to xenstore.h to make it > build against 4.2. > > I used the latest binary download of opam to install ocaml 4.00.1. Being > a local installation this meant the paths differed from Dave's tutorial > being ~/.opam/4.00.1/ instead of ~/.opam/system/ > > I hit an error building xenopsd because it was depending on xenctrl 4.1.0 > rather than just the latest version - Dave fixed this in his repo. > > To run xenopsd I have to uncomment the vncterm config line in > xenopsd.conf to point to the binary. In the same file I had to uncomment > the hvmloader line and remove the quotes (xenopsd was treating them > literally) > > For the VM storage I chose to use LVM to fit with the current "phy:" > constraint. > > Trying to start a PV guest hit a few problems: > > 1. xenopsd gave an error saying it had no bootable devices - this was > because the devices list was hard wired to empty in the CLI, Dave > fixed this in the repo > > 2. xenopsd assumes that pygrub has the --default_args, --extra_args and > --vm arguments present in the XenServer/XCP version of pygrub but not > present in the Xen 4.2 version. I patched the latter to add these. > > 3. xenopsd complains of an invalid result from the domain builder. Dave > is currently working on this. > > Trying a HVM guest led to a different set of challenges: > > 1. xenopsd was hanging waiting to plug the VBD - this turns out to be > because the hotplug scripts were not running because xl had disabled > them (by default xl runs these scripts itself but this can be > overridden by setting "run_hotplug_scripts=0" in /etc/xen/xl.conf). I > suspect this problem will go away when Rob does the xenopsd libxl > port. > > 2. xenopsd is using a VIF hotplug scripts that is very XenServer/XCP > centric and doesn't run to completion on CentOS 6.3. This was > configured in the automatically generaled xenopsd.conf so I instead > changed this to use /etc/xen/scripts/vif-bridge instead. > > 3. xenopsd doesn't put the "bridge" key in the usual backend xenstore > location (/local/domain/0/backend/vif//) so the Xen > 4.2 vif script defaulted to the first bridge, not the one I had > configured. > > 4. xenopsd was hanging waiting for a hotplug event on the VIF but was > watching /xapi//vif//hotplug which would never be > touched by Xen 4.2 hotplug scripts. To workaround this I manually > created that entry after each VM start > > 5. qemu-dm-wrapper would always silently fail when run by xenopsd but > not when run interactively. This is because it tried to setrlimit a > value with the soft limit being higher than the hard limit. I put in > a simple fix to avoid this. > > 6. qemu-dm-wrapper would always fail because it hard-coded the path to > xenstore-write in /usr/sbin but it's in /usr/bin on my system. I > fixed this locally but w search path will be useful in the future. > > So in summary with a few tweaks and workarounds I can no run HVM guests > on CentOS 6.3 using xenopsd. I encourage others to try this on your > distro of choice. > > Bugs have been filed at https://github.com/xen-org/xenopsd/issues > > Cheers, > James > >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >> bounces@lists.xen.org] On Behalf Of Dave Scott >> Sent: 04 January 2013 15:44 >> To: xen-api@lists.xen.org >> Subject: [Xen-API] running latest dev versions of xenopsd on >> Debian/Ubuntu >> >> Hi, >> >> I've written a wiki page describing how to build the latest development >> version of "xenopsd" (and its dependencies) from source: >> >> http://wiki.xen.org/wiki/Building_Xenopsd >> >> "xenopsd" is the name of the domain manager of the XCP toolstack -- it >> is responsible for starting, stopping, migrating VMs. >> >> Being able to build the development version is really useful if you >> want to: >> * check out a new feature >> * reproduce a bug >> * test a fix >> >> Let me know if you try this and have any problems or suggestions! >> >> There are a couple more components of the XCP toolstack that need some >> fixups so they can build easily, in particular: >> * squeezed: manages memory ballooning >> * networkd: configures VM networking >> * rrdd: collects and archives performance statistics >> * xapi: manages the overall resource pool >> >> Hopefully we can work on these one-by-one until they are all as easy to >> build as xenopsd. >> >> Cheers, >> Dave >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 14:17:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 14:17:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqHi-0008Nz-LT; Thu, 17 Jan 2013 14:17:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqHg-0008Np-Td for xen-api@lists.xen.org; Thu, 17 Jan 2013 14:17:37 +0000 Received: from [85.158.137.99:42429] by server-4.bemta-3.messagelabs.com id 46/0A-04976-00808F05; Thu, 17 Jan 2013 14:17:36 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-217.messagelabs.com!1358432252!12578491!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22209 invoked from network); 17 Jan 2013 14:17:33 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-7.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 14:17:33 -0000 Received: by mail-la0-f51.google.com with SMTP id fj20so2715904lab.10 for ; Thu, 17 Jan 2013 06:17:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m5/anvDvpzO1TaVCLA1GG8F7MFj6P4FUH2BK5wBDtLU=; b=MZ2vLds+XUbGLgEVVTeHyMAOUMKJmqcDKvzBX38g8XA7LKM+tzYBLaWQNhoMk12sK+ P/19XELMyyILzXc0SDSMnJyXLsFiXIDr5ct30qnjQsXKlqA0p9J/RIXP5W8TKGzecqkf ekBHETL14OTXgONj0eYG7rz+Ev4CF0F3PxUmXTgHvfgeQX2diEceS81ffOVhWWeGPwTG XVbDZYB20kqX5BNmbzrRKRwiWMkFLQPuNuhJSpt4pVj0YpemlnSkM2E8jnLc56VXWUR5 wUovB0lQKoPo7HSnxID9pMAcneFLdV0adKSrMT9QKN6PkF8jdf6/lnrvLra7Y6v4rYlk ZdiA== X-Received: by 10.112.36.137 with SMTP id q9mr2335260lbj.42.1358432252447; Thu, 17 Jan 2013 06:17:32 -0800 (PST) Received: from [172.16.25.10] (b0fb48e2.bb.sky.com. [176.251.72.226]) by mx.google.com with ESMTPS id f8sm856852lbg.2.2013.01.17.06.17.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jan 2013 06:17:31 -0800 (PST) Message-ID: <50F807DC.3000101@xen.org> Date: Thu, 17 Jan 2013 14:17:00 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> <344C0F67BC927847A2C92F9EE358DB0E01224E5B3E64@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E5B3E64@LONPMAILBOX01.citrite.net> Subject: Re: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Scott, thank you for this. I am going to add categories to the page, such that they can be more easily found. Please make sure you do this in future. Uncategorized pages are really hard to find on the wiki. More info at: - http://wiki.xen.org/wiki/Categories_for_Authors - http://wiki.xen.org/wiki/Category:Templates also useful Regards Lars On 11/01/2013 18:58, James Bulpin wrote: > Feeling brave I've tried this on CentOS 6.3 with Xen 4.2. Here's > how it went... > > I used the "Software development workstation" installation base for > CentOS 6.3 (x86_64) which meant I got a certain amount of virtualisation > infrastructure including a "virbr0" NATed bridge. I prefer basic L2 > bridging so I manually created a xenbr0 in the traditional manner. I > installed Xen 4.2.1 and a suitable 3.4 kernel. > > I chose to compile vncterm from the source at > https://github.com/xen-org/vncterm - this uses the old xs.h filename for > the xenstore headers so I have to change this to xenstore.h to make it > build against 4.2. > > I used the latest binary download of opam to install ocaml 4.00.1. Being > a local installation this meant the paths differed from Dave's tutorial > being ~/.opam/4.00.1/ instead of ~/.opam/system/ > > I hit an error building xenopsd because it was depending on xenctrl 4.1.0 > rather than just the latest version - Dave fixed this in his repo. > > To run xenopsd I have to uncomment the vncterm config line in > xenopsd.conf to point to the binary. In the same file I had to uncomment > the hvmloader line and remove the quotes (xenopsd was treating them > literally) > > For the VM storage I chose to use LVM to fit with the current "phy:" > constraint. > > Trying to start a PV guest hit a few problems: > > 1. xenopsd gave an error saying it had no bootable devices - this was > because the devices list was hard wired to empty in the CLI, Dave > fixed this in the repo > > 2. xenopsd assumes that pygrub has the --default_args, --extra_args and > --vm arguments present in the XenServer/XCP version of pygrub but not > present in the Xen 4.2 version. I patched the latter to add these. > > 3. xenopsd complains of an invalid result from the domain builder. Dave > is currently working on this. > > Trying a HVM guest led to a different set of challenges: > > 1. xenopsd was hanging waiting to plug the VBD - this turns out to be > because the hotplug scripts were not running because xl had disabled > them (by default xl runs these scripts itself but this can be > overridden by setting "run_hotplug_scripts=0" in /etc/xen/xl.conf). I > suspect this problem will go away when Rob does the xenopsd libxl > port. > > 2. xenopsd is using a VIF hotplug scripts that is very XenServer/XCP > centric and doesn't run to completion on CentOS 6.3. This was > configured in the automatically generaled xenopsd.conf so I instead > changed this to use /etc/xen/scripts/vif-bridge instead. > > 3. xenopsd doesn't put the "bridge" key in the usual backend xenstore > location (/local/domain/0/backend/vif//) so the Xen > 4.2 vif script defaulted to the first bridge, not the one I had > configured. > > 4. xenopsd was hanging waiting for a hotplug event on the VIF but was > watching /xapi//vif//hotplug which would never be > touched by Xen 4.2 hotplug scripts. To workaround this I manually > created that entry after each VM start > > 5. qemu-dm-wrapper would always silently fail when run by xenopsd but > not when run interactively. This is because it tried to setrlimit a > value with the soft limit being higher than the hard limit. I put in > a simple fix to avoid this. > > 6. qemu-dm-wrapper would always fail because it hard-coded the path to > xenstore-write in /usr/sbin but it's in /usr/bin on my system. I > fixed this locally but w search path will be useful in the future. > > So in summary with a few tweaks and workarounds I can no run HVM guests > on CentOS 6.3 using xenopsd. I encourage others to try this on your > distro of choice. > > Bugs have been filed at https://github.com/xen-org/xenopsd/issues > > Cheers, > James > >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >> bounces@lists.xen.org] On Behalf Of Dave Scott >> Sent: 04 January 2013 15:44 >> To: xen-api@lists.xen.org >> Subject: [Xen-API] running latest dev versions of xenopsd on >> Debian/Ubuntu >> >> Hi, >> >> I've written a wiki page describing how to build the latest development >> version of "xenopsd" (and its dependencies) from source: >> >> http://wiki.xen.org/wiki/Building_Xenopsd >> >> "xenopsd" is the name of the domain manager of the XCP toolstack -- it >> is responsible for starting, stopping, migrating VMs. >> >> Being able to build the development version is really useful if you >> want to: >> * check out a new feature >> * reproduce a bug >> * test a fix >> >> Let me know if you try this and have any problems or suggestions! >> >> There are a couple more components of the XCP toolstack that need some >> fixups so they can build easily, in particular: >> * squeezed: manages memory ballooning >> * networkd: configures VM networking >> * rrdd: collects and archives performance statistics >> * xapi: manages the overall resource pool >> >> Hopefully we can work on these one-by-one until they are all as easy to >> build as xenopsd. >> >> Cheers, >> Dave >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 14:19:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 14:19:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqJm-0000F4-3t; Thu, 17 Jan 2013 14:19:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqJk-0000Ea-EM for xen-api@lists.xen.org; Thu, 17 Jan 2013 14:19:44 +0000 Received: from [85.158.139.83:4223] by server-13.bemta-5.messagelabs.com id DE/36-06386-F7808F05; Thu, 17 Jan 2013 14:19:43 +0000 X-Env-Sender: simon.beaumont@citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1358432382!28337257!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2OTgz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10247 invoked from network); 17 Jan 2013 14:19:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 14:19:42 -0000 X-IronPort-AV: E=Sophos;i="4.84,486,1355097600"; d="scan'208";a="724405" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Jan 2013 14:19:42 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 17 Jan 2013 14:19:41 +0000 From: Simon Beaumont To: 'Andrey' Date: Thu, 17 Jan 2013 14:19:40 +0000 Thread-Topic: [Xen-API] xcp-xapi devscan.py kernel support Thread-Index: Ac30sqHQyGI24pfYR5CpVE6j3tZTCQACTkvg Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> References: <50F7F4C8.2090408@bk.ru> In-Reply-To: <50F7F4C8.2090408@bk.ru> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/mixed; boundary="_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_" MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org= ] On > Behalf Of Andrey > Sent: 17 January 2013 12:56 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] xcp-xapi devscan.py kernel support > > I installed xcp-xapi on the Debian Wheezy and can't get LVMoHBA to work: >=20 > stderr: Traceback (most recent call last): > File "/usr/lib/xcp/sm/LVMoHBASR", line 220, in > SRCommand.run(LVHDoHBASR, DRIVER_INFO) > File "/usr/lib/xcp/sm/SRCommand.py", line 261, in run > sr =3D driver(cmd, cmd.sr_uuid) > File "/usr/lib/xcp/sm/SR.py", line 136, in __init__ > self.load(sr_uuid) > File "/usr/lib/xcp/sm/LVMoHBASR", line 94, in load > print >>sys.stderr,self.hbasr.print_devs() > File "/usr/lib/xcp/sm/HBASR.py", line 224, in print_devs > self._init_hbadict() > File "/usr/lib/xcp/sm/HBASR.py", line 61, in _init_hbadict > dict =3D devscan.adapters(filterstr=3Dself.type) > File "/usr/lib/xcp/sm/devscan.py", line 168, in adapters > glob.glob(os.path.join(path,"device","block:*"))[0]).split(':')[1] > IndexError: list index out of range >=20 >=20 > Can you please send devscan.py patch to support lvmohba in kernel 3.X. I have attached the patch in question. It uses the right sysfs paths after = detecting the kernel version. It might not apply to your version but it may= help you make the change you require. > Also will in this case other lvmohba features will work smoothly in that = case > on Debian, especially multipath? It's unlikely you'll get LVM to work with your setup since we use a patched= version that accepts another option (--master) which affords us a differen= t locking mechanism to allow shared SRs. This option doesn't exist in the u= pstream Debian LVM. It may(!) be possible to get it to work if you remove the --master option f= rom the calls to lvm in the source and ensure that you are only using these= SRs in single-host pools. Again, your mileage may vary. Hope this helps, -Si --_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_ Content-Type: application/octet-stream; name="HBA-sysfs-paths-3.x-fix.patch" Content-Description: HBA-sysfs-paths-3.x-fix.patch Content-Disposition: attachment; filename="HBA-sysfs-paths-3.x-fix.patch"; size=4842; creation-date="Thu, 17 Jan 2013 14:11:41 GMT"; modification-date="Thu, 17 Jan 2013 12:48:22 GMT" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL2RyaXZlcnMvZGV2c2Nhbi5weSBiL2RyaXZlcnMvZGV2c2Nhbi5weQotLS0g YS9kcml2ZXJzL2RldnNjYW4ucHkKKysrIGIvZHJpdmVycy9kZXZzY2FuLnB5CkBAIC0xMSwxMiAr MTEsNiBAQAogIyBNRVJDSEFOVEFCSUxJVFkgb3IgRklUTkVTUyBGT1IgQSBQQVJUSUNVTEFSIFBV UlBPU0UuIFNlZSB0aGUgCiAjIEdOVSBMZXNzZXIgR2VuZXJhbCBQdWJsaWMgTGljZW5zZSBmb3Ig bW9yZSBkZXRhaWxzLgogCi0jIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjCi0jICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgTk9USUNFICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAjCi0jIFBM RUFTRSBLRUVQIGhvc3QtaW5zdGFsbGVyLmhnL2RldnNjYW4ucHkgQU5EIHNtLmhnL2RyaXZlcnMv ZGV2c2Nhbi5weSAjCi0jIFNZTkNIUk9OSVNFRCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAjCi0jIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjCi0KIGltcG9y dCBzeXMsIG9zLCByZQogaW1wb3J0IHNjc2l1dGlsLCB1dGlsCiBpbXBvcnQgeG1sLmRvbS5taW5p ZG9tCkBAIC0xMjIsMTMgKzExNiw4IEBACiAgICAgICAgICAgICAgICAgICAgICAgICBkaXIgPSBv cy5wYXRoLmpvaW4oc3lzZnMsbHVuKQogICAgICAgICAgICAgICAgICAgICBlbHNlOgogICAgICAg ICAgICAgICAgICAgICAgICAgZGlyID0gb3MucGF0aC5qb2luKHN5c2ZzLGx1biwiZGV2aWNlIikK LSAgICAgICAgICAgICAgICAgICAgZm9yIGRldiBpbiBmaWx0ZXIobWF0Y2hfZGV2LG9zLmxpc3Rk aXIoZGlyKSk6Ci0gICAgICAgICAgICAgICAgICAgICAgICBrZXkgPSBkZXYucmVwbGFjZSgiYmxv Y2s6IiwiIikKLSAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5ID0ge30KLSAgICAgICAgICAg ICAgICAgICAgICAgIGVudHJ5Wydwcm9jbmFtZSddID0gcHJvYwotICAgICAgICAgICAgICAgICAg ICAgICAgZW50cnlbJ2hvc3QnXSA9aWQKLSAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wyd0 YXJnZXQnXSA9IGx1bgotICAgICAgICAgICAgICAgICAgICAgICAgZGV2c1trZXldID0gZW50cnkK KyAgICAgICAgICAgICAgICAgICAgKGRldiwgZW50cnkpID0gX2V4dHJhY3RfZGV2KGRpciwgcHJv YywgaWQsIGx1bikKKyAgICAgICAgICAgICAgICAgICAgZGV2c1tkZXZdID0gZW50cnkKICAgICAg ICAgICAgICMgZm9yIG5ldyBxbG9naWMgc3lzZnMgbGF5b3V0IChycG9ydCB1bmRlciBkZXZpY2Us IHRoZW4gdGFyZ2V0KQogICAgICAgICAgICAgZm9yIGkgaW4gZmlsdGVyKG1hdGNoX3Jwb3J0LG9z Lmxpc3RkaXIocGF0aCkpOgogICAgICAgICAgICAgICAgIG5ld3BhdGggPSBvcy5wYXRoLmpvaW4o cGF0aCwgaSkKQEAgLTEzOSwxMyArMTI4LDggQEAKICAgICAgICAgICAgICAgICAgICAgICAgIGlm IG5vdCBtYXRjaF9MVU5zKGx1bix0Z3QpOgogICAgICAgICAgICAgICAgICAgICAgICAgICAgIGNv bnRpbnVlCiAgICAgICAgICAgICAgICAgICAgICAgICBkaXIgPSBvcy5wYXRoLmpvaW4oc3lzZnMs bHVuLCJkZXZpY2UiKQotICAgICAgICAgICAgICAgICAgICAgICAgZm9yIGRldiBpbiBmaWx0ZXIo bWF0Y2hfZGV2LG9zLmxpc3RkaXIoZGlyKSk6Ci0gICAgICAgICAgICAgICAgICAgICAgICAgICAg a2V5ID0gZGV2LnJlcGxhY2UoImJsb2NrOiIsIiIpCi0gICAgICAgICAgICAgICAgICAgICAgICAg ICAgZW50cnkgPSB7fQotICAgICAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wydwcm9jbmFt ZSddID0gcHJvYwotICAgICAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wydob3N0J10gPSBp ZAotICAgICAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wyd0YXJnZXQnXSA9IGx1bgotICAg ICAgICAgICAgICAgICAgICAgICAgICAgIGRldnNba2V5XSA9IGVudHJ5CisgICAgICAgICAgICAg ICAgICAgICAgICAoZGV2LCBlbnRyeSkgPSBfZXh0cmFjdF9kZXYoZGlyLCBwcm9jLCBpZCwgbHVu KQorICAgICAgICAgICAgICAgICAgICAgICAgZGV2c1tkZXZdID0gZW50cnkKIAogICAgICAgICAg ICAgIyBmb3IgbmV3IG1wdHNhcyBzeXNmcyBlbnRyaWVzLCBjaGVjayBmb3IgcGh5KiBub2RlCiAg ICAgICAgICAgICBmb3IgaSBpbiBmaWx0ZXIobWF0Y2hfcGh5LG9zLmxpc3RkaXIocGF0aCkpOgpA QCAtMTU2LDIyICsxNDAsMTcgQEAKICAgICAgICAgICAgICAgICAgICAgaWYgbm90IG1hdGNoX0xV TnMobHVuLHRndCk6CiAgICAgICAgICAgICAgICAgICAgICAgICBjb250aW51ZQogICAgICAgICAg ICAgICAgICAgICBkaXIgPSBvcy5wYXRoLmpvaW4oc3lzZnMsbHVuLCJkZXZpY2UiKQotICAgICAg ICAgICAgICAgICAgICBmb3IgZGV2IGluIGZpbHRlcihtYXRjaF9kZXYsb3MubGlzdGRpcihkaXIp KToKLSAgICAgICAgICAgICAgICAgICAgICAgIGtleSA9IGRldi5yZXBsYWNlKCJibG9jazoiLCIi KQotICAgICAgICAgICAgICAgICAgICAgICAgZW50cnkgPSB7fQotICAgICAgICAgICAgICAgICAg ICAgICAgZW50cnlbJ3Byb2NuYW1lJ10gPSBwcm9jCi0gICAgICAgICAgICAgICAgICAgICAgICBl bnRyeVsnaG9zdCddID0gaWQKLSAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wyd0YXJnZXQn XSA9IGx1bgotICAgICAgICAgICAgICAgICAgICAgICAgZGV2c1trZXldID0gZW50cnkKKyAgICAg ICAgICAgICAgICAgICAgKGRldiwgZW50cnkpID0gX2V4dHJhY3RfZGV2KGRpciwgcHJvYywgaWQs IGx1bikKKyAgICAgICAgICAgICAgICAgICAgZGV2c1tkZXZdID0gZW50cnkKICAgICAgICAgICAg IGlmIHBhdGguc3RhcnRzd2l0aChTWVNGU19QQVRIMik6Ci0gICAgICAgICAgICAgICAga2V5ID0g b3MucGF0aC5iYXNlbmFtZShcCi0gICAgICAgICAgICAgICAgICAgIGdsb2IuZ2xvYihvcy5wYXRo LmpvaW4ocGF0aCwiZGV2aWNlIiwiYmxvY2s6KiIpKVswXSkuc3BsaXQoJzonKVsxXQotICAgICAg ICAgICAgICAgIGlmIGRldnMuaGFzX2tleShrZXkpOgorICAgICAgICAgICAgICAgIG9zLnBhdGgu am9pbihwYXRoLCJkZXZpY2UiLCJibG9jazoqIikKKyAgICAgICAgICAgICAgICBkZXYgPSBfZXh0 cmFjdF9kZXZfbmFtZShvcy5wYXRoLmpvaW4ocGF0aCwgJ2RldmljZScpKQorICAgICAgICAgICAg ICAgIGlmIGRldnMuaGFzX2tleShkZXYpOgogICAgICAgICAgICAgICAgICAgICBjb250aW51ZQog ICAgICAgICAgICAgICAgIGhidGwgPSBvcy5wYXRoLmJhc2VuYW1lKHBhdGgpCiAgICAgICAgICAg ICAgICAgKGgsYix0LGwpID0gaGJ0bC5zcGxpdCgnOicpCiAgICAgICAgICAgICAgICAgZW50cnkg PSB7J3Byb2NuYW1lJzpwcm9jLCAnaG9zdCc6aWQsICd0YXJnZXQnOmx9Ci0gICAgICAgICAgICAg ICAgZGV2c1trZXldID0gZW50cnkKKyAgICAgICAgICAgICAgICBkZXZzW2Rldl0gPSBlbnRyeQog CiAgICAgZGljdFsnZGV2cyddID0gZGV2cwogICAgIGRpY3RbJ2FkdCddID0gYWR0CkBAIC0yNTYs NiArMjM1LDMzIEBACiAgICAgcmVnZXggPSByZS5jb21waWxlKCJeYmxvY2s6IikKICAgICByZXR1 cm4gcmVnZXguc2VhcmNoKHMsIDApCiAKK2RlZiBfZXh0cmFjdF9kZXZfbmFtZShkZXZpY2VfZGly KToKKyAgICAiIiJSZXR1cm5zIHRoZSBuYW1lIG9mIHRoZSBibG9jayBkZXZpY2UgZnJvbSBzeXNm cyBlLmcuICdzZGEnIiIiCisgICAga2VybmVsX3ZlcnNpb24gPSBvcy51bmFtZSgpWzJdCisKKyAg ICBpZiBrZXJuZWxfdmVyc2lvbi5zdGFydHN3aXRoKCcyLjYnKToKKyAgICAgICAgIyBzdWItZGly ZWN0b3J5IG9mIGZvcm0gYmxvY2s6c2R4LworICAgICAgICBkZXYgPSBmaWx0ZXIobWF0Y2hfZGV2 LCBvcy5saXN0ZGlyKGRldmljZV9kaXIpKVswXQorICAgICAgICAjIHJlbW92ZSAnYmxvY2s6JyBm cm9tIGVudHJ5IGFuZCByZXR1cm4KKyAgICAgICAgcmV0dXJuIGRldi5sc3RyaXAoJ2Jsb2NrOicp CisgICAgZWxpZiBrZXJuZWxfdmVyc2lvbi5zdGFydHN3aXRoKCczLicpOgorICAgICAgICAjIGRp cmVjdG9yeSBmb3IgZGV2aWNlIG5hbWUgbGl2ZXMgaW5zaWRlIGJsb2NrIGRpcmVjdG9yeSBlLmcu IGJsb2NrL3NkeAorICAgICAgICBkZXYgPSBnbG9iLmdsb2Iob3MucGF0aC5qb2luKGRldmljZV9k aXIsICdibG9jay8qJykpWzBdCisgICAgICAgICMgcHJ1bmUgcGF0aCB0byBleHRyYWN0IHRoZSBk ZXZpY2UgbmFtZQorICAgICAgICByZXR1cm4gb3MucGF0aC5iYXNlbmFtZShkZXYpCisgICAgZWxz ZToKKyAgICAgICAgbXNnID0gJ0tlcm5lbCB2ZXJzaW9uIGRldGVjdGVkOiAlcycgJSBrZXJuZWxf dmVyc2lvbgorICAgICAgICByYWlzZSB4c19lcnJvcnMuWGVuRXJyb3IoJ1Vuc3VwcG9ydGVkS2Vy bmVsJywgbXNnKQorCitkZWYgX2V4dHJhY3RfZGV2KGRldmljZV9kaXIsIHByb2NuYW1lLCBob3N0 LCB0YXJnZXQpOgorICAgICIiIlJldHVybnMgZGV2aWNlIG5hbWUgYW5kIGNyZWF0ZXMgZGljdGlv bmFyeSBlbnRyeSBmb3IgaXQiIiIKKyAgICBkZXYgPSBfZXh0cmFjdF9kZXZfbmFtZShkZXZpY2Vf ZGlyKQorICAgIGVudHJ5ID0ge30KKyAgICBlbnRyeVsncHJvY25hbWUnXSA9IHByb2NuYW1lCisg ICAgZW50cnlbJ2hvc3QnXSA9IGhvc3QKKyAgICBlbnRyeVsndGFyZ2V0J10gPSB0YXJnZXQKKyAg ICByZXR1cm4gKGRldiwgZW50cnkpCisKIGRlZiBzY2FuKHNyb2JqKToKICAgICBzeXN0ZW1yb290 SUQgPSB1dGlsLmdldHJvb3RkZXZJRCgpCiAgICAgaGJhZGljdCA9IHNyb2JqLmhiYWRpY3QK --_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_-- From xen-api-bounces@lists.xen.org Thu Jan 17 14:19:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 14:19:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqJm-0000F4-3t; Thu, 17 Jan 2013 14:19:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqJk-0000Ea-EM for xen-api@lists.xen.org; Thu, 17 Jan 2013 14:19:44 +0000 Received: from [85.158.139.83:4223] by server-13.bemta-5.messagelabs.com id DE/36-06386-F7808F05; Thu, 17 Jan 2013 14:19:43 +0000 X-Env-Sender: simon.beaumont@citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1358432382!28337257!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE2OTgz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10247 invoked from network); 17 Jan 2013 14:19:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 14:19:42 -0000 X-IronPort-AV: E=Sophos;i="4.84,486,1355097600"; d="scan'208";a="724405" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Jan 2013 14:19:42 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 17 Jan 2013 14:19:41 +0000 From: Simon Beaumont To: 'Andrey' Date: Thu, 17 Jan 2013 14:19:40 +0000 Thread-Topic: [Xen-API] xcp-xapi devscan.py kernel support Thread-Index: Ac30sqHQyGI24pfYR5CpVE6j3tZTCQACTkvg Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> References: <50F7F4C8.2090408@bk.ru> In-Reply-To: <50F7F4C8.2090408@bk.ru> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/mixed; boundary="_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_" MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org= ] On > Behalf Of Andrey > Sent: 17 January 2013 12:56 PM > To: xen-api@lists.xen.org > Subject: [Xen-API] xcp-xapi devscan.py kernel support > > I installed xcp-xapi on the Debian Wheezy and can't get LVMoHBA to work: >=20 > stderr: Traceback (most recent call last): > File "/usr/lib/xcp/sm/LVMoHBASR", line 220, in > SRCommand.run(LVHDoHBASR, DRIVER_INFO) > File "/usr/lib/xcp/sm/SRCommand.py", line 261, in run > sr =3D driver(cmd, cmd.sr_uuid) > File "/usr/lib/xcp/sm/SR.py", line 136, in __init__ > self.load(sr_uuid) > File "/usr/lib/xcp/sm/LVMoHBASR", line 94, in load > print >>sys.stderr,self.hbasr.print_devs() > File "/usr/lib/xcp/sm/HBASR.py", line 224, in print_devs > self._init_hbadict() > File "/usr/lib/xcp/sm/HBASR.py", line 61, in _init_hbadict > dict =3D devscan.adapters(filterstr=3Dself.type) > File "/usr/lib/xcp/sm/devscan.py", line 168, in adapters > glob.glob(os.path.join(path,"device","block:*"))[0]).split(':')[1] > IndexError: list index out of range >=20 >=20 > Can you please send devscan.py patch to support lvmohba in kernel 3.X. I have attached the patch in question. It uses the right sysfs paths after = detecting the kernel version. It might not apply to your version but it may= help you make the change you require. > Also will in this case other lvmohba features will work smoothly in that = case > on Debian, especially multipath? It's unlikely you'll get LVM to work with your setup since we use a patched= version that accepts another option (--master) which affords us a differen= t locking mechanism to allow shared SRs. This option doesn't exist in the u= pstream Debian LVM. It may(!) be possible to get it to work if you remove the --master option f= rom the calls to lvm in the source and ensure that you are only using these= SRs in single-host pools. Again, your mileage may vary. Hope this helps, -Si --_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_ Content-Type: application/octet-stream; name="HBA-sysfs-paths-3.x-fix.patch" Content-Description: HBA-sysfs-paths-3.x-fix.patch Content-Disposition: attachment; filename="HBA-sysfs-paths-3.x-fix.patch"; size=4842; creation-date="Thu, 17 Jan 2013 14:11:41 GMT"; modification-date="Thu, 17 Jan 2013 12:48:22 GMT" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL2RyaXZlcnMvZGV2c2Nhbi5weSBiL2RyaXZlcnMvZGV2c2Nhbi5weQotLS0g YS9kcml2ZXJzL2RldnNjYW4ucHkKKysrIGIvZHJpdmVycy9kZXZzY2FuLnB5CkBAIC0xMSwxMiAr MTEsNiBAQAogIyBNRVJDSEFOVEFCSUxJVFkgb3IgRklUTkVTUyBGT1IgQSBQQVJUSUNVTEFSIFBV UlBPU0UuIFNlZSB0aGUgCiAjIEdOVSBMZXNzZXIgR2VuZXJhbCBQdWJsaWMgTGljZW5zZSBmb3Ig bW9yZSBkZXRhaWxzLgogCi0jIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjCi0jICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgTk9USUNFICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAjCi0jIFBM RUFTRSBLRUVQIGhvc3QtaW5zdGFsbGVyLmhnL2RldnNjYW4ucHkgQU5EIHNtLmhnL2RyaXZlcnMv ZGV2c2Nhbi5weSAjCi0jIFNZTkNIUk9OSVNFRCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAjCi0jIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjCi0KIGltcG9y dCBzeXMsIG9zLCByZQogaW1wb3J0IHNjc2l1dGlsLCB1dGlsCiBpbXBvcnQgeG1sLmRvbS5taW5p ZG9tCkBAIC0xMjIsMTMgKzExNiw4IEBACiAgICAgICAgICAgICAgICAgICAgICAgICBkaXIgPSBv cy5wYXRoLmpvaW4oc3lzZnMsbHVuKQogICAgICAgICAgICAgICAgICAgICBlbHNlOgogICAgICAg ICAgICAgICAgICAgICAgICAgZGlyID0gb3MucGF0aC5qb2luKHN5c2ZzLGx1biwiZGV2aWNlIikK LSAgICAgICAgICAgICAgICAgICAgZm9yIGRldiBpbiBmaWx0ZXIobWF0Y2hfZGV2LG9zLmxpc3Rk aXIoZGlyKSk6Ci0gICAgICAgICAgICAgICAgICAgICAgICBrZXkgPSBkZXYucmVwbGFjZSgiYmxv Y2s6IiwiIikKLSAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5ID0ge30KLSAgICAgICAgICAg ICAgICAgICAgICAgIGVudHJ5Wydwcm9jbmFtZSddID0gcHJvYwotICAgICAgICAgICAgICAgICAg ICAgICAgZW50cnlbJ2hvc3QnXSA9aWQKLSAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wyd0 YXJnZXQnXSA9IGx1bgotICAgICAgICAgICAgICAgICAgICAgICAgZGV2c1trZXldID0gZW50cnkK KyAgICAgICAgICAgICAgICAgICAgKGRldiwgZW50cnkpID0gX2V4dHJhY3RfZGV2KGRpciwgcHJv YywgaWQsIGx1bikKKyAgICAgICAgICAgICAgICAgICAgZGV2c1tkZXZdID0gZW50cnkKICAgICAg ICAgICAgICMgZm9yIG5ldyBxbG9naWMgc3lzZnMgbGF5b3V0IChycG9ydCB1bmRlciBkZXZpY2Us IHRoZW4gdGFyZ2V0KQogICAgICAgICAgICAgZm9yIGkgaW4gZmlsdGVyKG1hdGNoX3Jwb3J0LG9z Lmxpc3RkaXIocGF0aCkpOgogICAgICAgICAgICAgICAgIG5ld3BhdGggPSBvcy5wYXRoLmpvaW4o cGF0aCwgaSkKQEAgLTEzOSwxMyArMTI4LDggQEAKICAgICAgICAgICAgICAgICAgICAgICAgIGlm IG5vdCBtYXRjaF9MVU5zKGx1bix0Z3QpOgogICAgICAgICAgICAgICAgICAgICAgICAgICAgIGNv bnRpbnVlCiAgICAgICAgICAgICAgICAgICAgICAgICBkaXIgPSBvcy5wYXRoLmpvaW4oc3lzZnMs bHVuLCJkZXZpY2UiKQotICAgICAgICAgICAgICAgICAgICAgICAgZm9yIGRldiBpbiBmaWx0ZXIo bWF0Y2hfZGV2LG9zLmxpc3RkaXIoZGlyKSk6Ci0gICAgICAgICAgICAgICAgICAgICAgICAgICAg a2V5ID0gZGV2LnJlcGxhY2UoImJsb2NrOiIsIiIpCi0gICAgICAgICAgICAgICAgICAgICAgICAg ICAgZW50cnkgPSB7fQotICAgICAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wydwcm9jbmFt ZSddID0gcHJvYwotICAgICAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wydob3N0J10gPSBp ZAotICAgICAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wyd0YXJnZXQnXSA9IGx1bgotICAg ICAgICAgICAgICAgICAgICAgICAgICAgIGRldnNba2V5XSA9IGVudHJ5CisgICAgICAgICAgICAg ICAgICAgICAgICAoZGV2LCBlbnRyeSkgPSBfZXh0cmFjdF9kZXYoZGlyLCBwcm9jLCBpZCwgbHVu KQorICAgICAgICAgICAgICAgICAgICAgICAgZGV2c1tkZXZdID0gZW50cnkKIAogICAgICAgICAg ICAgIyBmb3IgbmV3IG1wdHNhcyBzeXNmcyBlbnRyaWVzLCBjaGVjayBmb3IgcGh5KiBub2RlCiAg ICAgICAgICAgICBmb3IgaSBpbiBmaWx0ZXIobWF0Y2hfcGh5LG9zLmxpc3RkaXIocGF0aCkpOgpA QCAtMTU2LDIyICsxNDAsMTcgQEAKICAgICAgICAgICAgICAgICAgICAgaWYgbm90IG1hdGNoX0xV TnMobHVuLHRndCk6CiAgICAgICAgICAgICAgICAgICAgICAgICBjb250aW51ZQogICAgICAgICAg ICAgICAgICAgICBkaXIgPSBvcy5wYXRoLmpvaW4oc3lzZnMsbHVuLCJkZXZpY2UiKQotICAgICAg ICAgICAgICAgICAgICBmb3IgZGV2IGluIGZpbHRlcihtYXRjaF9kZXYsb3MubGlzdGRpcihkaXIp KToKLSAgICAgICAgICAgICAgICAgICAgICAgIGtleSA9IGRldi5yZXBsYWNlKCJibG9jazoiLCIi KQotICAgICAgICAgICAgICAgICAgICAgICAgZW50cnkgPSB7fQotICAgICAgICAgICAgICAgICAg ICAgICAgZW50cnlbJ3Byb2NuYW1lJ10gPSBwcm9jCi0gICAgICAgICAgICAgICAgICAgICAgICBl bnRyeVsnaG9zdCddID0gaWQKLSAgICAgICAgICAgICAgICAgICAgICAgIGVudHJ5Wyd0YXJnZXQn XSA9IGx1bgotICAgICAgICAgICAgICAgICAgICAgICAgZGV2c1trZXldID0gZW50cnkKKyAgICAg ICAgICAgICAgICAgICAgKGRldiwgZW50cnkpID0gX2V4dHJhY3RfZGV2KGRpciwgcHJvYywgaWQs IGx1bikKKyAgICAgICAgICAgICAgICAgICAgZGV2c1tkZXZdID0gZW50cnkKICAgICAgICAgICAg IGlmIHBhdGguc3RhcnRzd2l0aChTWVNGU19QQVRIMik6Ci0gICAgICAgICAgICAgICAga2V5ID0g b3MucGF0aC5iYXNlbmFtZShcCi0gICAgICAgICAgICAgICAgICAgIGdsb2IuZ2xvYihvcy5wYXRo LmpvaW4ocGF0aCwiZGV2aWNlIiwiYmxvY2s6KiIpKVswXSkuc3BsaXQoJzonKVsxXQotICAgICAg ICAgICAgICAgIGlmIGRldnMuaGFzX2tleShrZXkpOgorICAgICAgICAgICAgICAgIG9zLnBhdGgu am9pbihwYXRoLCJkZXZpY2UiLCJibG9jazoqIikKKyAgICAgICAgICAgICAgICBkZXYgPSBfZXh0 cmFjdF9kZXZfbmFtZShvcy5wYXRoLmpvaW4ocGF0aCwgJ2RldmljZScpKQorICAgICAgICAgICAg ICAgIGlmIGRldnMuaGFzX2tleShkZXYpOgogICAgICAgICAgICAgICAgICAgICBjb250aW51ZQog ICAgICAgICAgICAgICAgIGhidGwgPSBvcy5wYXRoLmJhc2VuYW1lKHBhdGgpCiAgICAgICAgICAg ICAgICAgKGgsYix0LGwpID0gaGJ0bC5zcGxpdCgnOicpCiAgICAgICAgICAgICAgICAgZW50cnkg PSB7J3Byb2NuYW1lJzpwcm9jLCAnaG9zdCc6aWQsICd0YXJnZXQnOmx9Ci0gICAgICAgICAgICAg ICAgZGV2c1trZXldID0gZW50cnkKKyAgICAgICAgICAgICAgICBkZXZzW2Rldl0gPSBlbnRyeQog CiAgICAgZGljdFsnZGV2cyddID0gZGV2cwogICAgIGRpY3RbJ2FkdCddID0gYWR0CkBAIC0yNTYs NiArMjM1LDMzIEBACiAgICAgcmVnZXggPSByZS5jb21waWxlKCJeYmxvY2s6IikKICAgICByZXR1 cm4gcmVnZXguc2VhcmNoKHMsIDApCiAKK2RlZiBfZXh0cmFjdF9kZXZfbmFtZShkZXZpY2VfZGly KToKKyAgICAiIiJSZXR1cm5zIHRoZSBuYW1lIG9mIHRoZSBibG9jayBkZXZpY2UgZnJvbSBzeXNm cyBlLmcuICdzZGEnIiIiCisgICAga2VybmVsX3ZlcnNpb24gPSBvcy51bmFtZSgpWzJdCisKKyAg ICBpZiBrZXJuZWxfdmVyc2lvbi5zdGFydHN3aXRoKCcyLjYnKToKKyAgICAgICAgIyBzdWItZGly ZWN0b3J5IG9mIGZvcm0gYmxvY2s6c2R4LworICAgICAgICBkZXYgPSBmaWx0ZXIobWF0Y2hfZGV2 LCBvcy5saXN0ZGlyKGRldmljZV9kaXIpKVswXQorICAgICAgICAjIHJlbW92ZSAnYmxvY2s6JyBm cm9tIGVudHJ5IGFuZCByZXR1cm4KKyAgICAgICAgcmV0dXJuIGRldi5sc3RyaXAoJ2Jsb2NrOicp CisgICAgZWxpZiBrZXJuZWxfdmVyc2lvbi5zdGFydHN3aXRoKCczLicpOgorICAgICAgICAjIGRp cmVjdG9yeSBmb3IgZGV2aWNlIG5hbWUgbGl2ZXMgaW5zaWRlIGJsb2NrIGRpcmVjdG9yeSBlLmcu IGJsb2NrL3NkeAorICAgICAgICBkZXYgPSBnbG9iLmdsb2Iob3MucGF0aC5qb2luKGRldmljZV9k aXIsICdibG9jay8qJykpWzBdCisgICAgICAgICMgcHJ1bmUgcGF0aCB0byBleHRyYWN0IHRoZSBk ZXZpY2UgbmFtZQorICAgICAgICByZXR1cm4gb3MucGF0aC5iYXNlbmFtZShkZXYpCisgICAgZWxz ZToKKyAgICAgICAgbXNnID0gJ0tlcm5lbCB2ZXJzaW9uIGRldGVjdGVkOiAlcycgJSBrZXJuZWxf dmVyc2lvbgorICAgICAgICByYWlzZSB4c19lcnJvcnMuWGVuRXJyb3IoJ1Vuc3VwcG9ydGVkS2Vy bmVsJywgbXNnKQorCitkZWYgX2V4dHJhY3RfZGV2KGRldmljZV9kaXIsIHByb2NuYW1lLCBob3N0 LCB0YXJnZXQpOgorICAgICIiIlJldHVybnMgZGV2aWNlIG5hbWUgYW5kIGNyZWF0ZXMgZGljdGlv bmFyeSBlbnRyeSBmb3IgaXQiIiIKKyAgICBkZXYgPSBfZXh0cmFjdF9kZXZfbmFtZShkZXZpY2Vf ZGlyKQorICAgIGVudHJ5ID0ge30KKyAgICBlbnRyeVsncHJvY25hbWUnXSA9IHByb2NuYW1lCisg ICAgZW50cnlbJ2hvc3QnXSA9IGhvc3QKKyAgICBlbnRyeVsndGFyZ2V0J10gPSB0YXJnZXQKKyAg ICByZXR1cm4gKGRldiwgZW50cnkpCisKIGRlZiBzY2FuKHNyb2JqKToKICAgICBzeXN0ZW1yb290 SUQgPSB1dGlsLmdldHJvb3RkZXZJRCgpCiAgICAgaGJhZGljdCA9IHNyb2JqLmhiYWRpY3QK --_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_002_344C0F67BC927847A2C92F9EE358DB0E01224E1417E9LONPMAILBOX_-- From xen-api-bounces@lists.xen.org Thu Jan 17 14:32:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 14:32:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqVl-0000x8-BI; Thu, 17 Jan 2013 14:32:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqVj-0000x0-Q0 for xen-api@lists.xen.org; Thu, 17 Jan 2013 14:32:08 +0000 Received: from [85.158.143.99:23953] by server-2.bemta-4.messagelabs.com id 2E/F5-24322-66B08F05; Thu, 17 Jan 2013 14:32:06 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1358433124!18586618!1 X-Originating-IP: [209.85.215.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 976 invoked from network); 17 Jan 2013 14:32:05 -0000 Received: from mail-la0-f50.google.com (HELO mail-la0-f50.google.com) (209.85.215.50) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 14:32:05 -0000 Received: by mail-la0-f50.google.com with SMTP id er20so971752lab.23 for ; Thu, 17 Jan 2013 06:32:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=sopBpYFDDynClu/RmiYatTKaHcSmE8TFP59JxaYWbGo=; b=P1T/c2AAKiKMtwjftsPG0HjBH0oIjSF1Ssk5DL/9PllpED1ZESBn2Qsa75BXNPHb8h LK112UHm/7Ld/Zv9xLPLW4cdxMlg7Lqarb0zvMS8kuFynKGQTk/UPUx1AZsaRIoaFu13 0KVHD8dT/G6tgOEaIDUwbwT80dkMVO4rgbiw5C8MzylkvVfN4aYvhiipNJxLonFZKjNc JrRpeZNclm28+JuOrGerqYxzJpdyv/uHcLB1ds6LlaL4geWQUW89ciU6pRF004nnGSyo b/IB7/cnSfQctOrHVTBg31zHZf3+YQwOWiqH9ujDyPhxTO8EmaXXnGiIUMmy7ukb+has mLMQ== X-Received: by 10.152.104.112 with SMTP id gd16mr5101662lab.26.1358433124634; Thu, 17 Jan 2013 06:32:04 -0800 (PST) Received: from [172.16.26.11] (b0fb48e2.bb.sky.com. [176.251.72.226]) by mx.google.com with ESMTPS id u5sm876090lbm.8.2013.01.17.06.32.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jan 2013 06:32:03 -0800 (PST) Message-ID: <50F80B5E.1050402@xen.org> Date: Thu, 17 Jan 2013 14:31:58 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> <344C0F67BC927847A2C92F9EE358DB0E01224E5B3E64@LONPMAILBOX01.citrite.net> <50F807DC.3000101@xen.org> In-Reply-To: <50F807DC.3000101@xen.org> Subject: Re: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org OOps, meant to say Dave! On 17/01/2013 14:17, Lars Kurth wrote: > Scott, > > thank you for this. I am going to add categories to the page, such > that they can be more easily found. > > Please make sure you do this in future. Uncategorized pages are really > hard to find on the wiki. More info at: > - http://wiki.xen.org/wiki/Categories_for_Authors > - http://wiki.xen.org/wiki/Category:Templates also useful > Regards > Lars > > On 11/01/2013 18:58, James Bulpin wrote: >> Feeling brave I've tried this on CentOS 6.3 with Xen 4.2. Here's >> how it went... >> >> I used the "Software development workstation" installation base for >> CentOS 6.3 (x86_64) which meant I got a certain amount of virtualisation >> infrastructure including a "virbr0" NATed bridge. I prefer basic L2 >> bridging so I manually created a xenbr0 in the traditional manner. I >> installed Xen 4.2.1 and a suitable 3.4 kernel. >> >> I chose to compile vncterm from the source at >> https://github.com/xen-org/vncterm - this uses the old xs.h filename for >> the xenstore headers so I have to change this to xenstore.h to make it >> build against 4.2. >> >> I used the latest binary download of opam to install ocaml 4.00.1. Being >> a local installation this meant the paths differed from Dave's tutorial >> being ~/.opam/4.00.1/ instead of ~/.opam/system/ >> >> I hit an error building xenopsd because it was depending on xenctrl >> 4.1.0 >> rather than just the latest version - Dave fixed this in his repo. >> >> To run xenopsd I have to uncomment the vncterm config line in >> xenopsd.conf to point to the binary. In the same file I had to uncomment >> the hvmloader line and remove the quotes (xenopsd was treating them >> literally) >> >> For the VM storage I chose to use LVM to fit with the current "phy:" >> constraint. >> >> Trying to start a PV guest hit a few problems: >> >> 1. xenopsd gave an error saying it had no bootable devices - this was >> because the devices list was hard wired to empty in the CLI, Dave >> fixed this in the repo >> >> 2. xenopsd assumes that pygrub has the --default_args, --extra_args >> and >> --vm arguments present in the XenServer/XCP version of pygrub >> but not >> present in the Xen 4.2 version. I patched the latter to add these. >> >> 3. xenopsd complains of an invalid result from the domain builder. >> Dave >> is currently working on this. >> >> Trying a HVM guest led to a different set of challenges: >> >> 1. xenopsd was hanging waiting to plug the VBD - this turns out to be >> because the hotplug scripts were not running because xl had >> disabled >> them (by default xl runs these scripts itself but this can be >> overridden by setting "run_hotplug_scripts=0" in >> /etc/xen/xl.conf). I >> suspect this problem will go away when Rob does the xenopsd libxl >> port. >> >> 2. xenopsd is using a VIF hotplug scripts that is very XenServer/XCP >> centric and doesn't run to completion on CentOS 6.3. This was >> configured in the automatically generaled xenopsd.conf so I instead >> changed this to use /etc/xen/scripts/vif-bridge instead. >> >> 3. xenopsd doesn't put the "bridge" key in the usual backend xenstore >> location (/local/domain/0/backend/vif//) so the Xen >> 4.2 vif script defaulted to the first bridge, not the one I had >> configured. >> >> 4. xenopsd was hanging waiting for a hotplug event on the VIF but was >> watching /xapi//vif//hotplug which would never be >> touched by Xen 4.2 hotplug scripts. To workaround this I manually >> created that entry after each VM start >> >> 5. qemu-dm-wrapper would always silently fail when run by xenopsd but >> not when run interactively. This is because it tried to setrlimit a >> value with the soft limit being higher than the hard limit. I >> put in >> a simple fix to avoid this. >> >> 6. qemu-dm-wrapper would always fail because it hard-coded the path to >> xenstore-write in /usr/sbin but it's in /usr/bin on my system. I >> fixed this locally but w search path will be useful in the future. >> >> So in summary with a few tweaks and workarounds I can no run HVM guests >> on CentOS 6.3 using xenopsd. I encourage others to try this on your >> distro of choice. >> >> Bugs have been filed at https://github.com/xen-org/xenopsd/issues >> >> Cheers, >> James >> >>> -----Original Message----- >>> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >>> bounces@lists.xen.org] On Behalf Of Dave Scott >>> Sent: 04 January 2013 15:44 >>> To: xen-api@lists.xen.org >>> Subject: [Xen-API] running latest dev versions of xenopsd on >>> Debian/Ubuntu >>> >>> Hi, >>> >>> I've written a wiki page describing how to build the latest development >>> version of "xenopsd" (and its dependencies) from source: >>> >>> http://wiki.xen.org/wiki/Building_Xenopsd >>> >>> "xenopsd" is the name of the domain manager of the XCP toolstack -- it >>> is responsible for starting, stopping, migrating VMs. >>> >>> Being able to build the development version is really useful if you >>> want to: >>> * check out a new feature >>> * reproduce a bug >>> * test a fix >>> >>> Let me know if you try this and have any problems or suggestions! >>> >>> There are a couple more components of the XCP toolstack that need some >>> fixups so they can build easily, in particular: >>> * squeezed: manages memory ballooning >>> * networkd: configures VM networking >>> * rrdd: collects and archives performance statistics >>> * xapi: manages the overall resource pool >>> >>> Hopefully we can work on these one-by-one until they are all as easy to >>> build as xenopsd. >>> >>> Cheers, >>> Dave >>> >>> _______________________________________________ >>> Xen-api mailing list >>> Xen-api@lists.xen.org >>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 14:32:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 14:32:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqVl-0000x8-BI; Thu, 17 Jan 2013 14:32:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqVj-0000x0-Q0 for xen-api@lists.xen.org; Thu, 17 Jan 2013 14:32:08 +0000 Received: from [85.158.143.99:23953] by server-2.bemta-4.messagelabs.com id 2E/F5-24322-66B08F05; Thu, 17 Jan 2013 14:32:06 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1358433124!18586618!1 X-Originating-IP: [209.85.215.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 976 invoked from network); 17 Jan 2013 14:32:05 -0000 Received: from mail-la0-f50.google.com (HELO mail-la0-f50.google.com) (209.85.215.50) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2013 14:32:05 -0000 Received: by mail-la0-f50.google.com with SMTP id er20so971752lab.23 for ; Thu, 17 Jan 2013 06:32:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=sopBpYFDDynClu/RmiYatTKaHcSmE8TFP59JxaYWbGo=; b=P1T/c2AAKiKMtwjftsPG0HjBH0oIjSF1Ssk5DL/9PllpED1ZESBn2Qsa75BXNPHb8h LK112UHm/7Ld/Zv9xLPLW4cdxMlg7Lqarb0zvMS8kuFynKGQTk/UPUx1AZsaRIoaFu13 0KVHD8dT/G6tgOEaIDUwbwT80dkMVO4rgbiw5C8MzylkvVfN4aYvhiipNJxLonFZKjNc JrRpeZNclm28+JuOrGerqYxzJpdyv/uHcLB1ds6LlaL4geWQUW89ciU6pRF004nnGSyo b/IB7/cnSfQctOrHVTBg31zHZf3+YQwOWiqH9ujDyPhxTO8EmaXXnGiIUMmy7ukb+has mLMQ== X-Received: by 10.152.104.112 with SMTP id gd16mr5101662lab.26.1358433124634; Thu, 17 Jan 2013 06:32:04 -0800 (PST) Received: from [172.16.26.11] (b0fb48e2.bb.sky.com. [176.251.72.226]) by mx.google.com with ESMTPS id u5sm876090lbm.8.2013.01.17.06.32.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jan 2013 06:32:03 -0800 (PST) Message-ID: <50F80B5E.1050402@xen.org> Date: Thu, 17 Jan 2013 14:31:58 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <81A73678E76EA642801C8F2E4823AD21012F0D72EBEE@LONPMAILBOX01.citrite.net> <344C0F67BC927847A2C92F9EE358DB0E01224E5B3E64@LONPMAILBOX01.citrite.net> <50F807DC.3000101@xen.org> In-Reply-To: <50F807DC.3000101@xen.org> Subject: Re: [Xen-API] running latest dev versions of xenopsd on Debian/Ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org OOps, meant to say Dave! On 17/01/2013 14:17, Lars Kurth wrote: > Scott, > > thank you for this. I am going to add categories to the page, such > that they can be more easily found. > > Please make sure you do this in future. Uncategorized pages are really > hard to find on the wiki. More info at: > - http://wiki.xen.org/wiki/Categories_for_Authors > - http://wiki.xen.org/wiki/Category:Templates also useful > Regards > Lars > > On 11/01/2013 18:58, James Bulpin wrote: >> Feeling brave I've tried this on CentOS 6.3 with Xen 4.2. Here's >> how it went... >> >> I used the "Software development workstation" installation base for >> CentOS 6.3 (x86_64) which meant I got a certain amount of virtualisation >> infrastructure including a "virbr0" NATed bridge. I prefer basic L2 >> bridging so I manually created a xenbr0 in the traditional manner. I >> installed Xen 4.2.1 and a suitable 3.4 kernel. >> >> I chose to compile vncterm from the source at >> https://github.com/xen-org/vncterm - this uses the old xs.h filename for >> the xenstore headers so I have to change this to xenstore.h to make it >> build against 4.2. >> >> I used the latest binary download of opam to install ocaml 4.00.1. Being >> a local installation this meant the paths differed from Dave's tutorial >> being ~/.opam/4.00.1/ instead of ~/.opam/system/ >> >> I hit an error building xenopsd because it was depending on xenctrl >> 4.1.0 >> rather than just the latest version - Dave fixed this in his repo. >> >> To run xenopsd I have to uncomment the vncterm config line in >> xenopsd.conf to point to the binary. In the same file I had to uncomment >> the hvmloader line and remove the quotes (xenopsd was treating them >> literally) >> >> For the VM storage I chose to use LVM to fit with the current "phy:" >> constraint. >> >> Trying to start a PV guest hit a few problems: >> >> 1. xenopsd gave an error saying it had no bootable devices - this was >> because the devices list was hard wired to empty in the CLI, Dave >> fixed this in the repo >> >> 2. xenopsd assumes that pygrub has the --default_args, --extra_args >> and >> --vm arguments present in the XenServer/XCP version of pygrub >> but not >> present in the Xen 4.2 version. I patched the latter to add these. >> >> 3. xenopsd complains of an invalid result from the domain builder. >> Dave >> is currently working on this. >> >> Trying a HVM guest led to a different set of challenges: >> >> 1. xenopsd was hanging waiting to plug the VBD - this turns out to be >> because the hotplug scripts were not running because xl had >> disabled >> them (by default xl runs these scripts itself but this can be >> overridden by setting "run_hotplug_scripts=0" in >> /etc/xen/xl.conf). I >> suspect this problem will go away when Rob does the xenopsd libxl >> port. >> >> 2. xenopsd is using a VIF hotplug scripts that is very XenServer/XCP >> centric and doesn't run to completion on CentOS 6.3. This was >> configured in the automatically generaled xenopsd.conf so I instead >> changed this to use /etc/xen/scripts/vif-bridge instead. >> >> 3. xenopsd doesn't put the "bridge" key in the usual backend xenstore >> location (/local/domain/0/backend/vif//) so the Xen >> 4.2 vif script defaulted to the first bridge, not the one I had >> configured. >> >> 4. xenopsd was hanging waiting for a hotplug event on the VIF but was >> watching /xapi//vif//hotplug which would never be >> touched by Xen 4.2 hotplug scripts. To workaround this I manually >> created that entry after each VM start >> >> 5. qemu-dm-wrapper would always silently fail when run by xenopsd but >> not when run interactively. This is because it tried to setrlimit a >> value with the soft limit being higher than the hard limit. I >> put in >> a simple fix to avoid this. >> >> 6. qemu-dm-wrapper would always fail because it hard-coded the path to >> xenstore-write in /usr/sbin but it's in /usr/bin on my system. I >> fixed this locally but w search path will be useful in the future. >> >> So in summary with a few tweaks and workarounds I can no run HVM guests >> on CentOS 6.3 using xenopsd. I encourage others to try this on your >> distro of choice. >> >> Bugs have been filed at https://github.com/xen-org/xenopsd/issues >> >> Cheers, >> James >> >>> -----Original Message----- >>> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >>> bounces@lists.xen.org] On Behalf Of Dave Scott >>> Sent: 04 January 2013 15:44 >>> To: xen-api@lists.xen.org >>> Subject: [Xen-API] running latest dev versions of xenopsd on >>> Debian/Ubuntu >>> >>> Hi, >>> >>> I've written a wiki page describing how to build the latest development >>> version of "xenopsd" (and its dependencies) from source: >>> >>> http://wiki.xen.org/wiki/Building_Xenopsd >>> >>> "xenopsd" is the name of the domain manager of the XCP toolstack -- it >>> is responsible for starting, stopping, migrating VMs. >>> >>> Being able to build the development version is really useful if you >>> want to: >>> * check out a new feature >>> * reproduce a bug >>> * test a fix >>> >>> Let me know if you try this and have any problems or suggestions! >>> >>> There are a couple more components of the XCP toolstack that need some >>> fixups so they can build easily, in particular: >>> * squeezed: manages memory ballooning >>> * networkd: configures VM networking >>> * rrdd: collects and archives performance statistics >>> * xapi: manages the overall resource pool >>> >>> Hopefully we can work on these one-by-one until they are all as easy to >>> build as xenopsd. >>> >>> Cheers, >>> Dave >>> >>> _______________________________________________ >>> Xen-api mailing list >>> Xen-api@lists.xen.org >>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 14:32:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 14:32:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqVv-0000xd-Hn; Thu, 17 Jan 2013 14:32:19 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqVu-0000xX-7B for xen-api@lists.xen.org; Thu, 17 Jan 2013 14:32:18 +0000 Received: from [193.109.254.147:44260] by server-15.bemta-14.messagelabs.com id E0/55-05116-17B08F05; Thu, 17 Jan 2013 14:32:17 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-12.tower-27.messagelabs.com!1358433062!9226878!1 X-Originating-IP: [80.12.242.128] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27653 invoked from network); 17 Jan 2013 14:31:02 -0000 Received: from smtp06.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.128) by server-12.tower-27.messagelabs.com with SMTP; 17 Jan 2013 14:31:02 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d29 with ME id p2X01k01V3zjds1032X1rK; Thu, 17 Jan 2013 15:31:02 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id DE959161BB4; Thu, 17 Jan 2013 15:31:00 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nKirnm68hK8v; Thu, 17 Jan 2013 15:31:00 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 55275161BBA; Thu, 17 Jan 2013 15:31:00 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id gIyiukNKsPwa; Thu, 17 Jan 2013 15:30:59 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 9A6CE161BB4; Thu, 17 Jan 2013 15:30:59 +0100 (CET) Message-ID: <50F80B23.7040105@tranquil-it-systems.fr> Date: Thu, 17 Jan 2013 15:30:59 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Anatoliy.Poloz@onetelecom.od.ua References: <50F51D97.9020604@onetelecom.od.ua> In-Reply-To: <50F51D97.9020604@onetelecom.od.ua> Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Anatoliy, > I tried to import a previously saved VM > with the command > "#xe vm-import filename =3D / > var/run/sr-mount/c0da11ed-72d8-1a58-aa94-127035fa28d7/infr-samba-2013-01-= 02_01-04-01.xva > sr-uuid =3D c0da11ed-72d8-1a58-aa94-127035fa28d7 force=3Dtrue" from your command line, it seems like you are storing your xva exports = on the same directory where the ext3 SR is configured. You should put your xva on another storage that is not a SR. > c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr > > the size of imported file 123G > > but failed with message "Fatal error: exception Unix.Unix_error(13, > "tcsetattr", "")" > and hung task > uuid ( RO) : be568259-c9cd-be13-7da5-8ed2a222e898 > name-label ( RO): VM import > name-description ( RO): > status ( RO): pending > progress ( RO): 0.720 > > is there any chance to recover VM? You should clean up your SR by removing everything that does not belong = to XCP, then run a sr-scan, and try to import your xva again. In case you have some doubt on the state of your xva exported vm, there = is a tool somewhere to check if the xva is corrupted or not, something = called xva_verify.exe, there is probably a equivalent binary for linux. Cheers, Denis > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 14:32:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 14:32:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqVv-0000xd-Hn; Thu, 17 Jan 2013 14:32:19 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvqVu-0000xX-7B for xen-api@lists.xen.org; Thu, 17 Jan 2013 14:32:18 +0000 Received: from [193.109.254.147:44260] by server-15.bemta-14.messagelabs.com id E0/55-05116-17B08F05; Thu, 17 Jan 2013 14:32:17 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-12.tower-27.messagelabs.com!1358433062!9226878!1 X-Originating-IP: [80.12.242.128] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27653 invoked from network); 17 Jan 2013 14:31:02 -0000 Received: from smtp06.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.128) by server-12.tower-27.messagelabs.com with SMTP; 17 Jan 2013 14:31:02 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d29 with ME id p2X01k01V3zjds1032X1rK; Thu, 17 Jan 2013 15:31:02 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id DE959161BB4; Thu, 17 Jan 2013 15:31:00 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nKirnm68hK8v; Thu, 17 Jan 2013 15:31:00 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 55275161BBA; Thu, 17 Jan 2013 15:31:00 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id gIyiukNKsPwa; Thu, 17 Jan 2013 15:30:59 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 9A6CE161BB4; Thu, 17 Jan 2013 15:30:59 +0100 (CET) Message-ID: <50F80B23.7040105@tranquil-it-systems.fr> Date: Thu, 17 Jan 2013 15:30:59 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Anatoliy.Poloz@onetelecom.od.ua References: <50F51D97.9020604@onetelecom.od.ua> In-Reply-To: <50F51D97.9020604@onetelecom.od.ua> Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] vm import error X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Anatoliy, > I tried to import a previously saved VM > with the command > "#xe vm-import filename =3D / > var/run/sr-mount/c0da11ed-72d8-1a58-aa94-127035fa28d7/infr-samba-2013-01-= 02_01-04-01.xva > sr-uuid =3D c0da11ed-72d8-1a58-aa94-127035fa28d7 force=3Dtrue" from your command line, it seems like you are storing your xva exports = on the same directory where the ext3 SR is configured. You should put your xva on another storage that is not a SR. > c0da11ed-72d8-1a58-aa94-127035a28d7 - ext3 local sr > > the size of imported file 123G > > but failed with message "Fatal error: exception Unix.Unix_error(13, > "tcsetattr", "")" > and hung task > uuid ( RO) : be568259-c9cd-be13-7da5-8ed2a222e898 > name-label ( RO): VM import > name-description ( RO): > status ( RO): pending > progress ( RO): 0.720 > > is there any chance to recover VM? You should clean up your SR by removing everything that does not belong = to XCP, then run a sr-scan, and try to import your xva again. In case you have some doubt on the state of your xva exported vm, there = is a tool somewhere to check if the xva is corrupted or not, something = called xva_verify.exe, there is probably a equivalent binary for linux. Cheers, Denis > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 16:00:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 16:00:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvrtO-0000Ac-9O; Thu, 17 Jan 2013 16:00:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvrtL-00009w-KW; Thu, 17 Jan 2013 16:00:36 +0000 Received: from [85.158.143.99:39042] by server-1.bemta-4.messagelabs.com id A6/3F-18740-22028F05; Thu, 17 Jan 2013 16:00:34 +0000 X-Env-Sender: martinu@vshosting.cz X-Msg-Ref: server-7.tower-216.messagelabs.com!1358438400!24401795!1 X-Originating-IP: [78.24.8.155] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28886 invoked from network); 17 Jan 2013 16:00:09 -0000 Received: from pipa-ng.vshosting.cz (HELO pipa-ng.vshosting.cz) (78.24.8.155) by server-7.tower-216.messagelabs.com with SMTP; 17 Jan 2013 16:00:09 -0000 Received: from localhost (localhost [127.0.0.1]) by pipa-ng.vshosting.cz (Postfix) with ESMTP id DE8092F0C089; Thu, 17 Jan 2013 16:59:58 +0100 (CET) X-Virus-Scanned: amavisd-new at pipa-ng.vshosting.cz Received: from pipa-ng.vshosting.cz ([127.0.0.1]) by localhost (pipa-ng.vshosting.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bd9Nak8FoHu7; Thu, 17 Jan 2013 16:59:55 +0100 (CET) Received: from [78.24.8.73] (ts.vshosting.cz [78.24.8.73]) by pipa-ng.vshosting.cz (Postfix) with ESMTPSA id 8B4AB2F0C084; Thu, 17 Jan 2013 16:59:55 +0100 (CET) Message-ID: <50F81FFC.1060201@vshosting.cz> Date: Thu, 17 Jan 2013 16:59:56 +0100 From: =?ISO-8859-2?Q?Jan_Martin=F9?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-API] XCP 1.1 SR_BACKEND_FAILURE_46 The VDI is not available [opterr=VDI already attached RW] issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-2"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello I have a problem with VDI already attached RW in the "adding tag" in = blktap2. This issue is on all hosts in pool with attached lvmoiscsi SR. Is there any solution to this problem? /var/log/SMlog: [32484] 2013-01-17 14:59:44.200883 vdi_activate {'sr_uuid': = 'e33281eb-ba4c-3829-9b61-7c64764dff9c', 'subtask_of': = 'OpaqueRef:78dd7c48-383b-253c-9c2d-a60edcb9e2e1', 'vdi_ref': = 'OpaqueRef:9e3252f6-403b-7045-2147-401beeafc8ca', 'vdi_on_boot': = 'persist', 'args': ['true'], 'vdi_location': = 'ff54dd4f-5ad3-4cf2-814f-9abd12b1045e', 'host_ref': = 'OpaqueRef:a8aeb980-a584-bf7f-d9dd-377f27d030f7', 'session_ref': = 'OpaqueRef:5b8af71e-3432-0ce6-3ed4-4fe2fe0197a7', 'device_config': = {'target': '172.16.132.1', 'chappassword_secret': = 'b47a23a5-4939-d613-8641-51c740b8dd87', 'chapuser': 'cloud1', = 'targetIQN': 'iqn.2011-04.cz.vshosting:storage1.cloud1', 'SRmaster': = 'true', 'device': '/dev/disk/by-id/scsi-26c756e3020636239', 'SCSIid': = '26c756e3020636239', 'targetlist': '172.16.132.1'}, 'command': = 'vdi_activate', 'vdi_allow_caching': 'false', 'sr_ref': = 'OpaqueRef:9fc8a54a-dd45-4313-f783-7883b3335604', 'vdi_uuid': = 'ff54dd4f-5ad3-4cf2-814f-9abd12b1045e'} [32484] 2013-01-17 14:59:44.201233 blktap2.activate [32484] 2013-01-17 14:59:44.201476 lock: acquired = /var/lock/sm/ff54dd4f-5ad3-4cf2-814f-9abd12b1045e/vdi [32484] 2013-01-17 14:59:44.201567 Adding tag to: = ff54dd4f-5ad3-4cf2-814f-9abd12b1045e [32484] 2013-01-17 14:59:44.238928 ***** BLKTAP2:: EXCEPTION util.SMException, VDI = ff54dd4f-5ad3-4cf2-814f-9abd12b1045e already attached RW File "/opt/xensource/sm/blktap2.py", line 32, in wrapper ret =3D op(self, *args) File "/opt/xensource/sm/blktap2.py", line 1297, in _activate_locked if not self._add_tag(vdi_uuid): File "/opt/xensource/sm/blktap2.py", line 1230, in _add_tag raise util.SMException("VDI %s already attached RW" % vdi_uuid) [32484] 2013-01-17 14:59:44.272130 Raising exception [46, The VDI = is not available [opterr=3DVDI ff54dd4f-5ad3-4cf2-814f-9abd12b1045e = already attached RW]] [32484] 2013-01-17 14:59:44.272325 lock: released = /var/lock/sm/ff54dd4f-5ad3-4cf2-814f-9abd12b1045e/vdi [32484] 2013-01-17 14:59:44.272847 ***** vdi_activate: EXCEPTION = SR.SROSError, The VDI is not available [opterr=3DVDI = ff54dd4f-5ad3-4cf2-814f-9abd12b1045e already attached RW] File "/opt/xensource/sm/SRCommand.py", line 94, in run return self._run_locked(sr) File "/opt/xensource/sm/SRCommand.py", line 131, in _run_locked return self._run(sr, target) File "/opt/xensource/sm/SRCommand.py", line 183, in _run caching_params) File "/opt/xensource/sm/blktap2.py", line 1283, in activate if self._activate_locked(sr_uuid, vdi_uuid, caching_params): File "/opt/xensource/sm/blktap2.py", line 40, in wrapper raise xs_errors.XenError(excType, opterr=3Dmsg) File "/opt/xensource/sm/xs_errors.py", line 49, in __init__ raise SR.SROSError(errorcode, errormessage) -- = S pozdravem Jan Martin=F9 VSHosting s.r.o. Telefon: 246 035 835 Email: martinu@vshosting.cz www.vshosting.cz _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 16:00:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 16:00:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvrtO-0000Ac-9O; Thu, 17 Jan 2013 16:00:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvrtL-00009w-KW; Thu, 17 Jan 2013 16:00:36 +0000 Received: from [85.158.143.99:39042] by server-1.bemta-4.messagelabs.com id A6/3F-18740-22028F05; Thu, 17 Jan 2013 16:00:34 +0000 X-Env-Sender: martinu@vshosting.cz X-Msg-Ref: server-7.tower-216.messagelabs.com!1358438400!24401795!1 X-Originating-IP: [78.24.8.155] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28886 invoked from network); 17 Jan 2013 16:00:09 -0000 Received: from pipa-ng.vshosting.cz (HELO pipa-ng.vshosting.cz) (78.24.8.155) by server-7.tower-216.messagelabs.com with SMTP; 17 Jan 2013 16:00:09 -0000 Received: from localhost (localhost [127.0.0.1]) by pipa-ng.vshosting.cz (Postfix) with ESMTP id DE8092F0C089; Thu, 17 Jan 2013 16:59:58 +0100 (CET) X-Virus-Scanned: amavisd-new at pipa-ng.vshosting.cz Received: from pipa-ng.vshosting.cz ([127.0.0.1]) by localhost (pipa-ng.vshosting.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bd9Nak8FoHu7; Thu, 17 Jan 2013 16:59:55 +0100 (CET) Received: from [78.24.8.73] (ts.vshosting.cz [78.24.8.73]) by pipa-ng.vshosting.cz (Postfix) with ESMTPSA id 8B4AB2F0C084; Thu, 17 Jan 2013 16:59:55 +0100 (CET) Message-ID: <50F81FFC.1060201@vshosting.cz> Date: Thu, 17 Jan 2013 16:59:56 +0100 From: =?ISO-8859-2?Q?Jan_Martin=F9?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-API] XCP 1.1 SR_BACKEND_FAILURE_46 The VDI is not available [opterr=VDI already attached RW] issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-2"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello I have a problem with VDI already attached RW in the "adding tag" in = blktap2. This issue is on all hosts in pool with attached lvmoiscsi SR. Is there any solution to this problem? /var/log/SMlog: [32484] 2013-01-17 14:59:44.200883 vdi_activate {'sr_uuid': = 'e33281eb-ba4c-3829-9b61-7c64764dff9c', 'subtask_of': = 'OpaqueRef:78dd7c48-383b-253c-9c2d-a60edcb9e2e1', 'vdi_ref': = 'OpaqueRef:9e3252f6-403b-7045-2147-401beeafc8ca', 'vdi_on_boot': = 'persist', 'args': ['true'], 'vdi_location': = 'ff54dd4f-5ad3-4cf2-814f-9abd12b1045e', 'host_ref': = 'OpaqueRef:a8aeb980-a584-bf7f-d9dd-377f27d030f7', 'session_ref': = 'OpaqueRef:5b8af71e-3432-0ce6-3ed4-4fe2fe0197a7', 'device_config': = {'target': '172.16.132.1', 'chappassword_secret': = 'b47a23a5-4939-d613-8641-51c740b8dd87', 'chapuser': 'cloud1', = 'targetIQN': 'iqn.2011-04.cz.vshosting:storage1.cloud1', 'SRmaster': = 'true', 'device': '/dev/disk/by-id/scsi-26c756e3020636239', 'SCSIid': = '26c756e3020636239', 'targetlist': '172.16.132.1'}, 'command': = 'vdi_activate', 'vdi_allow_caching': 'false', 'sr_ref': = 'OpaqueRef:9fc8a54a-dd45-4313-f783-7883b3335604', 'vdi_uuid': = 'ff54dd4f-5ad3-4cf2-814f-9abd12b1045e'} [32484] 2013-01-17 14:59:44.201233 blktap2.activate [32484] 2013-01-17 14:59:44.201476 lock: acquired = /var/lock/sm/ff54dd4f-5ad3-4cf2-814f-9abd12b1045e/vdi [32484] 2013-01-17 14:59:44.201567 Adding tag to: = ff54dd4f-5ad3-4cf2-814f-9abd12b1045e [32484] 2013-01-17 14:59:44.238928 ***** BLKTAP2:: EXCEPTION util.SMException, VDI = ff54dd4f-5ad3-4cf2-814f-9abd12b1045e already attached RW File "/opt/xensource/sm/blktap2.py", line 32, in wrapper ret =3D op(self, *args) File "/opt/xensource/sm/blktap2.py", line 1297, in _activate_locked if not self._add_tag(vdi_uuid): File "/opt/xensource/sm/blktap2.py", line 1230, in _add_tag raise util.SMException("VDI %s already attached RW" % vdi_uuid) [32484] 2013-01-17 14:59:44.272130 Raising exception [46, The VDI = is not available [opterr=3DVDI ff54dd4f-5ad3-4cf2-814f-9abd12b1045e = already attached RW]] [32484] 2013-01-17 14:59:44.272325 lock: released = /var/lock/sm/ff54dd4f-5ad3-4cf2-814f-9abd12b1045e/vdi [32484] 2013-01-17 14:59:44.272847 ***** vdi_activate: EXCEPTION = SR.SROSError, The VDI is not available [opterr=3DVDI = ff54dd4f-5ad3-4cf2-814f-9abd12b1045e already attached RW] File "/opt/xensource/sm/SRCommand.py", line 94, in run return self._run_locked(sr) File "/opt/xensource/sm/SRCommand.py", line 131, in _run_locked return self._run(sr, target) File "/opt/xensource/sm/SRCommand.py", line 183, in _run caching_params) File "/opt/xensource/sm/blktap2.py", line 1283, in activate if self._activate_locked(sr_uuid, vdi_uuid, caching_params): File "/opt/xensource/sm/blktap2.py", line 40, in wrapper raise xs_errors.XenError(excType, opterr=3Dmsg) File "/opt/xensource/sm/xs_errors.py", line 49, in __init__ raise SR.SROSError(errorcode, errormessage) -- = S pozdravem Jan Martin=F9 VSHosting s.r.o. Telefon: 246 035 835 Email: martinu@vshosting.cz www.vshosting.cz _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 18:12:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 18:12:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvtxH-0002vL-3s; Thu, 17 Jan 2013 18:12:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvtxF-0002vE-DP for xen-api@lists.xen.org; Thu, 17 Jan 2013 18:12:45 +0000 Received: from [85.158.143.99:58289] by server-3.bemta-4.messagelabs.com id 33/23-19220-C1F38F05; Thu, 17 Jan 2013 18:12:44 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1358446362!21363919!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22054 invoked from network); 17 Jan 2013 18:12:43 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-6.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 18:12:43 -0000 Received: from [201.122.115.101] (port=44728 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TvtxB-0003Wa-9G for xen-api@lists.xen.org; Thu, 17 Jan 2013 12:12:42 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 416A1A209 for ; Thu, 17 Jan 2013 12:09:21 -0600 (CST) Message-ID: <50F83F0F.6020803@ondore.com> Date: Thu, 17 Jan 2013 12:12:31 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50F70A3E.3060908@ondore.com> <344C0F67BC927847A2C92F9EE358DB0E01224E896531@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E896531@LONPMAILBOX01.citrite.net> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Serial console with IPMI SOL X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. El 17/01/13 05:15, James Bulpin escribi=F3: > Try reversing the order of the two console=3D args in the kernel > command line. Linux uses the rightmost of these for /dev/console, > i.e. you want the hvc0 one last. Got it. If I put the consoles as "console=3Dtty0 xencons=3Dhvc console=3Dhvc0", the startup messages become = visible on the serial console. >> -----Original Message----- >> - Made inttab to use serial as console (Wiki suggests using agetty >> instead of getty, don't know how relevant this might be): >> T0:2345:respawn:/sbin/getty -L ttyS1 115200 vt100 I must add, the configuration of getty is unnecessary in /etc/inittab. = The serial console is mapped to hvc0, inittab already defines a spawn of = a getty on that tty. Another thing, /sbin/getty is simply unavailable on XCP 1.6 default = install. For any purpose, /sbin/mingetty or /sbin/agetty should be used. >> - Added 'ttyS1' to /etc/securetty (not sure if really needed). A login on a serial console appears as attached to TTY hvc0, no = alteration of securetty is required. >> (Note the incomplete line at 9.990896, that's also an issue) It still does something wired around [ 10.000000], when detecting USB. The output changed slightly after changing the console order in kernel's = boot parameters. Was: [ 9.870053] usb 1-1.6.1: new high speed USB device using ehci_hcd and = address 4 [ 9.990896] u[ 20.637067] kjournald starting. Commit interval 15 = seconds [ 20.637083] EXT3-fs: mounted filesystem with ordered data mode. Now: [ 10.524283] usb 1-1.6.1: new high speed USB device using ehci_hcd and = address 4 [ 10.645127] usbScanning and configuring dmraid supported devices Creating root device. Mounting root filesystem. [ 21.243566] kjournald starting. Commit interval 15 seconds Setting up other filesystems. Setting up new root fs [ 21.243586] EXT3-fs: mounted filesystem with ordered data mode. Thank you. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 18:12:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 18:12:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvtxH-0002vL-3s; Thu, 17 Jan 2013 18:12:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvtxF-0002vE-DP for xen-api@lists.xen.org; Thu, 17 Jan 2013 18:12:45 +0000 Received: from [85.158.143.99:58289] by server-3.bemta-4.messagelabs.com id 33/23-19220-C1F38F05; Thu, 17 Jan 2013 18:12:44 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1358446362!21363919!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22054 invoked from network); 17 Jan 2013 18:12:43 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-6.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 18:12:43 -0000 Received: from [201.122.115.101] (port=44728 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TvtxB-0003Wa-9G for xen-api@lists.xen.org; Thu, 17 Jan 2013 12:12:42 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 416A1A209 for ; Thu, 17 Jan 2013 12:09:21 -0600 (CST) Message-ID: <50F83F0F.6020803@ondore.com> Date: Thu, 17 Jan 2013 12:12:31 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <50F70A3E.3060908@ondore.com> <344C0F67BC927847A2C92F9EE358DB0E01224E896531@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E896531@LONPMAILBOX01.citrite.net> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-API] XCP 1.6 Serial console with IPMI SOL X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello. El 17/01/13 05:15, James Bulpin escribi=F3: > Try reversing the order of the two console=3D args in the kernel > command line. Linux uses the rightmost of these for /dev/console, > i.e. you want the hvc0 one last. Got it. If I put the consoles as "console=3Dtty0 xencons=3Dhvc console=3Dhvc0", the startup messages become = visible on the serial console. >> -----Original Message----- >> - Made inttab to use serial as console (Wiki suggests using agetty >> instead of getty, don't know how relevant this might be): >> T0:2345:respawn:/sbin/getty -L ttyS1 115200 vt100 I must add, the configuration of getty is unnecessary in /etc/inittab. = The serial console is mapped to hvc0, inittab already defines a spawn of = a getty on that tty. Another thing, /sbin/getty is simply unavailable on XCP 1.6 default = install. For any purpose, /sbin/mingetty or /sbin/agetty should be used. >> - Added 'ttyS1' to /etc/securetty (not sure if really needed). A login on a serial console appears as attached to TTY hvc0, no = alteration of securetty is required. >> (Note the incomplete line at 9.990896, that's also an issue) It still does something wired around [ 10.000000], when detecting USB. The output changed slightly after changing the console order in kernel's = boot parameters. Was: [ 9.870053] usb 1-1.6.1: new high speed USB device using ehci_hcd and = address 4 [ 9.990896] u[ 20.637067] kjournald starting. Commit interval 15 = seconds [ 20.637083] EXT3-fs: mounted filesystem with ordered data mode. Now: [ 10.524283] usb 1-1.6.1: new high speed USB device using ehci_hcd and = address 4 [ 10.645127] usbScanning and configuring dmraid supported devices Creating root device. Mounting root filesystem. [ 21.243566] kjournald starting. Commit interval 15 seconds Setting up other filesystems. Setting up new root fs [ 21.243586] EXT3-fs: mounted filesystem with ordered data mode. Thank you. -- = Alexandre Kouznetsov _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 17 18:35:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 18:35:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvuIz-0003VV-WD; Thu, 17 Jan 2013 18:35:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvuIx-0003VQ-Q3 for xen-api@lists.xen.org; Thu, 17 Jan 2013 18:35:12 +0000 Received: from [85.158.143.35:39638] by server-2.bemta-4.messagelabs.com id 73/50-24322-F5448F05; Thu, 17 Jan 2013 18:35:11 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-7.tower-21.messagelabs.com!1358447703!11905935!1 X-Originating-IP: [94.100.176.174] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26426 invoked from network); 17 Jan 2013 18:35:04 -0000 Received: from smtp21.mail.ru (HELO smtp21.mail.ru) (94.100.176.174) by server-7.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 18:35:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=S5Nb4HhY7kX2EdBev+l2JOYWxI61Flf2C77Fs49UPS0=; b=BHwgNotjHeuRIDJK8GbtHXq9KOpIA7/kQ/WcunXeFmU2xT14u3C0dPWupP7Wjp7W6z6bvjfiYc8QmvqFleeW3c67+Ez/ff/NcIEH7XfqPXXJ1om0eH3+BxVV4YSso60845ZtNUsSruTlbNW8g0bMGTaYg4kJX7BzbzaDiHf/vhw=; Received: from [78.36.51.211] (port=6923 helo=[192.168.1.2]) by smtp21.mail.ru with esmtpa (envelope-from ) id 1TvuIo-00049j-Jo; Thu, 17 Jan 2013 22:35:02 +0400 Message-ID: <50F8444F.8020109@bk.ru> Date: Thu, 17 Jan 2013 22:34:55 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Simon Beaumont References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> X-Spam: Not detected X-Mras: Ok Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VGhhbmsgeW91IGZvciB0aGUgcGF0Y2gsIHdpbGwgdHJ5IHRvIGFwcGx5IGl0LgoKSW4gb3VyIGNv bmZpZ3VyYXRpb24gd2UgZG9uJ3QgbmVlZCBzaGFyZWQgbHZtIFNSIGJlY2F1c2Ugd2UgaGF2ZSBv bmUgCnNlcnZlciB3aXRoIGR1YWwtcGF0aCBkaXJlY3RseSBhdHRhY2hlZCAgUDIwMDAgU0FOLiBJ IGFsc28gaGF2ZSAKY29uZmlndXJlZCBtdWx0aXBhdGggZm9yIHRoZSBMVU5zLiBTbyBtYXkgYmUg d2UgY2FuIGNyZWF0ZSBsb2NhbCBMVk0gU1IgCnRoZW4gZm9yIHRoZSBtdWx0aXBhdGggZGV2aWNl cz8KCjE3LjAxLjIwMTMgMTg6MTksIFNpbW9uIEJlYXVtb250INC/0LjRiNC10YI6Cj4+IC0tLS0t T3JpZ2luYWwgTWVzc2FnZS0tLS0tCj4+IEZyb206IHhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4u b3JnIFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmddIE9uCj4+IEJlaGFsZiBP ZiBBbmRyZXkKPj4gU2VudDogMTcgSmFudWFyeSAyMDEzIDEyOjU2IFBNCj4+IFRvOiB4ZW4tYXBp QGxpc3RzLnhlbi5vcmcKPj4gU3ViamVjdDogW1hlbi1BUEldIHhjcC14YXBpIGRldnNjYW4ucHkg a2VybmVsIHN1cHBvcnQKPj4KPj4gSSBpbnN0YWxsZWQgeGNwLXhhcGkgb24gdGhlIERlYmlhbiBX aGVlenkgYW5kIGNhbid0IGdldCBMVk1vSEJBIHRvIHdvcms6Cj4+Cj4+IHN0ZGVycjogVHJhY2Vi YWNrIChtb3N0IHJlY2VudCBjYWxsIGxhc3QpOgo+PiAgICAgRmlsZSAiL3Vzci9saWIveGNwL3Nt L0xWTW9IQkFTUiIsIGxpbmUgMjIwLCBpbiA8bW9kdWxlPgo+PiAgICAgICBTUkNvbW1hbmQucnVu KExWSERvSEJBU1IsIERSSVZFUl9JTkZPKQo+PiAgICAgRmlsZSAiL3Vzci9saWIveGNwL3NtL1NS Q29tbWFuZC5weSIsIGxpbmUgMjYxLCBpbiBydW4KPj4gICAgICAgc3IgPSBkcml2ZXIoY21kLCBj bWQuc3JfdXVpZCkKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9TUi5weSIsIGxpbmUgMTM2 LCBpbiBfX2luaXRfXwo+PiAgICAgICBzZWxmLmxvYWQoc3JfdXVpZCkKPj4gICAgIEZpbGUgIi91 c3IvbGliL3hjcC9zbS9MVk1vSEJBU1IiLCBsaW5lIDk0LCBpbiBsb2FkCj4+ICAgICAgIHByaW50 ID4+c3lzLnN0ZGVycixzZWxmLmhiYXNyLnByaW50X2RldnMoKQo+PiAgICAgRmlsZSAiL3Vzci9s aWIveGNwL3NtL0hCQVNSLnB5IiwgbGluZSAyMjQsIGluIHByaW50X2RldnMKPj4gICAgICAgc2Vs Zi5faW5pdF9oYmFkaWN0KCkKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9IQkFTUi5weSIs IGxpbmUgNjEsIGluIF9pbml0X2hiYWRpY3QKPj4gICAgICAgZGljdCA9IGRldnNjYW4uYWRhcHRl cnMoZmlsdGVyc3RyPXNlbGYudHlwZSkKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9kZXZz Y2FuLnB5IiwgbGluZSAxNjgsIGluIGFkYXB0ZXJzCj4+ICAgICAgIGdsb2IuZ2xvYihvcy5wYXRo LmpvaW4ocGF0aCwiZGV2aWNlIiwiYmxvY2s6KiIpKVswXSkuc3BsaXQoJzonKVsxXQo+PiBJbmRl eEVycm9yOiBsaXN0IGluZGV4IG91dCBvZiByYW5nZQo+Pgo+Pgo+PiBDYW4geW91IHBsZWFzZSBz ZW5kIGRldnNjYW4ucHkgcGF0Y2ggdG8gc3VwcG9ydCBsdm1vaGJhIGluIGtlcm5lbCAzLlguCj4K PiBJIGhhdmUgYXR0YWNoZWQgdGhlIHBhdGNoIGluIHF1ZXN0aW9uLiBJdCB1c2VzIHRoZSByaWdo dCBzeXNmcyBwYXRocyBhZnRlciBkZXRlY3RpbmcgdGhlIGtlcm5lbCB2ZXJzaW9uLiBJdCBtaWdo dCBub3QgYXBwbHkgdG8geW91ciB2ZXJzaW9uIGJ1dCBpdCBtYXkgaGVscCB5b3UgbWFrZSB0aGUg Y2hhbmdlIHlvdSByZXF1aXJlLgo+Cj4+IEFsc28gd2lsbCBpbiB0aGlzIGNhc2Ugb3RoZXIgbHZt b2hiYSBmZWF0dXJlcyB3aWxsIHdvcmsgc21vb3RobHkgaW4gdGhhdCBjYXNlCj4+IG9uIERlYmlh biwgZXNwZWNpYWxseSBtdWx0aXBhdGg/Cj4KPiBJdCdzIHVubGlrZWx5IHlvdSdsbCBnZXQgTFZN IHRvIHdvcmsgd2l0aCB5b3VyIHNldHVwIHNpbmNlIHdlIHVzZSBhIHBhdGNoZWQgdmVyc2lvbiB0 aGF0IGFjY2VwdHMgYW5vdGhlciBvcHRpb24gKC0tbWFzdGVyKSB3aGljaCBhZmZvcmRzIHVzIGEg ZGlmZmVyZW50IGxvY2tpbmcgbWVjaGFuaXNtIHRvIGFsbG93IHNoYXJlZCBTUnMuIFRoaXMgb3B0 aW9uIGRvZXNuJ3QgZXhpc3QgaW4gdGhlIHVwc3RyZWFtIERlYmlhbiBMVk0uCj4KPiBJdCBtYXko ISkgYmUgcG9zc2libGUgdG8gZ2V0IGl0IHRvIHdvcmsgaWYgeW91IHJlbW92ZSB0aGUgLS1tYXN0 ZXIgb3B0aW9uIGZyb20gdGhlIGNhbGxzIHRvIGx2bSBpbiB0aGUgc291cmNlIGFuZCBlbnN1cmUg dGhhdCB5b3UgYXJlIG9ubHkgdXNpbmcgdGhlc2UgU1JzIGluIHNpbmdsZS1ob3N0IHBvb2xzLiBB Z2FpbiwgeW91ciBtaWxlYWdlIG1heSB2YXJ5Lgo+Cj4gSG9wZSB0aGlzIGhlbHBzLAo+Cj4gLVNp Cj4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1h cGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Thu Jan 17 18:35:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 17 Jan 2013 18:35:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvuIz-0003VV-WD; Thu, 17 Jan 2013 18:35:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvuIx-0003VQ-Q3 for xen-api@lists.xen.org; Thu, 17 Jan 2013 18:35:12 +0000 Received: from [85.158.143.35:39638] by server-2.bemta-4.messagelabs.com id 73/50-24322-F5448F05; Thu, 17 Jan 2013 18:35:11 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-7.tower-21.messagelabs.com!1358447703!11905935!1 X-Originating-IP: [94.100.176.174] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26426 invoked from network); 17 Jan 2013 18:35:04 -0000 Received: from smtp21.mail.ru (HELO smtp21.mail.ru) (94.100.176.174) by server-7.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2013 18:35:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=S5Nb4HhY7kX2EdBev+l2JOYWxI61Flf2C77Fs49UPS0=; b=BHwgNotjHeuRIDJK8GbtHXq9KOpIA7/kQ/WcunXeFmU2xT14u3C0dPWupP7Wjp7W6z6bvjfiYc8QmvqFleeW3c67+Ez/ff/NcIEH7XfqPXXJ1om0eH3+BxVV4YSso60845ZtNUsSruTlbNW8g0bMGTaYg4kJX7BzbzaDiHf/vhw=; Received: from [78.36.51.211] (port=6923 helo=[192.168.1.2]) by smtp21.mail.ru with esmtpa (envelope-from ) id 1TvuIo-00049j-Jo; Thu, 17 Jan 2013 22:35:02 +0400 Message-ID: <50F8444F.8020109@bk.ru> Date: Thu, 17 Jan 2013 22:34:55 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Simon Beaumont References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> X-Spam: Not detected X-Mras: Ok Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VGhhbmsgeW91IGZvciB0aGUgcGF0Y2gsIHdpbGwgdHJ5IHRvIGFwcGx5IGl0LgoKSW4gb3VyIGNv bmZpZ3VyYXRpb24gd2UgZG9uJ3QgbmVlZCBzaGFyZWQgbHZtIFNSIGJlY2F1c2Ugd2UgaGF2ZSBv bmUgCnNlcnZlciB3aXRoIGR1YWwtcGF0aCBkaXJlY3RseSBhdHRhY2hlZCAgUDIwMDAgU0FOLiBJ IGFsc28gaGF2ZSAKY29uZmlndXJlZCBtdWx0aXBhdGggZm9yIHRoZSBMVU5zLiBTbyBtYXkgYmUg d2UgY2FuIGNyZWF0ZSBsb2NhbCBMVk0gU1IgCnRoZW4gZm9yIHRoZSBtdWx0aXBhdGggZGV2aWNl cz8KCjE3LjAxLjIwMTMgMTg6MTksIFNpbW9uIEJlYXVtb250INC/0LjRiNC10YI6Cj4+IC0tLS0t T3JpZ2luYWwgTWVzc2FnZS0tLS0tCj4+IEZyb206IHhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4u b3JnIFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmddIE9uCj4+IEJlaGFsZiBP ZiBBbmRyZXkKPj4gU2VudDogMTcgSmFudWFyeSAyMDEzIDEyOjU2IFBNCj4+IFRvOiB4ZW4tYXBp QGxpc3RzLnhlbi5vcmcKPj4gU3ViamVjdDogW1hlbi1BUEldIHhjcC14YXBpIGRldnNjYW4ucHkg a2VybmVsIHN1cHBvcnQKPj4KPj4gSSBpbnN0YWxsZWQgeGNwLXhhcGkgb24gdGhlIERlYmlhbiBX aGVlenkgYW5kIGNhbid0IGdldCBMVk1vSEJBIHRvIHdvcms6Cj4+Cj4+IHN0ZGVycjogVHJhY2Vi YWNrIChtb3N0IHJlY2VudCBjYWxsIGxhc3QpOgo+PiAgICAgRmlsZSAiL3Vzci9saWIveGNwL3Nt L0xWTW9IQkFTUiIsIGxpbmUgMjIwLCBpbiA8bW9kdWxlPgo+PiAgICAgICBTUkNvbW1hbmQucnVu KExWSERvSEJBU1IsIERSSVZFUl9JTkZPKQo+PiAgICAgRmlsZSAiL3Vzci9saWIveGNwL3NtL1NS Q29tbWFuZC5weSIsIGxpbmUgMjYxLCBpbiBydW4KPj4gICAgICAgc3IgPSBkcml2ZXIoY21kLCBj bWQuc3JfdXVpZCkKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9TUi5weSIsIGxpbmUgMTM2 LCBpbiBfX2luaXRfXwo+PiAgICAgICBzZWxmLmxvYWQoc3JfdXVpZCkKPj4gICAgIEZpbGUgIi91 c3IvbGliL3hjcC9zbS9MVk1vSEJBU1IiLCBsaW5lIDk0LCBpbiBsb2FkCj4+ICAgICAgIHByaW50 ID4+c3lzLnN0ZGVycixzZWxmLmhiYXNyLnByaW50X2RldnMoKQo+PiAgICAgRmlsZSAiL3Vzci9s aWIveGNwL3NtL0hCQVNSLnB5IiwgbGluZSAyMjQsIGluIHByaW50X2RldnMKPj4gICAgICAgc2Vs Zi5faW5pdF9oYmFkaWN0KCkKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9IQkFTUi5weSIs IGxpbmUgNjEsIGluIF9pbml0X2hiYWRpY3QKPj4gICAgICAgZGljdCA9IGRldnNjYW4uYWRhcHRl cnMoZmlsdGVyc3RyPXNlbGYudHlwZSkKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9kZXZz Y2FuLnB5IiwgbGluZSAxNjgsIGluIGFkYXB0ZXJzCj4+ICAgICAgIGdsb2IuZ2xvYihvcy5wYXRo LmpvaW4ocGF0aCwiZGV2aWNlIiwiYmxvY2s6KiIpKVswXSkuc3BsaXQoJzonKVsxXQo+PiBJbmRl eEVycm9yOiBsaXN0IGluZGV4IG91dCBvZiByYW5nZQo+Pgo+Pgo+PiBDYW4geW91IHBsZWFzZSBz ZW5kIGRldnNjYW4ucHkgcGF0Y2ggdG8gc3VwcG9ydCBsdm1vaGJhIGluIGtlcm5lbCAzLlguCj4K PiBJIGhhdmUgYXR0YWNoZWQgdGhlIHBhdGNoIGluIHF1ZXN0aW9uLiBJdCB1c2VzIHRoZSByaWdo dCBzeXNmcyBwYXRocyBhZnRlciBkZXRlY3RpbmcgdGhlIGtlcm5lbCB2ZXJzaW9uLiBJdCBtaWdo dCBub3QgYXBwbHkgdG8geW91ciB2ZXJzaW9uIGJ1dCBpdCBtYXkgaGVscCB5b3UgbWFrZSB0aGUg Y2hhbmdlIHlvdSByZXF1aXJlLgo+Cj4+IEFsc28gd2lsbCBpbiB0aGlzIGNhc2Ugb3RoZXIgbHZt b2hiYSBmZWF0dXJlcyB3aWxsIHdvcmsgc21vb3RobHkgaW4gdGhhdCBjYXNlCj4+IG9uIERlYmlh biwgZXNwZWNpYWxseSBtdWx0aXBhdGg/Cj4KPiBJdCdzIHVubGlrZWx5IHlvdSdsbCBnZXQgTFZN IHRvIHdvcmsgd2l0aCB5b3VyIHNldHVwIHNpbmNlIHdlIHVzZSBhIHBhdGNoZWQgdmVyc2lvbiB0 aGF0IGFjY2VwdHMgYW5vdGhlciBvcHRpb24gKC0tbWFzdGVyKSB3aGljaCBhZmZvcmRzIHVzIGEg ZGlmZmVyZW50IGxvY2tpbmcgbWVjaGFuaXNtIHRvIGFsbG93IHNoYXJlZCBTUnMuIFRoaXMgb3B0 aW9uIGRvZXNuJ3QgZXhpc3QgaW4gdGhlIHVwc3RyZWFtIERlYmlhbiBMVk0uCj4KPiBJdCBtYXko ISkgYmUgcG9zc2libGUgdG8gZ2V0IGl0IHRvIHdvcmsgaWYgeW91IHJlbW92ZSB0aGUgLS1tYXN0 ZXIgb3B0aW9uIGZyb20gdGhlIGNhbGxzIHRvIGx2bSBpbiB0aGUgc291cmNlIGFuZCBlbnN1cmUg dGhhdCB5b3UgYXJlIG9ubHkgdXNpbmcgdGhlc2UgU1JzIGluIHNpbmdsZS1ob3N0IHBvb2xzLiBB Z2FpbiwgeW91ciBtaWxlYWdlIG1heSB2YXJ5Lgo+Cj4gSG9wZSB0aGlzIGhlbHBzLAo+Cj4gLVNp Cj4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1h cGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Fri Jan 18 07:03:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 07:03:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw5yX-00079D-A3; Fri, 18 Jan 2013 07:02:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw5yU-000798-Tx for xen-api@lists.xen.org; Fri, 18 Jan 2013 07:02:51 +0000 Received: from [85.158.137.99:57039] by server-16.bemta-3.messagelabs.com id BA/4D-31306-A93F8F05; Fri, 18 Jan 2013 07:02:50 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-4.tower-217.messagelabs.com!1358492568!17460294!1 X-Originating-IP: [94.100.176.152] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16491 invoked from network); 18 Jan 2013 07:02:48 -0000 Received: from smtp10.mail.ru (HELO smtp10.mail.ru) (94.100.176.152) by server-4.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jan 2013 07:02:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=J9BoKjRARWK4Fop0RU4BrCZNGV4/THlPDflhWKDbf3o=; b=kjSZpzwq04z3Srx5ug5dGDQCyjEs43B2pSq+Oeuwda0+aukKwDYPKnqTgptqZ6n4+qgOG8qlyHsPzPRK7XYDKTczmx/LlAwy1VsMKtoYDdOH5x7PrjqHw922jHXpuf0+1VMXsJqcdaz3AWRSp7pQx3lLiF++DoEPQM6Bc/Ufdf8=; Received: from [78.36.60.25] (port=16844 helo=[10.168.2.113]) by smtp10.mail.ru with esmtpa (envelope-from ) id 1Tw5yR-0005UW-Gt; Fri, 18 Jan 2013 11:02:47 +0400 Message-ID: <50F8F396.4060101@bk.ru> Date: Fri, 18 Jan 2013 11:02:46 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Simon Beaumont References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> X-Spam: Not detected X-Mras: Ok Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org QWxzbyBub3RpY2VkIHRoYXQgL2Rldi9kaXNrL2J5LXNjc2lidXMvKiBwYXRoIGRvZXMgbm90IGV4 aXN0IGFzIHN1cHBvc2VkIAppbiBjYWNoZVNDU0lpZGVudGlmaWVycygpIGluIHRoZSBzY3NpdXRp bC5weSBzbyBkZXZzIHByb3BlcnR5IGlzIGVtcHR5IAp3aGlsZSBzci1wcm9iZSBhbmQgb25seSBn ZW5lcmFsIGluZm9ybWF0aW9uIHJldHVybnMuIERvZXMgYW55IHBhdGNoIApleGlzdCB0b28/Cgox Ny4wMS4yMDEzIDE4OjE5LCBTaW1vbiBCZWF1bW9udCDQv9C40YjQtdGCOgo+PiAtLS0tLU9yaWdp bmFsIE1lc3NhZ2UtLS0tLQo+PiBGcm9tOiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyBb bWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbgo+PiBCZWhhbGYgT2YgQW5k cmV5Cj4+IFNlbnQ6IDE3IEphbnVhcnkgMjAxMyAxMjo1NiBQTQo+PiBUbzogeGVuLWFwaUBsaXN0 cy54ZW4ub3JnCj4+IFN1YmplY3Q6IFtYZW4tQVBJXSB4Y3AteGFwaSBkZXZzY2FuLnB5IGtlcm5l bCBzdXBwb3J0Cj4+Cj4+IEkgaW5zdGFsbGVkIHhjcC14YXBpIG9uIHRoZSBEZWJpYW4gV2hlZXp5 IGFuZCBjYW4ndCBnZXQgTFZNb0hCQSB0byB3b3JrOgo+Pgo+PiBzdGRlcnI6IFRyYWNlYmFjayAo bW9zdCByZWNlbnQgY2FsbCBsYXN0KToKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9MVk1v SEJBU1IiLCBsaW5lIDIyMCwgaW4gPG1vZHVsZT4KPj4gICAgICAgU1JDb21tYW5kLnJ1bihMVkhE b0hCQVNSLCBEUklWRVJfSU5GTykKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9TUkNvbW1h bmQucHkiLCBsaW5lIDI2MSwgaW4gcnVuCj4+ICAgICAgIHNyID0gZHJpdmVyKGNtZCwgY21kLnNy X3V1aWQpCj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vU1IucHkiLCBsaW5lIDEzNiwgaW4g X19pbml0X18KPj4gICAgICAgc2VsZi5sb2FkKHNyX3V1aWQpCj4+ICAgICBGaWxlICIvdXNyL2xp Yi94Y3Avc20vTFZNb0hCQVNSIiwgbGluZSA5NCwgaW4gbG9hZAo+PiAgICAgICBwcmludCA+PnN5 cy5zdGRlcnIsc2VsZi5oYmFzci5wcmludF9kZXZzKCkKPj4gICAgIEZpbGUgIi91c3IvbGliL3hj cC9zbS9IQkFTUi5weSIsIGxpbmUgMjI0LCBpbiBwcmludF9kZXZzCj4+ICAgICAgIHNlbGYuX2lu aXRfaGJhZGljdCgpCj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vSEJBU1IucHkiLCBsaW5l IDYxLCBpbiBfaW5pdF9oYmFkaWN0Cj4+ICAgICAgIGRpY3QgPSBkZXZzY2FuLmFkYXB0ZXJzKGZp bHRlcnN0cj1zZWxmLnR5cGUpCj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vZGV2c2Nhbi5w eSIsIGxpbmUgMTY4LCBpbiBhZGFwdGVycwo+PiAgICAgICBnbG9iLmdsb2Iob3MucGF0aC5qb2lu KHBhdGgsImRldmljZSIsImJsb2NrOioiKSlbMF0pLnNwbGl0KCc6JylbMV0KPj4gSW5kZXhFcnJv cjogbGlzdCBpbmRleCBvdXQgb2YgcmFuZ2UKPj4KPj4KPj4gQ2FuIHlvdSBwbGVhc2Ugc2VuZCBk ZXZzY2FuLnB5IHBhdGNoIHRvIHN1cHBvcnQgbHZtb2hiYSBpbiBrZXJuZWwgMy5YLgo+Cj4gSSBo YXZlIGF0dGFjaGVkIHRoZSBwYXRjaCBpbiBxdWVzdGlvbi4gSXQgdXNlcyB0aGUgcmlnaHQgc3lz ZnMgcGF0aHMgYWZ0ZXIgZGV0ZWN0aW5nIHRoZSBrZXJuZWwgdmVyc2lvbi4gSXQgbWlnaHQgbm90 IGFwcGx5IHRvIHlvdXIgdmVyc2lvbiBidXQgaXQgbWF5IGhlbHAgeW91IG1ha2UgdGhlIGNoYW5n ZSB5b3UgcmVxdWlyZS4KPgo+PiBBbHNvIHdpbGwgaW4gdGhpcyBjYXNlIG90aGVyIGx2bW9oYmEg ZmVhdHVyZXMgd2lsbCB3b3JrIHNtb290aGx5IGluIHRoYXQgY2FzZQo+PiBvbiBEZWJpYW4sIGVz cGVjaWFsbHkgbXVsdGlwYXRoPwo+Cj4gSXQncyB1bmxpa2VseSB5b3UnbGwgZ2V0IExWTSB0byB3 b3JrIHdpdGggeW91ciBzZXR1cCBzaW5jZSB3ZSB1c2UgYSBwYXRjaGVkIHZlcnNpb24gdGhhdCBh Y2NlcHRzIGFub3RoZXIgb3B0aW9uICgtLW1hc3Rlcikgd2hpY2ggYWZmb3JkcyB1cyBhIGRpZmZl cmVudCBsb2NraW5nIG1lY2hhbmlzbSB0byBhbGxvdyBzaGFyZWQgU1JzLiBUaGlzIG9wdGlvbiBk b2Vzbid0IGV4aXN0IGluIHRoZSB1cHN0cmVhbSBEZWJpYW4gTFZNLgo+Cj4gSXQgbWF5KCEpIGJl IHBvc3NpYmxlIHRvIGdldCBpdCB0byB3b3JrIGlmIHlvdSByZW1vdmUgdGhlIC0tbWFzdGVyIG9w dGlvbiBmcm9tIHRoZSBjYWxscyB0byBsdm0gaW4gdGhlIHNvdXJjZSBhbmQgZW5zdXJlIHRoYXQg eW91IGFyZSBvbmx5IHVzaW5nIHRoZXNlIFNScyBpbiBzaW5nbGUtaG9zdCBwb29scy4gQWdhaW4s IHlvdXIgbWlsZWFnZSBtYXkgdmFyeS4KPgo+IEhvcGUgdGhpcyBoZWxwcywKPgo+IC1TaQo+Cgpf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1h aWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Fri Jan 18 07:03:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 07:03:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw5yX-00079D-A3; Fri, 18 Jan 2013 07:02:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw5yU-000798-Tx for xen-api@lists.xen.org; Fri, 18 Jan 2013 07:02:51 +0000 Received: from [85.158.137.99:57039] by server-16.bemta-3.messagelabs.com id BA/4D-31306-A93F8F05; Fri, 18 Jan 2013 07:02:50 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-4.tower-217.messagelabs.com!1358492568!17460294!1 X-Originating-IP: [94.100.176.152] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16491 invoked from network); 18 Jan 2013 07:02:48 -0000 Received: from smtp10.mail.ru (HELO smtp10.mail.ru) (94.100.176.152) by server-4.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jan 2013 07:02:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=J9BoKjRARWK4Fop0RU4BrCZNGV4/THlPDflhWKDbf3o=; b=kjSZpzwq04z3Srx5ug5dGDQCyjEs43B2pSq+Oeuwda0+aukKwDYPKnqTgptqZ6n4+qgOG8qlyHsPzPRK7XYDKTczmx/LlAwy1VsMKtoYDdOH5x7PrjqHw922jHXpuf0+1VMXsJqcdaz3AWRSp7pQx3lLiF++DoEPQM6Bc/Ufdf8=; Received: from [78.36.60.25] (port=16844 helo=[10.168.2.113]) by smtp10.mail.ru with esmtpa (envelope-from ) id 1Tw5yR-0005UW-Gt; Fri, 18 Jan 2013 11:02:47 +0400 Message-ID: <50F8F396.4060101@bk.ru> Date: Fri, 18 Jan 2013 11:02:46 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Simon Beaumont References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> X-Spam: Not detected X-Mras: Ok Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org QWxzbyBub3RpY2VkIHRoYXQgL2Rldi9kaXNrL2J5LXNjc2lidXMvKiBwYXRoIGRvZXMgbm90IGV4 aXN0IGFzIHN1cHBvc2VkIAppbiBjYWNoZVNDU0lpZGVudGlmaWVycygpIGluIHRoZSBzY3NpdXRp bC5weSBzbyBkZXZzIHByb3BlcnR5IGlzIGVtcHR5IAp3aGlsZSBzci1wcm9iZSBhbmQgb25seSBn ZW5lcmFsIGluZm9ybWF0aW9uIHJldHVybnMuIERvZXMgYW55IHBhdGNoIApleGlzdCB0b28/Cgox Ny4wMS4yMDEzIDE4OjE5LCBTaW1vbiBCZWF1bW9udCDQv9C40YjQtdGCOgo+PiAtLS0tLU9yaWdp bmFsIE1lc3NhZ2UtLS0tLQo+PiBGcm9tOiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyBb bWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbgo+PiBCZWhhbGYgT2YgQW5k cmV5Cj4+IFNlbnQ6IDE3IEphbnVhcnkgMjAxMyAxMjo1NiBQTQo+PiBUbzogeGVuLWFwaUBsaXN0 cy54ZW4ub3JnCj4+IFN1YmplY3Q6IFtYZW4tQVBJXSB4Y3AteGFwaSBkZXZzY2FuLnB5IGtlcm5l bCBzdXBwb3J0Cj4+Cj4+IEkgaW5zdGFsbGVkIHhjcC14YXBpIG9uIHRoZSBEZWJpYW4gV2hlZXp5 IGFuZCBjYW4ndCBnZXQgTFZNb0hCQSB0byB3b3JrOgo+Pgo+PiBzdGRlcnI6IFRyYWNlYmFjayAo bW9zdCByZWNlbnQgY2FsbCBsYXN0KToKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9MVk1v SEJBU1IiLCBsaW5lIDIyMCwgaW4gPG1vZHVsZT4KPj4gICAgICAgU1JDb21tYW5kLnJ1bihMVkhE b0hCQVNSLCBEUklWRVJfSU5GTykKPj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9TUkNvbW1h bmQucHkiLCBsaW5lIDI2MSwgaW4gcnVuCj4+ICAgICAgIHNyID0gZHJpdmVyKGNtZCwgY21kLnNy X3V1aWQpCj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vU1IucHkiLCBsaW5lIDEzNiwgaW4g X19pbml0X18KPj4gICAgICAgc2VsZi5sb2FkKHNyX3V1aWQpCj4+ICAgICBGaWxlICIvdXNyL2xp Yi94Y3Avc20vTFZNb0hCQVNSIiwgbGluZSA5NCwgaW4gbG9hZAo+PiAgICAgICBwcmludCA+PnN5 cy5zdGRlcnIsc2VsZi5oYmFzci5wcmludF9kZXZzKCkKPj4gICAgIEZpbGUgIi91c3IvbGliL3hj cC9zbS9IQkFTUi5weSIsIGxpbmUgMjI0LCBpbiBwcmludF9kZXZzCj4+ICAgICAgIHNlbGYuX2lu aXRfaGJhZGljdCgpCj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vSEJBU1IucHkiLCBsaW5l IDYxLCBpbiBfaW5pdF9oYmFkaWN0Cj4+ICAgICAgIGRpY3QgPSBkZXZzY2FuLmFkYXB0ZXJzKGZp bHRlcnN0cj1zZWxmLnR5cGUpCj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vZGV2c2Nhbi5w eSIsIGxpbmUgMTY4LCBpbiBhZGFwdGVycwo+PiAgICAgICBnbG9iLmdsb2Iob3MucGF0aC5qb2lu KHBhdGgsImRldmljZSIsImJsb2NrOioiKSlbMF0pLnNwbGl0KCc6JylbMV0KPj4gSW5kZXhFcnJv cjogbGlzdCBpbmRleCBvdXQgb2YgcmFuZ2UKPj4KPj4KPj4gQ2FuIHlvdSBwbGVhc2Ugc2VuZCBk ZXZzY2FuLnB5IHBhdGNoIHRvIHN1cHBvcnQgbHZtb2hiYSBpbiBrZXJuZWwgMy5YLgo+Cj4gSSBo YXZlIGF0dGFjaGVkIHRoZSBwYXRjaCBpbiBxdWVzdGlvbi4gSXQgdXNlcyB0aGUgcmlnaHQgc3lz ZnMgcGF0aHMgYWZ0ZXIgZGV0ZWN0aW5nIHRoZSBrZXJuZWwgdmVyc2lvbi4gSXQgbWlnaHQgbm90 IGFwcGx5IHRvIHlvdXIgdmVyc2lvbiBidXQgaXQgbWF5IGhlbHAgeW91IG1ha2UgdGhlIGNoYW5n ZSB5b3UgcmVxdWlyZS4KPgo+PiBBbHNvIHdpbGwgaW4gdGhpcyBjYXNlIG90aGVyIGx2bW9oYmEg ZmVhdHVyZXMgd2lsbCB3b3JrIHNtb290aGx5IGluIHRoYXQgY2FzZQo+PiBvbiBEZWJpYW4sIGVz cGVjaWFsbHkgbXVsdGlwYXRoPwo+Cj4gSXQncyB1bmxpa2VseSB5b3UnbGwgZ2V0IExWTSB0byB3 b3JrIHdpdGggeW91ciBzZXR1cCBzaW5jZSB3ZSB1c2UgYSBwYXRjaGVkIHZlcnNpb24gdGhhdCBh Y2NlcHRzIGFub3RoZXIgb3B0aW9uICgtLW1hc3Rlcikgd2hpY2ggYWZmb3JkcyB1cyBhIGRpZmZl cmVudCBsb2NraW5nIG1lY2hhbmlzbSB0byBhbGxvdyBzaGFyZWQgU1JzLiBUaGlzIG9wdGlvbiBk b2Vzbid0IGV4aXN0IGluIHRoZSB1cHN0cmVhbSBEZWJpYW4gTFZNLgo+Cj4gSXQgbWF5KCEpIGJl IHBvc3NpYmxlIHRvIGdldCBpdCB0byB3b3JrIGlmIHlvdSByZW1vdmUgdGhlIC0tbWFzdGVyIG9w dGlvbiBmcm9tIHRoZSBjYWxscyB0byBsdm0gaW4gdGhlIHNvdXJjZSBhbmQgZW5zdXJlIHRoYXQg eW91IGFyZSBvbmx5IHVzaW5nIHRoZXNlIFNScyBpbiBzaW5nbGUtaG9zdCBwb29scy4gQWdhaW4s IHlvdXIgbWlsZWFnZSBtYXkgdmFyeS4KPgo+IEhvcGUgdGhpcyBoZWxwcywKPgo+IC1TaQo+Cgpf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1h aWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Fri Jan 18 08:23:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 08:23:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7EJ-0001Mx-Vg; Fri, 18 Jan 2013 08:23:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7EI-0001Ms-An for xen-api@lists.xen.org; Fri, 18 Jan 2013 08:23:14 +0000 Received: from [85.158.139.83:57860] by server-5.bemta-5.messagelabs.com id 45/C5-31624-17609F05; Fri, 18 Jan 2013 08:23:13 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1358497391!21054505!1 X-Originating-IP: [209.85.217.177] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20917 invoked from network); 18 Jan 2013 08:23:12 -0000 Received: from mail-lb0-f177.google.com (HELO mail-lb0-f177.google.com) (209.85.217.177) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2013 08:23:12 -0000 Received: by mail-lb0-f177.google.com with SMTP id gm6so366651lbb.22 for ; Fri, 18 Jan 2013 00:23:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=SwCXspxf2ufugCURkcU4f9K2itDxzB1GhS8pgK/Mdcg=; b=KHBiMJbsxdb7qw+vG1hMdmc51fankAQeR10jWBv9qDDmXevKDXC1nDyJ0AUrkz6taZ 8T/iaTPRyEMpPCb9DlDRfJWGZahTvIFvowvlXX0LYQeouB98hoEOBrJsPbVio1CLc1cN fibPnk/GqTwPUqRfnL8lpjbatpJQCnBVHzDrfw9OL6EVMsnoOaTpOJuYTybe3omB86qA z54Agq29cYS0nABBLTuFpwIp/tXvetx2klchPF6HtvaD+75TFqBLx2/5kkBpp+RUSmgl 4VMSEb0aFdPAy5chhLGPuy3rOAS0qis0y11hs1/ronsJL84r3Dm/8cuSbKwS5HoSF1cI CSxw== X-Received: by 10.152.121.212 with SMTP id lm20mr7517766lab.42.1358497391553; Fri, 18 Jan 2013 00:23:11 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03? ([2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03]) by mx.google.com with ESMTPS id n2sm1730808lbc.5.2013.01.18.00.23.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Jan 2013 00:23:10 -0800 (PST) Message-ID: <50F9066D.6020005@gmail.com> Date: Fri, 18 Jan 2013 12:23:09 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> <50F8444F.8020109@bk.ru> In-Reply-To: <50F8444F.8020109@bk.ru> Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WW91IHNob3VsZCBiZSAxNDYlIHN1cmUgbm8gb3RoZXIgaG9zdHMgd2lsbCBhY2Nlc3Mgc3RvcmFn ZSBpbiB0aGF0IGNhc2UuIApJZiBzb21lIGJhY2tncm91bmQgcHJvY2VzcyAoZi5lLiBWSEQgY29h bGVzaW5nKSB3aWxsIGNvbGxpZGUgd2l0aCBvdGhlcnMgCmhvc3RzIGFjdGl2aXR5IG9uIFNSLCB5 b3Ugd2lsbCB0cmFzaCBzb21lIHJhbmRvbSBwZWljZSBvZiBkYXRhIChtYXkgYmUgCmluY2x1ZGlu ZyBMVk0gbWV0YWRhdGEpLgoKMTcuMDEuMjAxMyAyMjozNCwgQW5kcmV5INC/0LjRiNC10YI6Cj4g VGhhbmsgeW91IGZvciB0aGUgcGF0Y2gsIHdpbGwgdHJ5IHRvIGFwcGx5IGl0Lgo+Cj4gSW4gb3Vy IGNvbmZpZ3VyYXRpb24gd2UgZG9uJ3QgbmVlZCBzaGFyZWQgbHZtIFNSIGJlY2F1c2Ugd2UgaGF2 ZSBvbmUgCj4gc2VydmVyIHdpdGggZHVhbC1wYXRoIGRpcmVjdGx5IGF0dGFjaGVkICBQMjAwMCBT QU4uIEkgYWxzbyBoYXZlIAo+IGNvbmZpZ3VyZWQgbXVsdGlwYXRoIGZvciB0aGUgTFVOcy4gU28g bWF5IGJlIHdlIGNhbiBjcmVhdGUgbG9jYWwgTFZNIAo+IFNSIHRoZW4gZm9yIHRoZSBtdWx0aXBh dGggZGV2aWNlcz8KPgo+IDE3LjAxLjIwMTMgMTg6MTksIFNpbW9uIEJlYXVtb250INC/0LjRiNC1 0YI6Cj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQo+Pj4gRnJvbTogeGVuLWFwaS1ib3Vu Y2VzQGxpc3RzLnhlbi5vcmcgCj4+PiBbbWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4u b3JnXSBPbgo+Pj4gQmVoYWxmIE9mIEFuZHJleQo+Pj4gU2VudDogMTcgSmFudWFyeSAyMDEzIDEy OjU2IFBNCj4+PiBUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4+PiBTdWJqZWN0OiBbWGVuLUFQ SV0geGNwLXhhcGkgZGV2c2Nhbi5weSBrZXJuZWwgc3VwcG9ydAo+Pj4KPj4+IEkgaW5zdGFsbGVk IHhjcC14YXBpIG9uIHRoZSBEZWJpYW4gV2hlZXp5IGFuZCBjYW4ndCBnZXQgTFZNb0hCQSB0byAK Pj4+IHdvcms6Cj4+Pgo+Pj4gc3RkZXJyOiBUcmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwgbGFz dCk6Cj4+PiAgICAgRmlsZSAiL3Vzci9saWIveGNwL3NtL0xWTW9IQkFTUiIsIGxpbmUgMjIwLCBp biA8bW9kdWxlPgo+Pj4gICAgICAgU1JDb21tYW5kLnJ1bihMVkhEb0hCQVNSLCBEUklWRVJfSU5G TykKPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vU1JDb21tYW5kLnB5IiwgbGluZSAyNjEs IGluIHJ1bgo+Pj4gICAgICAgc3IgPSBkcml2ZXIoY21kLCBjbWQuc3JfdXVpZCkKPj4+ICAgICBG aWxlICIvdXNyL2xpYi94Y3Avc20vU1IucHkiLCBsaW5lIDEzNiwgaW4gX19pbml0X18KPj4+ICAg ICAgIHNlbGYubG9hZChzcl91dWlkKQo+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9MVk1v SEJBU1IiLCBsaW5lIDk0LCBpbiBsb2FkCj4+PiAgICAgICBwcmludCA+PnN5cy5zdGRlcnIsc2Vs Zi5oYmFzci5wcmludF9kZXZzKCkKPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vSEJBU1Iu cHkiLCBsaW5lIDIyNCwgaW4gcHJpbnRfZGV2cwo+Pj4gICAgICAgc2VsZi5faW5pdF9oYmFkaWN0 KCkKPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vSEJBU1IucHkiLCBsaW5lIDYxLCBpbiBf aW5pdF9oYmFkaWN0Cj4+PiAgICAgICBkaWN0ID0gZGV2c2Nhbi5hZGFwdGVycyhmaWx0ZXJzdHI9 c2VsZi50eXBlKQo+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9kZXZzY2FuLnB5IiwgbGlu ZSAxNjgsIGluIGFkYXB0ZXJzCj4+PiBnbG9iLmdsb2Iob3MucGF0aC5qb2luKHBhdGgsImRldmlj ZSIsImJsb2NrOioiKSlbMF0pLnNwbGl0KCc6JylbMV0KPj4+IEluZGV4RXJyb3I6IGxpc3QgaW5k ZXggb3V0IG9mIHJhbmdlCj4+Pgo+Pj4KPj4+IENhbiB5b3UgcGxlYXNlIHNlbmQgZGV2c2Nhbi5w eSBwYXRjaCB0byBzdXBwb3J0IGx2bW9oYmEgaW4ga2VybmVsIDMuWC4KPj4KPj4gSSBoYXZlIGF0 dGFjaGVkIHRoZSBwYXRjaCBpbiBxdWVzdGlvbi4gSXQgdXNlcyB0aGUgcmlnaHQgc3lzZnMgcGF0 aHMgCj4+IGFmdGVyIGRldGVjdGluZyB0aGUga2VybmVsIHZlcnNpb24uIEl0IG1pZ2h0IG5vdCBh cHBseSB0byB5b3VyIAo+PiB2ZXJzaW9uIGJ1dCBpdCBtYXkgaGVscCB5b3UgbWFrZSB0aGUgY2hh bmdlIHlvdSByZXF1aXJlLgo+Pgo+Pj4gQWxzbyB3aWxsIGluIHRoaXMgY2FzZSBvdGhlciBsdm1v aGJhIGZlYXR1cmVzIHdpbGwgd29yayBzbW9vdGhseSBpbiAKPj4+IHRoYXQgY2FzZQo+Pj4gb24g RGViaWFuLCBlc3BlY2lhbGx5IG11bHRpcGF0aD8KPj4KPj4gSXQncyB1bmxpa2VseSB5b3UnbGwg Z2V0IExWTSB0byB3b3JrIHdpdGggeW91ciBzZXR1cCBzaW5jZSB3ZSB1c2UgYSAKPj4gcGF0Y2hl ZCB2ZXJzaW9uIHRoYXQgYWNjZXB0cyBhbm90aGVyIG9wdGlvbiAoLS1tYXN0ZXIpIHdoaWNoIGFm Zm9yZHMgCj4+IHVzIGEgZGlmZmVyZW50IGxvY2tpbmcgbWVjaGFuaXNtIHRvIGFsbG93IHNoYXJl ZCBTUnMuIFRoaXMgb3B0aW9uIAo+PiBkb2Vzbid0IGV4aXN0IGluIHRoZSB1cHN0cmVhbSBEZWJp YW4gTFZNLgo+Pgo+PiBJdCBtYXkoISkgYmUgcG9zc2libGUgdG8gZ2V0IGl0IHRvIHdvcmsgaWYg eW91IHJlbW92ZSB0aGUgLS1tYXN0ZXIgCj4+IG9wdGlvbiBmcm9tIHRoZSBjYWxscyB0byBsdm0g aW4gdGhlIHNvdXJjZSBhbmQgZW5zdXJlIHRoYXQgeW91IGFyZSAKPj4gb25seSB1c2luZyB0aGVz ZSBTUnMgaW4gc2luZ2xlLWhvc3QgcG9vbHMuIEFnYWluLCB5b3VyIG1pbGVhZ2UgbWF5IHZhcnku Cj4+Cj4+IEhvcGUgdGhpcyBoZWxwcywKPj4KPj4gLVNpCj4+Cj4KPiBfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1hcGkgbWFpbGluZyBsaXN0Cj4g WGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWls bWFuL2xpc3RpbmZvL3hlbi1hcGkKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcK aHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Fri Jan 18 08:23:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 08:23:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7EJ-0001Mx-Vg; Fri, 18 Jan 2013 08:23:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7EI-0001Ms-An for xen-api@lists.xen.org; Fri, 18 Jan 2013 08:23:14 +0000 Received: from [85.158.139.83:57860] by server-5.bemta-5.messagelabs.com id 45/C5-31624-17609F05; Fri, 18 Jan 2013 08:23:13 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1358497391!21054505!1 X-Originating-IP: [209.85.217.177] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20917 invoked from network); 18 Jan 2013 08:23:12 -0000 Received: from mail-lb0-f177.google.com (HELO mail-lb0-f177.google.com) (209.85.217.177) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2013 08:23:12 -0000 Received: by mail-lb0-f177.google.com with SMTP id gm6so366651lbb.22 for ; Fri, 18 Jan 2013 00:23:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=SwCXspxf2ufugCURkcU4f9K2itDxzB1GhS8pgK/Mdcg=; b=KHBiMJbsxdb7qw+vG1hMdmc51fankAQeR10jWBv9qDDmXevKDXC1nDyJ0AUrkz6taZ 8T/iaTPRyEMpPCb9DlDRfJWGZahTvIFvowvlXX0LYQeouB98hoEOBrJsPbVio1CLc1cN fibPnk/GqTwPUqRfnL8lpjbatpJQCnBVHzDrfw9OL6EVMsnoOaTpOJuYTybe3omB86qA z54Agq29cYS0nABBLTuFpwIp/tXvetx2klchPF6HtvaD+75TFqBLx2/5kkBpp+RUSmgl 4VMSEb0aFdPAy5chhLGPuy3rOAS0qis0y11hs1/ronsJL84r3Dm/8cuSbKwS5HoSF1cI CSxw== X-Received: by 10.152.121.212 with SMTP id lm20mr7517766lab.42.1358497391553; Fri, 18 Jan 2013 00:23:11 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03? ([2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03]) by mx.google.com with ESMTPS id n2sm1730808lbc.5.2013.01.18.00.23.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Jan 2013 00:23:10 -0800 (PST) Message-ID: <50F9066D.6020005@gmail.com> Date: Fri, 18 Jan 2013 12:23:09 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> <50F8444F.8020109@bk.ru> In-Reply-To: <50F8444F.8020109@bk.ru> Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WW91IHNob3VsZCBiZSAxNDYlIHN1cmUgbm8gb3RoZXIgaG9zdHMgd2lsbCBhY2Nlc3Mgc3RvcmFn ZSBpbiB0aGF0IGNhc2UuIApJZiBzb21lIGJhY2tncm91bmQgcHJvY2VzcyAoZi5lLiBWSEQgY29h bGVzaW5nKSB3aWxsIGNvbGxpZGUgd2l0aCBvdGhlcnMgCmhvc3RzIGFjdGl2aXR5IG9uIFNSLCB5 b3Ugd2lsbCB0cmFzaCBzb21lIHJhbmRvbSBwZWljZSBvZiBkYXRhIChtYXkgYmUgCmluY2x1ZGlu ZyBMVk0gbWV0YWRhdGEpLgoKMTcuMDEuMjAxMyAyMjozNCwgQW5kcmV5INC/0LjRiNC10YI6Cj4g VGhhbmsgeW91IGZvciB0aGUgcGF0Y2gsIHdpbGwgdHJ5IHRvIGFwcGx5IGl0Lgo+Cj4gSW4gb3Vy IGNvbmZpZ3VyYXRpb24gd2UgZG9uJ3QgbmVlZCBzaGFyZWQgbHZtIFNSIGJlY2F1c2Ugd2UgaGF2 ZSBvbmUgCj4gc2VydmVyIHdpdGggZHVhbC1wYXRoIGRpcmVjdGx5IGF0dGFjaGVkICBQMjAwMCBT QU4uIEkgYWxzbyBoYXZlIAo+IGNvbmZpZ3VyZWQgbXVsdGlwYXRoIGZvciB0aGUgTFVOcy4gU28g bWF5IGJlIHdlIGNhbiBjcmVhdGUgbG9jYWwgTFZNIAo+IFNSIHRoZW4gZm9yIHRoZSBtdWx0aXBh dGggZGV2aWNlcz8KPgo+IDE3LjAxLjIwMTMgMTg6MTksIFNpbW9uIEJlYXVtb250INC/0LjRiNC1 0YI6Cj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQo+Pj4gRnJvbTogeGVuLWFwaS1ib3Vu Y2VzQGxpc3RzLnhlbi5vcmcgCj4+PiBbbWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4u b3JnXSBPbgo+Pj4gQmVoYWxmIE9mIEFuZHJleQo+Pj4gU2VudDogMTcgSmFudWFyeSAyMDEzIDEy OjU2IFBNCj4+PiBUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4+PiBTdWJqZWN0OiBbWGVuLUFQ SV0geGNwLXhhcGkgZGV2c2Nhbi5weSBrZXJuZWwgc3VwcG9ydAo+Pj4KPj4+IEkgaW5zdGFsbGVk IHhjcC14YXBpIG9uIHRoZSBEZWJpYW4gV2hlZXp5IGFuZCBjYW4ndCBnZXQgTFZNb0hCQSB0byAK Pj4+IHdvcms6Cj4+Pgo+Pj4gc3RkZXJyOiBUcmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwgbGFz dCk6Cj4+PiAgICAgRmlsZSAiL3Vzci9saWIveGNwL3NtL0xWTW9IQkFTUiIsIGxpbmUgMjIwLCBp biA8bW9kdWxlPgo+Pj4gICAgICAgU1JDb21tYW5kLnJ1bihMVkhEb0hCQVNSLCBEUklWRVJfSU5G TykKPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vU1JDb21tYW5kLnB5IiwgbGluZSAyNjEs IGluIHJ1bgo+Pj4gICAgICAgc3IgPSBkcml2ZXIoY21kLCBjbWQuc3JfdXVpZCkKPj4+ICAgICBG aWxlICIvdXNyL2xpYi94Y3Avc20vU1IucHkiLCBsaW5lIDEzNiwgaW4gX19pbml0X18KPj4+ICAg ICAgIHNlbGYubG9hZChzcl91dWlkKQo+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9MVk1v SEJBU1IiLCBsaW5lIDk0LCBpbiBsb2FkCj4+PiAgICAgICBwcmludCA+PnN5cy5zdGRlcnIsc2Vs Zi5oYmFzci5wcmludF9kZXZzKCkKPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vSEJBU1Iu cHkiLCBsaW5lIDIyNCwgaW4gcHJpbnRfZGV2cwo+Pj4gICAgICAgc2VsZi5faW5pdF9oYmFkaWN0 KCkKPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vSEJBU1IucHkiLCBsaW5lIDYxLCBpbiBf aW5pdF9oYmFkaWN0Cj4+PiAgICAgICBkaWN0ID0gZGV2c2Nhbi5hZGFwdGVycyhmaWx0ZXJzdHI9 c2VsZi50eXBlKQo+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9kZXZzY2FuLnB5IiwgbGlu ZSAxNjgsIGluIGFkYXB0ZXJzCj4+PiBnbG9iLmdsb2Iob3MucGF0aC5qb2luKHBhdGgsImRldmlj ZSIsImJsb2NrOioiKSlbMF0pLnNwbGl0KCc6JylbMV0KPj4+IEluZGV4RXJyb3I6IGxpc3QgaW5k ZXggb3V0IG9mIHJhbmdlCj4+Pgo+Pj4KPj4+IENhbiB5b3UgcGxlYXNlIHNlbmQgZGV2c2Nhbi5w eSBwYXRjaCB0byBzdXBwb3J0IGx2bW9oYmEgaW4ga2VybmVsIDMuWC4KPj4KPj4gSSBoYXZlIGF0 dGFjaGVkIHRoZSBwYXRjaCBpbiBxdWVzdGlvbi4gSXQgdXNlcyB0aGUgcmlnaHQgc3lzZnMgcGF0 aHMgCj4+IGFmdGVyIGRldGVjdGluZyB0aGUga2VybmVsIHZlcnNpb24uIEl0IG1pZ2h0IG5vdCBh cHBseSB0byB5b3VyIAo+PiB2ZXJzaW9uIGJ1dCBpdCBtYXkgaGVscCB5b3UgbWFrZSB0aGUgY2hh bmdlIHlvdSByZXF1aXJlLgo+Pgo+Pj4gQWxzbyB3aWxsIGluIHRoaXMgY2FzZSBvdGhlciBsdm1v aGJhIGZlYXR1cmVzIHdpbGwgd29yayBzbW9vdGhseSBpbiAKPj4+IHRoYXQgY2FzZQo+Pj4gb24g RGViaWFuLCBlc3BlY2lhbGx5IG11bHRpcGF0aD8KPj4KPj4gSXQncyB1bmxpa2VseSB5b3UnbGwg Z2V0IExWTSB0byB3b3JrIHdpdGggeW91ciBzZXR1cCBzaW5jZSB3ZSB1c2UgYSAKPj4gcGF0Y2hl ZCB2ZXJzaW9uIHRoYXQgYWNjZXB0cyBhbm90aGVyIG9wdGlvbiAoLS1tYXN0ZXIpIHdoaWNoIGFm Zm9yZHMgCj4+IHVzIGEgZGlmZmVyZW50IGxvY2tpbmcgbWVjaGFuaXNtIHRvIGFsbG93IHNoYXJl ZCBTUnMuIFRoaXMgb3B0aW9uIAo+PiBkb2Vzbid0IGV4aXN0IGluIHRoZSB1cHN0cmVhbSBEZWJp YW4gTFZNLgo+Pgo+PiBJdCBtYXkoISkgYmUgcG9zc2libGUgdG8gZ2V0IGl0IHRvIHdvcmsgaWYg eW91IHJlbW92ZSB0aGUgLS1tYXN0ZXIgCj4+IG9wdGlvbiBmcm9tIHRoZSBjYWxscyB0byBsdm0g aW4gdGhlIHNvdXJjZSBhbmQgZW5zdXJlIHRoYXQgeW91IGFyZSAKPj4gb25seSB1c2luZyB0aGVz ZSBTUnMgaW4gc2luZ2xlLWhvc3QgcG9vbHMuIEFnYWluLCB5b3VyIG1pbGVhZ2UgbWF5IHZhcnku Cj4+Cj4+IEhvcGUgdGhpcyBoZWxwcywKPj4KPj4gLVNpCj4+Cj4KPiBfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1hcGkgbWFpbGluZyBsaXN0Cj4g WGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWls bWFuL2xpc3RpbmZvL3hlbi1hcGkKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcK aHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Fri Jan 18 08:28:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 08:28:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7J3-0001S6-GO; Fri, 18 Jan 2013 08:28:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7J2-0001S1-Ay for xen-api@lists.xen.org; Fri, 18 Jan 2013 08:28:08 +0000 Received: from [85.158.137.99:28663] by server-7.bemta-3.messagelabs.com id 9E/5A-07262-79709F05; Fri, 18 Jan 2013 08:28:07 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1358497686!15103452!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30709 invoked from network); 18 Jan 2013 08:28:06 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2013 08:28:06 -0000 Received: by mail-lb0-f180.google.com with SMTP id gj3so2479361lbb.25 for ; Fri, 18 Jan 2013 00:28:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=rtmSq/XS8uroKdhN8K7oGLqLP8XEKlvJcEqxG63L4YY=; b=t0DkwoKoYdoMmcDhP/rat9cc6u8En3FaKtwW5IsCs2E3UCIKE7ZztIfZA6l8jfIui6 Pr33fqTmBZFJloYbsekYScXaYG23SBFy05X6OxN0CScG+3UNuXIGEHtrGgeutbgWIVPC AN8iPSrFRzQboke8I/x5+odYf1byoQsZPWLzvo8ASTpzP/M6eBCNtI6r5Z2n9gW4VRUf CqZmV0NqZ0FkmDXhfTNanYnVmh6XBaH8rCmpnbxyOAiJ0gYF/CXEkb9/sZlGippFTkUg 0hETq4h7pO+woPKK3mtupp3rOBDjjCub1bEkOV+HzohG/D42jaHFYmJuqvLU5S97FB+/ COag== X-Received: by 10.112.23.233 with SMTP id p9mr3449303lbf.6.1358497685997; Fri, 18 Jan 2013 00:28:05 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03? ([2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03]) by mx.google.com with ESMTPS id lx18sm1649041lab.14.2013.01.18.00.28.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Jan 2013 00:28:05 -0800 (PST) Message-ID: <50F90794.5050600@gmail.com> Date: Fri, 18 Jan 2013 12:28:04 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50F81FFC.1060201@vshosting.cz> In-Reply-To: <50F81FFC.1060201@vshosting.cz> Subject: Re: [Xen-API] XCP 1.1 SR_BACKEND_FAILURE_46 The VDI is not available [opterr=VDI already attached RW] issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WENQIDEuMT8KClRoZXJlIGlzIGZldyBjYXNlcyBmb3IgdGhhdCBtZXNzYWdlLgoKMSkgU29tZSBo b3N0cyBoYW5ncyBhbmQgd2FzIGZvcmNlZnVsbHkgcmVib290ZWQKMikgU29tZSBWTSBjcmFzaGVk IG5vIG5vIGxvY2sgaGFzIGJlZW4gcmVtb3ZlZCBvbiBub3JtYWwgaG9zdCAoYnVnKS4KCllvdSBj YW4KCjEpIHVzZSAvb3B0L3hlbnNvdXJjZS9zbS9yZXNldHZkaXMucHkKMikgTWFudWFsbHkgcmVt b3ZlIGxvY2sgZnJvbSBWREkgaW4gc3RhdGUuZGIgKGVlaywgZXh0cmVtZWx5IGxvdyBsZXZlbCAK aGFja2luZyB3aXRoIGhvcnJpYmxlIHBvc3NpYmxlIGNvbnNlcXVlbmNlcykKMykgQ2hlY2sgZXZl cnkgaG9zdCBpbiBwb29sIGZvciBoYW5nZWQgdGFwZGlza3MgKHNpbXBseSBjaGVjayBhbGwgCi9w cm9jL1BJRC9mZCBmb3IgZXZlcnkgdGFwZGlzayB0byBzZWUgaWYgc29tZW9uZSBzdGlsbCBsb2Nr aW5nIHZkaSkuCgpBbnl3YXksIHRoYXQgbWVzc2FnZSBpcyBqdXN0IG5vdGljZSB0aGF0IGxvY2sg aXMgcHJldmVudGluZyB0byBkbyBiYWQgCnN0dWZmLiBJZiBjYW4gYmUgZmFsc2UgYWxhcm0sIG9y IG1heSBiZSBsYXN0IHRoaW5nIG9uIEVhcnRoIHNhdmluZyB5b3VyIApWTXMgZnJvbSBjb21wbGV0 ZSB0cmFzaGluZy4KCjE3LjAxLjIwMTMgMTk6NTksIEphbiBNYXJ0aW7FryDQv9C40YjQtdGCOgo+ IEhlbGxvCj4KPiBJIGhhdmUgYSBwcm9ibGVtIHdpdGggVkRJIGFscmVhZHkgYXR0YWNoZWQgUlcg aW4gdGhlICJhZGRpbmcgdGFnIiBpbiAKPiBibGt0YXAyLiBUaGlzIGlzc3VlIGlzIG9uIGFsbCBo b3N0cyBpbiBwb29sIHdpdGggYXR0YWNoZWQgbHZtb2lzY3NpIFNSLgo+Cj4gSXMgdGhlcmUgYW55 IHNvbHV0aW9uIHRvIHRoaXMgcHJvYmxlbT8KPgo+IC92YXIvbG9nL1NNbG9nOgo+Cj4gWzMyNDg0 XSAyMDEzLTAxLTE3IDE0OjU5OjQ0LjIwMDg4MyB2ZGlfYWN0aXZhdGUgeydzcl91dWlkJzogCj4g J2UzMzI4MWViLWJhNGMtMzgyOS05YjYxLTdjNjQ3NjRkZmY5YycsICdzdWJ0YXNrX29mJzogCj4g J09wYXF1ZVJlZjo3OGRkN2M0OC0zODNiLTI1M2MtOWMyZC1hNjBlZGNiOWUyZTEnLCAndmRpX3Jl Zic6IAo+ICdPcGFxdWVSZWY6OWUzMjUyZjYtNDAzYi03MDQ1LTIxNDctNDAxYmVlYWZjOGNhJywg J3ZkaV9vbl9ib290JzogCj4gJ3BlcnNpc3QnLCAnYXJncyc6IFsndHJ1ZSddLCAndmRpX2xvY2F0 aW9uJzogCj4gJ2ZmNTRkZDRmLTVhZDMtNGNmMi04MTRmLTlhYmQxMmIxMDQ1ZScsICdob3N0X3Jl Zic6IAo+ICdPcGFxdWVSZWY6YThhZWI5ODAtYTU4NC1iZjdmLWQ5ZGQtMzc3ZjI3ZDAzMGY3Jywg J3Nlc3Npb25fcmVmJzogCj4gJ09wYXF1ZVJlZjo1YjhhZjcxZS0zNDMyLTBjZTYtM2VkNC00ZmUy ZmUwMTk3YTcnLCAnZGV2aWNlX2NvbmZpZyc6IAo+IHsndGFyZ2V0JzogJzE3Mi4xNi4xMzIuMScs ICdjaGFwcGFzc3dvcmRfc2VjcmV0JzogCj4gJ2I0N2EyM2E1LTQ5MzktZDYxMy04NjQxLTUxYzc0 MGI4ZGQ4NycsICdjaGFwdXNlcic6ICdjbG91ZDEnLCAKPiAndGFyZ2V0SVFOJzogJ2lxbi4yMDEx LTA0LmN6LnZzaG9zdGluZzpzdG9yYWdlMS5jbG91ZDEnLCAnU1JtYXN0ZXInOiAKPiAndHJ1ZScs ICdkZXZpY2UnOiAnL2Rldi9kaXNrL2J5LWlkL3Njc2ktMjZjNzU2ZTMwMjA2MzYyMzknLCAnU0NT SWlkJzogCj4gJzI2Yzc1NmUzMDIwNjM2MjM5JywgJ3RhcmdldGxpc3QnOiAnMTcyLjE2LjEzMi4x J30sICdjb21tYW5kJzogCj4gJ3ZkaV9hY3RpdmF0ZScsICd2ZGlfYWxsb3dfY2FjaGluZyc6ICdm YWxzZScsICdzcl9yZWYnOiAKPiAnT3BhcXVlUmVmOjlmYzhhNTRhLWRkNDUtNDMxMy1mNzgzLTc4 ODNiMzMzNTYwNCcsICd2ZGlfdXVpZCc6IAo+ICdmZjU0ZGQ0Zi01YWQzLTRjZjItODE0Zi05YWJk MTJiMTA0NWUnfQo+IFszMjQ4NF0gMjAxMy0wMS0xNyAxNDo1OTo0NC4yMDEyMzMgYmxrdGFwMi5h Y3RpdmF0ZQo+IFszMjQ4NF0gMjAxMy0wMS0xNyAxNDo1OTo0NC4yMDE0NzYgbG9jazogYWNxdWly ZWQgCj4gL3Zhci9sb2NrL3NtL2ZmNTRkZDRmLTVhZDMtNGNmMi04MTRmLTlhYmQxMmIxMDQ1ZS92 ZGkKPiBbMzI0ODRdIDIwMTMtMDEtMTcgMTQ6NTk6NDQuMjAxNTY3IEFkZGluZyB0YWcgdG86IAo+ IGZmNTRkZDRmLTVhZDMtNGNmMi04MTRmLTlhYmQxMmIxMDQ1ZQo+IFszMjQ4NF0gMjAxMy0wMS0x NyAxNDo1OTo0NC4yMzg5MjggKioqKiogQkxLVEFQMjo8ZnVuY3Rpb24gCj4gX2FjdGl2YXRlX2xv Y2tlZCBhdCAweGI2ZmJjMDY0PjogRVhDRVBUSU9OIHV0aWwuU01FeGNlcHRpb24sIFZESSAKPiBm ZjU0ZGQ0Zi01YWQzLTRjZjItODE0Zi05YWJkMTJiMTA0NWUgYWxyZWFkeSBhdHRhY2hlZCBSVwo+ IEZpbGUgIi9vcHQveGVuc291cmNlL3NtL2Jsa3RhcDIucHkiLCBsaW5lIDMyLCBpbiB3cmFwcGVy Cj4gcmV0ID0gb3Aoc2VsZiwgKmFyZ3MpCj4gRmlsZSAiL29wdC94ZW5zb3VyY2Uvc20vYmxrdGFw Mi5weSIsIGxpbmUgMTI5NywgaW4gX2FjdGl2YXRlX2xvY2tlZAo+IGlmIG5vdCBzZWxmLl9hZGRf dGFnKHZkaV91dWlkKToKPiBGaWxlICIvb3B0L3hlbnNvdXJjZS9zbS9ibGt0YXAyLnB5IiwgbGlu ZSAxMjMwLCBpbiBfYWRkX3RhZwo+IHJhaXNlIHV0aWwuU01FeGNlcHRpb24oIlZESSAlcyBhbHJl YWR5IGF0dGFjaGVkIFJXIiAlIHZkaV91dWlkKQo+Cj4gWzMyNDg0XSAyMDEzLTAxLTE3IDE0OjU5 OjQ0LjI3MjEzMCBSYWlzaW5nIGV4Y2VwdGlvbiBbNDYsIFRoZSBWREkgaXMgCj4gbm90IGF2YWls YWJsZSBbb3B0ZXJyPVZESSBmZjU0ZGQ0Zi01YWQzLTRjZjItODE0Zi05YWJkMTJiMTA0NWUgYWxy ZWFkeSAKPiBhdHRhY2hlZCBSV11dCj4gWzMyNDg0XSAyMDEzLTAxLTE3IDE0OjU5OjQ0LjI3MjMy NSBsb2NrOiByZWxlYXNlZCAKPiAvdmFyL2xvY2svc20vZmY1NGRkNGYtNWFkMy00Y2YyLTgxNGYt OWFiZDEyYjEwNDVlL3ZkaQo+IFszMjQ4NF0gMjAxMy0wMS0xNyAxNDo1OTo0NC4yNzI4NDcgKioq KiogdmRpX2FjdGl2YXRlOiBFWENFUFRJT04gCj4gU1IuU1JPU0Vycm9yLCBUaGUgVkRJIGlzIG5v dCBhdmFpbGFibGUgW29wdGVycj1WREkgCj4gZmY1NGRkNGYtNWFkMy00Y2YyLTgxNGYtOWFiZDEy YjEwNDVlIGFscmVhZHkgYXR0YWNoZWQgUlddCj4gRmlsZSAiL29wdC94ZW5zb3VyY2Uvc20vU1JD b21tYW5kLnB5IiwgbGluZSA5NCwgaW4gcnVuCj4gcmV0dXJuIHNlbGYuX3J1bl9sb2NrZWQoc3Ip Cj4gRmlsZSAiL29wdC94ZW5zb3VyY2Uvc20vU1JDb21tYW5kLnB5IiwgbGluZSAxMzEsIGluIF9y dW5fbG9ja2VkCj4gcmV0dXJuIHNlbGYuX3J1bihzciwgdGFyZ2V0KQo+IEZpbGUgIi9vcHQveGVu c291cmNlL3NtL1NSQ29tbWFuZC5weSIsIGxpbmUgMTgzLCBpbiBfcnVuCj4gY2FjaGluZ19wYXJh bXMpCj4gRmlsZSAiL29wdC94ZW5zb3VyY2Uvc20vYmxrdGFwMi5weSIsIGxpbmUgMTI4MywgaW4g YWN0aXZhdGUKPiBpZiBzZWxmLl9hY3RpdmF0ZV9sb2NrZWQoc3JfdXVpZCwgdmRpX3V1aWQsIGNh Y2hpbmdfcGFyYW1zKToKPiBGaWxlICIvb3B0L3hlbnNvdXJjZS9zbS9ibGt0YXAyLnB5IiwgbGlu ZSA0MCwgaW4gd3JhcHBlcgo+IHJhaXNlIHhzX2Vycm9ycy5YZW5FcnJvcihleGNUeXBlLCBvcHRl cnI9bXNnKQo+IEZpbGUgIi9vcHQveGVuc291cmNlL3NtL3hzX2Vycm9ycy5weSIsIGxpbmUgNDks IGluIF9faW5pdF9fCj4gcmFpc2UgU1IuU1JPU0Vycm9yKGVycm9yY29kZSwgZXJyb3JtZXNzYWdl KQo+CgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVu LWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4u b3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Fri Jan 18 08:28:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 08:28:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7J3-0001S6-GO; Fri, 18 Jan 2013 08:28:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7J2-0001S1-Ay for xen-api@lists.xen.org; Fri, 18 Jan 2013 08:28:08 +0000 Received: from [85.158.137.99:28663] by server-7.bemta-3.messagelabs.com id 9E/5A-07262-79709F05; Fri, 18 Jan 2013 08:28:07 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1358497686!15103452!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30709 invoked from network); 18 Jan 2013 08:28:06 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2013 08:28:06 -0000 Received: by mail-lb0-f180.google.com with SMTP id gj3so2479361lbb.25 for ; Fri, 18 Jan 2013 00:28:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=rtmSq/XS8uroKdhN8K7oGLqLP8XEKlvJcEqxG63L4YY=; b=t0DkwoKoYdoMmcDhP/rat9cc6u8En3FaKtwW5IsCs2E3UCIKE7ZztIfZA6l8jfIui6 Pr33fqTmBZFJloYbsekYScXaYG23SBFy05X6OxN0CScG+3UNuXIGEHtrGgeutbgWIVPC AN8iPSrFRzQboke8I/x5+odYf1byoQsZPWLzvo8ASTpzP/M6eBCNtI6r5Z2n9gW4VRUf CqZmV0NqZ0FkmDXhfTNanYnVmh6XBaH8rCmpnbxyOAiJ0gYF/CXEkb9/sZlGippFTkUg 0hETq4h7pO+woPKK3mtupp3rOBDjjCub1bEkOV+HzohG/D42jaHFYmJuqvLU5S97FB+/ COag== X-Received: by 10.112.23.233 with SMTP id p9mr3449303lbf.6.1358497685997; Fri, 18 Jan 2013 00:28:05 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03? ([2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03]) by mx.google.com with ESMTPS id lx18sm1649041lab.14.2013.01.18.00.28.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Jan 2013 00:28:05 -0800 (PST) Message-ID: <50F90794.5050600@gmail.com> Date: Fri, 18 Jan 2013 12:28:04 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50F81FFC.1060201@vshosting.cz> In-Reply-To: <50F81FFC.1060201@vshosting.cz> Subject: Re: [Xen-API] XCP 1.1 SR_BACKEND_FAILURE_46 The VDI is not available [opterr=VDI already attached RW] issue X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org WENQIDEuMT8KClRoZXJlIGlzIGZldyBjYXNlcyBmb3IgdGhhdCBtZXNzYWdlLgoKMSkgU29tZSBo b3N0cyBoYW5ncyBhbmQgd2FzIGZvcmNlZnVsbHkgcmVib290ZWQKMikgU29tZSBWTSBjcmFzaGVk IG5vIG5vIGxvY2sgaGFzIGJlZW4gcmVtb3ZlZCBvbiBub3JtYWwgaG9zdCAoYnVnKS4KCllvdSBj YW4KCjEpIHVzZSAvb3B0L3hlbnNvdXJjZS9zbS9yZXNldHZkaXMucHkKMikgTWFudWFsbHkgcmVt b3ZlIGxvY2sgZnJvbSBWREkgaW4gc3RhdGUuZGIgKGVlaywgZXh0cmVtZWx5IGxvdyBsZXZlbCAK aGFja2luZyB3aXRoIGhvcnJpYmxlIHBvc3NpYmxlIGNvbnNlcXVlbmNlcykKMykgQ2hlY2sgZXZl cnkgaG9zdCBpbiBwb29sIGZvciBoYW5nZWQgdGFwZGlza3MgKHNpbXBseSBjaGVjayBhbGwgCi9w cm9jL1BJRC9mZCBmb3IgZXZlcnkgdGFwZGlzayB0byBzZWUgaWYgc29tZW9uZSBzdGlsbCBsb2Nr aW5nIHZkaSkuCgpBbnl3YXksIHRoYXQgbWVzc2FnZSBpcyBqdXN0IG5vdGljZSB0aGF0IGxvY2sg aXMgcHJldmVudGluZyB0byBkbyBiYWQgCnN0dWZmLiBJZiBjYW4gYmUgZmFsc2UgYWxhcm0sIG9y IG1heSBiZSBsYXN0IHRoaW5nIG9uIEVhcnRoIHNhdmluZyB5b3VyIApWTXMgZnJvbSBjb21wbGV0 ZSB0cmFzaGluZy4KCjE3LjAxLjIwMTMgMTk6NTksIEphbiBNYXJ0aW7FryDQv9C40YjQtdGCOgo+ IEhlbGxvCj4KPiBJIGhhdmUgYSBwcm9ibGVtIHdpdGggVkRJIGFscmVhZHkgYXR0YWNoZWQgUlcg aW4gdGhlICJhZGRpbmcgdGFnIiBpbiAKPiBibGt0YXAyLiBUaGlzIGlzc3VlIGlzIG9uIGFsbCBo b3N0cyBpbiBwb29sIHdpdGggYXR0YWNoZWQgbHZtb2lzY3NpIFNSLgo+Cj4gSXMgdGhlcmUgYW55 IHNvbHV0aW9uIHRvIHRoaXMgcHJvYmxlbT8KPgo+IC92YXIvbG9nL1NNbG9nOgo+Cj4gWzMyNDg0 XSAyMDEzLTAxLTE3IDE0OjU5OjQ0LjIwMDg4MyB2ZGlfYWN0aXZhdGUgeydzcl91dWlkJzogCj4g J2UzMzI4MWViLWJhNGMtMzgyOS05YjYxLTdjNjQ3NjRkZmY5YycsICdzdWJ0YXNrX29mJzogCj4g J09wYXF1ZVJlZjo3OGRkN2M0OC0zODNiLTI1M2MtOWMyZC1hNjBlZGNiOWUyZTEnLCAndmRpX3Jl Zic6IAo+ICdPcGFxdWVSZWY6OWUzMjUyZjYtNDAzYi03MDQ1LTIxNDctNDAxYmVlYWZjOGNhJywg J3ZkaV9vbl9ib290JzogCj4gJ3BlcnNpc3QnLCAnYXJncyc6IFsndHJ1ZSddLCAndmRpX2xvY2F0 aW9uJzogCj4gJ2ZmNTRkZDRmLTVhZDMtNGNmMi04MTRmLTlhYmQxMmIxMDQ1ZScsICdob3N0X3Jl Zic6IAo+ICdPcGFxdWVSZWY6YThhZWI5ODAtYTU4NC1iZjdmLWQ5ZGQtMzc3ZjI3ZDAzMGY3Jywg J3Nlc3Npb25fcmVmJzogCj4gJ09wYXF1ZVJlZjo1YjhhZjcxZS0zNDMyLTBjZTYtM2VkNC00ZmUy ZmUwMTk3YTcnLCAnZGV2aWNlX2NvbmZpZyc6IAo+IHsndGFyZ2V0JzogJzE3Mi4xNi4xMzIuMScs ICdjaGFwcGFzc3dvcmRfc2VjcmV0JzogCj4gJ2I0N2EyM2E1LTQ5MzktZDYxMy04NjQxLTUxYzc0 MGI4ZGQ4NycsICdjaGFwdXNlcic6ICdjbG91ZDEnLCAKPiAndGFyZ2V0SVFOJzogJ2lxbi4yMDEx LTA0LmN6LnZzaG9zdGluZzpzdG9yYWdlMS5jbG91ZDEnLCAnU1JtYXN0ZXInOiAKPiAndHJ1ZScs ICdkZXZpY2UnOiAnL2Rldi9kaXNrL2J5LWlkL3Njc2ktMjZjNzU2ZTMwMjA2MzYyMzknLCAnU0NT SWlkJzogCj4gJzI2Yzc1NmUzMDIwNjM2MjM5JywgJ3RhcmdldGxpc3QnOiAnMTcyLjE2LjEzMi4x J30sICdjb21tYW5kJzogCj4gJ3ZkaV9hY3RpdmF0ZScsICd2ZGlfYWxsb3dfY2FjaGluZyc6ICdm YWxzZScsICdzcl9yZWYnOiAKPiAnT3BhcXVlUmVmOjlmYzhhNTRhLWRkNDUtNDMxMy1mNzgzLTc4 ODNiMzMzNTYwNCcsICd2ZGlfdXVpZCc6IAo+ICdmZjU0ZGQ0Zi01YWQzLTRjZjItODE0Zi05YWJk MTJiMTA0NWUnfQo+IFszMjQ4NF0gMjAxMy0wMS0xNyAxNDo1OTo0NC4yMDEyMzMgYmxrdGFwMi5h Y3RpdmF0ZQo+IFszMjQ4NF0gMjAxMy0wMS0xNyAxNDo1OTo0NC4yMDE0NzYgbG9jazogYWNxdWly ZWQgCj4gL3Zhci9sb2NrL3NtL2ZmNTRkZDRmLTVhZDMtNGNmMi04MTRmLTlhYmQxMmIxMDQ1ZS92 ZGkKPiBbMzI0ODRdIDIwMTMtMDEtMTcgMTQ6NTk6NDQuMjAxNTY3IEFkZGluZyB0YWcgdG86IAo+ IGZmNTRkZDRmLTVhZDMtNGNmMi04MTRmLTlhYmQxMmIxMDQ1ZQo+IFszMjQ4NF0gMjAxMy0wMS0x NyAxNDo1OTo0NC4yMzg5MjggKioqKiogQkxLVEFQMjo8ZnVuY3Rpb24gCj4gX2FjdGl2YXRlX2xv Y2tlZCBhdCAweGI2ZmJjMDY0PjogRVhDRVBUSU9OIHV0aWwuU01FeGNlcHRpb24sIFZESSAKPiBm ZjU0ZGQ0Zi01YWQzLTRjZjItODE0Zi05YWJkMTJiMTA0NWUgYWxyZWFkeSBhdHRhY2hlZCBSVwo+ IEZpbGUgIi9vcHQveGVuc291cmNlL3NtL2Jsa3RhcDIucHkiLCBsaW5lIDMyLCBpbiB3cmFwcGVy Cj4gcmV0ID0gb3Aoc2VsZiwgKmFyZ3MpCj4gRmlsZSAiL29wdC94ZW5zb3VyY2Uvc20vYmxrdGFw Mi5weSIsIGxpbmUgMTI5NywgaW4gX2FjdGl2YXRlX2xvY2tlZAo+IGlmIG5vdCBzZWxmLl9hZGRf dGFnKHZkaV91dWlkKToKPiBGaWxlICIvb3B0L3hlbnNvdXJjZS9zbS9ibGt0YXAyLnB5IiwgbGlu ZSAxMjMwLCBpbiBfYWRkX3RhZwo+IHJhaXNlIHV0aWwuU01FeGNlcHRpb24oIlZESSAlcyBhbHJl YWR5IGF0dGFjaGVkIFJXIiAlIHZkaV91dWlkKQo+Cj4gWzMyNDg0XSAyMDEzLTAxLTE3IDE0OjU5 OjQ0LjI3MjEzMCBSYWlzaW5nIGV4Y2VwdGlvbiBbNDYsIFRoZSBWREkgaXMgCj4gbm90IGF2YWls YWJsZSBbb3B0ZXJyPVZESSBmZjU0ZGQ0Zi01YWQzLTRjZjItODE0Zi05YWJkMTJiMTA0NWUgYWxy ZWFkeSAKPiBhdHRhY2hlZCBSV11dCj4gWzMyNDg0XSAyMDEzLTAxLTE3IDE0OjU5OjQ0LjI3MjMy NSBsb2NrOiByZWxlYXNlZCAKPiAvdmFyL2xvY2svc20vZmY1NGRkNGYtNWFkMy00Y2YyLTgxNGYt OWFiZDEyYjEwNDVlL3ZkaQo+IFszMjQ4NF0gMjAxMy0wMS0xNyAxNDo1OTo0NC4yNzI4NDcgKioq KiogdmRpX2FjdGl2YXRlOiBFWENFUFRJT04gCj4gU1IuU1JPU0Vycm9yLCBUaGUgVkRJIGlzIG5v dCBhdmFpbGFibGUgW29wdGVycj1WREkgCj4gZmY1NGRkNGYtNWFkMy00Y2YyLTgxNGYtOWFiZDEy YjEwNDVlIGFscmVhZHkgYXR0YWNoZWQgUlddCj4gRmlsZSAiL29wdC94ZW5zb3VyY2Uvc20vU1JD b21tYW5kLnB5IiwgbGluZSA5NCwgaW4gcnVuCj4gcmV0dXJuIHNlbGYuX3J1bl9sb2NrZWQoc3Ip Cj4gRmlsZSAiL29wdC94ZW5zb3VyY2Uvc20vU1JDb21tYW5kLnB5IiwgbGluZSAxMzEsIGluIF9y dW5fbG9ja2VkCj4gcmV0dXJuIHNlbGYuX3J1bihzciwgdGFyZ2V0KQo+IEZpbGUgIi9vcHQveGVu c291cmNlL3NtL1NSQ29tbWFuZC5weSIsIGxpbmUgMTgzLCBpbiBfcnVuCj4gY2FjaGluZ19wYXJh bXMpCj4gRmlsZSAiL29wdC94ZW5zb3VyY2Uvc20vYmxrdGFwMi5weSIsIGxpbmUgMTI4MywgaW4g YWN0aXZhdGUKPiBpZiBzZWxmLl9hY3RpdmF0ZV9sb2NrZWQoc3JfdXVpZCwgdmRpX3V1aWQsIGNh Y2hpbmdfcGFyYW1zKToKPiBGaWxlICIvb3B0L3hlbnNvdXJjZS9zbS9ibGt0YXAyLnB5IiwgbGlu ZSA0MCwgaW4gd3JhcHBlcgo+IHJhaXNlIHhzX2Vycm9ycy5YZW5FcnJvcihleGNUeXBlLCBvcHRl cnI9bXNnKQo+IEZpbGUgIi9vcHQveGVuc291cmNlL3NtL3hzX2Vycm9ycy5weSIsIGxpbmUgNDks IGluIF9faW5pdF9fCj4gcmFpc2UgU1IuU1JPU0Vycm9yKGVycm9yY29kZSwgZXJyb3JtZXNzYWdl KQo+CgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVu LWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4u b3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Fri Jan 18 09:07:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 09:07:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7uv-0003ZA-KO; Fri, 18 Jan 2013 09:07:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7ut-0003Z2-55 for xen-api@lists.xen.org; Fri, 18 Jan 2013 09:07:15 +0000 Received: from [85.158.139.211:64314] by server-12.bemta-5.messagelabs.com id E6/6D-31102-2C019F05; Fri, 18 Jan 2013 09:07:14 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-14.tower-206.messagelabs.com!1358500020!18604740!1 X-Originating-IP: [94.100.177.102] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12175 invoked from network); 18 Jan 2013 09:07:00 -0000 Received: from smtp42.i.mail.ru (HELO smtp42.i.mail.ru) (94.100.177.102) by server-14.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jan 2013 09:07:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=PR++07qBOofd6NouN1188fy5SIErA4Qij8tllNEjjQA=; b=KnlY7L8eCd8oWtCTzch/0e/Y7RAMTcjpOQkY4Te6JHdmpnQfFGFCAJP96fQTdRg0Lc9H6nCsfTn9giVInFX/P6my0wI22VvIPsaiHS8gNZlNsoBg89x27HqQqnxct4VdKBlQkngdhnQdFMhIJl+Wt45NNtqjRDWL0oUoxaUyLZY=; Received: from [78.36.60.25] (port=9980 helo=[10.168.2.113]) by smtp42.i.mail.ru with esmtpa (envelope-from ) id 1Tw7ud-0001fl-PG; Fri, 18 Jan 2013 13:06:59 +0400 Message-ID: <50F910B3.8090004@bk.ru> Date: Fri, 18 Jan 2013 13:06:59 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> <50F8444F.8020109@bk.ru> <50F9066D.6020005@gmail.com> In-Reply-To: <50F9066D.6020005@gmail.com> X-Spam: Not detected X-Mras: Ok Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SXQgc3VwcG9zZWQgdGhhdCBvbmx5IG9uZSBYQ1AgaG9zdCB3aWxsIGJlIGNvbm5lY3RlZCB0byB0 aGF0IHN0b3JhZ2UgCihwb3J0cyBQMjAwMCB6b25pbmcgYWxzbyBjb25maWd1cmVkIG9ubHkgZm9y IHRoYXQgaG9zdCkuIEFsc28gaWYgdGhpcyAKc3RvcmFnZSB3aWxsIGJlIGNyZWF0ZWQgYXMgbG9j YWwgKHNoYXJlZD1mYWxzZSkgb3RoZXIgWENQIGhvc3RzIGFuZCAKYmFja2dyb3VuZCBwcm9jY2Vz c2VzIGNhbiBhY2Nlc3MvY29sbGlkZSB0byB0aGF0IFNSIGFueXdheT8KCjE4LjAxLjIwMTMgMTI6 MjMsIEdlb3JnZSBTaHVrbGluINC/0LjRiNC10YI6Cj4gWW91IHNob3VsZCBiZSAxNDYlIHN1cmUg bm8gb3RoZXIgaG9zdHMgd2lsbCBhY2Nlc3Mgc3RvcmFnZSBpbiB0aGF0IGNhc2UuCj4gSWYgc29t ZSBiYWNrZ3JvdW5kIHByb2Nlc3MgKGYuZS4gVkhEIGNvYWxlc2luZykgd2lsbCBjb2xsaWRlIHdp dGggb3RoZXJzCj4gaG9zdHMgYWN0aXZpdHkgb24gU1IsIHlvdSB3aWxsIHRyYXNoIHNvbWUgcmFu ZG9tIHBlaWNlIG9mIGRhdGEgKG1heSBiZQo+IGluY2x1ZGluZyBMVk0gbWV0YWRhdGEpLgo+Cj4g MTcuMDEuMjAxMyAyMjozNCwgQW5kcmV5INC/0LjRiNC10YI6Cj4+IFRoYW5rIHlvdSBmb3IgdGhl IHBhdGNoLCB3aWxsIHRyeSB0byBhcHBseSBpdC4KPj4KPj4gSW4gb3VyIGNvbmZpZ3VyYXRpb24g d2UgZG9uJ3QgbmVlZCBzaGFyZWQgbHZtIFNSIGJlY2F1c2Ugd2UgaGF2ZSBvbmUKPj4gc2VydmVy IHdpdGggZHVhbC1wYXRoIGRpcmVjdGx5IGF0dGFjaGVkICBQMjAwMCBTQU4uIEkgYWxzbyBoYXZl Cj4+IGNvbmZpZ3VyZWQgbXVsdGlwYXRoIGZvciB0aGUgTFVOcy4gU28gbWF5IGJlIHdlIGNhbiBj cmVhdGUgbG9jYWwgTFZNCj4+IFNSIHRoZW4gZm9yIHRoZSBtdWx0aXBhdGggZGV2aWNlcz8KPj4K Pj4gMTcuMDEuMjAxMyAxODoxOSwgU2ltb24gQmVhdW1vbnQg0L/QuNGI0LXRgjoKPj4+PiAtLS0t LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQo+Pj4+IEZyb206IHhlbi1hcGktYm91bmNlc0BsaXN0cy54 ZW4ub3JnCj4+Pj4gW21haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gT24KPj4+ PiBCZWhhbGYgT2YgQW5kcmV5Cj4+Pj4gU2VudDogMTcgSmFudWFyeSAyMDEzIDEyOjU2IFBNCj4+ Pj4gVG86IHhlbi1hcGlAbGlzdHMueGVuLm9yZwo+Pj4+IFN1YmplY3Q6IFtYZW4tQVBJXSB4Y3At eGFwaSBkZXZzY2FuLnB5IGtlcm5lbCBzdXBwb3J0Cj4+Pj4KPj4+PiBJIGluc3RhbGxlZCB4Y3At eGFwaSBvbiB0aGUgRGViaWFuIFdoZWV6eSBhbmQgY2FuJ3QgZ2V0IExWTW9IQkEgdG8KPj4+PiB3 b3JrOgo+Pj4+Cj4+Pj4gc3RkZXJyOiBUcmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwgbGFzdCk6 Cj4+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9MVk1vSEJBU1IiLCBsaW5lIDIyMCwgaW4g PG1vZHVsZT4KPj4+PiAgICAgICBTUkNvbW1hbmQucnVuKExWSERvSEJBU1IsIERSSVZFUl9JTkZP KQo+Pj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vU1JDb21tYW5kLnB5IiwgbGluZSAyNjEs IGluIHJ1bgo+Pj4+ICAgICAgIHNyID0gZHJpdmVyKGNtZCwgY21kLnNyX3V1aWQpCj4+Pj4gICAg IEZpbGUgIi91c3IvbGliL3hjcC9zbS9TUi5weSIsIGxpbmUgMTM2LCBpbiBfX2luaXRfXwo+Pj4+ ICAgICAgIHNlbGYubG9hZChzcl91dWlkKQo+Pj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20v TFZNb0hCQVNSIiwgbGluZSA5NCwgaW4gbG9hZAo+Pj4+ICAgICAgIHByaW50ID4+c3lzLnN0ZGVy cixzZWxmLmhiYXNyLnByaW50X2RldnMoKQo+Pj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20v SEJBU1IucHkiLCBsaW5lIDIyNCwgaW4gcHJpbnRfZGV2cwo+Pj4+ICAgICAgIHNlbGYuX2luaXRf aGJhZGljdCgpCj4+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9IQkFTUi5weSIsIGxpbmUg NjEsIGluIF9pbml0X2hiYWRpY3QKPj4+PiAgICAgICBkaWN0ID0gZGV2c2Nhbi5hZGFwdGVycyhm aWx0ZXJzdHI9c2VsZi50eXBlKQo+Pj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vZGV2c2Nh bi5weSIsIGxpbmUgMTY4LCBpbiBhZGFwdGVycwo+Pj4+IGdsb2IuZ2xvYihvcy5wYXRoLmpvaW4o cGF0aCwiZGV2aWNlIiwiYmxvY2s6KiIpKVswXSkuc3BsaXQoJzonKVsxXQo+Pj4+IEluZGV4RXJy b3I6IGxpc3QgaW5kZXggb3V0IG9mIHJhbmdlCj4+Pj4KPj4+Pgo+Pj4+IENhbiB5b3UgcGxlYXNl IHNlbmQgZGV2c2Nhbi5weSBwYXRjaCB0byBzdXBwb3J0IGx2bW9oYmEgaW4ga2VybmVsIDMuWC4K Pj4+Cj4+PiBJIGhhdmUgYXR0YWNoZWQgdGhlIHBhdGNoIGluIHF1ZXN0aW9uLiBJdCB1c2VzIHRo ZSByaWdodCBzeXNmcyBwYXRocwo+Pj4gYWZ0ZXIgZGV0ZWN0aW5nIHRoZSBrZXJuZWwgdmVyc2lv bi4gSXQgbWlnaHQgbm90IGFwcGx5IHRvIHlvdXIKPj4+IHZlcnNpb24gYnV0IGl0IG1heSBoZWxw IHlvdSBtYWtlIHRoZSBjaGFuZ2UgeW91IHJlcXVpcmUuCj4+Pgo+Pj4+IEFsc28gd2lsbCBpbiB0 aGlzIGNhc2Ugb3RoZXIgbHZtb2hiYSBmZWF0dXJlcyB3aWxsIHdvcmsgc21vb3RobHkgaW4KPj4+ PiB0aGF0IGNhc2UKPj4+PiBvbiBEZWJpYW4sIGVzcGVjaWFsbHkgbXVsdGlwYXRoPwo+Pj4KPj4+ IEl0J3MgdW5saWtlbHkgeW91J2xsIGdldCBMVk0gdG8gd29yayB3aXRoIHlvdXIgc2V0dXAgc2lu Y2Ugd2UgdXNlIGEKPj4+IHBhdGNoZWQgdmVyc2lvbiB0aGF0IGFjY2VwdHMgYW5vdGhlciBvcHRp b24gKC0tbWFzdGVyKSB3aGljaCBhZmZvcmRzCj4+PiB1cyBhIGRpZmZlcmVudCBsb2NraW5nIG1l Y2hhbmlzbSB0byBhbGxvdyBzaGFyZWQgU1JzLiBUaGlzIG9wdGlvbgo+Pj4gZG9lc24ndCBleGlz dCBpbiB0aGUgdXBzdHJlYW0gRGViaWFuIExWTS4KPj4+Cj4+PiBJdCBtYXkoISkgYmUgcG9zc2li bGUgdG8gZ2V0IGl0IHRvIHdvcmsgaWYgeW91IHJlbW92ZSB0aGUgLS1tYXN0ZXIKPj4+IG9wdGlv biBmcm9tIHRoZSBjYWxscyB0byBsdm0gaW4gdGhlIHNvdXJjZSBhbmQgZW5zdXJlIHRoYXQgeW91 IGFyZQo+Pj4gb25seSB1c2luZyB0aGVzZSBTUnMgaW4gc2luZ2xlLWhvc3QgcG9vbHMuIEFnYWlu LCB5b3VyIG1pbGVhZ2UgbWF5IHZhcnkuCj4+Pgo+Pj4gSG9wZSB0aGlzIGhlbHBzLAo+Pj4KPj4+ IC1TaQo+Pj4KPj4KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KPj4gWGVuLWFwaSBtYWlsaW5nIGxpc3QKPj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4+ IGh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCj4K Pgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gWGVu LWFwaSBtYWlsaW5nIGxpc3QKPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPiBodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQoKX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWlsaW5nIGxpc3QKWGVu LWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9s aXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Fri Jan 18 09:07:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 09:07:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7uv-0003ZA-KO; Fri, 18 Jan 2013 09:07:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw7ut-0003Z2-55 for xen-api@lists.xen.org; Fri, 18 Jan 2013 09:07:15 +0000 Received: from [85.158.139.211:64314] by server-12.bemta-5.messagelabs.com id E6/6D-31102-2C019F05; Fri, 18 Jan 2013 09:07:14 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-14.tower-206.messagelabs.com!1358500020!18604740!1 X-Originating-IP: [94.100.177.102] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12175 invoked from network); 18 Jan 2013 09:07:00 -0000 Received: from smtp42.i.mail.ru (HELO smtp42.i.mail.ru) (94.100.177.102) by server-14.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jan 2013 09:07:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=PR++07qBOofd6NouN1188fy5SIErA4Qij8tllNEjjQA=; b=KnlY7L8eCd8oWtCTzch/0e/Y7RAMTcjpOQkY4Te6JHdmpnQfFGFCAJP96fQTdRg0Lc9H6nCsfTn9giVInFX/P6my0wI22VvIPsaiHS8gNZlNsoBg89x27HqQqnxct4VdKBlQkngdhnQdFMhIJl+Wt45NNtqjRDWL0oUoxaUyLZY=; Received: from [78.36.60.25] (port=9980 helo=[10.168.2.113]) by smtp42.i.mail.ru with esmtpa (envelope-from ) id 1Tw7ud-0001fl-PG; Fri, 18 Jan 2013 13:06:59 +0400 Message-ID: <50F910B3.8090004@bk.ru> Date: Fri, 18 Jan 2013 13:06:59 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> <50F8444F.8020109@bk.ru> <50F9066D.6020005@gmail.com> In-Reply-To: <50F9066D.6020005@gmail.com> X-Spam: Not detected X-Mras: Ok Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SXQgc3VwcG9zZWQgdGhhdCBvbmx5IG9uZSBYQ1AgaG9zdCB3aWxsIGJlIGNvbm5lY3RlZCB0byB0 aGF0IHN0b3JhZ2UgCihwb3J0cyBQMjAwMCB6b25pbmcgYWxzbyBjb25maWd1cmVkIG9ubHkgZm9y IHRoYXQgaG9zdCkuIEFsc28gaWYgdGhpcyAKc3RvcmFnZSB3aWxsIGJlIGNyZWF0ZWQgYXMgbG9j YWwgKHNoYXJlZD1mYWxzZSkgb3RoZXIgWENQIGhvc3RzIGFuZCAKYmFja2dyb3VuZCBwcm9jY2Vz c2VzIGNhbiBhY2Nlc3MvY29sbGlkZSB0byB0aGF0IFNSIGFueXdheT8KCjE4LjAxLjIwMTMgMTI6 MjMsIEdlb3JnZSBTaHVrbGluINC/0LjRiNC10YI6Cj4gWW91IHNob3VsZCBiZSAxNDYlIHN1cmUg bm8gb3RoZXIgaG9zdHMgd2lsbCBhY2Nlc3Mgc3RvcmFnZSBpbiB0aGF0IGNhc2UuCj4gSWYgc29t ZSBiYWNrZ3JvdW5kIHByb2Nlc3MgKGYuZS4gVkhEIGNvYWxlc2luZykgd2lsbCBjb2xsaWRlIHdp dGggb3RoZXJzCj4gaG9zdHMgYWN0aXZpdHkgb24gU1IsIHlvdSB3aWxsIHRyYXNoIHNvbWUgcmFu ZG9tIHBlaWNlIG9mIGRhdGEgKG1heSBiZQo+IGluY2x1ZGluZyBMVk0gbWV0YWRhdGEpLgo+Cj4g MTcuMDEuMjAxMyAyMjozNCwgQW5kcmV5INC/0LjRiNC10YI6Cj4+IFRoYW5rIHlvdSBmb3IgdGhl IHBhdGNoLCB3aWxsIHRyeSB0byBhcHBseSBpdC4KPj4KPj4gSW4gb3VyIGNvbmZpZ3VyYXRpb24g d2UgZG9uJ3QgbmVlZCBzaGFyZWQgbHZtIFNSIGJlY2F1c2Ugd2UgaGF2ZSBvbmUKPj4gc2VydmVy IHdpdGggZHVhbC1wYXRoIGRpcmVjdGx5IGF0dGFjaGVkICBQMjAwMCBTQU4uIEkgYWxzbyBoYXZl Cj4+IGNvbmZpZ3VyZWQgbXVsdGlwYXRoIGZvciB0aGUgTFVOcy4gU28gbWF5IGJlIHdlIGNhbiBj cmVhdGUgbG9jYWwgTFZNCj4+IFNSIHRoZW4gZm9yIHRoZSBtdWx0aXBhdGggZGV2aWNlcz8KPj4K Pj4gMTcuMDEuMjAxMyAxODoxOSwgU2ltb24gQmVhdW1vbnQg0L/QuNGI0LXRgjoKPj4+PiAtLS0t LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQo+Pj4+IEZyb206IHhlbi1hcGktYm91bmNlc0BsaXN0cy54 ZW4ub3JnCj4+Pj4gW21haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gT24KPj4+ PiBCZWhhbGYgT2YgQW5kcmV5Cj4+Pj4gU2VudDogMTcgSmFudWFyeSAyMDEzIDEyOjU2IFBNCj4+ Pj4gVG86IHhlbi1hcGlAbGlzdHMueGVuLm9yZwo+Pj4+IFN1YmplY3Q6IFtYZW4tQVBJXSB4Y3At eGFwaSBkZXZzY2FuLnB5IGtlcm5lbCBzdXBwb3J0Cj4+Pj4KPj4+PiBJIGluc3RhbGxlZCB4Y3At eGFwaSBvbiB0aGUgRGViaWFuIFdoZWV6eSBhbmQgY2FuJ3QgZ2V0IExWTW9IQkEgdG8KPj4+PiB3 b3JrOgo+Pj4+Cj4+Pj4gc3RkZXJyOiBUcmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwgbGFzdCk6 Cj4+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9MVk1vSEJBU1IiLCBsaW5lIDIyMCwgaW4g PG1vZHVsZT4KPj4+PiAgICAgICBTUkNvbW1hbmQucnVuKExWSERvSEJBU1IsIERSSVZFUl9JTkZP KQo+Pj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vU1JDb21tYW5kLnB5IiwgbGluZSAyNjEs IGluIHJ1bgo+Pj4+ICAgICAgIHNyID0gZHJpdmVyKGNtZCwgY21kLnNyX3V1aWQpCj4+Pj4gICAg IEZpbGUgIi91c3IvbGliL3hjcC9zbS9TUi5weSIsIGxpbmUgMTM2LCBpbiBfX2luaXRfXwo+Pj4+ ICAgICAgIHNlbGYubG9hZChzcl91dWlkKQo+Pj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20v TFZNb0hCQVNSIiwgbGluZSA5NCwgaW4gbG9hZAo+Pj4+ICAgICAgIHByaW50ID4+c3lzLnN0ZGVy cixzZWxmLmhiYXNyLnByaW50X2RldnMoKQo+Pj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20v SEJBU1IucHkiLCBsaW5lIDIyNCwgaW4gcHJpbnRfZGV2cwo+Pj4+ICAgICAgIHNlbGYuX2luaXRf aGJhZGljdCgpCj4+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9IQkFTUi5weSIsIGxpbmUg NjEsIGluIF9pbml0X2hiYWRpY3QKPj4+PiAgICAgICBkaWN0ID0gZGV2c2Nhbi5hZGFwdGVycyhm aWx0ZXJzdHI9c2VsZi50eXBlKQo+Pj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vZGV2c2Nh bi5weSIsIGxpbmUgMTY4LCBpbiBhZGFwdGVycwo+Pj4+IGdsb2IuZ2xvYihvcy5wYXRoLmpvaW4o cGF0aCwiZGV2aWNlIiwiYmxvY2s6KiIpKVswXSkuc3BsaXQoJzonKVsxXQo+Pj4+IEluZGV4RXJy b3I6IGxpc3QgaW5kZXggb3V0IG9mIHJhbmdlCj4+Pj4KPj4+Pgo+Pj4+IENhbiB5b3UgcGxlYXNl IHNlbmQgZGV2c2Nhbi5weSBwYXRjaCB0byBzdXBwb3J0IGx2bW9oYmEgaW4ga2VybmVsIDMuWC4K Pj4+Cj4+PiBJIGhhdmUgYXR0YWNoZWQgdGhlIHBhdGNoIGluIHF1ZXN0aW9uLiBJdCB1c2VzIHRo ZSByaWdodCBzeXNmcyBwYXRocwo+Pj4gYWZ0ZXIgZGV0ZWN0aW5nIHRoZSBrZXJuZWwgdmVyc2lv bi4gSXQgbWlnaHQgbm90IGFwcGx5IHRvIHlvdXIKPj4+IHZlcnNpb24gYnV0IGl0IG1heSBoZWxw IHlvdSBtYWtlIHRoZSBjaGFuZ2UgeW91IHJlcXVpcmUuCj4+Pgo+Pj4+IEFsc28gd2lsbCBpbiB0 aGlzIGNhc2Ugb3RoZXIgbHZtb2hiYSBmZWF0dXJlcyB3aWxsIHdvcmsgc21vb3RobHkgaW4KPj4+ PiB0aGF0IGNhc2UKPj4+PiBvbiBEZWJpYW4sIGVzcGVjaWFsbHkgbXVsdGlwYXRoPwo+Pj4KPj4+ IEl0J3MgdW5saWtlbHkgeW91J2xsIGdldCBMVk0gdG8gd29yayB3aXRoIHlvdXIgc2V0dXAgc2lu Y2Ugd2UgdXNlIGEKPj4+IHBhdGNoZWQgdmVyc2lvbiB0aGF0IGFjY2VwdHMgYW5vdGhlciBvcHRp b24gKC0tbWFzdGVyKSB3aGljaCBhZmZvcmRzCj4+PiB1cyBhIGRpZmZlcmVudCBsb2NraW5nIG1l Y2hhbmlzbSB0byBhbGxvdyBzaGFyZWQgU1JzLiBUaGlzIG9wdGlvbgo+Pj4gZG9lc24ndCBleGlz dCBpbiB0aGUgdXBzdHJlYW0gRGViaWFuIExWTS4KPj4+Cj4+PiBJdCBtYXkoISkgYmUgcG9zc2li bGUgdG8gZ2V0IGl0IHRvIHdvcmsgaWYgeW91IHJlbW92ZSB0aGUgLS1tYXN0ZXIKPj4+IG9wdGlv biBmcm9tIHRoZSBjYWxscyB0byBsdm0gaW4gdGhlIHNvdXJjZSBhbmQgZW5zdXJlIHRoYXQgeW91 IGFyZQo+Pj4gb25seSB1c2luZyB0aGVzZSBTUnMgaW4gc2luZ2xlLWhvc3QgcG9vbHMuIEFnYWlu LCB5b3VyIG1pbGVhZ2UgbWF5IHZhcnkuCj4+Pgo+Pj4gSG9wZSB0aGlzIGhlbHBzLAo+Pj4KPj4+ IC1TaQo+Pj4KPj4KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KPj4gWGVuLWFwaSBtYWlsaW5nIGxpc3QKPj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4+ IGh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCj4K Pgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gWGVu LWFwaSBtYWlsaW5nIGxpc3QKPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPiBodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQoKX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWFwaSBtYWlsaW5nIGxpc3QKWGVu LWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9s aXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Fri Jan 18 11:10:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 11:10:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw9pa-0001xl-Oy; Fri, 18 Jan 2013 11:09:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw9pZ-0001xg-CL for xen-api@lists.xen.org; Fri, 18 Jan 2013 11:09:53 +0000 Received: from [85.158.139.211:41538] by server-11.bemta-5.messagelabs.com id A7/35-07660-08D29F05; Fri, 18 Jan 2013 11:09:52 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-6.tower-206.messagelabs.com!1358507391!18682084!1 X-Originating-IP: [94.100.177.102] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3109 invoked from network); 18 Jan 2013 11:09:52 -0000 Received: from smtp42.i.mail.ru (HELO smtp42.i.mail.ru) (94.100.177.102) by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jan 2013 11:09:52 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=MtbwvRAiXlANfr87RTTINZbqNDzcU/FzkjtnZjBUeUE=; b=BVokESSOZ10YAZhIVJJDz2cdTjnOoXDCwqUf3Nc4JoMkMh7nr7WsUms2V0N9riD6stJMfeLlmf0JZlj9mMcFqUzf7VT73MtMYRuunLBvfC3ZzEBEH0lTXlf7zyNOojTUICQeJKFOfTmHfBhAOIWf9Clnk7o9T0maAS7N2jmqmR4=; Received: from [78.36.60.25] (port=13681 helo=[10.168.2.113]) by smtp42.i.mail.ru with esmtpa (envelope-from ) id 1Tw9pX-0002RA-03 for xen-api@lists.xen.org; Fri, 18 Jan 2013 15:09:51 +0400 Message-ID: <50F92D7E.50908@bk.ru> Date: Fri, 18 Jan 2013 15:09:50 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" X-Spam: Not detected X-Mras: Ok Subject: [Xen-API] xcp-xapi antispoof and QoS support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I'm trying to setup QoS for the vifX.X with xcp-xapi installed on Debian Wheezy but it does not work. Also I don't see any antispoof XCP 1.6 related fields in vif-param-set output such as locking-mode and ipv4-allowed. Is there any support of these features in xcp-xapi(kronos)? If not I will have to discard of using it for out purposes, it's a great pity... Andrey _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 18 11:10:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 11:10:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw9pa-0001xl-Oy; Fri, 18 Jan 2013 11:09:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw9pZ-0001xg-CL for xen-api@lists.xen.org; Fri, 18 Jan 2013 11:09:53 +0000 Received: from [85.158.139.211:41538] by server-11.bemta-5.messagelabs.com id A7/35-07660-08D29F05; Fri, 18 Jan 2013 11:09:52 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-6.tower-206.messagelabs.com!1358507391!18682084!1 X-Originating-IP: [94.100.177.102] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3109 invoked from network); 18 Jan 2013 11:09:52 -0000 Received: from smtp42.i.mail.ru (HELO smtp42.i.mail.ru) (94.100.177.102) by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jan 2013 11:09:52 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=MtbwvRAiXlANfr87RTTINZbqNDzcU/FzkjtnZjBUeUE=; b=BVokESSOZ10YAZhIVJJDz2cdTjnOoXDCwqUf3Nc4JoMkMh7nr7WsUms2V0N9riD6stJMfeLlmf0JZlj9mMcFqUzf7VT73MtMYRuunLBvfC3ZzEBEH0lTXlf7zyNOojTUICQeJKFOfTmHfBhAOIWf9Clnk7o9T0maAS7N2jmqmR4=; Received: from [78.36.60.25] (port=13681 helo=[10.168.2.113]) by smtp42.i.mail.ru with esmtpa (envelope-from ) id 1Tw9pX-0002RA-03 for xen-api@lists.xen.org; Fri, 18 Jan 2013 15:09:51 +0400 Message-ID: <50F92D7E.50908@bk.ru> Date: Fri, 18 Jan 2013 15:09:50 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" X-Spam: Not detected X-Mras: Ok Subject: [Xen-API] xcp-xapi antispoof and QoS support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I'm trying to setup QoS for the vifX.X with xcp-xapi installed on Debian Wheezy but it does not work. Also I don't see any antispoof XCP 1.6 related fields in vif-param-set output such as locking-mode and ipv4-allowed. Is there any support of these features in xcp-xapi(kronos)? If not I will have to discard of using it for out purposes, it's a great pity... Andrey _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 18 12:00:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 12:00:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwAcR-0003qy-2Q; Fri, 18 Jan 2013 12:00:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwAcP-0003qM-ND for xen-api@lists.xen.org; Fri, 18 Jan 2013 12:00:21 +0000 Received: from [85.158.143.35:59945] by server-1.bemta-4.messagelabs.com id ED/64-18740-55939F05; Fri, 18 Jan 2013 12:00:21 +0000 X-Env-Sender: simon.beaumont@citrix.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1358510248!11628105!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3MjI0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13138 invoked from network); 18 Jan 2013 11:57:32 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2013 11:57:32 -0000 X-IronPort-AV: E=Sophos;i="4.84,491,1355097600"; d="scan'208";a="749529" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Jan 2013 11:57:28 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Fri, 18 Jan 2013 11:57:28 +0000 From: Simon Beaumont To: 'Andrey' Date: Fri, 18 Jan 2013 11:57:27 +0000 Thread-Topic: [Xen-API] xcp-xapi devscan.py kernel support Thread-Index: Ac31SdZUDOmN9QqWRoal77nUUB60hQAJGycQ Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E1417EA@LONPMAILBOX01.citrite.net> References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> <50F8F396.4060101@bk.ru> In-Reply-To: <50F8F396.4060101@bk.ru> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/mixed; boundary="_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_" MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 PiBBbHNvIG5vdGljZWQgdGhhdCAvZGV2L2Rpc2svYnktc2NzaWJ1cy8qIHBhdGggZG9lcyBub3Qg ZXhpc3QgYXMgc3VwcG9zZWQgaW4NCj4gY2FjaGVTQ1NJaWRlbnRpZmllcnMoKSBpbiB0aGUgc2Nz aXV0aWwucHkgc28gZGV2cyBwcm9wZXJ0eSBpcyBlbXB0eSB3aGlsZSBzci0NCj4gcHJvYmUgYW5k IG9ubHkgZ2VuZXJhbCBpbmZvcm1hdGlvbiByZXR1cm5zLiBEb2VzIGFueSBwYXRjaCBleGlzdCB0 b28/DQoNClRoYXQgZGlyZWN0b3J5IGlzIHBvcHVsYXRlZCBieSB1ZGV2IGJ5IDU1LXhzLW1wYXRo LXNjc2lkZXYucnVsZXMgdXNpbmcgdGhlIHhzLW1wYXRoLXNjc2lkZXYuc2ggc2NyaXB0LiBUaGlz IGhhcyBhbHNvIGJlZW4gcGF0Y2hlZCB0byB3b3JrIHdpdGggdGhlIGRpZmZlcmVudCBrZXJuZWwg c3lzZnMgZW50cmllcyBidXQgdGhlIHNjcmlwdCBsaXZlcyBpbiBhIGRpZmZlcmVudCByZXBvIHNv IGl0IGVzY2FwZWQgbXkgYXR0ZW50aW9uLiBIZXJlJ3MgdGhlIHBhdGNoIGJ1dCB0aGUgc3lzZnMg Yml0IGlzIHJlbGF0ZWQgdG8gaVNDU0kgYW5kIHRoZXJlIGRvZXNuJ3Qgc2VlbSB0byBiZSBzeXNm cyByZWxhdGVkIHdvcmsgZG9uZSBmb3IgdGhlIGRpcmVjdG9yeSB5b3UgbWVudGlvbi4NCg0KVHJ5 IHRoZSBmb2xsb3dpbmcgdHdvIHBhdGNoZXMgYW55d2F5LiBPbmUgZm9yIHRoZSB1ZGV2IHJ1bGVz IGFuZCBvbmUgZm9yIHRoZSBpU0NTSSByZWxhdGVkIGZ1bmN0aW9uYWxpdHkgaW4gdGhlIFNNLg0K DQpIb3BlIHRoZXNlIGhlbHAsIG9yIGF0IGxlYXN0IHBvaW50IHlvdSBpbiB0aGUgcmlnaHQgZGly ZWN0aW9uLg0KDQotU2kNCg0KPjE3LjAxLjIwMTMgMTg6MTksIFNpbW9uIEJlYXVtb250INC/0LjR iNC10YI6DQo+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+PiBGcm9tOiB4ZW4tYXBp LWJvdW5jZXNAbGlzdHMueGVuLm9yZw0KPj4+IFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3Rz Lnhlbi5vcmddIE9uIEJlaGFsZiBPZiBBbmRyZXkNCj4+PiBTZW50OiAxNyBKYW51YXJ5IDIwMTMg MTI6NTYgUE0NCj4+PiBUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnDQo+Pj4gU3ViamVjdDogW1hl bi1BUEldIHhjcC14YXBpIGRldnNjYW4ucHkga2VybmVsIHN1cHBvcnQNCj4+Pg0KPj4+IEkgaW5z dGFsbGVkIHhjcC14YXBpIG9uIHRoZSBEZWJpYW4gV2hlZXp5IGFuZCBjYW4ndCBnZXQgTFZNb0hC QSB0byB3b3JrOg0KPj4+DQo+Pj4gc3RkZXJyOiBUcmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwg bGFzdCk6DQo+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9MVk1vSEJBU1IiLCBsaW5lIDIy MCwgaW4gPG1vZHVsZT4NCj4+PiAgICAgICBTUkNvbW1hbmQucnVuKExWSERvSEJBU1IsIERSSVZF Ul9JTkZPKQ0KPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vU1JDb21tYW5kLnB5IiwgbGlu ZSAyNjEsIGluIHJ1bg0KPj4+ICAgICAgIHNyID0gZHJpdmVyKGNtZCwgY21kLnNyX3V1aWQpDQo+ Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9TUi5weSIsIGxpbmUgMTM2LCBpbiBfX2luaXRf Xw0KPj4+ICAgICAgIHNlbGYubG9hZChzcl91dWlkKQ0KPj4+ICAgICBGaWxlICIvdXNyL2xpYi94 Y3Avc20vTFZNb0hCQVNSIiwgbGluZSA5NCwgaW4gbG9hZA0KPj4+ICAgICAgIHByaW50ID4+c3lz LnN0ZGVycixzZWxmLmhiYXNyLnByaW50X2RldnMoKQ0KPj4+ICAgICBGaWxlICIvdXNyL2xpYi94 Y3Avc20vSEJBU1IucHkiLCBsaW5lIDIyNCwgaW4gcHJpbnRfZGV2cw0KPj4+ICAgICAgIHNlbGYu X2luaXRfaGJhZGljdCgpDQo+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9IQkFTUi5weSIs IGxpbmUgNjEsIGluIF9pbml0X2hiYWRpY3QNCj4+PiAgICAgICBkaWN0ID0gZGV2c2Nhbi5hZGFw dGVycyhmaWx0ZXJzdHI9c2VsZi50eXBlKQ0KPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20v ZGV2c2Nhbi5weSIsIGxpbmUgMTY4LCBpbiBhZGFwdGVycw0KPj4+DQo+Pj4gZ2xvYi5nbG9iKG9z LnBhdGguam9pbihwYXRoLCJkZXZpY2UiLCJibG9jazoqIikpWzBdKS5zcGxpdCgnOicpWzFdDQo+ Pj4gSW5kZXhFcnJvcjogbGlzdCBpbmRleCBvdXQgb2YgcmFuZ2UNCj4+Pg0KPj4+DQo+Pj4gQ2Fu IHlvdSBwbGVhc2Ugc2VuZCBkZXZzY2FuLnB5IHBhdGNoIHRvIHN1cHBvcnQgbHZtb2hiYSBpbiBr ZXJuZWwgMy5YLg0KPj4NCj4+IEkgaGF2ZSBhdHRhY2hlZCB0aGUgcGF0Y2ggaW4gcXVlc3Rpb24u IEl0IHVzZXMgdGhlIHJpZ2h0IHN5c2ZzIHBhdGhzIGFmdGVyDQo+ZGV0ZWN0aW5nIHRoZSBrZXJu ZWwgdmVyc2lvbi4gSXQgbWlnaHQgbm90IGFwcGx5IHRvIHlvdXIgdmVyc2lvbiBidXQgaXQgbWF5 DQo+aGVscCB5b3UgbWFrZSB0aGUgY2hhbmdlIHlvdSByZXF1aXJlLg0KPj4NCj4+PiBBbHNvIHdp bGwgaW4gdGhpcyBjYXNlIG90aGVyIGx2bW9oYmEgZmVhdHVyZXMgd2lsbCB3b3JrIHNtb290aGx5 IGluDQo+Pj4gdGhhdCBjYXNlIG9uIERlYmlhbiwgZXNwZWNpYWxseSBtdWx0aXBhdGg/DQo+Pg0K Pj4gSXQncyB1bmxpa2VseSB5b3UnbGwgZ2V0IExWTSB0byB3b3JrIHdpdGggeW91ciBzZXR1cCBz aW5jZSB3ZSB1c2UgYSBwYXRjaGVkDQo+dmVyc2lvbiB0aGF0IGFjY2VwdHMgYW5vdGhlciBvcHRp b24gKC0tbWFzdGVyKSB3aGljaCBhZmZvcmRzIHVzIGEgZGlmZmVyZW50DQo+bG9ja2luZyBtZWNo YW5pc20gdG8gYWxsb3cgc2hhcmVkIFNScy4gVGhpcyBvcHRpb24gZG9lc24ndCBleGlzdCBpbiB0 aGUNCj51cHN0cmVhbSBEZWJpYW4gTFZNLg0KPj4NCj4+IEl0IG1heSghKSBiZSBwb3NzaWJsZSB0 byBnZXQgaXQgdG8gd29yayBpZiB5b3UgcmVtb3ZlIHRoZSAtLW1hc3RlciBvcHRpb24NCj5mcm9t IHRoZSBjYWxscyB0byBsdm0gaW4gdGhlIHNvdXJjZSBhbmQgZW5zdXJlIHRoYXQgeW91IGFyZSBv bmx5IHVzaW5nIHRoZXNlDQo+U1JzIGluIHNpbmdsZS1ob3N0IHBvb2xzLiBBZ2FpbiwgeW91ciBt aWxlYWdlIG1heSB2YXJ5Lg0KPj4NCj4+IEhvcGUgdGhpcyBoZWxwcywNCj4+DQo+PiAtU2kNCj4+ DQo= --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_ Content-Type: application/octet-stream; name="3.x-kernel-udev-script.patch" Content-Description: 3.x-kernel-udev-script.patch Content-Disposition: attachment; filename="3.x-kernel-udev-script.patch"; size=2330; creation-date="Fri, 18 Jan 2013 11:56:36 GMT"; modification-date="Fri, 18 Jan 2013 11:36:48 GMT" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL2JpbmFyeS1vdmVybGF5L2V0Yy91ZGV2L3NjcmlwdHMveHMtbXBhdGgtc2Nz aWRldi5zaCBiL2JpbmFyeS1vdmVybGF5L2V0Yy91ZGV2L3NjcmlwdHMveHMtbXBhdGgtc2NzaWRl di5zaAotLS0gYS9iaW5hcnktb3ZlcmxheS9ldGMvdWRldi9zY3JpcHRzL3hzLW1wYXRoLXNjc2lk ZXYuc2gKKysrIGIvYmluYXJ5LW92ZXJsYXkvZXRjL3VkZXYvc2NyaXB0cy94cy1tcGF0aC1zY3Np ZGV2LnNoCkBAIC03LDYgKzcsMjMgQEAKIE9VVD0kezR9CiBMVU49YGVjaG8gJEJVUyB8IGN1dCAt ZDogLWY0YAogCisjIFRoZSByZXF1aXJlZCBmaWxlcyBhcmUgbG9jYXRlZCBpbiBhbiBleHRyYSBs YXllciBvZiBkaXJlY3RvcmllcyBpbiAzLngga2VybmVscwora2VybmVsPWB1bmFtZSAtciB8IGN1 dCAtZC4gLWYxLTJgCitjYXNlICRrZXJuZWwgaW4KKyAgICAyLjYpCisgICAgICAgIHRhcmdldElR TlBhdGg9Ii9kZXZpY2Uvc2Vzc2lvbiovaXNjc2lfc2Vzc2lvbioiCisgICAgICAgIHRhcmdldElQ UG9ydFBhdGg9Ii9kZXZpY2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVjdGlvbioi CisgICAgICAgIDs7CisgICAgMy4qKQorICAgICAgICB0YXJnZXRJUU5QYXRoPSIvZGV2aWNlL3Nl c3Npb24qL2lzY3NpX3Nlc3Npb24vc2Vzc2lvbioiCisgICAgICAgIHRhcmdldElQUG9ydFBhdGg9 Ii9kZXZpY2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVjdGlvbi9jb25uZWN0aW9u KiIKKyAgICAgICAgOzsKKyAgICAqKQorICAgICAgICBlY2hvICJVbmtvd24ga2VybmVsOiBuZWl0 aGVyIDIuNiBub3IgMy54LiBFeGl0aW5nLi4uIgorICAgICAgICBleGl0IDIKKyAgICAgICAgOzsK K2VzYWMKKwogI0FyZ3M6IElECiBxdWVyeV9ob3N0cygpIHsKICAgICAvdXNyL3NiaW4vbXBwVXRp bCAtZyAkMSB8IGdyZXAgaG9zdElkIHwgd2hpbGUgcmVhZCBmaWxlCkBAIC0xNiwxMCArMzMsMTEg QEAKICAgICAgIFsgLWUgJHtJU0NTSVBBVEh9IF0gfHwgY29udGludWUKIAogICAgICAgI1F1ZXJ5 IHRoZSBJUU4sIElQIGFuZCBQb3J0IHZhbHVlcwotICAgICAgdGFyZ2V0SVFOZmlsZT0iJHtJU0NT SVBBVEh9L2RldmljZS9zZXNzaW9uKi9pc2NzaV9zZXNzaW9uKi90YXJnZXRuYW1lIgorICAgICAg dGFyZ2V0SVFOZmlsZT0iJHtJU0NTSVBBVEh9JHt0YXJnZXRJUU5QYXRofS90YXJnZXRuYW1lIgog ICAgICAgdGFyZ2V0SVFOPSQoY2F0ICR7dGFyZ2V0SVFOZmlsZX0pCi0gICAgICB0YXJnZXRJUGZp bGU9IiR7SVNDU0lQQVRIfS9kZXZpY2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVj dGlvbiovcGVyc2lzdGVudF9hZGRyZXNzIgotICAgICAgdGFyZ2V0UG9ydGZpbGU9IiR7SVNDU0lQ QVRIfS9kZXZpY2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVjdGlvbiovcGVyc2lz dGVudF9wb3J0IgorCisgICAgICB0YXJnZXRJUGZpbGU9IiR7SVNDU0lQQVRIfSR7dGFyZ2V0SVBQ b3J0UGF0aH0vcGVyc2lzdGVudF9hZGRyZXNzIgorICAgICAgdGFyZ2V0UG9ydGZpbGU9IiR7SVND U0lQQVRIfSR7dGFyZ2V0SVBQb3J0UGF0aH0vcGVyc2lzdGVudF9wb3J0IgogICAgICAgdGFyZ2V0 SVA9JChjYXQgJHt0YXJnZXRJUGZpbGV9KQogICAgICAgdGFyZ2V0UG9ydD0kKGNhdCAke3Rhcmdl dFBvcnRmaWxlfSkKIApAQCAtNjksMTIgKzg3LDEyIEBACiBbIC1lICR7SVNDU0lQQVRIfSBdIHx8 IGV4aXQgMQogCiAjIFF1ZXJ5IHRhcmdldElRTgotdGFyZ2V0SVFOZmlsZT0iJHtJU0NTSVBBVEh9 L2RldmljZS9zZXNzaW9uKi9pc2NzaV9zZXNzaW9uKi90YXJnZXRuYW1lIgordGFyZ2V0SVFOZmls ZT0iJHtJU0NTSVBBVEh9JHt0YXJnZXRJUU5QYXRofS90YXJnZXRuYW1lIgogdGFyZ2V0SVFOPSQo Y2F0ICR7dGFyZ2V0SVFOZmlsZX0pCiAKICMgUXVlcnkgdGFyZ2V0IGFkZHJlc3MgYW5kIHBvcnQK LXRhcmdldElQZmlsZT0iJHtJU0NTSVBBVEh9L2RldmljZS9zZXNzaW9uKi9jb25uZWN0aW9uKi9p c2NzaV9jb25uZWN0aW9uKi9wZXJzaXN0ZW50X2FkZHJlc3MiCi10YXJnZXRQb3J0ZmlsZT0iJHtJ U0NTSVBBVEh9L2RldmljZS9zZXNzaW9uKi9jb25uZWN0aW9uKi9pc2NzaV9jb25uZWN0aW9uKi9w ZXJzaXN0ZW50X3BvcnQiCit0YXJnZXRJUGZpbGU9IiR7SVNDU0lQQVRIfSR7dGFyZ2V0SVBQb3J0 UGF0aH0vcGVyc2lzdGVudF9hZGRyZXNzIgordGFyZ2V0UG9ydGZpbGU9IiR7SVNDU0lQQVRIfSR7 dGFyZ2V0SVBQb3J0UGF0aH0vcGVyc2lzdGVudF9wb3J0IgogdGFyZ2V0SVA9JChjYXQgJHt0YXJn ZXRJUGZpbGV9KQogdGFyZ2V0UG9ydD0kKGNhdCAke3RhcmdldFBvcnRmaWxlfSkKIAo= --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_ Content-Type: application/octet-stream; name="3.x-kernel-iscsi-sysfs.patch" Content-Description: 3.x-kernel-iscsi-sysfs.patch Content-Disposition: attachment; filename="3.x-kernel-iscsi-sysfs.patch"; size=5272; creation-date="Fri, 18 Jan 2013 11:57:02 GMT"; modification-date="Fri, 18 Jan 2013 11:56:52 GMT" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL1hlbkNlcnQvU3RvcmFnZUhhbmRsZXJVdGlsLnB5IGIvWGVuQ2VydC9TdG9y YWdlSGFuZGxlclV0aWwucHkKLS0tIGEvWGVuQ2VydC9TdG9yYWdlSGFuZGxlclV0aWwucHkKKysr IGIvWGVuQ2VydC9TdG9yYWdlSGFuZGxlclV0aWwucHkKQEAgLTExOSwxMiArMTE5LDggQEAKICAg ICBhZGFwdGVyID0ge30KICAgICBmb3IgaG9zdCBpbiBpZHM6CiAgICAgICAgIHRyeToKLSAgICAg ICAgICAgIHRhcmdldElRTiA9IHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShnbG9iLmdsb2IoXAotICAg ICAgICAgICAgICAgICcvc3lzL2NsYXNzL2lzY3NpX2hvc3QvaG9zdCVzL2RldmljZS9zZXNzaW9u Ki9pc2NzaV9zZXNzaW9uKi90YXJnZXRuYW1lJyAlIGhvc3QpWzBdKQotICAgICAgICAgICAgYWRk ciA9IHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShnbG9iLmdsb2IoXAotICAgICAgICAgICAgICAgICcv c3lzL2NsYXNzL2lzY3NpX2hvc3QvaG9zdCVzL2RldmljZS9zZXNzaW9uKi9jb25uZWN0aW9uKi9p c2NzaV9jb25uZWN0aW9uKi9wZXJzaXN0ZW50X2FkZHJlc3MnICUgaG9zdClbMF0pCi0gICAgICAg ICAgICBwb3J0ID0gdXRpbC5nZXRfc2luZ2xlX2VudHJ5KGdsb2IuZ2xvYihcCi0gICAgICAgICAg ICAgICAgJy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlL3Nlc3Npb24qL2Nvbm5l Y3Rpb24qL2lzY3NpX2Nvbm5lY3Rpb24qL3BlcnNpc3RlbnRfcG9ydCcgJSBob3N0KVswXSkKKyAg ICAgICAgICAgIHRhcmdldElRTiA9IGlzY3NpbGliLmdldF90YXJnZXRJUU4oaG9zdCkKKyAgICAg ICAgICAgIChhZGRyLCBwb3J0KSA9IGlzY3NpbGliLmdldF90YXJnZXRJUF9hbmRfcG9ydChob3N0 KQogICAgICAgICAgICAgZW50cnkgPSAiJXM6JXMiICUgKGFkZHIscG9ydCkKICAgICAgICAgICAg IGFkYXB0ZXJbZW50cnldID0gaG9zdAogICAgICAgICBleGNlcHQgRXhjZXB0aW9uLCBlOgpkaWZm IC0tZ2l0IGEvZHJpdmVycy9JU0NTSVNSLnB5IGIvZHJpdmVycy9JU0NTSVNSLnB5Ci0tLSBhL2Ry aXZlcnMvSVNDU0lTUi5weQorKysgYi9kcml2ZXJzL0lTQ1NJU1IucHkKQEAgLTIzMiwxNCArMjMy LDEwIEBACiAgICAgICAgIHNlbGYuYWRhcHRlciA9IHt9CiAgICAgICAgIGZvciBob3N0IGluIGlk czoKICAgICAgICAgICAgIHRyeToKLSAgICAgICAgICAgICAgICB0YXJnZXRJUU4gPSB1dGlsLmdl dF9zaW5nbGVfZW50cnkoZ2xvYi5nbG9iKFwKLSAgICAgICAgICAgICAgICAgICAgJy9zeXMvY2xh c3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlL3Nlc3Npb24qL2lzY3NpX3Nlc3Npb24qL3Rhcmdl dG5hbWUnICUgaG9zdClbMF0pCisgICAgICAgICAgICAgICAgdGFyZ2V0SVFOID0gaXNjc2lsaWIu Z2V0X3RhcmdldElRTihob3N0KQogICAgICAgICAgICAgICAgIGlmIHRhcmdldElRTiAhPSBzZWxm LnRhcmdldElRTjoKICAgICAgICAgICAgICAgICAgICAgY29udGludWUKLSAgICAgICAgICAgICAg ICBhZGRyID0gdXRpbC5nZXRfc2luZ2xlX2VudHJ5KGdsb2IuZ2xvYihcCi0gICAgICAgICAgICAg ICAgICAgICcvc3lzL2NsYXNzL2lzY3NpX2hvc3QvaG9zdCVzL2RldmljZS9zZXNzaW9uKi9jb25u ZWN0aW9uKi9pc2NzaV9jb25uZWN0aW9uKi9wZXJzaXN0ZW50X2FkZHJlc3MnICUgaG9zdClbMF0p Ci0gICAgICAgICAgICAgICAgcG9ydCA9IHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShnbG9iLmdsb2Io XAotICAgICAgICAgICAgICAgICAgICAnL3N5cy9jbGFzcy9pc2NzaV9ob3N0L2hvc3Qlcy9kZXZp Y2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVjdGlvbiovcGVyc2lzdGVudF9wb3J0 JyAlIGhvc3QpWzBdKQorICAgICAgICAgICAgICAgIChhZGRyLCBwb3J0KSA9IGlzY3NpbGliLmdl dF90YXJnZXRJUF9hbmRfcG9ydChob3N0KQogICAgICAgICAgICAgICAgIGVudHJ5ID0gIiVzOiVz IiAlIChhZGRyLHBvcnQpCiAgICAgICAgICAgICAgICAgc2VsZi5hZGFwdGVyW2VudHJ5XSA9IGhv c3QKICAgICAgICAgICAgIGV4Y2VwdDoKQEAgLTMyOCwxMSArMzI0LDEwIEBACiAgICAgICAgIGVs c2U6CiAgICAgICAgICAgICBJUU5zLmFwcGVuZChzZWxmLnRhcmdldElRTikKICAgICAgICAgc2Vz c2lvbnMgPSAwCi0gICAgICAgIHBhdGhzID0gZ2xvYi5nbG9iKFwKLSAgICAgICAgICAgICAgICAg ICAgJy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0Ki9kZXZpY2Uvc2Vzc2lvbiovaXNjc2lfc2Vz c2lvbiovdGFyZ2V0bmFtZScpCisgICAgICAgIHBhdGhzID0gaXNjc2lsaWIuZ2V0X0lRTl9wYXRo cygpCiAgICAgICAgIGZvciBwYXRoIGluIHBhdGhzOgogICAgICAgICAgICAgdHJ5OgotICAgICAg ICAgICAgICAgIGlmIHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShwYXRoKSBpbiBJUU5zOgorICAgICAg ICAgICAgICAgIGlmIHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShvcy5wYXRoLmpvaW4ocGF0aCwgJ3Rh cmdldG5hbWUnKSkgaW4gSVFOczoKICAgICAgICAgICAgICAgICAgICAgc2Vzc2lvbnMgKz0gMQog ICAgICAgICAgICAgICAgICAgICB1dGlsLlNNbG9nKCJJUU4gbWF0Y2guIEluY3JlbWVudGluZyBz ZXNzaW9ucyB0byAlZCIgJSBzZXNzaW9ucykKICAgICAgICAgICAgIGV4Y2VwdDoKZGlmZiAtLWdp dCBhL2RyaXZlcnMvWEVfU1JfRVJST1JDT0RFUy54bWwgYi9kcml2ZXJzL1hFX1NSX0VSUk9SQ09E RVMueG1sCi0tLSBhL2RyaXZlcnMvWEVfU1JfRVJST1JDT0RFUy54bWwKKysrIGIvZHJpdmVycy9Y RV9TUl9FUlJPUkNPREVTLnhtbApAQCAtODk3LDQgKzg5Nyw5IEBACiAJCQk8dmFsdWU+NDQ3PC92 YWx1ZT4NCiAJCTwvY29kZT4NCiANCisgICAgICAgIDxjb2RlPg0KKyAgICAgICAgICAgIDxuYW1l PlVuc3VwcG9ydGVkS2VybmVsPC9uYW1lPg0KKyAgICAgICAgICAgIDxkZXNjcmlwdGlvbj5VbnN1 cHBvcnRlZCBrZXJuZWw6IG5laXRoZXIgMi42IG5vciAzLnguPC9kZXNjcmlwdGlvbj4NCisgICAg ICAgICAgICA8dmFsdWU+NDQ4PC92YWx1ZT4NCisgICAgICAgIDwvY29kZT4NCiA8L1NNLWVycm9y Y29kZXM+DQpkaWZmIC0tZ2l0IGEvZHJpdmVycy9pc2NzaWxpYi5weSBiL2RyaXZlcnMvaXNjc2ls aWIucHkKLS0tIGEvZHJpdmVycy9pc2NzaWxpYi5weQorKysgYi9kcml2ZXJzL2lzY3NpbGliLnB5 CkBAIC0xOCw4ICsxOCwyNSBAQAogaW1wb3J0IHNodXRpbAogaW1wb3J0IHhzX2Vycm9ycwogaW1w b3J0IGxvY2sKK2ltcG9ydCBnbG9iCiBmcm9tIGNsZWFudXAgaW1wb3J0IExPQ0tfVFlQRV9SVU5O SU5HCiAKKyMgVGhlIDMueCBrZXJuZWwgYnJpbmdzIHdpdGggaXQgc29tZSBpU0NTSSBwYXRoIGNo YW5nZXMgaW4gc3lzZnMKK19LRVJORUxfVkVSU0lPTiA9IG9zLnVuYW1lKClbMl0KK2lmIF9LRVJO RUxfVkVSU0lPTi5zdGFydHN3aXRoKCcyLjYnKToKKyAgICBfR0VORVJJQ19TRVNTSU9OX1BBVEgg PSAoJy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlL3Nlc3Npb24qLycgKworICAg ICAgICAgICAgJ2lzY3NpX3Nlc3Npb24qLycpCisgICAgX0dFTkVSSUNfQ09OTkVDVElPTl9QQVRI ID0gKCcvc3lzL2NsYXNzL2lzY3NpX2hvc3QvaG9zdCVzL2RldmljZS8nICsKKyAgICAgICAgICAg ICdzZXNzaW9uKi9jb25uZWN0aW9uKi9pc2NzaV9jb25uZWN0aW9uKi8nKQorZWxpZiBfS0VSTkVM X1ZFUlNJT04uc3RhcnRzd2l0aCgnMy4nKToKKyAgICBfR0VORVJJQ19TRVNTSU9OX1BBVEggPSAo Jy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlL3Nlc3Npb24qLycgKworICAgICAg ICAgICAgJ2lzY3NpX3Nlc3Npb24vc2Vzc2lvbiovJykKKyAgICBfR0VORVJJQ19DT05ORUNUSU9O X1BBVEggPSAoJy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlLycgKworICAgICAg ICAgICAgJ3Nlc3Npb24qL2Nvbm5lY3Rpb24qL2lzY3NpX2Nvbm5lY3Rpb24vY29ubmVjdGlvbiov JykKK2Vsc2U6CisgICAgX21zZyA9ICdLZXJuZWwgdmVyc2lvbiBkZXRlY3RlZDogJXMnICUgX0tF Uk5FTF9WRVJTSU9OCisgICAgcmFpc2UgeHNfZXJyb3JzLlhlbkVycm9yKCdVbnN1cHBvcnRlZEtl cm5lbCcsIF9tc2cpCisKIGRlZiBleG5fb25fZmFpbHVyZShjbWQsIG1lc3NhZ2UpOgogICAgICcn J0V4ZWN1dGVzIHZpYSB1dGlsLmRvZXhlYyB0aGUgY29tbWFuZCBzcGVjaWZpZWQuIElmIHRoZSBy ZXR1cm4gY29kZSBpcyAKICAgICBub24temVybywgcmFpc2VzIGFuIElTQ1NJRXJyb3Igd2l0aCB0 aGUgZ2l2ZW4gbWVzc2FnZScnJwpAQCAtMjU1LDYgKzI3MiwyNSBAQAogICAgIGV4Y2VwdDoKICAg ICAgICAgcGFzcwogCitkZWYgZ2V0X0lRTl9wYXRocygpOgorICAgICIiIlJldHVybiB0aGUgbGlz dCBvZiBpU0NTSSBzZXNzaW9uIGRpcmVjdG9yaWVzIiIiCisgICAgcmV0dXJuIGdsb2IuZ2xvYihf R0VORVJJQ19TRVNTSU9OX1BBVEggJSAnKicpCisKK2RlZiBnZXRfdGFyZ2V0SVFOKGlzY3NpX2hv c3QpOgorICAgICIiIkdldCB0YXJnZXQgSVFOIGZyb20gc3lzZnMgZm9yIGdpdmVuIGlTQ1NJIGhv c3QgbnVtYmVyIiIiCisgICAgaXFuX2ZpbGUgPSBvcy5wYXRoLmpvaW4oX0dFTkVSSUNfU0VTU0lP Tl9QQVRIICUgaXNjc2lfaG9zdCwgJ3RhcmdldG5hbWUnKQorICAgIHRhcmdldElRTiA9IHV0aWwu Z2V0X3NpbmdsZV9lbnRyeShnbG9iLmdsb2IoaXFuX2ZpbGUpWzBdKQorICAgIHJldHVybiB0YXJn ZXRJUU4KKworZGVmIGdldF90YXJnZXRJUF9hbmRfcG9ydChpc2NzaV9ob3N0KToKKyAgICAiIiJH ZXQgdGFyZ2V0IElQIGFkZHJlc3MgYW5kIHBvcnQgZm9yIGdpdmVuIGlTQ1NJIGhvc3QgbnVtYmVy IiIiCisgICAgY29ubmVjdGlvbl9kaXIgPSBfR0VORVJJQ19DT05ORUNUSU9OX1BBVEggJSBpc2Nz aV9ob3N0CisgICAgaXAgPSB1dGlsLmdldF9zaW5nbGVfZW50cnkoZ2xvYi5nbG9iKG9zLnBhdGgu am9pbigKKyAgICAgICAgICAgIGNvbm5lY3Rpb25fZGlyLCAncGVyc2lzdGVudF9hZGRyZXNzJykp WzBdKQorICAgIHBvcnQgPSB1dGlsLmdldF9zaW5nbGVfZW50cnkoZ2xvYi5nbG9iKG9zLnBhdGgu am9pbigKKyAgICAgICAgICAgIGNvbm5lY3Rpb25fZGlyLCAncGVyc2lzdGVudF9wb3J0JykpWzBd KQorICAgIHJldHVybiAoaXAsIHBvcnQpCisKIGRlZiBnZXRfcGF0aCh0YXJnZXRJUU4sIHBvcnRh bCwgbHVuKToKICAgICAiIiJHZXRzIHRoZSBwYXRoIG9mIGEgc3BlY2lmaWVkIExVTiAtIHRoaXMg c2hvdWxkIGJlIGUuZy4gJzEnIG9yICc1JyIiIgogICAgIHBhdGggPSBvcy5wYXRoLmpvaW4oIi9k ZXYvaXNjc2kiLHRhcmdldElRTixwb3J0YWwpCg== --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_-- From xen-api-bounces@lists.xen.org Fri Jan 18 12:00:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 12:00:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwAcR-0003qy-2Q; Fri, 18 Jan 2013 12:00:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwAcP-0003qM-ND for xen-api@lists.xen.org; Fri, 18 Jan 2013 12:00:21 +0000 Received: from [85.158.143.35:59945] by server-1.bemta-4.messagelabs.com id ED/64-18740-55939F05; Fri, 18 Jan 2013 12:00:21 +0000 X-Env-Sender: simon.beaumont@citrix.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1358510248!11628105!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3MjI0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13138 invoked from network); 18 Jan 2013 11:57:32 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2013 11:57:32 -0000 X-IronPort-AV: E=Sophos;i="4.84,491,1355097600"; d="scan'208";a="749529" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Jan 2013 11:57:28 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Fri, 18 Jan 2013 11:57:28 +0000 From: Simon Beaumont To: 'Andrey' Date: Fri, 18 Jan 2013 11:57:27 +0000 Thread-Topic: [Xen-API] xcp-xapi devscan.py kernel support Thread-Index: Ac31SdZUDOmN9QqWRoal77nUUB60hQAJGycQ Message-ID: <344C0F67BC927847A2C92F9EE358DB0E01224E1417EA@LONPMAILBOX01.citrite.net> References: <50F7F4C8.2090408@bk.ru> <344C0F67BC927847A2C92F9EE358DB0E01224E1417E9@LONPMAILBOX01.citrite.net> <50F8F396.4060101@bk.ru> In-Reply-To: <50F8F396.4060101@bk.ru> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/mixed; boundary="_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_" MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xcp-xapi devscan.py kernel support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 PiBBbHNvIG5vdGljZWQgdGhhdCAvZGV2L2Rpc2svYnktc2NzaWJ1cy8qIHBhdGggZG9lcyBub3Qg ZXhpc3QgYXMgc3VwcG9zZWQgaW4NCj4gY2FjaGVTQ1NJaWRlbnRpZmllcnMoKSBpbiB0aGUgc2Nz aXV0aWwucHkgc28gZGV2cyBwcm9wZXJ0eSBpcyBlbXB0eSB3aGlsZSBzci0NCj4gcHJvYmUgYW5k IG9ubHkgZ2VuZXJhbCBpbmZvcm1hdGlvbiByZXR1cm5zLiBEb2VzIGFueSBwYXRjaCBleGlzdCB0 b28/DQoNClRoYXQgZGlyZWN0b3J5IGlzIHBvcHVsYXRlZCBieSB1ZGV2IGJ5IDU1LXhzLW1wYXRo LXNjc2lkZXYucnVsZXMgdXNpbmcgdGhlIHhzLW1wYXRoLXNjc2lkZXYuc2ggc2NyaXB0LiBUaGlz IGhhcyBhbHNvIGJlZW4gcGF0Y2hlZCB0byB3b3JrIHdpdGggdGhlIGRpZmZlcmVudCBrZXJuZWwg c3lzZnMgZW50cmllcyBidXQgdGhlIHNjcmlwdCBsaXZlcyBpbiBhIGRpZmZlcmVudCByZXBvIHNv IGl0IGVzY2FwZWQgbXkgYXR0ZW50aW9uLiBIZXJlJ3MgdGhlIHBhdGNoIGJ1dCB0aGUgc3lzZnMg Yml0IGlzIHJlbGF0ZWQgdG8gaVNDU0kgYW5kIHRoZXJlIGRvZXNuJ3Qgc2VlbSB0byBiZSBzeXNm cyByZWxhdGVkIHdvcmsgZG9uZSBmb3IgdGhlIGRpcmVjdG9yeSB5b3UgbWVudGlvbi4NCg0KVHJ5 IHRoZSBmb2xsb3dpbmcgdHdvIHBhdGNoZXMgYW55d2F5LiBPbmUgZm9yIHRoZSB1ZGV2IHJ1bGVz IGFuZCBvbmUgZm9yIHRoZSBpU0NTSSByZWxhdGVkIGZ1bmN0aW9uYWxpdHkgaW4gdGhlIFNNLg0K DQpIb3BlIHRoZXNlIGhlbHAsIG9yIGF0IGxlYXN0IHBvaW50IHlvdSBpbiB0aGUgcmlnaHQgZGly ZWN0aW9uLg0KDQotU2kNCg0KPjE3LjAxLjIwMTMgMTg6MTksIFNpbW9uIEJlYXVtb250INC/0LjR iNC10YI6DQo+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+PiBGcm9tOiB4ZW4tYXBp LWJvdW5jZXNAbGlzdHMueGVuLm9yZw0KPj4+IFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3Rz Lnhlbi5vcmddIE9uIEJlaGFsZiBPZiBBbmRyZXkNCj4+PiBTZW50OiAxNyBKYW51YXJ5IDIwMTMg MTI6NTYgUE0NCj4+PiBUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnDQo+Pj4gU3ViamVjdDogW1hl bi1BUEldIHhjcC14YXBpIGRldnNjYW4ucHkga2VybmVsIHN1cHBvcnQNCj4+Pg0KPj4+IEkgaW5z dGFsbGVkIHhjcC14YXBpIG9uIHRoZSBEZWJpYW4gV2hlZXp5IGFuZCBjYW4ndCBnZXQgTFZNb0hC QSB0byB3b3JrOg0KPj4+DQo+Pj4gc3RkZXJyOiBUcmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwg bGFzdCk6DQo+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9MVk1vSEJBU1IiLCBsaW5lIDIy MCwgaW4gPG1vZHVsZT4NCj4+PiAgICAgICBTUkNvbW1hbmQucnVuKExWSERvSEJBU1IsIERSSVZF Ul9JTkZPKQ0KPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20vU1JDb21tYW5kLnB5IiwgbGlu ZSAyNjEsIGluIHJ1bg0KPj4+ICAgICAgIHNyID0gZHJpdmVyKGNtZCwgY21kLnNyX3V1aWQpDQo+ Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9TUi5weSIsIGxpbmUgMTM2LCBpbiBfX2luaXRf Xw0KPj4+ICAgICAgIHNlbGYubG9hZChzcl91dWlkKQ0KPj4+ICAgICBGaWxlICIvdXNyL2xpYi94 Y3Avc20vTFZNb0hCQVNSIiwgbGluZSA5NCwgaW4gbG9hZA0KPj4+ICAgICAgIHByaW50ID4+c3lz LnN0ZGVycixzZWxmLmhiYXNyLnByaW50X2RldnMoKQ0KPj4+ICAgICBGaWxlICIvdXNyL2xpYi94 Y3Avc20vSEJBU1IucHkiLCBsaW5lIDIyNCwgaW4gcHJpbnRfZGV2cw0KPj4+ICAgICAgIHNlbGYu X2luaXRfaGJhZGljdCgpDQo+Pj4gICAgIEZpbGUgIi91c3IvbGliL3hjcC9zbS9IQkFTUi5weSIs IGxpbmUgNjEsIGluIF9pbml0X2hiYWRpY3QNCj4+PiAgICAgICBkaWN0ID0gZGV2c2Nhbi5hZGFw dGVycyhmaWx0ZXJzdHI9c2VsZi50eXBlKQ0KPj4+ICAgICBGaWxlICIvdXNyL2xpYi94Y3Avc20v ZGV2c2Nhbi5weSIsIGxpbmUgMTY4LCBpbiBhZGFwdGVycw0KPj4+DQo+Pj4gZ2xvYi5nbG9iKG9z LnBhdGguam9pbihwYXRoLCJkZXZpY2UiLCJibG9jazoqIikpWzBdKS5zcGxpdCgnOicpWzFdDQo+ Pj4gSW5kZXhFcnJvcjogbGlzdCBpbmRleCBvdXQgb2YgcmFuZ2UNCj4+Pg0KPj4+DQo+Pj4gQ2Fu IHlvdSBwbGVhc2Ugc2VuZCBkZXZzY2FuLnB5IHBhdGNoIHRvIHN1cHBvcnQgbHZtb2hiYSBpbiBr ZXJuZWwgMy5YLg0KPj4NCj4+IEkgaGF2ZSBhdHRhY2hlZCB0aGUgcGF0Y2ggaW4gcXVlc3Rpb24u IEl0IHVzZXMgdGhlIHJpZ2h0IHN5c2ZzIHBhdGhzIGFmdGVyDQo+ZGV0ZWN0aW5nIHRoZSBrZXJu ZWwgdmVyc2lvbi4gSXQgbWlnaHQgbm90IGFwcGx5IHRvIHlvdXIgdmVyc2lvbiBidXQgaXQgbWF5 DQo+aGVscCB5b3UgbWFrZSB0aGUgY2hhbmdlIHlvdSByZXF1aXJlLg0KPj4NCj4+PiBBbHNvIHdp bGwgaW4gdGhpcyBjYXNlIG90aGVyIGx2bW9oYmEgZmVhdHVyZXMgd2lsbCB3b3JrIHNtb290aGx5 IGluDQo+Pj4gdGhhdCBjYXNlIG9uIERlYmlhbiwgZXNwZWNpYWxseSBtdWx0aXBhdGg/DQo+Pg0K Pj4gSXQncyB1bmxpa2VseSB5b3UnbGwgZ2V0IExWTSB0byB3b3JrIHdpdGggeW91ciBzZXR1cCBz aW5jZSB3ZSB1c2UgYSBwYXRjaGVkDQo+dmVyc2lvbiB0aGF0IGFjY2VwdHMgYW5vdGhlciBvcHRp b24gKC0tbWFzdGVyKSB3aGljaCBhZmZvcmRzIHVzIGEgZGlmZmVyZW50DQo+bG9ja2luZyBtZWNo YW5pc20gdG8gYWxsb3cgc2hhcmVkIFNScy4gVGhpcyBvcHRpb24gZG9lc24ndCBleGlzdCBpbiB0 aGUNCj51cHN0cmVhbSBEZWJpYW4gTFZNLg0KPj4NCj4+IEl0IG1heSghKSBiZSBwb3NzaWJsZSB0 byBnZXQgaXQgdG8gd29yayBpZiB5b3UgcmVtb3ZlIHRoZSAtLW1hc3RlciBvcHRpb24NCj5mcm9t IHRoZSBjYWxscyB0byBsdm0gaW4gdGhlIHNvdXJjZSBhbmQgZW5zdXJlIHRoYXQgeW91IGFyZSBv bmx5IHVzaW5nIHRoZXNlDQo+U1JzIGluIHNpbmdsZS1ob3N0IHBvb2xzLiBBZ2FpbiwgeW91ciBt aWxlYWdlIG1heSB2YXJ5Lg0KPj4NCj4+IEhvcGUgdGhpcyBoZWxwcywNCj4+DQo+PiAtU2kNCj4+ DQo= --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_ Content-Type: application/octet-stream; name="3.x-kernel-udev-script.patch" Content-Description: 3.x-kernel-udev-script.patch Content-Disposition: attachment; filename="3.x-kernel-udev-script.patch"; size=2330; creation-date="Fri, 18 Jan 2013 11:56:36 GMT"; modification-date="Fri, 18 Jan 2013 11:36:48 GMT" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL2JpbmFyeS1vdmVybGF5L2V0Yy91ZGV2L3NjcmlwdHMveHMtbXBhdGgtc2Nz aWRldi5zaCBiL2JpbmFyeS1vdmVybGF5L2V0Yy91ZGV2L3NjcmlwdHMveHMtbXBhdGgtc2NzaWRl di5zaAotLS0gYS9iaW5hcnktb3ZlcmxheS9ldGMvdWRldi9zY3JpcHRzL3hzLW1wYXRoLXNjc2lk ZXYuc2gKKysrIGIvYmluYXJ5LW92ZXJsYXkvZXRjL3VkZXYvc2NyaXB0cy94cy1tcGF0aC1zY3Np ZGV2LnNoCkBAIC03LDYgKzcsMjMgQEAKIE9VVD0kezR9CiBMVU49YGVjaG8gJEJVUyB8IGN1dCAt ZDogLWY0YAogCisjIFRoZSByZXF1aXJlZCBmaWxlcyBhcmUgbG9jYXRlZCBpbiBhbiBleHRyYSBs YXllciBvZiBkaXJlY3RvcmllcyBpbiAzLngga2VybmVscwora2VybmVsPWB1bmFtZSAtciB8IGN1 dCAtZC4gLWYxLTJgCitjYXNlICRrZXJuZWwgaW4KKyAgICAyLjYpCisgICAgICAgIHRhcmdldElR TlBhdGg9Ii9kZXZpY2Uvc2Vzc2lvbiovaXNjc2lfc2Vzc2lvbioiCisgICAgICAgIHRhcmdldElQ UG9ydFBhdGg9Ii9kZXZpY2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVjdGlvbioi CisgICAgICAgIDs7CisgICAgMy4qKQorICAgICAgICB0YXJnZXRJUU5QYXRoPSIvZGV2aWNlL3Nl c3Npb24qL2lzY3NpX3Nlc3Npb24vc2Vzc2lvbioiCisgICAgICAgIHRhcmdldElQUG9ydFBhdGg9 Ii9kZXZpY2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVjdGlvbi9jb25uZWN0aW9u KiIKKyAgICAgICAgOzsKKyAgICAqKQorICAgICAgICBlY2hvICJVbmtvd24ga2VybmVsOiBuZWl0 aGVyIDIuNiBub3IgMy54LiBFeGl0aW5nLi4uIgorICAgICAgICBleGl0IDIKKyAgICAgICAgOzsK K2VzYWMKKwogI0FyZ3M6IElECiBxdWVyeV9ob3N0cygpIHsKICAgICAvdXNyL3NiaW4vbXBwVXRp bCAtZyAkMSB8IGdyZXAgaG9zdElkIHwgd2hpbGUgcmVhZCBmaWxlCkBAIC0xNiwxMCArMzMsMTEg QEAKICAgICAgIFsgLWUgJHtJU0NTSVBBVEh9IF0gfHwgY29udGludWUKIAogICAgICAgI1F1ZXJ5 IHRoZSBJUU4sIElQIGFuZCBQb3J0IHZhbHVlcwotICAgICAgdGFyZ2V0SVFOZmlsZT0iJHtJU0NT SVBBVEh9L2RldmljZS9zZXNzaW9uKi9pc2NzaV9zZXNzaW9uKi90YXJnZXRuYW1lIgorICAgICAg dGFyZ2V0SVFOZmlsZT0iJHtJU0NTSVBBVEh9JHt0YXJnZXRJUU5QYXRofS90YXJnZXRuYW1lIgog ICAgICAgdGFyZ2V0SVFOPSQoY2F0ICR7dGFyZ2V0SVFOZmlsZX0pCi0gICAgICB0YXJnZXRJUGZp bGU9IiR7SVNDU0lQQVRIfS9kZXZpY2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVj dGlvbiovcGVyc2lzdGVudF9hZGRyZXNzIgotICAgICAgdGFyZ2V0UG9ydGZpbGU9IiR7SVNDU0lQ QVRIfS9kZXZpY2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVjdGlvbiovcGVyc2lz dGVudF9wb3J0IgorCisgICAgICB0YXJnZXRJUGZpbGU9IiR7SVNDU0lQQVRIfSR7dGFyZ2V0SVBQ b3J0UGF0aH0vcGVyc2lzdGVudF9hZGRyZXNzIgorICAgICAgdGFyZ2V0UG9ydGZpbGU9IiR7SVND U0lQQVRIfSR7dGFyZ2V0SVBQb3J0UGF0aH0vcGVyc2lzdGVudF9wb3J0IgogICAgICAgdGFyZ2V0 SVA9JChjYXQgJHt0YXJnZXRJUGZpbGV9KQogICAgICAgdGFyZ2V0UG9ydD0kKGNhdCAke3Rhcmdl dFBvcnRmaWxlfSkKIApAQCAtNjksMTIgKzg3LDEyIEBACiBbIC1lICR7SVNDU0lQQVRIfSBdIHx8 IGV4aXQgMQogCiAjIFF1ZXJ5IHRhcmdldElRTgotdGFyZ2V0SVFOZmlsZT0iJHtJU0NTSVBBVEh9 L2RldmljZS9zZXNzaW9uKi9pc2NzaV9zZXNzaW9uKi90YXJnZXRuYW1lIgordGFyZ2V0SVFOZmls ZT0iJHtJU0NTSVBBVEh9JHt0YXJnZXRJUU5QYXRofS90YXJnZXRuYW1lIgogdGFyZ2V0SVFOPSQo Y2F0ICR7dGFyZ2V0SVFOZmlsZX0pCiAKICMgUXVlcnkgdGFyZ2V0IGFkZHJlc3MgYW5kIHBvcnQK LXRhcmdldElQZmlsZT0iJHtJU0NTSVBBVEh9L2RldmljZS9zZXNzaW9uKi9jb25uZWN0aW9uKi9p c2NzaV9jb25uZWN0aW9uKi9wZXJzaXN0ZW50X2FkZHJlc3MiCi10YXJnZXRQb3J0ZmlsZT0iJHtJ U0NTSVBBVEh9L2RldmljZS9zZXNzaW9uKi9jb25uZWN0aW9uKi9pc2NzaV9jb25uZWN0aW9uKi9w ZXJzaXN0ZW50X3BvcnQiCit0YXJnZXRJUGZpbGU9IiR7SVNDU0lQQVRIfSR7dGFyZ2V0SVBQb3J0 UGF0aH0vcGVyc2lzdGVudF9hZGRyZXNzIgordGFyZ2V0UG9ydGZpbGU9IiR7SVNDU0lQQVRIfSR7 dGFyZ2V0SVBQb3J0UGF0aH0vcGVyc2lzdGVudF9wb3J0IgogdGFyZ2V0SVA9JChjYXQgJHt0YXJn ZXRJUGZpbGV9KQogdGFyZ2V0UG9ydD0kKGNhdCAke3RhcmdldFBvcnRmaWxlfSkKIAo= --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_ Content-Type: application/octet-stream; name="3.x-kernel-iscsi-sysfs.patch" Content-Description: 3.x-kernel-iscsi-sysfs.patch Content-Disposition: attachment; filename="3.x-kernel-iscsi-sysfs.patch"; size=5272; creation-date="Fri, 18 Jan 2013 11:57:02 GMT"; modification-date="Fri, 18 Jan 2013 11:56:52 GMT" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL1hlbkNlcnQvU3RvcmFnZUhhbmRsZXJVdGlsLnB5IGIvWGVuQ2VydC9TdG9y YWdlSGFuZGxlclV0aWwucHkKLS0tIGEvWGVuQ2VydC9TdG9yYWdlSGFuZGxlclV0aWwucHkKKysr IGIvWGVuQ2VydC9TdG9yYWdlSGFuZGxlclV0aWwucHkKQEAgLTExOSwxMiArMTE5LDggQEAKICAg ICBhZGFwdGVyID0ge30KICAgICBmb3IgaG9zdCBpbiBpZHM6CiAgICAgICAgIHRyeToKLSAgICAg ICAgICAgIHRhcmdldElRTiA9IHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShnbG9iLmdsb2IoXAotICAg ICAgICAgICAgICAgICcvc3lzL2NsYXNzL2lzY3NpX2hvc3QvaG9zdCVzL2RldmljZS9zZXNzaW9u Ki9pc2NzaV9zZXNzaW9uKi90YXJnZXRuYW1lJyAlIGhvc3QpWzBdKQotICAgICAgICAgICAgYWRk ciA9IHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShnbG9iLmdsb2IoXAotICAgICAgICAgICAgICAgICcv c3lzL2NsYXNzL2lzY3NpX2hvc3QvaG9zdCVzL2RldmljZS9zZXNzaW9uKi9jb25uZWN0aW9uKi9p c2NzaV9jb25uZWN0aW9uKi9wZXJzaXN0ZW50X2FkZHJlc3MnICUgaG9zdClbMF0pCi0gICAgICAg ICAgICBwb3J0ID0gdXRpbC5nZXRfc2luZ2xlX2VudHJ5KGdsb2IuZ2xvYihcCi0gICAgICAgICAg ICAgICAgJy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlL3Nlc3Npb24qL2Nvbm5l Y3Rpb24qL2lzY3NpX2Nvbm5lY3Rpb24qL3BlcnNpc3RlbnRfcG9ydCcgJSBob3N0KVswXSkKKyAg ICAgICAgICAgIHRhcmdldElRTiA9IGlzY3NpbGliLmdldF90YXJnZXRJUU4oaG9zdCkKKyAgICAg ICAgICAgIChhZGRyLCBwb3J0KSA9IGlzY3NpbGliLmdldF90YXJnZXRJUF9hbmRfcG9ydChob3N0 KQogICAgICAgICAgICAgZW50cnkgPSAiJXM6JXMiICUgKGFkZHIscG9ydCkKICAgICAgICAgICAg IGFkYXB0ZXJbZW50cnldID0gaG9zdAogICAgICAgICBleGNlcHQgRXhjZXB0aW9uLCBlOgpkaWZm IC0tZ2l0IGEvZHJpdmVycy9JU0NTSVNSLnB5IGIvZHJpdmVycy9JU0NTSVNSLnB5Ci0tLSBhL2Ry aXZlcnMvSVNDU0lTUi5weQorKysgYi9kcml2ZXJzL0lTQ1NJU1IucHkKQEAgLTIzMiwxNCArMjMy LDEwIEBACiAgICAgICAgIHNlbGYuYWRhcHRlciA9IHt9CiAgICAgICAgIGZvciBob3N0IGluIGlk czoKICAgICAgICAgICAgIHRyeToKLSAgICAgICAgICAgICAgICB0YXJnZXRJUU4gPSB1dGlsLmdl dF9zaW5nbGVfZW50cnkoZ2xvYi5nbG9iKFwKLSAgICAgICAgICAgICAgICAgICAgJy9zeXMvY2xh c3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlL3Nlc3Npb24qL2lzY3NpX3Nlc3Npb24qL3Rhcmdl dG5hbWUnICUgaG9zdClbMF0pCisgICAgICAgICAgICAgICAgdGFyZ2V0SVFOID0gaXNjc2lsaWIu Z2V0X3RhcmdldElRTihob3N0KQogICAgICAgICAgICAgICAgIGlmIHRhcmdldElRTiAhPSBzZWxm LnRhcmdldElRTjoKICAgICAgICAgICAgICAgICAgICAgY29udGludWUKLSAgICAgICAgICAgICAg ICBhZGRyID0gdXRpbC5nZXRfc2luZ2xlX2VudHJ5KGdsb2IuZ2xvYihcCi0gICAgICAgICAgICAg ICAgICAgICcvc3lzL2NsYXNzL2lzY3NpX2hvc3QvaG9zdCVzL2RldmljZS9zZXNzaW9uKi9jb25u ZWN0aW9uKi9pc2NzaV9jb25uZWN0aW9uKi9wZXJzaXN0ZW50X2FkZHJlc3MnICUgaG9zdClbMF0p Ci0gICAgICAgICAgICAgICAgcG9ydCA9IHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShnbG9iLmdsb2Io XAotICAgICAgICAgICAgICAgICAgICAnL3N5cy9jbGFzcy9pc2NzaV9ob3N0L2hvc3Qlcy9kZXZp Y2Uvc2Vzc2lvbiovY29ubmVjdGlvbiovaXNjc2lfY29ubmVjdGlvbiovcGVyc2lzdGVudF9wb3J0 JyAlIGhvc3QpWzBdKQorICAgICAgICAgICAgICAgIChhZGRyLCBwb3J0KSA9IGlzY3NpbGliLmdl dF90YXJnZXRJUF9hbmRfcG9ydChob3N0KQogICAgICAgICAgICAgICAgIGVudHJ5ID0gIiVzOiVz IiAlIChhZGRyLHBvcnQpCiAgICAgICAgICAgICAgICAgc2VsZi5hZGFwdGVyW2VudHJ5XSA9IGhv c3QKICAgICAgICAgICAgIGV4Y2VwdDoKQEAgLTMyOCwxMSArMzI0LDEwIEBACiAgICAgICAgIGVs c2U6CiAgICAgICAgICAgICBJUU5zLmFwcGVuZChzZWxmLnRhcmdldElRTikKICAgICAgICAgc2Vz c2lvbnMgPSAwCi0gICAgICAgIHBhdGhzID0gZ2xvYi5nbG9iKFwKLSAgICAgICAgICAgICAgICAg ICAgJy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0Ki9kZXZpY2Uvc2Vzc2lvbiovaXNjc2lfc2Vz c2lvbiovdGFyZ2V0bmFtZScpCisgICAgICAgIHBhdGhzID0gaXNjc2lsaWIuZ2V0X0lRTl9wYXRo cygpCiAgICAgICAgIGZvciBwYXRoIGluIHBhdGhzOgogICAgICAgICAgICAgdHJ5OgotICAgICAg ICAgICAgICAgIGlmIHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShwYXRoKSBpbiBJUU5zOgorICAgICAg ICAgICAgICAgIGlmIHV0aWwuZ2V0X3NpbmdsZV9lbnRyeShvcy5wYXRoLmpvaW4ocGF0aCwgJ3Rh cmdldG5hbWUnKSkgaW4gSVFOczoKICAgICAgICAgICAgICAgICAgICAgc2Vzc2lvbnMgKz0gMQog ICAgICAgICAgICAgICAgICAgICB1dGlsLlNNbG9nKCJJUU4gbWF0Y2guIEluY3JlbWVudGluZyBz ZXNzaW9ucyB0byAlZCIgJSBzZXNzaW9ucykKICAgICAgICAgICAgIGV4Y2VwdDoKZGlmZiAtLWdp dCBhL2RyaXZlcnMvWEVfU1JfRVJST1JDT0RFUy54bWwgYi9kcml2ZXJzL1hFX1NSX0VSUk9SQ09E RVMueG1sCi0tLSBhL2RyaXZlcnMvWEVfU1JfRVJST1JDT0RFUy54bWwKKysrIGIvZHJpdmVycy9Y RV9TUl9FUlJPUkNPREVTLnhtbApAQCAtODk3LDQgKzg5Nyw5IEBACiAJCQk8dmFsdWU+NDQ3PC92 YWx1ZT4NCiAJCTwvY29kZT4NCiANCisgICAgICAgIDxjb2RlPg0KKyAgICAgICAgICAgIDxuYW1l PlVuc3VwcG9ydGVkS2VybmVsPC9uYW1lPg0KKyAgICAgICAgICAgIDxkZXNjcmlwdGlvbj5VbnN1 cHBvcnRlZCBrZXJuZWw6IG5laXRoZXIgMi42IG5vciAzLnguPC9kZXNjcmlwdGlvbj4NCisgICAg ICAgICAgICA8dmFsdWU+NDQ4PC92YWx1ZT4NCisgICAgICAgIDwvY29kZT4NCiA8L1NNLWVycm9y Y29kZXM+DQpkaWZmIC0tZ2l0IGEvZHJpdmVycy9pc2NzaWxpYi5weSBiL2RyaXZlcnMvaXNjc2ls aWIucHkKLS0tIGEvZHJpdmVycy9pc2NzaWxpYi5weQorKysgYi9kcml2ZXJzL2lzY3NpbGliLnB5 CkBAIC0xOCw4ICsxOCwyNSBAQAogaW1wb3J0IHNodXRpbAogaW1wb3J0IHhzX2Vycm9ycwogaW1w b3J0IGxvY2sKK2ltcG9ydCBnbG9iCiBmcm9tIGNsZWFudXAgaW1wb3J0IExPQ0tfVFlQRV9SVU5O SU5HCiAKKyMgVGhlIDMueCBrZXJuZWwgYnJpbmdzIHdpdGggaXQgc29tZSBpU0NTSSBwYXRoIGNo YW5nZXMgaW4gc3lzZnMKK19LRVJORUxfVkVSU0lPTiA9IG9zLnVuYW1lKClbMl0KK2lmIF9LRVJO RUxfVkVSU0lPTi5zdGFydHN3aXRoKCcyLjYnKToKKyAgICBfR0VORVJJQ19TRVNTSU9OX1BBVEgg PSAoJy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlL3Nlc3Npb24qLycgKworICAg ICAgICAgICAgJ2lzY3NpX3Nlc3Npb24qLycpCisgICAgX0dFTkVSSUNfQ09OTkVDVElPTl9QQVRI ID0gKCcvc3lzL2NsYXNzL2lzY3NpX2hvc3QvaG9zdCVzL2RldmljZS8nICsKKyAgICAgICAgICAg ICdzZXNzaW9uKi9jb25uZWN0aW9uKi9pc2NzaV9jb25uZWN0aW9uKi8nKQorZWxpZiBfS0VSTkVM X1ZFUlNJT04uc3RhcnRzd2l0aCgnMy4nKToKKyAgICBfR0VORVJJQ19TRVNTSU9OX1BBVEggPSAo Jy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlL3Nlc3Npb24qLycgKworICAgICAg ICAgICAgJ2lzY3NpX3Nlc3Npb24vc2Vzc2lvbiovJykKKyAgICBfR0VORVJJQ19DT05ORUNUSU9O X1BBVEggPSAoJy9zeXMvY2xhc3MvaXNjc2lfaG9zdC9ob3N0JXMvZGV2aWNlLycgKworICAgICAg ICAgICAgJ3Nlc3Npb24qL2Nvbm5lY3Rpb24qL2lzY3NpX2Nvbm5lY3Rpb24vY29ubmVjdGlvbiov JykKK2Vsc2U6CisgICAgX21zZyA9ICdLZXJuZWwgdmVyc2lvbiBkZXRlY3RlZDogJXMnICUgX0tF Uk5FTF9WRVJTSU9OCisgICAgcmFpc2UgeHNfZXJyb3JzLlhlbkVycm9yKCdVbnN1cHBvcnRlZEtl cm5lbCcsIF9tc2cpCisKIGRlZiBleG5fb25fZmFpbHVyZShjbWQsIG1lc3NhZ2UpOgogICAgICcn J0V4ZWN1dGVzIHZpYSB1dGlsLmRvZXhlYyB0aGUgY29tbWFuZCBzcGVjaWZpZWQuIElmIHRoZSBy ZXR1cm4gY29kZSBpcyAKICAgICBub24temVybywgcmFpc2VzIGFuIElTQ1NJRXJyb3Igd2l0aCB0 aGUgZ2l2ZW4gbWVzc2FnZScnJwpAQCAtMjU1LDYgKzI3MiwyNSBAQAogICAgIGV4Y2VwdDoKICAg ICAgICAgcGFzcwogCitkZWYgZ2V0X0lRTl9wYXRocygpOgorICAgICIiIlJldHVybiB0aGUgbGlz dCBvZiBpU0NTSSBzZXNzaW9uIGRpcmVjdG9yaWVzIiIiCisgICAgcmV0dXJuIGdsb2IuZ2xvYihf R0VORVJJQ19TRVNTSU9OX1BBVEggJSAnKicpCisKK2RlZiBnZXRfdGFyZ2V0SVFOKGlzY3NpX2hv c3QpOgorICAgICIiIkdldCB0YXJnZXQgSVFOIGZyb20gc3lzZnMgZm9yIGdpdmVuIGlTQ1NJIGhv c3QgbnVtYmVyIiIiCisgICAgaXFuX2ZpbGUgPSBvcy5wYXRoLmpvaW4oX0dFTkVSSUNfU0VTU0lP Tl9QQVRIICUgaXNjc2lfaG9zdCwgJ3RhcmdldG5hbWUnKQorICAgIHRhcmdldElRTiA9IHV0aWwu Z2V0X3NpbmdsZV9lbnRyeShnbG9iLmdsb2IoaXFuX2ZpbGUpWzBdKQorICAgIHJldHVybiB0YXJn ZXRJUU4KKworZGVmIGdldF90YXJnZXRJUF9hbmRfcG9ydChpc2NzaV9ob3N0KToKKyAgICAiIiJH ZXQgdGFyZ2V0IElQIGFkZHJlc3MgYW5kIHBvcnQgZm9yIGdpdmVuIGlTQ1NJIGhvc3QgbnVtYmVy IiIiCisgICAgY29ubmVjdGlvbl9kaXIgPSBfR0VORVJJQ19DT05ORUNUSU9OX1BBVEggJSBpc2Nz aV9ob3N0CisgICAgaXAgPSB1dGlsLmdldF9zaW5nbGVfZW50cnkoZ2xvYi5nbG9iKG9zLnBhdGgu am9pbigKKyAgICAgICAgICAgIGNvbm5lY3Rpb25fZGlyLCAncGVyc2lzdGVudF9hZGRyZXNzJykp WzBdKQorICAgIHBvcnQgPSB1dGlsLmdldF9zaW5nbGVfZW50cnkoZ2xvYi5nbG9iKG9zLnBhdGgu am9pbigKKyAgICAgICAgICAgIGNvbm5lY3Rpb25fZGlyLCAncGVyc2lzdGVudF9wb3J0JykpWzBd KQorICAgIHJldHVybiAoaXAsIHBvcnQpCisKIGRlZiBnZXRfcGF0aCh0YXJnZXRJUU4sIHBvcnRh bCwgbHVuKToKICAgICAiIiJHZXRzIHRoZSBwYXRoIG9mIGEgc3BlY2lmaWVkIExVTiAtIHRoaXMg c2hvdWxkIGJlIGUuZy4gJzEnIG9yICc1JyIiIgogICAgIHBhdGggPSBvcy5wYXRoLmpvaW4oIi9k ZXYvaXNjc2kiLHRhcmdldElRTixwb3J0YWwpCg== --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --_003_344C0F67BC927847A2C92F9EE358DB0E01224E1417EALONPMAILBOX_-- From xen-api-bounces@lists.xen.org Fri Jan 18 13:01:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 13:01:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwBZP-0006g8-SX; Fri, 18 Jan 2013 13:01:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwBZO-0006fy-Ra for xen-api@lists.xen.org; Fri, 18 Jan 2013 13:01:19 +0000 Received: from [85.158.137.99:60891] by server-15.bemta-3.messagelabs.com id 0B/C2-25008-99749F05; Fri, 18 Jan 2013 13:01:13 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1358514071!14353297!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27946 invoked from network); 18 Jan 2013 13:01:12 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2013 13:01:12 -0000 Received: by mail-la0-f41.google.com with SMTP id em20so3845213lab.28 for ; Fri, 18 Jan 2013 05:01:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=0qOGjNhyhJKkEIYQLjSQQUooaMDXGTAI1sUOG/aZQw8=; b=SErKe+cTYyKp06dgqI4N5q+2i4ABTpyO5Xtd6MfO31ti+2R4JR91iKek9I+IBMC2Mb h8mdwP6nUofisNkvN3a0J3p4u6yL3mlB6/t1TNg0Zo85wiLmE4EUtNlRpXpf1fTL090r YWokev6b333tMv8z8RLgyDGy02Ko/7GX2O+zr5HUxDsnLRc5taOVWgUEjWpMzpKR+1db zDEGQK3RVMRTwWa+Cty8UCxq8x9fWDB9QOkC08P+PUlyORBiAQEfbkU+mFVB4tTeXF5Y g7MX+PtbDIUXJzYuejEjrQgjK0CtaeBUQ/ohtnRgJTagi6ZTvHuTAxgtK/evpdgvm60B GmWg== X-Received: by 10.112.40.129 with SMTP id x1mr3771373lbk.95.1358514071269; Fri, 18 Jan 2013 05:01:11 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03? ([2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03]) by mx.google.com with ESMTPS id o2sm2080165lby.11.2013.01.18.05.01.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Jan 2013 05:01:10 -0800 (PST) Message-ID: <50F94796.1080907@gmail.com> Date: Fri, 18 Jan 2013 17:01:10 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50F92D7E.50908@bk.ru> In-Reply-To: <50F92D7E.50908@bk.ru> Subject: Re: [Xen-API] xcp-xapi antispoof and QoS support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Rm9yIG9sZGVyIHZlcnNpb25zIG9mIFhDUCAoY3VycmVudCB2ZXJzaW9uIGluIFNpZC93aGVlenkg aW5jbHVkZXMgaGVyZSAKdG9vKSBJIHBvc3QgYSBwYXRjaCB0byB2aWYgc2NyaXB0IHNvbWUgdGlt ZSBhZ28gKHRoYXQgY29kZSBpbiBwcm9kdWN0IAphYm91dCAyIHllYXJzIGFscmVhZHkpIC0gaXQg bm90IHNvIGZhbmN5IGFzIHhhcGkgZmllbGRzLCBidXQgd29ya2luZy4KCk9yIHlvdSBjYW4ganVz dCB0cnkgdG8gYnVpbGQgeGNwLXhhcGkgb24gd2hlZXp5IGZyb20gdGFtcGEtbGNtIGJyYW5jaCAK ZnJvbSBnaXRodWIuCgoxOC4wMS4yMDEzIDE1OjA5LCBBbmRyZXkg0L/QuNGI0LXRgjoKPiBIZWxs bywKPgo+IEknbSB0cnlpbmcgdG8gc2V0dXAgUW9TIGZvciB0aGUgdmlmWC5YIHdpdGggeGNwLXhh cGkgaW5zdGFsbGVkIG9uIAo+IERlYmlhbiBXaGVlenkgYnV0IGl0IGRvZXMgbm90IHdvcmsuIEFs c28gSSBkb24ndCBzZWUgYW55IGFudGlzcG9vZiBYQ1AgCj4gMS42IHJlbGF0ZWQgZmllbGRzIGlu IHZpZi1wYXJhbS1zZXQgb3V0cHV0IHN1Y2ggYXMgbG9ja2luZy1tb2RlIGFuZCAKPiBpcHY0LWFs bG93ZWQuCj4KPiBJcyB0aGVyZSBhbnkgc3VwcG9ydCBvZiB0aGVzZSBmZWF0dXJlcyBpbiB4Y3At eGFwaShrcm9ub3MpPyBJZiBub3QgSSAKPiB3aWxsIGhhdmUgdG8gZGlzY2FyZCBvZiB1c2luZyBp dCBmb3Igb3V0IHB1cnBvc2VzLCBpdCdzIGEgZ3JlYXQgcGl0eS4uLgo+Cj4gQW5kcmV5Cj4KPiBf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1hcGkg bWFpbGluZyBsaXN0Cj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5v cmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKCgpfX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBp QGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Fri Jan 18 13:01:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 18 Jan 2013 13:01:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwBZP-0006g8-SX; Fri, 18 Jan 2013 13:01:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwBZO-0006fy-Ra for xen-api@lists.xen.org; Fri, 18 Jan 2013 13:01:19 +0000 Received: from [85.158.137.99:60891] by server-15.bemta-3.messagelabs.com id 0B/C2-25008-99749F05; Fri, 18 Jan 2013 13:01:13 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1358514071!14353297!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27946 invoked from network); 18 Jan 2013 13:01:12 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2013 13:01:12 -0000 Received: by mail-la0-f41.google.com with SMTP id em20so3845213lab.28 for ; Fri, 18 Jan 2013 05:01:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=0qOGjNhyhJKkEIYQLjSQQUooaMDXGTAI1sUOG/aZQw8=; b=SErKe+cTYyKp06dgqI4N5q+2i4ABTpyO5Xtd6MfO31ti+2R4JR91iKek9I+IBMC2Mb h8mdwP6nUofisNkvN3a0J3p4u6yL3mlB6/t1TNg0Zo85wiLmE4EUtNlRpXpf1fTL090r YWokev6b333tMv8z8RLgyDGy02Ko/7GX2O+zr5HUxDsnLRc5taOVWgUEjWpMzpKR+1db zDEGQK3RVMRTwWa+Cty8UCxq8x9fWDB9QOkC08P+PUlyORBiAQEfbkU+mFVB4tTeXF5Y g7MX+PtbDIUXJzYuejEjrQgjK0CtaeBUQ/ohtnRgJTagi6ZTvHuTAxgtK/evpdgvm60B GmWg== X-Received: by 10.112.40.129 with SMTP id x1mr3771373lbk.95.1358514071269; Fri, 18 Jan 2013 05:01:11 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03? ([2a00:ab00:0:fffe:68f2:f3e6:a94b:7d03]) by mx.google.com with ESMTPS id o2sm2080165lby.11.2013.01.18.05.01.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Jan 2013 05:01:10 -0800 (PST) Message-ID: <50F94796.1080907@gmail.com> Date: Fri, 18 Jan 2013 17:01:10 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50F92D7E.50908@bk.ru> In-Reply-To: <50F92D7E.50908@bk.ru> Subject: Re: [Xen-API] xcp-xapi antispoof and QoS support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Rm9yIG9sZGVyIHZlcnNpb25zIG9mIFhDUCAoY3VycmVudCB2ZXJzaW9uIGluIFNpZC93aGVlenkg aW5jbHVkZXMgaGVyZSAKdG9vKSBJIHBvc3QgYSBwYXRjaCB0byB2aWYgc2NyaXB0IHNvbWUgdGlt ZSBhZ28gKHRoYXQgY29kZSBpbiBwcm9kdWN0IAphYm91dCAyIHllYXJzIGFscmVhZHkpIC0gaXQg bm90IHNvIGZhbmN5IGFzIHhhcGkgZmllbGRzLCBidXQgd29ya2luZy4KCk9yIHlvdSBjYW4ganVz dCB0cnkgdG8gYnVpbGQgeGNwLXhhcGkgb24gd2hlZXp5IGZyb20gdGFtcGEtbGNtIGJyYW5jaCAK ZnJvbSBnaXRodWIuCgoxOC4wMS4yMDEzIDE1OjA5LCBBbmRyZXkg0L/QuNGI0LXRgjoKPiBIZWxs bywKPgo+IEknbSB0cnlpbmcgdG8gc2V0dXAgUW9TIGZvciB0aGUgdmlmWC5YIHdpdGggeGNwLXhh cGkgaW5zdGFsbGVkIG9uIAo+IERlYmlhbiBXaGVlenkgYnV0IGl0IGRvZXMgbm90IHdvcmsuIEFs c28gSSBkb24ndCBzZWUgYW55IGFudGlzcG9vZiBYQ1AgCj4gMS42IHJlbGF0ZWQgZmllbGRzIGlu IHZpZi1wYXJhbS1zZXQgb3V0cHV0IHN1Y2ggYXMgbG9ja2luZy1tb2RlIGFuZCAKPiBpcHY0LWFs bG93ZWQuCj4KPiBJcyB0aGVyZSBhbnkgc3VwcG9ydCBvZiB0aGVzZSBmZWF0dXJlcyBpbiB4Y3At eGFwaShrcm9ub3MpPyBJZiBub3QgSSAKPiB3aWxsIGhhdmUgdG8gZGlzY2FyZCBvZiB1c2luZyBp dCBmb3Igb3V0IHB1cnBvc2VzLCBpdCdzIGEgZ3JlYXQgcGl0eS4uLgo+Cj4gQW5kcmV5Cj4KPiBf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1hcGkg bWFpbGluZyBsaXN0Cj4gWGVuLWFwaUBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5v cmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKCgpfX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBp QGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Sun Jan 20 01:54:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 01:54:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twk7I-0007jV-5F; Sun, 20 Jan 2013 01:54:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twk7G-0007jQ-Ts for xen-api@lists.xen.org; Sun, 20 Jan 2013 01:54:35 +0000 Received: from [85.158.143.35:30865] by server-3.bemta-4.messagelabs.com id 5F/09-10689-A5E4BF05; Sun, 20 Jan 2013 01:54:34 +0000 X-Env-Sender: werners@bloudraak.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1358646871!11779831!1 X-Originating-IP: [74.125.149.250] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23684 invoked from network); 20 Jan 2013 01:54:33 -0000 Received: from na3sys009aog132.obsmtp.com (HELO na3sys009aog132.obsmtp.com) (74.125.149.250) by server-7.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Jan 2013 01:54:33 -0000 Received: from bloudraak.com ([66.209.67.179]) by na3sys009aob132.postini.com ([74.125.148.12]) with SMTP ID DSNKUPtOV8QBJ+Ab9sGB9L0PUQz1aNy4e4SL@postini.com; Sat, 19 Jan 2013 17:54:33 PST Received: from [192.168.1.100] (c-69-181-25-84.hsd1.ca.comcast.net [69.181.25.84]) by bloudraak.com (Postfix) with ESMTPSA id EEB0562F2371; Sat, 19 Jan 2013 17:54:30 -0800 (PST) From: Werner Strydom Date: Sat, 19 Jan 2013 17:54:28 -0800 To: xen-api@lists.xen.org Message-Id: <3371CE47-8A8A-42AA-B71F-59CFD714B593@bloudraak.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Subject: [Xen-API] Running OS X 10.8 as a guest in XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I installed XCP using the ISO image on a Mac Mini without any problems other than blessing the hard disk. The Mac Mini has a model identifier of "macmini6,2". As I'm typing this, it runs Ubuntu 12.04 and Windows Server 2012 without any problems. I wouldn't mind to spend some time to see if I can get OS X 10.8, OS X 10.7 and OS X 10.6 running. The fact that it is not supported isn't a problem. At this point I'm stuck with two issues: - Boot OS X Mountain Lion from ISO inside XCP - Displaying graphics when OS X boots up I converted the InstallESD.dmg to an ISO. However, creating a virtual machine in XCP and booting from the ISO I get an error "failure: could not read boot disk". I can use the same ISO to create OS X 10.8 virtual machines in ESXi, Parallels, VMware Fusion without much hassle. So I tried to boot from the USB recovery disk. This time I get a message "Boot Device: Hard Drive - success", however, no graphics is displayed. Looking at CPU and network usage, something is happening in that CPU usage is 100% for a couple of minutes, and network usage indicates something is being downloaded. This consistent with when the recovery agent is running on my Mac and preparing for recovery by downloading stuff from the internet. >From what I'm gathering this may be related to support for EFI, but I can't be sure. Before we digress by discussing legal implications of doing this, I am running this on Apple hardware and have server licenses for OS X Snow Leopard. I'd appreciate any help. Thanks, Werner -- Werner Strydom wernerstrydom.com _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 20 01:54:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 01:54:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twk7I-0007jV-5F; Sun, 20 Jan 2013 01:54:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twk7G-0007jQ-Ts for xen-api@lists.xen.org; Sun, 20 Jan 2013 01:54:35 +0000 Received: from [85.158.143.35:30865] by server-3.bemta-4.messagelabs.com id 5F/09-10689-A5E4BF05; Sun, 20 Jan 2013 01:54:34 +0000 X-Env-Sender: werners@bloudraak.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1358646871!11779831!1 X-Originating-IP: [74.125.149.250] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23684 invoked from network); 20 Jan 2013 01:54:33 -0000 Received: from na3sys009aog132.obsmtp.com (HELO na3sys009aog132.obsmtp.com) (74.125.149.250) by server-7.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Jan 2013 01:54:33 -0000 Received: from bloudraak.com ([66.209.67.179]) by na3sys009aob132.postini.com ([74.125.148.12]) with SMTP ID DSNKUPtOV8QBJ+Ab9sGB9L0PUQz1aNy4e4SL@postini.com; Sat, 19 Jan 2013 17:54:33 PST Received: from [192.168.1.100] (c-69-181-25-84.hsd1.ca.comcast.net [69.181.25.84]) by bloudraak.com (Postfix) with ESMTPSA id EEB0562F2371; Sat, 19 Jan 2013 17:54:30 -0800 (PST) From: Werner Strydom Date: Sat, 19 Jan 2013 17:54:28 -0800 To: xen-api@lists.xen.org Message-Id: <3371CE47-8A8A-42AA-B71F-59CFD714B593@bloudraak.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Subject: [Xen-API] Running OS X 10.8 as a guest in XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello, I installed XCP using the ISO image on a Mac Mini without any problems other than blessing the hard disk. The Mac Mini has a model identifier of "macmini6,2". As I'm typing this, it runs Ubuntu 12.04 and Windows Server 2012 without any problems. I wouldn't mind to spend some time to see if I can get OS X 10.8, OS X 10.7 and OS X 10.6 running. The fact that it is not supported isn't a problem. At this point I'm stuck with two issues: - Boot OS X Mountain Lion from ISO inside XCP - Displaying graphics when OS X boots up I converted the InstallESD.dmg to an ISO. However, creating a virtual machine in XCP and booting from the ISO I get an error "failure: could not read boot disk". I can use the same ISO to create OS X 10.8 virtual machines in ESXi, Parallels, VMware Fusion without much hassle. So I tried to boot from the USB recovery disk. This time I get a message "Boot Device: Hard Drive - success", however, no graphics is displayed. Looking at CPU and network usage, something is happening in that CPU usage is 100% for a couple of minutes, and network usage indicates something is being downloaded. This consistent with when the recovery agent is running on my Mac and preparing for recovery by downloading stuff from the internet. >From what I'm gathering this may be related to support for EFI, but I can't be sure. Before we digress by discussing legal implications of doing this, I am running this on Apple hardware and have server licenses for OS X Snow Leopard. I'd appreciate any help. Thanks, Werner -- Werner Strydom wernerstrydom.com _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 20 13:00:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 13:00:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwuVX-0002F4-Qt; Sun, 20 Jan 2013 13:00:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwuVW-0002Ez-M8 for xen-api@lists.xen.org; Sun, 20 Jan 2013 13:00:18 +0000 Received: from [85.158.139.83:42707] by server-3.bemta-5.messagelabs.com id 90/B8-15993-16AEBF05; Sun, 20 Jan 2013 13:00:17 +0000 X-Env-Sender: adhi.pri@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1358686814!24369140!1 X-Originating-IP: [209.85.219.46] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8312 invoked from network); 20 Jan 2013 13:00:16 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2013 13:00:16 -0000 Received: by mail-oa0-f46.google.com with SMTP id h16so5286846oag.33 for ; Sun, 20 Jan 2013 05:00:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=OjvxIKHlX1fJVEn+xRMK9IIWzYINgoRkAu4tpf7OS20=; b=bFO34dziBZlvCC6OnqPvpJ8SjZBWsjcYUIowZx8KCwNaeTNNbTXnckh3SBmTGbt5oy 0GsmAbrv7qNKfBvCezLr/f8EQOw1B5bQ+06/sd37eGRIFR7MrRVifL1M+R/xPNzDZks3 s9Dr9ZvyoH8L5slpMI1GAp5fuh7ZiEINUAVak/V2TEypzDS7NW47aRIosUbqqbwyE1zA 71NHFLzBPU5b1TmKVp+ZaqX+FjFpv8olCWNTDW8McoaSg6FwICW6AyxnQgaay+XhAoEY gBGNfyhkKp/qVGw0cIkgsMvut5b7yvU4MjcumlZuXruXIpWMAdZl/anR1Pz8xGaShsR0 HB5A== MIME-Version: 1.0 X-Received: by 10.182.131.101 with SMTP id ol5mr11397230obb.12.1358686814265; Sun, 20 Jan 2013 05:00:14 -0800 (PST) Received: by 10.76.153.33 with HTTP; Sun, 20 Jan 2013 05:00:14 -0800 (PST) Date: Sun, 20 Jan 2013 20:00:14 +0700 Message-ID: From: Adhi Priharmanto To: xen-api@lists.xen.org Subject: [Xen-API] Centos 5.9 can't boot in xcp 1.1 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6562387658842608824==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6562387658842608824== Content-Type: multipart/alternative; boundary=e89a8f503946ece16d04d3b7ec16 --e89a8f503946ece16d04d3b7ec16 Content-Type: text/plain; charset=ISO-8859-1 Hi, I Was running in XCP 1.1 for a years, no problem until 2 days ago. I have 4 x XCP 1.1 group-in 1 pool, tweak with this guide http://wiki.xen.org/wiki/XenCenterXCP, storage with iSCSI - the problem was start at our VM centos 5.8 with cpanel was doing scripts/upcp automaticaly, VM centos 5.8 was got high load, so I decide to force reboot. - In xencenter console show boot was stuck, here few last messages shown: kjournald starting. Commit interval 5 seconds > > EXT3-fs: mounted filesystem with ordered data mode. > > Setting up other filesystems. > > Setting up new root fs > > no fstab.sys, mounting internal defaults > > Switching to new root and running init. > > unmounting old /dev > > unmounting old /proc > > unmounting old /sys > > > > no process after this condition - Try to create new VM using centos 5-3 iso , VM working successfully, but when working yum update it's stuck in process > Updating : tzdata [ 5/627] > Updating : glibc-common [ 6/627] > process > top - 05:30:19 up 21 min, 3 users, load average: 1.04, 1.00, 0.72 > Tasks: 114 total, 2 running, 112 sleeping, 0 stopped, 0 zombie > Cpu(s): 16.2%us, 0.0%sy, 0.0%ni, 83.8%id, 0.0%wa, 0.0%hi, 0.0%si, > 0.0%st > Mem: 4194304k total, 814456k used, 3379848k free, 25952k buffers > Swap: 4095992k total, 0k used, 4095992k free, 531584k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ > COMMAND > 2057 root 25 0 788 140 108 R 100.0 0.0 19:39.74 > build-locale-ar > 1 root 15 0 10344 732 608 S 0.0 0.0 0:00.01 init > > # ps ax |grep build > 2057 pts/0 R+ 20:11 /usr/sbin/build-locale-archive > 2853 pts/1 S+ 0:00 grep build > wait for an few times no clue, and CPU utilization get High until 100%, and if the VM rebooted, will be stuck same at case above. - In same pool I was download centos 5.9 xva templates from stacklet, and try to import and start in pool as new VM , but another weird show at booting, last message shown are : en virtual console successfully installed as xvc0 > Event-channel device installed. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > Initalizing network drop monitor service > Write protecting the kernel read-only data: 506k > Could somebody help me ???? - Best Regards, *Adhi Priharmanto* --e89a8f503946ece16d04d3b7ec16 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I Was running in XCP 1.1 for a years, no problem until 2 days a= go.

I have 4 x XCP 1.1 group-in 1 pool, tweak with this guide http://wiki.xen.org/wiki/XenCen= terXCP, storage with iSCSI

- the problem was start at our VM centos 5.8 with cpanel was doing scri= pts/upcp automaticaly, VM centos 5.8 was got high load, so I decide to forc= e reboot.
- In xencenter console show boot was stuck, here few last mess= ages shown:

kjournald starting.= =A0 Commit interval 5 seconds

EXT3-fs: mounted filesystem with order= ed data mode.

Setting up other filesystems.

Setting up new root fs

no f= stab.sys, mounting internal defaults

Switching to new root and runni= ng init.

unmounting old /dev

unmounting old /proc

unmounting old /sys




no process after this c= ondition


- Try to create new VM using centos 5-3 iso , VM worki= ng successfully, but when working yum update it's stuck in process
Updating=A0=A0=A0=A0=A0= =A0 : tzdata=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [=A0 5/627]
=A0U= pdating=A0=A0=A0=A0=A0=A0 : glibc-common=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [=A0 6/6= 27]
process
= top - 05:30:19 up 21 min,=A0 3 users,=A0 load average: 1.04, 1.00, 0.72
= Tasks: 114 total,=A0=A0 2 running, 112 sleeping,=A0=A0 0 stopped,=A0=A0 0 z= ombie
Cpu(s): 16.2%us,=A0 0.0%sy,=A0 0.0%ni, 83.8%id,=A0 0.0%wa,=A0 0.0%hi,=A0 0.= 0%si,=A0 0.0%st
Mem:=A0=A0 4194304k total,=A0=A0 814456k used,=A0 337984= 8k free,=A0=A0=A0 25952k buffers
Swap:=A0 4095992k total,=A0=A0=A0=A0=A0= =A0=A0 0k used,=A0 4095992k free,=A0=A0 531584k cached

=A0PID USER=A0=A0=A0=A0=A0 PR=A0 NI=A0 VIRT=A0 RES=A0 SHR S %CPU %MEM= =A0=A0=A0 TIME+=A0 COMMAND=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
2057 root=A0=A0=A0=A0=A0 25= =A0=A0 0=A0=A0 788=A0 140=A0 108 R 100.0=A0 0.0=A0 19:39.74 build-locale-ar= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
=A0=A0 = 1 root=A0=A0=A0=A0=A0 15=A0=A0 0 10344=A0 732=A0 608 S=A0 0.0=A0 0.0=A0=A0 = 0:00.01 init

# ps ax |grep build
2057 pts/0=A0=A0=A0 R+=A0=A0=A0 20:11 /usr/sbin/= build-locale-archive
2853 pts/1=A0=A0=A0 S+=A0=A0=A0=A0 0:00 grep build<= br>
=A0wait for an few times no clue, and CPU utilization get H= igh until 100%, and if the VM rebooted, will be stuck same at case above.

- In same pool I was download centos 5.9 xva templates from stackle= t, and try to import and start in pool as new VM , but another weird show a= t booting, last message shown are :

en virtual console successfully installed as xvc0
Event-channel device i= nstalled.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
id= e: Assuming 50MHz system bus speed for PIO modes; override with idebus=3Dxx=
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
u= sbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:= USB HID core driver
PNP: No PS/2 controller found. Probing ports directl= y.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mic= e
md: md driver 0.90.3 MAX_MD_DEVS=3D256, MD_SB_DISKS=3D27
md: bitmap= version 4.39
TCP bic registered
Initializing IPsec netlink socket NET: Registered protocol family 1
NET: Registered protocol family 17
= XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no d= river: device/vif/0
Initalizing network drop monitor service
Write pr= otecting the kernel read-only data: 506k
=A0Could somebody help me ????

-
Best Regards,

Adhi Priharmanto

<= /font> --e89a8f503946ece16d04d3b7ec16-- --===============6562387658842608824== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6562387658842608824==-- From xen-api-bounces@lists.xen.org Sun Jan 20 13:00:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 13:00:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwuVX-0002F4-Qt; Sun, 20 Jan 2013 13:00:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwuVW-0002Ez-M8 for xen-api@lists.xen.org; Sun, 20 Jan 2013 13:00:18 +0000 Received: from [85.158.139.83:42707] by server-3.bemta-5.messagelabs.com id 90/B8-15993-16AEBF05; Sun, 20 Jan 2013 13:00:17 +0000 X-Env-Sender: adhi.pri@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1358686814!24369140!1 X-Originating-IP: [209.85.219.46] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8312 invoked from network); 20 Jan 2013 13:00:16 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2013 13:00:16 -0000 Received: by mail-oa0-f46.google.com with SMTP id h16so5286846oag.33 for ; Sun, 20 Jan 2013 05:00:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=OjvxIKHlX1fJVEn+xRMK9IIWzYINgoRkAu4tpf7OS20=; b=bFO34dziBZlvCC6OnqPvpJ8SjZBWsjcYUIowZx8KCwNaeTNNbTXnckh3SBmTGbt5oy 0GsmAbrv7qNKfBvCezLr/f8EQOw1B5bQ+06/sd37eGRIFR7MrRVifL1M+R/xPNzDZks3 s9Dr9ZvyoH8L5slpMI1GAp5fuh7ZiEINUAVak/V2TEypzDS7NW47aRIosUbqqbwyE1zA 71NHFLzBPU5b1TmKVp+ZaqX+FjFpv8olCWNTDW8McoaSg6FwICW6AyxnQgaay+XhAoEY gBGNfyhkKp/qVGw0cIkgsMvut5b7yvU4MjcumlZuXruXIpWMAdZl/anR1Pz8xGaShsR0 HB5A== MIME-Version: 1.0 X-Received: by 10.182.131.101 with SMTP id ol5mr11397230obb.12.1358686814265; Sun, 20 Jan 2013 05:00:14 -0800 (PST) Received: by 10.76.153.33 with HTTP; Sun, 20 Jan 2013 05:00:14 -0800 (PST) Date: Sun, 20 Jan 2013 20:00:14 +0700 Message-ID: From: Adhi Priharmanto To: xen-api@lists.xen.org Subject: [Xen-API] Centos 5.9 can't boot in xcp 1.1 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6562387658842608824==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6562387658842608824== Content-Type: multipart/alternative; boundary=e89a8f503946ece16d04d3b7ec16 --e89a8f503946ece16d04d3b7ec16 Content-Type: text/plain; charset=ISO-8859-1 Hi, I Was running in XCP 1.1 for a years, no problem until 2 days ago. I have 4 x XCP 1.1 group-in 1 pool, tweak with this guide http://wiki.xen.org/wiki/XenCenterXCP, storage with iSCSI - the problem was start at our VM centos 5.8 with cpanel was doing scripts/upcp automaticaly, VM centos 5.8 was got high load, so I decide to force reboot. - In xencenter console show boot was stuck, here few last messages shown: kjournald starting. Commit interval 5 seconds > > EXT3-fs: mounted filesystem with ordered data mode. > > Setting up other filesystems. > > Setting up new root fs > > no fstab.sys, mounting internal defaults > > Switching to new root and running init. > > unmounting old /dev > > unmounting old /proc > > unmounting old /sys > > > > no process after this condition - Try to create new VM using centos 5-3 iso , VM working successfully, but when working yum update it's stuck in process > Updating : tzdata [ 5/627] > Updating : glibc-common [ 6/627] > process > top - 05:30:19 up 21 min, 3 users, load average: 1.04, 1.00, 0.72 > Tasks: 114 total, 2 running, 112 sleeping, 0 stopped, 0 zombie > Cpu(s): 16.2%us, 0.0%sy, 0.0%ni, 83.8%id, 0.0%wa, 0.0%hi, 0.0%si, > 0.0%st > Mem: 4194304k total, 814456k used, 3379848k free, 25952k buffers > Swap: 4095992k total, 0k used, 4095992k free, 531584k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ > COMMAND > 2057 root 25 0 788 140 108 R 100.0 0.0 19:39.74 > build-locale-ar > 1 root 15 0 10344 732 608 S 0.0 0.0 0:00.01 init > > # ps ax |grep build > 2057 pts/0 R+ 20:11 /usr/sbin/build-locale-archive > 2853 pts/1 S+ 0:00 grep build > wait for an few times no clue, and CPU utilization get High until 100%, and if the VM rebooted, will be stuck same at case above. - In same pool I was download centos 5.9 xva templates from stacklet, and try to import and start in pool as new VM , but another weird show at booting, last message shown are : en virtual console successfully installed as xvc0 > Event-channel device installed. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > Initalizing network drop monitor service > Write protecting the kernel read-only data: 506k > Could somebody help me ???? - Best Regards, *Adhi Priharmanto* --e89a8f503946ece16d04d3b7ec16 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I Was running in XCP 1.1 for a years, no problem until 2 days a= go.

I have 4 x XCP 1.1 group-in 1 pool, tweak with this guide http://wiki.xen.org/wiki/XenCen= terXCP, storage with iSCSI

- the problem was start at our VM centos 5.8 with cpanel was doing scri= pts/upcp automaticaly, VM centos 5.8 was got high load, so I decide to forc= e reboot.
- In xencenter console show boot was stuck, here few last mess= ages shown:

kjournald starting.= =A0 Commit interval 5 seconds

EXT3-fs: mounted filesystem with order= ed data mode.

Setting up other filesystems.

Setting up new root fs

no f= stab.sys, mounting internal defaults

Switching to new root and runni= ng init.

unmounting old /dev

unmounting old /proc

unmounting old /sys




no process after this c= ondition


- Try to create new VM using centos 5-3 iso , VM worki= ng successfully, but when working yum update it's stuck in process
Updating=A0=A0=A0=A0=A0= =A0 : tzdata=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [=A0 5/627]
=A0U= pdating=A0=A0=A0=A0=A0=A0 : glibc-common=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [=A0 6/6= 27]
process
= top - 05:30:19 up 21 min,=A0 3 users,=A0 load average: 1.04, 1.00, 0.72
= Tasks: 114 total,=A0=A0 2 running, 112 sleeping,=A0=A0 0 stopped,=A0=A0 0 z= ombie
Cpu(s): 16.2%us,=A0 0.0%sy,=A0 0.0%ni, 83.8%id,=A0 0.0%wa,=A0 0.0%hi,=A0 0.= 0%si,=A0 0.0%st
Mem:=A0=A0 4194304k total,=A0=A0 814456k used,=A0 337984= 8k free,=A0=A0=A0 25952k buffers
Swap:=A0 4095992k total,=A0=A0=A0=A0=A0= =A0=A0 0k used,=A0 4095992k free,=A0=A0 531584k cached

=A0PID USER=A0=A0=A0=A0=A0 PR=A0 NI=A0 VIRT=A0 RES=A0 SHR S %CPU %MEM= =A0=A0=A0 TIME+=A0 COMMAND=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
2057 root=A0=A0=A0=A0=A0 25= =A0=A0 0=A0=A0 788=A0 140=A0 108 R 100.0=A0 0.0=A0 19:39.74 build-locale-ar= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
=A0=A0 = 1 root=A0=A0=A0=A0=A0 15=A0=A0 0 10344=A0 732=A0 608 S=A0 0.0=A0 0.0=A0=A0 = 0:00.01 init

# ps ax |grep build
2057 pts/0=A0=A0=A0 R+=A0=A0=A0 20:11 /usr/sbin/= build-locale-archive
2853 pts/1=A0=A0=A0 S+=A0=A0=A0=A0 0:00 grep build<= br>
=A0wait for an few times no clue, and CPU utilization get H= igh until 100%, and if the VM rebooted, will be stuck same at case above.

- In same pool I was download centos 5.9 xva templates from stackle= t, and try to import and start in pool as new VM , but another weird show a= t booting, last message shown are :

en virtual console successfully installed as xvc0
Event-channel device i= nstalled.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
id= e: Assuming 50MHz system bus speed for PIO modes; override with idebus=3Dxx=
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
u= sbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:= USB HID core driver
PNP: No PS/2 controller found. Probing ports directl= y.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mic= e
md: md driver 0.90.3 MAX_MD_DEVS=3D256, MD_SB_DISKS=3D27
md: bitmap= version 4.39
TCP bic registered
Initializing IPsec netlink socket NET: Registered protocol family 1
NET: Registered protocol family 17
= XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no d= river: device/vif/0
Initalizing network drop monitor service
Write pr= otecting the kernel read-only data: 506k
=A0Could somebody help me ????

-
Best Regards,

Adhi Priharmanto

<= /font> --e89a8f503946ece16d04d3b7ec16-- --===============6562387658842608824== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6562387658842608824==-- From xen-api-bounces@lists.xen.org Sun Jan 20 15:17:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 15:17:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwweW-00067v-Fd; Sun, 20 Jan 2013 15:17:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwweU-00067q-8W for xen-api@lists.xen.org; Sun, 20 Jan 2013 15:17:42 +0000 Received: from [85.158.143.35:57282] by server-1.bemta-4.messagelabs.com id 42/0A-05635-59A0CF05; Sun, 20 Jan 2013 15:17:41 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1358695060!15122945!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 513 invoked from network); 20 Jan 2013 15:17:40 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2013 15:17:40 -0000 Received: by mail-la0-f42.google.com with SMTP id fe20so5341208lab.1 for ; Sun, 20 Jan 2013 07:17:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=NF1eEV5LilgkhtHB0hFWdDZf567yjKo+Gm26uOqxn4g=; b=xCyc/4FhONIwsFqmULKXNupRonXDJxQ6/EHsEI8mtKWI4jAA1NXbbmMcLTQXCn8ITp 5hGJ4DE+YxvF17tO14YBvErNxQagG94UczstbCXDMaZFWi6TksWauKFtDHVTlMBSXMAh 02i3ih2nGKUmcX8s8Wc9ywrp4+jDKH2kBtlRdZjAP87dK3AovFHuIdEf328pw6sQgQpO KEUOjCo1NGtltmd55Ys3xKrie6nhEaN31bewH2pyDqjeAR0O8XYzLU+kbU5pvKhgJYfT rRbqTy5TrMMnUAH67G79X/39pMNR3JdRV+O7kmWP0vqn9pcKSBXhHqNQhC54wa0Cdvdq I7rA== X-Received: by 10.112.29.229 with SMTP id n5mr6524456lbh.130.1358695060076; Sun, 20 Jan 2013 07:17:40 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id z4sm4225783lbn.17.2013.01.20.07.17.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Jan 2013 07:17:39 -0800 (PST) Message-ID: <50FC0A92.90203@gmail.com> Date: Sun, 20 Jan 2013 19:17:38 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <3371CE47-8A8A-42AA-B71F-59CFD714B593@bloudraak.com> In-Reply-To: <3371CE47-8A8A-42AA-B71F-59CFD714B593@bloudraak.com> Subject: Re: [Xen-API] Running OS X 10.8 as a guest in XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I think main problem is that mac os X don't want to work on S3 video graphics ATA PIIXE adapter and nec 2000 network card (this is the stuff XCP emulates for guests by qemu). ... And that question is better to address to Apple: why Mac OS X don't want to run on commodity hardware every other sane OS can run? On 20.01.2013 05:54, Werner Strydom wrote: > Hello, > > I installed XCP using the ISO image on a Mac Mini without any problems other > than blessing the hard disk. The Mac Mini has a model identifier of > "macmini6,2". As I'm typing this, it runs Ubuntu 12.04 and Windows Server > 2012 without any problems. > > I wouldn't mind to spend some time to see if I can get OS X 10.8, OS X 10.7 > and OS X 10.6 running. The fact that it is not supported isn't a problem. At > this point I'm stuck with two issues: > > - Boot OS X Mountain Lion from ISO inside XCP > > - Displaying graphics when OS X boots up > > I converted the InstallESD.dmg to an ISO. However, creating a virtual > machine in XCP and booting from the ISO I get an error "failure: could not > read boot disk". I can use the same ISO to create OS X 10.8 virtual > machines in ESXi, Parallels, VMware Fusion without much hassle. > > So I tried to boot from the USB recovery disk. This time I get a message > "Boot Device: Hard Drive - success", however, no graphics is displayed. > Looking at CPU and network usage, something is happening in that CPU usage > is 100% for a couple of minutes, and network usage indicates something is > being downloaded. This consistent with when the recovery agent is running > on my Mac and preparing for recovery by downloading stuff from the > internet. > > From what I'm gathering this may be related to support for EFI, but > I can't be sure. > > Before we digress by discussing legal implications of doing this, > I am running this on Apple hardware and have server licenses for > OS X Snow Leopard. > > I'd appreciate any help. > > Thanks, > Werner > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 20 15:17:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 15:17:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwweW-00067v-Fd; Sun, 20 Jan 2013 15:17:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TwweU-00067q-8W for xen-api@lists.xen.org; Sun, 20 Jan 2013 15:17:42 +0000 Received: from [85.158.143.35:57282] by server-1.bemta-4.messagelabs.com id 42/0A-05635-59A0CF05; Sun, 20 Jan 2013 15:17:41 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1358695060!15122945!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 513 invoked from network); 20 Jan 2013 15:17:40 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2013 15:17:40 -0000 Received: by mail-la0-f42.google.com with SMTP id fe20so5341208lab.1 for ; Sun, 20 Jan 2013 07:17:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=NF1eEV5LilgkhtHB0hFWdDZf567yjKo+Gm26uOqxn4g=; b=xCyc/4FhONIwsFqmULKXNupRonXDJxQ6/EHsEI8mtKWI4jAA1NXbbmMcLTQXCn8ITp 5hGJ4DE+YxvF17tO14YBvErNxQagG94UczstbCXDMaZFWi6TksWauKFtDHVTlMBSXMAh 02i3ih2nGKUmcX8s8Wc9ywrp4+jDKH2kBtlRdZjAP87dK3AovFHuIdEf328pw6sQgQpO KEUOjCo1NGtltmd55Ys3xKrie6nhEaN31bewH2pyDqjeAR0O8XYzLU+kbU5pvKhgJYfT rRbqTy5TrMMnUAH67G79X/39pMNR3JdRV+O7kmWP0vqn9pcKSBXhHqNQhC54wa0Cdvdq I7rA== X-Received: by 10.112.29.229 with SMTP id n5mr6524456lbh.130.1358695060076; Sun, 20 Jan 2013 07:17:40 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id z4sm4225783lbn.17.2013.01.20.07.17.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Jan 2013 07:17:39 -0800 (PST) Message-ID: <50FC0A92.90203@gmail.com> Date: Sun, 20 Jan 2013 19:17:38 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <3371CE47-8A8A-42AA-B71F-59CFD714B593@bloudraak.com> In-Reply-To: <3371CE47-8A8A-42AA-B71F-59CFD714B593@bloudraak.com> Subject: Re: [Xen-API] Running OS X 10.8 as a guest in XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I think main problem is that mac os X don't want to work on S3 video graphics ATA PIIXE adapter and nec 2000 network card (this is the stuff XCP emulates for guests by qemu). ... And that question is better to address to Apple: why Mac OS X don't want to run on commodity hardware every other sane OS can run? On 20.01.2013 05:54, Werner Strydom wrote: > Hello, > > I installed XCP using the ISO image on a Mac Mini without any problems other > than blessing the hard disk. The Mac Mini has a model identifier of > "macmini6,2". As I'm typing this, it runs Ubuntu 12.04 and Windows Server > 2012 without any problems. > > I wouldn't mind to spend some time to see if I can get OS X 10.8, OS X 10.7 > and OS X 10.6 running. The fact that it is not supported isn't a problem. At > this point I'm stuck with two issues: > > - Boot OS X Mountain Lion from ISO inside XCP > > - Displaying graphics when OS X boots up > > I converted the InstallESD.dmg to an ISO. However, creating a virtual > machine in XCP and booting from the ISO I get an error "failure: could not > read boot disk". I can use the same ISO to create OS X 10.8 virtual > machines in ESXi, Parallels, VMware Fusion without much hassle. > > So I tried to boot from the USB recovery disk. This time I get a message > "Boot Device: Hard Drive - success", however, no graphics is displayed. > Looking at CPU and network usage, something is happening in that CPU usage > is 100% for a couple of minutes, and network usage indicates something is > being downloaded. This consistent with when the recovery agent is running > on my Mac and preparing for recovery by downloading stuff from the > internet. > > From what I'm gathering this may be related to support for EFI, but > I can't be sure. > > Before we digress by discussing legal implications of doing this, > I am running this on Apple hardware and have server licenses for > OS X Snow Leopard. > > I'd appreciate any help. > > Thanks, > Werner > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 20 15:20:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 15:20:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twwgi-0006Bk-Pz; Sun, 20 Jan 2013 15:20:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twwgh-0006Bb-EO for xen-api@lists.xen.org; Sun, 20 Jan 2013 15:19:59 +0000 Received: from [85.158.138.51:55980] by server-10.bemta-3.messagelabs.com id 6F/51-09363-E1B0CF05; Sun, 20 Jan 2013 15:19:58 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1358695196!28840338!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15735 invoked from network); 20 Jan 2013 15:19:57 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2013 15:19:57 -0000 Received: by mail-lb0-f172.google.com with SMTP id n8so2049185lbj.3 for ; Sun, 20 Jan 2013 07:19:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=WMUvWxCdDKtp/OncjWMb8sh1N4WbAGHNmsExdw5JKnw=; b=ZSD0ii58X8o5o05J116qHle7YuP9xJRR7xHCRJR77QtxUcgCl+1ukoauVd8oz71/p0 XTP1nK/BkuviLfRxpsbJdpzumqkaB+ci4l3WMMNXw4JPbXE3cjJxCo3998DNsoaHbdza dO39aCCAuq3fPXcVusnQR8yArvLSBiW9o+Kyi1FR8CDGUgCGoF5VH2OQgFJ3A2uMi8bz 7OikeIJtmUDttGP26Fnw/oQW2XNxZDslTUsd7XQfd02vayF2t9+StM4aUorp35/p2anb LeDSvccOatJTW+7Ir4mnOXbWmwuqMIx+oeCIgbD3L2mwLHlpJjhFziymFhy73tFhgazW K+eQ== X-Received: by 10.152.109.176 with SMTP id ht16mr14677572lab.2.1358695196705; Sun, 20 Jan 2013 07:19:56 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id o2sm4234016lby.11.2013.01.20.07.19.56 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Jan 2013 07:19:56 -0800 (PST) Message-ID: <50FC0B1B.1070809@gmail.com> Date: Sun, 20 Jan 2013 19:19:55 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] Centos 5.9 can't boot in xcp 1.1 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5469717212080083985==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5469717212080083985== Content-Type: multipart/alternative; boundary="------------010207060200040401010401" This is a multi-part message in MIME format. --------------010207060200040401010401 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Too few information (something broken, someone help me). Some gotchas: * check dom0 free space. If no free space, delete some logs and restart xapi service. * check SR state * check xapi task queue (xe task-list), should be empty. On 20.01.2013 17:00, Adhi Priharmanto wrote: > Hi, > > I Was running in XCP 1.1 for a years, no problem until 2 days ago. > > I have 4 x XCP 1.1 group-in 1 pool, tweak with this guide > http://wiki.xen.org/wiki/XenCenterXCP, storage with iSCSI > > - the problem was start at our VM centos 5.8 with cpanel was doing > scripts/upcp automaticaly, VM centos 5.8 was got high load, so I > decide to force reboot. > - In xencenter console show boot was stuck, here few last messages shown: > > kjournald starting. Commit interval 5 seconds > > EXT3-fs: mounted filesystem with ordered data mode. > > Setting up other filesystems. > > Setting up new root fs > > no fstab.sys, mounting internal defaults > > Switching to new root and running init. > > unmounting old /dev > > unmounting old /proc > > unmounting old /sys > > > > > no process after this condition > > > - Try to create new VM using centos 5-3 iso , VM working successfully, > but when working yum update it's stuck in process > > Updating : tzdata [ > 5/627] > Updating : glibc-common [ > 6/627] > > process > > top - 05:30:19 up 21 min, 3 users, load average: 1.04, 1.00, 0.72 > Tasks: 114 total, 2 running, 112 sleeping, 0 stopped, 0 zombie > Cpu(s): 16.2%us, 0.0%sy, 0.0%ni, 83.8%id, 0.0%wa, 0.0%hi, > 0.0%si, 0.0%st > Mem: 4194304k total, 814456k used, 3379848k free, 25952k > buffers > Swap: 4095992k total, 0k used, 4095992k free, 531584k > cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 2057 root 25 0 788 140 108 R 100.0 0.0 19:39.74 > build-locale-ar > 1 root 15 0 10344 732 608 S 0.0 0.0 0:00.01 init > > # ps ax |grep build > 2057 pts/0 R+ 20:11 /usr/sbin/build-locale-archive > 2853 pts/1 S+ 0:00 grep build > > wait for an few times no clue, and CPU utilization get High until > 100%, and if the VM rebooted, will be stuck same at case above. > > > - In same pool I was download centos 5.9 xva templates from stacklet, > and try to import and start in pool as new VM , but another weird show > at booting, last message shown are : > > en virtual console successfully installed as xvc0 > Event-channel device installed. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > Initalizing network drop monitor service > Write protecting the kernel read-only data: 506k > > Could somebody help me ???? > > - > Best Regards, > > *Adhi Priharmanto* > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------010207060200040401010401 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Too few information (something broken, someone help me).

Some gotchas:
* check dom0 free space. If no free space, delete some logs and restart xapi service.
* check SR state
* check xapi task queue (xe task-list), should be empty.

On 20.01.2013 17:00, Adhi Priharmanto wrote:
Hi,

I Was running in XCP 1.1 for a years, no problem until 2 days ago.

I have 4 x XCP 1.1 group-in 1 pool, tweak with this guide http://wiki.xen.org/wiki/XenCenterXCP, storage with iSCSI

- the problem was start at our VM centos 5.8 with cpanel was doing scripts/upcp automaticaly, VM centos 5.8 was got high load, so I decide to force reboot.
- In xencenter console show boot was stuck, here few last messages shown:

kjournald starting.  Commit interval 5 seconds

EXT3-fs: mounted filesystem with ordered data mode.

Setting up other filesystems.

Setting up new root fs

no fstab.sys, mounting internal defaults

Switching to new root and running init.

unmounting old /dev

unmounting old /proc

unmounting old /sys




no process after this condition


- Try to create new VM using centos 5-3 iso , VM working successfully, but when working yum update it's stuck in process
Updating       : tzdata                                        [  5/627]
 Updating       : glibc-common                                  [  6/627]
process
top - 05:30:19 up 21 min,  3 users,  load average: 1.04, 1.00, 0.72
Tasks: 114 total,   2 running, 112 sleeping,   0 stopped,   0 zombie
Cpu(s): 16.2%us,  0.0%sy,  0.0%ni, 83.8%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   4194304k total,   814456k used,  3379848k free,    25952k buffers
Swap:  4095992k total,        0k used,  4095992k free,   531584k cached

 PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                              
2057 root      25   0   788  140  108 R 100.0  0.0  19:39.74 build-locale-ar                     
   1 root      15   0 10344  732  608 S  0.0  0.0   0:00.01 init

# ps ax |grep build
2057 pts/0    R+    20:11 /usr/sbin/build-locale-archive
2853 pts/1    S+     0:00 grep build
 wait for an few times no clue, and CPU utilization get High until 100%, and if the VM rebooted, will be stuck same at case above.


- In same pool I was download centos 5.9 xva templates from stacklet, and try to import and start in pool as new VM , but another weird show at booting, last message shown are :

en virtual console successfully installed as xvc0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
Initalizing network drop monitor service
Write protecting the kernel read-only data: 506k
 Could somebody help me ????

-
Best Regards,

Adhi Priharmanto

 

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------010207060200040401010401-- --===============5469717212080083985== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5469717212080083985==-- From xen-api-bounces@lists.xen.org Sun Jan 20 15:20:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 15:20:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twwgi-0006Bk-Pz; Sun, 20 Jan 2013 15:20:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twwgh-0006Bb-EO for xen-api@lists.xen.org; Sun, 20 Jan 2013 15:19:59 +0000 Received: from [85.158.138.51:55980] by server-10.bemta-3.messagelabs.com id 6F/51-09363-E1B0CF05; Sun, 20 Jan 2013 15:19:58 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1358695196!28840338!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15735 invoked from network); 20 Jan 2013 15:19:57 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2013 15:19:57 -0000 Received: by mail-lb0-f172.google.com with SMTP id n8so2049185lbj.3 for ; Sun, 20 Jan 2013 07:19:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=WMUvWxCdDKtp/OncjWMb8sh1N4WbAGHNmsExdw5JKnw=; b=ZSD0ii58X8o5o05J116qHle7YuP9xJRR7xHCRJR77QtxUcgCl+1ukoauVd8oz71/p0 XTP1nK/BkuviLfRxpsbJdpzumqkaB+ci4l3WMMNXw4JPbXE3cjJxCo3998DNsoaHbdza dO39aCCAuq3fPXcVusnQR8yArvLSBiW9o+Kyi1FR8CDGUgCGoF5VH2OQgFJ3A2uMi8bz 7OikeIJtmUDttGP26Fnw/oQW2XNxZDslTUsd7XQfd02vayF2t9+StM4aUorp35/p2anb LeDSvccOatJTW+7Ir4mnOXbWmwuqMIx+oeCIgbD3L2mwLHlpJjhFziymFhy73tFhgazW K+eQ== X-Received: by 10.152.109.176 with SMTP id ht16mr14677572lab.2.1358695196705; Sun, 20 Jan 2013 07:19:56 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id o2sm4234016lby.11.2013.01.20.07.19.56 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Jan 2013 07:19:56 -0800 (PST) Message-ID: <50FC0B1B.1070809@gmail.com> Date: Sun, 20 Jan 2013 19:19:55 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] Centos 5.9 can't boot in xcp 1.1 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5469717212080083985==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5469717212080083985== Content-Type: multipart/alternative; boundary="------------010207060200040401010401" This is a multi-part message in MIME format. --------------010207060200040401010401 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Too few information (something broken, someone help me). Some gotchas: * check dom0 free space. If no free space, delete some logs and restart xapi service. * check SR state * check xapi task queue (xe task-list), should be empty. On 20.01.2013 17:00, Adhi Priharmanto wrote: > Hi, > > I Was running in XCP 1.1 for a years, no problem until 2 days ago. > > I have 4 x XCP 1.1 group-in 1 pool, tweak with this guide > http://wiki.xen.org/wiki/XenCenterXCP, storage with iSCSI > > - the problem was start at our VM centos 5.8 with cpanel was doing > scripts/upcp automaticaly, VM centos 5.8 was got high load, so I > decide to force reboot. > - In xencenter console show boot was stuck, here few last messages shown: > > kjournald starting. Commit interval 5 seconds > > EXT3-fs: mounted filesystem with ordered data mode. > > Setting up other filesystems. > > Setting up new root fs > > no fstab.sys, mounting internal defaults > > Switching to new root and running init. > > unmounting old /dev > > unmounting old /proc > > unmounting old /sys > > > > > no process after this condition > > > - Try to create new VM using centos 5-3 iso , VM working successfully, > but when working yum update it's stuck in process > > Updating : tzdata [ > 5/627] > Updating : glibc-common [ > 6/627] > > process > > top - 05:30:19 up 21 min, 3 users, load average: 1.04, 1.00, 0.72 > Tasks: 114 total, 2 running, 112 sleeping, 0 stopped, 0 zombie > Cpu(s): 16.2%us, 0.0%sy, 0.0%ni, 83.8%id, 0.0%wa, 0.0%hi, > 0.0%si, 0.0%st > Mem: 4194304k total, 814456k used, 3379848k free, 25952k > buffers > Swap: 4095992k total, 0k used, 4095992k free, 531584k > cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 2057 root 25 0 788 140 108 R 100.0 0.0 19:39.74 > build-locale-ar > 1 root 15 0 10344 732 608 S 0.0 0.0 0:00.01 init > > # ps ax |grep build > 2057 pts/0 R+ 20:11 /usr/sbin/build-locale-archive > 2853 pts/1 S+ 0:00 grep build > > wait for an few times no clue, and CPU utilization get High until > 100%, and if the VM rebooted, will be stuck same at case above. > > > - In same pool I was download centos 5.9 xva templates from stacklet, > and try to import and start in pool as new VM , but another weird show > at booting, last message shown are : > > en virtual console successfully installed as xvc0 > Event-channel device installed. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > Initalizing network drop monitor service > Write protecting the kernel read-only data: 506k > > Could somebody help me ???? > > - > Best Regards, > > *Adhi Priharmanto* > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------010207060200040401010401 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Too few information (something broken, someone help me).

Some gotchas:
* check dom0 free space. If no free space, delete some logs and restart xapi service.
* check SR state
* check xapi task queue (xe task-list), should be empty.

On 20.01.2013 17:00, Adhi Priharmanto wrote:
Hi,

I Was running in XCP 1.1 for a years, no problem until 2 days ago.

I have 4 x XCP 1.1 group-in 1 pool, tweak with this guide http://wiki.xen.org/wiki/XenCenterXCP, storage with iSCSI

- the problem was start at our VM centos 5.8 with cpanel was doing scripts/upcp automaticaly, VM centos 5.8 was got high load, so I decide to force reboot.
- In xencenter console show boot was stuck, here few last messages shown:

kjournald starting.  Commit interval 5 seconds

EXT3-fs: mounted filesystem with ordered data mode.

Setting up other filesystems.

Setting up new root fs

no fstab.sys, mounting internal defaults

Switching to new root and running init.

unmounting old /dev

unmounting old /proc

unmounting old /sys




no process after this condition


- Try to create new VM using centos 5-3 iso , VM working successfully, but when working yum update it's stuck in process
Updating       : tzdata                                        [  5/627]
 Updating       : glibc-common                                  [  6/627]
process
top - 05:30:19 up 21 min,  3 users,  load average: 1.04, 1.00, 0.72
Tasks: 114 total,   2 running, 112 sleeping,   0 stopped,   0 zombie
Cpu(s): 16.2%us,  0.0%sy,  0.0%ni, 83.8%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   4194304k total,   814456k used,  3379848k free,    25952k buffers
Swap:  4095992k total,        0k used,  4095992k free,   531584k cached

 PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                              
2057 root      25   0   788  140  108 R 100.0  0.0  19:39.74 build-locale-ar                     
   1 root      15   0 10344  732  608 S  0.0  0.0   0:00.01 init

# ps ax |grep build
2057 pts/0    R+    20:11 /usr/sbin/build-locale-archive
2853 pts/1    S+     0:00 grep build
 wait for an few times no clue, and CPU utilization get High until 100%, and if the VM rebooted, will be stuck same at case above.


- In same pool I was download centos 5.9 xva templates from stacklet, and try to import and start in pool as new VM , but another weird show at booting, last message shown are :

en virtual console successfully installed as xvc0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
Initalizing network drop monitor service
Write protecting the kernel read-only data: 506k
 Could somebody help me ????

-
Best Regards,

Adhi Priharmanto

 

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------010207060200040401010401-- --===============5469717212080083985== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5469717212080083985==-- From xen-api-bounces@lists.xen.org Sun Jan 20 18:43:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 18:43:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twzrx-0002ls-FP; Sun, 20 Jan 2013 18:43:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twzrw-0002ln-5g for xen-api@lists.xen.org; Sun, 20 Jan 2013 18:43:48 +0000 Received: from [85.158.143.99:8666] by server-2.bemta-4.messagelabs.com id 1D/CA-03518-3EA3CF05; Sun, 20 Jan 2013 18:43:47 +0000 X-Env-Sender: nathanbr@distributel.net X-Msg-Ref: server-6.tower-216.messagelabs.com!1358707424!21696440!1 X-Originating-IP: [208.68.17.94] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29344 invoked from network); 20 Jan 2013 18:43:46 -0000 Received: from mx3.edtmtds.thinktel.ca (HELO mx3.edtmtds.thinktel.ca) (208.68.17.94) by server-6.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Jan 2013 18:43:46 -0000 Received: from localhost (sa4.edtmtds.thinktel.ca [208.68.17.77]) by mx3.edtmtds.thinktel.ca (Postfix) with ESMTP id BC94B24B25; Sun, 20 Jan 2013 11:43:43 -0700 (MST) X-Virus-Scanned: Debian amavisd-new at sa4.edmtds.thinktel.ca Received: from mx3.edtmtds.thinktel.ca ([208.68.17.94]) by localhost (sa4.edtmtds.thinktel.ca [208.68.17.77]) (amavisd-new, port 10024) with ESMTP id g1K406QDWHvc; Sun, 20 Jan 2013 11:43:41 -0700 (MST) Received: from Serveur (216-246-238-210.cpe.distributel.net [216.246.238.210]) by mx3.edtmtds.thinktel.ca (Postfix) with ESMTP id 0A77E24B2C; Sun, 20 Jan 2013 11:43:40 -0700 (MST) From: "Nat" To: , References: <3371CE47-8A8A-42AA-B71F-59CFD714B593@bloudraak.com> <50FC0A92.90203@gmail.com> In-Reply-To: <50FC0A92.90203@gmail.com> Date: Sun, 20 Jan 2013 13:43:38 -0500 Message-ID: <000c01cdf73e$106c2bd0$31448370$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac33IXCtX28Xnyn/RRe5lOwzn2iEUwAG8oEQ Content-Language: fr-ca Subject: Re: [Xen-API] Running OS X 10.8 as a guest in XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Years ago I success running a Mac OS X 10.6 Server into a XenServer VM. First I had install this VM with VirtualBox and then import it into XenServer/XCP You got to boot it with special bootloader or with a hackmod iso.. The only thing that not working was the mouse. So I first install any remote software like Teamviewer to control the VM. Hope this can help. Good Luck. -----Message d'origine----- De=A0: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org]= De la part de George Shuklin Envoy=E9=A0: 20 janvier 2013 10:18 =C0=A0: xen-api@lists.xen.org Objet=A0: Re: [Xen-API] Running OS X 10.8 as a guest in XCP I think main problem is that mac os X don't want to work on S3 video = graphics ATA PIIXE adapter and nec 2000 network card (this is the stuff = XCP emulates for guests by qemu). ... And that question is better to address to Apple: why Mac OS X don't = want to run on commodity hardware every other sane OS can run? On 20.01.2013 05:54, Werner Strydom wrote: > Hello, > > I installed XCP using the ISO image on a Mac Mini without any problems other > than blessing the hard disk. The Mac Mini has a model identifier of > "macmini6,2". As I'm typing this, it runs Ubuntu 12.04 and Windows Server > 2012 without any problems. > > I wouldn't mind to spend some time to see if I can get OS X 10.8, OS X 10.7 > and OS X 10.6 running. The fact that it is not supported isn't a problem. At > this point I'm stuck with two issues: > > - Boot OS X Mountain Lion from ISO inside XCP > > - Displaying graphics when OS X boots up > > I converted the InstallESD.dmg to an ISO. However, creating a virtual > machine in XCP and booting from the ISO I get an error "failure: could not > read boot disk". I can use the same ISO to create OS X 10.8 virtual > machines in ESXi, Parallels, VMware Fusion without much hassle. > > So I tried to boot from the USB recovery disk. This time I get a message > "Boot Device: Hard Drive - success", however, no graphics is displayed. > Looking at CPU and network usage, something is happening in that CPU usage > is 100% for a couple of minutes, and network usage indicates something is > being downloaded. This consistent with when the recovery agent is running > on my Mac and preparing for recovery by downloading stuff from the > internet. > > From what I'm gathering this may be related to support for EFI, but > I can't be sure. > > Before we digress by discussing legal implications of doing this, > I am running this on Apple hardware and have server licenses for > OS X Snow Leopard. > > I'd appreciate any help. > > Thanks, > Werner > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 20 18:43:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 20 Jan 2013 18:43:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twzrx-0002ls-FP; Sun, 20 Jan 2013 18:43:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Twzrw-0002ln-5g for xen-api@lists.xen.org; Sun, 20 Jan 2013 18:43:48 +0000 Received: from [85.158.143.99:8666] by server-2.bemta-4.messagelabs.com id 1D/CA-03518-3EA3CF05; Sun, 20 Jan 2013 18:43:47 +0000 X-Env-Sender: nathanbr@distributel.net X-Msg-Ref: server-6.tower-216.messagelabs.com!1358707424!21696440!1 X-Originating-IP: [208.68.17.94] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29344 invoked from network); 20 Jan 2013 18:43:46 -0000 Received: from mx3.edtmtds.thinktel.ca (HELO mx3.edtmtds.thinktel.ca) (208.68.17.94) by server-6.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Jan 2013 18:43:46 -0000 Received: from localhost (sa4.edtmtds.thinktel.ca [208.68.17.77]) by mx3.edtmtds.thinktel.ca (Postfix) with ESMTP id BC94B24B25; Sun, 20 Jan 2013 11:43:43 -0700 (MST) X-Virus-Scanned: Debian amavisd-new at sa4.edmtds.thinktel.ca Received: from mx3.edtmtds.thinktel.ca ([208.68.17.94]) by localhost (sa4.edtmtds.thinktel.ca [208.68.17.77]) (amavisd-new, port 10024) with ESMTP id g1K406QDWHvc; Sun, 20 Jan 2013 11:43:41 -0700 (MST) Received: from Serveur (216-246-238-210.cpe.distributel.net [216.246.238.210]) by mx3.edtmtds.thinktel.ca (Postfix) with ESMTP id 0A77E24B2C; Sun, 20 Jan 2013 11:43:40 -0700 (MST) From: "Nat" To: , References: <3371CE47-8A8A-42AA-B71F-59CFD714B593@bloudraak.com> <50FC0A92.90203@gmail.com> In-Reply-To: <50FC0A92.90203@gmail.com> Date: Sun, 20 Jan 2013 13:43:38 -0500 Message-ID: <000c01cdf73e$106c2bd0$31448370$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac33IXCtX28Xnyn/RRe5lOwzn2iEUwAG8oEQ Content-Language: fr-ca Subject: Re: [Xen-API] Running OS X 10.8 as a guest in XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Years ago I success running a Mac OS X 10.6 Server into a XenServer VM. First I had install this VM with VirtualBox and then import it into XenServer/XCP You got to boot it with special bootloader or with a hackmod iso.. The only thing that not working was the mouse. So I first install any remote software like Teamviewer to control the VM. Hope this can help. Good Luck. -----Message d'origine----- De=A0: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org]= De la part de George Shuklin Envoy=E9=A0: 20 janvier 2013 10:18 =C0=A0: xen-api@lists.xen.org Objet=A0: Re: [Xen-API] Running OS X 10.8 as a guest in XCP I think main problem is that mac os X don't want to work on S3 video = graphics ATA PIIXE adapter and nec 2000 network card (this is the stuff = XCP emulates for guests by qemu). ... And that question is better to address to Apple: why Mac OS X don't = want to run on commodity hardware every other sane OS can run? On 20.01.2013 05:54, Werner Strydom wrote: > Hello, > > I installed XCP using the ISO image on a Mac Mini without any problems other > than blessing the hard disk. The Mac Mini has a model identifier of > "macmini6,2". As I'm typing this, it runs Ubuntu 12.04 and Windows Server > 2012 without any problems. > > I wouldn't mind to spend some time to see if I can get OS X 10.8, OS X 10.7 > and OS X 10.6 running. The fact that it is not supported isn't a problem. At > this point I'm stuck with two issues: > > - Boot OS X Mountain Lion from ISO inside XCP > > - Displaying graphics when OS X boots up > > I converted the InstallESD.dmg to an ISO. However, creating a virtual > machine in XCP and booting from the ISO I get an error "failure: could not > read boot disk". I can use the same ISO to create OS X 10.8 virtual > machines in ESXi, Parallels, VMware Fusion without much hassle. > > So I tried to boot from the USB recovery disk. This time I get a message > "Boot Device: Hard Drive - success", however, no graphics is displayed. > Looking at CPU and network usage, something is happening in that CPU usage > is 100% for a couple of minutes, and network usage indicates something is > being downloaded. This consistent with when the recovery agent is running > on my Mac and preparing for recovery by downloading stuff from the > internet. > > From what I'm gathering this may be related to support for EFI, but > I can't be sure. > > Before we digress by discussing legal implications of doing this, > I am running this on Apple hardware and have server licenses for > OS X Snow Leopard. > > I'd appreciate any help. > > Thanks, > Werner > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 21 06:45:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 06:45:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxB7v-0006A8-15; Mon, 21 Jan 2013 06:45:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxB7t-0006A3-RH for xen-api@lists.xen.org; Mon, 21 Jan 2013 06:45:02 +0000 Received: from [193.109.254.147:60288] by server-6.bemta-14.messagelabs.com id 99/1D-23901-8E3ECF05; Mon, 21 Jan 2013 06:44:56 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-3.tower-27.messagelabs.com!1358750687!9612110!1 X-Originating-IP: [94.100.177.110] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21128 invoked from network); 21 Jan 2013 06:44:48 -0000 Received: from smtp50.i.mail.ru (HELO smtp50.i.mail.ru) (94.100.177.110) by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Jan 2013 06:44:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=LTeULDovyG4xR+XgnYTM4411YQFjeykItowgZtlFddY=; b=FTGRS6o3q7eaRr2NQQidA9cQbs2sBzcCRSbYqramLwcvDG1O6io4n0m8kGxQIaADgPPMYynySqUin4xHxTcS+gXQik5YFrV9j7v5EdjzM6elN6SwugO6ggdK+fsCeoXKclaosg2lR1k//2O14iuY8rPqKUOCWKxrdsCgaKRDItM=; Received: from [78.36.60.25] (port=50508 helo=[10.168.2.113]) by smtp50.i.mail.ru with esmtpa (envelope-from ) id 1TxB7f-0005SB-1p; Mon, 21 Jan 2013 10:44:47 +0400 Message-ID: <50FCE3DD.1050403@bk.ru> Date: Mon, 21 Jan 2013 10:44:45 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <50F92D7E.50908@bk.ru> <50F94796.1080907@gmail.com> In-Reply-To: <50F94796.1080907@gmail.com> X-Spam: Not detected X-Mras: Ok Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xcp-xapi antispoof and QoS support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8sCgpUcnlpbmcgdG8gZGViaWFuaXplIGxjbS10YW1wYSBicmFuY2ggYW5kIGdldHRpbmcg Y29tcGlsZSBlcnJvcnMsIApzdWNlc3NmdWxseSBwb3J0ZWQgZXhpc3RlZCBkZWJpYW4vcGF0Y2hl cywgYnV0IGdldHRpbmcgZXJyb3Igd2hpbGUgCmNvbXBpbGluZzoKCi0tLSBDaGVja2luZyBmb3Ig b2NhbWxmaW5kLi4uIChmb3VuZCAvdXNyL2Jpbi9vY2FtbGZpbmQpCi0tLSBDaGVja2luZyBmb3Ig b2NhbWxjLm9wdC4uLiAoZm91bmQgL3Vzci9iaW4vb2NhbWxjLm9wdCkKLS0tIENoZWNraW5nIGZv ciBvY2FtbG9wdC5vcHQuLi4gKGZvdW5kIC91c3IvYmluL29jYW1sb3B0Lm9wdCkKLS0tIENoZWNr aW5nIHdoZXRoZXIgb2NhbWxjIHVuZGVyc3RhbmRzIHRoZSAieiIgd2FybmluZ3MuLi4gKHllcykK LSBidWlsZCBvY2FtbC9pZGwvb2NhbWxfYmFja2VuZCBnZW5fcmJhYy5jbWkgCgorIG9jYW1sZmlu ZCBvY2FtbG9wdCAtcGFja2FnZSAKc3RkZXh0LGxvZyx4bWwtbGlnaHQyLHN0dW5uZWwsc2V4cHIs aHR0cC1zdnIscnBjLWxpZ2h0IC1nIC1kdHlwZXMgCi10aHJlYWQgLXdhcm4tZXJyb3IgK2EtNC02 LTktMjctMjgtMjkgLWNjb3B0IC1mUElDIC1JIC4uLy4uLy4uL29jYW1sL2lkbCAKLUkgK29jYW1s ZG9jIC1JIC4uIC1JIC4uLy4uIC1JIC4uLy4uL2RhdGFiYXNlIC1JIC4uLy4uL2F1dG9nZW4gLUkg Ci4uLy4uL3hhcGkgLUkgLi4vLi4vY2xpZW50X3JlY29yZHMgLUkgLi4vLi4vdXRpbCAtYyBnZW5f cmJhYy5tbApGaWxlICJnZW5fcmJhYy5tbCIsIGxpbmUgMzYsIGNoYXJhY3RlcnMgMTAtMjk6CkVy cm9yOiBVbmJvdW5kIHZhbHVlIERlYnVnLmdldHRpbWVzdHJpbmcKCkFueSB0aG91Z2h0cz8KCjE4 LjAxLjIwMTMgMTc6MDEsIEdlb3JnZSBTaHVrbGluINC/0LjRiNC10YI6Cj4gRm9yIG9sZGVyIHZl cnNpb25zIG9mIFhDUCAoY3VycmVudCB2ZXJzaW9uIGluIFNpZC93aGVlenkgaW5jbHVkZXMgaGVy ZQo+IHRvbykgSSBwb3N0IGEgcGF0Y2ggdG8gdmlmIHNjcmlwdCBzb21lIHRpbWUgYWdvICh0aGF0 IGNvZGUgaW4gcHJvZHVjdAo+IGFib3V0IDIgeWVhcnMgYWxyZWFkeSkgLSBpdCBub3Qgc28gZmFu Y3kgYXMgeGFwaSBmaWVsZHMsIGJ1dCB3b3JraW5nLgo+Cj4gT3IgeW91IGNhbiBqdXN0IHRyeSB0 byBidWlsZCB4Y3AteGFwaSBvbiB3aGVlenkgZnJvbSB0YW1wYS1sY20gYnJhbmNoCj4gZnJvbSBn aXRodWIuCj4KPiAxOC4wMS4yMDEzIDE1OjA5LCBBbmRyZXkg0L/QuNGI0LXRgjoKPj4gSGVsbG8s Cj4+Cj4+IEknbSB0cnlpbmcgdG8gc2V0dXAgUW9TIGZvciB0aGUgdmlmWC5YIHdpdGggeGNwLXhh cGkgaW5zdGFsbGVkIG9uCj4+IERlYmlhbiBXaGVlenkgYnV0IGl0IGRvZXMgbm90IHdvcmsuIEFs c28gSSBkb24ndCBzZWUgYW55IGFudGlzcG9vZiBYQ1AKPj4gMS42IHJlbGF0ZWQgZmllbGRzIGlu IHZpZi1wYXJhbS1zZXQgb3V0cHV0IHN1Y2ggYXMgbG9ja2luZy1tb2RlIGFuZAo+PiBpcHY0LWFs bG93ZWQuCj4+Cj4+IElzIHRoZXJlIGFueSBzdXBwb3J0IG9mIHRoZXNlIGZlYXR1cmVzIGluIHhj cC14YXBpKGtyb25vcyk/IElmIG5vdCBJCj4+IHdpbGwgaGF2ZSB0byBkaXNjYXJkIG9mIHVzaW5n IGl0IGZvciBvdXQgcHVycG9zZXMsIGl0J3MgYSBncmVhdCBwaXR5Li4uCj4+Cj4+IEFuZHJleQo+ Pgo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+PiBY ZW4tYXBpIG1haWxpbmcgbGlzdAo+PiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPj4gaHR0cDovL2xp c3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKPgo+Cj4gX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBYZW4tYXBpIG1haWxp bmcgbGlzdAo+IFhlbi1hcGlAbGlzdHMueGVuLm9yZwo+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL2Nn aS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCgpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hl bi1hcGkK From xen-api-bounces@lists.xen.org Mon Jan 21 06:45:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 06:45:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxB7v-0006A8-15; Mon, 21 Jan 2013 06:45:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxB7t-0006A3-RH for xen-api@lists.xen.org; Mon, 21 Jan 2013 06:45:02 +0000 Received: from [193.109.254.147:60288] by server-6.bemta-14.messagelabs.com id 99/1D-23901-8E3ECF05; Mon, 21 Jan 2013 06:44:56 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-3.tower-27.messagelabs.com!1358750687!9612110!1 X-Originating-IP: [94.100.177.110] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21128 invoked from network); 21 Jan 2013 06:44:48 -0000 Received: from smtp50.i.mail.ru (HELO smtp50.i.mail.ru) (94.100.177.110) by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Jan 2013 06:44:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=LTeULDovyG4xR+XgnYTM4411YQFjeykItowgZtlFddY=; b=FTGRS6o3q7eaRr2NQQidA9cQbs2sBzcCRSbYqramLwcvDG1O6io4n0m8kGxQIaADgPPMYynySqUin4xHxTcS+gXQik5YFrV9j7v5EdjzM6elN6SwugO6ggdK+fsCeoXKclaosg2lR1k//2O14iuY8rPqKUOCWKxrdsCgaKRDItM=; Received: from [78.36.60.25] (port=50508 helo=[10.168.2.113]) by smtp50.i.mail.ru with esmtpa (envelope-from ) id 1TxB7f-0005SB-1p; Mon, 21 Jan 2013 10:44:47 +0400 Message-ID: <50FCE3DD.1050403@bk.ru> Date: Mon, 21 Jan 2013 10:44:45 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <50F92D7E.50908@bk.ru> <50F94796.1080907@gmail.com> In-Reply-To: <50F94796.1080907@gmail.com> X-Spam: Not detected X-Mras: Ok Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xcp-xapi antispoof and QoS support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGVsbG8sCgpUcnlpbmcgdG8gZGViaWFuaXplIGxjbS10YW1wYSBicmFuY2ggYW5kIGdldHRpbmcg Y29tcGlsZSBlcnJvcnMsIApzdWNlc3NmdWxseSBwb3J0ZWQgZXhpc3RlZCBkZWJpYW4vcGF0Y2hl cywgYnV0IGdldHRpbmcgZXJyb3Igd2hpbGUgCmNvbXBpbGluZzoKCi0tLSBDaGVja2luZyBmb3Ig b2NhbWxmaW5kLi4uIChmb3VuZCAvdXNyL2Jpbi9vY2FtbGZpbmQpCi0tLSBDaGVja2luZyBmb3Ig b2NhbWxjLm9wdC4uLiAoZm91bmQgL3Vzci9iaW4vb2NhbWxjLm9wdCkKLS0tIENoZWNraW5nIGZv ciBvY2FtbG9wdC5vcHQuLi4gKGZvdW5kIC91c3IvYmluL29jYW1sb3B0Lm9wdCkKLS0tIENoZWNr aW5nIHdoZXRoZXIgb2NhbWxjIHVuZGVyc3RhbmRzIHRoZSAieiIgd2FybmluZ3MuLi4gKHllcykK LSBidWlsZCBvY2FtbC9pZGwvb2NhbWxfYmFja2VuZCBnZW5fcmJhYy5jbWkgCgorIG9jYW1sZmlu ZCBvY2FtbG9wdCAtcGFja2FnZSAKc3RkZXh0LGxvZyx4bWwtbGlnaHQyLHN0dW5uZWwsc2V4cHIs aHR0cC1zdnIscnBjLWxpZ2h0IC1nIC1kdHlwZXMgCi10aHJlYWQgLXdhcm4tZXJyb3IgK2EtNC02 LTktMjctMjgtMjkgLWNjb3B0IC1mUElDIC1JIC4uLy4uLy4uL29jYW1sL2lkbCAKLUkgK29jYW1s ZG9jIC1JIC4uIC1JIC4uLy4uIC1JIC4uLy4uL2RhdGFiYXNlIC1JIC4uLy4uL2F1dG9nZW4gLUkg Ci4uLy4uL3hhcGkgLUkgLi4vLi4vY2xpZW50X3JlY29yZHMgLUkgLi4vLi4vdXRpbCAtYyBnZW5f cmJhYy5tbApGaWxlICJnZW5fcmJhYy5tbCIsIGxpbmUgMzYsIGNoYXJhY3RlcnMgMTAtMjk6CkVy cm9yOiBVbmJvdW5kIHZhbHVlIERlYnVnLmdldHRpbWVzdHJpbmcKCkFueSB0aG91Z2h0cz8KCjE4 LjAxLjIwMTMgMTc6MDEsIEdlb3JnZSBTaHVrbGluINC/0LjRiNC10YI6Cj4gRm9yIG9sZGVyIHZl cnNpb25zIG9mIFhDUCAoY3VycmVudCB2ZXJzaW9uIGluIFNpZC93aGVlenkgaW5jbHVkZXMgaGVy ZQo+IHRvbykgSSBwb3N0IGEgcGF0Y2ggdG8gdmlmIHNjcmlwdCBzb21lIHRpbWUgYWdvICh0aGF0 IGNvZGUgaW4gcHJvZHVjdAo+IGFib3V0IDIgeWVhcnMgYWxyZWFkeSkgLSBpdCBub3Qgc28gZmFu Y3kgYXMgeGFwaSBmaWVsZHMsIGJ1dCB3b3JraW5nLgo+Cj4gT3IgeW91IGNhbiBqdXN0IHRyeSB0 byBidWlsZCB4Y3AteGFwaSBvbiB3aGVlenkgZnJvbSB0YW1wYS1sY20gYnJhbmNoCj4gZnJvbSBn aXRodWIuCj4KPiAxOC4wMS4yMDEzIDE1OjA5LCBBbmRyZXkg0L/QuNGI0LXRgjoKPj4gSGVsbG8s Cj4+Cj4+IEknbSB0cnlpbmcgdG8gc2V0dXAgUW9TIGZvciB0aGUgdmlmWC5YIHdpdGggeGNwLXhh cGkgaW5zdGFsbGVkIG9uCj4+IERlYmlhbiBXaGVlenkgYnV0IGl0IGRvZXMgbm90IHdvcmsuIEFs c28gSSBkb24ndCBzZWUgYW55IGFudGlzcG9vZiBYQ1AKPj4gMS42IHJlbGF0ZWQgZmllbGRzIGlu IHZpZi1wYXJhbS1zZXQgb3V0cHV0IHN1Y2ggYXMgbG9ja2luZy1tb2RlIGFuZAo+PiBpcHY0LWFs bG93ZWQuCj4+Cj4+IElzIHRoZXJlIGFueSBzdXBwb3J0IG9mIHRoZXNlIGZlYXR1cmVzIGluIHhj cC14YXBpKGtyb25vcyk/IElmIG5vdCBJCj4+IHdpbGwgaGF2ZSB0byBkaXNjYXJkIG9mIHVzaW5n IGl0IGZvciBvdXQgcHVycG9zZXMsIGl0J3MgYSBncmVhdCBwaXR5Li4uCj4+Cj4+IEFuZHJleQo+ Pgo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+PiBY ZW4tYXBpIG1haWxpbmcgbGlzdAo+PiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPj4gaHR0cDovL2xp c3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkKPgo+Cj4gX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBYZW4tYXBpIG1haWxp bmcgbGlzdAo+IFhlbi1hcGlAbGlzdHMueGVuLm9yZwo+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL2Nn aS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCgpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hl bi1hcGkK From xen-api-bounces@lists.xen.org Mon Jan 21 11:31:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 11:31:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxFbI-0000TF-TS; Mon, 21 Jan 2013 11:31:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxFbI-0000T7-20; Mon, 21 Jan 2013 11:31:40 +0000 Received: from [85.158.139.211:62699] by server-9.bemta-5.messagelabs.com id 7F/6C-29536-9172DF05; Mon, 21 Jan 2013 11:31:37 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1358767895!15020568!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3NDU0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3119 invoked from network); 21 Jan 2013 11:31:35 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 11:31:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,506,1355097600"; d="scan'208";a="783827" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Jan 2013 11:31:35 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 21 Jan 2013 11:31:35 +0000 From: Dave Scott To: "'xen-devel@lists.xen.org'" Date: Mon, 21 Jan 2013 11:31:35 +0000 Thread-Topic: driver domain crash and reconnect handling Thread-Index: Ac33yoAXx4zndl6rTKKvrmsXTPVYvQ== Message-ID: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Zoltan Kiss , "xen-api@lists.xen.org" Subject: [Xen-API] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, [ my apologies if this has been discussed before but I couldn't find a relevant thread ] In XCP we're hoping to make serious use of driver domains soon. We'd like to tell people that their xen-based cloud is even more robust than before, because even if a host driver crashes, there is only a slight interruption to guest I/O. For this to work smoothly, we need to figure out how to re-establish disk and network I/O after the driver restart -- this is where I'd appreciate some advice! Is the current xenstore protocol considered sufficient to support reconnecting a frontend to a new backend? I did a few simple experiments with an XCP driver domain prototype a while back and I failed to make the frontend happy -- usually it would become confused about the backend and become stuck. This might just be because I didn't know what I was doing :-) Zoltan (cc:d) also did a few simple experiments to see whether we could re-use the existing suspend/resume infrastructure, similar to the 'fast' resume we already use for live checkpoint. As an experiment he modified libxc's xc_resume.c to allow the guest's HYPERVISOR_suspend hypercall invocation to return with '0' (success) rather than '1' (cancelled). The effect of this was to leave the domain running, but since it thinks it has just resumed in another domain, it explicitly reconnects its frontends. With this change and one or two others (like fixing the start_info->{store_,console.domU}.mfns) he made it work for a number of oldish guests. I'm sure he can describe the changes needed more accurately than I can! What do you think of this approach? Since it's based on the existing suspend/resume code it should hopefully work with all guest types without having to update the frontends or hopefully even fix bugs in them (because it looks just like a regular resume which is pretty well tested everywhere). This is particularly important in "cloud" scenarios because the people running clouds have usually little or no control over the software their customers are running. Unfortunately if we have to wait for a PV frontend change to trickle into all the common distros it will be a while before we can fully benefit from driver domain restart. If there is a better way of doing this in the long term involving a frontend change, what do you think about this as a stopgap until the frontends are updated? Cheers, Dave _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 21 11:31:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 11:31:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxFbI-0000TF-TS; Mon, 21 Jan 2013 11:31:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxFbI-0000T7-20; Mon, 21 Jan 2013 11:31:40 +0000 Received: from [85.158.139.211:62699] by server-9.bemta-5.messagelabs.com id 7F/6C-29536-9172DF05; Mon, 21 Jan 2013 11:31:37 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1358767895!15020568!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3NDU0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3119 invoked from network); 21 Jan 2013 11:31:35 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 11:31:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,506,1355097600"; d="scan'208";a="783827" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Jan 2013 11:31:35 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 21 Jan 2013 11:31:35 +0000 From: Dave Scott To: "'xen-devel@lists.xen.org'" Date: Mon, 21 Jan 2013 11:31:35 +0000 Thread-Topic: driver domain crash and reconnect handling Thread-Index: Ac33yoAXx4zndl6rTKKvrmsXTPVYvQ== Message-ID: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Zoltan Kiss , "xen-api@lists.xen.org" Subject: [Xen-API] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, [ my apologies if this has been discussed before but I couldn't find a relevant thread ] In XCP we're hoping to make serious use of driver domains soon. We'd like to tell people that their xen-based cloud is even more robust than before, because even if a host driver crashes, there is only a slight interruption to guest I/O. For this to work smoothly, we need to figure out how to re-establish disk and network I/O after the driver restart -- this is where I'd appreciate some advice! Is the current xenstore protocol considered sufficient to support reconnecting a frontend to a new backend? I did a few simple experiments with an XCP driver domain prototype a while back and I failed to make the frontend happy -- usually it would become confused about the backend and become stuck. This might just be because I didn't know what I was doing :-) Zoltan (cc:d) also did a few simple experiments to see whether we could re-use the existing suspend/resume infrastructure, similar to the 'fast' resume we already use for live checkpoint. As an experiment he modified libxc's xc_resume.c to allow the guest's HYPERVISOR_suspend hypercall invocation to return with '0' (success) rather than '1' (cancelled). The effect of this was to leave the domain running, but since it thinks it has just resumed in another domain, it explicitly reconnects its frontends. With this change and one or two others (like fixing the start_info->{store_,console.domU}.mfns) he made it work for a number of oldish guests. I'm sure he can describe the changes needed more accurately than I can! What do you think of this approach? Since it's based on the existing suspend/resume code it should hopefully work with all guest types without having to update the frontends or hopefully even fix bugs in them (because it looks just like a regular resume which is pretty well tested everywhere). This is particularly important in "cloud" scenarios because the people running clouds have usually little or no control over the software their customers are running. Unfortunately if we have to wait for a PV frontend change to trickle into all the common distros it will be a while before we can fully benefit from driver domain restart. If there is a better way of doing this in the long term involving a frontend change, what do you think about this as a stopgap until the frontends are updated? Cheers, Dave _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 21 11:41:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 11:41:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxFkF-00011U-Hw; Mon, 21 Jan 2013 11:40:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxFkE-00011C-DT for Xen-api@lists.xen.org; Mon, 21 Jan 2013 11:40:54 +0000 Received: from [85.158.138.51:4341] by server-15.bemta-3.messagelabs.com id 68/96-25008-E392DF05; Mon, 21 Jan 2013 11:40:46 +0000 X-Env-Sender: lukasz.nowak@unity.pl X-Msg-Ref: server-11.tower-174.messagelabs.com!1358768443!28894656!1 X-Originating-IP: [216.32.181.183] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20731 invoked from network); 21 Jan 2013 11:40:45 -0000 Received: from ch1ehsobe003.messaging.microsoft.com (HELO ch1outboundpool.messaging.microsoft.com) (216.32.181.183) by server-11.tower-174.messagelabs.com with AES128-SHA encrypted SMTP; 21 Jan 2013 11:40:45 -0000 Received: from mail210-ch1-R.bigfish.com (10.43.68.228) by CH1EHSOBE003.bigfish.com (10.43.70.53) with Microsoft SMTP Server id 14.1.225.23; Mon, 21 Jan 2013 11:40:43 +0000 Received: from mail210-ch1 (localhost [127.0.0.1]) by mail210-ch1-R.bigfish.com (Postfix) with ESMTP id 5B87138017D for ; Mon, 21 Jan 2013 11:40:43 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.253.149; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0311HT005.eurprd03.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: 0 X-BigFish: PS0(zzc89bhzz1ee6h1de0h1d18h1202h1e76h1d1ah1d2ahzzz2fh2a8h668h839h93fhd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h1155h) Received-SPF: pass (mail210-ch1: domain of unity.pl designates 157.56.253.149 as permitted sender) client-ip=157.56.253.149; envelope-from=lukasz.nowak@unity.pl; helo=DBXPRD0311HT005.eurprd03.prod.outlook.com ; .outlook.com ; Received: from mail210-ch1 (localhost.localdomain [127.0.0.1]) by mail210-ch1 (MessageSwitch) id 135876844194795_5073; Mon, 21 Jan 2013 11:40:41 +0000 (UTC) Received: from CH1EHSMHS039.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.232]) by mail210-ch1.bigfish.com (Postfix) with ESMTP id 14AAB3600B0 for ; Mon, 21 Jan 2013 11:40:41 +0000 (UTC) Received: from DBXPRD0311HT005.eurprd03.prod.outlook.com (157.56.253.149) by CH1EHSMHS039.bigfish.com (10.43.69.248) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 21 Jan 2013 11:40:40 +0000 Received: from [192.168.0.32] (193.178.214.60) by pod51013.outlook.com (10.255.76.168) with Microsoft SMTP Server (TLS) id 14.16.257.4; Mon, 21 Jan 2013 11:40:35 +0000 Message-ID: <50FD2930.9010207@unity.pl> Date: Mon, 21 Jan 2013 12:40:32 +0100 From: =?UTF-8?B?xYF1a2FzeiBOb3dhaw==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: X-Enigmail-Version: 1.4.1 X-Originating-IP: [193.178.214.60] X-OriginatorOrg: unity.pl Subject: [Xen-API] XCP online resize vdi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGksCmhvdyBjYW4gSSBpbmNyZWFzZSBWREkgc3BhY2Ugb25saW5lPwoKCkkgdHJpZWQ6Cltyb290 QHVzeXFheGMwMSB+XSMgeGUgdmRpLXJlc2l6ZSBkaXNrLXNpemU9MjE0NzQ5MzY0OAp1dWlkPTk1 NzVkMDc2LTk3YTUtNDhhYi1iMWUwLWQ4OTAwNTNlZThlZiBvbmxpbmU9dHJ1ZQpUaGUgU1IgYmFj a2VuZCBkb2VzIG5vdCBzdXBwb3J0IHRoZSBvcGVyYXRpb24gKGNoZWNrIHRoZSBTUidzIGFsbG93 ZWQKb3BlcmF0aW9ucykKc3I6IGZhOTMzNDNlLTdiZTAtNzNkYS1jMDE5LTMxMGQyZWRiYjNkYSAo aXNjc2kgLSBzZG0pCgoKTXkgU1IgdHlwZSBpczogbHZtb2lzY3NpClhDUCAxLjYKCkxpbnV4IGRp c3RyaWJ1dGlvbiBpbiB0aGUgdm0gaXMgZGViaWFuLiBJIGhhdmUgaW5zdGFsbGVkCnhlLWd1ZXN0 LXV0aWxpdGllcyBvbiB0aGUgdm0uCgpbcm9vdEB1c3lxYXhjMDEgfl0jIHhlIHZkaS1wYXJhbS1s aXN0CnV1aWQ9OTU3NWQwNzYtOTdhNS00OGFiLWIxZTAtZDg5MDA1M2VlOGVmIHwgZ3JlcCBhbGxv d2VkIG9wZXJhdGlvbnMKCgogICAgICBhbGxvd2VkLW9wZXJhdGlvbnMgKFNSTyk6IGNsb25lOyBz bmFwc2hvdAoKW3Jvb3RAdXN5cWF4YzAxIH5dIyB4ZSBzci1wYXJhbS1saXN0CnV1aWQ9ZmE5MzM0 M2UtN2JlMC03M2RhLWMwMTktMzEwZDJlZGJiM2RhfGdyZXAgYWxsb3dlZC1vcGVyYXRpb25zCiAg ICAgIGFsbG93ZWQtb3BlcmF0aW9ucyAoU1JPKTogVkRJLmNyZWF0ZTsgVkRJLnNuYXBzaG90OyBQ QkQuY3JlYXRlOwpQQkQuZGVzdHJveTsgcGx1ZzsgdXBkYXRlOyBWREkuZGVzdHJveTsgc2Nhbjsg VkRJLmNsb25lOyBWREkucmVzaXplOyB1bnBsdWcKCgoKCkJlc3QgcmVnYXJkcywKLS0gCsWBdWth c3ogTm93YWsKQWRtaW5pc3RyYXRvciBTeXN0ZW3Ds3cgVW5peApHU006ICs0OCA2MDMgOTkyIDU1 OCB8IGx1a2Fzei5ub3dha0Bjb250aXVtLnBsCkpBQkJFUjogbHVrYXN6Lm5vd2FrQGNvbnRpdW0u cGwKIApHcnVwYSBVbml0eSB8IHVsLiBQcnplZG1pZWpza2EgNi0xMCwgNTQtMjAxIFdyb2PFgmF3 CnVsLiBDb25yYWRhIDU1QiwgMzEtMzU3IEtyYWvDs3cgfCB1bC4gWsWCb3RhIDU5LCAwMC0xMjAg V2Fyc3phd2EKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f XwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Mon Jan 21 11:41:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 11:41:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxFkF-00011U-Hw; Mon, 21 Jan 2013 11:40:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxFkE-00011C-DT for Xen-api@lists.xen.org; Mon, 21 Jan 2013 11:40:54 +0000 Received: from [85.158.138.51:4341] by server-15.bemta-3.messagelabs.com id 68/96-25008-E392DF05; Mon, 21 Jan 2013 11:40:46 +0000 X-Env-Sender: lukasz.nowak@unity.pl X-Msg-Ref: server-11.tower-174.messagelabs.com!1358768443!28894656!1 X-Originating-IP: [216.32.181.183] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20731 invoked from network); 21 Jan 2013 11:40:45 -0000 Received: from ch1ehsobe003.messaging.microsoft.com (HELO ch1outboundpool.messaging.microsoft.com) (216.32.181.183) by server-11.tower-174.messagelabs.com with AES128-SHA encrypted SMTP; 21 Jan 2013 11:40:45 -0000 Received: from mail210-ch1-R.bigfish.com (10.43.68.228) by CH1EHSOBE003.bigfish.com (10.43.70.53) with Microsoft SMTP Server id 14.1.225.23; Mon, 21 Jan 2013 11:40:43 +0000 Received: from mail210-ch1 (localhost [127.0.0.1]) by mail210-ch1-R.bigfish.com (Postfix) with ESMTP id 5B87138017D for ; Mon, 21 Jan 2013 11:40:43 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.253.149; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0311HT005.eurprd03.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: 0 X-BigFish: PS0(zzc89bhzz1ee6h1de0h1d18h1202h1e76h1d1ah1d2ahzzz2fh2a8h668h839h93fhd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h1155h) Received-SPF: pass (mail210-ch1: domain of unity.pl designates 157.56.253.149 as permitted sender) client-ip=157.56.253.149; envelope-from=lukasz.nowak@unity.pl; helo=DBXPRD0311HT005.eurprd03.prod.outlook.com ; .outlook.com ; Received: from mail210-ch1 (localhost.localdomain [127.0.0.1]) by mail210-ch1 (MessageSwitch) id 135876844194795_5073; Mon, 21 Jan 2013 11:40:41 +0000 (UTC) Received: from CH1EHSMHS039.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.232]) by mail210-ch1.bigfish.com (Postfix) with ESMTP id 14AAB3600B0 for ; Mon, 21 Jan 2013 11:40:41 +0000 (UTC) Received: from DBXPRD0311HT005.eurprd03.prod.outlook.com (157.56.253.149) by CH1EHSMHS039.bigfish.com (10.43.69.248) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 21 Jan 2013 11:40:40 +0000 Received: from [192.168.0.32] (193.178.214.60) by pod51013.outlook.com (10.255.76.168) with Microsoft SMTP Server (TLS) id 14.16.257.4; Mon, 21 Jan 2013 11:40:35 +0000 Message-ID: <50FD2930.9010207@unity.pl> Date: Mon, 21 Jan 2013 12:40:32 +0100 From: =?UTF-8?B?xYF1a2FzeiBOb3dhaw==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: X-Enigmail-Version: 1.4.1 X-Originating-IP: [193.178.214.60] X-OriginatorOrg: unity.pl Subject: [Xen-API] XCP online resize vdi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGksCmhvdyBjYW4gSSBpbmNyZWFzZSBWREkgc3BhY2Ugb25saW5lPwoKCkkgdHJpZWQ6Cltyb290 QHVzeXFheGMwMSB+XSMgeGUgdmRpLXJlc2l6ZSBkaXNrLXNpemU9MjE0NzQ5MzY0OAp1dWlkPTk1 NzVkMDc2LTk3YTUtNDhhYi1iMWUwLWQ4OTAwNTNlZThlZiBvbmxpbmU9dHJ1ZQpUaGUgU1IgYmFj a2VuZCBkb2VzIG5vdCBzdXBwb3J0IHRoZSBvcGVyYXRpb24gKGNoZWNrIHRoZSBTUidzIGFsbG93 ZWQKb3BlcmF0aW9ucykKc3I6IGZhOTMzNDNlLTdiZTAtNzNkYS1jMDE5LTMxMGQyZWRiYjNkYSAo aXNjc2kgLSBzZG0pCgoKTXkgU1IgdHlwZSBpczogbHZtb2lzY3NpClhDUCAxLjYKCkxpbnV4IGRp c3RyaWJ1dGlvbiBpbiB0aGUgdm0gaXMgZGViaWFuLiBJIGhhdmUgaW5zdGFsbGVkCnhlLWd1ZXN0 LXV0aWxpdGllcyBvbiB0aGUgdm0uCgpbcm9vdEB1c3lxYXhjMDEgfl0jIHhlIHZkaS1wYXJhbS1s aXN0CnV1aWQ9OTU3NWQwNzYtOTdhNS00OGFiLWIxZTAtZDg5MDA1M2VlOGVmIHwgZ3JlcCBhbGxv d2VkIG9wZXJhdGlvbnMKCgogICAgICBhbGxvd2VkLW9wZXJhdGlvbnMgKFNSTyk6IGNsb25lOyBz bmFwc2hvdAoKW3Jvb3RAdXN5cWF4YzAxIH5dIyB4ZSBzci1wYXJhbS1saXN0CnV1aWQ9ZmE5MzM0 M2UtN2JlMC03M2RhLWMwMTktMzEwZDJlZGJiM2RhfGdyZXAgYWxsb3dlZC1vcGVyYXRpb25zCiAg ICAgIGFsbG93ZWQtb3BlcmF0aW9ucyAoU1JPKTogVkRJLmNyZWF0ZTsgVkRJLnNuYXBzaG90OyBQ QkQuY3JlYXRlOwpQQkQuZGVzdHJveTsgcGx1ZzsgdXBkYXRlOyBWREkuZGVzdHJveTsgc2Nhbjsg VkRJLmNsb25lOyBWREkucmVzaXplOyB1bnBsdWcKCgoKCkJlc3QgcmVnYXJkcywKLS0gCsWBdWth c3ogTm93YWsKQWRtaW5pc3RyYXRvciBTeXN0ZW3Ds3cgVW5peApHU006ICs0OCA2MDMgOTkyIDU1 OCB8IGx1a2Fzei5ub3dha0Bjb250aXVtLnBsCkpBQkJFUjogbHVrYXN6Lm5vd2FrQGNvbnRpdW0u cGwKIApHcnVwYSBVbml0eSB8IHVsLiBQcnplZG1pZWpza2EgNi0xMCwgNTQtMjAxIFdyb2PFgmF3 CnVsLiBDb25yYWRhIDU1QiwgMzEtMzU3IEtyYWvDs3cgfCB1bC4gWsWCb3RhIDU5LCAwMC0xMjAg V2Fyc3phd2EKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f XwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Mon Jan 21 12:21:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 12:21:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxGMy-0002ke-5e; Mon, 21 Jan 2013 12:20:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxGMw-0002kC-Oc; Mon, 21 Jan 2013 12:20:54 +0000 Received: from [85.158.138.51:64077] by server-15.bemta-3.messagelabs.com id FB/98-25008-5A23DF05; Mon, 21 Jan 2013 12:20:53 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1358770846!27134301!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3NDU0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 936 invoked from network); 21 Jan 2013 12:20:47 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 12:20:47 -0000 X-IronPort-AV: E=Sophos;i="4.84,506,1355097600"; d="scan'208";a="785370" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Jan 2013 12:20:45 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Mon, 21 Jan 2013 12:20:46 +0000 Message-ID: <1358770844.3279.194.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Dave Scott Date: Mon, 21 Jan 2013 12:20:44 +0000 In-Reply-To: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" , Zoltan Kiss , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mon, 2013-01-21 at 11:31 +0000, Dave Scott wrote: > Hi, > > [ my apologies if this has been discussed before but I couldn't > find a relevant thread ] I don't think it has. > In XCP we're hoping to make serious use of driver domains soon. > We'd like to tell people that their xen-based cloud is even > more robust than before, because even if a host driver crashes, > there is only a slight interruption to guest I/O. For this to > work smoothly, we need to figure out how to re-establish disk > and network I/O after the driver restart -- this is where I'd > appreciate some advice! > > Is the current xenstore protocol considered sufficient to > support reconnecting a frontend to a new backend? I did a few > simple experiments with an XCP driver domain prototype a while > back and I failed to make the frontend happy -- usually it would > become confused about the backend and become stuck. This might > just be because I didn't know what I was doing :-) I think the protocol is probably sufficient but the implementations of that protocol are not... > Zoltan (cc:d) also did a few simple experiments to see whether > we could re-use the existing suspend/resume infrastructure, > similar to the 'fast' resume we already use for live checkpoint. > As an experiment he modified libxc's xc_resume.c to allow the > guest's HYPERVISOR_suspend hypercall invocation to return with > '0' (success) rather than '1' (cancelled). The effect of this > was to leave the domain running, but since it thinks it has just > resumed in another domain, it explicitly reconnects its frontends. > With this change and one or two others (like fixing the > start_info->{store_,console.domU}.mfns) he made it work for a > number of oldish guests. I'm sure he can describe the changes > needed more accurately than I can! Would be interesting to know, especially if everything was achieved with toolstack side changes only! > What do you think of this approach? Since it's based on the > existing suspend/resume code it should hopefully work with all > guest types without having to update the frontends or hopefully even > fix bugs in them (because it looks just like a regular resume which > is pretty well tested everywhere). This is particularly important in > "cloud" scenarios because the people running clouds have usually > little or no control over the software their customers are running. > Unfortunately if we have to wait for a PV frontend change to trickle > into all the common distros it will be a while before we can fully > benefit from driver domain restart. If there is a better way > of doing this in the long term involving a frontend change, what > do you think about this as a stopgap until the frontends are updated? I think it could undoubtedly serve well as a stop gap. Longer term I guess it depends on the shortcomings of this approach whether we also want to do something more advanced in the PV drivers upstream and have them trickle through. The main downsides I suppose is the brief outage due to the proto-suspend plus the requirement to reconnect all devices and not just the failed one? I expect the outage due to the proto-suspend is dwarfed by the outage caused by a backend going away for however long it takes to notice, rebuild, reset the hardware, etc etc. The "it's just a normal-ish suspend" argument is pretty compelling since you are correct that it is likely to be better tested than a crashing driver domain. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 21 12:21:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 12:21:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxGMy-0002ke-5e; Mon, 21 Jan 2013 12:20:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxGMw-0002kC-Oc; Mon, 21 Jan 2013 12:20:54 +0000 Received: from [85.158.138.51:64077] by server-15.bemta-3.messagelabs.com id FB/98-25008-5A23DF05; Mon, 21 Jan 2013 12:20:53 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1358770846!27134301!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3NDU0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 936 invoked from network); 21 Jan 2013 12:20:47 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 12:20:47 -0000 X-IronPort-AV: E=Sophos;i="4.84,506,1355097600"; d="scan'208";a="785370" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Jan 2013 12:20:45 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Mon, 21 Jan 2013 12:20:46 +0000 Message-ID: <1358770844.3279.194.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Dave Scott Date: Mon, 21 Jan 2013 12:20:44 +0000 In-Reply-To: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" , Zoltan Kiss , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mon, 2013-01-21 at 11:31 +0000, Dave Scott wrote: > Hi, > > [ my apologies if this has been discussed before but I couldn't > find a relevant thread ] I don't think it has. > In XCP we're hoping to make serious use of driver domains soon. > We'd like to tell people that their xen-based cloud is even > more robust than before, because even if a host driver crashes, > there is only a slight interruption to guest I/O. For this to > work smoothly, we need to figure out how to re-establish disk > and network I/O after the driver restart -- this is where I'd > appreciate some advice! > > Is the current xenstore protocol considered sufficient to > support reconnecting a frontend to a new backend? I did a few > simple experiments with an XCP driver domain prototype a while > back and I failed to make the frontend happy -- usually it would > become confused about the backend and become stuck. This might > just be because I didn't know what I was doing :-) I think the protocol is probably sufficient but the implementations of that protocol are not... > Zoltan (cc:d) also did a few simple experiments to see whether > we could re-use the existing suspend/resume infrastructure, > similar to the 'fast' resume we already use for live checkpoint. > As an experiment he modified libxc's xc_resume.c to allow the > guest's HYPERVISOR_suspend hypercall invocation to return with > '0' (success) rather than '1' (cancelled). The effect of this > was to leave the domain running, but since it thinks it has just > resumed in another domain, it explicitly reconnects its frontends. > With this change and one or two others (like fixing the > start_info->{store_,console.domU}.mfns) he made it work for a > number of oldish guests. I'm sure he can describe the changes > needed more accurately than I can! Would be interesting to know, especially if everything was achieved with toolstack side changes only! > What do you think of this approach? Since it's based on the > existing suspend/resume code it should hopefully work with all > guest types without having to update the frontends or hopefully even > fix bugs in them (because it looks just like a regular resume which > is pretty well tested everywhere). This is particularly important in > "cloud" scenarios because the people running clouds have usually > little or no control over the software their customers are running. > Unfortunately if we have to wait for a PV frontend change to trickle > into all the common distros it will be a while before we can fully > benefit from driver domain restart. If there is a better way > of doing this in the long term involving a frontend change, what > do you think about this as a stopgap until the frontends are updated? I think it could undoubtedly serve well as a stop gap. Longer term I guess it depends on the shortcomings of this approach whether we also want to do something more advanced in the PV drivers upstream and have them trickle through. The main downsides I suppose is the brief outage due to the proto-suspend plus the requirement to reconnect all devices and not just the failed one? I expect the outage due to the proto-suspend is dwarfed by the outage caused by a backend going away for however long it takes to notice, rebuild, reset the hardware, etc etc. The "it's just a normal-ish suspend" argument is pretty compelling since you are correct that it is likely to be better tested than a crashing driver domain. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 21 13:46:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 13:46:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxHhb-0005sV-Nw; Mon, 21 Jan 2013 13:46:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxHhZ-0005sN-JE for xen-api@lists.xen.org; Mon, 21 Jan 2013 13:46:17 +0000 Received: from [85.158.143.35:49707] by server-1.bemta-4.messagelabs.com id C0/16-05635-8A64DF05; Mon, 21 Jan 2013 13:46:16 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1358775869!13100115!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21918 invoked from network); 21 Jan 2013 13:44:36 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 13:44:36 -0000 Received: by mail-lb0-f182.google.com with SMTP id gg6so3824056lbb.13 for ; Mon, 21 Jan 2013 05:44:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=HHuJSghp5bywfnlfH8esQQt4JUNj85JGqAI3meO4tjo=; b=sFk+avi4QyRNt6DFCbE4CwMzShyodYPVJXLVvDV7+6aL2Xfa18dvWPMKBvtByYfy5x jUx7jWkUgY1JDugdA3FGgRVMsLGsc6DPM6dDLAIhVkyKRKPhR1nv5cKI9P1ZUfMGtWq2 aSLEee65olGqOrQe1A2qeW/GCmnfFFwo9+Qm/GSyEJvT7zCOlelmOcI0sLr5f1PbhLPz yYxt8OC1yHq215iPO6tBwz0oO/n0CjExkiW0ObL5/82gNO1VQ5UcV7Aor9YgowsVbReL zwQVC2I8nCcQp4Bu7zIz4KW9LqMqgJeu96iEeC2S1vNtNL9/Lwdyky1SMEh9JzI0Ay/q 8txg== X-Received: by 10.112.88.105 with SMTP id bf9mr7706834lbb.43.1358775869216; Mon, 21 Jan 2013 05:44:29 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:2458:d561:8ffa:b3f4? ([2a00:ab00:0:fffe:2458:d561:8ffa:b3f4]) by mx.google.com with ESMTPS id ox6sm5468886lab.16.2013.01.21.05.44.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jan 2013 05:44:28 -0800 (PST) Message-ID: <50FD463C.5030704@gmail.com> Date: Mon, 21 Jan 2013 17:44:28 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50FD2930.9010207@unity.pl> In-Reply-To: <50FD2930.9010207@unity.pl> Subject: Re: [Xen-API] XCP online resize vdi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Tm93YXksIHNvcnJ5LiBBRkFJSyB0aGlzIGlzIHJlc2VydmUgZm9yIHRoZSBmdXR1cmUuCgoyMS4w MS4yMDEzIDE1OjQwLCDFgXVrYXN6IE5vd2FrINC/0LjRiNC10YI6Cj4gSGksCj4gaG93IGNhbiBJ IGluY3JlYXNlIFZESSBzcGFjZSBvbmxpbmU/Cj4KPgo+IEkgdHJpZWQ6Cj4gW3Jvb3RAdXN5cWF4 YzAxIH5dIyB4ZSB2ZGktcmVzaXplIGRpc2stc2l6ZT0yMTQ3NDkzNjQ4Cj4gdXVpZD05NTc1ZDA3 Ni05N2E1LTQ4YWItYjFlMC1kODkwMDUzZWU4ZWYgb25saW5lPXRydWUKPiBUaGUgU1IgYmFja2Vu ZCBkb2VzIG5vdCBzdXBwb3J0IHRoZSBvcGVyYXRpb24gKGNoZWNrIHRoZSBTUidzIGFsbG93ZWQK PiBvcGVyYXRpb25zKQo+IHNyOiBmYTkzMzQzZS03YmUwLTczZGEtYzAxOS0zMTBkMmVkYmIzZGEg KGlzY3NpIC0gc2RtKQo+Cj4KPiBNeSBTUiB0eXBlIGlzOiBsdm1vaXNjc2kKPiBYQ1AgMS42Cj4K PiBMaW51eCBkaXN0cmlidXRpb24gaW4gdGhlIHZtIGlzIGRlYmlhbi4gSSBoYXZlIGluc3RhbGxl ZAo+IHhlLWd1ZXN0LXV0aWxpdGllcyBvbiB0aGUgdm0uCj4KPiBbcm9vdEB1c3lxYXhjMDEgfl0j IHhlIHZkaS1wYXJhbS1saXN0Cj4gdXVpZD05NTc1ZDA3Ni05N2E1LTQ4YWItYjFlMC1kODkwMDUz ZWU4ZWYgfCBncmVwIGFsbG93ZWQgb3BlcmF0aW9ucwo+Cj4KPiAgICAgICAgYWxsb3dlZC1vcGVy YXRpb25zIChTUk8pOiBjbG9uZTsgc25hcHNob3QKPgo+IFtyb290QHVzeXFheGMwMSB+XSMgeGUg c3ItcGFyYW0tbGlzdAo+IHV1aWQ9ZmE5MzM0M2UtN2JlMC03M2RhLWMwMTktMzEwZDJlZGJiM2Rh fGdyZXAgYWxsb3dlZC1vcGVyYXRpb25zCj4gICAgICAgIGFsbG93ZWQtb3BlcmF0aW9ucyAoU1JP KTogVkRJLmNyZWF0ZTsgVkRJLnNuYXBzaG90OyBQQkQuY3JlYXRlOwo+IFBCRC5kZXN0cm95OyBw bHVnOyB1cGRhdGU7IFZESS5kZXN0cm95OyBzY2FuOyBWREkuY2xvbmU7IFZESS5yZXNpemU7IHVu cGx1Zwo+Cj4KPgo+Cj4gQmVzdCByZWdhcmRzLAoKCl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMu eGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVu LWFwaQo= From xen-api-bounces@lists.xen.org Mon Jan 21 13:46:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 13:46:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxHhb-0005sV-Nw; Mon, 21 Jan 2013 13:46:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxHhZ-0005sN-JE for xen-api@lists.xen.org; Mon, 21 Jan 2013 13:46:17 +0000 Received: from [85.158.143.35:49707] by server-1.bemta-4.messagelabs.com id C0/16-05635-8A64DF05; Mon, 21 Jan 2013 13:46:16 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1358775869!13100115!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21918 invoked from network); 21 Jan 2013 13:44:36 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 13:44:36 -0000 Received: by mail-lb0-f182.google.com with SMTP id gg6so3824056lbb.13 for ; Mon, 21 Jan 2013 05:44:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=HHuJSghp5bywfnlfH8esQQt4JUNj85JGqAI3meO4tjo=; b=sFk+avi4QyRNt6DFCbE4CwMzShyodYPVJXLVvDV7+6aL2Xfa18dvWPMKBvtByYfy5x jUx7jWkUgY1JDugdA3FGgRVMsLGsc6DPM6dDLAIhVkyKRKPhR1nv5cKI9P1ZUfMGtWq2 aSLEee65olGqOrQe1A2qeW/GCmnfFFwo9+Qm/GSyEJvT7zCOlelmOcI0sLr5f1PbhLPz yYxt8OC1yHq215iPO6tBwz0oO/n0CjExkiW0ObL5/82gNO1VQ5UcV7Aor9YgowsVbReL zwQVC2I8nCcQp4Bu7zIz4KW9LqMqgJeu96iEeC2S1vNtNL9/Lwdyky1SMEh9JzI0Ay/q 8txg== X-Received: by 10.112.88.105 with SMTP id bf9mr7706834lbb.43.1358775869216; Mon, 21 Jan 2013 05:44:29 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:2458:d561:8ffa:b3f4? ([2a00:ab00:0:fffe:2458:d561:8ffa:b3f4]) by mx.google.com with ESMTPS id ox6sm5468886lab.16.2013.01.21.05.44.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jan 2013 05:44:28 -0800 (PST) Message-ID: <50FD463C.5030704@gmail.com> Date: Mon, 21 Jan 2013 17:44:28 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50FD2930.9010207@unity.pl> In-Reply-To: <50FD2930.9010207@unity.pl> Subject: Re: [Xen-API] XCP online resize vdi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Tm93YXksIHNvcnJ5LiBBRkFJSyB0aGlzIGlzIHJlc2VydmUgZm9yIHRoZSBmdXR1cmUuCgoyMS4w MS4yMDEzIDE1OjQwLCDFgXVrYXN6IE5vd2FrINC/0LjRiNC10YI6Cj4gSGksCj4gaG93IGNhbiBJ IGluY3JlYXNlIFZESSBzcGFjZSBvbmxpbmU/Cj4KPgo+IEkgdHJpZWQ6Cj4gW3Jvb3RAdXN5cWF4 YzAxIH5dIyB4ZSB2ZGktcmVzaXplIGRpc2stc2l6ZT0yMTQ3NDkzNjQ4Cj4gdXVpZD05NTc1ZDA3 Ni05N2E1LTQ4YWItYjFlMC1kODkwMDUzZWU4ZWYgb25saW5lPXRydWUKPiBUaGUgU1IgYmFja2Vu ZCBkb2VzIG5vdCBzdXBwb3J0IHRoZSBvcGVyYXRpb24gKGNoZWNrIHRoZSBTUidzIGFsbG93ZWQK PiBvcGVyYXRpb25zKQo+IHNyOiBmYTkzMzQzZS03YmUwLTczZGEtYzAxOS0zMTBkMmVkYmIzZGEg KGlzY3NpIC0gc2RtKQo+Cj4KPiBNeSBTUiB0eXBlIGlzOiBsdm1vaXNjc2kKPiBYQ1AgMS42Cj4K PiBMaW51eCBkaXN0cmlidXRpb24gaW4gdGhlIHZtIGlzIGRlYmlhbi4gSSBoYXZlIGluc3RhbGxl ZAo+IHhlLWd1ZXN0LXV0aWxpdGllcyBvbiB0aGUgdm0uCj4KPiBbcm9vdEB1c3lxYXhjMDEgfl0j IHhlIHZkaS1wYXJhbS1saXN0Cj4gdXVpZD05NTc1ZDA3Ni05N2E1LTQ4YWItYjFlMC1kODkwMDUz ZWU4ZWYgfCBncmVwIGFsbG93ZWQgb3BlcmF0aW9ucwo+Cj4KPiAgICAgICAgYWxsb3dlZC1vcGVy YXRpb25zIChTUk8pOiBjbG9uZTsgc25hcHNob3QKPgo+IFtyb290QHVzeXFheGMwMSB+XSMgeGUg c3ItcGFyYW0tbGlzdAo+IHV1aWQ9ZmE5MzM0M2UtN2JlMC03M2RhLWMwMTktMzEwZDJlZGJiM2Rh fGdyZXAgYWxsb3dlZC1vcGVyYXRpb25zCj4gICAgICAgIGFsbG93ZWQtb3BlcmF0aW9ucyAoU1JP KTogVkRJLmNyZWF0ZTsgVkRJLnNuYXBzaG90OyBQQkQuY3JlYXRlOwo+IFBCRC5kZXN0cm95OyBw bHVnOyB1cGRhdGU7IFZESS5kZXN0cm95OyBzY2FuOyBWREkuY2xvbmU7IFZESS5yZXNpemU7IHVu cGx1Zwo+Cj4KPgo+Cj4gQmVzdCByZWdhcmRzLAoKCl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMu eGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVu LWFwaQo= From xen-api-bounces@lists.xen.org Mon Jan 21 16:18:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 16:18:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxK4j-0007Jg-9V; Mon, 21 Jan 2013 16:18:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxK4h-0007JY-RC for xen-api@lists.xen.org; Mon, 21 Jan 2013 16:18:20 +0000 Received: from [193.109.254.147:10825] by server-14.bemta-14.messagelabs.com id 51/2B-15097-B4A6DF05; Mon, 21 Jan 2013 16:18:19 +0000 X-Env-Sender: theamazingdrew@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1358784999!9310264!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19252 invoked from network); 21 Jan 2013 16:16:41 -0000 Received: from mail-da0-f43.google.com (HELO mail-da0-f43.google.com) (209.85.210.43) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 16:16:41 -0000 Received: by mail-da0-f43.google.com with SMTP id u36so2782818dak.16 for ; Mon, 21 Jan 2013 08:16:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=Anboe/vFxvFVrJ/QG2ok1kRAvmgzt163MbzJJ8L747g=; b=eQR5pDkls/zwd5w4VCMx1nncVZwojpwt9WYkbDWXqpu3A3Os0tZZZ6bqbvn3BhQSp0 h63seJ2kSoTfJ7Jm9deE7tJrL4PoSJDE76ejVLOdlUZmVzLmQzXN2UXfXZNvORVDXpyT CMDM5Q5L/YTlN1ubIj0Q89Ffj5TytxVD3X/jjnTXIW7+wgLHmmslllFVceCfzV+gg4oC b1Z/4bSj9omgJbwXBWnWH0V2VstunDmIxFTsVECQ+CbOUJCPAR5M9cT8Vg5gl31ZtDl4 CmbjKGvTsuWg8X/jsPEQtV3J4bDnjhfCf4iC8yFfO0+Z6yVRa2l71YEWl+Wsvg4KQfLg c19A== MIME-Version: 1.0 X-Received: by 10.68.130.226 with SMTP id oh2mr49677861pbb.157.1358784999102; Mon, 21 Jan 2013 08:16:39 -0800 (PST) Received: by 10.66.192.136 with HTTP; Mon, 21 Jan 2013 08:16:38 -0800 (PST) Date: Mon, 21 Jan 2013 11:16:38 -0500 X-Google-Sender-Auth: IqKD5JTF8Ve--_dvY2JdKmVRc6Q Message-ID: From: Drew Brown To: xen-api@lists.xen.org Subject: [Xen-API] VM DNS Resolution Head-scratcher X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: dbrown@byu.net List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4007774239326833899==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4007774239326833899== Content-Type: multipart/alternative; boundary=047d7b10c7d33296c604d3cec998 --047d7b10c7d33296c604d3cec998 Content-Type: text/plain; charset=ISO-8859-1 Hi all, thanks for taking time to read this. I've got a two-week-old XCP 1.6 install that I'm trying out for my environment. It's running on a single-nic server I have lying around, and has been running about 6 VMs at any given time. So far, so good. Over the weekend we had a power outage that caused the server to go down. When I brought everything back up, I noticed one problem - that most of the VMs can't ping dns names (yahoo.com). They will ping ip addresses however on the internal network and across the internet. The host XCP machine has no DNS issues, and the switch appears to be acting fine. I have about 11 vms built, all ubuntu 12.04, built based on the 64-bit template. I built them by creating two gold images, and then copying those images to create the other vms using Fast Clone. I tested each vm, and what I found is as follows: - The gold vms resolve DNS just fine - One of the non-gold images resolves just fine - all the other "copies" of the gold images do not resolve The one catch here is, I may have created the one aforementioned working non-gold from scratch; e.g. it may not be a copy. If that's the case, then all the copies aren't resolving DNS, and all the originals are - but I'm not sure. Also of note, every time I make a copy of either of the gold images, DNS resolution is not working in the copy. Every vm has a static ip address in the 192.168.1.x range. No network configuration issues have been noted in /etc/network/interfaces. I have deleted and created new virtual nics on several virtual servers to no avail. I attempted to change network setting on the host machine to no avail. I have xs-tools running on all vms, and reinstalled it on one of the copies to no avail. Finally, I just installed a fresh VM from the standard Ubuntu 64 bit template, and it works great. Thoughts? Drew --047d7b10c7d33296c604d3cec998 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all, thanks for taking time to read this.

I've got a two-week-old XCP 1.6 install that I'm trying= out for my environment. It's running on a single-nic server I have lyi= ng around, and has been running about 6 VMs at any given time. So far, so g= ood.

Over the weekend we had a power outage that= caused the server to go down. When I brought everything back up, I noticed= one problem - that most of the VMs can't ping dns names (yahoo.com). They will ping ip addresses however on the = internal network and across the internet. The host XCP machine has no DNS i= ssues, and the switch appears to be acting fine.=A0

I have about 11 vms built, all ubuntu 12.04= , built based on the 64-bit template. I built them by creating two gold ima= ges, and then copying those images to create the other vms using Fast Clone= . I tested each vm, and what I found is as follows:

- The gold vms resolve DNS just fine
<= div style>- One of the non-gold images resolves just fine
-= all the other "copies" of the gold images do not resolve

The one catch here is, I may have created t= he one aforementioned working non-gold from scratch; e.g. it may not be a c= opy. If that's the case, then all the copies aren't resolving DNS, = and all the originals are - but I'm not sure. Also of note, every time = I make a copy of either of the gold images, DNS resolution is not working i= n the copy.

Every vm has a static ip address in the 192= .168.1.x range. No network configuration issues have been noted in /etc/net= work/interfaces. I have deleted and created new virtual nics on several vir= tual servers to no avail. I attempted to change network setting on the host= machine to no avail. I have xs-tools running on all vms, and reinstalled i= t on one of the copies to no avail.

Finally, I just installed a fresh VM from t= he standard Ubuntu 64 bit template, and it works great.
Thoughts?




Drew
<= br>



--047d7b10c7d33296c604d3cec998-- --===============4007774239326833899== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4007774239326833899==-- From xen-api-bounces@lists.xen.org Mon Jan 21 16:18:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 16:18:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxK4j-0007Jg-9V; Mon, 21 Jan 2013 16:18:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxK4h-0007JY-RC for xen-api@lists.xen.org; Mon, 21 Jan 2013 16:18:20 +0000 Received: from [193.109.254.147:10825] by server-14.bemta-14.messagelabs.com id 51/2B-15097-B4A6DF05; Mon, 21 Jan 2013 16:18:19 +0000 X-Env-Sender: theamazingdrew@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1358784999!9310264!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19252 invoked from network); 21 Jan 2013 16:16:41 -0000 Received: from mail-da0-f43.google.com (HELO mail-da0-f43.google.com) (209.85.210.43) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 16:16:41 -0000 Received: by mail-da0-f43.google.com with SMTP id u36so2782818dak.16 for ; Mon, 21 Jan 2013 08:16:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=Anboe/vFxvFVrJ/QG2ok1kRAvmgzt163MbzJJ8L747g=; b=eQR5pDkls/zwd5w4VCMx1nncVZwojpwt9WYkbDWXqpu3A3Os0tZZZ6bqbvn3BhQSp0 h63seJ2kSoTfJ7Jm9deE7tJrL4PoSJDE76ejVLOdlUZmVzLmQzXN2UXfXZNvORVDXpyT CMDM5Q5L/YTlN1ubIj0Q89Ffj5TytxVD3X/jjnTXIW7+wgLHmmslllFVceCfzV+gg4oC b1Z/4bSj9omgJbwXBWnWH0V2VstunDmIxFTsVECQ+CbOUJCPAR5M9cT8Vg5gl31ZtDl4 CmbjKGvTsuWg8X/jsPEQtV3J4bDnjhfCf4iC8yFfO0+Z6yVRa2l71YEWl+Wsvg4KQfLg c19A== MIME-Version: 1.0 X-Received: by 10.68.130.226 with SMTP id oh2mr49677861pbb.157.1358784999102; Mon, 21 Jan 2013 08:16:39 -0800 (PST) Received: by 10.66.192.136 with HTTP; Mon, 21 Jan 2013 08:16:38 -0800 (PST) Date: Mon, 21 Jan 2013 11:16:38 -0500 X-Google-Sender-Auth: IqKD5JTF8Ve--_dvY2JdKmVRc6Q Message-ID: From: Drew Brown To: xen-api@lists.xen.org Subject: [Xen-API] VM DNS Resolution Head-scratcher X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: dbrown@byu.net List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4007774239326833899==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4007774239326833899== Content-Type: multipart/alternative; boundary=047d7b10c7d33296c604d3cec998 --047d7b10c7d33296c604d3cec998 Content-Type: text/plain; charset=ISO-8859-1 Hi all, thanks for taking time to read this. I've got a two-week-old XCP 1.6 install that I'm trying out for my environment. It's running on a single-nic server I have lying around, and has been running about 6 VMs at any given time. So far, so good. Over the weekend we had a power outage that caused the server to go down. When I brought everything back up, I noticed one problem - that most of the VMs can't ping dns names (yahoo.com). They will ping ip addresses however on the internal network and across the internet. The host XCP machine has no DNS issues, and the switch appears to be acting fine. I have about 11 vms built, all ubuntu 12.04, built based on the 64-bit template. I built them by creating two gold images, and then copying those images to create the other vms using Fast Clone. I tested each vm, and what I found is as follows: - The gold vms resolve DNS just fine - One of the non-gold images resolves just fine - all the other "copies" of the gold images do not resolve The one catch here is, I may have created the one aforementioned working non-gold from scratch; e.g. it may not be a copy. If that's the case, then all the copies aren't resolving DNS, and all the originals are - but I'm not sure. Also of note, every time I make a copy of either of the gold images, DNS resolution is not working in the copy. Every vm has a static ip address in the 192.168.1.x range. No network configuration issues have been noted in /etc/network/interfaces. I have deleted and created new virtual nics on several virtual servers to no avail. I attempted to change network setting on the host machine to no avail. I have xs-tools running on all vms, and reinstalled it on one of the copies to no avail. Finally, I just installed a fresh VM from the standard Ubuntu 64 bit template, and it works great. Thoughts? Drew --047d7b10c7d33296c604d3cec998 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all, thanks for taking time to read this.

I've got a two-week-old XCP 1.6 install that I'm trying= out for my environment. It's running on a single-nic server I have lyi= ng around, and has been running about 6 VMs at any given time. So far, so g= ood.

Over the weekend we had a power outage that= caused the server to go down. When I brought everything back up, I noticed= one problem - that most of the VMs can't ping dns names (yahoo.com). They will ping ip addresses however on the = internal network and across the internet. The host XCP machine has no DNS i= ssues, and the switch appears to be acting fine.=A0

I have about 11 vms built, all ubuntu 12.04= , built based on the 64-bit template. I built them by creating two gold ima= ges, and then copying those images to create the other vms using Fast Clone= . I tested each vm, and what I found is as follows:

- The gold vms resolve DNS just fine
<= div style>- One of the non-gold images resolves just fine
-= all the other "copies" of the gold images do not resolve

The one catch here is, I may have created t= he one aforementioned working non-gold from scratch; e.g. it may not be a c= opy. If that's the case, then all the copies aren't resolving DNS, = and all the originals are - but I'm not sure. Also of note, every time = I make a copy of either of the gold images, DNS resolution is not working i= n the copy.

Every vm has a static ip address in the 192= .168.1.x range. No network configuration issues have been noted in /etc/net= work/interfaces. I have deleted and created new virtual nics on several vir= tual servers to no avail. I attempted to change network setting on the host= machine to no avail. I have xs-tools running on all vms, and reinstalled i= t on one of the copies to no avail.

Finally, I just installed a fresh VM from t= he standard Ubuntu 64 bit template, and it works great.
Thoughts?




Drew
<= br>



--047d7b10c7d33296c604d3cec998-- --===============4007774239326833899== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4007774239326833899==-- From xen-api-bounces@lists.xen.org Mon Jan 21 16:22:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 16:22:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxK8x-0007jK-Tn; Mon, 21 Jan 2013 16:22:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxK8x-0007j1-3b for xen-api@lists.xen.org; Mon, 21 Jan 2013 16:22:43 +0000 Received: from [85.158.143.99:5049] by server-2.bemta-4.messagelabs.com id BB/11-03518-25B6DF05; Mon, 21 Jan 2013 16:22:42 +0000 X-Env-Sender: theamazingdrew@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1358785359!23556248!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10191 invoked from network); 21 Jan 2013 16:22:41 -0000 Received: from mail-da0-f43.google.com (HELO mail-da0-f43.google.com) (209.85.210.43) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 16:22:41 -0000 Received: by mail-da0-f43.google.com with SMTP id u36so2793411dak.30 for ; Mon, 21 Jan 2013 08:22:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=OQuhkMnY8+AhqA0ErAdY4RNpBV1pCwjuYtMLc5VFvIc=; b=swjRfd1RkjqNV+KVecOYvn9OYtQtDteOQttiOKABCbf8opXM1XZb6EBtWag6nagQn8 jDAf+UCzptI/zgajr6Lh6EmrayvvjU+3ql0Sal1npgnjIopShQxoxb9pj7QN5EL1MK/F 0ydxC3KjekHFsNWx3qTiv2Td1oqvSmzFb+nkOopxdygwdzhggJz0x/flgn3NXYLDN818 IVyB0oIydXVdrQuytVVeenaaS7u2g4rNrAAFABiWpw2kiyk1JdKX4LZjL66lqwMjP3FR iTyaKj+2wZARIWoU7yBZQ5ozgOie9Jg2FTX9V0sZ6RWoclQPsrWGGIlQ7mvVwGz6C16C 9Kfg== MIME-Version: 1.0 X-Received: by 10.69.0.74 with SMTP id aw10mr30861621pbd.87.1358785359326; Mon, 21 Jan 2013 08:22:39 -0800 (PST) Received: by 10.66.192.136 with HTTP; Mon, 21 Jan 2013 08:22:39 -0800 (PST) Date: Mon, 21 Jan 2013 11:22:39 -0500 X-Google-Sender-Auth: FUokygbg9jZKmyuBpaTNyiRzKXU Message-ID: From: Drew Brown To: xen-api@lists.xen.org Subject: [Xen-API] VM DNS Resolution Head-scratcher - Correction X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: dbrown@byu.net List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1639630178115639041==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1639630178115639041== Content-Type: multipart/alternative; boundary=047d7b1633f5ab2f3804d3cede47 --047d7b1633f5ab2f3804d3cede47 Content-Type: text/plain; charset=ISO-8859-1 I erroneously stated in my previous email that resolution was not happening on servers cloned from my gold image. New clones are working, but the existing one will not. Drew --047d7b1633f5ab2f3804d3cede47 Content-Type: text/html; charset=ISO-8859-1
I erroneously stated in my previous email that resolution was not happening on servers cloned from my gold image. New clones are working, but the existing one will not.



Drew
--047d7b1633f5ab2f3804d3cede47-- --===============1639630178115639041== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1639630178115639041==-- From xen-api-bounces@lists.xen.org Mon Jan 21 16:22:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 16:22:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxK8x-0007jK-Tn; Mon, 21 Jan 2013 16:22:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxK8x-0007j1-3b for xen-api@lists.xen.org; Mon, 21 Jan 2013 16:22:43 +0000 Received: from [85.158.143.99:5049] by server-2.bemta-4.messagelabs.com id BB/11-03518-25B6DF05; Mon, 21 Jan 2013 16:22:42 +0000 X-Env-Sender: theamazingdrew@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1358785359!23556248!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10191 invoked from network); 21 Jan 2013 16:22:41 -0000 Received: from mail-da0-f43.google.com (HELO mail-da0-f43.google.com) (209.85.210.43) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 16:22:41 -0000 Received: by mail-da0-f43.google.com with SMTP id u36so2793411dak.30 for ; Mon, 21 Jan 2013 08:22:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=OQuhkMnY8+AhqA0ErAdY4RNpBV1pCwjuYtMLc5VFvIc=; b=swjRfd1RkjqNV+KVecOYvn9OYtQtDteOQttiOKABCbf8opXM1XZb6EBtWag6nagQn8 jDAf+UCzptI/zgajr6Lh6EmrayvvjU+3ql0Sal1npgnjIopShQxoxb9pj7QN5EL1MK/F 0ydxC3KjekHFsNWx3qTiv2Td1oqvSmzFb+nkOopxdygwdzhggJz0x/flgn3NXYLDN818 IVyB0oIydXVdrQuytVVeenaaS7u2g4rNrAAFABiWpw2kiyk1JdKX4LZjL66lqwMjP3FR iTyaKj+2wZARIWoU7yBZQ5ozgOie9Jg2FTX9V0sZ6RWoclQPsrWGGIlQ7mvVwGz6C16C 9Kfg== MIME-Version: 1.0 X-Received: by 10.69.0.74 with SMTP id aw10mr30861621pbd.87.1358785359326; Mon, 21 Jan 2013 08:22:39 -0800 (PST) Received: by 10.66.192.136 with HTTP; Mon, 21 Jan 2013 08:22:39 -0800 (PST) Date: Mon, 21 Jan 2013 11:22:39 -0500 X-Google-Sender-Auth: FUokygbg9jZKmyuBpaTNyiRzKXU Message-ID: From: Drew Brown To: xen-api@lists.xen.org Subject: [Xen-API] VM DNS Resolution Head-scratcher - Correction X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: dbrown@byu.net List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1639630178115639041==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1639630178115639041== Content-Type: multipart/alternative; boundary=047d7b1633f5ab2f3804d3cede47 --047d7b1633f5ab2f3804d3cede47 Content-Type: text/plain; charset=ISO-8859-1 I erroneously stated in my previous email that resolution was not happening on servers cloned from my gold image. New clones are working, but the existing one will not. Drew --047d7b1633f5ab2f3804d3cede47 Content-Type: text/html; charset=ISO-8859-1
I erroneously stated in my previous email that resolution was not happening on servers cloned from my gold image. New clones are working, but the existing one will not.



Drew
--047d7b1633f5ab2f3804d3cede47-- --===============1639630178115639041== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1639630178115639041==-- From xen-api-bounces@lists.xen.org Mon Jan 21 16:37:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 16:37:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxKNB-0000Dw-HI; Mon, 21 Jan 2013 16:37:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxKN9-0000Dl-TR for xen-api@lists.xen.org; Mon, 21 Jan 2013 16:37:24 +0000 Received: from [85.158.143.35:20024] by server-1.bemta-4.messagelabs.com id FA/7C-05635-3CE6DF05; Mon, 21 Jan 2013 16:37:23 +0000 X-Env-Sender: theamazingdrew@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1358786218!5234593!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6577 invoked from network); 21 Jan 2013 16:37:01 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 16:37:01 -0000 Received: by mail-pa0-f54.google.com with SMTP id bi5so3478665pad.13 for ; Mon, 21 Jan 2013 08:36:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=36xi0ckWTBSrPC2M/6UMdrcAUCC8a1L0JYck7y8krXQ=; b=tNZGCnLmNkBeHBh3/O6rL+Y4T13DkXk9NVgvh3h4kKdnAquhKt3ekhnW52WzdobXOu dGoyFXRrspembfDq6Gh+aaBIG5ddTHIWzr0t4TVod4Sdgysy9pwbZdCFs/pexFsQ49UT Z2qsH80lGE/vqT6RLKurAibywDtGg9jnJnPu+SzEpbd0xwQ6f3lURwzGHVM2nnn/5cBP SBdBl47r0ChqTebPkdeCijafIL2/KxxkY+JgwOw4WEwgI0UKFA1bVq0vGTzLW9y+obAN K1LODtlwLpYMEzPgWBTEtsjnU39XL/xypLJiL+Lc02cVdSEA9UqACIPw/a9OpDSA0XvO WE1Q== MIME-Version: 1.0 X-Received: by 10.69.0.74 with SMTP id aw10mr30972173pbd.87.1358786217937; Mon, 21 Jan 2013 08:36:57 -0800 (PST) Received: by 10.66.192.136 with HTTP; Mon, 21 Jan 2013 08:36:57 -0800 (PST) Date: Mon, 21 Jan 2013 11:36:57 -0500 X-Google-Sender-Auth: 7a5UqmP8fY6oV382G7SzWP2ygdY Message-ID: From: Drew Brown To: xen-api@lists.xen.org Subject: [Xen-API] VM DNS Resolution Head-scratcher - Never Mind... X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: dbrown@byu.net List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5195967513826010754==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5195967513826010754== Content-Type: multipart/alternative; boundary=047d7b1633f5d889a204d3cf11cd --047d7b1633f5d889a204d3cf11cd Content-Type: text/plain; charset=ISO-8859-1 Figured it out - network configuration issue - didn't update resolv.conf, and the one clone that was working was still on DHCP. I apologize for cluttering the mailing list. Drew --047d7b1633f5d889a204d3cf11cd Content-Type: text/html; charset=ISO-8859-1
Figured it out - network configuration issue - didn't update resolv.conf, and the one clone that was working was still on DHCP. I apologize for cluttering the mailing list.


Drew
--047d7b1633f5d889a204d3cf11cd-- --===============5195967513826010754== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5195967513826010754==-- From xen-api-bounces@lists.xen.org Mon Jan 21 16:37:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 16:37:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxKNB-0000Dw-HI; Mon, 21 Jan 2013 16:37:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxKN9-0000Dl-TR for xen-api@lists.xen.org; Mon, 21 Jan 2013 16:37:24 +0000 Received: from [85.158.143.35:20024] by server-1.bemta-4.messagelabs.com id FA/7C-05635-3CE6DF05; Mon, 21 Jan 2013 16:37:23 +0000 X-Env-Sender: theamazingdrew@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1358786218!5234593!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6577 invoked from network); 21 Jan 2013 16:37:01 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 16:37:01 -0000 Received: by mail-pa0-f54.google.com with SMTP id bi5so3478665pad.13 for ; Mon, 21 Jan 2013 08:36:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=36xi0ckWTBSrPC2M/6UMdrcAUCC8a1L0JYck7y8krXQ=; b=tNZGCnLmNkBeHBh3/O6rL+Y4T13DkXk9NVgvh3h4kKdnAquhKt3ekhnW52WzdobXOu dGoyFXRrspembfDq6Gh+aaBIG5ddTHIWzr0t4TVod4Sdgysy9pwbZdCFs/pexFsQ49UT Z2qsH80lGE/vqT6RLKurAibywDtGg9jnJnPu+SzEpbd0xwQ6f3lURwzGHVM2nnn/5cBP SBdBl47r0ChqTebPkdeCijafIL2/KxxkY+JgwOw4WEwgI0UKFA1bVq0vGTzLW9y+obAN K1LODtlwLpYMEzPgWBTEtsjnU39XL/xypLJiL+Lc02cVdSEA9UqACIPw/a9OpDSA0XvO WE1Q== MIME-Version: 1.0 X-Received: by 10.69.0.74 with SMTP id aw10mr30972173pbd.87.1358786217937; Mon, 21 Jan 2013 08:36:57 -0800 (PST) Received: by 10.66.192.136 with HTTP; Mon, 21 Jan 2013 08:36:57 -0800 (PST) Date: Mon, 21 Jan 2013 11:36:57 -0500 X-Google-Sender-Auth: 7a5UqmP8fY6oV382G7SzWP2ygdY Message-ID: From: Drew Brown To: xen-api@lists.xen.org Subject: [Xen-API] VM DNS Resolution Head-scratcher - Never Mind... X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: dbrown@byu.net List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5195967513826010754==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5195967513826010754== Content-Type: multipart/alternative; boundary=047d7b1633f5d889a204d3cf11cd --047d7b1633f5d889a204d3cf11cd Content-Type: text/plain; charset=ISO-8859-1 Figured it out - network configuration issue - didn't update resolv.conf, and the one clone that was working was still on DHCP. I apologize for cluttering the mailing list. Drew --047d7b1633f5d889a204d3cf11cd Content-Type: text/html; charset=ISO-8859-1
Figured it out - network configuration issue - didn't update resolv.conf, and the one clone that was working was still on DHCP. I apologize for cluttering the mailing list.


Drew
--047d7b1633f5d889a204d3cf11cd-- --===============5195967513826010754== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5195967513826010754==-- From xen-api-bounces@lists.xen.org Mon Jan 21 18:18:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 18:18:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxLwe-00064i-CM; Mon, 21 Jan 2013 18:18:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxLwc-00064D-Pa for xen-api@lists.xen.org; Mon, 21 Jan 2013 18:18:06 +0000 Received: from [85.158.143.35:44344] by server-3.bemta-4.messagelabs.com id 39/97-10689-E568DF05; Mon, 21 Jan 2013 18:18:06 +0000 X-Env-Sender: Vishwanath.Rawat@netapp.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1358792282!6266270!1 X-Originating-IP: [216.240.18.77] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE2LjI0MC4xOC43NyA9PiA0MDM1MA==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8984 invoked from network); 21 Jan 2013 18:18:04 -0000 Received: from mx12.netapp.com (HELO mx12.netapp.com) (216.240.18.77) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 18:18:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,508,1355126400"; d="scan'208,217";a="10095622" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 21 Jan 2013 10:18:02 -0800 Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0LII12h011781 for ; Mon, 21 Jan 2013 10:18:02 -0800 (PST) Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.14]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0328.009; Mon, 21 Jan 2013 10:18:01 -0800 From: "Rawat, Vishwanath" To: "xen-api@lists.xen.org" Thread-Topic: VM Migration Thread-Index: Ac33+OeqHnhY2v4qQ3+kjxm30/vuEA== Date: Mon, 21 Jan 2013 18:18:00 +0000 Message-ID: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] MIME-Version: 1.0 Subject: [Xen-API] VM Migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4343655080469206001==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4343655080469206001== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7B89652AC48EE14E979D933CF09A0F1016ED9790SACEXCMBX04PRDh_" --_000_7B89652AC48EE14E979D933CF09A0F1016ED9790SACEXCMBX04PRDh_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I am writing some perl scripts to do VM Migration using Xen= APIs. This is the API call I am using to do VM Migration pool_migrate (session_id s, VM ref vm, host ref host, (string -> string) Ma= p options). Now it is also possible to migrate datastore along with VM. I would like to= know what is the option that I can pass to above function so that it will = also migrate datastore. Regards, Rawat --_000_7B89652AC48EE14E979D933CF09A0F1016ED9790SACEXCMBX04PRDh_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

        &nbs= p;       I am writing some perl scripts to do= VM Migration using Xen APIs.

This is the API call I am using to do VM Migration

 

= pool_migrate (session_id s, VM ref vm, host ref host, (string -> string)= Map options).

=  

= Now it is also possible to migrate datastore along with VM. I would like to= know what is the option that I can pass to above function so that it will = also migrate datastore.

=  

= Regards,

= Rawat

=  

 

--_000_7B89652AC48EE14E979D933CF09A0F1016ED9790SACEXCMBX04PRDh_-- --===============4343655080469206001== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4343655080469206001==-- From xen-api-bounces@lists.xen.org Mon Jan 21 18:18:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 18:18:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxLwe-00064i-CM; Mon, 21 Jan 2013 18:18:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxLwc-00064D-Pa for xen-api@lists.xen.org; Mon, 21 Jan 2013 18:18:06 +0000 Received: from [85.158.143.35:44344] by server-3.bemta-4.messagelabs.com id 39/97-10689-E568DF05; Mon, 21 Jan 2013 18:18:06 +0000 X-Env-Sender: Vishwanath.Rawat@netapp.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1358792282!6266270!1 X-Originating-IP: [216.240.18.77] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE2LjI0MC4xOC43NyA9PiA0MDM1MA==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8984 invoked from network); 21 Jan 2013 18:18:04 -0000 Received: from mx12.netapp.com (HELO mx12.netapp.com) (216.240.18.77) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 18:18:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,508,1355126400"; d="scan'208,217";a="10095622" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 21 Jan 2013 10:18:02 -0800 Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0LII12h011781 for ; Mon, 21 Jan 2013 10:18:02 -0800 (PST) Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.14]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0328.009; Mon, 21 Jan 2013 10:18:01 -0800 From: "Rawat, Vishwanath" To: "xen-api@lists.xen.org" Thread-Topic: VM Migration Thread-Index: Ac33+OeqHnhY2v4qQ3+kjxm30/vuEA== Date: Mon, 21 Jan 2013 18:18:00 +0000 Message-ID: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] MIME-Version: 1.0 Subject: [Xen-API] VM Migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4343655080469206001==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4343655080469206001== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7B89652AC48EE14E979D933CF09A0F1016ED9790SACEXCMBX04PRDh_" --_000_7B89652AC48EE14E979D933CF09A0F1016ED9790SACEXCMBX04PRDh_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I am writing some perl scripts to do VM Migration using Xen= APIs. This is the API call I am using to do VM Migration pool_migrate (session_id s, VM ref vm, host ref host, (string -> string) Ma= p options). Now it is also possible to migrate datastore along with VM. I would like to= know what is the option that I can pass to above function so that it will = also migrate datastore. Regards, Rawat --_000_7B89652AC48EE14E979D933CF09A0F1016ED9790SACEXCMBX04PRDh_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

        &nbs= p;       I am writing some perl scripts to do= VM Migration using Xen APIs.

This is the API call I am using to do VM Migration

 

= pool_migrate (session_id s, VM ref vm, host ref host, (string -> string)= Map options).

=  

= Now it is also possible to migrate datastore along with VM. I would like to= know what is the option that I can pass to above function so that it will = also migrate datastore.

=  

= Regards,

= Rawat

=  

 

--_000_7B89652AC48EE14E979D933CF09A0F1016ED9790SACEXCMBX04PRDh_-- --===============4343655080469206001== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4343655080469206001==-- From xen-api-bounces@lists.xen.org Mon Jan 21 21:41:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 21:41:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxP7Z-0000YO-Bf; Mon, 21 Jan 2013 21:41:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxP7Y-0000YJ-0v for xen-api@lists.xen.org; Mon, 21 Jan 2013 21:41:36 +0000 Received: from [85.158.143.99:59219] by server-2.bemta-4.messagelabs.com id 8B/0B-03518-F06BDF05; Mon, 21 Jan 2013 21:41:35 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1358804494!19269018!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20359 invoked from network); 21 Jan 2013 21:41:34 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 21:41:34 -0000 Received: by mail-la0-f44.google.com with SMTP id eb20so5623017lab.31 for ; Mon, 21 Jan 2013 13:41:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=Ng4DgGNqKjDt4PGXqo9bDu7D5vlf00rU58+xUZakB+E=; b=cCFJIx34z2KzhCUEJGf0o/y3Nqt1yWpljKpYmeoxIozxg4hqh5gsXYxHn3GFutel7W 222RJJzkx5WjX/RaprfdlDfwyuabDxkhPH3OvMRkKsYrQhHosRnQDdp+wLjqpS43hgzq KpYS2RDOcQJpcundJQteQZjYNZscpHkShQ1E6A5ilHsJRjOmNAlOeaZt+yczHdQ+VtUm kERKGb0+8HceBlI/9ch3gzC5NJ2FI3srzdYr5yWDoq01Gkx/nx8tEiG+0qor9Dc3UACW pgQ/cRaJdt7pG6b1JpypzjnzsjhBQYIVc3N65O2lDjHJSz5OBpfIBYAj8ZKvxb7MYcPj FsiQ== X-Received: by 10.152.113.66 with SMTP id iw2mr18609829lab.37.1358804494167; Mon, 21 Jan 2013 13:41:34 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id to7sm6077675lab.13.2013.01.21.13.41.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jan 2013 13:41:33 -0800 (PST) Message-ID: <50FDB60D.7050509@gmail.com> Date: Tue, 22 Jan 2013 01:41:33 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: "'xen-api@lists.xen.org'" Subject: [Xen-API] Fighting for right commit: xen-api-libs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Good day, all. After 'diff-based differential evolution' allows to get the right commit for xen-api-libs: 629b5db569c21d7b01258b39706aeebad36269c2. (no difference at all with xen-api-libs-0.1.rpm from xcp 1.6 source.iso). Interesting - it came from 'master' branch, not tampa. Any suggestions about 'how to build all that stuff together' appreciated. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 21 21:41:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 21 Jan 2013 21:41:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxP7Z-0000YO-Bf; Mon, 21 Jan 2013 21:41:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxP7Y-0000YJ-0v for xen-api@lists.xen.org; Mon, 21 Jan 2013 21:41:36 +0000 Received: from [85.158.143.99:59219] by server-2.bemta-4.messagelabs.com id 8B/0B-03518-F06BDF05; Mon, 21 Jan 2013 21:41:35 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1358804494!19269018!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20359 invoked from network); 21 Jan 2013 21:41:34 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2013 21:41:34 -0000 Received: by mail-la0-f44.google.com with SMTP id eb20so5623017lab.31 for ; Mon, 21 Jan 2013 13:41:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=Ng4DgGNqKjDt4PGXqo9bDu7D5vlf00rU58+xUZakB+E=; b=cCFJIx34z2KzhCUEJGf0o/y3Nqt1yWpljKpYmeoxIozxg4hqh5gsXYxHn3GFutel7W 222RJJzkx5WjX/RaprfdlDfwyuabDxkhPH3OvMRkKsYrQhHosRnQDdp+wLjqpS43hgzq KpYS2RDOcQJpcundJQteQZjYNZscpHkShQ1E6A5ilHsJRjOmNAlOeaZt+yczHdQ+VtUm kERKGb0+8HceBlI/9ch3gzC5NJ2FI3srzdYr5yWDoq01Gkx/nx8tEiG+0qor9Dc3UACW pgQ/cRaJdt7pG6b1JpypzjnzsjhBQYIVc3N65O2lDjHJSz5OBpfIBYAj8ZKvxb7MYcPj FsiQ== X-Received: by 10.152.113.66 with SMTP id iw2mr18609829lab.37.1358804494167; Mon, 21 Jan 2013 13:41:34 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id to7sm6077675lab.13.2013.01.21.13.41.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jan 2013 13:41:33 -0800 (PST) Message-ID: <50FDB60D.7050509@gmail.com> Date: Tue, 22 Jan 2013 01:41:33 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: "'xen-api@lists.xen.org'" Subject: [Xen-API] Fighting for right commit: xen-api-libs X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Good day, all. After 'diff-based differential evolution' allows to get the right commit for xen-api-libs: 629b5db569c21d7b01258b39706aeebad36269c2. (no difference at all with xen-api-libs-0.1.rpm from xcp 1.6 source.iso). Interesting - it came from 'master' branch, not tampa. Any suggestions about 'how to build all that stuff together' appreciated. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 22 01:52:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 01:52:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxT20-0007co-1k; Tue, 22 Jan 2013 01:52:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxT1y-0007cg-FH for xen-api@lists.xen.org; Tue, 22 Jan 2013 01:52:06 +0000 Received: from [85.158.139.211:28156] by server-15.bemta-5.messagelabs.com id D4/EF-12730-4C0FDF05; Tue, 22 Jan 2013 01:52:04 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1358819522!17589818!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6377 invoked from network); 22 Jan 2013 01:52:03 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 01:52:03 -0000 Received: by mail-lb0-f180.google.com with SMTP id gj3so4790701lbb.25 for ; Mon, 21 Jan 2013 17:52:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=W7eq/8YqGDSUIlcJfzpZYydrgc9kwQeIV/lXLFsp+Rc=; b=NjTlA7beXJX/Ied2kcSnMQ2gJvm5+EGtpKh4e8P4RoZnKhVFfdcYV2zUUW4envYWP7 erdx5ichs6UxEyu64OOL2Y1i2tpXjL1nVic/C80tNDUgQsUypTt9HKcPEpFKedpWnm+G HNTQUEPMaAYpFG+NIaDcTFPEiWTGrU9gBfhlmkhMd7dUdkbEQ4clVHd3yXbxQZM6QzEk 1d1/cWkfPubHfzqGksrCq4R7sLwFnzK5jvIHDVwd7tKwhkaL96BoqMmRDXx5Upxz5Guq HZAO1MaoOKfFq5+n3YfT/2bLR9+ZR23eoP6KKwD4nIjh4JNcQMl7soyh9ouLy2ZX/pXS 5m5Q== X-Received: by 10.152.112.36 with SMTP id in4mr19432247lab.35.1358819522227; Mon, 21 Jan 2013 17:52:02 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id z4sm6244468lbn.17.2013.01.21.17.52.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jan 2013 17:52:01 -0800 (PST) Message-ID: <50FDF0C0.1070605@gmail.com> Date: Tue, 22 Jan 2013 05:52:00 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> In-Reply-To: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> Subject: Re: [Xen-API] VM Migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8119691879513259093==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8119691879513259093== Content-Type: multipart/alternative; boundary="------------020605090407050202000403" This is a multi-part message in MIME format. --------------020605090407050202000403 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit I think you using outdated API documentation. Not sure about API call, but corresponding xe call can contains remote-host, remote-username, remote-password and so on. On 21.01.2013 22:18, Rawat, Vishwanath wrote: > > Hi All, > > I am writing some perl scripts to do VM Migration > using Xen APIs. > > This is the API call I am using to do VM Migration > > pool_migrate (session_id s, VM ref vm, host ref host, (string -> > string) Map options). > > Now it is also possible to migrate datastore along with VM. I would > like to know what is the option that I can pass to above function so > that it will also migrate datastore. > > Regards, > > Rawat > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------020605090407050202000403 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit I think you using outdated API documentation. Not sure about API call, but corresponding xe call can contains remote-host, remote-username, remote-password and so on.

On 21.01.2013 22:18, Rawat, Vishwanath wrote:

Hi All,

                I am writing some perl scripts to do VM Migration using Xen APIs.

This is the API call I am using to do VM Migration

 

pool_migrate (session_id s, VM ref vm, host ref host, (string -> string) Map options).

 

Now it is also possible to migrate datastore along with VM. I would like to know what is the option that I can pass to above function so that it will also migrate datastore.

 

Regards,

Rawat

 

 



_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------020605090407050202000403-- --===============8119691879513259093== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8119691879513259093==-- From xen-api-bounces@lists.xen.org Tue Jan 22 01:52:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 01:52:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxT20-0007co-1k; Tue, 22 Jan 2013 01:52:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxT1y-0007cg-FH for xen-api@lists.xen.org; Tue, 22 Jan 2013 01:52:06 +0000 Received: from [85.158.139.211:28156] by server-15.bemta-5.messagelabs.com id D4/EF-12730-4C0FDF05; Tue, 22 Jan 2013 01:52:04 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1358819522!17589818!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6377 invoked from network); 22 Jan 2013 01:52:03 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 01:52:03 -0000 Received: by mail-lb0-f180.google.com with SMTP id gj3so4790701lbb.25 for ; Mon, 21 Jan 2013 17:52:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=W7eq/8YqGDSUIlcJfzpZYydrgc9kwQeIV/lXLFsp+Rc=; b=NjTlA7beXJX/Ied2kcSnMQ2gJvm5+EGtpKh4e8P4RoZnKhVFfdcYV2zUUW4envYWP7 erdx5ichs6UxEyu64OOL2Y1i2tpXjL1nVic/C80tNDUgQsUypTt9HKcPEpFKedpWnm+G HNTQUEPMaAYpFG+NIaDcTFPEiWTGrU9gBfhlmkhMd7dUdkbEQ4clVHd3yXbxQZM6QzEk 1d1/cWkfPubHfzqGksrCq4R7sLwFnzK5jvIHDVwd7tKwhkaL96BoqMmRDXx5Upxz5Guq HZAO1MaoOKfFq5+n3YfT/2bLR9+ZR23eoP6KKwD4nIjh4JNcQMl7soyh9ouLy2ZX/pXS 5m5Q== X-Received: by 10.152.112.36 with SMTP id in4mr19432247lab.35.1358819522227; Mon, 21 Jan 2013 17:52:02 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id z4sm6244468lbn.17.2013.01.21.17.52.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jan 2013 17:52:01 -0800 (PST) Message-ID: <50FDF0C0.1070605@gmail.com> Date: Tue, 22 Jan 2013 05:52:00 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> In-Reply-To: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> Subject: Re: [Xen-API] VM Migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8119691879513259093==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8119691879513259093== Content-Type: multipart/alternative; boundary="------------020605090407050202000403" This is a multi-part message in MIME format. --------------020605090407050202000403 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit I think you using outdated API documentation. Not sure about API call, but corresponding xe call can contains remote-host, remote-username, remote-password and so on. On 21.01.2013 22:18, Rawat, Vishwanath wrote: > > Hi All, > > I am writing some perl scripts to do VM Migration > using Xen APIs. > > This is the API call I am using to do VM Migration > > pool_migrate (session_id s, VM ref vm, host ref host, (string -> > string) Map options). > > Now it is also possible to migrate datastore along with VM. I would > like to know what is the option that I can pass to above function so > that it will also migrate datastore. > > Regards, > > Rawat > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------020605090407050202000403 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit I think you using outdated API documentation. Not sure about API call, but corresponding xe call can contains remote-host, remote-username, remote-password and so on.

On 21.01.2013 22:18, Rawat, Vishwanath wrote:

Hi All,

                I am writing some perl scripts to do VM Migration using Xen APIs.

This is the API call I am using to do VM Migration

 

pool_migrate (session_id s, VM ref vm, host ref host, (string -> string) Map options).

 

Now it is also possible to migrate datastore along with VM. I would like to know what is the option that I can pass to above function so that it will also migrate datastore.

 

Regards,

Rawat

 

 



_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------020605090407050202000403-- --===============8119691879513259093== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8119691879513259093==-- From xen-api-bounces@lists.xen.org Tue Jan 22 03:15:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 03:15:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxUKN-000094-PX; Tue, 22 Jan 2013 03:15:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxUKM-00008r-4F for Xen-api@lists.xen.org; Tue, 22 Jan 2013 03:15:10 +0000 Received: from [85.158.137.99:55146] by server-3.bemta-3.messagelabs.com id 18/39-17026-D340EF05; Tue, 22 Jan 2013 03:15:09 +0000 X-Env-Sender: k110168@gmail.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1358824506!12801172!1 X-Originating-IP: [209.85.216.172] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17169 invoked from network); 22 Jan 2013 03:15:08 -0000 Received: from mail-qc0-f172.google.com (HELO mail-qc0-f172.google.com) (209.85.216.172) by server-6.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 03:15:08 -0000 Received: by mail-qc0-f172.google.com with SMTP id b25so2624091qca.31 for ; Mon, 21 Jan 2013 19:15:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=SudpkMM8DllxdJ44ODekU5X/3dKUZfPlF8W486Y8fXw=; b=f3uERoE1O5DnO33cLFCYezWL+gD5Fji6pyk/ZG3iF/95J8wPWuXD299XUDvU33/Q5/ Sn8f+vkg4SMtLO2MnKGBANrzjWDd3ITO5lKq13vlXd57K+vw43FOuVRaD7azbow93rdE vlmtIEIK1zXQaM9XUskhzVjl5cSDKMxHrdd+TRIjuHZ8fWSTqE08tVJZf+gSO6R/P8/4 LyNUISNX03MVEpigmXCKjIzsJR1p6NKNR5HIm8yLnQZI3BEMQTkFx2Z2aQQoZLV3ZW0u 5u02t23ds3YjeCHruKjCw8vnRYgJpPR7YBo059tYZvOvObBD1r0ayK3kW6o1uIsxjQ+k bR8A== MIME-Version: 1.0 X-Received: by 10.224.41.196 with SMTP id p4mr21761389qae.92.1358824506463; Mon, 21 Jan 2013 19:15:06 -0800 (PST) Received: by 10.49.87.101 with HTTP; Mon, 21 Jan 2013 19:15:06 -0800 (PST) Date: Tue, 22 Jan 2013 11:15:06 +0800 Message-ID: From: ND KK To: Xen-api@lists.xen.org Subject: [Xen-API] A question of Virtual Disk(VHD) size in thin provisioning NFS SR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1735791444712601680==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1735791444712601680== Content-Type: multipart/alternative; boundary=20cf3074b4d605176304d3d7fc37 --20cf3074b4d605176304d3d7fc37 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I have a question. But my English is very poor, I hope you will understand My VM has one virtual disk which *allocated **100G** * I find the utilization of this disk in *guest OS is **39.5G *( Get utilization on guest OS file system) but I ssh to the NFS server check the VHD files size I use command:* ls -lh VHD_FILE_NAME *( Get utilization on NFS server file system) It show that *-rw-r--r-- 1 root root 19G Jan 22 2013 XXXXXXX.vhd* * * Then, I use command:* du -sh VHD_FILE_NAM*E ( Get physical utilization on disk ) It show that *5.5G XXXXXXXX.vhd* * * * * *My question is what happen in this **process ( 100G -> 39.5G -> 19G -> 5.5G )**? * Are they representing XenServer's thin provision, VHD's thin provision and File System sparse file ? Does XenServer's thin provision equals VHD's thin provision? VHD's thin provision equals File System sparse file ? If yes, what happen in this process?* * Thanks - Best Regards, Leo Hsu --20cf3074b4d605176304d3d7fc37 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,=A0
I have a question. But my English = is very poor,=A0I hope you will understand

My VM has one virtual disk which allocated 100G=A0

I find the utilization of this disk i= n guest OS is 39.5G=A0( Get=A0utilizatio= n on guest OS file system)

but =A0I ssh to the NFS server check the VHD files size
I use = command: ls -lh =A0VHD_FILE_NAME=A0( Get utilization = on NFS server file system)
It show that=A0<= /div>
<= i>-rw-r--r-- 1 root root 19G Jan 22 =A02013 XXXXXXX.vhd
=
Then, I=A0use command: du -sh=A0VHD_FILE_NAM<= /i>E ( Get physical utilization on disk=A0)
It show that=A0<= /div>
5.5G<= /b>=A0=A0XXXXXXXX.vhd


My question is what happen in this=A0process ( 100G -> 39.5G -> 19G = -> 5.5G )?=A0

Are they representing=A0=A0XenServer's thin provision,=A0VHD's t= hin provision and=A0File System sparse file ?

=
Does XenServer's thin provision equals VHD's thin provision?=A0<= /span>VHD's= thin provision equals File System sparse file ?

If yes,=A0=A0what happen in this=A0process?

Thanks

-
= Best Regards,
Leo Hsu
--20cf3074b4d605176304d3d7fc37-- --===============1735791444712601680== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1735791444712601680==-- From xen-api-bounces@lists.xen.org Tue Jan 22 03:15:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 03:15:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxUKN-000094-PX; Tue, 22 Jan 2013 03:15:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxUKM-00008r-4F for Xen-api@lists.xen.org; Tue, 22 Jan 2013 03:15:10 +0000 Received: from [85.158.137.99:55146] by server-3.bemta-3.messagelabs.com id 18/39-17026-D340EF05; Tue, 22 Jan 2013 03:15:09 +0000 X-Env-Sender: k110168@gmail.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1358824506!12801172!1 X-Originating-IP: [209.85.216.172] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17169 invoked from network); 22 Jan 2013 03:15:08 -0000 Received: from mail-qc0-f172.google.com (HELO mail-qc0-f172.google.com) (209.85.216.172) by server-6.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 03:15:08 -0000 Received: by mail-qc0-f172.google.com with SMTP id b25so2624091qca.31 for ; Mon, 21 Jan 2013 19:15:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=SudpkMM8DllxdJ44ODekU5X/3dKUZfPlF8W486Y8fXw=; b=f3uERoE1O5DnO33cLFCYezWL+gD5Fji6pyk/ZG3iF/95J8wPWuXD299XUDvU33/Q5/ Sn8f+vkg4SMtLO2MnKGBANrzjWDd3ITO5lKq13vlXd57K+vw43FOuVRaD7azbow93rdE vlmtIEIK1zXQaM9XUskhzVjl5cSDKMxHrdd+TRIjuHZ8fWSTqE08tVJZf+gSO6R/P8/4 LyNUISNX03MVEpigmXCKjIzsJR1p6NKNR5HIm8yLnQZI3BEMQTkFx2Z2aQQoZLV3ZW0u 5u02t23ds3YjeCHruKjCw8vnRYgJpPR7YBo059tYZvOvObBD1r0ayK3kW6o1uIsxjQ+k bR8A== MIME-Version: 1.0 X-Received: by 10.224.41.196 with SMTP id p4mr21761389qae.92.1358824506463; Mon, 21 Jan 2013 19:15:06 -0800 (PST) Received: by 10.49.87.101 with HTTP; Mon, 21 Jan 2013 19:15:06 -0800 (PST) Date: Tue, 22 Jan 2013 11:15:06 +0800 Message-ID: From: ND KK To: Xen-api@lists.xen.org Subject: [Xen-API] A question of Virtual Disk(VHD) size in thin provisioning NFS SR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1735791444712601680==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1735791444712601680== Content-Type: multipart/alternative; boundary=20cf3074b4d605176304d3d7fc37 --20cf3074b4d605176304d3d7fc37 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I have a question. But my English is very poor, I hope you will understand My VM has one virtual disk which *allocated **100G** * I find the utilization of this disk in *guest OS is **39.5G *( Get utilization on guest OS file system) but I ssh to the NFS server check the VHD files size I use command:* ls -lh VHD_FILE_NAME *( Get utilization on NFS server file system) It show that *-rw-r--r-- 1 root root 19G Jan 22 2013 XXXXXXX.vhd* * * Then, I use command:* du -sh VHD_FILE_NAM*E ( Get physical utilization on disk ) It show that *5.5G XXXXXXXX.vhd* * * * * *My question is what happen in this **process ( 100G -> 39.5G -> 19G -> 5.5G )**? * Are they representing XenServer's thin provision, VHD's thin provision and File System sparse file ? Does XenServer's thin provision equals VHD's thin provision? VHD's thin provision equals File System sparse file ? If yes, what happen in this process?* * Thanks - Best Regards, Leo Hsu --20cf3074b4d605176304d3d7fc37 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,=A0
I have a question. But my English = is very poor,=A0I hope you will understand

My VM has one virtual disk which allocated 100G=A0

I find the utilization of this disk i= n guest OS is 39.5G=A0( Get=A0utilizatio= n on guest OS file system)

but =A0I ssh to the NFS server check the VHD files size
I use = command: ls -lh =A0VHD_FILE_NAME=A0( Get utilization = on NFS server file system)
It show that=A0<= /div>
<= i>-rw-r--r-- 1 root root 19G Jan 22 =A02013 XXXXXXX.vhd
=
Then, I=A0use command: du -sh=A0VHD_FILE_NAM<= /i>E ( Get physical utilization on disk=A0)
It show that=A0<= /div>
5.5G<= /b>=A0=A0XXXXXXXX.vhd


My question is what happen in this=A0process ( 100G -> 39.5G -> 19G = -> 5.5G )?=A0

Are they representing=A0=A0XenServer's thin provision,=A0VHD's t= hin provision and=A0File System sparse file ?

=
Does XenServer's thin provision equals VHD's thin provision?=A0<= /span>VHD's= thin provision equals File System sparse file ?

If yes,=A0=A0what happen in this=A0process?

Thanks

-
= Best Regards,
Leo Hsu
--20cf3074b4d605176304d3d7fc37-- --===============1735791444712601680== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1735791444712601680==-- From xen-api-bounces@lists.xen.org Tue Jan 22 08:28:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 08:28:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxZDe-0002l3-7Y; Tue, 22 Jan 2013 08:28:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxZDc-0002ky-A2 for xen-api@lists.xen.org; Tue, 22 Jan 2013 08:28:32 +0000 Received: from [193.109.254.147:8227] by server-6.bemta-14.messagelabs.com id 39/49-23901-FAD4EF05; Tue, 22 Jan 2013 08:28:31 +0000 X-Env-Sender: Vishwanath.Rawat@netapp.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1358843142!8610856!1 X-Originating-IP: [216.240.18.77] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE2LjI0MC4xOC43NyA9PiA0MDgxNA==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14726 invoked from network); 22 Jan 2013 08:25:44 -0000 Received: from mx12.netapp.com (HELO mx12.netapp.com) (216.240.18.77) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 08:25:44 -0000 X-IronPort-AV: E=Sophos;i="4.84,513,1355126400"; d="scan'208,217";a="10284625" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 22 Jan 2013 00:25:42 -0800 Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0M8Pgbc004948; Tue, 22 Jan 2013 00:25:42 -0800 (PST) Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.14]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0328.009; Tue, 22 Jan 2013 00:25:41 -0800 From: "Rawat, Vishwanath" To: George Shuklin , "xen-api@lists.xen.org" Thread-Topic: [Xen-API] VM Migration Thread-Index: Ac33+OeqHnhY2v4qQ3+kjxm30/vuEAAjTfAAAAMiJFA= Date: Tue, 22 Jan 2013 08:25:40 +0000 Message-ID: <7B89652AC48EE14E979D933CF09A0F1016EDCB64@SACEXCMBX04-PRD.hq.netapp.com> References: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> <50FDF0C0.1070605@gmail.com> In-Reply-To: <50FDF0C0.1070605@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] MIME-Version: 1.0 Subject: Re: [Xen-API] VM Migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7666442626248187858==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7666442626248187858== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7B89652AC48EE14E979D933CF09A0F1016EDCB64SACEXCMBX04PRDh_" --_000_7B89652AC48EE14E979D933CF09A0F1016EDCB64SACEXCMBX04PRDh_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SSBoYXZlIGRvd25sb2FkZWQgdGhlIGxhdGVzdCBBUEkgZ3VpZGUoWGVuU2VydmVyIDYuMS4wIE1h bmFnZW1lbnQgQVBJIEd1aWRlKS4gUHJvdG90eXBlIG9mIHBvb2xfbWlncmF0ZSBpcyBzdGlsbCBz YW1lIGluIG5ldyBtYW5hZ2VtZW50IEFQSSBndWlkZS4NCnBvb2xfbWlncmF0ZSAoc2Vzc2lvbl9p ZCBzLCBWTSByZWYgdm0sIGhvc3QgcmVmIGhvc3QsIChzdHJpbmcgLT4gc3RyaW5nKSBNYXAgb3B0 aW9ucykuDQoNCkkgdGhpbmsgdGhlcmUgc2hvdWxkIGJlIHNvbWUgcGFyYW0gdGhhdCBJIGNhbiBw YXNzIGFzIHBhcnQgb2Yg4oCcTWFwIG9wdGlvbnPigJ0gbWVudGlvbmVkIGluIGFib3ZlIHByb3Rv dHlwZS4gSSBqdXN0IGRvbuKAmXQga25vdyBvcHRpb24gbmFtZSBhbmQgaXRzIHZhbHVlLg0KDQpS ZWdhcmRzLA0KUmF3YXQNCg0KRnJvbTogeGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmcgW21h aWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gT24gQmVoYWxmIE9mIEdlb3JnZSBT aHVrbGluDQpTZW50OiBUdWVzZGF5LCBKYW51YXJ5IDIyLCAyMDEzIDc6MjIgQU0NClRvOiB4ZW4t YXBpQGxpc3RzLnhlbi5vcmcNClN1YmplY3Q6IFJlOiBbWGVuLUFQSV0gVk0gTWlncmF0aW9uDQoN CkkgdGhpbmsgeW91IHVzaW5nIG91dGRhdGVkIEFQSSBkb2N1bWVudGF0aW9uLiBOb3Qgc3VyZSBh Ym91dCBBUEkgY2FsbCwgYnV0IGNvcnJlc3BvbmRpbmcgeGUgY2FsbCBjYW4gY29udGFpbnMgcmVt b3RlLWhvc3QsIHJlbW90ZS11c2VybmFtZSwgcmVtb3RlLXBhc3N3b3JkIGFuZCBzbyBvbi4NCg0K T24gMjEuMDEuMjAxMyAyMjoxOCwgUmF3YXQsIFZpc2h3YW5hdGggd3JvdGU6DQpIaSBBbGwsDQog ICAgICAgICAgICAgICAgSSBhbSB3cml0aW5nIHNvbWUgcGVybCBzY3JpcHRzIHRvIGRvIFZNIE1p Z3JhdGlvbiB1c2luZyBYZW4gQVBJcy4NClRoaXMgaXMgdGhlIEFQSSBjYWxsIEkgYW0gdXNpbmcg dG8gZG8gVk0gTWlncmF0aW9uDQoNCnBvb2xfbWlncmF0ZSAoc2Vzc2lvbl9pZCBzLCBWTSByZWYg dm0sIGhvc3QgcmVmIGhvc3QsIChzdHJpbmcgLT4gc3RyaW5nKSBNYXAgb3B0aW9ucykuDQoNCk5v dyBpdCBpcyBhbHNvIHBvc3NpYmxlIHRvIG1pZ3JhdGUgZGF0YXN0b3JlIGFsb25nIHdpdGggVk0u IEkgd291bGQgbGlrZSB0byBrbm93IHdoYXQgaXMgdGhlIG9wdGlvbiB0aGF0IEkgY2FuIHBhc3Mg dG8gYWJvdmUgZnVuY3Rpb24gc28gdGhhdCBpdCB3aWxsIGFsc28gbWlncmF0ZSBkYXRhc3RvcmUu DQoNClJlZ2FyZHMsDQpSYXdhdA0KDQoNCg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX18NCg0KWGVuLWFwaSBtYWlsaW5nIGxpc3QNCg0KWGVuLWFw aUBsaXN0cy54ZW4ub3JnPG1haWx0bzpYZW4tYXBpQGxpc3RzLnhlbi5vcmc+DQoNCmh0dHA6Ly9s aXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpDQo= --_000_7B89652AC48EE14E979D933CF09A0F1016EDCB64SACEXCMBX04PRDh_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIg MiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q01UVDEwO30NCi8qIFN0eWxl IERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFs DQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4w cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjpibGFjazt9 DQpoMQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTsNCgltc28tc3R5bGUtbGluazoiSGVhZGluZyAx IENoYXIiOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJ bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6 ZToyNC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxp bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpi bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5 cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7 DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5 Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJnaW46 MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQt ZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcN Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z LXNlcmlmIjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXIN Cgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1w cmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQt ZmFtaWx5OkNvbnNvbGFzOw0KCWNvbG9yOmJsYWNrO30NCnNwYW4uRW1haWxTdHlsZTIwDQoJe21z by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fu cy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkhlYWRpbmcxQ2hhcg0KCXttc28tc3R5 bGUtbmFtZToiSGVhZGluZyAxIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5Ow0KCW1zby1z dHlsZS1saW5rOiJIZWFkaW5nIDEiOw0KCWZvbnQtd2VpZ2h0OmJvbGQ7fQ0KLk1zb0NocERlZmF1 bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpA cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEu MGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7 fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm XS0tPg0KPC9oZWFkPg0KPGJvZHkgYmdjb2xvcj0id2hpdGUiIGxhbmc9IkVOLVVTIiBsaW5rPSJi bHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8aDEgc3R5 bGU9Im1hcmdpbjowaW47bWFyZ2luLWJvdHRvbTouMDAwMXB0O2JhY2tncm91bmQ6d2hpdGUiPjxz cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjaztmb250LXdlaWdodDpub3JtYWwi PkkgaGF2ZSBkb3dubG9hZGVkIHRoZSBsYXRlc3QgQVBJIGd1aWRlKFhlblNlcnZlciA2LjEuMCBN YW5hZ2VtZW50IEFQSSBHdWlkZSkuIFByb3RvdHlwZSBvZiBwb29sX21pZ3JhdGUNCiBpcyBzdGls bCBzYW1lIGluIG5ldyBtYW5hZ2VtZW50IEFQSSBndWlkZS48bzpwPjwvbzpwPjwvc3Bhbj48L2gx Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u dC1mYW1pbHk6Q01UVDEwIj5wb29sX21pZ3JhdGUgKHNlc3Npb25faWQgcywgVk0gcmVmIHZtLCBo b3N0IHJlZiBob3N0LCAoc3RyaW5nIC0mZ3Q7IHN0cmluZykgTWFwIG9wdGlvbnMpLjwvc3Bhbj48 bzpwPjwvbzpwPjwvcD4NCjxoMSBzdHlsZT0ibWFyZ2luOjBpbjttYXJnaW4tYm90dG9tOi4wMDAx cHQ7YmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJs YWNrO2ZvbnQtd2VpZ2h0Om5vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9oMT4NCjxo MSBzdHlsZT0ibWFyZ2luOjBpbjttYXJnaW4tYm90dG9tOi4wMDAxcHQ7YmFja2dyb3VuZDp3aGl0 ZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrO2ZvbnQtd2VpZ2h0Om5v cm1hbCI+SSB0aGluayB0aGVyZSBzaG91bGQgYmUgc29tZSBwYXJhbSB0aGF0IEkgY2FuIHBhc3Mg YXMgcGFydCBvZiDigJxNYXAgb3B0aW9uc+KAnSBtZW50aW9uZWQgaW4gYWJvdmUgcHJvdG90eXBl Lg0KIEkganVzdCBkb27igJl0IGtub3cgb3B0aW9uIG5hbWUgYW5kIGl0cyB2YWx1ZS48bzpwPjwv bzpwPjwvc3Bhbj48L2gxPg0KPGgxIHN0eWxlPSJtYXJnaW46MGluO21hcmdpbi1ib3R0b206LjAw MDFwdDtiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250 LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6 YmxhY2s7Zm9udC13ZWlnaHQ6bm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2gxPg0K PGgxIHN0eWxlPSJtYXJnaW46MGluO21hcmdpbi1ib3R0b206LjAwMDFwdDtiYWNrZ3JvdW5kOndo aXRlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2s7Zm9udC13ZWlnaHQ6 bm9ybWFsIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvaDE+DQo8aDEgc3R5bGU9Im1hcmdp bjowaW47bWFyZ2luLWJvdHRvbTouMDAwMXB0O2JhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxl PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7 c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjaztmb250LXdlaWdodDpub3JtYWwiPlJhd2F0PG86 cD48L286cD48L3NwYW4+PC9oMT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBz dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6 My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9 ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3Nh bnMtc2VyaWYmcXVvdDs7Y29sb3I6d2luZG93dGV4dCI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0 eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVv dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOndpbmRvd3RleHQiPiB4ZW4tYXBpLWJvdW5jZXNAbGlz dHMueGVuLm9yZyBbbWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXQ0KPGI+T24g QmVoYWxmIE9mIDwvYj5HZW9yZ2UgU2h1a2xpbjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBK YW51YXJ5IDIyLCAyMDEzIDc6MjIgQU08YnI+DQo8Yj5Ubzo8L2I+IHhlbi1hcGlAbGlzdHMueGVu Lm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW1hlbi1BUEldIFZNIE1pZ3JhdGlvbjxvOnA+ PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48 bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgdGhpbmsgeW91IHVz aW5nIG91dGRhdGVkIEFQSSBkb2N1bWVudGF0aW9uLiBOb3Qgc3VyZSBhYm91dCBBUEkgY2FsbCwg YnV0IGNvcnJlc3BvbmRpbmcgeGUgY2FsbCBjYW4gY29udGFpbnMgcmVtb3RlLWhvc3QsIHJlbW90 ZS11c2VybmFtZSwgcmVtb3RlLXBhc3N3b3JkIGFuZCBzbyBvbi4NCjxicj4NCjxicj4NCk9uIDIx LjAxLjIwMTMgMjI6MTgsIFJhd2F0LCBWaXNod2FuYXRoIHdyb3RlOiA8bzpwPjwvbzpwPjwvcD4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIEFsbCw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBJIGFtIHdyaXRpbmcg c29tZSBwZXJsIHNjcmlwdHMgdG8gZG8gVk0gTWlncmF0aW9uIHVzaW5nIFhlbiBBUElzLjxvOnA+ PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhpcyBpcyB0aGUgQVBJIGNhbGwgSSBh bSB1c2luZyB0byBkbyBWTSBNaWdyYXRpb248bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01UVDEwIj5wb29sX21pZ3JhdGUg KHNlc3Npb25faWQgcywgVk0gcmVmIHZtLCBob3N0IHJlZiBob3N0LCAoc3RyaW5nIC0mZ3Q7IHN0 cmluZykgTWFwIG9wdGlvbnMpLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCI+ Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01UVDEwIj5Ob3cgaXQgaXMgYWxz byBwb3NzaWJsZSB0byBtaWdyYXRlIGRhdGFzdG9yZSBhbG9uZyB3aXRoIFZNLiBJIHdvdWxkIGxp a2UgdG8ga25vdyB3aGF0IGlzIHRoZSBvcHRpb24gdGhhdCBJIGNhbiBwYXNzIHRvIGFib3ZlIGZ1 bmN0aW9uIHNvIHRoYXQgaXQgd2lsbCBhbHNvIG1pZ3JhdGUgZGF0YXN0b3JlLjwvc3Bhbj48bzpw PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6 MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m YW1pbHk6Q01UVDEwIj5SZWdhcmRzLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQx MCI+UmF3YXQ8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpDTVRUMTAiPiZuYnNwOzwvc3Bh bj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+ PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7 Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7 Ij48YnI+DQo8YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cHJlPl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPG86cD48L286cD48L3ByZT4N CjxwcmU+WGVuLWFwaSBtYWlsaW5nIGxpc3Q8bzpwPjwvbzpwPjwvcHJlPg0KPHByZT48YSBocmVm PSJtYWlsdG86WGVuLWFwaUBsaXN0cy54ZW4ub3JnIj5YZW4tYXBpQGxpc3RzLnhlbi5vcmc8L2E+ PG86cD48L286cD48L3ByZT4NCjxwcmU+PGEgaHJlZj0iaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkiPmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpPC9hPjxvOnA+PC9vOnA+PC9wcmU+DQo8L2Rpdj4N CjwvYm9keT4NCjwvaHRtbD4NCg== --_000_7B89652AC48EE14E979D933CF09A0F1016EDCB64SACEXCMBX04PRDh_-- --===============7666442626248187858== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7666442626248187858==-- From xen-api-bounces@lists.xen.org Tue Jan 22 08:28:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 08:28:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxZDe-0002l3-7Y; Tue, 22 Jan 2013 08:28:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxZDc-0002ky-A2 for xen-api@lists.xen.org; Tue, 22 Jan 2013 08:28:32 +0000 Received: from [193.109.254.147:8227] by server-6.bemta-14.messagelabs.com id 39/49-23901-FAD4EF05; Tue, 22 Jan 2013 08:28:31 +0000 X-Env-Sender: Vishwanath.Rawat@netapp.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1358843142!8610856!1 X-Originating-IP: [216.240.18.77] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE2LjI0MC4xOC43NyA9PiA0MDgxNA==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14726 invoked from network); 22 Jan 2013 08:25:44 -0000 Received: from mx12.netapp.com (HELO mx12.netapp.com) (216.240.18.77) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 08:25:44 -0000 X-IronPort-AV: E=Sophos;i="4.84,513,1355126400"; d="scan'208,217";a="10284625" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 22 Jan 2013 00:25:42 -0800 Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0M8Pgbc004948; Tue, 22 Jan 2013 00:25:42 -0800 (PST) Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.14]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0328.009; Tue, 22 Jan 2013 00:25:41 -0800 From: "Rawat, Vishwanath" To: George Shuklin , "xen-api@lists.xen.org" Thread-Topic: [Xen-API] VM Migration Thread-Index: Ac33+OeqHnhY2v4qQ3+kjxm30/vuEAAjTfAAAAMiJFA= Date: Tue, 22 Jan 2013 08:25:40 +0000 Message-ID: <7B89652AC48EE14E979D933CF09A0F1016EDCB64@SACEXCMBX04-PRD.hq.netapp.com> References: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> <50FDF0C0.1070605@gmail.com> In-Reply-To: <50FDF0C0.1070605@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] MIME-Version: 1.0 Subject: Re: [Xen-API] VM Migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7666442626248187858==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7666442626248187858== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7B89652AC48EE14E979D933CF09A0F1016EDCB64SACEXCMBX04PRDh_" --_000_7B89652AC48EE14E979D933CF09A0F1016EDCB64SACEXCMBX04PRDh_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SSBoYXZlIGRvd25sb2FkZWQgdGhlIGxhdGVzdCBBUEkgZ3VpZGUoWGVuU2VydmVyIDYuMS4wIE1h bmFnZW1lbnQgQVBJIEd1aWRlKS4gUHJvdG90eXBlIG9mIHBvb2xfbWlncmF0ZSBpcyBzdGlsbCBz YW1lIGluIG5ldyBtYW5hZ2VtZW50IEFQSSBndWlkZS4NCnBvb2xfbWlncmF0ZSAoc2Vzc2lvbl9p ZCBzLCBWTSByZWYgdm0sIGhvc3QgcmVmIGhvc3QsIChzdHJpbmcgLT4gc3RyaW5nKSBNYXAgb3B0 aW9ucykuDQoNCkkgdGhpbmsgdGhlcmUgc2hvdWxkIGJlIHNvbWUgcGFyYW0gdGhhdCBJIGNhbiBw YXNzIGFzIHBhcnQgb2Yg4oCcTWFwIG9wdGlvbnPigJ0gbWVudGlvbmVkIGluIGFib3ZlIHByb3Rv dHlwZS4gSSBqdXN0IGRvbuKAmXQga25vdyBvcHRpb24gbmFtZSBhbmQgaXRzIHZhbHVlLg0KDQpS ZWdhcmRzLA0KUmF3YXQNCg0KRnJvbTogeGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmcgW21h aWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gT24gQmVoYWxmIE9mIEdlb3JnZSBT aHVrbGluDQpTZW50OiBUdWVzZGF5LCBKYW51YXJ5IDIyLCAyMDEzIDc6MjIgQU0NClRvOiB4ZW4t YXBpQGxpc3RzLnhlbi5vcmcNClN1YmplY3Q6IFJlOiBbWGVuLUFQSV0gVk0gTWlncmF0aW9uDQoN CkkgdGhpbmsgeW91IHVzaW5nIG91dGRhdGVkIEFQSSBkb2N1bWVudGF0aW9uLiBOb3Qgc3VyZSBh Ym91dCBBUEkgY2FsbCwgYnV0IGNvcnJlc3BvbmRpbmcgeGUgY2FsbCBjYW4gY29udGFpbnMgcmVt b3RlLWhvc3QsIHJlbW90ZS11c2VybmFtZSwgcmVtb3RlLXBhc3N3b3JkIGFuZCBzbyBvbi4NCg0K T24gMjEuMDEuMjAxMyAyMjoxOCwgUmF3YXQsIFZpc2h3YW5hdGggd3JvdGU6DQpIaSBBbGwsDQog ICAgICAgICAgICAgICAgSSBhbSB3cml0aW5nIHNvbWUgcGVybCBzY3JpcHRzIHRvIGRvIFZNIE1p Z3JhdGlvbiB1c2luZyBYZW4gQVBJcy4NClRoaXMgaXMgdGhlIEFQSSBjYWxsIEkgYW0gdXNpbmcg dG8gZG8gVk0gTWlncmF0aW9uDQoNCnBvb2xfbWlncmF0ZSAoc2Vzc2lvbl9pZCBzLCBWTSByZWYg dm0sIGhvc3QgcmVmIGhvc3QsIChzdHJpbmcgLT4gc3RyaW5nKSBNYXAgb3B0aW9ucykuDQoNCk5v dyBpdCBpcyBhbHNvIHBvc3NpYmxlIHRvIG1pZ3JhdGUgZGF0YXN0b3JlIGFsb25nIHdpdGggVk0u IEkgd291bGQgbGlrZSB0byBrbm93IHdoYXQgaXMgdGhlIG9wdGlvbiB0aGF0IEkgY2FuIHBhc3Mg dG8gYWJvdmUgZnVuY3Rpb24gc28gdGhhdCBpdCB3aWxsIGFsc28gbWlncmF0ZSBkYXRhc3RvcmUu DQoNClJlZ2FyZHMsDQpSYXdhdA0KDQoNCg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX18NCg0KWGVuLWFwaSBtYWlsaW5nIGxpc3QNCg0KWGVuLWFw aUBsaXN0cy54ZW4ub3JnPG1haWx0bzpYZW4tYXBpQGxpc3RzLnhlbi5vcmc+DQoNCmh0dHA6Ly9s aXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpDQo= --_000_7B89652AC48EE14E979D933CF09A0F1016EDCB64SACEXCMBX04PRDh_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIg MiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q01UVDEwO30NCi8qIFN0eWxl IERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFs DQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4w cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjpibGFjazt9 DQpoMQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTsNCgltc28tc3R5bGUtbGluazoiSGVhZGluZyAx IENoYXIiOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJ bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6 ZToyNC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxp bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpi bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5 cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7 DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5 Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJnaW46 MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQt ZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcN Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z LXNlcmlmIjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXIN Cgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1w cmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQt ZmFtaWx5OkNvbnNvbGFzOw0KCWNvbG9yOmJsYWNrO30NCnNwYW4uRW1haWxTdHlsZTIwDQoJe21z by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fu cy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkhlYWRpbmcxQ2hhcg0KCXttc28tc3R5 bGUtbmFtZToiSGVhZGluZyAxIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5Ow0KCW1zby1z dHlsZS1saW5rOiJIZWFkaW5nIDEiOw0KCWZvbnQtd2VpZ2h0OmJvbGQ7fQ0KLk1zb0NocERlZmF1 bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpA cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEu MGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7 fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm XS0tPg0KPC9oZWFkPg0KPGJvZHkgYmdjb2xvcj0id2hpdGUiIGxhbmc9IkVOLVVTIiBsaW5rPSJi bHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8aDEgc3R5 bGU9Im1hcmdpbjowaW47bWFyZ2luLWJvdHRvbTouMDAwMXB0O2JhY2tncm91bmQ6d2hpdGUiPjxz cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjaztmb250LXdlaWdodDpub3JtYWwi PkkgaGF2ZSBkb3dubG9hZGVkIHRoZSBsYXRlc3QgQVBJIGd1aWRlKFhlblNlcnZlciA2LjEuMCBN YW5hZ2VtZW50IEFQSSBHdWlkZSkuIFByb3RvdHlwZSBvZiBwb29sX21pZ3JhdGUNCiBpcyBzdGls bCBzYW1lIGluIG5ldyBtYW5hZ2VtZW50IEFQSSBndWlkZS48bzpwPjwvbzpwPjwvc3Bhbj48L2gx Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u dC1mYW1pbHk6Q01UVDEwIj5wb29sX21pZ3JhdGUgKHNlc3Npb25faWQgcywgVk0gcmVmIHZtLCBo b3N0IHJlZiBob3N0LCAoc3RyaW5nIC0mZ3Q7IHN0cmluZykgTWFwIG9wdGlvbnMpLjwvc3Bhbj48 bzpwPjwvbzpwPjwvcD4NCjxoMSBzdHlsZT0ibWFyZ2luOjBpbjttYXJnaW4tYm90dG9tOi4wMDAx cHQ7YmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJs YWNrO2ZvbnQtd2VpZ2h0Om5vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9oMT4NCjxo MSBzdHlsZT0ibWFyZ2luOjBpbjttYXJnaW4tYm90dG9tOi4wMDAxcHQ7YmFja2dyb3VuZDp3aGl0 ZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrO2ZvbnQtd2VpZ2h0Om5v cm1hbCI+SSB0aGluayB0aGVyZSBzaG91bGQgYmUgc29tZSBwYXJhbSB0aGF0IEkgY2FuIHBhc3Mg YXMgcGFydCBvZiDigJxNYXAgb3B0aW9uc+KAnSBtZW50aW9uZWQgaW4gYWJvdmUgcHJvdG90eXBl Lg0KIEkganVzdCBkb27igJl0IGtub3cgb3B0aW9uIG5hbWUgYW5kIGl0cyB2YWx1ZS48bzpwPjwv bzpwPjwvc3Bhbj48L2gxPg0KPGgxIHN0eWxlPSJtYXJnaW46MGluO21hcmdpbi1ib3R0b206LjAw MDFwdDtiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250 LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6 YmxhY2s7Zm9udC13ZWlnaHQ6bm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2gxPg0K PGgxIHN0eWxlPSJtYXJnaW46MGluO21hcmdpbi1ib3R0b206LjAwMDFwdDtiYWNrZ3JvdW5kOndo aXRlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2s7Zm9udC13ZWlnaHQ6 bm9ybWFsIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvaDE+DQo8aDEgc3R5bGU9Im1hcmdp bjowaW47bWFyZ2luLWJvdHRvbTouMDAwMXB0O2JhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxl PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7 c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjaztmb250LXdlaWdodDpub3JtYWwiPlJhd2F0PG86 cD48L286cD48L3NwYW4+PC9oMT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBz dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6 My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9 ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3Nh bnMtc2VyaWYmcXVvdDs7Y29sb3I6d2luZG93dGV4dCI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0 eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVv dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOndpbmRvd3RleHQiPiB4ZW4tYXBpLWJvdW5jZXNAbGlz dHMueGVuLm9yZyBbbWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXQ0KPGI+T24g QmVoYWxmIE9mIDwvYj5HZW9yZ2UgU2h1a2xpbjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBK YW51YXJ5IDIyLCAyMDEzIDc6MjIgQU08YnI+DQo8Yj5Ubzo8L2I+IHhlbi1hcGlAbGlzdHMueGVu Lm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW1hlbi1BUEldIFZNIE1pZ3JhdGlvbjxvOnA+ PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48 bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgdGhpbmsgeW91IHVz aW5nIG91dGRhdGVkIEFQSSBkb2N1bWVudGF0aW9uLiBOb3Qgc3VyZSBhYm91dCBBUEkgY2FsbCwg YnV0IGNvcnJlc3BvbmRpbmcgeGUgY2FsbCBjYW4gY29udGFpbnMgcmVtb3RlLWhvc3QsIHJlbW90 ZS11c2VybmFtZSwgcmVtb3RlLXBhc3N3b3JkIGFuZCBzbyBvbi4NCjxicj4NCjxicj4NCk9uIDIx LjAxLjIwMTMgMjI6MTgsIFJhd2F0LCBWaXNod2FuYXRoIHdyb3RlOiA8bzpwPjwvbzpwPjwvcD4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIEFsbCw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBJIGFtIHdyaXRpbmcg c29tZSBwZXJsIHNjcmlwdHMgdG8gZG8gVk0gTWlncmF0aW9uIHVzaW5nIFhlbiBBUElzLjxvOnA+ PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhpcyBpcyB0aGUgQVBJIGNhbGwgSSBh bSB1c2luZyB0byBkbyBWTSBNaWdyYXRpb248bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01UVDEwIj5wb29sX21pZ3JhdGUg KHNlc3Npb25faWQgcywgVk0gcmVmIHZtLCBob3N0IHJlZiBob3N0LCAoc3RyaW5nIC0mZ3Q7IHN0 cmluZykgTWFwIG9wdGlvbnMpLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCI+ Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01UVDEwIj5Ob3cgaXQgaXMgYWxz byBwb3NzaWJsZSB0byBtaWdyYXRlIGRhdGFzdG9yZSBhbG9uZyB3aXRoIFZNLiBJIHdvdWxkIGxp a2UgdG8ga25vdyB3aGF0IGlzIHRoZSBvcHRpb24gdGhhdCBJIGNhbiBwYXNzIHRvIGFib3ZlIGZ1 bmN0aW9uIHNvIHRoYXQgaXQgd2lsbCBhbHNvIG1pZ3JhdGUgZGF0YXN0b3JlLjwvc3Bhbj48bzpw PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6 MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m YW1pbHk6Q01UVDEwIj5SZWdhcmRzLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQx MCI+UmF3YXQ8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpDTVRUMTAiPiZuYnNwOzwvc3Bh bj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+ PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7 Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7 Ij48YnI+DQo8YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cHJlPl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPG86cD48L286cD48L3ByZT4N CjxwcmU+WGVuLWFwaSBtYWlsaW5nIGxpc3Q8bzpwPjwvbzpwPjwvcHJlPg0KPHByZT48YSBocmVm PSJtYWlsdG86WGVuLWFwaUBsaXN0cy54ZW4ub3JnIj5YZW4tYXBpQGxpc3RzLnhlbi5vcmc8L2E+ PG86cD48L286cD48L3ByZT4NCjxwcmU+PGEgaHJlZj0iaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkiPmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpPC9hPjxvOnA+PC9vOnA+PC9wcmU+DQo8L2Rpdj4N CjwvYm9keT4NCjwvaHRtbD4NCg== --_000_7B89652AC48EE14E979D933CF09A0F1016EDCB64SACEXCMBX04PRDh_-- --===============7666442626248187858== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7666442626248187858==-- From xen-api-bounces@lists.xen.org Tue Jan 22 08:47:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 08:47:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxZVN-0002tx-2x; Tue, 22 Jan 2013 08:46:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxZVL-0002ts-HE for xen-api@lists.xen.org; Tue, 22 Jan 2013 08:46:51 +0000 Received: from [85.158.143.35:56972] by server-3.bemta-4.messagelabs.com id 89/F9-10689-AF15EF05; Tue, 22 Jan 2013 08:46:50 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1358844396!16383257!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16229 invoked from network); 22 Jan 2013 08:46:36 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 08:46:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,513,1355097600"; d="scan'208,217";a="803642" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Jan 2013 08:46:36 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Tue, 22 Jan 2013 08:46:36 +0000 From: John Else To: "Rawat, Vishwanath" , George Shuklin , "xen-api@lists.xen.org" Date: Tue, 22 Jan 2013 08:46:56 +0000 Thread-Topic: [Xen-API] VM Migration Thread-Index: Ac33+OeqHnhY2v4qQ3+kjxm30/vuEAAjTfAAAAMiJFAABdVswA== Message-ID: <7EA643C653F17F4C80DE959E978F10ED010E6CA10084@LONPMAILBOX01.citrite.net> References: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> <50FDF0C0.1070605@gmail.com> <7B89652AC48EE14E979D933CF09A0F1016EDCB64@SACEXCMBX04-PRD.hq.netapp.com> In-Reply-To: <7B89652AC48EE14E979D933CF09A0F1016EDCB64@SACEXCMBX04-PRD.hq.netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] VM Migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1517481114643203329==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1517481114643203329== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7EA643C653F17F4C80DE959E978F10ED010E6CA10084LONPMAILBOX_" --_000_7EA643C653F17F4C80DE959E978F10ED010E6CA10084LONPMAILBOX_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgUmF3YXQsDQoNClRoZSBBUEkgY2FsbCB5b3UgYXJlIHVzaW5nIGlzIHN0aWxsIHN1cHBvcnRl ZCwgYnV0IGl0IG9ubHkgbGV0cyB5b3UgZG8gbWlncmF0aW9uIHdpdGhpbiBhIHBvb2wsIHdpdGgg bm8gc3RvcmFnZSBtaWdyYXRpb24uDQoNCklmIHlvdSB3YW50IHRvIG1pZ3JhdGUgYSBWTSBhbmQg aXRzIHN0b3JhZ2UgKG1heWJlIGV2ZW4gYmV0d2VlbiBwb29scyksIHlvdSBmaXJzdCBuZWVkIHRv IGNhbGwgSG9zdC5taWdyYXRlX3JlY2VpdmUgKHNlZSBodHRwOi8vZG9jcy52bWQuY2l0cml4LmNv bS9YZW5TZXJ2ZXIvNi4xLjAvMS4wL2VuX2diL2FwaS8/Yz1ob3N0KSB3aXRoIHRoZSByZWZlcmVu Y2Ugb2YgdGhlIGhvc3QgeW91IHdpc2ggdG8gbWlncmF0ZSB0aGUgVk0gdG8uIFRoaXMgQVBJIGNh bGwgbmVlZHMgdG8gYmUgbWFkZSB0byB0aGUgbWFzdGVyIG9mIHRoZSBwb29sIHlvdSB3YW50IHRv IG1pZ3JhdGUgdG8gKG9idmlvdXNseSB0aGUgaG9zdCByZWZlcmVuY2UgbmVlZHMgdG8gYmUgb25l IG9mIHRoZSBob3N0cyBpbiB0aGlzIHBvb2wpLg0KDQpUaGlzIHdpbGwgcmV0dXJuIGEgdmFsdWUg b2YgdHlwZSAoc3RyaW5nIC0+IHN0cmluZykgbWFwLiBZb3UgdGhlbiBuZWVkIHRvIGNhbGwgVk0u bWlncmF0ZV9zZW5kIG9uIHRoZSBtYXN0ZXIgb2YgdGhlIHBvb2wgeW91IHdpc2ggdG8gbWlncmF0 ZSBmcm9tIChzZWUgaHR0cDovL2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4wLzEu MC9lbl9nYi9hcGkvP2M9Vk0pLiBUaGlzIGNvdWxkIGJlIGNhbGxlZCB0byB0aGUgc2FtZSBtYXN0 ZXIgYXMgYWJvdmUsIGlmIHlvdSBvbmx5IHdhbnQgdG8gZG8gYSBzdG9yYWdlIG1pZ3JhdGlvbiB3 aXRoaW4gYSBwb29sLg0KDQpUaGUgYXJndW1lbnRzIHRvIHRoaXMgZnVuY3Rpb24gYXJlLCBpbiBv cmRlcjoNCg0KVk0gcmVmOiBUaGlzIGlzIHRoZSBWTSB5b3Ugd2FudCB0byBtaWdyYXRlDQooc3Ry aW5nIC0+IHN0cmluZykgbWFwOiBUaGlzIGlzIHRoZSByZXR1cm4gdmFsdWUgeW91IHJlY2VpdmVk IGZyb20gSG9zdC5taWdyYXRlX3JlY2VpdmUgYWJvdmUuDQpib29sOiBUaGUgaXMgdGhlIOKAnGxp dmXigJ0gZmxhZy4gVGhpcyBtdXN0IGJlIOKAnHRydWXigJ0gYXQgdGhlIG1vbWVudC4NCihWREkg cmVmIC0+IFNSIHJlZikgbWFwOiBUaGlzIGluZGljYXRlcyB3aGljaCBTUiAoYXR0YWNoZWQgdG8g dGhlIGRlc3RpbmF0aW9uIGhvc3QpIGVhY2ggb2YgdGhlIFZN4oCZcyBWRElzIHdpbGwgYmUgbW92 ZWQgdG8uDQooVklGIHJlZiAtPiBuZXR3b3JrIHJlZikgbWFwOiBUaGlzIGluZGljYXRlcyB3aGlj aCBuZXR3b3JrIChwcmVzZW50IG9uIHRoZSBkZXN0aW5hdGlvbiBob3N0KSBlYWNoIG9mIHRoZSBW TeKAmXMgVklGcyB3aWxsIGJlIG1vdmVkIHRvLg0KKHN0cmluZyAtPiBzdHJpbmcpIG1hcDogRXh0 cmEgb3B0aW9ucyBmaWVsZCBmb3IgZnV0dXJlIGltcHJvdmVtZW50cyDigJMgbm90IHVzZWQgYXQg dGhlIG1vbWVudCAoanVzdCBwYXNzIGFuIGVtcHR5IGRpY3Rpb25hcnkpLg0KDQpBbHNvLCBpZiB5 b3Ugd2FudCB0byBtaWdyYXRlIGEgVkRJIGJldHdlZW4gU1JzIHdpdGhvdXQgbWlncmF0aW5nIHRo ZSBWTSB3aGljaCBvd25zIHRoZSBWREksIHlvdSBjYW4ganVzdCB1c2UgVkRJLnBvb2xfbWlncmF0 ZSAoc2VlIGh0dHA6Ly9kb2NzLnZtZC5jaXRyaXguY29tL1hlblNlcnZlci82LjEuMC8xLjAvZW5f Z2IvYXBpLz9jPVZESSkuIFRoZSBhcmd1bWVudHMgYXJlOg0KDQpWREkgcmVmOiBUaGUgVkRJIHlv dSB3YW50IHRvIG1vdmUuDQpTUiByZWY6IFRoZSBTUiB5b3Ugd2FudCB0byBtb3ZlIHRoZSBWRGkg dG8uDQooc3RyaW5nIC0+IHN0cmluZykgbWFwOiBhbm90aGVyIHVudXNlZCDigJxvcHRpb25z4oCd IGZpZWxkLg0KDQpIb3BlIHRoaXMgaGVscHMhDQoNCkpvaG4NCg0KRnJvbTogeGVuLWFwaS1ib3Vu Y2VzQGxpc3RzLnhlbi5vcmcgW21haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10g T24gQmVoYWxmIE9mIFJhd2F0LCBWaXNod2FuYXRoDQpTZW50OiAyMiBKYW51YXJ5IDIwMTMgMDg6 MjYNClRvOiBHZW9yZ2UgU2h1a2xpbjsgeGVuLWFwaUBsaXN0cy54ZW4ub3JnDQpTdWJqZWN0OiBS ZTogW1hlbi1BUEldIFZNIE1pZ3JhdGlvbg0KDQpJIGhhdmUgZG93bmxvYWRlZCB0aGUgbGF0ZXN0 IEFQSSBndWlkZShYZW5TZXJ2ZXIgNi4xLjAgTWFuYWdlbWVudCBBUEkgR3VpZGUpLiBQcm90b3R5 cGUgb2YgcG9vbF9taWdyYXRlIGlzIHN0aWxsIHNhbWUgaW4gbmV3IG1hbmFnZW1lbnQgQVBJIGd1 aWRlLg0KcG9vbF9taWdyYXRlIChzZXNzaW9uX2lkIHMsIFZNIHJlZiB2bSwgaG9zdCByZWYgaG9z dCwgKHN0cmluZyAtPiBzdHJpbmcpIE1hcCBvcHRpb25zKS4NCg0KSSB0aGluayB0aGVyZSBzaG91 bGQgYmUgc29tZSBwYXJhbSB0aGF0IEkgY2FuIHBhc3MgYXMgcGFydCBvZiDigJxNYXAgb3B0aW9u c+KAnSBtZW50aW9uZWQgaW4gYWJvdmUgcHJvdG90eXBlLiBJIGp1c3QgZG9u4oCZdCBrbm93IG9w dGlvbiBuYW1lIGFuZCBpdHMgdmFsdWUuDQoNClJlZ2FyZHMsDQpSYXdhdA0KDQpGcm9tOiB4ZW4t YXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZzxtYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhl bi5vcmc+IFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmddIE9uIEJlaGFsZiBP ZiBHZW9yZ2UgU2h1a2xpbg0KU2VudDogVHVlc2RheSwgSmFudWFyeSAyMiwgMjAxMyA3OjIyIEFN DQpUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbi5vcmc+ DQpTdWJqZWN0OiBSZTogW1hlbi1BUEldIFZNIE1pZ3JhdGlvbg0KDQpJIHRoaW5rIHlvdSB1c2lu ZyBvdXRkYXRlZCBBUEkgZG9jdW1lbnRhdGlvbi4gTm90IHN1cmUgYWJvdXQgQVBJIGNhbGwsIGJ1 dCBjb3JyZXNwb25kaW5nIHhlIGNhbGwgY2FuIGNvbnRhaW5zIHJlbW90ZS1ob3N0LCByZW1vdGUt dXNlcm5hbWUsIHJlbW90ZS1wYXNzd29yZCBhbmQgc28gb24uDQoNCk9uIDIxLjAxLjIwMTMgMjI6 MTgsIFJhd2F0LCBWaXNod2FuYXRoIHdyb3RlOg0KSGkgQWxsLA0KICAgICAgICAgICAgICAgIEkg YW0gd3JpdGluZyBzb21lIHBlcmwgc2NyaXB0cyB0byBkbyBWTSBNaWdyYXRpb24gdXNpbmcgWGVu IEFQSXMuDQpUaGlzIGlzIHRoZSBBUEkgY2FsbCBJIGFtIHVzaW5nIHRvIGRvIFZNIE1pZ3JhdGlv bg0KDQpwb29sX21pZ3JhdGUgKHNlc3Npb25faWQgcywgVk0gcmVmIHZtLCBob3N0IHJlZiBob3N0 LCAoc3RyaW5nIC0+IHN0cmluZykgTWFwIG9wdGlvbnMpLg0KDQpOb3cgaXQgaXMgYWxzbyBwb3Nz aWJsZSB0byBtaWdyYXRlIGRhdGFzdG9yZSBhbG9uZyB3aXRoIFZNLiBJIHdvdWxkIGxpa2UgdG8g a25vdyB3aGF0IGlzIHRoZSBvcHRpb24gdGhhdCBJIGNhbiBwYXNzIHRvIGFib3ZlIGZ1bmN0aW9u IHNvIHRoYXQgaXQgd2lsbCBhbHNvIG1pZ3JhdGUgZGF0YXN0b3JlLg0KDQpSZWdhcmRzLA0KUmF3 YXQNCg0KDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXw0KDQpYZW4tYXBpIG1haWxpbmcgbGlzdA0KDQpYZW4tYXBpQGxpc3RzLnhlbi5vcmc8bWFp bHRvOlhlbi1hcGlAbGlzdHMueGVuLm9yZz4NCg0KaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJp bi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkNCg== --_000_7EA643C653F17F4C80DE959E978F10ED010E6CA10084LONPMAILBOX_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5 OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJ e2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30N CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q01UVDEwO30NCi8qIFN0eWxlIERlZmluaXRpb25z ICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjow Y207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1m YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjpibGFjazt9DQpoMQ0KCXttc28t c3R5bGUtcHJpb3JpdHk6OTsNCgltc28tc3R5bGUtbGluazoiSGVhZGluZyAxIENoYXIiOw0KCW1z by1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1i b3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQtc2l6ZToyNC4wcHQ7DQoJ Zm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxpbmssIHNwYW4uTXNv SHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQt ZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxv d2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNv cmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1z dHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdp bi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3Vy aWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBk aXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6 IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFw dDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYi Ow0KCWNvbG9yOmJsYWNrO30NCnNwYW4uSGVhZGluZzFDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJI ZWFkaW5nIDEgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk7DQoJbXNvLXN0eWxlLWxpbms6 IkhlYWRpbmcgMSI7DQoJZm9udC13ZWlnaHQ6Ym9sZDt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRD aGFyDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5 bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglm b250LWZhbWlseTpDb25zb2xhczsNCgljb2xvcjpibGFjazt9DQpzcGFuLkVtYWlsU3R5bGUyMA0K CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt c2VyaWYiOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0 eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsN Cgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTIyDQoJe21zby1zdHlsZS10eXBlOnBl cnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29s b3I6IzFGNDk3RDt9DQpzcGFuLkJhbGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFs bG9vbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGlu azoiQmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7DQoJ Y29sb3I6YmxhY2s7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9u bHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIu MHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYu V29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBn dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIx MDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpz aGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIg Lz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT48L2hlYWQ+PGJvZHkgYmdjb2xv cj13aGl0ZSBsYW5nPUVOLUdCIGxpbms9Ymx1ZSB2bGluaz1wdXJwbGU+PGRpdiBjbGFzcz1Xb3Jk U2VjdGlvbjE+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjp3aW5kb3d0ZXh0 Jz5IaSBSYXdhdCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu IHN0eWxlPSdjb2xvcjp3aW5kb3d0ZXh0Jz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAg Y2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjp3aW5kb3d0ZXh0Jz5UaGUgQVBJIGNh bGwgeW91IGFyZSB1c2luZyBpcyBzdGlsbCBzdXBwb3J0ZWQsIGJ1dCBpdCBvbmx5IGxldHMgeW91 IGRvIG1pZ3JhdGlvbiB3aXRoaW4gYSBwb29sLCB3aXRoIG5vIHN0b3JhZ2UgbWlncmF0aW9uLjxv OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9y OiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+ PHNwYW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQnPklmIHlvdSB3YW50IHRvIG1pZ3JhdGUgYSBW TSBhbmQgaXRzIHN0b3JhZ2UgKG1heWJlIGV2ZW4gYmV0d2VlbiBwb29scyksIHlvdSBmaXJzdCBu ZWVkIHRvIGNhbGwgSG9zdC5taWdyYXRlX3JlY2VpdmUgKHNlZSA8L3NwYW4+PGEgaHJlZj0iaHR0 cDovL2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4wLzEuMC9lbl9nYi9hcGkvP2M9 aG9zdCI+aHR0cDovL2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4wLzEuMC9lbl9n Yi9hcGkvP2M9aG9zdDwvYT4pIHdpdGggdGhlIHJlZmVyZW5jZSBvZiB0aGUgaG9zdCB5b3Ugd2lz aCB0byBtaWdyYXRlIHRoZSBWTSB0by4gVGhpcyBBUEkgY2FsbCBuZWVkcyB0byBiZSBtYWRlIHRv IHRoZSBtYXN0ZXIgb2YgdGhlIHBvb2wgeW91IHdhbnQgdG8gbWlncmF0ZSB0byAob2J2aW91c2x5 IHRoZSBob3N0IHJlZmVyZW5jZSBuZWVkcyB0byBiZSBvbmUgb2YgdGhlIGhvc3RzIGluIHRoaXMg cG9vbCkuPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+ PC9wPjxwIGNsYXNzPU1zb05vcm1hbD5UaGlzIHdpbGwgcmV0dXJuIGEgdmFsdWUgb2YgdHlwZSAo c3RyaW5nIC0mZ3Q7IHN0cmluZykgbWFwLiBZb3UgdGhlbiBuZWVkIHRvIGNhbGwgVk0ubWlncmF0 ZV9zZW5kIG9uIHRoZSBtYXN0ZXIgb2YgdGhlIHBvb2wgeW91IHdpc2ggdG8gbWlncmF0ZSBmcm9t IChzZWUgPGEgaHJlZj0iaHR0cDovL2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4w LzEuMC9lbl9nYi9hcGkvP2M9Vk0iPmh0dHA6Ly9kb2NzLnZtZC5jaXRyaXguY29tL1hlblNlcnZl ci82LjEuMC8xLjAvZW5fZ2IvYXBpLz9jPVZNPC9hPikuIFRoaXMgY291bGQgYmUgY2FsbGVkIHRv IHRoZSBzYW1lIG1hc3RlciBhcyBhYm92ZSwgaWYgeW91IG9ubHkgd2FudCB0byBkbyBhIHN0b3Jh Z2UgbWlncmF0aW9uIHdpdGhpbiBhIHBvb2wuPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9y bWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD5UaGUgYXJndW1lbnRz IHRvIHRoaXMgZnVuY3Rpb24gYXJlLCBpbiBvcmRlcjo8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1N c29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPlZNIHJlZjog VGhpcyBpcyB0aGUgVk0geW91IHdhbnQgdG8gbWlncmF0ZTxvOnA+PC9vOnA+PC9wPjxwIGNsYXNz PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4dCc+KHN0cmluZyAtJmd0OyBz dHJpbmcpIG1hcDogVGhpcyBpcyB0aGUgcmV0dXJuIHZhbHVlIHlvdSByZWNlaXZlZCBmcm9tIEhv c3QubWlncmF0ZV9yZWNlaXZlIGFib3ZlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1N c29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQnPmJvb2w6IFRoZSBpcyB0aGUg 4oCcbGl2ZeKAnSBmbGFnLiBUaGlzIG11c3QgYmUg4oCcdHJ1ZeKAnSBhdCB0aGUgbW9tZW50Ljxv OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9y OndpbmRvd3RleHQnPihWREkgcmVmIC0mZ3Q7IFNSIHJlZikgbWFwOiBUaGlzIGluZGljYXRlcyB3 aGljaCBTUiAoYXR0YWNoZWQgdG8gdGhlIGRlc3RpbmF0aW9uIGhvc3QpIGVhY2ggb2YgdGhlIFZN 4oCZcyBWRElzIHdpbGwgYmUgbW92ZWQgdG8uPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNz PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4dCc+KFZJRiByZWYgLSZndDsg bmV0d29yayByZWYpIG1hcDogVGhpcyBpbmRpY2F0ZXMgd2hpY2ggbmV0d29yayAocHJlc2VudCBv biB0aGUgZGVzdGluYXRpb24gaG9zdCkgZWFjaCBvZiB0aGUgVk3igJlzIFZJRnMgd2lsbCBiZSBt b3ZlZCB0by48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0 eWxlPSdjb2xvcjp3aW5kb3d0ZXh0Jz4oc3RyaW5nIC0mZ3Q7IHN0cmluZykgbWFwOiBFeHRyYSBv cHRpb25zIGZpZWxkIGZvciBmdXR1cmUgaW1wcm92ZW1lbnRzIOKAkyBub3QgdXNlZCBhdCB0aGUg bW9tZW50IChqdXN0IHBhc3MgYW4gZW1wdHkgZGljdGlvbmFyeSkuPG86cD48L286cD48L3NwYW4+ PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4dCc+PG86 cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n Y29sb3I6d2luZG93dGV4dCc+QWxzbywgaWYgeW91IHdhbnQgdG8gbWlncmF0ZSBhIFZESSBiZXR3 ZWVuIFNScyB3aXRob3V0IG1pZ3JhdGluZyB0aGUgVk0gd2hpY2ggb3ducyB0aGUgVkRJLCB5b3Ug Y2FuIGp1c3QgdXNlIFZESS5wb29sX21pZ3JhdGUgKHNlZSA8L3NwYW4+PGEgaHJlZj0iaHR0cDov L2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4wLzEuMC9lbl9nYi9hcGkvP2M9VkRJ Ij5odHRwOi8vZG9jcy52bWQuY2l0cml4LmNvbS9YZW5TZXJ2ZXIvNi4xLjAvMS4wL2VuX2diL2Fw aS8/Yz1WREk8L2E+KS4gVGhlIGFyZ3VtZW50cyBhcmU6PG86cD48L286cD48L3A+PHAgY2xhc3M9 TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD5WREkgcmVm OiBUaGUgVkRJIHlvdSB3YW50IHRvIG1vdmUuPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9y bWFsPlNSIHJlZjogVGhlIFNSIHlvdSB3YW50IHRvIG1vdmUgdGhlIFZEaSB0by48bzpwPjwvbzpw PjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+KHN0cmluZyAtJmd0OyBzdHJpbmcpIG1hcDogYW5vdGhl ciB1bnVzZWQg4oCcb3B0aW9uc+KAnSBmaWVsZC48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4 dCc+PG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n Y29sb3I6d2luZG93dGV4dCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1z b05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4dCc+SG9wZSB0aGlzIGhlbHBzITxv OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9y OndpbmRvd3RleHQnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3Jt YWw+PHNwYW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQnPkpvaG48bzpwPjwvbzpwPjwvc3Bhbj48 L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz48bzpwPiZu YnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRpdj48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3JkZXIt dG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSc+PHAgY2xh c3M9TXNvTm9ybWFsPjxiPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7 Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO2NvbG9yOndpbmRvd3RleHQnPkZyb206 PC9zcGFuPjwvYj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQt ZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjtjb2xvcjp3aW5kb3d0ZXh0Jz4geGVuLWFwaS1i b3VuY2VzQGxpc3RzLnhlbi5vcmcgW21haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9y Z10gPGI+T24gQmVoYWxmIE9mIDwvYj5SYXdhdCwgVmlzaHdhbmF0aDxicj48Yj5TZW50OjwvYj4g MjIgSmFudWFyeSAyMDEzIDA4OjI2PGJyPjxiPlRvOjwvYj4gR2VvcmdlIFNodWtsaW47IHhlbi1h cGlAbGlzdHMueGVuLm9yZzxicj48Yj5TdWJqZWN0OjwvYj4gUmU6IFtYZW4tQVBJXSBWTSBNaWdy YXRpb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFs PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxoMSBzdHlsZT0nbWFyZ2luOjBjbTttYXJnaW4tYm90dG9t Oi4wMDAxcHQ7YmFja2dyb3VuZDp3aGl0ZSc+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1z aXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOmJsYWNr O2ZvbnQtd2VpZ2h0Om5vcm1hbCc+SSBoYXZlIGRvd25sb2FkZWQgdGhlIGxhdGVzdCBBUEkgZ3Vp ZGUoWGVuU2VydmVyIDYuMS4wIE1hbmFnZW1lbnQgQVBJIEd1aWRlKS4gUHJvdG90eXBlIG9mIHBv b2xfbWlncmF0ZSBpcyBzdGlsbCBzYW1lIGluIG5ldyBtYW5hZ2VtZW50IEFQSSBndWlkZS48bzpw PjwvbzpwPjwvc3Bhbj48L2gxPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0 eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCc+cG9vbF9taWdyYXRlIChz ZXNzaW9uX2lkIHMsIFZNIHJlZiB2bSwgaG9zdCByZWYgaG9zdCwgKHN0cmluZyAtJmd0OyBzdHJp bmcpIE1hcCBvcHRpb25zKS48L3NwYW4+PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwvc3Bh bj48L3A+PGgxIHN0eWxlPSdtYXJnaW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDtiYWNrZ3Jv dW5kOndoaXRlJz48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQt ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6YmxhY2s7Zm9udC13ZWlnaHQ6bm9y bWFsJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2gxPjxoMSBzdHlsZT0nbWFyZ2luOjBjbTtt YXJnaW4tYm90dG9tOi4wMDAxcHQ7YmFja2dyb3VuZDp3aGl0ZSc+PHNwYW4gbGFuZz1FTi1VUyBz dHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYi O2NvbG9yOmJsYWNrO2ZvbnQtd2VpZ2h0Om5vcm1hbCc+SSB0aGluayB0aGVyZSBzaG91bGQgYmUg c29tZSBwYXJhbSB0aGF0IEkgY2FuIHBhc3MgYXMgcGFydCBvZiDigJxNYXAgb3B0aW9uc+KAnSBt ZW50aW9uZWQgaW4gYWJvdmUgcHJvdG90eXBlLiBJIGp1c3QgZG9u4oCZdCBrbm93IG9wdGlvbiBu YW1lIGFuZCBpdHMgdmFsdWUuPG86cD48L286cD48L3NwYW4+PC9oMT48aDEgc3R5bGU9J21hcmdp bjowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0O2JhY2tncm91bmQ6d2hpdGUnPjxzcGFuIGxhbmc9 RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z LXNlcmlmIjtjb2xvcjpibGFjaztmb250LXdlaWdodDpub3JtYWwnPjxvOnA+Jm5ic3A7PC9vOnA+ PC9zcGFuPjwvaDE+PGgxIHN0eWxlPSdtYXJnaW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDti YWNrZ3JvdW5kOndoaXRlJz48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0 O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6YmxhY2s7Zm9udC13ZWln aHQ6bm9ybWFsJz5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvaDE+PGgxIHN0eWxlPSdtYXJn aW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDtiYWNrZ3JvdW5kOndoaXRlJz48c3BhbiBsYW5n PUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fu cy1zZXJpZiI7Y29sb3I6YmxhY2s7Zm9udC13ZWlnaHQ6bm9ybWFsJz5SYXdhdDxvOnA+PC9vOnA+ PC9zcGFuPjwvaDE+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2Nv bG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48ZGl2PjxkaXYgc3R5bGU9 J2JvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0 IDBjbSAwY20gMGNtJz48cCBjbGFzcz1Nc29Ob3JtYWw+PGI+PHNwYW4gbGFuZz1FTi1VUyBzdHls ZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7Y29s b3I6d2luZG93dGV4dCc+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2Zv bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO2NvbG9yOndp bmRvd3RleHQnPiA8YSBocmVmPSJtYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmci Pnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPC9hPiBbPGEgaHJlZj0ibWFpbHRvOnhlbi1h cGktYm91bmNlc0BsaXN0cy54ZW4ub3JnIj5tYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhl bi5vcmc8L2E+XSA8Yj5PbiBCZWhhbGYgT2YgPC9iPkdlb3JnZSBTaHVrbGluPGJyPjxiPlNlbnQ6 PC9iPiBUdWVzZGF5LCBKYW51YXJ5IDIyLCAyMDEzIDc6MjIgQU08YnI+PGI+VG86PC9iPiA8YSBo cmVmPSJtYWlsdG86eGVuLWFwaUBsaXN0cy54ZW4ub3JnIj54ZW4tYXBpQGxpc3RzLnhlbi5vcmc8 L2E+PGJyPjxiPlN1YmplY3Q6PC9iPiBSZTogW1hlbi1BUEldIFZNIE1pZ3JhdGlvbjxvOnA+PC9v OnA+PC9zcGFuPjwvcD48L2Rpdj48L2Rpdj48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1F Ti1VUz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu IGxhbmc9RU4tVVM+SSB0aGluayB5b3UgdXNpbmcgb3V0ZGF0ZWQgQVBJIGRvY3VtZW50YXRpb24u IE5vdCBzdXJlIGFib3V0IEFQSSBjYWxsLCBidXQgY29ycmVzcG9uZGluZyB4ZSBjYWxsIGNhbiBj b250YWlucyByZW1vdGUtaG9zdCwgcmVtb3RlLXVzZXJuYW1lLCByZW1vdGUtcGFzc3dvcmQgYW5k IHNvIG9uLiA8YnI+PGJyPk9uIDIxLjAxLjIwMTMgMjI6MTgsIFJhd2F0LCBWaXNod2FuYXRoIHdy b3RlOiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9 RU4tVVM+SGkgQWxsLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNw YW4gbGFuZz1FTi1VUz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgSSBhbSB3cml0 aW5nIHNvbWUgcGVybCBzY3JpcHRzIHRvIGRvIFZNIE1pZ3JhdGlvbiB1c2luZyBYZW4gQVBJcy48 bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+ VGhpcyBpcyB0aGUgQVBJIGNhbGwgSSBhbSB1c2luZyB0byBkbyBWTSBNaWdyYXRpb248bzpwPjwv bzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+Jm5ic3A7 PG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVT IHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCc+cG9vbF9taWdyYXRl IChzZXNzaW9uX2lkIHMsIFZNIHJlZiB2bSwgaG9zdCByZWYgaG9zdCwgKHN0cmluZyAtJmd0OyBz dHJpbmcpIE1hcCBvcHRpb25zKS48L3NwYW4+PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwv c3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQt c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01UVDEwJz4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz1F Ti1VUz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9 RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01UVDEwJz5Ob3cgaXQg aXMgYWxzbyBwb3NzaWJsZSB0byBtaWdyYXRlIGRhdGFzdG9yZSBhbG9uZyB3aXRoIFZNLiBJIHdv dWxkIGxpa2UgdG8ga25vdyB3aGF0IGlzIHRoZSBvcHRpb24gdGhhdCBJIGNhbiBwYXNzIHRvIGFi b3ZlIGZ1bmN0aW9uIHNvIHRoYXQgaXQgd2lsbCBhbHNvIG1pZ3JhdGUgZGF0YXN0b3JlLjwvc3Bh bj48c3BhbiBsYW5nPUVOLVVTPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3Jt YWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpD TVRUMTAnPiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPUVOLVVTPjxvOnA+PC9vOnA+PC9zcGFuPjwv cD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEw LjBwdDtmb250LWZhbWlseTpDTVRUMTAnPlJlZ2FyZHMsPC9zcGFuPjxzcGFuIGxhbmc9RU4tVVM+ PG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVT IHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCc+UmF3YXQ8L3NwYW4+ PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFs PjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01U VDEwJz4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+ PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+Jm5ic3A7PG86cD48L286cD48L3Nw YW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbToxMi4wcHQnPjxz cGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6IlRpbWVz IE5ldyBSb21hbiIsInNlcmlmIic+PGJyPjxicj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHByZT48 c3BhbiBsYW5nPUVOLVVTPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fPG86cD48L286cD48L3NwYW4+PC9wcmU+PHByZT48c3BhbiBsYW5nPUVOLVVTPlhlbi1h cGkgbWFpbGluZyBsaXN0PG86cD48L286cD48L3NwYW4+PC9wcmU+PHByZT48c3BhbiBsYW5nPUVO LVVTPjxhIGhyZWY9Im1haWx0bzpYZW4tYXBpQGxpc3RzLnhlbi5vcmciPlhlbi1hcGlAbGlzdHMu eGVuLm9yZzwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT48cHJlPjxzcGFuIGxhbmc9RU4tVVM+ PGEgaHJlZj0iaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hl bi1hcGkiPmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4t YXBpPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPjwvZGl2PjwvYm9keT48L2h0bWw+ --_000_7EA643C653F17F4C80DE959E978F10ED010E6CA10084LONPMAILBOX_-- --===============1517481114643203329== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1517481114643203329==-- From xen-api-bounces@lists.xen.org Tue Jan 22 08:47:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 08:47:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxZVN-0002tx-2x; Tue, 22 Jan 2013 08:46:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxZVL-0002ts-HE for xen-api@lists.xen.org; Tue, 22 Jan 2013 08:46:51 +0000 Received: from [85.158.143.35:56972] by server-3.bemta-4.messagelabs.com id 89/F9-10689-AF15EF05; Tue, 22 Jan 2013 08:46:50 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1358844396!16383257!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16229 invoked from network); 22 Jan 2013 08:46:36 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 08:46:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,513,1355097600"; d="scan'208,217";a="803642" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Jan 2013 08:46:36 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Tue, 22 Jan 2013 08:46:36 +0000 From: John Else To: "Rawat, Vishwanath" , George Shuklin , "xen-api@lists.xen.org" Date: Tue, 22 Jan 2013 08:46:56 +0000 Thread-Topic: [Xen-API] VM Migration Thread-Index: Ac33+OeqHnhY2v4qQ3+kjxm30/vuEAAjTfAAAAMiJFAABdVswA== Message-ID: <7EA643C653F17F4C80DE959E978F10ED010E6CA10084@LONPMAILBOX01.citrite.net> References: <7B89652AC48EE14E979D933CF09A0F1016ED9790@SACEXCMBX04-PRD.hq.netapp.com> <50FDF0C0.1070605@gmail.com> <7B89652AC48EE14E979D933CF09A0F1016EDCB64@SACEXCMBX04-PRD.hq.netapp.com> In-Reply-To: <7B89652AC48EE14E979D933CF09A0F1016EDCB64@SACEXCMBX04-PRD.hq.netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] VM Migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1517481114643203329==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1517481114643203329== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7EA643C653F17F4C80DE959E978F10ED010E6CA10084LONPMAILBOX_" --_000_7EA643C653F17F4C80DE959E978F10ED010E6CA10084LONPMAILBOX_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgUmF3YXQsDQoNClRoZSBBUEkgY2FsbCB5b3UgYXJlIHVzaW5nIGlzIHN0aWxsIHN1cHBvcnRl ZCwgYnV0IGl0IG9ubHkgbGV0cyB5b3UgZG8gbWlncmF0aW9uIHdpdGhpbiBhIHBvb2wsIHdpdGgg bm8gc3RvcmFnZSBtaWdyYXRpb24uDQoNCklmIHlvdSB3YW50IHRvIG1pZ3JhdGUgYSBWTSBhbmQg aXRzIHN0b3JhZ2UgKG1heWJlIGV2ZW4gYmV0d2VlbiBwb29scyksIHlvdSBmaXJzdCBuZWVkIHRv IGNhbGwgSG9zdC5taWdyYXRlX3JlY2VpdmUgKHNlZSBodHRwOi8vZG9jcy52bWQuY2l0cml4LmNv bS9YZW5TZXJ2ZXIvNi4xLjAvMS4wL2VuX2diL2FwaS8/Yz1ob3N0KSB3aXRoIHRoZSByZWZlcmVu Y2Ugb2YgdGhlIGhvc3QgeW91IHdpc2ggdG8gbWlncmF0ZSB0aGUgVk0gdG8uIFRoaXMgQVBJIGNh bGwgbmVlZHMgdG8gYmUgbWFkZSB0byB0aGUgbWFzdGVyIG9mIHRoZSBwb29sIHlvdSB3YW50IHRv IG1pZ3JhdGUgdG8gKG9idmlvdXNseSB0aGUgaG9zdCByZWZlcmVuY2UgbmVlZHMgdG8gYmUgb25l IG9mIHRoZSBob3N0cyBpbiB0aGlzIHBvb2wpLg0KDQpUaGlzIHdpbGwgcmV0dXJuIGEgdmFsdWUg b2YgdHlwZSAoc3RyaW5nIC0+IHN0cmluZykgbWFwLiBZb3UgdGhlbiBuZWVkIHRvIGNhbGwgVk0u bWlncmF0ZV9zZW5kIG9uIHRoZSBtYXN0ZXIgb2YgdGhlIHBvb2wgeW91IHdpc2ggdG8gbWlncmF0 ZSBmcm9tIChzZWUgaHR0cDovL2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4wLzEu MC9lbl9nYi9hcGkvP2M9Vk0pLiBUaGlzIGNvdWxkIGJlIGNhbGxlZCB0byB0aGUgc2FtZSBtYXN0 ZXIgYXMgYWJvdmUsIGlmIHlvdSBvbmx5IHdhbnQgdG8gZG8gYSBzdG9yYWdlIG1pZ3JhdGlvbiB3 aXRoaW4gYSBwb29sLg0KDQpUaGUgYXJndW1lbnRzIHRvIHRoaXMgZnVuY3Rpb24gYXJlLCBpbiBv cmRlcjoNCg0KVk0gcmVmOiBUaGlzIGlzIHRoZSBWTSB5b3Ugd2FudCB0byBtaWdyYXRlDQooc3Ry aW5nIC0+IHN0cmluZykgbWFwOiBUaGlzIGlzIHRoZSByZXR1cm4gdmFsdWUgeW91IHJlY2VpdmVk IGZyb20gSG9zdC5taWdyYXRlX3JlY2VpdmUgYWJvdmUuDQpib29sOiBUaGUgaXMgdGhlIOKAnGxp dmXigJ0gZmxhZy4gVGhpcyBtdXN0IGJlIOKAnHRydWXigJ0gYXQgdGhlIG1vbWVudC4NCihWREkg cmVmIC0+IFNSIHJlZikgbWFwOiBUaGlzIGluZGljYXRlcyB3aGljaCBTUiAoYXR0YWNoZWQgdG8g dGhlIGRlc3RpbmF0aW9uIGhvc3QpIGVhY2ggb2YgdGhlIFZN4oCZcyBWRElzIHdpbGwgYmUgbW92 ZWQgdG8uDQooVklGIHJlZiAtPiBuZXR3b3JrIHJlZikgbWFwOiBUaGlzIGluZGljYXRlcyB3aGlj aCBuZXR3b3JrIChwcmVzZW50IG9uIHRoZSBkZXN0aW5hdGlvbiBob3N0KSBlYWNoIG9mIHRoZSBW TeKAmXMgVklGcyB3aWxsIGJlIG1vdmVkIHRvLg0KKHN0cmluZyAtPiBzdHJpbmcpIG1hcDogRXh0 cmEgb3B0aW9ucyBmaWVsZCBmb3IgZnV0dXJlIGltcHJvdmVtZW50cyDigJMgbm90IHVzZWQgYXQg dGhlIG1vbWVudCAoanVzdCBwYXNzIGFuIGVtcHR5IGRpY3Rpb25hcnkpLg0KDQpBbHNvLCBpZiB5 b3Ugd2FudCB0byBtaWdyYXRlIGEgVkRJIGJldHdlZW4gU1JzIHdpdGhvdXQgbWlncmF0aW5nIHRo ZSBWTSB3aGljaCBvd25zIHRoZSBWREksIHlvdSBjYW4ganVzdCB1c2UgVkRJLnBvb2xfbWlncmF0 ZSAoc2VlIGh0dHA6Ly9kb2NzLnZtZC5jaXRyaXguY29tL1hlblNlcnZlci82LjEuMC8xLjAvZW5f Z2IvYXBpLz9jPVZESSkuIFRoZSBhcmd1bWVudHMgYXJlOg0KDQpWREkgcmVmOiBUaGUgVkRJIHlv dSB3YW50IHRvIG1vdmUuDQpTUiByZWY6IFRoZSBTUiB5b3Ugd2FudCB0byBtb3ZlIHRoZSBWRGkg dG8uDQooc3RyaW5nIC0+IHN0cmluZykgbWFwOiBhbm90aGVyIHVudXNlZCDigJxvcHRpb25z4oCd IGZpZWxkLg0KDQpIb3BlIHRoaXMgaGVscHMhDQoNCkpvaG4NCg0KRnJvbTogeGVuLWFwaS1ib3Vu Y2VzQGxpc3RzLnhlbi5vcmcgW21haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10g T24gQmVoYWxmIE9mIFJhd2F0LCBWaXNod2FuYXRoDQpTZW50OiAyMiBKYW51YXJ5IDIwMTMgMDg6 MjYNClRvOiBHZW9yZ2UgU2h1a2xpbjsgeGVuLWFwaUBsaXN0cy54ZW4ub3JnDQpTdWJqZWN0OiBS ZTogW1hlbi1BUEldIFZNIE1pZ3JhdGlvbg0KDQpJIGhhdmUgZG93bmxvYWRlZCB0aGUgbGF0ZXN0 IEFQSSBndWlkZShYZW5TZXJ2ZXIgNi4xLjAgTWFuYWdlbWVudCBBUEkgR3VpZGUpLiBQcm90b3R5 cGUgb2YgcG9vbF9taWdyYXRlIGlzIHN0aWxsIHNhbWUgaW4gbmV3IG1hbmFnZW1lbnQgQVBJIGd1 aWRlLg0KcG9vbF9taWdyYXRlIChzZXNzaW9uX2lkIHMsIFZNIHJlZiB2bSwgaG9zdCByZWYgaG9z dCwgKHN0cmluZyAtPiBzdHJpbmcpIE1hcCBvcHRpb25zKS4NCg0KSSB0aGluayB0aGVyZSBzaG91 bGQgYmUgc29tZSBwYXJhbSB0aGF0IEkgY2FuIHBhc3MgYXMgcGFydCBvZiDigJxNYXAgb3B0aW9u c+KAnSBtZW50aW9uZWQgaW4gYWJvdmUgcHJvdG90eXBlLiBJIGp1c3QgZG9u4oCZdCBrbm93IG9w dGlvbiBuYW1lIGFuZCBpdHMgdmFsdWUuDQoNClJlZ2FyZHMsDQpSYXdhdA0KDQpGcm9tOiB4ZW4t YXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZzxtYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhl bi5vcmc+IFttYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmddIE9uIEJlaGFsZiBP ZiBHZW9yZ2UgU2h1a2xpbg0KU2VudDogVHVlc2RheSwgSmFudWFyeSAyMiwgMjAxMyA3OjIyIEFN DQpUbzogeGVuLWFwaUBsaXN0cy54ZW4ub3JnPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbi5vcmc+ DQpTdWJqZWN0OiBSZTogW1hlbi1BUEldIFZNIE1pZ3JhdGlvbg0KDQpJIHRoaW5rIHlvdSB1c2lu ZyBvdXRkYXRlZCBBUEkgZG9jdW1lbnRhdGlvbi4gTm90IHN1cmUgYWJvdXQgQVBJIGNhbGwsIGJ1 dCBjb3JyZXNwb25kaW5nIHhlIGNhbGwgY2FuIGNvbnRhaW5zIHJlbW90ZS1ob3N0LCByZW1vdGUt dXNlcm5hbWUsIHJlbW90ZS1wYXNzd29yZCBhbmQgc28gb24uDQoNCk9uIDIxLjAxLjIwMTMgMjI6 MTgsIFJhd2F0LCBWaXNod2FuYXRoIHdyb3RlOg0KSGkgQWxsLA0KICAgICAgICAgICAgICAgIEkg YW0gd3JpdGluZyBzb21lIHBlcmwgc2NyaXB0cyB0byBkbyBWTSBNaWdyYXRpb24gdXNpbmcgWGVu IEFQSXMuDQpUaGlzIGlzIHRoZSBBUEkgY2FsbCBJIGFtIHVzaW5nIHRvIGRvIFZNIE1pZ3JhdGlv bg0KDQpwb29sX21pZ3JhdGUgKHNlc3Npb25faWQgcywgVk0gcmVmIHZtLCBob3N0IHJlZiBob3N0 LCAoc3RyaW5nIC0+IHN0cmluZykgTWFwIG9wdGlvbnMpLg0KDQpOb3cgaXQgaXMgYWxzbyBwb3Nz aWJsZSB0byBtaWdyYXRlIGRhdGFzdG9yZSBhbG9uZyB3aXRoIFZNLiBJIHdvdWxkIGxpa2UgdG8g a25vdyB3aGF0IGlzIHRoZSBvcHRpb24gdGhhdCBJIGNhbiBwYXNzIHRvIGFib3ZlIGZ1bmN0aW9u IHNvIHRoYXQgaXQgd2lsbCBhbHNvIG1pZ3JhdGUgZGF0YXN0b3JlLg0KDQpSZWdhcmRzLA0KUmF3 YXQNCg0KDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXw0KDQpYZW4tYXBpIG1haWxpbmcgbGlzdA0KDQpYZW4tYXBpQGxpc3RzLnhlbi5vcmc8bWFp bHRvOlhlbi1hcGlAbGlzdHMueGVuLm9yZz4NCg0KaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJp bi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkNCg== --_000_7EA643C653F17F4C80DE959E978F10ED010E6CA10084LONPMAILBOX_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5 OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJ e2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30N CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q01UVDEwO30NCi8qIFN0eWxlIERlZmluaXRpb25z ICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjow Y207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1m YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjpibGFjazt9DQpoMQ0KCXttc28t c3R5bGUtcHJpb3JpdHk6OTsNCgltc28tc3R5bGUtbGluazoiSGVhZGluZyAxIENoYXIiOw0KCW1z by1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1i b3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQtc2l6ZToyNC4wcHQ7DQoJ Zm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxpbmssIHNwYW4uTXNv SHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQt ZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxv d2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNv cmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1z dHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdp bi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3Vy aWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBk aXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6 IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFw dDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYi Ow0KCWNvbG9yOmJsYWNrO30NCnNwYW4uSGVhZGluZzFDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJI ZWFkaW5nIDEgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk7DQoJbXNvLXN0eWxlLWxpbms6 IkhlYWRpbmcgMSI7DQoJZm9udC13ZWlnaHQ6Ym9sZDt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRD aGFyDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5 bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglm b250LWZhbWlseTpDb25zb2xhczsNCgljb2xvcjpibGFjazt9DQpzcGFuLkVtYWlsU3R5bGUyMA0K CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt c2VyaWYiOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0 eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsN Cgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTIyDQoJe21zby1zdHlsZS10eXBlOnBl cnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29s b3I6IzFGNDk3RDt9DQpzcGFuLkJhbGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFs bG9vbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGlu azoiQmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7DQoJ Y29sb3I6YmxhY2s7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9u bHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIu MHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYu V29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBn dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIx MDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpz aGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIg Lz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT48L2hlYWQ+PGJvZHkgYmdjb2xv cj13aGl0ZSBsYW5nPUVOLUdCIGxpbms9Ymx1ZSB2bGluaz1wdXJwbGU+PGRpdiBjbGFzcz1Xb3Jk U2VjdGlvbjE+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjp3aW5kb3d0ZXh0 Jz5IaSBSYXdhdCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu IHN0eWxlPSdjb2xvcjp3aW5kb3d0ZXh0Jz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAg Y2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjp3aW5kb3d0ZXh0Jz5UaGUgQVBJIGNh bGwgeW91IGFyZSB1c2luZyBpcyBzdGlsbCBzdXBwb3J0ZWQsIGJ1dCBpdCBvbmx5IGxldHMgeW91 IGRvIG1pZ3JhdGlvbiB3aXRoaW4gYSBwb29sLCB3aXRoIG5vIHN0b3JhZ2UgbWlncmF0aW9uLjxv OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9y OiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+ PHNwYW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQnPklmIHlvdSB3YW50IHRvIG1pZ3JhdGUgYSBW TSBhbmQgaXRzIHN0b3JhZ2UgKG1heWJlIGV2ZW4gYmV0d2VlbiBwb29scyksIHlvdSBmaXJzdCBu ZWVkIHRvIGNhbGwgSG9zdC5taWdyYXRlX3JlY2VpdmUgKHNlZSA8L3NwYW4+PGEgaHJlZj0iaHR0 cDovL2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4wLzEuMC9lbl9nYi9hcGkvP2M9 aG9zdCI+aHR0cDovL2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4wLzEuMC9lbl9n Yi9hcGkvP2M9aG9zdDwvYT4pIHdpdGggdGhlIHJlZmVyZW5jZSBvZiB0aGUgaG9zdCB5b3Ugd2lz aCB0byBtaWdyYXRlIHRoZSBWTSB0by4gVGhpcyBBUEkgY2FsbCBuZWVkcyB0byBiZSBtYWRlIHRv IHRoZSBtYXN0ZXIgb2YgdGhlIHBvb2wgeW91IHdhbnQgdG8gbWlncmF0ZSB0byAob2J2aW91c2x5 IHRoZSBob3N0IHJlZmVyZW5jZSBuZWVkcyB0byBiZSBvbmUgb2YgdGhlIGhvc3RzIGluIHRoaXMg cG9vbCkuPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+ PC9wPjxwIGNsYXNzPU1zb05vcm1hbD5UaGlzIHdpbGwgcmV0dXJuIGEgdmFsdWUgb2YgdHlwZSAo c3RyaW5nIC0mZ3Q7IHN0cmluZykgbWFwLiBZb3UgdGhlbiBuZWVkIHRvIGNhbGwgVk0ubWlncmF0 ZV9zZW5kIG9uIHRoZSBtYXN0ZXIgb2YgdGhlIHBvb2wgeW91IHdpc2ggdG8gbWlncmF0ZSBmcm9t IChzZWUgPGEgaHJlZj0iaHR0cDovL2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4w LzEuMC9lbl9nYi9hcGkvP2M9Vk0iPmh0dHA6Ly9kb2NzLnZtZC5jaXRyaXguY29tL1hlblNlcnZl ci82LjEuMC8xLjAvZW5fZ2IvYXBpLz9jPVZNPC9hPikuIFRoaXMgY291bGQgYmUgY2FsbGVkIHRv IHRoZSBzYW1lIG1hc3RlciBhcyBhYm92ZSwgaWYgeW91IG9ubHkgd2FudCB0byBkbyBhIHN0b3Jh Z2UgbWlncmF0aW9uIHdpdGhpbiBhIHBvb2wuPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9y bWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD5UaGUgYXJndW1lbnRz IHRvIHRoaXMgZnVuY3Rpb24gYXJlLCBpbiBvcmRlcjo8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1N c29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPlZNIHJlZjog VGhpcyBpcyB0aGUgVk0geW91IHdhbnQgdG8gbWlncmF0ZTxvOnA+PC9vOnA+PC9wPjxwIGNsYXNz PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4dCc+KHN0cmluZyAtJmd0OyBz dHJpbmcpIG1hcDogVGhpcyBpcyB0aGUgcmV0dXJuIHZhbHVlIHlvdSByZWNlaXZlZCBmcm9tIEhv c3QubWlncmF0ZV9yZWNlaXZlIGFib3ZlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1N c29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQnPmJvb2w6IFRoZSBpcyB0aGUg 4oCcbGl2ZeKAnSBmbGFnLiBUaGlzIG11c3QgYmUg4oCcdHJ1ZeKAnSBhdCB0aGUgbW9tZW50Ljxv OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9y OndpbmRvd3RleHQnPihWREkgcmVmIC0mZ3Q7IFNSIHJlZikgbWFwOiBUaGlzIGluZGljYXRlcyB3 aGljaCBTUiAoYXR0YWNoZWQgdG8gdGhlIGRlc3RpbmF0aW9uIGhvc3QpIGVhY2ggb2YgdGhlIFZN 4oCZcyBWRElzIHdpbGwgYmUgbW92ZWQgdG8uPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNz PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4dCc+KFZJRiByZWYgLSZndDsg bmV0d29yayByZWYpIG1hcDogVGhpcyBpbmRpY2F0ZXMgd2hpY2ggbmV0d29yayAocHJlc2VudCBv biB0aGUgZGVzdGluYXRpb24gaG9zdCkgZWFjaCBvZiB0aGUgVk3igJlzIFZJRnMgd2lsbCBiZSBt b3ZlZCB0by48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0 eWxlPSdjb2xvcjp3aW5kb3d0ZXh0Jz4oc3RyaW5nIC0mZ3Q7IHN0cmluZykgbWFwOiBFeHRyYSBv cHRpb25zIGZpZWxkIGZvciBmdXR1cmUgaW1wcm92ZW1lbnRzIOKAkyBub3QgdXNlZCBhdCB0aGUg bW9tZW50IChqdXN0IHBhc3MgYW4gZW1wdHkgZGljdGlvbmFyeSkuPG86cD48L286cD48L3NwYW4+ PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4dCc+PG86 cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n Y29sb3I6d2luZG93dGV4dCc+QWxzbywgaWYgeW91IHdhbnQgdG8gbWlncmF0ZSBhIFZESSBiZXR3 ZWVuIFNScyB3aXRob3V0IG1pZ3JhdGluZyB0aGUgVk0gd2hpY2ggb3ducyB0aGUgVkRJLCB5b3Ug Y2FuIGp1c3QgdXNlIFZESS5wb29sX21pZ3JhdGUgKHNlZSA8L3NwYW4+PGEgaHJlZj0iaHR0cDov L2RvY3Mudm1kLmNpdHJpeC5jb20vWGVuU2VydmVyLzYuMS4wLzEuMC9lbl9nYi9hcGkvP2M9VkRJ Ij5odHRwOi8vZG9jcy52bWQuY2l0cml4LmNvbS9YZW5TZXJ2ZXIvNi4xLjAvMS4wL2VuX2diL2Fw aS8/Yz1WREk8L2E+KS4gVGhlIGFyZ3VtZW50cyBhcmU6PG86cD48L286cD48L3A+PHAgY2xhc3M9 TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD5WREkgcmVm OiBUaGUgVkRJIHlvdSB3YW50IHRvIG1vdmUuPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9y bWFsPlNSIHJlZjogVGhlIFNSIHlvdSB3YW50IHRvIG1vdmUgdGhlIFZEaSB0by48bzpwPjwvbzpw PjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+KHN0cmluZyAtJmd0OyBzdHJpbmcpIG1hcDogYW5vdGhl ciB1bnVzZWQg4oCcb3B0aW9uc+KAnSBmaWVsZC48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4 dCc+PG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n Y29sb3I6d2luZG93dGV4dCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1z b05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4dCc+SG9wZSB0aGlzIGhlbHBzITxv OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9y OndpbmRvd3RleHQnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3Jt YWw+PHNwYW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQnPkpvaG48bzpwPjwvbzpwPjwvc3Bhbj48 L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz48bzpwPiZu YnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRpdj48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3JkZXIt dG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSc+PHAgY2xh c3M9TXNvTm9ybWFsPjxiPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7 Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO2NvbG9yOndpbmRvd3RleHQnPkZyb206 PC9zcGFuPjwvYj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQt ZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjtjb2xvcjp3aW5kb3d0ZXh0Jz4geGVuLWFwaS1i b3VuY2VzQGxpc3RzLnhlbi5vcmcgW21haWx0bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9y Z10gPGI+T24gQmVoYWxmIE9mIDwvYj5SYXdhdCwgVmlzaHdhbmF0aDxicj48Yj5TZW50OjwvYj4g MjIgSmFudWFyeSAyMDEzIDA4OjI2PGJyPjxiPlRvOjwvYj4gR2VvcmdlIFNodWtsaW47IHhlbi1h cGlAbGlzdHMueGVuLm9yZzxicj48Yj5TdWJqZWN0OjwvYj4gUmU6IFtYZW4tQVBJXSBWTSBNaWdy YXRpb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFs PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxoMSBzdHlsZT0nbWFyZ2luOjBjbTttYXJnaW4tYm90dG9t Oi4wMDAxcHQ7YmFja2dyb3VuZDp3aGl0ZSc+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1z aXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOmJsYWNr O2ZvbnQtd2VpZ2h0Om5vcm1hbCc+SSBoYXZlIGRvd25sb2FkZWQgdGhlIGxhdGVzdCBBUEkgZ3Vp ZGUoWGVuU2VydmVyIDYuMS4wIE1hbmFnZW1lbnQgQVBJIEd1aWRlKS4gUHJvdG90eXBlIG9mIHBv b2xfbWlncmF0ZSBpcyBzdGlsbCBzYW1lIGluIG5ldyBtYW5hZ2VtZW50IEFQSSBndWlkZS48bzpw PjwvbzpwPjwvc3Bhbj48L2gxPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0 eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCc+cG9vbF9taWdyYXRlIChz ZXNzaW9uX2lkIHMsIFZNIHJlZiB2bSwgaG9zdCByZWYgaG9zdCwgKHN0cmluZyAtJmd0OyBzdHJp bmcpIE1hcCBvcHRpb25zKS48L3NwYW4+PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwvc3Bh bj48L3A+PGgxIHN0eWxlPSdtYXJnaW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDtiYWNrZ3Jv dW5kOndoaXRlJz48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQt ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6YmxhY2s7Zm9udC13ZWlnaHQ6bm9y bWFsJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2gxPjxoMSBzdHlsZT0nbWFyZ2luOjBjbTtt YXJnaW4tYm90dG9tOi4wMDAxcHQ7YmFja2dyb3VuZDp3aGl0ZSc+PHNwYW4gbGFuZz1FTi1VUyBz dHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYi O2NvbG9yOmJsYWNrO2ZvbnQtd2VpZ2h0Om5vcm1hbCc+SSB0aGluayB0aGVyZSBzaG91bGQgYmUg c29tZSBwYXJhbSB0aGF0IEkgY2FuIHBhc3MgYXMgcGFydCBvZiDigJxNYXAgb3B0aW9uc+KAnSBt ZW50aW9uZWQgaW4gYWJvdmUgcHJvdG90eXBlLiBJIGp1c3QgZG9u4oCZdCBrbm93IG9wdGlvbiBu YW1lIGFuZCBpdHMgdmFsdWUuPG86cD48L286cD48L3NwYW4+PC9oMT48aDEgc3R5bGU9J21hcmdp bjowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0O2JhY2tncm91bmQ6d2hpdGUnPjxzcGFuIGxhbmc9 RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z LXNlcmlmIjtjb2xvcjpibGFjaztmb250LXdlaWdodDpub3JtYWwnPjxvOnA+Jm5ic3A7PC9vOnA+ PC9zcGFuPjwvaDE+PGgxIHN0eWxlPSdtYXJnaW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDti YWNrZ3JvdW5kOndoaXRlJz48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0 O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6YmxhY2s7Zm9udC13ZWln aHQ6bm9ybWFsJz5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvaDE+PGgxIHN0eWxlPSdtYXJn aW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDtiYWNrZ3JvdW5kOndoaXRlJz48c3BhbiBsYW5n PUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fu cy1zZXJpZiI7Y29sb3I6YmxhY2s7Zm9udC13ZWlnaHQ6bm9ybWFsJz5SYXdhdDxvOnA+PC9vOnA+ PC9zcGFuPjwvaDE+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2Nv bG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48ZGl2PjxkaXYgc3R5bGU9 J2JvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0 IDBjbSAwY20gMGNtJz48cCBjbGFzcz1Nc29Ob3JtYWw+PGI+PHNwYW4gbGFuZz1FTi1VUyBzdHls ZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7Y29s b3I6d2luZG93dGV4dCc+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2Zv bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO2NvbG9yOndp bmRvd3RleHQnPiA8YSBocmVmPSJtYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmci Pnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnPC9hPiBbPGEgaHJlZj0ibWFpbHRvOnhlbi1h cGktYm91bmNlc0BsaXN0cy54ZW4ub3JnIj5tYWlsdG86eGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhl bi5vcmc8L2E+XSA8Yj5PbiBCZWhhbGYgT2YgPC9iPkdlb3JnZSBTaHVrbGluPGJyPjxiPlNlbnQ6 PC9iPiBUdWVzZGF5LCBKYW51YXJ5IDIyLCAyMDEzIDc6MjIgQU08YnI+PGI+VG86PC9iPiA8YSBo cmVmPSJtYWlsdG86eGVuLWFwaUBsaXN0cy54ZW4ub3JnIj54ZW4tYXBpQGxpc3RzLnhlbi5vcmc8 L2E+PGJyPjxiPlN1YmplY3Q6PC9iPiBSZTogW1hlbi1BUEldIFZNIE1pZ3JhdGlvbjxvOnA+PC9v OnA+PC9zcGFuPjwvcD48L2Rpdj48L2Rpdj48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1F Ti1VUz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu IGxhbmc9RU4tVVM+SSB0aGluayB5b3UgdXNpbmcgb3V0ZGF0ZWQgQVBJIGRvY3VtZW50YXRpb24u IE5vdCBzdXJlIGFib3V0IEFQSSBjYWxsLCBidXQgY29ycmVzcG9uZGluZyB4ZSBjYWxsIGNhbiBj b250YWlucyByZW1vdGUtaG9zdCwgcmVtb3RlLXVzZXJuYW1lLCByZW1vdGUtcGFzc3dvcmQgYW5k IHNvIG9uLiA8YnI+PGJyPk9uIDIxLjAxLjIwMTMgMjI6MTgsIFJhd2F0LCBWaXNod2FuYXRoIHdy b3RlOiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9 RU4tVVM+SGkgQWxsLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNw YW4gbGFuZz1FTi1VUz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgSSBhbSB3cml0 aW5nIHNvbWUgcGVybCBzY3JpcHRzIHRvIGRvIFZNIE1pZ3JhdGlvbiB1c2luZyBYZW4gQVBJcy48 bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+ VGhpcyBpcyB0aGUgQVBJIGNhbGwgSSBhbSB1c2luZyB0byBkbyBWTSBNaWdyYXRpb248bzpwPjwv bzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+Jm5ic3A7 PG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVT IHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCc+cG9vbF9taWdyYXRl IChzZXNzaW9uX2lkIHMsIFZNIHJlZiB2bSwgaG9zdCByZWYgaG9zdCwgKHN0cmluZyAtJmd0OyBz dHJpbmcpIE1hcCBvcHRpb25zKS48L3NwYW4+PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwv c3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQt c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01UVDEwJz4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz1F Ti1VUz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9 RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01UVDEwJz5Ob3cgaXQg aXMgYWxzbyBwb3NzaWJsZSB0byBtaWdyYXRlIGRhdGFzdG9yZSBhbG9uZyB3aXRoIFZNLiBJIHdv dWxkIGxpa2UgdG8ga25vdyB3aGF0IGlzIHRoZSBvcHRpb24gdGhhdCBJIGNhbiBwYXNzIHRvIGFi b3ZlIGZ1bmN0aW9uIHNvIHRoYXQgaXQgd2lsbCBhbHNvIG1pZ3JhdGUgZGF0YXN0b3JlLjwvc3Bh bj48c3BhbiBsYW5nPUVOLVVTPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3Jt YWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpD TVRUMTAnPiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPUVOLVVTPjxvOnA+PC9vOnA+PC9zcGFuPjwv cD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEw LjBwdDtmb250LWZhbWlseTpDTVRUMTAnPlJlZ2FyZHMsPC9zcGFuPjxzcGFuIGxhbmc9RU4tVVM+ PG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVT IHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNNVFQxMCc+UmF3YXQ8L3NwYW4+ PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFs PjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q01U VDEwJz4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+ PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+Jm5ic3A7PG86cD48L286cD48L3Nw YW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbToxMi4wcHQnPjxz cGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6IlRpbWVz IE5ldyBSb21hbiIsInNlcmlmIic+PGJyPjxicj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHByZT48 c3BhbiBsYW5nPUVOLVVTPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fPG86cD48L286cD48L3NwYW4+PC9wcmU+PHByZT48c3BhbiBsYW5nPUVOLVVTPlhlbi1h cGkgbWFpbGluZyBsaXN0PG86cD48L286cD48L3NwYW4+PC9wcmU+PHByZT48c3BhbiBsYW5nPUVO LVVTPjxhIGhyZWY9Im1haWx0bzpYZW4tYXBpQGxpc3RzLnhlbi5vcmciPlhlbi1hcGlAbGlzdHMu eGVuLm9yZzwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT48cHJlPjxzcGFuIGxhbmc9RU4tVVM+ PGEgaHJlZj0iaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hl bi1hcGkiPmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4t YXBpPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPjwvZGl2PjwvYm9keT48L2h0bWw+ --_000_7EA643C653F17F4C80DE959E978F10ED010E6CA10084LONPMAILBOX_-- --===============1517481114643203329== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1517481114643203329==-- From xen-api-bounces@lists.xen.org Tue Jan 22 09:34:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 09:34:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxaFg-0004Bw-0w; Tue, 22 Jan 2013 09:34:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxaFe-0004Bj-8d for xen-api@lists.xen.org; Tue, 22 Jan 2013 09:34:42 +0000 Received: from [85.158.143.99:41288] by server-3.bemta-4.messagelabs.com id 3C/B1-10689-13D5EF05; Tue, 22 Jan 2013 09:34:41 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1358847279!21929969!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32062 invoked from network); 22 Jan 2013 09:34:40 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 09:34:40 -0000 Received: by mail-lb0-f181.google.com with SMTP id gm6so1107856lbb.26 for ; Tue, 22 Jan 2013 01:34:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=ngHCMgWfrMpN5c999pZo1GS11f1AnrcL6X1r3yt57T4=; b=kRmObsMNPG84BsLXx+pxG3yFVUvkrh/rFRQlH3TTw+BCBUl8Gf4nlTTb69kpPtDfLF wF+Q35zjprUuaY2SL4z/BfUUSTHkxmqhH/cOaiv1JkuC/UgzZJOjwCGtqGuj7E6ZV049 le9CvIRynVaU+i8a7HveN7G4X1TlEWcXUXFONL1bcQ0kVLT97XHOagdsLNGg/cbVmM9I AESXGERvAhccMsl4wFYwQg+R94vs9Vjz/zTTXQw92RdE7fAiwLs35a+bkd5HcTbjWssq idHTdf8uu0U7FicdjKRP5aVz0jW+WQDtqFEjDLZCmfsw+2kTl3i7fdyMZKLxRhWOBxFR /1pQ== X-Received: by 10.152.133.130 with SMTP id pc2mr6396982lab.51.1358847279506; Tue, 22 Jan 2013 01:34:39 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:2458:d561:8ffa:b3f4? ([2a00:ab00:0:fffe:2458:d561:8ffa:b3f4]) by mx.google.com with ESMTPS id ns7sm6592824lab.5.2013.01.22.01.34.38 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jan 2013 01:34:38 -0800 (PST) Message-ID: <50FE5D2D.7080809@gmail.com> Date: Tue, 22 Jan 2013 13:34:37 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] A question of Virtual Disk(VHD) size in thin provisioning NFS SR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3283863584655196694==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3283863584655196694== Content-Type: multipart/alternative; boundary="------------010706050909030703010600" This is a multi-part message in MIME format. --------------010706050909030703010600 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit difference between disk size in OS (blockdev --getsize64 /dev/xvda) and VHD size is thin provision stuff. difference between du and caused by holes in file (sparce file). Please note, that VDI can consists from few VHD files (so called VHD tree). That usually happens with cross-pool migration, snapshots and vm clonning. 22.01.2013 07:15, ND KK ?????: > Hello all, > I have a question. But my English is very poor, I hope you will understand > > My VM has one virtual disk which /allocated /*100G*// > > I find the utilization of this disk in /guest OS is /*39.5G *( Get > utilization on guest OS file system) > > but I ssh to the NFS server check the VHD files size > I use command:/ls -lh VHD_FILE_NAME /( Get utilization on NFS server > file system) > It show that > /-rw-r--r-- 1 root root *19G* Jan 22 2013 XXXXXXX.vhd/ > / > / > Then, I use command:/du -sh VHD_FILE_NAM/E ( Get physical utilization > on disk ) > It show that > /*5.5G* XXXXXXXX.vhd/ > / > / > / > / > /My question is what happen in this //process ( 100G -> 39.5G -> 19G > -> 5.5G )//? / > > Are they representing XenServer's thin provision, VHD's thin > provision and File System sparse file ? > > Does XenServer's thin provision equals VHD's thin provision? VHD's > thin provision equals File System sparse file ? > > If yes, what happen in this process?/ > > / > Thanks > > - > Best Regards, > Leo Hsu > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------010706050909030703010600 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
difference between disk size in OS (blockdev --getsize64 /dev/xvda) and VHD size is thin provision stuff.

difference between du and caused by holes in file (sparce file).

Please note, that VDI can consists from few VHD files (so called VHD tree). That usually happens with cross-pool migration, snapshots and vm clonning.

22.01.2013 07:15, ND KK пишет:
Hello all, 
I have a question. But my English is very poor, I hope you will understand

My VM has one virtual disk which allocated 100G 

I find the utilization of this disk in guest OS is 39.5G ( Get utilization on guest OS file system)

but  I ssh to the NFS server check the VHD files size
I use command: ls -lh  VHD_FILE_NAME ( Get utilization on NFS server file system)
It show that 
-rw-r--r-- 1 root root 19G Jan 22  2013 XXXXXXX.vhd

Then, I use command: du -sh VHD_FILE_NAME ( Get physical utilization on disk )
It show that 
5.5G  XXXXXXXX.vhd


My question is what happen in this process ( 100G -> 39.5G -> 19G -> 5.5G )? 

Are they representing  XenServer's thin provision, VHD's thin provision and File System sparse file ?

Does XenServer's thin provision equals VHD's thin provision? VHD's thin provision equals File System sparse file ?

If yes,  what happen in this process?

Thanks

-
Best Regards,
Leo Hsu


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------010706050909030703010600-- --===============3283863584655196694== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3283863584655196694==-- From xen-api-bounces@lists.xen.org Tue Jan 22 09:34:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 09:34:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxaFg-0004Bw-0w; Tue, 22 Jan 2013 09:34:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxaFe-0004Bj-8d for xen-api@lists.xen.org; Tue, 22 Jan 2013 09:34:42 +0000 Received: from [85.158.143.99:41288] by server-3.bemta-4.messagelabs.com id 3C/B1-10689-13D5EF05; Tue, 22 Jan 2013 09:34:41 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1358847279!21929969!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32062 invoked from network); 22 Jan 2013 09:34:40 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 09:34:40 -0000 Received: by mail-lb0-f181.google.com with SMTP id gm6so1107856lbb.26 for ; Tue, 22 Jan 2013 01:34:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=ngHCMgWfrMpN5c999pZo1GS11f1AnrcL6X1r3yt57T4=; b=kRmObsMNPG84BsLXx+pxG3yFVUvkrh/rFRQlH3TTw+BCBUl8Gf4nlTTb69kpPtDfLF wF+Q35zjprUuaY2SL4z/BfUUSTHkxmqhH/cOaiv1JkuC/UgzZJOjwCGtqGuj7E6ZV049 le9CvIRynVaU+i8a7HveN7G4X1TlEWcXUXFONL1bcQ0kVLT97XHOagdsLNGg/cbVmM9I AESXGERvAhccMsl4wFYwQg+R94vs9Vjz/zTTXQw92RdE7fAiwLs35a+bkd5HcTbjWssq idHTdf8uu0U7FicdjKRP5aVz0jW+WQDtqFEjDLZCmfsw+2kTl3i7fdyMZKLxRhWOBxFR /1pQ== X-Received: by 10.152.133.130 with SMTP id pc2mr6396982lab.51.1358847279506; Tue, 22 Jan 2013 01:34:39 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:2458:d561:8ffa:b3f4? ([2a00:ab00:0:fffe:2458:d561:8ffa:b3f4]) by mx.google.com with ESMTPS id ns7sm6592824lab.5.2013.01.22.01.34.38 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jan 2013 01:34:38 -0800 (PST) Message-ID: <50FE5D2D.7080809@gmail.com> Date: Tue, 22 Jan 2013 13:34:37 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] A question of Virtual Disk(VHD) size in thin provisioning NFS SR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3283863584655196694==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3283863584655196694== Content-Type: multipart/alternative; boundary="------------010706050909030703010600" This is a multi-part message in MIME format. --------------010706050909030703010600 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit difference between disk size in OS (blockdev --getsize64 /dev/xvda) and VHD size is thin provision stuff. difference between du and caused by holes in file (sparce file). Please note, that VDI can consists from few VHD files (so called VHD tree). That usually happens with cross-pool migration, snapshots and vm clonning. 22.01.2013 07:15, ND KK ?????: > Hello all, > I have a question. But my English is very poor, I hope you will understand > > My VM has one virtual disk which /allocated /*100G*// > > I find the utilization of this disk in /guest OS is /*39.5G *( Get > utilization on guest OS file system) > > but I ssh to the NFS server check the VHD files size > I use command:/ls -lh VHD_FILE_NAME /( Get utilization on NFS server > file system) > It show that > /-rw-r--r-- 1 root root *19G* Jan 22 2013 XXXXXXX.vhd/ > / > / > Then, I use command:/du -sh VHD_FILE_NAM/E ( Get physical utilization > on disk ) > It show that > /*5.5G* XXXXXXXX.vhd/ > / > / > / > / > /My question is what happen in this //process ( 100G -> 39.5G -> 19G > -> 5.5G )//? / > > Are they representing XenServer's thin provision, VHD's thin > provision and File System sparse file ? > > Does XenServer's thin provision equals VHD's thin provision? VHD's > thin provision equals File System sparse file ? > > If yes, what happen in this process?/ > > / > Thanks > > - > Best Regards, > Leo Hsu > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------010706050909030703010600 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
difference between disk size in OS (blockdev --getsize64 /dev/xvda) and VHD size is thin provision stuff.

difference between du and caused by holes in file (sparce file).

Please note, that VDI can consists from few VHD files (so called VHD tree). That usually happens with cross-pool migration, snapshots and vm clonning.

22.01.2013 07:15, ND KK пишет:
Hello all, 
I have a question. But my English is very poor, I hope you will understand

My VM has one virtual disk which allocated 100G 

I find the utilization of this disk in guest OS is 39.5G ( Get utilization on guest OS file system)

but  I ssh to the NFS server check the VHD files size
I use command: ls -lh  VHD_FILE_NAME ( Get utilization on NFS server file system)
It show that 
-rw-r--r-- 1 root root 19G Jan 22  2013 XXXXXXX.vhd

Then, I use command: du -sh VHD_FILE_NAME ( Get physical utilization on disk )
It show that 
5.5G  XXXXXXXX.vhd


My question is what happen in this process ( 100G -> 39.5G -> 19G -> 5.5G )? 

Are they representing  XenServer's thin provision, VHD's thin provision and File System sparse file ?

Does XenServer's thin provision equals VHD's thin provision? VHD's thin provision equals File System sparse file ?

If yes,  what happen in this process?

Thanks

-
Best Regards,
Leo Hsu


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------010706050909030703010600-- --===============3283863584655196694== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3283863584655196694==-- From xen-api-bounces@lists.xen.org Tue Jan 22 12:39:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 12:39:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Txd87-00058B-Ea; Tue, 22 Jan 2013 12:39:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Txd86-00057w-56; Tue, 22 Jan 2013 12:39:06 +0000 Received: from [85.158.143.35:9689] by server-1.bemta-4.messagelabs.com id 86/B0-05635-9688EF05; Tue, 22 Jan 2013 12:39:05 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1358858314!15352931!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9485 invoked from network); 22 Jan 2013 12:38:35 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 12:38:35 -0000 Received: by mail-la0-f41.google.com with SMTP id fo12so1898154lab.0 for ; Tue, 22 Jan 2013 04:38:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=TGgSnCooMzvkaJkjMWCoN9sBxk9Zgu5Ml4Pcg3dkX1U=; b=yC6htQLa2ScSdBsBT/j5rgZ5hAekgQmmOqGRQD5Lp4j9G+3gDJd5MA1PzQ0A0WvJeT P2VX+SHpdYl1TZVZ4YUb41UgnJXGtxr0MQZOTMwZlhmpb2uD7sMmvY3bYJZ87B6bw0Uh GL2lUxyPkJayadfBYFrsaCD4kn1AkTksJ0DGa7NL2cmFA4PGP8EKCirU3FHS9YXOaUGz w9dM14Mmu5Wk6oclr5oVktDShjwHryo9PDBXTaEmUp+X6QTx3aVleH3kr0JV8JzqZQwb nuXSl24KPkOLbpOB1tOLGTdr4/gGU0VxIRJ3KGz3PADY5J/f37Hdi0a+yjjsyX+RlPSU 8qxQ== X-Received: by 10.152.111.72 with SMTP id ig8mr20913647lab.1.1358858313567; Tue, 22 Jan 2013 04:38:33 -0800 (PST) Received: from [172.16.26.11] (b0fb48e2.bb.sky.com. [176.251.72.226]) by mx.google.com with ESMTPS id ft8sm6892068lab.9.2013.01.22.04.38.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jan 2013 04:38:32 -0800 (PST) Message-ID: <50FE8837.7030206@xen.org> Date: Tue, 22 Jan 2013 12:38:15 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-users@lists.xen.org" , xen-arm@lists.xen.org Subject: [Xen-API] Next Xen Document Day : Monday, Jan 28 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, a quick reminder that the first Xen Document Day of this year is happening next Monday. As usual, more info on document days at http://wiki.xen.org/wiki/Xen_Document_Days TODO LIST ========= Feel free to add stuff to the TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO) or put your name besides an item if you intend to work on it. How do I participate? ===================== - Join us on IRC: freenode channel #xendocs - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! See you on IRC! Best Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 22 12:39:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 12:39:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Txd87-00058B-Ea; Tue, 22 Jan 2013 12:39:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Txd86-00057w-56; Tue, 22 Jan 2013 12:39:06 +0000 Received: from [85.158.143.35:9689] by server-1.bemta-4.messagelabs.com id 86/B0-05635-9688EF05; Tue, 22 Jan 2013 12:39:05 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1358858314!15352931!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9485 invoked from network); 22 Jan 2013 12:38:35 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 12:38:35 -0000 Received: by mail-la0-f41.google.com with SMTP id fo12so1898154lab.0 for ; Tue, 22 Jan 2013 04:38:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=TGgSnCooMzvkaJkjMWCoN9sBxk9Zgu5Ml4Pcg3dkX1U=; b=yC6htQLa2ScSdBsBT/j5rgZ5hAekgQmmOqGRQD5Lp4j9G+3gDJd5MA1PzQ0A0WvJeT P2VX+SHpdYl1TZVZ4YUb41UgnJXGtxr0MQZOTMwZlhmpb2uD7sMmvY3bYJZ87B6bw0Uh GL2lUxyPkJayadfBYFrsaCD4kn1AkTksJ0DGa7NL2cmFA4PGP8EKCirU3FHS9YXOaUGz w9dM14Mmu5Wk6oclr5oVktDShjwHryo9PDBXTaEmUp+X6QTx3aVleH3kr0JV8JzqZQwb nuXSl24KPkOLbpOB1tOLGTdr4/gGU0VxIRJ3KGz3PADY5J/f37Hdi0a+yjjsyX+RlPSU 8qxQ== X-Received: by 10.152.111.72 with SMTP id ig8mr20913647lab.1.1358858313567; Tue, 22 Jan 2013 04:38:33 -0800 (PST) Received: from [172.16.26.11] (b0fb48e2.bb.sky.com. [176.251.72.226]) by mx.google.com with ESMTPS id ft8sm6892068lab.9.2013.01.22.04.38.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jan 2013 04:38:32 -0800 (PST) Message-ID: <50FE8837.7030206@xen.org> Date: Tue, 22 Jan 2013 12:38:15 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-users@lists.xen.org" , xen-arm@lists.xen.org Subject: [Xen-API] Next Xen Document Day : Monday, Jan 28 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, a quick reminder that the first Xen Document Day of this year is happening next Monday. As usual, more info on document days at http://wiki.xen.org/wiki/Xen_Document_Days TODO LIST ========= Feel free to add stuff to the TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO) or put your name besides an item if you intend to work on it. How do I participate? ===================== - Join us on IRC: freenode channel #xendocs - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! See you on IRC! Best Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 22 18:30:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 18:30:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxicH-0007qA-6U; Tue, 22 Jan 2013 18:30:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxhfW-0005bS-3i for xen-api@lists.xen.org; Tue, 22 Jan 2013 17:29:54 +0000 Received: from [85.158.143.99:46396] by server-2.bemta-4.messagelabs.com id 9E/12-03518-19CCEF05; Tue, 22 Jan 2013 17:29:53 +0000 X-Env-Sender: thanos.makatos@citrix.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1358875792!25081696!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3ODA2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9906 invoked from network); 22 Jan 2013 17:29:53 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 17:29:53 -0000 X-IronPort-AV: E=Sophos;i="4.84,515,1355097600"; d="scan'208";a="819813" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Jan 2013 17:29:36 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Tue, 22 Jan 2013 17:29:36 +0000 From: Thanos Makatos To: Ian Campbell Date: Tue, 22 Jan 2013 17:29:35 +0000 Thread-Topic: [Xen-devel] [PATCH 0 of 9 RFC v2] blktap3: Introduce a small subset of blktap3 files Thread-Index: Ac31oMhl4ywjlOILT0+FpiFQ89dCYADJHR0g Message-ID: <4B45B535F7F6BE4CB1C044ED5115CDDE0153A6E316FC@LONPMAILBOX01.citrite.net> References: <1358516375.3279.35.camel@zakaz.uk.xensource.com> <4B45B535F7F6BE4CB1C044ED5115CDDE014131C97251@LONPMAILBOX01.citrite.net> <1358527595.3279.114.camel@zakaz.uk.xensource.com> <4B45B535F7F6BE4CB1C044ED5115CDDE014131C9725E@LONPMAILBOX01.citrite.net> <1358528493.3279.116.camel@zakaz.uk.xensource.com> <4B45B535F7F6BE4CB1C044ED5115CDDE014131C97267@LONPMAILBOX01.citrite.net> <1358529916.3279.129.camel@zakaz.uk.xensource.com> In-Reply-To: <1358529916.3279.129.camel@zakaz.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 22 Jan 2013 18:30:36 +0000 Cc: "xen-devel@lists.xensource.com" , Keith Petley , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] [PATCH 0 of 9 RFC v2] blktap3: Introduce a small subset of blktap3 files X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > In fact I'm wondering why the tapback daemon does all the ring setup, > xenbus negotiation anyway. It could just watch "backend/" > and when it sees a new backend/// fork a new > "tapdisk --domain --devid " and have tapdisk take care > of the protocol entirely. Saves a bunch of messaging back and forth I > think. > > I don't have a problem with the existing model, it just strikes me as a > bit odd (but then I don't really know the architecture) > > Ian. I'm not aware of any particular reason for this design option. However, this may turn out to be more interesting/complicated -- I'm including xen-api. In the existing blktap3 prototype, when libxl starts a domain it also spawns the tapdisk. When tapback (formerly known as xenio) detects in XenStore that a front-end wants to connect to the VBD, it needs to locate which tapdisk is designated to serve the corresponding back-end file in order to instruct the tapdisk to connect to the ring. It seems that there is a number of ways for tapback to figure out which tapdisk it must use. I'm not sure whether all these alternatives are possible (please correct me if not), or whether all the necessary information is already written to XenStore. * When libxl spawns the tapdisk, it instructs it to attach to the back-end file. Then, it associates the process ID of the tapdisk with the domain and device Ids (I assume by writing all this to XenStore). When tapback needs to figure out which tapdisk to use, it knows the domain and devices ids so all it has to do is to check XenStore for the corresponding tapdisk. * When libxl spawns the tapdisk, it supplies to it the device and domain ID. It can also tell it which back-end file to use, or write this to XenStore. Tapback can then query all running tapdisk processes and select the one having the specified domain/device ID. It seems that having tapback spawning the tapdisk is simpler, though tapback needs to tell tapdisk which back-end file to use, so it seems that libxl needs to associate the back-end file with the domain and device ids -- I guess this can only be achieved by having libxl writing all this to XenStore. Tapdisk will then take care of running the rest of the XenBus protocol. Which solution is best, given that: * multiple front-ends attached to the same VBD may be desirable * VHD snapshot/coalesce operations need to figure out which tapdisks to pause/refresh * various race conditions should be avoided (?) * other? _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 22 18:30:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 22 Jan 2013 18:30:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxicH-0007qA-6U; Tue, 22 Jan 2013 18:30:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxhfW-0005bS-3i for xen-api@lists.xen.org; Tue, 22 Jan 2013 17:29:54 +0000 Received: from [85.158.143.99:46396] by server-2.bemta-4.messagelabs.com id 9E/12-03518-19CCEF05; Tue, 22 Jan 2013 17:29:53 +0000 X-Env-Sender: thanos.makatos@citrix.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1358875792!25081696!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE3ODA2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9906 invoked from network); 22 Jan 2013 17:29:53 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jan 2013 17:29:53 -0000 X-IronPort-AV: E=Sophos;i="4.84,515,1355097600"; d="scan'208";a="819813" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Jan 2013 17:29:36 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Tue, 22 Jan 2013 17:29:36 +0000 From: Thanos Makatos To: Ian Campbell Date: Tue, 22 Jan 2013 17:29:35 +0000 Thread-Topic: [Xen-devel] [PATCH 0 of 9 RFC v2] blktap3: Introduce a small subset of blktap3 files Thread-Index: Ac31oMhl4ywjlOILT0+FpiFQ89dCYADJHR0g Message-ID: <4B45B535F7F6BE4CB1C044ED5115CDDE0153A6E316FC@LONPMAILBOX01.citrite.net> References: <1358516375.3279.35.camel@zakaz.uk.xensource.com> <4B45B535F7F6BE4CB1C044ED5115CDDE014131C97251@LONPMAILBOX01.citrite.net> <1358527595.3279.114.camel@zakaz.uk.xensource.com> <4B45B535F7F6BE4CB1C044ED5115CDDE014131C9725E@LONPMAILBOX01.citrite.net> <1358528493.3279.116.camel@zakaz.uk.xensource.com> <4B45B535F7F6BE4CB1C044ED5115CDDE014131C97267@LONPMAILBOX01.citrite.net> <1358529916.3279.129.camel@zakaz.uk.xensource.com> In-Reply-To: <1358529916.3279.129.camel@zakaz.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 22 Jan 2013 18:30:36 +0000 Cc: "xen-devel@lists.xensource.com" , Keith Petley , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] [PATCH 0 of 9 RFC v2] blktap3: Introduce a small subset of blktap3 files X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > In fact I'm wondering why the tapback daemon does all the ring setup, > xenbus negotiation anyway. It could just watch "backend/" > and when it sees a new backend/// fork a new > "tapdisk --domain --devid " and have tapdisk take care > of the protocol entirely. Saves a bunch of messaging back and forth I > think. > > I don't have a problem with the existing model, it just strikes me as a > bit odd (but then I don't really know the architecture) > > Ian. I'm not aware of any particular reason for this design option. However, this may turn out to be more interesting/complicated -- I'm including xen-api. In the existing blktap3 prototype, when libxl starts a domain it also spawns the tapdisk. When tapback (formerly known as xenio) detects in XenStore that a front-end wants to connect to the VBD, it needs to locate which tapdisk is designated to serve the corresponding back-end file in order to instruct the tapdisk to connect to the ring. It seems that there is a number of ways for tapback to figure out which tapdisk it must use. I'm not sure whether all these alternatives are possible (please correct me if not), or whether all the necessary information is already written to XenStore. * When libxl spawns the tapdisk, it instructs it to attach to the back-end file. Then, it associates the process ID of the tapdisk with the domain and device Ids (I assume by writing all this to XenStore). When tapback needs to figure out which tapdisk to use, it knows the domain and devices ids so all it has to do is to check XenStore for the corresponding tapdisk. * When libxl spawns the tapdisk, it supplies to it the device and domain ID. It can also tell it which back-end file to use, or write this to XenStore. Tapback can then query all running tapdisk processes and select the one having the specified domain/device ID. It seems that having tapback spawning the tapdisk is simpler, though tapback needs to tell tapdisk which back-end file to use, so it seems that libxl needs to associate the back-end file with the domain and device ids -- I guess this can only be achieved by having libxl writing all this to XenStore. Tapdisk will then take care of running the rest of the XenBus protocol. Which solution is best, given that: * multiple front-ends attached to the same VBD may be desirable * VHD snapshot/coalesce operations need to figure out which tapdisks to pause/refresh * various race conditions should be avoided (?) * other? _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 23 06:12:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 23 Jan 2013 06:12:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxtZe-0004FL-Ud; Wed, 23 Jan 2013 06:12:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxtZe-0004FG-Af for xen-api@lists.xen.org; Wed, 23 Jan 2013 06:12:38 +0000 Received: from [85.158.143.35:13830] by server-1.bemta-4.messagelabs.com id 96/F7-05635-55F7FF05; Wed, 23 Jan 2013 06:12:37 +0000 X-Env-Sender: andy@webguyz.net X-Msg-Ref: server-5.tower-21.messagelabs.com!1358921555!5448168!1 X-Originating-IP: [72.249.59.249] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23491 invoked from network); 23 Jan 2013 06:12:36 -0000 Received: from smtp-249-out.webguyz.net (HELO smtp-249-out.webguyz.net) (72.249.59.249) by server-5.tower-21.messagelabs.com with SMTP; 23 Jan 2013 06:12:36 -0000 Received: from MAIL01 [72.249.59.30] by smtp-249-out.webguyz.net with SMTP; Wed, 23 Jan 2013 00:12:28 -0600 Received: from 76.186.43.103 by mail01.webguyz.net (LogSat Software SMTP Server - RC); Wed, 23 Jan 2013 00:12:28 -0600 Message-ID: <50FF7FA0.1010308@webguyz.net> Date: Wed, 23 Jan 2013 00:13:52 -0600 From: andy User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org X-SF-RX-Return-Path: X-SF-HELO-Domain: [10.0.0.55] X-SF-Originating-IP: 76.186.43.103 X-SF-WhiteListedReason: User authenticated with AUTH LOGIN Subject: [Xen-API] Any hotfixes for xcp 1.6 like there are for xenserver 6.1? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Notice a lot of hotfixes for Xenserver, anything avaiablable for XCP 1.6? Where would patches or updates be posted? Thanks! _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 23 06:12:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 23 Jan 2013 06:12:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxtZe-0004FL-Ud; Wed, 23 Jan 2013 06:12:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxtZe-0004FG-Af for xen-api@lists.xen.org; Wed, 23 Jan 2013 06:12:38 +0000 Received: from [85.158.143.35:13830] by server-1.bemta-4.messagelabs.com id 96/F7-05635-55F7FF05; Wed, 23 Jan 2013 06:12:37 +0000 X-Env-Sender: andy@webguyz.net X-Msg-Ref: server-5.tower-21.messagelabs.com!1358921555!5448168!1 X-Originating-IP: [72.249.59.249] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23491 invoked from network); 23 Jan 2013 06:12:36 -0000 Received: from smtp-249-out.webguyz.net (HELO smtp-249-out.webguyz.net) (72.249.59.249) by server-5.tower-21.messagelabs.com with SMTP; 23 Jan 2013 06:12:36 -0000 Received: from MAIL01 [72.249.59.30] by smtp-249-out.webguyz.net with SMTP; Wed, 23 Jan 2013 00:12:28 -0600 Received: from 76.186.43.103 by mail01.webguyz.net (LogSat Software SMTP Server - RC); Wed, 23 Jan 2013 00:12:28 -0600 Message-ID: <50FF7FA0.1010308@webguyz.net> Date: Wed, 23 Jan 2013 00:13:52 -0600 From: andy User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org X-SF-RX-Return-Path: X-SF-HELO-Domain: [10.0.0.55] X-SF-Originating-IP: 76.186.43.103 X-SF-WhiteListedReason: User authenticated with AUTH LOGIN Subject: [Xen-API] Any hotfixes for xcp 1.6 like there are for xenserver 6.1? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Notice a lot of hotfixes for Xenserver, anything avaiablable for XCP 1.6? Where would patches or updates be posted? Thanks! _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 23 10:11:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 23 Jan 2013 10:11:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxxJ4-0002rk-Ig; Wed, 23 Jan 2013 10:11:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxxJ3-0002rb-AJ for xen-api@lists.xen.org; Wed, 23 Jan 2013 10:11:45 +0000 Received: from [85.158.143.35:39860] by server-2.bemta-4.messagelabs.com id FC/5D-03518-067BFF05; Wed, 23 Jan 2013 10:11:44 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1358935903!15476804!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29085 invoked from network); 23 Jan 2013 10:11:43 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 23 Jan 2013 10:11:43 -0000 Received: by mail-la0-f43.google.com with SMTP id ek20so475377lab.2 for ; Wed, 23 Jan 2013 02:11:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=lvctd57E40YdHWp6mx7Lx88H8w1jCyQO0vyhCeYCxKw=; b=Oyj030ubZtI4soGCovZHHKyBuuh4eljUO8sfLBKQ6sqpMynvgY1DaG0raX4rAMX7eJ aP5V0mVs2oJShfSoPEpfMGbvSGvrMVf+n4lPFiwq+CKzUxPNrYUniciYZ6DdOTRspXR9 Lnbg3Ec2a2Q/uVJBWXpBrk2sllf4xeEWh6LIqqyHXBKNcLUETRzs14GJCyZw5L42DxQy zOuJbN0a1NVEkLv/pmxD3ZNa/cbyGo6jPFLctctsX/Qb+kxQsvjYWxOaWuDFASiI2j4f Jg5xPqrWc5603gjFrbHRIDHZSjK2kbLOi9PpFA90R/2/FaBLu25kqZM8k6BkW3kC6Xjo 5Mhg== X-Received: by 10.112.10.3 with SMTP id e3mr509341lbb.33.1358935902771; Wed, 23 Jan 2013 02:11:42 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id o2sm8035731lby.11.2013.01.23.02.11.41 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jan 2013 02:11:42 -0800 (PST) Message-ID: <50FFB75D.7070000@gmail.com> Date: Wed, 23 Jan 2013 14:11:41 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50FF7FA0.1010308@webguyz.net> In-Reply-To: <50FF7FA0.1010308@webguyz.net> Subject: Re: [Xen-API] Any hotfixes for xcp 1.6 like there are for xenserver 6.1? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org QUZBSUssIG5vdCwgc2FtZSBzdHVmZiBhcyB3aXRoIHhjcCAxLjEgYW5kIG90aGVycy4KCkJ1dCBp ZiB5b3UgcmVhZHkgdG8gcmVjb21waWxlIHhhcGkgYnkgeW91cnNlbGYsIHlvdSBjYW4gdXNlIGNv bW1pdHMgaW4gCmJyYW5jaCB0YW1wYS1sY20gYXMgZ3VpZGUgdG8gc2VlIHdoYXQgaGFzIGJlZW4g Zml4ZWQgYW5kIHRha2UgcGFydHMgeW91IApuZWVkLiBPdGhlciBsb3ctbGV2ZWwgc3R1ZmYgKGV4 Y2VwdCBTTSkgeW91IGNhbiBmcmVlbHkgdGFrZSBmcm9tIApYZW5TZXJ2ZXIncyB1cGRhdGVzIChY ZW4gaHlwZXJ2aXNvciwgZG9tMCBrZXJuZWwgYW5kIHNvIG9uKS4KCgoyMy4wMS4yMDEzIDEwOjEz LCBhbmR5INC/0LjRiNC10YI6Cj4gTm90aWNlIGEgbG90IG9mIGhvdGZpeGVzIGZvciBYZW5zZXJ2 ZXIsIGFueXRoaW5nIGF2YWlhYmxhYmxlIGZvciBYQ1AgCj4gMS42PyBXaGVyZSB3b3VsZCBwYXRj aGVzIG9yIHVwZGF0ZXMgYmUgcG9zdGVkPwo+Cj4gVGhhbmtzIQo+Cj4KPgo+IF9fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gWGVuLWFwaSBtYWlsaW5nIGxp c3QKPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPiBodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmlu L21haWxtYW4vbGlzdGluZm8veGVuLWFwaQoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVu Lm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFw aQo= From xen-api-bounces@lists.xen.org Wed Jan 23 10:11:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 23 Jan 2013 10:11:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxxJ4-0002rk-Ig; Wed, 23 Jan 2013 10:11:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TxxJ3-0002rb-AJ for xen-api@lists.xen.org; Wed, 23 Jan 2013 10:11:45 +0000 Received: from [85.158.143.35:39860] by server-2.bemta-4.messagelabs.com id FC/5D-03518-067BFF05; Wed, 23 Jan 2013 10:11:44 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1358935903!15476804!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29085 invoked from network); 23 Jan 2013 10:11:43 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 23 Jan 2013 10:11:43 -0000 Received: by mail-la0-f43.google.com with SMTP id ek20so475377lab.2 for ; Wed, 23 Jan 2013 02:11:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=lvctd57E40YdHWp6mx7Lx88H8w1jCyQO0vyhCeYCxKw=; b=Oyj030ubZtI4soGCovZHHKyBuuh4eljUO8sfLBKQ6sqpMynvgY1DaG0raX4rAMX7eJ aP5V0mVs2oJShfSoPEpfMGbvSGvrMVf+n4lPFiwq+CKzUxPNrYUniciYZ6DdOTRspXR9 Lnbg3Ec2a2Q/uVJBWXpBrk2sllf4xeEWh6LIqqyHXBKNcLUETRzs14GJCyZw5L42DxQy zOuJbN0a1NVEkLv/pmxD3ZNa/cbyGo6jPFLctctsX/Qb+kxQsvjYWxOaWuDFASiI2j4f Jg5xPqrWc5603gjFrbHRIDHZSjK2kbLOi9PpFA90R/2/FaBLu25kqZM8k6BkW3kC6Xjo 5Mhg== X-Received: by 10.112.10.3 with SMTP id e3mr509341lbb.33.1358935902771; Wed, 23 Jan 2013 02:11:42 -0800 (PST) Received: from [10.13.77.221] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id o2sm8035731lby.11.2013.01.23.02.11.41 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jan 2013 02:11:42 -0800 (PST) Message-ID: <50FFB75D.7070000@gmail.com> Date: Wed, 23 Jan 2013 14:11:41 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <50FF7FA0.1010308@webguyz.net> In-Reply-To: <50FF7FA0.1010308@webguyz.net> Subject: Re: [Xen-API] Any hotfixes for xcp 1.6 like there are for xenserver 6.1? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org QUZBSUssIG5vdCwgc2FtZSBzdHVmZiBhcyB3aXRoIHhjcCAxLjEgYW5kIG90aGVycy4KCkJ1dCBp ZiB5b3UgcmVhZHkgdG8gcmVjb21waWxlIHhhcGkgYnkgeW91cnNlbGYsIHlvdSBjYW4gdXNlIGNv bW1pdHMgaW4gCmJyYW5jaCB0YW1wYS1sY20gYXMgZ3VpZGUgdG8gc2VlIHdoYXQgaGFzIGJlZW4g Zml4ZWQgYW5kIHRha2UgcGFydHMgeW91IApuZWVkLiBPdGhlciBsb3ctbGV2ZWwgc3R1ZmYgKGV4 Y2VwdCBTTSkgeW91IGNhbiBmcmVlbHkgdGFrZSBmcm9tIApYZW5TZXJ2ZXIncyB1cGRhdGVzIChY ZW4gaHlwZXJ2aXNvciwgZG9tMCBrZXJuZWwgYW5kIHNvIG9uKS4KCgoyMy4wMS4yMDEzIDEwOjEz LCBhbmR5INC/0LjRiNC10YI6Cj4gTm90aWNlIGEgbG90IG9mIGhvdGZpeGVzIGZvciBYZW5zZXJ2 ZXIsIGFueXRoaW5nIGF2YWlhYmxhYmxlIGZvciBYQ1AgCj4gMS42PyBXaGVyZSB3b3VsZCBwYXRj aGVzIG9yIHVwZGF0ZXMgYmUgcG9zdGVkPwo+Cj4gVGhhbmtzIQo+Cj4KPgo+IF9fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gWGVuLWFwaSBtYWlsaW5nIGxp c3QKPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmcKPiBodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmlu L21haWxtYW4vbGlzdGluZm8veGVuLWFwaQoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVu Lm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFw aQo= From xen-api-bounces@lists.xen.org Thu Jan 24 05:25:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 05:25:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyFJB-0004mz-V1; Thu, 24 Jan 2013 05:25:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyFJA-0004mu-IH for Xen-api@lists.xen.org; Thu, 24 Jan 2013 05:25:04 +0000 Received: from [85.158.139.211:60524] by server-15.bemta-5.messagelabs.com id 78/D1-12730-FA5C0015; Thu, 24 Jan 2013 05:25:03 +0000 X-Env-Sender: jilingshu@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1359005102!19415998!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32680 invoked from network); 24 Jan 2013 05:25:02 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 05:25:02 -0000 Received: by mail-la0-f44.google.com with SMTP id eb20so8557704lab.3 for ; Wed, 23 Jan 2013 21:25:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=fyV3PqYtxajhwvgjyqksl9c2rSu0vYaYBoXvlX8uvBI=; b=xXuYj9fc0F81HumQfSYbnS5dh5RSnOssgckJjaQcN7XVPJ9G5Y+a3x1YDBXgNcWGcR YypGQFrBthSSFoyKwCW3ZmA9Kp8deFc2Q7a8ZswEz1uLG3Nfob72G3aLR0L5fN//IxUL R/6Nf6/PQy8nbqhMEH8pH7XrRzqOt+0bAnuLHlyx6LYIWNd2ABnAeWfVGvqnT3kvJ92f RLbbNFTkYqpyldcT2shI50zmhx7qbqu3uR1DdXlntdxrVL8uxFG6QDRXbV/m3/njaqHD BK9foStbCaTA9bCgKzlFEFk8tVcMlXahr1hxbNxmAy09W7HGg/OsSUEBNp3oetZW2ZI/ BCjQ== MIME-Version: 1.0 X-Received: by 10.112.10.232 with SMTP id l8mr275054lbb.69.1359005101748; Wed, 23 Jan 2013 21:25:01 -0800 (PST) Received: by 10.112.38.195 with HTTP; Wed, 23 Jan 2013 21:25:01 -0800 (PST) Date: Thu, 24 Jan 2013 13:25:01 +0800 Message-ID: From: Lingfeng Xiong To: Xen-api@lists.xen.org Subject: [Xen-API] =?utf-8?q?Anyway_to_migrate_my_VM_from_=10Xen_xl_to_XCP?= =?utf-8?q?=3F?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5235460642582264929==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5235460642582264929== Content-Type: multipart/alternative; boundary=e0cb4efe338056718104d40208f4 --e0cb4efe338056718104d40208f4 Content-Type: text/plain; charset=UTF-8 Hi all, I am running a Ubuntu Server with Xen 4.1 installed. All VMs are running on that server with one or more virtual disks stored in qcow2 format. These VMs are managed by 'xl' toolstack. One VM is Windows in HVM modes and others are PV VMs. The qcow2 file just contains the root filesystem and has no partition structures. Now I installed a new server with XCP 1.6. I have to migrate all VMs from old server to XCP with all data. Is there anyway to do this? Thanks in advanced! --e0cb4efe338056718104d40208f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all,

I am running a Ubuntu Server with Xen 4.1 installed. All VMs=20 are running on that server with one or more virtual disks stored in=20 qcow2 format. These VMs are managed by 'xl' toolstack. One VM is Wi= ndows in HVM modes and others are PV VMs. The qcow2 file just contains the=20 root filesystem and has no partition structures.

Now I installed a new server with XCP 1.6.=C2=A0 I have to migrate all V= Ms from old server to XCP with all data.

Is there anyway to do this?<= /p>

Thanks in advanced!


--e0cb4efe338056718104d40208f4-- --===============5235460642582264929== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5235460642582264929==-- From xen-api-bounces@lists.xen.org Thu Jan 24 05:25:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 05:25:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyFJB-0004mz-V1; Thu, 24 Jan 2013 05:25:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyFJA-0004mu-IH for Xen-api@lists.xen.org; Thu, 24 Jan 2013 05:25:04 +0000 Received: from [85.158.139.211:60524] by server-15.bemta-5.messagelabs.com id 78/D1-12730-FA5C0015; Thu, 24 Jan 2013 05:25:03 +0000 X-Env-Sender: jilingshu@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1359005102!19415998!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32680 invoked from network); 24 Jan 2013 05:25:02 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 05:25:02 -0000 Received: by mail-la0-f44.google.com with SMTP id eb20so8557704lab.3 for ; Wed, 23 Jan 2013 21:25:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=fyV3PqYtxajhwvgjyqksl9c2rSu0vYaYBoXvlX8uvBI=; b=xXuYj9fc0F81HumQfSYbnS5dh5RSnOssgckJjaQcN7XVPJ9G5Y+a3x1YDBXgNcWGcR YypGQFrBthSSFoyKwCW3ZmA9Kp8deFc2Q7a8ZswEz1uLG3Nfob72G3aLR0L5fN//IxUL R/6Nf6/PQy8nbqhMEH8pH7XrRzqOt+0bAnuLHlyx6LYIWNd2ABnAeWfVGvqnT3kvJ92f RLbbNFTkYqpyldcT2shI50zmhx7qbqu3uR1DdXlntdxrVL8uxFG6QDRXbV/m3/njaqHD BK9foStbCaTA9bCgKzlFEFk8tVcMlXahr1hxbNxmAy09W7HGg/OsSUEBNp3oetZW2ZI/ BCjQ== MIME-Version: 1.0 X-Received: by 10.112.10.232 with SMTP id l8mr275054lbb.69.1359005101748; Wed, 23 Jan 2013 21:25:01 -0800 (PST) Received: by 10.112.38.195 with HTTP; Wed, 23 Jan 2013 21:25:01 -0800 (PST) Date: Thu, 24 Jan 2013 13:25:01 +0800 Message-ID: From: Lingfeng Xiong To: Xen-api@lists.xen.org Subject: [Xen-API] =?utf-8?q?Anyway_to_migrate_my_VM_from_=10Xen_xl_to_XCP?= =?utf-8?q?=3F?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5235460642582264929==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5235460642582264929== Content-Type: multipart/alternative; boundary=e0cb4efe338056718104d40208f4 --e0cb4efe338056718104d40208f4 Content-Type: text/plain; charset=UTF-8 Hi all, I am running a Ubuntu Server with Xen 4.1 installed. All VMs are running on that server with one or more virtual disks stored in qcow2 format. These VMs are managed by 'xl' toolstack. One VM is Windows in HVM modes and others are PV VMs. The qcow2 file just contains the root filesystem and has no partition structures. Now I installed a new server with XCP 1.6. I have to migrate all VMs from old server to XCP with all data. Is there anyway to do this? Thanks in advanced! --e0cb4efe338056718104d40208f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all,

I am running a Ubuntu Server with Xen 4.1 installed. All VMs=20 are running on that server with one or more virtual disks stored in=20 qcow2 format. These VMs are managed by 'xl' toolstack. One VM is Wi= ndows in HVM modes and others are PV VMs. The qcow2 file just contains the=20 root filesystem and has no partition structures.

Now I installed a new server with XCP 1.6.=C2=A0 I have to migrate all V= Ms from old server to XCP with all data.

Is there anyway to do this?<= /p>

Thanks in advanced!


--e0cb4efe338056718104d40208f4-- --===============5235460642582264929== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5235460642582264929==-- From xen-api-bounces@lists.xen.org Thu Jan 24 08:36:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 08:36:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyIHx-0006w6-U8; Thu, 24 Jan 2013 08:36:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ty8Kb-00052t-4W; Wed, 23 Jan 2013 21:58:05 +0000 Received: from [193.109.254.147:12052] by server-10.bemta-14.messagelabs.com id 78/5C-01191-CEC50015; Wed, 23 Jan 2013 21:58:04 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1358978281!8832098!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTc5MDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24066 invoked from network); 23 Jan 2013 21:58:03 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 23 Jan 2013 21:58:03 -0000 X-IronPort-AV: E=Sophos;i="4.84,523,1355097600"; d="scan'208";a="4597504" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 23 Jan 2013 21:58:00 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Wed, 23 Jan 2013 16:57:59 -0500 Message-ID: <51005CF8.402@citrix.com> Date: Wed, 23 Jan 2013 21:58:16 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> In-Reply-To: <1358770844.3279.194.camel@zakaz.uk.xensource.com> X-Originating-IP: [10.80.2.133] X-Mailman-Approved-At: Thu, 24 Jan 2013 08:36:01 +0000 Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, On 21/01/13 12:20, Ian Campbell wrote: > On Mon, 2013-01-21 at 11:31 +0000, Dave Scott wrote: >> Is the current xenstore protocol considered sufficient to >> support reconnecting a frontend to a new backend? I did a few >> simple experiments with an XCP driver domain prototype a while >> back and I failed to make the frontend happy -- usually it would >> become confused about the backend and become stuck. This might >> just be because I didn't know what I was doing :-) > > I think the protocol is probably sufficient but the implementations of > that protocol are not... What kind of problems do you think about? >> Zoltan (cc:d) also did a few simple experiments to see whether >> we could re-use the existing suspend/resume infrastructure, >> similar to the 'fast' resume we already use for live checkpoint. >> As an experiment he modified libxc's xc_resume.c to allow the >> guest's HYPERVISOR_suspend hypercall invocation to return with >> '0' (success) rather than '1' (cancelled). The effect of this >> was to leave the domain running, but since it thinks it has just >> resumed in another domain, it explicitly reconnects its frontends. >> With this change and one or two others (like fixing the >> start_info->{store_,console.domU}.mfns) he made it work for a >> number of oldish guests. I'm sure he can describe the changes >> needed more accurately than I can! > > Would be interesting to know, especially if everything was achieved with > toolstack side changes only! Actually I've used the xc_domain_resume_any() function from libxc to resume the guests. It worked with PV guests, however with some hacks in the hypervisor to silently discarding the error condicions, and not returning from the hypercall with an error. The two guests I've used, and their problems with the hypercall return values: - SLES 11 SP1 (2.6.32.12) crashes because VCPUOP_register_vcpu_info hypercall returns EINVAL, as ( v->arch.vcpu_info_mfn != INVALID_MFN ) - Debian Squeeze 6.0 (2.6.32-5) crashes because EVTCHNOP_bind_virq returns EEXISTS, as ( v->virq_to_evtchnvirq != 0 ) - (these hypercalls were made right after guest comes back from the suspend hypercall) I suppose there will be similar problems with other PV guests, I intend to test other ones as well. My current problem is to architect a proper solution instead of my hacks in the hypervisor. I think we can't access those data areas outside the hypervisor (v is a "struct vcpu" equals current->domain->vcpu[vcpuid]), and unfortunately as I see Xen forgets the fact that the domain was suspended by the time these hypercalls comes. Windows however seems to be less problematic, I've tested Windows 7 with XenServer 6.1 PV drivers, and it worked seamlessly. That driver doesn't care about the suspend hypercall return value, it just do a full close-open cycle. It worked with the fast/cooperative way, obviously. >> What do you think of this approach? Since it's based on the >> existing suspend/resume code it should hopefully work with all >> guest types without having to update the frontends or hopefully even >> fix bugs in them (because it looks just like a regular resume which >> is pretty well tested everywhere). This is particularly important in >> "cloud" scenarios because the people running clouds have usually >> little or no control over the software their customers are running. >> Unfortunately if we have to wait for a PV frontend change to trickle >> into all the common distros it will be a while before we can fully >> benefit from driver domain restart. If there is a better way >> of doing this in the long term involving a frontend change, what >> do you think about this as a stopgap until the frontends are updated? > > I think it could undoubtedly serve well as a stop gap. > > Longer term I guess it depends on the shortcomings of this approach > whether we also want to do something more advanced in the PV drivers > upstream and have them trickle through. The main downsides I suppose is > the brief outage due to the proto-suspend plus the requirement to > reconnect all devices and not just the failed one? I think the current solution to reuse the suspend/resume is quite viable, however it has the mentioned drawbacks, the extra failure points of doing the suspend hypercall and reinit all the frontend devices, not just the affected ones. In the long term I think we should implement this as an extra feature, which could be controlled through xenstore. I already has a prototype version for Linux netfront, but it works through sysfs. It calls the same suspend resume callbacks, but only for the affected devices. > I expect the outage due to the proto-suspend is dwarfed by the outage > caused by a backend going away for however long it takes to notice, > rebuild, reset the hardware, etc etc. Indeed, probably the backend restoration would take at least 5 seconds. Compared to that, the suspend-resume and the frontend device reinit is much shorter. Probably in storage driver domains it's better to suspend the guest immediately when the backend is gone, as the guest can easily crash if the block device is inaccessible for a long time. In case of network access, this isn't such a big problem. Regards, Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 08:36:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 08:36:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyIHx-0006w6-U8; Thu, 24 Jan 2013 08:36:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ty8Kb-00052t-4W; Wed, 23 Jan 2013 21:58:05 +0000 Received: from [193.109.254.147:12052] by server-10.bemta-14.messagelabs.com id 78/5C-01191-CEC50015; Wed, 23 Jan 2013 21:58:04 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1358978281!8832098!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTc5MDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24066 invoked from network); 23 Jan 2013 21:58:03 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 23 Jan 2013 21:58:03 -0000 X-IronPort-AV: E=Sophos;i="4.84,523,1355097600"; d="scan'208";a="4597504" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 23 Jan 2013 21:58:00 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Wed, 23 Jan 2013 16:57:59 -0500 Message-ID: <51005CF8.402@citrix.com> Date: Wed, 23 Jan 2013 21:58:16 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> In-Reply-To: <1358770844.3279.194.camel@zakaz.uk.xensource.com> X-Originating-IP: [10.80.2.133] X-Mailman-Approved-At: Thu, 24 Jan 2013 08:36:01 +0000 Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, On 21/01/13 12:20, Ian Campbell wrote: > On Mon, 2013-01-21 at 11:31 +0000, Dave Scott wrote: >> Is the current xenstore protocol considered sufficient to >> support reconnecting a frontend to a new backend? I did a few >> simple experiments with an XCP driver domain prototype a while >> back and I failed to make the frontend happy -- usually it would >> become confused about the backend and become stuck. This might >> just be because I didn't know what I was doing :-) > > I think the protocol is probably sufficient but the implementations of > that protocol are not... What kind of problems do you think about? >> Zoltan (cc:d) also did a few simple experiments to see whether >> we could re-use the existing suspend/resume infrastructure, >> similar to the 'fast' resume we already use for live checkpoint. >> As an experiment he modified libxc's xc_resume.c to allow the >> guest's HYPERVISOR_suspend hypercall invocation to return with >> '0' (success) rather than '1' (cancelled). The effect of this >> was to leave the domain running, but since it thinks it has just >> resumed in another domain, it explicitly reconnects its frontends. >> With this change and one or two others (like fixing the >> start_info->{store_,console.domU}.mfns) he made it work for a >> number of oldish guests. I'm sure he can describe the changes >> needed more accurately than I can! > > Would be interesting to know, especially if everything was achieved with > toolstack side changes only! Actually I've used the xc_domain_resume_any() function from libxc to resume the guests. It worked with PV guests, however with some hacks in the hypervisor to silently discarding the error condicions, and not returning from the hypercall with an error. The two guests I've used, and their problems with the hypercall return values: - SLES 11 SP1 (2.6.32.12) crashes because VCPUOP_register_vcpu_info hypercall returns EINVAL, as ( v->arch.vcpu_info_mfn != INVALID_MFN ) - Debian Squeeze 6.0 (2.6.32-5) crashes because EVTCHNOP_bind_virq returns EEXISTS, as ( v->virq_to_evtchnvirq != 0 ) - (these hypercalls were made right after guest comes back from the suspend hypercall) I suppose there will be similar problems with other PV guests, I intend to test other ones as well. My current problem is to architect a proper solution instead of my hacks in the hypervisor. I think we can't access those data areas outside the hypervisor (v is a "struct vcpu" equals current->domain->vcpu[vcpuid]), and unfortunately as I see Xen forgets the fact that the domain was suspended by the time these hypercalls comes. Windows however seems to be less problematic, I've tested Windows 7 with XenServer 6.1 PV drivers, and it worked seamlessly. That driver doesn't care about the suspend hypercall return value, it just do a full close-open cycle. It worked with the fast/cooperative way, obviously. >> What do you think of this approach? Since it's based on the >> existing suspend/resume code it should hopefully work with all >> guest types without having to update the frontends or hopefully even >> fix bugs in them (because it looks just like a regular resume which >> is pretty well tested everywhere). This is particularly important in >> "cloud" scenarios because the people running clouds have usually >> little or no control over the software their customers are running. >> Unfortunately if we have to wait for a PV frontend change to trickle >> into all the common distros it will be a while before we can fully >> benefit from driver domain restart. If there is a better way >> of doing this in the long term involving a frontend change, what >> do you think about this as a stopgap until the frontends are updated? > > I think it could undoubtedly serve well as a stop gap. > > Longer term I guess it depends on the shortcomings of this approach > whether we also want to do something more advanced in the PV drivers > upstream and have them trickle through. The main downsides I suppose is > the brief outage due to the proto-suspend plus the requirement to > reconnect all devices and not just the failed one? I think the current solution to reuse the suspend/resume is quite viable, however it has the mentioned drawbacks, the extra failure points of doing the suspend hypercall and reinit all the frontend devices, not just the affected ones. In the long term I think we should implement this as an extra feature, which could be controlled through xenstore. I already has a prototype version for Linux netfront, but it works through sysfs. It calls the same suspend resume callbacks, but only for the affected devices. > I expect the outage due to the proto-suspend is dwarfed by the outage > caused by a backend going away for however long it takes to notice, > rebuild, reset the hardware, etc etc. Indeed, probably the backend restoration would take at least 5 seconds. Compared to that, the suspend-resume and the frontend device reinit is much shorter. Probably in storage driver domains it's better to suspend the guest immediately when the backend is gone, as the guest can easily crash if the block device is inaccessible for a long time. In case of network access, this isn't such a big problem. Regards, Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 10:01:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 10:01:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyJco-0000FU-SJ; Thu, 24 Jan 2013 10:01:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyJcn-0000FH-Ux; Thu, 24 Jan 2013 10:01:38 +0000 Received: from [85.158.143.35:13231] by server-1.bemta-4.messagelabs.com id DC/DA-05635-18601015; Thu, 24 Jan 2013 10:01:37 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1359021590!4690159!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28240 invoked from network); 24 Jan 2013 09:59:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 09:59:52 -0000 X-IronPort-AV: E=Sophos;i="4.84,528,1355097600"; d="scan'208";a="859209" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 09:59:46 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Thu, 24 Jan 2013 09:59:46 +0000 Message-ID: <1359021585.17440.93.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Zoltan Kiss Date: Thu, 24 Jan 2013 09:59:45 +0000 In-Reply-To: <51005CF8.402@citrix.com> References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Wed, 2013-01-23 at 21:58 +0000, Zoltan Kiss wrote: > Hi, > > On 21/01/13 12:20, Ian Campbell wrote: > > On Mon, 2013-01-21 at 11:31 +0000, Dave Scott wrote: > >> Is the current xenstore protocol considered sufficient to > >> support reconnecting a frontend to a new backend? I did a few > >> simple experiments with an XCP driver domain prototype a while > >> back and I failed to make the frontend happy -- usually it would > >> become confused about the backend and become stuck. This might > >> just be because I didn't know what I was doing :-) > > > > I think the protocol is probably sufficient but the implementations of > > that protocol are not... > What kind of problems do you think about? Just lack of testing of the code paths in that way, my gut feeling is that there will inevitably be frontends which can't cope, but maybe I'm pessimistic. > >> Zoltan (cc:d) also did a few simple experiments to see whether > >> we could re-use the existing suspend/resume infrastructure, > >> similar to the 'fast' resume we already use for live checkpoint. > >> As an experiment he modified libxc's xc_resume.c to allow the > >> guest's HYPERVISOR_suspend hypercall invocation to return with > >> '0' (success) rather than '1' (cancelled). The effect of this > >> was to leave the domain running, but since it thinks it has just > >> resumed in another domain, it explicitly reconnects its frontends. > >> With this change and one or two others (like fixing the > >> start_info->{store_,console.domU}.mfns) he made it work for a > >> number of oldish guests. I'm sure he can describe the changes > >> needed more accurately than I can! > > > > Would be interesting to know, especially if everything was achieved with > > toolstack side changes only! > Actually I've used the xc_domain_resume_any() function from libxc to > resume the guests. It worked with PV guests, however with some hacks in > the hypervisor to silently discarding the error condicions, and not > returning from the hypercall with an error. The two guests I've used, > and their problems with the hypercall return values: > > - SLES 11 SP1 (2.6.32.12) crashes because VCPUOP_register_vcpu_info > hypercall returns EINVAL, as ( v->arch.vcpu_info_mfn != INVALID_MFN ) > - Debian Squeeze 6.0 (2.6.32-5) crashes because EVTCHNOP_bind_virq > returns EEXISTS, as ( v->virq_to_evtchnvirq != 0 ) > - (these hypercalls were made right after guest comes back from the > suspend hypercall) The toolstack might need to do EVTCHNOP_reset or do some other cleanup? One difference between a cancelled suspend (i.e. resuming in the old domain) and a normal/successful one is that in the normal case you are starting in a fresh domain, so things like evtchns are all unbound and must be redone whereas in the cancelled case some of the old state can persist and needs to be reset. xend has some code which might form a useful basis of a list of things which may need resetting, see tools/python/xen/xend/XendDomainInfo.py resumeDomain. > I suppose there will be similar problems with other PV guests, I intend > to test other ones as well. My current problem is to architect a proper > solution instead of my hacks in the hypervisor. I think we can't access > those data areas outside the hypervisor (v is a "struct vcpu" equals > current->domain->vcpu[vcpuid]), and unfortunately as I see Xen forgets > the fact that the domain was suspended by the time these hypercalls comes. Xen isn't generally aware of things like suspend, it just sees a domain/vcpu getting torn down and new ones (unrelated as far as Xen knows) being created. > Probably in storage driver domains it's better to suspend the guest > immediately when the backend is gone, as the guest can easily crash if > the block device is inaccessible for a long time. In case of network > access, this isn't such a big problem. Pausing guests when one of their supporting driver domains goes away does seem like a good idea. I suppose the flip side is that a domain which isn't using a disk which goes away briefly would see a hiccup it wouldn't have otherwise seen. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 10:01:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 10:01:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyJco-0000FU-SJ; Thu, 24 Jan 2013 10:01:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyJcn-0000FH-Ux; Thu, 24 Jan 2013 10:01:38 +0000 Received: from [85.158.143.35:13231] by server-1.bemta-4.messagelabs.com id DC/DA-05635-18601015; Thu, 24 Jan 2013 10:01:37 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1359021590!4690159!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28240 invoked from network); 24 Jan 2013 09:59:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 09:59:52 -0000 X-IronPort-AV: E=Sophos;i="4.84,528,1355097600"; d="scan'208";a="859209" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 09:59:46 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Thu, 24 Jan 2013 09:59:46 +0000 Message-ID: <1359021585.17440.93.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Zoltan Kiss Date: Thu, 24 Jan 2013 09:59:45 +0000 In-Reply-To: <51005CF8.402@citrix.com> References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Wed, 2013-01-23 at 21:58 +0000, Zoltan Kiss wrote: > Hi, > > On 21/01/13 12:20, Ian Campbell wrote: > > On Mon, 2013-01-21 at 11:31 +0000, Dave Scott wrote: > >> Is the current xenstore protocol considered sufficient to > >> support reconnecting a frontend to a new backend? I did a few > >> simple experiments with an XCP driver domain prototype a while > >> back and I failed to make the frontend happy -- usually it would > >> become confused about the backend and become stuck. This might > >> just be because I didn't know what I was doing :-) > > > > I think the protocol is probably sufficient but the implementations of > > that protocol are not... > What kind of problems do you think about? Just lack of testing of the code paths in that way, my gut feeling is that there will inevitably be frontends which can't cope, but maybe I'm pessimistic. > >> Zoltan (cc:d) also did a few simple experiments to see whether > >> we could re-use the existing suspend/resume infrastructure, > >> similar to the 'fast' resume we already use for live checkpoint. > >> As an experiment he modified libxc's xc_resume.c to allow the > >> guest's HYPERVISOR_suspend hypercall invocation to return with > >> '0' (success) rather than '1' (cancelled). The effect of this > >> was to leave the domain running, but since it thinks it has just > >> resumed in another domain, it explicitly reconnects its frontends. > >> With this change and one or two others (like fixing the > >> start_info->{store_,console.domU}.mfns) he made it work for a > >> number of oldish guests. I'm sure he can describe the changes > >> needed more accurately than I can! > > > > Would be interesting to know, especially if everything was achieved with > > toolstack side changes only! > Actually I've used the xc_domain_resume_any() function from libxc to > resume the guests. It worked with PV guests, however with some hacks in > the hypervisor to silently discarding the error condicions, and not > returning from the hypercall with an error. The two guests I've used, > and their problems with the hypercall return values: > > - SLES 11 SP1 (2.6.32.12) crashes because VCPUOP_register_vcpu_info > hypercall returns EINVAL, as ( v->arch.vcpu_info_mfn != INVALID_MFN ) > - Debian Squeeze 6.0 (2.6.32-5) crashes because EVTCHNOP_bind_virq > returns EEXISTS, as ( v->virq_to_evtchnvirq != 0 ) > - (these hypercalls were made right after guest comes back from the > suspend hypercall) The toolstack might need to do EVTCHNOP_reset or do some other cleanup? One difference between a cancelled suspend (i.e. resuming in the old domain) and a normal/successful one is that in the normal case you are starting in a fresh domain, so things like evtchns are all unbound and must be redone whereas in the cancelled case some of the old state can persist and needs to be reset. xend has some code which might form a useful basis of a list of things which may need resetting, see tools/python/xen/xend/XendDomainInfo.py resumeDomain. > I suppose there will be similar problems with other PV guests, I intend > to test other ones as well. My current problem is to architect a proper > solution instead of my hacks in the hypervisor. I think we can't access > those data areas outside the hypervisor (v is a "struct vcpu" equals > current->domain->vcpu[vcpuid]), and unfortunately as I see Xen forgets > the fact that the domain was suspended by the time these hypercalls comes. Xen isn't generally aware of things like suspend, it just sees a domain/vcpu getting torn down and new ones (unrelated as far as Xen knows) being created. > Probably in storage driver domains it's better to suspend the guest > immediately when the backend is gone, as the guest can easily crash if > the block device is inaccessible for a long time. In case of network > access, this isn't such a big problem. Pausing guests when one of their supporting driver domains goes away does seem like a good idea. I suppose the flip side is that a domain which isn't using a disk which goes away briefly would see a hiccup it wouldn't have otherwise seen. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 11:46:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 11:46:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyLFr-0003tJ-DT; Thu, 24 Jan 2013 11:46:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyLFq-0003t9-4m; Thu, 24 Jan 2013 11:46:02 +0000 Received: from [85.158.137.99:57507] by server-15.bemta-3.messagelabs.com id 41/F4-25008-9FE11015; Thu, 24 Jan 2013 11:46:01 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1359027959!15181706!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14411 invoked from network); 24 Jan 2013 11:46:00 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 11:46:00 -0000 Received: by mail-la0-f44.google.com with SMTP id eb20so8889217lab.3 for ; Thu, 24 Jan 2013 03:45:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bNwQYEfwm01ftvn4CPfczQwuLUCYf/Mjti+CC4cReYk=; b=UODJi/5Fb9jjf8fpRhU0Gs9hc95McG8SixW/y5MckBqkWnHOZGtQP44Lwq1uO0Ehaw 5XYyqbYJC5/7pEKRecAfe3pSrBSD7ZVaPMiN8B4Fxz3buacVIukyuXsZjPLONuwQjiOF fhBrRqofABZ1rPmaPnYDOf5QGxHiLdSMBwEciuBgfrSbIm1oHFfoTVKPn6cfxgZkELxl z2v1n3KKMZjQ4KaX/X4Yy0BfXMfhwsBimakg6MdcD3Opj50nvv+rKvnXfheDYI+9711Z Lu7hmrFB7k4gmK21qn0h48UqQtkNwGpEXQxQ7iv3mpL5yyeQH4xv9tl0UDY9ASavxHjD wgvw== X-Received: by 10.112.54.1 with SMTP id f1mr667638lbp.85.1359027959417; Thu, 24 Jan 2013 03:45:59 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id to7sm9520459lab.13.2013.01.24.03.45.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Jan 2013 03:45:58 -0800 (PST) Message-ID: <51011EF5.9080708@gmail.com> Date: Thu, 24 Jan 2013 15:45:57 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Zoltan Kiss References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> In-Reply-To: <51005CF8.402@citrix.com> Cc: "'xen-devel@lists.xen.org'" , Ian Campbell , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org >> I expect the outage due to the proto-suspend is dwarfed by the outage >> caused by a backend going away for however long it takes to notice, >> rebuild, reset the hardware, etc etc. > Indeed, probably the backend restoration would take at least 5 > seconds. Compared to that, the suspend-resume and the frontend device > reinit is much shorter. > Probably in storage driver domains it's better to suspend the guest > immediately when the backend is gone, as the guest can easily crash if > the block device is inaccessible for a long time. In case of network > access, this isn't such a big problem. > > Some notes about guest suspend during IO. I tested that way for storage reboot (pause all domains, reboot ISCSI storage and resume every domain). If pause is short (less that 2 minutes), guest can survive. If pause is longer than 2 minutes, guests in state of waiting for io completion, detects IO timeout after resuming and cause IO error on virtual block devices. (PV). _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 11:46:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 11:46:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyLFr-0003tJ-DT; Thu, 24 Jan 2013 11:46:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyLFq-0003t9-4m; Thu, 24 Jan 2013 11:46:02 +0000 Received: from [85.158.137.99:57507] by server-15.bemta-3.messagelabs.com id 41/F4-25008-9FE11015; Thu, 24 Jan 2013 11:46:01 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1359027959!15181706!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14411 invoked from network); 24 Jan 2013 11:46:00 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 11:46:00 -0000 Received: by mail-la0-f44.google.com with SMTP id eb20so8889217lab.3 for ; Thu, 24 Jan 2013 03:45:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bNwQYEfwm01ftvn4CPfczQwuLUCYf/Mjti+CC4cReYk=; b=UODJi/5Fb9jjf8fpRhU0Gs9hc95McG8SixW/y5MckBqkWnHOZGtQP44Lwq1uO0Ehaw 5XYyqbYJC5/7pEKRecAfe3pSrBSD7ZVaPMiN8B4Fxz3buacVIukyuXsZjPLONuwQjiOF fhBrRqofABZ1rPmaPnYDOf5QGxHiLdSMBwEciuBgfrSbIm1oHFfoTVKPn6cfxgZkELxl z2v1n3KKMZjQ4KaX/X4Yy0BfXMfhwsBimakg6MdcD3Opj50nvv+rKvnXfheDYI+9711Z Lu7hmrFB7k4gmK21qn0h48UqQtkNwGpEXQxQ7iv3mpL5yyeQH4xv9tl0UDY9ASavxHjD wgvw== X-Received: by 10.112.54.1 with SMTP id f1mr667638lbp.85.1359027959417; Thu, 24 Jan 2013 03:45:59 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id to7sm9520459lab.13.2013.01.24.03.45.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Jan 2013 03:45:58 -0800 (PST) Message-ID: <51011EF5.9080708@gmail.com> Date: Thu, 24 Jan 2013 15:45:57 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Zoltan Kiss References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> In-Reply-To: <51005CF8.402@citrix.com> Cc: "'xen-devel@lists.xen.org'" , Ian Campbell , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org >> I expect the outage due to the proto-suspend is dwarfed by the outage >> caused by a backend going away for however long it takes to notice, >> rebuild, reset the hardware, etc etc. > Indeed, probably the backend restoration would take at least 5 > seconds. Compared to that, the suspend-resume and the frontend device > reinit is much shorter. > Probably in storage driver domains it's better to suspend the guest > immediately when the backend is gone, as the guest can easily crash if > the block device is inaccessible for a long time. In case of network > access, this isn't such a big problem. > > Some notes about guest suspend during IO. I tested that way for storage reboot (pause all domains, reboot ISCSI storage and resume every domain). If pause is short (less that 2 minutes), guest can survive. If pause is longer than 2 minutes, guests in state of waiting for io completion, detects IO timeout after resuming and cause IO error on virtual block devices. (PV). _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 12:57:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 12:57:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyMMf-0007IF-Sv; Thu, 24 Jan 2013 12:57:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyMMe-0007I4-B2; Thu, 24 Jan 2013 12:57:08 +0000 Received: from [85.158.139.83:55246] by server-12.bemta-5.messagelabs.com id 1E/AF-31102-3AF21015; Thu, 24 Jan 2013 12:57:07 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1359032225!23460063!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTY4ODk=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24608 invoked from network); 24 Jan 2013 12:57:06 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 12:57:06 -0000 X-IronPort-AV: E=Sophos;i="4.84,529,1355097600"; d="scan'208";a="4914133" Received: from unknown (HELO FTLPEX01CL03.citrite.net) ([10.13.107.80]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 12:57:04 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 07:57:03 -0500 Message-ID: <51012FB4.2060408@citrix.com> Date: Thu, 24 Jan 2013 12:57:24 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> In-Reply-To: <51011EF5.9080708@gmail.com> X-Originating-IP: [10.80.2.133] Cc: "'xen-devel@lists.xen.org'" , Ian Campbell , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/01/13 11:45, George Shuklin wrote: > >>> I expect the outage due to the proto-suspend is dwarfed by the outage >>> caused by a backend going away for however long it takes to notice, >>> rebuild, reset the hardware, etc etc. >> Indeed, probably the backend restoration would take at least 5 >> seconds. Compared to that, the suspend-resume and the frontend device >> reinit is much shorter. >> Probably in storage driver domains it's better to suspend the guest >> immediately when the backend is gone, as the guest can easily crash if >> the block device is inaccessible for a long time. In case of network >> access, this isn't such a big problem. >> >> > Some notes about guest suspend during IO. > > I tested that way for storage reboot (pause all domains, reboot ISCSI > storage and resume every domain). If pause is short (less that 2 > minutes), guest can survive. If pause is longer than 2 minutes, guests > in state of waiting for io completion, detects IO timeout after > resuming and cause IO error on virtual block devices. (PV). Good point! I haven't considered that even if the guest is paused, during coming back it will still notice that timers expired. I think the original idea came from Paul, CCing him to raise awareness about this problem. Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 12:57:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 12:57:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyMMf-0007IF-Sv; Thu, 24 Jan 2013 12:57:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyMMe-0007I4-B2; Thu, 24 Jan 2013 12:57:08 +0000 Received: from [85.158.139.83:55246] by server-12.bemta-5.messagelabs.com id 1E/AF-31102-3AF21015; Thu, 24 Jan 2013 12:57:07 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1359032225!23460063!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTY4ODk=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24608 invoked from network); 24 Jan 2013 12:57:06 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 12:57:06 -0000 X-IronPort-AV: E=Sophos;i="4.84,529,1355097600"; d="scan'208";a="4914133" Received: from unknown (HELO FTLPEX01CL03.citrite.net) ([10.13.107.80]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 12:57:04 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 07:57:03 -0500 Message-ID: <51012FB4.2060408@citrix.com> Date: Thu, 24 Jan 2013 12:57:24 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> In-Reply-To: <51011EF5.9080708@gmail.com> X-Originating-IP: [10.80.2.133] Cc: "'xen-devel@lists.xen.org'" , Ian Campbell , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/01/13 11:45, George Shuklin wrote: > >>> I expect the outage due to the proto-suspend is dwarfed by the outage >>> caused by a backend going away for however long it takes to notice, >>> rebuild, reset the hardware, etc etc. >> Indeed, probably the backend restoration would take at least 5 >> seconds. Compared to that, the suspend-resume and the frontend device >> reinit is much shorter. >> Probably in storage driver domains it's better to suspend the guest >> immediately when the backend is gone, as the guest can easily crash if >> the block device is inaccessible for a long time. In case of network >> access, this isn't such a big problem. >> >> > Some notes about guest suspend during IO. > > I tested that way for storage reboot (pause all domains, reboot ISCSI > storage and resume every domain). If pause is short (less that 2 > minutes), guest can survive. If pause is longer than 2 minutes, guests > in state of waiting for io completion, detects IO timeout after > resuming and cause IO error on virtual block devices. (PV). Good point! I haven't considered that even if the guest is paused, during coming back it will still notice that timers expired. I think the original idea came from Paul, CCing him to raise awareness about this problem. Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 13:26:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 13:26:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyMot-000268-C1; Thu, 24 Jan 2013 13:26:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyMor-00025m-Bn; Thu, 24 Jan 2013 13:26:17 +0000 Received: from [85.158.143.35:57365] by server-3.bemta-4.messagelabs.com id E6/97-10689-87631015; Thu, 24 Jan 2013 13:26:16 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1359033906!14412700!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15306 invoked from network); 24 Jan 2013 13:25:07 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 13:25:07 -0000 X-IronPort-AV: E=Sophos;i="4.84,529,1355097600"; d="scan'208";a="865565" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 13:25:05 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 24 Jan 2013 13:25:05 +0000 From: Paul Durrant To: George Shuklin , Zoltan Kiss Date: Thu, 24 Jan 2013 13:25:36 +0000 Thread-Topic: [Xen-devel] driver domain crash and reconnect handling Thread-Index: Ac36KIppdGGGmErSSe+Pbd3O7jV/uwADZF5Q Message-ID: <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> In-Reply-To: <51011EF5.9080708@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Ian Campbell , "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > -----Original Message----- > From: xen-devel-bounces@lists.xen.org [mailto:xen-devel- > bounces@lists.xen.org] On Behalf Of George Shuklin > Sent: 24 January 2013 11:46 > To: Zoltan Kiss > Cc: 'xen-devel@lists.xen.org'; Dave Scott; Ian Campbell; xen- > api@lists.xen.org > Subject: Re: [Xen-devel] driver domain crash and reconnect handling > > > >> I expect the outage due to the proto-suspend is dwarfed by the outage > >> caused by a backend going away for however long it takes to notice, > >> rebuild, reset the hardware, etc etc. > > Indeed, probably the backend restoration would take at least 5 > > seconds. Compared to that, the suspend-resume and the frontend device > > reinit is much shorter. > > Probably in storage driver domains it's better to suspend the guest > > immediately when the backend is gone, as the guest can easily crash if > > the block device is inaccessible for a long time. In case of network > > access, this isn't such a big problem. > > > > > Some notes about guest suspend during IO. > > I tested that way for storage reboot (pause all domains, reboot ISCSI storage > and resume every domain). If pause is short (less that 2 minutes), guest can > survive. If pause is longer than 2 minutes, guests in state of waiting for io > completion, detects IO timeout after resuming and cause IO error on virtual > block devices. (PV). > To be clear here: do you mean you *paused* and then unpaused the VMs, or *suspended* and then resumed the VMs? I suspect you mean the former. Paul _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 13:26:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 13:26:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyMot-000268-C1; Thu, 24 Jan 2013 13:26:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyMor-00025m-Bn; Thu, 24 Jan 2013 13:26:17 +0000 Received: from [85.158.143.35:57365] by server-3.bemta-4.messagelabs.com id E6/97-10689-87631015; Thu, 24 Jan 2013 13:26:16 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1359033906!14412700!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15306 invoked from network); 24 Jan 2013 13:25:07 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 13:25:07 -0000 X-IronPort-AV: E=Sophos;i="4.84,529,1355097600"; d="scan'208";a="865565" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 13:25:05 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 24 Jan 2013 13:25:05 +0000 From: Paul Durrant To: George Shuklin , Zoltan Kiss Date: Thu, 24 Jan 2013 13:25:36 +0000 Thread-Topic: [Xen-devel] driver domain crash and reconnect handling Thread-Index: Ac36KIppdGGGmErSSe+Pbd3O7jV/uwADZF5Q Message-ID: <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> In-Reply-To: <51011EF5.9080708@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Ian Campbell , "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org > -----Original Message----- > From: xen-devel-bounces@lists.xen.org [mailto:xen-devel- > bounces@lists.xen.org] On Behalf Of George Shuklin > Sent: 24 January 2013 11:46 > To: Zoltan Kiss > Cc: 'xen-devel@lists.xen.org'; Dave Scott; Ian Campbell; xen- > api@lists.xen.org > Subject: Re: [Xen-devel] driver domain crash and reconnect handling > > > >> I expect the outage due to the proto-suspend is dwarfed by the outage > >> caused by a backend going away for however long it takes to notice, > >> rebuild, reset the hardware, etc etc. > > Indeed, probably the backend restoration would take at least 5 > > seconds. Compared to that, the suspend-resume and the frontend device > > reinit is much shorter. > > Probably in storage driver domains it's better to suspend the guest > > immediately when the backend is gone, as the guest can easily crash if > > the block device is inaccessible for a long time. In case of network > > access, this isn't such a big problem. > > > > > Some notes about guest suspend during IO. > > I tested that way for storage reboot (pause all domains, reboot ISCSI storage > and resume every domain). If pause is short (less that 2 minutes), guest can > survive. If pause is longer than 2 minutes, guests in state of waiting for io > completion, detects IO timeout after resuming and cause IO error on virtual > block devices. (PV). > To be clear here: do you mean you *paused* and then unpaused the VMs, or *suspended* and then resumed the VMs? I suspect you mean the former. Paul _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 14:07:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 14:07:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyNSF-0003b4-Cy; Thu, 24 Jan 2013 14:06:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyNSD-0003aw-Ug; Thu, 24 Jan 2013 14:06:58 +0000 Received: from [85.158.143.99:21023] by server-3.bemta-4.messagelabs.com id 2E/D5-10689-10041015; Thu, 24 Jan 2013 14:06:57 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1359036399!28440141!1 X-Originating-IP: [209.85.217.175] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5877 invoked from network); 24 Jan 2013 14:06:40 -0000 Received: from mail-lb0-f175.google.com (HELO mail-lb0-f175.google.com) (209.85.217.175) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 14:06:40 -0000 Received: by mail-lb0-f175.google.com with SMTP id n3so6922247lbo.34 for ; Thu, 24 Jan 2013 06:06:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Pv7Q8FsdeR00gJ9heK2XqaZBgD3hhODRCQESPdsWgk0=; b=m7WLlRCSDsDcVVpl3FMycCq9lHnLB/GoDtd1Yg6CGDbtYHHACWKQxh/Po6bOaS6OOt hkLcZAsGnDfQI11sv2Z7usQq5RxypysuTtbM0LadO2g75Nj2bWsn2paovhR+FAqvKS0f n65eE24ymNiVOryVkMWUJ/vsX0RvQfgfoVazsiOiLVi71FZldV0kDbeE9UBeuTX/LIKP 8Ax6To5wbeEP4IPppAEWH9Vh00nY+BdA8D0PNIfG7r+mjDkBX4x6mbpY1HQZZ+W3Ky06 8jqLbo/KX4S5GOVXCnj/vKLCpmW6qxvnwdXIhR1kbRNb6lCCANByhLTmZUGRBlgHQ72r uCpQ== X-Received: by 10.112.103.196 with SMTP id fy4mr825835lbb.125.1359036399579; Thu, 24 Jan 2013 06:06:39 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:b571:5353:bcc1:a6c8? ([2a00:ab00:0:fffe:b571:5353:bcc1:a6c8]) by mx.google.com with ESMTPS id fj2sm9730788lbb.6.2013.01.24.06.06.38 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Jan 2013 06:06:39 -0800 (PST) Message-ID: <51013FED.60201@gmail.com> Date: Thu, 24 Jan 2013 18:06:37 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: Paul Durrant References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> In-Reply-To: <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> Cc: Ian Campbell , "xen-api@lists.xen.org" , Zoltan Kiss , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MjQuMDEuMjAxMyAxNzoyNSwgUGF1bCBEdXJyYW50INC/0LjRiNC10YI6Cj4+Cj4+IFNvbWUgbm90 ZXMgYWJvdXQgZ3Vlc3Qgc3VzcGVuZCBkdXJpbmcgSU8uCj4+Cj4+IEkgdGVzdGVkIHRoYXQgd2F5 IGZvciBzdG9yYWdlIHJlYm9vdCAocGF1c2UgYWxsIGRvbWFpbnMsIHJlYm9vdCBJU0NTSSBzdG9y YWdlCj4+IGFuZCByZXN1bWUgZXZlcnkgZG9tYWluKS4gSWYgcGF1c2UgaXMgc2hvcnQgKGxlc3Mg dGhhdCAyIG1pbnV0ZXMpLCBndWVzdCBjYW4KPj4gc3Vydml2ZS4gSWYgcGF1c2UgaXMgbG9uZ2Vy IHRoYW4gMiBtaW51dGVzLCBndWVzdHMgaW4gc3RhdGUgb2Ygd2FpdGluZyBmb3IgaW8KPj4gY29t cGxldGlvbiwgZGV0ZWN0cyBJTyB0aW1lb3V0IGFmdGVyIHJlc3VtaW5nICBhbmQgY2F1c2UgSU8g ZXJyb3Igb24gdmlydHVhbAo+PiBibG9jayBkZXZpY2VzLiAoUFYpLgo+Pgo+IFRvIGJlIGNsZWFy IGhlcmU6IGRvIHlvdSBtZWFuIHlvdSAqcGF1c2VkKiBhbmQgdGhlbiB1bnBhdXNlZCB0aGUgVk1z LCBvciAqc3VzcGVuZGVkKiBhbmQgdGhlbiByZXN1bWVkIHRoZSBWTXM/IEkgc3VzcGVjdCB5b3Ug bWVhbiB0aGUgZm9ybWVyLgo+Cj4gICAgUGF1bApQYXVzZSwgb2YgY2F1c2UuIE15IGJhZC4KCl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFp bGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Thu Jan 24 14:07:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 14:07:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyNSF-0003b4-Cy; Thu, 24 Jan 2013 14:06:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyNSD-0003aw-Ug; Thu, 24 Jan 2013 14:06:58 +0000 Received: from [85.158.143.99:21023] by server-3.bemta-4.messagelabs.com id 2E/D5-10689-10041015; Thu, 24 Jan 2013 14:06:57 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1359036399!28440141!1 X-Originating-IP: [209.85.217.175] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5877 invoked from network); 24 Jan 2013 14:06:40 -0000 Received: from mail-lb0-f175.google.com (HELO mail-lb0-f175.google.com) (209.85.217.175) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 14:06:40 -0000 Received: by mail-lb0-f175.google.com with SMTP id n3so6922247lbo.34 for ; Thu, 24 Jan 2013 06:06:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Pv7Q8FsdeR00gJ9heK2XqaZBgD3hhODRCQESPdsWgk0=; b=m7WLlRCSDsDcVVpl3FMycCq9lHnLB/GoDtd1Yg6CGDbtYHHACWKQxh/Po6bOaS6OOt hkLcZAsGnDfQI11sv2Z7usQq5RxypysuTtbM0LadO2g75Nj2bWsn2paovhR+FAqvKS0f n65eE24ymNiVOryVkMWUJ/vsX0RvQfgfoVazsiOiLVi71FZldV0kDbeE9UBeuTX/LIKP 8Ax6To5wbeEP4IPppAEWH9Vh00nY+BdA8D0PNIfG7r+mjDkBX4x6mbpY1HQZZ+W3Ky06 8jqLbo/KX4S5GOVXCnj/vKLCpmW6qxvnwdXIhR1kbRNb6lCCANByhLTmZUGRBlgHQ72r uCpQ== X-Received: by 10.112.103.196 with SMTP id fy4mr825835lbb.125.1359036399579; Thu, 24 Jan 2013 06:06:39 -0800 (PST) Received: from ?IPv6:2a00:ab00:0:fffe:b571:5353:bcc1:a6c8? ([2a00:ab00:0:fffe:b571:5353:bcc1:a6c8]) by mx.google.com with ESMTPS id fj2sm9730788lbb.6.2013.01.24.06.06.38 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Jan 2013 06:06:39 -0800 (PST) Message-ID: <51013FED.60201@gmail.com> Date: Thu, 24 Jan 2013 18:06:37 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: Paul Durrant References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> In-Reply-To: <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> Cc: Ian Campbell , "xen-api@lists.xen.org" , Zoltan Kiss , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MjQuMDEuMjAxMyAxNzoyNSwgUGF1bCBEdXJyYW50INC/0LjRiNC10YI6Cj4+Cj4+IFNvbWUgbm90 ZXMgYWJvdXQgZ3Vlc3Qgc3VzcGVuZCBkdXJpbmcgSU8uCj4+Cj4+IEkgdGVzdGVkIHRoYXQgd2F5 IGZvciBzdG9yYWdlIHJlYm9vdCAocGF1c2UgYWxsIGRvbWFpbnMsIHJlYm9vdCBJU0NTSSBzdG9y YWdlCj4+IGFuZCByZXN1bWUgZXZlcnkgZG9tYWluKS4gSWYgcGF1c2UgaXMgc2hvcnQgKGxlc3Mg dGhhdCAyIG1pbnV0ZXMpLCBndWVzdCBjYW4KPj4gc3Vydml2ZS4gSWYgcGF1c2UgaXMgbG9uZ2Vy IHRoYW4gMiBtaW51dGVzLCBndWVzdHMgaW4gc3RhdGUgb2Ygd2FpdGluZyBmb3IgaW8KPj4gY29t cGxldGlvbiwgZGV0ZWN0cyBJTyB0aW1lb3V0IGFmdGVyIHJlc3VtaW5nICBhbmQgY2F1c2UgSU8g ZXJyb3Igb24gdmlydHVhbAo+PiBibG9jayBkZXZpY2VzLiAoUFYpLgo+Pgo+IFRvIGJlIGNsZWFy IGhlcmU6IGRvIHlvdSBtZWFuIHlvdSAqcGF1c2VkKiBhbmQgdGhlbiB1bnBhdXNlZCB0aGUgVk1z LCBvciAqc3VzcGVuZGVkKiBhbmQgdGhlbiByZXN1bWVkIHRoZSBWTXM/IEkgc3VzcGVjdCB5b3Ug bWVhbiB0aGUgZm9ybWVyLgo+Cj4gICAgUGF1bApQYXVzZSwgb2YgY2F1c2UuIE15IGJhZC4KCl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1hcGkgbWFp bGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Thu Jan 24 15:02:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 15:02:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyOKC-0004ga-JT; Thu, 24 Jan 2013 15:02:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyOKB-0004gQ-6H; Thu, 24 Jan 2013 15:02:43 +0000 Received: from [193.109.254.147:30911] by server-9.bemta-14.messagelabs.com id E2/2E-17118-21D41015; Thu, 24 Jan 2013 15:02:42 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1359039714!3134542!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTgyMzA=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19533 invoked from network); 24 Jan 2013 15:01:56 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 15:01:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4683111" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 15:01:27 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 10:01:27 -0500 Message-ID: <51014CDC.1030501@citrix.com> Date: Thu, 24 Jan 2013 15:01:48 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> In-Reply-To: <51013FED.60201@gmail.com> X-Originating-IP: [10.80.2.133] Cc: "xen-api@lists.xen.org" , Ian Campbell , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gMjQvMDEvMTMgMTQ6MDYsIEdlb3JnZSBTaHVrbGluIHdyb3RlOgo+IDI0LjAxLjIwMTMgMTc6 MjUsIFBhdWwgRHVycmFudCDQv9C40YjQtdGCOgo+Pj4KPj4+IFNvbWUgbm90ZXMgYWJvdXQgZ3Vl c3Qgc3VzcGVuZCBkdXJpbmcgSU8uCj4+Pgo+Pj4gSSB0ZXN0ZWQgdGhhdCB3YXkgZm9yIHN0b3Jh Z2UgcmVib290IChwYXVzZSBhbGwgZG9tYWlucywgcmVib290IElTQ1NJIHN0b3JhZ2UKPj4+IGFu ZCByZXN1bWUgZXZlcnkgZG9tYWluKS4gSWYgcGF1c2UgaXMgc2hvcnQgKGxlc3MgdGhhdCAyIG1p bnV0ZXMpLCBndWVzdCBjYW4KPj4+IHN1cnZpdmUuIElmIHBhdXNlIGlzIGxvbmdlciB0aGFuIDIg bWludXRlcywgZ3Vlc3RzIGluIHN0YXRlIG9mIHdhaXRpbmcgZm9yIGlvCj4+PiBjb21wbGV0aW9u LCBkZXRlY3RzIElPIHRpbWVvdXQgYWZ0ZXIgcmVzdW1pbmcgIGFuZCBjYXVzZSBJTyBlcnJvciBv biB2aXJ0dWFsCj4+PiBibG9jayBkZXZpY2VzLiAoUFYpLgo+Pj4KPj4gVG8gYmUgY2xlYXIgaGVy ZTogZG8geW91IG1lYW4geW91ICpwYXVzZWQqIGFuZCB0aGVuIHVucGF1c2VkIHRoZSBWTXMsIG9y ICpzdXNwZW5kZWQqIGFuZCB0aGVuIHJlc3VtZWQgdGhlIFZNcz8gSSBzdXNwZWN0IHlvdSBtZWFu IHRoZSBmb3JtZXIuCj4+Cj4+ICAgICBQYXVsCj4gUGF1c2UsIG9mIGNhdXNlLiBNeSBiYWQuCj4K CklmIHlvdSB3b3VsZCBkbyBhIHN1c3BlbmQsIHRoZSBmcm9udGVuZCBkcml2ZXIgZmx1c2ggb3V0 IGRpc2sgSU8gCm9wZXJhdGlvbnMgYmVmb3JlIHN1c3BlbmQgcmVhY2hlZCwgYW5kIHRoZXJlZm9y ZSB0aGVyZSB3b24ndCBiZSBhbnl0aGluZyAKdG8gdGltZW91dCBhZnRlciByZXN1bWUuIEhvd2V2 ZXIsIGlmIHRoZSBzdG9yYWdlIGRyaXZlciBkb21haW4ganVzdCAKY3Jhc2hlZCwgSSBndWVzcyB0 aGUgZ3Vlc3Qgd291bGQgY3Jhc2ggYXQgc3VzcGVuZC4gTWF5YmUgd2UgY2FuIHRyeSBvdXQgCnNv bWV0aGluZyB0byBzYXZlIHRoZSB0aGUgcmluZyBidWZmZXIsIGFuZCByZXBsYXkgdGhlbSBiYWNr IG9uY2UgdGhlIApiYWNrZW5kIGNvbWUgYmFjayAoYnV0IGJlZm9yZSByZXN1bWluZyB0aGUgZ3Vl c3QpLiBCdXQgSSdtIG5vdCBzdXJlIAp3aGV0aGVyIHRoZSBndWVzdCB3b3VsZCBoYW5kbGUgdGhl IHRpbWVvdXRzIGFmdGVyIHRoZSByZXN1bWUgZmlyc3QsIG9yIApjYW5jZWwgdGhlbSBpZiB0aGUg cmVxdWVzdHMgd2VyZSBzdWNjZXNmdWxseSByZXNwb25kZWQuCgpab2xpCgpfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApY ZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFu L2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Thu Jan 24 15:02:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 15:02:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyOKC-0004ga-JT; Thu, 24 Jan 2013 15:02:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyOKB-0004gQ-6H; Thu, 24 Jan 2013 15:02:43 +0000 Received: from [193.109.254.147:30911] by server-9.bemta-14.messagelabs.com id E2/2E-17118-21D41015; Thu, 24 Jan 2013 15:02:42 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1359039714!3134542!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTgyMzA=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19533 invoked from network); 24 Jan 2013 15:01:56 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 15:01:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4683111" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 15:01:27 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 10:01:27 -0500 Message-ID: <51014CDC.1030501@citrix.com> Date: Thu, 24 Jan 2013 15:01:48 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: George Shuklin References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> In-Reply-To: <51013FED.60201@gmail.com> X-Originating-IP: [10.80.2.133] Cc: "xen-api@lists.xen.org" , Ian Campbell , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gMjQvMDEvMTMgMTQ6MDYsIEdlb3JnZSBTaHVrbGluIHdyb3RlOgo+IDI0LjAxLjIwMTMgMTc6 MjUsIFBhdWwgRHVycmFudCDQv9C40YjQtdGCOgo+Pj4KPj4+IFNvbWUgbm90ZXMgYWJvdXQgZ3Vl c3Qgc3VzcGVuZCBkdXJpbmcgSU8uCj4+Pgo+Pj4gSSB0ZXN0ZWQgdGhhdCB3YXkgZm9yIHN0b3Jh Z2UgcmVib290IChwYXVzZSBhbGwgZG9tYWlucywgcmVib290IElTQ1NJIHN0b3JhZ2UKPj4+IGFu ZCByZXN1bWUgZXZlcnkgZG9tYWluKS4gSWYgcGF1c2UgaXMgc2hvcnQgKGxlc3MgdGhhdCAyIG1p bnV0ZXMpLCBndWVzdCBjYW4KPj4+IHN1cnZpdmUuIElmIHBhdXNlIGlzIGxvbmdlciB0aGFuIDIg bWludXRlcywgZ3Vlc3RzIGluIHN0YXRlIG9mIHdhaXRpbmcgZm9yIGlvCj4+PiBjb21wbGV0aW9u LCBkZXRlY3RzIElPIHRpbWVvdXQgYWZ0ZXIgcmVzdW1pbmcgIGFuZCBjYXVzZSBJTyBlcnJvciBv biB2aXJ0dWFsCj4+PiBibG9jayBkZXZpY2VzLiAoUFYpLgo+Pj4KPj4gVG8gYmUgY2xlYXIgaGVy ZTogZG8geW91IG1lYW4geW91ICpwYXVzZWQqIGFuZCB0aGVuIHVucGF1c2VkIHRoZSBWTXMsIG9y ICpzdXNwZW5kZWQqIGFuZCB0aGVuIHJlc3VtZWQgdGhlIFZNcz8gSSBzdXNwZWN0IHlvdSBtZWFu IHRoZSBmb3JtZXIuCj4+Cj4+ICAgICBQYXVsCj4gUGF1c2UsIG9mIGNhdXNlLiBNeSBiYWQuCj4K CklmIHlvdSB3b3VsZCBkbyBhIHN1c3BlbmQsIHRoZSBmcm9udGVuZCBkcml2ZXIgZmx1c2ggb3V0 IGRpc2sgSU8gCm9wZXJhdGlvbnMgYmVmb3JlIHN1c3BlbmQgcmVhY2hlZCwgYW5kIHRoZXJlZm9y ZSB0aGVyZSB3b24ndCBiZSBhbnl0aGluZyAKdG8gdGltZW91dCBhZnRlciByZXN1bWUuIEhvd2V2 ZXIsIGlmIHRoZSBzdG9yYWdlIGRyaXZlciBkb21haW4ganVzdCAKY3Jhc2hlZCwgSSBndWVzcyB0 aGUgZ3Vlc3Qgd291bGQgY3Jhc2ggYXQgc3VzcGVuZC4gTWF5YmUgd2UgY2FuIHRyeSBvdXQgCnNv bWV0aGluZyB0byBzYXZlIHRoZSB0aGUgcmluZyBidWZmZXIsIGFuZCByZXBsYXkgdGhlbSBiYWNr IG9uY2UgdGhlIApiYWNrZW5kIGNvbWUgYmFjayAoYnV0IGJlZm9yZSByZXN1bWluZyB0aGUgZ3Vl c3QpLiBCdXQgSSdtIG5vdCBzdXJlIAp3aGV0aGVyIHRoZSBndWVzdCB3b3VsZCBoYW5kbGUgdGhl IHRpbWVvdXRzIGFmdGVyIHRoZSByZXN1bWUgZmlyc3QsIG9yIApjYW5jZWwgdGhlbSBpZiB0aGUg cmVxdWVzdHMgd2VyZSBzdWNjZXNmdWxseSByZXNwb25kZWQuCgpab2xpCgpfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApY ZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFu L2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Thu Jan 24 15:32:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 15:32:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyOnI-0005ss-1L; Thu, 24 Jan 2013 15:32:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyOS6-00051i-H8; Thu, 24 Jan 2013 15:10:54 +0000 Received: from [85.158.143.99:17989] by server-1.bemta-4.messagelabs.com id 26/CE-05635-DFE41015; Thu, 24 Jan 2013 15:10:53 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1359040250!28357027!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTY4ODk=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16480 invoked from network); 24 Jan 2013 15:10:52 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 15:10:52 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4937249" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 15:10:50 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 10:10:49 -0500 Received: from andrewcoop.uk.xensource.com ([10.80.2.18]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TyOS1-0004S3-El; Thu, 24 Jan 2013 15:10:49 +0000 Message-ID: <51014EF9.5040502@citrix.com> Date: Thu, 24 Jan 2013 15:10:49 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130119 Icedove/10.0.12 MIME-Version: 1.0 To: Zoltan Kiss References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> <51014CDC.1030501@citrix.com> In-Reply-To: <51014CDC.1030501@citrix.com> X-Enigmail-Version: 1.4 X-Mailman-Approved-At: Thu, 24 Jan 2013 15:32:46 +0000 Cc: "'xen-devel@lists.xen.org'" , "xen-api@lists.xen.org" , Ian Campbell Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gMjQvMDEvMTMgMTU6MDEsIFpvbHRhbiBLaXNzIHdyb3RlOgo+IE9uIDI0LzAxLzEzIDE0OjA2 LCBHZW9yZ2UgU2h1a2xpbiB3cm90ZToKPj4gMjQuMDEuMjAxMyAxNzoyNSwgUGF1bCBEdXJyYW50 INC/0LjRiNC10YI6Cj4+Pj4gU29tZSBub3RlcyBhYm91dCBndWVzdCBzdXNwZW5kIGR1cmluZyBJ Ty4KPj4+Pgo+Pj4+IEkgdGVzdGVkIHRoYXQgd2F5IGZvciBzdG9yYWdlIHJlYm9vdCAocGF1c2Ug YWxsIGRvbWFpbnMsIHJlYm9vdCBJU0NTSSBzdG9yYWdlCj4+Pj4gYW5kIHJlc3VtZSBldmVyeSBk b21haW4pLiBJZiBwYXVzZSBpcyBzaG9ydCAobGVzcyB0aGF0IDIgbWludXRlcyksIGd1ZXN0IGNh bgo+Pj4+IHN1cnZpdmUuIElmIHBhdXNlIGlzIGxvbmdlciB0aGFuIDIgbWludXRlcywgZ3Vlc3Rz IGluIHN0YXRlIG9mIHdhaXRpbmcgZm9yIGlvCj4+Pj4gY29tcGxldGlvbiwgZGV0ZWN0cyBJTyB0 aW1lb3V0IGFmdGVyIHJlc3VtaW5nICBhbmQgY2F1c2UgSU8gZXJyb3Igb24gdmlydHVhbAo+Pj4+ IGJsb2NrIGRldmljZXMuIChQVikuCj4+Pj4KPj4+IFRvIGJlIGNsZWFyIGhlcmU6IGRvIHlvdSBt ZWFuIHlvdSAqcGF1c2VkKiBhbmQgdGhlbiB1bnBhdXNlZCB0aGUgVk1zLCBvciAqc3VzcGVuZGVk KiBhbmQgdGhlbiByZXN1bWVkIHRoZSBWTXM/IEkgc3VzcGVjdCB5b3UgbWVhbiB0aGUgZm9ybWVy Lgo+Pj4KPj4+ICAgICBQYXVsCj4+IFBhdXNlLCBvZiBjYXVzZS4gTXkgYmFkLgo+Pgo+IElmIHlv dSB3b3VsZCBkbyBhIHN1c3BlbmQsIHRoZSBmcm9udGVuZCBkcml2ZXIgZmx1c2ggb3V0IGRpc2sg SU8gCj4gb3BlcmF0aW9ucyBiZWZvcmUgc3VzcGVuZCByZWFjaGVkLCBhbmQgdGhlcmVmb3JlIHRo ZXJlIHdvbid0IGJlIGFueXRoaW5nIAo+IHRvIHRpbWVvdXQgYWZ0ZXIgcmVzdW1lLiBIb3dldmVy LCBpZiB0aGUgc3RvcmFnZSBkcml2ZXIgZG9tYWluIGp1c3QgCj4gY3Jhc2hlZCwgSSBndWVzcyB0 aGUgZ3Vlc3Qgd291bGQgY3Jhc2ggYXQgc3VzcGVuZC4gTWF5YmUgd2UgY2FuIHRyeSBvdXQgCj4g c29tZXRoaW5nIHRvIHNhdmUgdGhlIHRoZSByaW5nIGJ1ZmZlciwgYW5kIHJlcGxheSB0aGVtIGJh Y2sgb25jZSB0aGUgCj4gYmFja2VuZCBjb21lIGJhY2sgKGJ1dCBiZWZvcmUgcmVzdW1pbmcgdGhl IGd1ZXN0KS4gQnV0IEknbSBub3Qgc3VyZSAKPiB3aGV0aGVyIHRoZSBndWVzdCB3b3VsZCBoYW5k bGUgdGhlIHRpbWVvdXRzIGFmdGVyIHRoZSByZXN1bWUgZmlyc3QsIG9yIAo+IGNhbmNlbCB0aGVt IGlmIHRoZSByZXF1ZXN0cyB3ZXJlIHN1Y2Nlc2Z1bGx5IHJlc3BvbmRlZC4KPgo+IFpvbGkKClBl cmhhcHMgSSBhbSBtYWtpbmcgdGhpcyBoYXJkZXIsIGJ1dCBtaWdodCBpdCBiZSBiZXN0IHRvIHdh aXQgZm9yIGEKc2hvcnQgd2hpbGUgKDE1LTMwIHNlY29uZHMpIGZvciB0aGUgZGV2aWNlIGRyaXZl ciBkb21haW4gdG8gY29tZSBiYWNrLAphbmQgaWYgaXQgdGFrZXMgbG9uZ2VyIHRoYW4gdGhhdCwg cGF1c2UgdGhlIFZNLgoKVGhpcyB3YXksIGlmIHRoZSBkcml2ZXIgZG9tYWluIGlzIGZhc3QgdG8g Y29tZSBiYWNrLCBhbGwgdGhlIGd1ZXN0Cm5vdGljZXMgaXMgdHJhbnNpdG9yaWx5IGJsb2NrZWQg SU8sIGFuZCBpZiB0aGUgZHJpdmVyIGRvbWFpbiBpcyB0b28gc2xvdwooYnV0IGRvZXMgY29tZSBi YWNrKSwgYWxsIHRoZSBndWVzdCBtaWdodCBub3RpY2VzIGlzIGEgcGF1c2UuCgpVbHRpbWF0ZWx5 LCBpZiB0aGUgZHJpdmVyIGRvbWFpbiBuZXZlciBjb21lcyBiYWNrLCB0aGVuIHdlIGFyZSBpbiBh IG5vCndvcnNlIHBvc2l0aW9uIHRoYW4gY3VycmVudGx5LgoKfkFuZHJldwoKPgo+IF9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gWGVuLWRldmVsIG1haWxp bmcgbGlzdAo+IFhlbi1kZXZlbEBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcv eGVuLWRldmVsCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18KWGVuLWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0 cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Thu Jan 24 15:32:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 15:32:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyOnI-0005ss-1L; Thu, 24 Jan 2013 15:32:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyOS6-00051i-H8; Thu, 24 Jan 2013 15:10:54 +0000 Received: from [85.158.143.99:17989] by server-1.bemta-4.messagelabs.com id 26/CE-05635-DFE41015; Thu, 24 Jan 2013 15:10:53 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1359040250!28357027!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTY4ODk=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16480 invoked from network); 24 Jan 2013 15:10:52 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 15:10:52 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4937249" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 15:10:50 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 10:10:49 -0500 Received: from andrewcoop.uk.xensource.com ([10.80.2.18]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TyOS1-0004S3-El; Thu, 24 Jan 2013 15:10:49 +0000 Message-ID: <51014EF9.5040502@citrix.com> Date: Thu, 24 Jan 2013 15:10:49 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130119 Icedove/10.0.12 MIME-Version: 1.0 To: Zoltan Kiss References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> <51014CDC.1030501@citrix.com> In-Reply-To: <51014CDC.1030501@citrix.com> X-Enigmail-Version: 1.4 X-Mailman-Approved-At: Thu, 24 Jan 2013 15:32:46 +0000 Cc: "'xen-devel@lists.xen.org'" , "xen-api@lists.xen.org" , Ian Campbell Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gMjQvMDEvMTMgMTU6MDEsIFpvbHRhbiBLaXNzIHdyb3RlOgo+IE9uIDI0LzAxLzEzIDE0OjA2 LCBHZW9yZ2UgU2h1a2xpbiB3cm90ZToKPj4gMjQuMDEuMjAxMyAxNzoyNSwgUGF1bCBEdXJyYW50 INC/0LjRiNC10YI6Cj4+Pj4gU29tZSBub3RlcyBhYm91dCBndWVzdCBzdXNwZW5kIGR1cmluZyBJ Ty4KPj4+Pgo+Pj4+IEkgdGVzdGVkIHRoYXQgd2F5IGZvciBzdG9yYWdlIHJlYm9vdCAocGF1c2Ug YWxsIGRvbWFpbnMsIHJlYm9vdCBJU0NTSSBzdG9yYWdlCj4+Pj4gYW5kIHJlc3VtZSBldmVyeSBk b21haW4pLiBJZiBwYXVzZSBpcyBzaG9ydCAobGVzcyB0aGF0IDIgbWludXRlcyksIGd1ZXN0IGNh bgo+Pj4+IHN1cnZpdmUuIElmIHBhdXNlIGlzIGxvbmdlciB0aGFuIDIgbWludXRlcywgZ3Vlc3Rz IGluIHN0YXRlIG9mIHdhaXRpbmcgZm9yIGlvCj4+Pj4gY29tcGxldGlvbiwgZGV0ZWN0cyBJTyB0 aW1lb3V0IGFmdGVyIHJlc3VtaW5nICBhbmQgY2F1c2UgSU8gZXJyb3Igb24gdmlydHVhbAo+Pj4+ IGJsb2NrIGRldmljZXMuIChQVikuCj4+Pj4KPj4+IFRvIGJlIGNsZWFyIGhlcmU6IGRvIHlvdSBt ZWFuIHlvdSAqcGF1c2VkKiBhbmQgdGhlbiB1bnBhdXNlZCB0aGUgVk1zLCBvciAqc3VzcGVuZGVk KiBhbmQgdGhlbiByZXN1bWVkIHRoZSBWTXM/IEkgc3VzcGVjdCB5b3UgbWVhbiB0aGUgZm9ybWVy Lgo+Pj4KPj4+ICAgICBQYXVsCj4+IFBhdXNlLCBvZiBjYXVzZS4gTXkgYmFkLgo+Pgo+IElmIHlv dSB3b3VsZCBkbyBhIHN1c3BlbmQsIHRoZSBmcm9udGVuZCBkcml2ZXIgZmx1c2ggb3V0IGRpc2sg SU8gCj4gb3BlcmF0aW9ucyBiZWZvcmUgc3VzcGVuZCByZWFjaGVkLCBhbmQgdGhlcmVmb3JlIHRo ZXJlIHdvbid0IGJlIGFueXRoaW5nIAo+IHRvIHRpbWVvdXQgYWZ0ZXIgcmVzdW1lLiBIb3dldmVy LCBpZiB0aGUgc3RvcmFnZSBkcml2ZXIgZG9tYWluIGp1c3QgCj4gY3Jhc2hlZCwgSSBndWVzcyB0 aGUgZ3Vlc3Qgd291bGQgY3Jhc2ggYXQgc3VzcGVuZC4gTWF5YmUgd2UgY2FuIHRyeSBvdXQgCj4g c29tZXRoaW5nIHRvIHNhdmUgdGhlIHRoZSByaW5nIGJ1ZmZlciwgYW5kIHJlcGxheSB0aGVtIGJh Y2sgb25jZSB0aGUgCj4gYmFja2VuZCBjb21lIGJhY2sgKGJ1dCBiZWZvcmUgcmVzdW1pbmcgdGhl IGd1ZXN0KS4gQnV0IEknbSBub3Qgc3VyZSAKPiB3aGV0aGVyIHRoZSBndWVzdCB3b3VsZCBoYW5k bGUgdGhlIHRpbWVvdXRzIGFmdGVyIHRoZSByZXN1bWUgZmlyc3QsIG9yIAo+IGNhbmNlbCB0aGVt IGlmIHRoZSByZXF1ZXN0cyB3ZXJlIHN1Y2Nlc2Z1bGx5IHJlc3BvbmRlZC4KPgo+IFpvbGkKClBl cmhhcHMgSSBhbSBtYWtpbmcgdGhpcyBoYXJkZXIsIGJ1dCBtaWdodCBpdCBiZSBiZXN0IHRvIHdh aXQgZm9yIGEKc2hvcnQgd2hpbGUgKDE1LTMwIHNlY29uZHMpIGZvciB0aGUgZGV2aWNlIGRyaXZl ciBkb21haW4gdG8gY29tZSBiYWNrLAphbmQgaWYgaXQgdGFrZXMgbG9uZ2VyIHRoYW4gdGhhdCwg cGF1c2UgdGhlIFZNLgoKVGhpcyB3YXksIGlmIHRoZSBkcml2ZXIgZG9tYWluIGlzIGZhc3QgdG8g Y29tZSBiYWNrLCBhbGwgdGhlIGd1ZXN0Cm5vdGljZXMgaXMgdHJhbnNpdG9yaWx5IGJsb2NrZWQg SU8sIGFuZCBpZiB0aGUgZHJpdmVyIGRvbWFpbiBpcyB0b28gc2xvdwooYnV0IGRvZXMgY29tZSBi YWNrKSwgYWxsIHRoZSBndWVzdCBtaWdodCBub3RpY2VzIGlzIGEgcGF1c2UuCgpVbHRpbWF0ZWx5 LCBpZiB0aGUgZHJpdmVyIGRvbWFpbiBuZXZlciBjb21lcyBiYWNrLCB0aGVuIHdlIGFyZSBpbiBh IG5vCndvcnNlIHBvc2l0aW9uIHRoYW4gY3VycmVudGx5LgoKfkFuZHJldwoKPgo+IF9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gWGVuLWRldmVsIG1haWxp bmcgbGlzdAo+IFhlbi1kZXZlbEBsaXN0cy54ZW4ub3JnCj4gaHR0cDovL2xpc3RzLnhlbi5vcmcv eGVuLWRldmVsCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18KWGVuLWFwaSBtYWlsaW5nIGxpc3QKWGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0 cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Thu Jan 24 16:56:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 16:56:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQ6T-000105-CJ; Thu, 24 Jan 2013 16:56:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQ6S-0000zx-6o; Thu, 24 Jan 2013 16:56:40 +0000 Received: from [85.158.139.83:30659] by server-12.bemta-5.messagelabs.com id 7B/0E-31102-7C761015; Thu, 24 Jan 2013 16:56:39 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1359046598!29597343!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23840 invoked from network); 24 Jan 2013 16:56:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 16:56:38 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="871542" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 16:56:38 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 24 Jan 2013 16:56:38 +0000 From: Paul Durrant To: Andrew Cooper , Zoltan Kiss Date: Thu, 24 Jan 2013 16:57:07 +0000 Thread-Topic: [Xen-devel] driver domain crash d reconnect handling Thread-Index: Ac36U0D2/UP3MvGNQLCbLRuFC7wlSA== Message-ID: <291EDFCB1E9E224A99088639C4762022013F451DCBB4@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "'xen-devel@lists.xen.org'" , Ian Campbell , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] driver domain crash d reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBBbmRyZXcgQ29vcGVyIFttYWls dG86YW5kcmV3LmNvb3BlcjNAY2l0cml4LmNvbV0NCj4gU2VudDogMjQgSmFudWFyeSAyMDEzIDE1 OjExDQo+IFRvOiBab2x0YW4gS2lzcw0KPiBDYzogR2VvcmdlIFNodWtsaW47IHhlbi1hcGlAbGlz dHMueGVuLm9yZzsgSWFuIENhbXBiZWxsOyBQYXVsIER1cnJhbnQ7IERhdmUNCj4gU2NvdHQ7ICd4 ZW4tZGV2ZWxAbGlzdHMueGVuLm9yZycNCj4gU3ViamVjdDogUmU6IFtYZW4tZGV2ZWxdIGRyaXZl ciBkb21haW4gY3Jhc2ggYW5kIHJlY29ubmVjdCBoYW5kbGluZw0KPiANCj4gT24gMjQvMDEvMTMg MTU6MDEsIFpvbHRhbiBLaXNzIHdyb3RlOg0KPiA+IE9uIDI0LzAxLzEzIDE0OjA2LCBHZW9yZ2Ug U2h1a2xpbiB3cm90ZToNCj4gPj4gMjQuMDEuMjAxMyAxNzoyNSwgUGF1bCBEdXJyYW50INC/0LjR iNC10YI6DQo+ID4+Pj4gU29tZSBub3RlcyBhYm91dCBndWVzdCBzdXNwZW5kIGR1cmluZyBJTy4N Cj4gPj4+Pg0KPiA+Pj4+IEkgdGVzdGVkIHRoYXQgd2F5IGZvciBzdG9yYWdlIHJlYm9vdCAocGF1 c2UgYWxsIGRvbWFpbnMsIHJlYm9vdA0KPiA+Pj4+IElTQ1NJIHN0b3JhZ2UgYW5kIHJlc3VtZSBl dmVyeSBkb21haW4pLiBJZiBwYXVzZSBpcyBzaG9ydCAobGVzcw0KPiA+Pj4+IHRoYXQgMiBtaW51 dGVzKSwgZ3Vlc3QgY2FuIHN1cnZpdmUuIElmIHBhdXNlIGlzIGxvbmdlciB0aGFuIDINCj4gPj4+ PiBtaW51dGVzLCBndWVzdHMgaW4gc3RhdGUgb2Ygd2FpdGluZyBmb3IgaW8gY29tcGxldGlvbiwg ZGV0ZWN0cyBJTw0KPiA+Pj4+IHRpbWVvdXQgYWZ0ZXIgcmVzdW1pbmcgIGFuZCBjYXVzZSBJTyBl cnJvciBvbiB2aXJ0dWFsIGJsb2NrIGRldmljZXMuDQo+IChQVikuDQo+ID4+Pj4NCj4gPj4+IFRv IGJlIGNsZWFyIGhlcmU6IGRvIHlvdSBtZWFuIHlvdSAqcGF1c2VkKiBhbmQgdGhlbiB1bnBhdXNl ZCB0aGUNCj4gVk1zLCBvciAqc3VzcGVuZGVkKiBhbmQgdGhlbiByZXN1bWVkIHRoZSBWTXM/IEkg c3VzcGVjdCB5b3UgbWVhbiB0aGUNCj4gZm9ybWVyLg0KPiA+Pj4NCj4gPj4+ICAgICBQYXVsDQo+ ID4+IFBhdXNlLCBvZiBjYXVzZS4gTXkgYmFkLg0KPiA+Pg0KPiA+IElmIHlvdSB3b3VsZCBkbyBh IHN1c3BlbmQsIHRoZSBmcm9udGVuZCBkcml2ZXIgZmx1c2ggb3V0IGRpc2sgSU8NCj4gPiBvcGVy YXRpb25zIGJlZm9yZSBzdXNwZW5kIHJlYWNoZWQsIGFuZCB0aGVyZWZvcmUgdGhlcmUgd29uJ3Qg YmUNCj4gPiBhbnl0aGluZyB0byB0aW1lb3V0IGFmdGVyIHJlc3VtZS4gSG93ZXZlciwgaWYgdGhl IHN0b3JhZ2UgZHJpdmVyDQo+ID4gZG9tYWluIGp1c3QgY3Jhc2hlZCwgSSBndWVzcyB0aGUgZ3Vl c3Qgd291bGQgY3Jhc2ggYXQgc3VzcGVuZC4gTWF5YmUNCj4gPiB3ZSBjYW4gdHJ5IG91dCBzb21l dGhpbmcgdG8gc2F2ZSB0aGUgdGhlIHJpbmcgYnVmZmVyLCBhbmQgcmVwbGF5IHRoZW0NCj4gPiBi YWNrIG9uY2UgdGhlIGJhY2tlbmQgY29tZSBiYWNrIChidXQgYmVmb3JlIHJlc3VtaW5nIHRoZSBn dWVzdCkuIEJ1dA0KPiA+IEknbSBub3Qgc3VyZSB3aGV0aGVyIHRoZSBndWVzdCB3b3VsZCBoYW5k bGUgdGhlIHRpbWVvdXRzIGFmdGVyIHRoZQ0KPiA+IHJlc3VtZSBmaXJzdCwgb3IgY2FuY2VsIHRo ZW0gaWYgdGhlIHJlcXVlc3RzIHdlcmUgc3VjY2VzZnVsbHkgcmVzcG9uZGVkLg0KPiA+DQo+ID4g Wm9saQ0KPiANCj4gUGVyaGFwcyBJIGFtIG1ha2luZyB0aGlzIGhhcmRlciwgYnV0IG1pZ2h0IGl0 IGJlIGJlc3QgdG8gd2FpdCBmb3IgYSBzaG9ydA0KPiB3aGlsZSAoMTUtMzAgc2Vjb25kcykgZm9y IHRoZSBkZXZpY2UgZHJpdmVyIGRvbWFpbiB0byBjb21lIGJhY2ssIGFuZCBpZiBpdA0KPiB0YWtl cyBsb25nZXIgdGhhbiB0aGF0LCBwYXVzZSB0aGUgVk0uDQo+IA0KPiBUaGlzIHdheSwgaWYgdGhl IGRyaXZlciBkb21haW4gaXMgZmFzdCB0byBjb21lIGJhY2ssIGFsbCB0aGUgZ3Vlc3Qgbm90aWNl cyBpcw0KPiB0cmFuc2l0b3JpbHkgYmxvY2tlZCBJTywgYW5kIGlmIHRoZSBkcml2ZXIgZG9tYWlu IGlzIHRvbyBzbG93IChidXQgZG9lcyBjb21lDQo+IGJhY2spLCBhbGwgdGhlIGd1ZXN0IG1pZ2h0 IG5vdGljZXMgaXMgYSBwYXVzZS4NCj4gDQo+IFVsdGltYXRlbHksIGlmIHRoZSBkcml2ZXIgZG9t YWluIG5ldmVyIGNvbWVzIGJhY2ssIHRoZW4gd2UgYXJlIGluIGEgbm8NCj4gd29yc2UgcG9zaXRp b24gdGhhbiBjdXJyZW50bHkuDQo+DQoNCldoYXQgZG8geW91IG1lYW4gYnkgJ2NvbWUgYmFjaycg aGVyZT8gSWYgeW91J3JlIHRhbGtpbmcgYWJvdXQgdGhlIHNhbWUgZHJpdmVyIGRvbWFpbiB0aGVu IGZhaXIgZW5vdWdoLiBJZiB5b3UncmUgdGFsa2luZyBhYm91dCBhIG5ldyBpbnN0YW5jZSB0aGVu IHBhdXNpbmcgb3Igbm90IHBhdXNpbmcgdGhlIFZNIGlzIGltbWF0ZXJpYWwuIFVubGVzcyB0aGUg ZnJvbnRlbmRzIGFyZSBwcm9kZGVkIHRvIGNvbm5lY3QgdG8gdGhlIG5ldyBiYWNrZW5kcyAocmVt ZW1iZXJpbmcgdGhhdCB0aGUgeGVuc3RvcmUgcGF0aHMgaGF2ZSB0aGUgZG9taWQgYmFrZWQgaW50 byB0aGVtKSB0aGVuIElPIHdpbGwgYmxvY2sgZm9yZXZlci4gSW4gZ2VuZXJhbCB5b3UncmUgZ29p bmcgdG8gbmVlZCB0byBnbyB0aHJvdWdoIGEgZnVsbCBzdXNwZW5kL3Jlc3VtZSBvZiB0aGUgZnJv bnRlbmQgdG8gYWNoaWV2ZSB0aGlzLCB1bmxlc3Mgd2Ugd3JpdGUgbmV3IGZyb250ZW5kIGNvZGUg dG8gZGlyZWN0bHkgbm90aWNlIHRoZSBjaGFuZ2UgaW4gdGhlIGJhY2tlbmQgKGFuZCBkaXN0aW5n dWlzaCBpdCBmcm9tIGFuIHVucGx1ZykgYW5kIHJlY29ubmVjdCBhdXRvbWF0aWNhbGx5Lg0KDQog IFBhdWwNCiANCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Clhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Thu Jan 24 16:56:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 16:56:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQ6T-000105-CJ; Thu, 24 Jan 2013 16:56:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQ6S-0000zx-6o; Thu, 24 Jan 2013 16:56:40 +0000 Received: from [85.158.139.83:30659] by server-12.bemta-5.messagelabs.com id 7B/0E-31102-7C761015; Thu, 24 Jan 2013 16:56:39 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1359046598!29597343!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23840 invoked from network); 24 Jan 2013 16:56:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 16:56:38 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="871542" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 16:56:38 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 24 Jan 2013 16:56:38 +0000 From: Paul Durrant To: Andrew Cooper , Zoltan Kiss Date: Thu, 24 Jan 2013 16:57:07 +0000 Thread-Topic: [Xen-devel] driver domain crash d reconnect handling Thread-Index: Ac36U0D2/UP3MvGNQLCbLRuFC7wlSA== Message-ID: <291EDFCB1E9E224A99088639C4762022013F451DCBB4@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "'xen-devel@lists.xen.org'" , Ian Campbell , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] driver domain crash d reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBBbmRyZXcgQ29vcGVyIFttYWls dG86YW5kcmV3LmNvb3BlcjNAY2l0cml4LmNvbV0NCj4gU2VudDogMjQgSmFudWFyeSAyMDEzIDE1 OjExDQo+IFRvOiBab2x0YW4gS2lzcw0KPiBDYzogR2VvcmdlIFNodWtsaW47IHhlbi1hcGlAbGlz dHMueGVuLm9yZzsgSWFuIENhbXBiZWxsOyBQYXVsIER1cnJhbnQ7IERhdmUNCj4gU2NvdHQ7ICd4 ZW4tZGV2ZWxAbGlzdHMueGVuLm9yZycNCj4gU3ViamVjdDogUmU6IFtYZW4tZGV2ZWxdIGRyaXZl ciBkb21haW4gY3Jhc2ggYW5kIHJlY29ubmVjdCBoYW5kbGluZw0KPiANCj4gT24gMjQvMDEvMTMg MTU6MDEsIFpvbHRhbiBLaXNzIHdyb3RlOg0KPiA+IE9uIDI0LzAxLzEzIDE0OjA2LCBHZW9yZ2Ug U2h1a2xpbiB3cm90ZToNCj4gPj4gMjQuMDEuMjAxMyAxNzoyNSwgUGF1bCBEdXJyYW50INC/0LjR iNC10YI6DQo+ID4+Pj4gU29tZSBub3RlcyBhYm91dCBndWVzdCBzdXNwZW5kIGR1cmluZyBJTy4N Cj4gPj4+Pg0KPiA+Pj4+IEkgdGVzdGVkIHRoYXQgd2F5IGZvciBzdG9yYWdlIHJlYm9vdCAocGF1 c2UgYWxsIGRvbWFpbnMsIHJlYm9vdA0KPiA+Pj4+IElTQ1NJIHN0b3JhZ2UgYW5kIHJlc3VtZSBl dmVyeSBkb21haW4pLiBJZiBwYXVzZSBpcyBzaG9ydCAobGVzcw0KPiA+Pj4+IHRoYXQgMiBtaW51 dGVzKSwgZ3Vlc3QgY2FuIHN1cnZpdmUuIElmIHBhdXNlIGlzIGxvbmdlciB0aGFuIDINCj4gPj4+ PiBtaW51dGVzLCBndWVzdHMgaW4gc3RhdGUgb2Ygd2FpdGluZyBmb3IgaW8gY29tcGxldGlvbiwg ZGV0ZWN0cyBJTw0KPiA+Pj4+IHRpbWVvdXQgYWZ0ZXIgcmVzdW1pbmcgIGFuZCBjYXVzZSBJTyBl cnJvciBvbiB2aXJ0dWFsIGJsb2NrIGRldmljZXMuDQo+IChQVikuDQo+ID4+Pj4NCj4gPj4+IFRv IGJlIGNsZWFyIGhlcmU6IGRvIHlvdSBtZWFuIHlvdSAqcGF1c2VkKiBhbmQgdGhlbiB1bnBhdXNl ZCB0aGUNCj4gVk1zLCBvciAqc3VzcGVuZGVkKiBhbmQgdGhlbiByZXN1bWVkIHRoZSBWTXM/IEkg c3VzcGVjdCB5b3UgbWVhbiB0aGUNCj4gZm9ybWVyLg0KPiA+Pj4NCj4gPj4+ICAgICBQYXVsDQo+ ID4+IFBhdXNlLCBvZiBjYXVzZS4gTXkgYmFkLg0KPiA+Pg0KPiA+IElmIHlvdSB3b3VsZCBkbyBh IHN1c3BlbmQsIHRoZSBmcm9udGVuZCBkcml2ZXIgZmx1c2ggb3V0IGRpc2sgSU8NCj4gPiBvcGVy YXRpb25zIGJlZm9yZSBzdXNwZW5kIHJlYWNoZWQsIGFuZCB0aGVyZWZvcmUgdGhlcmUgd29uJ3Qg YmUNCj4gPiBhbnl0aGluZyB0byB0aW1lb3V0IGFmdGVyIHJlc3VtZS4gSG93ZXZlciwgaWYgdGhl IHN0b3JhZ2UgZHJpdmVyDQo+ID4gZG9tYWluIGp1c3QgY3Jhc2hlZCwgSSBndWVzcyB0aGUgZ3Vl c3Qgd291bGQgY3Jhc2ggYXQgc3VzcGVuZC4gTWF5YmUNCj4gPiB3ZSBjYW4gdHJ5IG91dCBzb21l dGhpbmcgdG8gc2F2ZSB0aGUgdGhlIHJpbmcgYnVmZmVyLCBhbmQgcmVwbGF5IHRoZW0NCj4gPiBi YWNrIG9uY2UgdGhlIGJhY2tlbmQgY29tZSBiYWNrIChidXQgYmVmb3JlIHJlc3VtaW5nIHRoZSBn dWVzdCkuIEJ1dA0KPiA+IEknbSBub3Qgc3VyZSB3aGV0aGVyIHRoZSBndWVzdCB3b3VsZCBoYW5k bGUgdGhlIHRpbWVvdXRzIGFmdGVyIHRoZQ0KPiA+IHJlc3VtZSBmaXJzdCwgb3IgY2FuY2VsIHRo ZW0gaWYgdGhlIHJlcXVlc3RzIHdlcmUgc3VjY2VzZnVsbHkgcmVzcG9uZGVkLg0KPiA+DQo+ID4g Wm9saQ0KPiANCj4gUGVyaGFwcyBJIGFtIG1ha2luZyB0aGlzIGhhcmRlciwgYnV0IG1pZ2h0IGl0 IGJlIGJlc3QgdG8gd2FpdCBmb3IgYSBzaG9ydA0KPiB3aGlsZSAoMTUtMzAgc2Vjb25kcykgZm9y IHRoZSBkZXZpY2UgZHJpdmVyIGRvbWFpbiB0byBjb21lIGJhY2ssIGFuZCBpZiBpdA0KPiB0YWtl cyBsb25nZXIgdGhhbiB0aGF0LCBwYXVzZSB0aGUgVk0uDQo+IA0KPiBUaGlzIHdheSwgaWYgdGhl IGRyaXZlciBkb21haW4gaXMgZmFzdCB0byBjb21lIGJhY2ssIGFsbCB0aGUgZ3Vlc3Qgbm90aWNl cyBpcw0KPiB0cmFuc2l0b3JpbHkgYmxvY2tlZCBJTywgYW5kIGlmIHRoZSBkcml2ZXIgZG9tYWlu IGlzIHRvbyBzbG93IChidXQgZG9lcyBjb21lDQo+IGJhY2spLCBhbGwgdGhlIGd1ZXN0IG1pZ2h0 IG5vdGljZXMgaXMgYSBwYXVzZS4NCj4gDQo+IFVsdGltYXRlbHksIGlmIHRoZSBkcml2ZXIgZG9t YWluIG5ldmVyIGNvbWVzIGJhY2ssIHRoZW4gd2UgYXJlIGluIGEgbm8NCj4gd29yc2UgcG9zaXRp b24gdGhhbiBjdXJyZW50bHkuDQo+DQoNCldoYXQgZG8geW91IG1lYW4gYnkgJ2NvbWUgYmFjaycg aGVyZT8gSWYgeW91J3JlIHRhbGtpbmcgYWJvdXQgdGhlIHNhbWUgZHJpdmVyIGRvbWFpbiB0aGVu IGZhaXIgZW5vdWdoLiBJZiB5b3UncmUgdGFsa2luZyBhYm91dCBhIG5ldyBpbnN0YW5jZSB0aGVu IHBhdXNpbmcgb3Igbm90IHBhdXNpbmcgdGhlIFZNIGlzIGltbWF0ZXJpYWwuIFVubGVzcyB0aGUg ZnJvbnRlbmRzIGFyZSBwcm9kZGVkIHRvIGNvbm5lY3QgdG8gdGhlIG5ldyBiYWNrZW5kcyAocmVt ZW1iZXJpbmcgdGhhdCB0aGUgeGVuc3RvcmUgcGF0aHMgaGF2ZSB0aGUgZG9taWQgYmFrZWQgaW50 byB0aGVtKSB0aGVuIElPIHdpbGwgYmxvY2sgZm9yZXZlci4gSW4gZ2VuZXJhbCB5b3UncmUgZ29p bmcgdG8gbmVlZCB0byBnbyB0aHJvdWdoIGEgZnVsbCBzdXNwZW5kL3Jlc3VtZSBvZiB0aGUgZnJv bnRlbmQgdG8gYWNoaWV2ZSB0aGlzLCB1bmxlc3Mgd2Ugd3JpdGUgbmV3IGZyb250ZW5kIGNvZGUg dG8gZGlyZWN0bHkgbm90aWNlIHRoZSBjaGFuZ2UgaW4gdGhlIGJhY2tlbmQgKGFuZCBkaXN0aW5n dWlzaCBpdCBmcm9tIGFuIHVucGx1ZykgYW5kIHJlY29ubmVjdCBhdXRvbWF0aWNhbGx5Lg0KDQog IFBhdWwNCiANCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Clhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMu eGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Thu Jan 24 17:14:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 17:14:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQNl-00025j-8u; Thu, 24 Jan 2013 17:14:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQNj-00025X-AR; Thu, 24 Jan 2013 17:14:31 +0000 Received: from [193.109.254.147:59193] by server-5.bemta-14.messagelabs.com id F4/CB-01458-6FB61015; Thu, 24 Jan 2013 17:14:30 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1359047669!9884819!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1978 invoked from network); 24 Jan 2013 17:14:29 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 17:14:29 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="872107" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 17:14:29 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Thu, 24 Jan 2013 17:14:28 +0000 Message-ID: <1359047667.32057.31.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Zoltan Kiss Date: Thu, 24 Jan 2013 17:14:27 +0000 In-Reply-To: <51014CDC.1030501@citrix.com> References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> <51014CDC.1030501@citrix.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, 2013-01-24 at 15:01 +0000, Zoltan Kiss wrote: > If you would do a suspend, the frontend driver flush out disk IO > operations before suspend reached, and therefore there won't be anything > to timeout after resume. Actually the behaviour, of Linux blkfront at least, is to not do anything on suspend but instead to replay the outstanding requests on the ring on resume. This is to support checkpointing (where you don't need to replay but I think it is exactly what you want for the driver domain crash case too. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 17:14:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 17:14:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQNl-00025j-8u; Thu, 24 Jan 2013 17:14:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQNj-00025X-AR; Thu, 24 Jan 2013 17:14:31 +0000 Received: from [193.109.254.147:59193] by server-5.bemta-14.messagelabs.com id F4/CB-01458-6FB61015; Thu, 24 Jan 2013 17:14:30 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1359047669!9884819!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1978 invoked from network); 24 Jan 2013 17:14:29 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 17:14:29 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="872107" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 17:14:29 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Thu, 24 Jan 2013 17:14:28 +0000 Message-ID: <1359047667.32057.31.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Zoltan Kiss Date: Thu, 24 Jan 2013 17:14:27 +0000 In-Reply-To: <51014CDC.1030501@citrix.com> References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> <51014CDC.1030501@citrix.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Thu, 2013-01-24 at 15:01 +0000, Zoltan Kiss wrote: > If you would do a suspend, the frontend driver flush out disk IO > operations before suspend reached, and therefore there won't be anything > to timeout after resume. Actually the behaviour, of Linux blkfront at least, is to not do anything on suspend but instead to replay the outstanding requests on the ring on resume. This is to support checkpointing (where you don't need to replay but I think it is exactly what you want for the driver domain crash case too. Ian. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 17:32:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 17:32:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQea-0002fD-DX; Thu, 24 Jan 2013 17:31:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQeY-0002ez-Al for Xen-api@lists.xen.org; Thu, 24 Jan 2013 17:31:54 +0000 Received: from [85.158.143.35:19053] by server-1.bemta-4.messagelabs.com id 4F/C1-05635-90071015; Thu, 24 Jan 2013 17:31:53 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1359048712!15765260!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11982 invoked from network); 24 Jan 2013 17:31:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 17:31:52 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208,217";a="872478" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 17:31:52 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 24 Jan 2013 17:31:52 +0000 From: James Bulpin To: Lingfeng Xiong , "Xen-api@lists.xen.org" Date: Thu, 24 Jan 2013 17:32:47 +0000 Thread-Topic: =?utf-8?B?W1hlbi1BUEldIEFueXdheSB0byBtaWdyYXRlIG15IFZNIGZyb20gEFhlbiB4?= =?utf-8?B?bCB0byBYQ1A/?= Thread-Index: Ac3583mWTc8I3wL5SK2J8nHg//hk/AAXqNkw Message-ID: <344C0F67BC927847A2C92F9EE358DB0E0134C39EF234@LONPMAILBOX01.citrite.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] =?utf-8?q?Anyway_to_migrate_my_VM_from_=10Xen_xl_to_XCP?= =?utf-8?q?=3F?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7639614437799544109==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7639614437799544109== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_344C0F67BC927847A2C92F9EE358DB0E0134C39EF234LONPMAILBOX_" --_000_344C0F67BC927847A2C92F9EE358DB0E0134C39EF234LONPMAILBOX_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 T25lIHdheSB3b3VsZCBiZSB0bywgZm9yIGVhY2ggVk06DQoNCjEuICAgICAgIENvbnZlcnQgZWFj aCBxY293MiBmaWxlIHRvIGEgcmF3IGZpbGUgdXNpbmcgcWNvdzJyYXcg4oCTIHB1dCB0aGVzZSBm aWxlcyBzb21ld2hlcmUgKGUuZy4gYSBORlMgZXhwb3J0KSB3aGVyZSB5b3UgY2FuIHRlbXBvcmFy aWx5IHJlYWNoIHRoZW0gZnJvbSBYQ1DigJlzIGRvbWFpbjANCg0KMi4gICAgICAgVXNpbmcgWENQ IOKAnGluc3RhbGzigJ0gYSBWTSB1c2luZyB0aGUgbW9zdCBzdWl0YWJsZSB0ZW1wbGF0ZSBidXQg bm90IGFjdHVhbGx5IHN0YXJ0aW5nIHRoZSBWTSBvciBnb2luZyB0aHJvdWdoIHRoZSBpbnN0YWxs LiBNYWtlIHN1cmUgdG8gY2hvb3NlIHZpcnR1YWwgZGlzayBzaXplcyBhdCBsZWFzdCBhcyBiaWcg YXMgdGhlIHZpcnR1YWwgc2l6ZSBvZiB0aGUgb3JpZ2luYWwgcWNvdzIgb25lcy4gU2V0IHZpcnR1 YWwgTklDIE1BQyBhZGRyZXNzZXMgdG8gbWF0Y2ggeW91ciB4bCBWTS4gIEZvciBQViB5b3XigJls bCBuZWVkIHRvIHRyaWNrIFhDUCBpbnRvIHRoaW5raW5nIHlvdeKAmXZlIGNvbXBsZXRlZCB0aGUg aW5zdGFsbCBieQ0KDQphLiAgICAgICBjaGFuZ2luZyBQVi1ib290bG9hZGVyIHRvIHB5Z3J1YiAo eGUgdm0tcGFyYW0tc2V0IHV1aWQ9PHZtdXVpZD4gUFYtYm9vdGxvYWRlcj1weWdydWIpDQoNCmIu ICAgICAgbWFraW5nIHRoZSBmaXJzdCBWQkQgYm9vdGFibGUgKHhlIHZiZC1wYXJhbS1zZXQgdXVp ZD0kKHhlIHZiZC1saXN0IHZtLXV1aWQ9PHZtdXVpZD4gdXNlcmRldmljZT0wIC0tbWluaW1hbCkg Ym9vdGFibGU9dHJ1ZSkNCg0KYy4gICAgICAgbWFraW5nIHRoZSB2aXJ0dWFsIENEIGRyaXZlIChp ZiBwcmVzZW50KSBub3QgYm9vdGFibGU6ICh4ZSB2YmQtcGFyYW0tc2V0IHV1aWQ9JCh4ZSB2YmQt bGlzdCB2bS11dWlkPTx2bXV1aWQ+IHR5cGU9Q0QgLS1taW5pbWFsKSBib290YWJsZT1mYWxzZSkN Cg0KMy4gICAgICAgT25lIGJ5IG9uZSBhdHRhY2ggdGhlIFZN4oCZcyB2aXJ0dWFsIGRpc2tzIHRv IGRvbTAg4oCTIG15IHByZWZlcnJlZCB3YXkgaXMgdG86DQoNCmEuICAgICAgIEZpbmQgdGhlIFZE SeKAmXMgVVVJRCBieSB1c2luZyDigJx4ZSB2bS1kaXNrLWxpc3QgdXVpZD08dm11dWlkPuKAnSDi gJMgbG9vayBmb3IgZS5nLiDigJxEaXNrIDAgVkRJ4oCdDQoNCmIuICAgICAgUnVuIOKAnC9vcHQv eGVuc291cmNlL2RlYnVnL3dpdGgtdmRpIDx2ZGl1dWlkPuKAnSDigJMgdGhpcyBhdHRhY2hlcyB0 aGUgVkRJIHRvIGRvbTAgYXMgL2Rldi8kREVWSUNFIGFuZCBkcm9wcyB5b3UgaW50byBhIHNoZWxs IOKAkyBleGl0aW5nIHRoaXMgc2hlbGwgd2lsbCBkZXRhY2ggdGhlIFZESQ0KDQo0LiAgICAgICBV c2UgL29wdC94ZW5zb3VyY2UvbGliZXhlYy9zcGFyc2VfZGQgdG8gZGQgdGhlIGNvbnRlbnRzIG9m IHRoZSByYXcgZmlsZSAoZnJvbSBzdGVwIDEpIHRvIHRoZSBWREkuDQoNCmEuICAgICAgIEUuZy4g L29wdC94ZW5zb3VyY2UvbGliZXhlYy9zcGFyc2VfZGQgLXNyYyAvbW50L015Vk0uaW1nIC1kZXN0 IC9kZXYvJERFVklDRSAtc2l6ZSA4NTg5OTM0NTkyIC1wcmV6ZXJvZWQNCg0KNS4gICAgICAgRXhp dCB0aGUg4oCcd2l0aC12ZGnigJ0gc2hlbGwNCg0KSeKAmXZlIHRyaWVkIHRoaXMgZm9yIGEgeGwg UFYgVk0gSSBoYXZlIGFuZCBpdCB3b3JrZWQgKEkgc3RhcnRlZCBmcm9tIHJhdyBpbWFnZSByYXRo ZXIgdGhhbiBxY293MiBzbyBza2lwcGVkIHN0ZXAgMSkuIE15IHRlc3QgYWxzbyBkaWZmZXJzIGlu IHRoYXQgcm9vdCBpcyBvbiB4dmRhMSBob3dldmVyIHlvdXIgY2FzZSBzaG91bGQgYmUgZmluZSDi gJMgSUlSQyBweWdydWIgaXMgT0sgd2l0aCByb290IG9uIHRoZSByYXcgZGV2aWNlLg0KDQpDaGVl cnMsDQpKYW1lcw0KDQpGcm9tOiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyBbbWFpbHRv Onhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbiBCZWhhbGYgT2YgTGluZ2ZlbmcgWGlv bmcNClNlbnQ6IDI0IEphbnVhcnkgMjAxMyAwNToyNQ0KVG86IFhlbi1hcGlAbGlzdHMueGVuLm9y Zw0KU3ViamVjdDogW1hlbi1BUEldIEFueXdheSB0byBtaWdyYXRlIG15IFZNIGZyb20gWGVuIHhs IHRvIFhDUD8NCg0KSGkgYWxsLA0KDQpJIGFtIHJ1bm5pbmcgYSBVYnVudHUgU2VydmVyIHdpdGgg WGVuIDQuMSBpbnN0YWxsZWQuIEFsbCBWTXMgYXJlIHJ1bm5pbmcgb24gdGhhdCBzZXJ2ZXIgd2l0 aCBvbmUgb3IgbW9yZSB2aXJ0dWFsIGRpc2tzIHN0b3JlZCBpbiBxY293MiBmb3JtYXQuIFRoZXNl IFZNcyBhcmUgbWFuYWdlZCBieSAneGwnIHRvb2xzdGFjay4gT25lIFZNIGlzIFdpbmRvd3MgaW4g SFZNIG1vZGVzIGFuZCBvdGhlcnMgYXJlIFBWIFZNcy4gVGhlIHFjb3cyIGZpbGUganVzdCBjb250 YWlucyB0aGUgcm9vdCBmaWxlc3lzdGVtIGFuZCBoYXMgbm8gcGFydGl0aW9uIHN0cnVjdHVyZXMu DQoNCk5vdyBJIGluc3RhbGxlZCBhIG5ldyBzZXJ2ZXIgd2l0aCBYQ1AgMS42LiAgSSBoYXZlIHRv IG1pZ3JhdGUgYWxsIFZNcyBmcm9tIG9sZCBzZXJ2ZXIgdG8gWENQIHdpdGggYWxsIGRhdGEuDQoN CklzIHRoZXJlIGFueXdheSB0byBkbyB0aGlzPw0KDQpUaGFua3MgaW4gYWR2YW5jZWQhDQoNCg== --_000_344C0F67BC927847A2C92F9EE358DB0E0134C39EF234LONPMAILBOX_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0 aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt ZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYi O30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K CWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNw YW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y OnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnANCgl7bXNvLXN0eWxlLXBy aW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207 DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt c2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpw Lk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdy YXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBjbTsNCgltYXJnaW4t cmlnaHQ6MGNtOw0KCW1hcmdpbi1ib3R0b206MGNtOw0KCW1hcmdpbi1sZWZ0OjM2LjBwdDsNCglt YXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToi VGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHls ZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp ZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpl eHBvcnQtb25seTt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7 DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24x DQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGww DQoJe21zby1saXN0LWlkOjk0Mjc2Mjg2ODsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28t bGlzdC10ZW1wbGF0ZS1pZHM6LTU1Nzk2NDYgMTM0ODA3NTY3IDEzNDgwNzU3NyAxMzQ4MDc1Nzkg MTM0ODA3NTY3IDEzNDgwNzU3NyAxMzQ4MDc1NzkgMTM0ODA3NTY3IDEzNDgwNzU3NyAxMzQ4MDc1 Nzk7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0O30NCkBsaXN0 IGwwOmxldmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDphbHBoYS1sb3dlcjsNCgltc28t bGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJ dGV4dC1pbmRlbnQ6LTE4LjBwdDt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQp1bA0KCXtt YXJnaW4tYm90dG9tOjBjbTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K PG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwh W2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9 ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlv dXQ+PC94bWw+PCFbZW5kaWZdLS0+PC9oZWFkPjxib2R5IGxhbmc9RU4tR0IgbGluaz1ibHVlIHZs aW5rPXB1cnBsZT48ZGl2IGNsYXNzPVdvcmRTZWN0aW9uMT48cCBjbGFzcz1Nc29Ob3JtYWw+PHNw YW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNl cmlmIjtjb2xvcjojMUY0OTdEJz5PbmUgd2F5IHdvdWxkIGJlIHRvLCBmb3IgZWFjaCBWTTo8bzpw PjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTGlzdFBhcmFncmFwaCBzdHlsZT0ndGV4dC1p bmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSc+PCFbaWYgIXN1cHBvcnRMaXN0 c10+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJz YW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48c3BhbiBzdHlsZT0nbXNvLWxpc3Q6SWdub3JlJz4x LjxzcGFuIHN0eWxlPSdmb250OjcuMHB0ICJUaW1lcyBOZXcgUm9tYW4iJz4mbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxz cGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z ZXJpZiI7Y29sb3I6IzFGNDk3RCc+Q29udmVydCBlYWNoIHFjb3cyIGZpbGUgdG8gYSByYXcgZmls ZSB1c2luZyBxY293MnJhdyDigJMgcHV0IHRoZXNlIGZpbGVzIHNvbWV3aGVyZSAoZS5nLiBhIE5G UyBleHBvcnQpIHdoZXJlIHlvdSBjYW4gdGVtcG9yYXJpbHkgcmVhY2ggdGhlbSBmcm9tIFhDUOKA mXMgZG9tYWluMDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29MaXN0UGFyYWdyYXBo IHN0eWxlPSd0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8xJz48IVtp ZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28t bGlzdDpJZ25vcmUnPjIuPHNwYW4gc3R5bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5ldyBSb21hbiIn PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+PC9zcGFuPjwvc3Bh bj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNh bGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5Vc2luZyBYQ1Ag4oCcaW5zdGFsbOKA nSBhIFZNIHVzaW5nIHRoZSBtb3N0IHN1aXRhYmxlIHRlbXBsYXRlIGJ1dCBub3QgYWN0dWFsbHkg c3RhcnRpbmcgdGhlIFZNIG9yIGdvaW5nIHRocm91Z2ggdGhlIGluc3RhbGwuIE1ha2Ugc3VyZSB0 byBjaG9vc2UgdmlydHVhbCBkaXNrIHNpemVzIGF0IGxlYXN0IGFzIGJpZyBhcyB0aGUgPGI+dmly dHVhbDwvYj4gc2l6ZSBvZiB0aGUgb3JpZ2luYWwgcWNvdzIgb25lcy4gU2V0IHZpcnR1YWwgTklD IE1BQyBhZGRyZXNzZXMgdG8gbWF0Y2ggeW91ciB4bCBWTS4gwqBGb3IgUFYgeW914oCZbGwgbmVl ZCB0byB0cmljayBYQ1AgaW50byB0aGlua2luZyB5b3XigJl2ZSBjb21wbGV0ZWQgdGhlIGluc3Rh bGwgYnk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTGlzdFBhcmFncmFwaCBzdHls ZT0nbWFyZ2luLWxlZnQ6NzIuMHB0O3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2 ZWwyIGxmbzEnPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEu MHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PHNw YW4gc3R5bGU9J21zby1saXN0Oklnbm9yZSc+YS48c3BhbiBzdHlsZT0nZm9udDo3LjBwdCAiVGlt ZXMgTmV3IFJvbWFuIic+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDwvc3Bh bj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtm b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPmNoYW5naW5n IFBWLWJvb3Rsb2FkZXIgdG8gcHlncnViICg8L3NwYW4+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTox MS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojQzA1MDREJz54 ZSB2bS1wYXJhbS1zZXQgdXVpZD0mbHQ7dm11dWlkJmd0OyBQVi1ib290bG9hZGVyPXB5Z3J1Yjwv c3Bhbj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIs InNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPik8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xh c3M9TXNvTGlzdFBhcmFncmFwaCBzdHlsZT0nbWFyZ2luLWxlZnQ6NzIuMHB0O3RleHQtaW5kZW50 Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwyIGxmbzEnPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxz cGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z ZXJpZiI7Y29sb3I6IzFGNDk3RCc+PHNwYW4gc3R5bGU9J21zby1saXN0Oklnbm9yZSc+Yi48c3Bh biBzdHlsZT0nZm9udDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0n Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9y OiMxRjQ5N0QnPm1ha2luZyB0aGUgZmlyc3QgVkJEIGJvb3RhYmxlICg8L3NwYW4+PHNwYW4gc3R5 bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtj b2xvcjojQzA1MDREJz54ZSB2YmQtcGFyYW0tc2V0IHV1aWQ9JCh4ZSB2YmQtbGlzdCB2bS11dWlk PSZsdDt2bXV1aWQmZ3Q7IHVzZXJkZXZpY2U9MCAtLW1pbmltYWwpIGJvb3RhYmxlPXRydWU8L3Nw YW4+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJz YW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4pPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNz PU1zb0xpc3RQYXJhZ3JhcGggc3R5bGU9J21hcmdpbi1sZWZ0OjcyLjBwdDt0ZXh0LWluZGVudDot MTguMHB0O21zby1saXN0OmwwIGxldmVsMiBsZm8xJz48IVtpZiAhc3VwcG9ydExpc3RzXT48c3Bh biBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy aWYiO2NvbG9yOiMxRjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPmMuPHNwYW4g c3R5bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5ldyBSb21hbiInPiZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5 bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtj b2xvcjojMUY0OTdEJz5tYWtpbmcgdGhlIHZpcnR1YWwgQ0QgZHJpdmUgKGlmIHByZXNlbnQpIG5v dCBib290YWJsZTogKDwvc3Bhbj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiNDMDUwNEQnPnhlIHZiZC1wYXJhbS1z ZXQgdXVpZD0kKHhlIHZiZC1saXN0IHZtLXV1aWQ9Jmx0O3ZtdXVpZCZndDsgdHlwZT1DRCAtLW1p bmltYWwpIGJvb3RhYmxlPWZhbHNlPC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0 O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+KTxvOnA+ PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29MaXN0UGFyYWdyYXBoIHN0eWxlPSd0ZXh0LWlu ZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8xJz48IVtpZiAhc3VwcG9ydExpc3Rz XT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNh bnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPjMu PHNwYW4gc3R5bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5ldyBSb21hbiInPiZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNw YW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNl cmlmIjtjb2xvcjojMUY0OTdEJz5PbmUgYnkgb25lIGF0dGFjaCB0aGUgVk3igJlzIHZpcnR1YWwg ZGlza3MgdG8gZG9tMCDigJMgbXkgcHJlZmVycmVkIHdheSBpcyB0bzo8bzpwPjwvbzpwPjwvc3Bh bj48L3A+PHAgY2xhc3M9TXNvTGlzdFBhcmFncmFwaCBzdHlsZT0nbWFyZ2luLWxlZnQ6NzIuMHB0 O3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwyIGxmbzEnPjwhW2lmICFzdXBw b3J0TGlzdHNdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxp YnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PHNwYW4gc3R5bGU9J21zby1saXN0Okln bm9yZSc+YS48c3BhbiBzdHlsZT0nZm9udDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2Vu ZGlmXT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIs InNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkZpbmQgdGhlIFZESeKAmXMgVVVJRCBieSB1c2lu ZyDigJw8L3NwYW4+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNh bGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojQzA1MDREJz54ZSB2bS1kaXNrLWxpc3QgdXVpZD0m bHQ7dm11dWlkJmd0Ozwvc3Bhbj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPuKAnSDigJMgbG9vayBm b3IgZS5nLiDigJxEaXNrIDAgVkRJ4oCdPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1z b0xpc3RQYXJhZ3JhcGggc3R5bGU9J21hcmdpbi1sZWZ0OjcyLjBwdDt0ZXh0LWluZGVudDotMTgu MHB0O21zby1saXN0OmwwIGxldmVsMiBsZm8xJz48IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBz dHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYi O2NvbG9yOiMxRjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPmIuPHNwYW4gc3R5 bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5ldyBSb21hbiInPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyA8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9J2ZvbnQt c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0 OTdEJz5SdW4g4oCcL29wdC94ZW5zb3VyY2UvZGVidWcvd2l0aC12ZGkgJmx0O3ZkaXV1aWQmZ3Q7 4oCdIOKAkyB0aGlzIGF0dGFjaGVzIHRoZSBWREkgdG8gZG9tMCBhcyAvZGV2LyRERVZJQ0UgYW5k IGRyb3BzIHlvdSBpbnRvIGEgc2hlbGwg4oCTIGV4aXRpbmcgdGhpcyBzaGVsbCB3aWxsIGRldGFj aCB0aGUgVkRJPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb0xpc3RQYXJhZ3JhcGgg c3R5bGU9J3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEnPjwhW2lm ICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5 OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PHNwYW4gc3R5bGU9J21zby1s aXN0Oklnbm9yZSc+NC48c3BhbiBzdHlsZT0nZm9udDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+ Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFu PjwhW2VuZGlmXT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2Fs aWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPlVzZSAvb3B0L3hlbnNvdXJjZS9saWJl eGVjL3NwYXJzZV9kZCB0byBkZCB0aGUgY29udGVudHMgb2YgdGhlIHJhdyBmaWxlIChmcm9tIHN0 ZXAgMSkgdG8gdGhlIFZESS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTGlzdFBh cmFncmFwaCBzdHlsZT0nbWFyZ2luLWxlZnQ6NzIuMHB0O3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNv LWxpc3Q6bDAgbGV2ZWwyIGxmbzEnPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSdm b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6 I0MwNTA0RCc+PHNwYW4gc3R5bGU9J21zby1saXN0Oklnbm9yZSc+YS48c3BhbiBzdHlsZT0nZm9u dDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0nZm9udC1z aXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5 N0QnPkUuZy4gPC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5 OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6I0MwNTA0RCc+L29wdC94ZW5zb3VyY2UvbGli ZXhlYy9zcGFyc2VfZGQgLXNyYyAvbW50L015Vk0uaW1nIC1kZXN0IC9kZXYvJERFVklDRSAtc2l6 ZSA4NTg5OTM0NTkyIC1wcmV6ZXJvZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNv TGlzdFBhcmFncmFwaCBzdHlsZT0ndGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZl bDEgbGZvMSc+PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4w cHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48c3Bh biBzdHlsZT0nbXNvLWxpc3Q6SWdub3JlJz41LjxzcGFuIHN0eWxlPSdmb250OjcuMHB0ICJUaW1l cyBOZXcgUm9tYW4iJz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPC9zcGFu Pjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2Zv bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+RXhpdCB0aGUg 4oCcd2l0aC12ZGnigJ0gc2hlbGw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9y bWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwi c2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxw IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPknigJl2ZSB0cmllZCB0aGlz IGZvciBhIHhsIFBWIFZNIEkgaGF2ZSBhbmQgaXQgd29ya2VkIChJIHN0YXJ0ZWQgZnJvbSByYXcg aW1hZ2UgcmF0aGVyIHRoYW4gcWNvdzIgc28gc2tpcHBlZCBzdGVwIDEpLiBNeSB0ZXN0IGFsc28g ZGlmZmVycyBpbiB0aGF0IHJvb3QgaXMgb24geHZkYTEgaG93ZXZlciB5b3VyIGNhc2Ugc2hvdWxk IGJlIGZpbmUg4oCTIElJUkMgcHlncnViIGlzIE9LIHdpdGggcm9vdCBvbiB0aGUgcmF3IGRldmlj ZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdm b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6 IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48 c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt c2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkNoZWVycyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xh c3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJD YWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+SmFtZXM8bzpwPjwvbzpwPjwvc3Bh bj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2Zv bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJz cDs8L286cD48L3NwYW4+PC9wPjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv bGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCc+PGRpdj48ZGl2IHN0eWxl PSdib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBw dCAwY20gMGNtIDBjbSc+PHAgY2xhc3M9TXNvTm9ybWFsPjxiPjxzcGFuIGxhbmc9RU4tVVMgc3R5 bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiJz5G cm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtm b250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMu eGVuLm9yZyBbbWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSA8Yj5PbiBCZWhh bGYgT2YgPC9iPkxpbmdmZW5nIFhpb25nPGJyPjxiPlNlbnQ6PC9iPiAyNCBKYW51YXJ5IDIwMTMg MDU6MjU8YnI+PGI+VG86PC9iPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmc8YnI+PGI+U3ViamVjdDo8 L2I+IFtYZW4tQVBJXSBBbnl3YXkgdG8gbWlncmF0ZSBteSBWTSBmcm9tIFhlbiB4bCB0byBYQ1A/ PG86cD48L286cD48L3NwYW4+PC9wPjwvZGl2PjwvZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48bzpw PiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+SGkgYWxsLDxvOnA+PC9vOnA+PC9w PjxkaXY+PHA+SSBhbSBydW5uaW5nIGEgVWJ1bnR1IFNlcnZlciB3aXRoIFhlbiA0LjEgaW5zdGFs bGVkLiBBbGwgVk1zIGFyZSBydW5uaW5nIG9uIHRoYXQgc2VydmVyIHdpdGggb25lIG9yIG1vcmUg dmlydHVhbCBkaXNrcyBzdG9yZWQgaW4gcWNvdzIgZm9ybWF0LiBUaGVzZSBWTXMgYXJlIG1hbmFn ZWQgYnkgJ3hsJyB0b29sc3RhY2suIE9uZSBWTSBpcyBXaW5kb3dzIGluIEhWTSBtb2RlcyBhbmQg b3RoZXJzIGFyZSBQViBWTXMuIFRoZSBxY293MiBmaWxlIGp1c3QgY29udGFpbnMgdGhlIHJvb3Qg ZmlsZXN5c3RlbSBhbmQgaGFzIG5vIHBhcnRpdGlvbiBzdHJ1Y3R1cmVzLjxvOnA+PC9vOnA+PC9w PjxwPk5vdyBJIGluc3RhbGxlZCBhIG5ldyBzZXJ2ZXIgd2l0aCBYQ1AgMS42LiZuYnNwOyBJIGhh dmUgdG8gbWlncmF0ZSBhbGwgVk1zIGZyb20gb2xkIHNlcnZlciB0byBYQ1Agd2l0aCBhbGwgZGF0 YS48bzpwPjwvbzpwPjwvcD48cD5JcyB0aGVyZSBhbnl3YXkgdG8gZG8gdGhpcz88bzpwPjwvbzpw PjwvcD48cD5UaGFua3MgaW4gYWR2YW5jZWQhPG86cD48L286cD48L3A+PC9kaXY+PHAgY2xhc3M9 TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjwvZGl2PjwvZGl2PjwvYm9keT48L2h0bWw+ --_000_344C0F67BC927847A2C92F9EE358DB0E0134C39EF234LONPMAILBOX_-- --===============7639614437799544109== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7639614437799544109==-- From xen-api-bounces@lists.xen.org Thu Jan 24 17:32:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 17:32:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQea-0002fD-DX; Thu, 24 Jan 2013 17:31:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyQeY-0002ez-Al for Xen-api@lists.xen.org; Thu, 24 Jan 2013 17:31:54 +0000 Received: from [85.158.143.35:19053] by server-1.bemta-4.messagelabs.com id 4F/C1-05635-90071015; Thu, 24 Jan 2013 17:31:53 +0000 X-Env-Sender: James.Bulpin@eu.citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1359048712!15765260!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDE4Njg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11982 invoked from network); 24 Jan 2013 17:31:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 17:31:52 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208,217";a="872478" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 17:31:52 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 24 Jan 2013 17:31:52 +0000 From: James Bulpin To: Lingfeng Xiong , "Xen-api@lists.xen.org" Date: Thu, 24 Jan 2013 17:32:47 +0000 Thread-Topic: =?utf-8?B?W1hlbi1BUEldIEFueXdheSB0byBtaWdyYXRlIG15IFZNIGZyb20gEFhlbiB4?= =?utf-8?B?bCB0byBYQ1A/?= Thread-Index: Ac3583mWTc8I3wL5SK2J8nHg//hk/AAXqNkw Message-ID: <344C0F67BC927847A2C92F9EE358DB0E0134C39EF234@LONPMAILBOX01.citrite.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] =?utf-8?q?Anyway_to_migrate_my_VM_from_=10Xen_xl_to_XCP?= =?utf-8?q?=3F?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7639614437799544109==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7639614437799544109== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_344C0F67BC927847A2C92F9EE358DB0E0134C39EF234LONPMAILBOX_" --_000_344C0F67BC927847A2C92F9EE358DB0E0134C39EF234LONPMAILBOX_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 T25lIHdheSB3b3VsZCBiZSB0bywgZm9yIGVhY2ggVk06DQoNCjEuICAgICAgIENvbnZlcnQgZWFj aCBxY293MiBmaWxlIHRvIGEgcmF3IGZpbGUgdXNpbmcgcWNvdzJyYXcg4oCTIHB1dCB0aGVzZSBm aWxlcyBzb21ld2hlcmUgKGUuZy4gYSBORlMgZXhwb3J0KSB3aGVyZSB5b3UgY2FuIHRlbXBvcmFy aWx5IHJlYWNoIHRoZW0gZnJvbSBYQ1DigJlzIGRvbWFpbjANCg0KMi4gICAgICAgVXNpbmcgWENQ IOKAnGluc3RhbGzigJ0gYSBWTSB1c2luZyB0aGUgbW9zdCBzdWl0YWJsZSB0ZW1wbGF0ZSBidXQg bm90IGFjdHVhbGx5IHN0YXJ0aW5nIHRoZSBWTSBvciBnb2luZyB0aHJvdWdoIHRoZSBpbnN0YWxs LiBNYWtlIHN1cmUgdG8gY2hvb3NlIHZpcnR1YWwgZGlzayBzaXplcyBhdCBsZWFzdCBhcyBiaWcg YXMgdGhlIHZpcnR1YWwgc2l6ZSBvZiB0aGUgb3JpZ2luYWwgcWNvdzIgb25lcy4gU2V0IHZpcnR1 YWwgTklDIE1BQyBhZGRyZXNzZXMgdG8gbWF0Y2ggeW91ciB4bCBWTS4gIEZvciBQViB5b3XigJls bCBuZWVkIHRvIHRyaWNrIFhDUCBpbnRvIHRoaW5raW5nIHlvdeKAmXZlIGNvbXBsZXRlZCB0aGUg aW5zdGFsbCBieQ0KDQphLiAgICAgICBjaGFuZ2luZyBQVi1ib290bG9hZGVyIHRvIHB5Z3J1YiAo eGUgdm0tcGFyYW0tc2V0IHV1aWQ9PHZtdXVpZD4gUFYtYm9vdGxvYWRlcj1weWdydWIpDQoNCmIu ICAgICAgbWFraW5nIHRoZSBmaXJzdCBWQkQgYm9vdGFibGUgKHhlIHZiZC1wYXJhbS1zZXQgdXVp ZD0kKHhlIHZiZC1saXN0IHZtLXV1aWQ9PHZtdXVpZD4gdXNlcmRldmljZT0wIC0tbWluaW1hbCkg Ym9vdGFibGU9dHJ1ZSkNCg0KYy4gICAgICAgbWFraW5nIHRoZSB2aXJ0dWFsIENEIGRyaXZlIChp ZiBwcmVzZW50KSBub3QgYm9vdGFibGU6ICh4ZSB2YmQtcGFyYW0tc2V0IHV1aWQ9JCh4ZSB2YmQt bGlzdCB2bS11dWlkPTx2bXV1aWQ+IHR5cGU9Q0QgLS1taW5pbWFsKSBib290YWJsZT1mYWxzZSkN Cg0KMy4gICAgICAgT25lIGJ5IG9uZSBhdHRhY2ggdGhlIFZN4oCZcyB2aXJ0dWFsIGRpc2tzIHRv IGRvbTAg4oCTIG15IHByZWZlcnJlZCB3YXkgaXMgdG86DQoNCmEuICAgICAgIEZpbmQgdGhlIFZE SeKAmXMgVVVJRCBieSB1c2luZyDigJx4ZSB2bS1kaXNrLWxpc3QgdXVpZD08dm11dWlkPuKAnSDi gJMgbG9vayBmb3IgZS5nLiDigJxEaXNrIDAgVkRJ4oCdDQoNCmIuICAgICAgUnVuIOKAnC9vcHQv eGVuc291cmNlL2RlYnVnL3dpdGgtdmRpIDx2ZGl1dWlkPuKAnSDigJMgdGhpcyBhdHRhY2hlcyB0 aGUgVkRJIHRvIGRvbTAgYXMgL2Rldi8kREVWSUNFIGFuZCBkcm9wcyB5b3UgaW50byBhIHNoZWxs IOKAkyBleGl0aW5nIHRoaXMgc2hlbGwgd2lsbCBkZXRhY2ggdGhlIFZESQ0KDQo0LiAgICAgICBV c2UgL29wdC94ZW5zb3VyY2UvbGliZXhlYy9zcGFyc2VfZGQgdG8gZGQgdGhlIGNvbnRlbnRzIG9m IHRoZSByYXcgZmlsZSAoZnJvbSBzdGVwIDEpIHRvIHRoZSBWREkuDQoNCmEuICAgICAgIEUuZy4g L29wdC94ZW5zb3VyY2UvbGliZXhlYy9zcGFyc2VfZGQgLXNyYyAvbW50L015Vk0uaW1nIC1kZXN0 IC9kZXYvJERFVklDRSAtc2l6ZSA4NTg5OTM0NTkyIC1wcmV6ZXJvZWQNCg0KNS4gICAgICAgRXhp dCB0aGUg4oCcd2l0aC12ZGnigJ0gc2hlbGwNCg0KSeKAmXZlIHRyaWVkIHRoaXMgZm9yIGEgeGwg UFYgVk0gSSBoYXZlIGFuZCBpdCB3b3JrZWQgKEkgc3RhcnRlZCBmcm9tIHJhdyBpbWFnZSByYXRo ZXIgdGhhbiBxY293MiBzbyBza2lwcGVkIHN0ZXAgMSkuIE15IHRlc3QgYWxzbyBkaWZmZXJzIGlu IHRoYXQgcm9vdCBpcyBvbiB4dmRhMSBob3dldmVyIHlvdXIgY2FzZSBzaG91bGQgYmUgZmluZSDi gJMgSUlSQyBweWdydWIgaXMgT0sgd2l0aCByb290IG9uIHRoZSByYXcgZGV2aWNlLg0KDQpDaGVl cnMsDQpKYW1lcw0KDQpGcm9tOiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZyBbbWFpbHRv Onhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSBPbiBCZWhhbGYgT2YgTGluZ2ZlbmcgWGlv bmcNClNlbnQ6IDI0IEphbnVhcnkgMjAxMyAwNToyNQ0KVG86IFhlbi1hcGlAbGlzdHMueGVuLm9y Zw0KU3ViamVjdDogW1hlbi1BUEldIEFueXdheSB0byBtaWdyYXRlIG15IFZNIGZyb20gWGVuIHhs IHRvIFhDUD8NCg0KSGkgYWxsLA0KDQpJIGFtIHJ1bm5pbmcgYSBVYnVudHUgU2VydmVyIHdpdGgg WGVuIDQuMSBpbnN0YWxsZWQuIEFsbCBWTXMgYXJlIHJ1bm5pbmcgb24gdGhhdCBzZXJ2ZXIgd2l0 aCBvbmUgb3IgbW9yZSB2aXJ0dWFsIGRpc2tzIHN0b3JlZCBpbiBxY293MiBmb3JtYXQuIFRoZXNl IFZNcyBhcmUgbWFuYWdlZCBieSAneGwnIHRvb2xzdGFjay4gT25lIFZNIGlzIFdpbmRvd3MgaW4g SFZNIG1vZGVzIGFuZCBvdGhlcnMgYXJlIFBWIFZNcy4gVGhlIHFjb3cyIGZpbGUganVzdCBjb250 YWlucyB0aGUgcm9vdCBmaWxlc3lzdGVtIGFuZCBoYXMgbm8gcGFydGl0aW9uIHN0cnVjdHVyZXMu DQoNCk5vdyBJIGluc3RhbGxlZCBhIG5ldyBzZXJ2ZXIgd2l0aCBYQ1AgMS42LiAgSSBoYXZlIHRv IG1pZ3JhdGUgYWxsIFZNcyBmcm9tIG9sZCBzZXJ2ZXIgdG8gWENQIHdpdGggYWxsIGRhdGEuDQoN CklzIHRoZXJlIGFueXdheSB0byBkbyB0aGlzPw0KDQpUaGFua3MgaW4gYWR2YW5jZWQhDQoNCg== --_000_344C0F67BC927847A2C92F9EE358DB0E0134C39EF234LONPMAILBOX_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0 aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt ZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYi O30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K CWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNw YW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y OnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnANCgl7bXNvLXN0eWxlLXBy aW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207 DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt c2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpw Lk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdy YXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBjbTsNCgltYXJnaW4t cmlnaHQ6MGNtOw0KCW1hcmdpbi1ib3R0b206MGNtOw0KCW1hcmdpbi1sZWZ0OjM2LjBwdDsNCglt YXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToi VGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHls ZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp ZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpl eHBvcnQtb25seTt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7 DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24x DQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGww DQoJe21zby1saXN0LWlkOjk0Mjc2Mjg2ODsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28t bGlzdC10ZW1wbGF0ZS1pZHM6LTU1Nzk2NDYgMTM0ODA3NTY3IDEzNDgwNzU3NyAxMzQ4MDc1Nzkg MTM0ODA3NTY3IDEzNDgwNzU3NyAxMzQ4MDc1NzkgMTM0ODA3NTY3IDEzNDgwNzU3NyAxMzQ4MDc1 Nzk7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0O30NCkBsaXN0 IGwwOmxldmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDphbHBoYS1sb3dlcjsNCgltc28t bGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJ dGV4dC1pbmRlbnQ6LTE4LjBwdDt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQp1bA0KCXtt YXJnaW4tYm90dG9tOjBjbTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K PG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwh W2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9 ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlv dXQ+PC94bWw+PCFbZW5kaWZdLS0+PC9oZWFkPjxib2R5IGxhbmc9RU4tR0IgbGluaz1ibHVlIHZs aW5rPXB1cnBsZT48ZGl2IGNsYXNzPVdvcmRTZWN0aW9uMT48cCBjbGFzcz1Nc29Ob3JtYWw+PHNw YW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNl cmlmIjtjb2xvcjojMUY0OTdEJz5PbmUgd2F5IHdvdWxkIGJlIHRvLCBmb3IgZWFjaCBWTTo8bzpw PjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTGlzdFBhcmFncmFwaCBzdHlsZT0ndGV4dC1p bmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSc+PCFbaWYgIXN1cHBvcnRMaXN0 c10+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJz YW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48c3BhbiBzdHlsZT0nbXNvLWxpc3Q6SWdub3JlJz4x LjxzcGFuIHN0eWxlPSdmb250OjcuMHB0ICJUaW1lcyBOZXcgUm9tYW4iJz4mbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxz cGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z ZXJpZiI7Y29sb3I6IzFGNDk3RCc+Q29udmVydCBlYWNoIHFjb3cyIGZpbGUgdG8gYSByYXcgZmls ZSB1c2luZyBxY293MnJhdyDigJMgcHV0IHRoZXNlIGZpbGVzIHNvbWV3aGVyZSAoZS5nLiBhIE5G UyBleHBvcnQpIHdoZXJlIHlvdSBjYW4gdGVtcG9yYXJpbHkgcmVhY2ggdGhlbSBmcm9tIFhDUOKA mXMgZG9tYWluMDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29MaXN0UGFyYWdyYXBo IHN0eWxlPSd0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8xJz48IVtp ZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28t bGlzdDpJZ25vcmUnPjIuPHNwYW4gc3R5bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5ldyBSb21hbiIn PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+PC9zcGFuPjwvc3Bh bj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNh bGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5Vc2luZyBYQ1Ag4oCcaW5zdGFsbOKA nSBhIFZNIHVzaW5nIHRoZSBtb3N0IHN1aXRhYmxlIHRlbXBsYXRlIGJ1dCBub3QgYWN0dWFsbHkg c3RhcnRpbmcgdGhlIFZNIG9yIGdvaW5nIHRocm91Z2ggdGhlIGluc3RhbGwuIE1ha2Ugc3VyZSB0 byBjaG9vc2UgdmlydHVhbCBkaXNrIHNpemVzIGF0IGxlYXN0IGFzIGJpZyBhcyB0aGUgPGI+dmly dHVhbDwvYj4gc2l6ZSBvZiB0aGUgb3JpZ2luYWwgcWNvdzIgb25lcy4gU2V0IHZpcnR1YWwgTklD IE1BQyBhZGRyZXNzZXMgdG8gbWF0Y2ggeW91ciB4bCBWTS4gwqBGb3IgUFYgeW914oCZbGwgbmVl ZCB0byB0cmljayBYQ1AgaW50byB0aGlua2luZyB5b3XigJl2ZSBjb21wbGV0ZWQgdGhlIGluc3Rh bGwgYnk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTGlzdFBhcmFncmFwaCBzdHls ZT0nbWFyZ2luLWxlZnQ6NzIuMHB0O3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2 ZWwyIGxmbzEnPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEu MHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PHNw YW4gc3R5bGU9J21zby1saXN0Oklnbm9yZSc+YS48c3BhbiBzdHlsZT0nZm9udDo3LjBwdCAiVGlt ZXMgTmV3IFJvbWFuIic+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDwvc3Bh bj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtm b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPmNoYW5naW5n IFBWLWJvb3Rsb2FkZXIgdG8gcHlncnViICg8L3NwYW4+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTox MS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojQzA1MDREJz54 ZSB2bS1wYXJhbS1zZXQgdXVpZD0mbHQ7dm11dWlkJmd0OyBQVi1ib290bG9hZGVyPXB5Z3J1Yjwv c3Bhbj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIs InNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPik8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xh c3M9TXNvTGlzdFBhcmFncmFwaCBzdHlsZT0nbWFyZ2luLWxlZnQ6NzIuMHB0O3RleHQtaW5kZW50 Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwyIGxmbzEnPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxz cGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z ZXJpZiI7Y29sb3I6IzFGNDk3RCc+PHNwYW4gc3R5bGU9J21zby1saXN0Oklnbm9yZSc+Yi48c3Bh biBzdHlsZT0nZm9udDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0n Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9y OiMxRjQ5N0QnPm1ha2luZyB0aGUgZmlyc3QgVkJEIGJvb3RhYmxlICg8L3NwYW4+PHNwYW4gc3R5 bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtj b2xvcjojQzA1MDREJz54ZSB2YmQtcGFyYW0tc2V0IHV1aWQ9JCh4ZSB2YmQtbGlzdCB2bS11dWlk PSZsdDt2bXV1aWQmZ3Q7IHVzZXJkZXZpY2U9MCAtLW1pbmltYWwpIGJvb3RhYmxlPXRydWU8L3Nw YW4+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJz YW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4pPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNz PU1zb0xpc3RQYXJhZ3JhcGggc3R5bGU9J21hcmdpbi1sZWZ0OjcyLjBwdDt0ZXh0LWluZGVudDot MTguMHB0O21zby1saXN0OmwwIGxldmVsMiBsZm8xJz48IVtpZiAhc3VwcG9ydExpc3RzXT48c3Bh biBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy aWYiO2NvbG9yOiMxRjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPmMuPHNwYW4g c3R5bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5ldyBSb21hbiInPiZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5 bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtj b2xvcjojMUY0OTdEJz5tYWtpbmcgdGhlIHZpcnR1YWwgQ0QgZHJpdmUgKGlmIHByZXNlbnQpIG5v dCBib290YWJsZTogKDwvc3Bhbj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiNDMDUwNEQnPnhlIHZiZC1wYXJhbS1z ZXQgdXVpZD0kKHhlIHZiZC1saXN0IHZtLXV1aWQ9Jmx0O3ZtdXVpZCZndDsgdHlwZT1DRCAtLW1p bmltYWwpIGJvb3RhYmxlPWZhbHNlPC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0 O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+KTxvOnA+ PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29MaXN0UGFyYWdyYXBoIHN0eWxlPSd0ZXh0LWlu ZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8xJz48IVtpZiAhc3VwcG9ydExpc3Rz XT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNh bnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPjMu PHNwYW4gc3R5bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5ldyBSb21hbiInPiZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNw YW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNl cmlmIjtjb2xvcjojMUY0OTdEJz5PbmUgYnkgb25lIGF0dGFjaCB0aGUgVk3igJlzIHZpcnR1YWwg ZGlza3MgdG8gZG9tMCDigJMgbXkgcHJlZmVycmVkIHdheSBpcyB0bzo8bzpwPjwvbzpwPjwvc3Bh bj48L3A+PHAgY2xhc3M9TXNvTGlzdFBhcmFncmFwaCBzdHlsZT0nbWFyZ2luLWxlZnQ6NzIuMHB0 O3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwyIGxmbzEnPjwhW2lmICFzdXBw b3J0TGlzdHNdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxp YnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PHNwYW4gc3R5bGU9J21zby1saXN0Okln bm9yZSc+YS48c3BhbiBzdHlsZT0nZm9udDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2Vu ZGlmXT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIs InNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkZpbmQgdGhlIFZESeKAmXMgVVVJRCBieSB1c2lu ZyDigJw8L3NwYW4+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNh bGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojQzA1MDREJz54ZSB2bS1kaXNrLWxpc3QgdXVpZD0m bHQ7dm11dWlkJmd0Ozwvc3Bhbj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPuKAnSDigJMgbG9vayBm b3IgZS5nLiDigJxEaXNrIDAgVkRJ4oCdPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1z b0xpc3RQYXJhZ3JhcGggc3R5bGU9J21hcmdpbi1sZWZ0OjcyLjBwdDt0ZXh0LWluZGVudDotMTgu MHB0O21zby1saXN0OmwwIGxldmVsMiBsZm8xJz48IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBz dHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYi O2NvbG9yOiMxRjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPmIuPHNwYW4gc3R5 bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5ldyBSb21hbiInPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyA8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9J2ZvbnQt c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0 OTdEJz5SdW4g4oCcL29wdC94ZW5zb3VyY2UvZGVidWcvd2l0aC12ZGkgJmx0O3ZkaXV1aWQmZ3Q7 4oCdIOKAkyB0aGlzIGF0dGFjaGVzIHRoZSBWREkgdG8gZG9tMCBhcyAvZGV2LyRERVZJQ0UgYW5k IGRyb3BzIHlvdSBpbnRvIGEgc2hlbGwg4oCTIGV4aXRpbmcgdGhpcyBzaGVsbCB3aWxsIGRldGFj aCB0aGUgVkRJPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb0xpc3RQYXJhZ3JhcGgg c3R5bGU9J3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEnPjwhW2lm ICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5 OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PHNwYW4gc3R5bGU9J21zby1s aXN0Oklnbm9yZSc+NC48c3BhbiBzdHlsZT0nZm9udDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+ Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFu PjwhW2VuZGlmXT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2Fs aWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPlVzZSAvb3B0L3hlbnNvdXJjZS9saWJl eGVjL3NwYXJzZV9kZCB0byBkZCB0aGUgY29udGVudHMgb2YgdGhlIHJhdyBmaWxlIChmcm9tIHN0 ZXAgMSkgdG8gdGhlIFZESS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTGlzdFBh cmFncmFwaCBzdHlsZT0nbWFyZ2luLWxlZnQ6NzIuMHB0O3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNv LWxpc3Q6bDAgbGV2ZWwyIGxmbzEnPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSdm b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6 I0MwNTA0RCc+PHNwYW4gc3R5bGU9J21zby1saXN0Oklnbm9yZSc+YS48c3BhbiBzdHlsZT0nZm9u dDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0nZm9udC1z aXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5 N0QnPkUuZy4gPC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5 OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6I0MwNTA0RCc+L29wdC94ZW5zb3VyY2UvbGli ZXhlYy9zcGFyc2VfZGQgLXNyYyAvbW50L015Vk0uaW1nIC1kZXN0IC9kZXYvJERFVklDRSAtc2l6 ZSA4NTg5OTM0NTkyIC1wcmV6ZXJvZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNv TGlzdFBhcmFncmFwaCBzdHlsZT0ndGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZl bDEgbGZvMSc+PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4w cHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48c3Bh biBzdHlsZT0nbXNvLWxpc3Q6SWdub3JlJz41LjxzcGFuIHN0eWxlPSdmb250OjcuMHB0ICJUaW1l cyBOZXcgUm9tYW4iJz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPC9zcGFu Pjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2Zv bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+RXhpdCB0aGUg 4oCcd2l0aC12ZGnigJ0gc2hlbGw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9y bWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwi c2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxw IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPknigJl2ZSB0cmllZCB0aGlz IGZvciBhIHhsIFBWIFZNIEkgaGF2ZSBhbmQgaXQgd29ya2VkIChJIHN0YXJ0ZWQgZnJvbSByYXcg aW1hZ2UgcmF0aGVyIHRoYW4gcWNvdzIgc28gc2tpcHBlZCBzdGVwIDEpLiBNeSB0ZXN0IGFsc28g ZGlmZmVycyBpbiB0aGF0IHJvb3QgaXMgb24geHZkYTEgaG93ZXZlciB5b3VyIGNhc2Ugc2hvdWxk IGJlIGZpbmUg4oCTIElJUkMgcHlncnViIGlzIE9LIHdpdGggcm9vdCBvbiB0aGUgcmF3IGRldmlj ZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdm b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6 IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48 c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt c2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkNoZWVycyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xh c3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJD YWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+SmFtZXM8bzpwPjwvbzpwPjwvc3Bh bj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2Zv bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJz cDs8L286cD48L3NwYW4+PC9wPjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv bGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCc+PGRpdj48ZGl2IHN0eWxl PSdib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBw dCAwY20gMGNtIDBjbSc+PHAgY2xhc3M9TXNvTm9ybWFsPjxiPjxzcGFuIGxhbmc9RU4tVVMgc3R5 bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiJz5G cm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtm b250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPiB4ZW4tYXBpLWJvdW5jZXNAbGlzdHMu eGVuLm9yZyBbbWFpbHRvOnhlbi1hcGktYm91bmNlc0BsaXN0cy54ZW4ub3JnXSA8Yj5PbiBCZWhh bGYgT2YgPC9iPkxpbmdmZW5nIFhpb25nPGJyPjxiPlNlbnQ6PC9iPiAyNCBKYW51YXJ5IDIwMTMg MDU6MjU8YnI+PGI+VG86PC9iPiBYZW4tYXBpQGxpc3RzLnhlbi5vcmc8YnI+PGI+U3ViamVjdDo8 L2I+IFtYZW4tQVBJXSBBbnl3YXkgdG8gbWlncmF0ZSBteSBWTSBmcm9tIFhlbiB4bCB0byBYQ1A/ PG86cD48L286cD48L3NwYW4+PC9wPjwvZGl2PjwvZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48bzpw PiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+SGkgYWxsLDxvOnA+PC9vOnA+PC9w PjxkaXY+PHA+SSBhbSBydW5uaW5nIGEgVWJ1bnR1IFNlcnZlciB3aXRoIFhlbiA0LjEgaW5zdGFs bGVkLiBBbGwgVk1zIGFyZSBydW5uaW5nIG9uIHRoYXQgc2VydmVyIHdpdGggb25lIG9yIG1vcmUg dmlydHVhbCBkaXNrcyBzdG9yZWQgaW4gcWNvdzIgZm9ybWF0LiBUaGVzZSBWTXMgYXJlIG1hbmFn ZWQgYnkgJ3hsJyB0b29sc3RhY2suIE9uZSBWTSBpcyBXaW5kb3dzIGluIEhWTSBtb2RlcyBhbmQg b3RoZXJzIGFyZSBQViBWTXMuIFRoZSBxY293MiBmaWxlIGp1c3QgY29udGFpbnMgdGhlIHJvb3Qg ZmlsZXN5c3RlbSBhbmQgaGFzIG5vIHBhcnRpdGlvbiBzdHJ1Y3R1cmVzLjxvOnA+PC9vOnA+PC9w PjxwPk5vdyBJIGluc3RhbGxlZCBhIG5ldyBzZXJ2ZXIgd2l0aCBYQ1AgMS42LiZuYnNwOyBJIGhh dmUgdG8gbWlncmF0ZSBhbGwgVk1zIGZyb20gb2xkIHNlcnZlciB0byBYQ1Agd2l0aCBhbGwgZGF0 YS48bzpwPjwvbzpwPjwvcD48cD5JcyB0aGVyZSBhbnl3YXkgdG8gZG8gdGhpcz88bzpwPjwvbzpw PjwvcD48cD5UaGFua3MgaW4gYWR2YW5jZWQhPG86cD48L286cD48L3A+PC9kaXY+PHAgY2xhc3M9 TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjwvZGl2PjwvZGl2PjwvYm9keT48L2h0bWw+ --_000_344C0F67BC927847A2C92F9EE358DB0E0134C39EF234LONPMAILBOX_-- --===============7639614437799544109== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7639614437799544109==-- From xen-api-bounces@lists.xen.org Thu Jan 24 19:39:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 19:39:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySe6-0005ZG-7z; Thu, 24 Jan 2013 19:39:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySe4-0005Z8-Qp; Thu, 24 Jan 2013 19:39:33 +0000 Received: from [85.158.143.35:29079] by server-1.bemta-4.messagelabs.com id B2/D4-05635-4FD81015; Thu, 24 Jan 2013 19:39:32 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1359056369!13148368!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTgyMzA=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19958 invoked from network); 24 Jan 2013 19:39:31 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 19:39:31 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4730925" Received: from unknown (HELO FTLPEX01CL03.citrite.net) ([10.13.107.80]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 19:39:28 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 14:39:28 -0500 Message-ID: <51018E07.7020000@citrix.com> Date: Thu, 24 Jan 2013 19:39:51 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> <51014CDC.1030501@citrix.com> <1359047667.32057.31.camel@zakaz.uk.xensource.com> In-Reply-To: <1359047667.32057.31.camel@zakaz.uk.xensource.com> X-Originating-IP: [10.80.2.133] Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/01/13 17:14, Ian Campbell wrote: > On Thu, 2013-01-24 at 15:01 +0000, Zoltan Kiss wrote: >> If you would do a suspend, the frontend driver flush out disk IO >> operations before suspend reached, and therefore there won't be anything >> to timeout after resume. > > Actually the behaviour, of Linux blkfront at least, is to not do > anything on suspend but instead to replay the outstanding requests on > the ring on resume. This is to support checkpointing (where you don't > need to replay but I think it is exactly what you want for the driver > domain crash case too. That might be true, sorry, I worked from my faulty memories and haven't checked it again. Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 19:39:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 19:39:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySe6-0005ZG-7z; Thu, 24 Jan 2013 19:39:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySe4-0005Z8-Qp; Thu, 24 Jan 2013 19:39:33 +0000 Received: from [85.158.143.35:29079] by server-1.bemta-4.messagelabs.com id B2/D4-05635-4FD81015; Thu, 24 Jan 2013 19:39:32 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1359056369!13148368!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTgyMzA=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19958 invoked from network); 24 Jan 2013 19:39:31 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 19:39:31 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4730925" Received: from unknown (HELO FTLPEX01CL03.citrite.net) ([10.13.107.80]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 19:39:28 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 14:39:28 -0500 Message-ID: <51018E07.7020000@citrix.com> Date: Thu, 24 Jan 2013 19:39:51 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> <51014CDC.1030501@citrix.com> <1359047667.32057.31.camel@zakaz.uk.xensource.com> In-Reply-To: <1359047667.32057.31.camel@zakaz.uk.xensource.com> X-Originating-IP: [10.80.2.133] Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/01/13 17:14, Ian Campbell wrote: > On Thu, 2013-01-24 at 15:01 +0000, Zoltan Kiss wrote: >> If you would do a suspend, the frontend driver flush out disk IO >> operations before suspend reached, and therefore there won't be anything >> to timeout after resume. > > Actually the behaviour, of Linux blkfront at least, is to not do > anything on suspend but instead to replay the outstanding requests on > the ring on resume. This is to support checkpointing (where you don't > need to replay but I think it is exactly what you want for the driver > domain crash case too. That might be true, sorry, I worked from my faulty memories and haven't checked it again. Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 19:41:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 19:41:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySgH-0005io-Vz; Thu, 24 Jan 2013 19:41:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySgF-0005iS-TA; Thu, 24 Jan 2013 19:41:48 +0000 Received: from [85.158.138.51:11377] by server-11.bemta-3.messagelabs.com id 03/19-09112-67E81015; Thu, 24 Jan 2013 19:41:42 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1359056500!21403780!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTY4ODk=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12907 invoked from network); 24 Jan 2013 19:41:41 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 19:41:41 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4984285" Received: from unknown (HELO FTLPEX01CL03.citrite.net) ([10.13.107.80]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 19:41:39 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 14:41:39 -0500 Message-ID: <51018E8A.8020708@citrix.com> Date: Thu, 24 Jan 2013 19:42:02 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andrew Cooper References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> <51014CDC.1030501@citrix.com> <51014EF9.5040502@citrix.com> In-Reply-To: <51014EF9.5040502@citrix.com> X-Originating-IP: [10.80.2.133] Cc: "'xen-devel@lists.xen.org'" , "xen-api@lists.xen.org" , Ian Campbell Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/01/13 15:10, Andrew Cooper wrote: >> If you would do a suspend, the frontend driver flush out disk IO >> >operations before suspend reached, and therefore there won't be anything >> >to timeout after resume. However, if the storage driver domain just >> >crashed, I guess the guest would crash at suspend. Maybe we can try out >> >something to save the the ring buffer, and replay them back once the >> >backend come back (but before resuming the guest). But I'm not sure >> >whether the guest would handle the timeouts after the resume first, or >> >cancel them if the requests were succesfully responded. >> > >> >Zoli > Perhaps I am making this harder, but might it be best to wait for a > short while (15-30 seconds) for the device driver domain to come back, > and if it takes longer than that, pause the VM. > > This way, if the driver domain is fast to come back, all the guest > notices is transitorily blocked IO, and if the driver domain is too slow > (but does come back), all the guest might notices is a pause. > > Ultimately, if the driver domain never comes back, then we are in a no > worse position than currently. As Paul mentioned, pausing doesn't cause the guest to reconnect to the new backend, so you would need a suspend/resume. But in George's case, where the driver domain remains the same, this can work. However to avoid George's problem with timeouts, a reconnect should be necessary. As Ian mentioned, the guest will replay the ring and that might help to avoid the timouts to happen. Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 19:41:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 19:41:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySgH-0005io-Vz; Thu, 24 Jan 2013 19:41:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySgF-0005iS-TA; Thu, 24 Jan 2013 19:41:48 +0000 Received: from [85.158.138.51:11377] by server-11.bemta-3.messagelabs.com id 03/19-09112-67E81015; Thu, 24 Jan 2013 19:41:42 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1359056500!21403780!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTY4ODk=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12907 invoked from network); 24 Jan 2013 19:41:41 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 19:41:41 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4984285" Received: from unknown (HELO FTLPEX01CL03.citrite.net) ([10.13.107.80]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 19:41:39 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 14:41:39 -0500 Message-ID: <51018E8A.8020708@citrix.com> Date: Thu, 24 Jan 2013 19:42:02 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andrew Cooper References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <51011EF5.9080708@gmail.com> <291EDFCB1E9E224A99088639C4762022013F451DCB22@LONPMAILBOX01.citrite.net> <51013FED.60201@gmail.com> <51014CDC.1030501@citrix.com> <51014EF9.5040502@citrix.com> In-Reply-To: <51014EF9.5040502@citrix.com> X-Originating-IP: [10.80.2.133] Cc: "'xen-devel@lists.xen.org'" , "xen-api@lists.xen.org" , Ian Campbell Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/01/13 15:10, Andrew Cooper wrote: >> If you would do a suspend, the frontend driver flush out disk IO >> >operations before suspend reached, and therefore there won't be anything >> >to timeout after resume. However, if the storage driver domain just >> >crashed, I guess the guest would crash at suspend. Maybe we can try out >> >something to save the the ring buffer, and replay them back once the >> >backend come back (but before resuming the guest). But I'm not sure >> >whether the guest would handle the timeouts after the resume first, or >> >cancel them if the requests were succesfully responded. >> > >> >Zoli > Perhaps I am making this harder, but might it be best to wait for a > short while (15-30 seconds) for the device driver domain to come back, > and if it takes longer than that, pause the VM. > > This way, if the driver domain is fast to come back, all the guest > notices is transitorily blocked IO, and if the driver domain is too slow > (but does come back), all the guest might notices is a pause. > > Ultimately, if the driver domain never comes back, then we are in a no > worse position than currently. As Paul mentioned, pausing doesn't cause the guest to reconnect to the new backend, so you would need a suspend/resume. But in George's case, where the driver domain remains the same, this can work. However to avoid George's problem with timeouts, a reconnect should be necessary. As Ian mentioned, the guest will replay the ring and that might help to avoid the timouts to happen. Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 19:51:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 19:51:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySq0-00063Z-DA; Thu, 24 Jan 2013 19:51:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySpz-00063R-21; Thu, 24 Jan 2013 19:51:51 +0000 Received: from [85.158.139.211:10597] by server-2.bemta-5.messagelabs.com id E5/90-17076-4D091015; Thu, 24 Jan 2013 19:51:48 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1359057106!19568836!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTgyMzA=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27907 invoked from network); 24 Jan 2013 19:51:47 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 19:51:47 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4732780" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 19:51:28 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 14:51:28 -0500 Message-ID: <510190D7.9080304@citrix.com> Date: Thu, 24 Jan 2013 19:51:51 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <1359021585.17440.93.camel@zakaz.uk.xensource.com> In-Reply-To: <1359021585.17440.93.camel@zakaz.uk.xensource.com> X-Originating-IP: [10.80.2.133] Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/01/13 09:59, Ian Campbell wrote: >> Actually I've used the xc_domain_resume_any() function from libxc to >> resume the guests. It worked with PV guests, however with some hacks in >> the hypervisor to silently discarding the error condicions, and not >> returning from the hypercall with an error. The two guests I've used, >> and their problems with the hypercall return values: >> >> - SLES 11 SP1 (2.6.32.12) crashes because VCPUOP_register_vcpu_info >> hypercall returns EINVAL, as ( v->arch.vcpu_info_mfn != INVALID_MFN ) >> - Debian Squeeze 6.0 (2.6.32-5) crashes because EVTCHNOP_bind_virq >> returns EEXISTS, as ( v->virq_to_evtchnvirq != 0 ) >> - (these hypercalls were made right after guest comes back from the >> suspend hypercall) > > The toolstack might need to do EVTCHNOP_reset or do some other cleanup? Yep, that might be an another solution, to reset these values from toolstack via hypercall(s), but as far as I checked all the current hypercalls which are changing these things, doing a lot of other stuff which we not necessarily want. So it might be necessary to define a new hypercall specifically for this use-case. Probably it's easier than make Xen aware that a suspend/resume happened, and the guest remained in the same domain. > Pausing guests when one of their supporting driver domains goes away > does seem like a good idea. > > I suppose the flip side is that a domain which isn't using a disk which > goes away briefly would see a hiccup it wouldn't have otherwise seen. Well, I think it would be quite complicated to watch the ring buffer for activities while there is no backend connected. I would say this is an acceptable loss. Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Jan 24 19:51:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 24 Jan 2013 19:51:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySq0-00063Z-DA; Thu, 24 Jan 2013 19:51:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TySpz-00063R-21; Thu, 24 Jan 2013 19:51:51 +0000 Received: from [85.158.139.211:10597] by server-2.bemta-5.messagelabs.com id E5/90-17076-4D091015; Thu, 24 Jan 2013 19:51:48 +0000 X-Env-Sender: zoltan.kiss@citrix.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1359057106!19568836!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTgyMzA=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27907 invoked from network); 24 Jan 2013 19:51:47 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jan 2013 19:51:47 -0000 X-IronPort-AV: E=Sophos;i="4.84,530,1355097600"; d="scan'208";a="4732780" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 Jan 2013 19:51:28 +0000 Received: from [10.80.2.133] (10.80.2.133) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Thu, 24 Jan 2013 14:51:28 -0500 Message-ID: <510190D7.9080304@citrix.com> Date: Thu, 24 Jan 2013 19:51:51 +0000 From: Zoltan Kiss User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <81A73678E76EA642801C8F2E4823AD21014183065D27@LONPMAILBOX01.citrite.net> <1358770844.3279.194.camel@zakaz.uk.xensource.com> <51005CF8.402@citrix.com> <1359021585.17440.93.camel@zakaz.uk.xensource.com> In-Reply-To: <1359021585.17440.93.camel@zakaz.uk.xensource.com> X-Originating-IP: [10.80.2.133] Cc: "xen-api@lists.xen.org" , "'xen-devel@lists.xen.org'" Subject: Re: [Xen-API] [Xen-devel] driver domain crash and reconnect handling X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/01/13 09:59, Ian Campbell wrote: >> Actually I've used the xc_domain_resume_any() function from libxc to >> resume the guests. It worked with PV guests, however with some hacks in >> the hypervisor to silently discarding the error condicions, and not >> returning from the hypercall with an error. The two guests I've used, >> and their problems with the hypercall return values: >> >> - SLES 11 SP1 (2.6.32.12) crashes because VCPUOP_register_vcpu_info >> hypercall returns EINVAL, as ( v->arch.vcpu_info_mfn != INVALID_MFN ) >> - Debian Squeeze 6.0 (2.6.32-5) crashes because EVTCHNOP_bind_virq >> returns EEXISTS, as ( v->virq_to_evtchnvirq != 0 ) >> - (these hypercalls were made right after guest comes back from the >> suspend hypercall) > > The toolstack might need to do EVTCHNOP_reset or do some other cleanup? Yep, that might be an another solution, to reset these values from toolstack via hypercall(s), but as far as I checked all the current hypercalls which are changing these things, doing a lot of other stuff which we not necessarily want. So it might be necessary to define a new hypercall specifically for this use-case. Probably it's easier than make Xen aware that a suspend/resume happened, and the guest remained in the same domain. > Pausing guests when one of their supporting driver domains goes away > does seem like a good idea. > > I suppose the flip side is that a domain which isn't using a disk which > goes away briefly would see a hiccup it wouldn't have otherwise seen. Well, I think it would be quite complicated to watch the ring buffer for activities while there is no backend connected. I would say this is an acceptable loss. Zoli _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 25 08:01:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 25 Jan 2013 08:01:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyeDx-0002jw-PH; Fri, 25 Jan 2013 08:01:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyeDw-0002jr-8u for xen-api@lists.xen.org; Fri, 25 Jan 2013 08:01:20 +0000 Received: from [85.158.143.99:60493] by server-2.bemta-4.messagelabs.com id C5/70-03518-FCB32015; Fri, 25 Jan 2013 08:01:19 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-5.tower-216.messagelabs.com!1359100872!27879492!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13619 invoked from network); 25 Jan 2013 08:01:18 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-5.tower-216.messagelabs.com with SMTP; 25 Jan 2013 08:01:18 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d06 with ME id s81C1k00C3zjds10381CNF; Fri, 25 Jan 2013 09:01:12 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id F0BCE161BB4; Fri, 25 Jan 2013 09:01:11 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkXClYYDcBOu; Fri, 25 Jan 2013 09:01:11 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 34BA7161BBA; Fri, 25 Jan 2013 09:01:11 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 0IdrXY8SAMUL; Fri, 25 Jan 2013 09:01:10 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 81C6C161BB4; Fri, 25 Jan 2013 09:01:10 +0100 (CET) Message-ID: <51023BC6.1030209@tranquil-it-systems.fr> Date: Fri, 25 Jan 2013 09:01:10 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Lingfeng Xiong References: In-Reply-To: Cc: Xen-api@lists.xen.org Subject: =?iso-8859-1?q?Re=3A_=5BXen-API=5D_Anyway_to_migrate_my_VM_from_?= =?iso-8859-1?q?=10Xen_xl_to_XCP=3F?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Lingfeng, > I am running a Ubuntu Server with Xen 4.1 installed. All VMs are running > on that server with one or more virtual disks stored in qcow2 format. > These VMs are managed by 'xl' toolstack. One VM is Windows in HVM modes > and others are PV VMs. The qcow2 file just contains the root filesystem > and has no partition structures. > > Now I installed a new server with XCP 1.6. I have to migrate all VMs > from old server to XCP with all data. > > Is there anyway to do this? I usually go with rsync if the linux VM is not too exotic or too old = (otherwise just go with James path). You just prepare a linux VM on XCP with the same version/arch as the one = you have on your old server. Then you just use rsync on the new VM to do = the transfert, something like : rsync --numeric-ids --delete-after --exclude "/proc/**" --exclude = "/sys/**" --exclude "/dev/**" --exclude "/etc/inittab" --exclude = "/etc/fstab" --exclude "/boot/**" --exclude "/lib/modules/** " -aPz = root@old-ip:/ / Then you may have to clean up your old mac in the udev rules if necessary. This method has the advantage of being able to run the rsync multiple = times, and the final switch on the new server and the corresponding = downtime can be minimized. Note : you'll have to turn off the running = services before last rsync. Cheers, Denis > > Thanks in advanced! > > > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Jan 25 08:01:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 25 Jan 2013 08:01:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyeDx-0002jw-PH; Fri, 25 Jan 2013 08:01:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyeDw-0002jr-8u for xen-api@lists.xen.org; Fri, 25 Jan 2013 08:01:20 +0000 Received: from [85.158.143.99:60493] by server-2.bemta-4.messagelabs.com id C5/70-03518-FCB32015; Fri, 25 Jan 2013 08:01:19 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-5.tower-216.messagelabs.com!1359100872!27879492!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13619 invoked from network); 25 Jan 2013 08:01:18 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-5.tower-216.messagelabs.com with SMTP; 25 Jan 2013 08:01:18 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d06 with ME id s81C1k00C3zjds10381CNF; Fri, 25 Jan 2013 09:01:12 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id F0BCE161BB4; Fri, 25 Jan 2013 09:01:11 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkXClYYDcBOu; Fri, 25 Jan 2013 09:01:11 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 34BA7161BBA; Fri, 25 Jan 2013 09:01:11 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 0IdrXY8SAMUL; Fri, 25 Jan 2013 09:01:10 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 81C6C161BB4; Fri, 25 Jan 2013 09:01:10 +0100 (CET) Message-ID: <51023BC6.1030209@tranquil-it-systems.fr> Date: Fri, 25 Jan 2013 09:01:10 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Lingfeng Xiong References: In-Reply-To: Cc: Xen-api@lists.xen.org Subject: =?iso-8859-1?q?Re=3A_=5BXen-API=5D_Anyway_to_migrate_my_VM_from_?= =?iso-8859-1?q?=10Xen_xl_to_XCP=3F?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Lingfeng, > I am running a Ubuntu Server with Xen 4.1 installed. All VMs are running > on that server with one or more virtual disks stored in qcow2 format. > These VMs are managed by 'xl' toolstack. One VM is Windows in HVM modes > and others are PV VMs. The qcow2 file just contains the root filesystem > and has no partition structures. > > Now I installed a new server with XCP 1.6. I have to migrate all VMs > from old server to XCP with all data. > > Is there anyway to do this? I usually go with rsync if the linux VM is not too exotic or too old = (otherwise just go with James path). You just prepare a linux VM on XCP with the same version/arch as the one = you have on your old server. Then you just use rsync on the new VM to do = the transfert, something like : rsync --numeric-ids --delete-after --exclude "/proc/**" --exclude = "/sys/**" --exclude "/dev/**" --exclude "/etc/inittab" --exclude = "/etc/fstab" --exclude "/boot/**" --exclude "/lib/modules/** " -aPz = root@old-ip:/ / Then you may have to clean up your old mac in the udev rules if necessary. This method has the advantage of being able to run the rsync multiple = times, and the final switch on the new server and the corresponding = downtime can be minimized. Note : you'll have to turn off the running = services before last rsync. Cheers, Denis > > Thanks in advanced! > > > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Jan 26 07:50:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 26 Jan 2013 07:50:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tz0WW-0002zZ-97; Sat, 26 Jan 2013 07:50:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tz0WU-0002zU-No for Xen-api@lists.xen.org; Sat, 26 Jan 2013 07:49:59 +0000 Received: from [85.158.143.99:11164] by server-3.bemta-4.messagelabs.com id 0D/7A-10689-5AA83015; Sat, 26 Jan 2013 07:49:57 +0000 X-Env-Sender: jilingshu@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1359186595!19953204!1 X-Originating-IP: [209.85.220.41] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19755 invoked from network); 26 Jan 2013 07:49:56 -0000 Received: from mail-pa0-f41.google.com (HELO mail-pa0-f41.google.com) (209.85.220.41) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 26 Jan 2013 07:49:56 -0000 Received: by mail-pa0-f41.google.com with SMTP id bj3so675578pad.28 for ; Fri, 25 Jan 2013 23:49:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=H1u68DyI6Ue6O/E7WUBfg3sI/yK+H/rgmpWIycp9KGg=; b=IYudDHEfNZlPReudHeotC54kaH2wgj+EaTzJCBClkT/k+LcLCut4SM3eUS2e4h9Kz2 bSFT41NYW2PFxxWycBmgXsbNGKclnLAZDQVwnhqaj7IDxByI81AE4i3lPPAi+PfhpfJ6 jXKpaMVzUFJ7X6Ovty6Nfl7BgQiJDz8B4GQfkZ/VHUA4VCxBcnpgeemDtYXnTy2qk3Lt pXS/YuuqdiMl46iK9un+cszA7YXa791UffeO1qdny+GDU/U6Kf/jujuyS/prN7SoqjvW bsAoHu14SA0vVHi9F0zlxUqj9cohO0AvVGge3Kb9T4L+VVaoq6NNdgphUeFEumfY4fS+ c2Lw== X-Received: by 10.68.233.196 with SMTP id ty4mr20781509pbc.23.1359186594857; Fri, 25 Jan 2013 23:49:54 -0800 (PST) Received: from [192.168.1.4] ([182.148.111.122]) by mx.google.com with ESMTPS id a4sm2430438paw.21.2013.01.25.23.49.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Jan 2013 23:49:53 -0800 (PST) Message-ID: <51038A90.6080600@Gmail.com> Date: Sat, 26 Jan 2013 15:49:36 +0800 From: Bear User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: James Bulpin References: <344C0F67BC927847A2C92F9EE358DB0E0134C39EF234@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E0134C39EF234@LONPMAILBOX01.citrite.net> Cc: "Xen-api@lists.xen.org" Subject: =?iso-8859-1?q?Re=3A_=5BXen-API=5D_Anyway_to_migrate_my_VM_from_?= =?iso-8859-1?q?=10Xen_xl_to_XCP=3F?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGkgSmFtZXMsIFRvcnN0ZW4gYW5kIERlbmlzLApUaGFua3MgYWxsIG9mIHlvdSBmb3IgeW91ciBr aW5kbHkgcmVwbHkhCkkganVzdCB1c2Ugc29tZSBsaXR0bGUgdHJpY2tzIHRvIGVhc2lseSBtaWdy YXRlZCBteSBWTXMuIEJlZm9yZSBJIApkZXNjcmliZSBteSBzb2x1dGlvbiwgaGVyZSdzIG15IG9s ZCB4bCBWTXMnIGNvbmZpZ3VyYXRpb25zOgoKMS4gQWxsIExpbnV4IFZNJ3MgYXJlIFBWIFZNIChu b3QgcHlncnViKS4gVGhleSBhcmUgcnVubmluZyB1bmRlciAKb2xkLWZhc2hpb24ga2VybmVsL2lu aXRyYW1mcy9yb290ZnMgY29uZmlndXJhdGlvbgoyLiBPbmUgV2luZG93cyBWTSBpcyBhIEhWTSBn dWVzdCB3aXRoIEdOVSBQViBkcml2ZXJzIGluc3RhbGxlZC4KMy4gTmV3IFhDUCBTUiBpcyBjcmVh dGVkIGFzIE5GUyBWSEQuCgpBbmQgdGhlIHNvbHV0aW9ucyBpczoKMS4gQ29udmVydCBxY293MiBp bWFnZSB0byBWSEQgZmlsZXMgd2l0aApxZW11LWltZyBjb252ZXJ0IHh4eHh4LnFjb3cyIC1PIHZw YyB4eHh4eC52aGQKMi4gQ3JlYXRlIGEgVk0gd2l0aCBzYW1lIG9yIHNpbWlsYXIgT1MgdGVtcGxh dGVzIGluIFhlbkNlbnRlciBvciAKZGlyZWN0bHkgaW4gWENQLiBEb24ndCBib290IGl0LgozLiBR dWVyeSB0aGUgY29ycmVzcG9uZGluZyBWREkgZm9yIHRoZSBWTSB5b3UganVzdCBjcmVhdGVkCjQu IEluIE5GUyBTUiwgcmVwbGFjZSB0aGUge1ZESS1VVUlEfS52aGQgd2l0aCB0aGUgeHh4eHgudmhk IHlvdSBqdXN0IApjb252ZXJ0ZWQKNS4gRm9yIEhWTSBndWVzdCwganVzdCBib290IGl0IGZyb20g WGVuQ2VudGVyL1hDUC4gRm9yIFBWIGd1ZXN0cywgc3NoIAppbnRvIERvbTAgYW5kIGNvbmZpZ3Vy ZSBjb3JyZWN0IFBWLWtlcm5lbCBhbmQgUFYtcmFtZGlzay4KNS4gQm9vdCB0aGUgVk0gaW4gWGVu Q2VudGVyL1hDUC4KCkkganVzdCB1c2UgdGhpcyBtZXRob2QgdG8gbWlncmF0ZSBhbGwgbXkgVk1z IHRvIG15IG5ldyBYQ1Agc2VydmVyIDotKQoKQnV0IGl0IGNvbWVzIHNvbWUgaW50ZXJlc3Rpbmcg cHJvYmxlbXMuLi4KMS4gQWxsIFBWIFZNJ3MgY29uc29sZXMgYXJlIGluYWNjZXNzaWJsZS4gSSBj YW4gc3NoIGludG8gdGhvc2UgVk1zLCBidXQgCmluIFhlbkNlbnRlcidzIGNvbnNvbGUgcGFnZSwg aXQganVzdCBmcm96ZW4gd2hlbiBpdCBib290ZWQuIFRoZSBsYXN0IApsaW5lcyBJIGNhbiBzZWUg YXJlOgoKID4gTG9hZGluZywgcGxlYXNlIHdhaXQuLi4KID4gWyAgICAwLjM4MDE3OV0gdWRldmRb ODVdOiBzdGFydGluZyB2ZXJzaW9uIDE3NQogPiBCZWdpbjogTG9hZGluZyBlc3NlbnRpYWwgZHJp dmVycyAuLi4gZG9uZS4KID4gQmVnaW46IFJ1bm5pbmcgL3NjcmlwdHMvaW5pdC1wcmVtb3VudCAu Li4gZG9uZS4KID4gQmVnaW46IE1vdW50aW5nIHJvb3QgZmlsZSBzeXN0ZW0gLi4uIEJlZ2luOiBS dW5uaW5nIAovc2NyaXB0cy9sb2NhbC10b3AgLi4uIGRvbmUuCiA+IEJlZ2luOiBSdW5uaW5nIC9z Y3JpcHRzL2xvY2FsLXByZW1vdW50IC4uLiBkb25lLgogPiBbICAgIDUuNTM4MjE2XSBFWFQ0LWZz ICh4dmRhKTogbW91bnRlZCBmaWxlc3lzdGVtIHdpdGggb3JkZXJlZCBkYXRhIAptb2RlLiBPcHRz OiAobnVsbCkKID4gQmVnaW46IFJ1bm5pbmcgL3NjcmlwdHMvbG9jYWwtYm90dG9tIC4uLiBkb25l LgogPiBkb25lLgogPiBCZWdpbjogUnVubmluZyAvc2NyaXB0cy9pbml0LWJvdHRvbSAuLi4gZG9u ZS4KID4gbW91bnRhbGw6IERpc2Nvbm5lY3RlZCBmcm9tIFBseW1vdXRoCgpJIGNhbiBuZWl0aGVy IHNlZSB0aGUgbG9naW4gcHJvbXB0IG5vciB0eXBlIGluIGFueXRoaW5nIGludG8gY29uc29sZS4K CjIuIFRoZSBIVk0gV2luZG93cyBTZXJ2ZXIgMjAxMiBndWVzdCBzaG93IEJTT0QgZHVyaW5nIGJv b3RpbmcuIEkgY2Fubm90IAplbnRlciB0aGUgc3lzdGVtIGNvbXBsZXRlbHkuLi4gOi0oCgpIb3Bl IHlvdSBndXlzIGNhbiBnaXZlIG1lIHNvbWUgY2x1ZXMuLgpUaGFua3MgaW4gYWR2YW5jZWQuCgpP biAxLzI1LzIwMTMgMTozMiBBTSwgSmFtZXMgQnVscGluIHdyb3RlOgo+IE9uZSB3YXkgd291bGQg YmUgdG8sIGZvciBlYWNoIFZNOgo+Cj4gMS4gICAgICAgQ29udmVydCBlYWNoIHFjb3cyIGZpbGUg dG8gYSByYXcgZmlsZSB1c2luZyBxY293MnJhdyDigJMgcHV0IHRoZXNlIGZpbGVzIHNvbWV3aGVy ZSAoZS5nLiBhIE5GUyBleHBvcnQpIHdoZXJlIHlvdSBjYW4gdGVtcG9yYXJpbHkgcmVhY2ggdGhl bSBmcm9tIFhDUOKAmXMgZG9tYWluMAo+Cj4gMi4gICAgICAgVXNpbmcgWENQIOKAnGluc3RhbGzi gJ0gYSBWTSB1c2luZyB0aGUgbW9zdCBzdWl0YWJsZSB0ZW1wbGF0ZSBidXQgbm90IGFjdHVhbGx5 IHN0YXJ0aW5nIHRoZSBWTSBvciBnb2luZyB0aHJvdWdoIHRoZSBpbnN0YWxsLiBNYWtlIHN1cmUg dG8gY2hvb3NlIHZpcnR1YWwgZGlzayBzaXplcyBhdCBsZWFzdCBhcyBiaWcgYXMgdGhlIHZpcnR1 YWwgc2l6ZSBvZiB0aGUgb3JpZ2luYWwgcWNvdzIgb25lcy4gU2V0IHZpcnR1YWwgTklDIE1BQyBh ZGRyZXNzZXMgdG8gbWF0Y2ggeW91ciB4bCBWTS4gIEZvciBQViB5b3XigJlsbCBuZWVkIHRvIHRy aWNrIFhDUCBpbnRvIHRoaW5raW5nIHlvdeKAmXZlIGNvbXBsZXRlZCB0aGUgaW5zdGFsbCBieQo+ Cj4gYS4gICAgICAgY2hhbmdpbmcgUFYtYm9vdGxvYWRlciB0byBweWdydWIgKHhlIHZtLXBhcmFt LXNldCB1dWlkPTx2bXV1aWQ+IFBWLWJvb3Rsb2FkZXI9cHlncnViKQo+Cj4gYi4gICAgICBtYWtp bmcgdGhlIGZpcnN0IFZCRCBib290YWJsZSAoeGUgdmJkLXBhcmFtLXNldCB1dWlkPSQoeGUgdmJk LWxpc3Qgdm0tdXVpZD08dm11dWlkPiB1c2VyZGV2aWNlPTAgLS1taW5pbWFsKSBib290YWJsZT10 cnVlKQo+Cj4gYy4gICAgICAgbWFraW5nIHRoZSB2aXJ0dWFsIENEIGRyaXZlIChpZiBwcmVzZW50 KSBub3QgYm9vdGFibGU6ICh4ZSB2YmQtcGFyYW0tc2V0IHV1aWQ9JCh4ZSB2YmQtbGlzdCB2bS11 dWlkPTx2bXV1aWQ+IHR5cGU9Q0QgLS1taW5pbWFsKSBib290YWJsZT1mYWxzZSkKPgo+IDMuICAg ICAgIE9uZSBieSBvbmUgYXR0YWNoIHRoZSBWTeKAmXMgdmlydHVhbCBkaXNrcyB0byBkb20wIOKA kyBteSBwcmVmZXJyZWQgd2F5IGlzIHRvOgo+Cj4gYS4gICAgICAgRmluZCB0aGUgVkRJ4oCZcyBV VUlEIGJ5IHVzaW5nIOKAnHhlIHZtLWRpc2stbGlzdCB1dWlkPTx2bXV1aWQ+4oCdIOKAkyBsb29r IGZvciBlLmcuIOKAnERpc2sgMCBWREnigJ0KPgo+IGIuICAgICAgUnVuIOKAnC9vcHQveGVuc291 cmNlL2RlYnVnL3dpdGgtdmRpIDx2ZGl1dWlkPuKAnSDigJMgdGhpcyBhdHRhY2hlcyB0aGUgVkRJ IHRvIGRvbTAgYXMgL2Rldi8kREVWSUNFIGFuZCBkcm9wcyB5b3UgaW50byBhIHNoZWxsIOKAkyBl eGl0aW5nIHRoaXMgc2hlbGwgd2lsbCBkZXRhY2ggdGhlIFZESQo+Cj4gNC4gICAgICAgVXNlIC9v cHQveGVuc291cmNlL2xpYmV4ZWMvc3BhcnNlX2RkIHRvIGRkIHRoZSBjb250ZW50cyBvZiB0aGUg cmF3IGZpbGUgKGZyb20gc3RlcCAxKSB0byB0aGUgVkRJLgo+Cj4gYS4gICAgICAgRS5nLiAvb3B0 L3hlbnNvdXJjZS9saWJleGVjL3NwYXJzZV9kZCAtc3JjIC9tbnQvTXlWTS5pbWcgLWRlc3QgL2Rl di8kREVWSUNFIC1zaXplIDg1ODk5MzQ1OTIgLXByZXplcm9lZAo+Cj4gNS4gICAgICAgRXhpdCB0 aGUg4oCcd2l0aC12ZGnigJ0gc2hlbGwKPgo+IEnigJl2ZSB0cmllZCB0aGlzIGZvciBhIHhsIFBW IFZNIEkgaGF2ZSBhbmQgaXQgd29ya2VkIChJIHN0YXJ0ZWQgZnJvbSByYXcgaW1hZ2UgcmF0aGVy IHRoYW4gcWNvdzIgc28gc2tpcHBlZCBzdGVwIDEpLiBNeSB0ZXN0IGFsc28gZGlmZmVycyBpbiB0 aGF0IHJvb3QgaXMgb24geHZkYTEgaG93ZXZlciB5b3VyIGNhc2Ugc2hvdWxkIGJlIGZpbmUg4oCT IElJUkMgcHlncnViIGlzIE9LIHdpdGggcm9vdCBvbiB0aGUgcmF3IGRldmljZS4KPgo+IENoZWVy cywKPiBKYW1lcwo+Cj4gRnJvbTogeGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmcgW21haWx0 bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gT24gQmVoYWxmIE9mIExpbmdmZW5nIFhp b25nCj4gU2VudDogMjQgSmFudWFyeSAyMDEzIDA1OjI1Cj4gVG86IFhlbi1hcGlAbGlzdHMueGVu Lm9yZwo+IFN1YmplY3Q6IFtYZW4tQVBJXSBBbnl3YXkgdG8gbWlncmF0ZSBteSBWTSBmcm9tIFhl biB4bCB0byBYQ1A/Cj4KPiBIaSBhbGwsCj4KPiBJIGFtIHJ1bm5pbmcgYSBVYnVudHUgU2VydmVy IHdpdGggWGVuIDQuMSBpbnN0YWxsZWQuIEFsbCBWTXMgYXJlIHJ1bm5pbmcgb24gdGhhdCBzZXJ2 ZXIgd2l0aCBvbmUgb3IgbW9yZSB2aXJ0dWFsIGRpc2tzIHN0b3JlZCBpbiBxY293MiBmb3JtYXQu IFRoZXNlIFZNcyBhcmUgbWFuYWdlZCBieSAneGwnIHRvb2xzdGFjay4gT25lIFZNIGlzIFdpbmRv d3MgaW4gSFZNIG1vZGVzIGFuZCBvdGhlcnMgYXJlIFBWIFZNcy4gVGhlIHFjb3cyIGZpbGUganVz dCBjb250YWlucyB0aGUgcm9vdCBmaWxlc3lzdGVtIGFuZCBoYXMgbm8gcGFydGl0aW9uIHN0cnVj dHVyZXMuCj4KPiBOb3cgSSBpbnN0YWxsZWQgYSBuZXcgc2VydmVyIHdpdGggWENQIDEuNi4gIEkg aGF2ZSB0byBtaWdyYXRlIGFsbCBWTXMgZnJvbSBvbGQgc2VydmVyIHRvIFhDUCB3aXRoIGFsbCBk YXRhLgo+Cj4gSXMgdGhlcmUgYW55d2F5IHRvIGRvIHRoaXM/Cj4KPiBUaGFua3MgaW4gYWR2YW5j ZWQhCj4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVu Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Sat Jan 26 07:50:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 26 Jan 2013 07:50:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tz0WW-0002zZ-97; Sat, 26 Jan 2013 07:50:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tz0WU-0002zU-No for Xen-api@lists.xen.org; Sat, 26 Jan 2013 07:49:59 +0000 Received: from [85.158.143.99:11164] by server-3.bemta-4.messagelabs.com id 0D/7A-10689-5AA83015; Sat, 26 Jan 2013 07:49:57 +0000 X-Env-Sender: jilingshu@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1359186595!19953204!1 X-Originating-IP: [209.85.220.41] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19755 invoked from network); 26 Jan 2013 07:49:56 -0000 Received: from mail-pa0-f41.google.com (HELO mail-pa0-f41.google.com) (209.85.220.41) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 26 Jan 2013 07:49:56 -0000 Received: by mail-pa0-f41.google.com with SMTP id bj3so675578pad.28 for ; Fri, 25 Jan 2013 23:49:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=H1u68DyI6Ue6O/E7WUBfg3sI/yK+H/rgmpWIycp9KGg=; b=IYudDHEfNZlPReudHeotC54kaH2wgj+EaTzJCBClkT/k+LcLCut4SM3eUS2e4h9Kz2 bSFT41NYW2PFxxWycBmgXsbNGKclnLAZDQVwnhqaj7IDxByI81AE4i3lPPAi+PfhpfJ6 jXKpaMVzUFJ7X6Ovty6Nfl7BgQiJDz8B4GQfkZ/VHUA4VCxBcnpgeemDtYXnTy2qk3Lt pXS/YuuqdiMl46iK9un+cszA7YXa791UffeO1qdny+GDU/U6Kf/jujuyS/prN7SoqjvW bsAoHu14SA0vVHi9F0zlxUqj9cohO0AvVGge3Kb9T4L+VVaoq6NNdgphUeFEumfY4fS+ c2Lw== X-Received: by 10.68.233.196 with SMTP id ty4mr20781509pbc.23.1359186594857; Fri, 25 Jan 2013 23:49:54 -0800 (PST) Received: from [192.168.1.4] ([182.148.111.122]) by mx.google.com with ESMTPS id a4sm2430438paw.21.2013.01.25.23.49.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Jan 2013 23:49:53 -0800 (PST) Message-ID: <51038A90.6080600@Gmail.com> Date: Sat, 26 Jan 2013 15:49:36 +0800 From: Bear User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: James Bulpin References: <344C0F67BC927847A2C92F9EE358DB0E0134C39EF234@LONPMAILBOX01.citrite.net> In-Reply-To: <344C0F67BC927847A2C92F9EE358DB0E0134C39EF234@LONPMAILBOX01.citrite.net> Cc: "Xen-api@lists.xen.org" Subject: =?iso-8859-1?q?Re=3A_=5BXen-API=5D_Anyway_to_migrate_my_VM_from_?= =?iso-8859-1?q?=10Xen_xl_to_XCP=3F?= X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org SGkgSmFtZXMsIFRvcnN0ZW4gYW5kIERlbmlzLApUaGFua3MgYWxsIG9mIHlvdSBmb3IgeW91ciBr aW5kbHkgcmVwbHkhCkkganVzdCB1c2Ugc29tZSBsaXR0bGUgdHJpY2tzIHRvIGVhc2lseSBtaWdy YXRlZCBteSBWTXMuIEJlZm9yZSBJIApkZXNjcmliZSBteSBzb2x1dGlvbiwgaGVyZSdzIG15IG9s ZCB4bCBWTXMnIGNvbmZpZ3VyYXRpb25zOgoKMS4gQWxsIExpbnV4IFZNJ3MgYXJlIFBWIFZNIChu b3QgcHlncnViKS4gVGhleSBhcmUgcnVubmluZyB1bmRlciAKb2xkLWZhc2hpb24ga2VybmVsL2lu aXRyYW1mcy9yb290ZnMgY29uZmlndXJhdGlvbgoyLiBPbmUgV2luZG93cyBWTSBpcyBhIEhWTSBn dWVzdCB3aXRoIEdOVSBQViBkcml2ZXJzIGluc3RhbGxlZC4KMy4gTmV3IFhDUCBTUiBpcyBjcmVh dGVkIGFzIE5GUyBWSEQuCgpBbmQgdGhlIHNvbHV0aW9ucyBpczoKMS4gQ29udmVydCBxY293MiBp bWFnZSB0byBWSEQgZmlsZXMgd2l0aApxZW11LWltZyBjb252ZXJ0IHh4eHh4LnFjb3cyIC1PIHZw YyB4eHh4eC52aGQKMi4gQ3JlYXRlIGEgVk0gd2l0aCBzYW1lIG9yIHNpbWlsYXIgT1MgdGVtcGxh dGVzIGluIFhlbkNlbnRlciBvciAKZGlyZWN0bHkgaW4gWENQLiBEb24ndCBib290IGl0LgozLiBR dWVyeSB0aGUgY29ycmVzcG9uZGluZyBWREkgZm9yIHRoZSBWTSB5b3UganVzdCBjcmVhdGVkCjQu IEluIE5GUyBTUiwgcmVwbGFjZSB0aGUge1ZESS1VVUlEfS52aGQgd2l0aCB0aGUgeHh4eHgudmhk IHlvdSBqdXN0IApjb252ZXJ0ZWQKNS4gRm9yIEhWTSBndWVzdCwganVzdCBib290IGl0IGZyb20g WGVuQ2VudGVyL1hDUC4gRm9yIFBWIGd1ZXN0cywgc3NoIAppbnRvIERvbTAgYW5kIGNvbmZpZ3Vy ZSBjb3JyZWN0IFBWLWtlcm5lbCBhbmQgUFYtcmFtZGlzay4KNS4gQm9vdCB0aGUgVk0gaW4gWGVu Q2VudGVyL1hDUC4KCkkganVzdCB1c2UgdGhpcyBtZXRob2QgdG8gbWlncmF0ZSBhbGwgbXkgVk1z IHRvIG15IG5ldyBYQ1Agc2VydmVyIDotKQoKQnV0IGl0IGNvbWVzIHNvbWUgaW50ZXJlc3Rpbmcg cHJvYmxlbXMuLi4KMS4gQWxsIFBWIFZNJ3MgY29uc29sZXMgYXJlIGluYWNjZXNzaWJsZS4gSSBj YW4gc3NoIGludG8gdGhvc2UgVk1zLCBidXQgCmluIFhlbkNlbnRlcidzIGNvbnNvbGUgcGFnZSwg aXQganVzdCBmcm96ZW4gd2hlbiBpdCBib290ZWQuIFRoZSBsYXN0IApsaW5lcyBJIGNhbiBzZWUg YXJlOgoKID4gTG9hZGluZywgcGxlYXNlIHdhaXQuLi4KID4gWyAgICAwLjM4MDE3OV0gdWRldmRb ODVdOiBzdGFydGluZyB2ZXJzaW9uIDE3NQogPiBCZWdpbjogTG9hZGluZyBlc3NlbnRpYWwgZHJp dmVycyAuLi4gZG9uZS4KID4gQmVnaW46IFJ1bm5pbmcgL3NjcmlwdHMvaW5pdC1wcmVtb3VudCAu Li4gZG9uZS4KID4gQmVnaW46IE1vdW50aW5nIHJvb3QgZmlsZSBzeXN0ZW0gLi4uIEJlZ2luOiBS dW5uaW5nIAovc2NyaXB0cy9sb2NhbC10b3AgLi4uIGRvbmUuCiA+IEJlZ2luOiBSdW5uaW5nIC9z Y3JpcHRzL2xvY2FsLXByZW1vdW50IC4uLiBkb25lLgogPiBbICAgIDUuNTM4MjE2XSBFWFQ0LWZz ICh4dmRhKTogbW91bnRlZCBmaWxlc3lzdGVtIHdpdGggb3JkZXJlZCBkYXRhIAptb2RlLiBPcHRz OiAobnVsbCkKID4gQmVnaW46IFJ1bm5pbmcgL3NjcmlwdHMvbG9jYWwtYm90dG9tIC4uLiBkb25l LgogPiBkb25lLgogPiBCZWdpbjogUnVubmluZyAvc2NyaXB0cy9pbml0LWJvdHRvbSAuLi4gZG9u ZS4KID4gbW91bnRhbGw6IERpc2Nvbm5lY3RlZCBmcm9tIFBseW1vdXRoCgpJIGNhbiBuZWl0aGVy IHNlZSB0aGUgbG9naW4gcHJvbXB0IG5vciB0eXBlIGluIGFueXRoaW5nIGludG8gY29uc29sZS4K CjIuIFRoZSBIVk0gV2luZG93cyBTZXJ2ZXIgMjAxMiBndWVzdCBzaG93IEJTT0QgZHVyaW5nIGJv b3RpbmcuIEkgY2Fubm90IAplbnRlciB0aGUgc3lzdGVtIGNvbXBsZXRlbHkuLi4gOi0oCgpIb3Bl IHlvdSBndXlzIGNhbiBnaXZlIG1lIHNvbWUgY2x1ZXMuLgpUaGFua3MgaW4gYWR2YW5jZWQuCgpP biAxLzI1LzIwMTMgMTozMiBBTSwgSmFtZXMgQnVscGluIHdyb3RlOgo+IE9uZSB3YXkgd291bGQg YmUgdG8sIGZvciBlYWNoIFZNOgo+Cj4gMS4gICAgICAgQ29udmVydCBlYWNoIHFjb3cyIGZpbGUg dG8gYSByYXcgZmlsZSB1c2luZyBxY293MnJhdyDigJMgcHV0IHRoZXNlIGZpbGVzIHNvbWV3aGVy ZSAoZS5nLiBhIE5GUyBleHBvcnQpIHdoZXJlIHlvdSBjYW4gdGVtcG9yYXJpbHkgcmVhY2ggdGhl bSBmcm9tIFhDUOKAmXMgZG9tYWluMAo+Cj4gMi4gICAgICAgVXNpbmcgWENQIOKAnGluc3RhbGzi gJ0gYSBWTSB1c2luZyB0aGUgbW9zdCBzdWl0YWJsZSB0ZW1wbGF0ZSBidXQgbm90IGFjdHVhbGx5 IHN0YXJ0aW5nIHRoZSBWTSBvciBnb2luZyB0aHJvdWdoIHRoZSBpbnN0YWxsLiBNYWtlIHN1cmUg dG8gY2hvb3NlIHZpcnR1YWwgZGlzayBzaXplcyBhdCBsZWFzdCBhcyBiaWcgYXMgdGhlIHZpcnR1 YWwgc2l6ZSBvZiB0aGUgb3JpZ2luYWwgcWNvdzIgb25lcy4gU2V0IHZpcnR1YWwgTklDIE1BQyBh ZGRyZXNzZXMgdG8gbWF0Y2ggeW91ciB4bCBWTS4gIEZvciBQViB5b3XigJlsbCBuZWVkIHRvIHRy aWNrIFhDUCBpbnRvIHRoaW5raW5nIHlvdeKAmXZlIGNvbXBsZXRlZCB0aGUgaW5zdGFsbCBieQo+ Cj4gYS4gICAgICAgY2hhbmdpbmcgUFYtYm9vdGxvYWRlciB0byBweWdydWIgKHhlIHZtLXBhcmFt LXNldCB1dWlkPTx2bXV1aWQ+IFBWLWJvb3Rsb2FkZXI9cHlncnViKQo+Cj4gYi4gICAgICBtYWtp bmcgdGhlIGZpcnN0IFZCRCBib290YWJsZSAoeGUgdmJkLXBhcmFtLXNldCB1dWlkPSQoeGUgdmJk LWxpc3Qgdm0tdXVpZD08dm11dWlkPiB1c2VyZGV2aWNlPTAgLS1taW5pbWFsKSBib290YWJsZT10 cnVlKQo+Cj4gYy4gICAgICAgbWFraW5nIHRoZSB2aXJ0dWFsIENEIGRyaXZlIChpZiBwcmVzZW50 KSBub3QgYm9vdGFibGU6ICh4ZSB2YmQtcGFyYW0tc2V0IHV1aWQ9JCh4ZSB2YmQtbGlzdCB2bS11 dWlkPTx2bXV1aWQ+IHR5cGU9Q0QgLS1taW5pbWFsKSBib290YWJsZT1mYWxzZSkKPgo+IDMuICAg ICAgIE9uZSBieSBvbmUgYXR0YWNoIHRoZSBWTeKAmXMgdmlydHVhbCBkaXNrcyB0byBkb20wIOKA kyBteSBwcmVmZXJyZWQgd2F5IGlzIHRvOgo+Cj4gYS4gICAgICAgRmluZCB0aGUgVkRJ4oCZcyBV VUlEIGJ5IHVzaW5nIOKAnHhlIHZtLWRpc2stbGlzdCB1dWlkPTx2bXV1aWQ+4oCdIOKAkyBsb29r IGZvciBlLmcuIOKAnERpc2sgMCBWREnigJ0KPgo+IGIuICAgICAgUnVuIOKAnC9vcHQveGVuc291 cmNlL2RlYnVnL3dpdGgtdmRpIDx2ZGl1dWlkPuKAnSDigJMgdGhpcyBhdHRhY2hlcyB0aGUgVkRJ IHRvIGRvbTAgYXMgL2Rldi8kREVWSUNFIGFuZCBkcm9wcyB5b3UgaW50byBhIHNoZWxsIOKAkyBl eGl0aW5nIHRoaXMgc2hlbGwgd2lsbCBkZXRhY2ggdGhlIFZESQo+Cj4gNC4gICAgICAgVXNlIC9v cHQveGVuc291cmNlL2xpYmV4ZWMvc3BhcnNlX2RkIHRvIGRkIHRoZSBjb250ZW50cyBvZiB0aGUg cmF3IGZpbGUgKGZyb20gc3RlcCAxKSB0byB0aGUgVkRJLgo+Cj4gYS4gICAgICAgRS5nLiAvb3B0 L3hlbnNvdXJjZS9saWJleGVjL3NwYXJzZV9kZCAtc3JjIC9tbnQvTXlWTS5pbWcgLWRlc3QgL2Rl di8kREVWSUNFIC1zaXplIDg1ODk5MzQ1OTIgLXByZXplcm9lZAo+Cj4gNS4gICAgICAgRXhpdCB0 aGUg4oCcd2l0aC12ZGnigJ0gc2hlbGwKPgo+IEnigJl2ZSB0cmllZCB0aGlzIGZvciBhIHhsIFBW IFZNIEkgaGF2ZSBhbmQgaXQgd29ya2VkIChJIHN0YXJ0ZWQgZnJvbSByYXcgaW1hZ2UgcmF0aGVy IHRoYW4gcWNvdzIgc28gc2tpcHBlZCBzdGVwIDEpLiBNeSB0ZXN0IGFsc28gZGlmZmVycyBpbiB0 aGF0IHJvb3QgaXMgb24geHZkYTEgaG93ZXZlciB5b3VyIGNhc2Ugc2hvdWxkIGJlIGZpbmUg4oCT IElJUkMgcHlncnViIGlzIE9LIHdpdGggcm9vdCBvbiB0aGUgcmF3IGRldmljZS4KPgo+IENoZWVy cywKPiBKYW1lcwo+Cj4gRnJvbTogeGVuLWFwaS1ib3VuY2VzQGxpc3RzLnhlbi5vcmcgW21haWx0 bzp4ZW4tYXBpLWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gT24gQmVoYWxmIE9mIExpbmdmZW5nIFhp b25nCj4gU2VudDogMjQgSmFudWFyeSAyMDEzIDA1OjI1Cj4gVG86IFhlbi1hcGlAbGlzdHMueGVu Lm9yZwo+IFN1YmplY3Q6IFtYZW4tQVBJXSBBbnl3YXkgdG8gbWlncmF0ZSBteSBWTSBmcm9tIFhl biB4bCB0byBYQ1A/Cj4KPiBIaSBhbGwsCj4KPiBJIGFtIHJ1bm5pbmcgYSBVYnVudHUgU2VydmVy IHdpdGggWGVuIDQuMSBpbnN0YWxsZWQuIEFsbCBWTXMgYXJlIHJ1bm5pbmcgb24gdGhhdCBzZXJ2 ZXIgd2l0aCBvbmUgb3IgbW9yZSB2aXJ0dWFsIGRpc2tzIHN0b3JlZCBpbiBxY293MiBmb3JtYXQu IFRoZXNlIFZNcyBhcmUgbWFuYWdlZCBieSAneGwnIHRvb2xzdGFjay4gT25lIFZNIGlzIFdpbmRv d3MgaW4gSFZNIG1vZGVzIGFuZCBvdGhlcnMgYXJlIFBWIFZNcy4gVGhlIHFjb3cyIGZpbGUganVz dCBjb250YWlucyB0aGUgcm9vdCBmaWxlc3lzdGVtIGFuZCBoYXMgbm8gcGFydGl0aW9uIHN0cnVj dHVyZXMuCj4KPiBOb3cgSSBpbnN0YWxsZWQgYSBuZXcgc2VydmVyIHdpdGggWENQIDEuNi4gIEkg aGF2ZSB0byBtaWdyYXRlIGFsbCBWTXMgZnJvbSBvbGQgc2VydmVyIHRvIFhDUCB3aXRoIGFsbCBk YXRhLgo+Cj4gSXMgdGhlcmUgYW55d2F5IHRvIGRvIHRoaXM/Cj4KPiBUaGFua3MgaW4gYWR2YW5j ZWQhCj4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVu Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Sat Jan 26 17:12:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 26 Jan 2013 17:12:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tz9Iu-0007MQ-Un; Sat, 26 Jan 2013 17:12:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tz8MI-0006ss-Ps for Xen-api@lists.xen.org; Sat, 26 Jan 2013 16:11:58 +0000 Received: from [85.158.139.211:27425] by server-11.bemta-5.messagelabs.com id 94/EF-07660-E4004015; Sat, 26 Jan 2013 16:11:58 +0000 X-Env-Sender: jgreenlee@mail2web.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1359216716!18317559!1 X-Originating-IP: [168.144.250.247] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTY4LjE0NC4yNTAuMjQ3ID0+IDExOTM2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32455 invoked from network); 26 Jan 2013 16:11:57 -0000 Received: from xsmtp28.mail2web.com (HELO xsmtp08.mail2web.com) (168.144.250.247) by server-9.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 26 Jan 2013 16:11:57 -0000 Received: from [10.5.31.9] (helo=hub03.ad2.softcom.biz) by xsmtp08.mail2web.com with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.63) (envelope-from ) id 1Tz8ME-0006JT-HU for Xen-api@lists.xen.org; Sat, 26 Jan 2013 11:11:54 -0500 Received: from MBX81.ad2.softcom.biz ([10.5.13.49]) by hub03.ad2.softcom.biz ([10.5.31.9]) with mapi; Sat, 26 Jan 2013 11:11:53 -0500 From: James To: "Xen-api@lists.xen.org" Date: Sat, 26 Jan 2013 11:11:52 -0500 Thread-Topic: Disaster Recovery of Xen XCP. Thread-Index: AQHN+9/aB7D5DOIk8UmPrFjb29V6ew== Message-ID: <39F8F0A9F90D5C48A847177B56A22567015B80045B6D@MBX81.ad2.softcom.biz> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 26 Jan 2013 17:12:32 +0000 Subject: [Xen-API] Disaster Recovery of Xen XCP. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Over the past couple of weeks I've installed XCP onto a USB stick and have built up my virtual data-center. Now it would appear that the USB stick is failing and I would like to recover rather than rebuild. The good: This first showed up last night and I was able to shut down my VMs (at least partially) and power cycle the server to get XCP back up and running. Also good (I think) all of the VMs and their related storage is hosted from a hardware RAID controller. Whether I install another USB stick or use a normal hard drive, the issue is the same: How do I get my VM's recognized on a new install of XCP? If I recall correctly, when I created the RAID array as a storage repository for XCP, it warned me that all contents would be lost. However I don't think I need to "create" the SR...I just need to "import" the SR and then "import" the VM's. With that in mind...Surely there's an "export" option somewhere in XCP?? Thanks, James _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Jan 26 17:12:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 26 Jan 2013 17:12:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tz9Iu-0007MQ-Un; Sat, 26 Jan 2013 17:12:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tz8MI-0006ss-Ps for Xen-api@lists.xen.org; Sat, 26 Jan 2013 16:11:58 +0000 Received: from [85.158.139.211:27425] by server-11.bemta-5.messagelabs.com id 94/EF-07660-E4004015; Sat, 26 Jan 2013 16:11:58 +0000 X-Env-Sender: jgreenlee@mail2web.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1359216716!18317559!1 X-Originating-IP: [168.144.250.247] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTY4LjE0NC4yNTAuMjQ3ID0+IDExOTM2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32455 invoked from network); 26 Jan 2013 16:11:57 -0000 Received: from xsmtp28.mail2web.com (HELO xsmtp08.mail2web.com) (168.144.250.247) by server-9.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 26 Jan 2013 16:11:57 -0000 Received: from [10.5.31.9] (helo=hub03.ad2.softcom.biz) by xsmtp08.mail2web.com with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.63) (envelope-from ) id 1Tz8ME-0006JT-HU for Xen-api@lists.xen.org; Sat, 26 Jan 2013 11:11:54 -0500 Received: from MBX81.ad2.softcom.biz ([10.5.13.49]) by hub03.ad2.softcom.biz ([10.5.31.9]) with mapi; Sat, 26 Jan 2013 11:11:53 -0500 From: James To: "Xen-api@lists.xen.org" Date: Sat, 26 Jan 2013 11:11:52 -0500 Thread-Topic: Disaster Recovery of Xen XCP. Thread-Index: AQHN+9/aB7D5DOIk8UmPrFjb29V6ew== Message-ID: <39F8F0A9F90D5C48A847177B56A22567015B80045B6D@MBX81.ad2.softcom.biz> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 26 Jan 2013 17:12:32 +0000 Subject: [Xen-API] Disaster Recovery of Xen XCP. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Over the past couple of weeks I've installed XCP onto a USB stick and have built up my virtual data-center. Now it would appear that the USB stick is failing and I would like to recover rather than rebuild. The good: This first showed up last night and I was able to shut down my VMs (at least partially) and power cycle the server to get XCP back up and running. Also good (I think) all of the VMs and their related storage is hosted from a hardware RAID controller. Whether I install another USB stick or use a normal hard drive, the issue is the same: How do I get my VM's recognized on a new install of XCP? If I recall correctly, when I created the RAID array as a storage repository for XCP, it warned me that all contents would be lost. However I don't think I need to "create" the SR...I just need to "import" the SR and then "import" the VM's. With that in mind...Surely there's an "export" option somewhere in XCP?? Thanks, James _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 27 19:34:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 27 Jan 2013 19:34:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzXzG-0000aP-HY; Sun, 27 Jan 2013 19:33:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzXzF-0000aK-7k for xen-api@lists.xen.org; Sun, 27 Jan 2013 19:33:53 +0000 Received: from [85.158.137.99:63947] by server-7.bemta-3.messagelabs.com id B2/51-07262-02185015; Sun, 27 Jan 2013 19:33:52 +0000 X-Env-Sender: john@axioshost.net X-Msg-Ref: server-9.tower-217.messagelabs.com!1359315184!15577775!1 X-Originating-IP: [165.254.7.197] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11619 invoked from network); 27 Jan 2013 19:33:51 -0000 Received: from mx1.peer9.net (HELO mail.peer9.net) (165.254.7.197) by server-9.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 27 Jan 2013 19:33:51 -0000 Received: from MAIL.peer9.net ([fe80::2c00:73b9:3af7:bb36]) by mail.peer9.net ([fe80::2c00:73b9:3af7:bb36%12]) with mapi; Sun, 27 Jan 2013 14:31:01 -0500 From: John Koffler To: "xen-api@lists.xen.org" Thread-Topic: SR content-type Thread-Index: AQHN/MTWpZxQPVTapEGx07pIEOFUHQ== Date: Sun, 27 Jan 2013 19:26:10 +0000 Message-ID: <1048A8D3B689A14496E7B490017693F20A7D0951@mail.peer9.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 Subject: [Xen-API] SR content-type X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello all, Forgive me if this has been covered before. I'm using XCP 1.6 and a provisioning utility that interacts with the hypervisor. One thing I have noticed is that under any new SR's I create in the Xencenter UI, the content-type parameter is blank. As far as I am aware, there is no way to update this, other than to remove the SR and re-introduce it. Is this a change in Xencenter 6.X? See my list below, Local Storage 2 was attached using HBAs on the system, but the content-type was never set. Bug or did I do something wrong? I tried to do a param update, but its a RO field, so no go. Thanks all. Here is the output of my sr-list: uuid ( RO): c734ce2d-1545-880c-5677-cc4f5ab2913a name-label ( RW): Local storage name-description ( RW): host ( RO): IMS000B5Xen type ( RO): lvm content-type ( RO): user uuid ( RO): 72592cf7-8064-c980-75cf-daf944656f25 name-label ( RW): Local storage 2 on IMS000B5Xen name-description ( RW): Hardware HBA SR [Intel - /dev/sdq [sdr]] host ( RO): IMS000B5Xen type ( RO): lvmohba content-type ( RO): uuid ( RO): 8f0799c4-55c4-6cf3-25cb-ccb0a27d03e3 name-label ( RW): XenServer Tools name-description ( RW): XenServer Tools ISOs host ( RO): IMS000B5Xen type ( RO): iso content-type ( RO): iso _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 27 19:34:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 27 Jan 2013 19:34:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzXzG-0000aP-HY; Sun, 27 Jan 2013 19:33:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzXzF-0000aK-7k for xen-api@lists.xen.org; Sun, 27 Jan 2013 19:33:53 +0000 Received: from [85.158.137.99:63947] by server-7.bemta-3.messagelabs.com id B2/51-07262-02185015; Sun, 27 Jan 2013 19:33:52 +0000 X-Env-Sender: john@axioshost.net X-Msg-Ref: server-9.tower-217.messagelabs.com!1359315184!15577775!1 X-Originating-IP: [165.254.7.197] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11619 invoked from network); 27 Jan 2013 19:33:51 -0000 Received: from mx1.peer9.net (HELO mail.peer9.net) (165.254.7.197) by server-9.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 27 Jan 2013 19:33:51 -0000 Received: from MAIL.peer9.net ([fe80::2c00:73b9:3af7:bb36]) by mail.peer9.net ([fe80::2c00:73b9:3af7:bb36%12]) with mapi; Sun, 27 Jan 2013 14:31:01 -0500 From: John Koffler To: "xen-api@lists.xen.org" Thread-Topic: SR content-type Thread-Index: AQHN/MTWpZxQPVTapEGx07pIEOFUHQ== Date: Sun, 27 Jan 2013 19:26:10 +0000 Message-ID: <1048A8D3B689A14496E7B490017693F20A7D0951@mail.peer9.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 Subject: [Xen-API] SR content-type X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello all, Forgive me if this has been covered before. I'm using XCP 1.6 and a provisioning utility that interacts with the hypervisor. One thing I have noticed is that under any new SR's I create in the Xencenter UI, the content-type parameter is blank. As far as I am aware, there is no way to update this, other than to remove the SR and re-introduce it. Is this a change in Xencenter 6.X? See my list below, Local Storage 2 was attached using HBAs on the system, but the content-type was never set. Bug or did I do something wrong? I tried to do a param update, but its a RO field, so no go. Thanks all. Here is the output of my sr-list: uuid ( RO): c734ce2d-1545-880c-5677-cc4f5ab2913a name-label ( RW): Local storage name-description ( RW): host ( RO): IMS000B5Xen type ( RO): lvm content-type ( RO): user uuid ( RO): 72592cf7-8064-c980-75cf-daf944656f25 name-label ( RW): Local storage 2 on IMS000B5Xen name-description ( RW): Hardware HBA SR [Intel - /dev/sdq [sdr]] host ( RO): IMS000B5Xen type ( RO): lvmohba content-type ( RO): uuid ( RO): 8f0799c4-55c4-6cf3-25cb-ccb0a27d03e3 name-label ( RW): XenServer Tools name-description ( RW): XenServer Tools ISOs host ( RO): IMS000B5Xen type ( RO): iso content-type ( RO): iso _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sun Jan 27 20:18:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 27 Jan 2013 20:18:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzYft-0000v9-Uf; Sun, 27 Jan 2013 20:17:57 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TzYfs-0000v4-Q7 for Xen-api@lists.xen.org; Sun, 27 Jan 2013 20:17:56 +0000 Received: from [193.109.254.147:46378] by server-13.bemta-14.messagelabs.com id 51/F3-19158-47B85015; Sun, 27 Jan 2013 20:17:56 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1359317874!10336681!1 X-Originating-IP: [209.85.216.41] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6999 invoked from network); 27 Jan 2013 20:17:55 -0000 Received: from mail-qa0-f41.google.com (HELO mail-qa0-f41.google.com) (209.85.216.41) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jan 2013 20:17:55 -0000 Received: by mail-qa0-f41.google.com with SMTP id hy16so600998qab.14 for ; Sun, 27 Jan 2013 12:17:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1rVKptmZmL9ZWtDx9EcX0EslBMQ9r4i/6ye5jbSc9q0=; b=RllOjkFZGXjID8JY2IOIvuwc59tmr1qx2YTPcK1uhIe81KkfIZo1LIfOKwReJ9Zk20 hP/9zwlQ6d9CYVLF48ytjNLGgYZBOcfUWnN3iLkyol3kDq5Y/u4RdHyzDa+AkdMEpNoE pkrRLvuO65nzZe9ciXA7kSbINGO2Er1beK5w3X04U8jwADgbt9BldsFS7tQKXcMGDBGu ypjYmmscI2uyqUpRNh6+1FgfkMj9C9vyXiBQATdfH4pANt9e3qXZLEMHbvJFbyuIT5SN UBCS0wHb/5H8kohaGKQzNLHlgfRf4j5proDBmBRBWQRdmwyyfLfgxj2Bceaw8taOeLXS OeKQ== MIME-Version: 1.0 X-Received: by 10.229.203.28 with SMTP id fg28mr3237316qcb.103.1359317873837; Sun, 27 Jan 2013 12:17:53 -0800 (PST) Received: by 10.229.131.81 with HTTP; Sun, 27 Jan 2013 12:17:53 -0800 (PST) In-Reply-To: <50FD2930.9010207@unity.pl> References: <50FD2930.9010207@unity.pl> Date: Mon, 28 Jan 2013 01:47:53 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: =?ISO-8859-2?Q?=A3ukasz_Nowak?= Cc: Xen-api@lists.xen.org Subject: Re: [Xen-API] XCP online resize vdi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2479859182768646747==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2479859182768646747== Content-Type: multipart/alternative; boundary=0050450166f501c53204d44adbb5 --0050450166f501c53204d44adbb5 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable On Mon, Jan 21, 2013 at 5:10 PM, =A3ukasz Nowak wro= te: > Hi, > how can I increase VDI space online? > > Do you mean that the VM is online while you do VDI size increase ? You can increase the VDI size if the VM is OFFLINE or VDI is not attached to any VM but while VM is online, resize is not yet possible. > > I tried: > [root@usyqaxc01 ~]# xe vdi-resize disk-size=3D2147493648 > uuid=3D9575d076-97a5-48ab-b1e0-d890053ee8ef online=3Dtrue > The SR backend does not support the operation (check the SR's allowed > operations) > sr: fa93343e-7be0-73da-c019-310d2edbb3da (iscsi - sdm) > > > My SR type is: lvmoiscsi > XCP 1.6 > > Linux distribution in the vm is debian. I have installed > xe-guest-utilities on the vm. > > [root@usyqaxc01 ~]# xe vdi-param-list > uuid=3D9575d076-97a5-48ab-b1e0-d890053ee8ef | grep allowed operations > > > allowed-operations (SRO): clone; snapshot > > [root@usyqaxc01 ~]# xe sr-param-list > uuid=3Dfa93343e-7be0-73da-c019-310d2edbb3da|grep allowed-operations > allowed-operations (SRO): VDI.create; VDI.snapshot; PBD.create; > PBD.destroy; plug; update; VDI.destroy; scan; VDI.clone; VDI.resize; unpl= ug > > > > > Best regards, > -- > =A3ukasz Nowak > Administrator System=F3w Unix > GSM: +48 603 992 558 | lukasz.nowak@contium.pl > JABBER: lukasz.nowak@contium.pl > > Grupa Unity | ul. Przedmiejska 6-10, 54-201 Wroc=B3aw > ul. Conrada 55B, 31-357 Krak=F3w | ul. Z=B3ota 59, 00-120 Warszawa > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --0050450166f501c53204d44adbb5 Content-Type: text/html; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable

On Mon, Jan 21, 2013 at 5:10 PM, =A3ukas= z Nowak <lukasz.nowak@unity.pl> wrote:
Hi,
how can I increase VDI space online?


Do you mean that the VM is online while you do VD= I size increase ?
You can increase the VDI size if the VM is OFFLINE or = VDI is not attached to any VM but while VM is online, resize is not yet pos= sible.

=A0

I tried:
[root@usyqaxc01 ~]# xe vdi-resize disk-size=3D2147493648
uuid=3D9575d076-97a5-48ab-b1e0-d890053ee8ef online=3Dtrue
The SR backend does not support the operation (check the SR's allowed operations)
sr: fa93343e-7be0-73da-c019-310d2edbb3da (iscsi - sdm)


My SR type is: lvmoiscsi
XCP 1.6

Linux distribution in the vm is debian. I have installed
xe-guest-utilities on the vm.

[root@usyqaxc01 ~]# xe vdi-param-list
uuid=3D9575d076-97a5-48ab-b1e0-d890053ee8ef | grep allowed operations


=A0 =A0 =A0 allowed-operations (SRO): clone; snapshot

[root@usyqaxc01 ~]# xe sr-param-list
uuid=3Dfa93343e-7be0-73da-c019-310d2edbb3da|grep allowed-operations
=A0 =A0 =A0 allowed-operations (SRO): VDI.create; VDI.snapshot; PBD.create;=
PBD.destroy; plug; update; VDI.destroy; scan; VDI.clone; VDI.resize; unplug=




Best regards,
--
=A3ukasz Nowak
Administrator System=F3w Unix
GSM: +48 603 992 558 | lukasz.no= wak@contium.pl
JABBER: lukasz.nowak@contium.pl<= /a>

Grupa Unity | ul. Przedmiejska 6-10, 54-201 Wroc=B3aw
ul. Conrada 55B, 31-357 Krak=F3w | ul. Z=B3ota 59, 00-120 Warszawa


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--0050450166f501c53204d44adbb5-- --===============2479859182768646747== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2479859182768646747==-- From xen-api-bounces@lists.xen.org Sun Jan 27 20:18:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 27 Jan 2013 20:18:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzYft-0000v9-Uf; Sun, 27 Jan 2013 20:17:57 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1TzYfs-0000v4-Q7 for Xen-api@lists.xen.org; Sun, 27 Jan 2013 20:17:56 +0000 Received: from [193.109.254.147:46378] by server-13.bemta-14.messagelabs.com id 51/F3-19158-47B85015; Sun, 27 Jan 2013 20:17:56 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1359317874!10336681!1 X-Originating-IP: [209.85.216.41] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6999 invoked from network); 27 Jan 2013 20:17:55 -0000 Received: from mail-qa0-f41.google.com (HELO mail-qa0-f41.google.com) (209.85.216.41) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jan 2013 20:17:55 -0000 Received: by mail-qa0-f41.google.com with SMTP id hy16so600998qab.14 for ; Sun, 27 Jan 2013 12:17:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1rVKptmZmL9ZWtDx9EcX0EslBMQ9r4i/6ye5jbSc9q0=; b=RllOjkFZGXjID8JY2IOIvuwc59tmr1qx2YTPcK1uhIe81KkfIZo1LIfOKwReJ9Zk20 hP/9zwlQ6d9CYVLF48ytjNLGgYZBOcfUWnN3iLkyol3kDq5Y/u4RdHyzDa+AkdMEpNoE pkrRLvuO65nzZe9ciXA7kSbINGO2Er1beK5w3X04U8jwADgbt9BldsFS7tQKXcMGDBGu ypjYmmscI2uyqUpRNh6+1FgfkMj9C9vyXiBQATdfH4pANt9e3qXZLEMHbvJFbyuIT5SN UBCS0wHb/5H8kohaGKQzNLHlgfRf4j5proDBmBRBWQRdmwyyfLfgxj2Bceaw8taOeLXS OeKQ== MIME-Version: 1.0 X-Received: by 10.229.203.28 with SMTP id fg28mr3237316qcb.103.1359317873837; Sun, 27 Jan 2013 12:17:53 -0800 (PST) Received: by 10.229.131.81 with HTTP; Sun, 27 Jan 2013 12:17:53 -0800 (PST) In-Reply-To: <50FD2930.9010207@unity.pl> References: <50FD2930.9010207@unity.pl> Date: Mon, 28 Jan 2013 01:47:53 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: =?ISO-8859-2?Q?=A3ukasz_Nowak?= Cc: Xen-api@lists.xen.org Subject: Re: [Xen-API] XCP online resize vdi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2479859182768646747==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2479859182768646747== Content-Type: multipart/alternative; boundary=0050450166f501c53204d44adbb5 --0050450166f501c53204d44adbb5 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable On Mon, Jan 21, 2013 at 5:10 PM, =A3ukasz Nowak wro= te: > Hi, > how can I increase VDI space online? > > Do you mean that the VM is online while you do VDI size increase ? You can increase the VDI size if the VM is OFFLINE or VDI is not attached to any VM but while VM is online, resize is not yet possible. > > I tried: > [root@usyqaxc01 ~]# xe vdi-resize disk-size=3D2147493648 > uuid=3D9575d076-97a5-48ab-b1e0-d890053ee8ef online=3Dtrue > The SR backend does not support the operation (check the SR's allowed > operations) > sr: fa93343e-7be0-73da-c019-310d2edbb3da (iscsi - sdm) > > > My SR type is: lvmoiscsi > XCP 1.6 > > Linux distribution in the vm is debian. I have installed > xe-guest-utilities on the vm. > > [root@usyqaxc01 ~]# xe vdi-param-list > uuid=3D9575d076-97a5-48ab-b1e0-d890053ee8ef | grep allowed operations > > > allowed-operations (SRO): clone; snapshot > > [root@usyqaxc01 ~]# xe sr-param-list > uuid=3Dfa93343e-7be0-73da-c019-310d2edbb3da|grep allowed-operations > allowed-operations (SRO): VDI.create; VDI.snapshot; PBD.create; > PBD.destroy; plug; update; VDI.destroy; scan; VDI.clone; VDI.resize; unpl= ug > > > > > Best regards, > -- > =A3ukasz Nowak > Administrator System=F3w Unix > GSM: +48 603 992 558 | lukasz.nowak@contium.pl > JABBER: lukasz.nowak@contium.pl > > Grupa Unity | ul. Przedmiejska 6-10, 54-201 Wroc=B3aw > ul. Conrada 55B, 31-357 Krak=F3w | ul. Z=B3ota 59, 00-120 Warszawa > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --0050450166f501c53204d44adbb5 Content-Type: text/html; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable

On Mon, Jan 21, 2013 at 5:10 PM, =A3ukas= z Nowak <lukasz.nowak@unity.pl> wrote:
Hi,
how can I increase VDI space online?


Do you mean that the VM is online while you do VD= I size increase ?
You can increase the VDI size if the VM is OFFLINE or = VDI is not attached to any VM but while VM is online, resize is not yet pos= sible.

=A0

I tried:
[root@usyqaxc01 ~]# xe vdi-resize disk-size=3D2147493648
uuid=3D9575d076-97a5-48ab-b1e0-d890053ee8ef online=3Dtrue
The SR backend does not support the operation (check the SR's allowed operations)
sr: fa93343e-7be0-73da-c019-310d2edbb3da (iscsi - sdm)


My SR type is: lvmoiscsi
XCP 1.6

Linux distribution in the vm is debian. I have installed
xe-guest-utilities on the vm.

[root@usyqaxc01 ~]# xe vdi-param-list
uuid=3D9575d076-97a5-48ab-b1e0-d890053ee8ef | grep allowed operations


=A0 =A0 =A0 allowed-operations (SRO): clone; snapshot

[root@usyqaxc01 ~]# xe sr-param-list
uuid=3Dfa93343e-7be0-73da-c019-310d2edbb3da|grep allowed-operations
=A0 =A0 =A0 allowed-operations (SRO): VDI.create; VDI.snapshot; PBD.create;=
PBD.destroy; plug; update; VDI.destroy; scan; VDI.clone; VDI.resize; unplug=




Best regards,
--
=A3ukasz Nowak
Administrator System=F3w Unix
GSM: +48 603 992 558 | lukasz.no= wak@contium.pl
JABBER: lukasz.nowak@contium.pl<= /a>

Grupa Unity | ul. Przedmiejska 6-10, 54-201 Wroc=B3aw
ul. Conrada 55B, 31-357 Krak=F3w | ul. Z=B3ota 59, 00-120 Warszawa


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--0050450166f501c53204d44adbb5-- --===============2479859182768646747== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2479859182768646747==-- From xen-api-bounces@lists.xen.org Sun Jan 27 22:03:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 27 Jan 2013 22:03:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzaJl-00029R-E7; Sun, 27 Jan 2013 22:03:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzaJk-00029M-ED for xen-api@lists.xen.org; Sun, 27 Jan 2013 22:03:12 +0000 Received: from [85.158.143.99:50736] by server-3.bemta-4.messagelabs.com id 50/7E-10689-F14A5015; Sun, 27 Jan 2013 22:03:11 +0000 X-Env-Sender: jb@bw-networx.net X-Msg-Ref: server-3.tower-216.messagelabs.com!1359324190!29106272!1 X-Originating-IP: [178.63.214.118] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28834 invoked from network); 27 Jan 2013 22:03:10 -0000 Received: from mail.bw-networx.net (HELO mail.bw-networx.net) (178.63.214.118) by server-3.tower-216.messagelabs.com with SMTP; 27 Jan 2013 22:03:10 -0000 Received: from [10.0.10.105] (HSI-KBW-5-10-51-43.hsi18.kabel-badenwuerttemberg.de [5.10.51.43]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.bw-networx.net (Postfix) with ESMTPSA id 8595E6B3383 for ; Sun, 27 Jan 2013 23:03:10 +0100 (CET) From: Joern Bredereck Message-Id: <89FC82A6-DE26-4263-A1A0-42BC02FC7E32@bw-networx.net> Date: Sun, 27 Jan 2013 23:03:09 +0100 To: xen-api@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Subject: [Xen-API] No Keystrokes in XenCenter with HVM guests X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2569101740726017054==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2569101740726017054== Content-Type: multipart/signed; boundary="Apple-Mail=_86FA9168-0839-4D23-87FA-1AE1B3060A5E"; protocol="application/pkcs7-signature"; micalg=sha1 --Apple-Mail=_86FA9168-0839-4D23-87FA-1AE1B3060A5E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, it looks like my problem is already known: http://lists.xen.org/archives/html/xen-api/2012-08/msg00055.html http://ubuntuforums.org/showthread.php?t=3D2031220 http://lists.xen.org/archives/html/xen-api/2012-08/msg00055.html I tried XCP on Ubuntu 12.04 and on Debian Wheezer. Both show the same = problem: Keyboard in the XenCenter console works fine with PV guests, = but when connecting to HVM guests the keyboard does not work at all. =20 The only workaround I found was to use a generic VNC client instead of = XenCenter. Are there any other workarounds to make it work in XenCenter?=20 Regards, Joern --Apple-Mail=_86FA9168-0839-4D23-87FA-1AE1B3060A5E Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMeDCCBjQw ggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0 Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoX DTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy dENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN AQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK 75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC +y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxD z2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr /+N2JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0w ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFc fH6WNU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6 Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0 dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywG XLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXlt UfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+R HxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktv sv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+s sS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq +n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGT zWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGq Up/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb1 9mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGPDCCBSSg AwIBAgIDBTnCMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN MTIxMTAyMTIwOTI3WhcNMTMxMTAzMDQzNTM4WjBZMRkwFwYDVQQNExBBMmZhSVJLYm1pN1h1TXRZ MRowGAYDVQQDDBFqYkBidy1uZXR3b3J4Lm5ldDEgMB4GCSqGSIb3DQEJARYRamJAYnctbmV0d29y eC5uZXQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgM1GrKqoAtfXZOVfLqdUxSOvO Dk0HuP+Rg27O5cVEOwdDgdvEMO3hgYb6EbPCt+CCjm7jmofC0YnvJOEiz1EbEo59xBvTZluYFj37 xUGwooTaMw2eoSGcOg0xgN4zbBz/hhfoTm+bPagEPsZsZSXk7r/oIvIpwFROyqfVLx4Iq7Ub+tpd SAMFVYsZ/5OED1DHkGpK1bIEnPdXTpnTYXR3F2MkWTQ27vK4HMEHMHy1dpylwHsGtV+joaN4Kimi Oaw1AiBgV+v+wM7f4xRKaOHeesn5CHnifaJL0pWJbIme+eHBZimv5bgU5C30mCq3Kkq7PSo/mxiS bytxdTvGZBkRAgMBAAGjggLXMIIC0zAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAU BggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFE2SqZmCjbuIQnUTPXK7AmK5uObAMB8GA1Ud IwQYMBaAFFNy7ZKc4NrLAVx8fpY1TvLUuFGCMBwGA1UdEQQVMBOBEWpiQGJ3LW5ldHdvcngubmV0 MIIBTAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6 Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29t IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1 ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRo ZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJw b3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1Ud HwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsG AQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xh c3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMv c3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wu Y29tLzANBgkqhkiG9w0BAQUFAAOCAQEAu2yyBhkEB+XRY6aMxOfss4dj39BwwMAh1dtV/XvXqfBl oHVF1EDtdbYsmdEEPm8spDkZBxBlDdoQ4TywdQYWWNADE7/cWkHkeWCoImEkwSCs6W2QZSJOcMDB LtbO06d9SucZAi0JzSMKfHdmE82bURRx5Yv8WLRCYq6de+UpRw+/opwpI3xIq3MoLaAq2gZdfOJ+ nfj7jA74eDEy0W4afXTsmARMuxOBgC2L+1Cq9bUa7/1H74qBmnVyNv9Z3sudjzVWNaxwM57aa2/0 YrGeBbwhfKUOAjOpYWlLXeJevT1176mbuni0eE5KytbNyrJ+wbh6kyvhaKkJf+fjDY3WyDGCA28w ggNrAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwU5wjAJBgUrDgMCGgUAoIIB rzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzAxMjcyMjAzMTBa MCMGCSqGSIb3DQEJBDEWBBTsRgbqNIBGprVN+DQHib1uElDdzjCBpQYJKwYBBAGCNxAEMYGXMIGU MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJl IERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQ cmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwU5wjCBpwYLKoZIhvcNAQkQAgsxgZeggZQw gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFBy aW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBTnCMA0GCSqGSIb3DQEBAQUABIIBAHbjAN50 n34c+oKVC9ePqWZPc1aS/3a4Lit/xT+Sy1nAOinF3NvppKE+9aNArlBWGwg+C1MUKqUomM5TspLL h3VzVlhi3ERRC1ris7m3O995EE230bXwgKXTKiEgzaBFqnLSRJRJ1Lfee0J0wFzCTnJSdz5QtIP5 HpemJsrxfHZSOqKNd5lJhasglDsmACp1CqZ/GBTLpUdfVaE7I2UB6UBeFMm4Pc90WhLA43/zdWOr v9z7cTv12yHTaz/9hrCnNlxWMlYCGT9BLuJIbhiizbnqQj248zuXeNrWPhxqcYhvHC5txtkxZdYu nmXFeYlPZZsvMiKzymvOAyTmCHUukpsAAAAAAAA= --Apple-Mail=_86FA9168-0839-4D23-87FA-1AE1B3060A5E-- --===============2569101740726017054== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2569101740726017054==-- From xen-api-bounces@lists.xen.org Sun Jan 27 22:03:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 27 Jan 2013 22:03:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzaJl-00029R-E7; Sun, 27 Jan 2013 22:03:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzaJk-00029M-ED for xen-api@lists.xen.org; Sun, 27 Jan 2013 22:03:12 +0000 Received: from [85.158.143.99:50736] by server-3.bemta-4.messagelabs.com id 50/7E-10689-F14A5015; Sun, 27 Jan 2013 22:03:11 +0000 X-Env-Sender: jb@bw-networx.net X-Msg-Ref: server-3.tower-216.messagelabs.com!1359324190!29106272!1 X-Originating-IP: [178.63.214.118] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28834 invoked from network); 27 Jan 2013 22:03:10 -0000 Received: from mail.bw-networx.net (HELO mail.bw-networx.net) (178.63.214.118) by server-3.tower-216.messagelabs.com with SMTP; 27 Jan 2013 22:03:10 -0000 Received: from [10.0.10.105] (HSI-KBW-5-10-51-43.hsi18.kabel-badenwuerttemberg.de [5.10.51.43]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.bw-networx.net (Postfix) with ESMTPSA id 8595E6B3383 for ; Sun, 27 Jan 2013 23:03:10 +0100 (CET) From: Joern Bredereck Message-Id: <89FC82A6-DE26-4263-A1A0-42BC02FC7E32@bw-networx.net> Date: Sun, 27 Jan 2013 23:03:09 +0100 To: xen-api@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Subject: [Xen-API] No Keystrokes in XenCenter with HVM guests X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2569101740726017054==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2569101740726017054== Content-Type: multipart/signed; boundary="Apple-Mail=_86FA9168-0839-4D23-87FA-1AE1B3060A5E"; protocol="application/pkcs7-signature"; micalg=sha1 --Apple-Mail=_86FA9168-0839-4D23-87FA-1AE1B3060A5E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, it looks like my problem is already known: http://lists.xen.org/archives/html/xen-api/2012-08/msg00055.html http://ubuntuforums.org/showthread.php?t=3D2031220 http://lists.xen.org/archives/html/xen-api/2012-08/msg00055.html I tried XCP on Ubuntu 12.04 and on Debian Wheezer. Both show the same = problem: Keyboard in the XenCenter console works fine with PV guests, = but when connecting to HVM guests the keyboard does not work at all. =20 The only workaround I found was to use a generic VNC client instead of = XenCenter. Are there any other workarounds to make it work in XenCenter?=20 Regards, Joern --Apple-Mail=_86FA9168-0839-4D23-87FA-1AE1B3060A5E Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMeDCCBjQw ggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0 Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoX DTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy dENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN AQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK 75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC +y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxD z2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr /+N2JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0w ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFc fH6WNU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6 Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0 dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywG XLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXlt UfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+R HxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktv sv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+s sS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq +n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGT zWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGq Up/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb1 9mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGPDCCBSSg AwIBAgIDBTnCMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN MTIxMTAyMTIwOTI3WhcNMTMxMTAzMDQzNTM4WjBZMRkwFwYDVQQNExBBMmZhSVJLYm1pN1h1TXRZ MRowGAYDVQQDDBFqYkBidy1uZXR3b3J4Lm5ldDEgMB4GCSqGSIb3DQEJARYRamJAYnctbmV0d29y eC5uZXQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgM1GrKqoAtfXZOVfLqdUxSOvO Dk0HuP+Rg27O5cVEOwdDgdvEMO3hgYb6EbPCt+CCjm7jmofC0YnvJOEiz1EbEo59xBvTZluYFj37 xUGwooTaMw2eoSGcOg0xgN4zbBz/hhfoTm+bPagEPsZsZSXk7r/oIvIpwFROyqfVLx4Iq7Ub+tpd SAMFVYsZ/5OED1DHkGpK1bIEnPdXTpnTYXR3F2MkWTQ27vK4HMEHMHy1dpylwHsGtV+joaN4Kimi Oaw1AiBgV+v+wM7f4xRKaOHeesn5CHnifaJL0pWJbIme+eHBZimv5bgU5C30mCq3Kkq7PSo/mxiS bytxdTvGZBkRAgMBAAGjggLXMIIC0zAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAU BggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFE2SqZmCjbuIQnUTPXK7AmK5uObAMB8GA1Ud IwQYMBaAFFNy7ZKc4NrLAVx8fpY1TvLUuFGCMBwGA1UdEQQVMBOBEWpiQGJ3LW5ldHdvcngubmV0 MIIBTAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6 Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29t IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1 ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRo ZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJw b3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1Ud HwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsG AQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xh c3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMv c3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wu Y29tLzANBgkqhkiG9w0BAQUFAAOCAQEAu2yyBhkEB+XRY6aMxOfss4dj39BwwMAh1dtV/XvXqfBl oHVF1EDtdbYsmdEEPm8spDkZBxBlDdoQ4TywdQYWWNADE7/cWkHkeWCoImEkwSCs6W2QZSJOcMDB LtbO06d9SucZAi0JzSMKfHdmE82bURRx5Yv8WLRCYq6de+UpRw+/opwpI3xIq3MoLaAq2gZdfOJ+ nfj7jA74eDEy0W4afXTsmARMuxOBgC2L+1Cq9bUa7/1H74qBmnVyNv9Z3sudjzVWNaxwM57aa2/0 YrGeBbwhfKUOAjOpYWlLXeJevT1176mbuni0eE5KytbNyrJ+wbh6kyvhaKkJf+fjDY3WyDGCA28w ggNrAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwU5wjAJBgUrDgMCGgUAoIIB rzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzAxMjcyMjAzMTBa MCMGCSqGSIb3DQEJBDEWBBTsRgbqNIBGprVN+DQHib1uElDdzjCBpQYJKwYBBAGCNxAEMYGXMIGU MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJl IERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQ cmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwU5wjCBpwYLKoZIhvcNAQkQAgsxgZeggZQw gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFBy aW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBTnCMA0GCSqGSIb3DQEBAQUABIIBAHbjAN50 n34c+oKVC9ePqWZPc1aS/3a4Lit/xT+Sy1nAOinF3NvppKE+9aNArlBWGwg+C1MUKqUomM5TspLL h3VzVlhi3ERRC1ris7m3O995EE230bXwgKXTKiEgzaBFqnLSRJRJ1Lfee0J0wFzCTnJSdz5QtIP5 HpemJsrxfHZSOqKNd5lJhasglDsmACp1CqZ/GBTLpUdfVaE7I2UB6UBeFMm4Pc90WhLA43/zdWOr v9z7cTv12yHTaz/9hrCnNlxWMlYCGT9BLuJIbhiizbnqQj248zuXeNrWPhxqcYhvHC5txtkxZdYu nmXFeYlPZZsvMiKzymvOAyTmCHUukpsAAAAAAAA= --Apple-Mail=_86FA9168-0839-4D23-87FA-1AE1B3060A5E-- --===============2569101740726017054== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============2569101740726017054==-- From xen-api-bounces@lists.xen.org Mon Jan 28 07:34:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 07:34:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzjEu-0004Jt-C4; Mon, 28 Jan 2013 07:34:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzjEs-0004Je-W2; Mon, 28 Jan 2013 07:34:47 +0000 Received: from [85.158.143.99:56684] by server-2.bemta-4.messagelabs.com id EA/0A-03518-61A26015; Mon, 28 Jan 2013 07:34:46 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1359358485!29716711!1 X-Originating-IP: [209.85.214.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24294 invoked from network); 28 Jan 2013 07:34:45 -0000 Received: from mail-bk0-f51.google.com (HELO mail-bk0-f51.google.com) (209.85.214.51) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2013 07:34:45 -0000 Received: by mail-bk0-f51.google.com with SMTP id ik5so1133556bkc.38 for ; Sun, 27 Jan 2013 23:34:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=HpDV6Ep9f1QcTlfdN5mjmnKENJaxk0u7SlBKclGkoUc=; b=CL4RrM4gvpRZFArSS7boqyuXqD4zKUBkbfB478blImkvvH2fGNFNrN34FuoSsU48f0 70/WGGHGg6c9Cnzlbstwd8bYlOB6Spjg9G/8/XYAe4BbHEEgfvRSEYuDMYEGx6zhoV7C xm6jwUVqQe8I/p4nIjiVdrrsZtpWOjrYMhZmMnE7M4Uc35A0NXTsfJqPsRbB/1reGpVE ECo+lmBeT1zk38VZMhgG9c4XZ0olqdw4IpnDCdAnEIrdThysNXUFzr1dm4eOp4AZ0ihO aXprb/15UVjN06yJk1tdmmuPAN2AkprGn6QVn15W1AI9XuB/ql1LbMTGfzgC7kAwZeWw mEGw== X-Received: by 10.204.149.26 with SMTP id r26mr3725788bkv.71.1359358484718; Sun, 27 Jan 2013 23:34:44 -0800 (PST) Received: from [172.16.26.11] (b01bc791.bb.sky.com. [176.27.199.145]) by mx.google.com with ESMTPS id hu20sm4810697bkc.12.2013.01.27.23.34.42 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 27 Jan 2013 23:34:43 -0800 (PST) Message-ID: <51062A0E.7060605@xen.org> Date: Mon, 28 Jan 2013 07:34:38 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-users@lists.xen.org" , xen-arm@lists.xen.org Subject: [Xen-API] Xen Document Day is on today X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Good morning, a quick reminder that the Xen document day is on today See: - http://wiki.xen.org/wiki/Xen_Document_Days - http://wiki.xen.org/wiki/Xen_Document_Days/TODO See you on IRC Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 28 07:34:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 07:34:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzjEu-0004Jt-C4; Mon, 28 Jan 2013 07:34:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzjEs-0004Je-W2; Mon, 28 Jan 2013 07:34:47 +0000 Received: from [85.158.143.99:56684] by server-2.bemta-4.messagelabs.com id EA/0A-03518-61A26015; Mon, 28 Jan 2013 07:34:46 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1359358485!29716711!1 X-Originating-IP: [209.85.214.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24294 invoked from network); 28 Jan 2013 07:34:45 -0000 Received: from mail-bk0-f51.google.com (HELO mail-bk0-f51.google.com) (209.85.214.51) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2013 07:34:45 -0000 Received: by mail-bk0-f51.google.com with SMTP id ik5so1133556bkc.38 for ; Sun, 27 Jan 2013 23:34:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=HpDV6Ep9f1QcTlfdN5mjmnKENJaxk0u7SlBKclGkoUc=; b=CL4RrM4gvpRZFArSS7boqyuXqD4zKUBkbfB478blImkvvH2fGNFNrN34FuoSsU48f0 70/WGGHGg6c9Cnzlbstwd8bYlOB6Spjg9G/8/XYAe4BbHEEgfvRSEYuDMYEGx6zhoV7C xm6jwUVqQe8I/p4nIjiVdrrsZtpWOjrYMhZmMnE7M4Uc35A0NXTsfJqPsRbB/1reGpVE ECo+lmBeT1zk38VZMhgG9c4XZ0olqdw4IpnDCdAnEIrdThysNXUFzr1dm4eOp4AZ0ihO aXprb/15UVjN06yJk1tdmmuPAN2AkprGn6QVn15W1AI9XuB/ql1LbMTGfzgC7kAwZeWw mEGw== X-Received: by 10.204.149.26 with SMTP id r26mr3725788bkv.71.1359358484718; Sun, 27 Jan 2013 23:34:44 -0800 (PST) Received: from [172.16.26.11] (b01bc791.bb.sky.com. [176.27.199.145]) by mx.google.com with ESMTPS id hu20sm4810697bkc.12.2013.01.27.23.34.42 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 27 Jan 2013 23:34:43 -0800 (PST) Message-ID: <51062A0E.7060605@xen.org> Date: Mon, 28 Jan 2013 07:34:38 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-users@lists.xen.org" , xen-arm@lists.xen.org Subject: [Xen-API] Xen Document Day is on today X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Good morning, a quick reminder that the Xen document day is on today See: - http://wiki.xen.org/wiki/Xen_Document_Days - http://wiki.xen.org/wiki/Xen_Document_Days/TODO See you on IRC Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 28 09:58:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 09:58:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzlUE-0006QA-2a; Mon, 28 Jan 2013 09:58:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzlUC-0006Q5-LF for xen-api@lists.xen.org; Mon, 28 Jan 2013 09:58:44 +0000 Received: from [193.109.254.147:28860] by server-8.bemta-14.messagelabs.com id 15/7C-29383-3DB46015; Mon, 28 Jan 2013 09:58:43 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1359367103!9113553!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTc2OTk=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28274 invoked from network); 28 Jan 2013 09:58:25 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2013 09:58:25 -0000 X-IronPort-AV: E=Sophos;i="4.84,550,1355097600"; d="scan'208";a="5287137" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 28 Jan 2013 09:58:23 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Mon, 28 Jan 2013 04:58:23 -0500 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[192.168.0.6]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TzlTq-0004zw-TT; Mon, 28 Jan 2013 09:58:22 +0000 Message-ID: <51064BBD.80206@citrix.com> Date: Mon, 28 Jan 2013 09:58:21 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: John Koffler References: <1048A8D3B689A14496E7B490017693F20A7D0951@mail.peer9.net> In-Reply-To: <1048A8D3B689A14496E7B490017693F20A7D0951@mail.peer9.net> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] SR content-type X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 27/01/13 19:26, John Koffler wrote: > Hello all, > > Forgive me if this has been covered before. I'm using XCP 1.6 and a > provisioning utility that interacts with the hypervisor. One thing I > have noticed is that under any new SR's I create in the Xencenter UI, > the content-type parameter is blank. As far as I am aware, there is > no way to update this, other than to remove the SR and re-introduce > it. If it's read-only, then you won't be able to change it at runtime. You can set it during SR creation on the CLI and through the API. Why do you want to update this? Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 28 09:58:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 09:58:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzlUE-0006QA-2a; Mon, 28 Jan 2013 09:58:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzlUC-0006Q5-LF for xen-api@lists.xen.org; Mon, 28 Jan 2013 09:58:44 +0000 Received: from [193.109.254.147:28860] by server-8.bemta-14.messagelabs.com id 15/7C-29383-3DB46015; Mon, 28 Jan 2013 09:58:43 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1359367103!9113553!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTc2OTk=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28274 invoked from network); 28 Jan 2013 09:58:25 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2013 09:58:25 -0000 X-IronPort-AV: E=Sophos;i="4.84,550,1355097600"; d="scan'208";a="5287137" Received: from unknown (HELO FTLPEX01CL02.citrite.net) ([10.13.107.79]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 28 Jan 2013 09:58:23 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Mon, 28 Jan 2013 04:58:23 -0500 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[192.168.0.6]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TzlTq-0004zw-TT; Mon, 28 Jan 2013 09:58:22 +0000 Message-ID: <51064BBD.80206@citrix.com> Date: Mon, 28 Jan 2013 09:58:21 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: John Koffler References: <1048A8D3B689A14496E7B490017693F20A7D0951@mail.peer9.net> In-Reply-To: <1048A8D3B689A14496E7B490017693F20A7D0951@mail.peer9.net> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] SR content-type X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 27/01/13 19:26, John Koffler wrote: > Hello all, > > Forgive me if this has been covered before. I'm using XCP 1.6 and a > provisioning utility that interacts with the hypervisor. One thing I > have noticed is that under any new SR's I create in the Xencenter UI, > the content-type parameter is blank. As far as I am aware, there is > no way to update this, other than to remove the SR and re-introduce > it. If it's read-only, then you won't be able to change it at runtime. You can set it during SR creation on the CLI and through the API. Why do you want to update this? Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 28 10:30:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 10:30:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzlyV-0007er-6t; Mon, 28 Jan 2013 10:30:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzlyT-0007ef-JB for xen-api@lists.xen.org; Mon, 28 Jan 2013 10:30:01 +0000 Received: from [85.158.143.99:6963] by server-3.bemta-4.messagelabs.com id 2A/1F-10689-82356015; Mon, 28 Jan 2013 10:30:00 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-6.tower-216.messagelabs.com!1359368987!22752635!1 X-Originating-IP: [80.12.242.124] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8737 invoked from network); 28 Jan 2013 10:29:48 -0000 Received: from smtp02.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.124) by server-6.tower-216.messagelabs.com with SMTP; 28 Jan 2013 10:29:48 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d03 with ME id tNVm1k00U3zjds103NVmwr; Mon, 28 Jan 2013 11:29:47 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A09B9161BB4; Mon, 28 Jan 2013 11:29:46 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZE_FCOCtqt5a; Mon, 28 Jan 2013 11:29:44 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 22ECC161BBA; Mon, 28 Jan 2013 11:29:43 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id RVwOu7721RP1; Mon, 28 Jan 2013 11:29:41 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B8462161BB4; Mon, 28 Jan 2013 11:29:41 +0100 (CET) Message-ID: <51065315.3050104@tranquil-it-systems.fr> Date: Mon, 28 Jan 2013 11:29:41 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: James References: <39F8F0A9F90D5C48A847177B56A22567015B80045B6D@MBX81.ad2.softcom.biz> In-Reply-To: <39F8F0A9F90D5C48A847177B56A22567015B80045B6D@MBX81.ad2.softcom.biz> Cc: "Xen-api@lists.xen.org" Subject: Re: [Xen-API] Disaster Recovery of Xen XCP. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi James, > Over the past couple of weeks I've installed XCP onto a USB stick and hav= e built up my virtual data-center. Now it would appear that the USB stick = is failing and I would like to recover rather than rebuild. USB stick have very bad wear leveling, and you should avoid using them = if they is not mounted read only (you can take a look at the debian live = project to have system booting from usb mounted read only). Actually I = toasted a few usb stick with basic io write pattern. I used to have a few XCP servers on usb stick/CF cards, and I switched = all of them no SSD because of disastreous wear leveling. Standard XCP = servers I/O pattern is not very intensive, and USB stick should = theoritically be ok, however in case of problem you can get intensive = logging and your USB stick will be toasted in no time. > The good: > This first showed up last night and I was able to shut down my VMs (at le= ast partially) and power cycle the server to get XCP back up and running. > Also good (I think) all of the VMs and their related storage is hosted fr= om a hardware RAID controller. > > Whether I install another USB stick or use a normal hard drive, the issue= is the same: > > How do I get my VM's recognized on a new install of XCP? XCP metadata (which define VMs setup, network config and corresponding = virtual disk) are written in a db on the XCP partition (which you lost = with your toasted USB stick). You can setup a daily backup using = xsconsole on your storage SR for disaster recovery. Alternatively, you = can do a xe pool-dump-database through cronjob to have your metadata on = your backup server. > If I recall correctly, when I created the RAID array as a storage reposit= ory for XCP, it warned me that all contents would be lost. However I don't= think I need to "create" the SR...I just need to "import" the SR and then = "import" the VM's. > > With that in mind...Surely there's an "export" option somewhere in XCP?? Your new XCP install has no clue of what is inside your SR. I don't = remember the exact commands to introduce this existing SR to your new = server, but it should be something like = http://support.citrix.com/article/CTX121896 . Do backup first if you are = not familiar with all that stuff. Cheers, Denis > > Thanks, > > James > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 28 10:30:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 10:30:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzlyV-0007er-6t; Mon, 28 Jan 2013 10:30:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzlyT-0007ef-JB for xen-api@lists.xen.org; Mon, 28 Jan 2013 10:30:01 +0000 Received: from [85.158.143.99:6963] by server-3.bemta-4.messagelabs.com id 2A/1F-10689-82356015; Mon, 28 Jan 2013 10:30:00 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-6.tower-216.messagelabs.com!1359368987!22752635!1 X-Originating-IP: [80.12.242.124] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8737 invoked from network); 28 Jan 2013 10:29:48 -0000 Received: from smtp02.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.124) by server-6.tower-216.messagelabs.com with SMTP; 28 Jan 2013 10:29:48 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d03 with ME id tNVm1k00U3zjds103NVmwr; Mon, 28 Jan 2013 11:29:47 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A09B9161BB4; Mon, 28 Jan 2013 11:29:46 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZE_FCOCtqt5a; Mon, 28 Jan 2013 11:29:44 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 22ECC161BBA; Mon, 28 Jan 2013 11:29:43 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id RVwOu7721RP1; Mon, 28 Jan 2013 11:29:41 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id B8462161BB4; Mon, 28 Jan 2013 11:29:41 +0100 (CET) Message-ID: <51065315.3050104@tranquil-it-systems.fr> Date: Mon, 28 Jan 2013 11:29:41 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: James References: <39F8F0A9F90D5C48A847177B56A22567015B80045B6D@MBX81.ad2.softcom.biz> In-Reply-To: <39F8F0A9F90D5C48A847177B56A22567015B80045B6D@MBX81.ad2.softcom.biz> Cc: "Xen-api@lists.xen.org" Subject: Re: [Xen-API] Disaster Recovery of Xen XCP. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi James, > Over the past couple of weeks I've installed XCP onto a USB stick and hav= e built up my virtual data-center. Now it would appear that the USB stick = is failing and I would like to recover rather than rebuild. USB stick have very bad wear leveling, and you should avoid using them = if they is not mounted read only (you can take a look at the debian live = project to have system booting from usb mounted read only). Actually I = toasted a few usb stick with basic io write pattern. I used to have a few XCP servers on usb stick/CF cards, and I switched = all of them no SSD because of disastreous wear leveling. Standard XCP = servers I/O pattern is not very intensive, and USB stick should = theoritically be ok, however in case of problem you can get intensive = logging and your USB stick will be toasted in no time. > The good: > This first showed up last night and I was able to shut down my VMs (at le= ast partially) and power cycle the server to get XCP back up and running. > Also good (I think) all of the VMs and their related storage is hosted fr= om a hardware RAID controller. > > Whether I install another USB stick or use a normal hard drive, the issue= is the same: > > How do I get my VM's recognized on a new install of XCP? XCP metadata (which define VMs setup, network config and corresponding = virtual disk) are written in a db on the XCP partition (which you lost = with your toasted USB stick). You can setup a daily backup using = xsconsole on your storage SR for disaster recovery. Alternatively, you = can do a xe pool-dump-database through cronjob to have your metadata on = your backup server. > If I recall correctly, when I created the RAID array as a storage reposit= ory for XCP, it warned me that all contents would be lost. However I don't= think I need to "create" the SR...I just need to "import" the SR and then = "import" the VM's. > > With that in mind...Surely there's an "export" option somewhere in XCP?? Your new XCP install has no clue of what is inside your SR. I don't = remember the exact commands to introduce this existing SR to your new = server, but it should be something like = http://support.citrix.com/article/CTX121896 . Do backup first if you are = not familiar with all that stuff. Cheers, Denis > > Thanks, > > James > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 28 13:34:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 13:34:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzorH-00057V-EC; Mon, 28 Jan 2013 13:34:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzorG-00057Q-7m for xen-api@lists.xen.org; Mon, 28 Jan 2013 13:34:46 +0000 Received: from [85.158.139.83:48823] by server-6.bemta-5.messagelabs.com id 42/1A-25043-57E76015; Mon, 28 Jan 2013 13:34:45 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1359380084!29768109!1 X-Originating-IP: [209.85.217.171] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25770 invoked from network); 28 Jan 2013 13:34:44 -0000 Received: from mail-lb0-f171.google.com (HELO mail-lb0-f171.google.com) (209.85.217.171) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2013 13:34:44 -0000 Received: by mail-lb0-f171.google.com with SMTP id gg13so3912760lbb.16 for ; Mon, 28 Jan 2013 05:34:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=wQLvYo7IaMA/ZCTnlu3SL2xCK9Oan6gOtEWrX54fLOc=; b=HNRTjLD0NDpunaHrEK69inriWqBoEtwggIkjAksq8iGJEcASK/y/icVhqrZaCUfBzy 60QpQdvUr4iwfP93ft1Ochoa3jxXrUGp8fMGOslzo2x/qFyHID43c418SD66y5h3y3zk KBmDGaZw1WL07oENxCW9jP3Ju7M7Xg6S8kYWTXKoPhuNbYkQR3uCzfyaeLr/I4CP0PKh 4VruDGKALrDL94+DWEfzxexh2Smbr7UaNc8ZGyUoaIrPcoHBs7dioDKoSAYBMKWXyEoS EUsXSBE2mL4b3JhT1rRSa96o6N0I2Td0S6lIuIt9wtMcbpjvL5gKKK5SI+MKnPBSzhxs rSGg== X-Received: by 10.152.127.202 with SMTP id ni10mr13252570lab.6.1359380075358; Mon, 28 Jan 2013 05:34:35 -0800 (PST) Received: from [172.16.26.11] ([151.225.36.122]) by mx.google.com with ESMTPS id tm10sm3600070lab.10.2013.01.28.05.34.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Jan 2013 05:34:34 -0800 (PST) Message-ID: <51067E64.7080500@xen.org> Date: Mon, 28 Jan 2013 13:34:28 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" Subject: [Xen-API] Proposal: naming conventions for XCP, XAPI, etc. related documents on wiki.xen.org X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, as part of the docs day, we got feedback that the titles of XCP related documents are extremely confusing to users. I particular, users cannot find some XCP related documents in indexes and categories. My suggestion would be to go through a document renaming exercise. But before we do this, I want to get feedback. Here is my proposal: 1) User facing documents referring to the ISO start with "XCP", e.g. "XCP Overview" 2) Documents specific to "XCP-XAPI" packages start with "XCP-XAPI" 3) Design or developer documents start with the component, e.g. "XAPI", "XENOPSD", etc. whereas say a glossary item for XENOPSD, XAPI, etc. would be "XCP XENOPSD", "XCP XAPI", etc. Please let me know your views. Probably not something we want to fix this document day, but maybe for the next one. Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 28 13:34:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 13:34:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzorH-00057V-EC; Mon, 28 Jan 2013 13:34:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzorG-00057Q-7m for xen-api@lists.xen.org; Mon, 28 Jan 2013 13:34:46 +0000 Received: from [85.158.139.83:48823] by server-6.bemta-5.messagelabs.com id 42/1A-25043-57E76015; Mon, 28 Jan 2013 13:34:45 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1359380084!29768109!1 X-Originating-IP: [209.85.217.171] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25770 invoked from network); 28 Jan 2013 13:34:44 -0000 Received: from mail-lb0-f171.google.com (HELO mail-lb0-f171.google.com) (209.85.217.171) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2013 13:34:44 -0000 Received: by mail-lb0-f171.google.com with SMTP id gg13so3912760lbb.16 for ; Mon, 28 Jan 2013 05:34:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=wQLvYo7IaMA/ZCTnlu3SL2xCK9Oan6gOtEWrX54fLOc=; b=HNRTjLD0NDpunaHrEK69inriWqBoEtwggIkjAksq8iGJEcASK/y/icVhqrZaCUfBzy 60QpQdvUr4iwfP93ft1Ochoa3jxXrUGp8fMGOslzo2x/qFyHID43c418SD66y5h3y3zk KBmDGaZw1WL07oENxCW9jP3Ju7M7Xg6S8kYWTXKoPhuNbYkQR3uCzfyaeLr/I4CP0PKh 4VruDGKALrDL94+DWEfzxexh2Smbr7UaNc8ZGyUoaIrPcoHBs7dioDKoSAYBMKWXyEoS EUsXSBE2mL4b3JhT1rRSa96o6N0I2Td0S6lIuIt9wtMcbpjvL5gKKK5SI+MKnPBSzhxs rSGg== X-Received: by 10.152.127.202 with SMTP id ni10mr13252570lab.6.1359380075358; Mon, 28 Jan 2013 05:34:35 -0800 (PST) Received: from [172.16.26.11] ([151.225.36.122]) by mx.google.com with ESMTPS id tm10sm3600070lab.10.2013.01.28.05.34.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Jan 2013 05:34:34 -0800 (PST) Message-ID: <51067E64.7080500@xen.org> Date: Mon, 28 Jan 2013 13:34:28 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-api@lists.xen.org" Subject: [Xen-API] Proposal: naming conventions for XCP, XAPI, etc. related documents on wiki.xen.org X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, as part of the docs day, we got feedback that the titles of XCP related documents are extremely confusing to users. I particular, users cannot find some XCP related documents in indexes and categories. My suggestion would be to go through a document renaming exercise. But before we do this, I want to get feedback. Here is my proposal: 1) User facing documents referring to the ISO start with "XCP", e.g. "XCP Overview" 2) Documents specific to "XCP-XAPI" packages start with "XCP-XAPI" 3) Design or developer documents start with the component, e.g. "XAPI", "XENOPSD", etc. whereas say a glossary item for XENOPSD, XAPI, etc. would be "XCP XENOPSD", "XCP XAPI", etc. Please let me know your views. Probably not something we want to fix this document day, but maybe for the next one. Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 28 19:29:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 19:29:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzuOO-00007a-Jv; Mon, 28 Jan 2013 19:29:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzuOM-00007V-VM for Xen-api@lists.xen.org; Mon, 28 Jan 2013 19:29:19 +0000 Received: from [85.158.137.99:23067] by server-9.bemta-3.messagelabs.com id DA/22-08786-981D6015; Mon, 28 Jan 2013 19:29:13 +0000 X-Env-Sender: jgreenlee@mail2web.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1359401350!14196482!1 X-Originating-IP: [168.144.250.229] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTY4LjE0NC4yNTAuMjI5ID0+IDE3OTAy\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26532 invoked from network); 28 Jan 2013 19:29:11 -0000 Received: from xsmtp08.mail2web.com (HELO xsmtp08.mail2web.com) (168.144.250.229) by server-5.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 28 Jan 2013 19:29:11 -0000 Received: from [10.5.31.7] (helo=hub01.ad2.softcom.biz) by xsmtp08.mail2web.com with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.63) (envelope-from ) id 1TzuO7-0000QC-BH for Xen-api@lists.xen.org; Mon, 28 Jan 2013 14:29:09 -0500 Received: from MBX81.ad2.softcom.biz ([10.5.13.49]) by hub01.ad2.softcom.biz ([10.5.31.7]) with mapi; Mon, 28 Jan 2013 14:28:58 -0500 From: James To: Denis Cardon Date: Mon, 28 Jan 2013 14:28:58 -0500 Thread-Topic: [Xen-API] Disaster Recovery of Xen XCP. Thread-Index: Ac39QmfO3aaiTHuUS5mbS5YZ0dZSaAASY6OI Message-ID: <39F8F0A9F90D5C48A847177B56A22567015B80045B70@MBX81.ad2.softcom.biz> References: <39F8F0A9F90D5C48A847177B56A22567015B80045B6D@MBX81.ad2.softcom.biz>, <51065315.3050104@tranquil-it-systems.fr> In-Reply-To: <51065315.3050104@tranquil-it-systems.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "Xen-api@lists.xen.org" Subject: Re: [Xen-API] Disaster Recovery of Xen XCP. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I haven't found a reason for it...But the USB stick would randomly just "di= sappear." One thing I noticed is that the logging on XCP was out of contro= l. HUGE gzip'd archives several a day. I'll pull some log data and inquir= e later. I found this site... http://www.schirmacher.de/display/INFO/How+to+reattach+a+disk+to+XenServer Which provided some info that was helpful for CLI commands. Ultimately, I was able to get the USB stick to boot and write all the Metad= ata to the SR on my RAID controller. I then loaded a stand-alone SATA driv= e, attached the RAID SR through xsconsole, and then restored the VM's from = the Metadata that I had written to the RAID SR. I had to clean up a few things but everything came back. One thing that wa= s somewhat puzzling was the date on my system had moved forward over a week= . The hardware clock thought it was Feb8th. Apparently all of my VM's did= as well as they all were freaked out about the date and forced a fsck on b= oot. Not sure how the date got messed up. One thing I noticed is that XCP kept = setting my clock back 5 hours based on my timezone settings. I don't recal= l that being an issue before, but I went into BIOS and set the hardware clo= ck to be UTC, and then set XCP to be EST. I need to sift through my VM's t= o make sure they're seeing the right time. I'm very happy that I was able to save everything. James ________________________________________ From: Denis Cardon [denis.cardon@tranquil-it-systems.fr] Sent: Monday, January 28, 2013 5:29 AM To: James Cc: Xen-api@lists.xen.org Subject: Re: [Xen-API] Disaster Recovery of Xen XCP. Hi James, > Over the past couple of weeks I've installed XCP onto a USB stick and hav= e built up my virtual data-center. Now it would appear that the USB stick = is failing and I would like to recover rather than rebuild. USB stick have very bad wear leveling, and you should avoid using them if they is not mounted read only (you can take a look at the debian live project to have system booting from usb mounted read only). Actually I toasted a few usb stick with basic io write pattern. I used to have a few XCP servers on usb stick/CF cards, and I switched all of them no SSD because of disastreous wear leveling. Standard XCP servers I/O pattern is not very intensive, and USB stick should theoritically be ok, however in case of problem you can get intensive logging and your USB stick will be toasted in no time. > The good: > This first showed up last night and I was able to shut down my VMs (at le= ast partially) and power cycle the server to get XCP back up and running. > Also good (I think) all of the VMs and their related storage is hosted fr= om a hardware RAID controller. > > Whether I install another USB stick or use a normal hard drive, the issue= is the same: > > How do I get my VM's recognized on a new install of XCP? XCP metadata (which define VMs setup, network config and corresponding virtual disk) are written in a db on the XCP partition (which you lost with your toasted USB stick). You can setup a daily backup using xsconsole on your storage SR for disaster recovery. Alternatively, you can do a xe pool-dump-database through cronjob to have your metadata on your backup server. > If I recall correctly, when I created the RAID array as a storage reposit= ory for XCP, it warned me that all contents would be lost. However I don't= think I need to "create" the SR...I just need to "import" the SR and then = "import" the VM's. > > With that in mind...Surely there's an "export" option somewhere in XCP?? Your new XCP install has no clue of what is inside your SR. I don't remember the exact commands to introduce this existing SR to your new server, but it should be something like http://support.citrix.com/article/CTX121896 . Do backup first if you are not familiar with all that stuff. Cheers, Denis > > Thanks, > > James > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Jan 28 19:29:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 28 Jan 2013 19:29:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzuOO-00007a-Jv; Mon, 28 Jan 2013 19:29:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TzuOM-00007V-VM for Xen-api@lists.xen.org; Mon, 28 Jan 2013 19:29:19 +0000 Received: from [85.158.137.99:23067] by server-9.bemta-3.messagelabs.com id DA/22-08786-981D6015; Mon, 28 Jan 2013 19:29:13 +0000 X-Env-Sender: jgreenlee@mail2web.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1359401350!14196482!1 X-Originating-IP: [168.144.250.229] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTY4LjE0NC4yNTAuMjI5ID0+IDE3OTAy\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26532 invoked from network); 28 Jan 2013 19:29:11 -0000 Received: from xsmtp08.mail2web.com (HELO xsmtp08.mail2web.com) (168.144.250.229) by server-5.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 28 Jan 2013 19:29:11 -0000 Received: from [10.5.31.7] (helo=hub01.ad2.softcom.biz) by xsmtp08.mail2web.com with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.63) (envelope-from ) id 1TzuO7-0000QC-BH for Xen-api@lists.xen.org; Mon, 28 Jan 2013 14:29:09 -0500 Received: from MBX81.ad2.softcom.biz ([10.5.13.49]) by hub01.ad2.softcom.biz ([10.5.31.7]) with mapi; Mon, 28 Jan 2013 14:28:58 -0500 From: James To: Denis Cardon Date: Mon, 28 Jan 2013 14:28:58 -0500 Thread-Topic: [Xen-API] Disaster Recovery of Xen XCP. Thread-Index: Ac39QmfO3aaiTHuUS5mbS5YZ0dZSaAASY6OI Message-ID: <39F8F0A9F90D5C48A847177B56A22567015B80045B70@MBX81.ad2.softcom.biz> References: <39F8F0A9F90D5C48A847177B56A22567015B80045B6D@MBX81.ad2.softcom.biz>, <51065315.3050104@tranquil-it-systems.fr> In-Reply-To: <51065315.3050104@tranquil-it-systems.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "Xen-api@lists.xen.org" Subject: Re: [Xen-API] Disaster Recovery of Xen XCP. X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org I haven't found a reason for it...But the USB stick would randomly just "di= sappear." One thing I noticed is that the logging on XCP was out of contro= l. HUGE gzip'd archives several a day. I'll pull some log data and inquir= e later. I found this site... http://www.schirmacher.de/display/INFO/How+to+reattach+a+disk+to+XenServer Which provided some info that was helpful for CLI commands. Ultimately, I was able to get the USB stick to boot and write all the Metad= ata to the SR on my RAID controller. I then loaded a stand-alone SATA driv= e, attached the RAID SR through xsconsole, and then restored the VM's from = the Metadata that I had written to the RAID SR. I had to clean up a few things but everything came back. One thing that wa= s somewhat puzzling was the date on my system had moved forward over a week= . The hardware clock thought it was Feb8th. Apparently all of my VM's did= as well as they all were freaked out about the date and forced a fsck on b= oot. Not sure how the date got messed up. One thing I noticed is that XCP kept = setting my clock back 5 hours based on my timezone settings. I don't recal= l that being an issue before, but I went into BIOS and set the hardware clo= ck to be UTC, and then set XCP to be EST. I need to sift through my VM's t= o make sure they're seeing the right time. I'm very happy that I was able to save everything. James ________________________________________ From: Denis Cardon [denis.cardon@tranquil-it-systems.fr] Sent: Monday, January 28, 2013 5:29 AM To: James Cc: Xen-api@lists.xen.org Subject: Re: [Xen-API] Disaster Recovery of Xen XCP. Hi James, > Over the past couple of weeks I've installed XCP onto a USB stick and hav= e built up my virtual data-center. Now it would appear that the USB stick = is failing and I would like to recover rather than rebuild. USB stick have very bad wear leveling, and you should avoid using them if they is not mounted read only (you can take a look at the debian live project to have system booting from usb mounted read only). Actually I toasted a few usb stick with basic io write pattern. I used to have a few XCP servers on usb stick/CF cards, and I switched all of them no SSD because of disastreous wear leveling. Standard XCP servers I/O pattern is not very intensive, and USB stick should theoritically be ok, however in case of problem you can get intensive logging and your USB stick will be toasted in no time. > The good: > This first showed up last night and I was able to shut down my VMs (at le= ast partially) and power cycle the server to get XCP back up and running. > Also good (I think) all of the VMs and their related storage is hosted fr= om a hardware RAID controller. > > Whether I install another USB stick or use a normal hard drive, the issue= is the same: > > How do I get my VM's recognized on a new install of XCP? XCP metadata (which define VMs setup, network config and corresponding virtual disk) are written in a db on the XCP partition (which you lost with your toasted USB stick). You can setup a daily backup using xsconsole on your storage SR for disaster recovery. Alternatively, you can do a xe pool-dump-database through cronjob to have your metadata on your backup server. > If I recall correctly, when I created the RAID array as a storage reposit= ory for XCP, it warned me that all contents would be lost. However I don't= think I need to "create" the SR...I just need to "import" the SR and then = "import" the VM's. > > With that in mind...Surely there's an "export" option somewhere in XCP?? Your new XCP install has no clue of what is inside your SR. I don't remember the exact commands to introduce this existing SR to your new server, but it should be something like http://support.citrix.com/article/CTX121896 . Do backup first if you are not familiar with all that stuff. Cheers, Denis > > Thanks, > > James > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > -- Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Jan 29 08:08:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 29 Jan 2013 08:08:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U06FA-0000lL-1m; Tue, 29 Jan 2013 08:08:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U06F8-0000lG-Hi for xen-api@lists.xen.org; Tue, 29 Jan 2013 08:08:34 +0000 Received: from [85.158.143.99:25130] by server-1.bemta-4.messagelabs.com id 9B/8F-05635-18387015; Tue, 29 Jan 2013 08:08:33 +0000 X-Env-Sender: mxdog@comcast.net X-Msg-Ref: server-10.tower-216.messagelabs.com!1359446912!22318003!1 X-Originating-IP: [76.96.30.16] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzYuOTYuMzAuMTYgPT4gMTc4ODU5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22268 invoked from network); 29 Jan 2013 08:08:33 -0000 Received: from qmta01.emeryville.ca.mail.comcast.net (HELO qmta01.emeryville.ca.mail.comcast.net) (76.96.30.16) by server-10.tower-216.messagelabs.com with SMTP; 29 Jan 2013 08:08:33 -0000 Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta01.emeryville.ca.mail.comcast.net with comcast id tk2X1k0041wfjNsA1k8YAG; Tue, 29 Jan 2013 08:08:32 +0000 Received: from MXDOGPCN ([98.253.88.38]) by omta23.emeryville.ca.mail.comcast.net with comcast id tk8W1k00E0peYqi8jk8XuU; Tue, 29 Jan 2013 08:08:31 +0000 Message-ID: From: "mxdog" To: Date: Tue, 29 Jan 2013 03:08:30 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18197 X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1359446912; bh=I5OJ7Clkr53lbORQwON+JJf67+VZjAQ5vZu2Xf3U6to=; h=Received:Received:Message-ID:From:To:Subject:Date:MIME-Version: Content-Type; b=lK6rLd0rpZfAmrLeYEgczsf9pezJ+yMQXiHOihwGDs6jssY/lwu/6dePOcLsysXW8 C+N5lypU19CXtgNmAjipVUsg8C/NZ+RqalmZdZbFMXGiIOEij0HYus46ha98lWY0iq gbCdWqiOoULYzjZ4xpYMQryxfXS2gEovgYJ2SbM1Bpr9iJtspJAXLIdWfiGN6WLMvf C1hbGmGW1EWoIb4HUZqvrfHlO7mKjtlaYBlcfVWSA+o/J0HJre6OTM+gULv6qmBLuW lpxwGz/IxfZLRemZgF4VpdUzbXTznCGtB4bSHfNIkyG4c3pZqp5dUq36tu65AZ8T62 Pu2z65ZBZqweA== Subject: [Xen-API] XCP no reboot X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9083111023138885837==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============9083111023138885837== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01CDFDCD.EA279CC0" This is a multi-part message in MIME format. ------=_NextPart_000_0003_01CDFDCD.EA279CC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have been having problems with XCP not rebooting from either the = console or xencenter it basically hangs at "no more processes in this = runlevel" and the runlevel is a mystery i just upgraded to 1.6 from = beta and the problem is still there so i have to physically reset the = computer. I havent had the down time to trace it yet so no clue if = it's not coming out of rc3 clean or the script in rc6 is wrong or the = reboot command isnt working in this distro. i have had a few differant = distros of linux on this box and they all worked fine. and if i remember = right i had the same problen from all the XCP releases i tried before = moving to the beta =20 symptoms=20 reboot xencenter and console on reboot last message is no more process in this = run level ( no reboot ) doing a reboot -h -p does the same thing no reboot=20 shutdown=20 xencenter=20 vm's shut down but the server does not seem to do anything else (forgot = to check which runlevel it ended up in) console stops all process and halts the system ( no power off ) as an aside is there some reason there is no bugzilla or some other = mechanism for XCP? man = reboot ------=_NextPart_000_0003_01CDFDCD.EA279CC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have been having problems with XCP = not rebooting=20 from either the console or xencenter it basically hangs at "no more = processes in=20 this runlevel" and the runlevel is a mystery  i just upgraded to = 1.6 from=20 beta and the problem is still there so i have to physically reset the = computer.=20  I havent had the down  time to trace it yet  so no clue = if it's=20 not coming out of rc3 clean or the script in rc6 is wrong or the  = reboot=20 command isnt working in this distro. i have had a few differant distros = of linux=20 on this box and they all worked fine. and if i remember right i had the = same=20 problen from all the XCP  releases i  tried before moving = to the=20 beta  
 
symptoms
 
reboot
xencenter and console on reboot last = message is no=20 more process in this run level ( no reboot )
doing a reboot -h -p does the same = thing no reboot=20
 
shutdown
xencenter
 
vm's shut down but the server does not = seem to do=20 anything else (forgot to check which runlevel it ended up = in)
 
console stops all process and halts the = system ( no=20 power off )
 
 
 
 
as an aside is there some reason there = is no=20 bugzilla or some other mechanism for XCP?
 
 
 
 
 
 
          =             &= nbsp;           &n= bsp;           &nb= sp;           &nbs= p;        =20 man reboot
 
 
 
 
------=_NextPart_000_0003_01CDFDCD.EA279CC0-- --===============9083111023138885837== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============9083111023138885837==-- From xen-api-bounces@lists.xen.org Tue Jan 29 08:08:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 29 Jan 2013 08:08:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U06FA-0000lL-1m; Tue, 29 Jan 2013 08:08:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U06F8-0000lG-Hi for xen-api@lists.xen.org; Tue, 29 Jan 2013 08:08:34 +0000 Received: from [85.158.143.99:25130] by server-1.bemta-4.messagelabs.com id 9B/8F-05635-18387015; Tue, 29 Jan 2013 08:08:33 +0000 X-Env-Sender: mxdog@comcast.net X-Msg-Ref: server-10.tower-216.messagelabs.com!1359446912!22318003!1 X-Originating-IP: [76.96.30.16] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzYuOTYuMzAuMTYgPT4gMTc4ODU5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22268 invoked from network); 29 Jan 2013 08:08:33 -0000 Received: from qmta01.emeryville.ca.mail.comcast.net (HELO qmta01.emeryville.ca.mail.comcast.net) (76.96.30.16) by server-10.tower-216.messagelabs.com with SMTP; 29 Jan 2013 08:08:33 -0000 Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta01.emeryville.ca.mail.comcast.net with comcast id tk2X1k0041wfjNsA1k8YAG; Tue, 29 Jan 2013 08:08:32 +0000 Received: from MXDOGPCN ([98.253.88.38]) by omta23.emeryville.ca.mail.comcast.net with comcast id tk8W1k00E0peYqi8jk8XuU; Tue, 29 Jan 2013 08:08:31 +0000 Message-ID: From: "mxdog" To: Date: Tue, 29 Jan 2013 03:08:30 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18197 X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1359446912; bh=I5OJ7Clkr53lbORQwON+JJf67+VZjAQ5vZu2Xf3U6to=; h=Received:Received:Message-ID:From:To:Subject:Date:MIME-Version: Content-Type; b=lK6rLd0rpZfAmrLeYEgczsf9pezJ+yMQXiHOihwGDs6jssY/lwu/6dePOcLsysXW8 C+N5lypU19CXtgNmAjipVUsg8C/NZ+RqalmZdZbFMXGiIOEij0HYus46ha98lWY0iq gbCdWqiOoULYzjZ4xpYMQryxfXS2gEovgYJ2SbM1Bpr9iJtspJAXLIdWfiGN6WLMvf C1hbGmGW1EWoIb4HUZqvrfHlO7mKjtlaYBlcfVWSA+o/J0HJre6OTM+gULv6qmBLuW lpxwGz/IxfZLRemZgF4VpdUzbXTznCGtB4bSHfNIkyG4c3pZqp5dUq36tu65AZ8T62 Pu2z65ZBZqweA== Subject: [Xen-API] XCP no reboot X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9083111023138885837==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============9083111023138885837== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01CDFDCD.EA279CC0" This is a multi-part message in MIME format. ------=_NextPart_000_0003_01CDFDCD.EA279CC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have been having problems with XCP not rebooting from either the = console or xencenter it basically hangs at "no more processes in this = runlevel" and the runlevel is a mystery i just upgraded to 1.6 from = beta and the problem is still there so i have to physically reset the = computer. I havent had the down time to trace it yet so no clue if = it's not coming out of rc3 clean or the script in rc6 is wrong or the = reboot command isnt working in this distro. i have had a few differant = distros of linux on this box and they all worked fine. and if i remember = right i had the same problen from all the XCP releases i tried before = moving to the beta =20 symptoms=20 reboot xencenter and console on reboot last message is no more process in this = run level ( no reboot ) doing a reboot -h -p does the same thing no reboot=20 shutdown=20 xencenter=20 vm's shut down but the server does not seem to do anything else (forgot = to check which runlevel it ended up in) console stops all process and halts the system ( no power off ) as an aside is there some reason there is no bugzilla or some other = mechanism for XCP? man = reboot ------=_NextPart_000_0003_01CDFDCD.EA279CC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have been having problems with XCP = not rebooting=20 from either the console or xencenter it basically hangs at "no more = processes in=20 this runlevel" and the runlevel is a mystery  i just upgraded to = 1.6 from=20 beta and the problem is still there so i have to physically reset the = computer.=20  I havent had the down  time to trace it yet  so no clue = if it's=20 not coming out of rc3 clean or the script in rc6 is wrong or the  = reboot=20 command isnt working in this distro. i have had a few differant distros = of linux=20 on this box and they all worked fine. and if i remember right i had the = same=20 problen from all the XCP  releases i  tried before moving = to the=20 beta  
 
symptoms
 
reboot
xencenter and console on reboot last = message is no=20 more process in this run level ( no reboot )
doing a reboot -h -p does the same = thing no reboot=20
 
shutdown
xencenter
 
vm's shut down but the server does not = seem to do=20 anything else (forgot to check which runlevel it ended up = in)
 
console stops all process and halts the = system ( no=20 power off )
 
 
 
 
as an aside is there some reason there = is no=20 bugzilla or some other mechanism for XCP?
 
 
 
 
 
 
          =             &= nbsp;           &n= bsp;           &nb= sp;           &nbs= p;        =20 man reboot
 
 
 
 
------=_NextPart_000_0003_01CDFDCD.EA279CC0-- --===============9083111023138885837== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============9083111023138885837==-- From xen-api-bounces@lists.xen.org Tue Jan 29 14:38:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 29 Jan 2013 14:38:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0CKL-0001R2-Lj; Tue, 29 Jan 2013 14:38:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0CKK-0001Qm-9x; Tue, 29 Jan 2013 14:38:20 +0000 Received: from [85.158.138.51:57136] by server-6.bemta-3.messagelabs.com id 23/03-28717-ADED7015; Tue, 29 Jan 2013 14:38:18 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1359470297!28317642!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31467 invoked from network); 29 Jan 2013 14:38:17 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Jan 2013 14:38:17 -0000 Received: by mail-la0-f49.google.com with SMTP id fs13so342205lab.22 for ; Tue, 29 Jan 2013 06:38:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type; bh=DricW7qLhChb7VHdYrCJR/zAwRWV4jlJ/DnNbinqsKQ=; b=GSuF9L4Cjfzgxrr9KNV05GvCuKyCleOEsapIjpNLkvp75rxDAmEANRqkMl48b0i3P4 IEnbkluj8MU18pcUttuOxf07EQ0rvqTANLL+Co6H6LtD6qK32P4oEZP5fmw+t3I5ooEq VXw+Frgd5pDBeAvJPbPg36TKvMhKt3yMx8Rt4JhoFoU3RkZay31sizIJVMNxx0Whrn4c evzZqyxyUZpqugbFItThPoNl75+lY1Xn0MKXrUAnq6+JJPPmpUeA3ip6uuUKPhVqXg8n eG/1nx7c9lRQ48nwhmq9SwI7YW3vnL6Dn7PiUCwIFgBgIWxUZs8ZtT5TfpsRabYqLCx7 F07Q== X-Received: by 10.152.133.133 with SMTP id pc5mr1343110lab.32.1359470296773; Tue, 29 Jan 2013 06:38:16 -0800 (PST) Received: from [172.16.26.11] ([151.225.52.230]) by mx.google.com with ESMTPS id go4sm4659064lbb.16.2013.01.29.06.38.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Jan 2013 06:38:14 -0800 (PST) Message-ID: <5107DED1.2050308@xen.org> Date: Tue, 29 Jan 2013 14:38:09 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , xen-arm@lists.xen.org, "xen-api@lists.xen.org" Subject: [Xen-API] Xen Document Day : Thank You & Stats X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7514345046409678484==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7514345046409678484== Content-Type: multipart/alternative; boundary="------------030603040502000303090605" This is a multi-part message in MIME format. --------------030603040502000303090605 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi everybody, I wanted to thank everybody who partcipated in the docs day. Seems we have an issue getting the word out, that Xen Docs Days exist though. If you care about docs, please help promote through your social media and other channels. The next Docs Day is on Feb 25th. We changed >11K words on the wiki in more than 126 changesets. Changes to xen.org static pages were made. More than 25 people participated on IRC, and we had vibrant discussions on how to change navigation, improve look and feel, make it easier to find things, to visually distinguish between Xen, XCP, etc. content, and many more. This meant, that I spent a lot of time at this document day adding notes and adding issues to the TODO list and investigated how we could fix some issues that were identified. This led to new sections in the TODO list, e.g. Mediwiki Issues and XCP : Open work items . Also we had new contributors, in particular User:Double-p (who helped categorize many pages) and User:WeiLiu . This shows that adding the http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Easy_tasks_for_Beginners section to the TODO as came out of the last docs day, was the right thing to do. For detailed acknowledgements, see http://wiki.xen.org/wiki/Xen_Document_Days/Acknowledgements/Jan2013 - I was not aware of any docsday related patches. If I missed you, please add yourself to the Acknowledgements page. Thank you again! And see you on Feb 25th. Best Regards Lars P.S.: Feel free to continue contributing to the wiki --------------030603040502000303090605 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi everybody,

I wanted to thank everybody who partcipated in the docs day. Seems we have an issue getting the word out, that Xen Docs Days exist though. If you care about docs, please help promote through your social media and other channels. The next Docs Day is on Feb 25th.

We changed >11K words on the wiki in more than 126 changesets. Changes to xen.org static pages were made. More than 25 people participated on IRC, and we had vibrant discussions on how to change navigation, improve look and feel, make it easier to find things, to visually distinguish between Xen, XCP, etc. content, and many more. This meant, that I spent a lot of time at this document day adding notes and adding issues to the TODO list and investigated how we could fix some issues that were identified.

This led to new sections in the TODO list, e.g. Mediwiki Issues and XCP : Open work items. Also we had new contributors, in particular User:Double-p (who helped categorize many pages) and User:WeiLiu. This shows that adding the http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Easy_tasks_for_Beginners section to the TODO as came out of the last docs day, was the right thing to do.

For detailed acknowledgements, see http://wiki.xen.org/wiki/Xen_Document_Days/Acknowledgements/Jan2013 - I was not aware of any docsday related patches. If I missed you, please add yourself to the Acknowledgements page.

Thank you again! And see you on Feb 25th.

Best Regards
Lars
P.S.: Feel free to continue contributing to the wiki
--------------030603040502000303090605-- --===============7514345046409678484== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7514345046409678484==-- From xen-api-bounces@lists.xen.org Tue Jan 29 14:38:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 29 Jan 2013 14:38:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0CKL-0001R2-Lj; Tue, 29 Jan 2013 14:38:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0CKK-0001Qm-9x; Tue, 29 Jan 2013 14:38:20 +0000 Received: from [85.158.138.51:57136] by server-6.bemta-3.messagelabs.com id 23/03-28717-ADED7015; Tue, 29 Jan 2013 14:38:18 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1359470297!28317642!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31467 invoked from network); 29 Jan 2013 14:38:17 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Jan 2013 14:38:17 -0000 Received: by mail-la0-f49.google.com with SMTP id fs13so342205lab.22 for ; Tue, 29 Jan 2013 06:38:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type; bh=DricW7qLhChb7VHdYrCJR/zAwRWV4jlJ/DnNbinqsKQ=; b=GSuF9L4Cjfzgxrr9KNV05GvCuKyCleOEsapIjpNLkvp75rxDAmEANRqkMl48b0i3P4 IEnbkluj8MU18pcUttuOxf07EQ0rvqTANLL+Co6H6LtD6qK32P4oEZP5fmw+t3I5ooEq VXw+Frgd5pDBeAvJPbPg36TKvMhKt3yMx8Rt4JhoFoU3RkZay31sizIJVMNxx0Whrn4c evzZqyxyUZpqugbFItThPoNl75+lY1Xn0MKXrUAnq6+JJPPmpUeA3ip6uuUKPhVqXg8n eG/1nx7c9lRQ48nwhmq9SwI7YW3vnL6Dn7PiUCwIFgBgIWxUZs8ZtT5TfpsRabYqLCx7 F07Q== X-Received: by 10.152.133.133 with SMTP id pc5mr1343110lab.32.1359470296773; Tue, 29 Jan 2013 06:38:16 -0800 (PST) Received: from [172.16.26.11] ([151.225.52.230]) by mx.google.com with ESMTPS id go4sm4659064lbb.16.2013.01.29.06.38.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Jan 2013 06:38:14 -0800 (PST) Message-ID: <5107DED1.2050308@xen.org> Date: Tue, 29 Jan 2013 14:38:09 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , xen-arm@lists.xen.org, "xen-api@lists.xen.org" Subject: [Xen-API] Xen Document Day : Thank You & Stats X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7514345046409678484==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7514345046409678484== Content-Type: multipart/alternative; boundary="------------030603040502000303090605" This is a multi-part message in MIME format. --------------030603040502000303090605 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi everybody, I wanted to thank everybody who partcipated in the docs day. Seems we have an issue getting the word out, that Xen Docs Days exist though. If you care about docs, please help promote through your social media and other channels. The next Docs Day is on Feb 25th. We changed >11K words on the wiki in more than 126 changesets. Changes to xen.org static pages were made. More than 25 people participated on IRC, and we had vibrant discussions on how to change navigation, improve look and feel, make it easier to find things, to visually distinguish between Xen, XCP, etc. content, and many more. This meant, that I spent a lot of time at this document day adding notes and adding issues to the TODO list and investigated how we could fix some issues that were identified. This led to new sections in the TODO list, e.g. Mediwiki Issues and XCP : Open work items . Also we had new contributors, in particular User:Double-p (who helped categorize many pages) and User:WeiLiu . This shows that adding the http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Easy_tasks_for_Beginners section to the TODO as came out of the last docs day, was the right thing to do. For detailed acknowledgements, see http://wiki.xen.org/wiki/Xen_Document_Days/Acknowledgements/Jan2013 - I was not aware of any docsday related patches. If I missed you, please add yourself to the Acknowledgements page. Thank you again! And see you on Feb 25th. Best Regards Lars P.S.: Feel free to continue contributing to the wiki --------------030603040502000303090605 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi everybody,

I wanted to thank everybody who partcipated in the docs day. Seems we have an issue getting the word out, that Xen Docs Days exist though. If you care about docs, please help promote through your social media and other channels. The next Docs Day is on Feb 25th.

We changed >11K words on the wiki in more than 126 changesets. Changes to xen.org static pages were made. More than 25 people participated on IRC, and we had vibrant discussions on how to change navigation, improve look and feel, make it easier to find things, to visually distinguish between Xen, XCP, etc. content, and many more. This meant, that I spent a lot of time at this document day adding notes and adding issues to the TODO list and investigated how we could fix some issues that were identified.

This led to new sections in the TODO list, e.g. Mediwiki Issues and XCP : Open work items. Also we had new contributors, in particular User:Double-p (who helped categorize many pages) and User:WeiLiu. This shows that adding the http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Easy_tasks_for_Beginners section to the TODO as came out of the last docs day, was the right thing to do.

For detailed acknowledgements, see http://wiki.xen.org/wiki/Xen_Document_Days/Acknowledgements/Jan2013 - I was not aware of any docsday related patches. If I missed you, please add yourself to the Acknowledgements page.

Thank you again! And see you on Feb 25th.

Best Regards
Lars
P.S.: Feel free to continue contributing to the wiki
--------------030603040502000303090605-- --===============7514345046409678484== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7514345046409678484==-- From xen-api-bounces@lists.xen.org Tue Jan 29 16:43:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 29 Jan 2013 16:43:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0EH8-00049y-BH; Tue, 29 Jan 2013 16:43:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0CkG-00028Y-TM for xen-api@lists.xen.org; Tue, 29 Jan 2013 15:05:09 +0000 Received: from [85.158.143.99:21712] by server-1.bemta-4.messagelabs.com id CD/B9-05635-425E7015; Tue, 29 Jan 2013 15:05:08 +0000 X-Env-Sender: chrsnlsn1610@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1359471905!22982019!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=2.9 required=7.0 tests=FROM_LOCAL_NOVOWEL, HTML_50_60, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22981 invoked from network); 29 Jan 2013 15:05:06 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 29 Jan 2013 15:05:06 -0000 Received: by mail-wi0-f173.google.com with SMTP id hn17so2541143wib.6 for ; Tue, 29 Jan 2013 07:05:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=90kIcSnQYHVBt/eWj+eY73BwoNy596jD83tfMMpMZxU=; b=W/Bl5VgkPTkc5gtTNbs68zWnblBW5N4xn8h3Eo9bWnPzRCCUzw7dV9b0+DVa4E8l67 egaix6Flf58YHM3QcNlVpOwDH1gGNemhTQgcOpHGCc7lgJw2HHaFzeRCoe6puLGwPNXI DKhoLrk2IOBQ7/GfkqMzvusNul483QeGutRBGBCJ2JJmAL5QkfXp1IxpwgS9/ehK4Sns 9pcy0XtT7tEU2cdiIMti50v2E1K1dND3npNMbyxSXmMxF7rTRkRm0insV5KuoMKV/6/Q xljSKiuRqIGQKcpjDu0InW00CVxKff5BsCg3WcnXQS/Gh18pcofhIQdXNcXYIffpDZKv HNJw== MIME-Version: 1.0 X-Received: by 10.194.108.101 with SMTP id hj5mr3107783wjb.6.1359471905751; Tue, 29 Jan 2013 07:05:05 -0800 (PST) Received: by 10.194.21.226 with HTTP; Tue, 29 Jan 2013 07:05:05 -0800 (PST) Date: Wed, 30 Jan 2013 00:05:05 +0900 Message-ID: From: nelson chris To: xen-api@lists.xen.org X-Mailman-Approved-At: Tue, 29 Jan 2013 16:43:10 +0000 Subject: [Xen-API] [XCP1.6]multiple VDI copy in xencenter / xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4129343886502770047==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4129343886502770047== Content-Type: multipart/alternative; boundary=047d7bf10a360640ab04d46eb82e --047d7bf10a360640ab04d46eb82e Content-Type: text/plain; charset=ISO-8859-1 Hi, I've been testing XCP 1.6 and found out it's impossible to copy a VDI with synchronous 2 xapi operations... I mean I tried to call 2 VDI.copy() for a single vdi simultaneously. First copy op. succeeded but the second copy op. failed with the following error message: *This operation cannot be performed because this VDI is in use by some other operation* *But if I use asynchronous copy operations, the second copy doesn't fail but it seems waiting in the queue 'till the first copy finishes.. And it seems that it is also applied to Citrix XenServer 6.1. **is it true?* *In citrix xenserver 6.0.2 it is allowed to call 2 synchronous copy xapis for a single vdi. Is there any other way to use this method in xs 6.1 or XCP 1.6?* * * *Thank you.* * * --047d7bf10a360640ab04d46eb82e Content-Type: text/html; charset=EUC-KR Content-Transfer-Encoding: quoted-printable
Hi, 
I've been testing XCP 1.6 and foun= d out it's impossible to copy a VDI with synchronous 2 xapi operations.= .. I mean  I tried to call 2 VDI.copy() for a single vdi simultan= eously. First copy op. succeeded but the second copy op. failed with the fo= llowing error message: This operation cannot be performed because this VDI is in use by some oth= er operation
But if I u= se asynchronous copy operations, the second copy doesn't fail but it se= ems waiting in the queue 'till the first copy finishes.. And it seems t= hat it is also applied to Citrix XenServer 6.1. is it true?=

In citrix xenserver 6.0.2 it is allowed to= call 2 synchronous copy xapis for a single vdi. Is there any other way to = use this method in xs 6.1 or XCP 1.6?

Thank you.


--047d7bf10a360640ab04d46eb82e-- --===============4129343886502770047== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4129343886502770047==-- From xen-api-bounces@lists.xen.org Tue Jan 29 16:43:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 29 Jan 2013 16:43:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0EH8-00049y-BH; Tue, 29 Jan 2013 16:43:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0CkG-00028Y-TM for xen-api@lists.xen.org; Tue, 29 Jan 2013 15:05:09 +0000 Received: from [85.158.143.99:21712] by server-1.bemta-4.messagelabs.com id CD/B9-05635-425E7015; Tue, 29 Jan 2013 15:05:08 +0000 X-Env-Sender: chrsnlsn1610@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1359471905!22982019!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=2.9 required=7.0 tests=FROM_LOCAL_NOVOWEL, HTML_50_60, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22981 invoked from network); 29 Jan 2013 15:05:06 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 29 Jan 2013 15:05:06 -0000 Received: by mail-wi0-f173.google.com with SMTP id hn17so2541143wib.6 for ; Tue, 29 Jan 2013 07:05:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=90kIcSnQYHVBt/eWj+eY73BwoNy596jD83tfMMpMZxU=; b=W/Bl5VgkPTkc5gtTNbs68zWnblBW5N4xn8h3Eo9bWnPzRCCUzw7dV9b0+DVa4E8l67 egaix6Flf58YHM3QcNlVpOwDH1gGNemhTQgcOpHGCc7lgJw2HHaFzeRCoe6puLGwPNXI DKhoLrk2IOBQ7/GfkqMzvusNul483QeGutRBGBCJ2JJmAL5QkfXp1IxpwgS9/ehK4Sns 9pcy0XtT7tEU2cdiIMti50v2E1K1dND3npNMbyxSXmMxF7rTRkRm0insV5KuoMKV/6/Q xljSKiuRqIGQKcpjDu0InW00CVxKff5BsCg3WcnXQS/Gh18pcofhIQdXNcXYIffpDZKv HNJw== MIME-Version: 1.0 X-Received: by 10.194.108.101 with SMTP id hj5mr3107783wjb.6.1359471905751; Tue, 29 Jan 2013 07:05:05 -0800 (PST) Received: by 10.194.21.226 with HTTP; Tue, 29 Jan 2013 07:05:05 -0800 (PST) Date: Wed, 30 Jan 2013 00:05:05 +0900 Message-ID: From: nelson chris To: xen-api@lists.xen.org X-Mailman-Approved-At: Tue, 29 Jan 2013 16:43:10 +0000 Subject: [Xen-API] [XCP1.6]multiple VDI copy in xencenter / xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4129343886502770047==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4129343886502770047== Content-Type: multipart/alternative; boundary=047d7bf10a360640ab04d46eb82e --047d7bf10a360640ab04d46eb82e Content-Type: text/plain; charset=ISO-8859-1 Hi, I've been testing XCP 1.6 and found out it's impossible to copy a VDI with synchronous 2 xapi operations... I mean I tried to call 2 VDI.copy() for a single vdi simultaneously. First copy op. succeeded but the second copy op. failed with the following error message: *This operation cannot be performed because this VDI is in use by some other operation* *But if I use asynchronous copy operations, the second copy doesn't fail but it seems waiting in the queue 'till the first copy finishes.. And it seems that it is also applied to Citrix XenServer 6.1. **is it true?* *In citrix xenserver 6.0.2 it is allowed to call 2 synchronous copy xapis for a single vdi. Is there any other way to use this method in xs 6.1 or XCP 1.6?* * * *Thank you.* * * --047d7bf10a360640ab04d46eb82e Content-Type: text/html; charset=EUC-KR Content-Transfer-Encoding: quoted-printable
Hi, 
I've been testing XCP 1.6 and foun= d out it's impossible to copy a VDI with synchronous 2 xapi operations.= .. I mean  I tried to call 2 VDI.copy() for a single vdi simultan= eously. First copy op. succeeded but the second copy op. failed with the fo= llowing error message: This operation cannot be performed because this VDI is in use by some oth= er operation
But if I u= se asynchronous copy operations, the second copy doesn't fail but it se= ems waiting in the queue 'till the first copy finishes.. And it seems t= hat it is also applied to Citrix XenServer 6.1. is it true?=

In citrix xenserver 6.0.2 it is allowed to= call 2 synchronous copy xapis for a single vdi. Is there any other way to = use this method in xs 6.1 or XCP 1.6?

Thank you.


--047d7bf10a360640ab04d46eb82e-- --===============4129343886502770047== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4129343886502770047==-- From xen-api-bounces@lists.xen.org Wed Jan 30 09:04:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 09:04:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0Tap-0007rG-9U; Wed, 30 Jan 2013 09:04:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0Tan-0007r9-PK for xen-api@lists.xen.org; Wed, 30 Jan 2013 09:04:29 +0000 Received: from [85.158.138.51:4423] by server-4.bemta-3.messagelabs.com id 83/41-12802-812E8015; Wed, 30 Jan 2013 09:04:24 +0000 X-Env-Sender: peter.broennimann@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1359536663!28423779!1 X-Originating-IP: [209.85.215.179] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9789 invoked from network); 30 Jan 2013 09:04:23 -0000 Received: from mail-ea0-f179.google.com (HELO mail-ea0-f179.google.com) (209.85.215.179) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 09:04:23 -0000 Received: by mail-ea0-f179.google.com with SMTP id d12so557872eaa.38 for ; Wed, 30 Jan 2013 01:04:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=kuW+WmpviP9l394equ6/TOVl4lQwGR1tLdtHLOOIKU4=; b=0i74vQeN4lFLXnNEAa6fGC52K1XkFeLZntSw9zSz8HIC7nzLHPQ6mEHzRZuGpsyEI4 e9dm9tjafaH1IKX5V5N99nrgdaSrIwtN/Ipz4mXcO3/+R2pTA5/ew4934yapClBsQVL/ +N/6qRzYrXlNWAqxf/nzrxYmkjJd7nNAY2EpPhnf3hsiV35M7zN4OKhzA4TJc/H7tY/+ mdLrqbagbyV18cOYUrDX+lcER7+RI4bOLPBiyE9s5EUEYoDW1b+G8aGCpgMifhD9Uk0g yS2wA4s+Sj7MFJmyes35kntF3j1AHthgfAnjaK5qp/A3VxoCD+/LsmcsHyQrN69mhg81 reeA== X-Received: by 10.14.173.196 with SMTP id v44mr12988022eel.29.1359536663208; Wed, 30 Jan 2013 01:04:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.189.12 with HTTP; Wed, 30 Jan 2013 01:04:02 -0800 (PST) From: "P. Broennimann" Date: Wed, 30 Jan 2013 10:04:02 +0100 Message-ID: To: xen-api@lists.xen.org Subject: [Xen-API] XCP Guests Time Sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6000677532641095072==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6000677532641095072== Content-Type: multipart/alternative; boundary=047d7b604368dea14b04d47dcb5b --047d7b604368dea14b04d47dcb5b Content-Type: text/plain; charset=ISO-8859-1 Hi there I found various posts on this but it is still not 100% clear to me. I have two servers (with XCP 1.6) each running a handfull of Debian guests. What is the best method to have the same time on all Debian guests? (On both servers there is a PostgreSQL database running in a master <-> master replication configuration so I am interested in having everywhere the same time). I see the following solutions: 1) Each Debian guest has its own ntp client. 2) XCP uses ntp to sync its own time and all guests then sync themselves with XCP. 3) ??? Btw, does the installation of the "xs-tools" help in syncing times? Thanks & cheers, Peter --047d7b604368dea14b04d47dcb5b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi there

I found various posts on this but it is still n= ot 100% clear to me.

I have two servers = (with XCP 1.6) each running a handfull of Debian guests.
<= font face=3D"courier new, monospace">
What is the best method to have the same time on all = Debian guests? (On both servers there is a PostgreSQL database running in a= master <-> master replication configuration so I am interested in ha= ving everywhere the same time).

I see the following solutions:

1) Each Debian guest has its own ntp client.=
2) XCP uses ntp to sync its own = time and all guests then sync themselves with XCP.
3) ???

Btw, does the insta= llation of the "xs-tools" help in syncing times?

Thanks & cheers,
Peter
--047d7b604368dea14b04d47dcb5b-- --===============6000677532641095072== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6000677532641095072==-- From xen-api-bounces@lists.xen.org Wed Jan 30 09:04:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 09:04:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0Tap-0007rG-9U; Wed, 30 Jan 2013 09:04:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0Tan-0007r9-PK for xen-api@lists.xen.org; Wed, 30 Jan 2013 09:04:29 +0000 Received: from [85.158.138.51:4423] by server-4.bemta-3.messagelabs.com id 83/41-12802-812E8015; Wed, 30 Jan 2013 09:04:24 +0000 X-Env-Sender: peter.broennimann@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1359536663!28423779!1 X-Originating-IP: [209.85.215.179] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9789 invoked from network); 30 Jan 2013 09:04:23 -0000 Received: from mail-ea0-f179.google.com (HELO mail-ea0-f179.google.com) (209.85.215.179) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 09:04:23 -0000 Received: by mail-ea0-f179.google.com with SMTP id d12so557872eaa.38 for ; Wed, 30 Jan 2013 01:04:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=kuW+WmpviP9l394equ6/TOVl4lQwGR1tLdtHLOOIKU4=; b=0i74vQeN4lFLXnNEAa6fGC52K1XkFeLZntSw9zSz8HIC7nzLHPQ6mEHzRZuGpsyEI4 e9dm9tjafaH1IKX5V5N99nrgdaSrIwtN/Ipz4mXcO3/+R2pTA5/ew4934yapClBsQVL/ +N/6qRzYrXlNWAqxf/nzrxYmkjJd7nNAY2EpPhnf3hsiV35M7zN4OKhzA4TJc/H7tY/+ mdLrqbagbyV18cOYUrDX+lcER7+RI4bOLPBiyE9s5EUEYoDW1b+G8aGCpgMifhD9Uk0g yS2wA4s+Sj7MFJmyes35kntF3j1AHthgfAnjaK5qp/A3VxoCD+/LsmcsHyQrN69mhg81 reeA== X-Received: by 10.14.173.196 with SMTP id v44mr12988022eel.29.1359536663208; Wed, 30 Jan 2013 01:04:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.189.12 with HTTP; Wed, 30 Jan 2013 01:04:02 -0800 (PST) From: "P. Broennimann" Date: Wed, 30 Jan 2013 10:04:02 +0100 Message-ID: To: xen-api@lists.xen.org Subject: [Xen-API] XCP Guests Time Sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6000677532641095072==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6000677532641095072== Content-Type: multipart/alternative; boundary=047d7b604368dea14b04d47dcb5b --047d7b604368dea14b04d47dcb5b Content-Type: text/plain; charset=ISO-8859-1 Hi there I found various posts on this but it is still not 100% clear to me. I have two servers (with XCP 1.6) each running a handfull of Debian guests. What is the best method to have the same time on all Debian guests? (On both servers there is a PostgreSQL database running in a master <-> master replication configuration so I am interested in having everywhere the same time). I see the following solutions: 1) Each Debian guest has its own ntp client. 2) XCP uses ntp to sync its own time and all guests then sync themselves with XCP. 3) ??? Btw, does the installation of the "xs-tools" help in syncing times? Thanks & cheers, Peter --047d7b604368dea14b04d47dcb5b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi there

I found various posts on this but it is still n= ot 100% clear to me.

I have two servers = (with XCP 1.6) each running a handfull of Debian guests.
<= font face=3D"courier new, monospace">
What is the best method to have the same time on all = Debian guests? (On both servers there is a PostgreSQL database running in a= master <-> master replication configuration so I am interested in ha= ving everywhere the same time).

I see the following solutions:

1) Each Debian guest has its own ntp client.=
2) XCP uses ntp to sync its own = time and all guests then sync themselves with XCP.
3) ???

Btw, does the insta= llation of the "xs-tools" help in syncing times?

Thanks & cheers,
Peter
--047d7b604368dea14b04d47dcb5b-- --===============6000677532641095072== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6000677532641095072==-- From xen-api-bounces@lists.xen.org Wed Jan 30 10:25:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 10:25:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0UrV-0001Sv-5W; Wed, 30 Jan 2013 10:25:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0UrT-0001Sq-D7 for xen-api@lists.xen.org; Wed, 30 Jan 2013 10:25:47 +0000 Received: from [85.158.143.35:62229] by server-3.bemta-4.messagelabs.com id 58/93-08920-A25F8015; Wed, 30 Jan 2013 10:25:46 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-6.tower-21.messagelabs.com!1359541514!15780073!1 X-Originating-IP: [80.12.242.130] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23515 invoked from network); 30 Jan 2013 10:25:15 -0000 Received: from smtp08.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.130) by server-6.tower-21.messagelabs.com with SMTP; 30 Jan 2013 10:25:15 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d16 with ME id uARB1k00T3zjds103ARBL1; Wed, 30 Jan 2013 11:25:11 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 576CA161BB8; Wed, 30 Jan 2013 11:25:11 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1dAyPqTU5ha; Wed, 30 Jan 2013 11:25:10 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A8E2C161BBB; Wed, 30 Jan 2013 11:25:10 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id fTYuRn77z6Jm; Wed, 30 Jan 2013 11:25:09 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 8A589161BB8; Wed, 30 Jan 2013 11:25:09 +0100 (CET) Message-ID: <5108F505.6070703@tranquil-it-systems.fr> Date: Wed, 30 Jan 2013 11:25:09 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "P. Broennimann" References: In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP Guests Time Sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Peter, > I found various posts on this but it is still not 100% clear to me. > > I have two servers (with XCP 1.6) each running a handfull of Debian guest= s. > > What is the best method to have the same time on all Debian guests? (On > both servers there is a PostgreSQL database running in a master <-> > master replication configuration so I am interested in having everywhere > the same time). > > I see the following solutions: > > 1) Each Debian guest has its own ntp client. > 2) XCP uses ntp to sync its own time and all guests then sync themselves > with XCP. > 3) ??? you can get available clocksource on your current xen kernel looking at = the following /sys pseudo-file (I think in that clocksource is on a = stock debian xen kernel, you may get something different if you install = the xcp kernel). cat /sys/devices/system/clocksource/clocksource0/available_clocksource And you can get the current clocksource looking at cat /sys/devices/system/clocksource/clocksource0/current_clocksource To my knowledge there is a magical clock source that is supposed to sync = the dom0 and domU time in community XCP, but I was more succesfull at = having independant clock and using ntp in all the domU. You may find some more information on this page http://wiki.debian.org/Xen/Clocksource > Btw, does the installation of the "xs-tools" help in syncing times? I don't think so, I always have to install ntp client in my domUs. = Actually my nagios complains when time drift above 1 seconds, and I have = 600+ XCP VMs that are in the green, so I guess this method works fine :-) Cheers, Denis > > Thanks & cheers, > Peter > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 10:25:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 10:25:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0UrV-0001Sv-5W; Wed, 30 Jan 2013 10:25:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0UrT-0001Sq-D7 for xen-api@lists.xen.org; Wed, 30 Jan 2013 10:25:47 +0000 Received: from [85.158.143.35:62229] by server-3.bemta-4.messagelabs.com id 58/93-08920-A25F8015; Wed, 30 Jan 2013 10:25:46 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-6.tower-21.messagelabs.com!1359541514!15780073!1 X-Originating-IP: [80.12.242.130] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23515 invoked from network); 30 Jan 2013 10:25:15 -0000 Received: from smtp08.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.130) by server-6.tower-21.messagelabs.com with SMTP; 30 Jan 2013 10:25:15 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d16 with ME id uARB1k00T3zjds103ARBL1; Wed, 30 Jan 2013 11:25:11 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 576CA161BB8; Wed, 30 Jan 2013 11:25:11 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1dAyPqTU5ha; Wed, 30 Jan 2013 11:25:10 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A8E2C161BBB; Wed, 30 Jan 2013 11:25:10 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id fTYuRn77z6Jm; Wed, 30 Jan 2013 11:25:09 +0100 (CET) Received: from srvlts1.tranquil.it (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 8A589161BB8; Wed, 30 Jan 2013 11:25:09 +0100 (CET) Message-ID: <5108F505.6070703@tranquil-it-systems.fr> Date: Wed, 30 Jan 2013 11:25:09 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "P. Broennimann" References: In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP Guests Time Sync X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Peter, > I found various posts on this but it is still not 100% clear to me. > > I have two servers (with XCP 1.6) each running a handfull of Debian guest= s. > > What is the best method to have the same time on all Debian guests? (On > both servers there is a PostgreSQL database running in a master <-> > master replication configuration so I am interested in having everywhere > the same time). > > I see the following solutions: > > 1) Each Debian guest has its own ntp client. > 2) XCP uses ntp to sync its own time and all guests then sync themselves > with XCP. > 3) ??? you can get available clocksource on your current xen kernel looking at = the following /sys pseudo-file (I think in that clocksource is on a = stock debian xen kernel, you may get something different if you install = the xcp kernel). cat /sys/devices/system/clocksource/clocksource0/available_clocksource And you can get the current clocksource looking at cat /sys/devices/system/clocksource/clocksource0/current_clocksource To my knowledge there is a magical clock source that is supposed to sync = the dom0 and domU time in community XCP, but I was more succesfull at = having independant clock and using ntp in all the domU. You may find some more information on this page http://wiki.debian.org/Xen/Clocksource > Btw, does the installation of the "xs-tools" help in syncing times? I don't think so, I always have to install ntp client in my domUs. = Actually my nagios complains when time drift above 1 seconds, and I have = 600+ XCP VMs that are in the green, so I guess this method works fine :-) Cheers, Denis > > Thanks & cheers, > Peter > > > This body part will be downloaded on demand. > -- = Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, b=E2timent A 12 avenue Jules Verne 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 17:31:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 17:31:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0bVK-0000b2-WE; Wed, 30 Jan 2013 17:31:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0bVI-0000ax-RB for xen-api@lists.xen.org; Wed, 30 Jan 2013 17:31:21 +0000 Received: from [85.158.143.99:4053] by server-1.bemta-4.messagelabs.com id 8C/79-08839-8E859015; Wed, 30 Jan 2013 17:31:20 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1359567077!22660294!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1445 invoked from network); 30 Jan 2013 17:31:18 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-11.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jan 2013 17:31:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:MIME-Version; b=hu1IAg7OO/RbOmc7RGxadc9Ns/i8EANWHF8aaznc3onT+uDh4nWRow5fKZLvPxq3uH6WrPKy526jpsw/UWkj+8LEPxsTTR9SygEox7kWS9b1mqHJkIBR20D6JhCwF0mG; Received: from [192.168.1.29] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1U0bVF-0008BI-Ha for xen-api@lists.xen.org; Wed, 30 Jan 2013 09:31:17 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-004-sfo.servepath.com ([::1]) with mapi; Wed, 30 Jan 2013 09:31:16 -0800 From: Brian Menges To: "xen-api@lists.xen.org" Date: Wed, 30 Jan 2013 09:31:14 -0800 Thread-Topic: xe sr-create failed Thread-Index: Ac3+yQCzeUjLfXwvRJ2JTdZI8PLXAgARXVLg Message-ID: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6194780081806331579==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6194780081806331579== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3968CAC7E1BE7242B18501F292F3C7F16819879EEX004SFOservepa_" --_000_3968CAC7E1BE7242B18501F292F3C7F16819879EEX004SFOservepa_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a pool setup with two xcp 1.6 61809c builds. I destroyed the local s= torage sr on both hosts, and attempted to re-create them. On the first host= I was able to successfully do this, but on the second host I keep getting = failures: [root@xs-04 ~]# ls -la /dev/disk/by-id/ total 0 drwxr-xr-x 2 root root 140 Jan 30 08:56 . drwxr-xr-x 8 root root 160 Jan 30 08:56 .. lrwxrwxrwx 1 root root 9 Jan 30 08:56 scsi-3600605b003349b30189b8956b2716= 1a6 -> ../../sdb lrwxrwxrwx 1 root root 9 Jan 30 08:56 scsi-SATA_Hitachi_HTS7250100521PCK2= 00VJHJKU5J -> ../../sda lrwxrwxrwx 1 root root 10 Jan 30 08:56 scsi-SATA_Hitachi_HTS7250100521PCK2= 00VJHJKU5J-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 30 08:56 scsi-SATA_Hitachi_HTS7250100521PCK2= 00VJHJKU5J-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Jan 30 08:56 scsi-SATA_Hitachi_HTS7250100521PCK2= 00VJHJKU5J-part3 -> ../../sda3 [root@xs-04 ~]# xe host-list uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f name-label ( RW): xs-03. name-description ( RW): Default install of XenServer uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 name-label ( RW): xs-04. name-description ( RW): Default install of XenServer [root@xs-04 ~]# xe sr-create content-type=3Duser type=3Dlvm shared=3Dfalse = name-label=3D'Local storage' device-config:device=3D/dev/disk/by-id/scsi-36= 00605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 Error code: SR_BACKEND_FAILURE_19 Error parameters: , No such device [opterr=3DDevice /dev/disk/by-id/scsi-36= 00605b003349b30189b8956b27161a6 does not exist], ... uh, yeah, it does exist! [root@xs-04 ~]# grep -R '3600605b003349b30189b8956b27161a6' /var/log/* /var/log/messages:Jan 30 08:43:53 xs-04 xapi: [ info|xs-04.|2893 UNIX= /var/xapi/xapi||cli] xe sr-create password=3Dnull content-type=3Duser type= =3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device=3D/de= v/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-47= 93-a3e8-dc5c830c8e20 username=3Droot /var/log/messages:Jan 30 09:22:38 xs-04 xapi: [ info|xs-04.|3175 UNIX= /var/xapi/xapi||cli] xe sr-create password=3Dnull content-type=3Duser type= =3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device=3D/de= v/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-47= 93-a3e8-dc5c830c8e20 username=3Droot /var/log/xensource.log:Jan 30 08:43:53 xs-04 xapi: [ info|xs-04.|2893= UNIX /var/xapi/xapi||cli] xe sr-create password=3Dnull content-type=3Duser= type=3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device= =3D/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-b= ca4-4793-a3e8-dc5c830c8e20 username=3Droot /var/log/xensource.log:Jan 30 09:22:38 xs-04 xapi: [ info|xs-04.|3175= UNIX /var/xapi/xapi||cli] xe sr-create password=3Dnull content-type=3Duser= type=3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device= =3D/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-b= ca4-4793-a3e8-dc5c830c8e20 username=3Droot What's going on here? The logs don't show any errors... even searching up t= o 10 lines after this device match. Is this a problem because I have these in a pool? - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of P. Broennimann Sent: Wednesday, January 30, 2013 01:04 To: xen-api@lists.xen.org Subject: [Xen-API] XCP Guests Time Sync Hi there I found various posts on this but it is still not 100% clear to me. I have two servers (with XCP 1.6) each running a handfull of Debian guests. What is the best method to have the same time on all Debian guests? (On bot= h servers there is a PostgreSQL database running in a master <-> master rep= lication configuration so I am interested in having everywhere the same tim= e). I see the following solutions: 1) Each Debian guest has its own ntp client. 2) XCP uses ntp to sync its own time and all guests then sync themselves wi= th XCP. 3) ??? Btw, does the installation of the "xs-tools" help in syncing times? Thanks & cheers, Peter ________________________________ The information contained in this message, and any attachments, may contain= confidential and legally privileged material. It is solely for the use of = the person or entity to which it is addressed. Any review, retransmission, = dissemination, or action taken in reliance upon this information by persons= or entities other than the intended recipient is prohibited. If you receiv= e this in error, please contact the sender and delete the material from any= computer. --_000_3968CAC7E1BE7242B18501F292F3C7F16819879EEX004SFOservepa_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I have a pool setup with = two xcp 1.6 61809c builds. I destroyed the local storage sr on both hosts, = and attempted to re-create them. On the first host I was able to successfully do this, but on the second host I keep getting failur= es:

 <= /p>

[root@xs-04 ~]# ls -la /dev/disk/by-id/<= /o:p>

total 0

drwxr-xr-x 2 root root 140 Jan 30 08:56 .

drwxr-xr-x 8 root root 160 Jan 30 08:56 ..

lrwxrwxrwx 1 root root   9 Jan 30 0= 8:56 scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb

lrwxrwxrwx 1 root root   9 Jan 30 0= 8:56 scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda

lrwxrwxrwx 1 root root  10 Jan 30 08:56 = scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1

lrwxrwxrwx 1 root root  10 Jan 30 08:56 = scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2

lrwxrwxrwx 1 root root  10 Jan 30 08:56 = scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3

[root@xs-04 ~]# xe host-list

uuid ( RO)      = ;          : 6a5f2a4f-8f73-47c= 5-a4cf-09817777a55f

       &nb= sp;  name-label ( RW): xs-03.<FQDN>

    name-description ( RW): De= fault install of XenServer

 

 

uuid ( RO)      = ;          : 5b73d60a-bca4-479= 3-a3e8-dc5c830c8e20

       &nb= sp;  name-label ( RW): xs-04. <FQDN>

    name-description ( RW): De= fault install of XenServer

 

 

[root@xs-04 ~]# xe sr-create content-type=3Du= ser type=3Dlvm shared=3Dfalse name-label=3D'Local storage' device-config:de= vice=3D/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20

Error code: SR_BACKEND_FAILURE_19<= /span>

Error parameters: , No such device [opterr=3D= Device /dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 does not exis= t],

 <= /p>

… uh, yeah, it does= exist!

 <= /p>

[root@xs-04 ~]# grep -R '3600605b003349b30189= b8956b27161a6' /var/log/*

/var/log/messages:Jan 30 08:43:53 xs-04 xapi:= [ info|xs-04.<FQDN>|2893 UNIX /var/xapi/xapi||cli] xe sr-create pass= word=3Dnull content-type=3Duser type=3Dlvm shared=3Dfalse name-label=3DLoca= l storage device-config:device=3D/dev/disk/by-id/scsi-3600605b003349b30189b8= 956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=3Droot

/var/log/messages:Jan 30 09:22:38 xs-04 xapi:= [ info|xs-04.<FQDN>|3175 UNIX /var/xapi/xapi||cli] xe sr-create pass= word=3Dnull content-type=3Duser type=3Dlvm shared=3Dfalse name-label=3DLoca= l storage device-config:device=3D/dev/disk/by-id/scsi-3600605b003349b30189b8= 956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=3Droot

/var/log/xensource.log:Jan 30 08:43:53 xs-04 = xapi: [ info|xs-04.<FQDN>|2893 UNIX /var/xapi/xapi||cli] xe sr-create= password=3Dnull content-type=3Duser type=3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device=3D/dev/disk/by-id/scsi-360= 0605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 = username=3Droot

/var/log/xensource.log:Jan 30 09:22:38 xs-04 = xapi: [ info|xs-04.<FQDN>|3175 UNIX /var/xapi/xapi||cli] xe sr-create= password=3Dnull content-type=3Duser type=3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device=3D/dev/disk/by-id/scsi-360= 0605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 = username=3Droot

 <= /p>

What’s going on her= e? The logs don’t show any errors… even searching up to 10 line= s after this device match.

 <= /p>

Is this a problem because= I have these in a pool?

 <= /p>

- Brian Menges=

Principal Engineer, DevOp= s

GoGrid | ServePath | Colo= Serve | UpStream Networks

 <= /p>

From: xen-api-= bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of P. Broennimann
Sent: Wednesday, January 30, 2013 01:04
To: xen-api@lists.xen.org
Subject: [Xen-API] XCP Guests Time Sync

 

= Hi there

 

= I found various posts on this but it is still not 100% clear to me.<= o:p>

 

= I have two servers (with XCP 1.6) each running a handfull of Debian guests.=

 

= What is the best method to have the same time on all Debian guests? (On bot= h servers there is a PostgreSQL database running in a master <-> mast= er replication configuration so I am interested in having everywhere the same time).

 

= I see the following solutions:

 

= 1) Each Debian guest has its own ntp client.

= 2) XCP uses ntp to sync its own time and all guests then sync themselves wi= th XCP.

= 3) ???

 

= Btw, does the installation of the "xs-tools" help in syncing time= s?

 

= Thanks & cheers,

= Peter


The information contai= ned in this message, and any attachments, may contain confidential and lega= lly privileged material. It is solely for the use of the person or entity t= o which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by person= s or entities other than the intended recipient is prohibited. If you recei= ve this in error, please contact the sender and delete the material from an= y computer.
 --_000_3968CAC7E1BE7242B18501F292F3C7F16819879EEX004SFOservepa_-- --===============6194780081806331579== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6194780081806331579==-- From xen-api-bounces@lists.xen.org Wed Jan 30 17:31:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 17:31:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0bVK-0000b2-WE; Wed, 30 Jan 2013 17:31:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0bVI-0000ax-RB for xen-api@lists.xen.org; Wed, 30 Jan 2013 17:31:21 +0000 Received: from [85.158.143.99:4053] by server-1.bemta-4.messagelabs.com id 8C/79-08839-8E859015; Wed, 30 Jan 2013 17:31:20 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1359567077!22660294!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1445 invoked from network); 30 Jan 2013 17:31:18 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-11.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jan 2013 17:31:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:MIME-Version; b=hu1IAg7OO/RbOmc7RGxadc9Ns/i8EANWHF8aaznc3onT+uDh4nWRow5fKZLvPxq3uH6WrPKy526jpsw/UWkj+8LEPxsTTR9SygEox7kWS9b1mqHJkIBR20D6JhCwF0mG; Received: from [192.168.1.29] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1U0bVF-0008BI-Ha for xen-api@lists.xen.org; Wed, 30 Jan 2013 09:31:17 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-004-sfo.servepath.com ([::1]) with mapi; Wed, 30 Jan 2013 09:31:16 -0800 From: Brian Menges To: "xen-api@lists.xen.org" Date: Wed, 30 Jan 2013 09:31:14 -0800 Thread-Topic: xe sr-create failed Thread-Index: Ac3+yQCzeUjLfXwvRJ2JTdZI8PLXAgARXVLg Message-ID: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6194780081806331579==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6194780081806331579== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3968CAC7E1BE7242B18501F292F3C7F16819879EEX004SFOservepa_" --_000_3968CAC7E1BE7242B18501F292F3C7F16819879EEX004SFOservepa_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a pool setup with two xcp 1.6 61809c builds. I destroyed the local s= torage sr on both hosts, and attempted to re-create them. On the first host= I was able to successfully do this, but on the second host I keep getting = failures: [root@xs-04 ~]# ls -la /dev/disk/by-id/ total 0 drwxr-xr-x 2 root root 140 Jan 30 08:56 . drwxr-xr-x 8 root root 160 Jan 30 08:56 .. lrwxrwxrwx 1 root root 9 Jan 30 08:56 scsi-3600605b003349b30189b8956b2716= 1a6 -> ../../sdb lrwxrwxrwx 1 root root 9 Jan 30 08:56 scsi-SATA_Hitachi_HTS7250100521PCK2= 00VJHJKU5J -> ../../sda lrwxrwxrwx 1 root root 10 Jan 30 08:56 scsi-SATA_Hitachi_HTS7250100521PCK2= 00VJHJKU5J-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 30 08:56 scsi-SATA_Hitachi_HTS7250100521PCK2= 00VJHJKU5J-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Jan 30 08:56 scsi-SATA_Hitachi_HTS7250100521PCK2= 00VJHJKU5J-part3 -> ../../sda3 [root@xs-04 ~]# xe host-list uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f name-label ( RW): xs-03. name-description ( RW): Default install of XenServer uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 name-label ( RW): xs-04. name-description ( RW): Default install of XenServer [root@xs-04 ~]# xe sr-create content-type=3Duser type=3Dlvm shared=3Dfalse = name-label=3D'Local storage' device-config:device=3D/dev/disk/by-id/scsi-36= 00605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 Error code: SR_BACKEND_FAILURE_19 Error parameters: , No such device [opterr=3DDevice /dev/disk/by-id/scsi-36= 00605b003349b30189b8956b27161a6 does not exist], ... uh, yeah, it does exist! [root@xs-04 ~]# grep -R '3600605b003349b30189b8956b27161a6' /var/log/* /var/log/messages:Jan 30 08:43:53 xs-04 xapi: [ info|xs-04.|2893 UNIX= /var/xapi/xapi||cli] xe sr-create password=3Dnull content-type=3Duser type= =3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device=3D/de= v/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-47= 93-a3e8-dc5c830c8e20 username=3Droot /var/log/messages:Jan 30 09:22:38 xs-04 xapi: [ info|xs-04.|3175 UNIX= /var/xapi/xapi||cli] xe sr-create password=3Dnull content-type=3Duser type= =3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device=3D/de= v/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-47= 93-a3e8-dc5c830c8e20 username=3Droot /var/log/xensource.log:Jan 30 08:43:53 xs-04 xapi: [ info|xs-04.|2893= UNIX /var/xapi/xapi||cli] xe sr-create password=3Dnull content-type=3Duser= type=3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device= =3D/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-b= ca4-4793-a3e8-dc5c830c8e20 username=3Droot /var/log/xensource.log:Jan 30 09:22:38 xs-04 xapi: [ info|xs-04.|3175= UNIX /var/xapi/xapi||cli] xe sr-create password=3Dnull content-type=3Duser= type=3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device= =3D/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-b= ca4-4793-a3e8-dc5c830c8e20 username=3Droot What's going on here? The logs don't show any errors... even searching up t= o 10 lines after this device match. Is this a problem because I have these in a pool? - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] = On Behalf Of P. Broennimann Sent: Wednesday, January 30, 2013 01:04 To: xen-api@lists.xen.org Subject: [Xen-API] XCP Guests Time Sync Hi there I found various posts on this but it is still not 100% clear to me. I have two servers (with XCP 1.6) each running a handfull of Debian guests. What is the best method to have the same time on all Debian guests? (On bot= h servers there is a PostgreSQL database running in a master <-> master rep= lication configuration so I am interested in having everywhere the same tim= e). I see the following solutions: 1) Each Debian guest has its own ntp client. 2) XCP uses ntp to sync its own time and all guests then sync themselves wi= th XCP. 3) ??? Btw, does the installation of the "xs-tools" help in syncing times? Thanks & cheers, Peter ________________________________ The information contained in this message, and any attachments, may contain= confidential and legally privileged material. It is solely for the use of = the person or entity to which it is addressed. Any review, retransmission, = dissemination, or action taken in reliance upon this information by persons= or entities other than the intended recipient is prohibited. If you receiv= e this in error, please contact the sender and delete the material from any= computer. --_000_3968CAC7E1BE7242B18501F292F3C7F16819879EEX004SFOservepa_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I have a pool setup with = two xcp 1.6 61809c builds. I destroyed the local storage sr on both hosts, = and attempted to re-create them. On the first host I was able to successfully do this, but on the second host I keep getting failur= es:

 <= /p>

[root@xs-04 ~]# ls -la /dev/disk/by-id/<= /o:p>

total 0

drwxr-xr-x 2 root root 140 Jan 30 08:56 .

drwxr-xr-x 8 root root 160 Jan 30 08:56 ..

lrwxrwxrwx 1 root root   9 Jan 30 0= 8:56 scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb

lrwxrwxrwx 1 root root   9 Jan 30 0= 8:56 scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda

lrwxrwxrwx 1 root root  10 Jan 30 08:56 = scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1

lrwxrwxrwx 1 root root  10 Jan 30 08:56 = scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2

lrwxrwxrwx 1 root root  10 Jan 30 08:56 = scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3

[root@xs-04 ~]# xe host-list

uuid ( RO)      = ;          : 6a5f2a4f-8f73-47c= 5-a4cf-09817777a55f

       &nb= sp;  name-label ( RW): xs-03.<FQDN>

    name-description ( RW): De= fault install of XenServer

 

 

uuid ( RO)      = ;          : 5b73d60a-bca4-479= 3-a3e8-dc5c830c8e20

       &nb= sp;  name-label ( RW): xs-04. <FQDN>

    name-description ( RW): De= fault install of XenServer

 

 

[root@xs-04 ~]# xe sr-create content-type=3Du= ser type=3Dlvm shared=3Dfalse name-label=3D'Local storage' device-config:de= vice=3D/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20

Error code: SR_BACKEND_FAILURE_19<= /span>

Error parameters: , No such device [opterr=3D= Device /dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 does not exis= t],

 <= /p>

… uh, yeah, it does= exist!

 <= /p>

[root@xs-04 ~]# grep -R '3600605b003349b30189= b8956b27161a6' /var/log/*

/var/log/messages:Jan 30 08:43:53 xs-04 xapi:= [ info|xs-04.<FQDN>|2893 UNIX /var/xapi/xapi||cli] xe sr-create pass= word=3Dnull content-type=3Duser type=3Dlvm shared=3Dfalse name-label=3DLoca= l storage device-config:device=3D/dev/disk/by-id/scsi-3600605b003349b30189b8= 956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=3Droot

/var/log/messages:Jan 30 09:22:38 xs-04 xapi:= [ info|xs-04.<FQDN>|3175 UNIX /var/xapi/xapi||cli] xe sr-create pass= word=3Dnull content-type=3Duser type=3Dlvm shared=3Dfalse name-label=3DLoca= l storage device-config:device=3D/dev/disk/by-id/scsi-3600605b003349b30189b8= 956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=3Droot

/var/log/xensource.log:Jan 30 08:43:53 xs-04 = xapi: [ info|xs-04.<FQDN>|2893 UNIX /var/xapi/xapi||cli] xe sr-create= password=3Dnull content-type=3Duser type=3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device=3D/dev/disk/by-id/scsi-360= 0605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 = username=3Droot

/var/log/xensource.log:Jan 30 09:22:38 xs-04 = xapi: [ info|xs-04.<FQDN>|3175 UNIX /var/xapi/xapi||cli] xe sr-create= password=3Dnull content-type=3Duser type=3Dlvm shared=3Dfalse name-label=3DLocal storage device-config:device=3D/dev/disk/by-id/scsi-360= 0605b003349b30189b8956b27161a6 uuid=3D5b73d60a-bca4-4793-a3e8-dc5c830c8e20 = username=3Droot

 <= /p>

What’s going on her= e? The logs don’t show any errors… even searching up to 10 line= s after this device match.

 <= /p>

Is this a problem because= I have these in a pool?

 <= /p>

- Brian Menges=

Principal Engineer, DevOp= s

GoGrid | ServePath | Colo= Serve | UpStream Networks

 <= /p>

From: xen-api-= bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of P. Broennimann
Sent: Wednesday, January 30, 2013 01:04
To: xen-api@lists.xen.org
Subject: [Xen-API] XCP Guests Time Sync

 

= Hi there

 

= I found various posts on this but it is still not 100% clear to me.<= o:p>

 

= I have two servers (with XCP 1.6) each running a handfull of Debian guests.=

 

= What is the best method to have the same time on all Debian guests? (On bot= h servers there is a PostgreSQL database running in a master <-> mast= er replication configuration so I am interested in having everywhere the same time).

 

= I see the following solutions:

 

= 1) Each Debian guest has its own ntp client.

= 2) XCP uses ntp to sync its own time and all guests then sync themselves wi= th XCP.

= 3) ???

 

= Btw, does the installation of the "xs-tools" help in syncing time= s?

 

= Thanks & cheers,

= Peter


The information contai= ned in this message, and any attachments, may contain confidential and lega= lly privileged material. It is solely for the use of the person or entity t= o which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by person= s or entities other than the intended recipient is prohibited. If you recei= ve this in error, please contact the sender and delete the material from an= y computer.
 --_000_3968CAC7E1BE7242B18501F292F3C7F16819879EEX004SFOservepa_-- --===============6194780081806331579== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6194780081806331579==-- From xen-api-bounces@lists.xen.org Wed Jan 30 18:05:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 18:05:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0c2H-0000vo-3s; Wed, 30 Jan 2013 18:05:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0c2F-0000vj-OK for xen-api@lists.xen.org; Wed, 30 Jan 2013 18:05:23 +0000 Received: from [85.158.137.99:11297] by server-7.bemta-3.messagelabs.com id 60/C6-10367-ED069015; Wed, 30 Jan 2013 18:05:18 +0000 X-Env-Sender: andrei.maslennikov@gmail.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1359569115!16092549!1 X-Originating-IP: [209.85.223.179] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25697 invoked from network); 30 Jan 2013 18:05:17 -0000 Received: from mail-ie0-f179.google.com (HELO mail-ie0-f179.google.com) (209.85.223.179) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 18:05:17 -0000 Received: by mail-ie0-f179.google.com with SMTP id k11so326281iea.24 for ; Wed, 30 Jan 2013 10:05:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=NL6rL8JeNRU+tRYuhNSRUzDgOOCDNuaxVx+YrQfQ9iE=; b=VpfOtY90bUweupXOdbnJEgwVeGqgrU6U3zhyK9si6BBKEi5bT4sh7MK+Wz1i6QtTnm JkyCWe+cj1wxuQPk1dGZusWZL9VpSwGFTHDDBJ2FbnY07R4QX6lkP91j6z7YCV9tnLEx AXRXgK0JYL86JWtumH1qGN/Jjfof7cTsgb2a8zr5k4KoS4d4eYHDEO55Cd0Hbyb+f+Il Wwog/7hcYbkh1OpYXrGRJRGhQ6WwULZZ7t1UJUu6oS3ep0Uxgvn56j2yJHndVhm1Mtte PF/fbhlO16luvWyV7IeeFV1xfzdZC9Zi63CmZtUe8mycuhko5FxhSszV+lOe46KHC8bo xOyg== MIME-Version: 1.0 X-Received: by 10.50.155.134 with SMTP id vw6mr1313150igb.34.1359569115356; Wed, 30 Jan 2013 10:05:15 -0800 (PST) Received: by 10.50.104.194 with HTTP; Wed, 30 Jan 2013 10:05:15 -0800 (PST) Date: Wed, 30 Jan 2013 19:05:15 +0100 Message-ID: From: Andrei Maslennikov To: xen-api@lists.xen.org Subject: [Xen-API] Infiniband suport in XCP? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1472944828032831475==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1472944828032831475== Content-Type: multipart/alternative; boundary=e89a8f3ba0b12b1f4b04d4855a5d --e89a8f3ba0b12b1f4b04d4855a5d Content-Type: text/plain; charset=ISO-8859-1 Hello, we might want to recycle some existing Infiniband infrastructure configuring a couple of SRP targets shared across the hypervisors. So far XCP does not support Infiniband, but probably somebody in the community had already done a step forward and made it working? Any comment would be very welcome. Thanks ahead - Andrei. --e89a8f3ba0b12b1f4b04d4855a5d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

we might want to recycle some existing Infiniband infrastruct= ure configuring a couple of SRP targets shared across the hypervisors. So f= ar XCP does not support Infiniband, but probably somebody=A0 in the communi= ty had already done a step forward and made it working?

Any comment would be very welcome.

Thanks ahead - Andrei.=A0 --e89a8f3ba0b12b1f4b04d4855a5d-- --===============1472944828032831475== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1472944828032831475==-- From xen-api-bounces@lists.xen.org Wed Jan 30 18:05:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 18:05:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0c2H-0000vo-3s; Wed, 30 Jan 2013 18:05:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0c2F-0000vj-OK for xen-api@lists.xen.org; Wed, 30 Jan 2013 18:05:23 +0000 Received: from [85.158.137.99:11297] by server-7.bemta-3.messagelabs.com id 60/C6-10367-ED069015; Wed, 30 Jan 2013 18:05:18 +0000 X-Env-Sender: andrei.maslennikov@gmail.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1359569115!16092549!1 X-Originating-IP: [209.85.223.179] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25697 invoked from network); 30 Jan 2013 18:05:17 -0000 Received: from mail-ie0-f179.google.com (HELO mail-ie0-f179.google.com) (209.85.223.179) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 18:05:17 -0000 Received: by mail-ie0-f179.google.com with SMTP id k11so326281iea.24 for ; Wed, 30 Jan 2013 10:05:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=NL6rL8JeNRU+tRYuhNSRUzDgOOCDNuaxVx+YrQfQ9iE=; b=VpfOtY90bUweupXOdbnJEgwVeGqgrU6U3zhyK9si6BBKEi5bT4sh7MK+Wz1i6QtTnm JkyCWe+cj1wxuQPk1dGZusWZL9VpSwGFTHDDBJ2FbnY07R4QX6lkP91j6z7YCV9tnLEx AXRXgK0JYL86JWtumH1qGN/Jjfof7cTsgb2a8zr5k4KoS4d4eYHDEO55Cd0Hbyb+f+Il Wwog/7hcYbkh1OpYXrGRJRGhQ6WwULZZ7t1UJUu6oS3ep0Uxgvn56j2yJHndVhm1Mtte PF/fbhlO16luvWyV7IeeFV1xfzdZC9Zi63CmZtUe8mycuhko5FxhSszV+lOe46KHC8bo xOyg== MIME-Version: 1.0 X-Received: by 10.50.155.134 with SMTP id vw6mr1313150igb.34.1359569115356; Wed, 30 Jan 2013 10:05:15 -0800 (PST) Received: by 10.50.104.194 with HTTP; Wed, 30 Jan 2013 10:05:15 -0800 (PST) Date: Wed, 30 Jan 2013 19:05:15 +0100 Message-ID: From: Andrei Maslennikov To: xen-api@lists.xen.org Subject: [Xen-API] Infiniband suport in XCP? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1472944828032831475==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1472944828032831475== Content-Type: multipart/alternative; boundary=e89a8f3ba0b12b1f4b04d4855a5d --e89a8f3ba0b12b1f4b04d4855a5d Content-Type: text/plain; charset=ISO-8859-1 Hello, we might want to recycle some existing Infiniband infrastructure configuring a couple of SRP targets shared across the hypervisors. So far XCP does not support Infiniband, but probably somebody in the community had already done a step forward and made it working? Any comment would be very welcome. Thanks ahead - Andrei. --e89a8f3ba0b12b1f4b04d4855a5d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

we might want to recycle some existing Infiniband infrastruct= ure configuring a couple of SRP targets shared across the hypervisors. So f= ar XCP does not support Infiniband, but probably somebody=A0 in the communi= ty had already done a step forward and made it working?

Any comment would be very welcome.

Thanks ahead - Andrei.=A0 --e89a8f3ba0b12b1f4b04d4855a5d-- --===============1472944828032831475== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1472944828032831475==-- From xen-api-bounces@lists.xen.org Wed Jan 30 18:17:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 18:17:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0cDj-00011n-5A; Wed, 30 Jan 2013 18:17:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0cDh-00011i-C3 for xen-api@lists.xen.org; Wed, 30 Jan 2013 18:17:13 +0000 Received: from [85.158.143.35:3064] by server-3.bemta-4.messagelabs.com id 11/5E-08920-8A369015; Wed, 30 Jan 2013 18:17:12 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1359569830!16460240!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTk2NDU=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10664 invoked from network); 30 Jan 2013 18:17:11 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 18:17:11 -0000 X-IronPort-AV: E=Sophos;i="4.84,569,1355097600"; d="scan'208";a="5398427" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 30 Jan 2013 18:17:10 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Wed, 30 Jan 2013 13:17:09 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U0cDd-0000yS-Fq; Wed, 30 Jan 2013 18:17:09 +0000 Message-ID: <510963A4.3010805@citrix.com> Date: Wed, 30 Jan 2013 18:17:08 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Brian Menges References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> In-Reply-To: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 30/01/13 17:31, Brian Menges wrote: > I have a pool setup with two xcp 1.6 61809c builds. I destroyed the > local storage sr on both hosts, and attempted to re-create them. On the > first host I was able to successfully do this, but on the second host I > keep getting failures: > > [root@xs-04 ~]# ls -la /dev/disk/by-id/ > > total 0 > > drwxr-xr-x 2 root root 140 Jan 30 08:56 . > > drwxr-xr-x 8 root root 160 Jan 30 08:56 .. > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3 > > [root@xs-04 ~]# xe host-list > > uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f > > name-label ( RW): xs-03. > > name-description ( RW): Default install of XenServer > > uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > name-label ( RW): xs-04. > > name-description ( RW): Default install of XenServer > > [root@xs-04 ~]# xe sr-create content-type=user type=lvm shared=false > name-label='Local storage' > device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 > uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > Error code: SR_BACKEND_FAILURE_19 Can you check /var/log/SMlog for errors? What does this say? Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 18:17:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 18:17:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0cDj-00011n-5A; Wed, 30 Jan 2013 18:17:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0cDh-00011i-C3 for xen-api@lists.xen.org; Wed, 30 Jan 2013 18:17:13 +0000 Received: from [85.158.143.35:3064] by server-3.bemta-4.messagelabs.com id 11/5E-08920-8A369015; Wed, 30 Jan 2013 18:17:12 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1359569830!16460240!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAyOTk2NDU=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10664 invoked from network); 30 Jan 2013 18:17:11 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 18:17:11 -0000 X-IronPort-AV: E=Sophos;i="4.84,569,1355097600"; d="scan'208";a="5398427" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 30 Jan 2013 18:17:10 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Wed, 30 Jan 2013 13:17:09 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U0cDd-0000yS-Fq; Wed, 30 Jan 2013 18:17:09 +0000 Message-ID: <510963A4.3010805@citrix.com> Date: Wed, 30 Jan 2013 18:17:08 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Brian Menges References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> In-Reply-To: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 30/01/13 17:31, Brian Menges wrote: > I have a pool setup with two xcp 1.6 61809c builds. I destroyed the > local storage sr on both hosts, and attempted to re-create them. On the > first host I was able to successfully do this, but on the second host I > keep getting failures: > > [root@xs-04 ~]# ls -la /dev/disk/by-id/ > > total 0 > > drwxr-xr-x 2 root root 140 Jan 30 08:56 . > > drwxr-xr-x 8 root root 160 Jan 30 08:56 .. > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3 > > [root@xs-04 ~]# xe host-list > > uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f > > name-label ( RW): xs-03. > > name-description ( RW): Default install of XenServer > > uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > name-label ( RW): xs-04. > > name-description ( RW): Default install of XenServer > > [root@xs-04 ~]# xe sr-create content-type=user type=lvm shared=false > name-label='Local storage' > device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 > uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > Error code: SR_BACKEND_FAILURE_19 Can you check /var/log/SMlog for errors? What does this say? Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 18:40:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 18:40:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0ca7-0001TA-32; Wed, 30 Jan 2013 18:40:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0ca6-0001T5-4X for xen-api@lists.xen.org; Wed, 30 Jan 2013 18:40:22 +0000 Received: from [85.158.143.99:61882] by server-2.bemta-4.messagelabs.com id 8B/4D-01597-51969015; Wed, 30 Jan 2013 18:40:21 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1359571218!17268042!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29465 invoked from network); 30 Jan 2013 18:40:20 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-16.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jan 2013 18:40:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:CC:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:Content-Transfer-Encoding:MIME-Version; b=GAqe3dOtj/QMfwcpt/R8mF+2p/d5mXZWVztSyYmRrDAurSWCEp2HOiwmuk8QlTIAxXDT27syWW46vgpBhCOataLIegxLKtZkZbRB2vqRi1/p/pr0+d591TENHXNGISsd; Received: from [192.168.1.12] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1U0ca3-0009Jh-6I; Wed, 30 Jan 2013 10:40:19 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-002-sfo.servepath.com ([::1]) with mapi; Wed, 30 Jan 2013 10:40:16 -0800 From: Brian Menges To: Mike McClurg Date: Wed, 30 Jan 2013 10:40:15 -0800 Thread-Topic: [Xen-API] xe sr-create failed Thread-Index: Ac3/FgjgCQl3SbIWT1qoEHS2FXSurQAAhihQ Message-ID: <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> <510963A4.3010805@citrix.com> In-Reply-To: <510963A4.3010805@citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org When I just re-ran the sr-create, I got nothing new in the SMlog The only error I get is from the command's output: Error code: SR_BACKEND_FAILURE_19 Error parameters: , No such device [opterr=Device /dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 does not exist], I don't see any other errors in messages, xensource.log. I do see info stuff in /var/log/messages: Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi||cli] xe sr-create password=null content-type=user type=lvm shared=false name-label=Local storage device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=root Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi|session.login_with_password D:c1ac97a0f35f|xapi] Session.create trackid=99cbed91b097c6aac2542c43c10b1be6 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 But that's about it. Would there be someplace where I can turn up some logging that may give a better hint? - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: Mike McClurg [mailto:mike.mcclurg@citrix.com] Sent: Wednesday, January 30, 2013 10:17 To: Brian Menges Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed On 30/01/13 17:31, Brian Menges wrote: > I have a pool setup with two xcp 1.6 61809c builds. I destroyed the > local storage sr on both hosts, and attempted to re-create them. On > the first host I was able to successfully do this, but on the second > host I keep getting failures: > > [root@xs-04 ~]# ls -la /dev/disk/by-id/ > > total 0 > > drwxr-xr-x 2 root root 140 Jan 30 08:56 . > > drwxr-xr-x 8 root root 160 Jan 30 08:56 .. > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3 > > [root@xs-04 ~]# xe host-list > > uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f > > name-label ( RW): xs-03. > > name-description ( RW): Default install of XenServer > > uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > name-label ( RW): xs-04. > > name-description ( RW): Default install of XenServer > > [root@xs-04 ~]# xe sr-create content-type=user type=lvm shared=false > name-label='Local storage' > device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27 > 161a6 > uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > Error code: SR_BACKEND_FAILURE_19 Can you check /var/log/SMlog for errors? What does this say? Mike The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 18:40:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 18:40:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0ca7-0001TA-32; Wed, 30 Jan 2013 18:40:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0ca6-0001T5-4X for xen-api@lists.xen.org; Wed, 30 Jan 2013 18:40:22 +0000 Received: from [85.158.143.99:61882] by server-2.bemta-4.messagelabs.com id 8B/4D-01597-51969015; Wed, 30 Jan 2013 18:40:21 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1359571218!17268042!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29465 invoked from network); 30 Jan 2013 18:40:20 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-16.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jan 2013 18:40:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:CC:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:Content-Transfer-Encoding:MIME-Version; b=GAqe3dOtj/QMfwcpt/R8mF+2p/d5mXZWVztSyYmRrDAurSWCEp2HOiwmuk8QlTIAxXDT27syWW46vgpBhCOataLIegxLKtZkZbRB2vqRi1/p/pr0+d591TENHXNGISsd; Received: from [192.168.1.12] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1U0ca3-0009Jh-6I; Wed, 30 Jan 2013 10:40:19 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-002-sfo.servepath.com ([::1]) with mapi; Wed, 30 Jan 2013 10:40:16 -0800 From: Brian Menges To: Mike McClurg Date: Wed, 30 Jan 2013 10:40:15 -0800 Thread-Topic: [Xen-API] xe sr-create failed Thread-Index: Ac3/FgjgCQl3SbIWT1qoEHS2FXSurQAAhihQ Message-ID: <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> <510963A4.3010805@citrix.com> In-Reply-To: <510963A4.3010805@citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org When I just re-ran the sr-create, I got nothing new in the SMlog The only error I get is from the command's output: Error code: SR_BACKEND_FAILURE_19 Error parameters: , No such device [opterr=Device /dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 does not exist], I don't see any other errors in messages, xensource.log. I do see info stuff in /var/log/messages: Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi||cli] xe sr-create password=null content-type=user type=lvm shared=false name-label=Local storage device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=root Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi|session.login_with_password D:c1ac97a0f35f|xapi] Session.create trackid=99cbed91b097c6aac2542c43c10b1be6 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 But that's about it. Would there be someplace where I can turn up some logging that may give a better hint? - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: Mike McClurg [mailto:mike.mcclurg@citrix.com] Sent: Wednesday, January 30, 2013 10:17 To: Brian Menges Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed On 30/01/13 17:31, Brian Menges wrote: > I have a pool setup with two xcp 1.6 61809c builds. I destroyed the > local storage sr on both hosts, and attempted to re-create them. On > the first host I was able to successfully do this, but on the second > host I keep getting failures: > > [root@xs-04 ~]# ls -la /dev/disk/by-id/ > > total 0 > > drwxr-xr-x 2 root root 140 Jan 30 08:56 . > > drwxr-xr-x 8 root root 160 Jan 30 08:56 .. > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3 > > [root@xs-04 ~]# xe host-list > > uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f > > name-label ( RW): xs-03. > > name-description ( RW): Default install of XenServer > > uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > name-label ( RW): xs-04. > > name-description ( RW): Default install of XenServer > > [root@xs-04 ~]# xe sr-create content-type=user type=lvm shared=false > name-label='Local storage' > device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27 > 161a6 > uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > Error code: SR_BACKEND_FAILURE_19 Can you check /var/log/SMlog for errors? What does this say? Mike The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 18:56:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 18:56:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0cpz-0001cT-JO; Wed, 30 Jan 2013 18:56:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0cpy-0001cO-Cl for xen-api@lists.xen.org; Wed, 30 Jan 2013 18:56:46 +0000 Received: from [193.109.254.147:51639] by server-15.bemta-14.messagelabs.com id F0/65-24599-DEC69015; Wed, 30 Jan 2013 18:56:45 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1359572196!8610204!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26367 invoked from network); 30 Jan 2013 18:56:38 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-4.tower-27.messagelabs.com with SMTP; 30 Jan 2013 18:56:38 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Wed, 30 Jan 2013 12:56:36 -0600 Message-ID: <51096CE5.7070607@xenhive.com> Date: Wed, 30 Jan 2013 12:56:37 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-Auth: admin@xenhive.com Subject: Re: [Xen-API] Infiniband suport in XCP? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7614040933240239388==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7614040933240239388== Content-Type: multipart/alternative; boundary="------------010205060206000006000709" This is a multi-part message in MIME format. --------------010205060206000006000709 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I really wish XCP and XenServer included OFED support, because InfiniBand (especially IB with SRP) is totally awesome. Unfortunately, you need to use the DDK to manually compile the OFED support for XCP/XenServer. On 1/30/2013 12:05 PM, Andrei Maslennikov wrote: > Hello, > > we might want to recycle some existing Infiniband infrastructure > configuring a couple of SRP targets shared across the hypervisors. So > far XCP does not support Infiniband, but probably somebody in the > community had already done a step forward and made it working? > > Any comment would be very welcome. > > Thanks ahead - Andrei. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------010205060206000006000709 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
I really wish XCP and XenServer included OFED support, because InfiniBand (especially IB with SRP) is totally awesome.  Unfortunately, you need to use the DDK to manually compile the OFED support for XCP/XenServer.

On 1/30/2013 12:05 PM, Andrei Maslennikov wrote:
Hello,

we might want to recycle some existing Infiniband infrastructure configuring a couple of SRP targets shared across the hypervisors. So far XCP does not support Infiniband, but probably somebody  in the community had already done a step forward and made it working?

Any comment would be very welcome.

Thanks ahead - Andrei.  


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------010205060206000006000709-- --===============7614040933240239388== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7614040933240239388==-- From xen-api-bounces@lists.xen.org Wed Jan 30 18:56:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 18:56:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0cpz-0001cT-JO; Wed, 30 Jan 2013 18:56:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0cpy-0001cO-Cl for xen-api@lists.xen.org; Wed, 30 Jan 2013 18:56:46 +0000 Received: from [193.109.254.147:51639] by server-15.bemta-14.messagelabs.com id F0/65-24599-DEC69015; Wed, 30 Jan 2013 18:56:45 +0000 X-Env-Sender: admin@xenhive.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1359572196!8610204!1 X-Originating-IP: [216.51.232.10] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26367 invoked from network); 30 Jan 2013 18:56:38 -0000 Received: from mailcluster.fastdnsservers.com (HELO mailcluster.fastdnsservers.com) (216.51.232.10) by server-4.tower-27.messagelabs.com with SMTP; 30 Jan 2013 18:56:38 -0000 Received: from [192.168.1.103] by mailcluster.fastdnsservers.com ; Wed, 30 Jan 2013 12:56:36 -0600 Message-ID: <51096CE5.7070607@xenhive.com> Date: Wed, 30 Jan 2013 12:56:37 -0600 From: "admin@xenhive.com" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: X-Auth: admin@xenhive.com Subject: Re: [Xen-API] Infiniband suport in XCP? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7614040933240239388==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7614040933240239388== Content-Type: multipart/alternative; boundary="------------010205060206000006000709" This is a multi-part message in MIME format. --------------010205060206000006000709 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I really wish XCP and XenServer included OFED support, because InfiniBand (especially IB with SRP) is totally awesome. Unfortunately, you need to use the DDK to manually compile the OFED support for XCP/XenServer. On 1/30/2013 12:05 PM, Andrei Maslennikov wrote: > Hello, > > we might want to recycle some existing Infiniband infrastructure > configuring a couple of SRP targets shared across the hypervisors. So > far XCP does not support Infiniband, but probably somebody in the > community had already done a step forward and made it working? > > Any comment would be very welcome. > > Thanks ahead - Andrei. > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------010205060206000006000709 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
I really wish XCP and XenServer included OFED support, because InfiniBand (especially IB with SRP) is totally awesome.  Unfortunately, you need to use the DDK to manually compile the OFED support for XCP/XenServer.

On 1/30/2013 12:05 PM, Andrei Maslennikov wrote:
Hello,

we might want to recycle some existing Infiniband infrastructure configuring a couple of SRP targets shared across the hypervisors. So far XCP does not support Infiniband, but probably somebody  in the community had already done a step forward and made it working?

Any comment would be very welcome.

Thanks ahead - Andrei.  


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------010205060206000006000709-- --===============7614040933240239388== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7614040933240239388==-- From xen-api-bounces@lists.xen.org Wed Jan 30 19:50:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 19:50:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0dfp-0001y1-9i; Wed, 30 Jan 2013 19:50:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0dfo-0001xw-GA for xen-api@lists.xen.org; Wed, 30 Jan 2013 19:50:20 +0000 Received: from [85.158.139.83:22579] by server-14.bemta-5.messagelabs.com id 8A/5C-06967-B7979015; Wed, 30 Jan 2013 19:50:19 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1359575410!30410348!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26312 invoked from network); 30 Jan 2013 19:50:11 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jan 2013 19:50:11 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:CC:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:Content-Transfer-Encoding:MIME-Version; b=OKEcg9YAwmpX+ml6V+W0TQFICXI6rmrACWIvCsKopae2naAh76A9V+OMbUZlGNyMw3l5/6DrZUEVsRI/B2S0pPj7qUaZp/gbwALRpSHCr8doNTc1a7a4SsisOjP48fjo; Received: from [192.168.1.12] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1U0dfe-000ARk-V3; Wed, 30 Jan 2013 11:50:10 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-002-sfo.servepath.com ([::1]) with mapi; Wed, 30 Jan 2013 11:50:08 -0800 From: Brian Menges To: Mike McClurg Date: Wed, 30 Jan 2013 11:50:06 -0800 Thread-Topic: [Xen-API] xe sr-create failed Thread-Index: Ac3/FgjgCQl3SbIWT1qoEHS2FXSurQAAhihQAAKl6ZA= Message-ID: <3968CAC7E1BE7242B18501F292F3C7F16819891D@EX-004-SFO.servepath.com> References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> <510963A4.3010805@citrix.com> <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> In-Reply-To: <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org As a follow up to the chan; I was looking at the SMlog on the slave (the host where I was running the sr-create) Yes they are in a pool. - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Brian Menges Sent: Wednesday, January 30, 2013 10:40 To: Mike McClurg Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed When I just re-ran the sr-create, I got nothing new in the SMlog The only error I get is from the command's output: Error code: SR_BACKEND_FAILURE_19 Error parameters: , No such device [opterr=Device /dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 does not exist], I don't see any other errors in messages, xensource.log. I do see info stuff in /var/log/messages: Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi||cli] xe sr-create password=null content-type=user type=lvm shared=false name-label=Local storage device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=root Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi|session.login_with_password D:c1ac97a0f35f|xapi] Session.create trackid=99cbed91b097c6aac2542c43c10b1be6 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 But that's about it. Would there be someplace where I can turn up some logging that may give a better hint? - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: Mike McClurg [mailto:mike.mcclurg@citrix.com] Sent: Wednesday, January 30, 2013 10:17 To: Brian Menges Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed On 30/01/13 17:31, Brian Menges wrote: > I have a pool setup with two xcp 1.6 61809c builds. I destroyed the > local storage sr on both hosts, and attempted to re-create them. On > the first host I was able to successfully do this, but on the second > host I keep getting failures: > > [root@xs-04 ~]# ls -la /dev/disk/by-id/ > > total 0 > > drwxr-xr-x 2 root root 140 Jan 30 08:56 . > > drwxr-xr-x 8 root root 160 Jan 30 08:56 .. > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3 > > [root@xs-04 ~]# xe host-list > > uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f > > name-label ( RW): xs-03. > > name-description ( RW): Default install of XenServer > > uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > name-label ( RW): xs-04. > > name-description ( RW): Default install of XenServer > > [root@xs-04 ~]# xe sr-create content-type=user type=lvm shared=false > name-label='Local storage' > device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27 > 161a6 > uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > Error code: SR_BACKEND_FAILURE_19 Can you check /var/log/SMlog for errors? What does this say? Mike The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 19:50:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 19:50:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0dfp-0001y1-9i; Wed, 30 Jan 2013 19:50:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0dfo-0001xw-GA for xen-api@lists.xen.org; Wed, 30 Jan 2013 19:50:20 +0000 Received: from [85.158.139.83:22579] by server-14.bemta-5.messagelabs.com id 8A/5C-06967-B7979015; Wed, 30 Jan 2013 19:50:19 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1359575410!30410348!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26312 invoked from network); 30 Jan 2013 19:50:11 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jan 2013 19:50:11 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:CC:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:Content-Transfer-Encoding:MIME-Version; b=OKEcg9YAwmpX+ml6V+W0TQFICXI6rmrACWIvCsKopae2naAh76A9V+OMbUZlGNyMw3l5/6DrZUEVsRI/B2S0pPj7qUaZp/gbwALRpSHCr8doNTc1a7a4SsisOjP48fjo; Received: from [192.168.1.12] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1U0dfe-000ARk-V3; Wed, 30 Jan 2013 11:50:10 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-002-sfo.servepath.com ([::1]) with mapi; Wed, 30 Jan 2013 11:50:08 -0800 From: Brian Menges To: Mike McClurg Date: Wed, 30 Jan 2013 11:50:06 -0800 Thread-Topic: [Xen-API] xe sr-create failed Thread-Index: Ac3/FgjgCQl3SbIWT1qoEHS2FXSurQAAhihQAAKl6ZA= Message-ID: <3968CAC7E1BE7242B18501F292F3C7F16819891D@EX-004-SFO.servepath.com> References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> <510963A4.3010805@citrix.com> <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> In-Reply-To: <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org As a follow up to the chan; I was looking at the SMlog on the slave (the host where I was running the sr-create) Yes they are in a pool. - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Brian Menges Sent: Wednesday, January 30, 2013 10:40 To: Mike McClurg Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed When I just re-ran the sr-create, I got nothing new in the SMlog The only error I get is from the command's output: Error code: SR_BACKEND_FAILURE_19 Error parameters: , No such device [opterr=Device /dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 does not exist], I don't see any other errors in messages, xensource.log. I do see info stuff in /var/log/messages: Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi||cli] xe sr-create password=null content-type=user type=lvm shared=false name-label=Local storage device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=root Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi|session.login_with_password D:c1ac97a0f35f|xapi] Session.create trackid=99cbed91b097c6aac2542c43c10b1be6 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 But that's about it. Would there be someplace where I can turn up some logging that may give a better hint? - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: Mike McClurg [mailto:mike.mcclurg@citrix.com] Sent: Wednesday, January 30, 2013 10:17 To: Brian Menges Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed On 30/01/13 17:31, Brian Menges wrote: > I have a pool setup with two xcp 1.6 61809c builds. I destroyed the > local storage sr on both hosts, and attempted to re-create them. On > the first host I was able to successfully do this, but on the second > host I keep getting failures: > > [root@xs-04 ~]# ls -la /dev/disk/by-id/ > > total 0 > > drwxr-xr-x 2 root root 140 Jan 30 08:56 . > > drwxr-xr-x 8 root root 160 Jan 30 08:56 .. > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3 > > [root@xs-04 ~]# xe host-list > > uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f > > name-label ( RW): xs-03. > > name-description ( RW): Default install of XenServer > > uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > name-label ( RW): xs-04. > > name-description ( RW): Default install of XenServer > > [root@xs-04 ~]# xe sr-create content-type=user type=lvm shared=false > name-label='Local storage' > device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27 > 161a6 > uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > Error code: SR_BACKEND_FAILURE_19 Can you check /var/log/SMlog for errors? What does this say? Mike The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 19:56:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 19:56:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0dlD-00023F-RR; Wed, 30 Jan 2013 19:55:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0dlC-00023A-5Y for xen-api@lists.xen.org; Wed, 30 Jan 2013 19:55:54 +0000 Received: from [85.158.139.211:34045] by server-2.bemta-5.messagelabs.com id 2B/CC-16911-9CA79015; Wed, 30 Jan 2013 19:55:53 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1359575750!20373629!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11843 invoked from network); 30 Jan 2013 19:55:52 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jan 2013 19:55:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:CC:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:Content-Transfer-Encoding:MIME-Version; b=QvQVYnXddNiABX5W+WqXIkKP9an55ydMGMVPpP2sL47jlnFQqiN+ffWie3jPedM0VS0+w59UkaDE6KDiD+CLDv4YpW9A+FItz/yZB3dZ1o8UcBtAUTDIN43Ukpen9Wvt; Received: from [192.168.1.12] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1U0dl8-000AhA-TK; Wed, 30 Jan 2013 11:55:50 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-002-sfo.servepath.com ([::1]) with mapi; Wed, 30 Jan 2013 11:55:49 -0800 From: Brian Menges To: Mike McClurg Date: Wed, 30 Jan 2013 11:55:47 -0800 Thread-Topic: [Xen-API] xe sr-create failed Thread-Index: Ac3/FgjgCQl3SbIWT1qoEHS2FXSurQAAhihQAAKl6ZAAADmuAA== Message-ID: <3968CAC7E1BE7242B18501F292F3C7F16819892E@EX-004-SFO.servepath.com> References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> <510963A4.3010805@citrix.com> <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> <3968CAC7E1BE7242B18501F292F3C7F16819891D@EX-004-SFO.servepath.com> In-Reply-To: <3968CAC7E1BE7242B18501F292F3C7F16819891D@EX-004-SFO.servepath.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org BLAH!!!! I forgot the host-uuid portion of the api call. Seems it defaulted to the master host, instead of the local host. Really wish that the message was a little more helpful; considering that host-uuid is an optional parameter to this command. - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Brian Menges Sent: Wednesday, January 30, 2013 11:50 To: Mike McClurg Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed As a follow up to the chan; I was looking at the SMlog on the slave (the host where I was running the sr-create) Yes they are in a pool. - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Brian Menges Sent: Wednesday, January 30, 2013 10:40 To: Mike McClurg Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed When I just re-ran the sr-create, I got nothing new in the SMlog The only error I get is from the command's output: Error code: SR_BACKEND_FAILURE_19 Error parameters: , No such device [opterr=Device /dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 does not exist], I don't see any other errors in messages, xensource.log. I do see info stuff in /var/log/messages: Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi||cli] xe sr-create password=null content-type=user type=lvm shared=false name-label=Local storage device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=root Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi|session.login_with_password D:c1ac97a0f35f|xapi] Session.create trackid=99cbed91b097c6aac2542c43c10b1be6 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 But that's about it. Would there be someplace where I can turn up some logging that may give a better hint? - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: Mike McClurg [mailto:mike.mcclurg@citrix.com] Sent: Wednesday, January 30, 2013 10:17 To: Brian Menges Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed On 30/01/13 17:31, Brian Menges wrote: > I have a pool setup with two xcp 1.6 61809c builds. I destroyed the > local storage sr on both hosts, and attempted to re-create them. On > the first host I was able to successfully do this, but on the second > host I keep getting failures: > > [root@xs-04 ~]# ls -la /dev/disk/by-id/ > > total 0 > > drwxr-xr-x 2 root root 140 Jan 30 08:56 . > > drwxr-xr-x 8 root root 160 Jan 30 08:56 .. > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3 > > [root@xs-04 ~]# xe host-list > > uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f > > name-label ( RW): xs-03. > > name-description ( RW): Default install of XenServer > > uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > name-label ( RW): xs-04. > > name-description ( RW): Default install of XenServer > > [root@xs-04 ~]# xe sr-create content-type=user type=lvm shared=false > name-label='Local storage' > device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27 > 161a6 > uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > Error code: SR_BACKEND_FAILURE_19 Can you check /var/log/SMlog for errors? What does this say? Mike The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 19:56:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 19:56:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0dlD-00023F-RR; Wed, 30 Jan 2013 19:55:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0dlC-00023A-5Y for xen-api@lists.xen.org; Wed, 30 Jan 2013 19:55:54 +0000 Received: from [85.158.139.211:34045] by server-2.bemta-5.messagelabs.com id 2B/CC-16911-9CA79015; Wed, 30 Jan 2013 19:55:53 +0000 X-Env-Sender: bmenges@gogrid.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1359575750!20373629!1 X-Originating-IP: [216.93.160.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11843 invoked from network); 30 Jan 2013 19:55:52 -0000 Received: from smtp1.servepath.com (HELO smtp1.servepath.com) (216.93.160.25) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jan 2013 19:55:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:CC:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:Content-Transfer-Encoding:MIME-Version; b=QvQVYnXddNiABX5W+WqXIkKP9an55ydMGMVPpP2sL47jlnFQqiN+ffWie3jPedM0VS0+w59UkaDE6KDiD+CLDv4YpW9A+FItz/yZB3dZ1o8UcBtAUTDIN43Ukpen9Wvt; Received: from [192.168.1.12] (helo=fe-002-sfo.servepath.com) by smtp1.servepath.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1U0dl8-000AhA-TK; Wed, 30 Jan 2013 11:55:50 -0800 Received: from EX-004-SFO.servepath.com ([::1]) by fe-002-sfo.servepath.com ([::1]) with mapi; Wed, 30 Jan 2013 11:55:49 -0800 From: Brian Menges To: Mike McClurg Date: Wed, 30 Jan 2013 11:55:47 -0800 Thread-Topic: [Xen-API] xe sr-create failed Thread-Index: Ac3/FgjgCQl3SbIWT1qoEHS2FXSurQAAhihQAAKl6ZAAADmuAA== Message-ID: <3968CAC7E1BE7242B18501F292F3C7F16819892E@EX-004-SFO.servepath.com> References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> <510963A4.3010805@citrix.com> <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> <3968CAC7E1BE7242B18501F292F3C7F16819891D@EX-004-SFO.servepath.com> In-Reply-To: <3968CAC7E1BE7242B18501F292F3C7F16819891D@EX-004-SFO.servepath.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org BLAH!!!! I forgot the host-uuid portion of the api call. Seems it defaulted to the master host, instead of the local host. Really wish that the message was a little more helpful; considering that host-uuid is an optional parameter to this command. - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Brian Menges Sent: Wednesday, January 30, 2013 11:50 To: Mike McClurg Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed As a follow up to the chan; I was looking at the SMlog on the slave (the host where I was running the sr-create) Yes they are in a pool. - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On Behalf Of Brian Menges Sent: Wednesday, January 30, 2013 10:40 To: Mike McClurg Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed When I just re-ran the sr-create, I got nothing new in the SMlog The only error I get is from the command's output: Error code: SR_BACKEND_FAILURE_19 Error parameters: , No such device [opterr=Device /dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 does not exist], I don't see any other errors in messages, xensource.log. I do see info stuff in /var/log/messages: Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi||cli] xe sr-create password=null content-type=user type=lvm shared=false name-label=Local storage device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27161a6 uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 username=root Jan 30 10:37:21 xs-04 xapi: [ info|xs-04.|4989 UNIX /var/xapi/xapi|session.login_with_password D:c1ac97a0f35f|xapi] Session.create trackid=99cbed91b097c6aac2542c43c10b1be6 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 But that's about it. Would there be someplace where I can turn up some logging that may give a better hint? - Brian Menges Principal Engineer, DevOps GoGrid | ServePath | ColoServe | UpStream Networks -----Original Message----- From: Mike McClurg [mailto:mike.mcclurg@citrix.com] Sent: Wednesday, January 30, 2013 10:17 To: Brian Menges Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] xe sr-create failed On 30/01/13 17:31, Brian Menges wrote: > I have a pool setup with two xcp 1.6 61809c builds. I destroyed the > local storage sr on both hosts, and attempted to re-create them. On > the first host I was able to successfully do this, but on the second > host I keep getting failures: > > [root@xs-04 ~]# ls -la /dev/disk/by-id/ > > total 0 > > drwxr-xr-x 2 root root 140 Jan 30 08:56 . > > drwxr-xr-x 8 root root 160 Jan 30 08:56 .. > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-3600605b003349b30189b8956b27161a6 -> ../../sdb > > lrwxrwxrwx 1 root root 9 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J -> ../../sda > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part1 -> ../../sda1 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part2 -> ../../sda2 > > lrwxrwxrwx 1 root root 10 Jan 30 08:56 > scsi-SATA_Hitachi_HTS7250100521PCK200VJHJKU5J-part3 -> ../../sda3 > > [root@xs-04 ~]# xe host-list > > uuid ( RO) : 6a5f2a4f-8f73-47c5-a4cf-09817777a55f > > name-label ( RW): xs-03. > > name-description ( RW): Default install of XenServer > > uuid ( RO) : 5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > name-label ( RW): xs-04. > > name-description ( RW): Default install of XenServer > > [root@xs-04 ~]# xe sr-create content-type=user type=lvm shared=false > name-label='Local storage' > device-config:device=/dev/disk/by-id/scsi-3600605b003349b30189b8956b27 > 161a6 > uuid=5b73d60a-bca4-4793-a3e8-dc5c830c8e20 > > Error code: SR_BACKEND_FAILURE_19 Can you check /var/log/SMlog for errors? What does this say? Mike The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 21:26:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 21:26:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0fAE-0002Oy-8Z; Wed, 30 Jan 2013 21:25:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0fAC-0002On-LO for xen-api@lists.xen.org; Wed, 30 Jan 2013 21:25:48 +0000 Received: from [85.158.138.51:46428] by server-13.bemta-3.messagelabs.com id 6D/B1-20653-9DF89015; Wed, 30 Jan 2013 21:25:45 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1359581138!28531580!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDAwMTg=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16051 invoked from network); 30 Jan 2013 21:25:40 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 21:25:40 -0000 X-IronPort-AV: E=Sophos;i="4.84,572,1355097600"; d="scan'208";a="5426526" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 30 Jan 2013 21:25:38 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Wed, 30 Jan 2013 16:25:37 -0500 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[192.168.0.6]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U0fA1-0004Fl-HZ; Wed, 30 Jan 2013 21:25:37 +0000 Message-ID: <51098FD1.1060008@citrix.com> Date: Wed, 30 Jan 2013 21:25:37 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Brian Menges References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> <510963A4.3010805@citrix.com> <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> <3968CAC7E1BE7242B18501F292F3C7F16819891D@EX-004-SFO.servepath.com> <3968CAC7E1BE7242B18501F292F3C7F16819892E@EX-004-SFO.servepath.com> In-Reply-To: <3968CAC7E1BE7242B18501F292F3C7F16819892E@EX-004-SFO.servepath.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 30/01/13 19:55, Brian Menges wrote: > BLAH!!!! > > I forgot the host-uuid portion of the api call. Seems it defaulted > to the master host, instead of the local host. Really wish that the > message was a little more helpful; considering that host-uuid is an > optional parameter to this command. Wow, that is an embarrassingly bad error message! I'll file a bug for this. Perhaps if shared=false, then a host identifier should be required? I just checked the code, and this is definitely a problem in the CLI, which just blindly defaults to the pool master if host-uuid isn't found. And yes, you would expect that calling a command on a particular slave would execute the command on that slave, but it really just passes the command on to the master. Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 21:26:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 21:26:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0fAE-0002Oy-8Z; Wed, 30 Jan 2013 21:25:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0fAC-0002On-LO for xen-api@lists.xen.org; Wed, 30 Jan 2013 21:25:48 +0000 Received: from [85.158.138.51:46428] by server-13.bemta-3.messagelabs.com id 6D/B1-20653-9DF89015; Wed, 30 Jan 2013 21:25:45 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1359581138!28531580!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDAwMTg=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16051 invoked from network); 30 Jan 2013 21:25:40 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 21:25:40 -0000 X-IronPort-AV: E=Sophos;i="4.84,572,1355097600"; d="scan'208";a="5426526" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 30 Jan 2013 21:25:38 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Wed, 30 Jan 2013 16:25:37 -0500 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[192.168.0.6]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U0fA1-0004Fl-HZ; Wed, 30 Jan 2013 21:25:37 +0000 Message-ID: <51098FD1.1060008@citrix.com> Date: Wed, 30 Jan 2013 21:25:37 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Brian Menges References: <3968CAC7E1BE7242B18501F292F3C7F16819879E@EX-004-SFO.servepath.com> <510963A4.3010805@citrix.com> <3968CAC7E1BE7242B18501F292F3C7F168198868@EX-004-SFO.servepath.com> <3968CAC7E1BE7242B18501F292F3C7F16819891D@EX-004-SFO.servepath.com> <3968CAC7E1BE7242B18501F292F3C7F16819892E@EX-004-SFO.servepath.com> In-Reply-To: <3968CAC7E1BE7242B18501F292F3C7F16819892E@EX-004-SFO.servepath.com> Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe sr-create failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 30/01/13 19:55, Brian Menges wrote: > BLAH!!!! > > I forgot the host-uuid portion of the api call. Seems it defaulted > to the master host, instead of the local host. Really wish that the > message was a little more helpful; considering that host-uuid is an > optional parameter to this command. Wow, that is an embarrassingly bad error message! I'll file a bug for this. Perhaps if shared=false, then a host identifier should be required? I just checked the code, and this is definitely a problem in the CLI, which just blindly defaults to the pool master if host-uuid isn't found. And yes, you would expect that calling a command on a particular slave would execute the command on that slave, but it really just passes the command on to the master. Mike _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Jan 30 21:33:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 21:33:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0fHb-0002jI-Ii; Wed, 30 Jan 2013 21:33:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1U0fHa-0002jC-DJ for xen-api@lists.xen.org; Wed, 30 Jan 2013 21:33:26 +0000 Received: from [85.158.143.99:61690] by server-3.bemta-4.messagelabs.com id 04/6B-08920-5A199015; Wed, 30 Jan 2013 21:33:25 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1359581604!29578438!1 X-Originating-IP: [209.85.128.48] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12231 invoked from network); 30 Jan 2013 21:33:25 -0000 Received: from mail-qe0-f48.google.com (HELO mail-qe0-f48.google.com) (209.85.128.48) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 21:33:25 -0000 Received: by mail-qe0-f48.google.com with SMTP id 3so957490qea.35 for ; Wed, 30 Jan 2013 13:33:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=hMAs4/WHcM2Irh6Su5rKjTY5YQ8JQRV5kO1VklnIzLc=; b=jqRxIdiAaT/V/7MyXk04+UqjqIXqj9m6Hb14+r6a+YoO7qdr7E9lcP1Bn6QpiryHuC Sccpv5HieuSxG+uTJjB7l07rEmWTzP6Fc+aejofZCbCIGbEGa2l3x2er4WZhDZFDx+rI lVHcgm9WJCdrIRdV/6Zi3Z4T8/RsdkYRMm0J8x0wAaNNaTqVw5y73Xd7Waedia7z6zYD 11y947oSgyS8RYozKVOjznGrC9Aw0GjYu6GtrsWStpxGeJSpxIhyYOim+1nRRaE0uMkI 4mPKVdHx2gIraqP4VvRLDD9ERwlgnGF2lK0vEPP53gWA2Y8Ck0RMkWrTJRQgrnh8Vk/J KVUg== MIME-Version: 1.0 X-Received: by 10.49.121.40 with SMTP id lh8mr7706045qeb.30.1359581603768; Wed, 30 Jan 2013 13:33:23 -0800 (PST) Received: by 10.229.131.81 with HTTP; Wed, 30 Jan 2013 13:33:23 -0800 (PST) Date: Thu, 31 Jan 2013 03:03:23 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: xen-api@lists.xen.org Subject: [Xen-API] VM live migrate using *any* available network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1691048002853614078==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1691048002853614078== Content-Type: multipart/alternative; boundary=047d7bdc1be4892b0904d488426e --047d7bdc1be4892b0904d488426e Content-Type: text/plain; charset=ISO-8859-1 Hi List, I understand that Xapi uses its default management network for live migration of VMs. I was wondering if we could use any available network (other than management) for VM live migration with xapi ? Why? We have many 10G links for storage which are not used at full scale and migrating bigger VMs on 1G management network is quite time consuming. It may not be possible right away due to xapi binding itself only to management NIC but does anyone have a suggestion how to implement cross NIC migration ? Or is it possible to bind xapi on all available IPs ? ( some nasty hack ? ) Thanks, Rushikesh --047d7bdc1be4892b0904d488426e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi List,

I understand that Xapi uses its default management network = for live migration of VMs.
I was wondering if we could use any available= network (other than management) for VM live migration with xapi ?
Why? = We have many 10G links for storage which are not used at full scale and mig= rating bigger VMs on 1G management network is quite time consuming.

It may not be possible right away due to xapi binding itself only to ma= nagement NIC but does anyone have a suggestion how to implement cross NIC m= igration ?
Or is it possible to bind xapi on all available IPs ? ( some = nasty hack ? )

Thanks,
Rushikesh
--047d7bdc1be4892b0904d488426e-- --===============1691048002853614078== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1691048002853614078==-- From xen-api-bounces@lists.xen.org Wed Jan 30 21:33:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 30 Jan 2013 21:33:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0fHb-0002jI-Ii; Wed, 30 Jan 2013 21:33:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1U0fHa-0002jC-DJ for xen-api@lists.xen.org; Wed, 30 Jan 2013 21:33:26 +0000 Received: from [85.158.143.99:61690] by server-3.bemta-4.messagelabs.com id 04/6B-08920-5A199015; Wed, 30 Jan 2013 21:33:25 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1359581604!29578438!1 X-Originating-IP: [209.85.128.48] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12231 invoked from network); 30 Jan 2013 21:33:25 -0000 Received: from mail-qe0-f48.google.com (HELO mail-qe0-f48.google.com) (209.85.128.48) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2013 21:33:25 -0000 Received: by mail-qe0-f48.google.com with SMTP id 3so957490qea.35 for ; Wed, 30 Jan 2013 13:33:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=hMAs4/WHcM2Irh6Su5rKjTY5YQ8JQRV5kO1VklnIzLc=; b=jqRxIdiAaT/V/7MyXk04+UqjqIXqj9m6Hb14+r6a+YoO7qdr7E9lcP1Bn6QpiryHuC Sccpv5HieuSxG+uTJjB7l07rEmWTzP6Fc+aejofZCbCIGbEGa2l3x2er4WZhDZFDx+rI lVHcgm9WJCdrIRdV/6Zi3Z4T8/RsdkYRMm0J8x0wAaNNaTqVw5y73Xd7Waedia7z6zYD 11y947oSgyS8RYozKVOjznGrC9Aw0GjYu6GtrsWStpxGeJSpxIhyYOim+1nRRaE0uMkI 4mPKVdHx2gIraqP4VvRLDD9ERwlgnGF2lK0vEPP53gWA2Y8Ck0RMkWrTJRQgrnh8Vk/J KVUg== MIME-Version: 1.0 X-Received: by 10.49.121.40 with SMTP id lh8mr7706045qeb.30.1359581603768; Wed, 30 Jan 2013 13:33:23 -0800 (PST) Received: by 10.229.131.81 with HTTP; Wed, 30 Jan 2013 13:33:23 -0800 (PST) Date: Thu, 31 Jan 2013 03:03:23 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: xen-api@lists.xen.org Subject: [Xen-API] VM live migrate using *any* available network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1691048002853614078==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1691048002853614078== Content-Type: multipart/alternative; boundary=047d7bdc1be4892b0904d488426e --047d7bdc1be4892b0904d488426e Content-Type: text/plain; charset=ISO-8859-1 Hi List, I understand that Xapi uses its default management network for live migration of VMs. I was wondering if we could use any available network (other than management) for VM live migration with xapi ? Why? We have many 10G links for storage which are not used at full scale and migrating bigger VMs on 1G management network is quite time consuming. It may not be possible right away due to xapi binding itself only to management NIC but does anyone have a suggestion how to implement cross NIC migration ? Or is it possible to bind xapi on all available IPs ? ( some nasty hack ? ) Thanks, Rushikesh --047d7bdc1be4892b0904d488426e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi List,

I understand that Xapi uses its default management network = for live migration of VMs.
I was wondering if we could use any available= network (other than management) for VM live migration with xapi ?
Why? = We have many 10G links for storage which are not used at full scale and mig= rating bigger VMs on 1G management network is quite time consuming.

It may not be possible right away due to xapi binding itself only to ma= nagement NIC but does anyone have a suggestion how to implement cross NIC m= igration ?
Or is it possible to bind xapi on all available IPs ? ( some = nasty hack ? )

Thanks,
Rushikesh
--047d7bdc1be4892b0904d488426e-- --===============1691048002853614078== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============1691048002853614078==-- From xen-api-bounces@lists.xen.org Thu Jan 31 09:30:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 31 Jan 2013 09:30:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0qTh-0003sq-IT; Thu, 31 Jan 2013 09:30:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0qTf-0003sc-Ne for xen-api@lists.xen.org; Thu, 31 Jan 2013 09:30:40 +0000 Received: from [85.158.139.211:23479] by server-4.bemta-5.messagelabs.com id 00/06-29496-EB93A015; Thu, 31 Jan 2013 09:30:38 +0000 X-Env-Sender: sergey.kruchatov@k21.com.ua X-Msg-Ref: server-2.tower-206.messagelabs.com!1359624620!19396085!1 X-Originating-IP: [209.85.214.179] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25258 invoked from network); 31 Jan 2013 09:30:21 -0000 Received: from mail-ob0-f179.google.com (HELO mail-ob0-f179.google.com) (209.85.214.179) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 31 Jan 2013 09:30:21 -0000 Received: by mail-ob0-f179.google.com with SMTP id un3so2642060obb.24 for ; Thu, 31 Jan 2013 01:30:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=Td2er9dTBA5ndczbVW6yEtZnbCCbphiBGv2PoC0Qilw=; b=Hd+wORK9y/aViTTMrtKADgQrWTRgRErNl5I9wI0vyCdsWIVEFqbHRwdRuuyBLInD1i hvc2W2wTDZP6ZrHmErpdSBbZVXMq5iVtVF9vG9FI7WfGAuCD0VaUPFMZ8yT6vnSz6fKB P/UkcmPOSecZFmPjmgfRLMBd8VPVLFInGajKiUeZRoeMO6LHEVNl4Vw4lLR4FI+SZuic FWY3K9pv5bmDw07VwQagq3nb40OKRZQHIpQXyWuO3rac4aA0bZ35DNmVCJoAbTfu+Rn8 QmPAgOTcl2VURf3u4tTg6KEu9c6/x4VDm2XYfJsoh2LoAuyyhZOql+uRUkiQUFvpQAYs Q0FA== X-Received: by 10.182.8.70 with SMTP id p6mr5852270oba.90.1359624619919; Thu, 31 Jan 2013 01:30:19 -0800 (PST) Received: from mail-oa0-f52.google.com (mail-oa0-f52.google.com [209.85.219.52]) by mx.google.com with ESMTPS id dl6sm4977243obb.5.2013.01.31.01.30.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Jan 2013 01:30:19 -0800 (PST) Received: by mail-oa0-f52.google.com with SMTP id k14so2687584oag.25 for ; Thu, 31 Jan 2013 01:30:18 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.182.227.33 with SMTP id rx1mr5864194obc.69.1359624618347; Thu, 31 Jan 2013 01:30:18 -0800 (PST) Received: by 10.76.10.233 with HTTP; Thu, 31 Jan 2013 01:30:18 -0800 (PST) Date: Thu, 31 Jan 2013 11:30:18 +0200 Message-ID: From: hook To: "xen-api@lists.xen.org" X-Gm-Message-State: ALoCoQlop9svXRh9MYoHs8RSrjfAk59b5+qoZG6bNVRCzVE2IPhRq2unMF107l5V7omI1HmuMIKF Subject: [Xen-API] XenTools 6.1 update for XCP 1.6. How? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7602736853626542624==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7602736853626542624== Content-Type: multipart/alternative; boundary=f46d0444741f678bd804d49246d2 --f46d0444741f678bd804d49246d2 Content-Type: text/plain; charset=UTF-8 Hi all, There is well known bug in XenServer 6.1 when Windows VMs hang/freeze during intensive disk operation (presumably due to race condition somewhere in xentools drivers in multi-vCPU Windows systems). Best description and discussion of mentioned problem would be found there http://forums.citrix.com/thread.jspa?threadID=314906&start=0&tstart=0 In our production site (pooled dual XCP 1.6 final) we've expected above problem for every Windows XP 32 bit VM as well as for Windows 2003 Servers 32-bit. While Windows 2008/2008R2 servers work fine. Last year Citrix published temporary workaround for above problem - reduce vCPU to 1 for affected VMs. It's really helps but could be used in low/middle CPU load environment. Another workaround were found by someone in community - previous version from XenTools - exactly XS602E009 works fine. Everything stated above has been detailed in very tricky (as per my opinion) Citrix article there http://support.citrix.com/article/CTX135099. Recently Citrix published long awaited pair of Hot Fixes - XS61E009 and XS61E010. XS61E009 (http://support.citrix.com/article/CTX136252) contains patches for some core functions (xapi-core, xapi-xenopsd, xapi-firmware) while XS61E010 (http://support.citrix.com/article/CTX136253) provides xentools replacement. What's more interest xentools from XS61E010 contains new and legacy drivers - new with Windows 8/Server 2012 support while legacy - just renamed tools from XS602E009. In XS61E010's installation prerequisites stated that it can't be implemented without XS61E009. So, finally, my question is - is there some way to deploy core patches from XS61E009 into XCP 1.6? Or I just can use legacy windows driver from XS61E010 to workaround VM hang/freeze issue? -- WBR Sergey Kruchatov --f46d0444741f678bd804d49246d2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

There is well known bug in XenS= erver 6.1 when Windows VMs hang/freeze during intensive disk operation (pre= sumably due to race condition somewhere in xentools drivers in multi-vCPU W= indows systems).

Best description and discussion of mentioned problem wo= uld be found there=C2=A0http://forums.citrix.com/threa= d.jspa?threadID=3D314906&start=3D0&tstart=3D0

In our production site (pooled=C2=A0dual XCP 1.6 = final) we've expected above problem for every Windows XP 32 bit VM as w= ell as for Windows 2003 Servers 32-bit. While Windows 2008/2008R2 servers w= ork fine.

Last year Citrix published temporary workar= ound for above problem - reduce vCPU to 1 for=C2=A0affected VMs. It's r= eally helps but could be used in low/middle CPU load=C2=A0environment.
Another workaround were found by someone in community - previous version fr= om XenTools - exactly XS602E009 works fine.

Everything stated above = has been detailed in very tricky (as per my opinion) Citrix article there <= a href=3D"http://support.citrix.com/article/CTX135099">http://support.citri= x.com/article/CTX135099.

Recently Citrix published long awaited pair of Hot Fixes - =C2=A0XS61E0= 09 and XS61E010.

XS61E009 (http://support.citrix.com/article/CTX136252) contains pa= tches for some core functions (xapi-core, xapi-xenopsd, xapi-firmware) whil= e XS61E010 (http://= support.citrix.com/article/CTX136253) provides xentools replacement. Wh= at's more interest xentools from XS61E010 contains new and legacy drive= rs - new with Windows 8/Server 2012 support while legacy - just renamed too= ls from XS602E009.=C2=A0In XS61E010's installation prerequisites stated= that it can't be implemented without XS61E009.

So, finally, my question is - i= s there some way to deploy core patches from XS61E009 into XCP 1.6?=C2=A0
Or I just can use legacy windows driver from XS61E010 to wor= karound VM hang/freeze issue?

--=C2=A0
WBR

Sergey Kr= uchatov
--f46d0444741f678bd804d49246d2-- --===============7602736853626542624== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7602736853626542624==-- From xen-api-bounces@lists.xen.org Thu Jan 31 09:30:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 31 Jan 2013 09:30:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0qTh-0003sq-IT; Thu, 31 Jan 2013 09:30:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U0qTf-0003sc-Ne for xen-api@lists.xen.org; Thu, 31 Jan 2013 09:30:40 +0000 Received: from [85.158.139.211:23479] by server-4.bemta-5.messagelabs.com id 00/06-29496-EB93A015; Thu, 31 Jan 2013 09:30:38 +0000 X-Env-Sender: sergey.kruchatov@k21.com.ua X-Msg-Ref: server-2.tower-206.messagelabs.com!1359624620!19396085!1 X-Originating-IP: [209.85.214.179] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25258 invoked from network); 31 Jan 2013 09:30:21 -0000 Received: from mail-ob0-f179.google.com (HELO mail-ob0-f179.google.com) (209.85.214.179) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 31 Jan 2013 09:30:21 -0000 Received: by mail-ob0-f179.google.com with SMTP id un3so2642060obb.24 for ; Thu, 31 Jan 2013 01:30:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=Td2er9dTBA5ndczbVW6yEtZnbCCbphiBGv2PoC0Qilw=; b=Hd+wORK9y/aViTTMrtKADgQrWTRgRErNl5I9wI0vyCdsWIVEFqbHRwdRuuyBLInD1i hvc2W2wTDZP6ZrHmErpdSBbZVXMq5iVtVF9vG9FI7WfGAuCD0VaUPFMZ8yT6vnSz6fKB P/UkcmPOSecZFmPjmgfRLMBd8VPVLFInGajKiUeZRoeMO6LHEVNl4Vw4lLR4FI+SZuic FWY3K9pv5bmDw07VwQagq3nb40OKRZQHIpQXyWuO3rac4aA0bZ35DNmVCJoAbTfu+Rn8 QmPAgOTcl2VURf3u4tTg6KEu9c6/x4VDm2XYfJsoh2LoAuyyhZOql+uRUkiQUFvpQAYs Q0FA== X-Received: by 10.182.8.70 with SMTP id p6mr5852270oba.90.1359624619919; Thu, 31 Jan 2013 01:30:19 -0800 (PST) Received: from mail-oa0-f52.google.com (mail-oa0-f52.google.com [209.85.219.52]) by mx.google.com with ESMTPS id dl6sm4977243obb.5.2013.01.31.01.30.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Jan 2013 01:30:19 -0800 (PST) Received: by mail-oa0-f52.google.com with SMTP id k14so2687584oag.25 for ; Thu, 31 Jan 2013 01:30:18 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.182.227.33 with SMTP id rx1mr5864194obc.69.1359624618347; Thu, 31 Jan 2013 01:30:18 -0800 (PST) Received: by 10.76.10.233 with HTTP; Thu, 31 Jan 2013 01:30:18 -0800 (PST) Date: Thu, 31 Jan 2013 11:30:18 +0200 Message-ID: From: hook To: "xen-api@lists.xen.org" X-Gm-Message-State: ALoCoQlop9svXRh9MYoHs8RSrjfAk59b5+qoZG6bNVRCzVE2IPhRq2unMF107l5V7omI1HmuMIKF Subject: [Xen-API] XenTools 6.1 update for XCP 1.6. How? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7602736853626542624==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7602736853626542624== Content-Type: multipart/alternative; boundary=f46d0444741f678bd804d49246d2 --f46d0444741f678bd804d49246d2 Content-Type: text/plain; charset=UTF-8 Hi all, There is well known bug in XenServer 6.1 when Windows VMs hang/freeze during intensive disk operation (presumably due to race condition somewhere in xentools drivers in multi-vCPU Windows systems). Best description and discussion of mentioned problem would be found there http://forums.citrix.com/thread.jspa?threadID=314906&start=0&tstart=0 In our production site (pooled dual XCP 1.6 final) we've expected above problem for every Windows XP 32 bit VM as well as for Windows 2003 Servers 32-bit. While Windows 2008/2008R2 servers work fine. Last year Citrix published temporary workaround for above problem - reduce vCPU to 1 for affected VMs. It's really helps but could be used in low/middle CPU load environment. Another workaround were found by someone in community - previous version from XenTools - exactly XS602E009 works fine. Everything stated above has been detailed in very tricky (as per my opinion) Citrix article there http://support.citrix.com/article/CTX135099. Recently Citrix published long awaited pair of Hot Fixes - XS61E009 and XS61E010. XS61E009 (http://support.citrix.com/article/CTX136252) contains patches for some core functions (xapi-core, xapi-xenopsd, xapi-firmware) while XS61E010 (http://support.citrix.com/article/CTX136253) provides xentools replacement. What's more interest xentools from XS61E010 contains new and legacy drivers - new with Windows 8/Server 2012 support while legacy - just renamed tools from XS602E009. In XS61E010's installation prerequisites stated that it can't be implemented without XS61E009. So, finally, my question is - is there some way to deploy core patches from XS61E009 into XCP 1.6? Or I just can use legacy windows driver from XS61E010 to workaround VM hang/freeze issue? -- WBR Sergey Kruchatov --f46d0444741f678bd804d49246d2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

There is well known bug in XenS= erver 6.1 when Windows VMs hang/freeze during intensive disk operation (pre= sumably due to race condition somewhere in xentools drivers in multi-vCPU W= indows systems).

Best description and discussion of mentioned problem wo= uld be found there=C2=A0http://forums.citrix.com/threa= d.jspa?threadID=3D314906&start=3D0&tstart=3D0

In our production site (pooled=C2=A0dual XCP 1.6 = final) we've expected above problem for every Windows XP 32 bit VM as w= ell as for Windows 2003 Servers 32-bit. While Windows 2008/2008R2 servers w= ork fine.

Last year Citrix published temporary workar= ound for above problem - reduce vCPU to 1 for=C2=A0affected VMs. It's r= eally helps but could be used in low/middle CPU load=C2=A0environment.
Another workaround were found by someone in community - previous version fr= om XenTools - exactly XS602E009 works fine.

Everything stated above = has been detailed in very tricky (as per my opinion) Citrix article there <= a href=3D"http://support.citrix.com/article/CTX135099">http://support.citri= x.com/article/CTX135099.

Recently Citrix published long awaited pair of Hot Fixes - =C2=A0XS61E0= 09 and XS61E010.

XS61E009 (http://support.citrix.com/article/CTX136252) contains pa= tches for some core functions (xapi-core, xapi-xenopsd, xapi-firmware) whil= e XS61E010 (http://= support.citrix.com/article/CTX136253) provides xentools replacement. Wh= at's more interest xentools from XS61E010 contains new and legacy drive= rs - new with Windows 8/Server 2012 support while legacy - just renamed too= ls from XS602E009.=C2=A0In XS61E010's installation prerequisites stated= that it can't be implemented without XS61E009.

So, finally, my question is - i= s there some way to deploy core patches from XS61E009 into XCP 1.6?=C2=A0
Or I just can use legacy windows driver from XS61E010 to wor= karound VM hang/freeze issue?

--=C2=A0
WBR

Sergey Kr= uchatov
--f46d0444741f678bd804d49246d2-- --===============7602736853626542624== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============7602736853626542624==--
On Mon, Jan 1= 4, 2013 at 7:25 PM, John Else <john.else@citrix.com> wrot= e:

There=E2=80=99s also a known bug in XCP 1.6, where the API QoS setti= ngs don=E2=80=99t actually get passed down to Xen. The master branch patch = is here: https://github.com/xen-org/x= en-api/commit/4fb4b96b10c2d40cd5e166845659f27882c6dae5

=C2=A0

John<= /span>

=C2=A0

From:= xen-api-bounces@lists.xen.o= rg [mailto:xen-api-bounces@lists.xen.org] On Behalf Of George Shukli= n
Sent: 14 January 2013 13:33
To: xen-api@lists.xen.org
Subject: Re: [Xen-API] qos_algorithm_type=3Dratelimit

=C2=A0

14.01.2013 03:55, Matthew Spah =D0=BF=D0=B8=D1= =88=D0=B5=D1=82:

Hey everyone,

=C2=A0

I'm currently testing and do= cumenting the qos parameters for VIF interfaces. I've set up two VMs wi= th VIF interfaces attached to an internal network. I've set the followi= ng qos parameters on each VIF interface.

=C2=A0

xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_= type=3Dratelimit

xe vif-param-set uuid=3D<VIF UUID> qos_algorithm_params:kbps=3D1= 00

=C2=A0 =C2=A0

iperf is showing me bandwidth rates between the two= VMS that aren't limited to 100 kbps. Am I missing something?=C2=A0<= /u>

=C2=A0

kbps is not kbps, b= ut a KiloBYTESperSecond. Really strange, but it is. kbps=3D12 will make it = 100kpbs.


_______________________________________________=
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api