search for: autoselect

...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 feat...

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 firmwa...

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: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:01:02:78:11:e8...

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

...d B.B.B.B/32 A.A.A.A/32 ipencap -P in ipsec esp/tunnel/B.B.B.B-A.A.A.A/require; ifconfig output: dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.121.253 netmask 0xffffff00 broadcast 192.168.121.255 ether 00:a0:cc:d1:a2:df media: Ethernet autoselect (100baseTX <full-duplex>) status: active dc1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet A.A.A.A netmask 0xfffffff8 broadcast 216.160.154.159 ether 00:a0:cc:62:f0:6a media: Ethernet autoselect (100baseTX <full-duplex>)...

...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

...d ifconfig: ix0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,TSO4,VLAN_HWTSO> ether 90:e2:ba:29:c0:54 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> media: Ethernet autoselect status: no carrier ix1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,TSO4,VLAN_HWTSO> ether 90:e2:ba:29:c0:55 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> m...

...0 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 192.168.1.255 media: Ethernet autoselect (1000baseSX <full-duplex>) status: active # ifconfig bce0 media 1000baseSX ifconfig: SIOCSIFMEDIA (media): Device not configured or (according to bce(4)): # ifconfig bce0 media 1000baseTX ifconfig: SIOCSIFMEDIA (media): Device not configured system: # uname -rsm FreeBSD 7.1-RELEASE...

...ports it and I wanted to test the implementation before submitting any patch I also modified vncviewer to support WMVi. The patch "vncviewer-wmvi.patch" is meant to be applied to the realvnc vncviewer unix client version 4.1.2, using patch -p1. Try executing vncviewer with FullColour=1 AutoSelect=0. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Regards, Stefano Stabellini _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...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 the patches then do make oldconfig It is not autoselecting FAILOVER, it prompts me for it. This means if user says no then a non-working netvsc device is made.

...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 the patches then do make oldconfig It is not autoselecting FAILOVER, it prompts me for it. This means if user says no then a non-working netvsc device is made.

...0 [2001/12/21 14:23:20, 2] lib/interface.c:interpret_interface(134) can't determine netmask for 10.25.165.3 It seems to have problems with my network card, so here's my ifconfig output: fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 ether 00:b0:d0:aa:82:cf media: Ethernet autoselect (none) status: no carrier fxp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 10.25.165.1 netmask 0xffffff00 broadcast 10.25.165.255 inet 10.25.165.2 netmask 0xffffffff broadcast 10.25.165.2 inet 10.25.165.3 netmask 0xffffffff broadcast 10.25.165.3 ether 00:02:b3:1b:49...

...network like this that mabye I can bounce a few questions off you? Heres some output to look at: >> ifconfig -a pn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 ether 87:ff:87:ff:87:ff media: autoselect (10baseT/UTP <half-duplex>) supported media: autoselect 100baseT4 100baseTX <full-duplex> 100baseTX <half-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex> 10baseT/UTP lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 tun0:...

...xp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=8<VLAN_MTU> inet 192.168.77.1 netmask 0xffffff00 broadcast 192.168.77.255 inet6 fe80::2a0:c9ff:fe89:ca86%fxp0 prefixlen 64 scopeid 0x1 ether 00:a0:c9:89:ca:86 media: Ethernet autoselect (100baseTX <full-duplex>) status: active xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 options=9<RXCSUM,VLAN_MTU> ether 00:04:75:ad:a2:a4 media: Ethernet autoselect (none) status: no carrier xl1: flags=8802<BROADCAST,SIMPLEX,MULTI...

...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

...reenas. Don't be confused. igb0: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 00:25:90:34:c1:12 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 00:25:90:34:c1:13 inet 172.16.1.6 netmask 0xfffff000 broadcast 1...

...bs1% ifconfig em0; ifconfig tap0; ifconfig bridge0 em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=98<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> ether 00:0c:f1:6c:37:4c inet 192.168.16.30 netmask 0xffffff00 broadcast 192.168.16.255 media: Ethernet autoselect (100baseTX <full-duplex>) status: active tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 00:bd:3e:24:00:00 bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether ea:8b:1f:65:2a:5c id 00:00:00:00:00:00 priori...

...is what ifconfig looks like OUT of jail : rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 10.0.0.2 netmask 0xffffff00 broadcast 10.0.0.255 inet6 fe80::250:8dff:fe47:e567%rl0 prefixlen 64 scopeid 0x1 ether 00:50:8d:47:e5:67 media: Ethernet autoselect (10baseT/UTP) status: active rl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 10.0.2.1 netmask 0xffffff00 broadcast 10.0.2.255 inet6 fe80::250:fcff:fe47:8438%rl1 prefixlen 64 scopeid 0x2 inet 10.0.2.6 netmask 0xffffffff broadcast 10.0.2.6...