[Bug 209427] if_vtnet(4) is not sending LINK_(UP|DOWN) events

2016-05-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209427 Roman Bogorodskiy changed: What|Removed |Added Attachment #170183|0 |1

Re: Vmm.ko to kernel

2016-05-17 Thread Roman Bogorodskiy
kakawkaization kaka wrote: > Hello, I can't find instruction how to include module vmm to kernel. > Instruction like : > device vmm > Is not works. > > Please help me to solve this problem, thanks. Hi, I suggest to follow this instruction:

Re: Virt-manager issue (Solved)

2016-05-17 Thread Roman Bogorodskiy
Luciano Mannucci wrote: > On Mon, 16 May 2016 19:16:46 +0300 > Roman Bogorodskiy wrote: > > > Luciano Mannucci wrote: > > > > > > > > Hello all! I hpoe this is the right list for that kind of things... > > > > > > After last upgrade to libvirt 1.3.4, I get an error

Re: FreeBSD/XEN Dom XAPI

2016-05-17 Thread Roger Pau Monné
On Sat, May 14, 2016 at 04:07:49AM +0200, Outback Dingo wrote: > seems there is no management interface for XEN/FreeBSD via XAPI, any > suggestions or pointers for getting XOA, or XenCenter to manage the > FreeBSD/XEN boxes ?? just a quick inquiry. You would have to get XAPI working on FreeBSD

Re: Virt-manager issue (Solved)

2016-05-17 Thread Luciano Mannucci
On Mon, 16 May 2016 19:16:46 +0300 Roman Bogorodskiy wrote: > Luciano Mannucci wrote: > > > > > Hello all! I hpoe this is the right list for that kind of things... > > > > After last upgrade to libvirt 1.3.4, I get an error when I try to > > open a virtual host detail

Vmm.ko to kernel

2016-05-17 Thread kakawkaization kaka
Hello, I can't find instruction how to include module vmm to kernel. Instruction like : device vmm Is not works. Please help me to solve this problem, thanks. ___ freebsd-virtualization@freebsd.org mailing list

Re: pptdevs option crashes system

2016-05-17 Thread John Baldwin
On Sunday, April 24, 2016 11:57:55 AM David Ehrmann wrote: > It sounds like the bug I reported a while ago, but on a different chip > family: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207602 As a workaround on 10.3 and later you can use 'devctl set driver' to mark devices for pass