Re: [XenPPC] libvirt virt-manager/virsh status - working - update

2007-07-10 Thread Christian Ehrhardt
Just an update now that I finished my look around through libvirt xenppc 
support.


working
 *monitor load
 *remove network interface
 *remove hard disk
 *access serial console
 *define existing xen domains from/to xml file (virsh works 
virt-manager has no interface for that)

 *run/shutdown domains
partially working
 *add network device (work but cause a libvirt bug afterwards)
 *add hard disk (work but cause a libvirt bug afterwards)
not working
 *sometimes xend hangs and only /etc/init.d/xend restart helps, 
there are tracebacks in xend.log

 *change number of cpu's
 *create virtual network (libvirt bug) 



BTW - here iss a small howto for getting existing domains that run with 
xm to get managed by libvirt:

1. start domain(s) with xm create
2. use virsh dumxml DOMAINNAME
3. store the output in a xml file
4. virsh define XMLFILENAME
Now domains appear in virsh and virt-manager (=libvirt) even if they are 
off and can be started via that management tools.



Currently I have no plan to debug the few failing scenarios, so atm just 
for documentation reasons the xend  libvirt tracebacks that I found:


XEND
Sometimes:
[2007-08-04 00:04:28 8383] ERROR (XendConfig:925) dumping sxp from 
device controllers

Traceback (most recent call last):
 File //usr/lib/python/xen/xend/XendConfig.py, line 911, in to_sxp
   configs = controller.configurations()
 File //usr/lib/python/xen/xend/server/DevController.py, line 229, in 
configurations

   return map(self.configuration, self.deviceIDs())
 File //usr/lib/python/xen/xend/server/DevController.py, line 236, in 
configuration

   configDict = self.getDeviceConfiguration(devid)
 File //usr/lib/python/xen/xend/server/ConsoleController.py, line 23, 
in getDeviceConfiguration

   result = DevController.getDeviceConfiguration(self, devid)
 File //usr/lib/python/xen/xend/server/DevController.py, line 270, in 
getDeviceConfiguration

   raise VmError(Device %s not connected % devid)
VmError: Device 0 not connected


Rare:
[2007-08-04 00:03:12 8383] ERROR (SrvBase:88) Request shutdown failed.
Traceback (most recent call last):
 File //usr/lib/python/xen/web/SrvBase.py, line 85, in perform
   return op_method(op, req)
 File //usr/lib/python/xen/xend/server/SrvDomain.py, line 65, in 
op_shutdown

   return self.dom.shutdown(req.args['reason'][0])
 File //usr/lib/python/xen/xend/XendDomainInfo.py, line 447, in shutdown
   raise XendError('Domain cannot be shutdown')
XendError: Domain cannot be shutdown

VIRT-MANAGELIBVIRT
Adding network card:
pbclient4:~ # virt-manager
libvir: Xen Daemon error : POST operation failed: (xend.err Error 
creating domain: VM name 'SLES10_G2' already exists as domain 3)

Failed to create inactive domain SLES10_G2
Traceback (most recent call last):
 File /usr/local/share/virt-manager/virtManager/addhardware.py, line 
305, in finish

   self.add_network()
 File /usr/local/share/virt-manager/virtManager/addhardware.py, line 
340, in add_network

   self.vm.add_device(xml)
 File /usr/local/share/virt-manager/virtManager/domain.py, line 547, 
in add_device

   self.get_connection().define_domain(newxml)
 File /usr/local/share/virt-manager/virtManager/connection.py, line 
267, in define_domain

   self.vmm.defineXML(xml)
 File /usr/local/lib/python2.5/site-packages/libvirt.py, line 519, in 
defineXML
   if ret is None:raise libvirtError('virDomainDefineXML() failed', 
conn=self)
libvirt.libvirtError: virDomainDefineXML() failed POST operation failed: 
(xend.err Error creating domain: VM name 'SLES10_G2' already exists

as domain 3)


Adding Disk:
libvir: Xen Daemon error : POST operation failed: (xend.err Error 
creating domain: VM name 'SLES10_G2' already exists as domain 3)

Failed to create inactive domain SLES10_G2
Traceback (most recent call last):
 File /usr/local/share/virt-manager/virtManager/addhardware.py, line 
307, in finish

   self.add_storage()
 File /usr/local/share/virt-manager/virtManager/addhardware.py, line 
389, in add_storage

   self.vm.add_device(xml)
 File /usr/local/share/virt-manager/virtManager/domain.py, line 547, 
in add_device

   self.get_connection().define_domain(newxml)
 File /usr/local/share/virt-manager/virtManager/connection.py, line 
267, in define_domain

   self.vmm.defineXML(xml)
 File /usr/local/lib/python2.5/site-packages/libvirt.py, line 519, in 
defineXML
   if ret is None:raise libvirtError('virDomainDefineXML() failed', 
conn=self)
libvirt.libvirtError: virDomainDefineXML() failed POST operation failed: 
(xend.err Error creating domain: VM name 'SLES10_G2' already exists

as domain 3)

Adding virtual network:
libvir: error : library call virNetworkDefineXML failed, possibly not 
supported

Traceback (most recent call last):
 File /usr/local/share/virt-manager/virtManager/createnet.py, line 
297, in finish

   self.conn.create_network(xml)
 File /usr/local/share/virt-manager/virtManager/connection.py, line 
256, in create_network

   net = 

Re: [XenPPC] 64bit apps in DomU should get a more useful error message [Fixed]

2007-07-10 Thread Christian Ehrhardt

Jimi Xenidis wrote:

Now Executed in a xenppc DomU
./hellobit.32
Hello World!
./hellobit.64
-bash: ./hellobit.64: No such file or directory
hmm.. this works just fine for me and should have nothing to do with 
Xen at all, unless your block device does not work :)

can you cat it? ls it? file it?
Yes I can (tested it already). Hollis suggested that there may be some 
compat libraries missing but I did not find an obvious one missing.
And thats right, some links in /lib64 were broken while I created the 
DomU image files from my Dom0 some months ago.

I should never trust rpm -qa without checking file existence ;-)

=Fixed, the following is just a bit of output how it looks like so that 
everyone with a similar issue will find some help here via google.


DomU:
uname -a
Linux xen_SLES10_G1 2.6.18-Xen #25 SMP Sun Jul 29 00:29:02 CEST 2007 
ppc64 ppc64 ppc64 GNU/Linux

file hellobit.32 hellobit.64
hellobit.32: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 
(SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for 
GNU/Linux 2.6.4, not stripped
hellobit.64: ELF 64-bit MSB executable, cisco 7500, version 1 (SYSV), 
for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for 
GNU/Linux 2.6.4, not stripped

ldd hellobit.32
   linux-vdso32.so.1 =  (0x0010)
   libc.so.6 = /lib/power4/libc.so.6 (0x0fe8b000)
   /lib/ld.so.1 (0xf7fe1000)
ldd hellobit.64
   not a dynamic executable

Dom0:
uname -a
Linux pbclient4 2.6.18-Xen #25 SMP Sun Jul 29 00:29:02 CEST 2007 ppc64 
ppc64 ppc64 GNU/Linux

file hellobit.32 hellobit.64
hellobit.32: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 
(SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), not 
stripped
hellobit.64: ELF 64-bit MSB executable, 64-bit PowerPC or cisco 7500, 
version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared 
libs), not stripped

ldd hellobit.32
   linux-vdso32.so.1 =  (0x0010)
   libc.so.6 = /lib/libc.so.6 (0x0fe8d000)
   /lib/ld.so.1 (0xf7fe1000)
ldd hellobit.64
   linux-vdso64.so.1 =  (0x0010)
   libc.so.6 = /lib64/libc.so.6 (0x04055000)
   /lib64/ld64.so.1 (0x0400)

--

Grüsse / regards, 
Christian Ehrhardt


IBM Linux Technology Center, Open Virtualization
+49 7031/16-3385
[EMAIL PROTECTED]
[EMAIL PROTECTED]

IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Johann Weihen 
Geschäftsführung: Herbert Kircher 
Sitz der Gesellschaft: Böblingen

Registergericht: Amtsgericht Stuttgart, HRB 243294


___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel


Re: [XenPPC] 64bit apps in DomU should get a more useful error message [Fixed]

2007-07-10 Thread Jimi Xenidis


On Jul 10, 2007, at 9:22 AM, Christian Ehrhardt wrote:


Jimi Xenidis wrote:

Now Executed in a xenppc DomU
./hellobit.32
Hello World!
./hellobit.64
-bash: ./hellobit.64: No such file or directory
hmm.. this works just fine for me and should have nothing to do  
with Xen at all, unless your block device does not work :)

can you cat it? ls it? file it?
Yes I can (tested it already). Hollis suggested that there may be  
some compat libraries missing but I did not find an obvious one  
missing.
And thats right, some links in /lib64 were broken while I created  
the DomU image files from my Dom0 some months ago.

I should never trust rpm -qa without checking file existence ;-)


ahh I see, so the No such file or directory refers to /lib64/ 
ld64.so.1 which is the interpreter for the dynamic executable?

  $ objdump -s -j .interp hellobit.64




___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel