xen May 2014

xen@lists.fedoraproject.org

3 discussions

execute commands from dom0 into domU
by silviu d 06 Jun '15

06 Jun '15

Hello, I was wondering if there is a way to execute commands from dom0 into domU without loging into domU with ssh. thanks

3 2

Re: [Fedora-xen] Xen 4.4 RC2 [TestDay]
by M A Young 16 Nov '14

16 Nov '14

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

4 3

building Xen from SRPM
by Bill McGonigle 18 Jun '14

18 Jun '14

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

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen May 2014