Hofa's questions

I'm trying to set up a mini-cloud with Novell Xen (SLES 10 SP2 so it's Xen 3.2.x).

I have an iSCSI server in the back, using a Starwind 4.1 target. The problem is that I when I write to the iSCSI server with the first host, I can't see the file on the second host and visa versa.

I also tried out Citrix XenServer and that uses LVMoiSCSI, which works without a problem

Can anyone suggest what to do with Novell Xen. I'm not used to working with LVM, so I'd like to try other things before starting with LVM.

I am researching XenServer from Citrix and (with 2 colleagues) comparing it with VMware ESX and Microsoft HyperV.

In our tests, it seems that Xen's live migration is using less resources than VMware's ESX and I would like to know why that is. I found an article from last year that references a paper from 2005, explaining what actually happens with the pages/memory during live migration.

This is an extract of that article about the memory transfer:

Push phase- The source VM continues running while certain pages are pushed across the network to the new destination. To ensure consistency, pages modified during this process must be re-sent.

Stop-and-copy phase The source VM is stopped, pages are copied across to the destination VM, then the new VM is started.

Pull phase The new VM executes and, if it accesses a page that has not yet been copied, this page is faulted in ("pulled") across the network from the source VM.

I was wondering if the memory transfer still happens in the same fashion as it did 4 years ago.