WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1328] live migration with DomU's vcpu = 1

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1328] live migration with DomU's vcpu = 1
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 28 Oct 2008 03:21:23 -0700
Delivery-date: Tue, 28 Oct 2008 03:21:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1328-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1328





------- Comment #4 from bruno.plantier@xxxxxxxxxxxxxxxx  2008-10-28 03:21 
-------
I have the same bug here and i confirm your walkaround is working.

One strange bahviour is that, after doing one successfull migration (with your
walkaround or with an offline- instead of a live- migration ) all the further
migration on this domU will be fine.



(In reply to comment #3)
> Hi Tom,
> 
> I got it!
> We havet to set "cpu" entry in /etc/xen/<Domain> to assign certain CPUs to one
> VPU.
> It can be also set with "xm vcpu-pin" from command line.
> You can check its status using "xm vcpu-list".
> 
> This is my configuration;
> -----------------------------------------------------------------
> name = "dom-ua1"
> uuid = "94d0f9b4-08f6-448c-8c9b-91ca999a5f4b"
> maxmem = 2048
> memory = 2048
> vcpus = 1    # the number of vcpu is "1"
> cpus = "0"   # assigned cpus is allocated at "0"
> bootloader = "/usr/bin/pygrub"
> on_poweroff = "destroy"
> on_reboot = "restart"
> on_crash = "restart"
> vfb = [ "type=vnc,vncunused=1,keymap=ja" ]
> disk = [ "phy:/dev/sdf1,xvda,w","tap:aio:/dev/sdf3,/dev/sdf,w!", ]
> vif = [ "ip=192.168.201.146/24,mac=00:16:3e:13:32:27,bridge=xenbr0", 
>         "ip=192.168.101.146/24,mac=00:16:3e:13:32:28,bridge=xenbr1", 
>         "ip=192.168.102.146/24,mac=00:16:3e:13:32:29,bridge=xenbr2", 
>         "ip=192.168.16.146/22,mac=00:16:3e:13:32:30,bridge=xenbr3", ]
> -----------------------------------------------------------------
> 
> !!! NOTICE !!! :)
> 
> The live migration would work fine the above setting.
> but if you call "xm vcpu-list" after migration,
> you would find that the status of cpu is changed like "any cpu".
> It seems that the live migration can not take over this configuration for now.
> It might be improved with the latest version, I hope.
> So, you had better to reset the cpu status with "xm vcpu-pin" after migration,
> if not, the return migration would fail.
> 
> If you can confirm that this configuration can work fine,
> close this buggzila, please.
> 
> Thanks!
> 


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>