Port-xen archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: issues upgrading to 4.13
On Mon, Jan 18, 2021 at 11:55:15AM +1300, Mark Davies wrote:
>
>
> On 17/01/21 10:57 pm, Manuel Bouyer wrote:
> >> 1) xenstored is running at around 99% cpu, previously it hardly registered.
> >
> > I'm not seeing this. Not sure how to debug it; maybe try a ktrace
> > to see what it's doing ?
>
>
> ktrace shows its in a loop polling
>
> [...]
> 330 1 xenstored poll(0x7088c821b000, 0x69, 0xffffffff) = 88
> 330 1 xenstored __clock_gettime50(0x3, 0x7f7fff951db0) = 0
> 330 1 xenstored poll(0x7088c821b000, 0x69, 0xffffffff) = 88
> 330 1 xenstored __clock_gettime50(0x3, 0x7f7fff951db0) = 0
> 330 1 xenstored poll(0x7088c821b000, 0x69, 0xffffffff) = 88
> 330 1 xenstored __clock_gettime50(0x3, 0x7f7fff951db0) = 0
> 330 1 xenstored poll(0x7088c821b000, 0x69, 0xffffffff) = 88
> 330 1 xenstored __clock_gettime50(0x3, 0x7f7fff951db0) = 0
> 330 1 xenstored poll(0x7088c821b000, 0x69, 0xffffffff) = 88
> 330 1 xenstored __clock_gettime50(0x3, 0x7f7fff951db0) = 0
> [...]
looks like a descriptor that appears always ready when there's nothing to
do with it. I fear this will requires getting in the code to debug.
>
> >> The qemu-dm-XXX.log reports lots of:
> >> qemu-system-i386: failed to create 'qdisk' device '5632': no dev parameter
> >
> > I've also been migrating HVM guests from 4.11 to 4.13 and I've not
> > seen this. It's probably related to your disk = parameter;
> > what do you have ?
>
> I still had cdrom entries from when the machines were set up, removing
> that helped. Also the IP config had been statically configured on the
> machines and appears to have disappeared (change of driver?) - setting
> up dhcp for them got them on the network again.
Yes, it's possible that the qemu change appears as a hardware change for
the guest OS.
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index