Search results

  1. K

    converting openvz to lxc

    LXC no need this options.
  2. K

    directory based storage in lxc

    I don't think so, with Image Based you will: Can not browse VPS to copy/rename/delete/move file Can not directly copy/rename/delete/move file between host and VPS If you need Image Base then you can use KVM instead -- that's why we use OpenVZ rather than KVM Can not copy/sync partially, this...
  3. K

    pty issue with ve 4 containers (converted from 3)

    Added to https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC#PTY_Allocation Thanks for sharing Ruben
  4. K

    [SOLVED] Failed to Resize LXC: CT File resized but CT OS reports old size

    # pct fsck 36165 fsck from util-linux 2.25.2 /mnt/sda1/images/36165/vm-36165-disk-1.raw: clean, 369528/6553600 files, 8523021/26214400 blocks root@ids-094110:~# pct start 36165 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details...
  5. K

    [SOLVED] Failed to Resize LXC: CT File resized but CT OS reports old size

    root@ids-094110:~# pct fsck 36165 cannot run fsck on active container root@ids-094110:~# pveversion -v proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve) pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4) pve-kernel-4.2.6-1-pve: 4.2.6-26 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 0.17.2-1...
  6. K

    [SOLVED] Failed to Resize LXC: CT File resized but CT OS reports old size

    1. CT is ON ---------------- Resizing CT from 100 GB to 200 GB, Proxmox UI failed message: Image resized. resize2fs 1.42.12 (29-Aug-2014) resize2fs: Permission denied to resize filesystem Filesystem at /dev/loop0 is mounted on /tmp; on-line resizing required old_desc_blocks = 7, new_desc_blocks...
  7. K

    Debian install guide - no webinterface loading

    Use the Bare-metal installation.see: https://pve.proxmox.com/wiki/Quick_installation
  8. K

    Force pvecm to use FQDN?

    More details please? What is the tool to generate the certificate (unfortunately pvecm updatecerts has no option to read certain file config).
  9. K

    Force pvecm to use FQDN?

    Still find how to check the method I think using existing certificate from other Server will cause security issue? Becase verify the certificate's name against host will failed?
  10. K

    Force pvecm to use FQDN?

    I think https://www.startssl.com/ is free for first year only? A self signed is enough for me because our Proxmox Server only access by our API.
  11. K

    Force pvecm to use FQDN?

    The "hostname -f" result is FQDN, but "pvecm updatecerts --force" still generate a short hostname certificate. I have checked /etc/hosts. Any idea to fix this issue?
  12. K

    Force pvecm to use FQDN?

    How to force "pvecm updatecerts" to use FQDN, I try "pvecm updatecerts --force" but still the Hostname used. Should I manually use openssl? Note: this case happen after I change Hostname then run pvecm updatecerts --force, the result is just the Hostname not FQDN.
  13. K

    [SOLVED] Can not access using Proxmox PHP API

    Right, on installation there are options to choose: Debian or Proxmox. Choose Proxmox instead.
  14. K

    [SOLVED] Can not access using Proxmox PHP API

    I do reinstall, and just aware that Hetzner also provided Proxmox beside Debian. Use built in Proxmox image then Proxmox API PHP works fine.
  15. K

    [SOLVED] Can not access using Proxmox PHP API

    Right, above code running well on other Data Centers, I have use it for hundreds servers. Unfortunately, Hetzner does not help, I have open Ticket to Hezner but they told me to ask to forum.
  16. K

    API commands reference

    http://pve.proxmox.com/pve2-api-doc/ Look at: nodes/qemu/{vmid}/config -- ide[n]
  17. K

    [SOLVED] Can not access using Proxmox PHP API

    This script below works fine on several server but only server from Hetzner doesn't. <?php require_once("pve2_api.class.php"); $pve2 = new PVE2_API("my-server-ip", "root", "pam", "my-password"); if ($pve2->login()) { foreach ($pve2->get_node_list() as $node_name) {...
  18. K

    kernel: ip_set_hash_net: disagrees about version of symbol module_layout

    Dear, My kern.log file very2 large, I found 99% entry was: kernel: ip_set_hash_net: disagrees about version of symbol module_layout Any idea to fix this? # pveversion -v proxmox-ve-2.6.32: 3.4-166 (running kernel: 2.6.32-37-pve) pve-manager: 3.4-11 (running version: 3.4-11/6502936f)...
  19. K

    Assign public IPs automatically to VMs

    I manage hundred IPs so it is not possible to do it manually, use DCHP instead. Install DHCP Server is very simple: #apt-get install isc-dhcp-server edit /etc/dhcp/dhcpd.conf, to specify your available IPs Inside VM set to DHCP. I install the DHCP on Proxmox node. Read this tutorial for...