Hi Adam and all,
at the end my problem description I sent to -virtualization first.
(Thanks Adam, to pointing out that I am barking up the wrong tree;-)
On Mon, Apr 2, 2012 at 3:28 PM, Adam Vande More <amvandem...@gmail.com> wrote:
> On Sun, Apr 1, 2012 at 11:44 PM, Petro Rossini <petro.ross...@gmail.com>
>> > AFAICT, that error message is related to a permissions issue. Can you
>> > supply the VM log when you post the question to emulation?
>>
>> See you there:-) But there isn't much I found:
>>
>> 00:00:01.368 nspr-2 Loading settings file
>> "/vboxes/zimbra/zimbra.vbox" with version "1.11-freebsd"
>> 00:00:01.885 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
>> aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine}
>> aText={The virtual machine 'zimbra' has terminated unexpectedly during
>> startup with exit code 0}, preserve=false
>
>
> I would like to see it in full if possible.
Where else could I look? This is what I could find:
# cat VBoxSVC.log.3
VirtualBox (XP)COM Server 4.1.8_OSE r75467 freebsd.amd64 (Apr 1 2012
23:02:19) release log
00:00:00.001 main Log opened 2012-04-01T13:05:46.587439000Z
00:00:00.001 main OS Product: FreeBSD
00:00:00.001 main OS Release: 9.0-STABLE
00:00:00.001 main OS Version: FreeBSD 9.0-STABLE #5: Sun Apr 1
21:07:30 EST 2012
r...@dellt410one.vv.fda:/usr/obj/usr/src/sys/GENERIC
00:00:00.001 main OS Service Pack: FreeBSD 9.0-STABLE #5: Sun Apr
1 21:07:30 EST 2012
r...@dellt410one.vv.fda:/usr/obj/usr/src/sys/GENERIC
00:00:00.001 main Executable: /usr/local/lib/virtualbox/VBoxSVC
00:00:00.001 main Process ID: 86377
00:00:00.001 main Package type: BSD_64BITS_GENERIC (OSE)
00:00:00.121 nspr-2 Loading settings file
"/root/.VirtualBox/VirtualBox.xml" with version "1.10-freebsd"
00:00:01.331 nspr-2 VDInit finished
00:00:01.368 nspr-2 Loading settings file
"/vboxes/zimbra/zimbra.vbox" with version "1.11-freebsd"
00:00:01.885 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine}
aText={The virtual machine 'zimbra' has terminated unexpectedly during
startup with exit code 0}, preserve=false
00:00:06.888 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE
(0x80bb000c) aIID={53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
aComponent={Medium} aText={Medium
'/root/.VirtualBox/zimbra/zimbra_root.vdi' cannot be closed because it
is still attached to 1 virtual machines}, preserve=false
00:00:06.888 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE
(0x80bb000c) aIID={53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
aComponent={Medium} aText={Medium
'/root/.VirtualBox/zimbra/zimbra_swap.vdi' cannot be closed because it
is still attached to 1 virtual machines}, preserve=false
00:00:06.888 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE
(0x80bb000c) aIID={53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
aComponent={Medium} aText={Medium
'/root/.VirtualBox/zimbra/zimbra_var.vdi' cannot be closed because it
is still attached to 1 virtual machines}, preserve=false
00:00:06.888 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE
(0x80bb000c) aIID={53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
aComponent={Medium} aText={Medium
'/root/.VirtualBox/zimbra/zimbra_opt_zimbra.vdi' cannot be closed
because it is still attached to 1 virtual machines}, preserve=false
00:00:06.888 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE
(0x80bb000c) aIID={53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
aComponent={Medium} aText={Medium
'/root/.VirtualBox/zimbra/zimbra_opt_zimbra_db.vdi' cannot be closed
because it is still attached to 1 virtual machines}, preserve=false
00:00:06.888 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE
(0x80bb000c) aIID={53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
aComponent={Medium} aText={Medium
'/root/.VirtualBox/zimbra/zimbra_opt_zimbra_index.vdi' cannot be
closed because it is still attached to 1 virtual machines},
preserve=false
00:00:06.889 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE
(0x80bb000c) aIID={53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
aComponent={Medium} aText={Medium
'/root/.VirtualBox/zimbra/zimbra_opt_zimbra_store.vdi' cannot be
closed because it is still attached to 1 virtual machines},
preserve=false
00:00:06.895 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005)
aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox}
aText={The object is not ready}, preserve=false
The disk errors come 5 seconds after the termination so I guess it
isn't really related. But I can be wrong.
Regards
Peter
Here my first post:
Hi all,
I had some VirtualBox hassle over the weekend.
It started with thes messages inside the VM, a Ubuntu 10.04 Server
(running Zimbra).
2012-03-30T18:37:11.581591+11:00 mail kernel: [4520695.304357] sd
4:0:0:0: [sdd] Unhandled error code
2012-03-30T18:37:15.201744+11:00 mail kernel: [4520695.304362] sd
4:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
2012-03-30T18:37:15.201753+11:00 mail kernel: [4520695.304366] sd
4:0:0:0: [sdd] CDB: Write(10): 2a 00 02 1d 44 f8 00 00 08 00
2012-03-30T18:37:15.201756+11:00 mail kernel: [4520695.304457]
end_request: I/O error, dev sdd, sector 35472632
2012-03-30T18:37:15.201758+11:00 mail kernel: [4520695.312601]
__ratelimit: 9 callbacks suppressed
2012-03-30T18:37:15.201761+11:00 mail kernel: [4520695.312604] Buffer
I/O error on device sdd, logical block 4434079
2012-03-30T18:37:15.201763+11:00 mail kernel: [4520695.321978] lost
page write due to I/O error on sdd
Two hours later it moves to another disk: "sd 3:0:0:0: [sdc] Unhandled
error code"
The Linux reacts with a read-only remount - practically the box is falling over.
The VDI disks are on a ZFS filesystem, and I scrubbed the ZVolume and
looked for other possible problems - host-side all seamt to be okay.
I restarted the system once - and for a few hours it worked, untiul I
see the same problem again.
A second reboot is not that successful, I cannot start the VM headless
anymore, getting a
Result Code: NS_ERROR_FAILURE (0x00004005)
I have a second machine with the same setup and continous mirroring of
the disks (zfs send/receive) - the same result.
Tried an older ZFS snapshot of the VDI disks - still not starting.
It was FreeBSD 8.2 and VirtualBox 4.0.4, and some people with similar
problems when the VirtualBox kernel module and system where outy of
sync.
I did some port upgrades recently but left VirtualBox alone. Hmmh..
Anyway, I started upgading to the newest VirtualBox in the
ports(4.1.18). Under 8.2 the rebuild does not seem to work anymore, it
has some clang related compile errors (apologize that I do not have
the detail, it is a dodgy macro with "clang" in it).
So I upgraded the base system to 9-STABLE first and was able to build
VirtualBox 4.1.18 now. (with a minor hickup, libpcre.so.0 not found, I
just symlinked .1 against ist)
Still the same error:
Result Code: NS_ERROR_FAILURE (0x00004005)
So I decided to go home to get access to the X11-GUI (on the road I
had ssh only). I thought of rebuilding a new VM with the same disks
(because of some forum suggestions the config could be corrupted).
To my astonishment the system started!
And now I can start it headless again!
I am at loss to explain it, maybe someone else may have a clue?
Regards
Peter
_______________________________________________
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
