From: FantasyCookie17 <FantasyCookie17@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libvirt is broken
Date: Fri, 24 Jul 2020 13:56:32 +0200 [thread overview]
Message-ID: <20200724115632.r9CLpgfdLtkboWt4_UcxdRonHvq7QhoMxRfNo2gelYk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23724@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
New comment by FantasyCookie17 on void-packages repository
https://github.com/void-linux/void-packages/issues/23724#issuecomment-663503374
Comment:
Well, the problem is it doesn't seem to do anything at all. My QEMU VMs that previously worked were not started either and such. So, I'd suppose connecting as a different user wouldn't work, even `virsh list` didn't. However, others on the IRC were not able to reproduce the issue, and I myself have found a solution that works for me (start QEMU VMs manually as individual Runit services), so I'm closing this for now.
next prev parent reply other threads:[~2020-07-24 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 11:25 [ISSUE] " FantasyCookie17
2020-07-22 17:42 ` abenson
2020-07-23 11:58 ` ahesford
2020-07-24 4:19 ` anjandev
2020-07-24 11:56 ` FantasyCookie17 [this message]
2020-07-24 11:56 ` [ISSUE] [CLOSED] " FantasyCookie17
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=20200724115632.r9CLpgfdLtkboWt4_UcxdRonHvq7QhoMxRfNo2gelYk@z \
--to=fantasycookie17@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).