Merge lp://qastaging/~terceiro/lava-project/kvm-further-networking-optimization into lp://qastaging/lava-project
Proposed by
Antonio Terceiro
| Status: | Merged |
|---|---|
| Merged at revision: | 61 |
| Proposed branch: | lp://qastaging/~terceiro/lava-project/kvm-further-networking-optimization |
| Merge into: | lp://qastaging/lava-project |
| Diff against target: |
41 lines (+32/-0) 1 file modified
doc/kvm-deploy.rst (+32/-0) |
| To merge this branch: | bzr merge lp://qastaging/~terceiro/lava-project/kvm-further-networking-optimization |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Linaro Validation Team | Pending | ||
|
Review via email:
|
|||
Description of the change
document extra optimization for kvm networking setup
To post a comment you must log in.
Revision history for this message
| Matthew Hart (matthew-hart) wrote | # |
Revision history for this message
| Antonio Terceiro (terceiro) wrote | # |
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
I've been playing around with the KVM image and I noticed that by default it was setup to use NAT networking (assigned a 10.X address) and this would mean it is not visible by other devices on the internal network.
Does using this bridge setup solve this problem?