[virt-tools-list] How can I run virt-manager 0.8.5 and 0.8.6 at the same system?

[Bruno Lamps]

Hi,

Just found the software where I can see the error messages (the
kernel-related ones).

Package:        kernel
> Latest Crash:    Qua 02 Fev 2011 14:33:43
> Command:        not_applicable
> Reason:         WARNING: at lib/list_debug.c:26 __list_add+0x3f/0x81()
> Comment:        None
> Bug Reports:
>
> Package:        kernel
> Latest Crash:    Qua 02 Fev 2011 14:33:43
> Command:        not_applicable
> Reason:         WARNING: at lib/list_debug.c:30 __list_add+0x68/0x81()
> Comment:        None
> Bug Reports:
>

But I'm not sure that this is a clue, really. =/


On Mon, Feb 7, 2011 at 3:22 PM, Bruno Lamps <lampss at gmail.com> wrote:

> Hi, sorry to be this late, things are a little messed up here. =D
>
> Fedora isn't showing me the kernel dump in gnome tray, where can I find it?
>
> I located a log in /var/log/libvirt/libvirtd.log, previously actived:
>
> 14:36:17.444: debug : qemuMonitorGetBalloonInfo:1001 : mon=0x7f1ac800ce80
>> 14:36:17.444: debug : qemuMonitorCommandWithHandler:231 : Send command
>> 'info balloon' for write with FD -1
>> 14:36:20.203: debug : qemuMonitorCommandWithHandler:236 : Receive command
>> reply ret=-1 errno=104 0 bytes '(null)'
>> 14:36:20.276: debug : qemuMonitorIO:577 : Triggering EOF callback error? 1
>> 14:36:20.277: error : qemuMonitorCommandWithHandler:255 : cannot send
>> monitor command 'info balloon': Connection reset by peer
>> 14:36:20.277: error : qemuMonitorTextGetBalloonInfo:555 : operation
>> failed: could not query memory balloon allocation
>> 14:36:20.287: debug : qemuMonitorClose:691 : mon=0x7f1ac800ce80
>> 14:36:20.307: debug : qemuMonitorFree:200 : mon=0x7f1ac800ce80
>> 14:36:20.957: error : qemudDomainGetVcpus:6044 : Requested operation is
>> not valid: cannot list vcpu pinning for an inactive domain
>> 14:36:29.782: debug : qemuMonitorOpen:668 : New mon 0x7f1ac8014560 fd =37
>> watch=11
>> 14:36:29.782: debug : qemuMonitorSetCapabilities:902 : mon=0x7f1ac8014560
>> 14:36:29.872: debug : qemuMonitorGetPtyPaths:1702 : mon=0x7f1ac8014560
>> 14:36:29.874: debug : qemuMonitorCommandWithHandler:231 : Send command
>> 'info chardev' for write with FD -1
>> 14:36:29.876: debug : qemuMonitorCommandWithHandler:236 : Receive command
>> reply ret=0 errno=0 102 bytes 'monitor:
>> filename=unix:/var/lib/libvirt/qemu/stfcnc$
>> serial0: filename=pty:/dev/pts/2
>> '
>> 14:36:29.876: debug : qemuMonitorGetCPUInfo:982 : mon=0x7f1ac8014560
>> 14:36:29.876: debug : qemuMonitorCommandWithHandler:231 : Send command
>> 'info cpus' for write with FD -1
>> 14:36:29.879: debug : qemuMonitorCommandWithHandler:236 : Receive command
>> reply ret=0 errno=0 48 bytes '* CPU #0: pc=0x00000000000ffff0 thread_id=369
>> '
>> 14:36:29.879: debug : qemuMonitorTextGetCPUInfo:448 : vcpu=0 pid=369
>> 14:36:29.879: debug : qemuMonitorSetBalloon:1113 : mon=0x7f1ac8014560
>> newmem=1048576
>> 14:36:29.879: debug : qemuMonitorCommandWithHandler:231 : Send command
>> 'balloon 1024' for write with FD -1
>> 14:36:29.879: debug : qemuMonitorCommandWithHandler:236 : Receive command
>> reply ret=0 errno=0 0 bytes '(null)'
>> 14:36:29.879: debug : qemuMonitorStartCPUs:923 : mon=0x7f1ac8014560
>> 14:36:29.879: debug : qemuMonitorCommandWithHandler:231 : Send command
>> 'cont' for write with FD -1
>> 14:36:29.880: debug : qemuMonitorCommandWithHandler:236 : Receive command
>> reply ret=0 errno=0 0 bytes '(null)'
>> 14:36:29.881: debug : qemuMonitorGetBalloonInfo:1001 : mon=0x7f1ac8014560
>> 14:36:29.881: debug : qemuMonitorCommandWithHandler:231 : Send command
>> 'info balloon' for write with FD -1
>> 14:36:29.892: debug : qemuMonitorCommandWithHandler:236 : Receive command
>> reply ret=0 errno=0 22 bytes 'balloon: actual=1024
>>
>
> Does this log help you guys? I tried windows 2003 and windows 7 isos, both
> installation processes stops right after HD formatting.
>
>
> On Thu, Feb 3, 2011 at 10:20 AM, Richard W.M. Jones <rjones at redhat.com>wrote:
>
>> On Wed, Feb 02, 2011 at 03:14:47PM -0300, Bruno Lamps wrote:
>> > But today I noticed that I'm not able to run (not even install) windows
>> 2003
>> > VMs. LOL
>> > I create the machine, boot the install cd, format the disk, and the
>> machine
>> > goes down unexpectedly. Fedora gives me some crach report, saying that
>> some
>> > kernel crach happened. Then I turn the VM on again, but the disk image
>> isn't
>> > bootable, and if I try to run the win2003 install CD again, it crashes
>> > again, same way.
>>
>> We don't print these reports out for entertainment.  Please post
>> the full messages you see into a new bug.
>>
>> Rich.
>>
>> --
>> Richard Jones, Virtualization Group, Red Hat
>> http://people.redhat.com/~rjones
>> virt-df <http://people.redhat.com/%7Erjones%0Avirt-df> lists disk usage
>> of guests without needing to install any
>> software inside the virtual machine.  Supports Linux and Windows.
>> http://et.redhat.com/~rjones/virt-df/
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/virt-tools-list/attachments/20110208/6b640dd2/attachment.htm>