search for: patchqueue

OK, I've got a basic initial port of the xen package up to 4.4.0. But before I post that, I wanted to get comments on a new method of managing the Xen part of the patchqueue. You can find the RFC branch here: repo: http://github.com/gwd/sig-virt-xen branch: out/git-am-patchqueue-RFC-v1 The basic idea is to put as much as possible into a 'git am' file. This file can easily be imported into git on top of a Xen git repository with "git am [filename]",...

...ng thru some merge hell and a need some newer PPC code from kernel.org. is it: http://xenbits.xensource.com/linux-2.6-xen.hg (worked on) --or-- http://xenbits.xensource.com/ext/linux-2.6-merge.hg (six weeks of nothing) there is also linux-2.6.rc-xen.hg, linux-2.6.tip-xen.hg, linux-2.6- patchqueue.hg the PPC team depends on the xenolinux repos trees rather that the sparse tree. We were haning off linux-2.6-merge.hg we would like to figure out which one tracks Linus''s git tree best. Please advise -JX _______________________________________________ Xen-devel mailing list Xen-d...

...virt6 with virt7 or 44 with 46 as appropriate). The patches to the xen hypervisor are in a rather unusual format: a git "am". This makes it *much* easier to rebase and manipulate the queue if you're familiar with git; but it does add a bit to get familiar with. To manipulate the am patchqueue (using 4.4.3 as an example): 1. Check out a git repo and make a branch based on the baseline version $ git checkout -b centos/pq/4.4.3 RELEASE-4.4.3 2. Import SOURCES/xen-queue.am $ git am ${path-to-package-repo}/SOURCES/xen-queue.am OR using stackgit: $ stg init $ stg import -M ${path-to-pac...

...des usb support (same as backported to old ioemu recently) - Doesn''t include pcnet network driver but rtl8139 The main reason for wanting to move to this new codebase is that the current one is badly hacked, making it hard to include updates from qemu. The new codebase is maintained as a patchqueue against qemu so that updates to newer qemu versions are easy. The patchqueue and the repository containing qemu are available at: http://xenbits.xensource.com/chris/xs-tools-ioemu.hg http://xenbits.xensource.com/chris/xs-tools-ioemu.pq.hg Only patches upto 00-last should be applied, all later patc...

Hi, current paravirt patchqueue dies with ... Checking if this processor honours the WP bit even in supervisor mode... Ok. general protection fault: 0000 [#1] SMP Modules linked in: CPU: 0 EIP: 0061:[<c01021a8>] Not tainted VLI EFLAGS: 00010013 (2.6.20-git8-default-hg770 #7) EIP is at xen_evtchn_do_upcall+0x56/0...

Hi, current paravirt patchqueue dies with ... Checking if this processor honours the WP bit even in supervisor mode... Ok. general protection fault: 0000 [#1] SMP Modules linked in: CPU: 0 EIP: 0061:[<c01021a8>] Not tainted VLI EFLAGS: 00010013 (2.6.20-git8-default-hg770 #7) EIP is at xen_evtchn_do_upcall+0x56/0...

...ple understand this. We are actively developing paravirt ops, we have a patch series that begins to implement it (although it's still in it's nascent stage). If anybody is interested in our work it is done in public. The working tree is here: http://ozlabs.org/~rusty/paravirt/ (mercurial patchqueue, just be forewarned that it's still quite early to be playing with it, doesn't do much yet). We are using the virtualization mailing list for discussions https://lists.osdl.org/mailman/listinfo/virtualization if you are interested. Zach (please correct me if I'm wrong here), is workin...

...ple understand this. We are actively developing paravirt ops, we have a patch series that begins to implement it (although it's still in it's nascent stage). If anybody is interested in our work it is done in public. The working tree is here: http://ozlabs.org/~rusty/paravirt/ (mercurial patchqueue, just be forewarned that it's still quite early to be playing with it, doesn't do much yet). We are using the virtualization mailing list for discussions https://lists.osdl.org/mailman/listinfo/virtualization if you are interested. Zach (please correct me if I'm wrong here), is workin...

Folks, OLS is fast approaching. There is a session on virtualization at the Kernel Summit, with Keir and Zach invited, which will probably last an hour(?). There is also a Xen BoF currently scheduled (Thursday, 7/20, 7:00PM) which will cover Xen specific issues. And there are approximately 3 or 4 paper presentations on related subjects. None of the above are going to allow for adequate time to

...ightly (mainly because I had an epiphany about inter-guest I/O). I also implemented a console (lguest needs one). Finally, there is a working lguest implementation. Unfortunately, lguest is being refactored for non-i386 ports, so the virtio patches sit at the end of the (quite long) for-2.6.24 patchqueue. Nonetheless, they can be found at http://lguest.ozlabs.org/patches (click on bz2 to get the series). Cheers! Rusty.

...ightly (mainly because I had an epiphany about inter-guest I/O). I also implemented a console (lguest needs one). Finally, there is a working lguest implementation. Unfortunately, lguest is being refactored for non-i386 ports, so the virtio patches sit at the end of the (quite long) for-2.6.24 patchqueue. Nonetheless, they can be found at http://lguest.ozlabs.org/patches (click on bz2 to get the series). Cheers! Rusty.

It looks like no XSA-142 patch, which is "libxl fails to honour readonly flag on disks with qemu-xen" has been applied to Xen4CentOS. I assume this was on purpose? If not, I can have someone try adding the original patch from http://xenbits.xen.org/xsa/advisory-142.html and some variant of the commit from ef6cb76026628e26e3d1ae53c50ccde1c3c78b1b

As per our policy, the next officially supported Virt SIG Xen version will be 4.8. However, with 4.7 coming soon, I've ported the patchqueue over to 4.7rc4 and given it a spin. If you want to help testing for the upstream 4.7 release, do give it a spin and report any regressions. Please note that this version WILL NOT SUPPORTED. 4.6 is still the officially-supported version until 4.8 comes out (probably in around 6 month's time)....

> > working in 4.6 for some people, but is working in 4.5 > > How can I downgrade to Xen 4.5 so I can test this out? > > Many thanks > > We do not provide a CentOS-7 version of Xen lower than 4.6. At the > time > we started Xen support on CentOS-7, 4.6 was already stable and that > was > our first release for CentOS-7. > > We do currently have both

On 01/18/2018 09:56 AM, Kevin Stange wrote: > Apparently I failed to do proper due diligence before making this > recommendation. The Xen 4.4 repo does not have vixen build because of a > dependency upon grub2 which isn't available under CentOS 6. Your best > bet would be to use Vixen for PV domains, so if you think that's > something you want to do, we need some

...rly with pvops. But in its current state it's useful enough for testing that I've pushed it as it stands. NOTE: this current code has not actually been tagged and rebased, it's not exactly a "release" as much as a snapshot of the development work --- I'll do a rebase and patchqueue release of it once I've done the contig region cleanups. I've also got paravirt framebuffer patches from Markus Armbruster to integrate for that. --Stephen

...rly with pvops. But in its current state it's useful enough for testing that I've pushed it as it stands. NOTE: this current code has not actually been tagged and rebased, it's not exactly a "release" as much as a snapshot of the development work --- I'll do a rebase and patchqueue release of it once I've done the contig region cleanups. I've also got paravirt framebuffer patches from Markus Armbruster to integrate for that. --Stephen

...rly with pvops. But in its current state it's useful enough for testing that I've pushed it as it stands. NOTE: this current code has not actually been tagged and rebased, it's not exactly a "release" as much as a snapshot of the development work --- I'll do a rebase and patchqueue release of it once I've done the contig region cleanups. I've also got paravirt framebuffer patches from Markus Armbruster to integrate for that. --Stephen

Hi all, I have pushed out klibc-1.5.17, mostly based on Max' patchqueue: H. Peter Anvin (3): [klibc] 1.5.16 released, next version is 1.5.17 [klibc] socketcalls: add parens around defined() [klibc] losetup: fix pointer type warnings Louis Rilling (2): [klibc] ipconfig: Fix missing dhcp_end field [klibc] ipconfig: Fix null ciaddr on DHCPR...

Hi All, I'm seeing tapdisk processes not being terminated after a HVM vm is shutdown or migrated away. I don't see this problem with linux paravirt domu's, just windows hvm ones. xl.cfg: name = 'nathanwin' memory = 4096 vcpus = 2 disk = [ 'file:/mnt/gtc_disk_p1/nathanwin/drive_c,hda,w' ] vif = [ 'mac=00:16:3D:01:03:E0,bridge=vlan208' ] builder =