On Tue, Aug 31, 2021 at 10:00:18PM +0300, Michael Tokarev wrote:
> 31.08.2021 18:02, dann frazier wrote:
>
> > char device redirected to /dev/pts/14 (label charserial0)
> > about to fire assert: salen=2
> > qemu-system-x86_64: ../../util/qemu-sockets.c:1352:
> > socket_sockaddr_to_address_unix:
31.08.2021 18:02, dann frazier wrote:
char device redirected to /dev/pts/14 (label charserial0)
about to fire assert: salen=2
qemu-system-x86_64: ../../util/qemu-sockets.c:1352: socket_sockaddr_to_address_unix: Assertion
`salen >= sizeof(su->sun_family) + 1 && salen <= sizeof(struct
On Tue, Aug 31, 2021 at 01:13:40AM +0300, Michael Tokarev wrote:
> dann, can you please add a printf to util/qemu-sockets.c
> before the assert() which is failing, to see what's the
> value of salen? since you can reproduce this..
> I'm still not 100% sure what the actual problem is -
> or _which_
On Tue, Aug 31, 2021 at 01:13:40AM +0300, Michael Tokarev wrote:
> dann, can you please add a printf to util/qemu-sockets.c
> before the assert() which is failing, to see what's the
> value of salen? since you can reproduce this..
> I'm still not 100% sure what the actual problem is -
> or _which_
dann, can you please add a printf to util/qemu-sockets.c
before the assert() which is failing, to see what's the
value of salen? since you can reproduce this..
I'm still not 100% sure what the actual problem is -
or _which_ problem it is in particular.
It is either one byte too large (for the
On Mon, Aug 30, 2021 at 02:38:30PM -0600, dann frazier wrote:
> On Sat, Aug 28, 2021 at 02:53:01PM +0300, Michael Tokarev wrote:
> > On 27.08.2021 23:25, dann frazier wrote:
> > > Package: qemu-system-x86
> > > Version: 1:6.1+dfsg-1
> > > Severity: normal
> > >
> > >
> > > A VM that I created
On Sat, Aug 28, 2021 at 02:53:01PM +0300, Michael Tokarev wrote:
> On 27.08.2021 23:25, dann frazier wrote:
> > Package: qemu-system-x86
> > Version: 1:6.1+dfsg-1
> > Severity: normal
> >
> >
> > A VM that I created with either virt-manager or virtinst sometime ago now
> > crashes when I attempt
Btw, which sockets are used by livbirt for qemu-monitor or qga?
May it be too long a pathname?
/mjt
Alternatively, a debugging backtrace from the failing run will be
much apprecated, -- the `bt' gdb command after installing
qemu-system-x86's dbgsym package.
Thanks!
30.08.2021 21:04, Günter Frenz wrote:
I can confirm this error, I get the same message in the logs for every
VM I try to start since the update to version 6.1
...> I removed the guest-agent channel from the VM-definition via
virt-manager, but I get the same message in the logs as with the
Hi all,
attached is the log from the test without guest-agent channel:
Cheers
Günter
--
---
Günter Frenz
Börschgasse 16a, D-51143 Köln
(h) gu...@guefz.de, gu...@freenet.de
(w) g.frenz@gso.schule.koeln
Hi all,
On Sat, 28 Aug 2021 14:53:01 +0300 Michael Tokarev
wrote:
> On 27.08.2021 23:25, dann frazier wrote:
> > Package: qemu-system-x86
> > Version: 1:6.1+dfsg-1
> > Severity: normal
> >
> >
> > A VM that I created with either virt-manager or virtinst sometime
> > ago now crashes when I
On 27.08.2021 23:25, dann frazier wrote:
Package: qemu-system-x86
Version: 1:6.1+dfsg-1
Severity: normal
A VM that I created with either virt-manager or virtinst sometime ago now
crashes when I attempt to start it under QEMU 6.1.
Lovely.
I can only guess this is due to libvirt's
Package: qemu-system-x86
Version: 1:6.1+dfsg-1
Severity: normal
A VM that I created with either virt-manager or virtinst sometime ago now
crashes when I attempt to start it under QEMU 6.1.
2021-08-27 20:12:17.236+: starting up libvirt version: 7.6.0, package: 1
(Andrea Bolognani Thu, 19
14 matches
Mail list logo
