Package Details: xen-docs 4.21.2pre-1

Git Clone URL: https://aur.archlinux.org/xen.git (read-only, click to copy)
Package Base: xen
Description: Xen hypervisor documentation and man pages
Upstream URL: https://xenproject.org/
Keywords: hypervisor virtualization xen
Licenses: GPL2
Submitter: sergej
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 182
Popularity: 0.000012
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2026-05-06 02:59 (UTC)

Required by (3)

Sources (13)

Latest Comments

« First ‹ Previous 1 .. 60 61 62 63 64 65 66 67 68 69 70 .. 102 Next › Last »

kantras commented on 2013-08-14 07:20 (UTC)

Ok, the new build is up on my website: http://www.kantras.info/xen/xen-4.3.0-4.tgz - it has the TOM register patch (the one which helps with the >3Gb memory assignment) as well as a little more cleanup (more to come) I've also included the ATI Passthrough patch, although its not enabled by default and so far I've only made sure that it would still compile if enabled

evilsephiroth commented on 2013-08-14 06:22 (UTC)

ok. With qemu-xen-traditional the domU seems pretty stable so I'm not in a hurry.

kantras commented on 2013-08-14 04:40 (UTC)

@tritron I've not tried opennebula yet - not had a need to.

kantras commented on 2013-08-14 04:38 (UTC)

OK, having been playing with that patch I mentioned, I found out it requires additional code which doesn't exist yet (and the PCI Passthrough issue is still listed as outstanding for 4.4, so no sign of an official patch yet) but found other references to the one you've mentioned so am going to clean it up a touch, add, test, and then will upload.

tritron commented on 2013-08-12 01:39 (UTC)

Did anyone compiled this package with qemu git? This could solve the issue? Is anyone using opennebula with xen ?

kantras commented on 2013-08-12 00:33 (UTC)

I'm also using qemu-xen-traditional, which is why I guess I wasn't affected. I've just spent an hour or so going back through the history on that patch; it was rejected for multiple reasons, including the mechanism used as well as the change occuring too late in the boot up sequence. A workaround patch was sent to the qemu-devel list but I don't know that it was included in time (my build sources show no sign on the patch http://marc.info/?l=qemu-devel&m=137043414711228&q=raw ) I'm going to work on getting this newer patch into place in my AUR package, and will post here when the new version is uploaded into my web space. I'm also looking into becoming the maintainer of this package, so I can help keep it up to date.

evilsephiroth commented on 2013-08-11 21:59 (UTC)

radeon 6570 to windows 7 hvm domu but the limit persists also with discrete card... Strange but true :D

evilsephiroth commented on 2013-08-11 21:52 (UTC)

Thanks. At the moment,I solved the memory issue adding device_model_version = 'qemu-xen-traditional' to the hvm win7 domu conf file... Doing this, I lost completely vnc capabiliities for domU, so the patch would be greatly appreciated... Thanks again...

kantras commented on 2013-08-11 20:31 (UTC)

I've not included that patch yet, since I'm not currently affected (have gfx passthrough of a radeon 6770 to a window 7 HVM domU, with 6Gb of RAM). I remember seeing that patch around on the mailing list ; let me recheck the context and I can add it in (the file paths listed in the patch don't mention which subsection it'srelated to)

« First ‹ Previous 1 .. 60 61 62 63 64 65 66 67 68 69 70 .. 102 Next › Last »