Search results

Still no closer to a solve on my end.. Anyone out there who might have found a solution ti this behaviour ?

Sorry to (re-)activate this thread, but i am also facing this issue. As to the above provided solution i am a bit cautioned by introducing wildcards. My situation : - LXC console (across the cluster) works fine. - VM console only works when i am on the GUI of the node the VM is on. -...

Tonight it even got more weird ... the VM was shutdown after it was touched by the backup-job : INFO: VM Name: vm-lx-01 INFO: include disk 'scsi0' 'vms01:125/vm-125-disk-0.qcow2' 64G INFO: include disk 'scsi1' 'vms01:125/vm-125-disk-1.qcow2' 64G INFO: backup mode: snapshot INFO: ionice priority...

Well unfortunately no change in the issue, so reinstalling the agent did not solve it :( Below is a screenie of the agent's consumption of resourses on the VM

FYI: As far as i have been able to determine it was due to a/the qemu agent just sucking up all runtime.... So as a measure i have re-installed the agent forcefully with : zypper in -f qemu-guest-agent Need to determine if this solves anything, but hey, its atleast an action aimed at the...

Extra info, this is not a 'Pure SLES box, its an Open Enterprise Server: vm-lx-01:~ # cat /etc/novell-release Open Enterprise Server 2018 (x86_64) VERSION = 2018.2 PATCHLEVEL = 2

Additional info on the VM ( logged from an SSH-session i still had running : Message from syslogd@vm-lx-01 at Nov 28 03:11:29 ... kernel:[39135.014041] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [sshd:25223] Message from syslogd@vm-lx-01 at Nov 28 03:11:29 ...

i have pfSense (as hardware box / DL360Gen7) router that handles internet ( my ISP router is configured in bridging mode) , so no issues there/ everything is under my control. Next to that i am running split-DNS with own dns server(s) on the inside as VM's

i migrated to RHEL 8 - with a free developer license

In my world Servers should never be submitted to the perils of a DHCP server. - Servers should not receive an IP thru DHCP (even with reservations), but rather set in stone via manual config. As DHCP relies on external availabillity ( and possible set Reservations) you are introducing an...

In you using an USB drive to install i am assuming you have not licensed the iLo functionality to mount an ISO remotely to the server ? I in my situation have licensed them, and always use the iLo way of mounting ISO's remote to a/the server for use (and the remote console) of installing server.

From 192.168.1.150 icmp_seq=1 Destination Host Unreachable Looks more as next to you having a DNS problem you are also facing a routing issue .. gateway correct ?

I had issues with a DL380 Gen5 where it (when installing Debian ( i prefer to have control over how my disk-layout is done) and then moving from Debian to Proxmox as described on the PM Wiki) due to missing drivers. I then found a debian BootISO which already had those missing drivers in them...

I have the strangest thing with just -one- of my VM's where when its being backed up it times out : INFO: Starting Backup of VM 125 (qemu) INFO: Backup started at 2021-11-26 03:12:21 INFO: status = running INFO: VM Name: vm-lx-01 INFO: include disk 'scsi0' 'vms01:125/vm-125-disk-0.qcow2' 64G...

Still suffering from a Timing-issue that when i reboot a node it hangs after shutting down all VM's/Containers. From the cluster-perspective this is quite unwanted. At the moment i just hard-reboot the node from iLO ( HP's solution on servers to manage them from remote via a management board)...

Just an update from my end, it seems the location (since a bit ( now running 7.0.14 PVE) ) of the unitfile has changed, and introduced some issues so i had to adapt my Ansible playbook. --- # ./roles/proxmox/tasks/main.yml - name: remove mcp repository to reset content ansible.builtin.file...

So what do logs say when you mount this dir ? (IMHO) Mounts are OS issues, so before PRoxmox can use them they need to be available on the underlying OS, if that fails then the cause needs to be first sought in the logs from the OS.

just my 5 cents, but .. If a scheduelled power-outage were there, would a scheduelled cronjob on the Proxmox host be equally efficient, without poking around with the API ? - if the scheduelled outage is always the same, then use a cronjob to shutdown the hosts/guests prior to the outage...

What i am curious is the following - as information provided is like at an absolute minimum.... - Why do you want to automate a full install of a Proxmox server ? => (in my opinion) the times you (re-)install a server is like not a day-2-day task If you were running a cluster then sometimes...

I install manually up untill i have network and can login over SSH , then Ansible takes over and configures the rest of the box.