Xen project Mailing List

Hello Wei,

On Sun, Jun 9, 2013 at 1:26 PM, Wei Liu <wei.liu2@xxxxxxxxxx> 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@xxxxxxxxx>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@xxxxxxxxxxxxx) (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@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users

Re: [Xen-users] DomU: piix:not 100% native mode: will probe irq later