search for: standy

Hi, I have a Packard Bell Easynote B notebook with CentOS 4.2 on it. I activated the standby option and it seems that entering the standby is OK (in a few seconds the display and hdd are closed, the power led is clipping). But when I try to restart the notebook, the hdd sems like it reads something, but the display remains blank. Also ctrl+alt+backspace or ctrl+alt+del don't have any efect.

Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: >Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: [...] >>+ >>+ err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, >>+ failover_dev); >>+ if (err) { >>+ netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n",

Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: >Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: [...] >>+ >>+ err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, >>+ failover_dev); >>+ if (err) { >>+ netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n",

...tdev_lower_state_changed() when the active slave > > device changes from primary->backup of backup->primary and whenever link > > state of a slave changes > > > Sure. will look into it.? Do you think this will help with the issue > you saw with having to change mac on standy twice to get the init scripts > working? We are now going to block changing the mac on both standby and > failover. > > Also, i was wondering if we should set dev->flags to IFF_MASTER on failover > and IFF_SLAVE on primary and standby. We do need a way to find things out, that...

...d since VF does I wish people would say primary/standby and not "VF" :) > not allow it as you say, once it will be enslaved, the mac change could > not be done. Seems like a correct behavior to me what if primary does not allow mac changes and is attached after mac is changed on standy? > and is in-sync with how > bond/team behaves. I think in the end virtio can just block MAC changes for simplicity. I personally don't see softmac as a must have feature in v1, we can add it later. What's the situation with init scripts and whether it's possible to make them...

...ccessfully negotiated or not. The upper layer can then decide if it should hot plug a VF with the same MAC and manage the 2 links. If VF is successfully hot plugged, virtio-net link should be disabled. > >> How about control the visibility of standby device? >> >> Thanks > standy the always there to guarantee no downtime. > >>> However just for testing purposes, we could add a non-stable >>> interface "x-standby" with the understanding that as any >>> x- prefix it's unstable and will be changed down the road, >>> likely i...

...ccessfully negotiated or not. The upper layer can then decide if it should hot plug a VF with the same MAC and manage the 2 links. If VF is successfully hot plugged, virtio-net link should be disabled. > >> How about control the visibility of standby device? >> >> Thanks > standy the always there to guarantee no downtime. > >>> However just for testing purposes, we could add a non-stable >>> interface "x-standby" with the understanding that as any >>> x- prefix it's unstable and will be changed down the road, >>> likely i...

On 2018?06?12? 01:26, Michael S. Tsirkin wrote: > On Mon, May 07, 2018 at 04:09:54PM -0700, Sridhar Samudrala wrote: >> This feature bit can be used by hypervisor to indicate virtio_net device to >> act as a standby for another device with the same MAC address. >> >> I tested this with a small change to the patch to mark the STANDBY feature 'true' >> by

On 2018?06?12? 01:26, Michael S. Tsirkin wrote: > On Mon, May 07, 2018 at 04:09:54PM -0700, Sridhar Samudrala wrote: >> This feature bit can be used by hypervisor to indicate virtio_net device to >> act as a standby for another device with the same MAC address. >> >> I tested this with a small change to the patch to mark the STANDBY feature 'true' >> by

...> Also, please call netdev_lower_state_changed() when the active slave > device changes from primary->backup of backup->primary and whenever link > state of a slave changes > Sure. will look into it.? Do you think this will help with the issue you saw with having to change mac on standy twice to get the init scripts working? We are now going to block changing the mac on both standby and failover. Also, i was wondering if we should set dev->flags to IFF_MASTER on failover and IFF_SLAVE on primary and standby. netvsc does this. Does this help with the init scripts and network ma...

...lity of the primary device. > > The problem is legacy guest won't use primary device at all if we do this. And that's by design - I think it's the only way to ensure the legacy guest isn't confused. > How about control the visibility of standby device? > > Thanks standy the always there to guarantee no downtime. > > However just for testing purposes, we could add a non-stable > > interface "x-standby" with the understanding that as any > > x- prefix it's unstable and will be changed down the road, > > likely in the next relea...

...m Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: baumber at hotmail.com QA Contact: xorg-team at lists.x.org Created attachment 113124 --> https://bugs.freedesktop.org/attachment.cgi?id=113124&action=edit syslog messages standy and resume - working Hello, I use Kubuntu 14.04.x together with a nvidia graphics card NVC1 (GF108) GT 430 passive and driver nouveau. Standby and resume works with the nouveau driver, but hibernate and resume don't. There is a black screen after resume, then the monitor goes off (no signa...

...monitor. WinUPSC re-uses the UPSC logic to poll the UPS. > This initial version was tested against two Eaton UPS devices connected to my NAS device. 4 PC's monitor the UPS they are depending on, > WinUPSC is now robuust enough to deal with all kind of circumstances (e.g. continue after standy, hibernation, disconnects etc). > > I really appriciate the NUT initiative and would like to actively contribute with this tool, but never published code to the open source community before. Can it be included in the NUT Windows distribution? Or just a link to e.g. sourgeforge on the Downlo...

On Jan 12, 2020, at 12:58 PM, Gene Heskett wrote: > > But this doesn't pass the smell test, 3 other machines that are trained > to reboot when power returns and have no ups fitted, were NOT rebooted > as evidenced by their reported uptimes, one of which shows a 144 day > uptime. So why should this have been logged via a -wall bc to every > login it is servicing? >

...layer probably already has at least a hunch that it's a new guest otherwise why bother specifying the feature at all - you save even more resources without it. > > > > > > How about control the visibility of standby device? > > > > > > Thanks > > standy the always there to guarantee no downtime. > > > > > > However just for testing purposes, we could add a non-stable > > > > interface "x-standby" with the understanding that as any > > > > x- prefix it's unstable and will be changed down the...

I'm fairly new to VoIP, and brand-new to Asterisk. I am wondering what are the best/least expensive phones or phone adapters to use with Asterisk, both wired and WiFi. I would appreciate any insight or recommendations you may have. Thanks, James arbaughj@myrealbox.com

...auto-manages the presence of the primary, and hot plug the device as needed before or after the migration. -Siwei > > >> >> >>>>> How about control the visibility of standby device? >>>>> >>>>> Thanks >>>> >>>> standy the always there to guarantee no downtime. >>>> >>>>>> However just for testing purposes, we could add a non-stable >>>>>> interface "x-standby" with the understanding that as any >>>>>> x- prefix it's unstable and will...

...devices. If we can do all the required management of the primary/standby devices within Qemu, that is definitely a better approach without upper layer involvement. > > >>>> How about control the visibility of standby device? >>>> >>>> Thanks >>> standy the always there to guarantee no downtime. >>> >>>>> However just for testing purposes, we could add a non-stable >>>>> interface "x-standby" with the understanding that as any >>>>> x- prefix it's unstable and will be changed down...

...are about the consequences these actions have on userspace. > Therefore, I propose let?s go ?all in?: Kernel should also be responsible for hiding it?s artefacts unless customer userspace explicitly wants to view and manipulate them. Just a minor point: failover device is an artefact of kernel. Standy and primary devices are created by the hypervisor. > > > >>> > >>>> The whole point is to make most customer ignore the net-failover slaves and remain them ?hidden? in their dedicated netns. > >>> > >>> So that makes the common case easy....

On 4/30/2018 12:20 AM, Jiri Pirko wrote: > >>> Now I try to change mac of the failover master: >>> [root at test1 ~]# ip link set ens3 addr 52:54:00:b2:a7:f3 >>> RTNETLINK answers: Operation not supported >>> >>> That I did expect to work. I would expect this would change the mac of >>> the master and both standby and primary slaves.