atom feed14 messages in [et-mgmt-tools] [RFC]Re: [libvirt...
FromSent OnAttachments
S.SakamotoSep 19, 2008 2:43 am.jpg, .jpg
Daniel P. BerrangeSep 19, 2008 3:07 am 
S.SakamotoOct 1, 2008 2:48 am 
S.SakamotoOct 9, 2008 2:10 am.patch
Atsushi SAKAIOct 14, 2008 9:20 pm 
S.SakamotoOct 14, 2008 10:04 pm.patch
Atsushi SAKAIOct 16, 2008 6:43 am 
Cole RobinsonOct 16, 2008 8:05 am 
S.SakamotoOct 20, 2008 1:44 am.patch
S.SakamotoOct 24, 2008 1:29 am 
Cole RobinsonOct 28, 2008 8:25 am 
S.SakamotoOct 29, 2008 5:21 pm.patch
Cole RobinsonOct 30, 2008 2:18 pm.patch
S.SakamotoOct 30, 2008 6:29 pm 
Subject:Re: [et-mgmt-tools] [RFC]Re: [libvirt] [RFC][PATCH] virt-managercalls migration API
From:S.Sakamoto (
Date:Oct 1, 2008 2:48:27 am

Hi, Daniel

Sorry for delaying response.

Thank you for your suggestions. I understand. I will make the prototype patch!

Thanks Shigeki Sakamoto.

On Fri, Sep 19, 2008 at 06:43:37PM +0900, S.Sakamoto wrote:

You probably want to send this to et-mgmt-list, which is where virt-manager development happens,

OK. For this, I tried to hear in et-mgmt-list.

I'm sorry to be pressing, but would you give me a comment on this patch for going on the next step to migrate from virt-manager ? I attached screenshots this patch shows.

I think rather than having it popup a new window with a list of hosts to migrate to, you could just have a sub-menu where you choose the destination host directly.


right-click | +- Run Pause Shutdown -------- Migrate ----> ...etc...

When the user selects one of these hosts, it'd popup a confirmation window, and do the neccessary migration checks, and then allow the admin to confirm to start the migration.

I sent an e-mail last month with proposals for doing this within libvirt. I put up all of the information I have in the libvirt wiki here:

Thank you for your information. I see above libvirt wiki and I have a few idea adding checks within libvirt. These point of view are Guest and Host sanity in BASIC CHECKS. How about this points ?

1)Guest sanity is checking whether already existing or not on the destination. Otherwise the uniqueness of the domain(UUID, name) are lost. * I think that it is right to check this in libvirt. How do you think this ?

Yes, checking for name/uuid uniqueness has to be done inside libvirt by each hypervisor driver according to their own rules.

2)Host sanity is checking whether a migration flag is ON at each

virt-manager will need to check the kind of things on the TodoPreMigrationChecks wiki page.