Bug 184999 - devd: Cannot parse /etc/devd.conf at line 202
Summary: devd: Cannot parse /etc/devd.conf at line 202
Status: Closed Not Enough Information
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-19 15:50 UTC by Maciej Sobczak
Modified: 2019-01-17 09:51 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Sobczak 2013-12-19 15:50:00 UTC
i386 system (10.0 RC2) was installed in the VirtualBox and from the first boot after installation there is a message as in synopsis.
Interestingly, when the /etc/devd.conf file is viewed with less, no problem can be seen, but vi shows a very long series of ^@ special characters from the middle of the 202 line.

Problem is repeatable.

It looks like there is some problem with text parsing.
The system does not work properly due to this (no network, for example).

Note a similar discussion:

http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044816.html

Note: 9.2-RELEASE (i386) works fine in the same environment.
Comment 1 barbara.freebsd 2014-01-06 12:43:44 UTC
I've lost a lot of time some days ago with similar problems
(vbox+10.0+i386), so maybe it is still worth replying.

Try with #1 here:
http://lists.freebsd.org/pipermail/freebsd-current/2013-October/046081.html
It's just a workaround and with this setting you are forced to set 1
CPU only, and without virtualization extensions the VM will be slow.

I hope that this will help to shed some light on the problem.

Maybe also all the problems reported here have the same root (not sure
the OP is running on VirtualBox):
http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044776.html
Comment 2 zmey20000 2014-11-21 11:30:59 UTC
This is not a FreeBSD problem. You need to check virtualisation settings and enable proper options at the BIOS of your system (depends of your hardware).

When you run Virtualbox on 64-bit system, indicator of wrong configuration may be that Virtualbox "allows" to create only x86 virtual systems, but not 64-bit architectures. See: http://mezzantrop.wordpress.com/2014/11/21/virtualbox-intel-core-i5-and-corrupted-devd-on-freebsd-10-x/ (sorry for Russian language)
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-05-20 23:52:58 UTC
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "bugs@FreeBSD.org"
- Last Modified Year <= 2017

Do
- Set Status to "Open"
Comment 4 Dave Cottlehuber freebsd_committer 2019-01-17 09:51:05 UTC
Maciej thanks for reporting this, there's been no update from your side since last comments so I'm closing this at present but please feel free to re-open this if you're still hitting issues.