Re: [libvirt] [Xen-devel] [PATCH LIBVIRT] libxl: Recognise ARM architectures

2014-02-28 Thread Daniel P. Berrange
On Fri, Feb 28, 2014 at 02:12:30AM +, Ian Campbell wrote:
 On Wed, 2014-02-26 at 15:01 +, Daniel P. Berrange wrote:
  Yep, if ARM has a PV console, then we'd need to add  tiny bit to the XML
  to allow us to configure that explicitly, similar to how we do for KVM's
  virtio-console support.
 
 Do you mean I need to add something to the XML config snippet, or I need
 to add some special handling in the XML parser/consumer?
 
 I've grepped around the virtio-console stuff and I'm none the wiser.

Opps, yes, I should have explained this better, since our docs here are
about as clear as mud.

With traditional x86 paravirt Xen, we just have the plain paravirt console
devices

console type='pty'
  target type='xen'/
/console

With x86  fullvirt Xen/KVM/QEMU, the console type just defaults to being
a serial port so you would usually just add

serial type='pty'
/serial

and then libvirt would automatically add a console with

console type='pty'
  target type='serial'/
/console


With x86 fullvirt KVM, we also have support for virtio which is
done using

console type='pty'
  target type='virtio'/
/console


So actually this leads me to ask what kind of console Arm fullvirt Xen
guests actually have ? If they just use the traditional Xen paravirt
console, then we just need to make sure that this works for them by
default:

console type='pty'
  target type='xen'/
/console


If there's a different type of console device that's not related to
the Xen paravirt console device, then we'd need to invent a new
target type='xxx'/ value for Arm.

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [libvirt] [Xen-devel] [PATCH LIBVIRT] libxl: Recognise ARM architectures

2014-02-28 Thread Stefano Stabellini
On Fri, 28 Feb 2014, Daniel P. Berrange wrote:
 On Fri, Feb 28, 2014 at 02:12:30AM +, Ian Campbell wrote:
  On Wed, 2014-02-26 at 15:01 +, Daniel P. Berrange wrote:
   Yep, if ARM has a PV console, then we'd need to add  tiny bit to the XML
   to allow us to configure that explicitly, similar to how we do for KVM's
   virtio-console support.
  
  Do you mean I need to add something to the XML config snippet, or I need
  to add some special handling in the XML parser/consumer?
  
  I've grepped around the virtio-console stuff and I'm none the wiser.
 
 Opps, yes, I should have explained this better, since our docs here are
 about as clear as mud.
 
 With traditional x86 paravirt Xen, we just have the plain paravirt console
 devices
 
 console type='pty'
   target type='xen'/
 /console
 
 With x86  fullvirt Xen/KVM/QEMU, the console type just defaults to being
 a serial port so you would usually just add
 
 serial type='pty'
 /serial
 
 and then libvirt would automatically add a console with
 
 console type='pty'
   target type='serial'/
 /console
 
 
 With x86 fullvirt KVM, we also have support for virtio which is
 done using
 
 console type='pty'
   target type='virtio'/
 /console
 
 
 So actually this leads me to ask what kind of console Arm fullvirt Xen
 guests actually have ? If they just use the traditional Xen paravirt
 console, then we just need to make sure that this works for them by
 default:
 
 console type='pty'
   target type='xen'/
 /console
 
 
 If there's a different type of console device that's not related to
 the Xen paravirt console device, then we'd need to invent a new
 target type='xxx'/ value for Arm.

It is just the traditional Xen paravirt console.

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [libvirt] [Xen-devel] [PATCH LIBVIRT] libxl: Recognise ARM architectures

2014-02-28 Thread Ian Campbell
On Fri, 2014-02-28 at 14:29 +, Stefano Stabellini wrote:
 On Fri, 28 Feb 2014, Daniel P. Berrange wrote:
  So actually this leads me to ask what kind of console Arm fullvirt Xen
  guests actually have ? If they just use the traditional Xen paravirt
  console, then we just need to make sure that this works for them by
  default:
  
  console type='pty'
target type='xen'/
  /console
  
  
  If there's a different type of console device that's not related to
  the Xen paravirt console device, then we'd need to invent a new
  target type='xxx'/ value for Arm.
 
 It is just the traditional Xen paravirt console.

I tried the above,which AIUI should work, but it fails with the same
cannot find character device null error. I'll investigate properly
next week.

Ian.

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [libvirt] [Xen-devel] [PATCH LIBVIRT] libxl: Recognise ARM architectures

2014-02-27 Thread Ian Campbell
On Wed, 2014-02-26 at 15:01 +, Daniel P. Berrange wrote:
 Yep, if ARM has a PV console, then we'd need to add  tiny bit to the XML
 to allow us to configure that explicitly, similar to how we do for KVM's
 virtio-console support.

Do you mean I need to add something to the XML config snippet, or I need
to add some special handling in the XML parser/consumer?

I've grepped around the virtio-console stuff and I'm none the wiser.

Thanks,
Ian.


--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [libvirt] [Xen-devel] [PATCH LIBVIRT] libxl: Recognise ARM architectures

2014-02-26 Thread Daniel P. Berrange
On Wed, Feb 26, 2014 at 02:55:13PM +, Ian Campbell wrote:
 On Wed, 2014-02-26 at 15:00 +0100, Olaf Hering wrote:
  On Wed, Feb 26, Ian Campbell wrote:
  
   On Wed, 2014-02-26 at 12:37 +, Daniel P. Berrange wrote:
On Wed, Feb 26, 2014 at 12:34:17PM +, Ian Campbell wrote:
 Currently virsh console fails with:
   Connected to domain libvirt-test
   Escape character is ^]
   error: internal error: cannot find character device null
That'll be because no console or serial device is
listed in your config above I expect. Also looks like
bogus error handling in the console API, not checking
for null.
   Thanks. I've just tried (inside devices.../...):
console tty='/dev/pts/5'/
   and
console type='pty'
 target port='0'/
   /console
   which I gleaned from http://libvirt.org/drvxen.html but neither seem to
   do the trick (and the first ones use of an explicit pts looks odd to
   me...).
  
  I learned yesterday this should be serial instead of console, maybe
  it fixes also your case.
 
 My understanding was that this was for HVM guests, whereas ARM has a PV
 console but I suppose I should try it anyway. I've got a flight to catch
 so it'll be a few days I expect.

Yep, if ARM has a PV console, then we'd need to add  tiny bit to the XML
to allow us to configure that explicitly, similar to how we do for KVM's
virtio-console support.


Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [libvirt] [Xen-devel] [PATCH LIBVIRT] libxl: Recognise ARM architectures

2014-02-26 Thread Ian Campbell
On Wed, 2014-02-26 at 15:00 +0100, Olaf Hering wrote:
 On Wed, Feb 26, Ian Campbell wrote:
 
  On Wed, 2014-02-26 at 12:37 +, Daniel P. Berrange wrote:
   On Wed, Feb 26, 2014 at 12:34:17PM +, Ian Campbell wrote:
Currently virsh console fails with:
  Connected to domain libvirt-test
  Escape character is ^]
  error: internal error: cannot find character device null
   That'll be because no console or serial device is
   listed in your config above I expect. Also looks like
   bogus error handling in the console API, not checking
   for null.
  Thanks. I've just tried (inside devices.../...):
   console tty='/dev/pts/5'/
  and
   console type='pty'
target port='0'/
  /console
  which I gleaned from http://libvirt.org/drvxen.html but neither seem to
  do the trick (and the first ones use of an explicit pts looks odd to
  me...).
 
 I learned yesterday this should be serial instead of console, maybe
 it fixes also your case.

My understanding was that this was for HVM guests, whereas ARM has a PV
console but I suppose I should try it anyway. I've got a flight to catch
so it'll be a few days I expect.

Thanks,

Ian.

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [libvirt] [Xen-devel] [PATCH LIBVIRT] libxl: Recognise ARM architectures

2014-02-26 Thread Olaf Hering
On Wed, Feb 26, Ian Campbell wrote:

 On Wed, 2014-02-26 at 12:37 +, Daniel P. Berrange wrote:
  On Wed, Feb 26, 2014 at 12:34:17PM +, Ian Campbell wrote:
   Currently virsh console fails with:
 Connected to domain libvirt-test
 Escape character is ^]
 error: internal error: cannot find character device null
  That'll be because no console or serial device is
  listed in your config above I expect. Also looks like
  bogus error handling in the console API, not checking
  for null.
 Thanks. I've just tried (inside devices.../...):
  console tty='/dev/pts/5'/
 and
  console type='pty'
   target port='0'/
 /console
 which I gleaned from http://libvirt.org/drvxen.html but neither seem to
 do the trick (and the first ones use of an explicit pts looks odd to
 me...).

I learned yesterday this should be serial instead of console, maybe
it fixes also your case.

Olaf

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list