From: Cesar Veiga <cveiga@cesga.es>
To: xen-devel@lists.xensource.com
Subject: xen 3.0.4 does not run
Date: Thu, 22 Mar 2007 12:20:30 +0100 [thread overview]
Message-ID: <4602667E.4070102@cesga.es> (raw)
Hi all,
I had installed the Xen 3.0.3 on a opensuse 10.2 (64 bits) on new
quadcore intel processors with VT support, on a Dell Power Edge 1955
blade. I had many machines working. This installation had a poor network
performance when using hardware virtualization. My applications for MPI
require low network latencies.
I try to upgrade to Xen 3,0.4 to check the network performance.
I downloaded the tarball, and I installed it.
Now my machines doesn't run. Aditionally at the secont xm related comand
used the dom0 crashs.
I ask previously for help at xen-users, there they recommend me the
xen-devel list.
Any help is welcomed
regards, cesar
Last lines of xm dmesg say:
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
(XEN) microcode: error! Bad data in microcode data file
(XEN) microcode: Error in the microcode data
(XEN) mtrr: type mismatch for d8000000,1000000 old: write-back new:
write-combining
My /var/log/xen/xend.log says:
[2007-03-19 15:34:57 xend 3391] INFO (SrvDaemon:283) Xend Daemon started
[2007-03-19 15:34:57 xend 3391] INFO (SrvDaemon:287) Xend changeset: Mon
Jan 08 14:09:25 2007 +0000 13130:4d34be661f31.
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] DEBUG
(XendDomainInfo:212) XendDomainInfo.recreate({'paused': 0, 'cpu_time'
: 16194471880L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0
, 'dom': 0, 'mem_kb': 512144, 'maxmem_kb': 17179869180, 'max_vcpu_id':
7, 'crashed': 0, 'running': 1, 'shutdown': 0, 'onli
ne_vcpus': 8, 'blocked': 0})
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] INFO (XendDomainInfo:224)
Recreating domain 0, UUID 00000000-0000-0000-0000
-000000000000.
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] WARNING
(XendDomainInfo:246) No vm path in store for existing domain 0
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] DEBUG
(XendDomainInfo:712) Storing VM details: {'shadow_memory': '0', 'uuid
': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart',
'on_poweroff': 'destroy', 'name': 'Domain-0', 'xend/res
tart_count': '0', 'vcpus': '8', 'vcpu_avail': '1', 'memory': '501',
'on_crash': 'restart', 'maxmem': '501'}
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] DEBUG
(XendDomainInfo:747) Storing domain details: {'cpu/1/availability': '
offline', 'cpu/3/availability': 'offline', 'name': 'Domain-0',
'console/limit': '1048576', 'cpu/2/availability': 'offline'
, 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
'cpu/7/availability': 'offline', 'cpu/0/availability': '
online', 'memory/target': '513024', 'cpu/5/availability': 'offline',
'cpu/6/availability': 'offline', 'cpu/4/availability'
: 'offline'}
[2007-03-19 15:34:58 xend 3391] DEBUG (XendDomain:153) number of vcpus
to use is 0
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] DEBUG
(XendDomainInfo:933) XendDomainInfo.handleShutdownWatch
xen04:/etc/init.d
reply other threads:[~2007-03-22 11:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4602667E.4070102@cesga.es \
--to=cveiga@cesga.es \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.