Re: Problem with Vbox after recent upgrade

2012-07-20 Thread Lukasz Wojcik
On 07/20/12 03:31, AN wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #27 r238629: Thu Jul 19 21:07:44 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 After a recent upgrade, when I try to start a VM it fails with: Failed to open a session for the virtual machine OpenSuse11.4.

Re: Script to monitor battery status on X220

2012-07-20 Thread Erich Dollansky
Hi, On Friday 20 July 2012 12:31:08 Lars Engels wrote: > On Fri, Jul 20, 2012 at 10:04:59AM +0700, Erich Dollansky wrote: > > Hi, > > > > I forget yesterday to share these two scripts: > > > > http://www.alogreentechnologies.com/freebsd/checkbattery > > > > checks the battery status of an X220

Re: Script to monitor battery status on X220

2012-07-20 Thread Matthias Apitz
El día Friday, July 20, 2012 a las 03:45:23PM +0700, Erich Dollansky escribió: > > ... > > Is it necessary to poll? Usually devd generates an event when the > > battery status and/or percentage changes. Just read the events from > > /var/run/devd.pipe. > > > this is a good idea. I did not like t

Re: Script to monitor battery status on X220

2012-07-20 Thread Erich Dollansky
Hi, On Friday 20 July 2012 16:13:56 Matthias Apitz wrote: > El día Friday, July 20, 2012 a las 03:45:23PM +0700, Erich Dollansky escribió: > > > > ... > > > Is it necessary to poll? Usually devd generates an event when the > > > battery status and/or percentage changes. Just read the events from

usb plugin msg class

2012-07-20 Thread Fbsd8
In 8.x and older when I plugged in my usb thumb drive I got some messages on the console. But in 9.0 and 9.1 those message no longer show up on my console. I have a custom /etc/syslog.conf Did the message class of those usb plug-in message change between 8.x and 9.x? IE as defined in /etc/sysl

Re: usb plugin msg class

2012-07-20 Thread Erich Dollansky
Hi, On Friday 20 July 2012 21:34:42 Fbsd8 wrote: > In 8.x and older when I plugged in my usb thumb drive I got some > messages on the console. But in 9.0 and 9.1 those message no longer show > up on my console. I have a custom /etc/syslog.conf > > Did the message class of those usb plug-in mess

-current build failure

2012-07-20 Thread Kim Culhan
Seeing this for r:238655 ===> dtrace/dtrace (depend) @ -> /usr/src/sys machine -> /usr/src/sys/amd64/include x86 -> /usr/src/sys/x86/include awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk

Re: -current build failure

2012-07-20 Thread Dimitry Andric
On 2012-07-20 16:49, Kim Culhan wrote: > Seeing this for r:238655 ... > In file included from > /usr/src/sys/modules/dtrace/dtrace/../../../sys/pcpu.h:44: > ./machine/pcpu.h:226:13: error: indirection of non-volatile null > pointer will be deleted, not trap > [-Werror,-Wnull-dereference] >

Re: -current build failure

2012-07-20 Thread Konstantin Belousov
On Fri, Jul 20, 2012 at 05:40:32PM +0200, Dimitry Andric wrote: > On 2012-07-20 16:49, Kim Culhan wrote: > > Seeing this for r:238655 > ... > > In file included from > > /usr/src/sys/modules/dtrace/dtrace/../../../sys/pcpu.h:44: > > ./machine/pcpu.h:226:13: error: indirection of non-volatile null

Re: Awful FreeBSD 9 block IO performance in KVM

2012-07-20 Thread Adrian Chadd
On 19 July 2012 11:27, Richard Yao wrote: > Dear Everyone, > > FreeBSD 9 has awful block IO performance in KVM. I have experienced it > and others have experienced it. Someone posted slides to slideshare with > benchmarks documenting it: > > http://www.slideshare.net/TakeshiHasegawa1/runningfreebs

Re: -current build failure

2012-07-20 Thread David Chisnall
On 20 Jul 2012, at 17:33, Konstantin Belousov wrote: > It is not related to dtrace at all, and indeed OFFSETOF_CURTHREAD is 0. > This is a bug in clang, we compile our kernel in freestanding environment. The copies of the C spec that I have do not differentiate between freestanding and hosted en

Re: Awful FreeBSD 9 block IO performance in KVM

2012-07-20 Thread Richard Yao
On 07/20/2012 03:44 PM, Adrian Chadd wrote: > On 19 July 2012 11:27, Richard Yao wrote: >> Dear Everyone, >> >> FreeBSD 9 has awful block IO performance in KVM. I have experienced it >> and others have experienced it. Someone posted slides to slideshare with >> benchmarks documenting it: >> >> htt

delay for switch of current [was Re: [HEADSUP & CFT] pkg 1.0rc1 and schedule]

2012-07-20 Thread Baptiste Daroussin
Hi, [...] > > The plan is to switch the ports tree to pkgng on CURRENT by default on July > 25th > No dates are planned yet for other branches. > > Note that there will be a NO_PKGNG knob for some time (undefined yet) for > people > not will to switch on July 25th > [...] Because I won't hav

Re: Awful FreeBSD 9 block IO performance in KVM

2012-07-20 Thread Adrian Chadd
On 20 July 2012 15:26, Richard Yao wrote: > I am in the process of setting up a VM instance specifically for this. > While installing it, I noticed that qemu-kvm printed 'lsi_scsi: error: > ORDERED queue not implemented', which might be a clue as to why the > block device performance is bad. > >

Re: -current build failure

2012-07-20 Thread Konstantin Belousov
On Fri, Jul 20, 2012 at 10:07:05PM +0100, David Chisnall wrote: > On 20 Jul 2012, at 17:33, Konstantin Belousov wrote: > > > It is not related to dtrace at all, and indeed OFFSETOF_CURTHREAD is 0. > > This is a bug in clang, we compile our kernel in freestanding environment. > > The copies of the

Re: MPSAFE VFS -- List of upcoming actions

2012-07-20 Thread Antony Mawer
On Wed, Jul 18, 2012 at 6:45 PM, Attilio Rao wrote: > 2012/7/18, Gustau Pérez i Querol : >> >> Sorry fo the delay. >> >> About the ntfs support, I'd go with fuse and leave the most relevant >> filesystems in kernel space. In fact filesystems not particulary >> specific and not tied our ker

PCIe hotplug

2012-07-20 Thread Julian Elischer
Is anyone looking at PCIe hotplug support? I'm especially interested if anyone has a strategy for device re-insertion and reassociating the reinserted device with its old device_t so that it gets the same unit number.. (assumes access to a serial number or similar) Even if it is put back into