Hyper-V Problem?

[AMD Lover]

Sooo, whats this and how can I fix it. New to the whole virtual machine thing. Thanks

[AMD Lover]

Post has been fixed (Pictures added now)

[Altecice]

Nothing much to say, Enable it in the BIOS and away you go... Feel free to install VM's at your will.

 

----edit----

 

That looks like your VM is set to PXE boot (boot from network) this may be a setting from inside your Hypervisor.

[xox]

I'd make a start by using Virtualbox

 

Second point is make sure boot priority is set so that the Virtual Disk Image file is first in order.

[AMD Lover]

I'd make a start by using Virtualbox

 

Second point is make sure boot priority is set so that the Virtual Disk Image file is first in order.

 

 

Nothing much to say, Enable it in the BIOS and away you go... Feel free to install VM's at your will.

 

----edit----

 

That looks like your VM is set to PXE boot (boot from network) this may be a setting from inside your Hypervisor.

 

If I set my VM to run on a separate HDD does my ISO have to be on the separate HDD? 

[Altecice]

If I set my VM to run on a separate HDD does my ISO have to be on the separate HDD? 

 

I havent used Hyper-V much I tend to use Oracle virtual box, But id imagine your ISO can be mounted from any point.

[AMD Lover]

I havent used Hyper-V much I tend to use Oracle virtual box, But id imagine your ISO can be mounted from any point.

 

 

I'd make a start by using Virtualbox

 

Second point is make sure boot priority is set so that the Virtual Disk Image file is first in order.

 

Heres the settings

[xox]

Heres the settings

I'd simply install and use Virtualbox, less problems

[AMD Lover]

Yeah, I like how this is built in though. Also if I ever get into networking they're going to use Hyper-V not Virtualbox

 

Can't I just install the OS later after the VM is created?

[AMD Lover]

Tried extracting the setup file with WinRAR and it said it was corrupted. I'll download it again and go from there.

[Altecice]

Yeah, I like how this is built in though. Also if I ever get into networking they're going to use Hyper-V not Virtualbox

 

Can't I just install the OS later after the VM is created?

 

They don't, most company's use some form of stripped back level 1 hypervisor with CLI only. But yeah that looks the same as Vbox, just select the iso and you are good to go. 

[GoodBytes]

I like how people suggests to install Virtual Box an inferior VM for Windows OS.

Can you post all the configurations of Hyper-V, including the network card you made.

I believe you didn't create your network adapter correctly, where you created a legacy one.

[Eniqmatic]

I would delete the VM and re-create it, read each option this time, anyways can you post a screenshot of the harddrive menu?

[RH00D]

It looks like the VM is trying to boot from the network instead of disc image (.iso) or virtual hard drive. Just make sure that virtual disc drive is the first in the boot order and that the .iso is mounted to it, which it looks like you have from the 2nd screenshot you posted.

 

I can't recall but when its booting you might have to press a key to make sure it boots from virtual disc. Is it still giving you problems despite the settings being right?

[omniomi]

Based on the name of your vhdx and the iso I assume you're going to be running Windows 7? You've selected Generation 2 when creating your VM (you have SCSI controllers instead of IDE controllers and there's secure boot in your firmware options.) Gen 2 only works for Windows 8 and Windows Server 2012. You need to delete the VM, create a new one using Generation 1, and you'll be good to go.

 

 

Even if you were running a Gen 2 supported OS getting it to boot from an ISO the first time is a bit of a pain and I usually disable secure boot and remove PXE all together.

[GoodBytes]

*Sigh* So many replies... so little useful information.

Well the OP is keeping details secret. So we help so much, and only playing guess work. We all assume that the OP READ what he or she was doing, and not randomly picking options.

[omniomi]

Well the OP is keeping details secret. So we help so much, and only playing guess work. We all assume that the OP READ what he or she was doing, and not randomly picking options.

 

I deleted that line but my point was more towards the "switch to VirtualBox" people. Hyper-V is hardly my favourite virtualization product but I can tell you it's superior to VirtualBox. It's a bit like someone saying "hey guys, I can't get this action to work in Photoshop" and having a bunch of "you should use GIMP" replies... It just doesn't follow. 

[NumLock21]

I mostly use Gen 1 for better compatibility and less hassle. Also I want to use a physical DVD drive. Gen 2 doesn't support that.

[omniomi]

I mostly use Gen 1 for better compatibility and less hassle. Also I want to use a physical DVD drive. Gen 2 doesn't support that.

 

I use Gen 2 for Windows Server 2012/R2 VMs and so far haven't had any issues save for the earlier mentioned pain of getting it to boot from an ISO for the first time. My desk is in Canada and the farms I work in are spread across the US and the rest of the world, I'm not going to be popping DVDs into drives any time soon. For that reason the lack of physical disc drive support isn't a real concern to me; All of our Hyper-V clusters are built with or with access to an ISO share. 

 

There have been a few instances where I've had to build out Windows Server 2012 VMs on Gen 1 but the specifics of why escape me at the moment...

[Eniqmatic]

I deleted that line but my point was more towards the "switch to VirtualBox" people. Hyper-V is hardly my favourite virtualization product but I can tell you it's superior to VirtualBox. It's a bit like someone saying "hey guys, I can't get this action to work in Photoshop" and having a bunch of "you should use GIMP" replies... It just doesn't follow. 

 

Precisely! It's counter productive to offer that as advice, it's basically the lazy "solution".