Thanks for your answer!
oneadmin@Arbeitsrechner:~/one-templates$ brctl show
bridge namebridge idSTP enabledinterfaces
virbr08000.fe00c0a87a05yesvnet0
Cheers,
Marco
Am 18.01.2013 14:43, schrieb Javier Fontan:
Can you check that virbr0 bridge is associated
In case its important:
oneadmin@Arbeitsrechner:~/one-templates$ ifconfig vnet0
vnet0 Link encap:Ethernet Hardware Adresse fe:00:c0:a8:7a:05
inet6-Adresse: fe80::fc00:c0ff:fea8:7a05/64
Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
virbr0 is a bridge automatically created by libvirt and is not
associated to any physical interface (vnet0 is not a physical
interface). You should create a new bridge or associate a physical
interface to virbr0. I think it is better to create a new one. If you
are using ubuntu you can find more
Thank you!
I will try it, but why is ttylinux working when virbr0 isn't associated
with any physical interface?
Am 21.01.2013 12:10, schrieb Javier Fontan:
virbr0 is a bridge automatically created by libvirt and is not
associated to any physical interface (vnet0 is not a physical
-- Forwarded message --
From: Mihály Héder mer...@sztaki.hu
Date: 21 January 2013 12:34
Subject: Re: [one-users] iSCSI multipath
To: Miloš Kozák milos.ko...@lejmr.com
Cc: users users@lists.opennebula.org
Hi!
Last time we could test an Equalogic it did not have option for
Hello,
I'm digging this thread up because I just found out the reason why this
could be happening. Apparently RHEL/CentOS doesn't have support for scsi
drivers in its kvm version. I suggest you use this device prefix: vd
(virtio) and try again.
cheers,
Jaime
On Tue, Nov 27, 2012 at 6:55 PM, jd
In Addition: The whole system is just on one computer so there is no
need for contacting other computers. And also no need for bridging?
Am 21.01.2013 12:23, schrieb Marco Jagodzinska:
Thank you!
I will try it, but why is ttylinux working when virbr0 isn't
associated with any physical
Hi,
lvm metadata[1] is simply stored on the disk. In the setup we are
discussing this happens to be a shared virtual disk on the storage,
so any other hosts that are attaching the same virtual disk should see
the changes as they happen, provided that they re-read the disk. This
re-reading step
Thank you. does it mean, that I can distribute metadata files located in
/etc/lvm on frontend onto other hosts and these hosts will see my
logical volumes? Is there any code in nebula which would provide it? Or
I need to update DS scripts to update/distribute LVM metadata among
servers?
Oh snap, that sounds great I didn't know about that.. it makes all
easier. In this scenario only frontend can work with LVM, so no issues
of concurrent change. Only one last think to make it really safe against
that. Is there any way to suppress LVM changes from hosts, make it read
only? And
Dear OpenNebula users,
We are happy to announce the creation of an OpenNebula News
distribution list, where where you will receive communications about
the project like new releases, community events, tutorials, workshops,
webinars, newsletters, cool hacks and more.
You can register for this
Hi,
I see that bug http://dev.opennebula.org/issues/1087 reappeared in
3.8.3. The sequence to repeat is:
1) create an image as save from VM (as an user in oneadmin group);
2) change owner to oneadmin;
3) delete image;
4) repeat (1) and (2) will fail saying [ImageChown] USER [0] already
owns
12 matches
Mail list logo
