1903?

On 2019-05-13 04:07, T wrote:
Any rumors on 1903 yet?

Tried it on my embedded development system (Windows home version).
It blocked _ALL_ my virtual machines (Virtualbox and VMware).
Apparently Hyper-V was triggered and that was not compatible.
Rolled back to 1803 - still same problem.
Tried reinstalling virtual machines - won't run.
Switched to using WSL - at least that did work (and runs FAST).
Now waiting for virtual machine provider update fixes...

Arie.

Arie de Muynck wrote:
On 2019-05-13 04:07, T wrote:
Any rumors on 1903 yet?

Tried it on my embedded development system (Windows home version).
It blocked _ALL_ my virtual machines (Virtualbox and VMware).
Apparently Hyper-V was triggered and that was not compatible.
Rolled back to 1803 - still same problem.
Tried reinstalling virtual machines - won't run.
Switched to using WSL - at least that did work (and runs FAST).
Now waiting for virtual machine provider update fixes...

Arie.

Why did you leave SLAT/EPT turned on in the BIOS ?

If you leave it turned off, Hyper-V can never leap up
and take a bite out of your VMs.

The way this works, is Hyper-V on Windows Server OSes,
does not rely on SLAT/EPT. Whereas Windows 10 Home
or Windows 10 Pro, your CPU needs SLAT/EPT and it
has to be turned on in the BIOS, before you can
use Hyper-V.

Paul

Arie de Muynck wrote:

On 2019-05-13 04:07, T wrote:

Any rumors on 1903 yet?

Tried it on my embedded development system (Windows home version).
It blocked _ALL_ my virtual machines

Hadn't tried virtualbox since 1903 upgrade, but it hangs starting an
existing Win7 VM, I see a virtual box 6.0.8 upgrade but it doesn't
specifically mention 1903 fixes ...

On 2019-06-01 19:46, Paul wrote:
Arie de Muynck wrote:
On 2019-05-13 04:07, T wrote:
Any rumors on 1903 yet?

Tried it on my embedded development system (Windows home version).
It blocked _ALL_ my virtual machines (Virtualbox and VMware).
Apparently Hyper-V was triggered and that was not compatible.
Rolled back to 1803 - still same problem.
Tried reinstalling virtual machines - won't run.
Switched to using WSL - at least that did work (and runs FAST).
Now waiting for virtual machine provider update fixes...

Arie.

Why did you leave SLAT/EPT turned on in the BIOS ?

If you leave it turned off, Hyper-V can never leap up
and take a bite out of your VMs.

The way this works, is Hyper-V on Windows Server OSes,
does not rely on SLAT/EPT. Whereas Windows 10 Home
or Windows 10 Pro, your CPU needs SLAT/EPT and it
has to be turned on in the BIOS, before you can
use Hyper-V.

Â*Â* Paul

It is probably left on in the BIOS because I did not know anything about
it. The laptop is a MSI GP63 8RD-007NL (a game machine - never used for
gaming but bought for the fast i7 hexcore CPU, large memory etc.) I
never changed the BIOS except to turn off the irritating keyboard LED
lighting effects. Maybe the BIOS had SLAT/EPT default enabled?
Thanks for the tip - I'll start studying and investigating. Hopefully I
can still recover from this deadlock.

Regards,
Arie

On 2019-06-02 08:50, Andy Burns wrote:
Arie de Muynck wrote:

On 2019-05-13 04:07, T wrote:

Any rumors on 1903 yet?

Tried it on my embedded development system (Windows home version).
It blocked _ALL_ my virtual machines

Hadn't tried virtualbox since 1903 upgrade, but it hangs starting an
existing Win7 VM, I see a virtual box 6.0.8 upgrade but it doesn't
specifically mention 1903 fixes ...


So, same as here. Also tried an upgrade, then a roll-back of virtualbox,
both not working.
I guess we'll have to wait for the VM provider, or Mickey$oft, to fix
this... Unfortunately I need the machine working NOW...

Arie