yes, this is the log from the node which restarted. I just finished reading the doc and have realized what happened. I tried to migrate in online mode one of the vm and then I got error similar to which I have described in other post...
Hello,
When I try to start VM i get following errors :
WARNING: Not using device /dev/mapper/proxmox_data for PV 45obR9-bE57-FB8s-lA4w-mqiZ-H0aS-JlcCMY.
WARNING: Not using device /dev/mapper/proxmox_test for PV SWZ5CD-10AY-ZGYE-Qete-XU7i-sg77-Jj2Zeq.
WARNING: Not using device...
I have three node cluster and one of the node just restarted. I tried to look something interesting in logs but couldn't find anything beside this:
what does it mean? why one of the node restarted?
Aug 26 21:40:16 proxmox-prod-2 systemd[1]: Started User Manager for UID 0.
Aug 26 21:40:16...
On the first pve node I have 384GB with 9 VMs. Total RAM assigned for those machines is 153GB but in node summary I can see RAM usage 70.03 (264.54 GiB of 377.77 GiB)
all of the VMs (Windows) have virtio/balloon/qemu-agent installed.
So why there is so high consumption?
Ok, it's solved
what I did was:
- exported vm from vmware one more time
- imported vm to proxmox
- disconnect network card from vm
- followed http://woshub.com/remove-hidden-ghost-network-adapter-windows/ to uninstall hidden vmware network card
- configured new network interface
- followed...
sorry for digging out thread from 2012 but it happened to me as well with proxmox 6.3-3.
I have SCSI array, created LVM on top of the LUN. Multipath is configured. LVM is enabled as a shared storage.
What could be the issue of it?
I've successfully migrated Windows 2012 R2 from vmware to proxmox, installed all necessary drivers to get QEMU, VirtIO SCSI. After log in from console I've configured new network interface with the same IP/DNS/gateway as from vmware. There was some information about deleting old configuration so...
I have installed two nodes of PVE 6.3 in VMware workstation and what I noticed "online migration" is available even when there is no shared storage. As far as I remember shared storage is required to do that. So how does it work here?
Below configuration didn't work for me.
What I wanted to achieve was set up management ip on vmbr0, so I could access GUI through 10.162.242.85. After the reboot, when I wanted to ping gateway I got network unreachable.
Where is the problem?
auto lo
iface lo inet loopback
iface eno1 inet...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.