[Qemu-devel] IO port 0x61 is multiple used

2015-03-15 Thread Weidong Huang
Hi ALL: IO port 0x61 is used by pc speaker and NMI reason port. This is ambiguous. How to distinguish in QEMU? I see that NMI reason port is not realized in QEMU. But linux guest will access this port to determine what the NMI reason code means. It will access pc speaker's io port. Is this a

Re: [Qemu-devel] Close the BlockDriverState when guest eject the media

2014-10-20 Thread Weidong Huang
On 2014/10/20 19:39, Kevin Wolf wrote: > Am 20.10.2014 um 13:27 hat Weidong Huang geschrieben: >> On 2014/10/20 17:41, Kevin Wolf wrote: >> >>> Am 18.10.2014 um 12:02 hat Weidong Huang geschrieben: >>>> Hi ALL: >>>> >>>> There are

Re: [Qemu-devel] Close the BlockDriverState when guest eject the media

2014-10-20 Thread Weidong Huang
On 2014/10/20 20:12, Markus Armbruster wrote: > > Correct. This is a known wart. To work around it, wait for event > DEVICE_TRAY_MOVED and eject again. Yes, this is racy: the guest can > reclose the tray and lock it before you get your eject in. Yes. You got it. But how to resolve the racy?

Re: [Qemu-devel] Close the BlockDriverState when guest eject the media

2014-10-20 Thread Weidong Huang
On 2014/10/20 19:39, Kevin Wolf wrote: > Am 20.10.2014 um 13:27 hat Weidong Huang geschrieben: >> On 2014/10/20 17:41, Kevin Wolf wrote: >> >>> Am 18.10.2014 um 12:02 hat Weidong Huang geschrieben: >>>> Hi ALL: >>>> >>>> There are

Re: [Qemu-devel] Close the BlockDriverState when guest eject the media

2014-10-20 Thread Weidong Huang
On 2014/10/20 17:41, Kevin Wolf wrote: > Am 18.10.2014 um 12:02 hat Weidong Huang geschrieben: >> Hi ALL: >> >> There are two ways to eject the cdrom tray. One is by the eject's qmp >> commmand(eject_device). >> The another one is by the guest(bdrv_eject).

[Qemu-devel] Close the BlockDriverState when guest eject the media

2014-10-18 Thread Weidong Huang
Hi ALL: There are two ways to eject the cdrom tray. One is by the eject's qmp commmand(eject_device). The another one is by the guest(bdrv_eject). They have different results. eject_device: close the BlockDriverState(bdrv_close(bs)) bdrv_eject: don't close the BlockDriverState, This is ambiguou

Re: [Qemu-devel] [PATCH 2/7] qemu-char: Allow a chardev to reconnect if disconnected

2014-03-05 Thread Weidong Huang
On 2014/3/5 8:38, miny...@acm.org wrote: > From: Corey Minyard > > Allow a socket that connects to reconnect on a periodic basis if it > fails to connect at startup or if the connection drops while in use. > > Signed-off-by: Corey Minyard > --- > include/sysemu/char.h | 16 - > qemu-char

[Qemu-devel] 【Question】About "Add an IPMI device to QEMU" patches

2014-02-27 Thread Weidong Huang
Hi, I am interesting in your patches about the IPMI device addition. When will you commit the next version? Best regards, -Huang WeiDong

Re: [Qemu-devel] question about patch "send the gratuitous by guest"

2014-02-17 Thread Weidong Huang
On 2014/2/18 10:48, Jason Wang wrote: > On 02/15/2014 11:01 AM, Weidong Huang wrote: >> it >> configure vlan or alias on the virtio net. >> >> But bridge or bond do not send arp. what's your opinion? > > Do you mean bridge or bond in guest? yes. >> &

Re: [Qemu-devel] question about patch "send the gratuitous by guest"

2014-02-15 Thread Weidong Huang
Hi， after testing your patch,the guest will send arp packet when it configure vlan or alias on the virtio net. But bridge or bond do not send arp. what's your opinion? BTW,this feature need modify the driver of virtio net. Only the newest linux kernel support it. So what's about old guest os?