Search results

I've seen references to at least a balloon driver as well as to a balloon service. Usually, a balloon device does appear on systems. I don't recall if that is done when the VM is specified with variable memory instead of fixed. In any case, the balloon driver from the virtio tools seems to be...

Still shouldn't virtio writethrough outperform ide writethrough? And, as for 0.1.102, I did not use that because I saw a lot of comments regarding bug fixes and enhancement on the windows 2k12 driver. I don't think that I will see any change though, it's just inexplicable for me.

I set up a VM for 2k12r2. The disk is a sparse raw file, converted from a .vhdx snapshot taken with disk2vhd. The configuration of the system, with the disk connected to ide0 was as follows: agent: 1 balloon: 2048 boot: cd bootdisk: ide0 cores: 2 hotplug: usb ide0...

Glad it was solved, please set the title to SOLVED. And do paste here what prompted you to remove the cpuunits from the configuration.

Under /var/log/messages you should find which command is used to move the raw to the qcow file and paste it here. Another approach: 1) keep only the original VM-DATA:103/vm-103-disk-1.raw as boot disk 2) Create a new qcow disk of the same size on another virtio controller If the system boots...

You're awesome, thanks, just what I wanted to find! :)

Can you post your VM config (qm config vmid from a shell) before and after the changes? A newbie here, but just wondering if I can help.

Thanks for the reply mate! Isn't this going to hurt performance a lot? I know, I was mainly asking for a best practice, considering what I have in hand (just a simple RAID-1 setup with 2 disks). Yes, I've done that (even though I must say that on my internal testing I did not have any...

Hello all, I've got a live 2012R2 server, with no Hyper-V functionality enabled. I'm considering doing a P2V of this system, after taking into account https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE as well as the wiki Proxmox best practices for 2012R2. I do have some questions...

Thanks!

This sounds like a newbie question and, well, indeed it is :) Basically, I am trying to figure out how do I "update" a Debian container. If it were a KVM installation, I'd do the usual change of /etc/apt/sources and then apt-get update/dist-upgrade etc. I don't know what's the right thing to do...

Hello all, I have a couple of Debian installations that I have to provide to users elsewhere. These boxes host a back-end and a web front-end. The apps of these boxes have to reconfigured (which is not my problem) and security to these boxes has to be tight (which is). A specific policy...

Perfect, just what I needed! :)

... or when the node admin selects More -> Stop all VMs and Containers? Is it stop or shutdown? I also have networkupstools (NUT) setup. I guess that when a fatal power failure alerts the node to go down, it also automatically brings the KVM boxes down, but how? Via stop or shutdown? Sorry...

Installed older driver, same issue unfortunately. Will keep going to older versions...

Installed SP3; same deal. I'll leave the VM running with the IDE controller I presume...

I used https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso on this VM, as I have done with success in other Windows XP/7 VMs. Like I said, the main difference here is that this XP box is on SP2. I am not aware if SP3 is a requirement. I'll take a VM...

Thank you for all information! :)

Hello all, I salvaged a broken physical system and created first a 4.1 PVE node and then a XP VM in it. For the latter I simply used the existing actual hard disk of the broken system. It booted perfectly from the start, even though no mergeide took place. In fact I expected hell to break...

Thanks, I'll most likely (try to) follow the second approach. Which howto (if any) would you recommend for me to start reading?