Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] libvirt is broken
@ 2020-07-22 11:25 FantasyCookie17
  2020-07-22 17:42 ` abenson
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: FantasyCookie17 @ 2020-07-22 11:25 UTC (permalink / raw)
  To: ml

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

New issue by FantasyCookie17 on void-packages repository

https://github.com/void-linux/void-packages/issues/23724

Description:
### System

* xuname:  
  `Void 5.7.9_1 x86_64-musl AuthenticAMD notuptodate rFFF`
* package:  
  `libvirt-6.5.0_1`

### Expected behavior
Connecting to `qemu:///system` or `qemu+ssh://root@hostname/system` (with `openbsd-netcat` installed) with `virsh` or `virt-manager` should work. QEMU VMs should be booted.

### Actual behavior
Connecting with any of the above hangs indefinitely. QEMU VMs are not started.

### Steps to reproduce the behavior
1. Install libvirt and virsh or virt-manager. If connecting via SSH, also install openbsd-netcat.
2. Enable and start libvirtd, virtlogd and virtlockd.
3. Try to connect.



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: libvirt is broken
  2020-07-22 11:25 [ISSUE] libvirt is broken FantasyCookie17
@ 2020-07-22 17:42 ` abenson
  2020-07-23 11:58 ` ahesford
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: abenson @ 2020-07-22 17:42 UTC (permalink / raw)
  To: ml

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

New comment by abenson on void-packages repository

https://github.com/void-linux/void-packages/issues/23724#issuecomment-662591581

Comment:
Is your user in the `libvirt` group?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: libvirt is broken
  2020-07-22 11:25 [ISSUE] libvirt is broken FantasyCookie17
  2020-07-22 17:42 ` abenson
@ 2020-07-23 11:58 ` ahesford
  2020-07-24  4:19 ` anjandev
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: ahesford @ 2020-07-23 11:58 UTC (permalink / raw)
  To: ml

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

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/23724#issuecomment-662965630

Comment:
Connecting to `root@host` should avoid any `libvirt` group issues, but is also a bad idea. Have you tried connecting to `qemu+ssh://user@host/system` for some user in the `libvirt` group?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: libvirt is broken
  2020-07-22 11:25 [ISSUE] libvirt is broken FantasyCookie17
  2020-07-22 17:42 ` abenson
  2020-07-23 11:58 ` ahesford
@ 2020-07-24  4:19 ` anjandev
  2020-07-24 11:56 ` [ISSUE] [CLOSED] " FantasyCookie17
  2020-07-24 11:56 ` FantasyCookie17
  4 siblings, 0 replies; 6+ messages in thread
From: anjandev @ 2020-07-24  4:19 UTC (permalink / raw)
  To: ml

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

New comment by anjandev on void-packages repository

https://github.com/void-linux/void-packages/issues/23724#issuecomment-663339870

Comment:
https://github.com/void-linux/void-docs/pull/217/files

Read line 205 onwards on this patch for instructions to fixing permissions.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: libvirt is broken
  2020-07-22 11:25 [ISSUE] libvirt is broken FantasyCookie17
                   ` (3 preceding siblings ...)
  2020-07-24 11:56 ` [ISSUE] [CLOSED] " FantasyCookie17
@ 2020-07-24 11:56 ` FantasyCookie17
  4 siblings, 0 replies; 6+ messages in thread
From: FantasyCookie17 @ 2020-07-24 11:56 UTC (permalink / raw)
  To: ml

[-- 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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [ISSUE] [CLOSED] libvirt is broken
  2020-07-22 11:25 [ISSUE] libvirt is broken FantasyCookie17
                   ` (2 preceding siblings ...)
  2020-07-24  4:19 ` anjandev
@ 2020-07-24 11:56 ` FantasyCookie17
  2020-07-24 11:56 ` FantasyCookie17
  4 siblings, 0 replies; 6+ messages in thread
From: FantasyCookie17 @ 2020-07-24 11:56 UTC (permalink / raw)
  To: ml

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

Closed issue by FantasyCookie17 on void-packages repository

https://github.com/void-linux/void-packages/issues/23724

Description:
### System

* xuname:  
  `Void 5.7.9_1 x86_64-musl AuthenticAMD notuptodate rFFF`
* package:  
  `libvirt-6.5.0_1`

### Expected behavior
Connecting to `qemu:///system` or `qemu+ssh://root@hostname/system` (with `openbsd-netcat` installed) with `virsh` or `virt-manager` should work. QEMU VMs should be booted.

### Actual behavior
Connecting with any of the above hangs indefinitely. QEMU VMs are not started.

### Steps to reproduce the behavior
1. Install libvirt and, optionally, virt-manager. If connecting via SSH, also install openbsd-netcat.
2. Enable and start libvirtd, virtlogd and virtlockd.
3. Try to connect.



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2020-07-24 11:56 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-22 11:25 [ISSUE] libvirt is broken FantasyCookie17
2020-07-22 17:42 ` abenson
2020-07-23 11:58 ` ahesford
2020-07-24  4:19 ` anjandev
2020-07-24 11:56 ` [ISSUE] [CLOSED] " FantasyCookie17
2020-07-24 11:56 ` FantasyCookie17

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).