On 7/18/2018 2:54 AM, Florian Obser wrote:
> During g2k18 I commited rad(8).
>
> [snip]
I had a chance to do a couple simple tests with rad(8) in my test
environment.
# cat rad.conf
interface em0 {
prefix fdcf:b715:2f4d:100::/64
prefix 2001:DB8:2f4d:100::/64
dns {
--- 63.html Mon Mar 26 12:28:54 2018
+++ 63new.html Mon Mar 26 12:29:38 2018
@@ -320,7 +320,7 @@
Support for dumping USB transfers via
https://man.openbsd.org/bpf.4";>bpf(4)
https://man.openbsd.org/tcpdump.8";>tcpdump(8) can now
-unserstand dumps of USB transfers i
adding and when removing from the ugen list.
Seems to work well, but I don't have a lot of hardware to test it.
What do you think ?
https://github.com/mickaeltorres/openbsd_ugenctl and inlined.
Cheers,
Mike.
kernel patch below:
Index: usb.c
==
On 12/19/2015 7:08 AM, Stefan Sperling wrote:
> On Fri, Dec 18, 2015 at 05:40:39PM -0500, David Hill wrote:
>> With sthen@'s patch I can associate, dhcp, and use net.
>
> Here's an updated iwn diff with a better approach for Stuart's fix.
>
> [snip]
I was able to do some limited testing with th
On 2/15/2015 at 2:51 AM j...@wxcvbn.org wrote:
|Jason McIntyre writes:
|
|> On Fri, Feb 13, 2015 at 09:49:58PM -0600, Adam Thompson wrote:
|>> Fix a minor typo in the ntpctl help output, and same semantic
mistake
|in the
|>> manpage. Currently says (to be pedantic) that '-s' only works
with
|'
On 3/13/2017 7:02 PM, Mark Kettenis wrote:
>> From: "Todd C. Miller"
>> Date: Mon, 13 Mar 2017 16:31:35 -0600
>>
>> How about we just eliminate the "logfile turned over" message
>> entirely? It's kind of bogus for newsyslog to be writing to the
>> log files directly. I don't think that message p
my friend.. long time no talk
prolly because i have not emailed in two years lol
saw this thought you might be interested
www.elitewealthsecret.com
thank me later =)
blessings
Mike
just got back from Hawaii and i Know i KNOw its been a very long time since i
mailed my list ..3 years? well
i just needed to show you this!
do Not Miss OUT!
www.elitewealthsecret.com
blessings,
Mike
i know you will love this =))
www.elitewealthsecret.com
thank me later
blessings,
Mike
Minor typos.
Index: rtadvd.conf.5
===
RCS file: /cvs/src/usr.sbin/rtadvd/rtadvd.conf.5,v
retrieving revision 1.31
diff -u -r1.31 rtadvd.conf.5
--- rtadvd.conf.5 26 Sep 2012 16:19:45 - 1.31
+++ rtadvd.conf.5 29
Is this going to eventually make it in the tree ?
Best regards,
Mike
On 9/7/2012 at 6:35 PM Patrick Wildt wrote:
|I have machines which might not have an internet connection, but still
|need to
|be synchronized,
|even if the time's not correct. What's important is, that every
machine in
|the
|network has the
|same time. Also the ntp server doesn't have a sensor to
On Tue, Jan 05, 2021 at 12:49:29PM -0700, Tracey Emery wrote:
> Hello tech@,
>
> Some of us have been having shutdown issues with our VMs on OpenBSDAms.
> I tracked down the problem to too short of a timeout for the shutdown
> event.
>
> If there are an additional 1 or 2 package daemons running on
try increasing amount of iterations to 1 (or more) for example
and see
if this is a timing issue.
Cheers,
Mike
> Index: xen.c
> ===
> RCS file: /cvs/src/sys/dev/pv/xen.c,v
> retrieving revision 1.97
> diff -u -p -r
On Mon, Feb 15, 2021 at 01:15:33PM +0100, Martin Pieuchot wrote:
> On 15/02/21(Mon) 11:47, Martin Pieuchot wrote:
> > Diff below includes non-functional changes:
> >
> > - Sync comments with NetBSD including locking details.
> > - Remove superfluous parenthesis and spaces.
> > - Add brackets, even
On Sat, Feb 27, 2021 at 09:44:03AM +1000, David Gwynne wrote:
>
>
> > On 27 Feb 2021, at 7:50 am, Klemens Nanni wrote:
> >
> > On Sat, Feb 27, 2021 at 07:30:56AM +1000, David Gwynne wrote:
> >> i think this is enough to let vmd wire guests up to veb interfaces.
> > But please update vm.conf(5) to
On Wed, Mar 10, 2021 at 03:08:21PM +0100, Mischa wrote:
> Hi All,
>
> Currently I am running 6.9-beta on one of my hosts to test veb(4)/vport(4).
>
> root@server14:~ # sysctl kern.version
> kern.version=OpenBSD 6.9-beta (GENERIC.MP) #385: Mon Mar 8 12:57:12 MST 2021
> dera...@amd64.openbsd.org
On Thu, Mar 11, 2021 at 06:11:03PM -0500, Dave Voutila wrote:
> tl;dr: tedu vmboot.{c,h}, ufs.c from vmd(8) to remove broken ability to
> exract and boot a kernel image from a raw or qcow2 disk image
>
> The following diff removes the ability to boot directly from a disk
> image containing a FFS fi
On Wed, Mar 10, 2021 at 08:30:32PM +0100, Mischa wrote:
> On 10 Mar at 18:59, Mike Larkin wrote:
> > On Wed, Mar 10, 2021 at 03:08:21PM +0100, Mischa wrote:
> > > Hi All,
> > >
> > > Currently I am running 6.9-beta on one of my hosts to test
> > &g
On Wed, Mar 17, 2021 at 10:29:32PM +0100, Klemens Nanni wrote:
> On Sun, Mar 14, 2021 at 11:00:22AM -0400, Dave Voutila wrote:
> > Any takers?
> Yes, I plan to commit the updated diff at the end until friday
> unless someone objects.
>
no objection, thanks everyone.
ok mlarkin
> > Here's an upda
On Tue, Mar 23, 2021 at 01:52:20PM +0100, Martin Pieuchot wrote:
> Diff below convert multiple "return(val)" and "return (val)" to
> "return val". I only changed those that help decrease the size
> of the diff with NetBSD or didn't change anything.
>
> ok?
>
I read through these and agree this sh
On Sun, Mar 28, 2021 at 09:28:11AM -0400, Bryan Steele wrote:
> On Sun, Mar 28, 2021 at 08:38:13AM -0400, Dave Voutila wrote:
> > abieber@ found the latest 9front release ends up in a boot loop if
> > hosted on an AMD system. I tracked it down to 9front (oddly) trying to
> > read the PAT msr prior
On Sat, Mar 27, 2021 at 10:15:27AM -0400, Dave Voutila wrote:
>
> Adam Steen writes:
>
> > Hi
> >
> > IA32_EPT_VPID_CAP_XO_TRANSLATIONS is specified incorrectly, see the
> > patch below.
>
> Adam's diff looks correct to me based on reading Intel SDM Vol 3D,
> Appendix A.10 (VPID and EPT Capabilitie
On Fri, Mar 26, 2021 at 07:24:32AM -0400, Dave Voutila wrote:
>
> Theo Buehler writes:
>
> > On Thu, Mar 25, 2021 at 08:07:53PM +0100, Preben Guldberg wrote:
> >> Dave Voutila wrote:
> >> > Preben Guldberg writes:
> >> > > The patch below addresses an off-by-one error reading argv when
> >> > > gen
On Thu, Apr 01, 2021 at 06:43:30PM -0500, Scott Cheloha wrote:
> On Thu, Apr 01, 2021 at 03:41:24PM -0400, Josh Rickmar wrote:
> > On Thu, Apr 01, 2021 at 03:22:00PM -0400, Josh Rickmar wrote:
> > > On Thu, Apr 01, 2021 at 02:15:48PM -0500, Scott Cheloha wrote:
> > > > On Sat, Mar 27, 2021 at 02:20
On Fri, Apr 02, 2021 at 03:24:55AM +0200, Klemens Nanni wrote:
> On Thu, Apr 01, 2021 at 08:34:37PM -0400, Dave Voutila wrote:
> > I've updated the diff using your feedback. See below.
> Thanks, OK kn
>
ok mlarkin@ also
On Sat, Apr 03, 2021 at 10:21:02PM -0500, Scott Cheloha wrote:
> On Fri, Apr 02, 2021 at 10:37:36AM -0700, Mike Larkin wrote:
> > On Thu, Apr 01, 2021 at 06:43:30PM -0500, Scott Cheloha wrote:
> > >
> > > [...]
> > >
> > > Hmmm. Being able to work a
On Mon, Apr 05, 2021 at 07:37:51PM -0500, Scott Cheloha wrote:
> Intel calls it "IA32_TSC_ADJUST". Is "MSR_TSC_ADJUST" fine or should
> it be "MSR_IA32_TSC_ADJUST"?
>
> We have a feature flag for this one already, SEFF0EBX_TSC_ADJUST.
>
> Index: specialreg.h
> =
On Tue, Apr 06, 2021 at 07:47:52PM +0200, Thomas L. wrote:
> Hi,
>
> I'm running OpenBSD 6.8 as hypervisor with multiple OpenBSD VMs.
> Regularly, it happens that all VM are restarted, not at the same time
> but clustered. The indication that this happend is reduced uptime on the
> VMs, some servic
On Fri, Apr 02, 2021 at 07:14:34PM -0400, Dave Voutila wrote:
> If vmctl(8) sends an unpause request for a vm that doesn't exist, vmd(8)
> should be responding with the IMSG_VMDOP_UNPAUSE_VM_RESPONSE imsg_type
> with an ENOENT error code. (Similarly if the request comes from a user
> without permis
On Tue, Apr 06, 2021 at 09:15:10PM +0200, Thomas L. wrote:
> On Tue, 6 Apr 2021 11:11:01 -0700
> Mike Larkin wrote:
> > Anything in the host's dmesg?
>
*host* dmesg. I think you misread what I was after...
> Below is the dmesg and latest syslog from one of the VMs.
>
On Wed, Apr 07, 2021 at 12:22:23AM +0200, Thomas L. wrote:
> On Tue, 6 Apr 2021 14:28:09 -0700
> Mike Larkin wrote:
>
> > On Tue, Apr 06, 2021 at 09:15:10PM +0200, Thomas L. wrote:
> > > On Tue, 6 Apr 2021 11:11:01 -0700
> > > Mike Larkin wrote:
>
On Wed, Apr 07, 2021 at 07:26:41AM -0400, Dave Voutila wrote:
>
> Mike Larkin writes:
>
> > On Wed, Apr 07, 2021 at 12:22:23AM +0200, Thomas L. wrote:
> >> On Tue, 6 Apr 2021 14:28:09 -0700
> >> Mike Larkin wrote:
> >>
> >> > On Tue, Apr 06,
On Wed, Apr 07, 2021 at 09:23:14AM -0400, Dave Voutila wrote:
>
> Dave Voutila writes:
>
> > Mike Larkin writes:
> >
> >> On Wed, Apr 07, 2021 at 12:22:23AM +0200, Thomas L. wrote:
> >>> On Tue, 6 Apr 2021 14:28:09 -0700
> >>> Mike Larkin w
On Wed, Apr 07, 2021 at 07:47:28PM -0400, Dave Voutila wrote:
>
> Thomas L. writes:
>
> >> > Thomas: I looked at your host dmesg and your provided vm.conf. It
> >> > looks like 11 vm's with the default 512M memory and one (minecraft)
> >> > with 8G. Your host seems to have only 16GB of memory, some
On Sat, Jul 23, 2022 at 02:13:27PM -0400, Daniel Dickman wrote:
> The Rise mp6 was a short lived processor that was announced around 20+
> years and didn't make it to market.
>
> I think we can delete the cpu identification for this cpu at this point.
>
> ok?
ok mlarkin
>
> Index: i386/machdep.c
On Fri, Jul 15, 2022 at 12:27:04PM -0400, Dave Voutila wrote:
> The following diff adds in formalization around mmio assists for nested
> page/ept faults on Intel and AMD vmm(4) hosts. It provides what little
> information is available to userland in terms of either the instruction
> bytes (on AMD)
On Wed, Jul 27, 2022 at 10:18:55PM -0400, Daniel Dickman wrote:
> The diff below removes support for 386SX/DX processors. We already claim
> we don't support anything older than a Pentium so there's no point to keep
> this code.
>
> The main code change is in locore0.S and is to stop checking if th
s production
facilities in Hamburg. Regular flights do not use XFW except possibly in the
case of serious emergencies.
Mike
On Sun, Aug 14, 2022 at 11:24:37PM -0500, Scott Cheloha wrote:
> Hi,
>
> In the future when the LAPIC timer is run in oneshot mode there will
> be no lapic_delay().
>
> This is fine if you have a constant TSC, because we have tsc_delay().
>
> This is *very* bad for older amd64 machines, because you
On Wed, Aug 17, 2022 at 03:27:51PM +1000, Jonathan Gray wrote:
> broken after rev 1.652 of machdep.c
>
> cpu0: Intel(R) Pentium(R) M processor 1200MHz ("GenuineIntel" 686-class) 1.20
> GHz, 06-09-05
> cpu0: Intel(R) Pentium(R) M processor 1200MHz ("GenuineIntel" -class) 1.20
> GHz, 06-09-05
>
> C
On Wed, Aug 17, 2022 at 09:00:12PM +1000, Jonathan Gray wrote:
> On Wed, Aug 17, 2022 at 04:53:20PM +1000, Jonathan Gray wrote:
> >
> > It seems to me it would be cleaner if the decision of what to use for
> > delay could be moved into an md file.
> >
> > Or abstract it by having a numeric weight l
On Thu, Aug 18, 2022 at 12:39:58PM +0200, Martin Pieuchot wrote:
> The lock must be grabbed before iterating on the global array, ok?
>
> Index: uvm/uvm_pager.c
> ===
> RCS file: /cvs/src/sys/uvm/uvm_pager.c,v
> retrieving revision 1.8
On Fri, Aug 19, 2022 at 10:31:30PM -0400, Daniel Dickman wrote:
> The below diff removes detection code for the Cyrix 486DLC and Cyrix 6x86
> CPUs from OpenBSD/i386.
>
> The Cyrix 486DLC is a 486-class CPU which we no longer support.
>
> The 6x86, also known as the M1, does not support CPUID by def
On Sat, Aug 20, 2022 at 09:03:59AM +, Klemens Nanni wrote:
> vmd/Makefile filters for amd64 itself but still, no need to enter
> on !amd64.
>
> Index: ../Makefile
> ===
> RCS file: /cvs/src/regress/usr.sbin/Makefile,v
> retrieving
On Mon, Aug 22, 2022 at 12:31:45AM +1000, Jonathan Gray wrote:
> libkern bzero doesn't have the 486 path but is otherwise the same
>
ok mlarkin (but didnt test)
> diff --git sys/arch/i386/i386/locore.s sys/arch/i386/i386/locore.s
> index dba6ce75b81..3055a06812c 100644
> --- sys/arch/i386/i386/lo
On Mon, Aug 29, 2022 at 01:58:38PM +0200, Martin Pieuchot wrote:
> Small refactoring to introduce uvmpd_dropswap(). This will make an
> upcoming rewrite of the pdaemon smaller & easier to review :o)
>
> ok?
>
reads ok to me. ok mlarkin
> Index: uvm/uvm_pdaemon.c
> ===
(see below)
On Mon, Aug 15, 2022 at 03:06:05PM -0400, Dave Voutila wrote:
>
> Mike Larkin writes:
>
> > On Fri, Jul 15, 2022 at 12:27:04PM -0400, Dave Voutila wrote:
> >> The following diff adds in formalization around mmio assists for nested
> >> page/ept fau
On Sun, Aug 28, 2022 at 03:26:49PM -0500, Scott Cheloha wrote:
> As promised off-list: in anticipation of merging the clock interrupt
> code, let's sync up the lapic timer parts of i386/lapic.c with the
> corresponding parts in amd64/lapic.c. They will need identical
> changes to use the new code,
On Fri, Sep 02, 2022 at 11:42:03AM -0500, Scott Cheloha wrote:
> The 8254 data sheet [1] says this about the Read-Back command:
>
> > The read-back command may be used to latch multi-
> > ple counter output latches (OL) by setting the
> > COUNT bit D5 = 0 and selecting the desired coun-
> > ter(s).
On Fri, Sep 02, 2022 at 11:42:03AM -0500, Scott Cheloha wrote:
> The 8254 data sheet [1] says this about the Read-Back command:
>
> > The read-back command may be used to latch multi-
> > ple counter output latches (OL) by setting the
> > COUNT bit D5 = 0 and selecting the desired coun-
> > ter(s).
On Fri, Sep 02, 2022 at 06:00:25PM -0500, Scott Cheloha wrote:
> dv@ suggested coming to the list to request testing for the pvclock(4)
> driver. Attached is a patch that corrects several bugs. Most of
> these changes will only matter in the non-TSC_STABLE case on a
> multiprocessor VM.
>
> Ideal
On Sun, Sep 04, 2022 at 02:50:10PM +1000, Jonathan Gray wrote:
> On Sat, Sep 03, 2022 at 05:33:01PM -0500, Scott Cheloha wrote:
> > On Sat, Sep 03, 2022 at 10:37:31PM +1000, Jonathan Gray wrote:
> > > On Sat, Sep 03, 2022 at 06:52:20AM -0500, Scott Cheloha wrote:
> > > > > On Sep 3, 2022, at 02:22,
On Thu, Sep 08, 2022 at 08:32:27AM -0500, Scott Cheloha wrote:
> On Tue, Sep 06, 2022 at 03:30:44AM -0700, Mike Larkin wrote:
> > On Sun, Sep 04, 2022 at 02:50:10PM +1000, Jonathan Gray wrote:
> > > On Sat, Sep 03, 2022 at 05:33:01PM -0500, Scott Cheloha wrote:
> > > &
On Sun, Sep 11, 2022 at 12:26:31PM +0200, Martin Pieuchot wrote:
> Diff below adds a minimalist set of assertions to ensure proper locks
> are held in uvm_mapanon() and uvm_unmap_remove() which are the guts of
> mmap(2) for anons and munmap(2).
>
> Please test it with WITNESS enabled and report bac
On Wed, Sep 21, 2022 at 08:09:05AM -0400, Christoff Humphries wrote:
> Hello.
>
> I want to help with the virtualization project to get the things that are
> incomplete or missing completed (ie, the "not available at this time" list
> on https://www.openbsd.org/faq/faq16.html).
Great, always nice
On Sat, Sep 24, 2022 at 11:06:24AM +1000, Jonathan Gray wrote:
> On Fri, Sep 23, 2022 at 09:16:25AM -0500, Scott Cheloha wrote:
> > Hi,
> >
> > TL;DR:
> >
> > I want to compute the TSC frequency on AMD CPUs using the methods laid
> > out in the AMD manuals instead of calibrating the TSC by hand.
>
On Wed, Oct 05, 2022 at 05:03:16PM -0400, Dave Voutila wrote:
> Matthew Martin recently presented a patch on tech@ [1] fixing some missed
> scaling from when I converted vmd(8) to use bytes instead of megabytes
> everywhere. I finally found time to wade through the code it touches and
> am proposin
On Fri, Oct 07, 2022 at 11:59:49AM -0700, Bryan Vyhmeister wrote:
> Hey Patrick,
>
> I hope you're doing well. We have not talked in quite a while. I was
> wondering how well the support for the ThinkPad X13s works right now in
> OpenBSD. I did some searching around and couldn't find much other tha
On Sun, Nov 06, 2022 at 11:54:13AM +0100, Martin Pieuchot wrote:
> These 3 syscalls should now be ready to run w/o KERNEL_LOCK(). This
> will reduce contention a lot. I'd be happy to hear from test reports
> on many architectures and possible workloads.
>
> Do not forget to run "make syscalls" be
On Tue, Nov 08, 2022 at 11:59:17AM +, Scott Cheloha wrote:
> On some arm64 machines, the agtimer(4) ticks slowly enough that the
> tc_delta() doesn't overflow across brief suspends. While working on
> arm64 suspend/resume, kettenis@ has been seeing warnings like this
> during resume:
>
> tc_se
On Tue, Nov 08, 2022 at 01:14:02PM +, Martin Pieuchot wrote:
> Now that mmap/munmap/mprotect(2) are no longer creating contention it is
> possible to see that sched_yield(2) is one of the syscalls waiting for
> the KERNEL_LOCK() to be released. However this is no longer necessary.
>
> Traversi
This lock/unlock around an atomic operation was causing delays delivering
interupts into VMs. Pointed out by claudio@ when he ran md5 - in a VM
and it became very sluggish.
Debugging help from dlg and mpi, thanks.
ok?
-ml
Index: arch/amd64/amd64/vmm.c
==
On Tue, Nov 15, 2022 at 02:31:27PM +0100, Martin Pieuchot wrote:
> UVM vnode objects include a reference count to keep track of the number
> of processes that have the corresponding pages mapped in their VM space.
>
> When the last process referencing a given library or executable dies,
> the reape
On Sat, Jul 01, 2023 at 08:35:47PM -0500, Scott Cheloha wrote:
> Every platform made the clockintr switch six months ago or more. The
> __HAVE_CLOCKINTR symbol is now redundant and can be removed.
>
> ok?
>
makes sense if every platform defines it all the time.
> Index: ./ddb/db_command.c
> ==
On Tue, Jul 18, 2023 at 08:21:41AM -0500, Scott Cheloha wrote:
> This patch moves the profil(2)- and GPROF-specific parts of
> statclock() out into into separate clock interrupt routines. The
> profil(2) part moves into profclock() and is enabled/disabled as
> needed during mi_switch(). The GPROF
On Thu, Jul 20, 2023 at 12:58:33PM -0500, joshua stein wrote:
> bmercer@ noticed there was no newline printed after a successful attachment.
> I did some other minor cleanup removing duplicate dv_xname printing during
> attachment and wrapping at 80 chars.
>
> ok?
>
ok mlarkin
>
> Index: sys/dev/
On Thu, Jul 20, 2023 at 01:23:01PM -0500, Scott Cheloha wrote:
> On Wed, Jul 19, 2023 at 05:09:04AM +0000, Mike Larkin wrote:
> > On Tue, Jul 18, 2023 at 08:21:41AM -0500, Scott Cheloha wrote:
> > > This patch moves the profil(2)- and GPROF-specific parts of
> > >
On Fri, Jul 21, 2023 at 05:46:32PM +0200, Jeremie Courreges-Anglas wrote:
> On Thu, Jul 20 2023, Scott Cheloha wrote:
> > On Wed, Jul 19, 2023 at 05:09:04AM +0000, Mike Larkin wrote:
> >> On Tue, Jul 18, 2023 at 08:21:41AM -0500, Scott Cheloha wrote:
> >> > This
On Wed, Jul 26, 2023 at 12:23:58PM -0400, Dave Voutila wrote:
> When adding exec for vm's and fork/exec'd vio{blk,net} devices, the
> current verbosity wasn't being set on the new process. The below change
> keeps it simple, avoiding runtime string manipulation. Also tosses in an
> ifdef around a v
On Sun, Aug 20, 2023 at 10:39:46PM -0500, Scott Cheloha wrote:
> pOn amd64 we lie about the interrupts established during
> i8254_initclocks(). We claim they are MP-safe in order to mollify a
> KASSERT in intr_establish() and continue booting.
>
> See amd64/isa/clock.c:
>279 void
>280 i8
On Sat, Aug 19, 2023 at 01:44:47PM -0500, Scott Cheloha wrote:
> On Sun, Aug 13, 2023 at 01:48:21PM -0500, Scott Cheloha wrote:
> > This is the next patch in the clock interrupt reorganization series.
> >
> > Before we continue breaking up the hardclock(9) we need to detour into
> > the MD code.
>
On Mon, Aug 21, 2023 at 09:26:00PM -0500, Scott Cheloha wrote:
> On Mon, Aug 21, 2023 at 10:10:58PM +0000, Mike Larkin wrote:
> > On Sat, Aug 19, 2023 at 01:44:47PM -0500, Scott Cheloha wrote:
> > > On Sun, Aug 13, 2023 at 01:48:21PM -0500, Scott Cheloha wrote:
> > >
On Mon, Aug 21, 2023 at 10:23:53PM -0500, Scott Cheloha wrote:
> On Tue, Aug 22, 2023 at 02:36:31AM +0000, Mike Larkin wrote:
> > On Mon, Aug 21, 2023 at 09:26:00PM -0500, Scott Cheloha wrote:
> > > On Mon, Aug 21, 2023 at 10:10:58PM +, Mike Larkin wrote:
> > > >
On Fri, Sep 01, 2023 at 03:50:31PM -0400, Dave Voutila wrote:
> Now that my i8259 fix is in, it's safe to expand the testing pool for
> this diff. (Without that fix, users would definitely hit the hung block
> device issue testing this one.) Hoping that folks that run non-OpenBSD
> guests or strang
On Mon, Sep 04, 2023 at 02:30:23PM +0200, Mischa wrote:
> On 2023-09-03 21:18, Dave Voutila wrote:
> > Mischa writes:
> >
> > > Nice!! Thanx Dave!
> > >
> > > Running go brrr as we speak.
> > > Testing with someone who is running Debian.
> >
> > Great. I'll plan on committing this tomorrow afterno
On Mon, Sep 04, 2023 at 07:57:18PM +0200, Mischa wrote:
> On 2023-09-04 18:58, Mischa wrote:
> > On 2023-09-04 18:55, Mischa wrote:
> > > On 2023-09-04 17:57, Dave Voutila wrote:
> > > > Mischa writes:
> > > > > On 2023-09-04 16:23, Mike Larkin wro
On Tue, Sep 05, 2023 at 09:17:27AM -0500, Scott Cheloha wrote:
> mpi@ suggests folding the pseudorandom advance code from
> clockintr_statclock() into the clockintr API itself. This replaces
> three API calls -- clockintr_expiration(), clockintr_nsecuptime(), and
> clockintr_schedule() -- we just
On Sun, Sep 10, 2023 at 01:36:33AM +0200, Hrvoje Popovski wrote:
> Hi all,
>
> I've installed latest snapshot with uefi on Dell R7615 with AMD EPYC
> 9554P, with some NVMe disks on BOSS-N1 adapter and with Samsung NVMe
> disks directly connected to backplane and installation was fast and
> without
On Mon, Sep 11, 2023 at 03:23:28PM +0200, Hrvoje Popovski wrote:
> On 11.9.2023. 6:27, Hrvoje Popovski wrote:
> > On 11.9.2023. 2:48, Mike Larkin wrote:
> >> On Sun, Sep 10, 2023 at 01:36:33AM +0200, Hrvoje Popovski wrote:
> >>> Hi all,
> >>>
> >>
On Sun, Sep 24, 2023 at 01:07:43AM -0400, Dave Voutila wrote:
> vmd has a sneaky little deadlock hidden in the pause logic related to
> the use of mutexes and condition variables.
>
> When pausing, the vcpu is holding the "run" mutex. It then sleeps
> waiting for the unpause condition. If the event
On Sun, Oct 08, 2023 at 07:42:54PM +0200, Mark Kettenis wrote:
> Hector Martin has added support for the BCM4388 that is found on the
> last generation of Apple Macs. Based on his commits I've managed to
> get it working on my M2 Pro mini. I still have to clean up some of
> that stuff, but here i
On Thu, Mar 12, 2020 at 10:31:13PM +0100, Tobias Heider wrote:
> vmm uses 'strncpy(vm->vm_name, vcp->vcp_name, VMM_MAX_NAME_LEN)' to copy
> to buffers of size VMM_MAX_NAME_LEN, which can leave the resulting string
> unterminated.
> From strncpy(3):
> strncpy() only NUL terminates the destination
On Fri, Jun 26, 2020 at 02:45:53PM +0200, Stefan Sperling wrote:
> This patch adds support for 11n Tx aggregation to iwm(4).
>
> Please help with testing if you can by running the patch and using wifi
> as usual. Nothing should change, except that Tx speed may potentially
> improve. If you have tim
On Fri, Jun 26, 2020 at 09:01:03PM -0700, Mike Larkin wrote:
> On Fri, Jun 26, 2020 at 02:45:53PM +0200, Stefan Sperling wrote:
> > This patch adds support for 11n Tx aggregation to iwm(4).
> >
> > Please help with testing if you can by running the patch and using wifi
> &g
On Fri, Apr 23, 2021 at 01:55:14PM +0200, Alessandro Pistocchi wrote:
> Hi all,
>
> I am fairly new to openbsd so if this is something obvious that I missed
> please be understanding.
>
> I am adding a syscall to openbsd 6.8. I am working on a raspberry pi.
>
> During the syscall I allocate some me
On Fri, Apr 23, 2021 at 08:07:43PM +0200, Martin Pieuchot wrote:
> Diff below convert the last uses of uvm_km_alloc(9) and uvm_km_zalloc(9)
> to km_alloc(9).
>
> One of the allocations below uses `kp_pageable' instead of `kp_zero'
> because the mapping for `pm_pdir_intel' is lost when PAE is enable
On Thu, Apr 29, 2021 at 03:24:42PM -0400, Dave Voutila wrote:
> Found this while running ctags(1)... vioqcow2.c has struct qcheader
> already defined at L53 (which stylistically is where it should be).
>
> This diff just removes the duplicate definition inside
> virtio_qcow2_create().
>
> OK?
>
>
>
On Sat, May 01, 2021 at 09:26:39PM +, alloca wrote:
> This patch adds a serve_gzip option. When enabled, If the client requests
> path, then serve path.gz if it exists and the client accepts
> Content-Encoding: gzip.
>
>
man style
> diff -up httpd.orig/config.c httpd/config.c
> --- httpd.
On Mon, May 03, 2021 at 08:50:36PM -0400, Dave Voutila wrote:
> If debug state in the logging routines isn't set, messages from
> fatal{,x} and warn{,x} don't get flushed to stderr, so running vmd
> un-daemonized can result in the process exiting at startup with no
> discernable message reason othe
On Mon, Mar 15, 2021 at 09:29:29AM +, James Cook wrote:
> > The array "base" which is passed to log_warnx might be uninitialized:
> > virtio_get_base doesn't necessarily touch it if it returns -1. Maybe it
> > would be better just omit base from the output, e.g.
> >
> > log_warnx("vm \"%s\"
On Mon, Mar 15, 2021 at 08:21:56AM +, James Cook wrote:
> Hi tech@,
>
> The below patch removes calls to realpath(3) when looking up a qcow2
> base image. Previous thread:
> https://marc.info/?t=16156249642&r=1&w=2
>
> In short, the calls were failing inside vmctl, because of unveil. The
>
On Thu, May 20, 2021 at 07:36:23AM -0400, Dave Voutila wrote:
> We don't currently emulate all TSC related features yet. While hacking
> on other issues, I've found some more obnoxious guests (*cough* debian
> *cough*) constantly try to read the IA32_TSC_ADJUST msr every second,
> not getting the h
On Sat, May 22, 2021 at 10:20:37AM -0400, Dave Voutila wrote:
> tech@ & krw (since your code in question was imported to vmd),
>
> I found strange behavior running tcpbench(1) to measure the connection
> between a vmd guest and my host, as well as guest-to-guest. In short,
> it's some bogus logic i
On Mon, May 24, 2021 at 08:25:04AM +0200, Claudio Jeker wrote:
> On Sun, May 23, 2021 at 10:25:38PM -0400, Dave Voutila wrote:
> > The following diff adds in virtio 1.1's VIRTIO_NET_F_MTU feature support
> > to vmd(8)'s virtio networking device. This allows for communicating an MTU
> > to the guest
On Sun, May 23, 2021 at 09:50:46PM -0400, Dave Voutila wrote:
> Seems only right that vio.4 mention it's the driver used for the virtio
> networking device provided by vmd(8).
>
> OK?
>
ok mlarkin
>
> Index: vio.4
> ===
> RCS file: /
On Tue, Jun 01, 2021 at 08:03:43PM -0500, Scott Cheloha wrote:
> The documentation for the Linux pvclock is pretty sparse but I am
> pretty sure we want to use a monotonic base for ti_system_time. We
> also have a function for converting a timespec into a 64-bit count of
> nanoseconds we can use.
On Thu, Jun 10, 2021 at 03:19:43PM +1000, Jonathan Gray wrote:
> Ilya Voronin sent a diff to misc to limit MSR_INT_PEN_MSG use to
> < AMD family 17h prompted by a problem with an AWS t3a instance.
>
> https://marc.info/?l=openbsd-misc&m=162120066715633&w=2
>
> Digging some more the 16h bkdgs have i
On Wed, Jun 09, 2021 at 10:35:48PM -0700, Mike Larkin wrote:
> On Thu, Jun 10, 2021 at 03:19:43PM +1000, Jonathan Gray wrote:
> > Ilya Voronin sent a diff to misc to limit MSR_INT_PEN_MSG use to
> > < AMD family 17h prompted by a problem with an AWS t3a instance.
> >
On Thu, Jun 10, 2021 at 09:19:45AM -0400, Dave Voutila wrote:
>
> Still looking for an OK or feedback on the below. This is finishing work
> to fixes made previously to vmd(8)/vmctl(8) regarding vm
> stopping/running state corruption when using vmctl(8) to wait for a vm
> to stop.
>
Sorry for the
1 - 100 of 1782 matches
Mail list logo
