Dear Experts, Does anyone install Windows Vista on XVM successfully? I am using machine Sun x4600 with AMD 8218 cpu with virtualization feature. i installed OpenSolaris build 75, My installation steps: # 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="e1000g0" # svcadm refresh xvm/xend # svcadm restart xvm/xend #virt-install -n vista1 --hvm -r 4096 --vnc -f /vista1/vista1.img -s 9 -c /vista.iso Starting install... Creating storage file... 100% |=========================| 9.0 GB 00:00 Creating domain... 0 B 00:03 Unable to connect to graphical console; the GNOME vino VNC client is not installed. Please connect to 127.0.0.1:0 Domain installation still in progress. You can reconnect to the console to complete the installation process. bash-3.2# vncviewer :0 CConn: connected to host localhost port 5900 CConnection: Server supports RFB protocol version 3.3 CConnection: Using RFB protocol version 3.3 CConn: Using pixel format depth 24 (32bpp) big-endian rgb888 CConn: Using ZRLE encoding The vncviewer is opened, it show "Windows is loading files", it take a long time, but no response. Does anyone successfully with Vista installation? Many thanks. Regards, Angus This message posted from opensolaris.org
does anyone can help in this issue? Very appreciate for your help! This message posted from opensolaris.org
Angus Yiu wrote:> does anyone can help in this issue? Very appreciate for your help! >do you have the workaround for the following? 6612343 The fix for 6292092 and xvm dom0 not getting along MRJ http://www.opensolaris.org/os/community/xen/docs/relnotes/;jsessionid=C3ED1491F1781C75EE61E81CD429034C 6612343 The fix for 6292092 and xvm dom0 not getting along Workaround: add the following to /etc/system: set softcall_delay=0x100000
Hi MRJ, Thanks. but still fail the installation. I have installed snv_77 and set softcall_delay=0x100000 in /etc/system. I cannot find any error messages in /var/log/xen. Is there any tricks for this installation? and how to further troubleshooting? Thanks, Angus This message posted from opensolaris.org
Angus Yiu wrote:> Hi MRJ, > > Thanks. but still fail the installation. I have installed snv_77 and set softcall_delay=0x100000 in /etc/system. > > I cannot find any error messages in /var/log/xen. Is there any tricks for this installation? and how to further troubleshooting?What version of Vista do you have? How much memory did you give to the domain? I''ve installed vista with no problems in the past.. MRJ
Hi MRJ, Thanks for your response. I tried Vista Business and winXP professional, however both got fail. I assigned 4G Ram to the guest domain. The machine is sun x4600 with 8 CPU dual core and 36G Ram. Is there any post installation tasks before i run virt-install? Thanks, Angus This message posted from opensolaris.org
Hi MRJ, Sorry i used the wrong Vista Business 64 bit version. I can install in Vista Business (32 bit)version now. Thanks. Regards, Angus This message posted from opensolaris.org
Hi MRJ,
I can install Vista Business on XVM (snv_77). However the network
doesn''t work in Vista, it only scanned a network device "Realtek
RTL8139C + Fast Ethernet NIC".
i can assign IP to this network device. However the network connection
does''t work.
Do i need to specify the correct network device?
bash-3.2# dladm show-link
e1000g0 type: non-vlan mtu: 1500 device: e1000g0
e1000g1 type: non-vlan mtu: 1500 device: e1000g1
e1000g2 type: non-vlan mtu: 1500 device: e1000g2
e1000g3 type: non-vlan mtu: 1500 device: e1000g3
vnic901 type: non-vlan mtu: 1500 device: vnic901
bash-3.2# svccfg -s xvm/xend listprop |grep default
config/default-nic astring e1000g0
virsh # dumpxml vista2
domain type=''xen'' id=''23''>
name>vista2</name>
uuid>ff45ee7715c80544c6361f361eccbda5</uuid>
os>
type>hvm</type>
loader>/usr/lib/xen/boot/hvmloader</loader>
boot dev=''hd''/>
/os>
memory>4227072</memory>
currentMemory>4194304</currentMemory>
vcpu>4</vcpu>
on_poweroff>destroy</on_poweroff>
on_reboot>restart</on_reboot>
on_crash>restart</on_crash>
features>
acpi/>
apic/>
pae/>
/features>
devices>
emulator>/usr/lib/xen/bin/qemu-dm</emulator>
interface type=''ethernet''>
mac address=''00:16:3e:20:56:17''/>
/interface>
disk type=''file'' device=''disk''>
driver name=''file''/>
source file=''/vm/vista2.img''/>
target dev=''hda''/>
disk>
graphics type=''vnc'' port=''5901''/>
/devices>
/domain>
====================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
e1000g0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500
index 2
inet 192.168.0.10 netmask ffffff00 broadcast 192.168.0.255
ether 0:14:4f:45:be:7e
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
This message posted from opensolaris.org
Angus Yiu wrote:> Hi MRJ, > > I can install Vista Business on XVM (snv_77). However the network doesn''t work in Vista, it only scanned a network device "Realtek RTL8139C + Fast Ethernet NIC". > > i can assign IP to this network device. However the network connection does''t work. > > Do i need to specify the correct network device?The realtek device emulated in the qemu included in the Xen 3.0.4 source does not work with vista. It works fine with WinXP.. For Vista and 3.0.4, you need to use ne2k_pci. vif = [''type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci''] I believe this is fixed in 3.1.2, but I haven''t tried it to verify it yet. Thanks, MRJ> bash-3.2# dladm show-link > e1000g0 type: non-vlan mtu: 1500 device: e1000g0 > e1000g1 type: non-vlan mtu: 1500 device: e1000g1 > e1000g2 type: non-vlan mtu: 1500 device: e1000g2 > e1000g3 type: non-vlan mtu: 1500 device: e1000g3 > vnic901 type: non-vlan mtu: 1500 device: vnic901 > > bash-3.2# svccfg -s xvm/xend listprop |grep default > config/default-nic astring e1000g0 > > virsh # dumpxml vista2 > domain type=''xen'' id=''23''> > name>vista2</name> > uuid>ff45ee7715c80544c6361f361eccbda5</uuid> > os> > type>hvm</type> > loader>/usr/lib/xen/boot/hvmloader</loader> > boot dev=''hd''/> > /os> > memory>4227072</memory> > currentMemory>4194304</currentMemory> > vcpu>4</vcpu> > on_poweroff>destroy</on_poweroff> > on_reboot>restart</on_reboot> > on_crash>restart</on_crash> > features> > acpi/> > apic/> > pae/> > /features> > devices> > emulator>/usr/lib/xen/bin/qemu-dm</emulator> > interface type=''ethernet''> > mac address=''00:16:3e:20:56:17''/> > /interface> > disk type=''file'' device=''disk''> > driver name=''file''/> > source file=''/vm/vista2.img''/> > target dev=''hda''/> > disk> > graphics type=''vnc'' port=''5901''/> > /devices> > /domain> > ====================> 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 > e1000g0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2 > inet 192.168.0.10 netmask ffffff00 broadcast 192.168.0.255 > ether 0:14:4f:45:be:7e > lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 > inet6 ::1/128 > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
> The realtek device emulated in the qemu included in the > Xen 3.0.4 source does not work with vista. It works fine > with WinXP.. > > For Vista and 3.0.4, you need to use ne2k_pci. > > vif = [''type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci'']Yep, the model=ne2k_pci device works in a 32-bit Win/Vista hvm domain, but Vista doesn''t include a driver for the ne2000 pci device. You have to find an old Win2000 ne2000 driver and use that with Vista. This message posted from opensolaris.org
Jürgen Keil wrote:>> The realtek device emulated in the qemu included in the >> Xen 3.0.4 source does not work with vista. It works fine >> with WinXP.. >> >> For Vista and 3.0.4, you need to use ne2k_pci. >> >> vif = [''type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci''] > > Yep, the model=ne2k_pci device works in a 32-bit Win/Vista hvm > domain, but Vista doesn''t include a driver for the ne2000 pci device. > You have to find an old Win2000 ne2000 driver and use that with > Vista.I assume you meant "with *64-bit* vista"? MRJ
Mark Johnson wrote:> > > Jürgen Keil wrote: >>> The realtek device emulated in the qemu included in the >>> Xen 3.0.4 source does not work with vista. It works fine >>> with WinXP.. >>> >>> For Vista and 3.0.4, you need to use ne2k_pci. >>> >>> vif = [''type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci''] >> >> Yep, the model=ne2k_pci device works in a 32-bit Win/Vista hvm >> domain, but Vista doesn''t include a driver for the ne2000 pci device. >> You have to find an old Win2000 ne2000 driver and use that with >> Vista. > > > I assume you meant "with *64-bit* vista"?Ah, 32-bit vista.. I see that''s what I had done... Looks like I found the driver (w2k_8029.zip) and put it on a iso to install in my vista domU I can''t remember anything anymore :-( Thanks, MRJ
Dear MRJ, jkeil , After i configure vif = [ ''type=ioemu,model=ne2k_pci'' ] and install the new driver in winvista. My vista can connect the network now. Many thanks for your help in here. Regards, Angus This message posted from opensolaris.org
> Dear MRJ, jkeil , > > After i configure vif = [ ''type=ioemu,model=ne2k_pci'' > ] and install the new driver in winvista. My vista > can connect the network now. Many thanks for your > help in here.How do you set vif = [ ''type=ioemu,model=ne2k_pci''] ? Where does that go when using virt-install or an already existing domain? This message posted from opensolaris.org
Just in case the author (or further readers like me) haven''t seen the referenced thread, there''s word that HVM 64-bit domains are still underway, so for unmodified guests we must use the 32-bit versions. See: http://opensolaris.org/jive/thread.jspa?messageID=182165&tstart=0 BTW, can we force a 32-bit Guest domain boot (newly created or old) with a 64-bit dom0 xVM kernel loaded and running? Is it in FAQ somewhere? No?.. Beside giving the link, I have some questions of my own, concerning xVM performance and general compatibility: In my personal experience, the performance seems appaling when it''s working at all :( It''s worse with the idea of a 45% RAM footprint of Xen dom0, compared to 200-500Mb of VMWare ESX Server 3.0.1''s Console. On good big servers, 45% is a lot. We did some tests at work trying to install some Xen virtual machines on Sun X4600 (snv_b77), and see if [Open]Solaris+xVM(+ZFS+...) is a reasonable replacement right now for VMWare ESX... Does anyone have near-hardware performance? Maybe just a few times worse? Which OSes andversions? For our integrations, Solaris 10, RHEL 3-5 and Windows 2000/2003/XP are of primary interest. With the problems we had, I wonder: did we do something (many things) wrong, or does everyone suffer similarly, and that''s just the way things are right now? ;) Here''s some results of the few attempts so far (Solaris 10U4 works well, others suck at best): While we did get Windows XP SP2 (32-bit) to boot and even go on configuring in graphics mode (first reboot), it took a couple of hours to get to the TCP/IP Settings screen (Setup will completein approximately 29 minutes)... BTW, VNC screen loses somepart of the display bottom side (due to unusual resolution in the Windows installer); can it possibly adapt to VM resolution changes? Windows 64-bit releases failed (froze fordays) in the text mode part, Starting Windows - as expected, I see now. I did get a Solaris 10u4 8/07 running in a "--vnc --hvm" installation mode, but in the textmode installer over VNC (got a corrupted white screen in graphical attempts). Got the full install okay (End User + OEM packages), booted up all the way to the JDS. Apparently it works as 32-bit, without an amd64/boot_archive and amd64/multiboot parts yet, and seemed reasonably fast working. I did *not* get a guest snv_b77 running (best I did was text mode and Signal 11 in install-solaris after Reboot Warning screen). This message posted from opensolaris.org
I can answer some of these questions for you. I can''t answer this, I only have successfully worked with 32-bit para- virtualized and fully-virtualized domains. No, I couldn''t find it in the FAQ or documentation. VMware uses special virtualization methods for dealing with CPU cache and memory performance degradation inherent to fully virtualized guests. Their tools include a memory management daemon that reduces overhead by freeing truly unused memory. Using ZFS with xVM makes the situation worse since it aggressively caches memory and data, similar but more extreme than how SGI XFS works. xVM fully allocates the memory, it''s about the same if you didn''t ran their guest tools with memory consumption. Right now they are focused on getting support for common guests, remember this is a port, and only recently has it became commercially supported by Sun. It''s not viable yet because no tools exist for guests that could deal with inherent guest glitches, and the most important issues right now are networking drivers, mouse synchronization, and just simply being able to boot guests. It is not commercially ready, nor is Sun advertising that it is. Until SXDE comes with xVM, work focuses on the big issues first, the performance unfortunately is not as big of a priority since developers are already strained trying to get 64-bit para-virtualized guests, and a wide number of operating systems working under xVM. It doesn''t have near-native performance, and remember VMware has been around since 1998, with thousands of engineers and direct support from cpu vendors. Guests not fully virtualized exhibit the best performance, as they translate system calls instead of running through the respective cpu virtualization extension. Windows has the worst performance because it has some architectural annoyances that make it hard to tune for, namely source code, or lack thereof. FreeBSD, NetBSD, Linux, and OpenSolaris B75+ work almost all equally well as pvms, but there are quirks for each that are needed to address, performance is acceptable for them. Linux has the best performance as a guest because it is designed to have a small fingerprint, and has had the most amount of architecture work done specific to Xen as a guest and as a host. Specific versions would be NetBSD 4, FreeBSD 7 (CURRENT), CentOS 5 and less-popular distributions like Gentoo with a Xen kernel. The Windows VNC glitch is already known, and I''m pretty sure the VNC implementation can''t deal with it yet. Remember, the official VNC client from RealVNC still has its share of problems with adapting to changing resolutions, without a mirror driver (Unavailable in an installer) it can''t deal with it very easily. Solaris 10 under hvm does work well, I haven''t tried it, but some people I''ve talked with say its almost good enough to use for small porting projects between OpenSolaris and Solaris 10. I haven''t seen a bug for the corruption in the installer. As for OpenSolaris, most developers are using Indiana (B75) para- virtualized, higher builds may exhibit unreported or different behavior. You should try using B75 and see if it has less issues. James On Dec 4, 2007, at 2:40 PM, Jim Klimov wrote:> Just in case the author (or further readers like me) haven''t seen > the referenced thread, there''s word that HVM 64-bit domains are > still underway, so for unmodified guests we must use the 32-bit > versions. > > See: > http://opensolaris.org/jive/thread.jspa?messageID=182165&tstart=0 > > BTW, can we force a 32-bit Guest domain boot (newly created or old) > with a 64-bit dom0 xVM kernel loaded and running? > > Is it in FAQ somewhere? No?.. > > Beside giving the link, I have some questions of my own, concerning > xVM performance and general compatibility: > > In my personal experience, the performance seems appalling when it''s > working at all :( It''s worse with the idea of a 45% RAM footprint of > Xen dom0, compared to 200-500Mb of VMWare ESX Server 3.0.1''s > Console. On good big servers, 45% is a lot. > > We did some tests at work trying to install some Xen virtual > machines on Sun X4600 (snv_b77), and see if [Open]Solaris+xVM(+ZFS > +...) is a reasonable replacement right now for VMWare ESX... > > Does anyone have near-hardware performance? Maybe just a few times > worse? Which OSes and versions? For our integrations, Solaris 10, > RHEL 3-5 and Windows 2000/2003/XP are of primary interest. > > With the problems we had, I wonder: did we do something (many > things) wrong, or does everyone suffer similarly, and that''s just > the way things are right now? ;) > > Here''s some results of the few attempts so far (Solaris 10U4 works > well, others suck at best): > > While we did get Windows XP SP2 (32-bit) to boot and even go on > configuring in graphics mode (first reboot), it took a couple of > hours to get to the TCP/IP Settings screen (Setup will complete in > approximately 29 minutes)... BTW, VNC screen loses some part of the > display bottom side (due to unusual resolution in the Windows > installer); can it possibly adapt to VM resolution changes? > > Windows 64-bit releases failed (froze for days) in the text mode > part, Starting Windows - as expected, I see now. > > I did get a Solaris 10u4 8/07 running in a "--vnc --hvm" > installation mode, but in the text-mode installer over VNC (got a > corrupted white screen in graphical attempts). Got the full install > okay (End User + OEM packages), booted up all the way to the JDS. > Apparently it works as 32-bit, without an amd64/boot_archive and > amd64/multiboot parts yet, and seemed reasonably fast working. > > I did *not* get a guest snv_b77 running (best I did was text mode > and Signal 11 in install-solaris after Reboot Warning screen). > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Thanks for the many detailed answers :) I''ll stay tuned and hope xVM will soon become a real strong alternative to VMWare ESX 3. While I like the latter, its stack of licenses is not so cheap for many of our smaller customers, especially in non-IT businesses, to consider it seriously. So they only fiddle around with a Starter edition and get their feet wet :) This message posted from opensolaris.org