From: nizhichen <nizhichen@gmail.com>
To: xen-devel@lists.xensource.com
Subject: domain U create problem with xen-unstable
Date: Wed, 13 Jan 2010 20:50:10 +0800 [thread overview]
Message-ID: <e8d19b9f1001130450h3d35d587w1d861023a5de7893@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 6742 bytes --]
Yesterday I downloaded the latest changeset, installed and succeeded in
checking with "xm list".
However, when I was trying to create Domain U, it showed:
Using config file "/etc/xen/CentOS.hvm".
Error: device model '/usr/lib64/xen/bin/qemu-dm' not found
I found qemu-dm in /usr/lib/xen/bin, then I copy it to the tree above,
vnc started but there's another error says:
ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (20400 MBytes)
Here's the log for the two time's creating:
[2010-01-13 18:51:29 4234] INFO (SrvDaemon:332) Xend Daemon started
[2010-01-13 18:51:29 4234] INFO (SrvDaemon:336) Xend changeset: Tue Jan 12
07:17:40 2010 +0000 20790:0e3910f1de64.
[2010-01-13 18:51:29 4234] DEBUG (XendDomainInfo:149)
XendDomainInfo.recreate({'max_vcpu_id': 3, 'cpu_time': 20600861892L,
'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 4,
'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb':
17179869180L, 'shutdown': 0, 'mem_kb': 520448L, 'handle': [0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
[2010-01-13 18:51:29 4234] INFO (XendDomainInfo:166) Recreating domain 0,
UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
[2010-01-13 18:51:29 4234] DEBUG (XendDomainInfo:3377) Storing VM details:
{'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid':
'00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image':
'(linux (kernel ) (superpages 0) (tsc_mode 0) (nomigrate 0))',
'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignore',
'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '4',
'vcpu_avail': '15', 'bootloader': '', 'name': 'Domain-0'}
[2010-01-13 18:51:29 4234] DEBUG (XendDomainInfo:1782) Storing domain
details: {'cpu/3/availability': 'online', 'description': '',
'console/limit': '1048576', 'memory/target': '520448', 'cpu/2/availability':
'online', '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', 'name': 'Domain-0'}
[2010-01-13 18:51:29 4234] DEBUG (XendDomain:464) Adding Domain: 0
[2010-01-13 18:51:29 4234] DEBUG (XendDomain:398) number of vcpus to use is
0
[2010-01-13 18:51:29 4234] DEBUG (XendDomainInfo:1869)
XendDomainInfo.handleShutdownWatch
[2010-01-13 18:51:29 4234] WARNING (XendAPI:705) API call: VBD.set_device
not found
[2010-01-13 18:51:29 4234] WARNING (XendAPI:705) API call: VBD.set_type not
found
[2010-01-13 18:51:29 4234] WARNING (XendAPI:705) API call:
session.get_all_records not found
[2010-01-13 18:51:29 4234] WARNING (XendAPI:705) API call: event.get_record
not found
[2010-01-13 18:51:29 4234] WARNING (XendAPI:705) API call: event.get_all not
found
[2010-01-13 18:51:29 4234] WARNING (XendAPI:705) API call: VIF.set_device
not found
[2010-01-13 18:51:29 4234] WARNING (XendAPI:705) API call: VIF.set_MAC not
found
[2010-01-13 18:51:29 4234] WARNING (XendAPI:705) API call: VIF.set_MTU not
found
[2010-01-13 18:51:29 4234] WARNING (XendAPI:705) API call: debug.get_all not
found
[2010-01-13 18:51:29 4234] 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-01-13 18:51:29 4234] INFO (XMLRPCServer:156) Opening Unix domain
socket XML-RPC server on /var/run/xend/xmlrpc.sock.
[2010-01-13 18:52:43 4234] WARNING (XendConfig:874) Unconverted key:
Description
[2010-01-13 18:53:17 4234] WARNING (XendConfig:874) Unconverted key:
Description
............
[2010-01-13 20:15:32 4234] DEBUG (XendDomainInfo:1782) Storing domain
details: {'console/port': '3', 'description': '', 'console/limit':
'1048576', 'store/port': '2', 'vm':
'/vm/6e28228c-3aba-7cf3-ac7b-e2e9b7eac653', 'domid': '1',
'image/suspend-cancel': '1', 'cpu/0/availability': 'online',
'memory/target': '524288',
'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref':
'1044476', 'console/type': 'ioemu', 'name': 'CentOS_1'}
[2010-01-13 20:15:34 4234] DEBUG (DevController:95) DevController: writing
{'state': '1', 'backend-id': '0', 'backend':
'/local/domain/0/backend/console/1/0'} to /local/domain/1/device/console/0.
[2010-01-13 20:15:34 4234] DEBUG (DevController:97) DevController: writing
{'domain': 'CentOS_1', 'frontend': '/local/domain/1/device/console/0',
'uuid': '71b356d6-31da-5f94-24a9-de33f71ad3d0', 'frontend-id': '1', 'state':
'1', 'location': '3', 'online': '1', 'protocol': 'vt100'} to
/local/domain/0/backend/console/1/0.
[2010-01-13 20:15:34 4234] DEBUG (XendDomainInfo:1869)
XendDomainInfo.handleShutdownWatch
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
vif2.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
vif.
[2010-01-13 20:15:34 4234] DEBUG (DevController:144) Waiting for 0.
[2010-01-13 20:15:34 4234] DEBUG (DevController:628) hotplugStatusCallback
/local/domain/0/backend/vif/1/0/hotplug-status.
[2010-01-13 20:15:34 4234] DEBUG (DevController:642) hotplugStatusCallback
1.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
vscsi.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
vbd.
[2010-01-13 20:15:34 4234] DEBUG (DevController:144) Waiting for 768.
[2010-01-13 20:15:34 4234] DEBUG (DevController:628) hotplugStatusCallback
/local/domain/0/backend/vbd/1/768/hotplug-status.
[2010-01-13 20:15:34 4234] DEBUG (DevController:642) hotplugStatusCallback
1.
[2010-01-13 20:15:34 4234] DEBUG (DevController:144) Waiting for 5632.
[2010-01-13 20:15:34 4234] DEBUG (DevController:628) hotplugStatusCallback
/local/domain/0/backend/vbd/1/5632/hotplug-status.
[2010-01-13 20:15:34 4234] DEBUG (DevController:642) hotplugStatusCallback
1.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
ioports.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
irq.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
vkbd.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
vfb.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
console.
[2010-01-13 20:15:34 4234] DEBUG (DevController:144) Waiting for 0.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
pci.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
tap2.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
tap.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
vusb.
[2010-01-13 20:15:34 4234] DEBUG (DevController:139) Waiting for devices
vtpm.
[2010-01-13 20:15:34 4234] INFO (XendDomain:1206) Domain CentOS_1 (1)
unpaused.
[-- Attachment #1.2: Type: text/html, Size: 8025 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-01-13 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 12:50 nizhichen [this message]
2010-01-13 17:19 ` domain U create problem with xen-unstable Keir Fraser
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=e8d19b9f1001130450h3d35d587w1d861023a5de7893@mail.gmail.com \
--to=nizhichen@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).