Re: [Xen-users] xen-vnif.ko missing

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Mon, Nov 11, 2013 at 12:36:15PM +0530, Jaya Dhanesh wrote:
> I have attached the qemu logs here.
> ps aux did not have an entry for the vm I created.
> 

There should be a qemu process for your VM. Grepping for qemu doesn't
give you anything? It would be interesting to know the exact command
line of qemu process.

If qemu process crashes then there will not be one. But I cannot tell
from the log whether they crashed.

The main difference, as you stated in another email is that the working
VM has successfully registered Xen platform device. But the reason why
former one does register remains unknown.

Failing to register Xen platform device makes it impossible to
disconnect the emulated devices (disk, net, etc). That's why you're
seeing hda in working VM.

If would be better if you can provide more infomation such as VM config
file.

Wei.

> Thanks,
> Dhanesh.
> On 11/08/2013 07:47 PM, Wei Liu wrote:
> >On Fri, Nov 08, 2013 at 06:07:23PM +0530, Jaya Dhanesh wrote:
> >>Yes
> >Then probably 'ps aux | grep qemu' and logs from qemu are useful.
> >
> >>On 11/08/2013 06:05 PM, Wei Liu wrote:
> >>>On Fri, Nov 08, 2013 at 05:50:52PM +0530, Jaya Dhanesh wrote:
> >>>>Yes, but the same image on another system finds hda and is able to come 
> >>>>up.
> >>>Are you using the exact same version of Xen? Are you using the exact
> >>>same config file in both places?
> >>>
> >>>Wei.
> >>>
> >>>>On 11/08/2013 05:45 PM, Wei Liu wrote:
> >>>>>On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote:
> >>>>>[...]
> >>>>>>[    1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks:
> >>>>>>(8.58 GB/8.00 GiB)
> >>>>>>[    1.865438] sd 0:0:0:0: [sda] Write Protect is off
> >>>>>>[    1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache:
> >>>>>>enabled, doesn't support DPO or FUA
> >>>>>>[    1.899648]  sda: sda1 sda2
> >>>>>>[    1.902157] sd 0:0:0:0: [sda] Attached SCSI disk
> >>>>>sda1 it is
> >>>>>
> >>>>>Wei.
> 
> 

> domid: 327
> config qemu network with xen bridge for  tap327.0 intnet_tt.100
> config qemu network with xen bridge for  tap327.1 intnet_tt.100
> config qemu network with xen bridge for  tap327.2 intnet_tt.100
> config qemu network with xen bridge for  tap327.3 intnet_tt.100
> config qemu network with xen bridge for  tap327.4 intnet_tt.100
> config qemu network with xen bridge for  tap327.5 intnet_tt.100
> config qemu network with xen bridge for  tap327.6 intnet_tt.100
> config qemu network with xen bridge for  tap327.7 dbg_tt.100
> Using file /root/psv-plfm-app-sim-03/vsv-#ssrsim#SSR_SIM/sobj-tt1 in 
> read-write mode
> Watching /local/domain/0/device-model/327/logdirty/cmd
> Watching /local/domain/0/device-model/327/command
> Watching /local/domain/327/cpu
> char device redirected to /dev/pts/13
> qemu_map_cache_init nr_buckets = 10000 size 4194304
> /usr/src/packages/BUILD/xen-4.1.2-testing/tools/ioemu-dir/hw/xen_blktap.c:704:
>  Init blktap pipes
> shared page at pfn feffd
> buffered io page at pfn feffb
> Guest uuid = 94785e16-3f5d-2577-a8bb-695fa39b6119
> Time offset set 0
> populating video RAM at ff000000
> mapping video RAM from ff000000
> xs_read(/local/domain/0/device-model/327/xen_extended_power_mgmt): read error
> xs_read(): vncpasswd get error. 
> /vm/94785e16-3f5d-2577-a8bb-695fa39b6119/vncpasswd.
> Log-dirty: no command yet.
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> vcpu-set: watch node error.
> char device redirected to /dev/pts/17
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> cirrus vga map change while on lfb mode
> mapping vram to f0000000 - f0400000
> 

> domid: 8
> config qemu network with xen bridge for  tap8.0 intnet_tt.100
> config qemu network with xen bridge for  tap8.1 intnet_tt.100
> config qemu network with xen bridge for  tap8.2 intnet_tt.100
> config qemu network with xen bridge for  tap8.3 intnet_tt.100
> config qemu network with xen bridge for  tap8.4 intnet_tt.100
> config qemu network with xen bridge for  tap8.5 intnet_tt.100
> config qemu network with xen bridge for  tap8.6 intnet_tt.100
> config qemu network with xen bridge for  tap8.7 dbg_tt.100
> Using file /root/psv-linux-fzeq/vsv-#root#xen#13.2.79_image/sobj-ttool1 in 
> read-write mode
> Watching /local/domain/0/device-model/8/logdirty/cmd
> Watching /local/domain/0/device-model/8/command
> Watching /local/domain/8/cpu
> char device redirected to /dev/pts/6
> qemu_map_cache_init nr_buckets = 10000 size 4194304
> /usr/src/packages/BUILD/xen-4.1.2-testing/tools/ioemu-dir/hw/xen_blktap.c:704:
>  Init blktap pipes
> shared page at pfn feffd
> buffered io page at pfn feffb
> Guest uuid = 157e1ddb-3393-8364-ec5e-67e4ecc5e510
> Time offset set 0
> char device redirected to /dev/pts/7
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> populating video RAM at ff000000
> mapping video RAM from ff000000
> Register xen platform.
> Done register platform.
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw 
> state.
> xs_read(/local/domain/0/device-model/8/xen_extended_power_mgmt): read error
> xs_read(): vncpasswd get error. 
> /vm/157e1ddb-3393-8364-ec5e-67e4ecc5e510/vncpasswd.
> Log-dirty: no command yet.
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> vcpu-set: watch node error.
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xs_read(/local/domain/8/log-throttling): read error
> qemu: ignoring not-understood drive `/local/domain/8/log-throttling'
> medium change watch on `/local/domain/8/log-throttling' - unknown device, 
> ignored
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> cirrus vga map change while on lfb mode
> mapping vram to f0000000 - f0400000
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw 
> state.
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro 
> state.
> Disconnect IDE hard disk...
> Disconnect SCSI hard disk...
> Disconnect netifs...
> region type 0 at [f3000000,f3020000).
> squash iomem [f3000000, f3020000).
> region type 1 at [c100,c140).
> region type 0 at [f3020000,f3040000).
> squash iomem [f3020000, f3040000).
> region type 1 at [c140,c180).
> region type 0 at [f3040000,f3060000).
> squash iomem [f3040000, f3060000).
> region type 1 at [c180,c1c0).
> region type 0 at [f3060000,f3080000).
> squash iomem [f3060000, f3080000).
> region type 1 at [c1c0,c200).
> region type 0 at [f3080000,f30a0000).
> squash iomem [f3080000, f30a0000).
> region type 1 at [c200,c240).
> region type 0 at [f30a0000,f30c0000).
> squash iomem [f30a0000, f30c0000).
> region type 1 at [c240,c280).
> region type 0 at [f30c0000,f30e0000).
> squash iomem [f30c0000, f30e0000).
> region type 1 at [c280,c2c0).
> region type 0 at [f30e0000,f3100000).
> squash iomem [f30e0000, f3100000).
> region type 1 at [c2c0,c300).
> Shutdown taps...
> Done.
> Unknown PV product 65535 loaded in guest
> PV driver build 50334976
> 


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users