>
> LOL. We have been testing this (bonding *and* vlans).
>
> Once you understand how it works it makes sense, but you need to
> understand it first and most people researching this are probably used
> to the fantastic vmware tooling that keeps it all hidden.
>
>
>
One of the environments I built a
On Sat, Feb 2, 2013 at 2:12 AM, James Hogarth wrote:
> If you need bonding or vlans it becomes more complicated ;-)
LOL. We have been testing this (bonding *and* vlans).
Once you understand how it works it makes sense, but you need to
understand it first and most people researching this are pro
Am 02.02.2013 16:58, schrieb James Hogarth:
>> Isn't the rhel way to install NetworkManager anyway? Because then you can
> forget all your ifcfg scripts anyway because they will be overwritten by NM.
>> At least that was the cause when i had NetworkManager installed... (That
> was why i removed it
>
> Isn't the rhel way to install NetworkManager anyway? Because then you can
forget all your ifcfg scripts anyway because they will be overwritten by NM.
> At least that was the cause when i had NetworkManager installed... (That
was why i removed it if i remember correctly)
> Does anyone have a go
Am 02.02.2013 14:58, schrieb skull:
> Am 01.02.2013 23:39, schrieb James Hogarth:
>> You don't need a DE for that just yum install xauth virt-manager and ssh -X
>> to forward it to your local X server.
>>
> By the way I would be very interested in that bit, because I never
> managed to actually get
Am 01.02.2013 23:39, schrieb James Hogarth:
> You don't need a DE for that just yum install xauth virt-manager and ssh -X
> to forward it to your local X server.
>
By the way I would be very interested in that bit, because I never
managed to actually get X forwarding to work from a server running
Am 02.02.2013 02:12, schrieb James Hogarth:
>> What i did in terms of network changes was the following script. It's an
>> old one i used when i didn't work with virsh, because i followed an old
>> tutorial for kvm-qemu on CentOS 5.
>> It basically creates a new bridge called bg0, creates a tap0 in
>
> What i did in terms of network changes was the following script. It's an
> old one i used when i didn't work with virsh, because i followed an old
> tutorial for kvm-qemu on CentOS 5.
> It basically creates a new bridge called bg0, creates a tap0 interface,
> and connects eth0 and tap0 to the b
Am 01.02.2013 23:56, schrieb skull:
> Am 01.02.2013 23:39, schrieb James Hogarth:
>>> Does anyone have an idea how to recreate the default virbr0?
>>> Is it doable via virsh? I don't have a DE installed on this server, so
>>> no virtual-manager. I am willing to go that far if it's worth it though.
Am 01.02.2013 23:39, schrieb James Hogarth:
>> Does anyone have an idea how to recreate the default virbr0?
>> Is it doable via virsh? I don't have a DE installed on this server, so
>> no virtual-manager. I am willing to go that far if it's worth it though.
>>
> You don't need a DE for that just yu
>
> Does anyone have an idea how to recreate the default virbr0?
> Is it doable via virsh? I don't have a DE installed on this server, so
> no virtual-manager. I am willing to go that far if it's worth it though.
>
You don't need a DE for that just yum install xauth virt-manager and ssh -X
to forw
Hello CentOS mailinglist
I am running CentOS 6.3 with qemu-kvm and libvirt.
I was experimenting with bridged VM networking. Usually the VMs run over
the network device virbr0.
So i created a new bridge with brctl and added my eth0 to that bridge.
Not touching virbr0 or it's configuration at all.
12 matches
Mail list logo
