All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ron Yorston <rmy@tigress.co.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [FW: [libvirt] PATCH: Experimental User Mode Linux driver for libvirt]
Date: Mon, 20 Oct 2008 20:11:18 +0100	[thread overview]
Message-ID: <20081020191118.GA20239@redhat.com> (raw)
In-Reply-To: <200810201524.m9KFOSPg024776@tiffany.internal.tigress.co.uk>

On Mon, Oct 20, 2008 at 04:24:26PM +0100, Ron Yorston wrote:
> I've now had a chance to try out the UML driver for libvirt.  My host
> platform was CentOS 5 and the guest CentOS 4, with a 2.6.27.2 kernel
> configured as 'make defconfig ARCH=um'.  I used uml:///session as an
> unprivileged user.
> 
> The CVS snapshot tarball on the libvirt.org ftp site was out of date:
> use the cvs command to fetch the source.
> 
> My host system hadn't been set up for UML before so virsh didn't work
> until I'd:
> 
>    created the directory ~/.uml (which doesn't exist if you haven't
>    run a UML instance yet);

Ah, that's useful info - I would never have noticed that :-)

>    installed the UML utilities (because libvirt checks that uml_mconsole
>    exists, even though it doesn't use it).

Yep, that check is now obsolete, so I'll remove it.

> Once I'd figured that out I was able to start a virtual machine from
> virsh and see it using the list command.
> 
> However, connecting to the guest's console was very unreliable (No
> console available for domain).  Also, all attempts to shut down the
> guest from virsh failed (libvir: Remote error :  socket closed
> unexpectedly).  Once that had happened the domain was no longer shown
> by the list command.

Ok, that's a bug I'll look into.

> BTW, is there a way to disconnect from the guest console?

We follow the telnet defaults, and use 'Ctrl+]' sequence

Thanks for taking the time to test out this initial code, hopefully I'll 
get this polished up and incorporated in the next libvirt release.

Regards,
Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2008-10-20 19:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 11:50 [uml-devel] [FW: [libvirt] PATCH: Experimental User Mode Linux driver for libvirt] Daniel P. Berrange
2008-10-17  8:14 ` Ron Yorston
2008-10-20 15:24 ` Ron Yorston
2008-10-20 19:11   ` Daniel P. Berrange [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081020191118.GA20239@redhat.com \
    --to=berrange@redhat.com \
    --cc=rmy@tigress.co.uk \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.