Windows Forum / Virtual PC / March 2008
Porting physical drive issues.
|
|
Thread rating:  |
Jack - 08 Mar 2008 21:25 GMT I am giving up. After 7 days of tweaking I have enough. I used Acronis True Image Echo Workstation with Acronis Universal Restore and I have tried these 2 methods: A. Create a physical drive image, convert it to virtual disk and mount it. B. Create a physical drive image and restore it directly inside VPC.
Host: Windows XP PRO 3 MB RAM 1. physical Windows XP: ------------------------ method A never succeeded. ---> tried 5 times method B after hard trying: - booting Normal failed - booting Safe failed - booting Last working configuration ---> worked????? but virtual machine is not operative. Any Windows action (opening window) takes 5-7 minutes!!! and booting itself takes about 30 minutes until the last start-up app get loaded 2. physical Vista -------------- method A and method B both fail the same way. There is some hard drive activity at bootup and then bootup freezes. Using Safe mode the last loaded entry is: crcdisk.sys and booting stops. There is not boot log created, despite selecting "boot with logging" option. I used Vista DVD installation disk to repair it. It find few areas and repaired them but that did not help booting.
Conclusion: ======== Do not waste your time. It is not worth.
If you have any experience porting XP or Vista physical drives and you succeeded and your vm are working normally I invite you to share your experience. Jack
Robert Comer - 08 Mar 2008 21:45 GMT >If you have any experience porting XP or Vista physical drives and you >succeeded and your vm are working normally I invite you to share your >experience. I've never tried restoring Vista into a VM, but I've done a physical XP box to VM more than once.
Back up box with Acronis True Image Restore to a VM using True Image with Universal restore Boot into safe mode in VM the first time, reboot, install VM additions, reboot, done.
>B. >Create a physical drive image and restore it directly inside VPC. That's basically what I did, but I copied the image to an existing VHD using another VM and restore from that.
> but virtual machine is not operative. Any Windows action (opening window) >takes 5-7 minutes!!! and booting itself takes about 30 minutes until the >last start-up app get loaded Install the VM Additions. How much RAM are you allocating to the VM?
 Signature Bob Comer
>I am giving up. >After 7 days of tweaking I have enough. [quoted text clipped - 37 lines] >experience. >Jack Jack - 08 Mar 2008 22:21 GMT RAM allocated to guest 1.2 GB VM additions installed. XP non-operative. I wonder if the hardware installed on host can influence porting. I have a video capture PCI card and 2 modems installed on host. Robert, how did you do that:
> That's basically what I did, but I copied the image to an existing VHD > using another VM and restore from that. Please elaborate. What I did it was very labourous way. First installed WinXP from CD and created 2 partition during installation. Then copied image file to the second partition. Then restarted with Acronis bootable disk (iso) and restored image to c:\
Jack
> >If you have any experience porting XP or Vista physical drives and you >>succeeded and your vm are working normally I invite you to share your [quoted text clipped - 64 lines] >>experience. >>Jack Robert Comer - 09 Mar 2008 01:35 GMT >RAM allocated to guest 1.2 GB That's too much, back it down to 512M to start and raise it until it start slowing down.
>I wonder if the hardware installed on host can influence porting. If you use Universal restore, it's not supposed to as it sets XP to a state that it should detect the hardware correctly.
>I have a video capture PCI card and 2 modems installed on host. That should matter, the Video capture card isn't passed through, so XP shouldn't try to load the driver, and modems shouldn't ever cause a problem like that, even if they had a special serial port. You might be able to use them in the VM...
>Robert, how did you do that: >> That's basically what I did, but I copied the image to an existing VHD >> using another VM and restore from that. >Please elaborate. I created a new VHD, attached it to a working VM, and copied it from the host using a normal networking share. (as apposed to shard folders which is a feature of VPC) Then shut down that VM, created a new VM and VHD, Also attach the VHD from the step before, booted from the Acronis CD and restored.
>First installed WinXP from CD and created 2 partition during installation. >Then copied image file to the second partition. >Then restarted with Acronis bootable disk (iso) and restored image to c:\ That sounds as if it's basically what I did, except I already had a working VM to do the copy. I don't see anything wrong with doing it that way, except maybe how did you do the copy?
>Then restarted with Acronis bootable disk (iso) and restored image to c:\ Are you sure you're using the Universal restore option? On the Acronis menu it's a separate option than a normal true Image restore.
 Signature Bob Comer
>RAM allocated to guest 1.2 GB >VM additions installed. [quoted text clipped - 80 lines] >>>experience. >>>Jack Jack - 08 Mar 2008 22:28 GMT One thing more. How did you install VM Additions in Safe mode? That is impossible on my system. The error message is: "The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode or...." ??? Jack
> >If you have any experience porting XP or Vista physical drives and you >>succeeded and your vm are working normally I invite you to share your [quoted text clipped - 64 lines] >>experience. >>Jack Jack - 08 Mar 2008 22:42 GMT Ok. Ignore this. You did not install additions in Safe mode. My mistake.
> One thing more. > How did you install VM Additions in Safe mode? [quoted text clipped - 73 lines] >>>experience. >>>Jack Robert Comer - 09 Mar 2008 01:37 GMT >How did you install VM Additions in Safe mode? You can't, I did that after rebooting. (That's a Windows installer problem I don't particularly care for.)
 Signature Bob Comer
>One thing more. >How did you install VM Additions in Safe mode? [quoted text clipped - 73 lines] >>>experience. >>>Jack Jack - 09 Mar 2008 04:09 GMT I've found the source of problem why guestXP was soooooo slow. It was Symantec NAV. I have unistalled it from Control Panel (it took about 2 hours to complete that task!) Now it is normal. I am confused about all these options Acronis offers. On bootable disk (iso) I have at least 2 restore options involving Universe Restore. One is so called 'Safe' and another 'full install'. I do not have any clue which is for what. (I tried both anyway). Jack
> >If you have any experience porting XP or Vista physical drives and you >>succeeded and your vm are working normally I invite you to share your [quoted text clipped - 64 lines] >>experience. >>Jack Robert Comer - 09 Mar 2008 04:22 GMT >I've found the source of problem why guestXP was soooooo slow. >It was Symantec NAV. Cool, glad to hear it. (That you fixed it, not that Symantec was a problem!)
>On bootable disk (iso) I have at least 2 restore options involving Universe >Restore. >One is so called 'Safe' and another 'full install'. >I do not have any clue which is for what. (I tried both anyway). The only difference between safe and full install from what I understand is the drivers it tries to load. For instance, on my laptop it wont work at all with the full version, but works with no problem on the safe version.
 Signature Bob Comer
>I've found the source of problem why guestXP was soooooo slow. >It was Symantec NAV. [quoted text clipped - 76 lines] >>>experience. >>>Jack Jack - 09 Mar 2008 04:55 GMT Now, if I could port Vista.... I even cannot analyse it, because it refuses to create boot log. Jack
> >I've found the source of problem why guestXP was soooooo slow. >>It was Symantec NAV. [quoted text clipped - 95 lines] >>>>experience. >>>>Jack Jim Kay - 09 Mar 2008 22:43 GMT The problem is almost certainly not Vista but an ATA controller in the original real machine.
Actually, I have two open cases on this problem and there is no effective progress on either one.
Jim Kay
> Now, if I could port Vista.... > I even cannot analyse it, because it refuses to create boot log. [quoted text clipped - 102 lines] >>>>>experience. >>>>>Jack Jack - 10 Mar 2008 18:14 GMT Is Vista different in that case? WinXP does not have booting problem. Jack
> The problem is almost certainly not Vista but an ATA controller in the > original real machine. [quoted text clipped - 112 lines] >>>>>>experience. >>>>>>Jack Colin Barnhorst - 10 Mar 2008 19:01 GMT Vista in a vm would not be an issue. Jim is telling you to look at the host.
> Is Vista different in that case? WinXP does not have booting problem. > Jack [quoted text clipped - 118 lines] >>>>>>>experience. >>>>>>>Jack Jack - 10 Mar 2008 22:08 GMT In my case it is the same physical machine! I have dual boot and there is the same ATA controller for both! So, where should I look in the host? Jack
> Vista in a vm would not be an issue. Jim is telling you to look at the > host. [quoted text clipped - 124 lines] >>>>>>>>experience. >>>>>>>>Jack Colin Barnhorst - 10 Mar 2008 22:17 GMT Dual booting has nothing to do with Virtual PC. Please explain how you are using VPC.
> In my case it is the same physical machine! > I have dual boot and there is the same ATA controller for both! [quoted text clipped - 134 lines] >>>>>>>>>experience. >>>>>>>>>Jack Jack - 10 Mar 2008 22:59 GMT It has, if you are porting both physical drives into vm. Jack
> Dual booting has nothing to do with Virtual PC. Please explain how you > are using VPC. [quoted text clipped - 137 lines] >>>>>>>>>>experience. >>>>>>>>>>Jack Colin Barnhorst - 10 Mar 2008 23:40 GMT The dual boot aspect wouldn't make any difference. You would ghost each volume separately to its own vm. You will have issues with the change in hardware following the move, of course, but that also is apart from any dual booting matter.
> It has, if you are porting both physical drives into vm. > Jack [quoted text clipped - 140 lines] >>>>>>>>>>>experience. >>>>>>>>>>>Jack Jack - 11 Mar 2008 03:23 GMT Colin, I do not know what you want to say. The problem I am having is that I can port physical disk having Win XP but I cannot port physical disk having Vista. If you've succeeded that please help. I mean if you done it yourself. If not, please try it first if you have Vista and if you succeed please let us know. Otherwise, I don't think you can help in that matter. Jack
> The dual boot aspect wouldn't make any difference. You would ghost each > volume separately to its own vm. You will have issues with the change in [quoted text clipped - 148 lines] >>>>>>>>>>>>experience. >>>>>>>>>>>>Jack jeff™ - 27 Mar 2008 22:53 GMT Hi To All,
I experience what Jack is telling about, I am using Windows Vista Ulitmate Ed., and have a Virtual Server 2005 R2 w/ SP1 installed on it got 3 partition on a single hard drive which I perform I want to mount one partition on a virtual machine, when I try to link a physical drive into a virtual hard disk it displays like this: "Physical computer drive: <NONE>" it cannot display anything or not supporting my physical hard disk. Even I don't know why, or I am thinking about maybe this is because of ACU "Access Control List" feautures built-in on Vista settings that restrict the physical mount drive into virtual hard drive. Iexperience the same issue with him as well. Please help us to find a solution or provide a hotfix for this issue.
Thank you in advance and hope you can find a solution for this problem.
Jeff
> Colin, I do not know what you want to say. > The problem I am having is that I can port physical disk having Win XP but I [quoted text clipped - 157 lines] > >>>>>>>>>>>>experience. > >>>>>>>>>>>>Jack Sebastian G. - 28 Mar 2008 14:24 GMT > Hi To All, > [quoted text clipped - 7 lines] > feautures built-in on Vista settings that restrict the physical mount drive > into virtual hard drive. ACLs are not related to a lack of privileges for accessing the physical disk, but rather SE_BACKUP_RESTORE_PRIVILEGE. A non-admin user simply doesn't have it (for obvious reasons), and this isn't exactly news, since the same applies to Windows XP, Windows 2000 and NT 4/3.5 as well - just seems like you were an !%@#$&^ who has always been running as admin.
The solution is, of course, to use file containers unless you actually need it otherwise.
[Shitload or unnecessary, horribly broken quoting snipped]
jeff™ - 29 Mar 2008 12:47 GMT Sebastian and others,
What the issue is all about the Linked Virtual Disks, a Virtual Server running on Vista which we cannot port phyical to virtual.
The link virtual disk are pointers that point to host's entire physical disk. If you know P2V maybe you can understand what I am saying.
It used for the conversion of a physical machine to a virtual machine, hope this will be more clear to you.
Regards,
Jeff
> > Hi To All, > > [quoted text clipped - 18 lines] > > [Shitload or unnecessary, horribly broken quoting snipped] Bo Berglund - 28 Mar 2008 17:01 GMT On Thu, 27 Mar 2008 14:53:02 -0700, jeff <jeff@discussions.microsoft.com> wrote:
>Hi To All, > [quoted text clipped - 12 lines] > >Jeff If you want to use a *physical* disk partition inside a Virtual PC guest you are out of luck. This is not how VPC or VS works. The guests use emulated disks which are ordinary files (albeit big ones) on the host disk. THese files have the extension VHD (Virtual Hard Disk) and are to a guest what a hard disk is to the host.
Bo Berglund
jeff™ - 29 Mar 2008 12:51 GMT Man,
The link virtual disk are pointers that point to host's entire physical disk. If you know P2V maybe you can understand what I am saying.
It used for the conversion of a physical machine to a virtual machine, hope this will be more clear to you.
jeff
> >Hi To All, > > [quoted text clipped - 19 lines] > > Bo Berglund Bo Berglund - 29 Mar 2008 18:29 GMT On Sat, 29 Mar 2008 04:51:01 -0700, jeff <jeff@discussions.microsoft.com> wrote:
>Man, > [quoted text clipped - 3 lines] >It used for the conversion of a physical machine to a virtual machine, hope >this will be more clear to you. All right, this was not at all clear in your posting, we thought you (as several others before you) wanted to run VPC guests directly off the hardware disk, which does not work.
In order to link a disk for P2V you must reconfigure that disk so it does not have any drive letters assigned to it. This can be done in disk manager on Windows XP and probably also on Vista (I don't run Vista myself).
Bo Berglund
Steve Jain - 28 Mar 2008 21:55 GMT On Thu, 27 Mar 2008 14:53:02 -0700, jeff <jeff@discussions.microsoft.com> wrote:
>Hi To All, > [quoted text clipped - 10 lines] > >Thank you in advance and hope you can find a solution for this problem. You cannot link to a physical partition. This is not a supported function.
You can link to a physical disk in Virtual Server, but only for migration.
 Signature Cheers, Steve Jain, Virtual Machine MVP http://vpc.essjae.com/ I do not work for Microsoft.
jeff™ - 29 Mar 2008 12:53 GMT Steve,
Yes you can, if you know how to use the link virtual disk are pointers that point to host's entire physical disk. If you know P2V maybe you can understand what I am saying. Which we cannot use on Vista but on WinXP having no problem.
It used for the conversion of a physical machine to a virtual machine, hope this will be more clear to you.
jeff
> >Hi To All, > > [quoted text clipped - 16 lines] > You can link to a physical disk in Virtual Server, but only for > migration. Jim Kay - 09 Mar 2008 22:40 GMT If the original 'real' machine has an ATA controller for the boot disk, the Universal Restore will not convert it properly and the resulting virtual machine will not boot. The symptoms are exactly what you have described.
I have an open case at Acronis on this problem but they seem to be making zero progress. The case has been open since December.
Jim Kay
>I am giving up. > After 7 days of tweaking I have enough. [quoted text clipped - 38 lines] > experience. > Jack
|
|
|