Re: Problem with Vbox after recent upgrade
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.
The virtual machine 'OpenSuse11.4' has terminated unexpectedly during
startup with exit code 1.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Machine
Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}
Kernel driver not installed(rc=-1908)
Make sure the kernel module has been loading successfully
If I try to load vboxdrv.ko manually I get:
# kldload vboxdrv.ko
kldload: can't load vboxdrv.ko: Exec format error
# kldstat
Id Refs Address Size Name
1 16 0x8020 d0deb8 kernel
2 1 0x80f0e000 10ae520 nvidia.ko
3 3 0x81fbd000 48558 linux.ko
4 1 0x82212000 3df6 linprocfs.ko
# cat /boot/loader.conf
loader_logo=beastie
nvidia_load="YES"
vboxdrv_load="YES"
Vbox had been running fine before the upgrade.
# dmesg |grep vbox
KLD file vboxdrv.ko - could not finalize loading
Apparently the vbox kernel module is failing to load.
Any help is appreciated.
*
Additional info:
From log file
Jul 19 21:06:07 FBSD10 kernel: link_elf_obj: symbol vm_contig_grow_cache
undefined
Jul 19 21:06:07 FBSD10 kernel: linker_load_file: Unsupported file type
Dmesg:
Jul 19 21:22:58 FBSD10 kernel: FreeBSD 10.0-CURRENT #27 r238629: Thu Jul
19 21:07:44 EDT 2012
Jul 19 21:22:58 FBSD10 kernel: root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL
amd64
Jul 19 21:22:58 FBSD10 kernel: link_elf_obj: symbol vm_contig_grow_cache
undefined
Jul 19 21:22:58 FBSD10 kernel: KLD file vboxdrv.ko - could not finalize
loading
# kldload vboxdrv.ko
kldload: can't load vboxdrv.ko: Exec format error
Just a guess, maybe this commit is the issue?
http://svnweb.freebsd.org/base?view=revision&revision=238617
Hi,
I find it rather unlikely for this commit to be responsible. I think the
important part might be:
> Jul 19 21:06:07 FBSD10 kernel: link_elf_obj: symbol vm_contig_grow_cache
Thus suggesting this one:
http://svnweb.freebsd.org/base?view=revision&revision=238561
as a potential problem.
--
Lukasz Wojcik
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Script to monitor battery status on X220
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 and shuts the machine down when the > > battery falls to 2% or below. > > > > The status is checked every minute. > > > > It calls the following script to shut the machine down: > > > > http://www.alogreentechnologies.com/freebsd/poweroff > > > > You must run the first script as root to enable it to power the machine off > > at the end. > > > > I found that the battery life of my machine was higher using a simple > > window manager like blackbox compared to things like GNOME or KDE. This > > might depend on the usage pattern. > > > > Erich > > 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 this solution either but did not get a better idea when I did it. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Script to monitor battery status on X220
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 this solution either but did not get a > better idea when I did it. I wrote and used something similar for my netbook EeePC 900; it turned out that the battery is not showing the remaining capacity in a linear way; the last 5% are 'consumed' in a few seconds, i.e. below 20% I polled every 2 seconds; matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Script to monitor battery status on X220
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 > > > /var/run/devd.pipe. > > > > > this is a good idea. I did not like this solution either but did not get a > > better idea when I did it. > > I wrote and used something similar for my netbook EeePC 900; it turned > out that the battery is not showing the remaining capacity in a linear this is also true on the X220. > way; the last 5% are 'consumed' in a few seconds, i.e. below 20% I > polled every 2 seconds; I did some tests until I ended at the 2%. There was always enough energy left in the battery to restart the machine. I wonder anyway how they do it. I developed battery monitors a long time ago. As the voltage drop is not linear and the tolerances are very high. They might calibrate each battery when it reaches certain levels. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
usb plugin msg class
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/syslog.conf If their in a new class what is it? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: usb plugin msg class
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 message change between 8.x > and 9.x? IE as defined in /etc/syslog.conf > > If their in a new class what is it? I do not know. I only know that it works with the following configuration: # $FreeBSD$ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.warning;auth.notice;mail.crit/dev/console *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog lpr.info/var/log/lpd-errs ftp.info/var/log/xferlog cron.* /var/log/cron *.=debug/var/log/debug.log *.emerg * # uncomment this to log all writes to /dev/console to /var/log/console.log #console.info /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work #*.*/var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.*@loghost # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err # news.notice /var/log/news/news.notice !ppp *.* /var/log/ppp.log !* The file is the from a default installation of 10. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
-current build failure
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 -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h ln -sf /usr/obj/usr/src/sys/hyster3/opt_compat.h opt_compat.h ln -sf /usr/obj/usr/src/sys/hyster3/opt_kstack_pages.h opt_kstack_pages.h ln -sf /usr/obj/usr/src/sys/hyster3/opt_nfs.h opt_nfs.h ln -sf /usr/obj/usr/src/sys/hyster3/opt_hwpmc_hooks.h opt_hwpmc_hooks.h clang -c -O2 -pipe -DDIS_MEM -DSMP -DDEBUG -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/contrib/opensolaris/uts/intel -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/compat/opensolaris -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/dev/dtrace -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/dev/dtrace/amd64 -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/contrib/opensolaris/uts/common -I/usr/src/sys/modules/dtrace/dtrace/../../.. -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/hyster3/opt_global.h -I. -I@ -I@/contrib/altq -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/hyster3 -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-unknown-pragmas @/amd64/amd64/genassym.c In file included from @/amd64/amd64/genassym.c:46: In file included from /usr/src/sys/modules/dtrace/dtrace/../../../sys/buf.h:262: In file included from /usr/src/sys/modules/dtrace/dtrace/../../../cddl/compat/opensolaris/sys/proc.h:34: In file included from /usr/src/sys/modules/dtrace/dtrace/../../../sys/proc.h:62: In file included from /usr/src/sys/modules/dtrace/dtrace/../../../cddl/compat/opensolaris/sys/pcpu.h:33: 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] : "m" (*(char *)OFFSETOF_CURTHREAD)); ^~~ ./machine/pcpu.h:226:13: note: consider using __builtin_trap() or qualifying pointer with 'volatile' 1 error generated. *** [genassym.o] Error code 1 Stop in /usr/src/sys/modules/dtrace/dtrace. *** [depend] Error code 1 thanks -kim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: -current build failure
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] > : "m" (*(char *)OFFSETOF_CURTHREAD)); >^~~ > ./machine/pcpu.h:226:13: note: consider using __builtin_trap() or > qualifying pointer with 'volatile' That's indeed a valid warning from clang, since OFFSETOF_CURTHREAD is usually zero. It's probably due to recent work on dtrace. I'm not in the neighborhood of a FreeBSD box right now to verify, but can you please try to change the cast to "(volatile char *)"? That should fix the warning. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: -current build failure
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 > > pointer will be deleted, not trap > > [-Werror,-Wnull-dereference] > > : "m" (*(char *)OFFSETOF_CURTHREAD)); > >^~~ > > ./machine/pcpu.h:226:13: note: consider using __builtin_trap() or > > qualifying pointer with 'volatile' > > That's indeed a valid warning from clang, since OFFSETOF_CURTHREAD is > usually zero. It's probably due to recent work on dtrace. I'm not in > the neighborhood of a FreeBSD box right now to verify, but can you > please try to change the cast to "(volatile char *)"? That should fix > the warning. 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. pgp4ORWhhQS5b.pgp Description: PGP signature
Re: Awful FreeBSD 9 block IO performance in KVM
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/runningfreebsdonlinuxkvm > > Slides 13 and 20 are particular eye openers. Does anyone know what is wrong? For those watching at home - this is bad performance _with_ the virtio drivers themselves, not just with SCSI emulation. Slide 17 is very telling - the operation latency is quite high. Richard, are you able to easily test out things on FreeBSD-HEAD guest in a Linux KVM? If so, some of the storage/block/GEOM driver people may be able to step up and start offering some ideas. Thanks, Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: -current build failure
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 environments for the validity of dereferencing a pointer value of 0. Doing so is undefined in all cases and any standards-compliant compiler is quite at liberty to eat your dog in such situations - it is explicitly not guaranteed to read the memory at linear address 0 (this is undefined for at least two reasons that I can think of from the C spec, and probably more). David___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Awful FreeBSD 9 block IO performance in KVM
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: >> >> http://www.slideshare.net/TakeshiHasegawa1/runningfreebsdonlinuxkvm >> >> Slides 13 and 20 are particular eye openers. Does anyone know what is wrong? > > For those watching at home - this is bad performance _with_ the virtio > drivers themselves, not just with SCSI emulation. > > Slide 17 is very telling - the operation latency is quite high. > > Richard, are you able to easily test out things on FreeBSD-HEAD guest > in a Linux KVM? If so, some of the storage/block/GEOM driver people > may be able to step up and start offering some ideas. > > Thanks, > > > > Adrian Dear Adrian, 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. Also, I will try testing raw disk IO for Ivan after I have it setup. Yours truly, Richard Yao signature.asc Description: OpenPGP digital signature
delay for switch of current [was Re: [HEADSUP & CFT] pkg 1.0rc1 and schedule]
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 have time for the project in the beginning of august, and I expect some fixes and reactivity will be needed after the switch of current to pkgng by default, the switch is now schedule to 20th august. regards, Bapt pgp7m0f1W0aI5.pgp Description: PGP signature
Re: Awful FreeBSD 9 block IO performance in KVM
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. > > Also, I will try testing raw disk IO for Ivan after I have it setup. Thanks for setting this up. Setting up an easily reproducible environment is by far the biggest and most helpful step here. Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: -current build failure
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 C spec that I have do not differentiate between > freestanding and hosted environments for the validity of dereferencing > a pointer value of 0. Doing so is undefined in all cases and any > standards-compliant compiler is quite at liberty to eat your dog in > such situations - it is explicitly not guaranteed to read the memory at > linear address 0 (this is undefined for at least two reasons that I can > think of from the C spec, and probably more). Ok, I stand corrected. But the standard does not say what you claim either. It only specifies that NULL pointer is unequal to any pointer to object or function (implicitely saying that you can create a C object or function pointer to which is equal to NULL). So, lets reformulate it other way: freestanding implementation in clang has no use, at least for general purpose kernel. Especially ridiculous is the fact that clang throws it hands for asm inline wanting to get null address, on the machine with linearly addressable memory. pgpu3Ku7pA6i5.pgp Description: PGP signature
Re: MPSAFE VFS -- List of upcoming actions
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 kernel would go to userspace; thinks like >> smbfs, nwfs, ntfs, ext2 o ext4 for example should be in userspace (the >> list is incomplete and I don't really know if all of them are yet >> implemenent in userspace) in my opinion. That would make them easier to >> maintain (changes in the kernel would only affect fuse, once fixed all >> the userspace filesystem would work again). >> >> As a bonus, we would get many working fs based on fuse. In the >> server side gluster is a desirable thing; in the desktop things like >> gvfs (in the linux world gvfs is used not only by gnome but also by kde >> or xfce) or truecrypt > > I'm really concerned also about ntfs and smbfs at the moment. It seems > that there is also a FUSE smbfs port, but I never used it and I'm not > sure about its state at all. >From what I understand, Apple have done a considerable amount of work on the FreeBSD-drived smbfs in the latest versions of OS X, based on the existing smbfs in tree: http://www.opensource.apple.com/source/smb/smb-552.5/ I imagine things like the filesystem locking are probably somewhat different, but in terms of updating smbfs itself to support newer features it may be a good base (licensing permitting). smbfs at the moment lacks in some areas such as DFS support, although I do not know if the OS X version is any different there (given the consumer focus of their OS, probably not). There was also a version spun off by OpenSolaris: http://hub.opensolaris.org/bin/view/Project+smbfs/ which again was based on the FreeBSD + Apple versions. I also have a vested interest in NWFS continuing to work - only from a legacy point of view where we still interoperate with a number of Netware 6 servers through this. While those will likely eventually go away, more than likely before we move to 10.x, if there is anyone capable of working on it we could supply a test environment. Unfortunately the actual locking of the NWFS and NCP modules is outside my sphere of knowledge... -- Antony ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
PCIe hotplug
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 a different slot. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
