On 20.08.2013 11:21, Patrick Lamaiziere wrote:
> Le Fri, 09 Aug 2013 23:06:01 +0200,
> David Demelier a écrit :
>
>> Hello,
>>
>> I can reproduce a panic by just starting a virtual machine with
>> VirtualBox 4.2.16_2.
>>
>> Unfortunately, as the
Le Fri, 09 Aug 2013 23:06:01 +0200,
David Demelier a écrit :
> Hello,
>
> I can reproduce a panic by just starting a virtual machine with
> VirtualBox 4.2.16_2.
>
> Unfortunately, as the kmod driver is not built with debug symbols I
> could not provide much information.
Hello,
I can reproduce a panic by just starting a virtual machine with VirtualBox
4.2.16_2.
Unfortunately, as the kmod driver is not built with debug symbols I could not
provide much information.
Is this problem already reported?
Fatal trap 9: general protection fault while in kernel mode
ot; in your environment or the "make install"
> command line. *** [check-already-installed] Error code 1
...
> Stop in /usr/ports/emulators/virtualbox-ose.
>
> I had run "portupgrade -fr security/gnutls", even though i run
> "portupgrade -a", the problem
-depends] Error code 1
Stop in /usr/ports/emulators/virtualbox-ose.
*** [install] Error code 1
Stop in /usr/ports/emulators/virtualbox-ose.
I had run "portupgrade -fr security/gnutls", even though i run
"portupgrade -a", the problem is still.
any hints?
thanks
felix
-
How to svn to 9-stable, make world (etc)? How to delete all installed ports?
And then rm -rf /usr/local/*?
Nice hints!
Felix
发自我的 iPad
在 2013-8-5，3:53，John 写道：
> On 02/08/2013 16:54, John wrote:
>> Hello list,
>>
>> I'm trying to install virtualbox on a new mach
On 02/08/2013 16:54, John wrote:
> Hello list,
>
> I'm trying to install virtualbox on a new machine running
> FreeBSD 9.2-BETA2 #0 r253698. The ports version is 324162. Is it a
> problem with the port or my machine?
This was fixed by:
commenting everything out of /etc/make.
Hello list,
I'm trying to install virtualbox on a new machine running
FreeBSD 9.2-BETA2 #0 r253698. The ports version is 324162. Is it a
problem with the port or my machine?
Here is my make.conf:
# cat /etc/make.conf
CC=clang
CXX=clang++
CPP=clang-cpp
# add
On Thu, Feb 28, 2013 at 8:41 AM, Alan Gutierrez wrote:
> I run a Linux guest that suffers the same abuse, but does not lose data.
> My question:
> If anyone runs FreeBSD in VirtualBox, what VirtualBox settings do you use so
> that UFS will work correctly and recover recent writes?
On 28/2/2013 9:41 πμ, Alan Gutierrez wrote:
I'm getting to know FreeBSD by running a 64-bit FreeBSD guest in a VirtualBox
machine on my OS X Mountain Lion laptop. On occasion, when waking up from sleep,
the FreeBSD virtual machine will not restart. VirtualBox marks it as "Aborted.&qu
I'm getting to know FreeBSD by running a 64-bit FreeBSD guest in a VirtualBox
machine on my OS X Mountain Lion laptop. On occasion, when waking up from sleep,
the FreeBSD virtual machine will not restart. VirtualBox marks it as "Aborted."
When I restart FreeBSD, I've
I have built 4.2.6 and its working again! Thank you! :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd
. Be sure that the
virbualbox kernel modules are in sync with your kernel (ie rebuilt
virtualbox-ose-kmod).
Regards.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
This was brought up a few weeks/months ago and I seem to recall that setting
the interface in *promiscuous* mode (monitoring) in the Host configuration
(read, in your hypervisor) was mandatory.
See if that helps.
On Feb 6, 2013, at 3:03 PM, CeDeROM wrote:
> Hello :-)
>
> I cannot get Bridge
Hello :-)
I cannot get Bridged Network setup in VBox 4.1.22 on my 9.1RC3 AMD64 -
I get no traffic to the host interface at all. Did anyone noticed this
or related problems?
I have tried to watch the host interface with WireShark. I have
disabled local firewall. I have set net.inet.ip.forwarding=1
On 10-01-2013 05:56, ＊;sτóΡ〆~*~ξ wrote:
>��请�导
>
>���骤�
>
># portsnap fetch update
># cd /usr/ports/emulators/virtualbox-ose
># make install clean
>
>�路��认���OK�
>�
>
>pass -build programs
>pass -Libraries
>
���请�导
��骤��
# portsnap fetch update
# cd /usr/ports/emulators/virtualbox-ose
# make install clean
��路���认�OK��
���
pass -build programs
pass -Libraries
pass -DLLs
pass -Programs
Pass - install
kmk:*** NoRULE to make target '/usr/src/sys
jb gmail.com> writes:
>
> jb gmail.com> writes:
>
> > ...
>
> Next problem:
> the FB 9.1 dmesg differs on:
> - VB VM
> pnp bios: Bad PnP BIOS data checksum
> ...
> orm0: at iomem 0xc-0xc7fff pnpid ORM on isa0
Correction
> - on real hardware
> none of the above
dmesg:
...
isab0: at
On Sun, 6 Jan 2013 20:02:04 + (UTC), jb wrote:
> Polytropon edvax.de> writes:
>
> > ...
> > However, your transition of this knowledge to the terminology
> > to be used in combination with _virtual_ machines makes sense.
> > Maybe that wording is really not optimal. "Kill guest" matches
> >
Polytropon edvax.de> writes:
> ...
> However, your transition of this knowledge to the terminology
> to be used in combination with _virtual_ machines makes sense.
> Maybe that wording is really not optimal. "Kill guest" matches
> today's understanding, but could possibly be formed better in
> r
On Sun, 6 Jan 2013 19:02:43 + (UTC), jb wrote:
> Right, but the wordings are unfortunate and counterintuitive/misleading:
>
> 'Machine-Close-Send shutdown' means to 'shutdown -p now' (equivalent to
> 'poweroff') of Guest, followed by unforced "Close" of VM.
>
> 'Machine-Close-Power off' means
Matthew Seaman infracaninophile.co.uk> writes:
> ...
There is no problem with interface em0, NAT, manual/DHCP config, and ping or
traceroute.
jb
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-quest
Matthew Seaman FreeBSD.org> writes:
>
> On 06/01/2013 11:19, jb wrote:
> > Next problem:
> > when I am logged out from FB, and I do (I tested it repeatedly)
> >
> > Machine-Close-Power off the machine
> > to cloce VM with FB, then on subsequent VM Start and FB reboot I get error
> > msgs:
> > .
> /etc/rc: WARNING failed to start powerd
>
> Again -- standard for VirtualBox hosts: powerd doesn't work -- the guest
> OS can't control the frequency of the host CPU, which is what you'ld
> expect thinking about it.
>
> Just disable powerd in /etc/rc.conf to ge
jb gmail.com> writes:
> ...
Next problem:
the FB 9.1 dmesg differs on:
- VB VM
pnp bios: Bad PnP BIOS data checksum
...
orm0: at iomem 0xc-0xc7fff pnpid ORM on isa0
- on real hardware
none of the above
jb
___
freebsd-questions@freebsd.o
On Sun, 6 Jan 2013, Michael Powell wrote:
Matthew Seaman wrote:
On 06/01/2013 12:09, jb wrote:
A general question: to what extent is FB Install aware of installation
env (VB here) ?
If so, would it make sense to sanitize it to avoid offering install
options that are irrelevant/inappropriate ?
t PCI
Express, which is bge0 driver in FB.
How to force it to discover the right net device during install, and/or after
install ?
This is normal for VirtualBox -- it doesn't matter what NIC the host
has, VB always presents it as an em(4) interface to the guest.
Under Network/Adapter1/Advan
k at this:
http://www.virtualbsd.info/
This interesting project even skips the step of manual installation.
Instead it offers a fully functional image for VMware and VirtualBox.
It builds on the foundation of FreeBSD, instead of demanding a
change of the OS to fit one limited use case by predefin
On 01/06/2013 01:51 PM, Michael Powell wrote:
Michael Powell wrote:
[snip]
The converse may be applicable as well, that Vbox has configurability to
know a little something about the environment for the proposed guest. When
creating a new VM, you can choose BSD in the Operating System drop-down
Michael Powell wrote:
[snip]
>
> The converse may be applicable as well, that Vbox has configurability to
> know a little something about the environment for the proposed guest. When
> creating a new VM, you can choose BSD in the Operating System drop-down
> and then choose FreeBSD or FreebSD-64.
Michael Powell hotmail.com> writes:
> ...
> What I have not done is
> tried all the various partitioning schemes available under "Manual" config.
> Possibly one, such as Dos MBR or BSD disklabel which I have not tried, may
> be broken boot-loading wise. I only went straight down the GPT road.
Matthew Seaman wrote:
> On 06/01/2013 12:09, jb wrote:
>> A general question: to what extent is FB Install aware of installation
>> env (VB here) ?
>> If so, would it make sense to sanitize it to avoid offering install
>> options that are irrelevant/inappropriate ?
>
> This is FreeBSD. It doesn'
jb wrote:
[snip]
> But I also could not ping:
> $ ping -c 1 google.com
> I have VM-Settings-Network
> Attached to NAT
> What is the correct setting here ?
Vbox will not allow ping and/or traceroute type traffic through NAT. It
states this somewhere in the docs. This normal to NAT.
I've used bo
On 06/01/2013 12:09, jb wrote:
> A general question: to what extent is FB Install aware of installation env (VB
> here) ?
> If so, would it make sense to sanitize it to avoid offering install options
> that
> are irrelevant/inappropriate ?
This is FreeBSD. It doesn't hold your hand and wipe the
o configure the network;
>>> but my host has Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI
>>> Express, which is bge0 driver in FB.
>>> How to force it to discover the right net device during install, and/or
>>> after
>>> install ?
>> Thi
> /etc/rc: WARNING failed to start powerd
>
> Again -- standard for VirtualBox hosts: powerd doesn't work -- the guest
> OS can't control the frequency of the host CPU, which is what you'ld
> expect thinking about it.
>
> Just disable powerd in /etc/rc.conf to get
On 06/01/2013 11:19, jb wrote:
> Next problem:
> when I am logged out from FB, and I do (I tested it repeatedly)
>
> Machine-Close-Power off the machine
> to cloce VM with FB, then on subsequent VM Start and FB reboot I get error
> msgs:
> ...
> Trying to mount root from ufs:/dev/ada0s1a [rw]...
>
m Corporation NetLink BCM5787M Gigabit Ethernet PCI
> > Express, which is bge0 driver in FB.
> > How to force it to discover the right net device during install, and/or
> > after
> > install ?
>
> This is normal for VirtualBox -- it doesn't matter what NIC
On 06/01/2013 11:19, jb wrote:
> Next problem:
> I selected powerd service during install, but after boot, there was error msg:
> starting powerd
> powerd lookup freq: No such file or directory
> /etc/rc: WARNING failed to start powerd
Again -- standard for VirtualBox hosts: powe
is bge0 driver in FB.
> How to force it to discover the right net device during install, and/or after
> install ?
This is normal for VirtualBox -- it doesn't matter what NIC the host
has, VB always presents it as an em(4) interface to the guest.
Cheers,
Matthew
--
Dr M
jb gmail.com> writes:
>
> Hi,
>
> host=CentOS
> guest=FreeBSD in VirtualBox
>
> FB 9.1 installation seemed to be normal (there was a one page text at the end
> that quickly disappeared, but could not catch it ...),
Perhaps those messages I could not catch were rele
Hi,
host=CentOS
guest=FreeBSD in VirtualBox
FB 9.1 installation seemed to be normal (there was a one page text at the end
that quickly disappeared, but could not catch it ...),
virtual disk was set up as
ada0
ada0s1 BSD
ada0s1a /
ada0s1b swap
but after reboot:
No /boot/loader
FreeBSD/i386
t;>
>>>>> On Nov 29, 2012, at 6:43 PM, dweimer wrote:
>>>>>
>>>>>> I was trying to setup a test of CARP on two virtual machines running in
>>>>>> VirtualBox 4.2.4r81684 I am not sure if I have something wrong with my
>>>&
VirtualBox 4.2.4r81684 I am not sure if I have something wrong
with my CARP
configuration or if VirtualBox just doesn't work right with it.
I can only
ping the CARP interface IP address from the machine listed as
MASTER, if I
do an ifconfig carp0 down on the MASTER the other machine
corr
On 2012-11-30 13:44, dweimer wrote:
On 2012-11-29 14:07, dweimer wrote:
On 2012-11-29 12:53, Fleuriot Damien wrote:
On Nov 29, 2012, at 6:43 PM, dweimer wrote:
I was trying to setup a test of CARP on two virtual machines
running in VirtualBox 4.2.4r81684 I am not sure if I have something
On 2012-11-29 14:07, dweimer wrote:
On 2012-11-29 12:53, Fleuriot Damien wrote:
On Nov 29, 2012, at 6:43 PM, dweimer wrote:
I was trying to setup a test of CARP on two virtual machines
running in VirtualBox 4.2.4r81684 I am not sure if I have something
wrong with my CARP configuration or if
On 2012-11-29 14:47, Damien Fleuriot wrote:
On 29 Nov 2012, at 21:07, dweimer wrote:
On 2012-11-29 12:53, Fleuriot Damien wrote:
On Nov 29, 2012, at 6:43 PM, dweimer wrote:
I was trying to setup a test of CARP on two virtual machines
running in VirtualBox 4.2.4r81684 I am not sure if I
On 29 Nov 2012, at 21:07, dweimer wrote:
> On 2012-11-29 12:53, Fleuriot Damien wrote:
>> On Nov 29, 2012, at 6:43 PM, dweimer wrote:
>>
>>> I was trying to setup a test of CARP on two virtual machines running in
>>> VirtualBox 4.2.4r81684 I am not sure
On 2012-11-29 12:53, Fleuriot Damien wrote:
On Nov 29, 2012, at 6:43 PM, dweimer wrote:
I was trying to setup a test of CARP on two virtual machines running
in VirtualBox 4.2.4r81684 I am not sure if I have something wrong with
my CARP configuration or if VirtualBox just doesn't work
On Nov 29, 2012, at 6:43 PM, dweimer wrote:
> I was trying to setup a test of CARP on two virtual machines running in
> VirtualBox 4.2.4r81684 I am not sure if I have something wrong with my CARP
> configuration or if VirtualBox just doesn't work right with it. I can only
&
I was trying to setup a test of CARP on two virtual machines running in
VirtualBox 4.2.4r81684 I am not sure if I have something wrong with my
CARP configuration or if VirtualBox just doesn't work right with it. I
can only ping the CARP interface IP address from the machine listed as
M
On Mon, Nov 19, 2012 at 12:55 PM, Mario Lobo wrote:
> On Sun, 18 Nov 2012 20:07:44 -0500
> Fbsd8 wrote:
>
> Snip ...
>
> > So how can I run rpd on the freebsd host running the virtualbox
> > server system so I can access the configured vm? I this
> > configur
On Sun, 18 Nov 2012 20:07:44 -0500
Fbsd8 wrote:
Snip ...
> So how can I run rpd on the freebsd host running the virtualbox
> server system so I can access the configured vm? I this
> configuration even possible?
>
I'll give it one last shot.
CREATE/RUNNING <> ACCESSIN
ys the x11 server has to be
running on the host system. You do need an x11 server to access the QT4
GUI however it can reside on a remote system and even a Windows Box. Just
need the x11 libs locally that is it.
>
>
>>
>> So the bottom line is virtualbox=desktop.
>>&
andrew clarke wrote:
On Sun 2012-11-18 08:50:34 UTC-0500, Fbsd8 (fb...@a1poweruser.com) wrote:
By design virtualbox requires a desktop on the host to use the
virtualbox built in config screens and the only way to access a
configured and installed guest VM is from a remote PC with a desktop
Adam Vande More wrote:
On Sun, Nov 18, 2012 at 7:50 AM, Fbsd8 wrote:
So I was barking up the wrong tree. By design virtualbox requires a
desktop on the host to use the virtualbox built in config screens
False
One word answers have no meaning.
As I understand the VB manual there is only 2
On Mon, 19 Nov 2012 01:08:01 +1100
andrew clarke wrote:
> On Sun 2012-11-18 08:50:34 UTC-0500, Fbsd8 (fb...@a1poweruser.com) wrote:
>
> > By design virtualbox requires a desktop on the host to use the
> > virtualbox built in config screens and the only way to access a
On Sun 2012-11-18 08:50:34 UTC-0500, Fbsd8 (fb...@a1poweruser.com) wrote:
> By design virtualbox requires a desktop on the host to use the
> virtualbox built in config screens and the only way to access a
> configured and installed guest VM is from a remote PC with a desktop.
No, you c
On Sun, Nov 18, 2012 at 7:50 AM, Fbsd8 wrote:
>
> So I was barking up the wrong tree. By design virtualbox requires a
> desktop on the host to use the virtualbox built in config screens
False
> So the bottom line is virtualbox=desktop.
>
Since you can access it only by tra
Mario Lobo wrote:
On Sat, 17 Nov 2012 01:10:23 -0800
per...@pluto.rain.com wrote:
Adam Vande More wrote:
On Fri, Nov 16, 2012 at 3:18 PM, Fbsd8
wrote:
I do not run x11 or any desktop on my 9.0 host.
This would be your problem.
How so? Surely virtualbox _should_ be able to hand off a VT
On Sat, 17 Nov 2012 01:10:23 -0800
per...@pluto.rain.com wrote:
> Adam Vande More wrote:
> > On Fri, Nov 16, 2012 at 3:18 PM, Fbsd8
> > wrote:
> > > I do not run x11 or any desktop on my 9.0 host.
> >
> > This would be your problem.
>
> How so? Surely
On Sat, 17 Nov 2012 01:10:23 -0800
per...@pluto.rain.com wrote:
> XP itself, when running directly on the hardware, provides its own
> graphics environment. It should be able to do the same running on
> a VM with a virtualized keyboard, mouse, and display.
Yes, but the virtualised displa
On Sat, Nov 17, 2012 at 3:10 AM, wrote:
> Adam Vande More wrote:
> > On Fri, Nov 16, 2012 at 3:18 PM, Fbsd8 wrote:
> > > I do not run x11 or any desktop on my 9.0 host.
> >
> > This would be your problem.
>
> How so? Surely virtualbox _should_ be able to
Adam Vande More wrote:
> On Fri, Nov 16, 2012 at 3:18 PM, Fbsd8 wrote:
> > I do not run x11 or any desktop on my 9.0 host.
>
> This would be your problem.
How so? Surely virtualbox _should_ be able to hand off a VT to the
XP guest, for it to use as a keyboard, mouse, and
On Fri, 16 Nov 2012 16:18:10 -0500
Fbsd8 wrote:
> >>>>
> >>>> Section 23.3 of the handbook speaks about FreeBSD as a host.
> >>>> No where in that section does it say anything about virtualbox
> >>>> running from the FreeBSD host comma
.0 from scratch
> again. I read a post on this list where it was suggested to run
> Virtualbox on my 9.0 host and then run XP as a guest. I want to boot the
> 9.0 host and login to the 9.0 host, start the Virtualbox XP guest and
> enter the XP guest [IE: be in the XP OS windows envi
On Fri, Nov 16, 2012 at 1:18 PM, Fbsd8 wrote:
>
>>>>> Section 23.3 of the handbook speaks about FreeBSD as a host.
>>>>> No where in that section does it say anything about virtualbox
>>>>> running from the FreeBSD host command line or fro
Section 23.3 of the handbook speaks about FreeBSD as a host.
No where in that section does it say anything about virtualbox
running from the FreeBSD host command line or from A Desktop.
Do I need a Desktop for virtualbox to run under?
NOPE !!
VBoxHeadless -startvm "vm name"
On Fri, 16 Nov 2012 10:44:54 -0500
Fbsd8 wrote:
> Mario Lobo wrote:
> > On Fri, 16 Nov 2012 09:57:53 -0500
> > Fbsd8 wrote:
> >
> >> Section 23.3 of the handbook speaks about FreeBSD as a host.
> >> No where in that section does it say anything about v
On Fri, 16 Nov 2012 10:44:54 -0500
Fbsd8 wrote:
> Mario Lobo wrote:
> > On Fri, 16 Nov 2012 09:57:53 -0500
> > Fbsd8 wrote:
> >
> >> Section 23.3 of the handbook speaks about FreeBSD as a host.
> >> No where in that section does it say anything about v
Mario Lobo wrote:
On Fri, 16 Nov 2012 09:57:53 -0500
Fbsd8 wrote:
Section 23.3 of the handbook speaks about FreeBSD as a host.
No where in that section does it say anything about virtualbox
running from the FreeBSD host command line or from A Desktop.
Do I need a Desktop for virtualbox to
On Fri, 16 Nov 2012 09:57:53 -0500
Fbsd8 wrote:
> Section 23.3 of the handbook speaks about FreeBSD as a host.
> No where in that section does it say anything about virtualbox
> running from the FreeBSD host command line or from A Desktop.
>
> Do I need a Desktop for virtualb
Section 23.3 of the handbook speaks about FreeBSD as a host.
No where in that section does it say anything about virtualbox
running from the FreeBSD host command line or from A Desktop.
Do I need a Desktop for virtualbox to run under?
___
freebsd
On Wed, 31 Oct 2012 10:58:54 +1100, Lachlan Holmes wrote:
> Hey all,
>
> If you can help 'd really appreciate it.
>
> I have a 9.0 release 64bit freebsd. I've done a Portsnap fetch extract and
> freebsd-update.
>
> I can't get virtualbox-ose-additi
On Wed, 31 Oct 2012, Lachlan Holmes wrote:
Hey all,
If you can help 'd really appreciate it.
I have a 9.0 release 64bit freebsd. I've done a Portsnap fetch extract and
freebsd-update.
I can't get virtualbox-ose-additions to install I get this error message.
# mak
Hey all,
If you can help 'd really appreciate it.
I have a 9.0 release 64bit freebsd. I've done a Portsnap fetch extract and
freebsd-update.
I can't get virtualbox-ose-additions to install I get this error message.
# make install clean
===> virtualbox-ose-additions-4.1.
2012-10-09 03:05, Michael Hughes skrev:
On Sun, 07 Oct 2012 05:49:19 +0200
Bernt Hansson wrote:
Hello list!
When I try to start a virtual os in virtualbox i get an error.
kldload vboxdrv.ko
kldload: can't load vboxdrv.ko: Exec format error
Rebuilt VB and still this error
8.2-S
On Sun, 07 Oct 2012 05:49:19 +0200
Bernt Hansson wrote:
> Hello list!
>
> When I try to start a virtual os in virtualbox i get an error.
>
> kldload vboxdrv.ko
> kldload: can't load vboxdrv.ko: Exec format error
>
> Rebuilt VB and still this error
>
> 8.
At 10:49 PM 10/6/2012, Bernt Hansson wrote:
Hello list!
When I try to start a virtual os in virtualbox i get an error.
kldload vboxdrv.ko
kldload: can't load vboxdrv.ko: Exec format error
Rebuilt VB and still this error
8.2-STABLE FreeBSD 8.2-STABLE #0: Thu Jan 12 15:13:06 CET 2012
GE
On Sun, 7 Oct 2012, Bernt Hansson wrote:
Hello list!
When I try to start a virtual os in virtualbox i get an error.
kldload vboxdrv.ko
kldload: can't load vboxdrv.ko: Exec format error
Rebuilt VB and still this error
8.2-STABLE FreeBSD 8.2-STABLE #0: Thu Jan 12 15:13:06 CET 2012
GE
On Sat, Oct 6, 2012 at 10:49 PM, Bernt Hansson wrote:
> When I try to start a virtual os in virtualbox i get an error.
>
> kldload vboxdrv.ko
> kldload: can't load vboxdrv.ko: Exec format error
>
> Rebuilt VB and still this error
>
> 8.2-STABLE FreeBSD 8.2-STABLE #0:
Hello list!
When I try to start a virtual os in virtualbox i get an error.
kldload vboxdrv.ko
kldload: can't load vboxdrv.ko: Exec format error
Rebuilt VB and still this error
8.2-STABLE FreeBSD 8.2-STABLE #0: Thu Jan 12 15:13:06 CET 2012
GENERIC
On 2012-09-28 12:06, Warren Block wrote:
On Thu, 27 Sep 2012, Mike Jeays wrote:
I have been running PC-BSD 9.0 with the KDE interface in a
VirtualBox VM, and notice that it uses CPU resources when idle,
driving up my CPU temperature about 15 degrees on an otherwise idle
machine. (It is an
On Thu, 27 Sep 2012, Mike Jeays wrote:
I have been running PC-BSD 9.0 with the KDE interface in a VirtualBox
VM, and notice that it uses CPU resources when idle, driving up my CPU
temperature about 15 degrees on an otherwise idle machine. (It is an
Intel i5 quad four). Is this to be expected
On 2012-09-28 07:03, Rares Aioanei wrote:
On Thu, 27 Sep 2012 22:56:42 -0400
Mike Jeays wrote:
I have been running PC-BSD 9.0 with the KDE interface in a
VirtualBox
VM, and notice that it uses CPU resources when idle, driving up my
CPU temperature about 15 degrees on an otherwise idle
On Thu, 27 Sep 2012 22:56:42 -0400
Mike Jeays wrote:
> I have been running PC-BSD 9.0 with the KDE interface in a VirtualBox
> VM, and notice that it uses CPU resources when idle, driving up my
> CPU temperature about 15 degrees on an otherwise idle machine. (It is
> an Intel i5 qu
[ Mike Jeays wrote on Thu 27.Sep'12 at 22:56:42 -0400 ]
> I have been running PC-BSD 9.0 with the KDE interface in a VirtualBox VM, and
> notice that it uses CPU resources when idle, driving up my CPU temperature
> about 15 degrees on an otherwise idle machine. (It is an Inte
I have been running PC-BSD 9.0 with the KDE interface in a VirtualBox VM, and
notice that it uses CPU resources when idle, driving up my CPU temperature
about 15 degrees on an otherwise idle machine. (It is an Intel i5 quad four).
Is this to be expected
Hi,
I got a VM VirtualBox that use FreeBSD 9-STABLE (updated yesterday).
Now I want to update my ports, but I can't update
I use the command <# portmaster -a -D --no-confirm> to update ports with
portmaster tool.
The error is :
[...]
The failing command:
@cc -m6
Hi,
I have the same error with virtualbox-ose-kmod 4.1.10 but only with FreeBSD
8.0 and 8.0-p2.
With FreeBSD 8.2, no problem.
Hope this help you for investigating this "bug" since I need it working on
FreeBSD 8.0.
Regards
--
View this message in context:
http://freebsd.1045724.n5.
Bernhard Froehlich writes:
> Pointyhat has triggered the same compile error so it is real. Probably
> avg has a clue how to fix it.
A (quick) look at pointyhat only shows me amd64 errors.
My main build server (on amd64, building for i386 and amd64) doesn't see
those problems, and neither does
On Wednesday 21 March 2012, Lowell Gilbert wrote:
> > /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-
> >4.1.10/out/freebsd.x86/
> >
> > release/bin/src/vboxdrv/r0
Mike Clarke writes:
> On Friday 16 March 2012, Lowell Gilbert wrote:
>
>> My best advice is: clean out the directory for that port, update
>> again, and see if the problem is the same.
>
> I've now deleted everything in /usr/ports/emulators/virtualbox-ose-kmod and
On Friday 16 March 2012, Adam Vande More wrote:
> On Tue, Mar 13, 2012 at 9:13 AM, Mike Clarke
wrote:
> > in
> > /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-
> >4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv.
> >
> > I ran portsnap im
On Friday 16 March 2012, Lowell Gilbert wrote:
> My best advice is: clean out the directory for that port, update
> again, and see if the problem is the same.
I've now deleted everything in /usr/ports/emulators/virtualbox-ose-kmod and
downloaded a fresh copy of the
port (4.1.1
On Tue, Mar 13, 2012 at 9:13 AM, Mike Clarke wrote:
>
> in
> /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv.
>
> I ran portsnap immediately before portmaster so my ports are up to date.
>
> Any suggestio
-mno-3dnow -mno-sse -mno-sse2
>> -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999
>> -fstack-protector -Wall -Wredundant-decls -Wnested-externs
>> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
>> -Wcast-qual -Wundef -Wno-pointer-sign -ff
ctor -std=iso9899:1999
> -fstack-protector -Wall -Wredundant-decls -Wnested-externs
> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c
> /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/Virtual
-externs -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign
-fformat-extensions -c
/data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c
/data1
>> Hello,
>> Was running 8.2 and virtualbox 3 - wiped Freebsd 8.2, installed 9.0,
>> installed latest virtualbox port 4.0.14 and the networking broke in my
>> vms.
>>
>> Setup I had:
>>
>> {vm1,vm2,etc}---> vbox internal network -> em2[fi
1 - 100 of 424 matches
Mail list logo
