Displaying 11 results from an estimated 11 matches for "047uuid".
2008 Aug 05
2
Centos 5.2 using LVM -> DRBD 0.82 -> Xen Problems
...47, [\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/usr/lib64/xen/bin/qemu-dm\047],
[\047pae\047, 1], [\047vcpus\047, 2], [\047boot\047, \047d\047],
[\047fda\047, \047\047], [\047fdb\047...
2010 Jul 22
1
HVM domain can not boot up with Qcow incremental image
...-22 23:31:38 4609] DEBUG (image:801) apic = 1
[2010-07-22 23:31:38 4609] INFO (XendDomainInfo:1900) createDevice: vfb : {\047vncunused\047: 1, \047other_config\047: {\047vncunused\047: 1, \047vncpasswd\047: \047XXXXXXXX\047, \047vnclisten\047: \0470.0.0.0\047, \047type\047: \047vnc\047}, \047uuid\047: \047630a1ece-7bc1-91d8-3ba8-c41420c80b36\047, \047vnclisten\047: \0470.0.0.0\047, \047vncpasswd\047: \047XXXXXXXX\047, \047type\047: \047vnc\047}
[2010-07-22 23:31:38 4609] DEBUG (DevController:122) DevController: writing {\047state\047: \0471\047, \047backend-id\047: \0470\047, \047backend\04...
2012 Aug 24
1
Problems with create VM
...20120305 (Red Hat 4.4.6-4) (GCC)
cc_compile_by : mockbuild
cc_compile_domain : crc.id.au
cc_compile_date : Sat Aug 11 15:08:42 EST 2012
xend_config_format : 4
[root@localhost oracleteste]#
xm log
[2012-08-24 05:22:23 2831] INFO (XendDomainInfo:2357) createDevice: vbd : {\047uuid\047: \0476a97d455-5ff4-7dc3-7f18-2fb8658f80e0\047, \047bootable\047: 1, \047driver\047: \047paravirtualised\047, \047dev\047: \047hda2\047, \047uname\047: \047file:/vms/oracleteste/vmdisk0\047, \047mode\047: \047w\047}
[2012-08-24 05:22:23 2831] DEBUG (DevController:95) DevController: writing {\047...
2006 May 02
0
Mini-OS and Xend issue
...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:387)
parseConfig: result is {\047uuid\047: None, \047on_crash\047:
\047destroy\047, \047on_reboot\047: None, \047image\047: [\047linux\047,
[\047kernel\047,
\047/root/xen/xen-unstable.minios/extras/mini-os/mini-os.elf\047]],
\047on_poweroff\047: None, \047cpus\047: None, \047name\047:
\047Mini-OS\047, \047backend\047: [], \047vcpus\047...
2010 Jan 28
15
2.6.31.6 pv_ops can''t boot pv_ops DomU kernel
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
2010 Jan 28
15
2.6.31.6 pv_ops can''t boot pv_ops DomU kernel
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
2006 Apr 28
0
Can''t connect to domain
...mode\047, \047w\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: \047jo...
2006 Apr 20
2
Error: (28, ''No space left on device, while writing /vm/ba5fda47-f44a-2f44-b164-d2b1290d0d60/image/ostype : linux'')
...[\047uname\047, \047phy:helene74g/test-xenU-swap\047], [\047dev\047, \047sda2\047], [\047mode\047, \047w\047]]], [\047device\04
nbr0\047], [\047mac\047, \04700:0c:8d:00:0a:08\047]]]]
[2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:380) parseConfig: result is {\047ssidref\047: None, \047uuid\047: None, \047on_crash\047: \047restart\047, \047on_reboo
\047linux\047, [\047kernel\047, \047/boot/xen-kernels/vmlinuz-2.6.16-20060420.3-xen0-smp\047], [\047ip\047, \047192.168.5.47:1.2.3.4:192.168.5.15:255.255.255.0::eth0:off\047], [\047ro
oweroff\047: \047destroy\047, \047cpus\047: None, \047na...
2006 Apr 20
2
Error: (28, ''No space left on device, while writing /vm/ba5fda47-f44a-2f44-b164-d2b1290d0d60/image/ostype : linux'')
...[\047uname\047, \047phy:helene74g/test-xenU-swap\047], [\047dev\047, \047sda2\047], [\047mode\047, \047w\047]]], [\047device\04
nbr0\047], [\047mac\047, \04700:0c:8d:00:0a:08\047]]]]
[2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:380) parseConfig: result is {\047ssidref\047: None, \047uuid\047: None, \047on_crash\047: \047restart\047, \047on_reboo
\047linux\047, [\047kernel\047, \047/boot/xen-kernels/vmlinuz-2.6.16-20060420.3-xen0-smp\047], [\047ip\047, \047192.168.5.47:1.2.3.4:192.168.5.15:255.255.255.0::eth0:off\047], [\047ro
oweroff\047: \047destroy\047, \047cpus\047: None, \047na...
2010 Apr 08
23
Xen 4.0 on gentoo hotplug scripts problem?
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.
2010 Apr 08
23
Xen 4.0 on gentoo hotplug scripts problem?
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.