Re: [Fedora-xen] Xen 4.4 RC2 [TestDay]
by M A Young
On Mon, 20 Jan 2014, Eric Houby wrote:
> The first issue I hit was:
>
> [root@astar ~]# xl create mars.xl
> Parsing config from mars.xl
> libxl: error: libxl_create.c:1034: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/1/image/device-model-pid
> libxl: error: libxl.c:1425:libxl__destroy_domid:
> libxl__destroy_device_model failed for 1
> 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 1
>
> After some discussion about the xencommons init script and ExecStartPost
> in xenstored.service, it was determined that manually
> running /usr/bin/xenstore-write "/local/domain/0/domid" 0 would fix the
> issue.
Was xenstored.service enabled? That should have set up the environment
correctly.
> [root@astar ~]# xl create mars.xl
> Parsing config from mars.xl
> libxl: error: libxl_dm.c:1371:device_model_spawn_outcome: domain 6
> device model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1166:domcreate_devmodel_started: device
> model did not start: -3
> libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already
> exited
>
> My qemu-dm-mars log file contained one line, Option xen-domid not
> supported for this target. This error led those helping to question
> about my qemu version and whether or not it supported xen.
One of the experiments I was intending to do with that build was to see if
xen would would work with Fedora's qemu. As you have just discovered the
answer is no, though the tools configuration option allowing you tell xen
where to find it seems to work. If you uninstall the qemu-system-x86
package or add the line
device_model_version="qemu-xen-traditional"
to your configuration file then your hvm guest should boot.
Michael Young
8 years, 10 months
Re: [Fedora-xen] CONFIG_XEN_PVH ?
by Konrad Rzeszutek Wilk
On Jun 19, 2014 12:15 AM, Bill McGonigle <bill(a)bfccomputing.com> wrote:
>
> > On Tue, Jun 03, 2014 at 02:12:17PM -0400, Bill McGonigle wrote:
> >> > Hi, everybody,
> >> >
> >> > Went to give PVH a try, seeing as we have 4.4 and 3.14 now in f20, but:
> >> >
> >> > # grep XEN.*PV /boot/config-3.14.4-200.fc20.x86_64
> >> > CONFIG_XEN_PVHVM=y
> >> > # CONFIG_XEN_PVH is not set
> >> > CONFIG_XEN_HAVE_PVMMU=y
>
> Posting my notes here, in case anybody else is trying it and wants to compare. I haven't yet had luck getting a pvh domU to launch. I think I'm doing what the documentation calls for, but clearly something is missing.
>
> Current bits are up here:
> https://www.bfccomputing.com/downloads/fedora/xen/f20/
>
> I've got Xen 4.4 booting and a kernel built with PVH support, but when starting a domU with 'pvh=1' I get:
>
> xc_dom_parse_image: unsupported feature requested
Could you also include 'xl dmesg' please?
>
> and the domain fails to build. I did verify that BUILD/kernel-foo/.config is getting the entry, and it sure looks like the symbols are in the kernel:
>
> [root@librescu xen]# grep -i pvh /boot/config-3.14.4-200.xenpvh.fc20.x86_64 /boot/System.map-3.14.4-200.xenpvh.fc20.x86_64
> /boot/config-3.14.4-200.xenpvh.fc20.x86_64:# Linux/x86_64 3.14.4-200.xenpvh.fc20.x86_64 Kernel Configuration
> /boot/config-3.14.4-200.xenpvh.fc20.x86_64:CONFIG_XEN_PVHVM=y
> /boot/config-3.14.4-200.xenpvh.fc20.x86_64:CONFIG_XEN_PVH=y
> /boot/System.map-3.14.4-200.xenpvh.fc20.x86_64:ffffffff81004340 t xen_pvh_set_cr_flags
> /boot/System.map-3.14.4-200.xenpvh.fc20.x86_64:ffffffff816e04d0 T xen_pvh_secondary_vcpu_init
> /boot/System.map-3.14.4-200.xenpvh.fc20.x86_64:ffffffff81d2a0a9 t xen_pvh_gnttab_setup
> /boot/System.map-3.14.4-200.xenpvh.fc20.x86_64:ffffffff81e5fd48 t __initcall_xen_pvh_gnttab_setup1
> [root@librescu xen]# uname -r
> 3.14.4-200.xenpvh.fc20.x86_64
>
> So, I'm not sure what's up. I added "loglvl=all guest_loglvl=all" to grub and can get another reboot in this weekend to see if there's any more info logged.
>
> It also looks like I should update my 4.4 tarball to the stable-4.4 branch for non-broken guest shutdowns (but one step at a time).
>
> -Bill
>
> --
> Bill McGonigle, Owner
> BFC Computing, LLC
> http://bfccomputing.com/
> Telephone: +1.855.SW.LIBRE
> Email, IM, VOIP: bill(a)bfccomputing.com
> VCard: http://bfccomputing.com/vcard/bill.vcf
> Social networks: bill_mcgonigle/bill.mcgonigle
> --
> xen mailing list
> xen(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/xen
9 years, 3 months
CONFIG_XEN_PVH ?
by Bill McGonigle
Hi, everybody,
Went to give PVH a try, seeing as we have 4.4 and 3.14 now in f20, but:
# grep XEN.*PV /boot/config-3.14.4-200.fc20.x86_64
CONFIG_XEN_PVHVM=y
# CONFIG_XEN_PVH is not set
CONFIG_XEN_HAVE_PVMMU=y
:(
Does anybody want to talk me out of recompiling my kernel to try it out?
If it's working should we ask for the f20 build to enable it? The docs
make it sound like PVH is how we're going to be running everything in
the not-too-distant future (and the design looks very sensible to me).
Just finished replacing my AMD SOHO box with a Xeon 2620 box to give it
a go (and also never got the AMD/UEFI box to properly allocate memory
pages to Dom0) which made ZFS unbearable; now at this stage.
-Bill
--
Bill McGonigle, Owner
BFC Computing, LLC
http://bfccomputing.com/
Telephone: +1.855.SW.LIBRE
Email, IM, VOIP: bill(a)bfccomputing.com
VCard: http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle
9 years, 3 months
building Xen from SRPM
by Bill McGonigle
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
RPM build errors:
Explicit %attr() mode not applicaple to symlink:
/home/flowerpt/rpmbuild/BUILDROOT/xen-4.3.2-1.fc20.x86_64/usr/lib64/xen/bin/qemu-dm
File listed twice: /var/run/xend/boot
Installed (but unpackaged) file(s) found:
/usr/lib/xen/boot/vtpm-stubdom.gz
/usr/lib/xen/boot/vtpmmgr-stubdom.gz
--
Bill McGonigle, Owner
BFC Computing, LLC
http://bfccomputing.com/
Telephone: +1.855.SW.LIBRE
Email, IM, VOIP: bill(a)bfccomputing.com
VCard: http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle
9 years, 3 months
Fedora based Xen Live CD
by Dario Faggioli
Hello,
So, in the past weeks, as a pet project, I tried to put together a
Fedora based Xen LiveCD. Of course, I took advantage of kickstart, the
Fedora spins 'framework' [1], etc.
Actually, that is exactly what I ended up creating: a kickstart file for
a Fedora spin. It's not an official spin yet, just something I
personally maintain (so, if you like, a Remix [2], although one with
100% Fedora software)... but perhaps I can go ahead and propose it as an
official spin, if the idea reveals popular enough. :-) [3]
Here it comes how to give it a try. The kickstart file is attached to
this message, and the latest version of it will always be available
here:
git://xenbits.xen.org/people/dariof/fedora-live-xen.git
http://xenbits.xen.org/gitweb/?p=people/dariof/fedora-live-xen.git;a=summary
Once downloaded it, make sure you have the spin-kickstarts and
livecd-tools packages. Creating the ISO is (on a Fedora system, of
course!) as easy as running (as root) the following commands (full
instructions here [4]):
# cd /usr/share/spin-kickstarts
# livecd-creator --verbose \
--config=<path_to_downloaded_ks_file>/fedora-live-xen.ks \
--fslabel=Fedora-Xen \
--cache=/var/cache/live
Notice that the `livecd-creator' command accepts a
"--releasever=RELEASEVER" argument, in case one wants to create a live
image of a specific version of Fedora.
At the time of writing this email, there isn't any ISO uploaded
anywhere, as doing so, completely starves my poor little residential
ADSL! :-/ Anyway, I'm going to upload it as soon as possible, and I'll
send the link as a reply to this message... sorry for the
inconvenience! :-P
Once you have the ISO, it should be easy enough to get to create a
bootable USB stick (look at [5]).
Et voila`, you have a Fedora based Dom0 on your CD or USB stick, ready
to be used, for example, for testing Xen on all your boxes, without
actually having to install it! You just boot the live image as usual,
and the hypervisor and Dom0 environemnt is what will be started by
default. It also comes with libvirt (with the libxl driver),
virt-manager, virt-viewer, and all these stuff. :-)
The Xen and Dom0 kernel version used are the ones available in the
Fedora packages for the chosen distro, i.e., Xen 4.3.x on Fedora 20.
I'm already including the updates-testing and virt-preview repositories,
and packages are fetched from there during the live CD creation, so you
really should get software as updated as available.
It's probably not too hard to include rawhide packages at least for Xen
(which, at the moment would mean Xen 4.4), and I'm already trying to
enable that. A little bit more tricky would be to use something coming
from a personal build of the hypervisor (and toolstack, of course). The
problem is both automating the build inside of the kickstart file (but
that is certainly doable) and dealing with dependencies (as in, if you
build and install Xen from source, `yum install
libvirt-daemon-driver-libxl may complain). Anyway, if this is something
interesting, we can certainly try to make it happen. :-)
Of course, once inside the live session, it is possible to invoke the
official Fedora installer and install the distro. That path, however, is
not highly tested with this LiveCD image yet.
So, we're done I guess. Please, if interested, send me your comments,
suggestions, bugfixes, contributions of any kind, etc... let's improve
this
together! :-)
Thanks and Reegards,
Dario
[1] For those unfamiliar with Fedora spins, they're basically
alternative versions of Fedora, tailored for various types of users via
hand-picked application sets or customizations. See:
http://spins.fedoraproject.org/
http://spins.fedoraproject.org/about
[2] http://fedoraproject.org/wiki/Remix
[3] https://fedoraproject.org/wiki/Spins_Process
[4] http://fedoraproject.org/wiki/How_to_create_and_use_a_Live_CD
[5] https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB?rd=FedoraLi...
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
9 years, 3 months
