VM start issues
- Thread starter Juliano Silva
- Start date
Yes,
can you indicate a company that help me with this problem? I have 200 sites in VM are offline ..
I pay for the support
can you indicate a company that help me with this problem? I have 200 sites in VM are offline ..
I pay for the support
Hi,
what has changed, that the VMs have boot-problems?
How looks the VM-config?
Which pve-version do you use?
Any messages, if you start the VM from the console?
Have you look with "systemctl status ..." like discribed in the VM-console?
What OS (version) run inside the VMs?
Udo
what has changed, that the VMs have boot-problems?
How looks the VM-config?
Code:
cat /etc/pve/qemu-server/VMID.conf
Code:
pveversion -v
Code:
qm start VMIDWhat OS (version) run inside the VMs?
Udo
root@s115341:/# cat /etc/pve/qemu-server/106.conf
boot: cda
bootdisk: sata0
cores: 6
cpu: kvm64
cpulimit: 0
cpuunits: 370
memory: 8096
name: srv.xxxxxxxxx.com.br
net0: e1000=C2:5A:69
F:4C:7D,bridge=vmbr1
numa: 0
onboot: 1
sata0: local:106/vm-106-disk-1.qcow2,cache=writeback,size=550G
smbios1: uuid=38c2752e-82e8-46ad-92f0-6cb9cdd0c3ce
root@s115341:/# pveversion -v
proxmox-ve: 4.4-95 (running kernel: 4.4.79-1-pve)
pve-manager: 4.4-18 (running version: 4.4-18/ef2610e8)
pve-kernel-4.4.79-1-pve: 4.4.79-95
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-52
qemu-server: 4.0-112
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-101
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
fence-agents-pve: 4.0.20-1
root@s115341:/# qm start 106
VM 106 already running
What OS (version) run inside the VMs?
CentOS
[root@srv ~]# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
boot: cda
bootdisk: sata0
cores: 6
cpu: kvm64
cpulimit: 0
cpuunits: 370
memory: 8096
name: srv.xxxxxxxxx.com.br
net0: e1000=C2:5A:69
F:4C:7D,bridge=vmbr1numa: 0
onboot: 1
sata0: local:106/vm-106-disk-1.qcow2,cache=writeback,size=550G
smbios1: uuid=38c2752e-82e8-46ad-92f0-6cb9cdd0c3ce
root@s115341:/# pveversion -v
proxmox-ve: 4.4-95 (running kernel: 4.4.79-1-pve)
pve-manager: 4.4-18 (running version: 4.4-18/ef2610e8)
pve-kernel-4.4.79-1-pve: 4.4.79-95
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-52
qemu-server: 4.0-112
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-101
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
fence-agents-pve: 4.0.20-1
root@s115341:/# qm start 106
VM 106 already running
What OS (version) run inside the VMs?
CentOS
[root@srv ~]# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
Hi,root@s115341:/# cat /etc/pve/qemu-server/106.conf
boot: cda
bootdisk: sata0
cores: 6
cpu: kvm64
cpulimit: 0
cpuunits: 370
memory: 8096
name: srv.xxxxxxxxx.com.br
net0: e1000=C2:5A:69
numa: 0
onboot: 1
sata0: local:106/vm-106-disk-1.qcow2,cache=writeback,size=550G
smbios1: uuid=38c2752e-82e8-46ad-92f0-6cb9cdd0c3ce
the memory is strange and any reason, why you use sata? (but I don't think this is the reason for the non-booting)
are the cpuunits right?
I would try following config - save the original before, like "cp -p /etc/pve/qemu-server/106.conf /root/106.conf"
Code:
boot: cda
bootdisk: virtio0
cores: 6
cpu: kvm64
memory: 8192
name: srv.xxxxxxxxx.com.br
net0: virtio=C2:5A:69:DF:4C:7D,bridge=vmbr1
numa: 1
onboot: 1
virtio0: local:106/vm-106-disk-1.qcow2,cache=writeback,size=550G
smbios1: uuid=38c2752e-82e8-46ad-92f0-6cb9cdd0c3cedo an
Code:
apt update
apt dist-upgradeYou must stop VM 106 before you can start the VM on the console again.
I'm not an redhat/centos specialist...
Udo
Hi.
vm-106-disk-1.qcow2 is an hdd-container, like an normal hdd with partitiontable and different partitions (depends on content) in an qcow2-format.
Filesystem-check can be done from inside the VM - connect an live-cd to the VM (like grml), use this as boot-disk and boot the live-cd.
From the live-cd you can do an filesystem-check.
Anyway - what is about output of the questions?
Udo
Yes VM is not starting I had problems why VM was shut down forced why server crashed ..
see image below VM error
https://forum.proxmox.com/attachments/capturar-jpg.6009/
see image below VM error
https://forum.proxmox.com/attachments/capturar-jpg.6009/
Hi,
again - boot an live-cd distro.
Or try boot in single user mode: https://www.tecmint.com/boot-into-single-user-mode-in-centos-7/
But you should know what to do to repair the system. Because there are no info about an corrupt filesystem. Looks more like network trouble.
Is vmbr1 functional?
Udo
I think your VPS provider is having network related issues. I can't even ping srv.iwebhosting.com.br, or https://solusvm.iwebhosting.com.br. Even nameservers are not responding: ns1.iwebhosting.com.br
Last edited:
Doubt
boot an live-cd distro, am I going to lose information that are inside my VPS? I have 80 sites
boot an live-cd distro, am I going to lose information that are inside my VPS? I have 80 sites
Hi,
depends, what you are doing... if you take a look to find the issue you loose nothing.
If you remove content or reformat an filesystem you can loose a lot.
A. you should know what you are doing.
B. you should have an valid backup.
Udo
Hi,
what does that mean? Reset/shutdown of VM or the whole server?
Have you tried to check the qemu-file (with switched off VM 106)?
Code:
qemu-img check /var/lib/vz/images/106/vm-106-disk-1.qcow2