Not sure if this is clear to everyone else so as a hint (I haven't
looked at the code for lxc) the "IPv6" address shown gives a pretty good
indication that something is parsing an IPv6 address and then
representing the first 32 bits as an IPv4 address.
The specified ip address is 2607:f088:...
whi
Sure thing, by "start" I assume you mean "create" since there is nothing
created yet. There are only three lines in the debug output, I'll just
paste it here:
root@cps3:~/lxc# lxc-create -n horizon-cps3 -f horizon-cps3.net.conf -t ubuntu
-l debug -o debug
lxc-create: No such file or directory - i
Public bug reported:
root@cps3:~/lxc# cat horizon-cps3.net.conf
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br18
lxc.network.name = eth0
lxc.network.hwaddr = 00:16:3e:00:02:70
lxc.network.ipv6 = 2607:f088:0:12::39
lxc.network.mtu = 9000
root@cps3:~/lxc# lxc-create -n horiz
Hello Stéphane,
I downloaded the packages manually, rebooted the node and the lxc
containers seem to have started nominally. Thanks for the info!
Serge,
Thanks again for the quick fix!
Cheers,
-Tim
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this
Thanks for the quick fix! Unfortunately, something else broke when I
pulled that package from the trusty repository. The lxc instance is
started but nothing runs. Starting it manually vs on boot produces the
same behavior and I only see these two lines when I start manually:
<4>init: console-setup
Public bug reported:
root@cps2-c1:/var/log/upstart# cat lxc.log
lxc-instance (os-api-cps2) start/running, process 2880
root@cps2-c1:/var/log/upstart# tail -f lxc-instance-os-api-cps2.log
lxc-start: failed to rename veth3ITMNG->eth0 : File exists
lxc-start: failed to setup netdev
lxc-start: faile
Possibly a new vector, I have IPv6 as well as IPv4 on a network. I see
this segment of the (rather large) host file:
fa:16:3e:9d:de:21,host-192-168-2-103.openstacklocal,192.168.2.103
fa:16:3e:9d:de:21,host-2607-f088-0-2--1339.openstacklocal,2607:f088:0:2::1339
When I remove the second line, and k
Sorry, I realized a few seconds after this went through that puppet was
broken by something else in my own environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170801
Title:
puppet needs to u
Public bug reported:
On a new raring install I have added puppet (which brings in facter) but
puppet won't start:
# service puppet restart
* Restarting puppet agent
/usr/lib/ruby/
Thanks Serge,
I tried loading a sparc64 class machine before loading your package with
the Debian package still installed and got to the OpenBIOS screen. After
I installed it, the same qemu-system-sparc64 invocation just remained a
dark black screen. The qemu-system-sparc binary seems to get me to
Aha, interesting. In fact, it would seem that you need cross-compilers
in any case since there are no sparc64 buildd nodes, if I am
understanding this correctly. ie: under Debian, fixing either one might
work but under Ubuntu, cross compiling is the only real solution.
--
You received this bug no
I should also add that under Debian there is an openbios-sparc package
which contains the actual openbios image:
$ ls -la /usr/share/{qemu,openbios}/openbios-sparc64
-rw-r--r-- 1 root root 737264 Jun 9 2012 /usr/share/openbios/openbios-sparc64
lrwxrwxrwx 1 root root 28 Jan 14 03:37 /usr/sha
Public bug reported:
It appears that a broken symlink is shipped instead of the actual
openbios image:
$ qemu-system-sparc64 phobos.raw
qemu: could not load prom 'openbios-sparc64'
$ dpkg-query -S openbios-sparc64
qemu-system-sparc: /usr/share/qemu/openbios-sparc64
$ ls -la /usr/share/qemu/op
13 matches
Mail list logo
