Closed Karl-WE closed 1 year ago
Hyper-V Guest Support is not available in 0.2. It has however already been implemented in the latest actions and will be supported in the next release.
Fixed in 0.3.0, Right now if it's really needed use the actions one.
Thank you for your quick responses. The wizard does not find an updated playbook when using Atlas.Playbook.22H2.v0.2.apbx. As a remediation I restored the VM snapshot and ran it again disabling the autostart.
I've executed the script as admin in the configuration Hyper-V / VBS, but that just threw an error that the component store is corrupted. Haven't checked but it 0.3.0 available in the releases so far?
Thank you for your quick responses. The wizard does not find an updated playbook when using Atlas.Playbook.22H2.v0.2.apbx. As a remediation I restored the VM snapshot and ran it again disabling the autostart.
I've executed the script as admin in the configuration Hyper-V / VBS, but that just threw an error that the component store is corrupted. Haven't checked but it 0.3.0 available in the releases so far?
https://github.com/Atlas-OS/Atlas/actions/runs/5109914724, latest playbook action as of this message
that action has expired anyone want to attach it here?
pardon @GhostlyCrowd ?
@notdido thanks for the link, I am missing how to download this as a new playbook file. Thanks for your guidance.
pardon @GhostlyCrowd ?
@notdido thanks for the link, I am missing how to download this as a new playbook file. Thanks for your guidance.
What I meant is that action build expired, so you cannot download the playbook file it made. I was hoping you had grabbed it already and could attach it to the bug report so i could grab a copy.
@PencilNavigator
I can confirm .30 does boot on hyper-v now but the dynamic resolution and multi monitor is broken this is because of the removal of the "Microsoft remote display adapter" driver
And all of the remote desktop stuff, which makes the host os unable to optimally communicate with the guest os (Atlas) like copy and paste, dynamic resolution, sound and so forth.
Plea to Filter all drivers by Hyper-V and leave them alone.
Should be now fixed.
Description
I have evaluated AtlasOS in a Hyper-V VM but it does not seem to work. This is likely because you disable Hyper-V by default and it needs to be enabled manually before rebooting the system after the wizard succeeded.
Steps to reproduce (add screenshots if applicable)
Expected behavior
the runbook should detect if hyper-v is enabled or it is a hyper-v vm and ask if it should be disabled (same as you did with cpu mitigations.
Actual behavior (add screenshots if applicable)
Atlas Version
Atlas 10 22H2
Desktop information
intel i5 11600k (2 vCores Core for the VM) 64 GB (8 GB static virtual RAM for the VM)
Requisites
Additional content
if this is intended behaviour, and my guessing is correct please consider converting it to a feature request in the playbook / wizard.