RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 590965 - Can not boot up guest after modprobe vhost_net then remove it
Summary: Can not boot up guest after modprobe vhost_net then remove it
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-11 05:38 UTC by Qunfang Zhang
Modified: 2010-06-30 04:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-11 05:52:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Qunfang Zhang 2010-05-11 05:38:04 UTC 
Description of problem:
vhost_net module is not loaded by default and we can boot up a guest successfully.
But, after modprobe it (still can boot up guest at this moment) and then remove it, the guest can not boot up with the following message:

warning: could not open /dev/net/tun: no virtual network emulation
qemu-kvm: -net tap,vlan=0,script=/etc/qemu-ifup,ifname=hello: Device 'tap' could not be initialized

Command line:
# /usr/libexec/qemu-kvm -m 2G -smp 2 -rtc-td-hack -usbdevice tablet -no-kvm-pit-reinjection  -drive file=win2k8-r2.qcow2,media=disk,if=ide,cache=off,werror=stop,rerror=stop -net nic,vlan=0,macaddr=1e:2d:0a:18:9f:4d,model=e1000 -net tap,vlan=0,script=/etc/qemu-ifup,ifname=hello -vnc :10 -monitor stdio -boot c -cpu qemu64,+sse2 -uuid b1428152-97b8-4bd3-a24c-16c91177fa31 -startdate now -balloon none -name 161


Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.51.el6.x86_64
kernel: 2.6.32-24.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Boot a guest with the above command line.
2.Add the vhost_net module.
#modprobe  vhost_net
#lsmod | grep vhost_net
3.Boot the guest again.
4.Remove the vhost_net module.
#modprobe -r vhost_net
#lsmod | grep vhost_net
5.Boot the guest again with the same command line.
  
Actual results:
After step 5, guest can not boot up.

warning: could not open /dev/net/tun: no virtual network emulation

Expected results:
Guest can boot up successfully all the time.

Additional info:
Comment 1 Qunfang Zhang 2010-05-11 05:52:47 UTC 
Sorry, I used "modprobe -r" that removed the "tun" module.  So, this is not a bug and I will close it.
Note You need to log in before you can comment on or make changes to this bug.