This video is now more than a year old. I hope people are still getting value from it. If you leave a message in 2024 or beyond, there is no guarantee I will see it right away. f you have questions about Proxmox, I would invite you to head over to the OFFICIAL Proxmox Forums which can be found here: forum.proxmox.com/
@idriss1070
16 күн бұрын
Hello, it does. Thank you very much :) Best regards from France
@Practical-IT
Жыл бұрын
I hope this helps out some of you who are coming from using VMWare or VirtualBox over to Proxmox VE. Thanks for watching!
@QuikTechSolutions
Жыл бұрын
Clear & to the point!
@aperrao
Жыл бұрын
great video Jeremy....very clear process. Thanks
@johnnyg3606
10 ай бұрын
This saved me a lot of time - thanks mate!
@Practical-IT
8 ай бұрын
Glad it helped
@natenielsen9531
4 ай бұрын
life saver!! thank you for posting this.
@Practical-IT
4 ай бұрын
I'm glad you found it useful. If you have any suggestions for improvements, I have been thinking about recording an updated version of this video.
@seifeeeeeeeeeeeeeeee
Жыл бұрын
Hi , I followed your guide step by step, except that I tried using one of my own .ova files that I have been using during my course. I have sucessfully imported it except it showed 2 errors: 1. "invalid host ressource /disk/vmdisk1, skipping" 2. the boot order doesn't show anything so I can't boot the O.S. any tips? ty in advance.
@Practical-IT
Жыл бұрын
Judging by the error message 1, it did not import your disk. Was the file extension a vmdk? It's not included in your message. Error 2 is directly related to error 1. If your disk was skipped on import, you won't have anything to select in the boot menu. The first thing I would do is go back to whatever you used to create the OVA file and repeat the process. You might also try the process on a known good OVA file such as one from Turnkey Linux. If that imports successfully following the process, they your OVA file from your course is not valid. If the OVA from TKL does not import successfully, then you need to further dig into whatever messages are coming up on screen and/or dig into system logs for more information. Without being able to try this problematic OVA file myself, this is the best advice I can give you.
@seifeeeeeeeeeeeeeeee
Жыл бұрын
@@Practical-IT Hi, thx for your quick reply. The original file was an .ova with a Linux Server O.S installed. on it, I decompressed it with tar like in the video and obtained the 3 files that form an ova (.ovf , .mf and the .vmdk). Then I imported the .ovf file and that error appeared I tried to edit the .ovf but I get the same error so I'm out of ideas. After posting my original message I tried the Turnkey ova with the same procedures and that worked with no issues. The 2nd error i figured it was related to error number 1 due to exploring the boot record on the Turnkey VM which actually showed the disk that I got an error from. I could link you the OVA if you are interested, though I understand if you say no to downloading a stranger's link.
@Practical-IT
Жыл бұрын
if the Turnkey OVA worked with no issues, that reinforces the idea that there is something wrong with your OVA with the Linux Server OS. How did you get this original OVA file? Did you create it yourself? What Virtualization platform was used to originally create the OVA (VirtualBox, VMWare [Player|Workstation|ESXi]? Do you have access to the original software to regenerate that OVA file? That might be the best option right now. When you extracted the OVA with tar, what was the size of the VMDK file? Is it a size that makes sense compared to the disk size when that VM was running? You're welcome to send me a link, but it will have to be via email. I have links turned off for comments. If you go to the About tab for the channel, there will be an option there to see an email address. I truly believe that there is something wrong with that original OVA file, and specifically with the VMDK file contained within it. I can't guarantee how quickly I will take a look at it, especially since I will be unavailable during the upcoming holiday weekend.
@seifeeeeeeeeeeeeeeee
Жыл бұрын
@@Practical-IT The file was given to us by our teacher to learn about Mysql, so i'm not the original creator. It was intented for Virtualbox since it was our primary tool to use virtual machines. When I extracted the .ova file the .vmdk has almost the same size, so I think it made sense. I had sent you the .ova file already via mail. There is no rush on checking it out, i'm just curious more than anything else since I'm doing a project about Proxmox and I might encounter the same problem in the future so it might come handy a way to fix it. Thank you!
@zzsql
8 ай бұрын
I've imported three ova files and each say "No boot device selected" under Boot Order of each VM. Google isn't being useful, any thoughts. I'm stuck and my class starts Tuesday : / qm importovf 108 filename.ovf local-lvm --format qcow2 qm importdisk 108 filename-disk002.vmdk local-lvm -format qcow2
@Practical-IT
8 ай бұрын
My first question would be where did you acquire the OVF from in the first place? Is this something that is known to be good? Is it from your professor/school? You may find this reference useful: www.techtarget.com/searchvmware/definition/open-virtualization-format-OVF Have you tried to repeat the steps in the video with an OVA obtained from Turnkey Linux and manually extracted to get to the OVF? What are the error messages that come up? If I had the error messages, I might be able to come up with something.
@zzsql
8 ай бұрын
@@Practical-IT Vulnhub. Metasploitable worked as did MX Linux but no other VM from Vulnhub worked, which actually what I needed most. I teach offensive cyber operations and want to build a lab with a ton of vulnerable VMs on my proxmox server but the best VMs aren't cooperating. None of the offending VMs have bootable devices although when I do a lsblk -f i see file -l /dev/mapper/pve-vm--107--disk--0. That's the number for the failing VM. 107. Any ideas?
@Practical-IT
8 ай бұрын
I downloaded Metasploitable 1 from Vulnhub, and the error I'm getting when I try to import the disk is: Metasploitable.vmdk: non-existent or non-regular file I did notice that these VMs are both VERY old, going back to 2010 and 2012. I tried Metasploitable 1 in VirtualBox, and got different error messages. You might consider using HacktheBox or something similar instead. 12 and 14 years are pretty old, and I do question the value that would be gained from using them. You might check the Proxmox forums, Spiceworks or Reddit to see if anyone has any other ideas, or might be able to export a working copy of these machines into a newer OVA format. There is a Metasploitable 3 that requires some work to setup. It is based on Windows Server 2008, which again is pretty old and not supported any more. I wish I could be more help.
@zzsql
8 ай бұрын
@Practical-IT Alright. I'll figure it out. Aren't such config contained in the accompanying XML files? Maybe I can add the boot device strings to fix it.
@Practical-IT
8 ай бұрын
If you do figure it out, I would be happy to know the solution.
@jeanphilippeHamon
Жыл бұрын
Dear Jeremy, Thanks for this video - Do you make it for me with command lines ? 😀 Have a good days, Best regards,
@ronm6585
Жыл бұрын
Thanks Jeremy.
@Gobertron
Жыл бұрын
love this video thank you, removed all the fluff and BS. thank you again @!!
@Practical-IT
Жыл бұрын
Glad it helped!
@benelli22
8 ай бұрын
thanks!
@syskiessistemasit7448
Жыл бұрын
bash: qm: command not found ??? Need to install some more??
@Practical-IT
Жыл бұрын
Are you running the qm command from the Proxmox server? In >5 years of running Proxmox, I have never seen a command not found when trying to use the qm command.
@marcioantunes3332
Жыл бұрын
would you like to do something with xenserver/xcp for proxmox on windows machines?
@Practical-IT
Жыл бұрын
I'm not sure I understand your question. Xenserver/xcp-ng and Proxmox are two different products, and I really don't use Windows that much.
@cbbcbb6803
Жыл бұрын
Could you demonstrate usend turnkey Linux with VirtualBox?
@Practical-IT
Жыл бұрын
What exactly do you want to see as far as Turnkey and Virtualbox? I've already got these videos: • TurnKey WordPress Appliance in Virtualbox: kzitem.info/news/bejne/0o5vx4iEiqGii6g • TurnKey Bittorrent Appliance in Virtualbox: kzitem.info/news/bejne/q5CwyY6QpXucgaQ • TurnKey Mattermost Appliance in Virtualbox: kzitem.info/news/bejne/t22tl66Pb5N9jag • TurnKey Domain Controller in Virtualbox: kzitem.info/news/bejne/sYOLu6mOpqZ3lm0 The install for any given TurnKey appliance has not changed, but if something in particular is giving you issues, please be specific.
@gezginbsezgin4619
Жыл бұрын
perfect
@jeffreyschlieve590
Жыл бұрын
I really like the straight forward video. I did run into a problem. I used an OVA from NextCloud I used there AIO and I got this error "" warning: unable to parse the VM name in this OVF manifest, generating a default value invalid host ressource /disk/vmdisk1, skipping ''' I am still googleling for the answer. I see that TurnKey has their own NextCloud image, gonna try that as well. Again thank you for your time on the video, was straight forward and to the point.
@Practical-IT
Жыл бұрын
I haven't tried the NextCloud OVA file on Proxmox. I might have to give it a try and see if I can discover a way to make it work. Push come to shove, installing it on VirtualBox and then using Rescuezilla to create a backup image that can be restored on Proxmox might work.
@MrAndroid2013
9 ай бұрын
I got the following error.. "qemu-img: Could not open '/tmp/virtualmachine.vmdk': Invalid footer could not parse qemu-img info command output for '/tmp/virtualmachine.vmdk' - malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "(end of string)") at /usr/share/perl5/PVE/Storage/Plugin.pm line 946" Absolutely lost. I was reading that this would need to be converted from a vmdk to a flat image then imported, but I have no luck finding how to do that yet.
@Practical-IT
9 ай бұрын
Can you post the original command you used when you got the error? Also, did you start from a vmdk, or did you start from an OVF as shown in this video? If you just had the VMDK and not an OVM, this video may be more helpful. kzitem.info/news/bejne/ooqamJqwoH5_aJwsi=gvAqNoumJPjJzEMe You can also check the Proxmox forums: forum.proxmox.com If you search for "malformed json string" or other parts of your error message, you might be able to find something that will help.
Пікірлер: 37