XEN_BALLOON and XEN_SAVE_RESUME do not work for older xen hypervisors (older than xen 3.1)
Bug #345490 reported by
Chuck Short
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
These features are not available for ec2.
summary: |
- Please disable XEN_BALLOON and XEN_SAVE_RESUME for ec2 + XEN_BALLOON and XEN_SAVE_RESUME for older xen clients (older than xen + 3.1) |
summary: |
- XEN_BALLOON and XEN_SAVE_RESUME for older xen clients (older than xen - 3.1) + XEN_BALLOON and XEN_SAVE_RESUME for older xen clients do not work for + older xen hypervisors (older than xen 3.1) |
summary: |
- XEN_BALLOON and XEN_SAVE_RESUME for older xen clients do not work for - older xen hypervisors (older than xen 3.1) + XEN_BALLOON and XEN_SAVE_RESUME do not work for older xen hypervisors + (older than xen 3.1) |
Changed in linux (Ubuntu): | |
assignee: | nobody → timg-tpi |
importance: | Undecided → High |
milestone: | none → ubuntu-9.04-beta |
status: | New → In Progress |
To post a comment you must log in.
An example of this is
xen-3.0.3 hypervisor hardy dom0 and a jaunty domU. It might cause the kernel to oops in unforseen ways if users try to use this option.