Hello, When I install Windows XP I get missing files. The windows installed can''t see C drive, only A:\ and "GLOBALROOT\DEVICE\CDROM0\I386" Will this be fixed in snv88? # uname -srv SunOS 5.11 snv_87 # isainfo amd64 i386 # xm dmesg xVM version 3.1.2-xvm (xVM) Command line: (xVM) Video information: (xVM) VGA is text mode 80x25, font 8x16 (xVM) VBE/DDC methods: V2; EDID transfer time: 1 seconds (xVM) Disc information: (xVM) Found 1 MBR signatures (xVM) Found 1 EDD information structures (xVM) Xen-e820 RAM map: (xVM) 0000000000000000 - 000000000009d000 (usable) (xVM) 000000000009dc00 - 00000000000a0000 (reserved) (xVM) 00000000000dc000 - 00000000000e0000 (reserved) (xVM) 00000000000e4000 - 0000000000100000 (reserved) (xVM) 0000000000100000 - 000000003fe40000 (usable) (xVM) 000000003fe40000 - 000000003fe54000 (ACPI data) (xVM) 000000003fe54000 - 000000003fe55000 (ACPI NVS) (xVM) 000000003fe55000 - 0000000040000000 (reserved) (xVM) 00000000f0000000 - 00000000f8000000 (reserved) (xVM) 00000000fec00000 - 00000000fec10000 (reserved) (xVM) 00000000fee00000 - 00000000fee01000 (reserved) (xVM) 00000000ff000000 - 0000000100000000 (reserved) (xVM) System RAM: 1021MB (1046388kB) (xVM) Xen heap: 14MB (14836kB) (xVM) Domain heap initialised: DMA width 32 bits (xVM) Processor #0 6:15 APIC version 20 (xVM) Processor #1 6:15 APIC version 20 (xVM) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 (xVM) Enabling APIC mode: Flat. Using 1 I/O APICs (xVM) Using scheduler: SMP Credit Scheduler (credit) (xVM) Detected 2327.520 MHz processor. (xVM) HVM: VMX enabled (xVM) VMX: MSR intercept bitmap enabled (xVM) CPU0: Intel(R) Xeon(R) CPU 3065 @ 2.33GHz stepping 0b (xVM) Mapping cpu 0 to node 255 (xVM) Booting processor 1/1 eip 90000 (xVM) Mapping cpu 1 to node 255 (xVM) CPU1: Intel(R) Xeon(R) CPU 3065 @ 2.33GHz stepping 0b (xVM) Total of 2 processors activated. (xVM) ENABLING IO-APIC IRQs (xVM) -> Using new ACK method (xVM) Platform timer overflows in 234 jiffies. (xVM) Platform timer is 3.579MHz ACPI PM Timer (xVM) Brought up 2 CPUs (xVM) *** LOADING DOMAIN 0 *** (xVM) Xen kernel: 64-bit, lsb, compat32 (xVM) Dom0 kernel: 64-bit, lsb, paddr 0x40000000 -> 0x40825d78 (xVM) PHYSICAL MEMORY ARRANGEMENT: (xVM) Dom0 alloc.: 0000000038000000->000000003c000000 (221504 pages to be allocated) (xVM) VIRTUAL MEMORY ARRANGEMENT: (xVM) Loaded kernel: 0000000040000000->0000000040825d78 (xVM) Init. ramdisk: 0000000040826000->00000000423de000 (xVM) Phys-Mach map: 00000000423de000->00000000425aea00 (xVM) Start info: 00000000425af000->00000000425af49c (xVM) Page tables: 00000000425b0000->00000000425c7000 (xVM) Boot stack: 00000000425c7000->00000000425c8000 (xVM) TOTAL: 0000000040000000->0000000042800000 (xVM) ENTRY ADDRESS: 0000000040800000 (xVM) Dom0 has maximum 2 VCPUs (xVM) Initrd len 0x1bb8000, start at 0x40826000 (xVM) Scrubbing Free RAM: done. (xVM) Xen trace buffers: disabled (xVM) Std. Loglevel: Errors and warnings (xVM) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (xVM) Xen is relinquishing VGA console. (xVM) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). (xVM) Freed 132kB init memory. This message posted from opensolaris.org
Piotr Jasiukajtis wrote:> Hello, > > When I install Windows XP I get missing files. > The windows installed can''t see C drive, only A:\ and > "GLOBALROOT\DEVICE\CDROM0\I386" > > Will this be fixed in snv88?I don''t see this problem? How did you install the guest, virt-install? Are you saying that the Windows installer can''t find the CDROM? MRJ> # uname -srv > SunOS 5.11 snv_87 > > # isainfo > amd64 i386 > > # xm dmesg > xVM version 3.1.2-xvm > (xVM) Command line: > (xVM) Video information: > (xVM) VGA is text mode 80x25, font 8x16 > (xVM) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (xVM) Disc information: > (xVM) Found 1 MBR signatures > (xVM) Found 1 EDD information structures > (xVM) Xen-e820 RAM map: > (xVM) 0000000000000000 - 000000000009d000 (usable) > (xVM) 000000000009dc00 - 00000000000a0000 (reserved) > (xVM) 00000000000dc000 - 00000000000e0000 (reserved) > (xVM) 00000000000e4000 - 0000000000100000 (reserved) > (xVM) 0000000000100000 - 000000003fe40000 (usable) > (xVM) 000000003fe40000 - 000000003fe54000 (ACPI data) > (xVM) 000000003fe54000 - 000000003fe55000 (ACPI NVS) > (xVM) 000000003fe55000 - 0000000040000000 (reserved) > (xVM) 00000000f0000000 - 00000000f8000000 (reserved) > (xVM) 00000000fec00000 - 00000000fec10000 (reserved) > (xVM) 00000000fee00000 - 00000000fee01000 (reserved) > (xVM) 00000000ff000000 - 0000000100000000 (reserved) > (xVM) System RAM: 1021MB (1046388kB) > (xVM) Xen heap: 14MB (14836kB) > (xVM) Domain heap initialised: DMA width 32 bits > (xVM) Processor #0 6:15 APIC version 20 > (xVM) Processor #1 6:15 APIC version 20 > (xVM) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > (xVM) Enabling APIC mode: Flat. Using 1 I/O APICs > (xVM) Using scheduler: SMP Credit Scheduler (credit) > (xVM) Detected 2327.520 MHz processor. > (xVM) HVM: VMX enabled > (xVM) VMX: MSR intercept bitmap enabled > (xVM) CPU0: Intel(R) Xeon(R) CPU 3065 @ 2.33GHz stepping 0b > (xVM) Mapping cpu 0 to node 255 > (xVM) Booting processor 1/1 eip 90000 > (xVM) Mapping cpu 1 to node 255 > (xVM) CPU1: Intel(R) Xeon(R) CPU 3065 @ 2.33GHz stepping 0b > (xVM) Total of 2 processors activated. > (xVM) ENABLING IO-APIC IRQs > (xVM) -> Using new ACK method > (xVM) Platform timer overflows in 234 jiffies. > (xVM) Platform timer is 3.579MHz ACPI PM Timer > (xVM) Brought up 2 CPUs > (xVM) *** LOADING DOMAIN 0 *** > (xVM) Xen kernel: 64-bit, lsb, compat32 > (xVM) Dom0 kernel: 64-bit, lsb, paddr 0x40000000 -> 0x40825d78 > (xVM) PHYSICAL MEMORY ARRANGEMENT: > (xVM) Dom0 alloc.: 0000000038000000->000000003c000000 (221504 pages to be allocated) > (xVM) VIRTUAL MEMORY ARRANGEMENT: > (xVM) Loaded kernel: 0000000040000000->0000000040825d78 > (xVM) Init. ramdisk: 0000000040826000->00000000423de000 > (xVM) Phys-Mach map: 00000000423de000->00000000425aea00 > (xVM) Start info: 00000000425af000->00000000425af49c > (xVM) Page tables: 00000000425b0000->00000000425c7000 > (xVM) Boot stack: 00000000425c7000->00000000425c8000 > (xVM) TOTAL: 0000000040000000->0000000042800000 > (xVM) ENTRY ADDRESS: 0000000040800000 > (xVM) Dom0 has maximum 2 VCPUs > (xVM) Initrd len 0x1bb8000, start at 0x40826000 > (xVM) Scrubbing Free RAM: done. > (xVM) Xen trace buffers: disabled > (xVM) Std. Loglevel: Errors and warnings > (xVM) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (xVM) Xen is relinquishing VGA console. > (xVM) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). > (xVM) Freed 132kB init memory. > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
This is the same issue: http://www.opensolaris.org/jive/thread.jspa?messageID=199965&tstart=0 This message posted from opensolaris.org
Mark Johnson pisze:> > > Piotr Jasiukajtis wrote: >> Hello, >> >> When I install Windows XP I get missing files. >> The windows installed can''t see C drive, only A:\ and >> "GLOBALROOT\DEVICE\CDROM0\I386" >> >> Will this be fixed in snv88? > > I don''t see this problem? How did you install > the guest, virt-install?Yes, virt-install> > Are you saying that the Windows installer can''t > find the CDROM?I don''t know windows installer, but it seems that it can find only the floppy drive. This is the same issue: http://www.opensolaris.org/jive/thread.jspa?messageID=199965&tstart=0> > > > MRJ > > > > >> # uname -srv >> SunOS 5.11 snv_87 >> >> # isainfo amd64 i386 >> >> # xm dmesg >> xVM version 3.1.2-xvm >> (xVM) Command line: (xVM) Video information: >> (xVM) VGA is text mode 80x25, font 8x16 >> (xVM) VBE/DDC methods: V2; EDID transfer time: 1 seconds >> (xVM) Disc information: >> (xVM) Found 1 MBR signatures >> (xVM) Found 1 EDD information structures >> (xVM) Xen-e820 RAM map: >> (xVM) 0000000000000000 - 000000000009d000 (usable) >> (xVM) 000000000009dc00 - 00000000000a0000 (reserved) >> (xVM) 00000000000dc000 - 00000000000e0000 (reserved) >> (xVM) 00000000000e4000 - 0000000000100000 (reserved) >> (xVM) 0000000000100000 - 000000003fe40000 (usable) >> (xVM) 000000003fe40000 - 000000003fe54000 (ACPI data) >> (xVM) 000000003fe54000 - 000000003fe55000 (ACPI NVS) >> (xVM) 000000003fe55000 - 0000000040000000 (reserved) >> (xVM) 00000000f0000000 - 00000000f8000000 (reserved) >> (xVM) 00000000fec00000 - 00000000fec10000 (reserved) >> (xVM) 00000000fee00000 - 00000000fee01000 (reserved) >> (xVM) 00000000ff000000 - 0000000100000000 (reserved) >> (xVM) System RAM: 1021MB (1046388kB) >> (xVM) Xen heap: 14MB (14836kB) >> (xVM) Domain heap initialised: DMA width 32 bits >> (xVM) Processor #0 6:15 APIC version 20 >> (xVM) Processor #1 6:15 APIC version 20 >> (xVM) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 >> (xVM) Enabling APIC mode: Flat. Using 1 I/O APICs >> (xVM) Using scheduler: SMP Credit Scheduler (credit) >> (xVM) Detected 2327.520 MHz processor. >> (xVM) HVM: VMX enabled >> (xVM) VMX: MSR intercept bitmap enabled >> (xVM) CPU0: Intel(R) Xeon(R) CPU 3065 @ 2.33GHz stepping 0b >> (xVM) Mapping cpu 0 to node 255 >> (xVM) Booting processor 1/1 eip 90000 >> (xVM) Mapping cpu 1 to node 255 >> (xVM) CPU1: Intel(R) Xeon(R) CPU 3065 @ 2.33GHz stepping 0b >> (xVM) Total of 2 processors activated. >> (xVM) ENABLING IO-APIC IRQs >> (xVM) -> Using new ACK method >> (xVM) Platform timer overflows in 234 jiffies. >> (xVM) Platform timer is 3.579MHz ACPI PM Timer >> (xVM) Brought up 2 CPUs >> (xVM) *** LOADING DOMAIN 0 *** >> (xVM) Xen kernel: 64-bit, lsb, compat32 >> (xVM) Dom0 kernel: 64-bit, lsb, paddr 0x40000000 -> 0x40825d78 >> (xVM) PHYSICAL MEMORY ARRANGEMENT: >> (xVM) Dom0 alloc.: 0000000038000000->000000003c000000 (221504 pages >> to be allocated) >> (xVM) VIRTUAL MEMORY ARRANGEMENT: >> (xVM) Loaded kernel: 0000000040000000->0000000040825d78 >> (xVM) Init. ramdisk: 0000000040826000->00000000423de000 >> (xVM) Phys-Mach map: 00000000423de000->00000000425aea00 >> (xVM) Start info: 00000000425af000->00000000425af49c >> (xVM) Page tables: 00000000425b0000->00000000425c7000 >> (xVM) Boot stack: 00000000425c7000->00000000425c8000 >> (xVM) TOTAL: 0000000040000000->0000000042800000 >> (xVM) ENTRY ADDRESS: 0000000040800000 >> (xVM) Dom0 has maximum 2 VCPUs >> (xVM) Initrd len 0x1bb8000, start at 0x40826000 >> (xVM) Scrubbing Free RAM: done. >> (xVM) Xen trace buffers: disabled >> (xVM) Std. Loglevel: Errors and warnings >> (xVM) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) >> (xVM) Xen is relinquishing VGA console. >> (xVM) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch >> input to Xen). >> (xVM) Freed 132kB init memory. >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org
> This is the same issue: > http://www.opensolaris.org/jive/thread.jspa?messageID=199965&tstart=0> (One dialog form named "Files Needed" is shown with the following text: > The file ''asms'' on Windows XP Professional Service Pack 2 CD is needed.)Did you check the installation optical media on some other box? Is there a file or directory named "asms" in the subdirectory named "i386" on that media? I just checked my winxp sp2 media, and /I386/ASMS exists as a directory... This message posted from opensolaris.org
Jürgen Keil pisze:>> This is the same issue: >> http://www.opensolaris.org/jive/thread.jspa?messageID=199965&tstart=0 > >> (One dialog form named "Files Needed" is shown with the following text: >> The file ''asms'' on Windows XP Professional Service Pack 2 CD is needed.) > > Did you check the installation optical media on some other box? > Is there a file or directory named "asms" in the subdirectory named > "i386" on that media? > > I just checked my winxp sp2 media, and /I386/ASMS exists as > a directory...This is not a problem with CD/DVD media. I get similar error while installing Windows Server 2003. Some folks had the same issue with debiam (dom0) and WindowsXP (hvm domU)... Upgrade of the Xen (on debian) fixed the problem.
Piotr Jasiukajtis / estibi wrote:> Jürgen Keil pisze: >>> This is the same issue: >>> http://www.opensolaris.org/jive/thread.jspa?messageID=199965&tstart=0 >>> (One dialog form named "Files Needed" is shown with the following text: >>> The file ''asms'' on Windows XP Professional Service Pack 2 CD is needed.) >> Did you check the installation optical media on some other box? >> Is there a file or directory named "asms" in the subdirectory named >> "i386" on that media? >> >> I just checked my winxp sp2 media, and /I386/ASMS exists as >> a directory... > This is not a problem with CD/DVD media. > I get similar error while installing Windows Server 2003. > > Some folks had the same issue with debiam (dom0) and WindowsXP (hvm domU)... > Upgrade of the Xen (on debian) fixed the problem.Do you know what version of Xen they upgraded to? We just putback 3.1.4 to the xvm-gate last night, so it should show up in b89. We also have some xen unstable based bits that we were thinking of getting on the project site if folks are interested. There still some work to do to finish the port, but it seems to be functional. You would have to be able to build the xvm and onnv bits yourself to use it. MRJ
Mark Johnson pisze:> > > Piotr Jasiukajtis / estibi wrote: >> Jürgen Keil pisze: >>>> This is the same issue: >>>> http://www.opensolaris.org/jive/thread.jspa?messageID=199965&tstart=0 >>>> (One dialog form named "Files Needed" is shown with the following text: >>>> The file ''asms'' on Windows XP Professional Service Pack 2 CD is >>>> needed.) >>> Did you check the installation optical media on some other box? >>> Is there a file or directory named "asms" in the subdirectory named >>> "i386" on that media? >>> >>> I just checked my winxp sp2 media, and /I386/ASMS exists as >>> a directory... >> This is not a problem with CD/DVD media. >> I get similar error while installing Windows Server 2003. >> >> Some folks had the same issue with debiam (dom0) and WindowsXP (hvm >> domU)... >> Upgrade of the Xen (on debian) fixed the problem. > > > Do you know what version of Xen they upgraded to?I don''t know at this moment.>> We just putback 3.1.4 to the xvm-gate last night, > so it should show up in b89. > > > We also have some xen unstable based bits that > we were thinking of getting on the project site > if folks are interested. There still some work > to do to finish the port, but it seems to be > functional. You would have to be able to > build the xvm and onnv bits yourself to use it.I will try :) Anyway, virt-install don''t store CD/DVD settings to the configs. # cat /var/lib/xend/domains/fb96e8c9-940d-7e0a-12ef-f167a7f1102c/config.sxp (domain (domid 6) (vcpus_params ()) (PV_args ) (PV_bootloader ) (VCPUs_live 1) (actions_after_crash restart) (uuid fb96e8c9-940d-7e0a-12ef-f167a7f1102c) (PV_ramdisk ) (name_label wxpp01) (VCPUs_at_startup 1) (HVM_boot_params ((order c))) (platform ((device_model /usr/lib/xen/bin/qemu-dm) (keymap en-us) (boot c) (pae 1) (usb 1) ) ) (PV_kernel /usr/lib/xen/boot/hvmloader) (memory_static_min 0) (HVM_boot_policy ''BIOS order'') (VCPUs_max 1) (memory_static_max 268435456) (actions_after_shutdown destroy) (memory_dynamic_max 268435456) (is_a_template False) (memory_dynamic_min 268435456) (PV_bootloader_args ) (other_config ()) (actions_after_reboot restart) (on_crash restart) (uuid fb96e8c9-940d-7e0a-12ef-f167a7f1102c) (bootloader_args ) (vcpus 1) (name wxpp01) (on_poweroff destroy) (on_reboot restart) (bootloader ) (maxmem 256) (memory 256) (shadow_memory 3) (vcpu_avail 1) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop shutdown) (start_time 1209416034.2) (cpu_time 17.230961995) (online_vcpus 1) (image (hvm (kernel /usr/lib/xen/boot/hvmloader) (boot c) (device_model /usr/lib/xen/bin/qemu-dm) (keymap en-us) (pae 1) (usb 1) (notes (SUSPEND_CANCEL 1)) ) ) (status 1) (state ------) (store_mfn 65534) (device (vif (mac 00:16:3e:67:ad:6e) (script vif-vnic) (uuid 2dd2515b-d73a-f6bb-51f0-fef69d572dd3) (backend 0) ) ) (device (vbd (uname file:/export/xen/wxpp01/disk) (uuid ad50c92b-a9c2-a664-ede6-22b6c1a5713b) (mode w) (dev hda:disk) (backend 0) (bootable 1) ) ) (device (vkbd (backend 0))) (device (vfb (vncunused 1) (type vnc) (uuid e629021d-cb53-11ca-a5f1-7d4e1cd41009) (location localhost:5900) ) ) (device (console (protocol vt100) (location 3) (uuid 488e3509-07ec-9487-e067-96af10a88bdd) ) ) ) # xm list Name ID Mem VCPUs State Time(s) 2003std01 300 1 15.3 Domain-0 0 677 2 r----- 992.8 fbsd7 128 1 0.0 milax 11 256 1 r----- 463.5 rescue 128 1 0.0 wxpp01 256 1 8.6 # virsh dumpxml wxpp01 <domain type=''xen'' id=''-1''> <name>wxpp01</name> <uuid>fb96e8c9-940d-7e0a-12ef-f167a7f1102c</uuid> <os> <type>hvm</type> <loader>/usr/lib/xen/boot/hvmloader</loader> <boot dev=''hd''/> </os> <memory>262144</memory> <vcpu>1</vcpu> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <features> <pae/> </features> <clock offset=''utc''/> <devices> <emulator>/usr/lib/xen/bin/qemu-dm</emulator> <interface type=''ethernet''> <target dev=''vif-1.0''/> <mac address=''00:16:3e:67:ad:6e''/> </interface> <disk type=''file'' device=''disk''> <driver name=''file''/> <source file=''/export/xen/wxpp01/disk''/> <target dev=''hda''/> </disk> <input type=''mouse'' bus=''ps2''/> <graphics type=''vnc'' port=''-1''/> </devices> </domain>
Piotr Jasiukajtis / estibi wrote:> Mark Johnson pisze: >>> Some folks had the same issue with debiam (dom0) and WindowsXP (hvm >>> domU)... >>> Upgrade of the Xen (on debian) fixed the problem. >> >> Do you know what version of Xen they upgraded to? > I don''t know at this moment.>Just read a couple windows threads (non xen related) on the error. It appears that this can happen if the cdrom is too fast. Can you try using an actual cdrom/dvd vs an iso for the install? Thanks, MRJ>> We just putback 3.1.4 to the xvm-gate last night, >> so it should show up in b89. >> >> >> We also have some xen unstable based bits that >> we were thinking of getting on the project site >> if folks are interested. There still some work >> to do to finish the port, but it seems to be >> functional. You would have to be able to >> build the xvm and onnv bits yourself to use it. > I will try :) > > Anyway, virt-install don''t store CD/DVD settings to the configs. > > # cat /var/lib/xend/domains/fb96e8c9-940d-7e0a-12ef-f167a7f1102c/config.sxp > (domain > (domid 6) > (vcpus_params ()) > (PV_args ) > (PV_bootloader ) > (VCPUs_live 1) > (actions_after_crash restart) > (uuid fb96e8c9-940d-7e0a-12ef-f167a7f1102c) > (PV_ramdisk ) > (name_label wxpp01) > (VCPUs_at_startup 1) > (HVM_boot_params ((order c))) > (platform > ((device_model /usr/lib/xen/bin/qemu-dm) > (keymap en-us) > (boot c) > (pae 1) > (usb 1) > ) > ) > (PV_kernel /usr/lib/xen/boot/hvmloader) > (memory_static_min 0) > (HVM_boot_policy ''BIOS order'') > (VCPUs_max 1) > (memory_static_max 268435456) > (actions_after_shutdown destroy) > (memory_dynamic_max 268435456) > (is_a_template False) > (memory_dynamic_min 268435456) > (PV_bootloader_args ) > (other_config ()) > (actions_after_reboot restart) > (on_crash restart) > (uuid fb96e8c9-940d-7e0a-12ef-f167a7f1102c) > (bootloader_args ) > (vcpus 1) > (name wxpp01) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 256) > (memory 256) > (shadow_memory 3) > (vcpu_avail 1) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop shutdown) > (start_time 1209416034.2) > (cpu_time 17.230961995) > (online_vcpus 1) > (image > (hvm > (kernel /usr/lib/xen/boot/hvmloader) > (boot c) > (device_model /usr/lib/xen/bin/qemu-dm) > (keymap en-us) > (pae 1) > (usb 1) > (notes (SUSPEND_CANCEL 1)) > ) > ) > (status 1) > (state ------) > (store_mfn 65534) > (device > (vif > (mac 00:16:3e:67:ad:6e) > (script vif-vnic) > (uuid 2dd2515b-d73a-f6bb-51f0-fef69d572dd3) > (backend 0) > ) > ) > (device > (vbd > (uname file:/export/xen/wxpp01/disk) > (uuid ad50c92b-a9c2-a664-ede6-22b6c1a5713b) > (mode w) > (dev hda:disk) > (backend 0) > (bootable 1) > ) > ) > (device (vkbd (backend 0))) > (device > (vfb > (vncunused 1) > (type vnc) > (uuid e629021d-cb53-11ca-a5f1-7d4e1cd41009) > (location localhost:5900) > ) > ) > (device > (console > (protocol vt100) > (location 3) > (uuid 488e3509-07ec-9487-e067-96af10a88bdd) > ) > ) > ) > > > > # xm list > Name ID Mem VCPUs State Time(s) > 2003std01 300 1 15.3 > Domain-0 0 677 2 r----- 992.8 > fbsd7 128 1 0.0 > milax 11 256 1 r----- 463.5 > rescue 128 1 0.0 > wxpp01 256 1 8.6 > > # virsh dumpxml wxpp01 > <domain type=''xen'' id=''-1''> > <name>wxpp01</name> > <uuid>fb96e8c9-940d-7e0a-12ef-f167a7f1102c</uuid> > <os> > <type>hvm</type> > <loader>/usr/lib/xen/boot/hvmloader</loader> > <boot dev=''hd''/> > </os> > <memory>262144</memory> > <vcpu>1</vcpu> > <on_poweroff>destroy</on_poweroff> > <on_reboot>restart</on_reboot> > <on_crash>restart</on_crash> > <features> > <pae/> > </features> > <clock offset=''utc''/> > <devices> > <emulator>/usr/lib/xen/bin/qemu-dm</emulator> > <interface type=''ethernet''> > <target dev=''vif-1.0''/> > <mac address=''00:16:3e:67:ad:6e''/> > </interface> > <disk type=''file'' device=''disk''> > <driver name=''file''/> > <source file=''/export/xen/wxpp01/disk''/> > <target dev=''hda''/> > </disk> > <input type=''mouse'' bus=''ps2''/> > <graphics type=''vnc'' port=''-1''/> > </devices> > </domain> > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
> Jürgen Keil pisze: > >> This is the same issue: > >> http://www.opensolaris.org/jive/thread.jspa?messageID=199965&tstart=0 > > > >> (One dialog form named "Files Needed" is shown with the following text: > >> The file 'asms' on Windows XP Professional Service Pack 2 CD is needed.) > > > > Did you check the installation optical media on some other box? > > Is there a file or directory named "asms" in the subdirectory named > > "i386" on that media? > > > > I just checked my winxp sp2 media, and /I386/ASMS exists as > > a directory... > This is not a problem with CD/DVD media. > I get similar error while installing Windows Server 2003.That is, if you use the same media on a real computer ("on metal"), you don't get the error about the missing "...\i386\asms" file? Hmm, microsoft has a knowledge base article about such a problem: http://support.microsoft.com/?scid=kb%3Ben-us%3B311755&x=11&y=12 According to that article "the Setup program cannot communicate with the CD-ROM drive". (Well, so far the virtual cdrom drive hardware in a xvm hvm environment worked fine for me, I didn't encounter that "asms" file missing problem...) Google finds lots of pages discussing this problem, too. E.g. http://www.nocrash.com/ncbbs/msgs/1075.shtml http://www.jsifaq.com/SF/Tips/Tip.aspx?id=4639 http://windowsitpro.com/article/articleid/75946/jsi-tip-4639-you-are-prompted-for-the-asms-file-when-installing-windows-xp.html http://osdir.com/ml/linux.redhat.fedora.xen/2007/msg01018.html> Some folks had the same issue with debiam (dom0) and > WindowsXP (hvm domU)... > Upgrade of the Xen (on debian) fixed the problem.This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org
Mark Johnson pisze:> > > Piotr Jasiukajtis / estibi wrote: >> Mark Johnson pisze: >>>> Some folks had the same issue with debiam (dom0) and WindowsXP (hvm >>>> domU)... >>>> Upgrade of the Xen (on debian) fixed the problem. >>> >>> Do you know what version of Xen they upgraded to? >> I don''t know at this moment.> > > Just read a couple windows threads (non xen related) > on the error. It appears that this can happen if the > cdrom is too fast. > > Can you try using an actual cdrom/dvd vs an iso > for the install?I have just added cdrom bits to the config and now it works! :) # virsh define wxpp01-my.xml Domain wxpp01 defined from wxpp01-my.xml # virsh dumpxml wxpp01 <domain type=''xen'' id=''-1''> <name>wxpp01</name> <uuid>fb96e8c9-940d-7e0a-12ef-f167a7f1102c</uuid> <os> <type>hvm</type> <loader>/usr/lib/xen/boot/hvmloader</loader> <boot dev=''hd''/> </os> <memory>262144</memory> <vcpu>1</vcpu> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <features> <pae/> </features> <clock offset=''utc''/> <devices> <emulator>/usr/lib/xen/bin/qemu-dm</emulator> <interface type=''ethernet''> <target dev=''vif-1.0''/> <mac address=''00:16:3e:67:ad:6e''/> </interface> <disk type=''file'' device=''disk''> <driver name=''file''/> <source file=''/export/xen/wxpp01/disk''/> <target dev=''hda''/> </disk> <disk type=''file'' device=''cdrom''> <driver name=''file''/> <source file=''/export/xen/en_winxp_pro_with_sp2.iso''/> <target dev=''hdc''/> <readonly/> </disk> <input type=''mouse'' bus=''ps2''/> <graphics type=''vnc'' port=''-1''/> </devices> </domain> # xm start wxpp01