keep in mind you need to stop your VM and start it again for this change to be activated. unfortunately the update crashed with errorĠxC1900101 - 0x20017 The installation failed in the SAFE_OS phase with an error during BOOT operation I had a windows 7 license laying around so i used that but wanted to upgrade to win 10. I followed the suggestions in a Proxmox forum thread and switched to virtio. once the nic crashes, one has to go to network settings in windows and disable, then enable the card and it will be back online. I've experienced this first hand on a CCTV server that had to monitor a couple of cameras. however, using the e1000 (default if no model is given) is not recommended for windows VM's as this model has a tendency to crash and lose connection under heavy use. you can leave the model= option away on the first boot in order to download the virtio iso and install the drivers before switching over to virtio. Notice you will need virtio drivers for the nic to work. The default qemu-ifup script in /etc/ will do the rest for you. Now in your qemu command line you ened to add the parameters Now either reboot your machine or try to get your eth0 down using ifconfig and then get br0 up using ifup however be careful when you are doing this all remoetely!! in that case make really really sure you got your config right or even better, setup a backdoor, make sure your remote management module is accessible, whatever. Notice: you won't need any block for eth0 after you defined the bridge interface. Now change your /etc/network/scripts file and basically replace eth0 with br0 and then add three lines for the bridge config. You need to install bridge-utils to be able to create a bridge network device if you want your vm to be part of your network like any physical machine you have connected to your swich you can use a bridged connection. it may load the wrong one if you just select the root directory and let the installer search for it, resulting in an unstable windows vmīy default qemu uses nat-ed network, so that the vm is in its own network and the vm host acts as a nat router. make sure you choose the correct virtio storage driver for your windows version. you need to load the derivers from the second cdrom that is emulated. Now connect with your favourite vnc client to the ip of your server and install windows. Qemu-system-x86_64 -enable-kvm -k de-ch -name windows -vnc :1 -cdrom /dev/cdrom -drive file=/vm/virtio-win.iso,media=cdrom -boot d -drive file=/vm/windows.img,if=virtio,format=raw,index=0 -m 4096 Since I want to use virtio for fast hdd emulation, we also need the virtio drivers cd /vm if your server dos not have a cd rom you can also us an iso image instead. In my case i had a windows 7 cd that i installed from. however, it does not support snapshots, use qcow2 if you need snapsots or if your filesystem does not support sparse files) second you can easily mount it using mount -o loop at any time. all journalling filesystems that use inodes support that, so ext4 for example works fine. (note: creating a raw image has severale advantages: if your filesystem supports sparse files, it only uses the actually used space of your virtual disk on your physical disk. Qemu-img create -f raw /vm/windows.img 100G
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |