Re: [DNG] Problems with KVM server after updates (possibly linux-image is culprit) -- cannot start any guests.

[Thomas Besser]

Am 11.01.2018 um 00:25 schrieb Andrew McGlashan:
> On 11/01/18 08:10, Andrew McGlashan wrote:
>> I'm getting errors when trying to start guests after a restart with new
>> kernel.
>>
>> qemu-system-x86_64:
>> /build/qemu-CeGdkI/qemu-2.8+dfsg/target-i386/kvm.c:1805: kvm_put_msrs:
>> Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
>> 2018-01-10 20:29:51.073+: shutting down
>>
>> < ii  linux-image-3.16.0-4-amd64   3.16.43-2+deb8u5
>> amd64    Linux 3.16 for 64-bit PCs
>> ---
>>> ii  linux-image-3.16.0-4-amd64   3.16.51-3   
>> amd64    Linux 3.16 for 64-bit PCs
>>
>>
>> I don't think any other updates could have been the cause
> 
> Okay, well I tried to fix this with a different kernel, available, but
> not installed?
> 
> linux-image-3.16.0-5-amd64   3.16.51-3+deb8u1

Cannot confirm your problem.

Just upgraded one of the KVM server host machines to
linux-image-3.16.0-5-amd643.16.51-3+deb8u1

After that starting of virtual machines work like before (qemu-kvm
1:2.1+dfsg-12+deb8u6).

Regards
Thomas
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Problems with KVM server after updates (possibly linux-image is culprit) -- cannot start any guests.

[Andrew McGlashan]

Hi,

On 11/01/18 08:10, Andrew McGlashan wrote:
> Hi,
>
> I'm getting errors when trying to start guests after a restart with new
> kernel.
>
>
> qemu-system-x86_64:
> /build/qemu-CeGdkI/qemu-2.8+dfsg/target-i386/kvm.c:1805: kvm_put_msrs:
> Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
> 2018-01-10 20:29:51.073+: shutting down
>
>
> < ii  linux-image-3.16.0-4-amd64   3.16.43-2+deb8u5
> amd64    Linux 3.16 for 64-bit PCs
> ---
>> ii  linux-image-3.16.0-4-amd64   3.16.51-3   
> amd64    Linux 3.16 for 64-bit PCs
>
>
> I don't think any other updates could have been the cause

Okay, well I tried to fix this with a different kernel, available, but
not installed?

linux-image-3.16.0-5-amd64   3.16.51-3+deb8u1

That didn't work, so I looked in my /var/cache/apt/archives and foudn a
4.9 kernel.

I installed that and I can now start all my guests

# dpkg-query -l|grep linux-image
ii  linux-image-3.16.0-4-amd64   3.16.51-3   
amd64    Linux 3.16 for 64-bit PCs
ii  linux-image-3.16.0-5-amd64   3.16.51-3+deb8u1
amd64    Linux 3.16 for 64-bit PCs
ii  linux-image-4.9.0-0.bpo.4-amd64  4.9.65-3+deb9u1~bpo8+1  
amd64    Linux 4.9 for 64-bit PCs


The 4.9 kernel was there by some mis-configuration previously (with the
Devuan project).  I've done aptitude update and safe-upgrade -V ... but
the /older/ 4.9 kernel didn't have any updates.

Right now, I am /reasonably/ happy becuase he guests are running, but
whatever went wrong is serious and I'm sure others will see issues, so
if we an fix it properly, that would be great.

Thanks AndrewM



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Problems with KVM server after updates (possibly linux-image is culprit) -- cannot start any guests.

[Andrew McGlashan]

Hi,

I'm getting errors when trying to start guests after a restart with new
kernel.


qemu-system-x86_64:
/build/qemu-CeGdkI/qemu-2.8+dfsg/target-i386/kvm.c:1805: kvm_put_msrs:
Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
2018-01-10 20:29:51.073+: shutting down


< ii  linux-image-3.16.0-4-amd64   3.16.43-2+deb8u5
amd64    Linux 3.16 for 64-bit PCs
---
> ii  linux-image-3.16.0-4-amd64   3.16.51-3   
amd64    Linux 3.16 for 64-bit PCs


I don't think any other updates could have been the cause


Any ideas?

Thanks and Kind Regards
AndrewM



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Virtualbox?

[lpb+devuan]

So I can't run devuan ascii as a virtualbox guest with the guest utils?

On 01/10/2018 02:08 PM, Hleb Valoshka wrote:
> On 1/10/18, lpb+dev...@kandl.houston.tx.us
>  wrote:
>> I am unable to use jessie's virtualbox-guest-dkms in Devuan ascii
>> virtulabox guest linux sessions. When attempting to build
>> virtualbox-guest-dkms, I get the following. Perhaps, have GCC options
>> changed?
>>
>> DKMS make.log for vboxguest-4.3.36 for kernel 4.9.0-5-amd64 (x86_64)
>> Tue Jan  9 21:53:16 CST 2018
> 
> 
> More probably vb 4.3.36 doesn't support Linux 4.9.0.
> 

-- 
ıɐq  ıƃınl
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Virtualbox?

[Hleb Valoshka]

On 1/10/18, lpb+dev...@kandl.houston.tx.us
 wrote:
> I am unable to use jessie's virtualbox-guest-dkms in Devuan ascii
> virtulabox guest linux sessions. When attempting to build
> virtualbox-guest-dkms, I get the following. Perhaps, have GCC options
> changed?
>
> DKMS make.log for vboxguest-4.3.36 for kernel 4.9.0-5-amd64 (x86_64)
> Tue Jan  9 21:53:16 CST 2018


More probably vb 4.3.36 doesn't support Linux 4.9.0.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] d1h with LANG=de_DE@UTF-8 fails

[Hleb Valoshka]

On 1/10/18, Andreas Messer  wrote:
> xxx@xxx:~/Devuan/elogind$ d1h prepare unstable
> Auf Branch suites/experimental
> Ihr Branch ist auf dem selben Stand wie 'origin/suites/experimental'.
> nichts zu committen, Arbeitsverzeichnis unverändert
> There are uncommitted changes or untracked files present.
> Please commit your changes or ignore untracked files
> xxx@xxx:~/Devuan/elogind$ LANG=C d1h prepare unstable
> On branch suites/experimental
> Your branch is up-to-date with 'origin/suites/experimental'.
> nothing to commit, working tree clean
> [suites/unstable d6328942d] creating suite suites/unstable
>  1 file changed, 1 insertion(+), 2 deletions(-)
> [=  suite "suites/experimental" ready =]
> Switched to branch 'suites/experimental'
> Your branch is up-to-date with 'origin/suites/experimental'.

d1h is just a shell script, so you can try to run it as "/bin/sh -x
/usr/bin/d1h ..." to see what happens.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Meltdown and linux kernel KPTI patch

[viverna]

il devuanizzato KatolaZ  il 09-01-18 18:54:58 ha scritto:
> Just to confirm that a patched kernel for jessie is available in
> jessie-security, as reported at the URL above.
> 
> HND
> 
> KatolaZ
Thank you.

-- 
viverna
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] d1h with LANG=de_DE@UTF-8 fails

[Andreas Messer]

Hi,

just came accross the following:

xxx@xxx:~/Devuan/elogind$ d1h prepare unstable
Auf Branch suites/experimental
Ihr Branch ist auf dem selben Stand wie 'origin/suites/experimental'.
nichts zu committen, Arbeitsverzeichnis unverändert
There are uncommitted changes or untracked files present.
Please commit your changes or ignore untracked files
xxx@xxx:~/Devuan/elogind$ LANG=C d1h prepare unstable
On branch suites/experimental
Your branch is up-to-date with 'origin/suites/experimental'.
nothing to commit, working tree clean
[suites/unstable d6328942d] creating suite suites/unstable
 1 file changed, 1 insertion(+), 2 deletions(-)
[=  suite "suites/experimental" ready =]
Switched to branch 'suites/experimental'
Your branch is up-to-date with 'origin/suites/experimental'.


-- 
gnuPG keyid: 8C2BAF51
fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51


signature.asc
Description: PGP signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Virtualbox?

[lpb+devuan]

I am unable to use jessie's virtualbox-guest-dkms in Devuan ascii
virtulabox guest linux sessions. When attempting to build
virtualbox-guest-dkms, I get the following. Perhaps, have GCC options
changed?

DKMS make.log for vboxguest-4.3.36 for kernel 4.9.0-5-amd64 (x86_64)
Tue Jan  9 21:53:16 CST 2018
make: Entering directory '/usr/src/linux-headers-4.9.0-5-amd64'
  LD  /var/lib/dkms/vboxguest/4.3.36/build/built-in.o
  LD  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/built-in.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/VBoxGuest-linux.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/VBoxGuest.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/VBoxGuest2.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/GenericRequest.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/HGCMInternal.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/Init.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/PhysHeap.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/SysHlp.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/VMMDev.o
  CC [M]  /var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/alloc-r0drv.o
  CC [M]
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/initterm-r0drv.o
  CC [M]
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/memobj-r0drv.o
  CC [M]
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/mpnotification-r0drv.o
  CC [M]
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/powernotification-r0drv.o
  CC [M]
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/alloc-r0drv-linux.o
  CC [M]
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/assert-r0drv-linux.o
  CC [M]
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/initterm-r0drv-linux.o
  CC [M]
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.o
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:
In function ‘rtR0MemObjNativeFree’:
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:581:21:
error: implicit declaration of function ‘page_cache_release’
[-Werror=implicit-function-declaration]
 page_cache_release(pMemLnx->apPages[iPage]);
 ^~
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:
In function ‘rtR0MemObjNativeLockUser’:
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1032:29:
warning: passing argument 1 of ‘get_user_pages’ makes integer from
pointer without a cast [-Wint-conversion]
 rc = get_user_pages(pTask,  /* Task for fault
accounting. */
 ^
In file included from
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/the-linux-kernel.h:88:0,
 from
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:31:
/usr/src/linux-headers-4.9.0-5-common/include/linux/mm.h:1303:6: note:
expected ‘long unsigned int’ but argument is of type ‘struct task_struct *’
 long get_user_pages(unsigned long start, unsigned long nr_pages,
  ^~
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1033:29:
warning: passing argument 2 of ‘get_user_pages’ makes integer from
pointer without a cast [-Wint-conversion]
 pTask->mm,  /* Whose pages. */
 ^
In file included from
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/the-linux-kernel.h:88:0,
 from
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:31:
/usr/src/linux-headers-4.9.0-5-common/include/linux/mm.h:1303:6: note:
expected ‘long unsigned int’ but argument is of type ‘struct mm_struct *’
 long get_user_pages(unsigned long start, unsigned long nr_pages,
  ^~
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1035:29:
warning: passing argument 4 of ‘get_user_pages’ makes pointer from
integer without a cast [-Wint-conversion]
 cPages, /* How many pages. */
 ^~
In file included from
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/the-linux-kernel.h:88:0,
 from
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:31:
/usr/src/linux-headers-4.9.0-5-common/include/linux/mm.h:1303:6: note:
expected ‘struct page **’ but argument is of type ‘int’
 long get_user_pages(unsigned long start, unsigned long nr_pages,
  ^~
/var/lib/dkms/vboxguest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1036:29:
warning: passing argument 5 of ‘get_user_pages’ makes pointer from
integer without a cast [-Wint-conversion]
 fWrite, /* Write to memory. */
 ^~
In file included from

Re: [DNG] Should I, or should I not, make a Devuan VimOutliner package?

[Jaromil]

On Wed, 10 Jan 2018, Erik Christiansen wrote:

> If a foreign distro has forked your original, then in our distro it
> seems entirely reasonable for you as originator to restore the
> original.  If the foreign fork failed to identify itself as such,
> then it is not your problem or ours when substituting the original
> reclaims the original name. It is up to the fork to find a way to
> differentiate itself. If our community wants to keep both, then I
> propose that the debian package be renamed vimoutliner-debfork or
> similar.

I agree with all of the above. Plus its also part of Devuan's generic
mission to re-establish a constructive and respectful relationship
with upstream software developers, a long-standing problem Debian has.

ciao


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Should I, or should I not, make a Devuan VimOutliner package?

[Olaf Meeuwissen]

Hi,

Steve Litt writes:

> Hi all,
>
> BACKSTORY...
>
> I'm the *originator* of VimOutliner, an outline processor that uses the
> Vim engine. VimOutliner's top priority was authoring speed. That
> priority drove most VimOutliner keyboard commands to begin with a
> double comma (,,), which is both extremely easy to hit from typing home
> position, and very unlikely to happen within written text. I published
> VimOutliner 0.13 June 1 2001.
>
> Several other people used it, liked it, and improved it far beyond my
> capabilities. Several Linux distros acquired VimOutliner packages.
> Unfortunately, the Debian VimOutliner package manager insisted on using
> double backslash (//) instead of double comma (,,) as the first two

You mean double slash, right?  Double backslash would be \\ (and way too
Windows for my taste ;-).

On my Japanese keyboard these are right next to one another, two places
to the right of the comma.  Of the three, the comma would be easier to
type.

What's the Debian maintainer's rationale for changing the command
prefix?

> characters of commands. The double backslash is slower, and more
> important, it's a key that appears in different places on different
> keyboards. Use of the double backslash represents a degradation of
> VimOutliner's top priority: Authoring speed.
>
> I'm thinking of making the Devuan VimOutliner package use double comma.
> I'd take the Debian package and replace all appropriate double
> backslashes with double commas.

Just a thought, but would it be possible to make the command prefix
configurable upstream?  Then anyone could set it in a system-wide and/or
per user config file and everyone could use whatever is most convenient
for them.  Upstream can use ,, as the hard-coded default and the Debian
maintainer can simply plonk a system-wide configuration file in place.

Since everyone seems to be donating ;-) that was my two yen.
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] packages or pkgmaster?

[KatolaZ]

On Tue, Jan 09, 2018 at 03:12:08PM -0500, Hendrik Boom wrote:

[cut]

> 
> Those instructions say to use
> 
> deb http://packages.devuan.org/devuan/ experimental main
> 
> Elsewhere I've been told to use pkgmaster.devuan.org/merged instead.
> 
> WHich is correct in this case?
> 

Hendrik, you are mixing two things there. The first one is the mirror
to use. The original instructions point to packages.devuan.org, but
the latest implementation of amprolla, which merges every few minutes,
is available at pkgmaster.devuan.org. It is recommended to use the
latter, especially if you are on ascii (but you can use it also on
jessie). We will update the documentation in due course.

Then, Devuan archives have two "branches", namely "/merged" and
"/devuan". The former is the branch that includes the merged
Debian/Devuan repos, while the latter has only packages specific to
Devuan. In particular, the "experimental" suite is under "/devuan"
(i.e., using "pkgmaster.devuan.org/merged experimental" would result
in apt being unable to find the corresponding Release file).

In a word: if you really want to have experimental at the moment you
should use:

  deb http://pkgmaster.devuan.org/devuan experimental main

HTH

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] packages or pkgmaster?

[Jaromil]

On Tue, 09 Jan 2018, Hendrik Boom wrote:
> >   https://dev1galaxy.org/viewtopic.php?id=549
> 
> Those instructions say to use
> 
> deb http://packages.devuan.org/devuan/ experimental main
> 
> Elsewhere I've been told to use pkgmaster.devuan.org/merged instead.
> 
> WHich is correct in this case?

Let's say we are in a sort of transition period.

we have a new round-robin setup that is just ready for restricted
testing (details on devuan-dev) which includes all functioning package
mirrors so far and a bot to check if all hosts are reachable, have
valid paths and Release file signatures (again thanks to Katolaz for
all the work put into this).

Give us a few weeks and this will be announced along with the ASCII
beta images and then documentation should be updated to use it (its a
new vhost)

ciao

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Should I, or should I not, make a Devuan VimOutliner package?

[Fungal-net]

UTC Time: January 10, 2018 12:21 AM

> From: dva...@internode.on.net
> To: dng@lists.dyne.org
>
> On 09.01.18 10:52, Steve Litt wrote:
>
>> I'm thinking of making the Devuan VimOutliner package use double comma.
>> I'd take the Debian package and replace all appropriate double
>> backslashes with double commas.
>
> Steve,
> If a foreign distro has forked your original, then in our distro it
> seems entirely reasonable for you as originator to restore the original.
> If the foreign fork failed to identify itself as such, then it is not
> your problem or ours when substituting the original reclaims the
> original name. It is up to the fork to find a way to differentiate
> itself. If our community wants to keep both, then I propose that the
> debian package be renamed vimoutliner-debfork or similar.
>
> That would seem to keep the ducks in a row, without the distasteful
> problem of a fork masquerading as the original. It would also avoid
> future list traffic asking "Why is the devuan VimOutliner package
> backslash-borked??"
>
> Erik

I am with Erik on this one.  The fork should be renamed the one of the 
"originator" should retain its "original" name.

FunGus___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng