John Wang
2010-Jan-24 08:59 UTC
[Xen-users] Why domU not start automatically after server reboot
Hello there,
I have new installed a debian lenny server(intel Xeon E5504, 4 cores) with
xen(3.2-1) vms . A problem is when I reboot the serve(with domU status is
"-b----"), the domU will not get started automatically after the
server booted. But i can start those domUs by using the command "xm
create myDomU1.cfg" in the shell prompt with on error.
The domu can restart automatically orginially. But when i change some
configuration, it now failed to restart. unfortunatelly i dont know which
settings cause the problem.
I check the xend.log and found some error message(see below).
Anyone can help ?
The following information may help you to figure out the problem:
My configured domUs(I start them manually) :
######## Begin running domUs ########
svr1:/etc/xen# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 349 1 r----- 18.0
j1xen 3 768 3 -b---- 5.9
j2xen 4 512 3 -b---- 5.1
j3xen 5 384 3 -b---- 6.2
######## End running domUs ########
########Begin /var/log/xen/xend.log ########
[2010-01-24 14:54:24 2517] INFO (SrvDaemon:331) Xend Daemon started
[2010-01-24 14:54:24 2517] INFO (SrvDaemon:335) Xend changeset: unavailable.
[2010-01-24 14:54:24 2517] INFO (SrvDaemon:342) Xend version: Unknown.
[2010-01-24 14:54:24 2517] INFO (XendNetwork:114) Not recreating missing
unmanaged network eth0
[2010-01-24 14:54:24 2517] INFO (XendDomainInfo:149) Recreating domain 0, UUID
00000000-0000-0000-0000-00000000
0000. at /local/domain/0
[2010-01-24 14:54:24 2517] INFO (XendDomainInfo:1174) Set VCPU count on domain
Domain-0 to 1
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VBD.set_device not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VBD.set_type not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call:
session.get_all_records not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: event.get_record not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: event.get_all not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VM.get_auto_power_on
not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VM.set_auto_power_on
not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VIF.get_network not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VIF.set_device not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VIF.set_MAC not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VIF.set_MTU not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: debug.get_all not
found
[2010-01-24 14:54:24 2517] INFO (XMLRPCServer:149) Opening Unix domain socket
XML-RPC server on /var/run/xend/x
en-api.sock; authentication has been disabled for this server.
[2010-01-24 14:54:24 2517] INFO (XMLRPCServer:149) Opening Unix domain socket
XML-RPC server on /var/run/xend/x
mlrpc.sock.
[2010-01-24 14:54:25 2517] INFO (XendDomainInfo:1514) createDevice: console :
{''protocol'': ''vt100'',
''location'':
''2'', ''uuid'':
''76211aa8-4c9f-1c79-ef47-e4419e2b85f2''}
[2010-01-24 14:54:25 2517] INFO (XendDomainInfo:1514) createDevice: vbd :
{''uuid'': ''cf6c6f7d-bfd5-02e1-defe-59f
b4ff35274'', ''bootable'': 1,
''driver'': ''paravirtualised'',
''dev'': ''xvda1:disk'',
''uname'': ''phy:/dev/wjqVG1/j1xen-sw
ap'', ''mode'': ''w'',
''backend'': ''0''}
[2010-01-24 14:54:25 2517] INFO (XendDomainInfo:1514) createDevice: vbd :
{''uuid'': ''5622b865-d735-4aaf-bcc6-567
2cfa70b13'', ''bootable'': 0,
''driver'': ''paravirtualised'',
''dev'': ''xvda2:disk'',
''uname'': ''phy:/dev/wjqVG1/j1xen-di
sk'', ''mode'': ''w'',
''backend'': ''0''}
[2010-01-24 14:54:25 2517] INFO (XendDomainInfo:1514) createDevice: vif :
{''ip'': ''10.0.0.1'', ''mac'':
''00:16:3E:1
3:5A:D1'', ''script'': ''vif-nat'',
''uuid'':
''127bdc08-4b3c-e61b-88d2-d8fc12a46bfe'',
''backend'': ''0''}
[2010-01-24 14:54:26 2517] INFO (XendCheckpoint:373) xc_domain_restore start:
p2m_size = 30800
[2010-01-24 14:54:26 2517] INFO (XendCheckpoint:373) Reloading memory pages:
0%
[2010-01-24 14:54:28 2517] INFO (XendCheckpoint:373) ERROR Internal error: Error
when reading page (type was 0)
[2010-01-24 14:54:28 2517] INFO (XendCheckpoint:373) Restore exit with rc=1
[2010-01-24 14:54:28 2517] ERROR (XendDomainInfo:1926) XendDomainInfo.destroy:
xc.domain_destroy failed.
Traceback (most recent call last):
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line 1921, in destroyDomain
xc.domain_destroy(self.domid)
Error: (3, ''No such process'')
[2010-01-24 14:54:28 2517] ERROR (XendDomain:1136) Restore failed
Traceback (most recent call last):
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomain.py", line
1134, in domain_restore_fd
return XendCheckpoint.restore(self, fd, paused=paused)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py",
line 239, in restore
forkHelper(cmd, fd, handler.handler, True)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py",
line 361, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib/xen-3.2-1/bin/xc_restore 4 1 1 2 0 0 0 failed
######## End /var/log/xen/xend.log ########
The following is my environment:
#### Begin Server environment ############
svr1:/etc/xen# xm dmesg
(XEN) Xen version 3.2-1 (Debian 3.2.1-2) (waldi@debian.org) (gcc version 4.3.1
(Debian 4.3.1-2) ) Sat Jun 28 15:25:00 UTC 2008
(XEN) Command line: dom0_max_vcpus=1 & dom0_vcpus_pin
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009ec00 (usable)
(XEN) 000000000009ec00 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007f780000 (usable)
(XEN) 000000007f78e000 - 000000007f790000 type 9
(XEN) 000000007f790000 - 000000007f79e000 (ACPI data)
(XEN) 000000007f79e000 - 000000007f7d0000 (ACPI NVS)
(XEN) 000000007f7d0000 - 000000007f7e0000 (reserved)
(XEN) 000000007f7ec000 - 0000000080000000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffe00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2039MB (2088056kB)
(XEN) Xen heap: 9MB (10084kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) PAE enabled, limit: 16 GB
(XEN) Processor #16 7:10 APIC version 21
(XEN) Processor #18 7:10 APIC version 21
(XEN) Processor #20 7:10 APIC version 21
(XEN) Processor #22 7:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 23, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 24, version 32, address 0xfec8a000, GSI 24-47
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2000.143 MHz processor.
(XEN) , L1 D cache: 32K
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping 05
(XEN) Booting processor 1/18 eip 8c000
(XEN) , L1 D cache: 32K
(XEN) CPU1: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping 05
(XEN) Booting processor 2/20 eip 8c000
(XEN) , L1 D cache: 32K
(XEN) CPU2: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping 05
(XEN) Booting processor 3/22 eip 8c000
(XEN) , L1 D cache: 32K
(XEN) CPU3: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping 05
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) Platform timer overflows in 14998 jiffies.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 4 CPUs
(XEN) xenoprof: Initialization failed. Intel processor model 26 for P6 class
family is not supported
(XEN) AMD IOMMU: Disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 32-bit, PAE, lsb
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x100000 -> 0x42e000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (475060 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c042e000
(XEN) Init. ramdisk: c042e000->c1479c00
(XEN) Phys-Mach map: c147a000->c1651ed0
(XEN) Start info: c1652000->c1652474
(XEN) Page tables: c1653000->c1664000
(XEN) Boot stack: c1664000->c1665000
(XEN) TOTAL: c0000000->c1800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Initrd len 0x104bc00, start at 0xc042e000
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(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) Freed 96kB init memory.
#### End Server environment ############
Regards
John Wang
2010-01-24
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
John Wang
2010-Jan-24 11:04 UTC
[Xen-users] Re: Why domU not start automatically after server reboot
Hi there, my problem got solved. It''s due to that there is no free
space in my dom0 disk. The xen do show this hint,but i ignore them and rush
around to find out if there is config mistake. so stupid.
Anyway, after i found the reason, i make room for dom0 disk by delete some big
files. but it still failed to start xend daemon. finally I find the some posts
like this one
http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-virtualization/343286-unable-connect-xend.html
and this one:
http://lists.xensource.com/archives/html/xen-users/2007-10/msg00799.html
According to those post i just delete all the stuff in the directory
/var/lib/xend and /var/lib/xenstored and /var/run/xen*.pid and kill the
xenstored process. And at last reboot the server. Now everything is ok. great!
Sorry to bother you.
Regards
John Wang
2010-01-24
-------------------------------------------------------------
From: John Wang
Date: 2010-01-24 16:59:43
To: xen-users
Cc:
Subject: Why domU not start automatically after server reboot
Hello there,
I have new installed a debian lenny server(intel Xeon E5504, 4 cores) with
xen(3.2-1) vms . A problem is when I reboot the serve(with domU status is
"-b----"), the domU will not get started automatically after the
server booted. But i can start those domUs by using the command "xm
create myDomU1.cfg" in the shell prompt with on error.
The domu can restart automatically orginially. But when i change some
configuration, it now failed to restart. unfortunatelly i dont know which
settings cause the problem.
I check the xend.log and found some error message(see below).
Anyone can help ?
The following information may help you to figure out the problem:
My configured domUs(I start them manually) :
######## Begin running domUs ########
svr1:/etc/xen# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 349 1 r----- 18.0
j1xen 3 768 3 -b---- 5.9
j2xen 4 512 3 -b---- 5.1
j3xen 5 384 3 -b---- 6.2
######## End running domUs ########
########Begin /var/log/xen/xend.log ########
[2010-01-24 14:54:24 2517] INFO (SrvDaemon:331) Xend Daemon started
[2010-01-24 14:54:24 2517] INFO (SrvDaemon:335) Xend changeset: unavailable.
[2010-01-24 14:54:24 2517] INFO (SrvDaemon:342) Xend version: Unknown.
[2010-01-24 14:54:24 2517] INFO (XendNetwork:114) Not recreating missing
unmanaged network eth0
[2010-01-24 14:54:24 2517] INFO (XendDomainInfo:149) Recreating domain 0, UUID
00000000-0000-0000-0000-00000000
0000. at /local/domain/0
[2010-01-24 14:54:24 2517] INFO (XendDomainInfo:1174) Set VCPU count on domain
Domain-0 to 1
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VBD.set_device not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VBD.set_type not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call:
session.get_all_records not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: event.get_record not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: event.get_all not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VM.get_auto_power_on
not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VM.set_auto_power_on
not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VIF.get_network not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VIF.set_device not
found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VIF.set_MAC not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: VIF.set_MTU not found
[2010-01-24 14:54:24 2517] WARNING (XendAPI:678) API call: debug.get_all not
found
[2010-01-24 14:54:24 2517] INFO (XMLRPCServer:149) Opening Unix domain socket
XML-RPC server on /var/run/xend/x
en-api.sock; authentication has been disabled for this server.
[2010-01-24 14:54:24 2517] INFO (XMLRPCServer:149) Opening Unix domain socket
XML-RPC server on /var/run/xend/x
mlrpc.sock.
[2010-01-24 14:54:25 2517] INFO (XendDomainInfo:1514) createDevice: console :
{''protocol'': ''vt100'',
''location'':
''2'', ''uuid'':
''76211aa8-4c9f-1c79-ef47-e4419e2b85f2''}
[2010-01-24 14:54:25 2517] INFO (XendDomainInfo:1514) createDevice: vbd :
{''uuid'': ''cf6c6f7d-bfd5-02e1-defe-59f
b4ff35274'', ''bootable'': 1,
''driver'': ''paravirtualised'',
''dev'': ''xvda1:disk'',
''uname'': ''phy:/dev/wjqVG1/j1xen-sw
ap'', ''mode'': ''w'',
''backend'': ''0''}
[2010-01-24 14:54:25 2517] INFO (XendDomainInfo:1514) createDevice: vbd :
{''uuid'': ''5622b865-d735-4aaf-bcc6-567
2cfa70b13'', ''bootable'': 0,
''driver'': ''paravirtualised'',
''dev'': ''xvda2:disk'',
''uname'': ''phy:/dev/wjqVG1/j1xen-di
sk'', ''mode'': ''w'',
''backend'': ''0''}
[2010-01-24 14:54:25 2517] INFO (XendDomainInfo:1514) createDevice: vif :
{''ip'': ''10.0.0.1'', ''mac'':
''00:16:3E:1
3:5A:D1'', ''script'': ''vif-nat'',
''uuid'':
''127bdc08-4b3c-e61b-88d2-d8fc12a46bfe'',
''backend'': ''0''}
[2010-01-24 14:54:26 2517] INFO (XendCheckpoint:373) xc_domain_restore start:
p2m_size = 30800
[2010-01-24 14:54:26 2517] INFO (XendCheckpoint:373) Reloading memory pages:
0%
[2010-01-24 14:54:28 2517] INFO (XendCheckpoint:373) ERROR Internal error: Error
when reading page (type was 0)
[2010-01-24 14:54:28 2517] INFO (XendCheckpoint:373) Restore exit with rc=1
[2010-01-24 14:54:28 2517] ERROR (XendDomainInfo:1926) XendDomainInfo.destroy:
xc.domain_destroy failed.
Traceback (most recent call last):
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line 1921, in destroyDomain
xc.domain_destroy(self.domid)
Error: (3, ''No such process'')
[2010-01-24 14:54:28 2517] ERROR (XendDomain:1136) Restore failed
Traceback (most recent call last):
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomain.py", line
1134, in domain_restore_fd
return XendCheckpoint.restore(self, fd, paused=paused)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py",
line 239, in restore
forkHelper(cmd, fd, handler.handler, True)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py",
line 361, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib/xen-3.2-1/bin/xc_restore 4 1 1 2 0 0 0 failed
######## End /var/log/xen/xend.log ########
The following is my environment:
#### Begin Server environment ############
svr1:/etc/xen# xm dmesg
(XEN) Xen version 3.2-1 (Debian 3.2.1-2) (waldi@debian.org) (gcc version 4.3.1
(Debian 4.3.1-2) ) Sat Jun 28 15:25:00 UTC 2008
(XEN) Command line: dom0_max_vcpus=1 & dom0_vcpus_pin
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009ec00 (usable)
(XEN) 000000000009ec00 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007f780000 (usable)
(XEN) 000000007f78e000 - 000000007f790000 type 9
(XEN) 000000007f790000 - 000000007f79e000 (ACPI data)
(XEN) 000000007f79e000 - 000000007f7d0000 (ACPI NVS)
(XEN) 000000007f7d0000 - 000000007f7e0000 (reserved)
(XEN) 000000007f7ec000 - 0000000080000000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffe00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2039MB (2088056kB)
(XEN) Xen heap: 9MB (10084kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) PAE enabled, limit: 16 GB
(XEN) Processor #16 7:10 APIC version 21
(XEN) Processor #18 7:10 APIC version 21
(XEN) Processor #20 7:10 APIC version 21
(XEN) Processor #22 7:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 23, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 24, version 32, address 0xfec8a000, GSI 24-47
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2000.143 MHz processor.
(XEN) , L1 D cache: 32K
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping 05
(XEN) Booting processor 1/18 eip 8c000
(XEN) , L1 D cache: 32K
(XEN) CPU1: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping 05
(XEN) Booting processor 2/20 eip 8c000
(XEN) , L1 D cache: 32K
(XEN) CPU2: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping 05
(XEN) Booting processor 3/22 eip 8c000
(XEN) , L1 D cache: 32K
(XEN) CPU3: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping 05
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) Platform timer overflows in 14998 jiffies.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 4 CPUs
(XEN) xenoprof: Initialization failed. Intel processor model 26 for P6 class
family is not supported
(XEN) AMD IOMMU: Disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 32-bit, PAE, lsb
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x100000 -> 0x42e000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (475060 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c042e000
(XEN) Init. ramdisk: c042e000->c1479c00
(XEN) Phys-Mach map: c147a000->c1651ed0
(XEN) Start info: c1652000->c1652474
(XEN) Page tables: c1653000->c1664000
(XEN) Boot stack: c1664000->c1665000
(XEN) TOTAL: c0000000->c1800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Initrd len 0x104bc00, start at 0xc042e000
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(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) Freed 96kB init memory.
#### End Server environment ############
Regards
John Wang
2010-01-24
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Moi même
2010-Jan-24 13:33 UTC
Re: [Xen-users] Why domU not start automatically after server reboot
Le dimanche 24 janvier 2010 à 16:59 +0800, John Wang a écrit :> Hello there, > > I have new installed a debian lenny server(intel Xeon E5504, 4 cores) with xen(3.2-1) vms . A problem is when I reboot the serve(with domU status is "-b----"), the domU will not get started automatically after the server booted. But i can start those domUs by using the command "xm create myDomU1.cfg" in the shell prompt with on error. > > The domu can restart automatically orginially. But when i change some configuration, it now failed to restart. unfortunatelly i dont know which settings cause the problem. > > I check the xend.log and found some error message(see below). > > Anyone can help ? > > The following information may help you to figure out the problem: > > My configured domUs(I start them manually) : >Hello, A domain created with "xm create" is created, runs but is not "catalogued" so the machine can''t even start ! If you want "persistent" domains you have to create them with the "xm new " command. So the machine are registered and should start with "xm start". When the machines are OK, you copy their description files to "/etc/xen/auto" if you want then start at boot. But I don''t like that solution (with /etc/xen/auto) as the start is often a little bit to early eg : NFS or Iscsi mounts are not OK ... I prefer to do a start mith my own script when all the machine is started (start NFS and Iscsi at init level 3) and I start the machines at init level 5. Regards JP Pozzi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users