Re: [Xen-users] System unusable (hangs) after xm create - xen 4

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Fri, May 14, 2010 at 03:01:59PM -0400, LDavis wrote:
> Hello
> 
> I have a production server, on which I had to install a new OS.  
> Unfortunately, xen is not willing to run any domUs!
> Any help would be most highly appreciated.
> 
> My problem is essentially that described in this post, to which there was 
> no answer at the time:
> <http://lists.xensource.com/archives/html/xen-devel/2009-06/msg01147.html>
> 
> Symptoms:
> When trying to xm create a previously functional (Xen 3.3 and 3.0) domU 
> (with appropriate kernel), the system appears to lock up solid.
> In fact, it still logs some things for a while.
> 
> Sometimes I can control-c out of the xm process, but the next command will 
> lock it up just as hard.
> Sometimes a ctrl-alt-del at the console is reported to the ssh session 
> from which I work, but in no case does a reboot actually happen, and a 
> hard reset is necessary to recover.
> 
> Environment:
> 
> Ubuntu 10.04 server
> Kernel: 2.6.32.12-xen-2-gba739f9 (custom compile with huge initramfs)
> Xen 4.0
> 
> This setup was developed based on instructions from here:
> <http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/>
> 
> Grub config block:
> 
> title           Xen 4.0 / Ubuntu 10.04 LTS, kernel 
> 2.6.32.12-xen-2-gba739f9
> root            (hd0,5)
> kernel /xen-4.0.0.gz

Have you tried limiting dom0 memory to, say, 512 MB or 1024 MB ? dom0_mem=1024M 
parameter for xen.gz.

http://wiki.xensource.com/xenwiki/XenBestPractices

-- Pasi

> module /vmlinuz-2.6.32.12-xen-2-gba739f9 root=/dev/mapper/main-root ro
> module /initrd.img-2.6.32.12-xen-2-gba739f9
> 
> domU config:
> 
> name = "[DOMUNAME]"
> kernel = "/etc/xen/boot/vmlinuz-2.6.24-23-xen"
> ramdisk = "/etc/xen/boot/initrd.img-2.6.24-23-xen"
> root = "/dev/sda1 ro"
> memory = 200
> disk = [ "phy:/dev/mapper/virtuals-[DOMUNAME],sda1,w" ]
> hostname="[DOMUNAME].[FQDN]"
> vnc=0
> nographic=1
> serial='pty'
> monitor=0
> 
> I have placed a full dom0 dmesg, lshw (--disable dmi), and xend.log here:
> http://tinyurl.com/266osb3//dmesg.txt
> http://tinyurl.com/266osb3//xend.log.txt
> http://tinyurl.com/266osb3//lshw.html
> 
> The probably relevant portion of xend.log is:
> 
> [2010-05-14 13:10:57 1196] INFO (SrvDaemon:336) Xend changeset: 
> unavailable.
> [.]
> [2010-05-14 13:10:58 1196] DEBUG (XendDomain:398) number of vcpus to use 
> is 0
> [2010-05-14 13:10:58 1196] DEBUG (XendDomainInfo:1891) 
> XendDomainInfo.handleShutdownWatch
> [2010-05-14 13:10:58 1196] WARNING (XendAPI:705) API call: VBD.set_device 
> not found
> [2010-05-14 13:10:58 1196] WARNING (XendAPI:705) API call: VBD.set_type 
> not found
> [2010-05-14 13:10:58 1196] WARNING (XendAPI:705) API call: 
> session.get_all_records not found
> [2010-05-14 13:10:58 1196] WARNING (XendAPI:705) API call: 
> event.get_record not
> found
> [2010-05-14 13:10:58 1196] WARNING (XendAPI:705) API call: event.get_all 
> not found
> [2010-05-14 13:10:58 1196] WARNING (XendAPI:705) API call: VIF.set_device 
> not found
> [2010-05-14 13:10:58 1196] WARNING (XendAPI:705) API call: VIF.set_MAC not 
> found[2010-05-14 13:10:58 1196] WARNING (XendAPI:705) API call: 
> VIF.set_MTU not found[2010-05-14 13:10:58 1196] WARNING (XendAPI:705) API 
> call: debug.get_all not found
> [2010-05-14 13:10:58 1196] INFO (XMLRPCServer:156) Opening Unix domain 
> socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has 
> been disabled for this server.
> [2010-05-14 13:10:58 1196] INFO (XMLRPCServer:156) Opening Unix domain 
> socket XML-RPC server on /var/run/xend/xmlrpc.sock.
> 
> Thanks
> 
> LDavis
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users