[SOLVED] vm image file location & winserver import problem

[FPOlivier]

Hello
Sorry if my English is not perfect...

Here is my configuration:
-zfs raid1 with 2 250 Go ssd for the OS
-Zfs Raid5 with 5 1To HDD for datas

The install is fresh (yesterday).

When I create a vm, I can't find the file containing the hard drive of this vm.
I thought it would be in the data store created in zfs, as I configure the vm, but not file... But the vm is running....

Example: I create a vm vor ubuntu20.04 with a 50Go hdd. I thought I would fine a big file about 50Go or at least 3 - 4 Go related to this vm, but nothing...


Anyway, I wouldn't care about it if it's running well, but I need to import and convert vhdx vm and then I can't because I don't now where to import it.

Could you help me?
Many thanks

FPOlivier

 

[H4R0]

For zfs its a block device not a file.

e.g /dev/zvol/rpool/data/vm-100-disk-0

You can list them with "zfs list" to see how much space they use

You can mount them locally but only if the vm is offline.


https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#_importing_virtual_machines_and_disk_images

 

[FPOlivier]

Hi H4R0,

Thanks !
I had a look at my folder /dev/zvol/mydatafolder
I can see a file for my vm : vm-100-disk-0
but:
1)Its weight is very low : about 512o (or ko I don't know)
2)I can't see its extension ( raw, as I am in ZFS, I think)

Wouldn't this file be the weight of th installed vm?

 

[FPOlivier]

I ask because I really don't find wher my vm'sdisk is stored.
And then, when I'll convert/import my vhdx vm, I won't be able to store it in the good place.
Many thanks for your help

 

[FPOlivier]

Hello!

Would somebody have an idea to help me?

Many thanks

 

[FPOlivier]

I can find my vm's hdd :



But when I have a look on these 2 folders in MobaXterm, files are shown very small :


Thanks

 

[aaron]

These are not files but symlinks to other device paths where the block device is presented. When using ZFS as storage you just don't have files that you could copy around.

To import a disk, use the provided tools, such as qm importdisk [0][1].

For you it would probably look something like:
qm importdisk <vmid> /path/to/image.vhdx <storage name as shown in GUI>

[0] https://pve.proxmox.com/pve-docs/qm.1.html
[1] https://forum.proxmox.com/threads/converting-vhdx-to-raw.36354/#post-178353

 

[FPOlivier]

Thank you very very very much
explained like that, I understand immediatly (or even) why I didn't find my files

One question : my vm's disk does exist. so If it is not in a file, which kind of spiritual thing is it?
I'll try that way

Thanks a lot
Have a nice day

 

[aaron]

One question : my vm's disk does exist. so If it is not in a file, which kind of spiritual thing is it?

ZFS has two kinds of datasets. One that will show up as a regular file system and volumes, which are exposed as block devices to the system, such as your physical hard disk.

From the ZFS man page which you can read yourself if you run man zfs on the server.

A dataset can be one of the following:

file system A ZFS dataset of type filesystem can be mounted within the standard system namespace and behaves like other file systems. While ZFS file systems are designed to be POSIX compliant, known issues exist that prevent compliance in some cases. Applications that depend on standards conformance might fail due to non-standard behavior when checking file system free space.

volume A logical volume exported as a raw or block device. This type of dataset should only be used when a block device is required. File systems are typically used in most environments.

snapshot A read-only version of a file system or volume at a given point in time. It is specified as filesystem@name or volume@name.

bookmark Much like a snapshot, but without the hold on on-disk data. It can be used as the source of a send (but not for a receive). It is specified as filesystem#name or volume#name.

 

[FPOlivier]

ok
It's still a little obcious for me but I'll take time to learn it

Many thanks

 

[aaron]

Hehe, yeah it can be confusing when encountering it for the first time. It is owned to the fact that on unixoid systems, pretty much everything is exposed as a file(system).

Depending on the file type you can distinguish between regular files, symlinks, directories, block devices, and so on. It's the first letter in the `Access` column in your screenshot or you get the same when running ls -l on the CLI.

Wikipedia has an article about the most common file types: https://en.wikipedia.org/wiki/Unix_file_types

 

[FPOlivier]

Then:
I importer the vhdx => ok
but : when windows start, it comes on the blue screen with boot repair tool
When I run it, it tells it can't repair windows

So I followed a process I found in this forum :
1. Export the VM from HyperV, copy the VHDX file to Proxmox host storage.
2. Convert VHDX to RAW: qemu-img convert -f vhdx OSS-OWNCLOUD.vhdx -O raw /mnt/convert/occonverted.raw
3. Make a new VM, use its ID in the import disk command: qm importdisk 101 occonverted.raw local-lvm
4. Attach the disk to VM, also add an EFI Disk. Change BIOS mode to OVMF.
5. In OVMF BIOS, add an EFI boot entry to point to the efi loader on the disk.
https://forum.proxmox.com/threads/m...v-to-proxmox-qm-importdisk-boot-failed.63674/

But in the console, it shows:


I don't know what to do ?

 

[aaron]

Have you checked the boot order in the option panel of the VM?