From 0dc2f7d5173970ad5555dc888ac8202c35e359cf Mon Sep 17 00:00:00 2001 From: Alex Dubois Date: Fri, 9 Feb 2018 10:22:56 +0000 Subject: [PATCH 1/7] windows VM qvm-prefs should be HVM and no kernel --- managing-os/hvm.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/managing-os/hvm.md b/managing-os/hvm.md index 1632a84d..117c2beb 100644 --- a/managing-os/hvm.md +++ b/managing-os/hvm.md @@ -40,7 +40,7 @@ The name of the domain ("win7") as well as its label ("green") are just exemplar **Note:** It is unnecessary for Qubes 4 users to pass in the `--hvm` switch. To create a StandaloneVM in Qubes 4, use the --class option, as VMs are template-based by default: ~~~ -qvm-create win7 --class StandaloneVM --label green +qvm-create win7 --class StandaloneVM --property virt_mode=hvm --property kernel="" --label green ~~~ If you receive an error like this one, then you must first enable VT-x in your BIOS: @@ -53,9 +53,11 @@ Now we need to install an OS inside this VM. This can be done by attaching an i ~~~ qvm-start win7 --cdrom=/usr/local/iso/win7_en.iso +or +qvm-start win7 --cdrom=TempIsoVM:/home/user/win7.iso ~~~ -The above command assumes the installation ISO was transferred to Dom0 (copied using `dd` command from an installation CDROM for example). If one wishes to use the actual physical media without copying it first to a file, then one can just pass `/dev/cdrom` as an argument to `--cdrom`: +The above first command assumes the installation ISO was transferred to Dom0 (copied using `dd` command from an installation CDROM for example). The second is for when the iso is in another VM. If one wishes to use the actual physical media without copying it first to a file, then one can just pass `/dev/cdrom` as an argument to `--cdrom`: ~~~ qvm-start win7 --cdrom=/dev/cdrom From f1a01822610e9ba64ceaab732b664661bb0b0aef Mon Sep 17 00:00:00 2001 From: Alex Dubois Date: Fri, 9 Feb 2018 13:15:33 +0000 Subject: [PATCH 2/7] Windows 64bit requires 2GB of RAM minimum --- managing-os/hvm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/managing-os/hvm.md b/managing-os/hvm.md index 117c2beb..558442d9 100644 --- a/managing-os/hvm.md +++ b/managing-os/hvm.md @@ -40,7 +40,7 @@ The name of the domain ("win7") as well as its label ("green") are just exemplar **Note:** It is unnecessary for Qubes 4 users to pass in the `--hvm` switch. To create a StandaloneVM in Qubes 4, use the --class option, as VMs are template-based by default: ~~~ -qvm-create win7 --class StandaloneVM --property virt_mode=hvm --property kernel="" --label green +qvm-create win7 --class StandaloneVM --property virt_mode=hvm --property kernel="" --property memory=2048 --label green ~~~ If you receive an error like this one, then you must first enable VT-x in your BIOS: From 9a8cb3e642e2ee7a538aaacaeddc02d46ac06675 Mon Sep 17 00:00:00 2001 From: Alex Dubois Date: Fri, 9 Feb 2018 14:14:08 +0000 Subject: [PATCH 3/7] 2GB is not sufficiant. 4GB required. --- managing-os/hvm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/managing-os/hvm.md b/managing-os/hvm.md index 558442d9..82cd8197 100644 --- a/managing-os/hvm.md +++ b/managing-os/hvm.md @@ -40,7 +40,7 @@ The name of the domain ("win7") as well as its label ("green") are just exemplar **Note:** It is unnecessary for Qubes 4 users to pass in the `--hvm` switch. To create a StandaloneVM in Qubes 4, use the --class option, as VMs are template-based by default: ~~~ -qvm-create win7 --class StandaloneVM --property virt_mode=hvm --property kernel="" --property memory=2048 --label green +qvm-create win7 --class StandaloneVM --property virt_mode=hvm --property kernel="" --property memory=4096 --label green ~~~ If you receive an error like this one, then you must first enable VT-x in your BIOS: From 3ccf0dd09daba83ff1a6ffca634ccb76154bb40a Mon Sep 17 00:00:00 2001 From: Alex Dubois Date: Fri, 9 Feb 2018 18:00:25 +0000 Subject: [PATCH 4/7] Windows for R4 documentation --- managing-os/hvm.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/managing-os/hvm.md b/managing-os/hvm.md index 82cd8197..66d207db 100644 --- a/managing-os/hvm.md +++ b/managing-os/hvm.md @@ -37,10 +37,11 @@ qvm-create win7 --hvm --label green The name of the domain ("win7") as well as its label ("green") are just exemplary of course. -**Note:** It is unnecessary for Qubes 4 users to pass in the `--hvm` switch. To create a StandaloneVM in Qubes 4, use the --class option, as VMs are template-based by default: +**Note:** To create a StandaloneVM in Qubes 4, use the --class option, as VMs are template-based by default ~~~ -qvm-create win7 --class StandaloneVM --property virt_mode=hvm --property kernel="" --property memory=4096 --label green +qvm-create win7 --class StandaloneVM --property virt_mode=hvm --property kernel="" --property memory=4096 --property maxmem=4096 --property debug=True --label green +qvm-features win7 video-model cirrus ~~~ If you receive an error like this one, then you must first enable VT-x in your BIOS: From 31065b1daa024b1e2617b0fc83b70090637d9b4c Mon Sep 17 00:00:00 2001 From: Alex Dubois Date: Mon, 12 Feb 2018 05:52:03 +0000 Subject: [PATCH 5/7] Dom0 should be prepended with --cdrom option --- managing-os/hvm.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/managing-os/hvm.md b/managing-os/hvm.md index 66d207db..32971ea0 100644 --- a/managing-os/hvm.md +++ b/managing-os/hvm.md @@ -37,7 +37,7 @@ qvm-create win7 --hvm --label green The name of the domain ("win7") as well as its label ("green") are just exemplary of course. -**Note:** To create a StandaloneVM in Qubes 4, use the --class option, as VMs are template-based by default +**Note:** To create a StandaloneVM in Qubes R4, use the --class option, as VMs are template-based by default ~~~ qvm-create win7 --class StandaloneVM --property virt_mode=hvm --property kernel="" --property memory=4096 --property maxmem=4096 --property debug=True --label green @@ -53,12 +53,12 @@ libvirt.libvirtError: invalid argument: could not find capabilities for arch=x86 Now we need to install an OS inside this VM. This can be done by attaching an installation ISO to and starting the VM (this can currently only be done from command line, but in the future we will surely add an option to do this also from the manager): ~~~ -qvm-start win7 --cdrom=/usr/local/iso/win7_en.iso -or qvm-start win7 --cdrom=TempIsoVM:/home/user/win7.iso +or +qvm-start win7 --cdrom=dom0:/usr/local/iso/win7_en.iso ~~~ -The above first command assumes the installation ISO was transferred to Dom0 (copied using `dd` command from an installation CDROM for example). The second is for when the iso is in another VM. If one wishes to use the actual physical media without copying it first to a file, then one can just pass `/dev/cdrom` as an argument to `--cdrom`: +The above first command assumes the installation ISO was transferred to a TempIsoVM (copied using `dd` command from an installation CDROM for example). The second is for when the iso is in Dom0, which is not recommanded. If one wishes to use the actual physical media without copying it first to a file, then one can just pass `/dev/cdrom` as an argument to `--cdrom`: ~~~ qvm-start win7 --cdrom=/dev/cdrom From f06944d0c5b40bc0e18b0d240ac80237f860adca Mon Sep 17 00:00:00 2001 From: Alex Dubois Date: Mon, 12 Feb 2018 06:58:28 +0000 Subject: [PATCH 6/7] fixed travis typo errors --- managing-os/hvm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/managing-os/hvm.md b/managing-os/hvm.md index 32971ea0..702251ec 100644 --- a/managing-os/hvm.md +++ b/managing-os/hvm.md @@ -53,12 +53,12 @@ libvirt.libvirtError: invalid argument: could not find capabilities for arch=x86 Now we need to install an OS inside this VM. This can be done by attaching an installation ISO to and starting the VM (this can currently only be done from command line, but in the future we will surely add an option to do this also from the manager): ~~~ -qvm-start win7 --cdrom=TempIsoVM:/home/user/win7.iso +qvm-start win7 --cdrom=DispVM:/home/user/win7.iso or qvm-start win7 --cdrom=dom0:/usr/local/iso/win7_en.iso ~~~ -The above first command assumes the installation ISO was transferred to a TempIsoVM (copied using `dd` command from an installation CDROM for example). The second is for when the iso is in Dom0, which is not recommanded. If one wishes to use the actual physical media without copying it first to a file, then one can just pass `/dev/cdrom` as an argument to `--cdrom`: +The above first command assumes the installation ISO was transferred to a DispVM (copied using `dd` command from an installation CDROM for example). The second is for when the iso is in Dom0, which is not recomended. If one wishes to use the actual physical media without copying it first to a file, then one can just pass `/dev/cdrom` as an argument to `--cdrom`: ~~~ qvm-start win7 --cdrom=/dev/cdrom From 222c58952277f094aaabeb354c2acfd9c315a550 Mon Sep 17 00:00:00 2001 From: Alex Dubois Date: Mon, 12 Feb 2018 07:08:03 +0000 Subject: [PATCH 7/7] typo grrr --- managing-os/hvm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/managing-os/hvm.md b/managing-os/hvm.md index 702251ec..e120b458 100644 --- a/managing-os/hvm.md +++ b/managing-os/hvm.md @@ -58,7 +58,7 @@ or qvm-start win7 --cdrom=dom0:/usr/local/iso/win7_en.iso ~~~ -The above first command assumes the installation ISO was transferred to a DispVM (copied using `dd` command from an installation CDROM for example). The second is for when the iso is in Dom0, which is not recomended. If one wishes to use the actual physical media without copying it first to a file, then one can just pass `/dev/cdrom` as an argument to `--cdrom`: +The above first command assumes the installation ISO was transferred to a DispVM (copied using `dd` command from an installation CDROM for example). The second is for when the iso is in Dom0, which is not recommended. If one wishes to use the actual physical media without copying it first to a file, then one can just pass `/dev/cdrom` as an argument to `--cdrom`: ~~~ qvm-start win7 --cdrom=/dev/cdrom