WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] windows 2003 on xen-3.0.3 fails on disk format

To: "'Petersson, Mats'" <Mats.Petersson@xxxxxxx>, "'Konstantinos Pachopoulos'" <kostaspaxos@xxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] windows 2003 on xen-3.0.3 fails on disk format
From: "Artur Linhart - Linux communication" <AL.LINUX@xxxxxxxxxxx>
Date: Tue, 17 Apr 2007 15:19:28 +0200
Delivery-date: Tue, 17 Apr 2007 06:19:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B018E1BB3@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <461CC3E0.4030205@xxxxxxxx> <907625E08839C4409CE5768403633E0B018E1BB3@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acd8KxECLkWi621WQ7qpqzpcFFWGdAACx1XgAS8I/kA=
Hello, 

        Maybe I'm wrong, but I see You've started it with the configuration
> acpi=0
> apic=0
        And You have AMD64bit CPU - do You want to isntall also W2k# Server
64 bit? Because this I get running first after setting apic and acpi both to
1

        In other cases I encountered similar effects like You...

                Cheers, Archie.

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Petersson, Mats
Sent: Wednesday, April 11, 2007 2:43 PM
To: Konstantinos Pachopoulos; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] windows 2003 on xen-3.0.3 fails on disk format

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Konstantinos Pachopoulos
> Sent: 11 April 2007 12:18
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] windows 2003 on xen-3.0.3 fails on disk format
> 
> Hi,
> when i try to create a Windows 2003 domU image from an iso, 
> the Windows 
> installation fails at the beginning of the format
> procedure complaining that whether there is not enough memory for the 
> format procedure or installation files are corrupted
> - i have the same problem with WinXP and i do not think it is latter.

I'm pretty sure there's something going wrong with your qemu - I don't
know exactly WHAT goes wrong, but that's my feeling of this problem.
Check the latest qemu-dm.<pid>.log file (cat `ls -t|head -1` will show
you that) to see if that's got anything "interesting". 

You may also want to try an upgrade to Xen 3.0.4-1, as it's got a fair
number of improvements for HVM (SVM). 

I don't see anything wrong (including those messages about "unsupported
functions" in the BIOS - I get them all the time and they are harmless -
just means that the loader tries to do something that the BIOS doesn't
support, but loaders do a lot of things that may or may not be
important, including probing for functions that may or may not be
supported by the particular implementation - the only difference is that
most BIOS won't do anything to tell you that the software was trying to
use a function that didn't exist). 

--
Mats
> 
> My system is amd64 Debian Etch with an "AMD Athlon(tm) 64 X2 
> Dual Core 
> Processor 3800+" on an ASUS m2v m/b.
> 
> 
> starting with "xm create -c /etc/xen/win2003.hvm", i get:
> ===================================================================
> ...
> Started domain win2003
> xenconsole: Could not read tty from store: No such file or directory
> ===================================================================
> 
> 
> 
> Here's the my /var/log/xen/qemu-dm.9827.log:
> =================================================================== 
> domid: 7
> qemu: the number of cpus is 1
> shared page at pfn:2ffff, mfn: 109486
> buffered io page at pfn:2fffd, mfn: 109488
> False I/O request ... in-service already: 0, pvalid: 0, port: 
> 0, data: 
> 0, count: 0, size: 0
> ===================================================================
> 
> 
> 
> Here's my domU .conf. I have tried both with an LVM partition 
> and i am 
> now trying with an external USB hard disk -i face
> the same problem in both cases:
> ===================================================================
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>        arch_libdir='lib64'
> else:
>        arch_libdir='lib'
> 
> #--------------------------------------
> # kernel image file
> kernel= "/usr/lib/xen/boot/hvmloader"
> 
> # the domain build function. HVM domain uses 'hvm'
> builder='hvm'
> 
> memory=768
> name="win2003"
> #disk = ['phy:/dev/xendoms/winxp,ioemu:hda,w']
> #memmap = '/usr/lib/xen/boot/mem-map.sxp'
> device_model='/usr/'+arch_libdir+'/xen/bin/qemu-dm'
> disk=['phy:/dev/sda,ioemu:hda,w','file:/vservers/home/shared/i
> sos/WIN_SERVER_2003_EN.iso,hdc:cdrom,r'] 
> 
> #disk=['file:/mnt/1tmp/winxp.img,ioemu:hda,w','file:/vservers/
> home/shared/winxp.iso,hdc:cdrom,r'] 
> 
> boot="d"
> sdl=1
> vnc=0
> vncviewer=0
> ne2000=0
> acpi=0
> apic=0
> ===================================================================
> 
> 
> Here's the "xm dmesg" output. I noticed the last 2 lines:
> ===================================================================
> Xen version 3.0.3-1 (Debian 3.0.3-0-2) (ultrotter@xxxxxxxxxx) (gcc 
> version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)) Fri Nov  3 
> 00:21:27 CET 2006
> Latest ChangeSet: Tue Oct 17 22:09:52 2006 +0100
> 
> (XEN) Command line: /xen-3.0.3-1-amd64.gz
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009dc00 (usable)
> (XEN)  000000000009dc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e4000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000cffb0000 (usable)
> (XEN)  00000000cffb0000 - 00000000cffbe000 (ACPI data)
> (XEN)  00000000cffbe000 - 00000000cffe0000 (ACPI NVS)
> (XEN)  00000000cffe0000 - 00000000d0000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
> (XEN)  00000000fecc0000 - 00000000fecc1000 (reserved)
> (XEN)  00000000ff780000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000000130000000 (usable)
> (XEN) System RAM: 4095MB (4193588kB)
> (XEN) Xen heap: 13MB (14328kB)
> (XEN) found SMP MP-table at 000ff780
> (XEN) DMI present.
> (XEN) Using APIC driver default
> (XEN) ACPI: RSDP (v000 ACPIAM                                ) @ 
> 0x00000000000fa960
> (XEN) ACPI: RSDT (v001 NEC             0x02000709 MSFT 0x00000097) @ 
> 0x00000000cffb0000
> (XEN) ACPI: FADT (v002 A_M_I_ OEMFACP  0x02000709 MSFT 0x00000097) @ 
> 0x00000000cffb0200
> (XEN) ACPI: MADT (v001 A_M_I_ OEMAPIC  0x02000709 MSFT 0x00000097) @ 
> 0x00000000cffb0390
> (XEN) ACPI: MCFG (v001 A_M_I_ OEMMCFG  0x02000709 MSFT 0x00000097) @ 
> 0x00000000cffb0400
> (XEN) ACPI: SLIC (v001 NEC             0x02000709 MSFT 0x00000097) @ 
> 0x00000000cffb0440
> (XEN) ACPI: OEMB (v001 A_M_I_ AMI_OEM  0x02000709 MSFT 0x00000097) @ 
> 0x00000000cffbe040
> (XEN) ACPI: HPET (v001 A_M_I_ OEMHPET  0x02000709 MSFT 0x00000097) @ 
> 0x00000000cffb5400
> (XEN) ACPI: DSDT (v001  A0498 A0498000 0x00000000 INTL 0x20060113) @ 
> 0x0000000000000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:11 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> (XEN) Processor #1 15:11 APIC version 16
> (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x03] address[0xfecc0000] gsi_base[24])
> (XEN) IOAPIC[1]: apic_id 3, version 3, address 0xfecc0000, GSI 24-47
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) ACPI: IRQ9 used by override.
> (XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
> (XEN) ACPI: HPET id: 0x11068201 base: 0xfed00000
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Initializing CPU#0
> (XEN) Detected 1999.822 MHz processor.
> (XEN) CPU0: AMD Flush Filter disabled
> (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 
> bytes/line)
> (XEN) CPU: L2 Cache: 512K (64 bytes/line)
> (XEN) CPU 0(2) -> Core 0
> (XEN) AMD SVM Extension is enabled for cpu 0.
> (XEN) Intel machine check architecture supported.
> (XEN) Intel machine check reporting enabled on CPU#0.
> (XEN) CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
> (XEN) Booting processor 1/1 eip 90000
> (XEN) Initializing CPU#1
> (XEN) CPU1: AMD Flush Filter disabled
> (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 
> bytes/line)
> (XEN) CPU: L2 Cache: 512K (64 bytes/line)
> (XEN) CPU 1(2) -> Core 1
> (XEN) AMD: Disabling C1 Clock Ramping Node #0
> (XEN) AMD SVM Extension is enabled for cpu 1.
> (XEN) Intel machine check architecture supported.
> (XEN) Intel machine check reporting enabled on CPU#1.
> (XEN) CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
> (XEN) Total of 2 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using new ACK method
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0
> (XEN) checking TSC synchronization across 2 CPUs:
> (XEN) CPU#0 had 352 usecs TSC skew, fixed it up.
> (XEN) CPU#1 had -352 usecs TSC skew, fixed it up.
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) Brought up 2 CPUs
> (XEN) Machine check exception polling timer started.
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Domain 0 kernel supports features = { 0000001f }.
> (XEN) Domain 0 kernel requires features = { 00000000 }.
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000006000000->0000000008000000 
> (988709 pages 
> to be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80200000->ffffffff805995b0
> (XEN)  Init. ramdisk: ffffffff8059a000->ffffffff814b6a00
> (XEN)  Phys-Mach map: ffffffff814b7000->ffffffff81c52128
> (XEN)  Start info:    ffffffff81c53000->ffffffff81c5349c
> (XEN)  Page tables:   ffffffff81c54000->ffffffff81c67000
> (XEN)  Boot stack:    ffffffff81c67000->ffffffff81c68000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff82000000
> (XEN)  ENTRY ADDRESS: ffffffff80200000
> (XEN) Dom0 has maximum 2 VCPUs
> (XEN) Initrd len 0xf1ca00, start at 0xffffffff8059a000
> (XEN) Scrubbing Free RAM: 
> .................................................done.
> (XEN) Xen trace buffers: disabled
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch 
> input to Xen).
> (XEN) (GUEST: 2) HVM Loader
> (XEN) (GUEST: 2) Detected Xen v3.0.3-1
> (XEN) (GUEST: 2) Writing SMBIOS tables ...
> (XEN) (GUEST: 2) Loading ROMBIOS ...
> (XEN) (GUEST: 2) Loading Cirrus VGABIOS ...
> (XEN) (GUEST: 2) SVM go ...
> (XEN) (GUEST: 2)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
> (XEN) (GUEST: 2) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 
> vruppert Exp $
> (XEN) (GUEST: 2) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 
> 2005/05/07 15:55:26 $
> (XEN) (GUEST: 2)
> (XEN) (GUEST: 2) ata0-0: PCHS=14010/16/63 translation=lba 
> LCHS=879/255/63
> (XEN) (GUEST: 2) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk 
> (6896 MBytes)
> (XEN) (GUEST: 2) ata0  slave: Unknown device
> (XEN) (GUEST: 2) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
> (XEN) (GUEST: 2) ata1  slave: Unknown device
> (XEN) (GUEST: 2)
> (XEN) (GUEST: 2) Booting from CD-Rom...
> (XEN) (GUEST: 2) unsupported PCI BIOS function 0x0E
> (XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device 
> for ELDL=81
> (XEN) (GUEST: 3) HVM Loader
> (XEN) (GUEST: 3) Detected Xen v3.0.3-1
> (XEN) (GUEST: 3) Writing SMBIOS tables ...
> (XEN) (GUEST: 3) Loading ROMBIOS ...
> (XEN) (GUEST: 3) Loading Cirrus VGABIOS ...
> (XEN) (GUEST: 3) SVM go ...
> (XEN) (GUEST: 3)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
> (XEN) (GUEST: 3) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 
> vruppert Exp $
> (XEN) (GUEST: 3) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 
> 2005/05/07 15:55:26 $
> (XEN) (GUEST: 3)
> (XEN) (GUEST: 3) ata0-0: PCHS=14010/16/63 translation=lba 
> LCHS=879/255/63
> (XEN) (GUEST: 3) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk 
> (6896 MBytes)
> (XEN) (GUEST: 3) ata0  slave: Unknown device
> (XEN) (GUEST: 3) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
> (XEN) (GUEST: 3) ata1  slave: Unknown device
> (XEN) (GUEST: 3)
> (XEN) (GUEST: 3) Booting from CD-Rom...
> (XEN) (GUEST: 3) unsupported PCI BIOS function 0x0E
> (XEN) (GUEST: 3) int13_harddisk: function 15, unmapped device 
> for ELDL=81
> (XEN) (GUEST: 4) HVM Loader
> (XEN) (GUEST: 4) Detected Xen v3.0.3-1
> (XEN) (GUEST: 4) Writing SMBIOS tables ...
> (XEN) (GUEST: 4) Loading ROMBIOS ...
> (XEN) (GUEST: 4) Loading Cirrus VGABIOS ...
> (XEN) (GUEST: 4) SVM go ...
> (XEN) (GUEST: 4)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
> (XEN) (GUEST: 4) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 
> vruppert Exp $
> (XEN) (GUEST: 4) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 
> 2005/05/07 15:55:26 $
> (XEN) (GUEST: 4)
> (XEN) (GUEST: 4) ata0-0: PCHS=16383/16/63 translation=lba 
> LCHS=1024/255/63
> (XEN) (GUEST: 4) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk 
> (19092 MBytes)
> (XEN) (GUEST: 4) ata0  slave: Unknown device
> (XEN) (GUEST: 4) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
> (XEN) (GUEST: 4) ata1  slave: Unknown device
> (XEN) (GUEST: 4)
> (XEN) (GUEST: 4) Booting from CD-Rom...
> (XEN) (GUEST: 4) unsupported PCI BIOS function 0x0E
> (XEN) (GUEST: 4) int13_harddisk: function 15, unmapped device 
> for ELDL=81
> (XEN) (GUEST: 5) HVM Loader
> (XEN) (GUEST: 5) Detected Xen v3.0.3-1
> (XEN) (GUEST: 5) Writing SMBIOS tables ...
> (XEN) (GUEST: 5) Loading ROMBIOS ...
> (XEN) (GUEST: 5) Loading Cirrus VGABIOS ...
> (XEN) (GUEST: 5) SVM go ...
> (XEN) (GUEST: 5)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
> (XEN) (GUEST: 5) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 
> vruppert Exp $
> (XEN) (GUEST: 5) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 
> 2005/05/07 15:55:26 $
> (XEN) (GUEST: 5)
> (XEN) (GUEST: 5) ata0-0: PCHS=16383/16/63 translation=lba 
> LCHS=1024/255/63
> (XEN) (GUEST: 5) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk 
> (19092 MBytes)
> (XEN) (GUEST: 5) ata0  slave: Unknown device
> (XEN) (GUEST: 5) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
> (XEN) (GUEST: 5) ata1  slave: Unknown device
> (XEN) (GUEST: 5)
> (XEN) (GUEST: 5) Booting from CD-Rom...
> (XEN) (GUEST: 5) unsupported PCI BIOS function 0x0E
> (XEN) (GUEST: 5) int13_harddisk: function 15, unmapped device 
> for ELDL=81
> (XEN) (GUEST: 6) HVM Loader
> (XEN) (GUEST: 6) Detected Xen v3.0.3-1
> (XEN) (GUEST: 6) Writing SMBIOS tables ...
> (XEN) (GUEST: 6) Loading ROMBIOS ...
> (XEN) (GUEST: 6) Loading Cirrus VGABIOS ...
> (XEN) (GUEST: 6) SVM go ...
> (XEN) (GUEST: 6)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
> (XEN) (GUEST: 6) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 
> vruppert Exp $
> (XEN) (GUEST: 6) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 
> 2005/05/07 15:55:26 $
> (XEN) (GUEST: 6)
> (XEN) (GUEST: 6) ata0-0: PCHS=16383/16/63 translation=lba 
> LCHS=1024/255/63
> (XEN) (GUEST: 6) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk 
> (19092 MBytes)
> (XEN) (GUEST: 6) ata0  slave: Unknown device
> (XEN) (GUEST: 6) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
> (XEN) (GUEST: 6) ata1  slave: Unknown device
> (XEN) (GUEST: 6)
> (XEN) (GUEST: 6) Booting from CD-Rom...
> (XEN) (GUEST: 6) unsupported PCI BIOS function 0x0E
> (XEN) (GUEST: 6) int13_harddisk: function 15, unmapped device 
> for ELDL=81
> ===================================================================
> 
> 
> The last lines of "dmesg" (having to do with the usb hd) also are:
> ===================================================================
> usb-storage: device scan complete
> SCSI device sda: 39102336 512-byte hdwr sectors (20020 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 38 00 00
> sda: assuming drive cache: write through
> SCSI device sda: 39102336 512-byte hdwr sectors (20020 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 38 00 00
> sda: assuming drive cache: write through
> sda: sda1 sda2 sda4
> sd 2:0:0:0: Attached scsi disk sda
> NTFS driver 2.1.27 [Flags: R/W MODULE].
> NTFS-fs error (device sda1): read_ntfs_boot_sector(): Primary boot 
> sector is invalid.
> NTFS-fs error (device sda1): read_ntfs_boot_sector(): Mount option 
> errors=recover not used. Aborting without trying to recover.
> NTFS-fs error (device sda1): ntfs_fill_super(): Not an NTFS volume.
> ===================================================================
> 
> 
> What is going wrong? Please help.
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 
> 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

__________ Informace od NOD32 2181 (20070411) __________

Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>