Re: vmd: VMs are stopping with: vcpu 0 run ioctl failed: Invalid argument

[Carlos Cardenas]

On Tue, Jan 16, 2018 at 06:24:18PM +, Olivier Cherrier wrote:
> On Tue, Jan 16, 2018 at 06:56:04AM -0800, cardena...@gmail.com wrote:
> > > Here is what I typically get :
> > >
> > > ...
> > > vionet queue notify - no space, dropping packet
> > > vionet queue notify - no space, dropping packet
> > > vionet queue notify - no space, dropping packet
> > > vionet queue notify - no space, dropping packet
> > > vionet queue notify - no space, dropping packet
> > > vionet queue notify - no space, dropping packet
> > > vionet queue notify - no space, dropping packet
> > > vcpu_run_loop: vm 23 / vcpu 0 run ioctl failed: Invalid argument
> > > vmm_sighdlr: handling signal 20
> > > vmm_sighdlr: attempting to terminate vm 4
> > > terminate_vm: terminating vmid 23
> > > vmm_sighdlr: calling vm_remove
> > > vm_remove: removing vm id 4 from running config
> > > vm_remove: calling vm_stop
> > > vm_stop: stopping vm 4
> > > vmd_dispatch_vmm: handling TERMINATE_EVENT for vm id 4 ret 22
> > > vmd_dispatch_vmm: about to stop vm id 4
> > > vm_stop: stopping vm 4
> > >
> > > > to enable VMM_DEBUG in sys/arch/amd64/amd64/vmm.c and rebuild the 
> > > > kernel.
> > >
> > > Will try that.
> > >
> > > Thank you!
> > > Best
> > > Olivier
> > >
> > 
> > Thanks for reporting the symptoms Olivier.
> > 
> > In order for us to reproduce this and find the root cause, we're going
> > to need the info that Mike was asking:
> > * What guest VM are you running here?
> > * How much memory are you assigning?
>  
>   Hi Carlos,
> 
> Only OpenBSD involved here. The physical machine's dmesg is attached.
> My /etc/vm.conf configuration file is also attached.
> 
> I don't think it is related to memory exhaustion since it sometimes
> happens when the machine is not loaded (cpu and memory).
> 
> > I would add:
> > * What was your "vmctl start ..." command?
>  
> Here, I did use : vmd -d
> 
> Will try by recompiling with VMM_DEBUG.
> 
> Thanks a lot,
> Best
> Olivier

Ok...see comments inline

> OpenBSD 6.2-current (GENERIC.MP) #2: Thu Dec  7 10:13:35 CET 2017
> o...@stanislas.symacx.com:/sys/arch/amd64/compile/GENERIC.MP
This looks like a custom kernel, can you run the latest snapshot, as-is?

> real mem = 4188946432 (3994MB)
> avail mem = 4054945792 (3867MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x87ee6000 (43 entries)
> bios0: vendor American Megatrends Inc. version "5.11" date 06/03/2016
> bios0: Notebook N24_25JU
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT SSDT DBGP DBG2 SSDT 
> UEFI SSDT DMAR ASF!
> acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) 
> PXSX(S4) RP17(S4) PXSX(S4) RP18(S4) PXSX(S4) RP19(S4) PXSX(S4) RP20(S4) 
> PXSX(S4) RP01(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Pentium(R) CPU 4405U @ 2.10GHz, 2095.80 MHz
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,ERMS,INVPCID,RDSEED,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 24MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Pentium(R) CPU 4405U @ 2.10GHz, 2095.14 MHz
> cpu1: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,ERMS,INVPCID,RDSEED,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 1 (application processor)
> cpu2: Intel(R) Pentium(R) CPU 4405U @ 2.10GHz, 2095.14 MHz
> cpu2: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,ERMS,INVPCID,RDSEED,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 1, core 0, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Pentium(R) CPU 4405U @ 2.10GHz, 2095.14 MHz
> cpu3: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,S

Help moving OpenBSD installation to new machine

[Randall Gellens]

I have a pretty old OpenBSD that's been running on a Soekris Net5501, 
an AMD Geode LX single chip processor with CS5536 companion chip, 
classified as a "586 class processor".


I have a new box, a Protectli with a dual core Intel Celeron 3865U.

I want to first move the existing OpenBSD system to the new box, then 
after that's working, I can step through the upgrades to get current.


I naively thought I could move my OpenBSD from the old box to the new 
by cloning the old disc (a camera flash card) onto the new disc (a 
modern SSD).  I cloned the discs and installed the new disc in the 
new box.  When I boot the new box, OpenBSD kernel panics, probably 
because I switched it from a single-core AMD Geode to a dual-core 
Intel Celeron.


Is there an easy way to fix this?  I tried halting from the kernel 
panic debugger and booting /bsd.rd and doing an 'upgrade' (thinking I 
could 'upgrade' to the same version currently installed), but it says 
there are no disks.  I tried going into the /bsd.rd shell and 
entering 'mount /dev/sd0a /mnt' but it says "Device not configured." 
An 'ls /dev/sd*' shows the various partitions of /dev/sd0.


--
Randall Gellens
-- Randomly-selected tag: ---
My friends, no matter how rough the road may be, we can and we will,
never, never surrender to what is right.
 --U.S. Vice President Dan Quayle, in a
   speech to the Christian Coalition

Re: Re-compute bsd checksum

[Stuart Henderson]

> On 1/16/18 1:08 PM, Thuban wrote:
>> I disabled `ulpt` in the kernel using `config` to use an USB-printer.
>>
>> Now, at reboot, I see "kernel relinking failed" message.
>> How to recreate the new checksum? I can't igure out where to find this
>> information.
>>
>> Any advice?

On 2018-01-16, Base Pr1me  wrote:
> Don't think you can use config to disable ulpt and KARL. Someone will correct 
> me 
> if I'm wrong.

That's correct. And by implication, you can't use config to disable ulpt
and use syspatch for kernel patches (because they now rely on KARL relinking).

I think the least worst option in this case is probably to build a kernel
from source (using a -stable checkout if you're starting from a release).
As well as installing the kernel, the "make install" stage will install
the link-kit used for KARL, and update kernel.SHA256, in one go.

Re: Re-compute bsd checksum

[Alexander Hall]

On January 16, 2018 9:35:56 PM GMT+01:00, Sterling Archer  
wrote:
>On Tue, Jan 16, 2018 at 9:08 PM, Thuban  wrote:
>> I disabled `ulpt` in the kernel using `config` to use an USB-printer.
>>
>> Now, at reboot, I see "kernel relinking failed" message.
>> How to recreate the new checksum? I can't igure out where to find
>this
>> information.
>>
>> Any advice?
>>
>> Regards.
>>
>> --
>> thuban
>
>sha256 /bsd > /var/db/kernel.SHA256

While that might be a technically correct answer, I don't think the 
consequences are being considered. Think about why the situation occurs in the 
first place.

Re: Re-compute bsd checksum

[Thuban]

* Sterling Archer  le [16-01-2018 21:35:56 +0100]:
> On Tue, Jan 16, 2018 at 9:08 PM, Thuban  wrote:
> > I disabled `ulpt` in the kernel using `config` to use an USB-printer.
> >
> > Now, at reboot, I see "kernel relinking failed" message.
> > How to recreate the new checksum? I can't igure out where to find this
> > information.
> >
> > Any advice?
> >
> > Regards.
> >
> > --
> > thuban
> 
> sha256 /bsd > /var/db/kernel.SHA256
> 

thanks!


signature.asc
Description: PGP signature

Re: Re-compute bsd checksum

[Sterling Archer]

On Tue, Jan 16, 2018 at 9:08 PM, Thuban  wrote:
> I disabled `ulpt` in the kernel using `config` to use an USB-printer.
>
> Now, at reboot, I see "kernel relinking failed" message.
> How to recreate the new checksum? I can't igure out where to find this
> information.
>
> Any advice?
>
> Regards.
>
> --
> thuban

sha256 /bsd > /var/db/kernel.SHA256

-- 
:wq!

Re: bsd.mp not installed on EdgeRouter Lite

[Scott Bennett]

On 1/15/2018 5:30 PM, jungle Boogie wrote:
> On 12 January 2018 at 08:24, Scott Bennett  wrote:
>> After reading INSTALL.octeon, I was able to write miniroot62.fs to a usb,
>> plug that into the ERL, and perform a normal installation. The problem is
>> that the installer was not able to detect both cores, so it only installed
>> bsd.sp (bsd.mp was not an option in the set selection).
> 
> See this post:
> https://an.undulating.space/post/171020-erl-openbsd-smp/
> 
> See this reddit thread:
> https://www.reddit.com/r/openbsd/comments/7agdgh/openbsd_62_on_edgerouter_lite_with_bsdmp/
> 
> Hope that helps

Much appreciated! The reddit thread may just work.

Re: bsd.mp not installed on EdgeRouter Lite

[Scott Bennett]

On 1/13/2018 5:01 AM, Stefan Sperling wrote:
> On Fri, Jan 12, 2018 at 11:24:59AM -0500, Scott Bennett wrote:
>> After reading INSTALL.octeon, I was able to write miniroot62.fs to a usb,
>> plug that into the ERL, and perform a normal installation. The problem is
>> that the installer was not able to detect both cores, so it only installed
>> bsd.sp (bsd.mp was not an option in the set selection).
>>
>> Running 6.2-release.
>>
>> I did follow the instructions for setting the coremask=0x3 when booting the
>> installer, and setting the coremask=0x3 in the bootcmd. It seems that the
>> installer just wasn't able to recognize that it's a dual core system.
> 
> I've seen this, too. For some reason bsd.rd doesn't count CPUs correctly
> even with coremask=0x3.
> 
>> To workaround this problem, I downloaded bsd.mp after installation and copied
>> that to the FAT partition. My ERL can now run SMP, but as you probably
>> guessed this does break KARL.
> 
> That's what I did, too.
> 
>> Has anyone been able to install bsd.mp on the ERL and not break KARL?
> 
> Not me.
> 
> Looking into this is somewhere at the far end of my todo list.
> Not sure I'll ever get to it.

Thanks for the reply, Stefan! At least it's a known issue. I will
watch the tree for any updates in this area.

Re: Re-compute bsd checksum

[Base Pr1me]

Don't think you can use config to disable ulpt and KARL. Someone will correct me 
if I'm wrong.


On 1/16/18 1:08 PM, Thuban wrote:

I disabled `ulpt` in the kernel using `config` to use an USB-printer.

Now, at reboot, I see "kernel relinking failed" message.
How to recreate the new checksum? I can't igure out where to find this
information.

Any advice?

Regards.

Re-compute bsd checksum

[Thuban]

I disabled `ulpt` in the kernel using `config` to use an USB-printer.

Now, at reboot, I see "kernel relinking failed" message.
How to recreate the new checksum? I can't igure out where to find this
information.

Any advice?

Regards.

-- 
thuban


signature.asc
Description: PGP signature

Re: Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

[Reshey]

I am writing this from OpenBSD 6.2 apollo Lake, J4205 cpu. Intel drm works.
But crash if I exit x, and then run startx again.

penBSD 6.2 (GENERIC.MP) #2: Sun Dec 10 21:14:42 CET 2017
r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
GENERIC.MP
real mem = 8209797120 (7829MB)
avail mem = 7953960960 (7585MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xed450 (18 entries)
bios0: vendor American Megatrends Inc. version "P1.40" date 07/14/2017
bios0: ASRock J3455-ITX
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM
WSMT SSDT SSDT AAFT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 BERT WDAT NHLT
acpi0: wakeup devices SIO1(S3) UAR1(S4) HDAS(S3) XHC_(S4) XDCI(S4) BRCM(S0)
PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4)
PXSX(S4) RP05(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 1920 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1497.60 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: TSC frequency 149760 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 19MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1497.60 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1497.60 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1497.60 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP03)
acpiprt2 at acpi0: bus 2 (RP04)
acpiprt3 at acpi0: bus 3 (RP05)
acpiprt4 at acpi0: bus 4 (RP06)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C3(10@150 mwait.1@0x60), C2(10@50 mwait.1@0x21),
C1(1000@1 mwait.1@0x1), PSS
acpicpu1 at acpi0: C3(10@150 mwait.1@0x60), C2(10@50 mwait.1@0x21),
C1(1000@1 mwait.1@0x1), PSS
acpicpu2 at acpi0: C3(10@150 mwait.1@0x60), C2(10@50 mwait.1@0x21),
C1(1000@1 mwait.1@0x1), PSS
acpicpu3 at acpi0: C3(10@150 mwait.1@0x60), C2(10@50 mwait.1@0x21),
C1(1000@1 mwait.1@0x1), PSS
acpipwrres0 at acpi0: FN00, resource for FAN0
acpitz0 at acpi0: critical temperature is 100 degC
acpibtn0 at acpi0: PWRB
"INT3452" at acpi0 not configured
"INT3452" at acpi0 not configured
"INT3452" at acpi0 not configured
"INT3452" at acpi0 not configured
"INT33A1" at acpi0 not configured
"MSFT0101" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 1497 MHz: speeds: 1501, 1500, 1400, 1300, 1200,
1100, 1000, 900, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x5af0 rev
0x0b
inteldrm0 at pci0 dev 2 function 0 vendor "Intel", unknown product 0x5a85
rev 0x0b
drm0 at inteldrm0
inteldrm0: msi
error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to load
firmware i915/bxt_dmc_ver1.bin (-22)
error: [drm:pid0:i915_gem_init_hw] *ERROR* Failed to initialize GuC, error
-8 (ignored)
in

Re: vmd: VMs are stopping with: vcpu 0 run ioctl failed: Invalid argument

[Olivier Cherrier]

On Tue, Jan 16, 2018 at 06:56:04AM -0800, cardena...@gmail.com wrote:
> > Here is what I typically get :
> >
> > ...
> > vionet queue notify - no space, dropping packet
> > vionet queue notify - no space, dropping packet
> > vionet queue notify - no space, dropping packet
> > vionet queue notify - no space, dropping packet
> > vionet queue notify - no space, dropping packet
> > vionet queue notify - no space, dropping packet
> > vionet queue notify - no space, dropping packet
> > vcpu_run_loop: vm 23 / vcpu 0 run ioctl failed: Invalid argument
> > vmm_sighdlr: handling signal 20
> > vmm_sighdlr: attempting to terminate vm 4
> > terminate_vm: terminating vmid 23
> > vmm_sighdlr: calling vm_remove
> > vm_remove: removing vm id 4 from running config
> > vm_remove: calling vm_stop
> > vm_stop: stopping vm 4
> > vmd_dispatch_vmm: handling TERMINATE_EVENT for vm id 4 ret 22
> > vmd_dispatch_vmm: about to stop vm id 4
> > vm_stop: stopping vm 4
> >
> > > to enable VMM_DEBUG in sys/arch/amd64/amd64/vmm.c and rebuild the kernel.
> >
> > Will try that.
> >
> > Thank you!
> > Best
> > Olivier
> >
> 
> Thanks for reporting the symptoms Olivier.
> 
> In order for us to reproduce this and find the root cause, we're going
> to need the info that Mike was asking:
> * What guest VM are you running here?
> * How much memory are you assigning?
 
Hi Carlos,

Only OpenBSD involved here. The physical machine's dmesg is attached.
My /etc/vm.conf configuration file is also attached.

I don't think it is related to memory exhaustion since it sometimes
happens when the machine is not loaded (cpu and memory).

> I would add:
> * What was your "vmctl start ..." command?
 
Here, I did use : vmd -d

Will try by recompiling with VMM_DEBUG.

Thanks a lot,
Best
Olivier
OpenBSD 6.2-current (GENERIC.MP) #2: Thu Dec  7 10:13:35 CET 2017
o...@stanislas.symacx.com:/sys/arch/amd64/compile/GENERIC.MP
real mem = 4188946432 (3994MB)
avail mem = 4054945792 (3867MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x87ee6000 (43 entries)
bios0: vendor American Megatrends Inc. version "5.11" date 06/03/2016
bios0: Notebook N24_25JU
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT SSDT DBGP DBG2 SSDT UEFI 
SSDT DMAR ASF!
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) 
PXSX(S4) RP17(S4) PXSX(S4) RP18(S4) PXSX(S4) RP19(S4) PXSX(S4) RP20(S4) 
PXSX(S4) RP01(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Pentium(R) CPU 4405U @ 2.10GHz, 2095.80 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,ERMS,INVPCID,RDSEED,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Pentium(R) CPU 4405U @ 2.10GHz, 2095.14 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,ERMS,INVPCID,RDSEED,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Pentium(R) CPU 4405U @ 2.10GHz, 2095.14 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,ERMS,INVPCID,RDSEED,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Pentium(R) CPU 4405U @ 2.10GHz, 2095.14 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,ERMS,INVPCID,RDSEED,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0,

Re: USB Firewall

[Stephane HUC "PengouinBSD"]

Perhaps, using hotplugd and file /etc/hotplug/attach?

Le 01/16/18 à 18:39, Charlie Eddy a écrit :
> Hello,
> 
> Is there a method to detect and halt additional USB devices being added
> after initializing connections? Concerned about widespread vulnerability of
> keystroke injection.
> 

-- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<

Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net

Re: Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

[Marcus MERIGHI]

n.reu...@hxgn.net (Nils Reu??e), 2018.01.16 (Tue) 16:29 (CET):
> Hi all,
> 
> I'm still investigating the issue, and while reading the motherboards
> handbook, i noticed that it has a COM1 connection port.  I've never
> done anything over serial, but if i understand the FAQ correctly, i
> could attach an adapter and get the boot messages over the serial
> console, and if there is a kernel panic even play around in ddb.
> 
> Is that correct, and would i need any (other) hardware than the ones
> listed below? (sorry for german amazon)
> 
> https://www.amazon.de/dp/B0015S32W4/
> https://www.amazon.de/dp/B00QUZY4UG/

if it has the chip it says it has ("mit PL2303 Chipsatz") then:

uplcom(4) - Prolific PL-2303 USB serial adapter

Marcus

USB Firewall

[Charlie Eddy]

Hello,

Is there a method to detect and halt additional USB devices being added
after initializing connections? Concerned about widespread vulnerability of
keystroke injection.

Re : Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

[gro...@grompf.net]

The rs232 braket and the usb adapter seem good to be used acording to
your purpose

Regards,
Eric.

check list mails for malware

[Marko Cupać]

Hi,

my mail system has just blocked mail from b...@openbsd.org which
contains malware. Perhaps incoming mails to openbsd lists should be
checked for malware before they are distributed to list members?

Here's amavis report:


A virus was found: Rtf.Downloader.Obfuscation-6370377-2

Scanner detecting a virus: ClamAV-clamd

Content type: Virus
Internal reference code for the message is 38708-15/bg254irHCuHA

First upstream SMTP client IP address: [192.43.244.163]:25439
  lists.openbsd.org

Received trace: ESMTPS://[192.43.244.163]:25439 < ESMTP://127.0.0.1 <
  ESMTPS://46.102.152.157 < local://x

Return-Path: 
From: Natalia.S 
Sender: owner-b...@openbsd.org
Message-ID: 
Subject: Запрос на возврат средств клиента
The message has been quarantined as: virus-bg254irHCuHA

The message WAS NOT relayed to:
:
   250 2.7.0 ok, discarded, id=38708-15 - infected:
rtf.downloader.obfuscation-6370377-2

Virus scanner output:
  p001: Rtf.Downloader.Obfuscation-6370377-2 FOUND
  p004: Rtf.Downloader.Obfuscation-6370377-2 FOUND


Return-Path: 
Received: from openbsd.org (lists.openbsd.org [192.43.244.163])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
bits)) (No client certificate requested)
by mail.mimar.rs (Postfix) with ESMTPS id 294A9625A23E
for ; Tue, 16 Jan 2018 15:34:12 +0100
(CET) Received: from openbsd.org (localhost [127.0.0.1])
by openbsd.org (OpenSMTPD) with ESMTP id e9a25692;
Tue, 16 Jan 2018 07:34:08 -0700 (MST)
Received: from bankosantantder.com (bankosantantder.com
[46.102.152.157]) by openbsd.org (OpenSMTPD) with ESMTPS id b863df7e
(TLSv1.2:AES256-SHA256:256:NO) for ;
Tue, 16 Jan 2018 06:17:48 -0700 (MST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=bankosantantder.com; s=dkim;
h=Date:Message-Id:Reply-To:Content-type:MIME-Version:From:Subject:To;
bh=zqQlCXfowdvAkKI7caNIkqVOL643LzTD988dF1+98Ms=;
b=Z8IH5uRa0b4QCZ+m2aMA64/EIZvyl8O+Ep92Bg6J11VgMRXK1aVxvHEFT/vANurnwqVFyyEWcmU6Y72TD9IwwCF6hqV78kZl00rM/8RxDqBXrDs9AJwKFy6SEZQa8nvG7qSpZ7qCOlUgo8R3rWUO4Vw5yCIH4GnPctpPUA/IOSQ=;
Received: by bankosantantder.com with local (Exim 4.80) id
1ebOox-0006FW-0M; Tue, 16 Jan 2018 05:50:23 -0500 To: b...@openbsd.org
Subject:
=?UTF-8?B?0JfQsNC/0YDQvtGBINC90LAg0LLQvtC30LLRgNCw0YIg0YHRgNC10LTRgdGC0LIg0LrQu9C40LXQvdGC0LA=?=
From: =?UTF-8?B?TmF0YWxpYS5T?= 
MIME-Version: 1.0; Content-type: multipart/mixed;
boundary="--pnSRa1E8p2" Reply-To: natalia.shchetin...@westernunion.com
Message-Id:  Date: Tue, 16 Jan
2018 05:50:23 -0500 X-Content-Discarded: text/html
List-Help: 
List-ID: 
List-Owner: 
List-Post: 
List-Subscribe: 
List-Unsubscribe: 
X-Loop: b...@openbsd.org
Precedence: list
Sender: owner-b...@openbsd.org

-- 
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/

Re: Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

[Nils Reuße]

Hi all,

I'm still investigating the issue, and while reading the motherboards handbook, 
i noticed that it has a COM1 connection port.  I've never done anything over 
serial, but if i understand the FAQ correctly, i could attach an adapter and 
get the boot messages over the serial console, and if there is a kernel panic 
even play around in ddb.

Is that correct, and would i need any (other) hardware than the ones listed 
below? (sorry for german amazon)

https://www.amazon.de/dp/B0015S32W4/
https://www.amazon.de/dp/B00QUZY4UG/


Nils

Re: vmd: VMs are stopping with: vcpu 0 run ioctl failed: Invalid argument

[Carlos Cardenas]

On Tue, Jan 16, 2018 at 09:40:54AM +, Olivier Cherrier wrote:
> On Thu, Dec 21, 2017 at 10:57:12AM -0800, mlar...@azathoth.net wrote:
> > > Hi,
> > >
> > > I am running ~ current on amd64 (dmesg attached) and am experiencing
> > > vmd crashes. The processes responsible for operating the VMs are
> > > disappearing and I get the following messages in deamon:
> > >
> > > Dec 20 12:26:32 stanislas vmd[38693]: vcpu_run_loop: vm 14 / vcpu 0 run 
> > > ioctl failed: Invalid argument
> > > Dec 20 12:26:32 stanislas vmd[98389]: vcpu_run_loop: vm 15 / vcpu 0 run 
> > > ioctl failed: Invalid argument
> > >
> > > It happens randomly. Generally the VMs are staying up for a few hours.
> > > Is there anything I can do to troubleshoot ?
> > >
> >
> > Could be anything. What guest VM are you running here? And how much memory 
> > are
> > you assigning?
> >
> > A useful option is to run vmd manually (rcctl stop vmd && vmd -d), 
> > and/or
>
> Here is what I typically get :
>
> ...
> vionet queue notify - no space, dropping packet
> vionet queue notify - no space, dropping packet
> vionet queue notify - no space, dropping packet
> vionet queue notify - no space, dropping packet
> vionet queue notify - no space, dropping packet
> vionet queue notify - no space, dropping packet
> vionet queue notify - no space, dropping packet
> vcpu_run_loop: vm 23 / vcpu 0 run ioctl failed: Invalid argument
> vmm_sighdlr: handling signal 20
> vmm_sighdlr: attempting to terminate vm 4
> terminate_vm: terminating vmid 23
> vmm_sighdlr: calling vm_remove
> vm_remove: removing vm id 4 from running config
> vm_remove: calling vm_stop
> vm_stop: stopping vm 4
> vmd_dispatch_vmm: handling TERMINATE_EVENT for vm id 4 ret 22
> vmd_dispatch_vmm: about to stop vm id 4
> vm_stop: stopping vm 4
>
> > to enable VMM_DEBUG in sys/arch/amd64/amd64/vmm.c and rebuild the kernel.
>
> Will try that.
>
> Thank you!
> Best
> Olivier
>

Thanks for reporting the symptoms Olivier.

In order for us to reproduce this and find the root cause, we're going
to need the info that Mike was asking:
* What guest VM are you running here?
* How much memory are you assigning?

I would add:
* What was your "vmctl start ..." command?

Thanks in advance.

+--+
Carlos

Re: vmd: VMs are stopping with: vcpu 0 run ioctl failed: Invalid argument

[Olivier Cherrier]

On Thu, Dec 21, 2017 at 10:57:12AM -0800, mlar...@azathoth.net wrote:
> > Hi,
> > 
> > I am running ~ current on amd64 (dmesg attached) and am experiencing
> > vmd crashes. The processes responsible for operating the VMs are
> > disappearing and I get the following messages in deamon:
> > 
> > Dec 20 12:26:32 stanislas vmd[38693]: vcpu_run_loop: vm 14 / vcpu 0 run 
> > ioctl failed: Invalid argument
> > Dec 20 12:26:32 stanislas vmd[98389]: vcpu_run_loop: vm 15 / vcpu 0 run 
> > ioctl failed: Invalid argument
> > 
> > It happens randomly. Generally the VMs are staying up for a few hours.
> > Is there anything I can do to troubleshoot ?
> > 
> 
> Could be anything. What guest VM are you running here? And how much memory are
> you assigning?
> 
> A useful option is to run vmd manually (rcctl stop vmd && vmd -d), and/or

Here is what I typically get :

...
vionet queue notify - no space, dropping packet
vionet queue notify - no space, dropping packet
vionet queue notify - no space, dropping packet
vionet queue notify - no space, dropping packet
vionet queue notify - no space, dropping packet
vionet queue notify - no space, dropping packet
vionet queue notify - no space, dropping packet
vcpu_run_loop: vm 23 / vcpu 0 run ioctl failed: Invalid argument
vmm_sighdlr: handling signal 20
vmm_sighdlr: attempting to terminate vm 4
terminate_vm: terminating vmid 23
vmm_sighdlr: calling vm_remove
vm_remove: removing vm id 4 from running config
vm_remove: calling vm_stop
vm_stop: stopping vm 4
vmd_dispatch_vmm: handling TERMINATE_EVENT for vm id 4 ret 22
vmd_dispatch_vmm: about to stop vm id 4
vm_stop: stopping vm 4

> to enable VMM_DEBUG in sys/arch/amd64/amd64/vmm.c and rebuild the kernel.

Will try that.

Thank you!
Best
Olivier