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
9 years, 5 months
TODAY is Xen Document Day!
by Dario Faggioli
Today is the day!
Xen Project Document Day is a day to help improve overall Xen
documentation, with emphasis on the Xen Project Wiki.
However, this Document Day is special -- it is the prep day for our
impending 4.4 release.
We have a good amount of solid documentation for 4.3, but we need to
update to cover 4.4. The greatest software in the world is worthless
unless people understand how to use it. If you are still looking for
a way to contribute to the upcoming release, your opportunity has
arrived.
Never participated in a Document Day? All the info you need is here:
http://wiki.xenproject.org/wiki/Xen_Document_Days
Not sure what needs attention? Here is the current TODO list:
http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO
Add any documentation deficiencies you have come across while working
with Xen. Is there a subject you wrestled with? That's a perfect
opportunity for you to help shape the documentation into something
more useful for the next person who needs it!
If you haven't requested to be made a Wiki editor, just fill out the
form below:
http://xenproject.org/component/content/article/100-misc/145-request-to-b...
See you in #xendocs!
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 R&D Ltd., Cambridge (UK)
10 years, 2 months
Re: [Fedora-xen] [fedora-virt] f20 guest on centos5 xen host
by Pasi Kärkkäinen
On Fri, Jan 24, 2014 at 08:51:46AM +0000, Bruno Postle wrote:
> On Wed 22-Jan-2014 at 22:35 +0000, Bruno Postle wrote:
> >On Tue 21-Jan-2014 at 21:57 +0000, Bruno Postle wrote:
> >>
> >>Though it now fails to come back up after yum update and reboot:
> >>
> >>[2014-01-21 21:42:50 xend.XendDomainInfo 3625] WARNING (XendDomainInfo:1262) Domain has crashed: name=honk id=28.
> >>[2014-01-21 21:42:50 xend.XendDomainInfo 3625] ERROR (XendDomainInfo:2864) VM honk restarting too fast (Elapsed time: 1.151586 seconds). Refusing to restart to avoid loops.
> >
> >I have some more info on this second problem, the first problem is
> >clearly the same as described in this patch/workaround: http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b...
> >
> >Now the system will come back up on reboot, but not if I upgrade
> >the kernel on the guest (I can upgrade everything else).
> >
> >Any ideas? it is either that there is some new incompatibility
> >between kernel 3.11.10 and 3.12.8 on f20, or pygrub on centos5
> >can't cope with two kernel entries.
>
> Further info, I did the obvious test here: I installed this new f20
> kernel and removed the old f20 kernel entry from the grub.cfg file.
> The guest crashes, so I suppose the f20 3.12.8 kernel is
> incompatible with centos5 xen.
>
Can you please paste the full domU kernel verbose debug output,
so we can see what goes wrong?
-- Pasi
10 years, 2 months
Re: [Fedora-xen] [Xen-devel] [TestDay] F20 Xen 4.4 RC3 Spice support
by Dario Faggioli
On Wed, Feb 5, 2014 at 5:00 AM, Eric Houby <ehouby(a)yahoo.com> wrote:
> It is my understanding that the qemu package in F20 does not support xen
> so I compiled xen from source per the RC3 Test Day instructions and the
> instructions here:
>
Yes, we figured out that was the case during the previous TestDay.
Michael, any news on this? Who should we be talking with to have Xen
enabled in default Fedora qemu package build? I guess it won't be a
F20 thing anyway, but let's make sure we will have that enable in the
next Fedora release! :-)
Regards,
Dario
10 years, 2 months
Re: [Fedora-xen] [Xen-devel] [TestDay] xen 4.4 FC3 xl create error
by M A Young
On Wed, 5 Feb 2014, Ian Campbell wrote:
> On Tue, 2014-02-04 at 18:41 +0000, 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
10 years, 2 months
Re: [Fedora-xen] [Xen-devel] [TestDay] xen 4.4 FC3 xl create error
by M A Young
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
>> Name ID 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
10 years, 2 months
Re: [Fedora-xen] [Xen-users] REMINDER: Feb 3 is Xen Project Test Day for 4.4 RC3
by M A Young
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
10 years, 2 months
