search for: 047vm

...ith "domains_lock" happening somewhere? Could someone shed 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...

...p on the web with this other than ''this must be a bug'' from Nov 2005 - just wondered if anyone had more timely pearls of wisdom to impart? ;) The interesting part of xm log reports... [2006-04-28 12:35:40 xend.XendDomainInfo] DEBUG (XendDomainInfo:178) XendDomainInfo.create([\047vm\047, [\047name\047, \047joltpg1\047], [\047memory\047, 2048], [\047vcpus\047, 1], [\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]]], [\047device\047, [\047vbd\047, [\047uname\04...

...[2006-04-20 18:24:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327) XendDomainInfo.destroy: domid=27 [2006-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::e...

...[2006-04-20 18:24:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327) XendDomainInfo.destroy: domid=27 [2006-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::e...

...eba7d2eb4 build by root@mrhappy.whatever.com, 2008-08-05 14:04:25 0: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r--- ns:10485404 nr:0 dw:0 dr:10485404 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],...

...39; ]device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' boot='c' sdl=1 vnc=0 stdvga=0 serial='pty' usb=1 usbdevice='mouse' usbdevice='tablet' The following is xend log:[2010-07-22 23:31:38 4609] DEBUG (XendDomainInfo:89) XendDomainInfo.create([\047vm\047, [\047name\047, \047winXP\047], [\047memory\047, 1024], [\047vcpus\047, 2], [\047on_xend_start\047, \047ignore\047], [\047on_xend_stop\047, \047ignore\047], [\047image\047, [\047hvm\047, [\047kernel\047, \047/usr/lib/xen/boot/hvmloader\047], [\047device_model\047, \047/usr/lib64/xen/bin/qemu-dm...

...eteste\047} [2012-08-24 05:22:23 2831] DEBUG (XendDomainInfo:1794) Storing domain details: {\047console/ring-ref\047: \0471505169\047, \047image/entry\047: \04718446744071586935296\047, \047console/port\047: \0472\047, \047store/ring-ref\047: \0471505170\047, \047image/loader\047: \047generic\047, \047vm\047: \047/vm/c2228027-a311-f5f2-3955-09f60a839f6e\047, \047control/platform-feature-multiprocessor-suspend\047: \0471\047, \047image/hv-start-low\047: \04718446603336221196288\047, \047image/guest-os\047: \047linux\047, \047image/virt-base\047: \04718446744071562067968\047, \047memory/target\047: \...

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.