Summary: | devd: Cannot parse /etc/devd.conf at line 202 | ||
---|---|---|---|
Product: | Base System | Reporter: | Maciej Sobczak <prog> |
Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed Not Enough Information | ||
Severity: | Affects Only Me | CC: | dch, zmey20000 |
Priority: | Normal | ||
Version: | Unspecified | ||
Hardware: | Any | ||
OS: | Any |
Description
Maciej Sobczak
2013-12-19 15:50:00 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 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) For bugs matching the following conditions: - Status == In Progress - Assignee == "bugs@FreeBSD.org" - Last Modified Year <= 2017 Do - Set Status to "Open" 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. |