From: "Alex Braunegg" <alex.braunegg@gmail.com>
To: 'Paul Durrant' <Paul.Durrant@citrix.com>, xen-devel@lists.xenproject.org
Subject: Re: unable to start VM after xen upgrade to 4.8.2
Date: Sat, 2 Dec 2017 08:03:55 +1100 [thread overview]
Message-ID: <5a21c3c1.8bc8620a.3c244.329b@mx.google.com> (raw)
In-Reply-To: <710ed25b7ec0405a983e8d2993cbf776@AMSPEX02CL03.citrite.net>
Hi Paul,
> That's QEMU failing to start which is, most likely, an incompatibility
between libxl and the QEMU command line. With any luck you should have a log
> file called /var/log/xen/qemu-dm-<guest name>.log which in which QEMU
should say what it is unhappy about.
On checking the suggested log there is the following entry:
qemu-system-i386: -vnc 0.0.0.0:0,websocket,x509=/etc/pki/xen,password,to=99:
Failed to start VNC server: address resolution failed for 0.0.0.0:on:
Servname not supported for ai_socktype
As I use websockets to present the display via a HTML5 canvas it appears
that I have been hit with a QEMU regression due to the bundled version
(2.7.0) of QEMU with xen 4.8.2:
https://github.com/qemu/qemu/commit/1b1aeb5828c978af2ec4478e552884004f23c470
#diff-446cee24164cdeb527aa48c13210c9c2
Applying that fix resolves the guest failing to start, however websockets is
still not fully functional unlike when using 4.6.6. Will have to downgrade /
upgrade the bundled version of QEMU locally.
Thanks for the advice,
Alex
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2017-12-01 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 2:00 unable to start VM after xen upgrade to 4.8.2 Alex Braunegg
2017-12-01 9:40 ` Paul Durrant
2017-12-01 21:03 ` Alex Braunegg [this message]
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=5a21c3c1.8bc8620a.3c244.329b@mx.google.com \
--to=alex.braunegg@gmail.com \
--cc=Paul.Durrant@citrix.com \
--cc=xen-devel@lists.xenproject.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).