qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH 16/16] qapi-schema, qemu-options & slirp: Adding


From: Samuel Thibault
Subject: Re: [Qemu-devel] [PATCH 16/16] qapi-schema, qemu-options & slirp: Adding Qemu options for IPv6 addresses
Date: Tue, 22 Oct 2013 12:45:04 +0200
User-agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30)

Eric Blake, le Tue 22 Oct 2013 11:33:52 +0100, a écrit :
> On 10/22/2013 11:31 AM, Samuel Thibault wrote:
> > Hello,
> > 
> > Eric Blake, le Tue 22 Oct 2013 11:27:27 +0100, a écrit :
> >> On 10/22/2013 11:22 AM, Samuel Thibault wrote:
> >>> Eric Blake, le Mon 21 Oct 2013 22:04:23 +0100, a écrit :
> >>>>> +    '*ip6_prefix':      'str',
> >>>>
> >>>> Why is this a str instead of an integer?
> >>>
> >>> prefix would be e.g. fc00::1/64.
> >>
> >> That requires me to post-parse it. Would it be smarter to represent this
> >> as two elements, one for the "fc00::1" string, and another for the 64
> >> width, so that I don't have to post-parse?
> > 
> > It makes sense, yes, the syntax would be [ip6-prefix=net[/netsize]] . I
> > just don't know how to express that in qapi :)
> 
> '*ip6_net':'str', '*ip6_netsize':'int'
> 
> passed on the wire as:
> 
> "ip6_net":"fc00::1", "ip6_netsize":64

Err, so that means that the user would have to pass
"ip6-net=fc00::1,ip6_netsize=64"?  This would look awkward, compared to
the ipv4 situation, which is a mere "net=10.0.2.2/24".

Samuel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]