Requested operation is not valid: network 'default' is not active

最新推荐文章于 2025-08-21 08:56:20 发布

原创最新推荐文章于 2025-08-21 08:56:20 发布 · 5.5k 阅读

3 ·

CC 4.0 BY-SA版权

文章标签：

#kvm #debian #network #default #active

KVM 专栏收录该内容

3 篇文章

订阅专栏

本文解决在Debian系统中使用KVM部署虚拟机时遇到的default网络未激活问题。通过启动default网络，成功避免了network 'default' is not active的错误，确保virt-install命令正常运行。

错误信息

Debian系统通过KVM部署虚拟机，运行 virt-install 指定 --network network=default 的时候会出现下面的错误：

ERROR    Requested operation is not valid: network 'default' is not active

问题解决

确定virth环境中有default网络，如下：

root@bogon:/home/th# virsh net-list --all
 Name                 State      Autostart     Persistent
----------------------------------------------------------
 default              inactive   no            yes

start当前default网络
virsh net-start default

root@bogon:/home/th# virsh net-start default
Network default started

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

Ternence_Hsu

关注关注

1
点赞
踩
3

收藏

觉得还不错? 一键收藏
0
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

专栏目录

Securing Impala by Implementing Authentication and Auth：Kerberos Authentication Protocol

AI天才研究院

08-05

1574

Apache Impala (incubating) is a popular open-source distributed SQL query engine that provides high performance for large datasets stored in HDFS or Amazon S3 file systems. It has been widely used in enterprise data warehouses to process large volumes of d

kali kvm Requested operation is not valid: network 'default' is not active

weixin_33910759的博客

04-22

310

安装时候参考的：http://www.ilanni.com/?p=6101 今天安装完kvm，满是幸福的装了个xp，重启后出现了一个错误 Requested operation is not valid: network 'default' is not active详情： Details: Error starting domain: Requested operation i...

参与评论您还未登录，请先登录后发表或查看评论

Fix error:"Error starting domain: Requested operation is not valid: network 'default' is not active"

bless_forever的博客

04-01

4285

之前在Ubuntu中安装KVM的时候我并没有进行网络相关的配置，但是，在KVM中安装的系统是可以使用网络的，但是系统关机之后，今天在Virtual Meachine Manager中启动虚拟机时碰到了如下问题："Error starting domain: Requested operation is not valid: network 'default' is not active"解决方案的...

Error starting domain: Requested operation is not valid: network ‘default‘ is not active

良人眷的博客

10-12

1545

当某一天重启了server，kvm打不开虚拟机报这个错： Error starting domain: Requested operation is not valid: network 'default' is not active 是虚拟机默认网络没启动执行此命令可解决： sudo virsh net-start default 如下图为成功引用网上的第二个方案-解决方案二：在 /etc/libvirt/qemu/networks/default.xml中查看一下默认...

Linux KVM 启动虚拟机报错 error: Requested operation is not valid: network ‘default‘ is not active

想练武，就得下功夫

03-25

1295

这一期我们出一篇关于 Linux KVM 启动虚拟机报错解决的文章

RHCE（KVM——查看虚拟机）

金色%夕阳的博客

12-04

4101

4、连接至虚拟机要在 RHEL 8 中与虚拟机（VM）交互，您需要通过以下方法之一连接它：使用WEB控制台使用virt viewer应用程序和虚拟机图形界面交互如果不需要图形显示，请使用ssh终端连接当使用网络无法从系统连接到虚拟机，使用virsh控制台 ...

The operation, ‘DecodeJpeg/contents‘, does not exist in the graph.错误解决方法

weixin_44913038的博客

10-30

1968

在使用TensorFlow做inception v3 迁移训练是出现如下错误： TypeError: Cannot interpret feed_dict key as Tensor: The name ‘DecodeJpeg/contents:0’ refers to a Tensor which does not exist. The operation, ‘DecodeJpeg/contents’, does not exist in the graph. #12250 **错误原因：**在Tenso

Error: Failed to perform requested operation on instance "cirr", the instance has an error status: Please try again later [Error: 超过最大尝试次数。Exhausted all hosts available for retrying build failures for instance 2a850d2c-e586-4f35-8427-8ca4e4e69692.].

最新发布

12-24

No valid host found: [Failure: ...] # 资源不足 Failed to connect to AMQP server # RabbitMQ问题 ImageNotFound: Image ... not found # 镜像问题 ``` 6. **清理错误实例并重试** ```bash openstack ...

握手和证书验证在httpd模块请求入口那里就已经实现了对https的处理，这里是不是可以不用修改？基本上只要考虑事件推送pull point和basic notify相关，基于我前面给你的onvif协议上对此的规范，能不能重新给出完整的修改，分步骤，对每一步修改繇指出是根据协议规范上的哪一点来修改的？原因是什么？怎么修改？请根据协议重新对soap_tev.c和soap_event.c的代码进行修改——Real-time Pull-Point Notification Interface This section introduces the Real-time Pull-Point Notification Interface. This interface provides a firewall friendly notification interface that enables real-time polling and initiates all client communications. This interface is used in the following way: The client asks the device for a pull point with the CreatePullPointSubscriptionRequest message. The device evaluates the subscription request and returns either a CreatePullPointSubscriptionResponse or one of the Fault codes. If the subscription is accepted, the response contains a WS-EndpointReference to the instantiated pull point. This WS-Endpoint provides a PullMessages operation, which is used by the client to retrieve Notifications. Additionally it provides the Renew and Unsubscribe operations of the Base Subscription Manager Interface. The sequence diagram of the interaction is shown in Figure 6. Client Event Service CreatePullPoint SubscriptionRequest Instantiate CreatePullPoint SubscriptionResponse PullMessages Request PullPoint PullMessages Response Unsubscribe Request Unsubscribe Response Figure 6: Sequence diagram for the Real-time Pull-Point Notification Interface The device immediately responds with notifications that have been aggregated on behalf of the client. If there are no aggregated notifications, the device waits to respond until either a notification is produced for the client or the specified Timeout has exceeded. In any case, the response will contain, at most, the number of notifications specified by the MessageLimit parameter. The client can poll the notifications in real-time when it starts a new PullMessagesRequest immediately after each PullMessagesResponse. For a device implementation it is important to support multiple pull points (including multiple pullpoints per client) in order to allow precise event generation. If a device would only support one subscription at a time a client would need to subscribe without any scope restriction, because changing of event subscription is not possible. Hence this would require the device to serve all available events for which the device would have to activate all subsystems that generate events. This may cause unnecessary load by e.g. activating multiple motion detectors and similar without need. Additionally the traffic produced by all these events may cause a substantial network load. ONVIF™– 86 ONVIF Core Spec – Ver. 24.12 If the device supports persistent notification storage, see 9.1.7, the WS-Endpoint also provides a Seek opera tion. This operation allows to reposition the pull pointer into the past. With the Seek operation it is also possible to reverse the pull direction. There is also a BeginOfBuffer event, as defined in 9.11.1, that signals the start of the buffer. An ONVIF compliant device shall implement the Real Time Pull-Point Notification Interface. 9.1.1 Create pull point subscription An ONVIF compliant device shall provide the CreatePullPointSubscription command. If no Filter element is specified the pullpoint shall notify all occurring events to the client. By default the pull point keep alive is controlled via the PullMessages operation. In this case, after a PullMes sages response is returned, the subscription should be active for at least the timeout specified in the PullMes sages request. A device shall support an absolute time value specified in utc as well as a relative time value for the InitialTer minationTime parameter. A device shall respond both parameters CurrentTime and TerminationTime as utc using the ‘Z’ indicator. The following optional subscription policy elements are defined in tev:SubscriptionPolicy: • tev:ChangedOnly A pullpoint should not provide Initialized nor Deleted events for Properties. Both request and response message contain the same elements as the SubscriptionRequest and Response of [WS-BaseNotification] without the ConsumerReference. REQUEST: • Filter - optional [wsnt:FilterType] Optional filtering for e.g. topics. • InitialTerminationTime - optional [wsnt:AbsoluteOrRelativeTimeType] Initial termination time. • SubscriptionPolicy - optional [xs:any] RESPONSE: • SubscriptionReference [wsa:EndpointReferenceType] Endpoint reference of the subscription to be used for pulling the messages. • CurrentTime [xs:dateTime] Current time of the server for synchronization purposes. • TerminationTime [xs:dateTime] Date time when the PullPoint will be shut down without further pull requests. FAULTS: • The same faults as for Subscription Request of the [WS-BaseNotification] are used. ACCESS CLASS: READ_MEDIA 9.1.2 Pull messages The device shall provide the following PullMessages command for all SubscriptionManager endpoints returned by the CreatePullPointSubscription command. ONVIF™– 87 ONVIF Core Spec – Ver. 24.12 The device shall support a Timeout of at least one minute. The device shall not respond with a PullMessages FaultResponse when the MessageLimit is greater than the device supports. Instead, the device shall return up to the supported messages in the response. The response behavior shall be one of three types: • If there are one or more messages waiting (i.e., aggregated) when the request arrives, the device shall immediately respond with the waiting messages, up to the MessageLimit. The device shall not discard unsent messages, but shall await the next PullMessages request to send remaining messages. • If there are no messages waiting, and the device generates a message (or multiple simultaneous messages) prior to reaching the Timeout, the device shall immediately respond with the generated messages, up to the MessageLimit. The device shall not wait for additional messages before returning the response. • If there are no messages waiting, and the device does not generate any message prior to reaching the Timeout, the device shall respond with zero messages. The device shall not return a response with zero messages prior to reaching the Timeout. A device shall respond both parameters CurrentTime and TerminationTime as utc using the ‘Z’ indicator. After a seek operation the device shall return the messages in strict message utc time order. Note that this requirement is not applicable to standard realtime message delivery where the delivery order may be affected by device internal computations. A device should return an error (UnableToGetMessagesFault) when receiving a PullMessages request for a subscription where a blocking PullMessage request already exists. REQUEST: • Timeout [xs:duration] Maximum time to block until this method returns. • MessageLimit [xs:int] Upper limit for the number of messages to return at once. A server implementation may decide to return less messages. RESPONSE: • CurrentTime [xs:dateTime] The date and time when the messages have been delivered by the web server to the client. • TerminationTime [xs:dateTime] Date time when the PullPoint will be shut down without further pull requests. • NotificationMessage - optional, unbounded [wsnt:NotificationMessageHolderType] List of messages. This list shall be empty in case of a timeout. PULLMESSAGESFAULTRESPONSE: • MaxTimeout [xs:duration] Only when the Timeout exceeds the upper limit supported by the device. Not sent when the Message Limit is exceeded. The Fault Message shall contain the upper limits for both parameters. • MaxMessageLimit [xs:int] FAULTS: • No specific fault codes. ACCESS CLASS: READ_MEDIA ONVIF™– 88 ONVIF Core Spec – Ver. 24.12 9.1.3 Renew An ONVIF compliant device shall support this command if it signals support for [WS-Base Notification] via the MaxNotificationProducers capability. The command shall at least support a Timeout of one minute. A device shall respond both parameters Cur rentTime and TerminationTime as utc using the ‘Z’ indicator. REQUEST: • TerminationTime [wsnt:AbsoluteOrRelativeTimeType] The new relative or absolute termination time. RESPONSE: • CurrentTime [xs:dateTime] The current server time. • TerminationTime [xs:dateTime] The updated TerminationTime for the SubscriptionManager. RESOURCEUNKNOWNFAULTRESPONSE: • Timestamp [xs:dateTime] The pull point reference is invalid • Originator - optional [wsa:EndpointReferenceType] • ErrorCode - optional [xs:any] UNACCEPTABLETERMINATIONTIMEFAULTRESPONSE: • Timestamp [xs:dateTime] The Timeout exceeds the upper limit supported by the device. • Originator - optional [wsa:EndpointReferenceType] • ErrorCode - optional [xs:any] FAULTS: • No specific fault codes. ACCESS CLASS: READ_MEDIA 9.1.4 Unsubscribe The device shall provide the following Unsubscribe command for all SubscriptionManager endpoints returned by the CreatePullPointSubscription command. The command is defined in section 6.1.2 of [OASIS Web Ser vices Base Notification 1.3 [http://docs.oasis-open.org/wsn/wsn-ws_base_notification-1.3-spec-os.pdf]]. This command shall terminate the lifetime of a pull point. REQUEST: This is an empty message. RESPONSE: This is an empty message. ONVIF™– 89 ONVIF Core Spec – Ver. 24.12 RESOURCEUNKNOWNFAULTRESPONSE: • Timestamp [xs:dateTime] The pull point reference is invalid • Originator - optional [wsa:EndpointReferenceType] • ErrorCode - optional [xs:any] FAULTS: • No specific fault codes. ACCESS CLASS: READ_MEDIA 9.1.5 Seek A device supporting persistent notification storage as defined in section 9.1.7 shall provide the following Seek command for all SubscriptionManager endpoints returned by the CreatePullPointSubscription command. On a Seek a pullpoint shall abort any event delivery including any initial states of properties. Furthermore the pullpoint should flush events not already queued for transmission from the transmit queue. After a Seek request a pullpoint shall ignore the behavior described in section 9.6 for properties. A device shall only set the subscription in reverse pull mode if the Reverse argument is present and set to “true”. The UtcTime argument of the Seek request shall be matched against the UtcTime attribute of the notifications in the persistent notification storage. When Seek is used in the forward mode a device shall position the pull pointer to include all NotificationMes sages in the persistent storage with a UtcTime attribute greater than or equal to the Seek argument. When Seek is used in reverse mode a device shall position the pull pointer to include all NotificationMessages in the in the persistent storage with a UtcTime attribute less than or equal to the Seek argument. A device shall not provide information of the initial generate property state as response to a call to the Seek method. REQUEST: • UtcTime [xs:datetime] This message shall be addressed to a PullPoint in order to readjust the pull position: • Reverse - optional [xs:bool] RESPONSE: This is an empty message. FAULTS: • No specific fault codes. ACCESS CLASS: READ_MEDIA 9.1.6 Pull Point Lifecycle Figure 6 depicts the basic operation of a pull point. This chapter states the requirements on the pull point lifecycle. ONVIF™– 90 ONVIF Core Spec – Ver. 24.12 A device shall create a new pull point on each CreatePullPointSubscription command as long as the number of instantiated pull points does not exceed the capability MaxPullPoints. Each pull point shall have a unique endpoint reference to which the client can direct its consecutive operations on the pull point. A pull point shall exist until either its termination time has elapsed or the client has requested its disposal via an Unsubscribe request. There are no requirements regarding persistency of a pull point across a power cycle of a device. 9.1.7 Persistent notification storage To ensure that no notifications are lost by a client a device may store its notifications. The stored notifications can at any time be retrieved by a client. The device shall indicate if its support persistent notification storage with the PersistentNotificationStorage capability. See section 9.8. This specification defines that the interface to the persistent storage allows linear access via the originating message event time. This holds also for events that are delivered out of order in the live streaming case due to e.g. computational delay. The details of what notification and how and where those notifications actually are stored are outside the scope of this specification. Removal policy of stored notifications to get room for new ones is also out of scope. 9.2 Notification Streaming Interface This section defines the transmission of events via RTP streaming packets. For details regarding the configu ration see section “Metadata Configuration“ of the ONVIF Media Service Specification. The following requirements apply if a devices supports transmission of events via RTP streaming packets: • The events shall be encoded as wsnt:NotificationMessage as defined in [WS-BaseNotification] to trans port the Message Payload, the Topic and the ProducerReference. • Multiple instances of the wsnt:NotificationMessage elements can be placed within a metadata docu ment. • Since there is no explicit SubscriptionReference with streaming notifications, the wsnt:NotificationMes sage shall not contain the SubscriptionReference element. 9.3 Basic Notification Interface Section 9.3.1 briefly introduces the Basic Notification Interface of the [WS-BaseNotification] specification. Sec tion 9.3.2 summarizes the mandatory and the optional interfaces of the [WS-BaseNotification] specification. Please refer for a full documentation of the Basic Notification Interface to the [WS-BaseNotification] specifica tion. 9.3.1 Introduction The following logical entities participate in the notification pattern: Client: implements the NotificationConsumer interface. Event Service: implements the NotificationProducer interface. Subscription Manager: implements the BaseSubscriptionManager interface. The Event Service and the Subscription Manager should be instantiated on a device. Typical messages exchanged between the entities are shown in the sequence diagram in Figure 7. First, the client establishes a connection to the Event Service. The client can then subscribe for certain notifications by sending a SubscriptionRequest. If the Event Service accepts the Subscription, it dynamically instantiates a SubscriptionManager representing the Subscription. The Event Service shall return the WS-Endpoint-Address of the SubscriptionManager in the SubscriptionResponse. ONVIF™– 91 ONVIF Core Spec – Ver. 24.12 In order to transmit notifications matching the Subscription, another connection is established from the Event Service to the client. Via this connection, the Event Service sends a one-way Notify message to the Notifica tionConsumer interface of the client. Corresponding notifications can be sent at any time by the Event Service to the client, while the Subscription is active. To control the Subscription, the client directly addresses the SubscriptionManager returned in the Subscrip tionResponse. In the SubscriptionRequest the client can specify a termination time. The SubscriptionManager is automatically destroyed when the termination time is reached. RenewRequests can be initiated by the client in order to postpone the termination time. The client can also explicitly terminate the SubscriptionManager by sending an UnsubscribeRequest. After a successful Unsubscription, the SubscriptionManager no longer exists. The interaction between EventService and SubscriptionManager is not further specified by the [WS-BaseNo tification] and is up to the implementation of the device. Client Event Service SubscriptionRequest Instantiate SubscriptionResponse Notify RenewRequest RenewResponse Subscription Manager Notify UnsubscribeRequest UnsubscribeResponse Figure 7: Sequence diagram for the Base Notification Interface 9.3.2 Requirements This section details those interfaces of the [WS-BaseNotification] that a device shall provide. An ONVIF compliant device shall support the NotificationProducer Interface of the [WS-BaseNotification] if the capability MaxNotificationProducers is non-zero. The device shall support TopicExpression filters with the dialects described in 9.6.3. The support for MessageContent filters is signalled via the GetEventProperties method. If the device does not accept the InitialTerminationTime of a subscription, it shall provide a valid Ini tialTerminationTime within the Fault Message. The device shall be able to provide notifications using the Noti fy wrapper of the [WS-BaseNotification] specification. The SubscriptionPolicy wsnt:UseRaw is optional for the device. Although the [WS-BaseNotification] has CurrentTime and TerminationTime as optional elements in a SubscribeResponse and RenewResponse, an ONVIF compliant device shall list them in both SubscribeRe sponses and RenewResponse. The device may respond to any GetCurrentMessage request with a Fault mes sage indicating that no current message is available on the requested topic. An ONVIF compliant device shall implement the Base Subscription Manager Interface of the [WS-BaseNotifi cation] specification consisting of the Renew and Unsubscribe operations. The Pausable Subscription Manager Interface is optional. The implementation of Subscriptions as WS-Resources is optional. ONVIF™– 92 ONVIF Core Spec – Ver. 24.12 An ONVIF compliant device shall support time values in request parameters that are given in utc with the ‘Z’ indicator and respond all time values as utc including the ‘Z’ indicator

10-10

- 但既然HTTPD处理握手，可能不需要额外存储，直接在发送时检查soap->is_https。具体代码修改步骤： - **soap_tev.c修改**： - 在CreatePullPointSubscriptionHandler：生成端点引用时，使用https（如果请求是...

kvm虚拟机启动域时出错：Requestedoperationis not valid: network ‘default‘ is not active

u013317172的博客

10-04

2395

kvm虚拟机启动报错

Requested operation is not valid: network ‘default‘ is not active

啊渊的专栏

03-28

435

我在安装KVM时并没有进行网络配置。安装完成并且添加虚拟机后，在启动虚拟机是出现了如下问题： Requested operation is not valid: network 'default' is not active 解决方案： virsh net-autostart default virsh net-start default 再次开启虚拟机，问题解决。 KVM虚拟启动失败的办法。 ...

KVM启动虚拟机时报错Requested operation is not valid: network ‘default‘ is not active

Gremlins的博客

11-29

4796

在启动KVM虚拟机时，发生了如下错误启动域时出错：Requested operation is not valid: network ‘default’ is not active 原因是虚拟机默认网络未激活，解决办法如下： $ sudo virsh net-start default $ sudo virsh net-autostart default 处理完毕系统即可正常启动 ...

KVM Requested operation is not valid: network ‘default‘ is not active

Funning的博客

01-25

407

打开虚拟机报错：Requested operation is not valid: network ‘default’ is not active 虚拟机信息界面删除网卡重新创建网卡即可

ERROR Requested operation is not valid: network ‘default‘ is not active Domain installation does

完颜振江

08-21

1144

你的问题是由于libvirt 的 default 网络未启用导致的。之后就能正常创建 Ubuntu 虚拟机了。如有其他问题（如显卡、桥接网络、cloud-init 等），也可以继续问我！表示你的虚拟机（由运行）正在监听5900 端口，但只绑定在127.0.0.1（本地回环）上只有本机可以通过访问图形界面。外部主机无法通过你的服务器IP:5900访问 VNC。你想改成监听，即允许所有网络接口访问，这是很常见的需求（比如远程安装系统时用 VNC 客户端连接）。要让虚拟机的 VNC 监听0.0.0.0。

使用qume启动虚拟机的时候出现：“启动域时出错: Requested operation is not valid: network ‘default‘ is not active”

xdg15294969271的博客

11-02

2083

1、问题描述 2、解决方案 sudo virsh net-list sudo virsh net-start default sudo virsh net-list 此时就能成功启动了

Can‘t start KVM guest: “network ‘default‘ is not active“

weixin_39833509的博客

09-18

264

First, confirm that the default network is indeed inactive: sudo virsh net-list --all If so, start the default network: sudo virsh net-start default Run the first command line again to see if it worked.

#Centos7.4#Linux虚拟机KVM配置网卡【Requested operation is not valid: network 'br0' is not active】...

dengtuo3787的博客

12-20

559

案例：【20181218 10:25 事故描述】 jump宿主机服务器172.16.20.16死机，联系机房管理员重启，拨通机房vpn后ssh连接不上【20181219 11:25 现场问题排查】网卡显示ip是172.16.20.161，没有kvm桥接网卡br0，启动kvm虚拟机报错：Requested operation is not valid: network '...

解决：error:Requested operation is not valid: network 'ovs-network' is not active

鱼爻

11-19

2290

启动KVM虚拟机时报错的。显示的是网桥挂了，重启就好。 virsh net-list --all # 查看所有网桥，启动目标虚拟机失败，失败信息显示网桥断掉了 virsh net-start ovs-network #启动所断掉的网桥，并查看状态是否连接成功 virsh start XXXX_new # 启动虚拟机这样就OK了 ...

libvirt kvm error: Requested operation is not valid: can't undefine transient network

06-07

这个错误消息通常是由于尝试删除或未定义一个... virsh net-destroy NETWORK_NAME virsh net-undefine NETWORK_NAME ``` 如果您仍然遇到问题，请提供更多上下文信息，例如操作系统、libvirt和KVM版本、网络配置等。

Requested operation is not valid: network 'default' is not active

错误信息

问题解决

更多参考