VirtualBox to Hyper-V conversion
-
Well since that didn't work, have you tried Disk2VHD from within the VM?
-
@DustinB3403 said:
Well since that didn't work, have you tried Disk2VHD from within the VM?
That I have not tried. Was trying to stay focused on doing the conversion from within VirtualBox.
Does Disk2VHD even work on a Linux box?
-
I didn't know this was a Linux VM.
Um. not sure if it does or does not work on Linux....
-
@DustinB3403 said:
I didn't know this was a Linux VM.
Um. not sure if it does or does not work on Linux....
My fault. I forgot to put that in the body of the OC. I added it.
-
The screen shot above kind of gave it away that the VirtualBox session was Linux,
-
@Dashrender enough outta you...
Try this guide
http://www.hurryupandwait.io/blog/creating-a-hyper-v-vagrant-box-from-a-virtualbox-vmdk-or-vdi-image
-
@BBigford said:
It is supposed to have a GUI,
did the process for the GUI launch?
and even the CLI has no commands that are executable.
Not sure what you mean? if you type ls it doesn't show up on the command line? Sounds like a console problem. that would be like the keyboard isn't working on a baremetal install.
-
@BBigford said:
@DustinB3403 said:
Well since that didn't work, have you tried Disk2VHD from within the VM?
That I have not tried. Was trying to stay focused on doing the conversion from within VirtualBox.
Does Disk2VHD even work on a Linux box?
I thought Dustin was suggesting that you run disk2VHD inside VirtualBox - that's the VM he's talking about - I think.
-
This post is deleted! -
@Dashrender said:
@BBigford said:
It is supposed to have a GUI,
did the process for the GUI launch?
and even the CLI has no commands that are executable.
Not sure what you mean? if you type ls it doesn't show up on the command line? Sounds like a console problem. that would be like the keyboard isn't working on a baremetal install.
If you type something like hostname, it comes back as unrecognized. That same thing happens with any command.
-
@Dashrender said:
@BBigford said:
@DustinB3403 said:
Well since that didn't work, have you tried Disk2VHD from within the VM?
That I have not tried. Was trying to stay focused on doing the conversion from within VirtualBox.
Does Disk2VHD even work on a Linux box?
I thought Dustin was suggesting that you run disk2VHD inside VirtualBox - that's the VM he's talking about - I think.
Yeah the Linux box is the VM. I think Dustin thought maybe I was using a Windows VM. The screenshot is of the VM in Hyper-V booting (RHEL).
-
@BBigford said:
@Dashrender said:
@BBigford said:
It is supposed to have a GUI,
did the process for the GUI launch?
and even the CLI has no commands that are executable.
Not sure what you mean? if you type ls it doesn't show up on the command line? Sounds like a console problem. that would be like the keyboard isn't working on a baremetal install.
If you type something like hostname, it comes back as unrecognized. That same thing happens with any command.
So it booted - but now any command you type comes back as unrecognized? Sounds like a corrupt something.. weird that it could boot though.
Can you show a screen shot of the error when you type the command ls? -
@Dashrender said:
@BBigford said:
@Dashrender said:
@BBigford said:
It is supposed to have a GUI,
did the process for the GUI launch?
and even the CLI has no commands that are executable.
Not sure what you mean? if you type ls it doesn't show up on the command line? Sounds like a console problem. that would be like the keyboard isn't working on a baremetal install.
If you type something like hostname, it comes back as unrecognized. That same thing happens with any command.
So it booted - but now any command you type comes back as unrecognized? Sounds like a corrupt something.. weird that it could boot though.
Yeah. I think I'll just tell him he's going to be rebuilding it. The multiple screens acts funny on his computer sometimes if I remember right.
-
It was acting funny on my computer even before the conversion. Dual screens, 1 was black 1 was a GUI. You had to click somewhere in the black screen to get it to interact in the other screen. That magically went away (I didn't do anything but just reboot the machine a few times). Doesn't seem stable enough to dump more time into it.
