Re: [Xen-users] Fedora 19 installation with virt-install

[Alberto <alberto@xxxxxxxxxxx>]

Thanks for your answer, Ian

El 29/07/13 11:52, Ian Campbell escribiÃ:
> On Sun, 2013-07-28 at 13:14 +0200, Alberto wrote:
>> Hello,
>> I want to install a DomU with Fedora 19 in a Debian Host Dom0 with the
>> following versions...
> 
> Debian Squeeze from the looks of things? But with some Debian Wheezy
> installed (e.g. xenutils and xenstore have been upgraded, the rest of
> Xen and the kernel has not)?
> 

Debian Squeeze upgraded today!
:-P

>> ii  libc6-xen:i386                        2.13-38
>>      i386         Embedded GNU C Library: Shared libraries [Xen version]
>> ii  libxen-4.1                            4.1.4-3+deb7u1
>>      i386         Public libs for Xen
>> ii  libxenstore3.0                        4.1.4-3+deb7u1
>>      i386         Xenstore communications library for Xen
>> ii  linux-headers-2.6.32-5-common-xen     2.6.32-48squeeze1
>>      i386         Common header files for Linux 2.6.32-5-xen
>> ii  linux-image-2.6.32-5-xen-686          2.6.32-48squeeze1
>>      i386         Linux 2.6.32 for modern PCs, Xen dom0 support
>> ii  linux-image-xen-686                   2.6.32+29
>>      i386         Linux for modern PCs (meta-package), Xen dom0 support
>> ii  xen-docs-4.0                          4.0.1-5.10
>>      all          Documentation for Xen
>> ii  xen-hypervisor-4.0-i386               4.0.1-5.10
>>      i386         The Xen Hypervisor on i386
>> ii  xen-qemu-dm-4.0                       4.0.1-2+squeeze3
>>      i386         Xen Qemu Device Model virtual machine hardware emulator
>> ii  xen-tools                             4.3.1-1
>>      all          Tools to manage Xen virtual servers
>> ii  xen-utils-4.0                         4.0.1-5.10
>>      i386         XEN administrative tools
>> ii  xen-utils-common                      4.1.4-3+deb7u1
>>      all          Xen administrative tools - common files
>> ii  xenstore-utils                        4.1.4-3+deb7u1
>>      i386         Xenstore utilities for Xen
>> ii  xenwatch                              0.5.4-3
>>      i386         Virtualization utilities, mostly for Xen
>>
>>
>> The line what I use for the installation is...
>>
>> root@apevia:/etc/xen# virt-install --name=fedora19 --ram 512 --disk
>> path=/dev/MVvg/FEDORA19lv --location
>> http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/releases/19/Fedora/i386/os/
>> --description="Fedora" --network bridge=xenbr1 --hvm --vnc
>>
>> Empezando la instalaciïn...
Starting installation...

>> Obteniendo archivo .treeinfo...
Downloading .treeinfo file...

>>                                                              | 2.4 kB
>>   00:00 ...
>> Obteniendo archivo vmlinuz...
Downloading vmlinuz file...
>>                                                              | 9.4 MB
>>   00:17 ...
>> Obteniendo archivo initrd.img...
Downloading initrd.img file...
>>                                                              |  61 MB
>>   02:01 ...
>> Creando dominio...
Creating domain...

>>                                                              |    0 B
>>   00:00
>> No protocol specified
>> No se puede abrir el visor:
Can't open viewer:

>> Run 'virt-viewer --help' to see a full list of available command line
>> options
>> La instalaciïn del dominio continïa en progreso. Puede reconectarse a
>> la consola para completar el proceso de instalaciïn.
The domain installation process continues. You can reconnect to console
for complete installation process.

> Please can you rerun this command with prefixed with "LANG=C" so we can
> all read the messages.

I wrote above the translations.


>> It seems that the installation starts the DomU System, but after a few
>> seconds, it dies.  The XML file remains but the machine will not start.
>>
>> Can somebody help me?
>> Thank you so much
>>
>>
>>
>> LOGS FILES
> 
> The content of "xm dmesg" might contain a clue. More importantly since
> this looks like a guest crash would be to try to collect some guest
> logs.
> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs
> should help.

I reviewed your link, but Debian not have the /etc/default/xencommons
file (I probed creating and adding the line), and I add to
/etc/default/xend file, but without sucess.

I think that the "xm dmesg" not contain clues, this is...

...
(XEN)  00000000fff00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000230000000 (usable)
(XEN) System RAM: 8191MB (8387704kB)
(XEN) ACPI: RSDP 000FBB20, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT CFF80100, 005C (r1 A_M_I_ OEMXSDT   9000911 MSFT       97)
(XEN) ACPI: FACP CFF80290, 00F4 (r3 A_M_I_ OEMFACP   9000911 MSFT       97)
(XEN) ACPI: DSDT CFF80440, A01F (r1  A1032 A1032001        1 INTL 20051117)
(XEN) ACPI: FACS CFF8E000, 0040
(XEN) ACPI: APIC CFF80390, 006C (r1 A_M_I_ OEMAPIC   9000911 MSFT       97)
(XEN) ACPI: MCFG CFF80400, 003C (r1 A_M_I_ OEMMCFG   9000911 MSFT       97)
(XEN) ACPI: OEMB CFF8E040, 0089 (r1 A_M_I_ AMI_OEM   9000911 MSFT       97)
(XEN) ACPI: HPET CFF8A460, 0038 (r1 A_M_I_ OEMHPET   9000911 MSFT       97)
(XEN) ACPI: OSFR CFF8A4A0, 00B0 (r1 A_M_I_ OEMOSFR   9000911 MSFT       97)
(XEN) ACPI: SSDT CFF8E650, 0A7C (r1 DpgPmm    CpuPm       12 INTL 20051117)
(XEN) Xen heap: 8MB (8844kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:7 APIC version 20
(XEN) Processor #1 7:7 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2800.181 MHz processor.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: ASIDs disabled.
(XEN) HVM: VMX enabled
(XEN) I/O virtualisation disabled
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x1653000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000038000000->000000003c000000 (2028798 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c1000000->c1653000
(XEN)  Init. ramdisk: c1653000->c1e42000
(XEN)  Phys-Mach map: c1e42000->c260f3f8
(XEN)  Start info:    c2610000->c261047c
(XEN)  Page tables:   c2611000->c262a000
(XEN)  Boot stack:    c262a000->c262b000
(XEN)  TOTAL:         c0000000->c2800000
(XEN)  ENTRY ADDRESS: c1401000
(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 152kB init memory.


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