First remove the existing LVM-Thin:
lvremove pve/data
Then create an normal lvm on existing group. For example:
lvcreate -L 755.96G -n data pve
Format it:
mkfs.ext4 /dev/pve/data
Mount it in the fstab. The mount target must be empty, so delete everything in there.
/dev/pve/data /var/lib/vz ext4 defaults 0 2 rm -rf /var/lib/vz/* && mount -a
After all create you normal directory storage.
The installation of a supported Proxmox VE server should be done via Bare-metal_ISO_Installer. In some case it makes sense to install Proxmox VE on top of a running Debian Stretch 64-bit, especially if you want a custom partition layout. For this HowTO the following Debian Stretch ISO was used:
Install a standard Debian Stretch (amd64)
Install a standard Debian Stretch, for details see Debian, and select a fixed IP. It is recommended to only install the “standard” package selection and nothing else, as Proxmox VE brings its own packages for qemu, lxc.
Add an /etc/hosts entry for your IP address
Please make sure that your hostname is resolvable via /etc/hosts, i.e you need an entry in /etc/hosts which assigns an IPv4 address to that hostname.
Note: Make sure that no IPv6 address for your hostname is specified in `/etc/hosts`
For instance if your IP address is 192.168.15.77, and your hostname prox4m1, then your /etc/hosts file should look like: Continue reading “Install Proxmox VE on Debian 9 – Stretch” »
Command Line Tool
Most users will simply use the GUI to manage users. But there is also a full featured command line tool called pveum (short for “Proxmox VE User Manager”). Please note that all Proxmox VE command line tools are wrappers around the API, so you can also access those function through the REST API.
Here are some simple usage examples. To show help type:
pveum
or (to show detailed help about a specific command)
pveum help useradd
Create a new user:
pveum useradd testuser@pve -comment "Just a test"
Set or Change the password (not all realms support that):
pveum passwd testuser@pve
Disable a user:
pveum usermod testuser@pve -enable 0
Create a new group: Continue reading “Proxmox User Management- Proxmox VE authentication server” »
Let’s start uploading the exported ova file to the proxmox server. Extract the OVA file:
tar -xvf *.ova
This should output a couple of files from the OVA container, it should include an OVF file, which is the VM Defenition file, and a VMDK file, which is the actual hard disk image. Again, this may take a while.
Convert the vmdk to a Proxmox compatible qcow2 file:
qemu-img convert -f vmdk myvirtual-disk1.vmdk -O qcow2 qcowdisk.qcow2
We now need to get the image into a VM with some hardware so that we can begin to use it. This is where things get tricky – the OVF file is not compatible with Proxmox and needs to be manually understood. The principle here is we are going to use the Proxmox web GUI to create a VM and replace the empty disk image which is created with our recently converted qcow2 image.
You can use vi to open the OVF file and understand some of the basic settings which are required for the VM. Open the OVF file and look for the following XML tags:
Continue reading “Convert .ova and import it on Proxmox KVM virtualization” »
I hope you already know how to allow NFS from proxmox host server. if not, you may read my earlier post:
The fix works for Proxmox 4.x
I was actually receiving a error like below:
# mount -t nfsd nfsd /proc/fs/nfsd mount: nfsd is write-protected, mounting read-only mount: cannot mount nfsd read-only
My proxmox edition was 5.0-30 and my CentOS was 7.
However, this is a bit different rather looking the other one as mentioned above. I was experiencing connecting my Centos 7 LXC container to a NFS server in the network. The regular tweak didn’t work. So, had to spend a while googling the solution. Found the correct one on a forum thread. But eventually it worked. For this you need to edit the file
nano /etc/pve/lxc/<your container ID>.conf
Add the below line in the conf file:
lxc.aa_profile: unconfined
Reboot the container. And now try to connect the NFS server. It should work.
For Proxmox 5 a little re-worked edition:
First run
cp /etc/apparmor.d/lxc/lxc-default-cgns /etc/apparmor.d/lxc/lxc-default-with-nfs
Then edit the new file /etc/apparmor.d/lxc/lxc-default-with-nfs:
replace profile lxc-container-default-cgns by profile lxc-default-with-nfs put the NFS configuration (see below) just before the closing bracket (})
NFS configuration
mount fstype=nfs*, mount fstype=rpc_pipefs,
or (being more explicit)
mount fstype=nfs, mount fstype=nfs4, mount fstype=nfsd, mount fstype=rpc_pipefs,
and finally run
service apparmor reload
Use the new profile
Edit /etc/pve/lxc/${container_id}.conf and append this line:
lxc.apparmor.profile: lxc-container-default-with-nfs
Then stop the container and start it again, e.g. like this:
pct stop ${container_id} && pct start ${container_id}
Now mounting NFS shares should work.
Configure Proxmox host for TLS connections: This configures the host to accept VNC connections.
aptitude install openbsd-inetd
Run this to get your KVM id’s :
qm list
root@homenet-home10 /etc # qm list VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID 101 freenas stopped 1024 32.00 0 102 debpbx running 512 0.00 573304 105 winxp stopped 512 15.01 0 7012 ltsp-ldap-openfire-KVM running 512 9.00 495870 7016 fbc16-kvm running 512 8.00 462697 7159 win7 stopped 2048 0.00 0 27014 ltsp-term-KVM stopped 512 0.00 0
edit /etc/inetd.conf , put a port for each kvm you want to access using kvm
#port kvm 59055 stream tcp nowait root /usr/sbin/qm qm vncproxy 105 59058 stream tcp nowait root /usr/sbin/qm qm vncproxy 7159
restart openbsd-inetd Continue reading “Enable VNC viewer for Proxmox 2.x/3.x with tightvnc” »
Problem found-
Error show: Code: INFO: setting parameters failed - VM is locked (backup) ERROR: Backup of VM 516 failed - command 'qm set 516 --lock backup' failed with exit code 255
Resolution:
qm unlock <vmid>
1. Command to list the running VPSs in a node
# vzlist
Example:
# vzlist CTID NPROC STATUS IP_ADDR HOSTNAME 106 104 running xx.xx.xx.xx server1.test.com 107 46 running xx.xx.xx.xx server2.test.com 108 83 running xx.xx.xx.xx server3.test.com 109 86 running xx.xx.xx.xx server4.test.com
2. This command lists all (running and stopped) the VPSs in a node.
# vzlist -a
Example:
# vzlist -a CTID NPROC STATUS IP_ADDR HOSTNAME 106 104 running xx.xx.xx.xx server1.test1.com 107 46 running xx.xx.xx.xx server2.test2.com 108 83 running xx.xx.xx.xx server3.test3.com 109 86 running xx.xx.xx.xx server4.test4.com 110 - stopped xx.xx.xx.xx server5.test5.com
Continue reading “Essential Openvz commands” »
NFS client on LXC seems do not work. Why? The problem is apparmor on the real machine that block any appempt to mount NFS volumes.
In order to try to minimize the security changes on apparmor I add the following lines in/etc/apparmor.d/lxc/lxc-default
# allow nfs mount everywhere mount fstype=rpc_pipefs, mount fstype=nfs,
Then
$ /etc/init.d/apparmor reload
And now I was able to restart nfs-common and nfs-kernel-server without errors !
Update!!!!!
nano /etc/apparmor.d/lxc/lxc-default
Update the file as below-
# Do not load this file. Rather, load /etc/apparmor.d/lxc-containers, which
# will source all profiles under /etc/apparmor.d/lxc
profile lxc-container-default flags=(attach_disconnected,mediate_deleted) {
#include <abstractions/lxc/container-base>
# the container may never be allowed to mount devpts. If it does, it
# will remount the host's devpts. We could allow it to do it with
# the newinstance option (but, right now, we don't).
# deny mount fstype=devpts,
# allow nfs mount everywhere
mount fstype=rpc_pipefs,
mount fstype=nfs,
}
sasasa
Now read the other article on how to connect to NFS server from LXC container