RE: vboxguest on 9.0-BETA
Hi! I tried running Virtualbox Guest Addition with NetBSD-9.99.56/amd64. The host is Windows 10, Virtualbox-6.1.6. I appreciate the efforts of those involved. Because the version of xorg-server attached to NetBSD is 1.20.6, a patch like the link below was needed to make GuestAdditions of Virtualbox work. This is the difference against svn revision 83708. https://www.dropbox.com/s/hthsagl61oqhqhu/vbox-r83708-diff.txt.xz?dl=0 * The mouse driver of Xorg.conf uses "ws". * The clipboard sharing is bidirectional. * The loadable kernel module is automatically loaded when the VBoxService is started. With the above settings, things are working for the most part, but there is a small problem. I can select the screen resolution at Display->Virtual Screen 1 in the virtual machine, but it doesn't change. I can still change the screen size with xrandr though. Phenomenon in the graphics controller VMSVGA * When vboxvideo is selected in the Driver of Xorg.conf, it does not start with an error. * Virtual machine resets when running X with 256MB of video memory, OK for 128MB Phenomenon with graphics controller VBoxVGA/VBoxSVGA X server does not start when I select vmware in the Driver of Xorg.conf Do you have any thoughts or comments? -- SUNAGAWA Keiki -Original Message- From: current-users-ow...@netbsd.org On Behalf Of Chavdar Ivanov Sent: Thursday, August 1, 2019 10:10 PM To: NetBSD current-users Subject: vboxguest on 9.0-BETA Hi, FYI VirtualBox guest cleanly compiles and apparently works under 9.0-BETA; in this case I used fresh svn update: ... Starting local daemons:12:58:44.643043 main VBoxService 6.0.97 r80012 (verbosity: 0) netbsd.amd64 (Aug 1 2019 13:54:41) release log 12:58:44.643086 main Log opened 2019-08-01T12:58:44.643017000Z 12:58:44.643227 main OS Product: NetBSD 12:58:44.643239 main OS Release: 9.0_BETA 12:58:44.643266 main OS Version: NetBSD 9.0_BETA (GENERIC) #0: Tue Jul 30 16:52:10 UTC 2019 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC 12:58:44.643288 main Executable: /usr/local/bin/additions/VBoxService 12:58:44.643294 main Process ID: 25832 12:58:44.643299 main Package type: BSD_64BITS_GENERIC 12:58:44.646075 main 6.0.97 r80012 started. Verbose level = 0 . LocalConfig.kmk: ... VBOX_WITHOUT_HARDENING := 1 VBOX_ONLY_ADDITIONS := 1 VBOX_WITH_ADDITION_DRIVERS := 1 VBOX_WITH_X11_ADDITIONS := 1 VBOX_ONLY_ADDITIONS_WITHOUT_RTISOMAKER := 1 ifeq ($(KBUILD_TARGET), netbsd) TEMPLATE_VBOXGUESTR3EXE_LIBS = $(TEMPLATE_VBOXR3EXE_LIBS) crypt endif .. 9.0BETA# /usr/local/bin/additions/VBoxControl version Oracle VM VirtualBox Guest Additions Command Line Management Interface Version 6.0.97 (C) 2008-2019 Oracle Corporation All rights reserved. 6.0.97r80012 9.0BETA# ps ax | grep VBox 190 ? Is 0:00.00 /usr/local/bin/additions/VBoxClient --clipboard 7090 ? Isl 0:00.16 /usr/local/bin/additions/VBoxService --pidfile /var/run/VBoxService.pid 24395 ? Is 0:00.00 /usr/local/bin/additions/VBoxClient --display 25517 ? Il 0:00.01 /usr/local/bin/additions/VBoxClient --clipboard 26513 ? I0:00.01 /usr/local/bin/additions/VBoxClient --display 1023 pts/3 O+ 0:00.00 grep --color=auto --exclude=.bzr --exclude=CVS --exclude=.git --exclude=.hg --exclude=.svn VBox --
daily CVS update output
Updating src tree: P src/bin/csh/extern.h P src/bin/csh/time.c P src/bin/sh/eval.c P src/distrib/sets/lists/modules/mi P src/doc/CHANGES P src/external/bsd/atf/dist/tools/env.cpp P src/sbin/umount/Makefile P src/sbin/umount/umount.c P src/share/man/man4/sk.4 P src/share/mk/bsd.own.mk P src/sys/arch/aarch64/aarch64/netbsd32_machdep.c P src/sys/arch/aarch64/aarch64/sig_machdep.c P src/sys/arch/aarch64/include/profile.h P src/sys/arch/amd64/amd64/netbsd32_machdep.c P src/sys/arch/arm/include/asm.h P src/sys/arch/macppc/dev/lmu.c P src/sys/arch/x86/pci/amdsmn.c P src/sys/arch/x86/x86/cpu.c P src/sys/arch/x86/x86/procfs_machdep.c P src/sys/arch/x86/x86/tsc.c P src/sys/arch/xen/xen/if_xennet_xenbus.c P src/sys/arch/xen/xen/xbdback_xenbus.c P src/sys/dev/vnd.c P src/sys/dev/ic/hpet.c P src/sys/dev/ic/hpetvar.h P src/sys/dev/pci/if_aq.c P src/sys/dev/pci/pcidevs P src/sys/dev/pci/pcidevs.h P src/sys/dev/pci/pcidevs_data.h P src/sys/fs/adosfs/advnops.c P src/sys/fs/cd9660/cd9660_vnops.c P src/sys/fs/efs/efs_vnops.c P src/sys/fs/filecorefs/filecore_vnops.c P src/sys/fs/hfs/hfs_vnops.c P src/sys/fs/msdosfs/msdosfs_denode.c P src/sys/fs/msdosfs/msdosfs_vnops.c P src/sys/fs/nilfs/nilfs_vnops.c P src/sys/fs/puffs/puffs_vnops.c P src/sys/fs/sysvbfs/sysvbfs_vnops.c P src/sys/fs/tmpfs/tmpfs_subr.c P src/sys/fs/tmpfs/tmpfs_vnops.c P src/sys/fs/udf/udf_allocation.c P src/sys/fs/udf/udf_vnops.c P src/sys/fs/v7fs/v7fs_vnops.c P src/sys/kern/kern_crashme.c P src/sys/kern/vfs_cache.c P src/sys/lib/libkern/Makefile.compiler-rt P src/sys/lib/libkern/arch/m68k/divsi3.S P src/sys/lib/libkern/arch/m68k/modsi3.S P src/sys/lib/libkern/arch/m68k/udivsi3.S P src/sys/lib/libkern/arch/m68k/umodsi3.S P src/sys/nfs/nfs_bio.c P src/sys/rump/librump/rumpvfs/rumpfs.c P src/sys/sys/param.h P src/sys/ufs/chfs/chfs_subr.c P src/sys/ufs/chfs/chfs_vnops.c P src/sys/ufs/ext2fs/ext2fs_inode.c P src/sys/ufs/ext2fs/ext2fs_readwrite.c P src/sys/ufs/ffs/ffs_inode.c P src/sys/ufs/lfs/lfs_inode.c P src/sys/ufs/lfs/ulfs_readwrite.c P src/sys/ufs/ufs/ufs_readwrite.c P src/sys/uvm/uvm_bio.c P src/sys/uvm/uvm_extern.h P src/sys/uvm/uvm_glue.c P src/usr.bin/time/ext.h P src/usr.bin/time/time.1 P src/usr.bin/time/time.c P src/usr.bin/units/units.lib Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 37286291 Apr 24 03:08 ls-lRA.gz
Re: Aquantia AQC100 issues
Thank you for the help and updated code. Retested on current branch, works as expected. Possibly worth to mention AQC100 in aq.4 as well? On Thu, Apr 23, 2020 at 8:33 AM Ryo Shimizu wrote: > > > >Yes, the patch solves the problem. Linked is up immediately after the boot. > > I'm relieved. In the interim, I'll commit a fix that always polling linkstat > when FIBRE. > > thanks, > -- > ryo shimizu
Heads up: ubc_direct enabled by default
Hi, This affects amd64, alpha and aarch64, but only 1 and 2 CPU systems so far. Any more and it's still off by default. Only the default has changed so the sysctl (vm.ubc_direct) still works for turning it on and off manually. This works great for me on amd64 but needs some tweaks to handle many CPUs. I have some ideas on that one and hopefully will have something to try soon. Cheers, Andrew
heads up: /bin/sh -e no longer disabled in command substitutions
If we run the following command
$SHELL -ce 'printf %s\\n "${SHELL##*/}: $- ($-) \$($(printf %s $-))"'
with SHELL set to invoke a bunch of different shells, we can see the
settings of the options - and particularly the 'e' option in three
contexts - as it is in the top level shell, in a subshell, and in
a command substitution.
Here are some results:
fbsh: e (e) $(e)
dash: e (e) $(e)
bosh: es (es) $(es)
pbosh: es (es) $(es)
zsh: 569Xe (569Xe) $(569Xe)
yash: ce (ce) $(ce)
ksh: ceh (ceh) $(ceh)
mksh: ehc (ehc) $(ehc)
oksh: ceh (ceh) $(ceh)
pdksh: ceh (ceh) $(ceh)
ksh93: cehsB (cehsB) $(cehsB)
What other options are set by default isn't what's important here,
what is, is that the same set of options appears in all three
contexts - which is as it should be, nothing changed them.
When I test our sh:
sh: eL (eL) $(L)
Note that the 'e' option has mysteriously turned off in the
command substitution. (For those who have an interest, the 'L'
option relates to how $LINENO works in functions.)
That happens explicitly in our sh - whenever a command substitution
is started, the 'e' option is disabled. The code for that was included
in a patch set (taken from what is now dash - though I believe it had
not yet acquired that name) back in early 2000 - these were the patches
that fixed a number of "sh -e" PRs, that made sh -e mostly correct in
the NetBSD sh (there have been later changes that made it even better).
I have just removed (from /bin/sh in HEAD) the one line of code that
turns off the 'e' flag in a command substitution (in the command
substitution subshell).
Note: there are no changes here to the way -e works when enabled - only
to whether it is turned on or not in that one case.
Watch for any odd behaviour from scripts or makefiles - there really
should be none. Let me know if something breaks which might be
related.
kre
ps: you may have noticed that I omitted bash from the tests above.
That's because it has a foot in each camp, in default mode it acts
as our shell did:
bash: ehBc (ehBc) $(hBc)
but not when in posix mode (bash -o posix):
bash: ehBc (ehBc) $(ehBc)
It seems that sometime, long ago (last century/millennium) there was a
belief somewhere, that -e should be turned off in command substitutions.
The (not yet called) dash of the time evidently did that, which is from
where we got that. bash apparently did it as well. Perhaps some other
shells. Everyone else (if they ever did this) stopped it long ago.
bash is, however, big on backwards compat (as are we in general) and
changes to ancient code don't get made to the default mode if there's
any possibility someone might be relying upon it.
