[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-bugs] [Bug 1043] migration of x86_32p domU from x86_64 dom0 into x86_32p dom0 not working



http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1043


michal@xxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




------- Comment #2 from michal@xxxxxxxxx  2007-08-15 10:47 -------
(In reply to comment #1)

> [Actually, its the dom0 version which is important rather than the hypervisor
> version. You can probably live relo between an all-32b host and a 64b host
> running 64b xen and a 32b dom0. Running a 32b dom0 on a 64b hypervisor is
> actually a pretty smart thing to do anyhow as it tends to give slightly beter
> performance.]

now that's the smart idea. having some ready 64bit xen-3.1 binaries, i've tried
it, worked. well, almost. now i have 64b xen, 32b dom0, 32b userland of course.
and - two questions are comming with it:

1. how do i compile xen 64b on 32b system? XEN_TARGET_ARCH=x86_64 fails while
compilling.

2. after booting 32b dom0 under a 64b xen i can see 'total memory -757870',
'free_memory 0' in xm info. (with dom0_mem=512M, and totaly 3 GB of ram in this
machine, what xen itself can see -> xm dmesg shows it).

so now way i can boot any kind of domU.

now what about it?

btw - 32b xen 32 bit dom0 -> same amount of memory, below zero.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.