All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>,
	"Fabio Fantoni" <fabio.fantoni@heliman.it>,
	"Wei Liu" <Wei.Liu2@citrix.com>,
	"David Vrabel" <david.vrabel@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: Xen 4.4 development update: RC0 imminent
Date: Fri, 06 Dec 2013 14:30:28 +0100	[thread overview]
Message-ID: <52A1D174.3070903@m2r.biz> (raw)
In-Reply-To: <CAFLBxZZ9e2nRhC1MQDWEJC9H1eXrxELv1c_5wiwT6cZW06mtuw@mail.gmail.com>

Il 05/12/2013 17:29, George Dunlap ha scritto:
> On Thu, Dec 5, 2013 at 4:09 PM, George Dunlap
> <George.Dunlap@eu.citrix.com> wrote:
>> This information will be mirrored on the Xen 4.4 Roadmap wiki page:
>>   http://wiki.xen.org/wiki/Xen_Roadmap/4.4
>>
>> We're nearly to the completion of the code freeze, scheduled for
>> tomorrow.  After the code freeze, only bug fixes and features marked
>> as "blockers" will be considered.  At the moment, the only feature
>> considered a blocker is experimental PVH dom0 support.
>>
>> In early RCs, most bug fixes will be accepted; but in later RCs, even
>> bug fixes may be rejected if they risk breaking more important
>> functionality than they fix.
>>
>> I don't think at this point every bug fix needs a blessing from me;
>> committers, if there are fixes which are obviously low-risk, just go
>> ahead and check them in.
>>
>> I was thinking that for some of our new features, it would be good to
>> have a blog post describing the feature and how to test it.  This
>> would both raise awareness of the feature, and hopefully get it more
>> testing before the release.  We could choose a couple to focus on for
>> each test day.
> Features which might be worth highlighting for testing in blogs:
>
> * Non-udev scripts for driver domains (non-Linux driver domains)
>   - Roger Pau Monne
>
> * PHV domU (experimental only)
>
> * Improved Spice support on libxl
>   - Fabio Fantoni

libxl: Spice vdagent support for upstream qemu (on upstream git)

Usage:
- spicevdagent=1|0 (default=0)
Enables spice vdagent. The Spice vdagent is an optional component for
enhancing user experience and performing guest-oriented management
tasks. Its features includes: client mouse mode (no need to grab mouse
by client, no mouse lag), automatic adjustment of screen resolution,
copy and paste (text and image) between client and domU. It also
requires vdagent service installed on domU o.s. to work.

- spice_clipboard_sharing=1|0 (default=0)
Enables Spice clipboard sharing (copy/paste). It requires spicevdagent
enabled.

I used it since 2 year on windows domUs without problem.
About linux hvm domUs there is a problem with virtio-serial port create 
under /dev, to have it working pci=nomsi must be added on kernel boot line.
Latest post about it below:
http://lists.xen.org/archives/html/xen-devel/2013-12/msg01059.html

---

  libxl: spice usbredirection support for upstream qemu

Awaiting upstream approval latest version here is available here:
https://github.com/Fantu/Xen/commits/rebase/m2r-next
Require also usbversion patch.

Usage: spiceusbredirection=NUMBER (default=0)

Enables spice usbredirection. Creates NUMBER usbredirection channels
for redirection of up to 4 usb devices from spice client to domU's qemu.
It requires an usb controller and if not defined will automatically adds
an usb2 controller.

I used it since 2 year on hvm domUs (windows and linux) without problem, 
used mainly with usb2 controller.
In the latest tests made with  xen 4.4 and qemu 1.6 it is working with 
both usb 1,2,3 controllers.
It is also working even with new usb passthrough (from dom0) hotplug by 
George Dunlap patches.


>
> * Event channel scalability
>   - David Vrabel
>
> * pvgrub2 checked into grub upstream (external)
>   - Vladmir Servinenko
>
> * Guest EFI booting (tianocore)
>   - Wei Liu
>
> * kexec -- is this worth testing?
>   - David Vrabel
>
> * Disk: indirect descriptors (in 3.11)
>   - ?
>
> Are people willing to step up and write a brief description of what
> the feature is, as well as a quick guide for how to test it?
>
>   -George
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2013-12-06 13:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 16:09 Xen 4.4 development update: RC0 imminent George Dunlap
2013-12-05 16:29 ` George Dunlap
2013-12-05 16:34   ` Wei Liu
2013-12-05 16:39     ` George Dunlap
2013-12-05 16:48       ` Wei Liu
2013-12-05 16:59         ` Ian Campbell
2013-12-05 17:06           ` Wei Liu
2013-12-05 17:16             ` Ian Campbell
2013-12-05 17:34               ` Wei Liu
2013-12-05 17:53                 ` George Dunlap
2013-12-05 18:03                   ` Wei Liu
2013-12-06  9:27                     ` Ian Campbell
2013-12-06 10:51                       ` Wei Liu
2013-12-05 16:39   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-05 16:41     ` George Dunlap
2013-12-05 16:42   ` Roger Pau Monné
2013-12-05 16:51     ` George Dunlap
2013-12-05 17:01       ` Lars Kurth
2013-12-05 17:04         ` George Dunlap
2013-12-05 20:06           ` Russell Pavlicek
2013-12-05 23:54             ` Sander Eikelenboom
2013-12-06  9:39             ` Lars Kurth
2013-12-06 12:14             ` George Dunlap
2013-12-05 16:59   ` David Vrabel
2013-12-05 17:05     ` George Dunlap
2013-12-05 17:40       ` Dario Faggioli
2013-12-05 17:07     ` George Dunlap
2013-12-05 17:01   ` Olaf Hering
2013-12-05 17:06     ` David Vrabel
2013-12-05 17:32   ` Dario Faggioli
2013-12-06 13:30   ` Fabio Fantoni [this message]
2013-12-05 16:34 ` Andrew Cooper
2013-12-06  9:07   ` Jan Beulich
2013-12-06 13:07     ` George Dunlap
2013-12-06 14:58       ` Jan Beulich
2013-12-05 16:54 ` George Dunlap
2013-12-16 10:50   ` Lars Kurth

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=52A1D174.3070903@m2r.biz \
    --to=fabio.fantoni@m2r.biz \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Wei.Liu2@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=fabio.fantoni@heliman.it \
    --cc=phcoder@gmail.com \
    --cc=roger.pau@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 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.