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

Re: Network driver domain broken


  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: Andrea Stevanato <andrea.stevanato@xxxxxxxxxxxxxxx>
  • Date: Mon, 7 Mar 2022 15:43:52 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=santannapisa.it; dmarc=pass action=none header.from=santannapisa.it; dkim=pass header.d=santannapisa.it; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=6BMQLzh96Zx8smPPl/rUox3+iY+cxCT4cwG9pFYH1PM=; b=ZuM5IALBV84oIxjQMf6O7+HoPja3THh9zDocEm/tP8Vn9+xPWr15SzkNpgA85BKkqHbJw0HbfE6UdPfqz8NoWNIlkdOIbPfgEG0iJZgq1p/HDuUU67O2FoJ17E084ZVXQX2hPp7BMgwGk2H1rFQoQyf7SpWPNHguXIy2KuBA1UaGu6XnDyCV5BZQ3ZhrhU1aIxecTm6RnkDcRXt+WoEBOPANj9pLIPVTll9c/TSmnPk9o8sxD5xp2Cy1OWW9bx4s1mJOSo4vFZOW1N5y5wf+qjzJedrtQwBDrGwH4fRz7veRZhprlWWjGcthP+a357NOZMM137q0R0mydXPfg+tgYQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RrTK3Uz/L6kXO5cmYt5UysZPMhJj3oxo+hdFsJUYyH5mmHGW+oncC1XTxEcPuWBHQfoSjntJOCahLDVF5ehUlpRVVQN1CPg9BoAsret4e5Six3U2ln3Vy5TBvLsyeJboAmn4Ef53oYNLI9T7kFJZ9QGwTJqThgaLFelKUAHFHIktuMVfuc9mJcXNzNzma1Td67J5e3SXjOg124PE6nvyCXQZNImaEwn5pugbmuwPI04fTAzMmLXAjbp4hU5RZJpc0eOf6dlzsAOB2Ioqw/YQ86CRRwbULEAihwkZkc4v5ILAR8hrezIMV4njW8Z/8KWTD/DM57YiFKGi3SuT9byqtg==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=santannapisa.it;
  • Cc: Jason Andryuk <jandryuk@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "wl@xxxxxxx" <wl@xxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • Delivery-date: Mon, 07 Mar 2022 14:44:14 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 3/7/2022 3:36 PM, Jan Beulich wrote:
> On 07.03.2022 15:20, Andrea Stevanato wrote:
>> On 3/7/2022 12:46 PM, Roger Pau Monné wrote:
>>> On Mon, Mar 07, 2022 at 12:39:22PM +0100, Andrea Stevanato wrote:
>>>> /local/domain/2 = ""   (n0,r2)
>>>> /local/domain/2/vm = "/vm/f6dca20a-54bb-43af-9a62-67c55cb75708"   (n0,r2)
>>>> /local/domain/2/name = "guest1"   (n0,r2)
>>>> /local/domain/2/cpu = ""   (n0,r2)
>>>> /local/domain/2/cpu/0 = ""   (n0,r2)
>>>> /local/domain/2/cpu/0/availability = "online"   (n0,r2)
>>>> /local/domain/2/cpu/1 = ""   (n0,r2)
>>>> /local/domain/2/cpu/1/availability = "online"   (n0,r2)
>>>> /local/domain/2/memory = ""   (n0,r2)
>>>> /local/domain/2/memory/static-max = "1048576"   (n0,r2)
>>>> /local/domain/2/memory/target = "1048577"   (n0,r2)
>>>> /local/domain/2/memory/videoram = "-1"   (n0,r2)
>>>> /local/domain/2/device = ""   (n0,r2)
>>>> /local/domain/2/device/suspend = ""   (n0,r2)
>>>> /local/domain/2/device/suspend/event-channel = ""   (n2)
>>>> /local/domain/2/device/vif = ""   (n0,r2)
>>>> /local/domain/2/device/vif/0 = ""   (n2,r1)
>>>> /local/domain/2/device/vif/0/backend = "/local/domain/1/backend/vif/2/0"
>>>> (n2,r1)
>>>> /local/domain/2/device/vif/0/backend-id = "1"   (n2,r1)
>>>> /local/domain/2/device/vif/0/state = "6"   (n2,r1)
>>>> /local/domain/2/device/vif/0/handle = "0"   (n2,r1)
>>>> /local/domain/2/device/vif/0/mac = "00:16:3e:07:df:91"   (n2,r1)
>>>> /local/domain/2/device/vif/0/xdp-headroom = "0"   (n2,r1)
>>>> /local/domain/2/control = ""   (n0,r2)
>>>> /local/domain/2/control/shutdown = ""   (n2)
>>>> /local/domain/2/control/feature-poweroff = "1"   (n2)
>>>> /local/domain/2/control/feature-reboot = "1"   (n2)
>>>> /local/domain/2/control/feature-suspend = ""   (n2)
>>>> /local/domain/2/control/sysrq = ""   (n2)
>>>> /local/domain/2/control/platform-feature-multiprocessor-suspend = "1"
>>>> (n0,r2)
>>>> /local/domain/2/control/platform-feature-xs_reset_watches = "1"   (n0,r2)
>>>> /local/domain/2/data = ""   (n2)
>>>> /local/domain/2/drivers = ""   (n2)
>>>> /local/domain/2/feature = ""   (n2)
>>>> /local/domain/2/attr = ""   (n2)
>>>> /local/domain/2/error = ""   (n2)
>>>> /local/domain/2/error/device = ""   (n2)
>>>> /local/domain/2/error/device/vif = ""   (n2)
>>>> /local/domain/2/error/device/vif/0 = ""   (n2)
>>>> /local/domain/2/error/device/vif/0/error = "1 allocating event channel"
>>>> (n2)
>>>
>>> That's the real error. Your guest netfront fails to allocate the event
>>> channel. Do you get any messages in the guest dmesg after trying to
>>> attach the network interface?
>>
>> Just these two lines:
>>
>> [  389.453390] vif vif-0: 1 allocating event channel
>> [  389.804135] vif vif-0: 1 allocating event channel
> 
> Well, these are the error messages, from xenbus_alloc_evtchn().
> What's a little odd is that the error code is positive, but that's
> how -EPERM is logged. Is there perhaps a strange or broken XSM
> policy in use? I ask because evtchn_alloc_unbound() itself
> wouldn't return -EPERM afaics.

As you can see I'm pretty new to Xen. Furthermore, it is the first
time that I heard about XSM, so since I did not change anything I
do not know what to answer! The only thing that I can tell is that
for both dom0 and guests I'm using the same exact kernel and rootfs.
 
> Jan

Cheers,
Andrea



 


Rackspace

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