Context: System Center Virtual Machine Manager 2012 server and Hyper-V 2012 host
A couple of quick questions:
Are the following equivalent: guest agent, host agent and VMM agent?
What does the VMM agent do? It is required for communication b/w the VMM server and the host? I know that this is a basic question but believe it or not, I haven't been able to find an explanation online...
Thanks
-Rohan.
"Host agent" and "VMM agent" most likely refer to the "System Center Virtual Machine Manager Agent" service installed on a Hyper-V Host. "Guest Agent" is not as precise and rarely used, but probably means the set of Hyper-V services and devices installed on a guest VM as the "Hyper-V Integration Services".
From the "System Center: Virtual Machine Manager Engineering Blog" at Link
"As part of Hyper-V host addition, VMM installs an agent on the host machine. This agent communicates with the host using Windows Remote Management (WinRM) transport. We configure a listener for the ports that send and receive WS-Management protocol messages using either HTTP or HTTPS on any IP address"
From "Microsoft Hyper-V Integration Services" at Link
"Hyper-V Integration Services is a suite of utilities in Microsoft Hyper-V, designed to enhance the performance of a virtual machine's guest operating system. Hyper-V Integration Services optimizes the drivers of the virtual environments to provide end users with the best possible user experience. The suite improves virtual machine management by replacing generic operating system driver files for the mouse, keyboard, video, network and SCSI controller components. It also synchronizes time between the guest and host operating systems and can provide file interoperability and a heartbeat"
Host Agent is agent communication via SCVMM and the Hyper-v Host
Guest Agent sn Hyper-V Integration Services on the VM
VMM Guest is an agent deployed via VMM when provisioning a service
Related
After rebooting is it possible to open a Hyper-V virtual machine without going through the Manager? It seems like it is already running in the background or maybe it is just in its last state.
If the OS in the Hyper-V virtual allows for remoting and also it is on the same network as the attempt to open a remote desktop to that virtual.
Note that the default network adapter for a virtual will provide a different IP address than what the local network provides to the server. You will most likely want to create a network adapter (in Hyper-V) which shares the network card to the virtual and the virtual will get its IP address from the local network.
If you can ping it, then it can be remoted to..but other things within the virtual has to allow for remoting.
Upon reading the OPs comments, it is clear that the need is to launch the virtual outside of Hyper-V. Hyper-V uses VMConnect.exe to achieve that...and that is available.
One can do that in an elevated Powershell shell such as:
vmconnect {Local/remote computer name} {Virtual Name}
such as
vmconnect Hyperion W10-Zephyr
where Hyperion is the local computer name and W10-Zephyr is the virtual's name.
See also Connecting to Hyper-V virtual machines with PowerShell
I am working with an Ubuntu 18.04 virtual machine. I can SSH into this machine via puTTy on the same computer. However, how can I access this machine from another computer? Or do I have any option to set this machine as a cloud server so others can access and run it?
I think that would all depend on how the networking is configured on your VM.
You can configure the network as bridged (where the VM has it's own dedicated IP address on the local subnet), NAT (where the VM shares the IP with the system running Workstation, but NAT rules can be configured to handle traffic), or host-only (where only the system running Workstation is able to connect to it).
Bridged is probably the easiest to use for your situation.
More information on these networking configs: Common Networking Configurations for Workstation
I have been trying to setup a Win7 VM on Hyper-v that connects to the internet through my Win 8 host machine.
I can't seem to figure out why the VM can't ever get passed limited connectivity. Any ideas?
NO sure why but all I had to do was Disable/enable the vEthernet adapter and everything worked great!
Check that you have a Virtual Switch with an "External Network" using the Virtual Switch Manager.
The other network types offer VM isolation. If your VM is on an "Private Network" it can only talk to other VMs on the server. The "Internal Network" allows VMs can talk to other VMs and to the host.
In contrast, an External Network allows the VM to contact machines on the network that the host is attached to.
I worked on this issue for a while myself after upgrading to Windows 8.1 and losing connectivity. Added and removed the adapter to no avail. The solution was to upgrade the VM's Integration Services.
I had the same issue because my DHCP settings on my guest VM was setup wrong.
So check the DHCP setting if they are on obtain automatically.
Control Panel\Network and Internet\Network Connections
Network adapter properties -> Internet Protocol Version 4 (TCP/IPv4) -> Properties ->
Obtain DNS server address automatically
I have had great success with Hyper-V and windows 8 and windows 10 virtuals using external switches with a Windows 8.1 host. Unfortunately I could not get the external switch to ever work on windows xp virtual running under Hyper-V. Instead, after reading a lot of sites/suggestions, I followed this guide to bridge an internal virtual switch (with Hyper-V legacy network adapter for XP) to the host wifi. I hope this saves someone else some time when working on an XP virtual.
Using Hyper-V with a Wireless Network Adapter
I have a test environment that I host from my computer. I have configured an external switch so that it can be accessed by others.
If we take a look inside the Hyper-V Manager we can see that we have: "Hyper-V Manager" and under it we have connection to the local machine. We also have the possibility to add a new connection by connecting a server.
So can I host my PC's Hyper-V Instance as a server in the domain and would that make my peers able to connect to it as a new instance in their Hyper-V Manager?
Is it possible to share Hyper-V Manager or my instance of it, so that other people can use snapshots and the other functions that Hyper-V manager have to offer?
I'm thankful for all help!
Yes, it is possible for other users to manage your machines Hyper-V instance with Hyper-V Manager run on a different machine, as long as they have the correct privileges. Which I believe it's up to you or the domain admin to set.
Check out this blog post if it may help you. Good luck!
I am running windows server 2008 in vmware workstation and there I have installed sharepoint 2010.
How can I view a sharepoint site from my host machine, so from my windows 7?
Any ideas? Thank you
It depends on the network configuration you assigned to your VM. If you didn't isolate your VM, you should be able to ping it from your host (assuming they share the same network settings - subnet mask, gateway, ip class, ...) and access your SharePoint site from the host.
Also make sure that the native firwall on your server is allowing inbound / outbound connection with the relevant port (at least :80).
Cheers.