Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid

[Andrew Eross <eross@xxxxxxxxxxxx>]

Hi Ian,

Yep, confirmed, exact same images as you:

8525c3e8d6131ae462ba85b935a70bae  vmlinuz

f1f36dbfe47ebda085f41394dd079d09  initrd.gz

And I tried a very similar config:

name      = "ubuntu-calendar-test"

memory    = 1024

disk      = ['phy:/dev/mapper/center-calendar,xvda,w']

vif = [ 'mac=00:16:31:55:1c:82' ]

kernel    = "/root/ubuntu1204/vmlinuz"

ramdisk   = "/root/ubuntu1204/initrd.gz"

vcpus     = 2

>

on_crash  = 'destroy'

Unfortunately still not able to launch this VM, very strange!

xl create /etc/xen/ubuntu-calendar-test.cfg -c

#

Parsing config from /etc/xen/ubuntu-calendar-test.cfg

Daemon running with PID 28828

xenconsole: Could not read tty from store: No such file or directory

libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 2

#

cat /var/log/xen/xl-ubuntu-calendar-test.log

#

Waiting for domain ubuntu-calendar-test (domid 2) to die [pid 27391]

Domain 2 has shut down, reason code 3 0x3

Action for shutdown reason code 3 is destroy

Domain 2 needs to be cleaned up: destroying the domain

Done. Exiting now

#

I'm glad I can create VMs with "xen-create-image", but still this is strange... any possible other ideas?

Thanks much,

Andrew

On Tue, Feb 19, 2013 at 10:41 AM, Ian Murray <murrayie@xxxxxxxxxxx> wrote:

>Hi Ian,
>
>
>Thanks for the feedback -

No problem.

>
>
>I'm still a little wary that perhaps there's a bug in xl since the netboot image should've worked I think, but happy that this method does work.
>
>

I've just tried it again with 12.04.2 xen boot images and all went well. Here is my config file...

name      = "ubuntu-calendar-test"
memory    = 1024
disk      = ['phy:/dev/VG1/ubuntu-calendar-test,xvda,w' ]
vif = [ 'mac=00:16:31:55:1c:82' ]
kernel    = "/root/xen/ubuntu1204/vmlinuz"
ramdisk   = "/root/xen/ubuntu1204/initrd.gz"
vcpus     = 2
> on_crash  = 'destroy'


Are you sure there is no problem with your images? Here is are md5 hashes for the two files I used (12.04.2, 32bit as far as I remember)...

f1f36dbfe47ebda085f41394dd079d09  initrd.gz
8525c3e8d6131ae462ba85b935a70bae  vmlinuz

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users