I believe that xen has memory bug with qemu upstream. When i assign more than 3.5 GB of ram I get an error message that system cant read boot disk. host : localhost release : 3.9.5-1-xen version : #1 SMP Sat Jun 8 21:26:23 MDT 2013 machine : x86_64 nr_cpus : 8 max_cpu_id : 7 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 1995 hw_caps : bfebfbff:20100800:00000000:00000900:0004e33d:00000000:00000001:00000000 virt_caps : hvm total_memory : 16383 free_memory : 933 sharing_freed_memory : 0 sharing_used_memory : 0 outstanding_claims : 0 free_cpus : 0 xen_major : 4 xen_minor : 3 xen_extra : -unstable xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Wed Jun 12 17:27:08 2013 +0200 git:fd0b066-dirty xen_commandline : dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all elevator=noop cc_compiler : gcc (GCC) 4.8.1 cc_compile_by : root cc_compile_domain : hebe.us cc_compile_date : Thu Jun 13 11:44:39 MDT 2013 xend_config_format : 4 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Thanks for the report. In fact this issue is being discussed on Xen-devel. Jacek (and for anyone who''s interested): look for [BUG 1747]Guest could''t find bootable device with memory more than 3600M on Xen-devel archive. Wei. On Sat, Jun 15, 2013 at 07:01:38PM -0600, jacek burghardt wrote:> I believe that xen has memory bug with qemu upstream. When i assign more > than 3.5 GB of ram I get an error message that system cant read boot disk. > host : localhost > release : 3.9.5-1-xen > version : #1 SMP Sat Jun 8 21:26:23 MDT 2013 > machine : x86_64 > nr_cpus : 8 > max_cpu_id : 7 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 1995 > hw_caps : > bfebfbff:20100800:00000000:00000900:0004e33d:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 16383 > free_memory : 933 > sharing_freed_memory : 0 > sharing_used_memory : 0 > outstanding_claims : 0 > free_cpus : 0 > xen_major : 4 > xen_minor : 3 > xen_extra : -unstable > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : Wed Jun 12 17:27:08 2013 +0200 git:fd0b066-dirty > xen_commandline : dom0_mem=1024M,max:1024M loglvl=all > guest_loglvl=all elevator=noop > cc_compiler : gcc (GCC) 4.8.1 > cc_compile_by : root > cc_compile_domain : hebe.us > cc_compile_date : Thu Jun 13 11:44:39 MDT 2013 > xend_config_format : 4> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
I also would like to add that with latest changes hvm will not boot at all. I don''t why some arm related changes break hvm. So I had compiled latest unstable 4.3 and now hvm will start to boot and die. On Sun, Jun 16, 2013 at 4:00 AM, Wei Liu <wei.liu2@citrix.com> wrote:> Thanks for the report. > > In fact this issue is being discussed on Xen-devel. > > Jacek (and for anyone who''s interested): look for > > [BUG 1747]Guest could''t find bootable device with memory more than 3600M > > on Xen-devel archive. > > > Wei. > > On Sat, Jun 15, 2013 at 07:01:38PM -0600, jacek burghardt wrote: > > I believe that xen has memory bug with qemu upstream. When i assign more > > than 3.5 GB of ram I get an error message that system cant read boot > disk. > > host : localhost > > release : 3.9.5-1-xen > > version : #1 SMP Sat Jun 8 21:26:23 MDT 2013 > > machine : x86_64 > > nr_cpus : 8 > > max_cpu_id : 7 > > nr_nodes : 1 > > cores_per_socket : 4 > > threads_per_core : 1 > > cpu_mhz : 1995 > > hw_caps : > > bfebfbff:20100800:00000000:00000900:0004e33d:00000000:00000001:00000000 > > virt_caps : hvm > > total_memory : 16383 > > free_memory : 933 > > sharing_freed_memory : 0 > > sharing_used_memory : 0 > > outstanding_claims : 0 > > free_cpus : 0 > > xen_major : 4 > > xen_minor : 3 > > xen_extra : -unstable > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > xen_scheduler : credit > > xen_pagesize : 4096 > > platform_params : virt_start=0xffff800000000000 > > xen_changeset : Wed Jun 12 17:27:08 2013 +0200 git:fd0b066-dirty > > xen_commandline : dom0_mem=1024M,max:1024M loglvl=all > > guest_loglvl=all elevator=noop > > cc_compiler : gcc (GCC) 4.8.1 > > cc_compile_by : root > > cc_compile_domain : hebe.us > > cc_compile_date : Thu Jun 13 11:44:39 MDT 2013 > > xend_config_format : 4 > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Sun, Jun 16, 2013 at 06:23:13AM -0600, jacek burghardt wrote:> I also would like to add that with latest changes hvm will not boot at all. > I don''t why some arm related changes break hvm. > So I had compiled latest unstable 4.3 and now hvm will start to boot and > die. >Did you do any bisection to pin down the problematic changeset? git bisect is you friend. :-) Wei.
Well I have build xen on 13th and that works fine except for memory bug and 15th build fails to start. On Sun, Jun 16, 2013 at 6:29 AM, Wei Liu <wei.liu2@citrix.com> wrote:> On Sun, Jun 16, 2013 at 06:23:13AM -0600, jacek burghardt wrote: > > I also would like to add that with latest changes hvm will not boot at > all. > > I don''t why some arm related changes break hvm. > > So I had compiled latest unstable 4.3 and now hvm will start to boot and > > die. > > > > Did you do any bisection to pin down the problematic changeset? > > git bisect is you friend. :-) > > > Wei. >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Sun, Jun 16, 2013 at 06:43:08AM -0600, jacek burghardt wrote:> Well I have build xen on 13th and that works fine except for memory bug and > 15th build fails to start. >I presume you''re using the staging branch, because the latest commit on master is on 13th, which means there''s nothing new between 13th and 15th and Xen should not break. Well there''s lots of stuffs went in between 13th and 15th. Most notable changes are Ian Jackson''s XSA fix. After they pass OSS tests they will be pushed to mater. So my advice would be, use the master branch instead of the staging branch... Wei.