|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 1775] distro package of xen-4.1 breaks system on botting a vm
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1775 ------- Comment #10 from johneed@xxxxxxxxxxx 2011-07-31 08:49 ------- ok; to correct last entries. It seems that flask is fine. On repeating it a number of times, for whatever reason, on compiling the xensource package xen-4.1-testing.hg, it appears that entries flask and acm will in fact compile fine. It seems that setting flask on its own will fail, it depends upon xsm being set. Setting xsm om its own or with flask works. In fact, setting all 3, the package builds. But like the gentoo emerge, the hypervisor breaks the system if ACM_SECURITY is set. Setting use=ACM presumably leads to setting ACM_SECURITY ?= n in the Config.mk. simple. So the flaw isn't in gentoo, it' in the source. Like most everyone else in gentooland, we don't know ACM. ok so you don't know about flask, the question now is do you know about ACM. Know here is an unexpected little extra. After pointing out happily setting dom0=<1500MB> in the previous bug worked, it has now stopped working. On booting, gentoo64 grub # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 7473 4 r----- 117.6 centos5.com 1 512 2 -b---- 0.5 ... ... ... The kernel arg is being ignored it seems. xm mem-set will adjust it ok, but it's not doing what it's told. Foer fear of 'polluting' this one, shall I file a new one for this? It's clearly a trivial flaw. Essentially a workaround to the essence of the bug is to exclude ACM. Can it be resolved?? -- 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
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |