[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] issue with passing mtu field in "network record" while creating network using Perl(RPC::XML) xen-api


  • To: Mike McClurg <mike.mcclurg@xxxxxxxxxx>, "Rawat, Vishwanath" <Vishwanath.Rawat@xxxxxxxxxx>
  • From: Rob Hoes <Rob.Hoes@xxxxxxxxxx>
  • Date: Thu, 15 Nov 2012 18:04:24 +0000
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: "xen-api@xxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxx>
  • Delivery-date: Thu, 15 Nov 2012 18:04:35 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
  • Thread-index: Ac3DVGK9Wofe7qpXT2SvO/HPSrIGYwABtG9A
  • Thread-topic: [Xen-API] issue with passing mtu field in "network record" while creating network using Perl(RPC::XML) xen-api

> >
> > So I kept both mTU and MTU having the same value. Still didn't work
> >
> >
> > $VAR1 = {
> >           'ErrorDescription' => [
> >                                 'FIELD_TYPE_ERROR',
> >                                 'mTU'
> >                               ],
> >           'Status' => 'Failure'
> >         };
> >
> 
> You're getting an error here because the type of MTU is a string. I have no
> idea why, but yes, it's a string, not an int. Same goes for the device number.

Indeed. All integers in the XenAPI are assumed to be 64 bit, but the XML-RPC 
standard only has a built-in type for 32-bit integers. For this reason, 
integers are encoded as a string of decimal digits in the wire protocol.

Cheers,
Rob

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.