qemu-devel
[Top][All Lists]
Advanced

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

[Qemu-devel] nic is lost, in the virtual machine running


From: melolinux
Subject: [Qemu-devel] nic is lost, in the virtual machine running
Date: Sat, 19 Jul 2014 15:31:00 +0800 (CST)

Hi all:

Problem description.

1. /usr/bin/qemu-system-x86_64 -machine accel=kvm -name a58970a2-10aa-4973-9261-7384b2f53221 -S -machine pc-0.14,accel=kvm,usb=off -m 4096 -smp 4,sockets=1,cores=4,threads=1 -uuid f3a2217f-ae5c-461b-a922-d37a3a98edc6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/a58970a2-10aa-4973-9261-7384b2f53221.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/dev/493bdd93-6eb4-4499-a344-99cd0abef251/95eb250a-05ab-4da1-8673-8a616b4d0a6e,if=none,id=drive-ide0-0-0,format=qcow2,cache=writeback -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/dev/493bdd93-6eb4-4499-a344-99cd0abef251/27d2df8a-dc00-4f6a-8669-f5dffc7a92d8,if=none,id=drive-ide0-0-1,format=qcow2,cache=writeback -device ide-hd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -netdev tap,ifname=tapa589700,script=no,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=c6:b0:5c:de:54:39,bus=pci.0,addr=0x3 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=10.9.40.213,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=9437184 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6


2. Problem found :the client can't find the network device (It takes a long time since we create the vm)

3. we use "qemu-monitor-commond --hmp xx info pci" to check it and find that we lost the ethernet controller.

4. we reboot it and it is back to normal


It is a pity that we can not found the retrieval methods.  It happened twice in one month.
What causes this problem ? Is there any connecton between "spice" and this problem?

Looking forward to your reply.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]