[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] PVHVP guest launches ok and is completely usable, but what are these multiple errors in the startup qemu-dm-test.log ?


  • To: xen-users@xxxxxxxxxxxxx
  • From: suse.dev@xxxxxx
  • Date: Mon, 25 Jan 2016 09:49:08 -0800
  • Delivery-date: Mon, 25 Jan 2016 17:50:24 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

I'm runing Xen 4.6.0 Dom0, linux64.

I'm launching a PVHVM guest, linux64 too.

The guest .cfg includes

        builder = 'hvm'
        xen_platform_pci = 1
        device_model_version = "qemu-xen-traditional"
        boot = 'cd'
        hdtype = 'ahci'
        disk = ['phy:/dev/VG0/TEST,hda,w',]
        vif = ['mac=00:16:3E:09:00:01, bridge=br0, vifname=vif0, model=e1000',]
        videoram = 16
        vga = 'stdvga'
        vnc = 0
        vnclisten = '0.0.0.0'
        vncdisplay = 1
        vncpasswd = 'mypass'
        vcpus = 1
        cpus = "1-3"
        ...

I launch it with

        xl create test.cfg

The DomU comes completely up, I can get to it with SSH, and everything 'inside' 
seems to work.

But when I look in the log for the guests startup, I see some errors

        tail -f /var/log/xen/qemu-dm-test.log
                domid: 42
                Using file /dev/VG0/TEST in read-write mode
                Watching device-model/42/logdirty/cmd
                Watching device-model/42/command
                Watching /local/domain/42/cpu
                char device redirected to /dev/pts/3
                qemu_map_cache_init nr_buckets = 10000 size 4194304
                shared page at pfn feffd
                buffered io page at pfn feffb
                Guest uuid = 223f9dc5-43b5-4e96-9ae7-4815095e378a
                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(device-model/42/xen_extended_power_mgmt): read error
??              xs_read(): vncpasswd get error. 
/vm/223f9dc5-43b5-4e96-9ae7-4815095e378a/vncpasswd.
                Log-dirty: no command yet.
??              I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, 
size: 0
                vcpu-set: watch node error.
??              [xenstore_process_vcpu_set_event]: /local/domain/42/cpu has no 
CPU!
                xs_read(/local/domain/42/log-throttling): read error
??              qemu: ignoring not-understood drive 
`/local/domain/42/log-throttling'
??              medium change watch on `/local/domain/42/log-throttling' - 
unknown device, ignored
                vga s->lfb_addr = f0000000 s->lfb_end = f1000000 
                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.

Are these errors really errors, or warnings?

What should I do to 'fix' them?

Thanks.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.