proxmox-mirrors/qemu-server
1
0
Fork 0
mirror of https://git.proxmox.com/git/qemu-server synced 2025-05-29 18:34:50 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

destroy_vm: use write_config from our Config module to set an "empty" config

Browse Source 
brings us more in line with what we do in pve-container, also it's
good to not use file_set_contents directly if we have all those nice
wrapper interface methods to do things in a safe and guaranteed way.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2019-10-18 11:21:58 +02:00
parent 5172770df7
commit 3361d09901
1 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
PVE/QemuServer.pm
View File

@ -2619,8 +2619,6 @@ sub touch_config {
sub destroy_vm { sub destroy_vm {
my ($storecfg, $vmid, $keep_empty_config, $skiplock) = @_; my ($storecfg, $vmid, $keep_empty_config, $skiplock) = @_;
my $conffile = PVE::QemuConfig->config_file($vmid);
my $conf = PVE::QemuConfig->load_config($vmid); my $conf = PVE::QemuConfig->load_config($vmid);
PVE::QemuConfig->check_lock($conf) if !$skiplock; PVE::QemuConfig->check_lock($conf) if !$skiplock;
@ -2663,7 +2661,7 @@ sub destroy_vm {
}); });
if ($keep_empty_config) { if ($keep_empty_config) {
PVE::Tools::file_set_contents($conffile, "memory: 128\n"); PVE::QemuConfig->write_config($vmid, "memory: 128\n");
} else { } else {
PVE::QemuConfig->destroy_config($vmid); PVE::QemuConfig->destroy_config($vmid);
} }