Public bug reported:
I'm using vmbuilder and specifying hard coded fixed IP addresses with
--ip, --mask, --gw and --dns which is working fine for IPv4.
However I also want to provide IPv6 address to the virtual machine.
Adding a 'inet6' stanza to /etc/network/interfaces works, but requires
me to
** Description changed:
- I'm using vmbuilder and specifying hard coded fixed IP addresses with
- --ip, --mask, --gw and --dns which is working fine for IPv4.
+ I use vmbuilder and specify hard coded fixed IP addresses with --ip,
+ --mask, --gw and --dns. It works fine for IPv4.
However I
I'm using --dns 217.75.96.11,217.75.96.12 which does the right thing for
/etc/resolv.conf but the generated /etc/network/interfaces looks like
this:
dns-nameservers 217.75.96.11,217.75.96.12
I think they should be SPC-separated?
Still, I think multiple --dns parameters is more clear
One alternative solution to just naming the image after the hostname
would be to introduce a new parameter --image (or something) which would
take the filename of the image to generate. For example, --image
/var/lib/libvirt/images/webserver.qcow2. I always found it confusing to
have one
*** This bug is a duplicate of bug 539460 ***
https://bugs.launchpad.net/bugs/539460
The error message in bug #539460 is slightly different than this one.
But maybe the cause of the problem is the same. I also get the error
message displayed in this bug.
--
AttributeError: 'Hardy' object
