Search results

I had something similar, but mine was without HA. I had a snapshot attached to the VM, snapshot was stored local, VM was on shared storage. It would fail. In my case the snapshot did not exist at all on the local share, and I removed it (via GUI, had to put a dummy file in place so the GUI...

Status.txt contained within sources, it has a bit more info than the last post. Date 19 Jun 2013 repo git://git.engineering.redhat.com/users/vrozenfe/internal-kvm-guest-drivers-windows/.git tag mm85 Fixed bugs: BZ#972310 - in case if the interrupt and the device was not initiali...

Just getting back to testing... found one misconfig. In itself would have been problematic ... But just found the statement in the wiki "Note: Make sure that the VMs or CTs are not running when you add them to HA." That's the big one that burned me. If they are running, they'll just get...

Just discovered it has a snapshot.. but puzzled why they are on different disks ------ Have a VM that will not migrate (online or offline), and from the looks of this it might have been one that I cloned. But not sure... (it does say parent in the config) Anyway when you try to migrate...

yep, guessing thats the case. I had tested it but its been a few months ago. Plus there has been an ilo firmware update that was done. Once management settles down (am my confidence level rebounds) we'll give it a proper testing to confirm.

Well it turned into a royal mess.. I'm sure this deserves another thread, as I had multiple instances of VMs running causing a few corrupted VMs... discovered it after about a day and a half of terror.

I'm sure this has a simple answer, but spammers have beat me into a pulp and I need a break.. Can I specify a preferred node for a VM and have it used when fencing occurs? I would like it say stay on node 4 but if node 4 goes down, it does it thing. Then once node 4 is restored. have the VM...

Not going to say that this is your specific problem, but it might be worth looking at. I noticed that if I install a 32 bit OS on a proxmox default (kvm64) and then later tried to install the balloon driver that the driver installer would pull the 64 bit one, guess it was looking further than...

I fixed mine by logging in direct to the server via ssh. I tried a shortcut via proxmox gui shell and ran into the problem , but I only faced it on one machine of 4.

try qemu , I think new installs default to KVM now. I think all my BSD VMs I had to do this. BTW I'm on AMD procs here

ditto, same here...

Thanks, but it appears to "stop" adding backups after that point is reached.. I have used that in the past... Or is this just something I running into when doing manually or going forward this will behave as "max" number and roll off the old ones. Just added a new one, but no remove option...

Guess one could manually edit vzdump.cron?

Noticed that this is an option with vzdump, remove old backups. Will be see an option to enable this at some time? Having just noticed this and not researched any, but can I employ this option now?

Just a followup, I got this working. At least for now. But it had to do with Dell 6224 Powerconnect's config of a port for QinQ. Just discover this by accident.

Agree, just working to get my head around this powerconnect 6224 vlan configs.

Was working on adding tag to bond0.100, as new bridge vmbr2. Again it works within a node but not between nodes.. So logic tells me that it must be at the switch not passing it thru or the type of bond I am using (802.3ad) I will look further. Its not a show stopper for me, but a method I...

I speaking of VLAN when used with PROXMOX gui, resulting with this ###.conf first VM node 1 net0: virtio=xx:xx:xx:20:A2:18:CA,bridge=vmbr0 net1: virtio=xx:xx:xx:BC:E2:D7:AA,bridge=vmbr0,tag=1 On second VM, on node 2 net0: virtio=xx:xx:xx:FE:AC:13:B4,bridge=vmbr0 net1...

Was playing with this and found that adding a vlan tag, that those vlans worked if on the same node. But not one node to another.. node 1 has 2 VMs with nics configured to vlan 5, when VM was moved to node 2 it stopped. those nics worked between VMs on same node. So I guess the trick is to...

Is administrator spelled right? Mine worked on gen8 servers with your example. Thats the only thing I see. I think your error is listed, unauthorized name