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

[John Levon <levon@xxxxxxxxxxxxxxxxx>]

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