Bug 9372 - xen kernel config
Summary: xen kernel config
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-13 23:44 CET by AL13N
Modified: 2013-04-10 00:15 CEST (History)
3 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description AL13N 2013-03-13 23:44:57 CET 
# CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not set

==> should be set, or memory resizing from hypervisor will not work

and

(unsure)

CONFIG_XEN_XENBUS_FRONTEND=y

can this be 'm'? i think xenbus needs to be loaded after other modules are loaded so that it can trigger them (or something)

during boot, right not XENBUS just has the effect that is says: 2 devices without drivers... i suppose the xenbus in kernel can't really trigger netfront or blkfront, if those are modules...

Reproducible: 

Steps to Reproduce:
AL13N 2013-03-13 23:45:25 CET

Priority: Normal => release_blocker
CC: (none) => alien, tmb

Comment 1 AL13N 2013-03-26 22:50:45 CET 
ping @thomas

i just would like your opinion on this
Thierry Vignaud 2013-03-30 23:01:44 CET

CC: (none) => thierry.vignaud
Assignee: bugsquad => tmb

Comment 2 AL13N 2013-04-10 00:15:08 CEST 
the whole thing with xenbus is not so easy and might need some upstream work. skipping this one for now

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX
Note You need to log in before you can comment on or make changes to this bug.