i have hyperV server running on which , i have just created a windows server 2008 virtual machine, where in that virtual machine network adapter is not detected. how to solve this problem.
#kaustubh93 Try installing a LEGACY network adapter. For machines as old as Win2K8 Server, the default network adapters may not work (did not for me), but installing a Legacy adapter did the trick.
This fix (using a Legacy adapter) worked this evening on a Windows 10 Pro installation running Hyper-V Client. I'd installed a Windows 7 Pro VM, but it wouldn't access the Internet via the Virtual Switch (external). Once I installed the legacy NIC, I had Internet access from within the VM.
Windows 2008 R2 is essentially Windows 7 anyway, so this solution is likely to work for you as well.
Jeff W.
Reading, PA
To add a network adapter
Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager.
In the results pane, under Virtual Machines, select the virtual machine that you want to configure.
In the Action pane, under the virtual machine name, click Settings.
In the navigation pane, click Add Hardware.
On the Add Hardware page, choose a network adapter or a legacy network adapter.
Click Add. The Network Adapter or Legacy Network Adapter page appears.
Under Network, select the virtual network you want to connect to.
If you want to configure a static MAC address or virtual LAN identifier, specify the numbers you want to use.
Click OK.
More : technet troubleshooting
Related
I want to connect WinDbg to the Windows Server kernel running on a Microsoft Azure platform VM to debug some drivers. I tried to follow the instructions on msdn to connect the debugger over the network, but it seems that requires that the target machine and the host are locate in one local network. What are the options, is it possible to do it at all?
I tried:
Setting Up Network Debugging of a Virtual Machine - KDNET
The problem is solved. It was necessary to add a new rule for the port used by the kernel debugger. This is done in the virtual machine settings in the "Network" section.
I'm trying to deploy a UWP app from my Alienware 18, Laptop with Windows 10, version 1803 to a Tablet Galaxy TabPro S with Windows 10 version 1803 as well.
I had activated developer mode on the device target and the USB device discovery option as well.
First I tried connecting a USB Cable from my laptop to the tablet which has a USB-C port.
But My laptop doesn't even find it.
What I want is to find a way to deploy a UWP from my laptop to the tablet, I made some research and I found out that, only HoloLens and Windows Phone 10, are findable using USB Connection.
So what step should I follow to successfully remote debug my app to a windows 10 Tablet.
I would appreciate details because I tried to follow remote deploying but I haven't been able to successfully find the tablet.
The Windows 10 on your tablet, just like on your development machine, supports remotely debugging over the network rather than over USB. Make sure both machines are in developer mode, with the other machine also having Device Discovery turned on as described here. Both should connect to your WiFi as a private network. After that it should be as simple as configuring your project to deploy to the other machine, rather than locally, as described here and here. Don't forget to pair them with a PIN.
If you host a web API on your development machine, configure your firewall as described here.
Use remote debugging over at https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging?view=vs-2017
Make sure you follow the instructions, sometimes remote debugging is barred by firewall so check that.
Alternative right click your main project, go to store then click create packages for sideloading and then send the package over at your Samsung device.
So what step should I follow to successfully remote debug my app to a windows 10 Tablet.
To run a UWP app on a remote machine, you must attach to it using the Remote Tools for Visual Studio.
In some scenarios, the remote tools are automatically installed when you deploy to a remote device. For example,
For Windows 10 PCs running Creators Update and later versions, remote tools will be installed automatically.
Then, your remote device and the Visual Studio computer must be connected over a network or connected directly through a USB or Ethernet cable. Debugging over the internet is not supported.
After that, you need to configure the Visual Studio project for remote debugging. In the properties of the project, select the Debug and choose the Remote Machine from the Target Device list. In general, I will input the remote machine's IP address, you could choose Find to choose the device from the Select Remote Debugger Connection dialog box.
Next step, please move to your Tablet, you need to Set up the remote debugger. You must have administrative permissions on the remote computer. Then, open the Start menu and search for Remote Debugger. If you could find it, just start it normally. If you cannot find it, you need to install it Remote Tools manually. See this link to Download and Install the remote tools. Once the Remote Debugger started, you could do some configurations. After that, you could choose Start Debugging on the Debug menu (Keyboard: F5). The project is recompiled, then deployed to and started on the remote device. Please read Run UWP apps on a remote machine in Visual Studio for more information.
I’m trying to set up automatic driver deployment and debugging to test a win 8.1 driver from Visual Studio 2013.
Host machine:
Win 7
VS2013
Target Machine:
Win 8.1
My host machine is set up with 2 network cards, 1 which connects to the corporate network and one spare. The target machine also has a network adapter.
My question is: is it possible to set up automatic deployment and debugging of drivers in Visual studio 2013 by connecting the host and target via a LAN whilst still being connected to the corporate domain and if not, is there a way of debugging wdk drivers on a target pc outside of visual studio, maybe via another application?
The documentation I found here only makes it seem possible by connecting to the same domain name or workgroup.
link to documentation
Many Thanks
Yes you can set up automatic deployment of the driver as well as getting visual studio to do the provisioning of the target pc over a local network as well as being connected to a corporate domain.
Admin rights are needed on the target
An extra ethernet card is needed in the host
All networks connections on the target are open with printer and file sharing options enabled
The ip and name of the target are listed in system32/etc/host in the host PC
A switch is needed and DHCP setting are enable with automatic IP
A good place to start:
https://msdn.microsoft.com/en-us/library/windows/hardware/gg507680.aspx
EDIT:
Basically, this was a nightmare and started dropping its connection. I reverted back to using WinDBG using:
custom scripts to copy everything over to USB
devcon to automactially load the driver
WinDBG to autoload appropriate settings on startup and load source files in to debug
Host: Visual Studio 2012, Windows 8 Host, WDK8
Target: VirtualBox - Windows 7
When I try to add the target computer (Driver -> Test -> Configure Computers) in Visual Studio (like at http://msdn.microsoft.com/en-us/library/windows/hardware/hh439359%28v=vs.85%29.aspx ):
I select "Provision Computer and choose debugger settings"
I choose to use a Serial connection
But the result is always "Could not find a host entry for Name of VM"
VS gives the same response if I try to connect through the network (I know kernel debugging from a Win8 host to a Win7 target isn't supported through the network).
I can't see a problem in the connection; connection without provision works after hitting Debug -> Break (otherwise, I hit a Waiting to reconnect... message).
Anyone get this working or has better idea on how to debug the Windows OS in VirtualBox?
You should not choose the debugger option to provision the target, as the debugger docs state that "Provisioning is not supported for virtual machines." (See this page: Provision a computer for driver deployment and testing.) This is most likely because provisioning requires network connectivity to the target, no matter how you choose to connect for the actual kernel debugging session.
As you've already observed, connection without provisioning works just fine, so you can just do that instead. Make sure you've properly attached the virtual serial port on the target to a host named pipe.
In any case, provisioning isn't strictly necessary to run the kernel debugger. It's just a convenience that automatically enables kernel debugging on the target, makes some other useful configuration changes, and installs a set of useful tools. You can see what provisioning does on this page: What happens when you provision a computer?
Here is some general guidance on setting up kernel debugging of a VM: Setting Up Kernel-Mode Debugging of a a Virtual Machine in Visual Studio
This link Kernel-Mode Debugging in a VM using Visual Studio 2012describes how to provision to virtual machine. You will need to configure network in a way that host and guest can ping each other.
After that you need to update "hosts" on both computers(add ip and NetBIOS of guest to host "hosts" file and ip and NetBIOS of host to guest "hosts" file).
I am currently using Windows Server 2008 Standard and have several Hyper V machines. These are development VM's and I want to now switch back Vista x64 because I am missing Aero.
I know Windows Server 2008 can have aero but the host performance is very very bad when I run VM in Hyper V.
I want to export my Hyper V machines so that I can use it in Virtual PC. Anyone know an easy way?
If you have built them as Hyper-V machines, I don't think you can go back. There are serious differences in the HAL for Virtual PC and Hyper-V. You can move a VPC to Hyper-V permanantly by removing the VPC add-ins ans adding the Hyper-V integration drivers/services and re-detecting the hardware.
A VPC can run in Hyper-V just fine, don't add the machine drivers for Hyper-V and you can go back to VPC with no problem.
VPC to Hyper-V is one way.
Hyper-V is designed to be used on the server, obviously. Whereas VirtualPC is designed for the end user. Hyper-V will give you more control, and the ability to create and restore snapshots. However, it does not have a direct console interface to the VM, you would use a browser to access the console. I would go Hyper-V, but it really depends on what you're using your VMs for. Luckily, they share the same format for virtual disks, so you can try it out with your existing VMs.
You should review Windows 2008 R2 SP1 upgrade with RemoteFX, it comes with a new video driver for VM's that allow 3D, extended desktops and more. It will help resolve some of the issues you are seeing today.
Both the Host server and VM need to be running SP1 of Windows 2008 R2.
http://blogs.technet.com/b/virtualization/archive/2010/03/18/explaining-microsoft-remotefx.aspx