[et-mgmt-tools] Re: Re: Virt-manager: 5.0, 5.1, 5.2 fail in, Fedora 7

Tue Oct 23 05:39:29 UTC 2007

et-mgmt-tools-request at redhat.com wrote:
> Send et-mgmt-tools mailing list submissions to
> 	et-mgmt-tools at redhat.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.redhat.com/mailman/listinfo/et-mgmt-tools
> or, via email, send a message with subject or body 'help' to
> 	et-mgmt-tools-request at redhat.com
>
> You can reach the person managing the list at
> 	et-mgmt-tools-owner at redhat.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of et-mgmt-tools digest..."
>
>
> Today's Topics:
>
>    1. Re: Re: Virt-manager:  5.0, 5.1, 5.2 fail in, Fedora 7
>       (Hugh O. Brock)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 22 Oct 2007 09:28:01 -0400
> From: "Hugh O. Brock" <hbrock at redhat.com>
> Subject: Re: [et-mgmt-tools] Re: Virt-manager:  5.0, 5.1, 5.2 fail in,
> 	Fedora 7
> To: Fedora/Linux Management Tools <et-mgmt-tools at redhat.com>
> Message-ID: <20071022132801.GL15667 at redhat.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Sat, Oct 20, 2007 at 08:11:15PM -1000, Lawrence Nitz wrote:
>   
>>>  
>>>       
>> Thank, Hugh!
>> I opened  virt-manager explicitly from a root terminal window this 
>> evening. Once I connect to the Xen hypervisor, I can see two machines  
>> that I made last week, and have the Open and Detatils buttons on the 
>> bottom right of the main screen.  There is no Create button, even though 
>> I am running as root.
>>
>> I have options of Run, Pause, Shutdown, Details, Open in the right mouse 
>> button click over the machines.  I can open and start either of the two 
>> machines, and the machines show cpu and memory usage, but without a 
>> window in which to see the execution.
>>
>> I cannot bring up a response to the Details menu option on any of the 
>> machines-- Domain-0  or the two guests I had created.
>>
>>     
>
> Interesting, something is definitely not right. Do you see anything in
> /root/.virt-manager/virt-manager.log? Also, what do you see when you
> run virt-manager as root with the --no-fork option from the command
> line? Finally, what versions of virtinst and libvirt are you using?
>
> Thanks,
> --Hugh
>
>
>
> ------------------------------
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>
> End of et-mgmt-tools Digest, Vol 14, Issue 29
> *********************************************
>   
1.Virt-install version  virtinst-0.300-1.tar
2. Libvirt    libvirt-python -0.3.3-1.x86_64.rpm
3.                libvirt-devel-0.3.3-1.x86_64.rpm

In Log, 18 Oct:  Cannot find gtkvnc.   
gtk-vnc-python-0.2.0-2.fc7.x86-64  installed already

t the beginning of my session this evening, I installed the 
gtk-vnc-devel version from the Red Hat installer's archive.

Response to virt-manager  --no-fork
Attempt to open one of the displayed systems gives the window for the 
machine, then this error prompt.
 "Enable the local advanced programmable interrupt controller (APIC0.  
The X64-b ased operating system you are loding does not have APIC enabled.
The x64-based operating system yo are loding does not have APIC enab 
led.  Check the system's firmware settings and make sure the firmware 
has enabled APIC on this system............"

{I did not see this on the virt-manager opened without the --no-fork 
option earlier, but I saw no working screen for installing the client os.}

Virt-manager-log2 was collected using the --no-forks option.  Using it, 
I could randomly see my existing VM machines, and could open one, but it 
had no network connectivity--ip numbers were given in hex, like mac 
addresses.   Attempting to run or open all the other existing virtual 
machines (some defined only as far as setting up the machine's file) 
caused the virt-manager to immediately bomb.

The logs here are pretty complex. As far as I can tell, I should not use 
any specification of 2 processors for a VM.  There is some issue with 
the network, but I cannot determine what it is.

Finally, I have included my last virt-manager no-fork traceback as it 
spooled on the root terminal.  In this run, there were no bombs, but the 
windows for the VM systems did not open.

I am sorry that I cannot be more clear, but it is very hard for me to 
tell what is happening across the processes that are running.

Larry Nitz

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: virtmanager_nofork_output.txt
URL: <http://listman.redhat.com/archives/et-mgmt-tools/attachments/20071022/b10713f9/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: virt-manager.log
Type: text/x-log
Size: 32505 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/et-mgmt-tools/attachments/20071022/b10713f9/attachment.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: virt-manager-log2
URL: <http://listman.redhat.com/archives/et-mgmt-tools/attachments/20071022/b10713f9/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: virt-manager-nofork-traceback
URL: <http://listman.redhat.com/archives/et-mgmt-tools/attachments/20071022/b10713f9/attachment-0001.ksh>