Hi all, I have installed OpenVZ on Debian 8 using the following guide: https :// wiki . openvz . org /Installation_on_Debian_8 (spaced out because otherwise the forum wouldn't let me post ) Everything went smoothly until I had to reboot into the OpenVZ kernel. When I boot into the OpenVZ kernel the process gets stuck on: Code: Starting OpenVZ: ..done Applying OOM adjustments: ..done Bringing up interface venet0: ..done After this the process does not continue to boot or do anything else. Full startup log: Expand: log Loading Linux 2.6.32-openvz-042stab134.8-amd64 ... Loading initial ramdisk ... ▒Loading, please wait... [ 2.603407] piix4_smbus 0000:00:14.0: Host SMBus controller not enabled! /dev/mmcblk0p1: recovering journal /dev/mmcblk0p1: clean, 145436/3743744 files, 1505738/14947840 blocks INIT: version 2.88 booting [info] Using makefile-style concurrent boot in runlevel S. [ ok ] Starting the hotplug events dispatcher: udevd. [ ok ] Synthesizing the initial hotplug events...done. [ ok ] Waiting for /dev to be fully populated...done. [ ok ] Activating swap...done. [....] Checking root file system...fsck from util-linux 2.25.2 /dev/mmcblk0p1: clean, 145436/3743744 files, 1505738/14947840 blocks done. [ ok ] Activating lvm and md swap...done. [....] Checking file systems...fsck from util-linux 2.25.2 done. [ ok ] Cleaning up temporary files... /tmp. [ ok ] Mounting local filesystems...done. [ ok ] Activating swapfile swap...done. [info] Loading kernel module lp. [info] Loading kernel module ppdev. [info] Loading kernel module parport_pc. [info] Loading kernel module fuse. [ ok ] Cleaning up temporary files.... [ ok ] Setting kernel variables ...done. [ ok ] Configuring network interfaces...done. [ ok ] Starting rpcbind daemon.... [ ok ] Starting NFS common utilities: statd idmapd. [ ok ] Cleaning up temporary files.... [ ok ] Setting up ALSA...done. [ ok ] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix. INIT: Entering runlevel: 2 [info] Using makefile-style concurrent boot in runlevel 2. [ ok ] Starting UPnP devices daemon: MiniSSDPd. Checking vzevent kernel module .....done Starting vzeventd: [ ok ] Starting enhanced syslogd: rsyslogd. [info] speech-dispatcher disabled; edit /etc/default/speech-dispatcher. [info] GNUstep distributed object mapper disabled, see /etc/default/gdomap. [ ok ] Starting ACPI services.... [ ok ] Starting deferred execution scheduler: atd. [ ok ] Starting anac(h)ronistic cron: anacron. [ ok ] Starting CUPS Bonjour daemon: cups-browsed. [ ok ] Starting periodic command scheduler: cron. [ ok ] Starting system message bus: dbus. [ ok ] Starting bluetooth: bluetoothd. [ ok ] Starting OpenBSD Secure Shell server: sshd. [ ok ] saned disabled; edit /etc/default/saned. [ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. [ ok ] Starting Common Unix Printing System: cupsd. [ ok ] Starting MTA: exim4. Starting OpenVZ: ..done Applying OOM adjustments: ..done Bringing up interface venet0: ..done When I boot the OpenVZ kernel into maintenance mode I am able to get it working by manually starting up all required processes. The commands I use to get OpenVZ to work in maintenance mode: Code: dhclient eth0 service ssh start /etc/init.d/vz restart vzctl start 101 While this does achieve my goal of being able to create VM's and such, it isn't exactly practical. Nor is the booting process automatic which is a must for my project. I have tried some things like setting my /etc/network/interfaces static to both eth0 and venet0. This doesn't make a difference other than not having to use "dhclient eth0" when the eth0 is set static. I'm almost certain that venet0 is the issue as the interface does not exist at all on my host machine, though I am very new to OpenVZ. If any more settings/info is required to resolve this issue please let me know. I would really like to get it working so I can continue other parts of the project.
The startup log looks like it booted just fine. What did not work? If you have problems with this openvz, try Proxmox VE. https://www.proxmox.com/en/proxmox-ve
After "Bringing up interface venet0: ..done" nothing else happens, It doesn't lead me to the login screen nor does the server appear in my network. Because of this I assumed it either freezes or fails to start after the venet0 interfaces comes up.
OpenVZ kernel is really old, it might be that it does not support your network card. I won't use openvz anymore, the project is daed and tehy stopped development of their kernel, and openvz 7 is not the original openvz anymore, its basically a wrapper around KVM, so one could use KVM right away then.
I'm open to other suggestions for Virtualization software too. For context, I'm trying to install OpenVZ on a PCEngines Apu2d4 board. The minimal requirement is that it needs to be able to run two separate linux/debian systems and isn't bound to any licenses, so preferably open source. A nice addition would be the ability to run a linux and windows vm side by side however I expect to need better hardware for that. A easy-to-install and easy-to-use environment would be great too . Though if possible I would still like to see how far OpenVZ can take me despite it being outdated.
Check if that PCEngines Apu2d4 supports hardware virtualization, i.e. has vmx or svm flag: Code: egrep --color "(vmx|svm)" /proc/cpuinfo If yes, Proxmox should work, although that does not seem to be the fastest processor and system in the world. https://www.proxmox.com/en/proxmox-ve/requirements If the processor has the flag, but Proxmox says hw virtualization is not available, check BIOS and enable virtualization support. It may be in a strange place and named confusingly.
Thank you for the suggestion, upon entering "egrep --color "(vmx|svm)" /proc/cpuinfo" I receive a couple hits for svm and none for vmx. I've just now successfully gone through the Proxmox installation and I've gotten to the point where I'm able to reach the webpage and start testing. However I got a notification that I do not have a valid "license", I see Proxmox has a couple different subscriptions. Are these required for operation? As mentioned I'd prefer to stay away from licenses and subscriptions..
As far as I know, you don't need a subscription or license for proxmox. It might tease you to buy one though
Subscription is not needed. But set up the no-subscription repository to get updates with apt-get dist-upgrade: https://pve.proxmox.com/wiki/Package_Repositories Useful hint: With Proxmox always do the updates with Code: apt-get dist-upgrade . The plain upgrade may leave the system in only partially working state, because it does not install extra packages which are often needed when the pve packages are updated because Proxmox makes a new package with a new name instead of just updating the old package.
Thank you for the suggestion and kind help, all of you ! I've installed Proxmox and it works like a charm, incredible how much easier setup and configuration has been compared to OpenVZ. I won't be needing help with OpenVZ anymore.
