Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso

2012-04-16 Thread Claudius Herder
On 16/04/12 09:08, Craig Rodrigues wrote:
 Hi,
 
 I am trying to run FreeBSD-9.0-RELEASE-amd64-bootonly.iso
 inside VirtualBox and am having some problems.
 
 The error messages I am getting are similar to the ones mentioned here:
 
 http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/065079.html
 
 
 
 
 My host environment
 ===
 
 Operating System: Windows 7, home edition, 64-bit
 VirtualBox for Windows, version 4.1.12 r77245
 
 CPU Information
 
 
 I downloaded the CoreInfo.exe utility which is part of Windows
 Sysinternals utilities
 ( http://technet.microsoft.com/en-us/sysinternals/bb545027 )
 
 According to this utility, my CPU is:
 
 Intel(R) Core(TM)2 Duo CPU T5450  @ 1.66GHz
 Intel64 Family 6 Model 15 Stepping 13, GenuineIntel
 HTT   *   Hyperthreading enabled
 HYPERVISOR-   Hypervisor is present
 VMX   -   Supports Intel hardware-assisted virtualization
 SVM   -   Supports AMD hardware-assisted virtualization
 EM64T *   Supports 64-bit mode
 
 
 So my CPU support 64-bit mode, but does not support hardware-assisted
 virtualization.
 
 
 
 Error message
 =
 If I try to mount and then boot it under VirtualBox, I get this error:
 
CPU doesn't support long mode
 
Consoles: internal video/keyboard
BIOS drive C: is disk0
BIOS 639kB/523264kB available memory
 
FreeBSD/x86 bootstrap loader, Revision 1.1
(r...@farrell.cse.buffalo.edu, Tue Jan  3 06:51:49 UTC 2012)
Can't work out which disk we are booting from.
Guess BIOS device 0x not found by probes, defaulting to disk0:
FATAL: int13_harddisk: function 42. Can't use 64bits lba
 
 
 
 Does anyone know how to fix this problem in VirtualBox?
 
 
 
 
 QEMU for Windows
 
 
 Just to try something else, I downloaded QEMU 0.9.0 for Windows from:
 
 http://www.h7.dion.ne.jp/~qemu-win/
 
 I extracted the zip file into a directory:  C:\local\qemu-0.9.0-windows
 
 I then ran:
 
cd c:\local\qemu-0.9.0-windows
qemu-system-x86_64.exe -L . -m 128 -cdrom
 c:\temp\FreeBSD-9.0-RELEASE-amd64-bootonly.iso
 
 The ISO booted up just fine.  From the dmesg output, this was the emulated 
 CPU:
 
CPU: QEMU Virtual CPU version 0.9.0 (1666.98-MHz K8-class CPU)
 Origin = AuthenticAMD Id = 0x623 Family = 6 Model = 2 Stepping = 3
 
 Features=0x78bfbfdFPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,SE36,CLFLUSH,MMX,FXSR,SSE,SSE2
 Features2=0x1SSE3
 AMD Features=0x20100800SYSCALL,NX,LM
 
 
 
 
 Does anyone know how I can get VirtualBox to behave the same way
 as QEMU for FreeBSD-9.0-RELEASE-amd64-bootonly.iso?
 
 Thanks.
 
 --
 Craig Rodrigues
 rodr...@crodrigues.org
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Hi,

you can only use 64-bit guests if you have a cpu which supports hardware
acceleration.

From VirtualBox manual:
VirtualBox's 64-bit guest support (added with version 2.0) and
multiprocessing (SMP, added with version 3.0) both require hardware
virtualization to be enabled. (This is not much of a limitation since
the vast majority of today's 64-bit and multicore CPUs ship with
hardware virtualization anyway; the exceptions to this rule are e.g.
older Intel Celeron and AMD Opteron CPUs.)

https://www.virtualbox.org/manual/ch10.html#hwvirt

--
Claudius
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: problems with AHCI on FreeBSD 8.2

2012-02-14 Thread Claudius Herder

Hello,

I have got a quite similar problem with AHCI on FreeBSD 8.2 and it still
persists on FreeBSD 9.0 release.

Switching from ahci to ataahci resolved the problem for me too.

I'm using gmirror for swap, system is on a zpool and the problem first
occurred during a zpool scrub, but it is easily reproducible with dd.

The timeouts only occur when writing to disks, dd if=/dev/ada{0|1}
of=/dev/null is not an issue.
Sometimes I need to power off the server because after a reboot one disk
is still missing.

I really would like to help in this issue, so let me know if you need
any more information.

--
Claudius

dmesg:
--cut--
Jan 14 01:33:57 server kernel: ahcich0: Timeout on slot 7 port 0
Jan 14 01:33:57 server kernel: ahcich0: is  cs 0080 ss
 rs 0080 tfd c0 serr  cmd 0004c717
Jan 14 01:33:57 server kernel: ahcich1: Timeout on slot 31 port 0
Jan 14 01:33:57 server kernel: ahcich1: is  cs 8000 ss
 rs 8000 tfd c0 serr  cmd 0004df17
Jan 14 01:33:57 server kernel: ahcich0: Timeout on slot 7 port 0
Jan 14 01:33:57 server kernel: ahcich0: is  cs f800 ss
ff80 rs ff80 tfd c0 serr  cmd 0004cb17
Jan 14 01:33:57 server kernel: ahcich1: Timeout on slot 31 port 0
Jan 14 01:33:57 server kernel: ahcich1: is  cs 00f8 ss
80ff rs 80ff tfd c0 serr  cmd 0004c317
Jan 14 01:33:57 server kernel: ahcich0: Timeout on slot 23 port 0
Jan 14 01:33:57 server kernel: ahcich0: is  cs 0180 ss
 rs 0180 tfd c0 serr  cmd 0004d717
Jan 14 01:33:57 server kernel: ahcich1: Timeout on slot 15 port 0
Jan 14 01:33:57 server kernel: ahcich1: is  cs 00018000 ss
 rs 00018000 tfd c0 serr  cmd 0004cf17
Jan 14 01:33:57 server kernel: ahcich1: Timeout on slot 17 port 0
Jan 14 01:33:57 server kernel: ahcich1: is  cs 01f8 ss
01fe rs 01fe tfd c0 serr  cmd 0004d317
Jan 14 01:33:57 server kernel: ahcich0: AHCI reset: device not ready
after 31000ms (tfd = 0080)
Jan 14 01:33:57 server kernel: ahcich1: Timeout on slot 31 port 0
Jan 14 01:33:57 server kernel: ahcich1: is  cs 8000 ss
 rs 8000 tfd c0 serr  cmd 0004df17
Jan 14 01:33:57 server kernel: ahcich0: Timeout on slot 24 port 0
--cut--

smartctl -a /dev/ada0
smartctl 5.42 2011-10-20 r3458 [FreeBSD 9.0-RELEASE amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint F1 DT
Device Model: SAMSUNG HD753LJ
Serial Number:S13UJDWS900110
LU WWN Device Id: 5 0024e9 0020d1bfa
Firmware Version: 1AA01118
User Capacity:750,156,374,016 bytes [750 GB]
Sector Size:  512 bytes logical/physical
Device is:In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 3b
Local Time is:Tue Feb 14 16:32:58 2012 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status:  (   0) The previous self-test routine
completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection:( 9429) seconds.
Offline data collection
capabilities:(0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off 
support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:(0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:(0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time:(   2) minutes.
Extended self-test routine
recommended polling time:( 158) minutes.
Conveyance self-test routine
recommended polling time:(  17) minutes.
SCT capabilities:  (0x003f) SCT Status supported.
SCT Error Recovery Control supported.