Re: [Xen-devel] Failed to create a VM on -unstable

[Jun Koi <junkoi2004@xxxxxxxxx>]

On Wed, Jun 24, 2009 at 12:28 AM, Jun Koi<junkoi2004@xxxxxxxxx> wrote:
> On Mon, Jun 22, 2009 at 6:43 PM, Jun Koi<junkoi2004@xxxxxxxxx> wrote:
>> On Mon, Jun 22, 2009 at 5:38 PM, Jun Koi<junkoi2004@xxxxxxxxx> wrote:
>>> On Mon, Jun 22, 2009 at 4:44 PM, Keir Fraser<keir.fraser@xxxxxxxxxxxxx> 
>>> wrote:
>>>> On 22/06/2009 08:36, "Jun Koi" <junkoi2004@xxxxxxxxx> wrote:
>>>>
>>>>> Or do you think that the new version of Xen requires some change in below
>>>>> line:
>>>>>
>>>>> vif = ['type=ioemu']
>>>>>
>>>>>
>>>>> This same configuration works with older version 3.3.1.
>>>>
>>>> I think you should get rid of the dhcp= line from your config. It can't be
>>>> doing good.
>>>>
>>>
>>> Thanks, it is a bit better now - I dont see that error anymore.
>>> However, it still fails to create a VM, with the following report:
>>>
>>> "Error: Device 0 (vif) could not be connected. Hotplug scripts not working."
>>>
>>> And qemu log file is like below. I dont see much information, except
>>> that xs_read() failed. Do you have any idea?
>
> It seems people are busy on other things, so I am trying to track this
> down myself. I put some instrumented code into DevController.py, and
> it seems that the bug is caused when the console took too much time to
> process the request put into Xenstore (?).
>
> Is that because xenconsoled doesnt handle the request, or by something else?
>
> Anybody could give me some hints where to look at, so I can continue
> to chase this bug?
>
> I am using Ubuntu 9.04, python 2.6.2, if that matters.

I am using the latest code from unstable tree, C/S 19816:5f5112a7d2ff.

Thanks,
J

>
> BTW, my xend-debug.log has following messages. I am not sure what that
> means, and if it is important to this bug, or not.
>
> Thanks,
> J
>
> # cat /var/log/xen/xend-debug.log
> .....
> cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host0/model: No such file or directory
> cat: /sys/bus/scsi/devices/host0/type: No such file or directory
> cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host1/model: No such file or directory
> cat: /sys/bus/scsi/devices/host1/type: No such file or directory
> cat: /sys/bus/scsi/devices/host1/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host2/model: No such file or directory
> cat: /sys/bus/scsi/devices/host2/type: No such file or directory
> cat: /sys/bus/scsi/devices/host2/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/host3/model: No such file or directory
> cat: /sys/bus/scsi/devices/host3/type: No such file or directory
> cat: /sys/bus/scsi/devices/host3/rev: No such file or directory
> cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/target0:0:0/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/target0:0:0/model: No such file or directory
> cat: /sys/bus/scsi/devices/target0:0:0/type: No such file or directory
> cat: /sys/bus/scsi/devices/target0:0:0/rev: No such file or directory
> cat: /sys/bus/scsi/devices/target0:0:0/scsi_level: No such file or directory
> cat: /sys/bus/scsi/devices/target1:0:0/vendor: No such file or directory
> cat: /sys/bus/scsi/devices/target1:0:0/model: No such file or directory
> cat: /sys/bus/scsi/devices/target1:0:0/type: No such file or directory
> cat: /sys/bus/scsi/devices/target1:0:0/rev: No such file or directory
> cat: /sys/bus/scsi/devices/target1:0:0/scsi_level: No such file or directory
>
>
>
>
>
>
>
>
>
>>>
>>> Thanks,
>>> J
>>>
>>>
>>> domid: 1
>>> qemu: the number of cpus is 1
>>> config qemu network with xen bridge for  tap1.0 xenbr0
>>> Strip off blktap sub-type prefix to /home/xenvms/img.qcow2.ubuntu904
>>> (drv 'qcow2')
>>> Watching /local/domain/0/device-model/1/logdirty/next-active
>>> Watching /local/domain/0/device-model/1/command
>>> qemu_map_cache_init nr_buckets = 4000 size 327680
>>> shared page at pfn feffd
>>> buffered io page at pfn feffb
>>> Guest uuid = 9b962fea-e2ed-747c-fac7-1e8d23d3889f
>>> Time offset set 0
>>> populating video RAM at ff000000
>>> mapping video RAM from ff000000
>>> Register xen platform.
>>> Done register platform.
>>> xs_read(/vm/9b962fea-e2ed-747c-fac7-1e8d23d3889f/log-throttling): read error
>>> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw 
>>> state.
>>> xs_read(/local/domain/0/device-model/1/xen_extended_power_mgmt): read error
>>> xs_read(): vncpasswd get error.
>>> /vm/9b962fea-e2ed-747c-fac7-1e8d23d3889f/vncpasswd.
>>> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>>>
>>
>> It seems the reason is because VIF device (console in my case?) took
>> too much time to be initialized?
>> Below is the log from xend.log. Do you have any suggestion how to fix this?
>>
>> Thanks,
>> J
>>
>> .....
>> [2009-06-22 18:20:28 4595] DEBUG (DevController:95) DevController:
>> writing {'state': '1', 'backend-id': '0', 'backend':
>> '/local/domain/0/backend/console/2/0'} to
>> /local/domain/2/device/console/0.
>> [2009-06-22 18:20:28 4595] DEBUG (DevController:97) DevController:
>> writing {'domain': 'ubuntu904', 'frontend':
>> '/local/domain/2/device/console/0', 'uuid':
>> 'db9f2ab8-876a-5eae-bab2-9fb440abb427', 'frontend-id': '2', 'state':
>> '1', 'location': '3', 'online': '1', 'protocol': 'vt100'} to
>> /local/domain/0/backend/console/2/0.
>> [2009-06-22 18:20:28 4595] DEBUG (DevController:139) Waiting for devices vif.
>> [2009-06-22 18:20:28 4595] DEBUG (XendDomainInfo:1711)
>> XendDomainInfo.handleShutdownWatch
>> [2009-06-22 18:20:28 4595] DEBUG (DevController:144) Waiting for 0.
>> [2009-06-22 18:20:28 4595] DEBUG (DevController:657)
>> hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
>> [2009-06-22 18:22:08 4595] DEBUG (XendDomainInfo:2727)
>> XendDomainInfo.destroy: domid=2
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:2201) Destroying device 
>> model
>> [2009-06-22 18:22:09 4595] INFO (image:580) ubuntu904 device model terminated
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:2208) Releasing devices
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:2221) Removing vif/0
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:1137)
>> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:2221) Removing console/0
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:1137)
>> XendDomainInfo.destroyDevice: deviceClass = console, device =
>> console/0
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:2221) Removing vbd/768
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:1137)
>> XendDomainInfo.destroyDevice: deviceClass = tap, device = vbd/768
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:2221) Removing vfb/0
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:1137)
>> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:2206) No device model
>> [2009-06-22 18:22:09 4595] DEBUG (XendDomainInfo:2208) Releasing devices
>>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel