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:
> > .
Matthew Seaman 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
>
> A
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 ?
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
Exp
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 re
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
On 06/01/2013 11:52, jb wrote:
> Matthew Seaman 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 Corp
Matthew Seaman 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
>
> A
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 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 Eth
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 --
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.
>
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 relevant, because it seems
that
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 boot
Hi Gary
Thanks for your help. I am perplexed and frustrated
by BSD's bootloader :)
>> boot0cfg -B -s 5 -o packet ad0
>> boot0cfg -B -s 2 -o packet ad2
I did't try those yet because I wanted to see if you
could find a problem first.
I'll try those in a bit.
In the mean time I created a GRUB IS
John Do <[EMAIL PROTECTED]> writes:
fdisk, etc, looked good.
> boot0cfg -v /dev/ad0
>
> # flag | start chs | type| end chs
>| offset | size
> 1 0x80 0: 1:10x07 1023 254:63 63
> 40001787
OK.
> boot0cfg -v /dev/ad2
>
> # f
Hi Gary and Glen,
I have the output. It was sure tiring to write out
and then type back though :)
bsdlabel /dev/ad2s1:
No Valid Label
bsdlabel /dev/ad2s2:
8 partitions
# size offset fstype [fsizebsize
bps/cpg]
a: 8191983 0 4.2BSD 2048 16384
28552
b:
Glenn Dawson <[EMAIL PROTECTED]> writes:
>>boot0cfg -B -s 5 ad0
>>boot0cfg -B -s 2 ad2
I don't remember who asked what before, but you should also try:
boot0cfg -B -s 5 -o packet ad0
boot0cfg -B -s 2 -o packet ad2
> fdisk /dev/ad0
> fdisk /dev/ad2
> bsdlabel /dev/ad0
I wouldn't bother if you d
At 12:00 AM 9/18/2005, John Do wrote:
Hi guys
I still can't boot BSD :(
I have tried everything I can and bla bla read etc etc
:(
Here is the setup (I boot off ad0)
ad0 - boot loader and Windows XP
ad2 slice 2 - FreeBSD Install
Exactly from the emergency shell do I need to type to
configure
Hi guys
I still can't boot BSD :(
I have tried everything I can and bla bla read etc etc
:(
Here is the setup (I boot off ad0)
ad0 - boot loader and Windows XP
ad2 slice 2 - FreeBSD Install
Exactly from the emergency shell do I need to type to
configure the bootloader so it gives the option of
31 matches
Mail list logo
