jb jb.1234abcd at gmail.com writes:
jb jb.1234abcd at gmail.com writes:
...
Next problem:
the FB 9.1 dmesg differs on:
- VB VM
pnp bios: Bad PnP BIOS data checksum
...
orm0: ISA Option ROM at iomem 0xc-0xc7fff pnpid ORM on isa0
Correction
- on real hardware
none of the
jb jb.1234abcd at 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 relevant, because it seems
On 06/01/2013 11:19, jb wrote:
Next problem:
the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and
this is how install offers to configure the network;
but my host has Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI
Express, which is bge0 driver in FB.
How
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: powerd doesn't work -- the
Matthew Seaman matthew at FreeBSD.org writes:
On 06/01/2013 11:19, jb wrote:
Next problem:
the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and
this is how install offers to configure the network;
but my host has Broadcom Corporation NetLink BCM5787M Gigabit
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]...
Matthew Seaman matthew at FreeBSD.org writes:
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
On 06/01/2013 11:52, jb wrote:
Matthew Seaman matthew at FreeBSD.org writes:
On 06/01/2013 11:19, jb wrote:
Next problem:
the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and
this is how install offers to configure the network;
but my host has Broadcom Corporation
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
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 both
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't hold
Michael Powell nightrecon at 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
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.
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
On Sun, 6 Jan 2013 12:09:12 + (UTC), jb wrote:
A general question: to what extent is FB Install aware of installation env (VB
here) ?
FreeBSD can only detect hardware certainly to a specific point.
The idea behind virtualization is that it presents non-existent
devices as if they were real.
On Sun, 6 Jan 2013, Matthew Seaman wrote:
On 06/01/2013 11:19, jb wrote:
Next problem:
the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and
this is how install offers to configure the network;
but my host has Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI
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
jb jb.1234abcd at gmail.com writes:
...
Next problem:
the FB 9.1 dmesg differs on:
- VB VM
pnp bios: Bad PnP BIOS data checksum
...
orm0: ISA Option ROM at iomem 0xc-0xc7fff pnpid ORM on isa0
- on real hardware
none of the above
jb
___
Matthew Seaman matthew at FreeBSD.org writes:
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
Matthew Seaman matthew at 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:
...
Matthew Seaman m.seaman at 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
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 Kill
Polytropon freebsd at 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
On Sun, 6 Jan 2013 20:02:04 + (UTC), jb wrote:
Polytropon freebsd at 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
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
25 matches
Mail list logo
