Search results

I have made an Alpine Linux OpenVZ Template that still needs networking to be manually started after bootup. http://pve.proxmox.com/wiki/Alpine_Linux_Minimal http://pve.proxmox.com/wiki/OpenVZ_Console#Alpine_Linux Feedback will be useful.

Thanks Tom. The following do not appear to have the said update but have the DIRTY COW update: http://download.proxmox.com/debian/dists/wheezy/pve-no-subscription/binary-amd64/pve-kernel-2.6.32-48-pve_2.6.32-184.changelog...

CVE-2016-8655 Race Condition Error Exploit https://security-tracker.debian.org/tracker/CVE-2016-8655 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=84ac7260236a49c79eede91617700174c2c19b0c Has this been patched for PVE 3.x / 4.x ?

The first 4 lines of your pveversion -v are: proxmox-ve-2.6.32: 3.4-150 (running kernel: 2.6.32-37-pve) pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee) pve-kernel-2.6.32-32-pve: 2.6.32-136 pve-kernel-2.6.32-37-pve: 2.6.32-150 After upgrade and reboot, you are now running the kernel...

You might want to remove unused kernel first: pve-kernel-2.6.32-32-pve: 2.6.32-136 and reboot before upgrading.

The DAB Forum topic was really convenient. Mailing lists will mean more mail.... with the balance of convenience of not having to visit the forum contra-ed by the forum's ability to automatically keep it's threads in sequence topic wise. A survey of the DAB users should show us the way forward.

Attempted to install dvipng package with all dependencies in DAB in a single line and it failed with needing texlive-base-bin which is a virtual package provided by texlive-binaries package. The following mitigated it: dab install imagemagick htmldoc graphviz texlive-fonts-recommended...

All posts relating to DAB Builds get drowned in the general Installation topic. Please restore the DAB Templates Topic to mitigate this. What was the logic in disabling the DAB Build Topic in the first place?

The chroot method below works on DAB for OpenVZ in PVE 3.4 for Debian Jessie (8) 64 bit build: dab install php5-intl php5-imagick install -m 0755 aptnorec.sh ${BASEDIR}/aptnorec.sh echo "nameserver 8.8.8.8" > ${BASEDIR}/etc/resolv.conf /usr/sbin/chroot ${BASEDIR} /aptnorec.sh...

DAB installs packages by using debconf get selections and then dpkg -i .... This installs various large sized doc debs. To make a small DAB based template we need the equivalent of aptitude --without-recommends .... or apt-get --no-install-recommends install .... for certain deb packages that...

Finally got it! Place a file called dopear.sh with the following contents in the DAB build folder: #! /bin/bash pear upgrade pear install mail Net_SMTP Auth_SASL In the Makefile, insert the following (includes the php-pear install request as well): dab install libjs-jquery php-apc...

Please provide DAB commands for chroot and whether it will work in the old PVE 3.x DAB for OpenVZ template generation especially when only the bootstrap files are available at that time during the build. At that point in the build process if we error out and enter the build container using...

In the DAB files folder, the logfile shows only localhost loopback: ... ... Creating config file /etc/php5/mods-available/curl.ini with new version php5_invoke: Enable module curl for apache2 SAPI php5_invoke: Enable module curl for cli SAPI Setting up php5-apcu (4.0.7-1) ... php5_invoke: Enable...

Even the above still fails with: install: php-pear echo "nameserver 8.8.8.8" > /var/lib/vz/private/90000/etc/resolv.conf dab exec pear upgrade Error getting channel info from pear.php.net: Connection to `pear.php.net:80' failed: php_network_getaddresses: getaddrinfo failed: Name or service not...

While creating a Debian 8 (Jessie) template using DAB, apt-get install php-pear is successful, but thereafter pear upgrade fails since /etc/resolv.conf has not yet been created with a valid nameserver as that happens only on VM creation. A possible workaround is: apt-get install php-pear...

@dcsapak: Thanks.

I meant KVM. The post stands corrected.

I am aware of using the defaults. The point here is if during KVM creation, backup=no was chosen, where in the GUI do we revert it later. For now we merely edit the appropriate /etc/pve/nodes/host01/qemu-server/###.conf file.

Created a KVM under qemu64 with backup=no parameter in Proxmox VE 3.4. The conf file is at /etc/pve/nodes/host01/qemu-server/100.conf and it contains: ... ... ide0: local:100/vm-100-disk-1.qcow2,format=qcow2,backup=no,size=10G ... ... Where in the Proxmox VE GUI do we set the backup=yes...

There are many use cases where an old OS is desirable. Here are a few. 1. In a protected LAN environment 2. Legacy devices with custom drivers where the developers are no longer available. 3. Learning curve that each new OS brings with it - not to mention the variations that existing binaries...