18.24. 翻​​​​​​​译​​​​​​​错​​​​​​​误​​​​​​​信​​​​​​​息​​​​​​​

你​​​​​​​接​​​​​​​收​​​​​​​到​​​​​​​下​​​​​​​面​​​​​​​的​​​​​​​错​​​​​​​误​​​​​​​:
failed domain creation due to memory shortage, unable to balloon domain0
如​​​​​​​果​​​​​​​没​​​​​​​有​​​​​​​足​​​​​​​够​​​​​​​的​​​​​​​可​​​​​​​用​​​​​​​内​​​​​​​存​​​​​​​,域​​​​​​​将​​​​​​​不​​​​​​​能​​​​​​​运​​​​​​​行​​​​​​​。​​​​​​​Domain0 没​​​​​​​有​​​​​​​足​​​​​​​够​​​​​​​的​​​​​​​空​​​​​​​间​​​​​​​来​​​​​​​容​​​​​​​纳​​​​​​​新​​​​​​​创​​​​​​​建​​​​​​​的​​​​​​​客​​​​​​​户​​​​​​​机​​​​​​​。​​​​​​​你​​​​​​​可​​​​​​​以​​​​​​​检​​​​​​​查​​​​​​​ xend.log 里​​​​​​​关​​​​​​​于​​​​​​​这​​​​​​​个​​​​​​​错​​​​​​​误​​​​​​​的​​​​​​​内​​​​​​​容​​​​​​​:
[2006-12-21] 20:33:31 xend 3198] DEBUG (balloon:133) Balloon: 558432 Kib free; 0 to scrub; need 1048576; retries: 20
[2006-12-21] 20:33:31 xend. XendDomainInfo 3198] ERROR (XendDomainInfo: 202
Domain construction failed
You can check the amount of memory in use by domain0 by using the xm list Domain0 command. If domain0 is not ballooned down, you can use the command "xm mem-set Domain-0 NewMemSize" to check memory.
你​​​​​​​接​​​​​​​收​​​​​​​到​​​​​​​下​​​​​​​面​​​​​​​的​​​​​​​错​​​​​​​误​​​​​​​:
wrong kernel image: non-PAE kernel on a PAE
This message indicates that you are trying to run an unsupported guest kernel image on your Hypervisor. This happens when you try to boot a non-PAE paravirtual guest kernel on a RHEL 5.1 hypervisor. Red Hat Virtualization only supports guest kernels with PAE and 64bit architectures.
键​​​​​​​入​​​​​​​这​​​​​​​个​​​​​​​命​​​​​​​令​​​​​​​:
[root@smith]# xm create -c va base

Using config file "va-base"
Error: (22, 'invalid argument')
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] ERRORs
(XendDomainInfo:202) Domain construction failed

Traceback (most recent call last)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195 in create vm.initDomain()
File " /usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1363 in initDomain raise VmError(str(exn))
VmError: (22, 'Invalid argument')
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] DEBUG (XenDomainInfo: 1449]
XendDlomainInfo.destroy: domin=1
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] DEBUG (XenDomainInfo: 1457]
XendDlomainInfo.destroy:Domain(1)
如​​​​​​​果​​​​​​​你​​​​​​​需​​​​​​​要​​​​​​​运​​​​​​​行​​​​​​​ 32 位​​​​​​​/非​​​​​​​ PAE 内​​​​​​​核​​​​​​​,你​​​​​​​将​​​​​​​需​​​​​​​要​​​​​​​把​​​​​​​客​​​​​​​户​​​​​​​机​​​​​​​作​​​​​​​为​​​​​​​完​​​​​​​全​​​​​​​虚​​​​​​​拟​​​​​​​化​​​​​​​的​​​​​​​虚​​​​​​​拟​​​​​​​机​​​​​​​运​​​​​​​行​​​​​​​。​​​​​​​对​​​​​​​于​​​​​​​半​​​​​​​虚​​​​​​​拟​​​​​​​化​​​​​​​的​​​​​​​客​​​​​​​户​​​​​​​机​​​​​​​,如​​​​​​​果​​​​​​​你​​​​​​​需​​​​​​​要​​​​​​​运​​​​​​​行​​​​​​​ 32 位​​​​​​​的​​​​​​​ PAE 客​​​​​​​户​​​​​​​机​​​​​​​,你​​​​​​​必​​​​​​​须​​​​​​​具​​​​​​​有​​​​​​​ 32 位​​​​​​​的​​​​​​​ PAE 监​​​​​​​控​​​​​​​程​​​​​​​序​​​​​​​。​​​​​​​对​​​​​​​于​​​​​​​半​​​​​​​虚​​​​​​​拟​​​​​​​化​​​​​​​的​​​​​​​客​​​​​​​户​​​​​​​机​​​​​​​,如​​​​​​​果​​​​​​​你​​​​​​​要​​​​​​​运​​​​​​​行​​​​​​​ 64 位​​​​​​​的​​​​​​​ PAE 客​​​​​​​户​​​​​​​机​​​​​​​,你​​​​​​​必​​​​​​​须​​​​​​​具​​​​​​​有​​​​​​​ 64 位​​​​​​​的​​​​​​​ PAE 监​​​​​​​控​​​​​​​程​​​​​​​序​​​​​​​。​​​​​​​对​​​​​​​于​​​​​​​完​​​​​​​全​​​​​​​虚​​​​​​​拟​​​​​​​化​​​​​​​的​​​​​​​客​​​​​​​户​​​​​​​机​​​​​​​,你​​​​​​​必​​​​​​​须​​​​​​​用​​​​​​​ 64 位​​​​​​​的​​​​​​​监​​​​​​​控​​​​​​​程​​​​​​​序​​​​​​​运​​​​​​​行​​​​​​​ 64 位​​​​​​​客​​​​​​​户​​​​​​​机​​​​​​​。​​​​​​​RHEL 5 i686 里​​​​​​​的​​​​​​​ 32 位​​​​​​​ PAE 监​​​​​​​控​​​​​​​程​​​​​​​序​​​​​​​只​​​​​​​支​​​​​​​持​​​​​​​运​​​​​​​行​​​​​​​ 32 位​​​​​​​的​​​​​​​并​​​​​​​行​​​​​​​虚​​​​​​​拟​​​​​​​化​​​​​​​和​​​​​​​ 32 位​​​​​​​的​​​​​​​完​​​​​​​全​​​​​​​虚​​​​​​​拟​​​​​​​化​​​​​​​的​​​​​​​客​​​​​​​户​​​​​​​机​​​​​​​操​​​​​​​作​​​​​​​系​​​​​​​统​​​​​​​。​​​​​​​64 位​​​​​​​监​​​​​​​控​​​​​​​程​​​​​​​序​​​​​​​只​​​​​​​支​​​​​​​持​​​​​​​ 64 位​​​​​​​的​​​​​​​并​​​​​​​行​​​​​​​虚​​​​​​​拟​​​​​​​化​​​​​​​客​​​​​​​户​​​​​​​机​​​​​​​。​​​​​​​
This happens when you move the full virtualized HVM guest onto a RHEL 5.1 system. Your guest may fail to boot and you will see an error in the console screen. Check the PAE entry in your configuration file and ensure that pae=1.You should use a 32bit distibution.
你​​​​​​​接​​​​​​​收​​​​​​​到​​​​​​​下​​​​​​​面​​​​​​​的​​​​​​​错​​​​​​​误​​​​​​​:
Unable to open a connection to the Xen hypervisor or daemon
当​​​​​​​ virt-manager 程​​​​​​​序​​​​​​​不​​​​​​​能​​​​​​​启​​​​​​​动​​​​​​​时​​​​​​​,会​​​​​​​出​​​​​​​现​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​。​​​​​​​当​​​​​​​ /etc/hosts 配​​​​​​​置​​​​​​​文​​​​​​​件​​​​​​​里​​​​​​​没​​​​​​​有​​​​​​​ localhost 条​​​​​​​目​​​​​​​时​​​​​​​会​​​​​​​产​​​​​​​生​​​​​​​这​​​​​​​个​​​​​​​错​​​​​​​误​​​​​​​。​​​​​​​请​​​​​​​确​​​​​​​认​​​​​​​配​​​​​​​置​​​​​​​文​​​​​​​件​​​​​​​里​​​​​​​是​​​​​​​否​​​​​​​启​​​​​​​用​​​​​​​了​​​​​​​ localhost 条​​​​​​​目​​​​​​​。​​​​​​​下​​​​​​​面​​​​​​​是​​​​​​​一​​​​​​​个​​​​​​​错​​​​​​​误​​​​​​​的​​​​​​​ localhost 条​​​​​​​目​​​​​​​示​​​​​​​例​​​​​​​:
# Do not remove the following line, or various programs
# that require network functionality will fail.
localhost.localdomain localhost
下​​​​​​​面​​​​​​​是​​​​​​​一​​​​​​​个​​​​​​​正​​​​​​​确​​​​​​​的​​​​​​​ localhost 条​​​​​​​目​​​​​​​示​​​​​​​例​​​​​​​:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
localhost.localdomain. localhost
你​​​​​​​会​​​​​​​接​​​​​​​收​​​​​​​到​​​​​​​下​​​​​​​面​​​​​​​的​​​​​​​错​​​​​​​误​​​​​​​(在​​​​​​​ xen-xend.log file 文​​​​​​​件​​​​​​​里​​​​​​​):
Bridge xenbr1 does not exist!
This happens when the guest's bridge is incorrectly configured and this forces the Xen hotplug scipts to timeout. If you move configuration files between hosts, you must ensure that you update the guest configuration files to reflect network topology and configuration modifications. When you attempt to start a guest that has an incorrect or non-existent Xen bridge configuration, you will receive the following errors:
[root@trumble virt]# xm create r5b2-mySQL01

Using config file " r5b2-mySQL01"
Going to boot Red Hat Enterprise Linux Server (2.6.18.-1.2747 .el5xen)
kernel: /vmlinuz-2.6.18-12747.el5xen
initrd: /initrd-2.6.18-1.2747.el5xen.img
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
另​​​​​​​外​​​​​​​,xend.log 里​​​​​​​会​​​​​​​有​​​​​​​下​​​​​​​面​​​​​​​的​​​​​​​错​​​​​​​误​​​​​​​:
[2006-11-14 15:07:08 xend 3875] DEBUG (DevController:143) Waiting for devices vif
[2006-11-14 15:07:08 xend 3875] DEBUG (DevController:149) Waiting for 0
[2006-11-14 15:07:08 xend 3875] DEBUG (DevController:464) hotplugStatusCallback

/local/domain/0/backend/vif/2/0/hotplug-status

[2006-11-14 15:08:09 xend.XendDomainInfo 3875] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=2
[2006-11-14 15:08:09 xend.XendDomainInfo 3875] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(2)
[2006-11-14 15:07:08 xend 3875] DEBUG (DevController:464) hotplugStatusCallback

/local/domain/0/backend/vif/2/0/hotplug-status
要​​​​​​​解​​​​​​​决​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​,你​​​​​​​必​​​​​​​须​​​​​​​编​​​​​​​辑​​​​​​​你​​​​​​​的​​​​​​​客​​​​​​​户​​​​​​​机​​​​​​​配​​​​​​​置​​​​​​​文​​​​​​​件​​​​​​​,并​​​​​​​修​​​​​​​改​​​​​​​ vif 条​​​​​​​目​​​​​​​。​​​​​​​找​​​​​​​到​​​​​​​配​​​​​​​置​​​​​​​文​​​​​​​件​​​​​​​里​​​​​​​的​​​​​​​ vif 条​​​​​​​目​​​​​​​,假​​​​​​​定​​​​​​​你​​​​​​​把​​​​​​​ xenbr0 作​​​​​​​为​​​​​​​缺​​​​​​​省​​​​​​​网​​​​​​​桥​​​​​​​,正​​​​​​​确​​​​​​​的​​​​​​​设​​​​​​​置​​​​​​​应​​​​​​​该​​​​​​​如​​​​​​​下​​​​​​​所​​​​​​​示​​​​​​​:
# vif = ['mac=00:16:3e:49:1d:11, bridge=xenbr0',]
你​​​​​​​接​​​​​​​收​​​​​​​到​​​​​​​这​​​​​​​些​​​​​​​ python 错​​​​​​​误​​​​​​​:
[root@python xen]# xm shutdown win2k3xen12
[root@python xen]# xm create win2k3xen12

Using config file "win2k3xen12".

/usr/lib64/python2.4/site-packages/xenxm/opts.py:520: Deprecation Warning:
Non ASCII character '\xc0' in file win2k3xen12 on line 1, but no encoding
declared; see http://www.python.org/peps/pep-0263.html for details

execfile (defconfig, globs, locs,)
Error: invalid syntax 9win2k3xen12, line1)
当​​​​​​​遇​​​​​​​到​​​​​​​无​​​​​​​效​​​​​​​的​​​​​​​(或​​​​​​​不​​​​​​​正​​​​​​​确​​​​​​​的​​​​​​​)配​​​​​​​置​​​​​​​文​​​​​​​件​​​​​​​时​​​​​​​,Python 生​​​​​​​成​​​​​​​这​​​​​​​些​​​​​​​错​​​​​​​误​​​​​​​。​​​​​​​要​​​​​​​解​​​​​​​决​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​,你​​​​​​​必​​​​​​​须​​​​​​​更​​​​​​​正​​​​​​​不​​​​​​​正​​​​​​​确​​​​​​​的​​​​​​​配​​​​​​​置​​​​​​​文​​​​​​​件​​​​​​​,或​​​​​​​者​​​​​​​生​​​​​​​成​​​​​​​一​​​​​​​个​​​​​​​新​​​​​​​的​​​​​​​文​​​​​​​件​​​​​​​。​​​​​​​

为了尽快向用户提供最新的信息,本文档可能会包括由机器自动从英文原文翻译的内容。如需更多信息,请参阅此说明。