Connection to Proxmox slow and often lost

T

tabbi

New Member
Jul 30, 2011
25
0
1
Hi,

I´m quite new to Proxmox. I´ve installed it on a new PC:
Mainboard: ASRock H61M/U3S3
CPU: Intel Core i5 2400 4x3,1GHz
RAM: 4GB
HDD: Seagate ST1000DL002 1TB

I´ve installed 9 virtual machines on the Proxmox host (4 KVM, 5 OpenVZ with Debian 6.0):
proxmoxvms.jpg

The status of Proxmox seems to be okay:
proxmoxstatus.jpg

Now I have the problem that sometimes connecting Proxmox itself or any of the virtual machines is very slow or I don´t get a connection at all. This happens with HTTP, SSH, ping etc.

The Proxmox server is connected to a router and I´m connected to this router via WLAN.

Do you have an idea what the problem could be? It´s very annoying to wait for every action more than 10 seconds.
 
I try to check this next time. The problem is that I can´t check it through SSH (because then I´ve got no/very slow connection) and I usually don´t have any monitor and keyboard attached to the server.
 
what kind of network adapter you have on the host? (lspci -v)
 
I´ve put an old Realtek PCI card into the server as the onboard NIC didn´t work without additional drivers.

This is the NIC I use:
Code: 
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139                                                                             C+ (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
        Flags: bus master, medium devsel, latency 32, IRQ 17
        I/O ports at e000 [size=256]
        Memory at fbb00000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2
        Kernel driver in use: 8139too
        Kernel modules: 8139too, 8139cp

And this is the unused onboard NIC:
Code: 
04:00.0 Ethernet controller: Atheros Communications Device 1083 (rev c0)
        Subsystem: ASRock Incorporation Device 1083
        Flags: bus master, fast devsel, latency 0, IRQ 3
        Memory at fba00000 (64-bit, non-prefetchable) [size=256K]
        I/O ports at d000 [size=128]
        Capabilities: [40] Power Management version 3
        Capabilities: [48] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0                                                                              Enable-
        Capabilities: [58] Express Endpoint, MSI 00
        Capabilities: [6c] Vital Product Data <?>
        Capabilities: [100] Advanced Error Reporting <?>
        Capabilities: [180] Device Serial Number ff-22-25-00-7a-2a-b5-ff

Would buying a new NIC help?
 
tabbi said:
...
Would buying a new NIC help?
Click to expand...

if the nic is the issue, yes. if not, then it will not help. I know, not that useful info ...
 
udo said:
what shows "top" on the pve-host during this happens?
Click to expand...
Here´s the output of wait while having a slow connection (shot through SSH, not directly on the host):

Code: 
proxmox:~# top
top - 01:22:36 up 5 days,  5:15,  1 user,  load average: 0.00, 0.01, 0.00
Tasks: 197 total,   1 running, 196 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.4%us,  0.2%sy,  0.0%ni, 99.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   7885952k total,  7829612k used,    56340k free,   111792k buffers
Swap:  7340024k total,    55148k used,  7284876k free,  3799316k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
12313 root      20   0  860m 697m 1028 S    6  9.1 388:12.66 kvm
10202 root      20   0  627m 511m 1028 S    4  6.6 285:19.85 kvm
 1332 root      20   0 3262m 1.9g 1832 S    4 24.9   5:59.23 kvm
  691 sshd      20   0  134m  20m 4700 S    0  0.3   0:32.15 mysqld
13061 root      20   0  100m  21m 3876 S    0  0.3   1:00.32 python
    1 root      20   0 10316  652  584 S    0  0.0   0:03.01 init
    2 root      20   0     0    0    0 S    0  0.0   0:00.00 kthreadd
    3 root      RT   0     0    0    0 S    0  0.0   0:00.02 migration/0
    4 root      20   0     0    0    0 S    0  0.0   0:11.80 ksoftirqd/0
    5 root      RT   0     0    0    0 S    0  0.0   0:00.00 watchdog/0
    6 root      RT   0     0    0    0 S    0  0.0   0:00.02 migration/1
    7 root      20   0     0    0    0 S    0  0.0   0:01.16 ksoftirqd/1
    8 root      RT   0     0    0    0 S    0  0.0   0:00.00 watchdog/1
    9 root      RT   0     0    0    0 S    0  0.0   0:00.04 migration/2
   10 root      20   0     0    0    0 S    0  0.0   0:02.27 ksoftirqd/2
   11 root      RT   0     0    0    0 S    0  0.0   0:00.00 watchdog/2
   12 root      RT   0     0    0    0 S    0  0.0   0:00.02 migration/3
   13 root      20   0     0    0    0 S    0  0.0   0:01.02 ksoftirqd/3
   14 root      RT   0     0    0    0 S    0  0.0   0:00.00 watchdog/3
   15 root      20   0     0    0    0 S    0  0.0   0:03.44 events/0
   16 root      20   0     0    0    0 S    0  0.0   0:01.61 events/1
   17 root      20   0     0    0    0 S    0  0.0   0:01.75 events/2
   18 root      20   0     0    0    0 S    0  0.0   0:01.43 events/3
   19 root      20   0     0    0    0 S    0  0.0   0:00.00 khelper
   20 root      20   0     0    0    0 S    0  0.0   0:00.09 netns
   21 root      20   0     0    0    0 S    0  0.0   0:00.00 async/mgr
   22 root      20   0     0    0    0 S    0  0.0   0:00.00 pm
   23 root      20   0     0    0    0 S    0  0.0   0:00.38 sync_supers
   24 root      20   0     0    0    0 S    0  0.0   0:00.38 bdi-default
   25 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/0
   26 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/1
   27 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/2
   28 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/3
   29 root      20   0     0    0    0 S    0  0.0   0:06.11 kblockd/0
   30 root      20   0     0    0    0 S    0  0.0   0:00.52 kblockd/1
   31 root      20   0     0    0    0 S    0  0.0   0:00.65 kblockd/2
   32 root      20   0     0    0    0 S    0  0.0   0:00.34 kblockd/3
   33 root      20   0     0    0    0 S    0  0.0   0:00.00 kacpid
   34 root      20   0     0    0    0 S    0  0.0   0:00.00 kacpi_notify
   35 root      20   0     0    0    0 S    0  0.0   0:00.00 kacpi_hotplug
   36 root      20   0     0    0    0 S    0  0.0   0:00.00 kseriod
   41 root      20   0     0    0    0 S    0  0.0   0:00.00 kondemand/0
   42 root      20   0     0    0    0 S    0  0.0   0:00.00 kondemand/1
   43 root      20   0     0    0    0 S    0  0.0   0:00.00 kondemand/2
   44 root      20   0     0    0    0 S    0  0.0   0:00.00 kondemand/3
   45 root      20   0     0    0    0 S    0  0.0   0:00.00 ubstatd
   46 root      20   0     0    0    0 S    0  0.0   0:00.12 khungtaskd
   47 root      20   0     0    0    0 S    0  0.0   2:53.50 kswapd0
   48 root      20   0     0    0    0 S    0  0.0   0:00.00 aio/0
   49 root      20   0     0    0    0 S    0  0.0   0:00.00 aio/1
   50 root      20   0     0    0    0 S    0  0.0   0:00.00 aio/2
   51 root      20   0     0    0    0 S    0  0.0   0:00.00 aio/3
   52 root      20   0     0    0    0 S    0  0.0   0:00.00 crypto/0
 
tabbi said:
Here´s the output of wait while having a slow connection (shot through SSH, not directly on the host):

Code: 
proxmox:~# top
top - 01:22:36 up 5 days,  5:15,  1 user,  load average: 0.00, 0.01, 0.00
Tasks: 197 total,   1 running, 196 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.4%us,  0.2%sy,  0.0%ni, 99.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   7885952k total,  7829612k used,    56340k free,   111792k buffers
Swap:  7340024k total,    55148k used,  7284876k free,  3799316k cached

...
Click to expand...
Hi,
looks normal. So the issue seem not to be io-related.
Any hints in the logs?

Udo
 
Yesterday I put a new network interface card (1Gbit) into the server and now it really runs. Copying file to or from the server was really slow before (around 50kByte/s), now it is much faster. And I didn´t have any problems like the above since then :-)
 
You must log in or register to reply here.
Top Bottom