Xen4.7 unable to get domain type for domid

Xen4.7 unable to get domain type for domid

[soapcn]

Hi,

I keep getting this error about not being able to get domain type when I 
try to create a domU.
Xen-4.7, Ubuntu 12.04

$xl info

release                : 3.13.0-32-generic
version                : #57~xxxx-Ubuntu SMP Tue Jul 15 03:51:20 UTC 2014
machine                : x86_64
nr_cpus                : 8
max_cpu_id             : 15
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 1995
hw_caps                : 
bfebfbff:28100800:00000000:00003f00:15bae3bf:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 8169
free_memory            : 127
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims     : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 7
xen_extra              : -unstable
xen_version            : 4.7-unstable
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Wed Sep 16 14:16:09 2015 +0800 git:4600d75
xen_commandline        : placeholder
cc_compiler            : gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
cc_compile_by          : root
cc_compile_domain      :
cc_compile_date        : Sat Sep 26 17:37:35 EDT 2015
xend_config_format     : 4

$xl list
Name                                        ID   Mem VCPUs State    Time(s)
Domain-0                                     0  7947     8 r-----      79.6

$xl -vv create -c ubuntuImgNetBoot.cfg
Parsing config from ubuntuImgNetBoot.cfg
domainbuilder: detail: xc_dom_allocate: cmdline="(null)", features="(null)"
domainbuilder: detail: xc_dom_kernel_file: 
filename="/var/lib/xen/images/ubuntu-netboot/vmlinuz"
domainbuilder: detail: xc_dom_malloc_filemap    : 4849 kB
domainbuilder: detail: xc_dom_ramdisk_file: 
filename="/var/lib/xen/images/ubuntu-netboot/initrd.gz"
domainbuilder: detail: xc_dom_malloc_filemap    : 30178 kB
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.7, caps 
xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary 
loader ...
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ...
domainbuilder: detail: xc_dom_malloc            : 18254 kB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x4b34e6 -> 0x11d3aa0
domainbuilder: detail: loader probe OK
xc: detail: elf_parse_binary: phdr: paddr=0x1000000 memsz=0xad5000
xc: detail: elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xe50e0
xc: detail: elf_parse_binary: phdr: paddr=0x1ce6000 memsz=0x14480
xc: detail: elf_parse_binary: phdr: paddr=0x1cfb000 memsz=0x364000
xc: detail: elf_parse_binary: memory: 0x1000000 -> 0x205f000
xc: detail: elf_xen_parse_note: GUEST_OS = "linux"
xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6"
xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0"
xc: detail: elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
xc: detail: elf_xen_parse_note: ENTRY = 0xffffffff81cfb200
xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
xc: detail: elf_xen_parse_note: FEATURES = 
"!writable_page_tables|pae_pgdir_above_4gb"
xc: detail: elf_xen_parse_note: PAE_MODE = "yes"
xc: detail: elf_xen_parse_note: LOADER = "generic"
xc: detail: elf_xen_parse_note: unknown xen elf note (0xd)
xc: detail: elf_xen_parse_note: SUSPEND_CANCEL = 0x1
xc: detail: elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0
xc: detail: elf_xen_addr_calc_check: addresses:
xc: detail:     virt_base        = 0xffffffff80000000
xc: detail:     elf_paddr_offset = 0x0
xc: detail:     virt_offset      = 0xffffffff80000000
xc: detail:     virt_kstart      = 0xffffffff81000000
xc: detail:     virt_kend        = 0xffffffff8205f000
xc: detail:     virt_entry       = 0xffffffff81cfb200
xc: detail:     p2m_base         = 0xffffffffffffffff
domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 
0xffffffff81000000 -> 0xffffffff8205f000
domainbuilder: detail: xc_dom_mem_init: mem 512 MB, pages 0x20000 pages, 
4k each
domainbuilder: detail: xc_dom_mem_init: 0x20000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64
domainbuilder: detail: xc_dom_malloc            : 1024 kB
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 
0xffffffff81000000 -> 0xffffffff8205f000  (pfn 0x1000 + 0x105f pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
0x1000+0x105f at 0x7f2c946a4000
xc: detail: elf_load_binary: phdr 0 at 0x7f2c946a4000 -> 0x7f2c95179000
xc: detail: elf_load_binary: phdr 1 at 0x7f2c952a4000 -> 0x7f2c953890e0
xc: detail: elf_load_binary: phdr 2 at 0x7f2c9538a000 -> 0x7f2c9539e480
xc: detail: elf_load_binary: phdr 3 at 0x7f2c9539f000 -> 0x7f2c95477000
domainbuilder: detail: xc_dom_alloc_segment:   ramdisk      : 
0xffffffff8205f000 -> 0xffffffff86b0a000  (pfn 0x205f + 0x4aab pages)
domainbuilder: detail: xc_dom_malloc            : 448 kB
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
0x205f+0x4aab at 0x7f2c8fbf9000
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x1d78b44 -> 0x4aaa810
domainbuilder: detail: xc_dom_alloc_segment:   phys2mach    : 
0xffffffff86b0a000 -> 0xffffffff86c0a000  (pfn 0x6b0a + 0x100 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
0x6b0a+0x100 at 0x7f2c8faf9000
domainbuilder: detail: xc_dom_alloc_page   :   start info   : 
0xffffffff86c0a000 (pfn 0x6c0a)
domainbuilder: detail: xc_dom_alloc_page   :   xenstore     : 
0xffffffff86c0b000 (pfn 0x6c0b)
domainbuilder: detail: xc_dom_alloc_page   :   console      : 
0xffffffff86c0c000 (pfn 0x6c0c)
domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 
0xffff000000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 
0xffffff8000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 
0xffffffff80000000 -> 0xffffffffbfffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 
0xffffffff80000000 -> 0xffffffff86ffffff, 56 table(s)
domainbuilder: detail: xc_dom_alloc_segment:   page tables  : 
0xffffffff86c0d000 -> 0xffffffff86c48000  (pfn 0x6c0d + 0x3b pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
0x6c0d+0x3b at 0x7f2c9acaa000
domainbuilder: detail: xc_dom_alloc_page   :   boot stack   : 
0xffffffff86c48000 (pfn 0x6c48)
domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 
0xffffffff86c49000
domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 
0xffffffff87000000
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: arch_setup_bootearly: doing nothing
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
xen-3.0-x86_64 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
xen-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
hvm-3.0-x86_32
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
hvm-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
hvm-3.0-x86_64
domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x20000
domainbuilder: detail: clear_page: pfn 0x6c0c, mfn 0x12c40c
domainbuilder: detail: clear_page: pfn 0x6c0b, mfn 0x12c40b
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
0x6c0a+0x1 at 0x7f2c9ae6c000
domainbuilder: detail: start_info_x86_64: called
domainbuilder: detail: setup_hypercall_page: vaddr=0xffffffff81001000 
pfn=0x1001
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail:    allocated
domainbuilder: detail:       malloc             : 19835 kB
domainbuilder: detail:       anon mmap          : 0 bytes
domainbuilder: detail:    mapped
domainbuilder: detail:       file mmap          : 34 MB
domainbuilder: detail:       domU mmap          : 92 MB
domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 
0xb98ad
domainbuilder: detail: shared_info_x86_64: called
domainbuilder: detail: vcpu_x86_64: called
domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x6c0d mfn 0x12c40d
domainbuilder: detail: launch_vm: called, ctxt=0x7f2c9ae6d004
domainbuilder: detail: xc_dom_release: called
libxl: error: libxl_dom.c:37:libxl__domain_type: unable to get domain 
type for domid=5
xl: unable to exec console client: No such file or directory
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console 
child [3755] exited with error status 1



#contents of the cfg
name = "ubuntu"
memory = 512
vcpus = 2
disk = ['file:/home/precise/vmdisk/mydisk.img,xvda,w']
vif = ['bridge=xenbr0']
kernel="/var/lib/xen/images/ubuntu-netboot/vmlinuz"
ramdisk="/var/lib/xen/images/ubuntu-netboot/initrd.gz"
extra = "debian-installer/exit/always_halt=true console=hvc0"

I downloaded netboot from archive.ubuntu.com

$dmesg | grep xen
[    3.041134] xen: PV spinlocks enabled
[    3.117594] xen: sci override: global_irq=9 trigger=0 polarity=0
[    3.117597] xen: registering gsi 9 triggering 0 polarity 0
[    3.117610] xen: --> pirq=9 -> irq=9 (gsi=9)
[    3.117616] xen: acpi sci 9
[    3.117621] xen: --> pirq=1 -> irq=1 (gsi=1)
[    3.117625] xen: --> pirq=2 -> irq=2 (gsi=2)
[    3.117629] xen: --> pirq=3 -> irq=3 (gsi=3)
[    3.117633] xen: --> pirq=4 -> irq=4 (gsi=4)
[    3.117637] xen: --> pirq=5 -> irq=5 (gsi=5)
[    3.117640] xen: --> pirq=6 -> irq=6 (gsi=6)
[    3.117644] xen: --> pirq=7 -> irq=7 (gsi=7)
[    3.117648] xen: --> pirq=8 -> irq=8 (gsi=8)
[    3.117652] xen: --> pirq=10 -> irq=10 (gsi=10)
[    3.117658] xen: --> pirq=11 -> irq=11 (gsi=11)
[    3.117662] xen: --> pirq=12 -> irq=12 (gsi=12)
[    3.117666] xen: --> pirq=13 -> irq=13 (gsi=13)
[    3.117669] xen: --> pirq=14 -> irq=14 (gsi=14)
[    3.117673] xen: --> pirq=15 -> irq=15 (gsi=15)
[    3.333420] xen:grant_table: Grant tables using version 2 layout
[    3.428981] xen:balloon: Initialising balloon driver
[    3.429825] xen_balloon: Initialising balloon driver
[    3.437183] Switched to clocksource xen
[    3.443052] xen: registering gsi 13 triggering 1 polarity 0
[    3.443164] xen: registering gsi 8 triggering 1 polarity 0
[    3.443313] xen: registering gsi 12 triggering 1 polarity 0
[    3.443359] xen: registering gsi 1 triggering 1 polarity 0
[    3.455858] xen: registering gsi 16 triggering 0 polarity 1
[    3.455875] xen: --> pirq=16 -> irq=16 (gsi=16)
[    3.581412] xen: registering gsi 23 triggering 0 polarity 1
[    3.581424] xen: --> pirq=23 -> irq=23 (gsi=23)
[    3.709693] xen: registering gsi 19 triggering 0 polarity 1
[    3.709715] xen: --> pirq=19 -> irq=19 (gsi=19)
[    3.709767] xen: registering gsi 19 triggering 0 polarity 1
[    3.804009] xen: registering gsi 16 triggering 0 polarity 1
[    3.804248] xen: registering gsi 16 triggering 0 polarity 1
[    3.804449] xen: registering gsi 17 triggering 0 polarity 1
[    3.804460] xen: --> pirq=17 -> irq=17 (gsi=17)
[    3.804773] xen: registering gsi 17 triggering 0 polarity 1
[    3.835277] xen_acpi_processor: Uploading Xen processor PM info
[    3.841695] xen_netfront: Initialising Xen virtual ethernet driver
[    3.841794] xen: registering gsi 16 triggering 0 polarity 1
[    3.857580] xen: registering gsi 23 triggering 0 polarity 1
[    3.874257] xen: registering gsi 19 triggering 0 polarity 1
[    4.300437] xen: registering gsi 17 triggering 0 polarity 1
[    4.303817] xen: registering gsi 19 triggering 0 polarity 1
[    9.916823] xen: registering gsi 16 triggering 0 polarity 1
[   10.032353] xen: registering gsi 16 triggering 0 polarity 1
[   10.579305] xen: registering gsi 17 triggering 0 polarity 1
[   10.583604] xen: registering gsi 22 triggering 0 polarity 1
[   10.583616] xen: --> pirq=22 -> irq=22 (gsi=22)
[   11.601174] xen: registering gsi 17 triggering 0 polarity 1
[   13.687685] xen:xen_evtchn: Event-channel device installed
[   13.770140] xen_pciback: backend is vpci
[  299.456288] xenbr0: port 1(vif2.0) entered disabled state
[  299.456798] xenbr0: port 1(vif2.0) entered disabled state
[  317.234702] xenbr0: port 1(vif3.0) entered disabled state
[  317.235345] xenbr0: port 1(vif3.0) entered disabled state
[  331.480594] xenbr0: port 1(vif4.0) entered disabled state
[  331.481661] xenbr0: port 1(vif4.0) entered disabled state
[  417.910943] xenbr0: port 1(vif5.0) entered disabled state
[  417.911603] xenbr0: port 1(vif5.0) entered disabled state


$ifconfig
xenbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
           inet addr:192.168.2.1  Bcast:192.168.2.255 Mask:255.255.255.0
           inet6 addr: fe80::3064:6dff:fe54:76a7/64 Scope:Link
           UP BROADCAST MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:0 (0.0 B)  TX bytes:18227 (18.2 KB)

$vim /etc/network/interfaces
auto lo
iface lo inet loopback
auto xenbr0
iface xenbr0 inet static
address 192.168.2.1
netmask 255.255.255.0
broadcast 192.168.2.255

Tianyang

Re: Xen4.7 unable to get domain type for domid

[Wei Liu]

On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote:
[...]
> domainbuilder: detail: shared_info_x86_64: called
> domainbuilder: detail: vcpu_x86_64: called
> domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x6c0d mfn 0x12c40d
> domainbuilder: detail: launch_vm: called, ctxt=0x7f2c9ae6d004
> domainbuilder: detail: xc_dom_release: called
> libxl: error: libxl_dom.c:37:libxl__domain_type: unable to get domain type
> for domid=5
> xl: unable to exec console client: No such file or directory
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child
> [3755] exited with error status 1
> 

Couldn't think of a reason why this would fail. Is this a freshly
installed Xen? If not, is the previous installation purged?

Wei.

Re: Xen4.7 unable to get domain type for domid

[Andrew Cooper]

On 29/09/15 13:54, Wei Liu wrote:
> On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote:
> [...]
>> domainbuilder: detail: shared_info_x86_64: called
>> domainbuilder: detail: vcpu_x86_64: called
>> domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x6c0d mfn 0x12c40d
>> domainbuilder: detail: launch_vm: called, ctxt=0x7f2c9ae6d004
>> domainbuilder: detail: xc_dom_release: called
>> libxl: error: libxl_dom.c:37:libxl__domain_type: unable to get domain type
>> for domid=5
>> xl: unable to exec console client: No such file or directory
>> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child
>> [3755] exited with error status 1
>>
> Couldn't think of a reason why this would fail. Is this a freshly
> installed Xen? If not, is the previous installation purged?

It possibly means the domain has crashed very early after start.  Does
starting the domain paused (xl create -p) cause it to be constructed
correctly?

~Andrew

Re: Xen4.7 unable to get domain type for domid

[soapcn]

Andrew,

Yes, the domain is constructed and I can see it using xl list command. 
As soon as I unpaused it, it crashed again.

Tianyang

On 9/29/2015 9:00 AM, Andrew Cooper wrote:
> On 29/09/15 13:54, Wei Liu wrote:
>> On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote:
>> [...]
>>> domainbuilder: detail: shared_info_x86_64: called
>>> domainbuilder: detail: vcpu_x86_64: called
>>> domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x6c0d mfn 0x12c40d
>>> domainbuilder: detail: launch_vm: called, ctxt=0x7f2c9ae6d004
>>> domainbuilder: detail: xc_dom_release: called
>>> libxl: error: libxl_dom.c:37:libxl__domain_type: unable to get domain type
>>> for domid=5
>>> xl: unable to exec console client: No such file or directory
>>> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child
>>> [3755] exited with error status 1
>>>
>> Couldn't think of a reason why this would fail. Is this a freshly
>> installed Xen? If not, is the previous installation purged?
> It possibly means the domain has crashed very early after start.  Does
> starting the domain paused (xl create -p) cause it to be constructed
> correctly?
>
> ~Andrew

Re: Xen4.7 unable to get domain type for domid

[Wei Liu]

Please avoid top-posting.

On Tue, Sep 29, 2015 at 01:43:29PM -0400, soapcn wrote:
> Andrew,
> 
> Yes, the domain is constructed and I can see it using xl list command. As
> soon as I unpaused it, it crashed again.
> 

You then need to figure out why it crashed. Maybe "xl dmesg" can give you
some ideas what went wrong.

I don't think this is a bug in Xen. It's likely the kernel you used was
not able to boot as Xen *PV* guest.

Wei.

> Tianyang
> 
> On 9/29/2015 9:00 AM, Andrew Cooper wrote:
> >On 29/09/15 13:54, Wei Liu wrote:
> >>On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote:
> >>[...]
> >>>domainbuilder: detail: shared_info_x86_64: called
> >>>domainbuilder: detail: vcpu_x86_64: called
> >>>domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x6c0d mfn 0x12c40d
> >>>domainbuilder: detail: launch_vm: called, ctxt=0x7f2c9ae6d004
> >>>domainbuilder: detail: xc_dom_release: called
> >>>libxl: error: libxl_dom.c:37:libxl__domain_type: unable to get domain type
> >>>for domid=5
> >>>xl: unable to exec console client: No such file or directory
> >>>libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child
> >>>[3755] exited with error status 1
> >>>
> >>Couldn't think of a reason why this would fail. Is this a freshly
> >>installed Xen? If not, is the previous installation purged?
> >It possibly means the domain has crashed very early after start.  Does
> >starting the domain paused (xl create -p) cause it to be constructed
> >correctly?
> >
> >~Andrew

Re: Xen4.7 unable to get domain type for domid

[Andy Smith]

Hi Tianyang,

On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote:
> I keep getting this error about not being able to get domain type
> when I try to create a domU.
> Xen-4.7, Ubuntu 12.04

I also had this problem recently with regard to some Ubuntu 12.04
domUs, but on Xen 4.4.1, Debian jessie. These domUs worked fine on
earlier versions of Xen. I searched around a lot and found a few
other people with the same problem, but no answers.

In the end I discovered that these domUs were using the
linux-image-virtual kernel package instead of the more usual
linux-image-generic. I installed linux-image-generic and
uninstalled linux-image-virtual, and then the affected domUs would
boot.

I note also that I have some domUs with Ubuntu 12.04.01 using
linux-image-virtual and these are okay. So I assumed whatever
problem there was with that kernel was rectified by the time of the
12.04.01 release.

I hope that helps you.

Cheers,
Andy

Re: Xen4.7 unable to get domain type for domid

[Wei Liu]

Andy, please reply to all in the future. You only replied to
xen-deve@ but didn't CC Tianyang.

On Tue, Sep 29, 2015 at 10:06:53PM +0000, Andy Smith wrote:
> Hi Tianyang,
> 
> On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote:
> > I keep getting this error about not being able to get domain type
> > when I try to create a domU.
> > Xen-4.7, Ubuntu 12.04
> 
> I also had this problem recently with regard to some Ubuntu 12.04
> domUs, but on Xen 4.4.1, Debian jessie. These domUs worked fine on
> earlier versions of Xen. I searched around a lot and found a few
> other people with the same problem, but no answers.
> 
> In the end I discovered that these domUs were using the
> linux-image-virtual kernel package instead of the more usual
> linux-image-generic. I installed linux-image-generic and
> uninstalled linux-image-virtual, and then the affected domUs would
> boot.
> 
> I note also that I have some domUs with Ubuntu 12.04.01 using
> linux-image-virtual and these are okay. So I assumed whatever
> problem there was with that kernel was rectified by the time of the
> 12.04.01 release.
> 
> I hope that helps you.
> 
> Cheers,
> Andy
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: Xen4.7 unable to get domain type for domid

[Meng Xu]

[-- Attachment #1.1: Type: text/plain, Size: 1555 bytes --]

HI Andy,

2015-09-29 18:06 GMT-04:00 Andy Smith <andy@strugglers.net>:

> Hi Tianyang,
>
> On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote:
> > I keep getting this error about not being able to get domain type
> > when I try to create a domU.
> > Xen-4.7, Ubuntu 12.04
>
> I also had this problem recently with regard to some Ubuntu 12.04
> domUs, but on Xen 4.4.1, Debian jessie. These domUs worked fine on
> earlier versions of Xen. I searched around a lot and found a few
> other people with the same problem, but no answers.
>
> In the end I discovered that these domUs were using the
> linux-image-virtual kernel package instead of the more usual
> linux-image-generic. I installed linux-image-generic and
> uninstalled linux-image-virtual, and then the affected domUs would
> boot.
>
> I note also that I have some domUs with Ubuntu 12.04.01 using
> linux-image-virtual and these are okay. So I assumed whatever
> problem there was with that kernel was rectified by the time of the
> 12.04.01 release.
>
> I hope that helps you.
>

Thank you very much for your suggestions! ​


​After Tianyang changed the netboot image used to ​boot the domU, the error
disappears.
So it is likely that the linux-image provided by the ubuntu archive that he
uses is kind of broken.

It is glad to know that it is not Xen's problem. :-)

​Best regards,​

​Meng​



-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/

[-- Attachment #1.2: Type: text/html, Size: 2586 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Xen4.7 unable to get domain type for domid

[soapcn]

[-- Attachment #1.1: Type: text/plain, Size: 2222 bytes --]

On 9/29/2015 7:19 PM, Meng Xu wrote:
> HI Andy,
>
> 2015-09-29 18:06 GMT-04:00 Andy Smith <andy@strugglers.net
> <mailto:andy@strugglers.net>>:
>
>     Hi Tianyang,
>
>     On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote:
>     > I keep getting this error about not being able to get domain type
>     > when I try to create a domU.
>     > Xen-4.7, Ubuntu 12.04
>
>     I also had this problem recently with regard to some Ubuntu 12.04
>     domUs, but on Xen 4.4.1, Debian jessie. These domUs worked fine on
>     earlier versions of Xen. I searched around a lot and found a few
>     other people with the same problem, but no answers.
>
>     In the end I discovered that these domUs were using the
>     linux-image-virtual kernel package instead of the more usual
>     linux-image-generic. I installed linux-image-generic and
>     uninstalled linux-image-virtual, and then the affected domUs would
>     boot.
>
>     I note also that I have some domUs with Ubuntu 12.04.01 using
>     linux-image-virtual and these are okay. So I assumed whatever
>     problem there was with that kernel was rectified by the time of the
>     12.04.01 release.
>
>     I hope that helps you.
>
>
> Thank you very much for your suggestions! ​
>
> ​After Tianyang changed the netboot image used to ​boot the domU, the
> error disappears.
> So it is likely that the linux-image provided by the ubuntu archive
> that he uses is kind of broken.
>
> It is glad to know that it is not Xen's problem. :-)
>
> ​Best regards,​
>
> ​Meng​
>
>
>
> -----------
> Meng Xu
> PhD Student in Computer and Information Science
> University of Pennsylvania
> http://www.cis.upenn.edu/~mengxu/ <http://www.cis.upenn.edu/%7Emengxu/>
Andy,

I really appreciate for your suggestions. Like Meng said, there is
something wrong with the netboot image(precise) from archive.ubuntu.com.
I downloaded one couple weeks ago and it worked. It's the most recent
one that's broken and it's not Xen's problem.

For the record, I didn't do further testing but images from these two
won't work.

http://mirror.pnl.gov/ubuntu/...
http://archive.ubuntu.com/ubuntu/...


Tianyang


[-- Attachment #1.2: Type: text/html, Size: 4781 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Xen4.7 unable to get domain type for domid

[Andrew Cooper]

On 29/09/15 18:54, Wei Liu wrote:
> Please avoid top-posting.
>
> On Tue, Sep 29, 2015 at 01:43:29PM -0400, soapcn wrote:
>> Andrew,
>>
>> Yes, the domain is constructed and I can see it using xl list command. As
>> soon as I unpaused it, it crashed again.
>>
> You then need to figure out why it crashed. Maybe "xl dmesg" can give you
> some ideas what went wrong.
>
> I don't think this is a bug in Xen. It's likely the kernel you used was
> not able to boot as Xen *PV* guest.

Boot Xen with "loglvl=all guest_loglvl=all" and the domU with
"earlyprintk=xen xencons=hvc console=hvc0", and that will likely get
some kind of useful debugging visible in `xl dmesg`

~Andrew