ProxMox Network hang...

B

BiagioParuolo

Active Member
Apr 29, 2009
256
0
36
Salerno - Italy
Hi,

I've a problem.
If we start a download of a file >10Mb, download and connection hang. This problem there is also on ProxMox console, not only in Vm.
Why?

pveversion -ve
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5

Thank you
 
I guess you have problems with network driver. Try to install proxmox kernel 2.6.32 or, if you don't care about OpenVZ support, 2.6.35. Time ago I had a lot of issues with connectivity and 2.6.18 that I solved with the upgrade.
To see the available packages use:
# aptitude search proxmox-ve-
and install the one you want. As far as I remember, kvm changes a lot since 2.6.18, so if you have some Windows guests they could ask for ri-registration. So I suggest you to set VM not to start automatically, upgrade the kernel, test if fixes your problems, and only then take care of VMs. Also, if you use virtio, after upgrade the proxmox kernel, upgrade to the newest available from Fedora project.
 
Hi, I use KVM and OpenVz, so Can I upgrade to 2.6.32? How?
What you mean with "if you have some Windows guests they could ask for ri-registration"?
I don't use Virtio because I use Win2008r2 64bit.

Thanks.
 
you are using an old 2.6.18 version, so I suggest you just upgrade to the latest and see if the issue is resolved.

if this does not help, move to the 2.6.32 kernel branch. as this got a newer KVM your windows guests will see a new virtual hardware and therefore the windows could request a new activation.
 
I've upgraded.

pve-manager/1.7/5470
red-earth:~# pveversion -v
pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.7-30
pve-kernel-2.6.32-4-pve: 2.6.32-30
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4

but I've error on one vm win2008:

kernel kvm: 3887: cpu0 unhandled wrmsr: 0x198 data 0

Why????
 
That error is (should be) of no harm. To me it happens everytime the VM is rebooted, but one Win2003R2 32 bit and one Win2003R2 64 bit work fine (I had other issues and had to upgrade to 2.6.35 proxmox kernel, but this is a different story...). The real question is: is your win2008 working fine or not?
Regarding Virtio, you can use virtio even with Win2008, why not? I do, using certified drivers provided by fedora (see wiki).
 
The Proxmox wiki page is: http://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows (I've used "search" box in the wiki page for word "fedora", first result).
Direct link to the latest .iso is http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/
As I wrote, 2.6.35 DOES NOT support OpenVZ, here for details: http://pve.proxmox.com/wiki/Proxmox_VE_Kernel
Maybe you should invest less in M$ certification and proprietary software skill, and more in Free Software in general and Proxmox in particular (correct your homepage, is Proxmox and not ProxMOX). :) Out of joke, read carefully the wiki, has plenty of useful info.
 
NetWork Hang Solved.
Firewall had some problems, but I've upgraded to 2.6.32 and ProxMox 1.7 with this results:

proxmox 1.5 kernel 2.6.18
Linux red-earth 2.6.18-2-pve #1 SMP Mon Feb 1 10:45:26 CET 2010 x86_64 GNU/Linux
red-earth:/home/biapar# pveperf
CPU BOGOMIPS: 19151.96
REGEX/SECOND: 414701
HD SIZE: 57.09 GB (/dev/pve/root)
BUFFERED READS: 90.58 MB/sec
AVERAGE SEEK TIME: 15.97 ms
FSYNCS/SECOND: 125.91
DNS EXT: 15.52 ms
DNS INT: 21.20 ms

Linux red-earth 2.6.32-4-pve #1 SMP Wed Dec 15 14:04:31 CET 2010 x86_64 GNU/Linux
red-earth:/backups# pveperf
CPU BOGOMIPS: 19151.92
REGEX/SECOND: 912100
HD SIZE: 57.09 GB (/dev/mapper/pve-root)
BUFFERED READS: 91.04 MB/sec
AVERAGE SEEK TIME: 9.07 ms
FSYNCS/SECOND: 311.97
DNS EXT: 13.39 ms
DNS INT: 20.95 ms

I'm going to correct word on my homepage. I use Free or Open Source sw. Why Do you say that? How Can I help Proxmox? Do you help it?
I read Proxmox wiki, but: Are that Virtio Drvs for 32bit only?
 
I joked about your M$ expertise because you were posting questions that, just reading the wiki and searching the forum, you should have not (but you, of course, are welcome to ask in any case). By contrast, When you go to your site, there are plenty of "proprietary programs" expertise listed (M$, .NET, vmware...). So my joke was to push you to invest in Free (as in Freedom) software competence as well :)
You can help Proxmox spelling correctly it's name on your site, donating money, helping on the forum, telling other about it, etc.. (usual way in the Free Software world).
Yes, I do help them in the above listed way, as far as I can.
No, virtio drivers are for 64bit too (just download the iso and look inside it, don't be lazy! :))
Out of jokes and back to technical subjects, what an improvement in performance you got from 2.6.18 to 2.6.32!
But I see a really slow I/O performances, do you have really cheap HD or a RAID controller without write-back enabled? A simple sata should have around 1.000 FSYNCS/SECOND and a raid5 more than 3.000.
 
Last edited:
mmenaz said:
I joked about your M$ expertise because you were posting questions that, just reading the wiki and searching the forum, you should have not (but you, of course, are welcome to ask in any case). By contrast, When you go to your site, there are plenty of "proprietary programs" expertise listed (M$, .NET, vmware...). So my joke was to push you to invest in Free (as in Freedom) software competence as well :)
You can help Proxmox spelling correctly it's name on your site, donating money, helping on the forum, telling other about it, etc.. (usual way in the Free Software world).
Yes, I do help them in the above listed way, as far as I can.
No, virtio drivers are for 64bit too (just download the iso and look inside it, don't be lazy! :))
Out of jokes and back to technical subjects, what an improvement in performance you got from 2.6.18 to 2.6.32!
But I see a really slow I/O performances, do you have really cheap HD or a RAID controller without write-back enabled? A simple sata should have around 1.000 FSYNCS/SECOND and a raid5 more than 3.000.
Click to expand...

My server is a R200 DELL with RAID 1 hardware...
Do you need other info?
 
I've just added some info in the wiki, "introduction" part. I'm not a guru, is what I've experienced directly and collected from the forum posts.
http://pve.proxmox.com/wiki/Raid_controller
You often can find some help on irc (freenode, #proxmox channel) if you need some more info, but the above should be enough, and I don't know your hardware or controller features to be more precise.
 
You must log in or register to reply here.
Top Bottom