Seems the issue is not fully resolved.
Save/restore on 64bist host may cause guest to kernel panic.
Here is the snapshot:
https://sourceforge.net/tracker/download.php?group_id=180599&atid=893831&file_id=259112&aid=1824525
And following error message will be found in dmesg:
device sw0 entered promiscuous mode
Bad page state in process 'qemu-system-x86'
page:ffff81023f51e1c0 flags:0x0200000000000004 mapping:0000000000000000
mapcount:0 count:-1
Trying to fix it up, but a reboot is needed
Backtrace:
Call Trace:
[<ffffffff802397db>] recalc_sigpending+0xe/0x25
[<ffffffff8025a722>] bad_page+0x63/0x8d
[<ffffffff8025b42f>] get_page_from_freelist+0x2d9/0x47e
[<ffffffff80312cd6>] nfs_pagein_one+0xb8/0xff
[<ffffffff803130ed>] nfs_readpages+0x16e/0x17f
[<ffffffff8025b742>] __alloc_pages+0x61/0x2b5
[<ffffffff8025cf7f>] __do_page_cache_readahead+0xa1/0x217
[<ffffffff80559af0>] thread_return+0x0/0xea
[<ffffffff80545984>] call_transmit+0x201/0x22d
[<ffffffff8025d148>] blockable_page_cache_readahead+0x53/0xb2
[<ffffffff8025d229>] make_ahead_window+0x82/0x9e
[<ffffffff8025d3cf>] page_cache_readahead+0x18a/0x1c1
[<ffffffff8025792d>] do_generic_mapping_read+0x135/0x406
[<ffffffff80256f06>] file_read_actor+0x0/0xf1
[<ffffffff8025939e>] generic_file_aio_read+0x119/0x157
[<ffffffff8027b670>] do_sync_read+0xc9/0x10c
[<ffffffff8024255f>] autoremove_wake_function+0x0/0x2e
[<ffffffff8023aade>] group_send_sig_info+0x62/0x6f
[<ffffffff80245ac5>] getnstimeofday+0x32/0x8d
[<ffffffff80244c65>] ktime_get_ts+0x1a/0x4e
[<ffffffff8027bde2>] vfs_read+0xaa/0x132
[<ffffffff8027c265>] sys_pread64+0x50/0x70
[<ffffffff8020935e>] system_call+0x7e/0x83
apic write: bad size=1 fee00030
Ignoring de-assert INIT to vcpu 0
tap0: no IPv6 routers present
sw0: port 2(tap0) entering disabled state
device tap0 left promiscuous mode
sw0: port 2(tap0) entering disabled state
device sw0 left promiscuous mode
device tap0 entered promiscuous mode
sw0: port 2(tap0) entering learning state
sw0: topology change detected, propagating
sw0: port 2(tap0) entering forwarding state
apic write: bad size=1 fee00030
Ignoring de-assert INIT to vcpu 0
device sw0 entered promiscuous mode
tap0: no IPv6 routers present
sw0: port 2(tap0) entering disabled state
device tap0 left promiscuous mode
sw0: port 2(tap0) entering disabled state
device sw0 left promiscuous mode
device tap0 entered promiscuous mode
sw0: port 2(tap0) entering learning state
sw0: topology change detected, propagating
sw0: port 2(tap0) entering forwarding state
apic write: bad size=1 fee00030
Ignoring de-assert INIT to vcpu 0
tap0: no IPv6 routers present
sw0: port 2(tap0) entering disabled state
device tap0 left promiscuous mode
sw0: port 2(tap0) entering disabled state
device tap0 entered promiscuous mode
sw0: port 2(tap0) entering learning state
sw0: topology change detected, propagating
sw0: port 2(tap0) entering forwarding state
apic write: bad size=1 fee00030
Ignoring de-assert INIT to vcpu 0
tap0: no IPv6 routers present
>-----Original Message-----
>From: Avi Kivity [mailto:[EMAIL PROTECTED]
>Sent: 2007年12月19日 14:30
>To: Zhao, Yunfeng
>Cc: kvm-devel
>Subject: Re: [kvm-devel] KVM Test result, kernel 5ca24d9.., userspace 120e0c8..
>
>Zhao, Yunfeng wrote:
>> Retested it on KVM-57.
>> It has been fixed already.
>>
>
>Actually, the fix is post kvm-57. What kvm-userspace.git commit did you
>test?
>
>--
>error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
