Github messages for voidlinux
 help / color / mirror / Atom feed
From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: VirtualBox 6.1.36 does not start VMs
Date: Thu, 12 Jan 2023 00:33:51 +0100	[thread overview]
Message-ID: <20230111233351.HXvMJQnZXZT7RIGX7TuqkTeTH1ibO9IELyCyfVlkxmw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38967@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 636 bytes --]

New comment by ar-jan on void-packages repository

https://github.com/void-linux/void-packages/issues/38967#issuecomment-1379615847

Comment:
I have the same problem on 7.0.4. Machines do start and run, but cannot be shut down properly, only way is to kill the process.

Segfaults in `dmesg` similar to above (`EMT-0[16682]: segfault at 0 ip 00007f68f5c4db7f sp 00007f68d24f8868 error 4 in libc.so.6[7f68f5b7d000+f7000] likely on CPU 3 (core 4, socket 0)`), and cannot enable the vboxservice:

    sudo ln -s /etc/sv/vboxservice /var/service/
    sudo sv start vboxservice
    timeout: down: vboxservice: 1s, normally up, want up

  parent reply	other threads:[~2023-01-11 23:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 12:25 [ISSUE] " gtryujb
2022-08-29 13:18 ` Duncaen
2022-08-29 13:59 ` gtryujb
2022-08-31  9:51 ` rapha8l
2022-09-11  9:22 ` egorenar
2022-09-11  9:23 ` egorenar
2022-10-16 15:25 ` nezos
2022-10-16 16:52 ` gtryujb
2022-10-17  7:43 ` rapha8l
2023-01-11 23:33 ` ar-jan
2023-01-11 23:33 ` ar-jan [this message]
2023-01-16 15:07 ` [ISSUE] [CLOSED] " gtryujb
2023-01-16 15:07 ` gtryujb
2023-01-31 14:14 ` imiric
2023-02-01 11:41 ` ar-jan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230111233351.HXvMJQnZXZT7RIGX7TuqkTeTH1ibO9IELyCyfVlkxmw@z \
    --to=ar-jan@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).