Following on the heels of a successful KVM Forum and oVirt Workshop,
FOSDEM will be hosting a Virtualization DevRoom in February. If you've
been to FOSDEM before, you know this is about developers and code, not
products.
Presentation proposals are due by December 16th 2012.
The full details are
* Alexander Graf (ag...@suse.de) wrote:
> On 12.10.2012, at 02:28, David Gibson wrote:
> > On Fri, Oct 12, 2012 at 02:03:00AM +0200, Alexander Graf wrote:
> >> On 12.10.2012, at 00:59, David Gibson wrote:
> >>> On Thu, Oct 11, 2012 at 07:34:42AM +0530, Avik Sil wrote:
> This patch adds nvram s
For some reason I'm not seeing this on the qemu list, so here's a fwd
- Forwarded message from KVM Forum 2012 Program Committee
-
Date: Fri, 27 Jul 2012 16:31:45 -0700
From: KVM Forum 2012 Program Committee
To: k...@vger.kernel.org, libvir-l...@redhat.com, qemu-devel@nongnu.org,
* Anthony Liguori (aligu...@us.ibm.com) wrote:
> Peter Maydell writes:
> > Last year at KVM Forum, in addition to the scheduled talks we also
> > had an informal hacking session on one of the following days, since
> > we were colocated with LinuxCon NA and most people were still around
> > afterwa
* Natalia Portillo (clau...@claunia.com) wrote:
> QEMU hosted on Haiku would be interesting.
The fun of Haiku
especially when it is
hosting QEMU
* Anthony Liguori (anth...@codemonkey.ws) wrote:
> On 02/07/2012 07:18 AM, Avi Kivity wrote:
> >On 02/07/2012 02:51 PM, Anthony Liguori wrote:
> >>On 02/07/2012 06:40 AM, Avi Kivity wrote:
> >>>On 02/07/2012 02:28 PM, Anthony Liguori wrote:
>
> >It's a potential source of exploits
> >(
* Anthony Liguori (aligu...@us.ibm.com) wrote:
> 2) Two people walk through a particular piece of code and
> independently flag anything that looks like a potential security
> issue.
Auditing is always helpful, but won't ever get full coverage. qtest +
fuzz is another great way to identify proble
* Corey Bryant (cor...@linux.vnet.ibm.com) wrote:
> Count me in for step 2. A good approach may be to run a static
> analysis tool against the code, followed by a manual scan of the
> code for common vulnerabilities that static analysis can't find.
Good idea. Folks are already running things lik
* Chris Wright (chr...@redhat.com) wrote:
> * Anthony Liguori (aligu...@us.ibm.com) wrote:
> > 1. A short introduction to each of the guest agents, what guests they
> > support, and what verbs they support.
>
> I think we did this once before w/ Matahari. Can we please capt
* Peter Zijlstra (a.p.zijls...@chello.nl) wrote:
> On Wed, 2011-11-30 at 21:52 +0530, Dipankar Sarma wrote:
> >
> > Also, if at all topology changes due to migration or host kernel decisions,
> > we can make use of something like VPHN (virtual processor home node)
> > capability on Power systems t
* Anthony Liguori (aligu...@us.ibm.com) wrote:
> Hi,
>
> I'd like to propose that we discuss guest agent convergence in our next KVM
> call. I've CC'd folks from oVirt and libvirt to join the discussion.
>
> I think we should probably attempt to have some structure to the discussion.
> I would s
* Peter Zijlstra (a.p.zijls...@chello.nl) wrote:
> On Mon, 2011-11-21 at 21:30 +0530, Bharata B Rao wrote:
> >
> > In the original post of this mail thread, I proposed a way to export
> > guest RAM ranges (Guest Physical Address-GPA) and their corresponding host
> > host virtual mappings (Host Vir
* Alexander Graf (ag...@suse.de) wrote:
> On 29.10.2011, at 20:45, Bharata B Rao wrote:
> > As guests become NUMA aware, it becomes important for the guests to
> > have correct NUMA policies when they run on NUMA aware hosts.
> > Currently limited support for NUMA binding is available via libvirt
>
* Avi Kivity (a...@redhat.com) wrote:
> I would like to carry out an online code review of the memory API so that
> more people are familiar with the internals, and perhaps even to catch some
> bugs or deficiency. I'd like to use the next kvm conference call slot for
> this (Tuesday 1400 UTC) sinc
* Aaron Fabbri (aafab...@cisco.com) wrote:
> On 8/26/11 12:35 PM, "Chris Wright" wrote:
> > * Aaron Fabbri (aafab...@cisco.com) wrote:
> >> Each process will open vfio devices on the fly, and they need to be able to
> >> share IOMMU resources.
> >
>
* Aaron Fabbri (aafab...@cisco.com) wrote:
> On 8/26/11 7:07 AM, "Alexander Graf" wrote:
> > Forget the KVM case for a moment and think of a user space device driver. I
> > as
> > a user am not root. But I as a user when having access to /dev/vfioX want to
> > be able to access the device and man
* Chris Wright (chr...@sous-sol.org) wrote:
> * Stefan Hajnoczi (stefa...@linux.vnet.ibm.com) wrote:
> > @@ -199,6 +200,11 @@ static void change_process_uid(void)
> > fprintf(stderr, "Failed to setgid(%d)\n", user_pwd->pw_gid);
> > exit(
* Stefan Hajnoczi (stefa...@linux.vnet.ibm.com) wrote:
> @@ -199,6 +200,11 @@ static void change_process_uid(void)
> fprintf(stderr, "Failed to setgid(%d)\n", user_pwd->pw_gid);
> exit(1);
> }
> +if (initgroups(user_pwd->pw_name, user_pwd->pw_gid) < 0) {
>
Requesting CVE. Tools like libvirt deprivilege themselves before
launching qemu as an unprivileged user (no use of -runas), so aren't
vulnerable.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/807893
This bug is being tracked as CVE-2011-2527
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2011-2527
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/807893
Title:
qemu privilege esc
-by: Michael S. Tsirkin
Acked-by: Chris Wright
thanks,
-chris
concerns about backwards compat
- https://bugzilla.redhat.com/show_bug.cgi?id=689672
- f13 host can no longer run f14 guest after qemu update
- this particular bug is older f13 which includes patched qemu...
- could be useful to fingerprint the guest (lspci, etc)
- sounds simple enough, need so
Please send in any agenda items you are interested in covering.
thanks,
-chris
Tools for resource accounting the virtual machines.
- Luis Castro was not on the call
Status of glib tree - next steps?
- full conversion done in tree
- still targeting 0.15
status of QCFG
- code generator rewritten to be more generic and useful
- merge core infrastructure first
- to not block
* Alex Williamson (alex.william...@redhat.com) wrote:
> On Tue, 2011-04-19 at 15:26 -0700, Chris Wright wrote:
> > * Alex Williamson (alex.william...@redhat.com) wrote:
> > > On Tue, 2011-04-19 at 15:07 -0700, Chris Wright wrote:
> > > > * Alex Williamson (ale
* Alex Williamson (alex.william...@redhat.com) wrote:
> On Tue, 2011-04-19 at 15:07 -0700, Chris Wright wrote:
> > * Alex Williamson (alex.william...@redhat.com) wrote:
> > > When using VFIO to assign a device to a guest, we want to make sure
> > > the device is quies
* Alex Williamson (alex.william...@redhat.com) wrote:
> When using VFIO to assign a device to a guest, we want to make sure
> the device is quiesced on VM reset to stop all DMA within the guest
> mapped memory. Add an ioctl which just calls pci_reset_function()
> and returns whether it succeeds.
* Randy Dunlap (rdun...@xenotime.net) wrote:
> I can't find include/linux/vfio.h in linux-next or mainline git, but
> ioctls need to be documented in Documentation/ioctl/ioctl-number.txt
It is in the full patchset: https://github.com/pugs/vfio-linux-2.6
KVM Forum
- save the date is out, cfp will follow later this week
- abstracts due in 6wks, 2wk review period, notifications by end of May
Improving process to scale project
- Trivial patch bot
- Sub-maintainership
Trivial patch monkeys^Wteam
- small/simple patches posted can fall through the crac
* Anthony Liguori (anth...@codemonkey.ws) wrote:
> On 03/15/2011 09:53 AM, Chris Wright wrote:
> > QAPI
> >- c library implementation is critical to have unit tests and test
> > driven development
> > - thread safe?
> > - no shared state, no statics.
&
QAPI -- http://wiki.qemu.org/Features/QAPI
- please review!
- Anthony would like to see feedback and plans to commit in a week
(assuming agreement and no major issues in review)
- some concern about the maintainability of code generation
- but still nothing concrete on the list, need to review
ces the
> percentage of CPU time spent in qemu_get_ram_ptr from 6.3% to 2.1% in the
> profiling of a full boot.
Hopefully this is back on par with before the QLIST switchover.
> Signed-off-by: Vincent Palatin
Acked-by: Chris Wright
> ---
> exec.c |7 +--
>
QAPI merge plans
- should be 100% back compat
- qmp moved over
- hmp moved over
- 1st pass, core infrastructure (includes test framework)
- 2nd pass, command conversion
- 3rd pass, more controversial bits
- adds dependencies: glib and python
- some testing based on kvm-unit-test micro-os instance (
0.14 recap
- keeping schedule on wiki was helpful
- changelog was helpful
- testing (could even more emphasis could be improved)
- -rc cycles
- -rc2 and final release just hours
0.15
- tentative date July 1st
- qapi
- qed features
- virtagent?
- depends on whether to terminate in qemu vs exter
QAPI and QMP
- Anthony adding a new wiki page to describe all of this
- specified in formal schema using JSON
- includes documenation in javadoc-like syntax
- can generate api (possibly protocol) docs
- documenting each command and expected errors
- creates marshalling functions and C interfa
Please send in any agenda items you are interested in covering.
thanks,
-chris
Automated builds and testing
- found broken 32-bit
- luiz suggested running against maintainer trees
- daniel gollub offered to take on maintenance
- integration with kvm-autotest?
- lucas, daniel, stefan...
- testing each git commit is probably overkill and too expensive
- current autotest r
Please send in any agenda items you are interested in covering.
thanks,
-chris
KVM upstream merge: status, plans, coordination
- Jan has a git tree, consolidating
- qemu-kvm io threading is still an issue
- Anthony wants to just merge
- concerns with non-x86 arch and merge
- concerns with big-bang patch merge and following stability
- post 0.14 conversion to glib mainloop
Please send in any agenda items you are interested in covering.
thanks,
-chris
* Chris Wright (chr...@redhat.com) wrote:
> Please send in any agenda items you are interested in covering.
No agenda, this week's call is cancelled.
thanks,
-chris
Please send in any agenda items you are interested in covering.
thanks,
-chris
KVM Forum 2011
- expand the scope? yes, continue up the stack
- how long? 2 days (maybe 2 1/2 - 3 space permitting)
- where? Vancouver with LinuxCon
Spice guest agent:
- virt agent, matahari, spice agent...what is in spice agent?
- spice char device
- mouse, copy 'n paste, screen resolution ch
* Chris Wright (chr...@redhat.com) wrote:
> Please send in any agenda items you are interested in covering.
No agenda, today's call is cancelled.
Also, given people's holiday and vacation schedules, next week's call is
cancelled. Talk again after the New Year.
thanks,
-chris
Please send in any agenda items you are interested in covering.
thanks,
-chris
* Jes Sorensen (jes.soren...@redhat.com) wrote:
> Any chance you could fix your cronjob to send out the CFA a day earlier?
> 15 hrs before is a bit short notice.
Sure.
* Chris Wright (chr...@redhat.com) wrote:
> Please send in any agenda items you are interested in covering.
No agenda, today's call is cancelled.
Please send in any agenda items you are interested in covering.
thanks,
-chris
* Jes Sorensen (jes.soren...@redhat.com) wrote:
> On 12/07/10 00:51, Chris Wright wrote:
> > Please send in any agenda items you are interested in covering.
> >
> > thanks,
> > -chris
> >
>
> No agenda, no replies
>
> Call canceled I presume?
Indeed, next week, then pick up next year...
Please send in any agenda items you are interested in covering.
thanks,
-chris
* Peter Zijlstra (a.p.zijls...@chello.nl) wrote:
> On Wed, 2010-12-01 at 09:17 -0800, Chris Wright wrote:
> > Directed yield and fairness don't mix well either. You can end up
> > feeding the other tasks more time than you'll ever get back.
>
> If the directed yie
* Peter Zijlstra (a.p.zijls...@chello.nl) wrote:
> On Wed, 2010-12-01 at 21:42 +0530, Srivatsa Vaddagiri wrote:
>
> > Not if yield() remembers what timeslice was given up and adds that back when
> > thread is finally ready to run. Figure below illustrates this idea:
> >
> >
> > A0/4C0/
2011 KVM Conference
- together with LF event like LinuxCon Vancouver BC (Aug), KS Prague (Nov)
- wider audience
- include qemu (tcg)
- include libvirt
- include xen
0.14.0 release plan
- could push things out, mainly want to keep on track for
infrastructure changes (irc channel migration, g
qcow2 performance roadmap
- What can be done to achieve near-raw image format performance?
- some discussion points from Kevin on list
http://lists.nongnu.org/archive/html/qemu-devel/2010-11/msg02126.html
- please follow up on the list
- some perf numbers (latest upstream qcow2 compared wit
* Anthony Liguori (aligu...@linux.vnet.ibm.com) wrote:
> On 11/22/2010 05:04 PM, Chris Wright wrote:
> >* Anthony Liguori (aligu...@us.ibm.com) wrote:
> >>qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of
> >>teaching
> >>them to re
* Anthony Liguori (aligu...@us.ibm.com) wrote:
> qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of teaching
> them to respond to these signals, introduce monitor commands that stop and
> start
> individual vcpus.
In the past SIGSTOP has introduced time skew. Have you verified
* Juan Quintela (quint...@redhat.com) wrote:
> Please send in any agenda items you are interested in covering.
usb-ccid
Please send in any agenda items you are interested in covering.
thanks,
-chris
tils.c
> V2:
> - Introduce qemu_utimensat()
>
> Signed-off-by: Hidetoshi Seto
Looks good to me (no strong opinion on the cutils vs oslib-posix that
Jes mentioned).
Acked-by: Chris Wright
* Hidetoshi Seto (seto.hideto...@jp.fujitsu.com) wrote:
> +/*
> + * Fallback: use utimes() instead of utimensat().
> + * See commit 74bc02b2d2272dc88fb98d43e631eb154717f517 for known problem.
> + */
> +struct timeval tv[2];
> +int i;
> +
> +for (i = 0; i < 2; i++) {
> +
linux plumbers
- qemu talks, including xen folks efforts to get patches upstream
- considering virtio
- considering seabios
- even some xenner interest
- seabios presentation
- uefi
- still needs CSM support (lot of work) to be the only BIOS
- otherwise need legacy BIOS and UEFI and users
* Hidetoshi Seto (seto.hideto...@jp.fujitsu.com) wrote:
> (2010/10/14 4:11), Blue Swirl wrote:
> > On Wed, Oct 13, 2010 at 8:00 AM, Hidetoshi Seto
> > wrote:
> >> (Add CC to k...@vger)
> >>
> >> (2010/10/12 10:52), Hao, Xudong wrote:
> >>> Hi,
> >>> Currently qemu-kvm build fail on RHEL5 with gcc
Guest Agents
- need to get to guest userspace for many actions
- virtio for userspace
- host backend needs to terminate in QEMU
- portable across guest OS's
- virt-agent
- bi-directional RPC (XML-RPC just since it's easy)
- cmd: shutdown, reboot, dmesg, execute command, read/write file
- qu
* Juan Quintela (quint...@redhat.com) wrote:
> Please send in any agenda items you are interested in covering.
Guest agents
* Anthony Liguori (anth...@codemonkey.ws) wrote:
> On 10/22/2010 01:20 PM, Chris Wright wrote:
> >I'm not sure about that. That same new shiny Fedora 21 QEMU has no idea
> >what the right OS specific command to run in guest is. Granted, it's
> >not likely that &q
* Anthony Liguori (anth...@codemonkey.ws) wrote:
> On 10/22/2010 12:29 PM, Chris Wright wrote:
> >* Anthony Liguori (anth...@codemonkey.ws) wrote:
> >>The first step is just identifying what interfaces we need in a
> >>guest agent. So far, I think we can get away with
* Anthony Liguori (anth...@codemonkey.ws) wrote:
> The first step is just identifying what interfaces we need in a
> guest agent. So far, I think we can get away with a very small
> number of interfaces (mainly read/write files, execute command).
Could you elaborate here? I can't imagine you mea
* Anthony Liguori (anth...@codemonkey.ws) wrote:
> So there's no doubt in my mind that if you need a way to inventory
> physical and virtual systems, something like Matahari becomes a very
> appealing option to do that.
>
> But that's not the problem space I'm trying to tackle.
>
> An example of
* Chris Wright (chr...@redhat.com) wrote:
> We were also able to video the speakers, and will send a note when the
> videos are available.
> (and thanks again to Andrew Cathrow for making this happen)
I don't think a note went out yet. The videos are available as well.
thanks,
-chris
0.13.X -stable
- Anthony will send note to qemu-devel on this
- move 0.13.X -stable to a separate tree
- driven independently of main qemu tree
- challenge is always in the porting and testing of backported fixes
- looking for volunteers
0.14
- would like to do this before end of the year
- 0.13 f
* Juan Quintela (quint...@redhat.com) wrote:
>
> Please send in any agenda items you are interested in covering.
- 0.13.X -stable handoff
- 0.14 planning
- threadlet work
- virtfs proposals
* Andreas Färber (andreas.faer...@web.de) wrote:
> Am 04.10.2010 um 20:54 schrieb Marcelo Tosatti:
>
> I assume something went wrong with your cover letter here. It
> would've been nice to see MCE spelled out or summarized for those of
> us that don't speak x86.
It would help. The acronym is Mac
* Chris Wright (chr...@redhat.com) wrote:
> Please send in any agenda items you are interested in covering.
No agenda, call cancelled.
thanks,
-chris
Please send in any agenda items you are interested in covering.
thanks,
-chris
Please send in any agenda items you are interested in covering.
thanks,
-chris
Nested VMX
- looking for forward progress and better collaboration between the
Intel and IBM teams
- needs more review (not a new issue)
- use cases
- work todo
- merge baseline patch
- looks pretty good
- review is finding mostly small things at this point
- need some correctness v
Please send in any agenda items you are interested in covering.
thanks,
-chris
* Cam Macdonell (c...@cs.ualberta.ca) wrote:
> On Fri, Sep 17, 2010 at 2:52 PM, Cam Macdonell wrote:
> > On Fri, Sep 17, 2010 at 2:04 PM, Chris Wright wrote:
> >> * Cam Macdonell (c...@cs.ualberta.ca) wrote:
> >>> After fixing the resource_size_t return value with
&
* Cam Macdonell (c...@cs.ualberta.ca) wrote:
> After fixing the resource_size_t return value with
> pci_resource_alignment, I see one other strange behaviour only when
> using 4GB of RAM and a 2GB BAR. I haven't found any other combination
> of RAM/BAR size that triggers this bug. I am using 2.6.
0.13
- if all goes well...tomorrow
stable tree
- please look at -stable to see what is missing (bugfixes)
- esp. regressions from 0.12
- looking for dedicated stable maintainer/release manager
- pick this discussion up next week
qed/qcow2
- increase concurrency, performance
- threading vs sta
Please send in any agenda items you are interested in covering.
thanks,
-chris
es)
Yes, that's my mistake. Thanks for debugging the issue Cam.
This fixes the prototype for both pci_resource_alignment() and
pci_sriov_resource_alignment().
Patch started as debugging effort from Cam Macdonell.
Cc: Cam Macdonell
Cc: Avi Kivity
Cc: Jesse Barnes
[chrisw: add iov b
0.13 schedule
- RSN
- rc1 uploaded, tagged in git (and tag should actually be there now)
- announcement once it propagates
- 0.13.0 should be 1 week after rc1 announcement
- please check rc1 for any missing critical patches
qed
- concession that qcow2 is complicated and hard to get right
- it's mu
* Alex Williamson (alex.william...@redhat.com) wrote:
> On Tue, 2010-08-31 at 11:00 -0700, Chris Wright wrote:
> > * Alex Williamson (alex.william...@redhat.com) wrote:
> > > diff --git a/hw/virtio-net.c b/hw/virtio-net.c
> > > index 075f72d..9ef29f0 100644
> > &g
* Alex Williamson (alex.william...@redhat.com) wrote:
> diff --git a/hw/virtio-net.c b/hw/virtio-net.c
> index 075f72d..9ef29f0 100644
> --- a/hw/virtio-net.c
> +++ b/hw/virtio-net.c
> @@ -36,6 +36,7 @@ typedef struct VirtIONet
> VirtQueue *ctrl_vq;
> NICState *nic;
> QEMUTimer *tx_t
QMP/QPI
- declare what's in 0.13 supported
- means reasonable effort to avoid breaking something (deprecation is
possible)
- things that are left, shallow patch or human monitor conversion
- how to move forward?
- need to improve interfaces (no argument there)
- internal vs. external inte
* Anthony Liguori (anth...@codemonkey.ws) wrote:
> On 08/23/2010 05:30 PM, Chris Wright wrote:
> >Please send in any agenda items you are interested in covering.
>
> There are quite a few important discussions on the list but I think
> they should stay on the list right now.
Please send in any agenda items you are interested in covering.
thanks,
-chris
* Chris Wright (chr...@redhat.com) wrote:
> Please send in any agenda items you are interested in covering.
Today's call is cancelled.
Please send in any agenda items you are interested in covering.
thanks,
-chris
* Dor Laor (dl...@redhat.com) wrote:
> On 08/17/2010 12:50 AM, Chris Wright wrote:
> >KVM Forum 2010 was quite a success, many thanks to all who participated!
> >
> >For those who couldn't attend, the presentations are available online now:
> >(thanks to Andrew
KVM Forum 2010 was quite a success, many thanks to all who participated!
For those who couldn't attend, the presentations are available online now:
(thanks to Andrew Cathrow for pushing them all up)
http://www.linux-kvm.org/page/KVM_Forum_2010#Presentations
We were also able to video the speaker
* Anthony Liguori (anth...@codemonkey.ws) wrote:
> Here are the possible things we can do:
>
> 1) merge -libvirt-caps as an intermediate solution, stop caring
> about -help changes, when full caps are introduced, stop updating
> -libvirt-caps
>
> 2) don't merge -libvirt-caps, stop caring about -h
* Avi Kivity (a...@redhat.com) wrote:
> On 07/27/2010 07:29 PM, Chris Wright wrote:
> >
> >>QEMU stderr+out is already recorded in /var/lib/libvirt/qemu/$GUESTNAME.log
> >>along with the env variables and argv used to spawn it. Or did you mean
> >>provide an
* Daniel P. Berrange (berra...@redhat.com) wrote:
> On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
> > On 07/27/2010 06:28 PM, Anthony Liguori wrote:
> > >
> > >If we add docs/deprecated-features.txt, schedule removal for at least
> > >1 year in the future, and put a warning in the c
0.13
- -rc0 tagged, propagating now
- no more features, bug fix only
- although a few things, like shared memory device, are still feasible
qemu64 cpu model
- currently model 2
- this cpu simply does not exist at all in the real world
- model 13 or higher windows 32bit will enable MSI/-X support
Please send in any agenda items you are interested in covering.
thanks,
-chris
0.12.stable
- start w/ git tree + pull requests
- release process is separate from commit access
- justin will put up a tree for pull requests
- there's current backlog, what about that?
- anthony's concern with -stable is the testing (upstream tree gets more
testing than -stable)
- 0.12.5?
- p
Please send in any agenda items you are interested in covering.
thanks,
-chris
* Avi Kivity (a...@redhat.com) wrote:
> On 07/15/2010 08:17 PM, Chris Wright wrote:
> >
> >>For emulated device, it seems like we can ignore ATS completely, no?
> >Not if you want to emulate an ATS capable device ;)
>
> What I meant was that the whole request transl
1 - 100 of 171 matches
Mail list logo
