I can make a patch for this.
- Mail original -
De: "lists"
À: "proxmoxve"
Envoyé: Lundi 7 Novembre 2016 20:36:35
Objet: Re: [PVE-User] disable HyperV enlightments for win7 uefi VM
Just to add to my own question:
To disable HyperV
Hi there,
i just tried to migrate a dedicated Host to a LXC container by simple rsync
with —numeric-ids to keet it as it is.
The VM it selfs starts and can be accessed by Console via Proxmox but no
process is started.
Anyone has an idea what can happen? Folders like proc and dev still exists
Just to add to my own question:
To disable HyperV enlightments you have to make sure that these options
are NOT set:
"hv_time,hv_relaxed,hv_spinlocks=0x2000"
Can anyone tell me how to do / where to check that in proxmox?
MJ
On 7-11-2016 18:50, lists wrote:
Hi,
We are trying to migrate a
Hi,
would be realy cool if it is useable also with Logstash/Kibana (ELK Stack)
Maybe there is also to Monitor it?
Cheers
Daniel
> Am 07.11.2016 um 18:44 schrieb Thomas Lamprecht :
>
> Hi,
>
> On 07.11.2016 18:26, lists wrote:
>> Hi,
>>
>> We are using
Hi,
We are trying to migrate a win7 uefi machine into proxmox, and so far
we're failing. Done a lot of reading, and what seems to be the problem:
https://bugs.launchpad.net/qemu/+bug/1593605
My conclusion ius that we should be able to run win7/uefi on qemu, but
we need to disable the
Hi Thomas,
On 7-11-2016 18:44, Thomas Lamprecht wrote:
Proxmox VE provides an interface to Graphite and Influxdb (which can
be/is used by Grafana, IIRC), see:
http://pve.proxmox.com/pve-docs/pve-admin-guide.html#_external_metric_server
Thanks for the QUICK reply. :-)
Taking a look there
Hi,
On 07.11.2016 18:26, lists wrote:
Hi,
We are using collectd/grafana to monitor various servers. We would like to use
that also to check our VMs on proxmox.
There is a plugin for collectd: libvirt (or virt), but this requires libvirt,
which is not installed/used on proxmox.
Is there
it would also be nice for the GUI not to lose the details of the VMs if the
node is down, and indeed allow the transfer of the VM to an active node.
I know this can be done today with the HA but it would be nice to also do this
for non HA VMs
Guy
> On 7 Nov 2016, at 11:50, Kevin
> moving the /etc/pve/nodes/pve11/qemu-server/*.conf files to another node
> worked well. I didn't have to restart any services.
Still, that seems like a fairly usual operation that the GUI could
very well support, I think.
Would it be possible to add that in the future ?
--
Kevin Lemonnier
PGP
You need to move the conf files from /etc/pve/nodes/death-node/qemu-server to
/etc/pve/qemu-server, or I am wrong ?
- Il 7-nov-16, alle 11:50, Daniel dan...@linux-nerd.de ha scritto:
> You dont need to move anythink because /etc/pve is shared and all
> Cluster-Nodes
> knows all Configs
Hello again,
moving the /etc/pve/nodes/pve11/qemu-server/*.conf files to another node
worked well. I didn't have to restart any services.
Thanks again!
On Mon, Nov 7, 2016 at 11:41 AM, Szabolcs F. wrote:
> Hi All,
>
> thanks for all your comments.
>
> Yes, I've got shared
You dont need to move anythink because /etc/pve is shared and all Cluster-Nodes
knows all Configs from the whole Cluster.
The Magic Word here is Shared-Storage.
> Am 07.11.2016 um 11:37 schrieb Guy :
>
> Yes with shared storage it's simple. Move the Conf file to a new node
Hi All,
thanks for all your comments.
Yes, I've got shared storage.
> All my VMs are stored on NAS servers, so a failing Proxmox node is not an
> issue from this point of view, I can still access the VM files. All my 12
> PVE nodes access the storage with NFS.
I'll try to move the .conf files
You can simply move from any of the running nodes the files in
/etc/pve/nodes/name-of-dead-host/qemu-server and move the *conf files to
/etc/pve/qemu-server
Your VMs will appear in that node.
PS: if you can repair your dead node without reinstalling it, delete the files
in /etc/pve/qemu-server
Yes with shared storage it's simple. Move the Conf file to a new node and your
good to go. In fact that's how the migration works anyway.
Conf file storage /etc/pve is synced between the nodes.
No need to restart anything.
---Guy
(via iPhone)
> On 7 Nov 2016, at 10:34, Daniel
Do you have a shared Storage?
If not, how could it be migrated without having all data ;)
> Am 07.11.2016 um 11:16 schrieb Szabolcs F. :
>
> Hello All,
>
> I've got a Proxmox VE 4.3 cluster (no subscription) of 12 Dell C6220 nodes.
>
> My question is: how do I move a VM
In previous versions (3.x) I used to do the following:
(*_NEVER TESTED BY ME ON 4.X_*)
Let's say grop2 is your dead node, grop1 one of your running nodes.
From one of the running nodes:
- In /etc/pve look for config files of the dead node (es. grop2)
root@grop1: $ cd
Hello All,
I've got a Proxmox VE 4.3 cluster (no subscription) of 12 Dell C6220 nodes.
My question is: how do I move a VM from a dead node? Let's say my pve11
dies (hardware issue), but the other 11 nodes are still up In this
case I can't migrate VMs off of pve11, because I get the 'no route to
https://www.suse.com/documentation/sles11/book_kvm/data/sec_kvm_managing_clock.html
Hello list,
I migrated my home server to a VM last week (used MondoRescue images for
the P2V process). Initially, everything seemed to work well. But for the
last few days, the VM has started to show a strange behaviour:
- sometimes right after boot, sometimes after several hours of
operation,
20 matches
Mail list logo