Hi, all.
I''m a Xen newbie, more or less. I''ve got a Linux dom0
successfully
running two different flavors of Linux domU, now I''m trying for my
first
HVM guest, a Windows 2003 Server machine. I''ll paste my config file
below; I''ve found so many conflicting docs scattered around the net
that
I don''t know if it has any obvious errors in it or not.
The symptoms: when I create the domain, I don''t get any errors at the
command line, and I''m not sure if I''m seeing errors in
xend.log or not,
but the domain never does anything. The console doesn''t appear (have
tried all sorts of different config syntaxes for vnc and sdl -- again,
so many different forms appear around the net that I don''t know which
ones are correct, but I''m borrowing from the working configs for my
Linux domU''s). "xm list" shows straight dashes for the domU;
no "r",
no "b", no "c":
% sudo xm list loathsome
Name ID Mem VCPUs State Time(s)
loathsome 175 512 1 ------ 0.0
The hardware is a brand new Sun Ultra40, with SVM-equipped AMD
processors. dom0 kernel is the Gentoo package of Linux 2.6.21/xen, Xen
version is 3.2.0.
I have an LVM partition set up to act as the Windows hard drive. Works
for my other domains... CD is an iso file which I''ve used successfully
to install Windows on VMware, so it should be kosher...
Thanks in advance for any clues. Tips on where to get trustworthy docs
are also welcome; the Xen web site is nice so far as it goes, but there
are lots of gaps, unless I just don''t know where to look.
Thanks,
--Michael
-- begin domU config file, with comments --
builder = ''hvm''
kernel = ''/usr/lib/xen/boot/hvmloader''
memory = ''512''
device_model = ''/usr/lib/xen/bin/qemu-dm''
disk = [
''phy:/dev/mapper/pile-loathsome.uchicago.edu,ioemu:hda,w'',
''file:/xen/isos/server2003.iso,ioemu:hdc:cdrom,r'' ]
name = ''loathsome''
vif = [ '''' ]
boot = ''d''
# config lines which i''ve tried and rejected for one reason or another:
# disk = [
''phy:/dev/mapper/pile-loathsome.uchicago.edu,ioemu:hda,w'' ]
# cdrom=''/xen/isos/server2003.iso''
# vfb = [ ''type=vnc, vncpasswd=l3m0n, vncunused=1,
vnclisten=0.0.0.0'' ]
# vfb = [ ''type=vnc, vncpasswd=l3m0n, display=4,
vnclisten=0.0.0.0'' ]
# some sites show a completely different approach to console configs:
# vnc = 1
# vncunused = 1
# display = 3
# vncviewer = 1 # <- what does the "vncviewer" directive mean,
exactly?
# vncpasswd = ''l3m0n''
# vnclisten = 0.0.0.0
# apic = 0
# acpi = 0
# sdl = 1 # <- i''ve seen accounts of people saying "sdl"
worked better
# than a vnc console; how does one connect to an "sdl"
# console? not from vncviewer, right...?
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Following up to myself in case anybody else finds any of it useful: On Thu, Apr 24, 2008 at 09:12:04PM -0500, Michael Jinks wrote:><snip>> The symptoms: when I create the domain, I don''t get any errors at the > command line, and I''m not sure if I''m seeing errors in xend.log or not, > but the domain never does anything. The console doesn''t appear (have > tried all sorts of different config syntaxes for vnc and sdl -- again, > so many different forms appear around the net that I don''t know which > ones are correct, but I''m borrowing from the working configs for my > Linux domU''s). "xm list" shows straight dashes for the domU; no "r", > no "b", no "c": > > % sudo xm list loathsome > Name ID Mem VCPUs State Time(s) > loathsome 175 512 1 ------ 0.0Since posting this (and getting an example of a known good Windows xm config file which didn''t make any difference), I''ve discovered a few things and gotten a little further. First I noticed that the qemu-dm logs for my Windows machine were tiny. One complete example: % cat qemu-dm-177.log Watching /local/domain/0/device-model/177/logdirty/next-active Watching /local/domain/0/device-model/177/command warning: could not open /dev/net/tun: no virtual network emulation Could not initialize device ''tap'' I hadn''t needed a tap interface for any of my Linux domains. So I built and installed the module for dom0, then had to modprobe it by hand. That got me past this error and on to: [...] shift keysym 003e keycode 52 shift keysym 003f keycode 53 bind() failed bind() of what failed? Well, comparing this to the log for a working Linux machine, the next thing after all the shift keysym/keycode lines was "char device redirected to /dev/pts/12". Right or wrong, that made me think of serial lines. My Windows config (but none of my Linux) had serial=''pty'' ...so I commented that out. Now the qemu log still ends on an ugly looking line: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 ...but the Windows install CD has booted! Hooray! Now on to seeing if I can turn this into a working system. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Let me paste what I have that works for me:
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 1024
shadow_memory = 10
name = "acw1"
vcpus=3
pae=1
acpi=1
apic=1
vif = [ ''type=ioemu, mac=00:16:3e:37:b8:f7, bridge=xenbr1'' ]
disk = [ ''file:/store/acwin,ioemu:hda,w'' ]
boot=''c''
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
sdl=0
vnclisten="10.1.34.16"
vnc=1
vncdisplay=5
vncconsole=0
vncpasswd=''''
stdvga=0
serial=''pty''
on_reboot = ''restart''
on_crash = ''preserve''
This works with a Windows 2003 Server domU just fine. I have this
configuration working with CentOS 5.1. For Ubuntu, it''s slightly
different
-- mainly the path at the beginning.
On Thu, Apr 24, 2008 at 7:12 PM, Michael Jinks <mjinks@uchicago.edu>
wrote:
> Hi, all.
>
> I''m a Xen newbie, more or less. I''ve got a Linux dom0
successfully
> running two different flavors of Linux domU, now I''m trying for my
first
> HVM guest, a Windows 2003 Server machine. I''ll paste my config
file
> below; I''ve found so many conflicting docs scattered around the
net that
> I don''t know if it has any obvious errors in it or not.
>
> The symptoms: when I create the domain, I don''t get any errors at
the
> command line, and I''m not sure if I''m seeing errors in
xend.log or not,
> but the domain never does anything. The console doesn''t appear
(have
> tried all sorts of different config syntaxes for vnc and sdl -- again,
> so many different forms appear around the net that I don''t know
which
> ones are correct, but I''m borrowing from the working configs for
my
> Linux domU''s). "xm list" shows straight dashes for the
domU; no "r",
> no "b", no "c":
>
> % sudo xm list loathsome
> Name ID Mem VCPUs State
> Time(s)
> loathsome 175 512 1 ------ 0.0
>
> The hardware is a brand new Sun Ultra40, with SVM-equipped AMD
> processors. dom0 kernel is the Gentoo package of Linux 2.6.21/xen, Xen
> version is 3.2.0.
>
> I have an LVM partition set up to act as the Windows hard drive. Works
> for my other domains... CD is an iso file which I''ve used
successfully
> to install Windows on VMware, so it should be kosher...
>
> Thanks in advance for any clues. Tips on where to get trustworthy docs
> are also welcome; the Xen web site is nice so far as it goes, but there
> are lots of gaps, unless I just don''t know where to look.
>
> Thanks,
> --Michael
>
> -- begin domU config file, with comments --
>
> builder = ''hvm''
> kernel = ''/usr/lib/xen/boot/hvmloader''
> memory = ''512''
> device_model = ''/usr/lib/xen/bin/qemu-dm''
> disk = [
''phy:/dev/mapper/pile-loathsome.uchicago.edu,ioemu:hda,w'',
> ''file:/xen/isos/server2003.iso,ioemu:hdc:cdrom,r'' ]
> name = ''loathsome''
> vif = [ '''' ]
> boot = ''d''
>
> # config lines which i''ve tried and rejected for one reason or
another:
>
> # disk = [
''phy:/dev/mapper/pile-loathsome.uchicago.edu,ioemu:hda,w'' ]
>
> # cdrom=''/xen/isos/server2003.iso''
>
> # vfb = [ ''type=vnc, vncpasswd=l3m0n, vncunused=1,
vnclisten=0.0.0.0'' ]
> # vfb = [ ''type=vnc, vncpasswd=l3m0n, display=4,
vnclisten=0.0.0.0'' ]
>
> # some sites show a completely different approach to console configs:
> # vnc = 1
> # vncunused = 1
> # display = 3
> # vncviewer = 1 # <- what does the "vncviewer" directive
mean, exactly?
> # vncpasswd = ''l3m0n''
> # vnclisten = 0.0.0.0
> # apic = 0
> # acpi = 0
> # sdl = 1 # <- i''ve seen accounts of people saying
"sdl" worked better
> # than a vnc console; how does one connect to an "sdl"
> # console? not from vncviewer, right...?
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2008-Jun-21 10:48 UTC
RE: solved, Re: [Xen-users] Windows domU doesn''t boot
Hello, I had the same problem. But I do not think, this is related to the serial=''pty'' setting... In my case this line was remmed out in the configuration, but the error bind() failed was till there... The real problem is (at least in my case was) in the specification of "vnclisten" parameter - this specifies the address where the machine should "hear" to incomig VNC connections for management of the HVM hosts. If there is specified an invalid address, then the vnc "server" for that virtual instance cannot be started, because there fails the bind of the service to the specified port on specified address. This is also consistent with the fact the qemu-dm starts, but then everything stops and the TCP post is not allocated, what can be seen if running netstat -a -n Michael, is it possible in Your case this was the same and You not only remmed-out the "serial" oto, bu also repaired the IP address specified in vnclisten parameter? With regards, Archie -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Michael Jinks Sent: Friday, April 25, 2008 10:19 AM To: xen-users@lists.xensource.com Subject: solved, Re: [Xen-users] Windows domU doesn''t boot Following up to myself in case anybody else finds any of it useful: On Thu, Apr 24, 2008 at 09:12:04PM -0500, Michael Jinks wrote:><snip>> The symptoms: when I create the domain, I don''t get any errors at the > command line, and I''m not sure if I''m seeing errors in xend.log or not, > but the domain never does anything. The console doesn''t appear (have > tried all sorts of different config syntaxes for vnc and sdl -- again, > so many different forms appear around the net that I don''t know which > ones are correct, but I''m borrowing from the working configs for my > Linux domU''s). "xm list" shows straight dashes for the domU; no "r", > no "b", no "c": > > % sudo xm list loathsome > Name ID Mem VCPUs StateTime(s)> loathsome 175 512 1 ------ 0.0Since posting this (and getting an example of a known good Windows xm config file which didn''t make any difference), I''ve discovered a few things and gotten a little further. First I noticed that the qemu-dm logs for my Windows machine were tiny. One complete example: % cat qemu-dm-177.log Watching /local/domain/0/device-model/177/logdirty/next-active Watching /local/domain/0/device-model/177/command warning: could not open /dev/net/tun: no virtual network emulation Could not initialize device ''tap'' I hadn''t needed a tap interface for any of my Linux domains. So I built and installed the module for dom0, then had to modprobe it by hand. That got me past this error and on to: [...] shift keysym 003e keycode 52 shift keysym 003f keycode 53 bind() failed bind() of what failed? Well, comparing this to the log for a working Linux machine, the next thing after all the shift keysym/keycode lines was "char device redirected to /dev/pts/12". Right or wrong, that made me think of serial lines. My Windows config (but none of my Linux) had serial=''pty'' ...so I commented that out. Now the qemu log still ends on an ugly looking line: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 ...but the Windows install CD has booted! Hooray! Now on to seeing if I can turn this into a working system. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users __________ Informace od NOD32 3053 (20080424) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users