[PVE-User] Moving disk to a new storage - VM Reboot
Alexandre DERUMIER
aderumier at odiso.com
Tue Jul 5 17:46:19 CEST 2016
Is the migration task log finished correctly ?
----- Mail original -----
De: "Kevin Lemonnier" <lemonnierk at ulrar.net>
À: "proxmoxve" <pve-user at pve.proxmox.com>
Envoyé: Mardi 5 Juillet 2016 14:11:14
Objet: Re: [PVE-User] Moving disk to a new storage - VM Reboot
proxmox-ve: 4.2-56 (running kernel: 4.4.13-1-pve)
pve-manager: 4.2-15 (running version: 4.2-15/6669ad2c)
pve-kernel-4.4.13-1-pve: 4.4.13-56
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-42
qemu-server: 4.0-83
pve-firmware: 1.1-8
libpve-common-perl: 4.0-70
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-55
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-19
pve-container: 1.0-70
pve-firewall: 2.0-29
pve-ha-manager: 1.0-32
ksm-control-daemon: 1.2-1
glusterfs-client: 3.7.12-1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
I'll add that it's been doing that for a while on multiple installations,
so if it's a bug in a version it's been there for months. It just always
did this since I started using Proxmox.
On Tue, Jul 05, 2016 at 02:04:31PM +0200, Alexandre DERUMIER wrote:
> They are no reason for qemu process to be killed when storage migration occur.
>
> Could be a qemu crash, but I never had seeing this.
>
> What is the qemu version ?
>
>
>
> ----- Mail original -----
> De: "Kevin Lemonnier" <lemonnierk at ulrar.net>
> À: "proxmoxve" <pve-user at pve.proxmox.com>
> Envoyé: Lundi 4 Juillet 2016 16:51:36
> Objet: Re: [PVE-User] Moving disk to a new storage - VM Reboot
>
> I think the VM is not even rebooting, it looks like it just shuts down
> then the HA boots it. Unfortunatly it's not a clean shut down, it just stops
> right away as if the process was killed or something.
>
> The images are all qcows, no snapshots, most of them with no cache but some
> configured in directsync mode, doesn't seem to affect the result. Almost everytime
> it stops then reboots, but once or twice I've seen a move complete without a reboot.
>
> And if that matters the VMs are all Linux (Debian 8) with no agent installed. I can
> install the agent if that helps though.
>
>
> On Mon, Jul 04, 2016 at 05:46:45PM +0300, Markos Vakondios wrote:
> > Alexandre,
> >
> > I think Kevin means that the VM (windows?) auto reboots itself sometimes
> > after live migration without knowing what triggers the reboot, correct?
> >
> > What type of disk file do you use Kevin, raw/qcow2 and what disk cache
> > mode? Also, are there any VM snapshots on the migrated VMs?
> >
> > On 4 July 2016 at 17:06, Kevin Lemonnier <lemonnierk at ulrar.net> wrote:
> >
> > > Hi,
> > >
> > > I don't know if I had an error, it just reboots the VM without saying
> > > anything.
> > > But the VM reboots perfectly fine on the new storage.
> > >
> > > I'm migrating VMs to and from glusterfs to NFS or local storage, sometimes
> > > to other
> > > GlusterFS. The storage doesn't seem to matter, although I never tried
> > > local to local.
> > >
> > > On Mon, Jul 04, 2016 at 03:59:42PM +0200, Alexandre DERUMIER wrote:
> > > > Hi,
> > > >
> > > > I have migrate storage of around 300vms recently (windows/linux), and I
> > > didn't have any disk error.
> > > > This was from nfs to ceph rbd.
> > > >
> > > > what was your source/destintion storage and vm configuration
> > > > ----- Mail original -----
> > > > De: "Kevin Lemonnier" <lemonnierk at ulrar.net>
> > > > À: "proxmoxve" <pve-user at pve.proxmox.com>
> > > > Envoyé: Lundi 4 Juillet 2016 14:40:57
> > > > Objet: [PVE-User] Moving disk to a new storage - VM Reboot
> > > >
> > > > Hi,
> > > >
> > > > I've been doing a lot of moving disks around on different storage for
> > > running VMs
> > > > lately, and it works fine but I noticed that sometimes the VM doesn't
> > > reboot after
> > > > moving the disk, and most of the times in does (no warning by the way,
> > > corrupted a few
> > > > MySQL that way, would be nice to add one).
> > > >
> > > > Anyone knows what are the conditions for a VM to really migrate "live"
> > > to a new storage,
> > > > and what conditions will make it reboot after the move ? Would be
> > > interested in preventing
> > > > any kind of reboots like that, it's not great having to tell the client
> > > "it might reboot,
> > > > not sure".
> > > >
> > > > Thanks !
> > > >
> > > > --
> > > > Kevin Lemonnier
> > > > PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
> > > >
> > > > _______________________________________________
> > > > pve-user mailing list
> > > > pve-user at pve.proxmox.com
> > > > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> > > >
> > > > _______________________________________________
> > > > pve-user mailing list
> > > > pve-user at pve.proxmox.com
> > > > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> > >
> > > --
> > > Kevin Lemonnier
> > > PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
> > >
> > > _______________________________________________
> > > pve-user mailing list
> > > pve-user at pve.proxmox.com
> > > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> > >
> > >
> > _______________________________________________
> > pve-user mailing list
> > pve-user at pve.proxmox.com
> > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
> --
> Kevin Lemonnier
> PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
--
Kevin Lemonnier
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
_______________________________________________
pve-user mailing list
pve-user at pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
More information about the pve-user
mailing list