pvops dom0 work roadmap

pvops dom0 work roadmap

[Jeremy Fitzhardinge]

Hi all,

I know I've been a bit quiet lately;  I've been working through a number
of relatively small but time-consuming bugs while trying to stabilize
rebase/master.

The plan is:

    * make sure rebase/master is fairly functional and somewhat stable
    * rename rebase/* to xen/*
    * use it as the baseline dom0 and domU kernel in xen-unstable

rebase/mster is currently up to 2.6.31-rc6, and I intend to track
mainline fairly closely (probably no more closely than the -rc level). 
It also has some new features:

    * better acpi power management (ported from 2.6.18)
    * MCE (also from 2.6.18)
    * microcode updater (I forget whether that's in xen-tip/master)

rebase/master is mostly working for me now, but I would be interested in
getting some more testing (both success and bug reports welcomed).  Once
it seems to work, I'll do the rename and we'll work from there.

What does this mean for you?

    * If you're itching to test something, test rebase/master
    * If you're doing some new development, base it on rebase/master (or
      if you don't have any strong dependencies on other Xen pieces,
      base it on mainline)
          o also, tell me if you're working on something, even if it
            isn't ready yet, so I know who's doing what

It would also useful to do regression testing on plain, unpatched,
mainline, to make sure that any real bugfixes get merged promptly.

Thanks,
    J

Re: pvops dom0 work roadmap

[Pasi Kärkkäinen]

On Tue, Aug 18, 2009 at 11:43:38AM -0700, Jeremy Fitzhardinge wrote:
> Hi all,
> 
> I know I've been a bit quiet lately;  I've been working through a number
> of relatively small but time-consuming bugs while trying to stabilize
> rebase/master.
> 
> The plan is:
> 
>     * make sure rebase/master is fairly functional and somewhat stable
>     * rename rebase/* to xen/*
>     * use it as the baseline dom0 and domU kernel in xen-unstable
> 
> rebase/mster is currently up to 2.6.31-rc6, and I intend to track
> mainline fairly closely (probably no more closely than the -rc level). 
> It also has some new features:
> 
>     * better acpi power management (ported from 2.6.18)
>     * MCE (also from 2.6.18)
>     * microcode updater (I forget whether that's in xen-tip/master)
> 
> rebase/master is mostly working for me now, but I would be interested in
> getting some more testing (both success and bug reports welcomed).  Once
> it seems to work, I'll do the rename and we'll work from there.
> 
> What does this mean for you?
> 
>     * If you're itching to test something, test rebase/master
>     * If you're doing some new development, base it on rebase/master (or
>       if you don't have any strong dependencies on other Xen pieces,
>       base it on mainline)
>           o also, tell me if you're working on something, even if it
>             isn't ready yet, so I know who's doing what
> 

I just built and booted the latest 2.6.31-rc6 based tree on Xen 3.4.1.
I'm using 32bit PAE dom0 (and Xen) as usual.

Seems to work. I'll play some more with it tomorrow, install new guests etc.

> It would also useful to do regression testing on plain, unpatched,
> mainline, to make sure that any real bugfixes get merged promptly.
> 

Same kernel also booted OK on baremetal without Xen.

-- Pasi

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/18/09 13:07, Pasi Kärkkäinen wrote:
> I just built and booted the latest 2.6.31-rc6 based tree on Xen 3.4.1.
> I'm using 32bit PAE dom0 (and Xen) as usual.
>
> Seems to work. I'll play some more with it tomorrow, install new guests etc.
>   

Thanks,

>> It would also useful to do regression testing on plain, unpatched,
>> mainline, to make sure that any real bugfixes get merged promptly.
>>
>>     
> Same kernel also booted OK on baremetal without Xen.
>   

That's useful to know, but I was referring to testing release 2.6.30.x
kernels as well, just to make sure they still work.

    J

Re: pvops dom0 work roadmap

[Pasi Kärkkäinen]

On Tue, Aug 18, 2009 at 01:12:10PM -0700, Jeremy Fitzhardinge wrote:
> On 08/18/09 13:07, Pasi Kärkkäinen wrote:
> > I just built and booted the latest 2.6.31-rc6 based tree on Xen 3.4.1.
> > I'm using 32bit PAE dom0 (and Xen) as usual.
> >
> > Seems to work. I'll play some more with it tomorrow, install new guests etc.
> >   
> 
> Thanks,
> 

Actually I already managed to try some PV guest installations using
virt-install. Both CentOS 5.3 and Fedora 11 PV domUs installed OK.

(There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when using
Xen 3.4, but after I got that patched it was all fine).


One thing I noticed though: pv_ops dom0 kernel won't 'poweroff'. 

Last lines of output on the console:

Halting system...
Power down.

But it doesn't power down.. this was under Xen 3.4.1.

> >> It would also useful to do regression testing on plain, unpatched,
> >> mainline, to make sure that any real bugfixes get merged promptly.
> >>
> >>     
> > Same kernel also booted OK on baremetal without Xen.
> >   
> 
> That's useful to know, but I was referring to testing release 2.6.30.x
> kernels as well, just to make sure they still work.
> 

Oh, OK. I'll try to test those aswell.

-- Pasi

Re: pvops dom0 work roadmap

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 613 bytes --]

>There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> using Xen 3.4, but after I got that patched it was all fine

If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.

Thanks.
Boris



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[-- Attachment #1.2: Type: text/html, Size: 761 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Pasi Kärkkäinen]

On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > using Xen 3.4, but after I got that patched it was all fine
> 
> If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> 

I grabbed Xen 3.4.1-1 src.rpm from:
http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/

and rebuilt that for F11.

The next problem was that libvirt package in Fedora 11 has a bug, which causes it
to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.

Patch for the libvirt bug is here:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0

Upcoming libvirt update for F11 will fix this. After manually applying that
patch and rebuilding libvirt I'm now able to successfully install new guests
using virt-install and connect to their console by virt-viewer.

-- Pasi

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 1713 bytes --]

Thanks for info
Boris

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 3:09 AM

On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > using Xen 3.4, but after I got that patched it was all fine
> 
> If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> 

I grabbed Xen 3.4.1-1 src.rpm from:
http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/

and rebuilt that for F11.

The next problem was that libvirt package in Fedora 11 has a bug, which causes it
to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.

Patch for the libvirt bug is here:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0

Upcoming libvirt update for F11 will fix this. After manually applying that
patch and rebuilding libvirt I'm now able to successfully install new guests
using virt-install and connect to their console by virt-viewer.

-- Pasi

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 2507 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 3810 bytes --]

Pasi,

I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.

Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
and installed (pretty recent - 08/10/2009) :-

yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
libvirt-client-0.7.0-3.fc11.x86_64.rpm \
libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
libvirt-python-0.7.0-3.fc11.x86_64.rpm \
python-virtinst-0.500.0-1.fc11.noarch.rpm \
virt-manager-0.8.0-1.fc11.noarch.rpm \
virt-viewer-0.2.0-1.fc11.x86_64.rpm

[root@ServerXen341F Download]# rpm -qa|grep virt
libvirt-0.7.0-3.fc11.x86_64
libvirt-devel-0.7.0-3.fc11.x86_64
python-virtinst-0.500.0-1.fc11.noarch
virt-manager-0.8.0-1.fc11.noarch
virt-viewer-0.2.0-1.fc11.x86_64
libvirt-python-0.7.0-3.fc11.x86_64
libvirt-client-0.7.0-3.fc11.x86_64

Then i was able to connect to xend via virt-manager and attempted to start building
OSOL HVM. Got an error at startup:-

Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
    return self._do_install(consolecb, meter, removeOld, wait)
  File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: Domain not found: xenUnifiedDomainLookupByName

Please advise , how to escalate it to Fedora's people ?

Boris.
P.S. Usually i installed libvirt stuff :-

# yum install libvirt libvirt-python python-virtinst \

virt-manager virt-viewer

To apply patch manually i need a kind of libvirt.src.rpm.
I don't track Fedora so close to be aware of this.
'

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 3:09 AM

On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > using Xen 3.4, but after I got that patched it was all fine
> 
> If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> 

I grabbed Xen 3.4.1-1 src.rpm from:
http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/

and rebuilt that for F11.

The next problem was that libvirt package in Fedora 11 has a bug, which causes it
to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.

Patch for the libvirt bug is here:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0

Upcoming libvirt update for F11 will fix this. After manually applying that
patch and rebuilding libvirt I'm now able to successfully install new guests
using virt-install and connect to their console by virt-viewer.

-- Pasi

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 4831 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 4903 bytes --]

At page http://markmc.fedorapeople.org/virt-preview/f11/src/ :-

bochs-2.3.8-0.8.git04387139e3b.fc11.src.rpm 31-Jul-2009 15:39  3.9M  
libvirt-0.7.0-3.fc11.src.rpm                10-Aug-2009 10:34  7.6M  
python-virtinst-0.500.0-1.fc11.src.rpm      29-Jul-2009 13:39  453K  
qemu-0.10.91-0.5.rc1.fc11.src.rpm           07-Aug-2009 09:51  4.2M  
virt-manager-0.8.0-1.fc11.src.rpm           29-Jul-2009 13:40  2.0M  
virt-viewer-0.2.0-1.fc11.src.rpm            29-Jul-2009 14:56  327K  

I believe qemu installation was skipped

Boris.
--- On Wed, 8/19/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 5:54 AM

Pasi,

I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.

Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
and installed (pretty recent - 08/10/2009) :-

yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
libvirt-client-0.7.0-3.fc11.x86_64.rpm \
libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
libvirt-python-0.7.0-3.fc11.x86_64.rpm \
python-virtinst-0.500.0-1.fc11.noarch.rpm \
virt-manager-0.8.0-1.fc11.noarch.rpm \
virt-viewer-0.2.0-1.fc11.x86_64.rpm

[root@ServerXen341F Download]# rpm -qa|grep
 virt
libvirt-0.7.0-3.fc11.x86_64
libvirt-devel-0.7.0-3.fc11.x86_64
python-virtinst-0.500.0-1.fc11.noarch
virt-manager-0.8.0-1.fc11.noarch
virt-viewer-0.2.0-1.fc11.x86_64
libvirt-python-0.7.0-3.fc11.x86_64
libvirt-client-0.7.0-3.fc11.x86_64

Then i was able to connect to xend via virt-manager and attempted to start building
OSOL HVM. Got an error at startup:-

Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
    return self._do_install(consolecb, meter, removeOld, wait)
  File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in
 _do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: Domain not found: xenUnifiedDomainLookupByName

Please advise , how to escalate it to Fedora's people ?

Boris.
P.S. Usually i installed libvirt stuff :-

# yum install libvirt libvirt-python python-virtinst \

virt-manager virt-viewer

To apply patch manually i need a kind of libvirt.src.rpm.
I don't track Fedora so close to be aware of this.
'

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 3:09 AM

On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > using Xen 3.4, but after I got that patched it was all fine
> 
> If it's possible to share your experience , i
 wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> 

I grabbed Xen 3.4.1-1 src.rpm from:
http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/

and rebuilt that for F11.

The next problem was that libvirt package in Fedora 11 has a bug, which causes it
to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.

Patch for the libvirt bug is here:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0

Upcoming
 libvirt update for F11 will fix this. After manually applying that
patch and rebuilding libvirt I'm now able to successfully install new guests
using virt-install and connect to their console by virt-viewer.

-- Pasi

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      
-----Inline Attachment Follows-----

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 7254 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Pasi Kärkkäinen]

On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> Pasi,
> 
> I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> 
> Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> and installed (pretty recent - 08/10/2009) :-
> 
> yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> python-virtinst-0.500.0-1.fc11.noarch.rpm \
> virt-manager-0.8.0-1.fc11.noarch.rpm \
> virt-viewer-0.2.0-1.fc11.x86_64.rpm
> 
> [root@ServerXen341F Download]# rpm -qa|grep virt
> libvirt-0.7.0-3.fc11.x86_64
> libvirt-devel-0.7.0-3.fc11.x86_64
> python-virtinst-0.500.0-1.fc11.noarch
> virt-manager-0.8.0-1.fc11.noarch
> virt-viewer-0.2.0-1.fc11.x86_64
> libvirt-python-0.7.0-3.fc11.x86_64
> libvirt-client-0.7.0-3.fc11.x86_64
> 
> Then i was able to connect to xend via virt-manager and attempted to start building
> OSOL HVM. Got an error at startup:-
> 
> Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
>     dom = guest.start_install(False, meter = meter)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
>     return self._do_install(consolecb, meter, removeOld, wait)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
>     self.domain = self.conn.createLinux(install_xml, 0)
>   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
>     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> libvirtError: Domain not found: xenUnifiedDomainLookupByName
> 
> Please advise , how to escalate it to Fedora's people ?
> 

I think you should post to fedora-xen@redhat.com and possibly 
CC fedora-virt@redhat.com.

> Boris.
> P.S. Usually i installed libvirt stuff :-
> 
> # yum install libvirt libvirt-python python-virtinst \
> 
> virt-manager virt-viewer
> 
> To apply patch manually i need a kind of libvirt.src.rpm.
> I don't track Fedora so close to be aware of this.
> '


I was using the default libvirt from F11, but I manually added the bugfix patch:

- Download libvirt src.rpm:
  ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm

- install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"

- Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
  http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d

- Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
  patches are added. You need to add one line to two different places.

- Run "rpmbuild -bb libvirt.spec"

- Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/

-- Pasi


> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 3:09 AM
> 
> On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > using Xen 3.4, but after I got that patched it was all fine
> > 
> > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > 
> 
> I grabbed Xen 3.4.1-1 src.rpm from:
> http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> 
> and rebuilt that for F11.
> 
> The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> 
> Patch for the libvirt bug is here:
> http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> 
> Upcoming libvirt update for F11 will fix this. After manually applying that
> patch and rebuilding libvirt I'm now able to successfully install new guests
> using virt-install and connect to their console by virt-viewer.
> 
> -- Pasi
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 6436 bytes --]

Pasi,

Thanks  a lot a lot for your support.

  I was able  to reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
  I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. F11 PVM been created via virt-manager, cannot be , actually,
managed either via virt-manager or from command line.

# xm start VMF11

moves it to paused state and resuming shows :-

[root@ServerXen341F boris]# xm list
Name                                          ID   Mem VCPUs      State   Time(s)
Domain-0                                    0    6034     2     r-----    574.9
VMF11                                         3    2048     0     ------      0.0

Attempt to create HVM crashes immediately.

Boris.

P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
and installed glibc-devel.i586 for rpmbuild.

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 6:27 AM

On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> Pasi,
> 
> I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> 
> Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> and installed (pretty recent - 08/10/2009) :-
> 
> yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> python-virtinst-0.500.0-1.fc11.noarch.rpm \
> virt-manager-0.8.0-1.fc11.noarch.rpm \
> virt-viewer-0.2.0-1.fc11.x86_64.rpm
> 
> [root@ServerXen341F Download]# rpm -qa|grep virt
> libvirt-0.7.0-3.fc11.x86_64
> libvirt-devel-0.7.0-3.fc11.x86_64
> python-virtinst-0.500.0-1.fc11.noarch
> virt-manager-0.8.0-1.fc11.noarch
> virt-viewer-0.2.0-1.fc11.x86_64
> libvirt-python-0.7.0-3.fc11.x86_64
> libvirt-client-0.7.0-3.fc11.x86_64
> 
> Then i was able to connect to xend via virt-manager and attempted to start building
> OSOL HVM. Got an error at startup:-
> 
> Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
>     dom = guest.start_install(False, meter = meter)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
>     return self._do_install(consolecb, meter, removeOld, wait)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
>     self.domain = self.conn.createLinux(install_xml, 0)
>   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
>     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> libvirtError: Domain not found: xenUnifiedDomainLookupByName
> 
> Please advise , how to escalate it to Fedora's people ?
> 

I think you should post to fedora-xen@redhat.com and possibly 
CC fedora-virt@redhat.com.

> Boris.
> P.S. Usually i installed libvirt stuff :-
> 
> # yum install libvirt libvirt-python python-virtinst \
> 
> virt-manager virt-viewer
> 
> To apply patch manually i need a kind of libvirt.src.rpm.
> I don't track Fedora so close to be aware of this.
> '


I was using the default libvirt from F11, but I manually added the bugfix patch:

- Download libvirt src.rpm:
  ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm

- install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"

- Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
  http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d

- Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
  patches are added. You need to add one line to two different places.

- Run "rpmbuild -bb libvirt.spec"

- Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/

-- Pasi


> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 3:09 AM
> 
> On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > using Xen 3.4, but after I got that patched it was all fine
> > 
> > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > 
> 
> I grabbed Xen 3.4.1-1 src.rpm from:
> http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> 
> and rebuilt that for F11.
> 
> The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> 
> Patch for the libvirt bug is here:
> http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> 
> Upcoming libvirt update for F11 will fix this. After manually applying that
> patch and rebuilding libvirt I'm now able to successfully install new guests
> using virt-install and connect to their console by virt-viewer.
> 
> -- Pasi
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 9951 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Pasi Kärkkäinen]

On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> Pasi,
> 
> Thanks  a lot a lot for your support.
> 
>   I was able  to reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
>   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. 
> F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
> 
> # xm start VMF11
> 
> moves it to paused state and resuming shows :-
> 
> [root@ServerXen341F boris]# xm list
> Name                                          ID   Mem VCPUs      State   Time(s)
> Domain-0                                    0    6034     2     r-----    574.9
> VMF11                                         3    2048     0     ------      0.0
> 

What do you have in "xm log" ? Is the last line about running pygrub?

I'm seeing an issue with F11 domU where the domU grub.conf contains
timeout=0 and that causes pygrub to get stuck and thus prevents the domU
from starting.. changing to timeout=5 fixes the problem. 

I'm going to debug pygrub later today.. I believe it's a bug in pygrub.

> Attempt to create HVM crashes immediately.
> 

I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.

-- Pasi

> Boris.
> 
> P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> and installed glibc-devel.i586 for rpmbuild.
> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 6:27 AM
> 
> On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > Pasi,
> > 
> > I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> > 
> > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > and installed (pretty recent - 08/10/2009) :-
> > 
> > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> > 
> > [root@ServerXen341F Download]# rpm -qa|grep virt
> > libvirt-0.7.0-3.fc11.x86_64
> > libvirt-devel-0.7.0-3.fc11.x86_64
> > python-virtinst-0.500.0-1.fc11.noarch
> > virt-manager-0.8.0-1.fc11.noarch
> > virt-viewer-0.2.0-1.fc11.x86_64
> > libvirt-python-0.7.0-3.fc11.x86_64
> > libvirt-client-0.7.0-3.fc11.x86_64
> > 
> > Then i was able to connect to xend via virt-manager and attempted to start building
> > OSOL HVM. Got an error at startup:-
> > 
> > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> >     dom = guest.start_install(False, meter = meter)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> >     return self._do_install(consolecb, meter, removeOld, wait)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> >     self.domain = self.conn.createLinux(install_xml, 0)
> >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> > 
> > Please advise , how to escalate it to Fedora's people ?
> > 
> 
> I think you should post to fedora-xen@redhat.com and possibly 
> CC fedora-virt@redhat.com.
> 
> > Boris.
> > P.S. Usually i installed libvirt stuff :-
> > 
> > # yum install libvirt libvirt-python python-virtinst \
> > 
> > virt-manager virt-viewer
> > 
> > To apply patch manually i need a kind of libvirt.src.rpm.
> > I don't track Fedora so close to be aware of this.
> > '
> 
> 
> I was using the default libvirt from F11, but I manually added the bugfix patch:
> 
> - Download libvirt src.rpm:
>   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
> 
> - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
> 
> - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
>   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
> 
> - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
>   patches are added. You need to add one line to two different places.
> 
> - Run "rpmbuild -bb libvirt.spec"
> 
> - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
> 
> -- Pasi
> 
> 
> > 
> > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > 
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Wednesday, August 19, 2009, 3:09 AM
> > 
> > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > > using Xen 3.4, but after I got that patched it was all fine
> > > 
> > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > > 
> > 
> > I grabbed Xen 3.4.1-1 src.rpm from:
> > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> > 
> > and rebuilt that for F11.
> > 
> > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> > 
> > Patch for the libvirt bug is here:
> > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> > 
> > Upcoming libvirt update for F11 will fix this. After manually applying that
> > patch and rebuilding libvirt I'm now able to successfully install new guests
> > using virt-install and connect to their console by virt-viewer.
> > 
> > -- Pasi
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> > 
> >       
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 10968 bytes --]

> What do you have in "xm log" ? Is the last line about running pygrub?

Here we go 

[2009-08-19 16:28:06 2124] DEBUG (SrvDomain:76) Starting domain VMF11 False
[2009-08-19 16:28:06 2124] DEBUG (XendDomainInfo:2296) XendDomainInfo.constructDomain
[2009-08-19 16:28:06 2124] DEBUG (balloon:166) Balloon: 132448 KiB free; need 4096; done.
[2009-08-19 16:28:06 2124] DEBUG (XendDomain:452) Adding Domain: 1
[2009-08-19 16:28:06 2124] DEBUG (XendDomainInfo:2497) XendDomainInfo.initDomain: 1 256
[2009-08-19 16:28:06 3281] DEBUG (XendBootloader:113) Launching bootloader as [\047/usr/bin/pygrub\047, \047--output=/var/run/xend/boot/xenbl.4360\047, \047/dev/sda12\047].
[2009-08-19 16:28:47 2124] INFO (XendDomain:1180) Domain VMF11 (1) unpaused.
[2009-08-19 16:29:24 2124] DEBUG (XendDomainInfo:2724) XendDomainInfo.destroy: domid=1
[2009-08-19 16:29:24 2124] DEBUG (XendDomainInfo:2204) No device model
[2009-08-19 16:29:24 2124] DEBUG (XendDomainInfo:2206) Releasing devices
[2009-08-19 16:29:24 2124] ERROR (XendBootloader:207) Domain was died while the bootloader was running.
[2009-08-19 16:29:24 2124] ERROR (XendDomainInfo:476) VM start failed
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 456, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2499, in _initDomain
    self._configureBootloader()
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2919, in _configureBootloader
    bootloader_args, kernel, ramdisk, args)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py", line 208, in bootloader
    raise VmError, msg
VmError: Domain was died while the bootloader was running.
[2009-08-19 16:29:24 2124] ERROR (SrvBase:88) Request start failed.
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/web/SrvBase.py", line 85, in perform
    return op_method(op, req)
  File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDomain.py", line 77, in op_start
    return self.xd.domain_start(self.dom.getName(), paused)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 1039, in domain_start
    dominfo.start(is_managed = True)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 456, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2499, in _initDomain
    self._configureBootloader()
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2919, in _configureBootloader
    bootloader_args, kernel, ramdisk, args)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py", line 208, in bootloader
    raise VmError, msg
VmError: Domain was died while the bootloader was running.

Boris.

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 8:37 AM

On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> Pasi,
> 
> Thanks  a lot a lot for your support.
> 
>   I was able  to reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
>   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. 
> F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
> 
> # xm start VMF11
> 
> moves it to paused state and resuming shows :-
> 
> [root@ServerXen341F boris]# xm list
> Name                                          ID   Mem VCPUs      State   Time(s)
> Domain-0                                    0    6034     2     r-----    574.9
> VMF11                                         3    2048     0     ------      0.0
> 

What do you have in "xm log" ? Is the last line about running pygrub?

I'm seeing an issue with F11 domU where the domU grub.conf contains
timeout=0 and that causes pygrub to get stuck and thus prevents the domU
from starting.. changing to timeout=5 fixes the problem. 

I'm going to debug pygrub later today.. I believe it's a bug in pygrub.

> Attempt to create HVM crashes immediately.
> 

I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.

-- Pasi

> Boris.
> 
> P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> and installed glibc-devel.i586 for rpmbuild.
> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 6:27 AM
> 
> On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > Pasi,
> > 
> > I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> > 
> > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > and installed (pretty recent - 08/10/2009) :-
> > 
> > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> > 
> > [root@ServerXen341F Download]# rpm -qa|grep virt
> > libvirt-0.7.0-3.fc11.x86_64
> > libvirt-devel-0.7.0-3.fc11.x86_64
> > python-virtinst-0.500.0-1.fc11.noarch
> > virt-manager-0.8.0-1.fc11.noarch
> > virt-viewer-0.2.0-1.fc11.x86_64
> > libvirt-python-0.7.0-3.fc11.x86_64
> > libvirt-client-0.7.0-3.fc11.x86_64
> > 
> > Then i was able to connect to xend via virt-manager and attempted to start building
> > OSOL HVM. Got an error at startup:-
> > 
> > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> >     dom = guest.start_install(False, meter = meter)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> >     return self._do_install(consolecb, meter, removeOld, wait)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> >     self.domain = self.conn.createLinux(install_xml, 0)
> >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> > 
> > Please advise , how to escalate it to Fedora's people ?
> > 
> 
> I think you should post to fedora-xen@redhat.com and possibly 
> CC fedora-virt@redhat.com.
> 
> > Boris.
> > P.S. Usually i installed libvirt stuff :-
> > 
> > # yum install libvirt libvirt-python python-virtinst \
> > 
> > virt-manager virt-viewer
> > 
> > To apply patch manually i need a kind of libvirt.src.rpm.
> > I don't track Fedora so close to be aware of this.
> > '
> 
> 
> I was using the default libvirt from F11, but I manually added the bugfix patch:
> 
> - Download libvirt src.rpm:
>   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
> 
> - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
> 
> - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
>   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
> 
> - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
>   patches are added. You need to add one line to two different places.
> 
> - Run "rpmbuild -bb libvirt.spec"
> 
> - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
> 
> -- Pasi
> 
> 
> > 
> > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > 
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Wednesday, August 19, 2009, 3:09 AM
> > 
> > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > > using Xen 3.4, but after I got that patched it was all fine
> > > 
> > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > > 
> > 
> > I grabbed Xen 3.4.1-1 src.rpm from:
> > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> > 
> > and rebuilt that for F11.
> > 
> > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> > 
> > Patch for the libvirt bug is here:
> > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> > 
> > Upcoming libvirt update for F11 will fix this. After manually applying that
> > patch and rebuilding libvirt I'm now able to successfully install new guests
> > using virt-install and connect to their console by virt-viewer.
> > 
> > -- Pasi
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> > 
> >       
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 15953 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 7920 bytes --]

Yes, Pasi

 I've loaded F11 DomU manually and changed timeout=5 then shutdown DomU and started smoothly via virt-manager.

Thanks again.
Boris.

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 8:37 AM

On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> Pasi,
> 
> Thanks  a lot a lot for your support.
> 
>   I was able  to reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
>   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. 
> F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
> 
> # xm start VMF11
> 
> moves it to paused state and resuming shows :-
> 
> [root@ServerXen341F boris]# xm list
> Name                                          ID   Mem VCPUs      State   Time(s)
> Domain-0                                    0    6034     2     r-----    574.9
> VMF11                                         3    2048     0     ------      0.0
> 

What do you have in "xm log" ? Is the last line about running pygrub?

I'm seeing an issue with F11 domU where the domU grub.conf contains
timeout=0 and that causes pygrub to get stuck and thus prevents the domU
from starting.. changing to timeout=5 fixes the problem. 

I'm going to debug pygrub later today.. I believe it's a bug in pygrub.

> Attempt to create HVM crashes immediately.
> 

I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.

-- Pasi

> Boris.
> 
> P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> and installed glibc-devel.i586 for rpmbuild.
> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 6:27 AM
> 
> On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > Pasi,
> > 
> > I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> > 
> > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > and installed (pretty recent - 08/10/2009) :-
> > 
> > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> > 
> > [root@ServerXen341F Download]# rpm -qa|grep virt
> > libvirt-0.7.0-3.fc11.x86_64
> > libvirt-devel-0.7.0-3.fc11.x86_64
> > python-virtinst-0.500.0-1.fc11.noarch
> > virt-manager-0.8.0-1.fc11.noarch
> > virt-viewer-0.2.0-1.fc11.x86_64
> > libvirt-python-0.7.0-3.fc11.x86_64
> > libvirt-client-0.7.0-3.fc11.x86_64
> > 
> > Then i was able to connect to xend via virt-manager and attempted to start building
> > OSOL HVM. Got an error at startup:-
> > 
> > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> >     dom = guest.start_install(False, meter = meter)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> >     return self._do_install(consolecb, meter, removeOld, wait)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> >     self.domain = self.conn.createLinux(install_xml, 0)
> >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> > 
> > Please advise , how to escalate it to Fedora's people ?
> > 
> 
> I think you should post to fedora-xen@redhat.com and possibly 
> CC fedora-virt@redhat.com.
> 
> > Boris.
> > P.S. Usually i installed libvirt stuff :-
> > 
> > # yum install libvirt libvirt-python python-virtinst \
> > 
> > virt-manager virt-viewer
> > 
> > To apply patch manually i need a kind of libvirt.src.rpm.
> > I don't track Fedora so close to be aware of this.
> > '
> 
> 
> I was using the default libvirt from F11, but I manually added the bugfix patch:
> 
> - Download libvirt src.rpm:
>   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
> 
> - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
> 
> - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
>   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
> 
> - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
>   patches are added. You need to add one line to two different places.
> 
> - Run "rpmbuild -bb libvirt.spec"
> 
> - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
> 
> -- Pasi
> 
> 
> > 
> > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > 
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Wednesday, August 19, 2009, 3:09 AM
> > 
> > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > > using Xen 3.4, but after I got that patched it was all fine
> > > 
> > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > > 
> > 
> > I grabbed Xen 3.4.1-1 src.rpm from:
> > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> > 
> > and rebuilt that for F11.
> > 
> > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> > 
> > Patch for the libvirt bug is here:
> > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> > 
> > Upcoming libvirt update for F11 will fix this. After manually applying that
> > patch and rebuilding libvirt I'm now able to successfully install new guests
> > using virt-install and connect to their console by virt-viewer.
> > 
> > -- Pasi
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> > 
> >       
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 12555 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 9506 bytes --]

Attempt to create HVM via virt-manager aborts with message:-

Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 1501, in do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install
    return self._do_install(consolecb, meter, removeOld, wait)
  File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 974, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: Domain not found: xenUnifiedDomainLookupByName

Boris

--- On Wed, 8/19/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 9:26 AM

Yes, Pasi

 I've loaded F11 DomU manually and changed timeout=5 then shutdown DomU and started smoothly via virt-manager.

Thanks again.
Boris.

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 8:37 AM

On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> Pasi,
> 
> Thanks  a lot a lot for your support.
> 
>   I was able  to
 reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
>   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. 
> F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
> 
> # xm start VMF11
> 
> moves it to paused state and resuming shows :-
> 
> [root@ServerXen341F boris]# xm list
> Name                                          ID   Mem VCPUs      State   Time(s)
>
 Domain-0                                    0    6034     2     r-----    574.9
> VMF11                                         3    2048     0     ------      0.0
> 

What do you have in "xm log" ? Is the last line about running pygrub?

I'm seeing an issue with F11 domU where the domU grub.conf contains
timeout=0 and that causes pygrub to get stuck and thus prevents the domU
from starting.. changing to timeout=5 fixes the
 problem. 

I'm going to debug pygrub later today.. I believe it's a bug in pygrub.

> Attempt to create HVM crashes immediately.
> 

I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.

-- Pasi

> Boris.
> 
> P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> and installed glibc-devel.i586 for rpmbuild.
> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc:
 "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 6:27 AM
> 
> On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > Pasi,
> > 
> > I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> > 
> > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > and installed (pretty recent - 08/10/2009) :-
> > 
> > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
>
 > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> > 
> > [root@ServerXen341F Download]# rpm -qa|grep virt
> > libvirt-0.7.0-3.fc11.x86_64
> > libvirt-devel-0.7.0-3.fc11.x86_64
> > python-virtinst-0.500.0-1.fc11.noarch
> > virt-manager-0.8.0-1.fc11.noarch
> > virt-viewer-0.2.0-1.fc11.x86_64
> > libvirt-python-0.7.0-3.fc11.x86_64
> > libvirt-client-0.7.0-3.fc11.x86_64
> > 
> > Then i was able to connect to xend via virt-manager and attempted to start building
> > OSOL HVM. Got an error at startup:-
> > 
> > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > Traceback (most recent call last):
> >
   File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> >     dom = guest.start_install(False, meter = meter)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> >     return self._do_install(consolecb, meter, removeOld, wait)
> >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> >     self.domain = self.conn.createLinux(install_xml, 0)
> >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> > 
> > Please advise , how to escalate it to Fedora's people ?
> > 
> 
> I think you should
 post to fedora-xen@redhat.com and possibly 
> CC fedora-virt@redhat.com.
> 
> > Boris.
> > P.S. Usually i installed libvirt stuff :-
> > 
> > # yum install libvirt libvirt-python python-virtinst \
> > 
> > virt-manager virt-viewer
> > 
> > To apply patch manually i need a kind of libvirt.src.rpm.
> > I don't track Fedora so close to be aware of this.
> > '
> 
> 
> I was using the default libvirt from F11, but I manually added the bugfix patch:
> 
> - Download libvirt src.rpm:
>   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
> 
> - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
> 
> - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
>   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
> 
> - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
>   patches are
 added. You need to add one line to two different places.
> 
> - Run "rpmbuild -bb libvirt.spec"
> 
> - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
> 
> -- Pasi
> 
> 
> > 
> > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > 
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Wednesday, August 19, 2009, 3:09 AM
> > 
> > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > > using Xen 3.4, but after I got that patched it was all fine
> > > 
> > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > > 
> > 
> > I grabbed Xen 3.4.1-1 src.rpm from:
> > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> > 
> > and rebuilt that for F11.
> > 
> > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> > 
> > Patch for the libvirt bug is here:
> > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> > 
> > Upcoming libvirt update for F11 will fix this. After manually applying that
> > patch and rebuilding libvirt I'm now able to successfully install new guests
> > using virt-install and connect to their console by virt-viewer.
> > 
> > -- Pasi
> >
 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> > 
> >       
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel





      
-----Inline Attachment Follows-----

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[-- Attachment #1.2: Type: text/html, Size: 14197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Pasi Kärkkäinen]

On Wed, Aug 19, 2009 at 06:35:40AM -0700, Boris Derzhavets wrote:
> Attempt to create HVM via virt-manager aborts with message:-
> 
> Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/create.py", line 1501, in do_install
>     dom = guest.start_install(False, meter = meter)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install
>     return self._do_install(consolecb, meter, removeOld, wait)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install
>     self.domain = self.conn.createLinux(install_xml, 0)
>   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 974, in createLinux
>     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> libvirtError: Domain not found: xenUnifiedDomainLookupByName
> 

This is getting offtopic for xen-devel .. these are issues with
libvirt/virt-tools/fedora and should be discussed on their mailinglists..

Please open a thread about that HVM problem on fedora-xen (and CC fedora-virt).

-- Pasi

> Boris
> 
> --- On Wed, 8/19/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
> 
> From: Boris Derzhavets <bderzhavets@yahoo.com>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Pasi Kärkkäinen" <pasik@iki.fi>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 9:26 AM
> 
> Yes, Pasi
> 
>  I've loaded F11 DomU manually and changed timeout=5 then shutdown DomU and started smoothly via virt-manager.
> 
> Thanks again.
> Boris.
> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 8:37 AM
> 
> On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> > Pasi,
> > 
> > Thanks  a lot a lot for your support.
> > 
> >   I was able  to
>  reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
> >   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. 
> > F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
> > 
> > # xm start VMF11
> > 
> > moves it to paused state and resuming shows :-
> > 
> > [root@ServerXen341F boris]# xm list
> > Name                                          ID   Mem VCPUs      State   Time(s)
> >
>  Domain-0                                    0    6034     2     r-----    574.9
> > VMF11                                         3    2048     0     ------      0.0
> > 
> 
> What do you have in "xm log" ? Is the last line about running pygrub?
> 
> I'm seeing an issue with F11 domU where the domU grub.conf contains
> timeout=0 and that causes pygrub to get stuck and thus prevents the domU
> from starting.. changing to timeout=5 fixes the
>  problem. 
> 
> I'm going to debug pygrub later today.. I believe it's a bug in pygrub.
> 
> > Attempt to create HVM crashes immediately.
> > 
> 
> I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.
> 
> -- Pasi
> 
> > Boris.
> > 
> > P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> > and installed glibc-devel.i586 for rpmbuild.
> > 
> > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > 
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > Cc:
>  "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Wednesday, August 19, 2009, 6:27 AM
> > 
> > On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > > Pasi,
> > > 
> > > I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> > > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> > > 
> > > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > > and installed (pretty recent - 08/10/2009) :-
> > > 
> > > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> > > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> >
>  > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> > > 
> > > [root@ServerXen341F Download]# rpm -qa|grep virt
> > > libvirt-0.7.0-3.fc11.x86_64
> > > libvirt-devel-0.7.0-3.fc11.x86_64
> > > python-virtinst-0.500.0-1.fc11.noarch
> > > virt-manager-0.8.0-1.fc11.noarch
> > > virt-viewer-0.2.0-1.fc11.x86_64
> > > libvirt-python-0.7.0-3.fc11.x86_64
> > > libvirt-client-0.7.0-3.fc11.x86_64
> > > 
> > > Then i was able to connect to xend via virt-manager and attempted to start building
> > > OSOL HVM. Got an error at startup:-
> > > 
> > > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > > Traceback (most recent call last):
> > >
>    File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> > >     dom = guest.start_install(False, meter = meter)
> > >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> > >     return self._do_install(consolecb, meter, removeOld, wait)
> > >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> > >     self.domain = self.conn.createLinux(install_xml, 0)
> > >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> > >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> > > 
> > > Please advise , how to escalate it to Fedora's people ?
> > > 
> > 
> > I think you should
>  post to fedora-xen@redhat.com and possibly 
> > CC fedora-virt@redhat.com.
> > 
> > > Boris.
> > > P.S. Usually i installed libvirt stuff :-
> > > 
> > > # yum install libvirt libvirt-python python-virtinst \
> > > 
> > > virt-manager virt-viewer
> > > 
> > > To apply patch manually i need a kind of libvirt.src.rpm.
> > > I don't track Fedora so close to be aware of this.
> > > '
> > 
> > 
> > I was using the default libvirt from F11, but I manually added the bugfix patch:
> > 
> > - Download libvirt src.rpm:
> >   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
> > 
> > - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
> > 
> > - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
> >   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
> > 
> > - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
> >   patches are
>  added. You need to add one line to two different places.
> > 
> > - Run "rpmbuild -bb libvirt.spec"
> > 
> > - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
> > 
> > -- Pasi
> > 
> > 
> > > 
> > > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > > 
> > > From: Pasi Kärkkäinen <pasik@iki.fi>
> > > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > > Date: Wednesday, August 19, 2009, 3:09 AM
> > > 
> > > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > > > using Xen 3.4, but after I got that patched it was all fine
> > > > 
> > > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > > > 
> > > 
> > > I grabbed Xen 3.4.1-1 src.rpm from:
> > > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> > > 
> > > and rebuilt that for F11.
> > > 
> > > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> > > 
> > > Patch for the libvirt bug is here:
> > > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> > > 
> > > Upcoming libvirt update for F11 will fix this. After manually applying that
> > > patch and rebuilding libvirt I'm now able to successfully install new guests
> > > using virt-install and connect to their console by virt-viewer.
> > > 
> > > -- Pasi
> > >
>  
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> > > 
> > > 
> > > 
> > >       
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> > 
> >       
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
> 
> 
>       
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 11792 bytes --]

  Subscribed to both mailing lists and posted an extract from from xen-devel thread
Your's way to patching libvirt was chosen.

   Version of libvirt at  http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/  
doesn't seem clear to me. 
  Two qemu packages gets installed with Xen 3.4.1 and my original attempt seems
correct to me in meantime ( not to install qemu packages from link above).
 
 Both ways of obtain libvirt give same error attempting HVM DomUs creation.

 Version been built via http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/  
appears to be able to start PV DomU install via HTTP source, but every times fails
trying to mount /boot on /dev/xvda1 right after partitioning image device.
Patching old version does allow go through PV DomU install via HTTP source.


Thanks.
Boris.

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 10:32 AM

On Wed, Aug 19, 2009 at 06:35:40AM -0700, Boris Derzhavets wrote:
> Attempt to create HVM via virt-manager aborts with message:-
> 
> Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/create.py", line 1501, in do_install
>     dom = guest.start_install(False, meter = meter)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install
>     return self._do_install(consolecb, meter, removeOld, wait)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install
>     self.domain = self.conn.createLinux(install_xml, 0)
>   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 974, in createLinux
>     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> libvirtError: Domain not found: xenUnifiedDomainLookupByName
> 

This is getting offtopic for xen-devel .. these are issues with
libvirt/virt-tools/fedora and should be discussed on their mailinglists..

Please open a thread about that HVM problem on fedora-xen (and CC fedora-virt).

-- Pasi

> Boris
> 
> --- On Wed, 8/19/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
> 
> From: Boris Derzhavets <bderzhavets@yahoo.com>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Pasi Kärkkäinen" <pasik@iki.fi>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 9:26 AM
> 
> Yes, Pasi
> 
>  I've loaded F11 DomU manually and changed timeout=5 then shutdown DomU and started smoothly via virt-manager.
> 
> Thanks again.
> Boris.
> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 8:37 AM
> 
> On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> > Pasi,
> > 
> > Thanks  a lot a lot for your support.
> > 
> >   I was able  to
>  reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
> >   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. 
> > F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
> > 
> > # xm start VMF11
> > 
> > moves it to paused state and resuming shows :-
> > 
> > [root@ServerXen341F boris]# xm list
> > Name                                          ID   Mem VCPUs      State   Time(s)
> >
>  Domain-0                                    0    6034     2     r-----    574.9
> > VMF11                                         3    2048     0     ------      0.0
> > 
> 
> What do you have in "xm log" ? Is the last line about running pygrub?
> 
> I'm seeing an issue with F11 domU where the domU grub.conf contains
> timeout=0 and that causes pygrub to get stuck and thus prevents the domU
> from starting.. changing to timeout=5 fixes the
>  problem. 
> 
> I'm going to debug pygrub later today.. I believe it's a bug in pygrub.
> 
> > Attempt to create HVM crashes immediately.
> > 
> 
> I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.
> 
> -- Pasi
> 
> > Boris.
> > 
> > P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> > and installed glibc-devel.i586 for rpmbuild.
> > 
> > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > 
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > Cc:
>  "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Wednesday, August 19, 2009, 6:27 AM
> > 
> > On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > > Pasi,
> > > 
> > > I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> > > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> > > 
> > > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > > and installed (pretty recent - 08/10/2009) :-
> > > 
> > > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> > > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> >
>  > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> > > 
> > > [root@ServerXen341F Download]# rpm -qa|grep virt
> > > libvirt-0.7.0-3.fc11.x86_64
> > > libvirt-devel-0.7.0-3.fc11.x86_64
> > > python-virtinst-0.500.0-1.fc11.noarch
> > > virt-manager-0.8.0-1.fc11.noarch
> > > virt-viewer-0.2.0-1.fc11.x86_64
> > > libvirt-python-0.7.0-3.fc11.x86_64
> > > libvirt-client-0.7.0-3.fc11.x86_64
> > > 
> > > Then i was able to connect to xend via virt-manager and attempted to start building
> > > OSOL HVM. Got an error at startup:-
> > > 
> > > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > > Traceback (most recent call last):
> > >
>    File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> > >     dom = guest.start_install(False, meter = meter)
> > >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> > >     return self._do_install(consolecb, meter, removeOld, wait)
> > >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> > >     self.domain = self.conn.createLinux(install_xml, 0)
> > >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> > >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> > > 
> > > Please advise , how to escalate it to Fedora's people ?
> > > 
> > 
> > I think you should
>  post to fedora-xen@redhat.com and possibly 
> > CC fedora-virt@redhat.com.
> > 
> > > Boris.
> > > P.S. Usually i installed libvirt stuff :-
> > > 
> > > # yum install libvirt libvirt-python python-virtinst \
> > > 
> > > virt-manager virt-viewer
> > > 
> > > To apply patch manually i need a kind of libvirt.src.rpm.
> > > I don't track Fedora so close to be aware of this.
> > > '
> > 
> > 
> > I was using the default libvirt from F11, but I manually added the bugfix patch:
> > 
> > - Download libvirt src.rpm:
> >   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
> > 
> > - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
> > 
> > - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
> >   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
> > 
> > - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
> >   patches are
>  added. You need to add one line to two different places.
> > 
> > - Run "rpmbuild -bb libvirt.spec"
> > 
> > - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
> > 
> > -- Pasi
> > 
> > 
> > > 
> > > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > > 
> > > From: Pasi Kärkkäinen <pasik@iki.fi>
> > > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > > Date: Wednesday, August 19, 2009, 3:09 AM
> > > 
> > > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > > > using Xen 3.4, but after I got that patched it was all fine
> > > > 
> > > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > > > 
> > > 
> > > I grabbed Xen 3.4.1-1 src.rpm from:
> > > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> > > 
> > > and rebuilt that for F11.
> > > 
> > > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> > > 
> > > Patch for the libvirt bug is here:
> > > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> > > 
> > > Upcoming libvirt update for F11 will fix this. After manually applying that
> > > patch and rebuilding libvirt I'm now able to successfully install new guests
> > > using virt-install and connect to their console by virt-viewer.
> > > 
> > > -- Pasi
> > >
>  
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> > > 
> > > 
> > > 
> > >       
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> > 
> >       
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
> 
> 
>       
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[-- Attachment #1.2: Type: text/html, Size: 18916 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 12573 bytes --]

Sorry for typo.

Source for new libvirt version should be 
http://markmc.fedorapeople.org/virt-preview/f11/x86_64/ 
    instead of 
http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/  

Boris.

--- On Wed, 8/19/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 11:40 AM

  Subscribed to both mailing lists and posted an extract from from xen-devel thread
Your's way to patching libvirt was chosen.

   Version of libvirt at  http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/  
doesn't seem clear to me. 
  Two qemu packages gets installed with Xen 3.4.1 and my original attempt seems
correct to me in meantime ( not to install qemu packages from link above).
 
 Both ways of obtain libvirt give same error attempting HVM DomUs creation.

 Version been built via http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/  
appears to be able to start PV DomU install
 via HTTP source, but every times fails
trying to mount /boot on /dev/xvda1 right after partitioning image device.
Patching old version does allow go through PV DomU install via HTTP source.


Thanks.
Boris.

--- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, August 19, 2009, 10:32 AM

On Wed, Aug 19, 2009 at 06:35:40AM -0700, Boris Derzhavets wrote:
> Attempt to create HVM via virt-manager aborts with message:-
> 
> Unable to complete install '<class 'libvirt.libvirtError'>
 Domain not found: xenUnifiedDomainLookupByName
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/create.py", line 1501, in do_install
>     dom = guest.start_install(False, meter = meter)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install
>     return self._do_install(consolecb, meter, removeOld, wait)
>   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install
>     self.domain = self.conn.createLinux(install_xml, 0)
>   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 974, in createLinux
>     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> libvirtError: Domain not found: xenUnifiedDomainLookupByName
> 

This is getting offtopic for xen-devel .. these are issues
 with
libvirt/virt-tools/fedora and should be discussed on their mailinglists..

Please open a thread about that HVM problem on fedora-xen (and CC fedora-virt).

-- Pasi

> Boris
> 
> --- On Wed, 8/19/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
> 
> From: Boris Derzhavets <bderzhavets@yahoo.com>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Pasi Kärkkäinen" <pasik@iki.fi>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August
 19, 2009, 9:26 AM
> 
> Yes, Pasi
> 
>  I've loaded F11 DomU manually and changed timeout=5 then shutdown DomU and started smoothly via virt-manager.
> 
> Thanks again.
> Boris.
> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19,
 2009, 8:37 AM
> 
> On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> > Pasi,
> > 
> > Thanks  a lot a lot for your support.
> > 
> >   I was able  to
>  reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
> >   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. 
> > F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
> > 
> > # xm start VMF11
> > 
> > moves it to paused state and resuming shows :-
> > 
> > [root@ServerXen341F boris]# xm list
> >
 Name                                          ID   Mem VCPUs      State   Time(s)
> >
>  Domain-0                                    0    6034     2     r-----    574.9
> > VMF11                                         3   
 2048     0     ------      0.0
> > 
> 
> What do you have in "xm log" ? Is the last line about running pygrub?
> 
> I'm seeing an issue with F11 domU where the domU grub.conf contains
> timeout=0 and that causes pygrub to get stuck and thus prevents the domU
> from starting.. changing to timeout=5 fixes the
>  problem. 
> 
> I'm going to debug pygrub later today.. I believe it's a bug in pygrub.
> 
> > Attempt to create HVM crashes immediately.
> > 
> 
> I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.
> 
> -- Pasi
> 
> > Boris.
> > 
> > P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> > and installed glibc-devel.i586 for rpmbuild.
> > 
> > --- On Wed, 8/19/09, Pasi
 Kärkkäinen <pasik@iki.fi> wrote:
> > 
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > Cc:
>  "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Wednesday, August 19, 2009, 6:27 AM
> > 
> > On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > > Pasi,
> > > 
> > > I was able to install 3.4.1 Hypervisor via
 xen-3.4.1.src.rpm with no problems.
> > > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> > > 
> > > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > > and installed (pretty recent - 08/10/2009) :-
> > > 
> > > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> > > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> >
>  > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> > > 
> > > [root@ServerXen341F Download]# rpm -qa|grep virt
> >
 > libvirt-0.7.0-3.fc11.x86_64
> > > libvirt-devel-0.7.0-3.fc11.x86_64
> > > python-virtinst-0.500.0-1.fc11.noarch
> > > virt-manager-0.8.0-1.fc11.noarch
> > > virt-viewer-0.2.0-1.fc11.x86_64
> > > libvirt-python-0.7.0-3.fc11.x86_64
> > > libvirt-client-0.7.0-3.fc11.x86_64
> > > 
> > > Then i was able to connect to xend via virt-manager and attempted to start building
> > > OSOL HVM. Got an error at startup:-
> > > 
> > > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > > Traceback (most recent call last):
> > >
>    File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> > >     dom = guest.start_install(False, meter = meter)
> > >   File
 "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> > >     return self._do_install(consolecb, meter, removeOld, wait)
> > >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> > >     self.domain = self.conn.createLinux(install_xml, 0)
> > >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> > >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> > > 
> > > Please advise , how to escalate it to Fedora's people ?
> > > 
> > 
> > I think you should
>  post to fedora-xen@redhat.com
 and possibly 
> > CC fedora-virt@redhat.com.
> > 
> > > Boris.
> > > P.S. Usually i installed libvirt stuff :-
> > > 
> > > # yum install libvirt libvirt-python python-virtinst \
> > > 
> > > virt-manager virt-viewer
> > > 
> > > To apply patch manually i need a kind of libvirt.src.rpm.
> > > I don't track Fedora so close to be aware of this.
> > > '
> > 
> > 
> > I was using the default libvirt from F11, but I manually added the bugfix patch:
> > 
> > - Download libvirt src.rpm:
> >   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
> > 
> > - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
> > 
> > - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
> >   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
> > 
> > - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch
 like other
> >   patches are
>  added. You need to add one line to two different places.
> > 
> > - Run "rpmbuild -bb libvirt.spec"
> > 
> > - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
> > 
> > -- Pasi
> > 
> > 
> > > 
> > > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > > 
> > > From: Pasi Kärkkäinen <pasik@iki.fi>
> > > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > > Date: Wednesday, August 19, 2009, 3:09 AM
> > > 
> > > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > > > using Xen 3.4, but after I got that patched it was all fine
> > > > 
> > > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > > > 
> > > 
> > > I grabbed Xen 3.4.1-1 src.rpm from:
> >
 > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> > > 
> > > and rebuilt that for F11.
> > > 
> > > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> > > 
> > > Patch for the libvirt bug is here:
> > > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> > > 
> > > Upcoming libvirt update for F11 will fix this. After manually applying that
> > > patch and rebuilding libvirt I'm now able to successfully install new
 guests
> > > using virt-install and connect to their console by virt-viewer.
> > > 
> > > -- Pasi
> > >
>  
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> > > 
> > > 
> > > 
> > >       
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> > 
> >       
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
> 
> 
>       
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-----Inline Attachment Follows-----

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 19316 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 domU/guest pygrub grub.conf timeout=0 problem

[Pasi Kärkkäinen]

[-- Attachment #1: Type: text/plain, Size: 8643 bytes --]

On Wed, Aug 19, 2009 at 06:26:26AM -0700, Boris Derzhavets wrote:
> Yes, Pasi
> 
>  I've loaded F11 DomU manually and changed timeout=5 then shutdown DomU and started smoothly via virt-manager.
> 

Attached is a patch for /usr/bin/pygrub of Xen 3.4.1. It fixes the grub.conf
timeout=0 parameter handling of Fedora 11 PV domUs/guests.

Without this patch pygrub will get stuck and doesn't work if there's timeout=0 in domU grub.conf.

-- Pasi

> Thanks again.
> Boris.
> 
> --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Wednesday, August 19, 2009, 8:37 AM
> 
> On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> > Pasi,
> > 
> > Thanks  a lot a lot for your support.
> > 
> >   I was able  to reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
> >   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. 
> > F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
> > 
> > # xm start VMF11
> > 
> > moves it to paused state and resuming shows :-
> > 
> > [root@ServerXen341F boris]# xm list
> > Name                                          ID   Mem VCPUs      State   Time(s)
> > Domain-0                                    0    6034     2     r-----    574.9
> > VMF11                                         3    2048     0     ------      0.0
> > 
> 
> What do you have in "xm log" ? Is the last line about running pygrub?
> 
> I'm seeing an issue with F11 domU where the domU grub.conf contains
> timeout=0 and that causes pygrub to get stuck and thus prevents the domU
> from starting.. changing to timeout=5 fixes the problem. 
> 
> I'm going to debug pygrub later today.. I believe it's a bug in pygrub.
> 
> > Attempt to create HVM crashes immediately.
> > 
> 
> I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.
> 
> -- Pasi
> 
> > Boris.
> > 
> > P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> > and installed glibc-devel.i586 for rpmbuild.
> > 
> > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > 
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Wednesday, August 19, 2009, 6:27 AM
> > 
> > On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > > Pasi,
> > > 
> > > I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> > > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> > > 
> > > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > > and installed (pretty recent - 08/10/2009) :-
> > > 
> > > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> > > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> > > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> > > 
> > > [root@ServerXen341F Download]# rpm -qa|grep virt
> > > libvirt-0.7.0-3.fc11.x86_64
> > > libvirt-devel-0.7.0-3.fc11.x86_64
> > > python-virtinst-0.500.0-1.fc11.noarch
> > > virt-manager-0.8.0-1.fc11.noarch
> > > virt-viewer-0.2.0-1.fc11.x86_64
> > > libvirt-python-0.7.0-3.fc11.x86_64
> > > libvirt-client-0.7.0-3.fc11.x86_64
> > > 
> > > Then i was able to connect to xend via virt-manager and attempted to start building
> > > OSOL HVM. Got an error at startup:-
> > > 
> > > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > > Traceback (most recent call last):
> > >   File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> > >     dom = guest.start_install(False, meter = meter)
> > >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> > >     return self._do_install(consolecb, meter, removeOld, wait)
> > >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> > >     self.domain = self.conn.createLinux(install_xml, 0)
> > >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> > >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> > > 
> > > Please advise , how to escalate it to Fedora's people ?
> > > 
> > 
> > I think you should post to fedora-xen@redhat.com and possibly 
> > CC fedora-virt@redhat.com.
> > 
> > > Boris.
> > > P.S. Usually i installed libvirt stuff :-
> > > 
> > > # yum install libvirt libvirt-python python-virtinst \
> > > 
> > > virt-manager virt-viewer
> > > 
> > > To apply patch manually i need a kind of libvirt.src.rpm.
> > > I don't track Fedora so close to be aware of this.
> > > '
> > 
> > 
> > I was using the default libvirt from F11, but I manually added the bugfix patch:
> > 
> > - Download libvirt src.rpm:
> >   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
> > 
> > - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
> > 
> > - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
> >   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
> > 
> > - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
> >   patches are added. You need to add one line to two different places.
> > 
> > - Run "rpmbuild -bb libvirt.spec"
> > 
> > - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
> > 
> > -- Pasi
> > 
> > 
> > > 
> > > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > > 
> > > From: Pasi Kärkkäinen <pasik@iki.fi>
> > > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > > Date: Wednesday, August 19, 2009, 3:09 AM
> > > 
> > > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > > > using Xen 3.4, but after I got that patched it was all fine
> > > > 
> > > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > > > 
> > > 
> > > I grabbed Xen 3.4.1-1 src.rpm from:
> > > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> > > 
> > > and rebuilt that for F11.
> > > 
> > > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> > > 
> > > Patch for the libvirt bug is here:
> > > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> > > 
> > > Upcoming libvirt update for F11 will fix this. After manually applying that
> > > patch and rebuilding libvirt I'm now able to successfully install new guests
> > > using virt-install and connect to their console by virt-viewer.
> > > 
> > > -- Pasi
> > > 
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> > > 
> > > 
> > > 
> > >       
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> > 
> >       
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       

[-- Attachment #2: pygrub-fix-zero-timeout.patch --]
[-- Type: text/x-diff, Size: 505 bytes --]

--- pygrub-xen341	2009-08-17 22:22:29.000000000 +0300
+++ pygrub	2009-08-19 18:39:17.000000000 +0300
@@ -447,7 +447,7 @@
                     # So we may come here even after a key has been pressed.
                     # Check both timeout and mytime to avoid exiting
                     # when we shouldn't.
-                    if timeout != -1 and mytime >= int(timeout):
+		    if mytime >= int(timeout):
                         self.isdone = True
                         break
             else:

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap / Fedora 11 domU/guest pygrub grub.conf timeout=0 problem

[Pasi Kärkkäinen]

On Wed, Aug 19, 2009 at 08:00:05PM +0300, Pasi Kärkkäinen wrote:
> On Wed, Aug 19, 2009 at 06:26:26AM -0700, Boris Derzhavets wrote:
> > Yes, Pasi
> > 
> >  I've loaded F11 DomU manually and changed timeout=5 then shutdown DomU and started smoothly via virt-manager.
> > 
> 
> Attached is a patch for /usr/bin/pygrub of Xen 3.4.1. It fixes the grub.conf
> timeout=0 parameter handling of Fedora 11 PV domUs/guests.
> 
> Without this patch pygrub will get stuck and doesn't work if there's timeout=0 in domU grub.conf.
> 

Also it looks like even with the default version of pygrub of Xen 3.4.1 F11
domU works, but you have to go to "xm console <domain>" to choose the kernel
to boot! 

-- Pasi

> -- Pasi
> 
> > Thanks again.
> > Boris.
> > 
> > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > 
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Wednesday, August 19, 2009, 8:37 AM
> > 
> > On Wed, Aug 19, 2009 at 05:21:55AM -0700, Boris Derzhavets wrote:
> > > Pasi,
> > > 
> > > Thanks  a lot a lot for your support.
> > > 
> > >   I was able  to reproduce you instructions on F11 (64-bit) instance (C2D E8400,8 GB RAM).
> > >   I remind pretty clear,  that now i am experiencing the same issue as with xen-3.4.0-2.fc12.src.rpm. 
> > > F11 PVM been created via virt-manager, cannot be , actually, managed either via virt-manager or from command line.
> > > 
> > > # xm start VMF11
> > > 
> > > moves it to paused state and resuming shows :-
> > > 
> > > [root@ServerXen341F boris]# xm list
> > > Name                                          ID   Mem VCPUs      State   Time(s)
> > > Domain-0                                    0    6034     2     r-----    574.9
> > > VMF11                                         3    2048     0     ------      0.0
> > > 
> > 
> > What do you have in "xm log" ? Is the last line about running pygrub?
> > 
> > I'm seeing an issue with F11 domU where the domU grub.conf contains
> > timeout=0 and that causes pygrub to get stuck and thus prevents the domU
> > from starting.. changing to timeout=5 fixes the problem. 
> > 
> > I'm going to debug pygrub later today.. I believe it's a bug in pygrub.
> > 
> > > Attempt to create HVM crashes immediately.
> > > 
> > 
> > I can't test HVM guests on my testbox, it doesn't have VT support in the CPU.
> > 
> > -- Pasi
> > 
> > > Boris.
> > > 
> > > P.S. I was unable to find glibc-devel.i386 for 64-bit F11 (vs F10)
> > > and installed glibc-devel.i586 for rpmbuild.
> > > 
> > > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > > 
> > > From: Pasi Kärkkäinen <pasik@iki.fi>
> > > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > > Date: Wednesday, August 19, 2009, 6:27 AM
> > > 
> > > On Wed, Aug 19, 2009 at 02:54:36AM -0700, Boris Derzhavets wrote:
> > > > Pasi,
> > > > 
> > > > I was able to install 3.4.1 Hypervisor via xen-3.4.1.src.rpm with no problems.
> > > > Rebooted into Xen Host with 2.6.30.3 xenified aka Suse kernel. Fine.
> > > > 
> > > > Downloaded from http://markmc.fedorapeople.org/virt-preview/f11/x86_64/
> > > > and installed (pretty recent - 08/10/2009) :-
> > > > 
> > > > yum install libvirt-0.7.0-3.fc11.x86_64.rpm \       
> > > > libvirt-client-0.7.0-3.fc11.x86_64.rpm \
> > > > libvirt-devel-0.7.0-3.fc11.x86_64.rpm \
> > > > libvirt-python-0.7.0-3.fc11.x86_64.rpm \
> > > > python-virtinst-0.500.0-1.fc11.noarch.rpm \
> > > > virt-manager-0.8.0-1.fc11.noarch.rpm \
> > > > virt-viewer-0.2.0-1.fc11.x86_64.rpm
> > > > 
> > > > [root@ServerXen341F Download]# rpm -qa|grep virt
> > > > libvirt-0.7.0-3.fc11.x86_64
> > > > libvirt-devel-0.7.0-3.fc11.x86_64
> > > > python-virtinst-0.500.0-1.fc11.noarch
> > > > virt-manager-0.8.0-1.fc11.noarch
> > > > virt-viewer-0.2.0-1.fc11.x86_64
> > > > libvirt-python-0.7.0-3.fc11.x86_64
> > > > libvirt-client-0.7.0-3.fc11.x86_64
> > > > 
> > > > Then i was able to connect to xend via virt-manager and attempted to start building
> > > > OSOL HVM. Got an error at startup:-
> > > > 
> > > > Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName
> > > > Traceback (most recent call last):
> > > >   File "/usr/share/virt-manager/virtManager/create.py", line 1489, in do_install
> > > >     dom = guest.start_install(False, meter = meter)
> > > >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 628, in start_install
> > > >     return self._do_install(consolecb, meter, removeOld, wait)
> > > >   File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 726, in _do_install
> > > >     self.domain = self.conn.createLinux(install_xml, 0)
> > > >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1077, in createLinux
> > > >     if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
> > > > libvirtError: Domain not found: xenUnifiedDomainLookupByName
> > > > 
> > > > Please advise , how to escalate it to Fedora's people ?
> > > > 
> > > 
> > > I think you should post to fedora-xen@redhat.com and possibly 
> > > CC fedora-virt@redhat.com.
> > > 
> > > > Boris.
> > > > P.S. Usually i installed libvirt stuff :-
> > > > 
> > > > # yum install libvirt libvirt-python python-virtinst \
> > > > 
> > > > virt-manager virt-viewer
> > > > 
> > > > To apply patch manually i need a kind of libvirt.src.rpm.
> > > > I don't track Fedora so close to be aware of this.
> > > > '
> > > 
> > > 
> > > I was using the default libvirt from F11, but I manually added the bugfix patch:
> > > 
> > > - Download libvirt src.rpm:
> > >   ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/11/SRPMS/libvirt-0.6.2-14.fc11.src.rpm
> > > 
> > > - install it: "rpm -i libvirt-0.6.2-14.fc11.src.rpm"
> > > 
> > > - Copy & paste the patch to a file /root/rpmbuild/SOURCES/libvirt-bugfix-custom.patch from
> > >   http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55ffd3f9a5004e681c8ffb2279d27965eb42e956;hp=b211bb6293355bf68e33f56f947021bd7bb8e675;hb=14435163a086c0bcdff04308077fa46a5fa08bb0;hpb=fd90b67afe59265327dde7e447ea847687bd4e8d
> > > 
> > > - Edit /root/rpmbuild/SPECS/libvirt.spec and add the patch like other
> > >   patches are added. You need to add one line to two different places.
> > > 
> > > - Run "rpmbuild -bb libvirt.spec"
> > > 
> > > - Install the bugfixed rpms from /root/rpmbuild/RPMS/i586/
> > > 
> > > -- Pasi
> > > 
> > > 
> > > > 
> > > > --- On Wed, 8/19/09, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > > > 
> > > > From: Pasi Kärkkäinen <pasik@iki.fi>
> > > > Subject: Re: [Xen-devel] pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4
> > > > To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> > > > Cc: "Xen-devel" <xen-devel@lists.xensource.com>
> > > > Date: Wednesday, August 19, 2009, 3:09 AM
> > > > 
> > > > On Tue, Aug 18, 2009 at 09:16:08PM -0700, Boris Derzhavets wrote:
> > > > > >There was a bug in libvirt of F11 dom0 causing virt-viewer to crash when 
> > > > > > using Xen 3.4, but after I got that patched it was all fine
> > > > > 
> > > > > If it's possible to share your experience , i wonder does it mean, that  you've got xen-3.4.0-2.fc12.src.rpm working on F11 (32-bit) ?
> > > > > I was unable to connect to xend when starting virt-manager after xen-3.4.0-2.fc12.src.rpm install ( along with generated packages) on 64-bit F11 instance.
> > > > > 
> > > > 
> > > > I grabbed Xen 3.4.1-1 src.rpm from:
> > > > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/
> > > > 
> > > > and rebuilt that for F11.
> > > > 
> > > > The next problem was that libvirt package in Fedora 11 has a bug, which causes it
> > > > to crash (segfault) when virt-viewer is started. This crash only happens with Xen 3.4, not with Xen 3.3.
> > > > 
> > > > Patch for the libvirt bug is here:
> > > > http://libvirt.org/git/?p=libvirt.git;a=commit;h=14435163a086c0bcdff04308077fa46a5fa08bb0
> > > > 
> > > > Upcoming libvirt update for F11 will fix this. After manually applying that
> > > > patch and rebuilding libvirt I'm now able to successfully install new guests
> > > > using virt-install and connect to their console by virt-viewer.
> > > > 
> > > > -- Pasi
> > > > 
> > > > _______________________________________________
> > > > Xen-devel mailing list
> > > > Xen-devel@lists.xensource.com
> > > > http://lists.xensource.com/xen-devel
> > > > 
> > > > 
> > > > 
> > > >       
> > > 
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> > > 
> > > 
> > > 
> > >       
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> > 
> >       
> --- pygrub-xen341	2009-08-17 22:22:29.000000000 +0300
> +++ pygrub	2009-08-19 18:39:17.000000000 +0300
> @@ -447,7 +447,7 @@
>                      # So we may come here even after a key has been pressed.
>                      # Check both timeout and mytime to avoid exiting
>                      # when we shouldn't.
> -                    if timeout != -1 and mytime >= int(timeout):
> +		    if mytime >= int(timeout):
>                          self.isdone = True
>                          break
>              else:

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap

[Konrad Rzeszutek Wilk]

> That's useful to know, but I was referring to testing release 2.6.30.x
> kernels as well, just to make sure they still work.

I found three issues with 2.6.30-rc3-tip (xen-tip/master):
 - if you don't have CONFIG_HIBERNATION set it hangs at startup on the VGA init code (right after "about to get started").  I played
   with turning CONFIG_SWAP off, which in turn unselects _HIBERNATION off.
 - if you set CONFIG_STACKPROTECTOR=y you get a nice big page fault right at the startup (doesn't even get to 'about to get started' message).
 - poweroff doesn't turn the machine off (but I haven't verified whether the machine normally powers off with a non-Xen 2.6.30-rc3-tip kernel
   so this might be an operator errro).

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/19/09 06:26, Konrad Rzeszutek Wilk wrote:
> I found three issues with 2.6.30-rc3-tip (xen-tip/master):
>  - if you don't have CONFIG_HIBERNATION set it hangs at startup on the VGA init code (right after "about to get started").  I played
>    with turning CONFIG_SWAP off, which in turn unselects _HIBERNATION off.
>   

Oh, interesting.

>  - if you set CONFIG_STACKPROTECTOR=y you get a nice big page fault right at the startup (doesn't even get to 'about to get started' message).
>   

I have a tentative fix for this in rebase/master.

>  - poweroff doesn't turn the machine off (but I haven't verified whether the machine normally powers off with a non-Xen 2.6.30-rc3-tip kernel
>    so this might be an operator errro).
>   

I've found that's fairly erratic even on native.  But I guess its likely
to be something to do with ACPI.  Though I would have thought that Xen
would have the responsibility for poweroff when the dom0 kernel
terminates itself.

I think you should continue using rebase/master rather than xen-tip/.

    J

Re: pvops dom0 work roadmap

[Pasi Kärkkäinen]

On Wed, Aug 19, 2009 at 09:19:48AM -0700, Jeremy Fitzhardinge wrote:
> On 08/19/09 06:26, Konrad Rzeszutek Wilk wrote:
> > I found three issues with 2.6.30-rc3-tip (xen-tip/master):
> >  - if you don't have CONFIG_HIBERNATION set it hangs at startup on the VGA init code (right after "about to get started").  I played
> >    with turning CONFIG_SWAP off, which in turn unselects _HIBERNATION off.
> >   
> 
> Oh, interesting.
> 
> >  - if you set CONFIG_STACKPROTECTOR=y you get a nice big page fault right at the startup (doesn't even get to 'about to get started' message).
> >   
> 
> I have a tentative fix for this in rebase/master.
> 
> >  - poweroff doesn't turn the machine off (but I haven't verified whether the machine normally powers off with a non-Xen 2.6.30-rc3-tip kernel
> >    so this might be an operator errro).
> >   
> 
> I've found that's fairly erratic even on native.  But I guess its likely
> to be something to do with ACPI.  Though I would have thought that Xen
> would have the responsibility for poweroff when the dom0 kernel
> terminates itself.
> 

I have the same problem (like I already reported earlier). 
rebase/master 2.6.31-rc6 doesn't poweroff, with Xen 3.4.1.

Same kernel booted on baremetal without Xen does poweroff just fine.

-- Pasi

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/19/09 09:54, Pasi Kärkkäinen wrote:
> I have the same problem (like I already reported earlier). 
> rebase/master 2.6.31-rc6 doesn't poweroff, with Xen 3.4.1.
>   

Yeah.  Do other dom0 kernels power off properly?

    J

Re: pvops dom0 work roadmap

[Jan Beulich]

>>> Jeremy Fitzhardinge <jeremy@goop.org> 19.08.09 18:19 >>>
>On 08/19/09 06:26, Konrad Rzeszutek Wilk wrote:
>>  - poweroff doesn't turn the machine off (but I haven't verified whether the machine normally powers off with a non-Xen
>2.6.30-rc3-tip kernel
>>    so this might be an operator errro).
>>   
>
>I've found that's fairly erratic even on native.  But I guess its likely
>to be something to do with ACPI.  Though I would have thought that Xen
>would have the responsibility for poweroff when the dom0 kernel
>terminates itself.

Yes, but Dom0 has to tell Xen when this is to happen (see
acpi_enter_sleep_state() in the 2.6.18 tree). I think you had discussed
this with the ACPI folks already, and your initial approach was disliked
for whatever reason...

Jan

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/20/09 03:10, Jan Beulich wrote:
> Yes, but Dom0 has to tell Xen when this is to happen (see
> acpi_enter_sleep_state() in the 2.6.18 tree).

Oh, that's a bit awkward.  I'd assumed that dom0 would do a shutdown
hypercall and Xen would sort out the actual shutdown part.

> I think you had discussed
> this with the ACPI folks already, and your initial approach was disliked
> for whatever reason...

Yes, we haven't converged on something upstreamable yet, but
rebase/master has everything needed for S3, and I think that's enough
for shutdown?  I haven't tried shutdown lately, but reboot works for me;
is that the same path?

    J

Re: pvops dom0 work roadmap

[Jan Beulich]

>>> Jeremy Fitzhardinge <jeremy@goop.org> 20.08.09 18:43 >>>
On 08/20/09 03:10, Jan Beulich wrote:
>Yes, we haven't converged on something upstreamable yet, but
>rebase/master has everything needed for S3, and I think that's enough
>for shutdown?  I haven't tried shutdown lately, but reboot works for me;
>is that the same path?

Yes, if S3 works, then S5 should work too. S5 and reboot, however, are
different paths (reboot indeed is a simple hypercall).

Jan

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/19/09 06:26, Konrad Rzeszutek Wilk wrote:
>  - if you don't have CONFIG_HIBERNATION set it hangs at startup on the VGA init code (right after "about to get started").  I played
>    with turning CONFIG_SWAP off, which in turn unselects _HIBERNATION off.
>   

It looks like I've been testing without CONFIG_HIBERNATION enabled, so I
can't repro this.  Are there any messages, either from the kernel log or
in the Xen log?  What does pressing '0' on the Xen console show?  Are
you building Xen with DEBUG=y?

Thanks,
    J

Re: pvops dom0 work roadmap

[Konrad Rzeszutek Wilk]

On Wed, Aug 19, 2009 at 10:17:00AM -0700, Jeremy Fitzhardinge wrote:
> On 08/19/09 06:26, Konrad Rzeszutek Wilk wrote:
> >  - if you don't have CONFIG_HIBERNATION set it hangs at startup on the VGA init code (right after "about to get started").  I played
> >    with turning CONFIG_SWAP off, which in turn unselects _HIBERNATION off.
> >   
> 
> It looks like I've been testing without CONFIG_HIBERNATION enabled, so I
> can't repro this.  Are there any messages, either from the kernel log or
> in the Xen log?  What does pressing '0' on the Xen console show?  Are
They are from Linux:

<BEGIN>
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 140kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
<END>

Instrumenting the code lightly (xen_raw_console_write sprinkled) about shows that:
1132                 xen_init_vga(info, xen_start_info->console.dom0.info_size);

is the last time I see anything.

These are the boot options:

 APPEND xen.gz  com1=115200,8n1,0xcf00,0  console=com1,vga guest_loglvl=all  dom0_mem=max:512MB--- vmlinuz debug selinux=0 initrd_ignore_loglevel sysrq_always_enable ip=:::::eth1:dhcp earlyprintk=xen,keep irqpoll console=tty console=hvc0 loglevel=10 bb_inittab=/etc/inittab-debug  --- initramfs.cpio.gz

And my serial console, keyboard, nor the VGA screen show any activity.
I didn't really dig any deeper than that.


I hadn't tried to press '0'.
> you building Xen with DEBUG=y?

I belive so.


I will retry this, but in the meantime I am tracking balloon accessing non-existent pages:

<BEGIN>
[    0.239963] xen_balloon: Initialising balloon driver.
[    0.240057] xen_ballon: 131072 -> 1245184		<-- added a printk. 
[    0.257938] BUG: unable to handle kernel [    0.257938] BUG: unable to handle kernel paging requestpaging request at ffffea0002d80028
 at ffffea0002d80028
[    0.257960] IP:[    0.257960] IP: [<ffffffff81215f7b>] balloon_append+0x13/0x36
 [<ffffffff81215f7b>] balloon_append+0x13/0x36
[    0.257960] PGD 10402067 [    0.257960] PGD 10402067 PUD 10403067 PUD 10403067 PMD 1301a067 PMD 1301a067 PTE 0PTE 0

[    0.257960] Oops: 0002 [#1] [    0.257960] Oops: 0002 [#1] SMP SMP 

[    0.257960] last sysfs file: 
[    0.257960] last sysfs file: 
[    0.257960] CPU 0 [    0.257960] CPU 0 

[    0.257960] Modules linked in:[    0.257960] Modules linked in:

[    0.257960] Pid: 1, comm: swapper Not tainted 2.6.31-rc5-xen0-23866-g8584ce8-dirty #6 .  
[    0.257960] Pid: 1, comm: swapper Not tainted 2.6.31-rc5-xen0-23866-g8584ce8-dirty #6 .  
[    0.257960] RIP: e030:[<ffffffff81215f7b>] [    0.257960] RIP: e030:[<ffffffff81215f7b>]  [<ffffffff81215f7b>] balloon_append+0x13/0x36
 [<ffffffff81215f7b>] balloon_append+0x13/0x36
[    0.257960] RSP: e02b:ffff88001fc81e70  EFLAGS: 00010282
[    0.257960] RSP: e02b:ffff88001fc81e70  EFLAGS: 00010282
[    0.257960] RAX: ffffea0002d80028 RBX: 00000000000d0001 RCX: 0000000000000064
[    0.257960] RAX: ffffea0002d80028 RBX: 00000000000d0001 RCX: 0000000000000064
[    0.257960] RDX: ffffea0002d7fff0 RSI: ffffffff810000df RDI: ffffea0002d80000
[    0.257960] RDX: ffffea0002d7fff0 RSI: ffffffff810000df RDI: ffffea0002d80000
[    0.257960] RBP: ffff88001fc81e70 R08: 0000000000000000 R09: ffff88001fc38000
[    0.257960] RBP: ffff88001fc81e70 R08: 0000000000000000 R09: ffff88001fc38000
[    0.257960] R10: ffff88001fc81c20 R11: ffff88001fc81da0 R12: ffffea0002d80038
[    0.257960] R10: ffff88001fc81c20 R11: ffff88001fc81da0 R12: ffffea0002d80038
[    0.257960] R13: ffffffff816e1907 R14: 0000000000000000 R15: 0000000000000000
[    0.257960] R13: ffffffff816e1907 R14: 0000000000000000 R15: 0000000000000000
[    0.257960] FS:  0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
[    0.257960] FS:  0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
[    0.257960] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[    0.257960] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[    0.257960] CR2: ffffea0002d80028 CR3: 0000000001001000 CR4: 0000000000002660
[    0.257960] CR2: ffffea0002d80028 CR3: 0000000001001000 CR4: 0000000000002660
[    0.257960] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    0.257960] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    0.257960] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    0.257960] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    0.257960] Process swapper (pid: 1, threadinfo ffff88001fc80000, task ffff88001fc78000)
[    0.257960] Process swapper (pid: 1, threadinfo ffff88001fc80000, task ffff88001fc78000)
[    0.257960] Stack:
[    0.257960] Stack:
[    0.257960]  ffff88001fc81ea0[    0.257960]  ffff88001fc81ea0 ffffffff816e1ad0 ffffffff816e1ad0 ffff88001fc81ea0 ffff88001fc81ea0 ffffffff816e18ad ffffffff816e18ad

[    0.257960] <0>[    0.257960] <0> ffffffff817167a8 ffffffff817167a8 0000000000000040 0000000000000040 ffff88001fc81f10 ffff88001fc81f10 ffffffff8100a05c ffffffff8100a05c

[    0.257960] <0>[    0.257960] <0> ffff88001fc81e00 ffff88001fc81e00 ffffffff8108e691 ffffffff8108e691 0000000000003333 0000000000003333 ffffffff81110000 ffffffff81110000

[    0.257960] Call Trace:
[    0.257960] Call Trace:
[    0.257960]  [<ffffffff816e1ad0>] balloon_init+0x1c9/0x1fd
[    0.257960]  [<ffffffff816e1ad0>] balloon_init+0x1c9/0x1fd
[    0.257960]  [<ffffffff816e18ad>] ? xenbus_probe_frontend_init+0x53/0x59
[    0.257960]  [<ffffffff816e18ad>] ? xenbus_probe_frontend_init+0x53/0x59
[    0.257960]  [<ffffffff8100a05c>] do_one_initcall+0x56/0x136
[    0.257960]  [<ffffffff8100a05c>] do_one_initcall+0x56/0x136
[    0.257960]  [<ffffffff8108e691>] ? register_irq_proc+0xae/0xca
[    0.257960]  [<ffffffff8108e691>] ? register_irq_proc+0xae/0xca
[    0.257960]  [<ffffffff81110000>] ? elf_core_dump+0x81e/0xc29
[    0.257960]  [<ffffffff81110000>] ? elf_core_dump+0x81e/0xc29
[    0.257960]  [<ffffffff816bc9aa>] kernel_init+0x15e/0x1b6
[    0.257960]  [<ffffffff816bc9aa>] kernel_init+0x15e/0x1b6
[    0.257960]  [<ffffffff81012cea>] child_rip+0xa/0x20
[    0.257960]  [<ffffffff81012cea>] child_rip+0xa/0x20
[    0.257960]  [<ffffffff81011ea7>] ? int_ret_from_sys_call+0x7/0x1b
[    0.257960]  [<ffffffff81011ea7>] ? int_ret_from_sys_call+0x7/0x1b
[    0.257960]  [<ffffffff8101265d>] ? retint_restore_args+0x5/0x6
[    0.257960]  [<ffffffff8101265d>] ? retint_restore_args+0x5/0x6
[    0.257960]  [<ffffffff81012ce0>] ? child_rip+0x0/0x20
[    0.257960]  [<ffffffff81012ce0>] ? child_rip+0x0/0x20
[    0.257960] Code: [    0.257960] Code: 55 55 89 89 ff ff 48 48 89 89 e5 e5 e8 e8 25 25 32 32 df df ff ff c9 c9 c3 c3 55 55 48 48 89 89 e5 e5 e8 e8 5a 5a 32 32 df df ff ff c9 c9 c3 c3 48 48 8b 8b 15 15 d1 d1 0c 0c 43 43 00 00 48 48 8d 8d 47 47 28 28 55 55 48 48 89 89 e5 e5 48 48 89 89 42 42 08 08 <48> <48> 89 89 57 57 28 28 48 48 c7 c7 40 40 08 08 40 40 6c 6c 64 64 81 81 48 48 ff ff 05 05 6a 6a ac ac 60 60 00 00 48 48 ff ff 

[    0.257960] RIP [    0.257960] RIP  [<ffffffff81215f7b>] balloon_append+0x13/0x36
 [<ffffffff81215f7b>] balloon_append+0x13/0x36
[    0.257960]  RSP <ffff88001fc81e70>
[    0.257960]  RSP <ffff88001fc81e70>
[    0.257960] CR2: ffffea0002d80028
[    0.257960] CR2: ffffea0002d80028
[    0.257960] ---[ end trace 4eaa2a86a8e2da22 ]---
[    0.257960] ---[ end trace 4eaa2a86a8e2da22 ]---
<END>

Sorry for the duplicate lines. I think the combination of earlycons and console both pointing
to the Xen console driver is screwing this up.

This could be a simple bug with the max_pfn being reset to phantom value:

[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 000000000009f400 (usable)
[    0.000000]  Xen: 000000000009f400 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 00000000cfee0000 (usable)
[    0.000000]  Xen: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
[    0.000000]  Xen: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
[    0.000000]  Xen: 00000000cfef0000 - 00000000cff00000 (reserved)
[    0.000000]  Xen: 00000000e0000000 - 00000000f0000000 (reserved)
[    0.000000]  Xen: 00000000fec00000 - 0000000100000000 (reserved)
[    0.000000]  Xen: 0000000100000000 - 0000000130000000 (usable)
[    0.000000] console [xenboot0] enabled
[    0.000000] DMI 2.5 present.
[    0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[    0.000000] last_pfn = 0x130000 max_arch_pfn = 0x400000000
[    0.000000] max_pfn = 1245184			<-- Added a printk
[    0.000000] num_physpages: 1245184			<-- Added a printk
[    0.000000] Searching for max PFN under 4GB		<-- Added a printk
[    0.000000] last_pfn = 0xcfee0 max_arch_pfn = 0x400000000
[    0.000000] max_low_pfn: 851680m			<-- Added a printk
[    0.000000] Scanning 0 areas for low memory corruption
[    0.000000] modified physical RAM map:
[    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
[    0.000000]  modified: 0000000000010000 - 000000000009f400 (usable)
[    0.000000]  modified: 000000000009f400 - 0000000000100000 (reserved)
[    0.000000]  modified: 0000000000100000 - 00000000cfee0000 (usable)
[    0.000000]  modified: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
[    0.000000]  modified: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
[    0.000000]  modified: 00000000cfef0000 - 00000000cff00000 (reserved)
[    0.000000]  modified: 00000000e0000000 - 00000000f0000000 (reserved)
[    0.000000]  modified: 00000000fec00000 - 0000000100000000 (reserved)
[    0.000000]  modified: 0000000100000000 - 0000000130000000 (usable)
[    0.000000] initial memory mapped : 0 - 20000000

The machine has 4GB, but somehow the max_pfn is set to point to 5.1GB which is
surely not right. Oh, I am compiling a 64-bit Linux and Xen.

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/19/09 10:45, Konrad Rzeszutek Wilk wrote:
> I will retry this, but in the meantime I am tracking balloon accessing non-existent pages:
>   

Gianluca mentioned something about this to me.  I think he's looking
into it.

    J

> <BEGIN>
> [    0.239963] xen_balloon: Initialising balloon driver.
> [    0.240057] xen_ballon: 131072 -> 1245184		<-- added a printk. 
> [    0.257938] BUG: unable to handle kernel [    0.257938] BUG: unable to handle kernel paging requestpaging request at ffffea0002d80028
>  at ffffea0002d80028
> [    0.257960] IP:[    0.257960] IP: [<ffffffff81215f7b>] balloon_append+0x13/0x36
>  [<ffffffff81215f7b>] balloon_append+0x13/0x36
> [    0.257960] PGD 10402067 [    0.257960] PGD 10402067 PUD 10403067 PUD 10403067 PMD 1301a067 PMD 1301a067 PTE 0PTE 0
>
> [    0.257960] Oops: 0002 [#1] [    0.257960] Oops: 0002 [#1] SMP SMP 
>
> [    0.257960] last sysfs file: 
> [    0.257960] last sysfs file: 
> [    0.257960] CPU 0 [    0.257960] CPU 0 
>
> [    0.257960] Modules linked in:[    0.257960] Modules linked in:
>
> [    0.257960] Pid: 1, comm: swapper Not tainted 2.6.31-rc5-xen0-23866-g8584ce8-dirty #6 .  
> [    0.257960] Pid: 1, comm: swapper Not tainted 2.6.31-rc5-xen0-23866-g8584ce8-dirty #6 .  
> [    0.257960] RIP: e030:[<ffffffff81215f7b>] [    0.257960] RIP: e030:[<ffffffff81215f7b>]  [<ffffffff81215f7b>] balloon_append+0x13/0x36
>  [<ffffffff81215f7b>] balloon_append+0x13/0x36
> [    0.257960] RSP: e02b:ffff88001fc81e70  EFLAGS: 00010282
> [    0.257960] RSP: e02b:ffff88001fc81e70  EFLAGS: 00010282
> [    0.257960] RAX: ffffea0002d80028 RBX: 00000000000d0001 RCX: 0000000000000064
> [    0.257960] RAX: ffffea0002d80028 RBX: 00000000000d0001 RCX: 0000000000000064
> [    0.257960] RDX: ffffea0002d7fff0 RSI: ffffffff810000df RDI: ffffea0002d80000
> [    0.257960] RDX: ffffea0002d7fff0 RSI: ffffffff810000df RDI: ffffea0002d80000
> [    0.257960] RBP: ffff88001fc81e70 R08: 0000000000000000 R09: ffff88001fc38000
> [    0.257960] RBP: ffff88001fc81e70 R08: 0000000000000000 R09: ffff88001fc38000
> [    0.257960] R10: ffff88001fc81c20 R11: ffff88001fc81da0 R12: ffffea0002d80038
> [    0.257960] R10: ffff88001fc81c20 R11: ffff88001fc81da0 R12: ffffea0002d80038
> [    0.257960] R13: ffffffff816e1907 R14: 0000000000000000 R15: 0000000000000000
> [    0.257960] R13: ffffffff816e1907 R14: 0000000000000000 R15: 0000000000000000
> [    0.257960] FS:  0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
> [    0.257960] FS:  0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
> [    0.257960] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> [    0.257960] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> [    0.257960] CR2: ffffea0002d80028 CR3: 0000000001001000 CR4: 0000000000002660
> [    0.257960] CR2: ffffea0002d80028 CR3: 0000000001001000 CR4: 0000000000002660
> [    0.257960] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [    0.257960] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [    0.257960] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [    0.257960] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [    0.257960] Process swapper (pid: 1, threadinfo ffff88001fc80000, task ffff88001fc78000)
> [    0.257960] Process swapper (pid: 1, threadinfo ffff88001fc80000, task ffff88001fc78000)
> [    0.257960] Stack:
> [    0.257960] Stack:
> [    0.257960]  ffff88001fc81ea0[    0.257960]  ffff88001fc81ea0 ffffffff816e1ad0 ffffffff816e1ad0 ffff88001fc81ea0 ffff88001fc81ea0 ffffffff816e18ad ffffffff816e18ad
>
> [    0.257960] <0>[    0.257960] <0> ffffffff817167a8 ffffffff817167a8 0000000000000040 0000000000000040 ffff88001fc81f10 ffff88001fc81f10 ffffffff8100a05c ffffffff8100a05c
>
> [    0.257960] <0>[    0.257960] <0> ffff88001fc81e00 ffff88001fc81e00 ffffffff8108e691 ffffffff8108e691 0000000000003333 0000000000003333 ffffffff81110000 ffffffff81110000
>
> [    0.257960] Call Trace:
> [    0.257960] Call Trace:
> [    0.257960]  [<ffffffff816e1ad0>] balloon_init+0x1c9/0x1fd
> [    0.257960]  [<ffffffff816e1ad0>] balloon_init+0x1c9/0x1fd
> [    0.257960]  [<ffffffff816e18ad>] ? xenbus_probe_frontend_init+0x53/0x59
> [    0.257960]  [<ffffffff816e18ad>] ? xenbus_probe_frontend_init+0x53/0x59
> [    0.257960]  [<ffffffff8100a05c>] do_one_initcall+0x56/0x136
> [    0.257960]  [<ffffffff8100a05c>] do_one_initcall+0x56/0x136
> [    0.257960]  [<ffffffff8108e691>] ? register_irq_proc+0xae/0xca
> [    0.257960]  [<ffffffff8108e691>] ? register_irq_proc+0xae/0xca
> [    0.257960]  [<ffffffff81110000>] ? elf_core_dump+0x81e/0xc29
> [    0.257960]  [<ffffffff81110000>] ? elf_core_dump+0x81e/0xc29
> [    0.257960]  [<ffffffff816bc9aa>] kernel_init+0x15e/0x1b6
> [    0.257960]  [<ffffffff816bc9aa>] kernel_init+0x15e/0x1b6
> [    0.257960]  [<ffffffff81012cea>] child_rip+0xa/0x20
> [    0.257960]  [<ffffffff81012cea>] child_rip+0xa/0x20
> [    0.257960]  [<ffffffff81011ea7>] ? int_ret_from_sys_call+0x7/0x1b
> [    0.257960]  [<ffffffff81011ea7>] ? int_ret_from_sys_call+0x7/0x1b
> [    0.257960]  [<ffffffff8101265d>] ? retint_restore_args+0x5/0x6
> [    0.257960]  [<ffffffff8101265d>] ? retint_restore_args+0x5/0x6
> [    0.257960]  [<ffffffff81012ce0>] ? child_rip+0x0/0x20
> [    0.257960]  [<ffffffff81012ce0>] ? child_rip+0x0/0x20
> [    0.257960] Code: [    0.257960] Code: 55 55 89 89 ff ff 48 48 89 89 e5 e5 e8 e8 25 25 32 32 df df ff ff c9 c9 c3 c3 55 55 48 48 89 89 e5 e5 e8 e8 5a 5a 32 32 df df ff ff c9 c9 c3 c3 48 48 8b 8b 15 15 d1 d1 0c 0c 43 43 00 00 48 48 8d 8d 47 47 28 28 55 55 48 48 89 89 e5 e5 48 48 89 89 42 42 08 08 <48> <48> 89 89 57 57 28 28 48 48 c7 c7 40 40 08 08 40 40 6c 6c 64 64 81 81 48 48 ff ff 05 05 6a 6a ac ac 60 60 00 00 48 48 ff ff 
>
> [    0.257960] RIP [    0.257960] RIP  [<ffffffff81215f7b>] balloon_append+0x13/0x36
>  [<ffffffff81215f7b>] balloon_append+0x13/0x36
> [    0.257960]  RSP <ffff88001fc81e70>
> [    0.257960]  RSP <ffff88001fc81e70>
> [    0.257960] CR2: ffffea0002d80028
> [    0.257960] CR2: ffffea0002d80028
> [    0.257960] ---[ end trace 4eaa2a86a8e2da22 ]---
> [    0.257960] ---[ end trace 4eaa2a86a8e2da22 ]---
> <END>
>
> Sorry for the duplicate lines. I think the combination of earlycons and console both pointing
> to the Xen console driver is screwing this up.
>
> This could be a simple bug with the max_pfn being reset to phantom value:
>
> [    0.000000] BIOS-provided physical RAM map:
> [    0.000000]  Xen: 0000000000000000 - 000000000009f400 (usable)
> [    0.000000]  Xen: 000000000009f400 - 0000000000100000 (reserved)
> [    0.000000]  Xen: 0000000000100000 - 00000000cfee0000 (usable)
> [    0.000000]  Xen: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
> [    0.000000]  Xen: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
> [    0.000000]  Xen: 00000000cfef0000 - 00000000cff00000 (reserved)
> [    0.000000]  Xen: 00000000e0000000 - 00000000f0000000 (reserved)
> [    0.000000]  Xen: 00000000fec00000 - 0000000100000000 (reserved)
> [    0.000000]  Xen: 0000000100000000 - 0000000130000000 (usable)
> [    0.000000] console [xenboot0] enabled
> [    0.000000] DMI 2.5 present.
> [    0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
> [    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
> [    0.000000] last_pfn = 0x130000 max_arch_pfn = 0x400000000
> [    0.000000] max_pfn = 1245184			<-- Added a printk
> [    0.000000] num_physpages: 1245184			<-- Added a printk
> [    0.000000] Searching for max PFN under 4GB		<-- Added a printk
> [    0.000000] last_pfn = 0xcfee0 max_arch_pfn = 0x400000000
> [    0.000000] max_low_pfn: 851680m			<-- Added a printk
> [    0.000000] Scanning 0 areas for low memory corruption
> [    0.000000] modified physical RAM map:
> [    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
> [    0.000000]  modified: 0000000000010000 - 000000000009f400 (usable)
> [    0.000000]  modified: 000000000009f400 - 0000000000100000 (reserved)
> [    0.000000]  modified: 0000000000100000 - 00000000cfee0000 (usable)
> [    0.000000]  modified: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
> [    0.000000]  modified: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
> [    0.000000]  modified: 00000000cfef0000 - 00000000cff00000 (reserved)
> [    0.000000]  modified: 00000000e0000000 - 00000000f0000000 (reserved)
> [    0.000000]  modified: 00000000fec00000 - 0000000100000000 (reserved)
> [    0.000000]  modified: 0000000100000000 - 0000000130000000 (usable)
> [    0.000000] initial memory mapped : 0 - 20000000
>
> The machine has 4GB, but somehow the max_pfn is set to point to 5.1GB which is
> surely not right. Oh, I am compiling a 64-bit Linux and Xen.
>
>   

Re: pvops dom0 work roadmap

[Konrad Rzeszutek Wilk]

On Wed, Aug 19, 2009 at 12:06:09PM -0700, Jeremy Fitzhardinge wrote:
> On 08/19/09 10:45, Konrad Rzeszutek Wilk wrote:
> > I will retry this, but in the meantime I am tracking balloon accessing non-existent pages:
> >   
> 
> Gianluca mentioned something about this to me.  I think he's looking
> into it.

Oooh. I fired off a patch for this. Not sure if the approach is right - I will
CC him on it.

Re: pvops dom0 work roadmap

[Gianluca Guida]

Konrad Rzeszutek Wilk writes:
 > I will retry this, but in the meantime I am tracking balloon accessing non-existent pages:

Hm, what tree of dom0 kernel are you using? Is commit
7394b25905929a92e51771b832ee67b70ccebcf0 (Revert "Xen: Allow guest to
boot ballooned.") there?

The point is that xen_memory_setup should truncate the ram visible in
the e820 map to xen_start_info->nr_pages, so that the balloon driver
would never try to add pages on boot.

Thanks,
Gianluca


 > 
 > <BEGIN>
 > [    0.239963] xen_balloon: Initialising balloon driver.
 > [    0.240057] xen_ballon: 131072 -> 1245184            <-- added a printk.
 > [    0.257938] BUG: unable to handle kernel [    0.257938] BUG: unable to handle kernel paging requestpaging request at ffffea0002d80028
 >  at ffffea0002d80028
 > [    0.257960] IP:[    0.257960] IP: [<ffffffff81215f7b>] balloon_append+0x13/0x36
 >  [<ffffffff81215f7b>] balloon_append+0x13/0x36
 > [    0.257960] PGD 10402067 [    0.257960] PGD 10402067 PUD 10403067 PUD 10403067 PMD 1301a067 PMD 1301a067 PTE 0PTE 0
 > 
 > [    0.257960] Oops: 0002 [#1] [    0.257960] Oops: 0002 [#1] SMP SMP
 > 
 > [    0.257960] last sysfs file:
 > [    0.257960] last sysfs file:
 > [    0.257960] CPU 0 [    0.257960] CPU 0
 > 
 > [    0.257960] Modules linked in:[    0.257960] Modules linked in:
 > 
 > [    0.257960] Pid: 1, comm: swapper Not tainted 2.6.31-rc5-xen0-23866-g8584ce8-dirty #6 .
 > [    0.257960] Pid: 1, comm: swapper Not tainted 2.6.31-rc5-xen0-23866-g8584ce8-dirty #6 .
 > [    0.257960] RIP: e030:[<ffffffff81215f7b>] [    0.257960] RIP: e030:[<ffffffff81215f7b>]  [<ffffffff81215f7b>] balloon_append+0x13/0x36
 >  [<ffffffff81215f7b>] balloon_append+0x13/0x36
 > [    0.257960] RSP: e02b:ffff88001fc81e70  EFLAGS: 00010282
 > [    0.257960] RSP: e02b:ffff88001fc81e70  EFLAGS: 00010282
 > [    0.257960] RAX: ffffea0002d80028 RBX: 00000000000d0001 RCX: 0000000000000064
 > [    0.257960] RAX: ffffea0002d80028 RBX: 00000000000d0001 RCX: 0000000000000064
 > [    0.257960] RDX: ffffea0002d7fff0 RSI: ffffffff810000df RDI: ffffea0002d80000
 > [    0.257960] RDX: ffffea0002d7fff0 RSI: ffffffff810000df RDI: ffffea0002d80000
 > [    0.257960] RBP: ffff88001fc81e70 R08: 0000000000000000 R09: ffff88001fc38000
 > [    0.257960] RBP: ffff88001fc81e70 R08: 0000000000000000 R09: ffff88001fc38000
 > [    0.257960] R10: ffff88001fc81c20 R11: ffff88001fc81da0 R12: ffffea0002d80038
 > [    0.257960] R10: ffff88001fc81c20 R11: ffff88001fc81da0 R12: ffffea0002d80038
 > [    0.257960] R13: ffffffff816e1907 R14: 0000000000000000 R15: 0000000000000000
 > [    0.257960] R13: ffffffff816e1907 R14: 0000000000000000 R15: 0000000000000000
 > [    0.257960] FS:  0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
 > [    0.257960] FS:  0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
 > [    0.257960] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
 > [    0.257960] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
 > [    0.257960] CR2: ffffea0002d80028 CR3: 0000000001001000 CR4: 0000000000002660
 > [    0.257960] CR2: ffffea0002d80028 CR3: 0000000001001000 CR4: 0000000000002660
 > [    0.257960] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
 > [    0.257960] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
 > [    0.257960] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
 > [    0.257960] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
 > [    0.257960] Process swapper (pid: 1, threadinfo ffff88001fc80000, task ffff88001fc78000)
 > [    0.257960] Process swapper (pid: 1, threadinfo ffff88001fc80000, task ffff88001fc78000)
 > [    0.257960] Stack:
 > [    0.257960] Stack:
 > [    0.257960]  ffff88001fc81ea0[    0.257960]  ffff88001fc81ea0 ffffffff816e1ad0 ffffffff816e1ad0 ffff88001fc81ea0 ffff88001fc81ea0 ffffffff816e18ad ffffffff816e18ad
 > 
 > [    0.257960] <0>[    0.257960] <0> ffffffff817167a8 ffffffff817167a8 0000000000000040 0000000000000040 ffff88001fc81f10 ffff88001fc81f10 ffffffff8100a05c ffffffff8100a05c
 > 
 > [    0.257960] <0>[    0.257960] <0> ffff88001fc81e00 ffff88001fc81e00 ffffffff8108e691 ffffffff8108e691 0000000000003333 0000000000003333 ffffffff81110000 ffffffff81110000
 > 
 > [    0.257960] Call Trace:
 > [    0.257960] Call Trace:
 > [    0.257960]  [<ffffffff816e1ad0>] balloon_init+0x1c9/0x1fd
 > [    0.257960]  [<ffffffff816e1ad0>] balloon_init+0x1c9/0x1fd
 > [    0.257960]  [<ffffffff816e18ad>] ? xenbus_probe_frontend_init+0x53/0x59
 > [    0.257960]  [<ffffffff816e18ad>] ? xenbus_probe_frontend_init+0x53/0x59
 > [    0.257960]  [<ffffffff8100a05c>] do_one_initcall+0x56/0x136
 > [    0.257960]  [<ffffffff8100a05c>] do_one_initcall+0x56/0x136
 > [    0.257960]  [<ffffffff8108e691>] ? register_irq_proc+0xae/0xca
 > [    0.257960]  [<ffffffff8108e691>] ? register_irq_proc+0xae/0xca
 > [    0.257960]  [<ffffffff81110000>] ? elf_core_dump+0x81e/0xc29
 > [    0.257960]  [<ffffffff81110000>] ? elf_core_dump+0x81e/0xc29
 > [    0.257960]  [<ffffffff816bc9aa>] kernel_init+0x15e/0x1b6
 > [    0.257960]  [<ffffffff816bc9aa>] kernel_init+0x15e/0x1b6
 > [    0.257960]  [<ffffffff81012cea>] child_rip+0xa/0x20
 > [    0.257960]  [<ffffffff81012cea>] child_rip+0xa/0x20
 > [    0.257960]  [<ffffffff81011ea7>] ? int_ret_from_sys_call+0x7/0x1b
 > [    0.257960]  [<ffffffff81011ea7>] ? int_ret_from_sys_call+0x7/0x1b
 > [    0.257960]  [<ffffffff8101265d>] ? retint_restore_args+0x5/0x6
 > [    0.257960]  [<ffffffff8101265d>] ? retint_restore_args+0x5/0x6
 > [    0.257960]  [<ffffffff81012ce0>] ? child_rip+0x0/0x20
 > [    0.257960]  [<ffffffff81012ce0>] ? child_rip+0x0/0x20
 > [    0.257960] Code: [    0.257960] Code: 55 55 89 89 ff ff 48 48 89 89 e5 e5 e8 e8 25 25 32 32 df df ff ff c9 c9 c3 c3 55 55 48 48 89 89 e5 e5 e8 e8 5a 5a 32 32 df df ff ff c9 c9 c3 c3 48 48 8b 8b 15 15 d1 d1 0c 0c 43 43 00 00 48 48 8d 8d 47 47 28 28 55 55 48 48 89 89 e5 e5 48 48 89 89 42 42 08 08 <48> <48> 89 89 57 57 28 28 48 48 c7 c7 40 40 08 08 40 40 6c 6c 64 64 81 81 48 48 ff ff 05 05 6a 6a ac ac 60 60 00 00 48 48 ff ff
 > 
 > [    0.257960] RIP [    0.257960] RIP  [<ffffffff81215f7b>] balloon_append+0x13/0x36
 >  [<ffffffff81215f7b>] balloon_append+0x13/0x36
 > [    0.257960]  RSP <ffff88001fc81e70>
 > [    0.257960]  RSP <ffff88001fc81e70>
 > [    0.257960] CR2: ffffea0002d80028
 > [    0.257960] CR2: ffffea0002d80028
 > [    0.257960] ---[ end trace 4eaa2a86a8e2da22 ]---
 > [    0.257960] ---[ end trace 4eaa2a86a8e2da22 ]---
 > <END>
 > 
 > Sorry for the duplicate lines. I think the combination of earlycons and console both pointing
 > to the Xen console driver is screwing this up.
 > 
 > This could be a simple bug with the max_pfn being reset to phantom value:
 > 
 > [    0.000000] BIOS-provided physical RAM map:
 > [    0.000000]  Xen: 0000000000000000 - 000000000009f400 (usable)
 > [    0.000000]  Xen: 000000000009f400 - 0000000000100000 (reserved)
 > [    0.000000]  Xen: 0000000000100000 - 00000000cfee0000 (usable)
 > [    0.000000]  Xen: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
 > [    0.000000]  Xen: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
 > [    0.000000]  Xen: 00000000cfef0000 - 00000000cff00000 (reserved)
 > [    0.000000]  Xen: 00000000e0000000 - 00000000f0000000 (reserved)
 > [    0.000000]  Xen: 00000000fec00000 - 0000000100000000 (reserved)
 > [    0.000000]  Xen: 0000000100000000 - 0000000130000000 (usable)
 > [    0.000000] console [xenboot0] enabled
 > [    0.000000] DMI 2.5 present.
 > [    0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
 > [    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
 > [    0.000000] last_pfn = 0x130000 max_arch_pfn = 0x400000000
 > [    0.000000] max_pfn = 1245184                        <-- Added a printk
 > [    0.000000] num_physpages: 1245184                   <-- Added a printk
 > [    0.000000] Searching for max PFN under 4GB          <-- Added a printk
 > [    0.000000] last_pfn = 0xcfee0 max_arch_pfn = 0x400000000
 > [    0.000000] max_low_pfn: 851680m                     <-- Added a printk
 > [    0.000000] Scanning 0 areas for low memory corruption
 > [    0.000000] modified physical RAM map:
 > [    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
 > [    0.000000]  modified: 0000000000010000 - 000000000009f400 (usable)
 > [    0.000000]  modified: 000000000009f400 - 0000000000100000 (reserved)
 > [    0.000000]  modified: 0000000000100000 - 00000000cfee0000 (usable)
 > [    0.000000]  modified: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
 > [    0.000000]  modified: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
 > [    0.000000]  modified: 00000000cfef0000 - 00000000cff00000 (reserved)
 > [    0.000000]  modified: 00000000e0000000 - 00000000f0000000 (reserved)
 > [    0.000000]  modified: 00000000fec00000 - 0000000100000000 (reserved)
 > [    0.000000]  modified: 0000000100000000 - 0000000130000000 (usable)
 > [    0.000000] initial memory mapped : 0 - 20000000
 > 
 > The machine has 4GB, but somehow the max_pfn is set to point to 5.1GB which is
 > surely not right. Oh, I am compiling a 64-bit Linux and Xen.
 > 
 > _______________________________________________
 > Xen-devel mailing list
 > Xen-devel@lists.xensource.com
 > http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap

[Konrad Rzeszutek Wilk]

On Thu, Aug 20, 2009 at 04:49:08PM +0100, Gianluca Guida wrote:
> Konrad Rzeszutek Wilk writes:
>  > I will retry this, but in the meantime I am tracking balloon accessing non-existent pages:
> 
> Hm, what tree of dom0 kernel are you using? Is commit

[konrad@phenom linux]$ git checkout origin/rebase/master -b boo
Branch boo set up to track remote branch refs/remotes/origin/rebase/master.
Switched to a new branch 'boo'
[konrad@phenom linux]$ git show  7394b25905929a92e51771b832ee67b70ccebcf0
fatal: bad object 7394b25905929a92e51771b832ee67b70ccebcf0

> 7394b25905929a92e51771b832ee67b70ccebcf0 (Revert "Xen: Allow guest to
> boot ballooned.") there?

What branch is it in?

> 
> The point is that xen_memory_setup should truncate the ram visible in
> the e820 map to xen_start_info->nr_pages, so that the balloon driver
> would never try to add pages on boot.

Sure. This problem is for pages above ->nr_pages.

The loop goes from xen_start_info->nr_pages to max_pfn (which is set to
0x130000000 - the last E820 region for a 4GB machine). In the E820
there is a big gap between 0xcfee0000 to 0x100000000 on which
the ballooon driver tries to loop through and dereferncing
the pages. That fails as it seems the mapping for those pages isn't set.
(I haven't actually verified whether the page table has entries for this
or not, but the 'unable to handle kernel paging request' implies it isnt).

> 
> Thanks,
> Gianluca
> 
> 
>  > 
>  > <BEGIN>
>  > [    0.239963] xen_balloon: Initialising balloon driver.
>  > [    0.240057] xen_ballon: 131072 -> 1245184            <-- added a printk.
>  > [    0.257938] BUG: unable to handle kernel [    0.257938] BUG: unable to handle kernel paging requestpaging request at ffffea0002d80028
>  >  at ffffea0002d80028
>  > [    0.257960] IP:[    0.257960] IP: [<ffffffff81215f7b>] balloon_append+0x13/0x36
>  >  [<ffffffff81215f7b>] balloon_append+0x13/0x36
>  > [    0.257960] PGD 10402067 [    0.257960] PGD 10402067 PUD 10403067 PUD 10403067 PMD 1301a067 PMD 1301a067 PTE 0PTE 0
>  > 
>  > [    0.257960] Oops: 0002 [#1] [    0.257960] Oops: 0002 [#1] SMP SMP
>  > 
>  > [    0.257960] last sysfs file:
>  > [    0.257960] last sysfs file:
>  > [    0.257960] CPU 0 [    0.257960] CPU 0
>  > 
>  > [    0.257960] Modules linked in:[    0.257960] Modules linked in:
>  > 
>  > [    0.257960] Pid: 1, comm: swapper Not tainted 2.6.31-rc5-xen0-23866-g8584ce8-dirty #6 .
>  > [    0.257960] Pid: 1, comm: swapper Not tainted 2.6.31-rc5-xen0-23866-g8584ce8-dirty #6 .
>  > [    0.257960] RIP: e030:[<ffffffff81215f7b>] [    0.257960] RIP: e030:[<ffffffff81215f7b>]  [<ffffffff81215f7b>] balloon_append+0x13/0x36
>  >  [<ffffffff81215f7b>] balloon_append+0x13/0x36
>  > [    0.257960] RSP: e02b:ffff88001fc81e70  EFLAGS: 00010282
>  > [    0.257960] RSP: e02b:ffff88001fc81e70  EFLAGS: 00010282
>  > [    0.257960] RAX: ffffea0002d80028 RBX: 00000000000d0001 RCX: 0000000000000064
>  > [    0.257960] RAX: ffffea0002d80028 RBX: 00000000000d0001 RCX: 0000000000000064
>  > [    0.257960] RDX: ffffea0002d7fff0 RSI: ffffffff810000df RDI: ffffea0002d80000
>  > [    0.257960] RDX: ffffea0002d7fff0 RSI: ffffffff810000df RDI: ffffea0002d80000
>  > [    0.257960] RBP: ffff88001fc81e70 R08: 0000000000000000 R09: ffff88001fc38000
>  > [    0.257960] RBP: ffff88001fc81e70 R08: 0000000000000000 R09: ffff88001fc38000
>  > [    0.257960] R10: ffff88001fc81c20 R11: ffff88001fc81da0 R12: ffffea0002d80038
>  > [    0.257960] R10: ffff88001fc81c20 R11: ffff88001fc81da0 R12: ffffea0002d80038
>  > [    0.257960] R13: ffffffff816e1907 R14: 0000000000000000 R15: 0000000000000000
>  > [    0.257960] R13: ffffffff816e1907 R14: 0000000000000000 R15: 0000000000000000
>  > [    0.257960] FS:  0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
>  > [    0.257960] FS:  0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
>  > [    0.257960] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
>  > [    0.257960] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
>  > [    0.257960] CR2: ffffea0002d80028 CR3: 0000000001001000 CR4: 0000000000002660
>  > [    0.257960] CR2: ffffea0002d80028 CR3: 0000000001001000 CR4: 0000000000002660
>  > [    0.257960] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>  > [    0.257960] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>  > [    0.257960] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>  > [    0.257960] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>  > [    0.257960] Process swapper (pid: 1, threadinfo ffff88001fc80000, task ffff88001fc78000)
>  > [    0.257960] Process swapper (pid: 1, threadinfo ffff88001fc80000, task ffff88001fc78000)
>  > [    0.257960] Stack:
>  > [    0.257960] Stack:
>  > [    0.257960]  ffff88001fc81ea0[    0.257960]  ffff88001fc81ea0 ffffffff816e1ad0 ffffffff816e1ad0 ffff88001fc81ea0 ffff88001fc81ea0 ffffffff816e18ad ffffffff816e18ad
>  > 
>  > [    0.257960] <0>[    0.257960] <0> ffffffff817167a8 ffffffff817167a8 0000000000000040 0000000000000040 ffff88001fc81f10 ffff88001fc81f10 ffffffff8100a05c ffffffff8100a05c
>  > 
>  > [    0.257960] <0>[    0.257960] <0> ffff88001fc81e00 ffff88001fc81e00 ffffffff8108e691 ffffffff8108e691 0000000000003333 0000000000003333 ffffffff81110000 ffffffff81110000
>  > 
>  > [    0.257960] Call Trace:
>  > [    0.257960] Call Trace:
>  > [    0.257960]  [<ffffffff816e1ad0>] balloon_init+0x1c9/0x1fd
>  > [    0.257960]  [<ffffffff816e1ad0>] balloon_init+0x1c9/0x1fd
>  > [    0.257960]  [<ffffffff816e18ad>] ? xenbus_probe_frontend_init+0x53/0x59
>  > [    0.257960]  [<ffffffff816e18ad>] ? xenbus_probe_frontend_init+0x53/0x59
>  > [    0.257960]  [<ffffffff8100a05c>] do_one_initcall+0x56/0x136
>  > [    0.257960]  [<ffffffff8100a05c>] do_one_initcall+0x56/0x136
>  > [    0.257960]  [<ffffffff8108e691>] ? register_irq_proc+0xae/0xca
>  > [    0.257960]  [<ffffffff8108e691>] ? register_irq_proc+0xae/0xca
>  > [    0.257960]  [<ffffffff81110000>] ? elf_core_dump+0x81e/0xc29
>  > [    0.257960]  [<ffffffff81110000>] ? elf_core_dump+0x81e/0xc29
>  > [    0.257960]  [<ffffffff816bc9aa>] kernel_init+0x15e/0x1b6
>  > [    0.257960]  [<ffffffff816bc9aa>] kernel_init+0x15e/0x1b6
>  > [    0.257960]  [<ffffffff81012cea>] child_rip+0xa/0x20
>  > [    0.257960]  [<ffffffff81012cea>] child_rip+0xa/0x20
>  > [    0.257960]  [<ffffffff81011ea7>] ? int_ret_from_sys_call+0x7/0x1b
>  > [    0.257960]  [<ffffffff81011ea7>] ? int_ret_from_sys_call+0x7/0x1b
>  > [    0.257960]  [<ffffffff8101265d>] ? retint_restore_args+0x5/0x6
>  > [    0.257960]  [<ffffffff8101265d>] ? retint_restore_args+0x5/0x6
>  > [    0.257960]  [<ffffffff81012ce0>] ? child_rip+0x0/0x20
>  > [    0.257960]  [<ffffffff81012ce0>] ? child_rip+0x0/0x20
>  > [    0.257960] Code: [    0.257960] Code: 55 55 89 89 ff ff 48 48 89 89 e5 e5 e8 e8 25 25 32 32 df df ff ff c9 c9 c3 c3 55 55 48 48 89 89 e5 e5 e8 e8 5a 5a 32 32 df df ff ff c9 c9 c3 c3 48 48 8b 8b 15 15 d1 d1 0c 0c 43 43 00 00 48 48 8d 8d 47 47 28 28 55 55 48 48 89 89 e5 e5 48 48 89 89 42 42 08 08 <48> <48> 89 89 57 57 28 28 48 48 c7 c7 40 40 08 08 40 40 6c 6c 64 64 81 81 48 48 ff ff 05 05 6a 6a ac ac 60 60 00 00 48 48 ff ff
>  > 
>  > [    0.257960] RIP [    0.257960] RIP  [<ffffffff81215f7b>] balloon_append+0x13/0x36
>  >  [<ffffffff81215f7b>] balloon_append+0x13/0x36
>  > [    0.257960]  RSP <ffff88001fc81e70>
>  > [    0.257960]  RSP <ffff88001fc81e70>
>  > [    0.257960] CR2: ffffea0002d80028
>  > [    0.257960] CR2: ffffea0002d80028
>  > [    0.257960] ---[ end trace 4eaa2a86a8e2da22 ]---
>  > [    0.257960] ---[ end trace 4eaa2a86a8e2da22 ]---
>  > <END>
>  > 
>  > Sorry for the duplicate lines. I think the combination of earlycons and console both pointing
>  > to the Xen console driver is screwing this up.
>  > 
>  > This could be a simple bug with the max_pfn being reset to phantom value:
>  > 
>  > [    0.000000] BIOS-provided physical RAM map:
>  > [    0.000000]  Xen: 0000000000000000 - 000000000009f400 (usable)
>  > [    0.000000]  Xen: 000000000009f400 - 0000000000100000 (reserved)
>  > [    0.000000]  Xen: 0000000000100000 - 00000000cfee0000 (usable)
>  > [    0.000000]  Xen: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
>  > [    0.000000]  Xen: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
>  > [    0.000000]  Xen: 00000000cfef0000 - 00000000cff00000 (reserved)
>  > [    0.000000]  Xen: 00000000e0000000 - 00000000f0000000 (reserved)
>  > [    0.000000]  Xen: 00000000fec00000 - 0000000100000000 (reserved)
>  > [    0.000000]  Xen: 0000000100000000 - 0000000130000000 (usable)
>  > [    0.000000] console [xenboot0] enabled
>  > [    0.000000] DMI 2.5 present.
>  > [    0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
>  > [    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
>  > [    0.000000] last_pfn = 0x130000 max_arch_pfn = 0x400000000
>  > [    0.000000] max_pfn = 1245184                        <-- Added a printk
>  > [    0.000000] num_physpages: 1245184                   <-- Added a printk
>  > [    0.000000] Searching for max PFN under 4GB          <-- Added a printk
>  > [    0.000000] last_pfn = 0xcfee0 max_arch_pfn = 0x400000000
>  > [    0.000000] max_low_pfn: 851680m                     <-- Added a printk
>  > [    0.000000] Scanning 0 areas for low memory corruption
>  > [    0.000000] modified physical RAM map:
>  > [    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
>  > [    0.000000]  modified: 0000000000010000 - 000000000009f400 (usable)
>  > [    0.000000]  modified: 000000000009f400 - 0000000000100000 (reserved)
>  > [    0.000000]  modified: 0000000000100000 - 00000000cfee0000 (usable)
>  > [    0.000000]  modified: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
>  > [    0.000000]  modified: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
>  > [    0.000000]  modified: 00000000cfef0000 - 00000000cff00000 (reserved)
>  > [    0.000000]  modified: 00000000e0000000 - 00000000f0000000 (reserved)
>  > [    0.000000]  modified: 00000000fec00000 - 0000000100000000 (reserved)
>  > [    0.000000]  modified: 0000000100000000 - 0000000130000000 (usable)
>  > [    0.000000] initial memory mapped : 0 - 20000000
>  > 
>  > The machine has 4GB, but somehow the max_pfn is set to point to 5.1GB which is
>  > surely not right. Oh, I am compiling a 64-bit Linux and Xen.
>  > 
>  > _______________________________________________
>  > Xen-devel mailing list
>  > Xen-devel@lists.xensource.com
>  > http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap

[Gianluca Guida]

Konrad Rzeszutek Wilk writes:
 > On Thu, Aug 20, 2009 at 04:49:08PM +0100, Gianluca Guida wrote:
 > > Konrad Rzeszutek Wilk writes:
 > >  > I will retry this, but in the meantime I am tracking balloon accessing non-existent pages:
 > > 
 > > Hm, what tree of dom0 kernel are you using? Is commit
 > 
 > [konrad@phenom linux]$ git checkout origin/rebase/master -b boo
 > Branch boo set up to track remote branch refs/remotes/origin/rebase/master.
 > Switched to a new branch 'boo'
 > [konrad@phenom linux]$ git show  7394b25905929a92e51771b832ee67b70ccebcf0
 > fatal: bad object 7394b25905929a92e51771b832ee67b70ccebcf0

Ok, you don't have the revert, do you have
a472909fe0e3b7bfa34f7c9dd748121b0ede0ee6 in your tree?

 > 
 > > 7394b25905929a92e51771b832ee67b70ccebcf0 (Revert "Xen: Allow guest to
 > > boot ballooned.") there?
 > 
 > What branch is it in?

rebase/master, checked in last week.

 > 
 > > 
 > > The point is that xen_memory_setup should truncate the ram visible in
 > > the e820 map to xen_start_info->nr_pages, so that the balloon driver
 > > would never try to add pages on boot.
 > 
 > Sure. This problem is for pages above ->nr_pages.

max_pfn is calculated by the e820 map, so there would be nothing above
nr_pages.

I was assuming you had an up-to-date tree, where there's no "Allow
guest to boot ballooned" patch. When that patch is present no
truncation happens, and you get hit by that bug, which your patch
fixes.

Cheers,
Gianluca

Re: pvops dom0 work roadmap

[Konrad Rzeszutek Wilk]

On Thu, Aug 20, 2009 at 05:36:01PM +0100, Gianluca Guida wrote:
> Konrad Rzeszutek Wilk writes:
>  > On Thu, Aug 20, 2009 at 04:49:08PM +0100, Gianluca Guida wrote:
>  > > Konrad Rzeszutek Wilk writes:
>  > >  > I will retry this, but in the meantime I am tracking balloon accessing non-existent pages:
>  > > 
>  > > Hm, what tree of dom0 kernel are you using? Is commit
>  > 
>  > [konrad@phenom linux]$ git checkout origin/rebase/master -b boo
>  > Branch boo set up to track remote branch refs/remotes/origin/rebase/master.
>  > Switched to a new branch 'boo'
>  > [konrad@phenom linux]$ git show  7394b25905929a92e51771b832ee67b70ccebcf0
>  > fatal: bad object 7394b25905929a92e51771b832ee67b70ccebcf0
> 
> Ok, you don't have the revert, do you have
> a472909fe0e3b7bfa34f7c9dd748121b0ede0ee6 in your tree?

Yes.

> 
>  > 
>  > > 7394b25905929a92e51771b832ee67b70ccebcf0 (Revert "Xen: Allow guest to
>  > > boot ballooned.") there?
>  > 
>  > What branch is it in?
> 
> rebase/master, checked in last week.

Hmmm. Let me checkout a new tree and see why I am behind.

> 
>  > 
>  > > 
>  > > The point is that xen_memory_setup should truncate the ram visible in
>  > > the e820 map to xen_start_info->nr_pages, so that the balloon driver
>  > > would never try to add pages on boot.
>  > 
>  > Sure. This problem is for pages above ->nr_pages.
> 
> max_pfn is calculated by the e820 map, so there would be nothing above
> nr_pages.

Duh! Yes

> 
> I was assuming you had an up-to-date tree, where there's no "Allow
> guest to boot ballooned" patch. When that patch is present no
> truncation happens, and you get hit by that bug, which your patch
> fixes.
> 
> Cheers,
> Gianluca

Re: pvops dom0 work roadmap

[M A Young]

On Tue, 18 Aug 2009, Jeremy Fitzhardinge wrote:

>    * make sure rebase/master is fairly functional and somewhat stable
>    * rename rebase/* to xen/*
>    * use it as the baseline dom0 and domU kernel in xen-unstable

I have had problems booting rebase/master on i686 for some time now. The 
most recent crash looks different, and might be a STACKPROTECTOR issue 
(which I just turned back on). The log ends

(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input 
to Xen)
(XEN) Freed 116kB init memory.
(XEN) d0:v0: unhandled page fault (ec=0000)
(XEN) Pagetable walk from 00000014:
(XEN)  L3[0x000] = 000000001bc03001 00001c03
(XEN)  L2[0x000] = 0000000000000000 ffffffff
(XEN) domain_crash_sync called from entry.S (ff1b1cbe)
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.4.1  x86_32p  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e019:[<c0aaa9d0>]
(XEN) EFLAGS: 00000282   EM: 1   CONTEXT: pv guest
(XEN) eax: 00000000   ebx: 00000000   ecx: 00000007   edx: 00000000
(XEN) esi: c0ae739c   edi: c0a147b8   ebp: c0aa1fd4   esp: c0aa1fb8
(XEN) cr0: 8005003b   cr4: 000006f0   cr3: 1bc02000   cr2: 00000014
(XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
(XEN) Guest stack trace from esp=c0aa1fb8:
(XEN)    00000000 c0aaa9d0 0001e019 00010082 00000000 c0ae739c c0a1492c 
c0aa1ffc(XEN)    c0aa974f 00000000 00000000 00000000 00000000 00000000 
00000000 c1c01000(XEN)    00000000 00000000 c0834676 c083467e c0aa9f32 
c04053ad c04056bf c04059c2(XEN)    c0405bf1 c0405c95 c0405f6b c0405fec 
c04062c2 c04063e6 c0406a1f c0aaaa82(XEN)    c0aaaa8a c0834728 c0834828 
c0834859 c0408e6c c0408e7e c0408f07 c04090fc(XEN)    c0409141 c0409208 
c0409767 c0409ad3 c0409b18 c0409b2a c040a156 c040a79f(XEN)    c040a7c6 
c040acc2 c0aab563 c0aab60b c084093f c0840a1d c0840c6b c040db7f(XEN) 
c0840fda c0841079 c0841099 c0aabcfc c0aabd04 c040e8f5 c040eb1e 
c0aac573(XEN)    c0aad580 c0aad588 c04103b7 c04103c5 c041044b c0410459 
c0aaf678 c0aaf68b(XEN)    c041174d c04117ea c0411b45 c0411bfe c0411c50 
c0411c76 c0411f2f c041218d(XEN)    c04124c5 c04124f1 c0413760 c0413bab 
c0413e46 c0413e50 c0414649 c0414651(XEN)    c0414659 c041477f c0414807 
c0414816 c0414824 c041488f c083508f c0835218(XEN)    c0835279 c0835294 
c0835940 c0835a5c c0835b28 c0835cef c0aafe60 c0aafe68(XEN)    c0aafe7a 
c0aafe82 c0aafe8a c0aafe92 c0aafea4 c0aafeac c0aafed2 c0aafeda(XEN) 
c0aaff4f c0aaff57 c0835f91 c083624a c08362e4 c0836876 c0836911 
c083695c(XEN)    c0836a56 c0836a5b c0836b5e c0836ba0 c0836ba5 c0836baa 
c0836bc4 c0836cbb(XEN)    c0836d37 c0836de9 c0836df7 c0836e1c c0836e26 
c0836e42 c0836eb1 c0836ebb(XEN)    c0836f1e c0836f23 c0836f28 c0836f2d 
c0836f32 c0836f51 c0836f5d c0836f7e(XEN)    c0836f87 c0836f90 c083708e 
c0837093 c08370b2 c08370e2 c0837152 c08371a9(XEN)    c08371ae c08373bd 
c0837428 c08374b8 c08374c4 c0837593 c08375a4 c083769d(XEN) Domain 0 
crashed: rebooting machine in 5 seconds.

 	Michael Young

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/19/09 08:27, M A Young wrote:
> On Tue, 18 Aug 2009, Jeremy Fitzhardinge wrote:
>
>>    * make sure rebase/master is fairly functional and somewhat stable
>>    * rename rebase/* to xen/*
>>    * use it as the baseline dom0 and domU kernel in xen-unstable
>
> I have had problems booting rebase/master on i686 for some time now.
> The most recent crash looks different, and might be a STACKPROTECTOR
> issue (which I just turned back on). The log ends

What happens before then?  What stage is it at?

> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen)
> (XEN) Freed 116kB init memory.
> (XEN) d0:v0: unhandled page fault (ec=0000)
> (XEN) Pagetable walk from 00000014:
> (XEN)  L3[0x000] = 000000001bc03001 00001c03
> (XEN)  L2[0x000] = 0000000000000000 ffffffff
> (XEN) domain_crash_sync called from entry.S (ff1b1cbe)
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-3.4.1  x86_32p  debug=n  Not tainted ]----
> (XEN) CPU:    0
> (XEN) EIP:    e019:[<c0aaa9d0>]

What does this correspond to?

> (XEN) EFLAGS: 00000282   EM: 1   CONTEXT: pv guest
> (XEN) eax: 00000000   ebx: 00000000   ecx: 00000007   edx: 00000000
> (XEN) esi: c0ae739c   edi: c0a147b8   ebp: c0aa1fd4   esp: c0aa1fb8
> (XEN) cr0: 8005003b   cr4: 000006f0   cr3: 1bc02000   cr2: 00000014
> (XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
> (XEN) Guest stack trace from esp=c0aa1fb8:
> (XEN)    00000000 c0aaa9d0 0001e019 00010082 00000000 c0ae739c
> c0a1492c c0aa1ffc(XEN)    c0aa974f 00000000 00000000 00000000 00000000
> 00000000 00000000 c1c01000(XEN)    00000000 00000000 c0834676 c083467e
> c0aa9f32 c04053ad c04056bf c04059c2(XEN)    c0405bf1 c0405c95 c0405f6b
> c0405fec c04062c2 c04063e6 c0406a1f c0aaaa82(XEN)    c0aaaa8a c0834728
> c0834828 c0834859 c0408e6c c0408e7e c0408f07 c04090fc(XEN)    c0409141
> c0409208 c0409767 c0409ad3 c0409b18 c0409b2a c040a156 c040a79f(XEN)   
> c040a7c6 c040acc2 c0aab563 c0aab60b c084093f c0840a1d c0840c6b
> c040db7f(XEN) c0840fda c0841079 c0841099 c0aabcfc c0aabd04 c040e8f5
> c040eb1e c0aac573(XEN)    c0aad580 c0aad588 c04103b7 c04103c5 c041044b
> c0410459 c0aaf678 c0aaf68b(XEN)    c041174d c04117ea c0411b45 c0411bfe
> c0411c50 c0411c76 c0411f2f c041218d(XEN)    c04124c5 c04124f1 c0413760
> c0413bab c0413e46 c0413e50 c0414649 c0414651(XEN)    c0414659 c041477f
> c0414807 c0414816 c0414824 c041488f c083508f c0835218(XEN)    c0835279
> c0835294 c0835940 c0835a5c c0835b28 c0835cef c0aafe60 c0aafe68(XEN)   
> c0aafe7a c0aafe82 c0aafe8a c0aafe92 c0aafea4 c0aafeac c0aafed2
> c0aafeda(XEN) c0aaff4f c0aaff57 c0835f91 c083624a c08362e4 c0836876
> c0836911 c083695c(XEN)    c0836a56 c0836a5b c0836b5e c0836ba0 c0836ba5
> c0836baa c0836bc4 c0836cbb(XEN)    c0836d37 c0836de9 c0836df7 c0836e1c
> c0836e26 c0836e42 c0836eb1 c0836ebb(XEN)    c0836f1e c0836f23 c0836f28
> c0836f2d c0836f32 c0836f51 c0836f5d c0836f7e(XEN)    c0836f87 c0836f90
> c083708e c0837093 c08370b2 c08370e2 c0837152 c08371a9(XEN)    c08371ae
> c08373bd c0837428 c08374b8 c08374c4 c0837593 c08375a4 c083769d(XEN)
> Domain 0 crashed: rebooting machine in 5 seconds.

Thanks,
    J

Re: pvops dom0 work roadmap

[M A Young]

On Wed, 19 Aug 2009, Jeremy Fitzhardinge wrote:

> On 08/19/09 08:27, M A Young wrote:
>> On Tue, 18 Aug 2009, Jeremy Fitzhardinge wrote:
>>
>>>    * make sure rebase/master is fairly functional and somewhat stable
>>>    * rename rebase/* to xen/*
>>>    * use it as the baseline dom0 and domU kernel in xen-unstable
>>
>> I have had problems booting rebase/master on i686 for some time now.
>> The most recent crash looks different, and might be a STACKPROTECTOR
>> issue (which I just turned back on). The log ends
>
> What happens before then?  What stage is it at?

The previous problem gets a bit further, then reboots (in earlier builds I 
think it hung) after
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input 
to Xen)
(XEN) Freed 116kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) ioapic_guest_write: apic=0, pin=0, old_irq=0, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900
(XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900
(XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!


>> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
>> input to Xen)
>> (XEN) Freed 116kB init memory.
>> (XEN) d0:v0: unhandled page fault (ec=0000)
>> (XEN) Pagetable walk from 00000014:
>> (XEN)  L3[0x000] = 000000001bc03001 00001c03
>> (XEN)  L2[0x000] = 0000000000000000 ffffffff
>> (XEN) domain_crash_sync called from entry.S (ff1b1cbe)
>> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
>> (XEN) ----[ Xen-3.4.1  x86_32p  debug=n  Not tainted ]----
>> (XEN) CPU:    0
>> (XEN) EIP:    e019:[<c0aaa9d0>]
>
> What does this correspond to?

(gdb) x/i 0xc0aaa9d0
0xc0aaa9d0 <xen_init_irq_ops+23>:	mov    %gs:0x14,%eax
the context is
0xc0aaa9b9 <xen_init_irq_ops>:	push   %ebp
0xc0aaa9ba <xen_init_irq_ops+1>:	mov    $0x7,%ecx
0xc0aaa9bf <xen_init_irq_ops+6>:	mov    %esp,%ebp
0xc0aaa9c1 <xen_init_irq_ops+8>:	push   %edi
0xc0aaa9c2 <xen_init_irq_ops+9>:	mov    $0xc0a147b8,%edi
0xc0aaa9c7 <xen_init_irq_ops+14>:	push   %esi
0xc0aaa9c8 <xen_init_irq_ops+15>:	mov    $0xc0ae739c,%esi
0xc0aaa9cd <xen_init_irq_ops+20>:	sub    $0x4,%esp
0xc0aaa9d0 <xen_init_irq_ops+23>:	mov    %gs:0x14,%eax
0xc0aaa9d6 <xen_init_irq_ops+29>:	mov    %eax,-0xc(%ebp)
0xc0aaa9d9 <xen_init_irq_ops+32>:	xor    %eax,%eax
0xc0aaa9db <xen_init_irq_ops+34>:	rep movsl %ds:(%esi),%es:(%edi)
0xc0aaa9dd <xen_init_irq_ops+36>:	mov    -0xc(%ebp),%eax
0xc0aaa9e0 <xen_init_irq_ops+39>:	xor    %gs:0x14,%eax
0xc0aaa9e7 <xen_init_irq_ops+46>:	je     0xc0aaa9ee <xen_init_irq_ops+53>

 	Michael Young

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/19/09 10:35, M A Young wrote:
> On Wed, 19 Aug 2009, Jeremy Fitzhardinge wrote:
>
>> On 08/19/09 08:27, M A Young wrote:
>>> On Tue, 18 Aug 2009, Jeremy Fitzhardinge wrote:
>>>
>>>>    * make sure rebase/master is fairly functional and somewhat stable
>>>>    * rename rebase/* to xen/*
>>>>    * use it as the baseline dom0 and domU kernel in xen-unstable
>>>
>>> I have had problems booting rebase/master on i686 for some time now.
>>> The most recent crash looks different, and might be a STACKPROTECTOR
>>> issue (which I just turned back on). The log ends
>>
>> What happens before then?  What stage is it at?
>
> The previous problem gets a bit further, then reboots (in earlier
> builds I think it hung) after
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen)
> (XEN) Freed 116kB init memory.
> mapping kernel into physical memory
> Xen: setup ISA identity maps
> about to get started...
> (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=0, new_irq=-1
> (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900
> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
> (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1
> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900
> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
>
>
>>> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
>>> input to Xen)
>>> (XEN) Freed 116kB init memory.
>>> (XEN) d0:v0: unhandled page fault (ec=0000)
>>> (XEN) Pagetable walk from 00000014:
>>> (XEN)  L3[0x000] = 000000001bc03001 00001c03
>>> (XEN)  L2[0x000] = 0000000000000000 ffffffff
>>> (XEN) domain_crash_sync called from entry.S (ff1b1cbe)
>>> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
>>> (XEN) ----[ Xen-3.4.1  x86_32p  debug=n  Not tainted ]----
>>> (XEN) CPU:    0
>>> (XEN) EIP:    e019:[<c0aaa9d0>]
>>
>> What does this correspond to?
>
> (gdb) x/i 0xc0aaa9d0
> 0xc0aaa9d0 <xen_init_irq_ops+23>:    mov    %gs:0x14,%eax

Ah, right, stackprotector.  Please try the patches below (or try current
rebase/master).

    J

>From 3576935da8f4eeb0de6a3d7bd31b2422d39de30d Mon Sep 17 00:00:00 2001
From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Mon, 17 Aug 2009 12:25:41 -0700
Subject: [PATCH] x86: make sure load_percpu_segment has no stackprotector

load_percpu_segment() is used to set up the per-cpu segment registers,
which are also used for -fstack-protector.  Make sure that the
load_percpu_segment() function doesn't have stackprotector enabled.

[ Impact: allow percpu setup before calling stack-protected functions ]

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

diff --git a/arch/x86/kernel/cpu/Makefile b/arch/x86/kernel/cpu/Makefile
index 3efcb2b..c1f253d 100644
--- a/arch/x86/kernel/cpu/Makefile
+++ b/arch/x86/kernel/cpu/Makefile
@@ -7,6 +7,10 @@ ifdef CONFIG_FUNCTION_TRACER
 CFLAGS_REMOVE_common.o = -pg
 endif
 
+# Make sure load_percpu_segment has no stackprotector
+nostackp := $(call cc-option, -fno-stack-protector)
+CFLAGS_common.o		:= $(nostackp)
+
 obj-y			:= intel_cacheinfo.o addon_cpuid_features.o
 obj-y			+= proc.o capflags.o powerflags.o common.o
 obj-y			+= vmware.o hypervisor.o


>From ea1ea74befd78dc8386bc9619ebc045de69a4b3c Mon Sep 17 00:00:00 2001
From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Mon, 17 Aug 2009 12:26:53 -0700
Subject: [PATCH] xen: rearrange things to fix stackprotector

Make sure the stack-protector segment registers are properly set up
before calling any functions which may have stack-protection compiled
into them.

[ Impact: prevent Xen early-boot crash when stack-protector is enabled ]
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

diff --git a/arch/x86/xen/Makefile b/arch/x86/xen/Makefile
index 172438f..7410640 100644
--- a/arch/x86/xen/Makefile
+++ b/arch/x86/xen/Makefile
@@ -5,6 +5,10 @@ CFLAGS_REMOVE_time.o = -pg
 CFLAGS_REMOVE_irq.o = -pg
 endif
 
+# Make sure early boot has no stackprotector
+nostackp := $(call cc-option, -fno-stack-protector)
+CFLAGS_enlighten.o		:= $(nostackp)
+
 obj-y		:= enlighten.o setup.o multicalls.o mmu.o irq.o \
 			time.o xen-asm.o xen-asm_$(BITS).o \
 			grant-table.o suspend.o
diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index 121f272..c55ea67 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -984,10 +984,6 @@ asmlinkage void __init xen_start_kernel(void)
 
 	xen_domain_type = XEN_PV_DOMAIN;
 
-	BUG_ON(memcmp(xen_start_info->magic, "xen-3", 5) != 0);
-
-	xen_setup_features();
-
 	/* Install Xen paravirt ops */
 	pv_info = xen_info;
 	pv_init_ops = xen_init_ops;
@@ -996,8 +992,15 @@ asmlinkage void __init xen_start_kernel(void)
 	pv_apic_ops = xen_apic_ops;
 	pv_mmu_ops = xen_mmu_ops;
 
-	xen_init_irq_ops();
+#ifdef CONFIG_X86_64
+	/*
+	 * Setup percpu state.  We only need to do this for 64-bit
+	 * because 32-bit already has %fs set properly.
+	 */
+	load_percpu_segment(0);
+#endif
 
+	xen_init_irq_ops();
 	xen_init_cpuid_mask();
 
 #ifdef CONFIG_X86_LOCAL_APIC
@@ -1007,6 +1010,8 @@ asmlinkage void __init xen_start_kernel(void)
 	set_xen_basic_apic_ops();
 #endif
 
+	xen_setup_features();
+
 	if (xen_feature(XENFEAT_mmu_pt_update_preserve_ad)) {
 		pv_mmu_ops.ptep_modify_prot_start = xen_ptep_modify_prot_start;
 		pv_mmu_ops.ptep_modify_prot_commit = xen_ptep_modify_prot_commit;
@@ -1014,13 +1019,6 @@ asmlinkage void __init xen_start_kernel(void)
 
 	machine_ops = xen_machine_ops;
 
-#ifdef CONFIG_X86_64
-	/*
-	 * Setup percpu state.  We only need to do this for 64-bit
-	 * because 32-bit already has %fs set properly.
-	 */
-	load_percpu_segment(0);
-#endif
 	/*
 	 * The only reliable way to retain the initial address of the
 	 * percpu gdt_page is to remember it here, so we can go and

Re: pvops dom0 work roadmap

[M A Young]

On Wed, 19 Aug 2009, Jeremy Fitzhardinge wrote:

>>>> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
>>>> input to Xen)
>>>> (XEN) Freed 116kB init memory.
>>>> (XEN) d0:v0: unhandled page fault (ec=0000)
>>>> (XEN) Pagetable walk from 00000014:
>>>> (XEN)  L3[0x000] = 000000001bc03001 00001c03
>>>> (XEN)  L2[0x000] = 0000000000000000 ffffffff
>>>> (XEN) domain_crash_sync called from entry.S (ff1b1cbe)
>>>> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
>>>> (XEN) ----[ Xen-3.4.1  x86_32p  debug=n  Not tainted ]----
>>>> (XEN) CPU:    0
>>>> (XEN) EIP:    e019:[<c0aaa9d0>]
>>>
>>> What does this correspond to?
>>
>> (gdb) x/i 0xc0aaa9d0
>> 0xc0aaa9d0 <xen_init_irq_ops+23>:    mov    %gs:0x14,%eax
>
> Ah, right, stackprotector.  Please try the patches below (or try current
> rebase/master).

That doesn't help. Perhaps this is because xen_init_irq_ops is in irq.c, 
not enlighten.c though I am at a bit of a loss why stackprotector should 
care about that code segment anyway.

 	Michael Young

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/20/09 03:43, M A Young wrote:
>> Ah, right, stackprotector.  Please try the patches below (or try current
>> rebase/master).
>
>
> That doesn't help. Perhaps this is because xen_init_irq_ops is in
> irq.c, not enlighten.c though I am at a bit of a loss why
> stackprotector should care about that code segment anyway.

On i386, if %gs hasn't been loaded properly then using it as a base for
a memory access will GP.

Try this:

diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index 2e58099..3ebcbb2 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -51,6 +51,7 @@
 #include <asm/pgtable.h>
 #include <asm/tlbflush.h>
 #include <asm/reboot.h>
+#include <asm/stackprotector.h>
 
 #include "xen-ops.h"
 #include "mmu.h"
@@ -1013,13 +1014,8 @@ asmlinkage void __init xen_start_kernel(void)
 	pv_apic_ops = xen_apic_ops;
 	pv_mmu_ops = xen_mmu_ops;
 
-#ifdef CONFIG_X86_64
-	/*
-	 * Setup percpu state.  We only need to do this for 64-bit
-	 * because 32-bit already has %fs set properly.
-	 */
-	load_percpu_segment(0);
-#endif
+	setup_stack_canary_segment(0);
+	switch_to_new_gdt(0);
 
 	xen_init_irq_ops();
 	xen_init_cpuid_mask();

Thanks,
	J

Re: pvops dom0 work roadmap

[M A Young]

On Thu, 20 Aug 2009, Jeremy Fitzhardinge wrote:

> On i386, if %gs hasn't been loaded properly then using it as a base for
> a memory access will GP.
>
> Try this:
>
> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> index 2e58099..3ebcbb2 100644
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -51,6 +51,7 @@
> #include <asm/pgtable.h>
> #include <asm/tlbflush.h>
> #include <asm/reboot.h>
> +#include <asm/stackprotector.h>
>
> #include "xen-ops.h"
> #include "mmu.h"
> @@ -1013,13 +1014,8 @@ asmlinkage void __init xen_start_kernel(void)
> 	pv_apic_ops = xen_apic_ops;
> 	pv_mmu_ops = xen_mmu_ops;
>
> -#ifdef CONFIG_X86_64
> -	/*
> -	 * Setup percpu state.  We only need to do this for 64-bit
> -	 * because 32-bit already has %fs set properly.
> -	 */
> -	load_percpu_segment(0);
> -#endif
> +	setup_stack_canary_segment(0);
> +	switch_to_new_gdt(0);
>
> 	xen_init_irq_ops();
> 	xen_init_cpuid_mask();

It crashes with this patch (x86_64 also crashes) as follows

(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input 
to Xen)
(XEN) Freed 116kB init memory.
(XEN) d0:v0: unhandled page fault (ec=0000)
(XEN) Pagetable walk from 00000014:
(XEN)  L3[0x000] = 000000003a032001 00002032
(XEN)  L2[0x000] = 0000000000000000 ffffffff
(XEN) domain_crash_sync called from entry.S (ff1b221e)
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.4.1  x86_32p  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e019:[<c04064cc>]
(XEN) EFLAGS: 00000282   EM: 1   CONTEXT: pv guest
(XEN) eax: c0b1c0e0   ebx: c0b1c0e0   ecx: 00000010   edx: 0000001c
(XEN) esi: c0aa3fd8   edi: c0a1592c   ebp: c0aa3fb8   esp: c0aa3f94
(XEN) cr0: 8005003b   cr4: 000006f0   cr3: 3a031000   cr2: 00000014
(XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
(XEN) Guest stack trace from esp=c0aa3f94:
(XEN)    00000000 c04064cc 0001e019 00010082 00000000 00000000 00000010 
c0aa3fd8

(XEN)    c0a1592c c0aa3fcc c0403e3f 00000010 c0ae93f4 c0a1592c c0aa3ffc 
c0aab798

(XEN)    00000010 e0f00018 c04090b1 00000000 00000000 00000000 00000000 
00000000

(XEN)    c2030000 00000000 00000000
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.

The instruction and context is
(gdb) x/i 0xc04064cc
0xc04064cc <arbitrary_virt_to_machine+16>:	mov    %gs:0x14,%eax
(gdb) x/15i arbitrary_virt_to_machine
0xc04064bc <arbitrary_virt_to_machine>:	push   %ebp
0xc04064bd <arbitrary_virt_to_machine+1>:	mov    %esp,%ebp
0xc04064bf <arbitrary_virt_to_machine+3>:	push   %edi
0xc04064c0 <arbitrary_virt_to_machine+4>:	push   %esi
0xc04064c1 <arbitrary_virt_to_machine+5>:	push   %ebx
0xc04064c2 <arbitrary_virt_to_machine+6>:	sub    $0x8,%esp
0xc04064c5 <arbitrary_virt_to_machine+9>:	call   0xc040bc14 <mcount>
0xc04064ca <arbitrary_virt_to_machine+14>:	mov    %eax,%ebx
0xc04064cc <arbitrary_virt_to_machine+16>:	mov    %gs:0x14,%eax
0xc04064d2 <arbitrary_virt_to_machine+22>:	mov    %eax,-0x10(%ebp)
0xc04064d5 <arbitrary_virt_to_machine+25>:	xor    %eax,%eax
0xc04064d7 <arbitrary_virt_to_machine+27>:	mov    %ebx,%eax
0xc04064d9 <arbitrary_virt_to_machine+29>:
     call   0xc042f95c <__virt_addr_valid>
0xc04064de <arbitrary_virt_to_machine+34>:	test   %al,%al
0xc04064e0 <arbitrary_virt_to_machine+36>:
     je     0xc040650e <arbitrary_virt_to_machine+82>

 	Michael Young

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/20/09 16:17, M A Young wrote:
> On Thu, 20 Aug 2009, Jeremy Fitzhardinge wrote:
>
>> On i386, if %gs hasn't been loaded properly then using it as a base for
>> a memory access will GP.
>>
>> Try this:
>>
>> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
>> index 2e58099..3ebcbb2 100644
>> --- a/arch/x86/xen/enlighten.c
>> +++ b/arch/x86/xen/enlighten.c
>> @@ -51,6 +51,7 @@
>> #include <asm/pgtable.h>
>> #include <asm/tlbflush.h>
>> #include <asm/reboot.h>
>> +#include <asm/stackprotector.h>
>>
>> #include "xen-ops.h"
>> #include "mmu.h"
>> @@ -1013,13 +1014,8 @@ asmlinkage void __init xen_start_kernel(void)
>>     pv_apic_ops = xen_apic_ops;
>>     pv_mmu_ops = xen_mmu_ops;
>>
>> -#ifdef CONFIG_X86_64
>> -    /*
>> -     * Setup percpu state.  We only need to do this for 64-bit
>> -     * because 32-bit already has %fs set properly.
>> -     */
>> -    load_percpu_segment(0);
>> -#endif
>> +    setup_stack_canary_segment(0);
>> +    switch_to_new_gdt(0);
>>
>>     xen_init_irq_ops();
>>     xen_init_cpuid_mask();
>
> It crashes with this patch (x86_64 also crashes) as follows

Yeah that was a bit of a shot in the dark; I'd been avoiding setting the
GDT that early because its all a bit fragile, and aside from
stack-protector we can get away with Xen's GDT for quite a while.

Hm, its pretty fiddly...  Let me see what I can come up with.

>
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen)
> (XEN) Freed 116kB init memory.
> (XEN) d0:v0: unhandled page fault (ec=0000)
> (XEN) Pagetable walk from 00000014:
> (XEN)  L3[0x000] = 000000003a032001 00002032
> (XEN)  L2[0x000] = 0000000000000000 ffffffff
> (XEN) domain_crash_sync called from entry.S (ff1b221e)
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-3.4.1  x86_32p  debug=n  Not tainted ]----
> (XEN) CPU:    0
> (XEN) EIP:    e019:[<c04064cc>]
> (XEN) EFLAGS: 00000282   EM: 1   CONTEXT: pv guest
> (XEN) eax: c0b1c0e0   ebx: c0b1c0e0   ecx: 00000010   edx: 0000001c
> (XEN) esi: c0aa3fd8   edi: c0a1592c   ebp: c0aa3fb8   esp: c0aa3f94
> (XEN) cr0: 8005003b   cr4: 000006f0   cr3: 3a031000   cr2: 00000014
> (XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
> (XEN) Guest stack trace from esp=c0aa3f94:
> (XEN)    00000000 c04064cc 0001e019 00010082 00000000 00000000
> 00000010 c0aa3fd8
>
> (XEN)    c0a1592c c0aa3fcc c0403e3f 00000010 c0ae93f4 c0a1592c
> c0aa3ffc c0aab798
>
> (XEN)    00000010 e0f00018 c04090b1 00000000 00000000 00000000
> 00000000 00000000
>
> (XEN)    c2030000 00000000 00000000
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
>
> The instruction and context is
> (gdb) x/i 0xc04064cc
> 0xc04064cc <arbitrary_virt_to_machine+16>:    mov    %gs:0x14,%eax
> (gdb) x/15i arbitrary_virt_to_machine
> 0xc04064bc <arbitrary_virt_to_machine>:    push   %ebp
> 0xc04064bd <arbitrary_virt_to_machine+1>:    mov    %esp,%ebp
> 0xc04064bf <arbitrary_virt_to_machine+3>:    push   %edi
> 0xc04064c0 <arbitrary_virt_to_machine+4>:    push   %esi
> 0xc04064c1 <arbitrary_virt_to_machine+5>:    push   %ebx
> 0xc04064c2 <arbitrary_virt_to_machine+6>:    sub    $0x8,%esp
> 0xc04064c5 <arbitrary_virt_to_machine+9>:    call   0xc040bc14 <mcount>
> 0xc04064ca <arbitrary_virt_to_machine+14>:    mov    %eax,%ebx
> 0xc04064cc <arbitrary_virt_to_machine+16>:    mov    %gs:0x14,%eax
> 0xc04064d2 <arbitrary_virt_to_machine+22>:    mov    %eax,-0x10(%ebp)
> 0xc04064d5 <arbitrary_virt_to_machine+25>:    xor    %eax,%eax
> 0xc04064d7 <arbitrary_virt_to_machine+27>:    mov    %ebx,%eax
> 0xc04064d9 <arbitrary_virt_to_machine+29>:
>     call   0xc042f95c <__virt_addr_valid>
> 0xc04064de <arbitrary_virt_to_machine+34>:    test   %al,%al
> 0xc04064e0 <arbitrary_virt_to_machine+36>:
>     je     0xc040650e <arbitrary_virt_to_machine+82>
>
>     Michael Young
>

Thanks,
    J

Re: pvops dom0 work roadmap

[Daniel Schroeder]

Hi Jeremy,

thx for your work! I have tested current rebase/master on 64bit (Dell
PE2900, dual quad Xeon) with xen 3.4.2-rc1 and i have two issues:
> 
>     * better acpi power management (ported from 2.6.18)

how do i use the pm feature of pvops?
[1][2]

the other issue is dom0 memory...this is a bit odd...
system booted with dom0_mem=4096m but top displays only Mem:   2088992k
total.
xm top is correct and displays 4GB for Domain-0.


-
daniel

[1]
xenpm get-cpufreq-para
[CPU0] failed to get cpufreq parameter
[CPU1] failed to get cpufreq parameter
[CPU2] failed to get cpufreq parameter
[CPU3] failed to get cpufreq parameter
[CPU4] failed to get cpufreq parameter
[CPU5] failed to get cpufreq parameter
[CPU6] failed to get cpufreq parameter
[CPU7] failed to get cpufreq parameter

[2]
cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  no or unknown cpufreq driver is active on this CPU
analyzing CPU 1:
  no or unknown cpufreq driver is active on this CPU
analyzing CPU 2:
  no or unknown cpufreq driver is active on this CPU
analyzing CPU 3:
  no or unknown cpufreq driver is active on this CPU
analyzing CPU 4:
  no or unknown cpufreq driver is active on this CPU
analyzing CPU 5:
  no or unknown cpufreq driver is active on this CPU
analyzing CPU 6:
  no or unknown cpufreq driver is active on this CPU
analyzing CPU 7:
  no or unknown cpufreq driver is active on this CPU

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/19/09 17:25, Daniel Schroeder wrote:
> Hi Jeremy,
>
> thx for your work! I have tested current rebase/master on 64bit (Dell
> PE2900, dual quad Xeon) with xen 3.4.2-rc1 and i have two issues:
>   
>>     * better acpi power management (ported from 2.6.18)
>>     
> how do i use the pm feature of pvops?
> [1][2]
>   

Um, not sure.  I applied the patches, but I haven't tested them ;) 
Perhaps Yu Ke can add some light here.

> the other issue is dom0 memory...this is a bit odd...
> system booted with dom0_mem=4096m but top displays only Mem:   2088992k
> total.
> xm top is correct and displays 4GB for Domain-0.
>   

Hm, yes that's expected.  Currently some of dom0's memory is hidden
behind the PCI aperature and is wasted.  The quick fix is to simply
return the memory to Xen so that it can at least be properly used; the
complex fix is to move that memory higher up the address space so that
it's immediately available to dom0.  I tried the latter but it turned
out pretty complex.  The former is relatively simple, and I'll probably
apply a patch to do it soonish.  Once boot-time ballooning works (ie,
starting a domain so that it can be expanded), the memory can be
re-added via the balloon driver.

    J

Re: pvops dom0 work roadmap

[Jeremy Fitzhardinge]

On 08/19/09 17:25, Daniel Schroeder wrote:
> Hi Jeremy,
>
> thx for your work! I have tested current rebase/master on 64bit (Dell
> PE2900, dual quad Xeon) with xen 3.4.2-rc1 and i have two issues:
>   
>>     * better acpi power management (ported from 2.6.18)
>>     
> how do i use the pm feature of pvops?
> [1][2]
>   

Might help if I'd actually merged the branch...

    J

RE: pvops dom0 work roadmap

[Yu, Ke]

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]

Yes, I have tried to merge rebase/master with rebase/dom0/acpi-parser in my side, and the PM feature (Cx/Px) works.

Best Regards
Ke

-----Original Message-----
From: Jeremy Fitzhardinge [mailto:jeremy@goop.org] 
Sent: Thursday, August 20, 2009 8:46 AM
To: Daniel Schroeder
Cc: Xen-devel; Yu, Ke
Subject: Re: [Xen-devel] pvops dom0 work roadmap

On 08/19/09 17:25, Daniel Schroeder wrote:
> Hi Jeremy,
>
> thx for your work! I have tested current rebase/master on 64bit (Dell
> PE2900, dual quad Xeon) with xen 3.4.2-rc1 and i have two issues:
>   
>>     * better acpi power management (ported from 2.6.18)
>>     
> how do i use the pm feature of pvops?
> [1][2]
>   

Might help if I'd actually merged the branch...

    J

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 13935 bytes --]

Failure to build via the most recent rebase/master:-

In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:4,
                 from drivers/gpu/drm/ttm/ttm_agp_backend.c:39:
include/linux/swiotlb.h:48: warning: ‘enum dma_data_direction’ declared inside parameter list
include/linux/swiotlb.h:48: warning: its scope is only this definition or declaration, which is probably not what you want
include/linux/swiotlb.h:51: warning: ‘enum dma_data_direction’ declared inside parameter list
include/linux/swiotlb.h:63: warning: ‘enum dma_data_direction’ declared inside parameter list
include/linux/swiotlb.h:68: warning: ‘enum dma_data_direction’ declared inside parameter list
include/linux/swiotlb.h:72: warning: ‘enum dma_data_direction’ declared inside parameter list
include/linux/swiotlb.h:76: warning: ‘enum dma_data_direction’ declared inside parameter list
include/linux/swiotlb.h:80: warning: ‘enum dma_data_direction’ declared inside parameter list
include/linux/swiotlb.h:84: warning: ‘enum dma_data_direction’ declared inside parameter list
include/linux/swiotlb.h:89: warning: ‘enum dma_data_direction’ declared inside parameter list
include/linux/swiotlb.h:94: warning: ‘enum dma_data_direction’ declared inside parameter list
In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:8,
                 from drivers/gpu/drm/ttm/ttm_agp_backend.c:39:
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function ‘get_dma_ops’:
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:29: error: dereferencing pointer to incomplete type
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:32: error: dereferencing pointer to incomplete type
In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:36,
                 from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:8,
                 from drivers/gpu/drm/ttm/ttm_agp_backend.c:39:
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:12: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:11: error: parameter 4 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_map_single_attrs’:
include/asm-generic/dma-mapping-common.h:18: error: implicit declaration of function ‘valid_dma_direction’
include/asm-generic/dma-mapping-common.h:19: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:31: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:30: error: parameter 4 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_unmap_single_attrs’:
include/asm-generic/dma-mapping-common.h:36: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:37: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:43: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:42: error: parameter 4 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_map_sg_attrs’:
include/asm-generic/dma-mapping-common.h:52: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:60: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:59: error: parameter 4 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_unmap_sg_attrs’:
include/asm-generic/dma-mapping-common.h:66: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:67: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:72: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:72: error: parameter 5 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_map_page’:
include/asm-generic/dma-mapping-common.h:79: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:86: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:86: error: parameter 4 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_unmap_page’:
include/asm-generic/dma-mapping-common.h:91: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:92: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:98: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:98: error: parameter 4 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_sync_single_for_cpu’:
include/asm-generic/dma-mapping-common.h:103: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:104: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:111: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:111: error: parameter 4 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_sync_single_for_device’:
include/asm-generic/dma-mapping-common.h:116: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:117: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:126: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:126: error: parameter 5 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_sync_single_range_for_cpu’:
include/asm-generic/dma-mapping-common.h:131: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:132: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:137: error: type of formal parameter 4 is incomplete
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:144: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:144: error: parameter 5 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_sync_single_range_for_device’:
include/asm-generic/dma-mapping-common.h:149: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:150: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:155: error: type of formal parameter 4 is incomplete
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:160: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:160: error: parameter 4 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_sync_sg_for_cpu’:
include/asm-generic/dma-mapping-common.h:165: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:166: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h: At top level:
include/asm-generic/dma-mapping-common.h:173: warning: ‘enum dma_data_direction’ declared inside parameter list
include/asm-generic/dma-mapping-common.h:173: error: parameter 4 (‘dir’) has incomplete type
include/asm-generic/dma-mapping-common.h: In function ‘dma_sync_sg_for_device’:
include/asm-generic/dma-mapping-common.h:178: error: dereferencing pointer to incomplete type
include/asm-generic/dma-mapping-common.h:179: error: dereferencing pointer to incomplete type
In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:8,
                 from drivers/gpu/drm/ttm/ttm_agp_backend.c:39:
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function ‘dma_mapping_error’:
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:42: error: dereferencing pointer to incomplete type
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:43: error: dereferencing pointer to incomplete type
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: At top level:
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: warning: ‘enum dma_data_direction’ declared inside parameter list
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: error: parameter 4 (‘dir’) has incomplete type
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function ‘dma_alloc_coherent_mask’:
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:77: error: dereferencing pointer to incomplete type
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:79: error: implicit declaration of function ‘DMA_BIT_MASK’
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function ‘dma_alloc_coherent’:
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:114: error: implicit declaration of function ‘is_device_dma_capable’
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:117: error: dereferencing pointer to incomplete type
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:120: error: dereferencing pointer to incomplete type
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function ‘dma_free_coherent’:
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:138: error: dereferencing pointer to incomplete type
/usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:139: error: dereferencing pointer to incomplete type
  CC [M]  drivers/hwmon/adt7475.o
make[4]: *** [drivers/gpu/drm/ttm/ttm_agp_backend.o] Error 1
make[3]: *** [drivers/gpu/drm/ttm] Error 2
make[2]: *** [drivers/gpu/drm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
  CC [M]  drivers/hwmon/applesmc.o
  CC [M]  net/lapb/lapb_iface.o
  CC [M]  fs/ocfs2/dlm/dlmast.o
  CC [M]  fs/ocfs2/dlm/dlmconvert.o
  LD [M]  net/lapb/lapb.o
  CC      net/llc/llc_core.o
  CC      net/llc/llc_input.o
  CC [M]  drivers/hwmon/asus_atk0110.o
  LD      net/mac80211/built-in.o
  CC [M]  net/mac80211/main.o
  CC [M]  fs/ocfs2/dlm/dlmlock.o
  CC [M]  drivers/hwmon/atxp1.o
  CC      net/llc/llc_output.o
  CC [M]  drivers/hwmon/coretemp.o
  CC [M]  net/llc/llc_if.o
  CC [M]  net/mac80211/wext.o
  CC [M]  fs/ocfs2/dlm/dlmunlock.o
  CC [M]  drivers/hwmon/dme1737.o
  CC [M]  net/mac80211/sta_info.o
  CC [M]  net/llc/llc_c_ev.o
^Cmake[2]: *** [net/llc/llc_c_ev.o] Interrupt
make[1]: *** [net/llc] Interrupt
make[2]: *** [drivers/hwmon/dme1737.o] Interrupt
make[2]: *** [net/mac80211/sta_info.o] Interrupt
make[3]: *** Deleting file `fs/ocfs2/dlm/dlmunlock.o'
make[1]: *** [net/mac80211] Interrupt
make[1]: *** [drivers/hwmon] Interrupt
make: *** [drivers] Interrupt
make: *** [net] Interrupt
make[3]: *** [fs/ocfs2/dlm/dlmunlock.o] Interrupt
make[2]: *** [fs/ocfs2/dlm] Interrupt
make[1]: *** [fs/ocfs2] Interrupt
make: *** [fs] Interrupt

Boris.

--- On Tue, 8/18/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:

From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [Xen-devel] pvops dom0 work roadmap
To: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Tuesday, August 18, 2009, 2:43 PM

Hi all,

I know I've been a bit quiet lately;  I've been working through a number
of relatively small but time-consuming bugs while trying to stabilize
rebase/master.

The plan is:

    * make sure rebase/master is fairly functional and somewhat stable
    * rename rebase/* to xen/*
    * use it as the baseline dom0 and domU kernel in xen-unstable

rebase/mster is currently up to 2.6.31-rc6, and I intend to track
mainline fairly closely (probably no more closely than the -rc level). 
It also has some new features:

    * better acpi power management (ported from 2.6.18)
    * MCE (also from 2.6.18)
    * microcode updater (I forget whether that's in xen-tip/master)

rebase/master is mostly working for me now, but I would be interested in
getting some more testing (both success and bug reports welcomed).  Once
it seems to work, I'll do the rename and we'll work from there.

What does this mean for you?

    * If you're itching to test something, test rebase/master
    * If you're doing some new development, base it on rebase/master (or
      if you don't have any strong dependencies on other Xen pieces,
      base it on mainline)
          o also, tell me if you're working on something, even if it
            isn't ready yet, so I know who's doing what

It would also useful to do regression testing on plain, unpatched,
mainline, to make sure that any real bugfixes get merged promptly.

Thanks,
    J

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 15538 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap

[Konrad Rzeszutek Wilk]

On Tue, Sep 01, 2009 at 11:47:43PM -0700, Boris Derzhavets wrote:
> Failure to build via the most recent rebase/master:-
> 
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:4,
>                  from drivers/gpu/drm/ttm/ttm_agp_backend.c:39:
> include/linux/swiotlb.h:48: warning: ‘enum dma_data_direction’ declared inside parameter list

I am not seeing this on my build. Can you provide the .config?

Did you try to build a vanilla 2.6.31-rc6 with the same .config?

Re: pvops dom0 work roadmap

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 1164 bytes --]

I've just ran "git commit -a" which updated both of mentioned files.
Afterwards i was able to build kernel.

B. 

--- On Wed, 9/2/09, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:

From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] pvops dom0 work roadmap
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, September 2, 2009, 9:43 AM

On Tue, Sep 01, 2009 at 11:47:43PM -0700, Boris Derzhavets wrote:
> Failure to build via the most recent rebase/master:-
> 
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:4,
>                  from drivers/gpu/drm/ttm/ttm_agp_backend.c:39:
> include/linux/swiotlb.h:48: warning: ‘enum dma_data_direction’ declared inside parameter list

I am not seeing this on my build. Can you provide the .config?

Did you try to build a vanilla 2.6.31-rc6 with the same .config?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 1773 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 1053 bytes --]

Yes.

--- On Wed, 9/2/09, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:

From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] pvops dom0 work roadmap
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, September 2, 2009, 9:43 AM

On Tue, Sep 01, 2009 at 11:47:43PM -0700, Boris Derzhavets wrote:
> Failure to build via the most recent rebase/master:-
> 
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:4,
>                  from drivers/gpu/drm/ttm/ttm_agp_backend.c:39:
> include/linux/swiotlb.h:48: warning: ‘enum dma_data_direction’ declared inside parameter list

I am not seeing this on my build. Can you provide the .config?

Did you try to build a vanilla 2.6.31-rc6 with the same .config?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 1657 bytes --]

[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 26610 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: pvops dom0 work roadmap

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 1732 bytes --]

Previous .config was wrong. Working version attached ( for the most recent
git clone, git checkout rebase/master)

B.
--- On Wed, 9/2/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] pvops dom0 work roadmap
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, September 2, 2009, 9:50 AM

Yes.

--- On Wed, 9/2/09, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:

From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] pvops dom0 work roadmap
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "Xen-devel" <xen-devel@lists.xensource.com>
Date: Wednesday, September 2, 2009, 9:43 AM

On Tue, Sep 01, 2009 at 11:47:43PM -0700, Boris Derzhavets wrote:
> Failure to build via the most recent rebase/master:-
> 
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:4,
>
                  from drivers/gpu/drm/ttm/ttm_agp_backend.c:39:
> include/linux/swiotlb.h:48: warning: ‘enum dma_data_direction’ declared inside parameter list

I am not seeing this on my build. Can you provide the .config?

Did you try to build a vanilla 2.6.31-rc6 with the same .config?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      
-----Inline Attachment Follows-----

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel



      

[-- Attachment #1.2: Type: text/html, Size: 2985 bytes --]

[-- Attachment #2: config-working.gz --]
[-- Type: application/x-gzip, Size: 24110 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel