thr3ads.net - Xen users - [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0 [Jul 2009]

If this information is useful, please help other people find it:
Share via:

Joshua West

2009-Jul-31 00:00 UTC

[Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Hey all,

I''ve been attempting to get ''xm restore'' (and thus
''xm migrate'') to work
for a 32-bit HVM domU on a 64-bit dom0 running Xen 3.4.1-rc10.  Has
anyone else been able to do so?  I can boot the VM and work within it
just fine.  The ''xm save'' command also functions properly;
issue is just
with ''restore'' and therefore ''migrate''.

When I watch the system via "xm top" during the restoration process, I
do notice the memory allocation for the VM increase all the way to about
1024MB.  Suddenly, the amount of memory allocated to the VM decreases by
a bit, and then finally the VM disappears.

It may be of interest that I don''t have issues
saving/restoring/migrating 32-bit PV domU''s on this same set of 64-bit
dom0''s.  This seems to be an issue only with HVM domU''s.

The following is taken from /var/log/xen/xend.log and demonstrates the
failure:

[2009-07-30 19:48:18 4839] INFO (image:745) Need to create platform
device.[domid:37]
[2009-07-30 19:48:18 4839] DEBUG (XendCheckpoint:261)
restore:shadow=0x9, _static_max=0x40000000, _static_min=0x0,
[2009-07-30 19:48:18 4839] DEBUG (balloon:166) Balloon: 31589116 KiB
free; need 1061888; done.
[2009-07-30 19:48:18 4839] DEBUG (XendCheckpoint:278) [xc_restore]:
/usr/lib64/xen/bin/xc_restore 4 37 2 3 1 1 1
[2009-07-30 19:48:18 4839] INFO (XendCheckpoint:417) xc_domain_restore
start: p2m_size = 100000
[2009-07-30 19:48:18 4839] INFO (XendCheckpoint:417) Reloading memory
pages:   0%
[2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) Failed allocation
for dom 37: 1024 extents of order 0
[2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) ERROR Internal
error: Failed to allocate memory for batch.!
[2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417)
[2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) Restore exit with rc=1
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2724)
XendDomainInfo.destroy: domid=37
[2009-07-30 19:48:27 4839] ERROR (XendDomainInfo:2738)
XendDomainInfo.destroy: domain destruction failed.
Traceback (most recent call last):
  File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 2731, in destroy
    xc.domain_pause(self.domid)
Error: (3, \047No such process\047)
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2204) No device model
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2206) Releasing devices
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing vif/0
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing vbd/768
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing vfb/0
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing console/0
[2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2009-07-30 19:48:27 4839] ERROR (XendDomain:1149) Restore failed
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py",
line
1147, in domain_restore_fd
    return XendCheckpoint.restore(self, fd, paused=paused,
relocating=relocating)
  File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 282, in restore
    forkHelper(cmd, fd, handler.handler, True)
  File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 405, in forkHelper
    raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_restore 4 37 2 3 1 1 1 failed

And here is the xmconfig file:

#---------------------------------------------------------------#
import os, re
arch_libdir = ''lib''
arch = os.uname()[4]
if os.uname()[0] == ''Linux'' and
re.search(''64'', arch):
    arch_libdir = ''lib64''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 1024
name = "winxen"
vcpus=1
vif = [ ''type=ioemu, bridge=xenbr100, mac=aa:bb:cc:00:00:99'' ]
disk = [ ''phy:/dev/drbd/by-res/vm_winxen,hda,w'' ]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="c"
sdl=0
opengl=1
vnc=1
vncpasswd=''...''
stdvga=1
monitor=1
usbdevice=''tablet''
#---------------------------------------------------------------#

One thing of interest I did also notice in the logs was during the "xm
save" process:

[2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:110) [xc_save]:
/usr/lib64/xen/bin/xc_save 56 36 0 0 4
[2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:388) suspend
[2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:113) In
saveInputHandler suspend
[2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:115) Suspending 36 ...
[2009-07-30 19:47:26 4839] DEBUG (XendDomainInfo:511)
XendDomainInfo.shutdown(suspend)
[2009-07-30 19:47:26 4839] INFO (XendCheckpoint:417) xc_save: failed to
get the suspend evtchn port
[2009-07-30 19:47:26 4839] INFO (XendCheckpoint:417)
[2009-07-30 19:47:26 4839] DEBUG (XendDomainInfo:1709)
XendDomainInfo.handleShutdownWatch
[2009-07-30 19:47:27 4839] INFO (XendDomainInfo:1895) Domain has
shutdown: name=migrating-winxen id=36 reason=suspend.
[2009-07-30 19:47:27 4839] INFO (XendCheckpoint:121) Domain 36 suspended.
[2009-07-30 19:47:27 4839] INFO (image:479) signalDeviceModel:restore dm
state to running
[2009-07-30 19:47:27 4839] DEBUG (XendCheckpoint:130) Written done
 1: sent 266240, skipped 0, delta 8484ms, dom0 46%, target 0%, sent
1028Mb/s, dirtied 0Mb/s 0 pages
[2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) Total pages sent266240
(0.25x)
[2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) (of which 0 were
fixups)
[2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) All memory is saved
[2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) Save exit rc=0

Not sure if that xc_save error message has anything to do with this...

If there is any additional information you need, such as how I built Xen
or even the ''xm save'' copy of the VM itself, just let me know
and I''ll
make it available.

Thanks.

-- 
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu


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

Pasi Kärkkäinen

2009-Jul-31 07:19 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

On Thu, Jul 30, 2009 at 08:00:21PM -0400, Joshua West
wrote:> Hey all,
> 
> I''ve been attempting to get ''xm restore'' (and
thus ''xm migrate'') to work
> for a 32-bit HVM domU on a 64-bit dom0 running Xen 3.4.1-rc10.  Has
> anyone else been able to do so?  I can boot the VM and work within it
> just fine.  The ''xm save'' command also functions
properly; issue is just
> with ''restore'' and therefore ''migrate''.
> 
What dom0 kernel you are running?

If something else than linux-2.6.18-xen.hg please try with that instead.

-- Pasi
> When I watch the system via "xm top" during the restoration
process, I
> do notice the memory allocation for the VM increase all the way to about
> 1024MB.  Suddenly, the amount of memory allocated to the VM decreases by
> a bit, and then finally the VM disappears.
> 
> It may be of interest that I don''t have issues
> saving/restoring/migrating 32-bit PV domU''s on this same set of
64-bit
> dom0''s.  This seems to be an issue only with HVM domU''s.
> 
> The following is taken from /var/log/xen/xend.log and demonstrates the
> failure:
> 
> [2009-07-30 19:48:18 4839] INFO (image:745) Need to create platform
> device.[domid:37]
> [2009-07-30 19:48:18 4839] DEBUG (XendCheckpoint:261)
> restore:shadow=0x9, _static_max=0x40000000, _static_min=0x0,
> [2009-07-30 19:48:18 4839] DEBUG (balloon:166) Balloon: 31589116 KiB
> free; need 1061888; done.
> [2009-07-30 19:48:18 4839] DEBUG (XendCheckpoint:278) [xc_restore]:
> /usr/lib64/xen/bin/xc_restore 4 37 2 3 1 1 1
> [2009-07-30 19:48:18 4839] INFO (XendCheckpoint:417) xc_domain_restore
> start: p2m_size = 100000
> [2009-07-30 19:48:18 4839] INFO (XendCheckpoint:417) Reloading memory
> pages:   0%
> [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) Failed allocation
> for dom 37: 1024 extents of order 0
> [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) ERROR Internal
> error: Failed to allocate memory for batch.!
> [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417)
> [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) Restore exit with rc=1
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2724)
> XendDomainInfo.destroy: domid=37
> [2009-07-30 19:48:27 4839] ERROR (XendDomainInfo:2738)
> XendDomainInfo.destroy: domain destruction failed.
> Traceback (most recent call last):
>   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 2731, in destroy
>     xc.domain_pause(self.domid)
> Error: (3, \047No such process\047)
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2204) No device model
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2206) Releasing devices
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing vif/0
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing vbd/768
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing vfb/0
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing console/0
> [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
> [2009-07-30 19:48:27 4839] ERROR (XendDomain:1149) Restore failed
> Traceback (most recent call last):
>   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line
> 1147, in domain_restore_fd
>     return XendCheckpoint.restore(self, fd, paused=paused,
> relocating=relocating)
>   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
> line 282, in restore
>     forkHelper(cmd, fd, handler.handler, True)
>   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
> line 405, in forkHelper
>     raise XendError("%s failed" % string.join(cmd))
> XendError: /usr/lib64/xen/bin/xc_restore 4 37 2 3 1 1 1 failed
> 
> And here is the xmconfig file:
> 
> #---------------------------------------------------------------#
> import os, re
> arch_libdir = ''lib''
> arch = os.uname()[4]
> if os.uname()[0] == ''Linux'' and
re.search(''64'', arch):
>     arch_libdir = ''lib64''
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder=''hvm''
> memory = 1024
> name = "winxen"
> vcpus=1
> vif = [ ''type=ioemu, bridge=xenbr100,
mac=aa:bb:cc:00:00:99'' ]
> disk = [ ''phy:/dev/drbd/by-res/vm_winxen,hda,w'' ]
> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
> boot="c"
> sdl=0
> opengl=1
> vnc=1
> vncpasswd=''...''
> stdvga=1
> monitor=1
> usbdevice=''tablet''
> #---------------------------------------------------------------#
> 
> One thing of interest I did also notice in the logs was during the "xm
> save" process:
> 
> [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:110) [xc_save]:
> /usr/lib64/xen/bin/xc_save 56 36 0 0 4
> [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:388) suspend
> [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:113) In
> saveInputHandler suspend
> [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:115) Suspending 36 ...
> [2009-07-30 19:47:26 4839] DEBUG (XendDomainInfo:511)
> XendDomainInfo.shutdown(suspend)
> [2009-07-30 19:47:26 4839] INFO (XendCheckpoint:417) xc_save: failed to
> get the suspend evtchn port
> [2009-07-30 19:47:26 4839] INFO (XendCheckpoint:417)
> [2009-07-30 19:47:26 4839] DEBUG (XendDomainInfo:1709)
> XendDomainInfo.handleShutdownWatch
> [2009-07-30 19:47:27 4839] INFO (XendDomainInfo:1895) Domain has
> shutdown: name=migrating-winxen id=36 reason=suspend.
> [2009-07-30 19:47:27 4839] INFO (XendCheckpoint:121) Domain 36 suspended.
> [2009-07-30 19:47:27 4839] INFO (image:479) signalDeviceModel:restore dm
> state to running
> [2009-07-30 19:47:27 4839] DEBUG (XendCheckpoint:130) Written done
>  1: sent 266240, skipped 0, delta 8484ms, dom0 46%, target 0%, sent
> 1028Mb/s, dirtied 0Mb/s 0 pages
> [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) Total pages sent>
266240 (0.25x)
> [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) (of which 0 were
> fixups)
> [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) All memory is saved
> [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) Save exit rc=0
> 
> Not sure if that xc_save error message has anything to do with this...
> 
> If there is any additional information you need, such as how I built Xen
> or even the ''xm save'' copy of the VM itself, just let me
know and I''ll
> make it available.
> 
> Thanks.
> 
> -- 
> Joshua West
> Senior Systems Engineer
> Brandeis University
> http://www.brandeis.edu
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Pasi Kärkkäinen

2009-Jul-31 08:25 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

On Fri, Jul 31, 2009 at 10:19:04AM +0300, Pasi Kärkkäinen
wrote:> On Thu, Jul 30, 2009 at 08:00:21PM -0400, Joshua West wrote:
> > Hey all,
> > 
> > I''ve been attempting to get ''xm restore''
(and thus ''xm migrate'') to work
> > for a 32-bit HVM domU on a 64-bit dom0 running Xen 3.4.1-rc10.  Has
> > anyone else been able to do so?  I can boot the VM and work within it
> > just fine.  The ''xm save'' command also functions
properly; issue is just
> > with ''restore'' and therefore
''migrate''.
> > 
> 
> What dom0 kernel you are running?
> 
> If something else than linux-2.6.18-xen.hg please try with that instead.
> 
Also if you can reproduce this problem running linux-2.6.18-xen on dom0,
then please send an email to xen-devel about this. Keir wants to release Xen
3.4.1 final early next week, and this sounds like something that might be
good to check before the release.

If this problem happens running for example Debian lenny 2.6.26-xen kernel in
dom0,
or some other 2.6.27, 2.6.29, 2.6.30 dom0 kernel then it _could_ be a bug in
them, and not in Xen.

-- Pasi
> 
> > When I watch the system via "xm top" during the restoration
process, I
> > do notice the memory allocation for the VM increase all the way to
about
> > 1024MB.  Suddenly, the amount of memory allocated to the VM decreases
by
> > a bit, and then finally the VM disappears.
> > 
> > It may be of interest that I don''t have issues
> > saving/restoring/migrating 32-bit PV domU''s on this same set
of 64-bit
> > dom0''s.  This seems to be an issue only with HVM
domU''s.
> > 
> > The following is taken from /var/log/xen/xend.log and demonstrates the
> > failure:
> > 
> > [2009-07-30 19:48:18 4839] INFO (image:745) Need to create platform
> > device.[domid:37]
> > [2009-07-30 19:48:18 4839] DEBUG (XendCheckpoint:261)
> > restore:shadow=0x9, _static_max=0x40000000, _static_min=0x0,
> > [2009-07-30 19:48:18 4839] DEBUG (balloon:166) Balloon: 31589116 KiB
> > free; need 1061888; done.
> > [2009-07-30 19:48:18 4839] DEBUG (XendCheckpoint:278) [xc_restore]:
> > /usr/lib64/xen/bin/xc_restore 4 37 2 3 1 1 1
> > [2009-07-30 19:48:18 4839] INFO (XendCheckpoint:417) xc_domain_restore
> > start: p2m_size = 100000
> > [2009-07-30 19:48:18 4839] INFO (XendCheckpoint:417) Reloading memory
> > pages:   0%
> > [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) Failed allocation
> > for dom 37: 1024 extents of order 0
> > [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) ERROR Internal
> > error: Failed to allocate memory for batch.!
> > [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417)
> > [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) Restore exit with
rc=1
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2724)
> > XendDomainInfo.destroy: domid=37
> > [2009-07-30 19:48:27 4839] ERROR (XendDomainInfo:2738)
> > XendDomainInfo.destroy: domain destruction failed.
> > Traceback (most recent call last):
> >   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> > line 2731, in destroy
> >     xc.domain_pause(self.domid)
> > Error: (3, \047No such process\047)
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2204) No device model
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2206) Releasing
devices
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing vif/0
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> > XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing
vbd/768
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> > XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing vfb/0
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> > XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing
console/0
> > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> > XendDomainInfo.destroyDevice: deviceClass = console, device =
console/0
> > [2009-07-30 19:48:27 4839] ERROR (XendDomain:1149) Restore failed
> > Traceback (most recent call last):
> >   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line
> > 1147, in domain_restore_fd
> >     return XendCheckpoint.restore(self, fd, paused=paused,
> > relocating=relocating)
> >   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
> > line 282, in restore
> >     forkHelper(cmd, fd, handler.handler, True)
> >   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
> > line 405, in forkHelper
> >     raise XendError("%s failed" % string.join(cmd))
> > XendError: /usr/lib64/xen/bin/xc_restore 4 37 2 3 1 1 1 failed
> > 
> > And here is the xmconfig file:
> > 
> > #---------------------------------------------------------------#
> > import os, re
> > arch_libdir = ''lib''
> > arch = os.uname()[4]
> > if os.uname()[0] == ''Linux'' and
re.search(''64'', arch):
> >     arch_libdir = ''lib64''
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > builder=''hvm''
> > memory = 1024
> > name = "winxen"
> > vcpus=1
> > vif = [ ''type=ioemu, bridge=xenbr100,
mac=aa:bb:cc:00:00:99'' ]
> > disk = [ ''phy:/dev/drbd/by-res/vm_winxen,hda,w'' ]
> > device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
> > boot="c"
> > sdl=0
> > opengl=1
> > vnc=1
> > vncpasswd=''...''
> > stdvga=1
> > monitor=1
> > usbdevice=''tablet''
> > #---------------------------------------------------------------#
> > 
> > One thing of interest I did also notice in the logs was during the
"xm
> > save" process:
> > 
> > [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:110) [xc_save]:
> > /usr/lib64/xen/bin/xc_save 56 36 0 0 4
> > [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:388) suspend
> > [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:113) In
> > saveInputHandler suspend
> > [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:115) Suspending 36
...
> > [2009-07-30 19:47:26 4839] DEBUG (XendDomainInfo:511)
> > XendDomainInfo.shutdown(suspend)
> > [2009-07-30 19:47:26 4839] INFO (XendCheckpoint:417) xc_save: failed
to
> > get the suspend evtchn port
> > [2009-07-30 19:47:26 4839] INFO (XendCheckpoint:417)
> > [2009-07-30 19:47:26 4839] DEBUG (XendDomainInfo:1709)
> > XendDomainInfo.handleShutdownWatch
> > [2009-07-30 19:47:27 4839] INFO (XendDomainInfo:1895) Domain has
> > shutdown: name=migrating-winxen id=36 reason=suspend.
> > [2009-07-30 19:47:27 4839] INFO (XendCheckpoint:121) Domain 36
suspended.
> > [2009-07-30 19:47:27 4839] INFO (image:479) signalDeviceModel:restore
dm
> > state to running
> > [2009-07-30 19:47:27 4839] DEBUG (XendCheckpoint:130) Written done
> >  1: sent 266240, skipped 0, delta 8484ms, dom0 46%, target 0%, sent
> > 1028Mb/s, dirtied 0Mb/s 0 pages
> > [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) Total pages
sent> > 266240 (0.25x)
> > [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) (of which 0 were
> > fixups)
> > [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) All memory is
saved
> > [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) Save exit rc=0
> > 
> > Not sure if that xc_save error message has anything to do with this...
> > 
> > If there is any additional information you need, such as how I built
Xen
> > or even the ''xm save'' copy of the VM itself, just
let me know and I''ll
> > make it available.
> > 
> > Thanks.
> > 
> > -- 
> > Joshua West
> > Senior Systems Engineer
> > Brandeis University
> > http://www.brandeis.edu
> > 
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Sreeharsha Totakura

2009-Jul-31 09:21 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

xen-users-bounces@lists.xensource.com wrote on 07/31/2009 01:55:09 PM:
> Pasi Kärkkäinen <pasik@iki.fi>
>
> Subject
>
> Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM
> domU (W2K3 Server) on 64-bit dom0
>
> On Fri, Jul 31, 2009 at 10:19:04AM +0300, Pasi Kärkkäinen wrote:
> > On Thu, Jul 30, 2009 at 08:00:21PM -0400, Joshua West wrote:
> > > Hey all,
> > >
> > > I''ve been attempting to get ''xm
restore'' (and thus ''xm migrate'') to
work> > > for a 32-bit HVM domU on a 64-bit dom0 running Xen 3.4.1-rc10. 
Has
> > > anyone else been able to do so?  I can boot the VM and work
within it
> > > just fine.  The ''xm save'' command also
functions properly; issue is
just> > > with ''restore'' and therefore
''migrate''.
I too am attempting to live migrate a 32bit Guest from a 64 bit Dom-0 to a
32bit Dom-0 and haven''t succeeded yet. Is this possible?
>From the logs I found that there is a problem in restoring the virtualmachine on the 32 bit Dom-0.
> > What dom0 kernel you are running?
> >
> > If something else than linux-2.6.18-xen.hg please try with that
instead.> >
I am running the kernel ( 2.6.18-128.el5xen) which came with RHEL5.3
> Also if you can reproduce this problem running linux-2.6.18-xen on dom0,
> then please send an email to xen-devel about this. Keir wants to release
Xen> 3.4.1 final early next week, and this sounds like something that might be
> good to check before the release.
>
> If this problem happens running for example Debian lenny 2.6.26-xen
> kernel in dom0,
> or some other 2.6.27, 2.6.29, 2.6.30 dom0 kernel then it _could_ be a bug
in> them, and not in Xen.
>
> -- Pasi
>
> >
> > > When I watch the system via "xm top" during the
restoration process,
I> > > do notice the memory allocation for the VM increase all the way
to
about> > > 1024MB.  Suddenly, the amount of memory allocated to the VM
decreases
by> > > a bit, and then finally the VM disappears.
> > >
> > > It may be of interest that I don''t have issues
> > > saving/restoring/migrating 32-bit PV domU''s on this same
set of
64-bit> > > dom0''s.  This seems to be an issue only with HVM
domU''s.
May be true, I too have observed this on my 64bit Dom-0 where I am running
32bit Dom-U''s. I guess they are running under HVM. Little clarification
is
needed here.. Can we run 32 Dom-U''s under PV on 64 bit Dom-0 ?

Thanks,
Harsha

=====-----=====-----====Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you




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

Pasi Kärkkäinen

2009-Jul-31 10:18 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

On Fri, Jul 31, 2009 at 02:51:09PM +0530, Sreeharsha Totakura
wrote:> 
> 
> xen-users-bounces@lists.xensource.com wrote on 07/31/2009 01:55:09 PM:
> 
> > Pasi Kärkkäinen <pasik@iki.fi>
> >
> > Subject
> >
> > Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM
> > domU (W2K3 Server) on 64-bit dom0
> >
> > On Fri, Jul 31, 2009 at 10:19:04AM +0300, Pasi Kärkkäinen wrote:
> > > On Thu, Jul 30, 2009 at 08:00:21PM -0400, Joshua West wrote:
> > > > Hey all,
> > > >
> > > > I''ve been attempting to get ''xm
restore'' (and thus ''xm migrate'') to
> work
> > > > for a 32-bit HVM domU on a 64-bit dom0 running Xen
3.4.1-rc10.  Has
> > > > anyone else been able to do so?  I can boot the VM and work
within it
> > > > just fine.  The ''xm save'' command also
functions properly; issue is
> just
> > > > with ''restore'' and therefore
''migrate''.
> 
> I too am attempting to live migrate a 32bit Guest from a 64 bit Dom-0 to a
> 32bit Dom-0 and haven''t succeeded yet. Is this possible?
> 
I''m not sure if that''s possible.
> From the logs I found that there is a problem in restoring the virtual
> machine on the 32 bit Dom-0.
> 
> > > What dom0 kernel you are running?
> > >
> > > If something else than linux-2.6.18-xen.hg please try with that
> instead.
> > >
> 
> I am running the kernel ( 2.6.18-128.el5xen) which came with RHEL5.3
> 
Xen 3.4.x uses linux-2.6.18-xen.hg as a default dom0 kernel, ie. Xen is tested
and developed using that kernel. 

So you should try running that to see if the problem is in your RHEL5.3 kernel.

Btw RHEL 5.4 beta xen and kernel-xen has a lot of fixes for 32-on-64, live
migrations etc.
> > Also if you can reproduce this problem running linux-2.6.18-xen on
dom0,
> > then please send an email to xen-devel about this. Keir wants to
release
> Xen
> > 3.4.1 final early next week, and this sounds like something that might
be
> > good to check before the release.
> >
> > If this problem happens running for example Debian lenny 2.6.26-xen
> > kernel in dom0,
> > or some other 2.6.27, 2.6.29, 2.6.30 dom0 kernel then it _could_ be a
bug
> in
> > them, and not in Xen.
> >
> > -- Pasi
> >
> > >
> > > > When I watch the system via "xm top" during the
restoration process,
> I
> > > > do notice the memory allocation for the VM increase all the
way to
> about
> > > > 1024MB.  Suddenly, the amount of memory allocated to the VM
decreases
> by
> > > > a bit, and then finally the VM disappears.
> > > >
> > > > It may be of interest that I don''t have issues
> > > > saving/restoring/migrating 32-bit PV domU''s on this
same set of
> 64-bit
> > > > dom0''s.  This seems to be an issue only with HVM
domU''s.
> 
> May be true, I too have observed this on my 64bit Dom-0 where I am running
> 32bit Dom-U''s. I guess they are running under HVM. Little
clarification is
> needed here.. Can we run 32 Dom-U''s under PV on 64 bit Dom-0 ?
> 
Yes, 32-on-64 is supported also for PV guests. 
32bit PV guests need to be PAE though.

-- Pasi

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

Pasi Kärkkäinen

2009-Jul-31 10:18 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

On Fri, Jul 31, 2009 at 11:25:09AM +0300, Pasi Kärkkäinen
wrote:> On Fri, Jul 31, 2009 at 10:19:04AM +0300, Pasi Kärkkäinen wrote:
> > On Thu, Jul 30, 2009 at 08:00:21PM -0400, Joshua West wrote:
> > > Hey all,
> > > 
> > > I''ve been attempting to get ''xm
restore'' (and thus ''xm migrate'') to work
> > > for a 32-bit HVM domU on a 64-bit dom0 running Xen 3.4.1-rc10. 
Has
> > > anyone else been able to do so?  I can boot the VM and work
within it
> > > just fine.  The ''xm save'' command also
functions properly; issue is just
> > > with ''restore'' and therefore
''migrate''.
> > > 
> > 
> > What dom0 kernel you are running?
> > 
> > If something else than linux-2.6.18-xen.hg please try with that
instead.
> > 
> 
> Also if you can reproduce this problem running linux-2.6.18-xen on dom0,
> then please send an email to xen-devel about this. Keir wants to release
Xen
> 3.4.1 final early next week, and this sounds like something that might be
> good to check before the release.
> 
> If this problem happens running for example Debian lenny 2.6.26-xen kernel
in dom0,
> or some other 2.6.27, 2.6.29, 2.6.30 dom0 kernel then it _could_ be a bug
in
> them, and not in Xen.
> 
Oh, one more thing: If you are running GPLPV drivers in Windows, please try
without them!

-- Pasi
> 
> > 
> > > When I watch the system via "xm top" during the
restoration process, I
> > > do notice the memory allocation for the VM increase all the way
to about
> > > 1024MB.  Suddenly, the amount of memory allocated to the VM
decreases by
> > > a bit, and then finally the VM disappears.
> > > 
> > > It may be of interest that I don''t have issues
> > > saving/restoring/migrating 32-bit PV domU''s on this same
set of 64-bit
> > > dom0''s.  This seems to be an issue only with HVM
domU''s.
> > > 
> > > The following is taken from /var/log/xen/xend.log and
demonstrates the
> > > failure:
> > > 
> > > [2009-07-30 19:48:18 4839] INFO (image:745) Need to create
platform
> > > device.[domid:37]
> > > [2009-07-30 19:48:18 4839] DEBUG (XendCheckpoint:261)
> > > restore:shadow=0x9, _static_max=0x40000000, _static_min=0x0,
> > > [2009-07-30 19:48:18 4839] DEBUG (balloon:166) Balloon: 31589116
KiB
> > > free; need 1061888; done.
> > > [2009-07-30 19:48:18 4839] DEBUG (XendCheckpoint:278)
[xc_restore]:
> > > /usr/lib64/xen/bin/xc_restore 4 37 2 3 1 1 1
> > > [2009-07-30 19:48:18 4839] INFO (XendCheckpoint:417)
xc_domain_restore
> > > start: p2m_size = 100000
> > > [2009-07-30 19:48:18 4839] INFO (XendCheckpoint:417) Reloading
memory
> > > pages:   0%
> > > [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) Failed
allocation
> > > for dom 37: 1024 extents of order 0
> > > [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) ERROR
Internal
> > > error: Failed to allocate memory for batch.!
> > > [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417)
> > > [2009-07-30 19:48:27 4839] INFO (XendCheckpoint:417) Restore exit
with rc=1
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2724)
> > > XendDomainInfo.destroy: domid=37
> > > [2009-07-30 19:48:27 4839] ERROR (XendDomainInfo:2738)
> > > XendDomainInfo.destroy: domain destruction failed.
> > > Traceback (most recent call last):
> > >   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> > > line 2731, in destroy
> > >     xc.domain_pause(self.domid)
> > > Error: (3, \047No such process\047)
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2204) No device
model
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2206) Releasing
devices
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing
vif/0
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> > > XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing
vbd/768
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> > > XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing
vfb/0
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> > > XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:2219) Removing
console/0
> > > [2009-07-30 19:48:27 4839] DEBUG (XendDomainInfo:1134)
> > > XendDomainInfo.destroyDevice: deviceClass = console, device =
console/0
> > > [2009-07-30 19:48:27 4839] ERROR (XendDomain:1149) Restore failed
> > > Traceback (most recent call last):
> > >   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line
> > > 1147, in domain_restore_fd
> > >     return XendCheckpoint.restore(self, fd, paused=paused,
> > > relocating=relocating)
> > >   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
> > > line 282, in restore
> > >     forkHelper(cmd, fd, handler.handler, True)
> > >   File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
> > > line 405, in forkHelper
> > >     raise XendError("%s failed" % string.join(cmd))
> > > XendError: /usr/lib64/xen/bin/xc_restore 4 37 2 3 1 1 1 failed
> > > 
> > > And here is the xmconfig file:
> > > 
> > > #---------------------------------------------------------------#
> > > import os, re
> > > arch_libdir = ''lib''
> > > arch = os.uname()[4]
> > > if os.uname()[0] == ''Linux'' and
re.search(''64'', arch):
> > >     arch_libdir = ''lib64''
> > > kernel = "/usr/lib/xen/boot/hvmloader"
> > > builder=''hvm''
> > > memory = 1024
> > > name = "winxen"
> > > vcpus=1
> > > vif = [ ''type=ioemu, bridge=xenbr100,
mac=aa:bb:cc:00:00:99'' ]
> > > disk = [ ''phy:/dev/drbd/by-res/vm_winxen,hda,w''
]
> > > device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
> > > boot="c"
> > > sdl=0
> > > opengl=1
> > > vnc=1
> > > vncpasswd=''...''
> > > stdvga=1
> > > monitor=1
> > > usbdevice=''tablet''
> > > #---------------------------------------------------------------#
> > > 
> > > One thing of interest I did also notice in the logs was during
the "xm
> > > save" process:
> > > 
> > > [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:110) [xc_save]:
> > > /usr/lib64/xen/bin/xc_save 56 36 0 0 4
> > > [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:388) suspend
> > > [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:113) In
> > > saveInputHandler suspend
> > > [2009-07-30 19:47:26 4839] DEBUG (XendCheckpoint:115) Suspending
36 ...
> > > [2009-07-30 19:47:26 4839] DEBUG (XendDomainInfo:511)
> > > XendDomainInfo.shutdown(suspend)
> > > [2009-07-30 19:47:26 4839] INFO (XendCheckpoint:417) xc_save:
failed to
> > > get the suspend evtchn port
> > > [2009-07-30 19:47:26 4839] INFO (XendCheckpoint:417)
> > > [2009-07-30 19:47:26 4839] DEBUG (XendDomainInfo:1709)
> > > XendDomainInfo.handleShutdownWatch
> > > [2009-07-30 19:47:27 4839] INFO (XendDomainInfo:1895) Domain has
> > > shutdown: name=migrating-winxen id=36 reason=suspend.
> > > [2009-07-30 19:47:27 4839] INFO (XendCheckpoint:121) Domain 36
suspended.
> > > [2009-07-30 19:47:27 4839] INFO (image:479)
signalDeviceModel:restore dm
> > > state to running
> > > [2009-07-30 19:47:27 4839] DEBUG (XendCheckpoint:130) Written
done
> > >  1: sent 266240, skipped 0, delta 8484ms, dom0 46%, target 0%,
sent
> > > 1028Mb/s, dirtied 0Mb/s 0 pages
> > > [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) Total pages
sent> > > 266240 (0.25x)
> > > [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) (of which 0
were
> > > fixups)
> > > [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) All memory
is saved
> > > [2009-07-30 19:47:36 4839] INFO (XendCheckpoint:417) Save exit
rc=0
> > > 
> > > Not sure if that xc_save error message has anything to do with
this...
> > > 
> > > If there is any additional information you need, such as how I
built Xen
> > > or even the ''xm save'' copy of the VM itself,
just let me know and I''ll
> > > make it available.
> > > 
> > > Thanks.
> > > 
> > > -- 
> > > Joshua West
> > > Senior Systems Engineer
> > > Brandeis University
> > > http://www.brandeis.edu
> > > 
> > > 
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Joshua West

2009-Jul-31 14:39 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Hi Pasi,

Regarding your questions below:

  * I am running linux-2.6.18-xen.hg (changeset 922 ... aka the latest).
  * dom0 OS is RHEL 5.3; however I am using all custom built rpms (which
I wrote) for Xen 3.4.1-rc10.
  * I haven''t tried this on any kernel other than 2.6.18.8... nor do I
wish to.
  * The Windows machine has the GPLPV drivers installed, but the issue
occurs even with them disabled.

I will now reformat the Windows VM and do a fresh install, just to fully
eliminate the possibility of GPLPV causing the issue.

If the issue still persists with the fully redone 32-bit HVM domU on my
64-bit dom0''s, I will repost the thread on xen-devel.

If you or anybody else needs the kernel configurations, my RPM .spec
files to see how things were built, or the domU saved copy itself, no
problem - just let me know and I''ll post it on the web.

Thanks.

Pasi Kärkkäinen wrote:> What dom0 kernel you are running?
>
> If something else than linux-2.6.18-xen.hg please try with that instead.
>> Also if you can reproduce this problem running linux-2.6.18-xen on
dom0,
>> then please send an email to xen-devel about this. Keir wants to
release Xen
>> 3.4.1 final early next week, and this sounds like something that might
be
>> good to check before the release.
>>
>> If this problem happens running for example Debian lenny 2.6.26-xen
kernel in dom0,
>> or some other 2.6.27, 2.6.29, 2.6.30 dom0 kernel then it _could_ be a
bug in
>> them, and not in Xen.
>>
>>     
>
> Oh, one more thing: If you are running GPLPV drivers in Windows, please try
> without them!
>
> -- Pasi
>
>   -- 
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu

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

Pasi Kärkkäinen

2009-Jul-31 14:48 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

On Fri, Jul 31, 2009 at 10:39:42AM -0400, Joshua West
wrote:> Hi Pasi,
> 
> Regarding your questions below:
> 
>   * I am running linux-2.6.18-xen.hg (changeset 922 ... aka the latest).
>   * dom0 OS is RHEL 5.3; however I am using all custom built rpms (which
> I wrote) for Xen 3.4.1-rc10.
>   * I haven''t tried this on any kernel other than 2.6.18.8... nor
do I
> wish to.
Ok, so that''s all good. 
>   * The Windows machine has the GPLPV drivers installed, but the issue
> occurs even with them disabled.
> 
> I will now reformat the Windows VM and do a fresh install, just to fully
> eliminate the possibility of GPLPV causing the issue.
> 
That''s good to try. Also try with vcpus=1, if you had multiple vcpus
for the
HVM guest.
> If the issue still persists with the fully redone 32-bit HVM domU on my
> 64-bit dom0''s, I will repost the thread on xen-devel.
> 
Yes, you should.
> If you or anybody else needs the kernel configurations, my RPM .spec
> files to see how things were built, or the domU saved copy itself, no
> problem - just let me know and I''ll post it on the web.
> 
Would be nice to take a look at those..

-- Pasi
> Thanks.
> 
> Pasi Kärkkäinen wrote:
> > What dom0 kernel you are running?
> >
> > If something else than linux-2.6.18-xen.hg please try with that
instead.
> >> Also if you can reproduce this problem running linux-2.6.18-xen on
dom0,
> >> then please send an email to xen-devel about this. Keir wants to
release Xen
> >> 3.4.1 final early next week, and this sounds like something that
might be
> >> good to check before the release.
> >>
> >> If this problem happens running for example Debian lenny
2.6.26-xen kernel in dom0,
> >> or some other 2.6.27, 2.6.29, 2.6.30 dom0 kernel then it _could_
be a bug in
> >> them, and not in Xen.
> >>
> >>     
> >
> > Oh, one more thing: If you are running GPLPV drivers in Windows,
please try
> > without them!
> >
> > -- Pasi
> >
> >   
> -- 
> Joshua West
> Senior Systems Engineer
> Brandeis University
> http://www.brandeis.edu
> 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Keith Coleman

2009-Jul-31 15:41 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

On Fri, Jul 31, 2009 at 10:39 AM, Joshua West<jwest@brandeis.edu>
wrote:> I will now reformat the Windows VM and do a fresh install, just to fully
> eliminate the possibility of GPLPV causing the issue.
>
> If the issue still persists with the fully redone 32-bit HVM domU on my
> 64-bit dom0''s, I will repost the thread on xen-devel.

I have completed a clean install of win2k3 on xen 3.4.1-rc10 and am
able to save/restore and live migrate. Perhaps your problems are
related to the GPLPV drivers. I will add them and continue my testing.

Keith Coleman

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

Joshua West

2009-Jul-31 15:44 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Hi Pasi,

Ok so at this point, I''ve reformatted the HVM domU.  The "xm
save"
followed by "xm restore" operation DOES work.  I suspect its because I
have no GPLPV drivers installed on this system -- even though they were
disabled on the previous domU which was having problems.

I''m updating the machine to SP2 and giving it the rest of its security
updates.  After that, I''ll try again and confirm that things still
work.

Once I confirm 32-bit HVM domU save/restore/migrate on 64-bit dom0 does
indeed function properly, I''ll try again with the GPLPV drivers.  If it
seems to be an issue with the GPLPV drivers, I''ll start a new thread on
xen-users and hopefully it will catch James Harper''s eye.

While I did get the GPLPV drivers installed and they seemed to function
properly, I''m not sure if everything was still perfect -- the docs on
the wiki for the PV driver installation seem to be a bit old and quite
conflicting in back-to-back sentences heh.  *shrug*.

Thanks for your help Pasi.

Pasi Kärkkäinen wrote:> On Fri, Jul 31, 2009 at 10:39:42AM -0400, Joshua West wrote:
>   
>> Hi Pasi,
>>
>> Regarding your questions below:
>>
>>   * I am running linux-2.6.18-xen.hg (changeset 922 ... aka the
latest).
>>   * dom0 OS is RHEL 5.3; however I am using all custom built rpms
(which
>> I wrote) for Xen 3.4.1-rc10.
>>   * I haven''t tried this on any kernel other than 2.6.18.8...
nor do I
>> wish to.
>>     
>
> Ok, so that''s all good. 
>
>   
>>   * The Windows machine has the GPLPV drivers installed, but the issue
>> occurs even with them disabled.
>>
>> I will now reformat the Windows VM and do a fresh install, just to
fully
>> eliminate the possibility of GPLPV causing the issue.
>>
>>     
>
> That''s good to try. Also try with vcpus=1, if you had multiple
vcpus for the
> HVM guest.
>
>   
>> If the issue still persists with the fully redone 32-bit HVM domU on my
>> 64-bit dom0''s, I will repost the thread on xen-devel.
>>
>>     
>
> Yes, you should.
>
>   
>> If you or anybody else needs the kernel configurations, my RPM .spec
>> files to see how things were built, or the domU saved copy itself, no
>> problem - just let me know and I''ll post it on the web.
>>
>>     
>
> Would be nice to take a look at those..
>
> -- Pasi
>
>   
>> Thanks.
>>
>> Pasi Kärkkäinen wrote:
>>     
>>> What dom0 kernel you are running?
>>>
>>> If something else than linux-2.6.18-xen.hg please try with that
instead.
>>>       
>>>> Also if you can reproduce this problem running linux-2.6.18-xen
on dom0,
>>>> then please send an email to xen-devel about this. Keir wants
to release Xen
>>>> 3.4.1 final early next week, and this sounds like something
that might be
>>>> good to check before the release.
>>>>
>>>> If this problem happens running for example Debian lenny
2.6.26-xen kernel in dom0,
>>>> or some other 2.6.27, 2.6.29, 2.6.30 dom0 kernel then it
_could_ be a bug in
>>>> them, and not in Xen.
>>>>
>>>>     
>>>>         
>>> Oh, one more thing: If you are running GPLPV drivers in Windows,
please try
>>> without them!
>>>
>>> -- Pasi
>>>
>>>   
>>>       
>> -- 
>> Joshua West
>> Senior Systems Engineer
>> Brandeis University
>> http://www.brandeis.edu
>>
>>     

-- 
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu


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

Joshua West

2009-Jul-31 15:50 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Hi Keith,

Thanks -- yeah its looking to be a GPLPV issue.  Which version are you
going to use in your testing?  I was using the
"gplpv-fre-wnet-x86_0.10.0.86.msi" package.


Keith Coleman wrote:> On Fri, Jul 31, 2009 at 10:39 AM, Joshua West<jwest@brandeis.edu>
wrote:
>   
>> I will now reformat the Windows VM and do a fresh install, just to
fully
>> eliminate the possibility of GPLPV causing the issue.
>>
>> If the issue still persists with the fully redone 32-bit HVM domU on my
>> 64-bit dom0''s, I will repost the thread on xen-devel.
>>     
>
>
> I have completed a clean install of win2k3 on xen 3.4.1-rc10 and am
> able to save/restore and live migrate. Perhaps your problems are
> related to the GPLPV drivers. I will add them and continue my testing.
>
> Keith Coleman
>   

-- 
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu


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

Joshua West

2009-Aug-02 18:44 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Keith,

Did you have any success with the GPLPV drivers and save/restore/migrate
functionality?

For the record of this email thread -- the issue does not seem to be
with Xen save/restore/migrate.  It works perfectly when using Xen
3.4.1-rc10 with a 32-bit HVM domU (Windows 2003 Server) on 64-bit dom0. 
The issue is definitely only shown after installing and booting with the
GPLPV drivers, version 0.10.0.86.

I''ll start a new thread about the GPLPV issue.

Joshua West wrote:> Hi Keith,
>
> Thanks -- yeah its looking to be a GPLPV issue.  Which version are you
> going to use in your testing?  I was using the
> "gplpv-fre-wnet-x86_0.10.0.86.msi" package.
>
>
> Keith Coleman wrote:
>   
>> On Fri, Jul 31, 2009 at 10:39 AM, Joshua West<jwest@brandeis.edu>
wrote:
>>   
>>     
>>> I will now reformat the Windows VM and do a fresh install, just to
fully
>>> eliminate the possibility of GPLPV causing the issue.
>>>
>>> If the issue still persists with the fully redone 32-bit HVM domU
on my
>>> 64-bit dom0''s, I will repost the thread on xen-devel.
>>>     
>>>       
>> I have completed a clean install of win2k3 on xen 3.4.1-rc10 and am
>> able to save/restore and live migrate. Perhaps your problems are
>> related to the GPLPV drivers. I will add them and continue my testing.
>>
>> Keith Coleman
>>   
>>     
>
>
>   

-- 
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu


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

Keith Coleman

2009-Aug-03 22:09 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

On Sun, Aug 2, 2009 at 2:44 PM, Joshua West<jwest@brandeis.edu>
wrote:> Keith,
>
> Did you have any success with the GPLPV drivers and save/restore/migrate
> functionality?
>
> For the record of this email thread -- the issue does not seem to be
> with Xen save/restore/migrate.  It works perfectly when using Xen
> 3.4.1-rc10 with a 32-bit HVM domU (Windows 2003 Server) on 64-bit dom0.
> The issue is definitely only shown after installing and booting with the
> GPLPV drivers, version 0.10.0.86.
>
> I''ll start a new thread about the GPLPV issue.
>
I tried gplpv-fre-wnet-x86_0.10.0.86.msi and lost the ability to
save/restore/migrate so I agree that this is most likely a GPLPV
issue.


Keith Coleman

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

Joshua West

2009-Aug-03 22:09 UTC

head link

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Keith Coleman wrote:> I tried gplpv-fre-wnet-x86_0.10.0.86.msi and lost the ability to
> save/restore/migrate so I agree that this is most likely a GPLPV
> issue.
>
>
> Keith Coleman
>   
>
Ok cool.  Indicates its not necessarily my setup/environment.

I started a new thread regarding the issue titled "GPLPV
save/restore/migrate Issues".

-- 
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu


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

Xen users - Jul 2009 - Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

[Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0

Re: [Xen-users] Xen 3.4.1-rc10: Cannot restore/migrate 32-bit HVM domU (W2K3 Server) on 64-bit dom0