Hello, I was trying to get Proxmox and Deluged working but ran into a problem where speed would spike from 11MB to 200KB and everywhere in between. *I tried different kernel but didn't work*
This happened inside a container and on the host itself.
Also disk IO would go to 50% when d/l torrent. I thought it was a disk io problem and tried a few disk io optimization which did not help. People at FreeNode ##proxmox helped a lot but I still could not figure out the reason.
Solution:
Finally I installed Debian 7.5 Wheezy and installed Proxmox using the following guide https://pve.proxmox.com/wiki/Install..._Debian_Wheezy This solved the problem and I now longer see spikes with under 10% io under load.
Pay CLOSE ATTENTION and don't forget to partition properly.
---Partitioning Guide *-Really simple guide that got me through it :)
http://forum.online.net/index.php?/t...capabillities/
-Few things of note:
Before you do vgextend, you do vgcreate
Toward the end just remember to create a /var/lib/vz directory so it can be mounted.
-IRC stuff which was really helpful
04:15 < dima202> how do i find the name of my linux-image-kernel_3.10.23 (my kernel name 'linux-image-3.10.23-amd64')
04:24 < Jb_boin> and its never a good idea to remove the running kernel, at least reboot on the "new" one and check that it works well before thinking about removing the previous one
04:30 < Jb_boin> if the server is already booting on the local hard drive you just have to figure out in which position is the proxmox kernel on the grub config file and change the default value
04:31 < Jb_boin> by default its 'set default="0"' where 0 means it will boot on the first kernel entry listed on /boot/grub/grub.cfg
04:33 < dima202> http://pastebin.com/KDvtKC8W
04:35 < Jb_boin> well if you dont want to manually do it, you can edit /etc/default/grub and change the DEFAULT=0 to DEFAULT=1 then run update-grub --Rebooted Proxmox
04:48 < dima202> unfortunately now proxmox is behaving quite oddly
04:49 < Jb_boin> are you on the right kernel at least? :)
04:50 < dima202> yeah looks like 2.6.32-26-pve
04:50 < Jb_boin> what is the issue now?
04:52 < dima202> proxmox shows 2 containers which previously failed to install
04:52 < dima202> can't delete them
04:52 < dima202> cant create new ones because it says already exiss no matter the ct number
--Found answer on another thread Goto /etc/pve/nodes/!!"YOUR HOST"!!/openvz
--Fixed odd behavior by editing /etc/apt/sources with latest repositories https://pve.proxmox.com/wiki/Package_repositories
--apt-get update
--apt-get upgrade
05:09 < dima202> Jb_boin: your kung fu is awesome. i think i got it to the way i can use it
05:15 < Jb_boin> :)
--Useful Stuff
pveversion -v Show you the current kernel version & more.
This happened inside a container and on the host itself.
Also disk IO would go to 50% when d/l torrent. I thought it was a disk io problem and tried a few disk io optimization which did not help. People at FreeNode ##proxmox helped a lot but I still could not figure out the reason.
Solution:
Finally I installed Debian 7.5 Wheezy and installed Proxmox using the following guide https://pve.proxmox.com/wiki/Install..._Debian_Wheezy This solved the problem and I now longer see spikes with under 10% io under load.
Pay CLOSE ATTENTION and don't forget to partition properly.
---Partitioning Guide *-Really simple guide that got me through it :)
http://forum.online.net/index.php?/t...capabillities/
-Few things of note:
Before you do vgextend, you do vgcreate
Toward the end just remember to create a /var/lib/vz directory so it can be mounted.
-IRC stuff which was really helpful
04:15 < dima202> how do i find the name of my linux-image-kernel_3.10.23 (my kernel name 'linux-image-3.10.23-amd64')
04:24 < Jb_boin> and its never a good idea to remove the running kernel, at least reboot on the "new" one and check that it works well before thinking about removing the previous one
04:30 < Jb_boin> if the server is already booting on the local hard drive you just have to figure out in which position is the proxmox kernel on the grub config file and change the default value
04:31 < Jb_boin> by default its 'set default="0"' where 0 means it will boot on the first kernel entry listed on /boot/grub/grub.cfg
04:33 < dima202> http://pastebin.com/KDvtKC8W
04:35 < Jb_boin> well if you dont want to manually do it, you can edit /etc/default/grub and change the DEFAULT=0 to DEFAULT=1 then run update-grub --Rebooted Proxmox
04:48 < dima202> unfortunately now proxmox is behaving quite oddly
04:49 < Jb_boin> are you on the right kernel at least? :)
04:50 < dima202> yeah looks like 2.6.32-26-pve
04:50 < Jb_boin> what is the issue now?
04:52 < dima202> proxmox shows 2 containers which previously failed to install
04:52 < dima202> can't delete them
04:52 < dima202> cant create new ones because it says already exiss no matter the ct number
--Found answer on another thread Goto /etc/pve/nodes/!!"YOUR HOST"!!/openvz
--Fixed odd behavior by editing /etc/apt/sources with latest repositories https://pve.proxmox.com/wiki/Package_repositories
--apt-get update
--apt-get upgrade
05:09 < dima202> Jb_boin: your kung fu is awesome. i think i got it to the way i can use it
05:15 < Jb_boin> :)
--Useful Stuff
pveversion -v Show you the current kernel version & more.