and use it in memory hotplug and config_to_cmd
Signed-off-by: Alexandre Derumier aderum...@odiso.com
---
PVE/QemuServer.pm | 77 ++---
1 file changed, 38 insertions(+), 39 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index
code factorization
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
I really don't known why we always add a vmbr0 on reading
etc/network/interfaces.
Maybe user want to not use vmbr0 at all, and also in GUI we need to remove it,
if we want to create
an OVS vmbr0
___
pve-devel mailing list
pve-devel@pve.proxmox.com
Currently it's impossible to remove vmbr0 from network gui,
if we really want to remove it, or replace it with an OVS vmbr0
Signed-off-by: Alexandre Derumier aderum...@odiso.com
---
data/PVE/INotify.pm |6 --
1 file changed, 6 deletions(-)
diff --git a/data/PVE/INotify.pm
Am 07.02.2015 um 15:55 schrieb Dietmar Maurer:
THis won't help as my build and your build will differ. SO the kernel
message a have from the crash will not be applyable with gdb to my debug
symbols.
Sure, you also need to reproduce the bug :-( I guess we should really provide
a
debug
applied, thanks!
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel