search for: autoselection

...th 5.2.0, libvirt has a way to select the firmware by > specifying its type, provided configuration files for the firmware are > shipped. Currently we start the appliance as UEFI if any of the firmware > are found, so instead we can try to just set the firmware type iff: > - the libvirt autoselection works > - the 'efi' firmware is available > > The only behaviour change is that the default firmware may be a > non-debug version, so we get no debug messages even when running in > verbose mode. This most probably will need an addition in libvirt to > select this feature...

Starting with 5.2.0, libvirt has a way to select the firmware by specifying its type, provided configuration files for the firmware are shipped. Currently we start the appliance as UEFI if any of the firmware are found, so instead we can try to just set the firmware type iff: - the libvirt autoselection works - the 'efi' firmware is available The only behaviour change is that the default firmware may be a non-debug version, so we get no debug messages even when running in verbose mode. This most probably will need an addition in libvirt to select this feature among the available firmwares...

So, with the updated HAL, I'm now able to negotiate an IP address via DHCP over the WLAN. Huzzah! But I've got two questions (now that I can use the card): ath(4) doesn't contain a list of media nor mediaopt settings that can be used. Some are detailed down in EXAMPLES, but there's no comprehensive list. (As well, and this is minor, the speeds are explicitly listed for 802.11a

Starting with 5.2.0, libvirt has a way to select automatically the firmware for a guest using an attribute of the <os> tag. Hence, use this information (when available, of course) to flag the firmware used by the guest. --- v2v/parse_libvirt_xml.ml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/v2v/parse_libvirt_xml.ml b/v2v/parse_libvirt_xml.ml index

I have just checked the Openbsd box on the if interface. fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:02:55:30:54:28 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::202:55ff:fe30:5428%fxp0 prefixlen 64 scopeid 0x1 xl0:

My intention is to set up tinc so that I can connect from home to an office network. All CPUs are running MacOs X, 10.2.8 or 10.3.5. I have read the tinc manual, tincd.8 and tinc.conf.5. However, I am still unclear about a few issues. First and foremost, how to I setup the VPN interfaces on the hosts, on MacOs X? Which file do I have to alter and what is the exact syntax on Os X to setup

Hello, I have given myself quite the headache trying to make this VPN work correctly. I am attempting to use racoon to establish keys and construct an encrypted tunnel between one host(A.A.A.A) with a routable IP address and another that has a private address(10.0.0.2) with a cable modem(B.B.B.B) forwarding all ports to the private address(10.0.0.2). Here is a quick topographic dipiction of the

...range(xy$y[is.finite(xy$y)]) else if(length(ylim) == 2 & ylim[2] == Inf) c(ylim[1], max(xy$y[is.finite(xy$y)]) else ylim and some more if-else statements if cases like ylim=c(0, -Inf), ylim=c(Inf, 0), ylim=c(-Inf, 0) and ylim=c(-Inf, Inf)[as a replacement for NULL/ autoselection] and ylim=c(Inf, -Inf)[autoselection, reversed y axis] should be handled correctly. I would find such a feature useful. Do you think it would interfere with other functions? Thank you for your consideration. Best wishes, Matthias Gondan

I finally got a 10G card that is recognized by FreeBSD (9.1-stable): ... ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.4.8> port 0xecc0-0xecdf mem 0xd9e80000-0xd9efffff,0xd9ff8000-0xd9ffbfff irq 40 at device 0.0 on pci4 ix0: Using MSIX interrupts with 9 vectors ix0: RX Descriptors exceed system mbuf max, using default instead! ix0: Ethernet address: 90:e2:ba:29:c0:54

Hi, tuning my network fixing nic's speed and duplex (both on server and switch) i got this error with bce driver: # ifconfig bce0 bce0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4> ether 00:15:c5:fe:11:01 inet 192.168.1.13 netmask 0xffffff00 broadcast

Hi all, the patch "qemu-vnc-wmvi.patch" adds support for the WMVi pseudoencoding in qemu vnc server. If the client implements it, it is supposed to be able to change colour depth when receiving a WMVi message. Since I didn''t know any client that supports it and I wanted to test the implementation before submitting any patch I also modified vncviewer to support WMVi. The

On Thu, 24 May 2018 09:55:14 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > --- a/drivers/net/hyperv/Kconfig > +++ b/drivers/net/hyperv/Kconfig > @@ -2,5 +2,6 @@ config HYPERV_NET > tristate "Microsoft Hyper-V virtual network driver" > depends on HYPERV > select UCS2_STRING > + select FAILOVER When I take a working kernel config, add

On Thu, 24 May 2018 09:55:14 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > --- a/drivers/net/hyperv/Kconfig > +++ b/drivers/net/hyperv/Kconfig > @@ -2,5 +2,6 @@ config HYPERV_NET > tristate "Microsoft Hyper-V virtual network driver" > depends on HYPERV > select UCS2_STRING > + select FAILOVER When I take a working kernel config, add

Hello, I have installed samba 2.2.2 from the ports collection in FreeBSD. It dumps core whenever someone tries to use the nmbd server. I can connect OK if I do smbclient //10.25.165.3 -U user but not by doing smbclient //server -U user Here's the relevant part of the samba logfile: [2001/12/21 14:23:20, 2] lib/interface.c:add_interface(85) added interface ip=127.0.0.1

Hello Samba folks, I thought you might be able to help me. I have 2 machines, 1 is FreeBSD, 1 is win95. They can't ping each other, but the bsd box comes up in Network Nieghborhood when Samba is active. What's going on? Is it not possible to ping a windows machine from a unix box? They are on the same hub via UTP. IPs are 192.168.1.x and netmasks are same (255.255.255.0).

I recently reconfigured a box running FreeBSD 5.3 with Samba v. 3.0.7 running as PDC. It was servicing 2 networks, processing logons for 192.168.200.0/24 and 192.168.115.0/24. The reason for 2 networks was security, 115.0/24 had some stuff on it that the users on 200.0/24 shouldn't have access to. Before the reconfiguration, the system was working 100%. To make everything better I flattened

...ed=yes requires a firmware image that advertises the acpi-s4 feature, and you probably don't have one on your system. For example, on my Fedora 38 machine: $ grep acpi-s4 /usr/share/qemu/firmware/*.json $ Yeah, the error message is not very helpful. Unfortunately, due to the way firmware autoselection works, emitting a better one would be pretty much impossible :( -- Andrea Bolognani / Red Hat / Virtualization

Hi list, since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now on 9.1 we recognize that after a random period of time, sometimes a week, sometimes only a day, the system doesn't send any packets out. The phenomenon is that you can't login via ssh, nfs and istgt is not operative. Yet you can login on the console and execute commands. A clean shutdown isn't possible

Hello list! When em0 has an inet address while bridge0 doesn't, it seems to be OK: ----- bs1% uname -a FreeBSD bs1.sp34.ru 7.0-STABLE FreeBSD 7.0-STABLE #0: Sun May 25 20:15:26 MSD 2008 root@bs1.sp34.ru:/usr/obj/usr/src/sys/BSM i386 bs1% ifconfig em0; ifconfig tap0; ifconfig bridge0 em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

Hi, i've got this problem with my jail and i'm abolutly lost as in the why of it. I previously posted this on comp.unix.bsd.freebsd.misc but i was advised to send here I was unable to find help on google :( To resume quick, when i'm in a jail, netstat doesn't work properly. Hopefully i have provided sufficient information for anyone willing to help me :p First of all, my system :