similar to: [PATCH] com32: write_sectors fixes

Here is a partial patch that I'm using to illustrate a few questions that I have. Looking at the gpllib write_sectors (com32/gpllib/disk/write.c) it looks like the allocated size is wrong; size is in sectors so we should adjust the alloc/memcpy by size*SECTOR. Also, comparing core/diskio.c it looks like the registers aren't even setup right. In the patch below I put an #if 0 around the

Hi, Hopefully you someone can tell me what I'm doing wrong. First, the code. I placed this at the bottom of the main loop in com32/modules/disk.c as a simple test of writing to the disk: printf(" Host bus: %s, Interface type: %s\n\n", d->edd_params.host_bus_type, d->edd_params.interface_type); zero_buf = calloc(1, d->edd_params.bytes_per_sector); for(int

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:

Hi libvirt experts, I have some questions about live migration. * If a live migration failed during migrating, will the domain exist on the destination host? * Is the flag VIR_MIGRATE_PAUSED make sense to live migration? It's a little confusing for me. Does that indicate if I set this flag, then the domain on the destination will not disappear even if the migration is failed, and it will in

Linus' tree has a space-tab sequence for a few lines in these files, causing an unnecessary delta. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 7c753dbe7467f0d5ff6904f1bf5840350527e3c4 tree c40a68f6556a702a836d9a6e90f5d632eed0bc0c parent 0f5a324d655ad582246b6830843114d09835f593 author H. Peter Anvin <hpa at zytor.com> Thu, 06 Apr 2006 14:15:53 -0700 committer H.

ROOT_DEV carries a root device number communicated in an architecture- specific way. We now pass it to kinit via the real-root-dev sysctl call. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 0f5a324d655ad582246b6830843114d09835f593 tree fd3a96a69b6d74ee33dcd54a58b8666c02139a3a parent f3e41698e540a7d39658d6590fde1379c0f5bab0 author H. Peter Anvin <hpa at zytor.com> Thu,

> > For me this has a very low priority, as the jpg workaround is just fine. Well, vesamenu.c32 under UEFI, although "almost needed", it is already behaving in a crappy manner anyway :(. (Reminder, FWIW, PNG is non-patented, loss-less and popular.) With so many regressions and features not working (in vesamenu under UEFI), I have "suggested" in past months /

I compile the latest libvirt from fedora rawhide, but failed. The version of my software: wireshark-devel-2.0.1-2.fc24.x86_64 glib2-2.47.5-2.fc24.x86_64 gcc-5.1.1-4.fc23.x86_64 binutils-2.26-10.fc24.x86_64 The error as following: # ./autogen.sh --prefix=/usr && make ..... wireshark/src/plugin.c:5:21: fatal error: gmodule.h: No such file or directory compilation terminated. Makefile:2442:

On Fri, Oct 18, 2019 at 15:00:19 +0800, Luyao Zhong wrote: > Hi libvirt experts, > > I have some questions about live migration. I'm assuming you are not asking about post-copy migration, since it is a bit more complicated as the current state if split between the source and destination hosts and none of them can keep running without the other until migration finishes. > * If a

Fix breakage in the "hide" option support patch: - The code which initialized the global variable "dapa" was lost in commit 81c203f2, therefore EBIOS access did not work properly. Fixed by removing the global variable completely and moving all bounce buffer handling into read_sector() and write_sector(). - write_sector() copied data to the bounce buffer, but then

This patch adds a 'raid' interface class. It is basically a clone of the existing 'scsi' interface, only allowing up to 128 disks. Signed-off-by: Hannes Reinecke <hare at suse.de> --- hw/pc.c | 5 +++++ hw/pci-hotplug.c | 1 + hw/scsi-disk.c | 17 +++++++++++++++++ hw/scsi-disk.h | 20 +++++++++++++++++++- qemu-config.c | 2 +- sysemu.h

This patch adds a 'raid' interface class. It is basically a clone of the existing 'scsi' interface, only allowing up to 128 disks. Signed-off-by: Hannes Reinecke <hare at suse.de> --- hw/pc.c | 5 +++++ hw/pci-hotplug.c | 1 + hw/scsi-disk.c | 17 +++++++++++++++++ hw/scsi-disk.h | 20 +++++++++++++++++++- qemu-config.c | 2 +- sysemu.h

Hi all, I committed win32-driveinfo 0.1.0 to CVS. What is it? =========== A class for getting information of drives Synopsis ======== include Win32::DriveInfo (sectorsPerCluster, bytesPerSector, numberOfFreeClusters, totalNumberOfClusters, freeBytesAvailableToCaller, totalNumberOfBytes, totalNumberOfFreeBytes) = getDriveSpace(''c'').to_a

Sorry, hit send instead of attach again. Rest of patches included. -- Anthony Liguori Samba, Linux/Windows Interoperability Linux Technology Center (LTC) - IBM Austin E-mail: aliguori@us.ibm.com Phone: (512) 838-1208 Tie Line: 678-1208

Hi Shanko, I''ve read over the testunit results that you posted. First, please do not include win32-thread or win32-driveinfo. The former is extremely beta. The latter I want to reshape a bit before we release it. Other tests: You can ignore the LINK warnings. win32-dir - These failures are expected. Ignore. win32-file - You can ignore the warnings regarding File.encrypt and

Updating myself again: On 07-08-15 16:03, Oscar Roozen wrote: > e466d24 still has an issue with png's in vesalinux causing crashes I can confirm this remaining crash is caused by the line "MENU BACKGROUND bootlogo.png". The original bootlogo.png is 640x480. Forcing the videomode with "MENU RESOLUTION 640 480" did not resolve the crashes, nor did resizing the png

From 4780a4792ca7776268107e200ae77003c36d55c9 Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:52:43 +0200 Subject: [PATCH] virtio block device This patch implements the backend support for the virtio block device. It's designed to support in-order queueing of a virtually unlimited size so it will be able to perform better than SCSI. Besides

From 4780a4792ca7776268107e200ae77003c36d55c9 Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:52:43 +0200 Subject: [PATCH] virtio block device This patch implements the backend support for the virtio block device. It's designed to support in-order queueing of a virtually unlimited size so it will be able to perform better than SCSI. Besides

ldisk.c32 is a Lua module that provides information about disks to Lua scripts The example script com32/lua/test/detect_disks.lua uses it to implement some- thing akin to 'disk.c32'. The name 'ldisk.c32' was chosen to avoid a name-clash with 'disk.c32'. --- com32/lua/src/Makefile | 1 + com32/lua/src/ldisk.c | 103

This should help us to: - More easily add or remove machine initialization arguments without having to change every single machine init function; - More easily make mechanical changes involving the machine init functions in the future; - Let machine initialization forward the init arguments to other functions more easily. This change was half-mechanical process: first the struct was added