I see, deactivate_volumes() is called in vm_stop_cleanup or
migrate/phase3_cleanup().
I think i get the problem.
When the vm fails to start, the cleanup is missing.
The remaining devices are there because i had errors at first (TASK
ERROR: minimum memory must be 1024MB.)
QemuServer.pm
Hello,
Yes, I rebooted the entire host server because in the updates where
included a new kernel.
The problem arises after the upgrade and host server reboot. And it is
not inmediatly after the virtual machines boot, it has happen after
several hours of normal operation and the two virtual
Hello,
I have just licensed and upgraded a promox server to the last version
3.4-3. Before the upgrade I has the version 3.1.
A few hours after upgrade, I have had problems with two different
virtual machines, one with Windows and the other one with Linux. The
virtual machines have been stopped
More info about the problem ...
It seems that the virtual machines lost access to its disks, because
there are no logs in the /var/log/syslog file since the problem until de
hard reboot.
The two virtual machines use qcow2 virtual disks.
¿Should I do something in the virtual disks after the
On Tue, 05 May 2015 18:50:42 +0200
[SOLTECSIS] Carles Xavier Munyoz Baldó car...@unlimitedmail.org
wrote:
A few hours after upgrade, I have had problems with two different
virtual machines, one with Windows and the other one with Linux. The
virtual machines have been stopped working. I have
I think i get the problem.
When the vm fails to start, the cleanup is missing.
The remaining devices are there because i had errors at first (TASK
ERROR: minimum memory must be 1024MB.)
QemuServer.pm
4166 PVE::Storage::activate_volumes($storecfg, $vollist);
4167
SAN / LVM shared storage.
But i thought it was more related to device mapper or udev ?
Multipath isn't aware of what's inside pvs or vgs.
root@proxmoxt9:/usr/share/perl5/PVE/Storage# multipath -ll
VSCVNX4_T_proxmox_2 (3600014400010202fb54185fd9298) dm-4 EMC,Invista
size=2.0T features='1
Hello!
We updated an older install of proxmox over the weekend from 3.1 up to
3.4. A VM that we have that uses a couple of USB devices (following this
documentation: https://pve.proxmox.com/wiki/USB_physical_port_mapping) will
no longer startup. When we try to start this VM with the USB
On May 5, 2015 at 9:47 AM Dhaussy Alexandre adhau...@voyages-sncf.com wrote:
SAN / LVM shared storage.
But i thought it was more related to device mapper or udev ?
Multipath isn't aware of what's inside pvs or vgs.
But we deactivate lv's when we migrate a VM, so I have no real idea
