virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

Hello!

I'm using Fedora 10 on my Xen pv_ops testing box.

I rebuilt Xen 3.3.1-9 packages from F11/rawhide for Fedora 10 and installed them.

http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/9.fc11/src/xen-3.3.1...

xen-3.3.1-9.fc10.i386.rpm
xen-debuginfo-3.3.1-9.fc10.i386.rpm
xen-devel-3.3.1-9.fc10.i386.rpm
xen-hypervisor-3.3.1-9.fc10.i386.rpm
xen-libs-3.3.1-9.fc10.i386.rpm
xen-runtime-3.3.1-9.fc10.i386.rpm

I also built custom 2.6.29-rc7 pv_ops dom0 kernel, which seems to boot OK
for me.

xend starts OK, and I can run 'xm info', 'xm list' etc.

But now I'm having problems using virt-install and/or virt-manager to
install new domains.

[root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l
"ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"

ERROR    Unsupported virtualization type 'xen' 

Has Xen support been dropped from virt-install, or is this just some bug? 

-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Cole Robinson]

Pasi Kärkkäinen wrote:
>  Hello!
>  
>  I'm using Fedora 10 on my Xen pv_ops testing box.
>  
>  I rebuilt Xen 3.3.1-9 packages from F11/rawhide for Fedora 10 and installed them.
>  
>  http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/9.fc11/src/xen-3.3.1...
>  
>  xen-3.3.1-9.fc10.i386.rpm
>  xen-debuginfo-3.3.1-9.fc10.i386.rpm
>  xen-devel-3.3.1-9.fc10.i386.rpm
>  xen-hypervisor-3.3.1-9.fc10.i386.rpm
>  xen-libs-3.3.1-9.fc10.i386.rpm
>  xen-runtime-3.3.1-9.fc10.i386.rpm
>  
>  I also built custom 2.6.29-rc7 pv_ops dom0 kernel, which seems to boot OK
>  for me.
>  
>  xend starts OK, and I can run 'xm info', 'xm list' etc.
>  
>  But now I'm having problems using virt-install and/or virt-manager to
>  install new domains.
>  
>  [root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l
>
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  
>  ERROR    Unsupported virtualization type 'xen' 
>  
>  Has Xen support been dropped from virt-install, or is this just some bug? 
>   
Xen support hasn't been dropped, we are probably just failing to detect
that xen is available.

First, can you try 'virsh --connect xen:///' and see if it succeeds? If
that works, you can manually pass the connection string to virt-install
in the interim (virt-install --connect xen:/// ...)

Can you also check if the following 3 locations exist:

/var/lib/xend
/dev/xen/evtchn
/proc/xen

That is what we check in virtinst to guess that xen is present, and we
should use its connection by default. If one of those is missing, any
recommendations on how to detect xen presence would be appreciated.

Thanks,
Cole

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Sat, Mar 07, 2009 at 12:33:46PM -0500, Cole Robinson wrote:
>  Pasi Kärkkäinen wrote:
>  > Hello!
>  > 
>  > I'm using Fedora 10 on my Xen pv_ops testing box.
>  > 
>  > I rebuilt Xen 3.3.1-9 packages from F11/rawhide for Fedora 10 and installed them.
>  > 
>  >
> http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/9.fc11/src/xen-3.3.1...
>  > 
>  > xen-3.3.1-9.fc10.i386.rpm
>  > xen-debuginfo-3.3.1-9.fc10.i386.rpm
>  > xen-devel-3.3.1-9.fc10.i386.rpm
>  > xen-hypervisor-3.3.1-9.fc10.i386.rpm
>  > xen-libs-3.3.1-9.fc10.i386.rpm
>  > xen-runtime-3.3.1-9.fc10.i386.rpm
>  > 
>  > I also built custom 2.6.29-rc7 pv_ops dom0 kernel, which seems to boot OK
>  > for me.
>  > 
>  > xend starts OK, and I can run 'xm info', 'xm list' etc.
>  > 
>  > But now I'm having problems using virt-install and/or virt-manager to
>  > install new domains.
>  > 
>  > [root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p
> -l
>  >
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  > 
>  > ERROR    Unsupported virtualization type 'xen' 
>  > 
>  > Has Xen support been dropped from virt-install, or is this just some bug? 
>  > 
>  
>  Xen support hasn't been dropped, we are probably just failing to detect
>  that xen is available.
>  
>  First, can you try 'virsh --connect xen:///' and see if it succeeds? If
>  that works, you can manually pass the connection string to virt-install
>  in the interim (virt-install --connect xen:/// ...)
>   
Yeah, that seems to work:

[root@dom0test ~]# virsh --connect xen:///
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
       'quit' to quit

virsh # vcpuinfo 0
VCPU:           0
CPU:            0
State:          running
CPU time:       32.3s
CPU Affinity:   yy

VCPU:           1
CPU:            1
State:          idle
CPU time:       18.9s
CPU Affinity:   yy

virsh # version
Compiled against library: libvir 0.5.1
Using library: libvir 0.5.1
Using API: Xen 3.0.1
Running hypervisor: Xen 3.3.0

virsh # quit

[root@dom0test ~]# xm info
host                   : dom0test.localdomain
release                : 2.6.29-rc7-tip
version                : #10 SMP Sat Mar 7 16:04:28 EET 2009
machine                : i686
nr_cpus                : 2
nr_nodes               : 1
cores_per_socket       : 1
threads_per_core       : 2
cpu_mhz                : 3000
hw_caps                :
bfebfbff:00000000:00000000:00000180:0000441d:00000000:00000000:00000000
virt_caps              : 
total_memory           : 2038
free_memory            : 992
node_to_cpu            : node0:0-1
node_to_memory         : node0:992
xen_major              : 3
xen_minor              : 3
xen_extra              : .1-9.fc10
xen_caps               : xen-3.0-x86_32p 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xf5800000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC) 
cc_compile_by          : root
cc_compile_domain      : localdomain
cc_compile_date        : Fri Mar  6 17:24:19 EET 2009
xend_config_format     : 4


>  Can you also check if the following 3 locations exist:
>  
>  /var/lib/xend
>  /dev/xen/evtchn
>  /proc/xen
>   
Yep, all of those do exist.

[root@dom0test ~]# ls /var/lib/xend
domains  relocation-socket  state  storage  xend-socket

[root@dom0test ~]# ls -la /dev/xen/evtchn 
crw-rw---- 1 root root 10, 63 2009-03-07 20:10 /dev/xen/evtchn

[root@dom0test ~]# ls /proc/xen/
capabilities  privcmd  xenbus  xsd_kva  xsd_port


>  That is what we check in virtinst to guess that xen is present, and
> we
>  should use its connection by default. If one of those is missing, any
>  recommendations on how to detect xen presence would be appreciated.
>   
[root@dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f
/dev/vg00/vm01 --vnc -p -l
"ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"

ERROR    Unsupported virtualization type 'xen'

Hmm.. so that didn't help unfortunately.. Other ideas? 

And thanks!

-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Cole Robinson]

Pasi Kärkkäinen wrote:
>  
>  [root@dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f
> /dev/vg00/vm01 --vnc -p -l
>
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  
>  ERROR    Unsupported virtualization type 'xen'
>  
>  Hmm.. so that didn't help unfortunately.. Other ideas? 
>   
Ah okay. Libvirt capabilities must be getting confused. Can you attach
the output of

virsh --connect xen:/// capabilities
cat /sys/hypervisor/properties/capabilities

Thanks,
Cole

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote:
>  Pasi Kärkkäinen wrote:
>  > 
>  > [root@dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f
> /dev/vg00/vm01 --vnc -p -l
>  >
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  > 
>  > ERROR    Unsupported virtualization type 'xen'
>  > 
>  > Hmm.. so that didn't help unfortunately.. Other ideas? 
>  > 
>  
>  Ah okay. Libvirt capabilities must be getting confused. Can you attach
>  the output of
>  
>  virsh --connect xen:/// capabilities
>  cat /sys/hypervisor/properties/capabilities
>   
[root@dom0test ~]# virsh --connect xen:/// capabilities
<capabilities>

  <host>
    <cpu>
      <arch>i686</arch>
      <features>
        <pae/>
      </features>
    </cpu>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>xenmigr</uri_transport>
      </uri_transports>
    </migration_features>
    <topology>
      <cells num='1'>
        <cell id='0'>
          <cpus num='2'>
            <cpu id='0'/>
            <cpu id='1'/>
          </cpus>
        </cell>
      </cells>
    </topology>
  </host>

</capabilities>

[root@dom0test ~]# cat /sys/hypervisor/properties/capabilities
cat: /sys/hypervisor/properties/capabilities: No such file or directory


-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Sat, Mar 07, 2009 at 08:50:36PM +0200, Pasi Kärkkäinen wrote:
>  On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote:
>  > Pasi Kärkkäinen wrote:
>  > > 
>  > > [root@dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f
> /dev/vg00/vm01 --vnc -p -l
>  > >
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  > > 
>  > > ERROR    Unsupported virtualization type 'xen'
>  > > 
>  > > Hmm.. so that didn't help unfortunately.. Other ideas? 
>  > > 
>  > 
>  > Ah okay. Libvirt capabilities must be getting confused. Can you attach
>  > the output of
>  > 
>  > virsh --connect xen:/// capabilities
>  > cat /sys/hypervisor/properties/capabilities
>  > 
>  
>  [root@dom0test ~]# virsh --connect xen:/// capabilities
>  <capabilities>
>  
>    <host>
>      <cpu>
>        <arch>i686</arch>
>        <features>
>          <pae/>
>        </features>
>      </cpu>
>      <migration_features>
>        <live/>
>        <uri_transports>
>          <uri_transport>xenmigr</uri_transport>
>        </uri_transports>
>      </migration_features>
>      <topology>
>        <cells num='1'>
>          <cell id='0'>
>            <cpus num='2'>
>              <cpu id='0'/>
>              <cpu id='1'/>
>            </cpus>
>          </cell>
>        </cells>
>      </topology>
>    </host>
>  
>  </capabilities>
>  
>  [root@dom0test ~]# cat /sys/hypervisor/properties/capabilities
>  cat: /sys/hypervisor/properties/capabilities: No such file or directory
>   
[root@dom0test ~]# ls -la /sys/hypervisor
ls: cannot access /sys/hypervisor: No such file or directory


-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Cole Robinson]

Pasi Kärkkäinen wrote:
>  On Sat, Mar 07, 2009 at 08:50:36PM +0200, Pasi Kärkkäinen wrote:
> > On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote:
> >> Pasi Kärkkäinen wrote:
> >>> [root@dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f
> /dev/vg00/vm01 --vnc -p -l
> >>>
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
> >>>
> >>> ERROR    Unsupported virtualization type 'xen'
> >>>
> >>> Hmm.. so that didn't help unfortunately.. Other ideas? 
> >>>
> >> Ah okay. Libvirt capabilities must be getting confused. Can you attach
> >> the output of
> >>
> >> virsh --connect xen:/// capabilities
> >> cat /sys/hypervisor/properties/capabilities
> >>
> > [root@dom0test ~]# virsh --connect xen:/// capabilities
> > <capabilities>
> >
> >   <host>
> >     <cpu>
> >       <arch>i686</arch>
> >       <features>
> >         <pae/>
> >       </features>
> >     </cpu>
> >     <migration_features>
> >       <live/>
> >       <uri_transports>
> >         <uri_transport>xenmigr</uri_transport>
> >       </uri_transports>
> >     </migration_features>
> >     <topology>
> >       <cells num='1'>
> >         <cell id='0'>
> >           <cpus num='2'>
> >             <cpu id='0'/>
> >             <cpu id='1'/>
> >           </cpus>
> >         </cell>
> >       </cells>
> >     </topology>
> >   </host>
> >
> > </capabilities>
> >
> > [root@dom0test ~]# cat /sys/hypervisor/properties/capabilities
> > cat: /sys/hypervisor/properties/capabilities: No such file or directory
> >
>  
>  [root@dom0test ~]# ls -la /sys/hypervisor
>  ls: cannot access /sys/hypervisor: No such file or directory
>  
>   
Hmm, well that will do it. Libvirt capabilities are what tell user apps
what types of domains can be installed, and generating xen capabilities
is largely dependent on the above paths. Not too sure what to do from here.

- Cole

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote:
>  Pasi Kärkkäinen wrote:
>  > On Sat, Mar 07, 2009 at 08:50:36PM +0200, Pasi Kärkkäinen wrote:
>  >> On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote:
>  >>> Pasi Kärkkäinen wrote:
>  >>>> [root@dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512
> --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l
>  >>>>
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  >>>>
>  >>>> ERROR    Unsupported virtualization type 'xen'
>  >>>>
>  >>>> Hmm.. so that didn't help unfortunately.. Other ideas? 
>  >>>>
>  >>> Ah okay. Libvirt capabilities must be getting confused. Can you attach
>  >>> the output of
>  >>>
>  >>> virsh --connect xen:/// capabilities
>  >>> cat /sys/hypervisor/properties/capabilities
>  >>>
>  >> [root@dom0test ~]# virsh --connect xen:/// capabilities
>  >> <capabilities>
>  >>
>  >>   <host>
>  >>     <cpu>
>  >>       <arch>i686</arch>
>  >>       <features>
>  >>         <pae/>
>  >>       </features>
>  >>     </cpu>
>  >>     <migration_features>
>  >>       <live/>
>  >>       <uri_transports>
>  >>         <uri_transport>xenmigr</uri_transport>
>  >>       </uri_transports>
>  >>     </migration_features>
>  >>     <topology>
>  >>       <cells num='1'>
>  >>         <cell id='0'>
>  >>           <cpus num='2'>
>  >>             <cpu id='0'/>
>  >>             <cpu id='1'/>
>  >>           </cpus>
>  >>         </cell>
>  >>       </cells>
>  >>     </topology>
>  >>   </host>
>  >>
>  >> </capabilities>
>  >>
>  >> [root@dom0test ~]# cat /sys/hypervisor/properties/capabilities
>  >> cat: /sys/hypervisor/properties/capabilities: No such file or directory
>  >>
>  > 
>  > [root@dom0test ~]# ls -la /sys/hypervisor
>  > ls: cannot access /sys/hypervisor: No such file or directory
>  > 
>  > 
>  
>  Hmm, well that will do it. Libvirt capabilities are what tell user apps
>  what types of domains can be installed, and generating xen capabilities
>  is largely dependent on the above paths. Not too sure what to do from here.
>   
Ok.

I'll try asking what's the thing with that.. if it's still missing, or is it
deprecated or something..

-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Sat, Mar 07, 2009 at 09:37:25PM +0200, Pasi Kärkkäinen wrote:
>  On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote:
>  > Pasi Kärkkäinen wrote:
>  > > On Sat, Mar 07, 2009 at 08:50:36PM +0200, Pasi Kärkkäinen wrote:
>  > >> On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote:
>  > >>> Pasi Kärkkäinen wrote:
>  > >>>> [root@dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512
> --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l
>  > >>>>
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  > >>>>
>  > >>>> ERROR    Unsupported virtualization type 'xen'
>  > >>>>
>  > >>>> Hmm.. so that didn't help unfortunately.. Other ideas? 
>  > >>>>
>  > >>> Ah okay. Libvirt capabilities must be getting confused. Can you attach
>  > >>> the output of
>  > >>>
>  > >>> virsh --connect xen:/// capabilities
>  > >>> cat /sys/hypervisor/properties/capabilities
>  > >>>
>  > >> [root@dom0test ~]# virsh --connect xen:/// capabilities
>  > >> <capabilities>
>  > >>
>  > >>   <host>
>  > >>     <cpu>
>  > >>       <arch>i686</arch>
>  > >>       <features>
>  > >>         <pae/>
>  > >>       </features>
>  > >>     </cpu>
>  > >>     <migration_features>
>  > >>       <live/>
>  > >>       <uri_transports>
>  > >>         <uri_transport>xenmigr</uri_transport>
>  > >>       </uri_transports>
>  > >>     </migration_features>
>  > >>     <topology>
>  > >>       <cells num='1'>
>  > >>         <cell id='0'>
>  > >>           <cpus num='2'>
>  > >>             <cpu id='0'/>
>  > >>             <cpu id='1'/>
>  > >>           </cpus>
>  > >>         </cell>
>  > >>       </cells>
>  > >>     </topology>
>  > >>   </host>
>  > >>
>  > >> </capabilities>
>  > >>
>  > >> [root@dom0test ~]# cat /sys/hypervisor/properties/capabilities
>  > >> cat: /sys/hypervisor/properties/capabilities: No such file or directory
>  > >>
>  > > 
>  > > [root@dom0test ~]# ls -la /sys/hypervisor
>  > > ls: cannot access /sys/hypervisor: No such file or directory
>  > > 
>  > > 
>  > 
>  > Hmm, well that will do it. Libvirt capabilities are what tell user apps
>  > what types of domains can be installed, and generating xen capabilities
>  > is largely dependent on the above paths. Not too sure what to do from here.
>  > 
>  
>  Ok.
>  
>  I'll try asking what's the thing with that.. if it's still missing, or is it
>  deprecated or something..
>   
Ok, it seems that /sys/hypervisor feature is not yet implemented in pv_ops
dom0 kernel.

There's a patch somewhere in Redhat's old dom0 repository.. Jeremy is trying
to find that. 

For reference discussion on xen-devel about this:
http://lists.xensource.com/archives/html/xen-devel/2009-03/msg00472.html

-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Daniel P. Berrange]

On Sun, Mar 08, 2009 at 09:23:10PM +0200, Pasi K?rkk?inen wrote:
>  On Sat, Mar 07, 2009 at 09:37:25PM +0200, Pasi Kärkkäinen wrote:
>  > On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote:
>  > > >> [root@dom0test ~]# cat /sys/hypervisor/properties/capabilities
>  > > >> cat: /sys/hypervisor/properties/capabilities: No such file or
> directory
>  > > >>
>  > > > 
>  > > > [root@dom0test ~]# ls -la /sys/hypervisor
>  > > > ls: cannot access /sys/hypervisor: No such file or directory
>  > > > 
>  > > > 
>  > > 
>  > > Hmm, well that will do it. Libvirt capabilities are what tell user apps
>  > > what types of domains can be installed, and generating xen capabilities
>  > > is largely dependent on the above paths. Not too sure what to do from here.
>  > > 
>  > 
>  > Ok.
>  > 
>  > I'll try asking what's the thing with that.. if it's still missing, or
> is it
>  > deprecated or something..
>  > 
>  
>  Ok, it seems that /sys/hypervisor feature is not yet implemented in pv_ops
>  dom0 kernel.
>  
>  There's a patch somewhere in Redhat's old dom0 repository.. Jeremy is trying
>  to find that.  

If this patch gets rejected for whatever reason, let me know, becasue we
can possibly switch libvirt over to making a direct hypercall to fetch
this information.

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 :|

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Mon, Mar 09, 2009 at 10:39:29AM +0000, Daniel P. Berrange wrote:
>  On Sun, Mar 08, 2009 at 09:23:10PM +0200, Pasi K?rkk?inen wrote:
>  > On Sat, Mar 07, 2009 at 09:37:25PM +0200, Pasi Kärkkäinen wrote:
>  > > On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote:
>  > > > >> [root@dom0test ~]# cat /sys/hypervisor/properties/capabilities
>  > > > >> cat: /sys/hypervisor/properties/capabilities: No such file or
> directory
>  > > > >>
>  > > > > 
>  > > > > [root@dom0test ~]# ls -la /sys/hypervisor
>  > > > > ls: cannot access /sys/hypervisor: No such file or directory
>  > > > > 
>  > > > > 
>  > > > 
>  > > > Hmm, well that will do it. Libvirt capabilities are what tell user apps
>  > > > what types of domains can be installed, and generating xen capabilities
>  > > > is largely dependent on the above paths. Not too sure what to do from
> here.
>  > > > 
>  > > 
>  > > Ok.
>  > > 
>  > > I'll try asking what's the thing with that.. if it's still missing,
> or is it
>  > > deprecated or something..
>  > > 
>  > 
>  > Ok, it seems that /sys/hypervisor feature is not yet implemented in pv_ops
>  > dom0 kernel.
>  > 
>  > There's a patch somewhere in Redhat's old dom0 repository.. Jeremy is
> trying
>  > to find that. 
>  
>  
>  If this patch gets rejected for whatever reason, let me know, becasue we
>  can possibly switch libvirt over to making a direct hypercall to fetch
>  this information.
>   
Yep. I will.

The patch seems to be here:
http://git.et.redhat.com/?p=linux-2.6-dom0-pvops.git;a=commit;h=7aa79a560...

-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Mon, Mar 09, 2009 at 02:24:04PM +0200, Pasi Kärkkäinen wrote:
>  On Mon, Mar 09, 2009 at 10:39:29AM +0000, Daniel P. Berrange wrote:
>  > On Sun, Mar 08, 2009 at 09:23:10PM +0200, Pasi K?rkk?inen wrote:
>  > > On Sat, Mar 07, 2009 at 09:37:25PM +0200, Pasi Kärkkäinen wrote:
>  > > > On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote:
>  > > > > >> [root@dom0test ~]# cat
> /sys/hypervisor/properties/capabilities
>  > > > > >> cat: /sys/hypervisor/properties/capabilities: No such file
> or directory
>  > > > > >>
>  > > > > > 
>  > > > > > [root@dom0test ~]# ls -la /sys/hypervisor
>  > > > > > ls: cannot access /sys/hypervisor: No such file or directory
>  > > > > > 
>  > > > > > 
>  > > > > 
>  > > > > Hmm, well that will do it. Libvirt capabilities are what tell user
> apps
>  > > > > what types of domains can be installed, and generating xen
> capabilities
>  > > > > is largely dependent on the above paths. Not too sure what to do from
> here.
>  > > > > 
>  > > > 
>  > > > Ok.
>  > > > 
>  > > > I'll try asking what's the thing with that.. if it's still
> missing, or is it
>  > > > deprecated or something..
>  > > > 
>  > > 
>  > > Ok, it seems that /sys/hypervisor feature is not yet implemented in pv_ops
>  > > dom0 kernel.
>  > > 
>  > > There's a patch somewhere in Redhat's old dom0 repository.. Jeremy is
> trying
>  > > to find that. 
>  > 
>  > 
>  > If this patch gets rejected for whatever reason, let me know, becasue we
>  > can possibly switch libvirt over to making a direct hypercall to fetch
>  > this information.
>  > 
>  
>  Yep. I will.
>  
>  The patch seems to be here:
>
> http://git.et.redhat.com/?p=linux-2.6-dom0-pvops.git;a=commit;h=7aa79a560...
>   
And now this feature is committed to pv_ops kernel git tree:
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=834bf...

ATM this fix is needed to compile the kernel with /sys/hypervisor support patch:
http://lists.xensource.com/archives/html/xen-devel/2009-03/msg00699.html

I compiled a custom kernel with the patch included, and now:

[root@dom0test ~]# cat /sys/hypervisor/properties/capabilities 
xen-3.0-x86_32p 

But Fedora 10 domU installation still fails:

[root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l
"ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"


Starting install...
Retrieving file .treeinfo...                                             | 1.1 kB    
00:00     
Retrieving file vmlinuz-PAE...                                           | 2.5 MB    
00:01     
Retrieving file initrd-PAE.img...                                        |  16 MB    
00:10     
XML description for failed to build sexpr is not well formed or invalid
Domain installation may not have been
 successful.  If it was, you can restart your domain
 by running 'virsh start vm01'; otherwise, please
 restart your installation.
ERROR    XML description for failed to build sexpr is not well formed or invalid
Traceback (most recent call last):
  File "/usr/sbin/virt-install", line 692, in <module>
    main()
  File "/usr/sbin/virt-install", line 632, in main
    dom = guest.start_install(conscb, progresscb, wait=(not wait))
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 732, in
start_install
    return self._do_install(consolecb, meter, removeOld, wait)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 767, in
_do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib/python2.5/site-packages/libvirt.py", line 915, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: XML description for failed to build sexpr is not well formed or invalid


-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Daniel P. Berrange]

On Wed, Mar 11, 2009 at 07:56:10PM +0200, Pasi K?rkk?inen wrote:
>  But Fedora 10 domU installation still fails:
>  
>  [root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l
>
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  
>  
>  Starting install...
>  Retrieving file .treeinfo...                                             | 1.1 kB    
> 00:00     
>  Retrieving file vmlinuz-PAE...                                           | 2.5 MB    
> 00:01     
>  Retrieving file initrd-PAE.img...                                        |  16 MB    
> 00:10     
>  XML description for failed to build sexpr is not well formed or invalid
>  Domain installation may not have been
>   successful.  If it was, you can restart your domain
>   by running 'virsh start vm01'; otherwise, please
>   restart your installation.
>  ERROR    XML description for failed to build sexpr is not well formed or invalid 

Now this one sounds like a genuine libvirt or virt-install bug !

Can you re-run with --debug, and file a BZ with the information  so we can
track it formally.

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 :|

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Wed, Mar 11, 2009 at 05:59:01PM +0000, Daniel P. Berrange wrote:
>  On Wed, Mar 11, 2009 at 07:56:10PM +0200, Pasi K?rkk?inen wrote:
>  > But Fedora 10 domU installation still fails:
>  > 
>  > [root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p
> -l
>  >
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  > 
>  > 
>  > Starting install...
>  > Retrieving file .treeinfo...                                             | 1.1 kB   
>  00:00     
>  > Retrieving file vmlinuz-PAE...                                           | 2.5 MB   
>  00:01     
>  > Retrieving file initrd-PAE.img...                                        |  16 MB   
>  00:10     
>  > XML description for failed to build sexpr is not well formed or invalid
>  > Domain installation may not have been
>  >  successful.  If it was, you can restart your domain
>  >  by running 'virsh start vm01'; otherwise, please
>  >  restart your installation.
>  > ERROR    XML description for failed to build sexpr is not well formed or invalid
>  
>  
>  Now this one sounds like a genuine libvirt or virt-install bug !
>  
>  Can you re-run with --debug, and file a BZ with the information  so we can
>  track it formally.
>   
Ok. Will do. 

Here's the --debug info aswell:

[root@dom0test ~]# virt-install --debug -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc
-p -l
"ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
Wed, 11 Mar 2009 21:58:52 DEBUG    Using libvirt URI connect 'xen'
Wed, 11 Mar 2009 21:58:52 WARNING  Non-error from libvirt: 'Failed to find the
network: Is the daemon running ?'
Wed, 11 Mar 2009 21:58:52 DEBUG    Requesting virt method 'xen'
Wed, 11 Mar 2009 21:58:52 DEBUG    Received virt method 'xen'
Wed, 11 Mar 2009 21:58:52 DEBUG    Hypervisor type is 'xen'
Wed, 11 Mar 2009 21:58:52 DEBUG    Using self.path for VirtualDisk.
Wed, 11 Mar 2009 21:58:52 DEBUG    VirtualDisk storage exists.
Wed, 11 Mar 2009 21:58:52 DEBUG    Detected storage as type 'block'
Wed, 11 Mar 2009 21:58:52 DEBUG    DistroInstaller location is a network source.

Starting install...
Wed, 11 Mar 2009 21:58:53 DEBUG    Attempting to detect distro:
Wed, 11 Mar 2009 21:58:53 DEBUG    Detected .treeinfo file
Wed, 11 Mar 2009 21:58:53 DEBUG    Fetching URI
ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/release...
Wed, 11 Mar 2009 21:58:53 DEBUG    Saved file to /var/lib/xen/virtinst-.treeinfo.rXElMi
Retrieving file .treeinfo...                                             | /1.1 kB    
00:00     
Wed, 11 Mar 2009 21:58:53 DEBUG    Fetching URI
ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/release...
Retrieving file vmlinuz-PAE...                                  1.2 MB/s | /2.0 MB    
00:00    
Wed, 11 Mar 2009 21:58:54 DEBUG    Saved file to /var/lib/xen/virtinst-vmlinuz-PAE.OgMr10
Retrieving file vmlinuz-PAE...                                           |  2.5 MB    
00:01     
Wed, 11 Mar 2009 21:58:54 DEBUG    Fetching URI
ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/release...
Retrieving file initrd-PAE.img...                               1.9 MB/s | 16 MB     00:07
    
Wed, 11 Mar 2009 21:59:02 DEBUG    Saved file to
/var/lib/xen/virtinst-initrd-PAE.img.aF3UYJ
Retrieving file initrd-PAE.img...                                        | 16 MB     00:07
    
Wed, 11 Mar 2009 21:59:02 DEBUG    Using self.path for VirtualDisk.
Wed, 11 Mar 2009 21:59:02 DEBUG    VirtualDisk storage exists.
Wed, 11 Mar 2009 21:59:02 DEBUG    Detected storage as type 'block'
Wed, 11 Mar 2009 21:59:02 DEBUG    Creating guest from '<domain
type='xen'>

  <name>vm01</name>
  <currentMemory>524288</currentMemory>
  <memory>524288</memory>
  <uuid>c2d3c368-245d-05bd-7772-e799f0e05194</uuid>
  <os>
    <type>linux</type>
    <kernel>/var/lib/xen/virtinst-vmlinuz-PAE.OgMr10</kernel>
    <initrd>/var/lib/xen/virtinst-initrd-PAE.img.aF3UYJ</initrd>
   
<cmdline>method=ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fe...
  </os>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>destroy</on_reboot>
  <on_crash>destroy</on_crash>
  <vcpu>1</vcpu>
  <devices>
    <disk type='block' device='disk'>
      <source dev='/dev/vg00/vm01'/>
      <target dev='xvda' bus='xen'/>
    </disk>
    <interface type='network'>
      <source network='default'/>
      <mac address='00:16:36:55:e7:dd'/>
    </interface>
    <input type='mouse' bus='xen'/>
    <graphics type='vnc' port='-1' keymap='fi'/>
  </devices>
</domain>
'
Wed, 11 Mar 2009 21:59:02 DEBUG    Removing /var/lib/xen/virtinst-vmlinuz-PAE.OgMr10
Wed, 11 Mar 2009 21:59:02 DEBUG    Removing /var/lib/xen/virtinst-initrd-PAE.img.aF3UYJ
XML description for failed to build sexpr is not well formed or invalid
Domain installation may not have been
 successful.  If it was, you can restart your domain
 by running 'virsh start vm01'; otherwise, please
 restart your installation.
Wed, 11 Mar 2009 21:59:02 ERROR    XML description for failed to build sexpr is not well
formed or invalid
Traceback (most recent call last):
  File "/usr/sbin/virt-install", line 692, in <module>
    main()
  File "/usr/sbin/virt-install", line 632, in main
    dom = guest.start_install(conscb, progresscb, wait=(not wait))
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 732, in
start_install
    return self._do_install(consolecb, meter, removeOld, wait)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 767, in
_do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib/python2.5/site-packages/libvirt.py", line 915, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: XML description for failed to build sexpr is not well formed or invalid


-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Wed, Mar 11, 2009 at 10:05:03PM +0200, Pasi Kärkkäinen wrote:
>  On Wed, Mar 11, 2009 at 05:59:01PM +0000, Daniel P. Berrange wrote:
>  > On Wed, Mar 11, 2009 at 07:56:10PM +0200, Pasi K?rkk?inen wrote:
>  > > But Fedora 10 domU installation still fails:
>  > > 
>  > > [root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01
> --vnc -p -l
>  > >
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  > > 
>  > > 
>  > > Starting install...
>  > > Retrieving file .treeinfo...                                             | 1.1
> kB     00:00     
>  > > Retrieving file vmlinuz-PAE...                                           | 2.5
> MB     00:01     
>  > > Retrieving file initrd-PAE.img...                                        |  16
> MB     00:10     
>  > > XML description for failed to build sexpr is not well formed or invalid
>  > > Domain installation may not have been
>  > >  successful.  If it was, you can restart your domain
>  > >  by running 'virsh start vm01'; otherwise, please
>  > >  restart your installation.
>  > > ERROR    XML description for failed to build sexpr is not well formed or
> invalid
>  > 
>  > 
>  > Now this one sounds like a genuine libvirt or virt-install bug !
>  > 
>  > Can you re-run with --debug, and file a BZ with the information  so we can
>  > track it formally.
>  > 
>  
>  Ok. Will do. 
>   
Now done: https://bugzilla.redhat.com/show_bug.cgi?id=489799

-- Pasi

[fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10

[Pasi Kärkkäinen]

On Wed, Mar 11, 2009 at 11:39:00PM +0200, Pasi Kärkkäinen wrote:
>  On Wed, Mar 11, 2009 at 10:05:03PM +0200, Pasi Kärkkäinen wrote:
>  > On Wed, Mar 11, 2009 at 05:59:01PM +0000, Daniel P. Berrange wrote:
>  > > On Wed, Mar 11, 2009 at 07:56:10PM +0200, Pasi K?rkk?inen wrote:
>  > > > But Fedora 10 domU installation still fails:
>  > > > 
>  > > > [root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01
> --vnc -p -l
>  > > >
> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os"
>  > > > 
>  > > > 
>  > > > Starting install...
>  > > > Retrieving file .treeinfo...                                             |
> 1.1 kB     00:00     
>  > > > Retrieving file vmlinuz-PAE...                                           |
> 2.5 MB     00:01     
>  > > > Retrieving file initrd-PAE.img...                                        |
>  16 MB     00:10     
>  > > > XML description for failed to build sexpr is not well formed or invalid
>  > > > Domain installation may not have been
>  > > >  successful.  If it was, you can restart your domain
>  > > >  by running 'virsh start vm01'; otherwise, please
>  > > >  restart your installation.
>  > > > ERROR    XML description for failed to build sexpr is not well formed or
> invalid
>  > > 
>  > > 
>  > > Now this one sounds like a genuine libvirt or virt-install bug !
>  > > 
>  > > Can you re-run with --debug, and file a BZ with the information  so we can
>  > > track it formally.
>  > > 
>  > 
>  > Ok. Will do. 
>  > 
>  
>  Now done: https://bugzilla.redhat.com/show_bug.cgi?id=489799
>   
Ok, this "XML description for failed to build sexpr" error was caused by
libvirtd not being 
started before running virt-install.

Now I got further but still some problems.. I'll open another thread about that :) 

Thanks for the help!

-- Pasi