Search results

But if you want a graphical interface you should "startx" instead if the vm is a containet just do vzlist extract the ID and vzctl enter VMID voila... :-) Diaolin

Thanks, very good

With a debian 64 configured system i use this method: Install proxmox2 on second machine and then create the vms via interface and later import the kvm files in the /var/lib/vz/images/VMID/imgae.qcow2/raw Adapt the config via interface and live happy Don't forget that scsi is not more...

send it to me, i'll translate it quickly

Added two images red for stopped kvm green for started kvm you can overwrite the ones you find on /usr/share/pve-manager/images with the same name... But when you update they will be overwritten... Diaolin

Just create a new machine in the new proxmox2.0 and then replace the new image in /var/lib/vz/images/VMID/ with the same new name and then start the new machine on Proxmox2. Don't forget to not use te scsi system as boot.... Change it to ide or virtio... Diaolin

True but if you do not expose the filesystem itself and use a cgi that incapsulates a stream containing the right Content-Type i think that it's not so unsecure as you think Just for example; instead of exposing the file directly you can push it to the browser with a cgi. Diaolin

cat /dev/dvd1 > image.iso

The strange situation is that a dongle works with a winXP VM and another dongle does not work with a Linux machine. Bub, if i install the 0.14 version all is ok. Note that if i do lsusb in the VM the result is the same with 0.15 and 0.14 but in the 0.15 version the key results unreadable. In...

In the past, when you released the 0.15 pve-qemu-kvm package the "passthrough of USB" did not work anymore and despite the use of an external key did not work anymore with the internal machine. Downgrading to 0.14 solved the problem. My question is about this thread...

With the 1.9 i should always apply this metod while adding an usb passthrough: wget ftp://download1.proxmox.com/debian/dists/lenny/pve1.8/binary-amd64/pve-qemu-kvm_0.14.1-1_amd64.deb and dpkg -i pve-qemu-kvm_0.14.1-1_amd64.deb With 2.0 this problem was resolved or should i use a differente...

the eth was probably remapped.. dmesg | grep eth !..!.........

Interesting... did you do the Howto?

Found! It was my fault. I created the vm on the local disk... It works..., it hase a longer downtime than the kvm machine but i t starts normally. In any cases it does suspend even if online checked. Diaolin

Ok, i search myself. Tx.

Changed the name via hostname but in the Datacenter i see the already existent VM mapped on the oldnode and the new mapped on the new renamed node. I think that this information will be stored on /etc/pve/.members but it/s unchangeable... Tx, Diaolin

Yeah, seen before writing here. This mean that i should change the method or simply add the quorum disk to the existing proxmoxve2.0 config? Tx, DIaolin

and a file/images server of course! Do you have any suggestion howto create it? Diaolin

In any cases i find that this management will be very very interesting. For now i test it in my Proxmox2.0 course... Diaolin

My opinion is only that if i am in a tree i have the property from the point assigned to me but i cannot destroy that point because this is a property of the container and not of the point itself. But this is only my opinion. Diaolin