viBoot Onetimer?


Author
Message
Jools
Jools
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 16
Hello, I am trying resolve that issue:
Got image created by macrium, booting it with viboot on windows 10 pro with hyper-v, its starts, works fine but vm list in viboot is "deleted VM" only with attached image/images. It works only to first reboot of my Win10 pc. After that cant start/backup etc. from viboot menu. What the heck? Cant start in HYPER-V as well. Please help.



Nick
Nick
Macrium Representative
Macrium Representative (2.6K reputation)Macrium Representative (2.6K reputation)Macrium Representative (2.6K reputation)Macrium Representative (2.6K reputation)Macrium Representative (2.6K reputation)Macrium Representative (2.6K reputation)Macrium Representative (2.6K reputation)Macrium Representative (2.6K reputation)Macrium Representative (2.6K reputation)
Group: Administrators
Posts: 1.5K, Visits: 8.3K
Hi Jools

Thanks for posting. 

viBoot creates a temporary VM to test that images can be successfully booted using instant virtualisation. viBoot VM's do not persist after rebooting the host. 

but vm list in viboot is "deleted VM" only with attached image/images.


Is this after a host reboot? Can you please attach a screen shot if not?


Kind Regards

Nick - Macrium Support

Edited 8 June 2017 10:59 AM by Nick
Jools
Jools
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 16
Thanks for reply.
This state is just after create VM.
http://forum.macrium.com/uploads/images/ff3db82b-058d-44f1-a2be-3238.png

Mike A
Mike A
Macrium Representative
Macrium Representative (327 reputation)Macrium Representative (327 reputation)Macrium Representative (327 reputation)Macrium Representative (327 reputation)Macrium Representative (327 reputation)Macrium Representative (327 reputation)Macrium Representative (327 reputation)Macrium Representative (327 reputation)Macrium Representative (327 reputation)
Group: Forum Members
Posts: 133, Visits: 500
Hi Jools,

viBoot uses WMI to query Windows for VM's. It then maps VM's to mounted images. If there are mounted images that aren't mapped to VM's they are mapped to the "Delete VMs" entry to allow users to cleanly unmount images, etc... Could you please raise a support ticket so that your issue can be investigated further:

https://macrium.com/support

Thanks,

Mike.


Koky999
Koky999
New Member
New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)
Group: Forum Members
Posts: 1, Visits: 3
Hello, we have exactly the same problem on two PCs. Both running Windows 10 and after creating VM in viBoot and then booting, it changed to Deleted VM. But it is still in Hyper-V administration.
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