Search results

Now I have connectivity between the host and a kvm guest, both on untagged and vlan11 interfaces: root@pve1:~# ping -c 5 172.16.11.2 PING 172.16.11.2 (172.16.11.2) 56(84) bytes of data. 64 bytes from 172.16.11.2: icmp_req=1 ttl=64 time=0.403 ms 64 bytes from 172.16.11.2: icmp_req=2 ttl=64...

Moving the host IP address into the bridge rather than an IntPort has restored connectivity to the CTs with venet addresses. I re-orderd the interfaces file for readability, manually removed the vestigial vmbr0 info, and renamed the OVS bridge to vmbr0: -----------------...

I reconfigured the host to use OVS for everything in order to gain access to eth0. The OVS bridge was not given an Ethernet address -- instead, those were assigned to each IntPort. Now I can ping the routers on both 192.168.44.1 and 172.16.88.1 from the host. Unfortunately, this arrangement...

Any reason you can't use CTs for this? They're really quick (to set up, when operating, and to tear down.)

Decided to move the existing Linux bridge to vmbr1 in order to end up with an OVS bridge named vmbr0. Turns out that removing an active bridge really just deactivates it: Removing again and restarting does not change this: --- /etc/network/interfaces 2014-04-17 11:54:24.000000000 -0600 +++...

Straight replacement won't fly using the GUI. I removed the existing vmbr0, but when trying to add a new one I get a conflict with the (supposedly removed) config: So I created a new vmbr1 with no IP address, then an IntPort with the existing host IP and gateway settings: Here are the...

About what I figured. The VLANs never worked right anyway, so I'll just delete them before I start. Edit:root@pve1:~# brctl show bridge name bridge id STP enabled interfaces vmbr0 8000.002354458b04 no eth0 I'm hoping once I have the OVS bridge on eth0 that I'll be...

Right, makes perfect sense. So how do I migrate an existing host from Linux bridging to OVS? Is it as simple as removing the Linux bridge and adding the OVS bridge to the node? My concern is that I lose connectivity with the host during the process and run the potential risk of losing all net...

Thanks, that does actually make more sense. As it turns out, vmbr1 does not actually have eth0 in it, which would explain the lack of connectivity across those addresses:root@pve1:~# brctl show bridge name bridge id STP enabled interfaces vmbr0 8000.002354458b04 no...

Congratulations on a truly useful product. If imitation is the sincerest form of flattery, consider this http://www.informationweek.com/cloud/software-as-a-service/red-hat-touts-linux-containers-for-cloud/d/d-id/1204498

Understood -- just wanted to be clear that we were not using VLANs at this time, and that there is currently no firewall between the internal subnets. Update: Trying to create a new Linux bridge with a port on eth0 gives me the same kind of error:port 'eth0' is already used on interface...

Not at this time. 192.168.44.x subnet is fed by a pfSense box which knows nothing about 172.16.anything. The new upstream is connected to a Ubiquiti EdgeRouter Lite which currently has a minimal ruleset (NAT, block all inbound connections.) One of the KVM hosts is Untangle, which I plan to...

The issue came up when we added a second subnet. Existing hosts are on 192.168.44.x and the new subnet (the first of several planned) is 172.16.88.x, on which there is also a new router served by a new upstream provider. KVM guests can ping the router and some workstations with addresses in...

The intent is to move the entire host to OVS, assuming that will enable the CTs to talk to the KVM guests as I've been trying to configure for the past couple of weeks. If I delete the original vmbr, I lose the host completely other than console access. Not sure I want to make that leap, just...

Does anyone have OVS working alongside Linux bridging on the same NIC? Does OVS require exclusive access?

Gotcha -- makes far more sense now. I was hoping to find a way to boot the virgin XP Mode image inside KVM and just modify from there -- the goal being a bootable minimal, naked, but unregistered XP image from which to create other VMs on ProxMox. I can probably borrow a Win 7 laptop and...

More info: I get a similar error: port 'eth0' is already used on interface 'vmbr1' (500) if I enter nothing in the 'Bridge Ports' field, or if I enter an existing vmbr there.

Excellent! You lost me on these two. I'm using the unmodified vhd file extracted from the XP Mode distribution .exe archive. I did notice that the Proxmox GUI reports a 32G disk even though the qcow2 file is only 1.1G. I'll edit the .conf file and see what that does. Edit: Entering '1.1G'...

Now that I have the openvswitch-switch package installed on v3.2, I have GUI options for OVS showing. Given the current lack of documentation, I'm going to see what I can learn with a bit of brute force experimentation. Host is currently using vmbr0 (bridged to eth0) with its primary IP. I...

Thanks. I'm going to start a new thread mentioning OVS in the title.