<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.12.0"> </HEAD> <BODY> Typically you see that if Xen times out waiting to connect some devices. While it's "waiting to come up" please run virsh dumpxml rhel4pv1 This should show what devices it's looking to connect. Maybe it's unable to access the disk image - for example if your disk image file is some place other than /var/lib/xen/images and SELinux is in enforcing mode. Another common time we see this is when virt-install/virt-manager thinks you have a bridge called xenbr0 when infact you're using xenbr1. Look at dumpxml's output - look to see if the bridge interface there exists ? On Mon, 2007-03-26 at 13:08 +0100, Richard W.M. Jones wrote: <BLOCKQUOTE TYPE=CITE> <PRE> Deependra Shekhawat wrote: > Hi, > > Thanks for the script. It's working. But now I got a new problem. > Whenever I try to create a new virtual machine using either virt-install > or virt-manager I get this error: > Failed to get devices for domain rhel5pv1 > libvirt.libvirtError: virDomainCreateLinux() failed Are you getting any messages appearing in /root/.virt-manager/virt-manager.log? Rich. -- Fedora-xen mailing list <A HREF="mailto:Fedora-xen@redhat.com">Fedora-xen@redhat.com</A> <A HREF="https://www.redhat.com/mailman/listinfo/fedora-xen">https://www.redhat.com/mailman/listinfo/fedora-xen</A> </PRE> </BLOCKQUOTE> <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> <PRE> -- Andrew Cathrow Red Hat, Inc. (678) 733 0452 - Mobile (404) 437 6178 - Home Office <A HREF="mailto:acathrow@redhat.com">acathrow@redhat.com</A> </PRE> </TD> </TR> </TABLE> </TD> </TR> </TABLE> </BODY> </HTML>