Ask Your Question
0

qemu instances missing -netdev switch

asked 2013-08-22 02:09:35 -0500

tudor gravatar image

updated 2013-08-22 18:23:38 -0500

For some reason my instances are no longer being patched into the internal OVS switch on Grizzly.

All services appear to be running ok, and instances start up ok also. However they are all missing a network device.

When I look at an instance log, my previously-working instances have a -netdev switch, e.g.

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name instance-00000005 -S -M pc-1.0 -cpu ...

-netdev tap,fd=25,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:c5:f1:6b,bus=pci.0,addr=0x3

....     -chardev file,id=charserial0,path=/var/lib/nova/instances/instance-00000005/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 .... -vnc 0.0.0.0:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5

However, now my instance have no such -netdev switch when they are called:

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name instance-00000011 -S -M pc-1.0 -cpu core2duo,+erms,+smep,+fsgsbase,+lahf_lm,+rdtscp,+rdrand,+f16c,+avx,+osxsave,+xsave,+aes,+tsc-deadline,+popcnt,+x2apic,+sse4.2,+sse4.1,+pcid,+pdcm,+xtpr,+cx16,+tm2,+est,+smx,+vmx,+ds_cpl,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds -enable-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -uuid e366f347-9f47-4bf9-a4eb-4567d4f9deb8 -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=2013.1.2,serial=a1378421-8208-e211-a941-0010185aae5d,uuid=e366f347-9f47-4bf9-a4eb-4567d4f9deb8 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-00000011.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/instances/e366f347-9f47-4bf9-a4eb-4567d4f9deb8/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -chardev file,id=charserial0,path=/var/lib/nova/instances/e366f347-9f47-4bf9-a4eb-4567d4f9deb8/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4

Here is my nova.conf:

[DEFAULT]
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
rootwrap_config=/etc/nova/rootwrap.conf
verbose=True

#dhcpbridge_flagfile=/etc/nova/nova.conf
#dhcpbridge=/usr/bin/nova-dhcpbridge
#fixed_range=10.0.0.0/8
#flat_network_bridge=br-eth1
#flat_interface=eth1
#flat_injected=False
#public_interface=eth0

# MySQL Connection #
sql_connection=mysql://nova:password@10.0.0.1/nova

# nova-scheduler #
rabbit_host=10.0.0.1
rabbit_password=password
scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler

# nova-api #
cc_host=10.0.0.1
auth_strategy=keystone
s3_host=10.0.0.1
ec2_host=10.0.0.1
nova_url=http://10.0.0.1:8774/v1.1/
ec2_url=http://10.0.0.1:8773/services/Cloud
keystone_ec2_url=http://10.0.0.1:5000/v2.0/ec2tokens
api_paste_config=/etc/nova/api-paste.ini
allow_admin_api=true
use_deprecated_auth=false ...
(more)
edit retag flag offensive close merge delete

Comments

What do you have for libvirt_vif_driver in nova.conf on the compute node?

darragh-oreilly gravatar imagedarragh-oreilly ( 2013-08-22 06:59:51 -0500 )edit

nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver . I've included my nova.conf in the question now, too.

tudor gravatar imagetudor ( 2013-08-22 18:24:27 -0500 )edit

Is this the nova.conf being used on the compute node? It has libvirt_type=qemu but /usr/bin/kvm is running?

darragh-oreilly gravatar imagedarragh-oreilly ( 2013-08-23 02:42:19 -0500 )edit

I changed this to libvirt_type=kvm (and nothing else) but still no netdev. :-(

tudor gravatar imagetudor ( 2013-08-26 00:03:58 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2013-09-12 20:43:37 -0500

tudor gravatar image

It seems that OpenStack won't create a network device if the network doesn't have a subnet! This doesn't throw an error. But when I created a subnet, the device was created.

I was trying to create a network where the IP address was assigned by a DHCP server externally, so specifying the subnet made no sense. I'm trying to understand how this use case is supposed to be implemented!

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-08-22 02:09:35 -0500

Seen: 496 times

Last updated: Sep 12 '13