thr3ads.net - Fedora xen - [Fedora-xen] Problems running xp guest [Aug 2007]

If this information is useful, please help other people find it:
Share via:

Falk Zimmermann

2007-Aug-23 12:14 UTC

[Fedora-xen] Problems running xp guest

Hi,
I''m running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel and
used virt-manager to configure an F7 and xp guest domain. Whereas I can
correctly run the F7 guest, I receive the following message after trying
to run the xp guest:

(xend.err ''Disk image does not exist: '')

Both images reside in the same directory (/var/lib/xen/images) and I
have selinux disabled.
Any ideas?

Thanks,
Falk

Richard W.M. Jones

2007-Aug-23 13:29 UTC

head link

Re: [Fedora-xen] Problems running xp guest

Falk Zimmermann wrote:> Hi,
> I''m running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen kernel
and
> used virt-manager to configure an F7 and xp guest domain. Whereas I can
> correctly run the F7 guest, I receive the following message after trying
> to run the xp guest:
> 
> (xend.err ''Disk image does not exist: '')
> 
> Both images reside in the same directory (/var/lib/xen/images) and I
> have selinux disabled.
> Any ideas?
Can you try:

   virsh dumpxml <xp>

(where <xp> is the name of the XP guest domain).  Then check that the 
disk device shown has the right path.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

Falk Zimmermann

2007-Aug-23 13:42 UTC

head link

Re: [Fedora-xen] Problems running xp guest

Richard W.M. Jones schrieb:> Falk Zimmermann wrote:
>> Hi,
>> I''m running FC7 on an x86_64 with the 2.6.20-2925.13.fc7xen
kernel and
>> used virt-manager to configure an F7 and xp guest domain. Whereas I can
>> correctly run the F7 guest, I receive the following message after
trying
>> to run the xp guest:
>>
>> (xend.err ''Disk image does not exist: '')
>>
>> Both images reside in the same directory (/var/lib/xen/images) and I
>> have selinux disabled.
>> Any ideas?
>
> Can you try:
>
>   virsh dumpxml <xp>
>
> (where <xp> is the name of the XP guest domain).  Then check that the
> disk device shown has the right path.
>
> Rich.
>Hi Richard,
the entry in the xml file looks fine (at least to me) and the image file 
exists:

<domain type=''xen'' id=''-1''>
  <name>xp4</name>
  <uuid>1e9860a0e244a2645b0a321a0fe649ec</uuid>
  <os>
    <type>hvm</type>
    <loader>/usr/lib/xen/boot/hvmloader</loader>
    <boot dev=''hd''/>
  </os>
  <memory>512000</memory>
  <vcpu>1</vcpu>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <devices>
    <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
    <interface type=''bridge''>
      <source bridge=''eth0''/>
      <mac address=''00:16:3e:72:1b:29''/>
    </interface>
    <disk type=''file'' device=''disk''>
      <driver name=''file''/>
      <source file=''/var/lib/xen/images/xp4''/>
      <target dev=''hda''/>
    </disk>
    <disk type=''file'' device=''cdrom''>
      <driver name=''file''/>
      <source file=''''/>
      <target dev=''hdc''/>
      <readonly/>
    </disk>
    <graphics type=''vnc'' port=''-1''
keymap=''en-us''/>
  </devices>
</domain>


Cheers,
Falk

Richard W.M. Jones

2007-Aug-23 13:48 UTC

head link

Re: [Fedora-xen] Problems running xp guest

Falk Zimmermann wrote:> Richard W.M. Jones schrieb:
>> Falk Zimmermann wrote:
>>> Hi,
>>> I''m running FC7 on an x86_64 with the
2.6.20-2925.13.fc7xen kernel and
>>> used virt-manager to configure an F7 and xp guest domain. Whereas I
can
>>> correctly run the F7 guest, I receive the following message after
trying
>>> to run the xp guest:
>>>
>>> (xend.err ''Disk image does not exist: '')
>>>
>>> Both images reside in the same directory (/var/lib/xen/images) and
I
>>> have selinux disabled.
>>> Any ideas?
>>
>> Can you try:
>>
>>   virsh dumpxml <xp>
>>
>> (where <xp> is the name of the XP guest domain).  Then check that
the
>> disk device shown has the right path.
>>
>> Rich.
>>
> Hi Richard,
> the entry in the xml file looks fine (at least to me) and the image file 
> exists:
Looks like a bug.  Can you post also /var/log/xen/xend.log and 
/var/log/xen/xend-debug.log.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

Falk Zimmermann

2007-Aug-23 14:04 UTC

head link

Re: [Fedora-xen] Problems running xp guest

Richard W.M. Jones schrieb:> Falk Zimmermann wrote:
>> Richard W.M. Jones schrieb:
>>> Falk Zimmermann wrote:
>>>> Hi,
>>>> I''m running FC7 on an x86_64 with the
2.6.20-2925.13.fc7xen kernel and
>>>> used virt-manager to configure an F7 and xp guest domain.
Whereas I
>>>> can
>>>> correctly run the F7 guest, I receive the following message
after
>>>> trying
>>>> to run the xp guest:
>>>>
>>>> (xend.err ''Disk image does not exist: '')
>>>>
>>>> Both images reside in the same directory (/var/lib/xen/images)
and I
>>>> have selinux disabled.
>>>> Any ideas?
>>>
>>> Can you try:
>>>
>>>   virsh dumpxml <xp>
>>>
>>> (where <xp> is the name of the XP guest domain).  Then check
that
>>> the disk device shown has the right path.
>>>
>>> Rich.
>>>
>> Hi Richard,
>> the entry in the xml file looks fine (at least to me) and the image 
>> file exists:
>
> Looks like a bug.  Can you post also /var/log/xen/xend.log and 
> /var/log/xen/xend-debug.log.
>
> Rich.
>Ok, here they come:

Xend started at Tue Aug 21 08:57:05 2007.
device eth0 already exists; can''t create bridge with the same name
set hello timer failed: No such file or directory
set forward delay failed: No such file or directory
set stp status failed: No such file or directory
Nothing to flush.
Traceback (most recent call last):
  File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py",
line
140, in process
    resource = self.getResource()
  File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py",
line
172, in getResource
    return self.getServer().getResource(self)
  File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py",
line
351, in getResource
    return self.root.getRequestResource(req)
  File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 
39, in getRequestResource
    return findResource(self, req)
  File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 
26, in findResource
    next = resource.getPathResource(pathElement, request)
  File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 
49, in getPathResource
    val = self.getChild(path, request)
  File "/usr/lib64/python2.5/site-packages/xen/web/SrvDir.py", line
71,
in getChild
    val = self.get(x)
  File 
"/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", 
line 52, in get
    return self.domain(x)
  File 
"/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", 
line 44, in domain
    dom = self.xd.domain_lookup(x)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py",
line
524, in domain_lookup
    raise XendInvalidDomain(str(domid))
XendInvalidDomain: <Fault 3:
''1e9860a0-e244-a264-5b0a-321a0fe649ec''>
Traceback (most recent call last):
  File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py",
line
140, in process
    resource = self.getResource()
  File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py",
line
172, in getResource
    return self.getServer().getResource(self)
  File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py",
line
351, in getResource
    return self.root.getRequestResource(req)
  File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 
39, in getRequestResource
    return findResource(self, req)
  File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 
26, in findResource
    next = resource.getPathResource(pathElement, request)
  File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 
49, in getPathResource
    val = self.getChild(path, request)
  File "/usr/lib64/python2.5/site-packages/xen/web/SrvDir.py", line
71,
in getChild
    val = self.get(x)
  File 
"/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", 
line 52, in get
    return self.domain(x)
  File 
"/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", 
line 44, in domain
    dom = self.xd.domain_lookup(x)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py",
line
524, in domain_lookup
    raise XendInvalidDomain(str(domid))
XendInvalidDomain: <Fault 3: ''xp4''>
Running with no password
23/08/2007 11:09:34 Autoprobing TCP port
23/08/2007 11:09:34 Autoprobing selected port 5900
23/08/2007 11:09:35   other clients:
23/08/2007 11:09:35 Client Protocol Version 3.8
23/08/2007 11:09:35 Protocol version sent 3.8, using 3.8
23/08/2007 11:09:35 rfbProcessClientSecurityType: executing handler for 
type 1
23/08/2007 11:09:35 rfbProcessClientSecurityType: returning 
securityResult for client rfb versin >= 3.
8
23/08/2007 11:09:35 Pixel format for client 127.0.0.1:
23/08/2007 11:09:35   32 bpp, depth 8, big endian
23/08/2007 11:09:35   true colour: max r 255 g 255 b 255, shift r 24 g 
16 b 8
23/08/2007 11:09:35 Enabling NewFBSize protocol extension for client 
127.0.0.1
23/08/2007 11:09:35 Using raw encoding for client 127.0.0.1
23/08/2007 11:10:50 Client 127.0.0.1 gone
23/08/2007 11:10:50 Statistics             events    Transmit/ RawEquiv 
( saved)
23/08/2007 11:10:50  FramebufferUpdate   :    568 |         0/        0 
(  0.0%)
23/08/2007 11:10:50  raw                 :    568 | 175169312/175169312 
(  0.0%)
23/08/2007 11:10:50  TOTALS              :   1136 | 175169312/175169312 
(  0.0%)
23/08/2007 11:10:50 Statistics             events    Received/ RawEquiv 
( saved)
23/08/2007 11:10:50  PointerEvent        :     22 |       132/      132 
(  0.0%)
23/08/2007 11:10:50  FramebufferUpdate   :    569 |      5690/     5690 
(  0.0%)
23/08/2007 11:10:50  SetEncodings        :      1 |        12/       12 
(  0.0%)
23/08/2007 11:10:50  SetPixelFormat      :      1 |        20/       20 
(  0.0%)
23/08/2007 11:10:50  TOTALS              :    593 |      5854/     5854 
(  0.0%)
Xend started at Thu Aug 23 12:33:50 2007.
device eth0 already exists; can''t create bridge with the same name
set hello timer failed: No such file or directory
set forward delay failed: No such file or directory
set stp status failed: No such file or directory
Nothing to flush.
Xend started at Thu Aug 23 13:10:24 2007.
device eth0 already exists; can''t create bridge with the same name
set hello timer failed: No such file or directory
set forward delay failed: No such file or directory
set stp status failed: No such file or directory
Nothing to flush.
Running with no password
23/08/2007 13:26:58 Autoprobing TCP port
23/08/2007 13:26:58 Autoprobing selected port 5900
23/08/2007 13:27:00   other clients:
23/08/2007 13:27:00 Client Protocol Version 3.8
23/08/2007 13:27:00 Protocol version sent 3.8, using 3.8
23/08/2007 13:27:00 rfbProcessClientSecurityType: executing handler for 
type 1
23/08/2007 13:27:00 rfbProcessClientSecurityType: returning 
securityResult for client rfb versin >= 3.
8
23/08/2007 13:27:00 Pixel format for client 127.0.0.1:
23/08/2007 13:27:00   32 bpp, depth 8, big endian
23/08/2007 13:27:00   true colour: max r 255 g 255 b 255, shift r 24 g 
16 b 8
23/08/2007 13:27:00 Enabling NewFBSize protocol extension for client 
127.0.0.1
23/08/2007 13:27:00 Using raw encoding for client 127.0.0.1

===
[2007-08-23 15:37:31 2776] DEBUG (SrvDomain:76) Starting domain xp4 False
[2007-08-23 15:37:31 2776] DEBUG (XendDomainInfo:1463) 
XendDomainInfo.constructDomain
[2007-08-23 15:37:31 2776] DEBUG (balloon:113) Balloon: 7100988 KiB 
free; need 2048; done.
[2007-08-23 15:37:31 2776] DEBUG (XendDomain:443) Adding Domain: 5
[2007-08-23 15:37:31 2776] DEBUG (XendDomainInfo:1517) 
XendDomainInfo.initDomain: 5 256
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: boot, val: c
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: fda, val: None
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: fdb, val: None
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: soundhw, val: None
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: localtime, val: None
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: serial, val: pty
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: std-vga, val: None
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: isa, val: None
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: acpi, val: 1
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: usb, val: None
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: usbdevice, val: None
[2007-08-23 15:37:31 2776] DEBUG (image:330) args: k, val: None
[2007-08-23 15:37:31 2776] ERROR (XendDomainInfo:1584) 
XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last):
  File
"/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 1522, in _initDomain
    self.image = image.create(self, self.info)
  File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line
44,
in create
    return findImageHandlerClass(vmConfig)(vm, vmConfig)
  File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line
236,
in __init__
    ImageHandler.__init__(self, vm, vmConfig)
  File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line
75,
in __init__
    self.configure(vmConfig)
  File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line
250,
in configure
    self.dmargs = self.parseDeviceModelArgs(vmConfig)
  File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line
344,
in parseDeviceModelArgs
    vbdparam)
VmError: Disk image does not exist:
[2007-08-23 15:37:31 2776] ERROR (XendDomainInfo:416) VM start failed
Traceback (most recent call last):
  File
"/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 396, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendTask.py", line
209, in log_progress
    retval = func(*args, **kwds)
  File
"/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 1587, in _initDomain
    raise exn
VmError: Disk image does not exist:
[2007-08-23 15:37:31 2776] DEBUG (XendDomainInfo:1709) 
XendDomainInfo.destroy: domid=5
[2007-08-23 15:37:31 2776] DEBUG (XendDomainInfo:1726) 
XendDomainInfo.destroyDomain(5)
[2007-08-23 15:37:31 2776] ERROR (SrvBase:88) Request start failed.
Traceback (most recent call last):
  File "/usr/lib64/python2.5/site-packages/xen/web/SrvBase.py", line
85,
in perform
    return op_method(op, req)
  File 
"/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomain.py",
line
77, in op_start
    return self.xd.domain_start(self.dom.getName(), paused)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py",
line
994, in domain_start
    dominfo.start(is_managed = True)
  File
"/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 396, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendTask.py", line
209, in log_progress
    retval = func(*args, **kwds)
  File
"/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 1587, in _initDomain
    raise exn
VmError: Disk image does not exist:


Cheers,
Falk

Cole Robinson

2007-Aug-23 17:40 UTC

head link

Re: [Fedora-xen] Problems running xp guest

Falk Zimmermann wrote:
>     <disk type=''file''
device=''cdrom''>
>       <driver name=''file''/>
>       <source file=''''/>
>       <target dev=''hdc''/>
>       <readonly/>
>     </disk>

This section is what is causing the error. With windows guests, the
tools try to do some funky stuff so that windows can still have access
to the install cd for the second stage of the install (after the first
reboot.) It probably shouldn''t be erroring like that so there is a bug
somewhere, just not sure where in the chain it is.

In the interim, you can get your guest to work with access to your iso
image with:

- virsh dumpxml <xmdomain> > somefile.xml
- replace <source file=''''/> with <source
file=''/path/to/win.iso''/> in
the above block in somefile.xml
- virsh undefine <xmdomain>
- virsh define somefile.xml

If you don''t need access to the iso in the guest, you can go to the
details section of the domain in virt-manager and remove hdc, which will
get rid of the block of xml without needing to undefine/define.

- Cole

-- 
Cole Robinson
crobinso@redhat.com

Falk Zimmermann

2007-Aug-24 09:53 UTC

head link

Re: [Fedora-xen] Problems running xp guest

Thanks a lot, this fixed the problem.
Cheers,
Falk


Cole Robinson schrieb:> Falk Zimmermann wrote:
>
>   
>>     <disk type=''file''
device=''cdrom''>
>>       <driver name=''file''/>
>>       <source file=''''/>
>>       <target dev=''hdc''/>
>>       <readonly/>
>>     </disk>
>>     
>
> This section is what is causing the error. With windows guests, the
> tools try to do some funky stuff so that windows can still have access
> to the install cd for the second stage of the install (after the first
> reboot.) It probably shouldn''t be erroring like that so there is a
bug
> somewhere, just not sure where in the chain it is.
>
> In the interim, you can get your guest to work with access to your iso
> image with:
>
> - virsh dumpxml <xmdomain> > somefile.xml
> - replace <source file=''''/> with <source
file=''/path/to/win.iso''/> in
> the above block in somefile.xml
> - virsh undefine <xmdomain>
> - virsh define somefile.xml
>
> If you don''t need access to the iso in the guest, you can go to
the
> details section of the domain in virt-manager and remove hdc, which will
> get rid of the block of xml without needing to undefine/define.
>
> - Cole
>
>

Fedora xen - Aug 2007 - Problems running xp guest

[Fedora-xen] Problems running xp guest

Re: [Fedora-xen] Problems running xp guest

Re: [Fedora-xen] Problems running xp guest

Re: [Fedora-xen] Problems running xp guest

Re: [Fedora-xen] Problems running xp guest

Re: [Fedora-xen] Problems running xp guest

Re: [Fedora-xen] Problems running xp guest