janhoedt
asked on
VMware Workstation & Hyper-V Windows 2008
Hi,
I'm using my home pc mainly with VMWare workstation as primarely tool on Windows 7 64 BIT.
Now I would like to be able to work on the home pc when I'm not home, so I make a vpn and connect to it. However my wife uses the pc too, so I want to install Windows 2008 so we can work with multiple users on 1 pc. Furthermore: the pc would be always on so Windows 2008 is more stable (Windows 7 isn't that for me).
I won't use hyper-v since I like my vm's and hyper-v has issues with wireless (it's a laptop) & NAT: I cannot give my hyper-v machines an address on the local LAN when connected to wireless (opened a different ticket for this, just doesn't work)
Practical questions:
-is there a way to activate & de-activate Hyper-V "on the spot" (without rebooting)? I might want to use hyper-v just playing around
-my wife should be using a vmware workstation (Windows 2008 would be stupid to use + it's only for hosting my vm's) and so do I, can I startup VMWare workstation vm's on the same Windows 2008 she is working on, under another account or will this give issues (I won't touch the vm she is working on)?
-is there a remote console alike for VMWare workstation (as the server version or the ESX, which I have tried both but workstation stays favorite for home use)?
-can I take over the session of my wife (not RDP but really take over the screen) to help her in case she has issues with a built-in (Windows 2008) session (not tools like logmein or other), is it the mstsc /console?
Thanks,
J.
I'm using my home pc mainly with VMWare workstation as primarely tool on Windows 7 64 BIT.
Now I would like to be able to work on the home pc when I'm not home, so I make a vpn and connect to it. However my wife uses the pc too, so I want to install Windows 2008 so we can work with multiple users on 1 pc. Furthermore: the pc would be always on so Windows 2008 is more stable (Windows 7 isn't that for me).
I won't use hyper-v since I like my vm's and hyper-v has issues with wireless (it's a laptop) & NAT: I cannot give my hyper-v machines an address on the local LAN when connected to wireless (opened a different ticket for this, just doesn't work)
Practical questions:
-is there a way to activate & de-activate Hyper-V "on the spot" (without rebooting)? I might want to use hyper-v just playing around
-my wife should be using a vmware workstation (Windows 2008 would be stupid to use + it's only for hosting my vm's) and so do I, can I startup VMWare workstation vm's on the same Windows 2008 she is working on, under another account or will this give issues (I won't touch the vm she is working on)?
-is there a remote console alike for VMWare workstation (as the server version or the ESX, which I have tried both but workstation stays favorite for home use)?
-can I take over the session of my wife (not RDP but really take over the screen) to help her in case she has issues with a built-in (Windows 2008) session (not tools like logmein or other), is it the mstsc /console?
Thanks,
J.
ASKER
No, the hole point is that I have access to Vmware workstation to stop start pauze take snapshots install delete clone vm s.
So create a host of a Windows OS, with a VM inside for Hyper-V. There is no console for VMware Workstation, you would need to connect to host to control VMs.
Back specially to yout questions:-
1. -is there a way to activate & de-activate Hyper-V "on the spot" (without rebooting)? I might want to use hyper-v just playing around
No.
2. -my wife should be using a vmware workstation (Windows 2008 would be stupid to use + it's only for hosting my vm's) and so do I, can I startup VMWare workstation vm's on the same Windows 2008 she is working on, under another account or will this give issues (I won't touch the vm she is working on)?
Yes, if you set them up as shared VMs.
3. -is there a remote console alike for VMWare workstation (as the server version or the ESX, which I have tried both but workstation stays favorite for home use)?
No. (VMware Server 2.0.2 has this function, designed for use on Servers, and now discontinued.)
4. -can I take over the session of my wife (not RDP but really take over the screen) to help her in case she has issues with a built-in (Windows 2008) session (not tools like logmein or other), is it the mstsc /console?
Yes, connecting to the console using RDP, but you didn't want to do that. I'm a little confused here because mstsc is the Remote Desktop Connection client.
Back specially to yout questions:-
1. -is there a way to activate & de-activate Hyper-V "on the spot" (without rebooting)? I might want to use hyper-v just playing around
No.
2. -my wife should be using a vmware workstation (Windows 2008 would be stupid to use + it's only for hosting my vm's) and so do I, can I startup VMWare workstation vm's on the same Windows 2008 she is working on, under another account or will this give issues (I won't touch the vm she is working on)?
Yes, if you set them up as shared VMs.
3. -is there a remote console alike for VMWare workstation (as the server version or the ESX, which I have tried both but workstation stays favorite for home use)?
No. (VMware Server 2.0.2 has this function, designed for use on Servers, and now discontinued.)
4. -can I take over the session of my wife (not RDP but really take over the screen) to help her in case she has issues with a built-in (Windows 2008) session (not tools like logmein or other), is it the mstsc /console?
Yes, connecting to the console using RDP, but you didn't want to do that. I'm a little confused here because mstsc is the Remote Desktop Connection client.
You can not nest Hyper-V inside another virtualization layer. Hyper-V must run directly on the hardware. You can nest VMware products inside a VM running under Hyper-V.
ASKER
The answer is: Vmware workstation 8!
VMware Workstation with the correct additional VMX functions will allow nested Hypervisors.
ASKER
Ok, now my VMWare workstation 8 is configured on a Windows 2008 OS.
I have an account which my wife logs into and one for me (Windows 2008).
Now I would like her to work on a VM (not via RDP, this has disadvantages such as she won't know what happens if pc need reboot/hangs). Shared vm's exist in Workstation 8 and this looks nice, but it's to much trouble to explain her to start vmware workstation, set it to full screen etc.
So I wondered if there is a way to let her work in an easy way with this vmware workstation:
-vmware player? tried it, but machine can only be runned in vmware workstation (where I run it as automatic so it runs at boottime), not both in player AND workstation
-RDP: no option, as mentioned before
-could there be a cmd-line which opens the vmware-workstation full-screen?
Note: issue that I had: bridged network did not work when machine is shared, however NAT works ... very strange (machine worked fine, untill I shared it, then only "limited access" was possible, ip is fine (dchp), pings are fine .....
Thanks for your input.
J.
I have an account which my wife logs into and one for me (Windows 2008).
Now I would like her to work on a VM (not via RDP, this has disadvantages such as she won't know what happens if pc need reboot/hangs). Shared vm's exist in Workstation 8 and this looks nice, but it's to much trouble to explain her to start vmware workstation, set it to full screen etc.
So I wondered if there is a way to let her work in an easy way with this vmware workstation:
-vmware player? tried it, but machine can only be runned in vmware workstation (where I run it as automatic so it runs at boottime), not both in player AND workstation
-RDP: no option, as mentioned before
-could there be a cmd-line which opens the vmware-workstation full-screen?
Note: issue that I had: bridged network did not work when machine is shared, however NAT works ... very strange (machine worked fine, untill I shared it, then only "limited access" was possible, ip is fine (dchp), pings are fine .....
Thanks for your input.
J.
you can use the vmrun command to start a VM.
But I still think personally, this will be awkward for a user of a computer.
This is the vmrun command manual, the vrun commands syntax has been the same since version 5.5 and VMware Server.
http://www.vmware.com/pdf/vix162_vmrun_command.pdf
But I still think personally, this will be awkward for a user of a computer.
This is the vmrun command manual, the vrun commands syntax has been the same since version 5.5 and VMware Server.
http://www.vmware.com/pdf/vix162_vmrun_command.pdf
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is kind of helpfull but now I need an extra installation whereas there is already a VMWare Workstation AND player installed .... VSphere is the same as Workstation, only other interface. Workstation works with shared vm. I'd have to explain her VSphere Client (haven't tried it yet) and probably isn't much difference (I'll give it a try).
---
Note about VMWare & Hyper-V: you CAN run VMWare Workstation & Hyper-V on same machine, but not at the same time. However you can simply mulitboot:
http://social.msdn.microsoft.com/Forums/en-US/servervirtualization/thread/e9c72bc8-c48d-453b-9f33-143114adecee/
For all these problems I found a simple solution of booting Windows Server 2008 without the hypervisor by creating an extra entry in the boot loader. Here's how:
At the command prompt, type the following:
bcdedit /copy {default} /d "No Hypervisor"
The above command should say: The entry was successfully copied to {guid}.
Copy that guid to the clipboard including the curly braces.
Now, type the following command:
bcdedit /set {guid} hypervisorlaunchtype off
In the above command, replace {guid} with what you copied in step 2. The
above command just sets a property in the boot entry that will not load
the hypervisor on boot.
That's it. If you now boot your machine you will get a boot menu with an extra option.
---
Note about VMWare & Hyper-V: you CAN run VMWare Workstation & Hyper-V on same machine, but not at the same time. However you can simply mulitboot:
http://social.msdn.microsoft.com/Forums/en-US/servervirtualization/thread/e9c72bc8-c48d-453b-9f33-143114adecee/
For all these problems I found a simple solution of booting Windows Server 2008 without the hypervisor by creating an extra entry in the boot loader. Here's how:
At the command prompt, type the following:
bcdedit /copy {default} /d "No Hypervisor"
The above command should say: The entry was successfully copied to {guid}.
Copy that guid to the clipboard including the curly braces.
Now, type the following command:
bcdedit /set {guid} hypervisorlaunchtype off
In the above command, replace {guid} with what you copied in step 2. The
above command just sets a property in the boot entry that will not load
the hypervisor on boot.
That's it. If you now boot your machine you will get a boot menu with an extra option.
ASKER
Notes:
-would it also (VCenter client) work with VSphere Client 4? Have a already copy of that.
-to what should I connect, the shared vm doesn't work bridged (the others do) as mentioned in post, so there is no public ip to connected to (can't connect to NAT-address)
-would it also (VCenter client) work with VSphere Client 4? Have a already copy of that.
-to what should I connect, the shared vm doesn't work bridged (the others do) as mentioned in post, so there is no public ip to connected to (can't connect to NAT-address)
vSphere is not the same as Workstation, it's a bare metal type 1 hypervisor.
As originally stated in my first responsed, Hyper-V and Workstation will not co-exist. I'm aware you can make the Boot Menu change, to prevent Hyper-V from working.
But in your first question you state:-
is there a way to activate & de-activate Hyper-V "on the spot" (without rebooting)? I might want to use hyper-v just playing around
The simple answer to this is use VMware Workstation with nested hypervisors.
As originally stated in my first responsed, Hyper-V and Workstation will not co-exist. I'm aware you can make the Boot Menu change, to prevent Hyper-V from working.
But in your first question you state:-
is there a way to activate & de-activate Hyper-V "on the spot" (without rebooting)? I might want to use hyper-v just playing around
The simple answer to this is use VMware Workstation with nested hypervisors.
vSphere Client is the same, although version 5.0 client may have some added compatibility for VMware Workstation 8.0, as they were released at roughly the same time.
You connect to the VMware Workstation 8.0 Host IP address.
You connect to the VMware Workstation 8.0 Host IP address.
ASKER
ok
Why not install Windows 2008 or Windows 7 64 bit, and create two VMs:-
1. Windows 7 for Wife
2. Windows 2008 with Hyper-V to play with. (nested Hypervisors can be accomplished).
If your host has enough resources, you will be able to run two VMs, but you will need to Access via RDP.
Yes, you can connect to the console.