FreeBSD 7.0 - without sigreturn + with intel VT-x - host win

Discussions about using non Windows and Linux guests such as FreeBSD, DOS, OS/2, OpenBSD, etc.

Do you run freebsd, and did this work for you?

Yes, I run FreeBsd, and it worked (Host Windows)
0
No votes
Yes, I run FreeBsd, and it worked (host Linux)
0
No votes
Yes, I run FreeBsd, and it worked (host Other)
0
No votes
Yes, I run FreeBsd, but I didn't have the problem before
1
8%
Yes, I run FreeBsd, but it did *not* help (Host Windows)
1
8%
Yes, I run FreeBsd, but it did *not* help (Host Linux)
5
42%
Yes, I run FreeBsd, but it did *not* help (Host other)
1
8%
Yes, I run FreeBsd, but I didn't try => need a real fix by VBox
2
17%
No I don't run FreeBSD
2
17%
 
Total votes : 12

FreeBSD 7.0 - without sigreturn + with intel VT-x - host win

Postby me_martin » 28. Jul 2008, 00:58

Yes, I got it running :) :)

Guest: FreeBSD 7.0
Host: Windows Vista
System: Dell, with Dell bios
(anyone with any other system, please test and report)

- VT-x hardware acceleration => ON
- No sig-return encountered, while running 2 big make jobs

What you need to do:
* setup
- choose the right network adapter. the default doesn't work, I use the intel 1000 desktop

* For Installation:
- Switch off VT-x
- do *not* use your keyboard during the boot process. Just wait for the menu to count down

* Once installed
- edit your /boot.loader.rc
all you need is: "include /boot/loader.4th" and "start"
remove:
"check password": so I am not sure it causes any harm to leave it in?
"include .. beatie", "beastie-start"
=> beastie is the 2nd boot menu (with, withou ACPI, singl uesr,...) and this is what will kill your VT-x

- in your boot/loader.conf you may wan to enter
kern.hz=100
or even 50, to save some cpu time spend in the kernel? (I just took that hint from other posts)

- boot0cfg -t 15 /dev/xxxx
=> since you *must* not use the kbd, during boot up (once VT-x is on), it will be nice to reduce the wait time.

*** Thats it
Before you start next time, switch on VT-x (you may also have to enable in your bios, some bioses disable it). In VBox, you must switch it on twice: general setting, machine settings.


- I haven't tested running an x-server inside the guest, since my X runs on the host, and the guest connects to it.
- au contraire to other reports, it varaible sized "vdi" disk files work fine. (I do however use a smal fixed sized one for the swap space)


Hope this helps. Any feedback is welcome, Any test reports with differnet setup are welcome
me_martin
 
Posts: 11
Joined: 28. Jul 2008, 00:29

Postby Sunsawe » 29. Jul 2008, 21:07

I tried but the result was the same.
Sunsawe
 
Posts: 6
Joined: 26. Jul 2008, 21:56

Postby Dante » 13. Dec 2008, 00:17

Like the two others guy who voted. This trick doesn't help to be able to have VT-X emulation with a FreeBSD guest.

Is there some update about it ?
Dante
 
Posts: 1
Joined: 13. Dec 2008, 00:14

Postby me_martin » 16. Dec 2008, 01:51

--- UPDATE ---

This did last work with Virtualbox 1.66. (And then only if you managed to really run VT-x, checked your bios, etc)


Since VBox 2.x I have found no way to start FreeBSD with VT-x. And without VT-x you get the above error.
me_martin
 
Posts: 11
Joined: 28. Jul 2008, 00:29

Finally! Networking works in 2.1!

Postby actionbastard » 18. Dec 2008, 20:42

After much frustration on 2.0.x trying every combo of network settings, I finally have a FreeBSD guest that connects to the world. Now I can start to do real testing.

I'm running OS X 10.4.11 on a quad-core MacPro. Network for VBox is on en1 on the host with DHCP on host. Guest is on the Intel MT Desktop adapter with a fixed IP on the guest on the same subnet as the host's adapter. Vt-x is enabled and I haven't had any problems with touching the keyboard during boot screen selection.

Sweet!
actionbastard
 
Posts: 1
Joined: 18. Dec 2008, 20:20


Return to Other Guests

Who is online

Users browsing this forum: No registered users and 9 guests