On Jul 9, 2011, at 6:24 AM, kcobler@xxxxxxxxxxxxxx wrote:
> I've used xm new basic.cfg to add the domain to Xen management.
>
> Ken Cobler
Ah, yes.
Well, it keeps basic in `xm list` now, but when I start it I tend to get the
same output, but this time I only get that qemu-dm failure line only once:
---
domid: 8
Using xvda for guest's hda
Using file /var/xen/iso/finnix-101.iso in read-only mode
Watching /local/domain/0/device-model/8/logdirty/cmd
Watching /local/domain/0/device-model/8/command
Watching /local/domain/8/cpu
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 54084c29-56ef-d5b3-7573-bc74d6232071
Time offset set 0
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
Using xvda for guest's hda
medium change watch on `xvda' (index: 0): /var/xen/iso/finnix-101.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
char device redirected to /dev/pts/3
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
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
----
Also, when I start with 'xl', I get basically the same thing, only it tries it
a number of times before giving up.
-Sam
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home