[Fwd: about vbox and freebsd]

[John Francis Lee]

I got an answer to my question, posted here, from ... but I've been 
instructed not to post to individuals but to the list so I copy the 
Mak's response here :


snip
Your CPU is 64-bit from what I can see. From a bit of Googling, others 
have encountered this problem, and it seems to have to do with VM-X. I 
have no idea what that is, but a thread in which someone has a very 
similar issue is here:


  http://forums.virtualbox.org/viewtopic.php?f=1t=19420

One notable quote is:

  ...[the CPU] does not have Intel VT (hardware virtualization), so you 
will not be able to run 64 bit guests in Virtualbox even though you run 
a 64 bit host.


HTH
/snip

So, OK. I cannot have 64 bit guests using virtual box.

I have installed the 32 bit version of FreeBSD... but it has no X and 
apparently no networking because the ftp from pkg_add failed.


Did I do something wrong in the install, or do I really have to 
configure all that stuff by hand?


Thanks for your help.

--
John Francis Lee
1025/37 Thanon Jet Yod
Mueang Chiangrai 57000
Thailand
---BeginMessage---

08/20/2009 11:59 PM

Hello Duncan Hutty,

I write to you directly because I have posted several times to the list 
and have not seen an answer to my problem, and you seem knowledgeable 
about freebsd.


I have a dual-core amd64 machine running ubuntu 9.04 with vbox 3.04 and 
have tried to create a freebsd guest on it. I've had a freebsd webserver 
at iserver/viaverio for about 15 years but still have not set up a 
freebsd box of my own where I can really learn the ins and outs of the 
system, and I'd like to.


My problem is that I'm told right at the onset of the install that

  CPU doesn't support long mode

Someone suggested that I was trying to install a 64 bit os on 32 bit 
system, but I don't think that's the case :


j...@ws3:~$ hwinfo --cpu
01: None 00.0: 10103 CPU
  [Created at cpu.304]
  Unique ID: rdCR.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: X86-64
  Vendor: AuthenticAMD
  Model: 15.107.2 AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
  Features: 
fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,rdtscp,lm,3dnowext,3dnow,rep_good,pni,cx16,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,3dnowprefetch

  Clock: 1000 MHz
  BogoMips: 2009.02
  Cache: 512 kb
  Units/Processor: 2
  Config Status: cfg=new, avail=yes, need=no, active=unknown

02: None 01.0: 10103 CPU
  [Created at cpu.304]
  Unique ID: wkFv.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: X86-64
  Vendor: AuthenticAMD
  Model: 15.107.2 AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
  Features: 
fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,rdtscp,lm,3dnowext,3dnow,rep_good,pni,cx16,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,3dnowprefetch

  Clock: 1000 MHz
  BogoMips: 2009.02
  Cache: 512 kb
  Units/Processor: 2
  Config Status: cfg=new, avail=yes, need=no, active=unknown

I'm then dumped into an OK prompt and unable to do much more.

Have you seen or heard of this before?

Sorry to bother you if you have no clue yourself.

Thanks for any help you might be able to give.


--
John Francis Lee
1025/37 Thanon Jet Yod
Mueang Chiangrai 57000
Thailand


08/15/2009 10:38 PM

My problem seems to be that

 CPU doesn't support long mode

Is that it? Can't get there from here?

--
John Francis Lee
1025/37 Thanon Jet Yod
Mueang Chiangrai 57000
Thailand


08/15/2009 10:20 PM

Hi,

I got a new machine, a linux ubuntu-running AMD64 based one, and thought 
I'd try out FreeBSD here at home. But when I begin the VirtualBox 
installation I get dumped into a shell-looking terminal with an OK 
prompt. I can't read all the instructions and frankly cannot do anything 
with it. I tried hitting the 2 before the timeout to boot with ACPI 
disabled but that seems not to make any difference.


Have you heard of this problem before?

Any help you might give appreciated.

Thanks.

I'll go see if the VirtualBox people can shed any  light on the matter 
as well.


--
John Francis Lee
1025/37 Thanon Jet Yod
Mueang Chiangrai 57000


--
John Francis Lee
1025/37 Thanon Jet Yod
Mueang Chiangrai 57000
Thailand

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

Re: [Fwd: about vbox and freebsd]

[Michael Powell]

John Francis Lee wrote:

 I got an answer to my question, posted here, from ... but I've been
 instructed not to post to individuals but to the list so I copy the
 Mak's response here :
 
 snip
 Your CPU is 64-bit from what I can see. From a bit of Googling, others
 have encountered this problem, and it seems to have to do with VM-X. I
 have no idea what that is, but a thread in which someone has a very
 similar issue is here:
 
http://forums.virtualbox.org/viewtopic.php?f=1t=19420
 
 One notable quote is:
 
...[the CPU] does not have Intel VT (hardware virtualization), so you
 will not be able to run 64 bit guests in Virtualbox even though you run
 a 64 bit host.
 
 HTH
 /snip

Something sounds strange here. The name for Intel's hardware virtualization 
feature is VT-I, or sometimes VT-x, while AMD's name for the same thing is 
AMD-V. Your processor supports AMD-V and VirtualBox supports both, at least 
in the version 3.0.4 that I am running.

Alas, my processor is Intel and if there actually is a problem of VirtualBox 
not being 64 bit capable with AMD-V I cannot test. Since your host system is 
Ubuntu I am also wondering if the problem could involve their packaging of 
the product, e.g., an older version of VirtualBox such as 2.x or some such. 
Also wonder if it needs to be manually turned on in BIOS. Also I believe the 
64 bit support is relatively new so you might want to check which version of 
VirtualBox it became included as a new feature and compare that against the 
version you have.

Since this is a FreeBSD list I'm just going to say it could be an Ubuntu 
problem, and leave it at that.
 
 So, OK. I cannot have 64 bit guests using virtual box.
 
 I have installed the 32 bit version of FreeBSD... but it has no X and
 apparently no networking because the ftp from pkg_add failed.
 
 Did I do something wrong in the install, or do I really have to
 configure all that stuff by hand?

Don't know. But the default VirtualBox networking is NAT, with it supplying 
DHCP services to the client. You may need to enter a line in your (FreeBSD) 
/etc/rc.conf similar to:

ifconfig_rl0=DHCP   where rl0 would be whatever is your network interface. 
When it boots (the FreeBSD guest) it should be assigned an IP something like 
10.0.2.15 and a default gateway something like 10.0.2.2. These can vary.

Also be aware that while you can connect outbound and receive return traffic 
you will be unable to initiate inbound connections. If you require this 
ability you will need to manually set up VirtualBox in bridge mode, which 
also requires some non-trivial config changes to your host OS.

Like I said, something just sounds fishy to me because on the VirtualBox 
3.0.4 that I run it clearly supports both Intel and AMD hardware 
virtualization. Since I don't have the AMD processor to try it myself I 
can't confirm. At any rate, if the 32 bit FreeBSD runs and satisfies your 
needs why keep fiddling.

-Mike


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