Re: QEMU without KVM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It didn't abort during initialization ... it aborted when I clicked on the VNC (I'm assuming) window.  In the log file, the error first occurs with the call to hald (which wasn't installed on this system).

Once I installed hal, this problem cleared up (I guess that's one to put in the troubleshooting guide huh?).  The screen grabs work perfectly:)

Now I just need to finish my networking on the host side and I'll be all set (any hints?).

BTW:  My target is RHEL5, but I'm using a lot of software that doesn't have RPMs yet, so I'm working this all out on Gentoo.  As I mentioned before, I'm also going to write up a comprehensive how-to.

I'm using the system to test installation scripts.  One of the things that would be very handy is the ability to copy a guest (image file, configuration, etc.).  It could use the same wizard that's used to create a new guest, with everything already filled in (except a couple obvious fields).

Once I have some of this running, I'll dig into the Python code for virt-manager a bit ... I should be able to add a few enhancements myself.

Thanks again, smoyer

On Thursday 17 May 2007 15:25, Daniel P. Berrange wrote:
> On Thu, May 17, 2007 at 03:19:33PM -0400, Steven W. Moyer wrote:
> > > What is the error ? Is there anything in /root/.virt-manager/virt-manager.log
> > > after the crash.
> > 
> > This hasn't solved the problem with virt-manager (and children) crashing when I click in a child window (just DSL for now).  The error messages are a bit cleaner now that the networking issue if fixed (and I guess we know they're not related).  Here's what shows up on the console:
> > 
> > smoyernew images # virt-manager
> > process 5225: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
> > See the manual page for dbus-uuidgen to correct this issue.
> >   D-Bus not built with -rdynamic so unable to print a backtrace
> > Aborted
> 
> The word 'Aborted' is the key there. We call the DBus library, but it
> is hitting a fatal error during its initialization & aborting the entire
> process. That's not something we can work around in virt-manager :-(
> 
> Really need to figure out why dbus isn't setup correctly on this 
> machine. On Fedora systems that directory is created automatically by
> the RPM install  
> 
> $ rpm -qf /var/lib/dbus/
> dbus-1.0.1-12.fc6
> 
> Dan.

-- 
Steven W. Moyer
Principle Architect, Assurance Applications

C-COR Solutions, LLC
60 Decibel Road
State College, PA  16801

Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer@xxxxxxxxx

AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1@xxxxxxxxxxxxxxxxx
MSN: smoyer64
Yahoo: smoyer64


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]