Search results

Thank you for this will give it a shot if it happens again.

I've run into this with SuperMicro where Legacy BIOS and UEFI OS are not enabled as a boot option by default within the BIOS. i've often found that after BIOS updates they will sometimes reset these UEFI boot options again.

We are still unable to get the installation of any version of the qemu-agent nor the virtio package at any version on several VMs.

Several times ... same issue and identical log entries.

I think we have a disconnect with the issue. The problem isn't an inability to attach the ISO -- the problem is that when we attach and run through the installation, it fails at the guest-agent. If we attempt to install the guest-agent directly, it also fails. I provided the screen caps as...

Yes have seen [0] and [1]. agent: 1 balloon: 0 bootdisk: scsi0 cores: 4 cpu: host hotplug: disk,network,memory,cpu ide2: none,media=cdrom memory: 24576 name: PRDSQL1B net0: virtio=06:F0:FD:18:85:C0,bridge=vmbr0,tag=172 numa: 1 ostype: win8 scsi0: PRDPOOL01:vm-501-disk-0,discard=on,size=80G...

Good afternoon. I have a couple of servers that the QEMU-Guest agent fails to install from the virtio-1.190 release. If I attempt to install it from the guest-agent subdirectory I get "QEMU guest agent" window with message "There is a problem with this Windows Installer package. A program run...

Just wanted to add a "me too". Already triggered and found out late Friday afternoon and had scrambled to correct the NICS and remove the ghost missing nics. Another side effect is that some servers are not able to install the latest qemu-guest-agent in Windows. The MSI complains there was a...

Hello again friends. It's a Supermicro server with S2600GZ board and current BIOS/IPMI firmware. Followed the Wiki on installing from USB. Have downloaded 6.0.1 three different times and installed elsewhere with all three so the ISO is good. I have tried with a USB stick created with etcher...

I'd like to add that it displays in the GUI but not in the node list. How can I remove the node properly now to rebuild it?

Proxmox 6.0-7 5 nodes. When I added the 6th node the entire cluster goes down, gui becomes unresponsive on all nodes and unable to log into the newly added node at all from UI. Shelled into each of the nodes and run pvecm status with this result. I've restarted corosync on each nodes and...

I'm not familiar with current Dell gear but couldn't an option be two compute nodes, two data store nodes and use an aggressive VM replication schedule? This is assuming you could get enough storage out of two 1U servers and essentially mirror. Not true HA by any means ... but CEPH has a bit...

I guess that would depend what type of storage is used for backup store. I've used CIFS shares for backups and moved them for restore testing to another cluster without any issue. Just make sure that the permissions are good I suppose unless someone can think of anything else for other storage...

Think I found my answer ... ceph osd purge osd.270 --yes-i-really-mean-it ran and removed it from the display. Please let me know if this is not a good way to handle mass removal of OSDs or if there is a preferred method - be it GUI one at a time or otherwise. Thanks! ceph osd out osd.XXX...

Good morning. In playing with Proxmox v6 I added 100 OSDs in an integrated ceph deployment that I'd like to remove and redeploy differently. I can run systemctl stop ceph-osd@270 ceph-osd@269 ... etc to stop them all and can also run ceph osd out osd.270 osd.269 ... etc to mark them as out...

Wow ... I totally glossed over that! The new method is much simpler thanks!

Hi guys I notice that OSD encryption is available under create OSD. Is there any mechanism to show which OSDs are encrypted in the UI or command line? I made some encrypted and some non-encrypted to gauge performance but unable to differentiate which are which.

That wiki should be updated to reflect that at least for v6.0.5. I ran into the same issue that the wiki suggests to only remove pve-ssl.pem and pve-ssl.key but removing the pveproxy-ssl.* files did the trick!

Thank you! restarting corosync brought up 2 of the three hosts back into the cluster and gave quorum. I'm able to move guests disks out of the ceph cluster and backup guests while we troubleshoot the hardware issue on the third node.

We seemed to have lost quorom on all three nodes running 6.0.5 overnight! The guests are running, ceph storage is available but now each node thinks the other two are offline. I'm unable to move guests, backup, restore or make config changes because I get permission denied. How can I rescue...