From: "Ing. Ricardo Brisighelli" <ricardo@estilo.com.ar>
To: xen-devel@lists.xen.org
Subject: [xl restore and migrating problem - hardware compatibility]
Date: Fri, 23 Dec 2016 13:32:19 -0300 [thread overview]
Message-ID: <4469172.Oblta71HDi@rick> (raw)
Hi, i'm gentoo user and try with xen 4.6.3 and 4.7.1 in both version have the
same problem.
My cpu is AMD A10-7860K
I run VM as PVlinux, then try migrate to other server (same hardware) and dont
work, same occurs when try restore a saved VM, but this works well (migrate
and restore) if run VM as HVM.
I try same instalation in cpu Intel I7-4790 and ir works well VM as PVlinux
and HVM
Hardware Problem
#cat /proc/cpuinfo (only last core)
proprocessor : 3
vendor_id : AuthenticAMD
cpu family : 21
model : 56
model name : AMD A10-7860K Radeon R7, 12 Compute Cores 4C+8G
stepping : 1
microcode : 0x6003106
cpu MHz : 3591.088
cache size : 2048 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 0
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu de tsc msr pae mce cx8 apic mca cmov pat clflush mmx
fxsr sse sse2 ht syscall nx mmxext fxsr_opt l
m constant_tsc rep_good nopl nonstop_tsc extd_apicid eagerfpu pni pclmulqdq
ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsav
e avx f16c hypervisor lahf_lm cmp_legacy extapic cr8_legacy abm sse4a
misalignsse 3dnowprefetch xop fma4 tce tbm perfctr
_core perfctr_nb bpext arat cpb hw_pstate vmmcall fsgsbase bmi1 xsaveopt
bugs : fxsave_leak
bogomips : 7182.17
TLB size : 1536 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro [13]
Migration problem:
#xl migrate fs dstdomain
migration target: Ready to receive domain.
Saving to migration stream new xl format (info 0x3/0x0/1307)
Loading new save file <incoming migration stream> (new xl fmt info
0x3/0x0/1307)
Savefile contains xl domain config in JSON format
Parsing config from <saved>
xc: info: Saving domain 5, type x86 PV
xc: info: Found x86 PV domain from Xen 4.6
xc: info: Restoring domain
xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal error
xc: error: Restore failed (0 = Success): Internal error
libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done: restoring
domain: Success
libxl: error: libxl_create.c:1144:domcreate_rebuild_done: cannot (re-)build
domain: -3
libxl: error: libxl.c:1610:libxl__destroy_domid: non-existant domain 1
libxl: error: libxl.c:1568:domain_destroy_callback: unable to destroy guest
with domid 1
libxl: error: libxl.c:1495:domain_destroy_cb: destruction of domain 1 failed
migration target: Domain creation failed (code -3).
libxl: error: libxl_utils.c:430:libxl_read_exactly: file/stream truncated
reading ready message from migration receiver
stream
libxl: info: libxl_exec.c:118:libxl_report_child_exitstatus: migration
transport process [4250] exited with error status
3
Migration failed, resuming at sender.
Save and restore problem:
#xl save fs fs.snap
Saving to fs.snap new xl format (info 0x3/0x0/1307)
xc: info: Saving domain 5, type x86 PV
xc: Frames: 131072/131072 100%
xc: End of stream: 0/0 0%
#xl restore fs.snap
Loading new save file fs.snap (new xl fmt info 0x3/0x0/1307)
Savefile contains xl domain config in JSON format
Parsing config from <saved>
xc: info: Found x86 PV domain from Xen 4.6
xc: info: Restoring domain
xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal error
xc: error: Restore failed (0 = Success): Internal error
libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done: restoring
domain: Success
libxl: error: libxl_create.c:1144:domcreate_rebuild_done: cannot (re-)build
domain: -3
libxl: error: libxl.c:1610:libxl__destroy_domid: non-existant domain 6
libxl: error: libxl.c:1568:domain_destroy_callback: unable to destroy guest
with domid 6
libxl: error: libxl.c:1495:domain_destroy_cb: destruction of domain 6 failed
#verify-stream-v2 -v -f xl -i fs.snap
Processed xl header
Libxl Header: little endian
Libxl Record: Libxc context, length 0
Libxc Image Header: little endian
Domain Header: x86 PV from Xen 4.6
Libxc Record: x86 PV info, length 8
64bit guest, 4 levels of pagetables
Libxc Record: x86 PV P2M frames, length 2056
Start pfn 0x0, End 0x1ffff
Squashed 128 Page Data records together
Libxc Record: TSC info, length 24
Mode 0, 3591089 kHz, 1189155414000 ns, incarnation 1
Libxc Record: Shared info, length 4096
Libxc Record: x86 PV vcpu basic, length 5176
vcpu0 basic context, 5168 bytes
Libxc Record: x86 PV vcpu extended, length 64
vcpu0 extended context, 56 bytes
Libxc Record: x86 PV vcpu xsave, length 856
vcpu0 xsave context, 848 bytes
Libxc Record: x86 PV vcpu msrs, length 8
Stream Error:
Traceback (most recent call last):
File "/usr/libexec/xen/bin/verify-stream-v2", line 82, in read_stream
VerifyLibxl(info, stream_read).verify()
File "/usr/lib64/python2.7/site-packages/xen/migration/libxl.py", line 82, in
verify
while self.verify_record() != REC_TYPE_end:
File "/usr/lib64/python2.7/site-packages/xen/migration/libxl.py", line 136,
in verify_record
record_verifiers[rtype](self, content[:length])
File "/usr/lib64/python2.7/site-packages/xen/migration/libxl.py", line 155,
in verify_record_libxc_context
VerifyLibxc(self.info, self.read).verify()
File "/usr/lib64/python2.7/site-packages/xen/migration/libxc.py", line 132,
in verify
while self.verify_record() != REC_TYPE_end:
File "/usr/lib64/python2.7/site-packages/xen/migration/libxc.py", line 227,
in verify_record
record_verifiers[rtype](self, content[:length])
File "/usr/lib64/python2.7/site-packages/xen/migration/libxc.py", line 429,
in <lambda>
VerifyLibxc.verify_record_x86_pv_vcpu_generic(s, x, "msrs"),
File "/usr/lib64/python2.7/site-packages/xen/migration/libxc.py", line 323,
in verify_record_x86_pv_vcpu_generic
" bytes long" % (name, minsz))
RecordError: X86_PV_VCPU_msrs record length must be at least 8 bytes long
Hardware works correcltly
#cat /proc/cpuinfo (last core)
Processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
stepping : 3
microcode : 0x1c
cpu MHz : 3600.098
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu de tsc msr pae mce cx8 apic sep mca cmov pat clflush
acpi mmx fxsr sse sse2 ss ht syscall nx lm co
nstant_tsc arch_perfmon rep_good nopl nonstop_tsc eagerfpu pni pclmulqdq
monitor est ssse3 sdbg fma cx16 sse4_1 sse4_2 m
ovbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm
abm ida arat pln pts dtherm fsgsbase bmi1 av
x2 bmi2 erms xsaveopt
bugs :
bogomips : 7200.19
clflush size : 64
Regards.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-12-23 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 16:32 Ing. Ricardo Brisighelli [this message]
2016-12-23 17:00 ` [xl restore and migrating problem - hardware compatibility] Andrew Cooper
2016-12-23 17:16 ` Andrew Cooper
2016-12-23 22:56 ` Ing. Ricardo Brisighelli
2016-12-23 23:22 ` Andrew Cooper
2016-12-24 13:24 ` Ing. Ricardo Brisighelli
2016-12-26 20:43 ` Doug Goldstein
2016-12-28 14:50 ` Julien Grall
2017-01-04 11:00 ` Wei Liu
2016-12-28 14:58 ` Julien Grall
2016-12-28 15:00 ` Processed: " xen
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=4469172.Oblta71HDi@rick \
--to=ricardo@estilo.com.ar \
--cc=xen-devel@lists.xen.org \
/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.