| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
I haven't encountered this error, so I am not sure. One thing that comes to
mind is to check the version of guilt on your system and possibly upgrade to a
newer version if there is one.
Kamala
> -----Original Message-----
> From: scorbin [mailto:steve.corbin@xxxxxxxxxxxxxxxxxxx]
> Sent: Thursday, July 02, 2009 5:03 PM
> To: Kamala Narasimhan
> Cc: xen-devel
> Subject: RE: [Xen-devel] Host S3
>
> Hi Kamala,
>
> I am trying to build the XCI tree and am having some issues. The first
> problem is that the make configuration for xenclient-ioemu is setup to
> use alsa but libasound2 is not included in the XCI target packages. I
> avoided this issue by modifying xen-setup and configure in the
> xenclient-ioemu directory to not use alsa. The second issue is one I
> can't get passed. The build fails just after setting up
> xenclient-linux. Here is the output:
>
> ...
> Initialized empty Git repository
> in /home/scorbin/build/repo/xenclient-linux-2.6.27-pq/.git/
> master
> ln: target `' is not a directory: No such file or directory
> Applying patch..hgignore.patch
> Patch applied.
> Applying patch..build-system-integration.patch
> Patch applied.
> Applying patch..linux-2.6.27.19-5.1.patch
> Patch applied.
> Applying patch..sync-drivers-xen.patch
> Patch applied.
> Applying patch..forward-port-drivers-xen.patch
> Patch applied.
> Applying patch..linux-2.6.18-xen.hg-832.c0f2f398aa3c # x86: Fix
> interaction of NTP and dom0->xen time updates
> Patch linux-2.6.18-xen.hg-832.c0f2f398aa3c # x86: Fix interaction of
> NTP
> and dom0->xen time updates does not exist. Aborting.
> make[1]: *** [/home/scorbin/build/repo/xenclient-kernel-2.6.27] Error 1
> make[1]: Leaving directory `/home/scorbin/build'
> make: ***
> [/home/scorbin/build/build_i686/xenclient-kernel-2.6.27/.installed]
> Error 2
>
> The build system is a fresh install of 32-bit Debian 5.01.
>
> Any help you can provide on building XCI would be appreciated.
>
> - steve
>
>
> On Thu, 2009-07-02 at 11:22 -0400, Kamala Narasimhan wrote:
> > You might want to look for enter-s3.sh script. Since host S3/resume
> is impacted by different components running on the system and since XCI
> build already ensures that the components built by it plays along with
> host S3, you might be better off with XCI build so as not to chase yet
> another issue you might possibly run into that XCI build might have
> already taken care of...
> >
> > Kamala
> >
> > > -----Original Message-----
> > > From: scorbin [mailto:steve.corbin@xxxxxxxxxxxxxxxxxxx]
> > > Sent: Wednesday, July 01, 2009 7:04 PM
> > > To: Kamala Narasimhan
> > > Cc: xen-devel
> > > Subject: RE: [Xen-devel] Host S3
> > >
> > > Hi Kamala,
> > >
> > > Thanks for your response. Can you provide some pointers into the
> XCI
> > > trees where I can see the related source code changes?
> > >
> > > - steve
> > >
> > > On Wed, 2009-07-01 at 16:41 -0400, Kamala Narasimhan wrote:
> > > > You might want to consider using the XCI build which already
> takes
> > > care of this issue. We have added the necessary user mode quirks
> plus
> > > included relevant components you would need along with appropriate
> > > emulation library that would work with 64-bit hypervisor etc.
> > > >
> > > > Kamala
> > > >
> > > > > -----Original Message-----
> > > > > From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> > > > > bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of scorbin
> > > > > Sent: Wednesday, July 01, 2009 2:26 PM
> > > > > To: xen-devel
> > > > > Subject: Re: [Xen-devel] Host S3
> > > > >
> > > > > It looks like suspend.sf.net will not work. The s2ram utility
> > > > > requires /proc/sys/kernel/acpi_sleep_flags which does not exist
> in
> > > the
> > > > > Xen patched Linux kernel. It is removed via
> CONFIG_ACPI_PV_SLEEP.
> > > > >
> > > > > So how are people using dom0 suspend/resume? Any sample
> > > scripts/code?
> > > > > Simply doing 'echo mem > /sys/power/state' does not restore the
> > > > > graphics
> > > > > card. I also tried a script I found on the web that
> effectively
> > > does:
> > > > >
> > > > > # dump current data from the video card to the temporary file
> > > > > cat /proc/bus/pci/$ID > $TMP_FILE
> > > > >
> > > > > # suspend
> > > > > echo -n mem > /sys/power/state
> > > > >
> > > > > # restore video card data from the temporary file on resume
> > > > > cat $TMP_FILE > /proc/bus/pci/$ID
> > > > >
> > > > > with the same result that bare Linux works but booting with Xen
> > > does
> > > > > not
> > > > > restore the video card.
> > > > >
> > > > > - steve
> > > > >
> > > > > On Wed, 2009-07-01 at 13:40 -0400, scorbin wrote:
> > > > > > I tried it on a Dell, Lenovo and 2 HPs. Upon further
> > > investigation
> > > > > it
> > > > > > turns out the systems are resuming but the video card is not
> > > > > > re-initialized. It's strange because I can use the same
> > > procedure
> > > > > for
> > > > > > Linux without Xen and the video resumes properly.
> > > > > >
> > > > > > Searching the web I found suspend.sf.net. Is this what
> people
> > > are
> > > > > using
> > > > > > to do the video restore?
> > > > > >
> > > > > >
> > > > > > On Wed, 2009-07-01 at 20:08 +0300, Tom Rotenberg wrote:
> > > > > > > What is the hardware it didn't work for you?
> > > > > > >
> > > > > > > 2009/7/1 scorbin <steve.corbin@xxxxxxxxxxxxxxxxxxx>
> > > > > > > What is the state of host suspend to ram? I
> noticed
> > > that
> > > > > this
> > > > > > > functionality was put into 3.2 with fixes in 3.3.
> I
> > > also
> > > > > saw
> > > > > > > something
> > > > > > > recently that indicates there might be a separate
> tree
> > > > > where
> > > > > > > suspend/S3
> > > > > > > is being developed/enhanced?
> > > > > > >
> > > > > > > I did try Xen3.3/Ubuntu8.04 and did not get host S3
> to
> > > > > resume
> > > > > > > properly.
> > > > > > > Straight Ubuntu 8.04 suspends/resumes fine.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Xen-devel mailing list
> > > > > > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > > > > > http://lists.xensource.com/xen-devel
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Xen-devel mailing list
> > > > > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > > > > http://lists.xensource.com/xen-devel
> > > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Xen-devel mailing list
> > > > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > > > http://lists.xensource.com/xen-devel
> > > >
> >
> >
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home