VPC 2004 SP1 - Hangs or Get "An error has occurred"
in [Virtual PC]
|
From: Robert Comer on 30 Jul 2006 21:44 Interesting, is it still the same hardware? -- Bob Comer <Microsoft MVP Windows - Virtual Machine> "ohaya" <ohaya(a)yahoo.com> wrote in message news:1154303762.965150.293610(a)s13g2000cwa.googlegroups.com... > Hi, > > For the record: > > I worked with support for a couple of days, and they had me run some > things including something called "ADPLUS". I've sent them what they > asked for, but no response yet. > > In the meantime, I decided to build a new Win2K3 machine, and got > Virtual Server 2005 R2 on it. I then moved the VPC guests over, and > ran them, and they all run fine, with no hanging or unexpected errors > (so far). > > I don't know if it's my imagination, but the guests/VMs seem to run a > lot faster, especially starting up Windows... > > Jim > > > > > ohaya wrote: >> Bob, >> >> I have a support case open with MS through my company... Hopefully, >> they'll come up with something. >> >> Jim >> >> >> >> Robert Comer wrote: >> >> I know that some of you said that the AMD64 CPU shouldn't be a >> >> problem, >> >> but it kind of looks like that might be the problem? >> > >> > It could also be something in the chipset or drivers for the AMD64 >> > motherboard PC, but it definitely is some kind of incompatibility. >> > >
From: ohaya on 31 Jul 2006 01:13 Bob, Sorry, I forgot to clearly explain that. The Win2K3-SP1/Virtual Server 2005 R2 installation is on the SAME physical machine: Motherboard: MSI K8NGM2-FID CPU: AMD64 Memory: 3.xGB Also the memory allocated to the VMs is the same as it was under VPC. I setup a multi-boot configuration so I can still go back to the VPC configuration when I'm working on the support case with MS, because I'm still hoping that MS will figure out what the problem is so that I can go back to VPC. Also, I copied the VMC, VHD to create a physically different set of files for when I'm running under Virtual Server vs. VPC. I know that they're suppose to be compatible, but I didn't want to inadverdently have Virtual Server change the VHD (especially). BTW, I was able just do VM "Create" in Virtual Server for two of the three VMs, but the 3rd would not start under Virtual Server. I was able to get around that by deleting the copy of the .VMC file, and "Add"ing a new VM using the existing VHD that I had copied. I'm kind of curious: Did you expect me to have the same problem with VS that I had with VPC? I'm glad that it's working at least under VS, because between all of the hung VPC session and working with MS on this problem so far, I've lost a LOT of time :(!! At least now, I can keep on getting some "real" work done... Jim Robert Comer wrote: > Interesting, is it still the same hardware? >
From: Robert Comer on 31 Jul 2006 07:24 > I'm kind of curious: Did you expect me to have the same problem with VS > that I had with VPC? Not necessarily, but depending on the cause, you could have. -- Bob Comer <Microsoft MVP Windows - Virtual Machine> "ohaya" <ohaya(a)cox.net> wrote in message news:OgcyiAGtGHA.1512(a)TK2MSFTNGP03.phx.gbl... > Bob, > > Sorry, I forgot to clearly explain that. > > The Win2K3-SP1/Virtual Server 2005 R2 installation is on the SAME physical > machine: > > Motherboard: MSI K8NGM2-FID > CPU: AMD64 > Memory: 3.xGB > > Also the memory allocated to the VMs is the same as it was under VPC. > > I setup a multi-boot configuration so I can still go back to the VPC > configuration when I'm working on the support case with MS, because I'm > still hoping that MS will figure out what the problem is so that I can go > back to VPC. > > Also, I copied the VMC, VHD to create a physically different set of files > for when I'm running under Virtual Server vs. VPC. I know that they're > suppose to be compatible, but I didn't want to inadverdently have Virtual > Server change the VHD (especially). > > BTW, I was able just do VM "Create" in Virtual Server for two of the three > VMs, but the 3rd would not start under Virtual Server. I was able to get > around that by deleting the copy of the .VMC file, and "Add"ing a new VM > using the existing VHD that I had copied. > > I'm kind of curious: Did you expect me to have the same problem with VS > that I had with VPC? > > I'm glad that it's working at least under VS, because between all of the > hung VPC session and working with MS on this problem so far, I've lost a > LOT of time :(!! At least now, I can keep on getting some "real" work > done... > > Jim > > > > Robert Comer wrote: >> Interesting, is it still the same hardware? >>
From: ohaya on 4 Aug 2006 19:11 Hi, To keep you all posted: - Running the same 3 guests under VPC running on Win2K3-32bit on my AMD64 system causes the guests to hang. - I'm told that WinXP Pro (32bit) SP2 is suppose to work. Waiting to test it. Jim Robert Comer wrote: >> I'm kind of curious: Did you expect me to have the same problem with VS >> that I had with VPC? > > Not necessarily, but depending on the cause, you could have. >
From: ohaya on 5 Aug 2006 00:29
Hi, Well, running VPC 2004 SP1 on WinXP Pro SP2 didn't work either... the guests still all hung. In fact, it seemed worse on WinXP Pro SP2, because not only did the guests and VPC hang, but it eventually hung the "real" host also. I had to power the machine down physically. Jim ohaya wrote: > Hi, > > To keep you all posted: > > - Running the same 3 guests under VPC running on Win2K3-32bit on my > AMD64 system causes the guests to hang. > > - I'm told that WinXP Pro (32bit) SP2 is suppose to work. Waiting to > test it. > > Jim > > > > Robert Comer wrote: >>> I'm kind of curious: Did you expect me to have the same problem with >>> VS that I had with VPC? >> >> Not necessarily, but depending on the cause, you could have. >> |