https://wiki.xenproject.org/api.php?action=feedcontributions&user=Andyhhp&feedformat=atomXen - User contributions [en]2024-03-28T14:20:26ZUser contributionsMediaWiki 1.31.3https://wiki.xenproject.org/index.php?title=Archived/Hackathon/April2016&diff=16479Archived/Hackathon/April20162016-03-15T23:18:40Z<p>Andyhhp: /* Topics */</p>
<hr />
<div>{{InfoLeft|Registration his now open}}<br />
<br />
== When and Where ? ==<br />
<br />
=== ARM Cambridge, UK, April 18-19 ===<br />
ARM will be hosting this years Xen Project Hackathon on April 18-19, 2016 at their Cambridge Headquarters. <br />
<br />
Address:<br />
: ARM Ltd.<br />
: 110 Fulbourn Road<br />
: Cambridge<br />
: CB1 9NJ<br />
: United Kingdom<br />
<br />
'''[https://www.google.co.uk/maps/search/ARM+Ltd.+110+Fulbourn+Road+Cambridge+GB-CB1+9NJ/@52.185975,0.189242,17z/data=!3m1!4b1 Check out the event location on the map]'''<br />
<br />
=== Schedule & Rooms ===<br />
We will start at 9AM and finish at 5PM each day. There will also be an evening social event on April 18th. More details regarding the schedule and the social event will follow.<br />
<br />
== Logistics ==<br />
<br />
=== Getting to Cambridge, UK ===<br />
<br />
Cambridge, UK is located approximately 45 minutes North of London by train, with easy access by bus or train to [St. Pancras International - Eurostar (45m rail), London Stansted Airport (40m rail), London Heathrow Airport (LHR - 2h rail), London Gatwick Airport (LGW - 2h rail), Manchester Airport (MIA - 4h rail), London Luton Airport (1h25m bus). European attendees may consider '''Eurostar''' or '''Stansted Airport''' preferred routes due to short transit time to Cambridge and lower prices. <br />
<br />
Visitors from the US or elsewhere will likely need to travel into one of London's major international airports, such as Heathrow (LHR) or Gatwick (LGW). With the exception of Luton Airport, rail offers a more convenient but more expensive route to Cambridge than bus, but will require using a combination of Heathrow Express/Tube and Rail (cost is approx. GBP 50-60). There are also several car service companies which arrange transfers from London Heathrow to Cambridge. The trip takes about 1.5-2 hours depending on the time of day.<br />
* [http://www.onlineairportcars.com/heathrow/car-service-heathrow-to-cambridge-cabs-lhr-airports-transfers-heathrow-and-other-major-airports.php Online Airport Cars] (GBP 94 one way)<br />
* [http://www.taxicambridge.co.uk/ Taxi Cambridge] (GBP 95 one way)<br />
* [http://www.airporttaxis-uk.co.uk/Transfer/Cambridge-LHR/Heathrow/ Airport Taxis UK] (GBP 103 one way)<br />
* [http://www.cambridgeconnections.co.uk/airport-transfers Cambridge Connections] (quote required)<br />
* Note that Ueber is also available and comes in at around GBP 110-150 one way<br />
Relevant public transport information (from London Heathrow)<br />
* The best way to go from London Heathrow to Cambridge by rail is via ''Heathrow Express'' (cyan), then London Underground via the ''Hammersmith and City line'' (pink) or ''Circle Line'' (yellow) to Kings Cross. The following map outlines [https://thetrainline.files.wordpress.com/2015/07/lhr_train_map.gif train connections from London Heathrow].<br />
* Once you get to Kings Cross the [https://tomhalltravel.files.wordpress.com/2009/12/king-cross-upgrade-map2.gif station map] shows you where to arrive and where the platforms are. Usually trains to Cambridge go from platforms 9-11, but not always. Make sure you check the departure boards in the ticketing hall to get the right platform: <br />
* Note that there are slow and fast trains to Cambridge from Kings Cross (fast trains usually leave at 14 and 44 minutes past the hour - the fast train takes 52 minutes, the slow trains 1h 24 to 1h 34 minutes). You want to take a fast train.<br />
* The Heathrow Express ticket desk can sell you a through ticket from Heathrow to Cambridge which includes the tube<br />
* You can book individual train tickets in advance via the following sites: there are no options to book a through ticket - you have to get tickets separately. If you book timed tickets, you have to catch a specific train.<br />
** Self-print tickets via [http://www.mytrainticket.co.uk/self-print-tickets] (does not include tickets for Heathrow Express or tube tickets)<br />
** You can buy [https://www.heathrowexpress.com Heathrow Express tickets on-line], or from Heathrow Express staff before you get to the baggage hall at Heathrow or at the Heathrow Express entrance<br />
** Payment options for Tube (London Underground) tickets are listed [https://tfl.gov.uk/campaign/ways-to-pay?cid=waystopay here] - the easiest way to pay is via a [https://tfl.gov.uk/fares-and-payments/contactless?intcmp=8257 contactless credit or debit card]<br />
<br />
=== Recommended Hotel Options ===<br />
We are identifying suitable hotel options as we speak. We will select a mixture of hotels in the city centre and near the railway station. <br />
<br />
<br><br />
{| class="prettytable"<br />
|-<br />
! Hotel / Booking URL <br />
! Address<br />
! Review<br />
! Distance to venue<br />
! Location<br />
|-<br />
! [http://www3.hilton.com/en/hotels/united-kingdom/hilton-cambridge-city-centre-STNHCHI/index.html Hilton Cambridge City Centre]<br />
| Downing St<br>Cambridge<br>CB2 3DT<br />
| [http://www.tripadvisor.co.uk/Hotel_Review-g186225-d189358-Reviews-Hilton_Cambridge_City_Centre-Cambridge_Cambridgeshire_England.html 4.5]<br />
| 3.7 miles (or 15-25 minutes by taxi) <br />
| City centre<br />
|-<br />
![https://www.travelodge.co.uk/hotels/255/Cambridge-Central-hotel Travelodge Hotel Cambridge Central] <br />
| Cambridge Leisure Park<br>Clifton Way<br> Cambridge<br>CB1 7DY<br />
|[http://www.tripadvisor.co.uk/Hotel_Review-g186225-d446834-Reviews-Travelodge_Cambridge_Central_Hotel-Cambridge_Cambridgeshire_England.html 3.5]<br />
|2.7 miles (or 10 to 20 minutes by taxi)<br />
|Railway station<br />
|-<br />
![http://www.sorrentohotelcambridge.co.uk/ Sorrento Hotel]<br />
|196 Cherry Hinton Rd<br>Cambridge<br>CB1 7AN<br />
|[http://www.tripadvisor.co.uk/Hotel_Review-g186225-d446834-Reviews-Travelodge_Cambridge_Central_Hotel-Cambridge_Cambridgeshire_England.html 3]<br />
|2.2 miles (or 10 to 15 minutes by taxi, <br>12-15 minutes by [https://www.cambridgeshire.gov.uk/site/custom_scripts/bus_timetable_by_service.aspx citi 3 bus] which goes every 10 minutes)<br />
|Railway station<br />
|-<br />
![http://www.expresscambridge.co.uk/ Holiday Inn Express Cambridge]<br />
|15-17 Coldhams Park<br>Norman Way<br>Cambridge<br>CB1 3LH<br />
|[http://www.tripadvisor.co.uk/Hotel_Review-g186225-d291602-Reviews-Holiday_Inn_Express_Cambridge-Cambridge_Cambridgeshire_England.html 4]<br />
|1.5 miles (or 10 to 15 minutes by taxi)<br />
|Suburb<br />
|}<br />
<br><br />
<br />
<br />
=== Transport in Cambridge ===<br />
The following taxi companies operate in Cambridge<br />
* [http://www.panthertaxis.co.uk/ Panther Taxis] (+44 (0)1223 715715)<br />
* [http://www.taxicambridge.co.uk/ Taxi Cambridge] (+44 (0) 1223 929 026)<br />
* Note that Uber does '''not''' operate in Cambridge and that it is nearly impossible to hail taxis on the street<br />
* Cambridge is slightly too large to be convenient to walk everywhere, but small enough to be ideal for a bicycle. If you have a car, please be aware that you will not be able to drive in the city centre. If you feel adventurous, you could hire a bicycle. [http://stationcycles.co.uk/ Station Cycles] (confusingly located in the middle of town, nowhere near the station) rents bicycles at a reasonable rate. Please book with them directly. You can probably just turn up and get a bike but it's better to send them an email to make sure that they're not going to be surprised when 30 people turn up at once.<br />
<br><br />
<br />
=== Visa Invitation Letters ===<br />
If you require an invitation, please send an e-mail to community dot manager at xenproject dot org. You should make sure that you have at least 2 weeks to organise a visa. Please provide the following information. You may want to send this as GPG encrypted mail, in which case you should send the mail to lars dot kurth dot xen at gmail dot com. You can look up my public GPG key from the hkps://hkps.pool.sks-keyservers.net keyserver.<br />
<br />
==== Personal Information ====<br />
* Name (needs to be your full name as written in your passport, including middle names)<br />
* Gender<br />
* Date of birth<br />
* Nationality<br />
* Passport number<br />
* Full name of the company which you work for<br />
* Job title<br />
<br />
== Topics to Discuss, Code, Work on, ... at the Hackathon ==<br />
=== Instructions ===<br />
{{ambox<br />
|type=notice<br />
|text=Please use the {{Tl|Project}} template to add any discussions that you want to have at the Hackathon. Feel free to comment on discussions using {{Tl|Comment}} and your support for a specific topic - i.e. you indicate that you want to participate in this topic - by using {{Tl|Vote}} or {{Tl|VoteNo}} in the Review section of the project. To do this, use the Review section of the {{Tl|Project}}.<br />
<br />
The code will look like<br />
<br />
<pre><br />
{{project=Name<br />
...<br />
|Review=<br />
{{comment|~~~~:}} Some text/comment<br />
{{vote|~~~~}} Some explanation<br />
}}<br />
</pre><br />
Make sure you read the template documentation of {{Tl|Project}}, {{Tl|Comment}}, {{Tl|Vote}} and {{Tl|VoteNo}}. Mark unused fields of {{Tl|Project}} with {{Tl|N/A}}.<br />
}}<br />
<br />
=== Topics ===<br />
<br />
Please add topics you want to discuss in this section as described above<br />
<br />
{{project<br />
|Project=Project Governance<br />
|Date=Feb 26 2016<br />
|Contact=Lars Kurth<br />
|Desc=<br />
We do have a number of concrete issues regarding governance that we need to discuss<br />
* Project Leadership : will we go for a committee or project lead based approach, if the former how does it look<br />
* Review roles in the community : clarify boundaries and responsibilities<br />
* Decision making <br />
** Clarify Lazy Consensus and scope it (when does, does it not apply)<br />
** Clarify voting: scope, how +2 ... -2 and do votes have to be unanimous<br />
* Add some criteria for roles lapsing (right now, people retain their status forever, unless they formally step down)<br />
* Etc<br />
|Review=<br />
{{comment| Feel free to make suggestions here}}<br><br />
{{vote|And whether you intend to attend}}<br />
}}<br />
<br />
{{project<br />
|Project=Security<br />
|Date=Jan 19 2016<br />
|Contact=Konrad Rzeszutek Wilk<br />
|Desc=<br />
Discuss our multiple approaches to security and further goals:<br />
* Deprivileged of QEMU - and the leftover TODO (PCI passthrough?)<br />
* xSplice for patching hypervisor with XSA updates (should xen-security send out instructions on how to build binaries)? Make sure that the patches function nicely with xSplice tool?<br />
* Instruction parser in Xen hypervisor? Existing approaches to depriv it - other means to lower the performance impact?<br />
* Spell out limits of security support for qemu-xen and/or make QEMU an external dependency to Xen (also see [https://www.mail-archive.com/xen-devel@lists.xen.org/msg58158.html]<br />
* Hypervisor defence in depth<br />
* Other security related improvements<br />
|Review=<br />
{{comment| Feel free to make suggestions here}}<br><br />
{{vote|And whether you intend to attend}}<br />
}}<br />
<br />
<br />
{{project<br />
|Project=Lost+found Patches<br />
|Date=Feb 15 2016<br />
|Contact=Konrad Rzeszutek Wilk<br />
|Desc=<br />
Discuss "lost patches" that have floated around and haven't been addressed:<br />
* TLB flushing on grant table unmmap?<br />
* Memory scrubbing workers?<br />
* Various "worker" functions we want to run from cpu_idle<br />
* Other distros patches?<br />
* per-cpu tasklets to lessen the tasklet spinlock contention<br />
<br />
Some of these had been posted 2 years ago and while the authors are still<br />
around they have a huge TODO list that. Brainstorm:<br />
<br />
* Can we put all of those in a 'outstanding' patch queue?<br />
* Could we put some of those on an GSOC or Outreachy internships?<br />
* Other ideas?<br />
<br />
|Review=<br />
{{comment| Feel free to make suggestions here}}<br><br />
{{vote|And whether you intend to attend}}<br />
}}<br />
<br />
== I want to attend ==<br />
<br />
=== Request an Invitation ===<br />
<br />
In previous years we have requested for attendees to fill out a form and request an invitation. This was overly complicated, so we will revert back to a simpler approach. Please add your name to the [[#Request|list below]]. <br />
* If you are a maintainer or otherwise a core member of the community, just add yourself to the [[#Confirmed_attendees|Confirmed Attendees]] section stating your name and <br />
* If you are '''not''' a maintainer add yourself the [[#Request|Request invitation]]. If your '''email address is not known''' in the Xen Community, please also add the name of your employer and send your e-mail address to ''community dot manager at xenproject dot org'' using "Request for Hackathon 2016 Invite" as subject line. This is important, such that we can e-mail more information to you. We will monitor this page and confirm whether we have space for you to attend.<br />
<br />
You can use ...<br />
<pre><br />
* Name, Org<br />
</pre><br />
Or<br />
<pre><br />
{{Invite|Name|Org|IRC handle}}<br />
</pre><br />
Or to be able to co-ordinate travel and find people staying in the same place as you, ...<br />
<pre><br />
{{Invite|Name|Org|IRC handle|arrival date|leave date|lodging}}<br />
</pre><br />
<br />
'''IMPORTANT:''' The cut-off date for registrations is '''April 8th'''.<br />
<br />
Please read the text in the warning box below: it contains more detailed instructions.<br />
<br><br />
{{WarningLeft|To edit this page and thus to '''Request an Invitation''', you '''need to be added to the wiki's editors group'''. To be added to that group: <br />
* If you do not have a wiki account, please create one by using [[Special:UserLogin|this link]]. Write down your '''user name''' (we cannot look up user names from e-mail addresses) <br />
* Please [http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html fill out this form] (note: this form does not work in China) <br />
* If you cannot access the form, please send an email to community.manager at xenproject.org requesting that you need wiki access.}}<br />
{{Anchor|Request}}<br />
<br />
=== Request invitation ===<br />
<br />
Add your name and org here:<br />
<br />
<!-- You can use one of the following syntax patterns<br />
* Name, Org<br />
{{Invite|Name|Org|IRC handle}}<br />
{{Invite|Name|Org|IRC handle|arrival date|leave date|lodging}}<br />
<br />
--><br />
<br />
{{Invite|Anshul Makkar| Citrix|anshul_m| N/A| N/A| home}}<br />
{{Invite|Jennifer Herbert| Citrix|xenifer| - | - | home}}<br />
<br />
=== Confirmed attendees ===<br />
{{InfoLeft|Important note:<br />
* We have a maximum of 40 spaces<br />
* The cut-off for registration is '''April the 8th''', as we need to organise security passes, etc.<br />
}}<br />
<br />
If you are a maintainer or otherwise known in the Xen Project community please add your name below,<br />
<br />
<!-- You can use one of the following syntax patterns<br />
* Name, Org<br />
{{Invite|Name|Org|IRC handle}}<br />
{{Invite|Name|Org|IRC handle|arrival date|leave date|lodging}}<br />
<br />
--> <br />
<br />
{{Invite|Lars Kurth|Citrix|lars_kurth|April 17|April 20|TBD}}<br />
{{Invite|David Vrabel|Citrix|dvrabel|-|-|Home}}<br />
{{Invite|Paul Durrant|Citrix|xadimgnik|April 17|April 20|Home}}<br />
{{Invite|Andrew Cooper|Citrix|andyhhp|-|-|Home}}<br />
{{Invite|Rich Persaud|OpenXT, BAE Systems|-|April 17|April 19|TBD}}<br />
{{Invite|Stefano Stabellini|Citrix|stefanos|April 17|April 19|TBD}}<br />
{{Invite|Julian Chesterfield|OnApp|-|April 17|April 19|TBD}}<br />
{{Invite|Michail Flouris|OnApp|-|April 17|April 19|TBD}}<br />
{{Invite|Anastassios Nanos|OnApp|-|April 17|April 19|TBD}}<br />
{{Invite|Anthony PERARD|Citrix|anthonyper}}<br />
{{Invite|Dario Faggioli|Citrix|dariof|-|-|TBD}}<br />
{{Invite|Wei Liu|Citrix|-|-|-|TBD}}<br />
{{Invite|Roger Pau Monné|Citrix|royger|-|-|TBD}}<br />
{{Invite|Jan Beulich|SUSE|jbeulich|April 17|April 20|Sorrento}}<br />
{{Invite|Max FERGER|KOSTAL Automotive Electrical Systems|-|April 18|April 19|Cambridge Central Travelodge}}<br />
{{Invite|Boris Ostrovsky|Oracle|ostr|April 17|April 20|TBD}}<br />
{{Invite|Daniel Kiper|Oracle|dkiper|April 17|April 20|TBD}}<br />
{{Invite|Joao Martins|Oracle|-|April 17|April 20|TBD}}<br />
{{Invite|Konrad Rzeszutek Wilk|Oracle|konrad|April 17|April 20|TBD}}<br />
{{Invite|Olivier Lambert|Vates|Plam|April 17|April 20|TBD}}<br />
{{Invite|Julien Fontanet|Vates|julien_f|April 17|April 20|TBD}}<br />
{{Invite|Ross Lagerwall|Citrix|rosslagerwall|-|-|Home}}<br />
{{Invite|Iurii Konovalenko|GlobalLogic|iurii.konovalenko|April 17|April 19|TBD}}<br />
{{Invite|Juergen Gross|SUSE|juergen_gross|April 17|April 20|Sorrento}}<br />
{{Invite|Han Yongfei|Onets|-|April 17|April 20|TBD}}<br />
{{Invite|Ross Philipson|Assured Information Security|rphilipson}}<br />
{{Invite|Nick Hardiman|IM|-|April 17|April 19| Cambridge Central Travelodge}}<br />
{{Invite|Doug Goldstein|Star Lab|cardoe|April 17th|April 20th|TBD}}<br />
{{Invite|Ian Jackson|Citrix|cardoe|'''April 19th'''|'''April 19th'''|Home}}<br />
{{Invite|Julien Grall|ARM|julieng}}<br />
{{Invite|Steve Capper|ARM|SteveCapper}}<br />
{{Invite|Andre Przywara|ARM|apritzel}}<br />
<br />
[[Category:Project]]<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/Hackathon/April2016&diff=16209Archived/Hackathon/April20162016-01-13T16:56:06Z<p>Andyhhp: /* Confirmed attendees */</p>
<hr />
<div>{{InfoLeft|Registration his now open}}<br />
<br />
== When and Where ? ==<br />
<br />
=== ARM Cambridge, UK, April 18-19 ===<br />
ARM will be hosting this years Xen Project Hackathon on April 18-19, 2016 at their Cambridge Headquarters. <br />
<br />
Address:<br />
: ARM Ltd.<br />
: 110 Fulbourn Road<br />
: Cambridge<br />
: CB1 9NJ<br />
: United Kingdom<br />
<br />
'''[https://www.google.co.uk/maps/search/ARM+Ltd.+110+Fulbourn+Road+Cambridge+GB-CB1+9NJ/@52.185975,0.189242,17z/data=!3m1!4b1 Check out the event location on the map]'''<br />
<br />
=== Schedule & Rooms ===<br />
We will start at 9AM and finish at 5PM each day. There will also be an evening social event on April 18th. More details regarding the schedule and the social event will follow.<br />
<br />
== Logistics ==<br />
<br />
=== Getting to Cambridge, UK ===<br />
<br />
Cambridge, UK is located approximately 45 minutes North of London by train, with easy access by bus or train to [St. Pancras International - Eurostar (45m rail), London Stansted Airport (40m rail), London Heathrow Airport (LHR - 2h rail), London Gatwick Airport (LGW - 2h rail), Manchester Airport (MIA - 4h rail), London Luton Airport (1h25m bus). European attendees may consider '''Eurostar''' or '''Stansted Airport''' preferred routes due to short transit time to Cambridge and lower prices. <br />
<br />
Visitors from the US or elsewhere will likely need to travel into one of London's major international airports, such as Heathrow (LHR) or Gatwick (LGW). With the exception of Luton Airport, rail offers a more convenient but more expensive route to Cambridge than bus, but will require using a combination of Heathrow Express/Tube and Rail (cost is approx. GBP 50-60). There are also several car service companies which arrange transfers from London Heathrow to Cambridge. The trip takes about 1.5-2 hours depending on the time of day.<br />
* [http://www.onlineairportcars.com/heathrow/car-service-heathrow-to-cambridge-cabs-lhr-airports-transfers-heathrow-and-other-major-airports.php Online Airport Cars] (GBP 94 one way)<br />
* [http://www.taxicambridge.co.uk/ Taxi Cambridge] (GBP 95 one way)<br />
* [http://www.airporttaxis-uk.co.uk/Transfer/Cambridge-LHR/Heathrow/ Airport Taxis UK] (GBP 103 one way)<br />
* [http://www.cambridgeconnections.co.uk/airport-transfers Cambridge Connections] (quote required)<br />
* Note that Ueber is also available and comes in at around GBP 110-150 one way<br />
<br />
=== Recommended Hotel Options ===<br />
We are identifying suitable hotel options as we speak. We will select a mixture of hotels in the city centre and near the railway station. <br />
<br />
Transport in Cambridge: the following taxi companies operate in Cambridge<br />
* [http://www.panthertaxis.co.uk/ Panther Taxis] (+44 (0)1223 715715)<br />
* [http://www.taxicambridge.co.uk/ Taxi Cambridge] (+44 (0) 1223 929 026)<br />
* Note that Uber does '''not''' operate in Cambridge and that it is nearly impossible to hail taxis on the street<br />
<br />
<br><br />
{| class="prettytable"<br />
|-<br />
! Hotel / Booking URL <br />
! Address<br />
! Review<br />
! Distance to venue<br />
! Location<br />
|-<br />
! [http://www3.hilton.com/en/hotels/united-kingdom/hilton-cambridge-city-centre-STNHCHI/index.html Hilton Cambridge City Centre]<br />
| Downing St<br>Cambridge<br>CB2 3DT<br />
| [http://www.tripadvisor.co.uk/Hotel_Review-g186225-d189358-Reviews-Hilton_Cambridge_City_Centre-Cambridge_Cambridgeshire_England.html 4.5]<br />
| 3.7 miles (or 15-25 minutes by taxi) <br />
| City centre<br />
|-<br />
![https://www.travelodge.co.uk/hotels/255/Cambridge-Central-hotel Travelodge Hotel Cambridge Central] <br />
| Cambridge Leisure Park<br>Clifton Way<br> Cambridge<br>CB1 7DY<br />
|[http://www.tripadvisor.co.uk/Hotel_Review-g186225-d446834-Reviews-Travelodge_Cambridge_Central_Hotel-Cambridge_Cambridgeshire_England.html 3.5]<br />
|2.7 miles (or 10 to 20 minutes by taxi)<br />
|Railway station<br />
|-<br />
![http://www.sorrentohotelcambridge.co.uk/ Sorrento Hotel]<br />
|196 Cherry Hinton Rd<br>Cambridge<br>CB1 7AN<br />
|[http://www.tripadvisor.co.uk/Hotel_Review-g186225-d446834-Reviews-Travelodge_Cambridge_Central_Hotel-Cambridge_Cambridgeshire_England.html 3]<br />
|2.2 miles (or 10 to 15 minutes by taxi, <br>12-15 minutes by [https://www.cambridgeshire.gov.uk/site/custom_scripts/bus_timetable_by_service.aspx citi 3 bus] which goes every 10 minutes)<br />
|Railway station<br />
|-<br />
![http://www.expresscambridge.co.uk/ Holiday Inn Express Cambridge]<br />
|15-17 Coldhams Park<br>Norman Way<br>Cambridge<br>CB1 3LH<br />
|[http://www.tripadvisor.co.uk/Hotel_Review-g186225-d291602-Reviews-Holiday_Inn_Express_Cambridge-Cambridge_Cambridgeshire_England.html 4]<br />
|1.5 miles (or 10 to 15 minutes by taxi)<br />
|Suburb<br />
|}<br />
<br><br />
<br />
=== Visa Invitation Letters ===<br />
If you require an invitation, please send an e-mail to community dot manager at xenproject dot org. You should make sure that you have at least 2 weeks to organise a visa. Please provide the following information. You may want to send this as GPG encrypted mail, in which case you should send the mail to lars dot kurth dot xen at gmail dot com. You can look up my public GPG key from the hkps://hkps.pool.sks-keyservers.net keyserver.<br />
<br />
==== Personal Information ====<br />
* Name (needs to be your full name as written in your passport, including middle names)<br />
* Gender<br />
* Date of birth<br />
* Nationality<br />
* Passport number<br />
* Full name of the company which you work for<br />
* Job title<br />
<br />
== Topics to Discuss, Code, Work on, ... at the Hackathon ==<br />
=== Instructions ===<br />
{{ambox<br />
|type=notice<br />
|text=Please use the {{Tl|Project}} template to add any discussions that you want to have at the Hackathon. Feel free to comment on discussions using {{Tl|Comment}} and your support for a specific topic - i.e. you indicate that you want to participate in this topic - by using {{Tl|Vote}} or {{Tl|VoteNo}} in the Review section of the project. To do this, use the Review section of the {{Tl|Project}}.<br />
<br />
The code will look like<br />
<br />
<pre><br />
{{project=Name<br />
...<br />
|Review=<br />
{{comment|~~~~:}} Some text/comment<br />
{{vote|~~~~}} Some explanation<br />
}}<br />
</pre><br />
Make sure you read the template documentation of {{Tl|Project}}, {{Tl|Comment}}, {{Tl|Vote}} and {{Tl|VoteNo}}. Mark unused fields of {{Tl|Project}} with {{Tl|N/A}}.<br />
}}<br />
<br />
=== Topics ===<br />
<br />
Please add topics you want to discuss in this section as described above<br />
<br />
== I want to attend ==<br />
<br />
=== Request an Invitation ===<br />
<br />
In previous years we have requested for attendees to fill out a form and request an invitation. This was overly complicated, so we will revert back to a simpler approach. Please add your name to the [[#Request|list below]]. <br />
* If you are a maintainer or otherwise a core member of the community, just add yourself to the [[#Confirmed_attendees|Confirmed Attendees]] section stating your name and <br />
* If you are '''not''' a maintainer add yourself the [[#Request|Request invitation]]. If your '''email address is not known''' in the Xen Community, please also add the name of your employer and send your e-mail address to ''community dot manager at xenproject dot org'' using "Request for Hackathon 2016 Invite" as subject line. This is important, such that we can e-mail more information to you. We will monitor this page and confirm whether we have space for you to attend.<br />
<br />
You can use ...<br />
<pre><br />
* Name, Org<br />
</pre><br />
Or<br />
<pre><br />
{{Invite|Name|Org|IRC handle}}<br />
</pre><br />
Or to be able to co-ordinate travel and find people staying in the same place as you, ...<br />
<pre><br />
{{Invite|Name|Org|IRC handle|arrival date|leave date|lodging}}<br />
</pre><br />
<br />
'''IMPORTANT:''' The cut-off date for registrations is '''April 8th'''.<br />
<br />
Please read the text in the warning box below: it contains more detailed instructions.<br />
<br><br />
{{WarningLeft|To edit this page and thus to '''Request an Invitation''', you '''need to be added to the wiki's editors group'''. To be added to that group: <br />
* If you do not have a wiki account, please create one by using [[Special:UserLogin|this link]]. Write down your '''user name''' (we cannot look up user names from e-mail addresses) <br />
* Please [http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html fill out this form] (note: this form does not work in China) <br />
* If you cannot access the form, please send an email to community.manager at xenproject.org requesting that you need wiki access.}}<br />
{{Anchor|Request}}<br />
<br />
=== Request invitation ===<br />
<br />
Add your name and org here:<br />
<br />
<!-- You can use one of the following syntax patterns<br />
* Name, Org<br />
{{Invite|Name|Org|IRC handle}}<br />
{{Invite|Name|Org|IRC handle|arrival date|leave date|lodging}}<br />
<br />
--><br />
<br />
=== Confirmed attendees ===<br />
{{InfoLeft|Important note:<br />
* We have a maximum of 40 spaces<br />
* The cut-off for registration is '''April the 8th''', as we need to organise security passes, etc.<br />
}}<br />
<br />
If you are a maintainer or otherwise known in the Xen Project community please add your name below,<br />
<br />
<!-- You can use one of the following syntax patterns<br />
* Name, Org<br />
{{Invite|Name|Org|IRC handle}}<br />
{{Invite|Name|Org|IRC handle|arrival date|leave date|lodging}}<br />
<br />
--> <br />
<br />
{{Invite|Lars Kurth|Citrix|lars_kurth|April 17|April 20|TBD}}<br />
{{Invite|David Vrabel|Citrix|dvrabel|-|-|home}}<br />
{{Invite|Paul Durrant|Citrix|xadimgnik|April 17|April 20|Home}}<br />
{{Invite|Andrew Cooper|Citrix|andyhhp|-|-|home}}<br />
<br />
[[Category:Project]]<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/Developer_Meeting/Aug2015&diff=15205Archived/Developer Meeting/Aug20152015-08-04T09:51:31Z<p>Andyhhp: /* Confirmed Attendees */</p>
<hr />
<div>{{InfoLeft|Please add yourself to the list if you want to attend and add a topic you want to cover. Please make sure you get wiki edit rights (see below).}}<br />
{{WarningLeft|The Xen Wiki has been subject to sustained severe spam attacks in the last few months. To solve this and keep the wiki usable for everyone, we had to lock down the wiki and create an editors group. CAPTCHAs dp not appear to work against the spam attacks we have seen. Until we have a solution in place, please [http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html fill out this form] and we will add you to the editors group.}}<br />
<br />
== When and Where ? ==<br />
August 19, 2015 from 10:00-13:30<br><br><br />
<br />
Exact room to be announced<br><br />
Sheraton Seattle Hotel<br><br />
1400 6th Ave<br><br />
Seattle, WA<br><br />
USA<br />
<br />
Lunch and break will be provided<br />
<br />
== Topics to Discuss at the Developer Meeting ==<br />
=== Instructions ===<br />
Please reply to this [http://lists.xenproject.org/archives/html/xen-devel/2015-06/msg03138.html thread] or by update this wiki page<br />
<br />
=== Topics ===<br />
<br />
* PVH Next Steps (Konrad)<br />
* XSplice Design - Loose Ends and Decisions (Konrad)<br />
<br />
== Confirmed Attendees ==<br />
{{InfoLeft|Please Add yourself to the list. Note that we have space for '''30 people''' only.}}<br />
* Lars Kurth, Citrix <br />
* Dario Faggioli, Citrix<br />
* Jürgen Groß, SUSE<br />
* Julien Grall, Citrix<br />
* Andrew Cooper, Citrix<br />
<br />
[[Category:Project]]<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/Xen_Development_Projects&diff=15159Archived/Xen Development Projects2015-07-16T11:19:49Z<p>Andyhhp: </p>
<hr />
<div>__TOC__<br />
<br />
This page lists various Xen related development projects that can be picked up by anyone! If you're interesting in hacking Xen this is the place to start! Ready for the challenge?<br />
<br />
To work on a project:<br />
<br />
* Find a project that looks interesting (or a bug if you want to start with something simple)<br />
* Send an email to xen-devel mailinglist and let us know you started working on a specific project.<br />
* Post your ideas, questions, RFCs to xen-devel sooner than later so you can get comments and feedback.<br />
* Send patches to xen-devel early for review so you can get feedback and be sure you're going into correct direction.<br />
* Your work should be based on xen-unstable development tree, if it's Xen and/or tools related. After your patch has been merged to xen-unstable it can be backported to stable branches (Xen 4.2, Xen 4.1, etc).<br />
* Your kernel related patches should be based on upstream kernel.org Linux git tree (latest version).<br />
<br />
xen-devel mailinglist subscription and archives: http://lists.xensource.com/mailman/listinfo/xen-devel<br />
<br />
Before to submit patches, please look at [[Submitting Xen Patches]] wiki page.<br />
<br />
If you have new ideas, suggestions or development plans let us know and we'll update this list!<br />
<br />
== List of projects ==<br />
=== Domain support ===<br />
{{project<br />
|Project=Upstreaming Xen PVUSB drivers to mainline Linux kernel<br />
|Date=01/08/2012<br />
|Contact=Konrad Rzeszutek Wilk <konrad.wilk@oracle.com><br />
|Difficulty=Hard<br />
|GSoC=No, unless Konrad believes these can be done.<br />
|Desc=<br />
PVUSB drivers needs to be upstreamed yet. Necessary operations may include:<br />
* Upstream PVUSB usbfront frontend driver (for domU).<br />
* Upstream PVUSB usbback backend driver (for dom0).<br />
* Send to various related upstream mailinglists for review, comments.<br />
* Fix any upcoming issues.<br />
* Repeat until merged to upstream Linux kernel git tree.<br />
* http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=shortlog;h=refs/heads/devel/xen-usb.v1.1<br />
* More info: http://wiki.xen.org/xenwiki/XenUSBPassthrough<br />
{{Comment|[[User:Lars.kurth|Lars.kurth]] 14:14, 23 January 2013 (UTC):}} Would also need more detail<br />
}}<br />
<br />
{{project<br />
|Project=Implement Xen PVSCSI support in xl/libxl toolstack<br />
|Date=01/12/2012<br />
|Contact=Pasi Karkkainen <pasik@iki.fi><br />
|GSoC=Yes<br />
|Desc=<br />
xl/libxl does not currently support Xen PVSCSI functionality. Port the feature from xm/xend to xl/libxl. Necessary operations include:<br />
* Task 1: Implement PVSCSI in xl/libxl, make it functionally equivalent to xm/xend.<br />
* Send to xen-devel mailinglist for review, comments.<br />
* Fix any upcoming issues.<br />
* Repeat until merged to xen-unstable.<br />
* See above for PVSCSI drivers for dom0/domU.<br />
* Xen PVSCSI supports both PV domUs and HVM guests with PV drivers.<br />
* More info: http://wiki.xen.org/xenwiki/XenPVSCSI<br />
{{Comment|[[User:Lars.kurth|Lars.kurth]] 14:14, 23 January 2013 (UTC):}} Should be suitable, but desc needs. Rate in terms of challenges, size and skill. Also kernel functionality is not yet upstreamed. Maybe Suse kernel.<br />
}}<br />
<br />
{{project<br />
|Project=Utilize Intel QuickPath on network and block path.<br />
|Date=01/22/2013<br />
|Difficulty=High<br />
|Contact=Konrad Rzeszutek Wilk <konrad.wilk@oracle.com><br />
|Desc=The Intel QuickPath, also known as Direct Cache Access, is the chipset that sits in the PCIe subsystem in the Intel systems. It allows the PCIe subsystem to tag which PCIe writes to memory should reside in the Last Level Cache (LLC, also known as L3, which in some cases can be of 15MB or 2.5MB per CPU). This offers incredible boosts of speed - as we bypass the DIMMs and instead the CPU can process the data in the cache.<br />
<br />
Adding this component in the network or block backends can mean that we can keep the data longer in the cache and the guest can process the data right off the cache.<br />
<br />
|Skills=The basic requirement for this project is Linux kernel programming skill.<br />
The candidate for this project should be familiar with open source development workflow as it may require collaboration with several parties.<br />
<br />
|Outcomes=Expected outcome:<br />
* Have upstream patches.<br />
* benchmark report of with and without.<br />
|GSoC=Yes<br />
}}<br />
<br />
<br />
{{project<br />
|Project=Enabling the 9P File System transport as a paravirt device<br />
|Date=01/20/2014<br />
|Contact=Andres Lagar-Cavilla <andres@lagarcavilla.org><br />
|GSoC=Yes<br />
|Desc=VirtIO provides a 9P FS transport, which is essentially a paravirt file system device. VMs can mount arbitrary file system hierarchies exposed by the backend. The 9P FS specification has been around for a while, while the VirtIO transport is relatively new. The project would consist of implementing a classic Xen front/back pv driver pair to provide a transport for the 9P FS Protocol.<br />
<br />
* More info: http://www.linux-kvm.org/page/9p_virtio<br />
<br />
|Skills= Required skills include knowledge of kernel hacking, file system internals. Desired skills include: understanding of Xen PV driver structure, and VirtIO.<br />
<br />
|Outcomes=Expected outcome:<br />
* LKML patches for front and back end drivers. <br />
* In particular, domain should be able to boot from the 9P FS.<br />
}}<br />
<br />
{{project<br />
|Project=OVMF Compatibility Support Module support in Xen<br />
|Date=2/5/2014<br />
|Contact=Wei Liu <wei.liu2@citrix.com><br />
|GSoC=Yes<br />
|Difficulty=Easy<br />
|Desc=<br />
Currently Xen supports booting HVM guest with Seabios and OVMF UEFI firmware, but those are separate binaries. OVMF supports adding legacy BIOS blob in its binary with Compatibility Support Module support. We can try to produce single OVMF binary with Seabios in it, thus having only one firmware binary.<br />
<br />
Tasks may include:<br />
* figure out how CSM works<br />
* design / implement interface between Hvmloader and the unified binary<br />
<br />
}}<br />
<br />
{{project<br />
|Project=Improvements to firmware handling HVM guests<br />
|Date=07/16/2015<br />
|Contact=Andrew Cooper <andrew.cooper3@citrix.com><br />
|GSoC=Yes<br />
|Difficulty=Easy<br />
|Skills Needed=Gnu toolchain, Familiarity with Multiboot, C<br />
|Desc=<br />
Currently, all firmware is compiled into HVMLoader.<br />
<br />
This works, but is awkward when used using a single distro seabios/ovmf designed for general use. In such a case, any time an update to seabios/ovmf happens, hvmloader must be rebuilt.<br />
<br />
The purpose of this project is to alter hvmloader to take firmware blobs as a multiboot module rather than requiring them to be built in. This reduces the burden of looking after Xen in a distro environment, and will also be useful for developers wanting to work with multiple versions of firmware.<br />
<br />
As an extension, support loading an OVMF NVRAM blob. This enabled EFI NVRAM support for guests.<br />
}}<br />
<br />
=== Hypervisor ===<br />
<br />
{{project<br />
|Project=Introducing PowerClamp-like driver for Xen<br />
|Date=01/22/2013<br />
|Contact=George Dunlap <george.dunlap@eu.citrix.com><br />
|Desc=<br />
PowerClamp was introduced to Linux in late 2012 in order to allow users to set a system-wide maximum<br />
power usage limit. This is particularly useful for data centers, where there may be a need to<br />
reduce power consumption based on availability of electricity or cooling. A [http://lwn.net/Articles/528124/ more complete writeup]<br />
is available at LWN.<br />
<br />
These same arguments apply to Xen. The purpose of this project would be to implement a similar functionality in Xen,<br />
and to make it interface as well as possible with the Linux PowerClamp tools, so that the same tools could be used<br />
for both. [[GSoC_2013#powerclamp-for-xen]]<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=Integrating NUMA and Tmem<br />
|Date=08/08/2012<br />
|Contact=Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, Dario Faggioli <[mailto:dario.faggioli@citrix.com dario.faggioli@citrix.com]><br />
|Desc=NUMA (Non-Uniform Memory Access) systems are advanced server platforms, comprising multiple ''nodes''. Each node contains processors and memory. An advanced memory controller allows a node to use memory from all other nodes, but that happens, data transfer is slower than accessing local memory. Memory access times are not uniform and depend on the location of the memory and the node from which it is accessed, hence the name.<br />
<br />
Trascendent memory (Tmem) can be seen as a mechanism for discriminating between frequently and infrequently used data, and thus helping allocating them properly. It would be interesting to investigate and implement all the necessary mechanisms to take advantage of this and improve performances of Tmem enabled guests running on NUMA machines.<br />
<br />
For instance, implementing something like <code>alloc_page_on_any_node_but_the_current_one()</code> (or <code>any_node_except_this_guests_node_set()</code> for multinode guests), and have Xen's Tmem implementation use it (especially in combination with selfballooning), could solve a significant part of the NUMA problem when running Tmem-enabled guests.<br />
}}<br />
<br />
=== Userspace Tools ===<br />
<br />
<br />
{{project<br />
|Project=Refactor Linux hotplug scripts<br />
|Date=15/11/2012<br />
|Contact=Roger Pau Monné <[mailto:roger.pau@citrix.com roger.pau@citrix.com]><br />
|Desc=<br />
Current Linux hotplug scripts are all entangled, which makes them really difficult to understand or modify. The reason of hotplug scripts is to give end-users the chance to "easily" support different configuration for Xen devices.<br />
<br />
Linux hotplug scripts should be analized, providing a good description of what each hotplug script is doing. After this, scripts should be cleaned, putting common pieces of code in shared files across all scripts. A Coding style should be applied to all of them when the refactoring is finished.<br />
<br />
[[GSoC_2013#linux-hotplug-scripts]]<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=XL to XCP VM motion<br />
|Date=15/11/12<br />
|Contact=[mailto:ian.campbell@citrix.com Ian Campbell]<br />
|Desc=Currently [[XL|xl]] (the toolstack supplied alongside Xen) and [[XAPI|xapi]] (the XCP toolstack) have very different concepts about domain configuration, disk image storage etc. In the XCP model domain configuration is persistent and stored in a data base while under xl domain configuration is written in configuration files. Likewise disk images are stored as VDIs in Storage Repositories while under xl disk images are simply files or devices in the dom0 filesystem. For more information on xl see [[XL]]. For more information on XCP see [[XCP Overview]].<br />
<br />
This project is to produce one or more command-line tools which support migrating VMs between these toolstacks.<br />
<br />
One tool should be provided which takes an xl configuration file and details of an XCP pool. Using the XenAPI XML/RPC interface It should create a VM in the pool with a close approximation of the same configuration and stream the configured disk image into a selected Storage Repository.<br />
<br />
A second tool should be provided which performs the opposite operation, i.e. give a reference to a VM residing in an XCP pool it should produce an XL compatible configuration file and stream the disk image(s) our of Xapi into a suitable format.<br />
<br />
These tools could be reasonably bundled as part of either toolstack and by implication could be written in either C, Ocaml or some other suitable language.<br />
<br />
The tool need not operate on a live VM but that could be considered a stretch goal.<br />
<br />
An acceptable alternative to the proposed implementation would be to implement a tool which converts between a commonly used VM container format which is supported by XCP (perhaps [http://en.wikipedia.org/wiki/Open_Virtualization_Format OVF] or similar) and the xl toolstack configuration file and disk image formats.<br />
<br />
[[GSoC_2013#xl-to-xcp-vm-motion]]<br />
|GSoC=Yes<br />
}}<br />
<br />
<br />
{{project<br />
|Project=Allowing guests to boot with a passed-through GPU as the primary display<br />
|Date=01/22/2013<br />
|Contact=George Dunlap <george.dunlap@eu.citrix.com><br />
|Desc=<br />
One of the primary drivers of Xen in the "consumer market" of the open-source world is the ability to<br />
pass through GPUs to guests -- allowing people to run Linux as their main desktop but easily play <br />
games requiring proprietary operating systems without rebooting.<br />
<br />
GPUs can be easily passed through to guests as secondary displays, but as of yet cannot be passed<br />
through as primary displays. The main reason is the lack of ability to load the VGA BIOS from the card into the guest.<br />
<br />
The purpose of this project would be to allow HVM guests to load the physical card's VGA bios, so that the guest can<br />
boot with it as the primary display.<br />
<br />
[[GSoC_2013#gpu-passthrough]]<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=Advanced Scheduling Parameters<br />
|Date=01/22/2013<br />
|Contact=George Dunlap <george.dunlap@eu.citrix.com><br />
|Desc=<br />
The credit scheduler provides a range of "knobs" to control guest behavior, including CPU weight and caps. However,<br />
a number of users have requested the ability to encode more advanced scheduling logic. For instance, "Let this VM max out for 5 minutes out of any given hour; but after that, impose a cap of 20%, so that even if the system is idle he can't an unlimited amount of CPU power without paying for a higher level of service."<br />
<br />
This is too coarse-grained to do inside the hypervisor; a user-space tool would be sufficient. The goal of this project would<br />
be to come up with a good way for admins to support these kinds of complex policies in a simple and robust way.<br />
<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=CPU/RAM/PCI diagram tool<br />
|Date=01/30/2013<br />
|Contact=Andy Cooper <andrew.cooper3@citrix.com><br />
|Difficulty=Low to medium<br />
|Skills=Linux scripting; basic understanding of PC server hardware<br />
|Desc=It is often useful in debugging kernel, hypervisor or performance problems to understand the bus topology of a server. This project will create a layout diagram for a server automatically using data from ACPI Tables, SMBios Tables, lspci output etc. This tool would be useful in general Linux environments including Xen and KVM based virtualisation systems.<br />
<br />
There are many avenues for extension such as labelling relevant hardware errata, performing bus throughput calculations etc.<br />
|Outcomes=A tool is created that can either run on a live Linux system or offline using captured data to produce a graphical representation of the hardware topology of the system including bus topology, hardware device locations, memory bank locations, etc. The tool would be submitted to a suitable open-source project such as the Xen hypervisor project or XCP.<br />
|GSoC=yes}}<br />
<br />
{{project<br />
|Project=KDD (Windows Debugger Stub) enhancements<br />
|Date=01/30/2013<br />
|Contact=Paul Durrant <paul.durrant@citrix.com><br />
|Difficulty=Medium<br />
|Skills=C, Kernel Debuggers, Xen, Windows<br />
|Desc=kdd is a Windows Debugger Stub for Xen hypervisor. It is OSS found under http://xenbits.xen.org/hg/xen-unstable.hg/tools/debugger/kdd<br />
kdd allows you to debug a running Windows virtual machine on Xen using standard Windows kernel debugging tools like WinDbg. kdd is an external debugger stub for the windows kernel. <br />
Windows can be debugged without enabling the debugger stub inside windows kernel by using kdd. This is important for debugging hard to reproduce problems on Windows virtual machines that may not have debugging enabled.<br />
<br />
Expected Results:<br />
# Add support for Windows 8 (x86, x64) to kdd<br />
# Add support for Windows Server 2012 to kdd<br />
# Enhance kdd to allow WinDbg to write out usable Windows memory dumps (via .dump debugger extension) for all supported versions<br />
# Produce a user guide for kdd on Xen wiki page<br />
<br />
Nice to have: Allow kdd to operate on a Windows domain checkpoint file (output of xl save for e.g.)<br />
|Outcomes=Code is submitted to xen-devel@xen.org for inclusion in the xen-unstable project.<br />
|GSoC=yes}}<br />
<br />
{{project<br />
|Project=Lazy restore using memory paging<br />
|Date=01/20/2014<br />
|Contact=Andres Lagar-Cavilla <andres@lagarcavilla.org><br />
|GSoC=Yes<br />
|Desc=VM Save/restore results in a boatload of IO and non-trivial downtime as the entire memory footprint of a VM is read from IO.<br />
<br />
Xen memory paging support in x86 is now mature enough to allow for lazy restore, whereby the footprint of a VM is backfilled while the VM executes. If the VM hits a page not yet present, it is eagerly paged in.<br />
<br />
There has been some concern recently about the lack of docs and/or mature tools that use xen-paging. This is a good way to address the problem.<br />
<br />
|Skills= A good understanding of save/restore, and virtualized memory management (e.g. EPT, shadow page tables, etc). In principle the entire project can be implemented in user-space C code, but it may be the case that new hypercalls are needed for performance reasons.<br />
<br />
|Outcomes=Expected outcome:<br />
* Mainline patches for libxc and libxl<br />
}}<br />
<br />
{{project<br />
|Project=CPUID Programming for Humans<br />
|Date=02/04/2014<br />
|Contact=Andres Lagar-Cavilla <andres@lagarcavilla.org><br />
|GSoC=Yes<br />
|Desc=When creating a VM, a policy is applied to mask certain CPUID features. Right now it's black magic.<br />
<br />
THe KVM stack has done an excellent job of making this human-useable, and understandable.<br />
<br />
For example, in a qemu-kvm command-line you may encounter:<br />
<br />
-cpu SandyBridge,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme<br />
<br />
And in <qemu>/target-i386.c you find a fairly comprehensive description of x86 processor models, what CPUID features are inherent, and what CPUID feature each of these symbolic flags enables.<br />
<br />
In the Xen world, there is a libxc interface to do the same, although it's all hex and register driven. It's effective, yet horrible to use.<br />
<br />
An ideal outcome would have libxl config files and command line absorb a similarly human-friendly description of the CPUID features a user wishes for the VM, and interface appropriately with libxl. Further, autodetection of best CPUID shuold yield a human-readable output to be able to easily understand what the VM thinks about its processor.<br />
<br />
Finally, interfacing with libvirt should be carefully considered.<br />
<br />
CPUID management is crucial in a heterogeneous cluster where migrations and save restore require careful processor feature selection to avoid blow-ups.<br />
<br />
|Skills= A good understanding of C user-land programming, and the ability to dive into qemu/libvirt (for reference code and integration), as well as libxc and libxl (for implementation).<br />
<br />
|Outcomes=Expected outcome:<br />
* Mainline patches for libxl<br />
}}<br />
<br />
=== Mirage and XAPI projects ===<br />
There are separate wiki pages about XCP and XAPI related projects. Make sure you check these out aswell!<br />
<br />
{{project<br />
|Project=Create a tiny VM for easy load testing<br />
|Date=01/30/2013<br />
|Contact=Dave Scott <''first.last''@citrix.com><br />
|Difficulty=Medium<br />
|Skills=OCaml<br />
|Desc=The http://www.openmirage.org/ framework can be used to create tiny 'exokernels': entire software stacks which run directly on the xen hypervisor. These VMs have such a small memory footprint (16 MiB or less) that many of them can be run even on relatively small hosts. The goal of this project is to create a specific 'exokernel' that can be configured to generate a specific I/O pattern, and to create configurations that mimic the boot sequence of Linux and Windows guests. The resulting exokernel will then enable cheap system load testing.<br />
<br />
The first task is to generate an I/O trace from a VM. For this we could use 'xen-disk', a userspace Mirage application which acts as a block backend for xen guests (see http://openmirage.org/wiki/xen-synthesize-virtual-disk). Following the wiki instructions we could modify a 'file' backend to log the request timestamps, offsets, buffer lengths.<br />
<br />
The second task is to create a simple kernel based on one of the MirageOS examples (see http://github.com/mirage/mirage-skeleton). The 'basic_block' example shows how reads and writes are done. The previously-generated log could be statically compiled into the kernel and executed to generate load.<br />
|Outcomes=1. a repository containing an 'exokernel' (see http://github.com/mirage/mirage-skeleton)<br />
2. at least 2 I/O traces, one for Windows boot and one for Linux boot (any version)<br />
|GSoC=yes}}<br />
<br />
<br />
{{project<br />
|Project=Fuzz testing Xen with Mirage<br />
|Date=28/11/2012<br />
|Contact=Anil Madhavapeddy <anil@recoil.org><br />
|Skills=OCaml<br />
|Difficulty=medium<br />
|Desc=<br />
MirageOS (http://openmirage.org) is a type-safe exokernel written in OCaml which generates highly specialised "appliance" VMs that run directly on Xen without requiring an intervening guest kernel. We would like to use the Mirage/Xen libraries to fuzz test all levels of a typical cloud toolstack. Mirage has low-level bindings for Xen hypercalls, mid-level bindings for domain management, and high-level bindings to XCP for cluster management. This project would build a QuickCheck-style fuzzing mechanism that would perform millions of random operations against a real cluster, and identify bugs with useful backtraces.<br />
<br />
The first task would be to become familiar with a specification-based testing tool like Kaputt (see http://kaputt.x9c.fr/). The second task would be to choose an interface for testing; perhaps one of the hypercall ones.<br />
[[GSoC_2013#fuzz-testing-mirage]]<br />
|Outcomes=1. a repo containing a fuzz testing tool; 2. some unexpected behaviour with a backtrace (NB it's not required that we find a critical bug, we just need to show the approach works)<br />
|GSoC=yes<br />
}}<br />
<br />
{{project<br />
|Project=From simulation to emulation to production: self-scaling apps<br />
|Date=28/11/2012<br />
|Contact=Anil Madhavapeddy <anil@recoil.org><br />
|Difficulty=hard<br />
|Skills=OCaml<br />
|Desc=<br />
MirageOS (http://openmirage.org) is a type-safe exokernel written in OCaml which generates highly specialised "appliance" VMs that run directly on Xen without requiring an intervening guest kernel. An interesting consequence of programming Mirage applications in a functional language is that the device drivers can be substituted with emulated equivalents. Therefore, it should be possible to test an application under extreme load conditions as a simulation, and then recompile the *same* code into production. The simulation can inject faults and test data structures under distributed conditions, but using a fraction of the resources required for a real deployment.<br />
<br />
The first task is to familiarise yourself with a typical Mirage application, I suggest a webserver (see https://github.com/mirage/mirage-www). The second task is to replace the ethernet driver with a synthetic equivalent, so we can feed it simulated traffic. Third, we should inject simulated web traffic (recorded from a real session) and attempt to determine how the application response time varies with load (number of connections; incoming packet rate).<br />
<br />
This project will require a solid grasp of distributed protocols, and functional programming. Okasaki's book will be a useful resource...<br />
|Outcomes=1. a repo/branch with a fake ethernet device and a traffic simulator; 2. an interesting performance graph<br />
|GSoC=no, too much work<br />
}}<br />
<br />
{{project<br />
|Project=Towards a multi-language unikernel substrate for Xen<br />
|Date=28/11/2012<br />
|Contact=Anil Madhavapeddy <anil@recoil.org><br />
|Difficulty=hard<br />
|Skills=OCaml, Haskell, Java<br />
|Desc=<br />
There are several languages available that compile directly to Xen microkernels, instead of running under an intervening guest OS. We're dubbing such specialised binaries as "unikernels". Examples include:<br />
<br />
* OCaml: Mirage http://openmirage.org<br />
* Haskell: HalVM https://github.com/GaloisInc/HaLVM#readme<br />
* Erlang: ErlangOnXen http://erlangonxen.org<br />
* Java: GuestVM http://labs.oracle.com/projects/guestvm/, OSv https://github.com/cloudius-systems/osv<br />
<br />
Each of these is in a different state of reliability and usability. We would like to survey all of them, build some common representative benchmarks to evaluate them, and build a common toolchain based on XCP that will make it easier to share code across such efforts. This project will require a reasonable grasp of several programming languages and runtimes, and should be an excellent project to learn more about the innards of popular languages.<br />
<br />
[[GSoC_2013#unikernel-substrate]]<br />
|Outcomes=1. a repo containing a common library of low-level functions; 2. a proof of concept port of at least 2 systems to this new library<br />
|GSoC=no, too difficult<br />
}}<br />
<br />
{{project<br />
|Project=DRBD Integration<br />
|Date=07/01/2013<br />
|Contact=John Morris <john@zultron.com><br />
|Desc=<br />
DRBD is potentially a great addition to the other high-availability features in XenAPI. An architecture of as few as two Dom0s with DRBD mirrored local storage is an inexpensive minimal HA configuration enabling live migration of VMs between physical hosts and providing failover in case of disk failure, and eliminates the need for external storage. This setup can be used in small shop or hobbyist environments, or could be used as a basic unit in a much larger scalable architecture.<br />
<br />
Existing attempts at integrating DRBD sit below the SM layer and thus do not enable one VBD per DRBD device. They also suffer from a split-brain situation that could be avoided by controlling active/standby status from XenAPI.<br />
<br />
DRBD should be implemented as a new SR type on top of LVM. The tools for managing DRBD devices need to be built into storage management, along with the logic for switching the active and standby nodes.<br />
}}<br />
<br />
<!--<br />
* XCP and XAPI development projects: [[XAPI project suggestions]]<br />
* XCP short-term roadmap: [[XCP short term roadmap]]<br />
* XCP monthly developer meetings: [[XCP Monthly Meetings]]<br />
--><br />
* XAPI developer guide: [[XAPI Developer Guide]]<br />
<br />
== Quick links to changelogs of the various Xen related repositories/trees ==<br />
Please see [[XenRepositories]] wiki page!<br />
<br />
[[Category:Xen]]<br />
[[Category:Xen 4.4]]<br />
[[Category:PVOPS]]<br />
[[Category:Developers]]<br />
[[Category:Index]]<br />
[[Category:Project]]<br />
[[Category:Transient]] <!-- as if not maintained it becomes stale --></div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/Hackathon/April2015&diff=14528Archived/Hackathon/April20152015-03-12T13:35:09Z<p>Andyhhp: </p>
<hr />
<div>{{TODO|<br />
* Add more information on how to get from the hotels to some key sights in Shanghai using public transport (do by week of March 16)<br />
* Finalise time-table and bus pick-up with times (do by week of March 16)<br />
* Provide details on what to do when arriving at Intel (do by week of March 16)<br />
}}<br />
<br />
== When and Where ? ==<br />
<br />
=== Intel Shanghai, April 28-29 ===<br />
Intel will be hosting this years Xen Project Hackathon on April 28-29, 2015 at their [http://wikimapia.org/17649474/Intel-Zizhu-Campus Shanghai Site]. <br />
<br />
We will start at 9AM and finish at 5PM each day. '''There will also be an evening social event on April 28th : more details will follow.'''<br />
<br />
Address in English:<br />
: Intel Asia-Pacific Research and Development Ltd. <br />
: No. 880, Zixing Road<br />
: Shanghai Zizhu Science Park, <br />
: Min Hang District<br />
: Shanghai (200241)<br />
<br />
Address in Chinese:<br />
: 闵行区紫竹科学园区紫星路880号<br />
<br />
: Tel: 86-21-61165000<br />
<br />
'''[https://www.google.co.uk/maps/place/intel/@31.0233092,121.4515338,16z/data=!4m6!1m3!3m2!1s0x0000000000000000:0x2c789dc6a32a909d!2sintel!3m1!1s0x0000000000000000:0x2c789dc6a32a909d Check out the event location on the map]'''<br />
<br />
=== Schedule ===<br />
<br />
==== April 28th ====<br />
<br />
<pre><br />
8:45 - 9:30 Registration (Breakfast will not be provided)<br />
9:30 - 9:45 Welcome<br />
9:45 - 10:30 Scheduling<br />
10:30 - 11:30 Sessions 1<br />
11:30 - 12:30 Sessions 2<br />
12:30 - 13:30 Lunch<br />
13:30 - 14:30 Sessions 3<br />
14:30 - 15:30 Sessions 4<br />
15:30 - 16:00 Break <br />
16:00 - 17:00 Sessions 4<br />
17:00 - 17:30 Plenary<br />
</pre><br />
<br />
==== April 29th ====<br />
<pre><br />
9:00 - 9:45 Arrival<br />
9:45 - 10:15 Scheduling<br />
10:15 - 11:30 Sessions 1<br />
11:30 - 12:30 Sessions 2<br />
12:30 - 13:30 Lunch<br />
13:30 - 14:30 Sessions 3<br />
14:30 - 15:30 Sessions 4<br />
15:30 - 16:00 Break <br />
16:00 - 16:45 Plenary: Share achievements<br />
16:45 - 17:00 Closing<br />
</pre><br />
<br />
=== Recommended Hotel Options ===<br />
We will be organising a bus from and to one of the hotels below. They are all within walking distance from each other. More details will follow.<br />
<br />
==== Sheraton Shanghai Hongqiao Hotel ====<br />
[http://www.starwoodhotels.com/sheraton/property/overview/index.html?propertyID=1056&language=en_US Booking Information] and maps ([https://www.google.co.uk/maps/search/Sheraton+Shanghai+Hongqiao+Hotel/@31.203639,121.405572,17z/data=!3m1!4b1 english])<br />
<br />
Cost: around USD 150 - 230 per night based on room type and availability<br />
<br />
Address:<br />
: 5 Zun Yi Nan Road<br />
: Changning District<br />
: Shanghai 200336<br />
: China<br />
<br />
Chinese Address:<br />
: 长宁区遵义南路5号(靠近世贸商城,近上海国际展览中心)上海虹桥喜来登酒店<br />
<br />
==== Renaissance Shanghai Yangtze Hotel ====<br />
[http://www.marriott.com/hotels/travel/shabr-renaissance-shanghai-yangtze-hotel/ Booking Information] and maps ([https://www.google.co.uk/maps/search/Renaissance+Shanghai+Yangtze+Hotel/@31.203148,121.405792,17z/data=!3m1!4b1 english])<br />
<br />
Cost: around USD 115 - 240 per night based on room type and availability<br />
<br />
Address:<br />
: Renaissance Shanghai Yangtze Hotel<br />
: 2099 Yan'an West Road<br />
: Changning District <br />
: Shanghai 200336 <br />
: China <br />
<br />
Chinese Address:<br />
: 扬子江万丽大酒店 长宁区延安西路 2099 号, 邮编 200336<br />
<br />
==== Jin Jiang Rainbow Hotel ====<br />
<br />
[http://www.e-rainbowhotel.com/ Booking Information] and maps ([https://www.google.co.uk/maps/place/Jin+Jiang+Rainbow+Hotel/@31.2041,121.4106,17z/data=!3m1!4b1!4m2!3m1!1s0x35b2650ded63a25d:0x71972f09d770144f english])<br />
<br />
Cost: around USD 90 - 120 per night based on room type<br />
<br />
Address: <br />
: 2000 Yan An Road (W)<br />
: Changning District <br />
: Shanghai 200336 <br />
: China <br />
<br />
Chinese Address:<br />
: 锦江虹桥宾馆 延安西路2000号<br />
<br />
=== Transport Information ===<br />
This [http://wiki.xenproject.org/mediawiki/images/9/9a/Hackathon15-maps.pdf map] shows you the relative positions of the Intel campus, recommended hotels and key sights within Shanghai.<br />
<br />
==== Buses from hotels to the Intel Campus ====<br />
We will be organising a bus service from the recommended hotels (see above) to the Intel site in the morning and the evening. Exact pick-up and return times will be published later.<br />
<br />
==== Other ways to get to the Intel Campus ====<br />
Taxi's in Shanghai are relatively cheap. You are looking at a cost of around $20-$25 for a 1-1.5 hour taxi ride of about 30-35 km's. There is no easy way to get to the Intel site by public transport. Should you chose to use a taxi or chose to stay in a different hotel to those recommended, please make sure you organise the taxi with the concierge at your hotel. Printing out a map of the Intel site's location and the address in Chinese as well as your hotel address also helps.<br />
<br />
Reference distances to the Intel site:<br />
* [http://en.wikipedia.org/wiki/The_Bund The Bund] : 38 km's - approximately 1.5 hours<br />
* [http://en.wikipedia.org/wiki/Pudong Pudong] : 40 km's - approximately 1.5 hours<br />
* Recommended hotels in Hongqiao : 27 km's - approximately 1 hour<br />
<br />
==== Getting from the airport to the Hotels and vice versa ====<br />
To get from the airport to one of the recommended hotels, you can take a taxi. It is about a 50 km drive and will take 1-1.5 hours depending on the day of time. It will cost around $25-$30. Make sure to go to the airport's taxi stand and do *not* use one of the offers for a taxi when you come out of the gate. These are normally limousine services which will cost you several times more than a regular taxi. You should also print out the name and a map of the hotel, just in case.<br />
<br />
Alternatively, you can use public transport: see [https://www.google.co.uk/maps/dir/Sheraton+Shanghai+Hongqiao+Hotel,+5+Zunyi+South+Road,+Changning,+Shanghai,+China,+200336/A%C3%A9roport+international+de+Shanghai-Pudong,+S1+Yingbin+Expressway,+Pudong,+Shanghai,+China/@31.1918368,121.5323124,12z/data=!3m1!4b1!4m14!4m13!1m5!1m1!1s0x35b2650c024cf2a5:0x195cb22c6550b990!2m2!1d121.405572!2d31.203639!1m5!1m1!1s0x35ad8fde769550c1:0xc9e41371c92c355f!2m2!1d121.808273!2d31.144344!3e3 the following map]<br />
<br />
==== Taxi's in Shanghai ====<br />
Taxi's in Shanghai are relatively cheap. For more information see [http://www.travelchinaguide.com/cityguides/shanghai/transportation/taxi.htm the Travel China Guide]<br />
<br />
=== Visa Invitation Letters ===<br />
If you require an invitation, please send an e-mail to community dot manager at xenproject dot org (important: from March 5 to 10 please send to Russell dot pavlicek at xenproject dot org). You should leave make sure that you have at least 2 weeks to organise a visa with your local Chinese Embassy after you have received the visa invitation letter. Please provide the following information:<br />
<br />
==== Personal Information ====<br />
* Name <br />
* Gender<br />
* Date of birth<br />
* Nationality<br />
* Passport number<br />
* Full name of the company which you work for<br />
* Job title<br />
<br />
==== Other Information ====<br />
* Date of arrival and leaving - note that you need a full itinerary in the visa application, but that in practice after you received the visa modifications to the schedule without notifying the Chinese Embassy is OK<br />
* State your role in the Xen Project Community<br />
* You will need to state who will bear the cost of travel to/from China and your accommodation in China<br />
<br />
We will be processing invitation letters from the first week of March. Note that you do need to provide hotel information, when you apply for a Chinese visa. General information about receiving visa's to China can be found [http://www.travelchinaguide.com/embassy/visa/require<br />
<br />
== Topics to Discuss, Code, Work on, ... at the Hackathon ==<br />
=== Instructions ===<br />
{{ambox<br />
|type=notice<br />
|text=Please use the {{Tl|Project}} template to add any discussions that you want to have at the Hackathon. Feel free to comment on discussions using {{Tl|Comment}} and your support for a specific topic - i.e. you indicate that you want to participate in this topic - by using {{Tl|Vote}} or {{Tl|VoteNo}} in the Review section of the project. To do this, use the Review section of the {{Tl|Project}}.<br />
<br />
The code will look like<br />
<br />
<pre><br />
{{project=Name<br />
...<br />
|Review=<br />
{{comment|~~~~:}} Some text/comment<br />
{{vote|~~~~}} Some explanation<br />
}}<br />
</pre><br />
Make sure you read the template documentation of {{Tl|Project}}, {{Tl|Comment}}, {{Tl|Vote}} and {{Tl|VoteNo}}. Mark unused fields of {{Tl|Project}} with {{Tl|N/A}}.<br />
}}<br />
<br />
=== Topics ===<br />
<br />
Please add topics you want to discuss in this section as described above<br />
<br />
{{project<br />
|Project=Intel Virtual Graphics<br />
|Date=March 5th 2015<br />
|Verified={{N/A}}<br />
|Contact=Paul Durrant <paul.durrant@citrix.com><br />
|Difficulty={{N/A}}<br />
|Skills={{N/A}}<br />
|Desc=<br />
Code to support virtual graphics on Intel GPUs a.k.a XenGT needs to be upstreamed<br />
|GSoc={{N/A}}<br />
}}<br />
<br />
{{project<br />
|Project=Stable release cadence<br />
|Date=2015-03-12<br />
|Verified={{N/A}}<br />
|Contact=Jan Beulich <jbeulich@suse.com><br />
|Difficulty={{N/A}}<br />
|Skills={{N/A}}<br />
|Desc=The time delta between stable releases has been growing, for varying reasons. Is this okay with everyone?<br />
|GSoc={{N/A}}<br />
}}<br />
<br />
== I want to attend ==<br />
<br />
=== Request an Invitation ===<br />
<br />
In previous years we have requested for attendees to fill out a form and request an invitation. This was overly complicated, so we will revert back to a simpler approach. Please add your name to the [[#Request|list below]]. <br />
* If you are a maintainer or otherwise a core member of the community, just add yourself to the [[#Confirmed_attendees|Confirmed Attendees]] section stating your name and <br />
* If you are '''not''' a maintainer add yourself the [[#Request|Request invitation]]. If your '''email address is not known''' in the Xen Community, please also add the name of your employer and send your e-mail address to ''community dot manager at xenproject dot org'' using "Request for Hackathon 2015 Invite" as subject line. This is important, such that we can e-mail more information to you. We will monitor this page and confirm whether we have space for you to attend.<br />
<br />
'''IMPORTANT:''' The cut-off date for registrations is '''April 12th'''.<br />
<br />
Please read the text in the warning box below: it contains more detailed instructions.<br />
<br><br />
{{WarningLeft|To edit this page and thus to '''Request an Invitation''', you '''need to be added to the wiki's editors group'''. To be added to that group: <br />
* If you do not have a wiki account, please create one by using [[Special:UserLogin|this link]]. Write down your '''user name''' (we cannot look up user names from e-mail addresses) <br />
* Please [http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html fill out this form] (note: this form does not work in China) <br />
* If you cannot access the form, please send an email to community.manager at xenproject.org requesting that you need wiki access ('''important:''' from March 5 to 10 please CC Russell dot Pavlicek at xenproject dot org) with your user name.}}<br />
{{Anchor|Request}}<br />
<br />
=== Request invitation ===<br />
<br />
# Add your name and org here - optionally you may also want to state the hotel you are staying at<br />
# Chunjie Zhu (Citrix)<br />
# Phus Lu (Citrix)<br />
<br />
<br />
=== Confirmed attendees ===<br />
{{InfoLeft|Important note:<br />
* We have a maximum of 50 spaces<br />
* The cut-off for registration is '''April the 12th''', as we need to organise transport from the hotel, food, security passes, etc.<br />
}}<br />
<br />
If you are a maintainer or otherwise known in the Xen Project community please add your name below, if you want you can share your hotel, whether you are planning to attend the social event and whether you will use the bus.<br />
<br />
# Lars Kurth, Citrix - staying at Sheraton Shanghai Hongqiao Hotel, attending evening social event {{Tick}}, will use bus {{Tick}}<br />
# Paul Durrant, Citrix<br />
# Jan Beulich, SUSE<br />
# Gui Jianfeng, Fujitsu<br />
# Wen Congyang, Fujitsu<br />
# Yang Hongyang, Fujitsu<br />
# Yang Zhang, Intel<br />
# Wei Wang, Intel<br />
# Liang Li, Intel<br />
# Tianyu Lan, Intel<br />
# Guangrong Xiao, Intel<br />
# Feng Wu, Intel<br />
# Chao Peng, Intel<br />
# Kai Huang, Intel<br />
# Eddie Dong, Intel<br />
# Kevin Tian, Intel<br />
# Yu Zhang, Intel<br />
# Yulei Zhang, Intel<br />
# Xiao Zheng, Intel<br />
# Ping Gao, Intel<br />
# Hongbo Wang, Intel<br />
# Andrew Cooper (Citrix, x86 Maintainer)<br />
# Robert Hu, Intel<br />
# Xudong Hao, Intel<br />
# Gordon Jin, Intel<br />
# Daniel Kiper, Oracle<br />
# Wei Liu, Citrix<br />
# Elena Ufimtseva, Oracle<br />
# Konrad Rzeszutek Wilk, Oracle<br />
# Ian Campbell, Citrix<br />
# Bob Liu, Oracle<br />
<br />
[[Category:Project]]<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/Hackathon/April2015&diff=14505Archived/Hackathon/April20152015-03-06T23:39:00Z<p>Andyhhp: /* Request invitation */</p>
<hr />
<div>{{TODO|<br />
* Add more information on how to get from the hotels to some key sights in Shanghai using public transport (do by week of March 16)<br />
* Finalise time-table and bus pick-up with times (do by week of March 16)<br />
* Provide details on what to do when arriving at Intel (do by week of March 16)<br />
}}<br />
<br />
== When and Where ? ==<br />
<br />
=== Intel Shanghai, April 28-29 ===<br />
Intel will be hosting this years Xen Project Hackathon on April 28-29, 2015 at their [http://wikimapia.org/17649474/Intel-Zizhu-Campus Shanghai Site]. <br />
<br />
We will start at 9AM and finish at 5PM each day. '''There will also be an evening social event on April 28th : more details will follow.'''<br />
<br />
Address in English:<br />
: Intel Asia-Pacific Research and Development Ltd. <br />
: No. 880, Zixing Road<br />
: Shanghai Zizhu Science Park, <br />
: Min Hang District<br />
: Shanghai (200241)<br />
<br />
Address in Chinese:<br />
: 闵行区紫竹科学园区紫星路880号<br />
<br />
: Tel: 86-21-61165000<br />
<br />
'''[https://www.google.co.uk/maps/place/intel/@31.0233092,121.4515338,16z/data=!4m6!1m3!3m2!1s0x0000000000000000:0x2c789dc6a32a909d!2sintel!3m1!1s0x0000000000000000:0x2c789dc6a32a909d Check out the event location on the map]'''<br />
<br />
=== Schedule ===<br />
<br />
==== April 28th ====<br />
<br />
<pre><br />
8:45 - 9:30 Registration (Breakfast will not be provided)<br />
9:30 - 9:45 Welcome<br />
9:45 - 10:30 Scheduling<br />
10:30 - 11:30 Sessions 1<br />
11:30 - 12:30 Sessions 2<br />
12:30 - 13:30 Lunch<br />
13:30 - 14:30 Sessions 3<br />
14:30 - 15:30 Sessions 4<br />
15:30 - 16:00 Break <br />
16:00 - 17:00 Sessions 4<br />
17:00 - 17:30 Plenary<br />
</pre><br />
<br />
==== April 29th ====<br />
<pre><br />
9:00 - 9:45 Arrival<br />
9:45 - 10:15 Scheduling<br />
10:15 - 11:30 Sessions 1<br />
11:30 - 12:30 Sessions 2<br />
12:30 - 13:30 Lunch<br />
13:30 - 14:30 Sessions 3<br />
14:30 - 15:30 Sessions 4<br />
15:30 - 16:00 Break <br />
16:00 - 16:45 Plenary: Share achievements<br />
16:45 - 17:00 Closing<br />
</pre><br />
<br />
=== Recommended Hotel Options ===<br />
We will be organising a bus from and to one of the hotels below. They are all within walking distance from each other. More details will follow.<br />
<br />
==== Sheraton Shanghai Hongqiao Hotel ====<br />
[http://www.starwoodhotels.com/sheraton/property/overview/index.html?propertyID=1056&language=en_US Booking Information] and maps ([https://www.google.co.uk/maps/search/Sheraton+Shanghai+Hongqiao+Hotel/@31.203639,121.405572,17z/data=!3m1!4b1 english])<br />
<br />
Cost: around USD 150 - 230 per night based on room type and availability<br />
<br />
Address:<br />
: 5 Zun Yi Nan Road<br />
: Changning District<br />
: Shanghai 200336<br />
: China<br />
<br />
Chinese Address:<br />
: 长宁区遵义南路5号(靠近世贸商城,近上海国际展览中心)上海虹桥喜来登酒店<br />
<br />
==== Renaissance Shanghai Yangtze Hotel ====<br />
[http://www.marriott.com/hotels/travel/shabr-renaissance-shanghai-yangtze-hotel/ Booking Information] and maps ([https://www.google.co.uk/maps/search/Renaissance+Shanghai+Yangtze+Hotel/@31.203148,121.405792,17z/data=!3m1!4b1 english])<br />
<br />
Cost: around USD 115 - 240 per night based on room type and availability<br />
<br />
Address:<br />
: Renaissance Shanghai Yangtze Hotel<br />
: 2099 Yan'an West Road<br />
: Changning District <br />
: Shanghai 200336 <br />
: China <br />
<br />
Chinese Address:<br />
: 扬子江万丽大酒店 长宁区延安西路 2099 号, 邮编 200336<br />
<br />
==== Jin Jiang Rainbow Hotel ====<br />
<br />
[http://www.e-rainbowhotel.com/ Booking Information] and maps ([https://www.google.co.uk/maps/place/Jin+Jiang+Rainbow+Hotel/@31.2041,121.4106,17z/data=!3m1!4b1!4m2!3m1!1s0x35b2650ded63a25d:0x71972f09d770144f english])<br />
<br />
Cost: around USD 90 - 120 per night based on room type<br />
<br />
Address: <br />
: 2000 Yan An Road (W)<br />
: Changning District <br />
: Shanghai 200336 <br />
: China <br />
<br />
Chinese Address:<br />
: 锦江虹桥宾馆 延安西路2000号<br />
<br />
=== Transport Information ===<br />
This [http://wiki.xenproject.org/mediawiki/images/9/9a/Hackathon15-maps.pdf map] shows you the relative positions of the Intel campus, recommended hotels and key sights within Shanghai.<br />
<br />
==== Buses from hotels to the Intel Campus ====<br />
We will be organising a bus service from the recommended hotels (see above) to the Intel site in the morning and the evening. Exact pick-up and return times will be published later.<br />
<br />
==== Other ways to get to the Intel Campus ====<br />
Taxi's in Shanghai are relatively cheap. You are looking at a cost of around $20-$25 for a 1-1.5 hour taxi ride of about 30-35 km's. There is no easy way to get to the Intel site by public transport. Should you chose to use a taxi or chose to stay in a different hotel to those recommended, please make sure you organise the taxi with the concierge at your hotel. Printing out a map of the Intel site's location and the address in Chinese as well as your hotel address also helps.<br />
<br />
Reference distances to the Intel site:<br />
* [http://en.wikipedia.org/wiki/The_Bund The Bund] : 38 km's - approximately 1.5 hours<br />
* [http://en.wikipedia.org/wiki/Pudong Pudong] : 40 km's - approximately 1.5 hours<br />
* Recommended hotels in Hongqiao : 27 km's - approximately 1 hour<br />
<br />
==== Getting from the airport to the Hotels and vice versa ====<br />
To get from the airport to one of the recommended hotels, you can take a taxi. It is about a 50 km drive and will take 1-1.5 hours depending on the day of time. It will cost around $25-$30. Make sure to go to the airport's taxi stand and do *not* use one of the offers for a taxi when you come out of the gate. These are normally limousine services which will cost you several times more than a regular taxi. You should also print out the name and a map of the hotel, just in case.<br />
<br />
Alternatively, you can use public transport: see [https://www.google.co.uk/maps/dir/Sheraton+Shanghai+Hongqiao+Hotel,+5+Zunyi+South+Road,+Changning,+Shanghai,+China,+200336/A%C3%A9roport+international+de+Shanghai-Pudong,+S1+Yingbin+Expressway,+Pudong,+Shanghai,+China/@31.1918368,121.5323124,12z/data=!3m1!4b1!4m14!4m13!1m5!1m1!1s0x35b2650c024cf2a5:0x195cb22c6550b990!2m2!1d121.405572!2d31.203639!1m5!1m1!1s0x35ad8fde769550c1:0xc9e41371c92c355f!2m2!1d121.808273!2d31.144344!3e3 the following map]<br />
<br />
==== Taxi's in Shanghai ====<br />
Taxi's in Shanghai are relatively cheap. For more information see [http://www.travelchinaguide.com/cityguides/shanghai/transportation/taxi.htm the Travel China Guide]<br />
<br />
=== Visa Invitation Letters ===<br />
If you require an invitation, please send an e-mail to community dot manager at xenproject dot org (important: from March 5 to 10 please send to Russell dot pavlicek at xenproject dot org). You should leave make sure that you have at least 2 weeks to organise a visa with your local Chinese Embassy after you have received the visa invitation letter. Please provide the following information:<br />
<br />
==== Personal Information ====<br />
* Name <br />
* Gender<br />
* Date of birth<br />
* Nationality<br />
* Passport number<br />
* Full name of the company which you work for<br />
* Job title<br />
<br />
==== Other Information ====<br />
* Date of arrival and leaving - note that you need a full itinerary in the visa application, but that in practice after you received the visa modifications to the schedule without notifying the Chinese Embassy is OK<br />
* State your role in the Xen Project Community<br />
* You will need to state who will bear the cost of travel to/from China and your accommodation in China<br />
<br />
We will be processing invitation letters from the first week of March. Note that you do need to provide hotel information, when you apply for a Chinese visa. General information about receiving visa's to China can be found [http://www.travelchinaguide.com/embassy/visa/require<br />
<br />
== Topics to Discuss, Code, Work on, ... at the Hackathon ==<br />
=== Instructions ===<br />
{{ambox<br />
|type=notice<br />
|text=Please use the {{Tl|Project}} template to add any discussions that you want to have at the Hackathon. Feel free to comment on discussions using {{Tl|Comment}} and your support for a specific topic - i.e. you indicate that you want to participate in this topic - by using {{Tl|Vote}} or {{Tl|VoteNo}} in the Review section of the project. To do this, use the Review section of the {{Tl|Project}}.<br />
<br />
The code will look like<br />
<br />
<pre><br />
{{project=Name<br />
...<br />
|Review=<br />
{{comment|~~~~:}} Some text/comment<br />
{{vote|~~~~}} Some explanation<br />
}}<br />
</pre><br />
Make sure you read the template documentation of {{Tl|Project}}, {{Tl|Comment}}, {{Tl|Vote}} and {{Tl|VoteNo}}. Mark unused fields of {{Tl|Project}} with {{Tl|N/A}}.<br />
}}<br />
<br />
=== Topics ===<br />
<br />
Please add topics you want to discuss in this section as described above<br />
<br />
{{project<br />
|Project=Intel Virtual Graphics<br />
|Date=March 5th 2015<br />
|Verified={{N/A}}<br />
|Contact=Paul Durrant <paul.durrant@citrix.com><br />
|Difficulty={{N/A}}<br />
|Skills={{N/A}}<br />
|Desc=<br />
Code to support virtual graphics on Intel GPUs a.k.a XenGT needs to be upstreamed<br />
|GSoc={{N/A}}<br />
}}<br />
<br />
== I want to attend ==<br />
<br />
=== Request an Invitation ===<br />
<br />
In previous years we have requested for attendees to fill out a form and request an invitation. This was overly complicated, so we will revert back to a simpler approach. Please add your name to the [[#Request|list below]]. <br />
* If you are a maintainer or otherwise a core member of the community, just add yourself to the [[#Confirmed_attendees|Confirmed Attendees]] section stating your name and <br />
* If you are '''not''' a maintainer add yourself the [[#Request|Request invitation]]. If your '''email address is not known''' in the Xen Community, please also add the name of your employer and send your e-mail address to ''community dot manager at xenproject dot org'' using "Request for Hackathon 2015 Invite" as subject line. This is important, such that we can e-mail more information to you. We will monitor this page and confirm whether we have space for you to attend.<br />
<br />
'''IMPORTANT:''' The cut-off date for registrations is '''April 12th'''.<br />
<br />
Please read the text in the warning box below: it contains more detailed instructions.<br />
<br><br />
{{WarningLeft|To edit this page and thus to '''Request an Invitation''', you '''need to be added to the wiki's editors group'''. To be added to that group: <br />
* If you do not have a wiki account, please create one by using [[Special:UserLogin|this link]]. Write down your '''user name''' (we cannot look up user names from e-mail addresses) <br />
* Please [http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html fill out this form] (note: this form does not work in China) <br />
* If you cannot access the form, please send an email to community.manager at xenproject.org requesting that you need wiki access ('''important:''' from March 5 to 10 please CC Russell dot Pavlicek at xenproject dot org) with your user name.}}<br />
{{Anchor|Request}}<br />
<br />
=== Request invitation ===<br />
<br />
# Add your name and org here - optionally you may also want to state the hotel you are staying at<br />
# Andrew Cooper (Citrix, x86 Maintainer)<br />
<br />
=== Confirmed attendees ===<br />
{{InfoLeft|Important note:<br />
* We have a maximum of 50 spaces<br />
* The cut-off for registration is '''April the 12th''', as we need to organise transport from the hotel, food, security passes, etc.<br />
}}<br />
<br />
If you are a maintainer or otherwise known in the Xen Project community please add your name below, if you want you can share your hotel, whether you are planning to attend the social event and whether you will use the bus.<br />
<br />
# Lars Kurth, Citrix - staying at Sheraton Shanghai Hongqiao Hotel, attending evening social event {{Tick}}, will use bus {{Tick}}<br />
# Paul Durrant, Citrix<br />
# Jan Beulich, SUSE<br />
# Gui Jianfeng, Fujitsu<br />
# Wen Congyang, Fujitsu<br />
# Yang Hongyang, Fujitsu<br />
# Yang Zhang, Intel<br />
# Wei Wang, Intel<br />
# Liang Li, Intel<br />
# Tianyu Lan, Intel<br />
# Guangrong Xiao, Intel<br />
# Feng Wu, Intel<br />
# Chao Peng, Intel<br />
# Kai Huang, Intel<br />
# Eddie Dong, Intel<br />
# Kevin Tian, Intel<br />
# Yu Zhang, Intel<br />
# Yulei Zhang, Intel<br />
# Xiao Zheng, Intel<br />
# Ping Gao, Intel<br />
# Hongbo Wang, Intel<br />
<br />
[[Category:Project]]<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/Hackathon/April2015&diff=14504Archived/Hackathon/April20152015-03-06T23:38:43Z<p>Andyhhp: /* Request invitation */</p>
<hr />
<div>{{TODO|<br />
* Add more information on how to get from the hotels to some key sights in Shanghai using public transport (do by week of March 16)<br />
* Finalise time-table and bus pick-up with times (do by week of March 16)<br />
* Provide details on what to do when arriving at Intel (do by week of March 16)<br />
}}<br />
<br />
== When and Where ? ==<br />
<br />
=== Intel Shanghai, April 28-29 ===<br />
Intel will be hosting this years Xen Project Hackathon on April 28-29, 2015 at their [http://wikimapia.org/17649474/Intel-Zizhu-Campus Shanghai Site]. <br />
<br />
We will start at 9AM and finish at 5PM each day. '''There will also be an evening social event on April 28th : more details will follow.'''<br />
<br />
Address in English:<br />
: Intel Asia-Pacific Research and Development Ltd. <br />
: No. 880, Zixing Road<br />
: Shanghai Zizhu Science Park, <br />
: Min Hang District<br />
: Shanghai (200241)<br />
<br />
Address in Chinese:<br />
: 闵行区紫竹科学园区紫星路880号<br />
<br />
: Tel: 86-21-61165000<br />
<br />
'''[https://www.google.co.uk/maps/place/intel/@31.0233092,121.4515338,16z/data=!4m6!1m3!3m2!1s0x0000000000000000:0x2c789dc6a32a909d!2sintel!3m1!1s0x0000000000000000:0x2c789dc6a32a909d Check out the event location on the map]'''<br />
<br />
=== Schedule ===<br />
<br />
==== April 28th ====<br />
<br />
<pre><br />
8:45 - 9:30 Registration (Breakfast will not be provided)<br />
9:30 - 9:45 Welcome<br />
9:45 - 10:30 Scheduling<br />
10:30 - 11:30 Sessions 1<br />
11:30 - 12:30 Sessions 2<br />
12:30 - 13:30 Lunch<br />
13:30 - 14:30 Sessions 3<br />
14:30 - 15:30 Sessions 4<br />
15:30 - 16:00 Break <br />
16:00 - 17:00 Sessions 4<br />
17:00 - 17:30 Plenary<br />
</pre><br />
<br />
==== April 29th ====<br />
<pre><br />
9:00 - 9:45 Arrival<br />
9:45 - 10:15 Scheduling<br />
10:15 - 11:30 Sessions 1<br />
11:30 - 12:30 Sessions 2<br />
12:30 - 13:30 Lunch<br />
13:30 - 14:30 Sessions 3<br />
14:30 - 15:30 Sessions 4<br />
15:30 - 16:00 Break <br />
16:00 - 16:45 Plenary: Share achievements<br />
16:45 - 17:00 Closing<br />
</pre><br />
<br />
=== Recommended Hotel Options ===<br />
We will be organising a bus from and to one of the hotels below. They are all within walking distance from each other. More details will follow.<br />
<br />
==== Sheraton Shanghai Hongqiao Hotel ====<br />
[http://www.starwoodhotels.com/sheraton/property/overview/index.html?propertyID=1056&language=en_US Booking Information] and maps ([https://www.google.co.uk/maps/search/Sheraton+Shanghai+Hongqiao+Hotel/@31.203639,121.405572,17z/data=!3m1!4b1 english])<br />
<br />
Cost: around USD 150 - 230 per night based on room type and availability<br />
<br />
Address:<br />
: 5 Zun Yi Nan Road<br />
: Changning District<br />
: Shanghai 200336<br />
: China<br />
<br />
Chinese Address:<br />
: 长宁区遵义南路5号(靠近世贸商城,近上海国际展览中心)上海虹桥喜来登酒店<br />
<br />
==== Renaissance Shanghai Yangtze Hotel ====<br />
[http://www.marriott.com/hotels/travel/shabr-renaissance-shanghai-yangtze-hotel/ Booking Information] and maps ([https://www.google.co.uk/maps/search/Renaissance+Shanghai+Yangtze+Hotel/@31.203148,121.405792,17z/data=!3m1!4b1 english])<br />
<br />
Cost: around USD 115 - 240 per night based on room type and availability<br />
<br />
Address:<br />
: Renaissance Shanghai Yangtze Hotel<br />
: 2099 Yan'an West Road<br />
: Changning District <br />
: Shanghai 200336 <br />
: China <br />
<br />
Chinese Address:<br />
: 扬子江万丽大酒店 长宁区延安西路 2099 号, 邮编 200336<br />
<br />
==== Jin Jiang Rainbow Hotel ====<br />
<br />
[http://www.e-rainbowhotel.com/ Booking Information] and maps ([https://www.google.co.uk/maps/place/Jin+Jiang+Rainbow+Hotel/@31.2041,121.4106,17z/data=!3m1!4b1!4m2!3m1!1s0x35b2650ded63a25d:0x71972f09d770144f english])<br />
<br />
Cost: around USD 90 - 120 per night based on room type<br />
<br />
Address: <br />
: 2000 Yan An Road (W)<br />
: Changning District <br />
: Shanghai 200336 <br />
: China <br />
<br />
Chinese Address:<br />
: 锦江虹桥宾馆 延安西路2000号<br />
<br />
=== Transport Information ===<br />
This [http://wiki.xenproject.org/mediawiki/images/9/9a/Hackathon15-maps.pdf map] shows you the relative positions of the Intel campus, recommended hotels and key sights within Shanghai.<br />
<br />
==== Buses from hotels to the Intel Campus ====<br />
We will be organising a bus service from the recommended hotels (see above) to the Intel site in the morning and the evening. Exact pick-up and return times will be published later.<br />
<br />
==== Other ways to get to the Intel Campus ====<br />
Taxi's in Shanghai are relatively cheap. You are looking at a cost of around $20-$25 for a 1-1.5 hour taxi ride of about 30-35 km's. There is no easy way to get to the Intel site by public transport. Should you chose to use a taxi or chose to stay in a different hotel to those recommended, please make sure you organise the taxi with the concierge at your hotel. Printing out a map of the Intel site's location and the address in Chinese as well as your hotel address also helps.<br />
<br />
Reference distances to the Intel site:<br />
* [http://en.wikipedia.org/wiki/The_Bund The Bund] : 38 km's - approximately 1.5 hours<br />
* [http://en.wikipedia.org/wiki/Pudong Pudong] : 40 km's - approximately 1.5 hours<br />
* Recommended hotels in Hongqiao : 27 km's - approximately 1 hour<br />
<br />
==== Getting from the airport to the Hotels and vice versa ====<br />
To get from the airport to one of the recommended hotels, you can take a taxi. It is about a 50 km drive and will take 1-1.5 hours depending on the day of time. It will cost around $25-$30. Make sure to go to the airport's taxi stand and do *not* use one of the offers for a taxi when you come out of the gate. These are normally limousine services which will cost you several times more than a regular taxi. You should also print out the name and a map of the hotel, just in case.<br />
<br />
Alternatively, you can use public transport: see [https://www.google.co.uk/maps/dir/Sheraton+Shanghai+Hongqiao+Hotel,+5+Zunyi+South+Road,+Changning,+Shanghai,+China,+200336/A%C3%A9roport+international+de+Shanghai-Pudong,+S1+Yingbin+Expressway,+Pudong,+Shanghai,+China/@31.1918368,121.5323124,12z/data=!3m1!4b1!4m14!4m13!1m5!1m1!1s0x35b2650c024cf2a5:0x195cb22c6550b990!2m2!1d121.405572!2d31.203639!1m5!1m1!1s0x35ad8fde769550c1:0xc9e41371c92c355f!2m2!1d121.808273!2d31.144344!3e3 the following map]<br />
<br />
==== Taxi's in Shanghai ====<br />
Taxi's in Shanghai are relatively cheap. For more information see [http://www.travelchinaguide.com/cityguides/shanghai/transportation/taxi.htm the Travel China Guide]<br />
<br />
=== Visa Invitation Letters ===<br />
If you require an invitation, please send an e-mail to community dot manager at xenproject dot org (important: from March 5 to 10 please send to Russell dot pavlicek at xenproject dot org). You should leave make sure that you have at least 2 weeks to organise a visa with your local Chinese Embassy after you have received the visa invitation letter. Please provide the following information:<br />
<br />
==== Personal Information ====<br />
* Name <br />
* Gender<br />
* Date of birth<br />
* Nationality<br />
* Passport number<br />
* Full name of the company which you work for<br />
* Job title<br />
<br />
==== Other Information ====<br />
* Date of arrival and leaving - note that you need a full itinerary in the visa application, but that in practice after you received the visa modifications to the schedule without notifying the Chinese Embassy is OK<br />
* State your role in the Xen Project Community<br />
* You will need to state who will bear the cost of travel to/from China and your accommodation in China<br />
<br />
We will be processing invitation letters from the first week of March. Note that you do need to provide hotel information, when you apply for a Chinese visa. General information about receiving visa's to China can be found [http://www.travelchinaguide.com/embassy/visa/require<br />
<br />
== Topics to Discuss, Code, Work on, ... at the Hackathon ==<br />
=== Instructions ===<br />
{{ambox<br />
|type=notice<br />
|text=Please use the {{Tl|Project}} template to add any discussions that you want to have at the Hackathon. Feel free to comment on discussions using {{Tl|Comment}} and your support for a specific topic - i.e. you indicate that you want to participate in this topic - by using {{Tl|Vote}} or {{Tl|VoteNo}} in the Review section of the project. To do this, use the Review section of the {{Tl|Project}}.<br />
<br />
The code will look like<br />
<br />
<pre><br />
{{project=Name<br />
...<br />
|Review=<br />
{{comment|~~~~:}} Some text/comment<br />
{{vote|~~~~}} Some explanation<br />
}}<br />
</pre><br />
Make sure you read the template documentation of {{Tl|Project}}, {{Tl|Comment}}, {{Tl|Vote}} and {{Tl|VoteNo}}. Mark unused fields of {{Tl|Project}} with {{Tl|N/A}}.<br />
}}<br />
<br />
=== Topics ===<br />
<br />
Please add topics you want to discuss in this section as described above<br />
<br />
{{project<br />
|Project=Intel Virtual Graphics<br />
|Date=March 5th 2015<br />
|Verified={{N/A}}<br />
|Contact=Paul Durrant <paul.durrant@citrix.com><br />
|Difficulty={{N/A}}<br />
|Skills={{N/A}}<br />
|Desc=<br />
Code to support virtual graphics on Intel GPUs a.k.a XenGT needs to be upstreamed<br />
|GSoc={{N/A}}<br />
}}<br />
<br />
== I want to attend ==<br />
<br />
=== Request an Invitation ===<br />
<br />
In previous years we have requested for attendees to fill out a form and request an invitation. This was overly complicated, so we will revert back to a simpler approach. Please add your name to the [[#Request|list below]]. <br />
* If you are a maintainer or otherwise a core member of the community, just add yourself to the [[#Confirmed_attendees|Confirmed Attendees]] section stating your name and <br />
* If you are '''not''' a maintainer add yourself the [[#Request|Request invitation]]. If your '''email address is not known''' in the Xen Community, please also add the name of your employer and send your e-mail address to ''community dot manager at xenproject dot org'' using "Request for Hackathon 2015 Invite" as subject line. This is important, such that we can e-mail more information to you. We will monitor this page and confirm whether we have space for you to attend.<br />
<br />
'''IMPORTANT:''' The cut-off date for registrations is '''April 12th'''.<br />
<br />
Please read the text in the warning box below: it contains more detailed instructions.<br />
<br><br />
{{WarningLeft|To edit this page and thus to '''Request an Invitation''', you '''need to be added to the wiki's editors group'''. To be added to that group: <br />
* If you do not have a wiki account, please create one by using [[Special:UserLogin|this link]]. Write down your '''user name''' (we cannot look up user names from e-mail addresses) <br />
* Please [http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html fill out this form] (note: this form does not work in China) <br />
* If you cannot access the form, please send an email to community.manager at xenproject.org requesting that you need wiki access ('''important:''' from March 5 to 10 please CC Russell dot Pavlicek at xenproject dot org) with your user name.}}<br />
{{Anchor|Request}}<br />
<br />
=== Request invitation ===<br />
<br />
# Add your name and org here - optionally you may also want to state the hotel you are staying at<br />
Andrew Cooper (Citrix, x86 Maintainer)<br />
<br />
=== Confirmed attendees ===<br />
{{InfoLeft|Important note:<br />
* We have a maximum of 50 spaces<br />
* The cut-off for registration is '''April the 12th''', as we need to organise transport from the hotel, food, security passes, etc.<br />
}}<br />
<br />
If you are a maintainer or otherwise known in the Xen Project community please add your name below, if you want you can share your hotel, whether you are planning to attend the social event and whether you will use the bus.<br />
<br />
# Lars Kurth, Citrix - staying at Sheraton Shanghai Hongqiao Hotel, attending evening social event {{Tick}}, will use bus {{Tick}}<br />
# Paul Durrant, Citrix<br />
# Jan Beulich, SUSE<br />
# Gui Jianfeng, Fujitsu<br />
# Wen Congyang, Fujitsu<br />
# Yang Hongyang, Fujitsu<br />
# Yang Zhang, Intel<br />
# Wei Wang, Intel<br />
# Liang Li, Intel<br />
# Tianyu Lan, Intel<br />
# Guangrong Xiao, Intel<br />
# Feng Wu, Intel<br />
# Chao Peng, Intel<br />
# Kai Huang, Intel<br />
# Eddie Dong, Intel<br />
# Kevin Tian, Intel<br />
# Yu Zhang, Intel<br />
# Yulei Zhang, Intel<br />
# Xiao Zheng, Intel<br />
# Ping Gao, Intel<br />
# Hongbo Wang, Intel<br />
<br />
[[Category:Project]]<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/GSoc_2014&diff=10643Archived/GSoc 20142014-02-26T10:49:12Z<p>Andyhhp: </p>
<hr />
<div>__TOC__<br />
<br />
The Xen Project is a Linux Foundation collaborative project that develops the <br />
* Xen Hypervisor (for x86 and ARM)<br />
* The XAPI toolstack<br />
* Mirage OS<br />
The project also has excellent relationships with its upstreams (Linux Kernel, the BSDs, QEMU and other projects) and upstreams such as Linux distributions. This is reflected in the project list, which contains many interesting cross-project development projects for students.<br />
<br />
== GSoC and Xen ==<br />
This page is used to list project ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code (GSOC) 2014]. <br />
<br />
=== Key GSoC resources ===<br />
Google Summer of Code 2014 is On (see [http://google-opensource.blogspot.com/2013/10/google-code-in-2013-and-google-summer.html]). The Xen Project has applied as a Mentoring Organization. Stay posted.<br />
<br />
* [http://google-opensource.blogspot.com/2013/10/google-code-in-2013-and-google-summer.html Google Code-in 2013 and Google Summer of Code 2014 are on GSoC announcement]<br />
* [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 GSoC Homepage]<br />
<br />
=== Finding a project that fits you ===<br />
This page lists Xen Project development projects for GSoC that can be picked up by anyone! If you're interesting in hacking Xen Project code and want to become a part of our friendly developer community this is the place to start! Ready for the challenge?<br />
<br />
'''To work on a project:'''<br />
* Find a project that looks interesting (or a bug if you want to start with something simple)<br />
* Send an email to the relevant [http://www.xenproject.org/help/mailing-list.html mailing list] (see '''Developer Mailing Lists''') and let us know if you are interested in starting to work or applying on a specific project.<br />
* Post your ideas, questions, RFCs to the relevant [http://www.xenproject.org/help/mailing-list.html mailing list] sooner than later so you can get comments and feedback. <br />
<br />
'''You have your own project idea: no problem!'''<br />
* If you have your own project idea, outline what you are trying to do on the mailing list. If you know the right list, post your project idea on [http://www.xenproject.org/help/mailing-list.html mailing list]. Failing that post on xen-devel and we can redirect you to the right list. Make sure you add '''GSoC 2014''' to the subject line.<br />
<br />
'''It is a good idea to ...'''<br><br />
The Xen Project has also participated in the Gnome Outreach Program for Women (OPW) in the past. One of the things we learned by participating in OPW is that you will be more successful, happier and get more out of participating in student programs such as GSoC, if you do a bit of prep-work before writing an application. Here is some stuff you can do:<br />
* Contact your mentor early and get to know him or her<br />
* If the Xen Project is accepted into GSoC, start hanging out on our IRC channel. You can use the #xen-opw IRC channel on freenode.net for now (if accepted, we will create a GSoC channel)<br />
* You may want to ask the mentor for a couple of small bitesize work-items (such as reviewing someones patch, a bitesize bug, ...) and start communicating on the relevant [http://www.xenproject.org/help/mailing-list.html mailing list]. That helps you become familiar with our development process, the mentor and other community members and will help you chose the right project and help you decide whether the Xen project is for you.<br />
* Note that quite a few Xen maintainers used to be GSoC students once. Feel free to ask community dot manager at xenproject dot org to put you in touch with them if you have questions about their experience.<br />
* Any work you submit before applying for a project should be based on xen-unstable development tree, if the project is Xen Hypervisor and/or tools related. Linux kernel related patches should be based on upstream kernel.org Linux git tree (latest version). XAPI and Mirage OS patches should be based on the right codeline too. Check out the '''navigation by audience''' section on the left to find resources.<br />
<br />
==== More resources ====<br />
Quick links to changelogs of the various Xen related repositories/trees: Please see [[XenRepositories]] wiki page!<br />
<br />
Before to submit patches, please look at [[Submitting Xen Patches]] wiki page and the relevant [http://www.xenproject.org/developers/teams.html Xen Project team page]. This will contain more information.<br />
<br />
If you have new ideas, suggestions or development plans let us know and we'll update this list!<br />
<br />
=== Aspiring Students ===<br />
* Please contact the mentor and CC the most appropriate mailing list<br />
* Get a bite-size task from the mentor before the application starts<br />
* If you feel comfortable with an idea, please put your name to an idea using the following format<br />
<pre><br />
{{project<br />
...<br />
|Review=(delete as addressed)<br />
* {{Comment|~~~~:}} I am interested in this idea ... <br />
(note that you may also want to link to the e-mail thread with the mentor)<br />
</pre><br />
* You will need to request write access to the wiki by filling out [http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html this form]<br />
<br />
=== Applying for GSoC ===<br />
{{InfoLeft|Note that we will update this section when more student information on [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 melange] is available, to make it easier for you to find information. And of course assuming that the Xen Project will be accepted into GSoC.}}<br />
<br />
To apply for a project, follow the steps outlined on<br />
* [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 melange]<br />
* We do have our own [[GSoC Student Application Template]] form<br />
<br />
== List of peer reviewed Projects ==<br />
=== Domain support (PVOPS and Linux) ===<br />
<br />
{{project<br />
|Project=OVMF Compatibility Support Module support in Xen<br />
|Date=2/5/2014<br />
|Contact=Wei Liu <wei.liu2@citrix.com><br />
|GSoC=Yes<br />
|Difficulty=Medium<br />
|Desc=<br />
Currently Xen supports booting HVM guest with Seabios and OVMF UEFI firmware, but those are separate binaries. OVMF supports adding legacy BIOS blob in its binary with Compatibility Support Module support. We can try to produce single OVMF binary with Seabios in it, thus having only one firmware binary.<br />
<br />
Tasks may include:<br />
* figure out how CSM works<br />
* design / implement interface between Hvmloader and the unified binary<br />
| Outcomes=Produce a single firmware binary that can be used for legacy boot HVM guest and UEFI HVM guest<br />
| Skills=You need to have understanding of:<br />
* Firmware internal<br />
* Xen HVM booting process<br />
* Some C programming skills<br />
|Review=<br />
}}<br />
<br />
{{project<br />
|Project=Parallel xenwatch kthread<br />
|Date=01/08/2012<br />
|Difficulty=Low-Medium<br />
|Contact=Konrad Rzeszutek Wilk <konrad.wilk@oracle.com><br />
|Desc=<br />
<br />
Xenwatch is locked with a coarse lock. For a huge number of guests this represents a scalability issue. The need is to rewrite the xenwatch locking in order to support full scalability.<br />
|Outcomes=Expected outcome:<br />
* Have upstream patches.<br />
* benchmark report of with and without.<br />
|GSoC=Yes<br />
|Review=(delete as addressed)<br />
* {{Comment|[[User:Lars.kurth|Lars.kurth]] 15:24, 17 February 2014 (UTC):}} Konrad, maybe you can provide a pointer to the lock? Also, can you add the '''Skills''' section.<br />
}}<br />
<br />
{{project<br />
|Project=Utilize Intel QuickPath on network and block path.<br />
|Date=01/22/2013<br />
|Difficulty=High<br />
|Contact=Konrad Rzeszutek Wilk <konrad.wilk@oracle.com><br />
|Desc=The Intel QuickPath, also known as Direct Cache Access, is the chipset that sits in the PCIe subsystem in the Intel systems. It allows the PCIe subsystem to tag which PCIe writes to memory should reside in the Last Level Cache (LLC, also known as L3, which in some cases can be of 15MB or 2.5MB per CPU). This offers incredible boosts of speed - as we bypass the DIMMs and instead the CPU can process the data in the cache.<br />
<br />
Adding this component in the network or block backends can mean that we can keep the data longer in the cache and the guest can process the data right off the cache.<br />
<br />
|Skills=The basic requirement for this project is Linux kernel programming skill.<br />
The candidate for this project should be familiar with open source development workflow as it may require collaboration with several parties.<br />
<br />
|Outcomes=Expected outcome:<br />
* Have upstream patches.<br />
* benchmark report of with and without.<br />
|GSoC=Yes<br />
|Review=(delete as addressed)<br />
* {{Comment|[[User:Lars.kurth|Lars.kurth]] 15:24, 17 February 2014 (UTC):}} Konrad, this project would benefit to links to the mentioned specs and a list of the open source communities that the student may need to work with.<br />
}} <br />
<br />
{{project<br />
|Project=Enabling the 9P File System transport as a paravirt device<br />
|Date=01/20/2014<br />
|Difficulty=High<br />
|Contact=Andres Lagar-Cavilla <andres@lagarcavilla.org><br />
|GSoC=Yes<br />
|Desc=VirtIO provides a 9P FS transport, which is essentially a paravirt file system device. VMs can mount arbitrary file system hierarchies exposed by the backend. The 9P FS specification has been around for a while, while the VirtIO transport is relatively new. The project would consist of implementing a classic Xen front/back pv driver pair to provide a transport for the 9P FS Protocol.<br />
<br />
* More info: http://www.linux-kvm.org/page/9p_virtio<br />
<br />
|Skills= Required skills include knowledge of kernel hacking, file system internals. Desired skills include: understanding of Xen PV driver structure, and VirtIO.<br />
<br />
|Outcomes=Expected outcome:<br />
* LKML patches for front and back end drivers. <br />
* In particular, domain should be able to boot from the 9P FS.<br />
|Review=(delete as addressed)<br />
* {{Comment|[[User:Lars.kurth|Lars.kurth]] 15:24, 17 February 2014 (UTC):}} This project would benefit from links to the virtio specs and documents explaining how the PV protocol works.<br />
}}<br />
<br />
=== Xen Hypervisor Userspace Tools ===<br />
<br />
{{project<br />
|Project=CPU/RAM/PCI diagram tool<br />
|Date=01/30/2014<br />
|Contact=Andrew Cooper <andrew.cooper3@citrix.com><br />
|Difficulty=Moderate, to Extremely Difficult (depending on which area of the problem you choose to tackle)<br />
|Skills=Understanding of PC server hardware, Understanding of ACPI/SMBios tables, Linux scripting or kernel hacking (depending on which area of the problem you choose to tackle)<br />
|Desc=It is often useful in debugging kernel, hypervisor or performance problems to understand the bus topology of a server. This project will create a layout diagram for a server automatically using data from ACPI Tables, SMBios Tables, lspci output etc. This tool would be useful in general Linux environments including Xen and KVM based virtualisation systems.<br />
<br />
There are many avenues for extension such as labelling relevant hardware errata, performing bus throughput calculations etc.<br />
|Outcomes=A tool is created that can either run on a live Linux system or offline using captured data to produce a graphical representation of the hardware topology of the system including bus topology, hardware device locations, memory bank locations, etc. The tool would be submitted to a suitable open-source project such as the Xen hypervisor project or XCP.<br />
|GSoC=yes}}<br />
<br />
{{project<br />
|Project=KDD (Windows Debugger Stub) enhancements<br />
|Date=01/30/2014<br />
|Contact=Paul Durrant <paul.durrant@citrix.com><br />
|Difficulty=Medium<br />
|Skills=C, Kernel Debuggers, Xen, Windows<br />
|Desc=kdd is a Windows Debugger Stub for Xen hypervisor. It is OSS found under http://xenbits.xen.org/hg/xen-unstable.hg/tools/debugger/kdd<br />
kdd allows you to debug a running Windows virtual machine on Xen using standard Windows kernel debugging tools like WinDbg. kdd is an external debugger stub for the windows kernel. <br />
Windows can be debugged without enabling the debugger stub inside windows kernel by using kdd. This is important for debugging hard to reproduce problems on Windows virtual machines that may not have debugging enabled.<br />
<br />
Expected Results:<br />
# Add support for Windows 8 (x86, x64) to kdd<br />
# Add support for Windows Server 2012 to kdd<br />
# Enhance kdd to allow WinDbg to write out usable Windows memory dumps (via .dump debugger extension) for all supported versions<br />
# Produce a user guide for kdd on Xen wiki page<br />
<br />
Nice to have: Allow kdd to operate on a Windows domain checkpoint file (output of xl save for e.g.)<br />
|Outcomes=Code is submitted to xen-devel@xen.org for inclusion in the xen-unstable project.<br />
|GSoC=yes}}<br />
<br />
=== Mirage OS ===<br />
<br />
{{project<br />
|Project=Create a tiny VM for easy load testing<br />
|Date=01/30/2014<br />
|Contact=Dave Scott <''first.last''@citrix.com><br />
|Difficulty=Medium<br />
|Skills=OCaml<br />
|Desc=The Mirage OS framework (see http://xenproject.org/developers/teams/mirage-os.html, http://www.openmirage.org/) can be used to create tiny 'unikernels': entire software stacks which run directly on the Xen hypervisor. These VMs have such a small memory footprint (16 MiB or less) that many of them can be run even on relatively small hosts. The goal of this project is to create a specific unikernel that can be configured to generate a specific I/O pattern, and to create configurations that mimic the boot sequence of Linux and Windows guests. The resulting unikernel will then enable cheap system load testing.<br />
<br />
The first task is to generate an I/O trace from a VM. For this we could use 'xen-disk', a userspace Mirage application which acts as a block backend for xen guests (see http://openmirage.org/wiki/xen-synthesize-virtual-disk). Following the wiki instructions we could modify a 'file' backend to log the request timestamps, offsets, buffer lengths.<br />
<br />
The second task is to create a simple kernel based on one of the MirageOS examples (see http://github.com/mirage/mirage-skeleton). The 'block' example shows how reads and writes are done. The previously-generated log could be statically compiled into the kernel and executed to generate load.<br />
|Outcomes=1. a repository containing an 'unikernel' (see http://github.com/mirage/mirage-skeleton)<br />
2. at least 2 I/O traces, one for Windows boot and one for Linux boot (any version)<br />
|GSoC=yes}}<br />
<br />
{{project<br />
|Project=Fuzz testing Xen with Mirage<br />
|Date=28/11/2013<br />
|Contact=Anil Madhavapeddy <anil@recoil.org><br />
|Skills=OCaml, Xen<br />
|Difficulty=medium<br />
|Desc=<br />
Mirage OS (see http://xenproject.org/developers/teams/mirage-os.html, http://www.openmirage.org/) is a type-safe unikernel written in OCaml which generates highly specialised "appliance" VMs that run directly on Xen without requiring an intervening guest kernel. We would like to use the Mirage/Xen libraries to fuzz test all levels of a typical cloud toolstack. Mirage has low-level bindings for Xen hypercalls, mid-level bindings for domain management, and high-level bindings to XCP for cluster management. This project would build a QuickCheck-style fuzzing mechanism that would perform millions of random operations against a real cluster, and identify bugs with useful backtraces.<br />
<br />
The first task would be to become familiar with a specification-based testing tool like Kaputt (see http://kaputt.x9c.fr/). The second task would be to choose an interface for testing; perhaps one of the hypercall ones.<br />
[[GSoC_2013#fuzz-testing-mirage]]<br />
|Outcomes=1. a repo containing a fuzz testing tool; 2. some unexpected behaviour with a backtrace (NB it's not required that we find a critical bug, we just need to show the approach works)<br />
|GSoC=yes<br />
}}<br />
<br />
{{project<br />
|Project=Mirage OS cloud API support<br />
|Date=28/11/2013<br />
|Contact=Anil Madhavapeddy <anil@recoil.org><br />
|Skills=OCaml<br />
|Difficulty=medium<br />
|Desc=<br />
MirageOS (see http://xenproject.org/developers/teams/mirage-os.html, http://www.openmirage.org/) is a type-safe unikernel written in OCaml which generates highly specialised "appliance" VMs that run directly on Xen without requiring an intervening kernel. A MirageOS application typically runs via several communicating kernel instances on the cloud. Today these instances are difficult to manage; we would like to explore strategies for managing these distributed computations using common public cloud APIs such as those exposed by Amazon EC2 and Rackspace.<br />
<br />
First we need to create pure OCaml API bindings for (e.g.) EC2 and Rackspace (purity is needed to ensure portability). These API bindings can then be used to provide operating-system-level abstractions to the unikernels. For example, a traditional VM might hotplug a vCPU; while a MirageOS application would request a "VM create" using the cloud API and "connect" the new instance to the existing network. We should be able to spin up 1000s of "CPUs" by using such APIs in a cluster environment.<br />
<br />
As well as helping Xen/Mirage, the public cloud API bindings will be very useful to other people in other contexts-- a nice side-effect.<br />
|Outcomes=1. one or more public cloud API bindings plus examples, in a standalone repo on github; 2. an example mirage app which uses these APIs to spin up a new VM<br />
|GSoC=yes<br />
}}<br />
<br />
{{project<br />
|Project=Mirage OS web stack testing<br />
|Date=25/02/2014<br />
|Contact=Anil Madhavapeddy <anil@recoil.org><br />
|Skills=OCaml, shell scripting<br />
|Difficulty=medium<br />
|Desc=<br />
MirageOS has an emerging web toolstack that's broken up as a series of libraries -- for example, Cohttp, Uri, Cow, Ipaddr, RSS and Cowabloga. This project will get you familiar with them by building a protocol testing framework that can generate traffic using off-the-shelf tools such as httperf, and evaluate the results vs applications such as Apache or Nginx.<br />
<br />
|Outcomes=1. a test harness for HTTP; 2. some results of the evaluation using the test harness<br />
|GSoC=yes<br />
}}<br />
<br />
== List of projects that need more work ==<br />
{{Anchor|Unreviewed Project Ideas}}<br />
<br />
=== Domain support (PVOPS and Linux) ===<br />
{{project<br />
|Project=Implement Xen PVSCSI support in xl/libxl toolstack<br />
|Date=01/12/2012<br />
|Contact=Pasi Karkkainen <pasik@iki.fi><br />
|GSoC=Yes<br />
|Desc=<br />
xl/libxl does not currently support Xen PVSCSI functionality. Port the feature from xm/xend to xl/libxl. Necessary operations include:<br />
* Task 1: Implement PVSCSI in xl/libxl, make it functionally equivalent to xm/xend.<br />
* Send to xen-devel mailinglist for review, comments.<br />
* Fix any upcoming issues.<br />
* Repeat until merged to xen-unstable.<br />
* See above for PVSCSI drivers for dom0/domU.<br />
* Xen PVSCSI supports both PV domUs and HVM guests with PV drivers.<br />
* More info: http://wiki.xen.org/xenwiki/XenPVSCSI<br />
{{Comment|[[User:Lars.kurth|Lars.kurth]] 14:14, 23 January 2013 (UTC):}} Should be suitable, but desc needs. Rate in terms of challenges, size and skill. Also kernel functionality is not yet upstreamed. Maybe Suse kernel.<br />
}}<br />
<br />
{{project<br />
|Project=Implement Xen PVUSB support in xl/libxl toolstack<br />
|Date=01/12/2012<br />
|Contact=Pasi Karkkainen <pasik@iki.fi><br />
|GSoC=Yes<br />
|Desc=<br />
xl/libxl does not currently support Xen PVUSB functionality. Port the feature from xm/xend to xl/libxl. Necessary operations include:<br />
* Task 1: Implement PVUSB in xl/libxl, make it functionally equivalent to xm/xend.<br />
* Send to xen-devel mailinglist for review, comments.<br />
* Fix any upcoming issues.<br />
* Repeat until merged to xen-unstable.<br />
* See above for PVUSB drivers for dom0/domU.<br />
* Xen PVUSB supports both PV domUs and HVM guests with PV drivers.<br />
* More info: http://wiki.xen.org/xenwiki/XenUSBPassthrough<br />
{{Comment|[[User:Lars.kurth|Lars.kurth]] 14:14, 23 January 2013 (UTC):}} Should be suitable, but desc needs. Rate in terms of challenges, size and skill. Also kernel functionality is not yet upstreamed. Maybe Suse kernel.<br />
}}<br />
<br />
<br />
{{project<br />
|Project=Block backend/frontend improvements<br />
|Date=01/01/2013<br />
|Difficulty=Medium<br />
|Contact=Konrad Rzeszutek Wilk <konrad.wilk@oracle.com><br />
|Desc=<br />
Blkback requires a number of improvements, some of them being:<br />
* Multiple disks in a guest cause contention in the global pool of pages.<br />
* There is only one ring page and with SSDs nowadays we should make this larger, implementing some multi-page support.<br />
* With multi-page it becomes apparent that the segment size ends up wasting a bit of space on the ring. BSD folks fixed that by negotiating a new parameter to utilize the full size of the ring. Intel had an idea for descriptor page.<br />
* Add DIF/DIX support [http://oss.oracle.com/~mkp/docs/lpc08-data-integrity.pdf] for T10 PI (Protection Information), to support data integrity fields and checksums.<br />
* Further perf evaluation needs to be done to see how it behaves under high load.<br />
* Further discussion and issues outlined in http://lists.xen.org/archives/html/xen-devel/2012-12/msg01346.html and https://docs.google.com/document/d/1Vh5T8Z3Tx3sUEhVB0DnNDKBNiqB_ZA8Z5YVqAsCIjuI<br />
<br />
|GSoC=Yes, but we would have to chop them into smaller chunks working with the applicant<br />
}}<br />
<br />
=== Xen Hypervisor ===<br />
<br />
{{project<br />
|Project=Introducing PowerClamp-like driver for Xen<br />
|Date=01/22/2013<br />
|Contact=George Dunlap <george.dunlap@eu.citrix.com><br />
|Desc=<br />
PowerClamp was introduced to Linux in late 2012 in order to allow users to set a system-wide maximum<br />
power usage limit. This is particularly useful for data centers, where there may be a need to<br />
reduce power consumption based on availability of electricity or cooling. A [http://lwn.net/Articles/528124/ more complete writeup]<br />
is available at LWN.<br />
<br />
These same arguments apply to Xen. The purpose of this project would be to implement a similar functionality in Xen,<br />
and to make it interface as well as possible with the Linux PowerClamp tools, so that the same tools could be used<br />
for both. [[GSoC_2013#powerclamp-for-xen]]<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=HVM per-event-channel interrupts<br />
|Date=01/30/2013<br />
|Contact=Paul Durrant <paul.durrant@citrix.com><br />
|Skills=C, some prior knowledge of Xen useful<br />
|Desc=Windows PV drivers currently have to multiplex all event channel processing onto a single interrupt which is registered with Xen using the HVM_PARAM_CALLBACK_IRQ parameter. This results in a lack of scalability when multiple event channels are heavily used, such as when multiple VIFs in the VM as simultaneously under load.<br />
<br />
Goal: Modify Xen to allow each event channel to be bound to a separate interrupt (the association being controlled by the PV drivers in the guest) to allow separate event channel interrupts to be handled by separate vCPUs. There should be no modifications required to the guest OS interrupt logic to support this (as there is with the current Linux PV-on-HVM code) as this will not be possible with a Windows guest.<br />
|Outcomes=Code is submitted to xen-devel@xen.org for inclusion in xen-unstable<br />
|GSoC=yes}}<br />
<br />
=== Xen Hypervisor Userspace Tools ===<br />
{{project<br />
|Project=Refactor Linux hotplug scripts<br />
|Date=15/11/2012<br />
|Contact=Roger Pau Monné <[mailto:roger.pau@citrix.com roger.pau@citrix.com]><br />
|Desc=<br />
Current Linux hotplug scripts are all entangled, which makes them really difficult to understand or modify. The reason of hotplug scripts is to give end-users the chance to "easily" support different configuration for Xen devices.<br />
<br />
Linux hotplug scripts should be analized, providing a good description of what each hotplug script is doing. After this, scripts should be cleaned, putting common pieces of code in shared files across all scripts. A Coding style should be applied to all of them when the refactoring is finished.<br />
<br />
[[GSoC_2013#linux-hotplug-scripts]]<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=XL to XCP VM motion<br />
|Date=15/11/12<br />
|Contact=[mailto:ian.campbell@citrix.com Ian Campbell]<br />
|Desc=Currently [[XL|xl]] (the toolstack supplied alongside Xen) and [[XAPI|xapi]] (the XCP toolstack) have very different concepts about domain configuration, disk image storage etc. In the XCP model domain configuration is persistent and stored in a data base while under xl domain configuration is written in configuration files. Likewise disk images are stored as VDIs in Storage Repositories while under xl disk images are simply files or devices in the dom0 filesystem. For more information on xl see [[XL]]. For more information on XCP see [[XCP Overview]].<br />
<br />
This project is to produce one or more command-line tools which support migrating VMs between these toolstacks.<br />
<br />
One tool should be provided which takes an xl configuration file and details of an XCP pool. Using the XenAPI XML/RPC interface It should create a VM in the pool with a close approximation of the same configuration and stream the configured disk image into a selected Storage Repository.<br />
<br />
A second tool should be provided which performs the opposite operation, i.e. give a reference to a VM residing in an XCP pool it should produce an XL compatible configuration file and stream the disk image(s) our of Xapi into a suitable format.<br />
<br />
These tools could be reasonably bundled as part of either toolstack and by implication could be written in either C, Ocaml or some other suitable language.<br />
<br />
The tool need not operate on a live VM but that could be considered a stretch goal.<br />
<br />
An acceptable alternative to the proposed implementation would be to implement a tool which converts between a commonly used VM container format which is supported by XCP (perhaps [http://en.wikipedia.org/wiki/Open_Virtualization_Format OVF] or similar) and the xl toolstack configuration file and disk image formats.<br />
<br />
[[GSoC_2013#xl-to-xcp-vm-motion]]<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=VM Snapshots<br />
|Date=16/01/2013<br />
|Contact=<[mailto:stefano.stabellini@eu.citrix.com Stefano Stabellini]><br />
|Desc=Although xl is capable of saving and restoring a running VM, it is not currently possible to create a snapshot of the disk together with the rest of the VM.<br />
<br />
QEMU is capable of creating, listing and deleting disk snapshots on QCOW2 and QED files, so even today, issuing the right commands via the QEMU monitor, it is possible to create disk snapshots of a running Xen VM. xl and libxl don't have any knowledge of these snapshots, don't know how to create, list or delete them.<br />
<br />
This project is about implementing disk snapshots support in libxl, using the QMP protocol to issue commands to QEMU. Users should be able to manage the entire life-cycle of their disk snapshots via xl. The candidate should also explore ways to integrate disk snapshots into the regular Xen save/restore mechanisms and provide a solid implementation for xl/libxl.<br />
<br />
[[GSoC_2013#vm-snapshots]]<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=Allowing guests to boot with a passed-through GPU as the primary display<br />
|Date=01/22/2013<br />
|Contact=George Dunlap <george.dunlap@eu.citrix.com><br />
|Desc=<br />
One of the primary drivers of Xen in the "consumer market" of the open-source world is the ability to<br />
pass through GPUs to guests -- allowing people to run Linux as their main desktop but easily play <br />
games requiring proprietary operating systems without rebooting.<br />
<br />
GPUs can be easily passed through to guests as secondary displays, but as of yet cannot be passed<br />
through as primary displays. The main reason is the lack of ability to load the VGA BIOS from the card into the guest.<br />
<br />
The purpose of this project would be to allow HVM guests to load the physical card's VGA bios, so that the guest can<br />
boot with it as the primary display.<br />
<br />
[[GSoC_2013#gpu-passthrough]]<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=Advanced Scheduling Parameters<br />
|Date=01/22/2013<br />
|Contact=George Dunlap <george.dunlap@eu.citrix.com><br />
|Desc=<br />
The credit scheduler provides a range of "knobs" to control guest behavior, including CPU weight and caps. However,<br />
a number of users have requested the ability to encode more advanced scheduling logic. For instance, "Let this VM max out for 5 minutes out of any given hour; but after that, impose a cap of 20%, so that even if the system is idle he can't an unlimited amount of CPU power without paying for a higher level of service."<br />
<br />
This is too coarse-grained to do inside the hypervisor; a user-space tool would be sufficient. The goal of this project would<br />
be to come up with a good way for admins to support these kinds of complex policies in a simple and robust way.<br />
<br />
|GSoC=Yes<br />
}}<br />
<br />
{{project<br />
|Project=Lazy restore using memory paging<br />
|Date=01/20/2014<br />
|Contact=Andres Lagar-Cavilla <andres@lagarcavilla.org><br />
|Difficulty=Medium<br />
|GSoC=Yes<br />
|Desc=VM Save/restore results in a boatload of IO and non-trivial downtime as the entire memory footprint of a VM is read from IO.<br />
<br />
Xen memory paging support in x86 is now mature enough to allow for lazy restore, whereby the footprint of a VM is backfilled while the VM executes. If the VM hits a page not yet present, it is eagerly paged in.<br />
<br />
There has been some concern recently about the lack of docs and/or mature tools that use xen-paging. This is a good way to address the problem.<br />
<br />
|Skills= A good understanding of save/restore, and virtualized memory management (e.g. EPT, shadow page tables, etc). In principle the entire project can be implemented in user-space C code, but it may be the case that new hypercalls are needed for performance reasons.<br />
<br />
|Outcomes=Expected outcome:<br />
* Mainline patches for libxc and libxl<br />
}}<br />
<br />
{{project<br />
|Project=CPUID Programming for Humans<br />
|Date=02/04/2014<br />
|Contact=Andres Lagar-Cavilla <andres@lagarcavilla.org><br />
|Difficulty=Easy<br />
|GSoC=Yes<br />
|Desc=When creating a VM, a policy is applied to mask certain CPUID features. Right now it's black magic.<br />
<br />
The KVM stack has done an excellent job of making this human-useable, and understandable.<br />
<br />
For example, in a qemu-kvm command-line you may encounter:<br />
<br />
-cpu SandyBridge,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme<br />
<br />
And in <qemu>/target-i386.c you find a fairly comprehensive description of x86 processor models, what CPUID features are inherent, and what CPUID feature each of these symbolic flags enables.<br />
<br />
In the Xen world, there is a libxc interface to do the same, although it's all hex and register driven. It's effective, yet horrible to use.<br />
<br />
An ideal outcome would have libxl config files and command line absorb a similarly human-friendly description of the CPUID features a user wishes for the VM, and interface appropriately with libxl. Further, autodetection of best CPUID shuold yield a human-readable output to be able to easily understand what the VM thinks about its processor.<br />
<br />
Finally, interfacing with libvirt should be carefully considered.<br />
<br />
CPUID management is crucial in a heterogeneous cluster where migrations and save restore require careful processor feature selection to avoid blow-ups.<br />
<br />
|Skills= A good understanding of C user-land programming, and the ability to dive into qemu/libvirt (for reference code and integration), as well as libxc and libxl (for implementation).<br />
<br />
|Outcomes=Expected outcome:<br />
* Mainline patches for libxl<br />
}}<br />
<br />
=== XAPI ===<br />
<br />
{{project<br />
|Project=DRBD Integration<br />
|Date=07/01/2013<br />
|Contact=John Morris <john@zultron.com><br />
|Desc=<br />
DRBD is potentially a great addition to the other high-availability features in XenAPI. An architecture of as few as two Dom0s with DRBD mirrored local storage is an inexpensive minimal HA configuration enabling live migration of VMs between physical hosts and providing failover in case of disk failure, and eliminates the need for external storage. This setup can be used in small shop or hobbyist environments, or could be used as a basic unit in a much larger scalable architecture.<br />
<br />
Existing attempts at integrating DRBD sit below the SM layer and thus do not enable one VBD per DRBD device. They also suffer from a split-brain situation that could be avoided by controlling active/standby status from XenAPI.<br />
<br />
DRBD should be implemented as a new SR type on top of LVM. The tools for managing DRBD devices need to be built into storage management, along with the logic for switching the active and standby nodes.<br />
}}<br />
<br />
== New Project Ideas ==<br />
{{Anchor|New_Project_Ideas}}<br />
'''Please add new project ideas here, following '''<br />
<br />
== Conventions for Projects and Project Mentors == <br />
=== Rules and Advice for Adding Ideas ===<br />
* Be creative<br />
* Add projects into [[#New_Project_Ideas|New Project Ideas]] or improve projects in [[#Unreviewed Project Ideas|Project Ideas that Need Review or more work]] through review comments.<br />
* Use the {{tl|GSoC Project}} template to encode ideas on this page. Please read the [[Template:GSoC Project|Template Documentation]] before you do so.<br />
* Be specific: what do you want to be implemented; if at all possible provide an indication of size and complexity as described above to make it easier for a student to choose ideas<br />
* Check that the project meets the [[#Goals|GSoC Program Goals]]<br />
* If you are willing to mentors those ideas, add your name and email to the idea.<br />
* Aspiring mentors should introduce themselves on the most appropriate Xen Project mailing list<br />
<br />
=== Peer Review Goals ===<br />
We strongly recommend and invite project proposers and project mentors to review each others proposals. When you review, please look out for<br />
* Can a student get going and started with the information in the project description<br />
* Are any unstated assumptions in the proposal, is there undefined terminology, etc. in the proposal <br />
* Can the project completed in 3 months (assume that one month is needed for preparation)<br />
* {{Anchor|Goals}}Does the project meet Google Summer of Code goals, which are<br />
** Create and release open source code for the benefit of all<br />
** Inspire young developers to begin participating in open source development<br />
** Help open source projects identify and bring in new developers and committers <br />
** Provide students the opportunity to do work related to their academic pursuits (think "flip bits, not burgers")<br />
** Give students more exposure to real-world software development scenarios (e.g., distributed development, software licensing questions, mailing-list etiquette)<br />
<br />
=== Peer Review Conventions ===<br />
The {{tl|GSoC Project}} template used to encode GSoC projects, contains some review functionality. Please read the [[Template:GSoC Project|Template Documentation]] before you add a template, also please use the conventions below to make comments.<br />
<br />
<pre><br />
|Review=(delete as addressed)<br />
* {{Comment|~~~~:}} Comment 1<br />
* {{Comment|~~~~:}} Comment 2<br />
</pre><br />
<br />
=== Choosing Projects ===<br />
We have a bi-weekly mentor meeting overlooked by our program management team, which are a core team of 2-3 mentors and a program administrator. This group will work with mentors to ensure that project proposals are of good quality and whether mentors are engaging with the program management team and students in the weeks before the application period ends. <br />
<br />
[[Category:GSoC]]<br />
[[Category:Developers]]<br />
[[Category:Index]]<br />
[[Category:Project]]<br />
[[Category:Transient]] <!-- as if not maintained it becomes stale --></div>Andyhhphttps://wiki.xenproject.org/index.php?title=Submitting_Xen_Project_Patches&diff=6614Submitting Xen Project Patches2013-03-01T11:50:03Z<p>Andyhhp: s/xensource.com/xen.org/</p>
<hr />
<div>== How To Generate and Submit a Patch to Xen ==<br />
<br />
Xen uses [http://www.selenic.com/mercurial/wiki/index.cgi Mercurial] for its source code management. The current Xen development tree is at http://xenbits.xen.org/xen-unstable.hg. An excellent [http://www.selenic.com/mercurial/wiki/index.cgi/Tutorial tutorial] is here. Download and install mercurial to your system.<br />
<br />
=== Generating a patch ===<br />
----<br />
Here's a recommendation on how to send patches, as suggested by the Xen maintainers.<br />
<br />
To begin, configure Mercurial by making the following additions to your <code>~/.hgrc</code>:<br />
<br />
* Enable the [http://mercurial.selenic.com/wiki/MqExtension Patchqueue extension]<br />
<br />
<pre><br />
[extensions]<br />
mq=<br />
</pre><br />
<br />
<br />
* Show function names in patch hunk headers (which makes patches easier to review).<br />
<br />
<pre><br />
[diff]<br />
showfunc=True<br />
</pre><br />
<br />
<br />
When you want to make a patch, create a patch on the patch queue:<br />
<br />
<pre><br />
hg qnew patch01.diff<br />
</pre><br />
<br />
<br />
Then edit the source files you want to change. You can see which files have changed by using <code>hg status</code>.<br />
<br />
When you're done editing, save your changes into the patch, and add a description. The easiest way to add a description is to use the <code>-e</code> option to <code>hg qrefresh</code>:<br />
<br />
<pre><br />
hg qrefresh -e<br />
</pre><br />
<br />
<br />
<pre><br />
foobar: Add a new trondle calls<br />
<br />
Add a some new trondle calls to the foobar interface to support<br />
the new zot feature.<br />
<br />
Signed-off-by: Joe Smith <joe.smith@citrix.com><br />
</pre><br />
<br />
Alternately, after refreshing the patch with <code>hg qrefresh</code>, you can edit the files directly in <code>.hg/patches/</code>. Everything above the line starting with <code>diff</code> will be ignored:<br />
<br />
<pre><br />
foobar: Add a new trondle calls<br />
<br />
Add a some new trondle calls to the foobar interface to support<br />
the new zot feature.<br />
<br />
Signed-off-by: Joe Smith <joe.smith@citrix.com><br />
<br />
diff -r 63531e640828 tools/libxc/Makefile<br />
--- a/tools/libxc/Makefile Mon Dec 07 17:01:11 2009 +0000<br />
+++ b/tools/libxc/Makefile Mon Dec 21 11:45:00 2009 +0000<br />
...<br />
</pre><br />
<br />
Repeat as necessary for all of your changes<br />
<br />
<pre><br />
hg qnew patch02.diff<br />
</pre><br />
<br />
...<br />
=== Signing off a patch ===<br />
----<br />
All patches to the Xen code base must include the the line "Signed-off-by: your_name <your_email>" at the end of the change description. This is required and indicates that you certify the patch under the "Developer's Certificate of Origin" which states:<br />
<br />
<br />
<pre><br />
Developer's Certificate of Origin 1.1<br />
<br />
By making a contribution to this project, I certify that:<br />
<br />
(a) The contribution was created in whole or in part by me and I<br />
have the right to submit it under the open source license<br />
indicated in the file; or<br />
<br />
(b) The contribution is based upon previous work that, to the best<br />
of my knowledge, is covered under an appropriate open source<br />
license and I have the right under that license to submit that<br />
work with modifications, whether created in whole or in part<br />
by me, under the same open source license (unless I am<br />
permitted to submit under a different license), as indicated<br />
in the file; or<br />
<br />
(c) The contribution was provided directly to me by some other<br />
person who certified (a), (b) or (c) and I have not modified<br />
it.<br />
<br />
(d) I understand and agree that this project and the contribution<br />
are public and that a record of the contribution (including all<br />
personal information I submit with it, including my sign-off) is<br />
maintained indefinitely and may be redistributed consistent with<br />
this project or the open source license(s) involved.<br />
</pre><br />
<br />
=== Making good patches ===<br />
----<br />
Patches, if accepted, will turn into commits in the mercurial source tree. There are three people to think about when writing the patch and the comment:<br />
* Reviewers on the mailing list, who are trying to understand what your patch does, if it's correct, and what side effects it will have.<br />
* People skimming through changesets deciding if a patch is important for them to look at for backporting, review, implications on out-of-tree patches, &c.<br />
* Someone in the perhaps distant future, who is trying to understand why the code is the way it is.<br />
Try to make your patches with all of these people in mind. To do this:<br />
==== Break down your patches ====<br />
* Each patch should preferably do one logical thing (or one related set of things). The goal is for reviewers to understand the change that each patch is making with a minimum of effort.<br />
* No patch should ever break existing functionality.<br />
* Never fix bugs in one of your patches by changing it in a later patch; go back and change the patch with the bug in it.<br />
* Don't mix clean-up patches (which make things look prettier or move things round but don't change functionality) with code-change patches. Clean-up patches should be clearly marked as having no functional changes.<br />
==== Write a good description for each patch ====<br />
* If you're using mercurial queues, as described above, use <code>hg qrefresh -e</code> to edit the description, or edit the patch files directly in <code>.hg/patches/</code>. NB that if you edit the files directly, you'll have to <code>hg qpop -a ; hg qpush -a</code> to get the description into mercurial.<br />
* The first line the top of the patch should contain a short description of what the patch does, and hints as to what code it touches<br />
* The description should be useful for both the reviewers and people in the future trying to understand what the patch does. It can be as short as <code>Code cleanup -- no functional changes</code>, or as long as it takes to accurately describe the bug you are trying to solve or the new functionality you are introducing.<br />
* The description should be wrapped to a maximum of 80 columns.<br />
<br />
=== Sending the patches to the list ===<br />
----<br />
<br />
The xen-devel mailing list is moderated for non-subscribers. It is not mandatory to subscribe but it can help avoid this delay. It is possible to subscribe and then disable delivery in the mailman options so as to avoid moderation but not receive list traffic if that is what you would prefer.<br />
<br />
==== Mercurial Patchbomb Extension ====<br />
The most robust way to send files is by using the [http://mercurial.selenic.com/wiki/PatchbombExtension Mercurial Patchbomb extension]. <br />
<br />
To do this, first set up the Patchbomb extension in your <code>.hgrc</code> file:<br />
<br />
<pre><br />
[extensions]<br />
hgext.patchbomb =<br />
<br />
[email]<br />
method = smtp<br />
from = Your Name <your.email@your-domain.com><br />
cc = your.email@your-domain.com<br />
<br />
[smtp]<br />
host = mail.yourdomain.com<br />
port = 25<br />
</pre><br />
<br />
Then check to make sure you have the right patches to be submitted by using <code>hg out</code>:<br />
<br />
<pre><br />
$ hg out<br />
comparing with http://hg/xen-unstable.hg<br />
searching for changes<br />
changeset: 21165:2631707c54b3<br />
tag: qbase<br />
tag: add-trondle-call.diff<br />
user: Joe Smith <joe.smith@citrix.com><br />
date: Wed Apr 14 11:16:58 2010 +0100<br />
summary: foobar: Add new trondle calls<br />
<br />
...<br />
</pre><br />
<br />
Next you need to figure out who (if anyone) you should copy the patches to. To do this you should consult the <code>MAINTAINERS</code> file at the top of the Xen source tree. If there is a specific maintainer listed for the area of the code you are modifying then it is best to copy the patches to them. You should always send patches to the xen-devel@lists.xen.org mailing list as well.<br />
<br />
Once you're sure you have the proper series of patches and know who you are sending it to then you're ready to use the patchbomb tool:<br />
<br />
<pre><br />
$ hg email -o --plain --to xen-devel@lists.xen.org --cc the.maintainer@example.com<br />
</pre><br />
<br />
(The <code>-o</code> option tells patchbomb to submit all outgoing patches; <code>--plain</code> removes the extraneous HG header information from the patches in the e-mails; <code>--to</code> and <code>--cc</code> say who to send the mail to.) It will ask you some questions, like this:<br />
<br />
<pre><br />
comparing with http://hg/xen-unstable.hg<br />
searching for changes<br />
This patch series consists of 5 patches.<br />
<br />
Subject: [PATCH 0 of 5]<br />
</pre><br />
<br />
Enter in a summary for the entire patch series here, and press enter. You will then be dropped into an editor, to write the text for the patch series intro e-mail. <br />
<br />
NB, emacs users: if you're running this from an emacs shell, this can get tricky, since all of the editors it wants to offer you require a terminal. Best to run it in a normal terminal window somewhere.<br />
<br />
Tada! You should shortly see your patch series appear in your inbox, and on the xen-devel mailing list (depending on how you've configured it.)<br />
<br />
Other useful options include:<br />
* <code>-n</code> will go through all the motions of preparing the patchbomb, but instead of sending a mail, will just output the mails it would have sent. Useful for testing.<br />
* <code>-d</code> produces a "diffstat", showing lines added and removed for each file. It asks a lot more questions, though.<br />
* <code>-s</code> & <code>--desc</code> allow you to specify a subject line and body respectively for the summary email.<br />
* <code>firstpatch:lastpatch</code> allows you to name a specific range of patches to send and can be used instead of the <code>-o</code> option.<br />
<br />
==== Sending Patches Manually ====<br />
<br />
It is strongly recommended to use the Mercurial patchbomb extension discussed above. However it is possible to send a patch manually using your regular mail client. <br />
<br />
You should be aware that many mail clients have a tendency to mangle the whitespace of a patch making it impossible to apply. It is highly recommended to read Linux's [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/email-clients.txt;hb=HEAD email-clients.txt] for advice on how to avoid this in popular mail clients.<br />
<br />
=== Review, Rinse & Repeat ===<br />
----<br />
<br />
After posting your patches you will hopefully see some response in the form of comments, patch review and eventually commit.<br />
<br />
The form of the review may often be quite direct and to the point which may be daunting for some people. However bear in mind that detailed criticism of a patch usually means that the reviewer is interested in your patch and wants to see it go in!<br />
<br />
Once you have addressed any review you should normally resend the patch. It is normally expected that you address all review before reposting. This often means code changes in your patch but could also mean simply responding to the review comments explaining you reasoning or giving reasons why something should be the way it is.<br />
<br />
When resending a patch you should normally include a note of what has changed since last time in the message. Common practice is to include these notes after your Signed-off-by separated by a triple-dash ("---"). This indicates patch commentary specific to the posting which need not be included in the final changelog (although you should also remember to update the changelog if necessary). You should also including a "V2" (V3, V4 etc) tag in the subject line (if you are using the Mercurial patchbomb extension then the <code>--flag</code> option is helpful here).<br />
<br />
If someone replies to your patch with a tag of the form "Acked-by: <Developer>", "Reviewed-by:", "Tested-by:" etc then, assuming you have not completely reworked the patch, you should include these tags in any reposting after your own Signed-off-by line. This lets people know that the patch has been seen and that someone approves of it and also serves to prevent reviewers wasting time re-reviewing a patch which is not significantly different to last time. The developers with commit access also like to see postings with such tags since it means they are likely to be much easier to deal with and commit.<br />
<br />
An example of a resend of the example patch from above might be:<br />
<pre><br />
Subject: [PATCH v2] foobar: Add a new trondle calls<br />
<br />
Add a some new trondle calls to the foobar interface to support<br />
the new zot feature.<br />
<br />
Signed-off-by: Joe Smith <joe.smith@citrix.com><br />
Acked-by: Jane Doe <jane.doe@example.com><br />
<br />
---<br />
Changed since v1:<br />
* fix coding style<br />
* be sure to treadle the trondle in the error case.<br />
<br />
diff -r 63531e640828 tools/libxc/Makefile<br />
--- a/tools/libxc/Makefile Mon Dec 07 17:01:11 2009 +0000<br />
+++ b/tools/libxc/Makefile Mon Dec 21 11:45:00 2009 +0000<br />
...<br />
</pre><br />
<br />
If you do not get any response to your patch or you got lots of Acked-by's but the patch has not been committed (remember that reviewers and maintainers are busy people too and sometimes things may fall through the cracks) then after some time, perhaps 2-4 weeks ([http://blog.xen.org/index.php/2009/09/16/submitting-patches-to-xen-org-community/ guidelines]), you should resend the patch, perhaps including [RESEND] in the subject line to alert people that the last mail was dropped. Before resending it may be worth considering if there is anything you can do to improve the commit message or subject line of your patch to better attract the attention of the relevant people. Remember to include any Acked-by/Reviewed-by which you received in response to the previous post.<br />
<br />
=== What If ===<br />
----<br />
* Your patch is really big?<br />
** Break it up into smaller logically distinct patches<br />
** Example - http://markmail.org/thread/e36vcwk3347de27n<br />
* You have lots and lots of patches? If you are going to generate > 20 patches a week:<br />
** You might want to host a repository tree that the maintainers can pull from, talk to the maintainers<br />
<br />
=== After your patch is committed ===<br />
<br />
Changes committed to Xen by the committers are immediately available in the "staging" repositories, for example http://xenbits.xen.org/staging/xen-unstable.hg. They are then automatically tested, and if the tests pass the changes are propagated to the main tree http://xenbits.xen.org/xen-unstable.hg.<br />
<br />
If your patch turns out to break something you will be expected to respond promptly to help diagnose and fix the problem. If it can't be fixed quickly, your change may be reverted.<br />
<br />
[[Category:Developers]]<br />
[[Category:Development Process]]<br />
[[Category:Xen]]<br />
<br />
== How To Generate and Submit a Patch to Qemu-Xen ==<br />
<br />
Xen uses QEMU as device model, that is the software component that takes care of emulating devices (like the network card) for HVM guests.<br />
Two QEMU trees, both using [http://git-scm.com/ git] for revision control, are currently in use by xen-unstable.hg:<br />
<br />
- [http://xenbits.xen.org/gitweb/?p=qemu-xen-unstable.git;a=summary qemu-xen-traditional]: old and stable tree, only bug fixes are accepted in this tree at the moment;<br />
<br />
- [http://xenbits.xen.org/gitweb/?p=staging/qemu-upstream-unstable.git;a=summary qemu-xen]: new tree used for development, based on the latest stable branch of Upstream QEMU, that currently is available at [http://git.qemu.org/ qemu git repo]. See [[QEMU Upstream]] on how to manually build it and use it to run VMs.<br />
<br />
<br />
New features should be developed again the latest upstream QEMU first, see http://wiki.qemu.org/Contribute/SubmitAPatch, then upon request they can be backported to qemu-xen.<br />
Only patches that have been acked and committed to [http://git.qemu.org/qemu.git qemu.git] are eligible to be backported to qemu-xen.<br />
In order to request a backport, send an email to xen-devel@lists.xen.org, specifying the original commit id in qemu.git and the reason why the patch should be backported to qemu-xen.<br />
<br />
== How to Generate, and Submit a Xen Patch to the Linux Tree ==<br />
<br />
Linux uses the git SCM, unlike Xen, which currently uses Mercurial. The Linux tree contains documentation on submitting patches, in Documentation/SubmittingPatches, as well as a script (scripts/checkpatch.pl) that ensures your patch is in Linux house style. Running git apply --check on your patch can reveal merge errors.<br />
<br />
Patches should be emailed to xen-devel@lists.xen.org, linux-kernel@vger.kernel.org, and any relevant maintainers (which can be found by running scripts/get_maintainer.pl on your patch).</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Xen_Document_Days/TODO&diff=3173Xen Document Days/TODO2012-04-20T10:03:07Z<p>Andyhhp: Add Xen command line options to the developer docs todo list</p>
<hr />
<div>Go back to [[Xen Document Days]]<br />
<br />
== Requested Documentation ==<br />
<br />
{{Info|Feel free to add items. Feel free to comment on items. When you comment, please add a sub bullet and sign with '''<nowiki>~~~~: your comment</nowiki>''' which will resolve into your wikiname and date.}}<br />
<br />
=== Big work items ===<br />
<br />
* '''Feature status docs''' for end-users showing which features are expected to work in 4.0 and, possibly 4.1.2. Most people don't know if Feature X is even supposed to work on the Xen build their distro uses. And almost everything is broken somewhere! This is tricky since 4.0 (debian) still has rough edges like immediate panic when doing mem-set on a HV domU by mistake<br />
** [[User:Lars.kurth|Lars.kurth]] One way to approach handle this is to go through release notes and old blog posts and collate a table.<br />
* '''A Xen/XCP Overview''' which explains the top level architectural features and options, trade-offs and links to examples tutorials that show how you set these up<br />
** [[User:Lars.kurth|Lars.kurth]] 09:48, 27 March 2012 (UTC): [[:Category:Overview]] is a starting point, but this is patchy right now<br />
** [[User:Lars.kurth|Lars.kurth]] 22:35, 19 April 2012 (UTC) We have [[Paravirtualization (PV)]] & [[PV on HVM]]. I also have some bits and pieces that I have written for the new website, which could be moved to the wiki.<br />
* '''A Xen Tuning Guide:''' different options in Xen impacting performance, how to set them up, how to tune<br />
** [[User:Lars.kurth|Lars.kurth]] 09:48, 27 March 2012 (UTC): [[:Category:Performance]] contains some performance related docs<br />
* '''A Xen Security Guide:''' The different options in Xen for Security, trade-offs, how to set them up, how to test Xen for security and how to optimize for different scenarios<br />
** [[User:Lars.kurth|Lars.kurth]] 09:48, 27 March 2012 (UTC): [[:Category:Security]] contains some security related docs<br />
** [[User:Lars.kurth|Lars.kurth]] 11:01, 4 April 2012 (UTC): It would be good if we could document a) XSM, b) Introspection API, c) Xen and SELinux in Dom0, d) Memory Access API (introduced in 4.1)<br />
* User Docs that where migrating content would make sense and update such as (we can attach PDF's to the wiki now for starters, or we can use a [http://www.appropedia.org/Appropedia:Porting_PDF_files_to_MediaWiki conversion tool]<br />
** http://bits.xensource.com/Xen/docs/user.pdf<br />
<br />
In progress:<br />
* An Overview over Xen for people who do not yet use Xen, to help them make a decision on whether Xen is for them (aka "Why Xen" and "Which Xen") (be sure to mention "fastest" ;)<br />
** [[User:Lars.kurth|Lars.kurth]] 09:48, 27 March 2012 (UTC): am working on this and am almost ready to publish on the wiki<br />
<br />
=== Categories ===<br />
* Review the Debian and Openstack categories and add documentation that exists in other places.<br />
* Installation Guides<br />
** ijc: How to install on various distros. Tag with [[:Category:Host Install]] and [[:Category:Guest_Install]]. We seem to only have one or two of these but I thought we had more. Perhaps need to link to external sites (e.g. distro wikis/docs)<br />
** [[User:Lars.kurth|Lars.kurth]] 09:52, 27 March 2012 (UTC): moved a few from [[:Category:RefToExternalArticle]] to Guest Install. May be worth looking at http://grantmcwilliams.com/tech/virtualization/xen-howtos and http://grantmcwilliams.com/tech/virtualization/xcp-howtos<br />
<br />
=== Admin docs ===<br />
* Setting boot order for domUs (PV and HVM)<br />
* Chaining pypxeboot and pygrub <br />
** ijc: pypxeboot == tools/misc/xenpvnetboot?<br />
** [[User:Lars.kurth|Lars.kurth]] 10:35, 27 March 2012 (UTC): I found http://sourceforge.net/projects/pypxeboot/ - I don't actually know how added this request. Is pypxeboot popular at all?<br />
* xenpm usage recommendations<br />
* setting up vnc mime magic for xen in firefox (oracle has srpms for a vnc client plugin)<br />
* vcpu pinning<br />
* using xm trigger to poweroff or firing off NMIs<br />
<br />
== Developer Docs ==<br />
<br />
=== Docs for distro packagers ===<br />
* List i.e. stuff what to test after packaging. This would avoid the current state of affairs where most distros are infact broken w/re to Xen.<br />
<br />
=== Docs that need attention or are missing ===<br />
* Make XAPI docs (built from source) available on xen.org<br />
* PVOPS portal on xen.org - Konrad volunteered<br />
* some more xenstore docs (i.e. recent python bindings that were sent to the -users list<br />
* Using libxenstat python bindings (imo they're broken)<br />
* More PV protocol docs (see recent patches to blkif.h for example)<br />
* Document xenstore paths used by guests and toolstack etc<br />
* Xen command line options documentation in tree (started, but not complete)<br />
<br />
== Wiki Maintenance ==<br />
=== Fix artcles that need attention ===<br />
* [[:Category:Contains_Needs_Action]] - Pages that need fixing<br />
* [[:Category:Contains_Needs_Formatting]] - Pages that need formatting<br />
* [[Special:WantedPages]] - Missing pages (many may just need to be migrated), some may be obsolete<br />
<br />
=== Review Categorization ===<br />
We need to go through some of the categies on the http://wiki.xen.org/wiki/Main_Page and decise whether there are documents in each category that need to be highlighted in a trail, etc.<br />
<br />
=== Loose ends on migration ===<br />
* Migrate remaining wiki pages (see [[Wiki_Community/Migration_Instructions_from_Old_to_New_Xen_Wiki]])<br />
<br />
<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/Hackathon/March2012&diff=2744Archived/Hackathon/March20122012-02-29T10:31:29Z<p>Andyhhp: /* Sign-up List */</p>
<hr />
<div>== Contact ==<br />
{{ambox<br />
|type=notice<br />
|text=The Xen community manager will be on vacation from Feb 21 to March 5th. If you have any questions regarding the Hackathon in that time period, please ask the question on [http://lists.xen.org/mailman/listinfo/xen-devel xen-devel] or directly get in touch with Ian Campbell (ian DOT campbell AT citrix.com) and Konrad Rzeszutek Wilk (Konrad DOT Wilk AT oracle DOT com)<br />
}}<br />
== When and Where ? ==<br />
<br />
We confirmed the Xen Hackathon '''hosted by Oracle''' for March 6-8, 2012 at the Oracle campus in Santa Clara.<br \><br />
* March 6th: 9AM to 5PM<br />
* March 7th: 9AM to 5PM<br />
* March 8th: 9AM to 5PM<br />
<br />
Here is the address of the campus:<br> <br />
4030 George Sellon Circle<br> <br />
Santa Clara<br><br />
CA 95054<br><br />
<br />
Click to enlarge:<br><br />
[[File:Oracle_SCA_Campus.png|400px]]<br />
[[File:Oracle_SCA_Campus2.png|400px]]<br />
<br />
=== Conference Room number and location === <br />
<br />
Oracle Campus in Santa Clara<br />
Oracle<br><br />
4190 Network Circle, Santa Clara, CA 95054-1778<br><br />
Building: SCA03 - Room #2100 (2nd floor)<br><br />
<br />
This is building #22 on the map<br />
<br />
=== Parking ===<br />
<br />
AUDITORIUM PARKING: In the building 22 parking lot as well as along Palm Drive.<br />
<br />
== What is a Xen Hackathon? ==<br />
[[File:BeZenHackXen.png|460px|right]]The aim of Xen Hackathons is to give developers in the Xen community the opportunity to meet face to face to discuss development, coordinate, write code and collaborate with other Xen developers. It is a 3 day self-organizing event, where Xen developers work on concrete problems around the Xen codebase in small self-organizing groups. People working on <br />
documentation and other aspects of Xen, XCP, XenARM and related projects are also welcome.<br />
<br />
Xen developers with the following expertise will be present: Xen Hypervisor developers, kernel developers (working on Xen components in the Linux kernel), XCP developers working on project Kronos and the Xen Cloud Platform. Xen on ARM as well is MIPS will also feature in the March 2012 Hackathon.<br />
<br />
Xen Hackathons are also great opportunities for companies and open source projects, built on Xen, XCP or commercially based Xen products to test (and fix any issues in their products) against the latest open source baselines. You will have access and be able to work on concrete code problems with Xen developers at the Hackathon. <br />
<br />
There is no registration fee. However as an attendee you will need to cover your own travel, accommodation and other costs <br />
such as evening meals etc. We will be looking at organizing opportunities to drink beer, etc. in the evenings. If you<br />
know the area and have suggestions, please add to the wiki (see below).<br />
<br />
== Accomodation ==<br />
* The closest hotel to the Oracle Campus is [http://www.hyatt.com/hyatt/hotelsierra/default.htm Hotel Sierra, Santa Clara], but it is also the priciest option.<br />
* [http://www.marriott.com/hotels/travel/sjcga-santa-clara-marriott/ Santa Clara Marriott], 2700 Mission College Boulevard, Santa Clara, CA<br />
* [http://www.hotelbiltmore.com/ Biltmore - Santa Clara, CA], 2151 Laurelwood Road, Santa Clara, CA<br />
* [http://santaclara.hyatt.com Hyatt - Santa Clara], 5101 Great America Parkway, Santa Clara, CA<br />
<br />
== Sign-up List ==<br />
<br />
{{Info|You will have to have an account on the Wiki to sign up. We had to enable Wiki accounts as we had a spam problem.}}<br />
<br />
Please sign up, if you plan to attend:<br />
* If you think you may attend, but are not sure yet add "(provisional)" to the list.<br />
* If you can only attend part-time, please let us know which dates you want to attend.<br />
* If you do not regularly contribute to the Xen a mailing lists, please add your e-mail address such that we can get in touch with you<br />
* If you have any specifific dietary requirements, please add it besides your name<br />
* Please also state your T-shirt size<br />
* If you can't login/don't want a Wiki user, email konrad.wilk@oracle.com<br />
<br />
Attendees:<br />
# Lars Kurth, Xen.org (L)<br />
# Ian Campbell, Citrix. Xen.org committer (L)<br />
# George Dunlap, Citrix<br />
# Mike Hamanaka, Vertualize<br />
# Pasi Karkkainen, Elisa Links (provisional)<br />
# Stefano Stabellini, Citrix<br />
# Konrad Rzeszutek Wilk, Oracle, PVOPS project lead<br />
# Yonghong Song, Netlogic<br />
# Frank Zhang, CloudStack<br />
# Mark Hinkle, Cloudstack<br />
# David Nalley, Cloudstack (XL) <br />
# Andres Lagar-Cavilla, Individual<br />
# Adin Scannell, Individual<br />
# Mukesh Rathor, Oracle<br />
# Mike McClurg, Citrix, XCP project lead (provisional)<br />
# Qin Michael Li (M)<br />
# Wesley Shao, Oracle (M)<br />
# Ben Pfaff, Nicira, blp@nicira.com (L)<br />
# Jacob Ramirez, Oracle (M)<br />
# Kurt Hackel, Oracle (L)<br />
# Zhigang Wang, Oracle (S)<br />
# Aaron Culich, EECS at UC Berkeley (L)<br />
# Rob Hoes, Citrix (L)<br />
# Jacob Shin, AMD (M)<br />
# Justin Gibbs, Spectra Logic (XL)<br />
<br />
Provisionally reserved spaces (names TBD):<br />
* 2xGluster<br />
* 2xInternap<br />
<br />
== Topics to Discuss ==<br />
* Lars: Improving key documents, update and getting feedback on the new xen.org website<br />
* Lars: work with Konrad on PVOPS xen.org portal<br />
* IanC: Stub-oxenstored<br />
* David Nalley: Zeus (packaging XAPI toolstack on Fedora/EPEL) <br />
* Konrad: acpi fun.<br />
* Konrad: RAS features<br />
* Add topic here<br />
<br />
== Suggestions for Evening Social Activities ==<br />
* Add a suggestion here<br />
<br />
[[Category:Project]]<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/Hackathon/March2012&diff=2622Archived/Hackathon/March20122012-02-14T17:00:25Z<p>Andyhhp: /* Sign-up List */</p>
<hr />
<div>== When and Where ? ==<br />
<br />
We confirmed the Xen Hackathon '''hosted by Oracle''' for March 6-8, 2012 at the Oracle campus in Santa Clara.<br \><br />
* March 6th: 9AM to 5PM<br />
* March 7th: 9AM to 5PM<br />
* March 8th: 9AM to 5PM<br />
<br />
Here is the address of the campus:<br> <br />
4030 George Sellon Circle<br> <br />
Santa Clara<br><br />
CA 95054<br><br />
<br />
Click to enlarge:<br><br />
[[File:Oracle_SCA_Campus.png|400px]]<br />
[[File:Oracle_SCA_Campus2.png|400px]]<br />
<br />
=== Conference Room number and location === <br />
<br />
Oracle Campus in Santa Clara<br />
Oracle<br><br />
4190 Network Circle, Santa Clara, CA 95054-1778<br><br />
Building: SCA03 - Room #2100 (2nd floor)<br><br />
<br />
This is building #22 on the map<br />
<br />
=== Parking ===<br />
<br />
AUDITORIUM PARKING: In the building 22 parking lot as well as along Palm Drive.<br />
<br />
== What is a Xen Hackathon? ==<br />
The aim of Xen Hackathons is to give developers the opportunity to meet face to face to discuss development, coordinate, <br />
write code and collaborate with other developers as well as allowing everyone to put names with faces. People working on <br />
documentation and other aspects of Xen, XCP, XenARM and related projects are also welcome.<br />
<br />
There is no registration fee. However as an attendee you will need to cover your own travel, accommodation and other costs <br />
such as evening meals etc. We will be looking at organizing opportunities to drink beer, etc. in the evenings. If you<br />
know the area and have suggestions, please add to the wiki (see below).<br />
<br />
== Accomodation ==<br />
* The closest hotel to the Oracle Campus is [http://www.hyatt.com/hyatt/hotelsierra/default.htm Hotel Sierra, Santa Clara], but it is also the priciest option.<br />
* [http://www.marriott.com/hotels/travel/sjcga-santa-clara-marriott/ Santa Clara Marriott], 2700 Mission College Boulevard, Santa Clara, CA<br />
* [http://www.hotelbiltmore.com/ Biltmore - Santa Clara, CA], 2151 Laurelwood Road, Santa Clara, CA<br />
* [http://santaclara.hyatt.com Hyatt - Santa Clara], 5101 Great America Parkway, Santa Clara, CA<br />
<br />
== Sign-up List ==<br />
Please sign up, if you plan to attend:<br />
* If you think you may attend, but are not sure yet add "(provisional)" to the list.<br />
* If you can only attend part-time, please let us know which dates you want to attend.<br />
* If you do not regularly contribute to the Xen a mailing lists, please add your e-mail address such that we can get in touch with you<br />
* If you have any specifific dietary requirements, please add it besides your name<br />
* Please als state your T-shirt size<br />
<br />
Attendees:<br />
# Lars Kurth, Xen.org (L)<br />
# Ian Campbell, Citrix. Xen.org committer (L)<br />
# George Dunlap, Citrix<br />
# Mike Hamanaka, Vertualize<br />
# Pasi Karkkainen, Elisa Links (provisional)<br />
# Stefano Stabellini, Citrix<br />
# Andrew Cooper, Citrix (L) (provisional)<br />
# Konrad Rzeszutek Wilk, Oracle, PVOPS project lead<br />
# Yonghong Song, Netlogic<br />
# Anthony Xu, Intel<br />
# Mark Hinkle, Cloudstack<br />
# David Nalley, Cloudstack<br />
# Andres Lagar-Cavilla, Individual<br />
# Adin Scannell, Individual<br />
# Mukesh Rathor, Oracle<br />
# Mike McClurg, Citrix, XCP project lead (provisional)<br />
# Qin Michael Li (M)<br />
# Wesley Shao, Oracle (M)<br />
# Add yourself here<br />
<br />
Provisionally reserved spaces (names TBD):<br />
* 2xGluster<br />
* 2xInternap<br />
<br />
== Topics to Discuss ==<br />
* Lars: Improving key documents, update and getting feedback on the new xen.org website<br />
* Lars: work with Konrad on PVOPS xen.org portal<br />
* IanC: Stub-oxenstored<br />
* David Nalley: Zeus (packaging XAPI toolstack on Fedora/EPEL) <br />
* Add topic here<br />
<br />
== Suggestions for Evening Social Activities ==<br />
* Add a suggestion here<br />
<br />
[[Category:Project]]<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Archived/Hackathon/March2012&diff=2482Archived/Hackathon/March20122012-01-31T13:49:05Z<p>Andyhhp: /* Sign-up List */</p>
<hr />
<div>== When and Where ? ==<br />
<br />
We confirmed the Xen Hackathon '''hosted by Oracle''' for March 6-8, 2012 at the Oracle campus in Santa Clara.<br \><br />
Here is the address: 4030 George Sellon Circle, Santa Clara, CA 95054<br />
<br />
[[File:Oracle_SCA_Campus.png|800px]]<br />
<br />
== Sign-up List ==<br />
* Lars Kurth<br />
* Ian Campbell<br />
* George Dunlap<br />
* Mike Hamanaka<br />
* Pasi Karkkainen<br />
* Stefano Stabellini<br />
* Andrew Cooper (provisional)<br />
* Add yourself here<br />
<br />
== Topics to Discuss ==<br />
* Lars: Improving key documents, update and getting feedback on the new xen.org website<br />
* Lars: work with Konrad on PVOPS xen.org portal<br />
* IanC: Stub-oxenstored<br />
* Add topic here<br />
<br />
[[Category:Project]]<br />
[[Category:Community]]<br />
[[Category:Events]]</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Interrupts&diff=633Interrupts2011-11-14T18:30:23Z<p>Andyhhp: Imported information from old wiki</p>
<hr />
<div>[[Category:Developers]]<br />
<br />
The purpose of this page is to document how Xen set up and uses interrupts. It is a work in progress, and to a certain extent dynamic as patches modify the code. However, the contents of it is accurate of 14/11/2011<br />
<br />
== IDT vector entries ==<br />
Refer to <code>xen/include/asm-x86/mach-default/irq_vectors.h</code><br />
<br />
=== Vector Ranges ===<br />
{| cellpadding="2" cellspacing="0"<br />
|| '''Section''' || '''Range''' || '''Use'''<br />
|-<br />
|| Exceptions || <code>0x00 - 0x1f</code> || Architecturally reserved<br />
|-<br />
|| Dynamic IRQs || <code>0x20 - 0xdf</code> || Free for assignment for devices<br />
|-<br />
|| Legacy || <code>0xe0 - 0xef</code> || Reserved range for PIC before switching to APIC<br />
|-<br />
|| High Priority || <code>0xf0 - 0xff</code> || For IPIs and serial interrupts<br />
|}<br />
<br />
=== Specific Vectors ===<br />
{| cellpadding="2" cellspacing="0"<br />
|| '''Vector''' || '''Symbol''' || '''Description'''<br />
|-<br />
|| <code>0x20</code> || <code>IRQ_MOVE_CLEANUP_VECTOR</code> || Clean up references to IRQs in past PCPUs after they have been moved<br />
|-<br />
|| <code>0x80</code> || <code>LEGACY_SYSCALL_VECTOR</code><br />
|-<br />
|| <code>0x82</code> || <code>HYPERCALL_VECTOR</code><br />
|-<br />
|| <code>0xf7</code> || <code>CMCI_APIC_VECTOR</code><br />
|-<br />
|| <code>0xf8</code> || <code>PMU_APIC_VECTOR</code><br />
|-<br />
|| <code>0xf9</code> || <code>LOCAL_TIMER_VECTOR</code><br />
|-<br />
|| <code>0xfa</code> || <code>THERMAL_APIC_VECTOR</code><br />
|-<br />
|| <code>0xfb</code> || <code>CALL_FUNCTION_VECTOR</code><br />
|-<br />
|| <code>0xfc</code> || <code>EVENT_CHECK_VECTOR</code><br />
|-<br />
|| <code>0xfd</code> || <code>INVALIDATE_TLB_VECTOR</code><br />
|-<br />
|| <code>0xfe</code> || <code>ERROR_APIC_VECTOR</code><br />
|-<br />
|| <code>0xff</code> || <code>SPURIOUS_APIC_VECTOR</code><br />
|}</div>Andyhhphttps://wiki.xenproject.org/index.php?title=Interrupts&diff=632Interrupts2011-11-14T18:14:53Z<p>Andyhhp: Created page with "Category:Developers"</p>
<hr />
<div>[[Category:Developers]]</div>Andyhhp