Hi,
I wonder how in OpenNebula we can create an empty disk on-the-fly,
attach it to a VM (up to here, this is fine), then detach the disk and
save it for later reuse.
I could not found a way to do so.
Persistency seems more image related, not hot disks. But users cannot
create images so easily
So you have a virtual serial console *alongside* noVNS working?
On Wed, Nov 19, 2014 at 5:35 PM, Liu, Gene gene@alcatel-lucent.com wrote:
FYI.
We added virtual serial console feature on our private cloud via adding
and modifying a few back-end scripts and UI change a little bit.
Gene
Hello,
I install open nebula 4.8 on centos 7 as described in quickstarts and confiture
my private network as it was showed in example:
NAME = private
BRIDGE = br0
AR = [
TYPE = IP4,
IP = 192.168.0.100,
SIZE = 3
]
Starting vm I have got IP 192.168.0.100, but I can’t connect to
On Thursday 20 November 2014 11:57:17 Nikolaj Majorov wrote:
Hello,
I install open nebula 4.8 on centos 7 as described in quickstarts and
confiture my private network as it was showed in example:
NAME = private
BRIDGE = br0
AR = [
TYPE = IP4,
IP = 192.168.0.100,
SIZE
Hi Liu,
Would you be interested in contributing it back? Maybe we could either use
the addons collections for it, or include it in the main distribution
Thanks
On Wed Nov 19 2014 at 4:38:31 PM Liu, Gene gene@alcatel-lucent.com
wrote:
FYI.
We added virtual serial console feature on
HI,
unfortunately I can’t connect … :-(
Here is my new configuration:
$cat mynetwork_virbr0.one
NAME = 2private
BRIDGE = virbr0
AR = [
TYPE = IP4,
IP = 192.168.0.100,
SIZE = 3
]
$ tracepath -n 192.168.0.101
1: 46.4.99.350.052ms pmtu
Please post the output of
ip a
ip r
ip neigh show
iptables -nvL
from the hardwarenode the vm is running on and from within the vm.
cheers
t.
On 20. November 2014 16:44:29 MEZ, Nikolaj Majorov niko...@majorov.biz wrote:
HI,
unfortunately I can’t connect … :-(
Here is my new configuration:
hi Thomas,
thanks for help.
On the open nebula host server :
——-
[root@CentOS-70-64-minimal ~]# ip a
1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft
Hello Nikolaj,
I think the problem is that your AR uses a wrong network prefix. virbr0 is
configured
with 192.168.122.0/24 prefix and your definition in the AR is IP =
192.168.0.100.
Best,
Valentin
On Thu, Nov 20, 2014 at 6:20 PM, Nikolaj Majorov niko...@majorov.biz
wrote:
hi Thomas,
thanks
Hi,
many thanks Valentin ! Thanks Thomas !
Valentin you are right ! changing prefix , allow me to connect to the guest
vm… Cool !
regards,
Nikolaj
On 20.11.2014, at 17:56, Valentin Bud valentin@gmail.com wrote:
Hello Nikolaj,
I think the problem is that your AR uses a wrong
Hi Nikolaj,
Thomas deservers all the credit, he is wise enough to ask the right
questions.
After this was just a matter of text scraping :).
Best
Valentin
On Thu, Nov 20, 2014 at 7:23 PM, Nikolaj Majorov niko...@majorov.biz
wrote:
Hi,
many thanks Valentin ! Thanks Thomas !
Valentin you
11 matches
Mail list logo