On Jan 31, 2012, at 4:42 PM, Bruce Dubbs wrote:

> Qrux wrote:
> 
>> At the moment, there's a large body of support and activity for both
>> Xen and KVM...KVM may be easier to deploy for graphical Guests; I've never
>> tried hosting one on Xen.
> 
> Well I can say that figuring out KVM (networking) wasn't easy for me. 

The one nicety of Xen networking is that once you have the host bridge setup 
(BTW, Bruce, I'm about to test those scripts we worked on), the management 
tools to bring up new VMs takes care of creating the other bridges.  I also 
think the new scripts (bridge & modified if{up,down}) are going to trivialize 
the host bridge.

> Hopefully, it will be easier for others.  OTOH, the gui part was easy. 

That's really good to hear.  I think a lot of desktop users who want to get 
their feet with virtualization probably use a machine with X, and probably want 
their Guest OS to use X, too.

>> I'm not really trying to recommend one over the other (it appears to
>> be a rather religious "Emacs/Vi" issue for those who care).  My
>> personal opinion is just that Xen would be a nice add to BLFS.
>> Although, frankly, I'm not married to the idea.

> I don't have any preferences either, other than kvm is the one I 
> happened to choose first.  I did so because I knew the drivers are built 
> into the kernel and kvm-qemu is basically a CMMI app.  BTW, all the 
> online docs talk about running modprobe, etc.  That's not necessary. 
> Building the drivers directly into the kernel works fine.

I also build all the drivers directly into the kernel.  I hate mucking about 
with modprobe & co., and other than some embedded folks, I'm not sure anyone 
cares about the size of their kernel (i.e., if they're compiling their own 
anyway).

Xen also manages to boot "out-of-the-box" with the drivers compiled in.

What is "CMMI" in this context?  Not sure what "Capability Maturity Models" has 
to do with kvm-qemu...

>> Speaking of which--has anyone successfully compiled Dev86 on their
>> BLFS setup...?
> 
> I don't know what Dev86 is.

It's a toolset for compiling some low-level Xen stuff (like when it has to 
present a BIOS to an unmodified Guest--e.g., Windows).  I'm surprised KVM 
doesn't need it, since it's a full-virt system.  With some patches I found, I 
was able to build a subset of the tools in Dev86, but I think I hit a wall when 
Xen wanted to see a 32-bit glibc.

I'll investigate some more on my own...sorry about the non-sequitur.

        Q

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to