2.1.0 problems

missilesilo · Post by **missilesilo** » 23. Dec 2008, 18:56

I have a couple problems with 2.1.0

If I have Intel-VT checked on my Windows XP virtual machine guest, I can't start any of my other VMs, even though none of the other ones have VTX enabled. I have to disable Intel-VT on every VM to be able to run more than 1 machine.

Also, I am no longer able to connect to a virtual network adapter that I created before in 2.0.6. I don't see how to create one either. I want the guest and the host to have a static IP address so I can communicate with the guest while I am not on the internet.

Are these bugs or am I just retarded? I have reverted back to 2.0.6 for now.

lespaul20 · Post by **lespaul20** » 23. Dec 2008, 22:12

I have the same issue with the AMD-V enabled. Not sure how to get around it.

2.1 uses the host interface. You don't need a virtual interface anymore. Just choose your primary interface as your host interface.

Post by **Sasquatch** » 24. Dec 2008, 20:35

If you want a Host <> Guest communication only, like on 2.0.6 and before, you can install the MS loopback interface and select that as Host Interface.

As for the AMD-v/VT-x, you have to have it enabled or disabled on all the VMs, you can't have it enabled on one VM and disabled on the other.
If it doesn't work properly, check your hardware to make sure it's fully supported and if it is (should be, else you won't have that option), file a bug report in the Bugtracker. You need a separate account for it though.