Hi,
Since a week or two I can''t create two of my three WinXP
DomU''s anymore, the
third one starts just fine.
This is the basic error message I get:
# xm create WinXPViaLilaGeert
Using config file "./WinXPViaLilaGeert".
Error: Creating domain failed: name=WinXPViaLilaGeert
There is little information in this error message. /var/log/xen/xend.log has a
little more:
[2009-06-13 14:13:51 4862] DEBUG (XendDomainInfo:89)
XendDomainInfo.create([''vm'', [''name'',
''WinXPViaLilaGeert''], [''memory'', 512],
[''vcpus'',
1], [''on_xend_start'', ''ignore''],
[''on_xend_stop'', ''ignore''],
[''image'',
[''hvm'', [''kernel'',
''/usr/lib/xen/boot/hvmloader''],
[''device_model'',
''/usr/lib/xen/bin/qemu-dm''], [''pae'', 1],
[''vcpus'', 1], [''boot'',
''c''], [''fda'',
''''], [''fdb'', ''''],
[''timer_mode'', 0], [''localtime'', 0],
[''ser
ial'', ''pty''], [''stdvga'', 0],
[''isa'', 0], [''nographic'', 0],
[''soundhw'',
''sb16''], [''vnc'', 0],
[''vncdisplay'', 100], [''vncunused'', 1],
[''vnclis
ten'', ''0.0.0.0''], [''display'',
''localhost:10.0''], [''xauthority'',
''/root/.xauthociQOV''], [''rtc_timeoffset'',
''0''], [''monitor'', 1],
[''acpi'', 0]
, [''apic'', 1], [''usb'', 1],
[''usbdevice'', ''tablet''],
[''keymap'', ''''], [''pci'',
[]], [''hpet'', 0], [''guest_os_type'',
''default''], [''hap'', 1], [''o
pengl'', 1], [''cpuid'', []],
[''cpuid_check'', []], [''vncpasswd'',
''XXXXXXXX'']]],
[''device'', [''tap'',
[''uname'', ''tap:qcow:/var/lib/xen/images/Win
XP-ViaLilaGeert.qcow''], [''dev'',
''hda''], [''mode'', ''w'']]],
[''device'', [''vbd'',
[''uname'', ''''], [''dev'',
''hdc:cdrom''], [''mode'',
''r'']]], [''device''
, [''vif'', [''bridge'',
''xenbr0''], [''mac'',
''00:16:3e:4a:38:26''], [''type'',
''ioemu'']]]])
[2009-06-13 14:13:51 4862] DEBUG (XendDomainInfo:2036)
XendDomainInfo.constructDomain
[2009-06-13 14:13:51 4862] DEBUG (balloon:132) Balloon: 3560 KiB free; need
2048; done.
[2009-06-13 14:13:51 4862] ERROR (XendDomainInfo:467) VM start failed
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line
446, in start
XendTask.log_progress(0, 30, self._constructDomain)
File "/usr/lib/python2.4/site-packages/xen/xend/XendTask.py", line
209, in
log_progress
retval = func(*args, **kwds)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line
2076, in _constructDomain
raise VmError(''Creating domain failed: name=%s'' %
VmError: Creating domain failed: name=WinXPViaLilaGeert
[2009-06-13 14:13:51 4862] ERROR (XendDomainInfo:94) Domain construction
failed
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 92,
in create
vm.start()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line
446, in start
XendTask.log_progress(0, 30, self._constructDomain)
File "/usr/lib/python2.4/site-packages/xen/xend/XendTask.py", line
209, in
log_progress
retval = func(*args, **kwds)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line
2076, in _constructDomain
raise VmError(''Creating domain failed: name=%s'' %
VmError: Creating domain failed: name=WinXPViaLilaGeert
But still I don''t understand why this isn''t working. A google
search on this
error didn''t reveal much. Where else can I find a hint ?
Some more information:
The failing WinXP domain is a clone of the working WinXP domain. It has worked
fine for some time, but not anymore. The server has been rebooted a couple of
times in the meantime. Maybe that has something to do with it ?
Additional info on my setup:
* Dom0 is CentOS 5.3 (32bit)
* Xen is gitco stable (xen 3.3.1)
# xm dmesg
__ __ _____ _____ _
\ \/ /___ _ __ |___ / |___ / / |
\ // _ \ ''_ \ |_ \ |_ \ | |
/ \ __/ | | | ___) | ___) || |
/_/\_\___|_| |_| |____(_)____(_)_|
(XEN) Xen version 3.3.1 (root@gitco.tld) (gcc version 4.1.2 20071124 (Red Hat
4.1.2-42)) Tue Jan 20 23:35:28 CET 2009
(XEN) Latest ChangeSet: unavailable
(XEN) Command line:
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN) Found 6 MBR signatures
(XEN) Found 6 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e6000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000cbff0000 (usable)
(XEN) 00000000cbff0000 - 00000000cbffe000 (ACPI data)
(XEN) 00000000cbffe000 - 00000000cc000000 (ACPI NVS)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fee00000 - 00000000fef00000 (reserved)
(XEN) 00000000ff700000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000234000000 (usable)
(XEN) System RAM: 8191MB (8388156kB)
(XEN) ACPI: RSDP 000F9410, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT CBFF0100, 0054 (r1 SUPERM OEMXSDT 3000831 MSFT 97)
(XEN) ACPI: FACP CBFF0290, 00F4 (r3 SUPERM OEMFACP 3000831 MSFT 97)
(XEN) ACPI: DSDT CBFF0490, 5082 (r1 1HDM3 1HDM3007 7 INTL 20051117)
(XEN) ACPI: FACS CBFFE000, 0040
(XEN) ACPI: APIC CBFF0390, 00B8 (r1 SUPERM OEMAPIC 3000831 MSFT 97)
(XEN) ACPI: OEMB CBFFE040, 00A7 (r1 SUPERM AMI_OEM 3000831 MSFT 97)
(XEN) ACPI: SRAT CBFF5520, 0110 (r1 AMD HAMMER 1 AMD 1)
(XEN) ACPI: HPET CBFF5630, 0038 (r1 SUPERM OEMHPET0 3000831 MSFT 97)
(XEN) ACPI: SSDT CBFF5670, 03E8 (r1 SUPERM POWERNOW 1 AMD 1)
(XEN) Xen heap: 9MB (9548kB)
(XEN) Domain heap initialised
(XEN) Processor #0 15:1 APIC version 16
(XEN) Processor #1 15:1 APIC version 16
(XEN) Processor #2 15:1 APIC version 16
(XEN) Processor #3 15:1 APIC version 16
(XEN) IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 5, version 17, address 0xcffff000, GSI 40-46
(XEN) IOAPIC[2]: apic_id 6, version 17, address 0xcfffe000, GSI 47-53
(XEN) Enabling APIC mode: Flat. Using 3 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2211.378 MHz processor.
(XEN) AMD SVM: ASIDs disabled.
(XEN) HVM: SVM enabled
(XEN) CPU0: AMD K8 machine check reporting enabled.
(XEN) CPU0: AMD Dual-Core AMD Opteron(tm) Processor 2214 stepping 03
(XEN) Booting processor 1/1 eip 8c000
(XEN) AMD: Disabling C1 Clock Ramping Node #0
(XEN) AMD: Disabling C1 Clock Ramping Node #1
(XEN) AMD SVM: ASIDs disabled.
(XEN) CPU1: AMD K8 machine check reporting enabled.
(XEN) CPU1: AMD Dual-Core AMD Opteron(tm) Processor 2214 stepping 03
(XEN) Booting processor 2/2 eip 8c000
(XEN) AMD SVM: ASIDs disabled.
(XEN) CPU2: AMD K8 machine check reporting enabled.
(XEN) CPU2: AMD Dual-Core AMD Opteron(tm) Processor 2214 stepping 03
(XEN) Booting processor 3/3 eip 8c000
(XEN) AMD SVM: ASIDs disabled.
(XEN) CPU3: AMD K8 machine check reporting enabled.
(XEN) CPU3: AMD Dual-Core AMD Opteron(tm) Processor 2214 stepping 03
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) checking TSC synchronization across 4 CPUs:
(XEN) CPU#0 had 0 usecs TSC skew, fixed it up.
(XEN) CPU#1 had 0 usecs TSC skew, fixed it up.
(XEN) CPU#2 had -1942545 usecs TSC skew, fixed it up.
(XEN) CPU#3 had -1942545 usecs TSC skew, fixed it up.
(XEN) Platform timer is 25.000MHz HPET
(XEN) Brought up 4 CPUs
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 32-bit, PAE, lsb
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0400000 -> 0xc07c7000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (2037008 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0400000->c07c7000
(XEN) Init. ramdisk: c07c7000->c0e9be00
(XEN) Phys-Mach map: c0e9c000->c1669440
(XEN) Start info: c166a000->c166a474
(XEN) Page tables: c166b000->c167c000
(XEN) Boot stack: c167c000->c167d000
(XEN) TOTAL: c0000000->c1800000
(XEN) ENTRY ADDRESS: c0400000
(XEN) Dom0 has maximum 4 VCPUs
(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.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from 00000000:00043bff
to 00000000:00000003.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from 00000000:00043bff
to 00000000:00000003.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from 00000000:00000000
to 00000000:00000003.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from 00000000:00000000
to 00000000:00000003.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from 00000000:00000000
to 00000000:00000003.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from 00000000:00043bff
to 00000000:00000003.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from 00000000:00043bff
to 00000000:00000003.
(XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from 00000000:00000000
to 00000000:00000003.
(XEN) mm.c:707:d1 Error getting mfn 284a5 (pfn 1d38a5) from L1 entry
00000000284a5025 for dom1
(XEN) mm.c:3635:d1 ptwr_emulate: fixing up invalid PAE PTE 00000000284a5025
(XEN) mm.c:676:d1 Non-privileged (1) attempt to map I/O space 000000f8
(XEN) mm.c:676:d1 Non-privileged (1) attempt to map I/O space 000000f8
# xm info
host : aragorn.vialila.lan
release : 2.6.18-92.1.22.el5.centos.plusxen
version : #1 SMP Wed Dec 17 12:11:57 EST 2008
machine : i686
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2211
hw_caps :
178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f:00000000
virt_caps : hvm
total_memory : 8191
free_memory : 3
node_to_cpu : node0:0-3
node_to_memory : node0:3
xen_major : 3
xen_minor : 3
xen_extra : .1
xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xf5800000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)
cc_compile_by : root
cc_compile_domain : gitco.tld
cc_compile_date : Tue Jan 20 23:35:28 CET 2009
I am completely stuck here. Can someone give me a hint please ?
Thanks a lot.
Geert
--
Kobalt W.I.T.
Web & Information Technology
Brusselsesteenweg 152
1850 Grimbergen
Tel : +32 479 339 655
Email: info@kobaltwit.be
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Additional info: I''m not using gplv, it''s plain Windows on HVM. Geert -- Kobalt W.I.T. Web & Information Technology Brusselsesteenweg 152 1850 Grimbergen Tel : +32 479 339 655 Email: info@kobaltwit.be _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hmm, you can probably ignore my question. I rebooted the xen server (the shutdown part took abnormally long) and afterwards the domains came up again. So for now my issue is fixed. Sorry for the noise. Geert On Saturday 13 June 2009, Geert Janssens wrote:> Hi, > > Since a week or two I can''t create two of my three WinXP DomU''s anymore, > the third one starts just fine. > > This is the basic error message I get: > # xm create WinXPViaLilaGeert > Using config file "./WinXPViaLilaGeert". > Error: Creating domain failed: name=WinXPViaLilaGeert > > There is little information in this error message. /var/log/xen/xend.log > has a little more: > [2009-06-13 14:13:51 4862] DEBUG (XendDomainInfo:89) > XendDomainInfo.create([''vm'', [''name'', ''WinXPViaLilaGeert''], [''memory'', > 512], [''vcpus'', > 1], [''on_xend_start'', ''ignore''], [''on_xend_stop'', ''ignore''], [''image'', > [''hvm'', [''kernel'', ''/usr/lib/xen/boot/hvmloader''], [''device_model'', > ''/usr/lib/xen/bin/qemu-dm''], [''pae'', 1], [''vcpus'', 1], [''boot'', ''c''], > [''fda'', ''''], [''fdb'', ''''], [''timer_mode'', 0], [''localtime'', 0], [''ser > ial'', ''pty''], [''stdvga'', 0], [''isa'', 0], [''nographic'', 0], [''soundhw'', > ''sb16''], [''vnc'', 0], [''vncdisplay'', 100], [''vncunused'', 1], [''vnclis > ten'', ''0.0.0.0''], [''display'', ''localhost:10.0''], [''xauthority'', > ''/root/.xauthociQOV''], [''rtc_timeoffset'', ''0''], [''monitor'', 1], [''acpi'', 0] > , [''apic'', 1], [''usb'', 1], [''usbdevice'', ''tablet''], [''keymap'', ''''], [''pci'', > []], [''hpet'', 0], [''guest_os_type'', ''default''], [''hap'', 1], [''o > pengl'', 1], [''cpuid'', []], [''cpuid_check'', []], [''vncpasswd'', > ''XXXXXXXX'']]], [''device'', [''tap'', [''uname'', > ''tap:qcow:/var/lib/xen/images/Win > XP-ViaLilaGeert.qcow''], [''dev'', ''hda''], [''mode'', ''w'']]], [''device'', [''vbd'', > [''uname'', ''''], [''dev'', ''hdc:cdrom''], [''mode'', ''r'']]], [''device'' > , [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:16:3e:4a:38:26''], [''type'', > ''ioemu'']]]]) > [2009-06-13 14:13:51 4862] DEBUG (XendDomainInfo:2036) > XendDomainInfo.constructDomain > [2009-06-13 14:13:51 4862] DEBUG (balloon:132) Balloon: 3560 KiB free; need > 2048; done. > [2009-06-13 14:13:51 4862] ERROR (XendDomainInfo:467) VM start failed > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line > 446, in start > XendTask.log_progress(0, 30, self._constructDomain) > File "/usr/lib/python2.4/site-packages/xen/xend/XendTask.py", line 209, > in log_progress > retval = func(*args, **kwds) > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line > 2076, in _constructDomain > raise VmError(''Creating domain failed: name=%s'' % > VmError: Creating domain failed: name=WinXPViaLilaGeert > [2009-06-13 14:13:51 4862] ERROR (XendDomainInfo:94) Domain construction > failed > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line > 92, in create > vm.start() > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line > 446, in start > XendTask.log_progress(0, 30, self._constructDomain) > File "/usr/lib/python2.4/site-packages/xen/xend/XendTask.py", line 209, > in log_progress > retval = func(*args, **kwds) > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line > 2076, in _constructDomain > raise VmError(''Creating domain failed: name=%s'' % > VmError: Creating domain failed: name=WinXPViaLilaGeert > > But still I don''t understand why this isn''t working. A google search on > this error didn''t reveal much. Where else can I find a hint ? > > Some more information: > The failing WinXP domain is a clone of the working WinXP domain. It has > worked fine for some time, but not anymore. The server has been rebooted a > couple of times in the meantime. Maybe that has something to do with it ? > > Additional info on my setup: > * Dom0 is CentOS 5.3 (32bit) > * Xen is gitco stable (xen 3.3.1) > > # xm dmesg > __ __ _____ _____ _ > \ \/ /___ _ __ |___ / |___ / / | > \ // _ \ ''_ \ |_ \ |_ \ | | > / \ __/ | | | ___) | ___) || | > /_/\_\___|_| |_| |____(_)____(_)_| > > (XEN) Xen version 3.3.1 (root@gitco.tld) (gcc version 4.1.2 20071124 (Red > Hat 4.1.2-42)) Tue Jan 20 23:35:28 CET 2009 > (XEN) Latest ChangeSet: unavailable > (XEN) Command line: > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 2 seconds > (XEN) Disc information: > (XEN) Found 6 MBR signatures > (XEN) Found 6 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009fc00 (usable) > (XEN) 000000000009fc00 - 00000000000a0000 (reserved) > (XEN) 00000000000e6000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000cbff0000 (usable) > (XEN) 00000000cbff0000 - 00000000cbffe000 (ACPI data) > (XEN) 00000000cbffe000 - 00000000cc000000 (ACPI NVS) > (XEN) 00000000e0000000 - 00000000f0000000 (reserved) > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > (XEN) 00000000fee00000 - 00000000fef00000 (reserved) > (XEN) 00000000ff700000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000000234000000 (usable) > (XEN) System RAM: 8191MB (8388156kB) > (XEN) ACPI: RSDP 000F9410, 0024 (r2 ACPIAM) > (XEN) ACPI: XSDT CBFF0100, 0054 (r1 SUPERM OEMXSDT 3000831 MSFT 97) > (XEN) ACPI: FACP CBFF0290, 00F4 (r3 SUPERM OEMFACP 3000831 MSFT 97) > (XEN) ACPI: DSDT CBFF0490, 5082 (r1 1HDM3 1HDM3007 7 INTL 20051117) > (XEN) ACPI: FACS CBFFE000, 0040 > (XEN) ACPI: APIC CBFF0390, 00B8 (r1 SUPERM OEMAPIC 3000831 MSFT 97) > (XEN) ACPI: OEMB CBFFE040, 00A7 (r1 SUPERM AMI_OEM 3000831 MSFT 97) > (XEN) ACPI: SRAT CBFF5520, 0110 (r1 AMD HAMMER 1 AMD 1) > (XEN) ACPI: HPET CBFF5630, 0038 (r1 SUPERM OEMHPET0 3000831 MSFT 97) > (XEN) ACPI: SSDT CBFF5670, 03E8 (r1 SUPERM POWERNOW 1 AMD 1) > (XEN) Xen heap: 9MB (9548kB) > (XEN) Domain heap initialised > (XEN) Processor #0 15:1 APIC version 16 > (XEN) Processor #1 15:1 APIC version 16 > (XEN) Processor #2 15:1 APIC version 16 > (XEN) Processor #3 15:1 APIC version 16 > (XEN) IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23 > (XEN) IOAPIC[1]: apic_id 5, version 17, address 0xcffff000, GSI 40-46 > (XEN) IOAPIC[2]: apic_id 6, version 17, address 0xcfffe000, GSI 47-53 > (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2211.378 MHz processor. > (XEN) AMD SVM: ASIDs disabled. > (XEN) HVM: SVM enabled > (XEN) CPU0: AMD K8 machine check reporting enabled. > (XEN) CPU0: AMD Dual-Core AMD Opteron(tm) Processor 2214 stepping 03 > (XEN) Booting processor 1/1 eip 8c000 > (XEN) AMD: Disabling C1 Clock Ramping Node #0 > (XEN) AMD: Disabling C1 Clock Ramping Node #1 > (XEN) AMD SVM: ASIDs disabled. > (XEN) CPU1: AMD K8 machine check reporting enabled. > (XEN) CPU1: AMD Dual-Core AMD Opteron(tm) Processor 2214 stepping 03 > (XEN) Booting processor 2/2 eip 8c000 > (XEN) AMD SVM: ASIDs disabled. > (XEN) CPU2: AMD K8 machine check reporting enabled. > (XEN) CPU2: AMD Dual-Core AMD Opteron(tm) Processor 2214 stepping 03 > (XEN) Booting processor 3/3 eip 8c000 > (XEN) AMD SVM: ASIDs disabled. > (XEN) CPU3: AMD K8 machine check reporting enabled. > (XEN) CPU3: AMD Dual-Core AMD Opteron(tm) Processor 2214 stepping 03 > (XEN) Total of 4 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) checking TSC synchronization across 4 CPUs: > (XEN) CPU#0 had 0 usecs TSC skew, fixed it up. > (XEN) CPU#1 had 0 usecs TSC skew, fixed it up. > (XEN) CPU#2 had -1942545 usecs TSC skew, fixed it up. > (XEN) CPU#3 had -1942545 usecs TSC skew, fixed it up. > (XEN) Platform timer is 25.000MHz HPET > (XEN) Brought up 4 CPUs > (XEN) I/O virtualisation disabled > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 32-bit, PAE, lsb > (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0400000 -> 0xc07c7000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (2037008 pages to > be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: c0400000->c07c7000 > (XEN) Init. ramdisk: c07c7000->c0e9be00 > (XEN) Phys-Mach map: c0e9c000->c1669440 > (XEN) Start info: c166a000->c166a474 > (XEN) Page tables: c166b000->c167c000 > (XEN) Boot stack: c167c000->c167d000 > (XEN) TOTAL: c0000000->c1800000 > (XEN) ENTRY ADDRESS: c0400000 > (XEN) Dom0 has maximum 4 VCPUs > (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. > (XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from > 00000000:00043bff to 00000000:00000003. > (XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from > 00000000:00043bff to 00000000:00000003. > (XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from > 00000000:00000000 to 00000000:00000003. > (XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from > 00000000:00000000 to 00000000:00000003. > (XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from > 00000000:00000000 to 00000000:00000003. > (XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from > 00000000:00043bff to 00000000:00000003. > (XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from > 00000000:00043bff to 00000000:00000003. > (XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from > 00000000:00000000 to 00000000:00000003. > (XEN) mm.c:707:d1 Error getting mfn 284a5 (pfn 1d38a5) from L1 entry > 00000000284a5025 for dom1 > (XEN) mm.c:3635:d1 ptwr_emulate: fixing up invalid PAE PTE 00000000284a5025 > (XEN) mm.c:676:d1 Non-privileged (1) attempt to map I/O space 000000f8 > (XEN) mm.c:676:d1 Non-privileged (1) attempt to map I/O space 000000f8 > > # xm info > host : aragorn.vialila.lan > release : 2.6.18-92.1.22.el5.centos.plusxen > version : #1 SMP Wed Dec 17 12:11:57 EST 2008 > machine : i686 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 1 > cpu_mhz : 2211 > hw_caps : > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f:00000000 > virt_caps : hvm > total_memory : 8191 > free_memory : 3 > node_to_cpu : node0:0-3 > node_to_memory : node0:3 > xen_major : 3 > xen_minor : 3 > xen_extra : .1 > xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xf5800000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.2 20071124 (Red Hat 4.1.2-42) > cc_compile_by : root > cc_compile_domain : gitco.tld > cc_compile_date : Tue Jan 20 23:35:28 CET 2009 > > I am completely stuck here. Can someone give me a hint please ? > > Thanks a lot. > > Geert-- Kobalt W.I.T. Web & Information Technology Brusselsesteenweg 152 1850 Grimbergen Tel : +32 479 339 655 Email: info@kobaltwit.be _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Jun 13, 2009 at 9:28 PM, Geert Janssens<info@kobaltwit.be> wrote:> Hmm, you can probably ignore my question. I rebooted the xen server (the > shutdown part took abnormally long) and afterwards the domains came up again.For the long shutdown part, try looking at /etc/syconfig/xendomains, look for XENDOMAINS_SAVE. I''m guessing your system tries to save domUs state (which can take some time) instead of shutting it down, but failed doing so (probably due to not enough space). -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Saturday 13 June 2009, Fajar A. Nugraha wrote:> On Sat, Jun 13, 2009 at 9:28 PM, Geert Janssens<info@kobaltwit.be> wrote: > > Hmm, you can probably ignore my question. I rebooted the xen server (the > > shutdown part took abnormally long) and afterwards the domains came up > > again. > > For the long shutdown part, try looking at /etc/syconfig/xendomains, > look for XENDOMAINS_SAVE. I''m guessing your system tries to save domUs > state (which can take some time) instead of shutting it down, but > failed doing so (probably due to not enough space).I think you''re dead-on. My /var partition was almost full and XENDOMAINS_SAVE pointed at /var/lib/xen/save. Thanks, I learned something new from it ! Geert -- Kobalt W.I.T. Web & Information Technology Brusselsesteenweg 152 1850 Grimbergen Tel : +32 479 339 655 Email: info@kobaltwit.be _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users