NuKVM/xen-orchestra
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Text improvements (#123)

Browse Source 
* fixed some typos and made some small improvement to make the text more readable.
This commit is contained in:
ETL
2018-03-20 16:46:32 -04:00
committed by Olivier Lambert
parent f5d6407ec9
commit 96f4896c84
17 changed files with 59 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/vm_creation.md
View File

@@ -36,7 +36,7 @@ Those values can be changed anytime after your VM is created.
#### Multiple VMs
You can create multiple VMs at one here, if you toggle the option. The `{name}` pattern is the "Name" field of the VM. By default, it will start with number 1 and so on. You can change this via the "First index" label.
You can create multiple VMs at once by toggling the *Multiple VMs* option. The `{name}` pattern is the "Name" field of the VM. By default, it will start with number 1 and so on. You can change this via the "First index" field.
Click on refresh icon to take the change into account:
@@ -48,11 +48,11 @@ This is where you are configuring VM performances: number of vCPUs, RAM, CPU wei
#### CPU weight and cap
CPU weight default number is `256`. It means that it will be scheduler by Xen like any other VMs on the host where it runs. If you raise it, eg with `512`, CPUs on this VM will be scheduled twice more than another one. If you diminish it, with `64` for example, it will be schedule 4 times less.
CPU weight default number is `256` which means it will be scheduled by Xen like any other VMs on the host where it runs. If you raise it, eg with `512`, CPUs on this VM will be scheduled twice more than another one. If you diminish it, with `64` for example, it will be schedule 4 times less.
What about cap? It's the maximum amount of CPUs a VM can consume. It's using a 100 base (1 vCPU: 100). Default is 0 and means no upper cap.
What about cap? It's the maximum amount of CPUs a VM can consume, using a 100 base (1 vCPU: 100). Default is 0 and means no upper cap.
> Should I mess with these settings? In general: nope. It's only when you are sure of what are you doing. More can be found here: https://wiki.xen.org/wiki/Credit_Scheduler
> Should I mess with these settings? In general: nope. Change this only if you are sure of what are you doing. More can be found here: https://wiki.xen.org/wiki/Credit_Scheduler
### Install settings
@@ -76,7 +76,7 @@ Please refer to the [XenServer CloudInit section](cloudinit.md) for more.
### Interfaces
This is the network part of the VM configuration: in general, MAC field is kept empty (autogenerated from XenServer). We also select the management network by default: you can change it reflecting your own network configuration.
This is the network part of the VM configuration: in general, MAC field is kept empty (autogenerated from XenServer). We also select the management network by default, but you can change it to reflect your own network configuration.
### Disks