- NEW: Proxmox VE 6.1
- Moving disk image from one KVM machine to another
- Resize disks
- How to add an existing virtual disk to Proxmox
- User Management
Moving disk image from one KVM machine to another
In order to get new images you need a repository. Give you have no subscription we have to add the correct repository. Add the pev-no-sybscription between the main contrib and security updates in the file:. For home users the default bridged network makes most sense so not extra network is configured. Multiple bridges can be created. For improved security, vlans can be setup. I might do this in a test environmet but will not use VLAN for now. Creating the virtual machine. Default values apply if not specified in the instructions or on image. Download debian or what ever operating system you prefere. I use net install image of Debian 9. Select amd64 CD or torrent if you prefer. Hard disk I used 20 Gig as start disk, remember that the whole disk wont be allocated at once. This is the max size. For other operating systems please see other. I used swedish as language and sweden as location - Choose host name, I use hassio - Set the root password - Set the non root name and username - Use whole disk and standard settings for partitioning - Use standard settings util you are at the software selection - Unselect debian environment and print server - Select "SSH" server, I am sure you want to connect remote to the machine - Install rest as default and reboot. Install sudo and add your user the one you provided in installtime and exit from su. Make sure your settings are correct. In an VM the eth0 is probable something else. To list network interfaces write ip link show to get the correct one. You need to select the ethernet interface. Now it is a good time to make a snapshot.
How to add an existing virtual disk to Proxmox
Proxmox VE supports multiple authentication sources, e. By using the role based user- and permission management for all objects VMs, storages, nodes, etc. Passwords are not stored here, users are instead associated with authentication realms described below. This user cannot be deleted, but attributes can still be changed and system mails will be sent to the email address assigned to this user. Each user can be member of several groups. Groups are the preferred way to organize access permissions. You should always grant permission to groups instead of using individual users. That way you will get a much shorter access control list which is easier to handle. Tokens can be generated for individual users and can be given separate permissions and expiration dates to limit the scope and duration of the access. Should the API token get compromised it can be revoked without disabling the user itself. The following realms authentication methods are available:. In this case a system user has to exist e. Password are encrypted using the SHA hash method. This is the most convenient method for small or even medium installations where users do not need access to anything outside of Proxmox VE. It is possible to authenticate users via an LDAP server e. The server and an optional fallback server can be configured and the connection can be encrypted via SSL. This file should contain a single line containing the raw password. A server and authentication domain need to be specified. Like with ldap an optional fallback server, optional port, and SSL encryption can be configured. In this case a newly created user needs their keys added immediately as there is no way to log in without the second factor. Alternatively, users can choose to opt in to two-factor authentication via TOTP later on, even if the realm does not enforce it. As another option, if the server has an AppId configured, a user can opt into U2F authentication, provided the realm does not enforce any other second factor. This can be done by selecting one of the available methods via the TFA dropdown box when adding or editing an Authentication Realm. The time step and password length parameters are configured. A user can have multiple keys configured separated by spacesand the keys can be specified in Base32 RFC or hexadecimal notation. The Secret field contains the key, which can simply be generated randomly via the Randomize button. Now the user needs to verify both the current user password unless logged in as rootas well as the ability to correctly use the TOTP key by typing the current OTP value into the Verification Code field before pressing the Apply button. To allow users to use U2F authentication, the server needs to have a valid domain with a valid https certificate. Please note that some browsers may be more strict than others when matching AppIds.