On Wed, Sep 07, 2016 at 07:07:01PM +0300, Mart Tõnso wrote:
> >> OpenBSD 6.0-current (TIMMU) #4: Wed Sep  7 00:35:13 EEST 2016
> >
> > Not going to help with custom kernels. Work on -current on real
> 
> Only reason that I'm using a custom kernel is to enable vmm, so this
> is a catch 22.

True. If it was merely GENERIC[.MP] with vmm enabled, then fine. But a
kernel named "TIMMU" could deserve some explanation as to what's been
done to it.

/Alexander

> 
> > hardware with a standard kernel if you want to play with vmm please.
> 
> Hm, yes, bare metal makes sense
> 
> ---
> Regards,
> 
> Mart
> 
> > -ml
> >
> >>     r...@bsd1.lan:/usr/src/sys/arch/amd64/compile/TIMMU
> >> real mem = 1056899072 (1007MB)
> >> avail mem = 1020399616 (973MB)
> >> mpath0 at root
> >> scsibus0 at mpath0: 256 targets
> >> mainbus0 at root
> >> bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe1000 (10 entries)
> >> bios0: vendor innotek GmbH version "VirtualBox" date 12/01/2006
> >> bios0: innotek GmbH VirtualBox
> >> acpi0 at bios0: rev 2
> >> acpi0: sleep states S0 S5
> >> acpi0: tables DSDT FACP APIC SSDT
> >> acpi0: wakeup devices
> >> acpitimer0 at acpi0: 3579545 Hz, 32 bits
> >> acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
> >> cpu0 at mainbus0: apid 0 (boot processor)
> >> cpu0: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3312.50 MHz
> >> cpu0: 
> >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,RDRAND,NXE,LONG,LAHF,ABM,3DNOWP,ITSC,RDSEED,CLFLUSHOPT
> >> cpu0: 256KB 64b/line 8-way L2 cache
> >> cpu0: smt 0, core 0, package 0
> >> mtrr: CPU supports MTRRs but not enabled by BIOS
> >> cpu0: apic clock running at 1009MHz
> >> cpu1 at mainbus0: apid 1 (application processor)
> >> cpu1: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3345.27 MHz
> >> cpu1: 
> >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,RDRAND,NXE,LONG,LAHF,ABM,3DNOWP,ITSC,RDSEED,CLFLUSHOPT
> >> cpu1: 256KB 64b/line 8-way L2 cache
> >> cpu1: smt 0, core 1, package 0
> >> ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
> >> acpiprt0 at acpi0: bus 0 (PCI0)
> >> acpicpu0 at acpi0: C1(@1 halt!)
> >> acpicpu1 at acpi0: C1(@1 halt!)
> >> "PNP0303" at acpi0 not configured
> >> "PNP0F03" at acpi0 not configured
> >> "PNP0501" at acpi0 not configured
> >> acpiac0 at acpi0: AC unit online
> >> acpivideo0 at acpi0: GFX0
> >> pci0 at mainbus0 bus 0
> >> pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
> >> pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
> >> pciide0 at pci0 dev 1 function 1 "Intel 82371AB IDE" rev 0x01: DMA, 
> >> channel 0 configured to compatibility, channel 1 configured to 
> >> compatibility
> >> wd0 at pciide0 channel 0 drive 0: <VBOX HARDDISK>
> >> wd0: 128-sector PIO, LBA, 20480MB, 41943040 sectors
> >> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> >> atapiscsi0 at pciide0 channel 1 drive 0
> >> scsibus1 at atapiscsi0: 2 targets
> >> cd0 at scsibus1 targ 0 lun 0: <VBOX, CD-ROM, 1.0> ATAPI 5/cdrom removable
> >> cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> >> vga1 at pci0 dev 2 function 0 "InnoTek VirtualBox Graphics Adapter" rev 
> >> 0x00
> >> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> >> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> >> em0 at pci0 dev 3 function 0 "Intel 82540EM" rev 0x02: apic 2 int 19, 
> >> address 08:00:27:4e:af:77
> >> "InnoTek VirtualBox Guest Service" rev 0x00 at pci0 dev 4 function 0 not 
> >> configured
> >> ohci0 at pci0 dev 6 function 0 "Apple Intrepid USB" rev 0x00: apic 2 int 
> >> 22, version 1.0
> >> piixpm0 at pci0 dev 7 function 0 "Intel 82371AB Power" rev 0x08: apic 2 
> >> int 23
> >> iic0 at piixpm0
> >> isa0 at pcib0
> >> isadma0 at isa0
> >> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> >> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> >> pckbd0 at pckbc0 (kbd slot)
> >> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> >> pms0 at pckbc0 (aux slot)
> >> wsmouse0 at pms0 mux 0
> >> pcppi0 at isa0 port 0x61
> >> spkr0 at pcppi0
> >> usb0 at ohci0: USB revision 1.0
> >> uhub0 at usb0 configuration 1 interface 0 "Apple OHCI root hub" rev 
> >> 1.00/1.00 addr 1
> >> vmm at mainbus0 not configured
> >> vscsi0 at root
> >> scsibus2 at vscsi0: 256 targets
> >> softraid0 at root
> >> scsibus3 at softraid0: 256 targets
> >> root on wd0a (0726640cbb73e288.a) swap on wd0b dump on wd0b
> >> o
> >> On Wed, Sep 07, 2016 at 08:50:02AM -0700, Mike Larkin wrote:
> >> > On Wed, Sep 07, 2016 at 09:43:47PM +0300, Mart T??nso wrote:
> >> > > Hello,
> >> > >
> >> > > I'm trying to get vmd working, but am failing so far.
> >> > >
> >> > > What I've done:
> >> > >
> >> > > Custom kernel config to enable vmm:
> >> > >
> >> > > include "arch/amd64/conf/GENERIC"
> >> > >
> >> > > option  MULTIPROCESSOR
> >> > > #option MP_LOCKDEBUG
> >> > >
> >> > > cpu*            at mainbus?
> >> > >
> >> > > # enable vmm
> >> > > vmm0   at mainbus0
> >> > > # EOF
> >> > >
> >> > >
> >> > > /etc/vm.conf:
> >> > > # vm.conf
> >> > > sets="/var/www/htdocs/pub/OpenBSD/snapshots/amd64/"
> >> > >
> >> > > # OpenBSD snapshot install test
> >> > > vm "openbsd.vm" {
> >> > >         memory 512M
> >> > >         kernel $sets "bsd.rd"
> >> > >
> >> > >         # First disk from 'vmctl create "/home/vm/OpenBSD.img" -s 4G'
> >> > >         disk "/home/vm/OpenBSD.img"
> >> > >
> >> > >         # Second disk from OpenBSD contains the install sets
> >> > >         disk $sets "install59.fs"
> >> > >
> >> > >         # Interface will show up as tap(4) on the host and as vio(4) 
> >> > > in the VM
> >> > >         interfaces 1
> >> > > }
> >> > > # EOF
> >> > >
> >> > >
> >> > > And this is where it all falls apart:
> >> > >
> >> > > # vmd -vd
> >> > > vmd: /dev/vmm: Operation not supported by device
> >> > >
> >> > >
> >> > > What am I missing here?
> >> > >
> >> > > ---
> >> > > Regards,
> >> > >
> >> > > Mart
> >> > >
> >> >
> >> > Probably unsupported cpu. But you didn't give us even a dmesg, so who 
> >> > knows.

Reply via email to