OpenVZ Forum


Home » General » Support » Container start failure when ipv6 is disabled
Re: Container start failure when ipv6 is disabled [message #38587 is a reply to message #38584] Tue, 05 January 2010 22:14 Go to previous messageGo to previous message
tdaniel is currently offline  tdaniel
Messages: 2
Registered: January 2010
Location: Romania
Junior Member
Well,

Since ipv6 is not widely available and still not mainstream there are a few reasons why ipv6 would need to be disabled due to compatibility reasons.

I didn't encountered a scenario that would require ipv6 to be explicitly disabled but a warning would be a more correct approach to signal a sysadmin that ipv6 is required for a vps to start than a stack dump don't you agree ?

The bug mentioned by you seems unrelated to the situation I encountered since it clearly stated that ipv6 is disabled when an ipv6 address was used for a vps.

I didn't attempted to assign an ipv6 address to my containers, they all use ipv4 addresses.

The cryptic nature of the error message determined me to create this thread more with a fyi purpose than to require a fix for it.

Otherwise i would have opened a bug report in the bugzilla.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: limiting cpu core number
Next Topic: How to sync "production" host into "test" host?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon Jan 26 23:57:21 GMT 2026

Total time taken to generate the page: 0.76136 seconds
Powered by FUDforum Powered by Virtuozzo Containers