Search results

  1. M

    Can Proxmox GUI show memory speed?

    I meant more the overall speed of writing and reading to RAM of all modules online
  2. M

    Can Proxmox GUI show memory speed?

    It would be good to show it in GUI? And are you sure that "dmidecode --type 17" show actual speed? Yes, I'm not ask to actual.
  3. M

    Can Proxmox GUI show memory speed?

    Can Proxmox GUI show memory speed? Min. count memory models?
  4. M

    Cloned VM affect CPU load on others VMs

    I cloned VM to another cluster and just now i found out, that it's CPU load affect CPU load on another VMs (same hypervisor server type Dell R640) Have another mind, what can be wrong?
  5. M

    Different speed write/read throught iSCSI

    root@vig-node1:~# dd if=/dev/urandom of=/mnt/test3 ^C7335408+0 records in 7335407+0 records out 3755728384 bytes (3.8 GB, 3.5 GiB) copied, 29.2377 s, 128 MB/s root@vig-node1:/mnt# dd if=/mnt/test3 of=/mnt/test/test4 oflag=direct status=progress 57174528 bytes (57 MB, 55 MiB) copied, 55 s, 1.0...
  6. M

    Different speed write/read throught iSCSI

    Hello, I have the Proxmox 6 connected throught the network (1 switch) to iSCI on Dell Storage. All looks right, but writing is 100x speeder, than reading. Has anyone meet with it yet? THX
  7. M

    Container with CentOS 8.3 not start network device

    Exists some proxmox variable where is timeout for container creations?
  8. M

    Container with CentOS 8.3 not start network device

    Unfortunatelly with this settings we cannot run dockers on this containers. When we tried create docker, response is "Error response from daemon: using mount program fuse-overlayfs: fuse: device not found, try 'modprobe fuse' first"
  9. M

    Container with CentOS 8.3 not start network device

    THX, it helped. Can you explain what this three lines doing or why this helped us?
  10. M

    Container with CentOS 8.3 not start network device

    We tryed to change network settings (IPv6: Static) in Proxmox GUI and network device after start still not starting. cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.102.51 NETMASK=255.255.255.0 GATEWAY=192.168.102.1
  11. M

    Container with CentOS 8.3 not start network device

    THX, but if I anything changed in /etc/sysconfig/network-scripts/ifcfg-eth0, after restart all my changes are disappearsed.
  12. M

    Container with CentOS 8.3 not start network device

    root@node12:~# pct config 151 arch: amd64 cores: 2 cpulimit: 2 cpuunits: 1000 hostname: mas1.sandbox1.xxx... memory: 4096 nameserver: 192.168.102.10 192.168.102.68 net0: name=eth0,bridge=vmbr102,firewall=1,gw=192.168.102.1,hwaddr=6A:0B:2B:BF:35:51,ip=192.168.102.51/24,ip6=dhcp,type=veth onboot...
  13. M

    Container with CentOS 8.3 not start network device

    Hello, I have container with CentOS 8.3 and network device eth0 not start after boot, but command ifup eth0 works. cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.102.51 NETMASK=255.255.255.0 GATEWAY=192.168.102.1 IPV6INIT=yes DHCPV6C=yes...
  14. M

    Join node to the cluster failed.

    I have bonded interface: auto bond0 iface bond0 inet manual bond-slaves eno1 eno2 My colleague tell me, that is not possible to join together cluster with different version proxmoxs, so I reinstall/downgrade node2 to version 6.1-7 and tried to connect to cluster created from proxmox 6.1-3...
  15. M

    Join node to the cluster failed.

    Node with cluster: root@node1:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope...
  16. M

    Join node to the cluster failed.

    Node with cluster: root@node1:~# cat /etc/hosts 127.0.0.1 localhost.localdomain localhost 192.168.83.101 node1.....local node1 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes...
  17. M

    Join node to the cluster failed.

    Hello, I have one node, where I create cluster and want add new node to this cluster, but adding failed. root@node2:~# pvecm add 192.168.83.101 Please enter superuser (root) password for '192.168.83.101': ******** detected the following error(s): * local node address: cannot use IP '0.0.0.192'...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!