[Fedora-xen] Xen 4.8.0 now in rawhide
I have just finished building xen-4.8.0 in rawhide. As well as the update I have enabled armv7hl and aarch64 builds. These should be considered experimental, and may not work, particularly as I believe some other packages such as the kernel, don't yet have xen support for these architectures. Michael Young ___ xen mailing list -- xen@lists.fedoraproject.org To unsubscribe send an email to xen-le...@lists.fedoraproject.org
[Fedora-xen] Re: package xen for aarch64
On Tue, 25 Oct 2016, Ricardo Salveti wrote: > On Sun, Oct 23, 2016 at 10:49 PM, Ricardo Salveti > <ricardo.salv...@linaro.org> wrote: > > On Fri, Oct 21, 2016 at 5:36 PM, M A Young <m.a.yo...@durham.ac.uk> wrote: > >> On Wed, 19 Oct 2016, Ricardo Salveti wrote: > >> > >>> On Wed, Oct 19, 2016 at 4:12 PM, M A Young <m.a.yo...@durham.ac.uk> wrote: > >>> > On Tue, 18 Oct 2016, Anders Roxell wrote: > >>> > > >>> >> I'm trying to package dpdk for aarch64, but package xen-devel is > >>> >> missing. > >>> >> Looking at the xen spec file, it seems the problem is the lack of a > >>> >> compatible efi firmware for arm64, is that really the case? > >>> > > >>> > In Fedora, it is just that I haven't got around to adding ARM support, > >>> > and > >>> > as I have no way of testing it, I can't tell whether what is built will > >>> > actually work. The current spec file is based around x86 but it should > >>> > be > >>> > possible to adapt it to allow ARM builds - I have experimented with it > >>> > in > >>> > the past. > >>> > >>> We can definitely help testing the rpm, once there is one rpm that is > >>> compatible with aarch64. > >>> > >>> Marcin, do you know if there is already an aarch64-compatible efi > >>> image for Fedora? I believe it would also make sense to build xen with > >>> efi support on aarch64. > >> > >> I have done a temporary build of the Fedora 25 xen package adapted for > >> aarch64 at > >> http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=3757184 > >> > >> Could you test it and see if it works or needs further modification. If it > >> is satifactory then I will look at adding aarch64 support to the main > >> Fedora package. > > > > The package installs fine, but fails to run as there is no xen support > > enabled in the kernel. > > > > I will try to recompile the kernel and enable the required config > > options, but it would be nice if you could also take a look at what is > > required, as there are many options related with xen support. > > Built a new kernel including all the xen options, but still unable to > get it to work. > > The grub2 entry fails to load due lack of efi modules: > Loading Xen 4.7.0.config ... > error: can't find command `multiboot'. > Loading Linux 4.8.3-300.fc25.aarch64 ... > error: can't find command `module'. > Loading initial ramdisk ... > error: can't find command `module'. > > Looking at the grub2-efi-modules package, it seems there is no module > and no multiboot there. > > And when trying to chainload the efi loader, it also fails with the > following message: > Xen 4.7.0 (c/s ) EFI loader > No configuration file found. It seems unlikely that the multiboot option will work on aarch64 if there is no multiboot module. The chainloader option looks more promising. If your efi file is xen.efi then it is looking for a xen.cfg file in the same directory to tell it any xen options, what other files (still in the same directory) to load and with what options. For more details see http://xenbits.xenproject.org/docs/unstable/misc/efi.html or equivalently docs/html/misc/efi.html in the xen source. Michael Young ___ xen mailing list -- xen@lists.fedoraproject.org To unsubscribe send an email to xen-le...@lists.fedoraproject.org
[Fedora-xen] Re: package xen for aarch64
On Wed, 19 Oct 2016, Ricardo Salveti wrote: > On Wed, Oct 19, 2016 at 4:12 PM, M A Young <m.a.yo...@durham.ac.uk> wrote: > > On Tue, 18 Oct 2016, Anders Roxell wrote: > > > >> I'm trying to package dpdk for aarch64, but package xen-devel is missing. > >> Looking at the xen spec file, it seems the problem is the lack of a > >> compatible efi firmware for arm64, is that really the case? > > > > In Fedora, it is just that I haven't got around to adding ARM support, and > > as I have no way of testing it, I can't tell whether what is built will > > actually work. The current spec file is based around x86 but it should be > > possible to adapt it to allow ARM builds - I have experimented with it in > > the past. > > We can definitely help testing the rpm, once there is one rpm that is > compatible with aarch64. > > Marcin, do you know if there is already an aarch64-compatible efi > image for Fedora? I believe it would also make sense to build xen with > efi support on aarch64. I have done a temporary build of the Fedora 25 xen package adapted for aarch64 at http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=3757184 Could you test it and see if it works or needs further modification. If it is satifactory then I will look at adding aarch64 support to the main Fedora package. Michael Young ___ xen mailing list -- xen@lists.fedoraproject.org To unsubscribe send an email to xen-le...@lists.fedoraproject.org
[Fedora-xen] Re: package xen for aarch64
On Tue, 18 Oct 2016, Anders Roxell wrote: > I'm trying to package dpdk for aarch64, but package xen-devel is missing. > Looking at the xen spec file, it seems the problem is the lack of a > compatible efi firmware for arm64, is that really the case? In Fedora, it is just that I haven't got around to adding ARM support, and as I have no way of testing it, I can't tell whether what is built will actually work. The current spec file is based around x86 but it should be possible to adapt it to allow ARM builds - I have experimented with it in the past. Michael Young ___ xen mailing list -- xen@lists.fedoraproject.org To unsubscribe send an email to xen-le...@lists.fedoraproject.org
[Fedora-xen] Re: Xen utilities hanging on Fedora 24
On Tue, 31 May 2016, W. Michael Petullo wrote:
> Has anyone else seen things like "xl list" or xentop hang on Fedora 24?
>
> # rpm -q kernel xen
> kernel-4.5.5-300.fc24.x86_64
> xen-4.6.1-10.fc24.x86_64
>
> Running "strace xl list" produces the following, which seems to indicate
> that the hang occurs when "xl list" writes to /dev/xen/xenbus:
>
> access("/dev/xen/xenbus", F_OK) = 0
> stat("/dev/xen/xenbus", {st_mode=S_IFCHR|0600, st_rdev=makedev(10, 62), ...})
> = 0
> open("/dev/xen/xenbus", O_RDWR) = 6
> open("/etc/xen/xl.conf", O_RDONLY) = 7
I think this depends on having the right DomU running as I have used xl
list with the above settings without problems (though I don't think
anything I run depends on xenbus).
I also wonder what your selinux settings are. I had problems with
xen-4.7.0 which uses /dev/xen/privcmd which had
system_u:object_r:device_t:s0 permissions rather than
system_u:object_r:xen_device_t:s0 (now fixed if you have a recent enough
selinux). If you have selinux enabled could you try
chcon -t xen_device_t /dev/xen/xenbus
to see if that makes any difference or alternatively setenforce 0.
Michael Young
--
xen mailing list
xen@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/xen@lists.fedoraproject.org
[Fedora-xen] xen 4.6.0 on Fedora
I have just built xen 4.6.0-1 on rawhide, and if you want to test it on earlier Fedoras the same source has been built on my myoung/xentest copr repository (though you may have problems with qemu and libvirt if they are linked against earlier versions of xen). Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Running fedora xen on top of KVM?
On Wed, 16 Sep 2015, Cole Robinson wrote: > Unfortunately I couldn't get anything else extra out of xen using any of these > options or the ones Major recommended... in fact I couldn't get anything to > the serial console at all. console=con1 would seem to redirect messages since > they wouldn't show up on the graphical display, but nothing went to the serial > log. Maybe I'm missing something... That should be console=com1 so you have a typo either in this message or in your tests. > sync_console gives an extra message but that's all I could see. Is > console=hvc0 correct for a KVM guest, or is that only going to work for > xen-on-xen ? I tried console=ttyS0 as well but it didn't make a difference It is hvc0 to send it to xen and thus onto the console you specified above. You can get some early debug messages of the kernel with earlyprintk=xen and "log_lvl=all guest_loglvl=all" are recommended at http://wiki.xenproject.org/wiki/Debugging_Xen for the xen hypervisor line. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Running fedora xen on top of KVM?
On Tue, 15 Sep 2015, Cole Robinson wrote: > Anyone know how to get fedora + xen running in a KVM VM? I'd like to be able > to do basic xen/libxl/libvirt testing without needed to reboot a physical > machine. > > Trying with F23 AMD host, F22+xen L1, trying to boot into xen in the L1 VM > just reboots very soon after trying to boot the kernel. Tried disabling all > virtio for L1 VM, disabling virt extensions for the L1 VM, but it didn't seem > to change anything. Unfortunately the messages scroll by so quickly I can't > tell what's happening right before it reboots, and all efforts to convince it > to print more debugging haven't worked. > > FWIW this does work with rhel5+xen L1, but that's a world away at this point. > > So anyone know if it's even possible? Is there a trick to it? If not, > suggestions on getting more debug output from xen + grub2? It works for me after a basic and probably sub-optimal install, as follows * qemu-kvm -cdrom Fedora-Server-DVD-x86_64-22.iso -m 1024 -hda kvm.img * do a minimal install * after reboot dnf install xen xen-hypervisor * select "Fedora, with Xen hypervisor" in the boot menu If you need more debugging, boot without xen, and edit the grub.cfg file, adding console=com1 after xen.gz and replacing rhgb quiet with console=hvc0 in the 'Fedora, with Xen hypervisor' section, then boot kvm with -serial eg. -serial file:boot.log which should give you xen logging after grub has finished. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 21 crashes when booted as Dom0
On Fri, 6 Feb 2015, W. Michael Petullo wrote: Has anyone else seen this: https://bugzilla.redhat.com/show_bug.cgi?id=1188573 ? The current Fedora 21 kernel crashes on my computer when booted in Dom0. I had a crash with a 3.18.x Fedora 21 kernel, though I didn't have time then to investigate, so just backed down to the previous kernel. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] building Xen from SRPM
On Tue, 25 Mar 2014, Bill McGonigle wrote: In trying to hunt down a memory mapping problem (e801/e802/UEFI/etc. - trying out some upstream patches) I'm seeing the current Xen SRPM from koji not building on my f20 system. I'm trying to build xen-4.3.2-1.fc20.src.rpm. Looking in my SRPMS directory, the last one I built locally was xen-4.1.4-5.fc17.src.rpm, which completed. I wasn't successful in finding good docs on dealing with attributes for symlinks in a SPEC. Perhaps somebody on the list has a fix in their own tree? Once I can get it building again, I can pursue the memory issue further. -Bill Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/flowerpt/rpmbuild/BUILDROOT/xen-4.3.2-1.fc20.x86_64 error: Installed (but unpackaged) file(s) found: /usr/lib/xen/boot/vtpm-stubdom.gz /usr/lib/xen/boot/vtpmmgr-stubdom.gz This means you have package(s) installed that the standard build doesn't. One option is to edit the xen.spec file in ~/SPECS directory to package these files, eg. add these files after the /usr/lib/xen/boot/xenstore-stubdom.gz line, and then build from the revised spec file, ie. rpmbuild -ba ~/rpmbuild/SPECS/xen.spec Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen 4.4 Released!
On Mon, 10 Mar 2014, Pasi Kärkkäinen wrote: - Forwarded message from George Dunlap george.dun...@eu.citrix.com - The Xen Project team is pleased to announce the official release of Xen 4.4. The result of nearly 8 months of development, new features include: * Solid libvirt support in libxl. * FIFO scalable event channel implementation * Experimental support for PVH mode for guests * Driver domains: block scripts, qdisk, non-Linux driver domains * Improved support for SPICE * Improved kexec * Stable ABI for arm32 and arm64 * Simpler to add a new ARM platform * As always, a number of stability, performance, and security enhancements under the hood. There is now a build of xen-4.4.0 in Rawhide. Also the latest build of Fedora's qemu on Rawhide has xen support enabled. Michael Young-- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] [TestDay] xen 4.4 FC3 xl create error
On Wed, 5 Feb 2014, Ian Campbell wrote: On Tue, 2014-02-04 at 18:41 +, M A Young wrote: We should probably consider taking some unit files into the xen tree, if someone wants to submit a set? I can submit a set, which start services individually rather than a unified xencommons style start file. I didn't find a good way to reproduce the xendomains script, so I ended running an edited version of the sysvinit script with a systemd wrapper file. I don't know what is conventional in systemd land but I have no problem with that approach. Would it make sense to have some sort of configure option tools to choose between sysvinit and systemd? AIUI systemd will DTWT and ignore the initscript if there is a systemd unit file, so installing both seems to be fine to me, and is certain to be less error prone. Although perhaps the xencommons vs split units breaks that suppression logic? What depends on the xenstored xenconsole modules? Is it possible to have a metaunit xencommons which a) causes everything to be started and b) suppresses the initscript by having the same name? Or maybe there is a systemd syntax you can use to suppress xencommons.init? I don't know of an alternate way to suppress and init.d script, so I agree it makes sense to have a dummy xencommons.service unit which will start any other xen units, but doesn't do anything functional itself. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] [TestDay] xen 4.4 FC3 xl create error
On Tue, 4 Feb 2014, Ian Campbell wrote: On Tue, 2014-02-04 at 08:26 -0700, Eric Houby wrote: Xen list, I have a clean F20 install with the RC3 RPMs and see an error when starting a VM. A similar issue was seen with the RC2 RPMs. Thanks for the report. [root@xen ~]# xl create f20.xl Parsing config from f20.xl libxl: error: libxl_create.c:1054:domcreate_launch_dm: unable to add disk devices libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device model pid in /local/domain/2/image/device-model-pid libxl: error: libxl.c:1425:libxl__destroy_domid: libxl__destroy_device_model failed for 2 libxl: error: libxl_device.c:780:libxl__initiate_device_remove: unable to get my domid libxl: error: libxl.c:1461:devices_destroy_cb: libxl__devices_destroy failed for 2 [root@xen ~]# [root@xen ~]# /usr/bin/xenstore-write /local/domain/0/domid 0 [root@xen ~]# [root@xen ~]# xl create f20.xl Parsing config from f20.xl [root@xen ~]# [root@xen ~]# [root@xen ~]# xl list NameID Mem VCPUs State Time(s) Domain-0 0 2047 2 r- 19.7 f20 3 4095 1 r- 4.1 After running the xenstore-write command VMs start up without issue. This is a bug in the Fedora versions of the initscripts (or I suppose these days they are systemd unit files or whatever). The sysvinit scripts shipped with Xen itself have this write in already. I am puzzled by this as the systemd files in the Fedora RC3 test build do indeed run /usr/bin/xenstore-write /local/domain/0/domid 0 so I am not sure why it isn't being set in this case. It certainly works for me. We should probably consider taking some unit files into the xen tree, if someone wants to submit a set? I can submit a set, which start services individually rather than a unified xencommons style start file. I didn't find a good way to reproduce the xendomains script, so I ended running an edited version of the sysvinit script with a systemd wrapper file. Would it make sense to have some sort of configure option tools to choose between sysvinit and systemd? Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] [TestDay] xen 4.4 FC3 xl create error
On Tue, 4 Feb 2014, M A Young wrote: I am puzzled by this as the systemd files in the Fedora RC3 test build do indeed run /usr/bin/xenstore-write /local/domain/0/domid 0 so I am not sure why it isn't being set in this case. It certainly works for me. I have now worked out what the problem is. There are alternate systemd files, one for xenstored and one for oxenstored (if it is installed) and I only added the line /usr/bin/xenstore-write /local/domain/0/domid 0 to the xenstored one, so if the rpm containing oxenstored was installed it would produce the behaviour as reported in this thread. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-users] REMINDER: Feb 3 is Xen Project Test Day for 4.4 RC3
On Fri, 31 Jan 2014, Dario Faggioli wrote: On Fri, 2014-01-31 at 14:48 -0700, Eric Houby wrote: Next Monday, February 3, is the Test Day for Xen 4.4. Release Candidate 3. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC3_test_instructions Russ, On the RC3 test instructions page, the link for the RC3 RPMS are pointing to what looks like the RC2 RPMs from 1/16. Will there be updated RPMs for this test day? Michael, what do you think? It's late I know... Sorry for that, but I'm travelling and couldn't direct your attention to this before. There is an rc3 build at http://koji.fedoraproject.org/koji/taskinfo?taskID=6479953 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] f20 guest on centos5 xen host
On Tue, 21 Jan 2014, Cole Robinson wrote: On 01/21/2014 09:12 AM, Cole Robinson wrote: On 01/20/2014 03:59 PM, Bruno Postle wrote: Hi, I'm having trouble installing a fedora f20 guest on a centos5 host, I previously had a working f16 guest, so I guess I want to know if this is possible or not. virt-install seems to work ok as before, but then the reboot fails with this error: Error starting domain: POST operation failed: xend_post: error from xen daemon: (xend.err Error creating domain: Boot loader didn't return any data!) I've tried formatting /boot as ext2 and ext3 with the same result, now I'm out of ideas. Here is my virt-install command: virt-install --paravirt --name honk --ram 2048 --disk \ path=/dev/VolGroup02/LogVol12 --vnc --location \ http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/ F20 as a paravirt guest should work, but I think nowadays most people are using fullvirt xen, so maybe paravirt isn't tested as much with new distros. I'm just guessing though Regardless, you'll probably have to dig in xen logs to or do some googling to find more info: I don't have any idea. It's very unlikely to be a virt-install/libvirt issue though Sorry, I thought this email went to the upstream virt-manager list, hence I was focusing on that :) RHEL5 xen is an old frankenstein monster at this point as well, so could be a xen issue that just hasn't been backported. CCing fedora xen list as well, maybe they have ideas. I would need to see more logs to be sure, but I would guess pygrub is missing at least one update and this one http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b298b8776d7ffc5fb1261e176f4http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b298b8776d7ffc5fb1261e176f4 is a possibility. You could test if it is pygrub by running directly - in your case try /usr/bin/pygrub /dev/VolGroup02/LogVol12 as root - it should give you a choice of kernels and return the details for the one you pick. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen 4.4-rc2 TestDay on Monday, Jan 20
On Thu, 16 Jan 2014, Dario Faggioli wrote: On gio, 2014-01-16 at 14:17 +0100, Dario Faggioli wrote: Hi everyone, Hey Michael, Xen 4.4 release time is approaching, so Test Days have arrived! On Monday, January 20, we are holding a Test Day for Xen 4.4. Release Candidate 2. General Information about Test Days can be found here: http://wiki.xenproject.org/wiki/Xen_Test_Days and specific instructions for this Test Day are located here: http://wiki.xenproject.org/wiki/Xen_4.4_RC2_test_instructions Please join us on Monday, January 20, and help make sure the next release of Xen is the best one yet! Any chance you do something like (I really should say 'something equally awesome') what you did for 4.3 TestDays and prepare 4.4-rc2 RPMs? Of course, no big deal if you don't. Actually, sorry for the short notice with which I'm asking. However, if you happen to do it, let me know, so I can update the Wiki page accordingly. I have done a temporary build for F20 which is at http://koji.fedoraproject.org/koji/taskinfo?taskID=6416769 It is a bit of a work in progress, so things may change in later builds. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen 4.3.0 on Fedora 20
On Wed, 17 Jul 2013, Konrad Rzeszutek Wilk wrote: Does that mean if I do an 32bit install of Xen it will install a 64bit hypervisor (xen.gz)? That would be quite fantastic! Not at the moment, but it is what I would like to do. I don't think Fedora supports installing x86_64 packages on i686, so my current plan, if I can get it working, is to cross compile a 64-bit hypervisor in the 32-bit build. You may be able to force an install of the x86_64 hypervisor package on i686 as a temporary measure, or just copy over the files. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 6th Xen Test Day for 4.3 is on Friday!
On Thu, 27 Jun 2013, Dario Faggioli wrote: For more information, see: - on getting (available from tomorrow) and testing RC6: http://wiki.xen.org/wiki/Xen_4.3_RC6_test_instructions the release have been tagged, and the tarball is in the usual place: http://bits.xensource.com/oss-xen/release/4.3.0-rc6/xen-4.3.0-rc6.tar.gz If you want to play with it and build the RPMs, as you did last time, that would be awesome. There is a build for F18 temporarily at http://koji.fedoraproject.org/koji/taskinfo?taskID=5551851 . This one has i686 packages without a hypervisor (I still haven't decided what to do about i686). It also has XSM built in; if you want to try it add the line module /boot/flask/xenpolicy.24 after the other module lines for your chosen kernel and flask_enforcing=1 on the xen.gz line. http://wiki.xenproject.org/wiki/XSM has more details. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] 5th Xen Test Day is today!
On Wed, 19 Jun 2013, Konrad Rzeszutek Wilk wrote: On Wed, Jun 19, 2013 at 09:39:36AM +0200, Dario Faggioli wrote: Hi everybody, With this mail I kick off the 5th, and most likely the _final_, Xen Test Day for 4.3... come and join us on #xentest on freenode! We will be testing RC5 which, if everything goes fine, will the be released next week as Xen 4.3. Fetch Xen-4.3.0-rc5 RPMs here: http://koji.fedoraproject.org/koji/taskinfo?taskID=5517793 It boots nicely with a stock Fedora 18 install. This is on Thinkpad X230. The oddity was that I saw 'xenpolicy.24' as one of the boot options? It is a policy file for XSM - see http://wiki.xenproject.org/wiki/XSM As it was built I packaged it, though it looks like it should be in a flask subdirectory according to that page, so I might do that for a proper build. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 4th Xen Test Day for 4.3 is Tomorrow!
On Tue, 18 Jun 2013, Dario Faggioli wrote: Allow me to quickly remind you that the fifth and most likely *final* Xen Test Day for the 4.3 release cycle is happening _tomorrow_, Wednesday, June 19th! We will be on #xentest, testing Xen-4.3.0-RC5, which will likely be the version that will be released... If you were waiting for the code to be stable and close enough to the actual release to chime in and do some testing, well, tomorrow is the perfect time then! For more information, see: - On Xen Test Days (will point to RC5 test instructions): http://wiki.xen.org/wiki/Xen_Test_Days - On testing Xen in general: http://wiki.xen.org/wiki/Testing_Xen If anyone wants to test prebuilt RPMs there is a set for Fedora 18 x86_64 temporarily at http://koji.fedoraproject.org/koji/taskinfo?taskID=5517793 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen Test Day next Wednesday (May 22nd 2013)
On Mon, 20 May 2013, Dario Faggioli wrote: On lun, 2013-05-20 at 16:06 +0100, M A Young wrote: On Mon, 20 May 2013, W. Michael Petullo wrote: Will we have a Fedora RPM? I could probably build one if it would be useful. I did a bit of experimenting with rc1. Well, if you ask me, that would be something truly awesome to have. I can't be sure on how many people will participate, so I really don't want to push Michael to hard into doing it, if he's otherwise engaged but, again, if possible, that would be great. If you do that, do let me know, so that I can update the announcements and the relevant Wiki pages to have a link to it! There is a temporary build for Fedora 18 at http://koji.fedoraproject.org/koji/taskinfo?taskID=5407161 This is x86_64 only, as ix86 isn't fully supported in 4.3 and I haven't decided what (if anything) to build for it. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fresh Ubuntu Precise 12.04 i386 installation as domU in both F17 and 18 dom0 doesn't boot at all
On Tue, 5 Mar 2013, Roberto Fichera wrote: I'm trying to boot Ubuntu 12.04 LTS precise i386 as domU after a clean installation on Fedora F17 and/or F18 dom0 fully updated. VmError: (2, 'Invalid kernel', 'elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images') It seems that pygrub doesn't like your guest kernel (or possibly is failing to download them). Do you know what file format Ubuntu uses for these kernels? Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] f18, xen, utils
On Sat, 16 Feb 2013, Mike Wright wrote: rpm -qlp xen-4.2.1-5.fc18.x86_64.rpm yields quite a surprise. There is no trace of xl. The package still includes xm which requires xend, both of which have been deprecated since (I think) xen 4.0.0. Granted, I built, rather than yummed, 4.0.0 from sources and have been using xl ever since but the continued distribution of xm confuses me greatly. Two questions: Does anybody know why this was done? Is there a package that includes xl? If you install it, it will pull in other packages including xen-runtime, which does include xl. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
On Tue, 12 Feb 2013, Dario Faggioli wrote: Well, this is a very fair point, with the only issue being that, if you install 'libvirt-daemon-xen', things break! :-( How can we change that and make it work? Perhaps libvirt-daemon-xen shouldn't bring in, as dependency, libvirt-daemon-driver-libxl, at least not in versions where the libxl libvirt driver is known to be broken? It seems to me this thread has been focussing on a work around for an undisclosed problem rather than identifying what the problem actually is and solving it, or coming up with a better workaround. Could someone provide more details of exactly what happens and preferably submit a bug report to http://bugzilla.redhat.com/ so it can be looked at properly. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
On Tue, 12 Feb 2013, Dario Faggioli wrote: On Tue, 2013-02-12 at 10:48 +, M A Young wrote: It seems to me this thread has been focussing on a work around for an undisclosed problem rather than identifying what the problem actually is and solving it, or coming up with a better workaround. Indeed, while identifying and fixing/helping to fix was my first and main intent. I'm think this is still related to what we were discussing here: https://bugzilla.redhat.com/show_bug.cgi?id=893699, although that took so many different directions that it is now very difficult to make any sense out of it! If I'm not providing enough or good enough feedback and suggestions, I'm sorry, but really, my primary concern is to see all this working! :-) Could someone provide more details of exactly what happens and preferably submit a bug report to http://bugzilla.redhat.com/ so it can be looked at properly. Let me try (again), repeating all the steps, starting from a fresh F18 install. After that, we'll decide if we want to stick with 893699 bugzilla entry, or create a new one, or whatever else we want to do... Ok, here I am. 1. Install F18 2. yum install xen 3. reboot 4. ps aux | grep xend [nothing found] 5. creating a domain with xl[_works_] 6. yum install libvirt-daemon-xen virt-manager virt-viewer \ python-virt-inst libvirt-daemon-config-network 7. rpm -qa | grep daemon-driver-libxl [yes, 0.10.2.3-1] 8. rpm -qa | grep daemon-driver-xen [yes, 0.10.2.3-1] 9. reboot (just in case!) 10. ps aux | grep xend [nothing found] 11. systemctl status libvirtd.service [active (running)] 12. start virt manager [connected to xen:// (I can't see Dom0, but that is fine, IIRC)] 13. ps aux | grep xend [nothing found] 14. creating a domain with xl [_works_] 15. creating a domain with virt-install [_DOES_NOT_ work (*)] Check /var/log/libvirt/libxl/libxl.log to see what went wrong. I have done some testing and in my case it seems it defaults to trying the blktap driver for disks, which won't work with the Fedora kernel. There may be some way to get it to use file, phy or other driver as you can with an xl configuration file, but I haven't found a way that works yet. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
On Tue, 12 Feb 2013, M A Young wrote: Let me try (again), repeating all the steps, starting from a fresh F18 install. After that, we'll decide if we want to stick with 893699 bugzilla entry, or create a new one, or whatever else we want to do... Ok, here I am. 1. Install F18 2. yum install xen 3. reboot 4. ps aux | grep xend [nothing found] 5. creating a domain with xl[_works_] 6. yum install libvirt-daemon-xen virt-manager virt-viewer \ python-virt-inst libvirt-daemon-config-network 7. rpm -qa | grep daemon-driver-libxl [yes, 0.10.2.3-1] 8. rpm -qa | grep daemon-driver-xen [yes, 0.10.2.3-1] 9. reboot (just in case!) 10. ps aux | grep xend [nothing found] 11. systemctl status libvirtd.service [active (running)] 12. start virt manager [connected to xen:// (I can't see Dom0, but that is fine, IIRC)] 13. ps aux | grep xend [nothing found] 14. creating a domain with xl [_works_] 15. creating a domain with virt-install [_DOES_NOT_ work (*)] Check /var/log/libvirt/libxl/libxl.log to see what went wrong. I have done some testing and in my case it seems it defaults to trying the blktap driver for disks, which won't work with the Fedora kernel. There may be some way to get it to use file, phy or other driver as you can with an xl configuration file, but I haven't found a way that works yet. Actually, in your case you could try --disk path=/dev/vms/F18_x64,driver_name=phy . Unfortunately driver_name=file doesn't work for a disk image file as it seems that uses blktap, which is arguably a libvirt libxl driver bug. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
On Fri, 8 Feb 2013, Major Hayden wrote: After removing libvirt-daemon-driver-libxl, I noticed that libvirt-daemon-xen was removed along with it as a dependency. Creating VM's failed again with an error during the hotplug of the vif. I decided to get a little more forceful: yum -y install libvirt-daemon-xen rpm -ev --nodeps libvirt-daemon-driver-libxl I restarted the libvirtd daemon and now I'm creating VM's without any errors. Am I alone on this one? I was about to pop something in Bugzilla for it but I figured I'd ask the list just in case. If this belongs on the fedora-virt list, please throw a large piece of furniture in my general direction and I'll try to remember next time. ;) libvirt-daemon-xen is just a metapackage which pulls in packages you might want to use when using libvirt with xen, so it will go if you remove libvirt-daemon-driver-libxl but removing it doesn't change anything else. I suspect it was the libvirt restart that fixed your problems. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Updating xen package does not 'refresh' grub.cfg
On Wed, 23 Jan 2013, Dario Faggioli wrote: Just booting another option, executing manually `grub2-mkconfig -o /boot/grub/grub.cfg' and rebooting again did the trick. The standard Fedora location for the grub2 configuration file is /boot/grub2/grub.cfg and this is updated for me when the xen-hypervisor package is updated, so I am not sure why your configuration is there. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 4.2.1-rc2 available to test
Here is another temporary test build (on Fedora 17). This one is for the second release candidate of xen-4.2.1 and is available for testing at http://koji.fedoraproject.org/koji/taskinfo?taskID=4783768 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen 4.2 in rawhide
On Sat, 27 Oct 2012, Cole Robinson wrote: On 10/26/2012 10:01 AM, M A Young wrote: On Fri, 26 Oct 2012, George Dunlap wrote: What's the code freeze date for Fedora 18? There are some people working on 4.2 support for libvirt, so if that was working within the next month or two, could it be back-ported to the libvirt in Fedora? The final change deadline is currently 26th November. That may not be an absolute deadline, but you have a better chance of the libvirt team accepting changes before then. Whenever the patches land upstream I'll be happy to pull them into F18. Even if they don't show up for a few months we can always just push an F18 update after GA. Of course, sooner would be better :) I noticed today that a patch for libvirt to work with libxl from xen 4.2 has been sent to the libvir-list https://www.redhat.com/archives/libvir-list/2012-November/msg01119.html I did a bit of testing and got the F18 libvirt to build against xen 4.2 (the patch needed some minor tweaks). I haven't tested if it actually works. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 4.1.4-rc1 available to test
Here is a temporary test build (on Fedora 17) of the first release candidate of xen-4.1.4 available for testing at http://koji.fedoraproject.org/koji/taskinfo?taskID=4699286 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 4.2.1-rc1 available to test
I have a temporary test build (on Fedora 17) of the first release candidate of xen-4.2.1 available for testing at http://koji.fedoraproject.org/koji/taskinfo?taskID=4694272 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Installing a domU without virt-install
On Thu, 1 Nov 2012, Andy Burns wrote: [Re-sent from my list subscribed email address, sorry] I've got a Fedora 17 dom0, running under Xen 4.2 (thanks to the Pasi's archive of Michael's test SRPM at http://pasik.reaktio.net/fedora/xen/xen-4.2.0-0.1.fc17.src.rpm) Note there are now official xen-4.2.0 packages for F18 and F19. They should rebuild on F17, though offical F17 builds will stick to the 4.1 branch. Since there's no libvirt support in that build, I had to uninstall the existing virt-* tools too, therefore no helpers to create a new domU. However, a link on LWN reminded me of http://boot.fedoraproject.org/ and I wondered if I could use that to get a new domU installed. You could try the virt preview repository http://fedoraproject.org/wiki/Virtualization_Preview_Repository That looks like it has a F17 build of the latest F18/F19 libvirt which disables the libxl driver so it doesn't conflict with xen-4.2 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] xen 4.2 and libvirt
On Wed, 31 Oct 2012, Dario Faggioli wrote: ... Error: Package: libvirt-daemon-driver-libxl-0.10.2.1-1.fc18.x86_64 (updates-testing) Requires: libxenctrl.so.4.0()(64bit) Available: xen-libs-4.1.3-4.fc18.x86_64 (fedora) libxenctrl.so.4.0()(64bit) Installed: xen-libs-4.2.0-3.fc18.x86_64 (@updates-testing) Not found ... It should be okay once libvirt-0.10.2.1-2.fc18 gets to the updates-testing repository. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen install test: On Fedora 17, install Fedora 17. Mouse problem?
On Tue, 30 Oct 2012, Marko Ristola wrote: I don't have a bugzilla report item from this yet, maybe later. I have now Xen Dom0 Fedora 17 configuration, no experimental packages. Desktop computer is rather new and supports hardware virtualization, but not IOMMU. Test: Install paravirtual 64 bit Xen guest, Fedora 17 with HTTP based install. - With Virt-manager installing went flawlessly. - After reboot, I got in Finnish with a graphical picture: Voi ei! Jotain meni pieleen. This means Oh no, something got wrong. So it seems that GDM doesn't work with Xen with default virt-manager settings. It could be https://bugzilla.redhat.com/show_bug.cgi?id=810040 try removing the fprintd package (plus fprintd-pam I think for dependencies) - I can make Login screen by switching from GDM to KDM. Mouse works there: /etc/sysconfig/desktop: DISPLAYMANAGER=KDE - From KDM I can start Gnome. Mouse works but Mouse cursor is invisible. - If I start, via KDM, IceWM, mouse works and is visible. I don't know if Fedora 18 will have this issue too. It would be nice if Fedora as Dom0 would just work for Fedora Xen DomU with default options. Maybe plain AbsoluteAxis for paravirtual mouse would be the best option, no relative axis enabled by default? Maybe co-operation with Gnome people is needed to finish this issue? I see the invisible cursor as well, though I have never got around to raising a bug for it for some reason. It seems to be peculiar to gnome (and not gnome on ubuntu 10.0.4), for example the cursor is shown on text screens before gnome starts. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen 4.2 in rawhide
On Fri, 26 Oct 2012, George Dunlap wrote: What's the code freeze date for Fedora 18? There are some people working on 4.2 support for libvirt, so if that was working within the next month or two, could it be back-ported to the libvirt in Fedora? The final change deadline is currently 26th November. That may not be an absolute deadline, but you have a better chance of the libvirt team accepting changes before then. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Xen 4.2 in rawhide
Xen has been updated to version 4.2.0 in rawhide. To get this to work Cole Robinson has disabled libxl support in libvirt because libvirt doesn't yet support the 4.2 updates to libxl. There should still be time to get xen 4.2 into Fedora 18 if there aren't any problems in rawhide. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] pciback at boot time
On Mon, 15 Oct 2012, Gordon McLellan wrote: pciback is compiled as a module: [root@xenhost ~]# grep BACKEND /boot/config-3.6.1-1.fc17.x86_64 CONFIG_XEN_BLKDEV_BACKEND=m CONFIG_XEN_NETDEV_BACKEND=m CONFIG_XEN_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND=m and the file does exist: [root@xenhost ~]# ls -lah /lib/modules/3.6.1-1.fc17.x86_64/kernel/drivers/xen/xen-pciback/ total 108K drwxr-xr-x 2 root root 4.0K Oct 12 10:19 . drwxr-xr-x 4 root root 4.0K Oct 12 10:19 .. -rwxr--r-- 1 root root 100K Oct 10 08:41 xen-pciback.ko Near as I can tell the 0) is coming from the kernel command line but it is getting mangled somewhere along the way. If I remove the xen-pciback.hide directive from the grub config file, the kernel is able to load the pciback module without issue, and without any configuration. I tried moving the xen-pciback.hide directive to the front of the kernel command line, it did not help. From dmesg: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.6.1-1.fc17.x86_64 (mockbuild@) (gcc version 4.7.2 20120921 (Red Hat 4.7.2-2) (GCC) ) #1 SMP Wed Oct 10 12:13:05 UTC 2012 [0.00] Command line: placeholder root=/dev/mapper/vg0-root ro xen-pciback.hide=(0b:00.0)(09:00.0) rd.md=0 rd.dm=0 rd.lvm.lv=vg0/swap KEYTABLE=us rd.lvm.lv=vg0/root rd.luks=0 LANG=en_US.UTF-8 If you haven't already done so I suggest you get rid of anything in /etc/modprobe.d/ you added, just in case that is getting in the way. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] pciback at boot time
On Sun, 14 Oct 2012, Gordon McLellan wrote: Thank you for the tips. I made sure I specified xen-pciback instead of the older pciback ... not really sure which line in the configuration it goes on in /etc/default/grub - leaving it on the XEN line for now. I created /etc/modprobe.d/xen-pciback.conf to also reflect the same: options xen-pcibackhide='(:00:1a.0)(:00:1b.0)(:00:1d.0)(:01:00.0)(:01:00.1 )(:00:0b.0)' after making these changes, I updated the grub config file and rebooted. After reboot, none of the devices are hidden from dom0. I can forcibly unbind them from dom0 with a script, but that seems messy and some of the pci devices don't seem to like it (sata controller for example) Any suggestions? Could you try without the leading : in one or both places. I have been looking at http://wiki.xen.org/wiki/Xen_PCI_Passthrough and the examples there don't have the leading : . Michael Young-- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 4.2 released!
I have a temporary build of xen-4.2.0 at http://koji.fedoraproject.org/koji/taskinfo?taskID=4493396 I would like to know a bit more about libvirt support for 4.2 before I do any proper releases as I know a lot of people use xen via libvirt. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 4.2.0-rc3 available to test
There is a temporary test build of the new release candidate, 4.2.0-rc3 at http://koji.fedoraproject.org/koji/taskinfo?taskID=4418551 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 4.2.0-rc2 available to test
I have done a temporary build of 4.2.0-rc2 for testing which is at http://koji.fedoraproject.org/koji/taskinfo?taskID=4386920 This also adds the efi hypervisor back in for x86_64. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Xen, Fedora, and UEFI Secure Boot
I contacted the people behind the the Fedora Seure Boot feature and got the following responses, from Peter Jones: Okay, to be honest I don't remember much about Xen's layout - dom0 is the management kernel the hypervisor starts? So, depending on how xen works, there are probably more things that need to be done in the hypervisor than in the kernel, because the hypervisor is the part that does most physical memory accesses, and that's where there's a worry about faking SB=0 and launching windows. At the very least, the hypervisor will a) need to be an efi binary, and b) need to be signed with the fedora kernel-signing key. It may also need to be audited for any command line options that allow physical memory access or other similar things, analogous to Matthew's kernel patch for linux. We're still working out with rel-eng how getting things signed with that is going to work. I don't think there's really any necessity that it's announced in a proper Feature, but if you feel like going that way, that's fine too. and from Matthew Garrett: Right. We can conceivably sign Xen as long as it's an EFI binary, but I'd expect that it would have to enforce secure boot itself using the host databases. -- So we need to get xen working with EFI, to lock xen down so it can't be used to get around Secure Boot, and probably need to do some enforcement of secure boot as well. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen, Fedora, and UEFI Secure Boot
On Wed, 11 Jul 2012, Dario Faggioli wrote: On Thu, 2012-07-05 at 11:04 -0400, Konrad Rzeszutek Wilk wrote: Ok, so, should we be concerned? Is there something we can/should do about that? How do you think we can help in having xen being considered? First the Linux kernel running under EFI has to actually boot (with Xen hypervisor). It doesn't do that yet and the upstream kernel would need patches for that. Yes, I can imagine there are technical challenges and open issues, but (although, of course, I might be wrong), that is not what scares me most... I really think there are good enough brains working on them! :-) What I wanted to know here is whether or not there already are plans to include the xen binaries in that signing game, so that Fedora users can still `yum install xen -- reboot --start playing' as it is happening now, and, more important, if that is not the case what we can do to help this. Is the fact that Fedora release guidelines include Xen _guest_ support but not full _host_ functionalities going to be an issue if/when we decide to try influencing this http://fedoraproject.org/wiki/Features/SecureBoot ? In terms of getting xen into the Fedora signing game we would either need to get the people behind the SecureBoot feature to add xen or submit our own feature to add that functionality (I haven't contacted them but I guess they would prefer the latter). With regard to technical challenges I wonder what if any signature checking xen itself would need to do (for example would it check the signature on the dom0 kernel or would grub2 do that) because part of the securing process would be to ensure that xen itself didn't leave open doors to break into the secure system. Also there is the question of drivers as I gather they need to be signed to talk to bios devices, which may simply be a pass through of the dom0 kernel signed drivers or might be more complicated. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen, Fedora, and UEFI Secure Boot
On Tue, 3 Jul 2012, Dario Faggioli wrote: On Fri, 2012-06-29 at 15:18 +0100, M A Young wrote: Fedora's plans seem to be at http://fedoraproject.org/wiki/Features/SecureBoot Another good article I stumbled upon about what Fedora plans is at http://mjg59.dreamwidth.org/12368.html Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen/Linux 3.4.2 performance
On Mon, 2 Jul 2012, W. Michael Petullo wrote: We have seen a significant reduction in performance in our research DomU OS kernel when running on Fedora 16 with Linux 3.4.2 vs. 3.3.7. We run a series of benchmarks which are DomU-kernel-space-CPU-heavy; many of these run 10x slower when using the 3.4.2 Linux kernel as Dom0. This is a little surprising---we've been tracking the Fedora kernels for a long time with no problem like this. Did anyone else notice any changes? I have noticed a slow boot on one of my systems and it has been known to loose connections with keyboard and mouse when a guest is started. Given the previous issues with this system I suspect IRQ issues with the kernel interacting with xen though I haven't investigated further. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Can't text install DomU
On Thu, 7 Jun 2012, Cole Robinson wrote: There have been several reports of this issue so I don't think it's specific to your config. Indeed, looking at the xen spec file, this regressed a bit with the switch to systemd. xenconsoled used to be enabled at runlevels 345, but now it is never explicitly enabled with systemctl enable xenconsoled. This differs from xenstored, which was previously enabled at runlevel 345, and now _is_ explicitly systemctl enabled. Yes, that is my fault. When I was moving to systemd I was trying to decide what was and wasn't needed, and I think I decided that xenconsoled was optional (for the way I do xen it wasn't needed), so didn't enable it by default. It should only be an issue on F17 and rawhide as I stopped the systemd migration on F16 when it was released and xenconsoled was migrated afterwards. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen 4.2 pre build available to test
On Wed, 6 Jun 2012, Konrad Rzeszutek Wilk wrote: Should I use F17 and then dump the images or would you recommend F18(rawhide?) I don't think it matters whether you use F17 or F18 (though they are compiled against F17 so that is more likely to work). Incidentally, I tried rebuilding libvirt against this version of xen but it doesn't build, even if I add a patch that is supposed to get it to work. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Change xen package owner away from xen-maint?
On Tue, 15 May 2012, Cole Robinson wrote: Hey folks. Right now the package owner for xen in fedora is the xen-maint alias account. Originally this was an alias that was mapped to various @redhat folks who were doing xen development, and was used for both fedora and internal RHEL stuff. Nowadays it's not really used in upstream/fedora land and fedora-virt-maint is a better suited alias. Additionally @redhat isn't doing much xen work these days so we should just have a single package owner which reflects reality. So I propose we drop xen-maint as the package owner, and Michael can 'officially' take on package ownership. If that sounds fine I'll file a ticket with fedora infrastructure to make the change (required AFAIK for alias account changes). Michael, does that sound good to you? Yes, it sounds good to me. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 4.1.3-rc1 available to test
I have built 4.1.3-rc1 for F17 and it is temporarily available for testing at http://koji.fedoraproject.org/koji/taskinfo?taskID=4063767 . Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Reminder: Fedora 17 virt test day going on right now!
On Fri, 4 May 2012, Konrad Rzeszutek Wilk wrote: On Fri, May 04, 2012 at 09:36:49AM -0400, Gordon McLellan wrote: I'm going to buy a serial card for this machine so I can do the serial console on Xen and get more information. But so far, so good! You can try to do (on Xen) 'console=vga vga=text-80x50 guest_loglvl=all loglvl=all noreboot and on the Linux command line: console=hvc0 earlyprintk=xen loglevel=8 debug radeon.modeset=0 radeon.modeset=0 That should give you some idea where it is crashing and take a photo. If you are capturing logging with a photo, it can be helpful to add a boot_delay parameter eg. boot_delay=100 to the kernel line, particularly if the interesting lines scroll off the top of the screen before you can capture them. It does slow the boot down considerably though so you may need to adjust the parameter to get the balance right between it being slow enough to capture without taking ages to get to the crash. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 12 x86_64, Xen 4.0.1-6 and Fedora 16 domU
On Wed, 25 Jan 2012, Roberto Fichera wrote: 2) Running pygrub directly to see if it works or gives useful debugging ie. pygrub partition or image file The pygrub menu starts and after a second or so I got this: pygrub /dev/disk/by-path/ip-10.0.0.1:3260-iscsi-iqn.2009-12.it.tekno-soft:xen.vm.TeknoProxy-lun-1 Using class 'grub.GrubConf.GrubConfigFile' to parse /grub/menu.lst Traceback (most recent call last): File /usr/bin/pygrub, line 715, in module data = fs.open_file(chosencfg[kernel]).read() IOError: [Errno 2] No such file or directory As I can see the /grub2/grub.cfg contains a valid grub2 configuration. In pygrub in 4.1 grub gets checked before grub2, and I can't remember if it goes on to check grub2 locations if it finds a grub related file which doesn't work. I suggest you move or rename /grub/grub.conf and /grub/menu.lst so pygrub doesn't get confused by them. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 12 x86_64, Xen 4.0.1-6 and Fedora 16 domU
On Tue, 24 Jan 2012, Roberto Fichera wrote: My thought is that since Fedora 16 comes with grub2, my current xen setup doesn't support it. It doesn't. The most recent F16 xen (4.1.1-8 or later) should though (the patches for Fedora style grub2 support are upstream in the 4.1 and unstable development trees but not in any released version yet). You could try 1) turning selinux off (setenforce 0) if it is on. 2) Running pygrub directly to see if it works or gives useful debugging ie. pygrub partition or image file Note if you are using pvgrub as your boot loader then it is unlikely to cope with F16 guests. Another possibility is that your upgrade didn't generate a valid grub2 configuration, so there is nothing for the boot loader to find. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] beginner question
On Wed, 11 Jan 2012, Itamar Reis Peixoto wrote: On Wed, Jan 11, 2012 at 2:00 PM, Gergely Buday gbu...@gmail.com wrote: I have installed xen through yum. How can I start it? I started xend via its init.d script but still xm info says that it cannot connect xend. What should I do then? what version of fedora / centos are you using ? Fedora 15. On amd x64. - Gergely fedora 16 or newer have support for xen dom0 But it will work on F15 if you have a recent kernel update. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen broke my system
On Tue, 6 Dec 2011, Carlos Felipe Santacruz wrote: This is what happened: normally ran 'yum install xen' and that gave no problems, but then i rebooted to get to the xen kernel, it resulted on black screen (could change consoles with Alt + F2 etc.) so i rebooted and tried the regular 3.1.2 kernel with same results. uninstalled xen with 'yum history undo' so it would also remove all dependencies then rebooted. nothing. anyone knows what could have caused this? im running f16 x86_64 on an asus g74sx-bbk7(core i7-2630qm, geforce gtx560m, 8GB DDR3 ram) Xen runs the grub2 update script to give you an option to boot the kernel with the hypervisor. This is different from the way Fedora handles grub2 configuration when you add a kernel, as their method doesn't work with xen. However there is a risk that you will lose configuration options if the Fedora system hasn't set up grub2 correctly. This did happen while Fedora 16 was in beta as grub2 overwrote a configuration file when you updated it until they fixed it, but I am not sure if this is still a problem. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen build for testing
On Mon, 21 Nov 2011, Pasi Kärkkäinen wrote: There's an updated version of the second patch in here: http://old-list-archives.xen.org/archives/html/xen-devel/2011-11/msg01257.html and http://xenbits.xen.org/hg/staging/xen-4.1-testing.hg/rev/5a00ccfc6391 It fixes a bug with Linux 2.6.32 dom0 kernels. I have put the revised patch in 4.1.2-2 with other fixes and changes. It is available via koji http://koji.fedoraproject.org/koji/buildinfo?buildID=275077 and I will push it to updates-testing once I have done a bit of testing. Michael Young-- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] [PATCH] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out)
On Wed, 16 Nov 2011, Pasi Kärkkäinen wrote: On Wed, Nov 16, 2011 at 03:00:25PM +, Keir Fraser wrote: I responded on 3rd November: This looks like a backport of Stefano's xen-unstable c/s 24007. I would like him to submit/ack the backport, as it is not a trivial backport of the xen-unstable patch. Stefano already submitted a new patch for this.. The patch we have been testing is from this email http://lists.xensource.com/archives/html/xen-devel/2011-11/msg00321.html from Stephano. Michael Young-- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Current dom0 kernel for F15/16
On Mon, 7 Nov 2011, Robert Brown wrote: To move beyond Fedora 14 and update to 15/16, I need a more recent kernel as F15 won't install otherwise. I have read through the list and can't seem to locate a Fedora 15-supported prerolled kernel or SRPM. Does this exist, and if so can someone kindly point me to the proper location? Or is the current preferred approach to compile your own kernel? If this is the suggested approach, are there any special requirements for this or kernel options to be enabled/disabled? For F15 and F16 you can use the latest Fedora kernel for that version. Standard kernels from 3.0 onwards have the core xen patches included, F16 has 3.1 and the latest F15 kernel is 3.0 (rebadged as 2.6.40) and it should get 3.1 (possibly rebadged) shortly. Michael Young-- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] xen build for testing
I have done a temporary test build xen-4.1.2-1.1 at http://koji.fedoraproject.org/koji/taskinfo?taskID=3495905 which contains patches from http://lists.xensource.com/archives/html/xen-devel/2011-11/msg00218.html http://lists.xensource.com/archives/html/xen-devel/2011-11/msg00321.html which I would like to test before putting them into a released version. If anyone else wants to test it, please let me know whether it works. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Grubby Issues with F16 Dom0
On Mon, 24 Oct 2011, Tim Flink wrote: Just as a heads up, there seem to be a couple of issues with grubby and the grub.cfg submenus used for Xen right now. My system still boots after triggering any of these but it's usually not running Xen and not always running the kernel I want it to be running. I have seen what I suspect is another one though I haven't investigated fully yet to confirm it. I think that if you delete a kernel with a xen entry it can remove a submenu opening clause but not the corresponding closing } which is bad if you have the xen hypervisor installed in a guest as it upsets pygrub. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen release candidates to test
Here is the next batch of release candidates to test - 4.0.3-rc3 built for Fedora 14 is (temporarily) at http://koji.fedoraproject.org/koji/taskinfo?taskID=3414611 4.1.2-rc3 for Fedora 15 is (temporarily) at http://koji.fedoraproject.org/koji/taskinfo?taskID=3414766 and for Fedora 16 is (temporarily) at http://koji.fedoraproject.org/koji/taskinfo?taskID=3414876 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen release candidates to test
Here are the next set of release candidates, to test. 4.0.3-rc2 built for Fedora 14 is (temporarily) at http://koji.fedoraproject.org/koji/taskinfo?taskID=365 and 4.1.2-rc2 built for Fedora 15 is (temporarily) at http://koji.fedoraproject.org/koji/taskinfo?taskID=299 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen and fedora
On Tue, 24 May 2011, Mike McClurg wrote: On Tue, May 24, 2011 at 6:43 PM, Lefu Ntho lefun...@gmail.com wrote: hi Mike, indeed it got to me, I think what I am trying to find out is steps to take before I execute dracut. because the tutorial states for fc13, I think guys have already done this on fc14. I attempted to fetch and install myoung kernel but it fails as its build for earlier kernel version than the one I have. It should work if you yum install the specific kernel version. Or you can download it and run rpm -ivh --oldpackage . You won't be able to run xen with your stock Fedora 14 kernel. You'll have to replace it completely with a xen-capable kernel, like Jeremy's 2.6.32 kernel that you build yourself, or one of the ones that myoung built for Fedora 12. Though a stock Fedora 16 kernel will work (with xen 4.1 and xl). Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen and fedora
On Wed, 25 May 2011, Steven Haigh wrote: On 25/05/2011 4:20 AM, M A Young wrote: Though a stock Fedora 16 kernel will work (with xen 4.1 and xl). Sorry, does this mean an F16 kernel will work as a Dom0 with no issues? Or do I have my wires crossed here! :) Well, you have to set up grub yourself to get it to boot dom0, and you would be using qemu instead of blkback so disk access is slow, but xen network support is in the kernel, and thus you can indeed use it as a Dom0. I don't tend to use the more advanced xen features, so I am not sure which are supported and which aren't. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fwd: xen and fedora
On Wed, 25 May 2011, Lefu Ntho wrote: and correctly so, Michael, that --oldpackage did the trick, thanx a lot, I have bravely removed previously installed xen and kernel, I then reinstalled xen and kernel-2.6.32.39 via yum, rebooted the machine remotely, I executed uname -r and 2.6.32.39-175.xendom0.fc13.x86_64 is returned :) but vm info Error: Unable to connect to xend: No such file or directory. Is xend running? Did you edit grub.conf to allow the kernel to boot via the hypervisor? That kernel doesn't do it for you. You want something along the lines of Title something root (hd?,?) kernel /xen.gz or /boot/xen.gz module /vmlinuz-something kernel_boot_args module /initramfs-something adjusted to match your boot environment as given by the other grub entries. Michael Young-- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] xen packages to test
I have a couple of temporary builds of xen release candidates available for testing; xen-4.0.2-rc4 built for F14 at http://koji.fedoraproject.org/koji/taskinfo?taskID=3085546 and xen-4.1.1-rc1 built for F15 at http://koji.fedoraproject.org/koji/taskinfo?taskID=3086043 Also if you are interested in testing packages for RHEL6 see http://koji.fedoraproject.org/koji/taskinfo?taskID=3086043 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] How to compile Jeremy's dom0 pvops kernel (2.6.32.x) on Fedora 15
On Tue, 3 May 2011, Pasi Kärkkäinen wrote: I asked because one of the errors looked like running out of disk space.. unifdef: /home/xen_repo/linux-2.6-xen/usr/include/xen/privcmd.h.tmp: 79: Premature EOF (#if line 33 depth 1) unifdef: output may be truncated That is a fairly standard error. It doesn't seem to cause problems. Michael Young-- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.32 dom0 kernel
Here is another 2.6.32 kernel, based on my Fedora 12 kernels but updated to 2.6.32.39, and a recent xen stable-2.6.32 patch. It is available (temporarily) from koji at http://koji.fedoraproject.org/koji/taskinfo?taskID=3027978 - this isn't yet in the repository, but I may update that with the kernel at somme point. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Xen 4.0.2 rc3 available to test
I have done a test build of the latest xen 4.0.2 release candidate at http://koji.fedoraproject.org/koji/taskinfo?taskID=2998474 . I intend to update xen to 4.0.2 on F14 once it is released. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen 4.1.0-rc8
On Fri, 25 Mar 2011, fcxen user wrote: Also, do you anticipate then updating these packages throughout the life of F15 (even if they are just in testing or some other repo)? My general policy for the xen package is to stick with the main xen version it was released with, so F13 is 3.4.3, F14 is 4.0.1 and probably won't go to 4.1.0, but probably would go to 4.0.2 when it appears, and I imagine F15 with remain on 4.1.x though its life. The kernel situation is different because there is no official kernel that provides satisfactory dom0 support (so far), so I expect I will keep building dom0 kernels which should work on F15, at least until there is a reasonable official Fedora kernel. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 2.6.32 dom0 kernel
I have built a new 2.6.32 kernel, based on my Fedora 12 kernels, but with updates to the latest 2.6.32 kernel patch (2.6.32.34 with the extra patch to make it equivalent to 2.6.32.35) and latest xen next-2.6.32 patch. It was built on Fedora 13. It is available (temporarily) from koji at http://koji.fedoraproject.org/koji/taskinfo?taskID=2940510 and from my repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen 4.1.0-rc8
On Mon, 21 Mar 2011, M A Young wrote: We got another release candidiate xen-4.1.0-rc8 instead, built at http://koji.fedoraproject.org/koji/taskinfo?taskID=2929815 The final release has slipped to Friday. I am considering building the release candidate as an official rawhide/F15 package so I can be sure to get it into F15 in time for the Beta release. I have now done offical builds of a slightly tidied up version of the above build for rawhide and Fedora 15 which are available at http://koji.fedoraproject.org/koji/packageinfo?packageID=7 . Let me know if there are any problems. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] xen 4.1.0-rc8
On Thu, 17 Mar 2011, M A Young wrote: I have a build of xen-4.1.0-rc7 at http://koji.fedoraproject.org/koji/taskinfo?taskID=2918588 which is expected to be the last release candidate with the final release scheduled for Monday. We got another release candidiate xen-4.1.0-rc8 instead, built at http://koji.fedoraproject.org/koji/taskinfo?taskID=2929815 The final release has slipped to Friday. I am considering building the release candidate as an official rawhide/F15 package so I can be sure to get it into F15 in time for the Beta release. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Testing Xen dom0 for Fedora 15
On Sat, 19 Mar 2011, Pasi Kärkkäinen wrote: I assume Fedora 15 will ship with 2.6.38 kernel? That is what the current F15 kernel is, 2.6.39 won't be ready for another couple of months, so it is highly likely. There was some discussions earlier if we could add the various xen backend drivers as additional patches for F15 kernel.. what was the end result of that discussion? It was left open, because we didn't know what the patches would be at the time. Michael Young-- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] xen 4.1.0-rc6
It took me a while to spot it was out, but I have now done a build of xen-4.1.0-rc6 which is at http://koji.fedoraproject.org/koji/taskinfo?taskID=2891904 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] current docs to install xen on f14
On Sun, 6 Mar 2011, Mike Wright wrote: Installed myoung's latest f12.xendom0 which boots and runs in f14 environment but when set to boot xen.gz with modules vmlinuz and initrmfs system segfaults From what I can see on bootup (first time I couldn't make a machine go *slow* enough ;) xen.gz boots successfully but fails almost immediately after beginning to load the kernel. Motherboard has no com ports and the bios' default font size is so large that whatever error messages scroll away. To change the font add vga=ask,keep to the xen line and console=hvc0 to the kernel line, then pick a resolution when prompted. You may also need to add earlyprintk=xen to the kernel line. Another thing to try is adding dom0_mem=max:2GB to the xen line as there have been problems with letting the Dom0 have too much memory. Micahel Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Another 2.6.38-rc6 dom0 kernel
Here is another kernel (2.6.38-0.rc6.git6.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2874240 The crash when a domU shuts down seems to be fixed. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 2.6.38-rc6 dom0 kernel
Here is another kernel (2.6.38-0.rc6.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2861178 . This comes with a warning because for me the dom0 system reboots when a domU guest is shutdown. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Error Path closed or removed during hotplug with xen-4.0.1 on Fedora 14 (x86_64)
On Tue, 22 Feb 2011, Kaustav Dey Biswas wrote: I am running xen-4.0.1 on Fedora 14 (x86_64) with kernel 2.6.38-0.rc4. All xen modules are loaded correctly. # lsmod | grep xen xen_netback 24607 0 [permanent] xen_gntdev 9063 0 xen_evtchn 5179 1 xenfs 9917 1 I have created images of Ubuntu (maverick) Debian (squeeze) using xen-create-image. However, when I try to boot the images using xm, I am getting the following error (for both Debian Ubuntu): xm doesn't support the qemu block backend you need with that kernel. Use xl instead. You may also find that you need the more recent xl from the 4.1.0-rc versions of xen. Michael Young-- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] xen 4.1.0 rc5
There is a build of the newly released xen release candidate for xen-4.1.0-rc5 at http://koji.fedoraproject.org/koji/taskinfo?taskID=2845415 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc4 dom0 kernel
On Fri, 11 Feb 2011, W. Michael Petullo wrote: I just booted 2.6.38-0.rc4.git3.1.xendom0.fc15 on xen-4.1.0-0.1.rc4.fc14.x86_64. I end up with the xen_netback kernel module loaded: $ lsmod | grep net xen_netback24607 0 [permanent] I'm not sure if this is what you were refering to by indeed the hack stops xen-netback loading... The latest dom0 kernel and the latest xen rc should work unaltered. The hack I referred to was an edit to a file from the xen rc to get the previous dom0 kernel working. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] New xen RCs
I have some new xen release candidate packages for you to test. They are xen-4.0.2-0.rc2.fc14 at http://koji.fedoraproject.org/koji/taskinfo?taskID=2830813 and xen-4.1.0-0.1.rc4.fc14 at http://koji.fedoraproject.org/koji/taskinfo?taskID=2830883 Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xl create ... -c
On Fri, 11 Feb 2011, W. Michael Petullo wrote: Has anyone else noticed that xl create DOM -c does not work when using xen-runtime-4.1.0-0.1.rc4.fc14.x86_64? xl create -c DOM does though, so it looks like the help output doesn't match the actual usage. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 2.6.38-rc4 dom0 kernel
I have a new kernel (2.6.38-0.rc4.git3.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2833991 . This uses the Konrad's devel/next-2.6.38 branch (from http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git ), as I have been having trouble which Jeremy's xen/next-2.6.38 branch. It has the revised xen-netback patches, so doesn't need the hack to /etc/sysconfig/modules/xen.modules that the previous kernel needed to avoid backtraces (indeed the hack stops xen-netback loading with this kernel as the netback_kthread parameter has been dropped). Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] New xen RCs
On Fri, 11 Feb 2011, Marko Ristola wrote: I tried xen-4.1.0 rc4. Just as with xen-4.1.0 rc3, using same bleeding edge kernel 2.6.38-0.rc3.git0.1.xendom0.fc15.x86_64 in both dom0 and in 32 bit Ubuntu 10.10 guest, mouse move doesn't work but mouse clicks work. I don't know where the problem is (kernel / xen / other ). I have had trouble with the mouse in a DomU window one one machine I tested it on, though in that case it wouldn't click either. That was using xl with xen 4.1.0-rc on 2.6.38-rc3, xm on xen-4.0.x works. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] rc3 kernel and xen
On Thu, 3 Feb 2011, Digimer wrote: On 02/03/2011 08:28 AM, Digimer wrote: On 02/02/2011 11:02 PM, Digimer wrote: Another note; When I tried to sleep the machine, it hung. Screen went dark and the power button pulsed. I had to hard-reset the machine. :) Yet another; Normal power-off hung as well. Had to cold-boot the laptop. In case it matters, it's a Thinkpad T400s. note: taken under the plain kernel, not while booting via xen. lspci: http://pastebin.com/D5QJpb2b dmidecode: http://pastebin.com/mRMhragn cpuinfo: http://pastebin.com/P1hS8AYa uname: Linux lework.alteeve.com 2.6.38-0.rc3.git0.1.xendom0.fc15.x86_64 #1 SMP Tue Feb 1 23:35:33 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Try with kernel-2.6.38-0.rc3.git0.1.fc15 at http://koji.fedoraproject.org/koji/buildinfo?buildID=216558 (the latest regular rawhide kernel, though a later was is currently being built). If that shows the same behaviour you can probably file a bug somewhere (eg. http://bugzilla.redhat.com/ ) because it will be a Fedora or mainline kernel issue. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] rc3 kernel and xen
I have builds of a new dom0 kernel (2.6.38-0.rc3.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2755802 and xen (4.1.0-0.1.rc3.fc14) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2753907 You may need one or both of the following hacks Edit /etc/init.d/xenstored replacing the line XENSTORED_PID=/var/run/xenstore.pid with XENSTORED_PID=/var/run/xenstored.pid (I didn't notice they had changed the name of this file until after I tested the xen packages) Edit /etc/sysconfig/modules/xen.modules to remove xen-netback from the list of modules in the for loop then add modprobe xen-netback netback_kthread=1 to the end of the file. The xen-netback module in xen/next-2.6.38 when I built the kernel still needed some work and setting this value makes it less likely to throw up backtraces if you try to use it. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] rc3 kernel and xen
On Wed, 2 Feb 2011, Itamar Reis Peixoto wrote: On Wed, Feb 2, 2011 at 8:43 PM, M A Young m.a.yo...@durham.ac.uk wrote: I have builds of a new dom0 kernel (2.6.38-0.rc3.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2755802 and xen (4.1.0-0.1.rc3.fc14) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2753907 You may need one or both of the following hacks why the kernel is fc15 and xen is fc14 ? You are right, it isn't very consistent. The kernel is fc15 because it is actually a xenified version of current fc15 kernel, though it should work on other Fedora versions, and I use it on fc14 without any obvious additional problems. The xen package is fc14 because I am guessing that most people are still using fc14 and haven't switched to rawhide yet. I haven't tried the fc14 xen packages on rawhide, but I am not aware of any big differences that would cause them to break. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Thu, 27 Jan 2011, W. Michael Petullo wrote: When I try to use: disk = [ 'file:/tmp/openwrt-x86-xen_domu-rootfs-ext2.img,xvda,r', ] I get: [No boot] Error: Device 51712 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/13/51712 state: 1 I have finally got a domU to boot in this sort of situation, having found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub as a bootloader. Note that you may have to use xl rather than xm because they are deprecating xm and xm may not have support for qemu block backends. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Sun, 30 Jan 2011, W. Michael Petullo wrote: I have finally got a domU to boot in this sort of situation, having found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub as a bootloader. Note that you may have to use xl rather than xm because they are deprecating xm and xm may not have support for qemu block backends. Does anyone know where I can find documentatin on domain configuration for xl? There does not seem to be a man page and a review of the Xen Wiki did not find authoritative documentation. I am trying to figure out how to write an xl configuration, i.e., rewrite xmexample1 to work with xl. It is supposed to be a direct replacement for xm, the idea being for configuration files for xm to work for xl, though not necessarily the other way around. In practice, you can still find stuff that doesn't yet work. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-0.rc2.git3.2.xendom0.fc15 and power management
On Sat, 29 Jan 2011, W. Michael Petullo wrote: As reported earlier, I have been using 2.6.38-0.rc2.git3.2.xendom0.fc15 with good results. One thing I have come across is that power management does not seem to work. For example, pm-suspend does not suspend my system. Instead, the system merely becomes unresponsive. On the other hand, 2.6.32.26-174.2.xendom0 suspends fine. 2.6.38-0.rc2.git3.2.xendom0.fc15 also does not power down my system when I run shutdown. The last things that is printed to the console is: Halting system... [7962.081194] Power down. - The system halts but does not power down. Is 2.6.38-0.rc2.git3.1.xendom0.fc15 (at http://koji.fedoraproject.org/koji/taskinfo?taskID=2742521 ) any different? One of the patches I failed to apply in that one that was in git3.2 relates to shutting down, and I wonder if it has unintended consequences. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Thu, 27 Jan 2011, W. Michael Petullo wrote: Now, the last issue remaining for me is the backend drivers. My understanding is that, in the absence of backends being accepted upstream, we can use QEMU-based drivers. This would be acceptable for our work. Has anyone been using these with Fedora 15? In theory the block driver should work in 4.1.0, though I am not sure about the net driver. In practise I have failed so far to get the block driver working so far. This post today http://lists.xensource.com/archives/html/xen-devel/2011-01/msg01847.html talks about what block driver configurations should work. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] Dom0 xen support in Fedora 15?
On Thu, 20 Jan 2011, Bill McGonigle wrote: On 11/07/2010 03:55 PM, M A Young wrote: If the plan to get key xen drivers into 2.6.38 succeeds With the caveat that I don't really know what I'm looking for, I didn't see these make 2.6.38-rc1 (plenty of other Xen work, though). I saw a proposed patch for netback hit xen-devel yesterday. There was talk of userland netback and blkback in xen 4.1 which use the gntdev interface which did make it into 2.6.38 (userland blkback apparently gives the similar performance as the kernel one, netback is not as good). I am not sure of the details though, nor how you might use them if they are available. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] xen 4.1.0-rc1 build
Here is another release candidate to test, at http://koji.fedoraproject.org/koji/taskinfo?taskID=2722322 This is my first successful 4.1 build, and I haven't been particularly careful about the choices required to get it to build, so there are likely to be rough edges. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 2.6.37 dom0 kernel
There is a 2.6.37 kernel to test (2.6.37-1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2703408 I have had mixed success with this as the kernel package doesn't boot, but the kernel-debug package does boot to runlevel 3 (albeit with the couple of minutes delay which I have been seeing in the 2.6.37-rc kernels). Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 2.6.37-rc5 dom0 kernel
Here is another kernel to test (2.6.37-0.rc5.git0.1xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2651458 with the latest xen/next-2.6.37 patches. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] XenPvopsDom0, Fedora 15 Feature
On Mon, 29 Nov 2010, W. Michael Petullo wrote: I just completed some updates of https://fedoraproject.org/wiki/Features/XenPvopsDom0. I would like to submit this to the Fedora Feature Wranglers on Wednesday as a proposed feature for Fedora 15. If you are interested, please review the document and provide feedback. If you are a previous editor of the page, I hope you don't mind me trying to move this forward. I will appreciate any comments. With regard to the kernel, the Fedora kernel team currently expect Fedora 15 to ship with 2.6.38, see http://lists.fedoraproject.org/pipermail/kernel/2010-November/002849.html There are some comments relating to xen in a follow-up post. See http://lists.fedoraproject.org/pipermail/kernel/2010-November/002851.html So probably what we should do is provide a forked dom0 kernel for testing while F15 has 2.6.37 which should be as close as possible to what dom0 will look like in 2.6.38, then follow 2.6.38 once that appears in F15. With regard to xen versions, 4.1 is scheduled for mid to late Febrary, so we should be able to switch to that in time for F15. See http://lists.xensource.com/archives/html/xen-devel/2010-11/msg01349.html Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] 2.6.37-rc3 dom0 kernel
Here is an rc3 kernel (2.6.37-0.rc3.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2617730 It updates to the latest next-2.6.37 patch. I haven't tested it yet. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Compiling myoung's f12 dom0 on RHEL6
On Wed, 17 Nov 2010, Digimer wrote: On 11/17/2010 03:06 PM, M A Young wrote: On Wed, 17 Nov 2010, Digimer wrote: The source RPM depends on 'asciidoc', which isn't in the main Red Hat repository (at least, not that I could find). I was wondering what, exactly, needs asciidoc and if it would be safe/easy/possible/advisable to remove that dependency. It seems to be used in the perf Documentation. It is probably safe to remove, or you could get it from the EPEL repository (it is in EPEL5, I can't see it in EPEL6 yet). Michael Young A bit of a tangent, if I may. I just tried to install the recompiled kernel and it's complaining that it depends on 'kernel-firmware', which wasn't built. Was something extra needed at build time to have it created? Rebuild with --target=noarch Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
