Still can't boot Fedora rawhide xen with EL5
by Orion Poplawski
Getting different error now without LZMA:
Starting install...
Retrieving file .treeinfo... | 1.2 kB
00:00
Retrieving file .treeinfo... | 1.2 kB
00:00
Retrieving file vmlinuz... | 3.5 MB
00:00
Retrieving file initrd.img... | 22 MB
00:01
Creating domain... | 0 B
00:01
ERROR: It appears that your installation has crashed. You should be
able to find more information in the logs
[2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:200) XendDomainInfo.create(['vm', ['name', 'xenfdev64'],
['memory', '512'], ['maxmem', '512'], ['vcpus', '1'], ['uuid',
'7579b650-65c7-5baa-0bc0-3502da28df6c'], ['on_poweroff', 'destroy'],
['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux',
['kernel', '/var/lib/xen/virtinst-vmlinuz.h8bkQS'], ['ramdisk',
'/var/lib/xen/virtinst-initrd.img.yoWzKP'], ['args',
'ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg
method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os']]],
['device', ['vbd', ['dev', 'xvda'], ['uname',
'phy:/dev/rootvg/xenfdev64'], ['mode', 'w']]], ['device', ['vif',
['mac', '40:00:00:00:00:03'], ['bridge', 'xenbr0']]], ['device',
['vkbd']], ['device', ['vfb', ['type', 'vnc'], ['vncunused', '1']]]])
[2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:312) parseConfig: config is ['vm', ['name',
'xenfdev64'], ['memory', '512'], ['maxmem', '512'], ['vcpus', '1'],
['uuid', '7579b650-65c7-5baa-0bc0-3502da28df6c'], ['on_poweroff',
'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image',
['linux', ['kernel', '/var/lib/xen/virtinst-vmlinuz.h8bkQS'],
['ramdisk', '/var/lib/xen/virtinst-initrd.img.yoWzKP'], ['args',
'ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg
method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os']]],
['device', ['vbd', ['dev', 'xvda'], ['uname',
'phy:/dev/rootvg/xenfdev64'], ['mode', 'w']]], ['device', ['vif',
['mac', '40:00:00:00:00:03'], ['bridge', 'xenbr0']]], ['device',
['vkbd']], ['device', ['vfb', ['type', 'vnc'], ['vncunused', '1']]]]
[2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:417) parseConfig: result is {'shadow_memory': None,
'start_time': None, 'uuid': '7579b650-65c7-5baa-0bc0-3502da28df6c',
'on_crash': 'destroy', 'on_reboot': 'destroy', 'localtime': None,
'image': ['linux', ['kernel', '/var/lib/xen/virtinst-vmlinuz.h8bkQS'],
['ramdisk', '/var/lib/xen/virtinst-initrd.img.yoWzKP'], ['args',
'ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg
method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os']], 'on_poweroff':
'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'xenfdev64',
'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None,
'vcpu_avail': None, 'memory': 512, 'device': [('vbd', ['vbd', ['dev',
'xvda'], ['uname', 'phy:/dev/rootvg/xenfdev64'], ['mode', 'w']]),
('vif', ['vif', ['mac', '40:00:00:00:00:03'], ['bridge', 'xenbr0']]),
('vkbd', ['vkbd']), ('vfb', ['vfb', ['type', 'vnc'], ['vncunused',
'1']])], 'bootloader': None, 'cpu': None, 'maxmem': 512}
[2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:1427) XendDomainInfo.construct: None
[2009-08-12 09:52:30 xend 3214] DEBUG (balloon:143) Balloon: 525032 KiB
free; need 2048; done.
[2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:1475) XendDomainInfo.initDomain: 20 1.0
[2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:1514) _initDomain:shadow_memory=0x0, maxmem=0x200,
memory=0x200.
[2009-08-12 09:52:30 xend 3214] DEBUG (balloon:143) Balloon: 525024 KiB
free; need 524288; done.
[2009-08-12 09:52:30 xend 3214] INFO (image:137) buildDomain os=linux
dom=20 vcpus=1
[2009-08-12 09:52:30 xend 3214] DEBUG (image:206) domid = 20
[2009-08-12 09:52:30 xend 3214] DEBUG (image:207) memsize = 512
[2009-08-12 09:52:30 xend 3214] DEBUG (image:208) image =
/var/lib/xen/virtinst-vmlinuz.h8bkQS
[2009-08-12 09:52:30 xend 3214] DEBUG (image:209) store_evtchn = 1
[2009-08-12 09:52:30 xend 3214] DEBUG (image:210) console_evtchn = 2
[2009-08-12 09:52:30 xend 3214] DEBUG (image:211) cmdline =
ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg
method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os
[2009-08-12 09:52:30 xend 3214] DEBUG (image:212) ramdisk =
/var/lib/xen/virtinst-initrd.img.yoWzKP
[2009-08-12 09:52:30 xend 3214] DEBUG (image:213) vcpus = 1
[2009-08-12 09:52:30 xend 3214] DEBUG (image:214) features =
[2009-08-12 09:52:30 xend 3214] DEBUG (DevController:110) DevController:
writing {'protocol': 'x86_64-abi', 'state': '1', 'backend-id': '0',
'backend': '/local/domain/0/backend/vkbd/20/0'} to
/local/domain/20/device/vkbd/0.
[2009-08-12 09:52:30 xend 3214] DEBUG (DevController:112) DevController:
writing {'frontend-id': '20', 'domain': 'xenfdev64', 'frontend':
'/local/domain/20/device/vkbd/0', 'state': '1', 'online': '1'} to
/local/domain/0/backend/vkbd/20/0.
[2009-08-12 09:52:30 xend 3214] DEBUG (blkif:27) exception looking up
device number for xvda: [Errno 2] No such file or directory: '/dev/xvda'
[2009-08-12 09:52:30 xend 3214] DEBUG (DevController:110) DevController:
writing {'virtual-device': '51712', 'device-type': 'disk', 'protocol':
'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend':
'/local/domain/0/backend/vbd/20/51712'} to
/local/domain/20/device/vbd/51712.
[2009-08-12 09:52:30 xend 3214] DEBUG (DevController:112) DevController:
writing {'domain': 'xenfdev64', 'frontend':
'/local/domain/20/device/vbd/51712', 'format': 'raw', 'dev': 'xvda',
'state': '1', 'params': '/dev/rootvg/xenfdev64', 'mode': 'w', 'online':
'1', 'frontend-id': '20', 'type': 'phy'} to
/local/domain/0/backend/vbd/20/51712.
[2009-08-12 09:52:30 xend 3214] DEBUG (DevController:110) DevController:
writing {'mac': '40:00:00:00:00:03', 'handle': '0', 'protocol':
'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend':
'/local/domain/0/backend/vif/20/0'} to /local/domain/20/device/vif/0.
[2009-08-12 09:52:30 xend 3214] DEBUG (DevController:112) DevController:
writing {'bridge': 'xenbr0', 'domain': 'xenfdev64', 'handle': '0',
'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/20/device/vif/0', 'mac': '40:00:00:00:00:03', 'online':
'1', 'frontend-id': '20'} to /local/domain/0/backend/vif/20/0.
[2009-08-12 09:52:30 xend 3214] DEBUG (DevController:110) DevController:
writing {'protocol': 'x86_64-abi', 'state': '1', 'backend-id': '0',
'backend': '/local/domain/0/backend/vfb/20/0'} to
/local/domain/20/device/vfb/0.
[2009-08-12 09:52:30 xend 3214] DEBUG (DevController:112) DevController:
writing {'vncunused': '1', 'domain': 'xenfdev64', 'frontend':
'/local/domain/20/device/vfb/0', 'online': '1', 'frontend-id': '20',
'type': 'vnc', 'state': '1'} to /local/domain/0/backend/vfb/20/0.
[2009-08-12 09:52:30 xend 3214] DEBUG (vfbif:70) No VNC passwd
configured for vfb access
[2009-08-12 09:52:30 xend 3214] DEBUG (vfbif:11) Spawn:
['/usr/lib64/xen/bin/qemu-dm', '-M', 'xenpv', '-d', '20',
'-domain-name', 'xenfdev64', '-vnc', '127.0.0.1:0', '-vncunused']
[2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:797) Storing VM details: {'shadow_memory': '0', 'uuid':
'7579b650-65c7-5baa-0bc0-3502da28df6c', 'on_reboot': 'destroy',
'start_time': '1250092350.98', 'on_poweroff': 'destroy', 'name':
'xenfdev64', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1',
'memory': '512', 'on_crash': 'destroy', 'image': "(linux (kernel
/var/lib/xen/virtinst-vmlinuz.h8bkQS) (ramdisk
/var/lib/xen/virtinst-initrd.img.yoWzKP) (args
'ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg
method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os'))",
'maxmem': '512'}
[2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:832) Storing domain details: {'console/ring-ref':
'676374', 'console/port': '2', 'name': 'xenfdev64', 'console/limit':
'1048576', 'vm': '/vm/7579b650-65c7-5baa-0bc0-3502da28df6c', 'domid':
'20', 'cpu/0/availability': 'online', 'memory/target': '524288',
'store/ring-ref': '676375', 'store/port': '1'}
[2009-08-12 09:52:31 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:1036) XendDomainInfo.handleShutdownWatch
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices vif.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:160) Waiting for 0.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496)
hotplugStatusCallback /local/domain/0/backend/vif/20/0/hotplug-status.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496)
hotplugStatusCallback /local/domain/0/backend/vif/20/0/hotplug-status.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:510)
hotplugStatusCallback 1.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices usb.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices vbd.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:160) Waiting for 51712.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496)
hotplugStatusCallback /local/domain/0/backend/vbd/20/51712/hotplug-status.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496)
hotplugStatusCallback /local/domain/0/backend/vbd/20/51712/hotplug-status.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:510)
hotplugStatusCallback 1.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices irq.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices vkbd.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:160) Waiting for 0.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496)
hotplugStatusCallback /local/domain/0/backend/vkbd/20/0/hotplug-status.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:510)
hotplugStatusCallback 1.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices vfb.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:160) Waiting for 0.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496)
hotplugStatusCallback /local/domain/0/backend/vfb/20/0/hotplug-status.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:510)
hotplugStatusCallback 1.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices pci.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices ioports.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices tap.
[2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for
devices vtpm.
[2009-08-12 09:52:31 xend 3214] INFO (XendDomain:380) Domain xenfdev64
(20) unpaused.
[2009-08-12 09:52:31 xend.XendDomainInfo 3214] WARNING
(XendDomainInfo:965) Domain has crashed: name=xenfdev64 id=20.
[2009-08-12 09:52:31 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:1637) XendDomainInfo.destroy: domid=20
[2009-08-12 09:52:31 xend.XendDomainInfo 3214] WARNING
(XendDomainInfo:965) Domain has crashed: name=xenfdev64 id=20.
[2009-08-12 09:52:31 xend.XendDomainInfo 3214] DEBUG
(XendDomainInfo:1637) XendDomainInfo.destroy: domid=20
[2009-08-12 09:52:31 xend.XendDomainInfo 3214] ERROR
(XendDomainInfo:1645) XendDomainInfo.destroy: xc.domain_destroy failed.
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1643, in destroy
xc.domain_destroy(self.domid)
Error: (3, 'No such process')
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
14 years, 8 months
Fedora 11 Xen domU grub.conf timeout=0 problem with pygrub
by Pasi Kärkkäinen
Hello,
I just installed Fedora 11 Xen PV domU on Fedora 11 Xen dom0, using virt-install
like this:
virt-install -n testvm -r 512 --vcpus=1 -f /dev/vg_dom0test/testvm --vnc -p
-l "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/release..."
Installation goes fine, but after the installation is complete, and the domU
gets rebooted, it will never come up again. I tried multiple times, and it's
always the same. Installation starts and works fine, but after installation domU
doesn't start anymore - not even after "xm destroy" and "xm start".
I started investigating the problem, and from "xm log" I noticed the last
line of output is about starting pygrub and nothing after that.
I checked "ps aux" and noticed pygrub is there, waiting for something.
"strace -p" shows it's waiting for something, and checking the status all the time.
I tried running the same pygrub command from cmdline, and noticed I have to
press enter before the kernel gets chosen by pygrub. After pressing enter pygrub
copies the kernel/initrd/configuration and exists OK.
I echoed the config from manual pygrub run to /var/run/xend/boot/xenbl.pid file,
killed pygrub, and after that the after-installation-reboot continued normally..
When the domU got up I checked grub.conf from it:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_f11domu-lv_root
# initrd /initrd-version.img
#boot=/dev/xvda
default=0
timeout=0
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.29.4-167.fc11.i686.PAE)
root (hd0,0)
kernel /vmlinuz-2.6.29.4-167.fc11.i686.PAE ro
root=/dev/mapper/vg_f11domu-lv_root rhgb quiet
initrd /initrd-2.6.29.4-167.fc11.i686.PAE.img
timeout=0 looks suspicious.. so I changed it to 5.
After that domU comes up OK on its own..
I changed timeout back to 0, and pygrub gets stuck again.
Is this a bug of pygrub, or a broken default grub.conf timeout value of F11?
-- Pasi
14 years, 8 months
Setting up libvirt to work with Xen 3.4.1 on F11
by Boris Derzhavets
xen 3.4.1-1 src.rpm downloaded from
http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
rebuilt that for F11 and installed.
libvirt src.rpm downloaded from
ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates...
and installed : "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
Rebuilt libvirt packages applying patch :-
http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=...
Installed libvirt :-
yum install libvirt-0.6.2-14.fc11.x86_64.rpm \
libvirt-debuginfo-0.6.2-14.fc11.x86_64.rpm \
libvirt-devel-0.6.2-14.fc11.x86_64.rpm \
libvirt-python-0.6.2-14.fc11.x86_64.rpm \
virt-manager virt-viewer
Attempt to create any HVM via virt-manager aborts with message:-
Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 1501, in do_install
dom = guest.start_install(False, meter = meter)
File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 974, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: Domain not found: xenUnifiedDomainLookupByName
PV DomUs for F11 and CentOS 5.3 created and tested OK.
Boris.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
14 years, 8 months
virt-viewer crashing on F11 with Xen 3.4.1
by Pasi Kärkkäinen
Hello.
While continuing to test pv_ops dom0 kernels I also rebuilt
xen-3.4.1-1 src.rpm on F11.
I'm able to virt-install new centos 5.3 domU, but it seems virt-viewer
doesn't work. It segfaults on startup. vncviewer works though, and I'm able
to complete the installation with vncviewer.
http://pasik.reaktio.net/fedora/virt-viewer-crash.txt
virt-viewer works when used with the default xen-3.3.1 (which is included in F11).
Any tips?
-- Pasi
14 years, 8 months
[Xen-devel] pvops dom0 work roadmap
by Pasi Kärkkäinen
----- Forwarded message from Jeremy Fitzhardinge <jeremy(a)goop.org> -----
From: Jeremy Fitzhardinge <jeremy(a)goop.org>
To: Xen-devel <xen-devel(a)lists.xensource.com>
Date: Tue, 18 Aug 2009 11:43:38 -0700
Subject: [Xen-devel] pvops dom0 work roadmap
Hi all,
I know I've been a bit quiet lately; I've been working through a number
of relatively small but time-consuming bugs while trying to stabilize
rebase/master.
The plan is:
* make sure rebase/master is fairly functional and somewhat stable
* rename rebase/* to xen/*
* use it as the baseline dom0 and domU kernel in xen-unstable
rebase/mster is currently up to 2.6.31-rc6, and I intend to track
mainline fairly closely (probably no more closely than the -rc level).
It also has some new features:
* better acpi power management (ported from 2.6.18)
* MCE (also from 2.6.18)
* microcode updater (I forget whether that's in xen-tip/master)
rebase/master is mostly working for me now, but I would be interested in
getting some more testing (both success and bug reports welcomed). Once
it seems to work, I'll do the rename and we'll work from there.
What does this mean for you?
* If you're itching to test something, test rebase/master
* If you're doing some new development, base it on rebase/master (or
if you don't have any strong dependencies on other Xen pieces,
base it on mainline)
o also, tell me if you're working on something, even if it
isn't ready yet, so I know who's doing what
It would also useful to do regression testing on plain, unpatched,
mainline, to make sure that any real bugfixes get merged promptly.
Thanks,
J
_______________________________________________
Xen-devel mailing list
Xen-devel(a)lists.xensource.com
http://lists.xensource.com/xen-devel
----- End forwarded message -----
14 years, 8 months
Using virt-manager for managing KVM VMs running on CentOS 5
by Ranbir
Hi Everyone,
Can I use virt-manager from a Fedora 11 box to manage KVM VMs running on
a CentOS 5.3 host? The CentOS 5.3 machine is running KVM and related
RPMs from a third party repo
(http://www.lfarkas.org/linux/packages/centos/5/x86_64/virt/RPMS/) .
I'm using TLS for the encryption. I followed the TLS guide on the
libvirt.org website to create and install all the necessary certs and
keys. I have libvirtd listening on the CentOS 5 box. When I try to
connect to libvirtd with virt-manager from my Fedora 11 desktop, I see
the following error on the server:
error : qemudClientReadBuf:1554 : gnutls_record_recv: A TLS packet with
unexpected length was received.
So, that has me wondering if I can even connect to libvirtd on the
CentOS 5 box from Fedora 11 in the first place.
Regards,
Ranbir
--
Kanwar Ranbir Sandhu
Linux 2.6.27.29-170.2.78.fc10.x86_64 x86_64 GNU/Linux
10:54:02 up 5 days, 9:54, 5 users, load average: 2.36, 2.38, 1.27
14 years, 8 months
Possible to install Fedora Rawhide (F12) on RHEL5?
by Orion Poplawski
I'm trying to install current Fedora Rawhide on my RHEL5 box -
Starting install...
Retrieving file .treeinfo... | 1.2 kB
00:00
Retrieving file .treeinfo... | 1.2 kB
00:00
Retrieving file vmlinuz... | 2.9 MB
00:09
Retrieving file initrd.img... | 22 MB
01:17
virDomainCreateLinux() failed POST operation failed: (xend.err "Error
creating domain: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader
found\\n')")
Domain installation may not have been
successful. If it was, you can restart your domain
by running 'virsh start xenfdev64'; otherwise, please
restart your installation.
Mon, 10 Aug 2009 11:22:28 ERROR virDomainCreateLinux() failed POST
operation failed: (xend.err "Error creating domain: (2, 'Invalid
kernel', 'xc_dom_find_loader: no loader found\\n')")
domain-builder-ng.log shows:
xc_dom_kernel_file: filename="/var/lib/xen/virtinst-vmlinuz.jWnwEV"
xc_dom_malloc_filemap : 2921 kB
xc_dom_ramdisk_file: filename="/var/lib/xen/virtinst-initrd.img.ZWLIiQ"
xc_dom_malloc_filemap : 22491 kB
xc_dom_boot_xen_init: ver 3.1, caps xen-3.0-x86_64 xen-3.0-x86_32p
xc_dom_parse_image: called
xc_dom_find_loader: trying ELF-generic loader ... failed
xc_dom_find_loader: trying Linux bzImage loader ... failed
xc_dom_find_loader: trying multiboot-binary loader ... failed
xc_dom_core.c:495: panic: xc_dom_find_loader: no loader found
xc_dom_release: called
Any hope?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
14 years, 8 months
