Search results

  1. M

    Confused about proxmox-ve versions and kernels

    read better. mir didn't say that. if you are going to run a new kernel, you have to reboot. if you don't, the new kernel cannot run, so the old one will be still running until you do. at boot you can choose which of the installed kernels run (there is a default, and it should be the latest...
  2. M

    ProxMox backup on different ProxMox

    Yes you can, but the "backup" node should share some of its space through a folder. NFS is one way, you could install samba too, or else. So you should first setup some sharing server on the "backup" node, then configure the "running" node to mount the share locally. Then configure a "local"...
  3. M

    VM Migration to another Server

    one way is to create a vpn between hosts, and make them use the same private network over the vpn never done but read about it here Marco
  4. M

    Bugs related to reused VMIDs

    Hi, maybe it will be more clear if you detail a bit which "privileges" you are specifically referring to... if you created a user which can access pve web interface to use a VMID, someone could answer that if you remove the VMID then is your duty to make sure your permissions are always...
  5. M

    can vnc resolution be scaled/zoomed if too large?

    ok thanks. maybe also CTRL+/- works as usually does in web browsers (firefox at least) to zoom in /out the page, with novnc. Marco
  6. M

    can vnc resolution be scaled/zoomed if too large?

    what if you can't even log in, just because the original vm-inside resolution is too high that you can't even see the prompt? think 1920x1080 on a 800x600 or 1024x768 client (something like this just happened to me). ususally vnc clients can zoom the stramed video at connect time (like I said...
  7. M

    can vnc resolution be scaled/zoomed if too large?

    I didn't know what it was, but from what I see now, it seems an X/wayland client option? Assuming that, I guess this could be set on a linux client (Mac?). On windows, Ultravnc (which I use mostly) gives a zoom option... that works and helps in this case, it is probably something similar?. But...
  8. M

    Second Hard Disk Cannot Be Migrated To?

    afaik. with any shared disk storage you can migrate vm or disks live. not together, though. when you migrate vm with shared storage to another node, you move ram+ conf to the other node, all disks remain on same storage when you migrate a vm disk to shared storage, you move the disk to another...
  9. M

    Backup on Storwize v3700 with LVM

    Gluster storage should be supported, as a storage other filesystems mounted locally could be used as local storage but pve is unaware of their behaviour, imho. Marco
  10. M

    Backup on Storwize v3700 with LVM

    well you could mount the volumes through SAS into the nodes, and "local" backup there. but I guess this leaves out the "shared" option, unless the v3700 can add some magic... or you could script something that after the "local" backup moves/syncs backups together. Or, buy a v7000 :D you could...
  11. M

    Venom vulnerablity

    is the -fda switch still usable in .conf files? would this usage expose the node to the vulnerability? (sorry after posting I saw the coment above) Marco
  12. M

    Help with making a functional Proxmox setup out of this

    a two node cluster behaves very well (if hardwre is reliable) but requires more manual administration and could temporarily lock some service, until you restore its normal state. a third node could have different roles - as a quorum resolver (with two nodes, if 1 is unavailable the cluster goes...
  13. M

    Help with making a functional Proxmox setup out of this

    Yes (udo is much more expert than me, btw) I agree 3 nodes is better But he said "with what they got" and I assumed that the "lto workstation" could be also a Windows one, or not so reliable/redundant or maybe not always on. Of course If you can have 3 "nodes" is always better. I work with two...
  14. M

    Help with making a functional Proxmox setup out of this

    you could do a two nodes cluster somehow http://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster has some con, but the pro is needs only two nodes, and is simple (drbd HA is more complex) if there is budget a safe external shared storage for backups at least would be even better. Marco
  15. M

    Adding a node

    in general, follow this http://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster Marco
  16. M

    Windows QEmu Guest Agent...

    if using https try http Marco
  17. M

    Backup on Storwize v3700 with LVM

    to save backups, iso, etc, you need filesystem storage type, so NFS for example. v7000 could do this but I checked and v3700 coudl not have this. perhaps you could connect another machine (I would not use a vm but...) to the second sas connection to make that a NFS server for the pve cluster...
  18. M

    can vnc resolution be scaled/zoomed if too large?

    Hi, I dont' know how and if I can do this. I have a kvm server which I use at work with the desktop set to a 1600x1200 resolution which fits well my computer display at work. But if I need to connect with another pc (eg: through a vpn from elsewhere) I could have a smaller computer display...
  19. M

    Backup in Large VM Environment

    I cannot count for a large environment (15-20 vm), though I do pve full backups daily, plus some VM with backuppc (testing) and some VM with a commercial solution (which also copies to lto tape, kept forever - hp openview data protector), and also automysqlbackup - for you know what - on linux...
  20. M

    HA without reboot VM

    No expert here, but I guess the only way to have what you wish is having a cluster of specific services, not HA VMs. eg: if your VMs are serving web pages, you need a cluster of web servers in load balancing/failsave configuration, every server on a different host/hypervisor. the same could go...