Search results

thats most likely a matter of technical complexity to implement such. it's much easier to add a switch like the existing

Prolian DL100 G2 ? ( https://en.wikipedia.org/wiki/ProLiant ) that should have maximum 4gb ram and that should be ok for proxmox ( Minimum 2 GB for the OS and Proxmox VE services, plus designated memory for guests should be valid for for proxmox 6/7 and 8) i bet you get that for free from...

>I cant upgrade to proxmox 6 because my servers are old . And they can't run proxmox 6 can you explain why they can't run proxmox 6 ? you can even run proxmox 8.1 without problems on hardware more then 10 years old.

> Contabo VDS proxmox is not meant to run in virtual environment. you should be able to use it with lxc , but with hypervisor stacked on each other, i guess problems like this should be to expected

> Contabo Proxmox VDS runs on bare metal. how can a proxmox virtual dedicated server with 4 Epyc cores run on bare metal ? btw, i don't see that they offer proxmox with this, can you provide a link @ksceniev ?

there is a update script for manual update of drivedb # update-smart-drivedb /var/lib/smartmontools/drivedb/drivedb.h updated from branches/RELEASE_7_2_DRIVEDB ( https://svn.code.sf.net/p/smartmontools/code/branches/RELEASE_7_2_DRIVEDB/smartmontools/ )

what's the effect of this bug? does it cause data corruption?

https://pve.proxmox.com/wiki/WLAN Wi-Fi adapters can only be used as Linux bridge interface through workarounds, as most Access Points (APs) will reject frames that have a source address that didn’t authenticate with the AP.

that seems to make sense, i don't see the point why btrfs should consider a 100gb virtual disk file to be stored uncompressed because it's first blocks are badly compressible. if there is compression active, people will excpect that it's stored compressed. would you like to file a bugzilla...

what disk type/model is this ?

thank you, trying to repeat this in my own words: when proxmox code invokes qemu binary, qemu simply interprets the string before "+" ( here: "pc", which is pc-i440fx-7.2 on pve 7.4) and ignores the pve0 substring (+ used as divider), whereas proxmox server code interprets the latter ony and...

i have a question regarding pve qemu machine type in process list (ps -ef), kvm / qemu-system-x86_64 binary is using : "-machine type=pc+pve0" when doing a query on the supportet machine types, pc+pve0 is not listed what does pc+pve0 mean and/or where is it defined ? from...

did anybody see this issue with some linux based guest OS ? i did open an upstream issue report for this in the meantime. and i can also reproduce i xfce4 gui https://gitlab.com/qemu-project/qemu/-/issues/2067

https://gitlab.com/qemu-project/qemu/-/issues/1731

>Anybody else using all-SSD for this much space? What kind of disks? we don't want ssd, we want faster/optimized verify and optimized access to datastore first ;) https://bugzilla.proxmox.com/show_bug.cgi?id=5035 https://bugzilla.proxmox.com/show_bug.cgi?id=3752

i'm happy if proxmox will not hire a 100 new devs and support engineers because somebody getting dollar signs in his eyes or because vmware customers being frigthened and desperatly seeking for replacement and getting pushy because of this. imho, that would be the same stupid greediness...

try with nomodeset as a kernel param at boot

bugs in changed block tracking are real, and history is even repeating (cbt is the vsphere equivalent of qemu block/dirty bitmap) https://kb.vmware.com/s/article/95940 https://kb.vmware.com/s/article/2136854 https://kb.vmware.com/s/article/2090639 there is a reason why veeam has that feature...

this is really good news

so i guess this can be closed ? https://bugzilla.proxmox.com/show_bug.cgi?id=4953