Answered by:
[SOLVED] P2V Windows 2003 SP2 VM loses control after boot

-
Hi everyone,
Has anyone an idea on what to do in this case?
I did a P2V conversion in a Windows 2003 SP2 using Disk2vhd, the conversion concluded without any problem...
The Vm start normally on Windows 2012 R2 Hyper-V host. But at Windows login screen the mouse, keyboard and ctrl+alt+del doesn't respond.
I tried connect direct on the host console, the RDP session doesn't work either.
I tried everything, but the VM doesn't respond.
Regards,
Everton
- Edited by Everton_Weschenfelder Tuesday, February 14, 2017 3:37 PM
Question
Answers
-
Dave,
The question is solved. I've tested the VM on another hyper-v host and it worked well. So the problem was in my current hyper-v host, than I reinstalled it and now the VM is working well.
Thanks for the attention again.
Regards,
Everton Weschenfelder- Proposed as answer by Leo HanModerator Wednesday, February 15, 2017 1:30 AM
- Marked as answer by Everton_Weschenfelder Monday, March 20, 2017 6:59 PM
All replies
-
You will have to recall your keyboard skills (via console session) until you can get integration service installed on the guest.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
- Edited by Dave PatrickMVP Friday, February 10, 2017 7:46 PM
-
But you still might end up with problems. Remember that 2003 was written before virtualization became popular on the x86 platform. That means that it has no idea about running in a virtual environment. 2008 and later actually have changes made to them to recognize a virtual environment. As a result, 2003 has multiple things against when running in a virtual environment. One is what I just said. The other comes from trying to P2V it. If you spend some time searching through this forum, you will find lots of people who have had issues trying to get a P2V 2003 instance to run properly, particularly when using any of the free tools. Some of the tools that you pay for did a better job, but you still have the normal 2003 in a virtual environment issue.
If you really need to have 2003 in a virtual environment, you are better off to build the VM from scratch and re-install the applications.
. : | : . : | : . tim
-
-
You will have to recall your keyboard skills (via console session) until you can get integration service installed on the guest.
As Smjain said, I'll wait if the keyboard works after some time.
Thank you. -
But you still might end up with problems. Remember that 2003 was written before virtualization became popular on the x86 platform. That means that it has no idea about running in a virtual environment. 2008 and later actually have changes made to them to recognize a virtual environment. As a result, 2003 has multiple things against when running in a virtual environment. One is what I just said. The other comes from trying to P2V it. If you spend some time searching through this forum, you will find lots of people who have had issues trying to get a P2V 2003 instance to run properly, particularly when using any of the free tools. Some of the tools that you pay for did a better job, but you still have the normal 2003 in a virtual environment issue.
If you really need to have 2003 in a virtual environment, you are better off to build the VM from scratch and re-install the applications.
. : | : . : | : . tim
This is an old machine, with an old financial application installed (doesn't have support call anymore).
Thanks for the reply. -
So integration services got installed?
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. -
-
Then the input devices are not going to work. When you do the Action\Insert does the disk show up?
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. -
-
I'd look in My Computer for the integration services disk.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
- Edited by Dave PatrickMVP Monday, February 13, 2017 7:27 PM
-
-
Ok, did not know that. I'd probably try building a new one from ISO as a test to determine if the VM is corrupt.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.- Marked as answer by Everton_Weschenfelder Monday, March 20, 2017 6:58 PM
- Unmarked as answer by Everton_Weschenfelder Monday, March 20, 2017 6:58 PM
-
-
-
Dave,
The question is solved. I've tested the VM on another hyper-v host and it worked well. So the problem was in my current hyper-v host, than I reinstalled it and now the VM is working well.
Thanks for the attention again.
Regards,
Everton Weschenfelder- Proposed as answer by Leo HanModerator Wednesday, February 15, 2017 1:30 AM
- Marked as answer by Everton_Weschenfelder Monday, March 20, 2017 6:59 PM
-
-
Hi Everton,
Glad to hear the issue was solved.
You could mark the reply as answer to help others who met the same issue.
Best Regards,
Leo
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.