Non-xen machines are reported as being xen VMs
Bug #921970 reported by
Björn Tillenius
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
Medium
|
Thomas Herve | ||
landscape-client (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Both my oneiric and precise machines are being reported as being xen VMs. Looking closer at the detection code, it checks for the presence of /sys/bus/xen, which does indeed exist. It seems like we have to look at what's inside that directory. On my real machines, /sys/bus/
Canonistack instances also seem to be wrongly reported as xen vms, when they should be kvm ones.
Lucid doesn't seem to be affected. I haven't check what happens for natty.
Related branches
lp:~therve/landscape-client/fix-xen-report
- Alberto Donato (community): Approve
- Björn Tillenius (community): Approve
-
Diff: 81 lines (+37/-4)2 files modifiedlandscape/lib/tests/test_vm_info.py (+30/-3)
landscape/lib/vm_info.py (+7/-1)
Changed in landscape-client: | |
milestone: | none → backlog |
Changed in landscape-client: | |
importance: | Undecided → Medium |
Changed in landscape-client: | |
milestone: | backlog → 12.01.2 |
assignee: | nobody → Thomas Herve (therve) |
Changed in landscape-client: | |
status: | Confirmed → Fix Committed |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
My bare metal client is also recognized as "xen", and does not seem to send hardware information to Landscape server.
$ tree /sys/bus/xen/
/sys/bus/xen/
├── devices
├── drivers
├── drivers_autoprobe
├── drivers_probe
└── uevent