Replying to myself here for the edification of those interested.
A value of 320 for NKPT eliminated this crash, set in the
kernel config file:
options NKPT=320
For those of you with large ramdisk booting requirements, this
one option will likely save you hours of trial and
hi, anyone test freebsd as guest on kvm with virtio drivers? any expirience?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Hi,
CloudSigma has a very good kvm platform with virtio support in Switzerland and
Las Vegas, and very good SLA.
We've been using it for more than a year now and performance has been very
consistent, even when there was no virtio support yet.
You can try it for a week for free, with 2,5ghz,
Bane Ivosev (bane.ivosev) writes:
hi, anyone test freebsd as guest on kvm with virtio drivers? any expirience?
http://forums.freebsd.org/archive/index.php/t-28916.html
Cheers,
Phil
___
freebsd-stable@freebsd.org mailing list
I'm running stable that I built 1/12/12 on an amd64 system and I just updated
the sources and now every time I try to compile the kernel I get the error:
=
cc1: warnings being treated as errors
/usr/src/sys/x86/pci/pci_bus.c:118: warning: no previous prototype for
I discovered that my copy of src/sys/amd64/include/legacyvar.h does not
include the two lines
60| int legacy_pcib_map_msi(device_t pcib, device_t dev, int irq,
61| uint64_t *addr, uint32_t *data);
which is in the stable sources available through svn at
On Tuesday, May 01, 2012 12:22:17 pm James Hall wrote:
I discovered that my copy of src/sys/amd64/include/legacyvar.h does not
include the two lines
60| int legacy_pcib_map_msi(device_t pcib, device_t dev, int irq,
61| uint64_t *addr, uint32_t *data);
which is in the stable sources
On May 1, 2012 11:32 AM, John Baldwin j...@freebsd.org wrote:
On Tuesday, May 01, 2012 12:22:17 pm James Hall wrote:
I discovered that my copy of src/sys/amd64/include/legacyvar.h does not
include the two lines
60| int legacy_pcib_map_msi(device_t pcib, device_t dev, int irq,
61|
Hello,
So, I've been trying to debug an issue running nmap scans within jails,
partially documented here:
http://seclists.org/nmap-dev/2012/q2/220
On further debugging, it's seeming like jails can't read routing
information directly at all:
# route get 69.163.203.254
route: writing to
On 1. May 2012, at 19:41 , David Thiel wrote:
Hello,
So, I've been trying to debug an issue running nmap scans within jails,
partially documented here:
http://seclists.org/nmap-dev/2012/q2/220
On further debugging, it's seeming like jails can't read routing
information directly at
On Tue, May 01, 2012 at 09:01:33PM +, Bjoern A. Zeeb wrote:
On 1. May 2012, at 19:41 , David Thiel wrote:
Hello,
So, I've been trying to debug an issue running nmap scans within jails,
partially documented here:
http://seclists.org/nmap-dev/2012/q2/220
On further
11 matches
Mail list logo
