Recent content by bensode

  1. B

    QEMU-Guest Fails to install

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

    ProxMox Installing Without Boot Device?

    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.
  3. B

    QEMU-Guest Fails to install

    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.
  4. B

    QEMU-Guest Fails to install

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

    QEMU-Guest Fails to install

    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...
  6. B

    QEMU-Guest Fails to install

    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...
  7. B

    QEMU-Guest Fails to install

    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...
  8. B

    [SOLVED] [Warning] Latest Patch just broke all my WINDOWS vms. (6.3-4) [Patch Inside] (See #53)

    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...
  9. B

    No CDROM Found

    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...
  10. B

    Adding node crashes cluster

    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?
  11. B

    Adding node crashes cluster

    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...
  12. B

    Storage Idea

    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...
  13. B

    Moving Backups between storage

    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...
  14. B

    [SOLVED] Faster way to stop/out/destroy OSDs?

    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...
  15. B

    [SOLVED] Faster way to stop/out/destroy OSDs?

    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...


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!