User virtual machines on VLAB servers: Difference between revisions
Jump to navigation
Jump to search
(Created page with "<p style="color: red;">'''Proposed''' user-defined virtual machine setup for VLAB servers. Not operational.</p> Implement and run a user-defined virtual machine (VM). == Programs == {|class="firstcolfixed" !Program name !Description |- |vmcreatedisk |Create a virtual hard disk (file). |- |vmrun | Run a virtual machines, booting either from a supplied CD/ISO image or from virtual hard disk. |} == <code>vmcreatedisk</code> == Do we really need this? Can't users just r...") |
m (→vmrun) |
||
| Line 45: | Line 45: | ||
* The machine will be configured for "user" networking, meaning it will be on its own private subnetwork. It will be able to connect externally using Network Address Translation (NAT) but will not be reachable itself from external hosts (including the server the virtual machine is running on). The VM will see the network interfaces as an Intel E1000 card. | * The machine will be configured for "user" networking, meaning it will be on its own private subnetwork. It will be able to connect externally using Network Address Translation (NAT) but will not be reachable itself from external hosts (including the server the virtual machine is running on). The VM will see the network interfaces as an Intel E1000 card. | ||
* It will have a graphical console. | * It will have a graphical console. | ||
* The <nowiki>[virtual</nowiki> CPU will be Intel. There can a maximum of TWO per VM. | * The <nowiki>[virtual]</nowiki> CPU will be Intel. There can be a maximum of TWO per VM. | ||
Revision as of 10:32, 1 Haziran 2023
Proposed user-defined virtual machine setup for VLAB servers. Not operational.
Implement and run a user-defined virtual machine (VM).
Programs
| Program name | Description |
|---|---|
| vmcreatedisk | Create a virtual hard disk (file). |
| vmrun |
Run a virtual machines, booting either from a supplied CD/ISO image or from virtual hard disk. |
vmcreatedisk
Do we really need this? Can't users just run qemu-img instead?
Usage: vmcreatedisk [options] <disk0> -h Display this help -s Size of new virtual hard disk in megabytes. Conflicts with -b -b Backing image for virtual hard disk. Conflicts with -s <disk0> virtual hard disk path for new disk
vmrun
Usage: vmrun [options] [<disk0> [<disk1> ...]] -h Display this help -m RAM megabytes (128/2048 - default 1024) -n virtual CPUs (1/2 - default 1) -i CD/ISO file path -I boot from CD/ISO instead of virtual hard disk <diskn> virtual hard disk path
vmrun runs a user-defined virtual machine using qemu/KVM.
- The machine will be configured for "user" networking, meaning it will be on its own private subnetwork. It will be able to connect externally using Network Address Translation (NAT) but will not be reachable itself from external hosts (including the server the virtual machine is running on). The VM will see the network interfaces as an Intel E1000 card.
- It will have a graphical console.
- The [virtual] CPU will be Intel. There can be a maximum of TWO per VM.