a restore
set it to "null" instead. This has the same affect on both upstream
QEMU and qemu-xen-traditional.
Signed-off-by: Simon Waterman
---
tools/libxl/libxl_dm.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libx
Process xl.cfg file setting for PV device model version.
Valid values are qemu-xen and qemu-xen-traditional.
Signed-off-by: Simon Waterman
---
tools/xl/xl_parse.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/tools/xl/xl_parse.c b/tools/xl/xl_parse.c
index 856a304
This patch adds support for choosing upstream QEMU as the PV QEMU
backend for an IOEMU stubdom instead of qemu-xen-traditional.
The motivation is to expose QEMU features only available in upstream
like VNC auth options.
It adds a new xl.cfg file parameter named device_model_pv_version taking
the s
Add new domain build setting recording the chosen version of PV
Qemu backend for an IOEMU stubdom.
Signed-off-by: Simon Waterman
---
tools/libxl/libxl_types.idl | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl
index 2204425..16ddeaf
On 16/05/17 14:28, Ian Jackson wrote:
George Dunlap writes ("Re: [PATCH RFC 0/6] qemu-xen-trad: sasl: add SASL support to
VNC"):
On 16/05/17 14:16, Ian Jackson wrote:
Simon: What is stopping you moving to a modern version of qemu ?
I think from his previous query, it was the fact that there
This change adds calls to the SASL API to negotiate SASL auth and
includes SASL encode/decode into read and write flows if the SASL
mechanism is providing SSF.
The code is taken from upstream with minor adjustments for
compatibility with qemu-xen-traditional.
Signed-off-by: Simon Waterman
This change adjusts vnc.c for compatibility with the API defined
in vnc.h.
Signed-off-by: Simon Waterman
---
vnc.c | 212 +-
1 file changed, 27 insertions(+), 185 deletions(-)
diff --git a/vnc.c b/vnc.c
index 0e61197..728efec
Add the SASL auth API to hook into vnc.c. Taken from upstream
with minor changes to remove ACL support, which isn't in
qemu-xen-traditional yet.
Signed-off-by: Simon Waterman
---
vnc-auth-sasl.h | 67 +
1 file changed, 67 inser
This change adds build support for the SASL integration,
disabled by default.
Signed-off-by: Simon Waterman
---
Makefile.target | 6 ++
configure | 34 ++
2 files changed, 40 insertions(+)
diff --git a/Makefile.target b/Makefile.target
index 3c3db2b
Taken almost directly from upstream QEMU with minor changes:
1. Replace g_free etc. with standard equivalents
2. Remove ACL support, which is not in qemu-xen-traditional yet.
Signed-off-by: Simon Waterman
---
vnc-auth-sasl.c | 613
1 file
This patch series back-ports SASL authentication from
upstream QEMU to the VNC server in qemu-xen-traditional.
It enables authentication to the VNC console of a domain
to be controlled using any SASL mechanism when using an
IOEMU stubdom.
SASL can be used with or without X509 certificates.
The op
Expose minimum VNC API to support SASL auth. This is mainly the
VncState structure and a subset of the API funcs.
The layout of the file is modelled on the upstream QEMU vnc.h.
Signed-off-by: Simon Waterman
---
vnc.h | 231 +++---
1
Hi,
I read that only bug fixes are being accepted for qemu-xen-traditional.
I'd quite like to see SASL
support for VNC in qemu-xen-traditional so that it is available when
using IOEMU stub-domains.
I've got a patch that back-ports this support from upstream QEMU but as
it can't be considere
Hi,
We're hitting the kernel BUG below in one of our VMs running on Xen 4.4 and
Linux kernel 3.13.0. We use the xl toolstack and are using PCI pass-through
to pass network cards and a disk controller. It happens on a variety of our
hardware but not all servers and it seems to be related to the e
14 matches
Mail list logo
