http://www.jamescoyle.net/tag/opennode has had tremendous articles on opennode, and the opennode manager GUI;wardmundy is it worth comparing this to opennode?
Ok, I know proxmox 4.0 works for you, and it is fast... I wished we could have installed Proxmox then 3.4 on Wable (OpenVZ) , but (Wable offers no iso support), and though there are work arounds, other more important issues came up.I've had a chance to play with OpenNode now as well as the previous release of Proxmox. There's really not much of a comparison. OpenNode only supports OpenVZ containers so you can't build virtual machines from ISO images. Proxmox 4 is much improved and much, much more secure than prior versions so I think we'll focus on that one for the moment. Did we mention it's fast.
That is only fair, and if you have business to sustain the model, probably worth it.; I did note earlier, their email server, is now only a subscription based model, after 30 days. You must pay orThey're trying to eat. No reason to sign up if you don't want to.
cd / wget 'http://downloads.sourceforge.net/project/pbxinaflash/IncrediblePBX13-12 with Incredible PBX GUI/IncrediblePBX13-KVM.tar.gz' tar zxvf IncrediblePBX13-KVM.tar.gz rm IncrediblePBX13-KVM.tar.gz
Formatting '/var/lib/vz/backup/images/101/vm-101-disk-1.qcow2', fmt=qcow2 size=10737418240 encryption=off cluster_size=65536 preallocation='metadata' lazy_refcounts=off refcount_bits=16
new volume ID is 'backup:101/vm-101-disk-1.qcow2'
map 'drive-ide0' to '/var/lib/vz/backup/images/101/vm-101-disk-1.qcow2' (write zeros = 0)
progress 1% (read 107413504 bytes, duration 0 sec)
progress 2% (read 214761472 bytes, duration 0 sec)
progress 3% (read 322174976 bytes, duration 0 sec)
progress 4% (read 429522944 bytes, duration 1 sec)
progress 5% (read 536870912 bytes, duration 1 sec)
progress 6% (read 644284416 bytes, duration 1 sec)
progress 95% (read 10200547328 bytes, duration 20 sec)
progress 96% (read 10307960832 bytes, duration 20 sec)
progress 97% (read 10415308800 bytes, duration 20 sec)
progress 98% (read 10522722304 bytes, duration 20 sec)
progress 99% (read 10630070272 bytes, duration 20 sec)
progress 100% (read 10737418240 bytes, duration 20 sec)
total bytes read 10737418240, sparse bytes 5929807872 (55.2%)
I don't remember all the specifics, but wasn't there a networking/VPN issue with Proxmox 3.x and that was the reason that we abandoned Proxmox a while back?
Has that issue been resolved in this latest version (maybe moving from OpenVZ to LXC fixed that issue)?
1) Press F2 on boot. In VisualBIOS - check that "Internal UEFI Shell" is checked/enabled and that "UEFI: Built-in EFI Shell" is an option in the list of UEFI bootable devices. Turn OFF legacy boot option. In Power settings, set it to recover from power failure. Press F10 to SAVE your settings. 2) Boot the NUC and allow it to drop into the EFI shell prompt. ...assuming fs0: is the FAT32 EFI partition that Proxmox made... 3) type => fs0: 4) type => echo "fs0:\EFI\proxmox\grubx64.efi" > fs0:\startup.nsh 5) type => startup.nsh and you should boot into Proxmox
[email protected]:~# parted /dev/sda print Model: ATA Crucial_CT250MX2 (scsi) Disk /dev/sda: 250GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 17.4kB 1049kB 1031kB bios_grub 2 1049kB 134MB 133MB fat32 boot, esp 3 134MB 250GB 250GB lvm