Search results

  1. L

    how to fix mem/swap usage in the lxc ?

    # cat /etc/pve/lxc/103.conf arch: amd64 cpulimit: 4 cpuunits: 202400 hostname: test memory: 16384 net0: bridge=vmbr0,gw=172.16.1.254,hwaddr=36:64:30:33:31:38,ip=172.16.1.1/24,name=eth0,tag=2,type=veth onboot: 1 ostype: fedora rootfs: local:103/vm-103-disk-1.raw,size=32G swap: 16384 # pveversion...
  2. L

    how to fix mem/swap usage in the lxc ?

    hi, all In the fedora 22(lxc) have this issue. In the centos 6(lxc) have no this issue. # free -m total used free shared buff/cache available Mem: 16384 18014398509481164 16381 80 822 16381 Swap: 8796093005823 0 8796093005823 # lxc-info -n 103 Name: 103 State: RUNNING PID...
  3. L

    no MII interfaces found in PVE4

    thanks again, it's solved! but, there is use the OVS for network setup, so must be restart networking first, and restart the openvswitch.
  4. L

    TASK ERROR: migration problems

    hi offline can migration. online can't! /dev/rbd21 Failed to create message: Input/output error TASK ERROR: start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 106 -p 'KillMode=none' -p 'CPUShares=10000' /usr/bin/kvm -id 106 -chardev...
  5. L

    no MII interfaces found in PVE4

    thanks you reply! maybe you don't understand this problem. Sorry, my English is so poor! I mean: the normal device can display infomation with mii-tool command,like: # mii-tool eth0: negotiated 1000baseT-FD flow-control, link ok eth1: negotiated 1000baseT-FD flow-control, link ok eth2...
  6. L

    Note: NETDEV WATCHDOG: transmit queue timed out

    hi maybe the PVE can add the patch for fixed this issue. http://kb.odin.com/en/121971 https://bugzilla.mozilla.org/show_bug.cgi?id=778068 Jan 7 18:44:34 tnd01-0012 kernel: [181167.572655] ------------[ cut here ]------------ Jan 7 18:44:34 tnd01-0012 kernel: [181167.572673] NETDEV WATCHDOG...
  7. L

    no MII interfaces found in PVE4

    but how to activated the network card? Why after to reinstall the system and it's fixed?
  8. L

    no MII interfaces found in PVE4

    hi, here have a lot the Dell R510 devices have this issue. well, if have this issue, the network adapter can't work!! if to reinstall the PVE from ISO, it's will fixed! but... I don't want to reinstall it everytimes. there are other ways to fix that? thanks!
  9. L

    Proxmox 4 HA resource type IP address

    if can, it's will be a significant feature! a lot of people are needed!
  10. L

    Proxmox 4.1 SSD issue

    please use the livecd or other tools, delete the partition information on the SSD and try again!
  11. L

    Proxmox v4 Containers Questions

    hi, this feature is planned? have some good news? thks!
  12. L

    How to scroll up in console?

    thanks, but not very effective in console.
  13. L

    How to scroll up in console?

    what shortcuts on macbook pro? :confused:
  14. L

    WARNING: No balloon device has been activated

    thanks, this feature only for Windows OS? maybe most of the modern linux os should have ballon driver inside.
  15. L

    WARNING: No balloon device has been activated

    hi,all from pve-manager: 3.3-7, get a lot of this warning in /var/log/syslog What is the problem? ...... Dec 15 13:31:52 t1 pvedaemon[22934]: WARNING: No balloon device has been activated Dec 15 13:31:53 t1 pvedaemon[22934]: WARNING: No balloon device has been activated Dec 15 13:31:53 t1...
  16. L

    [SOLVED] OVS virtual interface with vlantag enable firewall can't work!

    Re: OVS virtual interface with valntag enable firewall can't work! all it's work! thank you a lot again! :D
  17. L

    [SOLVED] OVS virtual interface with vlantag enable firewall can't work!

    Re: OVS virtual interface with valntag enable firewall can't work! yes, thanks you a lot work. thanks again! :p
  18. L

    [SOLVED] OVS virtual interface with vlantag enable firewall can't work!

    Re: OVS virtual interface with valntag enable firewall can't work! yes, both have. yes,remove it, and restart pve-firewall , it's work. but, if like so, there is no rule can protect the host. maybe it's a bug.
  19. L

    [SOLVED] OVS virtual interface with vlantag enable firewall can't work!

    Re: OVS virtual interface with valntag enable firewall can't work! create PVEFW-0-management hash:net family inet hashsize 64 maxelem 64 add PVEFW-0-management 127.0.0.0/8 create PVEFW-0-venet0 hash:net family inet hashsize 64 maxelem 64 create PVEFW-0-whitelist hash:net family inet hashsize...
  20. L

    [SOLVED] OVS virtual interface with vlantag enable firewall can't work!

    Re: OVS virtual interface with valntag enable firewall can't work! yes, I have use it! thanks you a lot again! but another issue:see #6 enable host firewall,can't apply rules # pve-firewall status Status: enabled/running (pending changes) always pending changes of status ...... what...