Search results

Naja, die hwaddress Zeile stand seit mind. 3 reboots drin, der letzte edit war über die UI, da wurde aber nur ein comment gesetzt bei vmbr0. Meine Vermutung bzgl. Netzwerk kam (auch) daher, dass der Kunde ohne mein Wissen (und leider auch ohne grundlegende Kenntnisse der Netzwerktechnik im...

interfaces hat sich nur durch die Zeile hwaddress xx:xx:xx:xx:xx unterschieden. Die Option ist bei mir auf fast allen Maschinen die ich über 6.1 bis 7 hochgezogen habe drin gewesen und hat nie Probleme bereitet. Beim Reboot ist die Maschine anscheinend ohne NW hochgekommen und hat angefangen...

Leider existiert das alles nicht mehr, da ich nicht mehr in der Lage war, irgendetwas an der OS Platte zu machen, oder von dort logs zu sichern. Zum Glück waren die VM Disks auf anderen Platten gesichert, die ich durch ausbauen und späteres neu einlesen weiterverwenden konnte. Die pve...

Letztens ist beim neu laden der Netzwerk-Konfiguration ein Fehler aufgetreten, konkret wurde der Parameter "hwaddress" in /etc/network/interfaces als falsch moniert und die NW Konfiguration nicht geladen. Der Parameter ist aber seit mindestens einem Reboot drin. Da ich remote drauf war - so wie...

That's the plan, Pinky... ;)

D'accord, but consider this: the majority of admins using PBS are well versed in supporting multiple OSes and have to support them on a daily basis. Having an agent for Windows Server, without any drapings like M$SQL, EXCH etc., just an agent to backup the server from within, would be a huge...

Is it a matter of money? If so I think we could find enough people to financially support the development of such a thing.

After creating the vms anew with q35 and importing the vmdks via qm importdisk the win servers came up quite nicely. installing the virtio ver 1.0.28 helped also.

Hi, I'm having much the same issue. While installing fresh Win10Pro of various Builds works fine, also the migration of linux based VMs from VMWare, the migration of existing Win2k16 servers does not. The servers report the ethernet adapter as working with the newest drivers, but the network...

I found the reason: the machines could only resolve the fqdn not the short name. Adding them to the DNS everything works fine, even over subnet limits...

Sorry for the delay... the replacement took 2 months to arrive. The cloning of the disk failed (or I made some error). I took the coward's way and added the new hardware as a separate machine to the cluster, moved the vms and decommissioned the old hardware. It was the easiest way...

Thanks, I will live test this as soon as the replacement hardware is here.... (most probably around next wednesday) I'll keep you posted.

Is there a way to replace a node (still running, but ready to die) within a cluster with new hardware and retain the id and position in the cluster? Thanks in advance for any ideas.

I do have the same issue as theleeski. Under 5.x it worked like a charm for more than a year, after the update the system gets woozy after a few days. Unfortunately the Tandberg is builtin, so booting disconnected is not an option, disabeling the device neither. When there is no casette in the...

Update: even without the RDX the status changes to "unknown" out of the blue. messages show Dec 5 20:33:19 denobula kernel: [ 60.158232] hrtimer: interrupt took 6474 ns Dec 5 20:34:32 denobula kernel: [ 133.137384] perf: interrupt took too long (2507 > 2500), lowering...

I did find something similar: when inserting a RDX cassette, with e.g. 4TB, the os starts scanning the device, reports it (correctly) and about 10 mins later the node is unavailable, its vms show "state unknown". Mind, the RDX is not mounted. When rebooting with inserted RDX, the boot process...

Any idea yet? I do have the same problem. In a 3 node cluster, I normally log on to the first server and do my work from there. Starting a SPICE session for a VM on this node works pretty well, trying to start a session for a VM residing on a nother node via the first server ends with an http...

Update: Simply removing the /etc/fstab entry solved the problem. After that I manually changed the entries in /etc/pve/qemu-server/<ID>.conf from <PATH>:<ID>/<VM-DISK> to <LVMTHIN>:<VM-DISK> and restored the machines from the previous backup. All works as expected, after the reboot the host...

Fürs erste sieht es aus, als wäre das Problem behoben. Am WE werden wir die Maschinen wie geplant migrieren, dann werden wir ja sehen ob das des Pudels Kern war...

Gerade neu gestartet, gleiches Ergebnis: proxmox-ve: 6.0-2 (running kernel: 5.0.21-2-pve) apt update Hit:1 http://ftp.at.debian.org/debian buster InRelease Hit:3 http://ftp.at.debian.org/debian buster-updates InRelease Hit:2 http://security-cdn.debian.org buster/updates InRelease Hit:4...