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
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
grub2 vs. Xen
by Bill McGonigle
Hi, folks,
I've got two problems with grub2 that I thought others might have solved already. My initial attempts haven't been fruitful.
I have an f20 Dom0.
xen-4.3.2-1.fc20.x86_64
grub2-2.00-25.fc20.x86_64
Problem #1
My /etc/default/grub looks like [1].
I try to set the Dom0 to boot with:
grub2-set-default 'Fedora, with Xen 4.3.2 and Linux 3.12.10-300.fc20.x86_64'
and the default non-Xen menuentry gets booted instead.
It's definitely there in the config file [2] and I can boot it manually. I really need the machine to be able to boot unattended. I tried setting it manually in /etc/grub/default but that doesn't work either.
I'm generating the grub.cfg with grub2-mkconfig > /boot/grub2/grub.cfg and have re-installed grub2 on my /dev/sda and /dev/sdb (raid-1 /boot).
Problem #2
When I try to boot from grub manually, I first get an error message saying "xen_rm_opts" unknown command. In each Xen menuentry, I see, e.g.:
echo 'Loading Xen xen ...'
if [ "$grub_platform" = "pc" -o "$grub_platform" = "" ]; then
xen_rm_opts
else
xen_rm_opts="no-real-mode edd=off"
fi
whereas in previous times I remember the first conditional block saying:
xen_rm_opts=
I presume that makes the difference between a statement and an assignment in whatever sh-ish language grub is using. I'm not sure where to fix that as I'm no grub2 expert. I kinda miss the simplicity of 'default=6'. :)
My third possible-grub problem relates to memory and I'm not sure it really is a problem in grub2 yet, so I'll post that separately.
Thanks in advance!
-Bill
[1]
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Fedora"
GRUB_DEFAULT="saved"
GRUB_CMDLINE_LINUX="root=LABEL=librescu-root rootflags=data=journal rd_NO_LUKS rd.md=auto rd.lvm=0 rd.dm=0 KEYTABLE=us SYSFONT=lata
rcyrheb-sun16 rd.luks=0 LANG=en_US.UTF-8 selinux=0 elevator=deadline mem=4096M max_loop=32 selinux=0 ipv6.disable=1"
GRUB_CMDLINE_XEN="dom0_max_vcpus=2 dom0_vcpus_pin dom0_mem=4096M,max:4096M"
GRUB_SERIAL_COMMAND="serial --unit=0 --speed=19200 --word=8 --parity=no --stop=1"
GRUB_TIMEOUT=10
GRUB_TERMINAL="serial console"
[2]
# grep "'Fedora, with Xen 4.3.2 and Linux 3.12.10-300.fc20.x86_64'" /boot/grub2/grub.cfg
menuentry 'Fedora, with Xen 4.3.2 and Linux 3.12.10-300.fc20.x86_64' --class fedora --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-3.12.10-300.fc20.x86_64-advanced-9ccf2a16-82bf-41b0-a35f-1d79d63b3e28' {
--
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, 4 months
awoizisz
by Collins Oluoch
ZAIaNA
:-(:-tnO z l.duz. uz
9 years, 5 months
