RE: [Xen-API] Re: [Xen-users] XCP Set MTU not work after change XCP 1.0beta -> XCP 1.0 RC2

[Adrian Costin <adrian@xxxxxxxxxxx>]

Hi,

I've tested this in RC3 (should be the same for RC2) and while 
network-param-set does not have any effect on the actual PIFs, doing pif-unplug 
and then pif-plug will set the correct MTU on the interface.

I think this is the expected behavior, as network-param-set will just update 
the database. The actual configuration of the physical interface takes place on 
pif-plug.

Best regards,
Adrian Costin


-----Original Message-----
From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Todd Deshane
Sent: Saturday, February 19, 2011 4:03 AM
To: Jan MartinÅ
Cc: xen-users mailing list; xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Re: [Xen-users] XCP Set MTU not work after change XCP 
1.0beta -> XCP 1.0 RC2

adding xen-api to the CC.

dropping xen-devel from the CC.

2011/2/18 Jan MartinÅ <martinu@xxxxxxxxxxxx>:
> Hello,
>
> this command:
>
> xe network-param-set uuid=xxxxx MTU=9000
>
> sets MTU=9000 on bond and his slave PIFs.
>
> After change XCP 1.0beta to XCP 1.0 RC2, command has no effect to PIFs.

Thanks for the report.

Are others seeing this as well?

There was an rc3, but I don't think that it changed much in this space. Maybe 
Jon can comment to be sure.

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api