New pages
Jump to navigation
Jump to search
- 12:34, 3 March 2025 Solaris guest best practices (hist | edit) [1,306 bytes] A.lauterer (talk | contribs) (Created page with "== Introduction == This is a set of best practices when using Solaris in a VM. == Solaris 10 up to 11.3 == These versions don't come with support for VirtIO out of the box. Use the following VM settings: * '''Guest OS:''' Solaris * '''Disk:''' SATA or IDE * '''Network:''' e1000 * '''Machine-Type:''' i440 === Known Issues === CPUs and cores are not detected properly. If you run <code>psrinfo -pv</code> or <code>mpstat</code>, it will detect sockets, but not all core...")
- 15:22, 12 February 2025 QEMU Machine Version Upgrade (hist | edit) [4,342 bytes] Thomas Lamprecht (talk | contribs) (Created page with "== Introduction == This page documents specific incompatibilities between QEMU machine versions that can cause issues in guests. Please report any other issues you encounter, so they can be documented too. For general information about QEMU machine types in Proxmox VE, see [https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_machine_type the corresponding chapter in the Proxmox VE documentation]. Before upgrading the machine version, be sure to have a working backup f...")
- 14:23, 20 January 2025 VM Backup Consistency (hist | edit) [3,933 bytes] A.lauterer (talk | contribs) (Created page with "When backups (or snapshots) are triggered for VMs in Proxmox VE, it is necessary to make sure that the guest has written the latest changes to the disk image before the backup starts (or the snapshot is created). This is handled by the Qemu-Guest-Agent inside the guest OS. The trigger that can be observed in the backup task log: <pre> INFO: issuing guest-agent 'fs-freeze' command INFO: issuing guest-agent 'fs-thaw' command </pre> This will cause the guest OS to ensure t...")