https://bugzilla.novell.com/show_bug.cgi?id=856973
https://bugzilla.novell.com/show_bug.cgi?id=856973#c19
--- Comment #19 from Stanley Dziegiel
(In reply to comment #16)
libxl: error: libxl.c:321:libxl__domain_rename: domain with name "Debian6" already exists.
Seems Debian6 is already running. Did you happen to previously start it with xl? Or maybe the libvirt libxl driver did not properly cleanup a previously failed start attempt, leaving behind a skeletal domain.
I did not knowingly start it with xl. After the reboot I have always used YaST -> VMM to start Debian6, so if there is a skeletal domain it must persist across reboots.
Do you see Debian6 with 'xl list'? Is it running and accessible? Can you access its console or framebuffer (VNC)?
Yes: xl list Name ID Mem VCPUs State Time(s) Domain-0 0 6797 4 r----- 2991.3 Debian6 1 512 1 r----- 107951.1 I have forgotten how to access its console/frame buffer. What I want is for everything to work via VMM as it did before the upgrade to openSuSE 13.1.
If the domain is running and responds to shutdown requests, you can use 'xl shutdown Debian6' to gracefully shut it down, otherwise 'xl destroy Debian6' to destroy it. Then try starting Debian6 with libvirt (virsh) or virt-manager.
I ran xl shutdown Debian6 but it seemed to have no effect as xl list reports the same as above. xl destroy Debian6 did work as a subsequent xl list only displayed the Domain-0 entry. I then tried my preferred sequence of: YaST -> VMM -> localhost(xen) -> Debian6 -> <click start button> but I get the same Traceback as I usually do (posted in #14).
BTW, it seems you succeeded importing your domains into libvirt with 'virsh define dom.xml', since the traceback in #14 shows that you are trying to start one with virt-manager. Is that correct?
Yes I did succeed in importing the Debian6 domain (see first line of post #14). FYI: the log file now contains many more lines each time I click the start button. I am attaching that log (post #17: 123 lines). The only things that stand out are the error messages about xenbr0 as they do not tie up with the output of netstat -nr: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 br0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br0 as that is using br0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.