I dug a little deeper now and this is what I found.
I had a deeper look at systemd service files and subsequently called
openvswitch scripts in /usr/share/openvswitch/scripts.
I don't know if its upstream or patched by DEBIAN by AFAICT it seems to me that
it is intended behaviour to keep OVS
> Use auto...On Aug 17, 2022 18:02, topro wrote:
Ok, now I sacrificed one of my affected hosts by migrating away any guests and
putting it in a place where I got access to physical keeyboard and screen, so I
have a playground for testing. I tried any combination of auto and/or
allow-ovsbr
ld I omit just on one of those two, or replace with auto? is there any
authoritative documentation where I can learn how do configure it right?
and then, this config was working up until post-"~git" versions of 2.15 showed
up.
Best regards,
topro
address 192.168.99.80
netmask 255.255.255.0
gateway 192.168.99.1
ovs_type OVSIntPort
ovs_bridge ovsbr1
ovs_options tag=99
Best regards,
topro
gateway 192.168.99.1
ovs_type OVSIntPort
ovs_bridge ovsbr1
ovs_options tag=99
Best regards,
topro
Hi Bernd,
thanks for your quick response.
> that won't happen, ceph startup is a big mix of systemd template units
> and targets these days.
So why then are ceph upstream builds of 14.2.9 for ubuntu bionic and xenial
still able to provide an init script? Please see
Do you still get these distortions on an uptodate stack?
Yes, I do, with latest setup of debian sid packages
(I'm not quite
sure why you are using this weird 800x480 resolution...)
I need to use this resolution cause its the native resolution of the screen
used in that application (see
** Tainted: PC (1025)
* Proprietary module has been loaded.
* Module from drivers/staging has been loaded.
The first voids your waranty, the later maybe also considered this way.
Please reproduce without this modules ever loaded.
Well, I expected something like that beeing the policy.
Package: linux-2.6
Version: 2.6.32-9
Severity: critical
Justification: breaks the whole system
Using this version of linux image (and previous versions of 2.6.32 from sid as
well) on lenny-i386 results in intermittent soft-lockups (see netconsole
capture below). It is not an hardware-issue as I
Could this be caused by the fact that the only self-built kernel module
'cgosdrv' being built in lenny using lenny compiler and userland while the
linux-image is taken binary from sid? At least its both gcc-4.3.x, thats what I
checked first.
--
GMX DSL: Internet, Telefon und Entertainment für
10 matches
Mail list logo
