VPC 2004 SP1 - Hangs or Get "An error has occurred"
in [Virtual PC]
|
From: Robert Comer on 24 Jul 2006 20:46 > Thanks for 'hanging in there' with this one... I'm trying, but not helping much. :( From my search on the web it seems the only thing I've seen that even comes close to fixing this is change the amount of RAM allocated to the VM's. It doesn't appear to me you should be hitting a problem with what you have, but you may try lowering the allocation for each VM by 100 or 200M, just to see if it makes a difference. -- Bob Comer <Microsoft MVP Windows - Virtual Machine> "ohaya" <ohaya(a)cox.net> wrote in message news:e6ge6Y3rGHA.4660(a)TK2MSFTNGP04.phx.gbl... > Bob, > > Comments below, interspersed.... > > Thanks for 'hanging in there' with this one... > > > Robert Comer wrote: >>> What do you mean by "shell enhancement software"? >> >> Something that changes the appearance/functionality of windows explorer. > > Then, no, I don't have any shell enhancement software... > > > >> >>> What I don't understand is that these are suppose to be "VIRTUAL" guest >>> hosts, right? Why would a problem in one guest host (if there is one), >>> cause ALL of the guest hosts to hang? Aren't they suppose to be >>> isolated? >> >> Virtual PC is pretty much a single threaded app, so it makes sense that >> when the main thread in Virtual PC dies, everything dies. Virtual Server >> wouldn't act the same. >> >> Something is blocking the main VPC thread on your PC, and that's why it >> does what it does, unfortunately I don't know what that might be. Is >> there any kind of message in the event viewer system and Application >> logs? > > > I *am* seeing the following under Application Logn (these events seem to > come in pairs, and the offset shown in the 2nd event is the same as in the > popup when I get the "Unexpected" error): > > Event Type: Error > Event Source: Microsoft Virtual PC 2004 > Event Category: None > Event ID: 1001 > Date: 7/24/2006 > Time: 4:49:44 AM > User: N/A > Computer: TESTWIN2K > Description: > The description for Event ID ( 1001 ) in Source ( Microsoft Virtual PC > 2004 ) cannot be found. The local computer may not have the necessary > registry information or message DLL files to display messages from a > remote computer. The following information is part of the event: > 143763969. > Data: > 0000: 42 75 63 6b 65 74 3a 20 Bucket: > 0008: 31 34 33 37 36 33 39 36 14376396 > 0010: 39 0d 0a 9.. > > Event Type: Error > Event Source: Microsoft Virtual PC 2004 > Event Category: None > Event ID: 1000 > Date: 7/24/2006 > Time: 4:49:06 AM > User: N/A > Computer: TESTWIN2K > Description: > The description for Event ID ( 1000 ) in Source ( Microsoft Virtual PC > 2004 ) cannot be found. The local computer may not have the necessary > registry information or message DLL files to display messages from a > remote computer. The following information is part of the event: virtual > pc.exe, 5.3.582.27, virtual pc.exe, 5.3.582.27, 0005ba8b. > Data: > 0000: 41 70 70 6c 69 63 61 74 Applicat > 0008: 69 6f 6e 20 46 61 69 6c ion Fail > 0010: 75 72 65 20 20 76 69 72 ure vir > 0018: 74 75 61 6c 20 70 63 2e tual pc. > 0020: 65 78 65 20 35 2e 33 2e exe 5.3. > 0028: 35 38 32 2e 32 37 20 69 582.27 i > 0030: 6e 20 76 69 72 74 75 61 n virtua > 0038: 6c 20 70 63 2e 65 78 65 l pc.exe > 0040: 20 35 2e 33 2e 35 38 32 5.3.582 > 0048: 2e 32 37 20 61 74 20 6f .27 at o > 0050: 66 66 73 65 74 20 30 30 ffset 00 > 0058: 30 35 62 61 38 62 0d 0a 05ba8b.. > > > > > > >> >>> It seems move like VPC *itself* is hanging, but what could something >>> within a guest host be doing that would cause that??? >> >> That's exactly what it sounds like to me too, but I kind of doubt its >> something in a guest that's doing it, it sounds like something else on >> the host. >> >> Is there some kind of power management software running (something to >> quite the fans or throttle back the CPU? (on the host) > > I have AMD Powernow in the "Services", but I set that to not start since > yesterday, and the problems still have been occurring since then... > > Jim >
From: ohaya on 27 Jul 2006 22:42 Hi, I have some new info on this. Out of desparation, I moved the 3 guest hosts to a USB drive, and then attached the drive to another machine I had. This other machine has less memory (total 2GB) than the earlier machine, and has a Socket A mobo with an AMD XP2800+ CPU instead of an AMD64. OS is Win2K Server SP4, same on both machines. Guess what? Yep, all 3 guests start up and I haven't seen the hanging or unexpected exception so far!! 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? Jim Robert Comer wrote: >> 1) Are you suggesting putting this in the boot.ini for the 'real' PC, or >> in the boot.ini for the guest hosts, or for BOTH? > > The "real" pc. > >> 2) From what I've been able to find, this parameter is only for Windows XP >> SP2 and Win2K3? Is it applicable to Win2K Server SP4 also? > > You are correct, sorry, I had forgotten about the W2K. This wont make any > difference. >
From: Robert Comer on 28 Jul 2006 07:35 > 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. -- Bob Comer <Microsoft MVP Windows - Virtual Machine> "ohaya" <ohaya(a)cox.net> wrote in message news:enKDL8esGHA.1288(a)TK2MSFTNGP02.phx.gbl... > Hi, > > I have some new info on this. > > Out of desparation, I moved the 3 guest hosts to a USB drive, and then > attached the drive to another machine I had. This other machine has less > memory (total 2GB) than the earlier machine, and has a Socket A mobo with > an AMD XP2800+ CPU instead of an AMD64. OS is Win2K Server SP4, same on > both machines. > > Guess what? > > Yep, all 3 guests start up and I haven't seen the hanging or unexpected > exception so far!! > > 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? > > Jim > > > Robert Comer wrote: >>> 1) Are you suggesting putting this in the boot.ini for the 'real' PC, or >>> in the boot.ini for the guest hosts, or for BOTH? >> >> The "real" pc. >> >>> 2) From what I've been able to find, this parameter is only for Windows >>> XP SP2 and Win2K3? Is it applicable to Win2K Server SP4 also? >> >> You are correct, sorry, I had forgotten about the W2K. This wont make >> any difference. >>
From: ohaya on 28 Jul 2006 09:32 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 30 Jul 2006 19:56
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. > > |