1 |
On Thu, 8 Sep 2011 11:58:21 +0200 |
2 |
Alan McKinnon wrote: |
3 |
|
4 |
> On Wed, 7 Sep 2011 19:08:21 -0400 |
5 |
> David Relson <relson@×××××××××××××.com> wrote: |
6 |
> |
7 |
> > G'day, |
8 |
> > |
9 |
> > I'm having a problem with VirtualBox and am looking for ideas. |
10 |
> > |
11 |
> > As background, I'm running virtualbox-bin-4.1.2 on a |
12 |
> > 2.6.39-gentoo-r2 kernel on an AMD Phenom 9850. My vmware install |
13 |
> > no longer works because vmware wants the BKL and the 2.6.39 kernel |
14 |
> > doesn't have it. Using vmware-converted the WinXP vmware guest has |
15 |
> > been converted to .ova format. |
16 |
> > |
17 |
> > VirtualBox-4.1.2 loads the .ova OK. After clicking "start" the |
18 |
> > guest starts up, shows the splash screen, then aborts with a blue |
19 |
> > screen saying: |
20 |
> > |
21 |
> > A problem has been detected and windows has been shut down to |
22 |
> > prevent damage to your computer. |
23 |
> > |
24 |
> > If this is the first time you've seen this Stop error screen, |
25 |
> > restart your computer. If this screen appears again, follow |
26 |
> > these steps: |
27 |
> > |
28 |
> > Check to be sure you have adequate disk space. If a driver is |
29 |
> > identified in the Stop message, disable the driver or check with |
30 |
> > the manufacturer for driver updates. Try changing video |
31 |
> > adapters. |
32 |
> > |
33 |
> > Check with your hardware vendor for any BIOS updates. Disable |
34 |
> > BIOS memory options such as caching or shadowing. If you need to use |
35 |
> > Safe Mode to remove or disable components, restart your |
36 |
> > computer, press F8 to select Advanced Startup options, and then |
37 |
> > select Safe Mode. |
38 |
> > |
39 |
> > Technical information: |
40 |
>>> Verifying ebuild manifests |
41 |
>>> Jobs: 0 of 1 complete, 1 running Load avg: 1.05, |
42 |
>>> 0.72, 0.55 Emerging (1 of 1) app-emulation/virtualbox-4.1.2 |
43 |
>>> Jobs: 0 of 1 complete, 1 running Load avg: 1.05, |
44 |
>>> 0.72, 0.55 Jobs: 0 of 1 complete Load |
45 |
>>> avg: 2.10, 3.99, 3.56 |
46 |
> > |
47 |
> > *** STOP: 0x0000008E |
48 |
> > (0xC0000005,0x8053A8E3,0xF779E610,0x00000000) |
49 |
> > |
50 |
> > Using virtualbox-4.1.2 on my wife's Win 7 laptop, the same .ova file |
51 |
> > works fine. |
52 |
> > |
53 |
> > Any thoughts on what needs changing in my gentoo environment to |
54 |
> > successfully run the guest? |
55 |
> > |
56 |
> > Thank you. |
57 |
> > |
58 |
> > David |
59 |
> > |
60 |
> > P.S. The most recent log file is attached. |
61 |
> > |
62 |
> > |
63 |
> |
64 |
> Did you import the .ova file first? |
65 |
|
66 |
Yes. I imported the .ova file -- a process that took several minutes |
67 |
and resulted in .vbox (6.5K) and .vmdk (7.4G) files in directory |
68 |
~/VirtualBox/Machines/WinXP. |
69 |
|
70 |
In the log file (attached to the original message) can be seen the |
71 |
following "VM state" messages: |
72 |
|
73 |
00:00:01.535 Changing the VM state from 'CREATING' to 'CREATED'. |
74 |
00:00:01.535 Changing the VM state from 'CREATED' to 'POWERING_ON'. |
75 |
00:00:01.535 Changing the VM state from 'POWERING_ON' to 'RUNNING'. |
76 |
00:00:29.481 Changing the VM state from 'RUNNING' to 'RESETTING'. |
77 |
00:00:29.509 Changing the VM state from 'RESETTING' to 'RUNNING'. |
78 |
00:00:35.391 Changing the VM state from 'RUNNING' to 'SUSPENDING'. |
79 |
00:00:35.420 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'. |
80 |
00:00:38.711 Changing the VM state from 'SUSPENDED' to 'POWERING_OFF'. |
81 |
00:00:38.711 Changing the VM state from 'POWERING_OFF' to 'OFF'. |
82 |
00:00:38.722 Changing the VM state from 'OFF' to 'DESTROYING'. |
83 |
00:00:38.731 Changing the VM state from 'DESTROYING' to 'TERMINATED'. |
84 |
|
85 |
Looking at the log file, I interpret "RESETTING to RUNNING" as good, |
86 |
and the messages after that as bad, i.e. indicating that vbox wasn't |
87 |
happy with the VM. |
88 |
|
89 |
Why vbox wasn't happy is not at all clear to me. |
90 |
|
91 |
Any thoughts? |
92 |
|
93 |
Regards, |
94 |
|
95 |
David |