Search results

I am probably going to write a small script for the web interface so you can do it easily through the web. Place a link on the Virtual Machine Configuration page so you can throttle that virtual machine's bandwidth.

After searching the forum and alot of trial and error i figured out how to throttle bandwidth. I used the script below. Where it says IF= i put the "tap id" that i got from running ifconfig. Example: tap313i0d0 Link encap:Ethernet HWaddr 7a:71:f6:1e:0a:fb inet6 addr...

Seagate Cheetah i believe. It has nothing to do with the backup process though. My backups go to NFS.

I don't have any with 0 load at the moment but here is a server with the least amount of load. proxmox10:~# pveperf CPU BOGOMIPS: 38570.14 REGEX/SECOND: 1103118 HD SIZE: 73.33 GB (/dev/mapper/pve-root) BUFFERED READS: 76.76 MB/sec AVERAGE SEEK TIME: 13.41 ms...

Ah .. thanks!

Is there a place where the PVE commands are listed?

When ever i have backups in place i tend to lose my web interface and the nodes lose sync. If i ssh into a node and give a simple command like qm list .. it just hangs and nothing happens. Well after rebooting all of my nodes i was able to get everything working except when i click on backup i...

So after checking the disks they seem to be fine. It seems to me that there is some sort of issue with the uuid.

I think that might be the case. I am not sure how to check the disks though?

The iSCSI is openfiler. This server has been running for about 8 months with no problems, but crashed over the weekend. I restored vms from backups and redid the openfiler storage but now i can not add it. I was able to connect to it will a windows 7 machine. I can set up the iSCSI part okay...

Failed to read physical volume "/dev/disk/by-id/scsi-14f504e46494c45003469416e39552d5a7952482d66365541"

This is the error i am getting when i try to create a new LVM on ISCSI. Error: command '/sbin/pvs --separator : --noheadings --units k --unbuffered --nosuffix --options pv_name,pv_size,vg_name,pv_uuid /dev/disk/by-id/scsi-14f504e46494c45003469416e39552d5a7952482d66365541' failed with exit code...

I am using 1.8 and do not have this problem. The only ip allowed to connect to my storage is the "storage NIC" on my node. So the node could not use the other NICs to connect. Further more the "storage NIC" is physically on a different network. Works well for me. Here is a example of what my net...

Works well in both. There is a PBX In A Flash container already made for OpenVZ. Running a native PBX IN A Flash kernel in KVM works fine also.

I wrote a small script that stores all of the config files onto a FTP server. If a server "brutally" crashes then i just click a button and all the configs from that server will be uploaded to a back up server of my choosing. Its not seemless like Vmware but its better then losing the configs.

The migration takes place with the NIC that is allowed to access the storage weather you set that up to be the management NIC or not is up to you. In my setup i have a NIC for the storage network, a NIC for the vm internet access and a NIC for management. This is not hard to do with the current...

There are many problems with running asterisk with Vmware. You will get choppy audio on IVR recording and Voicemail. Asterisk works very well under KVM and OpenVZ. This is why we went to Proxmox.

So i was finally able to get this problem solved. One weird thing i noticed though (maybe it is not werid because i am not a linux guru) I have 3 nics in my nodes. One is vmbr0 for VM's to connect to the internet. eth1 connects to the storage. and eth2 is for management. I have a config file...

I have done this in the past. What i did was mount the new ISCSI target to the cluster then copied the imaged from one directory to a other. I don't remember all of the things i did but it something like.. # cd /dev/OLDISCSI # cp vm-101-disk-1 /dev/NEWISCSI Then edit: #nano...

How can i make it so that the virtual machines in my cluster can not communicate with each other? I have tried setting up VLANS and that did not work. I tried PVLANS, VACL also with no avail. My other thought is that the virtual Switch must allow them to talk. Any help would be greatly aprceaciated.