<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>
<br>
</div>I've been wondering about the definition of PV in the context of KVM/Xen.<br>
In the Linux on Linux case for Xen PV practically means that in the HVM<br>
case I have to access block devices using /dev/hda while in the PV case I<br>
can use the faster /dev/xvda. When using KVM which apparently only supports<br>
HVM I can still install a guest using the virtio drivers which seem to do<br>
the same as the paravirtualized devices on Xen.<br>
<br>
So what is the KVM+virtio case if not paravirtualization?<br>
<br>
Regards,<br>
<font color="#888888"> Dennis<br>
</font><div><div></div><div class="h5">__________</div></div></blockquote></div><br>All of it except for that! Your VM isn't just a process accessing a disk. With KVM they've attacked the most commond devices - network and disk and offered paravirtualized devices. This doesn't concern me as the speed has proven to be good although in mysqlbench Xen still leads by quite a bit. I'm concerned about everything else. With 41 interactive VMs I worry about how fast the hypervisor can switch focus, the cpu utilization of each etc..<br>
<br><br clear="all">Grant McWilliams<br><br>Some people, when confronted with a problem, think "I know, I'll use Windows." <br>Now they have two problems.<br><br>