Search results

Hi, ich hab keine Ahnung von Ceph. Aber das sieht doch sehr nach einem Fehler aus der mit Ceph zu tun hat. Hast du also mal die Ceph Versionen und die Ceph Konfiguration der beiden Nodes verglichen? Wenn ich diese Fehlermeldung in eine Suchmaschine einhacke dann kommen zu Hauf irgendwelche...

Guten Tag Zusammen, ich habe vor kurzem die Einstellung bei allen meinen Windows Gästen geändert. Jetzt laufen alle mit SCSI Controller VirtIO SCSI und die Festplatten logischerweise an scsi0 mit der Option discard.Auf allen VMs sind die aktuellen Spice-Tools mit dem Qemu Agent installiert...

I think you have to restart spiceproxy as well. Maybe pve-manager, too.

Steht direkt unter den diversen Subskription-Modellen :)

Already read this. Hope the patch will be merged in the enterprise repository soon :) Thank you very much Dominik.

Yep downgrade to virt-viewer 6.0 on windows or just do a dnf downgrade spice-glib virt-viewer on fedora 28 will bring back a working version. Some users on the Red Hat Bugtracker guess that this issue is related to changes happened between the version 0.34 and 0.35 of spice-glib. They switched...

I can confirm this for latest Fedora 28 virt-viewer and latest Windows virt-viewer build (7.0). I will submit this in the bug ticket. I read that downgrading on Fedora 28 works. Maybe on SUSE, too. Working versions in Fedora: spice-glib 0.34-4.fc28 spice-gtk3 0.34-4.fc28 virt-viewer 6.0-3.fc28

The certificate of your proxy nas.ub.ac.id:444 is not trusted. Thats you problem. Don't use a proxy or check why the proxy certificate is untrusted.

you have to say what the problem is. "trouble" is not a good problem description.

Please take a look at man page for qemu-img. qemu-img check /path/to/your/disk.qcow2 There are some more options. Just review the manual page for this tool.

Can you boot in normal mode? Not rescue! but with kvm console? it this possible?

Hi Dominik, thank you for your assistance. With this i found out wahts the problem. I don't know exactly how i could happened but on the first cluster a command "hostname 213.XXX.XXX.XXX" was entered. The hostname from the first node changed to the IP-Adress 213..... and the confiusion has...

Now i see a third node in my three bar. The one with the "213". I dont know how this happened.

Hi Guys, i habe a crazy issue. I can't control my cluster nodes and vms. I can login into the proxmox ve webinterface on any node. The nodes shown as green. Cluster shown as OK (green). But i can't start a VM. In my "Tasks" list i can see that the "Node" entry switches from the node names to a...

You can unmount the data Volume Mount it to a temporary location like /mnt Copy data from root Volume to data Volume then unmount in /mnt and mount data Volume back to /var/lib/vz

Did you used ZFS maybe? I don't know in which case this meta data volume will be created. But searched a bit and every time i found this volume i see something with ZFS was in use. Maybe you can do the file command on the meta colume, too. If it is not be in use i think you can remove this volume.

Hi Dominik, thank you very much. I applied the patch on my node and it works very well. Hope a offical solution will come in stable updates soon.

Sorry. Yes i mean /dev/pve/data. Ok looks for me like your filesystem table isn't there. Have you already data on this logical volume? If not then just reformat it.

Whats the type of the filesystem of the data logical volume? Post output of file -sL /etc/pve/data please. Do you get any error message while trying to mount the volume?

I liked the patch from 2016 which enables to open console with just a doubleclick on the VM in the tree bar. Finally i updated my Setup from 4.4 release to 5.2, some days ago. On 4.4 the doubleclick console was the same like the one when clicking on the dedicated console button. Now on 5.2 the...