Re: [Fedora-xen] Xen 4.4 RC2 [TestDay]
[Re-sending with the proper address to get to the list too...
sorry! :-/]
On lun, 2014-01-20 at 23:18 +, M A Young wrote:
On Mon, 20 Jan 2014, Eric Houby wrote:
[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.
Cool... That is definitely something worth experimenting! :-)
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.
That part definitely works. As a part of his participation to the
TestDay (which happened thanks to your rc2 packages, so thanks again
Michael for doing that, and Eric for participating!), Eric produced this
log: http://pastebin.com/iyTYEgJ4
...
libxl: debug: libxl_dm.c:1303:libxl__spawn_local_dm: Spawning device-model
/usr/bin/qemu-system-x86_64 with arguments:
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm:
/usr/bin/qemu-system-x86_64
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -xen-domid
libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: 5
...
So... Yay! :-)
While investigating, we also spotted this:
http://pkgs.fedoraproject.org/cgit/qemu.git/tree/qemu.spec?h=f20
Which contains the following:
dobuild() {
./configure \
--prefix=%{_prefix} \
--libdir=%{_libdir} \
--sysconfdir=%{_sysconfdir} \
--interp-prefix=%{_prefix}/qemu-%%M \
--audio-drv-list=pa,sdl,alsa,oss \
--localstatedir=%{_localstatedir} \
--libexecdir=%{_libexecdir} \
--disable-strip \
--extra-ldflags=$extraldflags -pie -Wl,-z,relro -Wl,-z,now \
--extra-cflags=%{optflags} -fPIE -DPIE \
--enable-mixemu \
--enable-trace-backend=dtrace \
--disable-werror \
--disable-xen \
--enable-kvm \
...
which seems to suggest that xen support is disabled in Fedora's qemu
package. Should we ask why they do that, and investigate whether that
can change (and, of course, whether that is enough for us) ?
Thanks again and Regards,
Dario
--
This happens because I choose it to happen! (Raistlin Majere)
-
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems RD Ltd., Cambridge (UK)
signature.asc
Description: This is a digitally signed message part
--
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 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. - Cole -- 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
