Hi,
recently I installed OpenSolaris build 134 in VirtualBox (3.2.6 as on the
install, now upgraded to 3.2.8) on my three years old MacBook Pro, a 2.13GHz
Core Duo with 2GB RAM and a 250GB hard disk. The VM instance has 1GB RAM
assigned and a 16GB disk image. So far, so good. Because newer builds are
available only as source code I decided to learn how to switch to newer
versions by compiling them from sources.
So far I managed to switch from 134 to 136, 136->138, 138->140, and finally
140->142. Because the builds took quite a lot of time on my machine, I recently
thought it would be a good idea to assign the second CPU to the VM, turn
IO-APIC on and then let build release 144 over night.
I therefore started the VM, opened a SSH connection to the VM instance from
Terminal.app to monitor the build log ("%> tail -f log/nightly.log"). When I
came back that morning to see what happened, my SSH connection was terminated,
and on the VM console I saw lots of messages:
Aug 9 02:10:56 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@1 (ata1):
Aug 9 02:10:56 opensolaris timeout: abort request, target=0 lun=0
Aug 9 02:10:56 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@1 (ata1):
Aug 9 02:10:56 opensolaris timeout: abort device, target=0 lun=0
Aug 9 02:10:56 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@1 (ata1):
Aug 9 02:10:56 opensolaris timeout: reset target, target=0 lun=0
Aug 9 02:10:56 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@1 (ata1):
Aug 9 02:10:56 opensolaris timeout: reset bus, target=0 lun=0
Aug 9 05:35:18 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@1 (ata1):
Aug 9 05:35:18 opensolaris timeout: abort request, target=0 lun=0
Aug 9 05:35:18 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@1 (ata1):
Aug 9 05:35:18 opensolaris timeout: abort device, target=0 lun=0
Aug 9 05:35:18 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@1 (ata1):
Aug 9 05:35:18 opensolaris timeout: reset target, target=0 lun=0
Aug 9 05:35:18 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@1 (ata1):
Aug 9 05:35:18 opensolaris timeout: reset bus, target=0 lun=0
Aug 9 06:59:17 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@0 (ata0):
Aug 9 06:59:17 opensolaris timeout: abort request, target=0 lun=0
Aug 9 06:59:17 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@0 (ata0):
Aug 9 06:59:17 opensolaris timeout: abort device, target=0 lun=0
Aug 9 06:59:17 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@0 (ata0):
Aug 9 06:59:17 opensolaris timeout: reset target, target=0 lun=0
Aug 9 06:59:17 opensolaris scsi: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@0 (ata0):
Aug 9 06:59:17 opensolaris timeout: reset bus, target=0 lun=0
In /var/adm/messages I also saw the following (don't know anymore if it was
printed on the console because in the mean time I rebooted the VM):
Aug 9 06:59:17 opensolaris gda: [ID 107833 kern.warning] WARNING:
/p...@0,0/pci-...@1,1/i...@0/c...@0,0 (Disk0):
Aug 9 06:59:17 opensolaris Error for command 'read sector' Error Level:
Informational
Aug 9 06:59:17 opensolaris gda: [ID 107833 kern.notice] Sense Key:
aborted command
Aug 9 06:59:17 opensolaris gda: [ID 107833 kern.notice] Vendor 'Gen-ATA
' error code: 0x3
I saw the same messages when trying to build rel.138 in from self-compiled rel.
136 also by using two CPUs and IO-APIC on. At least I figured that when I was
building the release in the VirtualBox window and was at the same time logged
in via SSH and executed some commands, sometimes it took a couple of seconds
until the command was executed, and often the above messages where printed in
the VirtualBox window. So it seemed to me not only a warning as the message
suggested, but a kind of a serious thing so that I finally stopped building,
powered off the VM, turned the second CPU and the IO-APIC off and rebuild rel.
138 which then went fine without any messages or errors.
So my question is:
Why seems everything to work fine as long as the VM uses only one CPU? What is
causing this error/behaviour when the VM uses 2 CPUs? Do I have to do anything
else apart from assigning CPU #2 to the VM and turning on IO-APIC? Or is this a
VirtualBox thing?
Regards
Thorsten
--
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org
