Yes, I did (always try to follow upgrade instructions as carefully as I can, studying especially the "known issues" section), just before making the switch to 6. But I did not reboot, after doing an apt-get dist-upgrade on 5.4... Perhaps that was why the issue appeared to be after upgrading to 6?
That's a bit strange because I ran pve5to6 and did not report any issue like that at all. Even at the end of the procedure, it only produced a single warning stating that I should reboot the system for the changes to take effect.
On the same boat, updating a 3.x-updated-to-5.x installation and the same error message pops up. Unfortunately, there was no mention of this in https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
Would you be kind enough to instruct how to do this?
EDIT: The following did it:
pvecm...
Thanks for the response, unfortunately the mikrotik VM hides its Linux shell. Instead it provides a RouterOS command line interface.
As for the Mikrotik OS, I do not know it as well, but I hoped that taking a look at https://wiki.mikrotik.com/wiki/Manual:CHR#KVM could be easily understood by...
qemu agent was enabled from proxmox gui. However:
qemu agent 106 ping
fails with a "QEMU agent is not running message".
I can't really understand what should be setup, from what I've read so far the CHR VM has qemu enabled as per the mikrotik wiki here...
I've been running a Mikrotik CHR VM version 6.41.2 for some time now, only for the record of using the embedded TheDude network monitoring package. Since I've been having problems with shutting the VM down before taking a backup from PVE, I've been searching for a way to notify the VM. This was...
First you have to properly add a second disk from within proxmox. Problem is that the CHR VM is a bit picky about which disk controller to use. You can either use an ide disk, or use LVM. If you do use LVM, in options select to use the VMware PVSCSI as the SCSI controller. IIRC, I could not use...
I've succesfully transferred Windows Server 2000-2003 systems in the past, that did not utilize UEFI for boot. Cloned them with VMWare vconverter standalone, transfer the vmdk resulting content to my PVE LVM-based storage and presto.
Now, I'm facing a similar scenario, in which I've been given...
Hello,
I've got a ready-to-use CentOS 7-based virtual appliance originally made for vmware and wanted to use it on PVE. It was quite easy to do so, just unpack the OVA, get the vmware disk images and dd them to my LVM partition, prepare a PVE guest for CentOS and then connect the LVM-based...
I'll give it a try. However, do you have any idea why the issue with my pvscsi config might occur? Could I do some troubleshooting to help you debug this?
The Linux distro is TheDude which unfortunately refused to boot with its disk boot image set to something other than either IDE or PVSCSI. The bottom line is that I might be able to resolve the problem described in this thread by moving to Virtio scsi for the new disk, but I intended to clone...
The PVE systems will be fresh installations, on low-grade/cheap server hardware (ie no RAID 10 and such). Also the VM on each PVE box will be rather small, less than 250Gb per virtual disk (and even less for data). Does pve now ask how it should set up base storage on installation? BCPs for...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.