The following patch series makes it possible to run Remus on top of pvops dom0. Specifically, it uses the IFB device (included with newer kernels) for buffering outbound network traffic, instead of the old 3rd-party IMQ patch. It also cleans up some bugs in the python rtnetlink bindings, supports guests with multiple VIFs, and allocates unused IFB/IMQ devices to allow concurrent protection of multiple guests. No non-Remus code is touched by these patches. With these patches applied, the IMQ patch can be dropped from the pvops tree. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Brendan Cully
2010-May-03 18:53 UTC
[Xen-devel] [PATCH 1 of 7] Remus: python netlink fixes
Fix deprecation warning in Qdisc class under python 2.6. Fix rtattr length and padding (rta_len is unaligned). Null-terminate qdisc name in rtnl messages. Signed-off-by: Brendan Cully <brendan@cs.ubc.ca> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Brendan Cully
2010-May-03 18:53 UTC
[Xen-devel] [PATCH 2 of 7] Remus: remove obsolete code
Signed-off-by: Brendan Cully <brendan@cs.ubc.ca> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Brendan Cully
2010-May-03 18:53 UTC
[Xen-devel] [PATCH 3 of 7] Remus: move device handling into its own module
Signed-off-by: Brendan Cully <brendan@cs.ubc.ca> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Brendan Cully
2010-May-03 18:53 UTC
[Xen-devel] [PATCH 4 of 7] Remus: fix VM stringification
Signed-off-by: Brendan Cully <brendan@cs.ubc.ca> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Brendan Cully
2010-May-03 18:53 UTC
[Xen-devel] [PATCH 5 of 7] Remus: include device name in vif objects
Signed-off-by: Brendan Cully <brendan@cs.ubc.ca> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Brendan Cully
2010-May-03 18:53 UTC
[Xen-devel] [PATCH 6 of 7] Remus: add file locking and modprobe utility functions
Signed-off-by: Brendan Cully <brendan@cs.ubc.ca> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Brendan Cully
2010-May-03 18:53 UTC
[Xen-devel] [PATCH 7 of 7] Remus: use IFB for net buffer on newer kernels
IMQ does not work with ebtables on 2.6.31, and IFB is not a third-party patch. Signed-off-by: Brendan Cully <brendan@cs.ubc.ca> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Yuvraj Agarwal
2010-May-03 19:21 UTC
[Xen-devel] Measuring the amount of memory read/written (basically touched) by a domU
Hi, We want to measure the amount of memory that a domU touches while its running, and if possible even get a breakdown between memory read/written. We want to basically do these measurements for some windows domUs (XP, vista, 7) and perhaps even linux domU''s on top of XEN... Does anyone know how do I can get this information easily? Has anyone done something like this already? My test system is using XEN 4.0 + 2.6.32 pvops kernel -- (Ubuntu 9.10) Thanks! Yuvraj _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2010-May-03 19:32 UTC
Re: [Xen-devel] Measuring the amount of memory read/written (basically touched) by a domU
The live migration shadow-pagetable logic could perhaps be used for this. Live migration uses it for dirty page tracking, but you could extend it no doubt to both accessed- and dirty-page tracking, and take counts periodically. Definitely some hacking involved, however! -- Keir On 03/05/2010 20:21, "Yuvraj Agarwal" <yuvraj@cs.ucsd.edu> wrote:> Hi, > > We want to measure the amount of memory that a domU touches while its > running, and if possible even get a breakdown between memory read/written. > We want to basically do these measurements for some windows domUs (XP, > vista, 7) and perhaps even linux domU''s on top of XEN... Does anyone know > how do I can get this information easily? Has anyone done something like > this already? > > My test system is using XEN 4.0 + 2.6.32 pvops kernel -- (Ubuntu 9.10) > > Thanks! > Yuvraj > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gilberto Nunes
2010-May-03 20:05 UTC
Re: [Xen-devel] [PATCH 0 of 7] Remus: pvops dom0 support
Thanks Brendan... I can''t wait to test this patches... Regards Em Seg, 2010-05-03 às 11:53 -0700, Brendan Cully escreveu:> The following patch series makes it possible to run Remus on top of > pvops dom0. Specifically, it uses the IFB device (included with newer kernels) > for buffering outbound network traffic, instead of the old 3rd-party IMQ patch. > > It also cleans up some bugs in the python rtnetlink bindings, supports > guests with multiple VIFs, and allocates unused IFB/IMQ devices to allow > concurrent protection of multiple guests. > > No non-Remus code is touched by these patches. With these patches applied, the > IMQ patch can be dropped from the pvops tree. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-develGilberto Nunes Ferreira Suporte T.I. Selbetti Gestão de Documentos (47) 3441-6004 / (47) 8861-6672 Fax (47) 3441-6027 gilberto.nunes@selbetti.com.br _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel