Qubes-R4.0 : missing argument to qvm-create

[gdr...@gmail.com]

Hi,

I'm trying to run the following command:

$ qemu-img convert -O raw *.vmdk win10.raw
$ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > /home/user/win10-root.img
$ qvm-create --hvm win10 --label red --mem=4096 --root-move-from /home/user/win10-root.img

qvm-create: error: unrecognized arguments: --hvm --mem=4096

Source : https://www.qubes-os.org/doc/hvm/

How to create a new PVH instead of HVM in Dom0 with the root image from R4.0 ?

Thank you so much for your help.

Best regards.

[Ivan Mitev]

On 08/30/2018 11:10 AM, gdr...@gmail.com wrote:
> Hi,
>
> I'm trying to run the following command:
>
> $ qemu-img convert -O raw *.vmdk win10.raw
> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > /home/user/win10-root.img
> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from /home/user/win10-root.img
>
> qvm-create: error: unrecognized arguments: --hvm --mem=4096
>
> Source : https://www.qubes-os.org/doc/hvm/

You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc.

The following command should do the trick:

qvm-create win10 \
--class StandaloneVM \
--property virt_mode=hvm \
--property kernel='' \
--label=red \
--property memory=4096 \
--property maxmen=4096 \
--root-move-from /home/user/win10-root.img

[GDRUB]

Thank you for those explanations.

However, Windows 10 fails with error code : 0xc0000225 "a required
device isn't connected or can't be accessed".

win10.raw = 96.6 GB

How to fix this error ?

[Ivan Mitev]

On 08/30/2018 11:43 PM, GDRUB wrote:
> Thank you for those explanations.
>
> However, Windows 10 fails with error code : 0xc0000225 "a required
> device isn't connected or can't be accessed".
>
> win10.raw = 96.6 GB
>
> How to fix this error ?

Sorry, no idea...

(PS: please do not top post)

[brenda...@gmail.com]

I think the issue of > 10GB images being truncated via ---root-copy-from during create still exists. See this Issue is still open in the tracker:

https://github.com/QubesOS/qubes-issues/issues/3422

You'll likely need to qvm-create w/o the root-copy-from, then qvm-grow-root, then copy the image to the right volume listed in /dev/mapper.

See this thread (and choose commands wisely!):

https://groups.google.com/forum/#!topic/qubes-users/vBk-jjvoeT0

Brendan

[GDRUB]

Hi Brendan,

It seems to be the solution to this problem.

I'll test this with caution.

[GDRUB]

missing binary in PATH ! :-(

$ qvm-grow-root win10 100g

bash : qvm-grow-root : command not found

[Ivan Mitev]

qvm-grow-root is a R3.2 command, on R4.0 you have to use `qvm-volume`:

https://www.qubes-os.org/doc/resize-disk-image/#expand-disk-image-r40

eg.:

qvm-volume resize win10:root 100G

[Alain BERNARD]

Sorry : qvm-volume extend <vm_name>:root <size>

[GDRUB]

Your solution worked like a charm.

I still have some difficulty with two issues :

1) in the panel of Qubes Manager,  state indicator is yellow -
something's not ok. That's troubling to me.

2) to get Windows HVM into real full screen mode. The procedure is
carried out correctly (https://www.qubes-os.org/doc/full-screen-mode/)
but Fullscreen stays grayed out into windows bar