Search results

The Firewall Wiki page https://pve.proxmox.com/wiki/Firewall explains If you enable the firewall, traffic to all hosts is blocked by default. Only exceptions is WebGUI(8006) and ssh(22) from your local network. I think quite a lot of Proxmox users have the server in a remote located...

No takers? No suggestions? # pveperf CPU BOGOMIPS: 54277.84 REGEX/SECOND: 1791183 HD SIZE: 19.10 GB (/dev/sda1) BUFFERED READS: 455.75 MB/sec AVERAGE SEEK TIME: 0.05 ms FSYNCS/SECOND: 2527.58 DNS EXT: 27.17 ms DNS INT: 2.06 ms

Yes it has been asked before, a decade ago. Things have moved on, we no longer use OpenVZ. How is it done 2019? I can rename the devices under /dev/pve and update the config files under /etc/pve/qemu-server, but after a reboot the symlinks under /dev/pve are back to their old values. I suppose...

I tried to get around this by disabling the qemu agent, but now it is just crashing the server instead. Then BANG reboot. I had a look around the files available under /var/log but don't see anything obvious. For example this from kern.log: help?

I believe I have the latest QEMU drivers available: Hypervisor: # dpkg -l | grep -i qemu ii pve-qemu-kvm 3.0.1-4 amd64 Full virtualization on x86 hardware ii qemu-server 5.0-54 amd64...

Ok, some more details: root@server36:~# qm agent 105 fsfreeze-status thawed root@server36:~# qm agent 105 fsfreeze-freeze # ... 10 minutes pass, nothing happens, 105 is dead to the world, so I decide to break this and thaw it. ^C root@server36:~# qm agent 105 fsfreeze-thaw QEMU guest agent is...

So here is the continuation of the story. Trying to do an automatic snapshot last night I woke up to a unresponsive server, and this logfile: The snapshot/backup was taken, the problem is just that the server was dead in the water for two hours. Off peak hours but still. Anyway, any idea why...

The vzdump(1) man page says: I'm just wondering how to understand this, as it conflicts with the above statement, and also with my own observations. No LVM - no snapshot. So how should we understand the man page? And somewhat related .... is it possible to use compression with snapshots and...

So yet another thin lvm question: LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert base-101-disk-0 pve Vri---tz-k 32.00g vmdata tz pve -wi-ao---- 250.00g vm-103-disk-0 pve Vwi-aotz-- 32.00g vmdata base-101-disk-0...

Now this is the weirdest ... the only change I made was adding [general] verbose = 1 To the bottom of /etc/sysconfig/qemu-ga. I did't know how to "restart" qemu so I rebooted the VM, then ran the vzdump command like before, but now it runs as it should. o_O

I don't have any /etc/default/qemu-guest-agent on my VM: ]# rpm -ql qemu-guest-agent /etc/qemu-ga /etc/qemu-ga/fsfreeze-hook /etc/qemu-ga/fsfreeze-hook.d /etc/sysconfig/qemu-ga /usr/bin/qemu-ga /usr/lib/systemd/system/qemu-guest-agent.service /usr/lib/udev/rules.d/99-qemu-guest-agent.rules...

Isn't Atheros wifi equipment?

Drunk with the success I decided to try the snapshot again. root@pme:~# qm agent 105 fsfreeze-status thawed root@pme:~# vzdump 105 --mode snapshot INFO: starting new backup job: vzdump 105 --mode snapshot INFO: Starting Backup of VM 105 (qemu) INFO: Backup started at 2019-11-05 05:37:47 INFO...

That seemed to go fine ... root@pve:~# qm agent 105 fsfreeze-status thawed root@pve:~# qm agent 105 fsfreeze-freeze 3 root@pve:~# qm agent 105 fsfreeze-status frozen root@pve:~# qm agent 105 fsfreeze-thaw 3 root@pve:~# qm agent 105 fsfreeze-status thawed root@pve:~#

If if if freeze up again, is there any way to make it unfreeze other than a reset of the VM ? Also, before doing this, would it make any sense to remove /reinstall the qemu-agent software?

Ok, how do I do that, and what is the expected result?

I rebooted the VM but it didn't suffice, i had to actually shut it down and restart it. Anyway, up again, without the qemu agent, and a vzdump -snapshot performs as it should.

I tried to disable qemu-agent, but it went Enabled|Disabled (on top of each other) as if it has to be rebootet to activate?

Ok, I'll give it a shot and see what happens.

I still don't understand what is expected to happen if I disable the qemu-agent option?