nesredin mahmud
2013-Jun-13 16:33 UTC
Re: DomU: piix:not 100% native mode: will probe irq later
Hello Wei, On Sun, Jun 9, 2013 at 1:26 PM, Wei Liu <wei.liu2@citrix.com> wrote:> On Sun, Jun 09, 2013 at 11:58:26AM +0200, nesredin mahmud wrote: > > Hey guys, > > > > I am posting this again....because i didnt get any replay. Please I am > > doing my thesis and I am stack installing a guest machine from Yocto, a > > unix like machine. It boots successfully on the same host without xen. > > > > Probably you need to state what''s different between a "Yocto" machine > and a normal Linux system? AIUI Yocto is a embedded Linux distribution > which doesn''t make much sense to me (or most Xen users) so that we are > really not able to help much here. > > Like you said, it is an embedded Linux distribution with 3.8 kernelversion currently working fine in similar host. I have that image and wana use it as a HVM guest machine. I am a newbie to xen, and I can post more information about it if needed.> > thank you again, > > > > Nas > > > > On Tue, Jun 4, 2013 at 5:37 PM, nesredin mahmud <nasmitlinux@gmail.com > >wrote: > > > > > hello everyone, > > > > > > I am experiencing DomU booting problem. It stacks some where when the > > > serial console tries to share IRQ (*serial: 8250/16550 driver, 4 ports, > > > IRQ sharing disabled*). But then a strange thing happens, once the DomU > > > hangup for a while, I restart the Host, then I find my DomU is already > > > booted successfully. However, if I reboot the DomU, it stacks on the > same > > > place. I really dont know what this means.... > > > > > It is also unclear to me what you''re trying to achieve. The description > above is confusing. If you''re trying to get a console for guest, should > you not use xenconsole instead of physical serial? Why would you need to > restart the host? Were you trying to pass through physical serial port > to guest? > > I am not using physical serial..that is the warning message when the guestboots it displays. In fact, I am using virt-manager to create the guest machine, but it stacks some where before it completes booting. The guest machine works perfectly fine without xen like i said. I somehow rebooted the host while the guest machine was stack. Finally the guest machine was already booted successfully. And I could not explain why this is happening. I hope this gives you some insight towards the problem i am trying to explain. But like you said i will test it xenconsole only ..without virt-manager!! Best, //Nas> > Wei. > > > > > > > *root@swart-2:/home/swart# xm dmesg* > > > (XEN) Xen version 4.1.2 (Ubuntu 4.1.2-2ubuntu2.8) ( > > > stefan.bader@canonical.com) (gcc version 4.6.3 (Ubuntu/Linaro > > > 4.6.3-1ubuntu5) ) Mon Apr 29 19:04:55 UTC 2013 > > > (XEN) Bootloader: GRUB 1.99-21ubuntu3.9 > > > (XEN) Command line: placeholder dom0_max_vcpus=2 dom0_vcpus_pin > > > xencons=off vpmu > > > (XEN) Video information: > > > (XEN) VGA is text mode 80x25, font 8x16 > > > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > > > (XEN) Disc information: > > > (XEN) Found 1 MBR signatures > > > (XEN) Found 1 EDD information structures > > > (XEN) Xen-e820 RAM map: > > > (XEN) 0000000000000000 - 000000000009dc00 (usable) > > > (XEN) 000000000009dc00 - 00000000000a0000 (reserved) > > > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > > > (XEN) 0000000000100000 - 0000000020000000 (usable) > > > (XEN) 0000000020000000 - 0000000020200000 (reserved) > > > (XEN) 0000000020200000 - 0000000040004000 (usable) > > > (XEN) 0000000040004000 - 0000000040005000 (reserved) > > > (XEN) 0000000040005000 - 00000000d87b7000 (usable) > > > (XEN) 00000000d87b7000 - 00000000d8a2c000 (reserved) > > > (XEN) 00000000d8a2c000 - 00000000d8a3f000 (ACPI data) > > > (XEN) 00000000d8a3f000 - 00000000d8ac8000 (reserved) > > > (XEN) 00000000d8ac8000 - 00000000d8ad6000 (ACPI data) > > > (XEN) 00000000d8ad6000 - 00000000d8b61000 (usable) > > > (XEN) 00000000d8b61000 - 00000000d8c14000 (ACPI NVS) > > > (XEN) 00000000d8c14000 - 00000000d8fae000 (reserved) > > > (XEN) 00000000d8fae000 - 00000000d8faf000 (usable) > > > (XEN) 00000000d8faf000 - 00000000d8ff2000 (ACPI NVS) > > > (XEN) 00000000d8ff2000 - 00000000d9e1a000 (usable) > > > (XEN) 00000000d9e1a000 - 00000000d9ff2000 (reserved) > > > (XEN) 00000000d9ff2000 - 00000000da000000 (usable) > > > (XEN) 00000000db000000 - 00000000df200000 (reserved) > > > (XEN) 00000000f8000000 - 00000000fc000000 (reserved) > > > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > > > (XEN) 00000000fed00000 - 00000000fed04000 (reserved) > > > (XEN) 00000000fed1c000 - 00000000fed45000 (reserved) > > > (XEN) 00000000fed90000 - 00000000fed94000 (reserved) > > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > > > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > > > (XEN) 0000000100000000 - 000000011ee00000 (usable) > > > (XEN) ACPI: RSDP 000F9810, 0024 (r2 HPQOEM) > > > (XEN) ACPI: XSDT D8A2C088, 0094 (r1 HPQOEM SLIC-BPC 1072009 AMI > 10013) > > > (XEN) ACPI: FACP D8A36650, 010C (r5 HPQOEM SLIC-BPC 1072009 AMI > 10013) > > > (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer than ACPI > > > 2.0 version, truncating length 0x10C to 0xF4 [20070126] > > > (XEN) ACPI: DSDT D8A2C1B0, A49B (r2 HPQOEM SLIC-BPC 17 INTL > 20051117) > > > (XEN) ACPI: FACS D8C12080, 0040 > > > (XEN) ACPI: APIC D8A36760, 0072 (r3 HPQOEM SLIC-BPC 1072009 AMI > 10013) > > > (XEN) ACPI: FPDT D8A367D8, 0044 (r1 HPQOEM SLIC-BPC 1072009 AMI > 10013) > > > (XEN) ACPI: MCFG D8A36820, 003C (r1 HPQOEM SLIC-BPC 1072009 MSFT > 97) > > > (XEN) ACPI: HPET D8A36860, 0038 (r1 HPQOEM SLIC-BPC 1072009 AMI. > 5) > > > (XEN) ACPI: SSDT D8A36898, 036D (r1 SataRe SataTabl 1000 INTL > 20091112) > > > (XEN) ACPI: MSDM D8A36C08, 0055 (r3 HPQOEM SLIC-BPC 1072009 HPQ > 10013) > > > (XEN) ACPI: SSDT D8A36C60, 668F (r1 COMPAQ WMI 1 MSFT > 3000001) > > > (XEN) ACPI: SLIC D8A3D2F0, 0176 (r1 HPQOEM SLIC-BPC 1 > 0) > > > (XEN) ACPI: SSDT D8A3D468, 0968 (r1 PmRef Cpu0Ist 3000 INTL > 20051117) > > > (XEN) ACPI: SSDT D8A3DDD0, 0A92 (r1 PmRef CpuPm 3000 INTL > 20051117) > > > (XEN) ACPI: TCPA D8A3E868, 0032 (r2 APTIO4 NAPAASF 1 MSFT > 1000013) > > > (XEN) ACPI: DMAR D8A3E8A0, 00B8 (r1 INTEL SNB 1 INTL > 1) > > > (XEN) ACPI: ASF! D8A3E958, 00A5 (r32 INTEL HCG 1 TFSM > > > F4240) > > > (XEN) System RAM: 3970MB (4065364kB) > > > (XEN) Domain heap initialised > > > (XEN) ACPI: 32/64X FACS address mismatch in FADT - > > > d8c12080/0000000000000000, using 32 > > > (XEN) Processor #0 7:10 APIC version 21 > > > (XEN) Processor #2 7:10 APIC version 21 > > > (XEN) Processor #4 7:10 APIC version 21 > > > (XEN) Processor #6 7:10 APIC version 21 > > > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > > *(XEN) Table is not found!* > > > (XEN) Switched to APIC driver x2apic_cluster. > > > (XEN) Using scheduler: SMP Credit Scheduler (credit) > > > (XEN) Detected 2893.477 MHz processor. > > > (XEN) Initing memory sharing. > > > (XEN) Intel VT-d Snoop Control not enabled. > > > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > > > (XEN) Intel VT-d Queued Invalidation enabled. > > > (XEN) Intel VT-d Interrupt Remapping enabled. > > > (XEN) Intel VT-d Shared EPT tables not enabled. > > > (XEN) I/O virtualisation enabled > > > (XEN) - Dom0 mode: Relaxed > > > (XEN) Enabled directed EOI with ioapic_ack_old on! > > > (XEN) ENABLING IO-APIC IRQs > > > (XEN) -> Using old ACK method > > > (XEN) Platform timer is 14.318MHz HPET > > > (XEN) Allocated console ring of 16 KiB. > > > (XEN) VMX: Supported advanced features: > > > (XEN) - APIC MMIO access virtualisation > > > (XEN) - APIC TPR shadow > > > (XEN) - Extended Page Tables (EPT) > > > (XEN) - Virtual-Processor Identifiers (VPID) > > > (XEN) - Virtual NMI > > > (XEN) - MSR direct-access bitmap > > > (XEN) - Unrestricted Guest > > > (XEN) EPT supports 2MB super page. > > > (XEN) HVM: ASIDs enabled. > > > (XEN) HVM: VMX enabled > > > (XEN) HVM: Hardware Assisted Paging detected. > > > (XEN) Brought up 4 CPUs > > > (XEN) *** LOADING DOMAIN 0 *** > > > (XEN) Xen kernel: 64-bit, lsb, compat32 > > > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2353000 > > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > > (XEN) Dom0 alloc.: 0000000110000000->0000000114000000 (936161 pages > to > > > be allocated) > > > (XEN) Init. ramdisk: 000000011b2cb000->000000011edff800 > > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > > (XEN) Loaded kernel: ffffffff81000000->ffffffff82353000 > > > (XEN) Init. ramdisk: ffffffff82353000->ffffffff85e87800 > > > (XEN) Phys-Mach map: ffffffff85e88000->ffffffff865ea0b0 > > > (XEN) Start info: ffffffff865eb000->ffffffff865eb4b4 > > > (XEN) Page tables: ffffffff865ec000->ffffffff86623000 > > > (XEN) Boot stack: ffffffff86623000->ffffffff86624000 > > > (XEN) TOTAL: ffffffff80000000->ffffffff86800000 > > > (XEN) ENTRY ADDRESS: ffffffff81cf2210 > > > (XEN) Dom0 has maximum 2 VCPUs > > > (XEN) Scrubbing Free RAM: .done. > > > (XEN) Xen trace buffers: disabled > > > (XEN) Std. Loglevel: Errors and warnings > > > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > > > (XEN) Xen is relinquishing VGA console. > > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch > input > > > to Xen) > > > (XEN) Freed 216kB init memory. > > > (XEN) no cpu_id for acpi_id 5 > > > (XEN) no cpu_id for acpi_id 6 > > > (XEN) no cpu_id for acpi_id 7 > > > (XEN) no cpu_id for acpi_id 8 > > > *(XEN) physdev.c:162: dom0: wrong map_pirq type 3* > > > > > > > > > > ------------------------------------///----------------------------------------- > > > > > > *# virsh dumpxml hvm-1* > > > <domain type=''xen'' id=''4''> > > > <name>hvm-2</name> > > > <uuid>634e3f03-4855-8bb8-4e9e- > > > f28d4ce7671a</uuid> > > > <memory unit=''KiB''>524288</memory> > > > <currentMemory unit=''KiB''>524288</currentMemory> > > > <vcpu placement=''static''>1</vcpu> > > > <os> > > > <type>hvm</type> > > > <loader>/usr/lib/xen/boot/hvmloader</loader> > > > <kernel>/home/swart/yoctoimage/sandybayimages/bzImage</kernel> > > > <cmdline>root=/dev/hda ip=dhcp acpi=off apic=off</cmdline> > > > </os> > > > <features> > > > <acpi/> > > > <apic/> > > > <pae/> > > > </features> > > > <clock offset=''variable'' adjustment=''0'' basis=''utc''> > > > <timer name=''hpet'' present=''no''/> > > > </clock> > > > <on_poweroff>destroy</on_poweroff> > > > <on_reboot>restart</on_reboot> > > > <on_crash>restart</on_crash> > > > <devices> > > > <emulator>/usr/lib64/xen/bin/qemu-dm</emulator> > > > <disk type=''file'' device=''disk''> > > > <driver name=''file''/> > > > <source > > > > file=''/home/swart/yoctoimage/sandybayimages/core-image-minimal-sugarbay.hddimg''/> > > > <target dev=''hda'' bus=''ide''/> > > > </disk> > > > <interface type=''bridge''> > > > <mac address=''00:16:3e:6f:f9:72''/> > > > <source bridge=''xenbr0''/> > > > <script path=''/etc/xen/scripts/vif-bridge''/> > > > <target dev=''vif4.0''/> > > > <model type=''e1000''/> > > > </interface> > > > <serial type=''pty''> > > > <source path=''/dev/pts/0''/> > > > <target port=''0''/> > > > </serial> > > > <console type=''pty'' tty=''/dev/pts/0''> > > > <source path=''/dev/pts/0''/> > > > <target type=''serial'' port=''0''/> > > > </console> > > > <input type=''mouse'' bus=''ps2''/> > > > <graphics type=''vnc'' port=''5900'' autoport=''yes'' keymap=''en-us''/> > > > <sound model=''es1370''/> > > > </devices> > > > </domain> > > > ----------------------//---------------------------- > > > WHILE THE GUEST IS BOOTING.... > > > [image: Inline image 1] > > > HOST: Ubuntu-12.0.4 LTS > > > XEN: xen-hypervisor-4.1-amd64 > > > BIOS REVISION: 2.83 > > > > > > I highly appreciate your support, > > > > > > Thank you, > > > > > > //nas > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
nesredin mahmud
2013-Jun-14 10:32 UTC
Re: DomU: piix:not 100% native mode: will probe irq later
hello again, I did the same the procedure with xen-4.2.2, the guest machine booted successfully. But I wana do it on xen-4.1.2 because virt-manager seems to work very well in this version and also is default ubuntu distribution support. I hope am not pushing so hard...but i have reproduced similar problem on xen-4.1.2 from the guest machine and it seems a console problem. But i ve no clue what to do next. ============================THIS MY GUEST CONFIGURATION: kernel = "hvmloader" builder=''hvm'' memory = 128 name = "hvmtest" acpi=1 apic=1 pae=1 vif = [ ''bridge=xenbr0, model=e1000'' ] disk = [ ''file:/var/lib/libvirt/images/base_swart.hddimg,hda,w'' ] device_model = ''qemu_dm'' sdl=0 vnc=1 vncpasswd=0 stdvga=0 serial=''pty'' tsc_mode=0 =============================# xm create -c test.cfg Using config file "./test.cfg". Started domain hvmtest (id=11) SYSLINUX 4.06 2012-10-23 Copyright (C) 1994-2012 H. Peter Anvin et al boot: Loading /vmlinuz........ Loading /initrd..........ready. root@ubuntu-3:/etc/xen# xm create -c test.cfg Using config file "./test.cfg". Error: Device 768 (vbd) could not be connected. File /var/lib/libvirt/images/base_swart.hddimg is loopback-mounted through /dev/loop1, which is mounted in the privileged domain, and so cannot be mounted by a guest. root@ubuntu-3:/etc/xen# xm create -c test.cfg Using config file "./test.cfg". Started domain hvmtest (id=13) SYSLINUX 4.06 2012-10-23 Copyright (C) 1994-2012 H. Peter Anvin et al boot: Loading /vmlinuz........ Loading /initrd..........ready. Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 3.8.4-yocto-standard (swart@swart-2) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Fri May 31 20:43:39 CEST 2013 Command line: initrd=/initrd LABEL=boot root=/dev/ram0 console=tty1 console=ttyS0 BOOT_IMAGE=/vmlinuz e820: BIOS-provided physical RAM map: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved BIOS-e820: [mem 0x0000000000100000-0x0000000007ffffff] usable BIOS-e820: [mem 0x00000000fc000000-0x00000000ffffffff] reserved NX (Execute Disable) protection: active SMBIOS 2.4 present. No AGP bridge found e820: last_pfn = 0x8000 max_arch_pfn = 0x400000000 x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 found SMP MP-table at [mem 0x000fbc70-0x000fbc7f] mapped at [ffff8800000fbc70] init_memory_mapping: [mem 0x00000000-0x07ffffff] RAMDISK: [mem 0x078db000-0x07ffefff] ACPI: RSDP 00000000000ea020 00024 (v02 Xen) ACPI: XSDT 00000000fc0134b0 00034 (v01 Xen HVM 00000000 HVML 00000000) ACPI: FACP 00000000fc0132d0 000F4 (v04 Xen HVM 00000000 HVML 00000000) ACPI: DSDT 00000000fc003440 0FE05 (v02 Xen HVM 00000000 INTL 20100528) ACPI: FACS 00000000fc003400 00040 ACPI: APIC 00000000fc0133d0 000D8 (v02 Xen HVM 00000000 HVML 00000000) Zone ranges: DMA [mem 0x00010000-0x00ffffff] DMA32 [mem 0x01000000-0xffffffff] Normal empty Movable zone start for each node Early memory node ranges node 0: [mem 0x00010000-0x0009dfff] node 0: [mem 0x00100000-0x07ffffff] ACPI: PM-Timer IO Port: 0xb008 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] disabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x08] disabled) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x0a] disabled) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x0c] disabled) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x0e] disabled) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] disabled) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x12] disabled) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x14] disabled) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x16] disabled) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x18] disabled) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x1a] disabled) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x1c] disabled) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level) ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level) ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level) Using ACPI (MADT) for SMP configuration information smpboot: Allowing 15 CPUs, 14 hotplug CPUs e820: [mem 0x08000000-0xfbffffff] available for PCI devices setup_percpu: NR_CPUS:24 nr_cpumask_bits:24 nr_cpu_ids:15 nr_node_ids:1 PERCPU: Embedded 27 pages/cpu @ffff880007600000 s79104 r8192 d23296 u131072 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32136 Kernel command line: initrd=/initrd LABEL=boot root=/dev/ram0 console=tty1 console=ttyS0 BOOT_IMAGE=/vmlinuz PID hash table entries: 512 (order: 0, 4096 bytes) Dentry cache hash table entries: 16384 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) __ex_table already sorted, skipping sort Checking aperture... No AGP bridge found Memory: 104436k/131072k available (8001k kernel code, 456k absent, 26180k reserved, 5040k data, 780k init) SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=15, Nodes=1 Preemptible hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=24 to nr_cpu_ids=15. NR_IRQS:4352 nr_irqs:1208 16 Console: colour VGA+ 80x25 console [tty1] enabled console [ttyS0] enabled allocated 524288 bytes of page_cgroup please try ''cgroup_disable=memory'' option if you don''t want memory cgroups tsc: Fast TSC calibration using PIT tsc: Detected 2893.800 MHz processor Calibrating delay loop (skipped), value calculated using timer frequency.. 5787.60 BogoMIPS (lpj=2893800) pid_max: default: 32768 minimum: 301 Security Framework initialized Mount-cache hash table entries: 256 Initializing cgroup subsys debug Initializing cgroup subsys cpuacct Initializing cgroup subsys memory Initializing cgroup subsys devices Initializing cgroup subsys freezer Initializing cgroup subsys net_cls Initializing cgroup subsys blkio CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 mce: CPU supports 9 MCE banks Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0 Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32 tlb_flushall_shift: 1 ACPI: Core revision 20121018 ftrace: allocating 28415 entries in 111 pages Switched APIC routing to physical flat. ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0 smpboot: CPU0: Intel(R) Core(TM) i5-3470S CPU @ 2.90GHz (fam: 06, model: 3a, stepping: 09) Performance Events: unsupported p6 CPU model 58 no PMU driver, software events only. @the guest stacks over here......... i really appreciate any support either to explain me what is going on or give me an indication to what I should do. Bear in mind, the same configuration has worked in xen-4.2.2 xend/xm toolstack. thank you so much, Best, //Nas On Thu, Jun 13, 2013 at 6:33 PM, nesredin mahmud <nasmitlinux@gmail.com>wrote:> Hello Wei, > > > > On Sun, Jun 9, 2013 at 1:26 PM, Wei Liu <wei.liu2@citrix.com> wrote: > >> On Sun, Jun 09, 2013 at 11:58:26AM +0200, nesredin mahmud wrote: >> > Hey guys, >> > >> > I am posting this again....because i didnt get any replay. Please I am >> > doing my thesis and I am stack installing a guest machine from Yocto, a >> > unix like machine. It boots successfully on the same host without xen. >> > >> >> Probably you need to state what''s different between a "Yocto" machine >> and a normal Linux system? AIUI Yocto is a embedded Linux distribution >> which doesn''t make much sense to me (or most Xen users) so that we are >> really not able to help much here. >> >> Like you said, it is an embedded Linux distribution with 3.8 kernel > version currently working fine in similar host. I have that image and wana > use it as a HVM guest machine. I am a newbie to xen, and I can post more > information about it if needed. > >> > thank you again, >> > >> > Nas >> > >> > On Tue, Jun 4, 2013 at 5:37 PM, nesredin mahmud <nasmitlinux@gmail.com >> >wrote: >> > >> > > hello everyone, >> > > >> > > I am experiencing DomU booting problem. It stacks some where when the >> > > serial console tries to share IRQ (*serial: 8250/16550 driver, 4 >> ports, >> > > IRQ sharing disabled*). But then a strange thing happens, once the >> DomU >> > > hangup for a while, I restart the Host, then I find my DomU is already >> > > booted successfully. However, if I reboot the DomU, it stacks on the >> same >> > > place. I really dont know what this means.... >> > > >> >> It is also unclear to me what you''re trying to achieve. The description >> above is confusing. If you''re trying to get a console for guest, should >> you not use xenconsole instead of physical serial? Why would you need to >> restart the host? Were you trying to pass through physical serial port >> to guest? >> >> I am not using physical serial..that is the warning message when the > guest boots it displays. In fact, I am using virt-manager to create the > guest machine, but it stacks some where before it completes booting. The > guest machine works perfectly fine without xen like i said. > > I somehow rebooted the host while the guest machine was stack. Finally the > guest machine was already booted successfully. And I could not explain why > this is happening. > > I hope this gives you some insight towards the problem i am trying to > explain. But like you said i will test it xenconsole only ..without > virt-manager!! > > Best, > > //Nas > >> >> Wei. >> >> > > >> > > *root@swart-2:/home/swart# xm dmesg* >> > > (XEN) Xen version 4.1.2 (Ubuntu 4.1.2-2ubuntu2.8) ( >> > > stefan.bader@canonical.com) (gcc version 4.6.3 (Ubuntu/Linaro >> > > 4.6.3-1ubuntu5) ) Mon Apr 29 19:04:55 UTC 2013 >> > > (XEN) Bootloader: GRUB 1.99-21ubuntu3.9 >> > > (XEN) Command line: placeholder dom0_max_vcpus=2 dom0_vcpus_pin >> > > xencons=off vpmu >> > > (XEN) Video information: >> > > (XEN) VGA is text mode 80x25, font 8x16 >> > > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds >> > > (XEN) Disc information: >> > > (XEN) Found 1 MBR signatures >> > > (XEN) Found 1 EDD information structures >> > > (XEN) Xen-e820 RAM map: >> > > (XEN) 0000000000000000 - 000000000009dc00 (usable) >> > > (XEN) 000000000009dc00 - 00000000000a0000 (reserved) >> > > (XEN) 00000000000e0000 - 0000000000100000 (reserved) >> > > (XEN) 0000000000100000 - 0000000020000000 (usable) >> > > (XEN) 0000000020000000 - 0000000020200000 (reserved) >> > > (XEN) 0000000020200000 - 0000000040004000 (usable) >> > > (XEN) 0000000040004000 - 0000000040005000 (reserved) >> > > (XEN) 0000000040005000 - 00000000d87b7000 (usable) >> > > (XEN) 00000000d87b7000 - 00000000d8a2c000 (reserved) >> > > (XEN) 00000000d8a2c000 - 00000000d8a3f000 (ACPI data) >> > > (XEN) 00000000d8a3f000 - 00000000d8ac8000 (reserved) >> > > (XEN) 00000000d8ac8000 - 00000000d8ad6000 (ACPI data) >> > > (XEN) 00000000d8ad6000 - 00000000d8b61000 (usable) >> > > (XEN) 00000000d8b61000 - 00000000d8c14000 (ACPI NVS) >> > > (XEN) 00000000d8c14000 - 00000000d8fae000 (reserved) >> > > (XEN) 00000000d8fae000 - 00000000d8faf000 (usable) >> > > (XEN) 00000000d8faf000 - 00000000d8ff2000 (ACPI NVS) >> > > (XEN) 00000000d8ff2000 - 00000000d9e1a000 (usable) >> > > (XEN) 00000000d9e1a000 - 00000000d9ff2000 (reserved) >> > > (XEN) 00000000d9ff2000 - 00000000da000000 (usable) >> > > (XEN) 00000000db000000 - 00000000df200000 (reserved) >> > > (XEN) 00000000f8000000 - 00000000fc000000 (reserved) >> > > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) >> > > (XEN) 00000000fed00000 - 00000000fed04000 (reserved) >> > > (XEN) 00000000fed1c000 - 00000000fed45000 (reserved) >> > > (XEN) 00000000fed90000 - 00000000fed94000 (reserved) >> > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) >> > > (XEN) 00000000ff000000 - 0000000100000000 (reserved) >> > > (XEN) 0000000100000000 - 000000011ee00000 (usable) >> > > (XEN) ACPI: RSDP 000F9810, 0024 (r2 HPQOEM) >> > > (XEN) ACPI: XSDT D8A2C088, 0094 (r1 HPQOEM SLIC-BPC 1072009 AMI >> 10013) >> > > (XEN) ACPI: FACP D8A36650, 010C (r5 HPQOEM SLIC-BPC 1072009 AMI >> 10013) >> > > (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer than >> ACPI >> > > 2.0 version, truncating length 0x10C to 0xF4 [20070126] >> > > (XEN) ACPI: DSDT D8A2C1B0, A49B (r2 HPQOEM SLIC-BPC 17 INTL >> 20051117) >> > > (XEN) ACPI: FACS D8C12080, 0040 >> > > (XEN) ACPI: APIC D8A36760, 0072 (r3 HPQOEM SLIC-BPC 1072009 AMI >> 10013) >> > > (XEN) ACPI: FPDT D8A367D8, 0044 (r1 HPQOEM SLIC-BPC 1072009 AMI >> 10013) >> > > (XEN) ACPI: MCFG D8A36820, 003C (r1 HPQOEM SLIC-BPC 1072009 MSFT >> 97) >> > > (XEN) ACPI: HPET D8A36860, 0038 (r1 HPQOEM SLIC-BPC 1072009 AMI. >> 5) >> > > (XEN) ACPI: SSDT D8A36898, 036D (r1 SataRe SataTabl 1000 INTL >> 20091112) >> > > (XEN) ACPI: MSDM D8A36C08, 0055 (r3 HPQOEM SLIC-BPC 1072009 HPQ >> 10013) >> > > (XEN) ACPI: SSDT D8A36C60, 668F (r1 COMPAQ WMI 1 MSFT >> 3000001) >> > > (XEN) ACPI: SLIC D8A3D2F0, 0176 (r1 HPQOEM SLIC-BPC 1 >> 0) >> > > (XEN) ACPI: SSDT D8A3D468, 0968 (r1 PmRef Cpu0Ist 3000 INTL >> 20051117) >> > > (XEN) ACPI: SSDT D8A3DDD0, 0A92 (r1 PmRef CpuPm 3000 INTL >> 20051117) >> > > (XEN) ACPI: TCPA D8A3E868, 0032 (r2 APTIO4 NAPAASF 1 MSFT >> 1000013) >> > > (XEN) ACPI: DMAR D8A3E8A0, 00B8 (r1 INTEL SNB 1 INTL >> 1) >> > > (XEN) ACPI: ASF! D8A3E958, 00A5 (r32 INTEL HCG 1 TFSM >> > > F4240) >> > > (XEN) System RAM: 3970MB (4065364kB) >> > > (XEN) Domain heap initialised >> > > (XEN) ACPI: 32/64X FACS address mismatch in FADT - >> > > d8c12080/0000000000000000, using 32 >> > > (XEN) Processor #0 7:10 APIC version 21 >> > > (XEN) Processor #2 7:10 APIC version 21 >> > > (XEN) Processor #4 7:10 APIC version 21 >> > > (XEN) Processor #6 7:10 APIC version 21 >> > > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 >> > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >> > > *(XEN) Table is not found!* >> > > (XEN) Switched to APIC driver x2apic_cluster. >> > > (XEN) Using scheduler: SMP Credit Scheduler (credit) >> > > (XEN) Detected 2893.477 MHz processor. >> > > (XEN) Initing memory sharing. >> > > (XEN) Intel VT-d Snoop Control not enabled. >> > > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. >> > > (XEN) Intel VT-d Queued Invalidation enabled. >> > > (XEN) Intel VT-d Interrupt Remapping enabled. >> > > (XEN) Intel VT-d Shared EPT tables not enabled. >> > > (XEN) I/O virtualisation enabled >> > > (XEN) - Dom0 mode: Relaxed >> > > (XEN) Enabled directed EOI with ioapic_ack_old on! >> > > (XEN) ENABLING IO-APIC IRQs >> > > (XEN) -> Using old ACK method >> > > (XEN) Platform timer is 14.318MHz HPET >> > > (XEN) Allocated console ring of 16 KiB. >> > > (XEN) VMX: Supported advanced features: >> > > (XEN) - APIC MMIO access virtualisation >> > > (XEN) - APIC TPR shadow >> > > (XEN) - Extended Page Tables (EPT) >> > > (XEN) - Virtual-Processor Identifiers (VPID) >> > > (XEN) - Virtual NMI >> > > (XEN) - MSR direct-access bitmap >> > > (XEN) - Unrestricted Guest >> > > (XEN) EPT supports 2MB super page. >> > > (XEN) HVM: ASIDs enabled. >> > > (XEN) HVM: VMX enabled >> > > (XEN) HVM: Hardware Assisted Paging detected. >> > > (XEN) Brought up 4 CPUs >> > > (XEN) *** LOADING DOMAIN 0 *** >> > > (XEN) Xen kernel: 64-bit, lsb, compat32 >> > > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2353000 >> > > (XEN) PHYSICAL MEMORY ARRANGEMENT: >> > > (XEN) Dom0 alloc.: 0000000110000000->0000000114000000 (936161 >> pages to >> > > be allocated) >> > > (XEN) Init. ramdisk: 000000011b2cb000->000000011edff800 >> > > (XEN) VIRTUAL MEMORY ARRANGEMENT: >> > > (XEN) Loaded kernel: ffffffff81000000->ffffffff82353000 >> > > (XEN) Init. ramdisk: ffffffff82353000->ffffffff85e87800 >> > > (XEN) Phys-Mach map: ffffffff85e88000->ffffffff865ea0b0 >> > > (XEN) Start info: ffffffff865eb000->ffffffff865eb4b4 >> > > (XEN) Page tables: ffffffff865ec000->ffffffff86623000 >> > > (XEN) Boot stack: ffffffff86623000->ffffffff86624000 >> > > (XEN) TOTAL: ffffffff80000000->ffffffff86800000 >> > > (XEN) ENTRY ADDRESS: ffffffff81cf2210 >> > > (XEN) Dom0 has maximum 2 VCPUs >> > > (XEN) Scrubbing Free RAM: .done. >> > > (XEN) Xen trace buffers: disabled >> > > (XEN) Std. Loglevel: Errors and warnings >> > > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) >> > > (XEN) Xen is relinquishing VGA console. >> > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch >> input >> > > to Xen) >> > > (XEN) Freed 216kB init memory. >> > > (XEN) no cpu_id for acpi_id 5 >> > > (XEN) no cpu_id for acpi_id 6 >> > > (XEN) no cpu_id for acpi_id 7 >> > > (XEN) no cpu_id for acpi_id 8 >> > > *(XEN) physdev.c:162: dom0: wrong map_pirq type 3* >> > > >> > > >> > > >> ------------------------------------///----------------------------------------- >> > > >> > > *# virsh dumpxml hvm-1* >> > > <domain type=''xen'' id=''4''> >> > > <name>hvm-2</name> >> > > <uuid>634e3f03-4855-8bb8-4e9e- >> > > f28d4ce7671a</uuid> >> > > <memory unit=''KiB''>524288</memory> >> > > <currentMemory unit=''KiB''>524288</currentMemory> >> > > <vcpu placement=''static''>1</vcpu> >> > > <os> >> > > <type>hvm</type> >> > > <loader>/usr/lib/xen/boot/hvmloader</loader> >> > > <kernel>/home/swart/yoctoimage/sandybayimages/bzImage</kernel> >> > > <cmdline>root=/dev/hda ip=dhcp acpi=off apic=off</cmdline> >> > > </os> >> > > <features> >> > > <acpi/> >> > > <apic/> >> > > <pae/> >> > > </features> >> > > <clock offset=''variable'' adjustment=''0'' basis=''utc''> >> > > <timer name=''hpet'' present=''no''/> >> > > </clock> >> > > <on_poweroff>destroy</on_poweroff> >> > > <on_reboot>restart</on_reboot> >> > > <on_crash>restart</on_crash> >> > > <devices> >> > > <emulator>/usr/lib64/xen/bin/qemu-dm</emulator> >> > > <disk type=''file'' device=''disk''> >> > > <driver name=''file''/> >> > > <source >> > > >> file=''/home/swart/yoctoimage/sandybayimages/core-image-minimal-sugarbay.hddimg''/> >> > > <target dev=''hda'' bus=''ide''/> >> > > </disk> >> > > <interface type=''bridge''> >> > > <mac address=''00:16:3e:6f:f9:72''/> >> > > <source bridge=''xenbr0''/> >> > > <script path=''/etc/xen/scripts/vif-bridge''/> >> > > <target dev=''vif4.0''/> >> > > <model type=''e1000''/> >> > > </interface> >> > > <serial type=''pty''> >> > > <source path=''/dev/pts/0''/> >> > > <target port=''0''/> >> > > </serial> >> > > <console type=''pty'' tty=''/dev/pts/0''> >> > > <source path=''/dev/pts/0''/> >> > > <target type=''serial'' port=''0''/> >> > > </console> >> > > <input type=''mouse'' bus=''ps2''/> >> > > <graphics type=''vnc'' port=''5900'' autoport=''yes'' keymap=''en-us''/> >> > > <sound model=''es1370''/> >> > > </devices> >> > > </domain> >> > > ----------------------//---------------------------- >> > > WHILE THE GUEST IS BOOTING.... >> > > [image: Inline image 1] >> > > HOST: Ubuntu-12.0.4 LTS >> > > XEN: xen-hypervisor-4.1-amd64 >> > > BIOS REVISION: 2.83 >> > > >> > > I highly appreciate your support, >> > > >> > > Thank you, >> > > >> > > //nas >> > > >> >> >> >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xen.org >> > http://lists.xen.org/xen-users >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Fri, Jun 14, 2013 at 12:32:01PM +0200, nesredin mahmud wrote:> hello again, > > I did the same the procedure with xen-4.2.2, the guest machine booted > successfully. But I wana do it on xen-4.1.2 because virt-manager seems to > work very well in this version and also is default ubuntu distribution > support. > I hope am not pushing so hard...but i have reproduced similar problem on > xen-4.1.2 from the guest machine and it seems a console problem. But i ve > no clue what to do next.Can you ssh into the guest even if the console is stuck? Serial console freezing doesn''t necessary means the guest is crashed / stuck. If the guest is still working, can you use ssh instead? Wei.