** Changed in: qemu
Assignee: (unassigned) => Michael liu (ztehypervisor)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1586611
Title:
usb-hub can not be detached when detach usb device f
** Description changed:
I give a host usb device to guest in the way of using "virsh attach-device"
cmd. In guest os,use "lsusb" cmd I can see two devices have been added,one is
usb device and the other is usb-hub（0409:55aa NEC Corp. Hub）.
when I use "virsh detach-device" detach the usb
Of course using virtual usb controller is normal,The situation of the
problems is to use the passthrough usb devices
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1586611
Title:
usb-hub can not be
Try detach the usb-hub device by the virsh detach-device usb-hub.xml?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1586611
Title:
usb-hub can not be detached when detach usb device from VM
I found that when I attached an usb device to the VM, the VM would add an
usb-hub automatically if there was no usb-hub.
After adding an usb-hub,the VM assigned a port to the actual usb device. When
detaching the usb device,the qemu only detach the port,without detaching the
usb-hub.So when
You can try to copy the image file from source to destination before
migration.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/797905
Title:
virsh live migration
Status in QEMU:
New
Bug
This is a qemu emulator problem, whould qemu stop when the memory is
larger than 128M? You can try set the memory 256 to start vm.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/682360
Title:
what a zero-length file means? Run the following command to see
qemu-img info foo.img
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/567380
Title:
qemu-img fails to create images >= 4G
Status in
Public bug reported:
I give a host usb device to guest in the way of passthrough,use "virsh
attach-device" cmd. In guest os,use "lsusb" cmd I can see two devices have been
added,one is usb device and the other is usb-hub（0409:55aa NEC Corp. Hub）.
when I use "virsh detach-device" detach the usb
Public bug reported:
I give a host usb device to guest in the way of using "virsh attach-device"
cmd. In guest os,use "lsusb" cmd I can see two devices have been added,one is
usb device and the other is usb-hub（0409:55aa NEC Corp. Hub）.
when I use "virsh detach-device" detach the usb device,in
Public bug reported:
magnum is running on centos7,
magnum baymodel-create --name k8sbaymodel5 --image-id fedora-23-atomic-20160405
--keypair-id testkey --external-network-id public --dns-nameserver 8.8.8.8
--flavor-id m1.small --coe kubernetes --docker-volume-size 5
magnum bay-create --name
Public bug reported:
magnum running on centos7,
I didn't create any services on k8s cluster,
but I got the result as follows:
[root@localhost ~(keystone_admin)]# magnum coe-service-list --bay k8sbay3
ERROR: Field `ports[0][node_port]' cannot be None (HTTP 500) (Request-ID:
Public bug reported:
create a virtual machine and start by libvirt. vm startup failed, qemu
returned "kvm run failed Bad address"
the error log is :
error: kvm run failed Bad address
EAX=7ffc EBX=7ffbffd0 ECX=fff0 EDX=002c
ESI=6f5c EDI=7ffbffd0 EBP=7ffc ESP=6f34
the vm bios is seabios. see the seabios,it queue size config 256,can not
change.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1575561
Title:
config qemu virtio_queue_size to 1024，create vm boot
but vm by other boot type ,such as dev='hd', can use virtio_queue_size =
1024
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1575561
Title:
config qemu virtio_queue_size to 1024，create vm boot from
Public bug reported:
config qemu virtio_queue_size to 1024，create vm boot from network failed。
in the vm vncviewer，see the error log：
“ERROR queue size 1024 > 256
could not open net0: no such file or directory"
** Affects: qemu
Importance: Undecided
Status: New
--
You received
How about the qemu process，in which state？ will it be blocking？
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/584514
Title:
Qemu-KVM 0.12.4 Guest entered Paused State
Status in QEMU:
New
Bug
http://patchwork.ozlabs.org/patch/293580/
In this patch，when KVM_CAP_NR_MEMSLOTS is implemented ，Convert the static
slots array to
be dynamically allocated, supporting more slots when available.
But how many slots we can use，the number is limited by the host kernel？Do any
one has the same
It's not safe for VM.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1485010
Title:
qemu-guest-agent should support systemd in addition to pmutils
Status in QEMU:
New
Bug description:
Hello,
You can do some performance optimization , such as isolating cpus, closing
selinux, closing nmi_watchdog, disable intel_pstate and so on. You can try such
grub cmdline:
nmi_watchdog=0 selinux=0 intel_pstate=disable nosoftlockup isolcpus=4,5,6,7
nohz_full=4,5,6,7
--
You received this bug
You should use qemu 2.5.0.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1495380
Title:
Invalid parameter 'queues'. multi-queue vhost-user backends does not
work.
Status in QEMU:
New
Bug
Maybe you detach disk too fast.When you detach disk,the guest os maybe
has not loaded the hotplug modules.So it can not detect your detach
event.Can you test the situation when detaching disk after guest os
starting up ?
--
You received this bug notification because you are a member of qemu-
when the second VM crashed,how about first VM? It seems like that you
use vhost-user as your backend type.Does the backend of the 1st VM and
2nd VM connect the same switch ?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
The VM has been shut off by hypervisor，so nova would use
heal_instance_state function to reboot the VM.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1574572
Title:
config 20 sriov direct bond
Public bug reported:
nova log：
2016-04-08 09:57:48.640 5057 INFO nova.compute.manager [req-
4e1b4d70-62b6-4158-8413-3c9f226fd13b - - - - -] report
alarm_instance_shutoff success
2016-04-08 09:57:48.712 5057 INFO nova.compute.manager [req-
4e1b4d70-62b6-4158-8413-3c9f226fd13b - - - - -]
Public bug reported:
I launch a VM which use vhost-user netdevice as follows.When detach the
netdevice in qemu monitor, the chardevice which used by the netdevice also
should be deatched.The netdevice can be detached sucessfully.But the chardevice
failed when it was being detaching.
Full
26 matches
Mail list logo
