Xen Project Q&A Forum: First Line Help for Simple Questions

This is your chance to ask questions and provide answers about basic use of the Xen Project software. For debugging problems and for more complex issues, consider using the xen-users mailing list instead. You can find information about xen-users under "HELP | Mailing Lists" in the navigation bar above.

Issue
Stefan
Stefan
Offline
0
Hello Xen community,

I am working for a company and try and virtualise our own 32-bit Unix based real-time operating system. However I am new to the field of virtualisation. I followed some tutorials to try to get our OS running as HVM on Xen using Debian Wheezy version 7.4. But I run into the following errors:

Using:
xm dmesg


Gives:
    (XEN) Xen version 4.1.4 (Debian 4.1.4-3+deb7u1) (carnil@debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) Fri May 10 07:22:47 UTC 2013
    (XEN) Bootloader: GRUB 1.99-27+deb7u2
    (XEN) Command line: placeholder dom0_max_vcpus=1 dom0_vcpus_pin
    (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 - 000000000009d800 (usable)
    (XEN)  000000000009d800 - 00000000000a0000 (reserved)
    (XEN)  00000000000e0000 - 0000000000100000 (reserved)
    (XEN)  0000000000100000 - 00000000bac8f000 (usable)
    (XEN)  00000000bac8f000 - 00000000bade2000 (reserved)
    (XEN)  00000000bade2000 - 00000000badea000 (ACPI NVS)
    (XEN)  00000000badea000 - 00000000baf1f000 (reserved)
    (XEN)  00000000baf1f000 - 00000000baf9f000 (ACPI NVS)
    (XEN)  00000000baf9f000 - 00000000bafff000 (ACPI data)
    (XEN)  00000000bafff000 - 00000000bb000000 (usable)
    (XEN)  00000000bb000000 - 00000000bfa00000 (reserved)
    (XEN)  00000000f8000000 - 00000000fc000000 (reserved)
    (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
    (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
    (XEN)  00000000fed10000 - 00000000fed1a000 (reserved)
    (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
    (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
    (XEN)  00000000ffd80000 - 0000000100000000 (reserved)
    (XEN)  0000000100000000 - 000000013e9ff000 (usable)
    (XEN)  000000013e9ff000 - 000000013fe00000 (reserved)
    (XEN) System RAM: 3990MB (4085936kB)
    (XEN) ACPI: RSDP 000F00E0, 0024 (r2 DELL  )
    (XEN) ACPI: XSDT BAFFE120, 008C (r1 DELL    QA09           2 LOHR        2)
    (XEN) ACPI: FACP BAFF0000, 00F4 (r3 DELL    QA09           2 PTL         2)
    (XEN) ACPI: DSDT BAFF3000, 8FB3 (r2 DELL    SNB-CPT        0 INTL 20061109)
    (XEN) ACPI: FACS BAF40000, 0040
    (XEN) ACPI: SLIC BAFFD000, 0176 (r1 DELL    QA09           2 LOHR        1)
    (XEN) ACPI: SSDT BAFFC000, 0166 (r1 DELL   PtidDevc     1000 INTL 20061109)
    (XEN) ACPI: ASF! BAFF2000, 00A5 (r32 DELL    QA09           2 PTL         2)
    (XEN) ACPI: HPET BAFEF000, 0038 (r1 DELL    QA09           2 PTL         2)
    (XEN) ACPI: APIC BAFEE000, 0098 (r1 DELL    QA09           2 PTL         2)
    (XEN) ACPI: MCFG BAFED000, 003C (r1 DELL    QA09           2 PTL         2)
    (XEN) ACPI: SSDT BAFEB000, 12AD (r1 NvORef NvOptTbl     1000 INTL 20061109)
    (XEN) ACPI: SSDT BAFEA000, 090C (r1  PmRef  Cpu0Ist     3000 INTL 20061109)
    (XEN) ACPI: SSDT BAFE9000, 0996 (r1  PmRef    CpuPm     3000 INTL 20061109)
    (XEN) ACPI: UEFI BAFE8000, 003E (r1 DELL    QA09           2 PTL         2)
    (XEN) ACPI: UEFI BAFE7000, 0042 (r1 PTL      COMBUF        1 PTL         1)
    (XEN) ACPI: UEFI BAFE6000, 026A (r1 DELL    QA09           2 PTL         2)
    (XEN) Xen heap: 9MB (9764kB)
    (XEN) Domain heap initialised
    (XEN) Processor #0 6:10 APIC version 21
    (XEN) Processor #1 6:10 APIC version 21
    (XEN) Processor #2 6:10 APIC version 21
    (XEN) Processor #3 6: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) Using scheduler: SMP Credit Scheduler (credit)
    (XEN) Detected 2095.309 MHz processor.
    (XEN) I/O virtualisation disabled
    (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) HVM: ASIDs enabled.
    (XEN) HVM: VMX enabled
    (XEN) HVM: Hardware Assisted Paging (HAP) detected
    (XEN) HVM: HAP page sizes: 4kB, 2MB
    (XEN) Brought up 4 CPUs
    (XEN) *** LOADING DOMAIN 0 ***
    (XEN)  Xen  kernel: 32-bit, PAE, lsb
    (XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x1786000
    (XEN) PHYSICAL MEMORY ARRANGEMENT:
    (XEN)  Dom0 alloc.:   0000000138000000->000000013a000000 (963846 pages to be allocated)
    (XEN)  Init. ramdisk: 000000013d056000->000000013e7ff800
    (XEN) VIRTUAL MEMORY ARRANGEMENT:
    (XEN)  Loaded kernel: c1000000->c1786000
    (XEN)  Init. ramdisk: c1786000->c2f2f800
    (XEN)  Phys-Mach map: c2f30000->c32eb2c0
    (XEN)  Start info:    c32ec000->c32ec47c
    (XEN)  Page tables:   c32ed000->c330c000
    (XEN)  Boot stack:    c330c000->c330d000
    (XEN)  TOTAL:         c0000000->c3400000
    (XEN)  ENTRY ADDRESS: c141b000
    (XEN) Dom0 has maximum 1 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 188kB init memory.
    (XEN) mm.c:918:d0 Error getting mfn 3809d (pfn bf74d) from L1 entry 000000003809d023 for l1e_owner=0, pg_owner=0
    (XEN) mm.c:918:d0 Error getting mfn 3809e (pfn bf74e) from L1 entry 000000003809e023 for l1e_owner=0, pg_owner=0
    (XEN) mm.c:918:d0 Error getting mfn 3809f (pfn bf74f) from L1 entry 000000003809f023 for l1e_owner=0, pg_owner=0
    (XEN) physdev.c:168: dom0: wrong map_pirq type 3


Using:
    cat /var/log/xen/qemu-dm-gp.log


Gives:
    domid: 4
    -c config qemu network with xen bridge for
    vif4.0-emu xenbr0
    Using file /usr/images/gp.img in read-write mode
    Watching /local/domain/0/device-model/4/logdirty/cmd
    Watching /local/domain/0/device-model/4/command
    Watching /local/domain/4/cpu
    char device redirected to /dev/pts/0
    qemu_map_cache_init nr_buckets = 4000 size 327680
    shared page at pfn feffd
    buffered io page at pfn feffb
    Guest uuid = 018df513-c808-f1d7-1a7c-d87576dc28b4
    Time offset set 0
    populating video RAM at ff000000
    mapping video RAM from ff000000
    Register xen platform.
    Done register platform.
    platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
    xs_read(/local/domain/0/device-model/4/xen_extended_power_mgmt): read error
    Log-dirty: no command yet.
    I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
    I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
    vcpu-set: watch node error.
    I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
    I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
    xs_read(/local/domain/4/log-throttling): read error
    qemu: ignoring not-understood drive `/local/domain/4/log-throttling'
    medium change watch on `/local/domain/4/log-throttling' - unknown device, ignored
    char device redirected to /dev/pts/1
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    xen be: console-0: xen be: console-0: initialise() failed
    initialise() failed
    cirrus vga map change while on lfb mode
    mapping vram to f0000000 - f0400000
    platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
    platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.


My config file:
    kernel = "/usr/lib/xen-4.1/boot/hvmloader"
    builder='hvm'
    memory=256
    vcpus=4
    name="gp"
    vif=['bridge=xenbr0']
    disk=['file:/usr/images/gp.img,hda,w']
    acpi=1
    device_model= 'qemu-dm'
    boot="d"
    sdl=0
    serial='pty'
    vnc=0


What am I doing wrong? Did I miss something in my CFG? Should I upgrade to a newer Xen version? Please let me know! Thanks in advance.;)

Accepted Answer

Stefan
Stefan
Offline
Monday, March 24 2014, 02:02 PM - #permalink
0
Update: the DomU now runs fine under Xen 4.3. :D
The reply is currently minimized Show
Responses (2)
  • Accepted Answer

    Wednesday, March 19 2014, 03:17 PM - #permalink
    0
    Stefan,

    I'm not an expert at the logs, but it looks like there might be a problem reading the gp.img file.

    Is the file in the proper location? How was that image created?

    Russ
    The reply is currently minimized Show
  • Accepted Answer

    Stefan
    Stefan
    Offline
    Thursday, March 20 2014, 02:59 PM - #permalink
    0
    It was converted by using qemu-img convert from our flat vmdk image.
    And indeed there might be a problem regarding the image file as I now moved the whole project to Xen 4.3 and it will say device model: spawn failed (rc=-3) almost right after trying to spawn the image.
    The reply is currently minimized Show
Your Reply