Recent content by Kyc

Well, you can try stopping the VM, unmounting the HDD500GB partition and undeleting the file: http://extundelete.sourceforge.net/ I'd suggesting copying all information that you want to keep that's running inside the VM to another computer first. It's very likely that your disk image won't be...

Cesar, Looking at our documentation we can't use ALB. Our servers shared NIC Port-1 with out IMM module. When using ALB we aren't able to access the IMM module at all, so we went with XOR instead.

It is possible that ALB could be a better protocol to use for bonding, unfortunately I can't test this on my production servers.

Good to know that my laziness hasn't cost me any speed ;)

Is the guest OS Linux? If so, are the mounted partitions managed by LVM? If the data inside the VM is accessible, I'd create an LVM snapshot inside the VM, then use dd to make an image of the snapshot and transfer it over the network to another box, then restore it on a fresh VM and test...

I'm pretty sure that in XOR the bonding module does MAC address matching, so that only one NIC is used when communicating to any specific destination MAC. When I did my testing with multiple streams I didn't get full transfer speeds with XOR, I got around 140MB/s, but I was topping out at...

This is pretty much what I'm running in production. In my environment everything is on 1gb ethernet, the storage servers (Gluster) have 8x 1gb bonded connections in LACP (server and switch need configuration), the Proxmox servers have 2x 1gb bonded in XOR and things run pretty well. If I were...

Yep, this topology is the way you'd want to go. If possible go for 10gb ethernet or infiniband on your storage backend.

I'm using Gluster in my production environment for storage. My Gluster cluster consists of 6 nodes, 4x 1TB bricks in each server, in distribute-replicate. The Gluster nodes replicate on private 10GB network (2 nic bond, active-passive) and clients connect on a 1GB network (2 nic, XOR...

Looking at the documentation, you don't have the vlan aliases or vlan specific bridges in your /etc/network/interfaces configuration: http://pve.proxmox.com/wiki/Vlans

I haven't had any issue with it. My test cluster was made up of 4 old IBM servers and 2 old Dell servers with an old fibre channel storage array. Haven't seen any issues, even migrating VMs between the different CPUs (Dual-Core AMD Opterons and Xeon 5110s).

According to the wiki you just need to change the network entry: http://pve.proxmox.com/wiki/Vlan I would have through you'd need to create vlan eth and bridge aliases... I don't have a test environment to play around with this to test, if the wiki method doesn't work this is a really...

You'll need to mount the storage or create an LVM group on the storage. If you've mounted the storage, click the datacenter folder and select the storage tab, then click the add drop-down and select directory. You can select what you want to store in the drive (content). If you have...

The easiest thing would be to just change the setting in /etc/network/interfaces (through a shell connection), then change the route yourself: route del default gw X.X.X.X {bridge interface} route add default gw X.X.X.X {bridge interface} If/when you reboot, or trip over the power cable, when...

If you're able to boot off a linux (any distro) USB stick or DVD you can chroot into the environment and re-install mdadm: 1) Boot to the live-distro 2) If the packages aren't already there, install mdadm 3) Mount your Proxmox partitions (I assume you're mounting the proxmox root partition at...