Thanks again for the reply. We're getting closer.
On 6/8/07, Martin Goldstone <m.j.goldstone@xxxxxxxxxxxxxxx> wrote:
What does your winxp2.xml file look like?
Does netstat show that anything is listening on any 59xx ports?
There is something on 5903, which turns out to be the WinXP domain.
And vncviewer 127.0.0.1:3 works. Of course that's not where I want it
to be.
Also,
try vncviewer with the port number instead of the display number; I know
it shouldn't work, but I've heard it suggested before.
It worked on 5903, but that of course isn't where I want it to be
From the log you posted, I'm not sure but it seems that it's not getting
the correct VNC display (in fact, it seems like its getting a
non-integer passed to it). This should be in the XML file (the line
reads <graphics type='vnc' port='5900'/> or similar). Is it in yours?
Yes I have that line. If I remove that line it appears to start,
however I can't get to it at all (the Virtual Machine Manager says the
console is unavailable and there doesn't appear to be any vnc
listening). If I remove port='5934' it seems to work (but again it's
on :3 and 5903 which isn't where I want it). Also this xml file gives
that weird mouse which I solved in the hvm file by adding
usbdevice='tablet', how do I add that to the xml file?
Here's the whole file with the vnc line:
<domain type='xen' id='34'>
<name>WinXP-001</name>
<uuid>5f22cbb1e5570945b2956aeae9be015b</uuid>
<os>
<type>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev='hd'/>
</os>
<memory>524288</memory>
<vcpu>1</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<features>
</features>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<interface type='bridge'>
<source bridge='xenbr0'/>
<mac address='00:16:3e:40:4b:e4'/>
<script path='vif-bridge'/>
</interface>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/VG_Guests/WinXP-001'/>
<target dev='hda'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='file'/>
<source file='/opt/xen_stuff/winxp.iso'/>
<target dev='hdc'/>
</disk>
<disk type='block' device='cdrom'>
<driver name='phy'/>
<source dev='/dev/scd0'/>
<target dev='hdd'/>
<readonly/>
</disk>
<graphics type='vnc' port='5934' listen='127.0.0.1'/>
<console tty='/dev/pts/2'/>
</devices>
</domain>
Martin
Just Anidiot wrote:
> Thanks for the reply. I think I'm a lot closer than before, but still
> no cigar.
>
> On 6/8/07, Martin Goldstone <m.j.goldstone@xxxxxxxxxxxxxxx> wrote:
>> You should be able to launch a VNC client (if you're not using SDL for
>> graphics), and point it at the port that that domain is on (netstat or
>> set the display with vncdisplay= in the domain's config).
>
> I've left vncdisplay commented out in the hvm file. The notes in that
> file imply that the default is domid. However when I try to vnc to
> 127.0.0.1:33 I get a connection refused. I then tried to set it to
> some random number (tried 5,10,15) and still get a connection refused.
> vnc=1 and vnclisten="127.0.0.1" and vncpasswd='' are set in the hvm
> file.
>
>> I've seen
>> this problem before: libvirt didn't seem to pick up the VNC display
>> properly, but I can't remember which version of libvirt I testing at the
>> time. Using virsh to get it's XML definition of the domain led me to
>> this conclusion, as soon as I added it in and created the domain from an
>> XML file using virsh instead of xm, the problem went away.
>>
>
> Ah-ha maybe this is part of my problem above.
> However I'm having trouble getting virsh to create the domain....
>
> This is on RHEL5,
> virsh version
> Compiled against library: libvir 0.1.8
> Using library: libvir 0.1.8
> Using API: Xen 3.0.1
> Running hypervisor: Xen 3.0.0
>
> This is what I did:
> WinXP is already running as ID=34 (created by xm)
> virsh dumpxml 34 > /etc/xen/winxp2.xml
> I then shutdown WinXP.
> virsh create /etc/xen/winxp2.xml
>
> libvir: Xen Daemon error : POST operation failed: (xend.err 'Error
> creating domain: int argument required')
> Failed to create domain WinXP-001
> error: Failed to create domain from /etc/xen/winxp2.xml
>
> I looked at xend.log and the following entries all are related to this
> error:
>
> [2007-06-08 08:58:08 xend.XendDomainInfo 3199] DEBUG
> (XendDomainInfo:190) XendDo
> mainInfo.create(['vm', ['name', 'WinXP-001'], ['memory', '512'],
> ['maxmem', '512
> '], ['vcpus', '1'], ['uuid', '5f22cbb1e5570945b2956aeae9be015b'],
> ['on_poweroff'
> , 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'],
> ['image', ['hvm
> ', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model',
> '/usr/lib/xen/bin
> /qemu-dm'], ['boot', 'c'], ['serial', 'pty'], ['vnc', '1'],
> ['vncdisplay', '34']
> , ['vnclisten', '127.0.0.1']]], ['device', ['vbd', ['dev', 'hda:disk'],
> ['uname'
> , 'phy:/dev/VG_Guests/WinXP-001'], ['mode', 'w']]], ['device', ['vbd',
> ['dev', '
> hdc:cdrom'], ['uname', 'file:/opt/xen_stuff/winxp.iso'], ['mode',
> 'w']]], ['devi
> ce', ['vbd', ['dev', 'hdd:cdrom'], ['uname', 'phy:/dev/scd0'], ['mode',
> 'r']]],
> ['device', ['vif', ['mac', '00:16:3e:40:4b:e4'], ['bridge', 'xenbr0'],
> ['script'
> , 'vif-bridge'], ['type', 'ioemu']]]])
>
> [2007-06-08 08:58:08 xend.XendDomainInfo 3199] DEBUG
> (XendDomainInfo:296) parseC
> onfig: config is ['vm', ['name', 'WinXP-001'], ['memory', '512'],
> ['maxmem', '51
> 2'], ['vcpus', '1'], ['uuid', '5f22cbb1e5570945b2956aeae9be015b'],
> ['on_poweroff
> ', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'],
> ['image', ['hv
> m', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model',
> '/usr/lib/xen/bi
> n/qemu-dm'], ['boot', 'c'], ['serial', 'pty'], ['vnc', '1'],
> ['vncdisplay', '34'
> ], ['vnclisten', '127.0.0.1']]], ['device', ['vbd', ['dev', 'hda:disk'],
> ['uname
> ', 'phy:/dev/VG_Guests/WinXP-001'], ['mode', 'w']]], ['device', ['vbd',
> ['dev',
> 'hdc:cdrom'], ['uname', 'file:/opt/xen_stuff/winxp.iso'], ['mode',
> 'w']]], ['dev
> ice', ['vbd', ['dev', 'hdd:cdrom'], ['uname', 'phy:/dev/scd0'], ['mode',
> 'r']]],
> ['device', ['vif', ['mac', '00:16:3e:40:4b:e4'], ['bridge', 'xenbr0'],
> ['script
> ', 'vif-bridge'], ['type', 'ioemu']]]]
>
> [2007-06-08 08:58:08 xend.XendDomainInfo 3199] DEBUG
> (XendDomainInfo:397) parseC
> onfig: result is {'shadow_memory': None, 'start_time': None, 'uuid':
> '5f22cbb1e5
> 570945b2956aeae9be015b', 'on_crash': 'restart', 'on_reboot': 'restart',
> 'localti
> me': None, 'image': ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'],
> ['device_
> model', '/usr/lib/xen/bin/qemu-dm'], ['boot', 'c'], ['serial', 'pty'],
> ['vnc', '
> 1'], ['vncdisplay', '34'], ['vnclisten', '127.0.0.1']], 'on_poweroff':
> 'destroy'
> , 'bootloader_args': None, 'cpus': None, 'name': 'WinXP-001', 'backend':
> [], 'vc
> pus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None,
> 'memory': 512
> , 'device': [('vbd', ['vbd', ['dev', 'hda:disk'], ['uname',
> 'phy:/dev/VG_Guests/
> WinXP-001'], ['mode', 'w']]), ('vbd', ['vbd', ['dev', 'hdc:cdrom'],
> ['uname', 'f
> ile:/opt/xen_stuff/winxp.iso'], ['mode', 'w']]), ('vbd', ['vbd', ['dev',
> 'hdd:cd
> rom'], ['uname', 'phy:/dev/scd0'], ['mode', 'r']]), ('vif', ['vif',
> ['mac', '00:
> 16:3e:40:4b:e4'], ['bridge', 'xenbr0'], ['script', 'vif-bridge'],
> ['type', 'ioem
> u']])], 'bootloader': None, 'cpu': None, 'maxmem': 512}
>
> [2007-06-08 08:58:08 xend.XendDomainInfo 3199] DEBUG
> (XendDomainInfo:1296) XendD
> omainInfo.initDomain: 36 1.0
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: boot, val: c
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: fda, val: None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: fdb, val: None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: soundhw, val: None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: localtime, val:
> None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: serial, val: pty
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: std-vga, val: None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: isa, val: None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: vcpus, val: None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: acpi, val: None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: usb, val: None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: usbdevice, val:
> None
> [2007-06-08 08:58:08 xend 3199] DEBUG (image:329) args: k, val: None
>
> [2007-06-08 08:58:08 xend.XendDomainInfo 3199] ERROR
> (XendDomainInfo:202) Domain
> construction failed
> Traceback (most recent call last):
> File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 195,
> in create
> vm.initDomain()
> File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 1309,
> in initDomain
> self.info['device'])
> File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 45, in
> create
> return findImageHandlerClass(imageConfig)(vm, imageConfig, deviceConfig)
> File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 75, in
> __init_
> _
> self.configure(imageConfig, deviceConfig)
> File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 272, in
> config
> ure
> self.dmargs += self.configVNC(imageConfig)
> File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 383, in
> config
> VNC
> ret += ['-vnc', '%d' % vncdisplay]
> TypeError: int argument required
>
> [2007-06-08 08:58:08 xend.XendDomainInfo 3199] DEBUG
> (XendDomainInfo:1463) XendD
> omainInfo.destroy: domid=36
>
> [2007-06-08 08:58:08 xend.XendDomainInfo 3199] DEBUG
> (XendDomainInfo:1471) XendD
> omainInfo.destroyDomain(36)
> [2007-06-08 08:58:08 xend 3199] ERROR (SrvBase:88) Request create failed.
> Traceback (most recent call last):
> File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85, in
> perfor
> m
> return op_method(op, req)
> File
> "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomainDir.py", line
> 82, in op_create
> raise XendError("Error creating domain: " + str(ex))
> XendError: Error creating domain: int argument required
>
> So what does any of this mean? Is my virsh broken or something? How
> do I fix this?
> Any ideas?
>
> Thanks.
>
>> Martin
>>
>> Just Anidiot wrote:
>> > I'm using RHEL 5. One of the virtual machines I have running is a
>> > WinXP install. I start this up after I login to X. If I log out of
>> > X, the virtual WinXP is still running (that's fine with me). However
>> > when I log back into X and start the Virtual Machine Manager, I am
>> > unable to open the machine. It normally says "Virtual Machine Console
>> > is unavailable." There does not appear to be any way to get back to
>> > doing anything with the WinXP virtual machine. I have to destroy it
>> > and start a new one. I've tried this with both KDE and Gnome
>> > sessions, both exhibit the same problem. Is there any way to get back
>> > to my virtual WinXP?
>> >
>> > _______________________________________________
>> > Xen-users mailing list
>> > Xen-users@xxxxxxxxxxxxxxxxxxx
>> > http://lists.xensource.com/xen-users
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home