qvm-create not creating a volume large enough on --root-copy-from a raw disk image...

[Marc Boschma]

I'm having trouble creating a HVM windows machine from a raw disk image (conversion of a VirtualBox VM).

The image is 132GB, but qvm-create only creates a root volume of 10G.

I've googled and looked at the documentation and there doesn't appear to be a property I can set to get the volume large enough.

I would have thought that the root volume would have been created to reflect the size of the image being used to build the VM?

Is it a bug or is there something I need to pass to the command to get the volume large enough?

Another option could be to extend the current root to a large enough size and then copy the disk over, but I have yet to work out how to do that. Pointers would be helpful.

Marc

[Sphere]

I'm not that experienced on Qubes yet but methinks you have to manually indicate a size large enough for that to fit before you put it in
so I suppose
qvm-grow-root win7new 150g

[Marc Boschma]

On Friday, 13 July 2018 18:56:24 UTC+10, Sphere wrote:
> I'm not that experienced on Qubes yet but methinks you have to manually indicate a size large enough for that to fit before you put it in
> so I suppose
> qvm-grow-root win7new 150g

I could do that, but then how do I get the raw image (re)copied onto the root disk? That isn't obvious.

[awokd]

cp raw.img /dev/mapper/qubes_dom0-vm--win7new--private

dd should also work. Picturing appropriate brightly coloured warning
labels are an exercise for the reader (i.e. be careful what volume you
overwrite with this approach).

[awokd]

More careful than me at least;

cp raw.img /dev/mapper/qubes_dom0-vm--win7new--root

would probably be a better idea.

[Marc Boschma]

On Friday, 13 July 2018 21:27:01 UTC+10, awokd wrote:

> More careful than me at least;

:)

> cp raw.img /dev/mapper/qubes_dom0-vm--win7new--root
>
> would probably be a better idea.

Coupled with R4 version of @Sphere's advise I managed to get the root enlarged and the image copied!

The disappointing thing is that windows didn't like the change in hardware change.

I might give up on the migration…

Thanks for advise.