Problem with viBoot + Windows Hyper-V


Author
Message
icotonev
icotonev
New Member
New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)
Group: Forum Members
Posts: 4, Visits: 46


Hello .. What do you think is due to the problem with the message in the picture. Please for opinion and recommendations ..! Thanks in advance..!
I apologize in advance for bad English ..!


jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)
Group: Forum Members
Posts: 4.3K, Visits: 31K
You should be able to fix that by doing this:

- Open the Hyper-V Manager application.
- Right-click the VM that was created through viBoot and select Settings.
- Select Checkpoints and uncheck "Enable checkpoints".  Click OK.

Your VM should now be able to start from Hyper-V Manager or viBoot without displaying that error message.  I'm not sure why checkpoints aren't disabled automatically as part of the viBoot wizard though.  Checkpoints can't be used if viBoot is using pass-through disks.

icotonev
icotonev
New Member
New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)
Group: Forum Members
Posts: 4, Visits: 46
Thanks for the reply..! But unfortunately it did not get ..! Now another error is generated ..! Apparently I can not handle it regretfully ..! Something to confuse ..!







jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)
Group: Forum Members
Posts: 4.3K, Visits: 31K
Open Task Manager on your system and click the Performsnce tab, then click Memory. If you don’t see the Performance tab, click “More details” first. How much available memory is shown there, and how much memory did you select for your VM? You should make sure that even after you start your VM your system will still have at least 1GB free.
icotonev
icotonev
New Member
New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)
Group: Forum Members
Posts: 4, Visits: 46
When Virtual Machine is turned on, Task Manager Productivity is 1.1 GBWhen Virtual Machine is turned on, Task Manager Productivity is 1.1 GB
icotonev
icotonev
New Member
New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)
Group: Forum Members
Posts: 4, Visits: 46
Sorry, I will not be able to use viBoot + Windows Hyper-V ..! There is no memory ... Unfortunately my laptop is Lenovo L 540 is weak for this function .. Thank you for your help and assistance.

Edited 26 August 2018 2:13 PM by icotonev
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)Macrium Evangelist (6.2K reputation)
Group: Forum Members
Posts: 4.3K, Visits: 31K
The reason those numbers are the same is because the virtual machine isn't turning on, as you can see. How much total memory does your system have available (not in use) when the virtual machine is off, and how much memory did you choose to allocate to the virtual machine in viBoot? Again, the memory allocation in the virtual machine should be small enough that you will still have at least 1GB available even AFTER the virtual machine powers on.  So for example if your system is showing 3GB of memory available while the virtual machine is off, you should only configure the virtual machine to use 2GB of memory.  If you do not have enough available memory to allocate at least 2GB to the virtual machine, you will probably see slow performance from the virtual machine.  In that case, you would need to install more memory on your system so that you can increase the virtual machine's memory allocation

Edited 26 August 2018 2:16 PM by jphughan
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search