-Messaggio originale-
Da: Dan Kenigsberg [mailto:dan...@redhat.com]
Inviato: martedì 7 luglio 2015 18:13
A: NUNIN Roberto; m...@redhat.com
Cc: users@ovirt.org; ibar...@redhat.com
Oggetto: Re: R: R: R: R: R: [ovirt-users] R: PXE boot of a VM on vdsm don't
read
DHCP offer
On
Dear Michael,
The network scripts look exactly as we did that, and then during setting
up the host network we also got the “already enslaved” message which did
not cause a problem since it actually was enslaved, afterwards there were
proper vdsm generated interface files.
Though we have the
On Mon, Jul 06, 2015 at 10:33:59AM +0200, NUNIN Roberto wrote:
Hi Dan
Sorry for question: what do you mean for interface vnet ?
Currently our path is :
eno1 - eno2 bond0 - bond.3500 (VLAN) -- bridge - vm.
Which one of these ?
Moreover, reading Fabian
On Tue, Jul 07, 2015 at 10:14:54AM +0200, NUNIN Roberto wrote:
On Mon, Jul 06, 2015 at 10:33:59AM +0200, NUNIN Roberto wrote:
Hi Dan
Sorry for question: what do you mean for interface vnet ?
Currently our path is :
eno1 - eno2 bond0 - bond.3500 (VLAN) -- bridge
Hello List,
I have a 2 node replica Gluster Cluster in a Datacenter which i want to
remove completely.
1.) I put both nodes in maintenance and removed the DataCenter and the
Storage unter the Storage Tab.
But now i am stuck removing the Cluster, Hosts and GlusterVolume.
a) When i try to
Dear Soeren,
Thank you very much for your feedback. I think that the issue is that bonding
mode balance-alb (with no special switch configuration) does work while 802.3ad
(with appropriate switch configuration) does not.
With correct switch configuration, 802.3ad does connect the server to the
6 matches
Mail list logo
