Creating VMs - Revision history

Wikislax: /* Creating a PV VM */

2026-04-06T20:55:03Z

‎Creating a PV VM

Wikislax: /* Creating a PV VM */

2026-04-01T13:52:33Z

‎Creating a PV VM

Wikislax: /* Creating a PV VM */

2018-08-03T17:21:40Z

‎Creating a PV VM

Wikislax: /* Creating a PV VM */

2018-07-30T20:37:56Z

‎Creating a PV VM

Wikislax: /* Creating a PV VM */

2018-07-30T20:23:51Z

‎Creating a PV VM

Wikislax: /* Creating a PV VM */

2018-07-30T18:40:33Z

‎Creating a PV VM

Wikislax: /* Creating a PV VM */

2018-07-30T18:20:16Z

‎Creating a PV VM

Wikislax: /* Creating a PV VM */

2018-07-07T04:32:05Z

‎Creating a PV VM

Wikislax: /* Creating a HVM */

2018-07-07T04:30:59Z

‎Creating a HVM

Wikislax: /* Creating a PV VM */

2018-07-07T04:20:35Z

‎Creating a PV VM

@@ Line 25: / Line 25: @@
   # mkdir loop
   # mount -o loop sl12.img loop
-  # cp -ax /mnt/sl12/{0,bin,boot,etc,home,initrd*,lib,lib64,media,mnt,opt,root,run,sbin,srv,sys,usr,var,vmlinuz*} loop
+  # cp -ax /mnt/sl12/{0,bin,boot,etc,home,lib,lib64,media,mnt,opt,root,run,sbin,srv,sys,usr,var} loop
   # mkdir loop/{dev,proc,tmp}
   # chmod 777 loop/tmp

@@ Line 19: / Line 19: @@
 Paravirtualization requires storing the kernel to boot in the dom0 filesystem, and populating the system in a virtual partition. The kernel generated must be able to manage [http://wiki.qemu.org/download/qemu-doc.html#QEMU-PC-System-emulator the QEMU devices] and include the .config file [http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs#Configuring_the_kernel domU options]. Here is a minimal example of such a [{{SERVER}}/wikislax/download/config-domU .config domU] file. The swap partition and VM filesystem can be created as below. Don't forget to update the root device in fstab :
-  # dd if=/dev/zero of=sl12.swp bs=1024k count=1024
+  # dd if=/dev/zero of=sl12.swp bs=1024k count=1024 status=progress
   # mkswap sl12.swp
-  # dd if=/dev/zero of=sl12.img bs=1024k count=16384
+  # dd if=/dev/zero of=sl12.img bs=1024k count=16384 status=progress
   # mkfs -t ext3 sl12.img
   # mkdir loop

@@ Line 21: / Line 21: @@
   # dd if=/dev/zero of=sl12.swp bs=1024k count=1024
   # mkswap sl12.swp
-  # dd if=/dev/zero of=sl12.img bs=1024k count=8192
+  # dd if=/dev/zero of=sl12.img bs=1024k count=16384
   # mkfs -t ext3 sl12.img
   # mkdir loop

@@ Line 31: / Line 31: @@
   # umount loop
   # dd if=/dev/zero bs=1G count=8 >> sl12.img
-  # fsck -f sl12.img
+  # e2fsck -f sl12.img
   # resize2fs sl12.img

@@ Line 25: / Line 25: @@
   # mkdir loop
   # mount -o loop sl12.img loop
-  # cp -ax /mnt/sl12/{0,bin,boot,etc,home,initrd*,lib,lib32,lib64,media,mnt,opt,root,run,sbin,srv,sys,usr,var,vmlinuz*} loop
+  # cp -ax /mnt/sl12/{0,bin,boot,etc,home,initrd*,lib,lib64,media,mnt,opt,root,run,sbin,srv,sys,usr,var,vmlinuz*} loop
   # mkdir loop/{dev,proc,tmp}
   # chmod 777 loop/tmp

@@ Line 19: / Line 19: @@
 Paravirtualization requires storing the kernel to boot in the dom0 filesystem, and populating the system in a virtual partition. The kernel generated must be able to manage [http://wiki.qemu.org/download/qemu-doc.html#QEMU-PC-System-emulator the QEMU devices] and include the .config file [http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs#Configuring_the_kernel domU options]. Here is a minimal example of such a [{{SERVER}}/wikislax/download/config-domU .config domU] file. The swap partition and VM filesystem can be created as below. Don't forget to update the root device in fstab :
-  # dd if=/dev/zero of=pv-sl12.swap bs=1024k count=1024
+  # dd if=/dev/zero of=sl12.swp bs=1024k count=1024
-  # mkswap pv-sl12.swap
+  # mkswap sl12.swp
-  # dd if=/dev/zero of=pv-sl12.img bs=1024k count=8192
+  # dd if=/dev/zero of=sl12.img bs=1024k count=8192
-  # mkfs -t ext3 pv-sl12.img
+  # mkfs -t ext3 sl12.img
-  # mkdir /tmp/loop
+  # mkdir loop
-  # mount -o loop pv-sl12.img /tmp/loop
+  # mount -o loop sl12.img loop
-  # cp -ax /mnt/sl12/{0,bin,boot,etc,home,initrd*,lib,lib32,lib64,media,mnt,opt,root,run,sbin,srv,sys,usr,var,vmlinuz*} /tmp/loop
+  # cp -ax /mnt/sl12/{0,bin,boot,etc,home,initrd*,lib,lib32,lib64,media,mnt,opt,root,run,sbin,srv,sys,usr,var,vmlinuz*} loop
-  # mkdir /tmp/loop/{dev,proc,tmp}
+  # mkdir loop/{dev,proc,tmp}
-  # chmod 777 /tmp/loop/tmp
+  # chmod 777 loop/tmp
-  # vi /tmp/loop/etc/fstab
+  # vi loop/etc/fstab
-  # umount /tmp/loop
+  # umount loop
 Then a PV config file needs to be created. Samples are available from the /etc/xen directory. Here is an [{{SERVER}}/wikislax/download/sl12 example] running in a X window for slackware 12.1 (32 bits). The main config options to modify are :
@@ Line 52: / Line 55: @@
   root = "/dev/xvda1 ro"
   # Window resolution additional parameters
-  extra = "xen-fbfront.video=16,1280,768"
+  extra = "xen-fbfront.video=16,1680,1024"
 The VM can then be launched with '''xl create ''file''''' :

@@ Line 64: / Line 64: @@
 * in full hardware virtualization (HVM) guests require CPU virtualization extensions from the host CPU (Intel VT-x, AMD-V). Xen uses a modified version of Qemu to emulate full PC hardware, including BIOS, IDE disk controller, VGA graphic adapter, USB controller, network adapter etc for HVM guests. CPU virtualization extensions are used to boost performance of the emulation. Fully virtualized guests do not require kernel support, so for example Windows operating systems can be used as Xen HVM guest. Fully virtualized guests are usually slower than paravirtualized guests, because of the required emulation.
-Full hardware virtualization requires only a disk image to execute in. Then a HV config file needs to be created. Samples are available from the /etc/xen directory. Here is an [{{SERVER}}/slax/download/win7 example] running in a X window for Windows 7. The main config options to modify are :
+Full hardware virtualization requires only a disk image to execute in. Then a HV config file needs to be created. Samples are available from the /etc/xen directory. Here is an [{{SERVER}}/wikislax/download/win7 example] running in a X window for Windows 7. The main config options to modify are :
   # Initial memory allocation (in megabytes) for the new domain.

@@ Line 17: / Line 17: @@
 * in paravirtualization (PV) guest operating systems are modified so they are able to interlock with Xen without emulation or virtual emulated hardware. Xen PV guest kernels exist for Linux, NetBSD, FreeBSD, OpenSolaris and Novell Netware. Upstream kernel.org Linux kernels since Linux 2.6.24 include Xen PV guest (domU) support based on the Linux pvops framework, so every upstream Linux kernel can be automatically used as Xen PV guest kernel without any additional patches or modifications.
-Paravirtualization requires storing the kernel to boot in the dom0 filesystem, and populating the system in a virtual partition. The kernel generated must be able to manage [http://wiki.qemu.org/download/qemu-doc.html#QEMU-PC-System-emulator the QEMU devices] and include the .config file [http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs#Configuring_the_kernel domU options]. Here is a minimal example of such a [{{SERVER}}/slax/download/config-domU .config domU] file. The swap partition and VM filesystem can be created as below. Don't forget to update the root device in fstab :
+Paravirtualization requires storing the kernel to boot in the dom0 filesystem, and populating the system in a virtual partition. The kernel generated must be able to manage [http://wiki.qemu.org/download/qemu-doc.html#QEMU-PC-System-emulator the QEMU devices] and include the .config file [http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs#Configuring_the_kernel domU options]. Here is a minimal example of such a [{{SERVER}}/wikislax/download/config-domU .config domU] file. The swap partition and VM filesystem can be created as below. Don't forget to update the root device in fstab :
   # dd if=/dev/zero of=pv-sl12.swap bs=1024k count=1024