Search results

Did you had a look at http://pve.proxmox.com/wiki/Nested_Virtualization ? I did the same as you but without disabling hardware virtualization, as it didn’t really makes sense why you want a slow machine^^, and used 4.0beta as host and a nested 4.0beta (even a nested in a nested, worked also...

http://forum.proxmox.com/archive/index.php/t-21647.html it was in fact already posted, and I could think that it's difficult do mention all changes, because there are really a lot of them you never really know which one affects someone bad, as there are almost infinity different...

Re: 4.0b1 | Start on boot not working when order is set Yes, on line 1152 and 1162 in your Nodes.pm file, should be in /usr/share/perl5/PVE/API2/Nodes.pm change # line 1152 $startup = PVE::JSONSchema::parse_startup($conf->{'pve.startup'}); # to $startup =...

Re: 4.0b1 | Start on boot not working when order is set I looked into the Code and it seems like the wrong method gets called (i think it's "only" a typo), I'll have a look at it. Please file a bug at https://bugzilla.proxmox.com/

Look at this thread from a few days, http://forum.proxmox.com/threads/22757-proxmox-4-0?p=114561#post114561 Your installation is in fact 64bit, but it seems lxc has some small bug so that uname doesn't recognized it correct. dpkg --print-architecture Should get you the expected correct result.

VZDump has a hook up script option. You can pass it a script and VZDump runs that on event like backup start, stop, abort and so on. I made a sample script which should fit your need: #!/bin/bash if [ "$1" == "backup-end" ]; then sleep 60; # here goes your time in seconds fi save that in...

Strange, copy this in your .vimrc file , if you haven't one in your home directory create one: set t_ku=^[OA set t_kd=^[OB set t_kr=^[OC set t_kl=^[OD Your basically mapping the key codes vim receives and map them to the right one, this worked for me.

Take a look at /var/log/auth.log maybe your PAM config is messed up. It also could be your /etc/shadow file, run pwconv to regenerate it (back up /etc/shadow first, shouldn't be risky but you never know). (Manpage) I suppose that your root filesystem is not mounted as read-only...^^ If...

First set it up like this: http://www.debiantutorials.com/how-to-add-a-new-hard-disk-or-partition-using-uuid-and-ext4-filesystem/ Then add it as directory where the path is your moint point.

With "With OpenVZ, it can be much more." he means that you can run much more than 5x 4GB VM's like in KVM not that OpenVZ needs more additional memory for teh host, thats the way I would understand it. But the point that it's much better if you don't overbook your host machine and leave a bit...

Damn, sorry about that, as it compiled without any problems here with a minimal setup i thought it wouldn't be a big deal to do it... Really glad you figured it out and all is working now!

As long as not all Servers run on full load you won't have problems here. Even when the worst case happens and every Container goes full rampage on the same time and uses every resource he has (or at least tries to use it), your server won't crash but everything will go slow as hell, or even be...

As a dirty temporary workaround, which isn't dirty because it's difficult (it's fairly easy) but because you install the program out of the scope from the package manager and so don't get automatic updates, build it yourself. I tried it successfully on a fresh installed Debian Wheezy (7.8)...

Haha, yeah i created a pull request on GitHub for the cookie function and saw your name... :D The problem is that the noVNC from PVE need to check if the request is a valid one and the necessary permissions are guaranteed. And it isn't directly accessible through the REST API, AFAIK. But I have...

You can access the noVNC console via it's address: https://your.proxmoxve.server:8006/?console=kvm&novnc=1&vmid=100&node=somenode change the vmid and the node GET parameters to your needs. But you need to respect the authentification security measures Proxmox VE has. I actually changed a...

How did you install the Proxmox VE and what are your system specifications? The response to those commands you entered: #/etc/pve/local/pve-ssl.key -bash:/etc/pve/local/pve-ssl.key: Permission denied #/etc/hostname -bash:/etc/hostname: Permission denied is normal, as the aren't executables...

Yes you can add a disk and make a new mount point for it. ( http://www.debiantutorials.com/how-to-add-a-new-hard-disk-or-partition-using-uuid-and-ext4-filesystem/ may help, this method preserves the mount point even after a reset/reboot) Then you can add it in Proxmox through Datacenter ->...

For that purpose use simply: setarch x86_64 ./scriptname as described above in my first post, and change ./scriptname to your desired script :) It changes the environment variables for the given command - in this case ./scriptname - so that uname returns 64bit. I hope that resolved the issue.

The packages you install will be 64bit ones, as the container-system is 64bit. running dpkg --print-architecture # returns, or should return: amd64 confirms that. If you need also 32bit support for some applications take a look at https://wiki.debian.org/Multiarch/HOWTO. Sorry, but what are...

I also installed a fresh Debian 8.0 lxc template (also compiled one with the dab, it is sure configured to be 64 bit). Your right uname -m tells that we're using a i686 system, but when you check some system binaries, i.e. with file /sbin/init # or file /usr/bin/file we get /sbin/init: ELF...