Hi All,
I cannot get windows xp to install on my laptop with nevada 79. I have
tried virt-install and xm create using a config file, each gives a
different error. I have attached related log output for virt-install
and xm create.
Any help is greatly appreciated :-)
Thanks,
Christian
# virt-install -n winxp01 -r 256 -s 4 --hvm -f /etc/opt/xvm/winxp01.img
-c /etc/opt/xvm/winxp.iso --vnc
Starting install...
libvir: Xen Daemon error : POST operation failed: (xend.err )
Traceback (most recent call last):
File "/usr/bin/virt-install", line 657, in ?
main()
File "/usr/bin/virt-install", line 606, in main
dom = guest.start_install(conscb,progresscb)
File
"/export/builds/xvm_79/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 638, in start_install
File
"/export/builds/xvm_79/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 655, in _do_install
File "/usr/lib/python2.4/vendor-packages/libvirt.py", line 503, in
createLinux
if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'',
conn=self)
libvirt.libvirtError: virDomainCreateLinux() failed POST operation
failed: (xend.err )
# xm create winxp01.hvm
Using config file "./winxp01.hvm".
Error:
#
# cat winxp01.hvm
disk = [ ''file:/etc/opt/xvm/winxp01.img,hdc,w'',
''file:/etc/opt/xvm/winxp.iso,hda:cdrom,r'' ]
memory = 256
name = "winxp01"
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
vif = [ ''bridge=wpi0'' ]
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''preserve''
vnc=1
vncpasswd=''''
vnclisten="0.0.0.0"
boot=''c''
serial=''null''
usb=1
usbdevice="tablet"
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
#
On Sat, Dec 08, 2007 at 01:27:43PM +0000, Christian Smith wrote:> I cannot get windows xp to install on my laptop with nevada 79. I haveIf you run just ''virt-install'', does it ask you if you want to create a fully-virtualized domain? If not, then you either don''t have VT/SVM or the BIOS has disabled it. regards john
> Hi All, > > I cannot get windows xp to install on my laptop with > nevada 79. I have > tried virt-install and xm create using a config file, > each gives a > different error. I have attached related log output > for virt-install > and xm create. > > Any help is greatly appreciated :-)Please ,view thread :- http://www.opensolaris.org/jive/thread.jspa?threadID=45607&tstart=0 In particular , Christian Smith wrote on Nov 25, 2007 5:53 PM Hi Bill, I am assuming that you are using virt-install to create your windows XP VM. When you first run virt-install it mounts a cdrom drive on your VM (the iso you selected). When your VM restarts after windows initial text based install no cdrom is mounted, therefore it cannot find the files on the cd. A quick workaround to this is to run the intial install using virt-install, wait for windows to reboot and complain that it cannot find the files. Shut down your VM now and delete the domain using ''xm delete'' so that it no longer appears when you run ''xm list''. Now re-run the same virt-install command using the same disk image and iso location. Your VM will restart the windows setup where it left off but with the cdrom drive mounted. Hope that helps, -Christian> > Thanks, > Christian > > # virt-install -n winxp01 -r 256 -s 4 --hvm -f > /etc/opt/xvm/winxp01.img > -c /etc/opt/xvm/winxp.iso --vnc > > Starting install... > libvir: Xen Daemon error : POST operation failed: > (xend.err ) > Traceback (most recent call last): > File "/usr/bin/virt-install", line 657, in ? > main() > File "/usr/bin/virt-install", line 606, in main > dom = guest.start_install(conscb,progresscb) > le > "/export/builds/xvm_79/proto/install/usr/lib/python2.4 > /site-packages/virtinst/Guest.py", > line 638, in start_install > File > export/builds/xvm_79/proto/install/usr/lib/python2.4/s > ite-packages/virtinst/Guest.py", > line 655, in _do_install > File > "/usr/lib/python2.4/vendor-packages/libvirt.py", > line 503, in > reateLinux > if ret is None:raise > libvirtError(''virDomainCreateLinux() failed'', > onn=self) > libvirt.libvirtError: virDomainCreateLinux() failed > POST operation > failed: (xend.err )This message posted from opensolaris.org
Christian, What happened with your experience in WinXP HVM install ? It looked perfect on Nov 25, 2007 5:53 PM . Boris. This message posted from opensolaris.org
http://bderzhavets.blogspot.com/2007/11/windows-xp-hvm-at-sxde-76-dom0.html This message posted from opensolaris.org
> On Sat, Dec 08, 2007 at 01:27:43PM +0000, Christian > Smith wrote: > > > I cannot get windows xp to install on my laptop > with nevada 79. I have > > If you run just ''virt-install'', does it ask you if > you want to create a > fully-virtualized domain? > > If not, then you either don''t have VT/SVM or the BIOS > has disabled it.I believe "xm info|grep hvm " will give answer right away> > regards > john > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgThis message posted from opensolaris.org
Hi Boris, I unfortunately I was using different hardware (Ultra 20 M2) and a different build (nv77) then. I am now using build 79 on mylaptop which is a gateway mx6960 with an intel chipset (core 2duo). I have VT enabled in the bios: -bash-3.2# xm info | grep hvm xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 -bash-3.2# Not sure what else to do :-( Thanks for your time, Christian On Sat, 2007-12-08 at 13:28 -0800, Boris Derzhavets wrote:> Christian, > What happened with your experience in WinXP HVM install ? > It looked perfect on Nov 25, 2007 5:53 PM . > Boris. > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Hi All, I think I found the cause of the problem. My laptop has a ethernet and wireless adapter in it. The ethernet does not have a driver installed so is not usable. The wireless is an intel ipw3945 and is my primary interface. The domain creation seems to be failing because of the networking. When I remove the ''vif'' line from the .hvm file when using ''xm create <name>.hvm'' it works fine. Is it possible to use a wireless interface with xen? Thanks, Christian On Sun, 2007-12-09 at 12:50 +0000, Christian Smith wrote:> Hi Boris, > > I unfortunately I was using different hardware (Ultra 20 M2) and a > different build (nv77) then. I am now using build 79 on mylaptop which > is a gateway mx6960 with an intel chipset (core 2duo). I have VT > enabled in the bios: > > -bash-3.2# xm info | grep hvm > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p > hvm-3.0-x86_64 > -bash-3.2# > > Not sure what else to do :-( > > Thanks for your time, > Christian > > > On Sat, 2007-12-08 at 13:28 -0800, Boris Derzhavets wrote: > > Christian, > > What happened with your experience in WinXP HVM install ? > > It looked perfect on Nov 25, 2007 5:53 PM . > > Boris. > > > > > > This message posted from opensolaris.org > > _______________________________________________ > > xen-discuss mailing list > > xen-discuss@opensolaris.org > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Worked for me with nv77 and Windows XP SP2, but I''m using an Ultra-20 M2 (2.6GHz 1218, 2GB memory, 250GB HD, Quadro FX 1500) James On Dec 9, 2007, at 4:50 AM, Christian Smith wrote:> Hi Boris, > > I unfortunately I was using different hardware (Ultra 20 M2) and a > different build (nv77) then. I am now using build 79 on mylaptop > which > is a gateway mx6960 with an intel chipset (core 2duo). I have VT > enabled in the bios: > > -bash-3.2# xm info | grep hvm > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p > hvm-3.0-x86_64 > -bash-3.2# > > Not sure what else to do :-( > > Thanks for your time, > Christian > > > On Sat, 2007-12-08 at 13:28 -0800, Boris Derzhavets wrote: >> Christian, >> What happened with your experience in WinXP HVM install ? >> It looked perfect on Nov 25, 2007 5:53 PM . >> Boris. >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Christian Smith - Sun Microsystems - Dublin Ireland
2007-Dec-10 09:53 UTC
Re: nv79 windows xp install error
Hi James, The Ultra 20 worked fine for me. The problem im having is with my laptop. I have determined the problem to be with my network configuration. I have an intel ipw3945 wireless nic and a Marvell ethernet adapter. Neither seem to be compatible. I can create a VM using ''xm create'' fine providing I have no network configuration in there. Do you know a way I can bridge to my wireless nic? Thanks, Christian James Cornell wrote:> Worked for me with nv77 and Windows XP SP2, but I''m using an Ultra-20 > M2 (2.6GHz 1218, 2GB memory, 250GB HD, Quadro FX 1500) > > James > On Dec 9, 2007, at 4:50 AM, Christian Smith wrote: > >> Hi Boris, >> >> I unfortunately I was using different hardware (Ultra 20 M2) and a >> different build (nv77) then. I am now using build 79 on mylaptop which >> is a gateway mx6960 with an intel chipset (core 2duo). I have VT >> enabled in the bios: >> >> -bash-3.2# xm info | grep hvm >> xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p >> hvm-3.0-x86_64 >> -bash-3.2# >> >> Not sure what else to do :-( >> >> Thanks for your time, >> Christian >> >> >> On Sat, 2007-12-08 at 13:28 -0800, Boris Derzhavets wrote: >>> Christian, >>> What happened with your experience in WinXP HVM install ? >>> It looked perfect on Nov 25, 2007 5:53 PM . >>> Boris. >>> >>> >>> This message posted from opensolaris.org >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >
Marvell Yukon, you mean the one that uses Sky2 reverse engineered driver on linux? Maybe something''s a miss with the bridging, like missing functionality in the driver that xVM depends on. I believe SisKonnect has a 64-bit Solaris driver for it, have you tried it? I don''t think bridging wifi works with xVM yet. James On Dec 10, 2007, at 1:53 AM, Christian Smith - Sun Microsystems - Dublin Ireland wrote:> Hi James, > > The Ultra 20 worked fine for me. The problem im having is with my > laptop. I have determined the problem to be with my network > configuration. I have an intel ipw3945 wireless nic and a Marvell > ethernet adapter. Neither seem to be compatible. I can create a VM > using ''xm create'' fine providing I have no network configuration in > there. Do you know a way I can bridge to my wireless nic? > > Thanks, > Christian > > > James Cornell wrote: >> Worked for me with nv77 and Windows XP SP2, but I''m using an >> Ultra-20 M2 (2.6GHz 1218, 2GB memory, 250GB HD, Quadro FX 1500) >> >> James >> On Dec 9, 2007, at 4:50 AM, Christian Smith wrote: >> >>> Hi Boris, >>> >>> I unfortunately I was using different hardware (Ultra 20 M2) and a >>> different build (nv77) then. I am now using build 79 on mylaptop >>> which >>> is a gateway mx6960 with an intel chipset (core 2duo). I have VT >>> enabled in the bios: >>> >>> -bash-3.2# xm info | grep hvm >>> xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0- >>> x86_32p >>> hvm-3.0-x86_64 >>> -bash-3.2# >>> >>> Not sure what else to do :-( >>> >>> Thanks for your time, >>> Christian >>> >>> >>> On Sat, 2007-12-08 at 13:28 -0800, Boris Derzhavets wrote: >>>> Christian, >>>> What happened with your experience in WinXP HVM install ? >>>> It looked perfect on Nov 25, 2007 5:53 PM . >>>> Boris. >>>> >>>> >>>> This message posted from opensolaris.org >>>> _______________________________________________ >>>> xen-discuss mailing list >>>> xen-discuss@opensolaris.org >>> >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >> >
On 8 Dec 2007, at 13:27, Christian Smith wrote:> vif = [ ''bridge=wpi0'' ]This won''t work. The VNIC code disallows the use of a wireless NIC underneath. In testing, none of the wireless NICs I could try would allow the transmission of packets with a source MAC address other than that of the device itself. Given that this is the basic mechanism used to enable VNICs, this meant that guest domains were not able to successfully transmit packets (as they use a different MAC address from that of the underlying NIC). If we can figure out how to make wireless NICs "do the right thing" then we can remove the restriction from the VNIC code. dme.
Boris Derzhavets
2007-Dec-10 11:43 UTC
Marvell Yukon Driver (SK-9E22) for Solaris ( SNV 59 x64) 8.19.1.3
Marvell Yukon Driver (SK-9E22) for Solaris (x64) 8.19.1.3 installation procedure in Solaris Express (SNV 59) http://bderzhavets.blogspot.com/2007/04/procedure-to-make-work-sk-9e22-driver.html Not sure, it will work on Solaris xVM This message posted from opensolaris.org
Just in case ethernet is Marvell Yukon, I would try on Solaris xVM ******************************************************************* Marvell Yukon Driver (SK-9E22) for Solaris (x64) 8.19.1.3 installation procedure in Solaris Express (SNV 59) ******************************************************************* http://bderzhavets.blogspot.com/2007/04/procedure-to-make-work-sk-9e22-driver.html This message posted from opensolaris.org
Christian Smith - Sun Microsystems - Dublin Ireland
2007-Dec-10 16:56 UTC
Re: nv79 windows xp install error
Hi Boris, I have a Marvell Yukon 88E8038 ethernet adapter (vendor-id=11ab, device-id=4352). I have installed the YUKONXsolx driver and it works fine for ethernet but I still cannot use it when creating a virtual machine. I have just installed the sk-9e22 driver according to you directions and it is working fine for ethernet but I am still getting the same output in my log file when using virt-install to create a virtual machine :-( Is this ethernet adapter supported with xVM? Thanks again, Christian Boris Derzhavets wrote:> Just in case ethernet is Marvell Yukon, I would try on Solaris xVM > ******************************************************************* > Marvell Yukon Driver (SK-9E22) for Solaris (x64) 8.19.1.3 > installation procedure in Solaris Express (SNV 59) > ******************************************************************* > http://bderzhavets.blogspot.com/2007/04/procedure-to-make-work-sk-9e22-driver.html > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >
Christian Smith - Sun Microsystems - Dublin Ireland
2007-Dec-10 17:06 UTC
Re: nv79 windows xp install error
Hi Boris, Just an update. Iwas just reading on this blog that any NIC to be used with xVM must support the latest GLD version 3. (http://blogs.sun.com/yongsun/entry/install_windows_domu_for_xvm) When I run ''dladm show-link'' it shows my skge0 device as legacy and therefore not supported according to that blog. Are you using this type of adapter? If so how? Thanks, Christian Christian Smith - Sun Microsystems - Dublin Ireland wrote:> Hi Boris, > > I have a Marvell Yukon 88E8038 ethernet adapter (vendor-id=11ab, > device-id=4352). I have installed the YUKONXsolx driver and it works > fine for ethernet but I still cannot use it when creating a virtual > machine. I have just installed the sk-9e22 driver according to you > directions and it is working fine for ethernet but I am still getting > the same output in my log file when using virt-install to create a > virtual machine :-( > > Is this ethernet adapter supported with xVM? > > Thanks again, > Christian > > Boris Derzhavets wrote: >> Just in case ethernet is Marvell Yukon, I would try on Solaris xVM >> ******************************************************************* >> Marvell Yukon Driver (SK-9E22) for Solaris (x64) 8.19.1.3 >> installation procedure in Solaris Express (SNV 59) >> ******************************************************************* >> http://bderzhavets.blogspot.com/2007/04/procedure-to-make-work-sk-9e22-driver.html >> >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >> > > ------------------------------------------------------------------------ > > > [2007-12-08 13:23:48 xend 831] DEBUG (SrvDomainDir:196) Listing domains in state 2 > [2007-12-08 13:23:48 xend 831] DEBUG (SrvDomainDir:196) Listing domains in state halted > [2007-12-08 13:23:48 xend 831] DEBUG (SrvDomainDir:196) Listing domains in state 2 > [2007-12-08 13:23:48 xend 831] DEBUG (SrvDomainDir:196) Listing domains in state halted > [2007-12-08 13:23:48 xend.XendDomainInfo 831] DEBUG (XendDomainInfo:94) XendDomainInfo.create([''vm'', [''name'', ''winxp01''], [''memory'', ''256''], [''maxmem'', ''256''], [''vcpus'', ''1''], [''uuid'', ''ee05fc52-46dd-77db-a677-44a4cad79326''], [''on_poweroff'', ''destroy''], [''on_reboot'', ''destroy''], [''on_crash'', ''destroy''], [''image'', [''hvm'', [''kernel'', ''/usr/lib/xen/boot/hvmloader''], [''device_model'', ''/usr/lib/xen/bin/qemu-dm''], [''vcpus'', ''1''], [''boot'', ''d''], [''pae'', ''1''], [''vnc'', ''1''], [''vncunused'', ''1'']]], [''device'', [''vbd'', [''dev'', ''hda:disk''], [''uname'', ''file:/etc/opt/xvm/winxp01.img''], [''mode'', ''w'']]], [''device'', [''vbd'', [''dev'', ''hdc:cdrom''], [''uname'', ''file:/etc/opt/xvm/winxp.iso''], [''mode'', ''r'']]], [''device'', [''vif'', [''mac'', ''00:16:3e:07:a9:7e''], [''bridge'', ''''], [''type'', ''ioemu'']]]]) > [2007-12-08 13:23:48 xend.XendConfig 831] WARNING (XendConfig:612) Unconverted key: cpus > [2007-12-08 13:23:48 xend.XendDomainInfo 831] DEBUG (XendDomainInfo:1320) XendDomainInfo.constructDomain > [2007-12-08 13:23:48 xend.XendDomainInfo 831] DEBUG (XendDomainInfo:1366) XendDomainInfo.initDomain: 5 256 > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: boot, val: d > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: fda, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: fdb, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: soundhw, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: localtime, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: serial, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: std-vga, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: isa, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: vcpus, val: 1 > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: acpi, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: usb, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: usbdevice, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (image:401) args: k, val: None > [2007-12-08 13:23:48 xend 831] DEBUG (balloon:116) Balloon: 274020 KiB free; need 273408; done. > [2007-12-08 13:23:48 xend 831] INFO (image:129) buildDomain os=hvm dom=5 vcpus=1 > [2007-12-08 13:23:48 xend 831] DEBUG (image:351) domid = 5 > [2007-12-08 13:23:48 xend 831] DEBUG (image:352) image = /usr/lib/xen/boot/hvmloader > [2007-12-08 13:23:48 xend 831] DEBUG (image:353) store_evtchn = 2 > [2007-12-08 13:23:48 xend 831] DEBUG (image:354) memsize = 256 > [2007-12-08 13:23:48 xend 831] DEBUG (image:355) vcpus = 1 > [2007-12-08 13:23:48 xend 831] DEBUG (image:356) pae = 1 > [2007-12-08 13:23:48 xend 831] DEBUG (image:357) acpi = 0 > [2007-12-08 13:23:48 xend 831] DEBUG (image:358) apic = 0 > [2007-12-08 13:23:48 xend 831] DEBUG (image:535) hvm shutdown watch registered > [2007-12-08 13:23:48 xend 831] DEBUG (image:574) hvm reboot feature watch registered > [2007-12-08 13:23:48 xend.XendDomainInfo 831] INFO (XendDomainInfo:1230) createDevice: vbd : {''uname'': ''file:/etc/opt/xvm/winxp01.img'', ''driver'': ''paravirtualised'', ''mode'': ''w'', ''dev'': ''hda:disk'', ''uuid'': ''cc455d17-89fb-8122-d74f-02e2d3955001''} > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:116) DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''768'', ''device-type'': ''disk'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vbd/5/768''} to /local/domain/5/device/vbd/768. > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:118) DevController: writing {''domain'': ''winxp01'', ''frontend'': ''/local/domain/5/device/vbd/768'', ''uuid'': ''cc455d17-89fb-8122-d74f-02e2d3955001'', ''dev'': ''hda'', ''state'': ''1'', ''params'': ''/etc/opt/xvm/winxp01.img'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': ''5'', ''type'': ''file''} to /local/domain/0/backend/vbd/5/768. > [2007-12-08 13:23:48 xend.XendDomainInfo 831] INFO (XendDomainInfo:1230) createDevice: vbd : {''uname'': ''file:/etc/opt/xvm/winxp.iso'', ''driver'': ''paravirtualised'', ''mode'': ''r'', ''dev'': ''hdc:cdrom'', ''uuid'': ''e97f7eeb-7ba0-1a30-b663-3c6f2e5f2681''} > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:116) DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''5632'', ''device-type'': ''cdrom'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vbd/5/5632''} to /local/domain/5/device/vbd/5632. > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:118) DevController: writing {''domain'': ''winxp01'', ''frontend'': ''/local/domain/5/device/vbd/5632'', ''uuid'': ''e97f7eeb-7ba0-1a30-b663-3c6f2e5f2681'', ''dev'': ''hdc'', ''state'': ''1'', ''params'': ''/etc/opt/xvm/winxp.iso'', ''mode'': ''r'', ''online'': ''1'', ''frontend-id'': ''5'', ''type'': ''file''} to /local/domain/0/backend/vbd/5/5632. > [2007-12-08 13:23:48 xend.XendDomainInfo 831] INFO (XendDomainInfo:1230) createDevice: vif : {''bridge'': '''', ''mac'': ''00:16:3e:07:a9:7e'', ''type'': ''ioemu'', ''uuid'': ''418a747f-be2e-067d-19fb-52adaeb0cbe0''} > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:116) DevController: writing {''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/vif/5/0''} to /local/domain/5/device/vif/0. > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:118) DevController: writing {''domain'': ''winxp01'', ''handle'': ''0'', ''uuid'': ''418a747f-be2e-067d-19fb-52adaeb0cbe0'', ''script'': ''/usr/lib/xen/scripts/vif-vnic'', ''state'': ''1'', ''frontend'': ''/local/domain/5/device/vif/0'', ''mac'': ''00:16:3e:07:a9:7e'', ''online'': ''1'', ''frontend-id'': ''5'', ''type'': ''ioemu''} to /local/domain/0/backend/vif/5/0. > [2007-12-08 13:23:48 xend 831] INFO (image:503) spawning device models: /usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'', ''-d'', ''5'', ''-m'', ''256'', ''-boot'', ''d'', ''-vcpus'', ''1'', ''-domain-name'', ''winxp01'', ''-net'', ''nic,vlan=0,macaddr=00:16:3e:07:a9:7e,model=rtl8139'', ''-net'', ''tap,vlan=0,bridge='', ''-vncunused'', ''-vnclisten'', ''127.0.0.1''] > [2007-12-08 13:23:48 xend 831] INFO (image:507) device model pid: 1365 > [2007-12-08 13:23:48 xend.XendDomainInfo 831] DEBUG (XendDomainInfo:1750) Storing VM details: {''on_xend_stop'': ''shutdown'', ''shadow_memory'': ''3'', ''uuid'': ''ee05fc52-46dd-77db-a677-44a4cad79326'', ''name'': ''winxp01'', ''on_reboot'': ''destroy'', ''start_time'': ''1197120228.62'', ''on_poweroff'': ''destroy'', ''on_xend_start'': ''ignore'', ''on_crash'': ''destroy'', ''xend/restart_count'': ''0'', ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': ''256'', ''image'': ''(hvm (kernel /usr/lib/xen/boot/hvmloader) (vnc 1) (vncunused 1) (device_model /usr/lib/xen/bin/qemu-dm) (pae 1) (boot d) (vcpus 1))'', ''maxmem'': ''256''} > [2007-12-08 13:23:48 xend.XendDomainInfo 831] DEBUG (XendDomainInfo:757) Storing domain details: {''console/port'': ''3'', ''name'': ''winxp01'', ''console/limit'': ''1048576'', ''vm'': ''/vm/ee05fc52-46dd-77db-a677-44a4cad79326'', ''domid'': ''5'', ''cpu/0/availability'': ''online'', ''memory/target'': ''262144'', ''store/ring-ref'': ''65534'', ''store/port'': ''2''} > [2007-12-08 13:23:48 xend 831] DEBUG (XendDomain:431) Adding Domain: 5 > [2007-12-08 13:23:48 xend 831] DEBUG (image:561) hvm_shutdown fired, shutdown reason=None > [2007-12-08 13:23:48 xend 831] DEBUG (image:593) hvm_reboot_feature fired, module status=None > [2007-12-08 13:23:48 xend.XendDomainInfo 831] DEBUG (XendDomainInfo:824) XendDomainInfo.handleShutdownWatch > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:149) Waiting for devices vif. > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:154) Waiting for 0. > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:561) hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:561) hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:575) hotplugStatusCallback 2. > [2007-12-08 13:23:48 xend 831] DEBUG (DevController:549) destroyCallback /local/domain/5/device/vif/0. > [2007-12-08 13:23:58 xend 831] ERROR (SrvBase:88) Request wait_for_devices failed. > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85, in perform > File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomain.py", line 85, in op_wait_for_devices > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 518, in waitForDevices > File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", line 150, in waitForDevices > File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", line 165, in waitForDevice > File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", line 237, in destroyDevice > EnvironmentError > [2007-12-08 13:23:58 xend.XendDomainInfo 831] DEBUG (XendDomainInfo:1519) XendDomainInfo.destroy: domid=5 > [2007-12-08 13:23:58 xend.XendDomainInfo 831] DEBUG (XendDomainInfo:1527) XendDomainInfo.destroyDomain(5) > [2007-12-08 13:23:58 xend 831] DEBUG (image:547) hvm shutdown watch unregistered > [2007-12-08 13:23:58 xend 831] DEBUG (image:586) hvm reboot feature watch unregistered > [2007-12-08 13:23:58 xend 831] DEBUG (DevController:549) destroyCallback /local/domain/5/device/vif/0. > [2007-12-08 13:23:58 xend 831] DEBUG (DevController:557) destroyCallback /local/domain/5/device/vif/0 is destroyed > > > ------------------------------------------------------------------------ > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >
On 10 Dec 2007, at 16:56, Christian Smith - Sun Microsystems - Dublin Ireland wrote:> I have a Marvell Yukon 88E8038 ethernet adapter (vendor-id=11ab, > device-id=4352). I have installed the YUKONXsolx driver and it > works fine for ethernet but I still cannot use it when creating a > virtual machine. I have just installed the sk-9e22 driver > according to you directions and it is working fine for ethernet but > I am still getting the same output in my log file when using virt- > install to create a virtual machine :-( > > Is this ethernet adapter supported with xVM?From a quick look at the driver binary it seems to be a traditional monolithic DLPI driver. If that''s correct then it will not work with the VNIC driver used by xVM Server, as that requires the NIC to have a GLDv3 driver. dme.
Christian, something that might work is to dedicate one of your network adaptors to the guest domain. It would then not be usable by dom0, but it might let you see stuff working. If you use wpi0 for Solaris and skge0 for the guest domain, the configuration would be something like: vif= [''bridge=skge0,mac=00:a:b:c:d:e,script=vif-dedicated''] Where "00:a:b:c:d:e" is replaced with the actual MAC address of your SysKonnect device. dme.
Dave, >>vif= [''bridge=skge0,mac=00:a:b:c:d:e,script=vif-dedicated''] Interessting option - is it already documented? I did not read about this feature until now. Does it also work for para-virtualized DomUs? If I understand this correct, the network adapter used for the DomU (skge0 in the example) is than in exclusive use by the DomU. If this is the case it''s not necessary that the driver for the network adapter supports more than one mac address. And therefor, at least in theory, this should work with wifi adapter using GLDv3 driver also ? regards Bernd David Edmondson wrote:> Christian, something that might work is to dedicate one of your > network adaptors to the guest domain. It would then not be usable by > dom0, but it might let you see stuff working. > > If you use wpi0 for Solaris and skge0 for the guest domain, the > configuration would be something like: > > vif= [''bridge=skge0,mac=00:a:b:c:d:e,script=vif-dedicated''] > > Where "00:a:b:c:d:e" is replaced with the actual MAC address of your > SysKonnect device. > > dme. > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org > >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
Christian, That's why I wrote "Would try for Solaris xVM" Actually, I am a linux guy. I do have experience with compiling just say Atansic Ethernet Drivers with 2.6.18-xen kernel sources. Through my comprehension Xen Hypervisor on Linux is a kind of usual Linux Kernel having some additional features. Xen implementation on Solaris is something different. Sorry for wasting your time. I didn't know results when made a suggestion. Regardless Marvell Yukon is integrated on almost all ASUS P965, P35 boards (and not only ASUS) Solaris Nevada Builds still don’t recognize Marvell Yukon Ethernet. Any Linux with 2.6.18 (or higher) xen enabled or usual kernel will pick up Marvell Yukon in a second. Finally I've just plugged Realtek 8139 in PCI slot. What allows me painlessly reinstall SNV builds every month. It's not a problem to find expensive or inexpensive GLD3 version card and plug it in PCI slot , but NOT on laptop . Thanks. Boris This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org
Christian Smith - Sun Microsystems - Dublin Ireland
2007-Dec-11 09:13 UTC
Re: nv79 windows xp install error
Hi Boris, Not your fault, it was worth a try anyway :-) Thanks for your time. If I get this resolved ill post it. -Christian Boris Derzhavets wrote:> Christian, > That's why I wrote "Would try for Solaris xVM" > Actually, I am a linux guy. I do have experience with > compiling just say Atansic Ethernet Drivers with 2.6.18-xen kernel > sources. Through my comprehension Xen Hypervisor on Linux is a kind > of usual Linux Kernel having some additional features. > Xen implementation on Solaris is something different. Sorry for > wasting your time. I didn't know results when made a suggestion. > Regardless Marvell Yukon is integrated on almost all ASUS P965, P35 boards (and not only ASUS) Solaris Nevada Builds still don’t recognize Marvell Yukon Ethernet. Any Linux with 2.6.18 (or higher) xen enabled or usual kernel will pick up Marvell Yukon in a second. Finally I've just plugged Realtek 8139 in PCI slot. What allows me painlessly reinstall SNV builds every month. It's not a problem to find expensive or inexpensive GLD3 version card and plug it in PCI slot , but NOT on laptop . > Thanks. > Boris > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >_______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org
rge driver? It works out-of-the-box mostly, with Marvell Yukon NIC''s, if not, just a simple /usr/X11/bin/scanpci, and an update_drv -a -i "''pci,id''" I remember to have had a good exeprience with the skge driver, sure, but rge is included. Or are there Marvell Yukon GBE chipsets that are not supported by the rge driver? A This message posted from opensolaris.org
On 10 Dec 2007, at 21:24, Bernd Schemmer wrote:> >>vif= [''bridge=skge0,mac=00:a:b:c:d:e,script=vif-dedicated''] > > Interessting option - is it already documented? I did not read > about this feature until now.It''s not documented anywhere. Much of these internal workings are not documented anywhere other than the implementation (and sometimes not even there).> Does it also work for para-virtualized DomUs?If the device in question has a GLDv3 driver, then yes (but see 6592059, which means that it doesn''t work for wireless NICs). For Christian, it won''t work for a PV guest (or HVM with PV drivers), because his NICs are either wireless (wpi) or use a DLPI driver (skge). HVM domains access the NIC (or VNIC) using libdlpi whereas PV domains have a layered kernel driver (xnbo), which leads to this inconsistency.> If I understand this correct, the network adapter used for the DomU > (skge0 in the example) is than in exclusive use by the DomU. If > this is the case it''s not necessary that the driver for the network > adapter supports more than one mac address. And therefor, at least > in theory, this should work with wifi adapter using GLDv3 driver > also ?In principle, yes. See above. Note that 6592059 is currently low priority. If fixing this would help someone out we can do it relatively easily - the changes are understood. dme.
Hi,
>>>>Does it also work for para-virtualized DomUs?
>>If the device in question has a GLDv3 driver, then yes (but see
6592059, which means that it doesn''t work for wireless NICs).
I tested this with a para-virtualized DomU and it works (see below).
But it''s a little bit confusing that the dedicated adapter is still
visible in the Dom0 and that you can use ifconfig to reconfigure it
without getting an error. But the changes for the adapter in the Dom0
are only "cosmetic". Nevertheless snoop on the adapter in the Dom0
works.
regards
Bernd
# ### in the Dom0
#
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu
1500 index 2
inet 192.168.1.6 netmask ffffff00 broadcast 192.168.1.255
ether 0:c0:9f:f4:6a:3c
iwi0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu
1500 index 3
inet 192.168.1.7 netmask ffffff00 broadcast 192.168.1.255
ether 0:15:0:45:d1:5f
bash-3.2# cat Solaris10_xen0707_test.phy
bootloader = "/usr/lib/xen/bin/pygrub"
name = "solaris_10_July_07"
memory = "368"
vcpus = "1"
disk = [
''file:/export/xen-images/Solaris10_xen0707/Solaris10_xen0707.raw,0,w''
]
root = "/dev/dsk/c0d0s0"
vif = [
''bridge=bge0,mac=0:c0:9f:f4:6a:3c,script=vif-dedicated'' ]
on_shutdown = ''destroy''
on_reboot = ''restart''
on_crash = ''destroy''
bash-3.2# xm create -c Solaris10_xen0707_test.phy
Using config file "./Solaris10_xen0707_test.phy".
Started domain solaris_10_July_07
# ### in the DomU
SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Found xen v3.0.4-1-xvm but need xen v3.0.4-1-sun
WARNING: The kernel may not function correctly
ip: joining multicasts failed (4) on xnf0 - will use link layer
broadcasts for multicast
Hostname: dhcppc1
dhcppc1 console login: root
Password:
Last login: Thu Nov 22 21:10:30 from localhost
Dec 11 20:07:35 dhcppc1 login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.11 xen-nv66-2007-06-24 October 2007
# bash
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000> Does it also work for para-virtualized DomUs?
If the device in question has a GLDv3 driver, then yes (but see 6592059,
which means that it doesn''t work for wireless NICs).
xnf0:
flags=201005843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,DHCP,IPv4,CoS>
mtu 1500 index 2
inet 192.168.1.6 netmask ffffff00 broadcast 192.168.1.255
ether 0:c0:9f:f4:6a:3c
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
8252 index 1
inet6 ::1/128
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
8252 index 1
inet6 ::1/128
bash-3.2#
# ### Dom0
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 635 1 r----- 58.3
solaris_10_July_07 1 367 1 ------ 15.8
#
# It looksl like the network adapter used in the DomU is still visible
in the Dom0 and ifconfig commands
# for this adapter are possible but do not change the configuration of
the adapter.
# ifconfig bge0
bge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu
1500 index 2
inet 192.168.1.6 netmask ffffff00 broadcast 192.168.1.255
ether 0:c0:9f:f4:6a:3c
bash-3.2# ifconfig bge0 down
bash-3.2# ifconfig bge0
bge0: flags=201000842<BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index
2
inet 0.0.0.0 netmask 0
ether 0:c0:9f:f4:6a:3c
bash-3.2# ifconfig bge0 192.168.1.8
bash-3.2# ifconfig bge0
bge0: flags=201000842<BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index
2
inet 192.168.1.8 netmask ffffff00 broadcast 192.168.1.255
ether 0:c0:9f:f4:6a:3c
bash-3.2# ping 192.168.1.8
^C
--
Bernd Schemmer, Frankfurt am Main, Germany
http://home.arcor.de/bnsmb/index.html
M s temprano que tarde el mundo cambiar .
Fidel Castro
Through my experience:- Dual Marvell Yukon 88E8056 10/100/1000 Mbit/sek (ASUS P5B Deluxe) is not supported by rge driver (SNV76 64-bit) I ran prtconv -pv > out.txt and update_drv. Plumb rge0 and broght it up. It may be installed as default NIC for xend. PVMs ping it OK. However , from external network SNV host is unreachable. and plugin socket for network cabel is red flashing. I succesfully installed SKGE driver. It works for Ethernet, but is useless for Solaris xVM (76). This message posted from opensolaris.org
Using a XP cdrom mounted in the cdrom /media folder, I get this error?
bash-3.2# virt-install --name windows1 --ram 512 --cdrom /media/WXPVOL_EN --file
/zones/cp.img 10 -vnc
How large would you like the disk (/zones/cp.img) to be (in gigabytes)? 10
Would you like to enable graphics support? (yes or no) yes
Starting install...
Traceback (most recent call last):
File "/usr/bin/virt-install", line 657, in ?
main()
File "/usr/bin/virt-install", line 606, in main
dom = guest.start_install(conscb,progresscb)
File
"/export/builds/xvm_78/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 636, in start_install
File
"/export/builds/xvm_78/proto/install/usr/lib/python2.4/site-packages/virtinst/FullVirtGuest.py",
line 259, in _prepare_install_location
File
"/export/builds/xvm_78/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 51, in __init__
ValueError: Must provide a file, not a directory for the disk
bash-3.2#
This message posted from opensolaris.org
John, I ran virt-install referencing ISO image of XP CD in command line. Auto mounted WinXP CD in drive and did "dd" like:- # dd if=/dev/dsk/c0d0p6 of=/export/home/ISO/winxp.iso # virt-install -n Winds --hvm -r 512 --vnc -f /second_root/dsk/winxp-dsk \ -s 7 -c /export/home/ISO/winxp.iso Just in case, I also give a link to blog entry regarding mentioned install:- ******************************************************* Virt-install Windows XP HVM on Solaris xVM (build 76) ******************************************************* http://bderzhavets.blogspot.com/2007/11/windows-xp-hvm-at-sxde-76-dom0.html Thank you. Boris This message posted from opensolaris.org
Thanks, worked great, pretty impressive, couple of issues , you must need to use a MS product disk, not sure which ones works, the one I had access to was a Windows XP Home edition HP 375052-001 , X10-60264 , 00043-612-991-449 supplied disk GUI error msg box was a error : Files Needed: The file asms on Windows XP Hume Edition Service Pack 2 CD is needed Copy files from: GLOBALROOT\DEIVCE\CDROM\I386 Fatel Error: One of the componsts that windows needs to continue setup could not be installed the operation was canncelled by the user, Fatel error when ether the cancel or the ok button was selected! steps used: bash-3.2# dd if=/dev/dsk/c1t0d0p0 of=/zones/winxp.iso 956540+0 records in 956540+0 records out bash-3.2# virt-install -n Winds --hvm -r 512 --vnc -f /zones/winxp.dsk -s 7 -c /zones/winxp.iso Starting install... Creating storage file... 100% |=========================| 7.0 GB 00:00 Creating domain... 0 B 01:56 VNC Viewer Free Edition 4.1.2 for X - built Nov 7 2007 14:58:36 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Sun Dec 30 12:14:32 2007 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 Sun Dec 30 12:14:56 2007 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding Sun Dec 30 12:15:06 2007 CConn: Throughput 20097 kbit/s - changing to hextile encoding CConn: Throughput 20097 kbit/s - changing to full colour CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using hextile encoding Sun Dec 30 12:22:26 2007 main: End of stream Guest installation complete... restarting guest. VNC Viewer Free Edition 4.1.2 for X - built Nov 7 2007 14:58:36 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Sun Dec 30 12:22:55 2007 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 Sun Dec 30 12:23:02 2007 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding CConn: Throughput 20285 kbit/s - changing to hextile encoding CConn: Throughput 20285 kbit/s - changing to full colour CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using hextile encoding Sun Dec 30 12:27:45 2007 main: End of stream bash-3.2# # vncviewer :0 # rem repeated twice to connect via vncviewer :0, same error message. bash-3.2# # xm shut Winds This message posted from opensolaris.org
Don''t have any experience with XP Home Edition, only XP Pro. Never got such kind of errors. Just one:- When text mode phase completed Windows HVM Guest system reboots the first time.It causes path to installation ISO image to be lost by "virt-install" on Solaris xVM. This "virt-install" behavior is considered to be normal. To resolve the issue with Windows HVM rebooting behavior :- 1. Run "xm delete Windows-Domain-Name" 2. Restart "virt-install" with original command line # virt-install -n Winds --hvm -r 512 --vnc -f /second_root/dsk/winxp-dsk \ -s 7 -c /export/home/ISO/winxp.iso This action will successfully restart installation exactly at the point of failure :- entering second installation phase. Second Windows HVM Guest system''s reboot requires again VNC authorization and brings Windows HVM into running state. Please, view regarding errors mentioned by you :- http://www.opensolaris.org/jive/thread.jspa?threadID=45607&tstart=0 This message posted from opensolaris.org