All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Bader <stefan.bader@canonical.com>
To: libvir-list@redhat.com, xen-devel@lists.xen.org
Cc: Jim Fehlig <jfehlig@suse.com>, Ian Campbell <ian.campbell@citrix.com>
Subject: libxl fixes/improvements for libvirt
Date: Thu, 27 Mar 2014 17:55:01 +0100	[thread overview]
Message-ID: <1395939304-9017-1-git-send-email-stefan.bader__47705.5144416683$1395939405$gmane$org@canonical.com> (raw)

Here several changes which improve the handling of Xen for me:

* 0001-libxl-Use-id-from-virDomainObj-inside-the-driver.patch
  This is a re-send as I initially submitted that as a reply to some
  discussion. Starting from the visibly broken libxlDomainGetInfo when
  creating or rebooting a guest with virt-manager, I replaced all usage
  of dom->id with the more stable vm->def->id.
* 0002-libxl-Set-disk-format-for-empty-cdrom-device.patch
  Fixes start of a guest after ejecting the iso image from a virtual
  CDROM drive (again using virt-manager).
* 0003-libxl-Implement-basic-video-device-selection.patch
  Should fix the occasional disagreement about the used VNC port and
  adds the ability to select the standard VGA graphics from Xen.
  VRAM size seemed to work with that. Only for Cirrus, while the qemu
  command-line looks good, ones seems to end up with 32M.

Note to people on the Xen list: I wonder whether libxenlight internally
should somehow should fix up the situation where a caller sets up the
video devices in the vfbs list but does not sync that with the information
in the build info. Question probably is what the semantics should be.

-Stefan

             reply	other threads:[~2014-03-27 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 16:55 Stefan Bader [this message]
     [not found] <1395939304-9017-1-git-send-email-stefan.bader@canonical.com>
2014-03-31 17:14 ` libxl fixes/improvements for libvirt Jim Fehlig

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='1395939304-9017-1-git-send-email-stefan.bader__47705.5144416683$1395939405$gmane$org@canonical.com' \
    --to=stefan.bader@canonical.com \
    --cc=ian.campbell@citrix.com \
    --cc=jfehlig@suse.com \
    --cc=libvir-list@redhat.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.