search for: 047on_crash

...ed some light on this as to how I can move forward in debugging this issue? Thanks, Aravindh Puthiyaparambil Xen Development Team Unisys [2006-05-01 15:25:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:182) XendDomainInfo.create([\047vm\047, [\047name\047, \047Mini-OS\047], [\047memory\047, 32], [\047on_crash\047, \047destroy\047], [\047vcpus\047, 1], [\047image\047, [\047linux\047, [\047kernel\047, \047/root/xen/xen-unstable.minios/extras/mini-os/mini-os.elf\047]]]]) [2006-05-01 15:25:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:288) parseConfig: config is [\047vm\047, [\047name\047, \047Mini-OS\047],...

...04-20 18:24:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335) XendDomainInfo.destroyDomain(27) [2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:178) XendDomainInfo.create([\047vm\047, [\047name\047, \047test-xen\047], [\047memory\047, 1024], [\047on_powerof 047, \047restart\047], [\047on_crash\047, \047restart\047], [\047vcpus\047, 2], [\047image\047, [\047linux\047, [\047kernel\047, \047/boot/xen-kernels/vmlinuz-2.6.16-20060420.3-xen0-s .2.3.4:192.168.5.15:255.255.255.0::eth0:off\047], [\047root\047, \047/dev/sda1 ro\047]]], [\047device\047, [\047vbd\047, [\047uname\047, \047phy:helene5...

...04-20 18:24:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335) XendDomainInfo.destroyDomain(27) [2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:178) XendDomainInfo.create([\047vm\047, [\047name\047, \047test-xen\047], [\047memory\047, 1024], [\047on_powerof 047, \047restart\047], [\047on_crash\047, \047restart\047], [\047vcpus\047, 2], [\047image\047, [\047linux\047, [\047kernel\047, \047/boot/xen-kernels/vmlinuz-2.6.16-20060420.3-xen0-s .2.3.4:192.168.5.15:255.255.255.0::eth0:off\047], [\047root\047, \047/dev/sda1 ro\047]]], [\047device\047, [\047vbd\047, [\047uname\047, \047phy:helene5...

...04 al:0 bm:640 lo:0 pe:0 ua:0 ap:0 oos:0 xm log: [2008-08-05 16:38:08 5979] DEBUG (XendDomainInfo:84) XendDomainInfo.create([\047vm\047, [\047name\047, \047dns1\047], [\047memory\047, 2048], [\047maxmem\047, 2048], [\047on_poweroff\047, \047destroy\047], [\047on_reboot\047, \047restart\047], [\047on_crash\047, \047restart\047], [\047vcpus\047, 2], [\047on_xend_start\047, \047ignore\047], [\047on_xend_stop\047, \047ignore\047], [\047uuid\047, \04753299e20-a828-a53a-53b8-88cfb9aa91f9\047], [\047image\047, [\047hvm\047, [\047kernel\047, \047/usr/lib/xen/boot/hvmloader\047], [\047device_model\047, \047/...

...], [\047device\047, [\047vbd\047, [\047uname\047, \047file:/root/xen/domains/joltpg1/swap.img\047], [\047dev\047, \047sda2\047], [\047mode\047, \047w\047]]]] [2006-04-28 12:35:40 xend.XendDomainInfo] DEBUG (XendDomainInfo:380) parseConfig: result is {\047ssidref\047: None, \047uuid\047: None, \047on_crash\047: None, \047on_reboot\047: None, \047image\047: [\047linux\047, [\047kernel\047, \047/boot/vmlinuz-2.6.16-xen\047], [\047ip\047, \047:1.2.3.4::::eth0:dhcp\047], [\047root\047, \047/dev/sda1 ro\047]], \047on_poweroff\047: None, \047cpus\047: None, \047name\047: \047joltpg1\047, \047backend\04...

...47Pool-0\047, \047shadow_memory\047: \0470\047, \047uuid\047: \047c2228027-a311-f5f2-3955-09f60a839f6e\047, \047on_reboot\047: \047restart\047, \047start_time\047: \0471345800143.27\047, \047on_poweroff\047: \047destroy\047, \047bootloader_args\047: \047\047, \047on_xend_start\047: \047ignore\047, \047on_crash\047: \047restart\047, \047xend/restart_count\047: \0470\047, \047vcpus\047: \0471\047, \047vcpu_avail\047: \0471\047, \047bootloader\047: \047\047, \047image\047: "(linux (kernel /boot/vmlinuz-2.6.32.57-2.el6xen.x86_64) (args \047root=/dev/hda2 ro \047) (superpages 0) (videoram 4) (pci ()) (no...

...7ignore\047, \047shadow_memory\047: \04710\047, \047uuid\047: \047096b961c-ca8d-4b8a-cf83-06ddaeba5bfc\047, \047on_reboot\047: \047restart\047, \047start_time\047: \0471279812698.25\047, \047on_poweroff\047: \047destroy\047, \047bootloader_args\047: \047\047, \047on_xend_start\047: \047ignore\047, \047on_crash\047: \047restart\047, \047xend/restart_count\047: \0470\047, \047vcpus\047: \0472\047, \047vcpu_avail\047: \0473\047, \047bootloader\047: \047\047, \047image\047: \047(hvm (kernel ) (hpet 0) (stdvga 0) (vnclisten 0.0.0.0) (loader /usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1) (boot c) (rtc...

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.

Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.