From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Fehlig Subject: Re: libxl fixes/improvements for libvirt Date: Mon, 31 Mar 2014 11:14:56 -0600 Message-ID: <5339A290.6020107__24508.4136062816$1396286243$gmane$org@suse.com> References: <1395939304-9017-1-git-send-email-stefan.bader@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1395939304-9017-1-git-send-email-stefan.bader@canonical.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefan Bader , libvir-list@redhat.com, xen-devel@lists.xen.org Cc: Ian Campbell List-Id: xen-devel@lists.xenproject.org On 03/27/2014 10:55 AM, Stefan Bader wrote: > Here several changes which improve the handling of Xen for me: Thanks for the improvements Stefan. I'm currently on bereavement leave and will look at these patches when returning, unless someone beats me to it. Regards, Jim > > * 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 > > .