Search results

  1. JonathanB19

    [SOLVED] Can't start vm code 1006

    Strange. Try starting the VM using the console (right click on VM and choose "Console" from the menu, then hit Start from the button on the top right of the console window). Can you see anything happening there? Also, can you post the VM's config? Log in to the host machine over SSH and see the...
  2. JonathanB19

    Updated Raid controller list page

    Here in the UK, many co-lo companies charge based on power used. Hardware RAID controllers take more power, so they're more expensive to run. Same goes for SSDs vs mechanical drives. Our current servers have hardware RAID and mechanical drives but we worked out that changing to SSDs and software...
  3. JonathanB19

    [SOLVED] Can't start vm code 1006

    Is this a KVM or a container? Also, have you been able to launch any VM or is this the first one you've tried? Is there anything that might be a clue in the syslog tab of the host?
  4. JonathanB19

    Ubuntu Container - No Internet

    Can you post the contents of the host machine's /etc/network/interfaces file so we can see what your network looks like? The same for the guest's would be good too.
  5. JonathanB19

    shared virtual disk on vms

    Good luck remzi! You've inspired me to experiment with the same thing - would be very useful to share disks between vms.
  6. JonathanB19

    restoring an image in proxmox

    This is a physical-to-virtual ("P2V") transfer. Here's how I've done it in the past (from memory - your mileage may vary): 1. Assuming you have your Clonezilla image of the physical machine on an external drive, plug that drive into the Proxmox VM host. 2. Upload a Clonezilla ISO image to...
  7. JonathanB19

    [SOLVED] Upgrade dry-run: how to update to current 3.4 version?

    I worked it out by copying all the *pve*.deb files from /var/cache/apt/archives on the host, then using these to upgrade the test machine's packages. For some reason there's a slight variation between the two though: production says it's running proxmox-ve-2.6.32: 3.4-166 while the test says...
  8. JonathanB19

    Disk Passed Through to KVM Errors When Starting the KVM

    Can you post the contents of the config file for the VM? It should be in /etc/pve/nodes/proxmox/qemu-server/
  9. JonathanB19

    shared virtual disk on vms

    OK, well I've not tried it, but you could try simply editing the VM's config files so that they use the same disk image (eg both using vm-8201-disk-1.qcow2 for ide0). You can't do that from the GUI though - you'll have to edit the VM's configs directly in /etc/pve/nodes/proxmox/qemu-server/...
  10. JonathanB19

    shared virtual disk on vms

    One way would be to set up an NFS server VM and have client machines connect to the exports.
  11. JonathanB19

    [SOLVED] Upgrade dry-run: how to update to current 3.4 version?

    I need to do an in-place upgrade of a licensed PVE production server from 3.4 to 4.1. I've set up a test rig replicating the production setup, but I can't update the test machine to the same version of PVE as the production machine because the test machine is only on the evaluation license...
  12. JonathanB19

    Warning about public portmapper on PVE host

    "Note that on newer PVE versions we enable 22 and 8006 always if not explicit disabled so user do not easy lock them self out." Ah that's good to know. From what PVE version is that enabled?
  13. JonathanB19

    Warning about public portmapper on PVE host

    OK thanks. So if I'm not using NFS, can I shut down RPC portmapper on the host without problems?
  14. JonathanB19

    Warning about public portmapper on PVE host

    Sorry if this has been mentioned before but I can't initially find anything. Just got a warning from my ISP about this: The folks at shadowserver security group are reporting open portmapper hosts to us, these need to get fixed as they can be used in amplification denial of service attacks...