[
https://issues.apache.org/jira/browse/CLOUDSTACK-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065518#comment-14065518
]
Wido den Hollander commented on CLOUDSTACK-7121:
------------------------------------------------
So I pushed the agent-ipv6 branch.
I tested it locally and it works for me.
This is what my logs tell me:
{quote}
2014-07-17 22:23:19,621 INFO [cloud.agent.Agent] (main:null) Agent [id = 2 :
type = LibvirtComputingResource : zone = 1 : pod = 1 : workers = 5 : host =
2a00:f10:11b:0:216:3eff:XXX:XXX : port = 8250
2014-07-17 22:23:19,638 INFO [utils.nio.NioClient] (Agent-Selector:null)
Connecting to 2a00:f10:11b:0:216:3eff:XXX:XXX:8250
2014-07-17 22:23:20,075 INFO [utils.nio.NioClient] (Agent-Selector:null)
Connected to 2a00:f10:11b:0:216:3eff:XXX:XXX:8250
{quote}
I can also see a open TCP connection over IPv6:
bq. tcp6 0 0 2a00:f10:11b:0:b0:59333 2a00:f10:11b:0:216:8250
ESTABLISHED
The agent also works for me.
> IPv6 support for KVM Agent communication with Management Server
> ---------------------------------------------------------------
>
> Key: CLOUDSTACK-7121
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7121
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, Management Server
> Affects Versions: Future
> Reporter: Wido den Hollander
> Assignee: Wido den Hollander
> Fix For: 4.5.0
>
>
> Currently the KVM Agent forces it's connection over IPv4. Although the
> management server also listens on port 8250 on IPv6 the Agent still forces
> the connection over IPv4.
> We should also allow this to be over IPv6 so administrators can deploy
> hypervisors with IPv6-only while Instances still have IPv4 connectivity.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
