|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Xen does not run domU
Cool, you got me on the true way. I just changed /usr/lib/xen/bin/qemu-dm' to /usr/lib64/xen/bin/qemu-dm' And it started normally. It is my first expirience with Linux in real conditions, thank you for you attention, you did not provide a clear answer, but you really helped me! 2008/12/7 <javera@xxxxxxxxxxxxxx>: > Hi Andrew. > > I don't know centos and yum very well but I suppose that it has a config file > for yum command with a lot of repositories to find the centos and xen > packages. So, you can try go to the xen site that appears in the repository > file with firefox and look for a package with ioemu sobstring. Then, repeat > your yum command but with the correct ioemu xen package name. > > > --- > > -----Original Message----- > From: "Andrey Chursin" <andll@xxxxxxxxxxx> > > Date: Sun, 7 Dec 2008 17:06:17 > To: <javera@xxxxxxxxxxxxxx> > Cc: <xen-users@xxxxxxxxxxxxxxxxxxx> > Subject: Re: [Xen-users] Xen does not run domU > > > I installed xen using > yum install xen > > I hoped, it is enougth to instal all required by xen, is not it? > > If not, how can i install additional package, google found many > solutions with apt-get util, but centos have no apt-get, afaik. > > > 2008/12/7 <javera@xxxxxxxxxxxxxx>: >> Do you have installed a package named xen-ioemu? I think that with this >> package you can see the qemu files that xen generates when it boots with hvm >> capabilities >> --- >> >> -----Original Message----- >> From: "Andrey Chursin" <andll@xxxxxxxxxxx> >> >> Date: Sun, 7 Dec 2008 15:51:52 >> To: <javera@xxxxxxxxxxxxxx> >> Cc: <xen-users@xxxxxxxxxxxxxxxxxxx> >> Subject: Re: [Xen-users] Xen does not run domU >> >> >> Hi, Javera, thank you for your answer. >> >> Unfortunelly, there is only 3 files and 1 directory in /var/log/xen: >> console xend-debug.log xend.log xen-hotplug.log >> >> I do not see any 'qemu' file... >> >> May be you mean another file name, or it is there in different >> location on CentOS? >> >> 2008/12/7 <javera@xxxxxxxxxxxxxx>: >>> You can see in /var/log/xen qemu log files for looking more information. >>> >>> javera >>> --- >>> >>> -----Original Message----- >>> From: "Andrey Chursin" <andll@xxxxxxxxxxx> >>> >>> Date: Sun, 7 Dec 2008 15:02:59 >>> To: <xen-users@xxxxxxxxxxxxxxxxxxx> >>> Subject: [Xen-users] Xen does not run domU >>> >>> >>> Hello, guys! >>> >>> My computer is running CentOS 5.0 with Xen >>> >>> I have a trouble with booting guest domain(domU). >>> >>> I have next script file: >>> >>> kernel = '/usr/lib/xen/boot/hvmloader' >>> builder = 'hvm' >>> memory = '1024' >>> device_model='/usr/lib/xen/bin/qemu-dm' >>> disk = [ 'file:/xen/0/disk.img,ioemu:hda,w', >>> 'file:/xen/0/ubuntu-8.10-desktop-i386.iso,ioemu:hdc:cdrom,r' ] >>> name = 'win01' >>> #vif = ['type=ioemu, bridge=xenbr0'] >>> boot='d' >>> vnc=1 >>> vncviewer=0 >>> sdl=0 >>> vncdisplay = "0" >>> vnclisten = "0.0.0.0" >>> >>> Where >>> /xen/0/disk.img - zero filled 40 Gb file, >>> /xen/0/ubuntu-8.10-desktop-i386.iso - ubuntu's distrib, downloaded >>> from official mirror >>> >>> When I am typing >>> Xm create file_name >>> I get next messages: >>> Using config file "./script". >>> Started domain win01 >>> >>> But then, if I write xm list, I see next: >>> Name ID Mem(MiB) VCPUs State Time(s) >>> Domain-0 0 2973 4 r----- 1383.4 >>> win01 1 1023 1 ------ 0.0 >>> (!) >>> >>> AFAIK it means that win01 was not started(0 second execution time), am >>> I wrong here? >>> >>> Can you help me to determine the problem? Is there any log file or >>> something like it when I can see, what is wrong with my domU? May be >>> it is known issue, or something like it? >>> >>> Thank you for your attention. >>> >>> >>> >>> INFORMATION about the system: >>> >>> Xm info shows next information: >>> >>> host : *** >>> release : 2.6.18-92.1.18.el5xen >>> version : #1 SMP Wed Nov 12 09:48:10 EST 2008 >>> machine : x86_64 >>> nr_cpus : 4 >>> nr_nodes : 1 >>> sockets_per_node : 1 >>> cores_per_socket : 4 >>> threads_per_core : 1 >>> cpu_mhz : 1695 >>> hw_caps : >>> 178bfbff:efd3fbff:00000000:00000110:00802009:00000000:000007ff >>> total_memory : 4094 >>> free_memory : 127 >>> node_to_cpu : node0:0-3 >>> xen_major : 3 >>> xen_minor : 1 >>> xen_extra : .2-92.1.18.el5 >>> 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_pagesize : 4096 >>> platform_params : virt_start=0xffff800000000000 >>> xen_changeset : unavailable >>> cc_compiler : gcc version 4.1.2 20071124 (Red Hat 4.1.2-42) >>> cc_compile_by : mockbuild >>> cc_compile_domain : centos.org >>> cc_compile_date : Wed Nov 12 09:13:10 EST 2008 >>> xend_config_format : 2 >>> >>> xm dmesg shows: >>> >>> __ __ _____ _ ____ ___ ____ _ _ ___ _ ____ >>> \ \/ /___ _ __ |___ / / | |___ \ / _ \___ \ / | / |( _ ) ___| | ___| >>> \ // _ \ \047_ \ |_ \ | | __) |_| (_) |__) | | | | |/ _ \ / _ \ |___ >>> \ >>> / \ __/ | | | ___) || |_ / __/|__\__, / __/ _| |_| | (_) | __/ |___) | >>> /_/\_\___|_| |_| |____(_)_(_)_____| /_/_____(_)_(_)_|\___(_)___|_|____/ >>> >>> http://www.cl.cam.ac.uk/netos/xen >>> University of Cambridge Computer Laboratory >>> >>> Xen version 3.1.2-92.1.18.el5 (mockbuild@xxxxxxxxxx) (gcc version >>> 4.1.2 20071124 (Red Hat 4.1.2-42)) Wed Nov 12 09:13:10 EST 2008 >>> Latest ChangeSet: unavailable >>> >>> (XEN) Command line: >>> (XEN) Video information: >>> (XEN) VGA is text mode 80x25, font 8x16 >>> (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds >>> (XEN) EDID info not retrieved because no DDC retrieval method detected >>> (XEN) Disc information: >>> (XEN) Found 1 MBR signatures >>> (XEN) Found 1 EDD information structures >>> (XEN) Xen-e820 RAM map: >>> (XEN) 0000000000000000 - 000000000009cc00 (usable) >>> (XEN) 000000000009cc00 - 00000000000a0000 (reserved) >>> (XEN) 00000000000d0000 - 0000000000100000 (reserved) >>> (XEN) 0000000000100000 - 00000000d7f40000 (usable) >>> (XEN) 00000000d7f40000 - 00000000d7f4e000 (ACPI data) >>> (XEN) 00000000d7f4e000 - 00000000d7f80000 (ACPI NVS) >>> (XEN) 00000000d7f80000 - 00000000d8000000 (reserved) >>> (XEN) 00000000e0000000 - 00000000f0000000 (reserved) >>> (XEN) 00000000fec00000 - 00000000fec03000 (reserved) >>> (XEN) 00000000fed00000 - 00000000fed00400 (reserved) >>> (XEN) 00000000fee00000 - 00000000fee01000 (reserved) >>> (XEN) 00000000fff00000 - 0000000100000000 (reserved) >>> (XEN) 0000000100000000 - 0000000128000000 (usable) >>> (XEN) System RAM: 4094MB (4193136kB) >>> (XEN) Xen heap: 14MB (14892kB) >>> (XEN) Domain heap initialised: DMA width 32 bits >>> (XEN) Processor #0 0:2 APIC version 16 >>> (XEN) Processor #1 0:2 APIC version 16 >>> (XEN) Processor #2 0:2 APIC version 16 >>> (XEN) Processor #3 0:2 APIC version 16 >>> (XEN) IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-15 >>> (XEN) IOAPIC[1]: apic_id 5, version 17, address 0xfec01000, GSI 16-31 >>> (XEN) IOAPIC[2]: apic_id 6, version 17, address 0xfec02000, GSI 32-47 >>> (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs >>> (XEN) Using scheduler: SMP Credit Scheduler (credit) >>> (XEN) Detected 1695.794 MHz processor. >>> (XEN) AMD SVM: ASIDs enabled. >>> (XEN) HVM: SVM enabled >>> (XEN) HVM: Hardware Assisted Paging detected and enabled. >>> (XEN) CPU0: AMD Quad-Core AMD Opteron(tm) Processor 2344 HE stepping 03 >>> (XEN) Booting processor 1/1 eip 90000 >>> (XEN) AMD SVM: ASIDs enabled. >>> (XEN) CPU1: AMD Quad-Core AMD Opteron(tm) Processor 2344 HE stepping 03 >>> (XEN) Booting processor 2/2 eip 90000 >>> (XEN) AMD SVM: ASIDs enabled. >>> (XEN) CPU2: AMD Quad-Core AMD Opteron(tm) Processor 2344 HE stepping 03 >>> (XEN) Booting processor 3/3 eip 90000 >>> (XEN) AMD SVM: ASIDs enabled. >>> (XEN) CPU3: AMD Quad-Core AMD Opteron(tm) Processor 2344 HE stepping 03 >>> (XEN) Total of 4 processors activated. >>> (XEN) ENABLING IO-APIC IRQs >>> (XEN) -> Using new ACK method >>> (XEN) Platform timer overflows in 14998 jiffies. >>> (XEN) Platform timer is 14.318MHz HPET >>> (XEN) Brought up 4 CPUs >>> (XEN) *** LOADING DOMAIN 0 *** >>> (XEN) elf_parse_binary: phdr: paddr=0xffffffff80200000 memsz=0x2d6d20 >>> (XEN) elf_parse_binary: phdr: paddr=0xffffffff804d6d80 memsz=0x1161d0 >>> (XEN) elf_parse_binary: phdr: paddr=0xffffffff805ed000 memsz=0xc08 >>> (XEN) elf_parse_binary: phdr: paddr=0xffffffff805ee000 memsz=0x1134e4 >>> (XEN) elf_parse_binary: memory: 0xffffffff80200000 -> 0xffffffff807014e4 >>> (XEN) elf_xen_parse_note: GUEST_OS = "linux" >>> (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" >>> (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" >>> (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 >>> (XEN) elf_xen_parse_note: PADDR_OFFSET = 0xffffffff80000000 >>> (XEN) elf_xen_parse_note: ENTRY = 0xffffffff80200000 >>> (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80206000 >>> (XEN) elf_xen_parse_note: FEATURES = >>> "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel" >>> (XEN) elf_xen_parse_note: LOADER = "generic" >>> (XEN) elf_xen_addr_calc_check: addresses: >>> (XEN) virt_base = 0xffffffff80000000 >>> (XEN) elf_paddr_offset = 0xffffffff80000000 >>> (XEN) virt_offset = 0x0 >>> (XEN) virt_kstart = 0xffffffff80200000 >>> (XEN) virt_kend = 0xffffffff807014e4 >>> (XEN) virt_entry = 0xffffffff80200000 >>> (XEN) Xen kernel: 64-bit, lsb, compat32 >>> (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> >>> 0xffffffff807014e4 >>> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>> (XEN) Dom0 alloc.: 0000000122000000->0000000124000000 (987118 pages >>> to be allocated) >>> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>> (XEN) Loaded kernel: ffffffff80200000->ffffffff807014e4 >>> (XEN) Init. ramdisk: ffffffff80702000->ffffffff80d3e600 >>> (XEN) Phys-Mach map: ffffffff80d3f000->ffffffff814d6f70 >>> (XEN) Start info: ffffffff814d7000->ffffffff814d749c >>> (XEN) Page tables: ffffffff814d8000->ffffffff814e7000 >>> (XEN) Boot stack: ffffffff814e7000->ffffffff814e8000 >>> (XEN) TOTAL: ffffffff80000000->ffffffff81800000 >>> (XEN) ENTRY ADDRESS: ffffffff80200000 >>> (XEN) Dom0 has maximum 4 VCPUs >>> (XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff804d6d20 >>> (XEN) elf_load_binary: phdr 1 at 0xffffffff804d6d80 -> 0xffffffff805ecf50 >>> (XEN) elf_load_binary: phdr 2 at 0xffffffff805ed000 -> 0xffffffff805edc08 >>> (XEN) elf_load_binary: phdr 3 at 0xffffffff805ee000 -> 0xffffffff80628388 >>> (XEN) Initrd len 0x63c600, start at 0xffffffff80702000 >>> (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 \047CTRL-a\047 three times to >>> switch input to Xen). >>> (XEN) Freed 100kB init memory. >>> >>> >>> >>> >>> -- >>> Regards, >>> Andrey >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@xxxxxxxxxxxxxxxxxxx >>> http://lists.xensource.com/xen-users >>> >>> -- >>> Aquest missatge ha estat verificat amb antivirus i >>> antispam. Es considera que esta net. >>> >>> >>> -- >>> Aquest missatge ha estat verificat amb antivirus i >>> antispam. Es considera que esta net. >>> >>> >> >> >> >> -- >> Regards, >> Andrey >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@xxxxxxxxxxxxxxxxxxx >> http://lists.xensource.com/xen-users >> >> -- >> Aquest missatge ha estat verificat amb antivirus i >> antispam. Es considera que esta net. >> >> >> -- >> Aquest missatge ha estat verificat amb antivirus i >> antispam. Es considera que esta net. >> >> > > > > -- > Regards, > Andrey > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users > > -- > Aquest missatge ha estat verificat amb antivirus i > antispam. Es considera que esta net. > > > -- > Aquest missatge ha estat verificat amb antivirus i > antispam. Es considera que esta net. > > -- Regards, Andrey _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |