https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c1 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |carnold@suse.com, | |cyliu@suse.com, | |jfehlig@suse.com InfoProvider| |stanley@stronglg.demon.co.u | |k --- Comment #1 from James Fehlig 2014-01-07 02:02:59 UTC --- In openSUSE13.1, the new xl/libxl (aka libxenlight) toolstack is prefered over xm/xend. In fact, the latter is deprecated upstream and slated for removal. Can you disable/remove xend and see if your existing VM's start using the new libxl stack? libxl doesn't support the notion of managed or persistent domains, so you will need to import your existing domains into libvirt. Before disabling/removing xend, you can export the current libvirt domXML for each domain with e.g. virsh dumpxml dom-name > dom-name.xml After disabling/removing xend and restarting libvirtd, you can import the domains using the libxl driver with virsh define dom-name.xml -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c3 --- Comment #3 from Stanley Dziegiel 2014-01-13 23:14:59 UTC --- Thanks for the information. The virsh dumpxml dom-name > dom-name.xml worked for about half of the virtual machines that I had. The other half ended up with xml files of size 1, so I discarded those. I then removed xend and rebooted. The calls of virsh define dom-name.xml all failed with 2 lines of error message similar to: error: Failed to define domain from Debian6.xml error: internal error: no supported architecture for os type 'hvm' I decided to change tack and see if I could create a new virtual machine via Virtual Machine Manager and use the config file that gets generated to allow me to recover my existing domU hosts. I have had a little more success and got all the way through to near the end of installing a Debian iso but I need to go through it again. The good news is that, with xend removed, creating a new virtual machine stays up for more than 90 seconds. Overall I am 50% of the way there. I just need to spend a solid block of time finishing this off. I will try creating a new VM again at the weekend (probably DSL as it will be quick) and merge its config into the existing domUs to see if I can revive them. I will also read bug#857271 in more detail. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c5 --- Comment #5 from Stanley Dziegiel 2014-01-19 19:55:13 UTC --- Created an attachment (id=574892) --> (http://bugzilla.novell.com/attachment.cgi?id=574892) Output of 'virsh capabilities' -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c7 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jdouglas@suse.com |jfehlig@suse.com --- Comment #7 from James Fehlig 2014-01-20 19:07:40 UTC --- Re. #3 an #5: The capabilities look fine. Do you still have Debian6.xml that caused error: Failed to define domain from Debian6.xml error: internal error: no supported architecture for os type 'hvm' ? If so, please attach. Re. #6: error: Domain not found: xenGetDomainDefForName Strange, libvirt requested domain details for 'Fedora18' from xend, but xend claims it knows nothing of 'Fedora18'. Could you see the domain with xm? E.g. 'xm list --long Fedora18'? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c9 --- Comment #9 from Stanley Dziegiel 2014-01-20 19:49:08 UTC --- The Debian6.xml was: <domain type='xen'> <name>Debian6</name> <description>None</description> <uuid>695a10d4-6d61-d1ba-8307-63afe8a07142</uuid> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu>1</vcpu> destroy restart destroy <clock sync='utc'/> <os> <type>hvm</type> <loader>/usr/lib/xen/boot/hvmloader</loader> <boot dev='hd'/> </os> <features> <acpi/> <pae/> </features> <devices> <emulator>/usr/lib/xen/bin/qemu-dm</emulator> <disk type='file' device='disk'> <driver name='file'/> <source file='/var/lib/xen/images/Debian6/disk1.raw'/> <target dev='hda'/> </disk> <disk type='file' device='cdrom'> <driver name='file'/> <source file='/xen/isos/debian-6.0.6-amd64-netinst.iso'/> <target dev='hdc'/> <readonly/> </disk> <interface type='bridge' model='rtl8139'> <mac address='00:16:3e:60:ad:1c'/> <script path='/etc/xen/scripts/vif-bridge'/> </interface> <graphics type='vnc'/> </devices> </domain> I have removed xm from the system. I am fairly sure that a simple 'xm list' showed Fedora18 as one of the hosts but I would not have run 'xm list --long Fedora18'. I have the old Fedora18.xml if that would help. As a matter of interest which file is actually used: the plain Debian6 or Debian6.xml? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c11 --- Comment #11 from Stanley Dziegiel 2014-01-21 18:54:24 UTC --- I have always used Yast -> Virtual Machine Manager (VMM) to control the virtual machines. Since the change from xm to xl (comment #3) I can only see the virtual machines that I have created afresh. VMM no longer displays the old virtual machines. When I click on VMM I am presented with this: localhost(QEMU) - Not Connected localhost(xen) - Not Connected I believe that the QEMU entry is new in 13.1. I double click on the xen line and the display becomes: localhost(QEMU) - Not Connected localhost(xen) dsl13.1 (shutoff) so from my point of view the old xml files are not visible, which includes the Debian6.xml file that I have edited. I tried copying the amended Debian6.xml from /etc/xen/vm to /etc/libvirt/libxl where the new dsl13.1.xml got created but it isn't recognized by VMM and I am wary of randomly trying things. I am happy, indeed would prefer, to try using xl to try to recover the old *.xml files (with or without your suggested edit) but I will need some guidance as to what I need to type. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c13 Thomas Wagner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |t.wagner@inode.at --- Comment #13 from Thomas Wagner 2014-02-27 20:21:27 UTC --- I also have the problem with xend after upgrading to openSuse 13.1. At the moment I have to stay on xend toolstack because I use the pvscsi module which is not in the upstream kernel and is only supported with xend as far as I know. I found - I think - a similar hint/problem description here: http://forge.univention.org/bugzilla/show_bug.cgi?id=20481 I tried the work around mentioned there but it did not work for me. I know that xend is deprecated but I hope the toolstack can be fixed at least in openSuse 13.1. The dicision to which toolstack / GUI I shall switch in the future is not easy at all at the moment I think. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c15 --- Comment #15 from James Fehlig 2014-03-03 00:08:21 UTC --- Maybe there is something telling in /var/log/libvirt/libxl/Debian6.log -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c17 --- Comment #17 from James Fehlig 2014-03-03 21:19:42 UTC --- (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. Do you see Debian6 with 'xl list'? Is it running and accessible? Can you access its console or framebuffer (VNC)? 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. 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? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c19 --- Comment #19 from Stanley Dziegiel 2014-03-03 23:08:24 UTC --- (In reply to comment #17)

(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.

https://bugzilla.novell.com/show_bug.cgi?id=856973 https://bugzilla.novell.com/show_bug.cgi?id=856973#c21 --- Comment #21 from Stanley Dziegiel 2014-03-04 18:43:13 UTC --- If I copy those 5 lines verbatim into Debian6.xml, remove the existing 5 lines and run virsh define Debian6.xml it works. Thank you. [ N.B. just adding the <source bridge='br0'/> still failed. Guess what I did first? ] I reckon that these are the steps that we used to revive the openSuSE 12.3 Debian6 domU in openSuSE 13.1: 1. remove xend 2. update device='cdrom' stanza to use <driver name='qemu'/> 3. destroy any existing VMs with xl destroy Debian6 4. update Debian6.xml to use the interface type='bridge' stanza to what you suggested above in #20 5. virsh define Debian6.xml 6. YaST -> VMM -> localhost(xen) -> Debian6 -> <click start button> Feel free to amend it if I have missed anything. Thanks again. -- 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.