[Bug 209427] if_vtnet(4) is not sending LINK_(UP|DOWN) events
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209427 Roman Bogorodskiychanged: What|Removed |Added Attachment #170183|0 |1 is obsolete|| --- Comment #2 from Roman Bogorodskiy --- Created attachment 170409 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=170409=edit proposed fix, v2 Attaching a new patch that's slightly less dirty than the previous one. Specifically, it does not change vtnet_is_link_up() behavior, but extends vtnet_update_link_status() event triggering. Specifically, if link is here and IFF_DRV_RUNNING is set, but interface was not active, we mark it active and trigger notification. If there is no link or IFF_DRV_RUNNING, then we consider interface down. Also, add a call to vtnet_update_link_status() on mtu change to trigger events as well like other if drivers usually do. So, a pair of ifconfig vtnet0 down/up followed by ifconfig vtnet0 mtu 1496 look like this in devd: !system=IFNET subsystem=vtnet0 type=LINK_DOWN !system=IFNET subsystem=vtnet0 type=LINK_UP !system=IFNET subsystem=vtnet0 type=LINK_DOWN !system=IFNET subsystem=vtnet0 type=LINK_UP !system=IFNET subsystem=vtnet0 type=LINK_DOWN !system=IFNET subsystem=vtnet0 type=LINK_UP I'm yet to figure out how I can test link status change in bhyve so vtnet_is_link_up() returned something other that 1. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Vmm.ko to kernel
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: https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html If you still want to build a custom kernel, please refer to this guide: https://www.freebsd.org/doc/handbook/kernelconfig.html If this does not help still, please be more specific, "is not works" is not really helpful, please post some more details on what you are doing and exact errors you get. Roman Bogorodskiy signature.asc Description: PGP signature
Re: Virt-manager issue (Solved)
Luciano Mannucci wrote: > On Mon, 16 May 2016 19:16:46 +0300 > Roman Bogorodskiywrote: > > > 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 from virt-manager: > > > > > > Error launching details: Requiring namespace 'Gtk' version '2.0', but > > > '3.0' > > > is already loaded > > > > > > I'm I missing something obvious? > > > > Hi Luciano, > > > > Thanks for the report. A couple of questions: > > > > 1. By "open virtual host" you mean right click on VM -> context menu -> > >Open, right? > Yes. > > > 2. Could you run virt-manager from console with the "--debug" flag and > > copy/paste complete error message (with traceback if it prints one)? > Well, afer looking at help->about I noticed it was sayin 1.2 instead of > 1.3. I thig the pkg upgrade didn't remove all old bits of the previous > version, so I removed virt-manager via "pkg delete" and reinstalled. > Now everything works as expected... :-) > > BTW, it was on a 10.1-RELEASE-p26 amd64. Hm, it's strange that upgrade didn't work as expected, but if the logs are gone there's nothing that could be done to debug that. Anyway, good that it's working finally. > Cheers && Many Thanks, > > luciano. > -- > /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) > \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 > X AGAINST HTML MAIL/ E-MAIL: posthams...@sublink.sublink.org > / \ AND POSTINGS/ WWW: http://www.lesassaie.IT/ Roman Bogorodskiy ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: FreeBSD/XEN Dom XAPI
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 before trying to use XOA or XenCenter, those are specific products that only work with XenServer. I don't know how much effort it would take to get XAPI working on FreeBSD, but I'm quite sure it's not a trivial task. OTOH, there are other managers that you can probably use with FreeBSD/Xen, like OpenStack, OpenNebula or similar managers that are designed to work with the open source Xen Project toolstack (xl). Or you can also install libvirt and try to use virsh or any manager that has libvirt bindings. Roger. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Virt-manager issue (Solved)
On Mon, 16 May 2016 19:16:46 +0300 Roman Bogorodskiywrote: > 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 from virt-manager: > > > > Error launching details: Requiring namespace 'Gtk' version '2.0', but '3.0' > > is already loaded > > > > I'm I missing something obvious? > > Hi Luciano, > > Thanks for the report. A couple of questions: > > 1. By "open virtual host" you mean right click on VM -> context menu -> >Open, right? Yes. > 2. Could you run virt-manager from console with the "--debug" flag and > copy/paste complete error message (with traceback if it prints one)? Well, afer looking at help->about I noticed it was sayin 1.2 instead of 1.3. I thig the pkg upgrade didn't remove all old bits of the previous version, so I removed virt-manager via "pkg delete" and reinstalled. Now everything works as expected... :-) BTW, it was on a 10.1-RELEASE-p26 amd64. Cheers && Many Thanks, luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL/ E-MAIL: posthams...@sublink.sublink.org / \ AND POSTINGS/ WWW: http://www.lesassaie.IT/ ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Vmm.ko to kernel
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 https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: pptdevs option crashes system
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 through post-boot rather than using the loader.conf option. E.g.: # devctl set driver pci0:11:0:0 ppt Currently there's no way to undo this, you can can 'set driver' to a "native" driver if one exists. -- John Baldwin ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"