Hi Team,
Hoping someone can help. I''ve had success SXDE 01/08 and Windows XP in
a Domain (domU) on an Ultra 40 M2. However, Windows 2003 is kicking-out during
the install, every time. After I issue "xm create ./win2k3.hvm" I get
a message "Started domain Windows 2003". When I connect to the
console via vncviewer I see:
"
Usage: fat32.exe [-wl]
-wl - Without LFN support
.....
Error. USB Driver not installed.
Not FAT32 Volumes Found, Exiting ....
.....
[DR-DOS] A:\>
"
Here''s some data on my setup and the configuration file:
bash-3.2# uname -a
SunOS sundemo 5.11 snv_79a i86pc i386 i86xpv
bash-3.2# psrinfo -vp
The physical processor has 1 virtual processor (0)
x86 (AuthenticAMD 40F13 family 15 model 65 step 3 clock 3000 MHz)
Dual-Core AMD Opteron(tm) Processor 2222
The physical processor has 1 virtual processor (1)
x86 (AuthenticAMD 40F13 family 15 model 65 step 3 clock 3000 MHz)
Dual-Core AMD Opteron(tm) Processor 2222
The physical processor has 1 virtual processor (2)
x86 (AuthenticAMD 40F13 family 15 model 65 step 3 clock 3000 MHz)
Dual-Core AMD Opteron(tm) Processor 2222
The physical processor has 1 virtual processor (3)
x86 (AuthenticAMD 40F13 family 15 model 65 step 3 clock 3000 MHz)
Dual-Core AMD Opteron(tm) Processor 2222
bash-3.2# cat win2k3.hvm
disk = [ ''file:/zfs/boot/win2k3/disk.raw,hdc,w'',
''file:/zfs/isofiles/W2K3-SP1-STD.iso,hda:cdrom,r'' ]
memory = 640
name = "Windows2003"
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
vif = [ ''mac= 0:14:4f:c3:26:15, bridge=nge1'' ]
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''preserve''
boot=''d''
vnc=1
vnclisten="0.0.0.0"
vncpasswd=''sun123''
serial=''null''
apic=0
usb=1
usbdevice="tablet"
device_model = ''/usr/lib/xen/bin/qemu-dm''
bash-3.2#
THOUGHTS?
Thanks.
This message posted from opensolaris.org
On 6 May 2008, at 3:17pm, Jason Doyle wrote:> disk = [ ''file:/zfs/boot/win2k3/disk.raw,hdc,w'', > ''file:/zfs/isofiles/W2K3-SP1-STD.iso,hda:cdrom,r'' ]I''ve never tried to install 2003, but it''s novel that you have your disk as drive 2 and CD as drive 0. Did you try with them the other way around?
I followed what''s documented here: http://www.opensolaris.org/os/community/xen/docs/windows.guest.html, and it worked for my XP guest. I should also mention that i created the drive using ... # qemu-img create -f raw /zfs/boot/win2k3/root.raw 15G After I initiate "xm create ....", when I open vncviewer I see .... +++++++++++++++++++++++++++++++++++ HVMAssist BIOS, 1 cpu, .... ata0 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom ata0 slave: Unknown device ata1 master: QEMU HARDDISK ATA-7 Hard-Disk (15360 MBytes) ata1 slave: unknown device Booting from CD-Rom ... Starting Caldera DR-DOS .... ....... +++++++++++++++++++++++++++++++++++++ Soon after, I get the error about NTFS ... This message posted from opensolaris.org
> Hi Team, > > Hoping someone can help. I''ve had success SXDE 01/08 > and Windows XP in a Domain (domU) on an Ultra 40 M2. > However, Windows 2003 is kicking-out during the > install, every time. After I issue "xm create > ./win2k3.hvm" I get a message "Started domain > Windows 2003". When I connect to the console via > vncviewer I see: > > Usage: fat32.exe [-wl] > -wl - Without LFN support > > Error. USB Driver not installed. > > Not FAT32 Volumes Found, Exiting .... > ..... > [DR-DOS] A:\> > " > Here''s some data on my setup and the configuration > file: > > bash-3.2# uname -a > SunOS sundemo 5.11 snv_79a i86pc i386 i86xpv > bash-3.2# psrinfo -vp > The physical processor has 1 virtual processor (0) > x86 (AuthenticAMD 40F13 family 15 model 65 step 3 > clock 3000 MHz) > Dual-Core AMD Opteron(tm) Processor 2222 > ical processor has 1 virtual processor (1) > x86 (AuthenticAMD 40F13 family 15 model 65 step 3 > clock 3000 MHz) > Dual-Core AMD Opteron(tm) Processor 2222 > ical processor has 1 virtual processor (2) > x86 (AuthenticAMD 40F13 family 15 model 65 step 3 > clock 3000 MHz) > Dual-Core AMD Opteron(tm) Processor 2222 > ical processor has 1 virtual processor (3) > x86 (AuthenticAMD 40F13 family 15 model 65 step 3 > clock 3000 MHz) > Dual-Core AMD Opteron(tm) Processor 2222 > # cat win2k3.hvm > disk = [ ''file:/zfs/boot/win2k3/disk.raw,hdc,w'', > ''file:/zfs/isofiles/W2K3-SP1-STD.iso,hda:cdrom,r'' > ]This notation (devices) is for Linux Dom0 and even for linux it''s not correct. hda and hdc are swapped. Solaris Dom0 won''t understand it at all . Actually, two options are available:- 1. Right disk notation:- disk = [''file:/zfs/isofiles/W2K3-SP1-STD.iso,6:cdrom,r'',''file:/zfs/boot/win2k3/disk.raw,0,w''] 2. Virt-install:- # virt-install -n Winds --hvm -r 1024 --vnc -f /second_root/dsk/win2003-dsk \ -s 10 -c /export/home/ISO/win2003.iso works fine through my experience specially to W2K3.> > memory = 640 > name = "Windows2003" > kernel = "/usr/lib/xen/boot/hvmloader" > builder=''hvm'' > vif = [ ''mac= 0:14:4f:c3:26:15, bridge=nge1'' ] > > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''preserve'' > > boot=''d'' > vnc=1 > vnclisten="0.0.0.0" > vncpasswd=''sun123'' > serial=''null'' > apic=0 > usb=1 > usbdevice="tablet" > > device_model = ''/usr/lib/xen/bin/qemu-dm'' > bash-3.2# > > THOUGHTS? > Thanks.This message posted from opensolaris.org
> This notation (devices) is for Linux Dom0 and even > for linux it''s not correct. hda and hdc are swapped. > Solaris Dom0 won''t understand it at all . > Actually, two options are available:- > 1. Right disk notation:- > disk = [''file:/zfs/isofiles/W2K3-SP1-STD.iso,6:cdrom,r'',''file:/zfs/boot/win2k3/disk.raw,0,w'']For a windows hvm guest domain the syntax should be OK. I''m using the same "hda" / "hdc" guest device names for win2003, but have the hdd and cdrom swapped: hdd -> "hda" and cdrom image "hdc:cdrom" disk = [ ''phy:/dev/zvol/dsk/files2/xen-win2003,hda,w'' , ''file:/files2/media/Win2003S_R2SP2_32_DE_1.iso,hdc:cdrom,r'' ] This message posted from opensolaris.org
Before running virt-install:- # dladm show-link LINK STATE SPEED DUPLEX your_nick up 100Mb full Next:- # svccfg -s xvm/xend setprop config/vncpasswd = astring: \"secret\" # svccfg -s xvm/xend setprop config/vnc-listen = astring: \"0.0.0.0\" # svccfg -s xvm/xend setprop config/default-nic="your_nick" # svcadm refresh xvm/xend # svcadm restart xvm/xend Make sure xend is ready for virt-install run :- # svccfg -s xend listprop This message posted from opensolaris.org
Yes, my first suggestion was wrong , too much Solaris HVM installs :-) Numbers (as devices) work for Solaris DomUs. This message posted from opensolaris.org
Still no luck:
1) I updated my config file with a new disk entry
bash-3.2# head win2k3.hvm
disk = [ ''file:/zfs/boot/win2k3/root.raw,hda,w'',
''file:/zfs/isofiles/W2K3-SP1-STD.iso,hdc:cdrom,r'' ]
2) I checked my services, the properties and then used virt-install instead -
same error.
bash-3.2# svcs -a | grep xvm
online 9:00:31 svc:/system/xvm/store:default
online 9:00:37 svc:/system/xvm/domains:default
online 13:44:30 svc:/system/xvm/xend:default
online 13:44:30 svc:/system/xvm/console:default
bash-3.2# svccfg -s xend listprop
config application
config/dom0-cpus integer 0
config/dom0-min-mem integer 196
config/enable-dump boolean true
config/stability astring Unstable
config/xend-relocation-address astring 127.0.0.1
config/xend-relocation-hosts-allow astring ^localhost$
config/xend-relocation-server boolean true
config/xend-unix-server boolean true
config/vncpasswd astring sun123
config/vnc-listen astring nge0
config/default-nic astring nge0
xenstored dependency
xenstored/entities fmri svc:/system/xvm/store
xenstored/grouping astring require_all
xenstored/restart_on astring restart
xenstored/type astring service
general framework
general/entity_stability astring Unstable
general/single_instance boolean true
start method
start/exec astring "/lib/svc/method/xend %m"
start/timeout_seconds count 0
start/type astring method
stop method
stop/exec astring :kill
stop/timeout_seconds count 60
stop/type astring method
tm_common_name template
tm_common_name/C ustring "Hypervisor Control
Daemon"
tm_man_xend template
tm_man_xend/manpath astring /usr/share/man
tm_man_xend/section astring 1M
tm_man_xend/title astring xend
bash-3.2# virt-install -n Windows2003 --hvm -r 640 --vnc -f
/zfs/boot/win2k3/root.raw \> -s 15 -c /zfs/isofiles/W2K3-SP1-STD.iso
Starting install...
Creating storage file... 100% |=========================| 15 GB 00:00
Creating domain... 0 B 00:00
VNC Viewer Free Edition 4.1.2 for X - built Nov 20 2007 00:39:59
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Tue May 6 14:02:11 2008
CConn: connected to host 127.0.0.1 port 5900
CConnection: Server supports RFB protocol version 3.3
CConnection: Using RFB protocol version 3.3
This message posted from opensolaris.org
> Still no luck: > 1) I updated my config file with a new disk entry > bash-3.2# head win2k3.hvm > disk = [ ''file:/zfs/boot/win2k3/root.raw,hda,w'', > ''file:/zfs/isofiles/W2K3-SP1-STD.iso,hdc:cdrom,r'' > ] > > 2) I checked my services, the properties and then > used virt-install instead - same error. > > bash-3.2# svcs -a | grep xvm > online 9:00:31 > svc:/system/xvm/store:default > online 9:00:37 > svc:/system/xvm/domains:default > online 13:44:30 svc:/system/xvm/xend:default > online 13:44:30 > svc:/system/xvm/console:default > bash-3.2# svccfg -s xend listprop > config application > config/dom0-cpus integer 0 > config/dom0-min-mem integer 196 > config/enable-dump boolean true > config/stability astring > Unstable > onfig/xend-relocation-address astring > 127.0.0.1 > onfig/xend-relocation-hosts-allow astring > ^localhost$ > onfig/xend-relocation-server boolean true > config/xend-unix-server boolean true > config/vncpasswd astring sun123 > config/vnc-listen astring nge0 ??******************************************************* config/vnc-listen astring 0.0.0.0 *******************************************************> config/default-nic astring nge0 > xenstored dependency > xenstored/entities fmri > svc:/system/xvm/store > tored/grouping astring require_all > xenstored/restart_on astring restart > xenstored/type astring service > general framework > general/entity_stability astring > Unstable > eneral/single_instance boolean true > start method > start/exec astring > "/lib/svc/method/xend %m" > tart/timeout_seconds count 0 > start/type astring method > stop method > stop/exec astring :kill > stop/timeout_seconds count 60 > stop/type astring method > tm_common_name template > tm_common_name/C ustring > "Hypervisor Control Daemon" > m_man_xend template > tm_man_xend/manpath astring > /usr/share/man > m_man_xend/section astring 1M > tm_man_xend/title astring xend > > bash-3.2# virt-install -n Windows2003 --hvm -r 640 > --vnc -f /zfs/boot/win2k3/root.raw \ > > -s 15 -c /zfs/isofiles/W2K3-SP1-STD.iso > > > Starting install... > Creating storage file... 100% > |=========================| 15 GB 00:00 > Creating domain... > 0 B > 00:00 > > VNC Viewer Free Edition 4.1.2 for X - built Nov 20 > 2007 00:39:59 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > > Tue May 6 14:02:11 2008 > CConn: connected to host 127.0.0.1 port 5900 > CConnection: Server supports RFB protocol version > 3.3 > CConnection: Using RFB protocol version 3.3This message posted from opensolaris.org
I haven''t had a problem connecting to VNC after the domain starts. But I still made these changes and confirmed the same results ... bash-3.2# svccfg -s xvm/xend setprop config/vnc-listen = astring: \''0.0.0.0\'' bash-3.2# svcadm refresh xvm/xend; svcadm restart xvm/xend bash-3.2# svccfg -s xend listprop | grep vnc-listen config/vnc-listen astring ''0.0.0.0'' bash-3.2# On another note, I decided to point to my XP ISO file, which I know works, because I installed XP this AM. bash-3.2# virt-install -n Windows2003 --hvm -r 640 --vnc -f /zfs/boot/win2k3/root.raw -s 15 -c /zfs/isofiles/wxpvol_en.iso XP startup starts immediately. Perhaps I''ve got a problem with my image. -Jason This message posted from opensolaris.org
Instead of pointing to the image I loaded the media into the DVD drive and ran: bash-3.2# virt-install -n Windows2003 --hvm -r 640 --vnc -f /zfs/boot/win2k3/root.raw -s 15 -c /dev/dsk/c0t0d0s2 This works and W2K3 is happily installing. I would have checked this before but I read somewhere that I couldn''t use a CD/DVD drive (ISO only) and I was distracted by the NTFS errors ... thinking it was the QEMU HDD and not the media. Thanks for everyone''s responses! -Jason This message posted from opensolaris.org
> However, Windows 2003 is kicking-out during the > install, every time. After I issue "xm create > ./win2k3.hvm" I get a message "Started domain > Windows 2003". When I connect to the console via > vncviewer I see: > > Usage: fat32.exe [-wl] > -wl - Without LFN support > > Error. USB Driver not installed. > > Not FAT32 Volumes Found, Exiting .... > ..... > [DR-DOS] A:\> > "That (Caldera?) DR-DOS prompt seems strange, esp. for a Microsoft OS CD. Where did that W2K3-SP1-STD.iso image come from? Did you copy it from a known working Microsoft optical installation media to your HDD using "dd" ? According to the following thread from a linux forum, these fat32.exe usage messages / dr-dos prompts might be the result of a failed boot from an optical media media that was written using "Nero" when you use Nero''s "Burn bootable disk" function: http://ubuntuforums.org/showthread.php?t=351450 This message posted from opensolaris.org