Re: bhyve cannot allocate memory

2014-11-23 Thread Shawn Webb
On Sat, 22 Nov 2014 19:57:07 -0800 Peter Grehan gre...@freebsd.org wrote: Hi Shawn, Interesting. I'll have to do more digging. Because removing map_at_zero support is the same as keeping it at the default of 0. It's not possible that our ASLR implementation is affecting bhyve, since our

Re: bhyve cannot allocate memory

2014-11-23 Thread Peter Grehan
Oliver fixed the problem. bhyve's vmm.ko uses VM_MIN_ADDRESS, which defaults to NULL in FreeBSD. We modified that to be at 64k to prevent NULL dereferences. Combine that with the removal of map_at_zero, NULL deref is not possible anymore. But since we bumped VM_MIN_ADDRESS up, bhyve's vmm.ko no

cu -l /dev/nmdm not setting rows and columns

2014-11-23 Thread Craig Rodrigues
Hi, I am configuring bhyve VM's with serial consoles directing to /dev/nmdm[n]. I am using cu -l /dev/nmdm[n]B to connect to the console. However, cu does not properly set the value of the rows and columns of my screen. For example, before connecting: # stty -a speed 9600 baud; 30 rows; 91

Re: cu -l /dev/nmdm not setting rows and columns

2014-11-23 Thread Peter Grehan
Hi Craig, # stty -a speed 9600 baud; 0 rows; 0 columns; # echo $TERM dialup Any idea how I can fix this? The console inside the VM is quite unusable when it does not have the correct rows/colums set. Not sure how you're getting 'dialup' as the terminal type: the default ttys file for 10.1