Rhanks for any idea...
PC
On 11/7/22 17:38, Simon Becherer wrote:
Am 07.11.22 um 16:42 schrieb Pierre Couderc via:
I have never gone in virt-manager, but I suppose that there sould be
corresponding native instruction...
i changed about 3 years in past from my shellscripts to virt-manager
and i have never
On 11/7/22 14:00, Simon Becherer wrote:
Am 07.11.22 um 13:52 schrieb Pierre Couderc via:
On 11/7/22 12:10, Simon Becherer wrote:
Am 07.11.22 um 10:49 schrieb Pierre Couderc via:
I use a XP guest in qemu on linux.
I use a 4K monitor and my 800x600 XP windows is very very small, lost in
On 11/7/22 12:10, Simon Becherer wrote:
Am 07.11.22 um 10:49 schrieb Pierre Couderc via:
I use a XP guest in qemu on linux.
I use a 4K monitor and my 800x600 XP windows is very very small, lost in the 4K
monitor.
I do not want to change my 800x600 size nor my monitor.
But I would like
On 11/7/22 11:49, Narcis Garcia wrote:
I do this by VNC display, and specifying scale factor to VNC client.
El 7/11/22 a les 10:49, Pierre Couderc via ha escrit:
I use a XP guest in qemu on linux.
I use a 4K monitor and my 800x600 XP windows is very very small, lost
in the 4K monitor.
I
I use a XP guest in qemu on linux.
I use a 4K monitor and my 800x600 XP windows is very very small, lost in
the 4K monitor.
I do not want to change my 800x600 size nor my monitor.
But I would like to enlarge the XP window so that a XP pixel be mapped
on 4 monitor pixels, or even if possib
I emulate XP on a debian amd64 PC with tap, since years :
qemu-system-x86_64 -enable-kvm -uuid
564d6522-2227-cda9-d1c7-390c71f68dbe -drive
driver=qcow2,file=/home/nous/qemu/xp/TOLL-XPVM.qcow2 -net
nic,model=rtl8139,macaddr=00:0C:29:B6:8D:BE -net
tap,ifname=tap0,script=no -net user
My XP VM "blocks" after a few minutes, that is 100% cpu on the qemu
core, nothing (mouse...) responding in the VM, and difficults (delay) to
quit the VM by ctrl-Alt-G. And moreover outside of the VM,
isc_socket_bind seems to be solicited (by qemu or by the XP VM) so much
that no more name reso
Currently WM_CLASS(STRING) is "qemu-system-x86_64".
I would like to change it to "qemu-XP", "qemu-W10",etc...
I success to chane -name qemu-XP but it doe not change the WM_CLASS...
Thanks for any help..
PC
On 07/27/2018 12:34 PM, Greg Kurz wrote:
On Fri, 27 Jul 2018 09:23:36 +0200
Pierre Couderc wrote:
Thank you very much, Pascal.
When I compare what is working for you :
the difference seems to be the presence of IPV6 in 'bad' case...
And the /24 mask... maybe try to do t
1>: icmp_seq=4 ttl=64
time=0.015 ms
--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3107ms
rtt min/avg/max/mdev = 0.015/0.017/0.021/0.005 ms
regards.
2018-07-26 19:19 GMT+02:00 Pierre Couderc <mailto:pie...@couderc.eu>>:
My bridge for qemu is
My bridge for qemu is started with :
sysctl net.ipv4.ip_forward=1
tunctl -t tap0 -u nous
ifconfig tap0 192.168.164.1 up
iptables...
I have replaced ipconfig line with ip:
ip link set tap0 up
ip address add 192.168.164.1 dev tap0
but it fails (no ping 192.168.164.1) in the vm.
What do I miss ?
I am looking for a howto for bridging on a laptop with wifi so that
the VMs are not in their own qemu subnetwork but remain in the LAN and
can be accessed from anywhere in the LAN.
Thank you in advance
PC
On 10/25/2017 04:57 PM, Nerijus Baliūnas wrote:
partx -a /dev/nbd0
Thank you very much. There are many incomplete howto on the web... Imake
a tutorial (on the web) for myself first.
It is a XP image.
#modprobe nbd max_part=8
#qemu-nbd -c /dev/nbd0 /home/nous/qemu/xp/XPVM.qcow2
#mount /dev/nbd0p1 /media/a
mount: special device /dev/nbd0p1 does not exist
More details here :
#lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 447.1G 0 disk
├─sda1 8:1
On 09/27/2017 10:49 PM, Pierre Couderc wrote:
I have compiled and built from git qemu tag 2.10.0 (./configure
--target-list=x86_64-softmmu --enable-debug) and I find it much more
slow than the debian package that I used before. kvm is enabled.
The mouse does not react, tests done with host
I have compiled and built from git qemu tag 2.10.0 (./configure
--target-list=x86_64-softmmu --enable-debug) and I find it much more
slow than the debian package that I used before. kvm is enabled.
The mouse does not react, tests done with host debian wheezy on various
Windows image, or stretch
I get this message when trying to use smb with W hosts.
What can I do ?
Thanks
PC
I am switching from vmw to qemu and I am stoped by this problem.
onn a linux system, I know how to mount a directory such as :
-virtfs
local,path=path/to,security_model=passthrough,id=host0,mount_tag=host0
But how should do for it to be ssen as D: from a W guest ?
Sorry, cetainly basic, but I hwave not found on google...
Thanks
PC
After converting a vmdk disk to qcow2, I get this error trying to boot.
My command line is :
kvm -drive file=TOLL-XPVM.qcow2 -net nic,macaddr=00:0C:29:F6:8D:BE
-net tap -uuid 564d6522-2227-cda9-d1c7-390c71f68dbe
I have extracted macadr and uuid from vmware files, but this does not
see
On 07/08/2017 10:25, Fam Zheng wrote:
On Mon, 08/07 10:10, Pierre Couderc wrote:
On 08/07/2017 09:50 AM, Fam Zheng wrote:
On Mon, 08/07 09:37, nous wrote:
I have tried qemu-img but it converts only the 1rst vmdk vmware disk...
and I have 20 other ones...
And did someone someday success in
On 08/07/2017 09:50 AM, Fam Zheng wrote:
On Mon, 08/07 09:37, nous wrote:
I have tried qemu-img but it converts only the 1rst vmdk vmware disk...
and I have 20 other ones...
And did someone someday success in doing that ?
What are your vmdk files like?
The splitted VMDK images have a descript
23 matches
Mail list logo
