qm importdisk, just sits there

[Manny Vazquez]

Hi,

I just finished a new cluster with 3 nodes. All seems fine, launched a few containers and all works fine, now I wanted to move a virtualbox vm from my pc to the proxmox .

So, I created a new vm (102), 2x2 cpu, 4gb ram and the stadard 32gb hd. Detached and removed the disk.
SCP the VDI file over to /dev/zvol/rpool/data named clonewin.vdi

issued the command
qm importdisk 102 clonewin.vdi local-zfs

And NADA.. it just sits there . The node went from .2 cpu to about 4% cpu .. but I see no progress.

Yesterday I tried the same with a .img file and the node rebooted by itself after like 20 minutes..

Any ideas? What is the safest, less stress to move a virtualbox vm to proxmox 5.3?

 

[wolfgang]

Hi,

vdi format is not supported by the importer.

only qcow2, raw and vmdk

What is the safest, less stress to move a virtualbox vm to proxmox 5.3?

convert your image to one of the formats above.

 

[Manny Vazquez]

In my previous post I mention that I tried a .img (created via the VBoxManage convertdd command) file the day before and the node actually rebooted by itself after doing nothing to the import for over 20 minutes.

I also tried "qemu-img convert -f vdi -O raw clone.vdi windows.img" and same result, after 30 minutes I control C since it was not showing any progress any where..

Is there anything that is missing on my installation?

when I run apt-get update I get this.

==========================================
root@pve1:~# apt-get update

Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.us.debian.org/debian stretch InRelease
Hit:3 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:4 http://ftp.us.debian.org/debian stretch Release
Ign:6 https://enterprise.proxmox.com/debian/pve stretch InRelease
Ign:7 https://enterprise.proxmox.com/debian/pve stretch Release
Ign:8 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:11 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en_US
Ign:8 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:11 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en_US
Ign:8 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:11 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en_US
Ign:8 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:11 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en_US
Ign:8 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:11 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en_US
Ign:8 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Err:9 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages

401 Unauthorized

Ign:10 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:11 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en_US

Reading package lists... Done

W: The repository 'https://enterprise.proxmox.com/debian/pve stretch Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/stretch/pve-enterprise/binary-amd64/Packages 401 Unauthorized

E: Some index files failed to download. They have been ignored, or old ones used instead.

root@pve1:~#
===============================================================

 

[Manny Vazquez]

I have tried both ways now.
with
qm importdisk 102 mydisk.vmdk local-zfs

and with
qemu-img convert -f vmdk -O qcow2 mydisk.vmdk newwin.qcow2


with the import, nothings, just sits there.. with the convert, it created a little file (see image) almost immediately and then just sat there.
No progres in a while so I killed the process.



I was reading all over and found report of qemu-img convert hanging on systems with large number of cps/cores.. could this be related? if so, how do I go around?
Will this be a problem for proxmox itself?

 

[Lucian]

Try to put a -p after convert, to show progress indicator, ie:
qemu-img convert -p -f vdi -O raw clone.vdi windows.img

 

[Manny Vazquez]

Thanks, now I can see 0% .. no change in behavior.
I tried first again with
qemu-img convert -p -f vmdk -O qcow2 mydisk.vmdk newwin.qcow2

and then with
qemu-img convert -p -f vmdk -O raw mydisk.vmdk newwin.img



It just sits there are 0%, even that 2 different files were created (one for each process) and the qcow2 was very little the other one had the full 80gb .


Good thing this is just a test, I do not really need to move this windows box over to proxmox, since it is what I use locally on my mac when I need windows. But, I am afraid this is going to happen again when I try to move the now physical boxes to proxmox. I do not want to have to reinstall all the physical servers, it is easier (and cheaper in licenses) if I just move the physicals to VMs.

Any other idea?

 

[Lucian]

Try to convert the vdi on the virtualbox side, using their tools, then import the raw file.
It's possible qemu vdi support is not so good.

 

[Manny Vazquez]

Try to convert the vdi on the virtualbox side, using their tools, then import the raw file.
It's possible qemu vdi support is not so good.

That is what I did first, not sure if related or not but the node rebooted after no progress in about 20 minutes.

I am now trying clonezila over network (source-destination mode), it seems to be working.
Again, this is mostly a lab, to make sure I can move physical machines to this new cluster.



I'll post results .. or failures.. lol

 

[Manny Vazquez]

This way worked perfectly fine. The imported machine works fine.

I am concerned with the importdisk tool .. etc.. but I can't fix it.

 

[Lucian]

The fact that the machine rebooted on its own is not good. Either RAM or PSU problems...
I would leave it a while running a tool such as "stress" before production, make sure it doesn't succumb to high CPU or RAM usage.

 

[Manny Vazquez]

Can you point to any tool in particular?
I have run this server already with a few VMs and has not happened again but of course, cpu usage never got over 25%. With the import that it rebooted, cpu only got to 4%. And with all the new attempts also to about 4% and did not reboot.

 

[Lucian]

apt-get install stress

 

[Manny Vazquez]

Great , thanks , I was not aware of this tool ..

I have put all 3 nodes on a 75% load for 2 hours.. Let's see.