Virtualization: vmm with Linux guests - when?

[Luis P. Mendes]

  Hi,

  I know that development time is not a determinisc thing, but
  nonetheless I'd like to know if it's closer to one, six, twelve (or
  more) months until we get the possibility to run Linux guests
  through vmm.

  I'd be happy even without a graphical interface, if the clients can
  run in xvfb mode and have graphical connections via VNC.

  What about hardware pass-through?  I don't recall to have read about
  this.  Is it something that is already possible?

  Thanks in advance for any info on this.
 

-- 


Luis Mendes

Re: Virtualization: vmm with Linux guests - when?

[Gregory Edigarov]

On 11/17/2015 05:46 PM, Luis P. Mendes wrote:

   Hi,

   I know that development time is not a determinisc thing, but
   nonetheless I'd like to know if it's closer to one, six, twelve (or
   more) months until we get the possibility to run Linux guests
   through vmm.

   I'd be happy even without a graphical interface, if the clients can
   run in xvfb mode and have graphical connections via VNC.

   What about hardware pass-through?  I don't recall to have read about
   this.  Is it something that is already possible?

   Thanks in advance for any info on this.


you must know developers don't like questions like this

Re: em(4) watchdog timeouts

[Alexis VACHETTE]

Hi Gregor,

I use the same revision than yours :

- "Intel 82583V" rev 0x00: msi

Regards,
Alexis VACHETTE.*
*
On 16/11/2015 10:12, Alexis VACHETTE wrote:
> Hi Gregor,
>
> Thank you for your feedback.
>
> Did you have some timeout on 5.6 ?
>
> On amd64 version, I experienced some on heavy network load. Is it 
> related ?
>
> Regards,
> Alexis VACHETTE.
> On 11/11/2015 21:19, Gregor Best wrote:
>> Hi Alexis,
>>
>> On Wed, Nov 11, 2015 at 08:11:15PM +, Alexis VACHETTE wrote:
>>> [...]
>>> Even with heavy network load ?
>>> [...]
>> So far, yes. I've saturated the device for about 45 Minutes with
>> something like this (the other end is my laptop):
>>
>> ## on the router
>> $ dd if=/dev/zero bs=8k | nc 172.31.64.174 55000
>> ## on my laptop
>> $ nc -l 55000 | dd of=/dev/null bs=8k
>>
>> (with two or three streams in parallel). There were about 6k
>> interrupts per second and bandwidth was about 250Mbps, which seems
>> to be the maximum the tiny CPU in this router can do. No watchdog
>> timeouts appeared, where previously something relatively low bandwidth
>> (the SSDs in router and laptop suck) like this caused one every 20
>> or 30 seconds:
>>
>> ## on the router
>> $ pax -w /home | nc 172.31.64.174 55000
>>
>> I'll keep an eye on things, but so far it looks good. Regular usage
>> works out so far as well. If you need me to run some special workload
>> for you, I'd be more than happy to do that.

Re: em(4) watchdog timeouts

[Alexis VACHETTE]

Hi Gregor,

Thank you for your feedback.

Did you have some timeout on 5.6 ?

On amd64 version, I experienced some on heavy network load. Is it related ?

Regards,
Alexis VACHETTE.
On 11/11/2015 21:19, Gregor Best wrote:

Hi Alexis,

On Wed, Nov 11, 2015 at 08:11:15PM +, Alexis VACHETTE wrote:

[...]
Even with heavy network load ?
[...]

So far, yes. I've saturated the device for about 45 Minutes with
something like this (the other end is my laptop):

## on the router
$ dd if=/dev/zero bs=8k | nc 172.31.64.174 55000
## on my laptop
$ nc -l 55000 | dd of=/dev/null bs=8k

(with two or three streams in parallel). There were about 6k
interrupts per second and bandwidth was about 250Mbps, which seems
to be the maximum the tiny CPU in this router can do. No watchdog
timeouts appeared, where previously something relatively low bandwidth
(the SSDs in router and laptop suck) like this caused one every 20
or 30 seconds:

## on the router
$ pax -w /home | nc 172.31.64.174 55000

I'll keep an eye on things, but so far it looks good. Regular usage
works out so far as well. If you need me to run some special workload
for you, I'd be more than happy to do that.

Re: Virtualization: vmm with Linux guests - when?

[lists]

>   I know that development time is not a determinisc thing

There is one very deterministic correlation though: contributions help
realise goals.

>   nonetheless I'd like to know if it's closer to one, six, twelve (or
>   more) months until we get the possibility to run Linux guests
>   through vmm.

Realistically looking at it, you could start to expect to be closer to
running OpenBSD instances first.  Optimistically, that should mean your
choice of operating system does run too, but not necessarily be
supported the way you would expect it, coming from OpenBSD developers.
Very likely it is quite a lot better than corporate support you get
anywhere else in all meanings of the word.

>   I'd be happy even without a graphical interface, if the clients can
>   run in xvfb mode and have graphical connections via VNC.

The facts are developers have to be happy with the results first.

>   What about hardware pass-through?  I don't recall to have read about
>   this.  Is it something that is already possible?

Hold your horses, next time you'll be doing profiling and complaining
for speed and fictitious scores compared to product X of some sort.  In
fact I see no meaning attached to this question since you're planning
to run a completely different kernel that ticks in a different way and
does not benefit from any similarity with the wonderful OpenBSD.

>   Thanks in advance for any info on this.

The way I see it, rushing it is wasting time empty talking, so I've
taken the opportunity to reply on my behalf, without being part of or
associated to the project in any form.  Except using the software and
having fun every second and generally being very confident decisions
are taken thoughtfully and support and appreciation eventually useful
feedback and contributions is all that is needed.  Or better, read it
from the developers, but please don't waste their time with
sensationalism questions.

Re: Linker warnings from libX11

[Theo de Raadt]

>on linking something with libX11 I got the warnings
>
>/usr/X11R6/lib/libX11.so.16.1: warning: warning: strcpy() is almost always 
>misused, please use strlcpy()
>/usr/X11R6/lib/libX11.so.16.1: warning: warning: strcat() is almost always 
>misused, please use strlcat()
>/usr/X11R6/lib/libX11.so.16.1: warning: warning: sprintf() is often misused, 
>please use snprintf()
>
>I am surprised that OpenBSD had not cleaned it's own libs.  Or is libX11(.so) 
>not used by OpenBSD itself?

X11 is not our library.  It comes from upstream.

There are too few of us, we cannot take on every problem.  Feel free to
work with the upstream to resolve that.  Good luck.

Re: Linker warnings from libX11

[Ted Unangst]

carsten.ku...@arcor.de wrote:
> Hello,
> 
> on linking something with libX11 I got the warnings
> 
> /usr/X11R6/lib/libX11.so.16.1: warning: warning: strcpy() is almost always 
> misused, please use strlcpy()
> /usr/X11R6/lib/libX11.so.16.1: warning: warning: strcat() is almost always 
> misused, please use strlcat()
> /usr/X11R6/lib/libX11.so.16.1: warning: warning: sprintf() is often misused, 
> please use snprintf()
> 
> I am surprised that OpenBSD had not cleaned it's own libs.  Or is libX11(.so) 
> not used by OpenBSD itself?

It's used by OpenBSD, but it doesn't come from OpenBSD...

Azalia Volume Too Quiet

[Daniel Wilkins]

When I try to play sounds on my Thinkpad T430 I find that the audio's rather
quiet, I've experimented a bit and found that at about 170 (mixerctl
outputs.master=170) the volume stops increasing. It just stays constant from
170 to 255, or at least the change is so quiet that I can't hear it. I've looked
around in the driver a little bit, but I'm no kernel hacker, the only thing I
noticed that might help is that for a few widgets outamp (I'm assuming output
amplify?) is muted.

dmesg (with AZALIA_DEBUG) and audioctl:
name=HD-Audio
encodings=slinear_le:16:2:1,slinear_le:20:4:1,slinear_le:24:4:1
properties=full_duplex,independent
hiwat=25
lowat=25
mode=play
play.rate=44100
play.channels=2
play.precision=16
play.bps=2
play.msb=1
play.encoding=slinear_le
play.pause=1
vplay.active=0
play.block_size=1792
play.bytes=0
play.errors=0
record.rate=44100
record.channels=2
record.precision=16
record.bps=2
record.msb=1
record.encoding=slinear_le
record.pause=1
record.active=0
record.block_size=1792
record.bytes=0
record.errors=0

OpenBSD 5.8-current (GENERIC.MP) #0: Tue Nov 17 19:22:36 EST 2015
da...@hetalia.router5d2448.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8237068288 (7855MB)
avail mem = 7983288320 (7613MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (69 entries)
bios0: vendor LENOVO version "G1ETA2WW (2.62 )" date 01/10/2014
bios0: LENOVO 2344BZU
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! 
UEFI UEFI MSDM SSDT SSDT DMAR UEFI DBG2
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3) EHC1(S3) 
EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.51 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,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 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpicpu0 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu1 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu2 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu3 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1, EHC2
acpitz0 at acpi0: critical temperature is 200 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "45N1107" serial 24045 type LION oem "LGC"
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit offline
acpithinkpad0 at acpi0
cpu0: Enhanced SpeedStep 1197 MHz: speeds: 2601, 

Rebooting hangs when /home NFS mounted locally

[Andreas Kusalananda Kähäri]

Hi,

I'm running OpenBSD, current as of 16/11-2015, in VirtualBox 5.0.10 on
an Apple system, for fun mostly.  I have a server machine ("rebus") that
serves a few diskless clients (also virtual machines).

There is a slight problem rebooting the server.  Since I'm NFS-mounting
/home from rebus:/export/home on the diskless clients *and* on the
"rebus" server itself, the server hangs if I'm rebooting using "doas
reboot" (or shutdown) as a user.

The reboot process seems to be hanging in a "nfsrcvl" state.  The user's
shell, ksh93, seems to be hanging around too (root can see it in "top",
its state is "netio"), even though the user has been kicked out (was
logged in over SSH).

This does not happen if I reboot as root, with no other user logged in.

(I also get "reboot: revoke: Inappropriate ioctl for device", regardless
of who does the reboot.)

Would it be smarter to have /home as a symlink to /export/home on the
server?  ... or NFS mount using -i?  What do others do?

/etc/export:
/export -alldirs -maproot=root internal-netgroup

/etc/netgroup:
internal-netgroup \
(rebus, root, internal) \
(ewok01, root, internal) \
(ewok02, root, internal)

/etc/fstab:
c6815a37518dd0cb.b none swap sw
c6815a37518dd0cb.a /ffs rw,softdep  1 1
c6815a37518dd0cb.d /usr ffs rw,nodev,softdep1 2
9757e0031628292b.a /srv ffs rw,nodev,nosuid,softdep 1 2
e08c770420db9a82.a /export  ffs rw,nodev,nosuid,softdep 1 2
rebus:/export/home /homenfs rw,nodev,nosuid 0 0

dmesg:

OpenBSD 5.8-current (GENERIC.MP) #0: Mon Nov 16 21:26:16 CET 2015
kk@rebus:/sys/arch/amd64/compile/GENERIC.MP
real mem = 2130640896 (2031MB)
avail mem = 2061996032 (1966MB)
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 HPET MCFG SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz, 2000.41 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,AVX,RDRAND,NXE,LONG,LAHF,ABM,ITSC
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 1000MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz, 2000.81 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,AVX,RDRAND,NXE,LONG,LAHF,ABM,ITSC
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xdc00, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
acpibat0 at acpi0: BAT0 model "1" serial 0 type VBOX oem "innotek"
acpiac0 at acpi0: AC unit online
acpivideo0 at acpi0: GFX0
pci0 at mainbus0 bus 0
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:81:58:f9
"InnoTek VirtualBox Guest Service" rev 0x00 at pci0 dev 4 function 0 not 
configured
auich0 at pci0 dev 5 function 0 "Intel 82801AA AC97" rev 0x01: apic 2 int 21, 
ICH AC97
ac97: codec id 0x83847600 (SigmaTel STAC9700)
audio0 at auich0
piixpm0 at pci0 dev 7 function 0 "Intel 82371AB Power" rev 0x08: SMBus disabled
em1 at pci0 dev 8 function 0 "Intel 82540EM" rev 0x02: apic 2 int 16, address 
08:00:27:ce:a3:b1
em2 at pci0 dev 9 function 0 "Intel 82540EM" rev 0x02: apic 2 int 17, address 
08:00:27:01:b5:15
ppb0 at pci0 dev 24 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xf2
pci1 at ppb0 bus 1
ppb1 at pci0 dev 25 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xf2
pci2 at ppb1 bus 2
pcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02
pciide0 at pci0 dev 31 function 1 "Intel 6321ESB IDE" rev 0x00: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 128-sector PIO, LBA, 5120MB, 10485760 sectors
wd1 at pciide0 channel 0 drive 1: 
wd1: 128-sector PIO, LBA, 10240MB, 20971520 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
wd2 at pciide0 channel 1 drive 0: 
wd2: 128-sector PIO, LBA, 5120MB, 10485760 sectors
atapiscsi0 at pciide0 channel 1 drive 1
scsibus1 at 

OpenSMTPD problem with filter-dnsbl

[Gianluca D.Muscelli]

Hi, I'v problem with filters in OpenSMTPD.
I would try to implement the filter-dnsbl, 
I also installed the extras opensmtpd but I can't find it!
Any suggestions?? 
Thank you!


System: OpenBSD 5.7-stable i386/GENERIC.MP
OpenSMTPD 5.4.4
opensmtpd-extras-20150119.tgz

$ ll  /usr/libexec/smtpd 
total 540
-r-xr-xr-x  1 root  bin  98640 Nov 12 23:31 makemap
-r-xr-xr-x  1 root  bin  27536 Mar  7  2015 queue-null
-r-xr-xr-x  1 root  bin  27984 Mar  7  2015 queue-ram
-r-xr-xr-x  1 root  bin  38576 Nov 12 23:31 table-ldap
-r-xr-xr-x  1 root  bin  19152 Nov 12 23:31 table-passwd
-r-xr-xr-x  1 root  bin  22128 Mar  7  2015 table-socketmap
-r-xr-xr-x  1 root  bin  19984 Nov 12 23:31 table-sqlite
-r-xr-xr-x  1 root  bin  14736 Mar  7  2015 table-stub

Linker warnings from libX11

[carsten . kunze]

Hello,

on linking something with libX11 I got the warnings

/usr/X11R6/lib/libX11.so.16.1: warning: warning: strcpy() is almost always 
misused, please use strlcpy()
/usr/X11R6/lib/libX11.so.16.1: warning: warning: strcat() is almost always 
misused, please use strlcat()
/usr/X11R6/lib/libX11.so.16.1: warning: warning: sprintf() is often misused, 
please use snprintf()

I am surprised that OpenBSD had not cleaned it's own libs.  Or is libX11(.so) 
not used by OpenBSD itself?

Carsten

Fw: No sound on speaker with azalia and Intel HD 3400

[Mike Cond]

  On Tuesday, November 17, 2015 6:57 PM, Mike Cond 
wrote:


 Hello Jonathan,thank you very much for the reply.
Your patch is against -current and I use the -release. So patching exited with
error.Actually I do not want to reinstall the system. But I manually changed
the file adding the line " this->qrks |= AZ_QRK_GPIO_UNMUTE_0;" and recompiled
the kernel.
Now with the new kernel speakers work :). 
However the mute button led is still red, but button is completely
functional.Best regards.

And here pcidump -v:
Domain /dev/pci0:
 0:0:0: Intel Core Host
    0x: Vendor ID: 8086 Product ID: 0044
    0x0004: Command: 0006 Status: 2090
    0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 02
    0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
    0x0010: BAR empty ()
    0x0014: BAR empty ()
    0x0018: BAR empty ()
    0x001c: BAR empty ()
    0x0020: BAR empty ()
    0x0024: BAR empty ()
    0x0028: Cardbus CIS: 
    0x002c: Subsystem Vendor ID: 103c Product ID: 7008
    0x0030: Expansion ROM Base Address: 
    0x0038: 
    0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
    0x00e0: Capability 0x09: Vendor Specific
 0:2:0: Intel HD Graphics
    0x: Vendor ID: 8086 Product ID: 0046
    0x0004: Command: 0007 Status: 0090
    0x0008: Class: 03 Subclass: 00 Interface: 00 Revision: 02
    0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
    0x0010: BAR mem 64bit addr: 0xd000/0x0040
    0x0018: BAR mem prefetchable 64bit addr: 0xc000/0x1000
    0x0020: BAR io addr: 0x5080/0x0008
    0x0024: BAR empty ()
    0x0028: Cardbus CIS: 
    0x002c: Subsystem Vendor ID: 103c Product ID: 7008
    0x0030: Expansion ROM Base Address: 
    0x0038: 
    0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
    0x0090: Capability 0x05: Message Signaled Interrupts (MSI)
    0x00d0: Capability 0x01: Power Management
    0x00a4: Capability 0x13: PCI Advanced Features
 0:22:0: Intel 3400 MEI
    0x: Vendor ID: 8086 Product ID: 3b64
    0x0004: Command: 0006 Status: 0010
    0x0008: Class: 07 Subclass: 80 Interface: 00 Revision: 06
    0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 00
    0x0010: BAR mem 64bit addr: 0xd4724000/0x0010
    0x0018: BAR empty ()
    0x001c: BAR empty ()
    0x0020: BAR empty ()
    0x0024: BAR empty ()
    0x0028: Cardbus CIS: 
    0x002c: Subsystem Vendor ID: 103c Product ID: 7008
    0x0030: Expansion ROM Base Address: 
    0x0038: 
    0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
    0x0050: Capability 0x01: Power Management
    0x008c: Capability 0x05: Message Signaled Interrupts (MSI)
 0:25:0: Intel 82577LM
    0x: Vendor ID: 8086 Product ID: 10ea
    0x0004: Command: 0007 Status: 0010
    0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 05
    0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
    0x0010: BAR mem 32bit addr: 0xd470/0x0002
    0x0014: BAR mem 32bit addr: 0xd4729000/0x1000
    0x0018: BAR io addr: 0x5000/0x0020
    0x001c: BAR empty ()
    0x0020: BAR empty ()
    0x0024: BAR empty ()
    0x0028: Cardbus CIS: 
    0x002c: Subsystem Vendor ID: 103c Product ID: 7008
    0x0030: Expansion ROM Base Address: 
    0x0038: 
    0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
    0x00c8: Capability 0x01: Power Management
    0x00d0: Capability 0x05: Message Signaled Interrupts (MSI)
    0x00e0: Capability 0x13: PCI Advanced Features
 0:26:0: Intel 3400 USB
    0x: Vendor ID: 8086 Product ID: 3b3c
    0x0004: Command: 0006 Status: 0290
    0x0008: Class: 0c Subclass: 03 Interface: 20 Revision: 05
    0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
    0x0010: BAR mem 32bit addr: 0xd4728000/0x0400
    0x0014: BAR empty ()
    0x0018: BAR empty ()
    0x001c: BAR empty ()
    0x0020: BAR empty ()
    0x0024: BAR empty ()
    0x0028: Cardbus CIS: 
    0x002c: Subsystem Vendor ID: 103c Product ID: 7008
    0x0030: Expansion ROM Base Address: 
    0x0038: 
    0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
    0x0050: Capability 0x01: Power Management
    0x0058: Capability 0x0a: Debug Port
    0x0098: Capability 0x13: PCI Advanced Features
 0:27:0: Intel 3400 HD Audio
    0x: Vendor ID: 8086 Product ID: 3b56
    0x0004: Command: 0006 Status: 0010
    0x0008: Class: 04 Subclass: 03 

Re: Virtualization: vmm with Linux guests - when?

[Peter Kay]

On 17 November 2015 15:46:59 GMT+00:00, "Luis P. Mendes"  
wrote:
>  Hi,
>
>  I know that development time is not a determinisc thing, but
>  nonetheless I'd like to know if it's closer to one, six, twelve (or
>  more) months until we get the possibility to run Linux guests
>  through vmm.
You'd be much better using Xen; I'd recommend using the latest version with a 
Linux dom0 (I know, but it has the most functionality), but you can use a 
NetBSD dom0 if you wish - it does support passthrough as does bhyve on FreeBSD 
(haven't tried).

I presume you don't need GPU passthrough - if you do, KVM is your best bet, 
although Xen can work, with the right hardware.