Search results

Woah! I didn't realise Kernelcare supported Proxmox. That's good to know. We use it for Virtuozzo. But I don't understand what's happening here. The 2000 load - was that something that co-incidentally happened, causing you to want to reboot and then happen to see this lvm-thin issue, or was the...

Hello François. The disk subsystem is key, just as LnxBil says. I am new to Proxmox, but not new to virtualisation. We use it for web hosting, where there is constant disk I/O (sooooo many log files being written all at once, so many emails being read and written, so many website files being...

Thank you. That's exactly what I needed to understand. Much appreciated.

I have found that creating a Snapshot of a VM with a qcow2 disk can corrupt the filesystem when the VM is doing heavy disk writes. It works fine when there are no disk writes. The error is repeatable and not a one-off. Although I have no intention of using qcow2 in production, the idea that...

Please can someone explain the difference between performing a VM Snapshot (Node>[VMID]>Snapshots) and using snapshot mode when creating a backup of a VM (Node>[VMID]>Backups > Create backup [and select Snapshot as backup mode])? I realise they are "different things" but no amount of Googling...

Is this using xterm.js? I have not been able to re-create my problem on real hardware since my original tests as long as I stick to xterm.js for the console. I have since moved on to testing fstrim and discard, and now backups and Snapshots, but I will return to this shortly. I will also see...

Please can someone give me an indication of the best action to take in the event that a node in a cluster is lost (say total failure - all hard disk lost), and is then replaced? In my case I would have no ceph and so no replication. Just two or three nodes in a cluster, each with only a local...

Well, I'm getting completely different result when I use real hardware again. I'm very confused. xterm seems to see all the console messages perfectly fine. I will continue to investigate what was going wrong originally. For now, all seems well.

I have not had any issued adding keys to /root/.ssh/authorized_keys Keep in mind, however, that this file will be synchronised across your Cluster. This is what we want, but may not be what you want.

In my testing, I've been having great success using Cloud-Init with Centos 7 VMs. I have essentially followed the instructions here https://pve.proxmox.com/wiki/Cloud-Init_Support but used used the "Generic Cloud" Centos 7 image from here...

How are you using the Community Edition please? What I mean is, are you running it within a VM, or are you running it on the PM server itself, or.....

Cloud it be a temperature issue? The "no fans running" -- has this happened every time? Because that's more than a crash. I would expect fans to only shut down if the system board lost power, or thought it was shutdown.

If you can't leave it blank, use the authoritative DNS server for your domain. As for the network issues, I normally use ping. ping secure.debian.org Then I use dig. dig debian.org dig secure.debian.org And check the results. I would see the nameservers associated with the domain and so on...

You would normally leave it blank. The Search Domain is what's used when your VM tries to look up something that is not a full domain name. e.g. if you enter "ping blah", "blah" is not a full domain, and there is no way to work out what you meant. If you have a corporate network, you can use...

Further to this, I tried creating the cloud-init image on interface scsi1 rather than ide2 and it was still treated as a CD-ROM image. Obviously this is due to the way cloud-init generates images. I thought it might be a function of the interface, but I was incorrect.

I'm having a similar issue. In my case it is local storage, not shared. But the result is the same, although with less detail: # qm migrate 223 pm2 --online --with-local-disks 2018-08-04 11:06:33 starting migration of VM 223 to node 'pm2' (192.168.1.230) 2018-08-04 11:06:33 found local disk...

ext4/LVM. It seems that zfs on top of HW RAID is not at all recommended or maybe doesn't even work, because it needs direct access to the physical disks.

As a total Proxmox newbie, I've taken the decision to stick to the hardware RAID controller, despite the disadvantages of not being able to use ZFS and therefore replication, which I really, really wanted. So if you do end up with hardware RAID, you won't be alone. Your choice to use RAID 5 on...

OK. So a reference or pointer to the data is created. But when the source Template is removed, something more must happen. Something must say "ah, there is a reference to this data, so we must preserve it and change the references". Is this some built-in feature of LVM? I would like to...

Thanks Alwin. OK, so I'm not going mad. This is good. But how does this work please? What magic happens in the background? It takes 2 seconds to create the linked clone, but many minutes to create a full clone, so there is obviously a difference on creation.