configure network to communicate between two Virtual Machines.

V

vikas027

Bit poster
Hi all,

I am using Dell Latitude D610 Laptop.

I have installed Parallels Workstation for windows Version 2.2 Build 2204. I need to install two Solaris 10 OS and have connectivity between them.

The setting for network Adapter is Bridged Ethernet and I have chosen my LAN adapter "Broadcom NetXtreme 57xx Gigabit Controller - Packet Scheduler Miniport". Also, I have tried giving default adapter also. But still I am not getting options to give IP in the virtual OS, I am not even able to recognize my network interface. Generally, network interface is shown while booting.

Anyone can help me out please.

Thanks in advance,
Vikas
 
Hello everyone,

I need a solution for this issue as well. Our configuration is somewhat similar, in that there's a host and 2 virtual machines running on it simultaneously. The host OS is Windows Vista Business and running in VMs are a Fedora Core 4 (no xwin, just httpd, samba and ssh) and a Windows XP Professional (for IE6 monkey testing). I need to be able to get from the XP VM to the FC4 VM via http. I can ping the FC4 VM just fine, but whenever I try to connect over http, ssh or anything for that matter, it just times out. I turned off the firewall on both VMs, so that's definitely not it.

The FC4 VM httpd (Apache) is accessible from both the host and other computers on the network, but not the secondary VM. Both VMs connect to the internet and can see the rest of the network, just not each other.

Thank you in advance,
Vasile.
 
To connect a virtual machine to a virtual network, you add a virtual network adapter to the virtual machine and then connect the virtual network adapter to an existing virtual network. There are two types of network adapters available for Hyper-V: a network adapter and a legacy network adapter.

The network adapter is designed specifically for Hyper-V and requires a virtual machine driver that is included with the Hyper-V integration services. This type of networking adapter provides better performance than a legacy network adapter and is the recommended choice when it can be used. Because this type of virtual network adapter requires integration services in the guest operating system, it can be used only with guest operating systems for which integration services are available.
The legacy network adapter emulates an Intel 21140-based PCI Fast Ethernet Adapter. This type of network adapter provides networking capabilities for two scenarios: when using a guest operating systems for which integration services are not available, and when network boot capabilities are required. The legacy network adapter uses a driver that is available in most operating systems, instead of a Hyper-V specific driver. The legacy network adapter also provides the ability to boot to the Pre-Boot Execution Environment (PXE).
 
You must log in or register to reply here.
Back
Top