Too bad they don't sell jails. Instead it's FreeBSD on KVM :\FreeBSD doesn't have paravirtualized network and block drivers for KVM, which means FreeBSD has less than optimal performance. In practise it works quite well, but if high performance is a requirement for your application we currently recommend a Linux based OS.
There appears to be a regression in KVM with regard to ACPI events. For some reason the ACPI power button event is not received by the FreeBSD guest. This effectively means you can't gracefully shutdown your FreeBSD VPS from our webapp. We expect this issue to be fixed soon-ish.
We can't resize the FreeBSD UFS filesystem from the Linux host, nor does the FreeBSD growfs command support online resizing. This makes it difficult if not impossible to properly automate resizing of FreeBSD guests. If you want to upgrade your FreeBSD VPS later on, be aware that the filesystems will not be resized. (Our webapp will give a warning about this.) If you want to start using the extra assigned disk space, contact us and we'll grow your filesystem manually.
ssh -i [i][b]path to your .pem file[/i][/b] root@[i][b]Your Public DNS Name[/b][/i]
So, once you create an EBS Volume and attach it to your running instance, tail your /var/log/messages and you will see the device name assigned by the kernel:This is a bug in fdisk. There is a simple workaround: Don't use fdisk --
there's really no point given that you can create as many virtual disks
as you want using EBS. Just newfs and mount the raw EBS disks.
Jun 10 15:55:37 yourhost kernel: xbd2: 10240MB <Virtual Block Device> at device/vbd/2080 on xenbusb_front0 Jun 10 15:55:37 yourhost kernel: xbd2: attaching as da2 Jun 10 15:55:37 yourhost kernel: GEOM: new disk da2
# newfs /dev/da2 # mkdir /ebs # mount /dev/da2 /ebs
/dev/da2 /ebs ufs rw 0 2
Reaction score: 2