* Can't boot dom0 ??
@ 2010-03-26 14:51 Leena M.
[not found] ` <7094659f1003261135h612ac985x471cc92846afbf08@mail.gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Leena M. @ 2010-03-26 14:51 UTC (permalink / raw)
To: xen-devel, xen-community, xen-users
[-- Attachment #1.1: Type: text/plain, Size: 3373 bytes --]
----------------- /var/log/xen/xend.log ----------------------
[2010-03-16 05:22:34 1656] INFO (SrvDaemon:332) Xend Daemon started
[2010-03-16 05:22:34 1656] INFO (SrvDaemon:336) Xend changeset: Tue Mar 02
19:22:22 2010 +0000 19913:6063c16aeeaa.
[2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:140)
XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 11566217542L,
'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2,
'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb':
4294967292L, 'shutdown': 0, 'mem_kb': 4003968L, 'handle': [0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
[2010-03-16 05:22:34 1656] INFO (XendDomainInfo:158) Recreating domain 0,
UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
[2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:3067) Storing VM details:
{'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid':
'00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image':
'(linux (kernel ))', 'on_poweroff': 'destroy', 'bootloader_args': '',
'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0',
'vcpus': '2', 'vcpu_avail': '3', 'bootloader': '', 'name': 'Domain-0'}
[2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:1629) Storing domain
details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target':
'4003968', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
'cpu/0/availability': 'online', 'cpu/1/availability': 'online',
'control/platform-feature-multiprocessor-suspend': '1', 'console/type':
'xenconsoled'}
[2010-03-16 05:22:34 1656] DEBUG (XendDomain:453) Adding Domain: 0
[2010-03-16 05:22:34 1656] DEBUG (XendDomain:387) number of vcpus to use is
0
[2010-03-16 05:22:34 1656] INFO (SrvServer:177) unix
path=/var/lib/xend/xend-socket
[2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:1716)
XendDomainInfo.handleShutdownWatch
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VBD.set_device
not found
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VBD.set_type not
found
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
session.get_all_records not found
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: event.get_record
not found
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: event.get_all not
found
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VIF.get_network
not found
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VIF.set_device
not found
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VIF.set_MAC not
found
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VIF.set_MTU not
found
[2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: debug.get_all not
found
[2010-03-16 05:22:34 1656] INFO (XMLRPCServer:156) Opening Unix domain
socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been
disabled for this server.
[2010-03-16 05:22:34 1656] INFO (XMLRPCServer:156) Opening Unix domain
socket XML-RPC server on /var/run/xend/xmlrpc.sock.
-----------------------------------------------------------
Please also find the xend-config.sxp file.
on booting last message I get on boot screen is
xenconsoled daemon ... [ok]
"*xend: No such file or directory. Is xend running?"
Please help me , I am struggling with this for quite some time now.
Regards,
Leena
*
[-- Attachment #1.2: Type: text/html, Size: 4072 bytes --]
[-- Attachment #2: xend-config.sxp --]
[-- Type: application/octet-stream, Size: 9140 bytes --]
# -*- sh -*-
#
# Xend configuration file.
#
# This example configuration is appropriate for an installation that
# utilizes a bridged network configuration. Access to xend via http
# is disabled.
# Commented out entries show the default for that entry, unless otherwise
# specified.
#(logfile /var/log/xen/xend.log)
#(loglevel DEBUG)
# Uncomment the line below. Set the value to flask, acm, or dummy to
# select a security module.
#(xsm_module_name dummy)
# The Xen-API server configuration.
#
# This value configures the ports, interfaces, and access controls for the
# Xen-API server. Each entry in the list starts with either unix, a port
# number, or an address:port pair. If this is "unix", then a UDP socket is
# opened, and this entry applies to that. If it is a port, then Xend will
# listen on all interfaces on that TCP port, and if it is an address:port
# pair, then Xend will listen on the specified port, using the interface with
# the specified address.
#
# The subsequent string configures the user-based access control for the
# listener in question. This can be one of "none" or "pam", indicating either
# that users should be allowed access unconditionally, or that the local
# Pluggable Authentication Modules configuration should be used. If this
# string is missing or empty, then "pam" is used.
#
# The final string gives the host-based access control for that listener. If
# this is missing or empty, then all connections are accepted. Otherwise,
# this should be a space-separated sequence of regular expressions; any host
# with a fully-qualified domain name or an IP address that matches one of
# these regular expressions will be accepted.
#
# Example: listen on TCP port 9363 on all interfaces, accepting connections
# only from machines in example.com or localhost, and allow access through
# the unix domain socket unconditionally:
#
# (xen-api-server ((9363 pam '^localhost$ example\\.com$')
# (unix none)))
#
# Optionally, the TCP Xen-API server can use SSL by specifying the private
# key and certificate location:
#
# (9367 pam '' /etc/xen/xen-api.key /etc/xen/xen-api.crt)
#
# Default:
# (xen-api-server ((unix)))
#(xend-http-server no)
(xend-unix-server no)
#(xend-tcp-xmlrpc-server no)
#(xend-unix-xmlrpc-server yes)
(xend-relocation-server no)
#(xend-relocation-server yes)
#(xend-relocation-ssl-server no)
#(xend-udev-event-server no)
#(xend-unix-path /var/lib/xend/xend-socket)
# Address and port xend should use for the legacy TCP XMLRPC interface,
# if xend-tcp-xmlrpc-server is set.
#(xend-tcp-xmlrpc-server-address 'localhost')
#(xend-tcp-xmlrpc-server-port 8006)
# SSL key and certificate to use for the legacy TCP XMLRPC interface.
# Setting these will mean that this port serves only SSL connections as
# opposed to plaintext ones.
#(xend-tcp-xmlrpc-server-ssl-key-file /etc/xen/xmlrpc.key)
#(xend-tcp-xmlrpc-server-ssl-cert-file /etc/xen/xmlrpc.crt)
# Port xend should use for the HTTP interface, if xend-http-server is set.
#(xend-port 8000)
# Port xend should use for the relocation interface, if xend-relocation-server
# is set.
#(xend-relocation-port 8002)
# Port xend should use for the ssl relocation interface, if
# xend-relocation-ssl-server is set.
#(xend-relocation-ssl-port 8003)
# SSL key and certificate to use for the ssl relocation interface, if
# xend-relocation-ssl-server is set.
#(xend-relocation-server-ssl-key-file /etc/xen/xmlrpc.key)
#(xend-relocation-server-ssl-cert-file /etc/xen/xmlrpc.crt)
# Whether to use ssl as default when relocating.
#(xend-relocation-ssl no)
# Address xend should listen on for HTTP connections, if xend-http-server is
# set.
# Specifying 'localhost' prevents remote connections.
# Specifying the empty string '' (the default) allows all connections.
#(xend-address '')
#(xend-address localhost)
# Address xend should listen on for relocation-socket connections, if
# xend-relocation-server is set.
# Meaning and default as for xend-address above.
#(xend-relocation-address '')
# The hosts allowed to talk to the relocation port. If this is empty (the
# default), then all connections are allowed (assuming that the connection
# arrives on a port and interface on which we are listening; see
# xend-relocation-port and xend-relocation-address above). Otherwise, this
# should be a space-separated sequence of regular expressions. Any host with
# a fully-qualified domain name or an IP address that matches one of these
# regular expressions will be accepted.
#
# For example:
# (xend-relocation-hosts-allow '^localhost$ ^.*\\.example\\.org$')
#
#(xend-relocation-hosts-allow '')
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
# The limit (in kilobytes) on the size of the console buffer
(console-limit 1024)
##
# To bridge network traffic, like this:
#
# dom0: ----------------- bridge -> real eth0 -> the network
# |
# domU: fake eth0 -> vifN.0 -+
#
# use
#
# (network-script network-bridge)
#
# Your default ethernet device is used as the outgoing interface, by default.
# To use a different one (e.g. eth1) use
#
# (network-script 'network-bridge netdev=eth1')
#
# The bridge is named xenbr0, by default. To rename the bridge, use
#
# (network-script 'network-bridge bridge=<name>')
#
# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain. To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
#(network-script network-bridge)
(network-script /bin/true)
# The script used to control virtual interfaces. This can be overridden on a
# per-vif basis when creating a domain or a configuring a new vif. The
# vif-bridge script is designed for use with the network-bridge script, or
# similar configurations.
#
# If you have overridden the bridge name using
# (network-script 'network-bridge bridge=<name>') then you may wish to do the
# same here. The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a default.
#
# If you are using only one bridge, the vif-bridge script will discover that,
# so there is no need to specify it explicitly.
#
(vif-script vif-bridge)
## Use the following if network traffic is routed, as an alternative to the
# settings for bridged networking given above.
#(network-script network-route)
#(vif-script vif-route)
## Use the following if network traffic is routed with NAT, as an alternative
# to the settings for bridged networking given above.
#(network-script network-nat)
#(vif-script vif-nat)
# dom0-min-mem is the lowest permissible memory level (in MB) for dom0.
# This is a minimum both for auto-ballooning (as enabled by
# enable-dom0-ballooning below) and for xm mem-set when applied to dom0.
(dom0-min-mem 256)
# Whether to enable auto-ballooning of dom0 to allow domUs to be created.
# If enable-dom0-ballooning = no, dom0 will never balloon out.
(enable-dom0-ballooning yes)
# In SMP system, dom0 will use dom0-cpus # of CPUS
# If dom0-cpus = 0, dom0 will take all cpus available
(dom0-cpus 0)
# Whether to enable core-dumps when domains crash.
#(enable-dump no)
# The tool used for initiating virtual TPM migration
#(external-migration-tool '')
# The interface for VNC servers to listen on. Defaults
# to 127.0.0.1 To restore old 'listen everywhere' behaviour
# set this to 0.0.0.0
#(vnc-listen '127.0.0.1')
# The default password for VNC console on HVM domain.
# Empty string is no authentication.
(vncpasswd '')
# The VNC server can be told to negotiate a TLS session
# to encryption all traffic, and provide x509 cert to
# clients enalbing them to verify server identity. The
# GTK-VNC widget, virt-viewer, virt-manager and VeNCrypt
# all support the VNC extension for TLS used in QEMU. The
# TightVNC/RealVNC/UltraVNC clients do not.
#
# To enable this create x509 certificates / keys in the
# directory /etc/xen/vnc
#
# ca-cert.pem - The CA certificate
# server-cert.pem - The Server certificate signed by the CA
# server-key.pem - The server private key
#
# and then uncomment this next line
# (vnc-tls 1)
# The certificate dir can be pointed elsewhere..
#
# (vnc-x509-cert-dir /etc/xen/vnc)
# The server can be told to request & validate an x509
# certificate from the client. Only clients with a cert
# signed by the trusted CA will be able to connect. This
# is more secure the password auth alone. Passwd auth can
# used at the same time if desired. To enable client cert
# checking uncomment this:
#
# (vnc-x509-verify 1)
# The default keymap to use for the VM's virtual keyboard
# when not specififed in VM's configuration
#(keymap 'en-us')
# Script to run when the label of a resource has changed.
#(resource-label-change-script '')
# Rotation count of qemu-dm log file.
#(qemu-dm-logrotate-count 10)
# Path where persistent domain configuration is stored.
# Default is /var/lib/xend/domains/
#(xend-domains-path /var/lib/xend/domains)
[-- Attachment #3: Type: text/plain, Size: 137 bytes --]
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Xen-community] Can't boot dom0 ??
[not found] ` <0722B099-4D75-425C-BD7F-1C31638BFD69@frasa.net>
@ 2010-03-27 11:51 ` Leena M.
2010-03-27 14:17 ` [Xen-users] " Pasi Kärkkäinen
0 siblings, 1 reply; 3+ messages in thread
From: Leena M. @ 2010-03-27 11:51 UTC (permalink / raw)
To: Mark Frasa, xen-devel, xen-community, xen-users
[-- Attachment #1.1: Type: text/plain, Size: 7646 bytes --]
I am not able to boot Xen , It gets stuck in run-level 5 after Xenconsoled
script is called.
it gives error soething like
Error: Error connecting to *xend*: *No such file or directory*. Is
*xend*running?
$ ls /boot/
config-2.6.18.8-xen vmlinuz-2.6.18.8-xen
config-2.6.31.5 vmlinuz-2.6.31.5
config-2.6.31.5-127.fc12.i686.PAE vmlinuz-2.6.31.5-127.fc12.i686.PAE
efi xen-3.4.2.gz
grub xen-3.4.3-rc4-pre.gz
initramfs-2.6.31.5-127.fc12.i686.PAE.img xen-3.4.gz
initramfs-2.6.31.5.img xen-3.gz
initrd-2.6.18.8-xen.img xen.gz
System.map-2.6.18.8-xen xen-syms-3.4.2
System.map-2.6.31.5 xen-syms-3.4.3-rc4-pre
System.map-2.6.31.5-127.fc12.i686.PAE
[onkar@localhost boot]$ uname -a
Linux localhost.localdomain 2.6.31.5 #2 SMP Wed Mar 10 07:27:18 IST 2010
i686 i686 i386 GNU/Linux
--------------------------------menu.lst
---------------------------------------------------------------------
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/sda1
# initrd /boot/initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
# hiddenmenu
title Fedora (2.6.31.5 - my custom kernel)
root (hd0,0)
kernel /boot/vmlinuz-2.6.31.5 ro
root=UUID=2f103b84-46c2-4976-9391-8ac6f6f73181 ro console=tty0
initrd /boot/initramfs-2.6.31.5.img
title Xen 3.4 / XenLinux 2.6
root (hd0,0)
kernel /boot/xen-3.4.gz
module /boot/vmlinuz-2.6.18.8-xen
root=UUID=2f103b84-46c2-4976-9391-8ac6f6f73181 ro console=tty0
module /boot/initrd-2.6.18.8-xen.img
title Fedora (2.6.31.5-127.fc12.i686.PAE)
root (hd0,0)
kernel /boot/vmlinuz-2.6.31.5-127.fc12.i686.PAE ro
root=UUID=2f103b84-46c2-4976-9391-8ac6f6f73181 LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /boot/initramfs-2.6.31.5-127.fc12.i686.PAE.img
Regards,
/Leena
On Sat, Mar 27, 2010 at 12:46 PM, Mark Frasa <mark@frasa.net> wrote:
> Your kernel version should contain -xen
>
> Can you paste the output from 'uname'
> Verify that you booted a xen kernel, cuz the steps you followed do not
> include copy the kernel to /boot neither checking grub.
>
> /Mark
>
> Op 27 mrt 2010 om 04:25 heeft "Leena M." <kernmonk@gmail.com> het volgende
> geschreven:\
>
> Thank you very much for your reply.
>
> Kernel version => 2.6.18.8
> OS => Linux
> configuration file is attached.
>
> Steps I followed :
>
> make world
> make install
> copy initrd image to /boot/
> reboot
> Is there any xend configuration needed ?
> Is there any dom0 configuration needed ??
>
>
> Please help me to get through this.
>
> Regards,
> Leena
>
> On Sat, Mar 27, 2010 at 12:05 AM, Mark Frasa < <mark@frasa.net>
> mark@frasa.net> wrote:
>
>> Some more info might be useful like:
>>
>> - Your kernel version
>> - The OS you are running
>> - Xen version that is installed
>> - etc..
>>
>> It looks like you did not boot into a xen-kernel, but it might be too
>> early to tell.
>> At least this line is suspicious:
>>
>>
>> "[2010-03-16 05:22:34 1656] DEBUG (XendDomain:387) number of vcpus to use
>> is 0"
>>
>> Give some more info an we might be able to help you.
>>
>>
>> /Mark
>>
>> 2010/3/26 Leena M. < <kernmonk@gmail.com>kernmonk@gmail.com>
>>
>>> ----------------- /var/log/xen/xend.log ----------------------
>>>
>>>
>>> [2010-03-16 05:22:34 1656] INFO (SrvDaemon:332) Xend Daemon started
>>> [2010-03-16 05:22:34 1656] INFO (SrvDaemon:336) Xend changeset: Tue Mar
>>> 02 19:22:22 2010 +0000 19913:6063c16aeeaa.
>>> [2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:140)
>>> XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 11566217542L,
>>> 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2,
>>> 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb':
>>> 4294967292L, 'shutdown': 0, 'mem_kb': 4003968L, 'handle': [0, 0, 0, 0, 0, 0,
>>> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
>>> [2010-03-16 05:22:34 1656] INFO (XendDomainInfo:158) Recreating domain 0,
>>> UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
>>> [2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:3067) Storing VM
>>> details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid':
>>> '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image':
>>> '(linux (kernel ))', 'on_poweroff': 'destroy', 'bootloader_args': '',
>>> 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0',
>>> 'vcpus': '2', 'vcpu_avail': '3', 'bootloader': '', 'name': 'Domain-0'}
>>> [2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:1629) Storing domain
>>> details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target':
>>> '4003968', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
>>> 'cpu/0/availability': 'online', 'cpu/1/availability': 'online',
>>> 'control/platform-feature-multiprocessor-suspend': '1', 'console/type':
>>> 'xenconsoled'}
>>> [2010-03-16 05:22:34 1656] DEBUG (XendDomain:453) Adding Domain: 0
>>> [2010-03-16 05:22:34 1656] DEBUG (XendDomain:387) number of vcpus to use
>>> is 0
>>> [2010-03-16 05:22:34 1656] INFO (SrvServer:177) unix
>>> path=/var/lib/xend/xend-socket
>>> [2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:1716)
>>> XendDomainInfo.handleShutdownWatch
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VBD.set_device
>>> not found
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VBD.set_type
>>> not found
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
>>> session.get_all_records not found
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
>>> event.get_record not found
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: event.get_all
>>> not found
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
>>> VIF.get_network not found
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VIF.set_device
>>> not found
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VIF.set_MAC
>>> not found
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: VIF.set_MTU
>>> not found
>>> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call: debug.get_all
>>> not found
>>> [2010-03-16 05:22:34 1656] INFO (XMLRPCServer:156) Opening Unix domain
>>> socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been
>>> disabled for this server.
>>> [2010-03-16 05:22:34 1656] INFO (XMLRPCServer:156) Opening Unix domain
>>> socket XML-RPC server on /var/run/xend/xmlrpc.sock.
>>>
>>> -----------------------------------------------------------
>>>
>>> Please also find the xend-config.sxp file.
>>>
>>> on booting last message I get on boot screen is
>>> xenconsoled daemon ... [ok]
>>> "*xend: No such file or directory. Is xend running?"
>>>
>>>
>>>
>>> Please help me , I am struggling with this for quite some time now.
>>>
>>>
>>> Regards,
>>> Leena
>>>
>>>
>>> *
>>>
>>>
>>> _______________________________________________
>>> Xen-community mailing list
>>> <Xen-community@lists.xensource.com>Xen-community@lists.xensource.com
>>> <http://lists.xensource.com/mailman/listinfo/xen-community>
>>> http://lists.xensource.com/mailman/listinfo/xen-community
>>>
>>>
>>
> <config-2.6.18.8-xen>
>
>
[-- Attachment #1.2: Type: text/html, Size: 9916 bytes --]
[-- Attachment #2: Type: text/plain, Size: 137 bytes --]
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Xen-users] Re: [Xen-community] Can't boot dom0 ??
2010-03-27 11:51 ` [Xen-community] " Leena M.
@ 2010-03-27 14:17 ` Pasi Kärkkäinen
0 siblings, 0 replies; 3+ messages in thread
From: Pasi Kärkkäinen @ 2010-03-27 14:17 UTC (permalink / raw)
To: Leena M.; +Cc: xen-devel, xen-users, xen-community, Mark Frasa
On Sat, Mar 27, 2010 at 05:21:25PM +0530, Leena M. wrote:
> I am not able to boot Xen , It gets stuck in run-level 5 after
> Xenconsoled script is called.
So the problem is in dom0, not actually in Xen.
> it gives error soething like
> Error: Error connecting to xend: No such file or directory. Is xend
> running?
>
So that means xend is not running.
Do you have xen-evtchn driver module loaded? Do you have xenfs mounted to /proc/xen?
Do you have files in /proc/xen/ directory?
See this wiki page for more information about troubleshooting pv_ops dom0 kernel:
http://wiki.xensource.com/xenwiki/XenParavirtOps
Also I recommend you to upgrade to later version of pv_ops dom0 kernel,
2.6.31.5 is pretty old already and many many bugs have been fixed after that.
-- Pasi
> $ ls /boot/
> config-2.6.18.8-xen vmlinuz-2.6.18.8-xen
> config-2.6.31.5 vmlinuz-2.6.31.5
> config-2.6.31.5-127.fc12.i686.PAE
> vmlinuz-2.6.31.5-127.fc12.i686.PAE
> efi xen-3.4.2.gz
> grub xen-3.4.3-rc4-pre.gz
> initramfs-2.6.31.5-127.fc12.i686.PAE.img xen-3.4.gz
> initramfs-2.6.31.5.img xen-3.gz
> initrd-2.6.18.8-xen.img xen.gz
> System.map-2.6.18.8-xen xen-syms-3.4.2
> System.map-2.6.31.5 xen-syms-3.4.3-rc4-pre
> System.map-2.6.31.5-127.fc12.i686.PAE
>
> [onkar@localhost boot]$ uname -a
> Linux localhost.localdomain 2.6.31.5 #2 SMP Wed Mar 10 07:27:18 IST 2010
> i686 i686 i386 GNU/Linux
>
> --------------------------------menu.lst
> ---------------------------------------------------------------------
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this
> file
> # NOTICE: You do not have a /boot partition. This means that
> # all kernel and initrd paths are relative to /, eg.
> # root (hd0,0)
> # kernel /boot/vmlinuz-version ro root=/dev/sda1
> # initrd /boot/initrd-[generic-]version.img
> #boot=/dev/sda
> default=0
> timeout=5
> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> # hiddenmenu
>
> title Fedora (2.6.31.5 - my custom kernel)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.31.5 ro
> root=UUID=2f103b84-46c2-4976-9391-8ac6f6f73181 ro console=tty0
> initrd /boot/initramfs-2.6.31.5.img
>
> title Xen 3.4 / XenLinux 2.6
> root (hd0,0)
> kernel /boot/xen-3.4.gz
> module /boot/vmlinuz-2.6.18.8-xen
> root=UUID=2f103b84-46c2-4976-9391-8ac6f6f73181 ro console=tty0
> module /boot/initrd-2.6.18.8-xen.img
>
> title Fedora (2.6.31.5-127.fc12.i686.PAE)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.31.5-127.fc12.i686.PAE ro
> root=UUID=2f103b84-46c2-4976-9391-8ac6f6f73181 LANG=en_US.UTF-8
> SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
> initrd /boot/initramfs-2.6.31.5-127.fc12.i686.PAE.img
>
> Regards,
> /Leena
>
> On Sat, Mar 27, 2010 at 12:46 PM, Mark Frasa <[1]mark@frasa.net> wrote:
>
> Your kernel version should contain -xen
> Can you paste the output from 'uname'
> Verify that you booted a xen kernel, cuz the steps you followed do not
> include copy the kernel to /boot neither checking grub.
>
> /Mark
> Op 27 mrt 2010 om 04:25 heeft "Leena M." <[2]kernmonk@gmail.com> het
> volgende geschreven:\
>
> Thank you very much for your reply.
>
> Kernel version => 2.6.18.8
> OS => Linux
> configuration file is attached.
>
> Steps I followed :
>
> make world
> make install
> copy initrd image to /boot/
> reboot
> Is there any xend configuration needed ?
> Is there any dom0 configuration needed ??
>
> Please help me to get through this.
>
> Regards,
> Leena
>
> On Sat, Mar 27, 2010 at 12:05 AM, Mark Frasa <[3]mark@frasa.net>
> wrote:
>
> Some more info might be useful like:
>
> - Your kernel version
> - The OS you are running
> - Xen version that is installed
> - etc..
>
> It looks like you did not boot into a xen-kernel, but it might be
> too early to tell.
> At least this line is suspicious:
>
> "[2010-03-16 05:22:34 1656] DEBUG (XendDomain:387) number of vcpus
> to use is 0"
>
> Give some more info an we might be able to help you.
>
> /Mark
>
> 2010/3/26 Leena M. <[4]kernmonk@gmail.com>
>
> ----------------- /var/log/xen/xend.log ----------------------
>
> [2010-03-16 05:22:34 1656] INFO (SrvDaemon:332) Xend Daemon
> started
> [2010-03-16 05:22:34 1656] INFO (SrvDaemon:336) Xend changeset:
> Tue Mar 02 19:22:22 2010 +0000 19913:6063c16aeeaa.
> [2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:140)
> XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time':
> 11566217542L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0,
> 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed':
> 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0,
> 'mem_kb': 4003968L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
> [2010-03-16 05:22:34 1656] INFO (XendDomainInfo:158) Recreating
> domain 0, UUID 00000000-0000-0000-0000-000000000000. at
> /local/domain/0
> [2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:3067) Storing VM
> details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid':
> '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart',
> 'image': '(linux (kernel ))', 'on_poweroff': 'destroy',
> 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash':
> 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail':
> '3', 'bootloader': '', 'name': 'Domain-0'}
> [2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:1629) Storing
> domain details: {'name': 'Domain-0', 'console/limit': '1048576',
> 'memory/target': '4003968', 'vm':
> '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
> 'cpu/0/availability': 'online', 'cpu/1/availability': 'online',
> 'control/platform-feature-multiprocessor-suspend': '1',
> 'console/type': 'xenconsoled'}
> [2010-03-16 05:22:34 1656] DEBUG (XendDomain:453) Adding Domain: 0
> [2010-03-16 05:22:34 1656] DEBUG (XendDomain:387) number of vcpus
> to use is 0
> [2010-03-16 05:22:34 1656] INFO (SrvServer:177) unix
> path=/var/lib/xend/xend-socket
> [2010-03-16 05:22:34 1656] DEBUG (XendDomainInfo:1716)
> XendDomainInfo.handleShutdownWatch
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> VBD.set_device not found
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> VBD.set_type not found
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> session.get_all_records not found
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> event.get_record not found
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> event.get_all not found
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> VIF.get_network not found
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> VIF.set_device not found
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> VIF.set_MAC not found
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> VIF.set_MTU not found
> [2010-03-16 05:22:34 1656] WARNING (XendAPI:701) API call:
> debug.get_all not found
> [2010-03-16 05:22:34 1656] INFO (XMLRPCServer:156) Opening Unix
> domain socket XML-RPC server on /var/run/xend/xen-api.sock;
> authentication has been disabled for this server.
> [2010-03-16 05:22:34 1656] INFO (XMLRPCServer:156) Opening Unix
> domain socket XML-RPC server on /var/run/xend/xmlrpc.sock.
>
> -----------------------------------------------------------
>
> Please also find the xend-config.sxp file.
>
> on booting last message I get on boot screen is
> xenconsoled daemon ... [ok]
> "xend: No such file or directory. Is xend running?"
>
> Please help me , I am struggling with this for quite some time
> now.
>
> Regards,
> Leena
>
> _______________________________________________
> Xen-community mailing list
> [5]Xen-community@lists.xensource.com
> [6]http://lists.xensource.com/mailman/listinfo/xen-community
>
> <config-2.6.18.8-xen>
>
> References
>
> Visible links
> 1. mailto:mark@frasa.net
> 2. mailto:kernmonk@gmail.com
> 3. mailto:mark@frasa.net
> 4. mailto:kernmonk@gmail.com
> 5. mailto:Xen-community@lists.xensource.com
> 6. http://lists.xensource.com/mailman/listinfo/xen-community
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-03-27 14:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-03-26 14:51 Can't boot dom0 ?? Leena M.
[not found] ` <7094659f1003261135h612ac985x471cc92846afbf08@mail.gmail.com>
[not found] ` <e49baca61003262025y4477f5e2j6d3f80f769e75b5f@mail.gmail.com>
[not found] ` <0722B099-4D75-425C-BD7F-1C31638BFD69@frasa.net>
2010-03-27 11:51 ` [Xen-community] " Leena M.
2010-03-27 14:17 ` [Xen-users] " Pasi Kärkkäinen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.