WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] That xenstored console leak...

To: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-devel] That xenstored console leak...
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Mon, 14 Jan 2008 20:08:53 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 14 Jan 2008 12:09:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <478BB78E.5020709@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080111173914.GA24773@xxxxxxxxxxxxxxxxxxxxxxx> <4787C804.4010909@xxxxxxxxxx> <478BB78E.5020709@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Jan 14, 2008 at 12:27:10PM -0700, Jim Fehlig wrote:

> After some investigation I have found that the /vm/<uuid> leak is caused
> by c/s 15957 (later modified by c/s 15967).  Reverting these changesets
> removes the leak on 3.2 RC4.  Further, when reverting c/s 15957 I am not
> seeing the issue it claims to fix - i.e. I am not losing the vif mac
> address when doing localhost migrations of PV or HVM domU's.
> 
> Keir - under what circumstances was vif mac address being lost?  I am
> unable to reproduce that behavior on RC4 with 15967 and 15957 reverted.

I see the behaviour in 3.1 with HVM domains. If I live migrate twice,
then the MAC address is lost, and a new random one is generated:

$ grep spawning /tmp/xend.log  | tail -3
[2008-01-10 23:55:01 101730] INFO (image:443) spawning device models: 
/usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '31', '-vcpus', 
'1', '-boot', 'c', '-usb', '-k', 'en-us', '-domain-name', 'winxp', '-net', 
'nic,vlan=0,macaddr=00:16:3e:52:76:6d,model=rtl8139', '-net', 
'tap,vlan=0,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused']
[2008-01-10 23:58:25 101730] INFO (image:443) spawning device models: 
/usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '32', '-vcpus', 
'1', '-boot', 'c', '-usb', '-k', 'en-us', '-domain-name', 'winxp', '-net', 
'nic,vlan=0,macaddr=00:16:3e:52:76:6d,model=rtl8139', '-net', 
'tap,vlan=0,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused', '-loadvm', 
'/tmp/xen.qemu-dm.32']
[2008-01-11 00:00:43 101730] INFO (image:443) spawning device models: 
/usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '33', '-vcpus', 
'1', '-boot', 'c', '-usb', '-k', 'en-us', '-domain-name', 'winxp', '-net', 
'nic,vlan=0,macaddr=00:16:3e:0d:93:13,model=rtl8139', '-net', 
'tap,vlan=0,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused', '-loadvm', 
'/tmp/xen.qemu-dm.33']

I don't have to do anything "special", this happens every time on 3.1. I
presume that the troublesome changeset fixes this exact problem.

regards
john

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel