[QUOTE=jmozdzen;9626]I think they’re talking about the “other” one - at least that’s what we’re using… and while the files are there until you delete them, you are right that they are not updated when you alter the definitions stored in the Xen config DB. Once you’re into clustering, you’ll want to only work with the files, as modifications to the Xen DB will only persist on a single Xen server, while you can share the files across many Xen Dom0s. But is should be easy to create up-to-date files, either manually or using virtmanager (just create a new VM with the proper settings and i.e. use the results as a template). Just keep in mind that you’ll have to actually DELETE the DomU definitions from the Xen store, else "xm create " wont have the desired effect and "xm start " will use the xen store definitions, rather than the config files.
Actually, they’re not different. SLES11 has simply dropped the Xen scripts to set up all the bridging environment - you do that in advance (outside the Xen configuration, ie via YaST) and then reference the bridge name you want the VIF to attach to, in the DomU config file. We did the same in SLES10 already, as we had other ideas of bridge names etc than the way Xen handled it 
I believe the DomU config file version will remain active for quite some time - it’s more difficult to run a Xen cluster with via a shared Xen store - AFAIK this isn’t available yet and IMO there’s no “business case” to implement this just to replace config files. But as boot loaders change and new features are available, the syntax and/or available commands within the config files will change over time… like when going from SLES10 to SLES11.
Indeed a valid approach - just make sure those changes are compatible with the SLES10 environment, else you’re fixed to running a SLES11 Dom0 
With regards,
Jens[/QUOTE]
Well actually the network bridging is different. I just attempted to import the “old” config (from the SLES10 machine) and the networking doesn’t even match up with how it is in SLES 11. Although that may have been due to the fact I was using bridging with custom script (the only way you really could do it in SLES 10).
Anyway, it seems the TID that Novell has is almost completely worthless. The first option is invalid as this isn’t a new install. The second option is vague and I can’t even get NTS to answer me back as to what it means.
Third option I cannot get to work because it won’t let me chroot /mnt or whatever (I get the error about /bin/bash not found or something). Never had that happen before, but then again I usually only do that via rescue installation.
4th option also doesn’t work if you ever made a change to the configuration. And I’m not sure if the command is listed properly. Novell has you running the xm with a -f instead of a -F. I believe the -f only works with the legacy file vs. the -F works with a file you exported via the xm list -l blah>blah command.
Now, I COULD get the 4th option to semi-work by using the -F command to import the exported VM. But I still got the error, but at that point it would let me modify the bootloader line.
Once I did that (paravirtualized DomU, BTW), it would boot, but then it refused to find the /dev/xvda3 for some reason (it IS there because it obviously boots fine on SLES10 Domu). Oh, and that’s also where I found that the bridging is totally different. It was trying to use “eth1” which isn’t even valid anymore, you have to pick paravirtualized - eth1 (br1) or whatever from the list.
So my whole opinion of the process is that you should give up hope on upgrading a SLES10 SP3 Dom0 to SLES11 SP2 and just start the entire thing from scratch and manually reinstall all your DomU.
Apparently nobody has ever bothered to actually TEST taking a DomU from SLES10 sP3 and trying to get it to run under SLES11 SP2 Dom0. At least the authors of the TID didn’t try it because none of their stuff works.
I may be daring and snap the LUNs and see what happens on an actual upgrade of the host OS (Dom0), but so far it seems one cannot easily take a DomU created on SLES10 SP3 and run it on SLES11 SP2 Dom0.