Recent content by ispirto

Virtuozzo 7 has a way to run interactive shell for qemu guests referenced at https://docs.openvz.org/openvz_command_line_reference.webhelp/_prlctl_enter.html It requires only the qemu guest agent installed on the guest. So I believe they have somehow wrapped an interactive shell around the...

Thank you. Sorry for the wrong wording. I know you guys aren't using libvirt. I meant if it'd be possible to implement such as feature like virsh console. The Serial Terminal is good but it requires login credentials. Is there a way to bypass that using a method like that tty autologin...

I was wondering if it'd be possible for you guys to add support for virsh console for Proxmox. Such as: http://erikimh.com/virtualization-kvm-equivalent-to-vzctl-enter-in-openvz/

Thank you. Unfortunately, the kernel provided by PVE 4.4 is causing CPU soft lockups and therefore I had to use a newer kernel. I was wondering what could be the reason of this. Every backup taken on the new kernel has this problem.

New findings: The file size of the backup taken on the 4.4.40-1pve is the same as the backup taken on 4.9.0-0.bpo.1-amd64. So I think the file is not actually corrupt. I've compiled the pve-qemu-kvm after commenting out checksum check and the other 2 checks after that and then extracted the...

So I've found the reason why the taken backups are showing this error. I've switched using the Jessie Backports kernel: 4.9.0-0.bpo.1-amd64 I've found out that backups taken under that kernel are showing this error. When I take the backup using the latest PVE kernel, they work fine. To sum...

We have been backing up 5 host nodes including several VMs to a NFS storage. We have tested restoring backups around 2 weeks ago and we didn't have any issues with it. However, when we needed to restore a VM from backups today, we have found out that all the backups taken on all 5 different...

New findings: - This only happens when the guest has more than one Virtual CPU. - Only happens on resets/reboots, if the guest is powered off then powered back on, it boots normally. - The issue goes away when I disable ACPI on the guest. It looks like somewhat related...

Started to see this on first boots time to time. Not sure if this is related to the kernel: smpboot: CPU1: Not responding smpboot: do_boot_cpu failed(1) to wakeup CPU#1

I think I did but it didn't help. What I ran was: ethtool -K eth5 rx off ethtool -K eth5 tx off ethtool -K eth5 sg off ethtool -K eth5 tso off ethtool -K eth5 ufo off ethtool -K eth5 gso off ethtool -K eth5 gro off ethtool -K eth5 lro off ethtool -K eth5 rxvlan off ethtool -K eth5 txvlan off...

Hello, We are seeing the following warning messages a few times a minute while a VM is doing multiple hundred mbits of download per second. I'm not sure if this is bridge related or the NIC related. Any insight? [7960695.303208] WARNING: CPU: 1 PID: 9426 at net/core/dev.c:2422...

Installing irqbalance and that new kernel solved it for me for now.

I've found this README file regarding the PVE kernel development: https://git.proxmox.com/?p=pve-kernel.git;a=blob_plain;f=README;hb=HEAD I'm not sure if it's the latest one but it doesn't sound like it's the latest one. Do you know where I can find the updated README on how you make your...

Thank you Thomas. I'm running the non rt version of the kernel now (4.9.0-0.bpo.1-amd64) and testing it. I don't use ZFS and this kernel doesn't have the realtime patch. So I guess the only visible risk is that it's not tested with the PVE. Am I correct? Are there any patches made by Proxmox...

Thanks a lot Thomas. I'm not sure how I missed the "rt" there in the name. I've rebooted it with the 4.9.0-0.bpo.1-amd64 and am testing it now.