Does PaperCut work on a Virtual Machine (VM) or Virtual Server?
KB Home | Does PaperCut work on a Virtual Machine (VM) or Virtual Server?
Main.PaperCutOnVM History
Hide minor edits - Show changes to output
October 19, 2015, at 11:17 PM
by - Updated to clarify RAM/CPU requirements
Changed lines 7-8 from:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on networks. We find that many sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM. If the VM is dedicated to running PaperCut, see the KB article [[IncreaseMaxMemoryUsage|+]].
to:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. '''NOTE''': PaperCut will use 1/4 of the available memory of the machine by default. So if you are building a VM for the PaperCut App Server, start off with a 4GB VM, and allow PaperCut to use up to 1/2 of the memory by making [[https://www.papercut.com/kb/Main/IncreaseMaxMemoryUsage|this config change]]. We find that many sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM. If the VM is dedicated to running PaperCut, see the KB article [[IncreaseMaxMemoryUsage|+]].
Changed lines 13-14 from:
* Ensure you allocate enough CPU resource to the VM. PaperCut is highly multi-threaded and we recommend more than one virtual CPU - particularly if the machine is acting as both the PaperCut primary application server and a busy print server.
to:
* Ensure you allocate enough CPU resource to the VM. PaperCut is highly multi-threaded and we recommend '''more than one virtual CPU''' - particularly if the machine is acting as both the PaperCut primary application server and a busy print server.
Changed line 32 from:
[-Keywords: artificial, virtualisation, hypervisor, `HyperV-]
to:
[-Keywords: artificial, virtualisation, hypervisor, `HyperV-]
Changed line 29 from:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]], [[http://www.virtualbox.org/|VirtualBox]], and `VMWare vSphere for platform testing.
to:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM]], [[http://www.virtualbox.org/|VirtualBox]], and `VMWare vSphere for platform testing.
Changed line 29 from:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and [[http://www.virtualbox.org/|VirtualBox]], and `VMWare vSphere for platform testing.
to:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]], [[http://www.virtualbox.org/|VirtualBox]], and `VMWare vSphere for platform testing.
Changed lines 3-4 from:
Yes. PaperCut will work fine and is fully supported on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux). We're finding that more users, both large and small are moving across to virtual machines to host their print queues and [[https://www.papercut.com/|print control software]].
to:
Yes. PaperCut will work fine and is fully supported on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux). We're finding that more users, both large and small are moving across to virtual machines to host their print queues and [[https://www.papercut.com/|print control software]]. There is also a growing trend in [[PrivateCloud|private cloud]] deployments.
Changed lines 9-10 from:
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory allocated to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technical explanation as to why this is important).
to:
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory allocated to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has '''full access''' to all the physical memory allocated to the guest OS. (See the section below for a technical explanation as to why this is important).
Changed line 29 from:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and [[http://www.virtualbox.org/|VirtualBox]], and VMWare vSphere for platform testing.
to:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and [[http://www.virtualbox.org/|VirtualBox]], and `VMWare vSphere for platform testing.
Changed line 29 from:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and [[http://www.virtualbox.org/|VirtualBox]] for platform testing.
to:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and [[http://www.virtualbox.org/|VirtualBox]], and VMWare vSphere for platform testing.
Changed lines 7-10 from:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on most large networks. We find that many sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM. If the VM is dedicated to running PaperCut, see the KB article [[IncreaseMaxMemoryUsage|+]].
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technical explanation as to why this is important).
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technical explanation as to why this is important).
to:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on networks. We find that many sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM. If the VM is dedicated to running PaperCut, see the KB article [[IncreaseMaxMemoryUsage|+]].
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory allocated to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technical explanation as to why this is important).
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory allocated to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technical explanation as to why this is important).
Changed lines 3-4 from:
Yes. PaperCut will work fine and is fully supported on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux). We're finding that more users, both big and small are moving across to virtual machines to host their print queues and [[https://www.papercut.com/|print control software]].
to:
Yes. PaperCut will work fine and is fully supported on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux). We're finding that more users, both large and small are moving across to virtual machines to host their print queues and [[https://www.papercut.com/|print control software]].
Changed lines 7-16 from:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM. If the VM is dedicated to running PaperCut, see the KB article [[IncreaseMaxMemoryUsage|+]].
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technicalexpiation as to why this is important).
* Keep an eye on system performance over the first few weeks of operation. We've seen sites deploy PaperCut on overloaded VM Hostsand the guests are starved of resources. This would usually be observed by seeing slow printing performance and/or a sluggish "feel" when using the web administration interface.
* Ensure you allocate enough CPU resource to the VM. PaperCut is highly multi-threaded and we recommend more than one virtual CPU. Particularly if the machine is acting as both the PaperCut primary application server and a busy print server.
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended. i.e. one small corruption in a part of a disk image may render the whole filesystem useless. Having a backup of just the files you need will reduce the changes of such a mishap occurring.
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technical
* Keep an eye on system performance over the first few weeks of operation. We've seen sites deploy PaperCut on overloaded VM Hosts
* Ensure you allocate enough CPU resource to the VM. PaperCut is highly multi-threaded and we recommend more than one virtual CPU
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended
to:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on most large networks. We find that many sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM. If the VM is dedicated to running PaperCut, see the KB article [[IncreaseMaxMemoryUsage|+]].
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technical explanation as to why this is important).
* Keep an eye on system performance over the first few weeks of operation. We've seen sites deploy PaperCut on overloaded VM Hosts causing guests to be starved of resources. This would usually be observed by seeing slow printing performance and/or a sluggish "feel" when using the web administration interface.
* Ensure you allocate enough CPU resource to the VM. PaperCut is highly multi-threaded and we recommend more than one virtual CPU - particularly if the machine is acting as both the PaperCut primary application server and a busy print server.
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended - i.e. one small corruption in a part of a disk image may render the whole filesystem useless. Having a backup of just the files you need will reduce the changes of such a mishap occurring.
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technical explanation as to why this is important).
* Keep an eye on system performance over the first few weeks of operation. We've seen sites deploy PaperCut on overloaded VM Hosts causing guests to be starved of resources. This would usually be observed by seeing slow printing performance and/or a sluggish "feel" when using the web administration interface.
* Ensure you allocate enough CPU resource to the VM. PaperCut is highly multi-threaded and we recommend more than one virtual CPU - particularly if the machine is acting as both the PaperCut primary application server and a busy print server.
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended - i.e. one small corruption in a part of a disk image may render the whole filesystem useless. Having a backup of just the files you need will reduce the changes of such a mishap occurring.
Changed lines 21-23 from:
If an operating system's physical RAM is swapped out by the VM host, the whole operating system may freeze while its memory is paged back in. (Note that this behaviour is different to application swapping as the whole operating system is contended rather than just an application.) During this period the operating system will be unable to process new TCP connections in a ream-time fashion. TCP connections may back up (or time-out) and when the system returns, and the TCP traffic will flood back in. This may swamp the system. PaperCut has seen this "bursty" network behaviour cause issues on large sites with high print volumes, a large number of active clients and/or a large number of jobs in a hold/release queue. The issues have been resolved by ensuring that memory allocated to the Virtual Machine Guest hosting PaperCut is reserved physical memory.
to:
If an operating system's physical RAM is swapped out by the VM host, the whole operating system may freeze while its memory is paged back in. (Note that this behavior is different to application swapping as the whole operating system is contended rather than just an application.) During this period the operating system will be unable to process new TCP connections in a real-time fashion. TCP connections may back up (or time-out) and when the system returns, and the TCP traffic will flood back in. This may swamp the system. PaperCut has seen this "bursty" network behavior cause issues on large sites with high print volumes, a large number of active clients and/or a large number of jobs in a hold/release queue. These issues have been resolved by ensuring that memory allocated to the Virtual Machine Guest hosting PaperCut is reserved physical memory.
Changed lines 9-10 from:
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximium amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS.
to:
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximum amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS. (See the section below for a technical expiation as to why this is important).
Added lines 17-23:
!!!Why is VM physical RAM allocation important?
PaperCut is a real-time application. It needs to be able to respond to network requests in a timely manner. Network requests come from a variety of sources ranging from secondary print servers, MFD embedded software, desktop client software, and of course Administrators using the web browser interface. Because of this real-time nature, it's important to ensure that the operating system has Physical RAM reserved.
If an operating system's physical RAM is swapped out by the VM host, the whole operating system may freeze while its memory is paged back in. (Note that this behaviour is different to application swapping as the whole operating system is contended rather than just an application.) During this period the operating system will be unable to process new TCP connections in a ream-time fashion. TCP connections may back up (or time-out) and when the system returns, and the TCP traffic will flood back in. This may swamp the system. PaperCut has seen this "bursty" network behaviour cause issues on large sites with high print volumes, a large number of active clients and/or a large number of jobs in a hold/release queue. The issues have been resolved by ensuring that memory allocated to the Virtual Machine Guest hosting PaperCut is reserved physical memory.
PaperCut is a real-time application. It needs to be able to respond to network requests in a timely manner. Network requests come from a variety of sources ranging from secondary print servers, MFD embedded software, desktop client software, and of course Administrators using the web browser interface. Because of this real-time nature, it's important to ensure that the operating system has Physical RAM reserved.
If an operating system's physical RAM is swapped out by the VM host, the whole operating system may freeze while its memory is paged back in. (Note that this behaviour is different to application swapping as the whole operating system is contended rather than just an application.) During this period the operating system will be unable to process new TCP connections in a ream-time fashion. TCP connections may back up (or time-out) and when the system returns, and the TCP traffic will flood back in. This may swamp the system. PaperCut has seen this "bursty" network behaviour cause issues on large sites with high print volumes, a large number of active clients and/or a large number of jobs in a hold/release queue. The issues have been resolved by ensuring that memory allocated to the Virtual Machine Guest hosting PaperCut is reserved physical memory.
Added lines 13-14:
* Ensure you allocate enough CPU resource to the VM. PaperCut is highly multi-threaded and we recommend more than one virtual CPU. Particularly if the machine is acting as both the PaperCut primary application server and a busy print server.
Changed lines 5-6 from:
General Advise:
to:
General Advice:
Changed line 20 from:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and [[http://www.virtualbox.org/|Virtual Box]] for platform testing.
to:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and [[http://www.virtualbox.org/|VirtualBox]] for platform testing.
Changed line 23 from:
[-Keywords: artificial, virtual machine, virtualisation, hypervisor, `HyperV -]
to:
[-Keywords: artificial, virtualisation, hypervisor, `HyperV-]
Changed lines 9-10 from:
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VMWare] and like tools allow admins to restrict a guest VM to a maximium amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS.
to:
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VM tools often allow admins to restrict a guest VM to a maximium amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS.
Changed lines 9-10 from:
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. VMWare and like tools allow admins to restrict a guest VM to a maximium amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS.
to:
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. `VMWare] and like tools allow admins to restrict a guest VM to a maximium amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS.
Changed lines 9-10 from:
* '''IMPORTANT:''' Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. VMWare and like tools allow admins to restrict a guest VM to a maximium amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS.
to:
* '''IMPORTANT''': Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. VMWare and like tools allow admins to restrict a guest VM to a maximium amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS.
Added lines 9-10:
* '''IMPORTANT:''' Ensure that the VM host does not artificially restrict physical memory to the PaperCut machine. VMWare and like tools allow admins to restrict a guest VM to a maximium amount of physical RAM. This option can have severely adverse affects on the PaperCut system. Ensure that the PaperCut guest VM has full access to all the physical memory allocated to the guest OS.
Changed line 18 from:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and Virtual Box for platform testing.
to:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and [[http://www.virtualbox.org/|Virtual Box]] for platform testing.
Changed lines 7-8 from:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM. If the VM is dedicated to running PaperCut, see the KB article [[IncreaseMaxMemoryUsage|+]]
to:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM. If the VM is dedicated to running PaperCut, see the KB article [[IncreaseMaxMemoryUsage|+]].
Changed lines 1-4 from:
(:title Does PaperCut work on a VM or Virtual Server? :)
Yes. PaperCut will work fine and is fully supported on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux).
Yes. PaperCut will work fine and is fully supported on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux).
to:
(:title Does PaperCut work on a Virtual Machine (VM) or Virtual Server? :)
Yes. PaperCut will work fine and is fully supported on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux). We're finding that more users, both big and small are moving across to virtual machines to host their print queues and [[https://www.papercut.com/|print control software]].
Yes. PaperCut will work fine and is fully supported on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux). We're finding that more users, both big and small are moving across to virtual machines to host their print queues and [[https://www.papercut.com/|print control software]].
Changed lines 7-8 from:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM.
to:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM. If the VM is dedicated to running PaperCut, see the KB article [[IncreaseMaxMemoryUsage|+]]
Changed line 18 from:
''Side note: PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and Virtual Box for platform testing.
to:
''Side note'': PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and Virtual Box for platform testing.
Added line 18:
''Side note: PaperCut uses [[https://www.papercut.com/blog/chris/2008/11/14/using-kvm-to-securely-host-servers-in-a-dmz/|KVM internally]] and Virtual Box for platform testing.
Changed lines 7-8 from:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM.
to:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB or higher will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM.
Changed lines 11-12 from:
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended. i.e. one small corruption in a part of a disk image may render the whole filesystem useless. Have a backup of just the files you need will reduce the changes of such a mishap occurring.
to:
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended. i.e. one small corruption in a part of a disk image may render the whole filesystem useless. Having a backup of just the files you need will reduce the changes of such a mishap occurring.
Changed lines 7-8 from:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Servers require a little more.
to:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Server guests will suffer with poor performance with low RAM.
Changed lines 16-17 from:
As a general rule we do not encourage the use of QEMU in a Linux server environment as the performance is a little slow. Instead consider KVM. KVM builds on QEMU and leverages hardware vitalization. Xen is another popular alternative.
to:
As a general rule we do not encourage the use of QEMU in a Linux server environment as the performance is a little slow. Instead consider KVM. KVM builds on QEMU and leverages hardware vitalization. XEN is another popular alternative.
Changed lines 11-12 from:
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended. i.e. one small corruption in a part of a disk image may render the whole filesystem useless. Have just the files you need will reduce the changes of such a mishap occurring.
to:
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended. i.e. one small corruption in a part of a disk image may render the whole filesystem useless. Have a backup of just the files you need will reduce the changes of such a mishap occurring.
Changed lines 16-17 from:
As a general rule we do not encourage the use of QEMU in a Linux server environment as the performance is a little slow. Instead consider KVM. KVM builds on QEMU and leverages hardware vitalization.
to:
As a general rule we do not encourage the use of QEMU in a Linux server environment as the performance is a little slow. Instead consider KVM. KVM builds on QEMU and leverages hardware vitalization. Xen is another popular alternative.
Changed lines 3-4 from:
Yes. PaperCut will work fine on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux).
to:
Yes. PaperCut will work fine and is fully supported on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux).
Changed lines 13-14 from:
!! Comments on individual technologies:
to:
!!!Comments on individual technologies:
Added lines 12-16:
!! Comments on individual technologies:
QEMU:
As a general rule we do not encourage the use of QEMU in a Linux server environment as the performance is a little slow. Instead consider KVM. KVM builds on QEMU and leverages hardware vitalization.
Changed lines 9-10 from:
* Keep an eye on system performance over the first few weeks of operation. We've seen sites deploy PaperCut on overloaded VM Hosts and the guests are starved of resources. This would usually be observed by setting slow printing performance and/or a sluggish feel when using the web administration interface.
to:
* Keep an eye on system performance over the first few weeks of operation. We've seen sites deploy PaperCut on overloaded VM Hosts and the guests are starved of resources. This would usually be observed by seeing slow printing performance and/or a sluggish "feel" when using the web administration interface.
Changed line 11 from:
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended.
to:
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended. i.e. one small corruption in a part of a disk image may render the whole filesystem useless. Have just the files you need will reduce the changes of such a mishap occurring.
Changed lines 1-2 from:
(:title Does PaperCut work on a VM or Virtual Server ? :)
to:
(:title Does PaperCut work on a VM or Virtual Server? :)
Changed lines 1-2 from:
(:title Does PaperCut work on a VM ? :)
to:
(:title Does PaperCut work on a VM or Virtual Server ? :)
Changed lines 5-11 from:
to:
General Advise:
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Servers require a little more.
* Keep an eye on system performance over the first few weeks of operation. We've seen sites deploy PaperCut on overloaded VM Hosts and the guests are starved of resources. This would usually be observed by setting slow printing performance and/or a sluggish feel when using the web administration interface.
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended.
* Take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB will be enough on most large networks. We find that sites have a tendency to run their VM's light on RAM. Linux systems generally handle this well but Microsoft Servers require a little more.
* Keep an eye on system performance over the first few weeks of operation. We've seen sites deploy PaperCut on overloaded VM Hosts and the guests are starved of resources. This would usually be observed by setting slow printing performance and/or a sluggish feel when using the web administration interface.
* Take care with backups. Although a snapshot or copy of a whole VM disk image is a backup option, scheduling a direct PaperCut data file or database backup is still strongly recommended.
Changed lines 3-4 from:
Yes. PaperCut will work fine on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
to:
Yes. PaperCut will work fine on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, Parallels, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on Windows, Mac and Linux).
Changed lines 3-4 from:
Yes. PaperCut will work fine on `VMs such as `VMware, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
to:
Yes. PaperCut will work fine on `VMs such as `VMware, EX Server, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
Changed lines 3-4 from:
Yes. PaperCut will work fine on `VMs such as `VMware, Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
to:
Yes. PaperCut will work fine on `VMs such as `VMware, Microsoft Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
Changed line 8 from:
[-Keywords: artificial, virtual machine, virtualisation, hypervisor, HyperV -]
to:
[-Keywords: artificial, virtual machine, virtualisation, hypervisor, `HyperV -]
Changed line 8 from:
[-Keywords: artificial, virtual machine, virtualisation, hypervisor -]
to:
[-Keywords: artificial, virtual machine, virtualisation, hypervisor, HyperV -]
Changed lines 3-4 from:
Yes. PaperCut will work fine on `VMs such as `VMware, Virtual Server, `Hyper-V, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
to:
Yes. PaperCut will work fine on `VMs such as `VMware, Virtual Server, Hyper-V, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
Changed line 5 from:
You should take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2 GB will be enough on most large networks.
to:
You should take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2.0 GB will be enough on most large networks.
Changed lines 3-4 from:
Yes. PaperCut will work fine on `VMs such as `VMware, Virtual Server, `HyperV, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
to:
Yes. PaperCut will work fine on `VMs such as `VMware, Virtual Server, `Hyper-V, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
Changed line 8 from:
[-Keywords: artificial, virtual machine -]
to:
[-Keywords: artificial, virtual machine, virtualisation, hypervisor -]
Changed lines 3-5 from:
All you need to make sure is
to:
Yes. PaperCut will work fine on `VMs such as `VMware, Virtual Server, `HyperV, `VirtualBox, Xen, KVM, and QEMU. We do have many large customers now running PaperCut in virtualized environments (on both Windows and Linux).
You should take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2 GB will be enough on most large networks.
You should take care not to skimp on RAM. Allocate a server class amount of RAM to your VM. 2 GB will be enough on most large networks.
Changed line 8 from:
[-Keywords: artificial -]
to:
[-Keywords: artificial, virtual machine -]
Changed line 5 from:
All you need to make sure is to allocate memory as much required on a server class. On most systems 2 GB will be enough.
to:
All you need to make sure is to allocate memory as much required on a server class OS. On most systems 2 GB will be enough.
Changed lines 3-4 from:
The answer is Yes. PaperCut will work fine on VMs such as VMware, Virtual Server, HyperV, VirtualBox, Xen, KVM, and QEMU. We do have large customers running PaperCut in a virtual environment.
to:
The answer is Yes. PaperCut will work fine on `VMs such as `VMware, Virtual Server, `HyperV, `VirtualBox, Xen, KVM, and QEMU. We do have large customers running PaperCut in a virtual environment.
Changed lines 3-4 from:
The answer is Yes. PaperCut will work fine on VM such as VMware, Virtual Server, Hyper V, Virtual Box, Xen, KVM, and QEMU. We do have large customers running PaperCut in a virtual environment.
to:
The answer is Yes. PaperCut will work fine on VMs such as VMware, Virtual Server, HyperV, VirtualBox, Xen, KVM, and QEMU. We do have large customers running PaperCut in a virtual environment.
Changed lines 3-4 from:
The answer is Yes. PaperCut will work fine on VMs such as VM Ware, Virtual Server, Hyper V, Virtual Box, Xen, KVM, and QEMU. We do have large customers running PaperCut in a virtual environment.
to:
The answer is Yes. PaperCut will work fine on VM such as VMware, Virtual Server, Hyper V, Virtual Box, Xen, KVM, and QEMU. We do have large customers running PaperCut in a virtual environment.
Changed lines 3-4 from:
The answer is Yes. PaperCut will work fine on VMs such as VMWare, Virtual Server, HyperV, VirtualBox, Xen, KVM, and QEMU. We do have large customers running PaperCut in a virtual environment.
to:
The answer is Yes. PaperCut will work fine on VMs such as VM Ware, Virtual Server, Hyper V, Virtual Box, Xen, KVM, and QEMU. We do have large customers running PaperCut in a virtual environment.
Changed lines 4-5 from:
All you need to make sure is to allocate memory as much required on a server class. On most systems 2 GB will be enough. we do have large customers running PaperCut ? We have seen a few customers choosing to go for birtualization environment:) allocate enough memory as a server class
to:
All you need to make sure is to allocate memory as much required on a server class. On most systems 2 GB will be enough.
Changed lines 3-4 from:
The answer is Yes. PaperCut will work fine on a VM such as VMWare, Virtual Server, HyperV, VirtualBox, Xen, KVM, QEmu. We do have large customers running PaperCut in a virtual environment.
All you need to make sure is to allocate memory as much required on a server class. On most systems 2 GB will be enough. we do have large customers running PaperCut ? We have seen a few customers choosing to go for birtualization environment:) allocate enough memory as a serverclass
All you need to make sure is to allocate memory as much required on a server class. On most systems 2 GB will be enough. we do have large customers running PaperCut ? We have seen a few customers choosing to go for birtualization environment:) allocate enough memory as a server
to:
The answer is Yes. PaperCut will work fine on VMs such as VMWare, Virtual Server, HyperV, VirtualBox, Xen, KVM, and QEMU. We do have large customers running PaperCut in a virtual environment.
All you need to make sure is to allocate memory as much required on a server class. On most systems 2 GB will be enough. we do have large customers running PaperCut ? We have seen a few customers choosing to go for birtualization environment:) allocate enough memory as a server class
----
[-Keywords: artificial -]
All you need to make sure is to allocate memory as much required on a server class. On most systems 2 GB will be enough. we do have large customers running PaperCut ? We have seen a few customers choosing to go for birtualization environment:) allocate enough memory as a server class
----
[-Keywords: artificial -]
Changed lines 1-4 from:
(:title Does PaperCut work on VM ? :)
to:
(:title Does PaperCut work on a VM ? :)
The answer is Yes. PaperCut will work fine on a VM such as VMWare, Virtual Server, HyperV, VirtualBox, Xen, KVM, QEmu. We do have large customers running PaperCut in a virtual environment.
All you need to make sure is to allocate memory as much required on a server class. On most systems 2 GB will be enough. we do have large customers running PaperCut ? We have seen a few customers choosing to go for birtualization environment:) allocate enough memory as a server class
The answer is Yes. PaperCut will work fine on a VM such as VMWare, Virtual Server, HyperV, VirtualBox, Xen, KVM, QEmu. We do have large customers running PaperCut in a virtual environment.
All you need to make sure is to allocate memory as much required on a server class. On most systems 2 GB will be enough. we do have large customers running PaperCut ? We have seen a few customers choosing to go for birtualization environment:) allocate enough memory as a server class
Changed line 1 from:
(:
to:
(:title Does PaperCut work on VM ? :)
Changed line 1 from:
( Does PaperCut work on VM :)
to:
(: Does PaperCut work on VM :)
Comments
Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.
Article last modified on October 19, 2015, at 11:17 PM
Printable View | Article History | Edit Article