Question is where is this zero checksum observed which is not clear from
the report.
If in the guest it is certainly correct.
If in the host it is correct so long as the bridge appears to have
checksum offloading as well. If whatever interface the guest packets
appear to come from is not set up
Also this is what bridge.conf contains:
# Access control file for qemu bridge helper
# Syntax consists of:
# # comment (ignored)
# allow all
# allow
# deny all
# deny
# include /path/to/additional/ACL/file
# Users are blacklisted by default and 'deny' takes precedence over 'allow'.
Public bug reported:
qemu output:
access denied by acl file
qemu-system-ppc64: bridge helper failed
Option description:
-netdev bridge,id=id[,br=bridge][,helper=helper]
Connect a host TAP network interface to a host bridge device.
Use the network helper helper to
I see no option in Xorg.conf to match serial. Maybe there is. It is
mostly undocumented, especially for some random ancient X11 snapshot the
distro has.
That said the VM happens to be configured in such a way it works -
keyboard and mouse are in same order on USB bus and in Xorg.conf
--
You
This is a problem with ancient Linux distributions that match vendor-
product in Xorg.conf as well.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1096714
Title:
qemu 1.3.0: usb devices shouldn't
Public bug reported:
There is no way to tell qemu to handle (or not) ^C on standard input.
This makes using serial console on stdio needlessly annoying and
difficult.
The code is there - depending on how you set up the console it may
handle the signal or not.
That's completely backwards. The
Also http://airlied.livejournal.com/69291.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037606
Title:
vmwgfx does not work with kvm vmware vga
Status in Linux:
Confirmed
Status in QEMU:
The kernel bugzilla response is:
The vmwgfx kernel module does not support devices without the pitchlock
capability. Sorry. In that case you need to use the xf86-video-vmware
driver standalone without kernel modesetting.
So presumably this is some capability to be added to the qemu device
--
Does qemu allow to disable the PS/2 port now?
If so then there is easy workaround in case something similar ever
happens.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/639651
Title:
tive endian.
With muliple layers of headers this is a bit tricky. A few message types
have to be swapped fully before passing through vdagentd.
Signed-off-by: Michal Suchanek <msucha...@suse.de>
---
v2:
- introduce helper functions to swap (a portion of) a message wholesale
- pollute fe
Signed-off-by: Michal Suchanek <msucha...@suse.de>
---
src/vdagentd/vdagentd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/vdagentd/vdagentd.c b/src/vdagentd/vdagentd.c
index 991514e..60a866e 100644
--- a/src/vdagentd/vdagentd.c
+++ b/src/vdagentd/vdagentd.c
@@ -334,6 +334,7 @@
pastes fast.
Signed-off-by: Michal Suchanek <msucha...@suse.de>
---
ui/gtk.c | 58 ++
1 file changed, 54 insertions(+), 4 deletions(-)
diff --git a/ui/gtk.c b/ui/gtk.c
index a216216..58e97ab 100644
--- a/ui/gtk.c
+++ b/ui/gtk.c
@@ -1
pastes fast.
Signed-off-by: Michal Suchanek <msucha...@suse.de>
---
ui/gtk.c | 57 +
1 file changed, 53 insertions(+), 4 deletions(-)
diff --git a/ui/gtk.c b/ui/gtk.c
index a216216..b3810c7 100644
--- a/ui/gtk.c
+++ b/ui/gtk.c
@@ -1
This is gtk interface.
However, the function on line 40 os spapr_vty.c looks really insane.
It asserts that it is not given more data to input in a ring buffer than
is size of the buffer and then stuffs all the data in regardless of the
amount of data already present.
It should probably loop or
Which interface is this?
I suspect this behaves differently in GTK/SDL/...
Also it seems to WorkForMe(tm) mostly. qemu tends to ignore the layout
completely so installing same keymap in host and guest gives consistent
result, and other configurations give inconsistent but correct result.
--
ncurses version in SUSE does not have .pc files so this is still needed to
build from git.
Signed-off-by: Michal Suchanek <msucha...@suse.de>
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index fd6f898..aab70ef 100755
--- a/con
Public bug reported:
This is broken in git and reportedly in 2.5 through 2.7.
Running a Linux kernel which includes a testsuite in initrd sometimes
produces no output.
Reportedly the console is sometimes not open when the early userspace
tries to log output resulting in either the testsuite
Public bug reported:
- run qemu-system-ppc64
- when X window appears press Ctrl+Alt+3
- paste any text longer than 16 characters
qemu-system-ppc64:
/home/abuild/rpmbuild/BUILD/qemu-2.6.1/hw/char/spapr_vty.c:40: vty_receive:
Assertion `(dev->in - dev->out) < 16' failed.
Aborted (core dumped)
The qxl display and vdagent running in guest do just this.
Unfortunately, the options needed in qemu command line to make vdagent
work with the spice client do not seem to be documented anywhere.
see bug 1452742
--
You received this bug notification because you are a member of qemu-
devel-ml,
Public bug reported:
Hello,
I tried running a guest with vdagent which is supposed to resize the
guest screen to match client window size.
However, a special serial port needs to be created for the vdagent to
communicate with the client.
This patch adds a short note to the vga qxl option.
**
On 13 June 2014 09:33, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
However,
-device nec-usb-xhci -usbdevice host:0b95:772b -usbdevice tablet
gives empy xhci bus and both devices attached to uhci bus which does not
work.
Either drop '-usb' so xhci is the only usb controller, or use
On 13 June 2014 10:12, Gerd Hoffmann kra...@redhat.com wrote:
On Fr, 2014-06-13 at 09:46 +0200, Michal Suchanek wrote:
On 13 June 2014 09:33, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
However,
-device nec-usb-xhci -usbdevice host:0b95:772b -usbdevice tablet
gives empy xhci bus
On 13 June 2014 16:51, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
Ok, so without a machine description that has ehci or xhci as default
device you cannot use -usbdevice and with -device you get a magic
incantation like -device usb-ehci,id=usb,bus=pci.0,addr=0x4 -device
So the RightWay(tm) to fix this is to download
http://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/ich9-ehci-
uhci.cfg;hb=HEAD
and run
qemu-system-x86_64 -net none -readconfig ich9-ehci-uhci.cfg -device usb-
host,vendorid=0x0b95,productid=0x772b -device usb-tablet extra options
here
--
You
Actually, in qemu 2.0.0 the file is packaged. However, it is packaged in
the qemu package rather than qemu-system package so users are unlikely
to have the file.
** Also affects: qemu (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Hello,
I hit bug https://bugs.launchpad.net/qemu/+bug/685096 and found the
usb2.txt file in the source which is sadly not installed by the
distribution.
What I would like is an -usb2 option which instantiates both uhci/ohci
and ehci root hubs. I don't particularly care if the buses appear as
On 12 June 2014 11:08, Gerd Hoffmann kra...@redhat.com wrote:
On Do, 2014-06-12 at 10:53 +0200, Michal Suchanek wrote:
Hello,
I hit bug https://bugs.launchpad.net/qemu/+bug/685096 and found the
usb2.txt file in the source which is sadly not installed by the
distribution.
What I would like
On 12 June 2014 12:26, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
However, for the piix4 which is the default platform and is desirable
due to driver issues in many cases no simple way to instantiate the
companion setup and have qemu automagically attach the devices
correctly exists.
We
I can connect to network with qemu 2.0 with and win 7 pro 64bit guest.
qemu-system-x86_64 -machine accel=kvm -smp 2 -m 1024 -net none -device
usb-ehci,id=usb,bus=pci.0,addr=0x4 -device usb-
host,vendorid=0x0b95,productid=0x772b,id=hostdev0,bus=usb.0 -usb
-usbdevice tablet -hda
On 26 April 2012 18:23, Serge Hallyn 504...@bugs.launchpad.net wrote:
This may be the root cause of bug 986192
I guess not. That bug is TwinView specific but this issue happens with
any graphics.
In fact, in qemu 1.5 this issue is no longer present.
--
You received this bug notification
So this is a compiler or system header error?
Anybody examined the differences in code generated with native compiler
and crosscompiler?
Is there some code difference or are wrong kernel headers pulled from
i386 resulting in invalid syscalls?
--
You received this bug notification because you
It might be just coincidence but if you read the above comments you will
notice that people who compiled qemu natively on arm report that they
can run various binaries without issue but people who crosscompiled
report that they can't run the simplest i386 shell utilities.
How come that the
I guess the problem here is that qemu emulates some very basic mouse
(reported as PS/2 compatible mouse in Windows) whereas real hardware
usually has a fancy mouse (reported as MS Explorer compatible mouse in
Windows).
I don't know how PS/2 mice are detected but due to different mice being
** Tags added: precise running-unity
** Description changed:
vmwgfx driver fails to initialize inside kvm.
tried: kvm -m 2048 -vga vmware -cdrom RebeccaBlackLinux.iso (Ubuntu
based, any Ubuntu live CD would do)
Apport data collected with qantal alpha live CD (somewhat older
** Bug watch added: Linux Kernel Bug Tracker #46711
http://bugzilla.kernel.org/show_bug.cgi?id=46711
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=46711
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265239/+files/ProcModules.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037606
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265242/+files/WifiSyslog.txt
** Description changed:
vmwgfx driver fails to initialize inside kvm.
- tried: kvm -m 2048 -vga vmware -cdrom RebeccaBlackLinux.iso (Ubuntu based,
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265237/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037606
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265240/+files/UdevDb.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037606
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265238/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
apport information
** Tags added: apport-collected quantal
** Description changed:
vmwgfx driver fails to initialize inside kvm.
- tried: kvm -m 2048 -vga vmware -cdrom RebeccaBlackLinux.iso (Ubuntu
- based, any Ubuntu live CD would do)
+ tried: kvm -m 2048 -vga vmware -cdrom
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265241/+files/UdevLog.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037606
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265235/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037606
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265236/+files/Lspci.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037606
Title:
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265234/+files/BootDmesg.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037606
apport information
** Attachment added: AlsaInfo.txt
https://bugs.launchpad.net/bugs/1037606/+attachment/3265233/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037606
Title:
** Attachment added: the error
https://bugs.launchpad.net/bugs/1037606/+attachment/3263897/+files/screenshot-20120816163835.png
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
There is screenshot of the error message.
The message reads
*ERROR* Hardware has no pichlock
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Since the error prevents graphical environment from starting and apport-
collect requires a graphical browser to post the data it collects it is
not useful to run.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member
There seems to be an issue with kvm virtual network interface being
connected to a in-kernel bridge implementation.
When you configure networking that way the bridge port comes up when the
kvm instance is started.
As the time from the kvm start to entering the netboot rom is minimal
and the
I use serial console to cutpaste between host and guest without
networking.
It's nice SPICE is addressing this but I agree this is not really
something qemu itself should do. There is no hardware cutpaste device
qemu can emulate, the video hardware has not notion of cutpaste.
At the very least
Isn't the issue here that the emulated card has too low video memory
forcing 800x600 when the driver selects the default 24bpp depth?
This is an issue with some very old real hardware too.
I guess X could account for that but due to its architecture every
driver would likely have a separate
Public bug reported:
Adds an option to disable the PS/2 mouse.
This is useful to work around bugs in PS/2 drivers in some system or
testing system without a PS/2 mouse present.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you
** Attachment added: patch against kvm 0.14
https://bugs.launchpad.net/bugs/813546/+attachment/2220915/+files/nops2.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/813546
Title:
option to
My window manager maximizes all windows. I am running kvm 0.14.
Initially the VM is displayed 1:1 in the top left corner leaving large
portion of the window black. Resizing the window or rebooting the VM
causes the output to be scaled which is horrendous.
There are three issues here: there is
Hello
attaching a patch that allows disabling the PS/2 mouse.
I use this feature to prevent Windows XP guest with recent Synaptics
driver installed from crashing at boot.
The Synaptics driver is somewhat misguided in that (unlike earlier
versions) it installs on pretty much any PS/2 hardware
On 1 June 2011 05:12, Zhi Yong Wu wu...@linux.vnet.ibm.com wrote:
On Tue, May 31, 2011 at 03:55:49PM -0400, Vivek Goyal wrote:
Date: Tue, 31 May 2011 15:55:49 -0400
From: Vivek Goyal vgo...@redhat.com
To: Zhi Yong Wu wu...@linux.vnet.ibm.com
Cc: kw...@redhat.com, aligu...@us.ibm.com,
Public bug reported:
Running a VM using raw sparse disk image on kvm 0.14 on Debian.
When disk writes use up all disk space kvm locks up.
if it cannot handle this situation gracefully (eg suspend the VM until
space becomes available) it should at the very least report an error and
exit, not
On 29 May 2011 13:33, Stefan Hajnoczi stefa...@gmail.com wrote:
On Sun, May 29, 2011 at 11:48 AM, Michal Suchanek hramr...@centrum.cz wrote:
Public bug reported:
Running a VM using raw sparse disk image on kvm 0.14 on Debian.
When disk writes use up all disk space kvm locks up
Public bug reported:
loading the vmwgfx module of kernel 2.6.39-rc7 in kvm 0.14 results in
[drm:vmw_driver_load] *ERROR* Hardware has no pitchlock
and the kernel module fails.
Consequently vmwgfx is broken, only the vmwlegacy driver works.
** Affects: qemu
Importance: Undecided
On 10 May 2011 13:56, Richard W.M. Jones rjo...@redhat.com wrote:
So I'd like feedback from virt-clone next generation users:
(a) Is cloning guests useful for you or not? Often or infrequently?
I clone guests quite often.
(b) Do you currently use virt-clone to clone guests?
no
(c) Do
On 23 March 2011 23:32, Jordan Justen jljus...@gmail.com wrote:
2011/3/23 Gleb Natapov g...@redhat.com:
On Tue, Mar 22, 2011 at 02:53:16PM -0700, Jordan Justen wrote:
To support a boot override for UEFI, this full path would be needed.
For the purposes of a UEFI boot override, could the user
Hello,
On 11 March 2011 20:09, Jordan Justen jljus...@gmail.com wrote:
On Thu, Mar 10, 2011 at 16:27, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 11.03.2011 01:19, Jan Kiszka schrieb:
At least it's an in-band interface, which is the better choice as we
currently only
Hello
On 7 March 2011 11:22, Peter Maydell peter.mayd...@linaro.org wrote:
On 6 March 2011 15:29, Michal Suchanek hramr...@centrum.cz wrote:
I would like to see the ability to run x86 on arm.
I think there were some attempts to implement this and an outdated?
support for arm on x86 exists
Hello
On 6 March 2011 05:12, Jordan Justen jljus...@gmail.com wrote:
I know you already have your own ideas to think of. :)
http://wiki.qemu.org/Google_Summer_of_Code_2011
But, I am wondering if any of you might have some UEFI or OVMF ideas for us:
Hello,
is it possible to run OS X in kvm or qemu?
I would like to be able to test some stuff in OS X on my mac mini
without rebooting the system.
Last time I looked at this I found a bunch of patches. From the top of
my head these included:
multiboot support to be able to use BootX (in qemu
On 13 January 2011 00:34, Mateusz Loskot mate...@loskot.net wrote:
On 12/01/11 17:15, Mateusz Loskot wrote:
On 12/01/11 16:48, Michal Suchanek wrote:
On 12 January 2011 16:21, Mateusz Loskotmate...@loskot.net wrote:
Thinking of future, could anyone estimate when it will be possible to
boot
On 12 January 2011 16:21, Mateusz Loskot mate...@loskot.net wrote:
On 12/01/11 14:40, Artyom Tarasenko wrote:
On Wed, Jan 12, 2011 at 3:28 PM, Mateusz Loskotmate...@loskot.net
wrote:
On 12/01/11 12:32, Mateusz Loskot wrote:
On 12/01/11 11:57, Artyom Tarasenko wrote:
On Wed, Jan 12, 2011
On 12 January 2011 20:17, Stefan Weil w...@mail.berlios.de wrote:
Am 12.01.2011 20:05, schrieb Stefan Weil:
Hi,
this is a regression in current QEMU: it cannot create disk images larger
than 2^31 B (2 GiB).
It's discussed at
On 7 January 2011 18:28, Mateusz Loskot mate...@loskot.net wrote:
Hi,
First, I'm sorry if my question does not belong here. The qemu-devel
says it's devel, but I can't find any qemu-users mailing list.
I have seen it once but could not find it either when searching for a
qemu mailing list to
On 19 October 2010 08:17, Alexander Graf ag...@suse.de wrote:
Am 19.10.2010 um 02:10 schrieb Anthony Liguori anth...@codemonkey.ws:
On 10/18/2010 06:29 PM, Alexander Graf wrote:
A user will get a really nasty surprise if they think they can use a flag
or rely on QEMU to prevent a VM from
On 7 October 2010 11:05, Jes Sorensen 639...@bugs.launchpad.net wrote:
Just to be sure, you are not using the virtio-blk driver for Windows
here?
I have seen similar crashes with the older version of virtio-blk when used on
recent versions of KVM.
--
DRIVER_IRQL_NOT_LESS_OR_EQUAL booting
I have no idea how to log the data.
I looked at the qemu man page but it does not even mention the PS/2
mouse as a chardev nor offers an option to log traffic of chardevs
without attaching them to a file and thus detaching them from the
emulated device.
Thanks
Michal
--
Attaching logged PS/2 port communication.
** Attachment added: PS/2 communication log
https://bugs.launchpad.net/qemu/+bug/639651/+attachment/1677112/+files/qemu-ps2.log
--
DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed
For reference attaching the patch used for obtaining the log.
** Patch added: patch used to obtain the above log
https://bugs.launchpad.net/qemu/+bug/639651/+attachment/1677122/+files/ps2dump.diff
--
DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed
is enabled.
Thanks
Michal
Signed-off-by: Michal Suchanek hramr...@centrum.cz
---
hw/isa.h|1 +
hw/pckbd.c | 36 +---
qemu-options.hx |9 +
vl.c|4
4 files changed, 35 insertions(+), 15 deletions(-)
diff --git a/hw
The output is not centered.
I am not sure how to achieve that because SDL just sets a video mode
which starts at upper left corner of the window.
It would be possible to make the mode larger but then the zoom routines
would have to take an offset.
Signed-off-by: Michal Suchanek hramr
Public bug reported:
$ qemu -nodefaults
press Ctrl+Alt+2 in the black window
Segmentation fault
qemu 0.12.5+dfsg-2
** Affects: qemu
Importance: Undecided
Status: New
--
qemu crashes with -nodefaults
https://bugs.launchpad.net/bugs/643496
You received this
** Summary changed:
- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping
+ DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver
installed
--
DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed
https://bugs.launchpad.net/bugs/639651
** Description changed:
Positng the issue here since I did not get any reply on the ML.
I was trying to update some windows XP (SP3) images in kvm.
It worked fine several times but last time I added mass storage
drivers to sysprep and now on the second boot after reseal (the first
On 16 September 2010 12:08, Avi Kivity a...@redhat.com wrote:
On 09/14/2010 07:29 PM, Michal Suchanek wrote:
Hello
I was trying to update some windows XP (SP3) images on kvm.
It worked fine several times but last time I added mass storage
drivers to sysprep and now on the second boot
** Attachment added: screenshot of the blue screen
https://bugs.launchpad.net/qemu/+bug/639651/+attachment/1593631/+files/gkrellShoot_2010-09-16_152436.png
** Description changed:
Positng the issue here since I did not get any reply on the ML.
I was trying to update some windows XP
On 16 September 2010 15:38, Avi Kivity a...@redhat.com wrote:
On 09/16/2010 03:34 PM, Michal Suchanek wrote:
On 16 September 2010 12:08, Avi Kivitya...@redhat.com wrote:
On 09/14/2010 07:29 PM, Michal Suchanek wrote:
Hello
I was trying to update some windows XP (SP3) images
On 16 September 2010 16:46, Avi Kivity a...@redhat.com wrote:
On 09/16/2010 04:37 PM, Michal Suchanek wrote:
On 16 September 2010 15:38, Avi Kivitya...@redhat.com wrote:
On 09/16/2010 03:34 PM, Michal Suchanek wrote:
On 16 September 2010 12:08, Avi Kivitya...@redhat.com wrote
Note that most of the section is generated by sysprep (the drivers
referencing C:\windows), only small part at the end is generated by my
script for additional drivers (references C:\drivers).
The previous images that did not have this section worked only on
controllers compatible with the MS
On 16 September 2010 19:54, Michal Suchanek hramr...@centrum.cz wrote:
On 16 September 2010 16:46, Avi Kivity a...@redhat.com wrote:
On 09/16/2010 04:37 PM, Michal Suchanek wrote:
On 16 September 2010 15:38, Avi Kivitya...@redhat.com wrote:
On 09/16/2010 03:34 PM, Michal Suchanek wrote
Public bug reported:
Positng the issue here since I did not get any reply on the ML.
I was trying to update some windows XP (SP3) images in kvm.
It worked fine several times but last time I added mass storage
drivers to sysprep and now on the second boot after reseal (the first
is mini-setup) I
Hello
I was trying to update some windows XP (SP3) images on kvm.
It worked fine several times but last time I added mass storage
drivers to sysprep and now on the second boot after reseal (the first
is mini-setup) I get a BSOD with message
DRIVER_IRQL_NOT_LESS_OR_EQUAL. I can post the
88 matches
Mail list logo
