[Fedora-xen] What's the Pre-requisites for virt-manager

[Henry Zhang]

Hi Dan,

 From Fedora site 
http://fedoraproject.org/wiki/Docs/Beats/Virtualization?highlight=%28xenguest-install%29

I find several information, I am sure if they are correct:

1, "Integrated graphical framebuffer. Both the GUI installer and the 
guest operating system's graphical environment can be accessed from 
virt-manager without the need for VNC."
As I remembered, you told me when we double-click any DomU, we will 
start a graphic console, this console just use virt-manmager embedded 
vnc-viewer to access DomU, so need vnc connection. Also I know when 
install a guest domain, there also will appear a vnc-viewer for install OS.
But from the above explanation, seems we never use vnc any more?

2,"CPU and memory management. The vCPUs and memory of active guest 
operating systems can be adjusted on the fly."
 From your website http://virt-manager.et.redhat.com/screenshots.html, I 
can see "Most of this dialog is currently non-functional. Compare with a 
scan of the design mockup" under "Virtual machine configuration", when I 
tried, seems it's true most of them can't work, so who is wrong?


Thanks,
Henry

Daniel P. Berrange 写道:
> On Fri, Nov 24, 2006 at 11:30:54AM +0800, Henry Zhang wrote:
>> hi Dan, I think it over, and seems more concern, see below,
>>
>> Daniel P. Berrange ??????:
>>> On Wed, Nov 22, 2006 at 07:31:07PM +0800, Henry Zhang wrote:
>>>  
>>>> Hi Daniel,
>>>>
>>>> Here I have another question on virt-manager, as you write "an embedded 
>>>> VNC client viewer provides console access to each of the guest domains", 
>>>> my concern is where is the vnc server, who provide it, and start it?
>>>> Need we setup vnc? I looked through the process used to create guest, 
>>>> seems there is no any step for vnc...
>>>>    
>>> The VNC server depends on what type of domain is being run. For HVM guests
>>> the VNC server is provided by the qemu-dm process assoicated with that
>>> guest. For paravirt guests, VNC is only available if you have the paravirt
>>> framebuffer patches applied to your xen tree - these are not in 
>>> xen-unstable
>>> yet. In paravirt, XenD will launch a xen-vncfb process to provide the VNC
>>> server. 
>> due to vnc connection is required by vnc-viewer, vnc-viewer can present 
>> the graphical console,
>> because there is no paravirt framebuffer patches applied to 
>> xen-unstable, so virt-manager can't work
>> with xen-unstable for paravirt guests, because we can't get the 
>> graphical console run. is it right?
> 
> That is correct - the paravirt framebuffer patches are no yet in the
> xen-unstable tree. In Fedora kernels we apply them as a patch ourselves
> since it was important to have graphical console available for both PV
> and FV guests in the same way. So any FC5, FC6 or RHEL-5 guest has the
> PV framebuffer patches available already, even though they're not 
> upstream
> 
>> xen-unstable should be the latest version of Xen, if it has no paravirt 
>> framebuffer patches, maybe xen-stable
>> should have no either? and if so, we may say virt-manager not support 
>> paravirt at the moment?
> 
> The PV framebuffer patches have been submitted several times & it looks
> like they are very close to being merged upstream. Perhaps next couple
> of weeks if all goes well.
> 
> Regards,
> Dan.