Search results

Hi Folks! I'm just actually checking out the qemu-guest-agent for Linux stuff, and I noticed a few areas of the documentation that would benefit from clarity. I'm referring to : https://pve.proxmox.com/wiki/Qemu-guest-agent My thoughts: The page should mention the VM needs to be turned off...

Okay but I don't care about containers. This topic is about VM import/export.

Thanks for the info! I'll have to see how well it works out for me ;)

Uhhh actually there's plenty of "appliance" VMs out there that can be imported easily into things like virtual box and other common hypervisors. So while there may be examples of failures of that, there are plenty of examples of sucesses too. Having this functionality (in some form) would help...

Could we get the roadmap page to better spell out what the advantages of the new elements in 5.0 are? When "Debian Stretch" or Linux Kernel 4.10 are mentioned, I don't see how that impacts me since I don't really have the time to spend a side by side comparison between my Proxmox 4.4 setup, and...

I would really like to see Proxmox with VM Import/Export features. It would be nice to have support for various different VM packages so I can export product VMs to my clients, or import VM packages between other environments I work with. Also when making a new VM it would be nice to have the...

I configured grub to only boot a specific version of the Linux kernel, as newer versions (at the time) were causing instability in a few of my VMs. Fortunately this had been solved since then. I am not entirely sure what solved it, but I am no longer "pinning" my Linux kernel version.

I actually haven't seen this problem in a long time. I did a major version for Proxmox VE upgrade a few months ago, and undid the kernel version pinning I was doing. I haven't seen the issue at all! I'm on "Virtual Environment 4.4-13/7ea56165" and haven't seen stability issues at all! I have...

Last I checked it never updated, even after a minute.

This is a small GUI bug, and so far I've seen it happen in the Datacenter scope, but I'm not sure if it happens elsewhere. I right click on a VM that's off. It turns on, and works, just like one would expect. I stay in this scope, don't reload page, or whatever. The VM is on, but I right click...

Ahh I didn't mean to make a big deal out of it, sorry. I just thought it was a little curious is all :P

lol I got an alert that Vito Reiter posted in here telling me to not run FreeNAS in a VM, and now the post is gone? perhaps they saw that I'm doing this for labbing purposes? :P

I'm watching DMESG and the FreeNAS GUI. I'm confident this is not an issue on their end. When I attach a disk to the VM DMESG does not output any new entries. When using bare metal it would.

So.... any idea what I can do? Or?

Oops, forgot to mention, also: proxmox-ve: 4.4-80 (running kernel: 4.4.40-1-pve) pve-manager: 4.4-12 (running version: 4.4-12/e71b7a74) pve-kernel-4.4.35-1-pve: 4.4.35-77 pve-kernel-4.2.6-1-pve: 4.2.6-36 pve-kernel-4.4.35-2-pve: 4.4.35-79 pve-kernel-4.4.21-1-pve: 4.4.21-71...

Top of the page right now says "Virtual Environment 4.4-12/e71b7a74" as of this very second. Should be new enough?

Okay I spun up a new VM with FreeNAS 10-beta, which is IIRC based on FreeBSD 10.3. I attached the disks in the same way, trying SCSI/VirtIO, and neither one is detected as hot-swappable. The controller is VirtIO SCSI, not VirtIO SCSI Single. So I'm very confident this is a ProxmoxVE or...

Tried UEFI and couldn't quite wrap my head around how it works, seems like this is heading in the wrong direction, switching back to SeaBIOS.

Turning QEMU agent off doesn't help either.

Switching the OS to "other" and the cpu arch to Default (kvm64) and disabling NUMA did not "fix" this. Drives still not showing up as added until reboot.