Recent content by prometheanfire

you can integrate this in with proxmox's networking as a 'patch' like this. You create the bridges with nothing but the VMs attached. Then you script out the building of the vlans and bridges and add that script to rc.local here is my script, note that even though I add bridges that already...

Odd, link worked for me. I'll describe the commands needed though. In this example I have two vlans, vlan 2 and 4. vlan 4 is for a group of vms, untagged. vlan 2 is tagged only. I have vms 110-112 on vlan 4 untagged. I have vm 113 on vlan 2 and 4 tagged. brctl addbr br-trunk brclt addbr...

Just so people know. Found this. My solution will be to have eth0 -> br0 -> vif and split of vlans based on br0, not eth0 Found the solution here - http://blog.davidvassallo.me/2012/05/05/kvm-brctl-in-linux-bringing-vlans-to-the-guests/ One way that proxmox can fix this is to do the...

I'm running Vyatta in a VM as my firewall and wish to use vlan trunking to simplify my configuration (I have 80 or so vlans). Is it possible to just pass through one interface into the VM that contains the entire trunk?

I have a large disk attached to a VM I'm using (10TB). I don't want to have this disk backed up with all the other disks (about 700G). What can I do to disable to backing up of that disk, but allow the primary disk of that VM to be backed up? running 2.1 virtio0: vm-os:vm102-disk-1 virtio1...

It should work now as of http://git.kernel.org/linus/07700a94b00a4fcbbfb07d1b72dc112a0e036735 Is there any way we can get this as a test kernel?

Currently,when a VM uses multiple disks and you set a backup job you can only backup the entire VM or not. Meaning you cannot choose a single disk from the VM to backup. Is this issue fixed in proxmox-2.0 I'd like to avoid backing up terabytes of data :|

I added intel_iommu=on,igfx_off,pass-through and tried only intel_iommu=on added onto the kernel boot. Both allow the bridge to be passed through but not the device beyond it.

from what I can tell, the 2.6.35 kernel is not working with IOMMU, is that right? The device is behind a pcie to pci bridge, do I need to specify the bridge device only (as it is now), or do I need specify both devices (adding 02:08.0)? conf file name: pbx bootdisk: virtio0 vlan3...

on the disk line in the conf file cat /etc/qemu-server/101.conf name: http bootdisk: virtio0 ostype: l26 memory: 1024 onboot: 0 sockets: 1 boot: c freeze: 0 cpuunits: 1000 acpi: 1 kvm: 1 cores: 4 description: dns,wiki,blog<br>10.0.1.3 vlan3: virtio=12:12:12:12:12:12 virtio0...

This is something I may test down the line then (2.3 months). The only other thing I can think of that would prevent me from using proxmox is user managment (looking at ganeti too).

ad2. So storage like glusterfs or in this case ceph would work (just to be clear). Thanks for the quick reply.

I am planing a buildout and trying to get a feel of what virt software I wish to use (I know it is going to be kvm based). DRBD does not seem to be capable of scaling as I would need it. I am trying to get rid of the requirement of a san and ceph looks like it can fill that hole quite well...

Ceph?

I use the following format virtio0: vm-os:vm-103-disk-1,cache=none