On Wed, 2006-07-05 at 09:48 -0600, Alex Williamson wrote:
> On Tue, 2006-07-04 at 14:33 +0200, Tristan Gingold wrote:
> > Le Mardi 04 Juillet 2006 09:22, Tristan Gingold a écrit :
> > > Hi Alex,
> > >
> > > have you any problems to integrate this patch ? Did you miss it ?
> > > I'd like to finish the save & restore work.
> > >
> > > Tristan.
> > Here is the updated version of the patch (it applies cleanly to tip).
> > Tested by booting domU and domVti.
>
> Thanks for the resend. Applied.
Tristan,
I'm having some problems with this patch when I sync with
xen-unstable.hg. The system is an 8-way, UP dom0 w/ dom0_mem=2048M.
When I try to boot a domU (UP, mem=1024M), I get this:
p
### domain f000000007c78080: rid=80000-c0000 mp_rid=2000
(XEN) arch_domain_create: domain=f000000007c78080
(XEN) DomainU EFI build up: ACPI 2.0=0xda8
(XEN) domain mem: type= 0, attr=0x0000000000000000,
range=[0x0000000000000000-0x0000000000000000) (0MB)
(XEN) domain mem: type= 9, attr=0x8000000000000008,
range=[0x0000000000000000-0x0000000000004000) (0MB)
(XEN) domain mem: type=13, attr=0x8000000000000008,
range=[0x0000000000100000-0x0000000000200000) (1MB)
(XEN) domain mem: type= 7, attr=0x0000000000000008,
range=[0x0000000000200000-0x000000003fff4000) (1021MB)
(XEN) domain mem: type=12, attr=0x0000000000000001,
range=[0x00000ffffc000000-0x00000ffffffff000) (63MB)
Unexpected error: xmlrpclib.ProtocolError
Please report to xen-devel@xxxxxxxxxxxxxxxxxxx
Traceback (most recent call last):
File "/usr/sbin/xm", line 10, in ?
main.main(sys.argv)
File "//usr/lib/python/xen/xm/main.py", line 1192, in main
rc = cmd(args)
File "<string>", line 1, in <lambda>
File "//usr/lib/python/xen/xm/main.py", line 582, in xm_subcommand
cmd.main([command] + args)
File "//usr/lib/python/xen/xm/create.py", line 1000, in main
dom = make_domain(opts, config)
File "//usr/lib/python/xen/xm/create.py", line 921, in make_domain
raise ex
xmlrpclib.ProtocolError: <ProtocolError for /RPC2: -1 >
/var/log/xend-debug.log shows this:
*** glibc detected *** double free or corruption (out): 0x60000000001aad70 ***
/var/log/xend.log looks pretty normal except for this:
[2006-07-05 19:36:44 xend 2169] DEBUG (image:177) dom = 1
[2006-07-05 19:36:44 xend 2169] DEBUG (image:178) image =
/opt/xen/vmlinux
[2006-07-05 19:36:44 xend 2169] DEBUG (image:179) store_evtchn = 1
[2006-07-05 19:36:44 xend 2169] DEBUG (image:180) console_evtchn = 2
[2006-07-05 19:36:44 xend 2169] DEBUG (image:181) cmdline =
root=/dev/hda1 ro console=tty1 single
[2006-07-05 19:36:44 xend 2169] DEBUG (image:182) ramdisk =
[2006-07-05 19:36:44 xend 2169] DEBUG (image:183) vcpus = 1
[2006-07-05 19:36:44 xend 2169] DEBUG (image:184) features =
[2006-07-05 19:36:44 xend 2167] CRITICAL (SrvDaemon:195) Xend died due to
signal 6! Restarting it.
^^^^^^^^
[2006-07-05 19:36:44 xend 2294] INFO (SrvDaemon:283) Xend Daemon started
[2006-07-05 19:36:44 xend 2294] INFO (SrvDaemon:287) Xend changeset: Wed Jul 05
11:56:18 2006 -0600 10660:c7b2f31e10c9.
Current xen-ia64-unstable (cset 10573) works fine. Current xen-unstable
works fine. Xen-ia64-unstable merged with xen-unstable fails booting
domU as above (domVTI works fine). If I revert xen-ia64-unstable cset
10570 the merge tree works. Could you take a look? I've exported my
merge tree here:
http://free.linux.hp.com/~awilliam/20060705-sync/
Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home